ATM Troubleshooting

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

ATM Troubleshooting

What problem are you having?

  • Host cannot join an emulated LAN.

  • Hosts on my IP/ATM network are unreachable.

  • A hardware error occurs when my ATM adapter attempts to initialize.

Host cannot join an emulated LAN.

Cause:  The client and switch must be running a user-to-network interface (UNI) based on parameters outlined in ATM Forum UNI 3.1 or 4.0 specifications. Otherwise, the initial point-to-multipoint (PMP) call setup fails and no connection is made. The LAN emulation client (LEC) provided in the Windows Server 2003 family is based on the ATM Forum UNI 3.1 specification.

Solution:  Use the Atmadm utility to determine if the setup call is failing. The Atmadm utility is used to monitor connections and addresses registered by the ATM Call Manager on an asynchronous transfer mode (ATM) network. You can use it to display statistics for incoming and outgoing calls on ATM adapters. If Atmadm displays few or no packets received on signaling and ILMI VCs, check your switch connectivity. For example:

Signaling and ILMI packets sent     = 90718
Signaling and ILMI packets received = 0

See also:  View ATM connection information; Atmadm

Hosts on my IP/ATM network are unreachable.

Cause:  If you have more than one ATM ARP/MARS for each virtual LAN on your network, the ARP caches can become out of synch. This causes clients to be able to only contact clients registered with the same server. Clients registered with another server are unreachable.

Solution:  Only use one ATM ARP/MARS for each virtual LAN.

A hardware error occurs when my ATM adapter attempts to initialize.

Cause:  Your ATM adapter is running IP/ATM and LAN emulation (LANE) on the same subnet.

Solution:  IP/ATM and LAN emulation (LANE) must be configured to run on separate subnets.