cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
520362
Views
103
Helpful
78
Comments
ashirkar
Level 7
Level 7

 

Introduction

The Cisco Virtual Switching System is a clustering technology that pools two Cisco Catalyst 4500-E Series Switches with Cisco Catalyst Supervisor Engine 7-E or 7-LE or two Catalyst 4500-X Series Switches into a single virtual switch. In a VSS, the data plane of both clustered switches is active at the same time in both chassis. VSS members are connected by virtual switch links (VSLs) using standard Gigabit or 10 Gigabit Ethernet connections between the VSS members. VSLs can carry regular user traffic in addition to the control plane communication between the VSS members.

Physical vs Logical Topology in a VSS Configuration

 

vss.jpg

 

This document describes how to configure a virtual switching system (VSS) for the Catalyst 4500 series switch (Supervisor Engine 7-E, Supervisor Engine 7L-E).

Some key point to be remembered for Cisco 4500 VSS

1) Configuration/Capability Supported supervisors on Catalyst 4500-E: VSS support Supervisor Engine 7-E or 7-LE (identical pairs).For more information about hardware to support please refer 4500 VSS Hardware requirement

2) Software requirement: Cisco IOS XE 3.4.0SG and ROMMON IOS Version 15.0(1r) SG7 later released support VSS.(Also refer How to Upgrade Cisco 4500 SUP7-E & Sup7L-E ROMMON To support VSS).

3)license requirement : 

To know more on license requirement refer "Release Notes for the Catalyst 4500E Series Switch"

Feature

LAN Base

IP Base

Enterprise Service

  • Virtual Switching System (VSS

 

No

Yes
(SUP7E only)

Yes

  • Support for Layer 3 MEC—VSS with Layer 3 Multichassis EtherChannel (MEC) at the aggregation layer

  • Support for VSLP Fast Hello—With VSLP Fast Hello, the Catalyst 4500-X configured for VSS can now connect Access Switches that do not support the ePAgP protocol.

  • Support for VSL Encryption

  • Support for Asymmetrix chassis

No

Yes (SUP7E)

No (SUP7LE)

Yes (SUP7E)

Yes (SUP7LE)

 

For information about Software Activation Licensing please refer Cisco Catalyst 4500E Supervisor 7-E and 7L-E and Cisco Catalyst 4500-X Series Software Activation Licensing Deployment Guide.

4) Single-sup cross-chassis VSS support: Yes.

5) Quad-sup VSS configuration with in-chassis redundant sups: In-chassis redundant sups in rommon mode with active uplinks.

6) It also supports 10 Gigabit Ethernet Virtual Switch Link (VSL) and 1 Gigabit Ethernet VSL.

7) SSO and nonstop forwarding (NSF) must be configured on each switch. If a VSS does not meet the requirements for SSO redundancy; it will be incapable of establishing a relationship with the peer switch. Catalyst 4500/4500-X series switches' VSS does not support route processor redundancy (RPR) mode.

Prerequisite

Before configuring VSS on Cisco 4500 please verify hardware and software requirement.

SW1#sh ver | in IOS
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSAL-M), Version 03.04.00.SG RELEASE SOFTWARE (fc3)
Cisco IOS-XE software, Copyright (c) 2005-2010, 2012 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE

SW1#sh ver | in ROM
ROM: 15.0(1r)SG7
System returned to ROM by power-on 

SW1#sh license image levels 
Module name       Image level Priority Configured Valid license
--------------------------------------------------------------------
WS-X45-SUP7-E     entservices  1         YES        entservices            
                  ipbase       2         NO         ipbase                
                  lanbase      3         NO         lanbase  
 
Module Name     Role           Current Level     Reboot Level
--------------------------------------------------------------------
WS-X45-SUP7-E  Active         entservices       entservices

 

SW2#sh ver | in IOS
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSAL-M), Version 03.04.00.SG RELEASE SOFTWARE (fc3)
Cisco IOS-XE software, Copyright (c) 2005-2010, 2012 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE

SW2#sh ver | in ROM
ROM: 15.0(1r)SG7
System returned to ROM by power-on

SW2#sh license image levels
Module name       Image level Priority Configured Valid license
--------------------------------------------------------------------
WS-X45-SUP7-E     entservices  1         YES        entservices            
                  ipbase       2         NO         ipbase                
                  lanbase      3         NO         lanbase 

Module Name     Role           Current Level     Reboot Level
--------------------------------------------------------------------
WS-X45-SUP7-E   Active        entservices       entservices

 

Configuration Steps

STEP1: Assigning Virtual Switch Domain and Switch Numbers

First you have to configure the same virtual switch domain number on both switches of the VSS. The virtual switch domain is a number between 1 and 255.After domain number you must configure one switch to be switch number 1 and the other switch to be switch number 2.

SW1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
SW1(config)#switch virtual domain 10
Domain ID 10 config will take effect only
after the exec command 'switch convert mode virtual' is issued
SW1(config-vs-domain)#switch 1
SW1(config-vs-domain)#exit
SW1(config)#

 

SW2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
SW2(config)#switch virtual domain 10
Domain ID 10 config will take effect only
after the exec command 'switch convert mode virtual' is issued
SW2(config-vs-domain)#switch 2
SW2(config-vs-domain)#exit
SW2(config)#

 

STEP2: Configuring VSL Port Channel

Then you need to configure VSL with a unique port channel on each switch. During the conversion, the VSS configures both port channels on the VSS Active switch. If the VSS Standby switch VSL port channel number has been configured for another use, the VSS comes up in RPR mode. To avoid this situation, check that both port channel numbers are available on both of the switches.

SW1(config)#int port-channel 5
SW1(config-if)#switchport
SW1(config-if)#switch virtual link 1
SW1(config-if)#no shut
SW1(config-if)#exit
*Jan 24 05:19:57.092: %SPANTREE-6-PORTDEL_ALL_VLANS: Port-channel5 deleted from all Vlans

 

SW2(config)#int port-channel 10
SW2(config-if)#switchport
SW2(config-if)#switch virtual link 2
SW2(config-if)#no shut
SW2(config-if)#exit
SW2(config)#
*Jan 24 05:14:17.273: %SPANTREE-6-PORTDEL_ALL_VLANS: Port-channel10 deleted from all Vlans

 

STEP3: configure the VSL ports

You need to add the VSL physical ports to the port channel. In the following example, interfaces Gigabit Ethernet 7/3 and 7/4 on Switch 1 are connected to interfaces Gigabit Ethernet 4/45 and 4/46 on Switch 2.

SW1(config)#int range gig7/3 - 4
SW1(config-if-range)#switchport mode trunk
SW1(config-if-range)#channel-group 5 mode on
WARNING: Interface GigabitEthernet7/3 placed in restricted config mode. All extraneous configs removed!
WARNING: Interface GigabitEthernet7/4 placed in restricted config mode. All extraneous configs removed!
SW1(config-if-range)#exit

 

SW2(config)#int range gig4/45 - 46
SW2(config-if-range)#switchport mode trunk
SW2(config-if-range)#channel-group 10 mode on
WARNING: Interface GigabitEthernet4/45 placed in restricted config mode. All extraneous configs removed!
WARNING: Interface GigabitEthernet4/46 placed in restricted config mode. All extraneous configs removed!
SW2(config-if-range)#exit

 

Note: Once the interfaces are put into VSL port-channel with “channel-group" command, then the interfaces goes into “notconnect” status. Interface status will show UP, but the line protocol will be down. The interface will be in UP/down (not connect) status, till the switch is rebooted in step 4.

STEP4: Converting the Switch to Virtual Switch Mode:

You need to enter the “switch convert mode virtual” command on Switch 1 for Converting to Virtual Switch Mode .After you enter this command it will prompted to confirm the action. Enter yes. The system creates a converted configuration file, and saves the file to the bootflash:

SW1#switch convert mode virtual 

This command will convert all interface names
to naming convention "interface-type switch-number/slot/port",
save the running config to startup-config and
reload the switch.
Do you want to proceed? [yes/no]: yes
Converting interface names
Building configuration...
Compressed configuration from 6551 bytes to 2893 bytes[OK]
Saving converted configuration to bootflash: ...
Destination filename [startup-config.converted_vs-20130124-062921]?
Please stand by while rebooting the system...
Restarting system. 

Rommon (G) Signature verification PASSED  
Rommon (P) Signature verification PASSED  
FPGA   (P) Signature verification PASSED

Similarly you need to enter the “switch convert mode virtual” command on Switch 2 for converting to Virtual Switch Mode.

 

SW2#switch convert mode virtual​ 

This command will convert all interface names
to naming convention "interface-type switch-number/slot/port",
save the running config to startup-config and
reload the switch.
Do you want to proceed? [yes/no]: yes
Converting interface names
Building configuration...
Compressed configuration from 6027 bytes to 2774 bytes[OK]
Saving converted configuration to bootflash: ...
Destination filename [startup-config.converted_vs-20130124-052526]?
Please stand by while rebooting the system...
Restarting system. 

Rommon (G) Signature verification PASSED  

Rommon (P) Signature verification PASSED  

FPGA   (P) Signature verification PASSED 

************************************************************
*                                                          *
* Welcome to Rom Monitor for   WS-X45-SUP7-E System.       *
* Copyright (c) 2008-2012 by Cisco Systems, Inc.           *
* All rights reserved.                                     *
*                                                          *
************************************************************

 

After you confirm the above commands on both switches, the running configuration is automatically saved as the startup configuration and the switch reboots. After the reboot, the switch is in virtual switch mode, so you must specify interfaces with three identifiers (switch/module/port).

When switches are being converted to VSS, you should not set them to ignore startup-config. If done, the switch can be enabled to parse the startup-config at the rommon prompt. Ignoring startup-config in VSS mode causes a switch to boot in a semi-VSS mode, which can only be corrected by a reboot and by enabling the parsing of startup-config.

Verification

1) To displays the virtual switch domain number, and the switch number and role for each of the switches you can use “show switch virtual” command.

SW1#sh switch virtual 

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

Switch mode                  : Virtual Switch
Virtual switch domain number : 10
Local switch number          : 1
Local switch operational role: Virtual Switch Active
Peer switch number           : 2
Peer switch operational role : Virtual Switch Standby 

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

Switch mode                  : Virtual Switch
Virtual switch domain number : 10
Local switch number          : 2
Local switch operational role: Virtual Switch Standby
Peer switch number           : 1
Peer switch operational role : Virtual Switch Active

 

2) Once both switches cluster in single virtual switch, you will only have Active switch console and your Standby switch console appears as follow:

SW2-standby> 
Standby console disabled

3) To displays the role, switch number, and priority for each of the switch in the VSS use “show switch virtual role” command.

SW1#sh switch virtual role 

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 )     100(100) ACTIVE   0       0
REMOTE  2     UP     FALSE(N )     100(100) STANDBY 6834   6152  

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 )     100(100) ACTIVE   6152   6834 

Peer 0 represents the local switch

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

 

4) To Displays information about the VSL use “show switch virtual link” command.

SW1#sh switch virtual link  

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

VSL Status : UP
VSL Uptime : 3 minutes
VSL Control Link : Gi1/7/4  

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

VSL Status : UP
VSL Uptime : 3 minutes
VSL Control Link : Gi2/4/45

 

5) You can also verify information about the VSL port channel using “show switch virtual link port-channel”command.

SW1#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
------+-------------+-----------+-------------------
5     Po5(SU)          -       Gi1/7/3(P) Gi1/7/4(P)
10    Po10(SU)         -       Gi2/4/45(P) Gi2/4/46(P)  

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
------+-------------+-----------+-------------------
5     Po5(SU)          -       Gi1/7/3(P) Gi1/7/4(P)
10    Po10(SU)         -       Gi2/4/45(P) Gi2/4/46(P) 

SW1#

Reference

Comments
MUQ_1899_
Level 1
Level 1

Have somebody tried to add/remove VSL links in production (there is always at least one active)? Is there impact for the VSS?

Robert.cotterman
Community Member

I have thoroughly tested this in a "non-official" way.

We tested pings going through two devices and popped off the vsl one at a time. and it performs just like a portchannel would. Any packets traversing that link are lost. but otherwise there is no impact. most systems can handle a packet loss.  The other question is bandwidth, I would suppose you lose bandwidth temporarily.

I am not sure how it divides bandwidth however, it doesn't seem to 1/1 round robin.  It might do it like other etherchannels, which you can specify with the command

(config)#Port-channel load-balance ?

and choose a way to do it.  This is likely the method it uses.  If so you always want 1, 2, 4 or 8 links for vss.  This is because load-balancing is based on binary, and since binary works in 2 4 or 8 bits. it divides that way, so if you have 7 links, 1 link will be designated 2 of 8 bits. and do the work of 2 lines.

Anyhow, you can add and remove with insanely minimal impact. However, do not remove all vss links at the same time, this will cause the standby machine to go into active, and neither will go back into standby unless reconnected AND rebooted.

If your network has zero loss requirements or has machines intolerant to any data loss, then your VSL link removing will cause a packet to drop, and that would "impact" your system.

Amrous_mohamed
Level 1
Level 1

hi all

i got issue with  Vss configuration on WS-C4507R+E with  WS-X4648-RJ45-E line  cards   and Sup 8L-E 10GE

when the chassis is on standalome mode the line card WS-X4648-RJ45-E  works correctly , but as i activate VSS mode ,  the line card   shown as Unsupported module

bellow show module

Switch Number: 2 Role: Virtual Switch Active

Chassis Type : WS-C4507R+E

Power consumed by backplane : 40 Watts

Mod Ports Card Type                              Model              Serial No.
---+-----+--------------------------------------+------------------+-----------
 1    12  10GE SFP+                              WS-X4712-SFP+E     CAT2020LB97
 2     0  Unsupported module                     WS-X4648-RJ45-E    JAE170905LU
 3     4  Sup 8L-E 10GE (SFP+), 1000BaseX (SFP)  WS-X45-SUP8L-E     CAT2024L88C

 M MAC addresses                    Hw  Fw           Sw               Status
--+--------------------------------+---+------------+----------------+---------
 1 cc16.7e03.0ce8 to cc16.7e03.0cf3 2.0                               Ok       
 2 001d.4505.2270 to 001d.4505.229f 2.4                               Unsupport
 3 b0fa.ebbd.b2c0 to b0fa.ebbd.b2c3 1.0 15.1(1r)SG6  03.08.01.E       Ok       

Mod  Redundancy role     Operating mode      Redundancy status
----+-------------------+-------------------+----------------------------------
 3   Active Supervisor   SSO                 Active     


for anoter costumer  the same chasis the same card ans sup card  il works correctly with no issue   bellow show module

Switch#sh module
Switch Number: 1 Role: Virtual Switch Active

Chassis Type : WS-C4507R+E

Power consumed by backplane : 40 Watts

Mod Ports Card Type                              Model              Serial No.
---+-----+--------------------------------------+------------------+-----------
 1    48  10/100/1000BaseT (RJ45)                WS-X4648-RJ45-E    JAE2017086U
 2    12  1000BaseX SFP                          WS-X4712-SFP-E     CAT2015L24C
 3     4  Sup 8L-E 10GE (SFP+), 1000BaseX (SFP)  WS-X45-SUP8L-E     CAT2019L82X

 M MAC addresses                    Hw  Fw           Sw               Status
--+--------------------------------+---+------------+----------------+---------
 1 0078.88e5.4844 to 0078.88e5.4873 2.2                               Ok       
 2 e00e.daa7.3f00 to e00e.daa7.3f0b 1.0                               Ok       
 3 00c8.8b9b.5a00 to 00c8.8b9b.5a03 1.0 15.1(1r)SG6  03.08.01.E       Ok       

Mod  Redundancy role     Operating mode      Redundancy status
----+-------------------+-------------------+----------------------------------
 3   Active Supervisor   SSO                 Active                            



the only diffirence between the two line cards (WS-X4648-RJ45-E)  is     HW  version   ,  for me  HW =2.4  for the other customer HW =2.2

please could you help me on this cas

thanks in advance

Amrous_mohamed
Level 1
Level 1

hi all

i got issue with  Vss configuration on WS-C4507R+E with  WS-X4648-RJ45-E line  cards   and Sup 8L-E 10GE

when the chassis is on standalome mode the line card WS-X4648-RJ45-E  works correctly , but as i activate VSS mode ,  the line card   shown as Unsupported module

bellow show module

Switch Number: 2 Role: Virtual Switch Active

Chassis Type : WS-C4507R+E

Power consumed by backplane : 40 Watts

Mod Ports Card Type                              Model              Serial No.
---+-----+--------------------------------------+------------------+-----------
 1    12  10GE SFP+                              WS-X4712-SFP+E     CAT2020LB97
 2     0  Unsupported module                     WS-X4648-RJ45-E    JAE170905LU
 3     4  Sup 8L-E 10GE (SFP+), 1000BaseX (SFP)  WS-X45-SUP8L-E     CAT2024L88C

 M MAC addresses                    Hw  Fw           Sw               Status
--+--------------------------------+---+------------+----------------+---------
 1 cc16.7e03.0ce8 to cc16.7e03.0cf3 2.0                               Ok       
 2 001d.4505.2270 to 001d.4505.229f 2.4                               Unsupport
 3 b0fa.ebbd.b2c0 to b0fa.ebbd.b2c3 1.0 15.1(1r)SG6  03.08.01.E       Ok       

Mod  Redundancy role     Operating mode      Redundancy status
----+-------------------+-------------------+----------------------------------
 3   Active Supervisor   SSO                 Active     


for anoter costumer  the same chasis the same card ans sup card  il works correctly with no issue   bellow show module

Switch#sh module
Switch Number: 1 Role: Virtual Switch Active

Chassis Type : WS-C4507R+E

Power consumed by backplane : 40 Watts

Mod Ports Card Type                              Model              Serial No.
---+-----+--------------------------------------+------------------+-----------
 1    48  10/100/1000BaseT (RJ45)                WS-X4648-RJ45-E    JAE2017086U
 2    12  1000BaseX SFP                          WS-X4712-SFP-E     CAT2015L24C
 3     4  Sup 8L-E 10GE (SFP+), 1000BaseX (SFP)  WS-X45-SUP8L-E     CAT2019L82X

 M MAC addresses                    Hw  Fw           Sw               Status
--+--------------------------------+---+------------+----------------+---------
 1 0078.88e5.4844 to 0078.88e5.4873 2.2                               Ok       
 2 e00e.daa7.3f00 to e00e.daa7.3f0b 1.0                               Ok       
 3 00c8.8b9b.5a00 to 00c8.8b9b.5a03 1.0 15.1(1r)SG6  03.08.01.E       Ok       

Mod  Redundancy role     Operating mode      Redundancy status
----+-------------------+-------------------+----------------------------------
 3   Active Supervisor   SSO                 Active                            



the only diffirence between the two line cards (WS-X4648-RJ45-E)  is     HW  version   ,  for me  HW =2.4  for the other customer HW =2.2

please could you help me on this cas

thanks in advance

Arjun Dabol
Level 1
Level 1

great article. 

can you please tell in what case we have VSL port-channel as 'switchport' and in what case we have as 'no switchport'

i see configuration of both types so want to understand .

thanks in adv

Skwerl234
Community Member

Following this guide connected our links with out any issues.  I would use the switchport method.

With that being said, no switchport makes a port layer 3.  This ends up needing it's own IP address, and I'm not sure how that would fly with using etherchannels.

However, it may act as a layer 2 port when etherchannel groups are put on it.

Just follow this guide.  Also note that both devices must be 100% identical.  If you try a 32 port 4500x and put it with a 16 port 4500x, it won't work.

As for 4507's etc... they may not need to be identical, as long as all the supervisor cards are identical.

I wouldn't see an issue with each chassis having different cards with different ports causing issues.

Also with 4500x's you should be able to add expansion cards with out an issue either.

bobjon
Cisco Employee
Cisco Employee

I have a pair of 4507's with Sup-7's in VSS running XE software version 03.05.02.e

and a pair of 4507's with Sup-8's in VSS running XE software version 03.08.01.e

What version release should I upgrade them to?

Aldmar Sousa
Level 1
Level 1

Guys, how are you doing? I hope you are guys doing really well. I have a question for you. At my distribution Layer there are 3 switches. On the switch of the middle, I have configured 2 VSLs(Of Course). My question is: Can I configure GLBP among them to do a load balance ?

Robert.cotterman
Community Member

Your question is too vague to answer directly, but I will do my best.

VSS makes two switches act like 1.

So, if you are trying to have two switches that are VSS'd together, act as GLBP separate routers, then NO you can't do that. A suitable alternative, would be to use Port channels with load balancing set to ip address, and whether it's source or destination would determine on which one has more ip address's. If you're a company with a lot of employee's, and minimal SaaS systems in use, I'd go for source, but if you're running a web server, then I'd go destination. also put it on the correct side of the link.  If a server is running and you're only working for internal users, then I'd put source on the user side, and destination on the server side.  Also, I would highly recommend BFD enabled on the port channels for minimal failover speeds.

Anyhow, the second option, is you have two stacks of VSS switches, and you want each stack to act as a GLBP router, then yes you can do that. OR if you have one VSS stack, and another stand alone device, they can each be a leg of the GLBP setup.

Just put in your mind that VSS is a variation of switch stacking.  It minimizes configuration needs, and also allows for redundancy, as you can put a fiber from each switch in the stack to another switch in your system, allowing either stacked switch to fail.  However, you can't program each piece of the stack to act as a different leg of GLBP.

I take this back, if you connect each switch in the VSS stack to your other switches, and each fiber connection is in a different VLAN, POSSIBLY cisco will let you set up different VLAN SVI's with a different leg of the GLBP setup, but I would imagine, cisco MIGHT have a block in this, also port channeling would likely be WAY more efficient, AND way simpler to program.

zidjali2007
Level 1
Level 1

Dears, 

Who can list the steps to upgrade the IOS for the switches which are configured in VSS mode. Without make the network down. Please anyone can help me  

Robert.cotterman
Community Member

First off, if you are asking this, you aren't googling enough, and you should look into what training you have done, and haven't done. This is a dangerous thing to not know.

But to get you started, you haven't said enough to be able to help.

First what switches are you using?  Every processor board NEEDS to restart during an update.

If you are VSSing two 4507's (or similar) with 2 processor boards each, then you can perform an ISSU upgrade. 

If you are VSSing two 4500x's with single processor boards each, then each half will need to reboot, so the only way that they can reboot without taking the network down, is by having redundant links to each individual switch, so that if one of your core nodes goes down, you aren't losing the network.

What i have said may seem harsh, and I apologize if it does, but you are treading on dangerous water, and should really consider what you have and haven't studdied/learned in your career so far, and should further your education.  I mean this only to boost your employment skills, and not as an insult.

pouryahashemian
Level 1
Level 1

Hi I have 4500x VSS and Layer 2 Etehrchanel with 8 ports Bundled in it that link To core uper network layer.

4 ports in switch number 1 and 4s are in switch2 . I have 8 servers that each of them  with 2 ports in Layer2  etherchannel to this swicth. Switch 1 is Active switch . After Traffic come from Server into switch and then go to 8 port for moving to uper layer  Traffic Just send from Switch1 to uper device.

Iwant redundancy between 2 switches and load balance between all 8 ports.

What's problem in VSS switches that sends Traffic only Active switch In layer2 etherchannels?

Eugen Bitca
Level 1
Level 1

7) SSO and nonstop forwarding (NSF) must be configured on each switch.

Do I need to have NSF configured before converting to VSS?

Thanks

shashi saranga
Level 1
Level 1

Hi Ashish

i have doubt that what will happened to port channels configured among VSS members if any member switch fails . It will forward traffic using remaining link or it will break the LACP port channel .

liju1488
Level 1
Level 1

hi,

thanks this post is really informative. myself have only deployed stacking. can u tell me how is this vss diffrent from stacking? the performance or the difftence in both these tecniques..

 

thank you

Liju.K

IBM-Netsol

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: