We were planning to move our existing M132 modules and replace it with F248-E modules. As of now, M132's take all downlinks to N5K (trunks - L2 only) . F2E will be in a VDC where we have other modules like M1/M2. We are testing this, and everything worked as expected , except :
1) After migrating to F248-E module on N7K1 - we reconfigured the peer link , and layer 2 links to N5k , and BOOOOM - the whole datacenter LAN segment reachability went down. This was probably because N5K was connected to AGGR1 on F2E module, and to AGGR2 on M132 module. It threw an error - " LOCAL CARD TYPE DOESNT MATCH WITH PEERS" and suspended all downlinks to N5K.
After we migrated the 2nd N7K also to F2E module - the problem was solved, but during the transit state - all the N5K segments lost L2 connectivity.
Is there a better way to do this upgrade ? Thanks to god - that this was a lab network.. If this was production, we would have lost access to all the servers in the datacenter.
Pleaseeeee help if there is a work around for this problem.
For instance, a vPC peer-link made of M1 interfaces on one side and of F2 interfaces on the other side is not supported. The peer-link should consist of either M1-only ports, F1-only ports, or F2-only ports on both vPC peer switches.
If the current N7k chassis does not have enough empty slots to host all the required F2 modules, a new chassis is needed for the migration procedure for each fully-loaded switch that already exists.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...