Welcome, Guest. Please login or register.

Author Topic: CISCO-POWER-EXT MIB  (Read 3060 times)

misch

  • Guest
CISCO-POWER-EXT MIB
« on: March 13, 2012, 08:46:03 PM »
Hi,

we have Cisco 4503-E switches. They provide a MIB called CISCO-POWER-EXT-MIB. (ciscoMgmt.402). The interfaces in that MIB are double indexed:
1) the module
2) a counting index (1...) depending on the attached device.

So a walk would be for instance:
power.2.1 for the power consumption of the first device attached to module 2. The port is available through an index that points to the physEntIndex (i.e. 2001 for Gi2/1) in my case.

Is it possible to extend nedi to get this double indexing and the device via the entity index?

Greetings,

Michael.   

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2785
    • View Profile
    • NeDi
Re: CISCO-POWER-EXT MIB
« Reply #1 on: March 13, 2012, 10:21:51 PM »
Can you check if the stack mib can be used? I remember a similar case, where I found the answer there...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

misch

  • Guest
Re: CISCO-POWER-EXT MIB
« Reply #2 on: March 14, 2012, 08:55:29 AM »
No. The switch does not provide the STACK MIB.

Could you plese send me your mail address to misch@schwartzkopff.org. I need to contact you off-list. Perhaps you read my mail from yesterday. Thanks.

misch

  • Guest
Re: CISCO-POWER-EXT MIB
« Reply #3 on: March 20, 2012, 11:37:58 AM »
Hi,

you get the power consumtion per port in
CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPwrConsumption.2.1 = Gauge32: 8367 milliwatts
CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPwrConsumption.2.2 = Gauge32: 0 milliwatts
CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPwrConsumption.2.3 = Gauge32: 0 milliwatts
(...)

The first index ("2") gives the number is the hint to the module or PSE device. Of course there could be multiple.
The second index ("1", ...) tells you about the port number on that specific device.

The physical infex of the interface within a PSE you find via the cpeExtPsePortEntPhyIndex. In my case it reads like:
CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortEntPhyIndex.2.1 = INTEGER: 2001
CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortEntPhyIndex.2.2 = INTEGER: 2002
CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortEntPhyIndex.2.3 = INTEGER: 2003
(...)

Walking along the entPhysicalTable you finally find the interface name:
ENTITY-MIB::entPhysicalName.2001 = STRING: GigabitEthernet2/1
ENTITY-MIB::entPhysicalName.2002 = STRING: GigabitEthernet2/2
ENTITY-MIB::entPhysicalName.2003 = STRING: GigabitEthernet2/3
(...)

Greetings,

Michael.

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2785
    • View Profile
    • NeDi
Re: CISCO-POWER-EXT MIB
« Reply #4 on: March 20, 2012, 10:26:47 PM »
Just to make sure, this OID doesn't yield any results? 1.3.6.1.4.1.9.5.1.4.1.1.11
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

misch

  • Guest
Re: CISCO-POWER-EXT MIB
« Reply #5 on: March 21, 2012, 09:35:10 AM »
The whole tree 1.3.6.1.4.1.9.5 does not exist.

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2785
    • View Profile
    • NeDi
Re: CISCO-POWER-EXT MIB
« Reply #6 on: March 21, 2012, 10:28:36 PM »
(moved to discovery)
Ok, I could add a routine, which constructs the proper index.
« Last Edit: March 21, 2012, 10:45:49 PM by rickli »
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

misch

  • Guest
Re: CISCO-POWER-EXT MIB
« Reply #7 on: March 22, 2012, 06:08:21 AM »
Thanks. Would be cool.

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2785
    • View Profile
    • NeDi
Re: CISCO-POWER-EXT MIB
« Reply #8 on: April 28, 2012, 10:35:02 PM »
I actually found the time to actually do this, but have you tried using the numeric OID for CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortEntPhyIndex in IFpwix?

Either way, I've added a shortcut, which allows a number like 1000 for IFpwix. This will multiple the 2 with 1000 and add the last index. Should work as long as this relationship is consistent. The beauty of it, one less walk which saves time and resources...
« Last Edit: April 28, 2012, 10:57:40 PM by rickli »
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo