1.3A Typical Application
A typical application for a MultiFRAD
MultiMux
LAN 1 | Trunk | Data |
Ethernet Network |
|
|
Ethernet
Channel 2 |
|
| 26 |
MultiMux | 16 | Frame Relay | MultiFRAD 100 |
Trunk | Network | Remote Site 2 | |
Channel 1 | 17 | ||
|
|
| |
|
|
| 27 |
PC
T1 DSU | Trunk |
|
Data
MultiFRAD II
Host Site
PC
MultiFRAD 100
Remote Site 1
Figure 1-2. Typical Frame Relay Network
A MultiFRAD is easily connected to a frame relay network. One Data Link Connection Identifier (DLCI) is required and it is provided by your local network service provider when you request (subscribe) for a local telephone line connection. When your local network service provider engineers your connection, a virtual circuit is established between your location and the destination of your connection. This virtual circuit is called a permanent virtual circuit (PVC).
1.3.1 Ordering a Frame Relay Line
Ordering frame relay services from your local telephone company involves connecting the physical line, defining the port connection, configuring the PVC through the network, and assigning the Data Link Connection Identifier (DLCI). The DLCI is a number between 16 and 1007 that identifies the PVC between your MultiFRAD and the phone company's switch. The DLCI is assigned at the same time your local service provider defines the permanent virtual circuit (PVC) that is the path to your destination. When a PVC is assigned, an average guaran- teed throughput is negotiated with the service provider. The guaranteed throughput is called committed information rate (CIR) and is based on
12