ATM Configuration and Troubleshooting Guide

Troubleshooting
Troubleshooting LAN Emulation
Chapter 9230
NOTE This procedure assumes that both end systems are on the same IP
subnet. If not, then you need a router to enable communication between
subnets. If this is the case, check that your router is configured correctly
to allow routing between the two subnets, then use the procedure
described below.
Start. Before you start this flowchart, do the following:
Step 1. If practical, kill all other traffic running through both systems’
adapters before you begin.
Step 2. Where possible, for a Token Ring network, ensure that the edge device
port that is connected to the ATM switch is configured so that it can
operate in both source routing and transparent routing modes.
A Run a continuous ping from the local system to the remote system by
typing the following command on the local system:
ping IP_address_of_ELAN_interface_on_remote_workstation 1024
Using the argument 1024 in the ping command results in about 20
packets being sent in the ping, making it easier to identify that the
destination connection is receiving network traffic.
B If ping is not successful, do the following:
Step 1. Confirm that the relevant IP interface is “Up” on both source and
destination systems, by using this command:
ifconfig net_interface
NOTE Do not use the command ifconfig net_interface up. We recommend
that you always use SAM for configuration.
Step 2. If any of the interfaces are not “Up”, then run SAM to reconfigure and
enable the IP interfaces.
Step 3. If the SVC is from a 622 Mbit/s adapter towards a 155 Mbit/s adapter,
ensure that you have configured an SVC whose peak cell rate is less than
155 Mbits/s.