Test Installation

Assuming you have not seen any error messages at boot time, follow this short procedure described here to ensure that your link is working. If you don't get the results described in each of the sections below, refer to the Troubleshooting chapter in the on-line Administrator's Guide for further guidance.

Checking X.25 and LAPB Links

Check Layer 2 Operation

When the X.25 protocol stack is built and configured, the software immediately attempts to set up the layer 2 (HDLC/LAPB) with the remote. Normally, this process takes less than a few seconds, so your link should be operational by the time your machine finishes booting, and you log in to check your installation. For LAPB-only links (those without a packet layer), the software waits until there is an application using the link before it starts up layer 2, so you will need to run a suitable application before the following test.

The easiest check of layer 2 operation is to run tsgstat. The first line the program displays should be:

Network Name: link0 ID:0, The link is UP

The key information on link operation is that your link is UP, meaning that it is able to transfer packets between your machine and the remote. By using the n option of the menu presented by tsgstat, you can check the status of other links.

Call Another Host (X.25 only)

Once your X.25 link is running, you can try and make a call to another host on the network:

cd /usr/lib/x25/utils

./xpad -r -d 0302092100086 -u A

You may have to substitute "1'" for the leading "0", as the digit that introduces a DNIC seems to vary from network to network. You should see a welcome banner for the Datapac Information System.

At that point, you can press the Enter key, followed by Ctrl+P C L R to disconnect.

If the call appears to "hang", eventually resulting in a clear with diagnostic 31, then it's possible that Wanware is configured for more virtual circuits than you've arranged for with your network provider. You may have to use tsgconfig to revise the protocol parameter bwc_num downwards before you can actually make a call that will be connected. (Refer to the X.25 Link Configuration section of the on-line Administrator's Guide.)

Checking Frame Relay Links

The Frame Relay stack in Wanware will periodically query the network to determine the status of the DLCIs. Unless the network tells it that a particular DLCI is active, Wanware is not allowed to send data on that DLCI.

The best way to check that this is all working is to take a look at the line trace using tsgtrace. You should see messages of the form:

T<01> ( 13)	DLCI: 1023
	Status Enquiry Message: Full Status
	Keep Alive Send: 0 (x00) Receive: 0 (x00)

The exact form of this message will vary according to your setting of lmitype.

There should also be a received message (one with an R on the left side) corresponding to each transmitted status enquiry. If not, then you may have the lmitype set incorrectly resulting in no response from the switch since it doesn't understand the format of the status enquiry.

If you have tried all of the lmitype settings and you still see no response, then it is likely that there is either a cabling problem, the DSU/CSU is not active or the switch has not been set to have your node active.