Cisco Cisco Nexus 5010 Switch Guida All'Installazione
31
Cisco Nexus 5500 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.2(0)N1(1)
Forcing an Upgrade
•
You want to do a disruptive upgrade. See the
.
Restoring the Configuration
Perform the following steps to restore the configuration if the configurations contain interface breakout
or unified port configurations:
or unified port configurations:
1.
Save the configuration to bootflash using the command copy running-config
bootflash:[directory/]filename.
bootflash:[directory/]filename.
2.
Use the default interface command to restore the default configurations of the breakout interfaces.
Example: default interface e1/49/1-4, e2/25/1-4.
Example: default interface e1/49/1-4, e2/25/1-4.
3.
Save the running configuration to startup configuration using the copy running-config
startup-config command.
startup-config command.
4.
Perform software migration using the install all command from Cisco NX-OS Release 7.2(0)N1(1)
to a lower version. In case of VPC, downgrade the primary switch first and then the secondary
switch.
to a lower version. In case of VPC, downgrade the primary switch first and then the secondary
switch.
5.
After the switch is up, power-off and power-on the module for the interface breakout to be effective.
If the breakout is configured on Baseboard module, save the running configuration to startup
configuration using the copy running-config startup-config command and then reload the switch
again.
If the breakout is configured on Baseboard module, save the running configuration to startup
configuration using the copy running-config startup-config command and then reload the switch
again.
6.
If breakout is not configured on the Baseboard module, then an additional reload is required if
running configuration contains hardware profile route resource service-template.
running configuration contains hardware profile route resource service-template.
7.
After the switch is up (with all the modules), copy the saved configuration from
bootflash:<filename> to running-config.
bootflash:<filename> to running-config.
8.
Verify if all the interfaces are up and traffic is resumed.
Forcing an Upgrade
You can choose to do a disruptive upgrade if one of the ISSU conditions are not met. One additional
reason where you might choose to do a disruptive upgrade is when FEXs are upgraded in a rolling
fashion (one FEX at a time), which requires a longer maintenance window. With a disruptive upgrade,
all the connected FEXs are upgraded simultaneously, so the maintenance window can be shorter. If you
need a shorter maintenance window (with traffic disruption), you can force a disruptive upgrade even if
an ISSU can be leveraged. It is important to note the possibility of an outage if you do a disruptive
upgrade.
reason where you might choose to do a disruptive upgrade is when FEXs are upgraded in a rolling
fashion (one FEX at a time), which requires a longer maintenance window. With a disruptive upgrade,
all the connected FEXs are upgraded simultaneously, so the maintenance window can be shorter. If you
need a shorter maintenance window (with traffic disruption), you can force a disruptive upgrade even if
an ISSU can be leveraged. It is important to note the possibility of an outage if you do a disruptive
upgrade.
switch# install all force kickstart bootflash:/kickstart_image.bin system
bootflash:/system_image.bin
Installer is forced disruptive
Verifying image bootflash:/kickstart_image.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/system_image.bin for boot variable "system".
...
You can also add the force keyword at the end of the install all command as follows:
switch# install all kickstart bootflash:/kickstart_image.bin system