Cisco Nexus 7000 Series Hardware Installation and Reference Guide

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

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.

– 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.

– 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.

– 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.

Supervisor Modules

The Cisco Nexus 7000 Series switch has one or two supervisor modules. The switch can use the following supervisor module types:

• Supervisor 1 (N7K-SUP1)
• Supervisor 2 (N7K-SUP2)
• Supervisor 2 Enhanced (N7K-SUP2E)

Note Supervisor 1 modules are supported by the Cisco 7009, 7010, and 7018 switches, but it is not supported by the Cisco Nexus 7004 switch. Supervisor 2 and 2E modules are supported by all Cisco Nexus 7000 Series switches.

Note If a switch has two supervisor modules, both must be the same type and have the same amount of memory in case the supervisor functions must switch over from one supervisor module to the other supervisor module.

When it has two supervisors, one supervisor is automatically active while the other is in standby mode. If the active supervisor goes down or is disconnected for replacement, the standby supervisor automatically becomes active. If you need to replace one of two installed supervisor modules with another module of the same type and amount of memory, you can do this without interrupting operations—the supervisor that you are not replacing becomes the active supervisor and retains the kickstart configuration while you replace the other supervisor. If you need to shutdown the switch to replace a supervisor module (for example, when there is only one supervisor installed in the switch or when the replacement supervisor is of another type or has a different amount of memory) you must follow the migration process explained in the “Replacing a Supervisor Module” section.

Supervisor modules are automatically powered up and started with the switch.

To understand the terms used for the supervisors, see Table 8-5 .

I/O Modules

Cisco Nexus 7000 Series switches support the following I/O modules:

• F1-Series 32-port 1- and 10-Gigabit Ethernet I/O modules (N7K-F132XP-15)1
• F2-Series 48-port 1-/10-Gigabit Ethernet I/O modules with XL (N7K-F248XP-25)
• F2-Series 48-port 1-/10-Gigabit Ethernet I/O modules with XL and enhancements (N7K-F248XP-25E)
• F3-Series 48-Port 1-/10-Gigabit Ethernet I/O modules (N7K-F348XP-25)
• F3-Series 12-Port 40-Gigabit Ethernet I/O modules (N7K-F312FQ-25)
• F3-Series 6-Port 100-Gigabit Ethernet I/O modules (N7K-F306CK-25)
• M1-Series 48-port 10/100/1000 I/O modules (N7K-M148GT-11) ¹
• M1-Series 48-port 10/100/1000 I/O modules with XL option (N7K-M148GT-11L)
• M1-Series 48-port 1-Gigabit Ethernet I/O modules (N7K-M148GS-11) ¹
• M1-Series 48-port 1-Gigabit Ethernet I/O modules with XL option (N7K-M148GS-11L)
• M1-Series 32-port 10-Gigabit Ethernet I/O modules (N7K-M132XP-12) ¹
• M1-Series 32-port 10-Gigabit Ethernet I/O modules with XL option (N7K-M132XP-12L)
• M1-Series 8-port 10-Gigabit Ethernet I/O modules with XL option(N7K-M108X2-12L)
• M2-Series 24-port 10-Gigabit Ethernet I/O modules with XL option (N7K-M224XP-23L)
• M2-Series 6-port 40-Gigabit Ethernet I/O modules with XL option (N7K-M206XP-23L)
• M2-Series 2-port 100-Gigabit Ethernet I/O modules with XL option (N7K-M202XP-23L)
• M3-Series 48-port 1- and 10-Gigabit Ethernet SFP+ I/O modules with XL option (N7K-M348XP-25L)
• M3-Series 24-port 40-Gigabit Ethernet QSFP+ I/O modules with XL option (N7K-M324FQ-25L)

Note ● M3-Series I/O modules are not compatible with Sup-1 and Fab-1 modules.

• M3-Series and F2e-Series modules cannot be in the same VDC.
• M3-Series modules cannot be combined with M1-,F1- or F2-Series modules in the same Cisco Nexus 7000 Series switch.
• Starting with Cisco NX-OS Release 8.0(1), F2-Series I/O modules and M1-Series with XL option I/O modules are not compatible with Cisco Nexus 7000 Series switches. For more information on unsupported I/O modules, refer Cisco Nexus 7000 Series Release Notes.

Fabric Modules

Cisco Nexus 7000 Series switches support up to five fabric modules in the chassis. Each chassis has its own type of fabric module as follows:

• Cisco Nexus 7009 chassis uses the Fabric 2 (N7K-C7009-FAB-2) modules.
• Cisco Nexus 7010 chassis uses the Fabric 1 (N7K-C7010-FAB-1) or Fabric 2 (N7K-C7010-FAB-2) modules.
• Cisco Nexus 7018 chassis uses the Fabric 1 (N7K-C7018-FAB-1) or Fabric 2 (N7K-C7018-FAB-2) modules.

Note The Cisco Nexus 7004 switch does not include fabric modules.

Note You can replace a Fabric 1 module with a Fabric 2 module in the Cisco Nexus 7010 and 7018 switches during operations, but while there is a mix of fabric module types, all of the fabric modules perform as Fabric 1 modules. If you power up a switch with both types of fabric modules installed, only the Fabric 2 modules will power up. To utilize the Fabric 2 module capabilities, all of the installed fabric modules must be Fabric 2 modules.

SUMMARY STEPS

1. config t

2. [no] hardware module boot-order reverse

DETAILED STEPS

SUMMARY STEPS

1. attach module slot_number

2. dir bootflash

DETAILED STEPS

You can also use the attach module command to display the standby supervisor module information, although you cannot configure the standby supervisor module using this command.

SUMMARY STEPS

1. attach console module slot_number

DETAILED STEPS

Note To exit the console mode, enter the ~, command.

Shutting Down a Supervisor

To shut down a supervisor module, use the out-of-service module command to specify the slot with that module as follows:

Shutting Down a Fabric Module

To shut down a fabric module, use either the out-of-service xbar command or the poweroff xbar command. If you use the poweroff command, the slot remains in that state until you use the no poweroff command. If you use the out-of-service command, the out-of-service state remains in effect until you do something like remove the module and replace it with another module.

Note If you are going to limit the maximum number of fabric modules (see the “Changing the Amount of Power Reserved for Fabric Modules” section), make sure that powered-on fabric modules are in the first n fabric module slots, where n is the new maximum number of fabric modules. For example, if you are limiting the maximum number of fabric modules to 4, you must make sure that the four powered-on fabric modules are in fabric slots 1 through 4.

Note If you are powering on more fabric modules than allowed by the current maximum number of fabric modules, then make sure that the fabric modules that you are powering on are installed in the first n fabric slots (slots 1 through n), power-on those modules with the no poweroff xbar command, and change the maximum number of fabric modules to n (see the “Changing the Amount of Power Reserved for Fabric Modules” section).

SUMMARY STEPS

1. config t

2. [no] poweroff xbar slot_number

Note Alternatively, you can use the out-of-service xbar slot_number command.

DETAILED STEPS

Shutting Down an I/O Module

To shut down an I/O module, use the poweroff module command to specify the slot with that module as follows:

When you are ready to power up the module, use the no poweroff module command.

SUMMARY STEPS

1. config t

2. [ no ] poweroff module slot_number

DETAILED STEPS

Overview of Module Temperatures

Built-in, automatic sensors are provided in all switches in the Cisco Nexus 7000 Series to monitor your switch at all times.

Each module (supervisor, I/O, and fabric) has temperature sensors with two thresholds:

• Minor temperature threshold—When a minor threshold is exceeded, a minor alarm occurs and the following actions occur for all four sensors:

– System messages are displayed.

– Call Home alerts are sent (if configured).

– SNMP notifications are sent (if configured).

• Major temperature threshold—When a major threshold is exceeded, a major alarm occurs and the following actions occur:

– For sensors 1, 3, and 4 (outlet and onboard sensors), the following actions occur:

System messages are displayed.

Call Home alerts are sent (if configured).

SNMP notifications are sent (if configured).

– For sensor 2 (intake sensor), the following actions occur:

If the threshold is exceeded in a switching module, only that module is shut down.

If the threshold is exceeded in an active supervisor module with HA-standby or standby present, only that supervisor module is shut down and the standby supervisor module takes over.

If you do not have a standby supervisor module in your switch, you have 2 minutes to decrease the temperature. During this interval, the software monitors the temperature every 5 seconds and continuously sends system messages as configured.

Tip We recommend that you install dual supervisor modules. If you are using a Cisco Nexus 7000 Series switch without dual supervisor modules, we recommend that you immediately replace the fan module if just one fan is not working.

Note A threshold value of –127 indicates that no thresholds are configured or applicable.

Displaying the Module Temperature

You can display temperature readings for module temperature sensors by using the show environment temperature command. See Example 8-6.

Example 8-6 Displaying Temperature Information for Hardware

Reloading the Switch

To reload the switch, use the reload command without any options. When you use this command, you reboot the switch.

Note If you need to use the reload command, be sure to save the running configuration by using the copy running-config startup-config command beforehand.

Power Cycling Modules

To power cycle any module, follow these steps:

Step 1 Identify the module that needs to be reset.

Step 2 Reset the identified module by entering the reload module command. This command power cycles the selected module.

The number indicates the slot in which the identified module resides.

SUMMARY STEPS

1. config t

2. hardware fabrics max number

DETAILED STEPS

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

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.

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

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:

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:

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.

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

Example 8-14 Determining the Amount of Available Slot0 Memory

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.

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:

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.

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).

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

Example 8-16 Installing EPLD Images in Parallel for Switches with Supervisor 2 or Supervisor 2E Modules

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)

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
• Verifying Automatic Upgrades of EPLD Images
• Resetting Automatic Upgrades of EPLD Images

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

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 .

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:

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 .

This example shows how to verify the EPLD images for the Cisco Nexus 7018 supervisor module in slot 9:

This example shows how to verify the EPLD images for the fan-tray module in fan-tray module slot 2:

This example shows how to verify the EPLD images for the fabric module in fabric module slot 4:

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

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