The following is a diagram of TCP/IP running over the x.25 network interface (xt).
=========== ============ xhost <--------mdmeliminator-----> yhost =========== direct connection ============ =========== X25 net ============ xhost <----mdm1------mdm2------> yhost =========== modem connection ============
If x.25 adapter cards have been moved to different slots, it is possible that the ODM database will have incorrect information. To verify that the database has correct information, run the following command:
lsdev -Cc adapter
You will see a list of objects and their current state. There should be one entry for each X.25 adapter you have installed. If the PTFs for support on the ARTIC card family are installed on your machine, you will see ampx0, ampx1, etc. If the PTFs are not installed, the adapters will be named x25s0, x25s1, etc. See fax on rename.adapter.sna (from the defect support center) for information on ARTIC support.
If there is an error, run the following command for each x25 adapter to correct the database:
rmdev -l objectname -d
For example,
rmdev -l x25s0 -d # x25 device driver rmdev -l x25s1 -d # x25 device driver rmdev -l ampx0 -d # x25 adapter rmdev -l ampx1 -d # x25 adapter
rmdev -l x25s0 -d # x25 adapter rmdev -l x25s1 -d # x25 adapter
After running rmdev for each x25 adapter, boot the machine.
Note: If the connection is direct, the following commands must be issued simultaneously on both machines due to link start-up requirements for direct connection. Normally the host is attached to an X.25 network which would not require this.
If the host is connected to an X.25 network, the network interface may be configured via SMIT (smit tcpip), allowing automatic startup of the interface at IPL time. DO NOT do this with a direct connection due to the timing problem described above.
On xhost, do the following:
On yhost, do the following:
On the xhost, issue the command
ping yhost
On the yhost, issue the command
ping xhost