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!

Similar Messages

How to mornitor VSS (Virtual Switching System) & Stack (Switch) By Cisco Prime Infrastructure

Dear all,
I have 02 C6504-E with VSS (Virtual Switching System)
and 02 C3750X-24T-L used Stack
How to you Cisco Prime Infrastructure to monitor VSS & Stack tatus?
Thanks.

Virtual Switching technology is the process of combining two standalone distribution switches found in the local distribution layer into a single management point.
The Virtual Switching System functions and appears as a single switch to the wiring closet and the core layer. You can also create Virtual Switching Systems with a pair of standalone switches available in the core layer.
For configuration please check the below link:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/user/guide/configuration/configvss.html#wp1042960

Configuring and Troubleshooting Virtual Switching System (VSS)

With Anand Ganesan
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about how to monitor, configure, and troubleshoot the Virtual Switching System (VSS) in Cisco Catalyst 6500 Series Switches with expert Anand Ganesan.
VSS is network system virtualization technology that pools multiple Cisco Catalyst 6500 Series Switches into one virtual switch, increasing operational efficiency, boosting nonstop communications, and scaling system bandwidth capacity to 1.4 Tbps. At the initial phase, a VSS will allow two physical Cisco Catalyst 6500 Series Switches to operate as a single logical virtual switch called a virtual switching system 1440 (VSS1440).
For more information, visit: www.cisco.com/en/US/prod/collateral/switches/ps5718/ps9336/prod_qas0900aecd806ed74b.html
The VSS simplifies network configuration and operation by reducing the number of Layer 3 routing neighbors and by providing a loop-free Layer 2 topology.
Anand Ganesan is a customer support engineer in the High-Touch Technical Service team at Cisco specializing in switching protocols. He has been supporting major service providers and enterprise customers in switching and all other switching technologies for more than two years with Cisco. He has a total of eight years of experience in the IT industry. He holds a bachelor of engineering degree from Bharathiyar University, Coimbatore.
Remember to use the rating system to let Anand know if you have received an adequate response.
Because of the volume expected during this event, Anand might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure subcommunity, LAN Switching & Routing shortly after the event. This event lasts through September 6, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Okay..they are two different /30 networks.
my BFD interfaces are GigabitEthernet1/3/48 and GigabitEthernet2/3/48 and they work fine.
interface GigabitEthernet1/3/48
description Switch 1 BFD Interface
no switchport
ip address 10.48.0.17 255.255.255.252
bfd interval 100 min_rx 100 multiplier 3
end
interface GigabitEthernet2/3/48
description Switch 2 BFD Interface
no switchport
ip address 10.48.0.21 255.255.255.252
bfd interval 100 min_rx 100 multiplier 3
end
switch virtual domain 1
switch mode virtual
switch 1 priority 110
dual-active pair interface GigabitEthernet1/3/48 interface GigabitEthernet2/3/48 bfd
show switch virtual dual-active bfd
Bfd dual-active detection enabled: Yes
Bfd dual-active interface pairs configured:
interface-1 Gi1/3/48 interface-2 Gi2/3/48
router eigrp 1
network 10.0.0.0
network 10.1.201.0 0.0.0.255
network 10.48.0.12 0.0.0.3
network 10.48.177.0 0.0.0.255
network 97.0.0.0
network 99.0.0.0
network 100.0.0.0
network 100.7.7.0 0.0.0.255
network 192.34.145.0
network 192.168.15.0
show ip ei in
EIGRP-IPv4 Interfaces for AS(1)
                       Xmit Queue   Mean   Pacing Time   Multicast   Pending
Interface       Peers Un/Reliable SRTT   Un/Reliable   Flow Timer   Routes
Gi1/2/40           1       0/0         1       0/1           50           0
Gi1/2/41           0       0/0         0       0/1           0           0
Vl1               1       0/0         1       0/1           50           0
Vl7               0       0/0         0       0/1           0           0
Vl13               0       0/0         0       0/1           0           0
Vl15               0       0/0         0       0/1           0           0
Vl21               0       0/0         0       0/1           0           0
Vl25               0       0/0         0       0/1            0           0
Vl26               0       0/0         0       0/1           0           0
Vl134             0       0/0         0       0/1           0           0
Vl135             0       0/0         0       0/1           0           0
Vl140             0       0/0         0       0/1           0           0
Vl300             0       0/0         0       0/1           0           0
Vl400             0       0/0         0       0/1           0           0
Vl199             0       0/0         0       0/1           0           0
Vl6               0       0/0         0       0/1           0           0
Vl20               0       0/0         0       0/1           0           0
Vl24               0        0/0         0       0/1           0           0
Vl30               0       0/0         0       0/1           0           0
Vl31               0       0/0         0       0/1           0           0
Vl37               0       0/0         0       0/1           0           0
Vl2               0       0/0         0       0/1           0           0
Gi1/3/48           0       0/0         0       0/1           0           0
Gi2/3/48           0       0/0         0       0/1           0           0
Vl17               0       0/0         0       0/1           0           0
Gi2/6/40           0       0/0         0       0/1           0           0
Gi2/6/41           0       0/0         0       0/1           0           0
Gi2/1/45           1        0/0         1       0/1           50           0
Gi1/1/33           1       0/0         1       0/1           50           0
My questions revolve around the same point.
Are there any significance in running eigrp or any other routing protocol over this BFD link?
Is the Dual active scenario detected by BFD or BFD notifies a routing protocol like eigrp and in turn dual active is detected?
Should I suppress the eigrp HELLOs on these interfaces to get rid of the log message?
Regards
Vinayak

WiSM-2 in 6500 running VSS (Virtual Switching System)

Hi,
Is this SM supported in VSS chassis? I couldn't find information about it. I found only about WiSM-1.
Thanks.

Sup2T 15.0SY VSS config guide add WiSM2 support.
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/15.0SY/configuration/guide/virtual_switching_systems.html
Service Module Support
•Application Control Engine (ACE):
–ACE20-MOD-K9
–ACE30-MOD-K9
•Firewall Services Module (FWSM): WS-SVC-FWM-1-K9
•Network Analysis Module (NAM):
–WS-SVC-NAM-1
–WS-SVC-NAM-2
•Wireless Services Module (WiSM):
–WS-SVC-WISM-1-K9
–WS-SVC-WISM2

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking and Hyper-V.

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking!
http://www.youtube.com/watch?v=8mOuoIWzmdE
Hi thanks for reading. Now I may well have my terminology incorrect here so I will try to explain as best I can and apologies from the start.
It’s a bit of both Hyper-v and Server 2012R2.
I am setting up a lab with Server 2012 R2. I have several physical network cards that I have teamed called “HostSwitchTeam” from those I have made several Virtual Network Adaptors such as below
examples.
New-VMSwitch "MgmtSwitch" -MinimumBandwidthMode weight -NetAdaptername "HostSwitchTeam" -AllowManagement $false
Add-VMNetworkAdapter -ManagementOS -Name "Vswitch" -SwitchName "MgmtSwitch"
Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "MgmtSwitch"
When I install Hyper-V and it comes to adding a virtual switch during installation it only shows the individual physical network cards and the
HostSwitchTeam for selection. When installed it shows the Microsoft Network Multiplexor Driver as the only option.
Is this correct or how does one use the Vswitch made above and incorporate into the Hyper-V so a weight can be put against it.
Still trying to get my head around Vswitches,VMNetworkadapters etc so somewhat confused as to the way forward at this time so I may have missed the plot altogether!
Any help would be much appreciated.
Paul
Paul Edwards

Hi P.J.E,
>>I have teams so a bit confused as to the adapter bindings and if the teams need to be added or just the vEthernet Nics?.
Nic 1,2
HostVMSwitchTeam
Nic 3,4,5
HostMgmtSwitchTeam
>>The adapter Binding settings are:
HostMgmtSwitchTeam
V-Curric
Nic 3
Nic 4
Nic 5
V-Livemigration
HostVMSwitch
Nic 1
Nic 2
V-iSCSI
V-HeartBeat
Based on my understanding of the description , "HostMgmtSwitchTeam and
HostVMSwitch " are teamed NIC .
You can think of them as two physical NICs (do not use NIC 1,2,3,4,5 any more , there are just two NICs "HostMgmtSwitchTeam and
HostVMSwitch").
V-Curric,
V-Livemigration , V-iSCSI ,
V-HeartBeat are just VNICs of host (you can change their name then check if the virtual switch name will be changed )
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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!

Differences between VMware virtual switches and HyperV virtual switches

Hello,
I've deployed an OpenVpn infrastructure (configured in bridging mode) within a VMmare ESX4 environment.
The scenario is this:
A remote client connects to the OpenVpn server (VM1), VM1 also owns an interface where traffic passes in tagged mode complaint to vlan 8021q, VM2 owns a interface on the vlan10. VM1 can ping VM2 without any problem (supposing vlan 10 traffic), but the remote
client cannot ping VM2.
The scenario works perfectly in a physical environment (without any virtual machine).
The scenario is like this:
Analizing traffic with Wireshark on the VM2 I've noticed that an ARP request leaves from the remote client MAC to the destination host interface of VM2 (broadcast ARP request).
The host VM2 sends an ARP reply directly to the MAC address of the remote client.
This last packet doesn't pass the vSwitch, so it isn't received by the remote client and the ping fails.
This occurs because the VMware ESX vSwitch only knows all the MACs of virtual machines within the ESX environment, it doesn't learn MAC addresses like a physical real switch and it discards packets sent to unknown unicast MAC addresses (broadcast traffic instead
is passed). Within the VMware infrastructure this is solvable only by using of the Promiscuos mode feature of the virtual switch port.
I would like to ask if HyperV virtual switches work like VMware ESX virtual switches. So in Hyper-V virtual switches do learn mac addresses actually like a physical switch?

This last packet doesn't pass the vSwitch, so it isn't received by the remote client and the ping fails. This occurs because the VMware ESX vSwitch only knows all the MACs of virtual machines within the ESX environment, it doesn't learn MAC addresses
like a physical real switch and it discards packets sent to unknown unicast MAC addresses (broadcast traffic instead is passed). Within the VMware infrastructure this is solvable only by using of the Promiscuos mode feature of the virtual switch port.
Thank you; I did the same in Wireshark and noticed the ARP reply was not being received by my VMware guest Hyper-V host, so I did an Internet search and found this document at the top of the list. For other people that came here because their VMware guest
Hyper-V lab server's SCVMM 2012 SP1 logical switch virtual network adapter combination could not ping other VMware guests; In addition to "Accept" for your VMware vSwitch (described above), you will need to change your VM Network VLAN ID to "All".

6500 Virtual Switching System (VSS) design in MPLS PE PoP

...

Hello,
The VSS is not designed to function as a PE , its best fit in a DataCenter Environment where I have Multiple Links from Core/Access to the Distribution layer.
Although VSS provides Higher backblane Throughput, Ease and Single Administartion Managment, and Redundancy SSO between SUP engines at the Control Plane, These features wont help at the MPLS edge, why? because Both Chasis have identical configuration, So I cant have two links from the CE or from the P router to the same VSS Chasis, So I have No redundancy here.
what if a VSL link fails between the Two Chasis, Each chasis will revert to be as a standlone chasis with Identical Configuration, So I dont have redundancy here.
The VSS would be an ideal option as a PE router if the CE and P routers can form a direct Layer-3 Eitherchannel to each of the VSS chasis in order to benefit from a redundancy, in this case we can say we have (Intra Chasis Redundancy).
Since this Type of Scenario is not an option, then its normaly Service Providers prefer (Inter Chasis Redundancy) by having Two Different PE routers with two different Configuration to have resilency.
Other than that, it could quitely fit.
Regards,
Mohamed

Proper sizing of VSS virtual switch link

I am considering using VSS in my collapsed core/distribution on a pair of 6509/Sup2T switches with 6904-40G-2T modules. My closets are 4506/Sup7E, and I have one high-density, mission critical IDF with two fully populated 4510R+E/Sup7E switches. The interlinks will be either 2x or 4x10GE depending on customer decisions to be made. I am trying to find information that would suggest best practice for sizing the VSL. From what I can find, it would appear that not a significant amount of traffic goes across this link if everything in the environment is equally connected to both members of the VSS pairs. So, 2x10GE would be just as good as 4x, or even 2x40GE. However, I haven't found anything definitive yet. Is there a rule of thumb for sizing this link?
Thanks for any guidance.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
The VSL can be the Achilles Heel of a VSS setup.
As you note, if everything is configured optimally, very little traffic should cross this link.
However, suppose a line card fails. As the sup2t supports 80Gbps slot, in theory, that 80Gbps might need to transit the VSL. (NB: Hopefully, VSL also wasn't on the failed card.)
So, to size your VSL, consider bandwidth needs if a line card fails.
Also keep in mind, VSL (at least on 6500s) doesn't allow custom QoS, so you also lose some control on traffic management if VSL congests.

Configure Virtual Switch - hyper V - Windows Server 2012R2

On my laptop i have windows server 2012 R2 data center edition installed connected to Wifi. I was able to install and configure to VM's on it. However i am little lost on how to configure the virtual switch for these two VM's. Below are the details:
IP Address : 192.168.1.155
Subnet: 255.255.255.0
Default Gateway: (Blank)
DNS: 192.168.1.254
I do not have any ethernet port, i only have wifi. I did create a virtual switch linked to the NIC (Wifi), and same virtual switch is used by the two VM's. I want few things out of this:
i) I should be able to RDC into both the VM's from other computer when on the same network.
ii) I also want the host and two VM's to be accessible from outside the network.
I need to know what IP addresses should i assign to the virtual switch and each of the VM's. Thanks in advance.

Hi Sqlunlimitedgeek,
The two VMs will need IP addresses on the same range as the host.
Essentially, the switch is like a normal switch and anything connected to it should be able to access each other and the switch itself wont need an IP address.
Just make sure the vSwitch has been configured as an external switch and the "allow management operating system to share this network adapter" is checked. This will create a vEthernet that can be configured on the host with the relevant
IP address and save you exporting out your own via powershell.
The clients all need to be on the same subnet as does the hosts vEthernet.
If your using a team and want to carve that up then powershell is the best way. Especially if configuring a cluster and using a single NIC or Team to created a converged network. In this instance, this doesn't appear necessary as your just using a single WIFI
adapter.
To RDP, just makes sure that is enabled in both VM guests as per normal.
Kind Regards
Michael Coutanche
Blog:
Twitter: LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Create Hyper-V virtual switch with VLAN tagging

Hello All,
I would like to create virtual network switch on a physical NIC of the Hyper-V host in Powershell.
I use "New-VMSwitch" with "-AllowManagementOS $true" and the virtual switch will be ready. I would like to use "Enable virtual LAN identification for management operating system"
and tag a VLAN to the virtual switch. Can you please help me with an example how to do it in Powershell?

Start with this walk-through.
http://www.vnotebook.ca/2013/11/configuring-management-vlan-in-hyper-v.html
tags are bound to adapters. A switch must have minimum of one adapter.
¯\_(ツ)_/¯

2 IPS 4270 SETUP FOR PROMISCOUS MODE

hi guys,
I have two ips 4270 and i want to set up for promiscous mode, Please help me on how to setup this two device. It is first time for me two set up this devices. Can somebody give me configuration guides on how to start it?
thank you

Here is configuration guide for IPS version 7.0:
http://www.cisco.com/en/US/docs/security/ips/7.0/configuration/guide/idm/idmguide7.html
Hope that helps.

Cannot create Hyper-V external virtual switch Server 2012 R2

Hi,
I am unable to create an external virtual switch on server 2012 R2. I have two Broadcom NICS bridged on a DC fully functional now. I can install Hyper-V but the option is grayed out to create an external switch. I try binding it to the
network bridge, connecting my two NICS and it makes no difference.
Am I correct in assuming that I cannot use Hyper-V on this server if the two NICS are bridged?

try command "New-VMSwitch" from Powershell to get more information
Windows 2012 & Hyper-V: Converged Network and QoS
Hyper-V Virtual Switch 101: How to create and use Virtual Switches to connect Virtual Machines to Network
Have a nice day !!!

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!

IPS 4270 with 6509 VSS in Promiscous mode

Dear all,
I am trying to figure out how to configure 2x IPS 4270 in promiscous mode with Cisco 6509 VSS:
I have attached the LLD core datacenter design including the IPS physical placement in my network.
The following points are my concerns in this design:
Shall I connect each of the IPS 4270's into VSS Chassis A and B, or I keep each IPS connected to different Chassis? (considering the SPAN port configuration on VSS and if I could encounted Asymmetric routing issue or not).
Can I use Etherchannel in either case (keep in mind it's promiscous mode), that means the destination interface on the VSS will be an Etherchannel interface, but does the Cisco IPS 4270 support Etherchannel while in promiscous mode?
I really appreciate your input on this matter guys.
Cheers
Mohammed Khair

Hi,
1.You can Connect the each IPS into Chasis A and B That is Not aproblem .But While Configuring the RSPAN Monitor From A to B and B to A should monitor the both vlans ( i mean RSAPN A and B also vice versa in your config then it will give both out put even connectivity between IPs and chasisi one fails also)
2.IPS Supports the Etherchannel while in promiscous mode as well.

IPS 4270 and VSS (Virtual Switch System)

Similar Messages

Maybe you are looking for