Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Allocating Excess Bandwidth Among Frame Relay DLCIs on Multiservices PICs

By default, all logical (lsq-) interfaces on a Multiservices PIC share bandwidth equally in the excess region (that is, bandwidth available once these interfaces have exhausted their committed information rate (CIR).

However, you can include the excess-rate statement to control an independent set of parameters for bandwidth sharing in the excess region of a frame relay data-link connection identifier (DLCI) on a Multiservices PIC. Include the excess-rate statement at the [edit class-of-service traffic-control-profile traffic-control-profile-name] hierarchy level.

There are several limitations to this feature:

  • The excess bandwidth comes from bandwidth not used by any DLCIs (that is, bandwidth above the CIR). Therefore, only FRF.16 is supported.

  • Only CIR mode is supported (you must configure a CIR on at least one DLCI).

  • Only the percent option is supported for lsq- interfaces. The priority option is not supported for DLCIs.

  • You cannot configure this feature if you also include one of the following statements in the configuration:

    • scheduler-map

    • shaping-rate

  • If you oversubscribe the DLCIs, then the bandwidth can only be distributed equally.

  • The excess-priority statement is not supported. However, for consistency, this statement will not result in a commit error.

  • This feature is only supported on the Multiservices 100, Multiservices 400, and Multiservices 500 PICs.

The following procedure configures excess bandwidth sharing in the ratio of 70 to 30 percent for two frame relay DLCIs. Only FRF.16 interfaces are supported.

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

  1. Enable the association of scheduler map names with logical interfaces.
  2. Configure the traffic control profiles.

    Only the percent option is supported.

  3. Apply the traffic control profiles to the logical interface.

    Only FRF.16 is supported.

  4. Verify the configuration.