Cyclades-PR2000
STEP FOUR
The Encapsulation parameters for Frame Relay are less
Menu CONFIG=>INTERFACE=>SWAN=>ENCAPSULATION=>FRAME RELAY
Parameter | Example |
| Your Application |
SNAP IP | Inactive for the example. The router on the |
| |
| sending end must be using the same header |
| |
| type (NLPID or SNAP) as the router on the |
| |
| receiving end. |
| |
LMI | ANSI for the example. This must also be |
| |
| the same as the router on the receiving end. |
| |
T391 | Ten seconds, the interval between the LMI |
| |
| Status Enquiry messages. |
| |
N391 | Six. |
|
|
N392 | Three. |
|
|
N393 | Four. This value must be larger than N392. |
| |
CIR | 90 percent. | 100 minus this number is the |
|
| percentage of total bandwidth that may be |
| |
| discarded if the network is congested. |
| |
Bandwidth Reservation | Inactive. Traffic control will not be covered |
| |
| in this example |
|
FIGURE 4.13 FRAME RELAY ENCAPSULATION MENU PARAMETERS
At the end of the parameter list shown above, the DLCI menu appears. Choosing Add DLCI will lead to the parameters shown in Figure 4.14. The <ESC> key used at any time during the Frame Relay encapsulation parameter list will also bring up the DLCI menu. A DLCI entry must be created for every remote Frame Relay network to be contacted. In the example, only one is shown.
Chapter 4 - | 31 |