User's Manual Part 4

Access / One
®
Network
122 Managing the Network
5
Enabling Communication Between Remote Subnets
Your Access/One Network can be configured to enable communication between
network servers on remote subnets, allowing you to manage subnets from any
network server on the network, regardless of its location. For example, remote
subnets in New York and Los Angeles can be configured and managed from the
same Manager/One interface.
Example
Los Angeles and New York each have their own network:
◗ Los Angeles (LA): 172.20.0.0
◗ New York (NY): 192.152.1.0)
You want both networks to be managed by the same Manager/One interface, and
you can assume that a network server in Los Angeles (172.20.0.50) is the primary
server for the Access/One Network.
See also, “Starting a New Network” on page 32.

It is recommended that you complete all of your configuration changes
before using the Apply Configuration command to propagate your
changes throughout the network. Once the Apply Configuration
command has been initiated, you cannot make any further changes
until the command cycle has been completed.

It is strongly recommended that customers use an NTP (Network Time
Protocol) server to synchronize Access/One Network to one clock. This
will ensure that the system's internal Syslog time-stamping process is
maintained correctly. See also, “Enabling Windows 2000 Servers for
NTP Requests” on page 33. Without an NTP server (no universal clock),
each network server will use its own internal clock and stamp times
accordingly.