vss 6500 adding a vsl link

Unanswered Question
Oct 9th, 2009

hi all ,

i'm looking for a way to add a 10GB link on a existing VSL Channel actually composed by one link.

i would like to be sure not going in dual-active mode

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Reza Sharifi Fri, 10/09/2009 - 08:29

A,

I would have an outage window just in case. Since you already have 2 diffrent port channels configure on you VSS boxes, all you have to do is add a second 10Gig link to the same port channels.

At the end, you config for you VSL links should look like this:

interface TenGigabitEthernet1/5/4

no switchport

no ip address

mls qos trust cos

channel-group 80 mode on

interface TenGigabitEthernet1/1/4

no switchport

no ip address

mls qos trust cos

channel-group 80 mode on

interface TenGigabitEthernet2/1/4

no switchport

no ip address

mls qos trust cos

channel-group 81 mode on

interface TenGigabitEthernet2/5/4

no switchport

no ip address

mls qos trust cos

channel-group 81 mode on

HTH

Reza

chrisgray1 Wed, 06/15/2011 - 05:56

I'm trying to do this exact procedure today, staging the kit for a customer.

We have had a single VSL etherchannel link to start with because only 1 10GB module was ordered with each chassis.

I've now come to add the second link into the etherchannel and the vsl will not come up over both links.

The second link simply doesn't come up when connected after the etherchannel config is applied, however if I pull the working VSL link, the second link comes on immediately but the active chassis goes into recovery mode and reboots. It then comes back up disabled, while the second chassis is active,

I can still bring the VSS up with one link but not with two connected.

If I restart both switches at the same time they do come up with one VSL link while the second stays down. My feeling is that maybe this is happening because the VSL etherchannel was not configured for two links before the switch was converted to virtual mode, however this is just guess work because I can see that the config looks ok..

interface Port-channel1

no switchport

no ip address

switch virtual link 1

mls qos trust cos

no mls qos channel-consistency

end

emea-oxf-vss#

emea-oxf-vss# sh run int po2

Building configuration...

Current configuration : 135 bytes

!

interface Port-channel2

no switchport

no ip address

switch virtual link 2

mls qos trust cos

no mls qos channel-consistency

end

emea-oxf-vss#

emea-oxf-vss#

emea-oxf-vss# sh run int t1/7/4

Building configuration...

Current configuration : 115 bytes

!

interface TenGigabitEthernet1/7/4

no switchport

no ip address

mls qos trust cos

channel-group 1 mode on

end

emea-oxf-vss# sh run int t1/7/5

Building configuration...

Current configuration : 115 bytes

!

interface TenGigabitEthernet1/7/5

no switchport

no ip address

mls qos trust cos

channel-group 1 mode on

end

emea-oxf-vss# sh run int t2/7/4

Building configuration...

Current configuration : 115 bytes

!

interface TenGigabitEthernet2/7/4

no switchport

no ip address

mls qos trust cos

channel-group 2 mode on

end

emea-oxf-vss# sh run int t2/7/5

Building configuration...

Current configuration : 115 bytes

!

interface TenGigabitEthernet2/7/5

no switchport

no ip address

mls qos trust cos

channel-group 2 mode on

end

emea-oxf-vss#sh switch virtual redundancy

                  My Switch Id = 1

                Peer Switch Id = 2

        Last switchover reason = none

    Configured Redundancy Mode = sso

     Operating Redundancy Mode = sso

Switch 1 Slot 7 Processor Information :

-----------------------------------------------

        Current Software state = ACTIVE

       Uptime in current state = 5 minutes

                 Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXI6, RELEASE SOFTWARE (fc4)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2011 by Cisco Systems, Inc.

Compiled Mon 28-Mar-11 12:09 by prod_rel_team

                          BOOT = bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXI6.bin,1;

        Configuration register = 0x2102

                  Fabric State = ACTIVE

           Control Plane State = ACTIVE

Peer information is not available because

it is in 'DISABLED' state

Rahul Kachalia Wed, 06/15/2011 - 15:58

Hello,

This should be simple as adding additional member-link to an existing EtherChannel. VSL leverages many of the existing EtherChannel design. Assuming there is no hardware issues (bad fiber/connectors etc) adding/links will not require any additional downtime and can be done in production network:

BEWARE VSS OPERATION WILL BE IMPACTED IF LAST MEMBER-LINKS FROM VSL ETHERCHANNEL IS REMOVED OR SHUTDOWN.

Refer to following logs as:

Setup

--------

Quad-Sup design with 4 VSL ports from SW1 and SW2 chassis

Removing VSL link from EtherChannel

-------------------------------------------------------

Dist-VSS#show module switch 1 | inc Supervisor

  5    5  Supervisor Engine 720 10GE (Active)    VS-S720-10G        SAD120407CT

  6    5  Supervisor Engine 720 10GE (RPR-Warm)  VS-S720-10G        SAD120407CL

Dist-VSS#show module switch 2 | inc Supervisor

  5    5  Supervisor Engine 720 10GE (Hot)       VS-S720-10G        SAL1205EWKX

  6    5  Supervisor Engine 720 10GE (RPR-Warm)  VS-S720-10G        SAD1205064R

Dist-VSS#show interface vsl

VSL Port-channel: Po1 

Port: Te1/5/4

Port: Te1/5/5

Port: Te1/6/4

Port: Te1/6/5

VSL Port-channel: Po2 

Port: Te2/5/4

Port: Te2/5/5

Port: Te2/6/4

Port: Te2/6/5

Removing Te1/5/4 and Te2/5/4 ports from VSL Port-Channel 1 and Port-Channel 2 interface :

Dist-VSS(config)#int te1/5/4

Dist-VSS(config-if)#no channel-group 1 mode on

Dist-VSS(config)#int te2/5/4

Dist-VSS(config-if)#no channel-group 2 mode on

Both chassis fully operational :

Dist-VSS(config-if)#do show module switch 1 | inc Supervisor

  5    5  Supervisor Engine 720 10GE (Active)    VS-S720-10G        SAD120407CT

  6    5  Supervisor Engine 720 10GE (RPR-Warm)  VS-S720-10G        SAD120407CL

Dist-VSS(config-if)#do show module switch 2 | inc Supervisor

  5    5  Supervisor Engine 720 10GE (Hot)       VS-S720-10G        SAL1205EWKX

  6    5  Supervisor Engine 720 10GE (RPR-Warm)  VS-S720-10G        SAD1205064R

interface Te1/5/4 and Te2/5/4 is removed from Port-Channel interface of each chassis:

Dist-VSS(config-if)#do show interface vsl

VSL Port-channel: Po1 

Port: Te1/5/5

Port: Te1/6/4

Port: Te1/6/5

VSL Port-channel: Po2 

Port: Te2/5/5

Port: Te2/6/4

Port: Te2/6/5

Adding VSL link to EtherChannel

------------------------------------------------

Dist-VSS#show run interface te1/5/4

interface TenGigabitEthernet1/5/4

no switchport

no ip address

logging event link-status

load-interval 30

end

Dist-VSS#show run interface t2/5/4

interface TenGigabitEthernet2/5/4

no switchport

no ip address

logging event link-status

load-interval 30

Dist-VSS#show interface vsl

VSL Port-channel: Po1 

Port: Te1/5/5

Port: Te1/6/4

Port: Te1/6/5

VSL Port-channel: Po2 

Port: Te2/5/5

Port: Te2/6/4

Port: Te2/6/5

Dist-VSS(config)#interface te1/5/4

Dist-VSS(config-if)#channel-group 1 mode on

Dist-VSS(config)#interface te2/5/4

Dist-VSS(config-if)#channel-group 2 mode on

Dist-VSS(config)#do show interface vsl

VSL Port-channel: Po1 

Port: Te1/5/4 <<<<<<<< Re added

Port: Te1/5/5

Port: Te1/6/4

Port: Te1/6/5

VSL Port-channel: Po2 

Port: Te2/5/4 <<<<<<<< Re added

Port: Te2/5/5

Port: Te2/6/4

Port: Te2/6/5

Nothing changed from chassis role-ownership perspective as we added/removed links from VSL EtherChannel.


5  Supervisor Engine 720 10GE (Active)    VS-S720-10G        SAD120407CT

  6    5  Supervisor Engine 720 10GE (RPR-Warm)  VS-S720-10G        SAD120407CL

Dist-VSS(config)#do show module switch 2 | inc Sup

  5    5  Supervisor Engine 720 10GE (Hot)       VS-S720-10G        SAL1205EWKX

  6    5  Supervisor Engine 720 10GE (RPR-Warm)  VS-S720-10G        SAD1205064R

Dist-VSS(config)#

Dist-VSS(config)#do show version | inc Up

Uptime for this control processor is 6 weeks, 1 day, 5 hours, 26 minutes

Refer to Chapter 2 for VSL best practices in following guide:

Borderless Campus 1.0 Design Guide

thanks,

rahul.

r.shummoogum Thu, 08/11/2011 - 18:33

Hi Christopher:

How did you fix that issue.

Reason: I ran into the same issue today and will troubleshoot tomorrow.

The port channel shows both members however only one appears in the VSL link. When I disconnect that link the other just pop up in the VSL link.

Thanks

r.shummoogum Fri, 08/12/2011 - 06:18

More info.

May be it is normal to only see one vsl link in the "show switch virtual link"

INITIAL STATE:


test#sh switch virtual link
VSL Status : UP
VSL Uptime : 17 hours, 23 minutes
VSL SCP Ping : Pass
VSL ICC Ping : Pass
VSL Control Link : Te1/4/1 

test#sh int vsl           

VSL Port-channel: Po10 
Port: Te1/4/1
Port: Te1/6/4

VSL Port-channel: Po11 
Port: Te2/4/1
Port: Te2/6/4

As you can see above the sh switch virtual link shows only one link.
When I disconnect Te1/4/1 then Te1/6/4 kicks in.


test#
*Aug 12 12:35:10.287: %VSLP-SW1_SP-3-VSLP_LMP_FAIL_REASON: Te1/4/1: Link down
*Aug 12 12:35:10.287: %VSL-SW1_SP-5-VSL_CNTRL_LINK:  New VSL Control Link Te1/6/4
*Aug 12 12:35:10.287: %VSLP-SW2_SPSTBY-3-VSLP_LMP_FAIL_REASON: Te2/4/1: Link down
*Aug 12 12:35:10.287: %VSL-SW2_SPSTBY-5-VSL_CNTRL_LINK:  New VSL Control Link Te2/6/4
test#

test#sh int vsl

VSL Port-channel: Po10 
Port: Te1/4/1
Port: Te1/6/4

VSL Port-channel: Po11 
Port: Te2/4/1
Port: Te2/6/4

test#sh switch virtual link
VSL Status : UP
VSL Uptime : 17 hours, 24 minutes
VSL SCP Ping : Pass
VSL ICC Ping : Pass
VSL Control Link : Te1/6/4 
test#

Rahul Kachalia Fri, 08/12/2011 - 08:38

Hello,

I m guessing when you say single link in VSL, you are comparing between number interfaces bundled in VSL EtherChannel (shown in "show interface vsl") versus VSL Control Link (shown in "show switch virtual link").

If I understood correctly, then there are no issues to VSL. The VSL is Layer 1 logical system interface. Out of multiple VSL bundled interfaces, during bootup process both chassis in virtual-switch mode negotiates and identifies just single interface to run all system control traffic.

System control traffic is all internal control and management communication to virtually manage the module/ports between two chassis. So even though when you have bundle multiple physical interfaces in VSL EtherChannel there will always single control-link needed. Rest are available for redundancy and handle data backplane if and when needed...

thanks,

rahul.

Actions

This Discussion