|
|
These release notes describe the features and caveats for Cisco IOS software on the Cisco AccessPath-VS3 Packet Telephony Concentrator. The Cisco AccessPath-VS3 System consists of five shelves:
Table 1 shows the Cisco IOS and Catalyst release versions used for the Cisco AccessPath-VS3 System. For additional information on the software release versions used on the Cisco AccessPath-VS3 System, refer to documents referenced in the "Related Documentation" section. The electronic documentation can be found on Cisco Connection Online on the World Wide Web and on the Documentation CD-ROM.
| Cisco AccessPath-VS3 System Shelf | Cisco IOS Release Version | Feature Image |
|---|---|---|
| 1The Switch Shelf runs Catalyst 5000 series software. |
These release notes discuss the following topics:
Follow these guidelines during the preconfiguration process for the Cisco AccessPath-VS3 Packet Telephony Concentrator. They should be taken into consideration during any subsequent reconfigurations of the AccessPath-VS3 System.
Note The AccessPath-VS3 System has been tested and optimized to work with its preconfigured hardware and software. For optimal performance, maintain the system's configuration in accordance with the following guidelines.
Disable unnecessary protocols on Ethernet interfaces such as:
The Access Server Shelves support the following LAN and WAN interfaces:
The VoIP Access Server Shelves support the following voice cards:
The Router Shelves support the following LAN interfaces:
The Router Shelves support the following WAN interfaces:
The Router Shelves support the following WAN data rates:
There are no new features in Cisco IOS Release 11.3(5)T which affect the System Controller for the Cisco AccessPath-VS3 system. For more information about other features on this platform, use the following path on CCO or the Documentation CD-ROM:
The following new feature is supported by the Cisco 3600 series in Cisco IOS Release 11.3(5)T and later releases.
56-kbps modem firmware (V.90) is available for the Cisco 3600 series beginning in Cisco IOS Release 11.3(5)T. V.90 is the new standard for 56k modem communication, and is an evolution from the older K56Flex and X2 protocols. This firmware update will allow 56K-enabled client modems to archive the maximum connect speeds possible using this new technology. Benefits include faster Web access, faster file download, and improved multimedia support. This firmware version
is 2.5.1.0.
The following new feature is supported by the Cisco 3600 series in Cisco IOS Release 11.3(4)T and later releases.
The following eight Enhanced PRI network modules were added to the Cisco 3600 series:
The Cisco 3600 series team is pleased to announce new enhanced versions of PRI Network Modules, now available with a integrated 10/100BaseTX Etherenet port. These network modules provide greater versatility, allowing for better slot efficiency and increased port densities when utilized in the Cisco 3600 series with Cisco IOS Release 11.3(4)T and later.
These new network modules, when combined with the Digital Modem network modules, provide hybrid ISDN/Analog dial access capabilities for the first time on the Cisco 3620, lowering the entry price for 1 PRI with 24/30 Digital Modems solution.
This network module can also be utilized in a Cisco 3640, allowing support for up to 8 PRI in a 2RU chassis.
The following new features are supported by the Cisco 3600 series in Cisco IOS Release 11.3(3)T and later releases.
The 1-port asynchronous transfer mode (ATM-25) network module provides connectivity to an external asynchronous digital subscriber line (ADSL) modem for Cisco series 3600 routers. This network module provides ATM traffic shaping for use with ADSL uplink speeds and protocol support for permanent virtual circuit (PVC) environments. This network module provides full support for multiprotocol encapsulation over ATM Adaptive Layer 5(RFC 1483), classic IP over ATM encapsulation (RFC 1577), and Cisco Point-to-Point Protocol (PPP) over ATM.
In the online feature description, Figure 1 shows the 1-port ATM-25 network module in a typical ADSL application environment. In this example, the network module and the associated Cisco 3640 router provide ATM connectivity to the ADSL modem and provide traffic shaping and protocol encapsulation for the downstream LAN clients.
The Cisco 3600 series 1-port high-speed serial interface (HSSI) network module provides full-duplex connectivity at Synchronous Optical Network (SONET) OC-1/STS-1 (51.840 Mhz), T3 (44.736 MHz), and E3 (34.368 MHz) rates in conformance with the EIA/TIA-612 and EIA/TIA-613 specifications. The actual rate of the interface depends on the external data service unit (DSU) and the type of service to which it is connected. This 1-port HSSI network module can reach speeds of up to 52 Mbps in unidirectional traffic with 1,548-byte packets and 4,250 packets per second. Asynchronous Transfer Mode (ATM), ATM with Data Exchange Interface (DXI), High-Level Data Link Control (HDLC), Point-to-Point Protocol (PPP), Frame Relay, and Switched Multi-Megabit Data Service (SMDS) WAN services are all fully supported.
The 1-Port HSSI network module provides the following benefits:
The Digital Modem Network Module for the Cisco 3640 is a high-density digital network module containing, 6, 12, 18, 24, or 30 digital (MICA) modems. These modems, along with the T1 (or E1) port module, provide a direct digital connection to an Integrated Services Digital Network (ISDN) Primary Rate Interface (PRI) channel. The T1 CAS feature enables these network modules to support voice call transmission using channelized T1 lines (CT1) with channel associated signaling (CAS).
CAS is a form of signaling used on a T1 line. With CAS, a signaling element is dedicated to each channel in the T1 frame. This type of signaling is sometimes called Robbed Bit Signaling (RBS) because a bit is taken out (or robbed) from the user's data stream to provide signaling information to and from the switch. The T1 CAS feature enables the modems on the Digital Network Modem Module to receive and transmit incoming and outgoing call signaling (such as on-hook and off-hook) through each T1 controller that is configured for a channelized T1 line.
By default, DLSw+ terminates the RIF for Token Ring, terminates the LLC for all media types and forwards only data across a WAN with DLSw+ and TCP/IP headers. The RIF is a field in source-route bridged frames that indicates the SRB path the frame should take when traversing a Token Ring network. In the case of an explorer packet, the RIF is a field of the source-route bridged frame that indicates the SRB path that the SRB explorer has traversed so far. The RIF is limited to seven hop counts by the IBM standards. Because DLSw+ terminates the RIF at the virtual ring, the network's scalability increases because the hop count of the packet starts over, and the packet can traverse seven additional hops. Also, RIF termination simplifies network design because ring numbers no longer have to be unique throughout an entire enterprise.
However, some environments do not function properly if the RIF is terminated. For that reason, DLSw+ now supports the RIF Passthrough feature, in which the entire source-route bridged path appears in the RIF.
The Virtual Private Dialup Network (VPDN) Management Information Base (MIB) feature is intended to support all the tables and objects defined in "Cisco VPDN Management MIB" for the user sessions of the VPDN features. There are a number of commands which provide information and statistics through the Command Line Interface (CLI) but not Simple Network Management Protocol (SNMP); the Cisco VPDN MIB has been created to satisfy the need to provide information and statistics through SNMP.
Remote Authentication Dial-In User Server (RADIUS) is an access server authentication, authorization, and accounting protocol originally developed by Livingston, Inc. Although an Internet Engineering Task Force (IETF) draft standard for RADIUS specifies a method for communicating vendor-proprietary information between the network access server and the RADIUS server, some vendors have extended the RADIUS attribute set in a unique way. In this release, Cisco IOS software introduces support for additional vendor-proprietary RADIUS attributes.
Users who have implemented security solutions using a vendor-proprietary implementation of RADIUS can now integrate Cisco access routers into their networks more easily.
For a complete list of supported IETF and vendor-proprietary RADIUS attributes, refer to the "RADIUS Attributes" appendix in the Cisco IOS Release 11.3 Security Configuration Guide.
The automated double authentication feature enhances the existing double authentication feature.
Previously, with the existing double authentication feature, a second level of user authentication is achieved when the user Telnets to the network access server or router and enters a username and password. Now, with automated double authentication, the user does not have to Telnet anywhere but instead responds to a dialog box that requests a username and password or PIN.
For information about the existing double authentication feature, refer to the "Configuring Authentication" chapter of the Cisco IOS Release 11.3 Security Configuration Guide.
Certificate Authority (CA) interoperability is provided in support of the IP Security (IPSec) standard. CA interoperability permits Cisco IOS devices and CA devices to communicate so that your Cisco IOS device can obtain and use digital certificates from the CA. Although IPSec can be implemented in your network without the use of a CA, using a CA provides manageability and scalability for IPSec.
For background and configuration information for IPSec, see the "IPSec Network Security" feature documentation.
IPSec is a framework of open standards developed by the Internet Engineering Task Force (IETF).
IPSec provides security for transmission of sensitive information over unprotected networks such as the Internet. IPSec acts at the network layer, protecting and authenticating IP packets between participating IPSec devices ("peers") such as Cisco routers.
IPSec provides the following network security services:
With IPSec, data can be transmitted across a public network without fear of observation, modification, or spoofing. This enables applications such as virtual private networks (VPNs), extranets, and remote user access.
IPSec services are similar to those provided by Cisco Encryption Technology, a proprietary security solution introduced in Cisco IOS Software Release 11.2. (The IPSec standard was not yet available at Release 11.2.) However, IPSec provides a more robust security solution, and is standards-based.
ISAKMP/Oakley is a key management protocol which is used in conjunction with the IPSec standard. IPSec is an IP security feature that provides robust authentication and encryption of IP packets.
IPSec can be configured without ISAKMP/Oakley, but ISAKMP/Oakley enhances IPSec by providing additional features, flexibility, and ease of configuration for the IPSec standard.
ISAKMP/Oakley is a hybrid protocol which implements the Oakley key exchange inside the ISAKMP framework.
Microsoft Challenge Handshake Authentication Protocol (MS-CHAP) is the Microsoft version of CHAP. Like the standard version of CHAP, MS-CHAP is used for PPP authentication; in this case, authentication occurs between a PC using Microsoft Windows NT or Microsoft Windows 95 and a Cisco router or access server acting as a network access server (NAS).
MS-CHAP differs from the standard CHAP as follows:
Depending on the security protocols you have implemented, PPP authentication using MS-CHAP can be used with or without Authentication, Authorization, and Accounting (AAA) security services. If you have enabled AAA, PPP authentication using MS-CHAP can be used in conjunction with both TACACS+ and RADIUS.
Two new vendor-specific RADIUS attributes (IETF Attribute 26) were added to enable RADIUS to support MS-CHAP. For a complete list of supported IETF and vendor-proprietary RADIUS attributes, refer to the "RADIUS Attributes" appendix in the Cisco IOS Release 11.3 Security Configuration Guide.
In earlier Cisco IOS releases, only named authentication method lists were supported under Cisco's Authentication, Authorization, and Accounting (AAA) network security services. With Cisco IOS Release 11.3(4)T, AAA has been extended to support both authorization and accounting named method lists. Named method lists for authorization and accounting function the same way as those for authentication. They allow you to define different methods for authorization and accounting and apply those methods on a per-interface or per-line basis.
Always On/Dynamic ISDN (AO/DI) is an on-demand service that optimizes the use of an existing Integrated Services Digital Network (ISDN) signaling channel (D channel) to transport X.25 traffic. The X.25 D channel call is placed from the subscriber to the packet data service provider. Multilink and TCP/IP protocols are encapsulated within the X.25 logical circuit carried by the D channel. The bearer channels (Bchannels) use the Multilink protocol without the standard Q.922 and X.25 encapsulations and invoke additional bandwidth as needed. AODI takes full advantage of existing packet handlers at the central office by using an existing D channel to transport the X.25 traffic. The link associated with the X.25 D channel packet connection is used as the primary link of the Multilink protocol. The Dchannel is a connectionless, packet oriented link between the Customer Premise Equipment (CPE) and the central office. Since the Dchannel is always available, it is possible to in turn offer "always available" services. On-demand functionality is achieved by using the Bchannels to temporarily boost data throughput and are disconnected after use.
Microsoft Point-to-Point Compression (MPPC) is a scheme used to compress Point-to-Point Protocol (PPP) packets between Cisco and Microsoft client devices. The MPPC algorithm is designed to optimize processor and bandwidth utilization in order to support multiple simultaneous connections. The MPPC algorithm uses a Lempel-Ziv (LZ) based algorithm with a continuous history buffer, called a dictionary.
The Multiple ISDN Switch Types feature allows you to configure more than one ISDN switch type per router. You can apply an ISDN switch type on a per interface basis, thus extending the existing global isdn switch-type command to the interface level. This allows Basic Rate Interfaces (BRI) and Primary Rate Interfaces (PRI) to run simultaneously on platforms that support both interface types.
The isdn tei command is also extended to the interface level. Terminal endpoint negotiation (TEI) determines when Layer 2 is activated (power-up or first-call).
National ISDN Switch Types for Basic Rate and Primary Rate Interfaces introduces changes to ISDN switch types for Primary Rate Interfaces (PRI) and Basic Rate Interfaces (BRI) as follows:
Note The command parser will still accept the following switch types: basic-nwnet3, vn2, and basic-net3; however, when viewing the NVRAM configuration using either the show running configuration or write terminal command, the basic-net3 or vn3 switch types are displayed respectively.
Basic Rate Interface (BRI) is an Integrated Systems Digital Network (ISDN) interface, and it consists of two B channels (B1 and B2) and one D channel. The B channels are used to transfer data, voice, and video. The D channel controls the B channels.
ISDN uses the D channel to carry signal information. ISDN can also use the D channel in a BRI to carry X.25 packets. The D channel has a capacity of 16 kbps, and the X.25 over D channel can use up to 9.6 kbps.
You can set the parameters of the X.25-over-D-channel interface without disrupting the original ISDN interface configuration. In a normal ISDN BRI interface, the D and B channels are bundled together and represented as a single interface. The original BRI interface continues to represent the D, B1, and B2 channels.
Because some end-user equipment uses static terminal endpoint identifiers (TEIs) to access this feature, static TEIs are supported. The dialer recognizes the X.25-over-D-channel calls and initiates them on a new interface.
X.25 traffic over the D channel can be used as a primary interface where low-volume, sporadic interactive traffic is the normal mode of operation. Supported traffic includes IPX, AppleTalk, transparent bridging, XNS, DECnet, and IP.
The following new features are supported by the Cisco 3600 series in Cisco IOS Release 11.3(2)T and later releases.
The Digital Modem Network Module for the Cisco 3640 is a high-density digital network module containing 6, 12, 18, 24, or 30 V.34+ (28.8 kbps) digital (MICA) modems. These modems provide a direct digital connection to an Integrated Services Digital Network (ISDN) Primary Rate Interface (PRI) channel. This digital modem network module allows you to support a mix of both digital (ISDN) and POTS analog modem calls over a single digital network interface.
Depending on the modem license you purchase with your Cisco 3640, the modems on the Digital Modem Network Module are either manageable or not manageable by Cisco IOS software commands. Manageable modems support the one out-of-band feature, which is used for gathering modem performance statistics and transmitting attention (AT) commands. If the license you purchase includes this modem management capability, you can use the modem management commands to gather call statistics and upgrade modem firmware for large modem pools.
Dialer Watch is a backup feature that integrates dial backup with routing capabilities. Prior dial backup implementations used the following conditions to trigger backup:
Prior backup implementations might not have supplied optimum performance on some networks, such as those using Frame Relay multipoint subinterfaces or Frame Relay connections that do not support end-to-end LMI.
Dialer Watch provides reliable connectivity without relying solely on defining interesting traffic to trigger outgoing calls at the central router. Dialer Watch uses the convergence times and characteristics of dynamic routing protocols. Integrating backup and routing features enables Dialer Watch to monitor every deleted route. By configuring a set of watched routes that define the primary interface, you are able to monitor and track the status of the primary interface as watched routes are added and deleted. Monitoring the watched routes is done in the following sequence:
1. Whenever a watched route is deleted, Dialer Watch checks to see if there is at least one valid route for any of the watched IP addresses defined.
2. If there is no valid route, the primary line is considered down and unusable.
3. If there is a valid route for at least one of the defined watched IP addresses, and if the route is pointing to an interface other than the backup interface configured for Dialer Watch, the primary link is considered up.
4. In the event that the primary link goes down, Dialer Watch is immediately notified by the routing protocol and the secondary link is brought up.
5. When the secondary link is up, at the expiration of each idle timeout, the primary link is rechecked.
6. If the primary link remains down, the idle timer is indefinitely reset.
7. If the primary link is up, the secondary backup link is disconnected. Additionally, a disable timer can be set to create a delay for the secondary link to disconnect, after the primary link is reestablished.
The MS Callback feature provides client-server callback services for Microsoft Windows 95 and Microsoft Windows NT clients. MS Callback supports the Microsoft Callback Control Protocol (MSCB). MSCB is Microsoft's proprietary protocol that is used by Windows 95 and Windows NT clients. MS Callback supports negotiated PPP Link Control Protocol (LCP) extensions initiated and agreed upon by the Microsoft client. MS Callback is added to existing PPP Callback functionality. Therefore, if you configure your Cisco access server to perform PPP Callback using Cisco IOS Release 11.3(2)T or later, MS Callback is automatically available.
MS Callback supports AAA security models using a local database or AAA server.
MSCB uses LCP callback options with suboption type 6. The Cisco MS Callback feature supports clients with a user-specified callback number and server specified (preconfigured) callback number.
MS Callback does not affect non-Microsoft machines that implement standard PPP LCP extensions as described in RFC 1570. In this scenario, MS Callback is transparent.
Protocol-Independent Multicast (PIM) Version 2 includes the following improvements over PIM Version 1:
PIM Version 1, together with the Auto-RP feature, can perform the same tasks as the PIM Version 2 BSR. However, Auto-RP is a standalone protocol, separate from PIM Version 1, and is Cisco proprietary. PIM Version 2 is a standards track protocol in the Internet Engineering Task Force (IETF).
Cisco's PIM Version 2 implementation allows good interoperability and transition between Version 1 and Version 2. You can upgrade to PIM Version 2 incrementally. PIM Versions 1 and 2 can be configured on different routers within one network. Internally, all routers on a shared media network must run the same PIM version. Therefore, if a PIM Version 2 router detects a PIM Version 1 router, the Version 2 router downgrades itself to Version 1 until all Version 1 routers have been shut down or upgraded.
PIM uses the BSR to discover and announce RP-set information for each group prefix to all the routers in a PIM domain. This is the same function accomplished by Auto-RP, but the BSR is part of the PIM Version 2 specification. The BSR mechanism interoperates with Auto-RP.
To avoid a single point of failure, you can configure several candidate BSRs in a PIM domain. A BSR is elected among the candidate BSRs automatically; they use bootstrap messages to discover which BSR has the highest priority. This router then announces to all PIM routers in the PIM domain that it is the BSR.
Routers that are configured as candidate RPs then unicast to the BSR the group range for which they are responsible. The BSR includes this information in its bootstrap messages and disseminates it to all PIM routers in the domain. Based on this information, all routers will be able to map multicast groups to specific RPs. As long as a router is receiving the bootstrap message, it has a current RP map.
DRP Server Agent Enhancements—The DRP Server Agent is a Director Response Protocol (DRP) server application based on UDP for use only with Distributed Director. The DRP Server Agent will provide the following additional functionality:
There were no new features supported by the Cisco 3600 series routers in this release.
The following new features are supported by the Cisco 3600 series routers in Cisco IOS Release 11.3(6)NA2.
The Gatekeeper can manage a zone and provide bandwidth management and address registration services to gateways that are present in the network. The Gatekeeper manages H.323 endpoints in a consistent manner, allowing them to register with a gatekeeper and to locate another gatekeeper. The Gatekeeper provides logic variables for proxies or gateways in a call path to provide connectivity with the public switched telephone network (PSTN), to improve Quality of Service (QoS), and to enforce security policies. Multiple gatekeepers may be configured to communicate with one another, either by integrating their addressing into Domain Naming System (DNS), or via Cisco IOS configuration options.
Gatekeeper HSRP (Hot Standby Router Protocol) support consists of elements that affect both the gateway and gatekeeper functions in the router. The gateway periodically retries its registration when it detects a possible gatekeeper failure, in order to register itself with the backup gatekeeper. The backup gatekeeper normally operates in a passive mode in which it does not accept registrations, and becomes active only when it is notified by HSRP that it must become the primary gatekeeper.
There are two types of addresses used in H.323 destination calls:
The Cisco IOS Release 11.3(2)NA software feature Multimedia Conference Manager dealt primarily with H.323-ID addressing in interzone calls. With the new prefix commands, the administrator can now also configure interzone routing when calls are made using E.164 addresses.
Technology prefixes are designed to enable the use of E.164 address routing. E.164 is an International Telecommunications Union (ITU) specification for the ISDN international telephone numbering plan, which has traditionally only been used in telephone networks. These prefixes identify gateways that have specific capabilities within a given zone. They are handled specially in that the technology prefixes are ignored during the zone selection process and then examined for gateway selection within the zone.
There were no new features supported by the Cisco 3600 series routers in these releases.
Cisco IOS Release 11.3(3)NA was not released.
The following new features are supported by the Cisco 3600 series routers in Release 11.3(2)NA. The special Cisco IOS Release 11.3(2)NA image for Cisco 3600 series routers was not designed to perform as standard Cisco 3600 series router Cisco IOS software.
The Gatekeeper shelf feature for Cisco 3600 series routers for Cisco IOS Release 11.3(2)NA is offered in the IP Standard Feature Set described as follows.
Cisco Multimedia Conference Manager provides network administrators with a mechanism to support ITU-T H.323 applications without impacting the mission-critical applications that are running on today's networks. Multimedia Conference Manager also provides the mechanism to implement security for H.323 communications. The image has specialized features designed specifically for the Gatekeeper shelf feature (gatekeeper and proxy conforming to ITU-T H.323).
H.323 Multimedia Conference Manager, implemented on Cisco IOS software, provides the network administrator with the ability to do the following:
The H.323 gatekeeper is an infrastructure component defined by the ITU H.323 standard. It provides call routing functionality for H.323 endpoints, provides simple bandwidth management for H.323, and adds authentication, authorization, and accounting functionality for H.323 calls.
The H.323 proxy is included in the Multimedia Conference Manager feature. The H.323 proxy is a boundary device that terminates all H.323 calls from the local LAN/Zone and can establish sessions with H.323 endpoints that are in a different LAN/Zone. In doing so, the proxy provides the administrator the ability to set and enforce Quality of Service (QoS) policy on WAN segments, and provides a method to tag H.323 traffic for tunneling through firewalls.
This section describes the new features for the Cisco AS5300 universal access server in Cisco IOS Release 12.0(2)XH.
The High-Density Voice with DSPM-549 feature implements high-density voice support on the Cisco AS5300 by using DSPM-549 digital signal processor (DSP) modules. High-density voice support doubles the voice capacity of a Cisco AS5300 to at least 120 channels. A fully configured voice capable Cisco AS5300 router includes two voice carrier cards, each capable of supporting 60 concurrent sessions.
The benefits of double-density voice features include:
This section describes the new features for the Cisco AS5300 universal access server in Cisco IOS Release 11.3(7)NA.
R2 Signaling support has been added to existing ISDN PRI over a channelized E1 interface. This feature is available in countries supporting R2 signaling.
This application provides basic Interactive Voice Response (IVR) capabilities necessary to collect caller Personal Identification Number (PIN), passwords, and destination phone numbers. IVR consists of simple voice prompting and digit collection to collect information from the caller for the purpose of authenticating the user and to identify the destination.
The following two new IVR scripts have been added to this release:
This script is similar to clid_authen_col_npw, but it allows two retries (3 tries total) for entering the account and password. For each of the two retries, it plays a special retry message.
This is similar to clid_col_npw_3, but it does not collect a PIN number. Instead, it uses the collected account number with a NULL password for authentication.
This section describes the new features for the Cisco AS5300 universal access server in Cisco IOS Release 11.3(6)NA2, which introduced features supported by IP Telephony. Refer to the document Configuring the Cisco AS5300 for Voice Service Provider Features , which is an addendum to the Voice Over IP for the Cisco AS5300 Software Configuration Guide, for detailed information about these features.
The IP Telephony features include enhancements made to the functionality and configuration of both the gateway and the VoIP gatekeeper. The architecture of these features provides the Quality of Service (QoS), stability, and functionality necessary for carrier class real-time IP communications services. The Cisco gateway functionality and gatekeeper functionality work in concert to provide the ITU-T H.323 infrastructure.
To help understand the overall implication of which features affect which portion of the internetworking environment, the various IP Telephony features are described in the following two categories:
Can manage a zone and provide bandwidth management and address resolution services to gateways when present in the network.
Refers to the Cisco AS5300 universal access server with voice cards and the Voice over IP (VoIP) image. Gateways are also referred to as VoIP gateways.
The gateway can terminate a call from PSTN, provide user admission control using IVR, direct the call to the destination or terminates the call from another Gateway and sends the call to the PSTN, and finally provide accounting records for the calls.
Registration, Admission, and Status (RAS) is a signaling function that performs registration, admissions, status, and disengage procedures between the VoIP gateway and the gatekeeper.
The gateway relies on Cisco IOS command-line interface commands, outside the gateway configuration mode, to configure the AAA servers. Two following RAS command fields have been added to the dial-peer entry to enable the RAS implementation:
AAA represents authentication, authorization, and accounting features that are required in the VoIP gateway. The standard Cisco authentication, authorization, and accounting functionality is enhanced to allow calls to:
The AAA authentication feature permits RADIUS to authenticate users on the gateway. It is normally used with IVR to check the legitimacy of a prospective gateway user based on an account number (collected by IVR) or based on answer number identification (ANI).
"Simple" IVR allows the use of one of several interactive voice response scripts embedded in Cisco IOS software. The ability to modify the embedded scripts is not yet provided. However, you can modify the audio files (for the prompts).
You receive a voice prompt instruction to enter a specific type of information, for example, a PIN number. After playing the voice prompt, the IVR feature starts the process of collecting some number of touch tones (digit collection).
The purpose of this feature is to support the redirecting call feature of the VoIP gateway. The redirecting number is an optional field of the Q.931 Setup message.
When a local exchange carrier (LEC) switch detects an incoming call that is destined for a busy or nonanswering party, the switch formulates a Q.931 Setup message with the redirecting number field set to the originally called number, and sends to the gateway. The called party number of the Setup message will be set to one of the service access numbers dialed number identification service (DNIS) of the gateway.
If a redirect number is present in an incoming call, then it is used in place of the called number (DNIS).
The Rotary Calling Pattern feature provides the ability to route, under certain circumstances, an incoming call arriving by a telephony interface back out by another telephony interface. This is primarily used to provide reliable service during network failures. Call establishment via Rotary Call Pattern will be supported via rotary group support of dial peers where multiple dial peers may match a given destination phone number and will be selected in sequence.
In prior releases of VoIP, if you wanted the system to search through a number of destinations when a given number is dialed, you needed to configure those dial peers with the same destination pattern. Now with the Rotary Call Pattern feature, if you want the destinations to be tried in a certain order, you can assign preference (via the preference command) to the dial peers to reflect that order.
Channel Associated Signaling (CAS) is the transmission of signaling information within the voice channel. In addition to receiving and placing calls, T1 CAS:
The development of this feature enhances and integrates T1 CAS capabilities on the DSP Module (DSPM) in order to support central office (CO) and PBX configurations for voice calls.
No new features were introduced in these releases for the Cisco AS5300 universal access server.
Cisco IOS Release 11.3(3)NA was not released.
This section describes the new features for the Cisco AS5300 universal access server in Cisco IOS Release 11.3(2)NA.
The Voice over IP (VoIP) software enhancement was added in Cisco AS5300 for Cisco IOS Release 11.3(2)NA. VoIP:
Major customer applications include:
VoIP on the Cisco AS5300 supports two primary applications:
To use VoIP, primarily a software feature on the Cisco AS5300, you must install the VoIP feature card (VFC) that contains multiple digital signal processor (DSP) modules. The VFC uses the Cisco AS5300 quad T1/E1 PSTN interface and LAN or WAN routing capabilities to provide up to a 48- or 60-channel gateway for VoIP packetized voice traffic to and from T1/E1 time-division multiplexing (TDM) traffic.
Features for the Cisco AS5300 in Release 11.3(8)T are also supported in the current Cisco IOS Release 11.3(8)NA. For information about these features, see the current Release Notes for Cisco AS5300 for Cisco IOS Release 11.3 T.
Features added to the Cisco AS5300 for Cisco IOS Release 11.3 T between Cisco IOS Releases 11.3(2)T and Cisco IOS Release 11.3.(8)T, are not supported in Cisco IOS Release 11.3(8)NA unless they have also been added separately to Cisco IOS Release 11.2 NA and support is explicitly stated to coincide in the release notes for Cisco IOS Release 11.3(8)NA. Currently, no such features have been added. Check the feature set in the Release Notes for Cisco AS5300 for Cisco IOS Release 11.3 T to determine at which maintenance release a given feature was added.
The following sections list the new features that are available for the router shelf for Cisco IOS Release 11.3(4)T.
For more information about other features on this platform, use the following path on CCO or the Documentation CD-ROM:
The following new features for the router shelf were introduced in Release 11.3(4)T.
PPP over Frame Relay allows a router to establish end-to-end Point-to-Point Protocol (PPP) sessions over Frame Relay. IP datagrams are transported over the PPP link using RFC 1973-compliant Frame Relay framing. This feature is useful for remote users running PPP to access their Frame Relay corporate networks.
The PA-2FEISL 100BaseT Fast Ethernet/Inter-Switch Link (ISL) port adapters (PA-2FEISL-TX and PA-2FEISL-FX) are available for the Cisco 7200 series routers, for second-generation VIP2-15, VIP2-20, and VIP2-40 in all Cisco 7500 series routers and Cisco 7000 series routers with the Cisco 7000 series Route Switch Processor (RSP7000) and Cisco 7000 series Chassis Interface (RSP7000CI).
The 2FEISL-TX or 2FEISL-FX port adapter provides two 100-Mbps, 100BaseT Fast Ethernet/ISL interfaces for VLAN transport over switch-to-switch backbone connections or switch-to-server data center attachments. These port adapters provide an inter-VLAN bridging and routing functionality that network administrators can use to deploy 100-Mbps Token Ring VLAN transport, 100-Mbps Ethernet VLAN transport, and bridging or routing between the mixed LAN types using the same physical ISL trunk links. Both full-duplex and half-duplex operation are supported for the 2FEISL-TX and 2FEISL-FX port adapters.
For more information on the PA-2FEISL port adapters, refer to the publication PA-2FEISL 100BaseT Fast Ethernet/ISL Port Adapter Installation and Configuration . This document is available on CCO and on the Documentation CD-ROM:
The following new features are supported by the Cisco 7000 family of routers in Cisco IOS Release 11.3(3)T.
For more information about other features on this platform, use the following path on CCO or the Documentation CD-ROM:
Always On/Dynamic ISDN (AO/DI) is an on-demand service that optimizes the use of an existing Integrated Services Digital Network (ISDN) signaling channel (D channel) to transport X.25 traffic. The X.25 D channel call is placed from the subscriber to the packet data service provider. Multilink and TCP/IP protocols are encapsulated within the X.25 logical circuit carried by the D channel. The bearer channels (B channels) use the Multilink protocol without the standard Q.922 and X.25 encapsulations, and invoke additional bandwidth as needed. AO/DI takes full advantage of existing packet handlers at the central office by using an existing D channel to transport the X.25 traffic. The link associated with the X.25 D-channel packet connection is used as the primary link of the Multilink protocol. The D channel is a connectionless, packet-oriented link between the customer premise equipment (CPE) and the central office. Since the D channel is always available, it is possible to in turn offer "always available" services. On-demand functionality is achieved by using the B channels to temporarily boost data throughput and are disconnected after use.
The Multiple ISDN Switch Types feature allows you to configure more than one ISDN switch type per router. You can apply an ISDN switch type on a per interface basis, thus extending the existing global isdn switch-type command to the interface level. This allows Basic Rate Interfaces (BRIs) and Primary Rate Interfaces (PRIs) to run simultaneously on platforms that support both interface types.
The isdn tei command is also extended to the interface level. Terminal endpoint negotiation (TEI) determines when Layer 2 is activated (powerup or first-call).
National ISDN Switch Types for Basic Rate and Primary Rate Interfaces introduces changes to ISDN switch types for PRI and BRI as follows:
Note The command parser will still accept the following switch types: basic-nwnet3, vn2, and basic-net3; however, when viewing the NVRAM configuration using either the show running configuration or write terminal command, the basic-net3 or vn3 switch types are displayed, respectively.
The Dedicated Token Ring port adapter (PA-4R-DTR) is available on Cisco 7500 series routers, Cisco 7200 series routers, and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI).
The PA-4R-DTR provides up to four IBM Token Ring or IEEE 802.5 Token Ring interfaces. Each Token Ring interface can be set for 4 Mbps or 16 Mbps half-duplex or full-duplex operation and can operate as a standard Token Ring station or as a concentrator port. The default for all interfaces is Token Ring station mode with half-duplex, 16-Mbps operation. The PA-4R-DTR connects over Type 1 lobe or Type 3 lobe cables, with each interface providing an RJ-45 receptacle.
The CPA is a standard single-width port adapter supporting ESCON or parallel (also known as "bus and tag") channel interfaces to IBM and IBM-compatible mainframes.
The CPA comes with a default of 16 MB of RAM. Customers might upgrade to 32 MB of RAM either at the Cisco factory before the CPA is shipped or as a field upgrade after the CPA has been installed.
The only difference between channel software applications (IP Datagram, Cisco SNA, TCP/IP Offload, TN3270 Server, and CMPC) running on the CIP and CPA is performance. The CIP will typically have higher performance and capacity than the CPA because the CIP has more memory (128 MB of RAM compared to 32 MB for the CPA) and a faster internal bus (64-bit bus compared to the 32-bit bus on the CPA).
By default, DLSw+ terminates the RIF for Token Ring, terminates the LLC for all media types, and forwards only data across a WAN with DLSw+ and TCP/IP headers. The RIF is a field in source-route bridged frames that indicates the SRB path the frame should take when traversing a Token Ring network. In the case of an explorer packet, the RIF is a field of the source-route bridged frame that indicates the SRB path that the SRB explorer has traversed so far. The RIF is limited to seven hop counts by IBM standards. Because DLSw+ terminates the RIF at the virtual ring, the network's scalability increases because the hop count of the packet starts over, and the packet can traverse seven additional hops. Also, RIF termination simplifies network design because ring numbers no longer have to be unique throughout an entire enterprise.
However, some environments do not function properly if the RIF is terminated. For that reason, DLSw+ now supports the RIF Passthru feature, in which the entire source-route bridged path appears in the RIF.
The DMS100 and NI2 switch types have been added to the existing Non-Facility Associated Signaling (NFAS) with D-channel Backup feature.
ISDN NFAS allows a single D channel to control multiple PRI interfaces. A backup D channel can be configured for use when the primary NFAS D channel fails.
When the channelized T1 controllers are configured for ISDN PRI, only the NFAS primary D channel must be configured; its configuration is distributed to all the members of the associated NFAS group.
RJ-45 Interface Support—Cisco 7200 series routers support a new I/O controller with an RJ-45 interface. The optional Fast Ethernet port is configurable for use at 100 Mbps full-duplex or half-duplex (half duplex is the default). The Fast Ethernet port is equipped with either a single MII receptacle or an MII receptacle and an RJ-45 receptacle.
To support this new feature, the media-type interface command has been modified. The media-type interface command now supports two options:
Note When using the I/O controller that is equipped with an MII receptacle and an RJ-45 receptacle, only one receptacle can be configured for use at a time.
The following new features are supported by the Cisco 7000 family of routers in Cisco IOS Release 11.3(2)T.
For more information about other features on this platform, use the following path on CCO or the Documentation CD-ROM:
The NPE-300 for Cisco 7200 series routers is now available. The network processing engine maintains and executes the system management functions for Cisco 7200 series routers. The network processing engine also shares the system memory and environmental monitoring function with the I/O controller. The NPE-300 has an R5000 microprocessor that operates at an internal clock speed of 200 megahertz (MHz), 4 MB of SRAM, and erasable programmable read-only memory (EPROM) for storing sufficient code for booting the Cisco IOS software. For more information on the NPE-300, refer to the publication Network Processing Engine Replacement Instructions .
The PA-12E/2FE Ethernet switch 10BASE-T and 100BASE-TX port adapters are available on Cisco 7200 series routers. The PA-12E/2FE port adapter provides up to twelve 10-Mbps and two 10/100-Mbps switched Ethernet (10BASE-T) and Fast Ethernet (100BASE-TX) interfaces for an aggregate bandwidth of 435 Mbps, full-duplex. For more information on the PA-12E/2EF port adapter, refer to the publication PA-12E/2EF Ethernet Switch 10BASE-T and 100BASE-TX Port Adapter Installation and Configuration that accompanies the hardware and the feature module in the Feature Guide for Cisco IOS Release 11.2.
The Enhanced ATM VC Configuration and Management feature set includes new and enhanced capabilities that allow you to create and manage ATM PVCs and SVCs with more ease and improved integrity. This feature set includes the following five subfeatures:
The New VC Configuration subfeature allows you to create ATM permanent virtual circuits (PVCs), switched virtual circuits (SVCs), static maps, and associated virtual circuit (VC) parameters more easily and with fewer errors using new ATM commands in new VC command modes.
The VC Integrity Management subfeature allows you to manage your ATM PVCs and SVCs so that your router receives immediate notification of when these VCs go down in your network. Upon notification, protocols can reroute packets and prevent unpredictable and relatively long timeout periods.
The PVC Discovery subfeature allows you to enable your router to automatically assign (or discover) PVCs on an ATM interface or subinterface using information from an attached adjacent switch.
The Multiprotocol Inverse ARP subfeature allows you to enable a dynamic protocol mapping between an ATM PVC and a network address by configuring Inverse Address Resolution Protocol (Inverse ARP) on ATM PVCs running IP or IPX.
The Rate Queue Tolerance subfeature allows you to configure a range of peak rates on a single rate queue, thereby improving ATM rate queue usage.
The following new features are supported by the Cisco 7000 family of routers in Cisco IOS Release 11.3(1)T.
For more information about other features on this platform, use the following path on CCO or the Documentation CD-ROM:
The SNMP Manager feature allows a router to serve as an SNMP manager. As an SNMP manager, the router can send SNMP requests to agents and receive SNMP responses and notifications from agents. When the SNMP manager process is enabled, the router can query other SNMP agents and process incoming SNMP traps.
The SNMP Inform Requests feature allows routers to send inform requests to SNMP managers. Routers can send notifications to SNMP managers when particular events occur. For example, an agent router might send a message to a manager when the agent router experiences an error condition.
SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send any acknowledgment when it receives a trap. The sender cannot determine if the trap was received. However, an SNMP manager that receives an inform request acknowledges the message with an SNMP response PDU. If the manager does not receive an inform request, it does not send a response. If the sender never receives a response, the inform request can be sent again. Thus, informs are more likely to reach their intended destination.
Because they are more reliable, informs consume more resources in the router and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in memory until a response is received or the request times out. Also, traps are sent only once, while an inform request might be retried several times. The retries increase traffic and contribute to a higher overhead on the network. Thus, traps and inform requests provide a trade-off between reliability and resources. If it is important that the SNMP manager receives every notification, use inform requests. On the other hand, if you are concerned about traffic on your network or memory in the router and you do not need to receive every notification, use traps.
There are no new features in Catalyst Release 3.2 that affect the switch shelf for the Cisco AccessPath-VS3 System.
For more information about other features on this platform, use the following path on CCO or the Documentation CD-ROM:
This section describes the new features for software release 3.2.
This section describes the new features for software release 3.1.
Enables and disables line protocol state determination of the RSM due to Catalyst port state changes.
Displays the current status of RSM line protocol state determination (either enabled or disabled).
The Cisco IOS software is packaged into "feature sets" (also called "software images"). There are many different feature sets available, and each feature set contains a specific subset of Cisco IOS features. The following tables list only those feature sets which apply to the Cisco AccessPath-VS3 System. For a detailed list of other features available for individual configurations when used independently of the Cisco AccessPath-VS3 System, refer to the "Cisco Connection Online" section, or the "Documentation CD-ROM" section.
Table 2 use the following conventions to identify features:
On the Cisco AccessPath-VS3 system, the System Controller uses the IP Plus Feature set exclusively. There are no new features in Cisco IOS Release 11.3(5)T which affect the System Controller for the Cisco AccessPath-VS3 system. For more information about other features on this platform, use the following path on CCO or the Documentation CD-ROM:
Table 2 lists the Cisco IOS software feature sets available for the Cisco 3600 series in Cisco IOS release 11.3 T. Cisco IOS release 11.3 T supports the same feature sets as Cisco IOS release 11.3, but it might also have new features supported by the Cisco 3600 series.
| Feature Set | Feature Set Matrix Term | Software Image | Platforms |
|---|---|---|---|
| IP Standard Feature Sets | |||
| 1This feature is offered in the Plus feature set.
2This feature is offered in the encryption feature sets which consist of 40-bit (Plus 40) data encryption feature sets. 3This feature is offered in the encryption feature sets which consist of IPsec 56-bit (Plus IPsec 56) data encryption feature sets. |
Table 3 lists the features and feature sets supported by the Cisco 3600 series in Cisco IOS Release 11.3 T.
Note This feature set table contains only a select list of features. This table is not a cumulative or complete list of all the features in each image.
| 1This column indicates the maintenance release in which the fetaure was introduced. For example, a (2) means a feature is introduced in Release 11.3(2)T. If a cell in this column is empty, the feature was included in the initial base release. |
For more specific feature set information for this platform, see: "Release Notes for Cisco 3600 Series Routers for Cisco IOS Release 11.3 NA." or access this document on CCO via the following path: Service and Support: Technical Documents: Documentation:Access Servers & Access Routers: Modular Access Routers:Cisco 3600 Series.
This section lists Cisco IOS software feature sets available in Cisco IOS Release 11.3(7)NA. The following list summarizes the Gatekeeper shelf features that you can use when running the IP feature set on the Cisco 3600 series in Cisco IOS Release 11.3(7)NA.
Table 4 lists the feature set available for the Cisco AS5300 in Cisco IOS Release 12.0(2)XH.
Note This feature set table contains only a selected list of features. This table is not a cumulative or complete list of all the features in each image. This release supports the features contained in Cisco IOS Release 12.0(2)XH for the Cisco AS5300. For the complete feature set table, see the Release Notes for Cisco AS5300 Universal Access Servers for Cisco IOS Release 12.0(2)XH.
Table 5 lists the feature sets available for the Cisco AS5300 in Cisco IOS Release 11.3(7)NA. The images shipped with the VoIP feature are available only under the following feature sets:
Note In addition to its special Voice over IP (VoIP) feature initially introduced in Cisco IOS Release 11.3(2)NA, this release also supports the features contained in Cisco IOS Release 11.3(8)T for the Cisco AS5300. For the feature set table for the previous release, see the Release Notes for Cisco AS5300 Series for Cisco IOS Release 11.3 T.
| In | Feature Set | ||||||
|---|---|---|---|---|---|---|---|
| Feature | IP | IP Plus | Desktop | Desktop Plus |
Enterprise | Enterprise Plus |
|
| Voice over IP | |||||||
On the Cisco AccessPath-VS3 System, the router shelf uses the Enterprise feature set exclusively.
For more information about other features on this platform, use the following path on CCO or the Documentation CD-ROM:
Note Encryption feature sets (for example, IP 40 and IP 56) are not available in Cisco IOS Releases 11.3(1)T and 11.3(2)T. These feature sets are available in Release 11.3(3)T and later 11.3 T releases.
Table 6 lists the features available for the router shelf up to and including Cisco IOS Release 11.2(4)T.
The optional feature sets listed in Table 7 can be used for routing out of the Cisco AccessPath-VS3 system and into your network.
| WAN Packet Protocols |
| Interdomain Routing |
| VIP/VIP2 support2 |
| CIP Support2, 3 |
| NetFlow Switching4 |
| 1BGP4 includes soft configuration, multipath support, and prefix filtering with inbound route maps.
2Supported on Cisco 7000 series with the RSP7000 and RSP7000CI. 3CIP orders must include one or both of the licenses. 4Supported on Cisco 7200 series only. 5NetFlow supports IP over all interfaces with optimal performance on Ethernet, FDDI, and HDLC. |
On the Cisco AccessPath-VS3 system, the Switch Shelf uses the Catalyst Supervisor Feature set exclusively. There is no new feature set information for the switch shelf which affects this configuration for the Cisco AccessPath-VS3 system.
For more information about other features on this platform, use the following path on CCO or the Documentation CD-ROM:
This section contains the open and resolved caveats for each Cisco IOS maintenance release that runs on the Cisco AccessPath-VS3 System. This information is organized by Cisco AccessPath-VS3 system component. For a list of software caveats that apply to previous maintenance releases refer to the "Related Documentation" section.
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. Bug Navigator II can be found at http://www.cisco.com/support/bugtools, or from CCO, select Service & Support: Online Technical Support: Software Bug Toolkit: Bug Navigator II.
This section contains open and resolved caveats for the Cisco 3640 when it is used as System Controller for the Cisco AccessPath-VS3 system. For more information on these and other caveats for the Cisco 3640, refer to the Release Notes for the Cisco 3600 Series For IOS Release 11.3T. This document is available on CCO and the Documentation CD-ROM:
For a list of software caveats that apply to this release, refer to the Caveats for Cisco IOS Release 11.3 T document that accompanies these release notes and is also located on CCO and the Documentation CD-ROM. The caveats document contains open and resolved caveats of severity 1, the most serious caveats, and severity 2, less serious caveats.
Because Release 11.3 T is based on Release 11.3, all caveats in Release 11.3 also apply to this release. To access these caveats, see the "Important Notes and Caveats" section in the cross-platform Release Notes for Cisco IOS Release 11.3 document located on CCO and the Documentation CD-ROM.
There are no new caveats in Cisco IOS Release 11.3(6)NA2; however, caveats for Cisco IOS Release 11.3(2)T, up to and including Cisco IOS Release 11.3(6)T can also apply to Cisco IOS Release 11.3(6)NA. For information on these caveats, refer to the maintenance release (6) version of Release Notes for Cisco 3600 series for Cisco IOS Release 11.3 T. This document is available through CCO via the following path: Service and Support: Technical Documents: Documentation:Access Servers & Access Routers: Modular Access Routers:Cisco 3600 Series.
There are currently no caveats exclusive to these releases for the Cisco 3600 series router.
This section describes possibly unexpected behavior by Release 11.3(5)NA. Unless otherwise noted, these caveats apply to all 11.3 releases up to and including 11.3(5)NA.
The R2 custom configuration does not take effect.
The conn is null when we get to pt_manage_vtyasync(). This could be because the connection is closed immediately after setup for unknown reasons. As a solution, check for conn before using it.
This section describes possibly unexpected behavior by Release 11.3(4)NA. Unless otherwise noted, these caveats apply to all 11.3 releases up to and including 11.3(4)NA. For additional caveats applicable to Release 11.3(4)NA, see the caveats sections for newer 11.3 releases. The caveats for newer releases precede this section.
All the caveats listed in this section are resolved in release 11.3(5)NA.
The command show ip bgp crashes when routes are displayed.
The full-duplex command will not work on the 1FE PA, due to this bug. There is no workaround.
The router does not recognize the 3 commands crypto cisco key-timeout, crypto cisco connections, and crypto cisco entities. These are features often used by customers and fixed in the 11.3(4)T.
Under certain conditions, MC11 hardware can deliver corrupted data to the system, which can cause various types of system crashes. There is no safe method of detecting if this problem exists in a given system. Analysis to determine if it is caused by a hardware flaw is still underway. Because it was observed with one specific MC11 modem card only, the current workaround is to replace the board.
When operating with a WIC-BRI-S/T or WIC-BRI-U in one WIC slot and a WIC-1T, WIC-2T or WIC-2A/S in the other WIC slot, the BRI WIC interface will not pass any data traffic. The BRI calls will come up, but they will drop after 22 to 23 seconds. The BRI WIC will work correctly if there is no WIC-1T, WIC-2T, or WIC-2A/S installed.
Caveats in the parent Release 11.3 T might also apply to Release 11.3(6)NA. For descriptions of caveats for the Cisco 3600 series routers supported under Cisco IOS Release 11.3 T, up to
and including 11.3(5)T, see the current Release Notes for the Cisco 3600 Series for Cisco IOS Release 11.3 T .
This section only contains open and resolved caveats for Release 12.0(2)XH. All caveats in Release 12.0 and Release 12.0 T are also in Release 12.0(2)XH.
These caveats documents are located on CCO and the Documentation CD-ROM.
This section describes possibly unexpected behavior by Release 12.0(2)XH and describes only severity 1 and 2 caveats.
The following CLI command does not function: snmp-server packetsize.
The maximum snmp packetsize for Release 12.0(3)T is fixed at 484. There is no known workaround.
When tunneling IPX over an IP tunnel and using an extended inbound access list for IP on the tunnel interface, the IPX traffic gets blocked by the access list. As a workaround a permit gre statement could be added in the extended access list.
There is no way to configure MICA modem lines on a Cisco 3640 for dialout only. The modem dtr-active command is supposed to work, but this fails with "NO DIALTONE".
A VIP controller hangs when encryption is used. The problem is intermittent. Reloading the Cisco 7500 returned the connections. The [shut | no shut] commands do not help.
A Cisco 3640 with PRI gets stuck on Layer 1 activating mode if the PRI D-channel is in standby or shut mode. The following error message appears:
Workaround: Remove the D-channel from standby or shut mode. To do this, remove the backup interface command, reload the router, then reinsert the backup interface command.
All the caveats listed in this section are resolved in Release 12.0(2)XH. This section only describes severity 1 and 2 caveats.
Because Release 12.0(2)XH is an initial release, there are no resolved caveats.
For more information on these caveats, refer to the "Release Notes for the Cisco AccessPath 5300 For IOS Release 11.3NA". This document is available on CCO via the following path: Service and Support: Technical Documents: Documentation: Access Servers & Access Routers: Cisco Voice over IP Documentation: Voice over IP for the Cisco AS5300.
For information on caveats in Cisco IOS Release 11.3 NA, refer to the "Important Notes and Caveats for Release 11.3" section in the cross-platform Release Notes for Cisco IOS Release 11.3 document. These cross-platform release notes contain caveats affecting all maintenance releases.
For information on other caveats that also apply to this release, refer to the Caveats for Cisco IOS Release 11.3 T document. This caveats document lists severity 1 and 2 caveats for Release 11.3 T. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Caveats describe unexpected behavior or defects in Cisco IOS software releases.
Because Release 11.3 NA is based on Release 11.3 and Release 11.3 T, all caveats in Release 11.3(8) and Release 11.3(8)T are also in Release 11.3(8)NA.
This section describes possibly unexpected behavior by Release 11.3(8)NA. This section describes only severity 1 and 2 caveats.
Under certain conditions, when you use session target ras on a Cisco AS5300, the h.225 IRR (Information Request Response) messages may not be properly built by the router.
When you have a Multilink PPP (MLP) bundle with more than 1 B channel in the bundle, the fragmentation and interleaving does not queue packets fairly on each of the links in the bundle.
All the caveats listed in this section are resolved in Release 11.3(8)NA. Unless otherwise noted, this section describes only severity 1 and 2 caveats.
When using RSVP with an AS5300 voice gateway, the gateway may crash with a bus error immediately preceded by a %UTIL-3-TREE data structure error. There is no known workaround other than to disable RSVP on the gateway.
The IP portion of an incoming call might not terminate correctly if the caller closes the connection. This situation is the result of rare timing conditions. There is no workaround.
Under very rare circumstances, the system can crash in cmts_rx_interrupt. This is caused by bad received data. It was only observed on MC11 cable line cards, and so far only once. There is no workaround.
Prior to this fix, the uBR7200 series router may crash with a bus error exception when user does a shutdown of a specific upstream port on the cable interface or shutdown of the cable interface itself. The crash is likely to happen only if at the time of shutting the cable interface (or upstream port), the downstream channel of that cable interface was running at high traffic load, with some back to back packets queued for transmission on the downstream link.
There is no known workaround for the problem.
In the downstream direction, (data) packets are not padded to the minimum length of 60 bytes. This may cause RUNT packets transmitted to the Ethernet behind a cable modem, if the cable modem software does not pad to the minimum packet length.
This used to be optional, but was changed recently in the specification, and is considered a caveat.
In Release 12.0, if CEF switching is enabled, packets shorter than the minimum permitted packet size are corrupted during transmission, and the modem receives packets with HCS errors. A workaround is to disable CEF switching.
Before this fix, the CMTS may be issue bad start allocation times, acknowledgment times in the upstream channel MAPs due to a bad counter mask value. This problem can only occur for the ASIC version of the cable line card.
All information below only applies if the (Cable) MAC header received from cable modems has an odd length. So far, this has only been observed by one modem vendor when Baseline Privacy is active.
If flow switching is enabled, packets received from a Cable interface and transmitted to another interface will be corrupted. Also, several alignment errors will be reported.
If flow switching is enabled, but CEF switching is disabled, several alignment errors will be reported. Switching itself will work.
If CEF switching is enabled, packets received from a Cable interface and transmitted to another interface will be corrupted. Also, several alignment errors will be reported.
If BPI is active, or registration requests contain BPI fields, each registration request will cause a memory leak of approximately 50-100 bytes.
A workaround is to not enable BPI, and to configure cable qos permission modems.
This section contains open and resolved caveats for the Cisco 7206 when it is used as a router shelf for the Cisco AccessPath-VS3 system. For more information on these and other caveats for the Cisco 7206, refer to the Release Notes for the Cisco 7206 Series For IOS Release 11.3(4)T.
This document is available on CCO and the Documentation CD-ROM:
Caveats in Cisco IOS Release 11.3 also apply to Cisco IOS Release 11.3T. For information on caveats in the Cisco IOS Release 11.3, refer to the "Caveats" section in the Cross-Platform Release Notes for Cisco IOS Release 11.3 document located on CCO and the Documentation CD-ROM. This section contains caveats affecting all maintenance releases.
This section describes possibly unexpected behavior by Cisco IOS Release 11.3(4). Unless otherwise noted, these caveats apply to all Cisco IOS 11.3 releases up to and including Cisco IOS Release11.3(4). For additional caveats applicable to Cisco IOS Release 11.3(4), see the caveats sections for newer Cisco IOS 11.3 releases. The caveats for newer releases precede this section.
A regression of CSCdj88079, which is a regression of CSCdj63179, occurs as a result of initializing the hardware PPP mode on.
This leads to a situation in the RX interrupt of the async driver where it assumes that if PPPMODE is set the appp_context must be allocated, and therefore crashes.
Dialer interfaces are not included in a data structure queryable via SNMP. Please include dialer interfaces in the structure.
ipRouteIfIndex returns illegal value of zero.
When bootflash is full, a squeeze operation may hangs the console session. Other symptoms may include high CPU and an endless loop in the operation.
When using boot config slot0:(filename) command to store and boot configuration from the flash card, it is unable to save running configurations larger than the NVRAM size to the flash card by the use of the write mem command.
service compress-config command can normally be used as a workaround, but it may be affected by DDTS CSCdj63926. The safe workaround is to use tftp to save the larger configurations.
slave auto-sync config does not work and wr mem is rejected with the error message:% Slave config is being used, please retry command.
This regression affects IOS maintenance releases 11.2(11), 11.1(16) 11.3(2) and later. It occurs when the wr mem command is not always executed from the same vty.
The workaround is to simply perform the 'wr mem' again from the same vty.
MTU size of interfaces using ESA's service: Currently the ESA will support maximal packet size up to 16K bytes. All the interfaces which use ESA's service should configure its MTU to be no larger than 16K (16384) bytes.
It has been possible in the past for corrupted pointers to cause errors while freeing packets. These errors could lead to system crashes in certain circumstances.
To prevent this, code has been added which will verify the integrity of these pointers to be sure they are valid.
If a pointer is found to be invalid an error similar to this will appear:
%RSP-2-BADCACHE: Possible cache overrun detected. End of MEMD buffer: 0x401E9200 End of datagram: 0x401E92E2 bufhdr 4800D0A0: 0200016B 000001F0 3FEFEFEF 001E8B80 Flushing Cache -Traceback= 601EB8B0 601EBCD4 601ED66C 601F29B0 601B9550
The "End of MEMD buffer" indicates the end of the area reserved for this packet. The "End of datagram" indicates where the system believes the current packet ends.
If the end of datagram is larger than the end of the MEMD buffer, we will take corrective actions and flush the processor memory cache. A traceback is displayed to aid Cisco Engineers in determining the code path which lead to the message being displayed.
Additional information can be obtained by issuing the command: "test rsp debug on"
Now when the condition occurs the user will see something similar to:
%RSP-2-BADCACHE: Possible cache overrun detected. End of current MEMD buffer : 0x401E9200 Where datagram would have ended: 0x401E92E2 bufhdr 4800D0A0: 0200016B 000001F0 3FEFEFEF 001E8B80 Flushing Cache -Traceback= 601EB8B0 601EBCD4 601ED66C 601F29B0 601B9550
%SYS-3-DMPMEM: 581E8B80: 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF %SYS-3-DMPMEM: 581E8B98: 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF %SYS-3-DMPMEM: 581E8BB0: 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF %SYS-3-DMPMEM: 581E8BC8: 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEFEFEF 3FEF0100 0CCCCCCC %SYS-3-DMPMEM: 581E8BE0: 00E0F9AA A010015D AAAA0300 000C2000 01B436BC 0001000E %SYS-3-DMPMEM: 581E8BF8: 37323036 722D5275 74680002 00110000 00010101 CC000463 %SYS-3-DMPMEM: 581E8C10: 63630100 03001346 61737445 74686572 6E657432 2F300004 %SYS-3-DMPMEM: 581E8C28: 00080000 00010005 00F14369 73636F20 496E7465 726E6574 %SYS-3-DMPMEM: 581E8C40: 776F726B 204F7065 72617469 6E672053 79737465 6D20536F %SYS-3-DMPMEM: 581E8C58: 66747761 7265200A 494F5320 28746D29 20373230 3020536F %SYS-3-DMPMEM: 581E8C70: 66747761 72652028 43373230 302D4A53 2D4D292C 20457870 %SYS-3-DMPMEM: 581E8C88: 6572696D 656E7461 6C205665 7273696F 6E203131 2E332831
The additional output is packet memory that can be used for analysis by Cisco Engineers.
Care should be taken when issuing the test rsp debug on command as it will also display other debug information from the system and error messages are not throttled. This could result in the console logs being filled with data if the error is occuring frequently enough.
NTP will not synchronize. This problem occurs only in 11.3 and 12.0.
Currently there is no workaround.
The '<Switching_method> not supported on <Interface_name>' error messages are missing a trailing CR/LF.
RTR will use IP Loose Source Routing option when doing traceroute to find out path. This eliminates the phantom path problem caused by multiple equal cost paths in a network. Here is how it works. Suppose we are doing traceroute from A to D:
TTL 1: Send packet without LSR option. We will get TTL expire message from B. TTL 2: We will put B in LSR IP option to force the packet to go through B. We will get TTL expire message from C. TTL 3: We will put C in LSR to force the packet to go through C. ...
If IP source routing option is disabled in intermediate hop, we will not use LSR from that point on.
If traceroute packets times out for 3 times for a TTL, we will stop sending traceroute packets for TTL greater than that TTL. That is, the path will stop at that point.
Customers may experience data anomalies over SMDS when running Cisco IOS 11.1, or 11.2 and fragmentation is required.
This problem does not occur when using any other encapsulation (i.e., HDLC).
The output rate (in pkt/sec) and amount of packet reported per sec are incorrect when fancy queuing is enabled.
This problem causes any translational bridging between any media and SMDS failed on 7200 and 3600 platform. The affected release will be 11.1CA, 11.2P, 11.3, 11.3T and 12.0.
When the BVI interface is created, it breaks the IP multicast filter and affects all routing protocols that use IP multicast hellos. If running OSPF, the neighbor command can be configured as a workaround. No workaround exists for HSRP or EIGRP.
Responses to RIP queries do not honor IP split horizon rules.
Routing table entry of interface configured with supernet address does not get removed from routing table when interface goes down; Workaround is to manually clear routing table by issuing the command, clear ip route *.
A (*,G) entry with 0.0.0.0 as the RP needs to install the RP information when a new RP is learned.
When two ABR's are both summarizing one particular network, if one ABR loses all the specifics then the router won't accept the summary route from the other ABR. The workaround for this is to take out the area range command.
For BGP paths with identical attributes and router IDs, the neighbor address comparison will be skipped over .
A workaround is to use local_pref, med or other attributes to designate the desired the path.
NTP does not synchronize if a router is configured as a broadcast client and has an NTP broadcast server.
Since the unicast and the broadcast NTP packets contain conflicting information the client cannot synchronize them.
The solution is to configure the client so that it is not configured as both a broadcast and unicast client.
Slow BGP convergence has been observed with ***EBGP peer-groups*** in 11.1(19)CC1.
As a workaround, customers are advised to configure the following command for EBGP peer-groups using the 11.1(19)CC1 image:
router bgp xxxx neighbor <ebgp-peergroup-name> advertisement-interval 6 end
EIGRP does not trigger the selection of a new route when an equal or lesser path is removed from the RT. The route disapears but no new route is selected from the topology table.
Host | -----------LAN | | Active Standby | | net net
The standby router will do proxy arp reply even though it's not active. This is because the active router may not reply if the next hop is through the LAN. When the standby router replies it puts the virtual MAC address in both the ARP field and in the MAC layer field.
If the active and standby routers are on different ports on a switch the switch learns the virtual MAC address from both of them and may thrash its MAC layer cache.
The workaround is to disable proxy arp.
When changing from unnumbered to numbered on a serial interface, EIGRP keeps the neighbor up, even though that interface is configured in an ip subnet, not belonging to any network statement under router eigrp.
The workaround is to reconfigure EIGRP, or reload the router. Clearing the neighbors does not help.
Another workaround is to issue the no ip unnumber before assign ip address on the serial interface.
On a particle platform (i.e., Cisco 7200 series), if NAT is configured on a non fast-swiching interface, a packet translated by NAT in the fast path may generate alignment error messages if it is bumped for process switching.
The output of show access-lists may display a negative number of matches, for example:
router#show access-lists 140 Extended IP access list 140 permit gre 194.68.128.0 0.0.0.255 any log-input permit ip any any (-185099051 matches) ^^^^^^^^^^
This is a cosmetic problem and has no effect on the performance of the router.
A NAT router might translate the source address of a packet generated by the router. This causes problems in establishing neighborships for OSPF EIGRP. Also pings generated by the router leave with an incorrect SA.
RIP version 2 authentication is failed if we configure service password-encryption command before configuring key-string and use more than 15 characters key-string.
When you have log-adjacency-changes configured under OSPF and a passive serial line goes down, it prints an erroneous OSPF-5-ADJCHG message.
When multiple ip pim accept-rp filters are configured, they must be in the following order: "accept-rp <specific RP address> <acl>", ...,"accept-rp auto-rp", "accept-rp 0.0.0.0 <acl>". E.g., the following will accept 171.69.58.88 as the RP for groups in 239.0.0.0/8, and RPs for groups in the Auto-RP cache. If the RP and group don't match the first two filters, the 3rd filter is in effect, i.e. any RP is accepted for groups permitted by ACL 2.
ip pim accept-rp 171.69.58.88 1 ip pim accept-rp auto-rp ip pim accept-rp 0.0.0.0 2
access-list 1 permit 239.0.0.0 0.255.255.255
access-list 2 deny 224.0.1.39 access-list 2 deny 224.0.1.40
Service timestamp should be on by default.
Workaround: turn on service timestamp to get the timestamp on your console messages.
The counter for the ESA commands is a signed variable that became a negative number instead of wrapping around as it should. Since that is not a valid counter value, the commands stopped working and the connection setup stopped authenticating properly.
4T serial on the Cisco 7200 series routers or RSP may cause crash during normal operation. If the stack decode shows that the crash is caused in the s4t receive interrupt, then it is related to this bug. There is no workaround for this problem. The only solution is to upgrade to a system image which has the fix for this problem.
When running NAT and encryption, FTP fails, but Telnet and Ping both work. It seems that the tcp checksum is not calculated correctly. Removing NAT or encryption will resolve the problem.
For performance reasons, decryption is not done until the packets are switched to the output interface. This caused the problem with IOS NAT since NAT may need to do the payload translation for certain protocols. The protocols which are effected by this problem are FTP and NetBios.
If a BRI interface is part of a rotary group, and if a crypto map is applied to both the Dialer and BRI, and if the crypto map is then removed from one of the interfaces, the system may reload.
When ten or more standby groups are configured before any IP addresses are configured, the router reloads.
Due to this bug the IP cache entries pointing towards sub-interfaces will not be deleted when the sub-interface goes down. The work around is to clear the IP cache.
This bug was introduced by CSCdi73935 and is present in releases 011.003(003.001) and later, 11.3(03.01)T and after.
This section contains open and resolved caveats for the Catalyst 5002 when it is used as the switch shelf for the Cisco AccessPath-VS3 system. For more information about other caveats on this platform, see the Release Notes for Catalyst 5000 Series Software Release 3.2(1b).
Under certain conditions, a Catalyst 5000 series switch stops sending syslog output to the logging server. The workaround is to reset the switch.
The following sections describe the documentation available for the Cisco AccessPath-VS3 system. Typically, these documents consist of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules, which are updates to Cisco IOS documentation. Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online only.
Table 1 lists the Cisco AccessPath-VS3 system shelves and the version of the Cisco IOS software each is running. (The switch shelf does not run Cisco IOS software.) In order for the Cisco AccessPath-VS3 system to operate correctly, it must have the correct software.
The most up-to-date documentation can be found on the Web via Cisco Connection Online (CCO) and the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard copy documents were printed.
These release notes should be used in conjunction with the documents listed in the following sections:
The following documents are specific to Cisco AccessPath-VS3 system. They are located on CCO and the Documentation CD-ROM:
Online documentation for the System Controller includes:
Online documentation for the Access server shelf with 8 PRI includes:
Online documentation for the Access server with 4 PRI includes:
Online documentation for the switch shelf includes:
The documents listed here are supplemental. You might not need them to use the Cisco AccessPath-VS3 system. Refer to them only if you have advanced software configuration requirements that are not discussed in the Cisco AccessPath-VS3 Packet Telephony Concentrator Software Configuration Guide.
The Cisco IOS software document sets consist of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents. These documents are shipped with your order in electronic form on the Documentation CD-ROM, unless you specifically ordered the printed versions.
Note The Cisco AccessPath-VS3 system has been tested and optimized to work with its preconfigured hardware and software. For optimal performance, maintain the Cisco AccessPath-VS3 system's configuration in accordance with the guidelines outlined in the "AccessPath-VS3 System Configuration Guidelines" section.
The following are some of the Cisco IOS Release document types that are available in electronic form, printed form, or both forms:
Table 8 lists the Cisco IOS software documentation set that contains Cisco IOS configuration guides, command references, and several supporting documents. The document set is available in electronic form, and is also available in printed form if you special order it.
Note The most current Cisco IOS documentation can be found on the latest Documentation CD-ROM and on the Web. These electronic documents contain updates and modifications made after the paper documents were printed.
Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, and Cisco IOS software functionality and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Each configuration guide can be used in conjunction with its corresponding command reference.
On CCO and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set: configuration guides and command references.
Table 8 details the contents of the Cisco IOS Release software documentation set for the three IOS Releases that appear on the Cisco AccessPath-VS3 system. Table 8 does not apply to the Catalyst 5002 Switch because it runs on Catalyst software. Cisco IOS documentation is available in electronic form, and also in printed form upon request.
Note The most current Cisco IOS documentation can be found on the latest Documentation CD-ROM and on the Web. These electronic documents might contain updates and modifications made after the paper documents were printed.
Those books or chapters that are specific to a Cisco IOS release are marked with the release number. If no release number appears after a chapter title, it applies to all three Cisco IOS releases that run on the Cisco AccessPath-VS3 system.
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 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 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: Tue Jan 21 05:13:30 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.