Specifications

55
Release Notes for Cisco 7000 Family for Cisco IOS Release 12.1 T
78-10811-05
New and Changed Information
IP DSCP Marking for Frame-Relay PVC
Platforms: Cisco 7100 series, Cisco 7200 series, and Cisco 7500 series routers
The functionality of configuring a policy on a main or a subinterface to match and set IP type of service
(ToS) and differentiated services code point (DSCP) bits has existed in Cisco IOS Release 12.0S and
Cisco IOS Release 12.0(7)XE. This feature was introduced to Cisco IOS 12.1(2)T with the added
support of configuring a policy on an ATM PVC. This feature extends the support of Frame-Relay PVC
in Cisco IOS Release 12.1(5)T.
MPLS Class of Service Enhancements
Platforms: Cisco 7200 series and Cisco 7500 series routers
When a customer transmits IP packets from one site to another, the IP precedence field (the first three
bits in the header of an IP packet) specifies the class of service (CoS) such as latency or the percent of
bandwidth allowed for a particular class of service. The service provider might want to set an MPLS
packet's CoS to a different value.
CoS transparency 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 CoS is not changed as the packet travels through the multiprotocol label switching
(MPLS) network.
MPLS Egress NetFlow Accounting
Platforms: Cisco 7200 series and Cisco 7500 series routers
The MPLS egress NetFlow accounting feature allows you to capture Internet Protocol (IP) flow
information for packets undergoing MPLS label disposition; that is, packets that arrive on a router as
MPLS and are transmitted as IP.
Previously, 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, and thus 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 from one site of a VPN to another site
of the same VPN through the service provider backbone.
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.