Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion User Manual - Page 15

Browse online or download pdf User Manual for Switch Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion. Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion 17 pages. Distributed forwarding card 4 for ws-x68xx, ws-x69xx, and select ws-x67xx modules
Also for Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion: Installation Note (14 pages), Solution Manual (17 pages), Installation Note (46 pages), White Paper (19 pages), Description (1 pages), Product Bulletin (6 pages), Notice (4 pages), Datasheet (9 pages), Datasheet (18 pages), White Paper (18 pages), Configuration Manual (8 pages), Installation Note (28 pages), Troubleshooting Manual (11 pages), Installation Note (18 pages), Installation Note (24 pages), Manual (19 pages), Installation Note (36 pages)

Print Page
Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion User Manual
•
VSL cannot be configured as SPAN destination.
•
VSL cannot be configured as source of RSPAN, ERSPAN, or Tx only local SPAN.
•
VSL header is removed by SPAN destination port before packet is transmitted out, and hence cannot
be captured in the sniffer traces.
•
When the source and destination are both on the same chassis (active or standby), then SPAN traffic
does not flow over the VSL link.
In order to capture traffic from both chassis, there are two options which avoids the flow of SPAN
traffic on the VSL:
♦
For each source interface on one chassis, the destination interface must be on the same
chassis.
For example, PO20 has gi1/1/1 and gi2/1/1: you need to have one destination for each
chassis.
However, this means that you use both the local SPAN sessions. Therefore, you cannot use
any other local SPAN session.
♦
You can use the destination interface for SPAN as a MEC (recommended).
The destination port can be a MEC.

Miscellaneous

Recommendations
•
Use a minimum of one Supervisor uplink for VSL in order to have faster VSL bring up.
•
Configure the switch accept mode virtual command after VSS conversion. Without this command,
the conversion is not complete.
•
Save the backup of the configuration file in both active and hot−standy bootdisk:. This is of much
help in supervisor replacement scenarios.
•
Use unique VSS domain−ID within the same network. Duplicate VSS domain−ID can cause
EtherChannel inconsistency.
Here is an example to change the VSS domain−ID.
1.
Use the switch virtual domain domain−id command in order to initiate the domain ID
change.
Note: Domain ID 50 config takes effect only after the switch convert mode virtual exec
command is issued.
2.
Use the switch convert mode virtual command in order to complete the task.
Note: Virtual Domain ID changes only after you save the config and reload the switch.
Monitor session 1 source interface gi1/1/1
Monitor session 1 destination interface gi1/1/2
Monitor session 2 source interface gi2/1/1
Monitor session 2 destination interface gi2/1/2
switch(config)#switch virtual domain 50
switch#switch convert mode virtual