Port-channel not working between Nexus 5548UP and 6513 Catalyst Switch
I'm configuration 1 gig port-channelling between Nexus 5548UP and 6513 Catalyst Switch. I'm getting the error message "port-channel not connected on the catalyst switch". Channel-group is up on the nexus but down on the catalyst switch. The ports are all up on both switches. I'm suspecting firmware on the catalyst because it hasn't been upgraded since it was bought years ago. Has anyone came across this issue?
The Catalyst 6500 supports two port-channel control protocols, the proprietary Port Aggregation Protocol (PAgP) and the IEEE standard Link Aggregation Control Protocol (LACP). By contrast the Cisco Nexus only supports the standards based LACP.
The default mode on the Catalyst switch is PAgP which you should be able to see under the Protocol column in the output of the show etherchannel summary command on the Catalyst switch.
If that's the case then what you need to do is use the command channel-group 60 mode active on the port-channel member interfaces. To do this you'll have to remove and re-add the channel-group command as it doesn't allow the protocol to be changed on ports that are already assigned to a port-channel.
Hi Steve i tried it, still didn't come up! I did used LACP on both switches and the channel-group 60 mode has been set to active on both sides. The port-channel is up on the nexus but down on the catalyst which is weird. Don't you think the problem could be the firmware????
It's always possible that it's a bug, but I've got Catalyst 6500 with 12.2(18)SXF IOS running port-channel to Nexus switches so if it's a bug, then it's something Cisco broke.
Can you post the configuration of the physical and port-channel interfaces from both the Catalyst and Nexus switches? Also the output of a show etherchannel 60 detail and show lacp neighbor detail from the Catalyst, and a show port-channel summary and show lacp neighbor interface port-channel 60 from the Nexus?
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...