Cisco IOS Release 12.2(16)BX3

These release notes for the Cisco 10000 series router support Cisco IOS Release 12.2(16)BX3, which provides Service Selection Gateway features for the Cisco 10000 series router. These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and changes to the microcode and related documents.

We recommend that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/customer/tech_tips/index/fn.htm l. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html.

Inheritance Information

To review the release notes for Cisco IOS Release 12.0(20)ST, go to the following URL:

To review the release notes for Cisco IOS Release 12.2, go to the following URL:

System Requirements

Cisco IOS Release 12.2(16)BX3 requires that you have the performance routing engine (PRE), part number ESR-PRE2 installed in the Cisco 10000 chassis. To verify which PRE is installed in the router, use the show version command.

Upgrading to a New Software Release

For general information about upgrading to a new software release, refer to Software Installation and Upgrade Procedures located at the following URL:

New and Changed Information

For information about new features supported on the Cisco 10000 router in other releases, see the appropriate release notes document at the following URL:

New Features—Cisco IOS Release 12.2(16)BX3

The following new features are supported on the Cisco 10000 router in Cisco IOS Release 12.2(16)BX3:

Variable Bit Rate-Non-Real Time Oversubscription

The Variable Bit Rate Non-Real Time (VBR-nrt) Oversubscription feature enables service providers to improve network utilization of otherwise underutilized shared networks by leveraging statistical multiplexing on ATM networks. Instead of supporting only unconditional reservation of network bandwidth to VCs, the router offers VC oversubscription to statistically guarantee bandwidth to VCs.

For more information, see the Variable Bit Rate-Non-Real Time Oversubscription, Release 12.2(16)BX3 feature module at the following URL:

F4 Operations, Administration, and Maintenance Ping Without Virtual Path

The F4 Operations, Administration, and Maintenance (OAM) Ping without Virtual Path (VP) Creation feature enables you to determine problems at the virtual path (VP) level using the ping command. Using this feature, you can create and remove virtual circuit identifiers (VCIs) that correspond to the VP segment and the VP end. These special VCs can be configured only on the Cisco 10000 router and are not available on any other Cisco platform. After creating the VCIs you can use the ping atm command to isolate connection problems.

Configuring F4 OAM Ping Without VC Creation

To configure an F4 VC segment or end, enter the following commands in interface configuration mode:

Verifying F4 VC Segment and End Creation

To verify the creation of an F4 VC segment or end, enter the following commands in privileged EXEC mode:

Configuration Example for F4 VC Creation

The following example shows how to create an F4 segment VC with a VPI/VCI pair of 10 3:

The following example shows how to create an F4 end VC with a VPI/VCI pair of 10 4:

The following example shows how to ping the newly created F4 segment and end VCs:

Non-SSG User-to-SSG User Policing

The Non-SSG User-to-SSG User Policing feature controls user-to-user traffic by policing aggregated traffic destined to or sent from a particular host. Using this feature, you can configure a policing rate for the upstream, downstream, or both upstream and downstream traffic for SSG hosts.

Command	Purpose
Router(config-if)# pvc VPI/3 f4-oam	Creates an F4 segment VC. VPI is the virtual path identifier value. Valid values are from 0 to 255.
Router(config-if)# pvc VPI/4 f4-oam	Creates an F4 end VC. VPI is the virtual path identifier value. Valid values are from 0 to 255.

Command	Purpose
Router# show atm pvc VPI/3	Displays information about the F4 segment VC. VPI is the virtual path identifier value. Valid values are from 0 to 255.
Router# show atm pvc VPI/4	Displays information about the F4 VC end. VPI is the virtual path identifier value. Valid values are from 0 to 255.

Note This feature is available only on the Cisco 10000 series router. It is not available on other Cisco SSG platforms.

When you configure the Non-SSG User-to-SSG User Policing feature, the Cisco 10000 router determines the policing rate for the SSG host based on the sum of the rate that you specify and the aggregate rate of the services to which a user is subscribed. If you specify a rate of 0, the Cisco 10000 router uses only the sum of the user-subscribed services to calculate the policing rate. The non-SSG user-to-SSG user policer is a global policer; therefore, applying this policer places a policing rate on all subscribers.

If you configure a per-subscriber host policing rate and a non-SSG user-to-SSG user policing rate, the per-subscriber host rate overrides the non-SSG user-to-SSG user policing rate and is applied for a host.

Configuring Non-SSG User-to-SSG User Policing

To configure a non-SSG user-to-SSG user policer, enter the following command in global configuration mode:

Configuration Example for Both Upstream and Downstream Policing

User A is subscribed to the BasicA service at a rate of 256 Kbps downstream and 128 Kbps upstream.

The following example configures both upstream and downstream policing at a rate of 64 Kbps:

The Cisco 10000 router determines the policing rate to apply to the downstream and upstream traffic for SSG hosts using the following calculations:

If the SSG host attempts to access peer-to-peer applications, the Cisco 10000 router limits the bandwidth of the downstream traffic to 320 Kbps and the upstream traffic to 192 Kbps.

If the host attempts to simultaneously access the Internet and peer-to-peer applications, the router still limits the total bandwidth for peer-to-peer applications to 320 Kbps downstream and 192 Kbps upstream, and the router limits the Internet bandwidth to 256 Kbps downstream and 128 Kbps upstream.

Configuration Example for Both Upstream and Downstream Policing at a Specified Rate of 0

UserA is subscribed to the BasicA service at a rate of 256 Kbps downstream and 128 Kbps upstream.

UserB is subscribed to the BasicA service at a rate of 256 Kbps downstream and 128 Kbps upstream, and to the Video service at a rate of 1 Mbps downstream and 128 Kbps upstream.

UserC is subscribed to the BasicA service at a rate of 256 Kbps downstream and 128 Kbps upstream, and to the Video service at a rate of 1 Mbps downstream and 128 Kbps upstream. UserC has a host-based policing rate configured using SESM.

The following example configures both upstream and downstream policing at a specified rate of 0:

The Cisco 10000 router determines the policing rate to apply to the downstream and upstream traffic for SSG hosts using the following calculations:

If the SSG host accesses peer-to-peer applications, the router limits the bandwidth to 256 Kbps downstream and 128 Kbps upstream. If the host simultaneously accesses the Internet and peer-to-peer applications, the router still limits the total bandwidth to 256 Kbps downstream and 128 Kbps upstream.

The Cisco 10000 router determines the policing rate to apply to the downstream and upstream traffic for SSG hosts using the following calculations:

If the SSG host accesses peer-to-peer applications, the router limits the bandwidth to 1.256 Mbps downstream and 256 Kbps upstream. If the host simultaneously accesses the Internet, video, and peer-to-peer applications, the router still limits the total bandwidth to 1.256 Mbps downstream and 256 Kbps upstream. The router also limits the Internet bandwidth to 256 Kbps downstream and 128 Kbps upstream, and Video bandwidth to 1 Mbps downstream and 128 Kbps upstream.

Because UserC has a host-based policing rate configured using SESM, the router uses the SESM policing rate as the SSG host rate.

SSG Link Redundancy

The SSG Interface Redundancy feature enables providers to configure the Cisco Service Selection Gateway (SSG) with redundant uplink interfaces to services and to the default network. This feature also supports the configuration of redundant downlink interfaces for nonoverlapping users configured with the port-bundle host key functionality. Interface redundancy benefits service providers as well as subscribers by helping to prevent subscriber downtime due to interface failure.

Volume-Based SSG Prepaid

The SSG Prepaid feature allows a user to connect to a service if the user has prepaid for the service. SSG checks a subscriber's available credit to determine whether to connect the subscriber to the service and how long the connection can last. The billing server administers the subscriber's credit as a series of quotas, which are allotments of available credit.

The volume-based SSG Prepaid feature allows for real-time billing with maximum flexibility, regardless of the type of service and billing scheme. Users are billed on a volume basis. The quotas represent the allowable data volume, expressed in bytes. Volume quotas are for combined upstream and downstream traffic.

To obtain the first quota for a connection, SSG submits an authorization request to the AAA server. The AAA server contacts the prepaid billing server, which forwards the quota values to SSG. SSG then monitors the connection to track the quota usage. When the quota runs out, SSG performs reauthorization. During reauthorization, the billing server can provide SSG with an additional quota if there is available credit. If no further quota is provided, SSG logs off the user.

For the Cisco 10000 router, it can take up to one minute to detect that the volumn-based prepaid quota has expired. The SSG Prepaid feature accounts the excess quota used in the current period against the quota received from the next prepaid reauthorization.

Command	Purpose
Router(config)# pxf ssg host {upstream \| downstream} [base_rate]	Configures the policing rate that you specify for traffic to and from a particular SSG host. (Optional) The base_rate parameter is the minimum bandwidth required. The Cisco 10000 uses this rate to derive the policing rate for traffic for the SSG host. Valid values are numbers from 0 to 2,500,000,000. The default value is 0. Note You can configure a policer for the upstream, downstream, or both the upstream and downstream traffic for SSG hosts.

A Quota VSA in the RADIUS access-accept packet defines the quota parameters for a connection. Table 1 defines the Quota VSA.

Configuring Volume-Based SSG Prepaid

To configure SSG to provide the prepaid billing server with the session ID and volume-based information, enter the following commands in global configuration mode:

Configuration Example for Volume-Based SSG Prepaid

The following example displays information about the SSG connection for a prepaid service that uses a volume-based quota:

Limitations and Restrictions

This section describes limitations and restrictions for the following areas. Be sure to review these limitations and restrictions before you use the Cisco 10000 router.

ssg bind direction Command Not Supported

Table 1 Quota VSA
Attribute ID	Vendor ID	Subattribute ID and Type	Attribute Name	Subattribute Data
26	9	253 Control-Info	Quota	Q—Control-Info code for prepaid quota. T or V—Quota subcode for time or volume. numeric string—Quota value.

	Command	Purpose
Step 1	Router(config)# radius-server attribute 55 include-in-acct-req	Sends the RADIUS attribute 55 (Event-Timestamp) in the accounting packets.
Step 1	Router(config)# radius-server attribute 44 include-in-access-req	Sends the RADIUS attribute 44 (Acct-Session-ID) in the access-request packets before performing user authentication (including requests for preauthentication).
Step 2	Router(config)# radius-server vsa send authentication	Configures the network access server to recognize and use vendor-specific authentication attributes.

Instead of the ssg bind direction command, which returns an error, use the new ssg direction command. See the feature module SSG Direction Command for Interfaces and Ranges for more information.

L2TP Tunnel Authorization

Cisco 10000 router supports Layer 2 Tunneling Protocol (L2TP) tunnel authorization. However, RADIUS does not provide attributes for such parameter values as L2TP tunnel timeouts, L2TP tunnel hello intervals, and L2TP tunnel receive window size. When the Cisco 10000 router does not receive a RADIUS attribute for a parameter, the router uses the default value.

Broadband Aggregation Groups

Cisco IOS Release 12.2(15)BX or later does not support the configuration of broadband aggregation (BBA) groups using RADIUS. You must configure BBA groups manually.

ATM PXF Queuing

If you intend to disable Asynchronous Transfer Mode (ATM) parallel express forwarding (PXF) queuing, to ensure reliable operation you must enter the no atm pxf queuing command before you configure any virtual circuits (VCs) on an interface. If you have already configured VCs on an interface and you need to change the mode of ATM PXF queuing, remove the VCs from the configuration and then change the ATM PXF queuing mode.

Dynamic Bandwidth Selection

The Cisco 10000 series router does not support dynamic bandwidth selection (DBS) on virtual path (VP) tunnels.

QoS Service Policy on a Virtual Access Interface

If you apply an output Quality of Service (QoS) service policy on a virtual-access interface, and that virtual access interface is L2TP tunneled (when the router is configured as an L2TP Network Server [LNS], for example) and the service policy indicates that the type of service (ToS) or Differentiated Services Code Point (DSCP) bits should be set (with the set ip command, for example), the router sends the packets as-is, without changing the IP Precedence bits or DSCP bits. The outer header gets the correct value, but the inner header is not changed.

CISCO-VPDN-MGMT MIB

SNMP limits the size of Virtual Private Dialup Network (VPDN) template names to 128 characters. This affects the functionality of the CISCO-VPDN-MGMT MIB. Due to this restriction, if any template name (cvpdnTemplateName) in the cvpdnTemplateTable exceeds 128 characters, you cannot use an SNMP getmany request to retrieve any table entries. Instead, you must use individual getone requests to retrieve each template name that does not exceed 128 characters. For more information, refer to the Cisco 10000 Series Internet Router Broadband MIB Specifications Guide.

AAA Method Lists

Cisco IOS Release 12.2(14)BX supports a maximum of 99 authentication, authorization, and accounting (AAA) method lists. If you configure more than 99 AAA method lists using the aaa authentication ppp or aaa authorization network command, traceback messages appear on the console.

Unshaped UBR PVCs

Cisco IOS Release 12.2(15)BX or later releases supports a maximum of 8000 unshaped unspecified bit rate permanent virtual circuits (UBR VCs) on the OC-12 ATM line card. An unshaped UBR PVC is a PVC that has no rate configured on it. You can configure up to 16,000 shaped UBR PVCs per port on the OC-12 line card if you configure the PVCs with a shaped rate of less than 299 Mbps.

Shaped UBR PVCs

The Cisco 10000 series router does not support shaped UBR in atm pxf queuing mode.

Controlling the Rate of Logging Messages

It is important that you limit the rate that system messages are logged by the Cisco 10000 series router. This helps to avoid a situation in which the router becomes unstable and the CPU is overloaded. To control the output of messages from the system, use the logging rate-limit command.

This rate-limits all messages to the console to 10 per second, except for messages with critical priority (level 3) or greater.

For more information about the logging rate-limit command, refer to the Cisco IOS Configuration Fundamentals Command Reference.

Testing Performance of High-Speed Interfaces

Cisco IOS software running on the Cisco 10000 series router has multiple queues for all classes of traffic over high-speed interfaces. The software selects a queue based on the source and destination address of the packet. This ensures that a traffic flow always uses the same queue and the packets are transmitted in proper order.

When the Cisco 10000 series router is installed in a real network, the high-speed interfaces work efficiently to spread traffic flow equally over the queues. However, using single traffic streams in a laboratory environment might result in less-than-expected performance.

Therefore, to ensure accurate test results, you should test the throughput of the gigabit Ethernet, Packet Over SONET (POS), or ATM uplink with multiple source or destination addresses.

Tip

To determine if traffic is being properly distributed, use the show pxf cpu queue command.

Important Notes

This section provides important information about the following items for Cisco IOS Release 12.2(16)BX3:

Interoperability with Test Equipment

Interoperability issues exist when using the Spirent Adtech AX/4000 with ATM connections. These conditions will not occur in a live network deployment, and only affect lab testing.

The Adtech appears to interpret packet padding, instead of ignoring it (reference ITU-T I.363.5 08/96).

Keepalive packets for PPPoA sessions are often dropped, causing sessions to drop. This behavior occurs especially when the Cisco 10000 has PPPoA and PPPoEoA on the same ATM line card, with three or more virtual path identifiers (VPIs) configured. The content of the padding in this configuration causes the Adtech to ignore the PPPoA keepalives.

More broad incompatabilities were resolved in Adtech version 4.51. This current interoperability is a more specific configuration.

Provisioning for Scaling

The following configuration parameters enhance scalability on the Cisco 10000 router:

To configure the Cisco 10000 series router for high scalability, be sure to configure the configuration parameters as described in the sections that follow.

PPP Terminated Aggregation Session Scaling

PPP terminated aggregation (PTA) sessions sometimes do not scale as expected because automatic PPP messages are saved to the buffer, which can cause PTA call rates to degrade. To avoid this problem, add the following command to the router's configuration:

CISCO-ATM-PVCTRAP-EXTN-MIB

The Cisco 10000 router does not support the CISCO-ATM-PVCTRAP-EXTN-MIB for large numbers of permanent virtual circuits (for example, 32,000 PVCs). To exclude the Cisco-ATM-PVCTRAP-EXTN-MIB from the Simple Network Management Protocol (SNMP) view and enhance scalability, configure the following commands in global configuration mode:

Command	Purpose
Router(config)# logging buffered warnings	Limits the logging of messages to the local buffer to warning conditions (level 4).


	Command	Purpose
Step 1	Router(config)# snmp-server view view-name oid-tree included	Creates or updates a view entry. The view-name argument is a label for the view record that you are updating or creating. The name is used to reference the record. The oid-tree argument is the object identifier of the ASN.1 subtree to be included from the view. Specify a valid oid-tree from where you want to poll the information. The included argument configures the OID (and subtree OIDs) specified in the oid-tree argument to be included in the SNMP view.
Step 2	Router(config)# snmp-server view view-name ciscoAtmPvcTrapExtnMIB excluded	Configures the CISCO-ATM-PVCTAP-EXTN-MIB OID (and subtree OIDs) to be explicitly excluded from the SNMP view. You must specify the oid-tree as shown in the command line. The view-name argument must match the view-name you specified in step 1.
Step 3	Router(config)# snmp-server community string [view view-name] [ro \| rw] [access-list-number]	Sets up the community access string to permit access to SNMP. The string argument is a community string that acts like a password and permits access to the SNMP protocol. The view-name argument must match the view-name you specified in step 1.

Example 1 shows how to create or modify the SNMP view named myview to include the information polled from the Internet oid-tree and to exclude the CISCO-ATM-PVCTRAP-EXTN-MIB oid-tree. The community access string named private is set up and access to SNMP is read-only (ro) access.

For more information about the snmp-server view and snmp-server community commands, see the Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3.

PPPoA Sessions with IP QoS Static Routes

To scale to 32,000 PPP over ATM (PPPoA) sessions with IP quality of service (QoS) enabled, you must limit the number of IP QoS static routes to 4,000 unidirectional QoS static routes.

AAA Authentication on the NME Port

If you use AAA authentication on the Network Management Ethernet (NME) port, set both the in and out interface hold queues to 4096. For example:

Call Admission Control

We recommend that you set the Call Admission Control (CAC) to a maximum of 95. For example:

Enhancing Scalability of Per-User Configurations

To enhance scalability of per-user configurations without changing the router configuration, use the ip:vrf-id and ip:ip-unnumbered RADIUS attributes. These per-user vendor specific attributes (VSAs) are used to map sessions to VPN routing and forwarding (VRF) and IP unnumbered interfaces. The VSAs apply to virtual access subinterfaces and are processed during PPP authorization.

In releases prior to Cisco IOS Release 12.2(16)BX1, the lcp:interface-config RADIUS attribute is used to map sessions to VRFs. This per-user VSA applies to any type of interface configuration, including virtual access interfaces. Valid values of this VSA are essentially any valid Cisco IOS interface command; however, not all Cisco IOS commands are supported on virtual access subinterfaces. To accommodate the requirements of the lcp:interface-config VSA, the per-user authorization process forces the Cisco 10000 router to create full virtual access interfaces, which consume more memory and are less scalable.

In Cisco IOS Release 12.2(16)BX1 and later releases, the ip:vrf-id is used to map sessions to VRFs. Any profile that uses the ip:vrf-id VSA must also use the ip:ip-unnumbered VSA to install IP configurations on the virtual access interface that is to be created. PPP that is used on a virtual access interface to be created requires the ip:ip-unnumbered VSA. An Internet Protocol Control Protocol (IPCP) session is not established if IP is not configured on the interface. You must configure either the ip address command or the ip unnumbered command on the interface so that these configurations are present on the virtual access interface that is to be created. However, specifying the ip address and ip unnumbered commands on a virtual template interface is not required because any pre-existing IP configurations are removed when the ip:ip-vrf VSA is installed on the virtual access interface. Therefore, any profile that uses the ip:vrf-id VSA must also use the ip:ip-unnumbered VSA to install IP configurations on the virtual access interface that is to be created.

These per-user VSAs can be applied to virtual access subinterfaces; therefore, the per-user authorization process does not require the creation of full virtual access interfaces, which improves scalability.

Setting VRF and IP Unnumbered Interface Configurations in User Profiles

Although the Cisco 10000 router continues to support the lcp:interface-config VSA, the ip:vrf-id and ip:ip-unnumbered VSAs provide another way to set the VRF and IP unnumbered interface configurations in user profiles. The ip:vrf-id and ip:ip-unnumbered VSAs have the following syntax:

You must only specify one ip:vrf-id and one ip:ip-unnumbered value in a user profile. However:

•

If the profile configuration includes multiple values, the Cisco 10000 router applies the value of the last VSA received, and creates a virtual access subinterface.

•

If the profile includes the lcp:interface-config VSA, the router always applies the value of the lcp:interface-config VSA, and creates a full virtual access interface.

Each time you specify a VRF in a user profile, but you do not configure the VRF on the Cisco 10000 router, in Cisco IOS Release 12.2(15)BX, the router accepted the profile. However, in Cisco IOS Release 12.2(16)BX1 and later releases, the router rejects the profile.

Setting VRF and IP Unnumbered Interface Configuration in a Virtual Interface Template

You can specify one VSA value in the user profile on RADIUS and another value locally in the virtual template interface. The Cisco 10000 router clones the template and then applies the values configured in the profiles it receives from RADIUS, resulting in the removal of any IP configurations when the router applies the profile values.

Redefining User Profiles to Use the ip:vrf-id and ip:ip-unnumbered VSAs

The requirement of a full virtual access interface when using the lcp:interface-config VSA in user profiles can result in scalability issues, such as increased memory consumption. This is especially true when the Cisco 10000 router attempts to apply a large number of per-user profiles that include the lcp:interface-config VSA. Therefore, when updating your user profiles, we recommend that you redefine the lcp:interface-config VSA to the scalable ip:vrf-id and ip:ip-unnumbered VSAs.

Example 3 shows how to redefine the Loopback 0 interface using the ip:ip-unnumbered VSA.

Inserting a New Line Card

Unlike other Cisco routers, if you insert a new or different line card into a Cisco 10000 chassis slot that previously had a line card installed, the line card initially reports that it is administratively up

Multilink PPP

Caveats for Cisco IOS Release 12.2(16)BX3

Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats sections.

For information about caveats in Cisco IOS Release 12.2(16)BX3, see the following sections:

Open Caveats—Cisco IOS Release 12.2(16)BX3

For information about open caveats in other Cisco IOS releases, see the appropriate release notes document at the following URL:

Table 2 Open Caveats in Cisco IOS Release 12.2(16)BX3
Caveat	Description
CSCdy79740	If 32,000 PPPoA sessions, 99 VRFs, RADIUS authentication, and the per vrf aaa case command are configured on the Cisco 10000 series router, and you insert or remove a line card, the PPPoA sessions disconnect within 45 seconds of the online insertion and removal (OIR) event. When this happens, the following traceback message might appear on the console: `[%IPRT-4-ROUTECOUNTNEGATIVE]` Workaround: There is no workaround for this problem.
CSCea46149	If you connect a test analyzer to the 6-port channelized T3 line card and configure a T1 under a T3 controller, and the line card and the test analyzer are both set to Extended Superframe (ESF) framing, the T1 does not start. Workaround: There is no workaround for this problem.
CSCea52741	If the Cisco 10000 series router reloads unexpectedly, any On-Demand Address Pool (ODAP) subnets allocated from the Cisco Network Registrar (CNR) remain marked as Leased (at the CNR). Workaround: There is currently no workaround to this problem. However, if this should occur, the subnets are released when the lease time expires, or they may be released manually through the CNR Command Line Interface (CLI).
CSCea67815	When you disable 32,000 sessions over 10,000 L2TP tunnels on a Cisco 10000 series router configured as an LNS with RADIUS AAA accounting enabled, the router might terminate the remaining sessions due to the overwhelming number of RADIUS records generated by this event. If this occurs, the following message might appear on the console: `%ALIGN-3-TRACE` Workaround: There is no workaround for this problem.
CSCea72016	The channelized OC-12 line card undergoes a watchdog reset when unconfiguring six channelized OC-12 line cards set up with 768 T1s each. This occurs only with a very specific large channelized card setup. This does not occur with five or less channelized OC-12 line cards. Workaround: Unconfigure fewer OC-12 channelized interfaces at one time.
CSCea81015	If you configure the management Ethernet port (fastethernet 0/0/0) on the PRE (part number ESR-PRE2) front panel using the ip address dhcp command, the port does not acquire an IP address. Workaround: Configure the fastethernet 0/0/0 interface with a static IP address.
CSCeb01499	The following traceback message displays in the log after you enter the hardware subslot shutdown, no card, and no hardware subslot shutdown or card 24che1t1 mode t1 commands: `May 2 23:31:53: %IPCGRP-3-SYSCALL: System call for command 409 (slot4/0) : ipc_send_rpc_blocked failed (Cause: retry queue flush)` `-Traceback= 6046B1EC 6046B4C0 6046BD5C` `May 2 23:31:54: %IPCOIR-4-REPEATMSG: IPC handle already exists for 4/0` Workaround: There is no workaround for this problem.
CSCeb26165	While the Cisco 10000 series router terminates PPP sessions and uses RADIUS accounting, the router generates both Accounting-Stop and Accounting-Off messages when you enter the reload command. Workaround: There is no workaround for this problem.
CSCeb51344	RADIUS configurations that use lcp: in the VSAs are not usable when they are downloaded and are to be VRF-aware on the Cisco 10000 series router. When downloading routes from RADIUS that are configured using Internet Engineering Task Force (IETF) attributes, sessions are established as expected and the routing table lists the routes as per-user routes. Workaround: There is no workaround for this problem.
CSCeb53474	With TACACS configured on the Cisco 10000 series router, the secondary PRE (part number ESR-PRE2) console attempts TACACS authentication using the fa0/0/0 interface. Before notifying the user that the secondary console is unavailable, the secondary PRE incorrectly attempts to contact the TACACS server for user authentication. The secondary PRE should not attempt to contact the TACACS server or it should try to contact the TACACS server using the primary PRE. Workaround: There is no workaround for this problem.
CSCec24597	When configuring a constant bit rate permanent virtual circuit (CBR PVC) using a test script, a traceback message appears and the router does not create the CBR PVC. Workaround: There is no workaround for this problem.
CSCed91686	When a nested policy map is attached to a subinterface, deleting the subinterface generates continuous traceback messages, and the router becomes unstable. Workaround: There is no workaround for this problem.
CSCee03702	A Cisco 10000 router with dual performance routing engines (PREs, part number ESR-PRE2) and dual route processors (RPs) fails at GetHostKey_10HostObjectP7hostkey. Workaround: There is no workaround for this problem.
CSCee40092	If you issue a shut/no shut command sequence while configured MPP bundles are carrying traffic, this triggers the race condition when MLP bundles are coming back up. MLP bundles fail to come up successfully because of a lack of resources for the bundle. Workaround: There is no workaround for this problem.
CSCee42660	When you implement auto-vc configuration using the pvc-in-range command and change the value of the class-vc to a different UBR+ speed, a traceback message appears. The PVC can enter a blocked state and the router can stop responding. Workaround: There is no workaround for this problem.
CSCee49305	If you issue the no shut command on a configured MLP bundle that is already in an UP/UP state, the MLP bundle and member interface link bounce each time. When an interface is in an UP/UP state, a no shut command should not bounce the interface. Workaround: There is no workaround for this problem.
CSCee51262	If you configure the clock source as line on a channelized STM1 line card on a Cisco 10000 series router, line flaps occur. This problem occurs only when there is an SDH network in the middle. Back-to-back configurations do not show this problem on a PRE, part number ESR-PRE2. Workaround: Configure the clock source line command one time.
CSCin46447	When you disable SSG traffic policing on the router by entering the no ssg qos police user and the no ssg qos police session commands, the router continues to police the traffic for the existing host and connection. Workaround: There is no workaround for this problem.

Resolved Caveats—Cisco IOS Release 12.2(16)BX3

This section describes caveats that were fixed in Cisco IOS Release 12.2(16)BX3.

For information about caveats fixed in other Cisco IOS releases, see the appropriate release notes document at the following URL:

(Duplicate of CSCea45943, CSCea46076) The throughput of Frame Relay traffic was sometimes up to 5 percent lower than the maximum possible throughput. This has been fixed.

The Cisco 10000 series router displayed a bus fault error when automatic protection switching (APS) was configured on the OC-12 ATM line card. This has been fixed.

(Duplicate of CSCeb15960) If APS was configured using the aps force atm slot/subslot/port from protect command on the 4-port OC-3 line card or the single-port OC-12 ATM line card, and a signal failure was received on the port of either line card, the output of the show interface atm slot/subslot/port command sometimes indicated the interface was up instead of down. This has been fixed.

(Duplicate of CSCea45002) When you configured automatic protection switching (APS) switchover on the 4-port OC-3 ATM line card, entering the show controller atm slot/subslot/port command for the ATM port displayed a signal degrade status for both the protection port and the working port. This has been fixed.

(Duplicate of CSCeb73578) In a Cisco 10000 chassis with redundant PREs, after a switchover from the primary PRE to the secondary PRE, the traffic rate of the single-port OC-12 ATM line card was low. This has been fixed.

(Duplicate of CSCea35065, CSCea55991) When you entered the show processes memory sorted command in privileged EXEC mode, the software sometimes forced the router to reload. This has been fixed.

A memory allocation error occurred when you attempted to scale a large number of users (for example, 4,000 PPPoA Service Selection Gateway [SSG] sessions). All of the connections were established and the show ssg command displayed all of the sessions as logged in and active. However, when sessions were dropped, a memory allocation error appeared. This has been fixed.

Packet counters and debug messages on the Cisco 10000 router could not be used to accurately count or view Interim Local Management Interface (ILMI) keepalive messages. This was because basic ILMI configurations generated bursts of ILMI transactions between the Cisco 10000 router and adjacent ATM switches.

For example, if you connected an OC-3 ATM line card that was installed in a Cisco 10000 router to a Cisco LS1010 ATM switch, and you enabled debugging using the debug atm ilmi command, the packet counters for the ILMI PVC incremented to match the bursts of packets. This is expected behavior.

(Duplicate of CSCec71974) If you entered the ip verify unicast rpf command for a virtual template, the calls-per-second rate was reduced. This has been fixed.

The Cisco 10000 router became unresponsive when multiple users simultaneously entered modular QoS CLI (MQC) commands (such as the show policy map command) on the same router using separate VTY sessions. This has been fixed.

The Cisco 10000 router frequently displayed the following interprocess communications (IPC) queue full message. This has been fixed.

Configurations with a large number of subinterfaces (for example, 32,000) sometimes experienced slow PPP over Ethernet over ATM (PPPoEoA) session clearing. This has been fixed.

(Duplicate of CSCeb38165) When a range of VCs were configured for autoprovisioning, if you shut down one of the VCs in the range by using the pvc-in-range command, the following message scrolled on the console until you started the VC again. This has been fixed.

The Cisco 10000 router created PPP sessions without allocating a virtual circuit connection identifier (VCCI). This has been fixed.

The ATM interface MAC address was used as the source MAC address. If RBE was also configured on the same interface with PPPoE, problems occurred at the customer premise equipment (CPE) because RBE also used the ATM interface MAC address. A customer-requested featurette now provides the ability to choose the desired MAC address as the source MAC address for PPPoEoA.

The parallel express forwarding (PXF) engine sometimes failed due to invalid commands being issued to the PXF. This occurred when an L2TP Network Server (LNS) received a large IP packet from the IP cloud, the destination IP address was a PPP session to a DSL customer, and the NetFlow Analyzer was enabled on the ingress interface. The size of the packet received from the trunk and entering the L2TP tunnel had to exceed the tunnel minimum transmission unit (MTU) so that fragmentation occurred. This has been fixed.

A memory leak occurred when a large number of SSG users were logged in and SSG accounting was enabled. Using the show memory summary command, the number of free bytes for processor and I/O memory diminished rapidly. With 32,000 sessions, the memory diminished to zero after approximately 24 hours. This has been fixed.

Some PPP sessions did not become active and remained in the link control protocol (LCP) negotiation state. This has been fixed.

Packets became stuck in the PAK_priority queue when an interface was congested. This occurred when the default queue (without a service policy applied) received a constant stream of large packets that overburdened the default queue. The PAK_priority queue stopped dequeueing packets, which resulted in the interface going down. This has been fixed.

Executing the show facility-alarm status command while an ATM interface is shut down sometimes led to inaccurate output from the command. This has been fixed.

The output packet counters on an interface were sometimes incorrect. Depending on the Cisco IOS release software, the counters showed either a large value or an unexpected value. This occurred after entering the clear counters command to clear the interface counters and then entering the microcode reload pxf command to reload the PXF microcode. The output packet counters became corrupted. This has been fixed.

An IP receive access control list (ACL) did not filter traffic when it was configured for the first time. After the ACL was removed and then configured again, the ACL started to work and filtered exactly the same traffic. This has been fixed.

For SSG hosts that were connected by an ATM multipoint interface (for example, PPPoE over ATM or RFC 1483), the network access server (NAS) port information was not included in Attribute 44 (Account Session ID) in the RADIUS accounting records. This occurred even though the radius-server attribute nas-port format d command had been configured on the router. This has been fixed.

A Cisco MGX 8800 series Route Processor Module XF (RPM-XF) sometimes failed and generated the following error message. This occurred when you entered the clear interface sw1 command multiple times on an RPM-XF. The RPM-XF was functioning as a provider edge (PE) router in a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN). This has been fixed.

When using the police command in a QoS policy, QoS police statistics displayed incorrectly. The values of the packet and byte counters were large and inaccurate. This has been fixed.

A small memory leak occurred on the Cisco 10000 router when testing the router as a PPP terminated aggregator (PTA). This occurred when PPPoE sessions connected to and disconnected from the router. The number of sessions remained constant on the router, but memory slowly began to decrease as sessions logged on and off. This has been fixed.

A flood of SSG API messages sometimes consumed all of the input/output (I/O) memory on the Cisco 10000 router. This occurred on the SSG when the remote AAA server for a RADIUS proxy service stopped responding for an extended period of time and many users tried to log in to the service. This has been fixed.

The network access server (NAS) stopped accepting PPP sessions when thousands of calls were brought up and down continuously within a few days. This occurred when the virtual template interface configuration included the ppp ipcp address unique command. The PPP debug information included the following information. This has been fixed.

Extended RADIUS reload processing sometimes occurred when you changed the router configuration to use a different, inaccessible RADIUS server and then you reloaded the system. If the system had redundant route processors (RPs) and the RADIUS reload process lasted more than a couple of minutes, then the reload process sometimes allowed the redundant RP to become active before the reload process completed, which led to an erroneous switchover operation instead of the intended reload operation. The switchover operation sometimes included interprocess communications (IPC) problems, causing the system to operate incorrectly. This has been fixed.

During periods of high calling rates, the router failed to apply a per-user access control list (ACL) to a virtual access subinterface and the following traceback message appeared. This has been fixed.

When you removed a multilink PPP (MLP) bundle by removing the member interface's channel information instead of by using the proper configuration removal procedure, a leak occurred in bundle resources. As a result, the resource sometimes indicated that it was no longer available and the following messages displayed in the log file. This has been fixed.

A Cisco 10000 router with two redundant performance routing engines (PREs), part number ESR-PRE2, reported a bus error (instead of a multibit ECC error) before transferring control to the secondary PRE. The multibit memory hardware error occurred in the external column memory (XCM). This has been fixed.

When issuing the ping command or sending L2TP traffic across a multiprotocol label switching (MPLS) interface with labeling enabled, MPLS encapsulated IP packets were not fragmented and the following error message appeared in the console log file. This has been fixed.

A configuration with a policing service policy that was attached to an ATM PVC that was never operationally active caused a row or rows to be missing from the cbQosPoliceCfgTable and cbQosPoliceStatsTable for police object types (cbQosObjectsType). This has been fixed.

Traceback messages continuously appeared when attempting to install multilink queues. This has been fixed.

When you removed an interface at a specific speed from a multilink interface, any attempt to add a different speed interface to the multilink interface resulted in the following error message. This has been fixed.

When low-latency queuing (LLQ) was configured on a multilink interface with Link Fragmentation Interface (LFI) fragmentation and the priority queue was configured as a shaped priority queue (for example, priority percent percent was configured), the priority queue (PQ) behaved as an absolute PQ. To protect the other queues, you had to configure a policer in the PQ. This has been fixed.

When you entered the show aaa user all command, the session duration time reported in accounting packets was incorrect. This occurred only when the aaa accounting session-duration ntp-adjusted command was configured. This has been fixed.

The Cisco 10000 router sometimes failed when receiving PPPoE call rates greater than 250 calls per second (cps). This has been fixed.

The LAC failed when an ATM VC went down and a PPPoA session went down before the VC changed the state to up. A queuing service policy was applied to the VC and then the client session was cleared. This occurred only if the service policy was applied to the ATM VC after the session was up. This has been fixed.

Under heavy traffic conditions, if a multilink PPP (MLP) bundle flapped, sometimes the MPLS bundle was not reallocated properly and the bundle could not achieve an up state. This occurred if the bundle flapped due to entering the shutdown or no shutdown command, flapping on the peer interface, or entering the hw-module reset command. The log file did not indicate the error, but you could view the condition using the show pxf cpu queue multilink<x> command. This has been fixed.

When removing a QoS child policy, a traceback message appeared. This occurred only when the policy was assigned to a subinterface. The removal of the policy resulted in a change in the traffic shaping parameter in the parent policy. This has been fixed.

The Link Fragmentation Interface (LFI) feature was not fragmenting packets as expected. This has been fixed.

When you configured a service policy on a multilink interface and on a serial interface, the router failed to create priority queueing (PQ) in the parallel express forwarding (PXF) engine. This has been fixed.

A ping failure occurred on multilink PPP (MLP) bundles after a high availability (HA) switchover. Not all of the MLP bundles returned to the up state. This was a serialization problem with tearing down the bundle on the PRE from which the bundle was switched. This has been fixed.

The Cisco 10000 router sometimes failed after the following error and traceback messages appeared on the console. This has been fixed.

The pvc-in-range configuration disappeared after online insertion and replacement (OIR) of the line card. This occurred only with create on-demand VCs. This has been fixed.

A Cisco 10000 router with redundant performance routing engines (PREs, part number ESR-PRE2) sometimes was not able to completely write a core dump file when required. This occurred because the secondary PRE reset the primary PRE before the file writing operation had completed. This has been fixed.

When you entered the microcode reload pxf command on the same router or a peer router, ping failures were observed. This sometimes occurred after entering the command multiple times. This has been fixed.

Entering the shutdown command and then the no shutdown command on an interface caused the following error message and traceback message to appear in the log file. This occurred when one bundle was configured with one member and no traffic was configured. This has been fixed.

When the permanent virtual path (PVP) was changed while a large number of VCs (more than 100 VC) were in the tunnel and traffic was running, ATM segmentation and reassembly (SAR) generated an error message and, under extreme conditions, the line card failed. The Cisco IOS software did not manage the error message as expected and sometimes also failed. This has been fixed.

Sometimes access control lists (ACLs) were not applied to virtual access interfaces. This has been fixed.

The multilink state machine was not operating properly because it was being indexed by the multilink queue index instead of the preferred static bundle index. The multilink queue index changed each time the bundle first in first out (FIFO) buffer was replaced. This has been fixed.

When a multilink PPP (MLP) bundle shut down due to the loss of its peer or because it was manually shut down, draining of the bundle FIFO sometimes was delayed for up to 30 minutes due to new packets traveling into the default queue of the member's serial interface. This condition caused an unacceptable delay in bringing the bundle back up after disabling it. When you entered the show pxf cpu queue multilink<n> command during this condition, the Packets in Bundle FIFO field displayed a non-zero value. This has been fixed.

When running the Cisco IOS experimental image c10k2-p11-mz.v122_16_bx_throttle.20040416, a Cisco 10000 router sometimes encountered a bus error failure. This has been fixed.

When a nested service policy was applied to a Gigabit Ethernet subinterface with a terminated PPPoE over VLAN session, any traffic that matched the service policy was not forwarded to the PPPoE over VLAN session. This has been fixed.

When using SNMP with the CISCO-CLASS-BASED-QOS-MIB for a class-default class configured with random-detect, the cbQosREDClassStatsTable did not have an entry for class-default. This has been fixed.

The priority queue (PQ) counters were not working with link fragmentation and interleaving (LFI). When you entered the show policy-map command, the PQ counters were not working and remained zero (0). The drop counters for SNMP were zero (0) for all queues. This has been fixed.

The multilink PPP (MLP) minimum fragment size was incorrect. The minimum fragment size set was 66 instead of 56 (64 bytes minus 8 bytes header). This has been fixed.

Multicast packets received on a PPPoE interface and sent out a GRE tunnel were not encapsulated correctly. The remote end of the GRE tunnel dropped the packet as an unknown type packet. This has been fixed.

When the SSG host object connected to two or more services, a system processor memory leak occurred in the SSGSerQue process. This has been fixed.

When an unauthenticated user tried to access a service, the TCP packets for the host were redirected to the SESM, but the returned packets were not reverse translated. This occurred on the Cisco 10000 router with PXF switching when the SSG TCP Redirect feature was enabled for unauthenticated users and the SSG Port Map feature was disabled. This has been fixed.

SSG service binding to the next-hop gateways failed when the configuration of the router was copied to the router from the TFTP server. This caused SSG services to sometimes become inaccessible. This has been fixed.

Other Caveats

This section includes caveats listed in previous release notes that are regarded as resolved because they are either unreproducible, they were reported in error, or they do not affect the behavior of the Cisco 10000 series router. If a caveat listed in this section causes problems, contact Cisco customer service. See the "Obtaining Technical Assistance" section.

The LNS sends keepalives at an incorrect interval. We have been unable to reproduce this problem.

Previously, it was reported that the output of the show controller e1 command showed the status of the E1 controller on the 24-port channelized E1/T1 line card as down when it was actually up. We have been unable to reproduce this problem.

Channelized interfaces with access control lists (ACLs) configured might show an incorrect ACL status even after the ACL is removed from the interface by entering the no ip access acl-name command. This occurs if the interface is rechannelized and the removed ACL is reconfigured on the interface. We have been unable to reproduce this problem.

In rare circumstances, if you enter the hw-module slot slot shutdown command followed by the no card command, the router reloads unexpectedly. This problem rarely occurs and you are unlikely to experience it. We have been unable to reproduce this problem.

A client was unable to ping the SSG access side downlink interface. This occurred when an SSG interface was configured as a downlink interface and routing with bridged encapsulation was configured. We have been unable to reproduce this problem.

Multiple memory leaks occurred while testing the Cisco IOS Release 12.2(16)BX image. We have been unable to reproduce this problem.

When 61,500 PPPoEoA sessions were active and SNMP was running in the background, executing the show ios command caused the following traceback message to appear:

If two users were logged into the router, and one user began a save of the system configuration to removable flash media while another user initiated a system reload, the configuration file on the removable media became corrupted and no file operations were possible on the file (for example, erase, copy, and overwrite did not work). We have been unable to reproduce this problem.

If you wanted to store a configuration locally on removable flash media disk0 and you were using the boot config statement and the boot config environment variable to point to the same configuration file on disk0, the file was not automatically synchronized to disk0 on the redundant PRE (sec-disk0). In the event of a failure, the backup PRE would not have had access to the current configuration file. We have been unable to reproduce this problem.

Table Of Contents

Release Notes for the Cisco 10000 Series Router for Cisco IOS Release 12.2(16)BX3

Contents

Inheritance Information

System Requirements

Upgrading to a New Software Release

New and Changed Information

New Features—Cisco IOS Release 12.2(16)BX3

Variable Bit Rate-Non-Real Time Oversubscription

F4 Operations, Administration, and Maintenance Ping Without Virtual Path

Configuring F4 OAM Ping Without VC Creation

Verifying F4 VC Segment and End Creation

Configuration Example for F4 VC Creation

Non-SSG User-to-SSG User Policing

Configuring Non-SSG User-to-SSG User Policing

Configuration Example for Both Upstream and Downstream Policing

Configuration Example for Both Upstream and Downstream Policing at a Specified Rate of 0

SSG Link Redundancy

Volume-Based SSG Prepaid

Configuring Volume-Based SSG Prepaid

Configuration Example for Volume-Based SSG Prepaid

Limitations and Restrictions

ssg bind direction Command Not Supported

L2TP Tunnel Authorization

Broadband Aggregation Groups

ATM PXF Queuing

Dynamic Bandwidth Selection

QoS Service Policy on a Virtual Access Interface

CISCO-VPDN-MGMT MIB

AAA Method Lists

Unshaped UBR PVCs

Shaped UBR PVCs

Controlling the Rate of Logging Messages

Testing Performance of High-Speed Interfaces

Important Notes

Interoperability with Test Equipment

Provisioning for Scaling

PPP Terminated Aggregation Session Scaling

CISCO-ATM-PVCTRAP-EXTN-MIB

PPPoA Sessions with IP QoS Static Routes

AAA Authentication on the NME Port

Call Admission Control

Enhancing Scalability of Per-User Configurations

Setting VRF and IP Unnumbered Interface Configurations in User Profiles

Setting VRF and IP Unnumbered Interface Configuration in a Virtual Interface Template

Redefining User Profiles to Use the ip:vrf-id and ip:ip-unnumbered VSAs

Inserting a New Line Card

Multilink PPP

Caveats for Cisco IOS Release 12.2(16)BX3

Open Caveats—Cisco IOS Release 12.2(16)BX3

Resolved Caveats—Cisco IOS Release 12.2(16)BX3

Other Caveats

Related Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information

All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R)

Copyright � 2004, Cisco Systems, Inc.All rights reserved.

Copyright � 2004, Cisco Systems, Inc.
All rights reserved.