Table Of Contents
4-Port Ethernet Switch Configuration Notes for the Cisco 1700 Series Routers
Switching Frames Between Segments
Layer 2 Interface Configuration Guidelines and Restrictions
Switch Virtual Interfaces (SVIs)
VLAN Trunking Protocol (Transparent Mode Only)
Default Spanning Tree Configuration
Configuring Layer 2 Interfaces
Configuring a Range of Interfaces
Verifying Configuration of a Range of Interfaces
Configuring Layer 2 Optional Interface Features
Deleting a VLAN Instance from the Database
Configuring VTP (Transparent Mode)
Configuring Spanning Tree Port Priority
Configuring Spanning Tree Port Cost
Configuring the Bridge Priority of a VLAN
Configuring the Forward-Delay Time for a VLAN
Configuring the Maximum Aging Time for a VLAN
Configuring Cisco Discovery Protocol (CDP)
Configuring Cisco Discovery Protocol (CDP)
Monitoring and Maintaining CDP
Verifying the Switch Port Configuration
Assigning IP Information to the Switch
Specifying a Domain Name and Configuring the DNS
Optional Interface Feature Examples
Disabling VTP (VTP Transparent Mode) Example
Obtaining Technical Assistance
Obtaining Additional Publications and Information
4-Port Ethernet Switch Configuration Notes for the Cisco 1700 Series Routers
This document describes the configuration of the 4-port 10/100BASE-TX Ethernet switch on Cisco 1711 and Cisco 1712 Security Access routers running Cisco IOS Release 12.2(15)ZL and higher, and the Cisco WIC-4ESW interface card supported on Cisco 1721, Cisco 1751, Cisco 1751-V, and Cisco 1760 routers, running Cisco IOS Release 12.3(2)XC and higher.
The 4-port 10/100BASE-TX Ethernet switch is a Layer 2 Ethernet switch with Layer 3 routing capability, and supports a maximum of 16 VLANs. (Layer 3 routing is forwarded to the host, and is not actually performed at the switch.)
There are no new or modified commands for use with the switch. All commands used with the switch are documented in the Cisco IOS command reference publications.
The first port on the Cisco WIC-4ESW is always identified as "1." For the Cisco 1721 router, the ports are referred to as FastEthernet1 to FastEthernet4, no matter in what slot the card is installed.
On the Cisco 1751 router and the Cisco 1760 router, the Fast Ethernet interfaces on Cisco WIC-4ESW are addressed as F<slot>/1 through F<slot>/4, depending in what slot the card is installed. (In this document, the ports will be referred as F1 through F4.)
Note
The Cisco 1700 series routers support one WIC-4ESW only. If you add more than one WIC-4ESW, then you might see one of the error messages as described in Table 1.
The following topics provide information about the 4-port Ethernet switch, along with configuration guidelines and examples:
•
•
Benefits
The following benefits are provided by the switch:
•
•
–
–
–
–
•
•
–
–
Supported Standards
The following standards are supported:
•
•
•
Platform Limitations
The following features are not supported on the switch:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Supported Features
The switch supports the features described below:
•
•
Layer 2 Ethernet Interfaces
The Ethernet switch supports simultaneous, parallel connections between Layer 2 Ethernet segments. Switched connections between Ethernet segments last only for the duration of the packet. New connections can be made between different segments for the next packet.
The Ethernet switch solves congestion problems caused by high-bandwidth devices and a large number of users by assigning each device (for example, a server) to its own 10-, 100-, or 1000-Mbps segment. Because each Ethernet interface on the switch represents a separate Ethernet segment, servers in a properly configured switched environment achieve full access to the bandwidth.
Because collisions are a major bottleneck in Ethernet networks, an effective solution is full-duplex communication. Normally, Ethernet operates in half-duplex mode, which means that stations can either receive or transmit. In full-duplex mode, two stations can transmit and receive at the same time. When packets can flow in both directions simultaneously, effective Ethernet bandwidth doubles to 20 Mbps for 10-Mbps interfaces and to 200 Mbps for Fast Ethernet interfaces.
Switching Frames Between Segments
Each Ethernet interface on an Ethernet switch can connect to a single workstation or server, or to a hub through which workstations or servers connect to the network.
On a typical Ethernet hub, all ports connect to a common backplane within the hub, and the bandwidth of the network is shared by all devices attached to the hub. If two stations establish a session that uses a significant level of bandwidth, the network performance of all other stations attached to the hub is degraded.
To reduce degradation, the switch treats each interface as an individual segment. When stations on different interfaces need to communicate, the switch forwards frames from one interface to the other at wire speed to ensure that each session receives full bandwidth.
To switch frames between interfaces efficiently, the switch maintains an address table. When a frame enters the switch, it associates the MAC address of the sending station with the interface on which it was received.
Building the Address Table
An Ethernet switch builds the address table by using the source address of the frames received. When the switch receives a frame for a destination address not listed in its address table, it floods the frame to all interfaces of the same VLAN except the interface that received the frame. When the destination station replies, the switch adds its relevant source address and interface ID to the address table. The switch then forwards subsequent frames to a single interface without flooding to all interfaces. The address table can store at least 1,024 address entries without flooding any entries. The switch uses an aging mechanism, with a fixed aging timer of 5 minutes; if an address remains inactive for 5 minutes, it is removed from the address table.
VLAN Trunks
A trunk is a point-to-point link between one or more Ethernet switch interfaces and another networking device such as a router or a switch. Trunks carry the traffic of multiple VLANs over a single link and allow you to extend VLANs across an entire network. The switch supports only one encapsulation on all Ethernet interfaces, 802.1Q-802.1Q, an industry-standard trunking encapsulation.
Layer 2 Interface Modes
Switchport mode access puts the interface into nontrunking mode. The interface will stay in access mode regardless of the connected port mode. Only access VLAN traffic will travel on the access port untagged (802.3).
When you connect a Cisco switch to a device other than a Cisco device through an 802.1Q trunk, the Cisco switch combines the Spanning Tree instance of the VLAN trunk with the Spanning Tree instance of the other 802.1Q switch. However, Spanning Tree information for each VLAN is maintained by Cisco switches separated by a cloud of 802.1Q switches that are not Cisco switches. The 802.1Q cloud separating the Cisco switches and that is not Cisco devised, is treated as a single trunk link between the switches.
Make sure that the native VLAN for an 802.1Q trunk is the same on both ends of the trunk link. If the VLAN on one end of the trunk is different from the VLAN on the other end, Spanning Tree loops might result. Inconsistencies detected by a Cisco switch mark the line as broken and block traffic for the specific VLAN.
Caution
Layer 2 Interface Configuration Guidelines and Restrictions
Follow these guidelines and restrictions when configuring Layer 2 interfaces:
In a network of Cisco switches connected through 802.1Q trunks, the switches maintain one instance of Spanning Tree for each VLAN allowed on the trunks. 802.1Q switches that are not Cisco switches, maintain only one instance of Spanning Tree for all VLANs allowed on the trunks.
Switch Virtual Interfaces (SVIs)
A switch virtual interface (SVI) represents a VLAN of switch ports as one interface to the routing or bridging function in the system. Only one SVI can be associated with a VLAN, but it is necessary to configure an SVI for a VLAN only when you wish to route between VLANs, fallback-bridge nonroutable protocols between VLANs, or to provide IP host connectivity to the switch. By default, an SVI is created for the default VLAN (VLAN 1) to permit remote switch administration. Additional SVIs must be explicitly configured. In Layer 2 mode, SVIs provide IP host connectivity only to the system; in Layer 3 mode, you can configure routing across SVIs.
SVIs are created the first time that you enter the vlan interface configuration command for a VLAN interface. The VLAN corresponds to the VLAN tag associated with data frames on an Inter-Switch Link (ISL) or 802.1Q encapsulated trunk or the VLAN ID configured for an access port. Configure a VLAN interface for each VLAN for which you want to route traffic, and assign it an IP address.
SVIs support routing protocol and bridging configurations.
Note
VLAN Trunking Protocol (Transparent Mode Only)
VTP is a Layer 2 messaging protocol that maintains VLAN configuration consistency by managing the addition, deletion, and renaming of VLANs within a VTP domain. A VTP domain (also called a VLAN management domain) is made up of one or more switches that share the same VTP domain name and that are interconnected with trunks.
VTP minimizes misconfigurations and configuration inconsistencies that can result in a number of problems, such as duplicate VLAN names, incorrect VLAN-type specifications, and security violations. Before you create VLANs, you must decide whether to use VTP in your network. With VTP, you can make configuration changes centrally on one or more switches and have those changes automatically communicated to all the other switches in the network.
The following sections provide information about VTP.
VTP Domain
A VTP domain (or VLAN management domain) is made up of one or more interconnected switches that share the same VTP domain name. A switch can be configured to be in one and only one VTP domain. You make global VLAN configuration changes for the domain using either the command-line interface (CLI) or Simple Network Management Protocol (SNMP).
By default, the switch is in VTP server mode and is in an unnamed domain state until the switch receives an advertisement for a domain over a trunk link or until you configure a management domain. You cannot create or modify VLANs on a VTP server until the management domain name is specified or learned.
If the switch receives a VTP advertisement over a trunk link, it inherits the management domain name and the VTP configuration revision number. The switch ignores advertisements with a different management domain name or an earlier configuration revision number.
When you make a change to the VLAN configuration on a VTP server, the change is propagated to all switches in the VTP domain. VTP advertisements are transmitted out all trunk connections using IEEE 802.1Q encapsulation.
VTP maps VLANs dynamically across multiple LAN types with unique names and internal index associations. Mapping eliminates excessive device administration required from network administrators.
Supported VTP Mode
The switch supports VTP only in transparent mode. By configuring the switch as VTP transparent, you can create and modify VLANs, but the changes affect only the individual switch.
A VTP transparent switch does not advertise its VLAN configuration and does not synchronize its VLAN configuration based on received advertisements. However, in VTP version 2, transparent switches do forward VTP advertisements that they receive out their trunk interfaces.
VTP Advertisements
Each switch in the VTP domain sends periodic advertisements out each trunk interface to a reserved multicast address. VTP advertisements are received by neighboring switches, which update their VTP and VLAN configurations as necessary.
The following global configuration information is distributed in VTP advertisements:
•
•
•
•
•
VTP Configuration Guidelines and Restrictions
Follow these guidelines and restrictions when implementing VTP in your network:
•
•
•
•
•
•
•
Spanning Tree Protocol
This section provides information about configuring the STP on an Ethernet switch.
Spanning Tree is a Layer 2 link management protocol that provides path redundancy while preventing undesirable loops in the network. For a Layer 2 Ethernet network to function properly, only one active path can exist between any two stations. Spanning Tree operation is transparent to end stations, which cannot detect whether they are connected to a single LAN segment or to a switched LAN of multiple segments.
The Ethernet switch uses STP (the IEEE 802.1D bridge protocol) on all VLANs. By default, a single instance of STP runs on each configured VLAN (provided that you do not manually disable STP). You can enable and disable STP on a per-VLAN basis.
When you create fault-tolerant internetworks, you must have a loop-free path between all nodes in a network. The Spanning Tree algorithm calculates the best loop-free path throughout a switched Layer 2 network. Switches send and receive Spanning Tree frames at regular intervals. The switches do not forward these frames, but use the frames to construct a loop-free path.
Multiple active paths between end stations cause loops in the network. If a loop exists in the network, end stations might receive duplicate messages and switches might learn endstation MAC addresses on multiple Layer 2 interfaces. These conditions result in an unstable network.
STP defines a tree with a root switch and a loop-free path from the root to all switches in the Layer 2 network. Spanning Tree forces redundant data paths into a standby (blocked) state. If a network segment in the Spanning Tree fails and a redundant path exists, the Spanning Tree algorithm recalculates the Spanning Tree topology and activates the standby path.
When two ports on a switch are part of a loop, the Spanning Tree port priority and port path cost setting determine which port is put in the forwarding state and which port is put in the blocking state. The Spanning Tree port priority value represents the location of an interface in the network topology and how well located it is to pass traffic. The Spanning Tree port path cost value represents media speed.
Bridge Protocol Data Units
The stable active Spanning Tree topology of a switched network is determined by the following:
•
•
•
The bridge protocol data units (BPDUs) are transmitted in one direction from the root switch, and each switch sends configuration BPDUs to communicate and compute the Spanning Tree topology. Each configuration BPDU contains the following minimal information:
•
•
•
•
•
•
Note
A BPDU exchange results in the following:
•
•
•
•
•
•
For each VLAN, the switch with the highest bridge priority (the lowest numerical priority value) is elected as the root switch. If all switches are configured with the default priority (32768), the switch with the lowest MAC address in the VLAN becomes the root switch.
The Spanning Tree root switch is the logical center of the Spanning Tree topology in a switched network. All paths that are not needed to reach the root switch from anywhere in the switched network are placed in Spanning Tree blocking mode.
BPDUs contain information about the transmitting bridge and its ports, including bridge and MAC addresses, bridge priority, port priority, and path cost. Spanning Tree uses this information to elect the root bridge and root port for the switched network, as well as the root port and designated port for each switched segment.
STP Timers
Table 3 describes the STP timers that affect the entire Spanning Tree performance.
Spanning Tree Port States
Propagation delays can occur when protocol information passes through a switched LAN. As a result, topology changes can take place at different times and at different places in a switched network. When a Layer 2 interface transitions directly from nonparticipation in the Spanning Tree topology to the forwarding state, it can create temporary data loops.
Ports must wait for new topology information to propagate through the switched LAN before starting to forward frames. They must allow the frame lifetime to expire for frames that have been forwarded using the old topology.
Each Layer 2 interface on a switch using Spanning Tree exists in one of the following five states:
•
•
•
•
•
A Layer 2 interface moves through these five states as follows:
•
•
•
•
•
Note
Cisco 3700 Series documentation that is available at the following URL: /en/US/docs/ios/12_2t/12_2t8/feature/guide/ft1636nm.html#1433396.
This document includes illustrations and detailed information about switch functionality.When you enable Spanning Tree, every port in the switch, VLAN, or network goes through the blocking state and the transitory states of listening and learning at power up. If properly configured, each Layer 2 interface stabilizes to the forwarding or blocking state.
When the Spanning Tree algorithm places a Layer 2 interface in the forwarding state, the following process occurs:
1.
2.
3.
4.
Blocking State
A Layer 2 interface in the blocking state does not participate in frame forwarding. After initialization, a BPDU is sent out to each Layer 2 interface in the switch. A switch initially assumes it is the root until it exchanges BPDUs with other switches. This exchange establishes which switch in the network is the root or root bridge. If only one switch is in the network, no exchange occurs, the forward delay timer expires, and the ports move to the listening state. A port always enters the blocking state following switch initialization.
A Layer 2 interface in the blocking state performs as follows:
•
•
•
•
•
•
Listening State
The listening state is the first transitional state a Layer 2 interface enters after the blocking state. The Layer 2 interface enters this state when STP determines that the Layer 2 interface should participate in frame forwarding.
A Layer 2 interface in the listening state performs as follows:
•
•
•
•
•
•
Learning State
A Layer 2 interface in the learning state prepares to participate in frame forwarding. The Layer 2 interface enters the learning state from the listening state.
A Layer 2 interface in the learning state performs as follows:
•
•
•
•
•
•
Forwarding State
A Layer 2 interface in the forwarding state forwards frames. The Layer 2 interface enters the forwarding state from the learning state.
A Layer 2 interface in the forwarding state performs as follows:
•
•
•
•
•
•
Disabled State
A Layer 2 interface in the disabled state does not participate in frame forwarding or Spanning Tree. A Layer 2 interface in the disabled state is virtually nonoperational.
A disabled Layer 2 interface performs as follows:
•
•
•
•
•
Default Spanning Tree Configuration
Table 4 provides a description of the default Spanning Tree configuration.
Spanning Tree Port Priority
In the event of a loop, Spanning Tree considers port priority when selecting an interface to put into the forwarding state. You can assign higher priority values to interfaces that you want Spanning Tree to select first, and lower priority values to interfaces that you want Spanning Tree to select last. If all interfaces have the same priority value, Spanning Tree puts the interface with the lowest interface number in the forwarding state and blocks other interfaces. The possible priority range is 0 through 255, configurable in increments of 4 (the default is 128).
Cisco IOS software uses the port priority value when the interface is configured as an access port and uses VLAN port priority values when the interface is configured as a trunk port.
Spanning Tree Port Cost
The Spanning Tree port path cost default value is derived from the media speed of an interface. In the event of a loop, Spanning Tree considers port cost when selecting an interface to put into the forwarding state. You can assign lower cost values to interfaces that you want Spanning Tree to select first and higher cost values to interfaces that you want Spanning Tree to select last. If all interfaces have the same cost value, Spanning Tree puts the interface with the lowest interface number in the forwarding state and blocks other interfaces.
The possible cost range is 0 through 65535 (the default is media-specific).
Spanning Tree uses the port cost value when the interface is configured as an access port and uses VLAN port cost values when the interface is configured as a trunk port.
Cisco Discovery Protocol
Cisco Discovery Protocol (CDP) is a protocol that runs over Layer 2 (the data link layer) on all Cisco routers, bridges, access servers, and switches. CDP allows network management applications to discover Cisco devices that are neighbors of already known devices, in particular, neighbors running lower-layer, transparent protocols. With CDP, network management applications can learn the device type and the SNMP agent address of neighboring devices. This feature enables applications to send SNMP queries to neighboring devices.
CDP runs on all LAN and WAN media that support Subnetwork Access Protocol (SNAP). Each CDP-configured device sends periodic messages to a multicast address. Each device advertises at least one address at which it can receive SNMP messages. The advertisements also contain the time-to-live, or hold-time information, which indicates the length of time a receiving device should hold CDP information before discarding it.
Quality of Service
Typically, networks operate on a best-effort delivery basis, which means that all traffic has equal priority and an equal chance of being delivered in a timely manner. When congestion occurs, all traffic has an equal chance of being dropped.
With the QoS feature configured on your switch, you can select specific network traffic, prioritize it according to its relative importance, and use congestion-management and congestion-avoidance techniques to provide preferential treatment. Implementing QoS in your network makes network performance more predictable and bandwidth utilization more effective.
The QoS implementation for this release is based on the DiffServ architecture, an emerging standard from the Internet Engineering Task Force (IETF). This architecture specifies that each packet is classified upon entry into the network. The classification is carried in the IP packet header, using 6 bits from the deprecated IP type of service (ToS) field to carry the classification (class) information. Classification can also be carried in the Layer 2 frame.
These special bits in the Layer 2 frame or a Layer 3 packet are described here and shown in Figure 1.
•
•
•
•
•
•
•
•
Figure 1 QoS Classification Layers in Frames and Packets
Note
All switches and routers across the Internet rely on the class information to provide the same forwarding treatment to packets with the same class information and different treatment to packets with different class information. The class information in the packet can be assigned by end hosts or by switches or routers along the way, based on a configured policy, detailed examination of the packet, or both. Detailed examination of the packet is expected to happen closer to the edge of the network so that the core switches and routers are not overloaded.
Switches and routers along the path can use the class information to limit the amount of resources allocated per traffic class. The behavior of an individual device when handling traffic in the DiffServ architecture is called per-hop behavior. If all devices along a path provide a consistent per-hop behavior, you can construct an end-to-end QoS solution.
Implementing QoS in your network can be a simple or complex task and depends on the QoS features offered by your internetworking devices, the traffic types and patterns in your network, and the granularity of control you need over incoming and outgoing traffic.
The Ethernet switch can function as a Layer 2 switch connected to a Layer 3 router. When a packet enters the Layer 2 engine directly from a switch port, it is placed into one of four queues in the dynamic, 120 KB shared memory buffer. The queue assignment is based on the dot1p value in the packet. The queues are then serviced on a weighted round-robin (WRR) basis.
Table 5 summarizes the queues, CoS values, and weights for Layer 2 QoS on the Ethernet switch.
Table 5 Queues, CoS Values, and Weights for Layer2 QoS
3
6,7
8
2
4,5
4
1
0,3
2
0
1,2
1
The weights specify the number of packets that are serviced in the queue before moving on to the next queue. If the queue has no packets to be serviced, it is skipped. Weighted Random Early Detection (WRED) is not supported on the Fast Ethernet ports.
The WRR default values cannot be changed. There are currently no CLI commands to determine QoS information for WRR weights and queue mappings. You cannot configure port based QoS on the Layer 2 switch ports.
Configuration Guidelines
This section provides guidelines for configuring the switch and contains the following sections:
•
•
•
•
•
Configuration Prerequisites
The following are prerequisites to configuring the Ethernet switch:
•
•
Note
Configuring Layer 2 Interfaces
This section provides the following configuration information:
•
•
•
Configuring a Range of Interfaces
Use the interface range command in global configuration mode to configure a range of interfaces.
Defining a Range Macro
Use the define interface-range command in global configuration mode to define an interface range macro:
Verifying Configuration of a Range of Interfaces
Use the show running-configuration command to show the defined interface-range macro configuration, as shown below:
Router#show running-configuration | include define interface-range enet_listdefine interface-range enet_list FastEthernet1 - 4Configuring Layer 2 Optional Interface Features
•
•
•
•
•
•
Interface Speed and Duplex Configuration Guidelines
When configuring an interface speed and duplex mode, note these guidelines:
•
•
•
Caution
Configuring the Interface Speed
Follow these steps to set the interface speed, beginning with the interface fastethernet command in global configuration mode:
Note
Configuring the Interface Duplex Mode
Follow these steps to set the duplex mode of an Ethernet or Fast Ethernet interface, beginning with the interface fastethernet command in global configuration mode:
Note
The following example shows how to set the interface duplex mode to full on Fast Ethernet interface 4:
Router(config)#interface fastethernet 4Router(config-if)#duplex fullVerifying Interface Speed and Duplex Mode Configuration
Use the show interfaces command to verify the interface speed and duplex mode configuration for an interface, as shown in the following output example:
Router#show interfaces fastethernet 4FastEthernet4 is up, line protocol is downHardware is Fast Ethernet, address is 0000.0000.0c89 (bia 0000.0000.0c89)MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Auto-duplex, Auto-speedARP type: ARPA, ARP Timeout 04:00:00Last input never, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 input packets with dribble condition detected3 packets output, 1074 bytes, 0 underruns(0/0/0)0 output errors, 0 collisions, 5 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outRouter#Configuring a Description for an Interface
You can add a description of an interface to help you remember its function. The description appears in the output of the following commands: show configuration, show running-config, and show interfaces.
Use the description command, in interface configuration mode, to add a description for an interface:
Configuring an Ethernet Interface as a Layer 2 Trunk
Use the following commands, beginning in global configuration mode, to configure an Ethernet interface as a Layer 2 trunk:
Note
Verifying an Ethernet Interface as a Layer 2 Trunk
Use the following show commands to verify the configuration for an Ethernet interface as a Layer 2 trunk.
Router#show running-config interface fastethernet 4Building configuration...Current configuration:!interface FastEthernet4no ip addressswitchport trunk encapsulation dot1qendRouter#show interfaces fastethernet 4 switchportName: Fa4Switchport: EnabledAdministrative Mode: trunkOperational Mode: trunkAdministrative Trunking Encapsulation: dot1qNegotiation of Trunking: DisabledAccess Mode VLAN: 0 ((Inactive))Trunking Native Mode VLAN: 1 (default)Trunking VLANs Enabled: ALLTrunking VLANs Active: nonePriority for untagged frames: 0Override vlan tag priority: FALSEVoice VLAN: noneAppliance trust: noneRouter#show interfaces fastethernet 4 trunkPort Mode Encapsulation Status Native vlanFa4 on 802.1q trunking 1Port Vlans allowed on trunkFa4 1-1005Port Vlans allowed and active in management domainFa4 1-2,200,300Port Vlans in spanning tree forwarding state and not prunedFa4 1-2,200,300Router#Configuring an Ethernet Interface as Layer 2 Access
Use the following commands, beginning in global configuration mode, to configure an Ethernet interface as Layer 2 access:
Verifying an Ethernet Interface as Layer 2 Access
Use the show running-config interface command to verify the running configuration of the interface, as shown below:
Router#show running-config interface fastethernet portUse the show interfaces command to verify the switch port configuration of the interface, as shown below:
Router#show interfaces fastethernet port switchportConfiguring VLANs and SVIs
This section describes how to configure VLANs and SVIs on the switch, and contains the following sections:
•
Configuring VLANs
Use the following commands, beginning in privileged EXEC mode, to configure an Ethernet interface as Layer 2 access:
Verifying the VLAN Configuration
You can verify the VLAN configuration in VLAN database mode.
Use the show command in VLAN database mode to verify the VLAN configuration, as shown below:
Router(vlan)#showVLAN ISL Id: 1Name: defaultMedia Type: EthernetVLAN 802.10 Id: 100001State: OperationalMTU: 1500Translational Bridged VLAN: 1002Translational Bridged VLAN: 1003VLAN ISL Id: 2Name: VLAN0002Media Type: EthernetVLAN 802.10 Id: 100002State: OperationalMTU: 1500VLAN ISL Id: 1002Name: fddi-defaultMedia Type: FDDIVLAN 802.10 Id: 101002State: OperationalMTU: 1500Bridge Type: SRBTranslational Bridged VLAN: 1Translational Bridged VLAN: 1003<snip>Router(vlan)#Enter the show vlan-switch command in EXEC mode using the Cisco IOS CLI to verify the VLAN configuration, as shown below:
Router#show vlan-switchVLAN Name Status Ports---- -------------------------------- --------- -------------------------------1 default active Fa1, Fa22 VLAN0002 active Fa3200 VLAN0200 active300 VLAN0300 active1002 fddi-default active1003 token-ring-default active1004 fddinet-default active1005 trnet-default activeVLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------1 enet 100001 1500 - - - - - 1002 10031002 fddi 101002 1500 - - - - - 1 10031003 tr 101003 1500 1005 0 - - srb 1 10021004 fdnet 101004 1500 - - 1 ibm - 0 01005 trnet 101005 1500 - - 1 ibm - 0 0Router#Configuring SVIs
Use the following commands, beginning in global configuration mode, to configure an SVI for Layer 3 processing:
Note
Verifying the SVI Configuration
Use the show interface vlan vlan_id command to verify the SVI configuration, as shown in the following output example:
Router#show interface vlan 2Vlan2 is up, line protocol is upHardware is EtherSVI, address is 0005.9a39.4f70 (bia 0005.9a39.4f70)MTU 1500 bytes, BW 100000 Kbit, DLY 1000000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setARP type: ARPA, ARP Timeout 04:00:00Last input never, output never, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 packets output, 0 bytes, 0 underruns0 output errors, 3 interface resets0 output buffer failures, 0 output buffers swapped outRouter#Deleting a VLAN Instance from the Database
When you delete a VLAN from a switch that is in VTP server mode, the VLAN is removed from all switches in the VTP domain. When you delete a VLAN from a switch that is in VTP transparent mode, the VLAN is deleted only on that specific switch.
You cannot delete the default VLANs for the different media types: Ethernet VLAN 1 and FDDI or Token Ring VLANs 1002 to 1005.
Use the following commands, beginning in privileged EXEC mode, to delete a VLAN from the database:
Verifying VLAN Deletion
You can verify that a VLAN has been deleted from the switch in VLAN database mode.
Use the show command in VLAN database mode to verify that a VLAN has been deleted from the switch, as shown in the following output example:
Router(vlan)#showVLAN ISL Id: 1Name: defaultMedia Type: EthernetVLAN 802.10 Id: 100001State: OperationalMTU: 1500Translational Bridged VLAN: 1002Translational Bridged VLAN: 1003VLAN ISL Id: 1002Name: fddi-defaultMedia Type: FDDIVLAN 802.10 Id: 101002State: OperationalMTU: 1500Bridge Type: SRBTranslational Bridged VLAN: 1Translational Bridged VLAN: 1003<snip>Router(vlan)#Enter the show vlan-switch brief command in EXEC mode, using the Cisco IOS CLI to verify that a VLAN has been deleted from the switch, as shown in the following output example:
Router#show vlan-switch briefVLAN Name Status Ports---- -------------------------------- --------- -------------------------------1 default active Fa1, Fa22 VLAN0002 active Fa3200 VLAN0200 active300 VLAN0300 active1002 fddi-default active1003 token-ring-default active1004 fddinet-default active1005 trnet-default activeRouter#Deleting an SVI
Use the following commands, beginning in global configuration mode, to delete an SVI:
Step 1
Removes the SVI interface corresponding to the VLAN.
Step 2
Router(config)#endExits configuration mode.
Note
Configuring VTP (Transparent Mode)
The Ethernet switch supports VTP only in transparent mode. This section describes how to configure the Ethernet switch in VTP transparent mode. When you configure the switch as VTP transparent, you disable VTP on the switch.
A VTP transparent switch does not send VTP updates and does not act on VTP updates received from other switches. However, a VTP transparent switch running VTP version 2 does forward received VTP advertisements out all of its trunk links.
Use the following commands, beginning in privileged EXEC mode, to disable VTP on the switch:
Verifying VTP
Use the show vtp status command to verify VTP status, as shown in the following output example:
Router#show vtp statusVTP Version : 2Configuration Revision : 0Maximum VLANs supported locally : 256Number of existing VLANs : 8VTP Operating Mode : TransparentVTP Domain Name : NULLVTP Pruning Mode : DisabledVTP V2 Mode : DisabledVTP Traps Generation : DisabledMD5 digest : 0x99 0x04 0x23 0x53 0x35 0x77 0x0F 0xD0Configuration last modified by 10.1.1.1 at 3-1-02 00:23:59Router#
Note
Configuring Spanning Tree
This section describes the configuration of Spanning Tree protocol on the switch, and contains the following sections:
•
•
•
•
•
Enabling Spanning Tree
You can enable Spanning Tree on a per-VLAN basis. The switch maintains a separate instance of Spanning Tree for each VLAN (except on VLANs on which you disable Spanning Tree).
Use the following commands, in global configuration mode, to enable Spanning Tree on a per-VLAN basis:
Step 1
Enables Spanning Tree protocol on a per-VLAN basis.
Step 2
Router(config)#endExits configuration mode.
Verifying Spanning Tree
Use the show spanning-tree vlan to verify Spanning Tree configuration, as shown in the following output example:
Router#show spanning-tree vlan 200VLAN200 is executing the ieee compatible Spanning Tree protocolBridge Identifier has priority 32768, address 000b.be96.49a8Configured hello time 2, max age 20, forward delay 15We are the root of the spanning treeTopology change flag not set, detected flag not setNumber of topology changes 1 last change occurred 00:04:12 agofrom FastEthernet4Times: hold 1, topology change 35, notification 2hello 2, max age 20, forward delay 15Timers: hello 1, topology change 0, notification 0, aging 0Port 4 (FastEthernet4) of VLAN200 is forwardingPort path cost 19, Port priority 128, Port Identifier 128.4.Designated root has priority 32768, address 000b.be96.49a8Designated bridge has priority 32768, address 000b.be96.49a8Designated port id is 128.4, designated path cost 0Timers: message age 0, forward delay 0, hold 0Number of transitions to forwarding state: 1BPDU: sent 141, received 0Router#Configuring Spanning Tree Port Priority
Use the following commands, beginning in global configuration mode, to configure the Spanning Tree port priority of an interface.
Verifying Spanning Tree Port Priority
Use the show spanning-tree interface to verify the Spanning Tree interface and the Spanning Tree port priority configuration, as shown in the following output example:
Router#show spanning-tree interface fastethernet 3Port 264 (FastEthernet3) of VLAN2 is forwardingPort path cost 19, Port priority 100, Port Identifier 129.8.Designated root has priority 32768, address 0010.0d40.34c7Designated bridge has priority 32768, address 0010.0d40.34c7Designated port id is 128.1, designated path cost 0Timers: message age 2, forward delay 0, hold 0Number of transitions to forwarding state: 1BPDU: sent 0, received 13513Router#Configuring Spanning Tree Port Cost
Use the following commands, beginning in global configuration mode, to configure the Spanning Tree port cost of an interface:
Verifying Spanning Tree Port Cost
Use the show spanning-tree vlan command to verify the Spanning Tree port cost configuration, as shown in the following output example:
Router#show spanning-tree vlan 200!Port 264 (FastEthernet3) of VLAN200 is forwardingPort path cost 17, Port priority 64, Port Identifier 129.8.Designated root has priority 32768, address 0010.0d40.34c7Designated bridge has priority 32768, address 0010.0d40.34c7Designated port id is 128.1, designated path cost 0Timers: message age 2, forward delay 0, hold 0Number of transitions to forwarding state: 1BPDU: sent 0, received 13513!Router#Configuring the Bridge Priority of a VLAN
Caution
Use the following commands, in global configuration mode, to configure the Spanning Tree bridge priority of a VLAN:
Verifying the Bridge Priority of a VLAN
Use the show spanning-tree vlan bridge command to verify the bridge priority, as shown in the following output example.
Router#show spanning-tree vlan 200 bridge briefHello Max FwdVlan Bridge ID Time Age Delay Protocol---------------- -------------------- ---- ---- ----- --------VLAN200 33792 0050.3e8d.64c8 2 20 15 ieeeRouter#Configuring the Hello Time
Use the following commands, in global configuration mode, to configure the hello interval for the Spanning Tree.
Configuring the Forward-Delay Time for a VLAN
Use the following commands, in global configuration mode, to configure the forward delay for the Spanning Tree:
Configuring the Maximum Aging Time for a VLAN
Use the following commands, in global configuration mode, to configure the maximum age interval for the Spanning Tree:
Configuring the Root Bridge
The Ethernet switch maintains a separate instance of Spanning Tree for each active VLAN configured on the switch. A bridge ID, consisting of the bridge priority and the bridge MAC address, is associated with each instance. For each VLAN, the switch with the lowest bridge ID will become the root bridge for that VLAN.
To configure a VLAN instance to become the root bridge, the bridge priority can be modified from the default value (32768) to a significantly lower value so that the bridge becomes the root bridge for the specified VLAN. Use the spanning-tree vlan vlan-ID root command to alter the bridge priority.
The switch checks the bridge priority of the current root bridges for each VLAN. The bridge priority for the specified VLANs is set to 8192 if this value will cause the switch to become the root for the specified VLANs.
If any root switch for the specified VLANs has a bridge priority lower than 8192, the switch sets the bridge priority for the specified VLANs to 1 less than the lowest bridge priority.
For example, if all switches in the network have the bridge priority for VLAN 100 set to the default value of 32768, entering the spanning-tree vlan 100 root primary command on a switch will set the bridge priority for VLAN 100 to 8192, causing the switch to become the root bridge for VLAN 100.
Note
Use the diameter keyword to specify the Layer 2 network diameter (that is, the maximum number of bridge hops between any two end stations in the Layer 2 network). When you specify the network diameter, the switch automatically picks an optimal hello time, forward delay time, and maximum age time for a network of that diameter, which can significantly reduce the Spanning Tree convergence time. You can use the hello keyword to override the automatically calculated hello time.
Note
Use the following commands, in global configuration mode, to configure the switch as the root:
Disabling Spanning Tree
Use the following commands, in global configuration mode, to disable Spanning Tree on a per-VLAN basis.
Step 1
Disables Spanning Tree on a per-VLAN basis.
Step 2
Router(config)#endExits configuration mode.
Verifying that Spanning Tree Is Disabled
Use the show spanning-tree vlan command to verify the that the Spanning Tree is disabled, as shown in the following output example:
Router#show spanning-tree vlan 200<...output truncated...>Spanning tree instance for VLAN 200 does not exist.Router#Configuring Cisco Discovery Protocol (CDP)
This section describes the following features of Cisco Discovery Protocol:
•
•
Configuring Cisco Discovery Protocol (CDP)
Use the following command, in global configuration mode, to enable CDP globally:
Enables CDP globally. Use the no keyword to disable CDP.
Verifying the CDP Global Configuration
Use the show cdp command to verify the CDP configuration, as shown in the following output example:
Router#show cdpGlobal CDP information:Sending CDP packets every 120 secondsSending a holdtime value of 180 secondsSending CDPv2 advertisements is enabledRouter#Enabling CDP on an Interface
Use the following command, in interface configuration mode, to enable CDP on an interface:
The following example shows how to enable CDP on Fast Ethernet interface 3:
Router(config)#interface fastethernet 3Router(config-if)#cdp enableVerifying the CDP Interface Configuration
Use the show cdp interface command to verify the CDP configuration for an interface, as shown in the following output example:
Router#show cdp interface fastethernet 3FastEthernet3 is up, line protocol is upEncapsulation ARPASending CDP packets every 120 secondsHoldtime is 180 secondsRouter#Verifying CDP Neighbors
Use the show cdp neighbors command to verify information about the neighboring equipment, as shown in the following output example:
Router#show cdp neighborsCapability Codes: R - Router, T - Trans Bridge, B - Source Route BridgeS - Switch, H - Host, I - IGMP, r - RepeaterDevice ID Local Intrfce Holdtme Capability Platform Port IDR51-C13-3524 Fas 1 159 T S WS-C3524-PFas 0/21orig_callgen Fas 2 160 R 3640 Fas 1/07200_1 Fas 3 177 R T 7206VXR Fas 0/0Monitoring and Maintaining CDP
Use one or more of the following commands, beginning in privileged EXEC mode, to monitor and maintain CDP on your device:
Verifying the Switch Port Configuration
Follow these steps to verify the switch port configuration:
Step 1
Router#show run interface <interface>Step 2
Router#write memory
Configuring IP Information
This section describes how to assign IP information on the Ethernet switch. The following topics are included:
•
•
Assigning IP Information to the Switch
You can use a BOOTP server to automatically assign IP information to the switch; however, the BOOTP server must be set up in advance with a database of physical MAC addresses and corresponding IP addresses, subnet masks, and default gateway addresses. In addition, the switch must be able to access the BOOTP server through one of its ports.
At startup, a switch without an IP address requests the information from the BOOTP server; the requested information is saved in the switch running the configuration file. To ensure that the IP information is saved when the switch is restarted, save the configuration by entering the write memory command in privileged EXEC mode.
You can change the information in these fields. The mask identifies the bits that denote the network number in the IP address. When you use the mask to subnet a network, the mask is then referred to as a subnet mask. The broadcast address is reserved for sending messages to all hosts. The CPU sends traffic to an unknown IP address through the default gateway.
Use the following commands, beginning in privileged EXEC mode, to enter the IP information:
Note
Use the following commands, beginning in global configuration mode, to remove an IP address from the switch:
Caution
Specifying a Domain Name and Configuring the DNS
Each unique IP address can have a host name associated with it. The Cisco IOS software maintains a EC mode, and related Telnet support operations. This cache speeds the process of converting names to addresses.
IP defines a hierarchical naming scheme that allows a device to be identified by its location or domain. Domain names are pieced together with periods (.) as the delimiting characters. For example, Cisco Systems is a commercial entity that IP identifies by a com domain name, so its domain name is cisco.com. A specific device in this domain, the FTP system, for example, is identified as ftp.cisco.com.
To track domain names, IP has defined the concept of a domain name system (DNS), the purpose of which is to hold a cache (or database) of names mapped to IP addresses. To map domain names to IP addresses, you must first identify the host names and then specify a name server and enable the DNS, the Internet's global naming scheme that uniquely identifies network devices.
Specifying the Domain Name
You can specify a default domain name that the software uses to complete domain name requests. You can specify either a single domain name or a list of domain names. When you specify a domain name, any IP host name without a domain name has that domain name appended to it before being added to the host table.
Specifying a Name Server
You can specify up to six hosts that can function as a name server to supply name information for the DNS.
Enabling the DNS
If your network devices require connectivity with devices in networks for which you do not control name assignment, you can assign device names that uniquely identify your devices within the entire internetwork. The Internet's global naming scheme, the DNS, accomplishes this task. This service is enabled by default.
Configuration Examples
This section provides the following configuration examples:
•
•
Range of Interface Examples
Single Range Configuration Example
The following example shows all Fast Ethernet interfaces being reenabled:
Router(config)#int range fastEthernet 1 - 4Router(config-if-range)#no shutRouter(config-if-range)#*Mar 3 22:38:35.929: %LINK-3-UPDOWN: Interface FastEthernet1, changed state to up*Mar 3 22:38:35.933: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to up*Mar 3 22:38:35.941: %LINK-3-UPDOWN: Interface FastEthernet3, changed state to up*Mar 3 22:38:35.949: %LINK-3-UPDOWN: Interface FastEthernet4, changed state to up*Mar 3 22:38:36.105: %DTP-5-TRUNKPORTON: Port Fa4 has become dot1q trunk*Mar 3 22:38:36.589: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up*Mar 3 22:38:36.597: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2, changed state to up*Mar 3 22:38:36.933: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet2, changed state to up*Mar 3 22:38:36.941: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3, changed state to up*Mar 3 22:38:36.949: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4, changed state to upRouter(config-if-range)#Range Macro Definition Example
The following example shows an interface-range macro named enet_list being defined to select Fast Ethernet interfaces 1 through 4:
Router(config)#define interface-range enet_list fastethernet 1 - 4Router(config)#The following example shows how to change to the interface-range configuration mode using the interface-range macro enet_list:
Router(config)#interface range macro enet_listOptional Interface Feature Examples
Interface Speed Example
The following example shows the interface speed being set to 100 Mbps on Fast Ethernet interface 4:
Router(config)#interface fastethernet 4Router(config-if)# speed 100Setting the Interface Duplex Mode Example
The following example shows the interface duplex mode being set to full on Fast Ethernet interface 4:
Router(config)#interface fastethernet 4Router(config-if)#duplex fullAdding a Description for an Interface Example
The following example shows how to add a description of Fast Ethernet interface 4:
Router(config)#interface fastethernet 4Router(config-if)#description Link to root switchConfiguring an Ethernet Interface as a Layer 2 Trunk Example
The following example shows how to configure the Fast Ethernet interface 4 as an 802.1Q trunk. This example assumes that the neighbor interface is configured to support 802.1Q trunking.
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#interface fastethernet 4Router(config-if)#shutdownRouter(config-if)#switchport trunk encapsulation dot1qRouter(config-if)#switchport mode trunkRouter(config-if)#no shutdownRouter(config-if)#endRouter#exitVLAN Configuration Example
The following example shows how to configure the VLAN:
Router#vlan databaseRouter(vlan)#vlan 3VLAN 3 added:Name: VLAN0003Router(vlan)#exitAPPLY completed.Exiting....Disabling VTP (VTP Transparent Mode) Example
The following example shows how to configure the switch as VTP transparent:
Router#vlan databaseRouter(vlan)#vtp transparentSetting device to VTP TRANSPARENT mode.Router(vlan)#exitAPPLY completed.Exiting....Spanning Tree Examples
The following example shows Spanning Tree being enabled on VLAN 200:
Router#configure terminalRouter(config)#spanning-tree vlan 200Router(config)#endRouter#
Note
The following example shows Spanning Tree being disabled on VLAN 200:
Router#configure terminalRouter(config)#no spanning-tree vlan 200Router(config)#endRouter#Spanning-Tree Interface and Spanning-Tree Port Priority Example
The following example shows the VLAN port priority of an interface being configured:
Router#configure terminalRouter(config)#interface fastethernet 3Router(config-if)#spanning-tree vlan 200 port-priority 64Router(config-if)#endRouter#The following example shows how to verify the configuration of VLAN 200 on the interface when it is configured as a trunk port:
Router#show spanning-tree vlan 200!Port 264 (FastEthernet3) of VLAN200 is forwardingPort path cost 19, Port priority 64, Port Identifier 129.8.Designated root has priority 32768, address 0010.0d40.34c7Designated bridge has priority 32768, address 0010.0d40.34c7Designated port id is 128.1, designated path cost 0Timers: message age 2, forward delay 0, hold 0Number of transitions to forwarding state: 1BPDU: sent 0, received 13513Router#Spanning-Tree Port Cost Example
The following example shows how to change the Spanning Tree port cost of a Fast Ethernet interface:
Router#configure terminalRouter(config)#interface fastethernet 3Router(config-if)#spanning-tree cost 18Router(config-if)#endRouter#The following example shows how to configure the Spanning Tree VLAN port cost of a Fast Ethernet interface:
Router#configure terminalRouter(config)#interface fastethernet 3Router(config-if)#spanning-tree vlan 200 cost 17Router(config-if)#exitThe following example shows how to verify the configuration of the interface when it is configured as an access port:
Router#show spanning-tree interface fastethernet 3Port 264 (FastEthernet3) of VLAN200 is forwardingPort path cost 18, Port priority 100, Port Identifier 129.8.Designated root has priority 32768, address 0010.0d40.34c7Designated bridge has priority 32768, address 0010.0d40.34c7Designated port id is 128.1, designated path cost 0Timers: message age 2, forward delay 0, hold 0Number of transitions to forwarding state: 1BPDU: sent 0, received 13513Router#Bridge Priority of a VLAN
The following example shows the bridge priority of VLAN 200 being configured to 33792:
Router#configure terminalRouter(config)#spanning-tree vlan 200 priority 33792Router(config)#endRouter#Hello Time Example
The following example shows the hello time for VLAN 200 being configured to 7 seconds:
Router#configure terminalRouter(config)#spanning-tree vlan 200 hello-time 7Router(config)#endRouter#Forward-Delay Time for a VLAN Example
The following example shows the forward delay time for VLAN 200 being configured to 21 seconds:
Router#configure terminalRouter(config)#spanning-tree vlan 200 forward-time 21Router(config)#endRouter#Maximum Aging Time for a VLAN Example
The following example configures the maximum aging time for VLAN 200 to 36 seconds:
Router#configure terminalRouter(config)#spanning-tree vlan 200 max-age 36Router(config)#endRouter#Spanning Tree Root Example
The following example shows the switch being configured as the root bridge for VLAN 10, with a network diameter of 4:
Router#configure terminalRouter(config)#spanning-tree vlan 10 root primary diameter 4Router(config)#exitRouter#Inter-VLAN Routing Example
Configuring inter-VLAN routing is identical to the configuration on an Ethernet switch with a Multilayer Switch Feature Card (MSFC). Configuring an interface for WAN routing is consistent with other Cisco IOS platforms.
The following example provides a sample configuration:
Router# interface Vlan 160Router(config-if)#description voice vlanRouter(config-if)#ip address 10.6.1.1 255.255.255.0Router(config)#interface Vlan 60Router(config-if)#description data vlanRouter(config-if)#ip address 10.60.1.1 255.255.255.0Router(config-if)#interface Serial1/0Router(config-if)#ip address 160.3.1.2 255.255.255.0
Note
Related Documentation
Refer to the following documentation for additional information on the Cisco 1700 series routers:
•
•
•
•
•
Obtaining Documentation
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html
All users can order annual or quarterly subscriptions through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can send your comments in e-mail to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance.
Cisco TAC Website
The Cisco TAC website (http://www.cisco.com/tac) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
Opening a TAC Case
The online TAC Case Open Tool (http://www.cisco.com/tac/caseopen) is the fastest way to open P3 and P4 cases. (Your network is minimally impaired or you require product information). After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using these recommendations, your case will be assigned to a Cisco TAC engineer.
For P1 or P2 cases (your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
TAC Case Priority Definitions
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
•
http://www.cisco.com/go/packet
•
http://www.cisco.com/go/iqmagazine
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/index.html
Glossary
802.1p—IEEE standard for queuing and multicast support
802.1q—IEEE standard for VLAN frame tagging
AVVID—Architecture for Voice, Video, and Integrated Data
BPDU—bridge protocol data unit
CBAC—Context-based Access Control
CDP—Cisco Discovery Protocol
CoS—class of service
DSCP—Differentiated Services Code Point
IP—Internet Protocol
PSTN—public switched telephone network
QoS—quality of service
SNMP—Simple Network Management Protocol
STP—Spanning Tree Protocol
VLAN—virtual local area network
VoIP—Voice over IP
VPN—Virtual Private Network
VTP—VLAN Trunking Protocol
WAN—wide area network
WRR—weighted round-robin
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Guest
