- Preface
- Using the Command-Line Interface
- Using the Web Graphical User Interface
-
- Configuring Interface Characteristics
- Configuring Auto-MDIX
- Configuring Ethernet Management Port
- Configuring LLDP, LLDP-MED, and Wired Location Service
- Configuring System MTU
- Configuring Internal Power Supplies
- Configuring Stack Power
- Configuring the Cisco eXpandable Power System (XPS) 2200
- Configuring PoE
- Configuring EEE
-
- Configuring the Device for Access Point Discovery
- Configuring Data Encryption
- Configuring Retransmission Interval and Retry Count
- Configuring Adaptive Wireless Intrusion Prevention System
- Configuring Authentication for Access Points
- Converting Autonomous Access Points to Lightweight Mode
- Using Cisco Workgroup Bridges
- Configuring Probe Request Forwarding
- Optimizing RFID Tracking
- Configuring Country Codes
- Configuring Link Latency
- Configuring Power over Ethernet
-
- Preventing Unauthorized Access
- Controlling Switch Access with Passwords and Privilege Levels
- Configuring TACACS+
- Configuring RADIUS
- Configuring Kerberos
- Configuring Local Authentication and Authorization
- Configuring Secure Shell (SSH)
- Configuring Secure Socket Layer HTTP
- Configuring IPv4 ACLs
- Configuring IPv6 ACLs
- Configuring DHCP
- Configuring IP Source Guard
- Configuring Dynamic ARP Inspection
- Configuring IEEE 802.1x Port-Based Authentication
- Configuring Device Sensor
- Configuring MACsec Encryption
- Configuring Web-Based Authentication
- Configuring Port-Based Traffic Control
- Configuring IPv6 First Hop Security
- Configuring Cisco TrustSec
- Configuring Wireless Guest Access
- Managing Rogue Devices
- Classifying Rogue Access Points
- Configuring wIPS
- Configuring Intrusion Detection System
-
- Administering the System
- Performing Device Setup Configuration
- Configuring Right-To-Use Licenses
- Configuring Administrator Usernames and Passwords
- Configuring 802.11 parameters and Band Selection
- Configuring Aggressive Load Balancing
- Configuring Client Roaming
- Configuring Application Visibility and Control
- Configuring Voice and Video Parameters
- Configuring RFID Tag Tracking
- Configuring Location Settings
- Monitoring Flow Control
- Configuring SDM Templates
- Configuring System Message Logs
- Configuring Online Diagnostics
- Managing Configuration Files
- Configuration Replace and Configuration Rollback
- Working with the Flash File System
- Working with Cisco IOS XE Software Bundles
- Troubleshooting the Software Configuration
Configuring the Cisco eXpandable Power System (XPS) 2200
This module contains the following sections:
- Restrictions for Configuring the XPS 2200
- Information About Configuring the XPS 2200
- How to Configure the XPS 2200
- Monitoring and Maintaining the XPS 2200
- Additional References
Restrictions for Configuring the XPS 2200
When using the XPS power supplies in the RPS mode for backing up switch power supplies, the smallest power supply in the XPS must be greater than the largest power supply in a switch connected to an XPS port in RPS mode.
In RPS mode, each XPS power supply can back up one and only one switch power supply, regardless of the size.
If you remove a power supply from the power stack (from a switch or the XPS), be sure that removing it does not deplete available power enough to cause load shedding.
Information About Configuring the XPS 2200
Cisco eXpandable Power System (XPS) 2200 Overview
The Cisco eXpandable Power System (XPS) 2200 is a standalone power system that you can connect to Catalyst switches. The XPS 2200 can provide backup power to connected devices that experience a power supply failure or, in a Catalyst switch power stack, it can supply additional power to the power stack budget. The XPS 2200 power ports and internal power supplies can operate in redundant power supply (RPS) mode or stack power (SP) mode.
Stack-power mode is used only on stacking-capable switches in a power stack. With no XPS, a power stack operates in ring topology with a maximum of four switches in the stack. If you merge two stacks, the total number of switches cannot exceed four. When an XPS is in the power stack, you can connect up to nine switches in the stack plus the XPS, providing power budgets to power stack members similar to stack-power ring topology operation.
All Catalyst switches connected to an XPS on SP ports are part of the same power stack, and all power from the XPS and the switch is shared across all switches in the stack. Power sharing is the default mode, but the XPS supports the same stack power modes that are supported in a ring topology (strict and nonstrict power-sharing or redundant modes).
When two power supplies are present, the system can operate in mixed mode, where one power supply operates in RPS mode and the other in SP mode. You can configure the ports and power supplies for the way that you plan to use the XPS 2200.
The XPS 2000 has nine power ports that can operate in an RPS role or in an automatic stack power (Auto-SP) role (the default), where mode of operation is determined by the type of switch connected to the port . You can also use the CLI to force the mode to be RPS for stackable switches.
-
When a Catalyst switch running the LAN base image, or a Catalyst (nonstackable) switch is connected to the port, the mode is RPS, and the XPS 2200 acts as a backup if the switch power supply goes down.
-
When a Catalyst (stackable) switch running the IP base or IP services license is connected to the port, the mode is SP, which enables the switch to be part of the stack power system.
You configure the XPS through any switch connected to a power port. You can use any XPS port for configuration, and you can configure any port from any switch connected to the XPS. If you enter XPS configuration commands on more than one switch, the last configuration applied takes effect.
Although all XPS configuration is done through a switch, the XPS 2200 also runs its own software. You can upgrade this software through the XPS Service Port.
XPS 2200 Power Supply Modes
The XPS has two power supplies that can also be in either RPS or SP mode.
In SP mode, all SP ports on the XPS belong to the same power stack. When a power stack includes an XPS, the stack topology is a star topology and consists of up to nine member switches plus the XPS 2200. The XPS power supply or power supplies that are in SP mode are considered in the power budgeting. If both XPS power supplies are in RPS mode, the power stack consists only of the switches connected to XPS ports in SP mode, and the power budget is determined by the power supplies in these switches.
If there is a power supply role mismatch, for example, if an XPS port is configured for RPS and both power supplies are in SP mode, the XPS detects the mismatch, and an error message is sent.
RPS Mode
When both XPS power supplies are in RPS mode, the XPS can back up two power supply failures for switch power supplies of equal value or less. The smallest power supply in the XPS must be greater than the largest power supply in a switch connected to an XPS port in RPS mode.
If only one supply is in RPS mode, the XPS can back up only one power supply, even when the failed power supply is much smaller. For example, if an XPS 1100 W power supply is in RPS mode and two 350 W switch power supplies fail, the XPS can back up only one of the switch power supplies.
When one XPS power supply in RPS mode is backing up a switch power supply and another switch power supply fails, a message appears that the XPS backup is not available. When the failed power supply comes up, the XPS becomes available to back up other power supplies.
If the XPS is backing up two failed power supplies in a single switch (both XPS power supplies in RPS mode), the XPS is not available to back up other switch power supplies until both of the failed supplies are repaired or replaced.
In mixed mode, with one power supply in RPS mode and one in SP mode, if two power supplies in a single switch fail, because the XPS can back up only one of them, it denies power to both power supplies, and the switch shuts down. This occurs only in mixed power mode.
If a switch is connected to a port configured as RPS, but neither of the power supplies is RPS, the RPS port configuration is rejected and the XPS attempts to add the switch to a power stack. If the switch is not capable of operating in SP mode (is not a stackable switch), the port is disabled.
Ports in RPS mode have a configurable priority. The default priority is based on the XPS port number, with port 1 as the highest priority port. A higher priority port has a higher precedence for backup than a lower priority port. If a switch connected to a higher priority port has a power supply failure while a switch connected to a low priority port is being backed up, the XPS drops power to the low priority port to supply power to the high priority port.
Stack Power Mode
Stack-power mode is used only on Catalyst switches in a power stack. With no XPS, a power stack operates in ring topology with a maximum of four switches in the stack. When an XPS is in the power stack, you can connect up to nine switches in the stack plus the XPS, providing power budgets to power stack members similar to stack-power ring topology operation.
All Catalyst switches connected to an XPS on SP ports are part of the same power stack, and all power from the XPS and the switches is shared across all switches in the stack. Power sharing is the default mode, but the XPS supports the same stack power modes that are supported in a ring topology (strict and nonstrict power-sharing or redundant modes).
The XPS uses neighbor discovery to create the power stack. When it discovers a Catalyst switch on an unconfigured port, it marks the port as an SP port, and the switch joins the power stack. The XPS notifies the switch, begins the power-budgeting process, and assigns budgets to each switch in the power stack based on their requirements, priorities, current power allocations, and the stack aggregate power capability.
The XPS sends the power budget to each switch. If not enough input power is available to provide every switch with its maximum requested power, power is distributed based on priority. Switches with the highest priority receive required power first, followed by any powered devices that have already been allocated power, in order of their priority. Any remaining power is distributed equally through the stack.
The RPS port priority (1 through 9) does not affect stack power priority. Each switch participating in stack power has its own system priority and a high and low priority for devices connected to its ports. These priorities are used for stack power, as is the case in a ring topology. You configure stack power priority for the system and for high and low-priority ports by using the power-priority switch, power-priority high, and power-priority low commands in switch stack power configuration mode. If a system or set of powered devices are using the default priority, the XPS automatically assigns a priority (1 through 27), with lower MAC addresses receiving higher priorities.
There are four power stack modes: power sharing, strict power sharing, redundant, or strict redundant. You configure the power stack mode by using the mode {power-sharing | redundant} [strict] command in power-stack configuration mode. The power-sharing or redundant configurations affect the power budgeting aspect of the stack; strict or non-strict affects the actions of the PoE application when a budget reduction does not result in load shedding.
-
In power sharing modes (strict or nonstrict), the stack power budget is the cumulative capacity of all the power supplies in the stack (minus 30 W reserved power). This is the default.
-
In redundant modes (strict or nonstrict), the stack power budget is the total available power (minus 30 W) after the capacity of the largest power supply in the power stack is subtracted. Redundant mode guarantees that no switch or powered device loses power or experiences load sheds if a single power supply fails, but load sheds can occur if more than one power supply fails.
-
In strict modes, if a loss of input power results in reduced power budgets but does not result in any hardware load shedding, the XPS automatically begins denying power to low-priority powered devices and then the high-priority powered devices until the amount of allocated power is less than or equal to the amount of available PoE power.
-
In nonstrict modes, in the event of a power reduction, the amount of allocated power is allowed to fall under budget.
For example, a system with a total PoE budget (available power) of 400 W can allocate 390 W of the budget (allocated power) to powered devices. The allocated power of a device is the maximum amount of power that the device needs. The actual power consumption (consumed power) for a set of powered devices is usually not equal to the allocated power. In this example, the actual power might be approximately 200 W. If a power loss in the stack reduces the available power to 210 W, this amount is enough to sustain the power being consumed by the powered devices, but less than the worst-case allocated power, which would put the system under budget. In strict mode, the stack would immediately deny power to powered devices until the allocated power was 210 W or less. In nonstrict mode, no action is taken, and the state is allowed to persist. In nonstrict mode if the actual power consumption becomes more than 210 W, this triggers a load shed and can result in the loss of power to all powered devices or switches with the lowest priority level.
Mixed Modes
The XPS 2200 can also operate in mixed mode, where some ports connected to switches are RPS and others are SP. At least one power supply must be an RPS power supply in this configuration. The power supply in the XPS can back up only one switch power supply and the XPS supply must be greater than the largest power supply in a switch connected to an XPS port in RPS mode.
Switches connected to SP ports belong to a single power stack. If the SP switches have a large enough power budget, an SP power supply is not required on the XPS. When an XPS power supply is configured, its power is added to the power pool shared by the power stack.
XPS 2200 System Defaults
The default role for a port is Auto-SP, where the power mode is determined by the switch connected to the port (RPS for Catalyst running the LAN base image, or SP for Catalyst switches running the IP base or IP services image).
The default for the XPS power supply A (PS1) is RPS mode. The default for power supply B (PS2) is SP mode.
The default mode for all ports and power supplies is enabled.
On ports configured for RPS, the default priority is the same as the port number.
How to Configure the XPS 2200
You can configure the XPS from any switch connected to an XPS port. If you enter XPS configuration commands on more than one switch, the last configuration applied takes effect. Only the switch and port name are saved in the switch configuration file.
Configuring System Names
1.
enable
3.
power xps
switch-number
name
{name |
serialnumber}
4.
power xps
switch-number
port
{name |
hostname |
serialnumber}
6.
show env xps system
7.
copy running-config
startup-config
DETAILED STEPS
Configuring XPS Ports
1.
enable
2.
power
xps
switch-number
port
{number |
connected}
mode
{disable |
enable}
3.
power xps
switch-number
port
{number |
connected}
role
{auto |
rps}
4.
power xps
switch-number
port
{number |
connected}
priority
port-priority
5.
show env xps port
DETAILED STEPS
Command or Action | Purpose | |||||
---|---|---|---|---|---|---|
Step 1 |
enable
Example:
Switch> enable
|
Enables privileged EXEC mode. Enter your password if prompted. | ||||
Step 2 |
power
xps
switch-number
port
{number |
connected}
mode
{disable |
enable}
|
| ||||
Step 3 | power xps
switch-number
port
{number |
connected}
role
{auto |
rps}
|
| ||||
Step 4 | power xps
switch-number
port
{number |
connected}
priority
port-priority
Example:
Switch
|
Sets the RPS priority of the port, where higher priority ports take precedence over low priority ports if multiple power supplies fail. This command takes effect only when the port mode is RPS. When the port mode is stack power, you set priority by using the stack power commands. | ||||
Step 5 | show env xps port
|
Verifies the XPS configuration of the port. |
Configuring XPS Power Supplies
1.
enable
2.
power
xps
switch-number
supply
{A |
B}
mode
{rps |
sp}
3.
power xps
switch-number
supply
{A |
B}
{on |
off}
5.
show env xps
power
DETAILED STEPS
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 |
enable
Example:
Switch> enable
|
Enables privileged EXEC mode. Enter your password if prompted. | ||
Step 2 |
power
xps
switch-number
supply
{A |
B}
mode
{rps |
sp}
|
Sets the XPS power supply mode.
| ||
Step 3 | power xps
switch-number
supply
{A |
B}
{on |
off}
|
Sets the XPS power supply to be on or off. The default is for both power supplies to be on. | ||
Step 4 | end
| |||
Step 5 | show env xps
power
|
Displays the status of the XPS power supplies. |
Monitoring and Maintaining the XPS 2200
Command |
Purpose |
---|---|
show env xps system |
Verifies the configured name of the system and ports. |
show env xps port |
Verifies the XPS configuration of the port. |
show env xps power |
Displays the status of the XPS power supplies. |
Additional References
The following sections provide references related to switch administration:
Feature History and Information for XPS 2200
Release |
Feature |
---|---|
Cisco IOS XE 15.2.(3)E1 |
XPS 2200 feature is introduced |
Related Documents
Related Topic | Document Title |
---|---|
Configuring Stack Power |
Consolidated Platform Configuration Guide, Cisco IOS XE 3.7E and Later (Catalyst 3850 Switches) |
Standards
Standards |
Document Title |
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
MIBs
MIBs | MIBs Link |
---|---|
— |
To locate and download MIBs using Cisco IOS XR software, use the Cisco MIB Locator found at the following URL and choose a platform under the Cisco Access Products menu: http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml |
RFCs
RFCs | Title |
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
— |
Technical Assistance
Description | Link |
---|---|
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content. |
http://www.cisco.com/techsupport |