Common Problems

Various symptoms of common problems and the associated solutions are as follows:

• ATMWAA is inactive.

  If ATMCON indicates that the ATMWAA interface is inactive, verify that the ATM adapter board has been loaded. To do this, enter CONFIG at the console, then verify that the physical adapter board name configured in the Link/ATM Network Interface Configuration window matches the adapter board name.

  • The ATM adapter board is not loaded.

    Cause 1 ---The ATM adapter board is not initialized because there is a system resource problem. Load NIASCFG (parameter path: Select configure NIAS > Protocols and Routing > View Configuration > Console Messages) to view console messages. You should see a message indicating that the loading of the adapter was attempted but failed.

    Cause 2 ---The ATM adapter board is enabled but not loaded. This occurs when the physical adapter board name has been changed but the system has not been reinitialized.

    Use NIASCFG to complete the following steps:

    1. Delete the adapter from the Link/ATM Network Interface Configuration window.

    2. Reselect the adapter, press Esc to return to the NIASCFG menu, and save your change when prompted.

    3. Select Reinitialize System.

  • The ATM adapter board is operating but is not registered with the ATM switch.

    Cause 1 ---The electrical characteristics of the adapter board`s physical interface do not match the characteristics of the switch's interface. For example, the encoding used by a 100-Mbps adapter board does not allow it to communicate with a 155-Mbps switch, even though they use the same cable and connectors.

    Cause 2 ---The adapter cannot acquire the ATM address from the switch. Use the MONITOR LAN/WAN driver function to view adapter information. The Number of Signaling Link (Re)starts and the Number of Addresses Registered should be at least 1. If you do not see this status, this indicates that the ATM link between the system and the ATM switch is not operational, or this indicates that the switch is not compliant with UNI 3.0.

• Connections cannot be established.

  Usually, if a connection cannot be established, a message indicating the reason is displayed on the console. In addition to the reasons listed in Configuration Tips the following causes can apply.

  Cause 1 ---The switch is using an incompatible call establishment protocol. NetWare Link/ATM uses ATM Forum 3.0 signaling with the Address Registration ILMI procedures. For private virtual circuits (PVCs), Forum 3.0 signaling is not required, but Forum 3.0 ILMI Address Registration must be used. For switched virtual circuits (SVCs), both Forum 3.0 signaling and ILMI Address Registration are required.

  Cause 2 ---The user data size is configured differently at each end of the ATM connection.

  Cause 3 ---The remote end station address is not specified in the authentication database when inbound authentication is enabled.

  Cause 4 ---The encapsulation method is incompatible for both end stations.

  Cause 5 ---For PVCs, a call has not been established at both end stations.

  Cause 6 ---For PVCs, the virtual connection identifier is improperly configured. Check with your Internet Service Provider (ISP) or the network manager who configured the ATM switch to obtain the correct Virtual Path Identifier/Virtual Channel Identifier (VPI/VCI) pair.

  Cause 7 ---The adapter board or ATM switch does not support the service class specified in the WAN call destination. Some adapter boards might convert unsupported service classes to a type that they support.

• Packets are dropped during data transfer.
• Protocol connection is taken down.

  If multiple protocols share a single ATM connection, the protocol connection will be automatically taken down if no data is received for 15 minutes. If necessary, you can reestablish the protocol connection from CALLMGR.