PoE Stats on Cisco 3000 series switches do not match
Various versions of Cisco IOS on 3000 series of switches do not report their PoE statistics correctly and will not associate with the correct interfaces. TotalView may show interfaces drawing PoE power when they aren’t delivering power, or that an interface is not drawing power when in fact it is.
This is a Cisco bug in their PoE SNMP implementation and can be referenced by Cisco bug number CSCvc99866
This has been fixed in 16.3(3.33), 16.5(0.210), 16.6(0.72), Everest-16.5.1
Track a Bug - CSCvc99866
|
Alert Type: |
Updated * |
|
Bug Id: |
CSCvc99866 |
|
Title: |
inconsistent index mapping between cpeExtPsePortEntPhyIndex and entPhysicalName |
|
Status: |
Fixed |
|
Severity: |
3 Moderate |
|
Description: |
Symptom: When polling the cpeExtPsePortEntPhyIndex inside PowerEthernet MIB to obtain the index that corresponds to a given port number which will then needs to be mapped out with the data returned by the entPhysicalName to get the actual port type (TenGigabitEthernet , GigabitEthernet , etc ) it is noticed that there is an inconsistency between the indexes returned by cpeExtPsePortEntPhyIndex and the ones returned by entPhysicalName , indexes being missing Example 1: cpeExtPsePortEntPhyIndex.1.1 (EntPhysicalIndexOrZero) 1021 2: cpeExtPsePortEntPhyIndex.1.2 (EntPhysicalIndexOrZero) 1022 3: cpeExtPsePortEntPhyIndex.1.3 (EntPhysicalIndexOrZero) 1023 4: cpeExtPsePortEntPhyIndex.1.4 (EntPhysicalIndexOrZero) 1024 5: cpeExtPsePortEntPhyIndex.1.5 (EntPhysicalIndexOrZero) 1025 6: cpeExtPsePortEntPhyIndex.1.6 (EntPhysicalIndexOrZero) 1026 7: cpeExtPsePortEntPhyIndex.1.7 (EntPhysicalIndexOrZero) 1027 8: cpeExtPsePortEntPhyIndex.1.8 (EntPhysicalIndexOrZero) 1028 9: cpeExtPsePortEntPhyIndex.1.9 (EntPhysicalIndexOrZero) 1029 10: cpeExtPsePortEntPhyIndex.1.10 (EntPhysicalIndexOrZero) 1030 11: cpeExtPsePortEntPhyIndex.1.11 (EntPhysicalIndexOrZero) 1031 12: cpeExtPsePortEntPhyIndex.1.12 (EntPhysicalIndexOrZero) 1032 13: cpeExtPsePortEntPhyIndex.1.13 (EntPhysicalIndexOrZero) 1033 14: cpeExtPsePortEntPhyIndex.1.14 (EntPhysicalIndexOrZero) 1034 15: cpeExtPsePortEntPhyIndex.1.15 (EntPhysicalIndexOrZero) 1035 16: cpeExtPsePortEntPhyIndex.1.16 (EntPhysicalIndexOrZero) 1036 17: cpeExtPsePortEntPhyIndex.1.17 (EntPhysicalIndexOrZero) 1037 18: cpeExtPsePortEntPhyIndex.1.18 (EntPhysicalIndexOrZero) 1038 19: cpeExtPsePortEntPhyIndex.1.19 (EntPhysicalIndexOrZero) 1039 17: entPhysicalName.1015 (SnmpAdminString) Switch 1 - FAN 1 [53.77.69.74.63.68.20.31.20.2D.20.46.41.4E.20.31 (hex)] 18: entPhysicalName.1016 (SnmpAdminString) Switch 1 - FAN 2 [53.77.69.74.63.68.20.31.20.2D.20.46.41.4E.20.32 (hex)] 19: entPhysicalName.1017 (SnmpAdminString) Switch 1 - FAN 3 [53.77.69.74.63.68.20.31.20.2D.20.46.41.4E.20.33 (hex)] 20: entPhysicalName.1040 (SnmpAdminString) Switch 1 Fixed Module 0 [53.77.69.74.63.68.20.31.20.46.69.78.65.64.20.4D.6F.64.75.6C.65.20.30 (hex)] 21: entPhysicalName.1041 (SnmpAdminString) Gi1/0/1 [47.69.31.2F.30.2F.31 (hex)] 22: entPhysicalName.1042 (SnmpAdminString) Gi1/0/2 [47.69.31.2F.30.2F.32 (hex)] 23: entPhysicalName.1043 (SnmpAdminString) Gi1/0/3 [47.69.31.2F.30.2F.33 (hex)] 24: entPhysicalName.1044 (SnmpAdminString) Gi1/0/4 [47.69.31.2F.30.2F.34 (hex)] 25: entPhysicalName.1045 (SnmpAdminString) Gi1/0/5 [47.69.31.2F.30.2F.35 (hex)] 26: entPhysicalName.1046 (SnmpAdminString) Gi1/0/6 [47.69.31.2F.30.2F.36 (hex)] 27: entPhysicalName.1047 (SnmpAdminString) Gi1/0/7 [47.69.31.2F.30.2F.37 (hex)] 28: entPhysicalName.1048 (SnmpAdminString) Gi1/0/8 [47.69.31.2F.30.2F.38 (hex)] 29: entPhysicalName.1049 (SnmpAdminString) Gi1/0/9 [47.69.31.2F.30.2F.39 (hex)] 30: entPhysicalName.1050 (SnmpAdminString) Gi1/0/10 [47.69.31.2F.30.2F.31.30 (hex)] indexes 1021 to 1039 from the cpeExtPsePortEntPhyIndex are missing on the entPhysicalName table Conditions: Devices running codes 3.7.x and 16.x can show this behavior, issue is not seeing on 3.6.x Issue has been seeing on C3650 but could affect other platforms as long as they are running one of the two affected codes mentioned above Workaround:</<> |
|
Last Modified: |
02-MAY-2017 |
|
Known Affected Releases: |
n/a |
|
Known Fixed Releases: * |
16.3(3.33), 16.5(0.210), 16.6(0.72), Everest-16.5.1 |