sysuptime events creating false criticals
Hi,
Support seem to be stumped on this one so i'm hoping someone out there has managed to fix this problem.
We have about 100 Cisco switches each only monitoring 1 or 2 Gigabit trunk ports and the switch itself.
We've minimised it for this so we have a nice clean system that will send us an alert in the event anything critical happens and won't bother us with trivial port issues.
The problem we are having is that all our cisco 3560's are sending sysuptime critical events using the same OID as the linkdown constantly for ports opmanager is not supposed to be even monitoring.
for example :
Critical Nov 18,2008 03:27:27 PM sysUpTime: -1234643945, snmpTrapOID: .1.3.6.1.6.3.1.1.5.3, ifIndex: 6, ifDescr: FastEthernet0/5, ifType: ethernetCsmacd, .1.3.6.1.4.1.9.2.2.1.1.20.6: down .1.3.6.1.4.1.9.1.248 c6_2 C
.1.3.6.1.6.3.1.1.5.3 = linkdown
Our dashboard is showing 276 of these generated today alone which is making it difficult to know when genuine issues are occuring and flooding our inboxes.
Support suggested we either turn this trap off on the switch(which means we cannot monitor any of our links) or create a custom trap to change it to non-critical which would also make linkdowns non critical and we wouldnt be alerted. Either way our network monitor isnt working as a network monitor!
As we use very standard hardware I'm sure other people have experienced this issue and I am hoping there is an easy solution.
thanks in advance,
Matt
Support seem to be stumped on this one so i'm hoping someone out there has managed to fix this problem.
We have about 100 Cisco switches each only monitoring 1 or 2 Gigabit trunk ports and the switch itself.
We've minimised it for this so we have a nice clean system that will send us an alert in the event anything critical happens and won't bother us with trivial port issues.
The problem we are having is that all our cisco 3560's are sending sysuptime critical events using the same OID as the linkdown constantly for ports opmanager is not supposed to be even monitoring.
for example :
Critical Nov 18,2008 03:27:27 PM sysUpTime: -1234643945, snmpTrapOID: .1.3.6.1.6.3.1.1.5.3, ifIndex: 6, ifDescr: FastEthernet0/5, ifType: ethernetCsmacd, .1.3.6.1.4.1.9.2.2.1.1.20.6: down .1.3.6.1.4.1.9.1.248 c6_2 C
.1.3.6.1.6.3.1.1.5.3 = linkdown
Our dashboard is showing 276 of these generated today alone which is making it difficult to know when genuine issues are occuring and flooding our inboxes.
Support suggested we either turn this trap off on the switch(which means we cannot monitor any of our links) or create a custom trap to change it to non-critical which would also make linkdowns non critical and we wouldnt be alerted. Either way our network monitor isnt working as a network monitor!
As we use very standard hardware I'm sure other people have experienced this issue and I am hoping there is an easy solution.
thanks in advance,
Matt