Support Support Downloads Knowledge Base Service Request Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EX] PoE stops working after Junos OS upgrade or during normal operations on EX2300/EX3400

0

0

Article ID: KB35188 KB Last Updated: 31 Oct 2019Version: 1.0
Summary:

On EX2300/3400 Series switches, Power over Ethernet (PoE) might stop working after a Junos OS upgrade or even during a stable operation.

This article gives a possible reason for the PoE to stop working and describes what must be done to resolve the issue.

Symptoms:

The following symptoms may be seen:

  1. The show poe controller output reports an alarm with the message that a new PoE firmware is available with an asterisk (*) in the index column.
root@KB> show poe controller

Controller  Maximum   Power         Guard   Management   Status      Lldp
index       power     consumption   band                             Priority
   0**      1440W     704.60W       0W      Class        AT_MODE     Disabled
   1**      1440W     227.00W       0W      Class        AT_MODE     Disabled
   2**      1440W     704.60W       0W      Class        AT_MODE     Disabled
   3**      1440W     704.60W       0W      Class        AT_MODE     Disabled
   4**      1440W     0.00W         0W      Class        AT_MODE     Disabled

  **New PoE software upgrade available.
Use 'request system firmware upgrade poe fpc-slot <slot>'
This procedure will take around 10 minutes (recommended to be performed during maintenance)
  1. The show chassis firmware detail output may show one of the following statuses for the PoE firmware. 

root@KB show chassis firmware detail

FPC 0                    
   Boot Firmware                              >>>>>>>>> Blank
      U-Boot               U-Boot 2016.01-rc1 (Sep 01 2016 - 16:00:13 -0700)  1.3.0
      loader                       FreeBSD/armv6 U-Boot loader 1.2
FPC 1                    
   PoE firmware            0.0.0.0.0          >>>>>> No version displayed
   Boot Firmware         
      U-Boot               U-Boot 2016.01-rc1 (Sep 01 2016 - 16:00:13 -0700)  1.3.0
      loader                       FreeBSD/armv6 U-Boot loader 1.2
FPC 2                    
   PoE firmware            0.0.0.0.0      >>>>>> No version displayed
   Boot Firmware         
      U-Boot               U-Boot 2016.01-rc1 (Sep 01 2016 - 16:00:13 -0700)  1.3.0
      loader                       FreeBSD/armv6 U-Boot loader 1.2
FPC 3                    
   Boot Firmware          1.6.1.21.1          >>>>>> Old PoE Version
      U-Boot               U-Boot 2016.01-rc1 (Sep 01 2016 - 16:00:13 -0700)  1.3.0
      loader                       FreeBSD/armv6 U-Boot loader 1.2
FPC 4                    
   PoE firmware            2.1.1.19.3      >>>>>> Only FPC4 has the new version.
   Boot Firmware         
      U-Boot               U-Boot 2016.01-rc1 (Sep 01 2016 - 16:00:13 -0700)  1.3.0
      loader                       FreeBSD/armv6 U-Boot loader 1.2
  1. The output of show poe interface might show “Power consumption” as 0.00W. 

root@KB> show poe controller

Controller  Maximum   Power         Guard    Management   Status        Lldp
index       power     consumption   band                                Priority
0           1440W     0.00W         0W       Class        AT_MODE       Disabled
1           1440W     0.00W         0W       Class        AT_MODE       Disabled
  1. The output of show poe interface might show that the FPC interfaces are drawing more power than the maximum specified. 

ge-1/0/24    Enabled      ON     15.4W      Low            45.6W*          0
ge-1/0/25    Enabled     OFF     15.4W      Low            21.8W*         not-applicable
ge-1/0/26    Enabled     OFF     15.4W      Low            37.4W*         not-applicable
ge-1/0/29    Enabled     OFF     15.4W      Low            42.6W*         not-applicable
ge-1/0/35    Enabled     OFF     15.4W      Low            45.6W*         not-applicable
ge-1/0/36    Enabled     OFF     15.4W      Low            21.8W*         not-applicable
ge-1/0/37    Enabled     OFF     15.4W      Low            37.4W*         not-applicable
ge-1/0/40    Enabled     OFF     15.4W      Low            42.6W*         not-applicable
ge-1/0/46    Enabled     OFF     15.4W      Low            45.6W*         not-applicable
ge-1/0/47    Enabled     OFF     15.4W      Low            21.8W*         not-applicable

‚Äč* Powered device is drawing more power than maximum power allowed on the port.

show poe controller

Controller  Maximum   Power         Guard    Management   Status        Lldp
index       power     consumption   band                                Priority
   0**      1440W     704.60W       0W       Class        AT_MODE       Disabled
   1**      1440W     227.00W       0W       Class        AT_MODE       Disabled
   2**      1440W     704.60W       0W       Class        AT_MODE       Disabled
   3**      1440W     704.60W       0W       Class        AT_MODE       Disabled
   4**      1440W     0.00W         0W       Class        AT_MODE       Disabled

**New PoE software upgrade available.
Use 'request system firmware upgrade poe fpc-slot <slot>'
This procedure will take around 10 minutes (recommended to be performed during maintenance)

 
Cause:

The PoE firmware is corrupted or a PoE software upgrade is required.

Solution:

Perform the following steps to recover from PoE failure:

  1. Power cycle the affected FPC (re-seat the power cord). Do not perform a soft reboot. 
  2. After the FPC joins the VC or the standalone device reboots, execute one of the following commands in operational mode:

  • request system firmware upgrade poe fpc-slot <slot>

OR

  • request system firmware upgrade poe fpc-slot 1 file /usr/libdata/poe_latest.s19.
 

Note: You need to change the fpc-slot number accordingly. Also, it is recommended that you push the PoE code one by one instead of adding all members in the virtual-chassis setup.

  1. After the above command is executed, the FPC should automatically reboot. If not, reboot from the Command Line Interface.
  2. After the FPC is online, check the PoE version with the show chassis firmware detail command. The PoE version should be the latest version (2.1.1.19.3) after the above steps are completed. 

  3. If the version is correct, the PoE devices should work.

  4. Repeat the above steps to upgrade the PoE versions on other FPCs in the virtual-chassis setup.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Security Alerts and Vulnerabilities

Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search