Cisco 4500-X16 - VSS active and standby Not functioning properly

[asalim25105]

Hi

Cisco 4500-X16 switch configured  as VSS,but Active and Standby is not functioning properly.After few minutes not appearing in the "#show switch virtual role"  list.

VSS-CORE#sh switch virtual ro

Executing the command on VSS member switch role = VSS Active, id = 1

RRP information for Instance 1

--------------------------------------------------------------------
Valid Flags Peer Preferred Reserved
Count Peer Peer

--------------------------------------------------------------------
TRUE V 1 1 1

Switch Switch Status Preempt Priority Role Local Remote
Number Oper(Conf) Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1 UP FALSE(N ) 110(110) ACTIVE 0 0
REMOTE 2 UP FALSE(N ) 100(100) STANDBY 4791 4785

Peer 0 represents the local switch

Flags : V - Valid
In dual-active recovery mode: No

Executing the command on VSS member switch role = VSS Standby, id = 2

RRP information for Instance 2

--------------------------------------------------------------------
Valid Flags Peer Preferred Reserved
Count Peer Peer

--------------------------------------------------------------------
TRUE V 1 1 1

Switch Switch Status Preempt Priority Role Local Remote
Number Oper(Conf) Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 2 UP FALSE(N ) 100(100) STANDBY 0 0
REMOTE 1 UP FALSE(N ) 110(110) ACTIVE 4785 4791

Peer 0 represents the local switch

Flags : V - Valid
In dual-active recovery mode: No
--More-- %Timer expired.

VSS-CORE#

[Leo Laohoo]

What does the "sh logs" say?

[asalim25105]

Thank you for your reply

VSS-CORE#sh log
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: level debugging, 243 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 101 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 243 messages logged, xml disabled,
filtering disabled
Exception Logging: size (8192 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 245 message lines logged
Logging Source-Interface: VRF Name:

Log Buffer (32768 bytes):

*Oct 13 23:45:55.758: %C4K_IOSVSLENCR-3-VSLPMKKEYSTOREERROR: Failed to open PMK keystore file.
*Oct 13 23:45:55.779: %C4K_IOSSYS-6-IMAGELEVEL: Supervisor booting in image level 'ipbase'
*Oct 13 23:47:21.506: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session UP on slot 1 port 2.
*Oct 13 23:47:21.518: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session UP on slot 1 port 1.
*Oct 13 23:47:37.518: %VSLP-5-VSL_UP: Ready for control traffic

*Oct 13 23:47:42.519: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as STANDBY by VSLP
*Oct 13 23:48:12.523: %C4K_REDUNDANCY-6-INIT: STANDBY:Initializing as STANDBY supervisor
*Oct 13 23:48:21.850: %C4K_REDUNDANCY-6-DUPLEX_MODE: STANDBY:The peer Supervisor has been detected
*Oct 13 23:48:21.914: %C4K_REDUNDANCY-3-COMMUNICATION: STANDBY:Communication with the peer Supervisor has been established
Oct 14 07:09:59.870: %C4K_REDUNDANCY-6-MODE: STANDBY:STANDBY supervisor initializing for sso mode
Oct 14 07:10:00.334: %SPANTREE-5-EXTENDED_SYSID: STANDBY:Extended SysId enabled for type vlan
Oct 14 10:10:10.560: %SPANTREE-6-PORTDEL_ALL_VLANS: STANDBY:Port-channel5 deleted from all Vlans
Oct 14 10:10:10.696: %SPANTREE-6-PORTDEL_ALL_VLANS: STANDBY:Port-channel10 deleted from all Vlans
Oct 14 10:10:19.127: %SYS-5-RESTART: STANDBY:System restarted --
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSALK9-M), Version 03.05.00.E RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Tue 27-Aug-13 14:56 by prod_rel_team
Oct 14 10:10:19.158: %SSH-5-ENABLED: STANDBY:SSH 2.0 has been enabled
Oct 14 10:10:20.120: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/2/1 joined port-channel Port-channel20
Oct 14 10:10:20.184: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/1 joined port-channel Port-channel10
Oct 14 10:10:20.247: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/2 joined port-channel Port-channel10
Oct 14 10:10:20.251: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/3 joined port-channel Port-channel6
Oct 14 10:10:20.408: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/4 joined port-channel Port-channel2
Oct 14 10:10:20.492: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/5 joined port-channel Port-channel1
Oct 14 10:10:20.505: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/6 joined port-channel Port-channel3
Oct 14 10:10:20.599: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/7 joined port-channel Port-channel4
Oct 14 10:10:20.691: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/8 joined port-channel Port-channel7
Oct 14 10:10:22.075: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/9 joined port-channel Port-channel8
Oct 14 10:10:22.956: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/1/1 joined port-channel Port-channel5
Oct 14 10:10:23.014: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/1/2 joined port-channel Port-channel5
Oct 14 10:10:26.222: %C4K_IOSMODPORTMAN-6-MODULEONLINE: STANDBY:Module 1 (WS-C4500X-16 S/N: JAE182301X1 Hw: 1.1) is online
Oct 14 10:10:26.222: %C4K_IOSMODPORTMAN-6-MODULEONLINE: STANDBY:Module 2 (C4KX-NM-8 S/N: JAE182406A5 Hw: 1.0) is online
Oct 14 10:10:26.222: %C4K_IOSMODPORTMAN-6-MODULEONLINE: STANDBY:Module 11 (WS-C4500X-16 S/N: JAE182101FZ Hw: 1.1) is online
Oct 14 10:10:26.222: %C4K_IOSMODPORTMAN-6-MODULEONLINE: STANDBY:Module 12 (C4KX-NM-8 S/N: JAE182406ES Hw: 1.0) is online
Oct 14 10:10:29.883: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/1/9 joined port-channel Port-channel8
Oct 14 10:10:31.898: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/1/3 joined port-channel Port-channel6
Oct 14 10:10:31.901: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/1/5 joined port-channel Port-channel1
Oct 14 10:10:31.904: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/1/6 joined port-channel Port-channel3
Oct 14 10:10:31.907: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/1/7 joined port-channel Port-channel4
Oct 14 10:10:31.909: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/1/8 joined port-channel Port-channel7
Oct 14 10:10:32.025: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/2/1 joined port-channel Port-channel20
Oct 14 10:10:33.010: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/1/4 joined port-channel Port-channel2
Oct 14 14:25:09.029: %EC-5-UNBUNDLE: STANDBY:Interface TenGigabitEthernet2/1/8 left the port-channel Port-channel7
Oct 14 14:26:13.996: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/8 joined port-channel Port-channel7
Oct 14 16:10:29.300: %EC-5-UNBUNDLE: STANDBY:Interface TenGigabitEthernet2/1/6 left the port-channel Port-channel3
Oct 14 16:12:20.986: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/6 joined port-channel Port-channel3
Oct 14 16:12:39.794: %EC-5-UNBUNDLE: STANDBY:Interface TenGigabitEthernet2/1/7 left the port-channel Port-channel4
Oct 14 16:12:46.812: %EC-5-UNBUNDLE: STANDBY:Interface TenGigabitEthernet2/1/8 left the port-channel Port-channel7
Oct 14 16:13:56.977: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/8 joined port-channel Port-channel7
Oct 14 16:14:22.985: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/7 joined port-channel Port-channel4
Oct 14 16:17:34.792: %EC-5-UNBUNDLE: STANDBY:Interface TenGigabitEthernet1/2/1 left the port-channel Port-channel20
Oct 14 16:18:34.984: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet1/2/1 joined port-channel Port-channel20
Oct 15 07:21:29.962: %VSLP-3-VSLP_LMP_FAIL_REASON: STANDBY:Te1/1/1: Timeout (30000msec) waiting for Hello packet from peer
Oct 15 07:21:32.958: %VSLP-3-VSLP_LMP_FAIL_REASON: STANDBY:Te1/1/2: Timeout (30000msec) waiting for Hello packet from peer
Oct 15 07:21:32.958: %VSLP-2-VSL_DOWN: STANDBY: All VSL links went down while switch is in Standby role

Oct 15 07:21:32.958: %EC-5-UNBUNDLE: STANDBY:Interface TenGigabitEthernet1/1/1 left the port-channel Port-channel5
Oct 15 07:21:32.960: %EC-5-UNBUNDLE: STANDBY:Interface TenGigabitEthernet1/1/2 left the port-channel Port-channel5
Oct 15 07:21:32.973: %C4K_REDUNDANCY-6-INIT: Initializing as ACTIVE supervisor
Oct 15 07:21:33.310: %C4K_REDUNDANCY-3-COMMUNICATION: Communication with the peer Supervisor has been lost
Oct 15 07:21:33.528: %C4K_REDUNDANCY-3-SIMPLEX_MODE: The peer Supervisor has been lost
Oct 15 07:21:33.596: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/6 left the port-channel Port-channel3
Oct 15 07:21:33.598: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/7 left the port-channel Port-channel4
Oct 15 07:21:33.599: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/8 left the port-channel Port-channel7
Oct 15 07:21:34.232: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/1 left the port-channel Port-channel10
Oct 15 07:21:34.241: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/2 left the port-channel Port-channel10
Oct 15 07:21:34.269: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/3 left the port-channel Port-channel6
Oct 15 07:21:34.270: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/4 left the port-channel Port-channel2
Oct 15 07:21:34.272: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/5 left the port-channel Port-channel1
Oct 15 07:21:34.273: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/9 left the port-channel Port-channel8
Oct 15 07:21:34.274: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/2/1 left the port-channel Port-channel20
Oct 15 07:21:35.033: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session DOWN on slot 1 port 1.
Oct 15 07:21:35.268: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session DOWN on slot 1 port 2.
Oct 15 07:21:40.282: CDP-EV: RCVD CDP packet on TenGigabitEthernet1/2/1 with len (1)

Oct 15 07:21:40.283: CDP Packet Process DONE

Oct 15 07:23:28.367: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0150.b7c3.e6a9.73 declined 192.168.60.53.
Oct 15 07:23:42.359: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0114.109f.f077.de declined 192.168.22.49.
Oct 15 07:24:00.354: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.51.
Oct 15 07:24:19.792: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.63.
Oct 15 07:24:22.796: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.65.
Oct 15 07:24:23.941: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.66.
Oct 15 07:24:33.459: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.59.
Oct 15 07:24:40.487: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.71.
Oct 15 07:24:53.547: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.62.
Oct 15 07:25:02.563: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.67.
Oct 15 07:25:19.660: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.79.
Oct 15 07:25:26.699: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.82.
Oct 15 07:25:33.865: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.85.
Oct 15 07:25:55.490: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.79.
Oct 15 07:25:56.497: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.80.
Oct 15 07:25:59.628: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.92.
Oct 15 07:26:02.793: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.82.
Oct 15 07:26:03.813: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.83.
Oct 15 07:26:04.821: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.84.
Oct 15 07:26:05.870: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.85.
Oct 15 07:26:20.980: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.97.
Oct 15 07:26:27.029: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0150.bc96.c987.2f declined 192.168.60.68.
Oct 15 07:26:28.834: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0102.c3d9.3a83.7c declined 192.168.60.58.
Oct 15 07:26:28.889: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0126.3338.ab27.19 declined 192.168.22.77.
Oct 15 07:26:29.604: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01d6.0bde.376a.cd declined 192.168.22.87.
Oct 15 07:26:30.434: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01a4.1731.ee0b.d7 declined 192.168.22.56.
Oct 15 07:26:35.247: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.90.
Oct 15 07:26:40.271: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.92.
Oct 15 07:26:43.321: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.94.
Oct 15 07:26:46.341: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.96.
Oct 15 07:26:56.969: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01c0.e862.5f0b.52 declined 192.168.22.58.
Oct 15 07:26:59.724: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01aa.f9ea.a02f.61 declined 192.168.22.93.
Oct 15 07:27:13.671: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.102.
Oct 15 07:27:14.727: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.103.
Oct 15 07:27:35.851: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0174.70fd.6af0.5e declined 192.168.22.104.
Oct 15 07:28:15.554: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0162.6cde.fec2.18 declined 192.168.60.109.
Oct 15 07:28:32.410: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.118.
Oct 15 07:28:39.668: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.23.222.
Oct 15 07:28:40.952: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.109.
Oct 15 07:29:23.638: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session UP on slot 1 port 2.
Oct 15 07:29:23.665: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session UP on slot 1 port 1.
Oct 15 07:29:39.637: %VSLP-5-VSL_UP: Ready for control traffic

Oct 15 07:29:44.650: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE by VSLP
Oct 15 07:29:44.650: %EC-5-BUNDLE: Interface TenGigabitEthernet1/1/1 joined port-channel Port-channel5
Oct 15 07:29:44.660: %EC-5-BUNDLE: Interface TenGigabitEthernet1/1/2 joined port-channel Port-channel5
Oct 15 07:29:45.394: %C4K_REDUNDANCY-6-DUPLEX_MODE: The peer Supervisor has been detected
Oct 15 07:30:04.761: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.128.
Oct 15 07:30:23.677: %C4K_REDUNDANCY-6-MODE: ACTIVE supervisor initializing for sso mode
Oct 15 07:30:24.488: %C4K_REDUNDANCY-3-COMMUNICATION: Communication with the peer Supervisor has been established
Oct 15 07:30:28.052: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.112.
Oct 15 07:30:29.357: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.113.
Oct 15 07:30:36.824: %C4K_REDUNDANCY-5-CONFIGSYNC: The bootvar has been successfully synchronized to the standby supervisor
Oct 15 07:30:36.825: %C4K_REDUNDANCY-5-CONFIGSYNC: The config-reg has been successfully synchronized to the standby supervisor
Oct 15 07:30:36.826: %C4K_REDUNDANCY-5-CALENDAR: The calendar has been successfully synchronized to the standby supervisor for the first time
Oct 15 07:30:36.826: %C4K_REDUNDANCY-5-CONFIGSYNC: The startup-config has been successfully synchronized to the standby supervisor
Oct 15 07:30:37.447: %C4K_REDUNDANCY-5-CONFIGSYNC: The private-config has been successfully synchronized to the standby supervisor
Oct 15 07:30:38.222: %C4K_IOSINTF-5-TRANSCEIVERINSERTED: Slot=11 Port=9: Transceiver has been inserted
Oct 15 07:30:38.426: %C4K_REDUNDANCY-5-CONFIGSYNC_RATELIMIT: The vlan database has been successfully synchronized to the standby supervisor
Oct 15 07:30:39.221: %C4K_IOSINTF-5-TRANSCEIVERINSERTED: Slot=11 Port=10: Transceiver has been inserted
Oct 15 07:30:43.478: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 015c.3a45.77c7.cd declined 192.168.22.114.
Oct 15 07:30:46.221: %C4K_IOSINTF-5-TRANSCEIVERINSERTED: Slot=11 Port=1: Transceiver has been inserted
Oct 15 07:30:46.221: %C4K_IOSINTF-5-TRANSCEIVERINSERTED: Slot=11 Port=2: Transceiver has been inserted
Oct 15 07:30:46.221: %C4K_IOSINTF-5-TRANSCEIVERINSERTED: Slot=11 Port=3: Transceiver has been inserted
Oct 15 07:30:46.222: %C4K_IOSINTF-5-TRANSCEIVERINSERTED: Slot=11 Port=4: Transceiver has been inserted
Oct 15 07:30:46.222: %C4K_IOSINTF-5-TRANSCEIVERINSERTED: Slot=11 Port=5: Transceiver has been inserted
Oct 15 07:30:46.222: %C4K_IOSINTF-5-TRANSCEIVERINSERTED: Slot=12 Port=1: Transceiver has been inserted
Oct 15 07:31:09.083: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01dc.5360.a86d.49 declined 192.168.22.251.
Oct 15 07:31:11.228: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/1 joined port-channel Port-channel10
Oct 15 07:31:11.255: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/2 joined port-channel Port-channel10
Oct 15 07:31:13.906: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
Oct 15 07:31:13.930: %RF-5-RF_TERMINAL_STATE: 1 ha_mgr: Terminal state reached for (SSO)
Oct 15 07:31:14.375: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0152.30f7.687d.eb declined 192.168.22.116.
Oct 15 07:31:13.936: %C4K_IOSMODPORTMAN-6-MODULEONLINE: STANDBY:Module 1 (WS-C4500X-16 S/N: JAE182301X1 Hw: 1.1) is online
Oct 15 07:31:13.936: %C4K_IOSMODPORTMAN-6-MODULEONLINE: STANDBY:Module 2 (C4KX-NM-8 S/N: JAE182406A5 Hw: 1.0) is online
Oct 15 07:31:13.936: %C4K_IOSMODPORTMAN-6-MODULEONLINE: STANDBY:Module 11 (WS-C4500X-16 S/N: JAE182101FZ Hw: 1.1) is online
Oct 15 07:31:13.936: %C4K_IOSMODPORTMAN-6-MODULEONLINE: STANDBY:Module 12 (C4KX-NM-8 S/N: JAE182406ES Hw: 1.0) is online
Oct 15 07:31:18.228: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/9 joined port-channel Port-channel8
Oct 15 07:31:17.698: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/9 joined port-channel Port-channel8
Oct 15 07:31:20.225: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/3 joined port-channel Port-channel6
Oct 15 07:31:20.232: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/5 joined port-channel Port-channel1
Oct 15 07:31:20.235: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/6 joined port-channel Port-channel3
Oct 15 07:31:20.238: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/7 joined port-channel Port-channel4
Oct 15 07:31:20.242: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/10 joined port-channel Port-channel7
Oct 15 07:31:20.245: %EC-5-BUNDLE: Interface TenGigabitEthernet2/2/1 joined port-channel Port-channel20
Oct 15 07:31:21.228: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/4 joined port-channel Port-channel2
Oct 15 07:31:20.245: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/3 joined port-channel Port-channel6
Oct 15 07:31:20.248: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/5 joined port-channel Port-channel1
Oct 15 07:31:20.250: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/6 joined port-channel Port-channel3
Oct 15 07:31:20.253: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/7 joined port-channel Port-channel4
Oct 15 07:31:20.256: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/10 joined port-channel Port-channel7
Oct 15 07:31:20.352: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/2/1 joined port-channel Port-channel20
Oct 15 07:31:21.333: %EC-5-BUNDLE: STANDBY:Interface TenGigabitEthernet2/1/4 joined port-channel Port-channel2
Oct 15 07:31:27.119: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.118.
Oct 15 07:31:28.130: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.119.
Oct 15 07:31:40.014: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.123.
Oct 15 07:32:26.227: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 018e.52f3.2042.2d declined 192.168.60.122.
Oct 15 07:32:27.283: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.132.
Oct 15 07:32:31.303: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01b2.1166.c2e8.9e declined 192.168.22.130.
Oct 15 07:32:31.306: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 013e.1551.5ec9.85 declined 192.168.22.131.
Oct 15 07:32:49.564: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0134.7c25.cbcd.51 declined 192.168.22.135.
Oct 15 07:32:52.597: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01e4.0eee.42ae.7c declined 192.168.22.95.
Oct 15 07:32:55.139: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01e4.0eee.42ae.7c declined 192.168.22.136.
Oct 15 07:32:56.389: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.137.
Oct 15 07:32:58.048: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.138.
Oct 15 07:33:12.099: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 013c.2eff.ae23.ab declined 192.168.22.140.
Oct 15 07:33:12.573: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01a4.9b4f.0cfd.f1 declined 192.168.22.142.
Oct 15 07:33:13.881: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.144.
Oct 15 07:33:15.048: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.145.
Oct 15 07:33:35.960: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.150.
Oct 15 07:34:06.736: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.156.
Oct 15 07:34:55.879: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.160.
Oct 15 07:35:11.867: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.151.
Oct 15 07:35:22.904: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.153.
Oct 15 07:35:37.148: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01ea.4199.8f3f.48 declined 192.168.22.154.
Oct 15 07:37:00.522: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.160.
Oct 15 07:37:01.531: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.161.
Oct 15 07:38:11.198: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0180.b03d.7521.ac declined 192.168.60.174.
Oct 15 07:38:35.559: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.176.
Oct 15 07:39:29.344: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.179.
Oct 15 07:40:49.338: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.6 dBm, Threshold value: -13.9 dBm.
Oct 15 07:47:08.171: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.175.
Oct 15 07:47:09.175: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.176.
Oct 15 07:49:03.918: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.200.
Oct 15 07:50:49.437: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.7 dBm, Threshold value: -13.9 dBm.
Oct 15 07:50:49.803: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.187.
Oct 15 07:53:10.923: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 01c4.9f4c.84cb.3d declined 192.168.60.138.
Oct 15 07:53:29.712: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.214.
Oct 15 07:53:39.841: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.198.
Oct 15 07:55:10.011: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.222.
Oct 15 07:58:08.266: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 016c.4d73.a83b.c2 declined 192.168.60.199.
Oct 15 07:59:01.654: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 016a.bfd7.2446.69 declined 192.168.60.228.
Oct 15 08:00:49.538: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.7 dBm, Threshold value: -13.9 dBm.
Oct 15 08:01:05.831: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.231.
Oct 15 08:01:34.942: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.208.
Oct 15 08:01:50.572: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.210.
Oct 15 08:02:17.522: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.235.
Oct 15 08:02:22.186: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.60.237.
Oct 15 08:10:49.640: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.7 dBm, Threshold value: -13.9 dBm.
Oct 15 08:11:04.540: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.223.
Oct 15 08:11:19.924: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.225.
Oct 15 08:12:09.264: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.227.
Oct 15 08:12:42.418: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.230.
Oct 15 08:12:44.423: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0172.d64e.377d.ff declined 192.168.60.253.
Oct 15 08:14:01.324: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.61.2.
Oct 15 08:15:06.697: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.239.
Oct 15 08:15:10.708: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0190.17c8.650e.2d declined 192.168.60.61.
Oct 15 08:16:39.832: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.61.16.
Oct 15 08:19:11.002: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.246.
Oct 15 08:19:28.754: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.61.20.
Oct 15 08:19:31.789: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.61.22.
Oct 15 08:20:49.737: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.8 dBm, Threshold value: -13.9 dBm.
Oct 15 08:23:16.754: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.253.
Oct 15 08:23:18.330: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.22.254.
Oct 15 08:30:49.838: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.6 dBm, Threshold value: -13.9 dBm.
Oct 15 08:38:42.841: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.23.11.
Oct 15 08:39:02.380: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.23.13.
Oct 15 08:40:49.938: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.7 dBm, Threshold value: -13.9 dBm.
Oct 15 08:45:19.964: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.23.18.
Oct 15 08:50:50.042: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.7 dBm, Threshold value: -13.9 dBm.
Oct 15 08:52:02.161: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.61.52.
Oct 15 08:53:53.413: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.61.61.
Oct 15 09:00:16.066: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0180.c5f2.eb04.33 declined 192.168.23.26.
Oct 15 09:00:50.141: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.7 dBm, Threshold value: -13.9 dBm.
Oct 15 09:10:50.242: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.7 dBm, Threshold value: -13.9 dBm.
Oct 15 09:11:21.452: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.61.82.
Oct 15 09:20:13.557: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.23.47.
Oct 15 09:20:50.348: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.7 dBm, Threshold value: -13.9 dBm.
Oct 15 09:30:50.446: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.8 dBm, Threshold value: -13.9 dBm.
Oct 15 09:40:50.545: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.8 dBm, Threshold value: -13.9 dBm.
Oct 15 09:50:50.646: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.7 dBm, Threshold value: -13.9 dBm.
Oct 15 09:53:03.250: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.23.62.
Oct 15 10:00:50.746: %SFF8472-5-THRESHOLD_VIOLATION: Te2/1/10: Rx power low alarm; Operating value: -15.8 dBm, Threshold value: -13.9 dBm.
VSS-CORE#

[Leo Laohoo]

Great.  Very useful information from the logs.   Here's how it goes: 

10:10 local time, 14 October 2020:  Primary and Standby unit boots up, with 3.5.0 firmware, and forms a VSS pair. 

Oct 15 07:21:29.962: %VSLP-3-VSLP_LMP_FAIL_REASON: STANDBY:Te1/1/1: Timeout (30000msec) waiting for Hello packet from peer
Oct 15 07:21:32.958: %VSLP-3-VSLP_LMP_FAIL_REASON: STANDBY:Te1/1/2: Timeout (30000msec) waiting for Hello packet from peer
Oct 15 07:21:32.958: %VSLP-2-VSL_DOWN: STANDBY: All VSL links went down while switch is in Standby role

07:21, 15 October 2020:  Secondary unit crashes. 

Oct 15 07:29:44.650: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE by VSLP
Oct 15 07:29:44.650: %EC-5-BUNDLE: Interface TenGigabitEthernet1/1/1 joined port-channel Port-channel5
Oct 15 07:29:44.660: %EC-5-BUNDLE: Interface TenGigabitEthernet1/1/2 joined port-channel Port-channel5
Oct 15 07:29:45.394: %C4K_REDUNDANCY-6-DUPLEX_MODE: The peer Supervisor has been detected

07:29, 15 October 2020:  Secondary unit joins the VSS pair.

If you want to know why the Secondary crashes then you'll need to post the output to the command:

dir slavecrashinfo:

Additionally, you need to plan to upgrade the firmware because 3.5.0 is not stable.

[asalim25105]

07:21, 15 October 2020: Secondary unit crashes. - I have rebooted mannually bcz active switch is goes down suddenly and will not came up automatically ,there is internet drop also.

I have to reboot the switch to get it online.

dir slavecrashinfo:

VSS-CORE#dir slavecrashinfo:
Directory of slavecrashinfo:/

58466 -rw- 0 Jun 18 2014 14:10:03 +03:00 koops.dat

286718976 bytes total (284595200 bytes free)
VSS-CORE#

[Leo Laohoo · Accepted solution]

Upgrade the firmware of the switches.  Like I've said before, 3.5.0 is not stable. 
Read the Release Notes very carefully because there are versions where ROMMON upgrade is mandatory.

[asalim25105]

Thanks@Leo Laohoo

I have upgraded to 03.08.10 .Now It is working perfectly.