Troubleshooting

2.TCP Connection Problems

No Response — The G3PD expects, but did not receive, a response to a connection request or a DEFINITY LAN Gateway heartbeat message that it sent to the DEFINITY LAN Gateway application. Check the physical connections.

Client Too Slow — The DEFINITY LAN Gateway application closed the TCP link because it did not receive the connection request from the G3PD quickly enough.

No Reply to HB — The DEFINITY LAN Gateway application did not get a response to a heartbeat message.

TCP Connect Fail — A remote failure (not a failure on the Windows NT server) was detected.

TCP Internal — An internal software problem was encountered when setting up the TCP connection with the Windows sockets.

3.Other TCP/IP Problems

The following steps may help solve other TCP/IP problems. If any problem cannot be resolved, contact Services.

a.Check the Windows NT TCP/IP administration for the G3PD Network Interface Card (NIC). Verify that the IP address and subnet mask are correct.

b.Check that the IP address and remote host destination are correct on the G3 PBX Driver Configuration dialog box (see Figure 2-1). Refer to ‘‘Using the G3 PBX Configuration Utilities’’ in Chapter 2.

c.Check the TCP/IP administration and brouter administration for the DEFINITY LAN Gateway.

d.Use the ping command provided with the DEFINITY LAN Gateway and the netstat command on Windows NT to verify that TCP/IP connectivity can be established between the Tserver and the DEFINITY LAN Gateway.

The ping report can be used to see if it is possible to reach the Tserver from the DEFINITY LAN Gateway.

4.Mismatched Version or Potential Software Problems

Unexpected Msg — The G3PD received a message that it did not expect or a message with an invalid size.

Invalid Version — The G3PD and the DEFINITY LAN Gateway application have different DEFINITY LAN Gateway Tunnel Protocol versions. Check the version via the Maint menu of the DEFINITY G3PD Administrator utility. See the ‘‘Version Command’’ section in Chapter 3.

Invalid Context — The DEFINITY LAN Gateway received a valid message type, but it was out of context and unexpected. Report to Services.

Issue 1 — December 2002

DEFNETM.PDF — Avaya CT 1.2

4-11

Page 63
Image 63
Avaya G3PBX manual