New and Changed Information
The following sections list the new hardware and software features that are supported by the Cisco ASR 1000 Series Routers for Cisco IOS XE Release 3.7S:
New Hardware Features in Cisco ASR 1000 Series Aggregation Services Routers Release 3.7S
The following are the new hardware features in Cisco ASR 1000 Series Aggregation Services Routers Release 3.7S:
Cisco ASR 1002-X Router
The Cisco ASR 1002-X Router is a 3-SPA, 2-RU chassis. The embedded services processor and route processor are integrated into the chassis. There are 6 small form factor pluggable (SFP) Gigabit Ethernet ports. The router provides a forwarding bandwidth of up to 36 Gbps. The Cisco ASR 1002-X Router supports all the general-purpose routing and security features of the Cisco ASR 1000 Series Aggregation Services Routers.
For detailed information, see the following Cisco document:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
Cisco ASR 1000 Embedded Services Processor 100-Gbps
The Cisco ASR 1000 Series Aggregation Services Routers 100-Gbps Embedded Services Processor is a centralized forwarding engine option for the Cisco ASR 1006 and ASR 1013 Routers.
Note Availability of ASR1000 Series100-Gbps Embedded Services Processor is limited to those customers whose feature set profiles are validated and approved by the corresponding Cisco Business Unit.
For detailed information, see the following Cisco document:
http://www.cisco.com/en/US/docs/routers/asr1000/install/guide/asr1routers/asr1higV8.html
New Software Features in Cisco ASR 1000 Series Aggregation Services Routers Release 3.7S
The following are the new software features introduced in Cisco ASR 1000 Series Aggregation Services Routers Release 3.7S:
ASR1000 IPSec Debuggability Enhancement - Phase I
The IOS-XE IPSec Debuggability Enhancements in IPsec VPN reduces the overall debugging effort for customers by modifying the debug platform hardware qfp active feature (IPsec) command and merging the output of several show commands into the output of the following commands that were modified for this feature: show crypto engine accelerator statistic, show crypto ipsec sa, show crypto ruleset, and show tech-support ipsec.
For more information, refer to the Cisco IOS Security Command Reference: Commands S to Z ( http://www.cisco.com/en/US/docs/ios-xml/ios/security/s1/sec-s1-cr-book.html), and Cisco IOS Debug Command Reference, Commands M through R ( http://www.cisco.com/en/US/docs/ios-xml/ios/debug/command/m1/db-m1-cr-book.html).
PfR Syslog and Trap enhancement
The PfR Syslog and Trap Enhancement feature introduces a new CLI command, trigger-log-percentage, that specifies the percentage of out- of-policy (OOP) PfR traffic classes that trigger a syslog. Enhanced error message descriptions are accessible from the Error Message Decoder tool.
For detailed information, see the following Cisco document:
http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/command/pfr-cr-book.html
BGP - multicast VPN auto-discovery and customer-multicast routing
For detailed information, see the following Cisco document:
http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_bgp/configuration/xe-3s/asr1000/irg-mvpn-safi-ipv6.html
ISIS BFD TLV
The IS-IS Bidirectional Forwarding Detection (BFD) Tag Length Value (TLV) feature provides a faster method to detect a loss of an IS-IS adjacency. Before, when an IS-IS adjacency reached the UP state (and therefore could be used for forwarding), a BFD session needed to be established with that neighbor. Now, a BFD session is maintained as long as the hello holddown timer for the neighbor does not expire, which is new for BFD TLV. The BFD session is only deleted if the neighbor hello times out. If BFD signals to IS-IS that a session has gone DOWN, the adjacency associated with that session will transition to DOWN state. Once the BFD session goes back UP, the adjacency state can transition back to an UP state. For a given IS-IS topology, IS-IS determines if BFD is usable for a given neighbor on that topology. BFD is not usable when BFD is enabled on both sides and the BFD session is down. When there are multiple BFD sessions enabled for different address families, such as IPv4 and IPv6, if BFD is not usable for any address family, then BFD is consider not usable for the entire adjacency on that topology. For example, if both IPv4 and IPv6 BFD are enabled for single topology, if either the IPv4 BFD session is down or IPv6 BFD session is down, the neighbor state will be set to DOWN state. If BFD is not enabled for a given address family, then BFD is considered usable for that address family. For single topology mode, the neighbor state is down when either the IPv4 or IPv6 BFD session is not BFD usable, that is, if BFD is enabled on both sides and the BFD session is DOWN. If BFD is not enabled on either side, BFD will be set to TRUE. For multi-topology mode, IS-IS adjacency will be in UP state as long as any topology is UP. However, the neighbor for the topology where BFD is consider not usable is considered down for that specific topology. For example, if both IPv4 and IPv6 BFD are enabled, and the IPv4 session is DOWN and IPv6 session is UP, then the IS-IS adjacency is still UP. In this case, the IPv4 neighbor is considered DOWN and ipv6 neighbor is considered UP.