Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

S-Series with "pethPsePortMan" errors and PoE failure

« Go Back

Information

 
TitleS-Series with "pethPsePortMan" errors and PoE failure
Symptoms
  • Power over Ethernet (PoE) is not working on the NEM's ports.
  • Error log ('show support') contains one or more instances of "pethPsePortMan" messaging; for example:
<3>PEM[2.SNMPSubAgt]pethPsePortMan::pethPsePortPowerPairsControlAbilityGet(): PoEDriver::PoEGetPortPairsControlAbility(372) failed
<3>PEM[2.SNMPSubAgt]pethPsePortMan::pethPsePortPowerPriorityGet(): PoEDriver::PoEGetPortPowerPriority(383) failed
<3>PEM[2.SNMPSubAgt]pethPsePortMan::pethPsePortPowerPairsGet(): PoEDriver::PoEGetPortPowerPairs(383) failed
<3>PEM[2.SNMPSubAgt]pethPsePortMan::pethPsePortAdminEnableGet(): PoEDriver::PoEGetPortAdminEnable(383) failed


 
Environment
  • S-Series
  • All firmware
Cause
Given that module slots are identified in messages as "[<slot>.<task>]", these sample messages are in reference to hardware installed in slot 2. This issue affects one or more of the NEMs installed in that slot's base module.
Resolution
  • Ensure that the PoE power header (looks like four parallel pins) is installed so that the NEM's RJ45 ports can physically receive PoE power.
  • See the "S-Series Option Module Quick Reference" guide, for more about the power header.
  • Contact the GTAC for assistance, as necessary.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255