| |
To isolate and resolve problems with NetWare Link/Frame Relay, complete the following steps:
Conduct a back-to-back test to make sure that the router hardware (PC, network interface board, cable, and so on) and software (driver, protocols, and so on) are functional. For information, refer to Back-to-Back Testing in the Overview documentation.
Attach one of the fully tested routers to the local DSU/CSU (or modem) and perform a DSU/CSU (or modem) local loopback test.
Use MONITOR to check whether the router can send and receive frames through the local DSU/CSU loopback. If the loopback test is unsuccessful, troubleshoot the DSU/CSU (or modem).
Verify that the routing configuration (including frame relay) and DSU/CSU (or modem) match the requirements of the carrier and remote router (LMI/ANNEX-D Status Exchange counters, timers, NRZ/NRZI, SF/ESF, B8ZS, network protocol options, and so on).
After you have attached the DSU/CSU and router to the network (switch) and restarted the router, use CALLMGR to check the protocol connection status.
Wait at least one minute to allow NetWare Link/Frame Relay to learn DLCI configuration information from the attached switch through status exchanges. If connections are not established, continue with Step 5. Otherwise, go to Step 11.
Check DTE/DCE handshake signals using MONITOR.
If the DTE/DCE signals are present and valid, use MONITOR to check the transmit and receive clocks and compare their speed with the expected (subscribed) port speed. Contact your ISP if the speeds are inconsistent. If the speeds match, check your DSU/CSU (or modem) configuration. If the DSU/CSU is configured properly and is functional, contact your ISP to troubleshoot the local loop (possibly through a remote DSU/CSU loopback test).
Use MONITOR to make sure that frames can be transmitted and received successfully.
Use FRTRACE to make sure NetWare Link/Frame Relay can exchange link management (LMI or ANNEX-D) frames successfully with the attached network switch.
Contact your ISP to resolve any link management status exchange errors.
Verify the configured DLCIs and their associated status using the (frame relay) Virtual Circuit option of FRCON or the Full Status Response decode option of FRTRACE.
Contact your ISP if these DLCIs are inconsistent with the services to which you subscribed.
Check the protocol connection status using CALLMGR.
If connections are not established, check the network protocol (IPX, IP, AppleTalk, and source route bridge) configuration on local and remote routers to ensure compatibility and interoperability. Repeat this step until all connections are established.
Check the console messages or CONLOG in SYS: etc\console.log for error messages. To determine the action required for each error message, refer to Novell Internet Access Server 4.1 Messages.
Check router/server connectivity using the DISPLAY SERVER console command, the protocol console's routing/forwarding tables, or the individual protocol's PING or Echo utility.
If expected routers are missing, check the network protocol configuration on local and remote routers to ensure compatibility and interoperability. Repeat this step, if required.
| |