Cisco 10000 - Manual (Page 469)

20-7
Cisco 10000 Series Router Software Configuration Guide
OL-2226-23
Chapter 20 Configuring Gigabit EtherChannel Features
Configuring Policy Based Routing Support on a GEC Bundle
Service-policy police_dscp
Interface Port-channel 1.1
Service-policy input customer_A
Interface Port-channel 1.2
Service-policy input customer_B
Configuring Policy Based Routing Support on a GEC Bundle
Cisco Policy Based Routing (PBR) provides a flexible mechanism for network administrators to
customize the operation of the routing table and the flow of traffic within their networks.
Load balancing is performed on packets that pass through PBR. If a PBR clause is applied to outbound
packets, and the clause results in the selection of an EtherChannel egress interface, then a new hash is
generated based on the new address information. This hash is used to select an appropriate member link
as the packet's final destination.
Policy based routing is supported on Gigabit EtherChannel. You can configure PBR directly on a GEC
bundle interface.
Restriction for Configuring PBR Support on a GEC Bundle
• Use of the set interface command is restricted in the set clause for PBR, on GEC bundle interfaces.
Only the IP address for the next hop can be specified.
Configuring IEEE 802.1Q and QinQ Support on GEC Bundle
Support for both dot1Q and QinQ subinterfaces is available for GEC bundle interfaces. Configuring
subinterface on a GEC bundle interface is similar to a normal Gigabit Ethernet interface configuration.
When a subinterface is configured on a GEC bundle interface, the GEC Toaster client creates
subinterface instances in the Toaster for all the GEC member links. The subinterface instances created
internally on GEC member links are hidden and not available to the user for applying configurations.
Note The toaster is designed to process IP packets at very high rates using existing forwarding algorithms,
though it may also be programmed to perform other tasks and protocols.
Prerequisites for Configuring IEEE 802.1Q and QinQ Support
• Create a GEC bundle main interface before creating subinterfaces.
Restrictions for Configuring IEEE 802.1Q and QinQ Support on GEC Bundle
• A dot1Q/QinQ subinterface created on GEC bundle requires a VCCI on all the member-links.
For example, a GEC bundle interface with 8 member-links uses 9 (1+8) VCCIs for each dot1Q/QinQ
subinterface created on the GEC bundle.