Power Supply Configuration Modes
This section includes the following topics:
Power Supply Configuration Overview
You can configure one of the following power modes to either use the combined power provided by the installed power supply units or to provide power redundancy when there is a power loss:
- Combined mode—Provides the maximum amount of available power by utilizing the combined power output from all installed power supply units for switch operations. This mode does not provide redundancy.
- Power-supply redundancy mode—Allows you to replace a power supply during switch operations. All power supplies are active. The available power is calculated as the least amount of power available from all but one of the power supply units (N+1). The reserve power is the amount of power output by the power supply unit that can output the most power. For example, if three power supply units output 3 kW, 6 kW, and 6 kW, the available power is 9 kW (3 kW + 6 kW) and the reserve power is 6 kW.
- Input source redundancy mode—Takes power from two electrical grids so that if one grid goes down, the other grid can provide the power needed by the switch. For the Cisco Nexus 7004 chassis, each grid powers half of the power supplies. For the Cisco Nexus 7009, 7010, and 7018 chassis, each grid powers half of each power supply unit (grid A is connected to the Input 1 receptacle on each power supply unit and grid B is connected to the Input 2 receptacle on each power supply unit). The available power is the amount of power output by the portions of the power supply units that are connected to the same grid. For example, if three power supply units are connected to a 110-V grid and a 220-V grid, each power supply outputs 1.2 kW for the 110-V grid and 3.0 kW for the 220-V grid. The available power would be 3.6 kW (1.2 kW + 1.2 kW + 1.2 kW) and the reserve power would be 9.0 kW (3.0 kW + 3.0 kW + 3.0 kW).
- Full redundancy mode—Provides both power-supply redundancy and input-source redundancy. This mode allows you to replace a power supply unit without interrupting switch operations or continue powering the switch if one of two grids goes down. The available power is the lesser amount of output power for power supply redundancy or input source redundancy.
The amount of power available for use with your Cisco Nexus 7000 Series switch depends on the number of power supply units, input voltage used, and the power mode used. To determine the amount of available power for the power supply units, see the following tables:
- For the 3-kW AC power supply units, see Table A-11
- For the 6-kW AC power supply units, see Table A-13
- For the 7.5-kW AC power supply units, see Table A-14
- For the 3-kW DC power supply units, see Table A-15
- For the 6-kW DC power supply units, see Table A-17
- For the 3.5-kW HVAC/HVDC power supplies, see and
Configuring the Power Supply Mode
You can configure the power supply mode.
SUMMARY STEPS
1. config t
2. power redundancy-mode mode
DETAILED STEPS
|
|
|
Step 1 |
|
Starts the global configuration mode. |
Step 2 |
power redundancy-mode
mode
switch(config)# power redundancy-mode redundant
switch(config)#
|
Configures one of the following power supply modes:
- For combined mode, use the combined keyword.
- For power supply redundancy, use the ps-redundant keyword.
- For input source redundancy, use the insrc-redundant keyword.
- For full redundancy, use the redundant keyword.
|
Note To display the current power supply configuration, use the show environment power command.
Power Supply Configuration Guidelines
Follow these guidelines when configuring power supply units:
- When power supply units with different capacities are installed in the switch, the amount of available power differs based on one of the following configuration modes:
– Combined mode—To activate this mode, use the power redundancy-mode combined command. If the combined power provided by all of the installed power supply units meets the power requirements of all of the switch modules, then this mode is sufficient for running your switch.
For example, suppose your system has the following setup:
Power supply unit 1 outputs 6 kW.
The switch power requirement is 8.784 kW.
The following two scenarios explain what happens for different numbers of power supply units that you install:
Scenario 1: If you do not add a power supply unit, the available power (6 kW) is insufficient for the switch power requirement, so the switch powers the supervisor modules, fabric modules, and fan trays, before powering as many I/O modules as the remaining available power can support (one or more I/O modules might not be powered).
Scenario 2: If you install an additional power supply unit that can output 3 kW, the available power becomes 9.0 kW. The increased amount of available power exceeds the switch power requirement, so all of the modules and fan trays in the switch can power up.
Table 8-1 shows the results for each scenario.
Table 8-1 Combined Power Mode Scenarios
|
|
|
|
|
|
1 |
6.0 |
— |
8.784 |
6.0 |
Available power is less than system usage, so you cannot power the entire system with this mode. |
2 |
6.0 |
3.0 |
8.784 |
9.0 |
Available power exceeds the system usage, so you can use this mode to power your entire system. |
– Power supply redundancy mode—To activate this power mode, use the power redundancy-mode ps-redundant command. The power supply unit that outputs the most power provides the reserve power, and the combined output for the other power supply units becomes the available power.
For example, suppose your system has the following setup:
Power supply unit 1 outputs 3.0 kW.
Power supply unit 2 outputs 6.0 kW.
The switch power requirement is 8.784 kW.
The following three scenarios explain what happens depending on what you install for the third power supply unit:
Scenario 1: If you do not add a third power supply unit, the reserve power is 6 kW and the available power is 3 kW. The available power is insufficient for the switch power requirement, so you cannot power the entire switch.
Scenario 2: If you add a power supply unit that outputs 3 kW, the reserve power remains 6 kW and available power becomes 6 kW. The available power is still insufficient because it does not meet the switch power requirement, so you can power more modules than you could with Scenario 1, but you still cannot power the entire switch.
Scenario 3: If you add a power supply unit that outputs 7.5 kW, the reserve power becomes 7.5 kW and the available power becomes 9 kW. The available power exceeds the switch power requirement, so you can power up all of the modules and fan trays in the switch.
Table 8-2 shows the results for each scenario.
Table 8-2 Power Supply Redundancy Mode Scenarios
|
|
|
|
|
|
|
|
1 |
3.0 |
6.0 |
— |
8.784 |
6.0 |
— |
The available power does not meet the system usage requirement, so you cannot power the entire system with this power supply configuration and mode. |
2 |
3.0 |
6.0 |
3.0 |
8.784 |
6.0 |
6.0 |
The available power does not meet the system usage, so you cannot power the entire system with this power supply configuration and mode. |
3 |
3.0 |
6.0 |
7.5 |
8.784 |
9.0 |
7.5 |
The available power exceeds the system usage, so you can power the entire system with this power supply configuration and mode. |
– Input source redundancy mode—To activate this power mode, use the power redundancy-mode insrc_redundant command. The reserve power is the greater of power outputs for the two grids, and the available power becomes the lesser of power outputs for the two grids.
For example, suppose your system has the following setup:
Grids 1 and 2 each input 220 V to the power supply units.
Power supply units 1 and 2 each output 6 kW.
Current usage requirement is 8.784 kW.
The following three scenarios explain what happens for different numbers of power supply units that you install:
Scenario 1: If you do not add a power supply unit, the reserve power is 6 kW (3 kW for one power supply unit and 3 kW for the other power supply unit), and the available power is 6 kW (3 kW for one power supply unit plus 3 kW for the other power supply unit). The available power does not meet the switch usage requirement, so you cannot power the entire switch.
Scenario 2: If you add a power supply that outputs 3 kW, the reserve power is 9 kW (3 kW for three power supply units), and the available power is 6 kW (3 kW for each of two power supply units). The available power does not meet the system usage requirement, so you cannot power the entire switch.
Scenario 3: If you add a power supply unit that outputs 7.5 kW, the reserve power is 9.75 kW (3 kW for two power supply units and 3.75 kW for the new power supply unit), and the available power is 9.75 kW (3 kW for two power supply units and 3.75 kW for the new power supply unit). The available power exceeds the switch usage requirement, so you can power up all of the modules and fan trays in the switch.
Table 8-3 shows the results for each scenario.
Table 8-3 Input Source Redundancy Mode Scenarios
|
|
|
|
|
|
|
|
1 |
6.0 |
6.0 |
- |
8.784 |
6.0 |
6.0 |
Available power (the power supply output for either grid) does not meet the system usage requirement. |
2 |
6.0 |
6.0 |
3.0 |
8.784 |
9.0 |
6.0 |
The power supply output for one grid meets the system usage requirement, but the power supply output for the other grid does not meet the system usage requirement. |
3 |
6.0 |
6.0 |
7.5 |
8.784 |
9.75 |
9.75 |
The power supply output for both grids meet the meet the system usage requirement. |
– Full redundancy mode—To activate this power mode, use the power redundancy-mode redundant command. The reserve power is the greater amount of reserve power for power supply redundancy and input source redundancy, and the available power is the lesser amount of available power for the same two redundancy modes.
For example, suppose your system has the following setup:
Grids A and B each provide 220 V.
Power supply units 1 and 2 each output 6.0 kW.
Switch usage requirement is 8.784 kW.
The following three scenarios explain what happens for different numbers of power supply units that you install:
Scenario 1: If you do not add a power supply unit, the reserve power is 6 kW and the available power is 6 kW. The available power does not meet the switch usage requirement, so you cannot power up the entire switch.
Scenario 2: If you add a 3-kW power supply unit, the reserve power is 9 kW (3 kW for three power supply units on one grid), and the available power is 6 kW (3 kW for two power supply units on a second grid). The available power does not meet the switch usage requirement, so you cannot power up the entire switch.
Scenario 3: If you add a 6-kW power supply unit, the reserve power is 9 kW (3 kW for three power supply units on the same grid), and the available power is 9 kW (3 kW for three power supply units on a second grid). The available power meets the switch usage requirements, so you can power up the entire switch.
Table 8-4 shows the results for each scenario.
Table 8-4 Full Redundancy Mode Scenarios
|
|
|
|
|
|
|
|
|
|
|
|
1 |
6.0 |
6.0 |
— |
8.784 |
6.0 |
6.0 |
6.0 |
6.0 |
Available power does not meet the switch usage requirement. |
2 |
6.0 |
6.0 |
3.0 |
8.784 |
6.0 |
9.0 |
9.0 |
6.0 |
Available power for the power supply mode is sufficient but the available power for the input source mode is insufficient, so the available power does not meet the switch usage requirement. |
3 |
6.0 |
6.0 |
6.0 |
8.784 |
9.0 |
9.0 |
12.0 |
6.0 |
Available power for both modes meets the switch usage requirement, so you can power up the entire switch. |
Information About Fan Trays
Hot-swappable fan trays are provided in all switches in the Cisco Nexus 7000 Series to manage airflow and cooling for the entire switch. Each fan tray contains multiple fans to provide redundancy. The switch can continue functioning in the following situations:
- One or more fans fail within a fan tray—Even with multiple fan failures, the Cisco Nexus 7000 Series switch can continue functioning. When a fan fails within a tray, the functioning fans in the module increase their speed to compensate for the failed fans.
- The fan tray is removed for replacement—The fan tray is designed to be removed and replaced while the system is operating without presenting an electrical hazard or damage to the system. Depending on the type of fan tray that you remove, one of the following will occur:
– Cisco Nexus 7004 or 7009 Series fan tray—The switch can function without a fan tray for up to two minutes by which time you must replace the missing fan tray.
– Cisco Nexus 7010 Series system fan tray—The fans in the remaining system fan tray increase their speeds as needed for the current temperature until you replace the missing fan tray.
– Cisco Nexus 7010 Series fabric fan tray—The fan in the remaining fabric fan tray increases its speed to the maximum speed until you replace the missing fabric fan tray.
– Cisco Nexus 7018 Series fan tray—If you do not replace the fan tray within three minutes, the system shuts down the modules cooled by the removed fan tray. For the top fan tray, that means that the system would shut down the supervisor in slot 9, the I/O modules in slots 1 through 8, and the fabric modules. For the bottom fan tray, that means that the system would shut down the supervisor in slot 10 and the I/O modules in slots 11 through 18.
Note When replacing a failed fan tray in a running system, be sure to promptly replace the fan tray.
Tip If one or more fans fail within a fan tray, the Fan Status LED turns red. A fan failure could lead to temperature alarms if not corrected immediately.
The fan status is continuously monitored by the software. In case of a fan failure, the following actions occur:
- System messages are displayed.
- Call Home alerts are sent (if configured).
- SNMP notifications are sent (if configured).
To display the fan module statuses, use the show environment fan command as shown inExample 8-8 (Cisco Nexus 7004 switch), Example 8-9 (Cisco Nexus 7009 switch), Example 8-10 (Cisco Nexus 7010 switch), or Example 8-11 (Cisco Nexus 7018 switch).
Example 8-8 Displaying Fan Information for a Cisco Nexus 7004 Series Chassis
switch# show environment fan
-------------------------------------------------------
-------------------------------------------------------
Fan1(sys_fan1) N7K-C7004-FAN 0.110 Ok
Fan Zone Speed: Zone 1: 0x7f
Example 8-9 Displaying Fan Information for a Cisco Nexus 7009 Series Chassis
switch# show environment fan
----------------------------------------------
----------------------------------------------
Fan1(sys_fan1) N7K-C700-FAN 0.31 Ok
Example 8-10 Displaying Fan Information for a Cisco Nexus 7010 Series Chassis
switch# show environment fan
------------------------------------------------------
------------------------------------------------------
ChassisFan1 N7K-C7010-FAN-S 0.410 Ok
ChassisFan2 N7K-C7010-FAN-S 0.410 Ok
ChassisFan3 N7K-C7010-FAN-F 0.209 Ok
ChassisFan4 N7K-C7010-FAN-F 0.209 Ok
Example 8-11 Displaying Fan Information for a Cisco Nexus 7018 Series Chassis
switch# show environment fan
------------------------------------------------------
------------------------------------------------------
Fan1(sys_fan1) N7K-C7018-FAN 0.204 Ok
Fan2(sys_fan2) N7K-C7018-FAN 0.204 Ok
The possible Status field values are as follows:
- If the fan module is operating properly, the status is Ok.
- If the fan is physically absent, the status is Absent.
- If the fan is physically present but not working properly, the status is Failure.
If the status for one of the fan trays is “Failure,” the status field also displays the numbers of the failing fans. For the Cisco Nexus 7010 system, each system fan tray has six fans to cool the supervisor and I/O modules and each fabric fan tray has one fan to cool the fabric modules. For the Cisco Nexus 7018 system, each fan tray has 14 fans to cool the supervisor, I/O modules, and fabric modules as follows:
– Fans 1 through 12 cool the I/O modules in slots 1 through 8 and the supervisor module in slot 9.
– Fans 13 and 14 cool the fabric modules
– Fans 1 through 12 cool the I/O modules in slots 11 through 18 and the supervisor module in slot 10
– Fans 13 and 14 are not used
Configuring EPLDs
The Cisco Nexus 7000 Series switches, which include the Cisco Nexus 70 xx and 77 xx switches, contain several programmable logical devices (PLDs) that provide hardware functionalities in all modules. Cisco provides electronic programmable logical device (EPLD) image upgrades to enhance hardware functionality or to resolve known issues. PLDs include electronic programmable logical devices (EPLDs), field programmable gate arrays (FPGAs), and complex programmable logic devices (CPLDs), but they do not include ASICs. In this document, the term EPLD is used for FPGA and CPLDs.
The advantage of having EPLDs for some module functions is that when you need to upgrade those functions, you just upgrade their software images instead of replacing their hardware.
Note EPLD image upgrades for an I/O module disrupt the traffic going through the module because the module must power down briefly during the upgrade. The system performs EPLD upgrades on one module at a time, so at any one time the upgrade disrupts only the traffic going through one module.
Cisco does not provide upgrade EPLD images very frequently, and you do not have to upgrade your EPLD images unless they fix the functions for the hardware that you are using in your Cisco Nexus 7000 Series switch. The EPLD image upgrades are independent from the Cisco NX-OS In-Service Software Upgrade (ISSU) process, which upgrades the system and kickstart images with no impact on the network environment.
When Cisco makes an EPLD image upgrade available, the Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes announce its availability, and you can download it from http://www.cisco.com.
This section includes the following topics:
Deciding When to Upgrade EPLDs
You do not always need to upgrade EPLD images but the following circumstances do require that you upgrade these images:
- If you are upgrading Supervisor 1 modules with Supervisor 2 or Supervisor 2E modules and the switch has Fabric 2 modules (For the Cisco Nexus 7009 switch, make sure that you are using image 1.003 or later image for the fabric 2 modules. For Cisco Nexus 7010 and 7018 switches, make sure that you are using image 0.007 or later image.)
Note Supervisor 1 modules are not supported by the Cisco Nexus 7004 switches.
- If you are enabling software features (LIST, VPCs, and so on) that require EPLDs
- If you are using M2 Series 100-Gbps Ethernet I/O modules that remain powered down after booting up the switch
When new EPLD images are available, the upgrades are always recommended if your network environment allows for a maintenance period in which some level of traffic disruption is acceptable. If such a disruption is not acceptable at this time, you might consider postponing the upgrade until a better time.
Note The EPLD upgrade operation is a disruptive operation. You should execute this operation only at a programmed maintenance time. The system/kickstart ISSU upgrade is a nondisruptive upgrade.
Note Do not perform an EPLD upgrade during an ISSU system/kickstart upgrade.
Table 8-8 provides high-level guidelines to help network administrators determine whether an EPLD upgrade is necessary when upgrading Cisco NX-OS Release 5.0(1) or a later release. If you are upgrading an earlier release, see one of the following earlier versions of the release notes:
- Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes, Release 4.0
- Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes, Release 4.1
Table 8-8 Conditions For Upgrading EPLD Images
|
Modules Targeted for Upgrades
|
M2 Series I/O modules remain powered down after booting up the switch for Cisco NX-OS Release 6.1(1) or 6.1(2). |
Download one of the following EPLD images and use the no poweroff module command for each powered down M2 Series I/O module:
- For Release 6.1(1) and supervisor 1 modules download n7000-s1-epld.6.1.1a.img.
- For Release 6.1(1) and supervisor 2 modules download n7000-s2-epld.6.1.1a.img.
- For Release 6.1(2) and supervisor 1 modules download n7000-s1-epld.6.1.2a.img.
- For Release 6.1(2) and supervisor 2 modules download n7000-s2-epld.6.1.2a.img.
|
Upgrading the Cisco NX-OS operating system from Release 4.x to Release 5.0 or later releases. |
Update all supervisor, I/O, and fabric modules with the latest EPLD images. |
Moving 32-port 10-Gigabit Ethernet I/O modules from a Cisco Nexus 7010 switch to a Cisco Nexus 7018 switch |
32-port 10-Gigabit Ethernet I/O modules (N7K-M132XP-12) |
Moving 48-port 10/100/1000 Ethernet I/O modules from a Cisco Nexus 7010 switch to a Cisco Nexus 7018 switch |
48-port 10/100/1000 Ethernet I/O modules (N7K-M148GT-11) |
Moving the supervisor (N7K-SUP1) modules from a Cisco Nexus 7010 switch to a Cisco Nexus 7018 switch |
Supervisor (N7K-SUP1) modules |
Switch Requirements
The Cisco Nexus 7000 Series switch must be running the Cisco NX-OS operating system and include the following hardware:
- One or two supervisor modules, each with at least 120 MB of available bootflash or slot0 memory
- One or more I/O modules
- One or more fabric modules
- One fan tray module (Cisco Nexus 7009)
- Two fabric fan tray modules (Cisco Nexus 7010)
- Two system fan tray modules (Cisco Nexus 7010)
- Two fan tray modules (Cisco Nexus 7018)
You must be able to access the system through a console, SSH, or Telnet.
You must have administrator privileges to work with the Cisco Nexus 7000 Series switches.
Determining Whether to Upgrade EPLDs
As shown in Table 8-9 , you can use various show commands to determine whether the EPLDs can be upgraded for all the modules or for specific modules on a switch. These commands indicate the current EPLD images, new EPLD images, and whether the upgrades would be disruptive to switch operations.
Table 8-9 Displaying the EPLD Upgrade Status for the Switch and its Modules
Modules to Verify EPLD Status
|
|
All modules on the switch |
show install all impact epld bootflash: filename |
I/O and supervisor modules |
show install module slot_number impact epld bootflash: filename |
Fabric modules |
show install xbar-module slot_number impact epld bootflash: filename |
Fan-tray modules |
show install fan-module slot_number impact epld bootflash: filename |
If there are different EPLD images to use depending on the version ID (VID) of a hardware module (see ), then you must determine the version number of the module by using the show sprom module number command as shown in Example 8-12.
Example 8-12 Determining the Version Number of a Supervisor or I/O Module
switch# show sprom module 8 1
DISPLAY linecard sprom contents of module 8:
snmpOID : 9.12.3.1.9.66.5.0
VID : V01 <------Version ID
Downloading the EPLD Images
Before you can prepare the EPLD images for installation, you must download them to the FTP or management server.
To download the EPLD images, follow these steps:
Step 1 From a browser, go to the following URL:
http://www.cisco.com
The browser will display the Cisco website.
Step 2 From the Products & Services tab, choose Switches.
The Switches page opens.
Step 3 In the Data Center area, click the arrow next to View Products.
The page lists the Data Center products.
Step 4 Click Nexus 7000.
The Cisco Nexus 7000 Series Switches page opens.
Step 5 In the Support area, click Download Software.
The Downloads page opens and lists the Data Center switches.
Step 6 Choose a Cisco Nexus 7000 Series switch from the list under Data Center Switches > Cisco Nexus 7000 Series Switches.
The Log In page opens.
Step 7 If you are an existing user, enter your username in the User Name field and your password in the Password field. If you are a new user, click Register Now and provide the required information before returning to the Log In page and logging in with your new username.
The Downloads page lists the software types that can be downloaded for the switch that you specified.
Step 8 Click NX-OS EPLD Updates.
The Downloads page lists software releases that you can download.
Step 9 Choose Latest Releases > 6.2(8).
The Downloads page displays image information, including a link to the downloadable Tar file, to the right of the releases.
Note For Releases 6.1(1) or 6.1(2), you must download EPLD image files for 6.1(1a) or 6.1(2a).
Step 10 Click the link for the Tar file.
The Downloads page displays a Download button and lists information for the Tar file.
Step 11 Click Download.
The Supporting Documents page opens to display the rules for downloading the software.
Step 12 Read the rules and click Agree.
A File Download dialog box opens to ask if you want to open or save the images file.
Step 13 Click Save.
The Save As dialog box appears.
Step 14 Indicate where to save the Tar file and click Save.
The Tar file saves to the location that you specified.
You are ready to prepare the EPLD images for Installation (see the “Preparing the EPLD Images for Installation” section).
EPLD Images Needed for vPCs
The virtual port channel (vPC) feature is available beginning with Cisco NX-OS Release 4.1(3). When you enable vPC on the chassis, you must have EPLD image 186.3 (or later image) on the 32-port 10-Gigabit Ethernet types of I/O modules (N7K-M132XP-12 and N7K-M132XP-12L).
Note The EPLD upgrade operation is a disruptive operation. You should execute this operation only at a programmed maintenance time. The system/kickstart ISSU upgrade is a nondisruptive upgrade.
Most of the N7K-M132XP-12 modules in the chassis already meet this minimum EPLD requirement, but if you are working with an N7K-M132XP-12 module that was shipped before June 2008, you might need to upgrade the EPLD version.
To determine the EPLD version for all N7K-M132XP-12 modules, enter the show version module slot_number epld command. If the line FE Bridge(x) version displays a version earlier than 186.7, you should schedule an EPLD upgrade to a version that is compatible with the target Cisco NX-OS release. For example, if you want to run Cisco NX-OS Release 6.1(1), you should choose Release 6.1(1) EPLDs.
The following example shows Release 186.008 on the FE Bridge line, which is the correct EPLD version:
Nexus-7k(config)# show version module 7 epld
EPLD Device Version
-----------------------------------------
Power Manager 4.008
IO 1.016
Forwarding Engine 1.006
FE Bridge(1) 186.008 << OK!
FE Bridge(2) 186.008 << OK!
Linksec Engine(1) 2.007
Linksec Engine(2) 2.007
Linksec Engine(3) 2.007
Linksec Engine(4) 2.007
Linksec Engine(5) 2.007
Linksec Engine(6) 2.007
Linksec Engine(7) 2.007
Linksec Engine(8) 2.007
EPLD Images Needed for LISP
The Locator/ID Separator Protocol ( LISP) feature is available beginning with Cisco NX-OS Release 5.2(1). When you enable LISP on the chassis, you must have EPLD image 186.8 or 186.008 (or later image) on the 32-port 10-Gigabit Ethernet types of I/O modules (N7K-M132XP-12 and N7K-M132XP-12L).
Note The EPLD upgrade operation is a disruptive operation. You should execute this operation only at a programmed maintenance time. The system/kickstart ISSU upgrade is a nondisruptive upgrade.
If you are working with an N7K-M132XP-12 module that was shipped before July 2011, you might need to upgrade the EPLD version.
To determine the EPLD version for all N7K-M132XP-12 and N7K-M132XP-12L modules, enter the show version module slot_number epld. If the line FE Bridge(x) version displays a version earlier than 186.8 or 186.008, you should schedule an EPLD upgrade to a version that is compatible with the target Cisco NX-OS release. For example, if you want to run Cisco NX-OS Release 5.2(1), you should choose Release 5.2(1) EPLDs.
The following example shows Release 186.008 on the FE Bridge line, which is the correct EPLD version:
Nexus-7k(config)# show version module 7 epld
EPLD Device Version
-----------------------------------------
Power Manager 4.008
IO 1.016
Forwarding Engine 1.006
FE Bridge(1) 186.008 << OK!
FE Bridge(2) 186.008 << OK!
Linksec Engine(1) 2.007
Linksec Engine(2) 2.007
Linksec Engine(3) 2.007
Linksec Engine(4) 2.007
Linksec Engine(5) 2.007
Linksec Engine(6) 2.007
Linksec Engine(7) 2.007
Linksec Engine(8) 2.007
Installation Guidelines
You can upgrade (or downgrade) EPLDs using CLI commands on the Cisco Nexus 7000 Series switch. Follow these guidelines when you upgrade or downgrade EPLDs:
- Before you upgrade any EPLD images, be sure that you have updated the Cisco NX-OS operating system to the level required for the images and be sure that you have one of the following EPLD image files:
– n7000-s1-epld.6.2.8.img (for Cisco Nexus 7004, 7009, 7010, and 7018 switches with Supervisor 1 modules)
– n7000-s2-epld.6.2.8.img (for Cisco Nexus 7004, 7009, 7010, and 7018 switches with Supervisor 2 or Supervisor 2E modules)
– n7700-s2-epld.6.2.8.img (for Cisco Nexus 7710 and 7718 switches)
Note EPLD and software images for a chassis with Supervisor 1 modules include “s1” in the image name and images for Supervisor 2 and Supervisor 2E have “s2” in the image name.
- You can execute an upgrade from the active supervisor module only. This upgrade is for one or all of the modules as follows:
– You can upgrade a module individually.
– You can upgrade all modules sequentially.
– You can upgrade all modules in parallel.
- You can update the images for one or all modules whether the switch is online or offline as follows:
– If the modules are online, only the EPLD images with version numbers that differ from the new EPLD images are upgraded.
– If the modules are offline, all of the EPLD images are upgraded.
- On a system that has two supervisor modules, upgrade the EPLDs for the standby supervisor and then switch the active supervisor to the standby mode to upgrade its EPLDs (the supervisor switchover is not disruptive to traffic on Cisco Nexus 7000 Series switches). On a switch that has only one supervisor module, you can upgrade the active supervisor, but this will disrupt its operations during the upgrade.
- If you interrupt an upgrade, you must upgrade the module that is being upgraded again.
- The upgrade process disrupts traffic on the targeted module.
- Do not insert or remove any modules while an EPLD upgrade is in progress.
Preparing the EPLD Images for Installation
Before you can update the EPLD images for each of your switch modules, you must determine the Cisco NX-OS version that your switch is using, make sure that there is space for the new EPLD images, and download the images.
To prepare the EPLD images for installation, follow these steps:
Step 1 Log in to the switch through the console port, an SSH session, or a Telnet session.
Step 2 Verify that the switch is using the expected version of the Cisco NX-OS operating system. The kickstart and system lines indicate the Cisco NX-OS version. This step determines the versions of EPLD images that you must download.
kickstart: version 6.2(8)
BIOS compile time: 02/20/10
kickstart image file is: bootflash:/n7000-s2-kickstart.6.2.8.bin
kickstart compile time: 4/06/2014 12:00:00 [04/06/2014 18:37:07]
system image file is: bootflash:/n7000-s2-dk9.6.2.8.bin
system compile time: 4/06/2014 13:00:00 [04/06/2014 19:21:22]
Step 3 Verify that you have 120 MB of free space on the active or standby supervisor memory devices for the EPLD images that you will be downloading by using the dir bootflash: or dir slot0: commands.
By default, these commands display the used and free memory for the active supervisor. If your switch has an additional supervisor (a standby supervisor), use the show module command to find the module number for the other supervisor, use the attach module command to attach to the module number, and then use the dir bootflash: or dir slot0: command to determine the amount of used and free memory. See Example 8-13 to determine the amount of available bootflash memory, and see Example 8-14 to determine the amount of available slot0 memory.
Example 8-13 Determining the Amount of Available Bootflash Memory
4096 Apr 06 01:19:53 2014 lost+found/
3020665 Jan 02 07:47:36 2014 n7000-s1-debug-sh-bash.6.2.6.gbin
207429135 Jan 02 07:35:03 2014 n7000-s1-dk9.6.2.6.gbin
207558132 Apr 06 07:11:31 2014 n7000-s2-dk9.6.2.8.gbin
29479424 Jan 02 12:03:47 2014 n7000-s2-kickstart.6.2.6.gbin
29467136 Apr 06 10:35:18 2014 n7000-s2-kickstart.6.2.8.gbin
Usage for bootflash://sup-local
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
6 8 10 Gbps Ethernet XL Module N7K-M108X2-12L ok
7 48 1/10 Gbps Ethernet Modul N7K-F248XP-24 ok
8 48 1000 Mbps Optical Ethernet XL Mo N7K-M148GS-11L ok
9 0 Supervisor module-1X N7K-SUP1 ha-standby
10 0 Supervisor module-1X N7K-SUP1 active *
To exit type 'exit', to abort type '$.'
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
Example 8-14 Determining the Amount of Available Slot0 Memory
Usage for slot0://sup-local
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
2 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok
3 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok
4 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok
5 0 Supervisor module-1X N7K-SUP1 ha-standby
6 0 Supervisor module-1X N7K-SUP1 active *
7 48 1/10 Gbps Ethernet Modul N7K-F248XP-24 ok
9 48 1000 Mbps Optical Ethernet Modul N7K-M148GS-11 ok
switch(standby)# dir slot0://sup-standby/
Usage for slot0://sup-standby
Step 4 If there is not at least 120 MB of memory free for the EPLD files, delete some unneeded files, such as earlier images, so there is enough free memory.
switch# delete bootflash:n7000-s1-kickstart.5.2.0.bin
Step 5 Copy the EPLD image file from the FTP or management server to the bootflash or slot0 memory in the active supervisor module. The following example shows how to copy from the FTP server to the bootflash memory:
switch# copy ftp://10.1.7.2/n7000-s1-epld.6.2.8.img bootflash:n7000-s1-epld.6.2.8.img
Note For NX-OS Release 6.1(1), you must copy the n7000-s1-epld.6.1.1a.img (for supervisor 1 modules) or n7000-s2-epld.6.1.1a.img (for supervisor 2 modules) files. For NX-OS Release 6.1(2), you must copy the n7000-s1-epld.6.1.2a.img (for supervisor 1 modules) or n7000-s1-epld.6.1.2a.img (for supervisor 2 modules) files.
Step 6 Copy the EPLD image to the standby supervisor.
switch# copy bootflash:n7000-s1-epld.6.2.8.img bootflash://sup-standby/n7000-s1-epld.6.2.8.img
You are ready to upgrade the EPLD images (see the “Manual Upgrading of EPLD Images” section).
Manual Upgrading of EPLD Images
You can manually upgrade the EPLD images for all of the modules installed in your switch or specific modules installed in your switch. When you request an upgrade, the Cisco NX-OS software lists the current and new versions for each EPLD image with the following results:
- If a module is installed and online, the software lists the installed and new versions for each EPLD. Where there is a difference in versions, the software indicates an upgrade or downgrade to occur when you confirm the process.
- If a module is installed and offline, the software cannot list its current EPLD versions so all EPLDs will be updated when you confirm the upgrade.
- If a module is not installed, the software displays an error message and does not upgrade the EPLDs.
If you need to know which modules can be updated and which upgrades are disruptive to switch operations, see the “Determining Whether to Upgrade EPLDs” section.
To upgrade the EPLD images for a Cisco Nexus 7000 Series switch, you use one of the install commands listed in Table 8-10 . These commands enable you to upgrade the EPLD images for all of the modules on the switch, multiple modules of one or two types, or single modules. When specifying a slot_number, use one number. When specifying slot_numbers, you can specify all for all slots, multiple slots separated by commas ( x, y, z) or a range of slot numbers ( x - y).
Table 8-10 EPLD Upgrade Commands
|
|
All installed modules with one module upgraded at a time |
install all epld epld_image |
All installed modules with the I/O modules upgraded in parallel |
install all epld epld_image parallel |
One or more I/O and supervisor modules with the I/O modules upgraded in parallel |
install all epld epld_image parallel module {all | slot_numbers } |
One or more I/O and supervisor modules with the I/O modules upgraded in parallel and one or more fan-tray modules |
install all epld epld_image parallel module {all | slot_numbers } fan-module {all | slot_numbers } |
One or more I/O and supervisor modules with the I/O modules upgraded in parallel and one or more fabric (xbar) modules |
install all epld epld_image parallel module {all | slot_numbers } xbar-module {all | slot_numbers } |
One or more fan-tray modules and one or more fabric (xbar) modules |
install all epld epld_image parallel fan-module {all | slot_numbers } xbar-module {all | slot_numbers } |
One I/O or supervisor module |
install module slot_number epld epld_image |
One fan module |
install fan-module slot_number epld epld_image |
One fabric module |
install xbar-module slot_number epld epld_image |
When you upgrade both supervisor modules in a switch, Cisco NX-OS upgrades the EPLD images for the standby supervisor module and then upgrades the active supervisor module. This action enables the upgrade of supervisor modules to be nondisruptive to switch operations.
Note When upgrading EPLD images for Supervisor 2 or Supervisor 2E modules in a two-supervisor switch, the standby supervisor will reset twice towards the end of that upgrade but the upgrade continues to completion and the console displays the upgrade status.
When you upgrade supervisor module in a single-supervisor switch, the operation is disruptive to switch operations if the switch is active.
To start the installation of all new EPLD images for all modules in a switch, use the install all epld command as shown in either Example 8-15 (switches with Supervisor 1 modules) or Example 8-16 (switches with Supervisor 2 or Supervisor 2E modules).
Example 8-15 Installing EPLD Images in Parallel for Switches with Supervisor 1 Modules
switch# install all epld bootflash:n7000-s1-epld.6.2.8.img parallel
Example 8-16 Installing EPLD Images in Parallel for Switches with Supervisor 2 or Supervisor 2E Modules
switch# install all epld bootflash:n7000-s2-epld.6.2.8.img parallel
Example 8-17 shows how to start the installation of all new EPLD images for all of the I/O and supervisor modules and the fan-tray module in fan-tray slot 1 (in this case for a switch with Supervisor 1 modules).
Example 8-17 Installing Supervisor and I/O Modules Plus Other Specific Modules (for Switches with Supervisor 1 Modules)
switch# install all epld bootflash:n7000-s1-epld.6.2.8.img parallel module all fan-module 1
Note For Releases 6.1(1) and 6.1(2), if there are any powered down M2 Series I/O modules, use the no poweroff module command to power up that module.
switch# no poweroff module slot_number
Note For Release 4.0(2) or earlier releases, if you updated the power management EPLD image, you must reset the power for the module so that EPLD can take effect (this is not required for release 4.0(3) or later). You can reset the power in one of the following two ways: reset the power for the module (physically remove the module and reinstall it--a module reload or just pressing the ejector buttons is not sufficient for this reset requirement), or reset the entire switch (power cycle the switch).
Caution
Resetting the power disrupts any data traffic going through the affected modules. If you power cycle the entire switch, all data traffic going through the switch at the time of the power cycling is disrupted. This is not necessary for Release 4.0(3) or later releases.
Note For Release 4.0(3) and later releases, the switch automatically loads the new power management EPLD after an upgrade, so it is no longer necessary to reset the power for the module or switch.
To confirm the EPLD upgrades, see the “Verifying the EPLD Upgrades” section.
Automatic Upgrading of EPLD Images for I/O Modules
You can enable, disable, and verify automatic upgrading of EPLD images for I/O modules installed in the Cisco Nexus 7004, 7009, 7010, and 7018 switches. Also, if the upgrade is canceled because it exceeds a maximum number of programmed attempts, you can reset the process to enable the upgrades.
Note You can set automatic upgrading of EPLD images for only I/O modules, not for other modules such as the supervisor modules, fabric modules, or fan trays.
This section includes the following topics:
Enabling or Disabling Automatic Upgrades of EPLD Images
You can enable or disable automatic upgrades of EPLD images for I/O modules. When enabled, the switch checks the EPLD image versions on newly installed or powered up I/O modules to see if they are older than the images that were installed with the current version of Ciscon NX-OS software on the switch. If the images on the I/O modules are older, the switch automatically upgrades the images to the newer versions.
SUMMARY STEPS
1. configure terminal
2. system auto-upgrade epld
3. show running-config | inc epld
Note Alternatively, to prevent automatic upgrades of EPLD images for I/O modules, use the no system auto-upgrade epld command.
DETAILED STEPS
|
|
|
Step 1 |
switch# configure terminal
|
Starts the global configuration mode. |
Step 2 |
Example:
switch(config)# system auto-update epld
|
Enables automatic updates. |
no system auto-update epld
switch(config)# no system auto-update epld
|
Disables automatic updates. |
Step 3 |
show running-config | inc epld
switch(config)# sh running-config | inc epld
|
Verifies whether auto upgrades are part of the running configuration. |
Verifying Automatic Upgrades of EPLD Images
To check on the automatic upgrade status while the upgrades occur or after the upgrades, use the commands listed in Table 8-11 .
Table 8-11 Automatic EPLD Upgrade Verification Commands
|
|
show system auto epld status |
Displays the status of the ongoing automatic upgrades. |
show install auto-upgrade epld status |
Displays the current and old EPLD versions after an upgrade. |
Resetting Automatic Upgrades of EPLD Images
If the automatic upgrade function has stopped because it has exceeded the maximum number of allowed update attempts, you will see the following message:
switch# 2013 May 21 13:30:21 switch %$ VDC-1 %$_ %USER-2-SYSTEM_MSG: <<%EPLD_AUTO-2-AUTO_UPGRADE_CHECK>> Automatic EPLD upgrade check for module 15: Max retries reached. Use 'clear auto-upgrade epld flags all' to upgrade. - epld_auto
You can reset the automatic upgrade process in one of the following ways:
- Clearing the auto-upgrade epld flags for all of the I/O modules by using the clear auto-upgrade epld flags all command.
- Clearing the auto-upgrade epld flags for a specific I/O module by using the clear auto epld flags module_number command.
- Restarting the switch.
Verifying the EPLD Upgrades
You can verify the EPLD upgrades for each slot in the switch by using the commands listed in Table 8-12 .
Table 8-12 Commands Used to Display EPLD Information for Modules
|
|
show version module slot_number epld |
I/O and supervisor modules |
show version fan slot_number epld |
Fan-tray modules |
show version xbar slot_number epld |
Fabric modules |
This example shows how to verify the EPLD images for the Cisco Nexus 7018 supervisor module in slot 9:
switch# show version module 9 epld
This example shows how to verify the EPLD images for the fan-tray module in fan-tray module slot 2:
switch# show version fan 2 epld
This example shows how to verify the EPLD images for the fabric module in fabric module slot 4:
switch# show version xbar 4 epld
Displaying the Available EPLD Versions
To view the available EPLD versions, use the show version epld url command as shown in Example 8-18.
Example 8-18 Displaying the Available EPLD Versions
switch# show version epld bootflash:n7000-s1-epld.6.2.8.img
Module Type EPLD Device Version
-----------------------------------------------------------------
Supervisor-1X Power Manager 3.009
Supervisor-1X IO 3.029
Supervisor-1X Inband 1.008
Supervisor-1X Local Bus CPLD 3.000
Supervisor-1X CMP CPLD 6.000
...
10/100/1000 Mbps Eth Module Power Manager 5.006
10/100/1000 Mbps Eth Module IO 2.014
10/100/1000 Mbps Eth Module Forwarding Engine 1.006
10 Gbps Ethernet Module Power Manager 4.008
10 Gbps Ethernet Module IO 1.016
10 Gbps Ethernet Module Forwarding Engine 1.006
10 Gbps Ethernet Module FE Bridge 186.008
10 Gbps Ethernet Module Linksec Engine 2.007
1000 Mbps Optical Ethernet Module Power Manager 4.008
1000 Mbps Optical Ethernet Module IO 1.006
1000 Mbps Optical Ethernet Module Forwarding Engine 1.006
1000 Mbps Optical Ethernet Module SFP 1.004
...
Fabric Module 2 Power Manager 1.003
Fabric Module 2 Power Manager 1.003
...
Fan<Cisco Nexus 7009> Fan Controller 0.009
Fan<Cisco Nexus 7009> Fan Controller 0.009
Displaying the Status of EPLD Upgrades
To display the status of EPLD upgrades on the switch, use the show install epld status command as shown in Example 8-19.
Example 8-19 Displaying EPLD Upgrades
switch# show install epld status
1) Xbar Module 4 upgraded on Wed Oct 26 16:36:27 2011 (524778 us)
Status: EPLD Upgrade was Successful
------------------------------------------------------
Power Manager 1.003 1.003
2) Module 14 upgraded on Mon May 23 19:45:55 2011 (835895 us)
Status: EPLD Upgrade was Successful