I assume you can get other OID's from this device without a problem?
What you must understand is that there is an OID and an instance. To obtain the instance(s) you should walk the OID.
So under 184.108.40.206.220.127.116.11.18.104.22.168.1.8 you may find that there are 4 instances for your card. I make up something here to paint you the picture:
These 4 entries are then for you to collect to have the uptime of each card.
Now if the device says 22.214.171.124.126.96.36.199.188.8.131.52.1.8 does not exist when you try to do a snmpwalk, it could be a number of things.
A SNMP view on the device could block at part of the MIB.( Chec kconfig e.g. exclude cisco 184.108.40.206.4.1.9.)
There could be a problem with the device agent (on device console try debug snmp [packets|event|all]. Compare with other devices )
And last but not least, cisco has (like other vendors) the habit of implementing mibs partialy :-| It is possible that a documented OID simply does not work (yet). (sometimes the releasenotes shed some light on this)
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...