Table Of Contents
Release Notes for Cisco 3200 Series Mobile Access Routers for Cisco IOS Release 12.2(11)YR
November 11, 2002
These release notes for the Cisco 3200 Series Mobile Access Routers describe the enhancements provided in Cisco IOS Release 12.2(11)YR. These release notes are updated as needed. Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.2 T located on Cisco.com and the Documentation CD.
For a list of the software caveats that apply to Cisco IOS Release 12.2(11)YR, see the "Caveats" section and Caveats for Cisco IOS Release 12.2 T. The caveats document is updated for every maintenance release and is located on Cisco.com and the Documentation CD.
This release note contains the following sections:
This section describes the system requirements for Cisco IOS Release 12.2(11)YR and includes the following sections:
Table 1 provides the memory requirements for the Cisco IOS feature sets supported by Cisco IOS Release 12.2(11)YR on the Cisco 3200 Series Mobile Access Router.
Cisco IOS Release 12.2(11)YR supports the Cisco 3200 Series Mobile Access Router. The Cisco 3200 Series Mobile Access Router includes the Cisco 3251 Mobile Access Router Card, Cisco 3201 Serial Mobile Interface Card, and the Fast Ethernet Switch Mobile Interface Card (FESMIC).
For detailed descriptions of new hardware features and which features are supported on each router, see the "New and Changed Information" section. For descriptions of existing hardware features and supported modules, see the configuration guides and additional documents specific to the Cisco 3200 Series Mobile Access Router, which are available on Cisco.com and the Documentation CD at the following location:
Determining the Software Version
To determine the version of Cisco IOS software running on your Cisco router, log in to the router and enter the show version EXEC command. The following sample displays command output from a Cisco 3200 series router running Cisco IOS Release 12.2(11)YR:Router> show versionCisco Internetwork Operating System SoftwareIOS (tm) 3200 Software (C3200-I11-M), Release 12.2(11)YR! text deletedConfiguration register is 0x0
Upgrading to a New Software Release
Youcan download either a software image or a configuration file via TFTP or via the console port, a ROM monitor function over the router console port. After downloading, the file is saved to the Flash memory.
Use console download when you do not have access to a TFTP server.
If you are using a PC to download a Cisco IOS image over the router console port at 115,200 bps, ensure that the PC serial port is using a 16550 universal asynchronous transmitter/receiver (UART). If the PC serial port is not using a 16550 UART, we recommend using a speed of 38,400 or less when downloading an Cisco IOS image over the console port.
Configure the PC communications port to match the router console port as follows:
•8 data bits
•1 stop bit
Follow the steps below to run Xmodem:
Step 1 Move the image file to the local drive where the xmodem will execute.
Step 2 Enter the xmodem command.
Following is the syntax and descriptions for the xmodem console download command:
xmodem [-ucyrx] destination_file_name
Feature Set Tables
The Cisco IOS software is packaged in feature sets consisting of software images, depending on the platform. Each feature set contains a specific set of Cisco IOS features. Cisco IOS Release 12.2(11)YR supports the same feature sets as Release 12.2 T, but Cisco IOS Release 12.2(11)YR can include new features supported by the Cisco 3200 series router.
Table 2 lists the features and feature sets supported in Cisco IOS Release 12.2(11)YR.
The table uses the following conventions:
•Platform and Feature Sets column
–Yes—The feature is supported in the software image.
–No—The feature is not supported in the software image.
•"In" column—The number in the "In" column indicates the Cisco IOS release in which the feature was introduced. For example, "12.2(4)YA" indicates that a feature was introduced in 12.2(4)YA. If a cell in this column is empty, the feature was included in a previous release or the initial base release.
Note These feature set tables contain only list of selected features. These tables are not cumulative—nor do they comprehensively list all the features in each image.
New and Changed Information
The following section list the new software features supported by Cisco IOS Release 12.2(11)YR for the Cisco 3200 Series Mobile Access Router.
New Software Features in Cisco IOS Release 12.2(11)YR
The following sections list the new software features supported by Cisco IOS Release 12.2(11)YR for the Cisco 3200 Series Mobile Access Router.
Basic Layer 2 Switching
Switching is a technology that alleviates congestion in Ethernet LANs by reducing traffic and increasing bandwidth utilization. An Ethernet LAN switch improves bandwidth by separating collision domains and selectively forwarding traffic to the appropriate LAN segments.
Layer 2 switching is the method by which the Fast Ethernet Switching Mobile Interface Card (FESMIC) learns the source MAC address (6 bytes) of the packets coming in on each port and places them in the forwarding table denoting the port the address resides on. When any MAC frames come in destined for a MAC address that was learned to be residing on a FESMIC port (that is, the MAC address has an entry in the FESMIC authority revocation lists [ARL] table), the packet is forwarded to the port number where that MAC station resides. Note that the packet will only be forwarded to other ports on the switch that are resident in the same Virtual LAN (VLAN).
When MAC addresses come in with unknown destinations, they are flooded to the other ports on the same VLAN and to the Mobile Access Router Card (MARC) host. When the destination MAC replies on a particular port with its source address, the MAC is thus resolved and placed in the ARL table. In this method, bridging is called plug and play and as long as source and destination pairs coreside on the FESMIC-attached LAN segments, all the bridges will communicate in a seamless fashion.
The four 10/100 auto-sensing Fast Ethernet ports on FESMIC are automatically defaulted to Layer 2 switch ports once the system is booted up. The FESMIC is in effect a "learning bridge," as defined in 802.1d, with the added VLAN capabilities of 802.1p/q. The FESMIC is fully capable of line-rate switching for all four FE ports.
Virtual LANs (VLANs) are created to provide the segmentation services traditionally provided by routers in LAN configurations. A VLAN consists of a single broadcast domain and solves the scalability problems of large flat networks by breaking a single broadcast domain into several smaller broadcast domains or VLANs. VLANs facilitate moves and changes in a network design more easily than traditional networks. VLANs improve security by isolating groups. High-security users can be grouped into a VLAN, possibly on the same physical segment, so that no users outside that VLAN can penetrate into the VLAN without appropriate routing into the VLAN via secure Layer 3 routing services.
Just as switches physically isolate collision domains for attached hosts and only forward traffic out a particular port, VLANs provide logical collision domains that confine broadcast and multicast traffic to the bridging domain.
If you do not include a Layer 3 router for a VLAN, no users outside of that VLAN can communicate with the users inside the VLAN and vice versa. This extreme level of security is highly desirable for such applications as military applications.
You can assign users who require high-performance networking to their own VLANs. You might, for example, assign to a single VLAN both an engineer who is testing a multicast application and the servers that the engineer is using. The engineer experiences improved network performance by being on a "dedicated LAN," and the rest of the engineering group experiences improved network performance because the traffic generated by the network-intensive application is isolated to another VLAN. This of course implies some areas of physical isolation of separate VLANs or prioritized service via tagging support and prioritized queuing classes within the switches/bridges of the 802.1q VLAN.
Software on the switch allows you to assign users to VLANs and later reassign them to another VLAN. Recabling to change connectivity is no longer necessary in the switched LAN environment because network management tools allow you to reconfigure the LAN logically in seconds.
Port-Based Virtual LAN
By default the four FE ports on FESMIC are defaulted to Layer 2 switch ports and all four ports belong to VLAN 1. The user can partition the four switch ports so that they belong to different VLAN groups by using switchport vlan access <vlan-id> command.
Following are the brief functional description of FESMIC port-based VLAN:
•Packets received from a port are forwarded only to ports that are members of the same VLAN as the receiving port. VLAN partitions provide hard firewalls for all traffic in different VLANs. Each VLAN has its own MAC address table.
•A VLAN comes into existence when a local port is configured to be associated with the VLAN, or when a user adds a VLAN to the local VLAN database. A maximum of 32 VLANs having VLAN ID in the range of 1-1005 is supported.
•By default, a spanning-tree instance is created for each VLAN.
802.1q Trunking Support
The 802.1q trunk port support is mainly used for VLAN extension from one switch to another 802.1q-capable switch, and for an 802.1q-capable router for inter-VLAN routing. The FESMIC will support both the VLAN extension and inter-VLAN routing in one single module.
A trunk is a point-to-point link between one or more Ethernet switch ports 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 IEEE 802.1q protocol is an industry-standard trunking encapsulation and that allows multiple VLANS to be switched/multiplexed out to a trunk port destined for the network. The designation of trunk or access is denoted via CLI by the show interface fastethernet <port number> switchport command.
The 802.1q uses an internal tagging mechanism. A tag is inserted within the frame (with ISL, the frame is encapsulated instead). Note that on an 802.1q trunk, one VLAN is not tagged. This VLAN, named the native VLAN, must be configured the same on each side of the trunk. This way, we can determine to which VLAN a frame belongs to when we receive a frame without a tag. The EtherType field identifying the 802.1q frame is 0x8100. In addition to the 12-bit VLAN-ID, 3 bits are reserved for 802.1p priority tagging. Also, inserting a tag into a frame that already has the maximum Ethernet size creates a 1522 byte frame that can be considered as a "baby giant" by the receiving equipment.
The FESMIC is capable of 802.1q tagging only; it does not support the Cisco proprietary Inter-Switch Link (ISL) encapsulation, so the FESMIC trunk port would only support the 802.1q trunking encapsulation.
Inter-Virtual LAN Routing Support
In a VLAN network, traffic and stations for multiple network layer subnets (VLANs) can coexist on a single physical LAN segment. In practice, a single VLAN corresponds to a network subnet, and a VLAN trunking capable router such as the Cisco 1700 router is required to forward traffic from a first VLAN to a second VLAN for a Layer 2 switch device such as a Cisco 1900 or Cisco 2900.
The FESMIC will enable the Cisco 3250 MAR to become one of the first few Cisco IOS Ethernet switch routers to deliver the intelligent Layer 2 switching capability and Layer 3 inter-VLAN routing functionality in a single-box solution.
In a typical Cisco IOS manageable Layer 2 switch device such as the Cisco 1900, there would be one Layer 3 virtual interface (SVI) that allows the user to configure the box over a Layer 3 protocol like SNMP or via a Telnet application. This is referred to as the management VLAN for the switch. The default management VLAN is usually the native VLAN. The user configurable management VLAN device allows the user to configure any VLAN to be the management VLAN, but only one virtual Layer 3 interface can exist in one device.
A switch routing module, like FESMIC and the 3600 network module, allows the user to configure more than one virtual Layer 3 interface to support routing capability between the different VLANs and between the virtual Layer 3 interface and any other router interface in the system by using the switch virtual interface. The user can manage the switch router with any switch virtual Layer 3 interface created in the system. The router switch port is not supported in FESMIC. The router switch port is a switch port that is capable of handling Layer 3 switching functionality in hardware, the SVI architecture has the framework to support such a functionality.
•An SVI represents a VLAN of switch ports as one interface to the routing function in the system.
•There is at least one SVI associated with a VLAN.
•It is worth noting that it is not necessary to configure a SVI for every known VLAN. It is necessary to configure a SVI only when the user wishes to route between VLANs or to provide IP host connectivity to the designated management VLAN.
•On the management SVI, an interface VLAN is created at system initialization to permit remote box administration. Additional SVIs exist only when they are explicitly configured by a user.
•Routing protocol and bridging configuration are supported.
Spanning-Tree Protocol (STP) is a link management protocol that provides path redundancy while preventing undesirable loops in the network. For an Ethernet network to function properly, only one active path can exist between any two stations. When two ports on a switch are detected to be in 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.
Spanning-Tree Protocol provides a way for switches and bridges to maintain a loop-free topology and to avoid broadcast storms that can occur if loops exist in the topology. The algorithm is fairly complex, but all the bridges connected on the network initially boot into listening state, in which they exchange Bridged Protocol Data Units (BPDUs). These BPDUs are used to calculate the loop-free spanning-tree for the network topology. These BDPUs will set ports that cause loops to block based on a priority scheme. A single bridge will also be designated as the root bridge in the spanning-tree. Ports can be assigned priority that is utilized by the STP algorithm.
For example, connecting a cable in a loop on two ports that are in same VLAN should eventually result in one of the two ports being shut off by the spanning-tree algorithm. The Spanning-Tree Protocol runs on the MARC in Cisco IOS software. BPDUs are generated once every hello-timer interval.
Once the bridge listens, it will then move on to a learning state in which it will store all the SRC MAC addresses it can see on the port in the ARL. After a certain time, the topology converges, and the switch/bridge spanning-tree places all ports to forwarding (this is all ports that are not detected as causing loops), and then MAC packets are bridged normally between ports on the same VLANs.
The 802.1q standard defines the method for running multiple VLANs over a single or multiple physical LAN segments and defines a unique spanning-tree instance to be created on each of the VLAN instances for all the VLANs in a network. A Mono Spanning-Tree (MST) network lacks some flexibility compared to a Per VLAN Spanning-Tree (PVST) network, which runs one instance of Spanning-Tree Protocol (STP) per VLAN. One spanning-tree is created for every new VLAN created on the FESMIC ports. STP is enabled by default on the VLAN and on all newly created VLANs.
Cisco developed PVST+ to allow running several STP instances (even over an 802.1q network) by using a tunneling mechanism. PVST+ can be briefly described as utilizing a Cisco device to connect a MST zone (typically another vendor's 802.1q-based network) to a PVST zone (typically a Cisco 802.1q-based network). There is no specific configuration to enter in order to achieve this. PVST+ is a spanning-tree which allows the coexistence of both PVST and Shared Spanning-Tree (SST) in a mixed vendor environment.
The Spanning-Tree Protocol takes a substantial amount of time to converge to a loop free topology. It fails to take advantage of the point-to-point wiring in todays networks. PVST is Cisco proprietary Per VLAN Spanning-Tree. PVST is enabled on all switch platforms. Rapid Spanning-Tree Protocol (RSTP) aims to improve the operation of spanning-tree while maintaining compatibility with equipment based on the (original) 802.1d spanning-tree, which will be a standardized version of the PVST.
The Cisco Shared Spanning-Tree Architecture documents use the terms MST and SST to mean Mono Spanning-Tree and Shared Spanning-Tree, respectively. However, the IEEE 802.1s uses the same terms with exactly opposite meanings; i.e., MST means Multiple Spanning-Tree, and SST is Single Spanning-Tree.
When you connect two Cisco switches through 802.1q trunks, the switches exchange spanning-tree BPDUs on each VLAN allowed on the trunks. The BPDUs on the native VLAN of the trunk are sent untagged to the reserved IEEE 802.1d spanning-tree multicast MAC address (01-80-C2-00-00-00). The BPDUs on all other VLANs on the trunk are sent tagged to the reserved Cisco SST.
For more detailed information on how Spanning-Tree Protocols work, go to:
802.1p CoS Features Support
The 802.1p class of service provides a simple mechanism to provide priority queuing/quality of service (QoS) to different packets by utilizing the 802.1q VLAN identifier (VID)/TAG field that is a 2-byte extension to the 802.1d MAC header. The 802.1p tag is mapped to different hardware queues in the FESMIC, with different queuing priorities associated with each queue.
The IEEE 802.1p specification defines eight levels of priority (0-7), with priority 7 being the highest priority. This information is carried in the 3-bit priority field of the VLAN tag header.
FESMIC supports up to two class of service (CoS) queues per egress port. For the tagged packets, the incoming packet priority can be mapped to one of the two queues, based on the priority field in the tag header or based on the result of filtering mechanism. For untagged packets, the CoS priority is derived either from a programmable field within the ARL (MAC address table) or from the result of filtering mechanism.
After the packets are mapped into a CoS queue, they are forwarded or conditioned using these scheduling algorithms:
•Strict Priority-Based Scheduling: In this policy, any packets in the two higher priority queues are transmitted first. Only when these queues empty are the packets of lower priority transmitted. The disadvantage of this scheme is potential starvation of packets in lower priority queues.
•Weighted Round-Robin Scheduling: This scheme alleviates the starvation of packets in lower priority queues by providing a certain minimum bandwidth to all queues for transmission. This bandwidth is programmable as the maximum number of packets of each CoS.
The FESMIC FE ports are set by default to use the strict priority-based scheduling after system boots up, the user can enable the weighted round-robin scheduling via the CLI.
Virtual Terminal Protocol (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. The FESMIC supports both VTP version 1 and version 2. But VTP pruning mode is not supported.
•VTP server mode
The user can create, modify, and delete VLANs and specify other configuration parameters (such as VTP version and VTP pruning) for the entire VTP domain. VTP servers advertise their VLAN configuration to other switches in the same VTP domain and synchronize their VLAN configuration with other switches, based on advertisements received over trunk links. VTP server is the default mode.
•VTP client mode
This mode functions the same way as VTP server mode functions, but it does not create, change, or delete VLANs on a VTP client.
•VTP transparent mode
Switches do not participate in VTP. 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 from their trunk interfaces.
Switch-Based Broadcast/Multicast/Unicast Storm Control
A packet storm occurs when a large number of broadcast, unicast, or multicast packets are received on a port. Forwarding these packets can cause the network to slow down or to time out. Storm control is configured for the switch as a whole but operates on a per-port basis. By default, storm control is disabled.
Storm control uses high and low thresholds to block and then restore the forwarding of broadcast, unicast, or multicast packets. You can also set the switch to shut down the port when the rising threshold is reached.
CLI commands are provided for enabling storm control thresholds, and the FESMIC is provisioned appropriately with thresholds for discarding excessive broadcast, multicast, and unicast MAC traffic in order to prevent the switch from being overwhelmed by traffic storms.
Internet Group Management Protocol (IGMP) snooping is a feature that allows the switch to "listen in" on the IGMP conversation between hosts and routers. When a switch hears an IGMP report from a host for a given multicast group, the switch adds the host's port number to the GDA list for that group. And, when the switch hears an IGMP leave, it removes the host's port from the CAM table entry.
The purpose of the IGMP snooping is to restrain multicast traffic in a switched network. By default, a LAN switch floods multicast traffic within the broadcast domain, and this can consume a lot of bandwidth if many multicast servers are sending streams to the segment.
Multicast traffic is flooded because a switch usually learns MAC addresses by looking into the source address field of all the frames it receives. But, since a multicast MAC address is never used as source address for a packet and since multicast MAC address do not appear in the MAC address table, the switch has no method for learning them. The IGMP fast-leave snooping process is supported.
Secure MAC Address/Secure Port
Network security is implemented by providing the user with the option to make a port secure by allowing only well-known MAC addresses to send in data traffic or to filter undesired MAC addresses. These MAC addresses can be provisioned into the FESMIC's filter/forward tables as static bridge table entries. Secure MAC address/port security means that if you provision a source MAC address or destination MAC address into a ports ARL filter/forward table as a static bridge table filter entry, the FESMIC can disallow or allow traffic from that MAC address (in the case of a source address), or to that MAC address (in the case of destination address) from being switched between chip ports.
The VLAN provides an inherent level of port security in that if different ports are assigned to different VLANs, traffic will not be switched between these VLANs. It may be routed or trunked but only via appropriate entries in the routing table in the MARC or via trunk provisioning as desired.
Auto-Negotiation and Auto-MDI/MDIX
All of the Ethernet ports in the FESMIC support Ethernet auto-negotiation for the line transmission speed. Auto-negotiation is a feature in which both sides will configure automatically to either 10BASE-TX or 100BASE-TX without any need for provisioning by the user. Auto-negotiation is widely used on most Ethernet interfaces and is generally the default mode of operation. As a subset of the auto-negotiation phase, the FESMIC supports an initialization process called HP Auto-MDI/MDIX. HP Auto-MDI/MDIX is enabled whenever the FESMIC is configured for auto-negotiation and whenever HP Auto-MDI/MDIX is a subset of the auto-negotiation phase in any chips supporting it. (In order to have auto-MDIX you must have auto-negotiation)
When an Ethernet interface is enabled, one end of the link must perform MDI crossover so that the transmitter on one end of the data link is connected to the receiver on the other end of the data link (generally a crossover cable is used). The Auto-MDIX feature eliminates the need for this crossover/cross-wired cabling by performing an internal crossover when a straight cable is detected during the auto-negotiation phase.
Auto-MDI/MDIX runs as a subset of the auto-negotiation phase. During auto-negotiation, the FESMIC transmits on TD+- and receives on RD+- (allowing the crossover detection during this sampling period). When connected via a straight-through cable to a device not supporting HP Auto-MDI/MDIX crossover, the FESMIC automatically switches its transmitter to RD+- and its receiver to TD+-, allowing communication to work correctly with the remote device without a crossover cable.
If both devices support HP Auto-MDI/MDIX crossover capability, a random algorithm in the HP Auto-MDI/MDIX algorithm selects only one of the two sides to perform the crossover function when required.
If the auto-negotiation feature is disabled, Auto-MDI/MDIX will not work since there is no signal transmission at initialization to sample the cabling with. Therefore, as in all systems not supporting HP Auto-MDIX, cabling will need to be correct for the devices being connected. The HP Auto-MDIX feature is disabled (via software which explicitly disables a bit in a register in the FESMIC) if the user selects the configuration of the line speed explicitly rather than leaving the default mode of auto-negotiation. Although it is possible to disable HP Auto-MDIX with auto-negotiation enabled, the current software does not implement an explicit CLI command that allows disabling of the Auto-MDIX during auto-negotiation.
Network Management and MIB Support
Cisco View is a web-based graphical device management application that provides monitoring and configuration features for Cisco Internetworking products (switches, routers, hubs, concentrators, and access servers). Cisco View aides network management by displaying a physical view of a Cisco device, allowing users to easily interact with device components to change configuration parameters or monitor statistics.
The following MIBs need to be added in Cisco IOS for FESMIC, so Cisco View can support VLAN creation and other switch functionality management effectively.
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats, severity 2 caveats are less serious, and severity 3 caveats are the least serious of these three severity levels.
Caveats in Cisco IOS Releases 12.2 and 12.2 T are also in Cisco IOS Release 12.2(11)YR. For information on caveats in Cisco IOS Release 12.2, see Caveats for Cisco IOS Release 12.2. For information on caveats in Cisco IOS Release 12.2 T, see Caveats for Cisco IOS Release 12.2 T. These two documents list severity 1 and 2 caveats and are located on Cisco.com and the Documentation CD-ROM.
Note If you have an account with Cisco.com, you can also use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in toCisco.com and click Service & Support: Technical Assistance Center: Tool Index: Bug Toolkit. Another option is to go to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
Open Caveats - Release 12.2(11)YR
This section describes possibly unexpected behavior by Cisco IOS Release 12.2(11)YR. Only severity 1 through 3 caveats are included.
PIM router fails to receive (S,G) when igmp join command is used on VLAN.
use interface which is not configured with PIM sparse for debugging the multicast traffic flow as igmp join is used for debugging.
IP header checksum errors happen under heavy traffic when the interface FastEthernet interface0/0 is configured with the command no ip mroute-cache.
Under interface FastEthernet0/0, execute ip mroute-cache.
Query for ifDesc of IfTable does not show mobile interface.
Traceback happens while configuring VTP password.
Do not use the VTP domain name of " ".
VLANS cannot be added or deleted until a VTP domain name is configured.
Use the VTP domain name of "NULL" instead of " ".
Router crashes due to the ip wccp version 1 and related commands.
After WRR bandwidth x y, not able to save WRR bandwidth 0 0 in NVRAM.
•Once the non-zero value is entered for the WRR feature, use no wrr-queue bandwidth x y and reload the router.
•Once the router is reloaded, use wrr-queue bandwidth 0 0 to turn off the CNG, and save it in the start-up configuration.
vtpVlanISCRFBackpup object returns incorrect values.
•Returns 0 when CRF backup is not configured for this VLAN.
•Returns false(2) when CRF backup is enabled for the given VLAN.
•Returns true(1) when CRF backup is explicitly disabled for the given VLAN.
The following sections describe the documentation available for the Cisco 3200 Series Mobile Access Routers. Typically, these documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other documents.
Documentation is available as electronic documents, except for feature modules and the Cisco IOS release notes, which are available online on Cisco.com and the Documentation CD-ROM.
Use these release notes with the documents listed in the following sections:
The following documents are specific to Release 12.2 and apply to Cisco IOS Release 12.2(11)YR. They are located on Cisco.com and the Documentation CD-ROM (under the heading Service & Support):
•To reach the Release Notes for the Cisco 3200 Series Mobile Access Routers for Cisco IOS Release 12.2(11)YQ, click this path:
•To reach the Cross-Platform Release Notes for Cisco IOS Release 12.2 T, click this path:
Technical Documents: Cisco IOS Software: Release 12.2: Release Notes: Cisco IOS Release 12.2 T
•To reach product bulletins, field notices, and other release-specific documents, click this path:
Technical Documents: Product Bulletins
•The Caveats for Cisco IOS Release 12.2 and Caveats for Cisco IOS Release 12.2 T documents contain caveats applicable to all platforms for all maintenance releases of Release 12.2. To reach the caveats documents, click this path:
Technical Documents: Cisco IOS Software: Release 12.2: Caveats
Note If you have an account with Cisco.com, you can also use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in toCisco.com and click Service & Support: Technical Assistance Center: Tool Index: Bug Toolkit. Another option is to go to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
Hardware installation guides, configuration and command reference guides, and additional documents are available for the Cisco 3200 Series Mobile Access Routers on Cisco.com and the Documentation CD-ROM.
Cisco 3200 Series Mobile Access Routers
Documentation specific to the Cisco 3200 Series Mobile Access Routers is available on Cisco.com and the Documentation CD at the following location:
These sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to email@example.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the Related Documentation section.
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.