User's Manual Part 1

Access / One
®
Network
16 Welcome to Access/One Network
1
Communicating Across Remote Subnets
Access/One Network can be configured to enable communication between network
servers on remote subnets (for example, remote subnets in New York and Los
Angeles can be managed from the same Manager/One session). When network
servers are configured to communicate with each other across remote subnets, you
should expect the following behaviors from the system.
◗ If you decide to remove the NS to NS communication feature and just one
network server does not register the updated configuration during the reboot,
the network servers will continue to exchange information.
See also, “Starting a New Network” on page 32.
◗ In Manager/One, using the intuitive mouse-over feature on Network
Connects does not reveal their corresponding Client Connects. You can
access this information by connecting to remote network servers directly from
the Web.
Client Connect
Client Connect is the system topology that enables your Access/One Network to
support and provide access to client devices using 4.9 GHz Public Safety, 802.11a
or 802.11g wireless technologies. With Client Connect you can customize each
network node to support the wireless technologies you need in the locations you
need them. Any mix of these technologies can be supported within a single node or
across the entire Access/One Network.
Whether users carry a notebook, PDA, barcode reader, or other WLAN device, they
are able to stay continually connected to the network as they roam. No special
software is needed on the device, and no special configuration is required to remain
connected.
Each network node is capable of supporting multiple Client Connect modules of any
type and technology mix. This versatility of design provides you with a wide variety
of configuration options to meet all your user connectivity needs. And support of
future wireless technologies is as simple as adding a new Client Connect module.