Welcome, Guest. Please login or register.

Author Topic: One of my WS-C4510R-E doesn't use the same temperature OID as the others  (Read 5293 times)

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Has anyone ever seen this issue?  NeDi identifies all of my WS-C4510R-E's as 1.3.6.1.4.1.9.1.877.def, as it should.  But one of them does not report its temperature on 1.3.6.1.4.1.9.9.13.1.3.1.3.1, but rather on 1.3.6.1.4.1.9.9.13.1.3.1.3.41.

Must be a Cisco issue of some sort, but can I tell NeDi for the same class of device to use a different sysobj?

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
I just noticed that my old nedi 1.0 installation is graphing the 4510R-E that is reporting temperature just fine.  But on my new 1.0.8 RC install it isn't.  Yet the one switch definitely isn't reporting with snmpget.

snmpget -v2c -c <community> <ip> 1.3.6.1.4.1.9.9.13.1.3.1.3.1

gives me "SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.1 = No Such Instance currently exists at this OID", whereas 1.3.6.1.4.1.9.9.13.1.3.1.3.1 gives me the temp number.

I'm completely confused.  How do I see what sysobj nedi 1.0 is using for a device?

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Oops, I meant that on the one 4510R-E that it reports temp on 1.3.6.1.4.1.9.9.13.1.3.1.3.41

Al

  • Guest
We have four 4500's with two supervisors, one of them has failed over to the second supervisor and the OID's are different and hence nagios / nedi etc no longer monitor the temp. If you have two sups, that could be your answer.

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Thanks for the response, but in this case it doesn't have two supervisors.  But I guess I'm confusing the matter.

I know now that the real problem is that my nedi 1.0 installation is graphing a devices' temperature that nedi 1.0.8 RC can't, despite the fact that both installations are using the same sysobj (and temp OID).  So the actual OID of a 4510 of mine uses OID 1.3.6.1.4.1.9.9.13.1.3.1.3.41 and snmpget fails entirely on 1.3.6.1.4.1.9.9.13.1.3.1.3.1, but nedi 1.0 graphs the temperature anyway and nedi 1.0.8 can't.  How is nedi 1.0 graphing temperature if the sysobj temp OID doesn't match the actual OID?  My 6509e is in the same situation.  Nedi 1.0 graphs the temperature for it but nedi 1.0.8 doesn't though they are using the same sysobj file and nedi 1.0.8 doesn't graph it because its temperature OID doesn't match its sysobj.  Since I only have one 6509 I just changed the temperature OID in the sysobj and that fixed my temperature graph for 1.0.8.

I'm baffled.  How did nedi get temperature by ignoring the sysobj, and if the behavior was supposed to change somewhere before 1.0.8 and it now must use the sysobj temperature OID, how would I allow for multiple devices that identify themselves as the same enterprises value (SNMPv2-SMI::enterprises.9.1.877) but use different OIDs for the same stat?

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2786
    • View Profile
    • NeDi
What do you get back from those devices, when walking 1.3.6.1.4.1.9.9.13.1.3.1.3?
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Here is a 4510 followed by the problem 4510:

This 4510R-E has:

WS-X45-SUP6-E supervisor
WS-X4648-RJ45V+E line cards

snmpwalk -v2c -c <community> <ip of 4510> 1.3.6.1.4.1.9.9.13.1.3.1.3
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.1 = Gauge32: 26
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.2 = Gauge32: 35
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.11 = Gauge32: 26
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.12 = Gauge32: 36
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.21 = Gauge32: 26
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.22 = Gauge32: 33
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.31 = Gauge32: 25
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.32 = Gauge32: 32
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.41 = Gauge32: 33
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.42 = Gauge32: 39
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.61 = Gauge32: 25
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.62 = Gauge32: 31

The problem 4510R-E has:

WS-X45-SUP6-E supervisor
WS-X4548-GB-RJ45V (non-enhanced) line cards

snmpwalk -v2c -c <community> <ip_of_problem_4510> 1.3.6.1.4.1.9.9.13.1.3.1.3
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.41 = Gauge32: 40
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.42 = Gauge32: 44


And here's my 6509:

snmpwalk -v2c -c <community> <ip_of_6509> 1.3.6.1.4.1.9.9.13.1.3.1.3
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.40010 = Gauge32: 39
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.40020 = Gauge32: 35
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.40030 = Gauge32: 39
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60010 = Gauge32: 26
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60011 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60020 = Gauge32: 44
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60021 = Gauge32: 25
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60040 = Gauge32: 33
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60041 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60050 = Gauge32: 27
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60051 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60052 = Gauge32: 31
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60053 = Gauge32: 31
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60054 = Gauge32: 23
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60055 = Gauge32: 23
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60056 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60057 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60058 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60059 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60060 = Gauge32: 27
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60061 = Gauge32: 23
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60062 = Gauge32: 30
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60063 = Gauge32: 29
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60064 = Gauge32: 23
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60065 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60066 = Gauge32: 23
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60067 = Gauge32: 23
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60068 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60069 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60070 = Gauge32: 23
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60071 = Gauge32: 23
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60080 = Gauge32: 30
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60081 = Gauge32: 22
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60090 = Gauge32: 32
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.60091 = Gauge32: 21
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.90050 = Gauge32: 32
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.90051 = Gauge32: 24
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.90060 = Gauge32: 32
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.90061 = Gauge32: 23
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.100050 = Gauge32: 25
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.100051 = Gauge32: 26
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.100060 = Gauge32: 25
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.100061 = Gauge32: 25

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2786
    • View Profile
    • NeDi
Well, it's nice to have the choice, but it's also a curse :) Always using the one ending with 41 is not an alternative?

I guess an inlet sensor (hopefully always in the same spot) makes the most sense. Easier said than done, especially on stacked devices and probably chassis...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Yes I guess it is an option to use 1.3.6.1.4.1.9.9.13.1.3.1.3.41 for all my 4510s.  I guess I was confused by how nedi 1.0 was ignoring the temperature OID and I got tunnel vision.  I missed the obvious solution.  :)  Using that OID for all my 4510 is a fine solution and I did it.  I suspect that perhaps this is an obscure problem due to the fact that there are old-style blades in a new chassis perhaps.  Anyway, it works for me.

But I'm still puzzled by how nedi 1.0 was ignoring the temp OID and graphing switches that use temp OIDs that differed from what was in their sysobj files.  Is that possible or do I have gremlins in my datacenter?  :)