I have spent last weeks configuring our new Cisco Nexus 5596UP switches in two data centers. The decision to use configuration synchronization feature (also known as Switch Profile) seemed logical as our new DC infrastructure design dictates to use Dual Homed FEXes with Active/Passive NIC teaming topology. This scenario (like any Dual Homed) requires almost all configuration to be identical on both switches that are part of vPC domain. Overall, I like this neat feature. In my humble opinion, Cisco had to come up with it years ago. It works like a charm if you are working on a clean deployment and follow Cisco guidelines. But… when it comes to the migration from Legacy configuration mode to the Switch Profile mode with both vPC domain switches already being pre-configured separately… well, you’ll definitely face some issues! I personally have spent few days trying to solve one puzzle that driven me nuts! Read more …
More and more Enterprises come to a decision to deploy Cisco Nexus switches in their corporate data centers. One of the main design considerations relates to Cisco 2200 Fabric Extenders (FEX) connectivity topology. To provide high availability Cisco Nexus 5500 series switches support different options to connect FEXes (all are based on a Virtual Port Channel feature):
- Straight-Through, where every FEX is connected to a single N5K (Active/Active and Active/Passive servers);
- Dual-Homed, where each FEX has one or more uplinks to two N5K switches (Active/Passive servers);
- Enhanced vPC, same as Dual-Homed but with Active/Active servers;
Each option has its own limitations and field of use, but this time we will concentrate our attention on the Dual-Homed FEX topology with Active/Standby Dual-Homed servers. Mainly because I recently deployed a pair of Cisco Nexus 5596UP switches with a number of Cisco 2248 TP-E Fabric Extenders using this approach.