Unable to remove old fibre switch port monitor from database ?
we are using IBM BladeCenter with Brocade Fibre switches with Virtual connection capability.
I set up SNMP monitor for swFCPortOpStatus ( .1.3.6.1.4.1.1588.2.1.1.1.6.2.1.4.* ) in Opmanager to monitor active ports incase of failure. Later I found that I can have a better monitor by using another OID. so I remove the old ones and put in the new OID (swFSPortPhyState, .1.3.6.1.4.1.1588.2.1.1.1.6.2.1.3.*). Out of the six switch monitors, only one works and the other 5 still remembers the old OID and keeps coming up with alerts saying some ports have an alerting status with the old OID which I had already removed and deleted.
Strangely, the alerts did not come from every port that is not in use but only from a certain number of ports.
e.g. the switch uses port 0-4 and 5 to 19 are not used. But the alert only comes from ports 13-19.
It looks to me that opmanager was not cleaning out the old parameters properly and keeps scanning the ports with incorrect parameter.
Does anyone knows how to remove the old parameters cleanly ?
Is there a database that may cause this issue ?
Stan..
I set up SNMP monitor for swFCPortOpStatus ( .1.3.6.1.4.1.1588.2.1.1.1.6.2.1.4.* ) in Opmanager to monitor active ports incase of failure. Later I found that I can have a better monitor by using another OID. so I remove the old ones and put in the new OID (swFSPortPhyState, .1.3.6.1.4.1.1588.2.1.1.1.6.2.1.3.*). Out of the six switch monitors, only one works and the other 5 still remembers the old OID and keeps coming up with alerts saying some ports have an alerting status with the old OID which I had already removed and deleted.
Strangely, the alerts did not come from every port that is not in use but only from a certain number of ports.
e.g. the switch uses port 0-4 and 5 to 19 are not used. But the alert only comes from ports 13-19.
It looks to me that opmanager was not cleaning out the old parameters properly and keeps scanning the ports with incorrect parameter.
Does anyone knows how to remove the old parameters cleanly ?
Is there a database that may cause this issue ?
Stan..