- Cisco Community
- Technology and Support
- Networking
- Switching
- Re: Some questions about C2960X stacking.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Some questions about C2960X stacking.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2021 06:57 PM
Hello
I have some questions about C2960X stacking.
I am running C9300, C2960X as a form of stacking. (two switches each are used for stacking)
Unlike C9300 switches, when I rebooted the C2960X master switch for redundancy test, Packet loss happened for 30 seconds.
I don't know if it was normal phenomenon. So I analyzed logs.
According to logs, when the master switch went down, the slave switch took the master role and recalled master configuration. This process took around 30 seconds.
Is it normal phenomenon?
Plus, is it okay if I use a number 2 switch as master switch?
please refer to the configuration below
Master switch : switch 2 priority 15
Standby switch : switch 1 priority 1
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
1 54 WS-C2960X-48FPD-L 15.2(7)E3 C2960X-UNIVERSALK9-M
* 2 54 WS-C2960X-48FPD-L 15.2(7)E3 C2960X-UNIVERSALK9-M
Here is log
May 7 22:13:42.773 JST: %STACKMGR-4-SWITCH_REMOVED: Switch 2 has been REMOVED from the stack
May 7 22:13:42.780 JST: license_init_config_queue: initializing the license_switch_boot_config_q
May 7 22:13:42.790 JST: %STACKMGR-4-MASTER_ELECTED: Switch 1 has been elected as MASTER of the stack
May 7 22:13:43.786 JST: %CFGMGR-6-APPLYING_RUNNING_CFG: as new master
May 7 22:13:43.881 JST: %CNS IQ:0.1 ID:0 Changed:[switch]
May 7 22:13:43.881 JST: %CNS IQ:0.2 ID:1 Changed:[switch]
May 7 22:13:43.881 JST: %CNS IQ:0.3 ID:2 Changed:[switch]
May 7 22:13:43.912 JST: %SSH-5-ENABLED: SSH 1.99 has been enabled
May 7 22:13:44.024 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:notify syslog contenttype plaintext
May 7 22:13:44.024 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:hidekeys
May 7 22:13:44.031 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:path flash:/archive
May 7 22:13:44.031 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:maximum 5
May 7 22:13:44.034 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:write-memory
May 7 22:13:44.034 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:spanning-tree mode rapid-pvst
May 7 22:13:44.038 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:spanning-tree extend system-id
May 7 22:13:44.041 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:spanning-tree pathcost method long
May 7 22:13:44.153 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:vlan 10
May 7 22:13:44.153 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:name network_mgmt
May 7 22:13:44.248 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:interface Port-channel1
May 7 22:13:44.251 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:description Po1401
~~~~skip~~~~~
May 7 22:13:49.669 JST: %LINK-5-CHANGED: Interface GigabitEthernet1/0/3, changed state to administratively down
May 7 22:13:49.669 JST: %LINK-3-UPDOWN: Interface Port-channel13, changed state to down
May 7 22:13:49.672 JST: %LINK-5-CHANGED: Interface GigabitEthernet1/0/4, changed state to administratively down
May 7 22:13:49.672 JST: %LINK-3-UPDOWN: Interface Port-channel14, changed state to down
May 7 22:13:50.966 JST: %LINK-5-CHANGED: Interface GigabitEthernet1/0/5, changed state to administratively down
May 7 22:13:51.105 JST: %LINK-3-UPDOWN: Interface Port-channel15, changed state to down
May 7 22:13:51.109 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/6, changed state to down
May 7 22:13:51.109 JST: %LINK-3-UPDOWN: Interface Port-channel16, changed state to down
May 7 22:13:51.109 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/7, changed state to down
May 7 22:13:51.109 JST: %LINK-3-UPDOWN: Interface Port-channel17, changed state to down
May 7 22:13:51.112 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/8, changed state to down
May 7 22:13:51.112 JST: %LINK-3-UPDOWN: Interface Port-channel18, changed state to down
May 7 22:13:51.112 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/3, changed state to down
May 7 22:13:51.112 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/4, changed state to down
May 7 22:13:51.112 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/5, changed state to down
May 7 22:13:52.109 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/6, changed state to down
May 7 22:13:52.109 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/7, changed state to down
May 7 22:13:52.115 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/8, changed state to down
May 7 22:13:53.912 JST: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/0/1, changed state to up
May 7 22:13:53.944 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up
May 7 22:13:53.944 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to down
May 7 22:13:53.944 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to down
May 7 22:13:53.944 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/4, changed state to down
May 7 22:13:53.947 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to down
May 7 22:13:55.939 JST: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.128.201.7 port 514 started - CLI initiated
May 7 22:13:56.016 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to up
May 7 22:13:56.544 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to up
May 7 22:13:56.659 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to up
May 7 22:13:57.107 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/4, changed state to up
May 7 22:13:57.219 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/7, changed state to up
May 7 22:13:57.785 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/6, changed state to up
I hope someone gives me any solutions or documents or cisco links regarding this issue.
- Labels:
-
Catalyst 2000
-
LAN Switching
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2021 07:16 PM - edited 05-12-2021 07:26 PM
here is my comments :
According to logs, when the master switch went down, the slave switch took the master role and recalled the master configuration. This process took around 30 seconds.
BB - on what basis these 30 seconds ? by ping to switch IP address?
Looking at the logs Master offline - May 7 22:13:42. all ports up by May 7 22:13:57 - 15 seconds?
Is it a normal phenomenon?
BB - should be less than 30seconds - as per my testings. - again question related to above?
Plus, is it okay if I use a number 2 switch as master switch?
BB - sure any switch act as Master.
depends on this switch role, some other things take factor also - if you consider ping to determine the switch back online :
Look at some document stack processes and STP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2021 09:30 PM
Hi
First, thank you for your comment.
I hope you understand my poor English.
Actually, it was my first time handling stacking. And I didn't do the redundancy test in person. My client did it and asked me if it was the normal operation or not.
we are using two 2960X switches as Distribution switch(DS).
Our topology consists of BB -> DS -> AS -> Client in order.
I have some questions.
we are using C2960X switches as a form of stacking with Gi1/0/1-48, Gi2/0/1-48.
I think when I reboot the master switch, the slave switch will take the master role and only Gi1/0/1-48 interfaces will go down and will not configure again because the configuration are synced between members.
But as you can see the logs, when I rebooted the master switch, all interfaces(Gi1/0/1-48, Gi2/0/1-48) went down and the configuration was configured again.
I am not sure if this operation was normal or not.
My client did ping test from client to google DNS. And when my client rebooted the master switch, packet loss happened for 30 seconds.
you said BB - should be less than 30 seconds -> I want to know a normal convergence time when I reboot a master switch.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2021 09:52 AM
Hi
I have some questions about the operation of C2960X stacking after a master switch is rebooted.
I am using two C2960X as a form of stacking. And they are used as DS(distribution switch)
Our topology consists of BB -> DS -> AS -> Users in order.
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
1 54 WS-C2960X-48FPD-L 15.2(7)E3 C2960X-UNIVERSALK9-M
* 2 54 WS-C2960X-48FPD-L 15.2(7)E3 C2960X-UNIVERSALK9-M -> master switch
Our initial configuration
Master switch : switch 2 priority 15
Standby switch : switch 1 priority 1
I think when I reboot the master switch, the slave switch will take the master role and only Gi2/0/1-48 interfaces will go down and will not configure again because the configuration are synced between members.
But as you can see the logs, when I rebooted the master switch, all interfaces(Gi1/0/1-48, Gi2/0/1-48) went down and the configuration was configured again.
I am not sure if this operation was normal or not.
My client did ping test from client to google DNS. And when my client rebooted the master switch, packet loss happened for 30 seconds.
So I have three question about the operation of C2960X stacking.
1. Is it okay if I use a number 2 switch as master switch?
Actually it was wrong configuration, but I am using like this because it looks fine.
Our initial configuration
Master switch : switch 2 priority 15
Standby switch : switch 1 priority 1
2. I think when I reboot the master switch, the slave switch will take the master role and only Gi2/0/1-48 interfaces will go down and will not configure again because the configuration are synced between members.
But as you can see the below logs, when I rebooted the master switch, all interfaces(Gi1/0/1-48, Gi2/0/1-48) went down and the configuration was configured again.
is it normal operation?
3. is there any show command that I can check to see if two switches's configuration are synced.
here is log
May 7 22:13:42.773 JST: %STACKMGR-4-SWITCH_REMOVED: Switch 2 has been REMOVED from the stack
May 7 22:13:42.780 JST: license_init_config_queue: initializing the license_switch_boot_config_q
May 7 22:13:42.790 JST: %STACKMGR-4-MASTER_ELECTED: Switch 1 has been elected as MASTER of the stack
May 7 22:13:43.786 JST: %CFGMGR-6-APPLYING_RUNNING_CFG: as new master
May 7 22:13:43.881 JST: %CNS IQ:0.1 ID:0 Changed:[switch]
May 7 22:13:43.881 JST: %CNS IQ:0.2 ID:1 Changed:[switch]
May 7 22:13:43.881 JST: %CNS IQ:0.3 ID:2 Changed:[switch]
May 7 22:13:43.912 JST: %SSH-5-ENABLED: SSH 1.99 has been enabled
May 7 22:13:44.024 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:notify syslog contenttype plaintext
May 7 22:13:44.024 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:hidekeys
May 7 22:13:44.031 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:path flash:/archive
May 7 22:13:44.031 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:maximum 5
May 7 22:13:44.034 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:write-memory
May 7 22:13:44.034 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:spanning-tree mode rapid-pvst
May 7 22:13:44.038 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:spanning-tree extend system-id
May 7 22:13:44.041 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:spanning-tree pathcost method long
May 7 22:13:44.153 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:vlan 10
May 7 22:13:44.153 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:name network_mgmt
May 7 22:13:44.248 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:interface Port-channel1
May 7 22:13:44.251 JST: %PARSER-5-CFGLOG_LOGGEDCMD: User:vty1 logged command:description Po1401
~~~~skip~~~~~
May 7 22:13:49.669 JST: %LINK-5-CHANGED: Interface GigabitEthernet1/0/3, changed state to administratively down
May 7 22:13:49.669 JST: %LINK-3-UPDOWN: Interface Port-channel13, changed state to down
May 7 22:13:49.672 JST: %LINK-5-CHANGED: Interface GigabitEthernet1/0/4, changed state to administratively down
May 7 22:13:49.672 JST: %LINK-3-UPDOWN: Interface Port-channel14, changed state to down
May 7 22:13:50.966 JST: %LINK-5-CHANGED: Interface GigabitEthernet1/0/5, changed state to administratively down
May 7 22:13:51.105 JST: %LINK-3-UPDOWN: Interface Port-channel15, changed state to down
May 7 22:13:51.109 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/6, changed state to down
May 7 22:13:51.109 JST: %LINK-3-UPDOWN: Interface Port-channel16, changed state to down
May 7 22:13:51.109 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/7, changed state to down
May 7 22:13:51.109 JST: %LINK-3-UPDOWN: Interface Port-channel17, changed state to down
May 7 22:13:51.112 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/8, changed state to down
May 7 22:13:51.112 JST: %LINK-3-UPDOWN: Interface Port-channel18, changed state to down
May 7 22:13:51.112 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/3, changed state to down
May 7 22:13:51.112 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/4, changed state to down
May 7 22:13:51.112 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/5, changed state to down
May 7 22:13:52.109 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/6, changed state to down
May 7 22:13:52.109 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/7, changed state to down
May 7 22:13:52.115 JST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/8, changed state to down
May 7 22:13:53.912 JST: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/0/1, changed state to up
May 7 22:13:53.944 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up
May 7 22:13:53.944 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to down
May 7 22:13:53.944 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to down
May 7 22:13:53.944 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/4, changed state to down
May 7 22:13:53.947 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to down
May 7 22:13:55.939 JST: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.128.201.7 port 514 started - CLI initiated
May 7 22:13:56.016 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to up
May 7 22:13:56.544 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to up
May 7 22:13:56.659 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to up
May 7 22:13:57.107 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/4, changed state to up
May 7 22:13:57.219 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/7, changed state to up
May 7 22:13:57.785 JST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/6, changed state to up
switch 2 goes up
May 7 22:19:14.400 JST: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 1 Switch 1 has changed to state UP
May 7 22:19:14.400 JST: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 2 Switch 1 has changed to state UP
May 7 22:19:47.599 JST: %STACKMGR-4-SWITCH_ADDED: Switch 2 has been ADDED to the stack
May 7 22:20:00.514 JST: %STACKMGR-5-SWITCH_READY: Switch 2 is READY
May 7 22:20:00.514 JST: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 1 Switch 2 has changed to state UP
May 7 22:20:00.514 JST: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 2 Switch 2 has changed to state UP
May 7 22:20:03.712 JST: %STACKMGR-5-SWITCH_READY: Switch 2 is READY (switch)
~~~~~~skip~~~~~~~~~~~
May 7 22:20:11.657 JST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/3, changed state to up
May 7 22:20:11.657 JST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/5, changed state to up
May 7 22:20:11.657 JST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/8, changed state to up
May 7 22:20:11.664 JST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/2, changed state to up
May 7 22:20:11.664 JST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/6, changed state to up
May 7 22:20:11.664 JST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state to up
May 7 22:20:11.664 JST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/7, changed state to up
May 7 22:20:11.664 JST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to up
May 7 22:20:18.137 JST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/24, changed state to up
I would appreciate it if I can get an answer for my questions regarding this issue ASAP.
I really need your help...uu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2021 11:02 AM
what you mentioned is not normal, but we look forward what is configured in the switch
post-show run
you said BB - should be less than 30 seconds -> I want to know a normal convergence time when I reboot a master switch.
i have provided the document which gives you the data correct. depend if the standalone it should come as expected. but STP convergency other facts need to consider here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2021 01:56 PM
Unsure it also applies to 2960 series switches, but on the various 3750 series stacks, one issue with losing the master, by default, the stack's MAC changes with a new master (which causes "issues", such as a hit to STP). On a 3750 stack, though, there's a command to maintain the same MAC as used by the original stack master.
You might check if this is a possible issue, with a possible configuration command to address, on your 2960X switches.
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
