! Configure next hop list 10 with interface FastEthernet 10/2 as the
! first next hop, and interface Serial 2/1:1 as the second next hop.
!
ip next-hop-list 10
next-hop-interface 5 FastEthernet 10/2
next-hop-interface 10 Serial 2/1:1
exit
Frame relay encapsulation
The Avaya G250/G350 Media Gateway supports the following frame relay encapsulation
features:
Priority DLCI
●
Traffic shaping and marking per Virtual Channel (VC)
●
Priority queuing
●
Note:
The term Virtual Channel (VC) refers to the unidirectional flow of ATM cells
Note:
between connecting (switching or end-user) points that share a common
identifier number.
To improve voice quality using RTP, see
Priority DLCI
To implement new priority mechanisms, ISPs rely on new classes of service. Traffic types and
users are divided into these classes and treated differently during peak periods. A premium, or
first class user or traffic stream receives higher priority than a general user. This rating system
ensures that the critical Internet user maintains peak performance. It also provides a means for
ISPs to enhance the cost structure of network operations.
The G250/G350 supports class-based traffic assignment (priority DLCI). Priority DLCI is a
means for implementing QoS on frame relay circuits. The G250/G350 separates traffic with
different QoS levels to up to four different VCs on the same frame relay sub-interface. This
feature enables you to assign unique Permanent VCs (PVC) for VoIP and non-VoIP traffic. You
can set and adjust the priority using policy. For more information, see
page 441.
Configure Priority DLCI using the frame-relay priority-dlci-group command in the
serial sub-interface context. Specify the DLCIs in this command from the highest to lowest
priority. If you specify less than four DLCIs, the last DLCI specified is automatically used for the
missing priorities.
Configuring header compression
Frame relay encapsulation
on page 118.
Configuring policy
on
Issue 1.1 June 2005
185