Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature : Use IOS POE code for IOSXE #8853
We match "iosxe" OS as well for POE polling on cisco devices, as they are using the same MIBs.
DO NOT DELETE THIS TEXT
If you would like to test this pull request then please run:
I don't have the necessary device unfortunately. I saw @boudreau comment on the previous PR #8705, which says that the Cisco code is not triggered with his 3850. As the MIBs is exactly the same for both families, I changed the condition to at least get in the Cisco part of the POE code (the generic code does not provide any useful value on Cisco devices anyway so it can't be worse than it is now).
I managed to get hands on a 3850 with POE enabled. And it does not answer to a required MIB :
Without this, there is no way to bind a "POE entry" from snmpwalk_cache_oid($device, 'cpeExtPsePortEntry', array(), 'CISCO-POWER-ETHERNET-EXT-MIB'); to the ifIndex of the interface.
Basically, the POE data is there but is not bound to the interface.
So unless Cisco corrects this, the 3850 will never have POE data displayed. The IOSXE code may still be usable by other IOSXE devices which would properly answer portIfIndex oid.
Hi, thanks for the response.
On the Cisco3850, in look like the cpeExtPsePortEntPhyIndex uses the same index as the entPhysicalDescr.
Thanks for the efforts.
It is actually, but there is no relation to ifIndex available for this. Parsing the Interface name would be ugly ... I hoped we could find something better. But it is clearly possible. *ifIndex *to *ifName *to *entPhysicalDescr* to ".4.1" 2018-07-09 19:50 GMT+02:00 boudreau <email@example.com>:…
Hi, thanks for the response. On the Cisco3850, in look like the cpeExtPsePortEntPhyIndex uses the same index as the entPhysicalDescr. Could that be used to map the interfaces to the index and then use that index to poll the POE: ENTITY-MIB::entPhysicalDescr.4022 = STRING: GigabitEthernet4/0/1 ^^^^ CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortEntPhyIndex.4.1 = INTEGER: 4022 ^^^^ CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortEnable.4.1 = INTEGER: auto(1) CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortDiscoverMode.4.1 = INTEGER: ieeeAndCisco(5) CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortDeviceDetected.4.1 = INTEGER: false(2) CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortIeeePd.4.1 = INTEGER: false(2) CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortAdditionalStatus.4.1 = BITS: 00 CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPwrMax.4.1 = Gauge32: 30000 milliwatts CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPwrAllocated.4.1 = Gauge32: 0 milliwatts CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPwrAvailable.4.1 = Gauge32: 0 milliwatts CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPwrConsumption.4.1 = Gauge32: 0 milliwatts CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortMaxPwrDrawn.4.1 = Gauge32: 0 milliwatts CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortEntPhyIndex.4.1 = INTEGER: 4022 CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPolicingCapable.4.1 = INTEGER: true(1) CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPolicingEnable.4.1 = INTEGER: off(2) CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPolicingAction.4.1 = INTEGER: deny(1) CISCO-POWER-ETHERNET-EXT-MIB::cpeExtPsePortPwrManAlloc.4.1 = Gauge32: 15400 milliwatts Thanks for the efforts. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8853 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aklhn6haJZhZUplu-xUlInb_irOw6rxCks5uE5fLgaJpZM4U8rGV> .
-- -- Philippe Teissier