10-12 Frame Relay Traffic Shaping (FRTS)

  • FRTS can perform traffic shaping to compensate for a mismatch in access rates at the ends of a virtual circuit.

  • Traffic shaping can be performed on an interface as a whole (all DLCIs) or on a per-DLCI basis.

  • FRTS is configured using Frame Relay map classes.

  • FRTS can dynamically adapt traffic rates based on feedback from Frame Relay switches. Backward congestion notification causes FRTS to throttle back the traffic rate.

Configuration

  1. Enable FRTS on an interface:

     (interface)  frame-relay traffic-shaping  

    FRTS is enabled for all PVCs and SVCs on the interface. Frame Relay encapsulation must be configured first.

  2. (Optional) Use Enhanced LMI.

    1. Enable QoS parameter exchange:

       (interface)  frame-relay qos-autosense  

      ELMI is detected on the interface if it is being used by a Cisco Frame Relay switch (BPX, MGX, and IGX families). QoS values (CIR, Bc, and Be) are exchanged between the router and the switch. ELMI must be enabled on both the router and the switch before it can be used.

    2. Choose an IP address for ELMI management.

      • Automatically choose an address:

         (global)  frame-relay address registration auto-address  

        By default, to communicate with ELMI network management stations , the router automatically chooses an Ethernet interface's IP address. If no Ethernet interface is available, a serial interface type and then other interface types are used.

      • Manually choose an address:

         (global)  frame-relay address registration ip   address  

        The IP address given is used as the ELMI management address.

  3. Define a map class for traffic shaping.

    1. Specify a map class name :

       (global)  map-class frame-relay   map-class-name  

      The map class named map-class-name (an arbitrary text string) is used to define any parameters related to a Frame Relay VC.

    2. Define the traffic-shaping parameters:

       (map-class)  frame-relay traffic-rate   average  [  peak  ] 

      The average traffic rate (in bps) and the peak traffic rate (in bps) are both defined for a map class.

    3. (Optional) Specify the type of backward congestion notification:

       (map-class)  frame-relay adaptive-shaping  {  becn   foresight  } 

      The router responds to standard BECN congestion notification ( becn ) or Foresight backward congestion notification ( foresight ) messages. Foresight can be used on some Cisco Frame Relay switches, and BECN is used on most Frame Relay switches.

    4. Apply the map class to an interface, subinterface, or DLCI:

       (interface)  frame-relay   class   map-class-name  

      -OR-

       (interface)  frame-relay interface-dlci   dlci   class   map-class-name  

      The map class named map-class-name is applied to a Frame Relay interface or subinterface. If the interface-dlci keyword is used, the map class is applied to the specific DLCI on the interface.

Frame Relay Traffic Shaping Example

Frame Relay traffic shaping is configured on interface serial 0 for all DLCIs, using the map class lowspeed with an average rate of 16 kbps and a peak rate of 32 kbps. Map classes are also applied to specific DLCIs on two subinterfaces. Subinterface serial 1.1 has DLCI 100 with a map class shaping to an average rate of 16 kbps and a peak rate of 32 kbps. Subinterface serial 1.2 has DLCI 101 and shapes to an average of 64 kbps and a peak rate of 128 kbps.

  interface serial 0   encapsulation frame-relay   frame-relay traffic shaping   frame-relay class lowspeed   interface serial 1   encapsulation frame-relay   interface serial 1.1 point-to-point   frame-relay interface-dlci 100 class lowspeed   interface serial 1.2 point-to-point   frame-relay interface-dlci 101 class highspeed   map-class frame-relay lowspeed   frame-relay traffic-rate 16000 32000   map-class frame-relay highspeed   frame-relay traffic-rate 64000 128000  


Cisco Field Manual[c] Router Configuration
Cisco Field Manual[c] Router Configuration
ISBN: 1587050242
EAN: N/A
Year: 2005
Pages: 185

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net