Module has lost or does not establish connectivity


To troubleshoot a loss of connectivity, perform the following steps:

Troubleshooting loss of connectivity


Isolate the end user/SM from peripheral equipment and variables such as routers, switches and firewalls.


Set up the minimal amount of equipment.


On each end of the link:

·         Check the cables and connections.

·         Verify that the cable/connection scheme—straight-through or crossover—is correct.

·         Verify that the LED labeled LNK is green.

·         Access the General Status tab in the Home page of the module.

·         Verify that the SM is registered.

·         Verify that Received Power Level is -87 dBm or higher.

·         Access the IP tab in the Configuration page of the module.

·         Verify that IP addresses match and are in the same subnet.

·         If RADIUS authentication is configured, ensure that the RADIUS server is operational


On the SM end of the link:

·         Verify that the PC that is connected to the SM is correctly configured to obtain an IP address through DHCP.

·         Execute ipconfig (Windows) or ifconfig (linux)

·         Verify that the PC has an assigned IP address.


On each end of the link:

·         Access the General tab in the Configuration page of each module.

·         Verify that the setting for Link Speeds (or negotiation) matches that of the other module.

·         Access the Radio tab in the Configuration page of each module.

·         Verify that the Radio Frequency Carrier setting is checked in the Custom Radio Frequency Scan Selection List.

·         Verify that the Color Code setting matches that of the other module.

·         Access the browser LAN settings (for example, at
Tools > Internet Options > Connections > LAN Settings in Internet Explorer).

·         Verify that none of the settings are selected.

·         Access the Link Capacity Test tab in the Tools page of the module.

·         Perform a link test

·         Verify that the link test results show efficiency greater than 90% in both the uplink and downlink

·         Execute ping.

          o    Verify that no packet loss was experienced.

          o    Verify that response times are not significantly greater than

                §  4 ms from AP to SM

                §  15 ms from SM to AP

          o    Replace any cables that you suspect may be causing the problem.



A ping size larger than 1494 Bytes to a module times out and fails. However, a ping of this size or larger to a system that is behind a Canopy module typically succeeds. It is generally advisable to ping such a system, since Canopy handles that ping with the same priority as is given all other transport traffic. The results are unaffected by ping size and by the load on the Canopy module that brokers this traffic.


After connectivity has been re-established, reinstall network elements and variables that you removed in Step 1.