11-24-2020 03:10 AM
Hello,
we have running two Cat 4510 with four SUP8-E. The SUPs in slot 6 in both chassis are stopped in ROMMON and VSL was working fine and all ports are up and correctly aggregated.
In chassis 1 are ports Te1/5/1 and 1/6/1 bundled in etherchannel 64. In chassis 2 are ports Te2/5/1 and 2/6/1 bundled in etherchannel 63
We have powered off chassis 2 for a view hours because of working on the UPS system.
After powering on chassis 2 vss is coming up and seems to work correct. But the vsl link Te2/6/1 is shown as DOWN but link is up to Te1/6/1.
Can anybody tell me why Te2/6/1 is not shown in the vsl link and how I can solve this?
SW-CORE# sh switch virtual link port-channel Executing the command on VSS member switch role = VSS Active, id = 1 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, no aggregation due to minimum links not met m - not in use, port not aggregated due to minimum links not met u - unsuitable for bundling d - default port w - waiting to be aggregated Group Port-channel Protocol Ports ------+-------------+-----------+------------------- 64 Po64(SU) - Te1/5/1(P) Te1/6/1(w) 63 Po63(SU) - Te2/5/1(P) Te2/6/1(w) Executing the command on VSS member switch role = VSS Standby, id = 2 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, no aggregation due to minimum links not met m - not in use, port not aggregated due to minimum links not met u - unsuitable for bundling d - default port w - waiting to be aggregated Group Port-channel Protocol Ports ------+-------------+-----------+------------------- 64 Po64(SU) - Te1/5/1(P) Te1/6/1(D) 63 Po63(SU) - Te2/5/1(P)
11-24-2020 03:27 AM
Look at the logs.
11-24-2020 05:12 AM
i would suggest to check the config of the 2/6/1 - make sure it belong to right port-channel is the config still exists or lost?
Once you see the interface available in port-channel check the any cables issue, make sure they patched correctly right ports ?
11-24-2020 06:42 AM
The config has not been changed and the interfaces are configured in the correct port-channel
interface TenGigabitEthernet1/5/1 description VSL switchport mode trunk switchport nonegotiate no lldp transmit no lldp receive channel-group 64 mode on service-policy output VSL-Queuing-Policy end SW-CORE#sh run int ten 1/6/1 Building configuration... Current configuration : 208 bytes ! interface TenGigabitEthernet1/6/1 description VSL switchport mode trunk switchport nonegotiate no lldp transmit no lldp receive channel-group 64 mode on service-policy output VSL-Queuing-Policy end SW-CORE#sh run int ten 2/5/1 Building configuration... Current configuration : 208 bytes ! interface TenGigabitEthernet2/5/1 description VSL switchport mode trunk switchport nonegotiate no lldp transmit no lldp receive channel-group 63 mode on service-policy output VSL-Queuing-Policy end SW-CORE#sh run int ten 2/6/1 Building configuration... Current configuration : 208 bytes ! interface TenGigabitEthernet2/6/1 description VSL switchport mode trunk switchport nonegotiate no lldp transmit no lldp receive channel-group 63 mode on service-policy output VSL-Queuing-Policy end
In the lock I see that the sup has failed to boot. Both redundant sup8-e are in ROMMON mode
Nov 20 19:49:18: %C4K_IOSMODPORTMAN-4-POWERSUPPLYBAD: STANDBY:Power supply 1 has failed or been turned off Nov 20 20:33:15: %FASTHELLO-2-FH_DOWN: Fast-Hello interface Gi1/2/4 lost dual-active detection capability Nov 20 20:33:15: %EC-5-UNBUNDLE: Interface TenGigabitEthernet1/5/1 left the port-channel Port-channel64 Nov 20 20:33:15: %VSLP-3-VSLP_LMP_FAIL_REASON: Te1/5/1: Link down Nov 20 20:33:15: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/5/1 left the port-channel Port-channel63 Nov 20 20:33:15: %EC-5-UNBUNDLE: Interface TenGigabitEthernet1/6/1 left the port-channel Port-channel64 Nov 20 20:33:15: %VSLP-3-VSLP_LMP_FAIL_REASON: Te1/6/1: Link down Nov 20 20:33:15: %VSLP-2-VSL_DOWN: All VSL links went down while switch is in ACTIVE role Nov 20 20:33:15: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/6/1 left the port-channel Port-channel63 Nov 20 20:33:15: %C4K_REDUNDANCY-3-COMMUNICATION: Communication with the peer Supervisor has been lost Nov 20 20:33:15: %CHKPT-4-INVALID_ENTITY: Invalid checkpoint entity ID (1718908769). Nov 21 01:16:55: %SSH-5-DISABLED: STANDBY:SSH 2.0 has been disabled Nov 21 01:16:55: %SSH-5-ENABLED: STANDBY:SSH 2.0 has been enabled Nov 21 01:17:20: %SPANTREE-5-TOPOTRAP: Topology Change Trap for vlan 1 Nov 21 01:18:24: %EC-5-BUNDLE: Interface Te2/5/2 joined port-channel Po65 Nov 21 01:18:27: %EC-5-UNBUNDLE: Interface Te2/5/2 left the port-channel Po65 Nov 21 01:18:26: %EC-5-BUNDLE: STANDBY:Interface Te2/5/2 joined port-channel Po65 Nov 21 01:18:27: %EC-5-UNBUNDLE: STANDBY:Interface Te2/5/2 left the port-channel Po65 Nov 21 01:19:52: %EC-5-BUNDLE: Interface Te2/5/2 joined port-channel Po65 Nov 21 01:19:52: %EC-5-BUNDLE: STANDBY:Interface Te2/5/2 joined port-channel Po65 Nov 21 01:26:28: %SFF8472-5-THRESHOLD_VIOLATION: Te1/6/1: Rx power low alarm; Operating value: -28.8 dBm, Threshold value: -13.9 dBm. Nov 21 01:27:16: %C4K_SUPERVISOR-4-UNSUPPORTEDMODULE: STANDBY:Card in Slot(6) Failed to Boot
11-24-2020 07:15 AM
A couple of suggestions, take sup # 2 in each chassis out of the equation by taking them out of each chassis and just leave sup in slot 5 active and available in each chassis. After that reboot both chassis and hopefully everything boots as expected, if not you would need to open a ticket with TAC, so they can analyze the issue.
HTH
11-24-2020 07:18 AM
No way. I only can try to reboot the redundant SUPs but not the acitve one.
11-24-2020 08:03 AM
In that case, you can simply take the redundant sups out and redo the VSL Portchannels and hope it all comes back. Quad sup VSS issues are not simple. Any changes to the production switch should be done in a maintenance window as results can vary.
HTH
11-24-2020 03:38 PM
Post the complete output from BOTH units:
sh module
11-24-2020 07:19 AM
If you connected to console, then boot the Supervisor - once they come back only they should be able to form the connection ?
Looks like insufficient power or something failed - worth check you have enough power and both PSU are ON
%C4K_IOSMODPORTMAN-4-POWERSUPPLYBAD: STANDBY:Power supply 1 has failed or been turned off
11-24-2020 07:28 AM
No Power problem. Only the connector has been changed. This switch has four power supplies
11-24-2020 08:45 AM
can you post show modules from both the devices, looks some physical issue than config.
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