HP X.25/9000 User's Guide HP-UX 11i v3 (5900-1523, August 2011)

Action:
• Check the remote node’s hardware address using lanscan. Use the same hardware address
in the generic X.25 configuration file. If you modify the hardware address to correct the error
then, re-initialize the card using x25init.
• If the nodes are connected back to back, check if the SAPs are identical for both the nodes
in the generic X.25 configuration file.
• If the nodes are connected back to back and one of the machines is configured for inbound
connections only and the other machine is configured for outbound connections only then, the
starting LCI for both the nodes must be identical in the generic X.25 configuration file.
Configuring X.25 over TCP (XOT)
This section describes the configuration files required for configuring X.25 over TCP (XOT) and the
configuration procedure.
X.25 over TCP (XOT) is based on RFC 1613 (Cisco Systems X.25 over TCP (XOT) ). Configuring
XOT allows X.25 layer 3 to connect to TCP/IP stack instead of LAP-B and provides X.25 functionality
on top of a TCP/IP infrastructure.
NOTE: IP over XOT is not supported.
Configuration files
To configure XOT, the following configuration files must be added or updated manually:
• Generic X.25 configuration file, x25init_xot_def
• XOT specific configuration file, x121_to_ip_map
IMPORTANT: When providing the configuration files as arguments to the x25init command,
they must always be specified along with the absolute pathname.
For example, /etc/x25/x25init_xot_def.
Generic X.25 Configuration file
The generic X.25 configuration file is used with a few additional XOT specific parameters to
configure XOT.
Table 15 (page 37) lists the specific parameters for XOT that must be defined while configuring
an XOT interface.
Table 15 Additional XOT specific configuration parameters
ValueFormatField
An XOT interface name.xot<instance number>name
NOTE: It must be in this prescribed
format.
A valid IP Address configured on the
system.
Dotted Decimal Notationlocal_tcpip_address
Flow control must be ON for a SVC.onflowcontrol
Incoming packetsize for SVC.
Recommended X.25 packet size for
XOT is 1024 octets.
A valid packet size between 128 and
4096 octets.
neg_inpacketsize
Outgoing packetsize for SVC.
Recommended X.25 packet size for
XOT is 1024 octets.
A valid packet size between 128 and
4096 octets.
neg_outpacketsize
Incoming Window Size for SVC.A valid Window size.neg_inwindow
Configuring X.25 over TCP (XOT) 37