Interconnecting two VSS chassis

Hi,
Is it possible to connect a VSS chassis to another VSS chassis redundantly? The result being a redundant virtual switch connected to another redundant virtual switch. The objective is to use them in multiple datacenters i.e. a VSS in DC(1) providing redundant 10g ports for our servers, then another VSS in DC(2) for those local servers.
The two VSS chassis will be connected by two enhanced PAGP port channels, one for one set of data and another for other data
Is this even feasible?
Do I need to terminate the portchannels on the same switch at each datacenter or can they be distributed on to the different switches in the VSS? I hope this makes sense. Diagram attached.
Andy

Yes Reza said the right thing main thing to remember is the VSS Domain ID.
I have seen customer configuring same VSS domain ID for 2 cluster and we have to face music of running in to different issues.
HTH

Similar Messages

Redundancy for single IDSM on two separate chassis

Can EtherChannel protocol be used to provide active/standby redundancy for single IDSM on two different chassis.
Rgds.

From the given link, I understand that active/standby redundancy configuration is not possible for IDSM's on two different chassis. Only active/active is possible.
Secondly, please let me know whether the below configuration is for two IDSM's within same chassis or across two separate chassis.
intrusion-detection module 4 management-port access-vlan 100
intrusion-detection module 5 management-port access-vlan 100
intrusion-detection module 4 data-port 1 channel-group 5
intrusion-detection module 4 data-port 2 channel-group 6
intrusion-detection module 5 data-port 1 channel-group 5
intrusion-detection module 5 data-port 2 channel-group 6
intrusion-detection port-channel 5 trunk allowed-vlan 200-204,208
intrusion-detection port-channel 5 trunk allowed-vlan 708
intrusion-detection port-channel 5 autostate include
intrusion-detection port-channel 5 portfast enable
intrusion-detection port-channel 6 trunk allowed-vlan 260,280,400,401
intrusion-detection port-channel 6 trunk allowed-vlan 111-114
intrusion-detection port-channel 6 autostate include
intrusion-detection port-channel 6 portfast enable
Rgds.

6500 VSS Chassis in unknown state

Hi,
we have 6500 chassises in our set up. But using CWLMS 4.0 , we are unable to manage VSS feature of 6500.Also
User tracking for Nexus 7K Switches subnets are not working.
Please guide.
Rgrds,
Soumik.

Hi,
Would you mind posting some more information about the VSS problem. (Exact steps or maybe a screenshot of what you are doing). I didn't have any major issues configuring Cisco 6500 VSS in LMS or NCS. Minor ones were some SNMP MIBs which you can simply ignore.
Predrag Petrovic

Interconnecting two services in the composite applciation

Hi all,
I am consuming two services in my composite application. I need to pass separate set of data to my two services. The first service is Create PO and the second service is Create SO. I enter the iputs for Create PO first and on the Click of Submit button, the Create Po service shoulbe executed. At the same time the create SO service also should get executed with the different set of inputs that I provide.
The inputs that I provide for Create SO need not be seen externally. The user does not provide these inputs. The user only enters inputs for Create PO and clicks on Submit.
All the remaining action i.e., creating SO and displaying the SO should happen in the action of Submit. Please let me know how to write the action for Submit.
Thanks & Regards,
Srilakshmi B

Hi Srilakshmi,
Have two actions on your button:
1. createPoAction
2. createSoAction
Name the link from FormView to Create PO Web Service as createPoAction (select this from the drop down); and the link from FormView to Create SO Web Service as CreateSoAction.
Since you say,
The inputs that I provide for Create SO need not be seen externally
do the 'required' data mapping on the event (right clk. on the event) which invokes Create SO Web Service.
Now for,
>displaying the SO
drag a FormView from the output port of the Create SO Web Service (assuming your createSoMethod returns the created SO)
One button clk and you see the output!
-Vani

Interconnecting two Linksys Routers

I have two linksys routers WRT54G with Internet IP 10.254.1.58 and LAN IP 192.168.1.1 and the second Router WVRS4400N with Internet IP Address 10.254.1.67 and LAN IP 192.168.1.1. Both Routers use same Internet Gateway 10.254.1.1 and Subnet 255.255.255.0.
In WRT54G Router, there is a network Printer 192.168.1.50 connected to its LAN Port. Since both Routers are within the same building and the users connected to WVRS4400N cannot PRINT in the Network Printer connected to WRT54G Router. I would like to have users connected to both Routers to be able to share this Network Printer. Please help me how I can do Routing within the two Routers. Please HELP.
Pnjau

Let me know the kind of connection you are using .... are you using WRT54G router behind WRVS4400N router or vice versa .,....
Also let me know is the connection coming from any router ??

Interconnect two SG500's based on MGBBX1 or GLC-BX-D?

Hi,
I want to connect two SG500 switches on 150 meters distance. Do I realy need a MGBBX1 on one end and a GLC-BX-D on the other end?
Sounds wiered to me... Why is this?
Regards,
Klaas.
http://www.cisco.com/en/US/docs/interfaces_modules/csbna/mgb/quick_start/guide/Optical_Module_QSG_en-US.pdf

Hi,
For the Cisco MGBBX1, use the Cisco GLC-BX-D as the
downstream SFP. For the Cisco MFEBX1, use the Cisco GLC-FE-
100BX-D as the downstream SFP. The Cisco MGBBX1 and the
Cisco MFEBBX1 support upstream only
Since you use only one strand of fiber you have a different wavelength for sending in each direction.
One side is transmitting using the 1490 nm wavelength, and the other side is transmitting on 1310 nm wavelength (and receiving on the 1490nm).
The MGBBX1 only supports the -U upstream version afaik. From the acccess side to the core side of the network.
So in the core you need the other version, and there is no MGBBX1 SKU for this version.
if at all possible for 150m you should consider Multimode with 2 threads and MGBSX1 as
1000BASE-BX10 is capable of up to 10 km over a single strand of fiber.
hope that helps
jo

Wism2 redundancy in two C6513 chassis - Lost heartbeat with the Supervisor

I get a lot of messages in the trap log "Lost heartbeat with the Supervisor"
The controller seems to be up and running. Failover works perfectly.
Why do I get these messages?
Rgds Snorre

HI Snorre,
I get a lot of messages in the trap log "Lost heartbeat with the Supervisor"The controller seems to be up and running. Failover works perfectly.Why do I get these messages?
There are several possible reasons that this error message is generated. From the WiSM's perspective, the most common reason is an incorrect configuration of the service port on the Supervisor Engine.
In the case of a WiSM, the service port is used solely for communication between the Supervisor and the WiSM.
Complete these steps in order to get rid of this error message:
1. Create a new VLAN for the WiSM service ports on the Supervisor Engine that does not exist anywhere on the network.
2. Create a DHCP scope setup on your Supervisor to assign IP addresses to the service ports of the controllers.
Note: It is recommended that you create a DHCP scope for the service port of the Catalyst WiSM. Alternatively, you can also session (session slot X process 1 or 2 ) or console directly into the WiSM and set the static IP addresses with the configure interface address service-port command.
3. Assign the WiSM service ports to this newly created VLAN with the command wism service-vlan new VLAN ID on the Supervisor Engine.
This VLAN is used for the Supervisor Engine to communicate with the service port of the WiSM. Refer to Configure Communication Between the Supervisor and Cisco WiSM for more information on how to configure the procedure mentioned here.
Cisco bug ID CSCsg59144 is also associated with this error message.
Other possible reasons might be with the backplane connection of the module to the chassis This can be verified by first moving the WiSM to another slot and see if it continues. Sometimes, this might be an issue with the module itself. But these are rare circumstances.
Example:
Configure Communication Between the Supervisor 720 and Cisco WiSM
After the Cisco WiSM controller is installed in a slot and detected by the Supervisor, these configurations are made on the Supervisor Engine to communicate with WiSM.
1. Create a DHCP scope for the Service-Port of the Catalyst WiSM.
ip dhcp excluded-address 192.168.10.1 192.168.10.2
ip dhcp pool wism-service-port
network 192.168.10.0 255.255.255.0
default-router 192.168.10.1
Alternatively, you can also session (session slot X proc 1 or 2 ) or console directly into WiSM and set static IP addresses (config Interface Address Service-Port).
Make sure that the service port IP address is not a routable IP address in your network because it is only used for communication between the Sup 720 and the WiSM.
Note: VLSM is supported on all ports, which includes the Service port.
2. Create the WiSM Service Port Gateway and assign the IP address.
Create a VLAN in the Supervisor 720. This VLAN is local to the chassis and is used for communication between Cisco WiSM and Catalyst Supervisor 720 over a Gigabit Interface on the Supervisor and a service port in the Cisco WiSM.
    interface Vlan192
    Description WiSM Service Port Gateway
    ip address 192.168.10.1 255.255.255.0
Note: There should already be a network management VLAN interface to reach the Cat6k.
3. Assign the WiSM Service Ports to a VLAN.
Configure this command to use VLAN 192 to communicate with the service-port.
    wism service-vlan 192
Hope it helps.
Reagrds

ACE on VSS problem

I have a VSS cluster 2x6509 and an ACE blade in each I had to upgrade(ACE A2) the software so it could be recognised by the VSS. I have connectivity to the newtork from the first ACE ,but the second cannot arp it's default gatetway both ACE blade are on the same management vlan.
any help will be appreciated following is the config
svclc multiple-vlan-interfaces
svclc switch 1 module 1 vlan-group 1
svclc switch 2 module 1 vlan-group 1
svclc vlan-group 1 88
access-list ANY line 8 extended permit ip any any
policy-map type management first-match remote-access
class remote-mgmt
permit
interface vlan 88
description Axfood MGMT-LAN
ip address 194.132.91.239 255.255.255.128
access-group ANY
no shutdown
ip route 0.0.0.0 0.0.0.0 194.132.91.254
show arp
================================================================================
IP ADDRESS MAC-ADDRESS Interface Type Encap NextArp(s) Status
================================================================================
194.132.91.238 00.21.a0.82.8e.e9 vlan88 LEARNED 519 12340 sec up
194.132.91.239 00.21.a0.82.8e.39 vlan88 INTERFACE LOCAL _ up
194.132.91.251 00.25.46.21.c8.00 vlan88 LEARNED 518 4807 sec up
194.132.91.254 00.00.00.00.00.00 vlan88 GATEWAY - * 3 req dn
sho interface
switch/Admin# show int
vlan88 is up
Hardware type is VLAN
MAC address is 00:21:a0:82:8e:39
Mode : routed
IP address is 194.132.91.239 netmask is 255.255.255.128
FT status is non-redundant
Description:Axfood MGMT-LAN
MTU: 1500 bytes
Last cleared: never
Alias IP address not set
Peer IP address not set
Assigned from the Supervisor, up on Supervisor
45822 unicast packets input, 553642216 bytes
8022597 multicast, 218206 broadcast
0 input errors, 0 unknown, 0 ignored, 0 unicast RPF drops
301 unicast packets output, 33548570 bytes
0 multicast, 523889 broadcast
0 output errors, 0 ignored

It looks like you don't have FT (alias & peer IP's) set up.
If the second ACE still can't ARP or ping the gateway after you get that taken care of, check w/ TAC to see if you're hitting bug CSCsz50968.
We ran into it when we were doing a bunch of failover tests between the two VSS chassis.

VSS - Virtual Switch Domain Uniqueness Doubt

Hi everyone,
In the Cisco documentation, says that
You must configure the same virtual switch domain number on both switches of the VSS. The virtual switch domain is a number between 1 and 255, and must be unique for each VSS in your network.
My doubt is how can I understand the word network ?
I cannot use the same Virtual Switch Domain in a L2 Network, in a L3 Network, in a same customer Network ?
For example, if a customer has a lot of sites connected by a MPLS Wan, can I reuse the Virtual Switch Domain in each site ?
Thanks for Advanced
Andre Gustavo

You can re-use the virtual domain ID as long as the the two VSS chassis are not directly connecting to each other. Take a look at this link:
VVirtual Domain
Defining the domain identifier (ID) is the first step in creating a VSS from two physical chassis. A unique domain ID identifies two switches that are intended to be part of the same VSS pair that defines the VSS domain. Assignment of a domain ID allows multiple virtual switch pairs to be connected in a hierarchical manner. Only one VSS pair can participate in a particular domain. The domain ID can have a value ranging from 1 to 255 and must be unique when multiple VSS pairs are connected together. See Figure 2-2.
Figure 2-2 VSS Domain IDs
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/VSS30dg/campusVSS_DG/VSS-dg_ch2.html
Hope this helps!
Thanks you for rating useful posts!

IPS 4270 and VSS (Virtual Switch System)

HI,
I would like to know whether it is possible to connect just One IPS 4270 to a VSS in etherchannel mode (two IPS interfaces per each 6500 Switch).
Thanks in advance

You can re-use the virtual domain ID as long as the the two VSS chassis are not directly connecting to each other. Take a look at this link:
VVirtual Domain
Defining the domain identifier (ID) is the first step in creating a VSS from two physical chassis. A unique domain ID identifies two switches that are intended to be part of the same VSS pair that defines the VSS domain. Assignment of a domain ID allows multiple virtual switch pairs to be connected in a hierarchical manner. Only one VSS pair can participate in a particular domain. The domain ID can have a value ranging from 1 to 255 and must be unique when multiple VSS pairs are connected together. See Figure 2-2.
Figure 2-2 VSS Domain IDs
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/VSS30dg/campusVSS_DG/VSS-dg_ch2.html
Hope this helps!
Thanks you for rating useful posts!

CISCO VSS with different line cards in chassis

Dear Team,
We are planning to build VSS in our 6509 chassis with 2T SUP.
But my chassis line cards are diifferent. For example one chassis is having CISCO NAM service module and other one dont have NAM and one chassis is having 68XX series line cards and other one is having 67XX series line cards.
**Note: Both chassis are having same SUP 2T
Can we build VSS with this kind of scenarion? if it is possible any issues with VSS for this setup.
Kindly Advise.
Thanks & Regards,
Shine Salim

Yes you can form.
Q. How many Cisco Catalyst 6500 Series Switches can be part of a VSS?
A. The VSS1440 will allow up to two physical Cisco Catalyst 6500 Series Switches to operate as a VSS. The two physical chassis does not need to be identical in the type of modules installed or even type of chassis. For example, a WS-C6503-E chassis can be combined with a WS-C6513 chassis to form a VSS.
HTH

WLC 4402 LAG connection to 2 different chassis of 6509 VSS switch system

Hi,
I have inherited a 6509 VSS switch system as the network core and have the task of ensuring proper redundancy and redesign of the directly connected data center devices. One of the connected devices (WLC 4402) physically appears to be connected to both switches - the WLC is in the same rack as VSS-Chassis1 so I can trace the fiber from WLC port 1 to gi1/1/22, the other fiber from the WLC port 2 goes into the floor and presumably over to VSS-Chassis2 gi2/1/22 (there is fiber connected there, I have link lights on both sides, and the port channel, Po200, on the VSS switch which is configured on gi1/1/22 is also configured on gi2/1/22). My question pertains to the CDP neighbor output I get on the VSS switch: (truncated to include just the WLC)
NCMECHQWiFi1     Gig 1/1/22        137               H    AIR-WLC44 Gig 0/0/2
NCMECHQWiFi1     Gig 1/1/22        137               H    AIR-WLC44 LAGInterface0/3/1
NCMECHQWiFi1     Gig 1/1/22        137               H    AIR-WLC44 Gig 0/0/1
It looks like both WLC ports are physically connected to Gi1/1/22, which they are quite obviously not.
This is confirmed on the WLC's sho cdp entry all output:
(Cisco Controller) >show cdp entry all
Device ID: ncmec-vsscoresw1.ncmec.org
Entry address(es): 100.1.0.254
Platform: cisco WS-C6509-E, Capabilities: Router Switch IGMP
Interface: LAGInterface0/3/1, Port ID (outgoing port): GigabitEthernet1/1/22
Holdtime : 160 sec
I believe that the multi chassis etherchannel is set up correctly on the VSS:
vsscoresw1#sho run int gi1/1/22
interface GigabitEthernet1/1/22
description WLC-Management
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate
channel-group 200 mode on
end
vsscoresw1#sho run int gi2/1/22
interface GigabitEthernet2/1/22
description WLC-Management
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate
channel-group 200 mode on
end
vsscoresw1#sho run int po200
interface Port-channel200
description WLC-Management
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate
end
And yet when I show the details of port channel 200, I expect to see "mode on" but get instead see LACP which is unsupported on the WLC:
vsscoresw1#sho etherchannel 200 detail
Group state = L2
Ports: 2   Maxports = 8
Port-channels: 1 Max Port-channels = 1
Protocol:    -
Minimum Links: 0
                Ports in the group:
Port: Gi1/1/22
Port state    = Up Mstr In-Bndl
Channel group = 200         Mode = On      Gcchange = -
Port-channel = Po200       GC   =   -         Pseudo port-channel = Po200
Port index    = 0           Load = 0xFF        Protocol =    -
Mode = LACP
Age of the port in the current state: 180d:19h:47m:01s
Port: Gi2/1/22
Port state    = Up Mstr In-Bndl
Channel group = 200         Mode = On      Gcchange = -
Port-channel = Po200       GC   =   -         Pseudo port-channel = Po200
Port index    = 1           Load = 0xFF        Protocol =    -
Mode = LACP
Age of the port in the current state: 180d:19h:47m:02s
                Port-channels in the group:
Port-channel: Po200
Age of the Port-channel   = 354d:12h:47m:27s
Logical slot/port   = 46/19          Number of ports = 2
GC                  = 0x00000000      HotStandBy port = null
Port state          = Port-channel Ag-Inuse
Protocol            =    -
Fast-switchover     = disabled
Load share deferral = disabled
Ports in the Port-channel:
Index   Load      Port          EC state       No of bits
------+------+------------+------------------+-----------
0      FF       Gi1/1/22                 On   8
1      FF       Gi2/1/22                 On   8
Time since last port bundled:    173d:17h:06m:34s    Gi2/1/22
Time since last port Un-bundled: 173d:17h:06m:34s    Gi2/1/22
Last applied Hash Distribution Algorithm: Fixed
>>> So my question, arising at least partly from the apparently misleading CDP information, is this: How can I confirm that the WLC is correctly dual homed to both core switches? (short of tracing the cable) I ask because there are several other devices (not WLCs) that need to have the dual homed connections confirmed.
I tried a layer 2 trace route but for all macs associated with the WLC, the trace abborts with the error "Device has Multiple CDP neighbours on destination port."
Thanks in advance!
Sue

PS: It is critical that I confirm the redundancy, since as a part of the data center redesign we will be moving the second VSS chassis to the same rack with the first to simplify the dual connections. I need to verify all the redundant connections before I take it offline and move it. Thanks!

Ucs question about major code F0283 and dce interfac and chassis number?

dear,
Introductions:
one 6120 connect chassis 1 one 2104-1 and chassis 2 one 2104-1
chassis 1 have sever 3/4/5/6/7/8 (all sever is B200 M3,two 2104)
chassis 2 have sever 1/2/3/4/5/7 (sever 1/2/3/4 is B200 M3,two 2104)
question
1.major code F0283
all server have major code F0283 ,but all sever still can use.what this? How I did it?
affected object:sys/chassis-1/blade-6/fabric-A/path-1/vc-722
description: ether vif 1/6 a-722 down,reason: unknown
chassis 1 have sever 3/4/5/6/7/8
chassis 2 have sever 1/2/3/4/5/7
i shutdown all ,and start the problem is also.
affected
i shutdown all ,and start the problem is also.
2.on chassis 1 sever-1 adapter 1 dce interface (dce interfac 1 and dce interface 5)
ony one use?
3.
chassis 1 have sever 3/4/5/6/7/8
chassis 2 have sever 1/2/3/4/5/7
but i reboot ,
chassis 2 have sever 3/4/5/6/7/8
chassis 1 have sever 1/2/3/4/5/7
so the profile is disorder
i shtdown all,and start chassis 1 ok ,later chassis 2
the problem is ok..what this ?

Hi Hailing,
The transport VIF for server is down.The Cisco UCS Manager raises this fault when any of the following scenario occur:
•Endpoint(switch/fabric interconnect) reports the connectivity state on virtual interface as one of: a.down, b.errored, c.unavailable.
Verify that the blade discovery was completed successfully. Check the states on all of the communicating ports in an end to end manner.
If connectivity seems correct, recommision the server.
Also, please make sure you are using the correct drivers of the OS installed in the server as Padma recommended you.
I hope this helps.
David

How to avoid Dual Active VSS switches in the network...

Hi Team,
We have 2 nos of VSS switches in the network those are connected with 2 nos 10 Gbps uplink, all access switches are connected to both VSS chassis with dual uplinks, When we removed VSL link between these two vss switches both became active. We have completely Layer-2 network, is that any feature which we can use and avoid dual active scenario in VSS and make any one of the switch in standby mode and all Layer link on that switch will be available in case of VSL link goes down.
I have 3750X series switches are connected to both VSS Core switch It's world be much appreciated if some one provide well document on this and their suggestion.
Your reply will be much appreciated.
Thanks,
Vishal

Thanks for the reply Reza,
Please let me know if we go with Epagp then when VSL link goes down then what would be the result?
1st My there won't be any effect in the network, standby chassis remain in Standby Mode and active in Active Mode?
2nd Active chassis will reboot and became standby and my standby chassis will be Active?
3rd Standby chassis will be shutdown all port except VSL? and only Active chassis will work?
4th Active chassis will restart and shutdown all port except VSL? and standby chassis will be active?
5th ???
Reza it would be much helpful if you please guide how to configured EPagp on 6500 and 3750X switch with "c3750e-universalk9-mz.122-55.SE8.bin (ipservices)" image.
Thanks,
Vishal

Migrating VSS VSL to Different Ports

Alright all ye experts, I have a situation I'm hoping to pick your brains on. Here's the setup: Two 4510R+E with Sup7Es in a remote campus running VSS. The VSL for the VSS was configured on two of the 10Gb ports off of the supervisor (in a port-channel). The issue is that when I perform a failover and the supervisor reloads, the VSL drops and all of the line cards in that chassis drop until the VSL comes back up.
I'm thinking that if I move the VSL to the line cards it will separate the management plane/card from the data plane so when I perform an upgrade or have to fail over (for some reason) the line cards will remain up as the VSL will not be affected. The biggest challenge I'm up against is that the line cards are 1Gb and the ports for the VSL are 10Gb - thus I'm not able to just add ports to the port channel and migrate that way. Does anyone know if two VSLs can be run within the VSS environment? This would make the transition easier otherwise I'll need to bring down the VSL in order to move it.
I forgot to mention that this is a small regional hospital so there really is no good time for a "downtime", but if it needs to happen it needs to happen.
Thanks all!

In Catalyst 4500 VSS, the linecards will reset if the Supervisor reload. Hence when you do the switchover from Active VSS chassis to Standby VSS chassis, the Supervisor and linecards in previous Active chassis will reload and your VSL link will go down.
So moving the VSL link to ports on linecard will not help here.
With Catalyst 4500 VSS, you cannot have both chassis forwarding traffic at the time of VSS failover.
Moreover as Sharieff answered, you cannot have two VSL portchannel in a VSS system.
HTH

Interconnecting two VSS chassis

Similar Messages

Maybe you are looking for