Table Of Contents
Documentation Updates for the Catalyst 3560E-12D Switches
Updates to the "Configuring SPAN and RSPAN" Chapter in the Software Configuration Guide
Updates to the "SPAN and RSPAN Concepts and Terminology" Section
Updates to the "Source Ports" Section
Addition of the "Destination-Port Group" Section
Updates to the "Configuring Local SPAN" Section
Creating a Local SPAN Session and Configuring Incoming Traffic
Updates to the "Configuring RSPAN" Section
Creating an RSPAN Source Session
Creating an RSPAN Destination Session
Creating an RSPAN Destination Session and Configuring Incoming Traffic
Addition of the "Fan Failures" Section to the Software Configuration Guide
Updates to the monitor session command in the Command Reference
Updates to the show monitor command in the Command Reference
Addition of the system env fan-fail-action shut Command in the Command Reference
Obtaining Documentation, Obtaining Support, and Security Guidelines
Documentation Updates for the Catalyst 3560E-12D Switches
November 27, 2007
This document describes how to configure the Catalyst 3560E -12D switch, referred to as the aggregator switch. The Catalyst 3750-E switches and Catalyst 3560-E switches other than the Catalyst 3560E-12D switch are referred to as desktop switches.
Use this document in conjunction with the Catalyst 3750-E and 3560-E software documentation (see the "Related Publications" section).
This document has these sections:
•
Updates to the "Configuring SPAN and RSPAN" Chapter in the Software Configuration Guide
•
•
•
•
•
Updates to the "Configuring SPAN and RSPAN" Chapter in the Software Configuration Guide
In this section, the Catalyst 3560E -12D switch is referred to as the aggregator switch, and the Catalyst 3750-E switches and Catalyst 3560-E switches other than the Catalyst 3560E-12D switch are referred to as desktop switches.
This information is modified or added:
•
•
•
•
•
Updates to the "SPAN and RSPAN Concepts and Terminology" Section
In the "SPAN Sessions" section:
Traffic monitoring in a SPAN session has these restrictions:
•
•
–
–
•
•
•
•
•
•
–
–
–
Updates to the "Source Ports" Section
A source port (also called a monitored port) is a switched or routed port that you monitor for network traffic analysis. In a local SPAN session or RSPAN source session, you can monitor source ports or VLANs for traffic in one or both directions. The switch supports any number of source ports (up to the maximum number of available ports on the switch) and any number of source VLANs (up to the maximum number of VLANs supported). However, the switch supports a maximum of two sessions (local or RSPAN) with source ports or VLANs, and the Catalyst 3560E-12D switch supports only one session (local or RSPAN) with source ports or VLANs. You cannot mix ports and VLANs in a single session.
A source port has these characteristics:
•
•
•
•
•
•
•
•
Addition of the "Destination-Port Group" Section
The "Destination-Port Group" section is added after the "Destination Port" section:
Note
The Catalyst 3560E-12D switch can only send SPAN and RSPAN traffic through destination ports belonging to the same destination-port group. When configuring an RSPAN destination session, you must specify the destination-port group (a, b, or c). For more information about the destination-port groups, see the "SPAN Configuration Guidelines" section.
In a local SPAN session with only one destination port, you do not need to specify the destination-port group. If you add a second destination port to the session, the port must be in the same destination-port group as the existing destination port.
Updates to the "Configuring Local SPAN" Section
These sections contain this configuration information:
•
•
•
•
SPAN Configuration Guidelines
Follow these guidelines when configuring SPAN:
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
Creating a Local SPAN Session
Beginning in privileged EXEC mode, follow these steps to create a SPAN session and to specify the source (monitored) ports or VLANs and the destination (monitoring) ports:
To delete a SPAN session, use the no monitor session session_number global configuration command. To remove a source or destination port or VLAN from the SPAN session, use the no monitor session session_number source {interface interface-id | vlan vlan-id} global configuration command or the no monitor session session_number destination interface interface-id global configuration command. For destination interfaces, the encapsulation options are ignored with the no form of the command.
This example shows how to set up SPAN session 1 for monitoring source port traffic to a destination port. First, any existing SPAN configuration for session 1 is deleted, and then bidirectional traffic is mirrored from source Gigabit Ethernet port 1 to destination Gigabit Ethernet port 2, retaining the encapsulation method.
Switch(config)# no monitor session 1Switch(config)# monitor session 1 source interface gigabitethernet1/0/1Switch(config)# monitor session 1 destination interface gigabitethernet1/0/2 encapsulation replicateSwitch(config)# endThis example shows how to remove port 1 as a SPAN source for SPAN session 1:
Switch(config)# no monitor session 1 source interface gigabitethernet1/0/1Switch(config)# endThis example shows how to disable received traffic monitoring on port 1, which was configured for bidirectional monitoring:
Switch(config)# no monitor session 1 source interface gigabitethernet1/0/1 rxThe monitoring of traffic received on port 1 is disabled, but traffic sent from this port continues to be monitored.
This example shows how to remove any existing configuration on SPAN session 2, configure SPAN session 2 to monitor received traffic on all ports belonging to VLANs 1 through 3, and send it to destination Gigabit Ethernet port 2. The configuration is then modified to also monitor all traffic on all ports belonging to VLAN 10.
Switch(config)# no monitor session 2Switch(config)# monitor session 2 source vlan 1 - 3 rxSwitch(config)# monitor session 2 destination interface gigabitethernet1/0/2Switch(config)# monitor session 2 source vlan 10Switch(config)# endCreating a Local SPAN Session and Configuring Incoming Traffic
Beginning in privileged EXEC mode, follow these steps to create a SPAN session, to specify the source ports or VLANs and the destination ports, and to enable incoming traffic on the destination port for a network security device (such as a Cisco IDS Sensor Appliance).
For details about the keywords not related to incoming traffic, see the "Creating a Local SPAN Session" section on page 12.
To delete a SPAN session, use the no monitor session session_number global configuration command. To remove a source or destination port or VLAN from the SPAN session, use the no monitor session session_number source {interface interface-id | vlan vlan-id} global configuration command or the no monitor session session_number destination interface interface-id global configuration command. For destination interfaces, the encapsulation and ingress options are ignored with the no form of the command.
This example shows how to remove any existing configuration on SPAN session 2, configure SPAN session 2 to monitor received traffic on Gigabit Ethernet source port 1, and send it to destination Gigabit Ethernet port 2 with the same egress encapsulation type as the source port, and to enable ingress forwarding with IEEE 802.1Q encapsulation and VLAN 6 as the default ingress VLAN.
Switch(config)# no monitor session 2Switch(config)# monitor session 2 source gigabitethernet1/0/1 rxSwitch(config)# monitor session 2 destination interface gigabitethernet1/0/2 encapsulation replicate ingress dot1q vlan 6Switch(config)# endSpecifying VLANs to Filter
Beginning in privileged EXEC mode, follow these steps to limit SPAN source traffic to specific VLANs only on trunk ports and voice VLAN ports:
To monitor all VLANs on the trunk port, use the no monitor session session_number filter global configuration command.
This example shows how to remove any existing configuration on SPAN session 2, configure SPAN session 2 to monitor traffic received on Gigabit Ethernet trunk port 2, and send traffic for only VLANs 1 through 5 and VLAN 9 to destination Gigabit Ethernet port 1.
Switch(config)# no monitor session 2Switch(config)# monitor session 2 source interface gigabitethernet1/0/2 rxSwitch(config)# monitor session 2 filter vlan 1 - 5 , 9Switch(config)# monitor session 2 destination interface gigabitethernet1/0/1Switch(config)# endUpdates to the "Configuring RSPAN" Section
This document has updates for these sections in the "Configuring RSPAN" section:
•
•
•
•
Creating an RSPAN Source Session
Beginning in privileged EXEC mode, follow these steps to start an RSPAN source session and to specify the monitored source and the destination RSPAN VLAN:
To delete a SPAN session, use the no monitor session session_number global configuration command.
To remove a source port or VLAN from the SPAN session, use the no monitor session session_number source {interface interface-id | vlan vlan-id} global configuration command. To remove the RSPAN VLAN from the session, use the no monitor session session_number destination remote vlan vlan-id.
This example shows how to remove any existing RSPAN configuration for session 1, configure RSPAN session 1 to monitor multiple source interfaces, and configure the destination as RSPAN VLAN 901.
Switch(config)# no monitor session 1Switch(config)# monitor session 1 source interface gigabitethernet1/0/1 txSwitch(config)# monitor session 1 source interface gigabitethernet1/0/2 rxSwitch(config)# monitor session 1 source interface port-channel 2Switch(config)# monitor session 1 destination remote vlan 901Switch(config)# endOn the Catalyst 3560E-12D switch, this example shows how to remove any existing RSPAN configuration for session 1, configure RSPAN session 1 to monitor multiple source interfaces, and configure the destination as RSPAN VLAN 901.
Switch(config)# no monitor session 1Switch(config)# monitor session 1 source interface gigabitethernet0/1 txSwitch(config)# monitor session 1 source interface gigabitethernet0/2 rxSwitch(config)# monitor session 1 source interface port-channel 2Switch(config)# monitor session 1 destination remote vlan 901 destination-port group bSwitch(config)# endSpecifying VLANs to Filter
Beginning in privileged EXEC mode, follow these steps to configure the RSPAN source session to limit RSPAN source traffic to specific VLANs:
To monitor all VLANs on the trunk port, use the no monitor session session_number filter vlan global configuration command.
This example shows how to remove any existing configuration on RSPAN session 2, configure RSPAN session 2 to monitor traffic received on trunk port 2, and send traffic for only VLANs 1 through 5 and 9 to destination RSPAN VLAN 902.
Switch(config)# no monitor session 2Switch(config)# monitor session 2 source interface gigabitethernet1/0/2 rxSwitch(config)# monitor session 2 filter vlan 1 - 5 , 9Switch(config)# monitor session 2 destination remote vlan 902Switch(config)# endOn the Catalyst 3560E-12D switch, this example shows how to remove any existing configuration on RSPAN session 2, configure RSPAN session 2 to monitor traffic received on trunk port 2, and send traffic for only VLANs 1 through 5 and 9 to destination RSPAN VLAN 902.
Switch(config)# no monitor session 1Switch(config)# monitor session 1 source interface gigabitethernet0/2 rxSwitch(config)# monitor session 1 filter vlan 1 - 5 , 9Switch(config)# monitor session 1 destination remote vlan 902 destination-port group aSwitch(config)# endCreating an RSPAN Destination Session
You configure the RSPAN destination session on a different switch or switch stack; that is, not the switch or switch stack on which the source session was configured.
Beginning in privileged EXEC mode, follow these steps to define the RSPAN VLAN on that switch, to create an RSPAN destination session, and to specify the source RSPAN VLAN and the destination port:
To delete a SPAN session, use the no monitor session session_number global configuration command. To remove a destination port from the SPAN session, use the no monitor session session_number destination interface interface-id global configuration command. To remove the RSPAN VLAN from the session, use the no monitor session session_number source remote vlan vlan-id.
This example shows how to configure VLAN 901 as the source remote VLAN and port 1 as the destination interface:
Switch(config)# monitor session 3 source remote vlan 901Switch(config)# monitor session 3 destination interface gigabitethernet2/0/1Switch(config)# endCreating an RSPAN Destination Session and Configuring Incoming Traffic
Beginning in privileged EXEC mode, follow these steps to create an RSPAN destination session, to specify the source RSPAN VLAN and the destination port, and to enable incoming traffic on the destination port for a network security device (such as a Cisco IDS Sensor Appliance).
For details about the keywords not related to incoming traffic, see the "Creating an RSPAN Destination Session" section on page 20. This procedure assumes that the RSPAN VLAN has already been configured.
To delete an RSPAN session, use the no monitor session session_number global configuration command. To remove a destination port from the RSPAN session, use the no monitor session session_number destination interface interface-id global configuration command. The ingress options are ignored with the no form of the command.
This example shows how to configure VLAN 901 as the source remote VLAN in RSPAN session 2, to configure Gigabit Ethernet source port 2 as the destination interface, and to enable forwarding of incoming traffic on the interface with VLAN 6 as the default receiving VLAN.
Switch(config)# monitor session 2 source remote vlan 901Switch(config)# monitor session 2 destination interface gigabitethernet1/0/2 ingress vlan 6Switch(config)# endAddition of the "Fan Failures" Section to the Software Configuration Guide
This information is added to the "Troubleshooting" chapter of the Catalyst 3750-E and 3560-E Switch Software Configuration Guide.
Fan Failures
The fan failures feature is supported only on the Catalyst 3560E-12D switch. You can use this feature to avoid overheating the switch.
By default, the feature is disabled. When more than one of the fans in a field-replaceable unit (FRU) or in a power supply fails, the switch does not shut down, and this error message appears:
Multiple fan(FRU/PS) failure detected. System may get overheated. Change fan quickly.The switch might overheat and shut down.
To enable the fan failures feature, enter the system env fan-fail-action shut privileged EXEC command. If more than one fan in the switch fails, the switch automatically shuts down, and this error message appears:
Faulty (FRU/PS) fans detected, shutting down system!After the first fan shuts down, if the switch detects a second fan failure, the switch waits for 20 seconds before it shuts down.
To restart the switch, it must be power cycled.
Updates to the monitor session command in the Command Reference
monitor session
Use the monitor session global configuration command on the switch stack or on a standalone switch to start a new Switched Port Analyzer (SPAN) session or Remote SPAN (RSPAN) source or destination session, to enable ingress traffic on the destination port for a network security device (such as a Cisco IDS Sensor Appliance), to add or delete interfaces or VLANs to or from an existing SPAN or RSPAN session, and to limit (filter) SPAN source traffic to specific VLANs. Use the no form of this command to remove the SPAN or RSPAN session or to remove source or destination interfaces or filters from the SPAN or RSPAN session. For destination interfaces, the encapsulation options are ignored with the no form of the command.
For all Catalyst 3750-E and 3560-E switches:
monitor session session_number filter vlan vlan-id [, | -]
monitor session session_number source {interface interface-id [, | -] [both | rx | tx]} | {vlan vlan-id [, | -] [both | rx | tx]}| {remote vlan vlan-id}
no monitor session {session_number | all | local | remote}
no monitor session session_number filter vlan vlan-id [, | -]
no monitor session session_number source {interface interface-id [, | -] [both | rx | tx]} | {vlan vlan-id [, | -] [both | rx | tx]}| {remote vlan vlan-id}
For a switch other than the Catalyst 3560E-12D switch:
monitor session session_number destination {interface interface-id [, | -] [encapsulation replicate] [ingress {dot1q vlan vlan-id | isl | untagged vlan vlan-id | vlan vlan-id}]} | {remote vlan vlan-id}
no monitor session session_number destination {interface interface-id [, | -] [encapsulation replicate] [ingress {dot1q vlan vlan-id | isl | untagged vlan vlan-id | vlan vlan-id}]} | {remote vlan vlan-id}
For the Catalyst 3560E-12D switch:
monitor session session_number destination {interface interface-id [, | -] [encapsulation replicate] [ingress {dot1q vlan vlan-id | isl | untagged vlan vlan-id | vlan vlan-id}]} | {remote vlan vlan-id} destination-port group {a | b | c}
no monitor session session_number destination {interface interface-id [, | -] [encapsulation replicate] [ingress {dot1q vlan vlan-id | isl | untagged vlan vlan-id | vlan vlan-id}]} | {remote vlan vlan-id} destination-port group {a | b | c}
Syntax Description
Defaults
No monitor sessions are configured.
On a source interface, the default is to monitor both received and sent traffic.
On a trunk interface used as a source port, all VLANs are monitored.
If encapsulation replicate is not specified on a local SPAN destination port, packets are sent in native form with no encapsulation tag.
Ingress forwarding is disabled on destination ports.
Command Modes
Global configuration
Command History
12.2(35)SE2
This command was introduced.
12.2(40)EX
The destination-port group {a | b | c} keywords were added only for the Catalyst 3560E-12D switch.
Usage Guidelines
Traffic that enters or leaves source ports or source VLANs can be monitored by using SPAN or RSPAN. Traffic routed to source ports or source VLANs cannot be monitored.
You can set a combined maximum of two local SPAN sessions and RSPAN source sessions. You can have a total of 66 SPAN and RSPAN sessions on a switch or switch stack.
You can have a maximum of 64 destination ports on a switch or a switch stack.
Each session can include multiple ingress or egress source ports or VLANs, but you cannot combine source ports and source VLANs in a single session. Each session can include multiple destination ports.
When you use VLAN-based SPAN (VSPAN) to analyze network traffic in a VLAN or set of VLANs, all active ports in the source VLANs become source ports for the SPAN or RSPAN session. Trunk ports are included as source ports for VSPAN, and only packets with the monitored VLAN ID are sent to the destination port.
You can monitor traffic on a single port or VLAN or on a series or range of ports or VLANs. You select a series or range of interfaces or VLANs by using the [, | -] options.
If you specify a series of VLANs or interfaces, you must enter a space before and after the comma. If you specify a range of VLANs or interfaces, you must enter a space before and after the hyphen (-).
EtherChannel ports cannot be configured as SPAN or RSPAN destination ports. A physical port that is a member of an EtherChannel group can be used as a destination port, but it cannot participate in the EtherChannel group while it is as a SPAN destination.
A private-VLAN port cannot be configured as a SPAN destination port.
You can monitor individual ports while they participate in an EtherChannel, or you can monitor the entire EtherChannel bundle by specifying the port-channel number as the RSPAN source interface.
A port used as a destination port cannot be a SPAN or RSPAN source, nor can a port be a destination port for more than one session at a time.
You can enable IEEE 802.1x authentication on a port that is a SPAN or RSPAN destination port; however, IEEE 802.1x authentication is disabled until the port is removed as a SPAN destination. If IEEE 802.1x authentication is not available on the port, the switch returns an error message. You can enable IEEE 802.1x authentication on a SPAN or RSPAN source port.
VLAN filtering refers to analyzing network traffic on a selected set of VLANs on trunk source ports. By default, all VLANs are monitored on trunk source ports. You can use the monitor session session_number filter vlan vlan-id command to limit SPAN traffic on trunk source ports to only the specified VLANs.
VLAN monitoring and VLAN filtering are mutually exclusive. If a VLAN is a source, VLAN filtering cannot be enabled. If VLAN filtering is configured, a VLAN cannot become a source.
If ingress traffic forwarding is enabled for a network security device, the destination port forwards traffic at Layer 2.
Destination ports can be configured to act in these ways:
•
•
•
•
•
•
Examples
This example shows how to create a local SPAN session 1 to monitor both sent and received traffic on source port 1 on stack member 1 to destination port 2 on stack member 2:
Switch(config)# monitor session 1 source interface gigabitethernet1/0/1 bothSwitch(config)# monitor session 1 destination interface gigabitethernet2/0/2This example shows how to delete a destination port from an existing local SPAN session:
Switch(config)# no monitor session 2 destination gigabitethernet1/0/2This example shows how to limit SPAN traffic in an existing session only to specific VLANs:
Switch(config)# monitor session 1 filter vlan 100 - 110This example shows how to configure RSPAN source session 1 to monitor multiple source interfaces and to configure the destination RSPAN VLAN 900.
Switch(config)# monitor session 1 source interface gigabitethernet1/0/1Switch(config)# monitor session 1 source interface port-channel 2 txSwitch(config)# monitor session 1 destination remote vlan 900Switch(config)# endOn the Catalyst 3560E-12D switch, this example shows how to configure RSPAN source session 1 to monitor multiple source interfaces and to configure the destination RSPAN VLAN 900.
Switch(config)# monitor session 1 source interface gigabitethernet1/0/1Switch(config)# monitor session 1 source interface port-channel 2 txSwitch(config)# monitor session 1 destination remote vlan 900 destination-group bSwitch(config)# endThis example shows how to configure an RSPAN destination session 10 in the switch receiving the monitored traffic.
Switch(config)# monitor session 10 source remote vlan 900Switch(config)# monitor session 10 destination interface gigabitethernet1/0/2This example shows how to configure the destination port for ingress traffic on VLAN 5 by using a security device that supports IEEE 802.1Q encapsulation. Egress traffic replicates the source; ingress traffic uses IEEE 802.1Q encapsulation.
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/2 encapsulation dot1q ingress dot1q vlan 5This example shows how to configure the destination port for ingress traffic on VLAN 5 by using a security device that does not support encapsulation. Egress traffic and ingress traffic is untagged.
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/2 ingress untagged vlan 5You can verify your settings by entering the show monitor privileged EXEC command. You can display SPAN and RSPAN configuration on the switch by entering the show running-config privileged EXEC command. SPAN information appears near the end of the output.
Related Commands
remote-span
Configures an RSPAN VLAN in vlan configuration mode.
show monitor
Displays SPAN and RSPAN session information.
show running-config
Displays the operating configuration. For syntax information, use this link to the Cisco IOS Release 12.2 Command Reference listing page: http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/prod_command_reference_list.html
Select the Cisco IOS Commands Master List, Release 12.2 to navigate to the command.
Updates to the show monitor command in the Command Reference
show monitor
Use the show monitor user EXEC command to display information about all Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) sessions on the switch. Use the command with keywords to show a specific session, all sessions, all local sessions, or all remote sessions.
show monitor [session {session_number | all | local | range list | remote} [detail]] [ | {begin | exclude | include} expression]
Syntax Description
Command Modes
User EXEC
Command History
Usage Guidelines
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output do not appear, but the lines that contain Output appear.
The output is the same for the show monitor command and the show monitor session all command.
Examples
This is an example of output for the show monitor user EXEC command on a switch other than the Catalyst 3560E-12D switch:
Switch# show monitorSession 1---------Type : Local SessionSource Ports :RX Only : Gi4/0/1Both : Gi4/0/2-3,Gi4/0/5-6Destination Ports : Gi4/0/20Encapsulation : ReplicateIngress : DisabledSession 2---------Type : Remote Source SessionSource VLANs :TX Only : 10Both : 1-9Dest RSPAN VLAN : 105This is an example of output for the show monitor user EXEC command for local SPAN source session 1:
Switch# show monitor session 1Session 1---------Type : Local SessionSource Ports :RX Only : Gi4/0/1Both : Gi4/0/2-3,Gi4/0/5-6Destination Ports : Gi4/0/20Encapsulation : ReplicateIngress : DisabledThis is an example of output for the show monitor session all user EXEC command when ingress traffic forwarding is enabled:
Switch# show monitor session allSession 1---------Type : Local SessionSource Ports :Both : Gi4/0/2Destination Ports : Gi4/0/3Encapsulation : NativeIngress : Enabled, default VLAN = 5Ingress encap : DOT1QSession 2---------Type : Local SessionSource Ports :Both : Gi4/0/8Destination Ports : Gi4/012Encapsulation : ReplicateIngress : Enabled, default VLAN = 4Ingress encap : UntaggedThis is an example of output for the show monitor user EXEC command on the Catalyst 3560E-12D switch. The destination-group information appears only when an RSPAN source session is configured on the switch.
Switch# show monitorSession 1---------Type : Remote Source SessionSource Ports :Both : Te0/7,Te0/10Dest RSPAN VLAN : 900Dest-port group : A = Te0/1-4, Gi0/1-8Related Commands
Addition of the system env fan-fail-action shut Command in the Command Reference
The system env fan-fail-action shut privileged EXEC command is added to the Catalyst 3750-E and 3560-E Switch Command Reference:
system env fan-fail shutdown
Use the system env fan-fail-action shut global configuration command to configure the Catalyst 3560-E-12 switch to shut down when more than one fan fails. Use the no form of this command to return to the default setting.
system env fan-fail-action shut
no system env fan-fail-action shut
This command is supported only on the Catalyst 3560E-12D switch.
Syntax Description
This command has no arguments or keywords.
Defaults
By default, the fan failures feature is disabled.The Catalyst 3560E-12D switch does not shut down when more than one fan in a field-replaceable unit (FRU) or a power supply fails.
Command Modes
Global configuration
Command History
Usage Guidelines
To enable the fan failures feature, enter the system env fan-fail-action shut global configuration command. If more than one of the switch fans fail, the Catalyst 3560E-12D switch automatically shuts down.
To disable this feature and return to the default setting, enter the no system env fan-fail-action shut command.
For more information about the feature, see the "Addition of the "Fan Failures" Section to the Software Configuration Guide" section.
Examples
This example shows how to enable the fan failures feature:
Switch# configure terminalSwitch(config)# system env fan-fail-action shutSwitch(config)# endRelated Publications
You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the URL referenced in the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section.
For more information about the switch, see these documents on Cisco.com:
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0709R)
Guest
