Table Of Contents
Cisco IOS Software Configuration for the Cisco 10720 Internet Router
PXF Accelerated Cisco Express Forwarding
CEF Per-Destination Load Balancing
Load-Balancing Algorithms for CEF Traffic
Subsecond Link Loss Detection on Gigabit Ethernet Interfaces
Fast EtherChannel and Gigabit EtherChannel
Dynamic Packet Transport—Spatial Reuse Protocol
Modular Quality of Service Command-Line Interface
PXF Accelerated Cisco Express Forwarding Switching for IPv6
IPv6 Provider Edge Router over MPLS—Cisco 6PE
PXF Accelerated IPv6 Provider Edge Router over MPLS
PXF Accelerated IPv6 Extended ACLs
PXF Accelerated IPv6 Quality of Service
PXF Accelerated IPv6 Multicast
Any Transport over MPLS—Ethernet over MPLS
Pseudowire Emulation Edge-to-Edge MIBs
BGP Multipath Load Sharing for Both eBGP and iBGP in an MPLS VPN
MPLS Embedded Management—LSP Ping/Traceroute and AToM VCCV
MPLS Label Distribution Protocol
MPLS Multi-VPN Routing and Forwarding Tables
MPLS Traffic Engineering Fast Reroute
MPLS Virtual Private Networks—RFC 2547
MPLS VPN—Carrier Supporting Carrier
MPLS VPN—Carrier Supporting Carrier—IPv4 BGP Label Distribution
MPLS VPN—Interautonomous Systems
MPLS VPN—Inter-AS—IPv4 BGP Label Distribution
Multicast-VPN—IP Multicast Support for MPLS VPNs
MPLS VPN Carrier Supporting Carrier over IP Tunnels
Layer 2 Tunneling Protocol Version 3
L2TPv3 Ethernet-to-VLAN Internetworking
Integrated Routing and Bridging
Bidirectional Forwarding Detection
Unicast Reverse Path Forwarding Feature
Control Plane Policing Feature
Restrictions for Cisco IOS Software Configuration on the Cisco 10720 Internet Router
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Loading and Maintaining System Images
Upgrading the ROM Monitor Image
Configuring a CEF Load-Balancing Algorithm
Configuring a Fast Ethernet Interface
Configuring a Gigabit Ethernet Interface
Configuring an RPR-IEEE Interface
Configuring SRP Mode on a Packet-over-SONET or an RPR-IEEE Interface
Configuring RPR-IEEE Mode on an SRP Interface
Configuring Modular Quality of Service
Distribution of Remaining Bandwidth
MQC Bandwidth in Absolute Values
Single Rate 3-Color Marker for Traffic Policing
MQC Hierarchical Class Maps on the Cisco 10720 Internet Router
MQC Strict Priority Queue on the Cisco 10720 Internet Router
DiffServ Compliant Weighted Random Early Detection
Configuring Policy-Based Routing
Configuring 802.3x Flow Control
Configuring Unicast Reverse Path Forwarding
Configuring Control Plane Policing
Configuring an Ethernet Interface
Configuring a VLAN Subinterface
Testing Cable Problems on a Fast Ethernet Interface
Verifying a Fast Ethernet Interface
Verifying a Gigabit Ethernet Interface
Verifying an RPR-IEEE Interface
Verifying the DSCP Configuration in a Service Policy and Displaying Drop Statistics
Verifying Unicast Reverse Path Forwarding
Verifying Control Plane Policing
Monitoring and Maintaining the Router
ip verify unicast source reachable-via
show hardware access mac-address-table
test interfaces fastethernet tdr
upgrade rom-monitor invalidate
upgrade rom-monitor preference
Cisco IOS Software Configuration for the Cisco 10720 Internet Router
Part Number OL-8689-01 (Rev A0), April 8, 2008
Feature History
This feature module describes the Cisco IOS software configuration for the Cisco 10720 Internet router and includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
Monitoring and Maintaining the Router
Feature Overview
The Cisco 10720 Internet router is a high-performance Cisco IOS router that enables service providers to offer next-generation business class IP services in edge-specific customer-facing networks. The Cisco 10720 Internet Router is a 2-rack unit (RU), 2-slot router.
One slot supports an optical or blank (console-only) uplink card. The following uplink cards are available:
•
High-speed 2-port OC-48c/STM-16c Packet-over-SONET/SRP (POS/SRP) uplink card that allows you to change POS interfaces to DPT/SRP, and is available in the following versions:
–
Short Reach (SR) 2 km
–
Intermediate Reach (IR)15 km
–
Long Reach 1 (LR1) 40 km
–
Long Reach 2 (LR2) 80 km
•
Dual Mode IEEE 802.17 RPR/SRP uplink card that allows you to use the OC-48c/STM-16c interfaces in either SRP or Resilient Packet Ring (RPR)-IEEE mode.
The Dual Mode IEEE 802.17 RPR/SRP uplink card supports small form-factor pluggable (SFP) modules for its two OC-48c/STM-16c ports. The pluggable options are available in the following versions:
–
Short Reach (SR) 2 km
–
Intermediate Reach (IR) 15 km
–
Long Reach 2 (LR2) 80 km
•
High-speed 2-port OC-48c/STM-16c Spatial Reuse Protocol (SRP) uplink card available in the following versions:
–
Short Reach (SR) 2 km
–
Intermediate Reach (IR)15 km
–
Long Reach 1 (LR1) 40 km
–
Long Reach 2 (LR2) 80 km
•
Console/Auxiliary Module: a blank (console-only) module that allows you to customize the Cisco 10720 Internet Router as an Ethernet-only router. The second slot supports an Ethernet access card. The following access cards are available:
–
24-port 10/100 Ethernet TX card available in copper RJ-45
–
24-port 10/100 Ethernet FX card available in single-mode (SM) and multimode (MM) optical fiber
–
4-port Gigabit Ethernet 8-port 10/100BASE-TX access card (Revision A and Revision B versions)
Gigabit Ethernet access is provided using SFP technology. The following optical interfaces options are supported:
–
1000BASE-SX (short reach)
–
1000BASE-LX (intermediate reach)
–
1000BASE-ZX (long reach)
The router provides IP services close to the user, enabling you to better control and monitor admission to network resources. The small form factor of the router allows easy deployment in central locations, such as office towers, business complexes, and telecommunications carrier central offices.
Based on the Cisco Parallel eXpress Forwarding (PXF) Toaster-based architecture, the Cisco 10720 Internet router is a cost-effective, reliable platform that allows advanced edge-focused Cisco IOS features to be introduced simply, efficiently, and without a compromise in performance.
You can use the AutoInstall feature to connect a new Cisco 10720 Internet router to the network, turn on the new router, and have it configured automatically from a preexisting configuration file on a TFTP server. The AutoInstall process begins any time a Cisco IOS software-based device is turned on and a valid configuration file is not found in nonvolatile random-access memory (NVRAM).
•
Starting in Cisco IOS Release 12.0(22)S, the AutoInstall feature is supported on the 2-port OC-48c/STM-16c SRP and 2-port OC-48c/STM-16c POS/SRP uplink cards in SRP mode.
•
Starting in Cisco IOS Release 12.0(32)S, the AutoInstall feature is supported on the Dual Mode IEEE 802.17 RPR/SRP uplink card in SRP and RPR-IEEE mode.
For information about how to configure and use the AutoInstall feature, refer to Using AutoInstall and Setup.
Note
On the Cisco 10720 Internet router, the AutoInstall feature supports the Bootstrap Protocol (BOOTP) but does not support the Dynamic Host Configuration Protocol (DHCP) and Reverse Address Resolution Protocol (RARP).
Starting in Cisco IOS Release 12.0(27)S, you can increase the route processor (RP) memory in the router from 256 MB to 512 MB. Cisco IOS software running on a Cisco 10720 Internet router in which 512 MB of RP memory has been installed can then use up to 512 MB of memory. The increase in RP memory supports increasingly larger route tables and allows for more route table entries.
Note
A Cisco 10720 Internet router with 256 MB of RP memory supports only up to 256 MB of memory for Cisco IOS use, even when running Cisco IOS Release 12.0(27)S and later releases.
•
To verify the amount of memory on a Cisco 10720 Internet router available for Cisco IOS use, use the show version command.
•
To upgrade a Cisco 10720 Internet router in your network from 256 MB to 512 MB, you can purchase a memory upgrade kit.
For information about how to install the memory upgrade, refer to Cisco 10720 Internet Router Memory Replacement Instructions.
Supported Software Features
The software features described in this section are supported in Cisco IOS Release 12.0S on the Cisco 10720 Internet router.
PXF Accelerated Cisco Express Forwarding
Cisco Express Forwarding (CEF) is advanced Layer 3 IP switching technology. CEF optimizes network performance and scalability for networks with large and dynamic traffic patterns (such as the Internet) on networks characterized by intensive web-based applications or interactive sessions. Although you can use CEF in any part of a network, it is designed for high-performance, highly resilient Layer 3 IP backbone switching.
On the Cisco 10720 Internet router, CEF packet switching is enabled by default and is performed on IPv4 traffic by PXF using an accelerated fast-path. (For information about PXF-accelerated CEF switching of IPv6 traffic, see PXF Accelerated Cisco Express Forwarding Switching for IPv6.)
CEF Per-Destination Load Balancing
CEF 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. Load-balancing is performed on outbound interfaces
On the Cisco 10720 Internet router, per-destination load balancing is enabled by default with CEF. Per-destination load balancing allows the router to use multiple paths to achieve load sharing across multiple source-destination host pairs. Packets for a given source-destination host pair are guaranteed to take the same path, even if multiple paths are available. Traffic streams destined for different pairs tend to take different paths.
To use per-destination load balancing, you do not perform any additional tasks. Per-destination is the load balancing method of choice for most situations. Because per-destination load balancing depends on the statistical distribution of traffic, load sharing becomes more effective as the number of source-destination host pairs increases.
Per-destination load balancing ensures that packets for a given host pair arrive in order. All packets intended for a certain host pair are routed over the same link (or links).
Note
The Cisco 10720 Internet router supports only per-destination load balancing. Per-packet load balancing is not supported.
Load-Balancing Algorithms for CEF Traffic
The following load-balancing algorithms are supported for use with CEF traffic on the Cisco 10720 Internet router. To change the currently configured load-balancing algorithm, use the ip cef load-sharing algorithm command.
•
Original algorithm—The original 10720-specific, CEF load-balancing algorithm is based on a source and destination hash. Because the same algorithm is used on every router, distortions in load sharing across multiple routers may result. Traffic assigned to different paths by the default hash function may be polarized so that instead of creating two or more sub-flows to the destination, all traffic flows through only one router.
On the Cisco 10720 Internet router, the original load-balancing algorithm is the default. Depending on your network environment, you can select the universal algorithm. (The tunnel algorithm is not supported on the Cisco 10720 Internet router.)
•
Universal algorithm—The universal load-balancing algorithm allows each router on the network to make a different load sharing decision for each source-destination address pair, which resolves load-sharing imbalances. The router is set to perform universal load sharing by default.
•
Tunnel algorithm—The tunnel algorithm is designed to balance the per-packet load when only a few source and destination pairs are involved.
Note
The tunnel algorithm is not supported on the Cisco 10720 Internet router.
For information about how to switch between the original and universal load-balancing algorithms, refer to the Configuring a Load-Balancing Scheme for CEF Traffic chapter in the Cisco IOS IP Switching Configuration Guide, Release 12.4 at:
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a0080430ac3.html
Ethernet
•
Ethernet Advanced Research Projects Agency (ARPA) and Subnetwork Access Protocol (SNAP) MAC encapsulation.
•
On a 24-port Fast Ethernet TX access card or a Revision A 4-port Gigabit Ethernet 8-port 10/100BASE-TX access card, only the media-dependent interface crossed-over (MDI-X) cable connector setting is supported for a Fast Ethernet TX interface, except in Japan where the media-dependent interface (MDI) mode is also permitted and supported.
On a Revision B 4-port Gigabit Ethernet 8-port 10/100BASE-TX access card, both MDI and MDI-X modes, and an autoconfiguration mode (see the "media-type" section), are supported.
•
Time domain reflectometry (TDR) for troubleshooting Layer 1 CAT5 media on 10/100BASE-TX.
•
Autonegotiation for speed and duplex.
•
2000 MAC addresses per port for the Address Resolution Protocol (ARP); 48,000 MAC addresses per system.
•
Cisco IOS Ethernet features and command-line interface (CLI).
•
802.3x flow control on Gigabit Ethernet ports on the 4-port Gigabit Ethernet 8-port 10/100 Ethernet TX access card.
Subsecond Link Loss Detection on Gigabit Ethernet Interfaces
In Cisco IOS Release 12.0(26)S and earlier, link loss on Gigabit Ethernet interfaces was detected by periodically polling the hardware at 1-second intervals. This method resulted in a latency of up to 1 second after a link loss occurred before the loss is detected and a Layer 3 notification is sent. Starting in Cisco IOS Release 12.0(27)S, the subsecond link loss detection feature for the Cisco 10720 Internet router is introduced, which detects a link loss using a hardware interrupt mechanism. This mechanism allows Layer 3 to detect the loss within 50 ms or less from the time a link goes down.
Fast EtherChannel and 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 Internet router, the EtherChannel feature is supported on both Fast Ethernet (FE) and Gigabit Ethernet (GE) ports:
•
A maximum of eight Fast Ethernet interfaces can be bundled together in a Fast EtherChannel on the 24-port Ethernet access card.
•
A maximum of four Gigabit Ethernet 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 Internet Router as follows:
•
You configure quality-of-service (QoS) features on a Fast Ethernet or Gigabit Ethernet interface using the modular quality-of-service command-line-interface (MQC), as described in the "Configuring Modular Quality of Service" section. 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 each physical EtherChannel interface, bandwidth is allocated according to the percentage value used in the bandwidth, priority, and shape commands.
•
Fast and Gigabit EtherChannels do not support UTI, L2TPv3, and 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 do not have to be contiguous.
•
802.3ad link aggregation using the Link Aggregate Control Protocol (LACP) is not supported on the Cisco 10720 Internet router.
•
When an individual EtherChannel link fails, traffic is redistributed to the remaining active links.
•
An output Fast Ethernet or Gigabit Ethernet port is selected using a hashing algorithm that is based on the source and destination addresses. Therefore, one IP flow is always sent out on the same port so that packet sequencing issues are avoided.
Note
This hashing mechanism may result in unequal distribution with a small number of source-destination pairs. The load balancing depends on the statistical distribution of traffic. Load sharing becomes more effective as the number of source-destination pairs increases.
To determine if the traffic is well-balanced, use the show interface command and, in the command output, compare the output rate and number of packets and bytes in the output on all operational physical links of the channel bundle.•
802.1Q VLANs are supported on Fast EtherChannel and Gigabit EtherChannel interfaces.
For more information about how to configure and use the EtherChannel feature, refer to:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios111/ca111/fechan.htm.
Dynamic Packet Transport—Spatial Reuse Protocol
The following Spatial Reuse Protocol (SRP) features are supported on Dynamic Packet Transport (DPT) uplink cards used in the Cisco 10720 Internet Router. For information about how to configure and use DPT/SRP features, refer to the Spatial Reuse Protocol document at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
srpapsgs.htm.
Note
SRP is the underlying technology used in the Cisco Dynamic Packet Transport family of products.
•
Versatile Optical Interface (VOI) on the 2-port OC-48c/STM-16c POS/SRP uplink card (allows you to change Packet-over-SONET [POS] interfaces to DPT/SRP mode)
•
Nine uplink card options with 2-, 15-, 40-, and 80-km reach capability available in either SRP-only or POS/SRP (VOI) mode, and a blank uplink card for Ethernet use only
•
SONET OC-48/Synchronous Digital Hierarchy (SDH)-16 compliance
•
IP/DCC management interface
•
Spatial Reuse Protocol (SRP) intelligent protection switching (IPS) IPS wrap-time less than 50 ms
•
SRP rate-limiting for transmitted (TX) traffic using high- and low-priority queues
•
SRP priority slicing for TX traffic
•
SRP-fa (SRP fairness algorithm)
•
9K maximum transmission unit (MTU)
•
SRP hold-off timer for protected SONET
•
SRP mandatory Management Information Base (MIB) objects
•
SRP optional MIB objects
Note
In Cisco IOS 12.0(21)ST, 12.0(21)SP, and later releases, the srp count and show srp source-counters commands are not supported on the Cisco 10720 Internet router due to a hardware limitation. As a result, the feature for counting packets from an SRP interface does not function correctly.
SRP—Layer 3 Fast Notification
Starting in Cisco IOS Release 12.0(27)S, the SRP—Layer 3 Fast Notification feature is supported on the Cisco 10720 Internet router. This feature enables faster convergence of Layer 3 routing protocols in case of SRP ring events that cause nodes to be dropped from the ring topology.
In Cisco IOS Release 12.0(26)S and earlier releases, a node failure in an SRP ring causes ring wrap to occur around the failed node. Traffic flow from other nodes in the ring to the failed node continues, even if there is an alternative path, until the Internal Gateway Protocol (IGP) reconverges. The traffic is interrupted for seconds because the SRP node failure is transparent to Layer 3 protocols and IP convergence takes the normal time based on routing updates.
With the Layer 3 Fast Notification feature, changes in the topology map of an SRP ring are reported immediately to Layer 3 protocols. The Layer 3 hello and routing update timers are bypassed, resulting in Layer 3 subsecond convergence.
On the Cisco 10720 Internet Router, the SRP—Layer 3 Fast Notification feature applies only to the Open Shortest Path First (OSPF) or Intermediate System-to-Intermediate System (IS-IS) routing protocols.
Also, when the Single Ring Recovery (SRR) protocol is enabled, faster convergence of Layer 3 routing protocols does not occur. The SRR protocol enables an 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.
Resilient Packet Ring
Starting in Cisco IOS Release 12.0(29)S, the IEEE 802.17 Resilient Packet Ring (802.17 RPR) protocol is supported on the Cisco 10720 Internet router. 802.17 RPR is a metropolitan area network (MAN) technology that supports data transfer between stations interconnected in a dual-ring configuration. It is an independent protocol with many similarities to SRP, but offers a much larger domain of configurability and control. RPR uses a new interface that is maintained across all platforms to ensure consistency between solutions.
The Cisco 10720 Internet router supports the following RPR features:
•
Protection: Wrapping and steering protection modes
Wrapping is a ring protection mode in which the two stations on either end of a failed span react by wrapping traffic back onto the opposite ringlet to reach the destination. 802.17 RPR wrapping is similar in behavior to SRP wrapping.
In steering protection mode, stations that detect a failed span notify all other stations in the ring. Each individual station is then responsible for "steering" traffic away from the failed span to reach the destination. Steering requires that every station determines the location of the failure to avoid the failed span. Compared to wrapping protection mode, steering can be slower to converge in large topologies.
•
Traffic: Relaxed and strict traffic modes
Relaxed mode does not flush (drop) traffic in case of a protection event, such as a fiber failure. As a result, there is less traffic loss but a slight possibility of re-ordering packets during a node recovery. Relaxed mode is the default traffic mode. Strict mode flushes traffic after a topology change, such as a protection event, until the topology stabilizes.
In case of a topology change caused by a ring failure:
–
Relaxed traffic is redirected based on the protection setting as quickly as possible. In some cases, relaxed traffic arrives out of order or is duplicated, but results in less traffic loss during node recovery than strict traffic mode.
–
Strict traffic is flushed from the ring until the ring topology recovers and is stable. In this way, a possible duplication or re-ordering of strict traffic is prevented. Strict traffic mode results in greater traffic loss than relaxed mode during the topology change.
You configure the traffic mode as relaxed or strict on a per-router basis. Topology stability is determined using the settings of the Topology Checksum and Context Containment features of the 802.17 RPR protocol.
•
Fairness: Weighted
Fairness ensures proper partitioning of opportunistic traffic. Weighted fairness allows a weighted fair access to available ring capacity and operates in two modes:
–
When the weights of all stations are equal (default mode sets all weights to 1), fairness is not modified by weight.
–
If the weight of a station is modified, weighted fairness allocates more bandwidth to the station based on its relative weight in the domain impacted by congestion.
•
Fairness rate adjustment: Aggressive and conservative modes
Aggressive rate adjustment reacts very quickly to changes in bandwidth use, resulting in optimal bandwidth use during a congestion condition on the ring. However, small fluctuations of bandwidth in very bursty traffic situations may occur.
An alternative method used to adjust the fairness rate on an RPR interface is conservative mode, which ramps up in stages (over a few hundred milliseconds) when bandwidth is available and ramps down in stages (over a few hundred milliseconds) when congestion occurs. Compared to aggressive rate adjustment, conservative mode results in slower ramping and in slightly lower bandwidth utilization, but is more applicable in very bursty traffic scenarios.
•
Service classes: Classes A and C are supported for classifying traffic.
Class A marks the highest-priority and lowest-latency traffic, is not subject to fairness controls, and is divided into Reserved and High priority traffic queues. Class C marks the lowest priority traffic using secondary queues, and is subject to fairness controls.
•
Maximum transmission unit (MTU): Jumbo and regular sizes supported
Jumbo MTU mode provides an operating MTU of 9100 bytes to each station on the ring.
Starting in Cisco IOS Release 12.0(30)S, the regular MTU of 1500 bytes is supported as the default MTU size.
•
Congestion history report
Starting in Cisco IOS Release 12.0(30)S, you can generate a report for traffic congestion events on the ring by using the show rpr-ieee fairness history command. This command reports the congestion status for a station over ninety-six time intervals of 15 minutes each (24 hours).
•
802.17 MIB support
•
802.17 Echo feature
The Operation, Administration, and Maintenance (OAM) echo feature for 802.17 RPR functions as a test feature for ring connectivity. Use the 802.17 echo feature to debug and resolve Layer 2 issues. The ping rpr-ieee echo command is similar to a ping command.
For information about how to configure and use RPR features, refer to IEEE 802.17 Resilient Packet Ring Feature Guide at: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/
rprs wg.htmPacket-over-SONET
On the Cisco 10720 2-port OC-48c/STM-16c POS/SRP uplink card, standard Cisco IOS Packet-over-SONET, Point-to-Point Protocol (PPP), and High-Level Data Link Control (HDLC) commands are supported.
The 2-port OC-48c/STM-16c POS/SRP uplink card allows you to use the Cisco 10720 Internet router to:
•
Send IP packets directly over SONET/SDH frames.
•
Interwork with the OC-48c/STM-16c POS/SDH line cards in Cisco 12000 series Internet routers and configure each side of a Spatial Reuse Protocol (SRP) ring as a POS interface.
•
Interwork with add-drop multiplexers (ADM) that provide SONET Automatic Protection Switching (APS) for line and card redundancy.
For detailed information about the POS commands supported on Packet-over-SONET interfaces on the Cisco 10720, refer to the relevant sections of the following documents:
•
Configuring the OC-48 POS Line Card
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7300/linecard/oc_12379/3438cnf.htm•
Configuring Clock Settings on POS Router Interfaces
http://www.cisco.com/warp/public/127/POS/posclocking_16181.html•
Routing Updates over APS on POS Interfaces
http://cco/warp/public/127/aps_routing_16142.html•
Understanding the APS Reflector Channel
http://cco/warp/public/127/refl_chan_16143.htmlFor information about using HDLC and PPP commands on Packet-over-SONET interfaces on the Cisco 10720 Internet router, refer to Configuring a Synchronous Serial Interface at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/finter_c/
icfserin.htm#xtocid7.Internet Protocol
The Internet Protocol (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.
The Cisco 10720 Internet router supports the following IP features:
•
Basic IPv4 forwarding with all Cisco IOS routing protocols
–
OSPF, IS-IS, BGP4, IGRP, EIGRP, RIP, RIPv2
–
OSPF Support for Fast Hello Packets allows you to configure the sending of hello packets in intervals less than 1 second. OSPF hello packets are packets that an OSPF process sends to its OSPF neighbors to maintain connectivity with those neighbors. For information about how to configure the interval (in seconds) at which the hello packets are sent, refer to OSPF Support for Fast Hello Packets.
•
All Cisco IOS routing multicast protocols
–
PIM SM, PIM DM, MSDP, MBGP, anycast RP, IGMPv1, IGMPv2
•
IP fragmentation
•
Unicast reverse path forwarding (uRPF)
•
Cisco IOS security features—TACACS+, Kerberos, Radius, and Cisco IOS privilege levels
•
SNMP support
•
Cisco Globally Resilient IP (GRIP)
Modular Quality of Service Command-Line Interface
The Cisco 10720 Internet router supports the modular QoS command-line interface (MQC) to create traffic polices and attach these polices to interfaces. A traffic policy contains a traffic class and one or more QoS features. A traffic class is used to classify traffic, while the QoS features in the traffic policy determine how to treat the classified traffic.
The following MQC features are implemented on the Cisco 10720 Internet router:
•
Default queuing functionality (FIFO)
–
Two queues per Ethernet interface (default and network control)
–
Two queues per SRP interface (default and network control) and one SRP control queue
–
Two queues per Packet-over-SONET (POS) interface (default and network control)
•
User-configurable queues:
•
One priority queue
•
Up to eight fair or shaped queues, including the default queue and the priority queue. Only one priority queue is supported.
•
Queue classification (matching)
–
Access control list, input interface, QoS group, IP precedence, IP DSCP, IP RTP port
•
Queue action (marking)
–
IP precedence, IP DSCP, SRP priority, QoS group
•
Traffic policing (CAR)
•
Weighted Random Early Detection (WRED)
•
Scheduling controlled by VTMS (Versatile Traffic Management System)
•
QoS policy propagation (QPPB) with the Border Gateway Protocol (BGP)
NetFlow
NetFlow provides highly granular per-flow traffic statistics in a Cisco router. A flow is a unidirectional set of packets that are received on the same subinterface. The packets have the same source and destination IP addresses, Layer 4 protocol, TCP/UDP source and destination ports, and the same type of service (TOS) byte in the IP headers. The router accumulates NetFlow statistics in a NetFlow cache and can export them to an external device (such as the Cisco CNS NetFlow Collection Engine) for further processing.
Sampled NetFlow
The Cisco 10720 Internet router supports Sampled NetFlow through Cisco IOS Release 12.0(28)S.
Sampled NetFlow allows you to sample one from a specified number of IP packets 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 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, refer to:
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 Internet 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 by Parallel eXpress Forwarding (PXF).
•
An snf counter in the output of 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. (On the Cisco 12000 series Internet router, you can only use the ip flow ingress command to enable Sampled NetFlow on a subinterface. The command has no effect on a main interface.)
Note
The ip route-cache flow command is not supported on the Cisco 10720 Internet router.
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.Changing to Random Sampling Method
Starting in Cisco IOS Release 12.0(29)S, the NetFlow sampling method supported on the Cisco 10720 Internet router has changed from deterministic (used in Sampled NetFlow) to random sampling without any changes in the configuration commands. You use the same configuration procedure that you use to configure Sampled NetFlow.
Random sampling gathers NetFlow data for a subset of traffic in a Cisco router by processing only one randomly selected packet from n sequential packets, where n is a user-configurable parameter. Packets are sampled as they arrive (before any NetFlow cache entries are made for those packets). Statistical traffic sampling substantially reduces consumption of router resources (especially CPU resources) while providing valuable NetFlow data.
The capability to sample packets was first provided using deterministic sampling by the Sampled NetFlow feature. Deterministic sampling selects every nth packet for NetFlow processing on a per-interface basis. For example, if you set the sampling rate to 1 out of 100 packets, then Sampled NetFlow samples the first, 101st, 201st, 301st, and so on packets. Because Sampled NetFlow does not allow random sampling, statistics can be inaccurate when traffic arrives in fixed patterns. Random Sampled NetFlow is more statistically accurate than Sampled NetFlow.
Note
Although the Cisco 10720 Internet router supports the random sampling method for collecting NetFlow data in Cisco IOS Release 12.0(29)S and later releases, the Random Sampled NetFlow feature and all configuration commands used to create NetFlow sampler maps are not supported. For information on the Random Sampled NetFlow feature, refer to Random Sampled NetFlow at: http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_2/
nfstatsa.htm
IP Version 6 Support
IPv6, formerly called IPng (next generation), is the latest version of IP. IPv6 offers many benefits, such as a larger address space over the previous version of IP (Version 4).
On the Cisco 10720 Internet router, most IPv6 features forward packets through the route processor (through the CPU), instead of using the Parallel eXpress Forwarding (PXF) processor for fast-path switching (packet and route processing) as IPv4 features do. Only the following IPv6 features use PXF for accelerated fast-path forwarding:
•
PXF Accelerated Cisco Express Forwarding Switching for IPv6
•
PXF Accelerated IPv6 Provider Edge Router over MPLS
•
PXF Accelerated IPv6 Extended ACLs
•
PXF Accelerated IPv6 Quality of Service
•
PXF Accelerated IPv6 Multicast
For information about how to configure and use these IPv6 software features on the Cisco 10720 Internet router, refer to the Cisco documents at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/
index.htm.For information about all IPv6 features supported in the 12.0 S Cisco IOS software train, refer to:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/
ftipv6s.htm.The Cisco 10720 Internet router supports the following IPv6 features:
•
IPv6 unicast routing
•
IPv6 services:
–
DNS lookups over an IPv4 transport
–
DNS lookups over an IPv6 transport
–
TFTP
–
Automatic IPv6 tunnels
–
Manual IPv6 tunnels
–
6to4 tunnels
–
Path MTU discovery
–
Internet Control Message Protocol version 6 (ICMPv6)
–
Neighbor discovery
–
Static cache for IPv6 neighbor discovery
–
Packet internet groper (ping)
–
Extended Access Control List (eACL)
The eACL feature extends the standard IPv6 ACL functionality 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 of 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; permit and deny conditions in an ACL are defined by using the permit and deny 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, refer to: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/
ftipv6o.htm#1029667.–
Stateless configuration
–
Telnet
–
Traceroute
•
Data link layer protocols
–
Ethernet, Fast Ethernet, and Gigabit Ethernet
–
Cisco High-Level Data Link Control
–
PPP over Packet-over-SONET interfaces
–
Spatial Reuse Protocol (SRP)/Dynamic Packet Transport (DPT)
–
Use of the first MAC address as the IPv6 interface identifier for point-to-point links
–
VLANs using IEEE 802.1Q encapsulation
•
Routing protocols
–
Integrated IS-IS for IPv6
–
IPv6 RIP enhancements
–
Link-local address peering in multiprotocol BGP extensions for IPv6
–
Multiprotocol BGP extensions for IPv6
–
OSPFv3
–
RIP for IPv6
–
Static routes
–
Route distribution
PXF Accelerated Cisco Express Forwarding Switching for IPv6
On the Cisco 10720 Internet router, Cisco Express Forwarding Switching for IPv6 is performed by PXF using an accelerated fast-path for the following types of IPv6 packets:
•
IPv6 header + payload
•
IPv6 header + Transmission Control Protocol (TCP)/User Datagram Protocol (UDP) parameters + payload
•
IPv6 header + fragment option header + payload
•
IPv6 header + fragment option header + TCP/UDP parameters + payload
All of these IPv6 packet types that match an eACL entry are also switched by PXF using the accelerated fast-path. However, all other IPv6 packets are managed by the CPU using the route processor path, including:
•
IPv6 packets set with other options besides the fragment option
•
All IPv6 control packets
•
IPv6 packets whose Layer 4 protocol is not TCP or UDP
•
IPv6 ICMP packets that are processed and generated
For more information about how to use CEF, refer to: http://www.cisco.com/univercd/cc/td/doc/product/software/ios112/ios112p/gsr/cef.htm
IPv6 Provider Edge Router over MPLS—Cisco 6PE
The Cisco 6PE feature allows service providers 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.
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. A PE router applies an appropriate label for the address in the packet to reach the other side of the MPLS backbone. This function 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.
On the Cisco 10720 Internet router, the IPv6 Provider Edge Router over MPLS feature is performed by PXF using an accelerated fast-path. For more information about the Cisco 6PE feature, refer to:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/
ftipv6o.htm#1026998.PXF Accelerated IPv6 Provider Edge Router over MPLS
The IPv6 Provider Edge Router over MPLS—Cisco 6PE feature is performed with the fast-path forwarding provided by PXF.
PXF Accelerated IPv6 Extended ACLs
The Extended Access Control List (eACL) feature for IPv6 is also performed on the Cisco 10720 Internet router using the fast-path forwarding provided by PXF.
Note
IPv6 ACL logging is not supported.
PXF Accelerated IPv6 Quality of Service
Quality-of-service (QoS) features, including packet classification, queuing, traffic shaping, WRED, class-based packet marking, and policing of IPv6 packets, are supported in IPv6 environments using PXF for accelerated fast-path forwarding.
All of the QoS features available for IPv6 environments are managed from the modular QoS command-line interface. The MQC allows you to define IPv6 traffic classes, create and configure traffic policies (policy maps) for IPv6 traffic, and then attach those traffic policies to interfaces.
For packet classification, the match protocol {ip | ipv6} command is introduced to classify IPv6 packets for QoS policies. For more information, see match protocol.
For information about how to configure QoS policies in IPv6 environments, refer to Implementing QoS for IPv6 for Cisco IOS Software.
For documentation on MQC configuration commands and tasks, and for general information on how to use the MQC, refer to Modular Quality of Service Command-Line Interface and Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.3.
PXF Accelerated IPv6 Multicast
IPv6 multicast allows a host to send one data stream to a subset of all hosts (group transmission) simultaneously, instead of only to one host (unicast transmission) or to all hosts (broadcast transmission).
To enable IPv6 multicast routing, you must:
•
Enable IPv6 unicast routing on the router as described in Implementing Basic Connectivity for IPv6.
•
Enable IPv6 multicast routing on all interfaces as described in Implementing IPv6 Multicast.
On the Cisco 10720 Internet router, PXF-accelerated IPv6 multicast forwarding is supported on the following modules:
•
4-port Gigabit Ethernet 8-port 10/100BASE-TX access card
•
24-port Ethernet 10/100BASE-TX access card
•
24-port Ethernet 10/100BASE-FX access card
•
2-port OC-48c/STM-16c POS/SRP uplink card in DPT/SRP mode
•
Dual Mode IEEE 802.17 RPR/SRP uplink card in SRP and RPR-IEEE mode
Note
On the 10720, PXF-accelerated fast-path switching of IPv6 multicast packets is not performed in an IEEE 802.17 Resilient Packet Ring (RPR) configuration when a node failure occurs in a ring configured to operate in steering protection mode and the failure is on a non-edge node. In this case, throughput is significantly lower and IPv6 multicast packets are punted to the route processor. For more information about steering protection, refer to the IEEE 802.17 Resilient Packet Ring Feature Guide.
The following multicast protocols are supported to implement PXF-accelerated IPv6 multicast routing:
•
Multicast Listener Discovery Protocol (MLD), Version 2—Used by IPv6 routers to discover multicast listeners (nodes that want to receive multicast packets destined for specific multicast addresses) on directly attached links. There are two versions of MLD: MLD version 1 is based on version 2 of the In

