This post is more than 5 years old
16 Posts
0
728
June 23rd, 2010 18:00
Brocade SMI Agent for EOS Products
We recently installed Brocade SMI Agent for EOS Products v2.6.2 for Linux on a Redhat Linux server for discovering our McData switches in a ECC 6.1 environment. SMI agent installation and McData switches discovery were all successfuly, however, by looking at the process in the Linux host, smi agent process looks a bit wired, it is very long process name:
# ps -ef|grep agent
daemon 1447 1 0 Jun11 ? 00:00:00 /opt/smi_agent/SMI_Agent_for_EOS_products/agent/bin/linux/slpd -l /opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../cfg/slp.log -c /opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../cfg/slp.conf -r /opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../cfg/slp.reg
root 3498 1 0 Jun11 ? 00:58:58 ../../../../jre/bin/java -classpath /opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/efcmSmisProxy_9_7_3.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/efcmApi_14.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/MClient.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/MCommon.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/MServer.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/SClient.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/SClientStubs.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/SServer.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/SServerStubs.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/SCommon.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/UpdateReleaseVehicle.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/UpdateReleaseVehicleStubs.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/T63Jars/callhome.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/mail.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/jserverinit.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/server.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/sanrouter.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../lib/jserverapi.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../lib/wbem.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../lib/wbem_cimxml.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../lib/wbem_wsman.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../lib/wsi_lib.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../lib/wsi_messages.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../lib/jserver.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../lib/cimrepository.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/../lib/mofcomp.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/jserver_services.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/coma_cimxml.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/coma_wsmanagement.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/poma_jsr48.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/soma_none.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/soma_pam.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/soma_windows.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/AdventNetLogging.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/AdventNetSnmp.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/log4j.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/mpi.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/mibs.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/mcdataEfcmLoader.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/xmlrpc-1.2-b1.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/mcdataProductInterface.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/McDATAServerConfig.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/server.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/sanrouter.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/resources.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/commons-cli-1.0.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/switch.jar:/opt/smi_agent/SMI_Agent_for_EOS_products/agent/server/jserver/lib/fabric.jar -Xmx1024m -Ddebug -Djava.security.manager -Djava.security.
Does anyone has any idea if this is normal?
youngp2
90 Posts
0
June 30th, 2010 11:00
From and EMC perspective we only know how the SMI agents interact with our products. I personally have always had better luck running the SMI agent on a Windows host but that may be becuase I am more familier with that operating system. If this is something that is causing an issue with monitoring the switches or an issue with your host I would recommend opening a ticket with Brocade Support.
If you bought your hardware through EMC and do not have a service contract with Brocade you can open a ticket with ControlCenter and we can open a corresponding ticket with Brocade.
Regards,
Paul Young
EMC Global Services