Hi,
I have been trying to monitor interface status for a couple of different types of devices and I feel I have hit a brick wall. I would be very grateful for support from the community in helping us sort out these issues:
Requirements:
1. Polling interface status for certain interfaces on Alcatel 7450 Switches.
2. Polling interface status for certain interfaces aggregates on a number of Solaris boxes.
We would like to receive alerts when a specific interface would go from up/up to up/down and vice versa. The document I followed to configure this is docs/DOC-2494
Problems faced with requirement 1 above ( Polling interface status for certain interfaces on Alcatel Switch RTEMR0000001TS)
1. On the Alcatel 7450 switch, for an interface 1/2/23, that is marked to be monitored with 'monitored=true', the status of the interface does not seem to get updated, neither is an alert raised when the ifOperStatus goes from down to up and vice versa. The 'Interfaces' section of Zenoss also continues to show (for example) 'Up/Down', when actually the interface is admin up, and oper up, and thus should be Up/Up. A manual snmpwalk on oid 1.3.6.1.2.1.2.2.1.8 returns values, an snmpget on sub oid`s returns values as well. We are using snmpv3 with authPriv for polling. Polling interval is set for 300 seconds.
snmpwalk:
# snmpwalk -v 3 -l authPriv -a SHA -A xxxxxx -x DES -X xxxxxxx -u SNMP 192.168.16.129 1.3.6.1.2.1.2.2.1.8 | head -n50
IF-MIB::ifOperStatus.1 = INTEGER: up(1)
IF-MIB::ifOperStatus.2 = INTEGER: up(1)
IF-MIB::ifOperStatus.3 = INTEGER: up(1)
IF-MIB::ifOperStatus.4 = INTEGER: up(1)
IF-MIB::ifOperStatus.5 = INTEGER: lowerLayerDown(7)
IF-MIB::ifOperStatus.6 = INTEGER: up(1)
IF-MIB::ifOperStatus.35684352 = INTEGER: up(1)
IF-MIB::ifOperStatus.35717120 = INTEGER: down(2)
IF-MIB::ifOperStatus.35749888 = INTEGER: up(1)
IF-MIB::ifOperStatus.35782656 = INTEGER: up(1)
IF-MIB::ifOperStatus.35815424 = INTEGER: up(1)
IF-MIB::ifOperStatus.35848192 = INTEGER: up(1)
IF-MIB::ifOperStatus.35880960 = INTEGER: up(1)
IF-MIB::ifOperStatus.35913728 = INTEGER: up(1)
IF-MIB::ifOperStatus.35946496 = INTEGER: down(2)
IF-MIB::ifOperStatus.35979264 = INTEGER: down(2)
IF-MIB::ifOperStatus.36012032 = INTEGER: down(2)
IF-MIB::ifOperStatus.36044800 = INTEGER: up(1)
IF-MIB::ifOperStatus.36077568 = INTEGER: up(1)
IF-MIB::ifOperStatus.36110336 = INTEGER: down(2)
#snmpget -v 3 -l authPriv -a SHA -A xxxxx -x DES -X xxxxx -u SNMP 192.168.16.129 1.3.6.1.2.1.2.2.1.8|head -n50
IF-MIB::ifOperStatus = No Such Instance currently exists at this OID
(I am assuming that Zenoss would take care of getting individual values as per below)
#snmpget -v 3 -l authPriv -a SHA -A xxxxx -x DES -X xxxxx -u SNMP 192.168.16.129 1.3.6.1.2.1.2.2.1.8.1|head -n50
IF-MIB::ifOperStatus.1 = INTEGER: up(1)
#snmpget -v 3 -l authPriv -a SHA -A xxxxx -x DES -X xxxxx -u SNMP 192.168.16.129 1.3.6.1.2.1.2.2.1.8.2|head -n50
IF-MIB::ifOperStatus.2 = INTEGER: up(1)
> When I re-model the device, the interface status changes to Up/Up, however, we would like the interface status for 1/2/23 in the 'Interfaces' tab to change to Up/Up and generate an alert. I have also tried deleting/re-adding the device.
As an aside, when looking at zenpersnmp logs, we see regular 'oid 1.3.6.1.2.1.2.2.1.8 is bad' errors for the switch.
2012-05-17 14:32:40,290 WARNING zen.zenperfsnmp: Error reading value for "ifOperStatus" on 192.168.16.129 (oid .1.3.6.1.2.1.2.2.1.8 is bad)
2012-05-17 14:32:40,291 WARNING zen.zenperfsnmp: Error reading value for "ifOutErrors" on 192.168.16.129 (oid .1.3.6.1.2.1.2.2.1.20 is bad)
2012-05-17 14:32:40,291 WARNING zen.zenperfsnmp: Error reading value for "ifOutUcastPackets" on 192.168.16.129 (oid .1.3.6.1.2.1.2.2.1.17 is bad)
2012-05-17 14:32:40,292 WARNING zen.zenperfsnmp: Error reading value for "ifOutOctets" on 192.168.16.129 (oid .1.3.6.1.2.1.2.2.1.16 is bad)
2012-05-17 14:32:40,292 WARNING zen.zenperfsnmp: Error reading value for "ifInErrors" on 192.168.16.129 (oid .1.3.6.1.2.1.2.2.1.14 is bad)
2012-05-17 14:32:40,292 WARNING zen.zenperfsnmp: Error reading value for "ifInUcastPackets" on 192.168.16.129 (oid .1.3.6.1.2.1.2.2.1.11 is bad)
2012-05-17 14:32:40,292 WARNING zen.zenperfsnmp: Error reading value for "ifInOctets" on 192.168.16.129 (oid .1.3.6.1.2.1.2.2.1.10 is bad)
Not sure what is going on here, since the throughput graphs (that depend on ifInOctets and ifOutOctets) seem to be generating just fine (as shown in the screenshots).
Problems faced with requirement 2 above (Polling interface status for certain interfaces aggregates shows up as 'Unknown' on a number of Solaris boxes.):
> All aggregates on the solaris box seem to show up as Up/Unknown although the admin status as well as oper status is both 'Up'. snmpwalk/snmpget (as above) seems to return valid and correct values. I have tried deleting/re-adding/remodelling the device, no luck. We see constant 'oid is bad' errors for this device as well, although the graphs seem to generate just fine.
> What could the cause of this be? Why does Zenoss show the interface as Unknown status when actually it is 'Up'? As an aside, when i deleted and re-added the device, the interfaces showed up as Up/Up for a short while, after which they went into 'Up/Unknown' status, thus trigerring the ifOperStatus warning (not even these alarms get generated in point 1 above).
Also, how could I go about creating an event transform (or other) that would suppress alerts when the interface is in 'Unknown' status and only generate an event when it is in 'Down' status?
Guys, any help would be greatly appreciated, i am standing by to provide any further logs and answer any queries.
- emr1ts ethernetcsmacd.jpg (153.8 K)
- emr1ts interfaces.jpg (243.2 K)
- emr1ts config properties.png (78.1 K)
-
Like (0)