01-27-2025 06:42 PM
I am trying to configure what should be a very simple setup. Two 9800-Ls on a bench with a switch in between. They can ping each other when I configure SSO on both boxes, and I can ping the secondary. But neither will ever become the standby.
I'm wondering if there is "something else", that everyone always forgets to do when configuring SSO. Its so simple, just using vlan1 on both, with 192.168.1.x addresses.
Waiting for remote chassis to join
#######################################################################################
wc01:
interface Port-channel1
description ** uplink **
switchport mode trunk
!
interface Port-channel2
description ** uplink **
switchport mode trunk
interface TenGigabitEthernet0/1/0
switchport mode trunk
no negotiation auto
no mop enabled
channel-group 1 mode on
!
interface TenGigabitEthernet0/1/1
switchport mode trunk
no negotiation auto
channel-group 1 mode on
!
interface GigabitEthernet0
vrf forwarding Mgmt-intf
ip address 192.168.1.100 255.255.255.0
negotiation auto
no mop enabled
!
interface Vlan1
ip address 192.168.1.249 255.255.255.0 secondary
ip address 192.168.1.251 255.255.255.0
ip helper-address 192.168.1.254
no mop enabled
!
ip tftp source-interface GigabitEthernet0
ip route 0.0.0.0 0.0.0.0 192.168.1.254
ip route vrf Mgmt-intf 0.0.0.0 255.255.255.0 192.168.1.254
redun-management interface Vlan1 chassis 2 address 192.168.1.249 chassis 1 address 192.168.1.250
wc02:
!
interface Port-channel1
description ** uplink **
switchport mode trunk
!
interface Port-channel2
description ** uplink **
switchport mode trunk
!
interface TenGigabitEthernet0/1/0
switchport mode trunk
speed 1000 (its a 1gig SFP)
no negotiation auto
no snmp trap link-status
no mop enabled
channel-group 2 mode on
!
interface TenGigabitEthernet0/1/1
switchport mode trunk
speed 10000
no negotiation auto
no snmp trap link-status
channel-group 2 mode on
!
interface GigabitEthernet0
vrf forwarding Mgmt-intf
ip address 192.168.1.101 255.255.255.0
negotiation auto
no mop enabled
!
interface Vlan1
ip address 192.168.1.250 255.255.255.0 secondary
ip address 192.168.1.252 255.255.255.0
ip helper-address 192.168.1.254
no mop enabled
!
!
ip tftp source-interface GigabitEthernet0
ip route 0.0.0.0 0.0.0.0 192.168.1.254
ip route vrf Mgmt-intf 0.0.0.0 255.255.255.0 192.168.1.254
redun-management interface Vlan1 chassis 1 address 192.168.1.250 chassis 2 address 192.168.1.249
Could I be missing something? This should not be that difficult!!!
Solved! Go to Solution.
01-28-2025 11:16 AM
Device ID Local Intrfce Holdtme Capability Platform Port ID
edh001-001-wc01 Gig 0/25 178 R I C9800-L-F Ten 0/1/0
edh001-001-wc02 Gig 0/27 145 R I C9800-L-C Ten 0/1/0
Total cdp entries displayed : 2
9k_sw1#
interface GigabitEthernet0/25
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 1 mode on
!
interface GigabitEthernet0/26
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 1 mode on
!
interface GigabitEthernet0/27
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 2 mode on
!
interface GigabitEthernet0/28
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 2 mode on
!
interface Vlan1
description lab network
ip address 192.168.1.254 255.255.255.0
01-28-2025 11:21 AM
po1 links to wc01
po2 links to wc02.
The simplest of configs.
When I plug the cable from wc02 into the switch, it immediately changes the hostname:
edh001-001-wc02(recovery-mode)>
edh001-001-wc02(recovery-mode)>
edh001-001-wc02(recovery-mode)>
01-28-2025 02:42 PM
Can you change mode of PO from ON to active.
Note:- shut down PO before you do change and after you do change no shut
After you change mode share
Show Etherchannel summary
Show lacp neighbor
From SW
MHM
01-28-2025 04:31 PM
TLDR = nothing changed. Everything keeps behaving the same.
I have checked. The configs for the POs are identical, less the speed on one of them which is set to 1000 since the other end is 1000 and its a tengig interface.
I have done a stare and compare three times. The configs in the WLCs appear accurate. The POs must be configured correctly, since as soon as I plug BOTH controllers in, one will go to "edh001-001-wc01(recovery-mode)#". It doesn't do that when it is NOT plugged in. When it is not plugged in to the switch, the hostname is correct. Its only after connecting both controllers to the switch that makes it change its hostname. When only one controller is plugged into the switch, it works fine. Its only after I plug both in at the same time does this go sideways. Both controllers running 17.9.4
I created a new PO on each box, and instead of ON, used ACTIVE.
============== wlc1=============================
edh001-001-wc01#
interface Port-channel3
description ** uplink **
switchport mode trunk
!
interface Port-channel4
description ** uplink **
switchport mode trunk
!
!
interface TwoGigabitEthernet0/0/3 <--using this port as uplink
switchport mode trunk
speed 1000
no negotiation auto
no snmp trap link-status
no mop enabled
channel-group 3 mode active
!
edh001-001-wc01#sho etherchannel summ
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
A - formed by Auto LAG
Number of channel-groups in use: 4
Number of aggregators: 4
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(SD) - Te0/1/0(D) Te0/1/1(D)
2 Po2(SD) -
3 Po3(SU) LACP Tw0/0/3(P)
4 Po4(SD) -
edh001-001-wc01#sh lacp nei
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 3 neighbors
LACP port Admin Oper Port Port
Port Flags Priority Dev ID Age key Key Number State
Tw0/0/3 SA 32768 00d6.fe29.6a00 8s 0x0 0x3 0x11B 0x3D
edh001-001-wc01#
============== wlc2=============================
!
interface Port-channel3
description ** uplink **
switchport mode trunk
!
interface Port-channel4
description ** uplink **
switchport mode trunk
!
!
interface TwoGigabitEthernet0/0/3<--using this port as uplink
switchport mode trunk
speed 1000
no negotiation auto
no snmp trap link-status
no mop enabled
channel-group 4 mode active
edh001-001-wc02#sho etherchannel summ
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
A - formed by Auto LAG
Number of channel-groups in use: 4
Number of aggregators: 4
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(SD) -
2 Po2(SD) - Te0/1/0(D)
3 Po3(SD) -
4 Po4(SU) LACP Tw0/0/3(P) Te0/1/1(D)
edh001-001-wc02#sh lacp nei
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 4 neighbors
LACP port Admin Oper Port Port
Port Flags Priority Dev ID Age key Key Number State
Tw0/0/3 SA 32768 00d6.fe29.6a00 21s 0x0 0x4 0x11D 0x3D
Te0/1/1 SP 0 0000.0000.0000 5775s 0x0 0x0 0x0 0x0
edh001-001-wc02#
============== switch =============================
interface Port-channel3
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
!
interface Port-channel4
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
!
!
interface GigabitEthernet0/26 <--using this port as uplink
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 3 mode active
!
!
interface GigabitEthernet0/28 <--using this port as uplink
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event bundle-status
channel-group 4 mode active
!
9k_sw1#sho etherchannel summary ============== only wlc #1 plugged in =============================
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use N - not in use, no aggregation
f - failed to allocate aggregator
M - not in use, minimum links not met
m - not in use, port not aggregated due to minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
A - formed by Auto LAG
Number of channel-groups in use: 4
Number of aggregators: 4
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(SD) - Gi0/25(D)
2 Po2(SD) - Gi0/27(D)
3 Po3(SD) LACP Gi0/26(D)
4 Po4(SU) LACP Gi0/28(P)
9k_sw1#
9k_sw1# sho lacp nei
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 3 neighbors
Partner's information:
LACP port Admin Oper Port Port
Port Flags Priority Dev ID Age key Key Number State
Gi0/26 SP 32768 687d.b4fd.4640 426s 0x0 0x3 0x4 0x34
Channel group 4 neighbors
Partner's information:
LACP port Admin Oper Port Port
Port Flags Priority Dev ID Age key Key Number State
Gi0/28 SA 32768 8c1e.806e.9080 21s 0x0 0x4 0x4 0x3D
9k_sw1#
9k_sw1#
9k_sw1#
============== both WLCs plugged in =============================
adding wlc #2
Jan 28 16:24:43.661: %DTP-5-TRUNKPORTON: Port Gi0/28 has become dot1q trunk
Jan 28 16:24:45.157: %LINK-3-UPDOWN: Interface GigabitEthernet0/28, changed state to up
Jan 28 16:24:53.458: %EC-5-BUNDLE: Interface Gi0/28 joined port-channel Po4
Jan 28 16:24:54.466: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/28, changed state to up
Jan 28 16:24:55.461: %LINK-3-UPDOWN: Interface Port-channel4, changed state to up
Jan 28 16:24:56.462: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to up
WLC #2 changes its name:
edh001-001-wc02(recovery-mode)#
WLC #1 does not change its name:
edh001-001-wc01>
01-29-2025 02:29 AM
Can I see
Show lacp count <<- in cisco
MHM
01-29-2025 08:29 AM
I am going to write erase and reload. This has been a complete waste of my time.
01-29-2025 08:31 AM
I suspect with cable' especially if you use fiber
MHM
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