Just run a trunk between the two with all the VLANs you need while you are migrating. It will not be hitless when moving the port-channels, as the LACP ID's will not match between the 3850 and the VPC member switches. Be conscious of your gateways, and check spanning tree is forwarding on all the correct vlans on uplinks/downlinks.
Setup your VPC domain first, with a bunch of test bonded links before the migration. VPC will allow each nexus to send the same LACP ID so that the downstream device thinks it's the same switch. Then add the VLANs to be migrated. VPC - you should spend some serious time investigating, as there are a lot more scenarios that will stop forwarding traffic than a simple LACP aggregation. -----Original Message----- From: cisco-nsp <cisco-nsp-boun...@puck.nether.net> On Behalf Of Giles Coochey Sent: Wednesday, May 1, 2019 4:53 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Migrating a LACP bond on Catalyst to a vPC on Nexus This message originates from outside of your organisation. Hi All, Working for a client, they have a need to migrate a LACP bond from a Catalyst 3850 stack to a vPC bond on a Nexus pair (93180 TOR type) There is an existing trunk bond between the Catalyst 3850s and the Nexus so the Layer-2 is present across these and VLANs in the bond are the same on both switches. The endpoints on the bonds are hosts, and configured for LACP (channel-group x mode active), 2 ports per channel. What advice is there to migrate hosts on the 3850 stack to the Nexus, can it be performed in a hitless manner? Many Thanks! Giles _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
