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

X25CHECK (c) COPYRIGHT Hewlett-Packard Company 1988.
Test Starts on .. Wed Dec 8 09:15:01 1993
Initialization of the test...
CALL packet sent ...
The following figures have been measured on the network:
Set up time : 267 ms
Remote Connection Succeeded
Execute the x25check command again, but this time with data packets:
$ x25check 250207 -s 32 -n 1
X25CHECK (c) COPYRIGHT Hewlett-Packard Company 1988.
Test Starts on .. Wed Dec 8 09:15:47 1993
Initialization of the test...
CALL packet sent ...
DATA packet sent ... DATA packet received
The following figures have been measured on the network:
Set up time : 286 ms
Transit time : 245 ms
Remote Connection Succeeded
If your system has multiple X.25 cards, you may need to specify the particular interface in order
for x25check to work properly. For example, to run x25check on the second port of the first
card (interface x25_0p2), you would use the following format:
x25check 250207 -i interface0p2
ping command Run theping command to check your IP over X.25 connection. You can use either
an IP address, or the alias for the local node (defined in the hosts file). The following example
sends 6 packets of 100 bytes:
ping hpindla 100 -n 6
PING hpindla: 100 byte packets
100 bytes from 15.128.131.152: icmp_seq=1. time=321. ms
100 bytes from 15.128.131.152: icmp_seq=2. time=320. ms
100 bytes from 15.128.131.152: icmp_seq=3. time=319. ms
100 bytes from 15.128.131.152: icmp_seq=4. time=318. ms
100 bytes from 15.128.131.152: icmp_seq=5. time=320. ms
100 bytes from 15.128.131.152: icmp_seq=6. time=321. ms
--hpindla PING Statistics--
6 packets transmitted, 6 packets received, 0% packet loss
round-trip (ms) min/avg/max = 318/319/321
You can then check your IP over X.25 connection to a remote host using its IP address or alias.
If ping does not run successfully on the local node address, refer to “Troubleshooting” (page 130).
Configuring the high availability feature for X.25 over LLC2
This section describes how to configure the local and remote failover features for X.25 over LLC2
(XOL) interface. It also describes the local, remote, and a combination of local and remote failover.
WARNING! The failover is not transparent and results in loss of data and existing connections.
After a failover, the XOL connections must be re-established.
Unique MAC address requirement
XOL High Availability (XOL HA) is based on sharing a unique MAC address for the primary and
standby LAN cards, whichever is active. The use of a unique MAC address makes the card swap
Configuring the high availability feature for X.25 over LLC2 61