![](/images/new-backgrounds/1170691/170691205x1.webp)
Diagnostics and Troubleshooting
Table 5-5. Network Problems (3 of 3)
Problem | Action |
|
| ||
|
|
| |||
Intranetworking | 1. | Verify that the internetworking network cables meet IEEE standards | |||
communication |
| for local Ethernet networks. |
| ||
problems. | 2. | Check cable connections to DSL chassis and other devices in the | |||
| |||||
|
| network. |
|
| |
| 3. | Determine whether or not your system is the only one in the | |||
|
| network with a problem. |
| ||
|
|
| |||
Performance is | 1. | Verify that there are enough buffers on the System Info screen and | |||
slow. |
| reset the system (see Monitoring → | Card Status | ||
|
| Monitoring the Hotwire DSL System). | |||
| 2. | Check the Ethernet Statistics screen for excessive Cycle | |||
|
| Redundancy Check (CRC) errors, a bad connection, or a bad cable | |||
|
| (see Monitoring → Physical Layer | |||
|
| the Hotwire DSL System). |
| ||
|
|
|
| ||
PPP circuit is | 1. | Verify that the DSL link is up. |
| ||
forwarding no | 2. | Go to: Configuration → | Interface → | Control | |
traffic. | |||||
| state of the system. |
|
| ||
|
|
|
| ||
| 3. | If the IP state is up and the local and peer IP addresses are | |||
|
| displayed, IPCP is completed. |
| ||
| 4. | If the IP state is missing from the screen, check that the port has an | |||
|
| IP address assigned. |
|
| |
| 5. | If the IP state is missing from the screen, check that the port has an | |||
|
| IP address assigned. |
|
| |
|
|
|
| ||
Proxy ARP not | 1. | Reconfigure DSL cards affected. |
| ||
properly set for | 2. | Set Proxy ARP only for Hotwire 5446 RTU, not entire subnet. | |||
Hotwire 5446 | |||||
|
|
|
| ||
RTU. | 3. | Using structured subnetting, verify proper subnetting was utilized. | |||
|
|
| |||
Stations cannot | 1. | Check to see that IP addresses have been configured correctly | |||
communicate |
| (see Who Am I screen in the Hotwire Management | |||
through the |
| Communications Controller User’s Guide, and Configuration → | |||
router. |
| Interfaces | |||
Incorrect IP | 2. | Go to: Configuration → | Interface → | Control | |
address. | |||||
| state of the system for e1a Bridge Up (forwarding). | ||||
Incorrect |
| ||||
|
|
|
| ||
Subnet Mask. |
|
|
|
| |
|
|
| |||
System does | 1. | Configure new DSL cards from MCC screen. | |||
not recognize | 2. | Restart s1b interface (see Configuration → DSL Cards | |||
new DSL cards | |||||
| Chapter 3, RADSL Card Configuration). | ||||
with new |
| ||||
|
|
|
| ||
addresses | 3. | Reset DSL card from the MCC screen (see Configuration → DSL | |||
(Addresses not |
| Cards | |||
preconfigured | 4. | Pull the card out and push it back in. | |||
on MCC card). | |||||
|
|
| |||
TFTP server | 1. | Before uploading configurations, create a dummy file and give it | |||
denies write |
| global |
| ||
permission | 2. | Configure TFTP host to have Write permissions is specified | |||
(Message is | |||||
| directory. |
|
| ||
TFTP recv |
|
|
| ||
|
|
|
| ||
failure). |
|
|
|
| |
|
|
|
|
|
April 2000 |