cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
693
Views
1
Helpful
1
Replies

Cisco CBS350 Stacking Dual Active Detection

Hi.

I'm trying to build a resiliant spine and leaf topology with Cisco CBS switches but I have some concerns.

Here's my lab setup:

I have 2x CBS350-24XTS that are stacked together using ports 21-24 which forms my core stack. I have 1x CBS350-24FP4X used as an access switch connected through a portchannel from ports Te1/0/23 and Te1/0/24 of the CBS350-24FP4X to ports Te1/0/20 and Te2/0/20 of the CBS350-24XTS stack.

This works fine when every is up and running. I'm using a laptop that is connected to the access switch from which I do recurent "PING" to the SVI of the Core switcth. Here's are te results of my tests:

  • If I disconnect one interface port of my port channel, I sometimes lose a ping or 2  but everything stabilize after that. If I reconnect the cable nothing happens, still satble.
  • If I disconnect 3 out of the 4 cables used for stacking the two CBS350-24XTS, everything stay stable.
  • Once I disconnect the last cable used for stacking, I loose communication.
  • As soon as I disconnect one of the interface that forms the channel group, it starts comminicating again

On some switch, there is a "dual active detection" mecanism that will shutdown all port on the device that has the higest Unit number. Anybody has a suggestion of what I could do?

 

Here’s the syslog when I unlink the 2 core switches

SW1-CORE#23-Mar-2023 16:15:20 %CSCDLAG-W-DOWN: Stack port te21 operational status is Down
23-Mar-2023 16:15:21 %MLDP-W-ABORT: Connection to Unit 2 is aborted due to Stack Management notification.
23-Mar-2023 16:15:21 %TRUNK-W-PORTDOWN: Port te2/0/20 removed from Po1: port is down/notPresent
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/1
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/2
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/3
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/4
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/5
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/6
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/7
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/8
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/9
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/10
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/11
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/12
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/13
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/14
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/15
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/16
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/17
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/18
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/19
23-Mar-2023 16:15:21 %LINK-W-Not Present: te2/0/20
23-Mar-2023 16:15:21 %Stack-I-STCK-BCKUP-REM: standby unit 2 was removed from the stack.
23-Mar-2023 16:15:21 %Entity-I-SEND-ENT-CONF-CHANGE-TRAP: entity configuration change trap.

1 Accepted Solution

Accepted Solutions

Hi @jonathan.levesque 

  This switch model use the simple setup for stack which is Active and standby.  For split-brain or dual active detection we need switch with VSS support or stackwise virtual.

 What you are seing is the expected behavior.

https://www.cisco.com/c/en/us/support/docs/smb/switches/Cisco-Business-Switching/2899-2544-stack-settings-cbs-switch.html

 

View solution in original post

1 Reply 1

Hi @jonathan.levesque 

  This switch model use the simple setup for stack which is Active and standby.  For split-brain or dual active detection we need switch with VSS support or stackwise virtual.

 What you are seing is the expected behavior.

https://www.cisco.com/c/en/us/support/docs/smb/switches/Cisco-Business-Switching/2899-2544-stack-settings-cbs-switch.html