This content has been marked as final. Show 2 replies
The post about M4000 and Sun Management Center Platform Agent is quite old now but as I had a similar problem I thought it would be still worth to reply to it.
First I would check SNMP connection from the SunMC server to the XSCF:
Users espublic and esmaster are defined by default in the SunMC Agent on XSCF.
# /usr/sfw/bin/snmpget -v 3 -u espublic -l noAuthNoPriv 10.172.21.11:1161 sysUpTime.0
If you get a reply (system time) then connectivity is fine. Well, I would not expect any problems if both hosts are in the same subnet.
Then check how many interfaces you have defined on the XSCF:
The problem in our system was caused by two interfaces (two IP addresses) defined on XSCF.
XSCF> shownetwork -a
I think it happens only when lan#0 is configured with IP address and you connect to Platform Agent on lan#1.
I believe it has something to do with the generation of SNMP v3 keys (or EngineIDs) although I cannot confirm it.
If you have two IPs in XSCF then remove the one that is not required for SunMC. Then, reconfigure and start SunMC Agent.
Here is how I did that:
... wait until XSCF is back after reboot
XSCF> setnetwork -r xscf#0-lan#0 XSCF> applynetwork XSCF> setsunmc disable XSCF> rebootxscf
In my system SunMC server was able to contact the XSCF Platform Agent immediately after that procedure.
XSCF> setsunmc -s <SunMC-server-IP> -z <seed> -c <community> XSCF> setsunmc enable XSCF> showsunmc
The first thing to check is that the XSCF agent security seed matches that of the SunMC server.