Revision as of 20:09, 16 June 2010

Contents

Introduction

This configuration allows the Cisco ITP to send a user defined amount of traffic to a primary destination. Excess traffic is then sent to a secondary destination. This distribution is more specific than those based on congestion. Overflow load sharing is especially useful for enforcing customer limitations.

Configuration

Restrictions and Considerations

Only one rate limit entry is allowed for a GTT application group.

You configure the rate limit entry for a specific destination in the GTT application group.

You must configure both a primary and secondary (backup).

You can define the primary and secondary by configuring ASs, DPCs, or any combination of an AS and DPC.

The primary AS or DPC is defined as the one with the lowest configured cost.

Example

In the following example, the application group named SMS-peak-on-weekdays has a primary DPC with a point code of 1.1.1. It is limited to a rate of 2000 MSU per second. Any overflow traffic is sent to the backup DPC with a point code of 1.1.2. The primary DPC is defined by the lower cost of 1. The backup is defined by the higher cost of 2.

cs7 gtt application-group SMS-peak-on-weekdays

multiplicity cost

pc 1.1.1 ssn 11 1 pcssn limit 2000

pc 1.1.2 ssn 11 2 pcssn

In the following example, the application group SMS-peak-on-weekdays. It has a primary AS named weekday is limited to a rate of 2000 MSU per second. Any overflow traffic is sent to the backup AS named weekend. The primary AS is defined by the lower cost of 1. The AS is defined by the higher cost of 2.

cs7 gtt application-group SMS-peak-on-weekdays

multiplicity cost

asname weekday 1 gt limit 2000

asname weekend 2 gt

Related show Commands

This section provides information you can use to confirm your configuration is working properly.