WS-C2960XR Failover Timeout

[NguyenHung2238]

Hi, 

When I do WS-C2960XR Stack Switch Failover Test,

My RDP from thin client to server disconnect.

Teaming both thin client side and server side. And log detail below. 

Any Idea what happing with this switch:

Apr 20 10:38:09.985: %STACKMGR-5-SWITCH_READY: Switch 1 is READY
Apr 20 10:38:11.544: %PHY-5-TRANSCEIVERINSERTED: Slot=1 Port=25: Transceiver has been inserted
Apr 20 10:38:11.673: %PNP-6-PNP_BEST_UDI_UPDATE: Best UDI [PID:WS-C2960XR-24TS-I,VID:V06,SN:] identified via (platform-registry)
Apr 20 10:38:11.673: %PNP-6-PNP_CDP_UPDATE: Device UDI [PID:WS-C2960XR-24TS-I,VID:V06,SN:] identified for CDP
Apr 20 10:38:11.676: %PNP-6-PNP_DISCOVERY_STOPPED: PnP Discovery stopped (Startup Config Present)
Apr 20 10:38:13.176: %USB_CONSOLE-6-MEDIA_RJ45: Console media-type is RJ45.
Apr 20 10:38:15.025: %CFGMGR-4-SLAVE_WRITING_STARTUP_CFG: only master can do that
Apr 20 10:38:15.025: %CFGMGR-4-SLAVE_WRITING_STARTUP_CFG: only master can do that
Apr 20 10:39:18.300: %STACKMGR-4-SWITCH_REMOVED: Switch 2 has been REMOVED from the stack
Apr 20 10:39:18.307: license_init_config_queue: initializing the license_switch_boot_config_q
Apr 20 10:39:18.310: %STACKMGR-4-MASTER_ELECTED: Switch 1 has been elected as MASTER of the stack
Apr 20 10:39:18.489: %CFGMGR-6-APPLYING_RUNNING_CFG: as new master
Apr 20 10:39:18.583: %SSH-5-ENABLED: SSH 1.99 has been enabled
Apr 20 10:39:18.625: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
Apr 20 10:39:18.628: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
Apr 20 10:39:18.628: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
Apr 20 10:39:18.632: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
Apr 20 10:39:18.999: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host x.x.x.x port 0 CLI Request Triggered
Apr 20 10:39:18.999: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.130.1.10 port 0 CLI Request Triggered
Apr 20 10:39:19.002: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host x.x.x.x port 0 CLI Request Triggered
Apr 20 10:39:19.369: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host x.x.x.x port 514 started - CLI initiated
Apr 20 10:39:19.369: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.130.1.10 port 514 started - CLI initiated
Apr 20 10:39:19.369: %STACKMGR-5-MASTER_READY: Master Switch 1 is READY
Apr 20 10:39:19.394: %COMMON_FIB-4-FIBIDB: No fibidb found for Virtual1 during address change
Apr 20 10:39:20.341: %LINK-3-UPDOWN: Interface Port-channel9, changed state to up
Apr 20 10:39:20.348: %LINK-3-UPDOWN: Interface Port-channel11, changed state to up
Apr 20 10:39:20.348: %LINK-3-UPDOWN: Interface Port-channel12, changed state to up
Apr 20 10:39:20.348: %LINK-5-CHANGED: Interface Vlan1, changed state to administratively down
Apr 20 10:39:20.355: %LINK-3-UPDOWN: Interface Vlan351, changed state to up
Apr 20 10:39:20.355: %LINK-3-UPDOWN: Interface Vlan352, changed state to up
Apr 20 10:39:20.359: %LINK-5-CHANGED: Interface FastEthernet0, changed state to administratively down
Apr 20 10:39:20.359: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan351, changed state to up
Apr 20 10:39:20.359: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan352, changed state to up
Apr 20 10:39:20.369: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host x.x.x.x port 514 started - CLI initiated
Apr 20 10:39:21.344: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel9, changed state to up
Apr 20 10:39:21.351: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel11, changed state to up
Apr 20 10:39:21.351: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel12, changed state to up
Apr 20 10:39:21.362: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to down

[balaji.bandi]

How is your Server connected, is the Server Dual Homed ? or single connection

is server configured LACP, can you give more information on this and configuration ?

[NguyenHung2238]

Hi,

Both server and thin client are enable teaming for 2 network port Active-Active

And use port channel to connect cisco switch 

interface Port-channel9
description Link To SGPSRYPAS-SW02-005 (51) FO Link
switchport trunk allowed vlan 351,352
switchport mode trunk
!
interface Port-channel11
description SRYTC-1153
switchport access vlan 351
switchport mode access
!
interface Port-channel12
description SRYTC-1154
switchport access vlan 351
switchport mode access

and Switch enable spanning tree:

spanning-tree mode rapid-pvst
spanning-tree portfast edge default
spanning-tree extend system-id 

[balaji.bandi]

Not sure we need more information - how this switch configured in terms of stacking

Switch 2 removed from Stack and Switch elected as MAster ? this is odd, most case switch 1 master and switch 2 act as salve

as per the Logs

all the Po gone down and come up .

Apr 20 10:39:20.341: %LINK-3-UPDOWN: Interface Port-channel9, changed state to up
Apr 20 10:39:20.348: %LINK-3-UPDOWN: Interface Port-channel11, changed state to up
Apr 20 10:39:20.348: %LINK-3-UPDOWN: Interface Port-channel12, changed state to up

can you post show etherchannel 9 summarty ( also for 11 and 12) and configuration of interface belong to Po 9 11 12

[NguyenHung2238]

Hi BB,

The Port Channel summary detail below :

SGPSRYPAS-SW02-008#sh etherchannel summary
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: 3
Number of aggregators: 3

Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
9 Po9(SU) - Gi1/0/25(P) Gi2/0/25(P)
11 Po11(SU) - Gi1/0/1(P) Gi2/0/1(P)
12 Po12(SU) - Gi1/0/2(P) Gi2/0/2(P)

All port change mode is on configuration below:

interface Port-channel9
description Link To SGPSRYPAS-SW02-005 (51) FO Link
switchport trunk allowed vlan 351,352
switchport mode trunk
!
interface Port-channel11
description SRYTC-1153
switchport access vlan 351
switchport mode access
!
interface Port-channel12
description SRYTC-1154
switchport access vlan 351
switchport mode access
!

interface GigabitEthernet1/0/1
description SRYTC-1153-Network1
switchport access vlan 351
switchport mode access
channel-group 11 mode on
!
interface GigabitEthernet1/0/2
description SRYTC-1154-Network1
switchport access vlan 351
switchport mode access
channel-group 12 mode on
!

interface GigabitEthernet1/0/25
description To SGPSRYPAS-SW02-005A (51) FO Link
switchport trunk allowed vlan 351,352
switchport mode trunk
channel-group 9 mode on

!

interface GigabitEthernet2/0/1
description SRYTC-1153-Network2
switchport access vlan 351
switchport mode access
channel-group 11 mode on
!
interface GigabitEthernet2/0/2
description SRYTC-1154-Network2
switchport access vlan 351
switchport mode access
channel-group 12 mode on
!

interface GigabitEthernet2/0/25
description To SGPSRYPAS-SW02-005B (51) FO Link
switchport trunk allowed vlan 351,352
switchport mode trunk
channel-group 9 mode on
!

Br,

Hung

[balaji.bandi]

channel-group 11 mode on  - this is not LACP ?

I can see switch side configuration looks ok (using 2 switch means dual home configured.), but i would suggest look at Server side configuration. (make sure it is LACP, do fail over remove 1 cable at a time and see if that was tested ?)

[NguyenHung2238]

Hi,

When I disconnect cable one by one, the no issue for RDP connection.

Only when I shutdown switch power, the RDP get disconnected. 

When power down slave switch, the RDP did not disconnect.

When power down master switch, the RDP disconnect around 5 sec

when disconnect cable one by one from server, RDP did not disconnect.

So the problem look like not from thin client and server. 

The issue look like from switching from member to master.

[balaji.bandi]

Post the complete configuration from the switch side to verify, (i still suggest making it LACP support rather than Mode ON)

as per the configuration provided high level other than LACP config, i do not see any issue. (that is the reason asking full config )

also post-show run  and  show switch

also worth checking Server config :

https://docs.microsoft.com/en-us/windows-server/networking/technologies/nic-teaming/nic-teaming-settings