Cisco IOS Release 12.3(14)YT

Available Languages

Download Options

This Cisco IOS
® Software special release is a short-lived release and will migrate into the second release of the 12.4T train. Six months after the migration into this 12.4T train, this release will no longer be orderable and will no longer be configurable in the dynamic configuration tool.

PRODUCT OVERVIEW

This product bulletin provides content and delivery information for Cisco IOS Software Release 12.3(14)YT. It should be used in conjunction with the product bulletin for Cisco IOS Software Release 12.4T. It supports Cisco
® 850 Series, 870 Series, 1800 Series (fixed-configuration and modular), and 2801 routers.

This product bulletin only lists Cisco IOS Software Release 12.3(14)YT features that are new to the respective routers; more information is available in the release notes. Customers should be prepared to upgrade using the migration path described in Figure 1.

VRF-aware Cisco IOS Firewall applies Cisco IOS Firewall capabilities to Virtual Routing and Forwarding (VRF) interfaces when the firewall is configured. This extends security service that can be managed by service providers. The VRF-aware Cisco IOS Firewall supports VRF-aware URL filtering and VRF-lite (also known as Multi-VRF CE).

The Advanced Application Inspection and Control feature augments the Cisco IOS Firewall to inspect TCP Port 80 and provides detailed policy control at an application level. It also recognizes traffic and follows state and protocol exchange of applications such as instant messaging applications.

MPLS assigns labels to packets for transport across packet- or cell-based ATM networks. The forwarding mechanism is label swapping, in which a label is assigned once at the edge of the MPLS network and removed at the other end. These labels are assigned to packets based on groupings or forward error corrections (FECs). Features include label imposition and disposition, label switching, label stacking (supports a five-label-deep stack), static labels, MPLS explicit null label, MPLS implicit null label, penultimate hop popping, label merging, and label stitching.

Label Distribution Protocol (LDP)

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 routing protocols. This feature adheres to the IETF standard and supports downstream unsolicited label advertisement as well as transport of LDP label switched paths (LSPs) over an RSVP-TE tunnel/LSP. This feature provides interoperable, standards-based dynamic LSP setup and teardown between MPLS-enabled devices from Cisco and third-party vendors. It provides best-effort path selection, and supports backward-compatibility with Tag Distribution Protocol (TDP)-based core networks, allowing interoperability with Cisco routers running TDP while allowing use of LDP only on Cisco OSR edge routers.

Resource Reservation Protocol (RSVP)

Provides explicitly created, source-routed path creation and teardown to provide guaranteed bandwidth reservation between two nodes, from end to end. Strict and loose explicit routes and bandwidth reservation are supported.

Weighted Random Early Detection (WRED)-Provides selective congestion control on a hop-by-hop basis. Uses a weighted average queue depth to determine drop probability. Drop thresholds are based on relative ToS, DSCP, or 802.1p values, as expressed in the MPLS EXP bits of the header.

Packet Marking, Policing, and Shaping

Committed Access Rate (CAR)-Used to classify and limit traffic according to predefined traffic policies, on ingress and egress from an interface.

RSVP CoS-Supports CoS for RSVP in adherence to IETF draft standards.

MPLS Traffic Engineering

MPLS Traffic Engineering

Supports RSVP-initiated traffic engineered tunnels, Open Shortest Path First (OSPF)-TE single area, and ISIS-TE single area.

TE-RSVP

RSVP in MPLS networks provides a quality of service (QoS) model designed to run over many technologies and optimized to support IP applications, both of which are necessary to build a consistent, workable, end-to-end IP QoS service.

Guaranteed Bandwidth Traffic Engineering (GB-TE) Tunnels

Extends MPLS Traffic Engineering capabilities to provide additional constraint-based routing and admission control. GB-TE builds upon traditional Traffic Engineering by introducing the concept of an additional class of service for specifically guaranteed bandwidth, enabling delivery of QoS services for customers that rely upon signaled QoS instead of provisioned QoS. This enables service providers to provide firm bandwidth commitments as a premium QoS service, and extends OSPF and ISIS to advertise available GB-TE bandwidth, in addition to available regular TE bandwidth.

MPLS DiffServ-Aware Traffic Engineering (DS-TE)

DS-TE is an enhancement to MPLS Traffic Engineering that introduces the concept of class types to Traffic Engineering. Each participating link advertises the amount of available bandwidth of each class type on that link. When the constraint-based routing process is executed for a new tunnel, a bandwidth constraint of a particular class type can be defined as one of the criteria to be used for the path selection. The admission control process carried using RSVP at each hop is performed against the available bandwidth of the specific class type.

Provides a mechanism to extend basic MPLS VPNs with the creation of point-to-point guaranteed bandwidth services with tightly defined and controlled QoS.

Interprovider VPN

Provides a mechanism for placing two or more MPLS provider edge devices into the same VPN, though each provider edge node might reside in a different autonomous system, with an EBGP connection between the two autonomous systems.

Provides a mechanism for supporting the concept of hierarchical VPNs by defining two new VPN layers for service provider networks-backbone carriers and customer carriers. The backbone carrier uses a VPN to carry all of the traffic of its customer carrier, which in turn is free to provision its own VPNs within the higher-level VPN to support its own customers.