• Do not copy any configurations using the
copy running-config startup-config
command or the
copy
running-config startup-config vdc-all
from any other management session while migration is in progress.
• Do not trigger any EPLD or BIOS upgrades during migration.
• Do not trigger any ISSU during migration.
• Do not perform migration from fabric module-2 to fabric module-3 during the supervisor-2E to
supervisor-3E migration.
• Take a backup of the licenses and configuration before starting the migration procedure. In case of any
failure or loss of licenses and configuration in Supervisor-2E, disruptive migration has to be done to
upgrade to Supervisor- 3E. In such a scenario, all configurations and licenses have to be applied or
installed again. Backup the installed licenses from the switch to a USB drive by using the
copy licenses
command. To view the current licenses installed on the switch, use the
show license
command.
switch#
copy licenses usb1:
<licenses_archive_file_name>
.tar
• Ensure that there is sufficient power in the chassis before starting the migration process. In case of a
power failure, redundant power supplies can then take over and migration will not be disrupted.
• Downgrade to supervisor-2E modules from supervisor-3E modules is a disruptive procedure.
Prerequisites for Nondisruptive Migration from Supervisor 2E Modules
(N77-SUP2E) to Supervisor 3E Modules (N77-SUP3E)
• The minimum supported release for this procedure is Cisco NX-OS Release 8.4(1). If you are using an
image older than Cisco NX-OS Release 8.4(1), upgrade to Cisco NX-OS Release 8.4(1), and then perform
nondisruptive migration from Supervisor 2E modules to Supervisor 3E modules.
• We recommend that you use a console connection to perform the migration procedure. In case you do
not have a console connection and are using an SSH/Telnet connection, use the
terminal monitor
command to display all the syslogs mentioned in the below procedures.
• Back up the running configuration from the current active supervisor module to the FTP/SFTP/TFTP
server, or a USB flash drive.
switch# copy running-config ftp:[//[username[:password]@]server][/path]
or
switch# copy running-config usb1:<runningconfiguration>.txt
Copy complete, now saving to disk (please wait)...
• Before you initiate the migration procedure, you must first remove QoS policies and ACLs from interfaces
that are in the down state. The clear inactive-config qos command, that clears inactive configuration,
will delete the port channel policies even if one of the ports in a port channel has inactive policies.
Guidelines for manual policy removal:
• During manual removal, when the interface is part of a port channel, remove the policy map or
access list from the port channel or remove the interface from the port channel before initiating the
migration procedure.
• For all other interface types, please remove the policy map or access list from the interface.
• The
migrate sup kickstart <sup3-kickstart-image> system <sup3-system-image>
command that is
used to initiate the non-disruptive migration process is only available in global config mode.
Cisco Nexus 7710 Switch Site Preparation and Hardware Installation Guide
OL-30452-01.
94
Installing or Replacing Modules, Fan Trays, and Power Supplies
Prerequisites for Nondisruptive Migration from Supervisor 2E Modules (N77-SUP2E) to Supervisor 3E Modules (N77-SUP3E)
