Configuring qos service policies on gec interfaces – Cisco 10000 User Manual

Page 465

Advertising
background image

20-3

Cisco 10000 Series Router Software Configuration Guide

OL-2226-23

Chapter 20 Configuring Gigabit EtherChannel Features

Prerequisites for Gigabit EtherChannel Configuration

Prerequisites for Gigabit EtherChannel Configuration

The following are the prerequisites for configuring GEC bundles:

Create a GEC bundle interface before adding GE links to the GEC bundle using the channel-group
command.

Add GE links to the GEC bundle and configure all the links identically.

Restrictions for Gigabit EtherChannel Configuration

The following are general restrictions applicable to GEC bundles:

Bidirectional Forwarding Detection Protocol (BFD) is not supported on GEC bundles.

A dot1Q/QinQ subinterface created on a GEC bundle requires one VCCI on all the member links.
The GEC bundle also uses one VCCI.

Intelligent Service Gateway (ISG) IP sessions are not supported on GEC bundles.

Gigabit EtherChannels are not supported on a 10 GE shared port adaptor (SPA).

On core facing deployments, queuing actions are only supported when they are applied on each
individual member link.

In 1:N deployment mode:

Combination of any SPA based Gigabit Ethernet ports with either a full height GE line card or
half height GE line card is not supported.

A maximum of 4 Gigabit Ethernet SPAs form a GEC bundle. Each SPA interface must have the
same bay number and port number, assuming the representation is
GigabitEthernetSlotNumber/BayNumber/Port-Number.

For example, in the case of SPAs, Gi1/2/1 can be bundled with Gi5/2/1, but Gi1/2/1 cannot be
bundled with Gi1/0/1.

Member link counters are not updated.

We do not recommend the deletion of the GEC bundle main interface before removing the member
links, using the no channel-group command. Similarly, before you delete the GEC bundle main
interface, remove the subinterfaces.

Configuring QoS Service Policies on GEC Interfaces

The QoS support feature on Gigabit EtherChannel allows service policies to be applied on GEC traffic.
Support for QoS can be applied differently to

GEC bundles or main interfaces of member links and GEC

bundle subinterfaces.

Input QoS can directly be applied on GEC bundle subinterfaces or main interfaces. Input QoS can
be applied on member links using the vlan-group QoS feature. For details, see the

“Configuration

Example for Using the VLAN Group Feature to Apply QoS on Member Links” section on page 20-5

and the

“Configuration Example for Applying QoS on GEC Bundle Subinterfaces” section on

page 20-6

.

Advertising