Command-Use the following commands to prepare for and install the new software:.– Remotely-Images are in a remote location and you specify the destination using the remote server parameters and the filename to be used locally. – Locally-Images are locally available on the switch. Retrieve compatible images in one of two ways:.If this happens, the subsequent reload will be done with the old kickstart and system images as the boot variables. If you specify the kickstart and system images and do not specify the save-config option, the kickstart and system boot variables will not be saved.– If you specify a different system image, ensure that it is compatible with the running kickstart image.

– If the kickstart image is not specified, the switch uses the current running kickstart image.

Software image-Ensure that the specified system and kickstart images are compatible with each other as follows:.

Link Aggregation Control Protocol (LACP) fast timers-To allow fast-reload, ensure that LACP fast timers are not configured.

The switch and the remote server must be in the same subnetwork if you do not have a router to route traffic between subnets. Ensure that the switch has a route to the remote server. Power interruptions can corrupt the software image.Ĭonfigure the IPv4 address or IPv6 address for the 10/100/1000 BASE-T Ethernet port connection (interface mgmt0).

Hardware-Avoid power interruptions during an installation procedure.

The internal bootflash requires approximately 200 MB of free space.

Space-Verify that sufficient space is available in the location where you are copying the images.

You cannot configure a switch during an upgrade. Ensure that everyone who has access to the switch or the network is not configuring the switch or the network during this time.

Scheduling-You should upgrade when your network is stable and steady.

However, you should not make changes to the Layer 2 and routing topologies, and the default root bridge should not be configured. You should perform module installations or removals only before or after an upgrade.

Topology-You should make topology changes such as Spanning Tree Protocol (STP) before you perform an upgrade.

Obtaining Documentation and Submitting a Service Request Upgrade Process for a vPC Topology on the Secondary Switch Upgrade Process for a vPC Topology on the Primary Switch Upgrading the BIOS and Power Sequencer ImagesĬopying the Running Configuration from an External Flash Memory DeviceĬopying the Startup Configuration from an External Flash Memory Device

Using the Install All Non-Interruptive Command Upgrading and Downgrading using Fast Reboot Using the Fast-Reload Non-Interruptive CommandĮnabling BGP Graceful Restart with Fast Reboot Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 6.x

Generals zero hour map pack 3000