Datatek DT-4180 - Manual (Page 54)

9 4 8 0 , 4 1 8 0 , 4 2 8 0 , 4 2 8 4 4 0 0 0 X A U s e r M a n u a l
04/09/09
54
virtual circuit number (e.g. 30001, 30002, …). Each subsequent X.25 port will add 200 to
this value. The second X.25 port begins at 30200, the third at 30400 and so on.
A port with (
type= E2AHOB ) is internally connected to a corresponding instance of the
E2AHOB application. The E2AHOB feature package is required for this option. There is
no required configuration of the E2AHOB application. The E2A remote connections will
be to the TCP port number of 30,000 for the 1 st port plus the remote number (e.g. 30001,
30002, …). Each subsequent E2AHOB port will add 200 to this value. The second
E2AHOB port begins at 30200, the third at 30400, and so on. The E2AHOB application
is available on the 9480, and the 4284.
A port with (
type= REDHOB ) is internally connected to a corresponding instance of the
REDHOB application. The REDHOB feature package is required for this option. There is
no required configuration of the REDHOB application. The REDAC protocol remote
connections will be to the TCP port number of 30,000 for the 1 st port plus the remote
number (e.g. 30001, 30002, …). Each subsequent REDHOB port will add 200 to this
value. The second REDHOB port begins at 30200, the third at 30400, and so on. The
REDHOB application is available on the 9480, and the 4284.
A port with (
type= IPDSU ) is internally connected to a corresponding instance of the
IPDSU protocol application. The IPDSU feature package is required for this option. The
IPDSU protocol options then become available for this port. The peer=<IP-DSU Peer IP
Address> option is used to define the remote peer IP-DSU connection for this port.
Loopback operations are perfomed with the loopback=< OFF | NET | PORT | BOTH >
option. The loopback=NET implements a loop of remote data back to the remote peer.
The loopback=PORT implements a local loopback to the port. The loopback=BOTH is
a union of these two functions. Loopbacks are disabled with loopback=OFF.
When the PDD destination information is specified with the pdd=<DNS destination
address> option, the xxxx uses the specified DNS server to resolve the name. A DNS
server address must be entered prior to configuration of any of the ports. The pdd
parameter is mutually exclusive with specifying the IP address directly via the dest and
dport parameters. A value of none (i.e. pdd=none) will clear the DNS destination
address.
A rcv-type user port is assigned a default TCP port number of 50000 + user port
number, i.e., 50001 to 50016. The port may then be addressed uniquely at that address.
However, when a specific TCP port number is specified via the hport=<tcp_port>
option, it is used in lieu of the default value. Multiple ports may share the same TCP port
number, to define a
hunt group . When a connection is directed to a TCP port number
associated with a hunt group , the xxxx selects the next available physical port by round
robin. The hport parameter only applies to rcv-type ports.
The hport option also operates on virtual circuits to create hunt groups. This operation is
selected when the hport option is used on an X.25 port. The virtual circuits must be
specified. The virtual circuits need not be contiguous, and may span X.25 ports. For
example, a 21 virtual circuit hunt group may be created by placing 7 virtual circuits each
from three ports into the same TCP port number hunt group.