|
|
 |
Note You can find the most current Cisco IOS documentation on Cisco.com. These electronic documents may contain updates and modifications made after the hardcopy documents were printed. |
These release notes for the Cisco AS5800 universal access servers describe the enhancements provided in Cisco IOS Release 12.1(5)T. These release notes are updated as needed.
For a list of the software caveats that apply to Cisco IOS Release 12.1(5)T, see Caveats for Cisco IOS Release that accompanies these release notes. The caveats document is updated for every maintenance release and is located on Cisco.com and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release on Cisco.com and the Documentation CD-ROM.
These release notes describe the following topics:
modem Wide Area Network (WAN) aggregation systems that provide digital and analog call termination. They are intended to be used as a service provider dial point-of-presence (POP) or centralized enterprise dial gateway. The Cisco AS5800 consists of a dial shelf and one or two router shelves:
ISDN calls are terminated onboard the trunk card on High-Level Data Link Control (HDLC) controllers. The E1 trunk, T1 trunk, and the CT3 trunk cards include channel service units (CSUs) and have either 12 E1 ports, 12 T1 ports, or 28 T1 ports (within the CT3 trunk) that can operate as Primary Rate Interfaces (PRIs), inter-machine trunks (IMTs), or channelized interfaces in any combination. The specific trunk card limitations are described in Table 2, Part 1.
|
Note The router shelf is only supported for routing data to and from the dial shelf. The router should not be used with multiple port adapter interfaces to route LAN traffic between multiple networks. |
The AC-input power shelf is an optional component of the Cisco AS5800 and is used to convert AC-input power into DC-output power for the DC-powered Cisco 5814 dial shelf. The AC-input power shelf contains two AC-input power supplies.
The AC-input to DC-output connection supplies -48V DC-output power to the dial shelf power entry modules (PEMs). The PEMs receive the -48V and transmit power to the filter module. Power flows through the filter module to the backplane, where it is distributed to the dial shelf controller card(s) and feature cards.
The AC-input power shelf includes two 2,000 W, AC-input power supplies that plug into a common power backplane in the AC-input power shelf. A single AC-input power supply is capable of powering a fully configured Cisco 5814 dial shelf. The second power supply provides full redundancy.
The Cisco AS5800/Voice Gateway enables highly scalable deployment of toll-quality voice and fax services over data networks. Enhanced with Cisco's IOS software and Service Node (SN) capabilities, the Cisco AS5800 supports features such as prepaid and postpaid calling card, 800 call redirect, voice activated dialing, and voice and fax mail.
The Cisco AS5800 is specifically designed to meet the demands of large service providers such as Post, Telephone, and Telegraphs (PTTs), regional bell operating companies (RBOCs), inter-exchange carriers (IXCs), and large Internet telephony service providers (ITSPs). The physical architecture of the Cisco AS5800 product enhances reliability, availability, and serviceability. Critical features to dial POP administrators include minimizing downtime, service costs, and time to deployment.
The Cisco AS5800 supports up to 1344 voice ports in a single system, thus offering the highest concentration of VoIP Digital Signal Processors (DSPs) available in a single voice gateway. The Cisco AS5800 offers breakthrough voice quality, density, and scalability, while continuing to provide the rich set of access, VoIP, and QoS services that are part of Cisco IOS software.
The Cisco AS5800 Voice Feature card is a full featured voice processing card that supports 192 DSP-based voice ports. Voice processing capabilities include Voice Activity Detection (VAD), comfort noise generation, adaptive jitter buffering, programmable 16 and 32 msec echo cancellation, programmable frame size, and Dual Tone Multiple Frequency (DTMF) detection and generation. The Cisco AS5800 Voice Feature card offers industry-leading DSP density and a wide range of VoIP codecs, including G.711, G.729, G.729a, G.723.1, and Group III real-time fax support, on any port at any time.
For more information on the Cisco AS5800, refer to the Cisco AS5800 Universal Access Server Operations, Administration, Maintenance, and Provisioning Guide .
For information on new features and Cisco IOS commands supported by Cisco IOS Release 12.1, see the "New and Changed Information" section and the "Related Documentation" section.
This section describes the system requirements for Cisco IOS Release 12.1 T:
Memory requirements for the Cisco AS5800 are presented in Table 1.
| System Components |
Feature Set |
Image Name | Software Image | Minimum Flash |
Minimum DRAM |
|---|---|---|---|---|---|
| Cisco AS5800 | |||||
| Dial Shelf: Cisco 5814 | |||||
| Cisco AS5800 |
| 1Cisco IOS Release 12.1(5)T may be used with the older RS7206 (NPE-200 based) router shelf as long as the shelf has 128M of DRAM installed. |
Cisco IOS Release 12.1 T supports the Cisco AS5800:
For detailed descriptions of the new hardware features, see the "New and Changed Information" section. Table 2, parts 1 and 2, details the supported interfaces, cards, options, NPE support, and port adapters.
| 172-port modem card requires 32M DRAM.
2144-port modem card requires 64M DRAM. 3High-complexity voice cards (with codecs G.723.1, G.728, or G.729) require greater resources to perform complex coding and decoding that results in Voice-handling capacity reduction. Medium-complexity voice cards (with codecs G.711, G.726, or G.729a) can manage twice the number of Voice channels than high-complexity voice cards can. |
| Router Shelf | Port Adapter | Description |
|---|---|---|
| RS7206 Router Shelf | ||
| RS7206 Router Shelf (continued) | ||
| RS7206VXR Router Shelf | ||
| RS7206VXR Router Shelf (continued) | ||
| Router Shelf | Port Adapter | Description |
|---|---|---|
| RS7206 Router Shelf | ||
| RS7206 Router Shelf (continued) | ||
| RS7206VXR Router Shelf | ||
| RS7206VXR Router Shelf (continued) | ||
To determine the version of Cisco IOS software running on your Cisco AS5800, log in to the Cisco AS5800 and enter the show version EXEC command:
For general information about upgrading to a new software release, refer to Upgrading the Cisco IOS Software Release in Cisco Routers and Modems located at:
http://www.cisco.com/warp/public/130/upgrade_index.shtml
For specific information about upgrading AS5800 IOS software, modem and firmware upgrades, and split dial shelf, refer to the "Provisioning" chapter in the Cisco AS5800 Operations, Administration, Maintenance, and Provisioning Guide (OAM&P) at:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/sw_conf/58_oamp/prov.htm
Microcode software images are bundled with the system software image—with the exception of the Channel Interface Processor (CIP) microcode (all system software images). Bundling eliminates the need to store separate microcode images. When the router starts, the system software unpacks the microcode software bundle and loads the proper software on all the interface processor boards.
You could have received a later version of modem code than the one bundled with the Cisco IOS software. The modem code in Flash memory is mapped to the modems. Unless you fully understand how Cisco IOS software uses modem code, it is important to keep the factory configuration.
The modem code release notes are on Cisco.com and the Documentation CD-ROM.
On Cisco.com at:
Technical Documents: Access Servers and Access Routers: Access Servers: Cisco AS5800: Configuration Documents for Cisco AS5800: Port Firmware
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Access Servers: Cisco AS5800: Configuration Documents for Cisco AS5800: Port Firmware
To obtain the latest Cisco IOS software release compatible with Cisco MICA portware, refer to the Cisco AS5x00 MICA 6-Port and 12-Port Modem Module Portware/Cisco IOS Software Compatibility Matrixes at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/sw_conf/sw_ports/compmat/mca12prt.htm.
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.
 |
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 are likely to require an export license. Customer orders may be denied or subject to delay due to United States government regulations. When applicable, purchaser/user must obtain local import and use authorizations for all encryption strengths. Please contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com. |
Table 3 lists the features and feature sets supported by the Cisco AS5800 in Cisco IOS Release 12.1 T and uses the following conventions:
|
Note This table might not be cumulative or list all the features in each image. You can find the most current Cisco IOS documentation on Cisco.com. These electronic documents may contain updates and modifications made after the hardcopy documents were printed. If you have a Cisco.com login account, you can find image and release information regarding features prior to Cisco IOS Release 12.1 T by using the Feature Navigator tool at: http://www.cisco.com/go/fn . |
| 1The number in the "In" column indicates the Cisco IOS release when the interface was introduced. For example, (4) means an interface was introduced in Cisco IOS Release 12.1(4). If a cell in this column is empty, the interface was included in the initial base release. |
The following sections list the new hardware and software features supported by the Cisco AS5800 for Cisco IOS Release 12.1 T.
There are no new hardware feature in the Cisco AS5800 for Cisco IOS Release 12.1(5)T.
The following new software features are supported by the Cisco AS5800 for Cisco IOS Release 12.1(5)T.
The AutoInstall Using DHCP for LAN Interfaces feature replaces the use of the Bootstrap Protocol (BOOTP) with the use of the Dynamic Host Configuration Protocol (DHCP) for Cisco IOS AutoInstall over LAN interfaces. AutoInstall is a Cisco IOS software feature that provides for the configuration of a new routing device automatically when the device is initialized. DHCP (defined in RFC 2131) is based on the Bootstrap Protocol, which provides the framework for passing configuration information to hosts on a TCP/IP network. DHCP adds the capability of automatic allocation of reusable network addresses and additional configuration options. In Cisco IOS release 12.1(5)T, the IP address procurement phase of the AutoInstall process is now accomplished using DHCP for Ethernet, Token Ring, and FDDI interfaces. Before this release, IP addresses for LAN interfaces were obtained using BOOTP during the AutoInstall process. The AutoInstall Using DHCP for LAN Interfaces feature also allows the routing device to recognize IP address allocation messages coming from regular BOOTP servers, providing a seamless transition for those devices already using BOOTP servers for AutoInstall. Additionally, this feature allows for the uploading of configuration files using unicast Trivial File Transfer Protocol (TFTP).
For further details, please see: http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dt_dhcpa.htm
The following enhancements to dial-on-demand authentication are provided with this feature:
This feature also introduces modifications to the dialer aaa command, which provides username configuration capability for dial-on-demand.
Internet Group Management Protocol (IGMP) is a protocol used by IPv4 systems to report IP multicast group memberships to neighboring multicast routers. On networks with hosts directly attached, IGMP Version 3 (IGMPv3) adds support for "source filtering," which enables a multicast receiver to signal to a router which groups it wants to receive multicast traffic from, and from which source(s) this traffic is expected. Based on this membership information, Cisco IOS software only forwards traffic that is requested by the host (or by other routers via Protocol Independent Multicast [PIM]) to that network. In addition to restricting traffic on the network of the receiver host, IGMPv3 membership information can be propagated to multicast routing protocols to enable the forwarding of traffic from permitted sources or to restrict traffic from denied sources along the entire multicast data delivery path.
In the Source Specific Multicast (SSM) feature, introduced in Cisco IOS Release 12.1(5)T, hosts must explicitly include sources when joining a multicast group (this is known as "channel subscription"). IGMPv3 is the industry-designated standard protocol for hosts to signal channel subscriptions in SSM. In deployment cases where IGMPv3 cannot be used (for example, if it is not supported by the receiver host or its applications), there are two other mechanisms to enable SSM: URL Rendezvous Directory (URD) and IGMP v3lite. Both of these features were introduced with SSM in Cisco IOS Release 12.1(5)T.
IVR Version 2.0 is the fourth release of IVR and TCL scripting on Cisco IOS VoIP gateways. The Cisco IVR feature (first made available in Cisco IOS Release 12.0(3)T and 12.0(7)T) provides IVR capabilities using TCL scripts.
IVR Version 2.0 is made up of several separate components which are described individually in the section that follows. These new features include:
These features add scalability and enable the IVR scripting functionality on VoIP legs. In addition, support for RTSP enables VoIP gateways to play messages from RTSP-compliant announcement servers.
One of the most commonly used identifiers in SNMP-based network management applications is the Interface Index (ifIndex) value. IfIndex is a unique identifying number associated with a physical or logical interface; as far as most software is concerned, the ifIndex is the "name" of the interface. Although there is no requirement in the relevant Requests for Comments (RFC) that the correspondence between particular ifIndex values and their interfaces be maintained across reboots, applications such as device inventory, billing, and fault detection increasingly depend on the maintenance of this correspondence.
Cisco IOS Release 12.1(5)T adds support for an ifIndex value that can persist across reboots, enabling users to avoid the workarounds previously required for consistent interface identification. The Interface Index Persistence feature allows for greater accuracy when collecting and processing network management data by uniquely identifying input and output interfaces for traffic flows and SNMP statistics. Relating each interface to a known entity (such as an ISP customer) enables network management data to be used more effectively. See the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dt5ifidx.htm.
The Interface Range Specification feature allows specification of a range of interfaces to which subsequent commands are applied and supports definition of macros that contain an interface range. The Interface Range Specification feature is implemented with the range keyword, which is used with the interface command. In the interface configuration mode with the range keyword, all entered commands are applied to all interfaces within the range until you exit interface configuration mode.
The Interworking Signaling Enhancements for H.323 VoIP feature enables Voice over IP (VoIP) networks to properly signal the setup and tear-down of calls when interworking with Public Switched Telephone Networks (PSTNs). These enhancements ensure that in-band tones and announcements are generated when needed so that the voice path is cut-through at the appropriate point of call setup and that early alerting (ringing) does not occur. In addition, support for network-side ISDN and the reducing of speech clipping is addressed.
This feature module describes enhancements to improve visibility into the line and modem status for the network access server (NAS).
NAS modem health is supported by the following features:
These features have been developed to monitor the NAS health conditions at the digital signal level zero (DS-0) level, Primary Rate Interface (PRI) bearer channel level, and modem level.
This combined set of features provides the following benefits:
Microsoft NetMeeting is a Windows-based application that enables multiuser interaction and collaboration from a user's PC over the Internet or an intranet. Support for the NetMeeting Directory (ILS) allows connections by name from the directory built into the NetMeeting application. Destination IP addresses do not need to be known in order for a connection to be made.
The Parser Cache feature optimizes the parsing (translation) of Cisco IOS software configuration command lines by remembering how to parse recently encountered command lines. This feature was developed to improve the scalability of the Cisco IOS software command-line interface (CLI) parser when processing large configuration files. This improvement is especially useful for those cases in which thousands of virtual circuits must be configured for interfaces, or hundreds of access control lists (ACLs) are required. The parser chain cache can rapidly recognize and translate configuration lines that differ slightly from previously used configuration lines (for example, pvc 0/100, pvc 0/101, and so on). Testing indicates an improvement to load time of between 30% and 36% for large configuration files when using the parser cache.
The parser cache is enabled by default on all platforms using Cisco IOS 12.1(5)T or later. A new command, [no] parser cache, allows the disabling or reenabling of this feature.
The PIM Dense Mode State Refresh feature keeps the pruned state in PIM dense mode from timing out by periodically forwarding a control message down the source-based distribution tree. The control message refreshes the prune state on the outgoing interfaces of each router in the distribution tree.
The Preauthentication Enhancements for Callback feature allows users to dial into the NAS without being charged. This enables telecommuters, and other remote network users who dial in, to have the charges applied back to the NAS into which they are dialing.
Two Cisco VSAs for preauthentication will be added to Attribute 26 as follows:
cisco-avpair = "preauth:send-name=<string>"
cisco-avpair = "preauth:send-secret=<string>"
This feature supports the use of new RADIUS VSAs. These RADIUS VSAs are configured in the RADIUS preauthentication profiles to specify preauthentication behavior. They may also be used, for instance, to specify whether subsequent authentication should occur and, if so, what authentication method should be used. Enhancements for this feature include:
Support for the Debit Card feature was extended to the Cisco AS5800 Universal Access Server. The Debit Card feature allows service providers to offer calling service with debit accounting. The Debit Card feature and RADIUS-specific enhancements also support Vendor-Specific Attributes (VSA). The Debit Card for Packet Telephony on the Cisco AS5800 works in tandem with the Cisco Interactive Voice Response (IVR) feature. The IVR voice scripts have been modified to use Tool Command Language (TCL) scripts.
The feature components consist of IVR functionality in Cisco IOS software that works in connection with an integrated third-party billing system. This includes the ability to maintain per-user credit balance information through a RADIUS interface to the Cisco IOS software. When these features are implemented, the billing system and IOS software functions enable a carrier to authorize voice calls and to debit individual user accounts in real time at the edges of a voice over IP network, without requiring external service nodes.
The RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements feature enables the user to specify the hostname of the NAS in attribute 66, rather than the IP address. This feature frees the user from having to remember the numerical IP address of the NAS, and may also provide a small measure of security by protecting the numerical IP address of the NAS.
The RADIUS Attribute 8 (Framed-IP-Address) in Access Requests feature makes it possible for a network access server (NAS) to provide the RADIUS server with a hint of the user IP address in advance of user authentication. An application can be run on the RADIUS server to use this hint and build a table (map) of user names and addresses. Using the mapping information, service applications can begin preparing user login information to have available upon successful user authentication.
The RADIUS Tunnel Attribute Extensions feature introduces RADIUS attribute 90 (Tunnel-Client-Auth-ID) and RADIUS attribute 91 (Tunnel-Server-Auth-ID). Both attributes help support the provision of compulsory tunneling in virtual private networks (VPNs) by allowing the user to specify authentication names for the network access server (NAS) and the RADIUS server.
Once a NAS has set up communication with a RADIUS sever, you can enable a tunneling protocol. Some applications of tunneling protocols are voluntary, but others involve compulsory tunneling; that is, a tunnel is created without any action from the user and without allowing the user any choice in the matter. In those cases, new RADIUS attributes are needed to carry the tunneling information from the NAS to the RADIUS server to establish authentication. Attributes 90 and 91 support Layer 2 Forwarding (L2F) and Layer 2 Tunneling Protocol (L2TP).
Attributes 90 and 91 must be included if the RADIUS sever accepts the request and the desired authentication name is different from the default.
Attributes 90 and 91 should be included in an accounting request that contains Acct-Status-Type attributes with values of either start or stop and that pertains to a tunneled session.
The Router-Port Group Management Protocol (RGMP) feature introduces a Cisco protocol that restricts IP multicast traffic in switched networks. RGMP is a Layer 2 protocol that enables a router to communicate to a switch (or a networking device that is functioning as a Layer 2 switch) the multicast group for which the router would like to receive or forward traffic.
The SDLC SNRM Timer and Window Size Enhancements feature introduces a new window size setting for Synchronous Data Link Control (SDLC) configurations, and a new timeout setting for the Set Normal Response (SNRM) frame. These enhancements change the operation of SDLC processing on a multidrop line.
Before this feature, all SDLC addresses on the multidrop had the same window count. Now the window count can be configured on a Physical Unit or SDLC address level. This enhancement gives a controller a different window size than other devices on the interface, and allows devices attached to the multidrop to be sized individually.
Cisco IOS software SDLC implementation currently uses a common response timer (T1) for all outstanding commands. Calculating the maximum frame size and line speed produces a minimum time of 3.5 seconds for receiving acknowledgments; thus, polling stations used for link activation use this 3.5-second timer. This is a problem on a multidrop, because stations that do not respond to the SNRM will have 3.5 seconds of downtime-waiting before the next station that is active is polled. This enhancement reduces the time to stations that are waiting idle, as opposed to those that are active.
The Cisco gateway based Settlement protocol interacts between carriers to create a single authentication at initialization. Two new features, Roaming and Multiple Roots have been added in Cisco IOS Release 12.1(5)T to enhance the OSP. The VoIP/Open Settlement Protocol (OSP) feature offers the ability to authorize, route calls, and billings between two different ISPs via a trusted third party, the settlement clearing house, which is the OSP server. Cisco has built this OSP client on Cisco 2600 series, Cisco 3600 series, Cisco AS5300, and Cisco AS5800 platforms, and partnered with a few companies (TransNexus, GRIC, etc.) that provide OSP servers. The code for this feature is an encrypted image.
The VoIP Call Admission Control Using RSVP feature synchronizes Resource Reservation Protocol (RSVP) procedures with H.323 Version 2 (Fast Connect) setup procedures to guarantee that the required Quality of Service (QoS) for VoIP calls is maintained across the IP network. Before Cisco IOS Release 12.1(3)XI, VoIP gateways used H.323 Version 1 (Slow Connect) procedures when initiating calls requiring bandwidth reservation. This feature, which is enabled by default, allows gateways to use H.323 Version 2 (Fast Connect) for all calls, including those requiring RSVP.
There are no new hardware feature in the Cisco AS5800 for Cisco IOS Release 12.1(3a)T1.
The following new software features are supported by the Cisco AS5800 for Cisco IOS Release 12.1(3a)T1:
Customers are demanding the ability to both monitor and terminate their authenticated client connections via SNMP. Furthermore, customers are requesting that the client data provided be directly related to the accounting information reported by AAA to either Radius or Tacacs. Moreover, additional real-time information such as idle times are also requested for this feature in order to provide the ability to terminate calls with no activity present.
This feature allows Cisco's customers to extend and expand their ability to monitor end users by providing access to some client data objects via SNMP.
The Circuit Interface MIB consists of a single table, with each row being a sequence of two objects: Circuit Interface Description (cciDescr) and Circuit Interface Status (cciStatus). The cciDescr object is used to identify circuits using a textual description of up to 255 characters specified by the user. (Note that MIB objects are modified using network management system (NMS) applications, and can not be configured using the Cisco IOS command-line interface.) When the row is created by a user, a value is set for the cciDescr object. The table is indexed by ifIndex from the IF-MIB. The cciStatus is the RowStatus object for the rows in the table. The cciStatus object can be set to only two values by the user: createAndGo(4), which creates a new row, and destroy(6), which removes an existing row. If the row is created successfully, the cciStatus will be active(1). When creating a new row, the user should set the cciDescr object along with the cciStatus in a single snmp set pdu command. If the row is already active, only the cciDescr object can be modified. The other option is to delete the row first by setting the cciStatus to destroy(6) and then recreate the row with a new value for cciDescr. When creating a new row, the ifIndex is validated first. If the ifIndex value is not valid, the row is not created and an error code is returned. Similarly, if ,when an interface is deleted, there was a corresponding row in this table, that row will be deleted automatically.
After an identifying description is created for an interface by a user, the description (the cciDescr object) will be sent along with the other varbinds as part of linkup and linkdown trap notifications.
For further details, see the CISCO-CIRCUIT-INTERFACE-MIB.my file, available from the Cisco Connection Online MIB site at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
The show caller command combines the output of the existing call-related show commands. This command displays connection status in summary or in detail. The summary field has been added (summary) to display the total number of calls, including the number of ISDN and Analog calls, since the last reload. This summary counter is cumulative of all calls since the NAS has been up, where other counters indicate the current number of calls in the NAS.
Using the show caller command provides the following benefits:
This MIB provides statistics reflecting the state of AAA Server operation within the device and AAA communications with external servers.
The Cisco AAA Server MIB provides the following information:
A server is defined as a logical entity that provides any of the three AAA functions. A TACACS+ server consists of all three functions with a single IP address and single TCP port. A RADIUS server can consist of the authentication/accounting pair with a single IP address but distinct UDP ports, or it may be just one of authentication or accounting.
On the Cisco AS5800 only, to request that the Dial Shelf Controller (DSC) [or Dial Shelf Controllers in a redundant configuration] be reloaded at the same time as a reload on the Router Shelf, use the reload components all command. Formerly, to reload a Cisco AS5800, separate reload commands were needed for both the DSC and the Router Shelf.
This new command allows refusal of a peer's request to remote (Point-to-Point Protocol [PPP]) authenticate using Password Authentication Protocol (PAP).
The Event MIB is an asynchronous notification mechanism standardized for use by network management systems using Simple Network Management Protocol (SNMP). The Event MIB provides the ability to monitor Management Information Base (MIB) objects on a local or remote system using SNMP and initiate simple actions whenever a trigger condition is met. By allowing notifications based on events, the Network Management System (NMS) does not need to constantly poll managed devices to find out if something has changed.
Support of the Event MIB has been added to Cisco IOS software to work with a variety of network management systems and, when combined with the currently integrated Expression MIB support, provides a flexible and efficient way to monitor complex conditions on network devices. By allowing SNMP notifications to take place only when a specified condition occurs, Event MIB support reduces the load on affected devices, significantly improving the scalability of network management solutions.
For documentation, see http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dtevent.htm
This feature improves the current real-time fax over IP (commonly known as fax relay) implementation in Cisco gateways, allowing fax transmissions to work reliably over higher packet loss conditions.
In addition, this feature includes enhanced real-time fax debug capabilities and statistics. These debugs and statistics will give better visibility into the real-time fax operation in the gateway, allowing for improved field diagnostics and troubleshooting.
These improvements include configuration of fax relay ECM (Error Correction Mode) on the VoIP dial peer. ECM provides for error-free page transmission. This mode is available on fax machines that include memory for storage of the page data (usually high-end fax machines).
The Individual SNMP Trap Support feature adds the ability to enable or disable SNMP system management notifications (traps) individually. SNMP traps that can be specified are "authentication", "linkup", "linkdown", and "coldstart". This feature expands the functionality of the snmp-server enable traps snmp command.
For documentation, see http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dtitraps.htm
This set of features provides enhancements to improve visibility into the line and modem status for the network access server (NAS). The combined features in this document have been developed to monitor the NAS health conditions at the DS0 level, PRI bearer channel level, and modem level.
These features are enabled and disabled by enhanced command-line interface and MIBs.
NAS modem health monitoring is supported by the following features:
The Network Side ISDN PRI Signaling, Trunking, and Switching feature enables Cisco IOS software to replicate the public switched network interface to a PBX that is compatible with the National ISDN (NI) switch type and European Telecommunications Standards Institute (ETSI) Net5 switch type. Routers and PBXs are both traditionally CPE devices with respect to the public switched network interfaces. However, for Voice over IP (VoIP) applications, it is desirable to interface access servers to PBXs with the access server representing the public switched network.
Enterprise organizations use the current VoIP features with Cisco products as a method to reduce costs for long distance phone calls within and outside their organizations. However, there are times that a call cannot go over VoIP and the call needs to be placed using the Public Switched Telephone Network (PSTN). The customer then must have two devices connected to a PBX to allow some calls to be placed using VoIP and some calls to be placed over the PSTN. In contrast, this feature allows Cisco access servers to connect directly to user-side CPE devices such as PBXs and allows voice and data calls to be placed without requiring two different devices to be connected to the PBXs.
The ISDN Network Side PRI Signaling, Trunking, and Switching feature allows Cisco ISDN-enabled access servers to switch calls across interfaces as legacy phone switches do today and to mimic the behavior of the legacy phone switches.
The Preauthentication with ISDN PRI and Channel-Associated Signaling feature allows a Cisco network access server (NAS) to determine if an incoming call may be answered on the basis of the called number, the calling number, or the call type. With an ISDN PRI (Primary Rate Interface), or with Channel-Associated Signaling (CAS), information about an incoming call is available to the NAS before the call is answered. The available call information includes the called station ID (DNIS), the calling station ID (CLID), and the bearer capability (call type).
When an incoming call arrives from the public network switch, but before it is answered, this feature enables the NAS to send the DNIS, CLID, and call type to a RADIUS server for authorization. If the server authorizes the call, then the NAS accepts the call. If the server does not authorize the call, then the NAS sends a disconnect message to the public network switch to reject the call. This feature supports the use of attribute 44 by the RADIUS server application, which allows user authentication based on the CLID at the same time.
This feature also supports the use of new RADIUS attributes. These RADIUS attributes are configured in the RADIUS preauthentication profiles to specify preauthentication behavior. They may also be used, for instance, to specify whether subsequent authentication should occur and, if so, what authentication method should be used.
In the event that the RADIUS server application becomes unavailable, this feature allows a guard timer to be set in the NAS. When the timer expires, the NAS uses a configurable parameter to accept or reject the incoming call without the authorization.
This feature provides inbound and outbound performance optimization for America Online (AOL) users of wholesale dialing services.
First introduced in Cisco IOS Release 12.1(1)AA, this feature is designed to provide more efficiency in the data transfers for AOL users who are using a Cisco network access server (the Cisco AS5800) to communicate with a wholesale dial carrier. It permits the Cisco AS5800 platform to support the maximum number of connections provided by two T3 connections (that is, 1344 connections) running the TCP Clear protocol with typical traffic loads.
There are no new hardware features in the Cisco AS5800 for Cisco IOS Release 12.1(2)T.
The following new software features are supported by the Cisco AS5800 for Cisco IOS Release 12.1(2)T.
The AAA Server Group Deadtimer feature allows each authentication, authorization, and accounting (AAA) server to be fully configured in the server group. Thus, it allows you to direct AAA traffic to separate groups of servers that have different operational characteristics.
With the introduction of this feature, deadtime has been added as a new attribute to the server group structure. In addition, a separate timer has been attached to each server host in every server group. Therefore, when a server is found to be unresponsive after numerous retransmissions and time-outs, the server is assumed to be dead. The timers attached to each server host in all server groups are triggered. In essence, the timers are checked and subsequent requests to a server (once it is assumed dead) are directed to alternate timers, if configured. When the network access server receives a reply from the server, it checks and stops all configured timers (if running) for that server in all server groups.
If the timer has expired, only the server to which the timer is attached is assumed to be alive. This becomes the only server that can be tried for later AAA requests using the server groups to which the timer belongs.
The feature allows a Cisco network access server (NAS) to determine if an incoming call may be answered on the basis of the called number, the calling number, or the call type. With an ISDN PRI (Primary Rate Interface), information about an incoming call is available to the NAS before the call is answered. The available call information includes the called station ID (DNIS), the calling station ID (CLID), and the bearer capability (call type).
When an incoming call arrives from the public network switch, but before it is answered, this feature enables the NAS to send the DNIS, CLID, and call type to a RADIUS server for authorization. If the server authorizes the call, then the NAS accepts the call. If the server does not authorize the call, then the NAS sends a disconnect message to the public network switch to reject the call. This feature supports the use of attribute 44 by the RADIUS server application, which allows user authentication based on the CLID at the same time.
This feature also supports the use of new RADIUS attributes. These RADIUS attributes are configured in the RADIUS preauthentication profiles to specify preauthentication behavior. They may also be used, for instance, to specify whether subsequent authentication should occur and, if so, what authentication method should be used.
In the event that the RADIUS server application becomes unavailable, this feature allows a guard timer to be set in the NAS. When the timer expires, the NAS uses a configurable parameter to accept or reject the incoming call without the authorization.
There are no new hardware features in the Cisco AS5800 for Cisco IOS Release 12.1(1)T.
The following new software feature is supported by the Cisco AS5800 for Cisco IOS Release 12.1(1)T.
Cisco H.323 Version 2 Phase 2 upgrades Cisco IOS software by adding several optional features of the H.323 Version 2 specification and facilitates customized extensions to the Cisco Gatekeeper.
The Fast Connect feature allows endpoints to establish media channels without waiting for a separate H.245 connection to be opened. This streamlines the number of messages that are exchanged and the amount of processing that must be done before endpoint connections can be established.
Through H.245 tunneling, H.245 messages are encapsulated within Q.931 messages without using a separate H.245 TCP connection. When tunneling is enabled, one or more H.245 messages can be encapsulated in any Q.931 message. H.245 tunneling is not supported as a standalone feature; initiation of H.245 tunneling procedures can be initiated only by using the dtmf-relay command, and only from an active Fast Connect call. Furthermore, if dtmf-relay is configured on a Version 2 VoIP dial peer and the active call has been established by using Fast Connect, tunneling procedures initiated by the opposite endpoint are accepted and supported.
H.245 tunneling is backward compatible with H.323 Version 1 configurations.
Call Transfer allows an H.323 endpoint to redirect an answered call to another H.323 endpoint. Cisco gateways support H.450.2 Call Transfer as the transferred and transferred-to party. The transferring endpoint must be an H.450-capable terminal; the Cisco gateway cannot act as the transferring endpoint. Gatekeeper-controlled or Gatekeeper-initiated Call Transfer is not supported.
|
Note Certain devices are limited in their support of H.450. The Cisco 1700 and ubr820 platforms do not support Interactive Voice Response (IVR). Therefore, these platforms are not able to act as H.450 Transferring endpoints. |
Call Deflection is a feature under H.450.3 Call Diversion (Call Forwarding) that allows a called H.323 endpoint to redirect the unanswered call to another H.323 endpoint. Cisco gateways support H.450.3 Call Deflection as the originating, deflecting, and deflected-to gateway. The Cisco gateway as the deflecting gateway will support invocation of Call Deflection only by using an incoming PRI QSIG message (a Call Deflection cannot be invoked by using any other trunk type).
Call Deflection is a feature under H.450.3 Call Diversion (Call Forwarding) that allows a called H.323 endpoint to redirect the unanswered call to another H.323 endpoint. Cisco gateways support H.450.3 Call Deflection as the originating, deflecting, and deflected-to gateway. The Cisco gateway as the deflecting gateway will support invocation of Call Deflection only by using an incoming PRI QSIG message (a Call Deflection cannot be invoked by using any other trunk type).
This feature provides the Gatekeeper with a configurable string that identifies the voice port or T1/E1 span from which an incoming call entered the ingress gateway. This is done using a Cisco proprietary, nonstandard field that has been added to the ARQ message sent by the ingress gateway. The string in the ARQ corresponds to the setting of the voice-port description command.
To download MIB modules, go to the Cisco MIB website on Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
The Cisco AS5800 support the following MIBs:
The following section contains important notes about Cisco IOS Release 12.1(5)T that can apply to the Cisco AS5800.
When using the 24th channel on a T1 and multilink with maximum calls set to 2 in the Cisco SS7 Interconnect for Access Servers Solution, calls will not complete with Password Authentication Protocol (PAP) authentication while running Cisco IOS Release 12.1(4)T.
This has been resolved in Cisco IOS Release 12.1(5)T.
The last maintenance release of the 12.1 T release train is 12.1(5)T. The migration path for customers who need bug fixes for the 12.1 T features is the 12.2 mainline release. The 12.2 mainline release has the complete feature content of 12.1 T and will eventually reach general deployment.
The last maintenance release was renamed from 12.1(4)T to 12.1(5)T to synchronize with its parent software base, the 12.1(5) mainline release, and to reflect that 12.1(5)T has all the bug fixes of the 12.1(5) mainline release. The 12.1 T release train is a superset of the 12.1 mainline release; hence any defect fixed in the 12.1 mainline is also fixed in 12.1 T. The set of features for 12.1(4)T is the same as that for 12.1(5)T. There was no change in the feature content of the release. The release was renamed so that the releases would be consistent with the Cisco release process.
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.
For information on caveats in Cisco IOS Release 12.1 T, see Caveats for Cisco IOS Release 12.1T.
All caveats in Cisco IOS Release 12.1 are also in Cisco IOS Release 12.1 T.
For information on caveats in Cisco IOS Release 12.1, see Caveats for Cisco IOS Release 12.1 , which lists severity 1 and 2 caveats and is located on Cisco.com and the Documentation CD-ROM.
The following sections describe the documentation available for the Cisco AS5800. These documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, 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 Cisco IOS Release 12.1 and are located on Cisco.com and the Documentation CD-ROM:
On Cisco.com at:
Technical Documents:Cisco IOS Software: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
See Caveats for Cisco IOS Release 12.1 and Caveats for Cisco IOS Release 12.1 T, which contain caveats applicable to all platforms for all maintenance releases of Cisco IOS Release 12.1 and Cisco IOS Release 12.1 T.
On Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.1: Caveats
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software: Cisco IOS Release 12.1: Caveats
These documents are available for the Cisco AS5800 on Cisco.com and the Documentation CD-ROM:
On Cisco.com at:
Technical Documents: Access Servers and Access Routers: Access Servers: Cisco AS5800
On the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Access Servers: Cisco AS5800
Feature modules describe new features supported by Cisco IOS Release 12.1 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 Cisco.com at:
Technical Documents: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: 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 Cisco.com and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.1: Configuration Guides and Command References
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software: Cisco IOS Release 12.1: Configuration Guides and Command References
Table 4 describes the contents of the Cisco IOS Release 12.1 software documentation set for the AS5800, which is available in electronic form and in printed form if ordered.
|
Note You can find the most current Cisco IOS documentation on Cisco.com and the Documentation CD-ROM. These electronic documents may contain updates and modifications made after the hard-copy documents were printed. |
On Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software: Cisco IOS Release 12.1
The most current Cisco documentation is available on the World Wide Web at http://www.cisco.com. Translated documentation can be accessed at http://www.cisco.com/public/countries_languages.shtml.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Cisco documentation is available in the following ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
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
Cisco.com 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.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, 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 Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
Posted: Thu Jan 16 11:10:40 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.