|
|
The following sections list the new features supported in Cisco IOS Release 12.1.
For additional information regarding the features supported in Cisco IOS Release 12.1, please refer to the feature-specific information at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/index.htm
The following features are supported in Cisco IOS Release 12.1.
The authentication, authorization, and accounting (AAA) Server Group feature introduces a way to group the existing server hosts. The Server Group feature allows the user to select a subset of the configured server hosts and use them for a particular service.
A Server Group is a list of server hosts of a particular type. Currently supported server hosts types are RADIUS server hosts and TACACS+ server hosts. A server-group is used in conjunction with a global server host list. The server group lists the IP addresses of the selected server hosts. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/serv_grp.htm
The Cisco uBR7200 series universal broadband routers contain the following additional or changed show commands:
The Airline Product Set Enhancements feature, ALPS phase III, provides support for Mapping of Airline Traffic over Internet Protocol (MATIP). MATIP is an industry standard protocol for transporting airline protocol traffic across a TCP/IP network. This feature enables the end-to-end delivery of ALC and UTS data streams between a Cisco router and the mainframe using TCP/IP. This feature removes the X.25 (AX.25 or EMTOX) requirements for communication with the host reservation system by enabling TCP/IP communication between the router and the airline host reservation system. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/alpmatip.htm
Occasionally, a headend cable router drops modems that have low carrier-to-noise ratios. This situation can occur when the headend router is making excessive power adjustments in response to RNG-RSP messages from affected modems. This feature allows you to set the cable access router so that it averages a configurable number of RNG-RSP messages before making power adjustments.
The show cable flap and show cable modem commands have been enhanced to show where the cable router is making power adjustments. Users can interpret these power adjustments as indicating an unstable return path connection.
Users can now configure cable access router power adjustments to optimize cable operations under less than ideal conditions. Users can also identify where the cable access router is making power adjustments and service the affected paths. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/ampliavg.htm
Annex G (X.25 over Frame Relay) facilitates the migration from an X.25 backbone to a Frame Relay backbone by permitting encapsulation of Consultative Committee for International Telegraph and Telephone (CCITT) X.25/X.75 traffic within a Frame Relay connection. Annex G has developed to accommodate the many Cisco customers in Europe, where X.25 still is a popular protocol. With Annex G, the process of transporting X.25 over Frame Relay has been simplified, by allowing direct X.25 encapsulation over a Frame Relay network.
This simple process is largely achieved using X.25 profiles (similar to dialer profiles), which were created to streamline the configuration of X.25 on a per-data-link connection identifier (DLCI) basis. X.25 profiles can contain any existing X.25 command and, once created and named, can be simultaneously associated with more than one Annex G DLCI connection, just using the profile name. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/x25anxg.htm
The Asynchronous Serial Traffic over User Datagram Protocol (UDP) feature provides the ability to encapsulate asynchronous data into UDP packets, and then unreliably send this data without needing to establish a connection with a receiving device.
You load the data you want to send through an asynchronous port, and then send it, optionally, as a multicast or a broadcast. The receiving devices can then receive the data whenever they want. If the receiver ends reception, the transmission is unaffected.
This process is referred to as UDP Telnet (UDPTN), although it does not (and cannot) use the Telnet protocol. UDPTN is similar to Telnet in that both are used to send data, but UDPTN is unique in that it does not require that a connection be established with a receiving device. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/asyncudp.htm
To improve the ATM LAN Emulation (LANE) Simple Server Redundancy Protocol (SSRP), Cisco has introduced the ATM LANE Fast Simple Server Redundancy Protocol (FSSRP). FSSRP differs from LANE SSRP in that all configured LANE servers of an emulated LAN (ELAN) are always active. FSSRP-enabled LANE clients have VCs linked to up to four LANE server broadcast-and-unknown servers (BUSs). If a LANE server goes down, the LANE client quickly switches over to a new LANE server and BUS, resulting in no data or LAN Emulation Address Resolution Protocol (LE-ARP) table entry losses and no extraneous signalling. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/fssrp.htm
The ATM PVC Trap Support feature provides Simple Network Management Protocol (SNMP) notification for permanent virtual circuit (PVC) failures, and it provides SNMP access to PVC status tables.
Normally, a management station is not notified when an ATM PVC goes down. The ATM PVC Trap Support feature enables an agent to send the required PVC traps for this notification. It also provides support for these PVC status tables: atmCurrentlyFailingPVclTable and atmInterfaceExtTable. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/pvctrap.htm
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 connects to the network access server or router using Telnet and enters a username and password. Now, with Automated Double Authentication, the user need not use Telnet but instead responds to a dialog box that requests a username and password or PIN.
The Baseline Privacy MIB, as currently defined, is now available in Cisco IOS Release 12.1. BPI allows an SNMP manager to monitor and manage the Cisco uBR924 cable access router BPI configuration, including whether BPI is enabled, status of current authorization keys, current timeout values, real-time status counters, and additional information about authorization errors.
 |
Note The SNMP manager must load the DOCSIS-BPI-MIB.my MIB to access the BPI attributes. |
The PA-A3 port adapters were introduced in Cisco IOS Release 11.1(19)CC. With Release 12.1, they now support Basic Cisco LAN Emulation (LANE) support based on ATM Forum LANE Specification 1.0. This basic LANE support includes IP and IPX protocols only. This LANE support does not include Cisco IOS Release 11.2 or 11.3 Cisco ATM or LANE features such as UNI 3.1, SSRP, Hot Standby Router Protocol (HSRP), and so on. Extended AppleTalk is not supported over LANE in this release.
The Basic Wiretap Support feature provides support for a basic wiretap facility for VoIP calls, as required by the United States Federal Communications Assistance for Law Enforcement Act (CALEA). The wiretap facility is based on the MAC address of the cable modem, so it can be used for either data or digitized voice connections.
The feature is controlled by the new interface command, cable intercept, which requires a MAC address, an IP address, and a UDP port number as its parameters. When activated, the Cisco uBR7200 series universal broadband router examines each packet for the desired MAC address; when a matching MAC address is found (for either the origination or destination endpoint), a copy of the packet is encapsulated into a UDP packet, which is then sent to the specified server at the given IP address and port.
Cisco bit error rate tester (BERT) solution and time-division multiplexing (TDM) command enhancements have been implemented for the Cisco AS5300 in Cisco IOS Release 12.0(2)XD and 12.0(3)T. This enhancement has been applied for T1 and E1 facilities. The BERT solution can be managed from remote command-line interface (CLI) and SNMP management platforms for any Cisco AS5300 in the network. A loopback LED on the Cisco AS5300 chassis blinks slowly to indicate that BERT is in progress and blinks rapidly if the test fails. Bit error rate testing and loopbacks are used by carriers and Internet Service Providers (ISPs) to aid in problem resolution and to test the quality of T1/E1 links. By early detection of poor quality links and fast problem isolation, Cisco AS5300 users can improve their quality of service and increase their revenue. The TDM subsystem troubleshooting commands are not used during normal system operation. Instead, the Cisco IOS commands show the current status and settings of the TDM backplane, enable debug output for display to the user when TDM programming occurs, and provide a set of test commands to test the functionality of the TDM path.
Because both routers within Cisco 7576 are totally independent, there is no software dependency between them. This feature allows customers to install and test updated versions of Cisco IOS software on one router before deployment.
All existing Cisco 7500 series Interface Processor modules, Versatile Interface Processor modules, and their port adapters are fully compatible with the Cisco 7576 router. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/5300bert.htm
For each modulation/burst profile configuration, Cisco uBR7200 series universal broadband routers will support burst profile number, burst profile interval usage code, burst type, preamble length and unique word length, differential encoding enable/disable, forward error correction (FEC) correctable bytes value, FEC code word length, scrambler seed value, maximum burst size, guard time size, last code word shortened/lengthened, and scrambler enable/disable.
|
Note Multiple burst profiles are supported on the MC11C, MC12C, MC14C, MC16B, and MC16C cable access router cards. Only one profile is supported on the original MC11-FPGA card. |
The Busyout Monitor feature is one aspect of connection admission control (CAC) that allows network administrators to use both a data network and the Public Switched Telephone Network (PSTN) to provide the best possible quality for Voice over IP (VoIP) calls. Although voice calls are routed across the data network whenever possible to take advantage of the cost savings provided by integrated applications, the Busyout Monitor feature allows network administrators to provide voice services through the PSTN in the event of a network interface failure.
If a locally connected LAN or WAN interface on a VoIP gateway fails, it busies out voice ports, which means that a connected PBX or key system reroutes the call through the local PSTN. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/busy_t7.htm
The Cable Device MIB feature is for DOCSIS-compliant cable access routers and CMTS. The Cable Device MIB records statistics related to the configuration and status of the Cisco uBR924 cable access router. Statistics include an events log and device status. The following list details the components of the Cable Device MIB feature:
The Cable Device MIB feature is very similar to the RFI MIB in that both allow access to statistics; they are different in that the Cable Device MIB reports statistics on the Cisco uBR924 cable access router, and the RFI MIB reports statistics on the radio frequency transmissions over the cable television line.
The Call Detail Records (CDR) feature provides the ability to track records for calls being processed by the Cisco MC3810. CDR data is collected for all plain old telephone service (POTS) call attempts, and the data is collected for each call leg and also by each Cisco MC3810 involved in the call session.
The call legs for which CDR data is collected are as follows:
CDR data is stored in an internal buffer on the Cisco MC3810 at call termination time, and becomes available to be polled periodically by the Cisco network management system (NMS) applications. The CDR/call history entries cannot be retrieved after a power loss or a software reload on the Cisco MC3810, so the Cisco NMS is considered the final destination for storing and tailoring the CDR call history table into report form. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t2/cdrfm.htm
Some switches do not include a called party number when they send a voice call to a Cisco 800 router. These calls are directed to port 1 by default.
The Called Party Number Port feature allows the router to direct calls of this type to a specified port. When this feature is combined with the command forward-to-unused-port, the router can direct a second call to the same port as the first call or to another port. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/dircall.htm
The Cisco Discovery Protocol (CDP) is a media-independent device discovery protocol that runs on all cisco manufactured equipment, including routers, bridges, access servers, and switches. Each device sends periodic messages to a multicast address. Each device listens to the periodic messages sent by others in order to learn about neighboring devices and determine when their interfaces to the media go up or down. With CDP, network management applications can learn the device type and the SNMP agent address of neighboring devices. This process enables applications to send SNMP queries to neighboring devices.
CDP runs on all media that support Subnetwork Access Protocol (SNAP), including LAN, Frame Relay, and ATM media. CDP runs over the data link layer only. Therefore, two systems that support different network-layer protocols can learn about each other.
Each device configured for CDP sends periodic messages to a multicast address. Each device advertises at least one address at which it can receive SNMP messages. The advertisements also contain time-to-live, or hold-time, information, which indicates the time a receiving device should hold CDP information before discarding it.
Additions for CDP include the following:
The benefits include the following:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/cdpadds.htm
The Cisco Dial-Out Utility feature is now supported on the Cisco AS5300 when MICA technologies modem portware version 2.5.1.0 is used. The Cisco Dial-Out Utility is a COM port redirector that utilizes a protocol defined in RFC 2217 for communications between the client PC and a dial NAS.
Cisco Express Forwarding (CEF) is advanced Layer 3 IP switching technology. CEF optimizes network performance and scalability for networks with large and dynamic traffic patterns, such as the Internet, networks characterized by intensive Web-based applications, or interactive sessions. Although you can use CEF in any part of a network, it is designed for high-performance, highly resilient Layer 3 IP backbone switching.
The Cisco H.323 gateway now supports the use of CryptoH323Tokens for authentication. The CryptoH323Token is defined in H.225 Version 2 and is used in a "password-with-hashing" security scheme as described in section 10.3.3 of the H.235 specification.
A cryptoToken can be included in any registration, admission, and status protocol (RAS) message and is used to authenticate the sender of the message. You can use a separate database for user ID and password verification.
With this release, Cisco H.323 gateways support three levels of authentication:
You can configure the level of authentication for the gateway using the Cisco IOS software CLI.
CryptoTokens for registration request (RRQ), unregistration request (URQ), disengage request (DRQ) and the terminating side of ARQ messages contain information about the gateway that generated the token, including the gateway ID (which is the H.323 ID configured on the gateway) and the gateway password. CryptoTokens for the originating side ARQ messages contain information about the user that is placing the call, including the user ID and PIN. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/0242call.htm
The Cisco H.323 Multizone Enhancements feature enables the Cisco gateway to provide information to the gatekeeper with the use of additional fields in the registration, admission, and status protocol (RAS) messages.
Previously, the source gateway attempted to set up a call to a destination IP address as provided by the gatekeeper in an Admission Confirm (ACF) message. If the gatekeeper was unable to resolve the destination E.164 phone number to an IP address, the incoming call was terminated.
This version of the H.323 software adds support to allow a gatekeeper to provide additional destination information and modify the destinationInfo field in the ACF. The gateway will include the canMapAlias associated destination information in setting up the call to the destination gateway.
In conjunction with the canMapAlias functionality, this version includes support for the gatekeeper to indicate to the gateway that the call should be destined to a new E.164 number. The gatekeeper indicates this situation by sending an ACF message with an IP address of 0.0.0.0 in the destCallSignalAddress field and the new destination E.164 phone number in the destinationInfo field.
The gateway receiving such an ACF will fall back to routing the call based on this new E.164 address and performing a re-lookup of the gateway's configured dial plan. This might result in the call being routed back to the PSTN or to an H.323 endpoint. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/0244_v2.htm
Cisco uBR7200 series universal broadband routers support the Cisco IOS Firewall feature, which is available in selected Cisco IOS Release 12.0(5)T and later images. This feature set offers Network Address Translation (NAT) and is designed to prevent unauthorized, external access to your internal network, blocking attacks on your network, while still allowing authorized users to access network resources. This feature is described in detail in the Cisco IOS Firewall Feature Set feature module, available on the Documentation CD-ROM and CCO.
The Cisco IOS Firewall feature set, available for a wide range of Cisco router platforms, adds greater depth and flexibility to existing Cisco IOS software security capabilities, enriching features such as authentication, encryption, and failover with robust firewall functionality and intrusion detection. A Cisco IOS software-based, integrated firewall solution scales to meet the bandwidth and performance requirements of any network. It also maximizes a Cisco router investment by combining multiprotocol routing functionality with sophisticated security policy enforcement throughout the network.
The Cisco IOS Firewall feature set delivers cost-effective perimeter security packaged with advanced features such as stateful, application-based filtering, dynamic per-user authentication and authorization, defense against network attacks, Java blocking, and real-time alerts. Because it is completely interoperable with Cisco IOS software features including NAT, VPN tunneling protocols, CEF, AAA extensions, Cisco encryption technology, and Cisco IOS IPSec, is a complete, integrated VPN solution. Refer to the following documents for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/iosfw2/
Cisco IOS IEEE 802.1Q provides support for IEEE 802.1Q encapsulation for Virtual LANs (VLANs). Use this feature for VLANs consisting of IEEE 802.1Q compliant switches. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/8021q.htm
Cisco IOS Spanning-Tree Protocol (STP) enhancements broaden the original Cisco IOS STP implementation with increased port identification capability, improved path cost determination, and support for a new VLAN bridge spanning-tree protocol. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/stpenh.htm
For locations terminating a large number of voice channels, the Cisco IGX provides scalability for a network design in which connections can be made between remote Cisco MC3810 concentrators.
Cisco MC3810—IGX 8400 Interworking allows the Cisco IGX 8400 to be used as a larger, central site access device that can provide the following services:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t2/igxinwfm.ht m
Cisco Multipath Channel+ (CMPC+) is the Cisco implementation of the IBM MPC+ feature. The CMPC+ feature in Cisco IOS Release 12.0(3)T supports MPC+ features and protocols necessary to support IP. CMPC+ enables High Performance Data Transfer (HPDT). It allows TCP/IP connections to the host through Cisco Mainframe Channel Connection (CMCC) adapters, using either the TCP/IP stack or the High Speed Access Services (HSAS) IP stack. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/cmpcplus.ht m
The Cisco Resource Pool Manager (RPM) feature enables telephone companies and ISPs to share dial resources for wholesale and retail dial network services. With RPM, telcos and ISPs can count, control, and manage dial resources and provide accounting for shared resources when implementing different service-level agreements. Resource pool management can be configured in a single, standalone Cisco network access server using RPM or, optionally, across multiple network access server stacks using one or more external Cisco Resource Pool Manager Servers. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/rpm1205t.ht m
Cisco Secure Integrated Software (Cisco Secure IS, previously known as the Cisco IOS Firewall Feature Set) enhancements provide audio, video, and multimedia application support.
The Cisco Secure IS H.323 v2 and RTSP inspection feature provides firewall support for multimedia applications that require delivery of data with real-time properties such as audio and video conferencing. Cisco Secure IS has been enhanced to inspect these multimedia application protocols:
RTSP is the IETF standards-based protocol (RFC 2326) for controlling the delivery of real-time data, such as audio and video streams. It is useful for large-scale broadcasts and audio or video on-demand streaming, and is supported by a variety of vendors of streaming audio and video multimedia, including Cisco IP/TV, RealNetworks RealAudio G2 Player, and Apple QuickTime 4 software.
H.323 is an International Telecommunications Union (ITU) recommendation that sets standards for multimedia communications including audio and video conferencing. Cisco Secure IS supports H.323 inspection, including H.323 Version 2 and H.323 Version 1. H.323 V2 provides additional options over H.323 V1, including a "fast start" option. H.323 V2 inspection is backward compatible with H.323 V1. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/fw_rtsp.htm
The Cisco Standard MIBs consists of the following components:
The Cisco Transaction Connection (CTRC) software feature provides the following functionality:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/ctrcfc2.htm
The Cisco Voice MIB featue has the following components:
The 12.0(3)T enhancements to the Cisco uBR7246 cable router extend and improve the command line interface (CLI). It supports burst profile, quality of service (QoS), improved parameter configuration, the MC11 modem card, and the MC16 modem card. Downstream QoS handling is compliant with Multimedia Cable Network System (MCNS) requirements, and upstream QoS handling and Spectrum Management have been improved.
The Cisco uBR7246 now supports multicast authentication via RADIUS, and security has been enhanced for baseline privacy (including MCNS Data Over Cable System Interface Specification (DOCSIS) compliance). Also, this cable router now supports Dynamic Host Configuration Protocol (DHCP) Relay Subscriber ID Insertion. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/7246_12.htm
The Class-Based Weighted Fair Queueing (CBWFQ) feature extends the standard WFQ functionality to provide support for user-defined traffic classes. For CBWFQ, you define traffic classes based on match criteria including protocols, access control lists (ACLs), and input interfaces. Packets satisfying the match criteria for a class constitute the traffic for that class. A queue is reserved for each class, and traffic belonging to a class is directed to the queue of that class. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/cbwfq.htm
The Command-Line Interface (CLI) String Search feature allows you to search or filter any show or more command output. This ability is useful when you need to sort though large amounts of output, or if you want to exclude output that you do not need to see. CLI String Search also allows for searching and filtering at --More-- prompts. This new capability is supported in Cisco IOS Release 12.1.
With the search function, you can begin unfiltered output at the first line that contains a regular expression you specify. You can then specify a maximum of one filter per command or start a new search from the --More-- prompt.
A regular expression is a pattern (a phrase, number, or more complex pattern) the CLI String Search feature matches against show or more command output. Regular expressions are case sensitive and allow for complex matching requirements.
You can perform two types of filtering:
You can then search this filtered output at the --More-- prompts.
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/cliparse.htm
Cisco Networking Services (CNS) Client feature for Cisco IOS software enables authenticated directory access. CNS Client for Cisco IOS software includes the following components:
LDAP V.3 client functionality enables Cisco IOS software-based applications to securely authenticate to a CNS for Active Directory (CNS/AD) server using Kerberos V.5 as security protocol to retrieve or store information such as policy and configuration data. Cisco IOS software-based applications publish or subscribe to events using CNS event services client, enabling external applications using the application programming interface (API) features of CNS to receive events or publish events to the Cisco IOS device. This Cisco IOS software-based device will use CNS locator services client to locate the nearest directory server using Domain Name System. The administrator need not configure the device to locate the nearest directory server.
All the above-mentioned functionality is intended for use by internal Cisco IOS application developers. CNS IPSec VPN provisioning agent enables the router to retrieve IPSec policies stored in the CNS/AD server and configure itself, automating the provisioning of customer premises equipment devices for IPSec VPN. CNS provisioning agent enables Cisco IOS device to be provisioned using CNS event services.
The Cisco uBR7200 series universal broadband router can use Committed Access Rate (CAR) policies to control the traffic exceeding its allocated bandwidth. This feature uses token bucket filters to measure the traffic load and limit sources, at either the network ingress or egress, to the allocated bandwidth.
Cisco IOS Release 12.0(2)T introduces support for three new Common Channel signalling (CCS) features that are described in the following sections.
This release adds support for QSIG, which is a Private Integrated Services Network Exchange (PINX) signalling protocol that provides connectivity between PINXs in a corporate environment. Using the ISDN PRI QSIG Voice signalling feature, the Cisco MC3810 can be used as an access device to allow corporate PINX networks at remote sites to be interconnected via a data network (WAN). The Cisco MC3810 QSIG software allows incoming voice calls from a PINX to be routed across the WAN to a destination PINX. The Cisco MC3810 is responsible for establishing the necessary connection to the peer Cisco MC3810 across the WAN where both signalling and voice packets can be transported on behalf of the PINXs.
The Cisco MC3810 also performs intelligent functions such as call routing to other Cisco MC3810 concentrators in the WAN (for example, tandem switching) and interworking with other types of signalling already supported on the Cisco MC3810. Transport of Supplementary Services transparent through the network is also supported.
This release adds support for Common Channel Signalling (CCS) frame forwarding, which enables the Cisco MC3810 digital voice module (DVM) to connect two CCS private integrated services network exchanges (PINXs) without needing to interpret CCS signalling information for call processing. This feature provides transparent CCS frame forwarding for PBXs that use proprietary forms of CCS. CCS frame forwarding forwards CCS messages by encapsulating them in either Frame Relay or ATM.
With CCS frame forwarding, the voice connections between PBXs over the network are configured as point-to-point links. voice activity detection (VAD) detects when a call is in progress.
This release adds support for transparent CCS, which provides point-to-point PINX connection capability to Cisco MC3810 DVM interfaces when the PINX does not support QSIG, or when the PINX has a proprietary solution.
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t2/ccsfm.htm
The compress interface configuration command has been modified to provide added functionality for Link Access Procedure, Balanced (LAPB), PPP, and High-Level Data Link Control (HDLC) encapsulations on Cisco 7000 series routers with RSP7000, Cisco 7200 series, and Cisco 7500 series routers. The compress command enhancements allow users to configure LAPB, PPP, and HDLC encapsulations based on throughput versus compression ratios. The ratio command adjusts throughput versus compression ratios.
This feature provides configuration commands that allow you to create downstream test signals. Both PRBS and unmodulated carrier test signals are now supported. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t4/downchan.ht m
In past Cisco IOS releases, RADIUS hosts were uniquely identified by their IP addresses; therefore, only one definition of a RADIUS server for each IP address was allowed. The Configuring RADIUS for Multiple UDP Ports feature expands RADIUS implementation so that RADIUS security servers are identified by their IP addresses and specific UDP port numbers. The combination of the IP address and UDP port number creates a unique identifier, allowing different ports to be individually defined as RADIUS hosts providing a specific AAA service. In other words, this unique identifier enables RADIUS requests to be sent to different UDP ports on a server at the same IP address. If two different host entries on the same RADIUS server are configured for the same service—for example, accounting—the second host entry configured acts as failover backup to the first one. Using this example, if the first host entry fails to provide accounting services, the network access server tries the second host entry configured on the same device for accounting services. (The RADIUS host entries are tried in the order that they are configured.)
The Configuring RADIUS for Multiple UDP Ports feature also applies to RADIUS server groups. Server groups can now include multiple service definitions for host entries for the same server, as long as each entry has a unique identifier. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/rad_udp6.htm
The registration timeout parameter is now configurable. Users can now configure the uBR7200 to eliminate conflicts with other timeouts such as Trivial File Transfer Protocol (TFTP) download timeouts.
The MC16E line card for the uBR7200 series cable router can switch between Annex A and Annex B without switching upconverters.
The uBR7200 series cable router now supports the RF interface MIB RFC 2670.
The Debit Card feature provides:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/cfios/cfselfea/0134bowi.htm
The Debit Card feature allows service providers to offer calling service with debit accounting. The Debit Card feature and RADIUS-specific enhancements also support Vendor-Specific Attributes (VSA). The Debit Card for Packet Telephony feature on the Cisco AS5300 works in tandem with the Cisco IVR feature. The IVR voice scripts have been modified to use TCL scripts.
The feature components consist of IVR functionality in Cisco IOS software that works in connection with an integrated third-party billing system, including the ability to maintain per-user credit balance information through a RADIUS interface to the Cisco IOS software. When these features are implemented, the billing system and Cisco IOS software functions enable a carrier to authorize voice calls and to debit individual user accounts in real time at the edges of a voice over IP network, without requiring external service nodes.
The default routes feature can be used to reduce the number of dial peers to be configured. It is designed for situations where, for example, the ports on a Cisco MC3810 have extension numbers, but all calls not terminating on those extensions should be sent to a central Cisco MC3810, usually for forwarding to a PBX. Instead of defining all the number blocks that can be called, the default route is a dial peer that automatically matches any call not terminated by other dial peers on the Cisco MC3810.
The DHCP Client ID/Remote ID Options feature, which is also known as the CPE Limitation, allows Cisco uBR7200 series universal broadband routers to report and limit the number of CPE devices that can use the cable modem to access the cable network.
|
Note This feature is separate from the cable modemability to support multiple CPE devices. For example, depending on the Cisco IOS software release being used, Cisco uBR900 series cable access routers can support a maximum of either 3 or 254 CPE devices. Also, by default, a DOCSIS-compliant cable modem supports one CPE device, but this situation can be changed by modifying the MAX CPE parameter in the DOCSIS configuration file of the modem. |
The DHCP Cable Modem Host ID—also known as Cable Modem and Host Subnet Addressing—allows the Cisco uBR7200 series universal broadband router to set the GIADDR field of DHCPDISCOVER and DHCPREQUEST packets with a Relay IP address to help automate the provisioning of cable modems on systems that use multiple IP subnets. The cable dhcp-giaddr [policy | primary] command enables this feature on a per-interface basis.
Cisco DistributedDirector provides dynamic, transparent, and scalable Internet traffic load distribution between multiple topologically dispersed servers. DistributedDirector is the only global Internet service scaling solution that utilizes Cisco IOS software and leverages routing table information in the network infrastructure to make "network intelligent" load distribution decisions.
Using routing table intelligence in the network infrastructure, DistributedDirector transparently redirects end-user service requests to the closest responsive server, as determined by client-to-server topological proximity or client-to-server response times, resulting in increased access performance seen by the end user and reduced transmission costs.
In a network with multiple capable paths, the DLSw+ Load Balancing Enhancements feature improves traffic load balancing between peers by distributing new circuits based on existing loads and the desired ratio.
For each capable peer (peers that have the lowest or equal cost specified), the DLSw+ Load Balancing feature calculates the difference between the desired and the actual ratio of circuits being used on a peer. It detects the path that is underloaded in comparison to the other capable peers and assigns new circuits to that path until the desired ratio is achieved. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/loadbal.htm
The DLSw+ Ethernet Redundancy feature provides redundancy in an Ethernet environment. It enables DLSw+ to support parallel paths between two points in an Ethernet environment, ensuring resiliency in the case of a router failure and providing load balancing for traffic load.
DLSw+ could provide redundancy prior to this feature in a Token Ring environment or via backup peers. When an end station on an Ethernet LAN had multiple active paths into a DLSw+ network, problems occurred.
Redundancy is not possible in an Ethernet environment because, unlike Token Ring, it does not have a RIF in its packet. The RIF notifies a router of the path a packet has traveled by tracking each ring number and bridge it travels along a path. If a bridge notices that the next ring matches a ring already in the RIF, then the frame is not copied on to that ring. The RIF prevents unreliable local reachability information, circuit contention, and undetected looping explorers. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/ethredu.htm
The DLSw+ Peer Clusters feature reduces the explorer packet replication that typically occurs in a large DLSw+ Peer Group design, where multiple routers are connected to the same LAN.
The DLSw+ Peer Clusters feature associates DLSw+ peers (that are connected to the same LAN) with logical groups. Once the multiple peers are defined in the same peer group cluster, the DLSw+ border peer recognizes that it need not forward explorers to more than one member within the same peer group cluster. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/cluster.htm
The DLSw+ Resource Reservation Protocol (RSVP) Bandwidth Reservation feature allows DLSw+ to reserve network bandwidth for the DLSw+ TCP connection between DLSw+ peers.
Although it has been possible in the past to reserve bandwidth for a particular existing DLSw+ peer connection through the RSVP CLI support in Cisco IOS software, the CLI required prior knowledge of the TCP ports for which the reservation was being made. Because DLSw+ uses one well-known port and one randomly assigned port, the reservation could not be made until after the peer connection was active.
The DLSw+ RSVP feature permits new DLSw+ peer connections to automatically request bandwidth reservations upon connection, thereby removing the need for user intervention after the peer is connected. This feature assures that the reservation will survive a network or device failure and that the DLSw+ traffic carried over a TCP connection is not affected by congestion. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rsvp.htm
Managing a large TCP/IP network requires accurate and up-to-date maintenance of IP addresses and X.121 address mapping information on each router database in the network. Currently, this data is managed manually. Because these addresses are constantly being added and removed in the network, the routing table of every router frequently needs to be updated, which is a time-consuming and error-prone task.
X.25 has long operated over an IP network, specifically using TCP as a reliable transport mechanism. This method is known as X.25 over TCP (XOT). However, large networks and financial legacy environments experienced problems with the amount of route configuration that needed to be performed manually because each router switching calls over TCP needed every destination configured. Every destination from the host router needed a static IP route statement, and for larger environments, these destinations could be as much as several thousand per router. Until now, the only way to map X.121 addresses and IP addresses was on a one-to-one basis using the x25 route x121address xot ipaddress command.
The solution to this problem was to centralize route configuration that routers could then access for their connectivity needs. This centralization is the function of the DNS-Based X.25 Routing feature, because the DNS server is a database of all domains and addresses on a network. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/x25dns.htm
The Cisco uBR7200 series universal broadband routers support quality of service (QoS) as defined by the DOCSIS 1.0 specification. Service class profiles can be configured through the CLI to support the QoS profile number, traffic priority, maximum upstream bandwidth, guaranteed upstream bandwidth, maximum downstream bandwidth, maximum transmit burst length, baseline privacy enable/disable, and type of service (ToS) overwrite byte.
The QoS Profile Enforcement feature allows cable modem termination system (CMTS) operators to control the QoS to eliminate any interference from improper local-rate limiting implemented on the cable modem. The CMTS provisions a registering cable modem with a default DOCSIS 1.0 service class assigned by the operator, overriding any service class that previously existed on the modem. This service class has no upstream or downstream rate limits, so that the CMTS can do traffic shaping based on the QoS profile enforced by the operator.
As part of this support, Cisco uBR7200 series universal broadband routers support multiple service classes per cable modem by providing multiple QoS SIDs, which allows the Cisco uBR7200 series CMTS to dynamically allocate and delete service flows for voice and fax transmissions.
The following commands are available on the Cisco uBR7200 to update the QoS table:
The DOCSIS Baseline Privacy feature is based on the DOCSIS Baseline Privacy Interface Specification. It provides data privacy across the hybrid fiber-coaxial (HFC) network by encrypting traffic flows between the Cisco uBR924 cable access router and the cable operator CMTS.
Baseline Privacy security services are defined as a set of extended services within the DOCSIS MAC sublayer. Two new MAC management message types, BPKM-REQ and BPKM-RSP, are employed to support the Baseline Privacy Key Management (BPKM) protocol.
The BPKM protocol does not use authentication mechanisms such as passwords or digital signatures; it provides basic protection of service by ensuring that a cable modem, uniquely identified by its 48-bit IEEE MAC address, can only obtain keying material for services it is authorized to access. The Cisco uBR924 cable access router is able to obtain two types of keys from the CMTS: the traffic exchange key (TEK), which is used to encrypt and decrypt data packets, and the key exchange key (KEK), which is used to decrypt the TEK.
For more information on this feature, refer to the DOCSIS Baseline Privacy Interface Specification (SP-BPI-IO1-970922).
The Downstream Channel ID feature allows all cable modems in an HFC network to identify themselves via unique downstream channel IDs instead of their downstream frequencies.
The Downstream Frequency Override feature allows Cisco uBR7200 series universal broadband routers to change the downstream frequency for any or all cable modems, overriding the DOCSIS configuration file settings.
Cisco uBR7200 series routers support downstream data rate shaping on a per-modem basis. The ToS bits in the IP packet header can be set to specify the class of service for that packet, allowing packets for certain traffic flows (such as VoIP) to be given precedence over packets for other flows (such as data).
Downstream rate shaping with ToS bits allows you to configure multiple data rates for a given modem. Also, by specifying a maximum data rate for a particular ToS, you can override the common maximum downstream data rate. Packets that contain ToS bytes that have not been configured for downstream data rates continue to use the common data rate limits.
Prior releases set the ToS bits to zero; however, with the advent of Virtual Private Network (VPN) and QoS applications, it is desirable to copy the ToS bits when the router encapsulates the packets using generic routing encapsulation (GRE). Thus, intermediate routers between tunnel endpoints can also take advantage of QoS features such as weighted fair queueing (WFQ) and Weighted Random Early Detection (WRED). Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/tosbit.htm
The Dynamic Multiple Encapsulations feature allows incoming calls over ISDN to be assigned an encapsulation type such as PPP, X.25, and ISDN Link Access Procedure, Balanced-terminal adapter (LAPB-TA) based on calling line identification (CLID) or Dialed Number Identification Service (DNIS). It also allows various encapsulation types and per-user configurations on the same ISDN B channel at different times according to the type of incoming call.
The Dynamic Multiple Encapsulations feature allows per-user configuration for each dial-in caller on any ingress ISDN B channel on which encapsulation can be run independently from other B channels on the same ISDN link. The caller is identified by CLID or DNIS to make sure that only incoming calls with authorization and valid user profiles are accepted. If the protocol is PPP, authentication and profile binding can also be done by PPP name.
Dynamic multiple encapsulations are especially important in Europe where ISDN is relatively inexpensive and it is desirable to allow maximum use of all B channels on the same ISDN link, especially for large-scale dial-in. Further, the feature removes the need to statically dedicate channels to a particular encapsulation and configuration type, and improves channel usage.
Although the Dynamic Multiple Encapsulations feature enhances large-scale dial-in functionality, the feature also works well in smaller scale dial-in situations and for modem calls. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/dmencp3.htm
With the introduction of Easy IP Phase 2, Cisco IOS software also supports Intelligent DHCP Relay functionality. A DHCP Relay Agent is any host that forwards DHCP packets between clients and servers. A DHCP Relay Agent enables the client and server to reside on separate subnets. If the Cisco IOS DHCP server cannot satisfy a DHCP request from its own database, it can forward the DHCP request to one or more secondary DHCP servers defined by the network administrator using standard Cisco IOS ip helper-address functionality.
The Baseline Privacy feature extensions permit the encryption of data transferred between the cable modem and the Cisco uBR7200 series universal broadband router. The key management protocol defined by the Baseline privacy feature allows Cisco uBR7200 series universal broadband routers to provide two types of keys to cable modems. The KEK decrypts the TEK. The TEK is the key used to encrypt and decrypt data packets.
|
Note For Cisco to be able to provide nonexport-controlled images, the standard image (uBR7200-p-mz) will no longer support Baseline Privacy. Only new images explicitly identified as encryption images (uBR7200-k1p-mz) will support Baseline Privacy. |
CMTS users can obtain operating statistics directly from their CMTSs using SNMP. Specific information includes the downstream receive power ratio, downstream signal-to-noise ratio, transmit timing offset, and micro reflection (in decibels).
The Cisco uBR924 cable access router contains four RJ-45 (10BaseT Ethernet) hub ports. Using Cisco IOS Release 12.0(5)T or later interim images, these hub ports can be connected to four computers directly or one of the four ports to an Ethernet hub. The Ethernet hub connects additional computers or devices at the site.
Formerly, if compression of TCP or Real-Time Transport Protocol (RTP) headers was enabled, compression was performed in the process-switching path, which meant that packets traversing interfaces that had TCP or RTP header compression enabled were queued and passed up to the process to be switched. This procedure slowed transmission of the packet, and therefore some users preferred to fast-switch uncompressed TCP and RTP packets.
Now, if TCP or RTP header compression is enabled, compression occurs by default in the fast-switched path or the Cisco Express Forwarding-switched (CEF-switched) path, depending on which switching method is enabled on the interface. Furthermore, the number of TCP and RTP header compression connections is increased to 1000 each.
If neither fast switching nor CEF switching is enabled and TCP or RTP header compression is enabled, compression occurs in the process-switched path as before. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/rtpfast.htm
Store and Forward Fax functionality is facilitated through Simple Mail Transfer Protocol (SMTP). Additional functionality provides confirmed delivery using existing SMTP mechanisms such as Extended SMTP for those features.
In Store and Forward Fax, you can collect accounting information about fax services in two ways:
The ESMTP Accounting in the Store and Forward Fax feature enables you to collect accounting information about fax services as part of the SMTP session. This functionality is activated through the use of an intelligent fax client or Internet Mail Transfer Agent (MTA).
In ESMTP accounting, the off-ramp gateway (acting in its capacity as an ESMTP server) advertises capabilities to the MTA, which is acting as an e-mail client. One of the capabilities the off-ramp gateway advertises is xaccounting, which means that the gateway supports ESMTP accounting. If the MTA recognizes the xaccounting service extension, the MTA (acting as the client) can accept the ESMTP accounting information sent from the off-ramp gateway. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/esmtp_a.htm
Cisco IOS Release 12.1 adds support for Facility Data Link (FDL) on the Multiflex Trunk (MFT) module. You can specify the FDL format to use as either the ANSI T1.403 standard or the AT&T TR54016 standard, or both.
In previous releases, when the voice-encap option was configured on Frame Relay or Cisco HDLC, all fancy queueing (such as WFQ, custom queueing, and priority queueing) on the interface was disabled, and queueing was handled on a first-come first-served (FCFS) basis. New enhancements have been made to support fancy queueing on Frame Relay and Cisco HDLC.
For Frame Relay, a new interface command, frag-pre-queueing, has been added that allows you to set the queueing to be performed after the data segmentation. The command is available for Frame Relay interfaces only. The syntax for this new command is the following:
frag-pre-queueingBy default, this command is enabled, which allows only FCFS queueing at the interface level. If you enter the no frag-pre-queueing command, you can configure WFQ, custom queueing, or priority queueing at the interface level. Note that if you enter no frag-pre-queueing, you still must explicitly configure the fancy queueing type on the interface.
For HDLC encapsulation, the queueing now takes place after segmentation when the voice-encap option is entered. WFQ, custom queueing, and priority queueing are now supported on an interface configured for Cisco HDLC.
FSSRP is an enhancement to the current LANE SSRP. In this new scheme, the LAN Emulation Clients (LECs) do not go down whenever there is a change in the master LAN Emulation Server (LES). This is achieved by connecting the LECs simultaneously to more than one LES/BUS (up to four) so that if the master LES goes down, the backups are immediately available. With the basic SSRP, the LEC has to go down and completely recycle before coming back up. This operation is accomplished by keeping the control connections open to all of the active LESs and BUSs in the emulated LAN (ELAN). Although this method uses more VCs, the main benefits are the transparency and speed in the switchover.
The feature includes the following commands:
The following is a sample output for the show lane client detail command:
ATM> enable
ATM# show lane client detail
LE Client ATM1/0.1 ELAN name:xxx Admin:up State:operational
Client ID:2 LEC up for 1 day 40 minutes 48 seconds
ELAN ID:0
Join Attempt:14
Known LE Servers:1
Configured Idle Time:5 seconds
Last Fail Reason:Config VC being released
HW Address:00e0.8fcf.d820 Type:ethernet Max Frame Size:1516
ATM Address:47.0091810000000061705B0C01.00E08FCFD820.01
VCD rxFrames txFrames Type ATM Address
0 0 0 configure 47.00918100000000613E5A2F01.006070174823.00
LEC ID:2, State:LESBUS_ACTIVE
52 1778 3556 direct 47.00918100000000613E5A2F01.00000C5A0C59.01
53 1778 0 distribute 47.00918100000000613E5A2F01.00000C5A0C59.01
54 0 0 send 47.00918100000000613E5A2F01.00000C5A0C5A.01
55 0 0 forward 47.00918100000000613E5A2F01.00000C5A0C5A.01
LEC ID:3, State:LESBUS_ACTIVE
93 122 234 direct 47.00918100000000613E5A2F01.00000ABCD001.09
94 122 0 distribute 47.00918100000000613E5A2F01.00000ABCD001.09
97 0 0 send 47.00918100000000613E5A2F01.00000ABCD002.09
98 0 0 forward 47.00918100000000613E5A2F01.00000ABCD002.09
FSSRP is compatible with older releases of SSRP LANE software. However, the full benefits of the protocol will not be realized unless all LANE components in the network are FSSRP-capable. Older versions of LECS, LES, and BUS will not allow FSSRP-capable LECs to join the ELAN because of DDTs CSCdj82158 and CSCdm01992. For more information, refer to CSCdj82158 and CSCdm01992 in the "Resolved Caveats in Release 12.0(5)T for the RSM/VIP2" section.
Note the following restrictions:
Fax support is introduced in Cisco IOS Release 12.0(5)T images that support voice. The two Cisco uBR924 cable access router VoIP ports can now be connected to telephone or fax devices. Also refer to New Hardware Features In Release 12.0(4)XI1.
|
Note Only one voice call (telephone or fax) per VoIP line is active at a time. |
The Flow-Based WRED feature provides a mechanism to penalize the flows that do not respond to WRED drops. This feature is provided as an extension to the existing WRED functionality and can be turned on after WRED is turned on.
Flow-WRED ensures that no single flow can monopolize all the buffer resources at the output interface queue. With WRED alone, this can occur in the presence of traffic sources that do not back off during congestion. Flow-WRED maintains minimal information about the buffer occupancy per flow. Whenever a flow exceeds its share of the output interface buffer resource, the packets of the flow are penalized by increasing the probability of their drop (by WRED). Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/flowwred.ht m
Frame Relay-to-ATM Service Interworking for data transfer is outlined in Frame Relay Forum (FRF) implementation agreement FRF.8 and designed for the Cisco MC3810 multiservice access concentrator.
FRF.8 Frame Relay-ATM Service Interworking provides the following services:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/frf8_t6.htm
The Frame Relay-to-ATM Network Interworking (FRF.5) feature that was first introduced in Cisco IOS Release 11.3(1)MA has been enhanced to allow setting the mode of the Discard Eligibility and Cell Loss Priority fields as defined in the FRF.5 implementation agreement.
Network Interworking allows the transparent tunneling of Frame Relay user traffic and PVCs over ATM. This function is often used to link Frame Relay networks over an ATM backbone. The most distant nodes must be configured to interoperate with one another—in contrast to Service Interworking—because intact Frame Relay frames are sent over the ATM network. The ATM backbone is used as an alternative to a leased line and provides cost savings over leased lines. There can be a one-to-one relationship between Frame Relay and ATM PVCs, or multiple Frame Relay PVCs can be multiplexed into a single ATM PVC. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/frf5_6t.htm
The Frame Relay End-to-End Keepalive feature enables the router to keep track of PVC status, independent of the switches in the Frame Relay network. The routers at both ends of a PVC in a Frame Relay network engage in a keepalive session where one router issues keepalive messages and the router at the other end of the PVC connection responds. The time interval for the keepalive is configurable and is enabled on a per-PVC basis. As long as the keepalive-issuing router receives response messages, the PVC status is up. When response messages are not received (because of line failure, a faulty switch in the Frame Relay network, or a router failure), the PVC is down. This mechanism enables bidirectional communication of PVC status to both routers at the ends of a PVC connection. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/frkeep.htm
The logging event command has been enhanced to enable or disable logging DLCI Change and subinterface UPDOWN console messages on Cisco 7200 and Cisco 7500 series routers. The logging event dlci-status-change and logging event subif-link-status commands are used to enable logging.
The display on the show frame-relay pvc command has been enhanced on Cisco 7200 and Cisco 7500 series routers to include a table showing the number of PVCs in their various states.
Full and DOCSIS-Compliant Bridging for the Cisco uBR924 cable access router is compatible with the DOCSIS standards for interoperable cable access routers and supports two modes of transparent bridging:
The current full transparent bridging is supported in Cisco IOS Release 12.0 and configured by using the command line interface.
DOCSIS-compliant transparent bridging is configured automatically at startup only. The DOCSIS bridging mode is set as the default for the Cisco uBR924 cable access router. A command line interface command is provided to disable automatic DOCSIS-compliant configuration after the next reload.
The G.726 (ADPCM) feature provides higher reliability for digit transport in networks with greater hop counts and can be used to support lower-speed modems (up to 9.6 kbps).
The Alternate Gatekeeper feature provides redundancy for a gatekeeper in a system where gatekeepers are used. This enhancement allows a gateway to use up to two alternate gatekeepers as a backup in the case of a primary gatekeeper failure.
A gatekeeper manages H.323 endpoints in a consistent manner, allowing them to register with the gateway and to locate another gatekeeper. The gatekeeper provides logic variables for proxies or gateways in a call path, to provide connectivity with the 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 by using Cisco IOS configuration options. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/0288_alt.htm
The H.323 Version 2 Support feature upgrades Cisco IOS software to comply with the mandatory requirements in the Version 2 specification. This upgrade enhances the existing VoIP gateway, the Multimedia Conference Manager (gatekeeper and proxy), and the DTMF digital relay using H.245.
DTMF is the tone generated on a touch-tone phone when you press keypad digits. The tones are compressed into a single stream at one end of a call and decompressed at the other end by using H.245 messages. However, this compression and decompression can lead to distortion, depending upon the codec used. Thus, the DTMF-relay is used to configure one of the following three methods to transport DTMF tones generated after the call is established out-of-band:
H.323 Version 2 defines a lightweight registration procedure that requires full registration for initial registration, but uses an abbreviated renewal procedure to update the gatekeeper and minimize overhead. Lightweight registration requires each endpoint to specify a time to live (TTL) value in its Registration Request (RRQ) message.
The H.323 Version 2 gateway supports the registration of fully qualified E.164 numbers with the gatekeeper for phones connected directly to the gateway. Tunneling through H.225 User-to-User Information Element (UUIE) facilitates transparent handling of supplementary services between two endpoints through a VoIP network. This tunneling eliminates the need to interpret various supplementary signalling messages in the VoIP gateways.
The H.323 Version 2 gatekeeper selects a destination gateway by choosing from among all gateways registered in a zone by allowing you to assign selection priorities to these gateways based on the dialed prefix. Gateway resource reporting allows the gateway to notify the gatekeeper when H.323 resources are getting low. The gatekeeper uses this information to determine which gateway it will use to complete a call. The gatekeeper maintains a separate gateway list, ordered by priority, for each of its zone prefixes. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/h323v2.htm
PPP over ATM is available on an ATM CES port adapter in a Cisco 7200-series router.
In previous releases of PPP over ATM, you configured PVCs for PPP over ATM on point-to-point subinterfaces. In this release, each PPP over ATM connection no longer requires two interfaces, a virtual access interface and ATM subinterface. Instead, you can configure multiple PVCs for PPP over ATM on multipoint subinterfaces, thereby providing a significant increase in the number of PPP over ATM sessions per router. Also in this release, PPP over ATM is enhanced to support VC multiplexed encapsulation and complies with the IETF draft on multiplexed encapsulation titled PPP over AAL5. The previous version of PPP over ATM supported only the Frame Forwarding data encapsulation (aal5ciscoppp).
|
Note The IETF PPP over ATM feature does not currently support Logical Link Control (LLC) encapsulated PPP over AAL5. |
This release of the PPP over ATM feature provides support for IETF-compliant PPP over ATM and significantly increases the maximum number of PPP over ATM sessions running on a router. The maximum number of PPP over ATM sessions supported on a platform depends on available system resources such as memory and CPU speed. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/ppp_atm2.ht m
Extensive CLI enhancements include user configuration using the CLI, SNMP, and HTTP. All methods will provide essentially the same set of configuration objects.
The Cisco uBR7200 series universal broadband router offers an integrated DHCP server to simplify provisioning of cable modems.
Cisco uBR7200 series universal broadband routers are now able to respond to RFC 868 time-of-day (ToD) queries from cable modems during the registration process.
Cisco uBR7200 series routers support the Inter-Switch Link (ISL) feature, a Cisco protocol for interconnecting multiple routers and switches. The ISL protocol maintains VLAN information as traffic passes between routers and switches.
A number of Cisco IOS cable interface commands have been enhanced as follows:
The previous cable downstream if-output command has not changed and continues to output a standard modulated signal. The no cable downstream if-output command also has not changed—it stops all signal output and shuts down the interface.
A new command changes the cable modem registration value (the T9 timer). The cable registration-timeout minutes command sets the T9 timer to the new value (from 2 to 60 minutes). The no cable registration-timeout command resets the T9 timer to its default of 3 minutes.
The Interface MIB Implementation for ATM Subinterfaces feature involves the implementation of the Interface MIB (RFC 2233) for ATM subinterfaces. Network managers can now query for the MIB variables on a per-subinterface basis. Because the implementation of this feature is in platform-independent code, this feature is supported on all Cisco ATM interfaces and port adapters where speeds are at or above OC-3. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/imib_atm.ht m
Internet Key Exchange (IKE) mode configuration, as defined by the IETF, allows a gateway to download an IP address (and other network level configuration) to the client as part of an IKE negotiation. Using this exchange, the gateway gives IP addresses to the IKE client to be used as an "inner" IP address encapsulated under IPSec. This provides a known IP address for the client, which can be matched against IPSec policy.
This feature implements IKE mode configuration into existing Cisco IOS IPSec software images. Using IKE mode configuration, you can configure a Cisco access server to download an IP address to a client as part of an IKE transaction. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe4/ modconf.htm
The IP Address Verification for the Cisco uBR7200 series cable router feature enables DHCP servers to verify IP addresses of upstream traffic.
The IP Multicast Multilayer Switching (MLS) feature provides high-performance, hardware-based, Layer 3 switching of IP multicast traffic for routers connected to Catalyst 5000 series LAN switches.
An IP multicast flow is a unidirectional sequence of packets between a multicast source and the members of a destination multicast group. Flows are based on the IP address of the source device and the destination IP multicast group address.
The packet forwarding function is moved onto the connected Layer 3 switch whenever a supported path exists between a source and members of a multicast group. Packets that do not have a supported path to reach their destinations are still forwarded in software by routers. Protocol Independent Multicast (PIM) is used for route determination. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/ipmctmls.htm
The IP RTP Priority feature provides a strict priority queueing scheme for delay sensitive data such as voice. Voice traffic can be identified by its RTP port numbers and classified into a priority queue configured by the ip rtp priority command. The result is that voice is serviced as strict priority in preference to other nonvoice traffic.
This feature extends and improves on the functionality offered by the IP RTP Reserve feature by allowing you to specify a range of UDP/RTP ports whose voice traffic is guaranteed strict priority service over any other queues or classes using the same output interface. Strict priority means that if packets exist in the priority queue, they are dequeued and sent first—that is, before packets in other queues are dequeued. We recommend that you use the ip rtp priority command instead of the ip rtp reserve command for voice configurations. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/iprtp.htm
The IP to ATM Class of Service feature maps quality of service (QoS) characteristics between IP and ATM, using network modules on the Cisco 2600 and 3600 series routers. The resulting feature makes it possible to support different service classes (sometimes termed "differential service classes") in network service provider environments.
IP to ATM CoS is designed to provide a true working solution to class-based services, without the investment of new ATM network infrastructures. Now networks can offer different services across the entire wide-area network, not just the routed portion. Mission-critical applications can be given exceptional service during periods of high network usage and congestion. In addition, noncritical traffic can be restricted in its network usage, which ensures greater QoS for more important traffic and user types.
IP to ATM CoS supports configuration of both a single ATM virtual circuit (VC) and VC bundles.
IP to ATM CoS support for a single ATM VC allows network managers to use existing features, such as committed access rate (CAR) or policy-based routing to classify and mark different IP traffic by modifying the IP Precedence field in the IPv4 packet header (PBR). Subsequently, Weighted Random Early Detection (WRED) can be configured on a per-VC basis so that the IP traffic is subject to different drop probabilities (and therefore priorities) as IP traffic coming into a router competes for bandwidth on a particular VC.
The Cisco 2600 and 3600 series ATM network modules provide the ability to shape traffic on each VC according to the ATM service category and traffic parameters employed. When you use the IP to ATM CoS feature, congestion is managed entirely at the IP layer by WRED running on the routers at the edge of the ATM network.
ATM VC bundle management allows users to:
Each VC in a bundle has its own ATM traffic class and ATM traffic parameters. You can apply attributes and characteristics to discrete VC bundle members or you can apply them collectively at the bundle level.
Using VC bundles, you can:
To determine which bundled VC should forward a packet to its destination, the ATM VC bundle management software matches precedence levels between packets and VCs in the following way:
|
Note The ATM VC bundle management feature allows you to configure how traffic will be redirected in the event that the VC to which a packet was directed goes down. |
The support of multiple parallel ATM VCs allows you to create stronger service differentiation at the IP layer. For instance, you might want to provide IP traffic belonging to real-time CoS (such as Voice over IP traffic) on an ATM VC with strict constraints constant bit rate (CBR) or variable bit rate (VBR-rt PVC, for example), while transporting traffic other than real-time traffic over a more elastic ATM available bit rate (ABR) permanent virtualcircuit (PVC). Using a configuration like this allows you to fully utilize your network capacity. You could also elect to transport best-effort IP traffic over a uncommitted bit rate (UBR) PVC---UBR is effectively ATM's version of best-effort service.
IP to ATM CoS provides the following benefits:
IP to ATM CoS has the following restrictions:
The IP to ATM CoS feature is supported on both the 2600 and 3600 series routers with the following restrictions:
The IP to ATM CoS feature requires ATM PVC management and Cisco Express Forwarding (CEF) switching functionality. It also requires that the remote router run a version of Cisco IOS software that supports IP to ATM CoS with VC bundle management.
To use this feature, you should be familiar with the following QoS features:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/ipatmcs2.htm
The IPSec Network Security feature is available on the Cisco 800 series routers (IP/Firewall/Plus/IPSec56 and IP/IPX/Firewall/IPSec56/Plus images only). This feature supports the 56-bit Data Encryption Standard (DES); it does not support the triple DES. Enabling this feature can impact your router performance.
IPSec is a framework of open standards that provides data confidentiality, data integrity, and data authentication between participating peers, such as two routers. IPSec provides these security services on IP datagrams.
Several IPX display and debug enhancements now improve flexibility and ease of maintenance as follows:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/ipxenhan.htm
The IPX Multilayer Switching (MLS) feature provides high-performance, hardware-based, Layer 3 switching for Catalyst 5000 series LAN switches. IPX data packet flows are switched between networks, off-loading processor-intensive packet routing from network routers.
Whenever a partial or complete switched path exists between two hosts, packet forwarding occurs on Layer 3 switches. Packets without such a partial or complete switched path are still forwarded by routers to their destinations. Standard routing protocols such as Routing Information Protocol (RIP), Enhanced Interior Gateway Protocol (EIGRP), and NetWare Link Services Protocol (NLSP) are used for route determination.
IPX MLS also allows you to debug and trace flows in your network. Use MLS explorer packets to identify which switch is handling a particular flow. These packets aid you in path detection and troubleshooting. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/ipxmls.htm
As Intermediate System-to-Intermediate System (IS-IS) networks grow, they are usually organized into a backbone area (Level 2) connected to local areas (Level 1). Routers establish Level 1 adjacencies to perform local area routing, and Level 2 adjacencies to perform routing between Level 1 areas. Previously, a Cisco router could route between the backbone (Level 2) area and at most a single Level 1 area.
The IS-IS Multiarea Support feature supports configuration of multiple Level 1 IS-IS areas on a single router. This configuration is especially useful in networks where devices support only Level 1 routing and are organized in a number of small Level 1 areas that cannot be aggregated for performance reasons. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/ismarea.htm
The VoIP feature enables the Cisco 3600 and Cisco 2600 series of modular routers to carry voice traffic simultaneously with data traffic over an IP network. VoIP is primarily a software feature, supporting both voice and fax calls. Support for the ISDN BRI signalling type allows a Cisco 3600 or Cisco 2600 series router to provide voice access connectivity to either an ISDN telephone network or to a digital interface on a PBX/key communications system. The voice or data also crosses an IP network to which the router connects. This allows branch offices and enterprises to route incoming public switched telephone network (PSTN) ISDN BRI calls over an IP network or send outgoing digital fax and voice calls via an IP network.
The ISDN Cause Code Override feature overrides cause codes that are sent to ISDN applications. Cisco IOS software contains ISDN cause codes that handle specific functions such as modem availability and resource pooling. The ISDN Cause Code Override feature is more general in its functionality and will override the specific ISDN cause codes.
When the command associated with this feature is implemented, the configured cause codes are sent to the switch; otherwise, default cause codes of the application are sent.
To override an ISDN cause code, enter the isdn disconnect-cause {cause-code-number | busy | not-available} command, where cause-code-number is a cause code number from 1 to 127.
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/isdnscrn.htm
To carry asynchronous traffic over ISDN, you need a terminal adapter to convert that traffic and forward it over synchronous connections. This process is normally implemented by the V.120 protocol, which carries asynchronous traffic over ISDN. However, several countries in Europe (Germany, Switzerland, and some Eastern European countries) use LAPB as the protocol to forward their asynchronous traffic over synchronous connections.
Your routers, therefore, need to be able to recognize and accept calls from these asynchronous/synchronous conversion devices. The LAPB-TA makes this situation possible. (LAPB is sometimes referred to as "X.75," because LAPB is the link layer specified in the ITU-T X.75 recommendation for carrying asynchronous traffic over ISDN.)
ISDN LAPB-TA allows a user with an ISDN terminal adapter that supports asynchronous traffic over LAPB to call into the router and establish an asynchronous PPP session. LAPB supports both local Challenge Handshake Authentication Protocol (CHAP) authentication and external RADIUS authorization on the AAA server. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t4/lapbta.htm
The new ISDN MIB RFC 2127 has been designed to provide useful information in accordance with the new IETF standard for the management of ISDN interfaces. RFC 2127 provides information on the physical BRIs, control and statistical information for B (bearer) and D (signalling) channels, terminal endpoints, and directory numbers.
The ISDN MIB RFC 2127 controls all aspects of ISDN interfaces. It has five groups:
The ISDN MIB RFC 2127 enables you to use any commercial SNMP network management application to support ISDN call processing in Cisco IOS software. You can integrate management of dial access products using ISDN with your existing network management systems. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/isdn_mib.htm
Cisco is building voice gateways to connect more traditional telephone networks to voice over IP (VoIP) networks. Customers that are installing VoIP networks often need a mechanism at the gateway to present a customized interface to the caller. The Interactive Voice Response (IVR) feature was first made available to customers with Cisco IOS Release 11.(3)NA2 with the Service Provider VoIP feature set. IVR, with the addition of scripts using TCL, was introduced with Cisco IOS Release 12.0(4)XH. These TCL IVR scripts are the default scripts that must be used with the IVR application in Cisco IOS Release 12.0(4)XH and later releases.
IVR consists of simple voice prompting and digit collection to gather caller information for authenticating the user and identifying the destination. IVR provides the following abilities:
The large-scale dial-out feature eliminates the need to configure dialer maps on every network access server for every destination. Instead, you create remote site profiles containing outgoing call attributes (telephone number, service type, maximum number of links, and so on) on an AAA server. The profile is downloaded by the network access ser ver when packet traffic requires a call to be placed to a remote site. Large-scale dial-out also takes advantage of features previously only available for incoming calls, such as dialer and virtual profiles, Multichassis Multilink PPP (MMP) support, and the ability to use an AAA server to store dial-out attributes. MMP allows network access servers to be stacked together and appear as a single network access server chassis so that if one network access server fails, another network access server in the stack can accept calls. Additionally, large-scale dial-out addresses congestion management by seeking an uncongested, alternative network access server when the designated primary network access server experiences port congestion. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/lsdial.htm
Layer 2 Tunneling Protocol (L2TP) is an emerging IETF standard that combines the best features of two existing tunneling protocols: Cisco Layer 2 Forwarding (L2F) and Microsoft Point-to-Point Tunneling Protocol (PPTP). L2TP is an extension to PPP, which is an important component for access VPNs. Access VPNs allow mobile users to connect to their corporate intranets or extranets, thus improving flexibility and reducing costs.
Traditional dial-up networking services only supported registered IP address, which limited the types of applications that could be implemented over Virtual Private Networks (VPNs). L2TP supports multiple protocols and unregistered and privately administered IP addresses over the Internet. This allows the existing access infastructure, such as the Internet, modems, access servers, and ISDN terminal adaptors (TAs), to be used.
L2TP can be initiated wherever PPTP or L2F is currently deployed and can be operated as a client initiated tunnel, such as PPTP, or a network access server (NAS) initiated tunnel, such as L2F. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/l2tpt.htm
The L2TP Dial-Out feature enables L2TP Network Servers (LNSs) to tunnel dial-out virtual private dial-up network (VPDN) calls using L2TP as the tunneling protocol. This feature enables a centralized network to efficiently and inexpensively establish a virtual point-to-point connection with any number of remote offices.
Using the L2TP Dial-Out feature, Cisco routers can carry both dial-in and dial-out calls in the same L2TP tunnels. Previously, only dial-in VPDN calls were supported.
L2TP dial-out involves two devices: an LNS and an L2TP Access Concentrator (LAC). When the LNS wants to perform L2TP dial-out, it negotiates an L2TP tunnel with the LAC. The LAC then places a PPP call to the client(s) the LNS wants to dial-out to. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/l2tpout.htm
The local voice busy-out feature for the Cisco MC3810 is designed to busy out the trunks assigned to a PVC whose pipe is broken so that the PBX will not attempt to seize the circuit. This feature allows the PBX to route or reroute a given call based on the actual availability of trunks.
This feature is different from the concept of busy-back. Busy-back refers to the signal sent from within the network to the calling party that indicates a busy (or congested) state anywhere along the route, up to and including the condition of the called part. When the number of available DSPs is less than the number of incoming trunks from a PBX, a call from the PBX will connect to dead air. The capability to provide a busy-back signal because no DSPs are available is not supported on the Cisco MC3810 as part of this feature. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/busyfm.htm
The Low Latency Queueing feature brings strict priority queueing to Class-Based Weighted Fair Queueing (CBWFQ). Strict priority queueing allows delay-sensitive data, such as voice, to be dequeued and sent first (before packets in other queues are dequeued), giving delay-sensitive data preferential treatment over other traffic.
Without Low Latency Queueing, CBWFQ provides weighted fair queueing based on defined classes with no strict priority queue available for real-time traffic. CBWFQ allows you to define traffic classes and then assign characteristics to that class. For example, you can designate the minimum bandwidth delivered to the class during congestion.
For CBWFQ, the weight for a packet belonging to a specific class is derived from the bandwidth you assigned to the class when you configured it. Therefore, the bandwidth assigned to the packets of a class determines the order in which packets are sent. All packets are serviced fairly based on weight; no class of packets may be granted strict priority. This scheme poses problems for voice traffic that is largely intolerant of delay, especially variation in delay. For voice traffic, variations in delay introduce irregularities of transmission manifesting as jitter in the heard conversation.
The Low Latency Queueing feature provides strict priority queueing for CBWFQ, reducing jitter in voice conversations. Configured by the priority command, Low Latency Queueing enables use of a single, strict priority queue within CBWFQ at the class level, allowing you to direct traffic belonging to a class to the CBWFQ strict priority queue.
In the event of congestion, policing is used to drop packets when the bandwidth is exceeded. Voice traffic enqueued to the priority queue is UDP-based and therefore not adaptive to the early packet drop characteristic of WRED.
When congestion occurs, traffic destined for the priority queue is metered to ensure that the bandwidth allocation configured for the class to which the traffic belongs is not exceeded. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/pqcbwfq.htm
The LU Pooling (ASSOCIATE) and Response Time MIB feature contains several TN3270 server configuration enhancements as follows:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/tn32enh2.htm
The MIB support in the Cisco uBR7200 series universal broadband routers provides much of the same ability to configure the router as using CLI commands at the router console port. Additionally, the Radio Frequency (RF) Interface MIB has changed to improve the object support for traps and to add the following QoS and service class support:
The maximum user links feature provides a method to limit the number of inbound connections a user can establish with a device. This maximum connection limit is only imposed on links that have name authentication configured. Each Multilink PPP connection is counted as one connection.
The User Maxlink feature enables Internet Service Providers (ISPs) to limit the number of inbound connections a user can establish so that they can provide various levels of subscriptions at different costs. Users that desire more bandwidth can be charged a higher rate to establish multiple connections, while users that require only a single connection can be charged a discounted rate.
The Memory Scan feature for Cisco 7500 series router Route Switch Processor (RSP) modules adds a low-priority background process that searches all installed DRAM for possible parity errors. The process runs every 60 seconds and can be controlled and monitored with new CLI commands. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/tmemscn.htm
Microsoft Point-to-Point Compression (MPPC) is a scheme used to compress 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.
Mobile IP provides users the freedom to roam beyond their home subnet while consistently maintaining their home IP address, which enables transparent routing of IP datagrams to mobile users during their movement, so that data sessions can be initiated to them while they roam; it also enables sessions to be maintained in spite of physical movement between points of attachment to the Internet or other networks. The Cisco implementation of Mobile IP is fully compliant with the IETF's proposed standard defined in RFC 2002. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/mobileip.htm
The Modem over BRI feature for the Cisco 3640 modular access router lowers the cost of remote access by offering high-speed modem and ISDN connectivity for mobile customers, home offices, and other remote-access users. Branch offices and enterprises can support analog modem users that call over the PSTN into BRI interfaces in Cisco 3640 routers.
Analog modem calls arrive at a speed of 33.6 kbps via the PSTN. The router digital modems accept the modem calls at connection speeds as fast as 56 kbps, adhering to the V.90 standard. The Cisco 3640 router in this way provides rapid access to e-mail and other network services. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/3600mbri.ht m
The modem status summary enhancements for the Cisco uBR7200 Series Cable Router feature provides detailed summary information on the current system status of modems. The show cable modem command now includes the following information for each upstream channel:
You can also limit your search for modem status to specific cable interfaces.
The Multiprotocol Label Switching (MPLS) CoS feature enables network administrators to provide differentiated types of service across an MPLS network. Differentiated service satisfies a range of requirements by supplying for each packet sent the particular kind of service specified for that packet by its CoS. Service can be specified in different ways, for example, through use of the IP Precedence bit settings in IP packets or in source and destination addresses. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/cos.htm
MPLS traffic engineering software provides the following services:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/te120_7t.htm
The MPLS IP VPN feature allows a Cisco IOS network to deploy scalable IPv4 Layer 3 VPN backbone services. An IP VPN is the foundation companies use for deploying or administering value-added services such as applications and data hosting network commerce, and telephony services to business customers.
In private LANs, IP-based intranets have fundamentally changed the way companies conduct their business. Companies are moving their business applications to their intranets to extend over a WAN. Companies are also embracing the needs of their customers, suppliers, and partners by using extranets (an intranet that encompasses multiple businesses). With extranets, companies reduce business process costs by facilitating supply-chain automation, electronic data interchange, and other forms of network commerce. To take advantage of this business opportunity, service providers must have an IP VPN infrastructure that delivers private network services to businesses over a public infrastructure.
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.
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 AAA security services. If you have enabled AAA, PPP authentication using MS-CHAP can be used in conjunction with both TACACS+ and RADIUS.
The Multicast Border Gateway Protocol (MBGP) feature adds capabilities to BGP to enable multicast routing policy throughout the Internet and to connect multicast topologies within and between BGP autonomous systems. That is, MBGP is an enhanced BGP that carries IP multicast routes. BGP carries two sets of routes, one set for unicast routing and one set for multicast routing. The routes associated with multicast routing are used by the PIM to build data distribution trees.
It is possible to configure BGP peers that exchange both unicast and multicast Network Layer Reachability Information (NLRI).
MBGP is useful when you want a link dedicated to multicast traffic, perhaps to limit which resources are used for which traffic. Perhaps you want all multicast traffic exchanged at one network access point (NAP). MBGP allows you to have a unicast routing topology different from a multicast routing topology. Thus, you have more control over your network and resources.
Prior to MBGP, the only way to perform interdomain multicast routing was to use the BGP infrastructure that was in place for unicast routing. If those routers were not multicast capable, or you had differing policies where you wanted multicast traffic to flow, you could not support it. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/mbgp.htm
The Multicast Routing Monitor (MRM) feature is a management diagnostic tool that provides network fault detection and isolation in a large multicast routing infrastructure. It is designed to notify a network administrator of multicast routing problems in near real time.
MRM has three components that play different roles: the Manager, the Test Sender, and the Test Receiver. The Manager can reside on the same device as the Test Sender or Test Receiver. You can test a multicast environment using test packets (perhaps before an upcoming multicast event), or you can monitor existing IP multicast traffic.
You create a test based on various test parameters, name the test, and start the test. The test runs in the background and the command prompt returns. If the Test Receiver detects an error (such as packet loss or duplicate packets), it sends an error report to the router configured as the Manager. The Manager immediately displays the error report. Also, by issuing a certain show command, you can see the error reports, if any. You then troubleshoot your multicast environment as normal, perhaps using the mtrace command from the source to the Test Receiver. If the show command displays no error reports, the Test Receiver is receiving test packets without loss or duplicates from the Test Sender. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/mrm.htm
Multicast Source Discovery Protocol (MSDP) connects multiple PIM sparse-mode (SM) domains. MSDP allows multicast sources for a group to be known to all rendezvous points (RPs) in different domains. Each PIM-SM domain uses its own RPs and need not depend on RPs in other domains. An RP runs MSDP over TCP to discover multicast sources in other domains.
An RP in a PIM-SM domain has an MSDP peering relationship with MSDP-enabled routers in another domain. The peering relationship occurs over a TCP connection, where primarily a list of sources sending to multicast groups is exchanged. The TCP connections between RPs are achieved by the underlying routing system. The receiving RP uses the source lists to establish a source path.
The purpose of this topology is to have domains discover multicast sources in other domains. If the multicast sources are of interest to a domain that has receivers, multicast data is delivered over the normal, source-tree building mechanism in PIM-SM.
MSDP is also used to announce sources sending to a group. These announcements must originate at the domain RP.
MSDP depends heavily on (M)BGP for interdomain operation. You should run MSDP in your domain RPs that act as sources, sending to global groups for announcement to the Internet. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/msdp.htm
Dial strings of multiple lengths can now be supported in the same network and on the same Cisco MC3810.
The Multilink Point-to-Point Protocol (MLP) Inverse Multiplexer feature allows you to combine multiple T1/E1 lines in a VIP T1/E1 interface into a bundle that has the combined bandwidth of the multiple T1/E1 lines, which is done by using a VIP MLP link. You choose the number of bundles and the number of T1/E1 lines in each bundle. This feature allows you to increase the bandwidth of you network links beyond that of a single T1/E1 line without the need to purchase a T3 line. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/multippp.htm
Use the Multimedia Conference Manager to enable your current internetwork to route bit-intensive data such as audio telephony, video and audio telephony, and data conferencing using existing telephone and ISDN links, without degrading the current level of service on the network. The Multimedia Conference Manager feature provides H.323 application options previously unavailable. Using Multimedia Conference Manager, you can implement H.323-compliant applications on existing networks in an incremental fashion without upgrades. This feature also provides a rich list of networking capability, including the following:
The Multimedia Conference Manager feature provides network administration mechanisms to support H.323 applications without impacting the mission-critical applications running on current networks. Multimedia Conference Manager is implemented on Cisco IOS software. Multimedia Conference Manager provides the network administrator with these abilities:
Multimedia Conference Manager has two principal functions: gatekeeper and proxy. These functions are unique to Multimedia Conference Manager. Similar robust features are currently not available in other vendor solutions.
Gatekeeper subsystems provide the following services:
Starting with Cisco IOS Releases 11.3(6)Q and 11.3(7)NA and later, you can configure Cisco gatekeepers to use the Cisco HSRP, so that when one gatekeeper fails, the standby gatekeeper assumes its role.
Proxy subsystems provide the following features:
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, which allows BRIs and 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 determines when Layer 2 is activated (power-up or first-call).
In earlier Cisco IOS releases, only named authentication method lists were supported under Cisco 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.
The National ISDN Switch Types for Basic Rate and Primary Rate Interfaces feature introduces changes to ISDN switch types for PRIs and Basic Rate Interfaces BRIs 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. |
IP policy routing now works with CEF, distributed CEF (dCEF), NetFlow, and NetFlow with flow acceleration. IP policy routing was formerly supported only in fast switching and process switching. Now that policy routing is integrated into CEF, policy routing can be deployed on a wide scale and on high-speed interfaces. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/policyrt.htm
NetFlow switching is a high-performance, network-layer switching path that provides network administrators with access to "call detail recording" information from their data networks; this information includes details such as user, protocol, port, type of service information, and the duration of the communication. This data can be used for a variety of purposes, including billing, enterprise accounting, network planning and performance analysis, QoS bandwidth management, security policies, and data warehousing/mining for marketing purposes.
The collected NetFlow data is sent out via UDP packets to a workstation running the NetFlow Flowcollector server, which can collect data from multiple routers for later analysis by a user running the NetFlow Flowanalyzer application. Through the NetFlow Data Export feature, traffic information can also be passed to external applications that perform functions such as billing or network performance analysis.
NetFlow also provides a highly efficient mechanism that can process security access lists without incurring the same performance penalty as other available switching methods. In conventional switching at the network layer, each incoming packet is handled on an individual basis with a series of functions to perform access list checks, capture accounting data, and switch the packet. In contrast, after NetFlow switching identifies a flow and processes the access list for the first packet in the flow, all subsequent packets are handled on a "connection-oriented" basis as part of the flow. This process avoids further access list checks on the flow, and packet switching and statistics capture are performed in tandem.
|
Note A network flow is identified as a unidirectional stream of packets between a given source and destination that has a unique combination of the following fields: source IP address, destination IP address, source port number, destination port number, protocol type, type of service, and input interface. |
Use the ip flow-cache, ip flow-export, and ip route-cache commands to configure NetFlow switching. See the Release 12.0 Cisco IOS Switching Services Configuration Guide on the Documentation CD-ROM and CCO for more details.
Cisco IOS Release 12.1 supports NetRanger programming. NetRanger is an Intrusion Detection System (IDS) composed of three parts:
Two scalability challenges facing the Internet are the depletion of registered IP address space and scaling in routing. Cisco IOS Network Address Translation (NAT) is a mechanism for conserving registered IP addresses in large networks and simplifying IP addressing management tasks. As its name implies, Cisco IOS NAT translates IP addresses within private "internal" networks to "legal" IP addresses for transport over public "external" networks (such as the Internet). Incoming traffic is translated back for delivery within the inside network.
Thus, Cisco IOS NAT allows an organization with unregistered "private" addresses to connect to the Internet by translating those addresses into globally registered IP addresses. Cisco IOS NAT also increases network privacy by hiding internal IP addresses from external networks.
The Network Director Forwarding Agent feature is a Cisco IOS-based packet redirector component of Cisco Network Director, the latest offering in the Cisco family of load-balancing solutions. The Network Director Forwarding Agent feature implements two new architectures, the Cisco Applications and Services Architecture and the Cisco patented Multinode Load Balancing Architecture.
Each Forwarding Agent "learns" the destination of specific connection requests and forwards packets between the appropriate client and chosen destination. When a Forwarding Agent receives a connection request, the request is forwarded to the Services Manager, the LocalDirector-based component of Cisco Network Director. The Services Manager makes the load-balancing decision and instructs the Forwarding Agents with the optimal destination. After destination selection, session data is forwarded directly to the destination without further Services Manager participation. There is no limit to the number of Forwarding Agents that can be configured in the Network Director solution.
The Offload Alias feature allows multihomed IP addresses for offload devices. This feature enables dispatch-based load-balancing access to mainframe hosts through TCP/IP offload devices that are configured on a CMCC adapter. The Offload Alias feature supports load-balancing access to multiple hosts by allowing you to configure multiple real IP addresses to an offload device on a CMCC adapter. Each of the real IP addresses is associated with a common single virtual IP address, or alias, for client access. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/ofdalias.htm
Internet voice telephony is often used for toll bypass by routing through an existing data network or the Internet instead of PSTN trunks. Calls of this nature require originating and terminating gateways. When the originating and terminating voice gateways are owned by two different carriers, settlement between these carriers is required. The Settlement for Packet Voice feature implements a standardized settlement protocol that can be implemented between different vendor gateways and voice settlement servers.
The Cisco gateway-based settlement protocol interacts between carriers to create a single authentication at initialization. The authentication is the basis for the establishment of a secure communication channel between the Settlement system and the infrastructure component. This channel then allows the following three types of transactions to be handled:
The OPX ring-through feature allows a port on the Cisco MC3810 to act like an Off-Premise Extension (OPX) to the PBX. When the PBX attempts to make a connection to the remote voice port on a Cisco MC3810, the OPX Ring-Through feature allows the PBX to reroute the call if there is no answer.
The former OSPF implementation for sending update packets needed to be more efficient. Some update packets were getting lost in cases where the link was slow, a neighbor could not receive the updates fast enough, or the router was out of buffer space. For example, packets might be dropped if either of these two topologies existed:
OSPF update packets are now automatically paced by a delay of 33 milliseconds. Pacing is also added between retransmissions to increase efficiency and minimize lost retransmissions.
OSPF update and retransmission packets are sent more efficiently. Also, you can display the link-state advertisements (LSAs) waiting to be sent out an interface. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/ospfpkpc.htm
Outgoing hunt is a new pots feature on the Cisco 800 series. This feature is available for U.S. switch types only. When enabled, the CSM will look for a free SPID to use for out going voice calls. If no calls are in progress, then the SPID associated with the dial peer destination is used. The customer must continue to program dial peers. By default, this feature is off.
The Open Settlement Protocol (OSP) Clearinghouse solution for Cisco Packet Telephony Gateway allows similar service providers to exchange traffic with other service providers without establishing multiple bilateral peering agreements.
Extended dialog mode for packet assembler/disassembler (PAD) service signals is now available in the French language and in English with the PAD French Enhancement feature. The French language service signals maintained in a table. When configured for the French language via PAD parameter 6, the PAD service signals map to this table, giving the appropriate French equivalent output. The internal table maintenance is based on the contents of the Annex-C/X.28 standard. Section 3.5/X.28 outlines parameter 6 and how it relates to extended mode dialog in multiple languages. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/x25tpad.htm
The Parse Bookmarks feature quickly processes consecutive similar commands, such as access-lists and prefix-lists, up to five times faster. The Parse Bookmarks feature reduces boot time and load time for large configurations with many similar consecutive commands. This feature is an enhancement to the parsing algorithm; therefore no configuration changes are needed.
The per-modem filters feature, also known as Per-Modem and Per-Host Access Lists, allows Cisco uBR7200 series universal broadband routers to filter incoming packets from individual hosts or cable modems based on the source MAC or IP address. This feature allows access lists to be specified on a per-interface or a per-address basis.
The Performance Data Collection feature allows a Cisco 3640 system controller to collect and store SNMP MIB data from its managed router and dial shelves. The system controller then serves as a central point for network management data collection. The system controller collects the raw data from the managed shelves periodically, saves the data, and provides a single access point for a central network management application. The data can then be uploaded to a network management station using FTP or TFTP.
The PGM Router Assist feature allows Cisco routers to support the optimal operation of Pragmatic General Multicast (PGM). The PGM Reliable Transport Protocol itself is implemented on the hosts of the customer. PGM is a reliable multicast transport protocol for applications that require ordered, duplicate-free, multicast data delivery from multiple sources to multiple receivers. PGM guarantees that a receiver in a multicast group either receives all data packets from transmissions and retransmissions, or can detect unrecoverable data packet loss. PGM is intended as a solution for multicast applications with basic reliability requirements. It is network-layer independent; the Cisco implementation of the PGM Router Assist feature supports PGM over IP. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/pgmscale.htm
Full support of IP Policy-based routing is used in conjunction with CEF and NetFlow. As CEF gradually obsoletes fast switching, policy routing must be integrated with CEF to meet customer performance requirements. When both policy routing and flow are enabled, redundant processing is avoided, performance is optimized, and a scalable set of services is delivered.
The PPP over Frame Relay feature allows a router to establish end-to-end 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.
PPP over Frame Relay provides the following benefits:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/pppframe.ht m
The multichassis hunt group has been enhanced to allow the preference command to be used to select remote dial peers before local dial peers using the priority values. This feature greatly extends the capability to support on-net to off-net rerouting of calls and alternate call center applications.
When the Cisco MC3810-IGX Interworking feature for the Cisco MC3810 was introduced, the FTC trunk could only support first-come first-served queueing. In Cisco IOS Release 12.1, the Cisco MC3810-IGX Interworking feature has been enhanced to support priority queueing, custom queueing, and generic traffic shaping. Standard Cisco IOS commands for priority queueing, custom queueing, and generic traffic shaping are supported.
|
Note The Cisco MC3810-IGX Interworking feature does not support WFQ. |
The addition of the CISCO-PROCESS-MIB and changes to the CISCO-MEMORY-POOL-MIB allow the retrieval of additional CPU and memory statistics and their reporting by SNMP. The CISCO-PROCESS-MIB provides CPU 5-second, 1-minute, and 5-minute statistics. In addition, this MIB provides CPU utilization and memory allocation/deallocation statistics for each process on each CPU listed in the CISCO-PROCESS-MIB.
The CISCO-PROCESS-MIB is enabled when the first SNMP command is configured. The background statistics collection for VIP cards and the master CPU occurs even if the SNMP subsystem is not initialized.
The Q.SIG Digit Forwarding feature extends support for dial peer digit forwarding to ISDN PRI QSIG signalling calls on the Cisco MC3810. When ISDN PRI QSIG signalling was first introduced on the Cisco MC3810 in Cisco IOS Release 12.0(2)T, digit forwarding on POTS dial peers was not supported in conjunction with ISDN PRI QSIG. In this release, digit forwarding is now supported in conjunction with ISDN PRI QSIG. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t4/qsigdf.htm
R2 signalling is an international signalling standard that is common to channelized E1 networks. However, there is no single signalling standard for R2. The ITU-T Q.400-Q.490 recommendation defines R2, but a number of countries and geographic regions implement R2 in entirely different ways. Cisco addresses this challenge by supporting many localized implementations of R2 signalling in its Cisco IOS software.
The Radio Frequency Interface (RFI) MIB feature is for DOCSIS-compliant radio frequency interfaces in cable access routers and cable access router termination systems. On the cable access router, RFI MIB entries provide the following features:
The RFI MIB includes tables describing both the cable access router termination system and the cable access router side of the cable interface. All cable access router tables are implemented.
Part of the Cisco SS7 Dial Access Solution (DAS), the Cisco Redundant Link Manager (RLM) provides link management over multiple IP networks, so that your Cisco SS7 DAS can tolerate a single point of failure.
By using the RLM functionality, the Q.931 signalling protocol and other proprietary protocols are transported on top of multiple redundant links between a telephony controller and the media gateways (MGWs).
A feature enhancement to RLM for this Cisco SS7 DAS release is redundancy at the link and telephony-controller level. When each RLM group has multiple telephony controllers associated with a MGW, a telephony-controller priority and a link priority are examined by the RLM client during failover, ensuring improved control handling. The RLM client is an MGW running RLM software.
The RLM client on the MGW supports both versions of RLM functionality:
After installation, the RLM client defaults to Version 2; however, you can choose a different version by using a CLI configuration command. Once an RLM version is selected, all RLM groups on a given MGW use the functionality of the selected version.
The RLM feature is backward compatible on the telephony-controller, but only one version of the RLM client can run on a given MGW. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rlm_123.htm
Resource Pool Management (RPM) diagnostics can now be run at start up, from the command line, or from the Scheduler. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/rpmdiags.htm
Part of the Cisco SS7 DAS, the Cisco Resource Pool Manager Server (RPMS) communicates with the RPM component of the MGWs to enable telephone companies and ISPs to count, control, bill, and manage resources centrally for wholesale and retail dial network services. RPM is configured across multiple MGW stacks using one or more external RPMS.
The Cisco RPMS provides the following services:
Cisco RPMS offers three major functions:
Cisco Resource Pool Manager (RPM) enables telephone companies and ISPs to share dial resources for wholesale and retail dial network services in a single network access server or across multiple network access server stacks. With Cisco RPM, service providers can count, control, and manage dial resources and provide accounting for shared resources when implementing different service-level agreements.
RPM can be configured in one or more standalone Cisco network access servers, or, optionally, across multiple network access server stacks by using one or more external Cisco RPMSs.
The Cisco RPM is ideal for combining retail and wholesale dial services using Cisco AS5200, AS5300, and AS5800 network access servers. Call management and call discrimination can be configured to occur before the call is answered. Dial customers are differentiated by the use of configurable customer profiles that are based on the DNIS and the call type determined at the time of an incoming call. When a call arrives at the network access server, the DNIS and call type are matched against a table of disallowed calls. If the DNIS and call type match an entry in this table, the call is rejected. Call discrimination can be used to manage the billing of calls to different types of resources.
When management by VPDN is configured, a VPDN group includes the information needed to set up or reject a VPDN session. VPDN setup can be based on the DNIS received during call setup, or on the domain name after the call is answered. Load balancing is used to achieve full usage of VPDN tunnels. The VPDN group can also serve as the "customer profile" when all calls are answered and sessions are identified and limited by domain name instead of DNIS.
To support data over voice bearer service (DoVBS), service providers use DNIS to direct calls to the appropriate resource. When a digital call arrives at the network access server through the voice network, it terminates on an HDLC controller rather than on a modem.
Direct remote services is an enhancement to Cisco RPM that enables service providers to implement wholesale dial services without using VPDN tunnels. A customer profile that has been preconfigured with a PPP template to define the unique PPP services for the wholesale dial customer is selected by the incoming DNIS and call type. At the same time, the DNIS is used to select AAA server groups for authentication/authorization and for accounting for the customer. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/rp1206ta.htm
RSVP works together with WFQ to give priority to packets that fall into a reservation within RSVP so that the packets enter the output queue and cable network before other packets.
The Response Time Reporter (RTR) feature allows you to monitor network performance, network resources, and applications by measuring response times and availability. RTR statistics can be used to perform troubleshooting, problem notifications, and preproblem analysis. The RTR enhancements extend IP support, such as ToS, and allow you to measure various types of IP traffic, such as UDP, TCP, and HTTP. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rtrenh.htm
Cisco IOS Release 12.1 supports RFC 1483 and enables the transfer of network interconnect traffic over ATM AAL5, using Logical Link Control (LLC) encapsulation. RFC 1483 defines an encapsulation type for transferring LAN data via ATM networks.
All LAN protocols that use the LLC format and run on Ethernet, Token Ring, or ATM networks are encapsulated in LLC data packets transported via ATM networks. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rfctr.htm
A routing configuration for the Cisco uBR904 and uBR924 cable access routers is most likely used when the cable access router is being added to an existing personal computer network. If set to support routing mode, the Cisco uBR904 or uBR924 cable access router will automatically configure the headend's IP address as its IP default gateway. When the IP host-routing is being configured, this automatic configuration of the headend's IP address as its IP default gateway will allow the Cisco uBR904 cable access router to send packets not intended for the Ethernet interface to the headend.
RIP V2 routing is useful for small internetworks in that it enables optimization of NIC-assigned IP addresses by defining VLSMs for networkaddresses, and it allows CIDR addressing schema.
The Token Ring VLAN support on the RSM enables a Catalyst 5000 switch to provide the functionality of bridging and multiprotocol routing for Token Ring VLANs. The installation of an RSM in a Catalyst 5000 supplements the existing switching capabilities with the functionality of a standalone router that performs inter-VLAN routing and bridging. If the Token Ring RSM is associated with a VIP2 board, it provides direct external network connections through a variety of media using the standard port adapters on the VIP2 and offers functionality similar to a Cisco 7500 series router.
The RSM module can either route or bridge Token Ring packets, thereby functioning as a router or as a bridge. In Cisco IOS Release 12.1, both Advanced Peer-to-Peer Networking (APPN) and DLSW+ are supported on the RSM's Token Ring VLANs. Remote source-route bridging (RSRB), however, is not supported on the RSM.
The RSVP to ATM QoS networking feature provides support for Controlled Load Services using RSVP over an ATM core network. This feature requires the ability to signal for switched virtual circuits (SVCs) across the ATM cloud in response to RSVP reservation messages. To meet this requirement, RSVP over ATM supports mapping of RSVP sessions to ATM nonbroadcast multiaccess (NBMA) SVCs.
RSVP over ATM allows you to configure an interface or subinterface to dynamically create SVCs in response to RSVP reservation requests. To ensure defined QoS, these SVCs are established having QoS profiles consistent with the mapped RSVP flowspecs. To further support QoS, this feature allows you to configure the IP Precedence and ToS values to be used for packets that conform to or exceed QoS profiles. Moreover, it allows you to attach DWRED group definitions to the (PA-A3 ATM port adapter) interface to support per-VC DWRED drop policy, which ensures that if packets must be dropped, then best-effort packets are dropped first and not those that conform to the appropriate QoS determined by the RSVP token bucket. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rsvpatm.htm
In large cable modem installations, cable debug commands need to be scalable and designed to provide the most information in the least amount of screen space. Large cable modem installations also need to limit the number of cable debug messages generated every second. Cisco limits the number of debug messages generated by counting the number of messages in the console output queue. If the number of messages in the queue exceeds an internally selected threshold, the uBR7200 series router will generate a message indicating that debugging will be disabled until the console output queue is empty.
In past Cisco IOS releases, authentication and accounting services (otherwise referred to as AAA services) have been implemented in one of the following methods:
With Cisco IOS Release 12.0(7)T, you can now select an AAA server group to which authentication and accounting requests will be sent by using DNIS. With this new Selecting AAA Server Groups Based on DNIS feature, you can specify the same server group for AAA services or a separate server group for each AAA service. You can now configure authentication and accounting on different physical devices and provide failover backup support.
This feature obsoletes the previous Cisco IOS Release 12.0(2)T AAA DNIS Map feature. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/serdnis6.htm
The Service Assurance (SA) Agent is both an enhancement to and a new name for the Response Time Reporter (RTR) feature that was introduced in Cisco IOS Release 11.2. The feature allows you to monitor network performance by measuring key Service Level Agreement metrics such as response time, network resources, availability, jitter, connect time, packet loss, and application performance.
With Cisco IOS Release 12.0(5)T, the SA Agent provides new capabilities that enable you to monitor the following:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/saaoper.htm
The Cisco voice service provider features include enhancements made to the functionality and configuration of both the gateway and the Voice over IP (VoIP) gatekeeper. The architecture of these features provides the QoS, stability, and functionality necessary for carrier class, real-time IP communications services.
This document contains a basic description of the H.323 VoIP gateway in addition to features required to implement the applications to run VoIP in a service provider environment. The features address the service provider needs to offer security, billing, scaling, and reliability.
The Cisco VoIP gateway is a high-performance H.323-compliant gateway optimized for VoIP applications. Supporting up to two T1/E1 digital channels, it connects with existing telephones and fax machines through the PSTN, key systems, and PBXs, making the process of placing calls over the IP network transparent to users.
The gateway capability allows the Cisco VoIP gateway to function as an H.323 endpoint. Therefore, the gateway provides admission control, address lookup and translation, and accounting services.
The gatekeeper manages H.323 endpoints in a consistent manner, allowing them to register with the gatekeeper and to locate another gatekeeper. The gatekeeper provides logic variables for proxies or gateways in a call path to provide connectivity with the PSTN, to improve QoS, and to enforce security policies. Multiple gatekeepers may be configured to communicate with one another, either by integrating their addressing into DNS, or via Cisco IOS configuration options.
Historically when a modem went offline, users could not tell why. The show cable modem command has been enhanced to make diagnosing offline modems easier. Now you can see what the status of modem was before it went offline. This additional information now includes the following:
The show controller upstream command has been enhanced to display the following average percentage information on specified cable interfaces:
The show interface cable command now displays per-SID counters for the number of bandwidth requests received and granted. This information will display in verbose mode.
The show cable modem detail command has been expanded to display SNR data on a per-modem basis. Previous versions of the show cable modem detail command only showed SNR data on a per-interface basis.
The Cisco uBR924 cable access router supports Simple Gateway Control Protocol (SGCP). SGCP is an out-of-band signalling protocol that interactswith the external Call Agent (CA) to establish telephone calls. SGCP eliminates the need for a dial plan mapper and static configuration on the router to map IP addresses to telephone numbers because this function is provided by the external CA.
The Cisco uBR924 cable access router supports SGCP residential gateway (RGW), as opposed to trunking gateway (TGW), which controls the telephone call.
Simple Gateway Control Protocol (SGCP) version 1.0 enables intelligent, external call agents to control gateways in a VoIP environment. Gateways include trunking gateways and residential gateways. Call agents include TransPath and third-party products. The SGCP for the Cisco AS5300 feature is intended for use in large IP networks typical of competitive local exchange carriers and Internet exchange carriers.
The SGCP MIB supports configuration, performance, and fault management of the SGCP interface. The SGCP MIB components are as follows:
Signalling System 7 (SS7) is a worldwide standard for switch-to-switch signalling in the Public Switched Telephone Network (PSTN). The Cisco SC2200 signalling controller provides centralized functions for adding SS7 interfaces to remote access points of presence (POPs). The Cisco SC2200 signalling controller works together with Cisco access servers (AS5800, AS5300, and AS5200) to create a virtual switch, which functions from a signalling perspective as a terminating and originating end office with SS7. Cisco access servers provide the interface from the circuit switched network to the data network. The protocol architecture for communication between the Cisco SC2200 signalling controller and access servers provides for reliable signalling over an IP infrastructure. This feature provides the control protocol for Cisco access servers to support the Cisco SS7 dial access solution.
The SLIP-PPP Banner feature enables you to configure the banner that is displayed when making a SLIP connection, which improves compatibility with non-Cisco SLIP dialup software.
The Banner Tokens feature introduces the use of tokens to all existing banner commands. Tokens allow you to display current information from the configuration, such as the router host name, IP address, encapsulation type, and MTU size. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/tokenban.htm
The smart-init feature is an extension to the existing memory split program of the Cisco IOS software running on Cisco 3600 series routers. It computes iomem size by looking at the network modules installed in the system and uses this iomem for carrying out the memory split. Also, compatibility with older Cisco IOS configurations is maintained by retaining support for the memory-size configuration command. The user can disable smart-init and set iomem percentage to the required value by using the memory-size configuration command.
SNASw provides an easier way than earlier methods to design and implement networks with SNA routing requirements. Previously, this network design was accomplished using Advanced Peer-to-Peer Networking (APPN) with full network node (NN) support in the Cisco router. This type of support provided the SNA routing functionality needed, but was inconsistent with the trends in enterprise networks. The corporate intranet is replacing the SNA WAN. Enterprises are replacing their traditional SNA network with an IP infrastructure that supports traffic from a variety of clients, using a variety of protocols, requiring access to applications on a variety of platforms, including SNA applications on enterprise servers.
Although SNA routing is still required when multiple servers must be accessed, the number of nodes required to perform this function is decreasing as the IP infrastructure grows and as the amount of native SNA traffic in the network decreases.
SNASw enables an enterprise to develop their IP infrastructure, while meeting SNA routing requirements. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/snaswit2.htm
Simple Network Management Protocol version 3 (SNMPv3) addresses issues related to the large-scale deployment of SNMP for configuration, accounting, and fault management. SNMP is predominantly used for monitoring and performance management. The primary goal of SNMPv3 is to define a secure version of SNMP. SNMPv3 also facilitates remote configuration of the SNMP entities, which make remote administration of SNMP entities a much simpler task. SNMPv3 builds on top of SNMPv1 and SNMPv2 to provide a secure environment for the management of systems and networks.
SNMPv3 provides an identification strategy for SNMP devices to facilitate communication only between known SNMP strategies. Each SNMP device has an identifier called the SNMP EngineID that is a copy of SNMP. Each SNMP message contains an SNMP EngineID. SNMP communication is possible only if an SNMP entity knows the identity of its peer SNMP device.
SNMPv3 also contains a security model or security strategy that exists between an SNMP user and the SNMP group to which the user belongs. A security model may define the security policy within an administrative domain or an intranet. The SNMPv3 protocol consists of the specification for the User-Based Security Model (USM).
Definition of security goals where the goals of message authentication service includes the following protection strategies:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/snmp3.htm
The spe configuration command enables you to download firmware into your modems. When the access server is booted, the spe command controls the location from where the firmware image is downloaded to the service processing element (SPE). An SPE unit is defined as the smallest software downloadable unit. For Microcom, an SPE is an individual modem; for MICA an SPE is either 6 or 12 modems, depending on whether the MICA module is single or double density. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/spe1206t.htm
The following spectrum management enhancements are available in the Cisco uBR7200 series universal broadband routers:
The Cisco SS7/CCS7 Dial Access Solution (DAS) feature provides centralized functions for adding Signaling System 7 (SS7) interfaces to large dial points of presence (POPs). This Non-Facility Associated Signaling (NFAS) functionality provides a full integration of dial access capabilities within the circuit-switched network infrastructure and provides significant savings on switching interface costs while simultaneously reducing trunking costs. Using the NFAS functionality means that all your T1 and E1 channels are used for voice and data while the associated signalling is carried separately over the SS7 network. In addition, you can cost-effectively scale your network from a few hundred to thousands of ports because you do not need to add a D channel for every additional port.
The Cisco SS7/CCS7 DAS feature allows feature carrier customers to connect their Cisco AS5300 access servers to the PSTN directly, using SS7 signalling protocols. The SS7 signalling links terminate on a separate UNIX system called the Signaling Controller (SC2200). The SC2200 maps incoming calls, which are signaled via SS7, to bearers on the access servers. The access servers and SC2200 interact to set up and tear down calls using an extended Q.931 protocol over Q.921 and User Datagram Protocol (UDP). In this manner, the Cisco AS5300 access servers and the SC2200 form a system that emulates a terminating or originating end-office telephone switch in the Public Switched Telephone Network (PSTN).
This feature adds two capabilites to Cisco IOS software:
The Store and Forward Fax feature enables Cisco AS5300 access servers to send and receive faxes across packet-based networks. This feature is an implementation of the RFC 2305 proposed standard from the IETF, which is the same as the T.37 recommendation from the ITU. With this feature, your access server becomes a multiservice platform, supplying both data and fax communication. Store and Forward Fax provides the following services:
Store and Forward Fax functionality is facilitated through SMTP. Additional functionality is provided in this product to provide confirmed delivery, capabilities negotiation, and session delivery, using existing SMTP mechanisms, such as Extended Simple Mail Transfer Protocol (ESMTP), for those features.
RSVP is a signalling mechanism that supports request of specific levels of service such as reserved bandwidth from the network. RSVP and its service class definitions are largely independent of the underlying network technologies. This independence requires that a user define the mapping of RSVP onto subnetwork technologies.
The Subnetwork Bandwidth Manager (SBM) feature answers this requirement for RSVP in relation to IEEE 802-based networks. SBM specifies a signalling method and protocol for LAN-based admission control for RSVP flows. SBM allows RSVP-enabled routers and Layer 2 and Layer 3 devices to support reservation of LAN resources for RSVP-enabled data flows. The SBM signalling method is similar to that of RSVP itself. SBM protocol entities have the following features:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/sbm.htm
The primary purpose of this card is to provide aggregation of channelized interfaces into the CT3 on a single T3 facility. This will allow for increased port density, lower per port cost, ease of deployment, ease of provisioning, and so on. which all lead to an overall lower cost of ownership to the customer.
T3 refers to a 672-channel interface as defined in the North American T-Carrier Hierarchy. T-Carrier represents one of several multiplexed carrier systems, three of which are listed. Each T-Carrier level is also commonly referred to by an appropriate digital signal (DS) level, which is also listed. The following provides the overall data rate and channel capacity of each level in the North American T-Carrier Hierarchy:
The T2 standard is very seldom (if ever) used, but services based on T1 and T3 are widely available. The current CT3 product offers individual T1 interfaces for a total of 24 each. Inclusion of a T3 interface to the product offering improves port density in that 28 T1s will be supported in the same chassis.
Due to the physical constraints of the CT3 chassis, a CT3 interface card is the only way to fully utilize extra modem capacity. To double the CT3 capacity to each T3 or 1344 modem, two CT3 cards per CT3 chassis would be required.
Cisco 800 series routers now support the TACACS+ through Telnet. TACACS+ is a Cisco proprietary authentication protocol that provides remote access authentication and related network security services, such as event logging. User passwords are administered in a central database rather than in individual routers.
The TACACS+ security application provides the centralized validation of users attempting to gain access to a router or network access server. TACACS+ services are maintained in a database on a TACACS+ daemon that typically runs on a UNIX or Windows NT workstation. The goal of TACACS+ is to provide a methodology for managing multiple network access points from a single management service. You must have access to and must configure a TACACS+ server before the configured TACACS+ features on your network access server are available.
The TACACS+ feature is supported by the AAA facility, which is configured at individual routers. However, Cisco 800 series routers do not support the RADIUS or Kerberos protocols. The TACACS+ AAA services are defined as follows:
For additional information, see and the Cisco 800 Series Routers Software Configuration Guide, Cisco 805 Router Software Configuration Guide, and the security-related configuration guides and command references located on CCO and the Documentation CD-ROM.
The Tag Switch Controller (TSC) is a tag switch router (TSR) that controls the operation of a separate ATM switch. Together, the router and ATM switch function as a single ATM-TSR. A Cisco 7200 or 7500 series router acts as the TSC and a Cisco BPX 8600 service node (8620 wide-area switch or 8650 IP+ATM switch) or a partner switch acts as the VSI-controlled ATM switch. The TSC controls the ATM switch using the Cisco Virtual Switch Interface (VSI), which runs over an ATM link connecting the two. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/tsc12_3.htm
Tag switching is a Cisco-developed technology that implements a next-generation architecture for the Internet backbone and large intranets. Tags placed on the fronts of packets contain forwarding information used for making switching decisions and applying network services.
Tag switching has become the foundation for flexible Layer 3 VPNs, QoS handling, and traffic engineering. It also forms the basis for the emerging IETF standard for MPLS.
A tag switching infrastructure combines with advanced routing protocol capabilities to define IP VPNs by selectively advertising IP reachability information to just those subscribers within the same VPN or extranet, thus keeping different VPN traffic logically separate. The subscribers are then all connected via tag switch paths (TSPs).
Forwarding is based entirely upon the assigned tag values (rather than IP destination prefixes), eliminating the requirement for uniqueness in the IP addresses that are used. This feature means subscribers to different VPNs need not concern themselves with the problems that would otherwise occur when connecting networks with different subnetworks into an integrated network.
The Debit Card for Packet Telephony on Cisco Access Platforms feature requires the use of both audio files and TCL scripts. Unzip and download the files to your TFTP server.
In addition, download the audio files and TCL scripts from the "Access Products Service and Support" site on CCO at the following "TCLWare" location:
http://www.cisco.com/kobayashi/sw-center/sw-access.shtml
The Telco Return for the Cisco uBR7200 Series Cable Access Router feature provides software support for telephone return in a cable-routed system. Telephone return in a cable environment is the part of the cable network that connects the cable modem of a subscriber with the headend cable router over standard phone lines (as opposed to an all-cable network connecting the headend router with cable modems). Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/telco125.htm
The telco return feature for the uBR7200 series cable router now supports full RADIUS realm configuration. Now you can use any valid domain name in the telco-return radius-realm command.
Implement access lists based on the time of day by creating a time range that defines specific times of the day and week. The time range is identified by a name, and then referenced by a function, so that those time restrictions are imposed on the function itself.
Currently, IP and IPX extended access lists are the only functions that can use time ranges. The time range allows the network administrator to define when the permit or deny statements in the access list are in effect. Prior to this feature, access list statements were always in effect once they were applied. Both named or numbered access lists can reference a time range. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/timerang.htm
Time-division multiplex (TDM) hairpinning is supported for voice calls on the Cisco AS5300. TDM hairpinning is the connection of an incoming and an outgoing voice call on the same Cisco AS5300 via the TDM bus. The current hairpinning functionality requires converting calls to and from packet form with a pair of DSPs.
The advantages of TDM hairpinning over conventional DSP-based hairpinning are as follows:
This new capability is transparent to users because the TDM code handles the hairpinning process. As a result of this internal processing, there are no new or changed CLI commands.
This feature adds a time-of-day service to the cable headend system. Standalone cable headend systems can obtain the correct time of day from larger systems as part of a low-maintenance, background function. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/time1205.htm
Token Ring Multiprotocol over ATM (MPOA) allows Token Ring hosts in an ATM network to communicate over alternate paths (called shortcuts) through the ATM network, which bypasses intermediate router hops that would otherwise be encountered in the default path.
Token Ring MPOA is an extension to LANE. Using the Next Hop Resolution Protocol (NHRP), and MPOA server (MPS) on the router, and MPO clients (MPCs) on the ATM edge devices, a direct virtual channel connection (VCC) between the ingress and egress edge devices is established. Token Ring MPOA allows Token Ring LANE clients to forward unicast IP packets between subnets to other Token Ring LANE clients through this shortcut VCC path on the ATM network. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/mpoatr.htm
Triggered extensions to IP RIP increase efficiency of RIP on point-to-point, serial interfaces.
Routers are used on connection-oriented networks to allow potential connectivity to many remote destinations. Circuits on the WAN are established on demand and are relinquished when the traffic subsides. Depending on the application, the connection between any two sites for user data could be short and relatively infrequent.
There were two problems using RIP to connect to a WAN:
To overcome these limitations, triggered extensions to RIP cause RIP to send information on the WAN only when there has been an update to the routing database. Periodic update packets are suppressed over the interface on which this feature is enabled. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/trigrip.htm
IPSec requires a peer router to be statically configured before an Internet Key Exchange (IKE) is initiated. An IKE is necessary to encrypt and decrypt packets. The Cisco router crypto maps require the capability to dynamically determine the IPSec peer. The Tunnel Endpoint Discovery protocol automatically discovers remote tunnel endpoints and enables secure IPSec communications.
Dynamic tunneling endpoint discovery allows IPSec to scale to larger networks by reducing thenumber of multiple encryptions, reducing the setup time, and allowing for simple configurations on participating peer routers. Each node has a simple configuration that defines the local network that the router is protecting and the IPSec transforms required, if any. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/ted.htm
The upstream address verification enhancement prevents the spoofing of IP addresses by verifying that each upstream data packet comes from the cable modem known to be associated with the source IP address in the packet. The cable source-verify [dhcp] cable interface command specifies that DHCP lease query requests are sent to verify any unknown source IP address found in upstream data packets. This feature requires a DHCP server that supports the new LEASEQUERY message type.
The Cisco uBR7200 series universal broadband router supports buffering both upstream and downstream grants to cable modems that are exceeding their allocated bandwidth. This strategy helps to avoid the TCP timeouts and the retransmission of the associated packets, which would further degrade overall throughput.
Previously, whenever a cable modem was found to be exceeding its configured peak upstream or downstream rate, the Cisco uBR7200 series universal broadband router would simply drop the bandwidth requests from that cable modem until it could be allowed to send more data.
The cable downstream port number rate-limit token-bucket shaping and cable upstream port number rate-limit token-bucket shaping commands configure the Cisco uBR7200 series universal broadband router to perform rate shaping by buffering the grants for rate-exceeded modems.
The Video over ATM Switched VCs feature expands the capabilities of the Cisco MC3810 multiservice access concentrator to provide cost-effective, dynamic, and flexible videoconferencing system support. Using a plug-in video dialing module (VDM) to provide an EIA/TIA-366 dialing interface to an H.320 video codec, the Cisco MC3810 automatically accepts dial-out requests from the video system. The codec connects to one of the Cisco MC3810 serial ports and also to the Cisco MC3810 EIA/TIA-366 dialup port.
The current feature also improves PVC support by permitting PVC connections with automatic connection through a serial port. Each codec must place a call to the other videoconferencing system prior to the expiration of the video codec timeout period (set on the codec, usually 1 minute).
Using a video dial map, each system reconciles the dialed number with a PVC that has already been configured, allowing fast connectivity.
Service providers, educational organizations, and enterprises can concentrate streams for video with packet data on a single high-speed ATM link without a separate ATM access multiplexer. Here are some features of the Cisco ATM SVC implementation:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/atmsvc/atmvi_t6.htm
The Virtual Console feature allows you to access dial and router shelves connected to a system controller. During a system controller session, you can connect to a router or dial shelf at the same privilege level as the current system controller session.
By entering one command, you can Telnet directly to a shelf, provide a username and password, and then go to the same privilege level as the system controller.
The Cisco 800 series routers support the connection of analog telephones, fax machines, and modems. These devices are connected to basic telephone services through the ISDN line. The routers support the following supplementary services, which can be ordered from the telephone service provider:
The ISDN voice priority feature controls the priority of data and voice calls for the devices connected to the router telephone ports. If an ISDN circuit endpoint is busy with a data call or calls, and either a voice call comes in or you attempt to place a voice call, the data call is handled per the voice priority setting.
The Voice over ATM Switched VCs feature allows the Cisco MC3810 to transfer voice data dynamically and as needed, without using the resources required for static, manually provisioned permanent virtual circuits (PVCs). An SVC connection is initiated for each call, and each request includes bandwidth and quality-of-service (QoS) information required for the connection. SVCs are ideal for networks that are highly interconnected, where scalability is essential, and in situations where traffic is sporadic. In addition, service providers often offer more advantageous, usage-based pricing options for SVCs.
VoATM using SVCs on the Cisco MC3810 includes all of the voice features that the Cisco MC3810 supports for PVCs and for Frame Relay transport. Like other Cisco voice implementations, VoATM using SVCs is based on dial peers and uses ATM adaptation layer 5 (AAL5).
ATM SVC service operates much like X.25 SVC service, although ATM allows much higher throughput. It requires a signalling protocol between a router or a multiservice access concentrator and an ATM switch. The ATM signalling software provides a method of dynamically establishing, maintaining, and clearing ATM connections at the User-Network Interface (UNI). In UNI, the router serves as the user and the ATM switch is considered the network. The router does not perform call-level routing. Instead, the ATM switch does the ATM call routing, and the router directs packets through the resulting circuit. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/atmsvc/atmvo_t6.htm
When multiple sets of flows are being handled by WFQ, the algorithm provides the low weight/reserved queued voice packets with higher priority but only until some of the other data packets have waited to the point where it is now their turn to be dequeued. Even if interleaving is active, the WFQ algorithm will not dequeue a voice packet until these data packets are sent, which can cause voice quality problems.
The solution to the voice quality problems consists of adding a special queue at the PVC level where all VoFR packets will be queued. This special queue runs in parallel to the WFQ and is serviced before any of the WFQs. In Cisco IOS Release 12.1, reserved queues are no longer required to support VoFR. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/vofrque.htm
The VoFR capabilities that were introduced on the Cisco MC3810 multiservice access concentrator beginning with Cisco IOS Release 11.3 are now extended to the Cisco 2600 series, 3600 series, and 7200 series router platforms. The following additional functionality is supported in Release 12.1:
When VoFR is implemented on a Cisco router, the router is able to carry voice traffic, such as telephone calls and faxes, over a Frame Relay network.
This VoFR feature also adds support for full FRF.11 and FRF.12 compliance to the Cisco MC3810, and is backward-compatible with earlier versions of the Cisco MC3810, which used a fragmentation format based on an early draft version of FRF.12.
|
Note Using this feature, the Cisco 7200 series routers can only serve as tandem routers in the Frame Relay environment, and cannot originate or terminate calls. |
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t4/120tvofr/
The Voice over IP Enhancements for the Cisco AS5300/Gateway feature implements voice support on the Cisco AS5300 using DSPM-542 DSP modules. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/sousa125.htm
VoIP enables a Cisco AS5300 access server to carry voice traffic (for example, telephone calls and faxes) over an IP network. VoIP is primarily a software feature; however, to use this feature on the Cisco AS5300, you must install a VoIP feature card (VFC). The VFC utilizes the Cisco AS5300 quad T1/E1 PSTN interface and LAN or WAN routing capabilities to provide up to a 48/60-channel gateway for VoIP packetized voice traffic. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/voip5300/
The Cisco 1750 router is a voice-and-data capable router that provides Voice over IP (VoIP) functionality and can carry voice traffic (for example, telephone calls and faxes) over an IP network. Cisco voice support is implemented using voice packet technology.
In VoIP, the digital signal processor (DSP) segments the voice signal into frames and stores them in voice packets. These voice packets are transported by using IP in compliance with the International Telecommunications Union-Telecommunications (ITU-T) specification H.323, the specification for sending multimedia (voice, video, and data) across a network.
Because VoIP is a delay-sensitive application, you need to have a well-engineered, end-to-end network to use it successfully. Fine-tuning your network to adequately support VoIP involves using a series of protocols and features to improve quality of service (QoS). Traffic shaping considerations must also be considered to ensure the reliability of the voice connection.
To use the VoIP feature, you must have voice interface cards (VICs) installed in the Cisco 1750 router. For information about installing a VIC in the router, see the Cisco WAN Interface Cards Hardware Installation Guide. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/voip1750.htm
QSIG Private Network Transparency provides the Cisco AS5300 the capability to relay QSIG messages transparently across H.323 VoIP networks for inter-PBX/KTS signalling. The feature also provides the ability for internetworking between non-QSIG signalling (for example, E&M, R2, and Q.931) and QSIG signalling for basic calls.
QSIG transparency provides support for ISDN supplementary features such as call waiting and caller identification delivery. The feature supports ISDN supplementary services defined ECMA-141, QSIG Data Link Layer, and Standard-142, and QSIG Basic Call Control by providing network feature transparency. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/cfios/cfselfea/0125qsig.htm
The VPDN Group Reorganization feature organizes the VPDN group commands into a new hierarchy. Along with one of the four VPDN services, VPDN groups can now support the following LNS VPDN services:
VPDN groups can now support the following LAC VPDN services:
A VPDN group can act as either an LNS or a LAC, but not both. But individual routers can have both LNS VPDN groups and LAC VPDN groups.
To facilitate this reorganization, the VPDN group now contains the four corresponding command modes. These new command modes are accessed from VPDN group mode; therefore, they are generically referred to as VPDN subgroups. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/vpdngrp.htm
In a VPDN that uses remote AAA, when a user dials in, the access server that receives the call forwards information about the user to its remote AAA server. With basic VPDN, the access server only sends the domain name of the user (when performing domain name-based authentication) or the telephone number the user dialed in from (when performing DNIS-based authentication).
The VPDN per-User Configuration feature sends the entire structured username to the AAA server the first time the router contacts the AAA server, which enables the Cisco IOS software to customize tunnel attributes for individual users that use a common domain name or DNIS.
Previously, Cisco IOS sent only the domain name or DNIS to determine VPDN tunnel attribute information. Then, if no VPDN tunnel attributes were returned, Cisco IOS sent the entire username string. Because of this behavior, there was no way to define specific tunnel attributes for a particular user within a domain. It also limited the types of connections that were possible in a RADIUS proxy VPDN roaming environment. All VPDN users were forwarded to the tunnel endpoint, even if they just needed generic Internet access. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/vpdnpert.htm
The dynamic crypto map command is one of the PIX IPSec network security commands. IPSec provides security for transmission of sensitive information over unprotected networks such as the Internet.
The dynamic crypto map command is used to create policy templates that are used when processing negotiation requests for new security associations from a remote IPSec peer, even if you do not know all of the crypto map parameters required to communicate with the remote peer (such as the IP address for the peer). The dynamic crypto map allows you to accept requests for new security associations from previously unknown peers. These requests, however, are not processed until the ISAKMP (IKE) authentication has completed successfully.
When the firewall receives a negotiation request via IKE from another IPSec peer, the request is examined to see if it matches a crypto map entry. If the negotiation does not match any explicit crypto map entry, it will be rejected unless the crypto map set includes a reference to a dynamic crypto map.
If the firewall accepts the request from the peer, at the point that it installs the new IPSec security associations, it also installs a temporary crypto map entry. This entry is filled in with the results of the negotiation. At this point, the firewall performs normal processing, using this temporary crypto map entry as a normal entry, even requesting new security associations if the current ones are expiring (based on the policy specified in the temporary crypto map entry). After all of the corresponding security associations expire, the temporary crypto map entry is removed.
Dynamic crypto map sets are not used for initiating IPSec security associations. However, they are used for determining whether traffic should be protected.
|
Note The only parameter required in a dynamic crypto map command is set transform-set. All other parameters are optional. |
The VPN Tunnel Management feature provides network administrators with two new functions for managing VPN tunnels, as follows:
These functions can be used on either end of a VPN tunnel—the network access server or on the home gateway.
When this feature is enabled, Multichassis Multilink PPP (MMP) L2F tunnels can still be created and established. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/vpnmng.htm
The Web Cache Communications Protocol Version 2 (WCCPv2) enables Cisco IOS routing platforms to transparently redirect content requests (for example, web requests) from clients to a locally connected Cisco Cache Engine (or Cache Cluster) instead of the intended origin server. When a Cache Engine receives such a request, it attempts to service it from its own local cache if the requested information is present. If not, the Cache Engine issues its own request to the originally requested origin server to get the required information. When the Cache Engine retrieves the requested information, it forwards it to the requesting client and caches it to fulfill future requests, thus maximizing download performance and significantly reducing WAN transmission costs.
WCCPv2 provides enhancements to WCCPv1, including the following:
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/wccp.htm
Weighted Fair Queueing (WFQ) is a congestion management algorithm that provides priority management, but not strict prioritization for voice, during periods of traffic congestion.
WFQ offers a solution that provides consistent, fair response time, based on weights, to heavy and light traffic alike without adding excessive bandwidth. WFQ provides features such as traffic isolation and delay bandwidth guarantees. Implicit within WFQ is a strict priority queue that is created when WFQ is enabled. However, this queue cannot be used until the IP RTP Priority feature is enabled.
WRED enhances the RED algorithm of handling congestion conditions by allowing the administrator to specify preferential traffic handling for higher priority traffic (as defined by the IP precedence bits). Administrators can define the minimum and maximum queue depth thresholds and drop probabilities for each class of service.
WFQ feature performs priority output queueing and custom queueing to grant resources to important sessions when the network bandwidth is saturated; for example, priority could be given to digitized voice traffic to minimize delays. WFQ provides expeditious handling of high priority traffic while fairly sharing the remaining bandwidth between the lower priority traffic.
The X.25 specification for Closed User Groups (CUG) provides the following services:
|
Note Previously, Cisco supported only the ability to specify the CUG value but did not enforce restriction. Cisco currently enforces this security restriction. |
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/x25scugs.htm
As the number of users accessing the same host has grown, competition for these application resources has become a problem. ISPs have needed to increase the number of users they could support by increasing the number of X.25 lines to the host.
In order to support a large number of VCs to a particular destination, configuration of more than one serial interface to that destination was needed. When a serial interface is configured to support X.25, a fixed number of VCs is available for use.
Using a facility called "hunt-group" (the method for X.25 load balancing), a switch is able to view a pool of X.25 lines going to the same host as one address and assign VCs on an "idle logical channel" basis. With this feature, X.25 calls can be load-balanced among all configured outgoing interfaces to fully use and balance all managed lines. The benefits include, the choice of two load-balancing distribution methods (rotary or vc-count) and improved performance of serial lines. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/x25lbal.htm
XOT is X.25 Over TCP, Request For Comments (RFC) 1613. This allows X.25 packets to be sent over a Transmission Control Protocol/Internet Protocol (TCP/IP) network instead of a Link Access Procedure, Balanced (LAPB) link.
In essence, X.25 traffic is funnelled through an IP cloud (for example, by connecting two X.25 clouds that have no physical connection with a virtual TCP tunnel across the IP cloud).
When an incoming call is received that should be forwarded, two fields in the X.25 routing table are consulted to determine a remote X.25 route, the destination X.121 address and, optionally, the X.25 packet's Call User Data (CUD) field.
When the destination address and the CUD of the incoming packet fit the X.121 and CUD patterns in the routing table, the call is forwarded. You can also specify an XOT source that causes the XOT TCP connection to use the IP address of a specified interface as the source address of the TCP connection.
If, for instance, a loopback interface is specified for the XOT connection's source address, TCP can use a primary interface or any backup interface to reach the other end of the connection. However, if a physical interface's address is specified as the source address, the XOTconnection is terminated if that interface goes down.
Static routes are used over a packet-switched data network in order to reduce volume-based costs of the network. Until now, if two routers were connected via multiple X.25 links (a primary and a secondary), a router could not detect failure of the primary link. If a failure occurred, the data was not transferred to the second link because X.25 was unable to determine whether remote links were up or down. Therefore X.25 could not use an alternate connection to a destination.
The X.25 Remote Failure Detection feature is important for X.25 users because now, after a primary link failure, the router can establish a secondary link and continue sending data. This feature is a way for the router to detect a call failure and to use a secondary route to send subsequent packets to the remote destination, at the same time as making periodic attempts to reconnect to its primary link. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/x25rhfd.htm
Cisco offers an X.25 switch function that creates VC by connecting channels between X.25 class services. The following X.25 class services are supported:
The current Cisco implementation provides end-to-end acknowledgment, which means that flow control or window and packet size acknowledgment is between the originating and terminating DTE.
Acknowledgment is not local to the DTE and DTE, and the overall effect is low throughput. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/x25locac.htm
The following features are supported in Cisco IOS Release 12.1.
Cisco T1/E1 multiflex voice/WAN interface cards (VWICs) support voice and data applications in the Cisco 2600 and 3600 series routers. The VWICs offer the WIC and the VIC functionality in a variety of applications for enterprises and for service providers that supply customer premises equipment.
Multiflex VWICs support the following applications:
The following multiflex VWICs are available:
Multiflex VWIC features include the following:
|
Note You can use T1/E1 channels either for drop-and-insert or VoIP, but not both. |
The 3600 series OC-3 ATM network modules allow your Cisco 3600 series router to concentrate data, voice, and video traffic onto an ATM uplink. The OC-3 ATM network module is available in a data-only version, or by installing a Voice Processing Deck (VPD) expansion card, you enable traditional TDM voice transport over ATM. Table 82 lists the available models.
| Network Module | Description |
|---|---|
NM-1A-OC3MM | This network module has a multimode fiber, 155 Mbps OC-3 uplink port. |
NM-1A-OC3SMI | This network module has a single-mode intermediate reach fiber, 155 Mbps OC-3 uplink port (VPD). |
NM-1A-OC3SML | This network module has a single-mode long reach fiber, 155 Mbps OC-3 uplink port. |
The OC-3 ATM is a full function ATM network module designed for OC-3 high bandwidth data and voice/data integration applications over SONET/SDH at speeds of 155.520 Mbps (STM-1). The OC-3 ATM network module can combine router packets with constant bit rate data onto an ATM uplink. Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/oc3_fm.htm
The AS5800/voice gateway converts and routes voice and fax calls between traditional circuit-switched networks and packet-switched networks. When equipped with AS5800 Voice Feature Cards (TI C549 DSP-based Voice Feature Card) and an H.323 voice-enabled Cisco IOS feature license, the AS5800 serves as a high-performance, carrier-class, H.323-compliant voice gateway. In other words, it provides the conversion and routing of voice and fax calls between CO switches/PBXs and IP networks for service provider and enterprise applications. Although Cisco offers a variety of voice gateway solutions for carrying VoIP, ATM, and Frame Relay networks, the AS5800 series devices are specifically designed and optimized for IP applications.
The PA-A3 ATM port adapters (PA-A3-T3, PA-A3-E3, PA-A3-OC3MM, PA-A3-OC3SMI, and PA-A3-OC3SML) available on Cisco 7500 series routers now support the following new features:
The PA-A3 ATM port adapters support multiplexing of one or more VCs over a VP that is shaped at a constant bandwidth. To use this feature, you configure a permanent virtual path (PVP) with a specific virtual path identifier (VPI). Any VCs that are created subsequently with the same VPI are multiplexed onto this VP; the traffic parameters of individual VCs are ignored.
BRI VICs allow branch offices and enterprises to route incoming PSTN ISDN BRI calls over an IP network or send outgoing digital fax and voice calls over an IP network. Support for the ISDN BRI signalling type allows a Cisco 2600 or Cisco 3600 series router to provide voice access connectivity to either an ISDN telephone network or a digital interface on a PBX or key communications system. The voice or data also crosses an IP network to which the router connects. The VoIP feature enables the Cisco 2600 and Cisco 3600 series of modular routers to carry voice traffic simultaneously with data traffic.
As an enhancement to baseline privacy, Cisco uBR7200 series universal broadband routers can be configured for cable modem and multicast authentication using the RADIUS, an access server AAA protocol. This release also introduces support for additional vendor-proprietary RADIUS attributes.
When a cable modem comes online or when an access request is sent through a multicast data stream, the Cisco uBR7200 series universal broadband routers send relevant information to RADIUS servers for cable modem/host authentication. This feature can be configured on a per-interface basis.
IETF draft standard RFC 2138 defines the RADIUS protocol. RFC 2139 defines the corresponding RADIUS accounting protocol. Additional RFC drafts define vendor-proprietary attributes and MIBs that can be used with an SNMP manager.
The software for the MC12C and MC14C cable modem cards is a driver running on the Cisco uBR7200 series universal broadband routers. Using a PCI interface, the universal broadband router line card software interacts with the cable modem card. Data is passed back and forth as direct memory access (DMA) transfers from the Cisco uBR7200 memory to the cable modem card.
Additionally, the MC12C and MC14C cable modem cards support universal broadband router line card management and control with the modem card MIBs, MAC control software, and logical link management software based on DOCSIS standards.
For more information, see the Cisco uBR7200 Series Cable Modem Card Installation and Configuration publication.
The MC16B cable modem card is available for the Cisco uBR7200 series universal broadband router. The software for the MC16B modem card is a driver running on the router and interacts with the card using a PCI interface. Data is passed back and forth as DMA transfers from the Cisco uBR7200 memory to the MC16B card.
Additionally, the MC16B card supports universal broadband router line card management and control with the MC16 MIB, MAC control software, and logical link management software based on Multimedia Cable Network System Partners Ltd (MCNS) standards.
For more information, refer to the update to the Cisco uBR7200 Series Cable Modem Card Installation and Configuration for the MC16B EFT Card publication.
The software for the MC16C cable modem card is a driver running on the Cisco uBR7200 series universal broadband routers. Using a PCI interface, the universal broadband router line card software interacts with the MC16C cable modem card. Data is passed back and forth as DMA transfers from the Cisco uBR7200 memory to the MC16C cable modem card.
Additionally, the MC16C cable modem card supports line card management and control with the MC16C MIB, MAC control software and logical link management software, based on DOCSIS standards.
For more information, refer to the Cisco uBR7200 Series Cable Modem Card Installation and Configuration and Update to the Cisco uBR7200 Series Cable Modem Card Installation and Configuration for the MC16C Cards publications.
The MC16E cable modem card provides one downstream and six upstream connections to the cable network, similar to the MC16C cable modem card, except that it supports the ITU J.83 Annex A physical layer and the proposed EuroDOCSIS (Annex A) standard (Cable Labs ECR RFI-R-98036). The MC16E card has the following differences with the current MC16C card:
All cable interface commands have been updated for the MC16E cable modem card.
Cisco IOS Release 12.1 includes support for the Cisco 805 router, which offers flexibility to small offices requiring secure and manageable Internet, intranet, and corporate LAN access. The Cisco 805 router has a fixed hardware configuration with one 10BaseT Ethernet port and one serial port. The serial port can connect X.21, V.35, RS-232, RS-449, RS-530 and RS-530A DTE and DCE.
Cisco IOS Release 12.1 now includes support for the Cisco 1750 router. The Cisco 1750 router is a voice-and-data capable router that provides VoIP functionality and can carry voice traffic (for example, telephone calls and faxes) over an IP network. Cisco voice support is implemented using voice packet technology.
The Cisco 7100 series VPN router is a full-featured, high-end, integrated VPN solution melding high-speed, industry-leading routing with a comprehensive suite of VPN services. The Cisco 7100 series VPN router integrates key features of VPNs—tunneling, data encryption, security, firewall, advanced bandwidth management, and service level validation—to provide secure, scalable VPN platforms to better and more cost-effectively accommodate remote-access, remote-office, and extranet connectivity using public data services. The Cisco 7100 series VPN router offers specific hardware configurations optimized for VPN applications and network topologies. Embedded WAN and Fast Ethernet interfaces combined with high-performance routing and rich VPN services provide turnkey VPN routing solutions.
The Cisco 7100 series consists of two VPN routers, the Cisco 7120 and the Cisco 7140. The Cisco 7120 is the entry-level Cisco 7100 series VPN router, integrating high-performance, industry-leading routing with scalable VPN security and bandwidth management to provide cost-effective, comprehensive VPN solutions for larger regional offices and headquarters. The Cisco 7120 comes in six different models defined by WAN interface. The Cisco 7140 series provides superior routing and VPN services performance for the most demanding VPN deployments, and dual WAN interfaces and power supplies for increased VPN solution reliability. The Cisco 7140 comes in five different models defined by WAN interface.
The Cisco 7576, an extension of the industry-leading Cisco 7500 series router, is designed to meet the price and performance requirements of service provider and enterprise customers. It features greater density, performance, and system availability, while maintaining compatibility with the existing set of Cisco 7500 router interface processors.
Both routers within the Cisco 7576 are fully autonomous, and function as independent routers. This separation is achieved through a split backplane design, with each half supporting a separate set of independent Route Switch Processors (RSP-4), interface processors, port adapters, and Cisco IOS software images. The chassis arbiter is logically separated, and the Cisco 7576 power supply system load shares across both backplanes in a fully redundant configuration.
The Cisco uBR924 cable access router is a fully functional Cisco IOS router and standards-based bidirectional cable modem that gives a residential or small-office, home-office (SOHO) subscriber high-speed Internet or intranet access and packet telephone services via a shared two-way cable system and IP backbone network. The Cisco uBR924 is based on the current Multimedia Cable Network System partner Data-Over-Cable Service Interface Specifications standards.
The Cisco uBR924 cable access router connects computers, telephone equipment, and other customer premises devices at a subscriber site to the hybrid/fiber coax and IP backbone network of the service provider. Subscribers can access the Internet at speeds of up to 10 Mbps and make telephone calls—all using the same cable system that delivers broadcast TV signals.
The Cisco uBR924 is a compact device that supports the direct connection of up to four PCs and has the familiar features and programming interface of other routers in the extensive line of small- and medium-sized business product offerings form Cisco. The Cisco uBR924 provides packet data transport and NAT for TCP/IP applications between home or office computers and the cable headend.
The data compression AIM provides hardware-based compression and decompression of packet data transmitted and received on the serial network interfaces of Cisco 2600 series routers without occupying the port module slot, that might otherwise be used for additional customer network ports. Supported are the industry standard LZS and MPPC compression algorithms.
Digital T1 packet voice trunk network modules for the Cisco 2600 and 3600 series routers allow enterprises or service providers, which supply the equipped routers as CPE, to deploy digital voice and fax relay. These modules receive constant bit-rate telephony information over T1 interfaces and can convert that information into a compressed format, so that the information can be sent as VoIP.
The following high-density T1 network modules are available:
T1 digital voice over IP includes the following functionality:
The new Cisco 2620 and 2621 routers include built-in 10/100-Mbps ports on the main board. The Cisco 2620 provides one 10/100-Mbps port and the Cisco 2621 provides two 10/100-Mbps ports. The 10/100-Mbps ports include VLAN support and the ISL, TR-ISL encapsulation feature as part of the VLAN subsystem.
The Gigabit Ethernet Port Adapter (PA-GE) is a single-port port adapter that, when combined with the appropriate optical fiber cable and a Gigabit Interface Converter (GBIC), provides one Gigabit Ethernet (GE) interface that is compliant with the IEEE 802.3z specification. The GE interface on a PA-GE operates in full-duplex mode. The PA-GE is supported by the Cisco 7200 VXR routers. Please note that this port adapter is not currently supported by the fourth-generation VIP4. See the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/7200vx/72vxpa/7188page/index.htm
The High-Density Voice over IP Support for the Cisco AS5300 Gateway feature implements high-density voice support on the Cisco AS5300 by using DSPM-549 digital signal processor modules. When equipped with VFCs and voice-enabled Cisco IOS software, the AS5300/voice gateway supports carrier-class VoIP and fax over IP services.
High-density voice support increases the voice capacity of a Cisco AS5300 up to 120 channels. This increase in voice support provides the voice density of up to four T1 lines (96 voice or fax calls) or four E1 lines (120 voice or fax calls).
A fully configured voice-capable Cisco AS5300 router includes two voice carrier cards, each capable of supporting 60 concurrent sessions.
The IEEE 802.3z PA-GE is a single-port adapter that provides a full-duplex, IEEE 802.3z compliant GE interface. The PA-GE is supported on the Cisco uBR7246 VXR universal broadband router; it is not supported on the Cisco uBR7223 and Cisco uBR7246 routers.
The PA-GE port adapter supports the following IEEE 802.3z interfaces:
The GE-PA requires optical fiber cable and a GBIC appropriate to the interface being used.
With the optional BRI voice module (BVM) installed, the Cisco MC3810 multiservice access concentrator provides four ISDN BRI ports for connection to ISDN PBXs (PINXs). The BVM has four ISDN BRI ports for voice traffic. Each BRI port supports two voice channels (ISDN B channels) and one signalling channel (ISDN D channel). The BRI voice ports have the following features:
The multichannel DS1/PRI port adapter (PA-MC-4T1 and PA-MC-8T1 versions) is a single-wide module that integrates CSU functionality, DSU functionality, and DS0 channel support into Cisco uBR7200 series routers. The PA-8DSX-1 version integrates DS1 DSU functionality and DS0 channel support into the Cisco uBR7200 series routers.
The multichannel DS1/PRI port adapter provides four or eight independent T1 (100-ohm) connections via RJ-48C connectors. Each multichannel DS1/PRI port adapter can provide up to 128 separate full-duplex HDLC DS0, fractional, or full T1 channels.
The multichannel E1/PRI port adapter (PA-MC-8E1/120) is a single-width module that integrates DSU functionality and E1 channel support into Cisco uBR7200 series universal broadband routers. The multichannel E1/PRI port adapter provides eight independent E1 (120-ohm) connections via RJ-48C connectors. Each multichannel E1/PRI port adapter can provide up to 128 separate full-duplex HDLC channelized E1, fractional E1, full E1, or unframed E1 interfaces.
This module provides all the same functionality as the existing MFT module but supplies an additional interface for BRI data backup. The BRI module provides an S/T interface only, which can be used for European deployment. An inexpensive NT1 can be used to provide connectivity to ISDN services in the United States.
The 4- and 8-port T1 and E1 inverse multiplexing for ATM (IMA) network modules for the Cisco 2600 and 3600 series routers provide four or eight T1 or E1 ATM links that can be combined to appear as a single physical link. Aggregation of multiple T1/E1 links by IMA increases bandwidth inexpensively to allow WAN uplinks at high speeds, ranging to 12.288 Mbps for T1 to 15.36 Mbps for E1.
The multiport T1/E1 ATM IMA network modules support the following features:
In addition to the previously supported network processing engines (NPEs), Cisco IOS Release 12.1 supports the NPE-300 card. The NPE-300 has an RM7000 RISC microprocessor that operates at an internal clock speed of 262 MHz. The microprocessor has three levels of cache: a primary cache (32 KB, divided equally between instruction and data) and a secondary unified cache (256 KB, used for both data and instructions) that are internal to the microprocessor, and a third external cache (2 MB) that provides additional high-speed storage for both data and instructions.
The NPE-300 uses SDRAM (64 MB to 256 MB) for code, data, and packet storage. The card boots from its onboard boot ROM (512 KB), so it does not require an upgrade to the Boot ROM on the I/O controller.
|
Note The NPE-300 card is supported only on the Cisco uBR7246 VXR chassis when using a software image that supports it, such as Cisco IOS Release 12.0(7)T. Also, the NPE-300 card does not support the original MC11-FPGA modem card, so you must use the MC11C modem card or other current modem card. |
For information on replacing the network processing engine, see Network Processing Engine Replacement Instructions, available on CCO and the Cisco Documentation CD-ROM.
The OC-12c dynamic packet transport (DPT) port adapter is a dual-width OC-12c port adapter that provides a shared IP over SONET capability. The DPT port adapter is available in three models (multimode fiber; single-mode fiber, intermediate reach; and single-mode fiber, long reach).
The DPT port adapter provides the Cisco uBR7246 universal broadband router with two SC duplex ports. Each SC duplex port provides the physical connection to a device in a SONET OC-12 DPT ring. DPT rings can also be connected to SONET add-drop multiplexers (ADMs), thus allowing for the creation of small or very large DPT rings.
|
Note The DPT port adapter cannot be used on the Cisco uBR7223 universal broadband router. |
Cisco IOS Release 12.0(3)T supports the CE3 Port Adapter for the Cisco 7200 and 7500 series routers. The CE3 PA divides the E3 channel into four channelized E2 data channels and further into 16 E1 channels, all of which are compliant with the CCITT/ITU G.703 physical layer standard.
Cisco IOS Release 12.0(3)T supports the CT3 Port Adapter for the Cisco 7200 and 7500 series routers. The CT3 PA divides the DS3 channel into 28 individual T1 data channels. Each of the T1 channels can use the whole T1 bandwidth, a portion of the T1 bandwidth (Fractional T1) or use the T1 in channelized form for data transmission. Usable bandwidths for each fractional T1 are (n * 56K) or (n * 64K), where n is a number from 1 to 24. Channelized T1 allows up to 24 time slots (64 kbps or 56 kbps) per T1.
The next-generation route switch processor (RSP8) has the following features:
This feature implements voice support on the Cisco AS5300 using DSPM-542 DSP modules.
The benefits of voice features include:
Cisco IOS Release 12.1 supports a C542-based VCWare that provides codec and feature interoperability between earlier generation, TI-C542-based AS5300/voice gateways, and the latest high density versions. This release supports parallel C542-based VCWare/DSPWare and C549-based VCWare/DSPWare. However, note that the C542-based VCWare does not increase the number of calls supported on those earlier generation voice feature cards. Increasing support to 96/120 channels requires the latest generation (C549-based, AS53-VOXD based) voice feature cards.
The Cisco uBR904 cable access router is a fully functional Cisco IOS router and standards-based DOCSIS cable access router designed for use in SOHO data-over-cable applications. It enables the delivery of secure, high-speed connections over small to medium-sized LANs. Downstream speeds up to 27 Mbps are supported using the 64-QAM modulation technique, or 40 Mbps using 256-QAM. On the upstream, the Cisco uBR904 can deliver 5 Mbps using Quadrature Phase-Shift Keying (QPSK) or 10 Mbps using 16-QAM.
The Cisco uBR904 cable access router is a compact device that supports the direct connection of up to four PCs and has the familiar features and programming interface of other routers in the Cisco line of small and medium-sized business product offerings. The Cisco uBR904 can be configured as a bridge or a router, and provides packet data transport and network address translation for TCP/IP applications between home or office computers and the cable headend.
The Cisco uBR904 cable access router is a compact, easy-to-install device that can receive and send digital data over a hybrid fiber-coaxial (HFC) network; the same cable that brings television broadcast transmissions into the home of a cable television (CATV) subscriber. With a Cisco uBR904 cable access router, a personal computer can be connected to the HFC cable network for high-speed access to the Internet. The link that enables the transmission of two-way digital data from the HFC network to the Internet is provided by the Cisco uBR7246 universal broadband router installed at the cable headend.
Cisco IOS Release 12.0(7)T supports the uBR7246 VXR chassis, a high-performance platform that contains four slots for cable modem cards, two port adapter slots (supporting either two single-width or one dual-width port adapter), one slot for an I/O controller card, and one slot for the NPE-300 high-performance network processing engine (NPE). An additional slot is available for a national clock card. The Cisco uBR7246 VXR also supports dual power supplies; the second power supply is optional but provides redundancy and load-sharing capabilities.
|
Note The Cisco uBR7246 VXR router does not support the original MC11-FPGA cable modem card or the NPE-150 and NPE-200 processor cards. |
Video over ATM SVCs on the Cisco MC3810 expands the capabilities of the Cisco MC3810 multiservice access concentrator to provide cost-effective, dynamic, and flexible videoconferencing system support. By using a plug-in video dialing module (VDM) to provide an RS-366 dialing interface to an H.320 video codec, the Cisco MC3810 automatically accepts dial-out requests from the video system. The codec connects to either one of the Cisco MC3810 serial ports and also to the Cisco MC3810 RS-366 dialup port.
In addition, PVC support is enhanced to permit PVC connections with automatic connection through a serial port. Each codec must place a call to the other videoconferencing system before the expiration of the video codec timeout period. By using a video dial map, each system reconciles the dialed number with a PVC that has already been configured, allowing fast connectivity. Cisco T1/E1 Multiflex VWICs support voice and data applications in the Cisco 2600 and 3600 series routers. The VWICs offer the WIC and the VIC functionality in a variety of applications for enterprises and for service providers that supply CPE.
Multiflex VWICs support the following applications:
The following multiflex VWICs are available:
Multiflex VWIC features include the following:
|
Note You can use T1/E1 channels either for drop-and-insert or VoIP, but not both. |
The following information applies to Cisco IOS Release 12.1(3). Please see the individual notes below to determine the Cisco IOS releases that contain the appropriate fixes.
Six images in Cisco IOS Release 12.1(3) were deferred due to a severe defect. This defect has been assigned Cisco Caveat ID CSCdr82387. This caveat affects the following images:
With Caveat CSCdr82387, a Cisco ubr920 might experience no outbound voice functionalities in DOCSIS bridge mode.
Manufacturing is discontinuing shipment of affected IOS images and will ship Cisco IOS Release 12.1(4) images instead, which will be available on CCO on 9/5/00 or 12.1(3)T images, which will be available on CCO on 7/24/00. If you wish to avoid risk of having your system affected by the above-identified defect, you may replace it with the replacement image described above. If you do so, the same licenses, terms and conditions that governed your rights and obligations, and those of Cisco, with respect to the deferred image, shall govern them with respect to the replacement image. If you decide not to replace the deferred image, you proceed at your own risk.
Fourteen images in Cisco IOS Release 12.1(3) were deferred due to a severe defect. This defect has been assigned Cisco Caveat ID CSCdr75021. This caveat affects the following images:
With Caveat CSCdr75021, a Cisco 7100 series router might experience a reload due to EEPROM contents being read into a short stack local. There is currently no workaround.
Manufacturing is discontinuing shipment of affected IOS images and will ship Cisco IOS Release 12.1(2) images instead. If you wish to avoid risk of having your system affected by the above-identified defect, you may replace it with the replacement image described above. If you do so, the same licenses, terms and conditions that governed your rights and obligations, and those of Cisco, with respect to the deferred image, shall govern them with respect to the replacement image. If you decide not to replace the deferred image, you proceed at your own risk.
Five images in Cisco IOS Release 12.1(3) were deferred due to a severe defect. This defect has been assigned Cisco Caveat ID CSCdr62168. This caveat affects the following images:
With Caveat CSCdr62168, ATM PVCs are left in the inactive state upon system initialization and do not transition to active state unless a shutdown/no shutdown is issued on the associated ATM interface in configuration mode. There is no workaround other than manual reinitialization of the interfaces.
Manufacturing is discontinuing shipment of affected IOS images and will ship Cisco IOS Release 12.1(3a) images instead, which will be available on CCO on 7/31/00. If you wish to avoid risk of having your system affected by the above-identified defect, you may replace it with the replacement image described above. If you do so, the same licenses, terms and conditions that governed your rights and obligations, and those of Cisco, with respect to the deferred image, shall govern them with respect to the replacement image. If you decide not to replace the deferred image, you proceed at your own risk.
Eight images in Cisco IOS Release 12.1(3) were deferred due to a severe defect. This defect has been assigned Cisco Caveat ID CSCdr52174. This caveat affects the following images:
With Caveat CSCdr52174, a Cisco MC3810 might experience a reload at RBTreeDelete. There is currently no workaround.
Manufacturing is discontinuing shipment of affected IOS images and will ship Cisco IOS Release 12.1(2) and 12.1(3a) images instead. Cisco IOS Release 12.1(3a) images will be available after 7/31/00. If you wish to avoid risk of having your system affected by the above-identified defect, you may replace it with the replacement image described above. If you do so, the same licenses, terms and conditions that governed your rights and obligations, and those of Cisco, with respect to the deferred image, shall govern them with respect to the replacement image. If you decide not to replace the deferred image, you proceed at your own risk.
Eighty-one images in Cisco IOS Release 12.1(3) were deferred due to a severe defect. This defect has been assigned Cisco Caveat ID CSCdr68321. This caveat affects the following images:
With Caveat CSCdr68321, a Cisco 2600 or 3600 series router will experience a condition where the service state of a Primary Rate Interface (PRI) is set to OutofService.
This release has been replaced with the following software solutions, which are available on CCO as of 8/1/2000:
If you wish to avoid risk of having your system affected by the above-identified defect, you may replace it with the replacement image described above. If you do so, the same licenses, terms and conditions that governed your rights and obligations, and those of Cisco, with respect to the deferred image, shall govern them with respect to the replacement image. If you decide not to replace the deferred image, you proceed at your own risk. Manufacturing is discontinuing shipment of IOS Affected and, instead, will ship the software solution.
Six images in Cisco IOS Release 12.1(3) were deferred due to a severe defect. This defect has been assigned Cisco Caveat ID CSCdr82387. This caveat affects the following images:
With Caveat CSCdr82387, a Cisco uBR924 might experience a lack of voice functionality in DOCSIS bridge mode.
This release has been replaced with the following software solutions, which are available on CCO:
If you wish to avoid risk of having your system affected by the above-identified defect, you may replace it with the replacement image described above. If you do so, the same licenses, terms and conditions that governed your rights and obligations, and those of Cisco, with respect to the deferred image, shall govern them with respect to the replacement image. If you decide not to replace the deferred image, you proceed at your own risk. Manufacturing is discontinuing shipment of IOS Affected and, instead, will ship the software solution.
The following rsp images will be obsoleted in 12.1(3) due to Cisco Caveat ID CSCdr48014. These images are fixed, supported, orderable, and shipping in Cisco IOS Release 12.1(3a). These images will be available from CCO on 8/1/2000 and in the /release directory.
The following information applies to Cisco IOS Release 12.1(2). Please see the individual notes below to determine the Cisco IOS releases that contain the appropriate fixes.
Cisco IOS Release 12.1 contains the following defects that are related to IVR:
These defects impact the functionality of IVR, and the router might reload under some circumstances. For this reason, Cisco IOS Release 12.1(2) images should not be used if IVR features must be added on the gateway. If IVR features must be activated, please contact Cisco TAC to gain access to an interim release where these defects have been removed.
The following c5200, c5300, and c5800 images will be obsoleted in 12.1(2) due to ThunderDial feature issues. These images are fixed, supported, orderable, and shipping in Cisco IOS Release 12.1(2a).
A defect in multiple versions of Cisco IOS software will cause a Cisco router or switch to stop and reload if the IOS HTTP service is enabled and an attempt is made to browse to http://<router-ip>%%. This defect can be exploited to produce a denial of service (DoS) attack. This defect has been discussed on public mailing lists and should be considered public information.
The vulnerability, identified as Cisco bug ID CSCdr36952, effects virtually all mainstream Cisco routers and switches running Cisco IOS Release 11.1 through Release 12.1, inclusive. The vulnerability has been corrected, and Cisco is making fixed versions available to replace all affected Cisco IOS releases. Customers are urged to upgrade to releases that are not vulnerable to this defect as shown in detail below.
Workaround: Nullify the vulnerability by disabling the IOS HTTP server, by preventing access to the port in use by the HTTP server on the affected router or switch, or by applying an access-class option to the service itself. The IOS HTTP server is not enabled by default except on a small number of router models in specific circumstances.
Please see http://www.cisco.com/warp/public/707/ioshttpserver-pub.shtml for the latest complete version of this security advisory.
The following information applies to Cisco IOS Release 12.1(1). Please see the individual notes below to determine the Cisco IOS releases that contain the appropriate fixes.
Four images in Cisco IOS Release 12.1(1) were deferred due to a severe defect. This defect has been assigned Cisco Caveat ID CSCdp90823. This caveat affects the following images:
With Caveat CSCdp90823, a Cisco 1700 series router might experience a software-forced reload when you load the c1700-bno3r2sy56i-mz image, the c1700-bno3r2sv3y56i-mz image, or the c1700-bk2no3r2sv3y-mz image. There is no workaround.
There is no fix estimate on the c1700 images as of the release of Cisco IOS Release 12.1(2). Use images in Cisco IOS Release 12.0(7)T.
Eight images in Cisco IOS Release 12.1(1) were deferred due to a severe defect. This defect has been assigned Cisco Caveat ID CSCdp16140. This caveat affects the following images:
These images will be available in Cisco IOS Release 12.1(1b), which will post to CCO on May 15, 2000.
Twelve images in Cisco IOS Release 12.1(1) were deferred due to two severe defects. These defects have been assigned Cisco Caveat IDs CSCdp69004 and CSCdp71997. These caveats affect the following images:
With Caveats CSCdp69004 and CSCdp71997, a Gigabit Ethernet Interface Processor (GEIP) that is configured for Cisco Encryptions Technology (CET) decrypts packets correctly but fails to encrypt packets that match the crypto policy and should be encrypted. In this situation, the GEIP forwards the packets unencrypted instead. The workaround is to use the VIP2-40 or VIP2-50 Versatile Interface Processor with one or two PA-FE port adapters when network topology permits. Cisco IOS Release 12.1(2) includes the fix for these caveats.
A number of images in Cisco IOS Release 12.1(1) were deferred due to a severe defect. This defect has been assigned Cisco Caveat ID CSCdp99255. This caveat effects the following images:
| Cisco 7100 Series | Cisco 7200 Series | Cisco 7500/RSP Series | Cisco Catalyst 5000 RSM | Cisco uBR7200 Series |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
With Caveats CSCdp99255, a Cisco RM7000 processor that is used by an NPE-300 network processing engine and a Cisco 7000 series router might cause the router to execute instructions incorrectly or not at all. This situation might result in memory corruption or reload. There is no workaround.
Cisco IOS Release 12.1(2) includes the fix for these caveats. The non crypto rsp images are also available in Cisco IOS Release 12.1(1a). The c7100 and c7200 images are also available in Cisco IOS Release 12.1(1.1) and all subsequent builds and in Cisco IOS Release 12.1(1a).
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.
For information on caveats in Cisco IOS Release 12.1, see Caveats for Cisco IOS Release 12.1, which lists severity 1 and 2 caveats for Release 12.1 and is located on CCO and the Documentation CD-ROM.
|
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. You can reach Bug Navigator II on CCO at Software Center: Cisco IOS Software: Cisco Bug Toolkit: Cisco Bugtool Navigator II, or at http://www.cisco.com/support/bugtools. |
Posted: Thu Aug 31 10:37:54 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.