Cisco Cisco Nexus 5010 Switch Guía De Instalación

Descargar
Página de 42
40
Cisco Nexus 5500 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.1(3)N1(1)
Downgrading from a Higher Release
switch-1(config)# sh fex 
  FEX         FEX           FEX                       FEX               
Number    Description      State            Model            Serial     
------------------------------------------------------------------------
126         FEX126       FEX AA Upg Idle  N2K-C2232TM-E-10GE   SSI153501JG
127         FEX127                Online  N2K-C2232TM-E-10GE   SSI153402XS
133         FEX133                Online    N2K-C2232PP-10GE   SSI1350065L
switch-2(config)# sh fex 
  FEX         FEX           FEX                       FEX               
Number    Description      State            Model            Serial     
------------------------------------------------------------------------
126         FEX126      Hitless Upg Idle  N2K-C2232TM-E-10GE   SSI153501JG
127         FEX127                Online  N2K-C2232TM-E-10GE   SSI153402XS
133         FEX133                Online    N2K-C2232PP-10GE   SSI1350065L
Downgrading from a Higher Release
The procedure for entering the install all command to downgrade the switch is identical to using the 
install all command for a switch upgrade, except that the image files to be loaded are for an earlier 
release than the image that is currently running on the switch. You can use the show incompatibility 
system
 command to ensure that there are no feature incompatibilities between the current release and 
the target release. Note that downgrades are disruptive. Refer to the release-specific information section 
to get information about certain downgrades that are nondisruptive.
Note
Before you downgrade to a specific release, check the release notes for the current release installed on 
the switch to ensure that your hardware is compatible with the specific release. You must be aware of 
special caveats before you downgrade the switch software to a Cisco NX-OS 4.0(0)-based release. See 
the Release Notes for your platform for details.
Troubleshooting ISSUs and Disruptive Installations
Some common causes for ISSU failure are as follows:
ISSU requirements are not met—Bridge Assurance is active or the switch is not a leaf node in the 
STP topology. These problems are described in the commands explained in the 
.
bootflash: does not have enough space to accept the updated image.
The specified system and kickstart are not compatible.
The hardware is installed or removed while the upgrade is in process.
Any power disruption that occurs while an upgrade is in progress.
The entire path for the remote server location is not specified accurately.