|
|
 |
|
Netopia 640 for ISDN Service
Routing with Netopia 640 for ISDN Service
Troubleshooting
LAN Issues
LAN issues arise from the customer's LAN to the Ethernet Interface on the PN640. The most common issue is the inability to ping the .1 interface. This problem may arise from an incorrect IP address or the Ethernet interface is incorrectly configured. The following steps were taken to solve the issue:
- Verify Ethernet Link by looking on the front of the Netopia PN640 for a green light on the Ethernet link indicator. Perform the same step on the Ethernet hub.
- If link light does not exist, verify/modify Ethernet cable connection and the Hub/PC switch setting on the rear.
- If link light exists on both the hub and Ethernet interface of the Netopia PN640, verify the IP address of the Ethernet interface.
- Use a console session to verify the IP addresses.
- If IP address is incorrect, add the correct IP address and remove the incorrect one.
Routing Issues
Routing issues arise from failure to reach a site's IP address known to be up and running. The most common issue is the inability to ping the 38.1.1.1 IP address. This is usually caused by a missing default route. This assumes that your LAN-ISDN connection is active on both ends and both the Ascend and Netopia PN640 show the link active. The following steps were taken to solve the issue:
- Verify that the default gateway of the Netopia PN640 points to 38.1.1.1.
- Use a console session to verify the default route.
- If default route is correct, verify IP addresses and LAN-ISDN connection status.
Connectivity issues
Connectivity issues are usually attributed to mis-configurations or cabling. The most common issue is connection to the ISDN switch failed:
- First, verify the ISDN cable is securely connected to the wall jack and the Netopia PN640. If connected properly, check link lights on the front panel of the PN640.
- If the link is out, verify the ISDN cable is properly connected.
- If link is still out, verify ISDN configurations. Use a console session to check the SPIDs and Directory Numbers. Make sure there are no additional messages in the WAN Event History. If so highlight the message, and press Enter for an explanation.
- If the link is up, but there is still a problem, perform an ISDN Switch Loopback test. This is located in the Statistics, Utilities, and Tests menu. If the test fails, you may need to contact your ISDN provider.
Viewing Log
From the Statistics, Utilities, and Tests screen, located directly off the Main Menu, there are a few more management/monitoring options. This screen has links to both the General Statistics screen and the Event Histories screen:
- The Statistics, Utilities, and Tests screen now offers a built-in traceroute utility, as well as the ping utility. This is also a new feature with firmware version 3.2.
- The General Statistics screen displays the number of packets transmitted, and received, as well as any collisions or errors. It also shows the WAN Connection Statistics.
- The Event Histories screen will display either the WAN Event History, or the Device Event History. The Device Event History displays any connections made to the device, or any restarts that may have happened. The WAN Event History displays any call requests, call connects, or ISDN Line problems. Any event in the histories can be highlighted, and pressing the Enter key will bring up a message box. This message box will give more information about the problem, and in some cases the ISDN cause code.
|
