- Preface
- Product Overview
- Configuring the Router for the First Time
- Configuring a Supervisor Engine 720
- Configuring a Route Switch Processor 720
- Configuring NSF with SSO Supervisor Engine Redundancy
- ISSU and eFSU on Cisco 7600 Series Routers
- Configuring RPR and RPR+ Supervisor Engine Redundancy
- Configuring Interfaces
- Configuring a Supervisor Engine 32
- Configuring LAN Ports for Layer 2 Switching
- Configuring Flex Links
- Configuring EtherChannels
- Configuring VTP
- Configuring VLANs
- Configuring Private VLANs
- Configuring Cisco IP Phone Support
- Configuring IEEE 802.1Q Tunneling
- Configuring Layer 2 Protocol Tunneling
- Configuring L2TPv3
- Configuring STP and MST
- Configuring Optional STP Features
- Configuring Layer 3 Interfaces
- Configuring GTP-SLB IPV6 Support
- IP Subscriber Awareness over Ethernet
- Configuring UDE and UDLR
- Configuring Multiprotocol Label Switching on the PFC
- Configuring IPv4 Multicast VPN Support
- Configuring Multicast VPN Extranet Support
- Configuring IP Unicast Layer 3 Switching
- Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching
- Configuring IPv4 Multicast Layer 3 Switching
- Configuring MLDv2 Snooping for IPv6 Multicast Traffic
- Configuring IGMP Snooping for IPv4 Multicast Traffic
- Configuring PIM Snooping
- Configuring Network Security
- Understanding Cisco IOS ACL Support
- Configuring VRF aware 6RD Tunnels
- Configuring VLAN ACLs
- Private Hosts (Using PACLs)
- Configuring IPv6 PACL
- IPv6 First-Hop Security Features
- Configuring Online Diagnostics
- Configuring Denial of Service Protection
- Configuring DHCP Snooping
- Configuring Dynamic ARP Inspection
- Configuring Traffic Storm Control
- Unknown Unicast Flood Blocking
- Configuring PFC QoS
- Configuring PFC QoS Statistics Data Export
- Configuring MPLS QoS on the PFC
- Configuring LSM MLDP based MVPN Support
- Configuring IEEE 802.1X Port-Based Authentication
- Configuring IEEE 802.1ad
- Configuring Port Security
- Configuring UDLD
- Configuring NetFlow and NDE
- Configuring Local SPAN, RSPAN, and ERSPAN
- Configuring SNMP IfIndex Persistence
- Power Management and Environmental Monitoring
- Configuring Web Cache Services Using WCCP
- Using the Top N Utility
- Using the Layer 2 Traceroute Utility
- Configuring Bidirectional Forwarding and Detection over Switched Virtual Interface
- Configuring Call Home
- Configuring IPv6 Policy Based Routing
- Using the Mini Protocol Analyzer
- Configuring Resilient Ethernet Protocol
- Configuring Synchronous Ethernet
- Configuring Link State Tracking
- Configuring BGP PIC Edge and Core for IP and MPLS
- Configuring VRF aware IPv6 tunnels over IPv4 transport
- ISIS IPv4 Loop Free Alternate Fast Reroute (LFA FRR)
- Multicast Service Reflection
- Y.1731 Performance Monitoring
- Online Diagnostic Tests
- Acronyms
- Cisco IOS Release 15S Software Images
- Index
Power Management and Environmental Monitoring
This chapter describes the power management and environmental monitoring features in the Cisco 7600 series routers.
Note For complete syntax and usage information for the commands used in this chapter, refer to the Cisco 7600 Series Routers Command References at this URL:
http://www.cisco.com/en/US/products/hw/routers/ps368/prod_command_reference_list.html
Understanding How Power Management Works
These sections describe power management in the Cisco 7600 series routers:
- Enabling or Disabling Power Redundancy
- Powering Modules Off and On
- Viewing System Power Status
- Power Cycling Modules
- Power Cycling Power Supplies
- Determining System Power Requirements
- Determining System Hardware Capacity
- Determining Sensor Temperature Threshold
Note Installed power supplies in a system can be of different wattage ratings. Installed power supplies can also be both AC-input, both DC-input, or one AC-input and one DC-input. Power supplies can be configured in either redundant or non-redundant mode. For detailed information on supported power supply configurations, refer to the Cisco 7600 Series Router Installation Guide.
The modules have different power requirements, and some configurations require more power than a single power supply can provide. The power management feature allows you to power all installed modules with two power supplies. However, redundancy is not supported in this configuration because the total power drawn from both power supplies is at no time greater than the capability of one supply. Redundant and nonredundant power configurations are described in the following sections.
To determine the power requirements for your system, see the “Determining System Power Requirements” section.
Enabling or Disabling Power Redundancy
To disable or enable redundancy (redundancy is enabled by default) from global configuration mode, enter the power redundancy-mode combined | redundant commands. You can change the configuration of the power supplies to redundant or nonredundant at any time.
To disable redundancy, use the combined keyword. In a nonredundant configuration, the power available to the system is the combined power capability of both power supplies. The system powers up as many modules as the combined capacity allows. However, if one power supply fails and there is not enough power for all of the previously powered-up modules, the system powers down those modules.
To enable redundancy, use the redundant keyword. In a redundant configuration, the total power drawn from both power supplies is not greater than the capability of one power supply. If one supply malfunctions, the other supply can take over the entire system load. When you install and power up two power supplies, each concurrently provides approximately half of the required power to the system. Load sharing and redundancy are enabled automatically; no software configuration is required.
To view the current state of modules and the total power available for modules, enter the show power command (see the “Viewing System Power Status” section).
Table 59-1 describes how the system responds to changes in the power supply configuration.
Powering Modules Off and On
To power modules off and on from the CLI, perform this task.
|
|
|
---|---|---|
Note When you enter the no power enable module slot command to power down a module, the module’s configuration is not saved.
This example shows how to power on the module in slot 3:
Viewing System Power Status
You can view the current power status of system components by entering the show power command as follows:
You can view the current power status of a specific power supply by entering the show power command as follows:
You can display power supply input fields by specifying the power supply number in the command. A new power-output field with operating mode is displayed for power supplies with more than one output mode. Enter the show env status power-supply command as follows:
Power Cycling Modules
You can power cycle (reset) a module from global configuration mode by entering the power cycle module slot command. The module powers off for 5 seconds, and then powers on.
Power Cycling Power Supplies
If you have redundant power supplies and you power cycle one of the power supplies, only that power supply is power cycled. If you power cycle both power supplies, the system goes down and comes back up in 10 seconds.
If you only have one power supply and you power cycle that power supply, the system goes down and comes back up in 10 seconds.
This example shows how to power cycle a power supply:
Determining System Power Requirements
The power supply size determines the system power requirements. When you use the 1000 W and 1300 W power supplies, you might have configuration limitations depending on the size of chassis and type of modules installed. For information about power consumption, refer to the Release Notes for Cisco IOS Release 12.2SX on the Supervisor Engine 720, Supervisor Engine 32, and Supervisor Engine 2 publication at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/122sx/ol_4164.htm
Determining System Hardware Capacity
You can determine the system hardware capacity by entering the show platform hardware capacity command. This command displays the current system utilization of the hardware resources and displays a list of the currently available hardware capacities, including the following:
- Hardware forwarding table utilization
- Switch fabric utilization
- CPU(s) utilization
- Memory device (flash, DRAM, NVRAM) utilization
This example shows how to display CPU capacity and utilization information for the route processor, the switch processor, and the LAN module in the Cisco 7600 series router:
This example shows how to display EOBC-related statistics for the route processor, the switch processor, and the DFCs in the Cisco 7600 series router:
This example shows how to display the current and peak switching utilization:
This example shows how to display information about the total capacity, the bytes used, and the percentage that is used for the flash and NVRAM resources present in the system:
This example shows how to display the capacity and utilization of the EARLs present in the system:
This example shows how to display the interface resources:
This example shows how to display SPAN information:
This example shows how to display the capacity and utilization of resources for Layer 3 multicast functionality:
This example shows how to display information about the system power capacities and utilizations:
This example shows how to display the capacity and utilization of QoS policer resources for each EARL in the Cisco 7600 series router.
This example shows how to display information about the key system resources:
This example shows how to display VLAN information:
Determining Sensor Temperature Threshold
The system sensors set off alarms based on different temperature threshold settings. You can determine the allowed temperatures for the sensors by using the show environment alarm threshold command.
This example shows how to determine sensor temperature thresholds:
Understanding How Environmental Monitoring Works
Environmental monitoring of chassis components provides early-warning indications of possible component failures, which ensures a safe and reliable system operation and avoids network interruptions. This section describes the monitoring of these critical system components, which allows you to identify and rapidly correct hardware-related problems in your system.
Monitoring System Environmental Status
To display system status information, enter the show environment [ alarm | cooling | status | temperature ] command. The keywords display the following information:
– status —Displays alarm status.
– thresholds —Displays alarm thresholds.
- cooling —Displays fan tray status, chassis cooling capacity, ambient temperature, and per-slot cooling capacity.
- status —Displays field-replaceable unit (FRU) operational status and power and temperature information.
- temperature —Displays FRU temperature information.
To view the system status information, enter the show environment command:
Understanding LED Environmental Indications
The LEDs can indicate two alarm types: major and minor. Major alarms indicate a critical problem that could lead to the system being shut down. Minor alarms are for informational purposes only, giving you notice of a problem that could turn critical if corrective action is not taken.
When the system has an alarm (major or minor), that indicates an overtemperature condition, the alarm is not canceled nor is any action taken (such as module reset or shutdown) for 5 minutes. If the temperature falls 5°C (41°F) below the alarm threshold during this period, the alarm is canceled.
Table 59-2 lists the environmental indicators for the supervisor engine and switching modules.
Note Refer to the Cisco 7600 Series Router Module Installation Guide for additional information on LEDs, including the supervisor engine SYSTEM LED.
|
|
|
|
---|---|---|---|
Supervisor engine temperature sensor exceeds major threshold1 |
Generates syslog message and an SNMP trap. If there is a redundancy situation, the system switches to a redundant supervisor engine and the active supervisor engine shuts down. If there is no redundancy situation and the overtemperature condition is not corrected, the system shuts down after 5 minutes. |
||
Supervisor engine temperature sensor exceeds minor threshold |
|||
Redundant supervisor engine temperature sensor exceeds major or minor threshold |
Generates syslog message and an SNMP trap. If a major alarm is generated and the overtemperature condition is not corrected, the system shuts down after 5 minutes. |
||
Generates syslog message and SNMP. Powers down the module4. |
|||
1.Temperature sensors monitor key supervisor engine components including daughter cards. 2.A STATUS LED is located on the supervisor engine front panel and all module front panels. 3.The STATUS LED is red on the failed supervisor engine. If there is no redundant supervisor, the SYSTEM LED is red also. 4.See the “Understanding How Power Management Works” section for instructions. |