Stratus ftserver 3300, Site Planning Manual

Page: 65 / 138

Site Planning for Systems in an ftGateway Group
Network and Telephone Line Planning 6-3
N O T E S
1. Telephone connection points for each system are not
required if ftGateway groups are implemented. See
“Site Planning for Systems in an ftGateway Group” on
page 6-3
for more information.
2. A dedicated phone line provides the most reliable
service. ActiveService Network (ASN) calls routed
through a PBX might be slow due to the load on the
PBX, or might not complete successfully because the
calls can become disconnected. If you must use a
PBX, do not route the telephone extension through a
switchboard; instead, provide a direct-dial analog
number.
Site Planning for Systems in an ftGateway Group
Multiple ftServer systems at a single site can share a single telephone connection to
the ASN by implementing an
ftGateway group . The systems in the group must be
connected to a single physical Ethernet subnetwork. One system acts as a gateway
for ASN connectivity. This gateway system requires an analog telephone line that
connects to the ftServer Access Adapters on the gateway system. Other systems in the
gateway group , called gateway slaves, connect to the gateway system over the
network. In this case, Ethernet connections are required for each system, but only two
analog telephone lines for each site are required.
Each ftGateway group is limited to a maximum of 20 ftServer systems. All systems in
a group must connect to the same subnetwork over the system Ethernet port, over
Ethernet adapters, or through ftServer Access Adapters. Using ftServer Access
Adapters provides the highest level of manageability by allowing the system to be
serviced even when the operating system is not operational.
Make sure that only layer 1 and layer 2 devices separate the gateway and slave
systems. During a connection, the gateway system assigns the slave system a
temporary IP address from an IP address range reserved by Stratus and uses that
address for all traffic.