NEXUS MIGRATION PATH

[yassine144]

Hello ,

need to confirm the migration path for the following switches:

Cisco Nexus9000 C92348GC-X Chassis Current version: /nxos.9.3.2.bin
Proposed migration path: 9.3(2) => 9.3(14) => 10.3(6)M

Cisco Nexus9000 93180YC-EX chassis Current version: /nxos.9.3.3.bin
Proposed migration path: 9.3(3) => 9.3(14) => 10.3(6)M

Please confirm if these migration paths are correct and supported. thanks in advance

[MHM Cisco World]

Cisco Nexus 9000 and 3000 Upgrade and ISSU Matrix

[yassine144]

We need confirmation on the vPC compatibility and upgrade path for two independent, homogeneous vPC clusters in a production environment.
Cluster 1: Nexus 92348GC-X Pair

Switches: 2x Cisco Nexus 92348GC-X (NX-OS 9.3(2))

Planned Upgrade Path:

Step 1: Upgrade both switches to NX-OS 9.3(14)

Step 2: Upgrade both switches to NX-OS 10.3(6)M

Cluster 2: Nexus 93180YC-EX Pair

Switches: 2x Cisco Nexus 93180YC-EX (NX-OS 9.3(3))

Planned Upgrade Path:

Step 1: Upgrade both switches to NX-OS 9.3(14)

Step 2: Upgrade both switches to NX-OS 10.3(6)M

Key Questions

Cluster 1 (92348GC-X) Compatibility:

Is vPC supported between two Nexus 92348GC-X switches running:

NX-OS 9.3(2) (current)?

NX-OS 9.3(14) (intermediate)?

NX-OS 10.3(6)M (target)?

Cluster 2 (93180YC-EX) Compatibility:

Is vPC supported between two Nexus 93180YC-EX switches running:

NX-OS 9.3(3) (current)?

NX-OS 9.3(14) (intermediate)?

NX-OS 10.3(6)M (target)?

Upgrade Path Validation:

For 92348GC-X: Is the path 9.3(2) → 9.3(14) → 10.3(6)M officially supported

For 93180YC-EX: Is the path 9.3(3) → 9.3(14) → 10.3(6)M officially supported

In-Place vPC Compatibility During Upgrades:

Can we perform vpc between 9.3(2) 10.3(6)M for both clusters?

Are there risks if one switch in a cluster is temporarily on a different version during the upgrade?