• Verify the recommended upgrade paths between releases are specified in the Cisco Nexus 9000 and 3000 Upgrade and ISSU Matrix.

• Ensure that no user—who has access to the device or the network—is configuring the device or the network during the upgrade. You cannot configure a device during an upgrade. To verify that you have no active configuration sessions, use the show configuration session summary command.

• Save, commit, or discard any active configuration sessions before upgrading or downgrading the NX-OS software image on your device. While upgrading NX-OS software on a device with dual supervisors, the active supervisor module cannot switch over to the standby supervisor module if there is an active configuration session.

• To transfer NX-OS software images to the Nexus switch through a file transfer protocol such as TFTP, FTP, SFTP, and SCP, verify that the Nexus switch can connect to the remote file server where the NX-OS software images are stored. If you do not have a router to route traffic between sub nets, ensure that the Nexus switch and the remote file server are on the same sub network. To verify connectivity to the remote server, transfer a test file using a file transfer protocol of your choice or use the ping command if the remote file server is configured to respond to ICMP Echo Request packets. Here is an example of using the ping command to verify connectivity to a remote file server 192.0.2.100.

  switch# ping 192.0.2.100 vrf management
  PING 192.0.2.100 (192.0.2.100): 56 data bytes
  64 bytes from 192.0.2.100: icmp_seq=0 ttl=239 time=106.647 ms
  64 bytes from 192.0.2.100: icmp_seq=1 ttl=239 time=76.807 ms
  64 bytes from 192.0.2.100: icmp_seq=2 ttl=239 time=76.593 ms
  64 bytes from 192.0.2.100: icmp_seq=3 ttl=239 time=81.679 ms
  64 bytes from 192.0.2.100: icmp_seq=4 ttl=239 time=76.5 ms
  
  --- 192.0.2.100 ping statistics ---
  5 packets transmitted, 5 packets received, 0.00% packet loss
  round-trip min/avg/max = 76.5/83.645/106.647 ms
  
  

• For non-disruptive ISSU in spanning tree topology, before running the show spanning-tree issu-impact command, the criteria that you must verify include

  • no topology change must be active in any STP instance

  • Bridge Assurance (BA) should not be active on any port (except MCT and vPC peer link)

  • there should be no Non-Edge Designated Forwarding port (except MCT and vPC peer link), and

  • ISSU criteria must be met on the vPC peer switch.

Note

For more information about configuration sessions, see the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide specific to your release.