-
Cisco Nexus 7000 Series Hardware Installation and Reference Guide
-
Index
-
New Info for Current Release
-
Preface
-
Overview
-
Installing a Cisco Nexus 7004 Switch
-
Installing a Cisco Nexus 7009 Chassis
-
Installing a Cisco Nexus 7010 Chassis
-
Installing a Cisco Nexus 7018 Chassis
-
Installing Power Supply Units
-
Connecting the Nexus 7000 Switch to the Network
-
Managing system hardware
-
Troubleshooting
-
Replacement Procedures
-
Technical Specifications
-
Transceiver and Module Connectors
-
Cisco Nexus 7000 Series Accessory Kit Contents
-
Chassis and Module LEDs
-
Repacking the Nexus 7000 Series Switch for Shipment
-
Site Preparation and Maintenance Records
-
Feedback
Table Of Contents
Displaying the Switch Hardware Inventory
Displaying the Switch Serial Number
Displaying Power Usage Information
Power Supply Configuration Modes
Power Supply Configuration Overview
Configuring the Power Supply Mode
Power Supply Configuration Guidelines
Verifying the Status of a Module
Checking the State of a Module
Accessing an I/O Module Through the Console
Information About Module Temperature
Overview of Module Temperatures
Displaying the Module Temperature
Displaying Environment Information
Saving the Module Configuration
Purging the Module Configuration
Changing the Amount of Power Reserved for Fabric Modules
Deciding When to Upgrade EPLDs
EPLDs Available with Releases 5.0(2) through 6.1(3)
Determining Whether to Upgrade EPLDs
Preparing the EPLD Images for Installation
Displaying the Available EPLD Versions
Displaying the Status of EPLD Upgrades
Managing the Switch Hardware
This chapter describes how to manage the switch hardware, which includes the fabric and I/O modules, and it provides information on how to monitor system and module states. This chapter includes the following sections:
•
Displaying the Switch Hardware Inventory
•
•
•
•
•
•
•
•
•
•
•
Displaying the Switch Hardware Inventory
You can display information about the field replaceable units (FRUs), including product IDs, serial numbers, and version IDs by entering the show inventory command. See Example 8-1.
Example 8-1 Displaying the Hardware Inventory
switch# show inventorypsconfigs# sh inventoryNAME: "Chassis", DESCR: "Nexus7000 C7009 (9 Slot) Chassis "PID: N7K-C7009 , VID: V01 , SN: JAF1437APPDNAME: "Slot 1", DESCR: "Supervisor module-1X"PID: N7K-SUP-1 , VID: V09 , SN: JAF1414AQFDNAME: "Slot 2", DESCR: "Supervisor module-1X"PID: N7K-SUP-1 , VID: V03 , SN: JAF1240AHNHNAME: "Slot 3", DESCR: "10/100/1000 Mbps Ethernet Module"PID: N7K-M148GT-11 , VID: V01 , SN: JAB115000NJNAME: "Slot 4", DESCR: "10 Gbps Ethernet Module"PID: N7K-M132XP-12 , VID: V01 , SN: JAB1152010ANAME: "Slot 5", DESCR: "10/100/1000 Mbps Ethernet XL Module"PID: N7K-M148GT-11L , VID: 0 , SN: JAF1416ABPMNAME: "Slot 6", DESCR: "10 Gbps Ethernet XL Module"PID: N7K-M108X2-12L , VID: 0 , SN: JAF1333AAJRNAME: "Slot 7", DESCR: "1000 Mbps Optical Ethernet Module"PID: N7K-M148GS-11 , VID: V02 , SN: JAF1409APRBNAME: "Slot 8", DESCR: "1/10 Gbps Ethernet Module"PID: N7K-F132XP-15 , VID: V01 , SN: JAF1424CFJRNAME: "Slot 9", DESCR: "1/10 Gbps Ethernet Module"PID: N7K-F132XP-15 , VID: V01 , SN: JAF1321ANHPNAME: "Slot 10", DESCR: "Fabric card module"PID: N7K-C7009-FAB-2 , VID: V01 , SN: JAF1448ARHJNAME: "Slot 11", DESCR: "Fabric card module"PID: N7K-C7009-FAB-2 , VID: V01 , SN: JAF1451BSSFNAME: "Slot 12", DESCR: "Fabric card module"PID: N7K-C7009-FAB-2 , VID: V01 , SN: JAF1448ARHQNAME: "Slot 13", DESCR: "Fabric card module"PID: N7K-C7009-FAB-2 , VID: V01 , SN: JAF1509BHBENAME: "Slot 14", DESCR: "Fabric card module"PID: N7K-C7009-FAB-2 , VID: V01 , SN: JAF1509BHCBNAME: "Slot 33", DESCR: "Nexus7000 C7009 (9 Slot) Chassis Power Supply"PID: N7K-AC-6.0KW , VID: V01 , SN: DTM141600XTNAME: "Slot 34", DESCR: "Nexus7000 C7009 (9 Slot) Chassis Power Supply"PID: N7K-AC-6.0KW , VID: V01 , SN: DTM1414007TNAME: "Slot 35", DESCR: "Nexus7000 C7009 (9 Slot) Chassis Fan Module"PID: N7K-C7009-FAN , VID: V00 , SN: JAF1433DDEJswitch#To display switch hardware inventory details, enter the show hardware command. See Example 8-2.
Example 8-2 Displaying Hardware Information
switch# show hardwareCisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpSoftwareBIOS: version 3.19.0loader: version N/Akickstart: version 5.0(2)system: version 5.0(2)BIOS compile time: 03/31/09kickstart image file is: bootflash:/n7000-s1-kickstart.5.0.2.bin.S19kickstart compile time: 12/25/2020 12:00:00 [03/04/2010 19:45:32]system image file is: bootflash:/n7000-s1-dk9.5.0.2.bin.S19system compile time: 2/7/2010 3:00:00 [03/04/2010 20:32:24]Hardwarecisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X")Intel(R) Xeon(R) CPU with 4135780 kB of memory.Processor Board ID JAF1309AECNDevice name: psconfigsbootflash: 2000880 kBslot0: 2075246 kB (expansion flash)Kernel uptime is 0 day(s), 1 hour(s), 5 minute(s), 53 second(s)Last reset at 65404 usecs after Fri Dec 12 19:34:13 2008Reason: Reset Requested by CLI command reloadSystem version: 5.0(2)Service:pluginCore Plugin, Ethernet PluginCMP (Module 5) okHardwareFreescale Inc mpc8343 (rev 3.1 (pvr 8083 0031)) CPU with 128 MB of memoryModel number is N7K-SUP1H/W Version is 1.2Part Number is 73-10877-11Part Revision is A1Serial number is JAF1309AECNCLEI code is COUCAHLCAAMAC address is 00-24-98-e8-20-00CMP (Module 6) okHardwareFreescale Inc mpc8343 (rev 3.1 (pvr 8083 0031)) CPU with 128 MB of memoryModel number is N7K-SUP1H/W Version is 1.2Part Number is 73-10877-11Part Revision is A1Serial number is JAF1309AEFECLEI code is COUCAHLCAAMAC address is 00-24-98-6f-37-92--------------------------------Switch hardware ID information--------------------------------Switch is booted upSwitch type is : Nexus7000 C7010 (10 Slot) ChassisModel number is N7K-C7010H/W version is 1.1Part Number is 73-10900-04Part Revision is B0Manufacture Date is Year 13 Week 10Serial number is JAF13100003CLEI code is IPMKA00ARA--------------------------------Chassis has 10 Module slots and 5 Fabric slots--------------------------------Module1 emptyModule2 okModule type is : 10/100/1000 Mbps Ethernet Module1 submodules are presentModel number is N7K-M148GT-11H/W version is 1.3Part Number is 73-10098-12Part Revision is A0Manufacture Date is Year 13 Week 6Serial number is JAF1306AAFPCLEI code is COUIAW3CAAModule3 okModule type is : 10/100/1000 Mbps Ethernet Module1 submodules are presentModel number is N7K-M148GT-11H/W version is 1.3Part Number is 73-10098-12Part Revision is A0Manufacture Date is Year 13 Week 3Serial number is JAF1303ACPBCLEI code is COUIAW3CAAModule4 okModule type is : 10/100/1000 Mbps Ethernet Module1 submodules are presentModel number is N7K-M148GT-11H/W version is 1.3Part Number is 73-10098-12Part Revision is A0Manufacture Date is Year 13 Week 9Serial number is JAF1309ABLECLEI code is COUIAW3CAAModule5 okModule type is : Supervisor module-1X0 submodules are presentModel number is N7K-SUP1H/W version is 1.2Part Number is 73-10877-11Part Revision is A1Manufacture Date is Year 13 Week 9Serial number is JAF1309AECNCLEI code is COUCAHLCAAModule6 okModule type is : Supervisor module-1X0 submodules are presentModel number is N7K-SUP1H/W version is 1.2Part Number is 73-10877-11Part Revision is A1Manufacture Date is Year 13 Week 9Serial number is JAF1309AEFECLEI code is COUCAHLCAAModule7 okModule type is : 10 Gbps Ethernet Module2 submodules are presentModel number is N7K-M132XP-12H/W version is 1.5Part Number is 73-10899-09Part Revision is B1Manufacture Date is Year 13 Week 7Serial number is JAF1307ALCBCLEI code is COUIAWGCAAModule8 emptyModule9 okModule type is : 1000 Mbps Optical Ethernet Module1 submodules are presentModel number is N7K-M148GS-11H/W version is 1.2Part Number is 73-11584-05Part Revision is A0Manufacture Date is Year 13 Week 11Serial number is JAF1311AEMMCLEI code is COUIAV0CABModule10 emptyXbar1 okModule type is : Fabric card module0 submodules are presentModel number is N7K-C7010-FAB-1H/W version is 1.0Part Number is 73-10624-04Part Revision is C0Manufacture Date is Year 13 Week 9Serial number is JAF1309ACAPCLEI code is COUCAGVCAAXbar2 okModule type is : Fabric card module0 submodules are presentModel number is N7K-C7010-FAB-1H/W version is 1.0Part Number is 73-10624-04Part Revision is C0Manufacture Date is Year 13 Week 9Serial number is JAF1309AAHBCLEI code is COUCAGVCAAXbar3 okModule type is : Fabric card module0 submodules are presentModel number is N7K-C7010-FAB-1H/W version is 1.0Part Number is 73-10624-04Part Revision is C0Manufacture Date is Year 13 Week 6Serial number is JAF1306ANJJCLEI code is COUCAGVCAAXbar4 okModule type is : Fabric card module0 submodules are presentModel number is N7K-C7010-FAB-1H/W version is 1.0Part Number is 73-10624-04Part Revision is C0Manufacture Date is Year 13 Week 9Serial number is JAF1309ACATCLEI code is COUCAGVCAAXbar5 okModule type is : Fabric card module0 submodules are presentModel number is N7K-C7010-FAB-1H/W version is 1.0Part Number is 73-10624-04Part Revision is C0Manufacture Date is Year 13 Week 6Serial number is JAF1306ANKFCLEI code is COUCAGVCAA---------------------------------------Chassis has 3 PowerSupply Slots---------------------------------------PS1 okPower supply type is: 6000.00W 220v ACModel number is N7K-AC-6.0KWH/W version is 1.0Part Number is 341-0230-02Part Revision is A0Manufacture Date is Year 12 Week 16Serial number is DTH1216T020CLEI code is IPUPADBAAAPS2 okPower supply type is: 6000.00W 220v ACModel number is N7K-AC-6.0KWH/W version is 1.0Part Number is 341-0230-02Part Revision is A0Manufacture Date is Year 12 Week 17Serial number is DTH1217T029CLEI code is IPUPADBAAAPS3 okPower supply type is: 6000.00W 220v ACModel number is N7K-AC-6.0KWH/W version is 1.0Part Number is 341-0230-02Part Revision is A0Manufacture Date is Year 12 Week 15Serial number is DTH1215T139CLEI code is IPUPADBAAA----------------------------------Chassis has 4 Fan slots----------------------------------Fan1(sys_fan1) okModel number is N7K-C7010-FAN-SH/W version is 1.1Part Number is 73-10741-04Part Revision is B0Manufacture Date is Year 13 Week 3Serial number is FOX1303XABCCLEI code is COM8210ARAFan2(sys_fan2) okModel number is N7K-C7010-FAN-SH/W version is 1.1Part Number is 73-10741-04Part Revision is B0Manufacture Date is Year 13 Week 6Serial number is FOX1306X03UCLEI code is COM8210ARAFan3(fab_fan1) okModel number is N7K-C7010-FAN-FH/W version is 1.1Part Number is 73-10967-02Part Revision is B0Manufacture Date is Year 12 Week 41Serial number is FOX1241XA6QCLEI code is IPEQABAEAAFan4(fab_fan2) okModel number is N7K-C7010-FAN-FH/W version is 1.1Part Number is 73-10967-02Part Revision is B0Manufacture Date is Year 12 Week 41Serial number is FOX1241XA7UCLEI code is IPEQABAEAAswitch#Displaying the Switch Serial Number
The serial number of your Cisco Nexus 7000 Series switch can be obtained by looking at the serial number label on the back of the switch (next to the power supply), or by entering the show sprom backplane 1 command. See Example 8-3.
Example 8-3 Displaying the Switch Serial Number
switch# show sprom backplane 1DISPLAY backplane sprom contents:Common block:Block Signature : 0xababBlock Version : 3Block Length : 160Block Checksum : 0x13bdEEPROM Size : 65535Block Count : 5FRU Major Type : 0x6001FRU Minor Type : 0x0OEM String : Cisco Systems, Inc.Product Number : N7K-C7010Serial Number : TBM11493268Part Number : 73-10900-04Part Revision : 06Mfg Deviation : 0H/W Version : 0.406Mfg Bits : 0Engineer Use : 0snmpOID : 0.0.0.0.0.0.0.0Power Consump : 0RMA Code : 0-0-0-0CLEI Code : 0VID : V01Chassis specific block:Block Signature : 0x6001Block Version : 3Block Length : 39Block Checksum : 0x268Feature Bits : 0x0HW Changes Bits : 0x0Stackmib OID : 0MAC Addresses : 00-1b-54-c2-1e-00Number of MACs : 128OEM Enterprise : 9OEM MIB Offset : 5MAX Connector Power: 0WWN software-module specific block:Block Signature : 0x6005Block Version : 1Block Length : 0Block Checksum : 0x66wwn usage bits:00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00License software-module specific block:Block Signature : 0x6006Block Version : 1Block Length : 16Block Checksum : 0x77lic usage bits:00 00 00 00 00 00 00 00Second Serial number specific block:Block Signature : 0x6007Block Version : 1Block Length : 28Block Checksum : 0x312Serial Number : TBM11476798switch#Displaying Power Usage Information
To display the actual power usage information for the entire switch, use the show environment power command. See Example 8-4. This command shows the power usage for many of the modules in the switch. For the older modules that do not have the capability to output this information, the output is shown as N/A.
Note
Example 8-4 Displaying Power Management Information
switch# show environment powerPower Supply:Power Supply:Voltage: 50 VoltsPower Actual TotalSupply Model Output Capacity Status(Watts ) (Watts )------- ------------------- ----------- ----------- --------------1 N7K-AC-6.0KW 812 W 6000 W Ok2 N7K-AC-6.0KW 704 W 6000 W Ok3 N7K-AC-6.0KW 727 W 6000 W OkActual PowerModule Model Draw Allocated Status(Watts ) (Watts )------- ------------------- ----------- ----------- --------------2 N7K-M148GT-11 N/A 400 W Powered-Up3 N7K-M148GT-11 N/A 400 W Powered-Up4 N7K-M148GT-11 N/A 400 W Powered-Up5 N7K-SUP1 N/A 210 W Powered-Up6 N7K-SUP1 N/A 210 W Powered-Up7 N7K-M132XP-12 N/A 750 W Powered-Up9 N7K-M148GS-11 284 W 400 W Powered-UpXb1 N7K-C7010-FAB-1 N/A 60 W Powered-UpXb2 N7K-C7010-FAB-1 N/A 60 W Powered-UpXb3 N7K-C7010-FAB-1 N/A 60 W Powered-UpXb4 N7K-C7010-FAB-1 N/A 60 W Powered-UpXb5 N7K-C7010-FAB-1 N/A 60 W Powered-Upfan1 N7K-C7010-FAN-S 76 W 720 W Powered-Upfan2 N7K-C7010-FAN-S 76 W 720 W Powered-Upfan3 N7K-C7010-FAN-F 8 W 120 W Powered-Upfan4 N7K-C7010-FAN-F 8 W 120 W Powered-UpN/A - Per module power not availablePower Usage Summary:--------------------Power Supply redundancy mode (configured) RedundantPower Supply redundancy mode (operational) RedundantTotal Power Capacity (based on configured mode) 9000 WTotal Power of all Inputs (cumulative) 18000 WTotal Power Output (actual draw) 2243 WTotal Power Allocated (budget) 4750 WTotal Power Available for additional modules 4250 Wswitch#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:
•
•
•
•
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:
•
•
•
•
•
Configuring the Power Supply Mode
You can configure the power supply mode.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Note
Power Supply Configuration Guidelines
Follow these guidelines when configuring power supply units:
•
–
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.
–
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.
–
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.
–
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.
Information About Modules
The following sections explain how you can manage operations for the switch modules:
Supervisor Modules
The Cisco Nexus 7000 Series switch has one or two supervisor modules. The switch can use the following supervisor module types:
•
•
•
Note
Note
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:
•
•
•
•
•
•
•
•
•
•
•
•
•
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:
•
•
•
Note
Note
Verifying the Status of a Module
Before you begin configuring the switch, you need to ensure that the modules in the chassis are functioning as designed. To verify the status of all modules, enter the show module command. To verify the status of a supervisor or I/O module, enter the show module slot_number command. To verify the status of a fabric module, enter the show module xbar slot_number command. The interfaces in each module are ready to be configured when the ok status is displayed in the show module command output. See Example 8-5.
Example 8-5 Displaying Module Information
switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------2 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok3 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok4 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok5 0 Supervisor module-1X N7K-SUP1 active *6 0 Supervisor module-1X N7K-SUP1 ha-standby7 32 10 Gbps Ethernet Module N7K-M132XP-12 ok9 48 1000 Mbps Optical Ethernet Modul N7K-M148GS-11 okMod Sw Hw--- -------------- ------2 5.0(2) 1.33 5.0(2) 1.34 5.0(2) 1.35 5.0(2) 1.26 5.0(2) 1.27 5.0(2) 1.59 5.0(2) 1.2Mod MAC-Address(es) Serial-Num--- -------------------------------------- ----------2 00-24-98-e9-14-58 to 00-24-98-e9-14-8c JAF1306AAFP3 00-24-98-e8-28-84 to 00-24-98-e8-28-b8 JAF1303ACPB4 00-24-f7-1c-85-b0 to 00-24-f7-1c-85-e4 JAF1309ABLE5 00-24-98-6f-95-00 to 00-24-98-6f-95-08 JAF1309AECN6 00-24-f7-18-92-88 to 00-24-f7-18-92-90 JAF1309AEFE7 00-24-98-e9-29-60 to 00-24-98-e9-29-84 JAF1307ALCB9 00-24-f7-1c-d5-50 to 00-24-f7-1c-d5-84 JAF1311AEMMMod Online Diag Status--- ------------------2 Pass3 Pass4 Pass5 Pass6 Pass7 Pass9 Pass...switch#The Status column in the output should display an ok status for switching modules and an active or standby (or HA-standby) status for supervisor modules. If the status is either ok or active, you can continue with your configuration.
Note
For information about the states through which a switching module progresses, see the "Checking the State of a Module" section.
Checking the State of a Module
If your chassis has more than one I/O module, you can check the progress by repeatedly using the show module command and viewing the Status column each time.
The I/O module goes through a testing and an initializing stage before displaying an ok status. Table 8-6 describes the possible states in which a module can exist.
Connecting to a Module
At any time, you can connect to any module by using the attach module command. Once you are at the module prompt, you can obtain further details about the module by using module-specific commands in EXEC mode.
SUMMARY STEPS
1.
2.
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.
Accessing an I/O Module Through the Console
You can troubleshoot bootup problems for an I/O module by accessing the module through its console port. This action establishes a console mode that you must exit in order to use other Cisco NX-OS commands.
To attach to the console port for an I/O module, use the attach console module command to specify the module you need to work with. You can specify a slot number of 1 to 8 or 11 to 18.
SUMMARY STEPS
1.
DETAILED STEPS
Note
Shutting Down Modules
This section includes the following topics:
•
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:
switch# out-of-service module slotShutting 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
Note
SUMMARY STEPS
1.
2.
Note
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:
switch# poweroff module slotWhen you are ready to power up the module, use the no poweroff module command.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Information About Module Temperature
This section includes the following topics:
•
•
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:
•
–
–
–
•
–
System messages are displayed.
Call Home alerts are sent (if configured).
SNMP notifications are sent (if configured).
–
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
Note
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
switch# show environment temperatureTemperature:--------------------------------------------------------------------Module Sensor MajorThresh MinorThres CurTemp Status(Celsius) (Celsius) (Celsius)--------------------------------------------------------------------1 Crossbar(s5) 105 95 60 Ok1 QEng1Sn1(s12) 115 110 70 Ok1 QEng1Sn2(s13) 115 110 68 Ok1 QEng1Sn3(s14) 115 110 67 Ok1 QEng1Sn4(s15) 115 110 68 Ok1 QEng2Sn1(s16) 115 110 70 Ok1 QEng2Sn2(s17) 115 110 68 Ok1 QEng2Sn3(s18) 115 110 68 Ok1 QEng2Sn4(s19) 115 110 68 Ok1 L2Lookup(s27) 115 105 57 Ok1 L3Lookup(s28) 120 110 62 Ok2 Crossbar(s5) 105 95 65 Ok2 QEng1Sn1(s12) 115 110 70 Ok2 QEng1Sn2(s13) 115 110 68 Ok2 QEng1Sn3(s14) 115 110 67 Ok2 QEng1Sn4(s15) 115 110 68 Ok2 QEng2Sn1(s16) 115 110 69 Ok2 QEng2Sn2(s17) 115 110 68 Ok2 QEng2Sn3(s18) 115 110 67 Ok2 QEng2Sn4(s19) 115 110 68 Ok2 L2Lookup(s27) 115 105 56 Ok2 L3Lookup(s28) 120 110 63 Ok5 Outlet1 (s1) 125 125 49 Ok5 Outlet2 (s2) 125 125 37 Ok5 Intake (s3) 60 42 32 Ok5 EOBC_MAC(s4) 105 95 43 Ok5 CPU (s5) 105 95 40 Ok5 Crossbar(s6) 105 95 61 Ok5 Arbiter (s7) 110 100 67 Ok5 CTSdev1 (s8) 115 105 43 Ok5 InbFPGA (s9) 105 95 44 Ok5 QEng1Sn1(s10) 115 105 60 Ok5 QEng1Sn2(s11) 115 105 59 Ok5 QEng1Sn3(s12) 115 105 56 Ok5 QEng1Sn4(s13) 115 105 57 Okxbar-1 Outlet (s1) 125 125 38 Okxbar-1 Intake (s2) 60 42 32 Okxbar-1 Crossbar(s3) 105 95 56 Okxbar-2 Outlet (s1) 125 125 39 Okxbar-2 Intake (s2) 62 42 31 Okxbar-2 Crossbar(s3) 105 95 56 Okswitch#Displaying Environment Information
You can display all of the environment-related switch information by using the show environment command. See Example 8-7.
Example 8-7 Displaying All Environmental Information
switch# show environmentClock:----------------------------------------------------------Clock Model Hw Status----------------------------------------------------------A Clock Module -- NotSupported/NoneB Clock Module -- NotSupported/NoneFan:------------------------------------------------------Fan Model Hw Status------------------------------------------------------Fan1(sys_fan1) N7K-C7010-FAN-S 1.1 OkFan2(sys_fan2) N7K-C7010-FAN-S 1.1 OkFan3(fab_fan1) N7K-C7010-FAN-F 1.1 OkFan4(fab_fan2) N7K-C7010-FAN-F 1.1 OkFan_in_PS1 -- -- OkFan_in_PS2 -- -- OkFan_in_PS3 -- -- OkFan Air Filter : AbsentTemperature:--------------------------------------------------------------------Module Sensor MajorThresh MinorThres CurTemp Status(Celsius) (Celsius) (Celsius)--------------------------------------------------------------------2 Crossbar(s5) 105 95 43 Ok2 CTSdev4 (s9) 115 105 58 Ok2 CTSdev5 (s10) 115 105 56 Ok2 CTSdev7 (s12) 115 105 53 Ok2 CTSdev9 (s14) 115 105 51 Ok2 CTSdev10(s15) 115 105 50 Ok2 CTSdev11(s16) 115 105 48 Ok2 CTSdev12(s17) 115 105 47 Ok2 QEng1Sn1(s18) 115 105 49 Ok2 QEng1Sn2(s19) 115 105 46 Ok2 QEng1Sn3(s20) 115 105 44 Ok2 QEng1Sn4(s21) 115 105 45 Ok2 L2Lookup(s22) 120 110 44 Ok2 L3Lookup(s23) 120 110 52 Ok3 Crossbar(s5) 105 95 43 Ok3 CTSdev4 (s9) 115 105 56 Ok3 CTSdev5 (s10) 115 105 54 Ok3 CTSdev7 (s12) 115 105 53 Ok3 CTSdev9 (s14) 115 105 50 Ok3 CTSdev10(s15) 115 105 49 Ok3 CTSdev11(s16) 115 105 47 Ok3 CTSdev12(s17) 115 105 46 Ok3 QEng1Sn1(s18) 115 105 47 Ok3 QEng1Sn2(s19) 115 105 45 Ok3 QEng1Sn3(s20) 115 105 44 Ok3 QEng1Sn4(s21) 115 105 43 Ok3 L2Lookup(s22) 120 110 44 Ok3 L3Lookup(s23) 120 110 50 Ok4 Crossbar(s5) 105 95 44 Ok4 CTSdev4 (s9) 115 105 56 Ok4 CTSdev5 (s10) 115 105 54 Ok4 CTSdev7 (s12) 115 105 54 Ok4 CTSdev9 (s14) 115 105 51 Ok4 CTSdev10(s15) 115 105 51 Ok4 CTSdev11(s16) 115 105 48 Ok4 CTSdev12(s17) 115 105 47 Ok4 QEng1Sn1(s18) 115 105 49 Ok4 QEng1Sn2(s19) 115 105 48 Ok4 QEng1Sn3(s20) 115 105 47 Ok4 QEng1Sn4(s21) 115 105 46 Ok4 L2Lookup(s22) 120 110 45 Ok4 L3Lookup(s23) 120 110 52 Ok5 Intake (s3) 60 42 23 Ok5 EOBC_MAC(s4) 105 95 44 Ok5 CPU (s5) 105 95 36 Ok5 Crossbar(s6) 105 95 47 Ok5 Arbiter (s7) 110 100 54 Ok5 CTSdev1 (s8) 115 105 46 Ok5 InbFPGA (s9) 105 95 41 Ok5 QEng1Sn1(s10) 115 105 48 Ok5 QEng1Sn2(s11) 115 105 47 Ok5 QEng1Sn3(s12) 115 105 44 Ok5 QEng1Sn4(s13) 115 105 45 Ok6 Intake (s3) 60 42 24 Ok6 EOBC_MAC(s4) 105 95 47 Ok6 CPU (s5) 105 95 37 Ok6 Crossbar(s6) 105 95 48 Ok6 Arbiter (s7) 110 100 54 Ok6 CTSdev1 (s8) 115 105 47 Ok6 InbFPGA (s9) 105 95 44 Ok6 QEng1Sn1(s10) 115 105 50 Ok6 QEng1Sn2(s11) 115 105 48 Ok6 QEng1Sn3(s12) 115 105 46 Ok6 QEng1Sn4(s13) 115 105 49 Ok7 Crossbar(s5) 105 95 58 Ok7 QEng1Sn1(s12) 115 110 66 Ok7 QEng1Sn2(s13) 115 110 63 Ok7 QEng1Sn3(s14) 115 110 62 Ok7 QEng1Sn4(s15) 115 110 62 Ok7 QEng2Sn1(s16) 115 110 66 Ok7 QEng2Sn2(s17) 115 110 63 Ok7 QEng2Sn3(s18) 115 110 63 Ok7 QEng2Sn4(s19) 115 110 63 Ok7 L2Lookup(s27) 115 105 51 Ok7 L3Lookup(s28) 120 110 61 Ok9 Crossbar(s5) 105 95 43 Ok9 CTSdev1 (s6) 115 105 53 Ok9 CTSdev3 (s8) 115 105 53 Ok9 CTSdev4 (s9) 115 105 56 Ok9 CTSdev5 (s10) 115 105 53 Ok9 CTSdev6 (s11) 115 105 57 Ok9 CTSdev7 (s12) 115 105 52 Ok9 CTSdev9 (s14) 115 105 50 Ok9 CTSdev10(s15) 115 105 53 Ok9 CTSdev11(s16) 115 105 50 Ok9 CTSdev12(s17) 115 105 53 Ok9 QEng1Sn1(s18) 115 105 55 Ok9 QEng1Sn2(s19) 115 105 54 Ok9 QEng1Sn3(s20) 115 105 52 Ok9 QEng1Sn4(s21) 115 105 51 Ok9 L2Lookup(s22) 120 110 52 Ok9 L3Lookup(s23) 120 110 60 Okxbar-1 Intake (s2) 60 42 27 Okxbar-1 Crossbar(s3) 105 95 59 Okxbar-2 Intake (s2) 60 42 26 Okxbar-2 Crossbar(s3) 105 95 50 Okxbar-3 Intake (s2) 60 42 26 Okxbar-3 Crossbar(s3) 105 95 54 Okxbar-4 Intake (s2) 60 42 26 Okxbar-4 Crossbar(s3) 105 95 53 Okxbar-5 Intake (s2) 60 42 26 Okxbar-5 Crossbar(s3) 105 95 55 OkPower Supply:Voltage: 50 VoltsPower Actual TotalSupply Model Output Capacity Status(Watts ) (Watts )------- ------------------- ----------- ----------- --------------1 N7K-AC-6.0KW 816 W 6000 W Ok2 N7K-AC-6.0KW 713 W 6000 W Ok3 N7K-AC-6.0KW 730 W 6000 W OkActual PowerModule Model Draw Allocated Status(Watts ) (Watts )------- ------------------- ----------- ----------- --------------2 N7K-M148GT-11 N/A 400 W Powered-Up3 N7K-M148GT-11 N/A 400 W Powered-Up4 N7K-M148GT-11 N/A 400 W Powered-Up5 N7K-SUP1 N/A 210 W Powered-Up6 N7K-SUP1 N/A 210 W Powered-Up7 N7K-M132XP-12 N/A 750 W Powered-Up9 N7K-M148GS-11 283 W 400 W Powered-UpXb1 N7K-C7010-FAB-1 N/A 60 W Powered-UpXb2 N7K-C7010-FAB-1 N/A 60 W Powered-UpXb3 N7K-C7010-FAB-1 N/A 60 W Powered-UpXb4 N7K-C7010-FAB-1 N/A 60 W Powered-UpXb5 N7K-C7010-FAB-1 N/A 60 W Powered-Upfan1 N7K-C7010-FAN-S 88 W 720 W Powered-Upfan2 N7K-C7010-FAN-S 88 W 720 W Powered-Upfan3 N7K-C7010-FAN-F 9 W 120 W Powered-Upfan4 N7K-C7010-FAN-F 9 W 120 W Powered-UpN/A - Per module power not availablePower Usage Summary:--------------------Power Supply redundancy mode (configured) RedundantPower Supply redundancy mode (operational) RedundantTotal Power Capacity (based on configured mode) 9000 WTotal Power of all Inputs (cumulative) 18000 WTotal Power Output (actual draw) 2259 WTotal Power Allocated (budget) 4750 WTotal Power Available for additional modules 4250 Wswitch#Reloading Modules
You can reload the entire switch, reset specific modules in the switch, or reload the image on specific modules in the switch.
This section includes the following topics:
Reloading the Switch
To reload the switch, use the reload command without any options. When you use this command, you reboot the switch.
Note
Power Cycling Modules
To power cycle any module, follow these steps:
Step 1
Step 2
switch# reload module numberThe number indicates the slot in which the identified module resides.
Caution
Saving the Module Configuration
To save the new configuration to nonvolatile storage, use the copy running-config startup-config command from EXEC mode. Once you enter this command, the running and the startup copies of the configuration are identical.
Table 8-7 displays various scenarios when module configurations are preserved or lost.
.
Purging the Module Configuration
To delete the configuration in an empty slot or in a slot with a powered-down I/O module, use the purge module slot running-config command from EXEC mode. This command clears the running configuration for the specified slot. This command does not work on supervisor modules or on any slot that currently has a powered-up module. This command only works on an empty slot (where the specified module once resided) or on a slot with a powered-down I/O module.
The purge module command clears the configuration for any module that previously existed in a slot and has since been removed or powered down. While the module was in that slot, some parts of the configuration may have been stored in the running configuration and cannot be reused (for example, IP addresses), unless you clear that from the running configuration.
For example, suppose you create an IP storage configuration with a 48-port 10/100/1000 Ethernet I/O module in slot 3 in Switch A. This module uses an IP address. You decide to remove this I/O module and move it to Switch B, and you no longer need the IP address. If you try to configure this unused IP address, you will receive an error message that prevents you from proceeding with the configuration. In this case, you need to enter the purge module 3 running-config command to clear the old configuration in Switch A before using the IP address.
Changing the Amount of Power Reserved for Fabric Modules
By default, each Cisco Nexus 7000 Series system reserves enough power for the maximum quantity (five) of fabric modules that can be installed in its chassis. If you have installed fewer than five fabric modules and need to free up unused reserve power for I/O modules, you can power down the unused slots and specify a smaller maximum number of fabric modules.
Before you can change the maximum number of fabric modules, you must do all of the following:
•
You do not have to fill all of those slots with fabric modules, but the fabric modules that you will be using must be in those slots. For example, if you specify 4 as the new maximum number of fabric modules, you must make sure that the fabric modules that you are using are in slots 1 through 4. Also make sure that any empty fabric module slots have blank modules installed in them.
•
•
To specify a different maximum number of fabric modules for your system, use the hardware fabrics max number command. To verify the status of the installed fabric modules, use the show module xbar command (see the "Verifying the Status of a Module" section). To verify the amount of reserved power, use the show environment power command (see the "Displaying Power Usage Information" section).
SUMMARY STEPS
1.
2.
DETAILED STEPS
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:
•
•
–
–
–
–
Note
Tip
The fan status is continuously monitored by the software. In case of a fan failure, the following actions occur:
•
•
•
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 fanFan:-------------------------------------------------------Fan Model Hw Status-------------------------------------------------------Fan1(sys_fan1) N7K-C7004-FAN 0.110 OkFan_in_PS1 -- -- OkFan_in_PS2 -- -- OkFan_in_PS3 -- -- AbsentFan_in_PS4 -- -- AbsentFan Zone Speed: Zone 1: 0x7fFan Air Filter : AbsentExample 8-9 Displaying Fan Information for a Cisco Nexus 7009 Series Chassis
switch# show environment fanFan:----------------------------------------------Fan Model Hw Status----------------------------------------------Fan1(sys_fan1) N7K-C700-FAN 0.31 OkFan_in_PS1 -- -- OkFan_in_PS2 -- -- OkFan Air Filter:Absentswitch#Example 8-10 Displaying Fan Information for a Cisco Nexus 7010 Series Chassis
switch# show environment fanFan:------------------------------------------------------Fan Model Hw Status------------------------------------------------------ChassisFan1 N7K-C7010-FAN-S 0.410 OkChassisFan2 N7K-C7010-FAN-S 0.410 OkChassisFan3 N7K-C7010-FAN-F 0.209 OkChassisFan4 N7K-C7010-FAN-F 0.209 OkFan_in_PS1 -- -- OkFan_in_PS2 -- -- OkFan_in_PS3 -- -- OkFan Air Filter : Absentswitch#Example 8-11 Displaying Fan Information for a Cisco Nexus 7018 Series Chassis
switch# show environment fanFan:------------------------------------------------------Fan Model Hw Status------------------------------------------------------Fan1(sys_fan1) N7K-C7018-FAN 0.204 OkFan2(sys_fan2) N7K-C7018-FAN 0.204 OkFan_in_PS1 -- -- OkFan_in_PS2 -- -- OkFan_in_PS3 -- -- AbsentFan_in_PS4 -- -- AbsentFan Air Filter : Absentswitch#The possible Status field values are as follows:
•
•
•
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:
•
–
–
•
–
–
Configuring EPLDs
The Cisco Nexus 7000 Series 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
Although Cisco provides EPLD images with each release, it is rare that these images are updates to the images included with past releases. To determine whether the images used for your hardware components have been updated for the current or past releases, see Table 8-9. 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:
•
•
•
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
Note
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:
•
•
Table 8-8 Conditions For Upgrading EPLD Images
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:
•
•
•
•
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
1 We recommend (not mandatory) that you upgrade the EPLD images for the supervisor, I/O, and fabric modules.
Switch Requirements
The Cisco Nexus 7000 Series switch must be running the Cisco NX-OS operating system and include the following hardware:
•
•
•
•
•
•
•
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.
EPLDs Available with Releases 5.0(2) through 6.1(3)
Each EPLD image that you can download from http://www.cisco.com is a bundle of EPLD upgrades. To see the updated EPLD versions for each release, see Table 8-9.
Note
Table 8-9 EPLD Upgrades for Cisco NX-OS Releases
Supervisor 1 module (N7K-SUP1)
Power Manager
IO
INBAND
Local Bus and CPLD
CMP CPLDAll
All
All
All
All3.009
3.028
1.008
3.000
6.000—
—
—
—
——
—
—
—
——
—
—
—
——
—
—
—
——
—
—
—
——
3.029
—
—
——
—
—
—
——
—
—
—
—Supervisor 2 and 2E modules
(N7K-SUP2 and N7K-SUP2E)Power Manager
IOAll
AllN/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A134.000
1.012—
1.013—
—F1 Series 32-port, 1- and 10-Gigabit Ethernet I/O module
(N7K-F132XP-15)Power Manager
IOAll
AllN/A1
N/A1N/A1
N/A11.000
0.045—
—1.001
——
——
——
——
—F2 Series 48-port, 1- and 10-Gigabit Ethernet I/O modules
(N7K-F248XP-25)Power Manager
IOAll
AllN/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A11.006
0.006—
——
——
—F2 Series 48-port, 1- and 10-Gigabit Ethernet I/O modules (enhanced)
(N7K-F248XP-25E)Power Manager
IOAll
AllN/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A11.006
0.001—
—F2 Series 48-port, 1- and 10-GBASE-T Ethernet I/O modules (enhanced)
(N7K-F248XT-25E)Power Manager
IOAll
AllN/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A1N/A1
N/A11.009
0.016—
—M1 Series 48-port, 1-Gigabit Ethernet I/O module
(N7K-M148GS-11)Power Manager
IO
SFP
Forwarding EngineAll
All
All
All4.008
1.005
1.004
1.006—
—
—
——
1.006
—
——
—
—
——
—
—
——
—
—
——
—
—
——
—
—
——
—
—
—M1 Series 48-port, 1-Gigabit Ethernet I/O module with XL
(N7K-M148GS-11L)Power Manager
IO
SFP
Forwarding EngineAll
All
All
V01-V04
V05+4.008
1.005
1.004
1.006
N/A2—
—
—
—
N/A2—
1.006
—
—
N/A2—
—
—
—
N/A2—
—
—
—
N/A2—
—
—
—
N/A2—
—
—
—
N/A2—
—
—
—
N/A2—
—
—
—
2.005M1 Series 48-port, 10/100/1000 Ethernet I/O module
(N7K-M148GT-11)Power Manager
IO
Forwarding EngineAll
All
All5.006
2.013
1.006—
—
——
2.014
——
—
——
—
——
—
——
—
——
—
——
—
—M1 Series 48-port, 10/100/1000 Ethernet I/O module with XL
(N7K-M148GT-11L)Power Manager
IO
Forwarding EngineAll
All
V01-V03
V04+N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A15.006
2.014
1.006
N/A2—
—
—
N/A2—
—
—
N/A2—
—
—
N/A2—
—
—
N/A2—
—
—
2.005M1 Series 32-port, 10-Gigabit Ethernet I/O module
(N7K-M132XP-12)Power Manager
IO
LinkSec Engine
FE Bridge
Forwarding EngineAll
All
All
All
All4.008
1.015
2.006
186.005
1.006—
—
—
—
——
1.016
—
186.006
——
—
—
—
——
—
2.007
186.008
——
—
—
—
——
—
—
—
——
—
—
—
——
—
—
—
—M1 Series 32-port, 10-Gigabit Ethernet I/O module with XL
(N7K-M132XP-12L)Power Manager
IO
LinkSec Engine
FE Bridge
Forwarding EngineAll
All
All
All
V01-V03
V04+N/A1
N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1
N/A14.008
1.016
2.006
186.006
1.006
N/A2—
—
—
—
—
N/A2—
—
2.007
186.008
—
N/A2—
—
—
—
—
N/A2—
—
—
—
—
N/A2—
—
—
—
—
N/A2—
—
—
—
—
2.005M1 Series 8-port, 10-Gigabit Ethernet I/O module with XL
(N7K-M108X2-12L)Power Manager
IO
CDL FPGA
Forwarding EngineAll
All
All
V01-V05
V06+4.008
2.006
2.004
1.006
N/A2—
—
—
—
N/A2—
2.007
—
—
N/A2—
—
—
—
N/A2—
—
—
—
N/A2—
—
—
—
N/A2—
—
—
—
N/A2—
—
—
—
N/A2—
—
—
—
2.005M2 Series 24-port, 10-Gigabit Ethernet I/O module with XL
(N7K-M224XP-23L)Power Manager
IO
SFP
Forwarding EngineAll
All
All
V01-V02
V03+N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A11.006
1.003
1.002
1.006
N/A2—
—
—
—
N/A2—
—
—
—
2.005M2 Series 6-port, 40-Gigabit Ethernet I/O module with XL
(N7K-M206FQ-23L)Power Manager
IO
SFP
Forwarding EngineAll
All
All
V01-V02
V03+N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A11.006
0.011
2.008
1.006
N/A2—
—
—
—
N/A2—
—
—
—
2.005M2 Series 2-port, 100-Gigabit Ethernet I/O module with XL
(N7K-M202CF-22L)Power Manager
IO
SFP
Forwarding EngineAll
All
All
V01-V02
V03+N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A1N/A1
N/A1
N/A1
N/A1
N/A11.006
0.009
0.004
1.006
N/A2—
—
—
—
N/A21.007
—
—
—
2.005Fabric-1 module (Cisco Nexus 7010)
(N7K-C7010-FAB1)Power Manager
All
2.010
—
—
—
—
—
—
—
—
Fabric-1 module (Cisco Nexus 7018)
(N7K-C7018-FAB1)Power Manager
All
1.003
—
—
—
—
—
—
—
—
Fabric-2 module (Cisco Nexus 7009)
(N7K-C7009-FAB2)Power Manager
All
N/A1
N/A1
N/A1
N/A1
1.003
—
—
—
—
Fabric-2 module (Cisco Nexus 7010)
(N7K-C7010-FAB2)Power Manager
All
N/A1
N/A1
N/A1
N/A1
N/A1
0.006
0.007
—
—
Fabric-2 module (Cisco Nexus 7018)
(N7K-C7018-FAB2)Power Manager
All
N/A1
N/A1
N/A1
N/A1
N/A1
0.006
0.007
—
—
Fan (Cisco Nexus 7004)
Fan Controller
All
N/A1
N/A1
N/A1
N/A1
N/A1
N/A1
N/A1
0.005
—
Fan (Cisco Nexus 7009)
Fan Controller
All
N/A1
N/A1
N/A1
N/A1
0.007
—
0.009
—
—
Fan (Cisco Nexus 7010)
Fan Controller
All
0.007
—
—
—
—
—
—
—
—
Fan (Cisco Nexus 7018)
Fan Controller
All
0.002
—
—
—
—
—
—
—
—
1 Module and EPLD are not available for that release.
2 This module version did not exist until a later software release.
Note
Determining Whether to Upgrade EPLDs
As shown in Table 8-10, 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 Table 8-9), 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 1DISPLAY linecard sprom contents of module 8:Common block:Block Signature : 0xababBlock Version : 3Block Length : 160Block Checksum : 0x198bEEPROM Size : 65535Block Count : 3... H/W Version : 0.102Mfg Bits : 0Engineer Use : 0snmpOID : 9.12.3.1.9.66.5.0Power Consump : -600RMA Code : 0-0-0-0CLEI Code : COUIAY6CAAVID : 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
The browser will display the Cisco website.
Step 2
The Switches page opens.
Step 3
The page lists the Data Center products.
Step 4
The Cisco Nexus 7000 Series Switches page opens.
Step 5
The Downloads page opens and lists the Data Center switches.
Step 6
The Log In page opens.
Step 7
The Downloads page lists the software types that can be downloaded for the switch that you specified.
Step 8
The Downloads page lists software releases that you can download.
Step 9
The Downloads page displays image information, including a link to the downloadable Tar file, to the right of the releases.
Note
Step 10
The Downloads page displays a Download button and lists information for the Tar file.
Step 11
The Supporting Documents page opens to display the rules for downloading the software.
Step 12
A File Download dialog box opens to ask if you want to open or save the images file.
Step 13
The Save As dialog box appears.
Step 14
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
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.007EPLD 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
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.007Installation 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:
•
–
–
•
•
–
–
•
•
•
•
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
Step 2
switch# show version..SoftwareBIOS: version 3.22.0kickstart: version 6.1(3)system: version 6.1(3)BIOS compile time: 06/09/12kickstart image file is: bootflash:/n7000-s2-kickstart.6.1.3.binkickstart compile time: 12/25/2020 12:00:00 [12/07/2012 18:37:07]system image file is: bootflash:/n7000-s2-dk9.6.1.3.binsystem compile time: 10/31/2012 13:00:00 [12/08/2012 19:21:22]Step 3
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
switch# dir bootflash:...4096 Dec 11 01:19:53 2012 lost+found/3020665 Oct 08 07:47:36 2012 n7000-s1-debug-sh-bash.6.1.2.gbin207429135 Oct 08 07:35:03 2012 n7000-s1-dk9.6.1.2.gbin207558132 Dec 11 07:11:31 2012 n7000-s2-dk9.6.1.3.gbin29479424 Oct 08 12:03:47 2012 n7000-s2-kickstart.6.1.2.gbin29467136 Dec 11 10:35:18 2012 n7000-s2-kickstart.6.1.3.gbin...Usage for bootflash://sup-local685359104 bytes used1153499136 bytes free1838858240 bytes totalswitch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------6 8 10 Gbps Ethernet XL Module N7K-M108X2-12L ok7 48 1/10 Gbps Ethernet Modul N7K-F248XP-24 ok8 48 1000 Mbps Optical Ethernet XL Mo N7K-M148GS-11L ok9 0 Supervisor module-1X N7K-SUP1 ha-standby10 0 Supervisor module-1X N7K-SUP1 active *...switch# attach module 9Attaching to module 9 ...To exit type 'exit', to abort type '$.'Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpswitch#Example 8-14 Determining the Amount of Available Slot0 Memory
switch# dir slot0:...Usage for slot0://sup-local4096 bytes used2044850176 bytes free2044854272 bytes totalswitch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------2 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok3 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok4 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok5 0 Supervisor module-1X N7K-SUP1 ha-standby6 0 Supervisor module-1X N7K-SUP1 active *7 48 1/10 Gbps Ethernet Modul N7K-F248XP-24 ok9 48 1000 Mbps Optical Ethernet Modul N7K-M148GS-11 ok...switch(standby)# dir slot0://sup-standby/...Usage for slot0://sup-standby1376256 bytes used2073870336 bytes free2075246592 bytes totalStep 4
switch# delete bootflash:n7000-s1-kickstart.5.2.0.binStep 5
switch# copy ftp://10.1.7.2/n7000-s1-epld.6.1.2a.img bootflash:n7000-s1-epld.6.1.3.img
Note
Step 6
switch# copy bootflash:n7000-s1-epld.6.1.3.img bootflash://sup-standby/n7000-s1-epld.6.1.3.imgYou are ready to upgrade the EPLD images (see the "Upgrading the EPLD Images" section).
Upgrading the EPLD Images
You can 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 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-11. 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 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.1.3.img parallelExample 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.1.3.img parallelExample 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.1.3.img parallel module all fan-module 1For 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_numberFor 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 action is not required for Release 4.0(3) or later releases). You can reset the power in one of the following two ways:
•
Note
•
Caution
Note
To confirm the EPLD upgrades, see the "Verifying the EPLD Upgrades" section.
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:
switch# show version module 9 epldThis example shows how to verify the EPLD images for the fan-tray module in fan-tray module slot 2:
switch# show version fan 2 epldThis example shows how to verify the EPLD images for the fabric module in fabric module slot 4:
switch# show version xbar 4 epldDisplaying 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.1.3.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.00610 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.0071000 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.003Fabric Module 2 Power Manager 1.003 ...Fan<Cisco Nexus 7009> Fan Controller 0.009 Fan<Cisco Nexus 7009> Fan Controller 0.009Displaying 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 status1) Xbar Module 4 upgraded on Wed Oct 26 16:36:27 2011 (524778 us)Status: EPLD Upgrade was SuccessfulEPLD Curr Ver Old Ver------------------------------------------------------Power Manager 1.003 1.0032) Module 14 upgraded on Mon May 23 19:45:55 2011 (835895 us)Status: EPLD Upgrade was Successful...Default Settings
Table 8-13 lists the default hardware settings.
Table 8-13 Default Hardware Parameters
Power supply mode
Power supply redundancy mode
bv
1 Not supported by the Cisco Nexus 7004 switch.
