08-02-2019 09:48 AM
Hi,
I have two Cisco C9300-24T switches arranged in a stack. I am trying to arrange two ports from each in the same port channel to two separate Nexus C93108TC-EX switches in what will eventually be a vPC configuration. I can't quite make them vPC, yet because of the brief service interruption that has incurred in the past to some of my other switches. I have to wait for our post-busy season before I add that functionality. In the meantime, I am trying to add these switches to a port channel. However, every time I attempt to do so, the two ports I assign from one switch or the other always goes into "suspended state." I tried adding/readding the ports to the port channel, bouncing the ports, and hard-coding LACP and speed and duplex settings, but nothing seems to work. Further, each time I added one of these features, the links from the both switches change place (meaning the two links from the Master switch change from "suspended" to "Passive", and vice-versa for the member switch) so it isn't consistently effecting one switch or the other. And If I remove the passive links from the channel-group, the suspended links come up.
Does anyone know my issue? The configs are below:
C9300 Switch Stack:
interface GigabitEthernet1/0/23
description To_Nexus_Core1
switchport mode trunk
speed 1000
duplex full
channel-protocol lacp
channel-group 1 mode active
interface GigabitEthernet1/0/24
description To_Nexus_Core1
switchport mode trunk
speed 1000
duplex full
channel-protocol lacp
channel-group 1 mode active
interface GigabitEthernet2/0/23
description To_Nexus_Core2
switchport mode trunk
speed 1000
duplex full
channel-protocol lacp
channel-group 1 mode active
interface GigabitEthernet2/0/24
description To_Nexus_Core2
switchport mode trunk
speed 1000
duplex full
channel-protocol lacp
channel-group 1 mode active
end
interface Port-channel1
switchport mode trunk
speed 1000
duplex full
end
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(SU) LACP Gi1/0/23(s) Gi1/0/24(s) Gi2/0/23(P)
Gi2/0/24(P)
#############################
Nexus Switch 1 (vPC core switche)
interface Ethernet1/8
description To_CC-BladeCtr1
switchport
switchport mode trunk
speed 1000
duplex full
channel-group 70 mode active
interface Ethernet1/9
description To_CC-BladeCtr1
switchport
switchport mode trunk
speed 1000
duplex full
channel-group 70 mode active
interface port-channel70
switchport
switchport mode trunk
speed 1000
duplex full
70 Po70(SD) Eth LACP Eth1/8(s) Eth1/9(s)
#############################
Nexus 2 (Other vPC core switch)
interface Ethernet1/8
description To_CC-BladeCtr2
switchport
switchport mode trunk
speed 1000
duplex full
channel-group 70 mode active
interface Ethernet1/9
description To_CC-BladeCtr2
switchport
switchport mode trunk
speed 1000
duplex full
channel-group 70 mode active
interface port-channel70
switchport
switchport mode trunk
speed 1000
duplex full
70 Po70(SU) Eth LACP Eth1/8(P) Eth1/9(P)
08-02-2019 10:37 AM
Hi,
If the nexus switches are not vPCed together, than you can't cross connect them to the stack of 9300 and build a Portchnnel.
Is that what you are trying to do?
Also, not that it matters but is there a reason you are not using the same Po ID on both the 9300 and The Nexus?
I see Po1 on the 9300 and 70 on the Nexus.
HTH
08-02-2019 12:50 PM
If Nexus environment non vPC mode, you have loop in the network. at this stage you mentioned you can not make it vPC on nexus.
in this case treat each link as seperate and make it trunk with required VLAN with spanning tree priority, so one link for odd vlan other one for even vlan to serve the purpose. this way you can still achive the goal what you looking.
when fix the vPC you can go back and review the setup and make vPC and Port-channel back
make sense ?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide