|
|
August 2, 1999
These release notes for Cisco AS5300 universal access server support Cisco IOS Release 11.3 T, up to and including Release 11.3(11)T. These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and changes to the microcode or modem code and related documents.
For a list of the software caveats that apply to Release 11.3(11)T, see the Caveats for Cisco IOS Release 11.3 T document that accompanies these release notes. The caveats document is updated for every maintenance release and is located on Cisco Connection Online (CCO) and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 11.3 on CCO and the Documentation CD-ROM.
These release notes describe the following topics:
The Cisco AS5300 universal access server is a versatile data communications platform that provides the functions of an access server, router, and digital modems in a single modular chassis. The access server is intended for Internet service providers (ISPs), telecommunications carriers, and other service providers that offer managed Internet connections, and also medium to large sites that provide both digital and analog access to users on an enterprise network. By terminating both analog and digital calls on the same chassis simultaneously, the access server provides a clear, simple, and easy migration path from analog to digital dial access services.
This section describes the system requirements for Release 11.3 T:
Table 1 describes the memory requirements for the Cisco AS5300 feature sets for Release 11.3(11)T.
| Feature Set | Image Name | Required Flash Memory | Required DRAM Memory | Runs From |
|---|---|---|---|---|
IP | c5300-i-mz | 8 MB | 32 MB | RAM |
IP Plus | c5300-is-mz | 8 MB | 32 MB | RAM |
IP Plus 40 | c5300-is40-mz | 8 MB | 32 MB | RAM |
IP Plus IPSec 56 | c5300-is56i-mz | 8 MB | 32 MB | RAM |
Desktop | c5300-d-mz | 8 MB | 32 MB | RAM |
Desktop Plus | c5300-ds-mz | 8 MB | 32 MB | RAM |
Enterprise | c5300-j-mz | 8 MB | 32 MB | RAM |
Enterprise Plus | c5300-js-mz | 8 MB | 32 MB | RAM |
Enterprise Plus 40 | c5300-js40-mz | 8 MB | 32 MB | RAM |
Enterprise Plus IPSec56 | c5300-js56i-mz | 8 MB | 32 MB | RAM |
Cisco IOS Release 11.3(11)T supports the Cisco AS5300 universal access server. For detailed descriptions of the new hardware features, see the "New and Changed Information" section. Table 2 lists the interface and modem cards supported by the Cisco AS5300.
| Interface Cards | Modem Cards |
|---|---|
Ethernet RJ-45 | MICA modems |
Ethernet/Fast Ethernet (RJ-45) | Microcom 56K modems |
ISDN PRI |
|
E1-G.703/G.704 |
|
Channelized T1 (4 ports) without serial support |
|
Channelized E1 (4 ports) without serial support |
|
Voice over IP (VoIP) feature card (VFC) |
|
To determine the version of Cisco IOS software running on your Cisco AS5300 universal access server, log in to the Cisco AS5300 and enter the show version EXEC command.
router> show version Cisco Internetwork Operating System Software IOS (tm) 5300 Software (c5300-js-n), Version 11.3(11)T, RELEASE SOFTWARE
For information about upgrading to a new software release, see the Cisco IOS Software Release 11.3 Upgrade Paths and Packaging Simplification product bulletin located on CCO at:
Service & Support: Technical Documents: Product Bulletins: Software
Under Cisco IOS 11.3, click Cisco IOS Software Release 11.3 Upgrade Paths (#703: 12/97)
This product bulletin does not contain information specific to Cisco IOS Release 11.3 but provides generic upgrade information that may apply to Cisco IOS Release 11.3.
Table 3 lists the current microcode versions for the Cisco AS5300. 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.
The modem code release notes are on CCO and the Documentation CD-ROM:
You can reach the release notes on CCO at:
Service & Support: Technical Documents: Cisco Product Documentation: Access Servers and Access Routers: Firmware and Portware Information
You can reach the release notes on the Documentation CD-ROM at:
Cisco Product Documentation: Access Servers and Access Routers: Firmware and Portware Information
| Modem Module | Bundled Modem Code | Cisco IOS 11.3 T Software | Cisco IOS 11.3 AA Software |
Microcom modems | Microcom version 3.1.30 | Starting with 11.3(2)T, up to 11.3(4)T | 11.3(4)AA |
Microcom modems | Microcom version 3.3.20 | Starting with 11.3(5)T, up to 11.3(7)T | 11.3(5)AA and 11.3(6)AA |
Microcom modems | Microcom version 5.1.20 | 11.3(8)T, and later releases | 11.3(7)AA, and later releases |
MICA modems | MICA portware version 2.0.1.7 | Starting with 11.3(2)T, up to 11.3(4)T | 11.3(4)AA |
MICA modems | MICA portware version 2.3.1.0 | Starting with 11.3(5)T, up to 11.3(7)T | 11.3(5)AA, up to 11.3(6)AA |
MICA modems | MICA portware version 2.6.2.0 | 11.3(8)T, and later releases | 11.3(7)AA, and later releases |
The show modemcap command lists all versions of modem code running on the modem modules, residing in system Flash, and bundled with Cisco IOS software. Enter the show modemcap command to help you decide if you need to update your modem code files.
The Cisco IOS Software Upgrade Planner on CCO contains information about downloading software. To access this document from CCO, click Login on the CCO home page to access all information. From the CCO home page, go to the Software Support area, click Software Center, then Cisco IOS Software or IOS Upgrade Planner.
The modem code release notes are on CCO and on the Documentation CD-ROM:
The Cisco IOS software is packaged in feature sets consisting of software images---depending on the platform. Each feature set contains a specific set of Cisco IOS features.
Release 11.3 T supports the same feature sets as Release 11.3, but Release 11.3 T can include new features supported by the Cisco AS5300 universal access server
.
| Feature Set | Software Image Name | Feature Set Matrix Term | Image Name | Platforms |
|---|---|---|---|---|
| IP Standard | IP | Basic1 | c5300-i-mz | Cisco AS5300 |
IP Plus | Plus2 | c5300-is-mz | Cisco AS5300 | |
IP Plus 40 | Plus, Plus 403 | c5300-is40-mz | Cisco AS5300 | |
Desktop | IP Plus IPSec 56 | Plus, IPSec 564 | c5300-is56i-mz | Cisco AS5300 |
Desktop | Basic | c5300-d-mz | Cisco AS5300 | |
Desktop Plus | Plus | c5300-ds-mz | Cisco AS5300 | |
Enterprise | Enterprise | Basic | c5300-j-mz | Cisco AS5300 |
Enterprise Plus | Plus | c5300-js-mz | Cisco AS5300 | |
Enterprise Plus 40 | Plus, Plus 405 | c5300-js40-mz | Cisco AS5300 | |
Enterprise Plus IPSec56 | Plus, IPSec 566 | c5300-js56i-mz | Cisco AS5300 |
Table 5 lists the features and feature sets supported by the Cisco AS5300 universal access server in Cisco IOS Release 11.3 and uses the following conventions:
| Feature Set | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Feature | In | IP | IP Plus | IP Plus401 | IP Plus IPSec 562 | Desktop | Desk top Plus | Enterprise | Enterprise Plus | Enterprise Plus 403 | Enterprise Plus IPSec 564 |
| IBM Support |
|
|
|
|
|
|
|
|
|
|
|
APPN High-Performance Routing |
| No | No | No | No | No | No | No | No | No | No |
APPN MIB Enhancements |
| No | No | No | No | No | No | No | No | No | No |
APPN over Ethernet LAN Emulation |
| No | No | No | No | No | No | No | No | No | No |
APPN Scalability Enhancements |
| No | No | No | No | No | No | No | No | No | No |
Bisync Enhancements:
|
| No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
Cisco MultiPath Channel (CMPC) |
| No | No | No | No | No | No | No | No | No | No |
DLSw+ Enhancements:
|
| No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
FRAS Enhancements:
|
| No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
RIF Passthru in DLSw+ | (3) | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
SRB over FDDI on Cisco 4000-M, 4500-M, and 4700-M Routers |
| No | No | No | No | No | No | No | No | No | No |
TN3270 LU Nailing |
| No | No | No | No | No | No | No | No | No | No |
TN3270 Server Enhancements |
| No | No | No | No | No | No | No | No | No | No |
Token Ring LANE |
| No | No | No | No | No | No | No | No | No | No |
Tunneling of Asynchronous Security Protocols |
| No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
| Internet |
|
|
|
|
|
|
|
|
|
|
|
DRP Server Agent |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
DRP Server Agent Enhancements | (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| IP Routing |
|
|
|
|
|
|
|
|
|
|
|
Easy IP (Phase 1) |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Hot Standby Router Protocol (HSRP) over ISL in Virtual LAN Configurations |
| No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
IP Enhanced IGRP Route Authentication |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
IP Type of Service and Precedence for GRE Tunnels | (4) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
PIM Version 2 |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
TCP Enhancements:
|
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| LAN Support |
|
|
|
|
|
|
|
|
|
|
|
AppleTalk Access List Enhancements |
| No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
DECnet Accounting |
| No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
IPX Named Access Lists |
| No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
IPX SAP-after-RIP |
| No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
NLSP Enhancements |
| No | No | No | No | No | No | Yes | Yes | Yes | Yes |
NLSP Multicast Support |
| No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| Management |
|
|
|
|
|
|
|
|
|
|
|
Cisco Call History MIB Command Line Interface |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Cisco IOS Internationalization |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Entity MIB, Phase 1 |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
SNMPv2C |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
SNMP Inform Requests | (1) | No | No | No | No | No | No | Yes | Yes | Yes | Yes |
Virtual Profiles |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
VPDN MIB | (2) | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
VPDN MIB and Syslog Facility | (3) | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
| Multimedia |
|
|
|
|
|
|
|
|
|
|
|
IP Multicast Load Splitting across Equal-Cost Paths |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
IP Multicast over ATM Point-to-Multipoint Virtual Circuits |
| No | No | No | No | No | No | No | No | No | No |
PIM Version 2 | (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
IP Multicast over Token Ring LANs |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Stub IP Multicast Routing |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Quality of Service |
|
|
|
|
|
|
|
|
|
|
|
RTP Header Compression |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Security |
|
|
|
|
|
|
|
|
|
|
|
Automated Double Authentication | (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Certificate Authority Interoperability | (3) | No | No | No | Yes | No | No | No | No | No | Yes |
Double Authentication |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Encrypted Kerberized Telnet |
| No | No | No | No | No | No | No | No | No | Yes |
HTTP Security |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Internet Key Exchange Security Protocol | (3) | No | No | No | Yes | No | No | No | No | No | Yes |
IPSec Network Security | (3) | No | No | No | Yes | No | No | No | No | No | Yes |
Message Banners for AAA Authentication | (4) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
MS-CHAP Support | (3) | No | No | No | No | No | No | Yes | Yes | Yes | Yes |
Named Method Lists for AAA Authentication and Accounting | (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Per-User Configuration |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Reflexive Access Lists |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
TCP Intercept |
| No | No | No | No | No | No | Yes | Yes | Yes | Yes |
Vendor-Proprietary RADIUS Attributes |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Vendor-Proprietary RADIUS -Additional Attributes | (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Switching |
|
|
|
|
|
|
|
|
|
|
|
AppleTalk Routing over ISL and IEEE 802.10 in Virtual LANs |
| No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
CLNS and DECnet Fast Switching over PPP |
| No | No | No | No | No | No | Yes | Yes | Yes | Yes |
DECnet/VINES/XNS over ISL:
|
| No | No | No | No | No | No | Yes | Yes | No | No |
Fast-Switched Policy Routing |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
IPX Routing over ISL Virtual LANs |
| No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
VIP Distributed Switching Support for IP Encapsulated in ISL |
| No | No | No | No | No | No | No | No | No | No |
| Terminal Services |
|
|
|
|
|
|
|
|
|
|
|
Telnet Extensions for Dialout |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Virtual Templates for Protocol Translation |
| No | No | No | No | No | No | Yes | Yes | Yes | Yes |
| WAN Optimization |
|
|
|
|
|
|
|
|
|
|
|
ATM MIB Enhancements |
| No | No | No | No | No | No | No | No | No | No |
PAD Enhancements |
| No | No | No | No | No | No | Yes | Yes | Yes | Yes |
PAD Subaddressing |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| WAN Services |
|
|
|
|
|
|
|
|
|
|
|
Always On/Dynamic ISDN (AO/DI) | (3) | No | No | No | No | No | No | Yes | Yes | Yes | Yes |
Bandwidth Allocation Control Protocol |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Dialer Watch | (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
E1 R2 Country Support5 | (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
E1 R1 Support for only Taiwan6 | (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Enhanced Local Management Interface (ELMI) |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Frame Relay Enhancements |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Frame Relay MIB Extensions |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Frame Relay Router ForeSight |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
ISDN Advice of Charge |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
ISDN Caller ID Callback |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
ISDN NFAS |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Layer 2 Forwarding---Fast Switching |
| No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
Leased-Line ISDN at 128 kbps |
| No | No | No | No | No | No | No | No | No | No |
Microsoft Point-to-Point Compression (MPPC) | (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
MS Callback | (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Modem Management Enhancements | (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Multiple ISDN Switch Types | (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
National ISDN Switch Types for BRI and PRI Interfaces (NI2) | (3) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
PPP over ATM |
| No | No | No | No | No | No | No | No | No | No |
Stackable Home Gateway | (3) | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
Switched 56K Digital Connections | (2) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Telnet Extensions for Dialout | (2) | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes |
X.25 Enhancements |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
X.25 on ISDN |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
X.25 Switching between PVCs and SVCs |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
X.28 Emulation |
| Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Table 6 lists the encryption images available in Cisco IOS Release 11.3(3)T and later 11.3 T releases; they are not available in Releases 11.3(1)T and 11.3(2)T.
| Image Name | Feature Set Name | Description |
c5300-is40-mz | IP Plus 40 | New image based on the IP Plus image, with 40-bit encryption. |
c5300-is56i-mz | IP Plus IPSec 56 | New image based on the IP Plus image, with 56-bit encryption and additional features including Certificate Authority Interoperability and Internet Key Exchange Security Protocol. |
c5300-js40-mz | Enterprise Plus 40 | New image based on the Enterprise Plus image, with 40-bit encryption. |
c5300-js56i-mz | Enterprise Plus IPSec 56 | New image based on the Enterprise Plus image, with 56-bit encryption, IP Security, and additional features including Certificate Authority Interoperability and Internet Key Exchange Security Protocol. |
 | 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. |
This section lists new features available for the Cisco AS5300 for Release 11.3 T.
No new software features were introduced in Cisco IOS Release 11.3(9)T through 11.3(11)T for the Cisco AS5300.
No new software features were introduced in Cisco IOS Release 11.3(8)T for the Cisco AS5300; however, the modem code that is bundled with the Cisco IOS software was upgraded as follows to support V.90:
No new software features were introduced in Cisco IOS Release 11.3(7)T for the Cisco AS5300.
The following three new cas-custom commands are available for the Cisco AS5300 in Cisco IOS Release 11.3(6)T:
as5300_1(config-ctrl-cas)# debounce-time?
<16-40> Debounce Time in Milliseconds
as5300_1(config-ctrl-cas)# seizure-ack-time?
<2-100> Seizure to Acknowledge time in Milliseconds
as5300_1(config-ctrl-cas)# release-guard-time?
<1-2000> Release Guard Time in Milliseconds
No new software features were introduced in Cisco IOS Release 11.3(5)T for the Cisco AS5300.
The following new software features in Cisco IOS Release 11.3(4)T are available for the Cisco AS5300. For easy online access, feature modules that describe these new features are linked.
Prior to this feature, at generic route encapsulation-based tunnel endpoints, the type of service (ToS) bits (including precedence bits) were not copied to the tunnel or GRE IP header that encapsulates the inner packet. Instead, those bits were set to zero. This was not a problem unless the intermediate routers between two tunnel endpoints honored ToS or precedence bits, in which case those settings were ignored.
With the advent of virtual private network (VPN) and quality of service (QoS) applications, it is desirable to copy the ToS bits when the router encapsulates the packets using GRE. Thus, intermediate routers between tunnel endpoints can take advantage of the QoS features such as weighted fair queuing (WFQ) and weighted random early detection (WRED).
The authentication, authorization, and accounting (AAA) suite of security services now supports the use of configurable, personalized login and failed-login banners. This feature lets you change the default message for login and failed-login. You can configure message banners that will be displayed when a user logs in to the system to be authenticated using AAA and when authentication, for whatever reason, fails.
The following new software features in Cisco IOS Release 11.3(3)T are available for the Cisco AS5300.
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. 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 D channel is a connectionless, packet-oriented link between the Customer Premises Equipment (CPE) and the central office. Because the D channel is always available, it is possible to offer always available services. On-demand functionality is achieved by using the B channels to temporarily boost data throughput and then disconnecting the B channels 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 (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 introduce changes to ISDN switch types for Primary Rate Interfaces (PRIs) and Basic Rate Interfaces (BRIs) as follows:
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 Virtual Private Dial-Up Network (VPDN) Management Information Base (MIB) feature is intended to support all tables and objects defined in "Cisco VPDN Management MIB" for the user sessions of the VPDN features. There are a number of commands that 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.
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.
Certificate Authority (CA) interoperability is provided in support of the IP Security (IPSec) standard. CA interoperability permits devices running Cisco IOS software and CA devices to communicate so that devices running Cisco IOS software 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 security feature that provides robust authentication and encryption of IP packets. 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 enables applications such as virtual private networks (VPNs), extranets, and remote user access.
IPSec provides the following network security services:
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 used in conjunction with the IPSec standard. 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 that implements the Oakley key exchange inside the ISAKMP framework.
The automated double authentication feature enhances the existing double authentication feature.
Previously, with the existing double authentication feature, a second level of user authentication was achieved when the user established a Telnet connection to the network access server or router and entered 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.)
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(3)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.
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.
Remote Authentication Dial-In User Service (RADIUS) is an access server authentication, authorization, and accounting protocol originally developed by Lucent Technologies Remote Access Business Unit (formerly 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 servers into their networks more easily.
Enabling R1 modified signaling allows a Cisco AS5200 or Cisco AS5300 universal access server to talk to central office trunks that also use R1 modified signaling. R1 Signaling is an international signaling standard that is common to channelized T1/E1 networks; however, this feature is only available in Taiwan. You can configure a channelized T1/E1 interface to support different types of R1 modified signaling, which is used in older analog telephone networks.
The following new software features in Cisco IOS Release 11.3(2)T are available for the Cisco AS5300.
This is the first Cisco IOS 11.3 T release to include support for the Cisco AS5300.
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 (Local Management Interface).
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 link 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 a Microsoft proprietary protocol used by Windows 95 and Windows NT clients. MS Callback supports negotiated PPP Link Control Protocol (LCP) extensions initiated and agreed to by the Microsoft client. MS Callback is added to existing PPP Callback functionality. Therefore, if you configure your Cisco AS5300 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.
The Director Response Protocol (DRP) Server Agent enhancements are as follows:
For VPDN (Virtual Private Dial-Up Network) sessions, information on active tunnels and sessions are retrievable through Simple Network Management Protocol (SNMP) from the VPDN Management Information Base (MIB). The VPDN 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 that provide information and statistics through the command-line interface (CLI) but not SNMP; the Cisco VPDN MIB has been created to satisfy the need to provide information and statistics through SNMP.
Internet service providers can provide switched 56-kbps access to their customers using a Cisco AS5300 and an ISDN PRI or a CT1 RBS connection:
The dial-in user can access a 56-kbps data connection to the ISP using either an ISDN BRI connection or a 2- or 4-wire switched 56-kbps connection. The telco to which the access server connects must configure its switches to route 56-kbps data calls and voice (modem) calls to the appropriate DS0 (digital signal level 0). Similarly, an enterprise can provide switched 56-kbps digital dial-in services to its full-time telecommuters or small remote offices using ISDN PRI or a CT1 RBS connection.
New country support for E1 R2 signaling and modem management enhancements is added to Cisco IOS Release 11.3(2)T and later for the Cisco AS5300 access server. Only MICA modems support the R2 functionality.
Cisco Systems' R2 signaling default is ITU, which supports the following countries: Denmark, Finland, Germany, Russia (ITU variant), Hong Kong (ITU variant), and South Africa (ITU variant). The "ITU variant" means there are multiple R2 signaling types in the specified country, but Cisco supports the ITU variant. Cisco Systems also supports specific local variants of E1 R2 signaling in the following regions, countries, and corporations.
This modem management enhancement is available for Cisco AS5300 access servers using MICA modems.
You can display a snapshot of all the firmware versions running on all modems in the access server by entering the show modemcap command. This command also shows the source location of each version of firmware (for example, running out of Flash memory, boot Flash memory, or bundled with Cisco IOS software). This command is useful for managing and monitoring multiple versions of modem firmware running in an access server.
The following software feature was first introduced in Cisco IOS Release 11.3(1)T.
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 protocol data unit (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 inform requests are more reliable, they 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. However, 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.
This section contains important notes concerning Cisco IOS Release 11.3 T software that apply to the Cisco AS5300.
A new authorization feature that allows you to separately configure and authorize Multilink PPP was added in Cisco IOS Release 11.3(1). This feature can cause MLP authorization to fail in Terminal Access Controller Access Control System (TACACS+) servers that do not include authorization permissions in the configuration.
For TACACS+, add the following attribute-value (AV) pair for all users who are allowed to negotiate Multilink PPP:
service = ppp protocol = multilink {
As of Cisco IOS Release 11.3(2)T, the bridge group multicast-source command is no longer available. This command was removed to comply with the source-route-transparent (SRT) bridging implementation.
Because of a production problem, many source-route bridging commands were omitted from the printed version of Cisco IOS Software Command Summary (78-4746-XX). For documentation of all source-route bridging commands, see the Bridging and IBM Networking Command Reference (78-4743-XX). You can also obtain the most current documentation on CCO or on the Documentation CD-ROM.
Cisco IOS Release 11.3(8)T was deferred to Release 11.3(8)T1 on all software images to incorporate corrections to the following caveats:
For more information on these caveats, refer to Bug Navigator II. Bug Navigator II is available at http://www.cisco.com/support/bugtools. On CCO, log in and click this path:
Service & Support: Online Technical Support: Software Bug Toolkit: Bug Navigator II.
End of Engineering (EOE) means that there are no more regularly scheduled maintenance releases. The last maintenance release scheduled on the EOE date is only available through CCO and Field Service Operations---not through manufacturing.
EOS and EOE releases are subject to change. For the most up-to-date information on the status of EOS or EOE, see the End of Sales and End of Engineering for Cisco IOS Software Releases product bulletins located on CCO.
Ongoing support for functionality in Releases 11.3, 11.3 NA, and 11.3 T is available in Cisco IOS Release 12.0(3)T and later maintenance releases of Cisco IOS Release 12.0 on CCO at:
Service & Support: Product Bulletins: Software
Under Cisco IOS 11.3, click End of Sales and End of Engineering for Cisco IOS Software Releases 11.3 and 11.3 T (#847: 12/98) or Cisco IOS Software 11.3 NA EoS and EoE (#849:12/98)
Caveats describe unexpected behavior or defects in Cisco IOS software releases. For information on caveats in Cisco IOS Release 11.3 T, refer to the Caveats for Cisco IOS Release 11.3 T document which is located on CCO and the Documentation CD-ROM.
All caveats in Release 11.3 are also in Release 11.3 T.
For information on caveats in Cisco IOS Release 11.3, 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 which is located on CCO and the Documentation CD-ROM. These release notes list severity 1 and 2 caveats affecting all maintenance releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.
Due to a production problem, many source-route bridging commands were omitted from the printed version of the Cisco IOS Software Command Summary (part number 78-4746-01). For complete documentation of all source-route bridging commands, refer to the Bridging and IBM Networking Command Reference (part number 78-4743-01). You can also obtain the most current documentation on the Documentation CD-ROM or Cisco Connection Online (CCO).
The following sections describe the documentation available for the Cisco AS5300 universal access server. 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 Release 11. 3 and are located on CCO and the Documentation CD-ROM.
The following Cisco AS5300 documents are available:
The above documentation can be found on CCO and on the Documentation CD-ROM:
Feature modules describe new features supported by Release 11.3 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.
You can reach the feature modules on CCO at:
Service & Support: Technical Documents: Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 11.3: Release Notes for Cisco IOS Release 11.3: New Features in Release 11.3
You can reach the feature modules on the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 11.3: Release Notes for Cisco IOS Release 11.3: New Features in Release 11.3
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents, which are shipped with your order in electronic form on the Documentation CD-ROM---unless you specifically ordered the printed versions.
Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide with its corresponding command reference.
On CCO and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
You can reach these documents on CCO at:
Service & Support: Technical Documents: Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 11.3: Cisco IOS Release 11.3 Configuration Guides, Command References: Configuration Guide Master Index or Command Reference Master Index
You can reach these documents on the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 11.3: Cisco IOS 11.3 Configuration Guides, Command References: Configuration Guide Master Index or Command Reference Master Index
Table 7 describes the contents of the Cisco IOS Release 11.3 software documentation set, which is available in electronic form and also in printed form upon request.
You can reach the Cisco IOS documentation set from CCO at:
Service & Support: Technical Documents: Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 11.3
You can reach the Cisco IOS documentation set on the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 11.3
| Books | Chapter Topics |
|---|---|
| Configuration Fundamentals Overview |
| IP Addressing |
| AppleTalk |
| Apollo Domain |
| ATM |
| AAA Security Services |
| Interface Configurations |
| Dial-In Port Setup |
| Switching Paths for IP Networks |
| Transparent Bridging |
| Voice over IP |
| Classification |
|
|
|
|
For service and support for a product purchased from a reseller, contact the reseller, who offers a wide variety of Cisco service and support programs described in "Service and Support" of Cisco Information Packet shipped with your product.
For service and support for a product purchased directly from Cisco, use CCO.
If you have a CCO login account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com/kobayashi/serv_tips.shtml
This URL is subject to change without notice. If it changes, point your Web browser to CCO and click on this path: Products & Technologies: Products: Technical Tips.
The following sections are provided from the Technical Tips page:
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can reach CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which package that ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Tue Jul 27 13:53:56 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.