|
Table Of Contents
New Hardware Features in Cisco IOS Release 12.0(33)S
New Software Features in Cisco IOS 12.0(33)S
New Hardware and Software Features in Cisco IOS Release 12.0(32)S3 to Cisco IOS Release 12.0(32)S9
New Hardware Features in Cisco IOS Release 12.0(32)S2
New Software Features in Cisco IOS Release 12.0(32)S2
New Hardware Features in Cisco IOS Release 12.0(32)S1
New Software Features in Cisco IOS Release 12.0(32)S1
New Hardware Features in Cisco IOS Release 12.0(32)S
New Software Features in Cisco IOS Release 12.0(32)S
New Hardware and Software Features in Cisco IOS Release 12.0(31)S4 to Cisco IOS Release 12.0(31)S4
New Hardware Features in Cisco IOS Release 12.0(31)S3
New Software Features in Cisco IOS Release 12.0(31)S3
New Hardware Features in Cisco IOS Release 12.0(31)S2
New Software Features in Cisco IOS Release 12.0(31)S2
New Hardware Features in Cisco IOS Release 12.0(31)S1
New Software Features in Cisco IOS Release 12.0(31)S1
New Hardware Features in Cisco IOS Release 12.0(31)S
New Software Features in Cisco IOS Release 12.0(31)S
New Hardware and Software Features in Cisco IOS Release 12.0(30)S1 to Cisco IOS Release 12.0(30)S5
New Hardware Features in Cisco IOS Release 12.0(30)S
New Software Features in Cisco IOS Release 12.0(30)S
New Hardware and Software Features in Cisco IOS Release 12.0(29)S1
New Hardware Features in Cisco IOS Release 12.0(29)S
New Software Features in Cisco IOS Release 12.0(29)S
New Hardware and Software Features in Cisco IOS Release 12.0(28)S1 to Cisco IOS Release 12.0(28)S6
New Hardware Features in Cisco IOS Release 12.0(28)S
New Software Features in Cisco IOS Release 12.0(28)S
New Hardware and Software Features in Cisco IOS Release 12.0(27)S1 to Cisco IOS Release 12.0(27)S5
New Hardware Features in Cisco IOS Release 12.0(27)S
New Software Features in Cisco IOS Release 12.0(27)S
New Hardware and Software Features in Cisco IOS Release 12.0(26)S1 to Cisco IOS Release 12.0(26)S6
New Hardware Features in Cisco IOS Release 12.0(26)S
New Software Features in Cisco IOS Release 12.0(26)S
New Hardware and Software Features in Cisco IOS Release 12.0(25)S1 to Cisco IOS Release 12.0(25)S4
New Hardware Features in Cisco IOS Release 12.0(25)S
New Software Features in Cisco IOS Release 12.0(25)S
New Hardware and Software Features in Cisco IOS Release 12.0(24)S1 to Cisco IOS Release 12.0(24)S6
New Hardware Features in Cisco IOS Release 12.0(24)S
New Software Features in Cisco IOS Release 12.0(24)S
New Hardware and Software Features in Cisco IOS Release 12.0(23)S1 to Cisco IOS Release 12.0(23)S6
New Hardware Features in Cisco IOS Release 12.0(23)S
New Software Features in Cisco IOS Release 12.0(23)S
New Hardware and Software Features in Cisco IOS Release 12.0(22)S1 to Cisco IOS Release 12.0(22)S6
New Hardware Features in Cisco IOS Release 12.0(22)S
New Software Features in Cisco IOS Release 12.0(22)S
New Hardware and Software Features in Cisco IOS Release 12.0(21)S1 to Cisco IOS Release 12.0(21)S8
New Hardware Features in Cisco IOS Release 12.0(21)S
New Software Features in Cisco IOS Release 12.0(21)S
New Hardware and Software Features in Cisco IOS Release 12.0(19)S1 to Cisco IOS Release 12.0(19)S4
New Hardware Features in Cisco IOS Release 12.0(19)S
New Software Features in Cisco IOS Release 12.0(19)S
New Hardware and Software Features in Cisco IOS Release 12.0(18)S1 to Cisco IOS Release 12.0(18)S7
New Hardware Features in Cisco IOS Release 12.0(18)S
New Software Features in Cisco IOS Release 12.0(18)S
New Hardware and Software Features in Cisco IOS Release 12.0(17)S1 to Cisco IOS Release 12.0(17)S7
New Hardware Features in Cisco IOS Release 12.0(17)S
New Software Features in Cisco IOS Release 12.0(17)S
New Hardware and Software Features in Cisco IOS Release 12.0(16)S1 to Cisco IOS Release 12.0(16)S10
New Hardware Features in Cisco IOS Release 12.0(16)S
New Software Features in Cisco IOS Release 12.0(16)S
New Hardware and Software Features in Cisco IOS Release 12.0(15)S1 to Cisco IOS Release 12.0(15)S7
New Hardware Features in Cisco IOS Release 12.0(15)S
New Software Features in Cisco IOS Release 12.0(15)S
New Hardware and Software Features in Cisco IOS Release 12.0(14)S1 to Cisco IOS Release 12.0(14)S8
New Hardware Features in Cisco IOS Release 12.0(14)S
New Software Features in Cisco IOS Release 12.0(14)S
New Hardware and Software Features in Cisco IOS Release 12.0(13)S1 to Cisco IOS Release 12.0(13)S6
New Hardware Features in Cisco IOS Release 12.0(13)S
New Software Features in Cisco IOS Release 12.0(13)S
New Hardware and Software Features in Cisco IOS Release 12.0(12)S3 to Cisco IOS Release 12.0(12)S3
New Hardware Features in Cisco IOS Release 12.0(12)S
New Software Features in Cisco IOS Release 12.0(12)S
New Hardware and Software Features in Cisco IOS Release 12.0(11)S6
New Hardware Features in Cisco IOS Release 12.0(11)S
New Software Features in Cisco IOS Release 12.0(11)S
New Hardware and Software Features in Cisco IOS Release 12.0(10)S7 to Cisco IOS Release 12.0(10)S8
New Hardware Features in Cisco IOS Release 12.0(10)S
New Software Features in Cisco IOS Release 12.0(10)S
New Hardware and Software Features in Cisco IOS Release 12.0(8)S1
New Hardware Features in Cisco IOS Release 12.0(8)S
New Software Features in Cisco IOS Release 12.0(8)S
New Hardware Features by Cisco IOS Release 12.0(7)S
New Software Features in Cisco IOS Release 12.0(7)S
New Hardware Features in Cisco IOS Release 12.0(6)S
New Software Features in Cisco IOS Release 12.0(6)S
New Hardware Features in Cisco IOS Release 12.0(5)S
New Software Features in Cisco IOS Release 12.0(5)S
Limitations That Apply to Cisco IOS Release 12.0(31)S
Limitations That Apply to Cisco IOS Release 12.0(30)S
Limitations That Apply to Cisco IOS Release 12.0(28)S
Limitations That Apply to Cisco IOS Release 12.0(22)S
Important Notes for Cisco IOS Release 12.0(33)S
Important Notes for Cisco IOS Release 12.0(32)S
Important Notes for Cisco IOS Release 12.0(31)S
Important Notes for Cisco IOS Release 12.0(28)S
Important Notes for Cisco IOS Release 12.0(27)S
Important Notes for Cisco IOS Release 12.0(26)S
Important Notes for Cisco IOS Release 12.0(24)S
Important Notes for Cisco IOS Release 12.0(23)S
Important Notes for Cisco IOS Release 12.0(22)S3
Important Notes for Cisco IOS Release 12.0(22)S
Important Notes for Cisco IOS Release 12.0(21)S
Important Notes for Cisco IOS Release 12.0(19)S
Important Notes for Cisco IOS Release 12.0(18)S
Important Notes for Cisco IOS Release 12.0(17)S
Important Notes for Cisco IOS Release 12.0(16)S
Important Notes for Cisco IOS Release 12.0(15)S
Important Notes for Cisco IOS Release 12.0(14)S
Important Notes for Cisco IOS Release 12.0(13)S
Important Notes for Cisco IOS Release 12.0(12)S
Important Notes for Cisco IOS Release 12.0(10)S
Important Notes for Cisco IOS Release 12.0(9)S
Important Notes for Cisco IOS Release 12.0(5)S
New and Changed Information
This section lists the new hardware and software features that are supported by the Cisco 7200 series routers, the Cisco 7500/RSP series routers, the Cisco 10000 series edge services routers, the Cisco 10720 Internet router, and the Cisco 12000 series Internet routers in Cisco IOS Release 12.0S and contains the following sections:
• New Hardware Features in Cisco IOS Release 12.0(33)S
• New Software Features in Cisco IOS 12.0(33)S
• New Hardware Features in Cisco IOS Release 12.0(32)S2
• New Software Features in Cisco IOS Release 12.0(32)S2
• New Hardware Features in Cisco IOS Release 12.0(32)S1
• New Software Features in Cisco IOS Release 12.0(32)S1
• New Hardware Features in Cisco IOS Release 12.0(32)S
• New Software Features in Cisco IOS Release 12.0(32)S
• New Hardware Features in Cisco IOS Release 12.0(31)S3
• New Software Features in Cisco IOS Release 12.0(31)S3
• New Hardware Features in Cisco IOS Release 12.0(31)S2
• New Software Features in Cisco IOS Release 12.0(31)S2
• New Hardware Features in Cisco IOS Release 12.0(31)S1
• New Software Features in Cisco IOS Release 12.0(31)S1
• New Hardware Features in Cisco IOS Release 12.0(31)S
• New Software Features in Cisco IOS Release 12.0(31)S
• New Hardware and Software Features in Cisco IOS Release 12.0(30)S1 to Cisco IOS Release 12.0(30)S5
• New Hardware Features in Cisco IOS Release 12.0(30)S
• New Software Features in Cisco IOS Release 12.0(30)S
• New Hardware and Software Features in Cisco IOS Release 12.0(29)S1
• New Hardware Features in Cisco IOS Release 12.0(29)S
• New Software Features in Cisco IOS Release 12.0(29)S
• New Hardware and Software Features in Cisco IOS Release 12.0(28)S1 to Cisco IOS Release 12.0(28)S6
• New Hardware Features in Cisco IOS Release 12.0(28)S
• New Software Features in Cisco IOS Release 12.0(28)S
• New Hardware and Software Features in Cisco IOS Release 12.0(27)S1 to Cisco IOS Release 12.0(27)S5
• New Hardware Features in Cisco IOS Release 12.0(27)S
• New Software Features in Cisco IOS Release 12.0(27)S
• New Hardware and Software Features in Cisco IOS Release 12.0(26)S1 to Cisco IOS Release 12.0(26)S6
• New Hardware Features in Cisco IOS Release 12.0(26)S
• New Software Features in Cisco IOS Release 12.0(26)S
• New Hardware and Software Features in Cisco IOS Release 12.0(25)S1 to Cisco IOS Release 12.0(25)S4
• New Hardware Features in Cisco IOS Release 12.0(25)S
• New Software Features in Cisco IOS Release 12.0(25)S
• New Hardware and Software Features in Cisco IOS Release 12.0(24)S1 to Cisco IOS Release 12.0(24)S6
• New Hardware Features in Cisco IOS Release 12.0(24)S
• New Software Features in Cisco IOS Release 12.0(24)S
• New Hardware and Software Features in Cisco IOS Release 12.0(23)S1 to Cisco IOS Release 12.0(23)S6
• New Hardware Features in Cisco IOS Release 12.0(23)S
• New Software Features in Cisco IOS Release 12.0(23)S
• New Hardware and Software Features in Cisco IOS Release 12.0(22)S1 to Cisco IOS Release 12.0(22)S6
• New Hardware Features in Cisco IOS Release 12.0(22)S
• New Software Features in Cisco IOS Release 12.0(22)S
• New Hardware and Software Features in Cisco IOS Release 12.0(21)S1 to Cisco IOS Release 12.0(21)S8
• New Hardware Features in Cisco IOS Release 12.0(21)S
• New Software Features in Cisco IOS Release 12.0(21)S
• New Hardware and Software Features in Cisco IOS Release 12.0(19)S1 to Cisco IOS Release 12.0(19)S4
• New Hardware Features in Cisco IOS Release 12.0(19)S
• New Software Features in Cisco IOS Release 12.0(19)S
• New Hardware and Software Features in Cisco IOS Release 12.0(18)S1 to Cisco IOS Release 12.0(18)S7
• New Hardware Features in Cisco IOS Release 12.0(18)S
• New Software Features in Cisco IOS Release 12.0(18)S
• New Hardware and Software Features in Cisco IOS Release 12.0(17)S1 to Cisco IOS Release 12.0(17)S7
• New Hardware Features in Cisco IOS Release 12.0(17)S
• New Software Features in Cisco IOS Release 12.0(17)S
• New Hardware and Software Features in Cisco IOS Release 12.0(16)S1 to Cisco IOS Release 12.0(16)S10
• New Hardware Features in Cisco IOS Release 12.0(16)S
• New Software Features in Cisco IOS Release 12.0(16)S
• New Hardware and Software Features in Cisco IOS Release 12.0(15)S1 to Cisco IOS Release 12.0(15)S7
• New Hardware Features in Cisco IOS Release 12.0(15)S
• New Software Features in Cisco IOS Release 12.0(15)S
• New Hardware and Software Features in Cisco IOS Release 12.0(14)S1 to Cisco IOS Release 12.0(14)S8
• New Hardware Features in Cisco IOS Release 12.0(14)S
• New Software Features in Cisco IOS Release 12.0(14)S
• New Hardware and Software Features in Cisco IOS Release 12.0(13)S1 to Cisco IOS Release 12.0(13)S6
• New Hardware Features in Cisco IOS Release 12.0(13)S
• New Software Features in Cisco IOS Release 12.0(13)S
• New Hardware and Software Features in Cisco IOS Release 12.0(12)S3 to Cisco IOS Release 12.0(12)S3
• New Hardware Features in Cisco IOS Release 12.0(12)S
• New Software Features in Cisco IOS Release 12.0(12)S
• New Hardware and Software Features in Cisco IOS Release 12.0(11)S6
• New Hardware Features in Cisco IOS Release 12.0(11)S
• New Software Features in Cisco IOS Release 12.0(11)S
• New Hardware and Software Features in Cisco IOS Release 12.0(10)S7 to Cisco IOS Release 12.0(10)S8
• New Hardware Features in Cisco IOS Release 12.0(10)S
• New Software Features in Cisco IOS Release 12.0(10)S
• New Hardware and Software Features in Cisco IOS Release 12.0(8)S1
• New Hardware Features in Cisco IOS Release 12.0(8)S
• New Software Features in Cisco IOS Release 12.0(8)S
• New Hardware Features by Cisco IOS Release 12.0(7)S
• New Software Features in Cisco IOS Release 12.0(7)S
• New Hardware Features in Cisco IOS Release 12.0(6)S
• New Software Features in Cisco IOS Release 12.0(6)S
• New Hardware Features in Cisco IOS Release 12.0(5)S
• New Software Features in Cisco IOS Release 12.0(5)S
Note These release notes are not cumulative and list only features that are new to Cisco IOS Release 12.0S. The parent release for Cisco IOS Release 12.0S is Cisco IOS Release 12.0. For information about inherited features, refer to Cisco.com or Cisco Feature Navigator. For Cisco.com, either go to Cisco.com and select the appropriate software release under Products and Service and IOS Software or go to http://www.cisco.com/univercd/home/index.htm and select the appropriate software release under Cisco IOS Software and Release Notes. You can use the Cisco Feature Navigator tool at http://www.cisco.com/go/fn.
Note MPLS class of service is now referred to as MPLS quality of service. This transition reflects the growth of MPLS to encompass a wider meaning and highlight the path toward Any Transport over MPLS (AToM).
New Hardware Features in Cisco IOS Release 12.0(33)S
This section describes new and changed features in Cisco IOS Release 12.0(33). Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(33)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature.
NPE-G2 Network Processing Engine
Platform: Cisco 7200VXR routers
The Network Processing Engine NPE-G2 is the latest and highest performing routing engine with largest scalability within the network processing engines family for the Cisco 7200VXR Series. A new chip design on the NPE-G2 offers up to double of the performance compared to the NPE-G1 network processing engine. This great performance improvement with the NPE-G2 makes it an ideal Cisco 7200 solution for new aggregation services for the enterprise as well as service provider segment.
New Software Features in Cisco IOS 12.0(33)S
This section describes new and changed features in Cisco IOS Release 12.0(33). Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(33)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature.
BFD Version 1 Support
Platform: Cisco 7200 series, Cisco 7500 series, Cisco 10720 router
Bidirectional Forwarding Detection (BFD) is a detection protocol designed to provide 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. Because the network administrator can use BFD to detect forwarding path failures at a uniform rate, rather than the variable rates for different routing protocol hello mechanisms, network profiling and planning will be easier, and reconvergence time will be consistent and predictable.
L2TPv3 Protocol Demultiplexing for IPv6 over HDLC
Platform: Cisco 7200 series and Cisco 7500 series
Upgrading a service provider network to support IPv6 is a long and expensive process. As an interim solution, the Protocol Demultiplexing for L2TPv3 feature introduces the ability to provide native IPv6 support by setting up a specialized IPv6 network and offloading IPv6 traffic from the IPv4 network. IPv6 traffic is transparently tunneled to the IPv6 network using L2TPv3 pseudowires without affecting the configuration of the CE routers. IPv4 traffic is routed as usual within the IPv4 network, maintaining the existing performance and reliability of the IPv4 network. Cisco IOS Release 12.0(33)S adds support for this feature over HDLC links.
L2TPv3 Protocol Demultiplexing for IPv6 over PPP
Platform: Cisco 7500 series
Upgrading a service provider network to support IPv6 is a long and expensive process. As an interim solution, the Protocol Demultiplexing for L2TPv3 feature introduces the ability to provide native IPv6 support by setting up a specialized IPv6 network and offloading IPv6 traffic from the IPv4 network. IPv6 traffic is transparently tunneled to the IPv6 network using L2TPv3 pseudowires without affecting the configuration of the CE routers. IPv4 traffic is routed as usual within the IPv4 network, maintaining the existing performance and reliability of the IPv4 network. Cisco IOS Release 12.0(33)S adds support for this feature over PPP links.
MPLS OAM Tools
Platform: Cisco 10720 router
Cisco IOS Release 12.0(33)S adds support for the following features:
•LSP Ping: tests LSP connectivity for IPv4 Label Distribution Protocol (LDP) prefixes, traffic engineering (TE) forwarding equivalence classes (FECs), and AToM FECs between two provider edge (PE) routers.
•LSP Traceroute: traces LSPs hop-by-hop for IPv4 LDP prefixes and TE tunnel FECs to localize faults in the network.
•AToM Virtual Circuit Connection Verification (VCCV): allows you to test the pseudowire (PW) section of an AToM virtual circuit (VC), providing end-to-end fault detection and diagnostics. (The AToM VCCV feature can be applied to EoMPLS connections configured on the Cisco 10720 Internet router.)
MPLS Traffic Engineering: BFD-Trigerred Fast Reroute Feature
Platform: Cisco 7200 series, Cisco 7500 series
The MPLS Traffic Engineering: BFD-trigerred Fast Reroute feature allows you to obtain link and node protection by using the Bidirectional Forwarding Detection (BFD) protocol to provide 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.
New Hardware and Software Features in Cisco IOS Release 12.0(32)S3 to Cisco IOS Release 12.0(32)S9
There are no new hardware or software features in Cisco IOS Release 12.0(32)S3 to Cisco IOS Release 12.0(32)S9.
New Hardware Features in Cisco IOS Release 12.0(32)S2
There are no new hardware features in Cisco IOS Release 12.0(32)S2.
New Software Features in Cisco IOS Release 12.0(32)S2
This section describes new and changed features in Cisco IOS Release 12.0(32)S2. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(32)S2. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Remark Precedence Feature
Platform: Cisco 12000 series
The hw-module slot 0 qos remark-precedence prec command has been introduced on the Cisco 12000 series router Engine 3 and Engine 5 line cards to support remarking non-important route processor generated traffic with a new precedence in Cisco IOS Release 12.0(32)S2.
For detailed information about this feature, see the L2/L3 QoS Computations and Remark Precedence for Cisco 12000 Series Router Multiservice Engine Line Cards document at the following URL:
Selective MVRF Download
Platform: Cisco 12000
The Selective MVRF Download feature allows Multicast Virtual Routing and Forwarding (MVRF) routing instances to be downloaded to line cards as needed instead of downloading to all line cards. The advantage is that this action saves line card memory by reducing the number of mroutes configured and lowers the use of the CPU by the line card.
This feature is set by default so the ip multicast command is modified with the addition of new keywords to bypass the feature if needed. The modified command is ip multicast mdfs download all. Two new commands show ip mds vrf vpn download interface slot and show ip mds vrf vpn download slot-list are added to monitor this feature.
Two show commands have been changed. For monitoring the MDFS Route Processor, use the show ip multicast command. For the MDFS line card, use the show ip mds vrf vrf_name summary command to display the multicast routes configured on a line card in the context of a VRF. This show command will display a flag indicating the feature was in effect on the line card.
New Hardware Features in Cisco IOS Release 12.0(32)S1
There are no new hardware features in Cisco IOS Release 12.0(32)S1.
New Software Features in Cisco IOS Release 12.0(32)S1
This section describes new and changed features in Cisco IOS Release 12.0(32)S1. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(32)S1. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
ATM CBR and VBR-rt Support
Platforms: Cisco 7200 series, Cisco 7500 series
The ATM CBR and VBR-rt Support feature is now available on the PA-A3-8E1IMA and PA-A3-8T1IMA port adapters. For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
cbrvb12s.htmNew Hardware Features in Cisco IOS Release 12.0(32)S
This section describes new and changed features in Cisco IOS Release 12.0(32)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(32)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
1-Port Enhanced ATM Port Adapter with Support for 8000 VCs
Platforms: Cisco 7200 series, Cisco 7500 series
Cisco IOS Release 12.0(32)S adds support for the PA-A6 port adapters and support for 8000 virtual circuits (VCs) on the PA-A6 port adapters. The PA-A6 is a series of single-width, single-port, ATM port adapters. With advanced ATM features, the PA-A6 port adapters supports broadband aggregation, WAN aggregation, and campus/MAN aggregation. The following PA-A6 port adapters are supported:
•PA-A6-OC3MM: 1-port ATM OC-3c/STM-1 multimode port adapter, enhanced
•PA-A6-OC3SMI: 1-port ATM OC-3c/STM-1 single-mode (IR) port adapter, enhanced
•PA-A6-OC3SML: 1-port ATM OC-3c/STM-1 single-mode (LR) port adapter, enhanced
•PA-A6-T3: 1-port ATM DS3 port adapter, enhanced
•PA-A6-E3: 1-port ATM E3 port adapter, enhanced
For detailed information about these products, see the PA-A6 Port Adapter Installation and Configuration document:
http://www.cisco.com/univercd/cc/td/doc/product/core/7206/port_adp/atm_-pas/pa-a6/
index.htmCWDM Pluggable Optics Support for the Cisco 12000 Series
Platform: Cisco 12000 series
For detailed information about these products, see the following documents:
•Cisco CWDM GBIC and SFP Solution Data Sheet:
http://www.cisco.com/en/US/products/hw/modules/ps5455/
products_data_sheet09186a00801a557c.html•Ethernet Line Card Installation and Configuration document:
http://www.cisco.com/en/US/products/hw/modules/ps2710/
prod_module_install_config_guide09186a00801f4dc7.htmlShared Port Adapters (SPAs) and SPA Interface Processors (SIPS) for the Cisco 12000 Series
Platform: Cisco 12000 series
Cisco IOS Release 12.0(32)S introduces the following Shared Port Adapter (SPA) Interface Processors (SIPs):
•12000-SIP-401: 12000 Series SPA Interface Processor-401
(also referred to as 2.5G Multiservice Engine SPA Interface Processor)•12000-SIP-501: 12000 Series SPA Interface Processor-501
(also referred to as 5G Multiservice Engine SPA Interface Processor)•12000-SIP-601: 12000 Series SPA Interface Processor-601
(also referred to as 10G Multiservice Engine SPA Interface Processor)These SIPs support the following types of SPAs:
•2 single-width, double-height, or
•2 single-width, single-height, or
•1 dual-width, double-height
Cisco IOS Release 12.0(32)S introduces the following SPAs:
•SPA-1XCHSTM1/OC3: 1-port channelized OC-3/STM-1 Engine 5 SPA
•SPA-2X1GE: 2-port Gigabit Ethernet Engine 5 SPA
•SPA-8XCHT1/E1: 8-port Channelized T1/E1 Engine 5 SPA
•SPA-8XFE: 8-port Fast Ethernet Engine 5 SPA
For detailed information about these products, see the Cisco 12000 series SIP and SPA installation and configuration guides at the following location:
•Cisco 12000 Series Routers SIP and SPA Hardware Installation Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_hw/
index.htm•Cisco 12000 Series Router SIP and SPA Software Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_swcs/
index.htmNew Software Features in Cisco IOS Release 12.0(32)S
This section describes new and changed features in Cisco IOS Release 12.0(32)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(32)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
ACL IP Options Selective Drop
Platform: Cisco 10720
For detailed information about this feature (also referred to as IP Options Selective Drop), see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/
sel_drop.htmAny Transport over MPLS (AToM)
Cisco IOS Release 12.0(32)S supports the following Any Transport over MPLS (AToM) features on Engine 5 line cards.
Any Transport over MPLS (AToM) Sequencing Support
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios12/120newft/120limit/120s/120s32/
fsatom32.fmAny Transport over MPLS (AToM): Layer 2 QoS (Quality of Service)
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
12sl2qos.fmAny Transport over MPLS (AToM): Ethernet over MPLS (EoMPLS)
Platform: Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/
fsatom28.htmAny Transport over MPLS (AToM): Frame Relay over MPLS (FRoMPLS)
Platform: Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/
fsatom28.htmAny Transport over MPLS (AToM): HDLC over MPLS (HDLCoMPLS)
Platform: Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/
fsatom28.htmAny Transport over MPLS (AToM): PPP over MPLS (PPPoMPLS)
Platform: Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/
fsatom28.htmAny Transport over MPLS (AToM): VC Independence
Platform: Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/
fsatom28.htmAutoInstall Support on Dual Mode IEEE 802.17 RPR/SRP Uplink Cards
Platform: Cisco 10720
For information about this feature, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/
10720.htmBidirectional Forwarding Detection
Platform: Cisco 10720, Cisco 12000 series
For the Cisco 12000 series, Cisco IOS Release 12.0(32)S introduces support for Bidirectional Forwarding Detection (BFD) on shared port adaptors (SPAs) and SPA Interface Processors (SIPs).
For detailed information about this feature for both the Cisco 10720 and the Cisco 12000 series, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122sx/
12218sxe/fs_bfd.htmFor information about this feature in relation to the Cisco 10720, see the "Bidirectional Forwarding Detection" section in the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/
10720.htmCisco 7200 Series Routers Boot Images Information
Platforms: Cisco 7200 series
The c7200-mboot-mz image contains support for a small, specific set of port adapters and older I/O controllers. The c7200-mboot-mz image is small enough to fit on older I/O controller Flash (bootflash) memory.
For detailed information about this feature, see the Cisco 7200 Series Routers Boot Images Information document at the following URL:
http://www.cisco.com/en/US/products/hw/routers/ps341/prod_installation_guide09186a00805e7d4d.html
Configuring 8 Queues per Interface on the 1-port Channelized OC12/STM-1 to DS1/E1 Line Card
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
8que_if.htmControl Plane Policing (CPP)
Platform: Cisco 10720
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s18/
gtrtlimt.htmDHCP-PD/DHCPv6
Platform: Cisco 12000 series
For more information on the DHCP-PD/DHCPv6 feature for Cisco 12000 series 10G ISE line cards, see the following documents:
•Start Here: Cisco IOS Software Release Specifics for IPv6 Features
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/ftipv6s.htm
•Implementing Basic Connectivity for IPv6
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_bconn.htm
Frame Relay Support on Engine 5 Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the Cisco 12000 Series Router SIP and SPA Software Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_swcs/index.htm
High Priority Traffic Jitter Improvement for Cisco 12000 Series Router, Cisco 12000 SIP-400, Shared Port Adapters
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
jitter.htmIP Receive ACL
Platform: Cisco 12000 series
This feature was enhanced to filter IPv6 traffic on the Cisco 12000 series. For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/
ft_ipacl.htmIPv6 QoS Enhancements for 12000 Series Router, ISE Line Cards, and SPAs
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
ipv6qos.htmL2/L3 QoS Computations for Cisco 12000 Series Router Engine 5 Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
l2l3comp.htmL2VPN Interworking Features
Platform: Cisco 12000 series
Cisco IOS Release 12.0(32)S supports the following Layer 2 VPN (L2VPN) features:
•L2VPN Interworking: Ethernet to VLAN Interworking
•L2VPN Interworking: Ethernet VLAN to ATM AAL5
•L2VPN Interworking: Ethernet VLAN to Frame Relay
•L2VPN Interworking: Frame Relay to ATM AAL5
For detailed information about these features, see the L2VPN Interworking document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
fsinterw.fmLink Bundling on Cisco 12000 Series Routers
Platform: Cisco 12000 series
This feature was enhanced. For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/
lnkbndl.htmLink Fragmentation and Interleaving for Multilink PPP
Platform: Cisco 12000 series
For detailed information about this feature, see the Cisco 12000 Series Router SIP and SPA Software Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_swcs/index.htm
MPLS VPN over IP Tunnels
Platform: Cisco 10720
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/
csgl3vpn.htmMulticast Egress QoS Support on Cisco 12000 Series Router ISE SPAs
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
mcastqos.htmMultilink Frame Relay and Multilink PPP Support on Channelized SPAs on Engine 5 Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the Cisco 12000 Series Router SIP and SPA Software Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_swcs/1232s/
index.htmMultilink Frame Relay over L2TPv3/AToM
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/
fsmfrl2.htmOSPF RFC 3623 Graceful Restart
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
gr_ospf.htmOutput Aggregate NetFlow
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
oaggnf.htmPower Management
Platform: Cisco 12000 series
In Cisco IOS Release 12.0(31)S, the Power Management feature calculates the maximum possible power consumption of all chassis components and generates warning messages if the calculation indicates the possibility of an underpowered condition. In Cisco IOS Release 12.0(32)S, if the calculation indicates the possibility of an underpowered condition, the last card added will not power up. For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
12spower.htmProtocol-Independent MAC ACL Filtering
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
macacl.htmPseudowire Emulation Edge-to-Edge MIBs for Ethernet Services
Platform: Cisco 10720
For detailed information about this feature, see the "Pseudowire Emulation Edge-to-Edge MIBs" section in the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/
10720.htmQoS: CBQoS MIB Index Enhancements
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124newft/124t/124t4/ht_cbqos.htm
QoS Ingress Hierarchical Policing for Cisco 12000 Series Router Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
hierpol.htmTofab QoS Queues per Egress ISE SPA or ISE Line Card on Cisco 12000 Series Routers
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
tofabqos.htmUnified QoS-Locally Generated Packet Prioritization on Cisco 12000 Series Router ISE Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
unif_qos.htmVirtual Private LAN Service over IP or MPLS on Cisco 12000 Series Router Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s32/
vpls_qos.htmNew Hardware and Software Features in Cisco IOS Release 12.0(31)S4 to Cisco IOS Release 12.0(31)S4
There are no new hardware or software features in Cisco IOS Release 12.0(31)S4 to Cisco IOS Release 12.0(31)S6.
New Hardware Features in Cisco IOS Release 12.0(31)S3
There are no new hardware features in Cisco IOS Release 12.0(31)S3.
New Software Features in Cisco IOS Release 12.0(31)S3
This section describes new and changed features in Cisco IOS Release 12.0(31)S3. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(31)S3. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Component Outage On-Line (COOL) Measurement
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
fscool12.htmIPv6 Provider Edge Router over MPLS (Cisco 6PE) Enhancement
Platform: Cisco 12000 series
On an IPv6-enabled provider edge (6PE) Cisco 12000 series router, when the edge-facing line card is an IP Services Engine (ISE) line card and when the core-facing line card is an Engine 4, Engine 4+, or Engine 5 line card, disposition performed on 6PE-labeled packets has been accelerated. The acceleration is possible because 6PE-label disposition is now performed in the hardware of the edge-facing ISE line card instead of in the CPU of the core-facing Engine 4, Engine 4+, or Engine 5 line card.
The acceleration applies only to IPv6 6PE-labeled packets. Aggregate 6PE label disposition has not been accelerated, and remains bound by the CPU forwarding performance of the core-facing Engine 4, Engine 4+, or Engine 5 line card.
Support for accelerated disposition on 6PE-labeled packets on Engine 4 and Engine 4+ line cards was introduced in Cisco IOS Release 12.0(28)S. Release 12.0(31)S3 adds support for accelerated disposition on 6PE-labeled packets over VLANs or subinterfaces on Engine 5 line cards.
No new or modified Cisco IOS software commands are introduced with this feature.
New Hardware Features in Cisco IOS Release 12.0(31)S2
This section describes new and changed features in Cisco IOS Release 12.0(31)S2. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(31)S2. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
1-Port Channelized OC-3/STM-1 Engine 5 SPA
Platform: Cisco 12000 series
Cisco IOS Release 12.0(31)S2 introduces the following Shared Port Adapter (SPA):
SPA-2XOC48c: 2-port OC48/STM16 POS SMLR Optics SPA
For detailed information about this product, see the Cisco 12000 series SIP and SPA installation and configuration guides at the following location:
•Cisco 12000 Series Routers SIP and SPA Hardware Installation Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_hw/
index.htm•Cisco 12000 Series Router SIP and SPA Software Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_swcs/
index.htmNew Software Features in Cisco IOS Release 12.0(31)S2
This section describes new and changed features in Cisco IOS Release 12.0(31)S2. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(31)S2. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Layer 2 Local Switching for Cisco 12000 Series IP Services Engine Line Cards
Platform: Cisco 12000 series
The Layer 2 Local Switching 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. Starting in Cisco IOS Release 12.0(31)S2, Layer 2 local switching is supported on customer-facing interfaces on IP Services Engine (ISE) line cards that are installed in a Cisco 12000 series Internet router and configured for a native L2TPv3 tunnel session or an L2TPv3 tunnel session using a tunnel server card.
Note Native L2TPv3 tunnel sessions on customer-facing ISE line cards can coexist with tunnel sessions that use a tunnel server card.
The ISE interface-to-interface switching combinations supported by the Layer 2 local switching feature are:
•ATM to ATM
•ATM to Ethernet
•ATM to Frame-Relay
•Ethernet to Ethernet VLAN
•Frame Relay to Frame Relay (including Multilink Frame Relay)
On an ISE customer-facing interface, the following types of same-port Layer 2 local switching are also supported:
•Same-Port Switching for ATM (PVC and PVP)
•Same-Port Switching for Ethernet VLAN
•Same-Port Switching for Frame Relay
For more information about this feature, see the Layer 2 Local Switching document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/
fslocal.htmLayer 2 Tunnel Protocol Version 3 for Cisco 12000 Series IP Services Engine Line Cards
Platform: Cisco 12000 series
The Layer 2 Tunnel Protocol Version 3 (L2TPv3) feature expands on Cisco support of the Layer 2 Tunnel Protocol (L2TP) to tunnel any Layer 2 payload over an IP core network using Layer 2 virtual private networks (VPNs). L2TPv3 simplifies the deployment of VPNs without requiring Multiprotocol Label Switching (MPLS) in the core network.
Starting in Cisco IOS Release 12.0(31)S2, L2TPv3 tunnel sessions (either native L2TPv3 or an L2TPv3 tunnel session that uses a tunnel server card) are supported on customer-facing interfaces on IP Services Engine (ISE) line cards that are installed in a Cisco 12000 series Internet router and configured for Layer 2 local switching.
Note Native L2TPv3 tunnel sessions on customer-facing ISE line cards can coexist with tunnel sessions that use a tunnel server card.
For more information about how to configure and use L2TPv3 tunneling for Layer 2 VPNs, including Layer 2 local switching support in an L2TPv3 tunnel session on an ISE line card, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
l2tpv31s.htmNew Hardware Features in Cisco IOS Release 12.0(31)S1
There are no new hardware features in Cisco IOS Release 12.0(31)S1.
New Software Features in Cisco IOS Release 12.0(31)S1
This section describes new and changed features in Cisco IOS Release 12.0(31)S1. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(31)S1. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
BGP Multipath Loadsharing for MPLS VPN over IP Tunnels for Cisco 12000 Series Engine 5 Line Cards
Platform: Cisco 12000 series
This release introduces BGP Multipath Load Sharing for MPLS VPN over IP Tunnels support on Engine 5 shared port adapters (SPAs) and SPA Interface Processors (SIPs) on the Cisco 12000 series. For details about this feature, see the Cisco documents at the following locations:
•MPLS VPNs over IP Tunnels
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
120s30/csgl 3vpn.htm•BGP Multipath Load Sharing for Both eBGP and iBGP in an MPLS-VPN
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122sx/
12218sxe/f sxeibmp.htmHierarchical Traffic Shaping for MPLS VPN over IP Tunnels
Platform: Cisco 12000 series
Detailed information about this feature will be available soon.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120sy/120sy32/
hiershap.htmNew Hardware Features in Cisco IOS Release 12.0(31)S
This section describes new and changed features in Cisco IOS Release 12.0(31)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(31)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Cisco 12810 and Cisco 12816 Internet Routers
Cisco IOS Release 12.0(31)S introduces support for the Cisco 12810 and Cisco 12816, both of which support 40-Gbps switch fabric. For detailed information about these platforms, see the Cisco documents at the following locations:
•For the Cisco 12810:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/cis12x10/index.htm
•For the Cisco 12816:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/cis12x16/index.htm
Shared Port Adapters (SPAs) and SPA Interface Processors (SIPS) for the Cisco 12000 Series
Platform: Cisco 12000 series
Cisco IOS Release 12.0(31)S introduces the following Shared Port Adapter (SPA) Interface Processors (SIPs):
•12000-SIP-400: 12000 Series SPA Interface Processor-400
(also referred to as 2.5G ISE SPA Interface Processor)This SIP supports the following types of SPAs:
–4 single-width, single-height
•12000-SIP-600: 12000 Series SPA Interface Processor-600
(also referred to as 10G Engine 5 SPA Interface Processor)This SIP supports the following types of SPAs:
–2 single-width, double-height, or
–2 single-width, single-height, or
–1 dual-width, double-height
Cisco IOS Release 12.0(31)S introduces the following SPAs:
•SPA-2XT3/E3: 2-Port T3/E3 Serial SPA
(also referred to as the 2-port clear channel T3/E3 ISE SPA)•SPA-4XT3/E3: 4-Port T3/E3 Serial SPA
(also referred to as the 4-port clear channel T3/E3 ISE SPA)•SPA-2XCT3/DS0: 2-Port Channelized T3 to DS0 SPA
(also referred to as the 2-port channelized T3/E3 ISE SPA)•SPA-4XCT3/DS0: 4-Port Channelized T3 to DS0 SPA
(also referred to as the 4-port channelized T3/E3 ISE SPA)•SPA-1XTENGE-XFP: 1-Port 10-Gigabit Ethernet Engine 5 SPA
•SPA-5X1GE: 5-Port Gigabit Ethernet Engine 5 SPA
•SPA-10X1GE: 10-Port Gigabit Ethernet Engine 5 SPA
•SPA-OC192POS-LR: 1-port OC192/STM64 POS/RPR SMLR Optics Engine 5 SPA
•SPA-OC192POS-XFP: 1-port OC192/STM64 POS/RPR XFP Optics Engine 5 SPA
For detailed information about these products, see the Cisco 12000 series SIP and SPA installation and configuration guides at the following location:
•Cisco 12000 Series Routers SIP and SPA Hardware Installation Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_hw/
index.htm•Cisco 12000 Series Router SIP and SPA Software Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_swcs/
index.htmNew Software Features in Cisco IOS Release 12.0(31)S
This section describes new and changed features in Cisco IOS Release 12.0(31)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(31)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
ATM CBR and VBR-rt Support
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
cbrvb12s.htmAToM Support on 2-Port and 4-Port Clear Channel T3/E3 SPAs
Platform: Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/
fsatom28.htmAToM Support on 2.5G ISE 2/4-Port Channelized T3/E3 SPAs
Platform: Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/
fsatom28.htmAToM VC Independence
Platform: Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/
fsatom28.htmBGP Route-Map Continue Support for Outbound Policy
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature, see the BGP Route-Map Continue document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
cs_brmcs.htmBidirectional Forwarding Detection (BFD) Standard Implementation
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
Building Integrated Timing Source (BITS)
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
12s_bits.htmExclusive Configuration Change Access and Access Session Locking
Platform: Cisco 12000 series
For detailed information about this feature, see the Exclusive Configuration Change Access (Configuration Lock) document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_14/
gt_exclu.htmIMA Dynamic Bandwidth
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
fsimadyb.htmInter-AS 10B Hybrid for MPLS VPN over IP Tunnels
Platform: Cisco 12000 series
Cisco 12000 series ISE line cards now support Inter-AS 10B Hybrid for MPLS VPN over IP Tunnels. This feature allows peering of two networks with different BGP autonomous systems when the core network is MPLS VPN over IP Tunnels.
For more information on the Inter-AS 10B Hybrid feature for MPLS VPN over IP Tunnels, see the following three feature modules:
•MPLS VPNs over IP Tunnels feature module
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
120s30/csgl3vpn.htm•MPLS VPN Interautonomous Systems Support feature module
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
120s24/fsias24.htm•MPLS VPN—Inter-AS—IPv4 BGP Label Distribution feature module
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
120s24/fsiasl24.htmIP Receive ACL
Platform: Cisco 10720
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/
ft_ipacl.htmIPv6 Multicast PxF Acceleration
Platform: Cisco 10720
For detailed information about this feature, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/
10720.htmL2VPN Pseudowire Redundancy
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
L2VPN Pseudowire Switching
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
fsstitch.htmL2TPv3 Native Tunneling on 4-port GE ISE Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
l2tpv31s.htmLayer 2 VPN (L2VPN): Syslog, SNMP Trap, and show Command Enhancements for AToM and L2TPv3
Platform: Cisco 12000 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
l2tpv31s.htmMPLS VPN Carrier Supporting Carrier over IP Tunnels
Platform: Cisco 12000 series
The Carrier Supporting Carrier for MPLS VPN over IP Tunnels feature is now supported on Cisco 12000 series ISE line cards. For detailed information about this feature, see the following documents:
•MPLS VPN—Carrier Supporting Carrier
•MPLS VPN—Carrier Supporting Carrier—IPv4 BGP Label Distribution
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
120s29/fscscleb.htmNative L2TPv3 Tunneling and MPLS VPN over IP Tunnels on Channelized E3 and T3 Shared Port Adaptors
Platform: Cisco 12000 series
For detailed information about these features, see the following documents:
•For support of native L2TPv3 tunneling on the channelized E3 and T3 Shared Port Adaptors, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
120s31/l2tpv31s.htm•For support of MPLS VPNs over IP tunnels on the channelized E3 and T3 Shared Port Adaptors, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
120s30/csgl3vpn.htmNative L2TPv3 Tunneling and MPLS VPN over IP Tunnels on Clear Channel E3 and T3 Shared Port Adaptors
Platform: Cisco 12000 series
For detailed information about these features, see the following documents:
•For support of native L2TPv3 tunneling on the clear channel E3 and T3 Shared Port Adaptors, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
120s31/l2tpv31s.htm•For support of MPLS VPNs over IP tunnels on the clear channel E3 and T3 Shared Port Adaptors, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
120s30/csgl3vpn.htmPower Management
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
Pseudowire Emulation Edge-to-Edge MIBs for Ethernet and Frame Relay Services
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
gspwe31s.htmQoS: Partial Support for Ingress Hierarchical Policing for the Cisco 12000 4-Port GE Line Card
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
12stetpo.htmReverse Path Forwarding—Source Exists Only
Platform: Cisco 10720
For detailed information about this feature, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/
10720.htmSingle Router APS
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
12ssraps.htmUnicast Reverse Path Forwarding for IPv6
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s31/
urpf_gsr.htmNew Hardware and Software Features in Cisco IOS Release 12.0(30)S1 to Cisco IOS Release 12.0(30)S5
There are no new hardware or software features in Cisco IOS Release 12.0(30)S1 to Cisco IOS Release 12.0(30)S5.
New Hardware Features in Cisco IOS Release 12.0(30)S
This section describes new and changed features in Cisco IOS Release 12.0(30)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(30)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
1-Port Packet over SONET OC3c/STM1 Port Adapter
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about the 1-port Packet over SONET OC3c/STM1 port adapter (PA-POS-1OC3), see the following documents:
•Cisco 1-Port OC-3/STM-1 Packet-Over-SONET Port Adapter data sheet:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/
products_data_sheet0900aecd80221d3d.html•PA-POS-1OC3 Single-Port Port Adapter Installation and Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/7301/73pa/73-son/6514_1oc/index.htm
Performance Route Processor 2 Enhancements
Platform: Cisco 12000 series
The Performance Route Processor 2 (PRP-2) now supports a 10/100/1000 Mbps Ethernet port and an optional 1-GB compact flash disk. For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/otherdoc/13302prp.htm
New Software Features in Cisco IOS Release 12.0(30)S
This section describes new and changed features in Cisco IOS Release 12.0(30)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(30)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Any Transport over MPLS (AToM) Sequencing Support
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/fsat om30.htm
ATM VC Class Support
Platform: Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fsat om28.htm
Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service)
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/12sl 2qos.htm
AToM: Remote Ethernet Port Shutdown
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/12s_ resd.htm
Back-to-Back VRF Support for MPLS-VPNs over IP Tunnels
Platform: Cisco 12000 series
The Back-to-back VRF support for the MPLS-VPNs over IP Tunnels feature enables provider edge (PE) routers from separate service provider networks to exchange VRF routes that are sourced from the other provider network. In this configuration scenario, the edge router in the source provider network functions as the PE router, and the edge router in the receiving provider network functions as the customer edge (CE) router. The routing protocols supported in the PE to CE Virtual Private Network (VPN) configuration are eBGP, EIGRP, OSPF, RIP, and static routing.
Distributed Control Plane Policing
Platform: Cisco 12000 series
For detailed information about this feature, see the Control Plane Policing document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s18/gtrtlimt.ht m
Disabling the RP Layer 3 Cache
Platform: Cisco 12000 series
For detailed information about this feature, see the Performance Route Processor (PRP) Software Configuration document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/prp. htm
IEEE 802.17 RPR Enhancements
Platform: Cisco 10720
For detailed information about the enhancements to the IEEE 802.17 RPR feature, see the IEEE 802.17 Resilient Packet Ring Feature Guide:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/rprs wg.htm
For additional information, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/107 20.htm
Inter-AS Support for Multicast VPN
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
The Inter-AS Support for Multicast VPN feature provides support for multiple autonomous systems (ASs) within a domain and support for VPNs that span multiple provider networks.
L2TPv3 Digest Secret Graceful Switchover
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/l2tp v30s.htm
Layer 2 Local Switching
Cisco IOS Release 12.0(30)S supports the following Layer 2 local switching features:
•Layer 2 Local Switching—ATM to ATM
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series•Layer 2 Local Switching—ATM to ATM with Cell Packing
Platform: Cisco 12000 series•Layer 2 Local Switching—Same-Port Switching for ATM
Platform: Cisco 12000 series•Layer 2 Local Switching—Same-Port Switching for Ethernet VLAN
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series•Layer 2 Local Switching—Same-Port Switching for Frame Relay
Platforms: Cisco 7200 series, Cisco 7500 seriesFor detailed information about these features, see the Layer 2 Local Switching document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fslo cal.htm
L2VPN Interworking
Platform: Cisco 12000 series
•L2VPN Interworking: Ethernet to VLAN Interworking
•L2VPN Interworking: Ethernet VLAN to ATM AAL5 Interworking
•L2VPN Interworking: Ethernet VLAN to Frame Relay Interworking
•L2VPN Interworking: Frame Relay to ATM AAL5 Interworking
For detailed information about these features, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s26/fsin terw.htm
Link Protection for GE Interface
Platform: Cisco 12000 series
For detailed information about this feature, see the MPLS Traffic Engineering (TE): Link and Node Protection with RSVP Hellos Support document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/fsln ph30.htm
Loopback Mode Detection Through OAM
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/lmd _oam.htm
Maximum Mask Aggregate Output NetFlow
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
MPLS CoS Transparency Explicit Null Enhancements
Platform: Cisco 12000 series
MPLS Pipe Mode CoS Transparency enables an Internet Service Provider (ISP) to offer differentiated services to its customers and still preserve the internal Quality of Service (QoS) policies of its customers.
The explicit null enhancements for Cisco 12000 series Engine 3 line cards include the following:
•Explicit null labels over MPLS VPN labels in the fast path
•Explicit null labels over MPLS VPN deaggregate labels in the fast path
•Explicit null labels over AToM labels in the fast path
•Explicit null labels over MPLS VPN IPv6 labels in the fast path
MPLS Label Distribution MIB: MPLS LDP Trap Enhancement
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the MPLS Label Distribution Protocol MIB document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ldpmib13.htm
MPLS LDP Autoconfiguration
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/fsld paut.htm
MPLS LDP IGP Synchronization
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/fsld psyn.htm
MPLS LDP Session Protection
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/fsse spro.htm
MPLS Traffic Engineering (TE)—Fast Tunnel Interface Down Detection
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the MPLS Traffic Engineering (TE): Link and Node Protection with RSVP Hellos Support document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/fsln ph30.htm
MPLS Traffic Engineering (TE)—Path Protection
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/gspa thpr.htm
MPLS VPN-MIB Support: MPLS VPN Trap Enhancement
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the MPLS VPN—MIB Support document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/fsvn mb25.htm
MPLS VPNs over IP Tunnels
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/csgl 3vpn.htm
Multilink Frame Relay (FRF.16.1)
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fs_mfr.htm
Multi Router APS on ISE ATM Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/12sm raps.htm
Native L2TPv3 Tunneling
Platform: Cisco 12000 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/l2tp v30s.htm
OAM Segment Endpoint
Platforms: Cisco 7200 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/12so amse.htm
On-Board Failure Logging
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/12so bfl.htm
OSPF Sham-Link MIB Support
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
PIM RPF Vector
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
Pseudowire Emulation Edge-to-Edge MIBs for Ethernet and Frame Relay Services
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/gspw e3fr.htm
PXF Accelerated IPv6 Quality of Service
Platform: Cisco 10720
For detailed information about this feature, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/107 20.htm
QoS: Match ATM OAM
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/gsat moam.htm
QoS: ATM CLP Queue-Limit
Platform: Cisco 12000 series
For detailed information about this feature (also referred to as QoS: ATM CLP-Based Queue Limit), see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/12sq atcl.htm
SNMP over IPv6
Platform: Cisco 12000 series
For detailed information about this feature, see the "Managing Cisco IOS Applications over IPv6" chapter in the Cisco IOS IPv6 Configuration Library:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_mgev6.htm
VLAN ID Rewrite
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fsat om28.htm
New Hardware and Software Features in Cisco IOS Release 12.0(29)S1
There are no new hardware or software features in Cisco IOS Release 12.0(29)S1.
New Hardware Features in Cisco IOS Release 12.0(29)S
This section describes new and changed features in Cisco IOS Release 12.0(29)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(29)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Note Cisco IOS Release 12.0(29)S does not support the Cisco 10000 series edge services routers and the Cisco 12000 series Internet routers.
Dual-Mode IEEE 802.17 RPR/SRP Uplink Module
Platform: Cisco 10720
For information about IEEE 802.17 RPR/SRP support via the new Dual-Mode IEEE 802.17 RPR/SRP uplink module, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/107 20.htm
New Software Features in Cisco IOS Release 12.0(29)S
This section describes new and changed features in Cisco IOS Release 12.0(29)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(29)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Note Cisco IOS Release 12.0(29)S does not support the Cisco 10000 series edge services routers and the Cisco 12000 series Internet routers.
Any Transport over MPLS (AToM) Sequencing Support
Platform: Cisco 7200 series
For detailed information about this feature, see the following document:
ATM Cell Packing over L2TPv3
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/l2tp v29s.htm
ATM Port Mode Cell Relay over L2TPv3
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/l2tp v29s.htm
ATM PVC Bundle Enhancement - MPLS-EXP Based PVC Selection
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/12sa tmvc.htm
AToM Graceful Restart
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/fsgr atom.htm
BGP Multicast IAS VPN
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/cs_b miav.htm
BGP Support for Fast Peering Session Deactivation
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/cs_b sfda.htm
BGP Support for IP Prefix Import from Global Table into a VRF Table
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_14/gt_bgivt.htm
BGP Support for Next-Hop Address Tracking
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_14/gt_bnht.htm
Control Plane Policing
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s18/gtrtlimt.ht m
EIGRP Prefix Limit Support
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/cs_e pls.htm
IEEE 802.17 RPR
Platform: Cisco 10720
For detailed information about this feature, see the IEEE 802.17 Resilient Packet Ring Feature Guide:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/rprs wg.htm
For additional information, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/107 20.htm
Enabling OSPFv2 on an Interface Using the ip ospf area Command
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10720
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/ospf area.htm
IS-IS Support for an IS-IS Instance per VRF for IP
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/vrf_ isis.htm
L2TPv3 Control Message Hashing
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/l2tp v29s.htm
L2TPv3 Control Message Rate Limiting
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/l2tp v29s.htm
MPLS LDP Graceful Restart
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/fsgr 29s.htm
MPLS Traffic Engineering - AutoTunnel Mesh Groups
Platforms: Cisco 7200 series, Cisco 7500 series
This feature now supports Interior Gateway Protocol (IGP) flooding of AutoTunnel mesh groups. For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/gsam g2.htm
MPLS Traffic Engineering - Class-Based Tunnel Selection
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/gscb ts.htm
MPLS Traffic Engineering - Inter-AS TE
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/gsin tast.htm
MPLS Traffic Engineering - RSVP Graceful Restart
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/gsrs vpgr.htm
MPLS Traffic Engineering - RSVP Hello State Timer
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/gsrs vpht.htm
MPLS Traffic Engineering: Shared Risk Link Groups (SRLG)
Platforms: Cisco 7200 series, Cisco 7500 series
Support for OSPF was added to this feature. For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/fs29 srlg.htm
MPLS VPN - Loadbalancing Support for Inter-AS and CSC VPNs
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following three documents:
•MPLS VPN—Carrier Supporting Carrier—IPv4 BGP Label Distribution:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29 /fscscleb.htm
•MPLS VPN—Inter-AS—IPv4 BGP Label Distribution:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29 /fsiasleb.htm
•MPLS VPN—Interautonomous System Support:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29 /fsiaseb.htm
Multicast Fast Switching Performance Improvement
Platform: Cisco 7200 series
The Multicast Fast Switching Performance Improvement feature provides improvement of up to 100 percent of the existing multicast path packet throughput. This feature targets software forwarding-based platforms for IPv4 multicast only.
Multicast VPN MIB
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/mcv pnmib.htm
N*DS0 BERT Support on PA-MC-8TE1+
Platforms: Cisco 7200 series, Cisco 7500 series
The N*DS0 bit error rate tester (BERT) capability allows BERT to run on a per channel-group/time-slot basis at a specified speed. PA-MC-8TE1+ is a single-width 8-port T1/E1 multichannel port adapter for the Cisco 7200 and Cisco 7500 series. Prior to this feature, BERT on the PA-MC-8TE1+ port adapter was enabled on all the channel groups/time slots.
New keywords have been added to the bert pattern interval command. Use the new timeslots and speed keywords with their associated arguments to specify the channel group/time slot and speed.
[no] bert pattern pattern interval time timeslots slot-number speed speed
The slot-number argument is in the range from 1 to 24 for a T1 line, and in the range from 1 to 31 for an E1 line. The speed argument can be either 56 kbps or 64 kbps, and the default is 64 kbps.
The show controllers e1 command and the show controllers t1 command will include time-slot and speed information for BERT only if either of the time-slot or speed arguments is not set to the default.
Protocol Demultiplexing for L2TPv3
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/l2tp v29s.htm
Pseudowire Emulation Edge-to-Edge MIBs for Ethernet Services
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s29/gspw e3mb.htm
Random Sampled NetFlow
Platform: Cisco 10720
For detailed information about this feature, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/
10720.htmNew Hardware and Software Features in Cisco IOS Release 12.0(28)S1 to Cisco IOS Release 12.0(28)S6
There are no new hardware or software features in Cisco IOS Release 12.0(28)S1 to Cisco IOS Release 12.0(32)S6.
New Hardware Features in Cisco IOS Release 12.0(28)S
This section describes new and changed features in Cisco IOS Release 12.0(28)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(28)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
NPE-G1
Platform: Cisco 7200 VXRrouters
The NPE-G1 is the first network processing engine for the Cisco 7200 VXR routers to provide the functionality of both a network processing engine and an I/O controller. If used without an I/O controller, an I/O blank panel must be in place.
While its design provides I/O controller functionality, it can also work with any I/O controller supported in the Cisco 7200 VXR routers. When installed with an I/O controller, the NPE-G1provides the primary input/out functionality; that is, the NPE-G1 input/out functionality enhances that of the existing I/O controller.
The NPE-G1 maintains and executes the system management functions for the Cisco 7200 VXR routers and also holds the system memory and environmental monitoring functions.
The NPE-G1 consists of one board with multiple interfaces. It is keyed so that it can be used only in the Cisco 7200 VXR routers.
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/core/7206/fru/npense/4448o5.htm
New Software Features in Cisco IOS Release 12.0(28)S
This section describes new and changed features in Cisco IOS Release 12.0(28)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(28)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
ATM AAL5 over L2TPv3
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature (also referred to as "ATM AAL5 SDU Mode over L2TPv3" and "OAM Cell Support"), see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/l2tp v328.htm
ATM Conditional Debug Support
Platform: Cisco 7200 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sa tmdb.htm
ATM OAM AIS-RDI Monitoring
Platform: Cisco 10000 series, Cisco 10720
The ATM OAM AIS-RDI Monitoring feature extends the existing ATM virtual circuit Operation, Administration, and Maintenance (OAM) functionality to include monitoring of the Alarm Indication Signal-Remote Defect Indication (AIS-RDI). Once the feature is enabled, OAM AIS-RDI is monitored on the virtual circuit (VC).
If the number of consecutive OAM AIS-RDI cells received is greater than a configurable number, the VC is brought down. The VC is brought up when there are no OAM AIS-RDI cells received within a configurable interval.
Use the oam ais-rdi command to specify the number of consecutive OAM AIS-RDI cells that are to be received before the permanent virtual circuit (PVC) is brought down. The no form of the command returns the OAM AIS-RDI function to the default configuration.
[no] oam ais-rdi [down-count [up-count]]
The down-count argument is the number of consecutive OAM AIS-RDI cells received. The range is from 1 to 60, and the default is 1 OAM AIS-RDI cell.
The down-count argument is the number of consecutive OAM AIS-RDI cells received. The range is from 1 to 60, and the default is 1 OAM AIS-RDI cell.
The up-count argument is the number of seconds that are allowed to elapse with no OAM AIS-RDI cells received. The range is from 3 to 60 seconds, and the default is 3.
ATM VC Bundles to MPLS VRF
Platform: Cisco 12000 series
The ATM VC Bundles to MPLS VRF feature is an extension of the IP-to-ATM Class of Service feature suite. The IP to ATM Class of Service feature suite, using virtual circuit (VC) support and bundle management, maps quality of service (QoS) characteristics between IP and ATM. It provides customers who have multiple VCs (with varying qualities of service to the same destination) with the ability to build a QoS differentiated network.
The ATM VC Bundles to MPLS VRF feature enables use Multiprotocol Label Switching (MPLS) VPN routing and forwarding (VRF) as an additional selection criteria for packet forwarding. When a provider edge device learns an IP prefix from a customer edge device, it will assign a label to this route. All traffic with that prefix will now be mapped to this VPN label. This works with ATM bundles because the IP prefix associated with the bundle is used to create the VPN label. VPN forwarding takes place just as it does for nonbundled interfaces. The only difference is at the PE, when it switches to the bundle interface in the MPLS-to-IP path. At that point it uses the different VCs for the different precedence traffic as listed in its member adjacency table.
To enable ATM VC bundles to MPLS VRF, use the ip vrf command. The following example creates the VPN bundle on interface ATM0.35:
interface ATM0.35 point-to-point
ip address 10.10.10.10 255.255.255.252
ip vrf forwarding bundle_vpn
bundle vipnet
encapsulation aal5snap
oam-bundle manage 5
pvc-bundle 0/36
vbr-nrt 512 300
service-policy output data
precedence other
pvc-bundle 0/35
cbr 171
service-policy output voice
precedence 5
ATM VC Single Cell Relay over L2TPv3
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the "ATM VCC Cell Relay Mode" section in the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/l2tp v328.htm
AToM VC Mode Single Cell Relay Support for PA-A3-OC12 PA
Platform: Cisco 7500 series
The AToM VC Mode Single Cell Relay feature (also referred to as ATM Single Cell Relay: VC Mode) is now supported on the PA-A3-OC12 port adapter. For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fsat om28.htm
CNS Interactive CLI
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series
Network management applications can use Cisco Networking Services (CNS) agents to manage network routers. The CNS exec agent provides the capability to send commands to a router from a programmable source. The CNS Interactive CLI feature introduces a new XML interface that allows you to send interactive commands to a router, such as commands that generate prompts for user input. A benefit of this feature is that interactive commands can be aborted before they have been fully processed. For example, for commands that generate a significant amount of output, the XML interface can be customized to limit the size of the output or the length of time allowed for the output to accumulate. The capability to use a programmable interface to abort a command before its normal termination (similar to manually aborting a command) can greatly increase the efficiency of diagnostic applications that might use this functionality. The new XML interface also allows for multiple commands to be processed in a single session. The response for each command is packaged together and sent in a single response event.
Distributed ATM OAM Support (dOAM)
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
Frame Relay Scalability Conditional Debug Support
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fmc onde.htm
FRF.1.2 Annex A support
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 12000 series
The FRF.1.2 Annex A Support feature is also known as Local Management Interface (LMI) segmentation and supports an enhancement to the Frame Relay LMI protocol where LMI full status messages are segmented because MTU constraints or large numbers of permanent virtual circuits (PVCs). This feature is useful when the MTU size cannot be increased but is insufficient to accommodate the large number of PVCs on the link. During Frame Relay internetworking with other Layer 2 protocols, the MTUs on each interface must match. In software without the FRF.1.2 Annex A Support feature, users cannot change the MTU size on the Frame Relay side and place all the PVC data into one LMI packet. With the FRF.1.2 Annex A Support functionality, this problem is solved.
The FRF.1.2 Annex A standard adds a new message type "Full status continued" to an LMI packet. When a DCE determines that it cannot fit all PVCs into one packet (enforced by the MTU size), the message type is set to "Full status continued." The DTE responds to "Full status continued" messages sent to this packet immediately instead of waiting for the T391 timer to expire. The DCE sends the remaining PVCs in one or more "Full status continued" messages until all the remaining PVCs can fit into one message. At this point, a normal "Full status" message is sent.
If the DTE receives a "Full status" or "Full status continued" STATUS message in response to a "Full status continued" STATUS ENQUIRY message, this exchange indicates a lower-valued data-link connection identifier (DLCI) than the previous "Full status continued" STATUS message and is considered to be an error event and PVC information elements (IEs) will not be processed. The next time the T391 timer expires, the "Full status" STATUS ENQUIRY procedure is reinitiated.
This feature follows the FRF1.2 implement agreement [1] and allows the Cisco IOS software to be compliant with the FRF1.2 standard. The implementation is platform-independent and applies to all platforms running Cisco IOS software that support Frame Relay. This feature interoperates only with existing Cisco IOS software releases where all PVCs can be reported in one packet. A router running the new functionality must be able to interoperate with routers running existing Cisco IOS software releases and with routers that support the new functionality using the continuation status request and reply frames. Only LMI types Q.933A and ANSI support the FRF.1.2 Annex A standard.
You can track "Full status continued" packets using the debug frame-relay lmi privileged EXEC command. An extra field, 04, has been added to the display output. The following example indicates where in the report to look for this field (text in bold for purpose of example):
17:42:39: Serial1(out): StEnq, myseq 126, yourseen 125, DTE up
17:42:39: datagramstart = 0x40058DA4, datagramsize = 13
17:42:39: FR encap = 0x00010308
17:42:39: 00 75 51 01
04 53 02 7E 7DThe string segment "active/inactive" in the show interface commands indicates whether the FRF.1.2 Annex A standard is triggered. The report indicates active when routers receive the "Full status continued" message; otherwise, the report indicates inactive.
Hardware CEF Resiliency on Cisco 12000 Series Engine 2 and ISE Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the Cisco Express Forwarding document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s15/cefc on.htm
IPv6 BSR
Platform: Cisco 12000 series
For detailed information about this feature, see the Implementing IPv6 Multicast document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_mcast.htm
L2TPv3 Distributed Sequencing
Platform: Cisco 7500 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/l2tp v328.htm
L2TPv3 Support for PA-A3-8T1IMA PA and PA-A3-8E1IMA Port Adapters
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the Layer 2 Tunnel Protocol Version 3 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/l2tp328.htm
Layer 2 Protocol Tunneling
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/l2pt .htm
Low Latency Queueing with Priority Percentage Support
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sl lqpc.htm
MPLS COS Multi-VC Mode
Platform: Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/multiVC.htm
MPLS Traffic Engineering: Shared Risk Link Groups (SRLG)
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fssr lgis.htm
MPLS VPNs over IP Tunnels
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fssr lgis.htm
Multilink Frame Relay over L2TPv3/AToM
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fsm frl2.htm
Multilink Frame Relay Stateful Switchover
Platform: Cisco 12000 series
For detailed information about this feature, see the Stateful Switchover document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s20/fssso20s.h tm
Packet Classification Using the Frame Relay DLCI Number
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sd lci.htm
PIM Dense Mode Fallback Prevention in a Network Following RP Information Loss
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_4/gtautorp.htm
Policy Based Routing: Recursive Next Hop
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature (also referred to as PBR Recursive Next Hop), see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12s_ pbr.htm
Port Mode Cell Relay Support
Platforms: Cisco 7200 series, Cisco 7500 series
The Port Mode Cell Relay Support feature consists of the following two features:
•Port Mode Cell Relay Support for PA-A3-8T1 IMA PA and PA-A3-8E1 IMA PA
•Port Mode Cell Relay Support for PA-A3-T3, PA-A3-E3, and PA-A3-OC3 PAs
For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fsat om28.htm
PPP/MLP MRRU Negotiation Configuration
Platform: Cisco 7200 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_7/gtmpmrru.htm
Quality of Service (QoS) Features
QoS for IPv6
Platform: Cisco 12000 series
Starting in Cisco IOS Release 12.0(28)S, the following quality of service (QoS) features are supported in IP version 6 (IPv6) environments on IP Service Engine (ISE) line cards:
•Packet classification
•Traffic shaping
•Traffic policing
•Packet marking/remarking
•Queueing
•WRED-based drop
Note QoS policy propagation through the Border Gateway Protocol (QPPB) is not supported.
These IPv6 QoS features are supported only in hardware-based fast-path forwarding on ISE line cards. IPv6 QoS is not supported in slow-path forwarding.
IPv6 QoS is not supported on the following ISE line cards:
•1-port channelized OC-12/STM-4 (DS1/E1)
•2-port OC-12/STM-4 DPT
•4-port OC-12/STM-4 ATM
All of the QoS features available for IPv6 environments are managed from the modular QoS CLI (MQC). The MQC is a command-line interface that allows you to define traffic classes, create and configure traffic policies (policy maps), and then attach those traffic policies to interfaces. For detailed information about how to use the MQC, see the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.3, at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/qos_vcg.htm
In addition to the existing MQC commands supported on the Cisco 12000 series Internet router, the following new and modified commands are also supported on ISE line cards in class-map configuration mode:
•match protocol {ip | ipv6}
Specifies whether the IPv4 or the IPv6 protocol is to be used as match criteria for a traffic class. If you do not use the match protocol command, the traffic class matches both IPv4 and IPv6 packets.
•match access-group name ipv6-access-group
Specifies the name of an IPv6 access list against whose contents packets are checked to determine if they belong to the traffic class.
•match [ip] dscp dscp-value
match [ip] precedence precedence-valueSpecifies a differentiated services code point (DSCP) or IP precedence value to be used as match criteria to classify packets in a traffic class.
If you specify the ip keyword, the IP precedence or DSCP value is used to match only IPv4 packets in a traffic class. If you do not specify the ip keyword, the IP precedence or DSCP value is used to match both IPv4 and IPv6 packets.
Note The IP DSCP value is the first six bits in the ToS byte, while the IP precedence value is the first three bits in the ToS value. The IP precedence value is actually part of the IP DSCP value. Therefore, both values cannot be matched simultaneously. If both values are set simultaneously, the packet is matched with the IP DSCP value.
The following modified command is supported on ISE line cards in policy-map configuration mode:
•set [ip] dscp dscp-value
set [ip] precedence precedence-valueSets the DSCP or IP precedence value in packet headers for a specified traffic class. Once the DSCP or IP precedence bits are set, other QoS services such as Weighted Random Early Detection (WRED) then operate on the bit settings.
The ip keyword is optional and supports backward compatibility with the IPv4 QoS commands. The set [ip] dscp and set [ip] precedence commands apply to both IPv4 and IPv6 traffic whether you enter the ip keyword or not.
Note The set precedence command cannot be used with the set dscp command to mark the same packet. The two values, DSCP and precedence, are mutually exclusive. A packet can have one value or the other, but not both.
For information about how to configure and use IPv6 QoS features, see "Implementing QoS for IPv6 for Cisco IOS" in the Cisco IOS IPv6 Configuration Library at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_qosv6.htm
QoS: ATM-CLP and L2-COS Based WRED
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sw red.htm
QoS: ATM Cell-Based Policer
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fscb p.htm
QoS: Classification of Locally Sourced Packets
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sc locp.htm
QoS: Enhancements to Single QoS Policy Definition for a Physical Interface (L3/1C/nD) Including Match FR DLCI
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sl 31dd.htm
QoS: Enhancement to Sub-interface QoS Policy Definitions (L3/nC/nD) Including Proportional Bandwidth Allocation
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sl 3ncd.htm
QoS: Implicit Queue Limit
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12si mql.htm
QoS: L2 Overhead Specification for Shaping and Policing Parameters for Ethernet
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sl 2os.htm
QoS: Match on ATM CLP
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sm catm.htm
QoS: Percentage-Based Policing
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature (including the QoS: Time-Based Parameters for Policing feature) see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sp ctpg.htm
QoS: Percentage-Based and Time-Based Policing Parameters
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sp btbp.htm
QoS: Percentage-Based Shaping
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature (including the QoS: Percentage-Based Shaping Parameters feature), see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sp ctsg.htm
QoS: Time-Based Thresholds for WRED and Queue Limit
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sw rdql.htm
QoS: Time-Based Thresholds for WRED and Queue Limit for the Cisco 12000 Series Router
Platforms: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12st bwr.htm
QoS: Tunnel Marking for L2TPv3 Tunnels
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12st nlmk.htm
Scalability Enhancements on Cisco 12000 Series 4-Port ATM ISE Line Cards
Platform: Cisco 12000 series
The Cisco 12000 series router, 4-port OC-3c/STM-1 and 4-port OC-12c/STM-4c ATM IP Services Engine (ISE) line cards are enhanced so that quality of service (QoS) policy maps applied to virtual circuits (VCs) can optimize their use of Ternary Content Addressable Memory (TCAM) space. This enhancement provides the following performance improvements:
•Reduction in the number of TCAM entries required, as individual TCAM entries are used for multiple VCs.
•Reduction in the amount of Route Processor (RP) memory.
•Reduction of overall merge time for TCAM entries.
Prior releases of the software provided for sharing of policy maps between VCs if all classes in the policy map could be shared. This greatly limited the use of the sharing, because if even one class in the policy map could not be shared, the entire policy map was unshared. This enhancement provides for sharing of individual classes between VCs.
When classes in a policy map are shared between VCs, the amount of TCAM space can be reduced in proportion to the number of VCs that use these classes. In many cases, this greatly reduces the amount of TCAM space required to store QoS policy maps applied to VCs.
Route Processor (RP) memory is reduced in proportion to the number of VCs that have shared classes. This is because a single instance of each class is stored on the RP and is used by all VCs on a line card that are configured with the same class.
In addition, the overall merge time for TCAM entries on all VCs that are configured with the same policy map in the same (ingress or egress) direction is reduced in proportion to the number of VCs using these TCAM entries.
A class in a policy map is shared, except in the following instances:
•The class is part of a policy map that uses percentage-based policing. In this instance, all classes in the policy map are unshared between VCs with different available bandwidths. For more information on percentage-based policing, see QoS: Percentage-Based Policing at http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28 /12spctpg.htm.
•The class is part of an ingress policy map that contains at least one shape command. In this instance, all classes in the policy map are unshared.
•The class contains at least one police statement.
Restriction
QoS statistics for shared classes, other than class-default, are available only on an egress traffic policy when the shared class has a bandwidth or priority command defined in the policy map. This is a result of the optimization of TCAM resources. Otherwise, the shared classes have no matched per-class statistics by default. QoS statistics will be available for class-default on an egress traffic policy if all of the other classes in the policy map have priority or bandwidth command defined for them or if class-default is unshared.
QoS statistics for shared classes are not available on an ingress traffic policy.
For a shared class in which QoS statistics are not available, you can disable the sharing and the optimization of TCAM entries for this class and thereby enable the QoS statistics. To enable QoS statistics for a traffic class in a shared class, it is recommended that you add a police command to the traffic class and configure the cir (committed information rate) parameter to its maximum value and the conform-action and exceed-action parameters as a transmit action. QoS statistics that were previously unavailable for a traffic class will now be displayed, however the class will be unshared. This applies to class-default as well.
The command syntax of the police (two rates) command is as follows:
Router(config-pmap-c)# police cir {cir_bps | percent cir_per} [bc conform-burst] {pir pir_bps} [be peak-burst] [conform-action action [exceed-action action [violate-action action]]]
For more information about the police command syntax, see the "police (two rates)" section at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/qos_r/qos_o1g.htm#108442 0.
Stacked VLAN Processing
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/qinq .htm
Transparent Layer 2 Protocol Tunneling and Layer 2 PDU Filtering
Platform: Cisco 12000 series
For detailed information about this feature (also referred to separately as the Transparent Layer 2 Protocol Tunneling feature and the Layer 2 PDU Filtering feature), see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/l2pt .htm
Upgrade Secondary ROMmon CLI
Platform: Cisco 7200 VXR routers
For detailed information about this procedure, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12s2 8fur.htm
VP/VC Mode Packed Cell Relay Support
Platforms: Cisco 7200 series, Cisco 7500 series
The VP/VC Mode Packed Cell Relay Support feature (also referred to as ATM Packed Cell Relay: VP and VC Modes) is now supported on the PA-A3-8E1 IMA and PA-A3-8T1 IMA port adapters. For detailed information about this feature, see the Any Transport over MPLS document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/fsat om28.htm
New Hardware and Software Features in Cisco IOS Release 12.0(27)S1 to Cisco IOS Release 12.0(27)S5
There are no new hardware or software features in Cisco IOS Release 12.0(27)S1 to Cisco IOS Release 12.0(27)S5.
New Hardware Features in Cisco IOS Release 12.0(27)S
This section describes new and changed features in Cisco IOS Release 12.0(27)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(27)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
1-Port Channelized OC-12/STM-4 (DS1/E1) ISE Line Card
Platform: Cisco 12000 series
There are no commands specific to the Cisco 1-port Channelized OC-12/STM-4 (DS1/E1) line card in Cisco IOS Release 12.0(27)S.
For detailed information about this feature, see the following documents:
1-Port Channelized OC-12c/STM-4c (DS1/E1) ISE Line Card Installation and Configuration at
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_chan/13921c12.htm
Cisco IOS Software Configuration for the Cisco 12000 Series 1-port Channelized OC-12/STM-4 (DS1/E1) ISE Line Card at
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/12_0s/index.htm
2-Port OC-192c/STM-64 Packet over SONET Line Card
Platform: Cisco 12000 series
There are no commands specific to the Cisco 2-port OC-192c/STM-64 Packet over SONET line card in Cisco IOS Release 12.0(27)S.
For detailed information about this feature, see the following documents:
2-Port OC-192c/STM-64c and 8-Port OC-48c/STM-16c Packet over SONET Line Card Installation and Configuration at
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_pos/16025pos.htm
Cisco IOS Software Configuration for the Cisco 12000 Series Router 2-Port OC-192c/STM-64 Packet over SONET Line Card at
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/12_0s/index.htm
2-Port Packet over SONET OC3c/STM1 Port Adapter
Platforms: Cisco 7200 series, Cisco 7500 series
The 2-port Packet over SONET OC3c/STM1 port adapter (PA-POS-2OC3) provides two Packet-over-SONET (POS) ports in a single port adapter slot. The two ports function either as dual independent OC-3c/STM1 ports or as a single port with automatic protection switching (APS). The PA-POS-2OC3 is used as a direct connection between the supported router or switch and external networks.
For more information about the PA-POS-2OC3, see the Cisco documents at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/7200vx/portadpt/sonet_pa/3028_2oc/index.htm
4-Port OC-3/STM-1 ATM ISE Line Card
Platform: Cisco 12000 series
If you configure a virtual circuit (VC) on a 4-Port OC-12/STM-4 ATM ISE interface with a peak cell rate (PCR) or sustainable cell rate (SCR) greater than OC-6 (using the ubr, vbr-nrt, vbr-rt, or cbr commands), and attach a service policy with MDRR (configured using the bandwidth command) to the interface for specified traffic classes, when traffic on the interface from the specified classes is equal to or greater than the configured PCR or SCR values, frequent queuing and dequeueing changes occur between the MDRR queues, which may result in decreased VC throughput. For more information about how to create a service policy and attach it to an interface, see the Modular Quality of Service Command-Line Interface at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5/mq c/mcli.htm
8-port OC-48c/STM-16 Packet over SONET Line Card
Platform: Cisco 12000 series
There are no commands specific to the Cisco 8-port OC-48c/STM-16 Packet over SONET line card in Cisco IOS Release 12.0(27)S.
The Cisco 8-Port OC-48 POS line card, in conjunction with 40 Gbps per slot Cisco 12800 routers, achieves up to 50 Mpps per slot of forwarding capacity. It is fully interoperable with all existing Cisco 12000 series line cards.
The Cisco 8-Port OC-48 POS line card features a dedicated Layer 3 forwarding engine that offers a comprehensive IP/MPLS feature set, including advanced quality of service (QoS), accounting (sampled NetFlow), security and traffic control, and committed access rate (CAR)—all at 50 Mpps. The line card supports more than one million prefixes, up to 256,000 multicast groups, and more than 32,000 lines of access control lists (ACLs), both ingress and egress, at wire speed.
The Cisco 8-Port OC-48 POS line card is equipped with third-generation pluggable optics for improved component integration, power consumption, and maximum versatility. It is fully interoperable with standard OC-48c and STM-16c optical interfaces. Available pluggable optics include short reach (SR), intermediate reach (IR), and long reach (LR); optics of different types can be combined.
Cisco 12000 Series Routers Upgradeable Fabric
Platforms: Cisco 12006 and Cisco 12010 Routers with 2.5-Gbps Switch Fabric
In Cisco IOS Release 12.0(27)S, two new chassis models that use a 2.5-Gbps switch fabric are introduced in the Cisco 12000 series: Cisco 12006 and Cisco 12010 routers. The switch fabric consists of a clock scheduler card (CSC) and a switch fabric card (SFC). Each SFC or CSC provides a 2.5-Gbps full-duplex connection to each line card in the router.
Note Although you may install line cards that require more than 2.5 Gbps of bandwidth in a Cisco 12006 or Cisco 12010 router, the line cards are held in a disabled state.
For information about how to install and use the 2.5-Gbps switch fabric, see the following documents:
•Cisco 12006 and Cisco 12406 Router Clock and Scheduler, Switch Fabric, and Alarm Card Replacement Instructions
•Cisco 12010, Cisco 12410, and Cisco 12810 Router Clock and Scheduler, Switch Fabric, and Alarm Card Replacement Instructions
New Software Features in Cisco IOS Release 12.0(27)S
This section describes new and changed features in Cisco IOS Release 12.0(27)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(27)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
ATM Cell Relay, Cell Packing over MPLS
Platform: Cisco 12000 series
For detailed information about this feature, see the following documents:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fsato m27.htm
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/4atm _ise.htm
ATM Port Mode Packed Cell Relay over MPLS
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fsato m27.htm
ATM VP Shaping, NNI, and Port Mode Cell Packing for Cisco 12000 Series Routers
Platform: Cisco 12000 series
For detailed information about this feature, see the following documents:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fsato m27.htm
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/4atm _ise.htm
BGP Cost Community Support for EIGRP MPLS VPN PE-CE with Backdoor Links
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature, see the following document:
BGP Support for Dual AS Configuration for Network AS Migrations
Platforms: Cisco 7200 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sb/newft/122sbc27/fsbgpdas.htm
Bridging Support for FE ports on the Cisco 10720 4GE+8FE module
Platform: Cisco 10720
For detailed information about this feature, see the following document:
BGP Support for TTL Security Check
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http:www.cisco.com/univercd/cc/td/doc/product/software/ios122sb/newft/122sbc27/fsxebtsh.htm
Binding L2TPv3 Sessions to MLFR Interfaces on E0 Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/l2tp v325.htm#1136637
DiffServ Compliant Weighted Random Early Detection
Platform: Cisco 10720
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/1072 0.htm
Dynamic Time Slot Configuration
Platform: Cisco 10000 series
The Dynamic Time Slot Configuration feature automatically reconfigures an existing channel group with different time slot allocations. You no longer are required to remove and recreate the channel group with the desired allocation.
On the Cisco 10000 router, you can create channel groups using available time slots on the following channelized line cards:
•Channelized T3
•Channelized OC-12
•Channelized STM-1
•Channelized E1/T1
In previous releases, once you configure channel groups, you cannot modify their time slot allocations without first deleting the channel group. After recreating the channel group with the different time slot allocations, you then recreate the interface and subinterfaces associated with the channel group.
The Dynamic Time Slot Configuration feature eliminates the requirement for manual reconfiguration. Instead, the reconfiguration of time slots on channelized line cards occurs automatically.
EBGP Label Distribution
Platform: Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/config/qos/index.htm
EIGRP MPLS VPN PE-CE Site of Origin (SoO)
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/s_m vesoo.htm
Enhanced RED Statistics
Platform: Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/config/qos/index.htm
Fast-Flooding IS-IS LSPs Using the fast-flood Command
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fstfl d.htm
Frame Relay over L2TPv3 QoS on E0 Line Cards
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/l2tp v325.htm
Integrated IS-IS Global Default Metric
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_4/gtisglob.htm
Integrated IS-IS Protocol Shutdown Support Maintaining Configuration Parameters
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_4/gtisprot.htm
IPv6 Multicast on Cisco 12000 Series Line Cards
Platform: Cisco 12000 series
In Cisco IOS Release 12.0(27)S, IPv6 Multicast is supported on all Cisco 12000 series line cards, except for the following line cards that will not support IPv6 Multicast:
•Engine 1:
–8-port Fast Ethernet
–1-port Gigabit Ethernet
•Engine 2:
–3-port Gigabit Ethernet
Note Note: The 1-port CHOC12-DS1 line card does not support IPv6 or IPv6 Multicast in Cisco IOS Release 12.0(27)S.
For more information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_mcast.htm
IPv6 Provider Edge Router over MPLS (Cisco 6PE) Enhancement
Platform: Cisco 12000 series
On an IPv6-enabled provider edge (6PE) Cisco 12000 Series Internet Router, when the edge-facing line card is IP Services Engine (ISE) and the core-facing line card is Engine 4 or Engine 4+, disposition performed on 6PE-labeled packets has been accelerated. The acceleration is possible because 6PE-label disposition is now performed on the hardware of the edge-facing ISE line card instead of on the CPU of the core-facing Engine 4 or Engine 4+ line card.
The acceleration applies only to IPv6 6PE-labeled packets. Aggregate 6PE label disposition has not been accelerated, and remains bound by the CPU forwarding performance on the core-facing Engine 4 or Engine 4+ line card.
No new or modified Cisco IOS software commands are introduced with this feature.
IS-IS Local RIB Support for Redistributed Routes
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/isred rib.htm
Layer 2 Local Switching—ATM to ATM
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fsloc al.htm
Layer 2 Local Switching—ATM to Ethernet
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fsloc al.htm
Layer 2 Local Switching—ATM to Frame Relay
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fsloc al.htm
Layer 2 Local Switching—Frame Relay to Frame Relay
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fsloc al.htm
L2TPv3 Distributed Sequencing
Platform: Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/l2tp v325.htm
MB RP Memory Support for Cisco 10720 Internet Router
Platform: Cisco 10720
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/107 20.htm
MPLS Embedded Management—LSP Ping/Traceroute and AToM VCCV
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/gsls ppt.htm
MPLS Traffic Engineering Autotunnel
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/gsau totn.htm
MPLS Traffic Engineering Autotunnel Mesh Groups
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/gsm eshgr.htm
MPLS VPN—eBGP Multipath Support for CSC and InterAS MPLS VPNs
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following documents:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fscs cmlp.htm
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fsias mlp.htm
MPLS VPN—Explicit Null Label Support with BGP IPv4 Label Session
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/gsxn lbsp.htm
MPLS VPN—VPN Aware LDP MIB
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fs27 ldp8.htm
MSDP Compliance with IETF RFC 3618
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_4/gt_msdp.htm
Multicast Heartbeat
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
The Multicast Heartbeat feature provides a way to monitor the status of IP multicast delivery and be informed when the delivery fails via Simple Network Management Protocol (SNMP) traps. For more information about this feature, see the "Using IP Multicast Heartbeat" section in the chapter "Configuring IP Multicast Routing" in the Cisco IOS IP Configuration Guide, Release 12.3, at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ip_vcg.htm
Multicast State Enhancements for Engine 2 and Engine 3 Line Cards on the Cisco 12000 Series
Platform: Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/mca st.htm
Multicast-VPN: Multicast Support for MPLS VPN
Platform: Cisco 10720
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/1072 0.htm
Online Offline Diagnostics (OOD)—Field Diagnostics
Platform: Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/tblshoot/index.htm
OSPF per-Interface Link-Local Signaling (LLS)
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/ospf lls.htm
OSPF Link State Database Overload Protection
Platforms: Cisco 7200 series, Cisco 7500 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/ospf opro.htm
OSPF Support for Unlimited Software VRFs per Provider Edge (PE) Router
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_4/gtospfvf.htm
Percent-Based Policing
Platforms: Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/config/qos/index.htm
Policy Map Scaling
Platforms: Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/config/qos/index.htm
RED with Queue Limit
Platforms: Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/config/qos/index.htm
RFC 2495/96 Support for DS1-MIB/DS3-MIB
Platform: Cisco 12000 series
The DS1-MIB and DS3-MIB have been enhanced to include support for new MIB variables and traps, as defined by RFC 2495 and RFC 2496, for the following Cisco 12000 series line cards:
•1-Port Channelized OC-12 (DS3)
•6-Port Channelized T3 (T1)
•6-Port DS3
•6-Port E3
•12-Port DS3
•12-Port E3
The DS1-MIB contains definitions of managed objects for the DS1, E1, DS2, and E2 interfaces, as defined by RFC 2495. The DS3-MIB contains definitions of managed objects for DS3/E3 interfaces, as defined by RFC 2496.
No new or modified Cisco IOS commands are associated with these MIBs. For details on managed objects within the DS1-MIB and DS3-MIB, see the DS1-MIB.my and DS3-MIB.my MIB files. Information on MIBs can be found at MIB Locator.
http://tools.cisco.com/ITDIT/MIBS/servlet/index
Router Security Audit Logs
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1838/products_feature_guide09186a00801afa4f.html
SNMP over IPv6
Platform: Cisco 12000 series
SNMP can be configured over IPv6 transport so that Cisco IOS devices can be managed from a notification server configured with only IPv6. An IPv6 host can perform SNMP queries and receive SNMP notifications from a device running Cisco IOS IPv6.
The following MIBs are supported for IPv6:
•CISCO-FLASH MIB
•CISCO-CONFIG-COPY-MIB
•CISCO-CONFIG-MAN-MIB
•CISCO-DATA-COLLECTION-MIB
•EXPRESSION-MIB
•ENTITY-MIB
•NOTIFICTAION-LOG-MIB
•SNMP-TARGET-MIB
see the Cisco IOS Configuration Fundamentals Configuration Guide for detailed information about SNMP, MIBs, and managing Cisco networks in Cisco IOS.
This feature is described in Managing Cisco IOS Applications over IPv6 at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_mgev6.htm
The commands descriptions are located in the Cisco IOS IPv6 Command Reference at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_r/index.htm
Source Specific Multicast (SSM)—Mapping
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00801a6d6f.html
SRP—Layer 3 Fast Notification
Platform: Cisco 10720
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/1072 0.htm
Three-Level Policy Maps
Platforms: Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/config/qos/index.htm
Unique Device Identifier (UDI)
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_4/gtpepudi.htm
VC Oversubscription
Platforms: Cisco 10000 series
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/config/qos/index.htm
New Hardware and Software Features in Cisco IOS Release 12.0(26)S1 to Cisco IOS Release 12.0(26)S6
There are no new hardware or software features in Cisco IOS Release 12.0(26)S1 to Cisco IOS Release 12.0(26)S6.
New Hardware Features in Cisco IOS Release 12.0(26)S
There are no new hardware features in Cisco IOS Release 12.0(26)S.
New Software Features in Cisco IOS Release 12.0(26)S
This section describes new and changed features in Cisco IOS Release 12.0(26)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(26)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Any Transport over MPLS
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s26/fsato m26.htm
ATM PVC Bundle Enhancement—MPLS EXP-Based PVC Selection
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/atm.htm
APS Stateful Switchover
For detailed information about this feature, see the following document:
ATM PVC F5 OAM Recovery Traps
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s26/26srctrp.htm
BECN and FECN Marking for Frame Relay over MPLS
For detailed information about this feature, see the following document:
Byte-Based Weighted Random Early Detection
For detailed information about this feature, see the following document:
Cisco 10720—New Features
In Cisco IOS Release 12.0(26)S, the Cisco 10720 supports new features that are documented in the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/1072 0.htm
The following new features are supported:
•L2TPv3 Ethernet-to-VLAN internetworking; for information, see the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/ 10720.htm#15456
•MQC hierarchical class maps; for information, see the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/ 10720.htm#1386722
•MQC strict priority queue; for information, see the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/ 10720.htm#1417317
Starting in Cisco IOS Release 12.0(26)S, the following IP version 6 (IPv6) features use Parallel Express Forwarding (PXF) for accelerated, fast path forwarding on the Cisco 10720:
•PXF accelerated IPv6
•PXF accelerated IPv6-6PE
•PXF accelerated IPv6 extended ACLs
For information about these three features, see the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/ 10720.htm#1384431
Cisco 12000 Series 4-Port OC-12c/STM-4c DPT ISE Line Card Enhancements
Platform: Cisco 12000 series
New software features have been added to the Cisco 12000 series 4-port OC-12c/STM-4c Dynamic Packet Transport (DPT) IP Services Engine (ISE) line card. Starting in Cisco IOS Release 12.0(26)S, the following software features are now supported on the 4-port OC-12c/STM-4c DPT ISE line card:
• IPv6
Stateful Switchover (SSO)
Note The Stateful Switchover (SSO) feature was introduced in Cisco IOS Release 12.0(22)S. This release introduces the feature on the 4-port OC-12c/STM-4c DPT ISE line card.
The Stateful Switchover (SSO) feature is an incremental step within an overall program to improve the availability of networks constructed with Cisco IOS routers. SSO is particularly useful at the network edge. Traditionally, core routers protect against network faults using router redundancy and mesh connections that allow traffic to bypass failed network elements. SSO provides protection for network edge devices with dual Route Processors (RPs) that represent a single point of failure in the network design, and where an outage might result in loss of service for customers.
In specific Cisco networking devices that support dual RPs, SSO takes advantage of RP redundancy to increase network availability. The SSO feature takes advantage of RP redundancy by establishing one of the RPs as the active processor while the other RP is designated as the standby processor, and then synchronizing critical state information between them. Following an initial synchronization between the two processors, SSO dynamically maintains RP state information between them.
A switchover from the active to the standby processor occurs when the active RP fails, is removed from the networking device, or is manually taken down for maintenance.
SSO is used with the Cisco Nonstop Forwarding (NSF) feature. Cisco NSF allows for the forwarding of data packets to continue along known routes while the routing protocol information is being restored following a switchover. With Cisco NSF, peer networking devices do not experience routing flaps, thereby reducing loss of service outages for customers.
For more information about the Stateful Switchover feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/sso2 4s.htm
IPv6
Note IP version 6 (IPv6) was introduced in Cisco IOS Release 12.0(22)S. This release introduces IPv6 on the 4-port OC-12c/STM-4c DPT ISE line card.
IP is a packet-based protocol used to exchange data, voice, and video traffic over digital networks. IP handles addressing, fragmentation, reassembly, and protocol demultiplexing. It is the foundation on which all other IP protocols (collectively referred to as the IP Protocol suite) are built. As a network-layer protocol, IP contains addressing and control information that allows data packets to be routed. IPv6, formerly called IPng (next generation), is the latest version of IP and offers many benefits, such as a larger address space, over the previous version of IP (version 4).
For more information, see the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
Error Recovery Enhancements
Error recovery on 4-port OC-12c/STM-4c DPT ISE line cards has been enhanced to include more comprehensive hardware failure detection and an improved recovery process. The boot time following hardware failures has also been minimized.
MPLS Functionality
In addition to MPLS Virtual Private Networks on the 4-Port OC-12c/STM-4c DPT ISE Line Card, which was introduced in Cisco IOS Release 12.0(25)S, the following Multiprotocol Label Switching (MPLS) features are now supported on the 4-port OC-12c/STM-4c DPT ISE line card:
MPLS Quality of Service (QoS)
The MPLS Quality of Service (QoS) feature was introduced in Cisco IOS Release 12.0(22)S. This release introduces the MPLS Quality of Service (QoS) feature on the 4-port OC-12c/STM-4c DPT ISE line card.
The MPLS Quality of Service (QoS) feature enables service providers to set the MPLS experimental field value without modifying the value of the IP precedence field in IP packets that are transported through an MPLS core network. By choosing different values for the MPLS experimental field, service providers can mark packets according to their characteristics, such as rate or type, so that packets have the priority that they require during periods of congestion.
For more information about how to use and configure the MPLS Quality of Service (QoS) feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st14mct /1214t.htm
MPLS Time To Live (TTL) Propagation from IP
The MPLS Time To Live (TTL) Propagation from IP feature was introduced in Cisco IOS Release 12.0(24)S for Engine 4+ DPT line cards. This release introduces the MPLS Time To Live (TTL) Propagation from IP feature on the 4-port OC-12c/STM-4c DPT ISE line card.
To control the generation of the time to live (TTL) field in the MPLS header when labels are first added to an IP packet, the 4-port OC-12c/STM-4c DPT ISE line card supports the use of the mpls ip propagate-ttl global configuration command.
For more information about this command, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122sup/122csum/csum2/122csswt/xs fscmd3.htm
Multicast Forwarding
Note The Multicast Forwarding feature was introduced in Cisco IOS Release 12.0(21)S. This release introduces the Multicast Forwarding feature on the 4-port OC-12c/STM-4c DPT ISE line card.
The Multicast Forwarding feature on the 4-port OC-12c/STM-4c DPT ISE line card allows hardware-based fast forwarding of IP version 4 (IPv4) multicast traffic, resulting in high throughputs and performance.
For more information about the hardware forwarding of IP multicast packets and how to enable hardware forwarding on DPT ISE line cards, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/mca st.htm
Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card Enhancements
Platform: Cisco 12000 series
Starting in Cisco IOS Release 12.0(26)S, the following software features are now supported on Cisco 12000 series 8-port OC-3/STM-1 ATM line cards:
• IP Packet Precedence Marking on Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Cards
• Sampled NetFlow and MPLS-aware NetFlow on Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Cards
ATM AAL5 and ATM Cell Relay Supported on the Same Port on Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Cards
Cisco 12000 series 8-port OC-3/STM-1 ATM line cards now support, by default, the Any Transport over MPLS (AToM): ATM Cell Relay over MPLS feature in both virtual circuit (VC) mode and virtual path (VP) mode and the configuration of the Any Transport over MPLS: ATM AAL5 over MPLS feature on the same port. In this section, both the Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: VC Mode feature and the Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: VP Mode feature are referred to as the ATM Cell Relay over MPLS: Single Cell Relay feature.
Starting in Cisco IOS Release 12.0(26)S, you no longer need to use the atm mode cell-relay interface configuration command to enable an 8-port OC-3/STM-1 ATM interface to send and receive ATM packets as part of the ATM Cell Relay over MPLS: Single Cell Relay feature.
Another restriction that has been removed from configuring the ATM Cell Relay over MPLS: Single Cell Relay feature on an 8-port OC-3/STM-1 ATM line card is that a corresponding port is no longer reserved for this feature. For example, in Cisco IOS Release 12.0(25)S, if you configure the ATM Cell Relay over MPLS: Single Cell Relay feature on port 0, port 1 is also reserved. Likewise, ports 2 and 3, ports 4 and 5, and ports 6 and 7 are reserved when you configure the ATM Cell Relay over MPLS: Single Cell Relay feature on either port in the pair.
In addition, in Cisco IOS Release 12.0(25)S, if you configure an 8-port OC-3/STM-1 ATM port for the Any Transport over MPLS: ATM AAL5 over MPLS feature and then configure the ATM Cell Relay over MPLS: Single Cell Relay feature on that port, the VCs and VPs for AAL5 on the port and its corresponding port were removed. Starting in Cisco IOS Release 12.0(26)S, this behavior no longer occurs. The Any Transport over MPLS: ATM AAL5 over MPLS feature and the ATM Cell Relay over MPLS: Single Cell Relay feature are supported on the same port.
Any Transport over MPLS (AToM) transports Layer 2 packets over a Multiprotocol Label Switching (MPLS) backbone. ATM single cell relay is one type of Layer 2 traffic that can be transported using AToM over an MPLS network core. For information about how to configure the ATM Cell Relay over MPLS: Single Cell Relay feature and the restrictions that existed in earlier Cisco IOS software releases, see the Any Transport over MPLS document at the following Cisco location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/atom 25s.htm
IP Packet Precedence Marking on Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Cards
Note The IP Packet Precedence Marking feature was introduced in Cisco IOS Release 12.0(22)S on the Cisco 12000 series Engine 2 Packet-over-SONET (POS) line cards. This release introduces the feature on Cisco 12000 series 8-port OC-3/STM-1 ATM line cards.
The IP Packet Precedence Marking feature is supported on 8-port OC-3/STM-1 ATM line cards. This feature is implemented in the Packet Switching ASIC (PSA) for fast path forwarding and in the line card switching software for slow path forwarding.
In the modular QoS CLI (MQC), you use the set ip precedence ip-precedence-value policy-map configuration command to set the precedence value in IP headers for a specified traffic class.
Note On 8-port OC-3/STM-1 ATM line cards, you can use the set ip precedence ip-precedence-value policy-map configuration command in a quality of service (QoS) policy configuration only with the default traffic class.
Usage Guidelines
On 8-port OC-3/STM-1 ATM line cards, IP packet precedence marking is implemented as follows:
•IP packet precedence marking is performed on an individual virtual circuit (VC) basis in the ingress direction. IP packets received on the VC are marked irrespective of the packet switching behavior of the egress port. The QoS treatment of the packet is based on the new precedence bits set with the set ip precedence ip-precedence-value policy-map configuration command, not the original precedence bits received in the packet.
•If a received IP packet is forwarded on an MPLS label-switched path (LSP), the experimental bits in the MPLS label are given the value of the precedence bit configured with the set ip precedence ip-precedence-value policy-map configuration command.
•IP packet precedence marking is disabled by default. VC traffic is forwarded "as is" with no special QoS action.
Restrictions
The following restrictions apply to IP packet precedence marking on 8-port OC-3/STM-1 ATM line cards:
•You can configure the IP precedence bit with the set ip precedence ip-precedence-value policy-map configuration command only on a per-PVC basis.
•The set ip precedence ip-precedence-value policy-map configuration command is not supported on a PVC configured as l2transport.
Configuration Example
The following example shows how to set the precedence value in IP headers to 5 for the service policy ip_color1 configured for the default traffic class, and then attach the policy to an ATM virtual circuit on an 8-port OC-3/STM-1 ATM line card.
router(config)# policy-map ip_color1
router(config-pmap)# class class-default
router(config-pmap-c)# set ip precedence 5
router(config-pmap-c)# end
!
router(config)# interface atm 3/0.1 point-to-point
router(config-subif)# pvc 10/10
router(config-if-atm-vc)# service-policy input ip_color1
router(config-if-atm-vc)# end
For more information about how to use MQC to configure IP packet precedence marking in a QoS policy and attach the service policy to an interface or ATM virtual circuit, see Configuring the Modular Quality of Service Command-Line Interface at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_c/fqcprt8/qcfmcli2.htm
Sampled NetFlow and MPLS-aware NetFlow on Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Cards
Cisco 12000 series 8-port OC-3/STM-1 ATM line cards now support the Sampled NetFlow and Multiprotocol Label Switching (MPLS)-aware NetFlow features.
Note The Sampled Netflow feature was introduced in Cisco IOS Release 12.0(11)S; the MPLS-aware NetFlow feature was introduced in Cisco IOS Release 12.0(24)S.
The Sampled NetFlow feature enables you to sample one out of many IP packets that are being forwarded to an interface. Sampled packets are accounted for in the NetFlow flow cache of the router. Sampling packets substantially decreases the CPU utilization that is needed to account for NetFlow packets, by allowing the majority of the packets to be switched faster because they do not require additional NetFlow processing. For information about how to configure and use Sampled NetFlow, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/12s_ sanf.htm
MPLS-aware NetFlow is an extension of the NetFlow feature. NetFlow traditionally provides statistics for IP version 4 (IPv4) traffic. MPLS-aware NetFlow provides per-flow statistics for traffic in MPLS-enabled networks. The network administrator can turn on MPLS-aware NetFlow inside an MPLS cloud on a subset of provider (P) backbone routers. These routers can export MPLS-aware NetFlow data in real time to an external NetFlow collector device for further processing or to a data terminal for analysis. MPLS-aware NetFlow statistics can be used for detailed MPLS traffic studies and analysis. For additional information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/fsmn f24.htm
Cisco 12000 Series ISE and E4+ Line Card MQC Enhancements
Platform: Cisco 12000 series
Cisco 12000 series IP Services Engine (ISE) and Engine 4 Plus (E4+) line cards now support an enhanced set of modular QoS CLI (MQC) commands for the following line card types:
•Packet-over-SONET (POS) ISE
•Gigabit Ethernet (GE) ISE
•ATM ISE
•E4+ POS
•E4+ GE
New Commands
Table 8 lists and describes the new MQC commands supported on ISE and E4+ line cards.
Table 8 MQC Commands Supported on Cisco 12000 Series ISE and E4+ Line Cards
MQC Command Descriptionmatch ip dscp
Configures a specific IP differentiated service code point (DSCP) value as a match criterion.
match mpls experimental
Configures a class map to use the specified value of the EXP field as a match criterion.
match qos-group
Configures a specific QoS group value as a match criterion.
random-detect discard-class-based
Enables weighted random early detection (WRED) so that it is based on the discard class value of a packet.
set discard-class
Marks a packet with a discard-class value that describes its per-hop behavior (PHB) for dropping traffic.
set ip dscp
Marks a packet by setting the IP differentiated services code point (DSCP) in the type of service (ToS) byte.
set ip precedence
Configures the precedence value in the IP header.
set mpls experimental imposition1
Configures the value of the Multiprotocol Label Switching (MPLS) EXP field in all imposed label entries at an input interface.
set mpls experimental topmost
Configures the MPLS EXP field value in the topmost MPLS label header at an input and/or output interface.
set qos-group2
Configures a group ID so that it can be used later to classify packets.
1 The set mpls experimental imposition command is supported only on the input interfaces of POS ISE, GE ISE, ATM ISE, ES+ POS, and E4+ Ethernet line cards.
2 The set qos-group command is supported only on the input interfaces of ISE and E4+ line cards. Up to eight QoS groups are supported per line card. The valid values for the set qos-group command are from 0 to 7; 0 is the default for the qos-group keyword.
The enhanced MQC command set is implemented in the following ways on Cisco 12000 series ISE and E4+ line cards:
•Although E4+ line cards support MQC QoS configuration only on physical interfaces, an E4+ Ethernet line card can support input access control lists (ACLs) for a VLAN.
Packet-over-SONET and Gigabit Ethernet ISE line cards support MQC QoS configuration on both physical interfaces and subinterfaces. ATM ISE line cards support MQC QoS configuration on virtual circuits (VCs).
•When a Cisco 12000 series is used as a Provider Edge (PE) router, the set qos-group and set discard-class commands support pipe mode on output interfaces only for the following combinations of output interfaces:
Restrictions
The following restrictions apply to pipe mode between Cisco 12000 series output interfaces:
•If the core-facing output interface is E4+, you must configure the set qos-group ID as a value between 0 and 7.
•Pipe mode is only partially supported between E2 core-facing and ISE customer-facing output interfaces. The only parameter that is sent from the E2 to the ISE interface is the set qos-group value (the set discard-class value is not sent), which is identically mapped to the E2 exp-value of the exposed label. On the ISE interface, scheduling is performed using the match qos-group command.
•On ISE and E4+ line cards, the MPLS experimental (EXP) value is automatically propagated from the null label to the exposed label.
•On ISE line cards, the set discard-class command is supported as one of the possible traffic policing actions that you can configure with the police command.
•On ISE and E4+ line cards, the set mpls experimental imposition and set mpls experimental topmost commands are supported as possible traffic policing actions that you can configure with the police command.
•Eight levels of quality of service are provided for ISE ToFab queues, instead of only two levels supported in earlier releases.
•ToFab queue and output queue selection is based on the remarked packets.
•Weighted Random Early Detection (WRED) enabled on an output interface is based on the remarked packets sent to the output interface.
More Information
For more information about MQC command syntax and how to use these MQC commands on Cisco 12000 series ISE and E4+ line cards, see the following publications:
•Cisco IOS Quality of Service Solutions Command Reference at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123tcr/123tqr/index.htm
•Modular Quality of Service Command-Line Interface at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5 /mqc/mcli.htm
MPLS DiffServ Tunneling Modes
The following MQC commands are supported on Cisco 12000 series ISE and E4+ line cards to configure the MPLS DiffServ Tunneling Modes feature:
•match qos-group
•set discard-class
•set mpls experimental imposition
•set mpls experimental topmost
•set discard-class
The MPLS DiffServ Tunneling Modes feature allows service providers to manage the quality of service that a router will provide to a Multiprotocol Label Switching (MPLS) packet in an MPLS network. The MPLS DiffServ Tunneling Modes feature conforms to the IETF draft standard for Uniform, Short Pipe, and Pipe modes. It also conforms to Cisco-defined extensions for scalable command-line interface (CLI) management of those modes at customer edge, provider edge, and core routers.
For more information about how to configure and use the MPLS DiffServ Tunneling Modes feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftdtmode.htm
CISCO-ATM-EXT-MIB
Platform: Cisco 12000 series
The CISCO-ATM-EXT-MIB has been enhanced to include support for Operation, Administration, and Maintenance (OAM) parameters used to manage ATM permanent virtual circuits (PVCs). OAM ensures that no packets are lost by allowing a PVC to go down if there is a disruption along its path, such as if network connectivity is lost. A new table is added to the CISCO-ATM-EXT-MIB that contains OAM configuration and PVC state information.
No new or modified Cisco IOS commands are associated with this MIB. For details on managed objects within the CISCO-ATM-EXT-MIB, see the CISCO-ATM-EXT-MIB.my MIB file, available from the Cisco MIB FTP site at the following location:
ftp://ftp.cisco.com/pub/mibs/v2/
Class-Based Marking
For detailed information about this feature, see the following document:
Class-Based Policing
For detailed information about this feature, see the following document:
Class-Based Shaping
For detailed information about this feature, see the following document:
Class-Based Weighted Fair Queueing and Weighted Random Early Detection
For detailed information about this feature, see the following document:
CNS Config Notify
For detailed information about this feature, see the following document:
CPU Threshold Notification
For detailed information about this feature, see the following document:
Digital-link Subrate Scramble for Cisco 12000 Series 6-Port E3 and 12-Port E3 Line Cards
Platform: Cisco 12000 series
The 6-port E3 (6E3-SMB) and 12-port E3 (12E3-SMB) line cards for the Cisco 12000 series now support interoperating with the Cisco 7200 series and Cisco 7500 series 1-port E3 serial port adapter (PA-E3) and 2-port E3 serial port adapter (PA-2E3) when subrate and scrambling are enabled in digital-link mode. The Digital-link Subrate Scramble feature enhances interoperability between the 6E3-SMB and 12E3-SMB line cards and the PA-E3 and PA-2E3 port adapters. Subrate means that the configured bandwidth of the interface is less than the full default rate of 34,010 kbps.
To implement the Digital-link Subrate Scramble feature, enter the scramble before subrate processing interface configuration command. The before subrate processing option performs scrambling before the data has gone through subrate processing.
The configuration scenarios that are shown in Table 9 should be used when attempting interoperability between the 6E3-SMB and 12E3-SMB line cards and the PA-E3 and PA-2E3 port adapters.
Table 9 Interoperability Configuration—Cisco 12000 Series 6E3-SMB and 12E3-SMB Line Cards and Cisco 7000 Series E3 Port Adapters
Mode Cisco 7000 Series Configuration1 Cisco 12000 Series Configuration2Digital-link: subrate and scrambling required
dsu mode 0
dsu bandwidth <y>
scramble
dsu mode digital-link
dsu bandwidth <y>
scramble before subrate processingDigital-link: subrate required, no scrambling required
dsu mode 0
dsu bandwidth <y>
dsu mode digital-link
dsu bandwidth <y>Digital-link: scrambling required, no subrate required
dsu mode 0
dsu bandwidth 34010
scramble
dsu mode digital-link
dsu bandwidth 34010
scrambleDigital-link: no subrate, no scrambling required
dsu mode 0
dsu mode digital-link
Kentrox mode: subrate and scrambling required
—
—
Kentrox mode: subrate required, no scrambling required
dsu mode 1
dsu bandwidth <x>3
dsu mode kentrox
dsu bandwidth <x>Kentrox mode: scrambling required, no subrate required
dsu mode 1
dsu bandwidth 34010
scramble
dsu mode kentrox
dsu bandwidth 34010
scrambleKentrox mode: no subrate, no scrambling required
dsu mode 1
dsu bandwidth 34010
dsu mode kentrox
dsu bandwidth 34010
1 Interface configuration on PA-E3 or PA-2E3.
2 Interface configuration on 6E3-SMB or 12E3-SMB.
3 x is between 1000 and 24,500 kbps.
Embedded Event Manager 1.0
For detailed information about this feature, see the following document:
Enhanced SNMP for Stateful Switchover
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s26/ssom ibs3.htm
Ethernet VLAN Interworking
For detailed information about this feature, see the following document:
Ethernet VLAN to ATM AAL5 Interworking
For detailed information about this feature, see the following document:
Ethernet VLAN to Frame Relay Interworking
For detailed information about this feature, see the following document:
Frame Relay PVC Bundles with QoS Support for IP and MPLS
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/fr.htm
Frame Relay to ATM AAL5 Interworking
For detailed information about this feature, see the following document:
Frame Relay to PPP Interworking
For detailed information about this feature, see the following document:
Image Verification
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s26/gt_image.htm
Integrated IS-IS Multitopology Support for IPv6
Platforms: Cisco 10720, Cisco 12000 series
The Integrated IS-IS Multitopology Support for IPv6 feature enables Intermediate System-to-Intermediate System (IS-IS) to maintain a set of independent topologies within a single area or domain. This mode removes the restriction that all interfaces on which IS-IS is configured must support the identical set of network address families. It also removes the restriction that all routers in the IS-IS area (for Level 1 routing) or domain (for Level 2 routing) must support the identical set of network layer address families. Because multiple shortest path first (SPF) calculations are performed, one for each configured topology, it is sufficient that connectivity exists among a subset of the routers in the area or domain for a given network address family to be routable.
For additional information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_isis6.htm
IP Source Tracker
For detailed information about this feature, see the following document:
IPMROUTE-STD-MIB
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
This feature introduces support for the IPMROUTE-STD-MIB in Cisco IOS Release 12.0(26)S. The IPMROUTE-STD-MIB, as defined in RFC 2932, is a module for management of IP multicast routing in a manner independent of the specific multicast routing protocol in use. Support for this MIB replaces the draft form of the IPMROUTE-MIB.
The IPMROUTE-STD-MIB supports all the MIB objects of the IPMROUTE-MIB and in addition supports the following four new MIB objects:
•ipMRouteEntryCount
•ipMRouteHCOctets
•ipMRouteInterfaceHCInMcastOctets
•ipMRouteInterfaceHCOutMcastOctets
The ipMRouteScopeNameTable MIB object is not supported as it is not relevant to multicast routers.
IPv6 Multicast on Cisco 12000 Series Routers
Platform: Cisco 12000 series
Traditional IP and IP version 6 (IPv6) communication enables a host to send packets to a single host (unicast transmission) or to all hosts (broadcast transmission). IPv6 multicast provides a third scheme, allowing a host to send a single data stream to a subset of all hosts (group transmission) at about the same time.
The multicast environment consists of senders and receivers. Any host, regardless of whether it is a member of a group, can send to a group. However, only the members of a group receive the message. Packets delivered to group members are identified by a single multicast group address. Multicast packets are delivered to a group using best-effort reliability, just like IPv6 unicast packets.
IPv6 Multicast Features
In Cisco IOS Release 12.0(26)S, the following IPv6 multicast features are supported on the Cisco 12000 series:
•Multicast Listener Discovery (MLD) protocol for IPv6, Versions 1 and 2—MLD is used by IPv6 routers to discover multicast listeners on directly attached links. There are two versions of MLD: MLD version 1 is based on version 2 of the Internet Group Management Protocol (IGMP) for IP version 4 (IPv4), and MLD version 2 is based on version 3 of the IGMP for IPv4. IPv6 multicast for Cisco IOS software uses both MLD version2 and MLD version 1.
•MLD access group—The MLD access group provides receiver access control in Cisco IOS IPv6 multicast routers. This feature limits the list of groups a receiver can join, and it allows or denies sources used to join Source Specific Multicast (SSM) channels.
•Protocol Independent Multicast sparse mode (PIM-SM)—IPv6 multicast provides support for intradomain multicast routing using PIM-SM. PIM-SM uses unicast routing to provide reverse-path information for multicast tree building, but it is not dependent on any particular unicast routing protocol.
•Protocol Independent Multicast Source Specific Multicast (PIM-SSM)—PIM-SSM is the routing protocol that supports the implementation of SSM and is derived from PIM-SM. However, unlike PIM-SM where all multicast sources are sent when there is a PIM join, the SSM feature forwards datagram traffic to receivers from only those multicast sources that the receivers have explicitly joined, thus optimizing bandwidth utilization and denying unwanted Internet broadcast traffic.
•Protocol Independent Multicast (PIM) embedded Route Processor (RP) support—Embedded RP allows the router to learn RP information (such as the RP address and group-to-RP mappings) using the multicast group destination address instead of the statically configured RP.
•IPv6 multicast over IPv4 tunnels—IPv6 multicast is supported only over IPv4 tunnels in Cisco IOS Release 12.0(26)S.
•Static rendezvous point (RP) configuration—To select a static RP over an embedded RP, the specific embedded RP group range or mask must be configured in the access list of the static RP.
•Multicast scope boundaries—IPv6 includes support for global and nonglobal addresses. A scope zone, or a simply a zone, is a connected region of topology of a given scope. For example, the set of links connected by routers within a particular site, and the interfaces attached to those links, comprise a single zone of site-local scope.
•Multicast Routing Information Base (MRIB)—The MRIB is a protocol-independent repository of multicast routing entries instantiated by multicast routing protocols (routing clients). Its main function is to provide independence between routing protocols and the Multicast Forwarding Information Base (MFIB).
•IPv6 multicast process switching and fast switching—In process switching, the Route Processor must examine, rewrite, and forward each packet. IPv6 multicast fast switching stores information in several data structures instead of in a route cache for efficient packet forwarding performance in IPv6 multicast switching.
•IPv6 static multicast routes (mroutes) for IPv6—IPv6 static mroutes share the same database as IPv6 static routes and are implemented by extending static route support.
•IPv6 multicast address family support for multiprotocol Border Gateway Protocol (BGP)—The multiprotocol BGP for the IPv6 multicast address family feature provides multicast BGP (MBGP) extensions for IPv6 and supports the same features and functionality as IPv4 BGP. IPv6 enhancements to MBGP include support for an IPv6 multicast address family and network layer reachability information (NLRI) and next hop (the next router in the path to the destination) attributes that use IPv6 addresses.
•Reverse Path Forwarding (RPF) flooding of bootstrap router (BSR) packets—Cisco IOS IPv6 routers provide support for the RPF flooding of BSR packets so that a Cisco IOS IPv6 router will not disrupt the flow of bootstrap messages (BSMs).
•IPv6 Protocol Independent Multicast (PIM) accept register—IPv6 multicast supports PIM-SM register message filtering at the RP. The user can match an access list or compare the autonomous system (AS) path for the registered source with the AS path specified in a route map.
•Routable address hello option—When an IPv6 interior gateway protocol is used to build the unicast routing table, the procedure to detect the upstream router address assumes the address of a PIM neighbor is always same as the address of the next-hop router, as long as they see the same router. However, it may not be the case when a router has multiple addresses on a link. The routable address hello option allows the PIM protocol avoid such situation by adding a PIM hello message option that includes all the addresses on the interface on which the PIM hello message is advertised.
For additional information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_mcast.htm
IPv6 Multicast on Cisco 12000 Series Line Cards
In Cisco IOS Release 12.0(26)S, IPv6 multicast is supported on the Cisco 12000 series on the following line cards:
•IP Services Engine (ISE) line cards:
–4-port Gigabit Ethernet ISE
–4-port OC-3c/STM-1c POS/SDH ISE
–8-port OC-3c/STM-1c POS/SDH ISE
–16-port OC-3c/STM-1c POS/SDH ISE
–4-port OC-12c/STM-4c POS/SDH ISE
–1-port OC-48c/STM-16c POS/SDH ISE
•Engine 4 Plus (E4+) Packet-over-SONET (POS) line cards:
–4-port OC-48c/STM-16c POS/SDH
–1-port OC-192c/STM-64c POS/SDH
Note In future Cisco IOS software releases, IPv6 Multicast will be supported on other Cisco 12000 series line cards. IPv6 Multicast will not, however, be supported on the 8-port Fast Ethernet and 1-port Gigabit Ethernet Engine 1 line cards and the 3-port Gigabit Ethernet Engine 2 line card.
Forwarding of IPv6 multicast traffic is hardware-based on Cisco 12000 series IP Services Engine (ISE) line cards and software-based on all other supported Cisco 12000 series line cards.
IPv6 Multicast on Cisco 12000 Series ISE Line Cards
On Cisco 12000 series ISE line cards, IPv6 multicast is implemented so that if the number of IPv6 multicast routes exceeds the hardware capacity of the ternary content addressable memory (TCAM), the following error message is displayed to describe how to increase the TCAM hardware capacity for IPv6 multicast routes:
EE48-3-IPV6_TCAM_CAPACITY_EXCEEDED: IPv6 multicast pkts will be software switched.
To support more IPv6 multicast routes in hardware:
Get current TCAM usage with: show controllers ISE <slot> tcam
In config mode, reallocate TCAM regions e.g. reallocate Netflow TCAM to IPv6 Mcast
hw-module slot <num> tcam carve rx_ipv6_mcast <v6-mcast-percent>
hw-module slot <num> tcam carve rx_top_nf <nf-percent>
Verify with show command that sum of all TCAM regions = 100%
Reload the linecard for the new TCAM carve config to take effect
WARNING: Recarve may affect other input features(ACL,CAR,MQC,Netflow)
TCAM is used for IPv6 Multicast forwarding lookups. To increase TCAM capacity for handling IPv6 Multicast routes, you must use the hw-module slot number tcam carve rx_ipv6_mcast v6-mcast-percentage privileged EXEC command, in which the v6-mcast-percentage argument specifies the percentage of TCAM hardware that is used by the IPv6 Multicast prefix.
For example, you can change the IPv6 Multicast region from 1 percent (default) to 16 percent of the TCAM hardware by reallocating the NetFlow region from 35 percent (default) to 20 percent as follows:
Router#
hw-module slot 3 tcam carve rx_ipv6_mcast 16
Router#
hw-module slot 3 tcam carve rx_nf 20Configuring IPv6 Multicast
For information about how to configure and use IPv6 multicast, see the Implementing IPv6 Multicast document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_vcg.htm
IS-IS Local RIB Support for Faster IP Prefix RIB Installation
For detailed information about this feature, see the following document:
Link Bundling on Cisco 12000 Series Internet Routers
For detailed information about this feature, see the following document:
Logging to Local Non-Volatile Storage (ATA Disk)
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s26/cs_sysls.htm
Low Latency Queueing
For detailed information about this feature, see the following document:
Modular Quality of Service Command-Line Interface
For detailed information about this feature, see the following document:
MPLS—Aware NetFlow
For detailed information about this feature, see the following document:
MPLS—LDP Inbound Label Binding Filtering
For detailed information about this feature, see the following document:
MPLS—VRF Aware Static Labels
For detailed information about this feature, see the following document:
MPLS Fast Reroute Link Protection
For detailed information about this feature, see the following document:
MPLS Traffic Engineering Fast Reroute—Link Protection
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s26/fslin kpt.htm
MPLS Traffic Engineering—Fast Reroute MIB
For detailed information about this feature, see the following document:
MPLS Traffic Engineering LSP Attributes
For detailed information about this feature, see the following document:
MPLS Traffic Engineering—Verbatim Path Support
For detailed information about this feature, see the following document:
MPLS Virtual Private Networks (VPNs)
For detailed information about this feature, see the following document:
MPLS VPN—Route Target Rewrite
For detailed information about this feature, see the following document:
MPLS VPN—VRF Selection based on Source IP Address
For detailed information about this feature, see the following document:
Multicast-VPN—IP Multicast Support for MPLS VPNs
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fs_mvpn.htm
Multirouter Automatic Protection Switching (APS)
For detailed information about this feature, see the following document:
NetFlow BGP Next Hop Support
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123_1/nfbgpnxt.htm
Optical Power Monitor on Cisco 12000 Series ISE and Engine 4 DPT Line Cards
Platform: Cisco 12000 series
You can monitor the optical power that is received and that is transmitted from Spatial Reuse Protocol (SRP) ports using the show controllers srp EXEC command. This feature is available on the following Cisco 12000 series Dynamic Packet Transport (DPT) line cards:
•4-port OC-12c/STM-4c DPT ISE
•4-port OC-48c/STM-16 DPT
•1-port OC-192c/STM-64 DPT
For more information on the show controllers srp EXEC command and for sample output, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/srpapsgs.htm
OSPF MIB Support of RFC 1850 and Latest Extensions
This release updates the OSPF MIB support to the latest RFC 1850 and adds the latest draft extensions. For more information regarding the definitions of the draft extensions, see the CISCO-OSPF-MIB.my and CISCO-OSPF-TRAP-MIB.my files that are available through the Cisco MIB FTP site. MIB information is available at the following URL
http://tools.cisco.com/ITDIT/MIBS/servlet/index
For routers that are running Cisco IOS Release 12.0(26)S and later releases, the OSPF MIB and CISCO OSPF MIB will be supported only for the first OSPF process (except for MIB objects that are related to virtual links and sham links). SNMP traps will be generated for OSPF events that are related to any of the OSPF processes. There is no workaround for this situation.
The CISCO-OSPF-MIB.my is a read-only MIB.
Output Sampled Netflow
For detailed information about this feature, see the following document:
Packet Classification Using the Frame Relay DLCI Number
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s26/ftdlc26i.htm
Policer Enhancement: Multiple Actions
For detailed information about this feature, see the following document:
PVC Bundle Selection over ATM and FR
For detailed information about this feature, see the following documents:
•ATM PVC Bundle Enhancement—MPLS EXP-Based PVC Selection:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/atm.htm
•Frame Relay PVC Bundles with QoS Support for IP and MPLS:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/fr.htm
QoS: Color-Aware Policer
For detailed information about this feature, see the following document:
Quality of Service on Aggregate VLAN Traffic
For detailed information about this feature, see the following document:
Random Sampled NetFlow
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_2/nfstatsa.htm
Regex Engine Performance Enhancement
For detailed information about this feature, see the following document:
RSVP Message Authentication
For detailed information about this feature, see the following document:
RSVP Refresh Reduction and Reliable Messaging
For detailed information about this feature, see the following document:
Sampled NetFlow
For detailed information about this feature, see the following document:
Service Assurance Agent (SAA) MPLS VPN Operation
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ft1csaa.htm
SNMP—IP Precedence and DSCP Support
For detailed information about this feature, see the following document:
Source Specific Multicast (SSM) - Mapping
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_2/gtssmma.htm
Two-Rate Policer
For detailed information about this feature, see the following document:
New Hardware and Software Features in Cisco IOS Release 12.0(25)S1 to Cisco IOS Release 12.0(25)S4
There are no new hardware or software features in Cisco IOS Release 12.0(25)S1 to Cisco IOS Release 12.0(25)S4.
New Hardware Features in Cisco IOS Release 12.0(25)S
This section describes new and changed features in Cisco IOS Release 12.0(25)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(25)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
4-Port Gigabit Ethernet ISE Line Card
Platform: Cisco 12000 series
The 4-port Gigabit Ethernet IP Services Engine (ISE) line card provides a Cisco 12000 series with four optical Gigabit Ethernet interfaces on a single line card, while providing full edge engine capabilities. Because the total ingress bandwidth of all four ports (4 Gbps) exceeds the throughput capabilities of the line card (2.5 Gbps), a series of plim qos input commands were introduced into Cisco IOS software to identify high-priority traffic and pass it to the high-priority queues.
The line card provides high-speed interconnections to other network devices, such as other Cisco 12000 series, other routers, or Layer 2 and Layer 3 switches that support Gigabit Ethernet interfaces. For information about how to configure and use software features on the 4-port Gigabit Ethernet ISE line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/4ge_ ise.htm
4-Port OC-12c/STM-4c ATM ISE Line Card
Platform: Cisco 12000 series
The 4-port OC-12c/STM-4c ATM IP Services Engine (ISE) line card provides four 622-Mbps ATM interfaces and brings enhanced Layer 3 processing and high bandwidth ATM capabilities to the Cisco 12000 series.
The 4-port OC-12c/STM-4c ATM ISE line card supports IP services engine (ISE) features, including extensive traffic queueing, shaping, and congestion management features at a sustained full duplex throughput of 5.66 million cells per second. The line card also delivers a robust set of edge packet processing features, such as access control lists (ACLs), extended access control lists (EACLs), committed access rate (CAR), NetFlow, and Multicast with incorporated Modified Deficit Round Robin (MDRR), Weighted Random Early Detection (WRED), and backpressure congestion avoidance mechanism.
For information about how to configure and use these software features on the 4-port OC-12c/STM-4c ATM ISE line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/4atm _ise.htm
New Software Features in Cisco IOS Release 12.0(25)S
This section describes new and changed features in Cisco IOS Release 12.0(25)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(25)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Any Transport over MPLS (AToM): ATM Cell Relay over MPLS
The following sections describe the various Any Transport over MPLS (AToM): ATM Cell Relay over Multiprotocol Label Switching (MPLS) features:
• Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: Packed Cell Relay
• Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: Port Mode
• Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: VC Mode
• Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: VP Mode
Table 10 shows the platforms that support the new ATM cell relay features.
Note The following restriction pertains to the ATM Cell Relay over MPLS feature.
Traffic engineering (TE) tunnels: If you have TE tunnels that are running between provider edge (PE) routers, you must enable label distribution protocol (LDP) on the tunnel interfaces.Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: Packed Cell Relay
Platforms: Cisco 7200 series, Cisco 7500 series
The packed cell relay feature allows you to insert multiple concatenated ATM cells in an MPLS packet. The packed cell relay feature is more efficient than single cell relay, because each ATM cell is 52 bytes, and each AToM packet is at least 64 bytes. You configure the packed cell relay feature in ATM virtual path (VP) or virtual circuit (VC) mode.
For more information, see the "Configuring ATM Cell Relay over MPLS: Packed Cell Relay" section in the Any Transport over MPLS document at the following Cisco location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/atom 25s.htm
Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: Port Mode
Platform: Cisco 12000 series
Port mode cell relay allows a single cell that comes into an ATM interface to be packed into an MPLS packet and transported over the MPLS backbone to an egress ATM interface.
To configure port mode, enter the xconnect command from an ATM main interface and specify the destination address and the virtual circuit (VC) ID. The syntax and semantics of the xconnect command are the same as for all other transport types. Each ATM port is associated with one unique pseudowire VC label.
For more information, see the "Configuring ATM Cell Relay over MPLS: Port Mode" section in the Any Transport over MPLS document at the following Cisco location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/atom 25s.htm
Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: VC Mode
Platform: Cisco 12000 series
ATM Cell Relay over MPLS in virtual circuit (VC) mode enables you to configure ATM circuits on permanent virtual circuits (PVCs). This feature was introduced in Cisco IOS Release 12.0(23)S for the Cisco 7200 series and Cisco 7500 series. Release 12.0(25)S introduces this feature for the Cisco 12000 series.
For the Cisco 12000 series, label imposition is supported on all Engine 0 ATM line cards and on the Engine 2 8-port OC-3/STM-1 ATM line card. Label disposition is supported on all line cards.
For more information, see the "Configuring ATM Cell Relay over MPLS: VC Mode" section in the Any Transport over MPLS document at the following Cisco location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/atom 25s.htm
Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: VP Mode
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
Virtual path (VP) mode allows cells that come into a predefined permanent virtual path (PVP) on the ATM interface to be transported over the MPLS backbone to a predefined PVP on the egress ATM interface. You can use VP mode to send single cells or packed cells over the MPLS backbone.
To configure VP mode, you must specify the following:
•The VP is for transporting cell relay cells.
•The IP address of the peer provider edge (PE) router and the virtual circuit (VC) ID.
For more information, see the "Configuring ATM Cell Relay over MPLS: VP Mode" section in the Any Transport over MPLS document at the following Cisco location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/atom 25s.htm
Any Transport over MPLS (AToM): Distributed Mode for Frame Relay, PPP, and HDLC over MPLS
Platforms: Cisco 7500 series, Cisco 12000 series
Note Distributed Cisco Express Forwarding (CEF) is the only forwarding model supported on the Cisco 12000 series and is enabled by default. Disabling distributed CEF on the Cisco 12000 series disables forwarding.
Distributed Versatile Interface Processor (VIP) switching is supported on the Cisco 7500 series for Frame Relay, High-Level Data Link Control (HDLC), and PPP. In distributed VIP switching, the switching process occurs on the VIPs that support switching.
Distributed CEF mode is supported on the Cisco 7500 series for Frame Relay, High-Level Data Link Control (HDLC), and PPP. In distributed CEF mode, the switching process occurs on the VIPs that support switching. When distributed CEF is enabled, VIP port adapters maintain identical copies of the Forwarding Information Base (FIB) and adjacency tables. The port adapters perform the express forwarding between port adapters, relieving the Route Switch Processor (RSP) from performing the switching. Distributed CEF uses an interprocess communications (IPC) mechanism to ensure synchronization of FIBs and adjacency tables between the RSP and port adapters.
To enable distributed CEF on the Cisco 7500 series, enter the ip cef distributed global configuration command.
For more information, see the "How to Configure Distributed CEF Mode" section in the Any Transport over MPLS document at the following Cisco location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/atom 25s.htm
Any Transport over MPLS (AToM): Ethernet over MPLS: Port Mode
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
Note The Any Transport over MPLS (AToM): Ethernet over MPLS feature in VLAN mode was introduced in Cisco IOS Release 12.0(22)S for the Cisco 10720 and the Cisco 12000 series and in Release 12.0(23)S for the Cisco 7200 series and Cisco 7500 series. Release 12.0(25)S introduces the Any Transport over MPLS (AToM): Ethernet over MPLS: Port Mode feature. The Cisco 10720 has supported the Any Transport over MPLS (AToM): Ethernet over MPLS feature in both VLAN mode and Port mode since the introduction of the feature in Release12.0(22)S.
The Any Transport over MPLS (AToM): Ethernet over MPLS: Port Mode feature enables a frame that is coming into an interface to be packed into a Multiprotocol Label Switching (MPLS) packet and transported over the MPLS backbone to an egress interface. The entire Ethernet frame without the preamble or frame check sequence (FCS) is transported as a single packet. To configure port mode, use the xconnect command in main interface mode and specify the destination address and the virtual circuit (VC) ID. The syntax and semantics of the xconnect command are the same as for all other transport types. Each interface is associated with one unique pseudowire VC label.
For more information, see the "Configuring Ethernet over MPLS: Port Mode" section in the Any Transport over MPLS document at the following Cisco location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/atom 25s.htm
Any Transport over MPLS (AToM): Tunnel Selection
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10720, Cisco 12000 series
Note The Cisco 10720 supports the Any Transport over MPLS (AToM): Tunnel Selection feature in an Ethernet over MPLS (EoMPLS) configuration.
The Any Transport over MPLS (AToM): Tunnel Selection feature enables you to specify the path that traffic uses. You can specify either a Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnel or a destination IP address/DNS name.
You also have the option of specifying whether virtual circuits (VCs) should use the default path (the path that label distribution protocol [LDP] used for signaling) if the preferred path is unreachable. This option is enabled by default; you must explicitly disable it.
For more information, see the "How to Configure Tunnel Selection" section in the Any Transport over MPLS document at the following Cisco location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/atom 25s.htm
Cisco 12000 Series 4-Port OC-12c/STM-4c DPT ISE Line Card Enhancements
Platform: Cisco 12000 series
Starting in Cisco IOS Release 12.0(25)S, the following software features are now supported on Cisco 12000 series 4-port OC-12c/STM-4c DPT IP Services Engine (ISE) line cards:
• MPLS Virtual Private Networks on the 4-Port OC-12c/STM-4c DPT ISE Line Card
• FPGA Updates Using Field Diagnostics on the 4-Port OC-12c/STM-4c DPT ISE Line Card
MPLS Virtual Private Networks on the 4-Port OC-12c/STM-4c DPT ISE Line Card
The Cisco 12000 series 4-port OC-12c/STM-4c DPT ISE line card now supports the IP Virtual Private Network (VPN) feature for Multiprotocol Label Switching (MPLS). An MPLS VPN allows a Cisco IOS network to deploy scalable IPv4 Layer 3 VPN backbone services.
An IP VPN is the foundation companies use for deploying or administering value-added services including applications and data hosting network commerce, and telephony services to business customers. In private LANs, IP-based intranets have fundamentally changed the way companies conduct their business. Companies are moving their business applications to their intranets to extend over a WAN. Companies are also embracing the needs of their customers, suppliers, and partners by using extranets (an intranet that encompasses multiple businesses). With extranets, companies reduce business process costs by facilitating supply-chain automation, electronic data interchange (EDI), and other forms of network commerce. To take advantage of this business opportunity, service providers must have an IP VPN infrastructure that delivers private network services to businesses over a public infrastructure.
For information about how to configure and use the MPLS VPN feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fsvp n23.htm
FPGA Updates Using Field Diagnostics on the 4-Port OC-12c/STM-4c DPT ISE Line Card
You can use the diag slot-number update-fpga command in privileged EXEC mode to update Flash memory with field-programmable gate array (FPGA) images from the current field diagnostics download image in a Cisco 12000 series 4-port OC-12c/STM-4c DPT ISE line card.
When you update Flash memory with an FPGA image, note the following restrictions:
•This diag option limits your field diagnostics session to one task: updating the FPGA images in Flash memory on the line card. No other testing is performed during this session.
•This diag option updates all FPGA images in Flash memory. This process is nonselective in cases in which a line card contains multiple FPGAs.
For more information about how to update FPGA images in Flash memory, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/diag .htm
Distributed Frame Relay Switching
Platform: Cisco 7500 series
The Distributed Frame Relay Switching feature enables Frame Relay switching, modular quality of service (QoS) command-line interface (CLI) (MQC) traffic shaping, MQC policing, and end-to-end FRF.12 fragmentation to occur locally on the Versatile Interface Processor (VIP) line cards. Enabling these processes to occur locally relieves the Route Switch Processor (RSP) of involvement in the switching and packet-handling operation.
Ethernet MDI/MDI-X Support on the Cisco 10720
Platform: Cisco 10720
The Ethernet MDI/MDI-X Support on the Cisco 10720 feature is documented in the following two sections:
• Revision B Ethernet Access Card
• media-type Command on the Cisco 10720
Revision B Ethernet Access Card
The combined 4-port Gigabit Ethernet 8-port 10/100 Ethernet TX access module that is used in the Cisco 10720 router is now available in a new revision—Revision B.
The Revision B Ethernet access module provides a configurable option for Fast Ethernet TX ports on the Cisco 10720 router. You can configure an Ethernet TX port on the Revision B access module for a media-dependent interface (MDI) or media-dependent interface crossed-over (MDI-X) cable connection. Also, you can configure a Fast Ethernet TX port to autosense the connection type (MDI or MDI-X) and autoconfigure the port to the right mode.
Ethernet ports on servers normally use an MDI connector. Ethernet ports on a hub normally use an MDI-X connector. An Ethernet straight-through cable (commonly available) is used to connect an MDI to an MDI-X port. A cross-over cable (less commonly available) is used to connect an MDI to an MDI port, or an MDI-X to an MDI-X port.
The PHY chips used on the Revision B Ethernet access module provide support for the following types of cable connections on a Fast Ethernet TX port:
•Cross-over cable to connect a media-dependent interface (MDI) port to a 10720 Fast Ethernet TX port in MDI mode.
•Cross-over cable to connect a media-dependent interface crossed-over (MDI-X) port to a 10720 Fast Ethernet TX port in MDI-X mode.
•Straight-through cable to connect an MDI port to a Cisco 10720 Fast Ethernet TX port in MDI-X mode, or an MDI-X port to a Cisco 10720 Fast Ethernet TX port in MDI mode.
The Revision B Ethernet access module provides the flexibility to configure an Ethernet TX port on the Cisco 10720 router as MDI or MDI-X according to the network device connected to the port, therefore allowing for the use of a straight-through cable for all combinations.
media-type Command on the Cisco 10720
To configure the type of cable connector used on a Fast Ethernet TX interface on the combined 4-port Gigabit Ethernet 8-port 10/100 Ethernet TX access module, use the media-type {auto | mdi | mdix} command in interface configuration mode.
The media-type command allows you to configure a media-dependent interface (MDI) connection, a media-dependent interface crossed-over interface (MDI-X) connection, or an autoconfiguration mode that automatically configures the required type of cable connector setting.
For the Revision A Ethernet access card, the default cable connector setting is mdix, except in Japan where it is possible to use the media-type command to change the cable connection type. On the Revision B Ethernet access card, the default setting for a Fast Ethernet TX interface is auto.
For more detailed information about how to use the media-type command, see the "Command Reference" section in the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/1072 0.htm
IPv6 Hardware-Assisted Enhancements on Cisco 12000 IP Services Engine (ISE) Line Cards
Platform: Cisco 12000 series
The following software features are now processed in the hardware of Cisco 12000 series ISE line cards:
• IPv6 Extended Access Control Lists on IP Services Engine (ISE) Line Cards
• IPv6 Provider Edge Router over MPLS (Cisco 6PE) on IP Services Engine (ISE) Line Cards
Hardware-assisted IPv6 extended access controls lists (ACLs) and Cisco 6PE are supported on the following Cisco 12000 series ISE line cards:
•4-port OC-3c/STM-1c POS/SDH ISE line card
•8-port OC-3c/STM-1c POS/SDH ISE line card
•16-port OC-3c/STM-1c POS/SDH ISE line card
•4-port OC-12c/STM-4c POS/SDH ISE line card
•1-port OC-48c/STM-16c POS/SDH ISE line card
•4-port Channelized OC-12/STM-4 (DS3/E3, OC-3c/STM-1c) POS/SDH ISE line card
•1-port Channelized OC-48/STM-16 (DS3/E3, OC-3c/STM-1c, OC-12c/STM-4c) POS/SDH line card
•4-port Gigabit Ethernet ISE line card
Note In Cisco IOS Release 12.0(25)S, hardware-assisted IPv6 extended ACLs and Cisco 6PE are not supported on the 4-port OC-12c/STM-4c ATM ISE line card.
For complete information about how to configure and use these IPv6 features, see the IPv6 for Cisco IOS Software documents at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
IPv6 Extended Access Control Lists on IP Services Engine (ISE) Line Cards
On Cisco 12000 series ISE line cards, standard IPv6 access control list (ACL) functionality is used for basic traffic filtering functions—traffic filtering is based on source and destination addresses, inbound and outbound to a specific interface, and with an implicit deny statement at the end of each access list (which is functionally similar to standard ACLs in IP version 4 [IPv4]).
IPv6 ACLs are defined and their deny and permit conditions are set by using the ipv6 access-list command with the deny and permit keywords in global configuration mode.
Starting in Cisco IOS Release 12.0(25)S, the standard IPv6 ACL functionality is extended to support—in addition to traffic filtering based on source and destination addresses—filtering of traffic based on IPv6 option headers, flow label, and optional, upper-layer protocol type information for finer granularity of control (functionality similar to extended ACLs in IPv4). IPv6 ACLs are defined by using the ipv6 access-list command in global configuration mode and their permit and deny conditions are set by using the deny and permit commands in IPv6 access list configuration mode. (Configuring the ipv6 access-list command places the router in IPv6 access list configuration mode, from which permit and deny conditions can be set for the defined IPv6 ACL.)
For more information about IPv6 extended access control lists, see the "IPv6 Access Control Lists" section in the "IPv6 for Cisco IOS Software, File 1 of 3: Overview" chapter of the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/ftipv6o.ht m
IPv6 Provider Edge Router over MPLS (Cisco 6PE) on IP Services Engine (ISE) Line Cards
The IPv6 Provider Edge Router over MPLS (Cisco 6PE) feature enables service providers that are running an MPLS/IPv4 infrastructure to offer IPv6 services on an MPLS network. A Cisco 6PE-enabled backbone allows IPv6 domains to communicate with each other over an MPLS IPv4 core network. A Cisco 6PE implementation requires no backbone infrastructure upgrades and no reconfiguration of core routers, because forwarding is based on labels rather than on the IPV6 header itself.
Additionally, the inherent Virtual Private Network (VPN) and Traffic Engineering (TE) services available within an MPLS environment allow IPv6 networks to be combined into VPNs or extranets over an infrastructure that supports IPv4 VPNs and MPLS-TE.
The provider edge (PE) routers at each end of the MPLS network must be IPv6-enabled. The PE routers apply an appropriate label for the address in the packet to reach the other side of the MPLS backbone. This is similar to tunneling because it allows IPv6 traffic to be transported over MPLS without the routers in the backbone being aware of the IPv6 traffic. An MPLS packet enters and exits the MPLS network on different routers, and each router must be IPv6- and 6PE-enabled.
For more information about the IPv6 Provider Edge Router over MPLS (Cisco 6PE) feature, see the "IPv6 Provider Edge Router over MPLS" section in the "IPv6 for Cisco IOS Software, File 1 of 3: Overview" chapter of the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/ftipv6o.ht m
IS-IS Limit on Number of Redistributed Routes
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
The IS-IS Limit on Number of Redistributed Routes feature provides a user-defined maximum number of prefixes that are allowed to be redistributed into Intermediate System-to-Intermediate System (IS-IS) from other protocols or other IS-IS processes. Such a limit could help prevent the router from being flooded by too many redistributed routes.
For more information about the IS-IS Limit on Number of Redistributed Routes feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/fsire dis.htm
Note Support for the IS-IS Limit on Number of Redistributed Routes feature is introduced on the Cisco 10000 series in Cisco IOS Release 12.0(25)S1.
Layer 2 Tunnel Protocol Version 3 on Cisco 12000 Series 1-Port Channelized OC-12 (DS3) Line Cards
Platform: Cisco 12000 series
Starting in Cisco IOS Release 12.0(25)S, Layer 2 Tunnel Protocol version 3 (L2TPv3) is supported on Cisco 12000 series 1-port channelized OC-12 (DS3) line cards.
Note L2TPv3 support on Cisco 12000 series 1-port channelized OC-12 (DS3) line cards is also included in Release 12.0(23)S3 and Release 12.0(24)S1.
For information about how to configure and use L2TPv3, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/l2tp v325.htm
Link Fragmentation and Interleaving
Platform: Cisco 10000 series
Note This section describes the Link Fragmentation and Interleaving for Multilink PPP feature and the Frame Relay Fragmentation (FRF.12) feature. These two features are also referred to as the Link Fragmentation and Interleaving (LFI) feature.
Interactive traffic (Telnet, Voice on IP, and the like) is susceptible to increased latency and jitter when the network processes large packets (LAN-to-LAN FTP transfers that traverse a WAN link, for example), especially as they are queued on slower links.
The Link Fragmentation and Interleaving (LFI) feature reduces delay and jitter on slower-speed links by breaking up large datagrams and interleaving low-delay traffic packets (such as voice) with the smaller packets that result from the fragmented datagram. LFI was designed especially for lower-speed links in which serialization delay is significant.
LFI Benefit
The Cisco 10000 series implementation of LFI provides the following benefits:
•Supports the following encapsulation protocols:
–Multilink PPP (MLP)
–Frame Relay (FRF.12) end-to-end
•Supports LFI on up to 1000 Cisco 10000 series interfaces.
•Prioritized traffic is always sent intact, while all other traffic is subject to fragmentation.
•During packet reassembly, the Cisco 10000 series detects and discards any packets that are missing fragments.
Cisco 10000 Series LFI Limitations and Restrictions
The following limitations and restrictions apply to the Cisco 10000 series implementation of LFI:
•Multilink LFI is restricted to 1-link bundles only.
•MLP must be enabled on an interface that has interleaving turned on.
•To enable LFI on an MLP interface, use the ppp multilink interleave command.
•MLP over ATM (MLPoATM) is not supported.
•The show frame-relay fragment command does not support the following statistics:
–fragments received (in_frag)
–fragments dropped (drop_frag)
–fragments transmitted (out_frag)
•The show frame-relay fragment interface command does not support the following statistics:
–in fragmented pkts
–in fragmented bytes
–in dropped reassembling packets
–in timeouts
–out interleaved packets
–out fragmented pkts
–out fragmented bytes
–out dropped fragmenting pkts
Further Information
For further information about the Link Fragmentation and Interleaving feature, see the "Link Fragmentation and Interleaving" section of the Release Notes for the Cisco 10000 Series ESR for Cisco IOS Release 12.0(23)SX at the following Cisco location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10krn/rn_23sx.htm
Note Support for the Link Fragmentation and Interleaving feature is introduced on the Cisco 10000 series in Cisco IOS Release 12.0(25)S1.
MQC Bandwidth in Absolute Values on the Cisco 10720
Platform: Cisco 10720
In Cisco IOS Release 12.0(24)S and earlier releases, the Cisco 10720 router supported only the percent percentage parameter in the bandwidth, priority, and shape modular QoS CLI (MQC) commands.
Starting in Cisco IOS Release 12.0(25)S, the Cisco 10720 router also supports the bandwidth-kbps parameter so that the command syntax in policy-map class configuration mode is as follows:
•bandwidth {percent percentage | bandwidth-kbps}
•priority {percent percentage | bandwidth-kbps}
•shape {percent percentage | bandwidth-kbps}
Syntax Description
On the Cisco 10720, the bandwidth, priority, and shape commands are implemented so that, when you enter a bandwidth value in kilobits per second (bandwidth-kbps), the kbps value is internally converted to a number between 0 and 1023, where 1023 represents the full bandwidth in kbps of the interface or subinterface.
For more detailed information about how to use the bandwidth, priority, and shape commands on the Cisco 10720 router, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/1072 0.htm
For more information about standard MQC command usage, see the Cisco documents at the following locations:
•bandwidth command:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_r/qrfcmd1.htm
•priority command:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_r/qrfcmd6.htm
•shape command:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_r/qrfcmd9.htm
MPLS Quality of Service Enhancements on Cisco 12000 Series Engine 2 Line Cards
Platform: Cisco 12000 series
Note MPLS Class of Service is now referred to as MPLS Quality of Service. This transition reflects the growth of Multiprotocol Label Switching (MPLS) to encompass a wider meaning in the Any Transport over MPLS (AToM) product set.
The MPLS Quality of Service (QoS) enhancement allows service providers to set the MPLS experimental field value without modifying the value of the IP precedence field in IP packets that are transported through an MPLS core network. By choosing different values for the MPLS experimental field, service providers can mark packets based on their characteristics, such as rate or type, so that packets have the priority that they require during periods of congestion.
The following Cisco 12000 series Engine 2 (E2) line cards now support the setting of the MPLS experimental field value:
•1-port OC-48c/STM-16c POS/SDH
•3-port Gigabit Ethernet
•4-port OC-12c/STM-4c POS/SDH
•8-port OC-3c/STM-1c POS/SDH
•16-port OC-3c/STM-1c POS/SDH
When a customer transmits IP packets from one site to another, the IP precedence field (the first three bits of the differentiated services code point [DSCP] field in the header of an IP packet) specifies the quality of service. Based on the IP precedence marking, the packet is given the desired treatment such as the latency or the percent of bandwidth allowed for that quality of service. If the service provider network is an MPLS network, the IP precedence bits are copied into the MPLS experimental (EXP) field at the edge of the network. However, the service provider might want to set an MPLS packet's QoS to a different value determined by the service offering.
This feature allows the service provider to set the MPLS experimental field instead of overwriting the value in the customer's IP precedence field. The IP header remains available for the customer's use; the IP packet's QoS is not changed as the packet travels through the MPLS network.
As implemented on Cisco 12000 series Engine 2 line cards in Cisco IOS Release 12.0(25)S, the MPLS QoS enhancement is not supported on the 4-port OC-12/STM-c ATM and 8-port OC-3/STM-1c ATM line cards. The MPLS QoS enhancement is implemented in the Packet Switching ASIC (PSA) for fast path packet-forwarding operations.
For more information about how to use and configure MPLS QoS, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st14/mc t1214t.htm
Multicast-VPN—IP Multicast Support for MPLS VPNs
Platform: Cisco 10000 series
The Multicast-VPN—IP Multicast Support for MPLS VPNs feature enables a service provider to configure and support multicast traffic in a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) environment. This feature supports routing and forwarding of multicast packets for each individual VPN routing and forwarding (VRF) instance, and it also provides a mechanism to transport VPN multicast packets across the service provider backbone.
The Multicast-VPN—IP Multicast Support for MPLS VPNs feature in Cisco IOS software provides the ability to support the multicast feature over a Layer 3 VPN. As enterprises extend the reach of their multicast applications, service providers can accommodate these enterprises over their MPLS core network. IP multicast is used to stream video, voice, and data to an MPLS VPN network core.
A VPN is network connectivity across a shared infrastructure, such as an Internet service provider (ISP). Its function is to provide the same policies and performance as a private network, at a reduced cost of ownership, thus creating many opportunities for cost savings through operations and infrastructure.
Historically, IP in IP generic routing encapsulation (GRE) tunnels was the only way to connect through a service provider network. Although such tunneled networks tend to have scalability issues, they represent the only means of passing IP multicast traffic through a VPN.
MPLS was derived from tag switching and various other vendor methods of IP-switching support enhancements in the scalability and performance of IP-routed networks by combining the intelligence of routing with the high performance of switching. MPLS is now used for VPNs, which is an appropriate combination because MPLS decouples information used for forwarding of the IP packet (the label) from the information carried in the IP header.
A Multicast-VPN allows an enterprise to transparently interconnect its private network across the network backbone of a service provider. The use of a Multicast-VPN to interconnect an enterprise network in this way does not change the way that enterprise network is administered, nor does it change general enterprise connectivity.
Because MPLS VPNs support only unicast traffic connectivity, deploying the Multicast-VPN feature in conjunction with MPLS VPN allows service providers to offer both unicast and multicast connectivity to MPLS VPN customers.
For more information about the Multicast-VPN—IP Multicast Support for MPLS VPNs feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fs_mvpn.h tm
Note Support for the Multicast-VPN—IP Multicast Support for MPLS VPNs feature is introduced on the Cisco 10000 series in Cisco IOS Release 12.0(25)S1.
OSPF Limit on Number of Redistributed Routes
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
The OSPF Limit on Number of Redistributed Routes feature provides a user-defined maximum number of prefixes (routes) that are allowed to be redistributed into Open Shortest Path First (OSPF) from other protocols or other OSPF processes. Such a limit could help prevent the router from being flooded by too many redistributed routes.
For more information about the OSPF Limit on Number of Redistributed Routes feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/fsor edis.htm
Note Support for the OSPF Limit on Number of Redistributed Routes feature is introduced on the Cisco 10000 series in Cisco IOS Release 12.0(25)S1.
OSPF Link-State Advertisement (LSA) Throttling
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
The OSPF Link-State Advertisement (LSA) Throttling feature provides a dynamic mechanism to slow down LSA updates in Open Shortest Path First (OSPF) during times of network instability. It also allows faster OSPF convergence by providing LSA rate-limiting in milliseconds.
For more information about the OSPF Link-State Advertisement (LSA) Throttling feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/fsols ath.htm
Note Support for the OSPF Link-State Advertisement (LSA) Throttling feature is introduced on the Cisco 10000 series in Cisco IOS Release 12.0(25)S1.
Single Rate 3-Color Marker for Traffic Policing
Platforms: Cisco 10000 series, Cisco 10720
The Single Rate 3-Color Marker for Traffic Policing feature meters an IP packet stream and marks its packets with different colors, based on the Committed Information Rate (CIR) and two associated burst sizes: Committed Burst Size (CBS) and Excess Burst Size (EBS). CIR is measured in bytes of IP packets per second (and it includes the IP header, but not link-specific headers). CBS and EBS are measured in bytes.
In earlier releases, the Cisco 10000 series and the Cisco 10720 supported a single rate, 2-color marker. The single rate, 3-color marker allows the Cisco 10000 series and the Cisco 10720 to classify packets that violate the EBS. This feature is useful, for example, for ingress policing of a service, where service eligibility is determined only by the length of the burst, and not by the peak rate of the burst.
The single rate 3-color marker uses the following colors to classify packets:
•Green (conforming)—Packet size is less than or equal to the CBS value and within the CIR allowance.
•Yellow (exceeding)—Packet size is greater than the CIR allowance but is less than or equal to the EBS value and within the available surplus.
•Red (violating)—Packet size is greater than both the CIR allowance and the available surplus. This is either because the packet size exceeds the EBS or because a previous packet used some of the surplus and the traffic since then has not slowed sufficiently to acquire the surplus needed for the current packet.
The marker starts with a surplus equal to the EBS and replenishes the surplus by the amount of unused CIR allowance until the surplus reaches the EBS.
The 3-color marker can be used to mark a packet stream in a service in which different, decreasing levels of assurances (either absolute or relative) are given to packets which are green, yellow, or red. For example, a service might do the following:
•Discard or deny all red packets because they exceed both the committed and excess burst sizes.
•Forward green packets because they are guaranteed for delivery.
Configuring the Single Rate 3-Color Marker for Traffic Policing Feature on the Cisco 10000 Series
To configure the Single Rate 3-Color Marker for Traffic Policing feature, do the following:
•Use the police command to set the feature's mode and to assign values for the CIR, CBS, and EBS:
Router(config-pmap-c)#
police CIR CIR_bps burst-normal burst-max conform-action action exceed-action action violate-action actionFor conform, exceed, and violate action, you can specify one of the following actions: transmit, set-dscp-transmit, set-prec-transmit, set-mpls-exp-transmit, or set-qos-transmit.
Configuring the Single Rate 3-Color Marker for Traffic Policing Feature on the Cisco 10720
For information about how to configure the Single Rate 3-Color Marker for Traffic Policing feature on the Cisco 10720, see the "police" section in the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/1072 0.htm
Note Support for the Single Rate 3-Color Marker for Traffic Policing feature is introduced on the Cisco 10000 series in Cisco IOS Release 12.0(25)S1.
New Hardware and Software Features in Cisco IOS Release 12.0(24)S1 to Cisco IOS Release 12.0(24)S6
There are no new hardware or software features in Cisco IOS Release 12.0(24)S1 to Cisco IOS Release 12.0(24)S6.
New Hardware Features in Cisco IOS Release 12.0(24)S
This section describes new and changed features in Cisco IOS Release 12.0(24)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(24)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
4-Port OC-12c/STM-4c DPT ISE Line Card
Platform: Cisco 12000 series
The 4-Port OC-12c/STM-4c DPT ISE line card provides connections for two complete OC-12c/STM-4c SRP nodes through the use of four full-duplex, single-mode, duplex LC connections.
The line card is available in the following versions:
•Intermediate-reach (IR) 1310 nm with a typical reach of 9.3 miles (15 km)
•Extended-reach (XR) 1550 nm with a typical reach of 49.7 miles (80 km)
For information about how to install and configure the line card, see the document at the following location:
http://cisco.com/push_targets1/ucdit/cc/td/doc/product/core/cis12000/linecard/lc_srp/14701srp.htm
New Software Features in Cisco IOS Release 12.0(24)S
This section describes new and changed features in Cisco IOS Release 12.0(24)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(24)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
ATM OAM Support for F5 Continuity Check
Platform: Cisco 12000 series
The ATM OAM Support for F5 Continuity Check feature introduces Operation, Administration, and Maintenance (OAM) support for the use of F5 segment and end-to-end continuity check (CC) cells to detect connectivity failures at the ATM layer. This feature also introduces new Simple Network Management Protocol (SNMP) notifications that are generated when CC cells indicate virtual circuit (VC) connectivity failure.
ATM OAM F5 CC cells provide an in-service tool optimized to detect connectivity problems at the VC level of the ATM layer. CC cells are sent between a router designated as the source location and a router designated as the sink location. The local router can be configured as the source, as the sink, or as both the source and the sink.
This feature implements two types of OAM cells: CC cells for fault management and CC cells for activation and deactivation. Fault management cells detect connectivity failures. Activation and deactivation cells initiate the activation or deactivation of continuity checking.
BGP Configuration Using Peer Templates
The BGP Configuration Using Peer Templates feature introduces a new mechanism that groups distinct neighbor configurations for Border Gateway Protocol (BGP) neighbors that share common policies. This type of policy configuration has been traditionally configured with BGP peer-groups. However, peer-groups have certain limitations because peer-group configuration is bound to update grouping and specific session characteristics. Configuration templates provide an alternative to peer-group configuration and overcome some of the limitations of peer-groups.
Configuration templates are configured and stored separately from update groups. Update grouping occurs automatically with the BGP Dynamic Update Peer-Group feature. There are two types of configuration templates: peer-policy templates and peer-session templates. Peer-policy templates are used to configure policy-related commands and do not allow session commands. Peer-session templates are used for the configuration of general session commands. General session commands that are common for neighbors that are configured in different address families can be configured within the same peer-session template. Configuration templates also support inheritance. Peer-policy templates can inherit up to five templates, whereas peer-session templates can inherit only one template.
With the configuration of the BGP Configuration Using Peer Templates feature and the support of the BGP Dynamic Update Peer-Groups feature, the network operator no longer needs to configure peer-groups in BGP and can benefit from improved configuration flexibility and system performance. However, peer-groups are still supported and do not conflict with this feature.
see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/s_bg pct.htm
BGP Cost Community
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
The BGP Cost Community feature introduces a new Border Gateway Protocol (BGP) extended community attribute called the cost community. The cost community is a nontransitive extended community attribute that is passed to internal BGP (iBGP) and confederation peers but not to external BGP (eBGP) peers. The cost community allows the network operator to customize the local route preference and influence best path selection process for specific paths. The cost community is applied to and configured for specific paths with set clauses in route maps. Multiple instances of the cost community can be configured for separate paths within the same autonomous system or confederation. The route with the lowest cost community ID will be preferred in this case.
see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/s_bg pcc.htm
BGP Dynamic Update Peer-Groups
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series, Cisco 12000 series
The BGP Configuration Using Peer Templates feature introduces a new mechanism that groups distinct neighbor configurations for Border Gateway Protocol (BGP) neighbors that share common policies. This type of policy configuration has been traditionally configured with BGP peer-groups. However, peer-groups have certain limitations because peer-group configuration is bound to update grouping and specific session characteristics. Configuration templates provide an alternative to peer-group configuration and overcome some of the limitations of peer-groups.
see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/s_bg pdpg.htm
BGP Link Bandwidth
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series, Cisco 12000 series
The Border Gateway Protocol (BGP) Link Bandwidth feature is used to advertise the bandwidth of an autonomous system exit link as an extended community. The BGP Link Bandwidth feature is supported by the internal BGP (iBGP) and external BGP (eBGP) multipath features. The link bandwidth extended community indicates the preference of an autonomous system exit link in terms of bandwidth. The link bandwidth extended community attribute may be propagated to all iBGP peers and used with the BGP multipath features to configure unequal cost load balancing. When a router receives a route from a directly connected external neighbor and advertises this route to iBGP neighbors, the router may advertise the bandwidth of that link.
see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ftbgplb.htm
BGP Multipath Load Sharing for Both eBGP and iBGP in an MPLS-VPN
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series, Cisco 12000 series
The BGP Multipath Load Sharing for eBGP and iBGP feature allows you to configure multipath load balancing with both external BGP (eBGP) and internal BGP (iBGP) paths in Border Gateway Protocol (BGP) networks that are configured to use Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). This feature provides improved load-balancing deployment and service-offering capabilities and is useful for multihomed autonomous systems and provider edge (PE) routers that import both eBGP and iBGP paths from multihomed and stub networks.
see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/
s_eibmpl.htmBGP Route-map Continue
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series, Cisco 12000 series
The BGP Route-map Continue feature introduces the continue clause to Border Gateway Protocol (BGP) route-map configuration. The continue clause allows for more programmable policy configuration and route filtering and introduces the capability to execute additional entries in a route map after an entry is executed with successful match and set clauses. Continue clauses allow the network operator to configure and organize more modular policy definitions so that specific policy configurations need not be repeated in different route maps. Only inbound route maps are supported.
see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sb/newft/122sbc27/gt_brmcs.htm
Cisco 12000 Series Engine 4 Plus DPT Line Card Enhancements
New software features have been added to Cisco 12000 Series Engine 4 Plus (E4+) Dynamic Packet Transport (DPT) line cards such as the following:
•Cisco 12000 Series Four-Port OC-48c/STM-16c DPT line card
•Cisco 12000 Series One-Port OC-192c/STM-64c DPT line card
Starting in Cisco IOS Release 12.0(24)S, the following software features are now supported on Cisco 12000 Series E4+ DPT line cards:
• MPLS Virtual Private Networks (VPNs)
• MPLS Quality of Service (QoS)
• MPLS Time To Live (TTL) Propagation from IP
• Modular Quality of Service Command-Line Interface
MPLS Virtual Private Networks (VPNs)
The IP Virtual Private Network (VPN) feature for Multiprotocol Label Switching (MPLS) allows a Cisco IOS network to deploy scalable IPv4 Layer 3 VPN backbone services. An IP VPN is the foundation companies use for deploying or administering value-added services including applications and data hosting network commerce and telephony services to business customers.
For more information about how to configure and use a VPN, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fsvp n22.htm
MPLS Quality of Service (QoS)
MPLS Class of Service (CoS) functionality enables network administrators to provide differentiated services across an MPLS network. Network administrators can satisfy a wide range of networking requirements by specifying the class of service applicable to each transmitted IP packet. Different classes of service can be established for IP packets by setting the IP precedence bit in the header of each packet.
Starting in Cisco IOS Release 12.0(24)S, the following MPLS CoS features are supported on Cisco 12000 Series E4+ DPT line cards:
•Packet classification using committed access rate (CAR). Packets are classified at the edge of the network before labels are assigned.
•Congestion avoidance using weighted random early detection (WRED). Packet classes are differentiated on the basis of drop probability.
•Congestion management using modified deficit round robin (MDRR) for Cisco 12000 series Internet routers. Packet classes are differentiated on the basis of bandwidth requirements and finite delay characteristics.
Note MPLS Class of Service is now referred to as MPLS Quality of Service (QoS). This transition reflects the growth of MPLS to encompass a wider meaning and highlight the path towards future enhancements.
For more information about how to configure MPLS CoS/QoS features, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fs22 cos.htm
MPLS Time To Live (TTL) Propagation from IP
To control the generation of the time to live (TTL) field in the MPLS header when labels are first added to an IP packet, E4+ DPT line cards support the use of the mpls ip propagate-ttl global configuration command. For more information on this command, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122sup/122csum/csum2/122csswt/xs fscmd3.htm
DPT Mapping to SRP Priority
Cisco 12000 Series E4+ DPT line cards support the use of the srp priority-map transmit min-tos-value command to set the priority map used for transmitting data packets, where the min-tos-value argument indicates the minimum type of service (ToS) value used to forward packets to the high-priority transmit queue.
For information about how to use this command to configure the Spatial Reuse Protocol (SRP) priority map, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/srpapsgs.htm #xtocid12
Multicast Forwarding
The Multicast Forwarding feature on Cisco 12000 Series E4+ DPT line cards allows hardware-based fast forwarding of IPv4 multicast traffic, resulting in high throughputs and performance.
For more information about the hardware forwarding of IP multicast packets and how to enable it on E4+ DPT line cards, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/mca st.htm
Modular Quality of Service Command-Line Interface
The modular quality of service (QoS) feature allows you to specify a traffic class independently of QoS policies. You use the modular QoS command-line interface (MQC) to configure (QoS) policies that you apply to an E4+ DPT interface. In Cisco IOS Release 12.0(24)S, QoS policies configured with MQC are supported only in the outbound direction on Cisco 12000 Series E4+ DPT interfaces.
For complete documentation on MQC configuration commands and tasks, and how to use MQC, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5/mq c/
Cisco 12000 Series IP Services Engine (ISE) Line Card Enhancements
New software features have been added to Cisco 12000 Series IP Services Engine (ISE) line cards such as the following:
•Cisco 12000 Series Four-Port OC-3c/STM-1c POS/SDH ISE line card
•Cisco 12000 Series Eight-Port OC-3c/STM-1c POS/SDH ISE line card
•Cisco 12000 Series Sixteen-Port OC-3c/STM-1c POS/SDH ISE line card
•Cisco 12000 Series Four-Port OC-12c/STM-4c POS/SDH ISE line card
•Cisco 12000 Series One-Port OC-48c/STM-16c POS/SDH ISE line card
•Cisco 12000 Series Four-Port Channelized OC-12/STM-4 (DS3/E3, OC-3c/STM-1c) POS/SDH ISE line card
•Cisco 12000 Series One-Port Channelized OC-48/STM-16 (DS3/E3, OC-3c/STM-1c) POS/SDH ISE line card
Starting in Cisco IOS Release 12.0(24)S, the following software features are now supported on Cisco 12000 Series ISE line cards:
• MPLS Traffic Engineering Fast Reroute (FRR)
• MPLS VPN—VRF Selection based on Source IP Address
• Source based BGP Policy Accounting Release
• Cisco Nonstop Forwarding (NSF)
MPLS Traffic Engineering Fast Reroute (FRR)
The MPLS Traffic Engineering Fast Reroute (FRR) — Link Protection feature is supported on Cisco 12000 Series ISE line cards. The Fast Reroute feature provides link protection to label-switched paths (LSPs).
Regular MPLS traffic engineering automatically establishes and maintains label-switched paths across the backbone using the Resource Reservation Protocol (RSVP). The path used by a given LSP at any point in time is based upon the LSP resource requirements and available network resources such as bandwidth.
Available resources are flooded via extensions to a link-state based Interior Gateway Protocol (IGP), such as Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF). Paths for LSPs are calculated at the LSP headend. Under failure conditions, the headend determines a new route for the LSP. Recovery at the headend provides for the optimal use of resources. However, because of messaging delays, the headend cannot recover as fast as possible by making a repair at the point of failure.
By providing link protection to LSPs, the Fast Reroute feature enables all traffic carried by LSPs that traverse a failed link to be rerouted around the failure. The reroute decision is completely controlled locally by the router interfacing the failed link. The headend of the tunnel is also notified of the link failure through IGP or RSVP; the headend then attempts to establish a new LSP that bypasses the failure.
For more information about the MPLS FRR feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fs_f rrnd.htm
MPLS VPN—VRF Selection based on Source IP Address
The VPN Routing and Forwarding (VRF) Selection feature allows a Cisco 12000 series ISE interface on a provider edge (PE) router to route packets to different Virtual Private Networks (VPNs) on the basis of the source IP address of the packet. This feature is an improvement over using a policy-based router to route packets to different VPNs.
The VRF Selection feature allows packets that arrive on an interface to be switched into the appropriate VRF table on the basis of the source IP address of the packets. Once the packets have been "selected" into the correct VRF routing table, they are processed normally on the basis of the destination address and forwarded through the rest of the Multiprotocol Label Switching (MPLS) VPN.
For more information about the MPLS VPN - VRF Selection feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/vrfs elec.htm
Source based BGP Policy Accounting Release
The BGP policy accounting feature allows you to account for IP traffic differentially by assigning counters based on community list, autonomous system (AS) number, and/or AS-path on a per input interface basis. For the policy accounting feature to work, you must enable BGP and Cisco Express Forwarding/distributed Cisco Express Forwarding (CEF/dCEF) on the Cisco 12000 series Internet router.
Using BGP policy accounting, you can account for traffic (and apply billing) according to the route it traverses. For example, you can account for traffic that is routed by domestic, international, terrestrial, or satellite routes. In this way, you can identify and account for all traffic on a per-customer basis.
Cisco 12000 series ISE line cards support source-based BGP policy accounting in addition to destination-based BGP accounting. In source-based BGP policy accounting, the source IP address of routed traffic is used instead of the destination IP address to classify traffic according to the configured BGP accounting policy and to update the counters for a given traffic category.
On Cisco 12000 series ISE line cards, BGP policy accounting supports the Stateful Switchover (SSO)/Nonstop Forwarding (NSF) features.
For more information about the BGP policy accounting feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/s_bgppax.htm
Stateful Switchover (SSO)
The Stateful Switchover (SSO) feature is an incremental step within an overall program to improve the availability of networks constructed with Cisco IOS routers. SSO is particularly useful at the network edge. Traditionally, core routers protect against network faults using router redundancy and mesh connections that allow traffic to bypass failed network elements. SSO provides protection for network edge devices with dual Route Processors (RPs) that represent a single point of failure in the network design, and where an outage might result in loss of service for customers.
In specific Cisco networking devices that support dual RPs, SSO takes advantage of RP redundancy to increase network availability. The SSO feature takes advantage of RP redundancy by establishing one of the RPs as the active processor while the other RP is designated as the standby processor, and then synchronizing critical state information between them. Following an initial synchronization between the two processors, SSO dynamically maintains RP state information between them.
A switchover from the active to the standby processor occurs when the active RP fails, is removed from the networking device, or is manually taken down for maintenance.
SSO is used with the Cisco Nonstop Forwarding (NSF) feature. Cisco NSF allows for the forwarding of data packets to continue along known routes while the routing protocol information is being restored following a switchover. With Cisco NSF, peer networking devices do not experience routing flaps, thereby reducing loss of service outages for customers.
For more information about the Stateful Switchover feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/sso2 4s.htm
Cisco Nonstop Forwarding (NSF)
Cisco Nonstop Forwarding (NSF) works with the Stateful Switchover (SSO) feature in Cisco IOS software. SSO is a prerequisite of Cisco NSF. NSF works with SSO to minimize the amount of time a network is unavailable to its users following a switchover. The main objective of Cisco NSF is to continue forwarding IP packets following a Route Processor (RP) switchover.
Usually, when a networking device restarts, all routing peers of that device detect that the device went down and then came back up. This transition results in what is called a routing flap, which could spread across multiple routing domains. Routing flaps caused by routing restarts create routing instabilities, which are detrimental to the overall network performance. Cisco NSF helps to suppress routing flaps in SSO-enabled devices, thus reducing network instability.
Cisco NSF allows for the forwarding of data packets to continue along known routes while the routing protocol information is being restored following a switchover. With Cisco NSF, peer networking devices do not experience routing flaps. Data traffic is forwarded through intelligent line cards or dual Forwarding Processors (FPs) while the standby RP assumes control from the failed active RP during a switchover. The ability of line cards and FPs to remain up through a switchover and to be kept current with the Forwarding Information Base (FIB) on the active RP is key to Cisco NSF operation.
For more information about the Nonstop Forwarding feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/nsf2 4s.htm
CISCO-APS-EXT-MIB
Platform: Cisco 12000 series
The Cisco SONET Linear Automatic Protection Switching (APS) allows switchover of Packet-over-SONET (POS) circuits in case of circuit failure. APS is a mechanism in which the protect POS interface acts as a backup to the working POS interface.
The CISCO-APS-EXT-MIB module extends the CISCO-APS-MIB by adding the following objects:
•cApsChanConfigExtTable—augments cApsChanConfigTable in the CISCO-APS-MIB.
•cApsChanAssociationTable—provides the associated working or protection channel IP address for all protection and working channels.
No new or modified Cisco IOS commands are associated with this MIB. For details on managed objects within the Cisco SONET Linear APS MIB, see the CISCO-APS-MIB.my MIB file. MIB information is available at the following location:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
Cisco ATM QoS MIB
The new Cisco ATM QoS MIB (CISCO-ATM-QOS-MIB) and its defined objects support quality of service (QoS) parameters configured for a virtual channel (VC) over an ATM interface through use of the following features:
•Shaping traffic on a per-VC basis
•Shaping traffic on a per-virtual path (VP) basis
•Configuring Weighted Random Early Detection (WRED) parameters per VC
Note This is a read-only MIB.
For details, see the CISCO-ATM-QOS-MIB.my file, available through the Cisco MIB FTP site at the following location:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
CISCO-ENHANCED-WRED-MIB Support for Cisco 12000 Series Internet Routers
Cisco Weighted Random Early Detection (WRED)/Drop is a method that avoids traffic congestion on an output interface. Congestion is detected by computing the average output queue size against queue thresholds, which can be configured per IP precedence or can be based on differentiated services code point (DSCP). WRED support is on the IP fast switching and IP flow switching only. It does not apply to IP process switching.
The purpose of the CISCO-ENHANCED-WRED-MIB is to provide Weighted Random Early Detection/Drop packet configuration and packet filtering information. This MIB provides the WRED information about the transmit (Tx) side and receive (Rx) side of the modules, for the managed systems that support WRED on both transmit side and receive side.
This feature supports the CISCO ENHANCED WRED MIB on Cisco 12000 series Internet routers and is implemented on the basis on the legacy CoS CLI used on Cisco 12000 series Internet routers.
Cisco Extension to the Interfaces MIB (CISCO-IF-EXTENTION-MIB)
The Cisco Extension to the Interfaces MIB (CISCO-IF-EXTENTION-MIB) feature introduces support for the Cisco Extension to the Interfaces (IF) MIB. The CISCO-IF-EXTENTION-MIB implements Cisco specific extensions to the Interface MIB (RFC 2233). These extensions are, specifically, two tables that provide information about interface packet statistics and interface properties. Details on these extensions can be found in the MIB file CISCO-IF-EXTENTION-MIB.my { ciscoMgmt 276 }.
No new or modified Cisco IOS commands are associated with this feature.
CISCO-FABRIC-C12K-MIB
Platform: Cisco 12000 series
The CISCO-FABRIC-C12K-MIB module is used to manage and track Cisco 12000 series Internet router fabric entities and fabric-related configuration, as well as status and statistics information.
The Cisco 12000 series Internet router fabric architecture is based on NxN nonblocking crossbar switch fabric, where N stands for the maximum number of line cards that can be supported in the chassis, including the Route Processor. Connections through the switch fabric are controlled by a clock scheduler card (CSC). The CSC accepts transmission requests from line cards, issues grants to access the fabric, and provides a reference clock to all the cards in the system to synchronize data transfer across the crossbar.
The basic components and entities related to fabric in the Cisco 12000 series Internet router are the following:
•ToFabFIA—To Fabric Interface ASIC that transmits data from the line card to the fabric.
•FrFabFia—From Fabric Interface ASIC that receives data from the fabric.
•SCA—Scheduler Control ASIC that resides on each CSC and is used to arbitrate among the line card requests to transmit CiscoCells through the switch fabric.
•XBAR—Crossbar Switch ASIC that resides on each fabric card and provides the functionality of a crossbar switch.
The CISCO-FABRIC-C12K-MIB provides information regarding these fabric entities. The MIB is divided into three basic groups for each fabric entity:
•Generic information that is common across pre-OC192 and OC192 fabric entities.
•Information about pre-OC192 fabric entities.
•Information pertaining to OC192 fabric entities.
The following Cisco IOS commands have been modified for use with this MIB:
•snmp-server enable traps c12k-fabric to enable traps for the CISCO-FABRIC-C12K-MIB.
•snmp-server host host-addr traps version {1 | 2c | 3 [auth | noauth | priv]} public c12k-fabric to specify the recipient of the SNMP notifications (traps) generated by the CISCO-FABRIC-C12K-MIB, where version {1 | 2c | 3 [auth | noauth | priv]} is the SNMP version used to send the traps.
For more detailed information about the snmp-server enable traps and snmp-server host command syntax and usage, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/fun_r/frprt3/frd3001.htm
For details on managed objects within the CISCO-FABRIC-C12K-MIB, see CISCO-FABRIC-C12K-MIB.my MIB file.
Cisco Nonstop Forwarding with Stateful Switchover on Cisco 12000 Series Line Cards
Support for the Cisco Nonstop Forwarding with Stateful Switchover (NSF/SSO) feature has been added to the following Cisco 12000 Series line cards:
•Engine 1
–Cisco 12000 Series 2-Port OC-12/STM-4c DPT line card
•Engine 2
–Cisco 12000 Series 1-Port OC-48/STM-16c DPT line card
–Cisco 12000 Series 8-Port OC-3/STM-1c ATM line card
•IP Services Engine (ISE)
–Cisco 12000 Series Four-Port OC-3c/STM-1c POS/SDH ISE line card
–Cisco 12000 Series Eight-Port OC-3c/STM-1c POS/SDH ISE line card
–Cisco 12000 Series Sixteen-Port OC-3c/STM-1c POS/SDH ISE line card
–Cisco 12000 Series Four-Port OC-12c/STM-4c POS/SDH ISE line card
–Cisco 12000 Series One-Port OC-48c/STM-16c POS/SDH ISE line card
–Cisco 12000 Series Four-Port Channelized OC-12/STM-4 (DS3/E3, OC-3c/STM-1c) POS/SDH ISE line card
–Cisco 12000 Series One-Port Channelized OC-48/STM-16 (DS3/E3, OC-3c/STM-1c) POS/SDH, OC-12c/STM-4c ISE line card
The Stateful Switchover (SSO) feature is an incremental step within an overall program to improve the availability of networks constructed with Cisco IOS routers. SSO is particularly useful at the network edge. Traditionally, core routers protect against network faults using router redundancy and mesh connections that allow traffic to bypass failed network elements. SSO provides protection for network edge devices with dual Route Processors (RPs) that represent a single point of failure in the network design, and where an outage might result in loss of service for customers.
In specific Cisco networking devices that support dual RPs, SSO takes advantage of RP redundancy to increase network availability. The SSO feature takes advantage of RP redundancy by establishing one of the RPs as the active processor while the other RP is designated as the standby processor, and then synchronizing critical state information between them. Following an initial synchronization between the two processors, SSO dynamically maintains RP state information between them.
A switchover from the active to the standby processor occurs when the active RP fails, is removed from the networking device, or is manually taken down for maintenance.
SSO is used with the Cisco Nonstop Forwarding (NSF) feature. Cisco NSF allows for the forwarding of data packets to continue along known routes while the routing protocol information is being restored following a switchover. With Cisco NSF, peer networking devices do not experience routing flaps, thereby reducing loss of service outages for customers.
The Cisco Nonstop Forwarding with Stateful Switchover feature was introduced in Cisco IOS Release 12.(22)S. In Cisco IOS Release 12.0(24)S, this feature is ported to Cisco 12000 Series 2-Port OC-12 DPT, 1-Port OC-48 DPT, 8-Port OC-3 ATM, and IP Services Engine (ISE) line cards.
For more information about the Stateful Switchover feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/sso2 4s.htm
For more information about the Cisco Nonstop Forwarding feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/nsf2 4s.htm
CISCO-PSA-MICROCODE-MIB
Platform: Cisco 12000 series
The CISCO-PSA-MICROCODE-MIB contains information about the microcode bundles on Engine 2 line cards in the Cisco 12000 series Internet router.
The Packet Switching ASIC (PSA) is used in Cisco 12000 series Engine 2 line cards for IP and Multiprotocol Label Switching (MPLS) packet forwarding. PSA supports features such as basic IP forwarding, basic MPLS forwarding, Per Interface Rate Control (PIRC), extended access control lists (EACLs), and so on.
Note that all features are not supported simultaneously on an Engine 2 line card. Each microcode bundle supports one or a limited number of features. Each bundle has a priority. When a feature is enabled through the command-line interface, the higher priority feature/bundle takes precedence over the lower priority features/bundles. The microcode bundle for the lower priority is removed and cleaned up. The higher priority microcode is loaded. Later, if the higher priority feature is removed, the lower priority microcode will be loaded again.
The following Cisco IOS commands have been modified for use with this MIB:
•snmp-server enable traps psa to enable traps for the CISCO-PSA-MICROCODE-MIB.
•snmp-server host host-addr traps version {1 | 2c | 3 [auth | noauth | priv]} public psa to specify the recipient of the SNMP notifications (traps) generated by the CISCO-PSA-MICROCODE-MIB, where version {1 | 2c | 3 [auth | noauth | priv]} is the SNMP version used to send the traps.
For more detailed information about the snmp-server enable traps and snmp-server host command syntax and usage, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/fun_r/frprt3/frd3001.htm
For details on managed objects within the CISCO-PSA-MICROCODE-MIB, see the CISCO-PSA-MICROCODE-MIB.my MIB file, available from the Cisco MIB FTP site at the following location:
ftp://ftp.cisco.com/pub/mibs/v2/
Class-Based QoS MIB for the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
Platform: Cisco 12000 series
The Class-Based Quality of Service (QoS) MIB is now supported on the Cisco 12000 series 8-Port OC-3/STM-1 ATM line card. The Class-Based QoS MIB contains statistical information about the per-VC (virtual circuit) CoS (class of service) queues in the line card.
To configure quality of service on the 8-Port OC-3/STM-1 ATM line card, use the modular QoS command-line interface (MQC). For complete documentation on MQC configuration commands and tasks and for general information on how to configure the MQC, see the Modular Quality of Service Command-Line Interface at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5/mq c/mcli.htm
The following Cisco IOS command has been modified for use with this MIB:
•show atm pvc vpi/vci queue-stats
Where vpi/vci are the ATM virtual path identifier (VPI) and virtual circuit identifier (VCI) numbers.
Use the show atm pvc vpi/vci queue-stats command to display the CoS queue statistics associated with the VCs identified by the vpi/vci combination. The CoS queue statistics include current queue depth, maximum current queue depth, current average queue depth, queue output packet counter, and queue drop packet count.
For more detailed information about the show atm pvc command syntax and usage, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/wan_r/wroampvc.htm
Because the 8-Port OC-3/STM-1 ATM line card supports only a subset of the MQC features, the Class-Based QoS MIB used with the 8-Port OC-3/STM-1 ATM line card supports only certain MQC objects. For details on the objects managed within the Class-Based QoS MIB, see the CISCO-CLASS-BASED-QOS-MIB.my MIB file, available from the Cisco MIB FTP site at the following location:
ftp://ftp.cisco.com/pub/mibs/v2/
Distributed Link Fragmentation and Interleaving over Leased Lines
Platform: Cisco 7500 series
The Distributed Link Fragmentation and Interleaving (dLFI) over Leased Lines feature introduces distributed link fragmentation and interleaving functionality on the VIP-enabled Cisco 7500 series routers to leased lines.
The dLFI feature supports the transport of real-time traffic, such as voice, and non-real-time traffic, such as data, on leased lines without causing excessive delay to the real-time traffic.
This feature is implemented using multilink PPP (MLP) over leased lines on VIP-enabled Cisco 7500 series routers. The feature enables delay-sensitive real-time packets and non-real-time packets to share the same link by fragmenting the large data packets into a sequence of smaller data packets (fragments). The fragments are then interleaved with the real-time packets. On the receiving side of the link, the fragments are reassembled and the packet reconstructed.
The dLFI feature is often useful in networks that send real-time traffic using Distributed Low Latency Queueing, such as voice, but have bandwidth problems that delay this real-time traffic because of the transport of large, less time-sensitive data packets. The dLFI feature can be used in these networks to disassemble the large data packets into multiple segments. The real-time traffic packets can then be sent between these segments of the data packets. In this scenario, the real-time traffic does not experience a lengthy delay waiting for the low-priority data packets to traverse the network. The data packets are reassembled at the receiving side of the link, so the data is delivered intact.
The ability to configure Quality of Service (QoS) using the Modular QoS CLI while also using distributed MLP (dMLP) is also introduced as part of the dLFI feature. This ability was not supported prior to the introduction of the dLFI feature.
Distributed Multilink Frame Relay
Platform: Cisco 7500 series
The Multilink Frame Relay feature introduces functionality based on the Frame Relay Forum Multilink Frame Relay UNI/NNI Implementation Agreement (FRF.16). This feature provides a cost-effective way to increase bandwidth for particular applications by enabling multiple serial links to be aggregated into a single bundle of bandwidth. Multilink Frame Relay is supported on User-to-Network Interfaces (UNIs) and Network-to-Network Interfaces (NNIs) in Frame Relay networks.
Hierarchical Policy Map
Platform: Cisco 10720
You can use a hierarchical policy map to specify a parent shaper for a given interface or subinterface (802.1Q). Under the parent shaper, you can specify a child policy map to configure multiple user queues such as shaped, fair, priority and default.
Use this feature to offer fractional bandwidth service on a Gigabit Ethernet or Fast Ethernet access interface. When you configure an interface with fractional bandwidth, the packet dequeue rate does not exceed the configured fractional value.
IP Receive ACL
Platform: Cisco 7500 series
Note Support for the IP Receive ACL feature was introduced on the Cisco 12000 series Internet router in Cisco IOS Release 12.0(22)S.
The IP Receive ACL feature provides basic filtering capability for traffic that is destined for the router; that is, the router can protect high-priority routing protocol traffic from an attack because the filtering occurs after any input access control list (ACL) on the ingress interface.
This feature may be implemented in a security solution to protect a router from remote intrusions. Access to the router can be restricted to known, trusted sources and expected traffic profiles.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/ft_ip acl.htm
IP Version 6 on the Cisco 10720 Internet Router
IP version 6 (IPv6), formerly called IPng (next generation), is the latest version of IP that offers many benefits, such as a larger address space, over the previous version of IP (version 4). On the Cisco 10720 Internet Router, IPv6 is implemented so that packets are routed through the Route Processor and, therefore, take the slow path.
For complete information about the IPv6 features supported on the Cisco 10720 Internet router, including IPv6 provider edge router over MPLS (Cisco 6PE), see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/1072 0.htm
IPv6 Provider Edge Router over MPLS (Cisco 6PE) on the Cisco 10720 Internet Router
The IPv6 Provider Edge Router over MPLS (Cisco 6PE) feature allows service providers that are running an MPLS/IPv4 infrastructure to offer IPv6 services on an MPLS network. A Cisco 6PE-enabled backbone allows IPv6 domains to communicate with each other over an MPLS IPv4 core network. A Cisco 6PE implementation requires no backbone infrastructure upgrades and no reconfiguration of core routers, because forwarding is based on labels rather than on the IP header itself.
Additionally, the inherent Virtual Private Network (VPN) and Traffic Engineering (TE) services available within an MPLS environment allow IPv6 networks to be combined into VPNs or extranets over an infrastructure that supports IPv4 VPNs and MPLS-TE.
The provider edge (PE) routers at each end of the MPLS network must be IPv6-enabled. The PE routers apply an appropriate label for the address in the packet to reach the other side of the MPLS backbone. This is similar to tunneling because it allows IPv6 traffic to be transported over MPLS without the routers in the backbone being aware of the IPv6 traffic. An MPLS packet enters and exits the MPLS network on different routers, and each router must be IPv6- and 6PE-enabled.
For more information about the IPv6 Provider Edge Router over MPLS (Cisco 6PE) feature, see the following document:
http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/iosip_an.htm
IS-IS Incremental SPF
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series,
Cisco 12000 seriesIntermediate System-to-Intermediate System (IS-IS) can be configured to use an incremental Shortest Path First (SPF) algorithm for calculating the SPF routes. Incremental SPF is more efficient, thereby allowing IS-IS to converge faster on a new routing topology in reaction to a network event.
L2TPv3 Enhancements on the Cisco 10720 Internet Router
Starting in Cisco IOS Release 12.0(24)S, the Cisco 10720 Internet router supports the following features:
• Don't Fragment (DF) Bit Reflection
For more detailed information about how these L2TPv3 features are supported on the Cisco 10720 Internet router, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/1072 0.htm
Path MTU Discovery
The Path MTU Discovery feature allows you to use the ip pmtu command to enable the discovery of an L2TPv3 path's maximum transmission unit (MTU). All packets (except IS-IS packets) that are sent in an L2TPv3 tunneling session having a size larger than the PMTU of the session are dropped. If an IP packet is dropped, an Internet Control Message Protocol (ICMP) unreachable message is sent back to the originator of the packet.
IS-IS Packet Fragmentation
The fragmentation of Intermediate System-to-Intermediate System (IS-IS) packets occurs in an L2TPv3 session if the size of the IS-IS packet exceeds the configured MTU of the L2TPv3 tunnel. IS-IS protocol packet fragmentation is supported only for dynamic L2TPv3 sessions.
IP ToS Reflection
The IP Type of Service (ToS) Reflection feature allows you to use the ip tos command to have the ToS byte in the outer headers of L2TPv3 tunneled packets reflected from the inner IP header of the encapsulated packet.
Don't Fragment (DF) Bit Reflection
In an L2TPv3 session, the destination of encapsulated packets in the provider edge (PE) network is the decapsulation router. To avoid congestion caused by the reassembly of fragments at the decapsulation router, you can use the ip dfbit set command to enable the DF bit on the encapsulating IP header. The DF bit results in packets being dropped in the provider network whenever the packet size exceeds the maximum transmission unit (MTU).
Variable Cookie Size
The L2TPv3 header contains a control channel cookie field that is similar to the UTI control channel key field. However, on the Cisco 10720 Internet router, the control channel cookie field has a variable length of 0, 4, or 8 bytes for packet encapsulation to a remote PE router. The Cisco 10720 Internet router supports only an 8-byte cookie locally for packet decapsulation.
You can manually configure the control channel cookie length for static sessions using the l2tp cookie remote command, or you can allow it to be dynamically determined for dynamic sessions.
L2TPv3 Enhancements on the Cisco 12000 Series Internet Router
In Cisco IOS Release 12.0(24)S, the following L2TPv3 enhancements are supported on Packet-over-SONET (POS) and Ethernet interfaces on the Cisco 12000 series Internet router using an Engine 2 (E2) tunnel server card:
•Variable Cookie Size for Packet Decapsulation
•Sequence Number Support
•Quality of Service Using ToS Reflection
•VLAN Support Using VLAN ID Rewrites
•Don't Fragment (DF) Bit Reflection
•Packet Fragmentation at Customer-Facing Interface (CFI)
For more information about how to configure and use Layer 2 Tunneling Protocol Version 3 on Cisco 12000 series Internet routers, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/l2tp v3.htm
Layer 2 Tunnel Protocol Version 3 Fragmentation
Platforms: 7200 series, 7500 series, 12000 series
The Layer 2 Tunnel Protocol Version 3 Fragmentation feature expands on Cisco support of Layer 2 Tunnel Protocol Version 3 (L2TPv3). Previous Cisco IOS releases contained only limited support of L2TPv3. L2TPv3 control plane support and new commands for configuring both static and dynamic L2TPv3 sessions were introduced in Cisco IOS Release 12.0(23)S. Cisco IOS Release 12.0(24)S introduces support of IP packet fragmentation before the packets enter the pseudo wire, forcing the reassembly of fragmented packets to occur in the customer edge (CE) network rather than in the service provider network.
L2TPv3 is an Internet Engineering Task Force (IETF) working group draft that provides several enhancements 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).
Leased Line SNMP MIB Enhancements
MIB capabilities on the Cisco 10000 series ESR have been enhanced as follows:
•The CISCO-ENTITY-EXT-MIB and CISCO-OAM-MIB were added.
•Support was verified for the following MIBs:
–ATM-MIB
–CISCO-AAL5-MIB
–CISCO-ATM-EXT-MIB
–SONET-MIB, RFC1315-MIB
–CISCO-FRAME-RELAY-MIB
–CISCO-RF-MIB
•Support was added for MPLS-LSR-MIB mplsInSegmentOctets.
•The IF-MIB was enhanced to support MPLS.
•MIBs were enhanced to support the ESR high-availability feature.
For more information about ESR MIB capabilities, see the Cisco 10000 Series ESR Leased Line MIB Specifications Guide (version 3) at the following URL:
http://cisco.com/univercd/cc/td/doc/product/aggr/10000/10kmibs/llguides/llgdv3/index.htm
Microcode Bundle Manager on Cisco 12000 Series Engine 2 Line Cards
The Microcode Bundle Manager provides an enhancement to the mechanism currently used to load and unload microcode bundles on the packet-switching ASIC (PSA) of Engine 2 (E2) line cards on the Cisco 12000 series Internet router. The Microcode Bundle Manager has the following benefits:
•Provides a simpler way to manage the complexity of the increasing number of software features supported on E2 line cards.
•Ensures that the correct microcode bundle is consistently and reliably loaded (or unloaded) when you enable (or disable) a software feature on an E2 line card.
MPLS COS Transparency on Cisco 12000 E4+ DPT Line Cards
MPLS COS Transparency is supported on the 1-port OC-192/STM-64 E4+ DPT line card and on the 4-port OC-48/STM-16 E4+ DPT line card.
MPLS LDP MIB Version 8 Upgrade
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series, Cisco 12000 series
The Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) MIB Version 8 Upgrade feature enhances the LDP MIB to support the Internet Engineering Task Force (IETF) draft version 8.
MPLS Traffic Engineering Fast Reroute on the Cisco 10720 Internet Router
The MPLS Traffic Engineering Fast Reroute (FRR) feature is supported on the Cisco 10720 2-Port OC-48c/STM-16c POS/DPT uplink card in POS mode only. The Fast Reroute feature provides link protection to label-switched paths (LSPs).
Regular MPLS traffic engineering automatically establishes and maintains label-switched paths across the backbone using the Resource Reservation Protocol (RSVP). The path used by a given LSP at any point in time is based upon the LSP resource requirements and available network resources such as bandwidth.
For more information about the MPLS FRR feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fs_f rrnd.htm
MPLS VPN—Carrier Supporting Carrier on the Cisco 10720 Internet Router
The MPLS VPN Carrier Supporting Carrier (CsC) feature enables one MPLS VPN-based service provider to allow other service providers to use a segment of its backbone network. The Cisco 10720 Internet router now supports the Carrier Supporting Carrier feature with IPv4 BGP label distribution.
The MPLS VPN CsC feature with IPv4 BGP label distribution allows you to configure your carrier supporting carrier network to enable Border Gateway Protocol (BGP) to transport routes and Multiprotocol Label Switching (MPLS) labels between the backbone carrier provider edge (PE) routers and the customer carrier customer edge (CE) routers. Previously you had to use Label Distribution Protocol (LDP) to carry the labels and an interior gateway protocol to carry the routes between PE and CE routers to achieve the same goal.
For more information about how to use the Carrier Supporting Carrier feature with IPv4 BGP label distribution, see the following document: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fscs c22.htm
MPLS VPN—Carrier Supporting Carrier—IPv4 BGP Label Distribution
The MPLS VPN—Carrier Supporting Carrier—IPv4 BGP Label Distribution feature enables you to configure your carrier supporting carrier network to enable Border Gateway Protocol (BGP) to transport routes and Multiprotocol Label Switching (MPLS) labels between the backbone carrier provider edge (PE) routers and the customer carrier customer edge (CE) routers. Previously you had to use Label Distribution Protocol (LDP) to carry the labels and an interior gateway protocol to carry the routes between PE and CE routers to achieve the same goal.
For additional information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/fscs cl24.htm
MPLS VPN—Inter-AS—IPv4 BGP Label Distribution
The MPLS VPN—Inter-AS—IPv4 BGP Label Distribution feature enables you to set up a Virtual Private Network (VPN) service provider network so that the autonomous system boundary routers (ASBRs) exchange IPv4 routes with Multiprotocol Label Switching (MPLS) labels of the provider edge (PE) routers. Route reflectors (RRs) exchange VPNv4 routes by using multihop, multiprotocol, Exterior Border Gateway Protocol (EBGP). This configuration saves the ASBRs from having to store all the VPNv4 routes. Using the route reflectors to store the VPNv4 routes and forward them to the PE routers results in improved scalability.
For additional information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/fsias l24.htm
MPLS VPN—Interautonomous System Support
The MPLS VPN—Interautonomous System Support feature allows Multiprotocol Label Switching Virtual Private Network (MPLS VPN) to span service providers and autonomous systems. Separate autonomous systems from different service providers can communicate by exchanging IPv4 Network Layer Reachability Information (NLRI) in the form of VPN-IPv4 addresses. The autonomous systems' border edge routers use Exterior Border Gateway Protocol (EBGP) to exchange that information. Then, an interior gateway protocol distributes the network layer information for VPN-IPv4 prefixes throughout each VPN and each autonomous system.
An MPLS VPN with interautonomous system support allows a service provider to provide to customers scalable Layer 3 VPN services, such as web hosting, application hosting, interactive learning, electronic commerce, and telephony service. A VPN service provider supplies a secure, IP-based network that shares resources on one or more physical networks.
For additional information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/fsias 24.htm
MPLS-aware NetFlow
Platform: Cisco 12000 series
Multiprotocol Label Switching (MPLS)-aware NetFlow is an extension of the NetFlow feature. NetFlow traditionally provides statistics for IPv4 traffic. MPLS-aware NetFlow provides per-flow statistics for traffic in MPLS-enabled networks. The network administrator can turn on MPLS-aware NetFlow inside an MPLS cloud on a subset of provider (P) backbone routers. These routers can export MPLS-aware NetFlow data in real time to an external NetFlow collector device for further processing or to a data terminal for analysis. MPLS-aware NetFlow statistics can be used for detailed MPLS traffic studies and analysis.
For additional information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/fsmn f24.htm
MQC Enhancements on the Cisco 10720 Internet Router
Starting in Cisco IOS Release 12.0(24)S, the Cisco 10720 Internet router supports the following modular quality of service (QoS) features that you configure using the modular QoS command-line interface (MQC):
• Distribution of Remaining Bandwidth
For more information about how these MQC features are supported on the Cisco 10720 Internet router, see the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/1072 0.htm
Fractional Bandwidth
You can use MQC to configure the output bit rate of a Cisco 10720 Ethernet, POS, or SRP port to be a fractional percentage of its maximum output. When you configure an interface with fractional bandwidth, the packet dequeue rate does not exceed the configured fractional value. Also, as long as the Cisco 10720 Internet router does not experience system-wide congestion, traffic on the interface is serviced at the specified fractional bandwidth.
Per-VLAN Queuing
You can use MQC to configure output packet queues for an 802.1q VLAN on a Cisco 10720 Ethernet interface. When you configure a VLAN queue, you must specify the amount of bandwidth reserved for the VLAN. Once VLAN queuing is configured, the packet dequeue rate does not exceed the specified rate. Also, as long as the Cisco 10720 Internet router does not experience system-wide congestion, traffic on the VLAN interface is serviced at the specified bandwidth.
Distribution of Remaining Bandwidth
You can use MQC to specify how the "remaining" bandwidth is distributed among the output queues on a Cisco 10720 Ethernet interface or subinterface. "Remaining" bandwidth is the available bandwidth left on an Ethernet interface or subinterface after all guaranteed traffic is accounted for. The amount of remaining bandwidth available for use is determined by the excess information rate (EIR) configured for the queue.
Turbo QoS Classifier
MQC match statements are normally searched sequentially to find a matching rule. Because of the increasing needs and requirements for better packet classification, the MQC matching process can expand to the point that searching through MQC class maps adds a significant amount of PXF feedback when packets are being forwarded.
The Turbo Quality of Service (QoS) Classifier feature compiles the MQC class maps into a set of lookup tables, similar to the Turbo ACL feature. Packet headers are used to access these tables in a small, fixed number of lookups, independently of the existing number of class-map entries. This feature dramatically reduces the need for feedback on the Cisco 10720 as a single lookup is needed per lookup table.
OSPF Forwarding Adjacency
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series, Cisco 12000 series
The Open Shortest Path First (OSPF) Forwarding Adjacency feature adds OSPF support to the Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Forwarding Adjacency feature, which allows a network administrator to handle a traffic engineering, label-switched path (LSP) tunnel as a link in an Interior Gateway Protocol (IGP) network based on the Shortest Path First (SPF) algorithm. An OSPF forwarding adjacency can be created between routers in the same area.
OSPF Incremental SPF
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series, Cisco 12000 series
Open Shortest Path First (OSPF) can be configured to use an incremental Shortest Path First (SPF) algorithm for calculating the SPF routes. Incremental SPF is more efficient, thereby allowing OSPF to converge faster on a new routing topology in reaction to a network event.
OSPF Route Map-Based Filtering
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series, Cisco 12000 series
Users can define a route map to prevent Open Shortest Path First (OSPF) routes from being added to the routing table. In the route map, the user can match on any attribute of the OSPF route.
OSPF for IPv6
Platforms: Cisco 10700 series, Cisco 12000 series
The Open Shortest Path First (OSPF) for IPv6 feature provides support for IPv6 routing prefixes. OSPF for IPv6 runs alongside the current OSPF in networks with both IPv4 and IPv6. In OSPF for IPv6, some commands used to configure OSPF are in interface configuration mode rather than in router configuration mode.
Output Sampled NetFlow on IP Services Engine (ISE) Line Cards
Platform: Cisco 12000 series
The existing Sampled NetFlow feature on input interfaces allows you to collect NetFlow statistics for a subset of incoming IPv4 traffic, processing only one of "N" sequential packets, where "N" is a user-configurable parameter. Traffic sampling substantially reduces consumption of the router resources while providing valuable NetFlow statistics. Starting in Cisco IOS Release 12.0(24)S, Cisco 12000 series IP Services Engine (ISE) line cards also support Sampled NetFlow as an output feature, providing NetFlow statistics for outgoing traffic.
To enable Output Sampled NetFlow on a Cisco 12000 Series ISE interface, use the ip route-cache flow sampled [input | output] command in interface configuration mode, where:
•input—Enables NetFlow sampling on incoming IPv4 traffic on the ISE interface.
•output—enables NetFlow sampling for outgoing IPv4 traffic on the ISE interface.
For more information about how to configure and use Sampled NetFlow, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/12so utfl.htm
Periodic MIB Data Collection and Transfer Mechanism
Platform: Cisco 12000 series
The Periodic MIB Data Collection and Transfer Mechanism feature provides the ability to periodically transfer selected MIB data from Cisco IOS based devices to specified Network Management Stations (NMSs). Using the command line interface (CLI), data from multiple MIBs can be grouped into lists, and a polling interval (frequency of data collection) can be configured. All the MIB objects in a list are periodically polled using this specified interval. The collected data from the lists can then be transferred to a specified NMS at a user-specified transfer interval (frequency of data transfer) using TFTP, RCP, or FTP.
QA Error Recovery for the Cisco 7500
Platform: Cisco 7500 series
The QA Error Recovery for the Cisco 7500 feature helps the networking device to recover quickly from problems known as QAERRORs. These QAERRORs can be caused by hardware or software issues. When a QAERROR occurs, the device can hang while it tries to recover from the problem. On fully loaded devices, hang times following QAERRORs can be up to five minutes (300 seconds). With the QAERROR recovery enabled, the hang time can be a little as one second.
In Cisco IOS Release 12.0(24)S1, Release 12.0(24)S2, and Release 12.0(24)S3, you must enable QA Error Recovery for the Cisco 7500 feature by entering the following global configuration command:
hw-module main-cpu qaerror-recovery-enable
Note In releases following Cisco IOS Release 12.0(24)S3—that is, from Cisco IOS Release 12.0(25)S on—the QA Error Recovery for the Cisco 7500 feature is enabled by default.
You can tell that recovery from an error was successful because a message reporting a successful recovery will appear on the console screen. Additionally, the number of QAERROR recoveries is displayed in the output of the show controllers cbus command.
The following example shows the output of the console or show logs when QAERROR happened. Although the example indicates both the point at which the feature begins trying to recover from the QAERROR and the point at which the device recovers from the error, the networking device may display many additional messages that can help service technicians diagnose the actual cause of the problem.
%QA-3-DIAG:Trying to recover from QA ERROR.
%QA-3-DIAG:Removing buffer header 0xE360 from all queues
%QA-3-DIAG:Buffer 0xE360 is element 155 on queue 0x2E
%QA-3-DIAG:Queue 0x2E (48000170) has 154 elements
%QA-3-DIAG:Buffer 0xE360 is element 1 on queue 0x340
%QA-3-DIAG:Queue 0x340 (48001A00) has 0 elements
%QA-3-DIAG:At least one QA queue is broken
%QA-3-DIAG:Recovered from QA ERROR
The following example shows the relevant QA error recovery output of the show controllers cbus command:
Router# sh controllers cbus
MEMD at E0000000, 8388608 bytes (unused 1565056, recarves 5, lost/qaerror recoveries 0/0)
.
.
.
Router#
To disable QAERROR recovery on the device, use the no version of the command:
no hw-module main-cpu qaerror-recovery-enable
RSVP Refresh Reduction and Reliable Messaging
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, Cisco 10700 series, Cisco 12000 series
The RSVP Refresh Reduction and Reliable Messaging feature includes refresh reduction, which improves the scalability, latency, and reliability of Resource Reservation Protocol (RSVP) signaling to enhance network performance and message delivery.
Support for SONET Notifications in CISCO-SONET-MIB
Platform: Cisco 7500 series, Cisco 12000 series
The CISCO-SONET-MIB describes SONET/SDH interface objects and is an extension to the standard SONET MIB (RFC 2558).
The following Cisco IOS commands have been modified for use with this MIB:
•snmp-server enable traps sonet to enable traps for the CISCO-SONET-MIB.
•snmp-server host host-addr traps version {1 | 2c | 3 [auth | noauth | priv]} public sonet to specify the recipient of the SNMP notifications (traps) generated by the CISCO-SONET-MIB, where version {1 | 2c | 3 [auth | noauth | priv]} is the SNMP version used to send the traps.
For more detailed information about the snmp-server enable traps and snmp-server host command syntax and usage, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/fun_r/frprt3/frd3001.htm
For details on managed objects within the CISCO-SONET-MIB, see the CISCO-SONET-MIB.my MIB file, available from the Cisco MIB FTP site at the following location:
ftp://ftp.cisco.com/pub/mibs/v2/
New Hardware and Software Features in Cisco IOS Release 12.0(23)S1 to Cisco IOS Release 12.0(23)S6
There are no new hardware or software features in Cisco IOS Release 12.0(23)S1 to Cisco IOS Release 12.0(23)S6.
New Hardware Features in Cisco IOS Release 12.0(23)S
This section describes new and changed features in Cisco IOS Release 12.0(23)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(23)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
1-Port 10-Gigabit Ethernet Line Card
Platform: Cisco 12000 series
The 1-Port 10-Gigabit Ethernet line card, which is designed for high-density and server-aggregation applications, provides the Cisco 12000 series routers with one optical 802.3ae 10-Gigabit Ethernet interface. This interface provides high-speed interconnections to other network devices, such as other Cisco 12000 series routers, or to other routers or Layer 2 or Layer 3 switches that support 10-Gigabit Ethernet interfaces.
Because the 1-port 10-Gigabit Ethernet line card requires a card cage slot that is 1.8 inches (4.5 centimeters) wide, you can use the 1-port 10-Gigabit Ethernet line card in only the Cisco 12416, Cisco 12410, Cisco 12406, and Cisco 12404 routers. The system must be configured for full switching fabric capacity, which is one clock and scheduler card (CSC) and three switch fabric cards (SFCs). In addition, the 1-port 10-Gigabit Ethernet line card requires a switch fabric that supports 10-Gigabit Ethernet, available only on the Cisco 12416, Cisco 12410, Cisco 12406, and Cisco 12404 routers.
The 1-Port 10-Gigabit Ethernet line card is available in two laser optical transceiver options:
•1310 nanometer (nm) nominal long haul or long wavelength, used for 1000BASE-LR links.
•1550 nm nominal long haul or long wavelength, used for 1000BASE-ER links.
For information about how to install and configure the line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_enet/12902.htm
2-Port OC-48c/STM-16c POS/DPT Uplink Card and Versatile Optical Interface
Descriptions of the following two features appear in this section:
• 2-Port OC-48c/STM-16c POS/DPT Uplink Card
2-Port OC-48c/STM-16c POS/DPT Uplink Card
Platform: Cisco 10720
The Cisco 10720 2-port OC-48c/STM-16c POS/DPT uplink card enables you to use the Cisco 10720 router to perform the following tasks:
•Send IP packets directly over SONET/Synchronous Digital Hierarchy (SDH) frames.
•Interwork with the OC-48c/STM-16c POS/SDH line cards in Cisco 12000 series routers, and configure each side of a Spatial Reuse Protocol (SRP) ring as a Packet-over-SONET (POS) interface.
•Interwork with add/drop multiplexers (ADM) that provide SONET automatic protection switching (APS) for line and line card redundancy.
Also, you can convert a POS interface to SRP mode to use the 2-port OC-48c/STM-16c POS/DPT uplink card in an SRP ring to internetwork with OC-48c/STM-16c DPT/SRP line cards in Cisco 12000 series routers. For more information, see the "Versatile Optical Interface" section.
Note SRP is the underlying technology used in the Cisco Dynamic Packet Transport (DPT) family of products.
The default POS/SDH mode on the 2-port OC-48c/STM-16c POS/DPT uplink card supports PPP and High-Level Data Link Control (HDLC) encapsulation. see the Cisco Software Configuration for the Cisco 10720 Internet Router document for information about:
•POS commands that are supported on POS interfaces on Cisco 12000 series routers and Cisco 10720 routers.
•PPP and HDLC commands that are supported in POS/SDH mode.
•APS commands that are supported on POS interfaces on Cisco 12000 series routers and Cisco 10720 routers.
The Cisco Software Configuration for the Cisco 10720 Internet Router is available at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st18/10 720.htm
For information about how to use SRP mode in an SRP ring, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/srpapsgs.htm
Versatile Optical Interface
Platform: Cisco 10720
The Versatile Optical Interface feature allows you to convert interfaces on the 2-port OC-48/STM-16c POS/DPT uplink card in a Cisco 10720 router from the default Packet-over-SONET (POS)/Synchronous Digital Hierarchy (SDH) mode to Spatial Reuse Protocol (SRP) mode. There is no performance impact.
The Versatile Optical Interface feature allows you to take advantage of the high-speed OC48/STM16 DPT/SRP technology over fiber uplink and use the 2-port OC-48/STM-16c POS/DPT uplink card on either side of an SRP ring.
Note SRP is the underlying technology used in the Cisco Dynamic Packet Transport (DPT) family of products.
For information about how to use SRP mode in an SRP ring, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/srpapsgs.htm
The following example shows how to use the Versatile Optical Interface feature to convert a 2-port OC-48/STM-16c POS/DPT uplink card from POS to SRP mode:
router#
configure terminal
Enter the configuration commands, one per line. End with CNTL/Z.
router(config)# hw-module slot 1 srp
`hw-module' needs reload to take effect.
router(config)# ^Z
router# write
router# reload4OC-48c/STM-16c DPT Line Card
Platform: Cisco 12000 series
The 4OC-48c/STM-16c DPT line card provides a Dynamic Packet Transport (DPT) solution, based on the Cisco-developed Spatial Reuse Protocol (SRP), for supported Cisco 12000 series routers. SRP is the underlying technology used in the Cisco DPT family of products.
The line card provides connections for two complete OC-48c/STM-16c SRP rings through the use of interchangeable pluggable optical modules (POMs). The POMs interface with the high-speed switch fabric of the router and provide four OC-48c/STM-16c duplex, single-mode LC connections.
For information about how to install and configure the line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_srp/14307srp.htm
8-Port Fast Ethernet Half-Height Line Card
Platform: Cisco 10000 series
The 8-port Fast Ethernet Half-Height line card contains eight IEEE 802.3u-compliant 100BASE-TX ports to provide high-density uplinks to devices such as content servers, routers, and other Fast Ethernet (FE) devices. Each port autonegotiates between half and full duplex. Each port supports 100BASE-T, but does not support 10BASE-T.
You install this line card in a half-height slot splitter in a Cisco 10000 series chassis. You must first install the half-height slot splitter in the Cisco 10000 series chassis slot.
Because the 8-port Fast Ethernet Half-Height line card occupies only a half slot, each slot can support two line cards for a total of 16 ports. The Cisco 10000 supports multiple FE line cards.
For information about how to install the line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/8hwdocs/cardinst/fehw.htm
For information about how to configure the line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10ksw/fesw.htm
Gigabit Ethernet Half-Height Line Card
Platform: Cisco 10000 series
The Gigabit Ethernet Half-Height line card contains a single Gigabit Ethernet (GE) port that provides a trunk uplink to switches and core routers such as the Cisco 12000 series router.
The Gigabit Ethernet Half-Height line card provides the Cisco 10000 series router with an IEEE 802.3z compliant Ethernet interface that runs up to 1 Gbps in full-duplex mode. You install this line card in a half-height slot splitter in a Cisco 10000 series chassis. You must first install the half-height slot splitter in the Cisco 10000 series chassis slot.
You can run the Gigabit Ethernet Half-Height line card with a second line card in the other subslot to provide the Cisco 10000 series chassis with redundant links while only occupying a single slot. This redundancy allows you to service or replace one of the line cards without losing uplink connectivity. You may also use the other subslot for a different half-height line card.
The Gigabit Ethernet Half-Height line card uses a Small Form-factor Pluggable (SFP) Gigabit Interface Converter (GBIC) that supports a variety of GE interface types (SX and LX/LH), which you can change or upgrade at any time.
Note On a Cisco 10000 series router that is configured with a Performance Routing Engine 1 (PRE1), the maximum throughput of the Gigabit Ethernet Half-Height line cards is limited to 710 Mbps.
Note Only SFP GBICs purchased from Cisco work with the Gigabit Ethernet Half-Height line card software.
For information about how to install the line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/8hwdocs/cardinst/hhgblc.htm
For information about how to configure the line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10ksw/geos.htm
Modular Gigabit Ethernet Line Card
Platform: Cisco 12000 series
The Modular Gigabit Ethernet line card, which is designed for high-density and server-aggregation applications, provides the Cisco 12000 series routers with up to 10 optical 802.3 Gigabit Ethernet interfaces. These interfaces provide high-speed interconnects to other network devices, such as other Cisco 12000 series routers, or to other routers or layer 2 or layer 3 switches that support Gigabit Ethernet interfaces.
For information about how to install and configure the Modular Gigabit Ethernet line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_enet/13816.htm
For information about the complete set of software features that are supported on the Modular Gigabit Ethernet line card, see the Cisco 12000 Series Modular Gigabit Ethernet Data Sheet.
OC-192c/STM-64c DPT Line Card
Platform: Cisco 12000 series
The OC-192c/STM-64c DPT line card provides a Dynamic Packet Transport (DPT) solution, based on the Cisco-developed Spatial Reuse Protocol (SRP), for supported Cisco 12000 series routers. SRP is the underlying technology used with the Cisco DPT family of products. The card can be mated to a second OC-192c/STM-64c DPT line card to create one full OC-192c/STM-64c SRP ring.
When two line cards are not mated, each OC-192c/STM-64c DPT line card is the equivalent of a single-fiber SRP ring on side B. The single-fiber SRP ring has a wrap at each end to ensure that all data packets reach their destination.
For information about how to install and configure the line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_srp/13786srp.htm
New Software Features in Cisco IOS Release 12.0(23)S
This section describes new and changed features in Cisco IOS Release 12.0(23)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(23)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
3-Port Gigabit Ethernet Line Card Enhancements
Platform: Cisco 12000 series
The software features that are described in the following sections are now supported on the Cisco 12000 series 3-port Gigabit Ethernet line card:
• MPLS VPN Bundled in EoMPLS Microcode on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
• MPLS VPN Carrier Supporting Carrier on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
• MPLS VPN Interautonomous System on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
• Support for the CWDM GBIC Solution on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
MPLS VPN Bundled in EoMPLS Microcode on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
The Ethernet over MPLS (EoMPLS) microcode in the packet switching ASIC (PSA) on the 3-port Gigabit Ethernet line card now includes support for the Multiprotocol Label Switching Virtual Private Network (MPLS VPN) feature.
As a result, you can configure EoMPLS and MPLS VPN at the same time on the 3-port Gigabit Ethernet line card. When you enter the show controller psa feature command in privileged EXEC mode on the line card, MPLS VPN is included in the display:
router#
exec slot 6 show controller psa feature
========= Line Card (Slot 6) =========
-- Current microcode bundle: -----------------
EoMPLS
-- This bundle supports: ---------------------
Basic IP Forwarding
Basic MPLS Switching
MPLS VPN
Ethernet over MPLS
Multicast
For more information about how to configure and use MPLS VPNs, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/fs_ vpn.htm
MPLS VPN Carrier Supporting Carrier on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
For a feature description, see the "MPLS VPN Carrier Supporting Carrier for Additional Cisco 12000 Series Line Cards" section.
MPLS VPN Interautonomous System on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
For a feature description, see the "MPLS VPN Interautonomous System on Additional Cisco 12000 Series Line Cards" section.
MPLS VPN—VRF Selection Based on Source IP Address on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
Note The MPLS VPN—VRF Selection Based on Source IP Address feature was introduced in Cisco IOS Release 12.0(22)S for the Cisco 10720 router and the Cisco 12000 series routers. This release is introducing support for the feature on the 3-port Gigabit Ethernet line card.
The VRF Selection feature allows packets that arrive on an interface to be switched into the appropriate Virtual Private Network (VPN) routing/forwarding (VRF) Selection table based upon the source IP address of the packets. Once the packets have been "selected" into the correct VRF Selection routing table, they are processed normally based upon the destination address and forwarded through the rest of the Multiprotocol Label Switching (MPLS) VPN.
The VRF Selection feature is a "one-way" feature; it works on packets that come from the end users to the provider edge (PE) router.
For more information about the MPLS VPN—VRF Selection Based on Source IP Address feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fsvr f.htm
Support for the CWDM GBIC Solution on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
The Cisco Coarse Wave Division Multiplexing (CWDM) Gigabit Interface Converter (GBIC) solution has two main components: the Cisco CWDM GBICs and the Cisco OADM plug-in modules or mux/demux plug-in modules, which are rack-mounted in a Cisco CWDM OADM chassis external to the Cisco 12000 series router that contains the 3-port Gigabit Ethernet line card.
The CWDM OADM plug-in modules and mux/demux plug-in modules are passive optical components that multiplex together multiple wavelengths from multiple SingleMode Fiber (SMF) fiber pairs into one SMF fiber pair. Up to two CWDM plug-in modules can be rack-mounted by using the single-rack-unit CWDM chassis.
The CWDM GBICs plug into the standard GBIC receptacles on the faceplate of the 3-port Gigabit Ethernet line card and are connected to the CWDM OADM or mux/demux plug-in modules in the external CWDM chassis using SMF jumper cables with SC-type connectors.
The CWDM GBICs come in the following eight wavelengths: 1470, 1490, 1510, 1530, 1550, 1570, 1590, and 1610 nanometers (nm).
A Cisco 12000 series router that is equipped with a 3-port Gigabit Ethernet line card and CWDM GBICs can be connected into a CWDM network through external CWDM plug-in modules in the following deployment scenarios:
•Point-to-point—Two endpoints are directly connected via a fiber link. You can add or drop up to eight Gigabit Ethernet channels into a pair of single-mode fiber.
•Hub-and-spoke (ring)—Multiple nodes (spokes) are connected with a hub location through a ring of single-mode fiber. Each hub/node connection can consist of one or more wavelengths, each carrying a full Gigabit Ethernet channel.
•Mesh (ring)—Combines the hub-and-spoke and point-to-point (or even multiple point-to-point) connections in parallel on the same CWDM optic link. The maximum of eight GBIC wavelengths allows different combinations of these scenarios.
For more information about how to install and configure CWDM GBICs in a Cisco 12000 series 3-port Gigabit Ethernet line card, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_enet/10551ge3.htm
Unicast Reverse Path Forwarding Bundled in Sampled NetFlow Microcode on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card
The Sampled NetFlow microcode in the packet switching ASIC (PSA) on the 3-port Gigabit Ethernet line card now includes support for unicast Reverse Path Forwarding (uRPF). As a result, you can configure Sampled NetFlow and uRPF at the same time on the line card.
Both the classic "strict mode" uRPF and enhanced "loose check" versions of uRPF are supported on the 3-port Gigabit Ethernet line card and are documented in the following Cisco publications:
•Configuring Unicast Reverse Path Forwarding, Release 12.1
•Unicast Reverse Path Forwarding Enhancements, Release 12.1
•Unicast Reverse Path Forwarding Commands, Release 12.1
Note The acl option is not supported for the ip verify unicast command in the 3-port Gigabit Ethernet line card.
For more information about how to configure and use Sampled NetFlow, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/12ssanf.htm
8-Port OC-3/STM-1 ATM Line Card Enhancements
Platform: Cisco 12000 series
The software features that are described in the following sections are now supported on the Cisco 12000 series 8-port OC-3/STM-1 ATM line card:
• 128 ACLs on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
• ATM Cell Loss Priority Setting on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
• ATM VC Bundle Management on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
• MPLS VPN Carrier Supporting Carrier on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
• MPLS VPN Interautonomous System on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
128 ACLs on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
You can now configure input access control lists (ACLs) on a per-subinterface basis on the 8-port OC-3/STM-1 ATM line card.
The use of input ACLs on the 8-port OC-3/STM-1 ATM line card is subject to the following restrictions:
•Only input ACLs are supported.
•A maximum of 16 distinct input ACLs per line card and 128 ACL entries per ACL are supported in the packet switching ASIC (PSA) microcode because of memory limitations. Additional ACLs are processed by the line card CPU rather than the PSA microcode. This situation remains true even when one of the ACLs processing in the PSA microcode is removed and the total number of distinct ACLs drops to 16.
•An input ACL configuration on a subinterface is supported only on the 8-port OC-3/STM-1 ATM line card.
•Only Logical Link Control/Subnetwork Access Protocol (LLC/SNAP) encapsulation is supported in the PSA microcode. VC Mux or Network Layer Protocol Identifiers (NLPID) encapsulation is processed by the line card CPU.
•Basic IP and Multiprotocol Label Switching (MPLS) forwarding are supported together with input ACLs in the same 8-port OC-3/STM-1 ATM line card microcode bundle. Any other features are either not supported, are processed by the line card CPU, or are processed in another PSA microcode bundle.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/eacl 128.htm
ATM Cell Loss Priority Setting on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
Note The ATM Cell Loss Priority Setting feature was introduced in Cisco IOS Release 12.0(7)S for the Cisco 7500 series routers under the feature title ATM CLP Setting. This release is porting the feature into the Cisco 12000 series 8-port OC-3/STM-1 ATM line card.
Before development of the ATM Cell Loss Priority Setting feature, the Cell Loss Priority (CLP) bit in the ATM header of a cell provided a method of controlling the discarding of cells in a congested ATM environment. A CLP bit contains two settings: 0 and 1. Cells with a CLP bit setting of 1 are discarded before cells with a CLP bit setting of 0. Before the introduction of the ATM Cell Loss Priority Setting feature, the CLP bit was automatically set to 0 when Cisco routers converted packets into ATM cells for ATM networks.
The ATM Cell Loss Priority Setting feature enables users to control the ATM CLP bit setting on the 8-port OC-3/STM-1 ATM line card for the Cisco 12000 series routers. The CLP bit is set on each packet individually, and the default CLP bit setting is 0. The application of the ATM Cell Loss Priority Setting feature changes the CLP bit setting to 1. Therefore, users have the option to leave each packet with the default CLP bit setting of 0 or to establish a new CLP bit setting of 1.
The ATM Cell Loss Priority Setting feature offers improved bandwidth management by enabling users to extend their IP quality of service (QoS) policies into an ATM network by setting the ATM CLP bit in ATM cells in an outgoing ATM adaptation layer 5 (AAL5) packet based on the IP precedence or Multiprotocol Label Switching (MPLS) experimental bits of the incoming packets. A downstream device, such as an ATM switch, can then make congestion-alleviating decisions based on the CLP bit of the ATM cells. As congestion occurs in the ATM network, cells with the CLP bit set are more likely to be dropped, resulting in improved network performance for high priority traffic and applications.
For more information about the ATM Cell Loss Priority Setting feature, see the Cisco document that is specific to the Cisco 12000 series routers at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atmc lp23.htm
ATM VC Bundle Management on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
Before the introduction of the ATM VC Bundle Management feature, the 8-port OC-3/STM-1 ATM line card was capable of using Weighted Random Early Detection (WRED) and Modified Deficit Round Robin (MDRR) to classify and set priorities for packets, but all packets shared a single quality of service (QoS) virtual circuit (VC). The ATM VC Bundle Management feature addresses this limitation by enabling you to define an ATM VC bundle and add VCs to it. Each VC of a bundle has its own ATM traffic class and ATM traffic parameters. You can apply attributes and characteristics to discrete VC bundle members, or you can apply them collectively at the bundle level.
Using VC bundles, you can create differentiated service by flexibly distributing IP precedence levels over the different VC bundle members. You can map a single precedence level or a range of levels to each discrete VC in the bundle, thereby enabling individual VCs in the bundle to carry packets marked with different precedence levels. You can use WRED to further differentiate service across traffic that has different IP precedences, but that uses the same VC in a bundle.
For more information about the ATM VC Bundle Management feature, see the Cisco document that is specific to the Cisco 12000 series routers at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/vc_b un23.htm
MPLS VPN Carrier Supporting Carrier on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
For a feature description, see the "MPLS VPN Carrier Supporting Carrier for Additional Cisco 12000 Series Line Cards" section.
MPLS VPN Interautonomous System on the Cisco 12000 Series 8-Port OC-3/STM-1 ATM Line Card
For a feature description, see the "MPLS VPN Interautonomous System on Additional Cisco 12000 Series Line Cards" section.
Any Transport over MPLS
The following sections describe Any Transport over Multiprotocol Label Switching (AToM) features:
• Any Transport over MPLS: ATM AAL5 over MPLS
• Any Transport over MPLS: ATM Cell Relay over MPLS: VC Mode
• Any Transport over MPLS: Ethernet over MPLS
• Any Transport over MPLS: Frame Relay over MPLS
• Any Transport over MPLS: HDLC over MPLS
• Any Transport over MPLS: PPP over MPLS
Any Transport over MPLS: ATM AAL5 over MPLS
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series.
Note The Any Transport over MPLS: ATM AAL5 over MPLS feature was introduced in Cisco IOS Release 12.0(22)S for the Cisco 12000 series routers. This release is updating the feature and is porting it into the Cisco 7200 and Cisco 7500 series routers and the Cisco 12000 series IP Services Engine (ISE) line cards.
The Any Transport over MPLS: ATM AAL5 over MPLS feature provides an ATM permanent virtual circuit (PVC) for transporting ATM adaptation layer 5 (AAL5) protocol data units (PDUs) across an IP/Multiprotocol Label Switching (MPLS) backbone with rate-limit policing and configurable PVC priority values. A dynamic MPLS tunnel is configured to enable label imposition and disposition of encapsulated ATM PDUs transported between two edge routers having a Label Distribution Protocol (LDP) neighbor relationship.
Each routed PVC label stack has two levels of labels prepended to each ATM PDU: an Interior Gateway Protocol (IGP) stack consisting of zero or more labels and a PVC-based label. Label imposition and disposition are performed by routers at the edge of the MPLS backbone. The imposition router takes the ATM PDU and encapsulates it in an MPLS PDU for transport to the correct disposition router. The disposition router takes the MPLS PDU, de-encapsulates the ATM PDU, and delivers it to the correct ATM interface and virtual path identifier/virtual circuit identifier (VPI/VCI).
Cisco IOS Release 12.0(23)S introduces support the Any Transport over MPLS: ATM AAL5 over MPLS feature for the Cisco 7200 series and Cisco 7500 series routers and for the Cisco 12000 series IP Services Engine line cards.
ATM AAL5 over MPLS label disposition is supported for the for Cisco 12000 series IP Services Engine line cards, including:
•4-port OC-3c/STM-1c POS/SDH ISE line card
•8-port OC-3c/STM-1c POS/SDH ISE line card
•16-port OC-3c/STM-1c POS/SDH ISE line card
•4-port OC-12c/STM-4c POS/SDH ISE line card
•1-port OC-48c/STM-16c POS/SDH ISE line card
•4-port Channelized OC-12/STM-4 (DS3/E3, OC-3c/STM-1c) POS/SDH ISE line card
•1-port Channelized OC-48/STM-16 (DS3/E3, OC-3c/STM-1c) POS/SDH, OC-12c/STM-4c ISE line card
For more information about the Any Transport over MPLS: ATM AAL5 over MPLS feature, see the Any Transport over MPLS document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atom /index.htm
Any Transport over MPLS: ATM Cell Relay over MPLS: VC Mode
Platforms: Cisco 7200 series, Cisco 7500 series
Note Before the Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: VP Mode feature was introduced, the Any Transport over MPLS (AToM): ATM Cell Relay over MPLS: VC Mode feature was known as the Any Transport over MPLS: ATM Cell Relay over MPLS feature, that is, without a distinction between virtual circuit (VC) mode and virtual path (VP) mode.
With ATM cell relay functionality, ATM cells can be transported across Multiprotocol Label Switching (MPLS) networks transparently. This setup allows transportation of ATM signaling and Operations, Administration, and Maintenance (OAM) cells across a packet network, making a packet network invisible to the ATM network. The Any Transport over MPLS: ATM Cell Relay over MPLS feature enables service providers to use the same tools for provisioning and to aggregate the existing frame and ATM installations to a high-speed packet core that is based on IP/MPLS.
For more information about the Any Transport over MPLS: ATM Cell Relay over MPLS feature, see the Any Transport over MPLS document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atom /index.htm
Any Transport over MPLS: Ethernet over MPLS
Platforms: Cisco 7200 series, Cisco 7500 series
Note The Any Transport over MPLS: Ethernet over MPLS feature was introduced in Cisco IOS Release 12.0(22)S for the Cisco 10720 router and the Cisco 12000 series routers. This release is updating the feature and is porting it into the Cisco 7200 and Cisco 7500 series routers.
The Any Transport over MPLS: Ethernet over MPLS feature enables you to connect two VLAN networks that are in different locations, without using expensive bridges, routers, or switches at the VLAN locations. You can enable the Multiprotocol Label Switching (MPLS) backbone network to accept Layer 2 VLAN traffic by configuring the label edge routers (LERs) at both ends of the MPLS backbone.
For more information about the Any Transport over MPLS: Ethernet over MPLS feature, see the Any Transport over MPLS document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atom /index.htm
Any Transport over MPLS: Frame Relay over MPLS
Platforms: Cisco 7200 series, Cisco 7500 series
With the Any Transport over MPLS: Frame Relay over MPLS feature, Frame Relay traffic can be encapsulated in Multiprotocol Label Switching (MPLS) packets and forwarded over an MPLS backbone to other Frame Relay destinations. Service providers can quickly add new sites with less effort than with typical Frame Relay provisioning.
For more information about the Any Transport over MPLS: Frame Relay over MPLS feature, see the Any Transport over MPLS document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atom /index.htm
Any Transport over MPLS: HDLC over MPLS
Platforms: Cisco 7200 series, Cisco 7500 series
The Any Transport over MPLS: HDLC over MPLS feature enables a customer router to emulate a High-Level Data Link Control (HDLC) connection to another customer router across the packet backbone. Like PPP, this technology allows transportation of Cisco HDLC frames across the packet networks. HDLC over Multiprotocol Label Switching (MPLS) also works in transparent mode.
For more information about the Any Transport over MPLS: HDLC over MPLS feature, see the Any Transport over MPLS document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atom /index.htm
Any Transport over MPLS: PPP over MPLS
Platforms: Cisco 7200 series, Cisco 7500 series
The Any Transport over MPLS: PPP over MPLS feature enables service providers to encapsulate PPP frames across a Multiprotocol Label Switching (MPLS) core in order to emulate a PPP link across any layer transport. Using PPP over MPLS on Packet-over-SONET (POS) links enables service providers to create a "multiplexed" subinterface that can then be used to individually peer with other providers.
PPP over MPLS further enables service providers to provide a transparent PPP pass-through where the customer-edge routers can exchange the traffic via an end-to-end PPP session. Service providers can offer a virtual leased-line solution, and use the PPP subinterface capability to peer with multiple providers via a single POS connection.
For more information about the Any Transport over MPLS: PPP over MPLS feature, see the Any Transport over MPLS document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atom /index.htm
ATM OAM Emulation
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
If a provider edge (PE) router does not support the transport of Operation, Administration, and Maintenance (OAM) cells across a label switched path (LSP), you can use OAM cell emulation to transport the OAM cells. You configure OAM cell emulation on both PE routers to form two unidirectional LSPs, which emulate a virtual circuit (VC). You use the oam-ac emulation-enable command on both PE routers to enable OAM cell emulation.
OAM cell emulation sends loopback cells at regular intervals. The endpoint can be either of the following:
•End-to-end loopback, which sends OAM cells to the device at the end of the LSP.
•Segment loopback, which sends OAM cells to a device along the LSP.
The OAM cells include the following:
•Alarm indication signal (AIS)
•Remote defect indication (RDI)
These cells identify and report defects along a VC. When a physical link or interface failure occurs, intermediate nodes insert OAM AIS cells into all the downstream devices affected by the failure. When a router receives an AIS cell, it marks the logical interface down and sends an RDI cell to inform the remote end about the failure.
For information on configuring OAM cell emulation, see the "Configure OAM Cell Emulation for AAL5 over MPLS" section in the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atom /fsatomb.htm
ATM OAM Traffic Reduction
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
The ATM OAM Traffic Reduction feature improves Operation, Administration, and Maintenance (OAM) scalability by reducing OAM cell traffic by 50 percent when OAM is enabled on both ends. The ATM OAM Traffic Reduction feature detects OAM cells that are enabled on both ends of a virtual circuit (VC), and then suppresses the transmission of OAM cell requests at one end.
For more information about the ATM OAM Traffic Reduction feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atmo am.htm
Cisco Nonstop Forwarding with Stateful Switchover on the Cisco 12000 Series Performance Route Processor and the Cisco 12000 Series 1-Port and 3-Port Gigabit Ethernet Line Cards
Platform: Cisco 12000
The Cisco Nonstop Forwarding with Stateful Switchover feature was introduced in Cisco IOS Release 12.0(22)S. This release is porting the feature into the Cisco 12000 series Performance Route Processor and the Cisco 12000 series 1-port Gigabit Ethernet (GE) and 3-port GE line cards.
For information, see the "Cisco Nonstop Forwarding with Stateful Switchover" section and see the following documents:
•For more information about the Cisco Nonstop Forwarding (NSF) feature, see the Cisco Nonstop Forwarding document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/ nsf_sso/nsf23s.htm
•For more information about the Stateful Switchover (SSO) feature, see the Stateful Switchover document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/ nsf_sso/sso23s.htm
Dynamic Layer-3 VPNs (L3VPNs) (RFC-2547 based) with Multipoint GRE (mGRE) Tunnel Support
Platforms: Cisco 7200 series, Cisco 7500 series
The Dynamic Layer-3 VPNs (L3VPNs) (RFC-2547 based) with Multipoint GRE (mGRE) Tunnel Support feature provides an IP-based alternative to the Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) that are used to transport IP Virtual Private Network (VPN) traffic across the core network between provider edge (PE) routers. This feature can be used instead of (or together with) MPLS to transport VPN traffic across a service provider network.
Fast EtherChannel and Gigabit EtherChannel on the Cisco 10720 Router
Platform: Cisco 10720
Note The Fast EtherChannel feature was introduced in Cisco IOS Release 12.0(8)S for the Cisco 7200 series routers. This release is porting the feature into the Cisco 10720 router and adding support for Gigabit EtherChannel.
The EtherChannel feature allows multiple Fast Ethernet and Gigabit Ethernet point-to-point links to be bundled into one logical link to provide bidirectional bandwidth of up to 800 Mbps. On the Cisco 10720 router, the EtherChannel feature is supported on both Fast Ethernet (FE) and Gigabit Ethernet (GE) ports:
•A maximum of 8 FE interfaces can be bundled together in a Fast EtherChannel on the 24-port Ethernet access card.
•A maximum of 4 GE interfaces can be bundled together in a Gigabit EtherChannel on the 4-port Gigabit Ethernet 8-Port 10/100 Ethernet TX access card.
EtherChannel is implemented on the Cisco 10720 router as follows:
•You configure quality of service (QoS) features on an FE or GE interface with the modular quality of service command-line interface (MQC). Using MQC, you create service policies for traffic classes and attach the policies to a Fast EtherChannel interface.
•When you use committed access rate (CAR) on an EtherChannel interface, the traffic rate on the entire channel is limited to the configured CAR value.
•On a physical EtherChannel interface, traffic is shaped according to the percentage of bandwidth allocated to the port using the bandwidth and priority commands.
•Fast and Gigabit EtherChannels do not support Universal Tunnel Interface (UTI), Layer 2 Tunneling Protocol version 3 (L2TPv3), or Ethernet over Multiprotocol Label Switching (EoMPLS) tunneling.
•All ports in a Fast or Gigabit EtherChannel must be the same speed (10 Mbps or 100 Mbps) and full duplex. Bundled EtherChannel ports can be contiguous.
•802.3ad link aggregation using Link Aggregate Control Protocol (LACP) is not supported.
•When an individual EtherChannel link fails, traffic is redistributed to the remaining active links.
•An output FE or GE port is selected using a hashing algorithm that is based on the source and destination addresses. One IP flow is, therefore, always sent out on the same port.
•802.1q VLANs are supported on Fast EtherChannel and Gigabit EtherChannel interfaces.
For more information about how to configure and use the EtherChannel feature, see the original Cisco document written for Cisco IOS Release 11.1 CC, at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios111/ca111/fechan.htm
Generic Routing Encapsulation (GRE) Tunnel Keepalive
Platforms: Cisco 7200 series, Cisco 7500 series
The Generic Routing Encapsulation (GRE) Tunnel Keepalive feature enables you to configure keepalive packets to be sent over IP-encapsulated GRE tunnels. You can specify the number of times a device will attempt to send keepalive packets before the interface becomes inactive.
Globalized Channelizations
Platform: Cisco 10000 series
With the Globalized Channelization feature, the Cisco 10000 series 1-port channelized OC-12 line card and 4-port channelized STM-1 line card support the following globalized channelization modes:
•SONET channelization:
–STS-1 over DS3/T3
–STS-1 over DS3/T3 over DS1
–STS-1 over DS3/T3 over DS3 subrate
–STS-1 over VT1.5 over DS1
–STS-1 over VT2 over E1
•Synchronous Digital Hierarchy (SDH) channelization:
–STM-1 over AU-3 over DS3/T3
–STM-1 over AU-3 over DS3/T3 over DS3 subrate
–STM-1 over AU-3 over TUG-2 over C-11 over DS1/T1
–STM-1 over AU-3 over TUG-2 over C-12 over E1
–STM-1 over AU-4 over TUG-3 over TUG-2 over C-11 over DS1/T1
–STM-1 over AU-4 over TUG-3 over TUG-2 over C-12 over E1
GRE Tunnel IP Source and Destination VRF Membership
Platforms: Cisco 7200 series, Cisco 7500 series
The GRE Tunnel IP Source and Destination VRF Membership feature makes it possible for you to specify the Virtual Private Network (VPN) routing/forwarding (VRF) membership of the Generic Routing Encapsulation (GRE) tunnel IP source and destination.
IP Options Selective Drop
Platform: Cisco 12000 series
Before the introduction of the IP Options Selective Drop feature, Cisco IOS routers may have been vulnerable to large-scale denial of service (DOS) attacks from IP Options packets because these packets cannot be handled by hardware engines, so they must be sent to software processing paths. The IP Options Selective Drop feature allows users to filter these packets, thereby mitigating the effects of the packets on a router and downstream routers.
The IP Options Selective Drop feature allows the users to drop (that is, the router drops all IP Options packets that it receives and prevents options from going deeper into the network) or ignore (that is, the router treats the packets as though they have no IP Options) all IP Options packets that are destined for the router. For many users, dropping the packets is the best solution. However, in environments where some IP Options may be legitimate, reducing the load that the packets present on the routers is sufficient. Thus, users may see skip options processing on the router and forward the packet as though it were pure IP.
For more information about the IP Options Selective Drop feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/sel_ drop.htm
IP Services Engine Line Card Enhancements (2)
Platform: Cisco 12000 series
In addition to the enhancements that were introduced in Cisco IOS Release 12.0(22)S, new software features have been added to Cisco 12000 series IP Services Engine (ISE) line cards, including:
•4-port OC-3c/STM-1c POS/SDH ISE line card
•8-port OC-3c/STM-1c POS/SDH ISE line card
•16-port OC-3c/STM-1c POS/SDH ISE line card
•4-port OC-12c/STM-4c POS/SDH ISE line card
•1-port OC-48c/STM-16c POS/SDH ISE line card
•4-port Channelized OC-12/STM-4 (DS3/E3, OC-3c/STM-1c) POS/SDH ISE line card
•1-port Channelized OC-48/STM-16 (DS3/E3, OC-3c/STM-1c) POS/SDH, OC-12c/STM-4c ISE line card
The software features that are now supported on Cisco 12000 series ISE line cards are described in the following sections:
• ATM AAL5 over MPLS on Cisco 12000 Series ISE Line Cards
• Access Control Entry (ACE) Counters on Cisco 12000 Series ISE Line Cards
• BGP Policy Accounting on Cisco 12000 Series ISE Line Cards
• IP and MPLS Subinterface Counters on Cisco 12000 Series ISE Line Cards
• IPv6 Hardware Forwarding on Cisco 12000 Series ISE Line Cards
• MPLS Traffic Engineering (TE)—Diff-Serv-Aware on Cisco 12000 Series ISE Line Cards
• Policy-Based Routing on Cisco 12000 Series ISE Line Cards
• Route Processor Redundancy Plus on Cisco 12000 Series ISEIP Services Engine Line Cards
ATM AAL5 over MPLS on Cisco 12000 Series ISE Line Cards
For a feature description, see the "Any Transport over MPLS: ATM AAL5 over MPLS" section.
Access Control Entry (ACE) Counters on Cisco 12000 Series ISE Line Cards
Cisco 12000 series ISE line cards support the logging and display of counters for the individual entries on an access control list (ACL). You can display an aggregate counter (number of matches) for all entries on an access list using the show access-lists access-list-number command in privileged EXEC mode as shown here:
router# show access-lists 108
Extended IP access list 108
permit tcp any host 1.1.1.1 gt 35
deny tcp any 1.1.1.0 0.0.0.255
permit ip any any
Individual entry match count isn't available
Aggregated matches: permit/deny 142325577/0
After you connect to the Cisco IOS image running on a Cisco 12000 series ISE line card, you can also display counters for individual access control entries (ACEs) using the show access-lists hardware interface interface-type slot:port [in | out] command:
Router# attach 2
Entering Console for 4 Port Packet Over SONET OC-3c/STM-1 in Slot: 2
Type exit to end this session
Press RETURN to get started!
LC-Slot2# show access-lists hardware interface pos 0:1 in
permit tcp any host 1.1.1.1 fragment (101 matches)
permit tcp any host 1.1.1.1 gt 35 (78 matches)
deny tcp any 1.1.1.0 0.0.0.255 (17 matches)
permit ip any any (316214931 matches)
Where:
slot:port specifies an ISE interface.
interface-type specifies the type of interface; for example, pos for Packet-over-SONET.
The in keyword displays the number of incoming (receive) packets on the interface that match each access list entry.
The out keyword displays the number of outgoing (transmit) packets on the interface that match each access list entry.
Note The show access-lists hardware interface command may display a different number of ACL entries than the show access-list command.
In addition, you can display both aggregate ACL counters and individual ACE counters for an ISE interface as follows, starting in global configuration mode:
1. Enter the hw-module slot number tcam compile acl no-merge command to turn off merge:
Router(config)#
hw-module slot 2 tcam compile acl no-merge2. In interface configuration mode, enter the no ip access-list access-list-number [in | out] command to unconfigure the access control list from the interface:
Router(config)#
interface pos 2/0:1
Router(config-if)#
no ip access-list 108 in3. In interface configuration mode, enter the ip access-list access-list-number [in | out] command to reconfigure the access control list to the interface:
Router(config-if)#
ip access-list 108 in4. In privileged EXEC mode, enter the show access-list access-list-number command to display both aggregate ACL counters and individual ACE counters:
Router#
show access-list 108
Extended IP access list 108
deny ip any host 1.1.1.1 (182 matches)
permit ip any any (18935489 matches)
Individual entry match count isn't available
Aggregated matches: permit/deny 18935671/0
For information about how to configure an access list, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113t/113t_3/stdlog.htm
BGP Policy Accounting on Cisco 12000 Series ISE Line Cards
Note For the Cisco 12000 series routers, the BGP Policy Accounting feature was introduced in Cisco IOS Release 12.0(10)S. This release is porting the feature into Cisco 12000 series IP Services Engine (ISE) line cards.
Border Gateway Protocol (BGP) policy accounting measures and classifies IP traffic that is sent to, or received from, different peers. Policy accounting is enabled on an input interface, and counters based on parameters such as community list, autonomous system number, or autonomous system path are assigned to identify the IP traffic.
Using BGP policy accounting, you can account for traffic according to the route it traverses. Service providers can identify and account for all traffic by customer and bill accordingly.
BGP policy accounting is implemented on Cisco 12000 series ISE line cards as follows:
•BGP policy accounting is performed in ternary content addressable memory (TCAM).
•BGP policy accounting is supported both on ISE physical interfaces and subinterfaces.
•BGP policy accounting is supported only on the input side of an ISE interface or subinterface; it is not supported on the output side.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s9/s_bgp pa.htm
IP and MPLS Subinterface Counters on Cisco 12000 Series ISE Line Cards
Counters for IP and Multiprotocol Label Switching (MPLS) traffic are supported on the subinterfaces of Cisco 12000 series IP Services Engine (ISE) line cards, and are implemented on ISE subinterfaces as follows:
•The accounting for IP and MPLS traffic on ISE subinterfaces is performed in ternary content addressable memory (TCAM).
•IP and MPLS counters are supported on both input and output sides of ISE subinterfaces.
•A TCAM lookup is not performed for nonroutable packets; that is, packets with destination addresses for which a route does not exist. These packets are, therefore, not counted in IP/MPLS subinterface counters.
To display the counters for IP and MPLS traffic on ISE subinterfaces, use the show interface interface-type slot/port:subinterface command in privileged EXEC mode; for example:
Router#
show interface pos 2/0:1
POS2/0.1 is up, line protocol is up
Hardware is Packet over SONET
Internet address is 33.33.33.2/24
MTU 4470 bytes, BW 622000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation FRAME-RELAY IETF
POS2/0.1
Protocol Pkts In Chars In Pkts Out Chars Out
IP 0 0 0 0
MPLS 0 0 0 0
IPv6 Hardware Forwarding on Cisco 12000 Series ISE Line Cards
Note IPv6 was introduced in Cisco IOS Release 12.0(22)S. This release is porting the feature into additional Cisco 12000 series line cards. See also the "IPv6 on Additional Cisco 12000 Series Line Cards" section.
IP version 6 (IPv6) is now supported on Cisco 12000 series IP Services Engine (ISE) line cards. IPv6, formerly called IPng (next generation), is the latest version of IP and offers many benefits, such as a larger address space, over the previous version of IP (version 4).
IPv6 is implemented on Cisco 12000 series ISE line cards as follows:
•IPv6 supports access control lists (ACLs) on input and output interfaces only in Cisco IOS software. If you configure input or output ACLs on an ISE interface, IPv6 packets are sent to the line card CPU for processing.
•If the number of IPv6 routes exceeds the hardware capacity of the ternary content addressable memory (TCAM), the following error message is displayed to describe how to increase the TCAM hardware capacity for IPv6 routes:
EE48-3-IPV6_TCAM_CAPACITY_EXCEEDED: IPv6 pkts will be software switched.
To support more IPv6 routes in hardware:
Get current TCAM usage with: show controllers ISE <slot> tcam
In config mode, reallocate TCAM regions e.g. reallocate Netflow TCAM to IPv6
hw-module slot <num> tcam carve rx_ipv6 <prefix> <v6-percent>
hw-module slot <num> tcam carve rx_top_nf <nf-percent>
Verify with show command that sum of all TCAM regions = 100%
Reload the linecard for the new TCAM carve config to take effect
WARNING: Recarve may affect other input features(ACL,CAR,MQC,Netflow)
TCAM is used for forwarding lookups. To increase TCAM capacity for handling IPv6 routes, you must use the hw-module slot number tcam carve rx_ipv6 prefix v6-percentage command in privileged EXEC mode, where: prefix specifies the prefix length of an IPv6 region in TCAM and v6-percentage specifies the percentage of TCAM hardware used by the specified IPv6 prefix.
For example, you can change the IPv6 region for prefix length 10 from 0 percent (default) to 15 percent of the TCAM hardware by reallocating the NetFlow region from 35 percent (default) to 20 percent as follows:
Router#
hw-module slot 3 tcam carve rx_ipv6 10 15
Router#
hw-module slot 3 tcam carve rx_nf 20For information about how to configure and use IPv6, see the Cisco documents at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
Modular Quality of Service Command-Line Interface (MQC) MIB Support on Cisco 12000 Series ISE Line Cards
The class-based quality of service (QoS) Management Information Base (class-based QoS MIB) that supports the modular quality of service command-line interface (MQC) feature is now supported on Cisco 12000 series IP Services Engine (ISE) line cards. This MIB provides read access to QoS configurations, and QoS statistics information based on the MQC, including information regarding class map and policy map parameters.
To locate the class-based QoS MIB, use the Cisco Network Management Toolkit for MIBs tool at the following location:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Modular Quality of Service Command-Line Interface (MQC) to Configure QoS on Frame Relay Subinterfaces on Cisco 12000 Series ISE Line Cards
You can use the modular quality of service command-line interface (MQC) to configure quality of service (QoS) for Frame Relay subinterfaces on Cisco 12000 series IP Services Engine (ISE) line cards. The following QoS policy actions are supported on incoming (receive) subinterfaces:
•Police
•Set
•Shape
•Random-detect (if Shape is configured)
•Queue-limit (if Shape is configured)
On outgoing (transmit) subinterfaces, the following policy actions are supported:
•Bandwidth (specified as an absolute rate, not as a percentage of the line rate)
•Shape
•Random-detect
•Queue-limit
•Priority
•Police
•Set
Because of hardware reasons, the following features are not supported on Cisco 12000 series ISE line cards:
•Frame Relay traffic shaping
•Frame Relay DE bit marking
•Link fragmentation and interleaving (LFI)
•Hierarchical policy maps
In addition, the following limitations apply:
•MQC cannot be used for Frame Relay point-to-multipoint subinterfaces.
•A Frame Relay data-link connection identifier (DLCI) must be defined under a subinterface configuration for QoS to be defined on it. MQC will not apply if the DLCI is defined directly under the interface configuration.
To configure the MQC on a Frame-Relay subinterface, you must:
1. Define a traffic class using the class-map command.
2. Define a policy map using the policy-map command for the traffic class defined in Step 1. (The service policy map should include a default class with configured bandwidth so that each DLCI has its own default class queue available.)
3. Define a map class using the map-class frame-relay command and then create a service input/output policy.
4. Attach the map class to a Frame Relay subinterface using the frame-relay class command.
For information about how to use the class-map and policy-map commands to create a service policy for a traffic class, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5/mq c/mcli.htm
For information about how to use the map-class frame-relay and frame-relay class commands, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/qos_c/qcprt4/qcdfrts.htm
MPLS Traffic Engineering (TE)—Automatic Bandwidth Adjustment for (TE) Tunnels on Cisco 12000 Series ISE Line Cards
Note For the Cisco 12000 series routers, the MPLS Traffic Engineering (TE)—Automatic Bandwidth Adjustment for (TE) Tunnels feature was introduced in Cisco IOS Release 12.0(22)S. This release is porting the feature into Cisco 12000 series IP Services Engine (ISE) line cards.
Cisco 12000 series ISE line cards support Multiprotocol Label Switching (MPLS) Traffic Engineering (MPLS TE) features for constraint-based routing of "guaranteed" traffic and automatic bandwidth adjustment in TE tunnels.
MPLS traffic engineering automatically establishes and maintain tunnels across the backbone. The path used by a given tunnel at any point in time is determined based on the tunnel resource requirements and network resources, such as bandwidth.
The MPLS Traffic Engineering (TE)—Automatic Bandwidth Adjustment for (TE) Tunnels automatically adjusts the bandwidth allocation for traffic engineering tunnels based on their measured traffic load. The autobandwidth feature samples the average output rate for each tunnel configured for automatic bandwidth adjustment, and periodically (for example, once per day) adjusts the allocated bandwidth of the tunnel to be the largest sample for the tunnel since the last adjustment. The frequency with which tunnel bandwidth is adjusted and the allowable range of adjustments is configurable on a per-tunnel basis. In addition, the sampling interval and the interval over which to average tunnel traffic to obtain the average output rate is user-configurable on a per-tunnel basis.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fstea ut.htm
MPLS Traffic Engineering (TE)—Diff-Serv-Aware on Cisco 12000 Series ISE Line Cards
Note For the Cisco 12000 series routers, the MPLS Traffic Engineering (TE)—Diff-Serv-Aware feature was introduced in Cisco IOS Release 12.0(22)S (see "Diff-Serv-Aware Traffic Engineering (DS-TE) for the Cisco 12000 Series Internet Routers" section). This release is porting the feature into Cisco 12000 series IP Services Engine (ISE) line cards.
Cisco 12000 series ISE line cards support Multiprotocol Label Switching TE (MPLS TE) features for constraint-based routing of "guaranteed" traffic and automatic bandwidth adjustment in TE tunnels.
MPLS traffic engineering automatically establishes and maintain tunnels across the backbone. The path used by a given tunnel at any point in time is determined based on the tunnel resource requirements and network resources, such as bandwidth.
The MPLS TE Diff-Serv-Aware feature allows you to manage the bandwidth reservable on each link for constraint-based routing (CBR) purposes through two bandwidth pools: a global pool and a subpool. The subpool can be limited to a smaller portion of the link bandwidth. You can then configure tunnels using the sub-pool bandwidth in conjunction with MPLS quality of service (QoS) mechanisms to deliver guaranteed bandwidth services end-to-end across the network.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/12s_ dste.htm
Policy-Based Routing on Cisco 12000 Series ISE Line Cards
Note For the Cisco 12000 series routers, the Policy-Based Routing feature was introduced in Cisco IOS Release 12.0(22)S on the Engine 4 line cards. This release adds support for the Cisco 12000 series IP Services Engine (ISE) line cards.
Policy-based routing (PBR) provides a flexible means of routing packets by allowing you to configure a defined policy for traffic flows, lessening reliance on routes derived from routing protocols. You can set up PBR as a way to route packets based on configured policies. For example, you can implement routing policies to allow or deny paths based on the identity of a particular end system or an application protocol.
Note The match-length command used in route-map configuration mode to configure an allow or deny path based on packet size is not supported on Cisco 12000 series ISE line cards.
Also, you can configure a unique policy for each input interface, or one policy for multiple interfaces. A policy contains one or more route maps. Each route map has one or more statements that specify the required matching criteria and actions. For example, a matching statement can be an access control list (ACL). If the matching criteria are met, the action statements are executed. An action statement can contain a routing action or a quality of service (QoS) action. The routing action determines what output interfaces the packet should take or what the next hop is. The QoS action may be to set the type of service (ToS) or IP precedence parameter to a specific value.
PBR is implemented on the Cisco 12000 series ISE line cards as follows:
•PBR cannot be configured to execute an action on multicast packets. PBR takes actions only on IP traffic.
•PBR can be applied to all kinds of interfaces or subinterfaces.
•The set interfaces command works only on point-to-point interface types.
•PBR does not support a traffic engineering (TE) tunnel as the next hop (outbound interface).
For information about how to configure policy-based routing, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_c/fqcprt1/qcfpbr.htm
Route Processor Redundancy Plus on Cisco 12000 Series ISEIP Services Engine Line Cards
Note For the Cisco 12000 series routers, the Route Processor Redundancy Plus feature was introduced in Cisco IOS Release 12.0(22)S on a variety of line cards. This release adds support for the Cisco 12000 series IP Services Engine (ISE) line cards.
When two Route Processors (RPs) are installed in a Cisco 12000 series router chassis, one RP acts as the active RP, and the other acts as a backup, or standby, RP. If the active RP fails, or is removed from the system, the standby RP detects the failure and initiates a switchover. During a switchover, the standby RP assumes control of the router, connects with the network interfaces, and activates the local network management interface and system console.
Using the Route Processor Redundancy Plus (RPR+) feature, the standby RP is fully initialized and configured, which allows RPR+ to dramatically shorten the switchover time if the active RP fails, or if a manual switchover is performed. Because both the startup and running configuration are continually synchronized from the active to the standby RP, line cards are not reset during a switchover. The interfaces remain up during this transfer, so neighboring routers do not detect a link flap (that is, the link does not go down and back up).
RPR+ is now supported on Cisco 12000 series ISE line cards. For information about how to configure and use RPR+, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st17/rpr _plus.htm
IPv6 Extended Access Control Lists
Platform: Cisco 12000 series
In Cisco IOS Release 12.2(2)T or later releases and Cisco IOS Release 12.0(21)ST, standard IP version 6 (IPv6) access control list (ACL) functionality is used for basic traffic filtering functions—traffic filtering is based on source and destination addresses, inbound and outbound to a specific interface, and with an implicit deny statement at the end of each access list (which is functionality similar to standard ACLs in IP version 4 [IPv4]).
IPv6 ACLs are defined and their deny and permit conditions are set by using the ipv6 access-list command with the deny and permit keywords in global configuration mode.
In Cisco IOS Release 12.0(23)S or later releases, the standard IPv6 ACL functionality is extended to support—in addition to traffic filtering based on source and destination addresses—filtering of traffic based on IPv6 option headers and optional, upper-layer protocol type information for finer granularity of control (functionality similar to extended ACLs in IPv4). IPv6 ACLs are defined by using the ipv6 access-list command in global configuration mode and their permit and deny conditions are set by using the deny and permit commands in IPv6 access list configuration mode. (Configuring the ipv6 access-list command places the router in IPv6 access list configuration mode, from which permit and deny conditions can be set for the defined IPv6 ACL.)
For more information, see the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
IPv6 on Additional Cisco 12000 Series Line Cards
Platform: Cisco 12000 series
Note IP version 6 (IPv6) was introduced in Cisco IOS Release 12.0(22)S. This release is porting the feature into additional Cisco 12000 series line cards. See also the "IPv6 Hardware Forwarding on Cisco 12000 Series ISE Line Cards" section.
IP is a packet-based protocol used to exchange data, voice, and video traffic over digital networks. IP handles addressing, fragmentation, reassembly, and protocol demultiplexing. It is the foundation on which all other IP protocols (collectively referred to as the IP Protocol suite) are built. As a network-layer protocol, IP contains addressing and control information that allows data packets to be routed. IPv6, formerly called IPng (next generation), is the latest version of IP that offers many benefits, such as a larger address space, over the previous version of IP (version 4).
For more information, see the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
Cisco IOS Release 12.0(23)S introduces support for IPv6 on the following Cisco 12000 series line cards:
•Cisco 12000 series Dynamic Packet Transport (DPT) line cards:
–2-port OC-12c/STM-4c DPT line card
–1-port OC-48c/STM-16c DPT line card
–4OC-48c/STM-16c DPT line card
–OC-192c/STM-64c DPT line card
•Cisco 12000 series Gigabit Ethernet line card:
–1-port 10-Gigabit Ethernet line card
–Modular Gigabit Ethernet line card
Note On the above-mentioned Gigabit Ethernet line cards, native IPv6 forwarding is supported in the slow path (that is, via the CPU); hardware-accelerated IPv6 forwarding through a server card is not yet supported.
•Cisco 12000 series Packet-over-SONET (POS) line cards:
–4-port OC-3c/STM-1c POS/SDH line card
–8-port OC-3c/STM-1c POS/SDH line card
–16-port OC-3c/STM-1c POS/SDH line card
–16-port OC-3c/STM-1c POS/SDH ISE line card
–1-port OC-12c/STM-4c POS/SDH line card
–4-port OC-12c/STM-4c POS/SDH line card
–4-port OC-12c/STM-4c POS/SDH ISE line card
–1-port OC-48c/STM-16c POS/SDH line card
–1-port OC-48c/STM-16c POS/SDH ISE line card
–4-port OC-48c/STM-16c POS/SDH line card
–1-port OC-192c/STM-64c POS/SDH line card
–16-port Channelized OC-3/STM-1 (DS3/E3) POS/SDH ISE line card
–4-port Channelized OC-12/STM-4 (DS3/E3, OC-3c/STM-1c) POS/SDH ISE line card
–1-port Channelized OC-48/STM-16 (DS3/E3, OC-3c/STM-1c) POS/SDH, OC-12c/STM-4c ISE line card
Layer 2 Tunneling Protocol Version 3
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10720, Cisco 12000 series
Layer 2 Tunneling Protocol version 3 (L2TPv3) is an Internet Engineering Task Force (IETF) l2tpext working group draft that provides several enhancements to the Layer 2 Tunnel Protocol 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 (Layer 2 VPNs).
L2TPv3 signaling is responsible for negotiating control plane parameters, session IDs and cookies, for performing authentication, and for exchanging configuration parameters. L2TPv3 is also used to reliably deliver hello messages and circuit status messages. These messages are critical to support circuit interworking, such as the Local Management Interface (LMI), and to monitor the remote circuit status.
L2TPv3 has two parts:
•A control plane responsible for setting up the connection.
•A data plane responsible for tunneling Layer 2 frames.
L2TPv3 provides Xconnect (Layer 2 tunneling via a pseudowire over IP) and Layer 2 VPN (provider edge [PE]-to-PE router service via Xconnect) support for Ethernet, 802.1q VLAN, Frame Relay, High-Level Data Link Control (HDLC), and PPP Layer 2 circuits, including both static (Universal Tunnel Interface [UTI]-like) and dynamic (using the new L2TPv3 signaling) forwarded sessions.
The UTI protocol is a Cisco proprietary protocol that offers a simple high-speed transparent Layer 2-to-Layer 2 service over an IP backbone. The UTI protocol lacks the signaling capability and standards support necessary for large-scale commercial service. To answer the need for a standard way to provide large-scale VPN connectivity over an IP core network, migration from UTI to L2TPv3 is introduced in Cisco IOS Release 12.0(23)S.
For more information about the L2TPv3 feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/l2tp v3.htm
Link Bundling
Platform: Cisco 12000 series
The Link Bundling feature allows you to group multiple point-to-point links into one logical link to provide higher bidirectional bandwidth (a bigger pipe), redundancy, and load sharing between two routers. The following types of link bundling are supported on Cisco 12000 series routers:
•Gigabit EtherChannel is used to bundle multiple Gigabit Ethernet (GE) interfaces.
•POS Channel is used to bundle multiple Packet-over-SONET (POS) interfaces.
Use link bundling on Cisco 12000 series routers in networks under the following conditions:
•Faster links do not exist.
•The next step available for increasing link capacity is too expensive.
•The operational costs to increase link capacity are too high.
Gigabit Ethernet and POS Channel link bundling on Cisco 12000 series routers provide flexible and incremental bandwidth with link redundancy and higher layer transparency to network applications. You can use Gigabit EtherChannel and POS channel in multiple locations in the same network.
For information about how to configure and use link bundling, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/lnkb ndl.htm
Manual IPv6 Tunnels
Platform: Cisco 12000 series
In previous releases, traffic with a destination of, or received from an IP version 6 (IPv6) tunnel that was manually configured would be processed by the Route Processor (RP) in the Cisco 12000 series router. The Manual IPv6 Tunnels feature allows IPv6 tunnel traffic that is manually configured to be processed in the Cisco IOS software on the CPU of the line card, which results in an enhanced performance.
For more information, see the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
MPLS Enhancements to the Interfaces MIB
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
The Interfaces MIB (IF-MIB) provides a method for managing interfaces that is based on Simple Network Management Protocol (SNMP). Each entry in the IF-MIB establishes indexing, statistics, and stacking relationships among underlying physical interfaces, subinterfaces, and Layer 2 protocols that exist within Cisco IOS software.
The enhancements add a Multiprotocol Label Switching (MPLS) layer to the IF-MIB as a Layer 2 protocol to provide statistics for traffic encapsulated as MPLS on an interface. In this new structure, MPLS data, such as MPLS-encapsulated traffic counters and the MPLS maximum transmission unit (MTU), resides on top of the underlying physical or virtual interface to allow separation from non-MPLS data.
The enhancements also allow you to view indexing, statistics, and stacking relationships using the ifStackTable. MPLS layer interfaces are stacked above the underlying physical or virtual interface that is actually forwarding the MPLS traffic. MPLS traffic engineering tunnels are then stacked above those MPLS layers.
The IF-MIB supports several types of interfaces. A virtual interface that provides protocol statistics for MPLS-encapsulated traffic has been added. This new interface is stacked above real Cisco IOS interfaces or subinterfaces, such as Ethernet (eth0)or ATM (atm1/1.1).
Cisco IOS software creates a corresponding MPLS sublayer above each interface capable of supporting MPLS when the MPLS encapsulation is enabled by issuing the mpls ip interface configuration command.
You can also create the interface layer if you enable MPLS traffic engineering (TE) by using the mpls traffic-eng tunnels interface configuration command.
Note You must also issue these commands in global configuration mode for MPLS IP or MPLS TE, or for both, to be enabled.
An IF MIB entry is created when you enable MPLS IP or MPLS TE tunnels, or both, on an interface; the entry is removed when you disable both MPLS IP and MPLS TE. For more information about the Interfaces MIB, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fsife mib.htm
MPLS Static Labels
Platform: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
Generally, label switching routers (LSRs) dynamically learn the labels they should use to label-switch packets by means of label distribution protocols that include:
•Label Distribution Protocol (LDP), the Internet Engineering Task Force (IETF) standard, used to bind labels to network addresses
•Resource Reservation Protocol (RSVP) used to distribute labels for traffic engineering (TE)
•Border Gateway Protocol (BGP) used to distribute labels for Multiprotocol Label Switching Virtual Private Networks (MPLS VPNs)
To use a learned label to label-switch packets, an LSR installs the label into its label forwarding information base (LFIB).
The MPLS Static Labels feature provides the means to configure statically:
•The binding between a label and an IP version 4 (IPv4) prefix
•The contents of an LFIB crossconnect entry
For more information about the MPLS Static Labels feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fs_s tlab.htm
MPLS Traffic Engineering (TE) on the Cisco 10720 Router
Platform: Cisco 10720
Note The MPLS Traffic Engineering (TE) feature was introduced in Cisco IOS Release 12.0(5)S. This release is porting the feature into the Cisco 10720 router: the feature is supported on Packet-over-SONET interfaces on the 2-port OC-48c/STM-16c POS/DPT uplink card.
Multiprotocol Label Switching (MPLS) traffic engineering enables an MPLS backbone to replicate and expand upon the traffic engineering capabilities of Layer 2 ATM and Frame Relay networks. Traffic engineering is essential for service provider and Internet service provider (ISP) backbones. Both backbones must support a heavy use of transmission capacitance, the networks must be very resilient, so that they can withstand link or node failures.
MPLS traffic engineering has the following features:
•Provides an integrated approach to traffic engineering. With MPLS, traffic engineering capabilities are integrated into Layer 3, which optimizes the routing of IP traffic, given the constraints imposed by backbone capacity and topology.
•Routes traffic flows across a network based on the resources the traffic flow requires and the resources available in the network.
•Employs constraint-based routing in which the path for a traffic flow is the shortest path that meets the resource requirements (constraints) of the traffic flow.
•In MPLS traffic engineering, the traffic flow has bandwidth requirements, media requirements, a priority versus other flows, and so on.
•Recovers to link or node failures that change the topology of the backbone by adapting to a new set of constraints.
On the Cisco 10720 router, MPLS traffic engineering is supported on Packet-over-SONET interfaces on the 2-port OC-48c/STM-16c POS/DPT uplink card.
For more information about the MPLS Traffic Engineering feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fs23 te.htm
MPLS VPN Carrier Supporting Carrier for Additional Cisco 12000 Series Line Cards
Platform: Cisco 12000 series
The following sections describe MPLS VPN Carrier Supporting Carrier features:
Note The MPLS VPN Carrier Supporting Carrier and MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution features were introduced in Cisco IOS Release 12.0(22)S. This release is porting the features into the Cisco 12000 series 3-port Gigabit Ethernet line card and the 8-port OC-3/STM-1 ATM line card.
MPLS VPN Carrier Supporting Carrier on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card and 8-Port OC-3/STM-1 ATM Line Card
The MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution feature is now supported in 3-port Gigabit Ethernet line cards in the Cisco 12000 series routers. The MPLS VPN Carrier Supporting Carrier feature enables one MPLS VPN-based service provider to allow other service providers to use a segment of its backbone network.
For more information about MPLS VPN Carrier Supporting Carrier, see the Cisco document at following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fscs c23.htm
MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card and 8-Port OC-3/STM-1 ATM Line Card
The MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution feature (that is, with labels) allows you to configure your carrier supporting carrier (CsC) network to enable Border Gateway Protocol (BGP) to transport routes and Multiprotocol Label Switching (MPLS) labels between the backbone carrier provider edge (PE) routers and the customer carrier customer edge (CE) routers. Previously you had to use Label Distribution Protocol (LDP) to carry the labels and an Interior Gateway Protocol (IGP) to carry the routes between PE and CE routers to achieve the same goal.
Feature Implementation on the 3-Port Gigabit Ethernet Line Card
The MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution feature is implemented on the Cisco 12000 series 3-port Gigabit Ethernet line card in its own microcode bundle.
To verify that the CsC microcode bundle is loaded, use the show controller psa feature command in privileged EXEC mode as shown here:
Router#
show controller psa feature
CsC
-- This bundle supports: ---------------------
Basic IP Forwarding
Basic MPLS Switching
Sampled Netflow
MPLS VPN
CsC
Multicast
Per Packet Loadbalancing
Source MAC Accounting
Further Information
For more information about MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution (with labels), see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fscs cl23.htm
MPLS VPN Features for Additional Cisco 12000 Series Line Cards
Platform: Cisco 12000 series
The following sections describe MPLS VPN features:
Note The MPLS VPN features were introduced in Cisco IOS Release 12.0(22)S. This release is porting selected MPLS VPN features into the Cisco 12000 series Modular Gigabit Ethernet line card and the 1-port 10-Gigabit Ethernet line card.
MPLS-VPN Support on the Cisco 12000 Series Modular Gigabit Ethernet Line Card and the 1-Port 10-Gigabit Ethernet Line Card
The Virtual Private Network (VPN) feature for Multiprotocol Label Switching (MPLS) allows a Cisco IOS network to deploy scalable IPv4 Layer 3 VPN backbone services. An IP VPN is the foundation companies use for deploying or administering value-added services including applications and data hosting network commerce, and telephony services to business customers.
For information about how to configure and use MPLS VPNs, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fsvp n23.htm
Ethernet over MPLS on the Cisco 12000 Series Modular Gigabit Ethernet Line Card and the 1-Port 10-Gigabit Ethernet Line Card
The Ethernet over MPLS (EoMPLS) feature enables you to connect two VLAN networks that are in different locations, without using bridges, routers, or switches at the VLAN locations. You can enable the Multiprotocol Label Switching (MPLS) backbone network to accept Layer 2 VLAN traffic by configuring the label edge routers (LERs) at both ends of the MPLS backbone. The EoMPLS feature is part of the Any Transport over MPLS (AToM) product set.
For information about how to configure and use EoMPLS, see the see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/atom /index.htm
VLAN-to-MPLS VPN Mapping on the Cisco 12000 Series Modular Gigabit Ethernet Line Card and the 1-Port 10-Gigabit Ethernet Line Card
The VLAN-to-MPLS VPN Mapping feature allows you to configure the Multiprotocol Label Switching Virtual Private Network (MPLS VPN) feature on VLAN subinterfaces. You associate a VLAN subinterface with a VPN routing/forwarding instance (VRF). A VRF defines the VPN membership of a customer site that is attached to a provider edge (PE) router.
MPLS VPN Interautonomous System on Additional Cisco 12000 Series Line Cards
Platform: Cisco 12000 series
The following sections describe MPLS VPN Interautonomous System features:
Note The MPLS VPN—Interautonomous System Support and MPLS VPN Inter-AS—IPv4 BGP Label Distribution features were introduced in Cisco IOS Release 12.0(22)S for the Cisco 7200 series and Cisco 7500/RSP series routers and for selected Cisco 12000 series line cards. This release is porting the feature into the Cisco 12000 series 3-port Gigabit Ethernet line card and the 8-port OC-3/STM-1 ATM line card.
MPLS VPN—Interautonomous System Support on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card and 8-Port OC-3/STM-1 ATM Line Card
The MPLS VPN—Interautonomous Systems Support feature allows a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) to span service providers and autonomous systems. In some cases, VPNs need to reside on different autonomous systems in different geographic areas. (An autonomous system is a single network or group of networks that is controlled by a common system administration group and that uses a single, clearly defined routing protocol.) Also, some VPNs need to extend across multiple service providers (overlapping VPNs).
The MPLS VPN—Interautonomous Systems Support feature provides seamless integration of autonomous systems and service providers. Separate autonomous systems from different service providers can communicate by exchanging IPv4 network layer reachability information (NLRI) in the form of VPN-IPv4 addresses. The autonomous systems boundary routers (ASBRs) use the Exterior Border Gateway Protocol (EBGP) to exchange that information. Then, an Interior Gateway Protocol (IGP) distributes the network layer information for VPN-IPv4 prefixes throughout each VPN and each autonomous system.
For more information about MPLS VPN—Interautonomous System Support, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fsias 23.htm
MPLS VPN Inter-AS—IPv4 BGP Label Distribution on the Cisco 12000 Series 3-Port Gigabit Ethernet Line Card and 8-Port OC-3/STM-1 ATM Line Card
The MPLS VPN Inter-AS—IPv4 BGP Label Distribution feature enables you to set up a Virtual Private Network (VPN) service provider network so that the autonomous systems boundary routers (ASBRs) exchange IPv4 routes with Multiprotocol Label Switching (MPLS) labels of the provider edge (PE) routers. Route reflectors exchange Virtual Private Network version 4 (VPNv4) routes, using multihop, multiprotocol external Border Gateway Protocol (BGP). This configuration saves the ASBRs from having to store all the VPNv4 routes. Using the route reflectors to store the VPNv4 routes and forward them to the PE routers results in improved scalability.
For more information about MPLS VPN Inter-AS—IPv4 BGP Label Distribution, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fsias l23.htm
MQC match cos Command
Platform: Cisco 10720 router
Note The MQC match cos Command feature is also known under the feature title Modular QoS CLI (MQC) Match CoS.
The match cos command is now supported on the modular quality of service command-line interface (MQC) that is used to specify a traffic class and configure quality of service (QoS) policies for Cisco 10720 router interfaces.
Use the match cos command in QoS class-map configuration mode to match a packet based on a Layer 2 class of service (CoS) marking.
For more detailed information about the match cos command, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5/mq c/mcli.htm
Multicast-VPN—IP Multicast Support for MPLS VPNs
Platforms: Cisco 7200 series, Cisco 7500 series
The Multicast-VPN—IP Multicast Support for MPLS VPNs feature allows a service provider to configure and support multicast traffic in a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) environment. Because MPLS VPNs support only unicast traffic connectivity, deploying the Multicast-VPN feature in conjunction with MPLS VPN allows service providers to offer both unicast and multicast connectivity to MPLS VPN customers.
This feature supports routing and forwarding of multicast packets for each individual VPN routing and forwarding (VRF) instance, and it also provides a mechanism to transport VPN multicast packets across the service provider backbone.
The Multicast-VPN feature in Cisco IOS software provides the ability to support the multicast feature over a Layer 3 VPN. As enterprises extend the reach of their multicast applications, service providers can accommodate these enterprises over their MPLS core network. IP multicast is used to stream video, voice, and data to an MPLS VPN network core.
A VPN is network connectivity across a shared infrastructure, such as an Internet service provider (ISP). Its function is to provide the same policies and performance as a private network, at a reduced cost of ownership, thus creating many opportunities for cost savings through operations and infrastructure.
Historically, IP in IP generic route encapsulation (GRE) tunnels was the only way to connect through a service provider network. Although such tunneled networks tend to have scalability issues, they represent the only means of passing IP multicast traffic through a VPN.
MPLS was derived from tag switching and various other vendor methods of IP-switching support enhancements in the scalability and performance of IP-routed networks by combining the intelligence of routing with the high performance of switching. MPLS is now used for VPNs, which is an appropriate combination because MPLS decouples information used for forwarding of the IP packet (the label) from the information carried in the IP header.
A multicast VPN allows an enterprise to transparently interconnect its private network across the network backbone of a service provider. The use of a multicast VPN to interconnect an enterprise network in this way does not change the way that enterprise network is administered, nor does it change general enterprise connectivity.
For more information about the Multicast-VPN—IP Multicast Support for MPLS VPNs feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/12sm vpn.htm
OSPF Shortest Path First Throttling
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, and Cisco 12000 series
The OSPF Shortest Path First Throttling feature makes it possible to configure Shortest Path First (SPF) scheduling in millisecond intervals and to potentially delay SPF calculations during network instability. SPF is scheduled to calculate the Shortest Path Tree (SPT) when there is a change in topology. One SPF run may include multiple topology change events.
The interval at which the SPF calculations occur is chosen dynamically and is based on the frequency of topology changes in the network. The chosen interval is within the boundary of the user-specified value ranges. If network topology is unstable, SPF throttling calculates SPF scheduling intervals to be longer until the topology becomes stable.
For more information, see the Cisco document at the following location:
OSPF Support for Fast Hellos
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 10000 series, and Cisco 12000 series
The OSPF Support for Fast Hellos feature provides a way to configure hello packets at an interval less than 1 second. Such a configuration would result in faster convergence in an Open Shortest Path First (OSPF) network.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fasth elo.htm
PFE MIB
Platform: Cisco 10000 series
The PFE MIB (CISCO-ENTITY-PFE-MIB.my) contains objects to monitor the utilization, efficiency, and performance of the Packet Forwarding Engine (PFE). The monitoring is done via measurement periods of actual, 1 minute, 5 minutes, and 15 minutes.
On the Cisco 10000 series router, the PFE is the parallel express forwarding (PXF) network processor, which is part of the performance routing engine (PRE). PFE technology accelerates certain IP features in order to improve network performance.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/pfe_mib.htm
Sampled NetFlow on the Cisco 10720 Internet Router
Platform: Cisco 10720
The Sampled NetFlow feature enables you to sample one out of many IP packets that are being forwarded to an interface. Sampled packets are accounted for in the NetFlow flow cache of the router. Sampling packets substantially decreases the CPU utilization that is needed to account for NetFlow packets, by allowing the majority of the packets to be switched faster because they do not require additional NetFlow processing. For information about how to configure and use Sampled NetFlow, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/12s_ sanf.htm
The Sampled NetFlow implementation on the Cisco 10720 router includes the following additional features:
•An snf_feed_back counter in the output of the show hardware pxf cpu context command displays the number of packets that are sampled and punted to the Route Processor (RP) by Parallel Express Forwarding (PXF).
•An snf counter in the output of the show hardware pxf cpu statistics diversion command displays the number of sampled packets received by the RP from PXF.
•The ip flow ingress command has the same effect on a main Ethernet interface as it does on a subinterface. (This effect is different on the Cisco 12000 series router, for which you can use only the ip flow ingress command to enable the Sampled NetFlow feature on a subinterface. The command has no effect on a main interface.)
Note The snf_feed_back and snf counters may have different values if the PXF RP queue is congested. In this case, the snf value should be equal to or less than the snf_feed_back value because some sampled packets are dropped from the PXF RP queue. The snf value should never be greater than the snf_feed_back value.
The ip route-cache flow command is not supported on the Cisco 10720 router.SNMP Support for VPNs
Platform: Cisco 7500 series, Cisco 10000 series, Cisco 12000 series
The SNMP Support for VPNs feature enables you to send and receive Simple Network Management Protocol (SNMP) notifications using Virtual Private Networks (VPN) routing forwarding (VRF) tables.
SNMP is an application-layer protocol that provides a message format for communication between SNMP managers and agents. A VPN is a network that provides high connectivity transfers on a shared system with the same usage guidelines as a private network. A VPN can be built over IP, Frame Relay, or ATM networks.
A VRF stores per-VPN routing data. It defines the VPN membership of a customer site attached to the network access server (NAS). A VRF consists of an IP routing table, a derived Cisco Express Forwarding (CEF) table, guidelines, and routing protocol parameters that control the information that is included in the routing table.
The SNMP Support for VPNs feature provides configuration commands that allow you to associate SNMP agents and managers with specific VRFs. The specified VRF is used to send SNMP notifications (traps and informs) and responses between agents and managers. If a VRF is not specified, the default routing table for the VPN is used.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/cs23 vpn.htm
New Hardware and Software Features in Cisco IOS Release 12.0(22)S1 to Cisco IOS Release 12.0(22)S6
There are no new hardware or software features in Cisco IOS Release 12.0(22)S1 to Cisco IOS Release 12.0(22)S6.
New Hardware Features in Cisco IOS Release 12.0(22)S
This section describes new and changed features in Cisco IOS Release 12.0(22)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(22)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
4-Port OC-3 ATM Line Card
Platform: Cisco 10000 series
The 4-port OC-3 ATM line card provides four 155.52-Mbps SONET/Synchronous Digital Hierarchy (SDH) connections to ATM networks. It uses a standard implementation of ATM over SONET switching to provide four trunk uplinks for the Cisco 10000 series edge services router.
Note This feature has been ported from Cisco IOS Release 12.0ST.
6-Port OC-3/POS Line Card
Platform: Cisco 10000 series
The 6-port OC-3/POS line card allows Internet access and provider-to-provider peering through Cisco 10000 equipment via unchannelized OC-3 interfaces. To meet global requirements, the card supports both SONET (STS3c) and Synchronous Digital Hierarchy (SDH) (STM1c) framing and signaling.
Note This feature has been ported from Cisco IOS Release 12.0ST.
8-Port OC-3/STM-1 ATM Line Card for Cisco 12000 Series Internet Routers
Platform: Cisco 12000 series routers
The 8-port OC-3/STM-1 ATM line card supports traffic shaping, and delivers line rate OC-3/STM-1 bandwidth while traffic shaping and per-virtual circuit (VC) queueing are performed. It also supports per-VC class-based weighted fair queueing (CBWFQ) and per-VC low latency queueing (LLQ).
The 8-port OC-3/STM-1 ATM line card can be configured with 64 Segmentation and Reassembly (SAR) Weighted Random Early Detection/Drop (WRED) packs per interface, for a total of 512 SAR WRED packs. Any or all of these packs can be reconfigured by the Cisco IOS software. CBWFQ is implemented on a per-VC basis, with up to eight queues per VC. You can choose to select LLQ mode by enabling the Modified Deficit Round Robin (MDRR) feature. Both per-VC WRED and per-VC CBWFQ are performed on the SAR.
The 8-port OC-3/STM-1 ATM line card provides the Cisco 12000 series product line with eight 155 Mbps ATM interfaces. The card communicates with the Cisco 12000 series product line switch fabric.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/8_oc 3_lc.htm
8-Port Unchannelized E3/T3 Line Card
Supported platform: Cisco 10000 series routers
The 8-port unchannelized E3/T3 line card is an advanced E3 and T3 interface module for the Cisco 10000 series edge services router (ESR). It supports eight physical BNC connections, which can be configured for E3 or T3. Each E3 or T3 connection can either support a full clear-channel or be subrated by limiting the data transfer rate, and thereby reducing the peak access rate.
Subrate modes configure each interface of the 8-port unchannelized E3/T3 line card to connect with Cisco port adapters and with customer premises data service units (DSUs). The 8-port unchannelized E3/T3 line card supports maximum flexibility in that it can be used in any Cisco 10000 series ESR chassis (with no slot dependency) and can be hot-swapped. It is fully manageable by means of standard Cisco management tools, and it supports all IP networking protocols. In addition, it supports the following encapsulation protocols:
•PPP
•Frame Relay
•Cisco High-Level Data Link Control (HDLC)
•Multiprotocol Label Switching (MPLS)
Note This feature has been ported from Cisco IOS Release 12.0ST.
10 Gbps POS Enhanced Services Line Cards
Platform: Cisco 12000 series
The 1-port OC-192 POS Enhanced Services (ES, also referred to as Engine 4 plus) and Quad OC-48 POS ES line cards for Cisco 12400 Internet routers support an extensive list of features that enable service providers to provide customers with the means to build scalable, feature-rich 10G networks that support value-added services, such as MPLS Virtual Private Network (VPN), voice, and tiered service offerings, without compromising performance.
Cisco IOS Release 12.0(22)S supports all the features in Release 12.0(21)S (see the note below) along with the following additional features:
•MPLS VPN features (see the "MPLS VPN and Fast Reroute on 10 Gbps POS Enhanced Services Line Cards" section).
•Basic MPLS VPN support.
•Inter-provider VPN (also known as Interautonomous System): allows a scalable MPLS VPN service to span different service providers.
•Carrier supporting Carrier (CsC): allows carriers to use MPLS VPN to offer transport services to other service providers.
•Fast Reroute (see the "MPLS VPN and Fast Reroute on 10 Gbps POS Enhanced Services Line Cards" section).
•High availability.
Note Cisco IOS Release 12.0(21)S introduced the following ES line card features that are listed under the section Engine 4 POS Line Card Enhancements: access control lists (ACLs) on inbound and outbound interfaces, NetFlow sampling on inbound and outbound IP flows, and output rate shaping.
For information about how to install and configure 10 Gbps POS Enhanced Services line cards, see the Cisco documents at the following locations:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_pos/11420q48.htm
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_pos/11421192.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
Cisco 24-Port Channelized E1/T1 Line Card
Platform: Cisco 10000 series
The Cisco 24-port channelized E1/T1 line card is a full-slot line card with 24 ports that you can configure as E1/T1 interfaces. Each port on the line card provides one or more interfaces that can be configured as framed (channelized) or unframed (unchannelized) interfaces.
The following E1 features are supported on the Cisco 24-port channelized E1 line card:
•European 2.048 Mbps International Telecommunication Union (ITU) G.703 and G.704 serial interfaces
•Cyclic Redundancy Check (CRC4) and non-CRC4 framing modes
•High-Level Data Link Control (HDLC) protocol, Frame Relay protocol, and PPP encapsulations
•Nx64 Kbps channel bandwidths in channelized E1 mode (where N = 0 < N < 31) and a 2048 Kbps single channel bandwidth in unframed E1 mode
•Clock source selected on a per-port basis—internal or external line
•Programmable National Reserved bits
•High Density Bipolar 3 (HDB3) line encoding
The following T1 features are supported on the Cisco 24-port channelized T1 line card:
•North American 1.554 Mbps serial interfaces
•Extended Superframe (ESF) and Superframe (SF) framing modes
•High-Level Data Link Control (HDLC) protocol, Frame Relay protocol, and PPP encapsulations
•Nx64 Kbps channel bandwidths in channelized T1 mode (where N = 0 < N < 24)
•Clock source selected on a per-port basis—internal or external line
•ESF-Facility Data Link (FDL) remote performance reporting
•Remote loopbacks
•Binary 8-0 substitution (B8ZS) or alternative mark inversion (AMI) line encoding
Cisco 10000 Series Edge Services Router
The Cisco 10000 series edge services router (ESR) is a Layer 3 platform that allows service providers to provision IP services across thousands of leased-line connections. The Cisco 10000 series ESR aggregates large numbers of T3, T1, and DS0 leased lines through OC-12 Packet-over-SONET (POS) and Gigabit Ethernet interfaces. The Cisco IOS software offers a range of features that service providers can use to improve their network and customize their services.
The series consists of two chassis—an 8-slot chassis designed to meet the needs of large service providers and a 5-slot chassis designed to meet the needs of medium-to-large service providers.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Cisco 10720 Console/Auxiliary Module
Platform: Cisco 10720
The Cisco 10720 Console/Auxiliary Module provides console and auxiliary access to the Cisco 10720 Internet router from the front panel. It is installed in the upper card slot of the router chassis.
You can use the Cisco 10720 Console/Auxiliary Module with either a 24-port 10/100 Ethernet TX or a combined 4-port Gigabit Ethernet 8-port 10/100 Ethernet TX access card to customize the CIsco 10720 as an Ethernet-only router.
For information about how to install, use, and verify the operation of the Cisco 10720 Console/Auxiliary Module, see the Cisco 10720 Internet Router Uplink Card Installation and Configuration Guide at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10720/10720fru/13113upl.htm
Cisco 10720 Internet Router
The Cisco 10720 Internet router is a high performance Cisco IOS router that enables service providers to offer next generation business class IP services within metropolitan networks. Designed with support for 10/100 and later 1000 Mbps Ethernet access and high-speed OC48/STM16 dynamic packet transport (DPT) technology over fiber uplink, the Cisco 10720 Internet router allows service providers to offer IP services that are closer to the user, enabling the users to better control admission to network resources. The small form factor allows easy deployment in central locations within business complexes. Based on Cisco Parallel Express Forwarding (PXF) (Toaster-based) architecture, the Cisco 10720 Internet router is a cost-effective reliable platform that allows advanced Cisco IOS features to be introduced simply, efficiently, and without compromising on performance.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Combined 4-Port Gigabit Ethernet 8-Port 10/100 Ethernet TX Access Card
Platform: Cisco 10720
The Combined 4-Port Gigabit Ethernet 8-Port 10/100 Ethernet TX Access Card with four Gigabit Ethernet and eight Fast Ethernet ports is available on the Cisco 10720 Internet router to provide network access using either Fast Ethernet or Gigabit Ethernet connectivity.
This card supports copper cabling on Fast Ethernet ports, and fiber-optic cabling on its Gigabit Ethernet ports. The Gigabit Ethernet ports use Small Form-Factor Plugable (SFP) optical modules to provide the following optical interfaces:
•1000BASE-SX (short reach)
•1000BASE-LH (intermediate reach)
•1000BASE-ZX (long reach)
For more information about how to install and configure the Combined 4-Port Gigabit Ethernet 8-Port 10/100 Ethernet TX access card, see the Cisco 10720 Internet Router Access Card Installation and Configuration Guide at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10720/10720fru/13082acc.htm
OC-3c/STM-1c POS/SDH ISE Line Cards
Platform: Cisco 12000 series
OC-3c/STM-1c POS/SDH ISE line cards for the Cisco 12000 series Internet router provide 155 Mbps of bandwidth on each interface and include the following:
•4-port OC-3c/STM-1c POS/SDH ISE
•8-port OC-3c/STM-1c POS/SDH ISE
•16-port OC-3c/STM-1c POS/SDH ISE
OC-3/STM-1c Packet-over-SONET (POS) line cards are available in the following versions:
•Short-reach (SR), multi-mode
•Intermediate-reach (IR), multi-mode
•Long-reach (LR), multi-mode
The OC-3/STM-1c POS line card connection is concatenated, which provides for increased efficiency by eliminating the need to partition the bandwidth.
PA-MC-8TE1+ Port Adapter
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The PA-MC-8TE1+ port adapter is a multichannel port adapter that provides eight DSX-1/DS1 or eight G.703 interfaces. The PA-MC-8TE1+ interfaces can be channelized, fractional, ISDN PRI, or nonframed.
The PA-MC-8TE1+ port adapter supports Facility Data Link (FDL) in Extended Superframe (ESF) framing on T1 networks, as well as network and payload loopbacks. Bit error rate testing (BERT) is supported on each of the T1 or E1 links and can run on all of the eight ports at the same time.
The PA-MC-8TE1+ port adapter does not support the aggregation of multiple T1s or E1s (called inverse muxing or bonding) for higher bandwidth data rates. The multichannel PA-MC-8TE1+ port adapter supports Cisco High-Level Data Link Control (HDLC), Frame Relay, PPP, and Switched Multimegabit Data Service (SMDS) Data Exchange Interface (DXI) encapsulations over each T1 or E1 link. For SMDS only, DXI is sent on the T1 or E1 line, so it needs to connect to an SMDS switch that has direct DXI input.
For more information, see the Cisco documents at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/7200vx/portadpt/multicha/8port_t1/index.htm
RSP16
Platform: Cisco 7500/RSP series
The Route Switch Processor 16 (RSP16) is the latest-generation, main system processor module for the Cisco 7500 series routers. The RSP16 is not available as an upgrade to an existing RSP, but supports VIP2, VIP4, and the new VIP6-80. The RSP16 contains the CPU and most of the memory components for the router.
For more information, see the Route Switch Processor (RSP16) Installation and Configuration Guide at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7505/rte_swit/13963r16.htm
SONET APS 1+1 for 4-Port OC-3 ATM and 1-Port OC-12 ATM Line Cards
Platform: Cisco 10000 series
In Cisco IOS Release 12.0(22)S, the Cisco 10000 series edge services router (ESR) supports SONET Automatic Protection Switching (APS) 1+1 redundancy for the 4-port OC-3 ATM and 1-port OC-12 ATM line cards. APS 1+1 support is card-to-card. When the active line card fails, the redundant line card takes over. For line cards with multiple ports (such as the 4-port OC-3 ATM line card), you can also use APS 1+1 support to switch from one port to another port as long as the redundant port is on a different line card.
The Cisco 10000 series ESR supports SONET APS operation that is:
•Linear—Connections are made back-to-back (as opposed to connections that are made via a ring topology).
•Unidirectional—Transmit and receive channels are switched independently.
•Nonreverting—Nonreverting channels continue to operate after a failure has been corrected, thus preventing data from flowing back to the working channel.
Note APS 1:1 redundancy is not supported in Cisco IOS Release 12.0(22)S.
For information about configuring APS on a Cisco 10000 series ESR, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10ksw/apsos.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
VIP6
Platform: Cisco 7500/RSP series
The Cisco Versatile Interface Processor 6-80 Services Accelerator (VIP6-80) is the newest and highest-performance versatile interface processor for the Cisco 7500 series routers. The VIP6-80 is not currently available as an upgrade to an existing VIP.
The VIP6-80 has a main processor and memory. When distributed switching is enabled on the router, the VIP6-80 can make packet switching decisions to help reduce the load on the Route Switch Processor (RSP). Interfaces located on port adapters that fit into the VIP6-80 connect the router to the external network. Either one dual-width or two single-width port adapters can be used on the VIP6-80.
The VIP6-80 supports Online Insertion and Removal (OIR). VIP6-80 port adapters do not support OIR, so you must first remove the VIP6-80 before removing or installing the port adapters.
For more information, see the Versatile Interface Processor (VIP6-80) Installation and Configuration Guide at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7505/vip1/14372v68.htm
New Software Features in Cisco IOS Release 12.0(22)S
This section describes new and changed features in Cisco IOS Release 12.0(22)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(22)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
3-Port Gigabit Ethernet Line Card MPLS-VPN Features
Platform: Cisco 12000 series
The following MPLS-VPN features are supported on the 3-port Gigabit Ethernet line card for the Cisco 12000 series Internet routers:
•MPLS-VPN support
•VLAN to MPLS VPN mapping
•Explicit Null
•VLAN "P" bits mapping to IP ToS/MPLS COS bits
Note This feature has been ported from Cisco IOS Release 12.0ST.
802.1p Support on the Cisco 10720 Internet Router
Platform: Cisco 10720
The IEEE 802.1p standard provides a means for individual end stations to request a particular quality of service (QoS) of the network and for the network to respond accordingly. 3-bits in the 802.1Q header with values ranging from 0 to 8 can be used to set different priority levels of user traffic at Layer 2. In the context of the Cisco 10720 router, the Modular QoS feature is used to set the 802.1p bits, similar to setting the IP type of service (ToS) bits. The switches that are deployed behind the Cisco 10720 router that supports this feature can take advantage of the priority bits for providing a higher quality of service for certain types of traffic.
Note This feature has been ported from Cisco IOS Release 12.0ST.
802.1q Support for the Cisco 10720 Internet Router
Platform: Cisco 10720
The term "VLAN" refers to the ability to virtually create a LAN using a switched architecture. Rather than being defined on a physical or geographical basis, VLANs can be defined on a logical or organizational basis in which the network can be configured via software. The IEEE standard 802.1q defines the operation of VLAN bridges that permit the definition, operation, and administration of VLAN topologies within a bridged LAN infrastructure. This standard is based on a frame-tagging mechanism to identify the specific VLAN.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Any Transport over MPLS: ATM AAL5 over MPLS
Platform: Cisco 12000 series
The Any Transport over MPLS: ATM AAL5 over MPLS feature, part of the Any Transport over MPLS (AToM) product set, provides an ATM permanent virtual circuit (PVC) for transporting ATM adaptation layer 5 (AAL5) protocol data units (PDUs) across an IP/Multiprotocol Label Switching (MPLS) backbone with rate-limit policing and configurable PVC priority values. A dynamic MPLS tunnel is configured to enable label imposition and disposition of encapsulated ATM PDUs transported between two edge routers having a Label Distribution Protocol (LDP) neighbor relationship.
Each routed PVC label stack has two levels of labels prepended to each ATM PDU: an Interior Gateway Protocol (IGP) stack consisting of zero or more labels and a PVC-based label. Label imposition and disposition are performed by routers at the edge of the MPLS backbone. The imposition router takes the ATM PDU and encapsulates it in an MPLS PDU for transport to the correct disposition router. The disposition router takes the MPLS PDU, de-encapsulates the ATM PDU, and delivers it to the correct ATM interface and virtual path identifier/virtual circuit identifier (VPI/VCI).
In Cisco 12000 series Internet routers, AAL5 over MPLS label disposition is supported on the following engines and line cards:
•Engine 0:
–4-port OC-3c/STM-1c POS/SDH line cards
–1-port OC-12c/STM-4c POS/SDH line cards
•Engine 2:
–3-port Gigabit Ethernet line cards
–8-port OC3c/STM-1c POS/SDH line cards
–16-port OC3c/STM-1c POS/SDH line cards
–4-port OC12c/STM-4c POS/SDH line cards
–1-port OC48c/STM-16c POS/SDH line cards
–1-port OC-48c/STM-16c DPT line cards
In Cisco 12000 series Internet routers, AAL5 over MPLS label imposition and disposition are supported on the following engines and line cards:
•Engine 0:
–4-port OC-3c/STM-1c ATM line cards
–1-port OC-12c/STM-4c ATM line cards
–4-port OC-12c/STM-4c ATM line cards
For further information, see the Cisco document MPLS AToM—ATM AAL5 over MPLS at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/fsa al5.htm
Note In Cisco IOS Release 12.0(22)S, line card support on Cisco 12000 series Internet routers for the Any Transport over MPLS: ATM AAL5 over MPLS feature is based on the existing control plane. In future Cisco IOS releases, a revised control plane for AToM will be implemented.
Note This feature has been ported from Cisco IOS Release 12.0ST. Any Transport over MPLS used to be referred to as MPLS AToM.
Any Transport over MPLS: Ethernet over MPLS
The following features appear under this feature heading:
• Any Transport over MPLS: Ethernet over MPLS in Cisco 10720 Internet Routers
• Any Transport over MPLS: Ethernet over MPLS in Cisco 12000 Series Internet Routers
Any Transport over MPLS: Ethernet over MPLS in Cisco 10720 Internet Routers
Platform: Cisco 10720
The Any Transport over MPLS: Ethernet over MPLS feature, part of the Any Transport over Multiprotocol Label Switching (AToM) product set, is now supported on the Cisco 10720 Internet routers. This feature allows you to connect two VLAN networks that are in different locations, without using expensive bridges, routers, or switches at the VLAN locations. You enable the MPLS backbone network to accept Layer 2 VLAN traffic by configuring the label edge routers (LERs) at both ends of the MPLS backbone.
The Cisco 10720 Internet router also supports the VLAN ID Rewrite feature for Ethernet over MPLS (EoMPLS) connections. The egress side of an EoMPLS connection that is mapped to a VLAN rewrites the VLAN ID in outgoing packets to the ID of the local VLAN. This feature allows you to use VLAN interfaces with different VLAN IDs at either end of the MPLS backbone.
For more information, see the MPLS AToM—Ethernet over MPLS document for the Cisco 10720 Internet router at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/12s1 0k.htm
Any Transport over MPLS: Ethernet over MPLS in Cisco 12000 Series Internet Routers
Platform: Cisco 12000 series
The Any Transport over MPLS: Ethernet over MPLS feature, part of the Any Transport over Multiprotocol Label Switching (AToM) product set, allows you to connect two VLAN networks that are in different locations, without using expensive bridges, routers, or switches at the VLAN locations. You can enable the MPLS backbone network to accept Layer 2 VLAN traffic by configuring the label edge routers (LERs) at both ends of the MPLS backbone.
In Cisco 12000 series Internet routers, Ethernet over MPLS label imposition is supported on the following engines and line cards:
•Engine 2:
–3-port Gigabit Ethernet line cards
In Cisco 12000 series Internet routers, Ethernet over MPLS label disposition is supported on the following engines and line cards:
•Engine 2:
–3-port Gigabit Ethernet line cards
–8-port OC3c/STM-1c POS/SDH line cards
–16-port OC3c/STM-1c POS/SDH line cards
–4-port OC12c/STM-4c POS/SDH line cards
–1-port OC48c/STM-16c POS/SDH line cards
•Engine 4+:
–4-port OC-48c/STM-16c POS line cards
–1-port OC-192c/STM-64c POS/SDH line cards
For further information, see the Cisco document MPLS AToM—Ethernet over MPLS at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/eom pls20.htm
Note This feature has been ported from Cisco IOS Release 12.0ST. Any Transport over MPLS used to be referred to as MPLS AToM.
ARP Optimization
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Address Resolution Protocol (ARP) is used to map a Layer 3 IP address to a Layer 2 MAC address. A Cisco router stores this mapped information in an ARP table. The ARP table provides MAC rewrite information when the router is forwarding a packet using Cisco Express Forwarding (CEF) or other IP switching technologies.
In previous versions of Cisco IOS, the ARP table was organized for easy searching on an entry based on the IP address. However, there are cases such as interface flapping on the router and a topology change in the network in which all related ARP entries need to be refreshed for correct forwarding. This situation could consume a significant amount of CPU time in the ARP process to search and clean up all the entries. The ARP Optimization feature improves ARP performance by reducing the ARP searching time by using an improved data structure.
The ARP Optimization feature introduces one new command: clear arp interface. This command clears the entire ARP cache on an interface.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/arpo ptim.htm
ATM PVCs
Platform: Cisco 10000 series
The Cisco 10000 series edge services router (ESR) now supports 4000 ATM permanent virtual circuits (PVCs).
Note This feature has been ported from Cisco IOS Release 12.0ST.
AutoInstall in Cisco 10720 Internet Routers
Platform: Cisco 10720
The AutoInstall feature allows you to configure a new Cisco 10720 Internet router automatically and dynamically. The AutoInstall procedure involves connecting a new router to a network in which an existing router is preconfigured, turning on the new router, and enabling it with a configuration file that is automatically downloaded from a TFTP server, reachable through the dynamic packet transport (DPT) /Spatial Reuse Protocol (SRP) uplink interface on the Cisco 10720 Internet router. If no startup configuration has already been saved in the router, the AutoInstall procedure is invoked when the router starts.
For more detailed information about the AutoInstall feature, see the Using Configuration Tools document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/fun_c/fcprt1/fccfgtoo.htm
Automatic Protection Switching on 2-Port Channelized OC-3/STM-1 (DS1/E1) Line Cards
Platform: Cisco 12000 series
The Automatic Protection Switching (APS) feature is supported on 2-port channelized OC-3/STM-1 (DS1/E1) line cards in Cisco 12000 series Internet routers. This feature allows switchover of Packet-over-SONET (POS) circuits in the event of circuit failure and is often required when connecting SONET equipment to telco equipment. APS refers to the mechanism of using a "protect" POS interface in the SONET network as the backup for the "working" POS interface. When the working interface fails, the protect interface quickly assumes its traffic load.
The protection mechanism used for this feature has "1+1, architecture" as described in the Bellcore publication TR-TSY-000253, SONET Transport Systems; Common Generic Criteria, Section 5.3. The connection may be bidirectional or unidirectional, and revertive or nonrevertive.
For more information about automatic protection switching of POS circuits, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios112/ios112p/gsr/posapsgs.htm
Auto-Shutdown Feature Changes
Platform: Cisco 10000 series
In Cisco IOS Release 12.0(22)S, the following changes have been made to the Auto-Shutdown feature for the Cisco 10000 series edge services routers (ESR):
•Fan events no longer cause an auto-shutdown of the ESR. This behavior differs from the behavior noted on the fan tray labels.
•By default, the ESR no longer shuts down automatically when a critical temperature threshold is exceeded. Now, you must enable auto-shutdown by issuing the facility-alarm command with critical exceed-action shutdown keyword. Then, if the core temperature exceeds its critical threshold (85°C) for 2 minutes, or the intake temperature exceeds its critical threshold (67°C) for 2 minutes, the ESR shuts down automatically.
BGP Conditional Route Injection
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
Cisco IOS software provides several methods in which you can originate a prefix into the Border Gateway Protocol (BGP). The existing methods include using the network or aggregate-address commands and redistribution. These methods assume the existence of more specific routing information (matching the route to be originated) in either the routing table or the BGP table.
The BGP Conditional Route Injection feature enables you to originate a prefix into BGP without the corresponding match. The routes are injected into the BGP table only if certain conditions are met. The most common condition is the existence of a less-specific prefix.
For more information about the BGP Conditional Route Injection feature, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/s_bg pcri.htm
Note This feature has been ported from Cisco IOS Release 12.0ST. Support for the Cisco 10000 series has been added in Cisco IOS Release 12.0(22)S.
BGP Convergence Optimization
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
BGP Convergence Optimization introduces a new algorithm for update generation that reduces the amount of time that is required for Border Gateway Protocol (BGP) convergence. Neighbor update messages are optimized before they are forwarded to neighbors. Updates are optimized and forwarded based on peer groups and per-individual neighbors. This enhancement improves BGP convergence, router boot time, and transient memory usage. This enhancement is not user configurable.
BGP Hybrid CLI
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The BGP Hybrid CLI feature simplifies the migration of Border Gateway Protocol (BGP) networks and existing configurations from the Network Layer Reachability Information (NLRI) format to the address-family identifier (AFI) format. This new functionality allows the network operator to configure commands in the AFI format and save these command configurations to existing NLRI formatted configurations. The feature provides the network operator with the capability to take advantage of new features and provides support for migration from the NLRI format to the AFI format. The BGP Hybrid CLI feature is present in Cisco IOS Release 12.0(22)S and later software releases and does not require the network operator to perform any specific configuration tasks.
The BGP Hybrid CLI feature does not add support for complete AFI and NLRI integration because of the limitations of the NLRI format. For complete support of AFI commands and features, the network operator must upgrade existing NLRI configurations with the bgp upgrade-cli command, which is used to convert existing NLRI configurations to the AFI format. For information about how to use the bgp upgrade-cli command to perform this upgrade and for more information about the BGP Hybrid CLI feature, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/sbgp hcli.htm
BGP Increased Support of Numbered AS-Path Access Lists to 500
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The BGP Increased Support of Numbered AS-Path Access Lists to 500 feature is an enhancement for Border Gateway Protocol (BGP) autonomous system access lists. This enhancement increases the maximum number autonomous system access lists from 199 to 500. For more information, see the Cisco document at the following location:
http:/www.cisco.com/univercd/cc/td/doc/product/software/ios122sb/newft/122sbc27/ftiaaspa.htm
BGP Next Hop Propagation
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The BGP Next Hop Propagation feature allows you to set Border Gateway Protocol (BGP) attributes for a BGP route reflector and the ability to turn off the next hop calculation for eBGP peers.
For more information about the BGP Next Hop Propagation feature, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/s_bgpnhp.htm
Note This feature has been ported from Cisco IOS Release 12.0ST. Support for the Cisco 10000 series has been added in Cisco IOS Release 12.0(22)S.
BGP Policy Accounting
The following features are included under this feature heading:
• BGP Policy Accounting on 3-Port Gigabit Ethernet Line Cards per VLAN Support
• BGP Policy Accounting on Engine 4 Plus Line Cards
• BGP Policy Accounting Support on the Cisco 10000 Platform
• BGP Policy Accounting Output Interface Accounting
BGP Policy Accounting on 3-Port Gigabit Ethernet Line Cards per VLAN Support
Platform: Cisco 12000 series
Cisco IOS Release 12.0(22)S now supports Border Gateway Protocol (BGP) policy accounting on 3-port Gigabit Ethernet line cards per VLAN.
Note This feature has been ported from Cisco IOS Release 12.0ST.
BGP Policy Accounting on Engine 4 Plus Line Cards
Platform: Cisco 12000 series
The Border Gateway Protocol (BGP) Policy Accounting feature is supported on Cisco 12000 series Engine 4 Plus line cards, including:
•4-port OC-48c/STM-16c POS/SDH
•1-port OC-192c/STM-64c POS/SDH
The BGP Policy Accounting feature on allows you to account for IP traffic differentially by assigning counters based on community-list, autonomous system (AS) number, and AS-Path on a per the input interface basis. For the policy accounting feature to work, you must enable BGP and Cisco Express Forwarding/distributed Cisco Express Forwarding (CEF/dCEF) on the router.
Using BGP policy accounting, you can account for traffic (and apply billing) according to the route it traverses. For example, you can account for traffic that is routed domestic, international, terrestrial, or satellite. In this way, you can identify and account for all traffic on a per-customer basis.
For more information on the BGP policy accounting feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s9/s_bgp pa.htm
BGP Policy Accounting Support on the Cisco 10000 Platform
Platform: Cisco 10000 series
Cisco IOS Release 12.0(22)S adds support for BGP Policy Accounting on the Cisco 10000 series ESR. The BGP Policy Accounting feature uses indexes to classify traffic by the route it travels (Trans-Pacific, Trans-Atlantic, satellite, domestic, and provider network).
Note The Cisco 10000 series ESR supports up to eight indexes for classifying BGP Policy Accounting traffic.
For instructions on enabling this feature, see the Cisco document at the following location:
http://www.cisco.com/warp/public/459/38.html
BGP Policy Accounting Output Interface Accounting
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
Border Gateway Protocol (BGP) policy accounting measures and classifies IP traffic that is sent to, or received from, different peers. Policy accounting was previously available on an input interface only. The BGP Policy Accounting Output Interface Accounting feature introduces several extensions to enable BGP policy accounting on an output interface, and to include accounting based on a source address for both input and output traffic on an interface. Counters based on parameters such as community list, autonomous system number, or autonomous system path are assigned to identify the IP traffic.
For more information about the BGP Policy Accounting Output Interface Accounting feature, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/s_bg ppax.htm.
BGP Prefix-Based Outbound Route Filtering
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The BGP Prefix-Based Outbound Route Filtering feature uses Border Gateway Protocol (BGP) outbound route filter (ORF) send and receive capabilities to minimize the number of BGP updates that are sent between peer routers. Configuration of this feature can help reduce the amount of resources required for generating and processing routing updates by filtering out unwanted routing updates at the source. For example, this feature can be used to reduce the amount of processing required on a router that is not accepting full routes from a service provider network.
The BGP Prefix-Based Outbound Route Filtering feature is enabled through the advertisement of ORF capabilities to peer routers. This capability indicates that a BGP-speaking router will accept a prefix list from a neighbor and apply the prefix list to locally configured ORFs (if any exist). When this capability is enabled, the BGP-speaking router can install the inbound prefix list filter to the remote peer as an outbound filter, which reduces the number of unwanted routing updates.
The BGP Prefix-Based Outbound Route Filtering feature can be configured with send, receive, or send and receive ORF capabilities. The local peer advertises the ORF capability in send mode. The remote peer receives the ORF capability in receive mode and applies the filter as outbound policy. The local and remote peers exchange updates to maintain the ORF for each router. Updates are exchanged between peer routers by address family depending on the ORF prefix list capability that is advertised. The remote peer starts sending updates to the local peer after a route refresh request or an ORF prefix list with immediate status has been received. The BGP-speaking router will continue to apply the inbound prefix list to received updates after the speaker pushes the inbound prefix list to the remote peer.
For more information about the BGP Prefix-Based Outbound Route Filtering feature, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/s_bpborf.htm
BGP Restart Session After Max-Prefix Limit
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The BGP Restart Session After Max-Prefix Limit feature enhances the capabilities of the neighbor maximum-prefix command with the introduction of the restart keyword. This enhancement allows the network operator to configure the time interval at which a peering session is reestablished by a router when the number of prefixes that have been received from a peer has exceeded the maximum prefix limit. The restart keyword has a configurable timer argument that is specified in minutes. The time range of the timer argument is from 1 to 65535.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sb/newft/122sbc27/ftbrsamp.htm
BGP Route-Map Policy List Support
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The BGP Route-Map Policy List Support feature introduces new functionality to Border Gateway Protocol (BGP) route maps. This feature adds the capability for a network operator to group route-map match clauses into a named list called a policy list. A policy list functions like a macro within a route map. When the policy list is referenced within a route map with the match policy-list command, all match statements in the policy list are executed. Policy lists can be used for all applications of a route map and for redistribution between routing protocols. Policy lists can coexist with configured match and set clauses within the same subblock. Policy lists, however, do not support set statements, and policy lists are not supported by IP routing policy.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sb/newft/122sbc27/ftbgprpl.htm
Bidirectional PIM
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The Bidirectional PIM feature is a variant of the Protocol Independent Multicast (PIM) suite of routing protocols for IP Multicast. In PIM, packet traffic for a multicast group is routed according to the rules of the mode that is configured for that multicast group.
The Cisco IOS implementation of PIM supports the following three modes for a multicast group:
•Bidirectional mode
•Dense mode
•Sparse mode
A router can simultaneously support all three modes or any combination of them for different multicast groups. In bidirectional mode, traffic is routed only along a bidirectional shared tree that is rooted at the rendezvous point (RP) for the group. In Bidirectional PIM (bidir-PIM), the IP address of the RP acts as the key to having all routers establish a loop-free spanning tree topology rooted in that IP address. This IP address does not need to be a router, but it can be any unassigned IP address on a network that is reachable throughout the PIM domain. Using this technique is the preferred configuration for establishing a redundant RP configuration for bidir-PIM.
Membership to a bidirectional group is signaled via explicit "Join" messages. Traffic from sources is unconditionally sent up the shared tree toward the RP and passed down the tree toward the receivers on each branch of the tree.
Bidir-PIM is designed to be used for many-to-many applications within individual PIM domains. Multicast groups in bidirectional mode can scale to an arbitrary number of sources without incurring overhead due to the number of sources.
Bidir-PIM is derived from the mechanisms of PIM sparse mode (PIM-SM) and shares many shortest path tree (SPT) operations. Bidir-PIM also has unconditional forwarding of source traffic toward the RP upstream on the shared tree, but it has no registering process for sources as in PIM-SM. These modifications are necessary and sufficient to allow forwarding of traffic in all routers solely on the basis of multicast routing entries (*, G). This feature eliminates any source-specific state and allows scaling capability to an arbitrary number of sources.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Cisco 10000 ESR MIB Enhancements
Platform: Cisco 10000 series
MIB enhancements in Cisco IOS Release 12.0(22)S provide enhanced management features that enable the Cisco 10000 series edge services routers (ESR) to be managed through the Simple Network Management Protocol (SNMP). These enhanced management features allow you to do the following:
•Use SNMP set and get requests to access information in ESR MIBs.
•Reduce the amount of time and system resources required to perform functions like inventory management and bulk data transfers.
Other benefits include:
•A standards-based technology (SNMP) for monitoring faults and performance on the ESR.
•Support for all SNMP versions (SNMPv1, SNMPv2c, and SNMPv3).
•Notification of faults, alarms, and conditions that can affect services.
•The ability to aggregate fault and alarm information for multiple entities.
For more information, see the Cisco 10000 Series ESR MIB Specifications Guide at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kmibs/llver2/index.htm
Cisco 12000 Series Field Diagnostics
Platform: Cisco 12000 series
Field diagnostics are available for the Cisco 12000 series Internet router to help you isolate faulty hardware to the level of a field-replaceable unit (FRU) without disrupting the operation of the system. After you identify the faulty unit, you can replace it with a spare unit.
Field diagnostics are not designed to identify specific components within the router. They simply determine whether a particular card is operational or defective.
Starting with Cisco IOS Release 12.0(22)S, Cisco Systems has unbundled the Cisco 12000 series field diagnostics line card software image from the Cisco IOS software image. In earlier Cisco IOS releases, diagnostics could be launched from the command line and the imbedded image would be launched. In order to accommodate customers with 20-MB Flash memory cards, field diagnostics are now stored and maintained as a separate image that must be available on a Flash memory card or a TFTP boot server before the field diagnostics commands can be used.
Note Before you can use the line card field diagnostics commands, you must install a valid field diagnostics software image in the Cisco 12000 series Internet router that is to be tested or on a TFTP boot server. The size of a field diagnostics software image is about 18 MB, and a Cisco IOS software image for the Cisco 12000 series Internet router is slightly larger. A single 64-MB Flash memory card can contain both images. Alternately, these images can be stored individually on 20-MB Flash memory cards in PCMCIA slots 0 and 1. To accommodate future Cisco IOS releases, we recommend that you use Flash memory cards that are larger than 20 MB.
Note Field diagnostics software images are compatible backwards and forwards with all releases of Cisco IOS Release 12.0S from Cisco IOS Release 12.0(22)S on. Cisco strongly recommends that you always download the latest available field diagnostics software image from Cisco.com. The field diagnostics software image is named "c12k-fdiagsbflc-mz.versionnumber."
To perform field diagnostics on a line card, Route Processor card (RP), including both the Performance Route Processor (PRP) and Gigabit Route Processor (GRP), Switch Fabric Card (SFC), or Clock Scheduler Card (CSC) in Cisco 12000 series Internet routers, use the diag command in privileged EXEC configuration mode. To halt a running field diagnostic session on a line card or RP, use the diag halt form of this command.
For more information about Cisco 12000 Series Field Diagnostics, see the document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/diag .htm
CISCO-APS-MIB
Platform: Cisco 12000 series
The Cisco SONET Linear Automatic Protection Switching (APS) MIB module supports the configuration and management of SONET linear APS groups. The definitions and descriptions that are used in this MIB are derived from SONET Transport Systems: Common Generic Criteria, GR-253-CORE Revision 2, section 5.3. The MIB is also consistent with the Multiplex Section Protection (MSP) protocol as specified in ITU-T Recommendation G.783, Characteristics of synchronous digital hierarchy (SDH) equipment function blocks, Annex A and B. This MIB was extracted from internet draft "draft-ietf-atommib-sonetaps-mib-05.txt" for SONET Linear APS architectures.
No new or modified Cisco IOS commands are associated with this MIB. For details on managed objects within the Cisco SONET Linear APS MIB, see the CISCO-APS-MIB.my MIB file.
http://tools.cisco.com/ITDIT/MIBS/servlet/index
CISCO-ENHANCED-WRED-MIB
Platform: Cisco 12000 series
Cisco Weighted Random Early Detection/Drop (WRED) is a method that avoids traffic congestion on an output interface. Congestion is detected by computing the average output queue size against queue thresholds, which can be configured either per IP precedence or are differentiated services code point (DSCP) based. WRED support are on IP fast switching and IP flow switching only. It does not apply to IP process switching.
The Cisco Enhanced WRED MIB (CISCO-ENHANCED-WRED-MIB) provides WRED packet configuration and packet filtering information. This MIB provides the WRED information about the transmit (Tx) side and receive (Rx) side of the modules, for the managed systems that support WRED on both the transmit side and the receive side.
No new or modified Cisco IOS commands are associated with this MIB. For additional details, see the CISCO-ENHANCED-WRED-MIB.my MIB file.
http://tools.cisco.com/ITDIT/MIBS/servlet/index
Cisco Nonstop Forwarding with Stateful Switchover
The following features appear under this feature heading:
• SNMP for Stateful Switchover
Note The Cisco Stateful Switchover with Nonstop Forwarding (SSO/NSF) feature is targeted to be supported on the Performance Route Processor (PRP) in Cisco IOS Release 12.0(23)S and later releases. However, in Cisco IOS Release 12.0(22)S, the PRP is NSF aware, meaning that it runs NSF software and can maintain session information with a peer device following a switchover of the peer device.
Cisco Nonstop Forwarding
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
Cisco Nonstop Forwarding (NSF) is a complementary feature to the Stateful Switchover (SSO) feature in Cisco IOS software. NSF always runs together with SSO and works with SSO to minimize the amount of time a network is unavailable to its users following a switchover. The main objective of NSF is to continue forwarding IP packets following a Route Processor (RP) switchover.
Usually, when a networking device restarts, all routing peers of that device detect that the device went down and then came back up. This transition results in what is called a routing flap, which could spread across multiple routing domains. Routing flaps caused by routing restarts create routing instabilities, which are detrimental to the overall network performance. NSF helps to suppress routing flaps in SSO-enabled devices, thus reducing network instability.
NSF allows for the forwarding of data packets to continue along known routes while the routing protocol information is being restored following a switchover. With NSF, peer networking devices do not experience routing flaps. Data traffic is forwarded through intelligent line cards or dual forwarding processors (FPs) while the Standby RP assumes control from the failed active RP during a switchover. The ability of line cards and FPs to remain up through a switchover and to be kept current with the Forwarding Information Base (FIB) on the Active RP is key to NSF operation.
Note The Cisco 7200 series router and the Cisco 10720 Internet router are single processor devices that will not switchover in the event of a fault; however, they are NSF aware, meaning that they run NSF software and can maintain session information with a peer device (a Cisco 7500, 10000, or 12000 series router) following a switchover of the peer device.
For information about the SSO feature, see the "Stateful Switchover" section.
For more information about Cisco NSF, see the Cisco Nonstop Forwarding document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/nsf1 20s.htm
Stateful Switchover
Platforms: Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
Note Development of the Stateful Switchover (SSO) feature is an incremental step within an overall program to improve the availability of networks constructed with Cisco IOS routers.
SSO is particularly useful at the network edge. Traditionally, core routers protect against network faults using router redundancy and mesh connections that allow traffic to bypass failed network elements. SSO provides protection for network edge devices with dual Route Processors (RPs) that represent a single point of failure in the network design, and at which point an outage might result in loss of service for customers.
In specific Cisco networking devices that support dual RPs, SSO takes advantage of RP redundancy to increase network availability. The SSO feature takes advantage of RP redundancy by establishing one of the RPs as the active processor while the other RP is designated as the standby processor, and then synchronizing critical state information between them. Following an initial synchronization between the two processors, SSO dynamically maintains RP state information between them.
A switchover from the active to the standby processor occurs when the active RP fails, is removed from the networking device, or is manually taken down for maintenance.
SSO is used with the Cisco Nonstop Forwarding (NSF) feature. Cisco NSF allows for the forwarding of data packets to continue along known routes while the routing protocol information is being restored following a switchover. With Cisco NSF, peer networking devices do not experience routing flaps, thereby reducing loss of service outages for end customers.
For Cisco NSF protocols that require neighboring devices to participate in Cisco NSF, Cisco NSF-aware software images must be installed on those neighboring distribution layer devices. Additional network availability benefits might be achieved by applying Cisco NSF and SSO features at the core layer of your network; however, talk with your network design engineers to evaluate your specific site requirements.
Note The Cisco 7200 series router and the Cisco 10720 Internet router are single processor devices that do not support SSO.
For information about the Cisco NSF feature, see the "Cisco Nonstop Forwarding" section.
For more information about the SSO feature, see the Stateful Switchover document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/sso1 20s.htm
SNMP for Stateful Switchover
Platforms: Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The SNMP for Stateful Switchover feature helps to improve the availability of networks that are made up of Cisco IOS-based networking devices. Using SSO, a networking device with redundant RPs will continue forwarding traffic, continue operating as a routing protocol peer, and remain manageable under a set of circumstances that ordinarily would cause an interruption in service.
The SSO feature allows one of the processors on the networking device to operate as the active RP, which passes the necessary system, routing, and application state information to the standby RP. Upon switchover, the standby RP quickly assumes the role of active RP. The goal of SNMP network management with SSO functionality is to provide an uninterrupted management interface to the end user during and after a switchover.
Network management support for SSO is provided through the synchronization of specific SNMP data between the active and standby RPs. From a network management perspective, this synchronization helps to provide an uninterrupted management interface to the network administrator.
Note Synchronization of SNMP data between RPs is available only when the networking device is operating in SSO mode.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/sso_ mibs.htm
CISCO-OPTICAL-MONITORING-MIB
Platform: Cisco 12000 series
The Cisco Optical Monitoring MIB module is used to monitor optical parameters of a network element. This MIB deals with the operating parameters of the optical layer. The optical layer is a term that defines all the devices or systems that deal with the conversion of data in it's electrical form to optical form, transmission and reception of optical data, and reconversion to electrical signals.
No new or modified Cisco IOS commands are associated with this MIB. For details on managed objects within the Cisco Optical Monitoring MIB, see the CISCO-OPTICAL-MONITORING-MIB.my MIB file, available from the Cisco MIB FTP site at the following location:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
CNS Configuration Agent
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
Cisco Networking Services (CNS) is a foundation technology for linking users to network services. CNS Software Developers Kit (SDK) accomplishes this linking by making applications network-aware and increasing the intelligence of the network elements. CNS SDK provides building blocks to a range of customers in market segments such as enterprise, service provider, independent software vendors, and system integrators.
The CNS Configuration Agent feature supports initial configurations, incremental configurations, and synchronized configuration updates for Cisco IOS software-based routing devices.
Initial Configurations
When a routing device first comes up, it connects to the configuration server component of CNS Configuration Agent by establishing a TCP connection through the use of the cns config initial command, a standard command-line interface (CLI) command. The device issues a request and identifies itself by providing a unique configuration ID to the configuration server.
When the CNS web server receives a request for a configuration file, it invokes the Java Servlet and executes the corresponding embedded code. The embedded code directs the CNS web server to access the directory server and file system to read the configuration reference for this device (configuration ID) and template. The Configuration Agent prepares an instantiated configuration file by substituting all the parameter values specified in the template with valid values for this device. The configuration server forwards the configuration file to the CNS web server for transmission to the routing device.
The CNS Configuration Agent feature accepts the configuration file from the CNS web server, performs extensible markup language (XML) parsing, checks syntax (optional), and loads the configuration file. The routing device reports the status of the configuration load as an event to which a network monitoring or workflow application can subscribe.
Incremental (Partial) Configurations
When the network is up and running, new services can be added using the CNS Configuration Agent. Incremental (partial) configurations can be sent to routing devices. The actual configuration can be sent as an event payload by way of the Event Gateway (push operation) or as a signal event that triggers the device to initiate a pull operation.
The routing device can check the syntax of the configuration before applying it. If the syntax is correct, the routing device applies the incremental configuration and publishes an event that signals success to the configuration server. If the device fails to apply the incremental configuration, it publishes an event that indicates an error status.
After the routing device has applied the incremental configuration, it can write it to NVRAM, or wait until signaled to do so.
Synchronized Configurations
When a routing device receives a configuration, it has the option to defer application of the configuration upon receipt of a write-signal event. The CNS Configuration Agent feature allows the device configuration to be synchronized with other dependent network activities.
For further information on enabling CNS services on your routing devices, see the CNS Configuration Agent and CNS Event Agent documents at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st18/
Note This feature has been ported from Cisco IOS Release 12.0ST.
CNS Event Agent
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
Cisco Networking Services (CNS) is a foundation technology for linking users to network services. CNS Software Developers Kit (SDK) accomplishes this linking by making applications network-aware and increasing the intelligence of the network elements. CNS SDK provides building blocks to a range of customers in market segments such as enterprise, service provider, independent software vendors, and system integrators.
The CNS Event Agent is part of the Cisco IOS software infrastructure that allows Cisco IOS software applications to publish and subscribe to events on a CNS Event Bus. CNS Event Agent works in conjunction with the CNS Configuration Agent feature.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Core and Intake Critical Temperature Thresholds
Platform: Cisco 10000 series
The Cisco 10000 series edge services routers (ESR) core and intake critical temperature threshold values have changed. When the ESR temperature exceeds one of these thresholds, the ESR generates a critical alarm and shuts down automatically if it is configured to do so. (See the "facility-alarm Command" section.
The new critical temperature thresholds (in Celsius) are as follows:
•85°C (core temperature)
•67°C (intake temperature)
Note You cannot configure critical temperature thresholds.
Diff-Serv-Aware Traffic Engineering (DS-TE)
The following features appear under this feature heading:
• Diff-Serv-Aware Traffic Engineering (DS-TE) for the Cisco 7500 Series Routers
• Diff-Serv-Aware Traffic Engineering (DS-TE) for the Cisco 12000 Series Internet Routers
Diff-Serv-Aware Traffic Engineering (DS-TE) for the Cisco 7500 Series Routers
Platform: Cisco 7500/RSP series
Extensions added to Multiprotocol Label Switching Traffic Engineering (MPLS TE) make it Diff-Serv aware. Specifically, the bandwidth reservable on each link for constraint-based routing (CBR) purposes can now be managed through two bandwidth pools: a global pool and a sub-pool. The sub-pool can be limited to a smaller portion of the link bandwidth. Tunnels using the sub-pool bandwidth can then be used in conjunction with MPLS Quality of Service (QoS) mechanisms to deliver guaranteed bandwidth services end-to-end across the network.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st14/ds_ te.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
Diff-Serv-Aware Traffic Engineering (DS-TE) for the Cisco 12000 Series Internet Routers
Platform: Cisco 12000 series
MPLS traffic engineering allows constraint-based routing of IP traffic. One of the constraints satisfied by constant bit rate (CBR) is the availability of required bandwidth over a selected path. Diff-Serv-Aware Traffic Engineering (DS-TE) extends MPLS traffic engineering to enable you to perform constraint-based routing of "guaranteed" traffic, which satisfies a more restrictive bandwidth constraint than that satisfied by CBR for regular traffic. The more restrictive bandwidth is termed a subpool, while the regular TE tunnel bandwidth is called the global pool. (The subpool is a portion of the global pool.) This ability to satisfy a more restrictive bandwidth constraint translates into an ability to achieve higher quality of service (QoS) performance (in terms of delay, jitter, or loss) for the guaranteed traffic.
For example, DS-TE can be used to ensure that traffic is routed over the network so that, on every link, there is never more than 40 per cent (or any assigned percentage) of the link capacity of guaranteed traffic (for example, voice), while there can be up to 100 per cent of the link capacity of regular traffic. Assuming QoS mechanisms are also used on every link to queue guaranteed traffic separately from regular traffic, it then becomes possible to enforce separate "overbooking" ratios for guaranteed and regular traffic. (In fact, for the guaranteed traffic it becomes possible to enforce no overbooking at all or even an underbooking so that very high QoS can be achieved end-to-end for that traffic, even while for the regular traffic a significant overbooking continues to be enforced.)
Also, through the ability to enforce a maximum percentage of guaranteed traffic on any link, the network administrator can directly control the end-to-end QoS performance parameters without having to rely on over-engineering or on expected shortest path routing behavior. This is essential for transport of applications that have very high QoS requirements (such as real-time voice, virtual IP leased line, and bandwidth trading), where over-engineering cannot be assumed everywhere in the network.
DS-TE involves extending Open Shortest Path First (OSPF) routing protocol, so that the available sub-pool bandwidth at each preemption level is advertised in addition to the available global pool bandwidth at each preemption level. And DS-TE modifies constraint-based routing to take this more complex advertised information into account during path computation.
In this release, tight guarantees can be achieved using the Cisco 12000 series Internet routers and Packet-over-SONET(POS) interface, with Engine 0 line card at the edge and Engine 2 line card at the core. End-to-end guaranteed bandwidth service is achieved by applying committed access rate (CAR) and MPLS QoS mechanisms in conjunction with DS-TE. Qos Policy Propagation via BGP (QPPB) is not supported with input CAR on the Cisco 12000 series Internet routers in this release.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st14/ds_ te.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
Diffserv Compliant WRED
Platform: Cisco 10000 series
The Diffserv Compliant WRED feature extends the functionality of Weighted Random Early Detection (WRED) to enable support for Differentiated Services (DiffServ) and Assured Forwarding (AF) Per Hop Behavior (PHB). DiffServ Compliant WRED enables customers to implement AF PHB by coloring packets according to differentiated services code point (DSCP) values and then assigning preferential drop probabilities to those packets.
Note This feature has been ported from Cisco IOS Release 12.0ST.
DPT MIB
Platform: Cisco 10720
see the following document for additional MIB information:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
Note This feature has been ported from Cisco IOS Release 12.0ST.
Explicit Null
Platform: Cisco 12000 series
With this release, Explicit Null is supported on Cisco 12000 series Internet routers Engine-2 line cards. Explicit Null labels are used where label encapsulation is needed, but no valid label is required. For example, an explicit null label might be used to retain the experimental (EXP) fields for quality of service (QoS) purposes on the last hop of an label switched path (LSP), even though no label is required by the last hop.
When the explicit null label is used, it must be the only entry in the label stack.
Note This feature has been ported from Cisco IOS Release 12.0ST.
facility-alarm Command
Platform: Cisco 10000 series
A new keyword (critical exceed-action shutdown) allows you to enable or disable the auto-shutdown feature on the Edge Services Router (ESR). Previously, auto-shutdown was enabled by default. When auto-shutdown is enabled, the ESR shuts down automatically when its core or intake temperature exceeds the critical temperature threshold for 2 minutes.
You can also use this command to set the temperature thresholds at which the Cisco 10000 ESR generates a major or minor alarm, or to disable those alarms. The command format is as follows:
Router(config)# [
no ] facility-alarm { intake-temperature | core-temperature }
{ major [##] | minor [##] | critical exceed-action shutdown }Use the no format of the command to turn off the facility-alarm action. For more information, see the "Command Examples" section.
Syntax Description
Command Examples
The following command configures the Cisco 10000 series ESR to shut down automatically when its core temperature exceeds the critical temperature threshold (85°C) for 2 minutes:
Router(config)#
facility-alarm core-temperature critical exceed-action shutdownThe following command disables the auto-shutdown feature for the core critical temperature threshold (which means the ESR does not shut down when the core critical temperature is exceeded for 2 minutes):
Router(config)#
no facility-alarm core-temperature critical exceed-action shutdownThe following command configures the ESR to generate a minor alarm when the intake temperature exceeds 55°C:
Router(config)#
facility-alarm intake-temperature minor 55The following commands disable major and minor alarms for core and intake temperature thresholds:
Router(config)#
no facility-alarm core-temperature major
Router(config)#
no facility-alarm intake-temperature minorFast Software Upgrade
Platform: Cisco 7500 series
Using the Fast Software Upgrade feature, you can reduce planned downtime. With Fast Software Upgrade (FSU), you can configure the system to switch over to a standby RSP, which is preloaded with an upgraded Cisco IOS software image. FSU reduces outage time during a software upgrade by transferring functions to the standby RSP that has the upgraded Cisco IOS software preinstalled. The only downtime with an FSU is the time required for the standby RSP to take control during the switchover. You can also use FSU to downgrade a system to an older version of Cisco IOS software or have a backup system loaded for downgrading to a previous image immediately after an upgrade.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Frame Relay Fast Restart
Platforms: Cisco 7500/RSP series, Cisco 10000 series
The Frame Relay Fast Restart feature increases network availability by reducing recovery time from Route Processor (RP) failures on Cisco routers in Frame Relay networks. This feature reduces recovery time by accelerating the transition from primary RP to standby RP after a hardware or software failure.
When a switchover from primary RP to standby RP occurs on a router that has been configured for Frame Relay encapsulation, the router must implement an initialization procedure to bring permanent virtual circuits (PVCs) back up and to reestablish dynamic mappings. While this procedure is under way, the Frame Relay interface is unavailable for traffic forwarding. Before the introduction of this feature, the initialization procedure took from 30 to 90 seconds to complete on each Frame Relay interface. The Frame Relay Fast Restart feature reduces interface restart time to 10 to 15 seconds.
The Frame Relay Fast Restart feature uses the methods described in the following sections to reduce interface restart time:
Accelerating the LMI Cycle
To address the possibility that the line protocol is down upon switchover to the standby RP, the Frame Relay Fast Restart feature introduces an accelerated Local Management Interface (LMI) cycle. The accelerated LMI cycle is designed to bring the line protocol up quickly, in turn making PVCs available sooner.
Before the introduction of Frame Relay fast restart, LMI polling cycles occurred every ten seconds, and on the sixth cycle a full LMI status request was sent. This LMI cycle resulted in the sending of a full LMI status request every 60 seconds. With the accelerated LMI cycle, a full status request is sent to the switch immediately after switchover to the standby RP. The next polling cycle begins within one second following receipt of the full status from the switch rather than waiting the default ten seconds. A full status request is also sent at the last polling cycle. The accelerated LMI cycle ends after a fixed number of polling cycles, which can be configured to meet the requirements of the switch.
The accelerated LMI cycle causes the line protocol to come up and PVCs to be reported active in one or two seconds instead of the 30 to 40 seconds that it would have taken before the introduction of this feature.
Note It may take an additional ten seconds before the remote router sees that the PVCs are up.
Note The accelerated data terminal equipment (DTE) LMI cycle is nonstandard and may cause problems for some data circuit-terminating equipment (DCE) LMI implementations. When the DTE device is directly connected to a Cisco DCE device that is terminating PVCs, the DCE device must be running a Cisco IOS software release based on 12.0(17.6)S, 12.0(22)S, 12.1(9.1), or 12.2(2.2) or later.
Accelerating Inverse ARP
Inverse Address Resolution Protocol (ARP) requests, where applicable, will be sent out as soon as a PVC becomes active. Before the introduction of the Frame Relay Fast Restart feature, when an Inverse ARP request was unsuccessful, the request was resent every 60 seconds. This new feature accelerates the Inverse ARP timer so that if a request comes back unsuccessful, a second request is sent in ten seconds. Subsequent requests are sent every 60 seconds.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Generic Routing Encapsulation (GRE)
Platform: Cisco 10000 series
The Generic Routing Encapsulation feature supports Generic Routing Encapsulation (GRE) IP and Distance Vector Multicast Routing Protocol (DVMRP) multicast tunnel modes to transport otherwise unroutable packets across the IP network and provide data separation for Virtual Private Network (VPN) services. GRE tunnels make it possible to have multiprotocol local networks running over a single-protocol backbone. They also provide workarounds for networks that contain protocols that have limited hop counts, connectivity for discontinuous subnetworks, and connectivity for VPNs across wide-area networks. DVMRP multicast tunnel modes are supported only between the Cisco 10000 series edge services router and other vendor-specific stations that are running DVMRP version 3.8 or higher.
Note This feature has been ported from Cisco IOS Release 12.0ST.
HSRP Support for MPLS VPNs
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
Hot Standby Router Protocol (HSRP) support on a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) interface is useful when an Ethernet is connected between two provider edges (PEs) with either of the following:
•A customer edge (CE) with a default route to the HSRP virtual IP address
•One or more hosts with the HSRP virtual IP address configured as the default gateway
Each VPN is associated with one or more VPN routing/forwarding (VRF) instances. A VRF consists of the following:
•IP routing table
•Cisco Express Forwarding (CEF) table
•Set of interfaces that use the CEF forwarding table
•Set of rules and routing protocol parameters to control the information in the routing tables
VPN routing information is stored in the IP routing table and the CEF table for each VRF. A separate set of routing and CEF tables is maintained for each VRF. These tables prevent information from being forwarded outside a VPN and also prevent packets that are outside a VPN from being forwarded to a router within the VPN.
HSRP currently adds Address Resolution Protocol (ARP) entries and IP hash table entries (aliases) using the default routing table instance. However, a different routing table instance is used when VRF forwarding is configured on an interface, causing ARP and Internet Control Message Protocol (ICMP) echo requests for the HSRP virtual IP address to fail.
The HSRP Support for MPLS VPNs feature ensures that the HSRP virtual IP address is added to the correct IP routing table and not to the default routing table.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dt_hsmp.htm
Note This feature has been ported from Cisco IOS Release 12.0ST. Support for the Cisco 10000 series has been added in Cisco IOS Release 12.0(22)S.
IP Event Dampening
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
The IP Event Dampening feature introduces a configurable exponential decay mechanism to suppress the effects of excessive interface flapping events to the routing protocols and the routing table. This feature allows the network operator to configure a router to identify and dampen flapping interfaces, thereby reducing the utilization of system processing resources and improving network stability.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/s_ip evdp.htm
IP Receive ACL
Platform: Cisco 12000 series
The IP Receive ACL feature provides basic filtering capability for traffic that is destined for the router; that is, the router can protect high priority routing protocol traffic from an attack because the filtering occurs after any input access control list (ACL) on the ingress interface.
This feature may be implemented in a security solution to protect a router from remote intrusions. Access to the router can be restricted to known, trusted sources and expected traffic profiles.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/ft_ip acl.htm
IP Source Tracker Supported on the 7500 Series Routers
Platform: Cisco 7500/RSP series
The IP Source Tracker feature allows you to gather information about the traffic flowing to a host that is suspected to be under attack. This feature also allows you to easily trace an attack back to its entry point into the network.
After you identify the destination being attacked, you can enable tracking for the destination address on the router by entering the ip source-track command. Each line card or port adapter creates a special Cisco Express Forwarding (CEF) entry for the destination address being tracked. For line cards or port adapters that use specialized application specific integrated circuits (ASICs) to do packet switching, the CEF entry is used to punt packets to the CPU of the line card or the CPU of the port adapter. These CPUs collect information about the traffic flow to the tracked destination.
The data generated is periodically exported to the router. To display a summary of the flow information, enter the show ip source-track summary command. To display more detailed information for each input interface, enter the show ip source-track command.
Statistics provide a breakdown of the traffic to each tracked IP address. This allows you to determine which upstream router to analyze next. You can shut down the IP source tracker on the current router by entering the no ip source-track command, and re-open it on the upstream router.
Repeat this process until you identify the source of the attack. You can then apply committed access rate (CAR) or access control lists (ACLs) to limit or stop the attack.
For further information, see the Cisco documents at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/ipst. htm
Note Support for the IP Source Tracker feature was introduced on the Cisco 12000 series Internet router in Cisco IOS Release 12.0(21)S.
IPv6
The following features appear under this feature heading:
• CEFv6/dCEFv6—Cisco Express Forwarding
• IPv6 Provider Edge Router over MPLS
• Secure Shell (SSH) over an IPv6 Transport
CEFv6/dCEFv6—Cisco Express Forwarding
Platform: Cisco 12000 series
Cisco Express Forwarding for IPv6 (CEFv6) is advanced, Layer 3 IP switching technology for the forwarding of IPv6 packets. Distributed CEF for IPv6 (dCEFv6) performs the same functions as CEFv6 but for distributed architecture platforms such as the Cisco 12000 series Internet routers. dCEFv6 and CEFv6 function the same and offer the same benefits as dCEFv4 and CEFv4.
In Cisco IOS Release 12.0(22)S, dCEFv6 and CEFv6 include support for separate Forwarding Information Bases (FIBs) for IPv6 global, site-local, and link-local addresses, and a separate global FIB for each Virtual Private Network (VPN).
For more information, see the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
IPv6 for Cisco IOS Software
Platform: Cisco 12000 series
IP version 6 (IPv6), formerly called IPng (next generation), is the latest version of IP and offers many benefits, such as a larger address space, over the previous version of IP (version 4). In Cisco IOS Release 12.0(22)S, the IPv6 for Cisco IOS Software feature is enhanced by the addition of the following features:
•DNS lookups over an IPv6 transport
•Static cache entry for IPv6 neighbor discovery
•Use of the first MAC address as the IPv6 interface identifier for point-to-point links
•Integrated IS-IS for IPv6
•Link-local address peering in multiprotocol BGP extensions for IPv6
•Distributed CEF switching for IPv6
For further information, see the Cisco documents at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
IPv6 Provider Edge Router over MPLS
Platform: Cisco 12000 series
The IPv6 Provider Edge Router over MPLS feature (also referred to as Cisco 6PE) enables IPv6 sites to communicate over a Multiprotocol Label Switching (MPLS) IPv4 network with no software or hardware upgrades in the core MPLS infrastructure and with no disruption to existing customer services.
For more information see the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
IPv6 RIP Enhancements
Platform: Cisco 12000 series
The IPv6 RIP Enhancements feature adds support for a separate IPv6 Routing Information Protocol (RIP) routing table, the ability to delete routes from the IPv6 RIP routing table, and the ability to set route tags. The holddown timer default is now set to zero, and a maximum number of parallel routes can be configured.
For more information, see the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
Secure Shell (SSH) over an IPv6 Transport
Platform: Cisco 12000 series
Secure Shell (SSH) in IP version 6 (IPv6) functions the same and offers the same benefits as SSH in IPv4—the SSH Server feature enables an SSH client to make a secure, encrypted connection to a Cisco router and the SSH Client feature enables a Cisco router to make a secure, encrypted connection to another Cisco router or to any other device running an SSH server. IPv6 enhancements to SSH consist of support for IPv6 addresses that enable a Cisco router to accept and establish secure, encrypted connections with remote IPv6 nodes over an IPv6 transport.
For more information see the IPv6 for Cisco IOS Software document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/index.htm
IS-IS HMAC-MD5 Authentication
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
The IS-IS HMAC-MD5 Authentication feature adds an HMAC-MD5 digest to each Intermediate System-to-Intermediate System (IS-IS) protocol data unit (PDU). HMAC is a mechanism for message authentication codes (MAC) using cryptographic hash functions. The digest allows authentication at the IS-IS routing protocol level, which prevents unauthorized routing messages from being injected into the network routing domain.
IS-IS has five packet types: link-state packet (LSP), LAN Hello, Serial Hello, complete sequence number PDU (CSNP), and partial sequence number PDU (PSNP). The IS-IS HMAC-MD5 authentication or the cleartext password authentication can be applied to all five types of PDU. The authentication can be enabled on different IS-IS levels independently. The interface-related PDUs (LAN Hello, Serial Hello, CSNP and PSNP) can be enabled with authentication on different interfaces, with different levels and different passwords.
The HMAC-MD5 mode cannot be mixed with the clear text mode on the same authentication scope (LSP or interface). However, administrators can use one mode for LSP and another mode for some interfaces, for example. If mixed modes are intended, different keys should be used for different modes in order not to compromise the encrypted password in the PDUs.
For more information about the IS-IS HMAC-MD5 Authentication feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/ftm d5isi.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
IS-IS Mechanisms to Exclude Connected IP Prefixes from LSP Advertisements
Platform: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10720, Cisco 12000 series
This feature provides two IS-IS mechanisms to exclude IP prefixes of connected networks from label-switched path (LSP) advertisements, thereby reducing IS-IS convergence time.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fsisi adv.htm
Label-Controlled ATM Interface (LC-ATM)
Platform: Cisco 12000 series
The Label-Controlled ATM Interface (LC-ATM) feature allows Cisco 12000 series Internet routers to operate with the Cisco Label Switch Controller (LSC). The LSC must be running IOS Version 12.1(5)T or higher, and the Cisco 12000 series Internet router must be running Cisco IOS Version 12.0(22)S or higher.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Label Switch Routing
Platform: Cisco 10000 series
The Label Switch Routing feature enables the Cisco 10000 series edge services (ESR) router to function as a provider router (P router) in a Multiprotocol Label Switching (MPLS) network. Previously, the Cisco 10000 series ESR could function as a provider edge (PE) router, forwarding packets from an IP network to an MPLS (label imposition) network and from an MPLS network to an IP (label disposition) network. This feature adds full Label Switch Routing (LSR) support, enabling the router to perform MPLS-to-MPLS forwarding (label switching).
For more information about MPLS on Cisco routers, including the Cisco 10000 series ESR, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/fs_ rtr.htm
New Features
LSR provides the following new features:
•Support for MPLS push, pop, and swap operations.
•The ability to switch labeled packets and function as an MPLS provider router (P router).
•Load balancing for each destination on a label switched path (LSP).
•Support for combined P router and PE router functionality: for example, in a distributed point of presence (POP) configuration that cross-connects POPs together for resilience purposes, or when the Cisco 10000 series ESR has redundant trunks into an MPLS network.
•Enhancements to the TFIB data structure:
–The router allocates tag info structures only for label switched paths (LSPs) that have load balancing enabled.
–Counters have been added to determine the number of bytes that are switched through each label in the TFIB.
–Support for explicit-null labels. These labels are used in label switch controller ATM (LC-ATM) processing to communicate experimental (EXP) bits.
Requirements
To run the LSR feature, the Cisco 10000 series ESR must have the PRE1 version (part number ESR-PRE1) of the Performance Routing Engine (PRE) installed in the Cisco 10000 series ESR chassis. You can verify which PRE is installed in the chassis by using the show version command.
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Egress NetFlow Accounting
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The MPLS Egress NetFlow Accounting feature allows you to capture IP flow information for packets undergoing Multiprotocol Label Switching (MPLS) label disposition—that is, packets that arrive on a router as MPLS and are transmitted as IP.
Prior to this feature, you captured NetFlow data only for flows that arrived on the packet in IP format. When an edge router performed MPLS label imposition (received an IP packet and transmitted it as an MPLS packet), NetFlow data was captured when the packet entered the network. Inside the network, the packet was switched based only on MPLS information; NetFlow information was not captured until after the last label was removed.
One common application of the MPLS Egress NetFlow Accounting feature allows you to capture the MPLS Virtual Private Network (VPN) IP flows that are traveling through a service provider backbone from one site in a VPN to another site in the same VPN.
Formerly, you captured flows only for IP packets on the ingress interface of a router. You could not capture flows for MPLS encapsulated frames, which were switched through Cisco Express Forwarding (CEF) from the input port. Therefore, in an MPLS VPN environment you captured flow information as packets were received from a customer edge (CE) router and forwarded to the backbone. However, you could not capture flow information as packets were transmitted to a CE router because those packets were received as MPLS frames.
The MPLS Egress NetFlow Accounting feature lets you capture the flows on the outgoing interfaces.
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Enhancements in the Cisco 10720 Internet Router
Platform: Cisco 10720
MPLS Provider Backbone and Provider Edge Functionality in the Cisco 10720 Internet Router
Cisco IOS Release 12.0(22)S supports the following MPLS provider (P) backbone and provider edge (PE) functionality in the Cisco 10720 Internet router in addition to existing IP features:
•MPLS Virtual Private Networks (RFC 2547)
•MPLS Label Distribution Protocol
•Label switching
The IP Virtual Private Network (VPN) feature for MPLS allows a Cisco IOS network to deploy scalable IPv4 Layer 3 VPN backbone services. An IP VPN is the foundation that companies use for deploying or administering value-added services including applications and data hosting network commerce, and telephony services to business customers. For more information about MPLS VPNs, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/fs_ vpn.htm
Cisco's MPLS Label Distribution Protocol (LDP), as standardized by the Internet Engineering Task Force (IETF) and as enabled by Cisco IOS software, allows the construction of highly scalable and flexible IP VPNs that support multiple levels of services.
LDP provides a standard methodology for hop-by-hop, or dynamic label, distribution in an MPLS network by assigning labels to routes that have been chosen by the underlying Interior Gateway Protocol (IGP) routing protocols. The resulting labeled paths, called label switch paths or label-switched paths (LSPs), forward label traffic across an MPLS backbone to particular destinations. These capabilities enable service providers to implement Cisco's MPLS-based IP VPN services across multivendor MPLS networks. For more information about MPLS LDP, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/fsl dp_21.htm
Label switching combines the performance and capabilities of Layer 2 (data link layer) switching with the proven scalability of Layer 3 (network layer) routing. It enables service providers to meet challenges brought about by explosive growth and provides the opportunity for differentiated services without necessitating the sacrifice of existing infrastructure. The label switching architecture is remarkable for its flexibility. Data can be transferred over any combination of Layer 2 technologies, support is offered for all Layer 3 protocols, and scaling is possible well beyond anything offered in today's networks.
Specifically, label switching can efficiently enable the delivery of IP services over an ATM switched network. It supports the creation of different routes between a source and a destination on a purely router-based Internet backbone. Service providers who use label switching can save money and increase revenue and productivity. For more information about MPLS label switching, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/fs_ rtr.htm
New Show Commands for MPLS Forwarding in Cisco 10720 Internet Routers
In a Cisco 10720 Internet router, you can use the following command to display hardware information about the MPLS forwarding performed by Parallel Express Forwarding (PXF) for a given IP prefix or incoming MPLS label:
show hardware pxf cpu mpls [network [mask] | label]
The argument network specifies the IP address of a destination network, the argument mask specifies the network mask of a destination network, and the argument label specifies an incoming MPLS label.
For more information on the command syntax and for sample output, see the Cisco document
Cisco IOS Software Configuration for the Cisco 10720 Internet Router at the following location:http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st18/10 720.htm
Note These features have been ported from Cisco IOS Release 12.0ST.
MPLS Label Distribution Protocol (LDP)
The following features appear under this feature heading:
• MPLS Label Distribution Protocol (LDP)
• MPLS Label Distribution Protocol (LDP) MIB
MPLS Label Distribution Protocol (LDP)
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The MPLS Label Distribution Protocol (LDP) feature is the Internet Engineering Task Force (IETF) standard protocol for label distribution. LDP provides the means for label switching routers (LSRs) to request, distribute, and release label prefix binding information to peer routers in a network. LDP is a two-party protocol that provides the means for LSRs to discover potential peers in a network and to establish LDP sessions with those peers for the purpose of exchanging label binding information.
Functionally, LDP is a superset of the prestandard Tag Distribution Protocol (TDP), which also supports Multiprotocol Label Switching (MPLS) forwarding along normally routed paths. In addition, for those features that LDP and TDP have in common, the pattern of protocol exchanges between platforms is identical. The differences between LDP and TDP for the features that both protocols support are largely embedded in their respective implementation details, such as the encoding of protocol messages.
This release, which supports both LDP and TDP, provides the means for transitioning an existing network from a TDP switching environment to an LDP switching environment. You can run LDP and TDP simultaneously on any given platform. The protocol that you use can be configured on a per-interface basis for directly connected neighbors and on a per-target basis for nondirectly connected (targeted) neighbors. In addition, a label-switched path (LSP) across an MPLS network can be supported by LDP on some hops and by TDP on other hops.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fsldp22.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Label Distribution Protocol (LDP) MIB
Platform: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Multiprotocol label switching (MPLS) is a packet forwarding methodology that uses a short, fixed-length value (called a label) in packets to enable the determination of the next hop for transporting packets through an MPLS network. Two label switching routers (LSRs) must agree on the definition of the labels used to forward network traffic between and through them. This common understanding of labels is achieved through a set of procedures embodied in the Label Distribution Protocol (LDP). The LDP enables an LSR to inform other LSRs of the label bindings it has made, thereby distributing label binding information to peer devices for the purpose of supporting hop-by-hop forwarding along normally routed paths.
For LDP to be used to the best advantage in an MPLS network, the MPLS Label Distribution Protocol MIB (MPLS LDP MIB) has been implemented in conjunction with MPLS and LDP. Designed as a network management aid, the MPLS LDP MIB is based on an Internet Engineering Task Force (IETF) draft that defines objects in a structured and standardized label-switching database.
The information in the MPLS LDP MIB is accessible by means of any network management utility that supports the Simple Network Management Protocol (SNMP). The SNMP-based code in a network management utility incorporates a layered structure for supporting the MPLS LDP MIB that is similar to that built into Cisco IOS software for supporting MIBs.
For further information, see the Cisco document MPLS Label Distribution Protocol (LDP) MIB at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/ldp mib21.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS LDP—MIB Traps
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
When you enable MPLS LDP MIB notification functionality by issuing the snmp-server enable traps mpls ldp command, notification messages are generated and sent to a designated network management station (NMS) in the network to signal the occurrence of specific events within Cisco IOS software.
The MPLS LDP MIB objects involved in Label Distribution Protocol (LDP) status transitions and event notifications include the following:
•mplsLdpSessionUp
•mplsLdpSessionDown
•mplsLdpPathVectorLimitMismatch
•mplsLdpFailedInitSessionThresholdExceeded
Note This implementation of the MPLS LDP MIB traps for Cisco IOS Release 12.0(22)S is limited to read-only (RO) permission for MIB objects, except for MIB object mplsLdpSessionUpDownTrapEnable, which, for purposes of this release, has been extended to be writeable by the Simple Network Management Protocol (SNMP) agent.
For further information, see the Cisco document MPLS Label Distribution Protocol (LDP) MIB at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/ldp mib21.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Label Switching Router MIB
Platforms: Cisco 7500/RSP series, Cisco 12000 series
The MPLS Label Switching Router MIB allows you to use the Simple Network Management Protocol (SNMP) to remotely monitor a label switching router (LSR) that is using the Multiprotocol Label Switching (MPLS) technology. The MPLS LSR MIB mirrors the Cisco Label Switching sub-system, specifically, the LSR management information that is provided by the Label Forwarding Information Base (LFIB).
The MPLS LSR MIB contains managed objects that support the retrieval of label switching information from a router and is based on Revision 05 of the IEFT MPLS-LSR-MIB. This implementation enables a network administrator to get information on the status, character, and performance of the following:
•MPLS capable interfaces on the LSR
•Incoming MPLS segments (labels) to an LSR and their associated parameters
•Outgoing segments (labels) at an LSR and their associated parameters
In addition, the network manager can retrieve the status of cross-connect entries that associate MPLS segments together.
For descriptions of supported MIBs and how to use them, see the Cisco MIB web site on Cisco.com at the following location:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Multiprotocol Label Switching
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Multiprotocol Label Switching (MPLS) combines the performance and capabilities of Layer 2 (data link layer) switching with the proven scalability of Layer 3 (network layer) routing. MPLS enables service providers to meet the challenges of explosive growth in network utilization while providing the opportunity to differentiate services without sacrificing the existing network infrastructure. The MPLS architecture is flexible and can be employed in any combination of Layer 2 technologies. MPLS support is offered for all Layer 3 protocols, and scaling is possible beyond that typically offered in today's networks.
MPLS efficiently enables the delivery of IP services over an ATM switched network. MPLS supports the creation of different routes between a source and a destination on a purely router-based Internet backbone. By incorporating MPLS into their network architecture, service providers can save money, increase revenue and productivity, provide differentiated services, and gain competitive advantages.
Note This feature is an update of the original tag switching command-line interface (CLI) to also incorporate the MPLS CLI for Cisco routers.
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Quality of Service (QoS)
The following features appear under this feature heading:
• MPLS Quality of Service (QoS)
• MPLS Quality of Service Enhancements
• MPLS Quality of Service in Cisco 10720 Internet Routers
MPLS Quality of Service (QoS)
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Note MPLS Class of Service is now referred to as MPLS Quality of Service. This transition reflects the growth of Multiprotocol Label Switching (MPLS) to encompass a wider meaning and highlights the path toward Any Transport over MPLS product set.
The MPLS Quality of Service (QoS) feature enables network administrators to provide differentiated services across an MPLS network. A range of networking requirements can be satisfied by supplying for each packet transmitted the particular QoS specified for each packet by means of its QoS precedence bit setting. QoS services are differentiated by means of the IP precedence bit setting in each transmitted IP packet.
In providing differentiated IP services, MPLS QoS supports the following services:
•Packet classification
•Congestion avoidance
•Congestion management
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st10/10 st_cos.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Quality of Service Enhancements
Platform: Cisco 7500/RSP series, Cisco 12000 series
Note MPLS Class of Service is now referred to as MPLS Quality of Service. This transition reflects the growth of Multiprotocol Label Switching (MPLS) to encompass a wider meaning and highlights the path toward Any Transport over MPLS product set.
When a customer transmits IP packets from one site to another, the IP precedence field (the first three bits of the differentiated services code point (DSCP) field in the header of an IP packet) specifies the quality of service. Based on the IP precedence marking, the packet is given the desired treatment such as the latency or the percent of bandwidth allowed for that quality of service. If the service provider network is an MPLS network, then the IP precedence bits are copied into the MPLS experimental (EXP) field at the edge of the network. However, the service provider might want to set an MPLS packet's QoS to a different value determined by the service offering.
This feature allows the service provider to set the MPLS experimental field instead of overwriting the value in the customer's IP precedence field. The IP header remains available for the customer's use; the IP packet's QoS is not changed as the packet travels through the MPLS network.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st14/mc t1214t.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Quality of Service in Cisco 10720 Internet Routers
Platform: Cisco 10720
The MPLS Quality of Service (QoS) feature in Cisco 10720 Internet routers allows a service provider to set the Multiprotocol Label Switching (MPLS) experimental field that specifies the class of service for MPLS encapsulated packets, overwriting the default value for this field. The default value is the customer's IP precedence field for IP packets, or zero for non-IP packets.
For more detailed information about MPLS QoS, see the MPLS Quality of Service Enhancements document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st14/mc t1214t.htm
MPLS Scalability Enhancements for the LSC and ATM LSR
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Multiprotocol Label Switching (MPLS) scalability enhancements allow the prevention of label-switched paths (LSPs) from being created in an MPLS network.
Some LSPs are often unnecessary between some label edge routers (LERs) in an MPLS network. Every time a new destination is created, LSPs are created from all LERs in the MPLS network to the new destination. You can use the tag-switching request-tags for command with an access list at an LER to restrict the destinations for which a downstream-on-demand request is issued. You specify the destination IP addresses that you want to disable from creating LSPs.
This command allows you to permit creation of some LSPs, while preventing the creation of others. Using this command reduces the number of LSPs in an MPLS network, which reduces the virtual circuit (VC) usage in the network.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st14/lsp bgone.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Support on Dynamic Packet Transport (DPT)
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Dynamic packet transport (DPT) offers the reliability and restorability typically associated with SONET/synchronous digital hierarchy (SDH) transport, without adding unnecessary overhead to IP traffic.
DPT uses dual counter-rotating fiber rings that can concurrently transport data and control traffic. DPT uses the Spatial Reuse Protocol (SRP), which is the media-independent MAC layer protocol, for addressing and stripping packets, controlling bandwidth, and controlling message propagation on the packet ring.
Note MPLS traffic engineering does not support DPT.
DPT (OC-12/STM4) is supported for forwarding and label distribution on the following:
•Cisco 7200 series routers
•Cisco 7500 series routers
•Cisco 12000 series Internet routers
DPT combines the bandwidth-efficient and service-rich capabilities of IP routing with the bandwidth-rich, self-healing capabilities of fiber rings to provide fundamental cost and functionality advantages over existing solutions.
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Traceroute
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
MPLS-aware traceroute functionality has been added to the traceroute program. When you enter the traceroute user EXEC command, the display output includes the IP address of the router interface through which the traceroute packet is passing, followed by the MPLS label information and the normal trace or ping information.
The following is sample output from the traceroute command:
Router-A#
traceroute 10.0.0.9
Type escape sequence to abort.
Tracing the route to 10.0.0.9
1 10.0.0.2 [MPLS: Label 138 Exp 0] 0 msec 0 msec 4 msec
2 10.0.0.5 [MPLS: Label 138 Exp 0] 0 msec 0 msec 0 msec
3 10.0.0.9 4 msec 0 msec
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Traffic Engineering (TE)
The following features appear under this feature heading:
• MPLS Traffic Engineering and Enhancements
• MPLS Traffic Engineering (TE)—Automatic Bandwidth Adjustment for (TE) Tunnels
• MPLS Traffic Engineering (TE)—Configurable Path Calculation Metric for Tunnels
• MPLS Traffic Engineering (TE)—Fast Reroute (FRR) Node Protection, with RSVP Hellos Support
• MPLS Traffic Engineering (TE)—Interarea Tunnels
• MPLS Traffic Engineering (TE)—Overload Avoidance Support for IS-IS
• MPLS Traffic Engineering (TE)—Scalability Enhancements
MPLS Traffic Engineering and Enhancements
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Multiprotocol Label Switching (MPLS) traffic engineering software enables an MPLS backbone to replicate and expand upon the traffic engineering capabilities of Layer 2 ATM and Frame Relay networks.
Traffic engineering (TE) is essential for service provider and Internet service provider (ISP) backbones. Such backbones must support the use of a high percentage of transmission capacity, and the networks must be very resilient so that they can withstand link or node failures.
MPLS traffic engineering provides an integrated approach to traffic engineering. With MPLS, traffic engineering capabilities are integrated into Layer 3, which optimizes the routing of IP traffic given the constraints imposed by backbone capacity and topology.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st10/te1 210st.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Traffic Engineering (TE)—Automatic Bandwidth Adjustment for (TE) Tunnels
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
Traffic engineering autobandwidth samples, at a user-configurable interval, the current 5-minute bandwidth average for each tunnel marked with an auto-bw flag. Traffic engineering autobandwidth then applies the highest sample to each marked tunnel at the tunnel's user-configurable time (for example, once per day).
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fstea ut.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Traffic Engineering (TE)—Configurable Path Calculation Metric for Tunnels
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
When Multiprotocol Label Switching (MPLS) traffic engineering (TE) is configured in a network, the Interior Gateway Protocol (IGP) floods two metrics for every link: the normal IGP (OSPF or IS-IS) link metric and a TE link metric. IGP uses the IGP link metric in the normal way to compute routes for destination networks. In previous releases, MPLS TE used the TE link metric to calculate and verify paths for TE tunnels. When the TE metric was not explicitly configured, the TE metric was the IGP metric.
The current enhancement enables you to control the metric used in path calculation for TE tunnels on a per-tunnel basis. It allows you to specify that the path calculation for a given tunnel be based on either of the following:
•IGP link metrics.
•TE link metrics, which you can configure so that they represent the needs of a particular application. For example, the TE link metrics can be configured to represent link transmission delay.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st18/del aysen.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS Traffic Engineering (TE)—Fast Reroute (FRR) Node Protection, with RSVP Hellos Support
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Fast ReRoute (FRR) is a mechanism for protecting Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) label-switched paths (LSPs) from link and node failures by locally repairing the LSPs at the point of failure, allowing data to continue to flow on the LSPs while their headend routers attempt to establish new end-to-end LSPs to replace them. FRR locally repairs the protected LSPs by rerouting them over backup tunnels that bypass failed links or nodes.
Backup tunnels that bypass only a single link of the LSP's path provide link protection. They protect LSPs if a link along their path fails by rerouting the LSP's traffic to the next hop (bypassing the failed link). These are referred to as next-hop (NHOP) backup tunnels because they terminate at the next hop of the LSP's path.
FRR provides node protection for LSPs with backup tunnels that bypass next-hop nodes along LSP paths. Such tunnels are called next-next-hop (NNH) backup tunnels because they terminate at the node following the next-hop node of the LSP paths, thereby bypassing the next-hop node. They protect LSPs if a node along their path fails by enabling the node upstream of the failure to reroute the LSPs and their traffic around the failed node to the next-next hop. FRR supports the use of Resource Reservation Protocol (RSVP) Hellos to accelerate the detection of node failures. NHOP backup tunnels also provide protection from link failures because they bypass the failed link as well as the node.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fs_f rnod.htm
Note In Cisco IOS Release 12.2(22)S, MPLS Traffic Engineering (TE)—Fast Reroute (FRR) Node Protection is also supported on the Cisco 12000 series Engine 4 OC-192 line cards.
Note This feature has been ported from Cisco IOS Release 12.0ST, where it was introduced as MPLS Traffic Engineering (TE)—Fast Reroute (FRR) Link Protection. Enhancements to the feature have been added in Cisco IOS Release 12.0(22)S.
MPLS Traffic Engineering (TE)—Interarea Tunnels
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The MPLS Traffic Engineering (TE)—Interarea Tunnels feature allows you to establish Multiprotocol Label Switching (MPLS) TE tunnels that span multiple Interior Gateway Protocol (IGP) areas and levels, removing the restriction that had required that the tunnel headend and tailend routers both be in the same area. The IGP can be either Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF).
To configure an interarea tunnel, you specify on the headend router a loosely routed explicit path for the tunnel label switched path (LSP) that identifies each area border router (ABR) that the LSP should traverse using the next-address loose command. The headend router and the ABRs along the specified explicit path expand the loose hops, each computing the path segment to the next ABR or tunnel destination.
For further information, see the Cisco document MPLS Traffic Engineering (TE)—Interarea Tunnels at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fs_a reat.htm
Note This feature has been ported from Cisco IOS Release 12.0ST. Support for the Cisco 10000 series has been added in Cisco IOS Release 12.0(22)S.
MPLS Traffic Engineering (TE)—Overload Avoidance Support for IS-IS
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The MPLS Traffic Engineering (TE)—Overload Avoidance Support for IS-IS feature allows you to include specific routers in Constrained Shortest Path First (CSPF) calculations, even when the routers indicate through Intermediate System-to-Intermediate System (IS-IS) that they are overloaded. This new feature is implemented through a single command, mpls traffic-eng path-selection overload allow. The function of this new command is closely tied to the function of the set-overload-bit command.
Occasionally you may want a router in an IS-IS network not to carry traffic. For example:
•A test router in a lab that is connected to a production network
•A router that is configured as a link-state packet (LSP) flooding server (for example, on a nonbroadcast multiaccess [NBMA] network) in combination with the Mesh Group feature
•A router that is aggregating virtual circuits (VCs) that are used only for network management
•A router on which a memory shortage occurs, which causes the routing table to be inaccurate or incomplete
To isolate any such router, enable the set-overload-bit command, which will allow other routers to ignore this router in their Shortest Path First (SPF) calculations. No paths through this router will be seen by other routers in the IS-IS area. Nevertheless, IP and Connectionless Network Service (CLNS) prefixes directly connected to this router will still be reachable.
The MPLS Traffic Engineering (TE)—Overload Avoidance Support for IS-IS feature enables you to selectively override the overload bit with respect to Multiprotocol Label Switching (MPLS) LSPs by using the new mpls traffic-eng path-selection overload allow command. This command enables the operator to include an overloaded node in CSPF calculations.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fs_is ovr.htm
MPLS Traffic Engineering (TE)—Scalability Enhancements
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Implementation of Multiprotocol Label Switching (MPLS) traffic engineering scalability has been improved so that scalability performs better for large numbers of tunnels. These improvements
•Increase the number of traffic engineering tunnels a router can support when acting as a tunnel headend and when acting as a tunnel midpoint.
•Reduce the time required to establish large numbers of traffic engineering tunnels.
User-visible scalability enhancements include the following:
•Pacing for RSVP Messages
•Signaling and Management for MPLS Traffic Engineering Tunnels
•Controlling IS-IS and MPLS Traffic Engineering Topology Database Interactions
•Improved Diagnostic Capabilities for MPLS Traffic Engineering and RSVP Signaling
Pacing for RSVP Messages
A burst of Resource Reservation Protocol (RSVP) traffic engineering signaling messages may overflow the input queue of a receiving router, causing some messages to be dropped. Dropped messages cause a substantial delay in completing link-state packet (LSP) signaling.
A new mechanism controls the transmission rate for RSVP messages and lessens the likelihood of input drops on the receiving router. The transmission rate is configurable with a default rate of 200 RSVP messages per second to a given neighbor.
Signaling and Management for MPLS Traffic Engineering Tunnels
The following changes improve the responsiveness of LSP recovery when a link used by an LSP fails:
•When the upstream end of a failed link detects the failure, it generates an RSVP No Route Path Error message. This enables the LSP headend to detect the link failure and initiate recovery even when the Interior Gateway Protocol (IGP) update announcing the link failure is delayed.
•The LSP headend marks the link in question so that subsequent constraint-based SPF calculations ignore the link until either a new IGP update arrives or a configurable timeout occurs. This ensures that resignaling to restore the LSP avoids the failed link.
Controlling IS-IS and MPLS Traffic Engineering Topology Database Interactions
The delay between when Intermediate System-to-Intermediate System (IS-IS) receives an IGP update and when it delivers it to the MPLS traffic engineering topology database has been reduced in most situations.
Previously, when IS-IS received a new LSP that contained traffic engineering type, length, value objects (TLVs) there could be a delay of several seconds before it passed the traffic engineering TLVs to the traffic engineering database. The purpose of the delay was to provide better scalability during periods of network instability and to give the router an opportunity to receive more fragments of the LSP before passing the information to the traffic engineering database. However, this delay introduced a corresponding delay to the convergence time for the traffic engineering database.
Now IS-IS extracts traffic engineering TLVs from received LSPs and passes them to the traffic engineering database immediately, except when there are large numbers of LSPs to process and it is important to limit CPU consumption, such as during periods of network instability. The arguments that control delivery of traffic engineering TLVs by IS-IS to the traffic engineering topology database are configurable.
Improved Diagnostic Capabilities for MPLS Traffic Engineering and RSVP Signaling
The following enhancements improve diagnostic and troubleshooting capabilities for Multiprotocol Label Switching (MPLS) Traffic Engineering and Resource Reservation Protocol (RSVP):
•Counters record tunnel headend error events such as no route (link down), preemption, and insufficient bandwidth on a per tunnel basis.
•Counters record RSVP messages. The counters are per interface and record the number of RSVP messages of each type sent and received on the interface.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st14/sca lable.htm
Note These features have been ported from Cisco IOS Release 12.0ST.
Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN)
The following features appear under this feature heading:
• MPLS Virtual Private Network (VPN)
• MPLS VPN Line Cards for Cisco 12000 Series Internet Routers
• MPLS VPN MIB and MPLS VPN MIB Traps
• MPLS VPN—OSPF Provider Edge (PE)-Customer Edge (CE) Support
• MPLS VPN Support for EIGRP Between Provider Edge (PE) and Customer Edge (CE)
• MPLS VPN—VRF Selection Based on Source IP Address
MPLS Virtual Private Network (VPN)
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
A Virtual Private Network (VPN) is a secure IP-based network that uses a shared backbone to distribute resources on one or more physical networks located in geographically dispersed sites. MPLS-based VPNs make it possible to have highly scalable, highly flexible IP VPNs in Layer 3 without tunneling or encryption.
Multiprotocol Label Switching (MPLS) VPNs have the following advantages over the current IP VPN solutions that rely on Layer 2 VC, Layer 3 tunnels, or encryption:
•Scales better.
•Provides any-to-any communication through connectionless Layer 3 IP.
•Allows flexible addressing schemes; for example, addresses do not have to be globally unique.
•More easily manages the addition of new members and new VPNs.
•Supports different classes of service within and between VPNs.
•Leverages additional services such as application and web hosting or network commerce solutions.
End users do not have to modify their IP applications or support MPLS.
MPLS-based VPNs support a variety of Layer 2 technologies (ATM, Frame Relay, Packet over SONET [POS], and multiaccess) for customer access and in the provider's backbone.
Line cards supported for Cisco 12000 series Internet routers include:
•4-port OC-3/POS (single- and multi-mode)
•1-port OC-12/POS (single- and multi-mode)
•4-port OC-3/ATM
•1-port OC-12/ATM (single- and multi-mode)
Note Additional line cards for the Cisco 12000 series Internet routers are documented in the "MPLS VPN Line Cards for Cisco 12000 Series Internet Routers" section.
Note A provider edge (PE) router supports only the 4-port OC-3 POS and ATM line cards and the 1-port OC-12 POS and ATM line cards.
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN ID
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The MPLS VPN ID feature allows you to identify Virtual Private Networks (VPNs) by a VPN identification number, as described in RFC 2685. Multiple VPNs can be configured in a router. You can use a VPN name (a unique ASCII string) to reference a specific VPN configured in the router.
Alternately, you can use a VPN ID to identify a particular VPN in the router. The VPN ID follows a standard specification (RFC 2685). To ensure that the VPN has a consistent VPN ID, assign the same VPN ID to all the routers in the service provider network that services that VPN.
Remote access applications, such as the RADIUS and Dynamic Host Configuration Protocol (DHCP), can use the MPLS VPN ID feature to identify a VPN. RADIUS can use the VPN ID to assign dial-in users to the proper VPN on the basis of the authentication information of each user.
Configuration of a VPN ID for a VPN is optional. You can still use a VPN name to identify configured VPNs in the router. The VPN name is not affected by the VPN ID configuration. These are two independent mechanisms to identify VPNs.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st17/vp nid.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN Line Cards for Cisco 12000 Series Internet Routers
Platform: Cisco 12000 series
This section consists of the following subsections:
• MPLS VPN and Fast Reroute on 10 Gbps POS Enhanced Services Line Cards
• MPLS VPN and IP Packet Precedence Marking on Engine 2 POS Line Cards
• MPLS VPN and Traffic Engineering Support on the 6E3-SMB and 12 E3-SMB Line Cards
• MPLS VPN and Traffic Engineering Support on the 6CT3-SMB Line Card
• MPLS VPN Support for POS, DPT, and Channelized Line Cards
• MPLS VPN Support for the QOC-12 ATM Line Card
• MPLS VPN, TE, and LDP Support for the OC-192c and QOC-48c Line Cards
MPLS VPN and Fast Reroute on 10 Gbps POS Enhanced Services Line Cards
The MPLS Virtual Private Network (VPN) and Fast Reroute (FRR) features are supported on Packet-over-SONET (POS) Enhanced Services (ES, also referred to as Engine 4 plus) line cards in Cisco 12000 series Internet routers, including:
•1-port OC-192c/STM-64c POS core line card
•4-port OC-48c/STM-16c POS core line card
A VPN is a secure IP-based network that uses a shared backbone to distribute resources on one or more physical networks located in geographically dispersed sites. MPLS-based VPNs enable highly scalable, highly flexible IP VPNs in Layer 3 without tunneling or encryption. For more information about MPLS VPNs, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/vpn.htm
Regular MPLS traffic engineering automatically establishes and maintains label-switched paths (LSPs) across the backbone using Resource Reservation Protocol (RSVP). The path used by a given LSP at any point in time is based upon the LSP resource requirements and available network resources such as bandwidth.
Available resources are flooded via extensions to a link-state-based Interior Gateway Protocol (IGP), such as Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF).
Paths for LSPs are calculated at the LSP headend. Under failure conditions, the headend determines a new route for the LSP. Recovery at the headend provides for the optimal use of resources. However, because of messaging delays, the headend cannot recover as fast as possible by making a repair at the point of failure.
Fast Reroute provides link protection to LSPs. This enables all traffic carried by LSPs that traverse a failed link to be rerouted around the failure. The reroute decision is completely controlled locally by the router interfacing the failed link. The headend of the tunnel is also notified of the link failure through the IGP or through RSVP; the headend then attempts to establish a new LSP that bypasses the failure.
For more information about Fast Reroute, see the "MPLS Traffic Engineering (TE)—Fast Reroute (FRR) Node Protection, with RSVP Hellos Support" section.
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN and IP Packet Precedence Marking on Engine 2 POS Line Cards
Engine 2 (E2) Packet-over-SONET (POS) line cards in Cisco 12000 series Internet routers now support the following features:
•MPLS VPNs
A Virtual Private Network (VPN) is a secure IP-based network that uses a shared backbone to distribute resources on one or more physical networks located in geographically dispersed sites. MPLS-based VPNs enable highly scalable, highly flexible IP VPNs in Layer 3 without tunneling or encryption. For more information about MPLS VPNs, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/vpn.htm
•IP Packet Precedence Marking
The IP Packet Precedence Marking feature (also referred to as IP Marking) allows you to mark packets by setting the IP precedence bits or the IP differentiated services code point (DSCP) in the IP type of service (ToS) byte. By marking packets, you can classify traffic on the basis of the IP precedence or IP DSCP value. IP marking can be used to identify traffic within the network. Also, other interfaces can match traffic on the basis of the IP precedence or DSCP markings. For more information about how to use IP Packet Precedence Marking, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/cbpmark2. htm
The MPLS VPNs and IP Packet Precedence Marking features are supported on the following Engine 2 POS line cards:
•8-port OC-3 POS edge line card
•16-port OC-3 POS edge line card
•4-port OC-12 POS edge line card
•1-port OC-48 POS core line card
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN and Traffic Engineering Support on the 6E3-SMB and 12 E3-SMB Line Cards
Cisco IOS Release 12.0(22)S introduces support for the following features on the 6E3-SMB and 12E3-SMB line cards:
•MPLS Virtual Private Networks (VPNs)
•MPLS Quality of Service (QoS)
•MPLS Traffic Engineering (TE)
The 6E3-SMB and 12E3-SMB line cards consist of high-density E# service through 6 or 12 E3 interfaces.
The 6-port line card is a partially depopulated version of the 12-port line card. The 6-port line card consists of a total of 12 connectors. A single port consists of one coaxial connector for receiving (Rx) and one coaxial connector for transmitting (Tx). The ports on the 6-port line card are numbered 0 to 5.
The 12-port line card consists of a total of 24 connectors. A single port consists of one coaxial connector for receiving (Rx) and one coaxial connector for transmitting (Tx). The ports on the 12-port line card are numbered 0 to 11.
see the following document for further information about the 6E3-SMB and 12E3-SMB line cards:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_chan/11613e3.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN and Traffic Engineering Support on the 6CT3-SMB Line Card
In Cisco IOS Release 12.0(22)S, the following support is introduced for the 6-port channelized T3 (6CT3-SMB) line card on the Cisco 12000 series Internet routers:
•MPLS Virtual Private Networks (VPNs)
•MPLS Quality of Service (QoS)
•MPLS Traffic Engineering (TE)
The 6CT3-SMB line card provides high-density digital signal level 3 (DS3) service through six copper T3 ports. T3 transmits DS3-formatted data at 44.736 Mbps through the telephone switching network that is used in a digital WAN carrier facility. A T3 can be channelized into 28 independent DS1 data channels or up to 35 NxDS0. A total of 168 DS1 channels are supported, or 210 NxDS0 per line card.
For more information on the Cisco 12000 series Internet routers 6CT3-SMB line card, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_chan/10318ct3.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN Support for POS, DPT, and Channelized Line Cards
MPLS-based Virtual Private Networks (VPNs) on Engine 2 line cards support Packet-over-SONET (POS) and DPT-48 technologies for customer access and for connection to the service provider's backbone. A maximum of 256 VPNs (16 x 16) can be configured on a Cisco 12000 series Internet router that is fully populated with 16xOC-3 Engine 2 line cards. A maximum of approximately 100,000 VPN routes can be configured on a Cisco 12000 series Internet router platform with Engine 2 line cards, when not using other Multiprotocol Label Switching (MPLS) applications such as QoS.
New MPLS VPN line cards supported for Cisco 12000 series Internet routers include the following:
•4-port OC-12 (4x-OC-12)/POS
•1-port OC-48/POS
•16xOC-3/POS
•DPT OC-48
•2-port Channelized OC-3/STM-1 to DS1/E1
•Channelized OC-12/STM-4 with four STS-3c/STM-1 POS paths
•Channelized OC-12c to DS3
•Six- or 12-port DS3
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN Support for the QOC-12 ATM Line Card
Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) is supported for only customer access on the QOC-12 ATM line card. Connection to the service provider's backbone is not supported on the QOC-12 ATM. A maximum of 320 VPNs can be configured on the ATM E2 line card per Cisco 12000 series Internet router. The maximum number of VPN routes per Cisco 12000 series Internet router should be no more than 100,000.
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN, TE, and LDP Support for the OC-192c and QOC-48c Line Cards
Cisco IOS Release 12.0(22)S adds support for the following features on the OC-192c/STM-64c Packet-over-SONET (POS) and Quad OC-48c/STM-16c POS line cards:
•MPLS Virtual Private Networks (VPNs)
•MPLS Traffic Engineering (TE)
•MPLS Label Distribution Protocol (LDP)
The OC-192c/STM-64c (POS) line card provides the Cisco 12416 Internet router with a single 10-Gbps POS interface on a single card. The card interfaces with the 320-Gbps switch fabric in the Cisco 12016 Internet router and provides one OC-192 duplex SC or FC single-mode connection. This connection is concatenated, which provides for increased efficiency by eliminating the need to partition the bandwidth.
The Quad OC-48c/STM-16c Packet-over-SONET (POS) line card provides the Cisco 12416 Internet router with a single 10-Gbps POS interface on a single card. The card interfaces with the switch fabric in the Internet router and provides one OC-48c/STM-16c duplex SC or FC single-mode connection. This connection is concatenated, which provides for increased efficiency by eliminating the need to partition the bandwidth.
For further information about the OC-192c and QOC-48c line cards, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/index.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN MIB and MPLS VPN MIB Traps
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Simple Network Management Protocol (SNMP) agent code operating in conjunction with the Provider-Provisioned VPN (PPVPN) Multiprotocol Label Switching Virtual Private Network (MPLS VPN) MIB enables a standardized, SNMP-based approach in managing MPLS VPNs in Cisco IOS software.
The PPVPN MPLS VPN MIB is based on the Internet Engineering Task Force (IETF) draft MIB draft-ietf-ppvpn-mpls-vpn-mib-03.txt, which includes objects describing features that support MPLS VPN events. This IETF draft MIB, which undergoes revisions from time to time, is being evolved toward becoming a standard. Accordingly, the Cisco implementation of features of the PPVPN MPLS VPN MIB is expected to track the evolution of the IETF draft MIB.
Some slight differences between the IETF draft MIB and the actual implementation of MPLS VPNs within Cisco IOS software require some minor translations between the PPVPN MPLS VPN MIB and the internal data structures of Cisco IOS software. These translations are accomplished by means of the SNMP agent code. Also, while running as a low priority process, the SNMP agent provides a management interface to Cisco IOS software.
The SNMP objects defined in the PPVPN MPLS VPN MIB can be viewed by any standard SNMP utility. The network administrator can retrieve information in the PPVPN MPLS VPN MIB using standard SNMP get and getnext operations.
All PPVPN MPLS VPN MIB objects are based on the IETF draft MIB; thus, no specific Cisco SNMP application is required to support the functions and operations that pertain to the PPVPN MPLS VPN MIB features.
In Cisco IOS Release 12.0(22)S, the PPVPN MPLS VPN MIB provides you with the ability to do the following:
•Gather routing and forwarding information for MPLS VPNs on a router.
•Expose information in the VPN routing/forwarding (VRF) routing table.
•Gather information on Border Gateway Protocol (BGP) configuration related to VPNs and VRF interfaces and statistics.
•Emit notification messages that signal changes when critical MPLS VPN events occur.
•Enable, disable, and configure notification messages for MPLS VPN events by using extensions to existing SNMP command-line interface (CLI) commands.
•Specify the IP address of a network management system (NMS) in the operating environment to which notification messages are sent.
•Write notification configurations into nonvolatile memory.
For further information—including information about how to configure the router to send SNMP traps— see the Cisco document MPLS VPN MIB at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/fsv pnmib.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN—OSPF Provider Edge (PE)-Customer Edge (CE) Support
Platforms: Cisco 7200 series, Cisco 7500/RSP series
Setting a separate router ID for each interface or subinterface on a provider edge (PE) router attached to multiple customer edge (CE) routers within a Virtual Private Network (VPN) provides increased flexibility through Open Shortest Path First (OSPF) when routers exchange routing information among sites. The OSPF Provider Edge (PE)-Customer Edge (CE) feature is supported only on the Cisco 7000 family of routers (Cisco 7200 and Cisco 7500).
For more information, see the MPLS Virtual Private Network Enhancements feature in Cisco IOS Release 12.0(7)T.
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN Support for EIGRP Between Provider Edge (PE) and Customer Edge (CE)
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The MPLS VPN Support for EIGRP Between Provider Edge (PE) and Customer Edge (CE) feature provides the Enhanced Interior Gateway Routing Protocol (EIGRP) with the capability to redistribute routes through a Border Gateway Protocol (BGP) Virtual Private Network (VPN) cloud. This feature is configured only on PE routers, requiring no upgrade or configuration changes to customer equipment. This feature also introduces EIGRP support for Multiprotocol Label Switching (MPLS) and BGP extended community attributes.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc//td/doc/product/software/ios120/120newft/120limit/120s/120s22/seig pece.htm
MPLS VPN—VRF Selection Based on Source IP Address
Platform: Cisco 12000 series
The VRF Selection feature allows packets that arrive on an interface to be switched into the appropriate Virtual Private Network (VPN) routing/forwarding (VRF) Selection table based upon the source IP address of the packets. Once the packets have been "selected" into the correct VRF Selection routing table, they are processed normally based upon the destination address and forwarded through the rest of the Multiprotocol Label Switching (MPLS) VPN.
The VRF Selection feature is a "one-way" feature; it works on packets that come from the end users to the provider edge (PE) router.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/vrfs elec.htm
MPLS VPN Carrier Supporting Carrier
The following features appear under this feature heading:
• MPLS VPN Carrier Supporting Carrier
• MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution
• MPLS VPN Carrier Supporting Carrier on Engine 0, Engine 2, and IP Service Engine (ISE) Line Cards
• MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution on Engine 0 and Engine 2 Line Cards
MPLS VPN Carrier Supporting Carrier
Platforms: Cisco 7200 series, Cisco 7500/RSP series
Carrier supporting carrier is a term used to describe a situation where one service provider allows another service provider to use a segment of its backbone network. The service provider that provides the segment of the backbone network to the other provider is called the backbone carrier. The service provider that uses the segment of the backbone network is called the customer carrier.
The Carrier Supporting Carrier (CsC) feature enables an MPLS VPN-based service provider to allow other service providers to use a segment of its backbone network. It provides the following benefits to the backbone carrier and customer carrier:
•The backbone carrier can accommodate many customer carriers and give them access to its backbone. The backbone carrier does not need to create and maintain separate backbones for its customer carriers.
•The MPLS VPN Carrier Supporting Carrier feature is scalable. Carrier supporting carrier can change the Virtual Private Network (VPN) to meet changing bandwidth and connectivity needs.
•The MPLS VPN Carrier Supporting Carrier feature is a flexible solution. The backbone carrier can accommodate many types of customer carriers. The backbone carrier can accept customer carriers who are Internet service providers (ISPs) or VPN service providers or both.
•The MPLS VPN Carrier Supporting Carrier feature removes from the customer carrier the burden of configuring, operating, and maintaining its own backbone.
•Customer carriers who use the VPN services provided by the backbone carrier receive the same level of security that Frame Relay or ATM-based VPNs provide.
•Customer carriers can use any link layer technology (SONET, DSL, Frame Relay, and so on) to connect the customer edge (CE) routers to the provider edge (PE) routers and the PE routers to the Provider (P) routers. The MPLS VPN Carrier Supporting Carrier feature is link layer independent. The CE routers and PE routers use IP to communicate, and the backbone carrier uses MPLS.
•The customer carrier can use any addressing scheme and still be supported by a backbone carrier.
For additional information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/csc2 2.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution feature enables you to configure your carrier supporting carrier network to enable Border Gateway Protocol (BGP) to transport routes and Multiprotocol Label Switching (MPLS) labels between the backbone carrier provider edge (PE) routers and the customer carrier customer edge (CE) routers. The backbone carrier offers BGP and MPLS VPN services. The customer carrier can be either:
•An Internet service provider (ISP) with an IP core
•An MPLS service provider with or without Virtual Private Network (VPN) services
Previously you had to use Label Distribution Protocol (LDP) and an Interior Gateway Protocol (IGP) between PE and CE routers to achieve the same goal. Using BGP to distribute IPv4 routes and MPLS labels routes has the following benefits:
•BGP takes the place of an IGP and LDP. You can use BGP to distribute routes and MPLS labels. Using a single protocol instead of two simplifies the configuration and troubleshooting.
•BGP is the preferred routing protocol for connecting two ISPs, mainly because of its routing policies and ability to scale. ISPs commonly use BGP between two providers. This feature enables those ISPs to use BGP.
This feature is an extension of the MPLS VPN Carrier Supporting Carrier feature. For more information, see the Cisco document MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fscs c22.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN Carrier Supporting Carrier on Engine 0, Engine 2, and IP Service Engine (ISE) Line Cards
Platform: Cisco 12000 series
The Carrier Supporting Carrier (CsC) feature enables an MPLS VPN-based service provider to allow other service providers to use a segment of its backbone network. The backbone network provides Border Gateway Protocol (BGP) and Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) services to a customer carrier network.
Cisco 12000 series Engine 0, Engine 2, and IP Services Engine (ISE) (also referred to as Engine 3) line cards are used in the backbone support MPLS label distribution between the service provider's backbone network and a customer carrier network using Label Distribution Protocol (LDP).
Engine 2 Packet-over-SONET (POS) line cards in Cisco 12000 series Internet routers that support CsC include the following:
•8-port OC-3 POS edge line card
•16-port OC-3 POS edge line card
•4-port OC-12 POS edge line card
•1-port OC-48 POS core line card
For more information about MPLS VPN Carrier Supporting Carrier (without labels), see the "MPLS VPN Carrier Supporting Carrier" section or see the Cisco document at following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/csc2 2.htm
Note Support for the Carrier Supporting Carrier feature on Engine 0 and Engine 2 line cards has been ported from Cisco IOS Release 12.0ST.
MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution on Engine 0 and Engine 2 Line Cards
Platform: Cisco 12000 series
The Carrier Supporting Carrier (CsC) feature enables an MPLS VPN-based service provider to allow other service providers to use a segment of its backbone network. The backbone network provides Border Gateway Protocol (BGP) and Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) services to a customer carrier network.
Cisco 12000 Series Engine 0 and Engine 2 line cards are used in the backbone support MPLS label distribution between the service provider's backbone network and a customer carrier network using BGP.
For more information about MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution (with labels), see the "MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution" section or see the Cisco document at following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fscs c22.htm
MPLS VPN Interautonomous System
The following features appear under this feature heading:
• MPLS VPN—Interautonomous System Support
• MPLS VPN Inter-AS—IPv4 BGP Label Distribution
MPLS VPN—Interautonomous System Support
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 10720 router
The MPLS VPN—Interautonomous System Support feature allows a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) to span service providers and autonomous systems.
As VPNs grow, their requirements expand. In some cases, VPNs need to reside on different autonomous systems in different geographic areas. (An autonomous system is a single network or group of networks that is controlled by a common system administration group and that uses a single, clearly defined routing protocol.)
Also, some VPNs need to extend across multiple service providers (overlapping VPNs). Regardless of the complexity and location of the VPNs, the connection between autonomous systems must be seamless to the customer.
The MPLS VPN—Interautonomous System Support feature provides that seamless integration of autonomous systems and service providers. Separate autonomous systems from different service providers can communicate by exchanging IPv4 network layer reachability information (NLRI) in the form of VPN-IPv4 addresses.
The border edge routers of the autonomous systems use Exterior Border Gateway Protocol (EBGP) to exchange that information. Then, an Interior Gateway Protocol (IGP) distributes the network layer information for VPN-IPv4 prefixes throughout each VPN and each autonomous system. Routing information uses the following protocols:
•Within an autonomous system, routing information is shared using an IGP.
•Between autonomous systems, routing information is shared using an EBGP. An EBGP allows a service provider to set up an interdomain routing system that guarantees the loop-free exchange of routing information between separate autonomous systems.
The MPLS VPN Interautonomous System Support feature allows a service provider to provide to customers scalable Layer 3 VPN services, such as web hosting, application hosting, interactive learning, electronic commerce, and telephony service. A VPN service provider supplies a secure, IP-based network that shares resources on one or more physical networks.
The primary function of a EBGP is to exchange network reachability information between autonomous systems, including information about the list of autonomous system routes. The autonomous systems use EBGP border edge routers to distribute the routes, which include label switching information. Each border edge router rewrites the next-hop and MPLS labels.
Note A VPN-IPv4 EBGP session must be configured between directly connected autonomous system boundary routers (ASBRs). Multihop VPN-IPv4 EBGP is not supported.
Interautonomous system configurations supported in an MPLS VPN can include:
•Interprovider VPN—MPLS VPNs that include two or more autonomous systems, connected by separate border edge routers. The autonomous systems exchange routes using EBGP. No IGP or routing information is exchanged between the autonomous systems.
•BGP confederations—MPLS VPNs that divide a single autonomous system into multiple subautonomous systems and classify them as a single, designated confederation. The network recognizes the confederation as a single autonomous system. The peers in the different autonomous systems communicate over EBGP sessions; however, they can exchange route information as if they were Internal Border Gateway Protocol (IBGP) peers.
Note This feature has been ported from Cisco IOS Release 12.0ST. Support for the Cisco 10720 Internet router has been added in Cisco IOS Release 12.0(22)S.
For more information about the MPLS VPN—Interautonomous System Support feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fsias 22.htm
MPLS VPN Inter-AS—IPv4 BGP Label Distribution
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The MPLS VPN Inter-AS—IPv4 BGP Label Distribution feature enables you to set up a Virtual Private Network (VPN) service provider (SP) network to exchange IPv4 routes with Multiprotocol Label Switching (MPLS) labels. You can configure the VPN service provider network as follows:
•Route reflectors (RRs) exchange Virtual Private Network version 4 (VPNv4) routes, using multihop, multiprotocol External Border Gateway Protocol (EBGP). This configuration also preserves the next hop information and the VPN labels across the autonomous systems.
•A local provider edge (PE) router needs to know the routes and label information for the remote PE router. This information can be exchanged between the PE routers and autonomous system boundary routers (ASBRs) in one of two ways:
–Interior Gateway Protocol (IGP) and Label Distribution Protocol (LDP): The ASBR can redistribute the IPv4 routes and MPLS labels it learned from EBGP into IGP and LDP and vice versa.
–Internal Border Gateway Protocol (IBGP) IPv4 label distribution: The ASBR and PE router can use direct IBGP sessions to exchange VPNv4 and IPv4 routes and MPLS labels.
Alternatively, the route reflector can reflect the IPv4 routes and MPLS labels learned from the ASBR to the PE routers in the VPN. This is accomplished by enabling the ASBR to exchange IPv4 routes and MPLS labels with the route reflector. The route reflector also reflects the VPNv4 routes to the PE routers in the VPN (as mentioned in the first bullet). For example, in VPN1, RR1 reflects to PE1 the VPNv4 routes it learned and the IPv4 routes and MPLS labels learned from ASBR1. Using the route reflectors to store the VPNv4 routes and forward them through the PE routers and ASBRs allows for a scalable configuration.
•ASBRs exchange IPv4 routes and MPLS labels for the PE routers, using EBGP.
Using BGP to distribute IPv4 routes and MPLS labels routes has the following benefits:
•Results in improved scalability because the route reflectors store VPNv4 routes.
•Enables a non-VPN core network to act as a transit network for VPN traffic.
•Eliminates the need for any other label distribution protocol between adjacent LSRs.
For more information, see the Cisco document MPLS VPN Inter-AS—IPv4 BGP Label Distribution at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fsias l22.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
MPLS VPN—Interautonomous Systems Support on Engine 0, Engine 2, and IP Service Engine (ISE) Line Cards
Platform: Cisco 12000 series
The MPLS VPN—Interautonomous Systems Support feature allows a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) to span service providers and autonomous systems. In some cases, VPNs need to reside on different autonomous systems in different geographic areas. (An autonomous system is a single network or group of networks that is controlled by a common system administration group and that uses a single, clearly defined routing protocol.) Also, some VPNs need to extend across multiple service providers (overlapping VPNs).
The MPLS VPN—Interautonomous Systems Support feature provides seamless integration of autonomous systems and service providers. Separate autonomous systems from different service providers can communicate by exchanging IPv4 network layer reachability information (NLRI) in the form of VPN-IPv4 addresses. The autonomous systems boundary routers (ASBRs) use the Exterior Border Gateway Protocol (EBGP) to exchange that information. Then, an Interior Gateway Protocol (IGP) distributes the network layer information for VPN-IPv4 prefixes throughout each VPN and each autonomous system.
Support for Cisco 12000 series Engine 0, Engine 2, and IP Services Engine (ISE) (also referred to as Engine 3) line cards for this feature was added to Cisco IOS Release 12.0(22)S. Engine 2 Packet-over-SONET (POS) line cards in Cisco 12000 series Internet routers that support the MPLS VPN—Interautonomous Systems Support feature include the following:
•8-port OC-3 POS edge line card
•16-port OC-3 POS edge line card
•4-port OC-12 POS edge line card
•1-port OC-48 POS core line card
For more information about the MPLS VPN—Interautonomous Systems Support feature (without labels), see the "MPLS VPN—Interautonomous System Support" section or see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fsias 22.htm
Note Support for the MPLS VPN—Interautonomous Systems Support feature on Engine 0 and Engine 2 line cards has been ported from Cisco IOS Release 12.0ST.
MPLS VPN Inter-AS—IPv4 BGP Label Distribution on Engine 0, Engine 2, and IP Service Engine (ISE) Line Cards
Platform: Cisco 12000 series
The MPLS VPN Inter-AS—IPv4 BGP Label Distribution feature enables you to set up a Virtual Private Network (VPN) service provider network so that the ASBRs exchange IPv4 routes with Multiprotocol Label Switching (MPLS) labels of the provider edge (PE) routers. Route reflectors (RRs) exchange Virtual Private Network version 4 (VPNv4) routes, using multihop, multiprotocol External Border Gateway Protocol (EBGP). This configuration saves the autonomous system boundary routers (ASBRs) from having to store all the VPNv4 routes. Using the route reflectors to store the VPNv4 routes and forward them to the PE routers results in improved scalability.
Support for Cisco 12000 series Engine 0, Engine 2, and IP Services Engine (ISE) (also referred to as Engine 3) line cards for this feature was added to Cisco IOS Release 12.0(22)S.
For more information about MPLS VPN Inter-AS—IPv4 BGP Label Distribution (with labels), see the "MPLS VPN Inter-AS—IPv4 BGP Label Distribution" section or see the Cisco document at following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/fsias l22.htm
Multicast Forwarding on IP Services Engine Line Cards
Platform: Cisco 12000 series
Cisco IOS Release 12.0(21)S introduced the Multicast Forwarding feature on Cisco 12000 series Engine 2 POS and Ethernet line cards. Cisco IOS Release 12.0(22)S introduces hardware engine-based multicast forwarding on the following Cisco 12000 series IP Services Engine (ISE) line cards (also referred to as Engine 3 line cards):
•1-port Channelized OC-48/STM-16 (DS3/E3, OC-3c/STM-1c) POS/SDH, OC-12c/STM-4c
•4-port OC-12c/STM-4c POS/SDH
•4-port Channelized OC-12/STM-4 (DS3/E3, OC-3c/STM-1c) POS/SDH
•16-port OC-3c/STM-1c POS/SDH
•16-port Channelized OC-3/STM-1 (DS3/E3) POS/SDH
Note On Cisco 12000 series ISE line cards, IP multicast forwarding does not support label-switched paths (LSPs). Multicast traffic cannot be routed over LSPs in the hardware engine.
For more information about the Multicast Forwarding feature in Cisco 12000 series Internet routers, see the "Multicast Forwarding in Cisco 12000 Series Internet Routers" section.
Multiplex Section Protection (MSP)
Platform: Cisco 10000 series
This feature adds support for Multiplex Section Protection (MSP) redundancy for the 4-port channelized STM-1 line card (ESR-4OC3-CHSTM1) for the Cisco 10000 router (ESR10008 and ESR10005). This feature provides linear, nonrevertive, 1+1 protection on a per-port basis. MSP support requires two ESR-4OC3-CHSTM1 line cards.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Multiprotocol BGP (MP-BGP)—MPLS VPN
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series,
Multiprotocol BGP (MP-BGP) provides extensions to BGP-4 as specified in IETF RFC 2283, Multiprotocol Extensions for BGP-4. T. Bates, R. Chandra, D. Katz, and Y. Rekhter. February 1998. (Format: TXT=18946 bytes) (Status: PROPOSED STANDARD).
These extensions enable MBGP to carry different address families. In Cisco IOS Release 12.0(22)S, Multicast Border Gateway Protocol (MBGP) supports the distribution of multicast and Multiprotocol Label Switching (MPLS) virtual private network (VPN) routes.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Multi-VPN Routing and Forwarding Tables
Platform: Cisco 10720 router
The Multi-VPN Routing and Forwarding Tables feature (also referred to as Multi-VRF) extends limited provider edge (PE) router functionality to a customer edge (CE) router in an Multiprotocol Label Switching (MPLS) virtual private network (VPN) configuration. When used as a CE router, the Cisco 10720 Internet router can now maintain separate VPN routing and forwarding (VRF) tables in order to extend the privacy and security of an MPLS VPN down to a branch office instead of only to the PE router node.
The Cisco 10720 Internet router supports up to:
•999 VRF entries for static routes
•200 VRF entries that use the Border Gateway Protocol (BGP) to distribute VPN routing information
•30 VRF entries that use the Open Shortest Path First (OSPF) protocol to distribute VPN routing information
For more information about the Multi-VRF feature for CE routers, see the Cisco document at the following location:
http://www.cisco.com/warp/public/cc/pd/rt/2600/prodlit/1575_pp.htm
NetFlow Accounting
Platform: Cisco 10000 series
The NetFlow Accounting feature supports gathering and exporting Version 5 and Version 8 record types to NetFlow FlowCollectors, and provides basic metering for a key set of applications, including network traffic accounting, usage-based network billing, network planning, and network monitoring capabilities.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Nested Policies
Platform: Cisco 10000 series
A nested policy allows multiple classes and subclasses of IP traffic to be shaped at a single rate. This feature provides the following benefits:
•Allows traffic from multiple queues to be shaped at a single rate, which provides a way to implement fair queues on virtual circuits.
•Enables you to shape the aggregate traffic of fair queues on a physical interface (for example, to provide a 10-Mbps service on a 100-Mbps physical interface).
•Enables you to specify the maximum transmission rate for traffic that is queued separately.
•Enables a single class of traffic to be divided into one or more subclasses.
•Can be applied to physical interfaces and to logical interfaces such as Frame Relay or VLAN interfaces.
To use the Nested Policies feature on the Cisco 10000 series edge services router, the following prerequisites must be met:
•The chassis must have a Performance Routing Engine (PRE) (classic) or PRE1 installed.
•You must have privileged mode access to configure or modify nested policies.
For more information about nested policies, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/nest_pol.htm
New and Enhanced PXF Commands
Platform: Cisco 10000 series
Several changes were made to Parallel eXpress Forwarding (PXF) commands on the Cisco 10000 series edge services router:
•New show hardware pxf keywords display PXF counters and statistics that can also be cleared. The statistics are a subset of the information displayed by commands such as show hardware pxf cpu queue, show hardware pxf cpu statistics drop, and show hardware pxf dma.
•New clear pxf commands enable you to clear PXF counters and statistics.
•The output of the show hardware pxf cpu cef command was modified to display the new format of the Mtrie structure, which was updated to support a larger routing table.
For more information about New and Enhanced PXF Commands, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/pxf_cmds.htm
OSPF Sham-Link Support for MPLS VPN
Platform: Cisco 10000 series, Cisco 12000 series
In a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) configuration, the Open Shortest Path First (OSPF) protocol is one way you can connect customer edge (CE) routers to service provider edge (PE) routers in the VPN backbone. OSPF is often used by customers that run OSPF as their intrasite routing protocol, subscribe to a VPN service, and want to exchange routing information between their sites using OSPF (during migration or on a permanent basis) over an MPLS VPN backbone.
Using an OSPF sham-link in an MPLS VPN has the following benefits:
•Client site connection across the MPLS VPN backbone: A sham-link overcomes the OSPF default behavior for selecting an intra-area backdoor route between VPN sites instead of an inter-area (PE-to-PE) route. A sham-link ensures that OSPF client sites that share a backdoor link can communicate over the MPLS VPN backbone and participate in VPN services.
•Flexible routing in an MPLS VPN configuration: In an MPLS VPN configuration, the OSPF cost configured with a sham-link allows you to decide if OSPF client site traffic will be routed over a backdoor link or through the VPN backbone.
For further information about OSPF sham-link support for MPLS VPN, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/sha mlink.htm
Note This feature has been ported from Cisco IOS Release 12.0ST. Support for the Cisco 10000 series has been added in Cisco IOS Release 12.0(22)S.
OSPF Support for Multi-VRF on CE Routers
Platform: Cisco 12000 series
The OSPF Support for Multi-VRF on CE Routers feature provides the capability of suppressing provider edge (PE) checks. The checks are needed to prevent loops when the PE is performing a mutual redistribution of packets between Open Shortest Path First (OSPF) and Border Gateway Protocol (BGP). When Virtual Private Network (VPN) routing/forwarding (VRF) is used on a router that is not a PE (that is, one that is not running BGP), the checks can be turned off to allow for correct population of the VRF routing table with routes to IP prefixes.
This feature allows you to split the router into multiple virtual routers, in which each contains its own set of interfaces, routing table, and forwarding table. On the basis of routing information stored in the VRF IP routing table and VRF Cisco Express Forwarding (CEF) table, packets are forwarded to their destination using Multiprotocol Label Switching (MPLS).
This feature gives you the ability to segment or single out parts of your network and configure those segments to perform specific functions, yet still maintain correct routing information.
For further information about the OSPF Support for Multi-VRF on CE Routers feature, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/ospfvrfl.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
Parser Cache
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
The Parser Cache feature optimizes the parsing (translation and execution) of Cisco IOS software configuration command lines by remembering how to parse recently encountered command lines. This feature was developed to improve the scalability of the Cisco IOS software command-line interface (CLI) parser when processing large configuration files. The Parser Cache feature can rapidly recognize and translate configuration lines that differ slightly from previously used configuration lines (for example, pvc 0/100, pvc 0/101, and so on) by dynamically creating, caching, and reusing simplified parse graphs. This improvement is especially useful for configuration files that repeat similar commands hundreds or thousands of times, such as when thousands of virtual circuits must be configured for subinterfaces or when hundreds of access lists must be configured. Cisco testing indicates an improvement to load time of up to 36 percent for large configuration files when using the Parser Cache feature. Performance will increase the most for those files in which the same commands are used repeatedly but the numerical arguments change from command to command. The Parser Cache feature is enabled by default.
For more information about configuring the Parser Cache feature, see the Cisco document at the following location:
http://www.Cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dt5parse.htm
Performance Route Processor
Platform: Cisco 12000 series
The Performance Route Processor (PRP) in the Cisco 12000 series Internet router is designed to meet the growing demands in the high-end IP routing market due to increased Internet traffic, larger routing tables, acceptance of IP as the common networking layer protocol, and an increasing shift in focus by service providers to IP infrastructures.
The PRP satisfies these demands by providing an evolution from the current Gigabit Route Processor (GRP) card with a faster processor, multilayer cache, improved fabric interface for faster communication between PRP and line cards, and larger memory capacity.
The PRP is designed to support all Cisco IOS software features that are supported on the GRP. Certain exceptions apply regarding the High Availability. These features are Nonstop Forwarding (NSF) and Stateful Switchover (SSO) for standard routing protocols. These features are being targeted for Cisco IOS Release 12.0(23)S and later releases. However, in Cisco IOS Release 12.0(22)S, the PRP is NSF aware, meaning that it runs NSF software and can maintain session information with a peer device following a switchover of the peer device
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/prp. htm
For more information on installing and configuring the Performance Route Processor, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/cis12012/fru/13302prp.htm
Per-Packet Load Balancing
Platform: Cisco 10000 series
Per-Packet Load Balancing (PPLB) ensures load balancing over multiple links by allowing the router to send successive data packets over paths without regard to individual hosts or user sessions. PPLB uses a round-robin method to determine which path each packet takes to arrive at the destination.
Note This feature has been ported from Cisco IOS Release 12.0ST.
PIM: Subsecond DR Failover
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The Subsecond DR Failover feature is an enhancement to Protocol Independent Multicast (PIM) that allows faster convergence (in the range of subseconds) when designated router (DR) failure occurs.
Policy-Based Routing
The following features appear under this feature heading:
• Policy-Based Routing on Engine 4 Plus Line Cards
• Policy Routing onto MPLS TE Tunnels
Policy-Based Routing (PBR)
Platform: Cisco 10000 series
Policy-Based Routing (PBR) provides a tool for expressing and implementing the forwarding or routing of data packets on the basis of the policies that are defined by network administrators. PBR allows policy override on routing protocol decisions by selectively applying policies based on either access list or packet size or both. Network administrators can also use PBR to selectively change the IP ToS, IP precedence, and IP QoS Group fields for matching incoming packets on an interface.
The Cisco 10000 series edge services router supports a maximum of 255 PBR policies and 32 route maps within each policy. The following subset of policy-based routing commands is supported in this release of Cisco IOS software:
•ip policy route-map map-tag
•route-map map-tag [permit | deny] [sequence-number]
•match ip address {ACL-number | ACL-name} [ACL-number | ACL-name ...]
•match length min max
•set [default] interface type number [type number ...]
•set ip [default] next-hop ip-address [ip-address ...]
•set ip precedence value
•set ip qos-group value
•set ip tos value
•show route-map [map-tag]
Note This feature has been ported from Cisco IOS Release 12.0ST.
Policy-Based Routing on Engine 4 Plus Line Cards
Platform: Cisco 12000 series
Policy-based routing is supported on Cisco 12000 series Engine 4 Plus line cards, including the following:
•4-port OC-48c/STM-16c POS/SDH
•1-port OC-192c/STM-64c POS/SDH
By using policy-based routing, you can implement policies that selectively cause packets to take different paths.
On Cisco 12000 series Engine 4 Plus line cards, policy routing with committed access rate (CAR) provides a mechanism to mark packets so that certain kinds of traffic receive differentiated, preferential service when used in combination with queueing techniques enabled through the Cisco IOS software. These queueing techniques provide an extremely powerful, simple, and flexible tool for network managers who implement routing policies in their networks.
For information about how to configure policy-based routing, see the "Configuring Policy-Based Routing" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide, "Release 12.0", at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/qos_c/qcpart1/qcpolicy.htm
Policy Routing onto MPLS TE Tunnels
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Cisco IOS Release 12.0(22)S supports mapping packets to tunnels. see the following Cisco document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/np1_c/1cprt1/1cindep.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
Post Switchover Core Dump
Platform: Cisco 10000 series
When a Route Processor (RP) reloads unexpectedly, it is sometimes useful to obtain a full copy of the memory image (called a core dump) to identify the cause of the reload. (Not all reload types produce a core dump.)
In networking devices that support redundant RPs, one processor acts as the active processor while the other processor acts as the standby processor. In the event of a reload, the standby processor switches over to become the active processor. The Post Switchover Core Dump feature allows the newly active processor to complete the switchover process before writing the core dump information from the previously active processor to a preconfigured file.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Privilege Command Enhancements
Platform: Cisco 12000 series
This feature simplifies the configuration of privilege levels for specific commands through the enhancement of the "privilege level" global configuration command. A privilege level can now be specified for all keyword options of a command with a single command-line interface (CLI) command. Previously, separate "privilege level" commands were required for each keyword combination of a command. This enhancement can significantly reduce the number of commands needed to configure user privilege levels and correspondingly reduce the size of configuration files.
Reserve Memory for Console Access
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
When a router is low on memory or heavily fragmented, console access is not allowed. This feature implements memory reserve sufficient to allow login via the console. This gives administrators the ability to log in to the router in any situation and perform administrative tasks and troubleshooting even when the router is running low on memory.
Routing Table Improvements
Platform: Cisco 10000 series
Cisco IOS Release 12.0(22)S increases the number of routes allowed in the routing table of the Cisco 10000 series edge services (ESR) router to the following approximate values:
•450,000 global routes
•230,000 MPLS/VPN routes
It is hard to specify the exact number of routes allowed in the routing table because the distribution of IP addresses affects the routing table storage capacity. Routes are stored in the Mtrie structure, which is part of the IP lookup algorithm used in Cisco Express Forwarding (CEF). Routes with a similar IP address (those that share an IP address prefix) take up less space in the Mtrie structure than routes with dissimilar addresses. This means that the structure can hold more routes if the routes share a similar IP address.
To accommodate the increased size of the routing table, the following changes have been made:
•The Mtrie structure has been modified as follows:
–New Level4 nodes have been added.
–Additional Level1, Level2, and Level3 nodes have been added.
–The structure format is now 12-8-4-4-4 instead of 10-9-5-8.
•Output of the show hardware pxf cpu cef command has been modified to accommodate changes to the Mtrie structure. For additional restrictions and limitations on creating nested policies, see the "Displaying PXF Memory Usage" section of the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/pxf_cmds.htm
•The Forwarding Information Base (FIB) and the Tag Forwarding Information Base (TFIB) have been enhanced as follows:
–More memory has been allocated to the FIB.
–Loadinfo nodes are allocated only for interfaces on which load balancing is enabled.
–TagRewrite, Leaf, and Adjacency data structure counts have been increased.
–The TFIB label range has been increased from 204,800 to 512,000.
Priority Queueing (PQ)/CBWFQ on ATM PVCs
Platform: Cisco 10000 series
Priority Queueing (PQ)/CBWFQ on ATM PVCs allows a service policy, including class queue policy statements, to be attached to ATM variable bit rate (VBR) virtual circuits (VCs). This feature is enabled using the Modular Quality of Service Command-Line Interface (MQC) syntax.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Route Processor Redundancy
The following features appear under this feature heading:
• Route Processor Redundancy Plus (RPR+)
• RPR+ in the Cisco 12000 Series Internet Router
Route Processor Redundancy
Platform: Cisco 7500/RSP series
Route Processor Redundancy (RPR) provides an alternative to the High System Availability (HSA) feature currently available on Cisco 7500 series routers. HSA enables a system to reset and use a standby Route Switch Processor (RSP) if the active RSP fails.
Using RPR you can reduce unplanned downtime. RPR enables a quicker switchover between a primary and secondary RSP in the event of a fatal error on the active RSP. When you configure RPR, the standby RSP loads a Cisco IOS image on bootup and initializes itself in standby mode. In the event of a fatal error on the active RSP, the system switches to the standby RSP, which reinitializes itself as the active RSP, reloads all of the line cards, and restarts the system.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Route Processor Redundancy Plus (RPR+)
Platform: Cisco 7500/RSP series
The Route Processor Redundancy Plus (RPR+) feature is an enhancement to the RPR feature on Cisco 7500 series routers. RPR+ keeps the Virtual Interface Processors (VIPs) from being reset and reloaded when a switchover occurs between the active and standby Route Switch Processors (RSPs). Because VIPs are not reset, microcode is not reloaded on the VIPs, the time needed to parse the configuration is eliminated, and switchover time is reduced to 30 to 40 seconds.
Note This feature has been ported from Cisco IOS Release 12.0ST.
RPR+ in the Cisco 12000 Series Internet Router
Platform: Cisco 12000 series
When two Route Processors (RPs) are installed in a Cisco 12000 series Internet router chassis, one RP acts as the active RP, and the other acts as a backup, or standby RP. If the active RP fails or is removed from the system, the standby RP detects the failure and initiates a switchover. During a switchover, the standby RP assumes control of the router, connects with the network interfaces, and activates the local network management interface and system console.
With Route Processor Redundancy Plus (RPR+), the standby RP is fully initialized and configured. This feature allows RPR+ to dramatically shorten the switchover time if the active RP fails or if a manual switchover is performed. Because both the startup configuration and the running configuration are continually synchronized from the active to the standby RP, line cards are not reset during a switchover. The interfaces remain up during this transfer, so neighboring routers do not detect a link flap (that is, the link does not go down and back up).
Supported Line Cards
In Cisco IOS Release 12.0(22)S, RPR+ is supported in the following line cards with the Cisco 12000 series Internet routers:
•All Engine 0, Engine 2, and Engine 4 Packet over SONET (POS) line cards
•All non-channelized DS3 and E3 line cards.
•All Engine 1 and Engine 2 Dynamic Packet Transport (DPT)/Spatial Reuse Protocol (SRP) line cards
•All Engine 0 channelized line cards
•All Engine 0 and Engine 2 Gigabit Ethernet (GE) line cards
•Engine 1 1-port GE line cards
•Engine 1 8-port Fast Ethernet line cards
•Engine 4 10-port 1-GE line cards
All other line cards (that is, ATM and Engine 3 line cards) are reset and reloaded during a RPR+ switchover.
see the following Cisco document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st17/rpr _plus.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
Single Ring Recovery (SRR) Protocol on the Cisco 10720 Internet Router
Platform: Cisco 10720
The Single Ring Recovery (SRR) Protocol enables a spatial reuse protocol (SRP) ring to preserve full node connectivity in the event of multiple failures on one of its two counter-rotating rings while the other is failure free. In all other cases, the SRP ring maintains the standard SRP intelligent protection switching (IPS) behavior. see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s16/srr.h tm
Note As of Cisco IOS Release 12.0(16)S, the SRR protocol has been supported on the Cisco 12000 series routers in OC-48 networks. Cisco IOS Release 12.0(21)S adds support for the SRR protocol on Cisco 7200, Cisco 7500, and Cisco 12000 series routers in OC-12 networks.
Note This feature has been ported from Cisco IOS Release 12.0ST.
SNMP Notification Logging
Platform: Cisco 12000 series
This feature implements support for the Notification Log MIB (defined in RFC 3014) in Cisco IOS software.
Systems that support SNMP often need a mechanism for recording notification information as a hedge against lost notifications, whether those are traps or informs that exceed retransmission limits. The Notification Log MIB provides a common infrastructure for other MIBs in the form of a local logging function. The SNMP Notification Logging feature adds Cisco IOS Command Line Interface (CLI) commands to change the size of the notification log, to set the global ageout value for the log, and to display logging summaries at the command line.
SNMP Support for Class Based QoS on Cisco 12000 Series Line Cards
Platform: Cisco 12000 series
This feature adds Simple Network Management Protocol (SNMP) monitoring support to the Engine 2, Engine 3, Engine 4, and Engine 4 plus (E4+) Cisco 12000 series line cards for Quality of Service (QoS). QoS is configured on Cisco devices using the Modular QoS CLI (MQC). E4+ line cards now support MQC configuration. The managed objects for QoS are defined in the Cisco Class-Based Quality of Service MIB (CISCO-CLASS-BASED-QOS-MIB.my). This MIB provides read access to QoS configurations and provides QoS statistics information based on the MQC, including information regarding class map and policy map parameters.
For details on the MQC, see the document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5/mq c/mcli.htm
For details on management options, see the CISCO-CLASS-BASED-QOS-MIB.my file, available through the Cisco MIB FTP site at the following location:
ftp://ftp.cisco.com/pub/mibs/v2/
SNMP Version 3
Platforms: Cisco 10000 series, Cisco 10720
Note The SNMP Version 3 feature was introduced in Cisco IOS Release 12.0(6)S on the Cisco 7200 series, Cisco 7500 series, and Cisco 12000 series routers. This release is porting the feature into the Cisco 10000 series routers and the Cisco 10720 router.
Simple Network Management Protocol version 3 (SNMPv3) addresses issues related to the large-scale deployment of SNMP for configuration, accounting, and fault management. Currently SNMP is predominantly used for monitoring and performance management. The primary goal of SNMPv3 is to define a secure version of the SNMP protocol. SNMPv3 also facilitates remote configuration of the SNMP entities that make remote administration of SNMP entities a much simpler task. SNMPv3 builds on top of SNMPv1 and SNMPv2 to provide a secure environment for the management of systems and networks.
SNMPv3 provides an identification strategy for SNMP devices to facilitate communication only between known SNMP strategies. Each SNMP device has an identifier called the SNMP EngineID, which is a copy of SNMP. Each SNMP message contains an SNMP EngineID. SNMP communication is possible only if an SNMP entity knows the identity of its peer SNMP device.
SNMPv3 also contains a security model or security strategy that exists between an SNMP user and the SNMP group to which the user belongs. A security model may define the security policy within an administrative domain or an intranet. The SNMPv3 protocol consists of the specification for the User-based Security Model (USM).
Definitions of security goals in which the goals of message authentication service include the following protection strategies:
•Modification of information, or protection against some unauthorized SNMP entity that alters in-transit SNMP messages generated on behalf of an authorized principal.
•Masquerade, or protection against attempting management operations not authorized for some principal by assuming the identity of another principal that has the appropriate authorizations.
•Message stream modification, or protection against messages getting maliciously reordered, delayed, or replayed in order to effect unauthorized management operations.
•Disclosure, or protection against eavesdropping on the exchanges between SNMP engines. Three different types of communication mechanisms are available for this protection strategy:
–Communication without authentication and privacy (NoAuthNoPriv)
–Communication with authentication and without privacy (AuthNoPriv)
–Communication with authentication and privacy (AuthPriv)
For further information about SNMP version 3, see the Cisco document SNMPv3 at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/snmp3.htm
Note This feature has been ported from Cisco IOS Release 12.0ST.
SNMPv3 Community MIB Support
Platform: Cisco 12000 series
The SNMPv3 Community MIB Support feature implements support for the SNMP Community MIB (SNMP-COMMUNITY-MIB) module, defined in RFC 2576, in Cisco IOS software.
RFC 2576, "Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework," defines the requirements for interoperability between SNMPv1, SNMPv2c, and SNMPv3. The SNMP Community MIB module defines objects to help support these requirements.
The SNMPv1/v2c Message Processing Model and Security Model require mappings between parameters used in SNMPv1 and SNMPv2c messages and the version independent parameters used in the SNMP architecture. The SNMP Community MIB contains objects for mapping between these community strings and version-independent SNMP message parameters.
The mapped parameters consist of the SNMPv1/v2c community name and the SNMP securityName and contextEngineID/contextName pair. This MIB provides mappings in both directions; that is, a community name may be mapped to a securityName, contextEngineID, and contextName, or the combination of securityName, contextEngineID, and contextName may be mapped to a community name. This MIB also augments the snmpTargetAddrTable with a transport address mask value and a maximum message size value.
For implementation details, see the SNMP-COMMUNITY-MIB.my file, available through Cisco.com at the following location:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
Subinterface Policy Maps
Platform: Cisco 10000 series
The Subinterface Policy Maps feature allows you to use the service-policy command to configure quality of service (QoS) features at the subinterface level in addition to configuring QoS features on main interfaces. The types of subinterfaces supported include Frame Relay, ATM (both unspecified bit rate [UBR] and variable bit rate [VBR]), and 802.1Q VLAN. ATM VBR subinterfaces support all QoS features including queueing. On all other subinterface types, any queueing-related commands in the service policy, such as bandwidth, priority, shape, queue-limit, and random-detect, are ignored.
Note This feature has been ported from Cisco IOS Release 12.0ST.
tunnel mpls traffic-eng autoroute announce Command
Platforms: Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
To instruct the Interior Gateway Protocol (IGP) to use the tunnel in its Shortest Path First (SPF)/next hop calculation (if the tunnel is up), use the tunnel mpls traffic-eng autoroute announce command. To disable this feature, use the no form of this command:
tunnel mpls traffic-eng autoroute announce
no tunnel mpls traffic-eng autoroute announce
Note You cannot use the tunnel mpls traffic-eng autoroute announce command on a Cisco 10000 series edge services router when you have enabled the MPLS Traffic Engineering (TE)—Interarea Tunnels feature.
For more information, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/te120_7t.htm
Note This feature has been ported from Cisco IOS Release 12.0ST. Support for the Cisco 10000 series has been added in Cisco IOS Release 12.0(22)S.
Turbo Quality of Service (QoS)
Platform: Cisco 10000 series
The Turbo Quality of Service (QoS) feature provides more efficient handling of QoS policy maps for quicker packet classification and a QoS solution that scales.
Note This feature has been ported from Cisco IOS Release 12.0ST.
Unicast Reverse Path Forwarding Checking
Platform: Cisco 10000 series
The Cisco 10000 series edge services router (ESR) supports enhancements to the ip verify unicast command to allow unicast Reverse Path Forwarding (uRPF) checks to be made in strict or loose mode:
•Loose mode—Checks that a packet's source IP address is reachable over any interface on the ESR.
•Strict mode—Checks that a packet's source IP address is reachable over the interface on which the packet was received.
Following is the command syntax for enabling and disabling uRPF checks. Use the no form of the command to disable uRPF checks.
ip verify unicast source reachable-via {rx | any} [allow-default] [list]
ip verify unicast reverse-path [ list ]
no ip verify unicast
Syntax Description
For more information about uRPF, see the following Cisco document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_r/fothercr/srfrpf.htm
Unicast Reverse Path Forwarding on Engine 4 Plus Line Cards
Platform: Cisco 12000 series
The forwarding application specific integrated circuit (ASIC) on Cisco 12000 series Engine 4 Plus (E4+) line cards is designed to support the enhanced "loose check" version of unicast Reverse Path Forwarding (uRPF) on the following line cards in Cisco 12000 series Internet routers:
•4-port OC-48c/STM-16c POS/SDH
•1-port OC-192c/STM-64c POS/SDH
uRPF "loose check" provides two key security functions:
•Ensures that the source addresses of packets are in the Global Internet Route Table.
•Allows Internet service providers (ISPs) to perform network-wide source-based black hole filtering on selected source addresses.
Note uRPF was originally designed for IP-only networks, not IP Multiprotocol Label Switching (MPLS) networks. The uRPF implementation on Cisco 12000 series Engine 4 Plus line cards operates only in IP-only networks. If uRPF and MPLS with Tag Forwarding Information Bases (tFIBs) are enabled, uRPF is shut down on all Cisco 12000 series Engine 4 Plus line cards in the router. Other Cisco 12000 series line card engines in the router that can perform uRPF in an IP MPLS topology are not affected.
In an IP-only network configuration, uRPF "loose check" operates normally. ASIC-based forwarding performance and functionality are not affected. However, if you configure MPLS on the router, the Cisco 12000 series software disables uRPF "loose check" on each Engine 4 Plus line card in the router. The order in which the line cards are configured is not taken into account.
If MPLS traffic engineering (TE) is already enabled when you enable uRPF on an Engine 4 Plus interface, a warning message is displayed on the console to notify you that uRPF is disabled. A syslog message is also recorded. If uRPF is already enabled when you enable MPLS TE, uRPF is disabled with the same warning and syslog messages.
When uRPF "loose check" and MPLS are both configured on an Engine 4 Plus interface, the following console error message is displayed:
router(config-if)# ip verify unicast source reachable-via any
router(config-if)# end
SLOT 2:00:04:36: WARNING: POS2/0 uRPF disabled since TFIB operational SLOT 2:00:04:36: WARNING: POS2/0 uRPF disabled since TFIB operational
The uRPF command still remains in the configuration settings.
If you disable MPLS when uRPF "loose check" is still configured, the following message is displayed:
router(config)# no tag ip
SLOT 4:00:06:11: POS4/0 uRPF enabled
For more information about the uRPF "loose check" feature, see the following Cisco publications:
•Configuring Unicast Reverse Path Forwarding, Release 12.1
•Unicast Reverse Path Forwarding Enhancements, Release 12.1
•Unicast Reverse Path Forwarding Commands, Release 12.1
Unicast Reverse Path Forwarding on IP Services Engine (ISE) Line Cards
Platform: Cisco 12000 series
Unicast Reverse Path Forwarding (uRPF) is supported on the following IP Services Engine (ISE) line cards in Cisco 12000 series Internet routers:
•4-port OC-3c/STM-1c POS/SDH ISE
•8-port OC-3c/STM-1c POS/SDH ISE
•16-port OC-3c/STM-1c POS/SDH ISE
•4-port OC-12c/STM-4c POS/SDH ISE
•1-port OC-48c/STM-16c POS/SDH ISE
•16-port Channelized OC-3/STM-1 (DS3/E3) POS/SDH ISE
•4-port Channelized OC-12/STM-4 (DS3/E3, OC-3c/STM-1c) POS/SDH ISE
•1-port Channelized OC-48/STM-16 (DS3/E3, OC-3c/STM-1c) POS/SDH, OC-12c/STM-4c ISE
Note This feature is also supported on subinterfaces on Cisco 12000 Series ISE line cards.
This feature supports only enhanced "loose check" uRPF as documented in the following Cisco publications. It does not support the classic "strict mode" version of uRPF.
•Configuring Unicast Reverse Path Forwarding, Release 12.1
•Unicast Reverse Path Forwarding Enhancements, Release 12.1
•Unicast Reverse Path Forwarding Commands, Release 12.1
•Cisco 7600 Internet Router IOS Commands, Release 12.1 E
Support for "loose check" enhanced uRPF on Cisco 12000 series ISE line cards includes the following command:
ip verify unicast source reachable-via {any} [allow-default] [allow-self-ping]
Where the command syntax is as follows:
source reachable-via: checks that the source address is reachable
any: checks that the source address is reachable on any path
allow-default: checks that the default route matches the source address
allow-self-ping: allows the router to ping itself
To disable uRPF, enter the no ip verify unicast command.
Note The acl option is not supported for the ip verify unicast command in Cisco 12000 series ISE line cards.
Virtual Router Redundancy Protocol (VRRP)
Platform: Cisco 12000 series
There are several ways in which a LAN client can determine which router should be the first hop to a particular remote destination. The client can use a dynamic process or a static configuration. Examples of dynamic router discovery are as follows:
•Proxy ARP—The client uses Address Resolution Protocol (ARP) to get the destination it wants to reach, and a router will respond to the ARP request with its own MAC address.
•Routing protocol—The client listens to dynamic routing protocol updates (for example, from Routing Information Protocol [RIP]) and forms its own routing table.
•IRDP client—The client runs an Internet Control Message Protocol (ICMP) Router Discovery Protocol (IRDP) client.
The drawback to dynamic discovery protocols is that they incur some configuration and processing overhead on the LAN client. Also, in the event of a router failure, the process of switching to another router can be slow.
An alternative to dynamic discovery protocols is to statically configure a default router on the client. This approach simplifies client configuration and processing, but creates a single point of failure. If the default gateway fails, the LAN client is limited to communicating only on the local IP network segment and is cut off from the rest of the network.
The Virtual Router Redundancy Protocol (VRRP) feature can solve the static configuration problem. VRRP enables a group of routers to form a single virtual router. The LAN clients can then be configured with the virtual router as their default gateway. The virtual router, representing a group of routers, is also known as a VRRP group.
VRRP is supported on Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces, and on Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) and VLANs.
Note This feature has been ported from Cisco IOS Release 12.0ST.
VPN-Aware DHCP Relay for Nonoverlapping Addresses
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 10720, Cisco 12000 series
In Cisco IOS Release 12.0(22)S, Dynamic Host Configuration Protocol (DHCP) relay works with Virtual Private Network (VPN) routing/forwarding (VRF) VPNs. The VPN-Aware DHCP Relay for Nonoverlapping Addresses feature requires each VPN to have its own DHCP server.
Note This feature has been ported from Cisco IOS Release 12.0ST.
VPN-Aware PING MIB
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The ping MIB supports Virtual Private Networks (VPNs). An attribute, VrfName, has been added to the ciscoPingEntry in MIBS/CISCO-PING_MIB.my. This attribute allows the provider-edge router to look up the appropriate VPN routing table while sending a ping packet. If this attribute is NULL (default), a ping packet uses the default VPN routing table.
For descriptions of supported MIBs and how to use them, see the Cisco MIB website on Cisco.com at the following location:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Note This feature has been ported from Cisco IOS Release 12.0ST.
VPN Routing/Forwarding (VRF) ARP Entry Support
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The Virtual Private Network (VPN) routing/forwarding (VRF) option in the arp command allows you to configure static Address Resolution Protocol (ARP) entries per VRF.
[no] arp [vrf name] ip-address hardware-address {arpa | sap | smds | snap} [{alias | interfaces}]
The following is output from a configuration example:
Router(config)# arp ?
A.B.C.D IP address of ARP entry
vrf Configure static ARP for a VPN Routing/Forwarding instance
Router(config)# arp vrf V4 ?
A.B.C.D IP address of ARP entry
Router(config)# arp vrf V4 10.1.1.1 0000.0000.0001 arpa
Note This feature has been ported from Cisco IOS Release 12.0ST.
VPN Routing/Forwarding (VRF) CLI Command
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 10000 series, Cisco 12000 series
The Virtual Private Network (VPN) routing/forwarding (VRF) configuration command allows you to enter comments about your VRF configuration.
description description string
no description
The following is output from a configuration example:
Router(config)# ip vrf V4
Router(config-vrf)# ?
IP VPN Routing/Forwarding instance configuration commands:
default Set a command to its defaults
description VRF specific description
exit Exit from VRF configuration mode
export VRF export
import VRF import
maximum Set a limit
no Negate a command or set its defaults
rd Specify Route Distinguisher
route-target Specify Target VPN Extended Communities
Router(config-vrf)# desc
Router(config-vrf)# description ?
LINE Up to 80 characters describing this VRF
Router(config-vrf)# description This Is My 4th VRF ;-)
Router(config-vrf)# end
Router# sh ru | beg V4
ip vrf V4
description This Is My 4th VRF ;-)
rd 1:406
route-target export 1:400
route-target import 1:400
Note This feature has been ported from Cisco IOS Release 12.0ST.
VPN Slow-Path Support on Engine 2 at Deaggregation Point (Between PE-P)
Platform: Cisco 12000 series
You can now have an Engine 2 card in the chassis when you are running Virtual Private Network (VPN).
Note This feature has been ported from Cisco IOS Release 12.0ST.
VRF over FR Subinterfaces
Platform: Cisco 12000 series
Virtual Private Network (VPN) routing/forwarding instances (VRFs) are supported over Frame Relay (FR) subinterfaces on Engine 2 Packet-over-SONET (POS) line cards in Cisco 12000 series Internet routers, including the following:
•8-port OC-3 POS edge line card
•16-port OC-3 POS edge line card
•4-port OC-12 POS edge line card
•1-port OC-48 POS core line card
On an Engine 2 line card interface configured with Frame Relay encapsulation, each subinterface can be associated to either the global Forwarding Information Base (FIB) table or any configured VRF. This association is independent for each Frame Relay subinterface. It is not necessary for all subinterfaces on the same physical interface to belong to the same VRF.
Packets that arrive at an E2 line card interface with Frame Relay encapsulation are processed as follows:
•The Data Link Connection Identifier (DLCI) is extracted from the Frame Relay header.
•The physical port number and DLCI are used together to perform a lookup.
•The result of the lookup is the mtrie root to be used for this DLCI: either the global FIB or a VRF.
Note This feature has been ported from Cisco IOS Release 12.0ST.
VT1.5 for Channelized OC-12 Card
Platform: Cisco 10000 series
The Cisco 10000 series edge services routers support the VT1.5 on the Channelized OC-12 line card through the controller vt command. This enhancement allows the configuration of the virtual tributary (VT) controllers and the T3 controllers on the line card.
A VT controller on a Channelized OC-12 line card is channelized into 28 T1 interfaces by default. The controller vt command can be used to shut down a VT link or to change the settings for a T1 interface.
The VT link can be configured by entering the controller vt command:
controller vt slot/subslot/port.path
Where path is a value from 1 to 12. Each number represents a VT that houses 28 T1 lines.
Example:
Router#
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller vt 1/0/0.1
Router(config-controller)#
Note This feature has been ported from Cisco IOS Release 12.0ST.
New Hardware and Software Features in Cisco IOS Release 12.0(21)S1 to Cisco IOS Release 12.0(21)S8
There are no new hardware or software features in Cisco IOS Release 12.0(21)S1 to Cisco IOS Release 12.0(21)S8.
New Hardware Features in Cisco IOS Release 12.0(21)S
This section describes new and changed features in Cisco IOS Release 12.0(21)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(21)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Note There was no Cisco IOS Release 12.0(20)S: Release 12.0(21)S follows Release 12.0(19)S1.
1-Port OC-48/STM-16 IP Services Engine Line Cards
Platform: Cisco 12000 series
The IP Services Engine (ISE) line cards (also referred to as Engine 3 line cards) for the Cisco 12000 series Internet router provide enhanced Layer 3 capabilities for high-speed customer aggregation, backbone connectivity, and peering solutions. Cisco IOS Release 12.0(21)S introduced the following new ISE line card for the 12000 series Internet routers:
Concatenated 1-Port OC-48/STM-16
The 1-port POS OC-482/STM-16 line card provides the Cisco 12000 series Internet routers with one 2488 Mbps concatenated Packet-over-SONET (POS) interface on a single card.
Channelized 1-Port OC-48/STM-16
The 1-port Channelized OC-48/STM-16 to DS-3/E3 line card supports both SONET and SDH framing and provides DS-3/E3 aggregation for the Cisco 12000 series Internet router. For SDH, both AU-3 and AU-4 mappings are supported. The line card interfaces with the 12000 series Internet router switch fabric and provides one OC-48/STM-16 duplex SC single-mode intermediate reach optical port that can be configured with up to 48 channelized interfaces.
see the following Cisco Systems publications for additional information:
•Cisco IOS Feature Descriptions and Configuration (Concatenated and Channelized Line Cards):
–ISE Line Cards for the Cisco 12000 Series Internet Routers
•Hardware Installation (Concatenated Line Card)
–1-Port POS OC-48/STM-164 with Extended Feature Set Line Card Installation and Configuration
•Hardware Installation (Channelized Line Card)
–1-Port Channelized OC-48/STM-16 to DS-3/E3 Line Card Installation and Configuration
Cisco 12404 Internet Router
Platform: Cisco 12000 series
The Cisco 12404 Internet router is a new member of the Cisco 12000 series of Internet routers. The Cisco 12404 is designed to scale the Internet and enterprise backbones to speeds of OC-3/STM-1 (155 Mbps), OC-12/STM-4 (622 Mbps), OC-48/STM-16 (2.4 Gbps), and OC-192/STM (10 Gbps).
see the following URL for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/index.htm
New Software Features in Cisco IOS Release 12.0(21)S
This section describes new and changed features in Cisco IOS Release 12.0(21)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(21)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Note There was no Cisco IOS Release 12.0(20)S: Release 12.0(21)S follows Release 12.0(19)S1.
Note The Cisco 12000 series images (all gsr- images) have been deferred in Cisco IOS Release 12.0(21)S. For additional information about the deferral and the software solution, please see the "Cisco 12000 Series Images Deferred in Cisco IOS Release 12.0(21)S" section.
10-Port 1-Gigabit Ethernet Line Card Enhancements
Platform: Cisco 12000 series
The 10-Port 1-Gigabit Ethernet line card now supports output committed access rate (CAR) and output access control lists (ACLs).
see the following document for information about CAR:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios111/cc111/car.htm
see the following document for information about the 10-Port 1-Gigabit Ethernet line card:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_enet/12901ge1.htm
ACL Table Optimization for Engine 2 Line Cards
Platform: Cisco 12000 series
Engine 2 line cards store a variety of access control list (ACL) tables in the pointer lookup (PLU) memory. This feature optimizes the table usage in some cases from 4 MB to 16 KB. This optimization can free up to 7.9 MB of memory, allowing for a larger number of prefixes on the router.
ATM OAM Ping
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The ATM OAM Ping feature modifies the ping atm interface atm and ping (privileged) commands, which allow a network administrator to send an Operation, Administration, and Maintenance (OAM) packet to verify permanent virtual circuit (PVC) connectivity. The status of the PVC is displayed when a response to the OAM packet is received. This feature also facilitates ATM network troubleshooting.
The ATM OAM Ping feature supports interactive ping functionality.
This feature provides the following two ATM OAM ping options:
•End loopback—Verifies end-to-end PVC integrity
•Segment loopback—Verifies PVC integrity to the neighboring ATM device
see the following document for command reference and further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/12at mpng.htm
BGP 4 MIB Support for per-Peer Received Routes
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The BGP 4 MIB Support for per-Peer Received Routes feature introduces a new table in the CISCO-BGP4-MIB that provides the capability to query (by using SNMP commands) for routes that are learned from individual BGP peers. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/sbgp rmib.htm
Bit Error Rate Testing for 4-Port Channelized OC-12/STM-4 Line Cards
Platform: Cisco 12000 series
Cisco IOS Release 12.0(21)S adds support for Bit Error Rate Testing (BERT) for 4-port channelized OC-12/STM-4 line cards. BER tests allow you to test cables and diagnose signal problems in the field. You can configure individual T1 channel groups to run an independent BER test. You set one local serial port to BERT mode while the remaining local serial ports continue to transmit and receive normal traffic. The BER test checks communication between the local and the remote ports.
When running a BER test, your system expects to receive the same pattern that it is transmitting. If traffic is not being transmitted or received, create a back-to-back loopback BER test on the link or in the network and send out a predictable stream to ensure that you receive the same data that was transmitted.
To determine if the remote serial port returns the BERT pattern unchanged, you must manually enable network loopback at remote serial port, while you configure a BERT pattern to use in the test at specified time intervals on the local serial port.
You can later display and analyze the total number of error bits transmitted and the total number of bits received on the link. You can retrieve error statistics anytime during the BER test. see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/bert .htm
Bit Error Rate Testing Enhancements for 6-Port Channelized T3 Line Cards
Platform: Cisco 12000 series
The 6-port channelized T3 line cards now support the following bit error rate test (BERT) patterns in addition to 2^11, 2^15, and 2^20 QRSS test patterns:
see the following document for further information about BERT patterns and BER tests on channelized line cards:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/bert .htm
CISCO-ENHANCED-MEMORY-POOL-MIB
Platform: Cisco 12000 series
The CISCO-ENHANCED-MEMORY-POOL-MIB monitors the memory pools of all physical entities (Route Processor [RP] and line cards) on a device. This is a new MIB that is introduced in Cisco IOS Release 12.0(21)S to provide memory pool statistics through SNMP about distributed components, such as line cards and the RP.
see the following document for further information about the CISCO-ENHANCED-MEMORY-POOL-MIB:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
CISCO-ENTITY-FRU-CONTROL-MIB
Platform: Cisco 12000 series
The CISCO-ENTITY-FRU-CONTROL-MIB resides in the ENTITY-MIB.my file and is used to monitor and configure the operational Field Replaceable Units (FRUs) of the system listed in the ENTITY MIB (RFC 2037) entPhysicalTable. The FRUs include assemblies such as power supplies, fans, processor modules, interface modules, and so forth.
see the following document for further information about the CISCO-ENTITY-FRU-CONTROL-MIB:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850r2/rel201/pxm/cscoent.htm
CISCO-PROCESS-MIB Enhancement
Platform: Cisco 12000 series
The CISCO-PROCESS-MIB provides information about CPU and memory utilization per process and CPU utilization for the distributed components of a device.
This MIB was previously implemented on Cisco 12000 series Internet routers to provide information only about memory and CPU utilization in the Route Processor (RP). In Cisco IOS Release 12.0(21)S, the CISCO-PROCESS-MIB is enhanced to provide information through SNMP about memory and CPU utilization on line cards in addition to the RP.
see the following document for further information about the CISCO-PROCESS-MIB:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB
Platform: Cisco 12000 series
The CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB provides a mapping between the VLAN identities of the VLANs that are configured, the physical interface on which the VLANs are configured, and the ifIndex values of the VLAN subinterface.
Engine 4 POS Line Card Enhancements
Platform: Cisco 12000 series
The 1-port OC-192 and Quad OC-48 Packet-over-SONET (POS) line cards now support the following features:
•Access control lists (ACLs) on inbound and outbound interfaces
•NetFlow sampling on inbound and outbound IP flows
•Output rate shaping
To configure NetFlow sampling on the line card, use the enhanced ip route-cache flow sampled command in interface configuration mode:
ip route-cache flow sampled [input | output]
Where input enables NetFlow sampling on inbound IP flows and output enables NetFlow sampling on outbound flows. The default is input.
To further configure NetFlow to sample packets that match the first entry in an access control list, use the enhanced ip netflow-match access-list command in interface the configuration mode:
ip netflow-match access-list {input | output}
Where access-list is the number of an existing ACL; input samples packets on inbound IP traffic; and output samples packets on outbound traffic.
GRE Tunneling
Platform: Cisco 12000 series
The generic routing encapsulation (GRE) Tunneling feature allows you to create a virtual point-to-point link to transmit packets between routers at remote distances over an IP network.
GRE is a standards-based tunneling protocol that can encapsulate a wide variety of protocol packet types inside IP tunnels, creating a virtual point-to-point link to Cisco routers at remote points over an IP network. By connecting multiprotocol subnetworks in a single-protocol backbone environment, IP tunneling using GRE allows network expansion across a single-protocol backbone environment.
Note In Cisco 12000 series Internet routers, only IP over GRE tunneling is supported.
see the following document for further information about the GRE Tunneling feature:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/gre. htm
IF-MIB Enhancements
Platform: Cisco 12000 series
Gigabit Ethernet (GE) and Fast Ethernet (FE) line cards now provide access points for the IF-MIB to allow the collection and reporting of 32-bit and 64-bit broadcast and multicast counters that are specific to GE and FE interfaces.
The following 32-bit broadcast and multicast counters are supported:
•ifInMulticastPkts
•ifInBroadcastPkts
•ifOutMulticastPkts
•ifOutBroadcastPkts
The following 64-bit broadcast and multicast counters are supported:
•ifHCInMulticastPkts
•ifHCInBroadcastPkts
•ifHCOutMulticastPkts
•ifHCOutBroadcastPkts
see the following document for general information about the IF-MIB:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850r2/rel201/pxm/ifmib.htm
Individual SNMP Trap Support
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Individual SNMP Trap Support feature adds the ability to enable or disable SNMP system management notifications (traps) individually. This increases your control over SNMP behaviors and allows you to tailor characteristics to the specific needs of your network. By disabling SNMP trap notifications which are not needed, you can increase the amount of free bandwidth and eliminate unnecessary SNMP processing tasks.
Using the Individual SNMP Trap Support feature, you can specify the authentication-failure, linkup, linkdown, and coldstart SNMP traps. This feature expands the functionality of the snmp-server enable traps snmp command. Prior to the introduction of this feature, all four trap types were enabled or disabled simultaneously by the snmp-server enable traps snmp [authentication] command.
Individual SNMP Trap Support is supported for all versions of SNMP that is supported by Cisco IOS software (SNMPv1, SNMPv2c, and SNMPv3).
see the following document for further information about the Individual SNMP Trap Support feature:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dtitraps.htm
IP Services Engine Line Card Enhancements (1)
Platform: Cisco 12000 series
In addition to extended access control lists (ACLs) and committed access rate (CAR), the new 1-port OC-48/STM-16 ISE line cards that are introduced in Cisco IOS Release 12.0(21)S and the 4-port POS OC-12/STM-4, 16-port POS OC-3/STM-1, and 4-port Channelized OC-12/STM-4 to DS-3/E ISE line cards that were introduced in Cisco IOS Release 12.0(19)S now support the following features on both physical interfaces and subinterfaces:
•Aggregated V8 NetFlow
•Automatic Protection Switching/Multiplex Section Protection (APS/MSP)
•Basic Multiprotocol Label Switching (MPLS)
•Dynamic Provisioning
•IPv4 Multicast
•IPv4 Unicast Forwarding
•Line-rate forwarding with multiple features enabled, including ACL, CAR, NetFlow and Traffic Shaping
•Modular QoS CLI (MQC) Support
•QoS Policy Propagation via Border Gateway Protocol (QPPB)
•Sampled V5 NetFlow
•Traffic Shaping
IP Source Tracker
Platform: Cisco 12000 series
The IP Source Tracker feature allows you to gather information about the traffic flowing to a host that is suspected to be under attack and also allows you to easily trace an attack back to its entry point into the network.
The IP Source Tracker feature provides a uniform, scalable service for tracking Denial of Service (DoS) attacks. Because this feature is supported on Engine 0, 1, 2, and 4 (in future releases, Engine 3) line cards, it allows you to track DoS attacks across your entire network.
The IP source tracker generates all the necessary information in an easy-to-use format to track the network entry point of a Denial of Service (DoS) attack. You also can track multiple IPs at the same time. see the following document for further information about the IP Source Tracker feature:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/ipst. htm
Multicast Forwarding in Cisco 12000 Series Internet Routers
Platform: Cisco 12000 series
The Multicast Forwarding feature on Engine 2 line cards in Cisco 12000 series Internet routers allows the packet switching ASIC (PSA) to forward IPv4 packets instead of having multicast traffic sent to the CPU of a line card for slower path processing.
PSA-based multicast forwarding is supported on the following Cisco 12000 series Engine 2 line cards:
•1-port OC-48c/STM-16c DPT
•1-port OC-48c/STM-16c POS/SDH
•3-port Gigabit Ethernet
•4-port OC-12c/STM-4c POS/SDH
•8-port OC-3c/STM-1c POS/SDH
•16-port OC-3c/STM-1c POS/SDH
Normally IP packets are switched on the CPU of a line card using Multicast Distributed Fast Switching (MDFS). This method reduces the load on the Route Processor (RP) and frees it to perform only router lookups. PSA-based multicast forwarding, however, provides even higher speed switching than MDFS.
Because packet forwarding is performed in the line card PSA hardware, higher forwarding rates are possible. Also, more CPU resources are free to perform other features and control plane processes, such as Cisco Express Forwarding (CEF).
The implementation of the Multicast Forwarding feature on Cisco 12000 series Internet routers is compatible with multicast routing protocols, such as Protocol Independent Multicast dense mode (PIM-DM), PIM sparse mode (PIM-SM), and single source multicast (SSM).
By multicasting IP packets, network applications (such as voice and video distribution) use transport resources efficiently by sending only one copy of the original packet from the data source through a multicast distribution tree to hosts on IP subnetworks.
Note Multicast Distributed Fast Switching (MDFS) is also known as Multicast Distributed Switching (MDS).
see the following document for further information about the Multicast Forwarding feature:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/mca st.htm
Per-Packet Load Balancing on Engine 2 Line Cards
Platform: Cisco 12000 series
The Per-Packet Load Balancing feature allows data traffic to be evenly distributed in an IP network over multiple equal-cost connections. Per-packet load balancing uses round-robin techniques to select the output path without basing the choice on the packet content.
Load Balancing
Load balancing is based on a combination of source and destination packet information; it allows you to optimize resources by distributing traffic over multiple paths for transferring data to a destination. You configure load balancing on outbound interfaces on a per-destination or per-packet basis.
Per-Destination and Per-Packet
Per-destination load balancing allows the router to distribute packets based on the destination address, and uses multiple paths to achieve load sharing. Packets for a given source-destination host pair are guaranteed to take the same path, even if multiple paths are available. For example, given two paths to the same network, all packets for destination1 on that network go over the first path, all packets for destination2 on that network go over the second path, and so on. Per-destination load balancing is enabled by default when you start the Cisco 12000 series Internet router, and is the preferred load balancing for most situations.
Per-packet load balancing allows the router to send successive data packets over paths without regard to individual hosts or user sessions. It uses the round-robin method to determine which path each packet takes to the destination. With per-packet load balancing enabled, the router sends one packet for destination1 over the first path, the second packet for (the same) destination1 over the second path, and so on. Per-packet load balancing ensures balancing over multiple links.
Although path utilization with per-packet load balancing is beneficial, packets for a given pair of source-destination hosts might take different paths. This means that per-packet load balancing can introduce reordering of packets. This load balancing method would be inappropriate for certain types of data traffic (such as voice traffic over IP) that depend on packets arriving at the destination in sequence.
Use per-packet load balancing to ensure that a path for a single source-destination pair does not get overloaded. If the bulk of data passing through parallel links is for a single pair, per-destination load balancing overloads a single link while other links have very little traffic. Enabling per-packet load balancing allows you to use alternate paths to the same busy destination.
Note The Cisco 12000 series Internet router is configured by default to perform per-destination load balancing.
Implementing Per-Packet Load Balancing on Cisco 12000 Series Internet Routers
On most Cisco IOS platforms, you need to separately configure load balancing for a destination IP prefix on each outgoing interface. Outgoing packets are then forwarded to the specified destination using the load balancing method that you configure.
Because of the Cisco 12000 series Internet router's distributed architecture, you configure load balancing on a per line card basis. This means that all traffic passing through the outgoing interfaces of a line card is switched with either per-packet or per-destination load balancing.
Note In the Cisco 12000 series Internet Router, per-packet load balancing is supported only on Engine 2 (E2) line cards.
see the following document for further information about the Per-Packet Load Balancing feature:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/pplb .htm
Sampled NetFlow and 128 ACLs on 3-Port Gigabit Ethernet Line Cards
Platform: Cisco 12000 series
On a Cisco 12000 series Internet router that is running Cisco IOS Release 12.0(21)S or later, the three-port Gigabit Ethernet line card supports Sampled NetFlow and 128 access control lists (ACLs) on input and output interfaces. see the following document for further information about Sampled NetFlow:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/12s_ sanf.htm
Secure Copy
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Secure Copy (SCP) feature provides a secure and authenticated method for copying router configuration or router image files. SCP relies on Secure Shell (SSH), an application and a protocol that provide a secure replacement for the Berkeley r-tools.
The behavior of SCP is similar to that of remote copy (rcp), which comes from the Berkeley r-tools suite, except that it is reliant upon SSH for security. In addition, SCP requires that AAA authorization be configured so the router can determine whether the user has the correct privilege level.
SCP allows a user logged in to Cisco IOS software to copy anything that exists in the Cisco IOS File System (IFS) to and from a router by using the copy command. An authorized administrator may also perform this action from a workstation.
see the following document for further information about SCP:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ftscp.htm
Single Ring Recovery Protocol
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Single Ring Recovery (SRR), an extension to the Spatial Reuse Protocol (SRP) protocol in Dynamic Packet Transport (DPT) rings, is supported in both OC-48 and OC-12 networks. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s16/srr.h tm
Note As of Cisco IOS Release 12.0(16)S, the SRR protocol has been supported on the Cisco 12000 series routers in OC-48 networks. Cisco IOS Release 12.0(21)S adds support for the SRR protocol on Cisco 7200, Cisco 7500, and Cisco 12000 series routers in OC-12 networks.
SNMP IF-MIB Support for VLAN (802.1Q) Subinterfaces
Platform: Cisco 12000 series
The SNMP IF-MIB Support for VLAN (802.1Q) Subinterfaces feature provides support for Simple Network Management Protocol (SNMP) monitoring of 802.1Q (DOT1Q) encapsulated subinterfaces using data stored in the ifTable and ifXTable of the Interfaces MIB (IF-MIB). Prior to this enhancement, the ifTable was not populated for subinterfaces that are defined as trunks having 802.1Q encapsulation.
Restrictions
For the Cisco 12000 series, this feature is supported only for Gigabit Ethernet cards. The Cisco 12000 series does not support SNMP accounting of Inter-Switch Link (ISL) encapsulated subinterfaces. The ifInDiscards, ifInErrors, ifOutDiscards, and ifOutErrors objects are not supported for 802.1Q encapsulated subinterfaces. The ifInNucastPkts and ifOutNUcastPkts objects are deprecated per RFC 2233.
All switched packets (unicast, multicast, and broadcast) on the 3-port Gigabit Ethernet line cards and 10-port 1-Gigabit Ethernet line cards are incremented in the ifTables as unicast packets for the purposes of SNMP accounting. The ifInOctets object is not supported on the 10-port 1-Gigabit Ethernet line card (byte accounting is not supported for switched packets on the 10-port 1-Gigabit Ethernet line card).
Universal Transport Interface on 2-Port Channelized E1/T1 and 6-Port Channelized T3 Line Cards
Platform: Cisco 12000 series
The Universal Transport Interface (UTI) feature is now supported on interfaces and subinterfaces facing the customer network site on 2-port OC-3/STM-1 Channelized E1/T1 and 6-port Channelized T3 line cards.
The UTI feature allows a pair of routers connected via an IP network to provide high-speed transparent Layer 2 connectivity between a pair of interfaces. This functionality can be used to build Layer 2 Virtual Private Networks (VPNs) or to support legacy network migration.
Note UTI is not supported on multilink interfaces on 2-port OC-3/STM-1 Channelized E1/T1 and 6-port Channelized T3 line cards.
see the following document for further information about the UTI:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s18/uti.h tm
UTI VLAN
Platform: Cisco 12000 series
The UTI VLAN feature extends UTI-raw tunneling to VLANs for Cisco 12000 series Internet routers. This feature allows you to configure a UTI tunnel and bind it to an 802.1Q VLAN subinterface provisioned on an Ethernet port in the router. An UTI VLAN is supported on 802.1Q subinterfaces only on 8-port Fast Ethernet, 1-port Gigabit Ethernet (GE), and 3-port GE line cards. The UTI VLAN feature is implemented with a tunnel card. see the following document for further information about the UTI VLAN feature:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s18/uti.h tm
New Hardware and Software Features in Cisco IOS Release 12.0(19)S1 to Cisco IOS Release 12.0(19)S4
There are no new hardware or software features in Cisco IOS Release 12.0(19)S1 to Cisco IOS Release 12.0(19)S4.
New Hardware Features in Cisco IOS Release 12.0(19)S
This section describes new and changed features in Cisco IOS Release 12.0(19)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(19)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
10-Port 1-Gigabit Ethernet Line Card for Cisco 12000 Series Internet Routers
Platform: Cisco 12000 series
The 10-Port 1-Gigabit Ethernet line card, which is designed for high-density and server-aggregation applications, provides the Cisco 12400 series Internet routers with ten optical 802.3 Gigabit Ethernet interfaces on a single line card. These interfaces provide high-speed interconnections to other network devices, such as other Cisco 12000 series Internet routers, or to other routers or Layer 2 or Layer 3 switches that support Gigabit Ethernet interfaces.
IP Services Engine Line Cards for the Cisco 12000 Series Internet Routers
Platform: Cisco 12000 series
The IP Services Engine (ISE) line cards for the Cisco 12000 series Internet router provide enhanced Layer 3 capabilities for high-speed customer aggregation, backbone connectivity, and peering solutions. These line cards are available in both concatenated and channelized versions. The ISE line cards offer the following advantages:
•High-Speed Applications at the Network Edge: The ISE line cards provide a single platform architecture from backbone to edge. Cisco 12000 series routers can be utilized for applications at the edges of the Service Provider network as well as in the Internet core and backbone.
•Reduced Cost of Ownership: The enhanced edge functionality of the ISE line cards significantly decrease up-front procurement costs and life cycle costs.
•Cisco Optical Internet Strategy Enabler: Allows high-speed direct customer aggregation and the rapid shift from DS-3 speed to optical OC-3 or OC-12c speeds building upon Cisco internetworking strategy. OC-48c backbone or peering capability will be available with Cisco IOS Release 12.0(20)S.
•Provides Layer 3 Functionality at High Speeds: The ISE line cards provide the Layer 3 functionality of the Cisco 7500 edge routers at the high speeds of the Cisco 12000 series Internet router.
•Edge Engine Functionality in the Backbone: The ISE line cards provide enhanced functionality in the backbone, such as Extended Access Control Lists (ACLs) and Committed Access Rate (CAR).
The following concatenated line cards are introduced for the 12000 series Internet routers:
Concatenated 4-Port OC-12/STM-4
The 4-port POS OC-12/STM-4 line card provides the Cisco 12000 series Internet routers with four 622 Mbps concatenated Packet-over-SONET (POS) interfaces on a single card.
Concatenated 16-Port OC-3/STM-1
The 16-port POS OC-3/STM-1 line card provides the Cisco 12000 series Internet routers with 16 155 Mbps concatenated POS interfaces on a single card.
The following channelized line card is introduced for the 12000 series Internet routers:
Channelized 4-Port OC-12/STM-4
The 4-port Channelized OC-12/STM-4 to DS-3/E3 line card supports both SONET and SDH framing and provides DS-3/E3 aggregation for the Cisco 12000 series Internet router. For SDH, both AU-3 and AU-4 mappings are supported. The line card interfaces with the 12000 series Internet router switch fabric and provides four OC-12/STM-4 duplex SC single-mode intermediate reach optical ports. Each of these ports can be configured with up to 12 channelized interfaces.
see the following Cisco Systems publications for additional information:
•Cisco IOS Feature Descriptions and Configuration (Concatenated and Channelized Line Cards):
–ISE Line Cards for the Cisco 12000 Series Internet Routers
•Hardware Installation (Concatenated Line Cards)
–4-Port POS OC-12/STM-4 with Extended Feature Set Line Card Installation and Configuration
–16-Port Packet-Over-SONET OC-3/STM-1 with Extended Feature Set Line Card Installation and Configuration
•Hardware Installation (Channelized Line Cards)
–4-Port Channelized OC-12/STM-4 to DS-3/E3 Line Card Installation and Configuration
New Software Features in Cisco IOS Release 12.0(19)S
This section describes new and changed features in Cisco IOS Release 12.0(19)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(19)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Explicit Tracking of Hosts, Groups, and Channels for IGMP Version 3
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Internet Group Management Protocol (IGMP) is used by IP hosts to report their multicast group memberships to neighboring multicast routers. IGMP is available in Versions 1, 2, and 3. IGMP Version 3 (IGMPv3) is supported in Cisco IOS Releases 12.0(15)S, 12.1(5)T, and 12.1(8)E and later releases.
The Explicit Tracking of Hosts, Groups, and Channels for IGMP Version 3 feature enables a multicast router to explicitly track the membership of all multicast hosts in a particular multiaccess network. This enhancement to the Cisco IOS implementation of IGMPv3 enables the router to keep track of each individual host that is joined to a particular group or channel. The main benefits of this feature are that it provides minimal leave latencies, faster channel changing, and improved diagnostics capabilities for IGMP.
NetFlow Multiple Export Destinations
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The NetFlow Multiple Export Destinations feature enables the configuration of multiple destinations of the NetFlow data. With this feature enabled, two identical streams of NetFlow data are sent to the destination host. Currently, the maximum number of export destinations allowed is two.
The NetFlow Multiple Export Destinations feature is available only if NetFlow is configured.
Unicast Reverse Path Forwarding on Engine 2 Line Cards
Platform: Cisco 12000 series
Unicast Reverse Path Forwarding (uRPF) is supported on Engine 2 line cards in the Cisco 12000 series Internet router. uRPF is supported by the following Engine 2 line cards:
•16 Port POS OC-3
•4 Port POS OC-12
•1 Port POS OC-48
Note This feature is not supported on subinterfaces on the Cisco 12000 series Engine 2 line cards.
This feature supports the classic "strict mode" uRPF and enhanced "loose check" version of uRPF as documented in the following Cisco publications:
•Configuring Unicast Reverse Path Forwarding, Release 12.1
•Unicast Reverse Path Forwarding Enhancements, Release 12.1
•Unicast Reverse Path Forwarding Commands, Release 12.1
•Cisco 7600 Internet Router IOS Commands, Release 12.1 E
Engine 2 support for enhanced uRPF includes the following enhanced command:
ip verify unicast source reachable-via {any | rx} [allow-default] [allow-self-ping]
To disable uRPF, enter the command no ip verify unicast.
Note The command ip verify unicast source reachable-via rx allow-default is equivalent to the command ip verify unicast reverse-path used in a previous release of uRPF.
The command syntax description is as follows:
•source reachable-via: to check that the source address is reachable
•any: to check that the source address is reachable on any path
•rx: to check that the source address is reachable on the interface the packet was received
•allow-default: to check that the default route matches the source address
•allow-self-ping: to allow the router to ping itself
Note The acl option is not supported for the ip verify unicast command in Engine 2 line cards.
Universal Transport Interface on Frame Relay Point-to-Point Subinterfaces
Platforms: Cisco 7200, Cisco 7500/RSP, Cisco 12000 series
Universal Transport Interface (UTI) is now supported on Frame Relay point-to-point subinterfaces in Engine 0 and Engine 2 line cards for the Cisco 7000, 7500, and 12000 series routers. see the Cisco Systems publication "Universal Transport Interface (UTI)" for additional information.
New Hardware and Software Features in Cisco IOS Release 12.0(18)S1 to Cisco IOS Release 12.0(18)S7
There are no new hardware or software features in Cisco IOS Release 12.0(18)S1 to Cisco IOS Release 12.0(18)S7.
New Hardware Features in Cisco IOS Release 12.0(18)S
There are no new hardware features in Cisco IOS Release 12.0(18)S.
New Software Features in Cisco IOS Release 12.0(18)S
This section describes new and changed features in Cisco IOS Release 12.0(18)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(18)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Cisco IOS Event Tracer
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Event Tracer feature provides a binary trace facility for troubleshooting Cisco IOS software. This feature gives Cisco service representatives additional insight into the operation of the Cisco IOS software and can be useful in helping to diagnose problems in the unlikely event of an operating system malfunction or, in the case of redundant systems, Route Processor (RP) switchover. This feature is intended for use as a software diagnostic tool and should be configured only under the direction of a Cisco Technical Assistance Center (TAC) representative.
Enhanced Password Security, Phase I
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Using the Enhanced Password Security feature, you can configure MD5 encryption for username passwords. Before the introduction of this feature there were two types of passwords associated with usernames. Type 0 is a clear text password visible to any user that has access to privileged mode on the router. Type 7 is a password with a weak, exclusive-or type encryption. Type 7 passwords can be retrieved from the encrypted text by using publicly available tools.
MD5 encryption is a one-way hash function that makes reversal of an encrypted password impossible, providing strong encryption protection. Using MD5 encryption, you cannot retrieve clear text passwords. MD5 encrypted passwords cannot be used with protocols that require that the clear text password be retrievable, such as Challenge Handshake Authentication Protocol (CHAP).
Use the username secret command to configure a user name and an associated MD5 encrypted secret.
ip pim sparse-mode-register Command
Platform: Cisco 12000 series
The ip pim sparse-mode-register command is available on Cisco 12000 series Internet routers Packet-over-SONET (POS) interfaces on Engine 4 line cards (OC-192 and Quad OC-48), and the command only applies when PIM sparse-mode (for multicast) is enabled. By default, this command is enabled and NVGen'ed, and the router will perform normally. If no ip pim sparse-mode-register is configured, the router will not perform registering for directly connected sources. This action only affects sparse-mode groups but does not affect dense-mode groups or source-specific-mode groups.
It is recommended that you configure no ip pim sparse-mode-register to save memory in hardware-forwarding database of Engine 4 line cards if you do not have directly connected sources, such as typical backbone links.
Output ACLs on Engine 4 Line Cards
Platform: Cisco 12000 series
Engine 4 line cards will no longer shut down when access control lists (ACLs) are configured on other line cards in the same router as the Engine 4 line card, and the ACLs will be applied. This feature works when the Engine 4 line card is the ingress card and the egress card is an Engine 0, Engine 1, or Engine 2 line card.
Turbo ACLs must be enabled for this feature to function properly on Engine 4 line cards. Turbo lists can be enabled by adding the "access-list compiled" line in the configuration. This configuration is an essential requirement for the output ACLs on Engine 4 line cards feature.
Engine 4 ingress line card CPU utilization with this feature alone should generally remain low (4 to 6-percent) while the egress line card's CPU utilization remains quite high (98 to 100-percent).
The following are some performance issues for the output ACLs on Engine 4 line cards feature:
•When both input and output ACLs are configured on the same egress line card interface, the input ACL performance is better, especially in Engine 2 line cards, due to PSA. However, when more than 448 lines of input ACLs are configured, the performance of both input and output ACLs on Engine 2 line cards reaches approximately 140-kpps
•Enabling the ACL logging option will result in a small drop in the performance.
•When output ACLs are configured on the egress line card and packets need to be fragmented, performance drops as the number of fragments increase.
The following are some route issues for the output ACLs on Engine 4 line cards feature:
•When both input and output ACLs are configured, and input ACLs are being processed by the PSA on an Engine 2 line card, there is a likelihood of the egress Engine 2 line card reloading if approximately 130,000 BGP routes are configured. A workaround would be to stop the input PSA ACL processing by adding the no access-list hardware psa command to the configuration. However, this configuration will result in input ACL performance degradation.
•When output ACLs are configured, the BGP convergence time may increase slightly. With approximately 180,000 routes, the convergence time can range from 20 to 25 seconds, and with 200,000 routes, the convergence time can increase to 50 seconds
The following are some miscellaneous issues for the output ACLs on Engine 4 line cards feature:
•When output ACLs that have more than approximately 400 entries are configured, removed, and configured again on an egress line card when traffic matching the entries in the ACL is being forwarded by the router, the egress line card could reload with a loss of fabric pings.
•CPUHOG tracebacks might be observed when more than 2000 output ACL entries are configured that have sequentially incrementing IP addresses and simplified permit/deny statement.
•It has been observed that approximately 300 complex entries in the output ACLs that have randomly assigned IP addresses and TCP/UDP ports numbers and precedence values can be configured.
PIM Scalability Enhancement
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The PIM Scalability Enhancement enhances the Protocol Independent Multicast (PIM) Protocol in Cisco IOS software to a new level of scalability. With the help of this feature, there can be a very large number of multicast groups and users for the edge devices without increasing the CPU utilization of the router.
Sampled NetFlow and 128 ACLs on Engine 2 POS Line Cards
Platform: Cisco 12000 series
Sampled NetFlow and 128 access control lists (ACLs) on the packet switch ASIC (PSA) can now be configured at the same time on Engine 2 Packet-over-SONET (POS) line cards.
see the following document for additional information about Sampled NetFlow:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/12s_ sanf.htm
show idb Command
Platform: Cisco 12000 series Internet routers
The show idb command is available on Cisco12000 series Internet routers. The show idb command displays the list of hardware interface description blocks (IDBs) in the router. The following is an example of the show idb command:
Router#
show idb
Maximum number of IDBs 4096
2014 SW IDBs allocated (2392 bytes each)
13 HW IDBs allocated (5624 bytes each)
HWIDB#1 1 POS1/0 (HW IFINDEX, SONET, Serial)
HWIDB#2 2 POS1/1 (HW IFINDEX, SONET, Serial)
HWIDB#3 3 POS1/2 (HW IFINDEX, SONET, Serial)
HWIDB#4 4 POS1/3 (HW IFINDEX, SONET, Serial)
HWIDB#5 5 POS2/0 (HW IFINDEX, SONET, Serial)
HWIDB#6 6 GigabitEthernet3/0 (HW IFINDEX, Ether)
HWIDB#7 7 GigabitEthernet3/1 (HW IFINDEX, Ether)
HWIDB#8 8 GigabitEthernet3/2 (HW IFINDEX, Ether)
HWIDB#9 9 ATM4/0 (HW IFINDEX, SONET, HW ATM)
HWIDB#10 10 GigabitEthernet5/0 (HW IFINDEX, Ether)
HWIDB#11 11 GigabitEthernet5/1 (HW IFINDEX, Ether)
HWIDB#12 12 GigabitEthernet5/2 (HW IFINDEX, Ether)
HWIDB#13 13 Ethernet0 (HW IFINDEX, Ether)SONET MIB
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The SONET MIB adds the following objects:
•sonetSESthresholdSet: The threshold value set for mapping the SESs to the CVs. This object is implemented as read-only.
•sonetMediumInvalidIntervals: Number of invalid intervals in the interval table.
•sonetMediumLoopbackConfig: The loopback information of the interface. This object is implemented as read-only.
The following objects have been added per interval table:
•sonetSectionIntervalValidData
•sonetLineIntervalValidData
•sonetFarEndLineIntervalValidData
•sonetPathIntervalValidData
•sonetFarEndPathIntervalValidData
•sonetVTIntervalValidData
•sonetFarEndVTIntervalValidData
These objects tell whether the data in that particular interval is valid.
The object sonetMediumCircuitIdentifier is now supported as read-write.
Universal Transport Interface
Platform: Cisco 12000 series
The Universal Transport Interface (UTI) feature allows a pair of routers connected via an IP network to provide high-speed transparent Layer2 connectivity between a pair of interfaces (subinterfaces are not supported in this release). This functionality can be used to build Layer2 Virtual Private Networks (VPNs) or to support legacy network migration. UTI tunnels are available with the basic IP package.
UTI allows service providers to provide a simple to integrate Layer2 VPN model for both internal and external use. Some instances where this is advantageous include the following:
•Where a simple sales and service model is required
•Where internetwork packet leakage must be avoided
•Where the passenger network needs to apply a different routing policy than that provided by the carrier network.
New Hardware and Software Features in Cisco IOS Release 12.0(17)S1 to Cisco IOS Release 12.0(17)S7
There are no new hardware or software features in Cisco IOS Release 12.0(17)S1 to Cisco IOS Release 12.0(17)S7.
New Hardware Features in Cisco IOS Release 12.0(17)S
This section describes new and changed features in Cisco IOS Release 12.0(17)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(17)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
2xCHOC-3/STM1-DS1/E1 Line Card
The 2xCHOC-3/STM1-DS1/E1 line card provides E1/DS1 aggregation for the Cisco 12000 series Internet routers. The 2xCHOC-3/STM1-DS1/E1 line card interfaces with the 12000 series Internet router switch fabric and provides two OC-3/STM-1 duplex SC single-mode intermediate-reach optical interfaces.
When configured for operation in a Synchronous Digital Hierarchy (SDH) environment, each STM-1 port is capable of supporting channelization into either 63 independent E1s through VC-12 ETSI mapping, or 84 J1 (Japanese T1 equivalent) channels through VC-11 ANSI mapping.
When configured for operation in a SONET environment, each OC-3 port is capable of supporting channelization into 84 independent DS1 (VT1.5 mapping or CT3 mapping into STS-1) channels.
Fractional E1 and individual 64-kbps channels can also be configured, up to the limit of 105 channel definitions per STM-1 (35 per TUG-3). Fractional T1 and individual DS0 channels can also be configured, up to the limit of 35 channel definitions per STS-1 (210 per line card).
Each 2xCHOC-3/STM1-DS1/E1 line card supports up to 126 E1s when configured for SDH operation, 168 DS1 connections when configured for SONET operation, or any combination of 64 kbps/DS0, fractional E1/T1, or E1/T1 interface definitions, up to the limit of 210 per line card.
Cisco 12406 Internet Router
Platform: Cisco 12000 series
The Cisco 12406 is a member of the Cisco 12000 series of Internet routers. The Cisco 12406 is aimed at scaling the Internet and enterprise backbones to speeds of OC-3/STM-1 (155 Mbps), OC-12/STM-4 (622 Mbps), OC-48/STM-16 (2.4 Gbps) and OC-192/STM (10 Gbps).
The Cisco 12406 has one Route Processor (RP) and linecard cage. The RP and line card cage has six user-configurable slots that support a combination of five line cards and one RP. Network interfaces reside on the line cards that provide connection between the router's switch fabric and the external networks.
There are two additional card cages and two sets of bays. The additional card cages hold the clock and scheduler cards (CSCs) and the switch fabric cards (SFCs). The two sets of bays hold the alarm cards and the power entry modules.
For more information, see the Cisco documents at the following location:
http://www.cisco.com/en/US/products/hw/routers/ps167/products_installation_guide_book09186a008007d0af.html
New Software Features in Cisco IOS Release 12.0(17)S
This section describes new and changed features in Cisco IOS Release 12.0(17)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(17)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
64-Bit SNMP Counters
Platform: Cisco 12000 series
The 64-bit SNMP counters feature provides 64-bit counter support on Frame Relay interfaces to allow the gathering of statistics through Simple Network Management Protocol (SNMP) for faster interfaces operating at OC-3, OC-12, and OC-48 speeds. This feature was introduced to support the deployment of Cisco 12000 series Internet routers line cards in service provider backbone networks.
A new show command is been introduced to display the 64-bit counters:
show frame-relay pvc [interface] [dlci] [64-bit]
Bit Error Rate Testing for 2-Port Channelized OC-3/STM-1 Line Cards
Platform: Cisco 12000 series
Cisco IOS Release 12.0(17)S adds support for Bit Error Rate Testing (BERT) for 2-port channelized OC-3/STM-1 line cards. BER tests allow you to test cables and diagnose signal problems in the field. You can configure individual T1 channel groups to run an independent BER test. You set one local serial port to BERT mode while the remaining local serial ports continue to transmit and receive normal traffic. The BER test checks communication between the local and the remote ports.
When running a BER test, your system expects to receive the same pattern that it is transmitting. If traffic is not being transmitted or received, create a back-to-back loopback BER test on the link or in the network and send out a predictable stream to ensure that you receive the same data that was transmitted.
To determine if the remote serial port returns the BERT pattern unchanged, you must manually enable network loopback at remote serial port, while you configure a BERT pattern to use in the test at specified time intervals on the local serial port.
You can later display and analyze the total number of error bits transmitted and the total number of bits received on the link. You can retrieve error statistics anytime during the BER test. see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/bert .htm
clear context Command
The clear context command provides the ability to clear the information displayed by the show context commands on the Cisco 12000 series Internet router.
The affected "show" commands are:
•show context slot number
•show context all
•show context summary.
Note The clear context command does not clear output for the show context command when entered with no arguments.
The show context commands display the following information, which is cleared with the clear context command:
•Reason for the system reboot.
•Stack trace.
•Software version.
•The signal number, code, and router uptime information.
•All the register contents at the time of the reload.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s17/cl_c ont.htm
Frame Relay Extended Addressing
Platform: Cisco 12000 series
The Frame Relay Extended Addressing feature implements a 23-bit data-link connection identifier (DLCI) on Network-to-Network Interfaces (NNIs). This 23-bit DLCI supports values between 16 and 8388607. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s17/fr_e a.htm
Frame Relay Traffic Policing
Platform: Cisco 12000 series
The Frame Relay Traffic Policing feature provides a mechanism to rate-limit packets on switched PVCs using a "leaky-bucket" implementation. When enabled, traffic policing prevents traffic congestion by discarding or setting the Discard Eligible (DE) bit on packets that exceed specified traffic parameters. Traffic policing parameters can be specified per DCE interface or per switched PVC, using the map class mechanisms.
The Frame Relay Traffic Policing prevents traffic congestion by treating traffic as either committed or excess. This section describes the parameters used to configure the way data is handled with Frame Relay Traffic Policing.
•Committed traffic is that which fits within the committed burst allowed within a given time interval.
•Excess traffic is traffic which does not fit within the committed burst allowed within a given time interval.
Note Some excess traffic can be configured to be allowed through.
For additional information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s17/frtp_ gsr.htm
MPLS Interface MIB Enhancements
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Cisco IOS Release 12.0(17)S introduces support of MPLS Interface MIB Enhancements.
MPLS Traffic Engineering MIB
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Simple Network Management Protocol (SNMP) agent code operating in conjunction with the MPLS TE MIB enables a standardized, SNMP-based approach to be used in managing the Multiprotocol Label Switching (MPLS) traffic engineering features in Cisco IOS software.
The MPLS TE MIB is based on the IETF draft MIB entitled draft-ietf-mpls-te-mib-05.txt, which includes objects describing features that support MPLS traffic engineering. This IETF draft MIB, which undergoes revisions from time to time, is being evolved toward becoming a standard. Accordingly, the Cisco implementation of the MPLS TE MIB is expected to track the evolution of the IETF draft MIB.
Slight differences between the IETF draft MIB and the implementation of the traffic engineering capabilities within Cisco IOS software require some minor translations between the MPLS TE MIB and the internal data structures of Cisco IOS software. These translations are accomplished by means of the SNMP agent code that is installed and operating on various hosts within the network. This SNMP agent code, running in the background as a low priority process, provides a management interface to Cisco IOS software.
The SNMP objects defined in the MPLS TE MIB can be viewed by any standard SNMP utility. All MPLS TE MIB objects are based on the IETF draft MI, which means that no specific Cisco SNMP application is required to support the functions and operations pertaining to the MPLS TE MIB.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s17/te_m ib17.htm
MPLS Traffic Engineering MIB Traps
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Cisco IOS Release 12.0(17)S introduces support for MPLS Traffic Engineering MIB Traps.
Multilink Frame Relay
Platform: Cisco 12000 series
The Multilink Frame Relay feature introduces functionality based on the Frame Relay Forum's Multilink Frame Relay UNI/NNI Implementation Agreement (FRF.16). This feature provides a cost-effective way to increase bandwidth for particular applications by enabling multiple serial links to be aggregated into a single bundle of bandwidth. Multilink Frame Relay is supported on User-Network Interfaces (UNI) and Network-to-Network Interfaces (NNIs) in Frame Relay networks.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s17/17s_ mfr.htm
Tunnel ToS
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Tunnel ToS feature allows you to configure the ToS and Time-to-Live (TTL) byte values in the encapsulating IP header of tunnel packets for an IP tunnel interface on a router. The Tunnel ToS feature is supported on Cisco Express Forwarding (CEF), fast switching, and process switching forwarding modes. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s17/12s_ tos.htm
New Hardware and Software Features in Cisco IOS Release 12.0(16)S1 to Cisco IOS Release 12.0(16)S10
There are no new hardware or software features in Cisco IOS Release 12.0(16)S1 to Cisco IOS Release 12.0(16)S10.
New Hardware Features in Cisco IOS Release 12.0(16)S
This section describes new and changed features in Cisco IOS Release 12.0(16)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(16)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Cisco 12410 Internet Router
Platform: Cisco 12000 series
The Cisco 12410 Internet router, is a new 10-slot chassis in the Cisco 12000 series routers. The Cisco 12410 Internet router chassis includes redundant Gigabit Route Processors (GRPs), switch fabric cards, clock scheduler cards, and AC or DC power supplies. At 37-inches tall, the Cisco 12410 Internet router was designed so that two chassis can fit in most typical racks. The 10-slot chassis can support two GRPs and eight line cards, or one GRP and nine line cards. Using the latest switch fabric technology, the Cisco 12410 Internet router provides 20-Gbps switching capacity (10 Gbps in each direction) to each slot in the chassis, and thus is able to support the newest Cisco OC-192c/STM-64c and Four-port OC-48c/STM-16c line cards. The Cisco 12410 Internet router supports all existing Cisco 12000 series line cards as well.
New Software Features in Cisco IOS Release 12.0(16)S
This section describes new and changed features in Cisco IOS Release 12.0(16)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(16)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Distributed Traffic Shaping on POS Engine 2 Line Cards
Cisco IOS Release 12.0S now supports distributed Traffic Shaping (dTS) on Packet-over-SONET (POS) Engine 2 line cards. These line cards include the OC-48 Packet-over-SONET (POS) line cards and the Quad OC-12 POS line cards. The 8xOC-3 POS or 16xOC-3 POS line cards do not support dTS.
Sampled NetFlow on 3-Port Gigabit Ethernet Line Cards
Platform: Cisco 12000 series
Cisco IOS Release 12.0S now supports Sampled NetFlow on 3-Port Gigabit Ethernet line cards. With NetFlow Accounting, every IP packet is examined to gather statistics on the traffic being forwarded. These statistics are used to help plan and manage networks. At the high switching rates of the Cisco 12000 series Internet routers, however, this method can cause a performance penalty.
Sampled NetFlow Accounting alleviates this performance penalty by examining only a percentage of the packets being forwarded. Users determine the this percentage by specifying that only one out of every "x" IP packets be examined. These sample packets are accounted for in the NetFlow cache on the router. see the following document for further information:
Single Ring Recovery Protocol
Platform: Cisco 12000 series
Single Ring Recovery (SRR) is an extension to the Spatial Reuse Protocol (SRP) protocol in Dynamic Packet Transport (DPT) rings. If multiple failures occur on one of the two counter-rotating SRP rings, the SRR protocol switches all traffic to the error-free ring, allowing the system to operate with full connectivity. In all other cases, the SRP ring operates in standard Intelligent Protection Switching (IPS) behavior.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s16/srr.h tm
New Hardware and Software Features in Cisco IOS Release 12.0(15)S1 to Cisco IOS Release 12.0(15)S7
There are no new hardware or software features in Cisco IOS Release 12.0(15)S1 to Cisco IOS Release 12.0(15)S7.
New Hardware Features in Cisco IOS Release 12.0(15)S
This section describes new and changed features in Cisco IOS Release 12.0(15)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(15)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
2-Port Fast Ethernet Port Adapter
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The PA-2FE is a single-wide port adapter for the Cisco 7200 and Cisco 7500/VIP platforms. It provides two 10/100-Mbps,10/100BASE-T Fast Ethernet/ISL interfaces, and support both full-duplex and half-duplex operation.
The PA-2FE is available in two variants: a copper, dual port 100BASE-TX version with 100BASET, half/full duplex, over Category 5, and unshielded twisted-pair (PA-2FE-TX) and a fiber, dual port 100BASE-FX version with 100BASET, half/full, and over multimode optical fiber (PA-2FE-FX).
6E3-SMB and 12E3-SMB Line Cards
Platform: Cisco 12000 series
The 6E3-SMB and 12E3-SMB line cards consist of high-density E3 service through 6 or 12 E3 interfaces.
The 6-port line card is a partially depopulated version of the 12-port line card. The 6-port line card consists of a total of 12 connectors. A single port consists of one coaxial connector for receiving (Rx) and one coaxial connector for transmitting (Tx). The ports on the 6-port line card are numbered 0 to 5.
The 12-port line card consists of a total of 24 connectors. A single port consists of one coaxial connector for receiving (Rx) and one coaxial connector for transmitting (Tx). The ports on the 12-port line card are numbered 0 to 11. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12016/hfrcfig/11613e3.htm
Cisco 12416 Internet Router
Platform: Cisco 12000 series
The Cisco 12416 Internet router is a 16-slot chassis member of the Cisco 12000 series Internet routers that provides a total switching capacity of 320 Gigabits per second (Gbps), with 20 Gbps (10 Gbps full duplex) capacity per slot. The distributed packet forwarding and crossbar matrix switch of the Cisco 12416 Internet router enables 10 Gbps OC-192c/STM-64c and 4-port OC-48c/STM-16c interfaces while continuing to support all existing Cisco 12000 series line cards. Virtual Output Queuing (VOQ) technology ensures that the fabric experiences no head-of-line (HOL) blocking and an enhanced clock scheduler guarantees that all line cards get equal access to the fabric. Extensive use of high-performance application-specific integrated circuits (ASICs) supports line rate forwarding with minimal latency of real-time traffic while the fabric handles replication of multicast traffic in the hardware, providing a high level of performance.
OC-192c/STM-64c POS Line Card
Platform: Cisco 12000 series
The OC-192c/STM-64c Packet-over-SONET (POS) line card provides the Cisco 12416 Internet router with a single 10-Gbps POS interface on a single card. The card interfaces with the 320-Gbps switch fabric in the Cisco 12016 Internet router and provides one OC-192 duplex SC or FC single-mode connection. This connection is concatenated, which provides for increased efficiency by eliminating the need to partition the bandwidth.
Quad OC-48c/STM-16c POS Line Card
Platform: Cisco 12000 series
The Quad OC-48c/STM-16c Packet-over-SONET (POS) line card provides the Cisco 12416 Internet router with a single 10-Gbps POS interface on a single card. The card interfaces with the switch fabric in the Internet router and provides one OC-48c/STM-16c duplex SC or FC single-mode connection. This connection is concatenated, which provides for increased efficiency by eliminating the need to partition the bandwidth.
New Software Features in Cisco IOS Release 12.0(15)S
This section describes new and changed features in Cisco IOS Release 12.0(15)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(15)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
448 ACL Support on the 3-Port Gigabit Ethernet Line Card
Platform: Cisco 12000 series
Cisco IOS Release 12.0(15)S provides support for 448 access control lists (ACLs) on the 3-Port Gigabit Ethernet line card.
Differentiated Services Compliant Distributed Weighted Random Early Detection
Platform: Cisco 7500/RSP series
The Differentiated Services Compliant Distributed Weighted Random Early Detection (DiffServ Compliant dWRED) feature extends the functionality of Weighted Random Early Detection (WRED) to enable support for Differentiated Services (DiffServ) and Assured Forwarding (AF) Per Hop Behavior (PHB). This feature enables WRED to be compliant with the DiffServ standard and the AF PHB standard being developed by the Internet Engineering Task Force (IETF). Customers can implement AF PHB by coloring packets according to DSCP values and then assigning preferential drop probabilities to those packets. This feature introduces the random-detect dscp policy map class configuration command.
Enhanced EIGRP Stub Routing
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Enhanced Interior Gateway Routing Protocol (EIGRP) Stub Routing feature improves network stability, reduces resource utilization, and simplifies stub router configuration.
Stub routing is commonly used in a hub and spoke network topology. In a hub and spoke network, one or more end (stub) networks are connected to a remote router (the spoke) that is connected to one or more distribution routers (the hub). The remote router is adjacent to only one or more distribution routers. The only route for IP traffic to follow into the remote router is through a distribution router. This type of configuration is commonly used in WAN topologies in which the distribution router is directly connected to a WAN. The distribution router can be connected to one or more remote routers. Often, the distribution router will be connected to 100 or more remote routers. In a hub and spoke topology, the remote router must forward all nonlocal traffic to a distribution router, so it becomes unnecessary for the remote router to hold a complete routing table. Generally, the distribution router does not need to send anything more than a default route to the remote router.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s15/eigr pstb.htm
Filtering Inter-Area Routes on an ABR
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Filtering Inter-Area Routes on an ABR feature extends the ability of an area border router (ABR) that is running the OSPF protocol to filter type 3 link-state advertisements (LSAs) between different OSPF areas. This feature allows only specified prefixes to be sent from one area to another area while restricting all other prefixes. This type of area filtering can be applied out of a specific OSPF area, into a specific OSPF area, or into and out of the same OSPF areas at the same time. This feature is supported by the addition of the area filter-list command.
ICMP and PIRC Support on 3-Port Gigabit Ethernet Line Cards
Platform: Cisco 12000 series
Cisco IOS Release 12.0S now provides Internet Control Message Protocol (ICMP) and Per Interface Rate Control (PIRC) on 3-Port Gigabit Ethernet line cards.
The ICMP rate limiting on Engine 2 Packet-over-SONET (POS) line card feature is used to rate-limit ICMP echo-reply traffic in order to protect hosts against Denial of Service (DoS) attacks. Per Interface Rate Control (PIRC) controls the input access rate on a single physical interface on the Engine 2 packet-over-SONET (POS) line cards.
see the following documents for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s15/12s_ ssm.htm
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s15/12s_ igmp.htm
IP QoS for 3-Port Gigabit Ethernet Line Cards
Platform: Cisco 12000 series
Cisco IOS Release 12.0S now provides Weighted Random Early Detection (WRED)/Modified Deficit Round Robin (MDRR) support on 3-Port Gigabit Ethernet line cards in both the ingress and egress directions.
Modular Quality of Service Command-Line Interface
Platform: Cisco 12000 series
The Modular QoS CLI allows users to specify a traffic class independently of QoS policies.
The Modular QoS CLI is used to configure QoS. The Modular QoS CLI contains the following three steps:
•Defining a traffic class with the class-map command
•Creating a service policy by associating the traffic class with one or more QoS policies (using the policy-map command)
•Attaching the service policy to the interface with the service-policy command
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5/mq c/mcli.htm
NetFlow ToS-Based Router Aggregation
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The NetFlow ToS-Based Router Aggregation feature provides the ability to enable limited router-based Type of Service (ToS) aggregation of NetFlow export data. This results in summarized NetFlow Export data to be exported to a collection device, resulting in lower bandwidth requirements for NetFlow Export data and reduced platform requirements for NetFlow data collection devices. The NetFlow ToS Based Router Aggregation feature introduces support for six aggregation schemes that include the ToS byte as a field:
1. ::AS-ToS aggregation scheme
2. ::Protocol-Port-ToS aggregation scheme
3. ::SourcePrefix-ToS aggregation scheme
4. ::DestinationPrefix-ToS aggregation scheme
5. ::Prefix-ToS aggregation scheme
6. ::Prefix-Port aggregation scheme
OSPF Stub Router Advertisement
Platform: Cisco 7200 series, Cisco 7500 series
The OSPF Stub Router Advertisement feature allows you to bring a new router into a network without immediately routing traffic through the new router and allows you to gracefully shut down or reload a router without dropping packets that are destined for other networks. This feature introduces three configuration options that allow you to configure a router that is running the Open Shortest Path First (OSPF) protocol to advertise a maximum or infinite metric to all neighbors.
For more information about the OSPF Stub Router Advertisement feature, see the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft11osra.htm
Source MAC Address Accounting on the 3-Port Gigabit Ethernet Line Card
Platform: Cisco 12000 series
The source MAC address accounting feature provides the information for IP traffic on the basis of the source MAC addresses on the LAN interfaces. This feature calculates the total packet and byte counts for a LAN interface that receives or sends IP packets to or from a unique MAC address.
Source Specific Multicast with IGMPv3
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The source specific multicast (SSM) feature is an extension of IP multicast in which datagram traffic is forwarded to receivers from only those multicast sources that the receivers have explicitly joined. For multicast groups configured for SSM, only SSM distribution trees (no shared trees) are created.
SSM is a datagram delivery model that best supports one-to-many applications, also known as broadcast applications. SSM is a core networking technology for the Cisco implementation of IP multicast solutions targeted for audio and video broadcast application environments.
Internet Group Management Protocol (IGMP) is the Internet Engineering Task Force (IETF) standards track protocol used for hosts to signal multicast group membership to routers. Version 3 of this protocol supports source filtering, which is required for SSM. To run SSM with IGMPv3, SSM must be supported in the Cisco IOS router, the host where the application is running, and the application itself. Cisco IOS Release 12.0(15)S also adds support for the ip pim ssm command.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dtssm5t.htm
Note Cisco IOS Release 12.0S does not currently support URL Rendezvous Directory (URD) for the Cisco 12000 series Internet routers.
Unicast Reverse Path Forwarding Loose Mode
Platforms: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series.
For detailed information about this feature, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_urpf.htm
New Hardware and Software Features in Cisco IOS Release 12.0(14)S1 to Cisco IOS Release 12.0(14)S8
There are no new hardware or software features in Cisco IOS Release 12.0(14)S1 to Cisco IOS Release 12.0(14)S8.
New Hardware Features in Cisco IOS Release 12.0(14)S
This section describes new and changed features in Cisco IOS Release 12.0(14)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(14)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Cisco 7200-I/O-GE+E and Cisco 7200-I/O-2FE/E Input/Output Controllers
Platforms: Cisco 7200 series (Cisco 7200 VXR routers only)
The Cisco 7200-I/O-GE+E is an Input/Output controller that provides one Gigabit Ethernet and one Ethernet port. It is equipped with a Gigabit Interface Converter (GBIC) receptacle for 1000 Mbps operation and an RJ-45 receptacle for 10 Mbps operation.
The Cisco 7200-I/O-2FE/E is an Input/Output controller that provides two autosensing Ethernet or Fast Ethernet ports and two RJ-45 receptacles for 10/100 Mbps operation.
I/O controllers support the following features:
•Dual EIA/TIA-232 channels for local console and auxiliary ports
•NVRAM for storing the system configuration and environmental monitoring logs
•Two PC card slots that hold Flash disks or Flash memory cards for storing the default Cisco IOS software image
•Flash memory for storing the boot helper image
•Two environmental sensors for monitoring the cooling air as it enters and leaves the chassis
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s14/12s_ asio.htm
Multichannel STM-1 Port Adapter for the Cisco 7500 Series Router
Platform: Cisco 7500 series
The PA-MC-STM-1 is a high-speed single-port multichannel STM-1 port adapter. You can configure the PA-MC-STM-1 as a multichannel E1/E0 STM-1 port. The PA-MC-STM-1 can be configured into 63 individual E1 links. Each E1 link can carry a single channel at full or fractional rates, or be broken down into multiple DS0 or Nx64 Kbps rates. The PA-MC-STM-1 supports up to 3 TUG-3/AU-3 transport slots numbered 1 to 3. You can configure each TUG-3/AU-3 to carry 21 SDH TU-12s. Each SDH TU-12 is capable of carrying a channelized E1 frame, which can be to Nx64 Kbps time slots.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s14/12s_ stm.htm
NPE-400
Platform: Cisco 7200 series (Cisco 7200 VXR routers only)
NPE-400 is a new version of network processing engine for Cisco 7200 series routers with the following enhancements:
• RM7000 microprocessor that operates at an internal clock speed of 350 MHz
• Up to 512 MB ECC SDRAM
• 100 MHz SysAD and memory bus speed
• 4 MB Layer 3 cache
The NPE-400 leverages technology from the NPE-225 and NSE-1 to provide a higher performance NPE card.
PA-MC-2T3+ Phase-II (T3 Subrate)
Platform: Cisco 7200 series, Cisco 7500/RSP series
The PA-MC-2T3+ is a single-width port adapter that provides two T3 interface connections. Each T3 interface can now be independently configured to be either channelized or unchannelized. A channelized T3 provides 28 T1 lines multiplexed into the T3. Each T1 line can be configured into one or more serial interface data channels.
Using the no channelized command, you can configure the T3 as a single, unchannelized serial interface data channel. You can configure this data channel to use all of the T3 bandwidth or a portion of it. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s14/12s_ ct3.htm
New Software Features in Cisco IOS Release 12.0(14)S
This section describes new and changed features in Cisco IOS Release 12.0(14)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(14)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Bit Error Rate Testing for 6-Port Channelized T3 Line Cards
Platform: Cisco 12000 series
Cisco IOS Release 12.0(14)S adds support for Bit Error Rate Testing (BERT) for 6-port channelized T3 line cards. BER tests allow you to test cables and diagnose signal problems in the field. You can configure individual T1 channel groups to run an independent BER test. You set one local serial port to BERT mode while the remaining local serial ports continue to transmit and receive normal traffic. The BER test checks communication between the local and the remote ports.
When running a BER test, your system expects to receive the same pattern that it is transmitting. If traffic is not being transmitted or received, create a back-to-back loopback BER test on the link or in the network and send out a predictable stream to ensure that you receive the same data that was transmitted.
To determine if the remote serial port returns the BERT pattern unchanged, you must manually enable network loopback at remote serial port, while you configure a BERT pattern to use in the test at specified time intervals on the local serial port.
You can later display and analyze the total number of error bits transmitted and the total number of bits received on the link. You can retrieve error statistics anytime during the BER test. see the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s21/bert .htm
BGP Policy Accounting on 3-Port Gigabit Ethernet Line Cards
Platform: Cisco 12000 series
Cisco IOS 12.0S now supports Border Gateway Protocol (BGP) policy accounting on 3-port Gigabit Ethernet line cards. For more information about this feature, see the "BGP Policy Accounting" section.
Extended ACLs on PSA
Platform: Cisco 12000 series
The Extended ACLs on PSA feature provides 448-Lines Access Control Lists (ACLs) support on the Performance OC-48 line card by implementing the functionality in the Packet Switching ASIC (PSA).
FRF2.1 Annex 1
Platform: Cisco 12000 series
FRF2.1 Annex 1 for Event Driven Procedures provides a signalling protocol for permanent virtual circuit (PVC) monitoring at the Network-to-Network Interface (NNI) for a frame relay switching network. FRF2.1 Annex 1 generates notification when an event occurs to change status and when an event occurs, it generates immediate notification.
It allows for faster notification of PVC status, such as addition, deletion, or availability, in frame relay switching networks with multiple switching nodes. The faster notification results in better network management as well as increased PVC scalability per interface since LMI procedures are not needed at each NNI node for each PVC in the network.
FRF2.1 Annex 1 adds event driven procedures to the enterprise frame relay network. It enables fast convergence and provides quick responses to any changes within a frame relay network. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s14/fr21 anx1.htm
ICMP Rate Limiting on Engine 2 POS Line Cards
Platform: Cisco 12000 series
The ICMP rate limiting on Engine 2 Packet-over-SONET (POS) line card feature is used to rate-limit ICMP echo-reply traffic in order to protect hosts against Denial of Service (DoS) attacks.
Inverse Multiplexing over ATM Enhancements
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The PA-A3-IMA port adapter has added the following functionalities for Cisco 7500 series routers running Cisco IOS Release 12.0(14)S or later:
•virtual path shaping
•IP-ATM Class of Service mapping on Cisco 7500 series routers (Class-Based Weighted Fair Queueing, Weighted Random Early Detection, Virtual Circuit Bundling)
•the available bit rate (ABR) Quality of Service class
MPLS Traffic Engineering IP Explicit Address Exclusion
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The MPLS traffic engineering Internet Protocol (IP) explicit address exclusion feature provides means to exclude a link or node from the path for an MPLS traffic engineering label-switched path (LSP).
The feature is accessible via the ip explicit-path command that allows you to create an IP explicit path and enter a configuration submode for specifying the path. The feature adds to the submode commands the exclude-address command for specifying addresses to exclude from the path.
If the exclude-address for an MPLS traffic engineering LSP identifies a flooded link, the constraint-based shortest path first (CSPF) routing algorithm does not consider that link when computing paths for the LSP. If the exclude-address specifies a flooded MPLS traffic engineering router ID, the CSPF routing algorithm does not allow paths for the LSP to traverse the node identified by the router ID.
NetFlow Export Version 5
Platform: Cisco 12000 series
Cisco IOS Release 12.0S now supports NetFlow Export version 5 on the Cisco 12000 series Internet router. The version 5 export format can be enabled along with traditional NetFlow and Sampled NetFlow features.
The NetFlow Export Version 5 feature provides the ability to export fine granularity data to the NetFlow collector. Per-flow information and statistics are maintained and uploaded to the workstation.
Sampled NetFlow on Engine 2 POS Line Cards
Platform: Cisco 12000 series
Cisco IOS Release 12.0S now supports Sampled NetFlow on Engine 2 Packet-over-SONET (POS) line cards. The Sampled NetFlow feature allows you to sample one out of "x" IP packets being forwarded to routers, by allowing the user to define the "x" interval with a value between a minimum and maximum. Sampling packets will be accounted for in the NetFlow Flow Cache of the router. These sampling packets will substantially decrease the CPU utilization needed to account for NetFlow packets by allowing the majority of the packets to be switched faster because they will not need to go through additional NetFlow processing.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/12s_ sanf.htm
New Hardware and Software Features in Cisco IOS Release 12.0(13)S1 to Cisco IOS Release 12.0(13)S6
There are no new hardware or software features in Cisco IOS Release 12.0(13)S1 to Cisco IOS Release 12.0(13)S8.
New Hardware Features in Cisco IOS Release 12.0(13)S
This section describes new and changed features in Cisco IOS Release 12.0(13)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(13)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
6-Port Channelized T3-SMB Line Card
Platform: Cisco 12000 series
The 6CT3-SMB line card consists of high-density digital signal level 3 (DS3) service through six copper T3 ports. T3 transmits DS3-formatted data at 44.736 Mbps through the telephone switching network that is used in a digital WAN carrier facility. Each T3 port can carry a full duplex DS3 rate signal. A T3 can be channelized into 28 independent DS1 data channels or up to 35 NxDS0. A total of 168 DS1 channels are supported, or 210 NxDS0 per line card.
The 28 DS1 channels are multiplexed into 7 DS2 channels. The 7 DS2 channels are multiplexed into a single DS3 signal. The 6CT3-SMB line card supports further channelization down to the DS0 time slot level (56 or 64 kilobits per second [kbps]).
The 6CT3-SMB line cards perform the High-Level Data Link Control (HDLC) encapsulation and de-encapsulation functions, and all other necessary functions including timing, signaling, and framing in compliance with DS1 and DS3 specifications. The six T3 ports are numbered 0 to 5.
The 6CT3-SMB line card is connected to devices on the remote customer side, using sub-miniature bayonet coupling (SMB) connectors. A single T3 port consists of one SMB connector for receiving (Rx) and one SMB connector for transmitting (Tx).
Quad OC-12c/STM-4c ATM Line Card
Platform: Cisco 12000 series
The Quad OC-12c/STM-4c ATM line card provides the Cisco 12000 series product line with four 622-Mbps ATM interfaces. The card interfaces to the Cisco 12000 product line's switch fabric and provides four OC-12c/STM-4c SC connectors for duplex single-mode or multimode SONET/SDH connections. There are four ports, numbered 0 to 3, on each line card. Each port has its own set of Status LEDs. Each SONET connection is concatenated, which provides for increased efficiency by eliminating the need to partition the bandwidth.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12012/bfrcfig/7193atm.htm
New Software Features in Cisco IOS Release 12.0(13)S
This section describes new and changed features in Cisco IOS Release 12.0(13)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(13)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
BGP Policy Accounting on Cisco 12000 Series Engine 2 Line Cards
Platform: Cisco 12000 series
Cisco IOS 12.0S now supports BGP policy accounting on Engine 2 line cards. For more information about this feature, see the "BGP Policy Accounting" section.
Cisco 7500 Single Line Card Reload
Platform: Cisco 7500/RSP series
Before the introduction of the Cisco 7500 Single Line Card Reload feature, the only method of correcting a line card hardware failure for one line card on a Cisco 7500 series router required the execution of a Cbus Complex, a process that reloaded every line card on the network backplane. The amount of time taken to complete the Cbus Complex was often inconvenient, and no network traffic could be routed or switched during the Cbus Complex process.
The Cisco 7500 Single Line Card Reload feature allows users to correct a line card hardware failure on a Cisco 7500 series router by reloading the failed line card without reloading any other line cards on the network backplane. During the single line card reload process, all physical lines and routing protocols on the other line cards of the network backplane remain active. Reloading a single line card is also significantly faster than the Cbus Complex execution process.
Class-Based Marking
Platform: Cisco 7200 series, Cisco 7500 series, Cisco 12000 series
The Class-Based Marking feature (formerly referred to as IP Packet Marking) is implemented on the PSA (hardware) and line card CPU (software) on Engine 2 line cards. In the context of this feature, class-based marking means setting or changing the 3-bit precedence value in the Type of Service (ToS) field of IP packets that are received on an interface by a user-configured value on the interface. The quality of service (QoS) treatment of the IP packets is then based on the new value of the precedence bits.
Policy Routing on Internet Router Engine 0 and Engine 1
Platform: Cisco 12000 series
Cisco IOS Release 12.0S now supports policy routing on Engine 0 and Engine 1 line cards.
New Hardware and Software Features in Cisco IOS Release 12.0(12)S3 to Cisco IOS Release 12.0(12)S3
There are no new hardware or software features in Cisco IOS Release 12.0(12)S3 to Cisco IOS Release 12.0(12)S4.
New Hardware Features in Cisco IOS Release 12.0(12)S
There are no new hardware features in Cisco IOS Release 12.0(12)S.
New Software Features in Cisco IOS Release 12.0(12)S
This section describes new and changed features in Cisco IOS Release 12.0(12)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(12)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Class-Based Quality of Service MIB
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The Class-Based Quality of Service MIB (Class-Based QoS MIB) provides read access to QoS configurations. This MIB also provides QoS statistics information based on the Modular QoS Command Line Interface (CLI), including information regarding class-map and policy-map parameters.
This Class-Based QoS MIB is actually two MIBs: CISCO-CLASS-BASED-QOS-MIB and CISCO-CLASS-BASED-QOS-CAPABILITY-MIB.
To locate MIBs, use the Cisco Network Management Toolkit for MIBs tool on Cisco.com.
Event MIB
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Event MIB is an asynchronous notification mechanism standardized for use by network management systems using Simple Network Management Protocol (SNMP). The Event MIB provides the ability to monitor MIB objects on a local or remote system using SNMP and to initiate simple actions whenever a trigger condition is met. By allowing notifications based on events, the Network Management Server (NMS) does not need to constantly poll managed devices to find out if something has changed.
Support of the Event MIB has been added to Cisco IOS software to work with network management systems and, when combined with the currently integrated Expression MIB support, provides a flexible and efficient way to monitor complex conditions on network devices.
By allowing SNMP notifications to take place only when a specified condition occurs, Event MIB support reduces the load on affected devices, significantly improving the scalability of network management solutions. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dtevent.htm
Frame Relay Switching Diagnostics and Troubleshooting
Platform: Cisco 12000 series
The Frame Relay Switching Diagnostics and Troubleshooting feature enhances Frame Relay switching functionality by providing tools to diagnose problems in switched Frame Relay networks. The show frame-relay pvc command has been enhanced to display detailed reasons why packets were dropped from switched permanent virtual circuits (PVCs). The command also displays the local PVC status, the Network-to-Network Interface (NNI) PVC status, and the overall PVC status. If a network problem is observed, the new debug frame-relay switching command can be used to display the status of packets on switched PVCs at regular intervals. This new debug command displays information such as the number of packets that were switched, why packets were dropped, and changes in status of physical links and PVCs.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s12/12sf rsdg.htm
Hot Standby Router Protocol MIB
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Cisco IOS Release 12.0(12)S adds support for the Hot Standby Router Protocol (HSRP) MIB for the Cisco 7100 series, 7500 series and 12000 series Internet router platforms.
HSRP is a Cisco proprietary protocol defined in RFC# 2281. The HSRP MIB allows network management systems (NMS) to get reports about the "active" or "standby" HSRP status of devices in a network using Simple Network Management Protocol (SNMP) operations. HSRP trap notifications are configured from the Cisco IOS command-line interface (CLI) using the snmp-server enable traps command and the snmp server host command. A trap notifies the NMS when a router leaves or enters the active or standby state. When an entry is configured from the CLI, the Row Status for that group in the MIB immediately goes to the active state.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s12/12s_ hsrp.htm
Multicast Source Discovery Protocol MIB
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The Multicast Source Discovery Protocol (MSDP) MIB feature adds support in Cisco IOS software for the MSDP MIB. This MIB describes objects used for managing MSDP operations using Simple Network Management Protocol (SNMP). Documentation for this MIB exists in the form of an Internet Draft titled "Multicast Source Discovery Protocol MIB" (draft-ietf-msdp-mib-03.txt) and is available through the Internet Engineering Task Force (IETF) at http://www.ietf.org.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s12/12s_ msdp.htm
Versatile Interface Processor-Based Distributed FRF.12
Platform: Cisco 7500/RSP series
The Voice over Frame Relay (VoFR) capabilities that were introduced on the Cisco MC3810 multiservice access concentrator beginning with Cisco IOS Release 11.3 were eventually extended to the Cisco 2600 series, 3600 series, and 7200 series router platforms. These capabilities are now available for Cisco 7500 series routers (with a VIP).
When VoFR is configured on a Cisco router, the router is able to carry voice traffic such as telephone calls and faxes over a Frame Relay network.
The Cisco implementation of Voice over Frame Relay provides the following benefits to existing Frame Relay networks:
•Enables real-time, delay-sensitive voice traffic to be carried over slow Frame Relay links.
•Allows dedicated 64-kbps Time-Division Muliplexing (TDM) telephony circuits to be replaced by more economical Frame Relay permanent virtual circuits.
•Allows voice-enabled routers from multiple remote sites to be multiplexed into a central site router through Frame Relay links.
•Utilizes voice compression technology that conforms to ITU-T specifications.
•Enables Cisco 7500 series routers with a VIP to support Frame Relay fragmentation.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s12/vofr /index.htm
New Hardware and Software Features in Cisco IOS Release 12.0(11)S6
There are no new hardware or software features in Cisco IOS Release 12.0(11)S6.
New Hardware Features in Cisco IOS Release 12.0(11)S
This section describes new and changed features in Cisco IOS Release 12.0(11)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(11)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
1OC-48/STM-16 SRP Line Card
Platform: Cisco 12000 series
The 1OC-48/STM-16 SRP line card has a pair of OC-48c, fiber-optic standard connector (SC) duplex ports that provide an SC connection for either the single-mode short-reach or single-mode long-reach version.
The 1OC-48/STM-16 SRP line card allows networks to:
•Provide transmit packet priority with 3 separate queues to prevent head-of-line blocking:
–Control packets are never rate-shaped or back-pressured by the Ring Access Controller (RAC)
–High-priority packets are rate-shaped by the RAC
–Low-priority packets are rate-shaped by the RAC
•Priority-map 8 levels IP/SRP into 2 levels of priority (high and low)
–Software-selectable rate shaping (rate=X or no shaping) for both high- and low-priority data (RAC)
–Packet priority determined by type of service (ToS) byte in IP Header (RAC + L3)
•Accept or reject a packet from a particular host
•Transmit Spatial Reuse Protocol (SRP) encapsulation at full rate
•Transmogrify an SRP packet into a Packet-over-SONET (POS) packet in order to allow fast path switching in the PSA.
•Transit Path Performance Monitors
–High/low queue depth (avg, min, max)
–High/low queue packet delay (avg, min, max)
–Packet and byte counts by source or destination MAC address
•Receive Path Performance Monitors
–Packet and byte counts by source or destination MAC address
•Monitors for incoming and outgoing packets in RAC with separate SRP interface counters
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12012/bfrcfig/10567srp.htm#xtocid2983614
3-Port Gigabit Ethernet Line Card
Platform: Cisco 12000 series
The 3-Port Gigabit Ethernet line card provides Cisco 12000 series routers with three optical Gigabit Ethernet interfaces, which operate faster than 1-Gbps, on a single card. These interfaces are designed to operate as trunks between Cisco 12000 series Internet routers and other routers or Layer 2 switches. These connections are concatenated, and provide for increased efficiency by eliminating the need to partition the bandwidth. The 3-Port Gigabit Ethernet Line card will provide two ports at full line rate provided the third port is shut down. With all three ports turned on, the 3-Port Gigabit Ethernet line card will balance the load across all three ports up to the card packet forwarding limitations of 4 million packets.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12012/bfrcfig/10551ge3.htm
Multiport T1/E1 ATM Port Adapters with Inverse Multiplexing over ATM
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The inverse multiplexing over ATM (IMA) port adapter is a single-width port adapter that allows
Cisco 7100 series, Cisco 7200 series, and Cisco 7500 series routers to support inverse multiplexing over ATM. These port adapters allow WAN uplinks at speeds ranging from 1.544 Mbps to 12.288 Mbps for T1 connections and from 2.048 Mbps to 16.384 Mbps for E1 connections.With this scalable ATM IMA solution from Cisco, network designers and managers can deploy only the bandwidth they need, using multiple T1 or E1 connections instead of more expensive T3 or OC-3 lines to bridge LANs and ATM WAN applications. Enterprises and branch offices can aggregate traffic from multiple lower-bandwidth physical transmission media, such as T1 or E1 pipes, to transmit voice and data at high-bandwidth connection speeds.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe7_1/imatm.htm
PA-A3 OC-12 ATM Port Adapter
Platform: Cisco 7500/RSP series
The PA-A3 OC-12 is a dual-width ATM port adapter that provides a single-port, 622.08 Mbps connection from Cisco 7500 series routers to any ATM switch. The PA-A3 OC-12 includes two hardware versions (PA-A3-OC12MM and PA-A3-OC12SMI) that support the following standards-based physical interfaces:
•OC-12c/STM-4 multimode
•OC-12c/STM-4 single-mode intermediate reach
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/6228oc12/6228ovrn.htm
VIP-4
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The VIP-4 is the fourth generation of Versatile Interface Processors for use with Cisco 7000 series routers using the Cisco 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI) and with Cisco 7500 series routers (which also include the Cisco 7507-MX and Cisco 7513-MX routers). The VIP4 installs in the interface processor slots in your Cisco 7000 series or Cisco 7500 series router.
New Software Features in Cisco IOS Release 12.0(11)S
This section describes new and changed features in Cisco IOS Release 12.0(11)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(11)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Distributed GRE Tunneling
Platform: Cisco 7500/RSP series
The Distributed generic routing encapsulation (GRE) Tunneling Support feature allows GRE IP and other features, such as Web Cache Communication Protocol (WCCP) tunneling, to be performed on VIP-based line cards for the Cisco 7500/RSP platform. The tunneling is performed using recursive or "double" switching techniques that are currently deployed on existing non-distributed platforms, the relevant bits of which are ported into this development. The double switching is performed by handling the received IP packet in the existing code path until it is determined that the packet needs encapsulation or de-encapsulation, at which point the necessary actions are performed, and the resultant IP packet is recursively forwarded through the IP switching path again.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/12s_ dgre.htm
Enhanced Gigabit Ethernet Interface Processor
Platform: Cisco 7500/RSP series
The Enhanced Gigabit Ethernet Interface Processor (GEIP+) is a single-port interface processor that, when combined with the appropriate optical fiber cable and a Gigabit Interface Converter (GBIC), provides one Gigabit Ethernet (GE) interface that is compliant with the IEEE 802.3z specification. The GE interface on a GEIP+ operates in full-duplex mode.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7505/vip1/vip4/10699dwg/index.htm
Frame Relay Switching on Engine 2
Platform: Cisco 12000 series
Cisco IOS Release 12.0(11)S supports Frame Relay switching on Engine 2 for the Cisco 12000 series Internet router. Frame Relay is an industry-standard, switched data link layer protocol that handles multiple virtual circuits using High-Level Data Link Control (HDLC) encapsulation between connected devices.
ifIndex Persistence
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
One of the most commonly used identifiers used in SNMP-based network management applications is the Interface Index (ifIndex) value. IfIndex is a unique identifying number associated with a physical or logical interface; as far as most software is concerned, the ifIndex is the "name" of the interface. Although there is no requirement in the relevant RFCs that the correspondence between particular ifIndex values and their interfaces be maintained across reboots, applications such as device inventory, billing, and fault detection increasingly depend on the maintenance of this correspondence.
Cisco IOS Release 12.0(11)S adds support for an ifIndex value that can persist across reboots, allowing users to avoid the workarounds previously required for consistent interface identification. The Interface Index Persistence feature allows for greater accuracy when collecting and processing network management data by uniquely identifying input and output interfaces for traffic flows and SNMP statistics. Relating each interface to a known entity (such as an ISP customer) allows network management data to be more effectively utilized.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/12si fidx.htm
Per Interface Rate Control
Per Interface Rate Control (PIRC) controls the input access rate on a single physical interface on the Engine 2 packet-over-SONET (POS) line cards. Examples of this type of line card are the Enhanced OC-48c/STM-16c POS line card and the Enhanced Quad OC-12c/STM-4c POS line card. You can configure PIRC to either set the precedence of a packet and resend it, transmit the packet as-is, or drop the packet.
WCCP Enhancements
Platforms: Cisco 7200 series, Cisco 7500/RSP series
WCCP enhancements add support for WCCP Version 2 for Cisco IOS Release 12.0(11)S. The WCCP feature allows you to use Cisco cache engines or third-party cache engines to handle web traffic, reducing transmission costs and downloading time. This traffic includes user requests to view pages and graphics on World Wide Web servers, whether internal or external to your network, and the replies to those requests. When a user requests a page from a Web server (located in the Internet), the router sends the request to a cache engine. If the cache engine has a copy of the requested page in storage, the cache engine sends the user that page. Otherwise, the cache engine retrieves the requested page and the objects on that page from the web server, stores a copy of the page and its objects, and forwards the page and objects to the user.
WCCP transparently redirects a variety of traffic types, specified by protocol (TCP or UDP) and port. Cisco Cache Engines support only redirection of HTTP (TCP port 80) traffic requests from the intended server to a cache engine. End users do not know that the page came from the cache engine rather than the originally requested Web server.
WCCP v2 for Cisco IOS 12.0S now contains the following new features:
•Distributed CEF Support
•Input Feature
•Policy Redirection (Policy Routing)
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s11/inde x.htm
New Hardware and Software Features in Cisco IOS Release 12.0(10)S7 to Cisco IOS Release 12.0(10)S8
There are no new hardware or software features in Cisco IOS Release 12.0(10)S7 to Cisco IOS Release 12.0(10)S8.
New Hardware Features in Cisco IOS Release 12.0(10)S
This section describes new and changed features in Cisco IOS Release 12.0(10)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(10)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
8xOC-3 POS or 16xOC-3 POS Line Card
Platform: Cisco 12000 series
The single-mode or multimode 8xOC-3 POS or 16xOC-3 POS line card allows Cisco 12000 series routers to aggregate large amounts of data on existing fiber networks. The 8xOC-3 POS or 16xOC-3 POS line card interfaces with the switch fabric in the Cisco 12000 series router and provides a support level of 64 ports per 8-port system and 256 ports per 16-port system. Support for quality of service (QoS) packet flow control processing provides an additional value-added routing feature for Internet service providers (ISPs).
The 8xOC-3 POS line card provides Cisco 12000 series routers with 8 OC-3/STM-1 ports per slot or up to 64 OC-3/STM-1 ports per system. The 16xOC-3 POS line card provides Cisco 12000 series routers with 16 OC-3/STM-1 ports per slot or up to 256 OC-3/STM-1 ports per system.
Cisco Optical Regenerator
Platform: Cisco 12000 series
The Cisco Optical Regenerator is a bidirectional OC-48/STM-16 regenerator that sends optical signals over the longest distance possible. It supports single-mode long reach optical-fiber transmission when connected to an OC-48 line card that is installed in a Cisco 12000 series Internet router. The SONET specification for fiber-optic transmission defines the standard for single-mode fiber. The regenerator provides an end-to-end IP transport for long distances by forwarding SONET/SDH traffic at OC-48 line rates.
The Cisco Optical Regenerator uses only single-mode fiber because signals can travel farthest through single-mode long reach fiber. The maximum distance for single-mode installations of the regenerator is determined by the amount of light loss in the fiber path and by the physical limitation of sending optical fiber to optical light over exceptionally long distances. High-quality single-mode fiber with minimal high-quality splices can carry a Cisco Optical Regenerator signal up to 50 miles (80 kilometers).
Route Switch Processor (RSP8)
Platform: Cisco 7500/RSP series
The RSP8 is the newest main system processor module for Cisco 7500 series routers. In addition to running the system software from DRAM, the RSP8 sends and receives routing protocol updates, manages tables and caches, monitors interface and environmental status, and provides Simple Network Management Protocol (SNMP) management and the interface between the console and Telnet.
The high-speed switching section of the RSP8 communicates with and controls the interface processors on the high-speed CyBus. This switching section of the RSP8 decides the destination of a packet and switches it based on that decision. see the following document for further information:
www.cisco.com/cc/td/doc/product/core/cis7507/7507cfig/6586rsp8.htm
New Software Features in Cisco IOS Release 12.0(10)S
This section describes new and changed features in Cisco IOS Release 12.0(10)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(10)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
2 x 32-Bit Counters
Platform: Cisco 12000 series
Cisco IOS Release 12.0S now supports 2 x 32-bit counters. The 2 x 32-bit counters MIB will allow the 64-bit counters ifHCInOctets, ifHCInUcastPkts, ifHCOutOctets, and ifHCOutUcastPkts to each be represented as two 32-bit objects. One object will represent the upper 32-bits and the other the lower 32-bits. The new objects are as follows:
•cHCCounterIfInOctetsUpper
•cHCCounterIfInOctetsLower
•cHCCounterIfInUcastPktsUpper
•cHCCounterIfInUcastPktsLower
•cHCCounterIfOutOctetsUpper
•cHCCounterIfOutOctetsLower
•cHCCounterIfOutUcastPktsUpper
•cHCCounterIfOutUcastPktsLower
Access List Performance Improvements for Cisco 12000 Internet Routers
Platform: Cisco 12000 series
Access list (ACL) performance improvements are provided for two types of Cisco 12000 line cards:
•Line cards using engine 1 architecture
•Line cards using engine 2 architecture
The ACL performance improvement is implemented in a slightly different way depending on the line card type. Engine 1 line cards achieve ACL performance improvement strictly through hardware, using an improved ASIC design. Engine 2 line cards use a microcode enhancement in the packet switch ASIC (PSA) for packet-over-SONET (POS) applications.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s10/hw_ acl.htm
BGP Policy Accounting
Platforms: Cisco 7200 series; Cisco 7500/RSP series, Cisco 12000 series
BGP Policy Accounting provides a means of charging customers according to the route that their traffic travels. Trans-Pacific, Trans-Atlantic, satellite, domestic, and other provider traffic can be identified and accounted for on a per-customer basis when customers are on a unique software interface. This feature also allows the accounting of traffic to known autonomous system numbers in order to better engineer and plan network circuit peering and transit agreements.
BGP Policy Accounting classifies IP traffic by autonomous system number or autonomous system community string and increments packet and byte counters per input interface. It performs this function using route-maps to classify the traffic into one of eight possible indexes, which represent a traffic classification.
Extended Ethernet Frame Size Support
Platform: Cisco 12000 series
Cisco IOS Release 12.0S now supports Extended Ethernet Frame Size in accordance with the Network Working Group Internet Draft titled "Extended Ethernet Frame Size Support," draft-kaplan-isis-ext-eth-00.txt.
MPLS over Frame Relay
Platforms: Cisco 7200 series, Cisco 7500/RSP series
Transmission of Multiprotocol Label Switching (MPLS)-encapsulated packets across a point-to-point Frame Relay subinterface is now supported. Configuration of the feature is identical to configuration of MPLS on any other interface type:
(
config)# interface Serial1/0.1 point-to-point
(config-if)# tag ipor
(config-if)# mpls traffic-engineering tunnels
Note that some Frame Relay features (for example, FRF.12 fragmentation) are not supported for MPLS packets.
Named Community Lists
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
With numbered community lists, there are two types of community list numbers (standard and extended), and there can be up to 100 of each of the lists. Named community lists do not have an upper limit on the number of lists that can be defined. The command syntax is as follows:
ip community-list standard [community-name | community-number] [permit|deny] community
ip community-list extended [community-name | community-number] [permit|deny]
regular-expressionAll rules of numbered community lists apply.
Secure Shell Client Version 1
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Secure Shell (SSH) is a protocol that provides a secure, remote connection to a router. Two versions of SSH are available: SSH Version 1, and SSH Version 2. Only SSH Version 1 is implemented in Cisco IOS software.
The SSH Server feature enables a SSH client to make a secure, encrypted connection to a Cisco router. This connection provides functionality that is similar to an inbound Telnet connection. The SSH server in Cisco IOS software will work with publicly and commercially available SSH clients.
The SSH Client feature is an application that runs on a reliable TCP/IP transport layer, and provides strong authentication and encryption. The SSH Client in Cisco IOS software allows a user that is running an EXEC session on a Cisco router to log in to another remote Cisco router, and execute commands on the remote router. With authentication and encryption, SSH Client allows for a secure communication over an insecure network. SSH Client Version 1 supports DES and 3DES encryption and userid/password authentication.
Section Data Communications Channel
Platform: Cisco 12000
On Cisco Internet router OC-48 based line cards, Cisco IOS Release 12.0S now supports the IP/Section Data Communications Channel (SDCC) interface that is available on the Cisco OC-48 Optical Regenerator. To enable this feature, enter the sdcc enable command in configuration mode. To disable this feature, enter the no sdcc enable command. For further information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/core/optregen/opt_cfg/regen48.htm
SNMP Support for BGP Policy Accounting
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
BGP Policy Accounting accumulates incoming packet counts and octet counts per interface in the fibidb structure. These counters are now SNMP retrievable because of a new MIB called CISCO-BGP-POLICY-ACCOUNTING-MIB. Each row in the MIB table contains statistics for a particular traffic type on an interface. The table is indexed by ifindex from the IF-MIB and a traffic_index that identifies a particular traffic type. The traffic can be classified into one of eight types using the command-line interface (CLI).
Weighted Random Early Detection
Platform: Cisco 12000 series
Random Early Detection (RED) is a congestion avoidance mechanism that takes advantage of the TCP congestion control mechanism. By randomly dropping packets prior to periods of high congestion, RED tells the packet source to decrease its transmission rate. Assuming the packet source is using TCP, it will decrease its transmission rate until all the packets reach their destination, indicating that the congestion is cleared.
Weighted RED (WRED) generally drops packets selectively based on IP precedence. Packets with a higher IP precedence are less likely to be dropped than packets with a lower precedence. Thus, higher priority traffic is delivered with a higher probability than lower priority traffic. However, you can also configure WRED to ignore IP precedence when making drop decisions so that nonweighted RED behavior is achieved.
WRED is useful on any output interface where you expect to have congestion. However, WRED is usually used in the core routers of a network, rather than at the edge. Edge routers assign IP precedences to packets as they enter the network. WRED uses these precedences to determine how it treats different types of traffic. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios112/ios112p/gsr/wred_gs.htm
Distributed Multilink Point-to-Point Protocol
Platform: Cisco 7500/RSP series
The Distributed Multilink Point to Point Protocol (distributed MLP) feature allows T1/E1 lines to be combined in a Versatile Interface Processor (VIP) on a Cisco 7500 series router into a bundle that has the combined bandwidth of multiple T1/E1 lines by using a VIP MLP link. You choose the number of bundles and the number of T1/E1 lines in each bundle, which allows you to increase the bandwidth of your network links beyond that of a single T1/E1 line without the need to purchase a T3 line. Nondistributed MLP can only perform limited links, with CPU utilization quickly reaching 90 percent with only a few T1/E1 lines running MLP. With distributed MLP, you can increase the total capacity of the router.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/multippp.htm
Low Latency Queueing
Platform: Cisco 7500/RSP series
The Low Latency Queueing feature brings strict priority queueing to Class-Based Weighted Fair Queueing (CBWFQ). Strict priority queueing allows delay-sensitive data, such as voice, to be dequeued and sent first (before packets in other queues are dequeued), giving delay-sensitive data preferential treatment over other traffic.
Without Low Latency Queueing, CBWFQ provides weighted fair queueing based on defined classes with no strict priority queue available for real-time traffic. CBWFQ allows you to define traffic classes and then assign characteristics to that class. For example, you can designate the minimum bandwidth delivered to the class during congestion.
For CBWFQ, the weight for a packet belonging to a specific class is derived from the bandwidth you assigned to the class when you configured it. Therefore, the bandwidth assigned to the packets of a class determines the order in which packets are sent. All packets are serviced fairly based on weight; no class of packets may be granted strict priority. This scheme poses problems for voice traffic, which is largely intolerant of delay, especially variation in delay. For voice traffic, variations in delay introduce irregularities of transmission manifesting as jitter in the heard conversation.
The Low Latency Queueing feature provides strict priority queueing for CBWFQ, reducing jitter in voice conversations. Configured by the priority command, Low Latency Queueing enables use of a single, strict priority queue within CBWFQ at the class level, allowing you to direct traffic belonging to a class to the CBWFQ strict priority queue.
In the event of congestion, when the bandwidth is exceeded, policing is used to drop packets. Voice traffic enqueued to the priority queue is User Datagram Protocol (UDP)-based and therefore not adaptive to the early packet drop characteristic of Weighted Random Early Detection (WRED).
When congestion occurs, traffic destined for the priority queue is metered to ensure that the bandwidth allocation configured for the class to which the traffic belongs is not exceeded. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5c/ll qvip.htm
New Revision of System Controller Chip for NPE-175/NPE-225
Platform: Cisco 7200 series
This feature adds support for a new revision of a hardware component that fixes a previous error. For the benefit of users that have not upgraded to the new hardware, it will also exhibit the following warning error message that indicates the old hardware revision:
PLATFORM-4-RECALLED_NPE: Old version NPE-175/225 with Rev= 0xNN system controller. Contact upgrades-info@cisco.com for replacement.
Cisco 7200 series routers with NPE-175 or NPE-225 network processing engines must upgrade to Cisco IOS releases that incorporate this change (for example, Cisco IOS Release 12.0(9) and later releases or Cisco IOS Release 12.0(9)S and later releases). Use of older Cisco IOS releases might result in unpredicted malfunctions.
Router-ports Group Management Protocol (RGMP)
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Router-Port Group Management (RGMP) is a new protocol that restricts multicast traffic to router ports.
CGMP (Cisco Group Management Protocol) and IGMP (Internet Group Management Protocol) are two existing features that restrict multicast traffic to hosts that do not need to receive them, reducing the amount of processing the hosts have to do. CGMP and IGMP only restrict traffic on the ports of switches to which hosts are connected. CGMP and IGMP are designed for typical access networks where many hosts are connected but only one or two routers forward traffic to those hosts.
RGMP is designed for switched backbone networks or exchange points where predominantly routers are connected to each other. Large amounts of multicast traffic can be restricted, eliminating unnecessary congestion on the router ports. To effectively restrict multicast traffic to router ports, both the routers and the switches on the network must support RGMP.
New Hardware and Software Features in Cisco IOS Release 12.0(8)S1
There are no new hardware or software features in Cisco IOS Release 12.0(8)S1.
New Hardware Features in Cisco IOS Release 12.0(8)S
This section describes new and changed features in Cisco IOS Release 12.0(8)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(8)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Cisco 12016 Internet Router
Platform: Cisco 12000 series
The Cisco 12016 Internet router, is a 16-slot member of the Cisco 12000 series Internet routers. The Cisco 12016 Internet Router delivers a raw transmission rate per slot of up to 10 Gbps, a switching capacity of up to 160 Gbps, and speeds of up to OC-48/STM-16 (2.44 Gbps). It uses the same Gigabit Route Processor (GRP) and line cards (OC-3, OC-12, and OC-48) as the other routers in the Cisco 12000 series of routers.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12016/hfricg/index.htm
Enhanced Quad OC-12c/STM-4c Layer 3 Packet-over-SONET Line Card
Platform: Cisco 12000 series
The Quad OC-12c/STM-4c Packet-over-SONET (POS) line card provides Cisco 12000 series routers with four 622-Mbps POS interfaces on a single card. The card interfaces with the switch fabric in the Cisco 12000 series router and provides four OC-12c/STM-4c duplex SONET connections via Single-Mode OC-3c Cable (SC Connectors). Each connection is concatenated, which provides for increased efficiency by eliminating the need to partition the bandwidth.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12012/bfrcfig/10187pos.htm
New Software Features in Cisco IOS Release 12.0(8)S
This section describes new and changed features in Cisco IOS Release 12.0(8)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(8)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
APS Reflector Mode
Platform: Cisco 12000 series
APS reflector mode enhances the operation of Automatic Protection Switching (APS) by decreasing the remote timeout that occurs when a remote router is informed of a switchover between the working router and protect router in an APS circuit.
Fast EtherChannel Support on the Cisco 7200 Platform
Platform: Cisco 7200 series
Fast EtherChannel is now supported on Cisco 7200 series routers. The Fast EtherChannel feature allows multiple Fast Ethernet point-to-point links to be bundled into one logical link to provide bidirectional bandwidth of up to 800 Mbps. For more information on Fast EtherChannel, see the original feature guide written for the 11.1 CC Release, Fast EtherChannel, at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios111/ca111/fechan.htm
Or see page 31 of the Cisco IOS Interface Configuration Guide for Cisco IOS Release 12.0 at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/inter_c/iclanint.htm#3809
Multiprotocol Label Switching Traffic Engineering OSPF Support
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Multiprotocol Label Switching (MPLS) traffic engineering software that was released in Cisco IOS Release 12.0(5)S has been enhanced to support OSPF routing. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s8/te_12 08s.htm
Service Assurance Agent
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Service Assurance (SA) Agent is both an enhancement to and a new name for the Response Time Reporter (RTR) feature that was introduced in Cisco IOS Release 11.2. The feature allows you to monitor network performance by measuring key service level agreement metrics such as response time, network resources, availability, jitter, connect time, packet loss, and application performance.
The SA Agent feature was introduced in Cisco IOS Release 12.0(5)T, and is now available in Cisco IOS Release 12.0(8)S.
The SA Agent provides new capabilities that enable you to monitor:
•Domain Name System (DNS) performance. Thresholds can be used to trigger additional collection of time delay statistics.
•Internet Control Message Protocol (ICMP), User Datagram Protocol (UDP) echo response time, and TCP connection setup time, with different ToS settings in the IP header.
•Network one-way delay variance (jitter) and packet loss.
•Web server response time.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/saaoper.htm
Virtual Path Traffic Shaping
Platform: Cisco 12000 series
Virtual path (VP) traffic shaping allows multiple virtual circuits (VCs) to be bundled into one VP. This "bundling" is also called traffic shaping because all VCs bundled within the VP are shaped as one traffic rate. In addition, bundling the VCs improves the error detection for the bundled VCs.
New Hardware Features by Cisco IOS Release 12.0(7)S
This section describes new and changed features in Cisco IOS Release 12.0(7)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(7)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Enhanced OC-48c/STM-16c Layer 3 Packet-over-SONET Line Card
Platform: Cisco 12000 series
The OC-48c/STM-16c POS line card provides Cisco 12000 series routers with a single 2.5-Gbps POS interface on a single card. The card interfaces with the switch fabric in the Cisco 12000 series router and provides one OC-48c/STM-16c duplex SC or FC single-mode connection. This connection is concatenated, which provides for increased efficiency by eliminating the need to partition the bandwidth. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12012/bfrcfig/6792oc48.htm
Gigabit Ethernet (PA-GE Support)
Platform: Cisco 7200 series
The PA-GE is a one-port port adapter that, when combined with the appropriate fiber-optic cable and a Gigabit Interface Converter (GBIC), provides one Gigabit Ethernet (GE) interface that is compliant with the IEEE 802.3z specification. The GE interface on a PA-GE operates in full-duplex mode. The PA-GE is supported by the Cisco 7200 VXR routers. Please note that this port adapter is not currently supported by the fourth-generation Versatile Interface Processor (VIP4). Refer the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/7200vx/72vxpa/7188page/index.htm
Two-Port Multichannel DS1/PRI and Multichannel E1/PRI Port Adapters
Platform: Cisco 12000 series
Two-port versions of the Multichannel DS1/PRI and Multichannel E1/PRI port adapters are now available. see the following documents for further information:
http://www.cisco.com/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/4815ds1p/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/5083e1p/index.htm
New Software Features in Cisco IOS Release 12.0(7)S
This section describes new and changed features in Cisco IOS Release 12.0(7)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(7)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
ATM CLP Setting
Platform: Cisco 7500/RSP series
The use of the Cell Loss Priority (CLP) bit in the ATM header of a cell provided a method of controlling the discarding of cells in a congested ATM environment. A CLP bit contains two settings: 0 or 1. Cells with a CLP bit setting of 1 are discarded before cells with a CLP bit setting of 0. Before the introduction of the ATM CLP Setting feature, the CLP bit was automatically set to 0 when Cisco routers converted packets into ATM cells for ATM networks.
The ATM CLP Setting feature allows users to control the CLP bit setting on routers running the PA-A3 port adapter. CLP bits are set on each packet individually, and the default CLP bit setting is 0. The application of the ATM CLP feature changes the CLP bit setting to 1. Therefore, users have the option of leaving each packet with the default CLP bit setting of 0 or establishing a new CLP bit setting of 1. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s7/atmcl p.htm
Distributed Traffic Shaping
Platform: Cisco 7500/RSP series
Many enterprise and service provider customers need to shape traffic in their networks and sometimes need to shape IP traffic independently of the underlying interface. In other cases, the goal is to perform traffic shaping to ensure adherence to committed information rates on Frame Relay links.
The dTS feature is one element used to manage the bandwidth of an interface to avoid congestion, meet remote site requirements, and conform to a service rate that is provided on that interface.
The distributed Traffic Shaping (dTS) feature uses queues to buffer traffic surges that can congest a network. Data is buffered and then sent into the network at a regulated rate, which ensures that traffic will behave in accordance with the configured descriptor, as defined by committed information rate (CIR) (mean rate), Bc (burst size), and Be (excess burst size). With the defined average bit rate and burst size that are acceptable on that shaped entity, you can derive a time interval value.
The excess burst size (Be) allows more than the burst size to be sent during a time interval under certain conditions. Therefore, dTS provides two types of shape commands: average and peak. When shape average is configured, the interface sends no more than the burst size for each interval, achieving an average rate no higher than the mean rate (CIR). When shape peak is configured, the interface sends Bc plus Be bits in each interval.
In a link layer network such as Frame Relay, the network sends messages with the forward explicit congestion notification (FECN) or backward explicit congestion notification (BECN) if there is congestion. With the dTS feature, the traffic shaping adaptive mode takes advantage of these signals and adjusts the traffic descriptors, which approximates the rate to the available bandwidth along the path.
IS-IS Over ISL
Platforms: Cisco 7200 series, Cisco 7500/RSP series
With Release 12.0(7)S, Intermediate System-to-Intermediate System (IS-IS), Connectionless Network Service (CLNS), and Interior Gateway Routing Protocol (IGRP) configuration commands are now recognized on an Inter-Switch Link (ISL) virtual LAN (VLAN) subinterface.
MPLS Switching Support for Gigabit Ethernet
Platform: Cisco 12000 series
Basic tag/Multiprotocol Label Switching (MPLS) switching is now supported for Gigabit Ethernet (GE) line cards for the Cisco 12000 series Internet routers.
NetFlow Support for Gigabit Ethernet
Platform: Cisco 12000 series
The NetFlow feature is now a supported feature for Gigabit Ethernet (GE) line cards for the Cisco 12000 series Internet routers.
Per-VC Queueing
Platform: Cisco 12000 series
The per-virtual circuit (VC) queueing enhancements for the Quad OC-3c/STM-1c ATM line card provide additional control of traffic management on the line card. Within limits, you can adjust queuing priorities for each VC defined on a line card interface. This feature lessens traffic congestion and improves quality of service (QoS).
New Hardware Features in Cisco IOS Release 12.0(6)S
This section describes new and changed features in Cisco IOS Release 12.0(6)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(6)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
1OC-12/STM-4 SRP Line Card
Platform: Cisco 12000 series
The 1OC-12/STM-4 spatial reuse protocol (SRP) line card equips the Cisco series 12000 Internet routers with a total of two OC-12c, fiber-optic SC duplex ports. The line card provides two duplex SC connections for either the single-mode or multimode version. The Service Processing Element (SPE) payload is concatenated, which increases efficiency by eliminating the need to partition the bandwidth. The 1OC-12/STM-4 SRP line card is slot independent.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12012/bfrcfig/5929srp.htm
6DS3-SMB Line Card
Platform: Cisco 12000 series
The 6DS3-SMB line card consist of high-density DS3 service through six T3 interfaces.
The 6-port line card is a partially depopulated version of the 12-port line card. The 6-port line card consists of a total of 12 connectors. A single port consists of one coaxial connector for receiving (Rx) and one coaxial connector for sending (Tx). The ports on the 6-port line card are numbered 0 to 5.
The 6DS3-SMB line card supports serial encapsulation protocols, Internet router standard line card packet switching, and DS3 support. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_chan/6587ds3.htm
8-Port Fast Ethernet Line Card
Platform: Cisco 12000 series
The 8-Port Fast Ethernet line card provides eight Fast Ethernet (IEEE 802.3u) interfaces that operate at a full-duplex data rate of 100 Mbps each. This line card connects to the Internet router switch fabric, which supports transfer rates of up to 40 Gbps within the Internet router.
The 8-Port Fast Ethernet line card supports both copper and fiber-optic Fast Ethernet transceivers. The fiber-optic 100BASE-FX interface supports multimode SC duplex connectors operating in half- or full- duplex mode. The copper interface supports both full- and half-duplex 100BaseTX standards that use an RJ-45 connector.
The Fast Ethernet connectivity gives the Internet router platform the flexibility to be used as an edge router in high-bandwidth environments, such as an Internet service provider or a corporate backbone. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12012/bfrcfig/6224fe8.htm
NPE-175/NPE-225
Platform: Cisco 7200 series
The network processing engine is available in five versions: NPE-150, NPE-175, NPE-200, NPE-225, and NPE-300. The network processing engines have the same functionality; however, the performance differs because of the microprocessor type and the type of memory for packet data (SRAM and DRAM, or SDRAM) each network processing engine provides.
The latest network processing engines, the NPE-175 and NPE-225, consist of two modular boards: the processing engine and the network controller board. SRAM is not included in the NPE-175 or NPE-225.
OC-12c Dynamic Packet Transport Port Adapter
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The Dynamic Packet Transport (DPT) port adapter is a dual-width OC-12c port adapter that provides a shared IP over SONET capability in a Cisco 7200 series, Cisco 7200 VXR, or Cisco uBR7200 series router.
The DPT port adapter is designed to be deployed in SONET OC-12 DPT rings. DPT rings can also be connected to SONET add drop multiplexers (ADMs), thus allowing for the creation of small or very large DPT rings. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/7206/7206cfig/6481oc12.htm
PA-MC-2T3+ Multichannel T3 Port Adapter
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The PA-MC-2T3+ is a single-width port adapter that provides two T3 interface connections using BNC connectors. The interface can provide up to 28 T1 lines (a single T3 group). Each T1 line is presented to the system as a serial interface that can be configured as one or more serial interfaces.
The PA-MC-2T3+ is a channelized port adapter that sends and receives data bidirectionally at the T3 rate of 44.736 Mbps (digital signal carried on a T3 line, DS3). The T3 connection, provided by two female BNC connections for transmit (TX) and receive (RX), requires 734A coaxial cable that has an impedance of 75 ohms.
On the VIP2, PA-MC-2T3+ microcode is loaded into and operates from synchronous dynamic random-access memory (SDRAM) on the VIP2-50. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/7206/7206cfig/64452t3/index.htm
New Software Features in Cisco IOS Release 12.0(6)S
This section describes new and changed features in Cisco IOS Release 12.0(6)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(6)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Memory Scan
Platform: Cisco 7500/RSP series
The Memory Scan feature for Cisco 7500 series router Route Switch Processor (RSP) modules adds a low-priority background process that searches all installed DRAM for possible parity errors. The process runs every 60 seconds and can be controlled and monitored with new command-line interface commands. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/tmemscn.htm
NetFlow Policy Routing
Platform: Cisco 7500/RSP series
IP policy routing now works with Cisco Express Forwarding (CEF), distributed CEF (dCEF), and NetFlow.
IP policy routing was formerly supported only in fast switching and process-switching. Furthermore, support in fast switching was limited because the routing table sometimes had to be consulted before packets could be policy-routed, which was too expensive or impossible in the fast-switching path.
NetFlow on Internet Routers
Platform: Cisco 12000 series
NetFlow routing is now supported on the Cisco 12000 series routers. Support for NetFlow routing on the Gigabit Ethernet port adapter, PA-GE, is not yet available.
Process MIB
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The addition of the CISCO-PROCESS-MIB and changes to the CISCO-MEMORY-POOL-MIB allow the retrieval of additional CPU and memory statistics and their reporting by Sample Network Management Protocol (SNMP). The CISCO-PROCESS-MIB provides CPU 5-second, 1-minute, and 5-minute statistics. In addition, this MIB provides CPU utilization and memory allocation and deallocation statistics for each process on each CPU listed in the CISCO-PROCESS-MIB.
The CISCO-PROCESS-MIB is enabled when the first SNMP command is configured. The background statistics collection for Versatile Interface Processor (VIP) cards and the master CPU occurs even if the SNMP subsystem is not initialized.
SNMP Version 3
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Simple Network Management Protocol version 3 (SNMPv3) addresses issues related to the large-scale deployment of SNMP for configuration, accounting, and fault management. Currently SNMP is predominantly used for monitoring and performance management. The primary goal of SNMPv3 is to define a secure version of the SNMP protocol. SNMPv3 also facilitates remote configuration of the SNMP entities that make remote administration of SNMP entities a much simpler task. SNMPv3 builds on top of SNMPv1 and SNMPv2 to provide a secure environment for the management of systems and networks.
SNMPv3 provides an identification strategy for SNMP devices to facilitate communication only between known SNMP strategy. Each SNMP device has an identifier called the SNMP EngineID, which is a copy of SNMP. Each SNMP message contains an SNMP EngineID. SNMP communication is possible only if an SNMP entity knows the identity of its peer SNMP device.
SNMPv3 also contains a security model or security strategy that exists between an SNMP user and the SNMP group to which the user belongs. A security model may define the security policy within an administrative domain or an intranet. The SNMPv3 protocol consists of the specification for the User-based Security Model (USM).
Definition of security goals where the goals of message authentication service includes the following protection strategies:
•Modification of information, or protection against some unauthorized SNMP entity altering in-transit SNMP messages generated on behalf of an authorized principal
•Masquerade, or protection against attempting management operations not authorized for some principal by assuming the identity of another principal that has the appropriate authorizations
•Message stream modification, or protection against messages getting maliciously reordered, delayed, or replayed in order to effect unauthorized management operations
•Disclosure, or protection against eavesdropping on the exchanges between SNMP engines. Three different types of communication mechanisms are available for this protection strategy:
–Communication without authentication and privacy (NoAuthNoPriv)
–Communication with authentication and without privacy (AuthNoPriv)
–Communication with authentication and privacy (AuthPriv)
Turbo Access Control Lists
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The turbo access control lists feature enables Cisco 7200 and 7500 series routers, and Cisco 12000 series Internet routers to evaluate access control lists (ACLs) for more expedient packet classification and access checks.
New Hardware Features in Cisco IOS Release 12.0(5)S
This section describes new and changed features in Cisco IOS Release 12.0(5)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(5)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
Cisco 7576 Router
Platform: Cisco 7500/RSP series
The Cisco 7576 router is the newest member of the Cisco 7500 series of routers, which consists of the 5-slot Cisco 7505, 7-slot Cisco 7507, and the 13-slot Cisco 7513. The Cisco 7576 router supports multiprotocol and multimedia routing and bridging with a wide variety of protocols and any combination of available electrical interfaces and media.
The Cisco 7576 router consists of two independent routers configured on a single backplane. This system is housed within the chassis footprint of a Cisco 7513 router. The dual independent router design effectively doubles the system bandwidth that exists in the Cisco 7513 router.
Network interfaces reside on interface processors that provide a direct connection between the two independent dual CyBuses located on the backplane of the Cisco 7576 router and your external networks. The two independent dual CyBuses facilitate the configuration of two independent routers on a single backplane.
There are bays for up to two AC-input or DC-input power supplies. The Cisco 7576 router will operate with one power supply. Although a second power supply is not required, a second power supply allows load sharing and increased system availability. For further information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7576/index.htm
Gigabit Ethernet Interface Processor
Platform: Cisco 7500/RSP series
The Gigabit Ethernet Interface Processor (GEIP) is a single-port fixed configuration interface processor that, when combined with the appropriate fiber optic cable, provides one 1000-Mbps Gigabit Ethernet interface that complies with IEEE 802.032 standards.
The Gigabit Ethernet interface operates in full-duplex mode at 1000 Mbps in each direction: transmit (TX) and receive (RX).
The GEIP is available on all Cisco 7500 series routers and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI).
An increased maximum Ethernet packet size of 1500 takes advantage of increased bandwidth and the full-duplex point-to-point link.
An interface command maximum transmission unit (MTU) allows users to specify an MTU size up to 16K (maximum supported by FX1000). The minimum allowable MTU size is 1500 bytes.
If the interface is configured with a fall-back option, the other port will be reconfigured to support a large packet when a switchover occurs. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7000/7000cfig/5350geip.htm
Gigabit Ethernet Line Card
Platform: Cisco 12000 series
The Gigabit Ethernet line card provides Cisco 12000 series routers with an optical Ethernet interface on a single card that operates faster than 1 Gbps. The card interfaces with the switch fabric in the Cisco 12000 series router and provides one Gigabit Ethernet SC single-mode or multimode connection. This connection is concatenated, which provides for increased efficiency by eliminating the need to partition the bandwidth.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios112/ios112p/gsr/gigecr.htm
NPE-300
Platform: Cisco 7200 series
The network processing engine NPE-300 is the newest and the highest performance processor in the family of network processing engines for the Cisco 7200 series routers. The NPE-300 performs at a rate of approximately 300,000 packets per second (pps) in fast switching, a 50 percent increase over the NPE-200 performance.
The NPE-300 uses a high-performance 262.5-MHz R7000 RISC processor and can support up to 256 MB of memory, providing superior performance for both enterprise and service provider applications that require processor-intensive services. Network layer services such as traffic management, security, and QoS benefit significantly from the high performance of NPE-300.
A Cisco 7200 VXR router equipped with an NPE-300 can support up to six high-speed port adapters and can also support higher-speed port adapter interfaces including Gigabit Ethernet and OC-12 ATM. The NPE-300 uses synchronous DRAM (SDRAM) for storing all packets received or sent from network interfaces. The SDRAM also stores routing tables and network accounting applications. There are two independent SDRAM memory arrays in the system that allow concurrent access by port adapters and the processor. The NPE-300 can be configured with up to 256 MB of processor and packet memory, which is double the 128-MB memory limit on the NPE-200.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/core/7200vx/72vxicg/index.htm
PA-MC-8E1/120, PA-MC-4T1, PA-MC-8T1, and PA-MC-8DSX1 Multichannel E1 and T1 ISDN PRI Port Adapters
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The multichannel E1 and T1 ISDN PRI port adapters (PA-MC-8E1/120, PA-MC-4T1, PA-MC-8T1, and PA-MC-8DSX1) are available on Cisco 7200 series routers, Cisco 7500 series routers, and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI).
The PA-MC-8E1/120, PA-MC-4T1, and PA-MC-8T1 are single-wide modules that integrate channel service unit (CSU) functionality, data service unit (DSU) functionality, and E1 or T1 channel support into the Cisco router. The PA-MC-8DSX1 is a single-wide module that integrates DS1 DSU functionality and DS0 channel support into the Cisco router.
The PA-MC-8E1/120, PA-MC-4T1, PA-MC-8T1, and PA-MC-8DSX1 provide four or eight independent T1 (100-ohm) or E1(120-ohm) connections via RJ-48C connectors. Each T1 or E1 port adapter can provide up to 128 separate full-duplex High-Level Data Link Control (HDLC) fractional or full T1 or E1 channels. Individual T1 connections of the DSX-1 version of the port adapters can connect to external CSUs, to digital cross connects (DACS), or to any other equipment that uses a DSX-1 interface.
see the following documents for further information:
http://www.cisco.com/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/4815ds1p/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/5083e1p/index.htm
PA-MC-E3 Multichannel E3 Synchronous Serial Port Adapter
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The PA-MC-E3 Multichannel E3 synchronous serial port adapter is available on Cisco 7200 series routers, Cisco 7500 series routers, and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI). The PA-MC-E3 has one channelized E3 high-speed serial interface that provides access to services at E1 (2.048 Mbps) data rates, transferring data bidirectionally. This port adapter divides the E3 signal stream into 16 E1 lines that can be further divided to the 64-kbps level, up to a total of 128 channels. The PA-MC-E3 complies with Consultative Committee for International Telegraph and Telephone/International Telecommunication Union (CCITT/ITU) G.703 physical layer standards and CCITT/ITU G.751 for E3, G.742 for E2, and G.704 and G.706 for E1 fault and alarm detection and response actions. The E1 lines can be configured as channelized, fractional, and unframed. PRI ISDN will be supported in a later release.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios111/cc111/pamce3.htm
PA-MC-T3 Multichannel T3 Port Adapter
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The PA-MC-T3 Multichannel T3 port adapter is available on Cisco 7200 series routers, second-generation Versatile Interface Processor (VIP2) in Cisco 7500 series routers, and the Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI).
The PA-MC-T3 has one channelized T3 high-speed serial interface that provides access to services at T1 data rates, transferring data bidirectionally.
This port adapter divides the T3 signal stream into 28 T1 lines that can be further divided into the 64 kbps level, up to a total of 128 channels. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios111/cc111/pamct3.htm
New Software Features in Cisco IOS Release 12.0(5)S
This section describes new and changed features in Cisco IOS Release 12.0(5)S. Some features may be new to Cisco IOS Release 12.0S but were released in earlier Cisco IOS software releases. Some features may have been released in earlier Cisco IOS software releases and have been changed in Cisco IOS Release 12.0(5)S. To determine if a feature is new or changed, see the feature history table at the beginning of the feature module for that feature. Links to feature modules are included below. If a feature listed below 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 below.
ATM PVC Trap Support
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The ATM PVC Trap Support feature provides Simple Network Management Protocol (SNMP) notification for permanent virtual circuit (PVC) failures, and it provides SNMP access to PVC status tables.
Normally, a management station is not notified when an ATM PVC goes down. The ATM PVC Trap Support feature enables an agent to send the required PVC traps for this notification. It also provides support for these PVC status tables: atmCurrentlyFailingPVclTable and atmInterfaceExtTable.
Available Bit Rate Servicing and Virtual Path Shaping on PA-A3 Port Adapters
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The PA-A3 ATM port adapters (PA-A3-T3, PA-A3-E3, PA-A3-OC3MM, PA-A3-OC3SMI, and PA-A3-OC3SML) available on Cisco 7500 series routers now support the following new features:
•Available bit rate (ABR)—The ABR service category is specified in the ATM Forum Traffic Management Specification Version 4.0.
•Virtual Path Shaping—A virtual path (VP) is a logical association or bundle of virtual circuits (VCs).
The PA-A3 ATM port adapters support multiplexing of one or more VCs over a VP that is shaped at a constant bandwidth. To use this feature, you configure a permanent virtual path (PVP) with a specific virtual path identifier (VPI). Any VCs that are created subsequently with the same VPI are multiplexed onto this VP; the traffic parameters of individual VCs are ignored.
Command Line Interface String Search
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The command line interface (CLI) string search feature allows you to search or filter the output of any show or more command, which is useful for sorting through large amounts of output, or if you want to exclude output that you do not need to see. CLI string search also allows for searching and filtering at --More-- paging prompts.
With the search function, you can begin unfiltered output at the first line that contains a regular expression you specify. You can specify a maximum of one filter per command to either include or exclude output lines that contain the specified regular expression.
A regular expression is any word, phrase, number, and the like that appears in show or more command output.
Frame Relay Enhancements for K2 Scalability
Platforms: Cisco 7200 series, Cisco 7500/RSP series
The logging event command has been enhanced to enable or disable logging data-link connection identifier (DLCI) Change and subinterface UPDOWN console messages on Cisco 7200 and Cisco 7500 series routers. The logging event dlci-status-change and logging event subif-link-status commands are used to enable logging.
The display on the show frame-relay pvc command has been enhanced on Cisco 7200 and Cisco 7500 series routers to include a table showing the number of permanent virtual connections (PVCs) in their various states.
GRP Redundant Processor Support
Platform: Cisco 12000 series
The Gigabit Route Processor (GRP) redundant processor feature allows for the installation of two GRPs in a Cisco 12000 series Internet router. One GRP functions as the primary processor. The primary GRP supports all normal GRP operation. The other GRP functions as the secondary processor. The secondary GRP monitors the primary and will take over normal GRP operations if it detects a failure in the primary GRP. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios112/ios112p/gsr/gsr_rp.htm
ISL Support
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Inter-Switch Link (ISL) support maintains virtual LAN (VLAN) information as traffic flows between switches and routers. ISL support has been added to the following images for the Cisco 7000 family in Release 12.0(5)S: c7200-p-mz, c7200-k3p-mz, c7200-k4p-mz, rsp-pv-mz, rsp-k3pv-mz and rsp-k4pv-mz.
Multicast BGP
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Multicast Border Gateway Protocol (MBGP) feature adds capabilities to BGP to enable multicast routing policy throughout the Internet and to connect multicast topologies within and between BGP autonomous systems. That is, MBGP is an enhanced BGP that carries IP multicast routes. BGP carries two sets of routes, one set for unicast routing and one set for multicast routing. The routes associated with multicast routing are used by the Protocol Independent Multicast (PIM) to build data distribution trees.
It is possible to configure BGP peers that exchange both unicast and multicast network-layer reachability information (NLRI).
MBGP is useful when you want a link dedicated to multicast traffic, perhaps to limit which resources are used for which traffic. Perhaps you want all multicast traffic exchanged at one network access point (NAP). MBGP allows you to have a unicast routing topology different from a multicast routing topology. Thus, you have more control over your network and resources.
Prior to MBGP, the only way to perform interdomain multicast routing was to use the BGP infrastructure that was in place for unicast routing. If those routers were not multicast capable, or you had differing policies where you wanted multicast traffic to flow, you could not support it.
see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/mbgp.htm
Multicast Distributed Switching
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Prior to multicast distributed switching (MDS), IP multicast traffic was always switched at the Route Processor (RP) in the Route Switch Processor (RSP)-based platforms. With Cisco IOS Release 11.2 GS and Release 11.1 CC, IP multicast traffic can be distributed switched on RSP-based platforms with Versatile Interface Processors (VIPs).
Furthermore, MDS is the only multicast switching method on the Cisco 12000 Internet router, starting with Cisco IOS Release 11.2(11)GS.
Switching multicast traffic at the RP has the following disadvantages:
•The load on the RP is increased. This increase affects important route updates and calculations (for BGP, among others) and can stall the router if the multicast load is significant.
•The net multicast performance is limited to what a single RP can switch.
MDS solves these problems by performing distributed switching of multicast packets received at the line cards (VIPs in the case of an RSP, and line cards in the case of an Internet router). The line card is the interface card that houses the VIPs (in the case of RSP) and the Internet router line card (in the case of an Internet router). MDS is accomplished using a forwarding data structure called a Multicast Forwarding Information Base (MFIB), which is a subset of the routing table. A copy of MFIB runs on each line card and is always kept up to date with the RP MFIB table.
In the case of RSP, packets received on non-VIP interface processors are switched by the RP.
MDS can work in conjunction with Cisco Express Forwarding (CEF), unicast distributed fast switching (DFS), or flow switching. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios111/cc111/mds.htm
Multicast Routing Monitor
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
The Multicast Routing Monitor (MRM) feature is a management diagnostic tool that provides network fault detection and isolation in a large multicast routing infrastructure. It is designed to notify a network administrator of multicast routing problems in near real time.
MRM has three components that play different roles: the Manager, the Test Sender, and the Test Receiver. The Manager can reside on the same device as the Test Sender or Test Receiver. You can test a multicast environment using test packets (perhaps before an upcoming multicast event), or you can monitor existing IP multicast traffic.
You create a test based on various test parameters, name the test, and start the test. The test runs in the background and the command prompt returns. If the Test Receiver detects an error (such as packet loss or duplicate packets), it sends an error report to the router configured as the Manager. The Manager immediately displays the error report. Also, by issuing a certain show command, you can see the error reports, if any. You then troubleshoot your multicast environment as normal, perhaps using the mtrace command from the source to the Test Receiver. If the show command displays no error reports, the Test Receiver is receiving test packets without loss or duplicates from the Test Sender.
Multicast Source Discovery Protocol
Platforms: Cisco 7200 series, Cisco 7500/RSP, Cisco 12000 series
Multicast Source Discovery Protocol (MSDP) connects multiple Protocol Independent Multicast (PIM) sparse-mode (SM) domains. MSDP allows multicast sources for a group to be known to all rendezvous points (RPs) in different domains. Each PIM-SM domain uses its own RPs and need not depend on RPs in other domains. An RP runs MSDP over TCP to discover multicast sources in other domains.
An RP in a PIM-SM domain has an MSDP peering relationship with MSDP-enabled routers in another domain. The peering relationship occurs over a TCP connection, where primarily a list of sources sending to multicast groups is exchanged. The TCP connections between RPs are achieved by the underlying routing system. The receiving RP uses the source lists to establish a source path.
The purpose of this topology is to have domains discover multicast sources in other domains. If the multicast sources are of interest to a domain that has receivers, multicast data is delivered over the normal, source-tree building mechanism in PIM-SM.
MSDP is also used to announce sources sending to a group. These announcements must originate at the domain RP.
MSDP depends heavily on MBGP for interdomain operation. You should run MSDP in your domain RPs that act as sources, sending to global groups for announcement to the Internet. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/msdp.htm
Multiprotocol Label Switching Traffic Engineering
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Multiprotocol Label Switching (MPLS) traffic engineering software enables an MPLS backbone to replicate and expand upon the traffic engineering capabilities of Layer 2 ATM and Frame Relay networks. Traffic engineering is essential for service provider and Internet service provider (ISP) backbones. Such backbones must support a high use of transmission capacity, and the networks must be very resilient so that they can withstand link or node failures.
MPLS traffic engineering provides an integrated approach to traffic engineering. With MPLS, traffic engineering capabilities are integrated into Layer 3, which optimizes the routing of IP traffic, given the constraints imposed by backbone capacity and topology.
MPLS traffic engineering routes traffic flows across a network based on the resources the traffic flow requires and the resources available in the network.
MPLS traffic engineering employs "constraint-based routing," in which the path for a traffic flow is the shortest path that meets the resource requirements (constraints) of the traffic flow. In MPLS traffic engineering, the flow has bandwidth requirements, media requirements, a priority versus other flows, and so on.
MPLS traffic engineering gracefully recovers to link or node failures that change the topology of the backbone by adapting to the new set of constraints. see the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s5/mpls_ te.htm
RFC 1483 Bridged PVC Encapsulation
Platform: Cisco 12000 series
Using RFC 1483 bridged permanent virtual connection (PVC) encapsulation on a Cisco 12000 series router, an Internet router ATM interface can be connected directly to a Catalyst 5000 series switch ATM port. When configuring the Internet router ATM interface, you must create a new 1483 half-bridge PVC connection using a multipoint subinterface. Only one PVC half-bridge connection per subinterface is allowed; however, other non-PVC connections (SVC or nonbridged PVC) are allowed on the subinterface. Configure an maximum transmission unit (MTU) size of 1500 so that the Catalyst switch will not drop packets. Full bridging in the Internet router is not supported. Also note that Ethernet format is supported. IEEE 802.3 format is not supported at this time.
Secure Shell Version 1
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Secure Shell (SSH) is a protocol that provides a secure, remote connection to a router. Two versions of SSH are available, SSH Version 1 and SSH Version 2. Only SSH Version 1 is implemented in Cisco IOS software.
The SSH server feature enables an SSH client to make a secure, encrypted connection to a Cisco router. This connection provides functionality that is similar to an inbound Telnet connection. The SSH server in Cisco IOS will work with publicly and commercially available SSH clients.
Before SSH, security was limited to Telnet security. SSH allows strong encryption to be used with Cisco IOS authentication.
Tag Switching
Platforms: Cisco 7200 series, Cisco 7500/RSP series, Cisco 12000 series
Tag switching is a novel approach to network layer packet forwarding. The two main components of the tag switching architecture are forwarding and control. Forwarding is accomplished using simple label-swapping techniques, while the existing network layer routing protocols plus mechanisms for binding and distributing tags are used for control. Tag switching can retain the scaling properties of IP and can help improve the scalability of IP networks.
MIBs
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Limitations and Restrictions
The following sections contain limitations and restrictions in Cisco IOS Release 12.0S that can apply to the Cisco 7200 series, the Cisco 7500/RSP series, the Cisco 10720 Internet router, the Cisco 10000 series, and the Cisco 12000 series.
Limitations That Apply to Cisco IOS Release 12.0(31)S
This section describes limitations and restrictions that you should be aware of for Cisco IOS Release 12.0(31)S.
BITS limitations on a Cisco 12000 Series with 2.5-Gbps or 10-Gbps Switch Fabric
The following BITS limitation apply to a Cisco 12000 series that is configured with 2.5-Gbps or 10-Gbps switch fabric:
•The E1/T1 input for BITS inputs is not programmable.
•The input impedance can not be changed on BITS inputs.
•The BITS input sensitivity can not be changed.
Field Diagnostics on a Cisco 12000 Series with 2.5-Gbps or 10-Gbps Switch Fabric
Do not execute any field diagnostics commands on a Cisco 12000 series that is configured with 2.5-Gbps or 10-Gbps switch fabric.
Limitations That Apply to Cisco IOS Release 12.0(30)S
This section describes limitations and restrictions that you should be aware of for Cisco IOS Release 12.0(30)S.
PRP-2 Hard Drive
The hard drive of the Cisco 12000 series PRP-2 is not operational in Cisco IOS Release 12.0(30)S. The hard drive is operational in Release 12.0(30)S1 and later rebuilds of Release 12.0(30)S and in Release 12.0(31)S and later releases.
Limitations That Apply to Cisco IOS Release 12.0(28)S
This section describes limitations and restrictions that you should be aware of for Cisco IOS Release 12.0(28)S.
match atm-clp and set atm-clp Commands in AToM VCs
The match atm-clp class-map configuration command and the set atm-clp policy-map class configuration command are not supported for an Any Transport over MPLS (AToM) virtual circuit (VC) on a provider edge (PE) router that is configured with an enhanced ATM port adapter (ATM PA-A3) that has either a DS3/E3 interface or an OC3/STM1 interface when the ATM PA-A3 functions in any of the following modes:
•VC single and packed cell relay
•VP single and packed cell relay
•Port mode single and packed cell relay
Note that match atm-clp and set atm-clp commands are supported in the AAL5 VC mode.
Limitations That Apply to Cisco IOS Release 12.0(22)S
This section describes limitations and restrictions that you should be aware of for Cisco IOS Release 12.0(22)S.
Controlling the Rate of Logging Messages on the Cisco 10000 Series Edge Services Router
It is important that you limit the rate at which system messages are logged by the Cisco 10000 series edge services router (ESR). This avoids a situation where the router becomes unstable and the CPU is overloaded. Use the logging rate-limit command to control the output of messages from the system.
We recommend that you configure the logging rate-limit command as follows:
Router(config)#
logging rate-limit console all 10 except criticalThis command rate-limits all messages to the console to 10 per second, except for messages with critical priority (level 3) or greater.
For more information on the logging rate-limit command, see the Cisco IOS Configuration Fundamentals Command Reference.
Forwarding Memory on Cisco 12000 Series Engine 4 Line Cards
A Cisco 12000 series Engine 4 line card supports forwarding memory for approximately 200,000 Border Gateway Protocol (BGP) prefixes and 4000 Intermediate System-to-Intermediate System (IS-IS)/Open Shortest Path First (OSPF) prefixes, if each IS-IS/OSPF prefix is a multipath route. Higher numbers of prefixes are not supported.
ip cef accounting per-prefix Command and Per-Packet Load Balancing
When a Cisco 12000 series Engine 2 line card has Per-Packet Load Balancing (PPLB) configured, the ip cef accounting per-prefix interface configuration command is not supported.
Nested Policy Feature
The following is a list of limitations and restrictions for the Cisco 10000 series ESR nested policy feature:
•The total shape rate of all nested policies on an interface must be 64 kbps less than the total bandwidth of the interface. For example, the combined shape rate of nested policies on a DS1 Frame Relay interface must be 1472 kbps or less (1536 - 64).
•Nested policies support no more than two hierarchy levels.
•For additional restrictions and limitations on creating nested policies, see the "Configuring Nested Policies on the ESR" section of the Cisco document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/nest_pol.htm
•The nested-policy shape rate is reserved for nested-policy traffic only. Excess bandwidth is not used for other traffic.
•DotP marking is not supported, nor is 802.1P (including matching and marking the 802.1P header).
Note The actual shape rate applied to nested-policy traffic might differ from that specified in the policy. For example, a specified shape rate of 10.5 Mbps might be mapped to 11 Mbps. Use the command show policy-map interface command to determine the actual shape rate.
Testing Performance of High-Speed Interfaces on the Cisco 10000 Series Edge Services Router
The Cisco 10000 series edge services router (ESR) has multiple queues for all classes of traffic over high-speed interfaces. The software selects a queue on the basis of the source and destination address for the packet. This ensures that a traffic flow always uses the same queue and that the packets are transmitted in order.
When the Cisco 10000 series ESR is installed in a real network, the high-speed interfaces work efficiently to spread traffic flows equally over the queues. However, using single traffic streams in a laboratory environment may result in less-than-expected performance.
Therefore, to ensure accurate test results, you should test the throughput of the Gigabit Ethernet, Packet-over-SONET, or ATM uplink with multiple source or destination addresses.
Tip To determine if traffic is being properly distributed, use the show hardware pxf cpu queue command.
Important Notes
The following sections contain important notes about Cisco IOS Release 12.0S that can apply to the Cisco 7200 series, the Cisco 7500/RSP series, the Cisco 10720 Internet router, the Cisco 10000 series, and the Cisco 12000 series.
Deferrals
Cisco IOS software images are subject to deferral. Cisco recommends that you view the deferral notices at the following location to determine if your software release is affected:
http://www.cisco.com/kobayashi/sw-center/sw-ios-advisories.shtml
Field Notices and Bulletins
For general information about the types of documents listed in this section, see the following link:
http://www.cisco.com/public/support/tac/tools.shtml
•Field Notices—http://www.cisco.com/public/support/tac/fn_index.html
•Product Bulletins—If you have an account with Cisco.com, you can find product bulletins at http://www.cisco.com/warp/customer/cc/general/bulletin/index.shtml. If you do not have a Cisco.com login account, you can find product bulletins at http://www.cisco.com/warp/public/cc/general/bulletin/iosw/index.shtml.
Important Notes for Cisco IOS Release 12.0(33)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(33)S.
Cisco 12000 Series Routers Not Supported
Cisco 12000 series routers are not supported by Cisco IOS Release 12.0(33)S. Contact your Cisco representative for additional details.
Cisco 7202, Cisco 7204, and Cisco 7206 Routers Not Supported
Cisco 7202, Cisco 7204, and Cisco 7206 routers are not supported by Cisco IOS Release 12.0(33)S. Cisco 7204VXR and Cisco 7206VXR routers continue to be supported.
Important Notes for Cisco IOS Release 12.0(32)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(32)S.
6PE Support for VLANS
As of Cisco IOS Release 12.0(32)S, a Cisco 12000 series that functions as an IPv6 provider edge router (6PE) supports VLANs on a SIP-401, SIP-501, SIP-600, or SIP-601.
Important Notes for Cisco IOS Release 12.0(31)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(31)S.
Cisco 12000 Flash Memory
Until recently, the Cisco 12000 series Gigabit Route Processor (GRP-B) was shipped with a 20-MB flash card used as non-volatile memory to store Cisco IOS software images and configuration files. As of Cisco IOS Release 12.0(31)S, a larger flash memory is needed to contain and properly support all features.
If you already have a GRP-B with a 20-MB flash card and wish to run Cisco IOS Release 12.0(31)S or a later release, you must upgrade the flash card to a 64-MB flash card.
Note The currently shipping Performance Route Processors (PRP-1, PRP-2) already contain a 64-MB flash card as a default flash card.
Field Programmable Device Upgrade Tool for the Cisco 12000 Series
Starting in Cisco IOS Release 12.0(31)S, the Field-Programmable Device Upgrade Tool is supported for Cisco 12000 series routers that are configured with SIPs and SPAs. For detailed information about this tool, see the "Upgrading Field-Programmable Devices" section in the Cisco 12000 Series Router SIP and SPA Software Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_swcs/fpds/
12sfpd.htmFor information about the FPD image packages, see the "Shared Port Adapter FPD Image Packages for the Cisco 12000 Series" section on page 20.
Maximum Number of Egress QoS Policies Supported on a Cisco 12000 Series 4-Port Gigabit Ethernet ISE Line Card
Starting in Cisco IOS Release 12.0(31)S, the maximum number of egress quality of service (QoS) policies supported on each port of the Cisco 12000 series 4-port Gigabit Ethernet ISE line card is 511. The total number of egress QoS policies supported on all ports of a 4-port Gigabit Ethernet ISE line card is 1020. For more information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s25/
4ge_ise.htmImportant Notes for Cisco IOS Release 12.0(28)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(28)S.
Upgrading the Gold ROM Monitor Image for the Cisco 10720
For detailed information about this procedure, see the "Upgrading the Gold ROM Monitor Image" section in the Cisco IOS Software Configuration for the Cisco 10720 Internet Router document at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/107 20.htm
Important Notes for Cisco IOS Release 12.0(27)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(27)S.
Available Free Memory for Cisco 12000 Series Line Cards and Route Processors
Compared to Cisco IOS Release 12.0(26)S, the amount of free memory that is available in Release 12.0(27)S for a Cisco 12000 series line card or Route Processor has decreased slightly by about 16 MB.
Required Memory for Cisco 12000 Series Line Cards
Cisco 12000 series line cards with less than 128 MB of memory will not be able to complete the boot process when attempting to upgrade to Cisco IOS Release 12.0(27)S. If a memory upgrade is required, 256 MB is the next recommended configuration, with 128 MB as the minimum configuration requirement.
Important Notes for Cisco IOS Release 12.0(26)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(26)S.
ROMMON Upgrades for Cisco 12000 Series Line Cards
As of Cisco IOS Release 12.0(26)S, you can no longer upgrade the ROM monitor (ROMmon) version of a line card by entering the service upgrade all router configuration command.
Instead, to update the ROMmon version of a line card, enter the service upgrade rommon router configuration command.
Important Notes for Cisco IOS Release 12.0(24)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(24)S.
QA Error Recovery for the Cisco 7500 Feature Not Enabled By Default in Cisco IOS Release 12.0(24)S
For Cisco IOS Release 12.0(24)S1, Release 12.0(24)S2, and Release 12.0(24)S3, you must enable the QA Error Recovery for the Cisco 7500 feature by entering the following global configuration command:
hw-module main-cpu qaerror-recovery-enable
In all releases following Cisco IOS Release 12.0(24)S3—that is from Release 12.0(25)S on—the QA Error Recovery for the Cisco 7500 feature is enabled by default.
Important Notes for Cisco IOS Release 12.0(23)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(23)S.
Configuring MD5 Authentication for BGP Peering Sessions
This document provides general information about deploying MD5 authentication for a BGP session. You can configure MD5 authentication between two BGP peers, meaning that each segment sent on the TCP connection between the peers is verified. MD5 authentication must be configured with the same password on both BGP peers; otherwise, the connection between them will not be made. Configuring MD5 authentication causes the Cisco IOS software to generate and check the MD5 digest of every segment sent on the TCP connection. If authentication is invoked and a segment fails authentication, then an error message will be displayed in the console.
Old Behavior
In previous versions of Cisco IOS software, configuring MD5 authentication for a BGP peering session was generally considered to be difficult because the initial configuration and any subsequent MD5 configuration changes required the BGP neighbor to be reset.
New Behavior
This behavior has been changed in current versions of Cisco IOS software. CSCdx23494—integrated in Cisco IOS Release 12.0(23)S—introduced a change to MD5 authentication for BGP peering sessions. The BGP peering session does not need to be reset to maintain or establish the peering session for initial configuration or after the MD5 configuration has been changed. However, the configuration must be completed on both the local and remote BGP peer before the BGP hold timer expires. If the hold down timer expires before the MD5 configuration has been completed on both BGP peers, the BGP session will time out.
The following example enables the authentication feature between this router and the BGP neighbor at 10.108.1.1. The password that must also be configured for the neighbor is bla4u00=2nkq. The remote peer must be configured before the holddown timer expires.
router bgp 109
neighbor 10.108.1.1 password bla4u00=2nkq
When the password has been configured, the MD5 key is applied to the tcp session immediately. If one peer is configured before the other, the TCP segments will be discarded on both the local and remote peers due to an authentication failure. The peer that is configured with the password will print an error message in the console similar to the following:
00:03:07: %TCP-6-BADAUTH: No MD5 digest from 10.0.0.2(179) to 10.0.0.1(11000)
The time period in which the password must changed is typically the life time of a stale BGP session. When the password or MD5 key is configured, incoming TCP segments will only be accepted if the key is known. If the key is unknown on both the remote and local peer, the TCP segments will be dropped, and the BGP session will time out when the holddown timer expires.
If the BGP session has been preconfigured with a hold time of 0 seconds, no keepalive messages will be sent. The BGP session will stay up until one of the peers, on either side, tries to transmit a message (For example, a prefix update).
Note Configuring a new timer value for the holddown timer will only take effect after the session has been reset. So, it is not possible to change the configuration of the holddown timer to avoid resetting the BGP session.
Important Notes for Cisco IOS Release 12.0(22)S3
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(22)S3.
Cisco 7200 Series and Cisco 7000/7500 RSP Series Images Deferred
Six images were deferred in Cisco IOS Release 12.0(22)S3 because of severe defects. The following images are affected:
•c7200-k3p-mz
•c7200-k4p-mz
•c7200-p-mz
•rsp-pv-mz
•rsp-k3pv-mz
•rsp-k4pv-mz
The following defect caused the deferral of these images:
•CSCdz57007—vip/rp/7200/any alignment errors or reload, mpls feature path
The following defects did not cause the deferral of these images but are included in the solution:
•CSCdz67103—Provider router reloads on export v 9 and configuring export dest
•CSCdz67162—Alignment errors at rsp_feature_tagswitch
•CSCdz70504—Bus error crashes on VIP and RSP in tagswitching
This release has been replaced with the following software solution(s), which are available on Cisco.com:
•Cisco IOS Release 12.0(22)S4
In order to increase network availability, we recommend that you upgrade affected Cisco IOS images with the suggested replacement software images. Cisco will discontinue manufacturing shipment of affected Cisco IOS images. Any pending order will be substituted by the replacement software images.
Caution Please be aware that failure to upgrade the affected Cisco IOS images may result in network downtime.
The terms and conditions that governed your rights and obligations and those of Cisco, with respect to the deferred images will apply to the replacement images.
Important Notes for Cisco IOS Release 12.0(22)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(22)S.
Change in Behavior of the Wrap LED on the Cisco 10720 Internet Router
The behavior of the Wrap LED on the Cisco 10720 router has changed. In previous releases of Cisco IOS Release 12.0S and 12.0ST, the behavior was as follows:
•LED off: No wrap is performed.
•LED green: Local wrap is being performed.
In compliance with the latest specifications for Wrap LED behavior in products that are based on Spatial Reuse Protocol (SRP), the Wrap LED on the Cisco 10720 router now functions as follows:
•LED off: No wrap is performed.
•LED green: Wrap is being performed in the system. (Another station on the SRP ring is wrapped.)
•LED red: Port is in local wrap mode.
Cisco Discovery Protocol on the Cisco 10000 Series Edge Services Router
Unlike other Cisco routers, on the Cisco 10000 series edge services router the Cisco Discovery Protocol (CDP) is disabled by default. You can enable CDP on an interface using the cdp enable command.
Detection Mechanism for the MPLS Traffic Engineering (TE)—Fast Reroute (FRR) Node Protection, with RSVP Hellos Support Feature
When the detection mechanism for the MPLS Traffic Engineering (TE)—Fast Reroute (FRR) Node Protection, with RSVP Hellos Support feature is configured with a refresh interval and missed refresh limit that are too short, a neighbor may be declared down while the neighbor is actually up, and a warning message may be generated. To prevent this situation, configure the refresh interval and missed refresh limit in the following ways:
•Ensure that the interval-value argument in the ip rsvp signalling hello refresh interval interval-value command is 200 milliseconds or longer.
•Ensure that the msg-countip argument in the rsvp signalling hello [fast-reroute] refresh misses msg-count command has a value of 4 or more.
The detection interval for the detection mechanism should be at least 800 milliseconds (that is, 200 milliseconds of the interval-value argument multiplied by the value 4 of the msg-countip argument) or longer.
Frame Relay and PPP Sessions on the Cisco 10000 Series Edge Services Router
You can run up to 4000 Frame Relay sessions or 4000 PPP sessions, and you can configure up to 800 Border Gateway Protocol (BGP) peers on the Cisco 10000 series edge services router (ESR). The ESR also supports up to 512 Multilink Point-to-Point (MLP) protocol sessions and up to 1024 MLP bundles.
Performance Routing Engine 1 (PRE1) on the Cisco 10000 Series Edge Services Router
In order for Cisco IOS Release 12.0(22)S and later releases to run on the Cisco 10000 series edge services router, the Performance Routing Engine (PRE) installed in the chassis must be the PRE1 version (part number ESR-PRE1). You can verify which PRE is installed in the chassis by using the show version command.
Note The Cisco 10000 series ESR does not support mixing two different PRE revisions in the same chassis. Do not install a PRE and PRE1 in the same chassis.
set-overload-bit Command
The set-overload-bit command has new functionality that allows you to specify that the overload bit gets set upon system startup and remains set until Border Gateway Protocol (BGP) converges. For more details about this functionality, see the information about the set-overload-bit command at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fiprrp_r/1rfisis.htm
Support for Jumbo Frames on Cisco 12000 Series 3-Port Gigabit Ethernet Line Cards
The Cisco 12000 series 3-port Gigabit Ethernet line cards that are numbered from 73-4775-02 revision E0 and later and from 800-06376-01 revision E0 and later are now enabled to handle incoming packets of sizes till 9180 bytes (also referred to as Jumbo Frames) on the first two ports of the line cards. Older revision line cards can support maximum transmission unit (MTU) sizes up to 2450 bytes.
Upgrading Cisco IOS Software from Earlier Cisco IOS Releases on the Cisco 10000 Series Edge Services Router
Upgrading from Cisco IOS Release 12.0(21)SX or Release 12.0(21)SX1
If you are upgrading from Cisco IOS Release 12.0(21)SX or Release 12.0(21)SX1 to Cisco IOS Release 12.0(22)S, you must upgrade the eboot image on the Cisco 10000 series edge services router (ESR). If you fail to upgrade the eboot image, the ESR configuration may not load properly, and a checksum error appears on the console. If you are upgrading from an earlier Cisco IOS release, you do not need to upgrade the eboot image.
Upgrading from Cisco IOS Release 12.(14)SL or from Earlier 12.0(x)SL-based Releases
If you are upgrading from Cisco IOS Release 12.0(14)SL or from earlier 12.0(x)SL-based releases to Cisco IOS Release 12.0(22)S, save your current configuration file. If you decide to reinstall Release 12.0(14)SL or an earlier release, you must also reinstall the configuration file associated with that release. This is because some Border Gateway Protocol (BGP) configuration-file entries in Release 12.0(22)S are not compatible with Release 12.0(14)SL or earlier releases.
Note For specific information about upgrading the Cisco 10000 series ESR to a new software release, see the Cisco 10000 Series ESR Software Configuration Guide at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10ksw/
For general information about upgrading to a new software release, see the "Upgrading to a New Software Release" section on page 18.
VLAN Session Support on the Cisco 10000 Series Edge Services Router
In Cisco IOS Release 12.0(22)S, the Cisco 10000 series edge services router provides session support for 4000 802.1Q VLANs.
Important Notes for Cisco IOS Release 12.0(21)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(21)S.
Cisco 12000 Series Images Deferred in Cisco IOS Release 12.0(21)S
The Cisco 12000 series images (all gsr- images) have been deferred in Cisco IOS Release 12.0(21)S due to a severe defect. The software solution for these deferred images is Cisco IOS Release 12.0(21)S1, which is available on Cisco.com.
In order to increase network availability, we recommend that you upgrade affected IOS images with the suggested replacement software images. Cisco will discontinue manufacturing shipment of affected IOS images. Any pending order will be substituted by the replacement software images.
Note Please be aware that failure to upgrade the affected IOS images may result in network downtime.
The terms and conditions that governed your rights and obligations and those of Cisco, with respect to the deferred images will apply to the replacement images.
show ip bgp dampened-paths and show ip bgp flap-statistics Commands Replaced by show ip bgp dampening Command
The show ip bgp dampened-paths and show ip bgp flap-statistics commands have been replaced by the show ip bgp dampening [dampened-paths|flap-statistics|parameters] command in Cisco IOS Release 12.0(21)S. See the sample output below.
Router# show ip bgp dampening ?
dampened-paths Display paths suppressed due to dampening
flap-statistics Display flap statistics of routes
parameters Display details of configured dampening parameters
The functionality of the dampened-paths and flap-statistics keywords remains the same as in the show ip bgp dampened-paths and show ip bgp flap-statistics commands.
Note The show ip bgp dampened-paths and show ip bgp flap-statistics commands will still function in Cisco IOS Release 12.0(21)S. However, these commands are now hidden in the parser and will be removed from the parser eventually. The following message will be displayed when these commands are used:
% NOTE: This command will be deprecated soon. Please use 'show ip bgp dampening [dampened-paths|flap-statistics]'The parameters keyword introduces new functionality. The parameters keyword is used to display the details of configured dampening parameters. The following is sample output for the show ip bgp dampening parameters command:
Router# show ip bgp dampening parameters
dampening 10 1590 3000 30
Half-life time : 10 mins Decay Time : 1250 secs
Max suppress penalty: 12720 Max suppress time: 30 mins
Suppress penalty : 3000 Reuse penalty : 1590
Table 11 describes the significant fields.
Important Notes for Cisco IOS Release 12.0(19)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(19)S.
Configurable Throttling for Integrated IS-IS
As of Cisco IOS Release 12.0(19)S, integrated Intermediate System-to-Intermediate System (IS-IS) provides configurable throttling of link-state packet (LSP) protocol data unit (PDU) generation, Shortest Path First (SPF) calculations, and partial route computations (PRC). For information about the lsp-gen-interval command, spf-interval command, and prc-interval command, see the "Integrated IS-IS Commands" chapter of the Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2 and the "Configuring Integrated IS-IS" chapter of the Cisco IOS IP Configuration Guide, Release 12.2.
Memory Enhancements for the Cisco 12000 Internet Router Gigabit Route Processor
Cisco IOS Release 12.0(19)S supports the following memory enhancements to the Cisco 12000 Internet Router Gigabit Route Processor (GRP):
•Increased route memory (DRAM), from 256MB to 512MB
•Increased PCMCIA flash storage from 20MB up to 128M with the use of PCMCIA ATA flash disks.
Important Notes for Cisco IOS Release 12.0(18)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(18)S.
ip routing protocol purge interface Command
When a link goes down and an interface is removed from the routing table, the process that is triggered to remove all the related next-hop prefixes could slow down convergence time. When you enter the ip routing protocol purge interface command, capable routing protocols are allowed to quickly find and purge all routes that point to the interface that went down, and therefore improve network convergence time.
Example:
Router(config)#
ip routing protocol purge interfaceRequired Memory for Cisco 12000 Series Line Cards with Full Internet Routes
The required DRAM memory for Cisco 12000 series line cards is 128 MB. In some configurations in earlier 12.0S releases, line cards with only 64 MB of DRAM memory would still work with full Internet routes. As of Cisco IOS Release 12.0(21)S, all Cisco 12000 series line cards with full Internet routes do require 128 MB of DRAM memory and will not work properly with less than 128 MB of DRAM memory.
Important Notes for Cisco IOS Release 12.0(17)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(17)S.
Addition of show interfaces interface x/y controller Command
The show interfaces interface x/y command has been added to the command line interface (CLI) in Cisco IOS Release 12.0(17)S. This command will show the output of the show interface interface x/y command in addition to the output of the show controllers interface x/y command. This command is common for all interfaces and is available for the end user in EXEC mode.
Important Notes for Cisco IOS Release 12.0(16)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(16)S.
Cisco Express Forwarding Command Added
Cisco IOS Release 12.0(16)S adds support for the ip cef table adjacency-prefix override global configuration command. This command enables Cisco Express Forwarding (CEF) adjacency prefixes to override static host glean routes.
Important Notes for Cisco IOS Release 12.0(15)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(15)S.
Additional or Changed msdp Commands
When malicious sources spam traffic to Class D addresses, a large number of states may be created in multicast routers. These states may be propagated to other domains through Multicast Source Discovery Protocol (MSDP).
Cisco IOS Release 12.0(15)S introduces the ip msdp sa-limit [ peer-address | peer-name] limit configuration command to set a limit for the number of Source-Active (SA) messages that an MSDP speaker will accept from each of its peers.
SA messages in excess of the limit set for the peer will be discarded. A rate-limited syslog (once a minute) in the following form will inform the network administrator when SA messages are discarded:
ip20-36a(config)#ip msdp sa-limit 172.16.0.1 40
ip20-36a(config)#end
ip20-36a# ...
ip20-36a#
%MSDP-4-SA_LIMIT: SA from peer 172.16.0.1, RP 172.20.0.2 for (172.16.0.45, 192.168.0.1) exceeded sa-limit of 40
%MSDP-4-SA_LIMIT: SA from peer 172.23.0.3, RP 172.27.99.3 for (172.23.0.55, 192.168.2.23) exceeded sa-limit of 50In addition, the following existing commands have been enhanced:
•The show ip msdp summary EXEC command has been enhanced to show the number of SA messages learned from each peer. The following is an example of the enhancement:
ip20-36a#show ip msdp summary
MSDP Peer Status Summary
Peer Address AS State Uptime/ Reset SA Peer Name
Downtime Count Count
172.16.0.1 65001 Up 00:07:03 0 2500 R1
172.23.0.3 65003 Up 00:07:35 0 2500 R3
• The show ip msdp count EXEC command has been enhanced to show the number of SA messages learned from each peer. The following is an example of the enhancement:
ip20-36a#show ip msdp count
SA State per Peer Counters, <Peer>: <# SA learned>
172.16.0.1: 40
172.23.0.3: 50
SA State per ASN Counters, <asn>: <# sources>/<# groups>
Total entries: 90
65001: 40/1, 65003: 50/1
Cisco Express Forwarding Commands Added
Cisco IOS Release 12.0(15)S adds support for the following commands:
•The clear ip cef event-log EXEC command clears the Cisco Express Forwarding (CEF) event-log buffer.
•The clear ip cef inconsistency EXEC command clears CEF inconsistency statistics and records found by the CEF consistency checkers.
•The debug ip cef table privileged EXEC command enables the collection of events that affect entries in the CEF tables.
•The ip cef table consistency-check global configuration command enables CEF table consistency checker types and parameters.
•The ip cef table event-log global configuration command controls CEF table event-log characteristics.
•The show ip cef events EXEC command displays all recorded CEF forwarding information base (FIB) and adjacency events.
•The show ip cef inconsistency EXEC command displays CEF IP prefix inconsistencies.
Important Notes for Cisco IOS Release 12.0(14)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(14)S.
Cisco Express Forwarding Command Added
Cisco IOS Release 12.0(14)S adds support for the debug ip cef fragmentation privileged EXEC command. This command reports fragmented IP packets when Cisco Express Forwarding (CEF) is enabled.
Important Notes for Cisco IOS Release 12.0(13)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(13)S.
Cisco 7500/RSP Series Images Deferred
Four images were deferred in Cisco IOS Release 12.0(13)S because of severe defects. The following images are affected:
•rsp-boot-mz
•rsp-pv-mz
•rsp-k3pv-mz
•rsp-k4pv-mz
The following defects caused the deferral of these images:
•CSCds58988—Nested r4k_return_to_monitor calls, 75xx will not boot (HSA)
•CSCds58988—Nested r4k_return_to_monitor calls, 75xx will not boot (HSA)
•CSCds17084—MQC:change q-limit then remove the policy would cause RSP reload
•CSCds50637—changes in Cisco 12000 series ACL config may reduce performance
•CSCds30549—sh ip bgp summ shows incorrect number of received prefixes
•CSCds61573—ATMOC3-LC stops packet forwarding from 3PortGigE w/egress CAR cnfg
•CSCdr47814—ifTable ATM0/0.0 subinterface shows up w/o any pvcs configured
•CSCds62557—VIP4-50 performance
•CSCdr76940—MPLS loadsharing inconsistency for 0.0.0.0
•CSCds56717—sh tag for shows untagged while remote binding is available
•CSCdr42215—SRP needs to run service downl - fl to upgrade rom vers permanent
•CSCdp24155—ISIS: (route-leaking) local L2 interfaces not redistributed into L1
This release has been replaced with the following software solution(s), which are available on Cisco.com:
•12.0(13)S2
In order to increase network availability, we recommend that you upgrade affected Cisco IOS images with the suggested replacement software images. Cisco will discontinue manufacturing shipment of affected Cisco IOS images. Any pending order will be substituted by the replacement software images.
Caution Please be aware that failure to upgrade the affected Cisco IOS images may result in network downtime.
The terms and conditions that governed your rights and obligations and those of Cisco, with respect to the deferred images will apply to the replacement images.
Important Notes for Cisco IOS Release 12.0(12)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(12)S.
Cisco Express Forwarding Commands Added
Cisco IOS Release 12.0(12)S adds support for the ip cef load-sharing algorithm global configuration command, which selects a Cisco Express Forwarding (CEF) load-sharing algorithm, and the debug ip cef hash privileged EXEC command, which records CEF load-sharing hash algorithm events.
Important Notes for Cisco IOS Release 12.0(10)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(10)S.
Cisco Express Forwarding Command Modified
In Cisco IOS Release 12.0(10)S, the output display of the show cef linecard EXEC command has been modified.
Unicast RPF—New ACL Bypass and Logging Functions
Access Control List (ACL) functions have been added to the Unicast RPF feature that will allow new logging capability and exceptions to Unicast RPF checks. Interface-specific counters for Unicast RPF drops have been included in show ip interface.
The ip verify unicast reverse-path [acl] command enables the checking of source IP addresses in packets that are being Cisco Express Forwarding (CEF) or distributed Cisco Express Forwarding (dCEF)-switched. If the source IP address is known to be reachable through the interface from which the packet was received, the packet is forwarded. Otherwise, the packet is dropped and counted once on the interface over which the packet was received and once globally. The interface counter is part of the show ip interface interface output, and the global counter is part of the show ip traffic output.
Important Notes for Cisco IOS Release 12.0(9)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(9)S.
Cisco Express Forwarding Command Added
Cisco IOS Release 12.0(9)S adds support for the clear cef interface EXEC command. This command clears Cisco Express Forwarding (CEF) policy-statistics interface counters.
Important Notes for Cisco IOS Release 12.0(5)S
This section describes important issues that you should be aware of for Cisco IOS Release 12.0(5)S.
Cisco Express Forwarding Command Added
Cisco IOS Release 12.0(5)S adds support for the debug ip cef subblock privileged EXEC command. This command troubleshoots Cisco Express Forwarding (CEF) subblock events.
Posted: Fri Dec 14 17:17:08 PST 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.