The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
These release notes for the Cisco ASR 1000 Series Aggregation Services Routers support Cisco IOS XE Release 2.6.2 and earlier Release 2 releases. These release notes are updated as needed to describe new features, caveats, potential software deferrals, and related documents.
For a list of the software caveats that apply to Cisco IOS XE Release 2, see the "Caveats for Cisco IOS XE Release 2" section on page 167.
Cisco recommends 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/en/US/customer/support/tsd_products_field_notice_summary.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/en/US/support/tsd_products_field_notice_summary.html.
These release notes describe the following topics:
•MIBs
•Obtaining Documentation and Submitting a Service Request
The Cisco ASR 1000 Series Aggregation Services Routers are the next generation Cisco midrange router products. The Cisco ASR 1000 Series Aggregation Services Routers use an innovative and powerful hardware processor technology known as the Cisco QuantumFlow Processor. The Cisco ASR 1000 Series Routers consist of three different routers: the Cisco ASR 1002 Router, the Cisco ASR 1004 Router, and the Cisco ASR 1006 Router.
•The Cisco ASR 1002 Router is a 3-SPA, 2-rack-unit (RU) chassis with one Embedded Services Processor (ESP) slot that comes with the Route Processor (RP), Cisco ASR 1000 Series Shared Port Adapter Interface Processor (SIP), and four Gigabit Ethernet ports built in.
•The Cisco ASR 1004 Router is an 8-SPA, 4-RU chassis with one ESP slot, one RP slot, and two SIP slots.
•The Cisco ASR 1006 Router is a 12-SPA, 6-rack-unit (RU), hardware-redundant chassis with two Embedded Services Processor (ESP) slots, two Route Processor (RP) slots, and three SIP slots.
For the single-route-processor Cisco ASR 1000 platforms, the Cisco ASR 1002 and Cisco ASR 1004, the Route Processor has a dual Cisco IOS Software option that allows these routers to use Cisco IOS software redundancy, Cisco high-availability features, Nonstop Forwarding (NSF), and In Service Software Upgrades (ISSUs). This option requires the Cisco ASR 1000 Series Route Processor to have 4 GB of DRAM memory.
The Cisco ASR 1006 Router supports fully redundant Route Processors that allow for full Route-Processor hardware redundancy, NSF, ISSU, and future Route-Processor service upgrades.
The Cisco ASR 1000 Series Routers run Cisco IOS XE Software and introduce a distributed software architecture that moves many operating system responsibilities out of the IOS process. In this architecture, Cisco IOS, which previously was responsible for almost all of the internal software processes, now runs as one of many Cisco IOS XE processes while allowing other Cisco IOS XE processes to share responsibility for running the router.
One of the key features of the Cisco IOS XE Software is support for dual Cisco IOS software consolidated packages in a single Route Processor for software redundancy in the 2-RU and 4-RU chassis systems. These dual Cisco IOS consolidated packages can consist of the same software consolidated packages for backup or different software consolidated packages for resilient upgrade.
Note Software redundancy is not supported on the 6-RU chassis.
The Cisco ASR 1000 Series Routers target both enterprise and service provider applications and provide application-specific features for broadband subscriber aggregation and network application services with improved processing performance and high availability.
For information on new features and Cisco IOS commands supported by Cisco IOS XE Release 2, see the "New and Changed Information" section and the "Related Documentation" section.
This section describes the system requirements for Cisco IOS XE Release 2 and includes the following sections:
•Software Packaging on the Cisco ASR 1000 Series Routers
•Cisco IOS XE Software Package Compatibility for ISSU
•Cisco IOS XE Release Compatibility Tables
•Determining the Software Version
•Upgrading to a New Software Release
•Cisco IOS XE to Cisco IOS Version Number Mapping
The Cisco ASR 1000 Series Routers run Cisco IOS XE Software and use a new software packaging model consisting of:
•Consolidated packages
•Individual software sub-packages within a consolidated package
•Optional software sub-packages outside of consolidated packages
Each Cisco IOS XE consolidated package contains a collection of individual software sub-packages. Each individual software sub-package is an individual software file that controls a different element or elements of the Cisco ASR 1000 Series Router. Some individual sub-packages may be installed per element (for example, per SPA).
Note The sub-package functionality is intended for both upgrade and field support, and not all combinations of sub-packages are supported.
Each individual software sub-package can be upgraded individually, or all individual software sub-packages for a specific Cisco IOS XE consolidated package can be upgraded as part of a complete Cisco IOS XE consolidated package upgrade.
Importantly, IOS (the RPIOS individual software sub-package) is considered one of the individual software sub-packages that makes up the complete Cisco IOS XE consolidated package.
The following are the individual software sub-packages within a consolidated package:
•Route Processor
–RPBase: Provides the Route-Processor operating system.
–RPControl: Provides the control-plane processes that interface between Cisco IOS Software and the rest of the platform.
–RPIOS: Provides the Cisco IOS Software kernel, which is where Cisco IOS Software features are stored and run; each consolidated image variant has a different RPIOS sub-package: RPIOS-ipbase, RPIOS-ipbasek9, RPIOS-advipservices, RPIOS-advipservicesk9, RPIOS-adventservices, and RPIOS-adventservicesk9.
Note The RPIOS-advipservices and RPIOS-adventservices sub-packages are only available beginning with Cisco IOS XE Release 2.2.1 and later releases. These two sub-packages are not available with Cisco IOS XE Release 2.1.2 and earlier releases.
–RPAccess: Provides components to manage enhanced router access functionality.
•ESP
–ESPBase: Provides the ESP operating system and control processes, and the Cisco QuantumFlow Processor client, driver, and ucode.
•SIP
–SIPBase: Provides the SIP operating system and control processes
–SIPSPA: Provides the SPA drivers and associated field-programmable device (FPD) image (SPA FPGA image)
A Cisco IOS XE consolidated package allows users to upgrade all individual software sub-packages on the router with a single Cisco IOS XE image download. The Cisco IOS XE consolidated packages available vary based on the Route Processor (RP1 or RP2) installed in the system and the Cisco IOS XE Release.
The following are the RP1 consolidated packages:
•Cisco ASR 1000 Series RP1 IP BASE W/O CRYPTO
•Cisco ASR 1000 Series RP1 IP BASE
•Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES
•Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES W/O CRYPTO
•Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES
•Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES W/O CRYPTO
Note The Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES W/O CRYPTO consolidated package is only available with Cisco IOS XE Release 2.2.1 through Cisco IOS XE Release 2.3.x. This consolidated package is not available with any other Cisco IOS XE Releases.
The Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES W/O CRYPTO consolidated package is only available beginning with Cisco IOS XE Release 2.2.1 and later releases. This consolidated package is not available with Cisco IOS XE Release 2.1.2 and earlier releases.
The following are the RP2 consolidated packages:
•Cisco ASR 1000 Series RP2 IP BASE W/O CRYPTO
•Cisco ASR 1000 Series RP2 IP BASE
•Cisco ASR 1000 Series RP2 ADVANCED IP SERVICES
•Cisco ASR 1000 Series RP2 ADVANCED IP SERVICES W/O CRYPTO
•Cisco ASR 1000 Series RP2 ADVANCED ENTERPRISE SERVICES
•Cisco ASR 1000 Series RP2 ADVANCED ENTERPRISE SERVICES W/O CRYPTO
Note The RP2 consolidated packages are only available beginning with Cisco IOS XE Release 2.3.0 and later releases. The RP2 consolidated packages are not available with Cisco IOS XE Release 2.2.3 and earlier releases.
The Cisco ASR 1000 Series RP2 ADVANCED IP SERVICES W/O CRYPTO consolidated package is only available with Cisco IOS XE Release 2.3.0 through Cisco IOS XE Release 2.3.x. This consolidated package is not available with any other Cisco IOS XE Releases.
The individual software sub-packages within the consolidated packages cannot be downloaded from Cisco.com; only the Cisco IOS XE consolidated packages and optional sub-packages can be downloaded from Cisco.com. Users who want to run the router using individual software sub-packages must first download the consolidated package from Cisco.com and extract the individual software sub-packages from the consolidated package.
In addition to the individual software sub-packages within a consolidated package, optional software sub-packages that are not part of a consolidated package are available. Optional software sub-packages are downloaded separately from Cisco.com and their installation is similar to the installation of an individual software sub-package using a provisioning file. The optional sub-package must be located in the same directory with the provisioning file and the other individual sub-package files. The optional software sub-packages available vary based on the Route Processor (RP) installed in the system: RP1 or RP2:
•For the RP1, the optional software sub-package available is the Cisco ASR 1000 Series RP1 WebEx Node (asr1000rp1-sipspawmak9.version.pkg)
•For the RP2, the optional software sub-package available is the Cisco ASR 1000 Series RP2 WebEx Node (asr1000rp2-sipspawmak9.version.pkg)
Note The Cisco ASR 1000 Series RP1 WebEx Node and Cisco ASR 1000 Series RP2 WebEx Node optional software sub-packages are only available beginning with Cisco IOS XE Release 2.4.0 and later releases and are only supported in conjunction with a related RP-based Cisco ASR 1000 Series RPx IP BASE, Cisco ASR 1000 Series RPx ADVANCED IP SERVICES, or Cisco ASR 1000 Series RPx ADVANCED ENTERPRISE SERVICES consolidated package. These optional software sub-packages are not supported with earlier Cisco IOS XE releases or with any of the non-CRYPTO consolidated packages.
Note ISSU operation on the Cisco ASR 1002 and Cisco ASR 1004 systems requires the system to be operating in sub-package mode.
Note USB (or any other removable media) cannot be used to boot the system into sub-package mode.
For further information on the advantages and disadvantages of running individual sub-packages or a complete Cisco IOS XE consolidated package, and the process of extracting the individual sub-packages, see the following document:
Cisco ASR 1000 Series Aggregation Services Router Software Configuration Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/chassis/asrswcfg.html
When upgrading the Cisco IOS XE operating system software using the In Service Software Upgrade (ISSU) process, it is important to determine the compatibility of the upgraded software to your current software and hardware. The ISSU process allows software to be updated or otherwise modified while packet forwarding continues with minimal interruption.
Cisco IOS XE release compatibility using the ISSU process utilizes the SSO functionality to preserve state while software versions on the router differ, as during an upgrade. Most SSO-capable features in each Cisco IOS XE release are ISSU capable. ISSU is only supported if SSO is enabled in the configuration and the system is in a steady state (SSO ready state has been achieved). ISSU compatibility depends on the set of specific feature clients that are in use and whether they support ISSU. All ISSU upgrades include at least one IOS switchover operation. It is important to understand which features are in use and whether these features are ISSU compatible.
The Cisco ASR1006 Series Router is a hardware-redundant chassis. The hardware-redundant chassis has two ESP linecards and two RPs which exchange state using hardware links. The Cisco ASR1002 and ASR1004 Series Routers are not hardware redundant, but are software-redundancy capable. The non-redundant chassis has a single RP and a single ESP, but allows the operation of up to two IOS processes on the single RP to exchange states locally.
•Non-hardware-redundant chassis models (such as the Cisco ASR 1002 Router and Cisco ASR 1004 Router)—Supports ISSU only if the router is running in subpackage mode.
•Hardware-redundant chassis models (such as the Cisco ASR 1006 Router)—Supports ISSU when the router is running in sub-package mode or in consolidated package mode.
For a complete discussion about the ISSU upgrade process on the Cisco ASR 1000 Series Routers, including prerequisites and restrictions, see the "In Service Software Upgrade (ISSU)" chapter of the Cisco ASR 1000 Series Aggregation Services Software Configuration Guide.
Rebuilds of a specific Cisco IOS XE release are intended to be fully ISSU and SSO capable for supported features between any two image pairings, however compatibility is not guaranteed for all releases. It is expected that rebuilds between release versions are compatible within a reasonable time frame.
The support policy for version rebuilds is as follows:
•The immediate prior rebuild for the version is expected to be SSO and ISSU compatible with a new released rebuild of that version.
•A newly released rebuild is expected to be SSO and ISSU compatible with the current rebuild for the previous two versions.
As an example, a rebuild Y of version X is version XY. For rebuilds on the two previous versions of X, X-1 and X-2, it is expected that XY will be compatible with those versions.
Certain special Cisco IOS XE software releases may be made from time to time. These releases are not specified in this document and any supported SSO or ISSU interoperability must be determined on a case by case basis.
The ISSU compatibility tables in this section provide information about release pairs that are compatible and those that are not compatible for Cisco ASR1000 Series Routers. You can use this information to determine the impact of a Route Processor (RP) or Embedded Service Processor (ESP) switchover when the router is running a mixed combination of software as occurs during the whole-node ISSU procedures.
Non-SSO-capable features and non-ISSU-capable features are not included in the ISSU compatibility tables since these features lose state on any Cisco IOS XE switchover—RP switchover in the case of hardware-redundant chassis and software switchover on software-redundant chassis.
In the ISSU compatibility tables, the following information is provided:
•SSO
A Cisco IOS XE release stating :SSO" for all supported SSO-capable features is fully compatible for upgrades using ISSU, even if some of the SSO-capable features are not ISSU capable. Two different versions of the software are denoted as supporting SSO if they are able to reach an SSO state when run simultaneously, regardless of the impact on specific features.
•SSO Tested
A Cisco IOS XE release stating "SSO Tested" indicates that the two releases are fully tested and supported as interoperable and will retain state across a switchover. ISSU upgrades between the releases are supported.
•SSO via <release>
A Cisco IOS XE release stating "SSO via <release>" indicates that the two releases are not interoperable and must not be run simultaneously (must not be run at the same time on the two RPs of a hardware redundant chassis and must not be co-installed as subpackages on any chassis). However, an SSO path exists using the intermediate release that is specified.
•Limited
A Cisco IOS XE release stating "Limited" indicates that the two releases have interoperability limitations. On the Cisco ASR1002 and Cisco ASR1004 routers. ISSU upgrade and downgrade are not supported. Instead you can perform a sub-package software upgrade. This process requires a RP reload.
The tables in the following sections list the compatibility of Cisco IOS XE software releases:
•ISSU Compatibility for Cisco IOS XE 2.1-Based Releases
•ISSU Compatibility for Cisco IOS XE 2.2-Based Releases
•ISSU Compatibility for Cisco IOS XE 2.3-Based Releases
•ISSU Compatibility for Cisco IOS XE 2.4-Based Releases
•ISSU Compatibility for Cisco IOS XE 2.5-Based Releases
•ISSU Compatibility for Cisco IOS XE 2.6-Based Releases
Note The ISSU compatibility tables use the following conventions:
•The software version numbers are given first as the Cisco IOS XE release version number followed by the bundled Cisco IOS release number.
•For descriptions of the table fields, see the "Discussion of Table Fields" section.
Note When not labeled, the compatibility information shown in Table 1-1 applies to all platforms based on the package mode supported for ISSU on that platform. In some cases, compatibility information varies by platform and is indicated in the table.
Note Cisco ASR1002 and Cisco ASR1004 routers do not support ISSU upgrade and downgrade due to lack of hardware redundancy and the requirement to reboot the RP. However, the sub-package software upgrade and downgrade is supported only if the router is running in sub-package mode in order to minimize interruption to service.
|
Cisco IOS XE 2.1.0 |
Cisco IOS XE 2.1.1 |
Cisco IOS XE 2.1.2 |
---|---|---|---|
Cisco IOS XE 2.1.0 |
— |
SSO Tested1 |
SSO Tested1 |
Cisco IOS XE 2.1.1 |
SSO Tested1 |
— |
SSO Tested |
Cisco IOS XE 2.1.2 |
SSO Tested1 |
SSO Tested |
— |
Cisco IOS XE 2.2.1 |
Cisco ASR 1006 Router SSO via 2.1.21 Cisco ASR 1002 and Cisco ASR 1004 Routers Limited. |
Cisco ASR 1006 Router SSO via 2.1.2 Cisco ASR 1002 and Cisco ASR 1004 Routers Limited |
Cisco ASR 1006 Router SSO Tested Cisco ASR 1002 and Cisco ASR 1004 Routers Limited |
Cisco IOS XE 2.2.2 |
SSO via 2.1.21 |
SSO via 2.1.2 |
Limited2 and 3 |
Cisco IOS XE 2.2.3 |
SSO via 2.1.2 |
SSO via 2.1.2 |
|
Cisco IOS XE 2.3.0 |
SSO via 2.1.2 |
SSO via 2.1.2 |
Limited2 and 3 |
Cisco IOS XE 2.3.1 |
SSO via 2.1.2 |
SSO via 2.1.2 |
Limited2 and 3 |
Cisco IOS XE 2.3.2 |
SSO via 2.1.2 |
SSO via 2.1.2 |
Limited2 and 3 |
1 For Cisco ASR 1006 Router, some ESP-maintained session state may be lost when ESPs of different versions interoperate. This affects primarily stateful firewall and network address translation functions implemented by the ESPs. 2 For Cisco ASR 1006 Router, downgrade may fail depending on the features that are configured. 3 For Cisco ASR 1002 Router and Cisco ASR 1004 Routers, the Cisco IOS XE software on the standby RP may spontaneously restart creating a core dump file when issu loadversion (issu command set) or request platform software package install (request platform command set) is used to simultaneously install the RP packages other than the base package (as specified by the {rpcontrol,rpaccess,rpios} portion of the filename specification). The Cisco IOS XE software on the standby RP will recover after this event. |
Note When not labeled, the compatibility information shown in Table 1-2 applies to all platforms based on the package mode supported for ISSU on that platform. In some cases, compatibility information varies by platform and is indicated in the table.
Note Cisco ASR1002 and Cisco ASR1004 routers do not support ISSU upgrade and downgrade due to lack of hardware redundancy and the requirement to reboot the RP. However, the sub-package software upgrade and downgrade is supported only if the router is running in sub-package mode in order to minimize interruption to service.
Note Cisco IOS XE 2.4.2t does not support ISSU upgrade and downgrade.
|
Cisco IOS XE 2.2.1 |
Cisco IOS XE 2.2.2 |
Cisco IOS XE 2.2.3 |
---|---|---|---|
Cisco IOS XE 2.1.0 |
SSO via 2.1.21 |
SSO via 2.1.2 |
SSO via 2.1.2 |
Cisco IOS XE 2.1.1 |
SSO via 2.1.2 |
SSO via 2.1.2 |
SSO via 2.1.2 |
Cisco IOS XE 2.1.2 |
SSO Tested |
SSO Tested |
|
Cisco IOS XE 2.2.1 |
— |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.2.2 |
SSO Tested |
— |
SSO Tested |
Cisco IOS XE 2.2.3 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited4 |
SSO Tested |
— |
Cisco IOS XE 2.3.0 |
Limited4 and 5 |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.3.1 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
SSO Tested |
Cisco IOS XE 2.3.2 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
SSO Tested |
Cisco IOS XE 2.4.0 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
SSO Tested |
Cisco IOS XE 2.4.1 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
SSO6 |
Cisco IOS XE 2.4.2 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
SSO Tested7 |
Cisco IOS XE 2.4.3 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
SSO |
Cisco IOS XE 2.4.4 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers Limited SSO via 2.2.3 |
SSO |
1 For the Cisco ASR 1006 Router, some ESP-maintained session state may be lost when ESPs of different versions interoperate. This affects primarily stateful firewall and network address translation functions implemented by the ESPs. 2 For the Cisco ASR 1006 Router, use of new features in the uprev release may be limited after ISSU. To correct this issue, perform an additional redundancy force-switchover after completing all steps of the ISSU procedure and after the device has reached SSO. Alternatively, a chassis reload also addresses the issue. 3 For the Cisco ASR 1002 Router and Cisco ASR 1004 Routers, when ISSU is used to upgrade router software, new features available in the new version are configurable as soon as the RP software portion of the update has been completed for both active and standby IOS. New features will be fully reflected in the operation of the router once the linecard images are also updated. Under some circumstances, the new features may not be available until after the final step of the Cisco ASR1002 and Cisco ASR1004 ISSU procedure is performed (chassis reload). 4 For the Cisco ASR 1002 Router and Cisco ASR 1004 Routers, the Cisco IOS XE software on the standby RP may spontaneously restart creating a core dump file when issu loadversion (issu command set) or request platform software package install (request platform command set) is used to simultaneously install the RP packages other than the base package (as specified by the {rpcontrol,rpaccess,rpios} portion of the filename specification). The Cisco IOS XE software on the standby RP will recover after this event. 5 For the Cisco ASR 1006 Router, downgrade may fail depending on the features that are configured. 6 After ISSU procedure, you might need to run an additional switchover to ensure R0 is active. 7 The forwarding processor (FP) remains in "init" state during ISSU sub-package procedure when broadband QoS is configured. The workaround is to recreate some broadband sessions, tear down all sessions, or unconfigure QoS queueing feature on the broadband sessions and then reload the FP. For more information, refer to CSCsz09462 in the Bug Toolkit. |
Note When not labeled, the compatibility information shown in Table 1-3 applies to all platforms based on the package mode supported for ISSU on that platform. In some cases, compatibility information varies by platform and is indicated in the table.
Note Cisco ASR1002 and Cisco ASR1004 routers do not support ISSU upgrade and downgrade due to lack of hardware redundancy and the requirement to reboot the RP. However, the sub-package software upgrade and downgrade is supported only if the router is running in sub-package mode in order to minimize interruption to service.
Note Cisco IOS XE 2.4.2t does not support ISSU upgrade and downgrade.
|
Cisco IOS XE 2.3.0 |
Cisco IOS XE 2.3.1 12.2(33)XNC1 |
Cisco IOS XE 2.3.2 12.2(33)XNC2 |
---|---|---|---|
Cisco IOS XE 2.1.0 |
SSO via 2.1.2 |
SSO via 2.1.2 |
SSO via 2.1.2 |
Cisco IOS XE 2.1.1 |
SSO via 2.1.2 |
SSO via 2.1.2 |
SSO via 2.1.2 |
Cisco IOS XE 2.1.2 |
Cisco ASR 1006 Router SSO Tested1 Cisco ASR 1002 and Cisco ASR 1004 Routers SSO via 2.2.2 |
Cisco ASR 1006 Router SSO Tested1 Cisco ASR 1002 and Cisco ASR 1004 Routers SSO via 2.2.2 |
Cisco ASR 1006 Router SSO Tested1 Cisco ASR 1002 and Cisco ASR 1004 Routers SSO via 2.2.2 |
Cisco IOS XE 2.2.1 |
Cisco ASR 1006 Router SSO Tested1 Cisco ASR 1002 and Cisco ASR 1004 Routers SSO via 2.2.2 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers SSO via 2.2.3 |
SSO |
Cisco IOS XE 2.2.2 |
SSO Tested1 |
Cisco ASR 1006 Router SSO Tested Cisco ASR 1002 and Cisco ASR 1004 Routers SSO via 2.2.3 |
SSO Tested |
Cisco IOS XE 2.2.3 |
SSO Tested1 |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.3.0 |
— |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.3.1 |
SSO Tested |
— |
SSO Tested |
Cisco IOS XE 2.3.2 |
SSO Tested |
SSO Tested |
— |
Cisco IOS XE 2.4.0 |
SSO |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.4.1 |
SSO |
SSO |
SSO Tested |
Cisco IOS XE 2.4.2 |
SSO |
SSO |
SSO Tested |
Cisco IOS XE 2.4.3 |
SSO |
SSO |
SSO Tested |
Cisco IOS XE 2.4.4 |
SSO |
SSO |
SSO Tested2 |
Cisco IOS XE 2.5.03 |
SSO |
SSO |
SSO Tested |
Cisco IOS XE 2.5.1 |
SSO4 |
SSO4 |
SSO Tested4 |
Cisco IOS XE 2.5.2 |
SSO4 |
SSO4 |
SSO Tested4 |
1 For the Cisco ASR 1006 Router, use of new features in the uprev release may be limited after ISSU. To correct this issue, perform an additional redundancy force-switchover after completing all steps of the ISSU procedure and after the device has reached SSO. Alternatively, a chassis reload also addresses the issue. 2 A loopback interface Outbound Cache Entry (OCE) may be lost after an RP failover. 3 For ATM SPAs on the Cisco ASR1000 Series Routers, ISSU from releases prior to Cisco IOS XE Release 2.5.0 to Cisco IOS XE Release 2.5.0, or from Cisco IOS XE Release 2.5.0 to a release prior to Cisco IOS XE Release 2.5.0, is not supported. If you want to perform ISSU in this environment, you must first remove the configuration from the ATM SPAs on the router, and then shut down the SPAs using the shutdown command prior to running the ISSU process. 4 PPP sessions requiring AAA authentication and authorization will not be synchronized to standby after ISSU upgrade procedure. This applies to scenarios where the Cisco ASR 1000 Series Router is acting as a PPP Termination and Aggregation (PTA) or L2TP network server (LNS) terminating PPP sessions. |
Note When not labeled, the compatibility information shown in Table 1-4 applies to all platforms based on the package mode supported for ISSU on that platform. In some cases, compatibility information varies by platform and is indicated in the table.
Note Cisco ASR1002 and Cisco ASR1004 routers do not support ISSU upgrade and downgrade due to lack of hardware redundancy and the requirement to reboot the RP. However, the sub-package software upgrade and downgrade is supported only if the router is running in sub-package mode in order to minimize interruption to service.
Note Cisco IOS XE 2.4.2t does not support ISSU upgrade and downgrade.
|
Cisco IOS XE 2.4.0 12.2(33)XND |
Cisco IOS XE 2.4.1 12.2(33)XND1 |
Cisco IOS XE 2.4.2 12.2(33)XND2 |
Cisco IOS XE 2.4.3 12.2(33)XND3 |
Cisco IOS XE 2.4.4 12.2(33)XND4 |
---|---|---|---|---|---|
Cisco IOS XE 2.2.1 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers SSO via 2.2.3 |
SSO |
SSO |
SSO |
SSO |
Cisco IOS XE 2.2.2 |
Cisco ASR 1006 Router SSO Cisco ASR 1002 and Cisco ASR 1004 Routers SSO via 2.2.3 |
SSO |
SSO |
SSO |
SSO |
Cisco IOS XE 2.2.3 |
SSO Tested |
SSO Tested |
SSO Tested |
SSO |
SSO |
Cisco IOS XE 2.3.0 |
SSO |
SSO |
SSO |
SSO |
SSO |
Cisco IOS XE 2.3.1 |
SSO Tested |
SSO |
SSO |
SSO |
SSO |
Cisco IOS XE 2.3.2 |
SSO Tested |
SSO Tested |
SSO Tested |
SSO Tested |
SSO Tested1 |
Cisco IOS XE 2.4.0 |
— |
SSO Tested |
SSO Tested2 |
SSO |
SSO |
Cisco IOS XE 2.4.1 |
SSO Tested |
— |
SSO Tested |
SSO |
SSO |
Cisco IOS XE 2.4.2 |
SSO Tested2 |
SSO Tested |
— |
SSO Tested |
SSO Tested1 |
Cisco IOS XE 2.4.3 |
SSO |
SSO |
SSO Tested |
— |
SSO Tested1 |
Cisco IOS XE 2.4.4 |
SSO |
SSO Tested1 |
SSO Tested1 |
SSO Tested1 |
— |
Cisco IOS XE 2.5.03 |
SSO |
SSO |
SSO Tested |
SSO |
SSO |
Cisco IOS XE 2.5.1 |
SSO4 |
SSO4 |
SSO Tested4 |
SSO Tested4 |
SSO4 |
Cisco IOS XE 2.5.2 |
SSO4 |
SSO4 |
SSO Tested4 |
SSO Tested4 |
SSO Tested1,4 |
Cisco IOS XE 2.6.0 |
SSO4 |
SSO4 |
SSO Tested4 |
SSO Tested4 |
SSO4 |
Cisco IOS XE 2.6.1 |
SSO4 |
SSO4 |
SSO4 |
SSO Tested4 |
SSO Tested4 |
Cisco IOS XE 2.6.2 |
SSO4 |
SSO4 |
SSO4 |
SSO4 |
SSO Tested1,4 |
1 A loopback interface Outbound Cache Entry (OCE) may be lost after an RP failover. 2 The Cisco IOS XE software might fail during the ISSU process while the network clock is configured. For more information about the conditions and workaround, refer to CSCsz12394 in the Bug Toolkit. 3 For ATM SPAs on the Cisco ASR1000 Series Routers, ISSU from releases prior to Cisco IOS XE Release 2.5.0 to Cisco IOS XE Release 2.5.0, or from Cisco IOS XE Release 2.5.0 to a release prior to Cisco IOS XE Release 2.5.0, is not supported. If you want to perform ISSU in this environment, you must first remove the configuration from the ATM SPAs on the router, and then shut down the SPAs using the shutdown command prior to running the ISSU process. 4 PPP sessions requiring AAA authentication and authorization will not be synchronized to standby after ISSU upgrade procedure. This applies to scenarios where the Cisco ASR 1000 Series Router is acting as a PPP Termination and Aggregation (PTA) or L2TP network server (LNS) terminating PPP sessions. |
Note For ATM SPAs on the Cisco ASR1000 Series Routers, ISSU from releases prior to Cisco IOS XE Release 2.5.0 to Cisco IOS XE Release 2.5.0, or from Cisco IOS XE Release 2.5.0 to a release prior to Cisco IOS XE Release 2.5.0, is not supported. If you want to perform ISSU in this environment, you must first remove the configuration from the ATM SPAs on the router, and then shut down the SPAs using the shutdown command prior to running the ISSU process.
Note Cisco ASR1002 and Cisco ASR1004 routers do not support ISSU upgrade and downgrade due to lack of hardware redundancy and the requirement to reboot the RP. However, the sub-package software upgrade and downgrade is supported only if the router is running in sub-package mode in order to minimize interruption to service.
Note Cisco IOS XE 2.4.2t does not support ISSU upgrade and downgrade.
|
Cisco IOS XE 2.5.0 1 12.2(33)XNE |
Cisco IOS XE 2.5.1 12.2(33)XNE1 |
Cisco IOS XE 2.5.2 12.2(33)XNE2 |
---|---|---|---|
Cisco IOS XE 2.3.0 |
SSO |
SSO |
SSO |
Cisco IOS XE 2.3.1 |
SSO |
SSO |
SSO |
Cisco IOS XE 2.3.2 |
SSO Tested |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.4.0 |
SSO |
SSO |
SSO |
Cisco IOS XE 2.4.1 |
SSO |
SSO |
SSO |
Cisco IOS XE 2.4.2 |
SSO Tested2 |
SSO Tested2 |
SSO2 |
Cisco IOS XE 2.4.3 |
SSO |
SSO |
SSO Tested |
Cisco IOS XE 2.4.4 |
SSO2 |
SSO2 |
SSO Tested2,3 |
Cisco IOS XE 2.5.01 |
— |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.5.1 |
SSO Tested |
— |
SSO Tested |
Cisco IOS XE 2.5.2 |
SSO Tested |
SSO Tested |
— |
Cisco IOS XE 2.6.0 |
SSO |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.6.1 |
SSO |
SSO |
SSO Tested |
Cisco IOS XE 2.6.2 |
SSO |
SSO |
SSO Tested3 |
1 For ATM SPAs on the Cisco ASR1000 Series Routers, ISSU from releases prior to Cisco IOS XE Release 2.5.0 to Cisco IOS XE Release 2.5.0, or from Cisco IOS XE Release 2.5.0 to a release prior to Cisco IOS XE Release 2.5.0, is not supported. If you want to perform ISSU in this environment, you must first remove the configuration from the ATM SPAs on the router, and then shut down the SPAs using the shutdown command prior to running the ISSU process. 2 PPP sessions requiring AAA authentication and authorization will not be synchronized to standby after ISSU upgrade procedure. This applies to scenarios where the Cisco ASR 1000 Series Router is acting as a PPP Termination and Aggregation (PTA) or L2TP network server (LNS) terminating PPP sessions. 3 A loopback interface Outbound Cache Entry (OCE) may be lost after an RP failover. |
Note Cisco ASR1002 and Cisco ASR1004 routers do not support ISSU upgrade and downgrade due to lack of hardware redundancy and the requirement to reboot the RP. However, the sub-package software upgrade and downgrade is supported only if the router is running in sub-package mode in order to minimize interruption to service.
Note Cisco IOS XE 2.4.2t does not support ISSU upgrade and downgrade.
|
Cisco IOS XE 2.6.0 12.2(33)XNF |
Cisco IOS XE 2.6.1 12.2(33)XNF1 |
Cisco IOS XE 2.6.2 12.2(33)XNF2 |
---|---|---|---|
Cisco IOS XE 2.4.0 |
SSO1 |
SSO1 |
SSO1 |
Cisco IOS XE 2.4.1 |
SSO1 |
SSO1 |
SSO1 |
Cisco IOS XE 2.4.2 |
SSO Tested1 |
SSO1 |
SSO1 |
Cisco IOS XE 2.4.3 |
SSO Tested1 |
SSO Tested1 |
SSO1 |
Cisco IOS XE 2.4.4 |
SSO1 |
SSO Tested1 |
SSO Tested1 |
Cisco IOS XE 2.5.0 |
SSO |
SSO |
SSO |
Cisco IOS XE 2.5.1 |
SSO Tested |
SSO |
SSO |
Cisco IOS XE 2.5.2 |
SSO Tested |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.6.0 |
— |
SSO Tested |
SSO Tested |
Cisco IOS XE 2.6.1 |
SSO Tested |
— |
SSO Tested |
Cisco IOS XE 2.6.2 |
SSO Tested |
SSO Tested |
SSO Tested |
1 PPP sessions requiring AAA authentication and authorization will not be synchronized to standby after ISSU upgrade procedure. This applies to scenarios where the Cisco ASR 1000 Series Router is acting as a PPP Termination and Aggregation (PTA) or L2TP network server (LNS) terminating PPP sessions. |
The Cisco IOS XE images and packages available vary based on the Route Processor (RP) installed in the system: RP1 or RP2.
•Table 7 describes the RP1 consolidated package images, their individual software sub-package contents, and their memory recommendations.
•Table 9 describes the RP1 optional sub-package images and their memory recommendations.
•Table 9 describes the RP2 consolidated package images, their individual software sub-package contents, and their memory recommendations.
•Table 10 describes the RP2 optional sub-package images and their memory recommendations.
Each Cisco IOS XE image also contains two provisioning files: asr1000rpx-packages.image.version.conf and packages.conf. A provisioning file is used for booting only in cases where the individual modules are extracted from the Cisco IOS XE image and then used to run the router. Either provisioning file can be used.
Note No In Service Software Upgrade (ISSU) is possible between different image types.
|
|
|
|
Memory |
---|---|---|---|---|
|
Cisco ASR 1000 Series RP1 IP BASE W/O CRYPTO |
asr1000rp1-ipbase.version.bin |
asr1000rp1-rpbase.version.pkg |
4GB (for Cisco ASR 1002 Router) 2GB-4GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp1-rpcontrol.version.pkg |
||||
asr1000rp1-rpaccess.version.pkg |
||||
asr1000rp1-rpios-ipbase.version.pkg |
||||
asr1000rp1-espbase.version.pkg |
||||
asr1000rp1-sipbase.version.pkg |
||||
asr1000rp1-sipspa.version.pkg |
||||
asr1000rp1-packages-ipbase.version. |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP1 IP BASE |
asr1000rp1-ipbasek9.version.bin |
asr1000rp1-rpbase.version.pkg |
4GB (for Cisco ASR 1002 Router) 2GB-4GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp1-rpcontrol.version.pkg |
||||
asr1000rp1-rpaccess.version.pkg |
||||
asr1000rp1-rpios-ipbasek9.version.pkg |
||||
asr1000rp1-espbase.version.pkg |
||||
asr1000rp1-sipbase.version.pkg |
||||
asr1000rp1-sipspa.version.pkg |
||||
asr1000rp1-packages-ipbasek9.version.conf |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES W/O CRYPTO1 |
asr1000rp1-advipservices.version. |
asr1000rp1-rpbase.version.pkg |
4GB (for Cisco ASR 1002 Router) 2GB-4GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp1-rpcontrol.version.pkg |
||||
asr1000rp1-rpaccess.version.pkg |
||||
asr1000rp1-rpios-advipservices. |
||||
asr1000rp1-espbase.version.pkg |
||||
asr1000rp1-sipbase.version.pkg |
||||
asr1000rp1-sipspa.version.pkg |
||||
asr1000rp1-packages-advipservices. |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES |
asr1000rp1-advipservicesk9.version.bin |
asr1000rp1-rpbase.version.pkg |
4GB (for Cisco ASR 1002 Router) 2GB-4GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp1-rpcontrol.version.pkg |
||||
asr1000rp1-rpaccess.version.pkg |
||||
asr1000rp1-rpios-ipbasek9.version.pkg |
||||
asr1000rp1-espbase.version.pkg |
||||
asr1000rp1-sipbase.version.pkg |
||||
asr1000rp1-sipspa.version.pkg |
||||
asr1000rp1-packages-advipservicesk9. |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES W/O CRYPTO2 |
asr1000rp1-adventservices.version. |
asr1000rp1-rpbase.version.pkg |
4GB (for Cisco ASR 1002 Router) 2GB-4GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp1-rpcontrol.version.pkg |
||||
asr1000rp1-rpaccess.version.pkg |
||||
asr1000rp1-rpios-adventservices. |
||||
asr1000rp1-espbase.version.pkg |
||||
asr1000rp1-sipbase.version.pkg |
||||
asr1000rp1-sipspa.version.pkg |
||||
asr1000rp1-packages-adventservices. |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES |
asr1000rp1-adventservicesk9.version.bin |
asr1000rp1-rpbase.version.pkg |
4GB (for Cisco ASR 1002 Router) 2GB-4GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp1-rpcontrol.version.pkg |
||||
asr1000rp1-rpaccess.version.pkg |
||||
asr1000rp1-rpios-adventservicesk9. |
||||
asr1000rp1-espbase.version.pkg |
||||
asr1000rp1-sipbase.version.pkg |
||||
asr1000rp1-sipspa.version.pkg |
||||
asr1000rp1-packages-adventservicesk9. |
||||
packages.conf |
1 The Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES W/O CRYPTO consolidated package is only available with Cisco IOS XE Release 2.2.1 through Cisco IOS XE Release 2.3.x. This consolidated package is not available with any other Cisco IOS XE Releases. 2 The Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES W/O CRYPTO consolidated package is only available beginning with Cisco IOS XE Release 2.2.1 and later releases. This consolidated package is not available with Cisco IOS XE Release 2.1.2 and earlier releases. |
|
|
|
|
---|---|---|---|
|
Cisco ASR 1000 Series RP1 WebEx Node1 |
asr1000rp1-sipspawmak9.version.XND.pkg |
100MB |
1 The Cisco ASR 1000 Series RP1 WebEx Node (asr1000rp1-sipspawmak9.version.pkg) optional software sub-package is only available beginning with Cisco IOS XE Release 2.4.0 and later releases and only supported in conjunction with the Cisco ASR 1000 Series RP1 IP BASE, Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES, or Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES consolidated package. This sub-package is not supported with earlier Cisco IOS XE releases or with any of the non-CRYPTO consolidated packages. |
Note The RP2 images are available beginning with Cisco IOS XE Release 2.3.0.
|
|
|
|
Memory |
---|---|---|---|---|
|
Cisco ASR 1000 Series RP2 IP BASE W/O CRYPTO |
asr1000rp2-ipbase.version.bin |
asr1000rp2-rpbase.version.pkg |
8GB-16GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp2-rpcontrol.version.pkg |
||||
asr1000rp2-rpaccess.version.pkg |
||||
asr1000rp2-rpios-ipbase.version.pkg |
||||
asr1000rp2-espbase.version.pkg |
||||
asr1000rp2-sipbase.version.pkg |
||||
asr1000rp2-sipspa.version.pkg |
||||
asr1000rp2-packages-ipbase.version. |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP2 IP BASE |
asr1000rp2-ipbasek9.version.bin |
asr1000rp2-rpbase.version.pkg |
8GB-16GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp2-rpcontrol.version.pkg |
||||
asr1000rp2-rpaccess.version.pkg |
||||
asr1000rp2-rpios-ipbasek9.version. pkg |
||||
asr1000rp2-espbase.version.pkg |
||||
asr1000rp2-sipbase.version.pkg |
||||
asr1000rp2-sipspa.version.pkg |
||||
asr1000rp2-packages-ipbasek9.version.conf |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP2 ADVANCED IP SERVICES W/O CRYPTO1 |
asr1000rp2-advipservices.version. |
asr1000rp2-rpbase.version.pkg |
8GB-16GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp2-rpcontrol.version.pkg |
||||
asr1000rp2-rpaccess.version.pkg |
||||
asr1000rp2-rpios-advipservices. |
||||
asr1000rp2-espbase.version.pkg |
||||
asr1000rp2-sipbase.version.pkg |
||||
asr1000rp2-sipspa.version.pkg |
||||
asr1000rp2-packages-advipservices. |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP2 ADVANCED IP SERVICES |
asr1000rp2-advipservicesk9. |
asr1000rp2-rpbase.version.pkg |
8GB-16GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp2-rpcontrol.version.pkg |
||||
asr1000rp2-rpaccess.version.pkg |
||||
asr1000rp2-rpios-advipservicesk9. |
||||
asr1000rp2-espbase.version.pkg |
||||
asr1000rp2-sipbase.version.pkg |
||||
asr1000rp2-sipspa.version.pkg |
||||
asr1000rp2-packages-advipservicesk9. |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP2 ADVANCED ENTERPRISE SERVICES W/O CRYPTO |
asr1000rp2-adventservices.version.bin |
asr1000rp2-rpbase.version.pkg |
8GB-16GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp2-rpcontrol.version.pkg |
||||
asr1000rp2-rpaccess.version.pkg |
||||
asr1000rp2-rpios-adventservices. |
||||
asr1000rp2-espbase.version.pkg |
||||
asr1000rp2-sipbase.version.pkg |
||||
asr1000rp2-sipspa.version.pkg |
||||
asr1000rp2-packages-adventservices. |
||||
packages.conf |
||||
|
Cisco ASR 1000 Series RP2 ADVANCED ENTERPRISE SERVICES |
asr1000rp2-adventservicesk9. |
asr1000rp2-rpbase.version.pkg |
8GB-16GB(for Cisco ASR 1004 and Cisco ASR 1006 routers) |
asr1000rp2-rpcontrol.version.pkg |
||||
asr1000rp2-rpaccess.version.pkg |
||||
asr1000rp2-rpios-adventservicesk9. |
||||
asr1000rp2-espbase.version.pkg |
||||
asr1000rp2-sipbase.version.pkg |
||||
asr1000rp2-sipspa.version.pkg |
||||
asr1000rp2-packages-adventservicesk9. |
||||
packages.conf |
1 The Cisco ASR 1000 Series RP2 ADVANCED IP SERVICES W/O CRYPTO consolidated package is only available with Cisco IOS XE Release 2.3.0 through the Cisco IOS XE Release 2.3.x. This consolidated package is not available with any other Cisco IOS XE Releases. |
|
|
|
|
---|---|---|---|
|
Cisco ASR 1000 Series RP2 WebEx Node1 |
asr1000rp2-sipspawmak9.version.XND.pkg |
100MB |
1 The Cisco ASR 1000 Series RP2 WebEx Node (asr1000rp1-sipspawmak9.version.pkg) optional software sub-package is only available beginning with Cisco IOS XE Release 2.4.0 and later releases and only supported in conjunction with the Cisco ASR 1000 Series RP2 IP BASE, Cisco ASR 1000 Series RP2 ADVANCED IP SERVICES, or Cisco ASR 1000 Series RP2 ADVANCED ENTERPRISE SERVICES consolidated package. This sub-package is not supported with earlier Cisco IOS XE releases or with any of the non-CRYPTO consolidated packages. |
Cisco IOS XE Release 2 supports the following Cisco ASR 1000 Series Routers:
•Cisco ASR 1002 Router
•Cisco ASR 1002-F Router
•Cisco ASR 1004 Router
•Cisco ASR 1006 Router
For descriptions of the new hardware features, see the "New and Changed Information" section.
This section describes the recommended and minimum ROMmon version requirements for Cisco IOS XE Release 2.
•The recommended ROMmon versions supported by the ROMmon upgradeable components for each Cisco IOS XE release are listed in the "Recommended ROMmon Versions for Cisco IOS XE Releases" subsection that follows.
•The minimum ROMmon versions required to support each specific ROMmon upgradeable component are listed in Table 11.
Recommended ROMmon Versions for Cisco IOS XE Releases
The recommended ROMmon version for Cisco IOS XE Release 2.6.0 and its rebuilds is Version 12.2(33r)XND1 for all ROMmon upgradeable components
The recommended ROMmon version for Cisco IOS XE Release 2.5.0 and its rebuilds is Version 12.2(33r)XND1 for all ROMmon upgradeable components
The recommended ROMmon version for Cisco IOS XE Release 2.4.0 and its rebuilds is Version 12.2(33r)XND1 for all ROMmon upgradeable components.
Note For customers requiring a FIPS 140-2 compliant environment, ROMmon Version 12.2(33r)XND is a required update.
The recommended ROMmon version to support the RP2 for Cisco IOS XE Release 2.3.2 is Version 12.2(33r)XNC0. The recommended ROMmon version to support the ASR1002, RP1, ESP5, ESP10, ESP10-N, ESP20, and SIP10 for Cisco IOS XE Release 2.3.2 is Version 12.2(33r)XNB.
The recommended ROMmon version to support the RP2 for Cisco IOS XE Release 2.3.1 is Version 12.2(33r)XNC0. The recommended ROMmon version to support the ASR1002, RP1, ESP5, ESP10, ESP10-N, ESP20, and SIP10 for Cisco IOS XE Release 2.3.1 is Version 12.2(33r)XNB.
The recommended ROMmon version to support the RP2 for Cisco IOS XE Release 2.3.0 is Version 12.2(33r)XNC0. The recommended ROMmon version to support the ASR1002, RP1, ESP5, ESP10, ESP10-N, ESP20, and SIP10 for Cisco IOS XE Release 2.3.0 is Version 12.2(33r)XNB.
The recommended ROMmon version for Cisco IOS XE Release 2.2.3 is Version 12.2(33r)XNB for all ROMmon upgradeable components.
The recommended ROMmon version for Cisco IOS XE Release 2.2.2 is Version 12.2(33r)XNB for all ROMmon upgradeable components.
The recommended ROMmon version for Cisco IOS XE Release 2.2.1 is Version 12.2(33r)XNB for all ROMmon upgradeable components.
The recommended ROMmon version supported for Cisco IOS XE Release 2.1.2 is Version 12.2(33r)XN2 for all ROMmon upgradeable components.
The recommended ROMmon version supported for Cisco IOS XE Release 2.1.1 is Version 12.2(33r)XN2 for all ROMmon upgradeable components.
The recommended ROMmon version supported for Cisco IOS XE Release 2.1.0 is Version 12.2(33r)XN2 for all ROMmon upgradeable components.
Note The minimum ROMmon version supported for Cisco IOS Release 2.1.x and later releases is Version 12.2(33r)XN2. Version 12.2(33r)XN2 is required to support the Cisco ASR 1002 Router. If support is not required for the Cisco ASR 1002 Router, the minimum ROMmon version required is Version 12.2(33r)XN1.
|
|
|
|
|
---|---|---|---|---|
ASR10021 |
X |
X |
||
ASR1002-F2 |
X |
X |
||
RP1 |
X |
X |
||
RP2 |
X |
X3 |
||
ESP5 |
X |
|||
ESP10 |
X |
|||
ESP10-N |
X |
|||
ESP20 |
X |
|||
SIP10 |
X |
1 ROMmon upgradeable components on the ASR1002: integrated RP1, field-replaceable ESP, and integrated SIP10. 2 ROMmon upgradeable components on the ASR1002-F: integrated RP1, ESP, and SIP10. 3 In 12.2(33r)XND1, when ROMmon is upgraded on RP2, show platform displays 12.2(33r)XND. |
To determine the version of the Cisco IOS XE Software (consolidated package) running on your Cisco ASR 1000 Series Router, log in to the router and enter the show version EXEC command:
Router# show version
Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-IPBASE-M), Version 12.2(33)XNF2,
RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Wed 07-Jul-10 01:35 by mcpre
Cisco IOS-XE software, Copyright (c) 2005-2010 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
ROM: IOS-XE ROMMON
Router uptime is 1 minute
Uptime for this control processor is 3 minutes
System returned to ROM by reload
System restarted at 06:05:49 UTC Wed Jul 7 2010
System image file is "tftp:/auto/tftp-smoke2/mcpdt-6ru-15/vmlinux"
Last reload reason: PowerOn
cisco ASR1006 (RP2) processor with 4407369K/6147K bytes of memory.
5 Gigabit Ethernet interfaces
2 Packet over SONET interfaces
2 Channelized T3 ports
32768K bytes of non-volatile configuration memory.
8388608K bytes of physical memory.
1925119K bytes of eUSB flash at bootflash:.
78085207K bytes of SATA hard disk at harddisk:.
Configuration register is 0x2
To determine the version of the individual sub-packages running on your Cisco ASR 1000 Series Router, log in to the router and enter the show version installed command in User EXEC, Privileged EXEC or Diagnostic mode.
Note The checksums in the show version installed output that follows are for example purposes only; the checksum values that appear in your output may vary.
Router# show version installed
Package: Provisioning File, version: n/a, status: active
File: consolidated:packages.conf, on: RP0
Built: n/a, by: n/a
File SHA1 checksum: 00b8d95bd6aa71795d9817492dfe2723a4cf7ca2
Package: rpbase, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-rpbase.02.06.02.122-33.XNF2.pkg, on: RP0
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: a6b9bea258d081075e65e8fe1867d5d680f85703
Package: rpcontrol, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-rpcontrol.02.06.02.122-33.XNF2.pkg, on: RP0/0
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: 54ac3da1473dd1e37796b1f5afa83b5c4a96f537
Package: rpios-ipbase, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-rpios-ipbase.02.06.02.122-33.XNF2.pkg, on: RP0/0
Built: 2010-07-07_03.12, by: mcpre
File SHA1 checksum: ffcd38ab5a39537121c83c23067459a9c1b485cb
Package: rpaccess, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-rpaccess.02.06.02.122-33.XNF2.pkg, on: RP0/0
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: ffccabb82f70fd6a21ad5a3128585104d6508965
Package: rpcontrol, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpcontrol.02.06.02.122-33.XNF2.pkg, on: RP0/1
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: 54ac3da1473dd1e37796b1f5afa83b5c4a96f537
Package: rpios-ipbase, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpios-ipbase.02.06.02.122-33.XNF2.pkg, on: RP0/1
Built: 2010-07-07_03.12, by: mcpre
File SHA1 checksum: ffcd38ab5a39537121c83c23067459a9c1b485cb
Package: rpaccess, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpaccess.02.06.02.122-33.XNF2.pkg, on: RP0/1
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: ffccabb82f70fd6a21ad5a3128585104d6508965
Package: rpbase, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpbase.02.06.02.122-33.XNF2.pkg, on: RP1
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: a6b9bea258d081075e65e8fe1867d5d680f85703
Package: rpcontrol, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpcontrol.02.06.02.122-33.XNF2.pkg, on: RP1/0
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: 54ac3da1473dd1e37796b1f5afa83b5c4a96f537
Package: rpios-ipbase, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpios-ipbase.02.06.02.122-33.XNF2.pkg, on: RP1/0
Built: 2010-07-07_03.12, by: mcpre
File SHA1 checksum: ffcd38ab5a39537121c83c23067459a9c1b485cb
Package: rpaccess, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpaccess.02.06.02.122-33.XNF2.pkg, on: RP1/0
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: ffccabb82f70fd6a21ad5a3128585104d6508965
Package: rpcontrol, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpcontrol.02.06.02.122-33.XNF2.pkg, on: RP1/1
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: 54ac3da1473dd1e37796b1f5afa83b5c4a96f537
Package: rpios-ipbase, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpios-ipbase.02.06.02.122-33.XNF2.pkg, on: RP1/1
Built: 2010-07-07_03.12, by: mcpre
File SHA1 checksum: ffcd38ab5a39537121c83c23067459a9c1b485cb
Package: rpaccess, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-rpaccess.02.06.02.122-33.XNF2.pkg, on: RP1/1
Built: 2010-07-07_03.10, by: mcpre
File SHA1 checksum: ffccabb82f70fd6a21ad5a3128585104d6508965
Package: espbase, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-espbase.02.06.02.122-33.XNF2.pkg, on: ESP0
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: f27b18ddc451406d23fd849e3a1b405f72531028
Package: espbase, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-espbase.02.06.02.122-33.XNF2.pkg, on: ESP1
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: f27b18ddc451406d23fd849e3a1b405f72531028
Package: sipbase, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-sipbase.02.06.02.122-33.XNF2.pkg, on: SIP0
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: 57de38b3a28e2bfe613eb1c14d14758eeced0bee
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP0/0
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP0/1
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP0/2
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP0/3
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipbase, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-sipbase.02.06.02.122-33.XNF2.pkg, on: SIP1
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: 57de38b3a28e2bfe613eb1c14d14758eeced0bee
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP1/0
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP1/1
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP1/2
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP1/3
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipbase, version: 02.06.02.122-33.XNF2, status: active
File: consolidated:asr1000rp2-sipbase.02.06.02.122-33.XNF2.pkg, on: SIP2
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: 57de38b3a28e2bfe613eb1c14d14758eeced0bee
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP2/0
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP2/1
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP2/2
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP2/3
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipbase, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipbase.02.06.02.122-33.XNF2.pkg, on: SIP3
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: 57de38b3a28e2bfe613eb1c14d14758eeced0bee
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP3/0
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP3/1
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP3/2
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP3/3
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipbase, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipbase.02.06.02.122-33.XNF2.pkg, on: SIP4
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: 57de38b3a28e2bfe613eb1c14d14758eeced0bee
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP4/0
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP4/1
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP4/2
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP4/3
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipbase, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipbase.02.06.02.122-33.XNF2.pkg, on: SIP5
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: 57de38b3a28e2bfe613eb1c14d14758eeced0bee
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP5/0
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP5/1
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP5/2
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Package: sipspa, version: 02.06.02.122-33.XNF2, status: n/a
File: consolidated:asr1000rp2-sipspa.02.06.02.122-33.XNF2.pkg, on: SIP5/3
Built: 2010-07-07_02.56, by: mcpre
File SHA1 checksum: fca726414781540f44dc166859a786bd1dc6279e
Each version of Cisco IOS XE has an associated Cisco IOS version. Table 12 lists these mappings for all released versions of Cisco IOS XE.
Note The Cisco IOS XE 2.3.0 and Cisco IOS XE 2.3.1 images are no longer downloadable from Cisco.com. Replacement images (Cisco IOS XE 2.3.0t and Cisco IOS XE 2.3.1t) with exactly the same content and bug fixes are available on Cisco.com. If the Cisco IOS XE 2.3.0 and Cisco IOS XE 2.3.1 images are not causing any issues, no action is necessary. Old image MD5 sums will still be available for verification on the download page. For more details, see CSCsz80074.
Only Cisco IOS XE consolidated packages can be downloaded from Cisco.com; users who want to run the router using individual sub-packages must first download the image from Cisco.com and extract the individual sub-packages from the consolidated package.
For information about upgrading to a new software release, see the following document:
Cisco ASR 1000 Series Aggregation Services Router Software Configuration Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/chassis/asrswcfg.html
This section lists the new hardware and software features that are supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2 and contains the following sections:
•New Hardware Features in Cisco IOS XE Release 2.6.2
•New Software Features in Cisco IOS XE Release 2.6.2
•New Hardware Features in Cisco IOS XE Release 2.6.1
•New Software Features in Cisco IOS XE Release 2.6.1
•New Hardware Features in Cisco IOS XE Release 2.6.0
•New Software Features in Cisco IOS XE Release 2.6.0
•New Hardware Features in Cisco IOS XE Release 2.5.2
•New Software Features in Cisco IOS XE Release 2.5.2
•New Hardware Features in Cisco IOS XE Release 2.5.1
•New Software Features in Cisco IOS XE Release 2.5.1
•New Hardware Features in Cisco IOS XE Release 2.5.0
•New Software Features in Cisco IOS XE Release 2.5.0
•New Hardware Features in Cisco IOS XE Release 2.4.3
•New Software Features in Cisco IOS XE Release 2.4.3
•New Hardware Features in Cisco IOS XE Release 2.4.4
•New Software Features in Cisco IOS XE Release 2.4.4
•New Hardware Features in Cisco IOS XE Release 2.4.2t
•New Software Features in Cisco IOS XE Release 2.4.2t
•New Hardware Features in Cisco IOS XE Release 2.4.2
•New Software Features in Cisco IOS XE Release 2.4.2
•New Software Features in Cisco IOS XE Release 2.4.1
•New Hardware Features in Cisco IOS XE Release 2.4.0
•New Software Features in Cisco IOS XE Release 2.4.0
•New Hardware Features in Cisco IOS XE Release 2.3.2
•New Software Features in Cisco IOS XE Release 2.3.2
•New Hardware Features in Cisco IOS XE Release 2.3.1
•New Software Features in Cisco IOS XE Release 2.3.1
•New Hardware Features in Cisco IOS XE Release 2.3.0
•New Software Features in Cisco IOS XE Release 2.3.0
•New Hardware Features in Cisco IOS XE Release 2.2.3
•New Software Features in Cisco IOS XE Release 2.2.3
•New Hardware Features in Cisco IOS XE Release 2.2.2
•New Software Features in Cisco IOS XE Release 2.2.2
•New Hardware Features in Cisco IOS XE Release 2.2.1
•New Software Features in Cisco IOS XE Release 2.2.1
•New Hardware Features in Cisco IOS XE Release 2.1.2
•New Software Features in Cisco IOS XE Release 2.1.2
•New Hardware Features in Cisco IOS XE Release 2.1.1
•New Software Features in Cisco IOS XE Release 2.1.1
•New Hardware Features in Cisco IOS XE Release 2.1.0
•New Software Features in Cisco IOS XE Release 2.1.0
•Release Note Only Software Features in Cisco IOS XE Release 2.1.0
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.6.2.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.6.2.
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.6.1.
This section lists new and changed features in Cisco IOS XE Release 2.6.1. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE:
•CUBE(SP Edition) - Billing:Packet Cable Billing support for Adjacency Information
•OER - Application Aware Routing with Static Application Mapping
•OER Border Router Only Functionality
•OER - Inbound Optimization through BGP
•OER Port and Protocol Based Prefix Learning
•OER Support for Cost-Based Optimization and Traceroute Reporting
•OER Support for Policy-Rules Configuration and Port-Based Prefix Learning
•OER VPN IPSec with GRE Tunnel Optimization
•OER - Voice Traffic Optimization
•PfR EIGRP mGRE DMVPN Hub-and-Spoke Support
•PfR - Protocol Independent Route Optimization (PIRO)
This feature allows for user configurable source address for Optimized Edge Routing (OER) Active Probes.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-advanced.html
For information about these Cisco Unified Border Element (SP Edition) features, see the following documents:
Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/sbcu/2_xe/sbcu_2_xe_book.html
Cisco Unified Border Element (SP Edition) Command Reference: Unified Model
http://www.cisco.com/en/US/docs/ios/sbc/command/reference/sbcu_book.html
This feature allows for optimize application traffic using PBR (Policy Based Routing).
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-stat-app-map.html
Optimized Edge Routing (OER) Border Router master controller software has been modified to handle the limited functionality.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/pfr/configuration/guide/pfr-br-only_xe.html
This feature allows for Optimized Edge Routing (OER) monitors and optimizes inbound (to enterprise) traffic using BGP advertisements to BGP external peers.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-bgp-inbound.html
OER Port and Protocol Based Prefix Learning allows one to configure a master controller to learn prefixes based on the protocol type and TCP or UDP port number.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-understand.html
This enhancement provides outbound traffic optimization based on financial link cost (i.e., fixed cost versus tier based cost). This release also adds support for traceroute reporting.
For more information, see the following documents:
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-trace.html
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-cost.html
OER support for policy-rule configuration and port-based prefix learning.
For more information, see the following documents:
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-advanced.html
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-understand.html
VPN IPSec/GRE Tunnel Optimization introduces the capability to configure IPSec with GRE tunnel interfaces as OER managed exit links. Only network based IPSec VPNs are supported.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-gre-exit.html
This feature allows for Optimize Route Control for Voice traffic on the network.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-voice-traffic.html
This gives PfR the ability to inject routes into the EIGRP routing table in order to control prefixes and applications over EIGRP routes. Also adds support for mGRE DMVPN deployments. Currently only supports Hub- and-Spoke, not Spoke-to-Spoke
For more information, see the following document
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-eigrp-mgre.html
This feature removes the requirement of having BGP or static parent routes and allows PfR to operate with any routing protocol.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/pfr/configuration/guide/pfr-piro.html
The following hardware features are supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.6.0:
The 1-Port Channelized OC-12/STM-4 SPA is a double-height serial SPA that can be installed into two, vertically-aligned SIP subslots. The channelized OC-12 SPA with small form-factor pluggable (SFP) optical transceiver modules provides SONET network connectivity with a per-port bandwidth of 622.08 Mbps, and supports channelization from OC-12 down to DS0 line rates.
For information about the 1-Port Channelized OC-12/STM-4 SPA and other SPAs supported on the Cisco ASR 1000 Series Routers, see the following documents:
Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide at:
Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Software Configuration Guide at:
http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/configuration/ASR1000/ASRspasw.html
This section lists new and changed features in Cisco IOS XE Release 2.6.0. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE:
•AAA: Supress System Accounting On Switchover
•ASRNAT - Overload Scaling Improvement - Support 800 Overloaded Pools
•BGP RT Changes Without PE-CE Neighbor Impact
•BGP Support for the L2VPN Address Family
•Broadband IPv6 Support at LNS
•CLNS Support for GRE Tunneling of IPv4 and IPv6
•Control Plane DSCP Support for RSVP
•Enabling OSPFv2 on an Interface Basis
•IGMP MIB Support Enhancements for SNMP
•IGMP Static Group Range Support
•IPv6 - Full Selective Packet Discard (SPD) Support
•IPv6 - Per Interface Neighbor Discovery Cache Limit
•IPv6 Multicast: Bandwidth-Based Call Admission Control (CAC)
•IPv6 Routing: IS-IS Multitopology Support for IPv6
•IPv6: Multicast Address Group Range Support
•IS-IS Fast-Flooding of LSPs Using the fast-flood Command
•IS-IS Limit on Number of Redistributed Routes
•Layer 2 Tunnel Protocol Version 3
•MPLS MTU command for GRE Tunnels
•MPLS TE--Tunnel-Based Admission Control (TBAC)
•Multicast Address Group Range Support
•Multiprotocol BGP (MP-BGP) Support for CLNS
•http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_bgp/configuration/guide/irg_sup_clns_xe.html
•OSPF Link-State Advertisement Throttling
•OSPF Mechanism to Exclude Connected IP Prefixes from LSA Advertisements
•OSPF SNMP ifIndex Value for Interface ID
•OSPF Limit on Number of Redistributed Routes
•Quality of Service: Policies Aggregation
•RSVP Fast Local Repair (RSVP FLR)
•RSVP Interface-based Receiver Proxy
•RSVP Scalability Enhancements
•SNMP Traps for PPPoE Session Limits
•Support for Software Media Termination Point (MTP) on the Cisco Unified Border Element (Enterprise)
•T.38 Fax Support on the Cisco Unified Border Element (Enterprise)
•VRRP: Virtual Router Redundancy (VRRS)
•Zone Based Firewall: Default Zone
•Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model
Suppressing System Accounting Records over Switchover allows to suppress the system accounting-on and accounting-off messages during switchover.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_cfg_accountg_ps10591_TSD_Products_Configuration_Guide_Chapter.html
Network Address Translation (NAT) now supports 800 overloaded pools on Cisco ASR 1000 series Routers with a 20-Gbps Embedded Services Processor (ESP).
For more information, see the following document:
For more information, see the following document:
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/iproute_bgp/configuration/guide/irg_overview.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
The Call Home feature provides e-mail-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard e-mail, or XML-based automated parsing applications. Common uses of this feature may include direct paging of a network support engineer, e-mail notification to a Network Operations Center, XML delivery to a support website, and utilization of Cisco Smart Call Home services for direct case generation with the Cisco Systems Technical Assistance Center (TAC).
For more information, see the feature documentation in the Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide at:
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/chassis/callhome_asr1k.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/isoclns/configuration/guide/configure_iso_clns.html
This feature allows for RSVP control message precedence and DSCP support.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/dscp_spt_for_rsvp_xe.html
Today there is no way for the user/administrator to exclude IP address range in different VRF address spaces. The intention of this work is to extend the present command line interface support creation of IP address exclusion list in different address spaces.For more information, see the following document:
The EIGRP Prefix Limit Support the feature allows for EIGRP Provider and Customer Edge Prefix Limit Support.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_eigrp/configuration/guide/ire_pref_limit_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_ospf/configuration/guide/iro_mode_ospfv2_xe.html
The Internet Group Management Protocol (IGMP) is used by IP hosts to report their multicast group memberships to neighboring multicast routers. The IGMP MIB describes objects that enable users to remotely monitor and configure IGMP using Simple Network Management Protocol (SNMP). It also allows users to remotely subscribe and unsubscribe from multicast groups. The IGMP MIB Support Enhancements for SNMP feature adds full support of RFC 2933 (Internet Group Management Protocol MIB) in Cisco IOS software.
There are no new or modified Cisco IOS commands associated with this feature.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipmulti/configuration/guide/imc_igmp_static_rng_xe.html
For more information, see the following document:
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ipmulti/configuration/guide/imc_customize_igmp.html
The IP-RIP Delay Start feature is used when a Cisco ASR Router is configured to establish a RIPv2 neighbor relationship using MD5 authentication with a non-Cisco device over a Frame Relay network.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_rip/configuration/guide/irr_cfg_rip_xe.html
IPv6 Full Selective Packet Discard (SPD) feature restores parity between SPD function for IPv4 and IPv6.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-spd_xe.html
IPv6 - Per interface Neighbor Discovery Cache Limit feature allows for a number of entries in the ND cache is limited on an interface basis. Once the limit is reached, no new entries are allowed.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-is-is_xe.html
The Bandwidth Based CAC for IPv6 Multicast feature implements a method to monitor bandwidth per interface and multicast group avoiding oversubscription due to multicast services.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-is-is_xe.html
IPv6 PIM Passive feature enable PIM passive mode on interface. PIM passive interface doesnt send and receive PIM control messages but it can act as RPF interface for multicast route entries and accept/forward multicast data packet.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html
Support for routing IPv6 Prefixes in IS-IS is using a multi-topology solution.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-is-is_xe.html
IPv6 Multicast Address Group Range feature allows for disables all operations for groups denied by <acl>. Drop/ignore group in all control packets - PIM, MLD.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html
The IS-IS Fast-Flooding of LSPs Using the fast-flood Command feature improves Intermediate System-to-Intermediate System (IS-IS) convergence time when new link-state packets (LSPs) are generated in the network and SPF is triggered by the new LSPs.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_isis/configuration/xe-3s/Reducing_Link_Failure_and_Topology_Change_Notification_Times_in_IS-IS_Networks.html
The IS-IS Limit on Number of Redistributed Routes feature provides for a user-defined maximum number of prefixes that are allowed to be redistributed into IS-IS from other protocols or other IS-IS processes. Such a limit can help prevent the router from being flooded by too many redistributed routes.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_isis/configuration/guide/irs_fscpc_xe.html
The IS-IS Support for Route Tags feature provides the capability to tag IS-IS route prefixes and use those tags in a route map to control IS-IS route redistribution or route leaking.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_isis/configuration/guide/irs_fscpc_xe.html
In Cisco IOS XE Release 2.6, pre-provisioning of circuit-ID based tapping of a PPP session is introduced. If the tap is provisioned before a user session is active, then the tap is effective whenever the user session becomes active. Also, corresponding RADIUS authentication and accounting packets are tapped. It is assumed in this instance that the user session is uniquely identified by a circuit ID tag.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/sec_user_services/configuration/guide/sec_lawful_intercept_xe.html
The Layer 2 Tunnel Protocol Version 3 (L2TPv3) feature expands Cisco support of Layer 2 Tunnel Protocol (L2TP). L2TPv3 is an Internet Engineering Task Force (IETF) Layer Two Tunneling Protocol Extensions (l2tpext) working group draft that provides several enhancements to L2TP for the capability to tunnel any Layer 2 payload over L2TP. Specifically, L2TPv3 defines the L2TP protocol for tunneling Layer 2 payloads over an IP core network using Layer 2 Virtual Private Networks (VPNs).
In addition Cisco IOS XE Release 2.6.0 introduces support for the following Layer 2 Tunnel Protocol Version 3 (L2TPv3) features:
•Ethernet over L2TPv3
•IfTable MIB for attachment circuit
•L2TPv3 - Layer-2 Tunneling Protocol Version 3
•L2TPv3 Basic Features
•L2TPv3 Control Message Hashing
•L2TPv3 Control Message Rate Limiting
•L2TPv3 Digest Secret Graceful Switchover
•L2TPv3: Custom Ethertype for Dot1Q and QinQ encapsulations
•L2TPv3: Remote Ethernet Port Shutdown
•Layer 2 VPN (L2 VPN): Syslog, SNMP Trap, and show Command Enhancements for AToM and L2TPv3
•Protocol Demultiplexing for L2TPv3
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios-xml/ios/mp_l2_vpns/configuration/xe-3s/mp-any-transport-xe.html
Tunnel Based Admission Control Phase.1 addresses the need to aggregate RSVP flows into a static multi-hop MPLS-TE tunnel. It is based on RFC 4804.
For more information, see the following document:
The Multicast Address Group Range Support feature enhances multicast access control by introducing the capability to define a global range of multicast groups and channels to be permitted or denied using the ip multicast group-range command.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/2/release/notes/rnasr21.html
The Multicast VRF MIB Support feature is an enhancement to help manage Cisco devices in a multicast VPN environment using SNMP.
This feature enhances the Cisco suite of supported multicast MIBs by making the following multicast MIBs MVRF aware:
CISCO-IPMROUTE-MIB
CISCO-PIM-MIB
IGMP-STD-MIB
IPMROUTE-STD-MIB
MSDP-MIB
PIM-MIB
Multicast VRF (MVRF) awareness enables the MIB objects associated with these Multicast MIBs to be queried and set for the individual MVRFs configured. In addition, MVRF awareness provides the capability to detect conditions for a trap inside of a MVRF and lookup the correct information for that MVRF; the traps would then be sent to the SNMP manager that is configured for that MVRF.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/2/release/notes/rnasr21.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_bgp/configuration/guide/irg_sup_clns_xe.html
This feature enables export of netflow data to a destination whose route is in a virutal routing table other than the global table.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/netflow/command/reference/nf_01.html#wp1049093
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_ospf/configuration/guide/iro_lsa_throt_xe.html
This feature provides OSPF mechanism to exclude IP prefixes of connected networks from link state advertisements (LSAs), thereby reducing OSPF convergence time.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_ospf/configuration/guide/iro_ex_lsa_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_ospf/configuration/guide/iro_sham_mib_xe.html
A configuration command will be added to the router ospf configuration for both OSPFv2 and OSPFv3 which, when enabled, will cause OSPF to use the SNMP MIB-II ifIndex number to identify interfaces.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_ospf/configuration/guide/iro_snmp_ifindex_xe.html
OSPF support for setting a maximum number of prefixes to be redistributed/imported from other protocols (SSO Capable).
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_ospf/configuration/guide/iro_lim_routes_xe.html
The PIM Triggered Joins feature is a multicast HA enhancement that improves the reconvergence of mroutes after an RP switchover. In the event of an RP switchover, this feature utilizes the PIM-SM GenID value as a mechanism to trigger adjacent PIM neighbors on an interface to send PIM join messages for all (*, G) and (S, G) mroutes that use that interface as an RPF interface, immediately reestablishing those states on the newly active RP.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipmulti/configuration/guide/imc_high_availability_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/qos_policies_agg_xe.html
Flow aggregation is a mechanism wherein RSVP state can be reduced in a router by aggregating many smaller reservations into a single larger reservation.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/qos_rsvp_agg_xe.html
This feature enhances RSVP to integrate with the IGP routewatch functionality, which will allow it to respond to routing changes with sub-second response time.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/rsvp_app_id_support_xe.html
This feature enhances RSVP to integrate with the IGP routewatch functionality, which will allow it to respond to routing changes with sub-second response time.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/rsvp_fast_local_rpr_xe.html
This feature allows for RSVP Receiver Proxy configuration based on outbound interface.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/rsvp_receiver_proxy_xe.html
RSVP feature enhancements will improve the ASR 1000 Router Series performance and scalability.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/rsvp_scalability_xe.html
The RSVP Support for IP Sessions feature allows Resource Reservation Protocol (RSVP) and Intelligent Services Gateway (ISG) to coexist in a structured framework in which edge access devices can deliver flexible and scalable services that include voice on demand (VoD) call admission control (CAC) to subscribers.
The SNMP traps for PPPoE session limits feature implements SNMP MIB support for PPPoE session limits which are configured using the following bba-group commands:
Session Limit/Throttle bba-group command
---------------------- ----------------------------------------
per-mac limit sessions per-mac limit <n>
sessions per-mac iwf limit <n>
per-vlan limit sessions per-vlan limit <n>
per-vc limit sessions per-vc limit <n>
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios-xml/ios/bbdsl/configuration/xe-3s/bba-mon-pppoe-snmp-xe.html
A software Media Termination Point (MTP) bridges the media streams between two connections allowing Cisco Unified Communications Manager to relay calls that are routed through SIP or H.323 endpoints via Skinny Call Control Protocol (SCCP) commands. This feature extends the software MTP support to the Cisco Unified Border Element (Enterprise).
For more information, see the following document:
This feature allows for the use of T.38 fax relay on an IP network. T.38 is an ITU standard that defines how fax communications are packetized and transported over IP networks. This feature extends the T.38 fax signaling and T.38 fax over UDP packets support to the Cisco Unified Border Element (Enterprise).
There are no new or modified command introduced by this feature.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios-xml/ios/voice/config_library/xe-3s/cube-xe-3s-library.html
The VRF-Aware IPsec feature introduces IP Security (IPsec) tunnel mapping to Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). Using the VRF-Aware IPsec feature, you can map IPsec tunnels to Virtual Routing and Forwarding (VRF) instances using a single public-facing address.
For more information, see the following document:
The VRRP MIB RFC2787 this allows for RFC2787 support.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipapp/configuration/guide/ipapp_vrrp_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipapp/configuration/guide/ipapp_vrrs_xe.html
Enable firewall policy to be configured on a zone pair which consist of a zone and a default zone. Any interface without explicit zone membership belongs to default zone.
For more information, see the following document:
The following Cisco Unified Border Element (SP Edition) features were introduced in Cisco IOS XE Release 2.6.0:
•CUBE(SP Edition) CODEC Enhancements
•CUBE(SP Edition) Unsignaled Secure Media
•CUBE(SP Edition): DBE: Optional TMAN Bandwidth Parameter Policing
•CUBE(SP Edition): DBE: Return Local and Remote Descriptors in H.248 Reply
•CUBE(SP Edition): SIP:Contact Username Passthrough (non-IMS case)
•CUBE(SP Editon): SIP:Interoperability for SIP Authentication
•SBC End Point Switching
•SIP Non-SDP Body Filtering
•SIP: SIP SDP and Body Filtering
•Source Number Analysis
In addition Cisco IOS XE Release 2.6.0 introduces support for the following CUBE(SP Edition) IPv6 Support:
•SIP:DNS support for IPv6
•Media:IPv6-IPv6 (RTP)
•SIP:SIP Signaling IPv4 to IPv6 interworking
•SIP:SIP Signaling Over IPv6
•SIP:SIP Media IPv4 to IPv6 interworking
For information about these Cisco Unified Border Element (SP Edition) features, see the following documents:
Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/sbcu/2_xe/sbcu_2_xe_book.html
Cisco Unified Border Element (SP Edition) Command Reference: Unified Model
http://www.cisco.com/en/US/docs/ios/sbc/command/reference/sbcu_book.html
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.5.2.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.5.2.
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.5.1.
This section lists new and changed features in Cisco IOS XE Release 2.5.1. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE:
•VRF-Aware Local Area Mobility (LAM)
VRF-Awareness in LAM provides the ability to distinguish two destinations with the same IP address.
For more information, see the following document:
http://preview.cisco.com/en/US/docs/ios/ipmobility/command/reference/imo_01.html#wp1020438
The following Cisco Unified Border Element (SP Edition) features were introduced in Cisco IOS XE Release 2.5.1:
•CUBE(SP Editon): H.323:H.323 TCS Codecs Support
For information about these Cisco Unified Border Element (SP Edition) features, see the following documents:
Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/sbcu/2_xe/sbcu_2_xe_book.html
Cisco Unified Border Element (SP Edition) Command Reference: Unified Model
http://www.cisco.com/en/US/docs/ios/sbc/command/reference/sbcu_book.html
The following hardware features are supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.5.0:
•1-Port Clear Channel OC-12 ATM SPA (SPA-1XOC12-ATM-v2)
•New XFP/SFPs Supported with SPAs and the Built-In Gigabit Ethernet Interface
The 1-Port Clear Channel OC-12 ATM SPA is a single-height ATM SPA that can be installed into one SIP subslot. The OC-12 ATM SPA with small form-factor pluggable (SFP) optical transceiver modules provides SONET and SDH network connectivity with a per-port bandwidth of 622.08 Mbps.
For information about the SPAs supported on the Cisco ASR 1000 Series Routers, see the following documents:
Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide at the following location:
Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Software Configuration Guide at the following location:
The following transceiver modules are newly supported on the Cisco ASR 1000 Series Routers for the following SPAs:
•Cisco10GBASE-SR XFP transceiver module for MMF, 850-nm wavelength, dual LC connector (XFP-10G-MM-SR)—Supported with the 1-Port 10-Gigabit Ethernet SPA (SPA-1X10GE-L-V2) only on the Cisco ASR-1002, Cisco ASR-1004, and Cisco ASR-1006 routers.
•Cisco1000BASE-BX10 SFP module for single-strand SMF, 1490-nm TX/1310-nm RX wavelength (GLC-BX-D)—Supported with the following hardware:
–2-Port Gigabit Ethernet SPA (SPA-2X1GE-V2)
–5-Port Gigabit Ethernet SPA (SPA-5X1GE-V2)
–10-Port Gigabit Ethernet SPA (SPA-10X1GE-V2)
–Built-in Gigabit Ethernet interface on the Cisco ASR-1002 router
•Cisco 1000BASE-BX10 SFP module for single-strand SMF, 1310-nm TX/1490-nm RX wavelength (GLC-BX-U)—Supported with the following hardware:
–2-Port Gigabit Ethernet SPA (SPA-2X1GE-V2)
–5-Port Gigabit Ethernet SPA (SPA-5X1GE-V2)
–10-Port Gigabit Ethernet SPA (SPA-10X1GE-V2)
–Built-in Gigabit Ethernet interface on the Cisco ASR-1002 router
For more information, see the following publications:
•For information on optics module compatibility with SPAs on the Cisco ASR 1000 series routers, see the "Modular Optics Compatibility" section of the "SIP and SPA Overview" chapter in the Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide at:
•For more information about the built-in Gigabit Ethernet interface on the Cisco ASR-1002 routers and optics module compatibility, see the Cisco ASR 1000 Series Aggregation Services Router Hardware Installation Guide at:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
•For more information about a specific supported transceiver module and its installation and maintenance, find the corresponding documentation for the supported module at the Cisco Transceiver Modules site at:
http://www.cisco.com/en/US/products/hw/modules/ps5455/prod_installation_guides_list.html
This section lists new and changed features in Cisco IOS XE Release 2.5. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE Release 2.5:
•2547oDMVPN - Enabling Traffic Segmentation within DMVPN
•AAA - Improvements for Broadband IPv6
•BGP Multicast Inter-AS (IAS) VPN
•BGP VPLS Auto Discovery Support on Route Reflector
•Configurable Domain Name Prefix and Suffix Stripping
•DHCP - DHCPv6 Prefix Delegation RADIUS VSA
•DHCP Enhancements to Support IPv6 Broadband Deployments
•DMVPN Manageability Enhancements
•DMVPN: Dynamic tunnels between spokes behind NAT
•Dynamic Subscriber Bandwidth Selection
•Firewall - VRF-aware ALG support
•Flow Based Per Port Channel Load Balancing
•IEEE 802.3ad - Faster Link Switchover Time
•IPv6 Access Services: AAA Support for Cisco VSA IPv6 Attributes
•IPv6 Access Services: AAA Support for RFC 3162 IPv6 RADIUS Attributes
•IPv6 Access Services: Stateless DHCPv6
•ISG:AAA Wireless Enhancements
•ISG:Authentication:Radius Proxy WiMax Enhancements
•ISG:Instrumentation:DHCP Lease Query Support
•ISG:Policy Control:Differentiated Initial Policy Control
•ISG:Session: Creation: Interface IP Session: L2
•ISG:Session: Creation: Interface IP Session: L3
•ISG:Session:Multicast:Coexistance
•ISG:Session:Static Session Creation
•Layer 2 Local Switching - Same-Port Switching for Ethernet VLAN
•Layer 2 Local Switching: Ethernet to VLAN
•Link Aggregation Control Protocol (LACP) (802.3ad) for Gigabit Interfaces
•Local Template-Based ATM PVC Provisioning
•MPLS VPN Half Duplex VRF (HDVRF)
•MSDP MD5 password authentication
•Multicast VPN Extranet Support
•Multicast VPN Extranet VRF Select
•Multicast VPN Inter-AS Support
•Multicast-VPN: Multicast Support for MPLS VPN
•NAT - VRF aware NAT for MPLS/VPN
•NBAR PDLM supported in ASR1000 Release 5
•NHRP - CEF rewrite for DMVPN Phase 3 Networks
•PPP Enhancement for Broadband IPv6
•PPP Session Queueing on ATM VC
•QoS: QoS support for GRE/sVTI Tunnel
•QoS: Shape Average Percent CLI
•Service Advertisement Framework (SAF)
•Cisco Unified Border Element (Enterprise)
•Cisco Unified Border Element (SP Edition)
Cisco IOS XE Release 2.5 provides an enhancement that allows you to segment VPN traffic within a DMVPN tunnel.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/sec_secure_connectivity/configuration/guide/sec_DMVPN_xe.html
This feature is supported in Cisco IOS XE Release 2.5.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
You can enable ANCP support on an ATM interface by using the enable ancp command. This is one of the optional steps for configuring PVC.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/atm/configuration/guide/atm_cfg_atm_xe.html
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, in the absence of VP configuration. After creating the VCIs you can use the ping atm command to isolate connection problems.
ATM supports two types of interfaces: point-to-point and multipoint.
–Point-to-point subinterface—With point-to-point subinterfaces, each pair of routers has its own subnet. If you put the PVC on a point-to-point subinterface, the router assumes that there is only one point-to-point PVC configured on the subinterface. Therefore, any IP packets with a destination IP address in the same subnet are forwarded on this virtual circuit (VC). This is the simplest way to configure the mapping and is therefore the recommended method.
–- Multipoint networks—Multipoint networks have three or more routers in the same subnet. If you put the PVC in a point-to-multipoint subinterface or in the main interface (which is multipoint by default), you need to either configure a static mapping or enable inverse Address Resolution Protocol (ARP) for dynamic mapping.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/atm/configuration/guide/atm_cfg_atm_xe.html
This feature module describes how to configure QoS hierarchical queueing policy maps on sessions and ATM VCs in ATM Digital Subscriber Line Access Multiplexer (A-DSLAM) applications.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/ppp_ses_que_atm_vc_xe.html
The BGP Best External feature provides the capability of configuring the additional backup paths and advertises the best-external route which is the most preferred route among the routes received by a router from its eBGP peers. The best-external route can be used in case the primary PE fails or the primary PE link fails thereby reducing traffic loss and aiding in achieving faster PIC time.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_bgp/configuration/guide/irg_best_external_xe.html
The BGP Best External feature provides the capability of configuring the additional backup paths and advertises the best-external route which is the most preferred route among the routes received by a router from its eBGP peers. The best-external route can be used in case the primary PE fails or the primary PE link fails thereby reducing traffic loss and aiding in achieving faster PIC time.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_bgp/configuration/guide/irg_best_external_xe.html
The BGP PIC feature provides the ability to converge BGP routes within sub-seconds instead of multiple seconds and allows you to configure your BGP to minimize traffic loss and improve convergence when a link between the PE and CE router fails.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_bgp/configuration/guide/irg_best_external_xe.html
On the ASR1000, BGP Route Reflector was enhanced to be able to reflect BGP VPLS prefixes without having VPLS explicitly configured on the route reflector. The route reflector reflects the VPLS prefixes to other provider edge (PE) routers so that the PEs do not need to have a full mesh of BGP sessions.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute_bgp/configuration/guide/irg_int_features_xe.html
VPDN Configurable Domain Name Prefix and Suffix Stripping: This feature allows the NAS to be configured to strip prefixes, suffixes, or both from the full username. The reformatted username is then forwarded to the remote AAA server.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/vpdn/configuration/guide/config_aaa_for_vpdn_xe.html
DHCP - DHCPv6 Prefix Delegation RADIUS VSA - "When the user requests a prefix from the prefix delegator, typically the NAS, the prefix is allocated using DHCPv6"
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
This feature is supported in Cisco IOS XE Release 2.5.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-dhcp_xe.html
DMVPN session manageability was expanded with DMVPN specific commands for debugging, show output, session and counter control, and system log information.
For more information, see the following document:
The DMVPN: Dynamic Tunnels Between Spokes Behind a NAT Device feature allows Next Hop Resolution Protocol (NHRP) spoke-to-spoke tunnels to be built in Dynamic Multipoint Virtual Private Networks (DMVPNs), even if one or more spokes is behind a Network Address Translation (NAT) device.
For more information, see the following document:
This feature enables wholesale service providers to sell different classes of service to retail service providers by controlling bandwidth at the ATM virtual circuit (VC) level. ATM quality of service (QoS) parameters from the subscriber domain are applied to the ATM PVC on which a PPPoE or PPPoA session is established.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_con_sub_bdwth_xe.html
The EtherChannel Min-Links feature allows a port channel to be shut down when the number of active links falls below the minimum threshold.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/cether/configuration/guide/ce_lnkbndl_xe.html
VRF-aware ALG support allows ALG to extract the correct IP-address and VRF-id from cached memory when creating ALG tokens.
For more information, see the following document:
The Flow-Based Per Port-Channel Load Balancing feature allows different flows of traffic over a Gigabit EtherChannel (GEC) interface to be identified based on the packet header and then mapped to the different member links of the port channel. You can apply flow-based load balancing or VLAN-manual load balancing to specific port channels.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/lanswitch/configuration/guide/lsw_cfg_flwload_xe.html
The IEEE 802.3ad Faster Link Switchover Time feature provides a link failover time of 250 milliseconds or less and a maximum link failover time of 2 seconds. Also, port channels remain in the LINK_UP state to eliminate reconvergence by the Spanning-Tree Protocol.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/cether/configuration/guide/ce_lnkbndl_xe.html
The IEEE 802.3ad Link Aggregation Control Protocol (LACP) enables the bundling of physical interfaces on a physical device to achieve more bandwidth than is available using a single interface. The LAG MIB supports the management of interfaces and ports that are part of an LACP port channel and is accessed by a Simple Network Management Protocol (SNMP) manager application.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/cether/configuration/guide/ce_lacpmib_xe.html
Vendor-specific attributes (VSAs) were developed to support AAA for IPv6
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
The AAA attributes for IPv6 are compliant with RFC 3162 and require a RADIUS server capable of supporting RFC 3162.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
ADSL and dial deployment is available for interfaces with PPP encapsulation enabled, including PPPoA.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
ADSL and dial deployment is available for interfaces with PPP encapsulation enabled, including PPPoE.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
The stateless DHCPv6 feature allows DHCPv6 to be used for configuring a node with parameters that do not require a server to maintain any dynamic state for the node.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-dhcp_xe.html
The ISG: AAA Wireless Enhancements feature enhances ISG Radius proxy functionality to provide additional support for mobile wireless environments. It includes changes to RADIUS attribute 31 processing.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_radius_proxy_xe.html
The ISG:Accounting: Prepaid feature supports ISG prepaid billing and allows ISG to check a subscriber's available credit to determine whether to allow the subscriber access to a service and how long the access can last. ISG supports volume-based and time-based prepaid billing.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_radius_proxy_xe.html
The ISG:Authentication:Radius Proxy WiMax Enhancements feature enhances ISG Radius proxy to provide additional support for WiMax broadband environments.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_radius_proxy_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_acess_sub_sessns_xe.html
The ISG:Policy Control:Differentiated Initial Policy Control feature provides minimal or temporary network access to the subscribers when the RADIUS servers are down or cannot be accessed because of network issues.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_cntrl_policies_xe.html
The ISG:Session: Creation: Interface IP Session: L2 feature provides the ability to create Layer 2 IP Sessions for ISG for an entire interface or subinterface.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_acess_sub_sessns_xe.html
The ISG:Session: Creation: Interface IP Session: L3 feature provides the ability to create Layer 3 IP Sessions for ISG for an entire interface or subinterface.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_acess_sub_sessns_xe.html
The ISG Session Multicast Coexistence feature introduces the ability to host all the subscribers and services (data and multicast) on the same VLAN by enabling multicast and IP sessions to coexist on the same subinterface for Cisco 1000 series routers.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_acess_sub_sessns_xe.html
The ISG Static Session Creation feature enables administrator initiated static IP sessions.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_acess_sub_sessns_xe.html
This feature is supported in Cisco IOS XE Release 2.5.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ha/configuration/guide/ha-inserv_updg_xe.html
The Cisco IOS Broadband High Availability Stateful Switchover feature provides the capability for dual Route Processor systems to support stateful switchover of PPPoX sessions and allow applications and features to maintain state while system control and routing protocol execution is transferred between an active and a standby processor.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_ha_svc_sw_up_xe.html
Note The Layer 2 Local Switching - Same-Port Switching for Ethernet VLAN feature allows you to switch Layer 2 data between two interfaces on the same router, and in some cases to switch Layer 2 data between two circuits on the same interface port.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios-xml/ios/wan_lserv/configuration/xe-3s/wan-l2-lcl-swng-xe.html
Note The Layer 2 Local Switching: Ethernet to VLAN feature allows you to switch Layer 2 data between two interfaces on the same router, and in some cases to switch Layer 2 data between two circuits on the same interface port.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/wan/configuration/guide/wan_l2_lcl_swng_xe.html
The LACP (802.3ad) for Gigabit Interfaces feature bundles individual Gigabit Ethernet links into a single logical link that provides the aggregate bandwidth of up to four physical links.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/cether/configuration/guide/ce_lnkbndl_xe.html
The Local Template-Based ATM Provisioning feature enables ATM permanent virtual circuits (PVCs) to be provisioned automatically as needed from a local configuration. ATM PVC autoprovisioning can be configured on a PVC, an ATM PVC range, or a VC class. If a VC class configured with ATM PVC autoprovisioning is assigned to an interface, all the PVCs on that interface will be autoprovisioned; this configuration is sometimes referred to as an infinite range.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/atm/configuration/guide/atm_pvc_prov_xe.html
This feature ensures that VPN clients that connect to the same PE router at the edge of the MPLS VPN use the hub site to communicate.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_vpn_half_dup_vrf_xe.html
The MSDP MD5 password authentication feature is an enhancement to support MD5 signature protection on a TCP connection between two MSDP peers. This feature provides added security by protecting MSDP against the threat of spoofed TCP segments being introduced into the TCP connection stream.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipmulti/configuration/guide/imc_msdp_im_pim_sm_xe.html
The Multicast VPN Extranet Support feature enables service providers to distribute IP multicast content originated from one enterprise site to other enterprise sites. This feature enables service providers to offer the next generation of flexible extranet services, helping to enable business partnerships between different enterprise VPN customers
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipmulti/configuration/guide/imc_mc_vpn_extranet_xe.html
The Multicast VPN Extranet VRF Select feature provides the capability for RPF lookups to be performed to the same source address in different VRFs using the group address as the VRF selector. This feature enhances extranet MVPNs by enabling service providers to distribute content streams coming in from different MVPNs and redistributing them from there.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipmulti/configuration/guide/imc_mc_vpn_extranet_xe.html
The Multicast VPN Inter-AS support feature enables MDTs used for MVPNs to span multiple autonomous systems. Benefits include increased multicast coverage to customers that require multicast to span multiple service providers in an MPLS Layer 3 VPN service with the flexibility to support all options described in RFC 4364. Additionally, the Multicast VPN Inter-AS Support feature may be used to consolidate an existing MVPN service with another MVPN service, such as the case with a company merger or acquisition
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipmulti/configuration/guide/imc_cfg_mc_vpn_sup_xe.html
The Multicast VPN MIB feature introduces the capability for SNMP monitoring of an MVPN using the MVPN MIB (CISCO-MVPN-MIB).
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipmulti/configuration/guide/imc_vpn_mib_xe.html
The Multicast VPN feature provides the ability to support multicast over a Layer 3 Virtual Private Network (VPN). As enterprises extend the reach of their multicast applications, service providers can accommodate these enterprises over their Multiprotocol Label Switching (MPLS) core network. IP multicast is used to stream video, voice, and data to an MPLS VPN network core.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipmulti/configuration/guide/imc_cfg_mc_vpn_xe.html
Enables multiple Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) to be configured to work together on a single device. NAT can determine which MPLS VPN it receives IP traffic from even if the MPLS VPNs are all using the same IP addressing scheme. This enhancement enables multiple MPLS VPN customers to share services while ensuring that each MPLS VPN is completely separate from the other.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipaddr/configuration/guide/iadnat_mpls_vpns_xe.html
Enables NAT to support virtual routing and forwarding (VRF) for protocols that require an application level gateway (ALG), such as SIP, H.323, and SCCP/Skinny.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipaddr/configuration/guide/iadnat_applvlgw_xe.html
Network-Based Application Recognition (NBAR) is a classification engine that recognizes and classifies a wide variety of protocols and applications. When NBAR recognizes and classifies a protocol or application, the network can be configured to apply the appropriate quality of service (QoS) for that application or traffic with that protocol.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/clsfy_traffic_nbar_xe.html
Routers in a Dynamic Multipoint VPN (DMVPN) network can use the Next Hop Resolution Protocol (NHRP) to discover the addresses of other routers and networks behind those routers that are connected to a DMVPN nonbroadcast multiaccess (NBMA) network. NHRP provides a solution that alleviates NBMA network problems, such as hub failure, decreased reliability, and complex configurations.
The Cisco NHRP MIB feature introduces support for the NHRP MIB, which helps to manage and monitor Next Hop Resolution.
For more information, see the following document:
This feature is supported in Cisco IOS XE Release 2.5.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ha/configuration/guide/ha-nonstp_fwdg_xe.html
http://www.cisco.com/en/US/docs/ios/ios_xe/ha/configuration/guide/ha-stfl_swovr_xe.html
This feature is supported in Cisco IOS XE Release 2.5.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
PPP Session Queuing on ATM Virtual Circuits (VCs) enables you to shape and queue PPP over Ethernet over ATM (PPPoEoA) sessions to a user specified rate.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/ppp_ses_que_atm_vc_xe.html
PPP over Ethernet (PPPoE) profiles contain configuration information for a group of PPPoE sessions. Multiple PPPoE profiles can be defined for a device, allowing different virtual templates and other PPPoE configuration parameters to be assigned to different PPP interfaces, VLANs, and ATM PVCs that are used in supporting broadband access aggregation of PPPoE sessions.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_pppoe_baa_xe.html
This feature module describes the PPP over Ethernet (PPPoE) on ATM feature. The PPPoE on ATM feature provides the ability to connect a network of hosts over a simple bridging-access device to a remote access concentrator.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_ppoe_atm_xe.html
The PPPoE Session Count Management Information Base feature provides the ability to use Simple Network Management Protocol (SNMP) to monitor in real time the number of PPP over Ethernet (PPPoE) sessions configured on permanent virtual circuits (PVCs) and on a router. This MIB also supports two SNMP traps that generate notification messages when a PPPoE session-count threshold is reached on any PVC or on the router.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_mon_pppoe_snmp_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/qos/command/reference/qos_a1.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/qos/command/reference/qos_a1.html
As the variety and number of network services grows, providing timely and reliable awareness of these services starts to play a more significant role in increasing productivity and efficiency. As networks grow so too do the services offered by the devices on these networks. Protocols responsible for the service advertisement need to scale to handle this increased load. This feature, Service Advertisement Framework (SAF) provides that function.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/saf/configuration/guide/XE_saf_cg.html
The Sharing IPsec with Tunnel Protection feature allows an IP Security (IPsec) security association database (SADB) to be shared between two or more Generic Routing Encapsulation (GRE) tunnel interfaces, when tunnel protection is used.
For more information, see the following document:
The SSO - LACP feature supports stateful switchover (SSO), in service software upgrade (ISSU), Cisco nonstop forwarding (NSF),
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/cether/configuration/guide/ce_lnkbndl_xe.html
This feature is supported in Cisco IOS XE Release 2.5
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-adsl_dial_xe.html
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios-xml/ios/bbdsl/configuration/xe-3s/bba-ha-stfl-swovr-xe.html
VRF Aware Cisco IOS Firewall applies Cisco IOS Firewall functionality to VRF interfaces when the firewall is configured on an SP or large enterprise edge router. SPs can provide managed services to small and medium business markets.
For more information, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/sec_data_plane/configuration/guide/sec_vrf_aware_fwall_xe.html
The Cisco Unified Border Element (Enterprise) on the ASR1000 brings a scalable Cisco UBE (Enterprise) options for enterprise customers. Running as a process on the ASR1000 and utilizing the high speed RTP packet processing path, The primary customers are ones who are consolidating TDM trunks. This release focuses on the initial set of functionality completed for SIP Trunks for PSTN access from Service Providers.
The following Cisco Unified Border (Enterprise) features were introduced in Cisco IOS XE Release 2.5.0:
•Configurable SIP Parameter Modification
•DTMF Events Through SIP Signaling
•Enhanced SIP REFER
•H.323 to SIP Supplementary Feature Interworking for Session Border Controller (SBC)
•iLBC Support for SIP and H.323
•IP-IP Gateway for H323 Call Manager to H323 Service Provider Connectivity
•IP-to-IP Gateway: SIP-SIP Basic Functionality
•SIP - Ability to Send a SIP Registration Message on a Border Element
•SIP - Configurable Hostname in Locally Generated SIP Headers
•SIP - Core SIP Technology Enhancements
•SIP - DNS SRV RFC2782 Compliance
•SIP - Enhanced 180 Provisional Response Handling
•SIP - Gateway Support for the Bind Command
•SIP - INFO Method for DTMF Tone Generation
•SIP - Session Initiation Protocol for VoIP
•SIP - Session Timer Support
•SIP - SIP Basic Feature Functionality for Session Border Controller (SBC)
•SIP - SIP Extended Feature Functionality for Session Border Controller (SBC)
•SIP - SIP GW Session Timer Support
•SIP - Stack Support of TLS
•SIP - Support for SESSION REFRESH with reINVITEs
•SIP and TEL URL Support
•SIP to SIP Supplementary Services for Session Border Controller (SBC)
•SIP:SIP Support for Options
•Support for negotiation of an audio codec from a list of codecs on each leg of a SIP-SIP call on the Cisco Unified Border Element
•Transparent Tunneling of QSIG and Q.931 over SIP-SIP Cisco Unified Border Element
For information about these Cisco Unified Border Element (Enterprise) features, see the following documents:
http://www.cisco.com/en/US/docs/ios-xml/ios/voice/config_library/xe-3s/cube-xe-3s-library.html
The following Cisco Unified Border Element (SP Edition) features were introduced in Cisco IOS XE Release 2.5.0:
•Call duration monitoring
•CDR:Support for CDR Media information
•CDR:Granular Timestamp Support
•H323:H.245 address in Call PROC
•H323:H.323 Registration with Multiple Gatekeepers
•H323:H.323 Slow start to H.323 Fast start Interop
•H323:H.323 Video codec support (H.261, H.263, H.264)
•H.323:In call facility pass through
•H323:Interop with Cisco H.323 gatekeeper
•H323:ITU H.323v4: Packet-Based Multimedia Communications System
•H323:Multiple TCP for H.323
•IMS:Support for Authentication via AKA
•Interop:Support interworking like CCM-SBC-CME topology
•Interworking:CCM-H.323 Slow-start to Fast-start
•Interworking:H.323 - SIP Cause code Mapping
•Interworking:H.323 and SIP interop services
•Interworking:H.323 and SIP Message Translation
•Interworking:H.323 Fast Start Call to SIP call
•Interworking:H.323 Slow Start Calls to SIP calls
•Interworking:H.323 to SIP Support for Emergency calls
•Interworking:H.323/SIP Call Routing
•Interworking:H.323-H.323 Interworking-basic calls
•Interworking:SIP to H.323 Fast Start
•Interworking:T.38 with H.323-H.323 and SIP-H.323.
•Media:Fax/Modem Upspeed Support
•Media:SBC will support Pass through Codec Types
•Media:Transcoding:For external media-server SBC shall work with MGX 8880 Media server.
•Media:Transcoding:SBC shall support external Media Server
•Signaling congestion handling enhancement
•SIP: Ability to Insert Firewall Parameter in SIP Contact Header
•SIP:Ability to adjust "b="""command in SIP INVITE"
•SIP:Call forking
•SIP:Call Park
•SIP:Contact Username Passthrough (non-IMS case)
•SIP:Customizable Late to Early Offer
•SIP:Find Me
•SIP:Instant Messaging and SIMPLE
•SIP:Interoperability for INVITE authentication
•SIP:IP - FQDN URI translation
•SIP:Regular Expression Based Routing
•SIP:SDP media line removal
•SIP:SIP - Specific Event Notification
•SIP:SIP Header Manipulation with Regular Expression/Privacy
•SIP:SIP trunk-group ID routing
•SIP:Support for "Supported: Path" under REGISTER request
•SIP:Support for IP Realm
•SIP:Support for P-KT-UE-IP support
•SIP:Support for PRACK/100rel interworking
•SIP:Support for P-visited-network-ID
•SIP:Support for Softswitch Registration Timer Shielding
•Support for P-called Party Identifier, P-Associated URI (RFC3445)
•Support for Subscriber Policy
For information about these Cisco Unified Border Element (SP Edition) features, see the following documents:
Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/sbcu/2_xe/sbcu_2_xe_book.html
Cisco Unified Border Element (SP Edition) Command Reference: Unified Model
http://www.cisco.com/en/US/docs/ios/sbc/command/reference/sbcu_book.html
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.4.4.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.4.4.
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.4.3.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.4.3.
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.4.2t.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.4.2t.
The following hardware features are supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.4.2:
The Cisco +24V DC power supply supports the Cisco ASR 1002 Router with Cisco IOS XE 2.4.2 and later. The Cisco ASR 1002 Router with the new +24V DC power supply is targeted in markets where 24V DC power is required, including, but not limited to, wireless/mobility providers cell-sites.
For information about the Cisco ASR 1002 Router and +24V DC power supply, see the following documents:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
and Cisco ASR 1002 Quick Start Guide
http://www.cisco.com/en/US/docs/routers/asr1000/quick/start/guide/asr1_qs2.html
This section lists new and changed features in Cisco IOS XE Release 2.4.2. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE Release 2.4.2:
Provides an optional keyword (forced) to the existing command clear ip nat translations that enable users to clear the NAT table of active dynamic half entries that have existing children translations.
For more information on NAT -Forced Clear of Dynamic Half Entries, see the following document:
https://www.cisco.com/en/US/docs/ios/ios_xe/ipaddr/configuration/guide/iad_monmain_nat_xe.html
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.4.1.
This section lists new and changed features in Cisco IOS XE Release 2.4.1. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE Release 2.4.1.
•IPv6 IPSec Static Virtual Interface
•IPSec QoS Group-Based LLQ QoS
•ALG Support for SIP T.38 Fax Relay over IP
Static Virtual Tunnel Interface (SVTI) configurations can be used for site-to-site connectivity in which a tunnel provides always-on access between two sites. The advantage of using SVTIs as opposed to map configurations is that users can enable dynamic routing protocols on the tunnel interface without the extra 24 bytes required for GRE headers, thus reducing the bandwidth for sending encrypted data.
For more information on SVTIs, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ipsec_xe.html
A limitation exists when IPSec and QoS are configured on an interface. IPSec uses the egress QoS policy to determine if a packet is a high priority packet before it enqueues it in a low latency queue (LLQ) of the crypto processor. For tunnel interfaces when the QoS policy is applied to the egress physical interface, Tunnel Protection is applied on the tunnel interface, and IPSec cannot determine if the packet is a high priority packet. In this scenario, high priority packets are queued to the default queue—increasing latency and traffic loss during oversubscription.
Starting with Cisco IOS XE Release 2.4.1, QoS group-based LLQ for IPSec provides LLQ functionality before crypto for the limitation described earlier. The idea is to use QoS groups to identify high priority traffic in the IPSec module. Packets are marked with a QoS group at the ingress interface. The user designates certain QoS groups to be used as high priority before crypto.
A new IOS XE command allows the user to configure certain QoS groups as high priority for IPSec:
[no] platform ipsec llq qos-group group_num
This command specifies that packets with QoS group group_num (allowed range 1 to 99) are to be treated as high priority packets before crypto and, therefore, are queued into a LLQ before reaching the crypto processor.
The SIP Application Layer Gateway has been enhanced to provide NAT and Firewall ALG support for T.38 Fax Relay over IP.
Intermediate System (IS-IS) has been enhanced to provide Internet Protocol version 6 (IPv6).
The following new hardware features are supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.4.0:
The Cisco ASR 1002-Fixed (Cisco ASR 1002-F) Router is the smallest of the Cisco ASR 1000 Series Aggregation Services Routers and supports all the general-purpose routing and security features of the Cisco ASR 1002 Router.
The Cisco ASR 1002-F Router uses the same internal control and data-plane architecture as the Cisco ASR 1002 router with the following variations:
•Has all integrated components: an integrated route processor (Cisco ASR1000-RP1), an integrated embedded services processor (2.5-Gbps Cisco ASR 1000 Series ESP), and an integrated 4xGE SPA interface (Cisco ASR1000-SIP10)
•Supports 2.5 GB of system bandwidth
•Is supported only with Cisco IOS XE Release 2.4.0 and later releases
For information about the Cisco ASR 1002-F Router, see the following documents:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
Cisco ASR 1002-F Quick Start Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/quick/start/guide/asr1_qs2F.html
Cisco IOS XE Release 2.4.0 introduces support for the following new shared port adapters (SPAs):
POS SPAs
•8-Port OC-3 POS SPA (SPA-8XOC3-POS)
•2-Port, 4-Port, and 8-Port OC-12 POS SPAs (SPA-2XOC12-POS, SPA-4XOC12-POS, and SPA-8X0C-12-POS)
•1-Port OC-48 POS SPA (SPA-1XOC48POS/RPR)
•1-Port OC-192 POS SPA (SPA-OC192POS-XFP)
Services SPA
•Cisco WebEx Node for ASR 1000 Series (SPA-WMA-K9)
The Cisco WebEx Node for ASR 1000 Series is a full-height SPA designed to run an application which is part of the WebEx MediaTone network management application. The Cisco WebEx Node for ASR 1000 Series improves the functionality of WebEx meeting services by adding the meeting servers into the SPA itself. This technology provides the following advantages:
–Improves performance for users inside the company firewall.
–Reduces the bandwidth going out of company firewall (to the WebEx MediaTone network).
–Provides better security by reducing traffic outside the company.
By moving the switching components of the WebEx Collaboration Cloud into the Cisco WebEx Node for ASR 1000 Series, the WebEx clients in the enterprise network need only connect to the Cisco WebEx Node for ASR 1000 Series. This reduces the traffic between the enterprise network and the WebEx MediaTone network, greatly reducing the customer's Internet bandwidth requirements.
Each Cisco WebEx Node for ASR 1000 Series can be configured to perform either web conferencing or voice and video conferencing, but not both features at the same time. Each Cisco WebEx Node for ASR 1000 Series uses the same software package that includes both features; the conferencing feature that actually runs on each SPA is determined by the WebEx Service Plan the customer has purchased. The WebEx MediaTone network retains the Cisco WebEx Node for ASR 1000 Series configuration files that the SPA retrieves each time the SPA boots. Multiple Cisco WebEx Nodes for ASR 1000 Series can be installed on the same Cisco ASR 1000 Series Router chassis to increase the conferencing performance or to provide conferencing coverage for both web and voice and video sessions.
For information about the SPAs supported on the Cisco ASR 1000 Series Routers, see the following documents:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide at the following location:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Software Configuration Guide at the following location:
This section lists new and changed features in Cisco IOS XE Release 2.4.0. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE Release 2.4.0.
•802.1P CoS Bit Set for PPP and PPPoE Control Frames
•ANCP (Access Node Control Protocol)
•Any Transport over MPLS (AToM): Ethernet over MPLS (EoMPLS)
•Any Transport over MPLS (AToM): Ethernet over MPLS: Port Mode (EoMPLS)
•Any Transport over MPLS (AToM): Remote Ethernet Port Shutdown
•Any Transport over MPLS— Ethernet over MPLS Enhancements: Fast Reroute
•Asynchronous Rotary Line Queuing
•Byte-Based Weighted Random Early Detection
•Cache Control Enhancements for Certification Revocation Lists
•Certificate—Complete Chain Validation
•Cisco Unified Border Element (SP Edition)
•Class-Based QoS MIB (CBQoSMIB) Enhancements
•CoA—Multi-Service Activation/Deactivation in Single mMessage
•Connect-info RADIUS Attribute 77—Configurable ASCII String
•Enabling ISG to Interact with External Policy Servers
•Etherchannel Flow Based Limited 1:1 Redundancy
•Firewall—SIP ALG—Extended Methods
•Firewall—SIP ALG—Extended Methods
•H.323 RAS Support in IOS Firewall
•IEEE 802.1Q Tunneling (QinQ) for AToMLawful Intercept
•IEEE 802.3ad Link Aggregation (LACP)
•Integrated Session Border Controller
•Interactive OAM and Scaling Improvements
•IPv6 Multicast: Bootstrap Router (BSR)
•IPv6 Multicast: IPv6 BSR—Ability to Configure RP Mapping
•IPv6 Multicast: IPv6 BSR Bidirectional Support
•IPv6 Multicast: PIM Sparse Mode (PIM-SM)
•IPv6 Multicast: Routable Address Hello Option
•ISG: Accounting: Per-Service Accounting
•ISG: Policy Control: Policy Server: Multi-Service Activation in access-accept Message
•ISG: Policy Control: Policy Server: RADIUS-Based Policing
•L2TP Forwarding of PPPoE Tag Information
•L2VPN Interworking—Ethernet to VLAN Interworking
•L2VPN Pseudowire Redundancy: Multiple Backup Pseudowires
•Layer 2 VPN (L2 VPN): Syslog, SNMP Trap, and show Command Enhancements for AToM and L2TPv3
•MCP GEC with QoS on memberlink
•Modified LNS Dead-Cache Handling
•MQC—Traffic Shaping Overhead Accounting for ATM
•NAT—NetMeeting Directory (LDAP) ALG Support
•NSF/SSO—Ethernet to Ethernet VLAN Interworking
•OCSP—Server Certification from Alternate Hierarchy
•Parameterization for ACL and Layer 4 Redirect
•Per Subinterface MTU for Ethernet over MPLS (EoMPLS)
•PKI—CLI to Control Certificate Revocation List (CRL) Cache
•PPPoE VLAN Session Throttling
•Pseudowire Emulation Edge-to-Edge MIBs for Ethernet, Frame Relay, and ATM Services
•QoS: CBQoSMIB Index Enhancements
•RADIUS-Based Lawful Intercept
•RADIUS-Based Policing Attribute Modifications
•RADIUS—CLI to Prevent Sending of Access Request with Blank Username
•RSA 4096-Bit Key Generation in Software Crypto Engine Support
•VPN Routing Forwarding (VRF) Framed Route (Pool) Assignment via PPP
•VRF Aware LI (Lawful Intercept)
Intermediate System-to-Intermediate System (IS-IS) has been enhanced to support Internet Protocol version 6 (IPv6). For more information on implementing IS-IS support, see the Cisco IOS XE IPv6 Configuration Guide, Release 2 at the following URL:
The 3 Level Egress QoS Policy feature allows 3 level hierarchical QoS policies to be applied as an egress service per physical interface or per VLAN (GE) or per subinterface (FR or serial).
At the top level, only class-default with shaping can be configured.
At the medium level, user defined classes can be configured where for each user defined class following can be applied:
•Bandwidth Remaining (BR): either as Bandwidth Remaining Ratio (BRR) or Bandwidth Remaining Percentage (BRP) or
• shaping or
•priority (conditional or unconditional policer)
All of the three items listed above can be configured concurrently with WRED.
At the bottom level, user defined classes can be configured where for each user defined class either policing or marking can be applied.
The 802.1P CoS Bit Set for PPP and PPPoE Control Frames feature provides the ability to set user priority bits in the IEEE 802.1Q tagged frame to allow traffic prioritization.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_cos_ppp_pppoe_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_cfg_accountg.html
The Template ACL feature groups ACLs with many common access control elements (ACEs) into a single ACL that saves system resources.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/sec_data_plane/configuration/guide/sec_tmplacl.html
The Access Node Control Protocol feature enhances communication between Digital Subscriber Line Access Multiplexers (DSLAMs) and a broadband remote access server (BRAS), enabling the exchange of events, actions, and information requests between the multiplexer end and the server end. As a result, either end can implement appropriate actions.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ancp/configuration/guide/ancp_xe.html
The ANCP Phase 2.5 feature allows multiple services to be activated or deactivated by a single Change of Authorization (CoA) message sent from the policy server.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ancp/configuration/guide/ancp_msad_coa_xe.html
The Any Transport over MPLS (AToM): Ethernet over MPLS (EoMPLS) feature allows you to transport Layer 2 Ethernet VLAN packets from various sources over an MPLS backbone. Ethernet over MPLS extends the usability of the MPLS backbone by enabling it to offer Layer 2 services in addition to already existing Layer 3 services.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_any_transport_xe.html
Ethernet over MPLS (EoMPLS) is the transport of Ethernet frames across an MPLS core. It transports all frames received on a particular Ethernet or virtual LAN (VLAN) segment, regardless of the destination Media Access Control (MAC) information.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_any_transport_xe.html
The Any Transport over MPLS (AToM): Remote Ethernet Port Shutdown feature allows a service provider edge (PE) router on the local end of an Ethernet over MPLS (EoMPLS) pseudowire to detect a remote link failure and cause the shutdown of the Ethernet port on the local customer edge (CE) router. Because the Ethernet port on the local CE router is shut down, the router does not lose data by continuously sending traffic to the failed remote link.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_any_transport_xe.html
The Any Transport over MPLS— Ethernet over MPLS Enhancements: Fast Reroute feature allows AToM to use MPLS traffic engineering (TE) tunnels with fast reroute (FRR) support. This feature enhances FRR functionality for Ethernet over MPLS (EoMPLS).
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_any_transport_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/dial/configuration/guide/dia_asyn_que_role.html
The Byte-Based Weighted Random Early Detection feature extends the functionality of WRED. In previous releases, you specified the WRED actions based on the number of packets. With the Byte-Based WRED, you can specify WRED actions based on the number of bytes.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/fsbyte_xe.html
For information about this feature, see the following document:
For information about this feature, see the following document:
The Cisco IOS SHA2 Support feature allows the user to specify a cryptographic hash function for Cisco IOS certificate servers and clients. The cryptographic hash functions that can be specified are Message-Digest algorithm 5 (MD5), Secure Hash Algorithm -- SHA-1, SHA-256, SHA-384, or SHA-512.
The following commands were introduced by this feature: hash (ca-trustpoint) and hash (cs-server). The hash (ca-trustpoint) command sets the hash function for the signature that the Cisco IOS client uses to sign its self-signed certificates. The hash (cs-server) command sets the hash function for the signature that the Cisco IOS certificate authority (CA) uses to sign all of the certificates issued by the server.
Cisco Unified Border Element (SP Edition) was formerly known as Integrated Session Border Controller.
With Cisco IOS XE Release 2.4.0, Cisco Unified Border Element (SP Edition) can operate in two modes or deployment models:
•Unified—In the unified model, both the SBE and DBE logical entities co-exist on the same network element. In this model, the signaling entity controls the media local to the router.
•Distributed—In the distributed model, the SBE and the DBE entities reside on different network elements. Logically, each of the SBE entities controls multiple DBE elements, and each DBE can be controlled by multiple SBE entities.
Note For Cisco IOS XE Release 2.3 and earlier releases of the Integrated Session Border Controller, only DBEs in the distributed model are supported.
In addition to introducing support for the SBC unified model, Cisco IOS XE Release 2.4.0 introduces support for the following Session Border Controller (SBC) features:
•AAA: End Point Authentication
•CAC: Bypass Admission Control for Emergency Calls
•CAC: CAC Enforcement Notification
•CAC: Configurable Rate Limiting
•CAC: DBE Shall Support DSCP Settings
•CAC: Policing and Marking Under SBE Control
•CAC: Policing: Number Analysis: Depending on Destination Adjacency
•CAC: Policing: Per Session Policing
•CAC: Policing: SBC Shall Support Whitelisting and Blacklisting Profiles Based on Request for Methods
•CAC: Policing: BC Shall Support Policy Based Session Routing
•CAC: Priority Handling of Traffic During an Attack or When System's Resources Are Overloaded
•CAC: SBE Shall Support Various CAC Mechanisms
•CDR: 24 hours CDR Buffering
•CDR: Real Time CDRs Can Be Extracted Upon Completion of a Session
•CDR: Send CDR to Radius Server
•Config: ALARM/Statistics
•Config: All Timer Values Should Be Configurable with Default Values
•Config: DBE Shall Provide QoS Statistics to SBE in Realtime upon Call Completion
•Config: DBE Shall Support to Collect Statistics of the Session
•Config: Display Session States in Real-time
•Config: Load Balancing
•Config: Required Debug Commands
•Config: SBE/DBE CLI Consistency
•Config: SBE Shall Support the Ability to Specify QoS for the Session Based QoS Categories
•Config: Shut/No-Shut of SBE/DBE/SBC
•Delta Renegotiation
•DoS: DoS (Denial of Service)
•DoS: Guard Against DoS Attack at Signaling Level
•DoS: Monitoring and Blacklisting Signaling/Media Traffic for a DoS Attack
•DoS: Signaling and Control Packets
•DoS: Media Pinhole Provides an Alert for Packets with Unknown Source Address
•HA: 1:1 Redundancy Support
•HA: 2 Seconds Until New Sessions Can Be Established Following Failover
•HA: Active Session Preservation Across Failover
•HA: Media Path Interruption Should Be Less Than 1 Second During Failover
•IMS: Support for P-CSCF Subscription to Subscriber Registration State
•Interop: Interop with CCM and SIP IP Phones
•Interop: Interop with Cisco SIP Proxy Servers
•Interop: Interop with Telepresence System
•Media: DTMF Interworking Support
•Media: DTMF Support for SIP-Notify
•Media: Fax/Modem Passthrough Support
•Media: Inter-VPN Media Relay Bypass
•Media: Media Packet Updates
•Media: RTCP Processing
•Media: Support DTMF Processing
•Media: Support for RFC 3550 (RTP)
•Media: Support for RFC 3551
•Media: Support for Video Codecs—H.263 and H.264
•Media: Support Media Relay
•Media: VPN Awareness and Translation
•MIB: Support SNMP Call Stats Requirements
•MIB: Support SNMP TRAPS Requirements
•NAPT: NAPT Traversal
•NAT: NAT Traversal
•Option to Use CODEC Instead of Bandwidth-Field for Media Bandwidth Allocation
•Performance: Jitter Measurement
•Performance: Latency Measurement
•QoS: DSCP, Pre/TOS, and MPLS EXO\P Marking for Media, Signaling and Control Traffic
•Radius: Configurable Radius Authentication/Accounting Server Port
•Radius: Support Multiple Radius Servers
•Security: Private Extensions to the SIP for Asserted Identity within Trusted Networks
•Security: Short Term Requirements for Network Asserted Identity
•Security: Support DTLS for SIP Signaling
•Security: Support for SRTP
•Security: Support Multi-VFF Support for SBC
•Security: Support TLS-TLS and TLS-nonTLS Call Support
•Security: TLS Encrypted Signaling Across SP-SP Border
•Security: Transport=TLS parameter in Record Route Headers
•SIP: 3xx Support
•SIP: Allow Fast Register and Softswitch Shielding to Be Configured Independently
•SIP: BYE Storm Pacing
•SIP: Call Forwarding—Busy
•SIP: Call Forwarding—No Answer
•SIP: Call Forwarding—Unconditional
•SIP: Call Hold
•SIP: Call Hold Interworking
•SIP: Call Hold with MOH
•SIP: Call Routing Enhancement
•SIP: Caller-ID and Calling Name Delivery
•SIP: Click To Dial
•SIP: Codec AAC-LD Support
•SIP: Consultation Hold
•SIP: Delayed Media to Early Media Support
•SIP: Delegated Registration
•SIP: Dynamic Route Selection
•SIP: HTTP Digest Authentication
•SIP: Min-SE Support
•SIP: Music On Hold (MOH)
•SIP: MWI (Message Waiting Indicator)
•SIP: Reason Header
•SIP: RFC 3262 PRACK (Provisional Response)
•SIP: RFC 3264 An Offer/Answer Model with the SDP
•SIP: RFC 3892 Referred-By Mechanism
•SIP: RFC2976 SIP INFO method
•SIP: RFC3261
•SIP: session-expire Support
•SIP: SIP Aggregation Registration
•SIP: SIP Header and Value Manipulation
•SIP: SIP Registration Forwarding
•SIP: SIP Session Refreshment with re-INVITE
•SIP: SIP to Tel URI
•SIP: SRTP S-Description Passthrough
•SIP: Support for VPN DNS Resolution
•SIP: Support 100rel in Supported Header
•SIP: Support Fast Registration
•SIP: Support for Diversion Header
•SIP: Support for SIP Date Header
•SIP: Support for SIP JOIN Header
•SIP: Support for SIP Profile for Message Normalization
•SIP: Support TCP/UDP and Interoperability
•SIP: Support Tel URI
•SIP: timer Support
•SIP: Transfer—Attended
•SIP: Transfer—Unattended
•SIP: Transfer—Instant
•SIP: user=phone Parameter
•SIP: Video Support with E.164 and SIP URI
•Support Renegotiated Call Over NAT
•T.38 Passthrough
•Topology-Hiding: Infrastructure and Topology Hiding
•TP Support for Secure Media
•VPN Awareness and Interconnect
For information about these SBC features, see the following documents:
Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/sbcu/2_xe/sbcu_2_xe_book.html
Note Because the Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model uses a task-oriented approach to SBC features, each individual feature is not necessarily identified by feature name within the configuration guide.
Cisco Unified Border Element (SP Edition) Command Reference: Unified Model
http://www.cisco.com/en/US/docs/ios/sbc/command/reference/sbcu_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/cbqos_mib_xe.html
The CoA—Multi-Service Activation/Deactivation in Single mMessage feature allows multiple services to be activated or deactivated by a single Change of Authorization (CoA) message sent from the policy server.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ancp/configuration/guide/ancp_msad_coa_xe.html
The Connect-Info RADIUS Attribute 77 feature enables the network access server (NAS) to report Connect-Info (attribute 77) in RADIUS accounting "start" and "stop" records that are sent to the RADIUS client (dial-in modem). These "start" and "stop" records allow the transmit and receive connection speeds, modulation, and compression to be compared in order to analyze a user session over a dial-in modem where speeds are often different at the end of the connection (after negotiation).
For information about this feature, see the following document:
The Dynamic Host Configuration Protocol (DHCP) Server RADIUS Proxy feature is a RADIUS-based address assignment mechanism in which a DHCP server authorizes remote clients and allocates addresses based on replies from a RADIUS server.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipaddr/configuration/guide/iad_dhcp_rad_proxy_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/en_isg_ext_plcy_svrs_xe.html
The EtherChannel Flow-Based Limited 1:1 Redundancy feature provides a way to configure load balancing at the port-channel level based on different flows of traffic. You can identify different flows of traffic based on key fields in the data packet and balance the traffic load according to those traffic flows. To use EtherChannel flow-based limited 1:1 redundancy, you configure an EtherChannel with two ports (one active and one standby). If the active link goes down, the EtherChannel stays up and the system performs fast switchover to the hot-standby link. When the failed link becomes operational again, the EtherChannel performs another fast switchover to revert to the original active link.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/lanswitch/configuration/guide/lsw_cfg_flwbal.html
The Ethernet Overhead Accounting feature enables the router to account for downstream Ethernet frame headers when applying shaping to packets.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/eth_overhead_acctng_xe.html
The Firewall—SIP ALG—Extended Methods feature provides voice security enhancements within the Firewall feature set in Cisco IOS XE software on the Cisco ASR 1000 series routers.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/sec_data_plane/configuration/guide/sec_fw_sip_alg_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/sec_data_plane/configuration/guide/sec_h323ras_firewall.html
The IEEE 802.1Q Tunneling (QinQ) for AToM feature allows you to configure IEEE 802.1Q Tunneling (QinQ) for AToM. It also permits the rewriting of QinQ tags for Multiple Protocol Label Switching (MPLS) layer 2 VPNs (L2VPNs).
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_qnq_tunneling_atom_xe.html
The IEEE 802.3ad Link Aggregation (LACP) feature provides a method for aggregating multiple Ethernet links into a single logical channel based on the IEEE 802.3ad standard. This feature helps improve the cost effectiveness of a device by increasing cumulative bandwidth without necessarily requiring hardware upgrades.
For information about this feature, see the Configuring IEEE 802.3ad Link Bundling document:
http://www.cisco.com/en/US/docs/ios/ios_xe/cether/configuration/guide/ce_lnkbndl_xe.html
The product formerly known as Integrated Session Border Controller is now known as the Cisco Unified Border Element (SP Edition). For information about this feature, see Cisco Unified Border Element (SP Edition).
The Interactive OAM and Scaling Improvements feature adds on-demand ping capability to access node control protocol (ANCP) for operations and troubleshooting.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ancp/configuration/guide/ancp_xe.html
For information about this feature, see the following documents:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html
http://www.cisco.com/en/US/docs/ios/ios_xe/interface/configuration/guide/ir_impl_tun_xe.html
For information about this feature, see the following document:
If an RP becomes unreachable, the IPv6 Multicast: Bootstrap Router (BSR) feature allows the RP to be detected and the mapping tables modified so that the unreachable RP is no longer used, and the new tables will be rapidly distributed throughout the domain.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html
TheIPv6 Multicast: IPv6 BSR—Ability to Configure RP Mapping feature allows IPv6 multicast routers to be statically configured to announce scope-to-RP mappings directly from the BSR instead of learning them from candidate-RP messages.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html
The IPv6 Multicast: IPv6 BSR Bidirectional Support feature allows bidirectional RPs to be advertised in C-RP messages and bidirectional ranges in the BSM.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html
TheIPv6 Multicast: PIM Sparse Mode (PIM-SM) feature uses unicast routing to provide reverse-path information for multicast tree building. PIM-SM is used in a multicast network when relatively few routers are involved in each multicast and these routers do not forward multicast packets for a group, unless there is an explicit request for the traffic.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html
The IPv6 Multicast: Routable Address Hello Option feature adds a PIM hello message option that includes all the addresses on the interface on which the PIM hello message is advertised.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html
The Intelligent Services Gateway (ISG) Per-Service Accounting feature provides the means to bill for account or service usage. ISG accounting uses the RADIUS protocol to facilitate interaction between ISG and an external RADIUS-based authentication, authorization, and accounting (AAA) or mediation server.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/cfg_isg_acctng_xe.html
The ISG: Policy Control: Policy Server: Multi-Service Activation in access-accept Message feature allows multiple services to be included in a single RADIUS access-accept message.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ancp/configuration/guide/ancp_msa_acc_xe.html
The RADIUS-Based Policing feature extends Intelligent Services Gateway (ISG) functionality to allow the use of a RADIUS server to provide subscriber policy information.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_rabapol_xe.html
The L2TP Forwarding of PPPoE Tag Information feature allows you to transfer DSL line information from the L2TP Access Concentrator (LAC) to the L2TP Network Server (LNS). Using this feature, you can also override the nas-port-id and/or calling-station-id VSAs on the LNS with the Circuit-ID and Remote-ID VSA respectively.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/vpdn/configuration/guide/config_aaa_for_vpdn_xe.html
The L2VPN Interworking—Ethernet to VLAN Interworking feature allows disparate attachment circuits to be connected. An interworking function facilitates the translation between the different Layer 2 encapsulations.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_l2vpn_intrntwkg_xe.html
The L2VPN Pseudowire Redundancy: Multiple Backup Pseudowires feature allows you to configure up to three backup pseudowires to maintain network connectivity if one pseudowire fails.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/wan_l2vpn_pw_red_xe.html
The L2VPN Pseudowire Switching feature extends layer 2 virtual private network (L2VPN) pseudowires across an interautonomous system (inter-AS) boundary or across two separate multiprotocol label switching (MPLS) networks.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_l2vpn_pseudo_swit_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_lawful_intercept.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/wan/configuration/guide/wan_l2_tun_pro_v3.html
Previously available on only port-channel subinterfaces, QoS can now be applied to the main GigabitEtherChannel (GEC) interface, or memberlink. QoS is applied through policy maps.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/lanswitch/configuration/guide/lsw_cfg_gecqos.html
The Modified LNS Dead-Cache Handling feature allows you to display and clear (restart) any Layer 2 Tunnel Protocol (L2TP) Network Server (LNS) entry in a dead-cache (DOWN) state. You can use this feature to generate a Simple Network Management Protocol (SNMP) or system message log (syslog) event when an LNS enters or exits a dead-cache state. Once an LNS exits the dead-cache state, the LNS is able to establish new sessions.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/vpdn/configuration/guide/config_aaa_for_vpdn_xe.html
The MQC—Traffic Shaping Overhead Accounting for ATM feature enables a broadband aggregation system (BRAS) to account for various encapsulation types when applying QoS functionality to packets.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/overhead_acctng_xe.html
Cisco IOS XE NAT provides ALG support for NetMeeting directory Lightweight Directory Access Protocol (LDAP) messages.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipaddr/configuration/guide/iadnat_applvlgw_xe.html
Cisco IOS XE NAT provides Skinny Call Control Protocol (SCCP) message translation support.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipaddr/configuration/guide/iadnat_applvlgw_xe.html
Cisco IOS XE NAT supports extended methods for the Session Initiation Protocol (SIP.)
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipaddr/configuration/guide/iadnat_applvlgw_xe.html
Cisco IOS XE NAT supports H.225 and H.245 message types, including those sent in the Registration, Admission, and Status (RAS) protocol.
RAS provides a number of messages that are used by software clients and VoIP devices to register their location, request assistance in call set up, and control bandwidth. The RAS messages are directed toward an H.323 gatekeeper.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipaddr/configuration/guide/iadnat_applvlgw_xe.html
The NSF/SS0—Ethernet to Ethernet VLAN Interworking features enables stateful switchover (SSO) and nonstop forwarding (NSF) capabilities for Ethernet to VLAN attachment circuits. Changes in the learned MAC address for interworking are reflected on the standby RP so that identical values exist on the Active and Standby RPs.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_trnsprt_mlps_atom_xe.html
For information about this feature, see the following document:
The Parameterization for ACL and Layer 4 Redirect feature provides parameterization enhancements for access control lists and Layer 4 redirect.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_l4_redirect_xe.html
The Parameterization of QoS ACL feature provides enhancements for quality of service (QoS) access control lists (ACLs). This feature allows the authentication, authorization, and accounting (AAA) device to dynamically change parameters.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_rabapol_xe.html
The Per Subinterface MTU for Ethernet over MPLS (EoMPLS) feature provides you with the ability to specify maximum transmission unit (MTU) values in xconnect subinterface configuration mode. When you use xconnect subinterface configuration mode to set the MTU value, you establish a pseudowire connection for situations where the interfaces have different MTU values that cannot be changed.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_any_transport_xe.html
The PKI-CLI to Control Certificate Revocation List (CRL) Cache feature allows the administrator to control the CRL cache size. CRLs are received by Cisco IOS software in Distinguished Encoding Rules (DER) encoded format. Because processing a DER encoded CRL uses CPU memory, Cisco IOS software allows CRLs either to be stored in cache after being processed or to be decoded. Configuring the CRL cache size allows the amount of memory to be decreased (for example, if low memory conditions exist) or to be increased (for example, when a large number of CRLs are being processed), resulting in better performance.
The following commands were introduced or modified by this feature: crypto pki crl cache and show crypto pki crls. The crypto pki crl cache command allows the administrator to set the maximum amount of volatile memory used to cache CRLs. When the crypto pki crl cache command is configured, the show crypto pki crls command output includes information on the CRL cache size.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_pppoe_baa_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_limit_legcfg_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_pppoe_sss_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_pppoe_baa_xe.html
The Pseudowire Emulation Edge-to-Edge MIBs for Ethernet, Frame Relay, and ATM Services feature provides Simple Network Management Protocol (SNMP) support within an Any Transport over Multiprotocol Label Switching (AToM) infrastructure emulating Ethernet, Frame Relay, and ATM services over packet switched networks (PSNs).
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_edge2edge_mibs_xe.html
The QoS: CBQoSMIB Index Enhancements feature allows automatic inclusion of downstream Ethernet frame headers in shaped rate
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/cbqos_mib_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_lawful_intercept.html
The RADIUS-Based Policing Attribute Modifications feature allows the RADIUS server to communicate with the Intelligent Services Gateway (ISG) by embedding specific attributes in Access-Accept and CoA messages. RADIUS-based shaping and policing employs this exchange of attributes to activate and deactivate services, and to modify the active quality of service (QoS) policy applied to a session.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/isg/configuration/guide/isg_rabapol_xe.html
The aaa authentication suppress null-username command is used to provide the ability to prevent an Access Request with a blank username from being sent to the RADIUS server. This functionality ensures that unnecessary RADIUS server interaction is avoided, and RADIUS logs are kept short.
For information about this feature, see the "Preventing an Access Request with a Blank Username from Being Sent to the RADIUS Server" subsection in following document:
http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_cfg_authentifcn.html
The RSA 4096-Bit Key Generation in Software Crypto Engine Support feature increases the maximum RSA key size from 2048 bits to 4096 bits for private key operations.
The SCCP for Video feature enables Cisco Firewalls to inspect Skinny control packets that are exchanged between a Skinny client and the Cisco Call Manager.
For information about this feature, see the following document:
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_secure_shell_v2.html
The VLAN ID Rewrite feature enables you to use VLAN interfaces with different VLAN IDs at both ends of the tunnel.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_any_transport_xe.html
The VPDN LNS Address Checking feature allows an L2TP Access Concentrator (LAC) to check the IP address of the L2TP Network Server (LNS) sending traffic to it during the setup of an L2TP tunnel, thus providing a check for uplink and downlink traffic arriving from different interfaces.
The benefit of the LNS Address Checking feature is avoiding the loss of revenue from users sending back traffic through an alternate network.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/vpdn/configuration/guide/config_aaa_for_vpdn_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_per_vrf_aaa.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_lawful_intercept.html
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.3.2.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.3.2.
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.3.1.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.3.1.
The following new hardware features are supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.3.0:
•New Cisco ASR 1000 Route Processor
Cisco IOS XE Release 2.3.0 introduces support for the following new Route Processor (RP):
The Cisco ASR 1000 Series Route Processor 2 (Cisco ASR1000-RP2) is the second-generation route processor for the Cisco ASR 1000 Series Aggregation Services Router. The Cisco ASR1000-RP2 provides advanced routing capabilities, monitors and manages the other components of the Cisco ASR 1000 Series Aggregation Services Router, and provides a processing engine for integrated applications. In addition to the current route processing features and benefits of the Cisco ASR 1000 Series Route Processor 1(Cisco ASR1000-RP1), the Cisco ASR1000-RP2, supports:
•Memory scalability up to 16 GB DRAM
•8 GB or 16 GB of synchronous dynamic RAM (SDRAM) in 4 SDRAM slots. A route processor with 8 GB can hold four 8 GB dual in-line memory modules (DIMMs); whereas a route processor with 16 GB can hold four 4-GB DIMMs.
•80 GB hard disk drive (HDD) for the storage and portability of code storage, boot, configurations, logs.
The Cisco ASR1000-RP2 is supported as a modular component on the Cisco ASR 1004 and Cisco ASR 1006 routers.
The Cisco ASR 1006 Router contains two RP slots to support full hardware redundancy for RP2s within the same router.
For information about the Cisco ASR1000-RP2, including a table that highlights the major differences between it and the Cisco ASR1000-RP1, see the following document:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
Cisco IOS XE Release 2.3.0 introduces support for the following new shared port adapters (SPAs):
ATM SPAs
•1-Port OC-3 ATM SPA (SPA-1XOC3-ATM-V2)
•3-Port OC-3 ATM SPA (SPA-3XOC3-ATM-V2)
For information about the SPAs supported on the Cisco ASR 1000 Series Routers, see the following documents:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide at the following location:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Software Configuration Guide at the following location:
This section lists new and changed features in Cisco IOS XE Release 2.3.0. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE Release 2.3.0.
•Any Transport Over MPLS (AToM): ATM Cell Relay Over MPLS: VP Mode
•Any Transport over MPLS (AToM): Graceful Restart
•Any Transport Over MPLS (AToM): Layer 2 QoS (Quality of Service)
•Any Transport Over MPLS (AToM): Single Cell Relay - VC Mode (CRoMPLS)
•ATM Conditional debug/show Commands
•ATM PVC F5 OAM Recovery Traps
•ATM PVC Trap Enhancements for Segment and AIS/RDI Failures
•ATM SNMP Trap and OAM Enhancements
•Cell-Based ATM Shaping per PVP
•Consistent and User-Selectable Fail/Open and Fail/Close Operation
•Control Plane Policing—Time Based
•Enhanced ATM VC Configuration and Management
•Explicit Passive Mode CLI Support
•Group Encrypted Transport VPN (GET VPN)
•Integrated Session Border Controller
•IPv6 Multicast: Address Family Support for Multiprotocol BGP
•IPv6 Source Specific Multicast (SSM) Mapping
•ISSU—AToM ATM Attachment Circuit
•ISSU—MPLS Traffic Engineering (TE)—Path Protection
•L2VPN PW Preferential Forwarding (Active/Standby Status)
•L2VPN PW Redundancy—ATM Attachment Circuits
•LSP Ping for FEC129 (via VCCV)—RFC4379
•MPLS EM—LSP Ping/Trace for LDP & RSVP IPv4 FECs
•MPLS EM—MPLS FRR MIB (IETF draft v01)
•MPLS EM—MPLS Multipath (ECMP) LSP Tree Trace
•MPLS EM—MPLS TE MIB (IETF draft v05)
•MPLS LSP Ping/Traceroute and AToM VCCV
•MPLS Pseudowire Status Signaling
•MPLS Support for Multi-Segment PWs—MPLS OAM/VCCV
•MPLS TE—BFD-Triggered Fast Reroute (FRR)
•MPLS TE—Fast Tunnel Interface Down Detection
•MPLS TE—Node Protection Desired Bit
•MPLS Traffic Engineering Forwarding Adjacency
•MPLS Traffic Engineering—Policy Routing onto MPLS TE Tunnels
•MPLS Traffic Engineering (TE)
•MPLS Traffic Engineering (TE)—Configurable Path Calculation Metric for Tunnels
•MPLS Traffic Engineering (TE)—Fast Reroute (FRR) Link and Node Protection
•MPLS Traffic Engineering (TE)—IP Explicit Address Exclusion
•MPLS Traffic Engineering (TE)—LSP Attributes
•MPLS Traffic Engineering (TE)—Path Protection
•MPLS Traffic Engineering (TE)—RSVP Graceful Restart
•MPLS Traffic Engineering (TE)—RSVP Hello State Timer
•MPLS Traffic Engineering (TE): Verbatim Path Support
•MPLS VPN—Explicit Null Label Support with BGP IPv4 Label Session
•NSF/SSO—AToM ATM Attachment Circuit
•NSF/SSO—MPLS TE and RSVP Graceful Restart
•NSF/SSO—MPLS Traffic Engineering (TE)—Path Protection
•Operation, Administration, and Maintenance (OAM) F4 and F5
•PPP—Max-Payload and IWF PPPoE Tag Support
•PPPoE Agent Remote ID and DSL Line Characteristics Enhancement
•PPPoE Circuit-ID Tag Processing
•PPPoE—Session Limiting on Inner QinQ VLAN
•Pseudowire Emulation Edge-to-Edge MIBs for Ethernet, FR, and ATM Services
•QoS-per-VC QoS Classification for ATM VP Pseudowires
•QoS Priority Percentage CLI Support
•Quality of Service: Policies Aggregation
•RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
•RSVP Refresh Reduction and Reliable Messaging
•RSVP—Resource Reservation Protocol
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_any_transport.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_atom_grace_rstrt.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_any_transport.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_any_transport.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_con_deb_supp.html
The Cisco AAL5 MIB adds a proprietary extension to the standard ATM MIB (RFC 1695) to provide per-VC statistic counters that are currently displayed in response to the Cisco IOS show atm vc command for a specified virtual circuit. This MIB extension allows SNMP network management system applications to query the same variables (SNMP objects) as those that can be gathered from the Cisco IOS command- line interface.
The Cisco AAL5 MIB provides SNMP access to four new statistics counters defined for AAL5 virtual connections: incoming packet counter, outgoing packet counter, incoming octet counter, and outgoing octet counter. The Cisco AAL5 MIB groups these four counters in a table called cAal5VccTable.
The proprietary extension of the Cisco AAL5 MIB supports all the tables and objects defined in the Cisco AAL5 MIB for ATM interfaces acting as endpoints of ATM connections that run Cisco IOS XE Release 2.3 software and later releases.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_oam_ping.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_oam.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_cfg_atm.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_oam_f5_cnck.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_snmp_oam_enh.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_snmp_oam_enh.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_any_transport.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_vp_avg_tfc_rate.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_any_transport.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_autosecure.html
The Basic ATM Support of RFC1483 feature provides the basic functions of asynchronous transfer mode (ATM) and compliance with RFC1483.
Documentation URLs are being updated and will be provided soon.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/iproute/configuration/guide/irp_bgp_overview.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/qos_atm_vp_support.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_encrypt_trns_vpn.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/ctrl_plane_policng.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipaddr/configuration/guide/iad_dhcp_client.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipaddr/configuration/guide/iad_dhcp_rly_agt.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_cfg_atm.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_encrypt_trns_vpn.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_encrypt_trns_vpn.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_encrypt_trns_vpn.html
Cisco IOS XE Release 2.3.0 introduces support for the following new Integrated Session Border Controller (SBC) features:
•In-Service Provisioning of H.248 Controllers
•RTCP Policing (with the additional new functionality of RTCP maximum burst size (mbs) policing equal to 5% of RTP mbs)
For information about these SBC features, see the following document:
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/sbc/2_xe/sbc_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-multicast.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-multicast.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-multicast.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ha/configuration/guide/ha-inserv_updg_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_trnsprt_mlps_atom.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_path_prot.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/l2vpn_pw_preferential_forwarding.html
For information about this feature, see the following document:
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_ldp_te_lsp_vccv.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_ldp_te_lsp_vccv.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_fast_rr_mib.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_em_multipath_tree.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_mib.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_ldp_te_lsp_vccv.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_pw_status.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/multisegmentpseudowires.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_bfd_frr.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_link_node_prot.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_link_node_prot.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_fwd_adjacency.html
Cisco IOS XE Release 2.3.0 supports mapping packets to MPLS Traffic Engineering tunnels.
For more information, see the set interface command in the Cisco IOS IP Routing Protocols Command Reference at the following URL:
http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_pi2.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_enhance.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_cfg_path_calc.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_frr_node_prot.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_expl_address.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_lsp_attr.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_path_prot.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_rsvp_graceful.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_rsvp_hello.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_verbatim_path.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_ce_vpn_explicit.html
For information about this feature, see the following document, which also includes a table listing the NBAR protocol support per Cisco IOS XE release:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/clsfy_traffic_nbar_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_trnsprt_mlps_atom.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_te_rsvp_graceful_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_path_prot.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/atm/configuration/guide/atm_oam_f5_cnck.html
The Per-VC Queueing for ATM feature on the Cisco ASR 1000 Series Routers supports two sets of queues on a virtual circuit (VC):
•Queues on a Shared Port Adapter (SPA) that uses segmentation and reassembly (SAR)
•Queues on a Cisco QuantumFlow Processor (QFP)
Configurable SAR queues are not supported on Cisco ASR 1000 Series Routers. SAR allocates two queues per VC, one for high-priority traffic and another for low-priority traffic.
ATM QoS queueing operations on a QFP are carried out using the Modular QoS CLI (MCQ). The tx_limit command is used to change queue size on the QFP.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_ppp_mx_payld_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_rmtid_dsl_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_cir_id_tag_pr_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_relaydis_ssf_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/bbdsl/configuration/guide/bba_qinq_vlan_limt_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_edge2edge_mibs.html
For information about this feature, see the following document:
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/qos_atm_vp_support.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/llq_with_pps_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/guide/qos_policies_agg_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_rad_a66_enhcmts.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/rsvp_messaging.html
The RSVP—Resource Reservation Protocol feature is supported for Multiprotocol Label Switching (MPLS) traffic engineering (TE) based on RFC 2205, Resource ReSerVation Protocol (RSVP - Version 1 Functional Specification, http://www.apps.ietf.org/rfc/rfc2205.html. To enable RSVP, see the ip rsvp bandwidth command in the Cisco IOS Quality of Service Solutions Command Reference.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ha/configuration/guide/ha-stfl_swovr_xe.html
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.2.3.
This section lists new and changed features in Cisco IOS XE Release 2.2.3. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE Release 2.2.3.
•MPLS VPN Carrier Supporting Carrier Using LDP and an IGP
•MPLS VPN Carrier Supporting Carrier with BGP
•MPLS VPN—eBGP Multipath Support for CSC and InterAS MPLS VPNs
•MPLS VPN—Load Balancing Support for Inter-AS and CSC VPNs
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_carrier_ldp_igp.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_carrier_bgp.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_load_share_vpn.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_load_share_vpn.html
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.2.2.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.2.2.
The following new hardware features are supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.2.1:
•New Cisco ASR 1000 Embedded Services Processors
Cisco IOS XE Release 2.2.1 introduces support for the following new Embedded Services Processors (ESPs):
The Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable (Cisco ASR1000-ESP10-N) is a non-crypto capable version of the encryption-enabled 10-Gbps Cisco ASR 1000 Series ESP (Cisco ASR1000-ESP10).
The Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable provides a Cisco ASR 1000 solution for customers who are under export restrictions and not qualified to implement products that support strong encryption services. The Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable feature support is the same as the 10-Gbps Cisco ASR 1000 Series ESP except that IPSec and other data-plane cryptographic features are not supported.
The Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable is supported on all Cisco ASR 1000 Series chassis but should only be used with following consolidated packages that do not contain cryptographic (K9) software:
•Cisco ASR 1000 Series RP1 IP BASE W/O CRYPTO
•Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES W/O CRYPTO
•Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES W/O CRYPTO
Note The Cisco ASR 1000 Series RP1 IP BASE W/O CRYPTO, Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES W/O CRYPTO, and Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES W/O CRYPTO consolidated packages do not require export qualification and can also run on the encryption-enabled 10-Gbps Cisco ASR 1000 Series ESP. The K9-based consolidated packages (Cisco ASR 1000 Series RP1 IP BASE, Cisco ASR 1000 Series RP1 ADVANCED IP SERVICES and Cisco ASR 1000 Series RP1 ADVANCED ENTERPRISE SERVICES) will never be supported on the Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable hardware.
Note The Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable should never be inserted into a chassis using K9 software or the router may reload.
Note The Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable and 10-Gbps Cisco ASR 1000 Series ESP should not be mixed in a hardware-redundant chassis.
For information about the Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable, see the following documents:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable New Feature at the following location:
http://www.cisco.com/en/US/partner/docs/routers/asr1000/feature/guides/ASR_depop.html
The 20-Gbps Cisco ASR 1000 Series ESP (Cisco ASR1000-ESP20) supports 20-Gbps bandwidth and is supported on the Cisco ASR 1004 and Cisco ASR 1006 chassis. It can optionally be deployed in customer networks that require 1+1 redundancy on Cisco ASR 1006 Routers. Performance highlights of the 20-Gbps ESP include hardware-assisted policing, encryption capability of 8 Gbps, 16 Mpps forwarding, 256MB of packet memory, 1GB (bytes) of resource memory performance, and special jitter- and latency-minimizing multicast packet replication.
For information about the 20-Gbps Cisco ASR 1000 Series ESP, see the following document:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
Cisco IOS XE Release 2.2.1 introduces support for the following new shared port adapters (SPAs):
Channelized SPA
•1-Port CHOC-3/CHSTM-1 SPA (SPA-1xCHSTM1/OC3)
POS SPAs
•2-Port OC-48 POS/RPR SPA with SFP Optics (SPA-2XOC48POS/RPR)
•4-Port OC-48 POS/RPR SPA with SFP Optics (SPA-4XOC48POS/RPR)
For information about the SPAs supported on the Cisco ASR 1000 Series Routers, see the following documents:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide at the following location:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Software Configuration Guide at the following location:
This section lists new and changed features in Cisco IOS XE Release 2.2.1. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE Release 2.2.1.
•Cisco Firewall and WAAS Inter-Op
•Class Based Weighted Fair Queuing (CBWFQ)
•Control Plane Policing (CoPP)
•Diffie-Hellman Group Support in IPSec
•GPI (Granular Protocol Inspection) Phase-1
•GRE Tunnel IP Source and Destination VRF Membership
•Integrated Session Border Controller
–Full Support for Wildcard Response
–H.248 Protocol—Acknowledgment Support for Three-Way Handshake
–Improved Media Timeout Detection
–Interim Authentication Header Full Support
–IPSec Pinhole Support—Twice NAT for IPv4 and No NAT for IPv6
•IP SLAs—LSP Health Monitor with LSP Discovery
•IPv6 QoS: MQC Packet Classification
•ISG: Accounting: Per Session, Service and Flow
•ISG: Accounting: Tariff Switching
•ISG: Authentication: DHCP Option 82 Line ID - AAA Authorization Support
•ISG:Flow Control: Flow Redirect (L4, Captive Portal)
•ISG: Flow Control: QoS Control: Dynamic Rate Limiting (QU;QD)
•ISG: Flow Control: QoS Control: MQC Support for IP Sessions
•ISG: Instrumentation: Advanced Conditional Debugging
•ISG: Instrumentation: Session and Flow Monitoring (Local and External)
•ISG: Network Interface: IP Routed, VRF Aware MPLS
•ISG: Network Interface: Tunneled (L2TP)
•ISG: Policy Control: Cisco Policy Language
•ISG: Policy Control: DHCP Proxy
•ISG: Policy Control: ISG-SCE Control Bus
•ISG: Policy Control: Multidimensional Identity per Session
•ISG: Policy Control: Policy: Domain Based (Auto-Domain, Proxy)
•ISG: Policy Control: Policy Server: CoA ASCII Command Code Support
•ISG: Policy Control: Policy Server: CoA (QoS, L4 Redirect, User ACL, TimeOut)
•ISG: Policy Control: Policy Server: SSG-SESM Protocol
•ISG: Policy Control: Policy: Triggers (Time, Volume, Duration)
•ISG: Policy Control: RADIUS Proxy Enhancement
•ISG: Policy Control: Service Profiles
•ISG: Policy Control: User Profiles
•ISG: Session: Auth: Single Sign On
•ISG: Session: Authentication (MAC, IP, EAP)
•ISG: Session: Creation: IP Session: Protocol Event (DHCP, RADIUS)
•ISG: Session: Creation: IP Session: Subnet and Source IP: L2
•ISG: Session: Creation: IP Session: Subnet and Source IP: L3
•ISG: Session: Creation: P2P Session (PPPoE, PPPoXoX)
•ISG: Session: LifeCycle: Idle Timeout
•ISG: Session: Multi-Service Creation and Flow Control
•ISG: Session: Protection and Resiliency: Keepalive—ARP, ICMP
•L2TP AAA Accounting Include NAS-PORT (VPI/VCI)
•L2TP HA Session SSO/ISSU on LAC/LNS
•MPLS LDP— VRF Aware Static Labels
•MPLS VPN: VRF Selection Using Policy Based Routing
•Multi-VRF Selection Using Policy Based Routing (PBR)
•NAT—Routemaps Outside-to-Inside Support
•Packet Classification Based on Layer3 Packet-Length
•PBR Support for Multiple Tracking Options
•Per Subscriber Firewall on LNS
•Policy-Based Routing (PBR) Default Next-Hop Route
•Policy Based Routing: Recursive Next Hop
•Policy Routing Infrastructure
•QoS—Hierarchical Queuing for Ethernet DSLAMs
•VRF Aware System Message Logging (Syslog)
•WCCP Layer 2 Redirection / Forwarding
•WCCP Redirection on Inbound Interfaces
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_cfg_accountg.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipmulti/configuration/guide/imc_basic_cfg.html
The Cisco Firewall and WAAS Interoperability feature enables a router configured with a firewall to successfully communicate with a cache engine, such as a Wide Area Application Acceleration (WAAS) device that is using the Web Cache Communication Protocol (WCCP).
WAAS optimizes remote access to applications.When the cache engine is a WAAS device, it can optimize TCP flow by modifying TCP headers. During the TCP three-way handshake, the WAAS device can add an extra TCP option in the header to indicate that the flow will be optimized. When the TCP session is established, the WAAS device can modify the sequence and acknowledge number in the TCP header to optimize the data flow.
When a Cisco firewall is configured on the router, the packets have to be inspected by the firewall. Depending on the deployment scenario, the firewall inspects packets as follows:
•For client-to-server packets, the firewall inspects packets in the redirect path and ignores packets in the return path.
•For server-to-client packets, the firewall inspects packets in the return path and ignores packets in the redirect path.
•If the firewall encounters a TCP SYN packet with the 0x21 option, the firewall knows that this packet is already a WAAS flow. The firewall will adjust the Layer 4 state to reflect the 2-GB jump in sequence and acknowledge numbers. No Layer 7 inspection will be applied to the flow.
•Although the firewall will ignore the same packets in either the redirect or the return path, the firewall must still perform a session lookup to get the information about the direction of the packet (from client to server or server to client).
This feature has the following restrictions:
•Only Generic Routing Encapsulation (GRE) redirect and return is supported. Layer 2 redirect and return is not supported.
•Certain platforms, such as the Cisco 2800 series, support an inbox network service module (WAAS-NM) that provides WAAS services. The Cisco ASR 1000 series routers do not support inbox network service modules; thus, the router will not support WAAS-NM.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/mrkg_netwk_traffic.html
CBWFQ extends the standard weighted fair queueing (WFQ) functionality to provide support for user-defined traffic classes. For CBWFQ, you define traffic classes based on match criteria such as protocols, access control lists (ACLs), and input interfaces.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/config_wfq.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/ctrl_plane_policng.html
The Diffie-Hellman Group Support in IPSec feature adds support for Diffie-Hellman groups 14, 15, and 16.
For more information, see the group (IKE policy) and set pfs commands in the following document:
http://www.cisco.com/en/US/docs/ios/security/command/reference/sec_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_flex_pack_match.html
The feature GPI (Granular Protocol Inspection) Phase-1 allows for support for the following 10 protocols:
GTP (Granular Protocol Inspection) - FTP (File Transfer Protocol)
GTP - H.323
GTP - ICMP
GTP - RTSP (Real Time Streaming Protocol)
GTP -SIP ( Session Initiation Protocol)
GTP - Skinny Client Control Protocol
GTP - TCP
GTP - TFTP (Trivial File Transfer Protocol)
GTP - UDP
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/interface/configuration/guide/ir_impl_tun.html
Cisco IOS XE Release 2.2.1 introduces support for the following new Integrated Session Border Controller (SBC) features:
•Full Support for Wildcard Response
•H.248 Protocol—Acknowledgment Support for Three-Way Handshake
•Improved Media Timeout Detection
•Interim Authentication Header Full Support
•IPSec Pinhole Support—Twice NAT for IPv4 and No NAT for IPv6
Previously Session Border Controller (SBC) supported H.248 wildcard operations that were restricted to W-Modify or W-Subtract requests, which yielded summary wildcard responses. This feature introduces support for a complete wildcard response. A wildcard H.248 Subtract or Modify operation now returns a complete response with per-termination statistics.
The ServiceChange Handoff functionality on Integrated Session Border Controller conforms to section 7.2.8, ServiceChange, and section 7.2.8.1.1, ServiceChangeMethod, of the H.248.1 v3 Gateway Control Protocol. The ServiceChange Handoff functionality allows a media gateway controller (MGC) to hand over control of a media gateway (MG) to another MGC. The MGC sends a ServiceChange message to the MG that it is currently associated with to request that the MG terminate that association and the MG form a new association with an MGC identified in the ServiceChange message.
In the previous media timeout functionality on the data border element (DBE), if no SBC packets have been seen by the configured number of seconds since the call has been established, then the DBE generates a media timeout alert to the SBE. The Improved Media Timeout Detection feature delays reporting of the media timeout event by instructing the DBE to wait until it has received the first packet since the call has been established. Only then does the media timeout timer start counting the number of seconds for which it has not seen an SBC packet. At the end of the count, the DBE generates an alert to the SBE.
The IPSec Pinhole Support—Twice NAT for IPv4 and No NAT for IPv6 feature adds support for voice calls over IPSec tunnels and adds support for IPSec address-only pinholes. This support enables the DBE to forward IPSec packets when the port cannot be determined because the port is within the encrypted portion of the frame. Thus, IPSec support handles the IPSec requirement that does not allow use of port numbers for session lookup or translation. Currently single IPSec pinholes are supported, whereby both IKE and the encrypted IPSec traffic passes through the same pinhole.
For information about these SBC features, see the following document:
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/sbc/2_xe/sbc_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/sla_lsp_mon_autodisc.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/sla_lsp_mon_autodisc.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/sla_overview.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-qos.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-eigrp.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
The L2TP AAA Accounting Include NAS-PORT (VPI/VCI) feature allows an L2TP Network Server (LNS) to send the NAS Port-ID (attribute 5), as part of the accounting record to the RADIUS authentication, authorization, and accounting (AAA) server.
In Cisco IOS XE Release 2.2.1, the L2TP AAA Accounting Include NAS-PORT feature does not support the asynchronous transfer mode (ATM) virtual path identifier/virtual channel identifier (VPI/VCI) pair.
The L2TP HA Session SSO/ISSU on a LAC/LNS feature provides a generic Stateful Switchover/In Service Software Upgrade (SSO/ISSU) mechanism for Layer 2 Tunneling Protocol (L2TP) on a Layer 2 Access Concentrator (LAC) and a Layer 2 Network Server (LNS). This feature preserves all fully-established Point-to-Point Protocol (PPP) and L2TP sessions (including Multihop) during an SSO switchover, or an ISSU upgrade or downgrade.
For information about this feature, see the following document:
L3 MPLS VPN over GRE provides a mechanism for tunneling Multi Protocol Label Switching (MPLS) packets over a non-MPLS network.
The L3 MPLS VPN over GRE feature utilizes MPLS over Generic Routing Encapsulation (MPLSoGRE) to encapsulate MPLS packets inside IP tunnels; thus creating a virtual point-to-point link across non-MPLS networks. This allows users of primarily MPLS networks to continue to use existing non-MPLS legacy networks until migration to MPLS is possible.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_vpn_gre.html
The MPLS LDP-VRF-Aware Static Labels document explains how to configure the MPLS LDP-VRF-Aware Static Labels feature and Multiprotocol Label Switching (MPLS) static labels.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_vrf_aware_static.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_vpn_per_vrf_lbl.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_vpn_vrf_select_rt.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/vpdn/configuration/guide/config_multihop_vpdn_xe.html
The Multi-VRF Selection Using Policy-Based Routing feature allows a specified interface on a provider edge (PE) router to route packets to Virtual Private Networks (VPNs) based on packet length or match criteria defined in an IP access list.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_mltvrf_slct_pbr.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipaddr/configuration/guide/iadnat_addr_consv_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/class_l3_pkt_length.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/iproute/configuration/guide/irp_prb_mult_track.html
The Per-Subscriber Firewall on LNS feature enables the zone-based policy firewall configuration model to be implemented on the Cisco ASR 1000 Series Router. Zone-based policy firewall is a unidirectional firewall policy between groups of interfaces known as zones. (Previously, Cisco firewalls were configured as an inspect rule only on interfaces. Traffic entering or leaving the configured interface was inspected based on the direction that the inspect rule was applied.) Now, interfaces are assigned to zones, and inspection policies are applied to traffic moving between the zones. Interzone policies offer considerable flexibility and granularity, so different inspection policies can be applied to multiple host groups connected to the same router interface.
In addition to the zone-based policy firewall model, the Per-Subscriber Firewall on LNS feature introduces the following additional functionality for the Cisco ASR 1000 Series Router:
•Dynamic zone assignment for virtual access interfaces
Subscribers can be assigned to a zone in one of two ways:
–Using the configuration on the virtual-template interface, which can be useful when placing subscribers in a default zone.
–Using the RADIUS vendor-specific attribute (VSA), which enables zone assignment to be determined when the session is authorized.
•PPP session-level granularity for zone-based policy firewall
Stateful inspection and application monitoring occur at the PPP session, enabling the full suite of firewall and broadband features to be applied per subscriber, simultaneously. That is, extra routers or service blades are not required to support the firewall functionality. The firewall functionality is applied by the packet processor engine (PPE) in the forwarding path for broadband traffic.
•Per-subscriber drop log messages
Service providers can track drops on a per-subscriber basis by including the subscriber's username in the drop log messages. These drop log messages can also be sent to an off-box server for additional processing.
•Zone pairs with matching source and destination zones
Service providers can customize the firewall policy for traffic between subscribers in the same zone. Customization is useful for overriding the default behavior, which is the passage of all traffic within the same zone.
For more information on zone-based policy firewalls, see the following documents:
•Zone-Based Policy Firewall
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_zone_polcy_firew.html
•Zone-based Policy Firewall Design and Application Guide
http://www.cisco.com/en/US/products/sw/secursw/ps1018/products_tech_note09186a00808bc994.shtml
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/iproute/configuration/guide/irp_ip_prot_indep.html
Note Cisco IOS XE Release 2 only supports PBR on IPv4; Cisco IOS Release 2 does not support IPv6 PBR.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/iproute/configuration/guide/irp_ip_prot_indep.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/iproute/configuration/guide/irp_prb_rec_next_hop_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/iproute/configuration/guide/irp_ip_prot_indep.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/bbdsl/configuration/guide/bba_pppoe_qinq.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/hier_que_eth_dslams.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_rad_route_dwnld.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_ra_mpls_vpns.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/isg/configuration/guide/2_xe/isg_2_xe_book.html
The VRF Aware System Message Logging (Syslog) feature allows a router to send system logging (syslog) messages to a syslog server host connected through a Virtual Private Network (VPN) routing and forwarding (VRF) interface.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_vrf_aware_loggng.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ios_xe/vpdn/configuration/guide/additional_vpdn_feat_xe.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_wccp.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_wccp.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_wccp.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_wccp.html
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_wccp.html
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.1.2.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.1.2.
There are no new hardware features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.1.1.
There are no new software features supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.1.1.
The following new hardware features are supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 2.1.0:
•Cisco ASR 1000 Embedded Services Processors
•Cisco ASR 1000 Route Processor 1
•Cisco ASR 1000 SPA Interface Processor
•1GB USB Flash Token for Cisco ASR 1000 Series
The Cisco ASR 1002 Router (3-SPA, 2-RU chassis) comes with an integrated Route Processor (RP), an integrated SPA Interface Processor (SIP), four built-in Gigabit Ethernet ports, and is configurable with either the 5 Gbps or 10 Gbps Embedded Services Processor (ESP). The Cisco ASR 1002 Router supports the following components:
•One Cisco ASR 1000 Series Embedded Services Processor (ESP). Either the 5-Gbps Cisco ASR 1000 Series ESP (Cisco ASR1000-ESP5) or the 10-Gbps Cisco ASR 1000 Series ESP (Cisco ASR1000-ESP10).
•One Cisco ASR 1000 Series Route Processor 1 (Cisco ASR1000-RP1) with 4-GB DRAM (memory is not factory- or field-upgradeable) integrated in the chassis
•Four built-in Gigabit Ethernet ports
•One Cisco ASR 1000 SPA Interface Processor 10 (Cisco ASR1000-SIP10) integrated in the chassis
•Up to three fixed SPAs integrated in the chassis
•Dual (redundant) power supplies, option of either AC or DC power supply
Running on Cisco IOS XE Software, the Cisco ASR 1002 Router supports software redundancy, Cisco high-availability features, Nonstop Forwarding (NSF), and In Service Software Upgrades (ISSUs) without redundant hardware.
For information about the Cisco ASR 1002 Router, see the following documents:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
Cisco ASR 1002 Quick Start Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/quick/start/guide/asr1_qs2.html
The Cisco ASR 1004 Router (8-SPA, 4-RU chassis) comes with one Route Processor (RP) slot, one Embedded Services Processor (ESP) slot, two SPA Interface Processor (SIP) slots, and provides 10 Gbps throughput support. The Cisco ASR 1004 Router supports the following components:
•One Cisco ASR 1000 Series Embedded Services Processor (Cisco ASR1000-ESP10)
•One Cisco ASR 1000 Series Route Processor 1 (Cisco ASR1000-RP1)
•Up to two Cisco ASR 1000 Series SPA Interface Processors (Cisco ASR1000-SIP10s)
•Up to eight SPAs
•Dual (redundant) power supplies, option of either AC or DC power supply
Running on Cisco IOS XE Software, the Cisco ASR 1004 Router supports software redundancy, Cisco high-availability features, NSF, and ISSUs without redundant hardware.
For information about the Cisco ASR 1004 Router, see the following documents:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
Cisco ASR 1004 Quick Start Guideat the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/quick/start/guide/asr1_qs4.html
The Cisco ASR 1006 Router (12-SPA, 6-RU chassis) provides the option of hardware-redundant Route Processor (RP) and Embedded Services Processor (ESP) support. Its features include two ESP slots, two RP slots, three SIP slots, and 10 Gbps throughput support. The Cisco ASR 1006 Router supports the following components:
•Dual Cisco ASR 1000 Series Embedded Services Processors (Cisco ASR1000-ESP10s)
•Dual Cisco ASR 1000 Series Route Processor 1s (Cisco ASR1000-RP1s)
•Up to three Cisco ASR 1000 Series SPA Interface Processors (Cisco ASR1000-SIP10s)
•Up to twelve SPAs
•Dual (redundant) power supplies, option of either AC or DC power supply
Note When multiple ESPs, RPs, and SIPs are used, the amount of memory should be equal for like components. (The amount of memory in both ESPs should be equal, the amount of memory in both RPs should be equal, and the amount of memory in each SIP should be equal.) Earlier releases may have a few field replaceable units (FRUs) that support different amounts of memory.
Running on Cisco IOS XE Software, the Cisco ASR 1006 Router supports hardware redundancy, NSF, ISSUs, and future Route-Processor service upgrades.
Note Software redundancy is not supported on the Cisco ASR 1006 Router.
For information about the Cisco ASR 1006 Router, see the following documents:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
Cisco ASR 1006 Quick Start Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/quick/start/guide/asr1_qs6.html
The Cisco ASR 1000 Series Embedded Services Processors (ESPs) provide the centralized forwarding-engine options for the Cisco ASR 1000 Series Routers. Based on the first generation of the hardware and software architecture known as the Cisco QuantumFlow Processor, the Cisco ASR 1000 Series ESPs are responsible for the data-plane processing tasks, and all network traffic flows through them. The modules perform all baseline packet routing operations, including MAC classification, Layer 2 and Layer 3 forwarding, Quality of Service (QoS) classification, policing and shaping, security access control lists (ACLs), virtual private networks (VPNs), load balancing, and NetFlow. They are also responsible for features such as firewalls, intrusion prevention, Network Based Application Recognition (NBAR), and Network Address Translation (NAT).
The Cisco ASR 1000 Series Routers support two ESPs:
•5-Gbps Cisco ASR 1000 Series ESP (Cisco ASR1000-ESP5), which is only supported on the Cisco ASR 1002 chassis
•10-Gbps Cisco ASR 1000 Series ESP (Cisco ASR1000-ESP10), which is supported on all Cisco ASR 1000 Series chassis
The 5-Gbps Cisco ASR 1000 Series ESP (Cisco ASR1000-ESP5) supports 5-Gbps bandwidth, an encryption capability of 1 Gbps, and is supported exclusively on the Cisco ASR 1002 chassis.
The 10-Gbps Cisco ASR 1000 Series ESP (Cisco ASR1000-ESP10) supports 10-Gbps bandwidth, is supported on all Cisco ASR 1000 Series chassis, and can optionally be deployed in customer networks that require 1+1 redundancy on Cisco ASR 1006 Routers. Performance highlights of the 10-Gbps ESP include hardware-assisted policing, encryption capability of 3 Gbps, and special jitter- and latency-minimizing multicast packet replication.
For information about the 5-Gbps Cisco ASR 1000 Series ESP and the 10-Gbps Cisco ASR 1000 Series ESP, see the following document:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
The Cisco ASR 1000 Series Route Processor 1 (Cisco ASR1000-RP1) is the main control plane processor in the chassis and is responsible for:
•All control processor communication (such as running the operating system, managing control traffic, storing files, system logging, and most management-type tasks).
•Processing locally destined control-plane packets and RP-switched packets.
•Central network clocking.
•Certain control plane functions related to PPPoE and Session Border Controller (SBC) functions. (These functions are the single largest source of RP overhead.)
•Cisco ASR 1000 Series field replaceable unit (FRU) online insertion and removal (OIR).
•Selection of the active Cisco ASR1000-RP1 and Cisco ASR 1000 Series Embedded Services Processor, and notification of the SIP of these events.
On the Cisco ASR 1002 Router, the Cisco ASR1000-RP1 is integrated in the chassis and comes with 4-GB DRAM (memory is neither factory- nor field-upgradeable).
On the Cisco ASR 1004 and Cisco ASR 1006 routers, the Cisco ASR1000-RP1 is supported as a modular component and supports two memory options:
•2-GB DRAM
•4-GB DRAM
The Cisco ASR 1006 Router contains two RP slots to support full hardware redundancy for RP1s within the same router.
For information about the Cisco ASR1000-RP1, see the following document:
Cisco ASR 1000 Series Aggregation Services Routers Hardware Installation Guide at the following location:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
The Cisco ASR 1000 Series SPA Interface Processor (SIP) (Cisco ASR1000-SIP10) accepts up to 4 half-height or 2 full-height Cisco SPAs, including Ethernet, Packet over SONET/SDH (POS), and Serial SPAs, providing up to 10-Gbps connection to the system backplane with an ability to differentiate traffic based on Layer 2 or Layer 3 header information.
The Cisco ASR 1000 Series SIP is built into the Cisco ASR1002 chassis and supported as a modular component on the Cisco ASR1004 and Cisco ASR1006 chassis. The Cisco ASR 1004 chassis contains two SIP slots; the Cisco ASR 1006 chassis contains three SIP slots.
For information about the Cisco ASR 1000 Series SIP, see the following documents:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide at the following location:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Software Configuration Guide at the following location:
Shared Port Adapters (SPAs) provide the physical interfaces for router connectivity ranging from copper, channelized, POS, and Ethernet.
The Cisco ASR 1000 Series Routers support the following SPAs:
Serial SPAs
•2-Port and 4-Port T3/E3 Serial SPA (SPA-2XT3/E3, SPA-4XT3/E3)
•2-Port and 4-Port Channelized T3 SPA (SPA-2XCT3/DS0, SPA-4XCT3/DS0)
•8-Port Channelized T1/E1 Serial SPA (SPA-8XCHT1/E1)
•4-Port Serial Interface SPA (SPA-4XT-Serial)
Ethernet SPAs
•4-Port and 8-Port Fast Ethernet SPA (SPA-4X1FE-TX-V2, SPA-8X1FE-TX-V2)
•1-Port 10-Gigabit Ethernet SPA (SPA-1X10GE-L-V2)
•2-Port Gigabit Ethernet SPA (SPA-2X1GE-V2)
•5-Port Gigabit Ethernet SPA (SPA-5X1GE-V2)
•8-Port Gigabit Ethernet SPA (SPA-8X1GE-V2)
•10-Port Gigabit Ethernet SPA (SPA-10X1GE-V2)
POS SPAs
•1-Port OC-12c/STM-4 POS SPA (SPA-1XOC12-POS)
•2-Port and 4-Port OC-3 POS SPA (SPA-2XOC3-POS, SPA-4XOC3-POS)
For information about the SPAs supported on the Cisco ASR 1000 Series Routers, see the following documents:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide at the following location:
•Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Software Configuration Guide at the following location:
The Cisco ASR 1000 Series Routers support a 1GB USB Flash Token for Cisco ASR 1000 Series. This USB Flash token can be used to store images, configuration files, or any other type of data, and can also be used to boot a consolidated package on the router. (The USB Flash token can not be used to boot sub-packages on the router.)
This section describes new and changed features in Cisco IOS XE Release 2.1.0. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS XE Release 2.1.0. To determine if a feature is new or changed, refer to the feature history table at the beginning of the feature module for that feature. Links to feature modules are included. If a feature does not have a link to a feature module, that feature is documented only in the release notes, and information about whether the feature is new or changed will be available in the feature description provided.
Note This section is not cumulative and list only new features that were introduced for Cisco IOS XE Release 2.1.0. For information about inherited features, refer to the Cisco Feature Navigator tool at http://www.cisco.com/go/fn.
•BFD—IPv6 Static Route Support
•DHCP—DHCPv6 Relay Agent Notification for Prefix Delegation
•DHCP Relay Server ID Override and Link Selection Option 82 Suboptions
•DHCPv6 Ethernet Remote ID Option
•Integrated Session Border Controller
•IPv6: Base Protocols High Availability
•IPv6: NSF and Graceful Restart for MP-BGP IPv6 Address Family
•IPv6: RIPng Non-Stop Forwarding
•IPv6: Static Route Non-Stop Forwarding
•MQC—Distribution of Remaining Bandwidth Using Ratio
•PPPoE Session Limit Local Override
•Quality of Service for Gigabit EtherChannels
•VLAN Mapping to GEC Member Links
The Bidirectional Forwarding Detection for IPv6 (BFDv6) protocol provides fast forwarding path failure detection times for all media types, encapsulations, topologies, and routing protocols. In addition to fast forwarding path failure detection, BFD provides a consistent failure detection method for network administrators. The BFD IPv6 Encaps Support feature updates the Bidirectional Forwarding Protocol (BFD) protocol to provide IPv6 support and accommodate IPv6 addresses.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-bfd.html
The BFD—IPv6 Static Route Support feature enables BFD for IPv6 to be used to verify next-hop reachability for IPv6 static routes.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-bfd.html
The DHCP—DHCPv6 Relay Agent Notification for Prefix Delegation feature allows the router working as a DHCPv6 relay agent to find prefix delegation options by reviewing the contents of a DHCPv6 packet that is being relayed by the relay agent to the client.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-dhcp.html
The DHCP Relay Server ID Override and Link Selection Option 82 Suboptions feature enables the relay agent to be part of all DHCP message exchanges by supporting the use of two suboptions of the relay agent information option (option 82). This design allows DHCPv4 to operate in networks where direct communication between the client and server is not possible or desired. When used together, these two suboptions enable the deployment of an architecture where it is desirable to have all DHCP traffic flow through the relay agent, allowing for greater control of DHCP communications.
This feature also introduces the capability to manually configure the interface for the relay agent to use as the source IP address for messages relayed to the DHCP server. This configuration allows the network administrator to specify a stable, hardware-independent IP address (such as a loopback interface).
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipaddr/configuration/guide/iad_dhcpservidlink_mcp.html
The DHCPv6 Ethernet Remote ID Option feature adds the remote-ID option to relayed (RELAY-FORWARD) DHCPv6 packets.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-dhcp.html
The Integrated Session Border Controller (SBC) is introduced on the Cisco ASR 1000 Series Routers. The Integrated SBC is integrated with other features on the Cisco ASR 1000 Series Routers, without requiring additional application-specific hardware, such as service blades, or the need to create an overlay network of standalone SBC appliances.
Session border controllers are used as key components in interconnecting Voice over IP (VoIP) and multimedia networks of different enterprise customers and service providers. SBCs are deployed at the edge of networks to meet the need for secure, intelligent border element functions. Using SBCs, the end user can make voice and video calls to another end user without being concerned about protocols, network reachability, or safety of the network.
The SBC enables direct IP-to-IP interconnect between multiple administrative domains for session-based services providing protocol and signaling interworking, security, Quality of Service (QoS), network hiding, statistics gathering, and admission control and management.
Currently the data border element (DBE) functionality of the Integrated Session Border Controller is supported on the Cisco ASR 1000 Series Routers.
For information about this feature, see the following documents:
http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/sbc/2_xe/sbc_2_xe_book.html
http://www.cisco.com/en/US/docs/ios/sbc/command/reference/sbc_book.html
The IPv6: Base Protocols High Availability feature enables IPv6 neighbor discovery to support stateful switchover.
For information about this feature, see the following document:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-mptcl_bgp.html
The IPv6: NSF and Graceful Restart for MP