- play_arrow Overview
- play_arrow Configuring Switching Control Board Redundancy
- play_arrow Configuring Bidirectional Forwarding Detection (BFD)
- play_arrow Configuring Routing Engine Redundancy
- play_arrow Configuring Load Balancing
- play_arrow Configuring Graceful Routing Engine Switchover (GRES)
- play_arrow Configuring Ethernet Ring Protection Switching
- play_arrow Configuring Nonstop Bridging
- play_arrow Configuring Nonstop Active Routing (NSR)
- play_arrow Configuring Graceful Restart
- play_arrow Configuring Virtual Router Redundancy Protocol (VRRP)
- play_arrow Performing Unified In-Service Software Upgrade (ISSU)
- play_arrow Performing Nonstop Software Upgrade (NSSU)
- play_arrow Multinode High Availability
- Multinode High Availability
- Prepare Your Environment for Multinode High Availability Deployment
- Multinode High Availability Services
- IPsec VPN Support in Multinode High Availability
- Asymmetric Traffic Flow Support in Multinode High Availability
- Example: Configure Multinode High Availability in a Layer 3 Network
- Example: Configure Multinode High Availability in a Default Gateway Deployment
- Example: Configure Multinode High Availability in a Hybrid Deployment
- Example: Configure IPSec VPN in Active-Active Multinode High Availability in a Layer 3 Network
- Software Upgrade in Multinode High Availability
- Insert Additional SRX5K-SPC3 in a Multinode High Availability Setup
- Multinode High Availability Support for vSRX Virtual Firewall Instances
- Multinode High Availability in AWS Deployments
- Multinode High Availability in Azure Cloud
- Multinode High Availability in Google Cloud Platform
- Multinode High Availability Monitoring Options
- play_arrow Administration
- Upgrading Software on an EX6200 or EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI Procedure)
- Upgrading Software on an EX8200 Virtual Chassis Using Nonstop Software Upgrade (CLI Procedure)
- Upgrading Software Using Nonstop Software Upgrade on EX Series Virtual Chassis and Mixed Virtual Chassis (CLI Procedure)
- play_arrow Verification Tasks
- play_arrow Troubleshooting
- play_arrow Knowledge Base
Configuring Power Management
Follow the steps below to configure power management on your switch.
Configuring the Power Priority of Line Cards (CLI Procedure)
The power management facility on EX6200 and EX8200 switches allows you to assign power priorities to the slots occupied by line cards. Power management provides power to the slots in priority order, which means that line cards in higher priority slots are more likely to receive power than line cards in lower priority slots if power to the switch is insufficient to power all the line cards.
The power priority you assign to a PoE line card affects both the order in which it receives base power and the order in which it receives PoE power. Base power is allocated first to all line cards in priority order. PoE power is then allocated to the PoE line cards in priority order.
When assigning power priority to slots, keep these points in mind:
0 is the highest priority. The number of priority levels depends on the number of slots in a switch—for example, for an EX8208 switch, which has eight slots, you can assign a priority of 0 through 7 to a slot.
All slots are assigned the lowest priority by default.
If a group of slots shares the same assigned priority, each slot’s power priority within the group is based on its slot number, with the lowest-numbered slots receiving power first. For example, if slot 3 and slot 7 each have an assigned power priority of 2, slot 3 has the higher power priority.
On EX6200 switches, slots containing a Switch Fabric and Routing Engine (SRE) module are automatically assigned the highest priority. If you assign a priority of 0 to a slot that has a lower number than a slot an SRE module is in, the slot with an SRE module still receives power first. You cannot change the power priority of slot containing an SRE module.
To assign or change the power priority for a slot:
[edit chassis] user@switch# set fpc slot power-budget-priority priority
For example, to set slot 6 to priority 0, enter:
[edit chassis] user@switch# set fpc 6 power-budget-priority 0
See Also
Configuring Power Supply Redundancy (CLI Procedure)
By default, the power management feature in EX Series switches is configured to manage the power supplies for N+1 redundancy, in which one power supply is held in reserve for backup if any one of the other power supplies is removed or fails.
You can configure power management to manage the power supplies for N+N redundancy. For example, to set up your AC power supplies for dual power feed, N+N redundancy is required. In N+N redundancy, power management allocates half of the online power supplies to normal operating power and half to redundant power. If you have an odd number of online power supplies, power management allocates one more power supply to normal operating power than to redundant power.
This topic describes how to configure power management for N+N redundancy and how to revert back to N+1 redundancy if your deployment needs change.
Before you configure power management for N+N redundancy, ensure that you have
sufficient power supplies to meet the power requirements of an N+N configuration. Use the show chassis power-budget-statistics
command to display your current power budget.
To allow more power to be available to line cards in an EX8200 switch, power management compensates for the reduced normal operating power in an N+N configuration by allocating less power to the chassis than it does in an N+1 configuration. For the EX8208 switch, the power allocated to the chassis is reduced to 1200 W from 1600 W. For the EX8216 switch, it is reduced to 1800 W from 2400 W. In determining whether you have enough power for an N+N configuration, take this reduction of allocated chassis power into account.
The reduction in allocated chassis power is achieved by reducing the maximum fan speed to 60 percent in an N+N configuration from 80 percent in an N+1 configuration. Because the maximum fan speed is reduced, it is possible that a line card that overheats would be shut down sooner in an N+N configuration than in an N+1 configuration.
On EX6200 switches, the same amount of power is allocated for the chassis in N+N configurations as in N+1 configurations.
To configure N+N redundancy:
[edit chassis]user@switch# set psu redundancy n-plus-n
To revert back to N+1 redundancy:
[edit chassis]user@switch# delete chassis psu redundancy n-plus-n