Asynchronous Port Communication Problems

The following problems may occur when nodes connected to the DECrouter 200 by the asynchronous ports are unable to communicate with the DECrouter 200. It is assumed that you have already gone through the checks described in Section 8.2.1, and the suggested troubleshooting procedures did not resolve the problem.

Problem 1: Port cable improperly attached

Remedy: Verify that each port cable is secure at both the DEC router and the adjacent node.

Problem 2: Circuit turned off

Verify that the circuit has not been turned off. To display the state of the circuit, refer to the Monitor display or type the NCP SHOW CIRCUIT command for remote execution at the DECrouter. If the circuit is off, use the NCP SET CIRCUIT com-mand to turn it on.

8-14 DECrouter 200 Management Guide, Vol. I

Problem 3: Mismatch of line parameters and connected devices Check for the following to remedy this problem:

1. Make sure the parameters defined for the OECrouter 200's asynchronous port match the devices connected to them:

• Line speed must match that set for the connected device. The Monitor dis-plays the speed of each line.

• The device connected to the OECrouter 200 must be an asynchronous device (see the DECrouter 200 Software Product Description (SPD) for supported communications options).

• The system/device connected to the OECrouter 200 must be running ODCMP as the data link protocol between the DECrouter 200 and that system (see the DECrouter 200 Software Product Description for sup-ported systems / devices).

• Modem Control must be enabled via ORCP if the attached device is a modem, a modem replacement device, or if it requires modem control signals (see the cable discussion below). The Monitor displays whether the line is connected by a modem.

• Modem Control must be disabled via ORCP if the attached device is not a modem or a modem replacement device, or if it does not desire modem control signals.

• The connected device must be operating full-duplex.

• The connected device must be set to 8-bit character size with no parity.

• If verification is enabled on the Circuit, and if the adjacent node was entered in the OECrouter 200 node database (via ORCP) along with a receive pass-word, then the transmit password on the adjacent node must match that receive password.

• If verification is enabled on the circuit, and if the adjacent node was entered in the OECrouter 200 node database (via ORCP) with a transmit password, then the receive password on the adjacent node must match that transmit password.

2. Make sure that the appropriate cable is being used for the type of device con-nected to the OECrouter 200. Possible cable types are:

• BC220 or BC 170 null modem cables: used to attach directly to devices that DO NOT require modem control signals.

Troubleshooting 8-15

• BC17D null modem cable: used to attach directly to devices that DO require modem control signals.

• BC22E or BC22F straight through cables: used to attach directly to modems or modem replacement devices (that is, null modem boxes, short haul modems, etc.).

3. If the line connected between the DEC router 200 and the adjacent node is being run at an excessively high speed, then communications between the DECrouter 200 and the adjacent node may not be possible because too much data is being lost. Type the NCP SHOW KNOWN CIRCUITS COUNTERS com-mand for execution at the DECrouter and check the following counters:

• Data Errors Inbound

• Data Errors Outbound

• Remote Reply Timeouts

If any of these counters display an appreciable error rate, especially if the error rates indicate NAKs (negative acknowledgments) due to CRC (cyclic redun-dancy check) failures, then the speed may be too high for the line, or it may be too high for the adjacent node. Try reducing the line speed and retrying the connection. Note that what is an "appreciable error rate" depends on the situation. You must monitor these circuits over a significant time to become familiar with what is a normal error rate for each line. Over a given duration, consider (1) the number of inbound errors relative to the total number of packets received and (2) the number of outbound errors relative to the total number of packets sent. If any of these percentages is abnormally high, then the line speed may be inappropriate.

4. The last possible cause of the problem to investigate is a hardware failure. The following set of loopback tests should be followed using the guidelines sup-plied in Section 7.4:

8-16

• Attach the asynchronous port loopback connector (supplied with the DECrouter 200 hardware unit) directly to the DECrouter 200 port which is having the problem. Use the NCP LOOP CIRCUIT command to test that port. (Issue the command for execution at the DECrouter 200.)

If the test does not complete successfully, then there is a problem with the port on the DECrouter 200. You should have the DECrouter replaced.

Note that you can still use the DECrouter 200. Do not use the faulty port;

use a different one until the DEC router is replaced.

DECrouter 200 Management Guide, Vol. I

If the loopback test completes successfully, then this hardware port is not faulty. Try the following test:

• If the asynchronous port on the DECrouter 200 is not faulty; reconnect the appropriate cable to that port, ensuring that the cable is firmly attached.

Connect the loopback connector to the other end of the cable (at the adja-cent node that is connected by the cable) and rerun the same LOOP CIRCUIT test just performed.

If the test fails, then the cable or the cable connections at the adjacent node are faulty.

If the test completes successfully, both the DEC router 200 port and the cable are operational. If the cable terminates directly into another node (that is, without a modem), then that node's connectivity should be tested, using the test procedures recommended for that node.

• If the cable terminates at a modem, and if that modem supports local loop-back tests, then switch the modem into locallooploop-back mode and rerun the same LOOP CIRCUIT test.

If the test fails, then either the DECrouter 200's line parameters and the modem do not match (see the first step under Problem 3, above), or the modem is faulty.

If the modem does not support local loopback mode, then see the documentation supplied with the modem for procedures to test the modem.

• If the modem local loop back test completes successfully, switch the local modem back out of localloopback mode. If the remote modem supports remote loopback tests, then switch the remote modem into loopback mode and rerun the same LOOP CIRCUIT test.

If the test fails, or if the remote loopback test cannot be run, then either the configuration of the two modems does not match, or one of the modems is faulty. See the documentation supplied with the modems for procedures to test the modems.

If the remote loopback test succeeds, then the DECrouter 200 port, the cable between the DECrouter 200 and the local modem, the local modem, and the remote modem are not at fault.

• At this point, similar tests should be run from the node connected to the asynchronous port to diagnose possible problems with that node or with the modem connected to that node. Remember that in most cases initiali-zation problems are caused by incompatible configuration, meaning that parameter values are not set appropriately to match the network configuration.

Troubleshooting 8-17

8.2.3 Dial-Back Problems

The following troubleshooting steps help isolate problems that may exist when dial-back failure occurs. These steps verify that both the router and the attached modem are configured for automatic dialing to a remote node.

1. At one of the router's load hosts, run DRCP.

2. Issue the SHOW LINE command and check that:

• The line being dialed has CONNECTION TYPE DIALBACK set.

• The MODEM type is correctly set. These are the valid values for the MODEM parameter according to the kind of software distribution kit you have:

Software Kit Values for MODEM Non - PTT DF03

DFl12 DF224 CODEX HAYES

PTT V25BIS

• The line's IDENTIFICATION NUMBER parameter is set correctly, if you have a PTT kit.

• The baud rate set for the modem and LINE SPEED for the router's line are compatible.

• The baud rate set for the remote line and LINE SPEED for the router's line are compatible.

3. Issue the SHOW NODE command and check that the DTEADDRESS (phone number) for the remote node is defined correctly.

4. Issue the SHOW CIRCUIT command to verify that the circuit STATE is ON.

After the router's modem answers the remote node's modem, the remote node's modem should be switched to data mode (autoanswer). The remote modem must be in this state waiting for the router to dial back. However, if the remote node's modem is not switched to autoanswer after the initial answer from the router, dial-back fails.

8-18 DECrouter 200 Management Guide, Vol. I

When a call failure occurs, the response from the router and what you can do depends on the type of kit you have:

• Non-PTT kit. The router attempts to redial according to the line values you speci-fied for CALL ATTEMPTS and RECALL TIMER. If dial-back continues to fail, fol-low these steps:

• Check that the router's modem switches are set correctly. See Appendix D for the correct settings.

• If the modem is a DF03, check that it has the DF03-AC option (board M7177).

• If the modem is either a Hayes Smartmodem 2400 or a Codex 2233, reinitial-ize the modem to the factory defaults and then reset it. Attach an asynchronous terminal to the modem and at the keyboard type:

AT&F (RET)

ATSO=2&D2EOVO&Cl&Sl&MO&W (RET)

• If the modem is a Codex 2260, reinitialize the modem to the factory defaults and then reset it. Attach an asynchronous terminal to the modem and at the keyboard type:

AT&F CBm

AT*AA2&D2EOVO&Cl*MRO&MO&WO (RETJ

If these steps fail, call the appropriate software specialist or Field Service.

• PTT kit. The router does not attempt to redial the number. Follow these steps to try to identify a problem:

1. Check that the modem is V.25 his compatible.

2. Check that the modem is set to: 7 bit; even parity; 1 stop unit element.

If these steps fail, call the appropriate software specialist or Field Service.