USRobotics NETServer/8, NETServer/16 manual Adding a Remote Device to the Location Table

Models: NETServer/16 NETServer/8

1 284
Download 284 pages 20.7 Kb
Page 88
Image 88

Adding a Remote Device to the Location Table

This is required only if the NETServer will dial out to the remote location. If the NETServer will not be initiating connections to the remote location (the remote device will always do the dialing), you may skip to the section titled Adding a Remote Device to the User Table.

Step 1 - Create a new location table entry.

Use the following command:

add location <location name>

The Location Name can be up to 15 characters long.

Step 2 - Set Required Location Parameters.

The parameters listed below must be set:

Type

The following command determines when the NETServer will dial out to the remote location:

set location <location> <on_demand manual continuous>

On Demand The NETServer dials out to the remote device when it has packets queued for that location. It then maintains the connection only as long as there is traffic on the line. Note that dynamic routing information is updated while there is a connection between the two devices, but not before the NETServer dials or after it hangs up. When an on-demand connection is terminated, the NETServer retains current RIP and SAP information in memory (stops aging it). It then uses these last known values to “spoof” (fake) RIP and SAP broadcasts to active LAN and WAN connections. When an on-demand connection is first created, the NETServer will immediately attempt to dial the remote location to obtain some initial RIP and SAP values.

6-14 LAN-to-LAN Routing

Page 88
Image 88
USRobotics NETServer/8, NETServer/16 manual Adding a Remote Device to the Location Table, Create a new location table entry