Table of Contents
Release Notes for Catalyst 6000 Family MSFC Cisco IOS Release 12.1(1)EX
Current Release (February 22, 2000): 12.1(1)EX
Previous Releases:
12.0(7)XE1, 12.0(7)XE (Deferred), 12.0(3)XE2 (Deferred), 12.0(3)XE1 (Deferred)
Note For information about the deferral of 12.0(7)XE, 12.0(3)XE2, and 12.0(3)XE1, refer to the Field Notice at:
http://www.cisco.com/warp/customer/770/fn11211.shtml
 | Caution
Use these Release Notes if you are running Catalyst software on the supervisor engine and Cisco IOS Release 12.1(1)EX on the MSFC and you have a FlexWAN module installed. These Release Notes do not apply to the Cisco IOS on the Catalyst 6000 Family Release 12.0 XE Supervisor Software product, which runs Cisco IOS Release 12.0 XE on both the supervisor engine and the MSFC (refer to the Release Notes for Catalyst 6000 Family for Cisco IOS Release 12.0 XE publication). |
Note See the online version of these release notes for the most current information about Release 12.1(1)EX.
These release notes describe the features, modifications, and caveats for Release 12.1(1)EX on the Catalyst 6000 family Multilayer Switch Feature Card (MSFC). These release notes are applicable to Release 12.1(1)EX. For features, modifications, and caveats for the Catalyst 6000 family supervisor engine software, refer to the Release Notes for Catalyst 6000 Family Software Release 5.x document.
Note The MSFC ships with Cisco IOS software installed. Ensure that the Catalyst 6000 family supervisor engine is running supervisor engine software release 5.4(1) or later. Software images are also available through Cisco Connection Online (CCO); see the "Cisco Connection Online" section for details.
This document consists of these sections:
Cisco IOS Release 12.1(1)EX supports the Catalyst 6000 family MSFC router daughtercard and FlexWAN module. Release 12.1(1)EX is based on Release 12.1(1)E, but it is available before Release 12.1(1)E is available.
Release 12.1(1)EX will be obsoleted after it is merged into Release 12.1(1)E, which will eventually be merged into 12.1 T. All maintenance updates will be placed into Release 12.1 E and future Release 12.1 E maintenance releases. No maintenance updates will be placed into Release 12.1(1)EX.
For more information about the Cisco IOS software release process, see the Cisco IOS Software Releases: Product Bulletin #537 located on the Documentation CD-ROM and on CCO:
http://www.cisco.com/warp/public/cc/cisco/mkt/ios/rel/prodlit/537_pp.htm
These release notes do not describe features that are available in Release 12.1, Release 12.1 T, or other Release 12.1 Early Deployment (ED) releases.
For information about features in Release 12.1, see the Cross-Platform Release Notes for Cisco IOS Release 12.1 on CCO and the Documentation CD-ROM, when available.
For a list of the software caveats that apply to Release 12.1(1)EX, see the "Open and Resolved Caveats in Release 12.1(1)EX" section.
The following MSFC default memory configurations are acceptable for all MSFC images:
- 64-MB synchronous dynamic random-access memory (SDRAM) DIMM
- 16-MB Flash SIMM
Note While 64 MB is the minimum acceptable DRAM configuration, 128MB of DRAM is recommended for most applications.
Table 1 lists the images available for the MSFC and their order numbers:
Table 1: Software Ordering Information
| Filename
| Description
| Orderable Product Number (Flash on System)
| Orderable Product Number (Spare UpgradeFloppy Media)
|
c6msfc-boot-mz.121-1.EX.bin
| Boot loader (available, but not required to support the FlexWAN module)
| N/A
| N/A
|
c6msfc-jsv-mz.121-1.EX.bin
| Catalyst 6000 Family MSFC Enterprise with FlexWAN module support
| SC6MSFCAV-12101EX
| SC6MSFCAV-12101EX=
|
c6msfc-dsv-mz.121-1.EX.bin
| Catalyst 6000 Family MSFC Desktop with FlexWAN module support
| SC6MSFCBV-12101EX
| SC6MSFCBV-12101EX=
|
c6msfc-isv-mz.121-1.EX.bin
| Catalyst 6000 Family MSFC IP with FlexWAN module support
| SC6MSFCCV-12101EX
| SC6MSFCCV-12101EX=
|
c6msfc-dsv-mz.121-1.EX.bin
| Catalyst 6000 Family MSFC IP/IPX with FlexWAN module support
| SC6MSFCDV-12101EX
| SC6MSFCDV-12101EX=
|
The orderable software images contain the following feature sets:
- The jsv, isv, and dsv images support the FlexWAN module.
- The IP feature set includes support for wire speed Layer 2 switching (bridging) and Layer 3 switching (routing). IP routing protocols supported include RIPv1, RIPv2, OSFP, IGRP, EIGRP, EGP, and BGP4.
Note EGP, BGP4 and IS-IS routing protocols require the additional purchase of the InterDomain Routing Feature License (FR-IRC6).
- The IP/IPX feature set adds support for wire speed IPX Layer 3 switching.
- The Desktop feature set adds support for AppleTalk Phase 1/2, DECnet Phase IV, and IS-IS routing.
- The Enterprise feature set adds support for DECnet Phase V and CLNS/OSI routing.
Note See the online version of these release notes for the most current information about Release 12.1(1)EX.
- With IOS Release 12.1(1)EX, the FlexWAN module supports these port adapters:
- Packet over Sonet (OC-3):
PA-POS-OC3MM
PA-POS-OC3SMI
PA-POS-OC3SML
- ATM (with traffic shaping):
PA-A3-OC3MM
PA-A3-OC3SMI
PA-A3-T3
PA-A3-OC3SML
PA-A3-E3
- T3/E3 (clear-channel and channelized):
PA-T3
PA-T3+
PA-2T3
PA-2T3+
PA-E3
PA-2E3
PA-MC-T3
PA-MC-E3
- T1/E1:
PA-4T+
PA-8T-V35
PA-8T-X21
PA-8T-232
PA-MC-8T1
PA-MC-8E1/120
- HSSI:
PA-H
PA-2H
Note Also see the "FlexWAN Module Usage Guidelines and Restrictions" section.
This section provides usage guidelines and restrictions:
- Integrated Routing and Bridging (IRB) and Concurrent Routing and Bridging (CRB) have deliberately been disabled on the Catalyst 6000 family switches. Routable Layer 2 VLANs and VLAN interfaces should be used for normal bridging and inter-VLAN routing. Bridge groups are supported only to bridge non-routable protocols.
- If the Catalyst 6000 family switch is being used to switch thousands of IPX flows which may all arrive in simultaneous bursts, we recommend that you configure the following to avoid excessive CPU load:
Router(config)# ipx route-cache inactivity-timeout 1 100.
- The above sets the IPX cache inactivity-timeout to 1 minute and the maximum invalidations per minute to 100.
- Before you can use a system image stored on the supervisor engine Flash PC card, you must set the BOOTLDR environment variable. In privileged mode, enter the boot bootldr bootflash: boot_loader_image command.
- Data-link switching plus (DLSw+) was mistakenly identified as not being supported in MSFC IOS release 12.0(3)XE1 and subsequent releases. DLSw+ is supported in 12.0(3)XE1 and subsequent releases.
- Cisco IOS Release 12.0(3)XE1 and subsequent releases support:
- The Web Cache Control Protocol (WCCP) feature, versions 1 and 2
- In addition to the Layer 3 routing protocols listed in the Catalyst 6000 Family MSFC(12.0) & PFC Configuration Guide: Apollo, AppleTalk Routing, DECnet, VINES, and XNS
- At power up or manual reset you must configure the MSFC to boot from its bootflash (or the supervisor engine's Flash PC card; however, bootflash is preferred). When you reset the supervisor engine through either a power up or a manual reset, the MSFC cannot boot from a TFTP server on the network. However, when the supervisor engine is up and the port over which the network is being accessed is in forwarding state, you can boot the MSFC from a TFTP server on the network.
- In a redundant supervisor engine setup, if a specific VLAN interface on one MSFC is shut down, you should manually shut down the corresponding VLAN interface on the other MSFC.
- By default, the MSFC sends Internet Control Message Protocol (ICMP) unreachables when a packet is denied by an access group; these access-group-denied packets are not dropped in hardware but are bridged to the MSFC so it can generate the ICMP-unreachable message. To drop access-group-denied packets in hardware, you must disable ICMP unreachables using the no ip unreachables interface configuration command. Note that the ip unreachables command is enabled by default.
- You can specify the MSFC as the MLS route processor (MLS-RP) for Catalyst 5000 family switches using MLS. Refer to the Layer 3 Switching Configuration GuideCatalyst 5000 Family, 4000 Family, 2926G Series, 2926 Series, 2948G for MLS configuration procedures.
- If one MSFC fails in a system with redundant MSFCs, second hop routers could continue to send traffic to the failed MSFC for a period of time until the second hop router realizes that the MSFC is down.
- HSRP addresses only first hop redundancy; it ensures that the default gateway configured on the clients (workstations) remains up even if one router from the HSRP group goes down.
- HSRP ensures that traffic going from the client through the default gateway to the ultimate destination is supported with the loss of one MSFC.
- The HSRP MAC and IP addresses are never known to the other routers, which means that the reverse traffic from the destination to the originating client may or may not go through the same router. This is especially true if the source and destination are more than one hop away. The second hop router (from the client) will see that the client is reachable through both the MSFCs and through load balancing, could spread the reverse traffic between the two MSFCs.
- When one MSFC fails, the HSRP detects it fairly fast (10 seconds based on default HSRP settings), which means that traffic from the client to its destination goes through. However, the second hop router has to rely on the routing protocol's (RIP/OSPF) convergence time (from 30 to 90 seconds) to realize that one MSFC is down and will try to send the reverse traffic to the failed MSFC.
- In summary, the reverse traffic flow can happen through either MSFC if the source and destination are more than one hop away.
- NetFlow Data Export (NDE) version 7 is not supported for the MSFC.
- When using the Network Address Translation (NAT) router feature on the MSFC, packets traversing the NAT outside interface might, under certain configurations, be software routed instead of being shortcut, regardless of whether they should or should not be translated. Ideally, for packets traversing the NAT outside interface, you would want only those packets requiring NAT to be software routed. IOS in software will only translate traffic that is traversing from NAT inside to NAT outside interfaces and vice versa.
- By making the ACL used for NAT more specific it is possible to limit the software handled packets to only those requiring NAT translation.
- For example, if you use a general ACL (such as permit ip any any) to specify the traffic that requires NAT, then all traffic inbound or outbound on the NAT outside interface will be software routed (including traffic not originating or destined to NAT inside interfaces). If it is possible to use a more specific ACL (such as permit ip 10.1.1.0 0.0.0.255 any), then only the NAT outside traffic matching that ACL will be software routed. This traffic will still be software routed regardless of whether it is originating or destined to NAT inside interfaces. However, by making the ACL more specific, you can limit the amount of traffic that is software routed due to the NAT ACL.
- ACL configuration guidelines: When configuring ACLs on an interface with the configuration command tcam priority {high | low | normal}, entering high Ternary Content Addressable Memory (TCAM) priority gives ACLs on that interface priority for getting into the TCAM over ACLs of interfaces with lower (low or normal) priority.
- If the ACLs on an interface with high priority do not fit in the TCAM, the ACLs for interfaces of lower priority will not be inserted into the TCAM until it is possible to fit the high priority ACLs into the TCAM.
- You can configure VLAN access control lists (VACLs) on the switch to apply to all packets that are routed into or out of a VLAN, or are bridged within a VLAN. VACLs are strictly for security packet filtering and redirecting traffic to specific physical switch ports. Unlike IOS ACLs, VACLs are not defined by direction (input or output).
- Refer to the Catalyst 6000 Family Multilayer Switch Feature Card and Policy Feature Card Configuration Guide for detailed information.
- MAC address-based IOS ACLs are not supported for packets shortcut in hardware. MAC address-based IOS ACLs will be applied on software-switched packets. MAC address-based access control can be supported in hardware for non IP/IPX packets using VACLs. We recommend that you use VACLs to do MAC-addressed-based ACLs.
- Broadcast-to-multicast translation used in conjunction with the multicast helper command does not work if a flow is hardware switched.
- If TFTP downloads (net boots) are timing out, use the following IOS global configuration command for TFTP booting:
- ip tftp boot-interface tftp_interface
- where tftp_interface is the interface the TFTP boot server is on.
- If you enable multicast routing globally, then you should also enable multicast routing (using the ip pim command) on all Layer3 interfaces on which you anticipate receiving IP multicast traffic. This causes the packets to be sent to the process switching level for creating the route entry. However, if you disable multicast routing on the RPF interface, the entry cannot be created and the packet is dropped. Exceeding the source-traffic rate that can be handled by the process level can have an undesirable impact on the system. For instance, HSRP timers can expire on a standby router and cause HSRP flapping.
- Delivery acknowledgment timeouts might occur:
SCP-4-DACK_TIMEOUT_MSG:SCP delivery ack timeout for opcode=118
- When a delivery acknowledgment timeout occurs for opcode 118 (i.e multicast MLS SCP messages), then the impact depends on whether MMLS is in IDLE or ACTIVE state (can be determined by entering the show mls ip multicast statistics command). If MMLS is ACTIVE, the message is only a warning and can be ignored. If MMLS is IDLE, this message displays:
Multicast MLS is disabled due to internal messaging error
- The feature is disabled on the MSFC. You must disable and reenable the IGMP feature on the NMP before reenabling MMLS on the MSFC.
- After enabling PIM on an interface, you need to enter the ip mroute-cache command on the interface to enable multicast fast-switching. If you have "no ip mroute-cache" configured, multicast packets that are not hardware switched will go to process level which increases the load on the router. Software fast-switching is useful for flows that can only be partially hardware switched.
Note See the online version of these release notes for the most current information about Release 12.1(1)EX.
- FlexWAN module support for switches with redundant supervisor engines will be in a future software release. The FlexWAN module does not support switches with redundant supervisor engines with Release 12.1(1)EX.
- FlexWAN module support for IPX MLS will be in a future software release. The FlexWAN module does not support IPX MLS with Release 12.1(1)EX.
This section describes open and resolved caveats in Release 12.1(1)EX.
This section describes open caveats in Release 12.1(1)EX.
- DLSw Ethernet redundancy is not supported. (CSCdp93599)
- All Layer 3 shortcuts are purged when the MSFC is added to or removed from a list of SPAN sources. This causes established flows to be sent to the routing software for forwarding.
- To honor the change in the SPAN configuration, the router software needs to flush the software cache entries on every interface. As a side effect, the Layer 3 table gets purged for each outgoing VLAN. This should only happen when the SPAN configuration changes and the MSFC gets added to or removed from a SPAN session in the ingress direction.
- Workaround: Use care when you choose to configure the MSFC as a SPAN source; we recommend that you do so during low traffic. (CSCdm83559)
- Entering the no ip routing command does not generate a purge request.
- The MSFC does not send a global purge request to the supervisor engine NMP the first time you enter the no ip routing command on the MSFC after a reload. IP traffic continues to be switched by the NMP even after the MSFC is configured with no ip routing.
- Workaround: Issuing the ip routing command followed by the no ip routing command a second time sends a global purge message to the NMP which purges shortcuts on the supervisor engine NMP. (CSCdm91663)
- When MSFCs are configured for multigroup HSRP, the ping success rate is 50 percent when CEF is enabled on the active MSFC. If CEF is disabled, the ping success rate is 100 percent but we do not recommend disabling CEF. This is an intermittent bug. (CSCdm68596)
- When a redundant MSFC comes up, an incorrect inventory message might be received after the Feature Manager is spawned. As a result, an incorrect module ID is used to communicate to the other MSFC. This is an intermittent bug. This problem corrects itself and the message can be ignored. (CSCdp56663)
None.
Note See the online version of these release notes for the most current information about Release 12.1(1)EX.
This section describes open caveats in Release 12.1(1)EX for the FlexWAN module.
- To use the interfaces on the FlexWAN module, IP routing must be enabled on the MSFC. (CSCdp34896)
- FlexWAN module ATM interfaces do not support MMLS. Enter the no mls ip multicast interface command to disable MMLS on FlexWAN module ATM interfaces. (CSCdp53760)
- The FlexWAN module supports MMLS for traffic going to Frame Relay interfaces only when they are configured with a multicast DLCI:
frame-relay multicast-dlci <dlci>
- The FlexWAN modules currently does not support MMLS for traffic going to Frame Relay interfaces when only broadcast DLCIs are configured:
frame-relay map ip <addr1> <dlci1> broadcast
frame-relay map ip <addr2> <dlci2> broadcast
frame-relay map ip <addr3> <dlci3> broadcast
- To ensure proper multicast operation with broadcast DLCIs, configure the following on the Frame Relay interface:
no mls ip multicast
- The FlexWAN module supports MMLS for traffic received from Frame Relay interfaces. (CSCdp53762)
- If the MSFC reloads, a FlexWAN module with multichannel E1 and T1 interfaces might experience an error and reload. To put a FlexWAN module back into service more quickly following MSFC reload, reload the FlexWAN module. (CSCdp64272)
- Do not assign MAC addresses to FlexWAN interfaces. Statically configured MAC addresses on FlexWAN interfaces causes MLS to fail on the MSFC, requiring reload of the MSFC after the static addresses are cleared. (CSCdp82346)
- FlexWAN V.35, 4T+, HSSI, MCT3/E3/T1/E1 interfaces with PPP encapsulation stop passing traffic after a reset or OIR of the FlexWAN module. Issue shutdown and then no shutdown commands to put the interfaces back in service. (CSCdp83150)
If you lose the boot loader image, please refer to the following link for boot loader image recovery procedures:
http://www.cisco.com/warp/customer/473/14.html
The following sections describe the documentation available for the MSFC on Catalyst 6000 family switches. 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 printed manuals or electronic documents.
Use these release notes with these documents:
The following documents are specific to Release 12.1 and are located on CCO and the Documentation CD-ROM:
- Cross-Platform Release Notes for Cisco IOS Release 12.1
- On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/xprn121/index.htm
- On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
- Product bulletins, field notices, and other release-specific documents on CCO at:
Technical Documents
- Caveats for Cisco IOS Release 12.1
- As a supplement to the caveats listed in the "Open and Resolved Caveats in Release 12.1(1)EX" section, see the Caveats for Cisco IOS Release 12.1 document.
- On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats
- On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, go to CCO and press Login. Then go to Software Center: Cisco IOS Software: Cisco Bugtool Navigator II. Another option is to go to http://www.cisco.com/support/bugtools.
- For earlier versions: Release Notes for Catalyst 6000 Family Multilayer Switch Feature Card Cisco IOS Release 12.0 XE
- On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Release Notes: Catalyst 6000 Family Multilayer Switches: Release Notes for Cisco IOS Release 12.0 XE : Release Notes for MSFC IOS Release 12.0
- On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Release Notes: Catalyst 6000 Family Multilayer Switches: Release Notes for Cisco IOS Release 12.0 XE : Release Notes for MSFC IOS Release 12.0
For information on configuring MSFC and PFC features, refer to these publications at
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/index.htm
- Catalyst 6000 Family FlexWAN Module Installation and Configuration Note
- Catalyst 6000 Family Multilayer Switch Feature Card and Policy Feature Card Configuration Guide
- Catalyst 6000 Family Software Configuration Guide and the Catalyst 6000 Family Command Reference publication
- For additional information on Cisco IOS commands, see the Configuration Fundamentals Command Reference publication
Feature modules describe new features supported by Release 12.1(1) and are an update to the Cisco IOS documentation set.
A feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference. As updates, the feature modules are available online on CCO or the documentation CD-ROM. The feature module information is incorporated in the next printing of the Cisco IOS documentation set.
On CCO:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
On the Documentation CD-ROM:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation: New Features in Release 12.1
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents that are shipped with your order in electronic form on the Documentation CD-ROM, unless you specifically ordered the printed versions.
Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, and Cisco IOS software functionality and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. You can use each configuration guide in conjunction with its corresponding command reference.
On CCO and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
On the Documentation CD-ROM:
Cisco Products Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
The following table describes the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form and in printed form ordered.
Note You can find the most current Cisco IOS documentation on CCO and the Documentation CD-ROM. These electronic documents may contain updates and modifications made after the hard-copy documents were printed.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1
| Books
| Chapter Topics
|
Configuration Fundamentals Configuration Guide
Configuration Fundamentals Command Reference
| Configuration Fundamentals Overview Cisco IOS User Interfaces File Management System Management
|
Bridging and IBM Networking Configuration Guide
Bridging and IBM Networking Command Reference
| Transparent Bridging Source-Route Bridging Token Ring Inter-Switch Link Remote Source-Route Bridging DLSw+ STUN and BSTUN LLC2 and SDLC IBM Network Media Translation DSPU and SNA Service Point SNA Frame Relay Access Support APPN Cisco Database Connection NCIA Client/Server Topologies Cisco Mainframe Channel Connection Airline Product Set
|
Dial Solutions Configuration Guide
Dial Solutions Command Reference
| X.25 over ISDN Appletalk Remote Access Asynchronous Callback, DDR, PPP, SLIP Bandwidth Allocation Control Protocol ISDN Basic Rate Service ISDN Caller ID Callback PPP Callback for DDR Channelized E1 & T1 Dial Backup for Dialer Profiles Dial Backup Using Dialer Watch Dial Backup for Serial Lines Peer-to-Peer DDR with Dialer Profiles DialOut Dial-In Terminal Services Dial-on-Demand Routing (DDR) Dial Backup Dial-Out Modem Pooling Large-Scale Dial Solutions Cost-Control Solutions Virtual Private Dialup Networks Dial Business Solutions and Examples
|
Cisco IOS Interface Configuration Guide
Cisco IOS Interface Command Reference
| Interface Configuration Overview LAN Interfaces Logical Interfaces Serial Interfaces
|
Network Protocols Configuration Guide, Part 1
Network Protocols Command Reference, Part 1
| IP Overview IP Addressing and Services IP Routing Protocols
|
Network Protocols Configuration Guide, Part 2
Network Protocols Command Reference, Part 2
| AppleTalk Novell IPX
|
Network Protocols Configuration Guide, Part 3
Network Protocols Command Reference, Part 3
| Network Protocols Overview Apollo Domain Banyan VINES DECnet ISO CLNS XNS
|
Security Configuration Guide
Security Command Reference
| AAA Security Services Security Server Protocols Traffic Filtering and Firewalls IP Security and Encryption Passwords and Privileges Neighbor Router Authentication IP Security Options
|
Cisco IOS Switching Services Configuration Guide
Cisco IOS Switching Services Command Reference
| Switching Services Switching Paths for IP Networks Virtual LAN (VLAN) Switching and Routing
|
Wide-Area Networking Configuration Guide
Wide-Area Networking Command Reference
| Wide-Area Network Overview ATM Frame Relay SMDS X.25 and LAPB
|
Voice, Video, and Home Applications Configuration Guide
Voice, Video, and Home Applications Command Reference
| Voice over IP Voice over Frame Relay Voice over ATM Voice over HDLC Frame Relay-ATM Internetworking Synchronized Clocks Video Support Universal Broadband Features
|
Quality of Service Solutions Configuration Guide
Quality of Service Solutions Command Reference
| Policy-Based Routing QoS Policy Propagation via BGP Committed Access Rate Weighted Fair Queueing Custom Queueing Priority Queueing Weighted Random Early Detection Scheduling Signaling RSVP Packet Drop Frame Relay Traffic Shaping Link Fragmentation RTP Header Compression
|
- Cisco IOS Software Command Summary
- Dial Solutions Quick Configuration Guide
- System Error Messages
- Debug Command Reference
|
|
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
- WWW: www.cisco.com
- Telnet: cco.cisco.com
- Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.
- From North America, call 408 526-8070
- From Europe, call 33 1 64 46 40 82
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
| Language
| E-mail Address
|
English
| tac@cisco.com
|
Hanzi (Chinese)
| chinese-tac@cisco.com
|
Kanji (Japanese)
| japan-tac@cisco.com
|
Hangul (Korean)
| korea-tac@cisco.com
|
Spanish
| tac@cisco.com
|
Thai
| thai-tac@cisco.com
|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTASC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.








Posted: Thu Sep 21 11:59:14 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.