Subnet id example – Baseline Systems FreeWave Ethernet Radio User Manual

Page 79

Advertising
background image

User Manual and Reference Guide

LUM0024AB Rev A

F, an Endpoint or Repeater connects with the first Repeater or Gateway that it
hears with the same Network ID. There are scenarios, however, where
communications need to be forced to follow a specific path. Subnet ID is
particularly helpful to force two Repeaters in the same network to operate in
series rather than in parallel, or, if desired, to force Endpoints to communicate
to a specific Repeater for load balancing purposes.

Two components exist with regard to the Subnet ID:

l

Subnet ID (RX) - This setting identifies which transceiver a Repeater or Endpoint listens to.

l

Subnet ID (TX) - This setting identifies the ID on which this device transmits, and in turn which
devices listen to it. The Subnet ID (TX) parameter is relevant for MultiPoint Gateways and
Repeaters only.

The default (disabled) setting for both Subnet ID (RX) and Subnet ID (TX) is F, which is a good visual way to
indicate that the device is the final in the line and does not use a subnet ID.

In some MultiPoint Networks, the Frequency Key will be at the same setting for all transceivers. In other
networks, where parallel Repeaters are introduced, the Frequency Key value needs to change. For more
information, see "Frequency Key" on page 54.

If both the Subnet ID (RX) and the Subnet ID (TX) settings are set to 0, this is known as Roaming mode.
This setting allows a mobile Endpoint to roam from subnet to subnet and possibly from network to network.

Subnet ID Example

The following drawing shows a network in which subnet IDs are used to force communications. In this
example:

l

Repeater1 must talk directly to the Gateway

l

Repeater2 must talk directly to Repeater1

l

Endpoints 1, 2, and 3 are forced along the direction of the solid lines

l

Endpoint4 may link to the first Gateway or Repeater it hears. (Rx, Tx)

63

Advertising