cisco SNMP locIfLoad problem

[Philippe]

Hello,

i want to view the load of my cisco layer 3 switches in a GRAPH.
So, i have the host SWITCH with some keys:


shortname ==> BD_3550:locIfLoad

DESCRIPTION: locIfLoad -connectie naar WD-
HOST: BD_3550
TYPE: SNMPv2 agent
SNMP OID: 1.3.6.1.4.1.9.2.2.1.1.24.24 (this means locIfLoad and last .24 is
the port number)
SNMP PORT: 161
KEY: locIfLoad
UNITS:
MULTIPLIER: -
UPDATE INTERVAL: 30
KEEP HISTORY: 7
STATUS: MONITORED
TYPE OF INFORMATION: NUMERIC
STORE VALUE: AS IS

Now, this is not working.
When i check the latest values i get 1 and for change -


then another but the same:

shortname ==> BD_3550:locIfLoad

DESCRIPTION: locIfLoad -connectie naar CK-
HOST: BD_3550
TYPE: SNMPv2 agent
SNMP OID: 1.3.6.1.4.1.9.2.2.1.1.24.9 (this means locIfLoad and last .9 is
the port number)
SNMP PORT: 161
KEY: locIfLoad
UNITS:
MULTIPLIER: -
UPDATE INTERVAL: 30
KEEP HISTORY: 7
STATUS: MONITORED
TYPE OF INFORMATION: NUMERIC
STORE VALUE: AS IS

for this item, i have values and these values are correct when i compare them with the TXload on the interface of that switch on the moment when i copy by example some 100's of megabytes.
my values go with +20, +5, +9 or -16, -8, -7
So it works fine for this interface port and this is on the same LAYER 3 cisco switch of course.
the version of the switch is Version 12.2(25)SE.

So, the parameters are the same but i get no values for the first one.
any idea ?
grtz,
Philippe.

[Philippe]

hi,

i did an additional test.
From the zabbix server i perform:

zabbix:~# snmpget 10.50.10.1 -v 2c -c public oid 1.3.6.1.4.1.9.2.2.1.1.24.9
SNMPv2-MIB::snmpTrapOID = No Such Object available on this agent at this OID
SNMPv2-SMI::enterprises.9.2.2.1.1.24.9 = INTEGER: 13
zabbix:~#

So i get value 13, this is correct with the TXload value at that time on the switch.


On the other port i perform:

zabbix:~# snmpget 10.50.10.1 -v 2c -c public oid 1.3.6.1.4.1.9.2.2.1.1.24.24
SNMPv2-MIB::snmpTrapOID = No Such Object available on this agent at this OID
SNMPv2-SMI::enterprises.9.2.2.1.1.24.24 = INTEGER: 1
zabbix:~#



So, it means that snmp-get gets that value from the switch and that zabbix is working fine ???
So, is the switch giving the wrong value ? or is snmp in fault with something ?
It's strange that it works fine for one port but not for the other port and this really sucks!

grtz,
Philippe.

[Philippe]

yo, i found the problem

2 weeks ago i preformed an IOS upgrade and appearantly, the indexes on the switch do not match as before.
so, ethernet 0/24 is by example .18....
i got these information via SNMP walk.

grtz,
Philippe

[joe]

2 weeks ago i preformed an IOS upgrade and appearantly, the indexes on the switch do not match as before.
so, ethernet 0/24 is by example .18....
i got these information via SNMP walk.

grtz,
Philippe

Philippe,

This is common on Cisco devices. Here's a document for routers (IOS) concerning this problem. It also tells you how to enable ifIndex persistence. However, I'm not sure about IOS-based switches. I believe CatOS switches have persistence also, but I think it is only for physical interfaces (ie, not VLAN interfaces).

This is one of the reasons why MRTG (and others like it) allow you to base the "unique" identifier per port/interface off of something besides ifIndex.... like MAC address, IP, description, etc.

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dt5ifidx.htm

joe