-
Cisco Nexus 7000 Series Hardware Installation and Reference Guide
-
Index
-
Preface
-
Overview
-
Installing a Cisco Nexus 7010 Chassis
-
Installing a Cisco Nexus 7018 Chassis
-
Installing Power Supply Units
-
Connecting the Nexus 7000 System to the Network
-
Managing system hardware
-
Hardware Troubleshooting
-
Removal and Installation Procedures
-
Technical Specifications
-
Cable and Port Specifications
-
LED descriptions
-
Repacking the Nexus 7000 Series System for Shipment
-
Site Preparation and Maintenance Records
-
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
Shutting Down a Supervisor or I/O Module
Information About Module Temperature
Overview of Module Temperatures
Displaying the Module Temperature
Displaying Environment Information
Saving the Module Configuration
Purging the Module Configuration
Deciding When to Upgrade EPLDs
Supported Switch Operating Systems
Preparing the EPLD Images for Installation
Upgrading the EPLD Images for I/O or Standby Supervisor Modules
Upgrading EPLDs for the Active Supervisor Module
Upgrading EPLDs for a Fabric Module
Upgrading EPLDs for a Fan Tray Module
Displaying EPLD Versions for an I/O or Supervisor Module
Displaying EPLD Versions for a Fabric Module
Displaying EPLD Versions for a Fan Tray Module
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 6-1.
Example 6-1 Displaying the Hardware Inventory
switch# show inventoryNAME: "Chassis", DESCR: "Nexus7000 C7010 (10 Slot) Chassis "PID: N7K-C7010 , VID: V01 , SN: TBM11493268NAME: "Slot 1", DESCR: "10 Gbps Ethernet Module"PID: N7K-M132XP-12 , VID: V01 , SN: JAB1152010ENAME: "Slot 2", DESCR: "10 Gbps Ethernet Module"PID: N7K-M132XP-12 , VID: V01 , SN: JAB120101QANAME: "Slot 5", DESCR: "Supervisor module-1X"PID: N7K-SUP1 , VID: , SN: JAB115200YJNAME: "Slot 11", DESCR: "Fabric card module"PID: N7K-C7010-FAB-1 , VID: , SN: JAB1152012JNAME: "Slot 12", DESCR: "Fabric card module"PID: N7K-C7010-FAB-1 , VID: , SN: JAB114800U5NAME: "Slot 33", DESCR: "Nexus7000 C7010 (10 Slot) Chassis Power Supply"PID: N7K-AC-6.0KW , VID: V01 , SN: DTH1205T002NAME: "Slot 34", DESCR: "Nexus7000 C7010 (10 Slot) Chassis Power Supply"PID: N7K-AC-6.0KW , VID: V01 , SN: DTH1205T006NAME: "Slot 36", DESCR: "Nexus7000 C7010 (10 Slot) Chassis Fan Module"PID: N7K-C7010-FAN-S , VID: V01 , SN: NWG114906HPNAME: "Slot 37", DESCR: "Nexus7000 C7010 (10 Slot) Chassis Fan Module"PID: N7K-C7010-FAN-S , VID: V01 , SN: NWG114906G9NAME: "Slot 38", DESCR: "Nexus7000 C7010 (10 Slot) Chassis Fan Module"PID: N7K-C7010-FAN-F , VID: V01 , SN: NWG114906N8NAME: "Slot 39", DESCR: "Nexus7000 C7010 (10 Slot) Chassis Fan Module"PID: N7K-C7010-FAN-F , VID: V01 , SN: NWG114906MCTo display switch hardware inventory details, enter the show hardware command. See Example 6-2.
Example 6-2 Displaying Hardware Information
switch# show hardwareCisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained herein are owned byother third parties and are used and distributed under license.Some parts of this software are covered under the GNU PublicLicense. A copy of the license is available athttp://www.gnu.org/licenses/gpl.html.SoftwareBIOS: version 3.11.0loader: version N/Akickstart: version 4.0(1) [build 4.0(0.855)] [gdb]system: version 4.0(1) [build 4.0(0.855)] [gdb]BIOS compile time: 10/15/07kickstart image file is: bootflash:/ks855.S7kickstart compile time: 10/12/2020 25:00:00 [02/02/2008 01:38:41]system image file is: bootflash:/is855.S7system compile time: 1/27/2008 14:00:00 [02/02/2008 02:21:24]Hardwarecisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X")Intel(R) Xeon(R) CPU with 4136544 kB of memory.Processor Board ID JAB115200YJbootflash: 2030616 kBslot0: 0 kB (expansion flash)switch Kernel uptime is 1 day(s), 3 hour(s), 17 minute(s), 12 second(s)Last resetReason: UnknownSystem version: 4.0(0.855)Service:pluginCore Plugin, Ethernet PluginCMPIs not online--------------------------------Switch hardware ID information--------------------------------Switch is booted upSwitch type is : Nexus7000 C7010 (10 Slot) ChassisModel number is N7K-C7010H/W version is 0.406Part Number is 73-10900-04Part Revision is 06Manufacture Date is Year 11 Week 49Serial number is TBM11493268CLEI code is 0--------------------------------Chassis has 10 Module slots and 5 Fabric slots--------------------------------Module1 okModule type is : 10 Gbps Ethernet Module2 submodules are presentModel number is N7K-M132XP-12H/W version is 0.601Part Number is 73-10899-06Part Revision is 13Manufacture Date is Year 11 Week 52Serial number is JAB1152010ECLEI code is 0Module2 okModule type is : 10 Gbps Ethernet Module2 submodules are presentModel number is N7K-M132XP-12H/W version is 0.601Part Number is 73-10899-06Part Revision is 13Manufacture Date is Year 12 Week 1Serial number is JAB120101QACLEI code is 0Module3 emptyModule4 emptyModule5 okModule type is : Supervisor module-1X0 submodules are presentModel number is N7K-SUP1H/W version is 0.901Part Number is 73-10877-09Part Revision is 10Manufacture Date is Year 11 Week 52Serial number is JAB115200YJCLEI code isModule6 emptyModule7 emptyModule8 emptyModule9 emptyModule10 emptyXbar1 okModule type is : Fabric card module0 submodules are presentModel number is N7K-C7010-FAB-1H/W version is 0.405Part Number is 73-10624-04Part Revision is 14Manufacture Date is Year 11 Week 52Serial number is JAB1152012JCLEI code isXbar2 okModule type is : Fabric card module0 submodules are presentModel number is N7K-C7010-FAB-1H/W version is 0.404Part Number is 73-10624-04Part Revision is 11Manufacture Date is Year 11 Week 48Serial number is JAB114800U5CLEI code isXbar3 emptyXbar4 emptyXbar5 empty---------------------------------------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 5Serial number is DTH1205T002CLEI 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 5Serial number is DTH1205T006CLEI code is IPUPADBAAAPS3 absent----------------------------------Chassis has 4 Fan slots----------------------------------Fan1 okModel number is N7K-C7010-FAN-SH/W version is 0.410Part Number is 73-10741-04Part Revision is 10Manufacture Date is Year 11 Week 49Serial number is NWG114906HPCLEI code isFan2 okModel number is N7K-C7010-FAN-SH/W version is 0.410Part Number is 73-10741-04Part Revision is 10Manufacture Date is Year 11 Week 49Serial number is NWG114906G9CLEI code isFan3 okModel number is N7K-C7010-FAN-FH/W version is 0.209Part Number is 73-10967-02Part Revision is 09Manufacture Date is Year 11 Week 49Serial number is NWG114906N8CLEI code isFan4 okModel number is N7K-C7010-FAN-FH/W version is 0.209Part Number is 73-10967-02Part Revision is 09Manufacture Date is Year 11 Week 49Serial number is NWG114906MCCLEI code isswitch#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 6-3.
Example 6-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 6-4.
Note
Example 6-4 Displaying Power Management Information
switch# show environment powerPower Supply:Voltage: 50 Volts-----------------------------------------------------PS Model Power Power Status(Watts) (Amp)-----------------------------------------------------1 N7K-AC-6.0KW 3000.00 60.00 Ok2 N7K-AC-6.0KW 3000.00 60.00 Ok3 N7K-AC-6.0KW 0.00 0.00 ShutdownMod Model Power Power Power Power StatusRequested Requested Allocated Allocated(Watts) (Amp) (Watts) (Amp)--- ------------------- ------- ---------- --------- ---------- ----------1 N7K-M132XP-12 773.50 15.47 773.50 15.47 Powered-Up2 N7K-M132XP-11 423.50 8.47 423.50 8.47 Powered-Up5 N7K-SUP1 210.00 4.20 210.00 4.20 Powered-Up6 N7K-SUP1 210.00 4.20 210.00 4.20 Powered-UpXb1 N7K-C7010-FAB-1 60.00 1.20 60.00 1.20 Powered-UpXb2 N7K-C7010-FAB-1 60.00 1.20 60.00 1.20 Powered-UpPower Usage Summary:--------------------Power Supply redundancy mode: PS-RedundantPower Supply redundancy operational mode: Non-RedundantTotal Power Capacity 12000.00 WPower reserved for Supervisor(s) 420.00 WPower reserved for Fan Module(s) 2184.00 WPower reserved for Fabric Module(s) 300.00 WPower currently used by Modules 1197.00 W-------------Total Power Available 7899.00 W-------------switch#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 all of the available power provided by the installed power supply units or to provide power redundancy when there is a power loss:
•
•
•
•
To determine the amount of available power for 6-kW power supply units in each power mode, see Table 6-1. To determine the amount of available power for 7.5-kW power supply units, see Table 6-2.
Configuring 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 6-3 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 6-4 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.Then 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 6-5 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.Then 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 6-6 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 7010 switch has one or two supervisor modules. 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. To understand the terms used for the supervisors, see Table 6-7.
Supervisor modules are automatically powered up and started with the switch.
I/O Modules
Cisco Nexus 7000 Series switches support the following I/O modules in slots 1 through 4 and 7 through 10:
•
•
•
Fabric Modules
Cisco Nexus 7000 Series switches support up to five fabric modules in the back of the chassis.
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 a module at any time, enter the show module 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 6-5.
Example 6-5 Displaying Module Information
switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------6 0 Supervisor module-1X N7K-SUP1 active *Mod Sw Hw World-Wide-Name(s) (WWN)--- -------------- ------ --------------------------------------------------6 4.0(0.855) 0.34051 --Mod MAC-Address(es) Serial-Num--- -------------------------------------- ----------6 00-1b-54-c1-20-90 to 00-1b-54-c1-28-90 JAB1152011J* this terminal sessionswitch#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 6-8 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.
Shutting Down Modules
This section includes the following topics:
•
•
Shutting Down a Supervisor or I/O Module
To perform a graceful shutdown of a supervisor or I/O 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 perform a graceful shutdown of a fabric module, use the out-of-service xbar command to specify the fabric slot with that module as follows:
switch# out-of-service xbar slotInformation 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 6-6.
Example 6-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 6-7.
Example 6-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------------------------------------------------------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 -- -- AbsentTemperature:--------------------------------------------------------------------Module Sensor MajorThresh MinorThres CurTemp Status(Celsius) (Celsius) (Celsius)--------------------------------------------------------------------6 Outlet1 (s1) 125 125 47 Ok6 Outlet2 (s2) 125 125 40 Ok6 Intake (s3) 60 42 31 Ok6 EOBC_MAC(s4) 105 95 44 Ok6 CPU (s5) 105 95 39 Ok6 Crossbar(s6) 105 95 58 Ok6 Arbiter (s7) 110 100 61 Ok6 CTSdev1 (s8) 115 105 41 Ok6 InbFPGA (s9) 105 95 45 Ok6 QEng1Sn1(s10) 115 105 62 Ok6 QEng1Sn2(s11) 115 105 60 Ok6 QEng1Sn3(s12) 115 105 59 Ok6 QEng1Sn4(s13) 115 105 60 Okxbar-1 Outlet (s1) 125 125 35 Okxbar-1 Intake (s2) 60 42 30 Okxbar-1 Crossbar(s3) 105 95 45 Okxbar-2 Outlet (s1) 125 125 37 Okxbar-2 Intake (s2) 62 42 29 Okxbar-2 Crossbar(s3) 105 95 45 OkPower Supply:Voltage: 50 Volts-----------------------------------------------------PS Model Power Power Status(Watts) (Amp)-----------------------------------------------------1 N7K-AC-6.0KW 6000.00 120.00 Ok2 N7K-AC-6.0KW 6000.00 120.00 Ok3 ------------ 0.00 0.00 AbsentMod Model Power Power Power Power StatusRequested Requested Allocated Allocated(Watts) (Amp) (Watts) (Amp)--- ------------------- ------- ---------- --------- ---------- ----------6 N7K-SUP1 400.00 8.00 400.00 8.00 Powered-UpXb1 N7K-C7010-FAB-1 60.00 1.20 60.00 1.20 Powered-UpXb2 N7K-C7010-FAB-1 60.00 1.20 60.00 1.20 Powered-UpPower Usage Summary:--------------------Power Supply redundancy mode: RedundantPower Supply redundancy operational mode: RedundantTotal Power Capacity 6000.00 WPower reserved for Supervisor(s) 800.00 WPower reserved for Fan Module(s) 2002.00 WPower reserved for Fabric Module(s) 300.00 WPower currently used by Modules 0.00 W-------------Total Power Available 2898.00 W-------------switch#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 6-9 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 module in slot 3 in Switch A. This module uses IP address 10.1.5.500. You decide to remove this I/O module and move it to Switch B, and you no longer need the IP address 10.1.5.500. 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 this IP address.
Powering Off I/O Modules
By default, all fabric modules are configured to be in the power up state.
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:
•
•
Tip
The fan status is continuously monitored by the software. In case of a fan failure, these actions occur:
•
•
•
Use the show environment fan command to display the fan module status (see Example 6-8).
Example 6-8 Displays Chassis Fan Information
switch# show environment fan------------------------------------------------------Fan Model Hw Status------------------------------------------------------Chassis DS-9SLOT-FAN 1.2 okPS-1 -- -- okPS-2 -- -- absentThe possible Status field values for a fan module on the Cisco Nexus 7000 Series switches are as follows:
•
•
•
On the Cisco Nexus 7010, each system fan module has 15 fans. If the State field for one of these fans contains "failure" in the show environment fan command output, it also displays the number of the failing fans (see Example 6-9).
Example 6-9 Displaying a Cisco Nexus 7010 System Fan Tray Failure
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 -- -- Absentswitch#EPLD Configuration
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 great 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
Cisco Systems does not provide upgrade EPLD images very frequently, and you do not have to upgrade your EPLD images unless they fix the functions for the hardware that you are using in your Cisco Nexus 7000 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 their availability, and you can download them from http://www.cisco.com.
This section includes the following topics:
•
•
•
Deciding When to Upgrade EPLDs
It is not always necessary to upgrade EPLD images; however, 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, then it is best to postpone the upgrade until a better time.
Table 6-10 provides high-level guidelines to help network administrators determine whether an EPLD upgrade is necessary.
Switch Requirements
This section includes the following topics:
•
Hardware Requirements
The Cisco Nexus 7000 Series switch must 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.
Supported Switch Operating Systems
The Cisco Nexus 7000 Series switch must be running the Cisco NX-OS operating system, which is used to perform the EPLD upgrades.
New EPLDs
Each EPLD image that you can download from http://www.cisco.com is a bundle of EPLD upgrades. To see which EPLD versions were updated for Release 4.1, see Table 6-11. To see all of the current EPLD versions for each device, see Table 6-12.
.
Note
EPLD Images Needed for vPC
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 Release 186.3 on the 32-port 10 Gbps Ethernet IO modules (N7K-M132XP-12).
Note
Most of the N7K-M132XP-12 modules in the chassis already meet this minimum EPLD requirement, but if you are working with a 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 module_id epld. If the line FE Bridge(x) version displays a version earlier than 186.3 (for example, 186.2), you should schedule an EPLD upgrade to a version that is compatible with the target NX-OS release. For example, if you want to run Cisco NX-OS Release 4.1(3), you should choose Release 4.1(3) EPLDs.
The following example shows Release 186.3 on the FE Bridge line, which is the correct EPLD version:
Nexus-7k(config)# show ver mod 7 epld EPLD Device Version --------------------------------------- Power Manager 4.4 IO 1.10 Forwarding Engine 1.6 FE Bridge(1) 186.3 << OK! FE Bridge(2) 186.3 << OK! Linksec Engine(1) 1.5 Linksec Engine(2) 1.5 Linksec Engine(3) 1.5 Linksec Engine(4) 1.5 Linksec Engine(5) 1.5 Linksec Engine(6) 1.5 Linksec Engine(7) 1.5 Linksec Engine(8) 1.5Installation 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:
•
•
•
–
–
•
•
•
•
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
http://www.cisco.com
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 the releases.
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).
Preparing the EPLD Images for Installation
Before you can update the EPLD images for each of your system modules, you must determine the Cisco NX-OS version that your system 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 versionCisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2008, 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.17.0loader: version N/Akickstart: version 4.0(2) [gdb]system: version 4.0(2) [gdb]...Step 3
Example 6-10 Determining the Amount of Available Bootflash Memory
switch# dir bootflash:4096 Mar 18 17:31:11 2008 bak/2429706 May 23 10:57:10 2008 dplug89154513 May 27 22:04:37 2008 n7-dk9-nk89151767 May 23 16:06:01 2008 n7-dk9-nk-old2429706 May 23 10:53:50 2008 n7000-s1-debug-sh.4.0.2.bin122171136 May 23 10:55:40 2008 n7000-s1-kickstart.4.0.2.bin14096 May 23 13:03:37 2008 newer-fs/4096 May 28 15:13:30 2008 nk/127 Mar 20 16:37:59 2008 setip.shUsage for bootflash://sup-local572186624 bytes used306606080 bytes free878792704 bytes totalswitch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------2 32 10 Gbps Ethernet Module N7K-M132XP-12 ok5 0 Supervisor module-1X N7K-SUP1 ha-standby6 0 Supervisor module-1X N7K-SUP1 active *...switch# attach module 5...4096 Mar 18 17:31:11 2008 bak/2429706 May 23 10:57:10 2008 dplug89154513 May 27 22:04:37 2008 n7-dk9-nk89151767 May 23 16:06:01 2008 n7-dk9-nk-old2429706 May 23 10:53:50 2008 n7000-s1-debug-sh.4.0.2.bin122171136 May 23 10:55:40 2008 n7000-s1-kickstart.4.0.2.bin14096 May 23 13:03:37 2008 newer-fs/4096 May 28 15:13:30 2008 nk/127 Mar 20 16:37:59 2008 setip.shUsage for bootflash://sup-local572186624 bytes used306606080 bytes free878792704 bytes totalExample 6-11 Determining the Amount of Available Slot0 Memory
switch# dir slot0:25 Apr 28 23:07:28 2008 slot0Usage for slot:642273280 bytes used261824512 bytes free904097792 bytes totalswitch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------2 32 10 Gbps Ethernet Module N7K-M132XP-12 ok5 0 Supervisor module-1X N7K-SUP1 ha-standby6 0 Supervisor module-1X N7K-SUP1 active *...switch(standby)# dir slot0://sup-standby/25 Apr 28 23:07:28 2008 slot0Usage for slot:642273280 bytes used261824512 bytes free904097792 bytes totalStep 4
switch# delete bootflash:n7000-s1-kickstart.4.0.1.binStep 5
switch# copy ftp://10.1.7.2/n7000-s1-epld.4.0.2.img bootflash:n7000-s1-epld.4.0.2.imgStep 6
switch# copy bootflash:n7000-s1-epld.4.0.2.img bootflash://sup-standby/n7000-s1-epld.4.0.2.imgYou are ready to upgrade the EPLD images (see the "Upgrading EPLD Images" section).
Upgrading EPLD Images
When you start upgrading the EPLD images for a module, the Cisco NX-OS software tries to list the current and new versions for each EPLD. If the module is installed and online, the software reports both the installed and new versions of each EPLD, and where there is a difference, the software upgrades (or downgrades) to the new version when you confirm that the upgrade should occur. For a module that is installed but offline, the software cannot determine the installed versions of its EPLDs so it upgrades all of the EPLDs for that module when you confirm the upgrade. For a module that is not installed, the software displays an error message and does not upgrade the EPLDs.
Example 6-12 shows how the software reports the current and new EPLD versions for a module that does not need EPLD upgrades. The current and new version numbers for each EPLD are the same.
Example 6-12 EPLD Version Comparison Report—No Upgrade Needed
EPLD Curr Ver New Ver-------------------------------------------------------Power Manager 5.3 5.3IO 2.10 2.10Forwarding Engine 1.6 1.6Module 1 is upto dateExample 6-13 shows how the software reports the current and new EPLD versions for a module that has EPLD images that can be upgraded. According to this report, each of the downloaded Linksec Engine EPLDs has a different version than the same EPLD on the module, so the software will upgrade those EPLDs but will not upgrade the other EPLDs that have the same version numbers. If the new versions have a smaller version number compared to the current version, the software downgrades the versions.
Example 6-13 EPLD Version Comparison Report—Upgrade Needed
EPLD Curr Ver New Ver-------------------------------------------------------Power Manager 4.4 4.4IO 1.10 1.10Forwarding Engine 1.6 1.6FE Bridge(1) 186.3 186.3FE Bridge(2) 186.3 186.3Linksec Engine(1) 1.5 1.7Linksec Engine(2) 1.5 1.7Linksec Engine(3) 1.5 1.7Linksec Engine(4) 1.5 1.7Linksec Engine(5) 1.5 1.7Linksec Engine(6) 1.5 1.7Linksec Engine(7) 1.5 1.7Linksec Engine(8) 1.5 1.7The following sections explain how to upgrade the EPLD images for I/O and standby modules, the active supervisor module on single-supervisor systems, fabric modules, and fan tray modules:
•
•
•
•
Upgrading the EPLD Images for I/O or Standby Supervisor Modules
You can upgrade the EPLD images for an I/O module or standby supervisor module while the switch is operational. If you need to upgrade EPLD images for a single-supervisor module, see the "Upgrading EPLDs for the Active Supervisor Module" section.
Caution
To upgrade EPLDs for an I/O module or the standby supervisor module, follow these steps:
Step 1
switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 48 10/100/1000 Mbps Ethernet Module N7K-N148GT-11 ok3 32 10 Gbps Ethernet Module N7K-M132XP-12 ok5 0 Supervisor module-1X N7K-SUP1 active6 0 Supervisor module-1X N7K-SUP1 ha-standby10 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 okMod Sw Hw World-Wide_name(s) (WWN)--- -------------- ------ -------------------------------------------------1 4.0(2) 0.503 --3 4.0(2) 0.601 --5 4.0(2) 0.900 --6 4.0(2) 0.802 --10 4.0(2) 0.902 --Mod MAC-Address(es) Serial-Num--- -------------------------------------- ----------1 00-19-07-6c-c0-6c to 00-19-07-6c-c0-a0 JAB110601443 00-1b-54-c1-33-98 to 00-1b-54-c1-33-bc JAB1152010K5 00-1b-54-c1-16-18 to 00-1b-54-c1-16-20 JAB114902HF6 00-19-07-c1-00-b8 to 00-1b-54-c1-00-c0 JAB114402JX10 00-1b-54-c1-07-88 to 00-1b-54-c1-07-bc JAB114501RW* this terminal sessionswitch#Step 2
switch# install module 6 epld bootflash:n7000-s1-epld.4.0.2.imgEPLD image file , built on Fri May 16 20:36:39 2008EPLD Curr Ver New Ver-------------------------------------------------------Power Manager 3.4 3.6IO 3.23 3.23Inband 1.7 1.7Local Bus CPLD 2.1 2.1CMP CPLD 6.0 6.0WARNING: Upgrade process could take upto 30 minutes.Standby supervisor is being upgraded.Do you want to continue (y/n) ?Step 3
Do you want to continue (y/n) ? YStep 4
•
Note
•
To confirm the EPLD upgrade, see the "Displaying EPLD Versions for an I/O or Supervisor Module" section.
Caution
Note
Upgrading EPLDs for the Active Supervisor Module
When you upgrade EPLDs on a system with only one supervisor module, data traffic on the switch will be affected when you reload the system after the upgrade. If you are upgrading EPLDs for a switch with two supervisor modules, you can upgrade the standby supervisor while the system is operational as explained in the "Upgrading the EPLD Images for I/O or Standby Supervisor Modules" section.
To upgrade EPLDs for the supervisor module in a system with a single supervisor module, follow these steps:
Step 1
switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 48 10/100/1000 Mbps Ethernet Module N7K-N148GT-11 ok3 32 10 Gbps Ethernet Module N7K-M132XP-12 ok5 0 Supervisor module-1X N7K-SUP1 active10 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 okMod Sw Hw World-Wide_name(s) (WWN)--- -------------- ------ -------------------------------------------------1 4.0(2) 0.503 --3 4.0(2) 0.601 --5 4.0(2) 0.900 --10 4.0(2) 0.902 --Mod MAC-Address(es) Serial-Num--- -------------------------------------- ----------1 00-19-07-6c-c0-6c to 00-19-07-6c-c0-a0 JAB110601443 00-1b-54-c1-33-98 to 00-1b-54-c1-33-bc JAB1152010K5 00-1b-54-c1-16-18 to 00-1b-54-c1-16-20 JAB114902HF10 00-1b-54-c1-07-88 to 00-1b-54-c1-07-bc JAB114501RW* this terminal sessionStep 2
switch# install module 5 epld bootflash:n7000-s1-epld.4.0.2.imgEPLD image file , built on Fri May 16 20:36:39 2008EPLD Curr Ver New Ver-------------------------------------------------------Power Manager 3.4 3.6IO 3.23 3.23Inband 1.7 1.7Local Bus CPLD 2.1 2.1CMP CPLD 6.0 6.0WARNING: Upgrade process could take upto 30 minutes.Active Supervisor is being upgraded.Data traffic on the switch will be affected!!The switch will reload after the upgrade process.Do you want to continue (y/n) ?Step 3
Do you want to continue (y/n) ? Y\Module 5 EPLD upgrade is successfulThe Cisco Nexus 7000 Series switch reloads as soon as the upgrade occurs.
Step 4
•
Note
•
To confirm the EPLD upgrade, see the "Displaying EPLD Versions for an I/O or Supervisor Module" section.
Caution
Note
Upgrading EPLDs for a Fabric Module
You can upgrade EPLDs for a fabric (Xbar) module while the system is operational as long as at least one other fabric module is operational.
To upgrade EPLDs for a fabric module, follow these steps:
Step 1
switch# show module xbarXbar Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 0 Xbar N7K-C7010-FAB-1 ok2 0 Xbar N7K-C7010-FAB-1 ok3 0 Xbar N7K-C7010-FAB-1 okXbar Sw Hw World-Wide-Name(s) (WWN)--- -------------- ------ ----------------------------------------------------1 NA 0.404 --2 NA 0.405 --4 NA 0.405 --Xbar MAC-Address(es) Serial-Num------------------------------------------- ------------------1 NA JAB114700WL2 NA JAB115000LU4 NA JAB115000LJ* this terminal sessionStep 2
switch# install xbar-module 1 epld bootflash:n7000-s1-epld.4.0.2.imgEPLD image file , built on Fri May 16 20:36:39 2008EPLD Curr Ver New Ver-------------------------------------------------------Power Manager 2.7 2.8WARNING: Upgrade process could upto 30 minutes.Module could be powered down and up.Xbar Module 1 will be powered down now!!Do you want to continue (y/n) ? [n]Step 3
Do you want to continue (y/n) ? [n] yTo confirm the EPLD upgrade, see the "Displaying EPLD Versions for a Fabric Module" section.
Upgrading EPLDs for a Fan Tray Module
You can upgrade EPLDs for fan tray modules while the switch is operational.
To upgrade EPLDs for a fan tray module, follow these steps:
Step 1
switch# show environment fanFan:------------------------------------------------------Fan Model Hw Status------------------------------------------------------Fan1(sys_fan1) 0.0 OkFan2(sys_fan2) 0.0 OkFan3(fab_fan1) 0.0 OkFan4(fab_fan2) 0.0 OkFan_in_PS1 -- -- OkFan_in_PS2 -- -- OkFan_in_PS3 -- -- OkFan Air Filter : Absentswitch#Step 2
switch# install fan-module 1 epld bootflash:n7000-s1-epld.4.0.2.imgEPLD image file , built on Fri May 16 20:36:39 2008EPLD Curr Ver New Ver-------------------------------------------------------Fan Controller 0.5 0.7Fan Controller 0.5 0.7WARNING: Upgrade process could upto 30 minutes.Module could be powered down and up.Programming Fan Module 1 !!Do you want to continue (y/n) ? [n]Step 3
...Do you want to continue (y/n) ? [n] y
To confirm the EPLD upgrade, see the "Displaying EPLD Versions for a Fan Tray Module" section.
Displaying the EPLD Versions
These topics describe how to display the EPLD versions on each module in your system and display the available EPLD versions:
•
•
•
•
Displaying EPLD Versions for an I/O or Supervisor Module
To display all of the current EPLD versions on a specific I/O or supervisor module, use the show version module slot_number epld command as shown in Example 6-14.
Example 6-14 Displaying the Current EPLD Versions for a Module
switch# show version module 2 epldEPLD Device Version---------------------------------------Power Manager 4.2IO 1.10Forwarding Engine 1.6FE Bridge(1) 186.2FE Bridge(2) 186.2Linksec Engine(1) 1.2Linksec Engine(2) 1.2Linksec Engine(3) 1.2Linksec Engine(4) 1.2Linksec Engine(5) 1.2Linksec Engine(6) 1.2Linksec Engine(7) 1.2Linksec Engine(8) 1.2Displaying EPLD Versions for a Fabric Module
To view all current EPLD versions on a fabric module, use the show version xbar slot_number epld command as shown in Example 6-15.
Example 6-15 Displaying the Current EPLD Versions for a Fabric Module
switch# show version xbar 1 epldEPLD Device Version---------------------------------------Power Manager 2.7Displaying EPLD Versions for a Fan Tray Module
To view all current EPLD versions on a specific fan tray, use the show version fan slot_number epld command as shown in Example 6-16.
Example 6-16 Displaying Current EPLD Versions for Fan Tray 1
switch# show version fan 1 epldEPLD Device Version---------------------------------------Fan Controller(BUS A) 2.7Fan Controller(BUS B) 2.7Displaying the Available EPLD Versions
To view the available EPLD versions, use the show version epld url command as shown in Example 6-17.
Example 6-17 Displaying the Available EPLD Versions
switch# show version epld bootflash:n7000-s1-epld.4.0.2.imgEPLD image file , built on Fri May 16 20:36:39 2008Module Type EPLD Device Version---------------------------------------------------------------Supervisor-1X Power Manager 3.7Supervisor-1X IO 3.26Supervisor-1X Inband 1.7Supervisor-1X Local Bus CPLD 3.0Supervisor-1X CMP CPLD 6.010/100/1000 Mbps Eth Module Power Manager 5.410/100/1000 Mbps Eth Module IO 2.1010/100/1000 Mbps Eth Module Forwarding Engine 1.610 Gbps Ethernet Module Power Manager 4.610 Gbps Ethernet Module IO 1.1410 Gbps Ethernet Module Forwarding Engine 1.610 Gbps Ethernet Module FE Bridge 186.310 Gbps Ethernet Module Linksec Engine 1.7Xbar Power Manager 2.9Fan Fan Controller 0.7Fan Fan Controller 0.7Displaying the Status of EPLD Upgrades
To display the status of EPLD upgrades on the switch, use the show install epld status command.
Example 18 Displaying EPLD Upgrades
switch# show install epld status1) Module 2 upgraded on Wed Sep 17 00:27:15 (354639 us)Status: EPLD Upgrade was SuccessfulEPLD Curr Ver Old Ver------------------------------------------------------Power Manager 5.4 5.0IO 2.11 2.8Forwarding Engine 1.6 1.3Default Settings
Table 6-13 lists the default hardware settings.
Table 6-13 Default Hardware Parameters
Power supply mode
Power supply redundancy mode
