Downloads |
Table Of Contents
Release Notes for Cisco MC3810 for
Cisco IOS Release 12.0(1)XADetermining Your Cisco IOS Software Release
New Features in Cisco IOS Release 12.0(1)XA
Cisco MC3810 - IGX 8400 Interworking
Common Channel Signaling Features
Facility Data Link (FDL) Capability on the Multiflex Trunk Module
Multiflex Trunk Module with integrated BRI interface
Serial Interface Command Change in Release 12.0(1)XA
Using the Cisco MC3810 with the PSTN
Open Caveats - Release 12.0(1)XA
Resolved Caveats - Release 12.0(1)XA
Software Configuration Tips on the Cisco TAC Home Page
Release Notes for Cisco MC3810 for
Cisco IOS Release 12.0(1)XA
November 2, 1998
These release notes describe new features for the Cisco MC3810 multiservice access concentrator that support Cisco IOS Release 12.0(1)XA. Cisco IOS Release 12.0(1)XA is based on Cisco IOS Release 12.0.
Use these release notes in conjunction with the cross-platform Release Notes for Cisco IOS Release 12.0 located on Cisco Connection Online (CCO) and the Documentation CD-ROM.
For a list of software caveats that apply to Release 12.0(1)XA, refer to the "Caveats" section.
Contents
These release notes discuss the following topics:
System Requirements
This section describes the system requirements for Release 12.0(1)XA and includes the following sections:
•
Determining Your Cisco IOS Software Release
Memory Requirements
lists the software product numbers and minimum memory requirements for the Cisco MC3810 multiservice access concentrator using Cisco IOS Release 12.0(1)XA.
Table 1
Memory Requirements
Hardware Supported
Cisco IOS Release 12.0(1)XA supports the following platform:
•
Determining Your Cisco IOS Software Release
To determine the version of Cisco IOS software currently running on the Cisco MC3810 multiservice access concentrator, log into the platform and use the show version EXEC command. The following is sample output from the show version command. The version number is indicated on the second line as shown below:
Cisco Internetwork Operating System Software IOS (tm) MC3810 Software (mc3810-js-mz), Version 12.0(1), RELEASE SOFTWAREAdditional command output lines include more information such as processor revision numbers, memory amounts, hardware IDs, and partition information.
Feature Set Table
To determine what features are available with each feature set, see . The table summarizes what features you can use when running a specific feature set on the Cisco MC3810 for Cisco IOS Release 12.0(1)XA. The feature set tables use the following terms to identify features:
•
•
Note
Table 2 Feature Sets Supported by the Cisco MC3810
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
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
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
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
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
No
No
No
No
No
Yes
No
Yes
Yes
No
Yes
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Stubby-Areas (NSSA)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
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
No
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
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
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
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
Yes
No
Yes
No
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
Yes
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
No
Yes
No
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
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
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
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
No
No
No
No
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
1 When the older motherboard (SCB 6.06) is used with this feature, serial port 1 cannot be used. When the new motherboard (SCB 6.07) is used, serial port 1 can be used, clocked at speeds up to 192 kbps.
2 Voice signaling on CES is not available.
3 ATM PVCs only. SVCs are not supported.
4 Includes T1 CAS protocols, plus UK Standard CAS (Mercury protocol) and CEPT standard E&M.
5 Applicable to data-only interfaces.
6 Applicable to data-only interfaces.
Cisco IOS File System
To make file management easier, the Cisco MC3810 provides a complete file system for software images, message files and reports. The standard Flash memory size is 8 MB, and a 16-MB upgrade option is available. The 16-MB version can hold two code images simultaneously for fail-safe upgrades.
Network Management
Management and configuration of the Cisco MC3810 should be familiar to the Cisco IOS user and compatible with existing management systems. As such, it provides a superset of the Cisco command-line interface (CLI). The Cisco MC3810 can be managed by standard Cisco management platforms and facilities. The Cisco MC3810 can be managed by CiscoView in addition to the native remote login facilities provided by Telnet and rlogin. Three types of configuration interfaces are provided:
•
•
•
The HTTP-based interface allows configuration from any Web browser such as Netscape Navigator or Microsoft Explorer. The SNMP MIB allows management of the Cisco MC3810 from SNMP managers (for example, HP OpenView).
New and Changed Information
The following section lists the new features supported by the Cisco MC3810 in Cisco IOS Release 12.0(1)XA.
New Features in Cisco IOS Release 12.0(1)XA
The following new features are supported on the Cisco MC3810 in Cisco IOS Release 12.0(1)XA:
•
•
•
•
Note
Call Detail Records
The Call Detail Records (CDR) feature provides the ability to track records for calls being processed by the Cisco MC3810. CDR data is collected for all POTS call attempts, and the data is collected for each call leg and also by each Cisco MC3810 involved in the call session.
The call legs for which CDR data is collected for are:
•
•
•
CDR data is stored in an internal buffer on the Cisco MC3810 at call termination time, and becomes available to be polled periodically by the Cisco network management system (NMS) applications. The CDR/call history entries cannot be retrieved after a power loss or a software reload on the Cisco MC3810, so the Cisco NMS is considered the final destination for storing and tailoring the CDR call history table into report form.
Cisco MC3810 - IGX 8400 Interworking
For locations terminating a greater number of voice channels, the Cisco IGX provides scalability that allows a network design in which connections can be made between remote Cisco MC3810 concentrators.
Cisco MC3810 -IGX 8400 Interworking allows the Cisco IGX 8400 to be used as a larger, central site access device that can do the following:
•
•
•
•
•
•
•
Common Channel Signaling Features
Cisco IOS Release 12.0(1)XA introduces support for three new Common Channel Signaling (CCS) features that are described in the sections below:
QSIG PRI Voice Switching
This release adds support for QSIG, which is an inter-PINX (Private Integrated services Network Exchange) signaling protocol that provides connectivity between PINXs in a corporate environment. Using the ISDN PRI QSIG Voice Signaling feature, the Cisco MC3810 can be used as an access device to allow corporate PINX networks at remote sites to be interconnected via a data network (WAN). The Cisco MC3810 QSIG software allows incoming voice calls from a PINX to be routed across the WAN to a destination PINX. The Cisco MC3810 is responsible for establishing the necessary connection to the peer Cisco MC3810 across the WAN where both signaling and voice packets can be transported on behalf of the PINXs.
The Cisco MC3810 also performs intelligent functions such as call routing to other Cisco MC3810 concentrators in the WAN (for example, tandem switching) and interworking with other types of signaling already supported on the Cisco MC3810. Transport of Supplementary Services transparent through the network is also supported.
CCS Frame Forwarding
This release adds support for CCS frame forwarding, which enables the Cisco MC3810 Digital Voice Module (DVM) to connect two CCS Private Integrated services Network Exchanges (PINXs) without having to interpret CCS signaling information for call processing. This feature provides transparent CCS frame forwarding for PBXs that use proprietary forms of CCS. CCS frame forwarding forwards CCS messages by encapsulating them in either Frame Relay or ATM.
With CCS frame forwarding, the voice connections between PBXs over the network are configured as point-to-point links.Voice Activity Detection (VAD) is used to detect when a call is in progress.
CCS Transparent Signaling
This release adds support for transparent Common Channel Signaling (CCS), which provides point-to-point PINX connection capability to Cisco MC3810 digital voice module (DVM) interfaces when the PINX does not support QSIG, or when the PINX has a proprietary solution.
Default Routes
The default routes feature can be used to reduce the number of dial peers to be configured. It is designed for situations where, for example, the ports on a Cisco MC3810 have extension numbers, but all calls not terminating on those extensions should be sent to a central Cisco MC3810, usually for forwarding to a PBX. Instead of defining all the number blocks that can be called, the default route is a dial peer that automatically matches any call not terminated by other dial peers on the Cisco MC3810.
Facility Data Link (FDL) Capability on the Multiflex Trunk Module
This release adds support for Facility Data Link (FDL) on the Multiflex Trunk module. You can specify the FDL format to use either the ANSI T1.403 standard, or the AT&T TR54016 standard, or both.
G.726 (ADPCM)
This newly supported vocoder provides higher reliability for digit transport in networks with greater hop counts and can be used to support lower speed modems (up to 9.6 kbps).
Multiflex Trunk Module with integrated BRI interface
This module provides all the same functionality as the existing MultiFlex Trunk module but now provides an additional interface for BRI data backup. The BRI module provides an S/T interface only, which can be used for European deployment. An inexpensive NT1 can be used to provide connectivity to ISDN services in the United States.
Multi-length Dial Patterns
Dial strings of multiple lengths can now be supported in the same network and on the same Cisco MC3810.
OPX Ring-through
This feature allows a port on the Cisco MC3810 to act like an "Off-Premise Extension" to the PBX. When the PBX attempts to make a connection to the remote voice port on a Cisco MC3810, OPX Ring-through allows the PBX to reroute the call if there is no answer.
Preference-based Hunt Group
The Multi-chassis hunt group has been enhanced to allow the preference command to be used to select remote dial peers before local dial peers using the priority values. This greatly extends the capability to support on-net to off-net rerouting of calls and alternate call center applications.
Important Notes
This section contains important information about the use of your Cisco IOS Release 12.0 software.
Serial Interface Command Change in Release 12.0(1)XA
In Cisco IOS Release 11.3(1) MA, serial 2 was a valid port number. Beginning with Cisco IOS Release 12.0(1), the interface serial 2 designation on the Cisco MC3810 is no longer valid. Depending on the application, you enter different designations for this interface as follows:
•
•
Deprecated MIBs
Because the older Cisco Management Information Bases (MIBs) do not scale well across Cisco products, they will be replaced in a future release. As an initial step toward this, the OLD-CISCO-* MIBS are being deprecated now. This has no immediate impact on any existing Cisco IOS product or network management system (NMS) application. Application developers need to be aware that the following MIBS are being discontinued and update their applications accordingly. lists the deprecated MIBs.
Using the Cisco MC3810 with the PSTN
This section describes important notes regarding use of the Cisco MC3810 with the Public Switched Telephone Network (PSTN).
Connections to a PSTN
Care should be exercised when connecting switched voice ports on the Cisco MC3810 directly to the PSTN because improper configurations can expose the corporate network to telephone fraud.
Switched Access from the PSTN
The Cisco MC3810 has the capability to connect a user from the PSTN directly to the corporate wide-area telephone network. As a phone switch, the Cisco MC3810 can be configured to switch the user to any location in that network, even remote locations that are connected again to another PSTN. However, the Cisco MC3810 does not provide any mechanism to restrict users from calling after they are connected. Without proper network design, this condition could result in the unauthorized use of the corporate network for making calls at the corporation's expense. To prevent this from occurring, Cisco does not recommend connecting a switched voice interface on the Cisco MC3810 directly to the PSTN. Instead, it should be connected to a PBX that implements a security scheme that prevents unauthorized use.
Non-Switched Calls
The same opportunity for illicit use does not exist for non-switched call types such as pass-through connections (although the possibility for fraud does exist at the direct contact point). Pass-through calls create a path to only a single location specified by the network administrator. For example, a pass-through connection might be used to pass a trunk from a PBX to the PSTN. In this case, the trunk on the PBX will always pass straight through the Cisco MC3810 to the PSTN. As a result, the necessary security is provided by the PBX.
Caveats
This section contains a detailed list of the open and resolved caveats affecting Cisco IOS Release 12.0(1)XA for the Cisco MC3810 only. For information on other caveats that also apply to this release, refer to the "Caveats" section in the Cross-Platform Release Notes for Cisco IOS Release 12.0 document located on CCO and the Documentation CD-ROM. This section contains caveats affecting all maintenance releases.
Note
Open Caveats - Release 12.0(1)XA
This section describes possibly unexpected behavior by Release 12.0(1)XA for the Cisco MC3810. This section describes only severity 1, 2 and 3 caveats.
AppleTalk
•
Slow switching fails in the inbound direction on Ethernet 0 to atm0 for Appletalk pings, where ethernet0 is configured for no appletalk route-cache and atm0 is configured for appletalk route-cache.
ATM
•
When E1 0 is configured for ATM, the bandwidth is set to 1920 Kb but when the command default bandwidth is entered for interface ATM0, the bandwidth is changed to 1544 KB, which is correct for T1 but not for E1.
•
If a PVC is created while ATM0 is shut down and then a no shutdown command is performed on ATM0, the PVC becomes active but does not increment the current VCC count. If the PVC is then deleted, the current VCC count goes to 4294967295 and an SNMP browser query on number-of-VCCs receives a value of -1.
Basic System Services
•
When loading an image from a TFTP server via the copy tftp flash command, if the line quality is bad and the copy encounters timeouts during transfers, the display might not indicate that the load had not transferred all data and the image is corrupt.
•
Fast switching does not work properly on s0 and s0:0 interfaces for the Enterprise protocols: Decnet, CLNS, Vines, XNS, AT2-Phy, AT2-AT1.
•
The state of s0:0 or atm0 interface is not reflected correctly after the interface goes down from a failure at the remote end or from a shutdown command. The CiscoView state indication does reflect UP and DOWN conditions correctly.
•
Use of an invalid interface in a command such as:
connect sw 0 dlci 200 s0:0 conn 150
will be accepted at the command line instead of rejected. This is not a valid combination, however, and will not work.
•
If a clock rate is configured for interface serial 0 and the running configuration is copied to the startup configuration, then the Cisco MC3810 is reloaded. When it comes up the, the clock rate is not applied to interface serial 0.
The workaround is to manually configure the interface again, or the startup configuration must be copied again to the running configuration.
•
Configuring bsc primary on serial1 causes an error message to be displayed:
ATM and Bisync cannot work together because of PQUICC limitation".•
A debug message might be displayed under certain circumstances:
"spi failed CPM init"Normal operation is not affected.
•
The Lex option is listed under help on a config interface command but is not currently supported and causes a syntax error when entered.
IP Routing
•
The valid range for mtu on interface serial1 when configured for clear-channel is different based on the current setting of the MTU. The range shown is 64 to a maximum of (18000 + configured-value - 1500). The actual range is 64 to 18000.
•
When an interface is set for encap clear-channel with an mtu setting, and the interface is then reconfigured to no encap, the previous setting for mtu is retained instead of being set to the default.
ISDN
•
A show isdn status can give incorrect information if the controller is not receiving frames with correct clocking or other configuration. The controller should be configured completely and checked for valid operation before proceeding to configure layer 2 or layer 3 functions.
•
If a serial interface configured for pri-group operation is configured for isdn switch operation before configuring the isdn calling number, an SNMP browser will receive error when querying for the value of the isdn-physical-address.
•
Debug messages are displayed on an ISDN BRI0 interface when the cable is removed. Operation is not affected.
Network Management
•
When an SNMP set to ifLinkUpDownTrapEnable with value "disabled" is received by the system for an analog voice port, the impedance of the voice port is also changed to UNKNOWN.
•
CiscoView will display N/A for an interface that has been configured for E1 then reconfigured to atm0 or vice-versa. The workaround is to advance to the next index to see the new data.
•
When a shutdown followed by a no shutdown is performed on S0 at the remote end, the syslog message LINK-UPDOWN indicating the link has come up is missing, only the LINEPROTO-UPDOWN message is logged.
Since some customers configure their network management stations to only display higher syslog severity messages, no indication of the interface state change might appear since the severity of the LINEPROTO-UPDOWN message is low (for example, severity 5 as opposed to the higher severity 3 of the LINK-UPDOWN message which would likely be displayed if it was generated.)
•
An SNMP browser can receive data for a non-existent controller (T1 1 or E1 1) on Cisco MC3810 concentrators equipped with an AVM when querying the system.
•
An SNMP browser query on FXO signal-type returns fxoLoopStart for voice ports of type EXT-SIGN-SLAVE. A query on FXS signal-type returns fxsLoopStart for voice ports of type EXT-SIGN-MASTER.
After a PRI group is configured, the resulting voice ports are of type FXO-NULL. A query on FXO signal-type returns fxoLoopStart for the voice port.
•
Ciscoview does not display Configuration Status and Configuration History categories and associated data in the configuration device window that appears when the user double-clicks on the representation of the chassis.
•
A shutdown on an interface dialer is invalid from the CLI but is accepted from an SNMP browser.
Voice Ports
•
Voice ports remain configured after the voice-groups are deleted.
Voice Support
•
The num-exp command does not operate correctly in configurations using either PLAR or TIE features on voice ports. Use of number-expansion in these cases might result in a crash due to memory allocation failure.
WAN Services
•
If a trunk interface is configured for ppp, the line protocol will come up but the NCP will not open up. The workaround is to shutdown and then no shutdown the interface.
•
There is a limit of 5 sessions supported for X.25 when tunneling PPP over an X.25 connection.
•
If interface s0:0 is first configured for X25, or any other encapsulation and then the encapsulation is changed to bstun, a message is displayed indicating bstun is not allowed on the interface.
However, the encapsulation is then changed to no encapsulation in show run. Checking show interface s0:0 the correct encapsulation (for example, X25) is indicated. The interface also goes down after this action, and it is necessary to reconfigure the original encapsulation then do a shutdown and no shutdown on s0:0 to get it to come up again.
Resolved Caveats - Release 12.0(1)XA
All the caveats listed in this section are resolved in Release 12.0(1)XA for the Cisco MC3810. This section describes only severity 1, 2 and 3 caveats.
•
When a channel-group is deleted from the T1 0 controller, the associated sub-interface Serial 0:x is also deleted but it is not automatically shutdown. This can cause incorrect behavior of many types, including 100% CPU utilization under apparently light load, system crash and forced crashes and others.
You should always shut down an interface before deleting it from a configuration.
Related Documentation
The following sections describe the documentation available for the Cisco MC3810 multiservice access concentrator. Typically, these documents consist of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules. Feature modules are updates to the Cisco IOS documentation. Documentation is available as printed manuals or electronic documents. Feature modules are available online only.
The most up-to-date documentation can be found on the Web via Cisco Connection Online (CCO) and on the latest Documentation CD-ROM. These electronic documents might contain updates and modifications made after the paper documents were printed. For information on CCO, refer to the "Cisco Connection Online" section. For more information on the CD-ROM, refer to the "Documentation CD-ROM" section
Release-Specific Documents
Use these release notes with the Release Notes for Cisco IOS Release 12.0 located on CCO and the Documentation CD-ROM.
Use these release notes in conjunction with the Caveats for Cisco IOS Release 12.0 that accompanies these release notes, and is also located on CCO and the Documentation CD-ROM.
Feature Modules
Feature modules describe new features supported by Release 12.0, and are an update to the Cisco IOS documentation set. As updates, the feature modules are available online only. The feature module information is included in the next printing of the Cisco IOS documentation set. Each feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference.
To access the feature modules on CCO, follow this path:
Products and Ordering: Cisco Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Cisco IOS 12.0(1) New Features
To access the feature modules on the Documentation CD-ROM, follow this path:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Cisco IOS 12.0(1) New Features
Platform Documents
Platform documentation for the Cisco MC3810 is listed in and in . These documents ship with the Cisco MC3810.
To access platform documents on CCO, follow this path:
Products and Ordering: Cisco Documentation: Access Servers and Access Routers: Multiservice Access Concentrators
To access platform documents on the Documentation CD-ROM, follow this path:
Cisco Product Documentation: Access Servers and Access Routers: Multiservice Access Concentrators
Cisco IOS Documentation
Cisco IOS software documentation is listed in . Software documentation consists of the Cisco IOS configuration guides and command references and also includes several supporting documents. These documents are shipped with the Cisco MC3810 in electronic form on the Documentation CD-ROM, unless you specifically ordered the printed version of the documents.
To access software documents on CCO, follow this path:
Products and Ordering: Cisco Documentation: Cisco IOS SOftware Configuration: Cisco IOS Release 12.0
To access software documentation on the Documentation CD-ROM, follow this path:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0
.
Note
Service and Support
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.
Note
For service and support for a product purchased directly from Cisco, use CCO.
Software Configuration Tips on the Cisco TAC Home Page
For helpful tips on configuring Cisco products, follow this path on CCO:
Software & Support: Technical Tips (button on left margin)
Hot Tips are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From international areas, call 415-596-4408.
The following sections are provided from the Technical Tips page:
•
•
•
•
•
•
Cisco Connection Online
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 access 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
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which 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.
78-5915-01
