Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Everyone,
Its kind of a stupid question but..
We are planning to replace our old NX5596 with 3132Q-V. There is a detailed document that explains the process and there is risk involved of things going south. We have multiple 40g ports available. I was wondering if it was in any way possible to setup another cluster network using these ports terminating on new switches? Once everything gets cabled and reachable we remove the old cluster switches. This will enable us to avoid the interim ISL between NX5596 and 3132Q-V.
Thank you
Solved! See The Solution
1 ACCEPTED SOLUTION
tahmad has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The cluster has one network. Theoretically, you can create an extra cluster lif and connect to the new switch.
My recommendation is to go through the tested process.
Replacing Cisco Nexus 5596 cluster switches with Cisco Nexus 3132Q-V cluster switches
3 REPLIES 3
tahmad has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The cluster has one network. Theoretically, you can create an extra cluster lif and connect to the new switch.
My recommendation is to go through the tested process.
Replacing Cisco Nexus 5596 cluster switches with Cisco Nexus 3132Q-V cluster switches
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also, the documentation is a bit confusing with the RCF files. Here's a gotcha you'll want to be aware of: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/Fabric%2C_Interconnect_and_Management_Switches/Switch_migration_from_CN1610_to_N...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Assuming you do not have AFF A320, AFF A250 or FAS500f in the cluster (nodes that use shared HA/cluster Ethernet ports), stick with RCF 1.1 files or RCF 1.6 files. Avoid RCF 1.3/1.4 versions since they change the native VLAN from 1 -> 92 and can create problems during cluster switch refresh.
Ref: https://mysupport.netapp.com/site/info/cisco-ethernet-switch
