IBM 8285 Nways, Installation And User Manual

Page: 195 / 265

Workgroup Switch Cannot PING an ARP Client
Steps to Take: Check if the workgroup switch can PING the ARP server. If not, then see “Problems with PINGing”
on page 166. If it can PING the server:
1. The port of the ARP client is not OKAY .
Check that the port of that ARP client is enabled. If it is enabled, and not OKAY , then the problem comes from the
ARP client or from the cable attached to it.
2. The ARP client is not registered in the ARP server.
Check that the ARP client has TCP/IP running, and that the address configured for its ARP server is correct.
3. If the workgroup switch and the ARP client are not in the same IP subnet, there may be a Gateway definition
problem.
Check the Default Gateway addresses in both machines. In general, they correspond to one common gateway.
4. The SVC between the workgroup switch and the ARP client cannot be established.
Check the Clear-Log Table in the Nways Campus Manager ATM (ATMC) to see the cause of the failure.
Workgroup Switch LEC Cannot PING another Client and Vice-versa
Steps to Take:
1. Check that the port of the LEC is enabled. If it is enabled, and not
OKAY
, then the problem comes from the LEC or
from the cable attached to it.
2. The LEC does not support the same Ethernet type as the workgroup switch LEC.
Check that the local LEC is emulating the same Ethernet type (802.3 or Ethernet V.2/DIX) as the remote LEC.
3. Check that both LECs are connected to the same LES.
4. If the workgroup switch LEC and the other LEC are not in the same IP subnet, there may be a Gateway definition
problem.
Check the Default Gateway addresses in both machines. In general, they correspond to one common gateway.
5. If both a Classical IP subnet and a LAN Emulation subnet have been started, check that they have been defined
with different subnetworks.
ARP Client Cannot PING the ARP Server
Explanation: The IP address of the client is not in the same subnet as the ARP server.
Steps to Take:
1. Re-define the IP address of the ARP client so that it is in the same subnet as the ARP server IP address.
Two Devices Using IP Over a PVC Cannot PING Each Other
Steps to Take:
1. If the PVC is not active, make sure that the PVC is 'in-service' from ATMC or 'active' (from the console). If not,
then try to re-enable that PVC.
2. The hardware connections may be failing, in which case replug the cables attached to the devices.
3. If the source and destination IP addresses are not in the same IP subnet, check both IP addresses. Change them
so that they belong to the same IP subnet.
Chapter 21. Troubleshooting
167