|
|
December 13, 1999
These release notes for Cisco 800 series support Cisco IOS Release 12.0 T, up to and including Release 12.0(7)T. These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and changes to the microcode or modem code and related documents.
For a list of the software caveats that apply to Release 12.0(7)T, see the Caveats for Cisco I OS Release 12.0 T document that accompanies these release notes. The caveats document is updated for every maintenance release and is located on Cisco Connection Online (CCO) and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.0 on CCO and the Documentation CD-ROM.
![]() |
Note Cisco IOS Release 12.0(5)T and earlier support the Cisco 801-804 only. The Cisco 805 router was introduced in the latest release, Release 12.0(7)T. |
These release notes describe the following topics:
This section describes the system requirements for Release 12.0 T:
| Platforms | Image Name | Software Image | Required Flash Memory | Required DRAM Memory | Runs From |
|---|---|---|---|---|---|
Cisco 801-804 Routers | IP | c800-y6-mw | 8 MB | 4 MB | RAM |
IP Plus | c800-sy6-mw | 8 MB | 4 MB | RAM | |
IP/IPX Plus | c800-nsy6-mw | 8 MB | 4 MB | RAM | |
IP/Firewall | c800-oy6-mw | 8 MB | 4 MB | RAM | |
IP/Firewall Plus | c800-osy6-mw | 8 MB | 4 MB | RAM | |
IP/FW/Plus/IPSEC56 | c800-osy656i-mw | 8 MB | 8 MB | RAM | |
IP/IPX/FW/IPSEC56/Plus | c800-nosy656i-mw | 8 MB | 8 MB | RAM | |
Cisco 805 Router | IP | c805-y6-mw | 4 MB | 8 MB | RAM |
IP Plus | c805-sy6-mw | 4 MB | 8 MB | RAM | |
IP/IPX Plus | c805-nsy6-mw | 4 MB | 8 MB | RAM | |
IP/Firewall | c805-oy6-mw | 4 MB | 8 MB | RAM | |
IP/Firewall Plus | c805-osy6-mw | 4 MB | 4 MB | RAM | |
IP/FW/Plus/IPSEC56 | c805-osy656i-mw | 8 MB | 8 MB | RAM | |
IP/IPX/FW/IPSEC56/Plus | c805-nosy656i-mw | 8 MB | 8 MB | RAM |
Cisco IOS Release 12.0 T supports the Cisco 800 series:
![]() |
Note Cisco IOS Release 12.0(5)T and earlier support the Cisco 801-804 only. The Cisco 805 router was introduced in the latest release, Release 12.0(7)T. |
For detailed descriptions of the new hardware features, see the "New and Changed Information" section.
| Router | Ethernet Ports | ISDN Ports | Serial Ports | Telephone Ports | Console Ports |
|---|---|---|---|---|---|
Cisco 801 | One 10BaseT (RJ-45) | ISDN BRI S/T (RJ-45) | - | - | RJ-45 |
Cisco 802 | One 10BaseT (RJ-45) | ISDN BRI U, integrated Network Termination 1 (NT-1) (RJ-45) | - | - | RJ-45 |
Cisco 803 | Four-port 10BaseT (RJ-45) hub | ISDN BRI S/T (RJ-45) | - | Two (RJ-11) | RJ-45 |
Cisco 804 | Four-port 10BaseT (RJ-45) hub | ISDN BRI U, integrated NT-1 (RJ-45) | - | Two (RJ-11) | RJ-45 |
Cisco 805 | One 10BaseT (RJ-45) | - | One smart serial (RS-232, RS-449, RS-530, RS-530A,X.21 and V.35) | - | RJ-45 |
The Cisco 801-804 routers provide the following key hardware features:
![]() |
Note To add additional Flash memory to the Cisco 801-804, you will remove the existing Flash card and install a the new one. |
The Cisco 805 router connects small professional offices over serial lines to corporate networks and to the Internet, and provides the following key features:
To determine the version of Cisco IOS software running on your Cisco 800 series, log in to the router and enter the show version EXEC command:
router> show version Cisco Internetwork Operating System Software IOS (tm) 800 Software (C800-Y6-MW), Version 12.0(7)T, RELEASE SOFTWARE
For information on upgrading to a new software release, see the product bulletin Cisco IOS Software Release 12.0 T Upgrade Paths and Packaging Simplification (#819: 1/99) on CCO at:
Technical Documents: Product Bulletins: Software
Under Cisco IOS 12.0, click Cisco IOS Software Release 12.0 T Upgrade (#819: 1/99).
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.
Release 12.0 T supports the same feature sets as Release 12.0, but Release 12.0 T can include new features supported by the Cisco 800 series.
| Image Names | Feature Set Matrix Term | Software Image | Platforms | In1 |
|---|---|---|---|---|
IP | Basic2 | c800-y6-mw | Cisco 801-804 |
|
c805-y6-mw | Cisco 805 | (7) | ||
IP Plus | Plus3 | c800-sy6-mw | Cisco 801-804 |
|
c805-sy6-mw | Cisco 805 | (7) | ||
IP/IPX Plus | Plus | c800-nsy6-mw | Cisco 801-804 |
|
c805-nsy6-mw | Cisco 805 | (7) | ||
IP/Firewall | Basic | c800-oy6-mw | Cisco 801-804 |
|
c805-oy6-mw | Cisco 805 | (7) | ||
IP/Firewall Plus | Plus | c800-osy6-mz | Cisco 801-804 | (5) |
c805-osy6-mz | Cisco 805 | (7) | ||
IP/FW/Plus/IPSEC56 | Plus, IPSec 564 | c800-osy656i-mw | Cisco 801-804 | (5) |
c805-osy656i-mw | Cisco 805 | (7) | ||
IP/IPX/FW/IPSEC56/Plus | Plus, IPSec 56 | c800-nosy656i-mw | Cisco 801-804 | (5) |
c805-nosy656i-mw | Cisco 805 | (7) |
![]() |
Caution Cisco IOS images with strong encryption (including, but not limited to 168-bit (3DES) data encryption feature sets) are subject to United States government export controls and have limited distribution. Strong encryption images to be installed outside the United States may require an export license. Customer orders may be denied or subject to delay due to United States government regulations. When applicable, the purchaser or the user must obtain local import and use authorizations for all encryption strengths. Contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com. |
Table 4 and Table 5 list the features and feature sets supported by the Cisco 801-804 routers in Cisco IOS Release 12.0 T, and Table 6 lists the features and feature sets supported by the Cisco 805 router. All three tables use the following conventions:
![]() |
Note These feature set tables only contain a selected list of features. These tables are not cumulative-- nor do they list all the features in each image. |
| Feature Set | ||||||||
|---|---|---|---|---|---|---|---|---|
| Features | In | IP | IP Plus | IP/IPX Plus | IP/FW | IP/FW Plus | IP/FW/Plus/ IPSEC56 (VPN) | IP/IPX/FW/ IPSEC56/ Plus |
| Address Conservation |
|
|
|
|
|
|
|
|
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No |
| Advanced Telephone Features1 |
|
|
|
|
|
|
|
|
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Basic Services |
|
|
|
|
|
|
|
|
|
| No | Yes | Yes | No | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Ease of Use and Deployment |
|
|
|
|
|
|
|
|
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes2. | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes2 | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| LAN |
|
|
|
|
|
|
|
|
|
| No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | Yes | No | No | No | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Management |
|
|
|
|
|
|
|
|
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | Yes | Yes | No | Yes | Yes | Yes |
| Routing |
|
|
|
|
|
|
|
|
|
| No | No | No | No | No | No | No |
|
| No | No | No | No | No | No | No |
|
| No | No | No | No | No | No | No |
|
| No | Yes | Yes | No | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No |
|
| No | Yes | Yes | No | Yes | Yes | Yes |
|
| No | Yes | Yes | No | Yes | Yes | Yes |
|
| No | No | Yes | No | No | No | Yes |
|
| No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Security |
|
|
|
|
|
|
|
|
|
| No | No | No | No | No | No | No |
|
| No | Yes | Yes | No | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No |
|
| No | No | No | No | No | No | No |
|
| No | No | No | No | No | No | No |
|
| No | No | No | No | No | Yes | Yes |
|
| No | No | No | No | No | Yes | Yes |
| (5) | No | No | No | No | No | Yes | Yes |
|
|
|
|
|
|
|
|
|
|
| No | No | No | Yes | Yes | Yes | Yes |
|
| No | No | No | Yes | Yes | Yes | Yes |
|
| No | No | No | Yes | Yes | Yes | Yes |
|
| No | No | No | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | Yes | Yes |
|
| No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Voice Technologies |
|
|
|
|
|
|
|
|
| (5) | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| WAN |
|
|
|
|
|
|
|
|
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No |
|
| No | No | No | No | No | No | No |
| WAN Optimization |
|
|
|
|
|
|
|
|
|
| No | Yes | Yes | No | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | No | No | No | No | No | No |
|
| No | No | Yes | No | No | No | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
|
| No | Yes | Yes | No | Yes | Yes | Yes |
| 1Advanced Telephone Features are available on the Cisco 803 and 804 routers only. These features require supplementary services from a telephone company. 2The X.25 configuration feature requires the use of the Cisco command line interface (CLI). 3Interoperability with Certification Authority servers from VeriSign is not supported for IPSec in Release 12.0(5)T and earlier releases on Cisco 800 series routers. |
The Cisco 800 series routers also support the features listed in Table 5.
| Feature | IP | IP Plus | IP/IPX Plus | IP/FW | IP/FW Plus | IP/FW/Plus/ IPSec | IP/FW/Plus/ IPSec Plus |
|---|---|---|---|---|---|---|---|
Routed Protocol | IP | IP | IP/IPX | IP | IP | IP | IP/IPX |
Routing Protocol | RIP Snapshot | RIP/IP- Snapshot | RIP/IP- Snapshot | RIP/IP- Snapshot | RIP/IP- Snapshot | RIP/IP- Snapshot | RIP/IP- Snapshot |
Tunneling |
| GRE | GRE |
| GRE | GRE | GRE |
X.25 |
| X.25 | X.25 |
| X.25 | X.25 | X.25 |
SNTP (Simple Network Time Protocol) | SNTP | SNTP | SNTP | SNTP | SNTP | SNTP | SNTP |
Multicast |
| IP Multicast Forwarding | IP Multicast Forwarding |
| IP Multicast Forwarding | IP Multicast Forwarding | IP Multicast Forwarding |
Management | SNMP | SNMP/ | SNMP/ | SNMP | SNMP/ | SNMP/ | SNMP/ |
Manual ISDN Calls (see reference for commands) | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Feature Set | |||||||
|---|---|---|---|---|---|---|---|
| Features | IP | IP Plus | IP/IPX Plus | IP/FW | IP/FW Plus | IP/FW/Plus/ IPSEC56 (VPN) | IP/IPX/FW/ IPSEC56/ Plus |
| Address Conservation |
|
|
|
|
|
|
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| No | No | No | No | No | No | No |
| Basic Services |
|
|
|
|
|
|
|
| No | Yes | Yes | No | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Ease of Use and Deployment |
|
|
|
|
|
|
|
| Yes | Yes | Yes2. | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes1 | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| LAN |
|
|
|
|
|
|
|
| No | No | No | No | No | No | No |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| No | No | Yes | No | No | No | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Management |
|
|
|
|
|
|
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| No | Yes | Yes | No | Yes | Yes | Yes |
| Routing |
|
|
|
|
|
|
|
| No | No | No | No | No | No | No |
| No | No | No | No | No | No | No |
| No | No | No | No | No | No | No |
| No | Yes | Yes | No | Yes | Yes | Yes |
| No | No | No | No | No | No | No |
| No | Yes | Yes | No | Yes | Yes | Yes |
| No | Yes | Yes | No | Yes | Yes | Yes |
| No | No | Yes | No | No | No | Yes |
| No | No | No | No | No | No | No |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Security |
|
|
|
|
|
|
|
| No | No | No | No | No | No | No |
| No | Yes | Yes | No | Yes | Yes | Yes |
| No | No | No | No | No | No | No |
| No | No | No | No | No | No | No |
| No | No | No | No | No | No | No |
| No | No | No | No | No | Yes | Yes |
| No | No | No | No | No | Yes | Yes |
| No | No | No | No | No | Yes | Yes |
|
|
|
|
|
|
|
|
| No | No | No | Yes | Yes | Yes | Yes |
| No | No | No | Yes | Yes | Yes | Yes |
| No | No | No | Yes | Yes | Yes | Yes |
| No | No | No | Yes | Yes | Yes | Yes |
| No | No | No | No | No | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| No | No | No | No | No | Yes | Yes |
| No | No | No | No | No | No | No |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| WAN |
|
|
|
|
|
|
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| No | No | No | No | No | No | No |
| No | No | No | No | No | No | No |
| WAN Optimization |
|
|
|
|
|
|
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| No | No | No | No | No | No | No |
| No | No | Yes | No | No | No | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| No | Yes | Yes | No | Yes | Yes | Yes |
| 1The X.25 configuration feature requires the use of the Cisco command line interface (CLI). |
The following sections list the new hardware and software features supported by the Cisco 800 series for Release 12.0 T:
The following new hardware feature is supported by the Cisco 800 series for Release 12.0(7)T and later releases:
Cisco IOS Release 12.0(7)T includes support for the Cisco 805 router, which offers flexibility to small offices requiring secure and manageable Internet, intranet, and corporate LAN access. The Cisco 805 router has a fixed hardware configuration with one 10BaseT Ethernet port and one serial port. The serial port can connect X.21, V.35, RS-232, RS-449, RS-530 and RS-530A DTE and DCE.
The following new software enhancements are supported by the Cisco 800 series for Release 12.0(7)T and later releases:
Cisco 800 series routers now support the Terminal Access Controller Access Control System Plus (TACACS+) protocol through Telnet. TACACS+ is a Cisco proprietary authentication protocol that provides remote access authentication and related network security services, such as event logging. User passwords are administered in a central database rather than in individual routers.
The TACACS+ security application provides the centralized validation of users attempting to gain access to a router or network access server. TACACS+ services are maintained in a database on a TACACS+ daemon that typically runs on a UNIX or Windows NT workstation. The goal of TACACS+ is to provide a methodology for managing multiple network access points from a single management service. You must have access to and must configure a TACACS+ server before the configured TACACS+ features on your network access server are available.
The TACACS+ feature is supported by the authentication, authorization, and accounting (AAA) facility, which is configured at individual routers. However, Cisco 800 series routers do not support the RADIUS or Kerberos protocols. The TACACS+ AAA services are defined as follows:
Authentication--Provides complete control of authentication through login and password dialog, challenge and response, messaging support. The authentication facility provides the ability to conduct an arbitrary dialog with the user (for example, after a login and password are provided, to challenge a user with a number of questions, like home address, mother's maiden name, service type, and social security number. In addition, the TACACS+ authentication service supports sending messages to user screens. For example, a message could notify users that their passwords must be changed because of a company password aging policy.
Authorization--Provides fine-grained control over user capabilities for the duration of the a user session, including but not limited to setting autocommands, access control, session duration, or protocol support. You can also enforce restrictions on what commands a user can execute with the TACACS+ authorization feature.
Accounting--Collects and sends information used for billing, auditing, and reporting to the TACACS+ daemon. Network managers can use the accounting facility to track user activity for a security audit or to provide information for user billing. Accounting records include user identities, start and stop times, executed commands (such as PPP), number of packets, and number of bytes.
For additional information, see and the Cisco 800 Series Routers Software Configuration Guide, Cisco 805 Router Software Configuration Guide, and the security-related configuration guides and command references located on CCO and the Documentation CD-ROM:
The following new software enhancements are supported by the Cisco 800 series in Release 12.0(5)T and later releases.
Cisco IOS Firewall Feature Set is not new to Release 12.0(5)T; however, the Cisco IOS Firewall Feature Set combined with IPSEC is new to this release.
Enhancements to the Cisco IOS Firewall feature set are now available on the Cisco 800 series routers. This feature set is available on the IP Firewall, IP Firewall Plus, IP Firewall Plus IPSec, and IP/IPX Firewall Plus IPSec images only. This feature set provides the following additional capabilities:
The Cisco IOS Firewall Feature Set feature module provides several sample firewall configurations, including the following examples for small-office environments:
If you want to configure a firewall in an IP-network-to-Internet network, you can use the Cisco 800 Fast Step application (recommended for inexperienced network administrators) or the Cisco IOS software command-line interface (CLI) (recommended for more experienced network administrators). You can also configure a firewall by using Cisco ConfigMaker software version 2.3.
With the Cisco 800 Fast Step application, you can configure CBAC only. For information on how to use the Cisco 800 Fast Step application, refer to the application online help.
If you want to configure a firewall in a remote-office-to-corporate-office network, you must use the Cisco IOS CLI. For information on how to configure a firewall using the CLI, refer to the following online documents:
The IPSec network security feature is now available on the Cisco 800 series routers (IP/Firewall/Plus/IPSec56 and IP/IPX/Firewall/IPSec56/Plus images only). This feature supports the 56-bit Data Encryption Standard (DES); it does not support the triple DES. Enabling this feature can impact your router performance.
IPSec is a framework of open standards that provides data confidentiality, data integrity, and data authentication between participating peers, such as two routers. IPSec provides these security services on IP datagrams.
For information on configuring this feature, refer to the Cisco IOS Release 12.0 Security Configuration Guide.
Some switches do not include a called party number when they send a voice call to a Cisco 800 router. These calls are directed to port 1 by default. The feature Called Party Number Port allows the router to direct calls of this type to a specified port. When this feature is combined with the command forward-to-unused-port, the router can direct a second call to the same port as the first call or to another port.
Layer Two Tunneling Protocol (L2TP) is an emerging Internet Engineering Task Force (IETF) standard that combines the best features of two existing tunneling protocols: Cisco's Layer Two Forwarding (L2F) and Microsoft's Point-to-Point Tunneling Protocol (PPTP). L2TP is an extension to the Point-to-Point Protocol (PPP), which is an important component for Access Virtual Private Networks (VPNs). Access VPNs allow mobile users to connect to their corporate intranets or extranets, thus improving flexibility and reducing costs.
Traditional dial-up networking services only supported registered IP address, which limited the types of applications that could be implemented over Virtual Private Networks (VPNs). L2TP supports multiple protocols and unregistered and privately administered IP addresses over the Internet. This allows the existing access infrastructure, such as the Internet, modems, access servers, and ISDN terminal adaptors (TAs), to be used.
L2TP can be initiated wherever PPTP or L2F is currently deployed and can be operated as a client initiated tunnel, such as PPTP, or a network access server (NAS) initiated tunnel, such as L2F.
The following new software enhancements are supported by the Cisco 800 series in Release 12.0(4)T1 and later releases.
The Cisco IOS Firewall feature set is now available on the Cisco 800 series routers. This feature set is available on the IP/Firewall image only; the product code for this image is S8CH-12.0(4)T. This feature set provides the following capabilities:
The Cisco IOS Firewall Feature Set feature module provides several sample firewall configurations, including the following examples for small-office environments:
If you want to configure a firewall in an IP-network-to-Internet network, you can use the Cisco 800 Fast Step application (recommended for inexperienced network administrators) or the Cisco IOS software command-line interface (CLI) (recommended for more experienced network administrators). You can also configure a firewall by using Cisco ConfigMaker software version 2.3.
With the Cisco 800 Fast Step application, you can configure CBAC only. If you want to configure a firewall in a remote-office-to-corporate-office network, you must use the Cisco IOS CLI.
For information on how to use the Cisco 800 Fast Step application, refer to the application online help. For information on how to configure a firewall using the CLI, refer to the Cisco IOS Firewall Feature Set feature module. (See the "Feature Modules" section.)
A new command forward-to-unused-port has been added to the dial peer configuration. The default is no forward-to-unused-port.
Suppose a call to 555-1111 is received and its dial peer is fetched and this points to port 1. The following will determine where the new call will be forwarded:
isdn spid1 40855511110101 5551111 5552222dial-peer v 1 pdestination-pattern 5551111forward-to-unused-portport 1dial-peer v 2 pdestination-pattern 5552222forward-to-unused-portport 1
Outgoing hunt is a new pots feature on the Cisco 800 series. This feature is available for US switch types only. When enabled, the CSM will look for a free SPID to use for out going voice calls. If no calls are in progress then the SPID associated with the dial-peer destination is used. The customer must continue to program dial peers. By default, this feature is off.
Command syntax:
pots outgoing-hunt no pots outgoing-hunt
Cisco IOS Release 12.0(3)T was the first 12.0 T release to support Cisco 800 series routers.
The following new software enhancements, which were introduced in Release 12.0(1)T, are supported by the Cisco 800 series beginning in this release.
The Cisco 800 series routers support the connection of analog telephones, fax machines, and modems. These devices are connected to basic telephone services through the ISDN line. The routers support the following supplementary services, which can be ordered from the telephone service provider:
The ISDN voice priority feature controls the priority of data and voice calls for the devices connected to the router telephone ports. If an ISDN circuit endpoint is busy with a data call or calls, and either a voice call comes in or you attempt to place a voice call, the data call is handled per the voice priority setting.
This feature applies to North America only. The Cisco 800 series routers can detect the ISDN switch that supports the ISDN line and the service profile identifiers (SPIDs) assigned by the telephone service provider. SPIDs identify the ISDN B channels. The SPID format is generally an ISDN telephone number with numbers added to it, for example, 40855522220101. Depending on the switch that supports the ISDN line, the ISDN line could be assigned zero, one, or two SPIDs.
With the introduction of Easy IP Phase 2, Cisco IOS software also supports Intelligent DHCP Relay functionality. A DHCP Relay Agent is any host that forwards DHCP packets between clients and servers. A DHCP Relay Agent enables the client and server to reside on separate subnets. If the Cisco IOS DHCP server cannot satisfy a DHCP request from its own database, it can forward the DHCP request to one or more secondary DHCP servers defined by the network administrator using standard Cisco IOS ip helper-address functionality.
It is now possible to implement access lists based on the time of day. To do so, you create a time range that defines specific times of the day and week. The time range is identified by a name, and then referenced by a function, so that those time restrictions are imposed on the function itself.
Currently, IP and IPX extended access lists are the only functions that can use time ranges. The time range allows the network administrator to define when the permit or deny statements in the access list are in effect. Prior to this feature, access list statements were always in effect once they were applied. Both named or numbered access lists can reference a time range.
Triggered extensions to IP RIP increase efficiency of RIP on point-to-point, serial interfaces.
Routers are used on connection-oriented networks to allow potential connectivity to many remote destinations. Circuits on the WAN are established on demand and are relinquished when the traffic subsides. Depending on the application, the connection between any two sites for user data could be short and relatively infrequent.
There were two problems using RIP to connect to a WAN:
To overcome these limitations, triggered extensions to RIP cause RIP to send information on the WAN only when there has been an update to the routing database. Periodic update packets are suppressed over the interface on which this feature is enabled.
The new Integrated Services Digital Network (ISDN) Management Information Base (MIB) RFC2127 has been designed to provide useful information in accordance with the IETF's new standard for the management of ISDN interfaces. It controls all aspects of ISDN interfaces. RFC2127 provides information on the physical Basic Rate Interfaces (BRIs), control and statistical information for B (bearer) and D (signaling) channels, terminal endpoints, and directory numbers.
The following sections contain important notes about Cisco IOS Release 12.0 that can apply to the Cisco 800 series.
Cisco IOS Release 12.0(6)T has been renamed 12.0(7)T to align this release with the 12.0(7) mainline release. The closed caveats for Release 12.0(7)T are identical to the caveats closed in the 12.0(7) mainline release. There was no change in the feature content of the renamed release--the features in 12.0(6)T are the same as 12.0(7)T. Release 12.0(7)T is the last maintenance release of the 12.0 T release train.
Customers needing closure of caveats for the 12.0 T features should migrate to the 12.1mainline release, which has the complete feature content of Release 12.0 T and will eventually reach General Deployment (GD). Release 12.0 T is a super set of the 12.0 mainline release, so all caveats closed in the 12.0 mainline are also closed in 12.0 T.
To run IPSec successfully, the Cisco 800 series router clock needs to be set accurately. Cisco 800 series router clocks are set and maintained using Simple Network Time Protocol (SNTP). For best results, set up a Network Time Protocol (NTP) server to periodically send time information messages to Cisco 800 series routers. See the SNTP configuration and command reference documentation for configuration instructions. If you do not have an NTP server, you must reset the Cisco 800 series router clock using the clock set command each time you restart the router.
The SNTP configuration documentation is available in the chapter "Monitoring the Router and Network" in the "System Management" volume of the Configuration Fundamentals Configuration Guide in the Cisco IOS documentation set.
The SNTP command reference documentation is available in the chapter "Router and Network Monitoring Commands" in the "System Management Commands" volume of the Configuration Fundamentals Command Reference manual in the Cisco IOS documentation set.
Before attempting to download new images, you must first delete files in your router's Flash memory. Be sure to use the delete command, not erase, to free up space. Entering erase will remove all files, including the configuration.
The images introduced in Release 12.0(4)XM apply to the Cisco 805 router only. They are not supported by the Cisco 801, 802, 803 or 804. For more information about this special release, see the Release Notes for the Cisco 805 Router for Cisco IOS Release 12.0(4)XM on CCO.
The isdn answer1 and isdn answer2 commands determine which called telephone numbers, for example, 555-1111 and 555-2222, a Cisco 800 series router can answer. Using these commands limits a router to using the two dial peers that contain the telephone numbers 555-1111 and 555-2222. (When not using these commands, a router can use up to six dial peers.)
A sample scenario in which the isdn answer1 and isdn answer2 commands are used is when a Cisco 801 or Cisco 803 router is connected with other ISDN devices to an ISDN S-bus.
The following protocols send updates that can cause an ISDN line to be activated excessively thereby increasing your monthly ISDN line cost:
For information on preventing this situation, refer to the Cisco 800 Series Routers Software Configuration Guide. This guide contains information on setting up extended access lists to prevent IP, UDP, IPX, and SNTP updates from activating the ISDN line. For CDP, make certain that you enter the no cdp enable command to disable CDP.
If an illegal console configuration is issued to the router, the console will then fail the POST test during boot and cause the router to hang. There is no way to recover a unit in this state except for pulling the soldered boot flash and re-burning the boot ROM.
This problem has been resolved in TinyROM version 1.0(3), a downloadable ROM upgrade available from CCO. Please contact Cisco to upgrade to this version or later, and prevent this problem from occurring.
Phone Mate answering machine model 9200 failed to recognize the ringing signal sent by AMD R79 ringing SLIC. This was confirmed by testing against Phone Mate model 3750 and newer model 9300.
The Cisco 800 router nonvolatile RAM (NVRAM) has a configuration data storage limitation in Cisco IOS Release 12.0(4)T and earlier releases. This problem was resolved in Release 12.0(5)T. Because of this limitation, you might not be able to save the digital certificate into the NVRAM if a large amount of other configuration data already exists. Cisco recommends that you not power off your router if you were not able to save the digital certificate. If you power off your router without successfully saving the digital certificate, you will need to generate the keys and request a new digital certificate from the Certificate Authority (CA) server after powering on the router again.
When a call comes in, a B channel is activated. If the amount of traffic on the B channel exceeds a threshold, the other B channel is activated. If the amount of traffic falls below the threshold, one of the B channels is deactivated. The B channel that is initially activated when the call comes in is not necessarily B1 nor is the B channel that is deactivated when the traffic level lessens necessarily B2.
Certain versions of Cisco IOS software may fail or hang when they receive invalid User Datagram Protocol (UDP) packets sent to their syslog ports (port 514). At least one commonly used Internet scanning tool generates packets that cause such problems. This fact has been published on public Internet mailing lists, which are widely read both by security professionals and by security crackers. This information should be considered in the public domain.
Attackers can cause Cisco IOS devices to repeatedly fail and reload, resulting in a completely disabled Cisco IOS device that needs to be reconfigured by its administrator. Some Cisco IOS devices have been observed to hang instead of failing when attacked. These devices do not recover until they are manually restarted by reset or power cycling. An administrator must personally visit an attacked, hung device to restart it, even if the attacker is no longer actively sending any traffic. Some devices have failed without providing stack traces; some devices may indicate that they were "restarted by power-on," even when that is not the case.
Assume that any potential attacker is likely to know that existence of this problem and the ways to exploit it. An attacker can use tools available to the public on the Internet and does not need to write any software to exploit the vulnerability. Minimal skill is required and no special equipment is required.
Despite Cisco specifically inviting such reports, Cisco has received no actual reports of malicious exploitation of this problem.
This vulnerability notice was posted on Cisco's World Wide Web site:
http://www.cisco.com/warp/public/770/iossyslog-pub.shtml
This information was also sent to the following e-mail and USENET news recipients:
Vulnerable devices and software versions are specified in Table 7, Affected and Repaired Software Versions. Affected versions include Releases 11.3 AA, 11.3 DB, and all 12.0 versions (including 12.0 mainline, 12.0 S, 12.0 T, and any other regular released version whose number starts with 12.0), up to the repaired releases listed in Table 7. Cisco is correcting the problem in certain special releases and will correct it in future maintenance and interim releases. See Table 7, Affected and Repaired Software Versions for details. Cisco intends to provide fixes for all affected IOS variants.
No particular configuration is needed to make a Cisco IOS device vulnerable. It is possible to filter out attack traffic by using access lists. See the "Workarounds" section for techniques. However, except at Internet firewalls, the appropriate filters are not common in customer configurations. Carefully evaluate your configuration before assuming that any filtering you have protects you against this attack.
The most commonly used or asked-about products are listed below. If you are unsure whether your device is running Cisco IOS software, log in to the device and issue the show version command. Cisco IOS software will identify itself simply as "IOS" or "Internetwork Operating System Software". Other Cisco devices will not have the show version command, or they will identify themselves differently in their output. The most common Cisco devices that run Cisco IOS software include the following:
Affected software versions, which are relatively new, are not necessarily available on every device listed above. If you are not running Cisco IOS software, you are not affected by this problem.
The following Cisco devices are not affected:
This vulnerability has been assigned Cisco bug ID CSCdk77426.
Cisco offers free software updates to correct this vulnerability for all affected customers--regardless of their contract status. However, because this vulnerability information has been disseminated by third parties, Cisco has released this notice before updates are available for all software versions. Table 7 gives Cisco's projected fix dates.
Make sure your hardware has adequate RAM to support the new software before installing it. The amount of RAM is seldom a problem when you upgrade within a major release (say, from 11.2[11]P to 11.2[17]P), but it is often a factor when you upgrade between major releases (say, from 11.2 P to 11.3 T).
Because fixes will be available for all affected releases, this vulnerability will rarely, if ever, require an upgrade to a new major release. Cisco recommends very careful planning for any upgrade between major releases. Make certain no known bugs will prevent the new software from working properly in your environment.
Further upgrade planning assistance is available on Cisco's World Wide Web site at:
If you have service contracts you can obtain new software through your regular update channels (generally through Cisco's World Wide Web site). You can upgrade to any software release, but you must remain within the boundaries of the feature sets you have purchased.
If you do not have service contracts, you can upgrade to obtain only the bug fixes; free upgrades are restricted to the minimum upgrade required to resolve the defects. In general, you will be restricted to upgrading within a single row of Table 7, except when no upgrade within the same row is available in a timely manner. Obtain updates by contacting one of the following Cisco Technical Assistance Centers (TACs):
Give the URL of this notice (http://www.cisco.com/warp/public/770/iossyslog-pub.shtml) as evidence for a free update. Non-contract customers must request free updates through the TAC. Please do not contact either "psirt@cisco.com" or "security-alert@cisco.com" for software updates.
You can work around this vulnerability by preventing any affected Cisco IOS device from receiving or processing UDP datagrams addressed to its port 514. This can be done either by using packet filtering on surrounding devices, or by using input access list filtering on the affected IOS device itself.
If you use an input access list, apply that list to all interfaces to which attackers may be able to send datagrams. Interfaces include not only physical LAN and WAN interfaces but also virtual subinterfaces of those physical interfaces, as well as virtual interfaces and interface templates corresponding to GRE, L2TP, L2F, and other tunneling protocols.
The input access list must block traffic destined for UDP port 514 at any of the Cisco IOS device's own IP addresses, as well as at any broadcast or multicast addresses on which the Cisco IOS device may be listening. Be sure to block both old-style "all-zeros" broadcasts and new-style "all-ones" broadcasts. It is not necessary to block traffic being forwarded to other hosts--only traffic actually addressed to the Cisco IOS device is of interest.
No single input access list works in all configurations. Know the effect of your access list in your specific configuration before activating it.
The following example shows a possible access list for a three-interface router, along with the configuration commands needed to apply the list. The example assumes input filtering is not needed, other than as a workaround for this problem:
! Deny all multicasts, and all unspecified-net broadcasts, to port 514 access-list 101 deny udp any 224.0.0.0 31.255.255.255 eq 514 ! Deny old-style unspecified-net broadcasts access-list 101 deny udp any host 0.0.0.0 eq 514 ! Deny network-specific broadcasts. This example assumes that all of ! the local interfaces are on the class B network 172.16.0.0, subnetted ! everywhere with mask 255.255.255.0. This will differ from network ! to network. Note that we block both new-style and old-style broadcasts. access-list 101 deny udp any 172.16.0.255 0.0.255.0 eq 514 access-list 101 deny udp any 172.16.0.0 0.0.255.0 eq 514 ! Deny packets sent to the addresses of our own network interfaces. access-list 101 deny udp any host 172.16.1.1 eq 514 access-list 101 deny udp any host 172.16.2.1 eq 514 access-list 101 deny udp any host 172.16.3.3 eq 514 ! Permit all other traffic (default would be to deny) access-list 101 permit ip any any ! Apply the access list to the input side of each interface interface ethernet 0 ip address 172.16.1.1 255.255.255.0 ip access-group 101 in interface ethernet 2 ip address 172.16.2.1 255.255.255.0 ip access-group 101 in interface ethernet 3 ip address 172.16.3.3 255.255.255.0 ip access-group 101 in
Listing all possible addresses--especially all possible broadcast addresses--to which attack packets may be sent is complicated. If you do not need to forward any legitimate syslog traffic received on an interface, you can block all syslog traffic arriving on that interface. Remember that blocking will affect traffic routed through the Cisco IOS device as well as traffic destined to the device; if the IOS device is expected to forward syslog packets, you will have to do the detailed filtering. Because input access lists impact system performance, install them with caution--especially on systems running very near their capacity.
Many Cisco software images have been or will be specially reissued to correct this vulnerability. For example, regular released Cisco IOS version 12.0(2) is vulnerable, as are interim versions 12.0(2.1) through 12.0(2.3). The first fixed interim version of Release12.0 mainline software is Release12.0(2.4). However, a special release, 12.0(2a), contains only the fix for this vulnerability and does not include any other bug fixes from later 12.0 interim releases.
If you are running Release 12.0(2) and want to fix this problem without risking possible instability presented by installing the 12.0(2.4) interim release, you can upgrade to Release 12.0(2a). Release 12.0(2a) is a "code branch" from the Release 12.0(2) base, which will merge back into the Release 12.0 mainline at Release 12.0(2.4).
Special releases, like 12.0(2a), are one-time, spot fixes, and they will not be maintained. Thus, the upgrade path from Release 12.0(2a) is to Release 12.0(3).
Table 7 specifies information about affected and repaired software versions.
![]() |
Note All dates within this table are subject to change. |
| Cisco IOS Major Release | Description | Special Fix1 | First Fixed Interim Release2 | Fixed Maintenance Release3 |
|---|---|---|---|---|
| Unaffected Releases | ||||
11.2 and earlier releases--all variants | Unaffected early releases (no syslog server) | Unaffected | Unaffected | Unaffected |
11.3, 11.3 T, 11.3 DA, 11.3 MA, 11.3 NA, 11.3 WA, 11.3(2)XA | 11.3 releases without syslog servers | Unaffected | Unaffected | Unaffected |
| Releases Based on 11.3 | ||||
11.3 AA | 11.3 early deployment for AS58xx | 11.3(7)AA2, 8-JAN-19994 | 11.3(7.2)AA | 11.3(8)AA, 15-FEB-1999 |
11.3 DB | 11.3 for Cisco NRP routing blade in Cisco 6400 xDSL DSLAM |
|
| 11.3(7)DB2, 18-JAN-1999 |
| Releases Based on 12.0 | ||||
12.0 | 12.0 Mainline | 12.0(2a), 8-JAN-1999 | 12.0(2.4) | 12.0(3), 1-FEB-1999 |
12.0 T | 12.0 new technology early deployment | 12.0(2a)T1, 11-JAN-1999 | 12.0(2.4)T | 12.0(3)T, 15-FEB-1999 |
12.0 S | ISP support; 7200, RSP, GSR |
| 12.0(2.3)S, 27-DEC-1998 | 12.0(2)S5, 18-JAN-1999 |
12.0 DB | 12.0 for Cisco 6400 universal access concentrator node switch processor (lab use) |
|
| 12.0(2)DB, 18-JAN-1999 |
12.0(1)W | 12.0 for Catalyst 8500 and LS1010 | 12.0(1)W5(5a) and 12.0(1a)W5(5b) (LS1010 platform only) | 12.0(1)W5(5.15) | 12.0(1)W5(6) (platform support for Catalyst 8540M will be in 12.0(1)W5(7)) |
12.0(0.6)W5 | One-time early deployment for CH-OC-12 module in Catalyst 8500 series switches | Unaffected; one-time release | Unaffected | Unaffected; To upgrade use 12.0(1)W5 releases. |
12.0(1)XA3 | Short-life release; merged to 12/0T at 12.0(2)T | Obsolete | Merged | Upgrade to 12.0(2a)T1 or to 12.0(3)T. |
12.0(1)XB | Short-life release for Cisco 800 series; merged to 12.0 T and 12.0 (3)T | 12.0(1)XB1 | Merged | Upgrade to 12.0(3)T. |
12.0(2)XC | Short-life release for new features in Cisco 2600, Cisco 3600, uBR7200, uBR900 series; merged to 12.0 T at 12.0(3)T | 12.0(2)XC1, 7-JAN-1999 | Merged | Upgrade to 12.0(3)T |
12.0(2)XD | Short-life release for ISDN voice features; merged to 12.0 T at 12.0(3)T | 12.0(2)XD1, 18-JAN-1999 | Merged | Upgrade to 12.0(3)T |
12.0(1)XE | Short-life release | 12.0(2)XE, 18-JAN-1999 | Merged | Upgrade to 12.0(3)T |
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.
This section only contains open and resolved caveats for the current Cisco IOS maintenance release.
All caveats in Release 12.0 T are also in Release 12.0.
For information on caveats in Cisco IOS Release 12.0, see Caveats for Cisco IOS Release 12.0 .
For information on caveats in Cisco IOS Release 12.0 T, see Caveats for Cisco IOS Release 12.0 T, which lists severity 1 and 2 caveats and is located on CCO and the Documentation CD-ROM.
![]() |
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. You can reach Bug Navigator II on CCO at Software Center: Cisco IOS Software: Cisco IOS BugToolkit: Cisco Bug Navigator II, or at http://www.cisco.com/support/bugtools |
This section describes possibly unexpected behavior by Release12.0(7)T, specific to the Cisco 800 series routers. Only severity 1 and 2 caveats are included.
router# show isdn status
Global ISDN Switchtype = basic-ni
ISDN BRI0 interface
dsl 0, interface ISDN Switchtype = basic-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 123, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 124, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI 123, ces = 1, state = 8(established)
spid1 configured, spid1 sent, spid1 NOT valid
TEI 124, ces = 2, state = 8(established)
spid2 configured, spid2 sent, spid2 NOT valid
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
The Free Channel Mask: 0x80000003
Total Allocated ISDN CCBs = 0
The frame-relay tunnel subcommand is not available on the Cisco 1600, 1700, and 800 series platforms. This subcommand is only available in IOS images corresponding to Enterprise feature sets:
router(config-if)# frame-relay route 19 interface ?
Serial Serial
Tunnel Tunnel interfaceIf a Cisco 804 router is running the Cisco IOS Release 12.0(4)T1 IP image and using an electrical phone plugged into a plain old telephone service (POTS) port with the ISDN line provisioned with US Caller ID, the router might have intermittent ringing problems.
This caveat has been resolved in Cisco IOS Release 12.1(3)T.
The following sections describe the documentation available for the Cisco 800 series. 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, except for feature modules, which are available online on CCO and the Documentation CD-ROM.
Use these release notes with these documents:
The following documents are specific to Release 12.0 and are located on CCO and the Documentation CD-ROM:
![]() |
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. You can reach Bug Navigator II on CCO at Software Center: Cisco IOS Software: Cisco IOS BugToolkit: Cisco Bug Navigator II, or at http://www.cisco.com/support/bugtools |
These documents are available for the Cisco 800 series on CCO and the Documentation CD-ROM:
On CCO at:
Technical Documents: Documentation Home Page: Access Servers and Access Routers: Fixed Access Routers: Cisco 801-804 Routers or Cisco 805 Router
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Fixed Access Routers: Cisco 801-804 Routers or Cisco 805 Router
Feature modules describe new features supported by Release 12.0 T and are updates 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 only. Feature module information is incorporated in the next printing of the Cisco IOS documentation set.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.0: New Feature Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: New Feature Documentation
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, Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide 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.0:Configuration Guides and Command References
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Configuration Guides and Command References
Table 8 describes the contents of the Cisco IOS Release 12.0 software documentation set, which is available in electronic form and in printed form upon request.
![]() |
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.0
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0
| Books | Chapter Topics |
|---|---|
| Configuration Fundamentals Overview |
| Transparent Bridging |
| X.25 over ISDN |
| Interface Configuration Overview |
| IP Overview |
| AppleTalk |
| Network Protocols Overview |
| AAA Security Services |
| Switching Services |
| Wide-Area Network Overview |
| Voice over IP |
| Policy-Based Routing |
|
|
![]() |
Note Cisco Management Information Base (MIB) User Quick Reference is no longer published. For the latest list of MIBs supported by Cisco, see Cisco Network Management Toolkit on Cisco Connection Online. From CCO, click on the following path: Service & Support: Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB. |
For service and support for a product purchased from a reseller, contact the reseller, who offers a wide variety of Cisco service and support programs described in "Service and Support" of Cisco Information Packet that shipped with your product.
![]() |
Note If you purchased your product from a reseller, you can access CCO as a guest. CCO is Cisco Systems' primary real-time support channel. Your reseller offers programs that include direct access to CCO services. |
For service and support for a product purchased directly from Cisco, use CCO.
If you have a CCO login account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com/kobayashi/serv_tips.shtml
This URL is subject to change without notice. If it changes, point your Web browser to CCO and click on this path: Products & Technologies: Products: Technical Tips.
The following sections are provided from the Technical Tips page:
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can reach CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
![]() |
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
Cisco documentation and additional literature are available in a CD-ROM package, which package that ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Sun Aug 13 02:01:36 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.