VSS configuration doubts

[vinodjad1234]

Hi,

I have doubt about vss configuration .................

If i want to configure the VSS , i need to follow the below procedure ....

1) first i need to configure the vss domain with switch virtual domain < domain number >  with switch ID  and with " switch priority "  command

2) i need to configure the vsl link ....

I will be configuring the two 10g ports with port channel ?

if suppose i want to use GBIC convertor and connect the same to ethernet 1g port , is it possible to make the vsl link configuration ?

i do not have provision to use direct 10g fiber link due to non-availability of 10g SFP ports connector ?

3) i need to configure the the physical port for the same to make bundle two ports ?

In my set-up i need to make two 10g ports from supervisor engine to bundle and configure for the VSL ..

4) then i need to configure the " switch convert mode virtual " command

that is all about i need to configure the VSS set-up ................

is there any thing i left out for completing the VSS configuration ?

I came across with some new commands which i need to configure for VSS ........... ?

I want to know , what is the use of this command and if i am not configuring the below command , what will happen ?

module provision switch 1

slot 1 slot-type 156 port-type 31 number 24  virtual-slot 17

slot 2 slot-type 227 port-type 60 number 8  virtual-slot 18

slot 5 slot-type 254 port-type 31 number 2 port-type 61 number 1 port-type 60 number 2  virtual-slot 21

module provision switch 2

slot 1 slot-type 156 port-type 31 number 24  virtual-slot 33

slot 2 slot-type 227 port-type 60 number 8  virtual-slot 34

slot 5 slot-type 254 port-type 31 number 2 port-type 61 number 1 port-type 60 number 2  virtual-slot 37

Please suggest me , for the same ...

It would be appriciative if i could get the answer for the same ....

[David Kosich]

Hi,

Your general understanding of configuring VSS seems to be correct. The VSL must be a port-channel, and it must be made up of 10 gig links.  You do not need to worry about those provision commands you listed. When you convert to VSS from two standalone chassis, those provision commands will be added to the VSS configuration for you. We do NOT recommend altering the provision commands.

You should also consider a Dual Active Detection mechanism, which is considered a best practice for VSS. In doing so, it will prevent an active/active type scenario should the  VSL ever go down. The configuration guide for VSS goes into the 3 available Dual Active Detection options.

Please keep in mind, in order to fully utilize the redundancy that comes with VSS, you must have all your connected devices dual homed to the VSS, meaning each device has a physical link to switch 1 and switch 2. In the case of servers or other devices that do not have dual nics, you could simply provide  a single link between it and its access layer switch, and then make sure the access layer switch is dual homed to the VSS.

Hope that helps,

Dave

RTP LAN-SWITCHING

[vinodjad1234]

Hi,

Thanks for your prompt reply.

for dual active scenario ,

I can connect one more link  between two chassis ,. and under that interface i can configure the " dual-active fast hello " command .

is it right ?

Please correct me if i am wrong ....

[David Kosich]

You are correct. Besides enabling it on the port on both sides of the link though, you would also have to enable 'dual-active detection fast-hello' under the switch virtual domain:
   
Router(config)# switch virtual domain domain_id
Router(config-vs-domain)# dual-active detection fast-hello

This is mentioned at the below link as well:

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/vss.html#wp1122676