BridgeLINK Troubleshooter:

If you are having problems with your BridgeLINK, follow these steps. If you still cannot solve your issue, then contact BridgeLINK Customer Support, and please be sure to have all the information required below.

Troubleshooting steps:

  1. Physically install the link according to the Quick Installation Guide. You may want to stage in a test environment before actually climbing towers to mount the antennas. If you do, make sure that the BL antennas are at least 50 feet away from each other. If you don't have 50 feet to work with, try to aim the antennas away from each other by about 30°. Otherwise, you will see poor signal quality on the Antenna Aiming tool below.

  2. Make sure all antenna connections are tight, and, in the final installation, that the cold shrink tubing is installed on the Antenna side cable connection.

  3. Power on the BridgeLINK units.

    • When the bridges power on, all the front-panel lights come on, and then go off after several seconds, except the power light, which should remain on. If the other station is seen, the Radio LED will come back on. If the Fault light remains on, contact your reseller or BridgeLINK's Customer Support team for repair or replacement.

    • The light on the CRM module should flash green and amber about once a second. The amber light will be of much shorter duration than the green. If one side is not flashing this way, there may be a problem with the link. Check the Antenna cables, as these are frequently the source of link problems. If there are no Amber lights on one or both sides, and the distance is great, you will need to visually aim the antennas so that a rough link can be established. We will tune this later.

    • Both lights on the Ethernet port should be operating, one steady, and one flashing. If the lights are not on, check that the Ethernet Cables are installed and working and that the attached equipment is powered up and operational. If they are still not on, do the following:

      • For the original BL, push the MDX/MDIX selector switch on the unit until you see a link light.

      • For the BL units, download and apply System Software version 3.02 or better to the bridge, and restart it. A bug in version 3.00 and 3.01 software can prevent the link-autosense feature from working.

  4. Run IPASSIGN. Does IPASSIGN find both MAC addresses?

    • If not, use the serial port configuration tool to verify that the bridges are set to an IP address of, and IP mode "Acquire". Retry IPASSIGN.

    • If still not, check the Ethernet cables between the BL and it's locally attached PC. Is there a link light on both Ethernet ports? If not, change cables. Retry IPASSIGN.

  5. Use IPASSIGN to install IP addresses on both Bridges, and allow IPASSIGN to invoke the browser to complete the configuration. It may take a minute or more for some of the applets to sense, load, and configure, so please be patient. Setup the IP, Gateway, Subnet ID, Packet Filtering, Spanning tree, and Security parameters as you like, and don't forget to "Save Configuration Changes" when you're done. You MUST reenter the IP address into the BL after using IPAssign.

  6. Run the browser applet, Antenna Aiming. Make sure the links can see each other with a link quality of 97 or better. If not, carefully aim the antennas until you get the link quality at or near 100%.

    • For links over a mile, make sure you use the special 'eXtended Range' software version, and set the proper setting to a good approximate real range, so the tool doesn't time-out.

    • To maximize the link quality number, make minor adjustments to the Antenna and its mount. The video feedback capability would allow you to use Walkie Talkies to do this job. Note: Don't run the antenna aiming tool on both sides of the link at the same time, or you will not get valid readings.

  7. Ping (Networking) tests: (Note that you may have to shut down any firewall in between any of these points, or you may not get a ping response.)

    • From a DOS box on either side of the link, ping the IP address of the locally attached BL unit and verify you get a response. This verifies correct connection to the BL.

    • Then, ping the IP address of the remote BL. This checks the connection across the RF.

    • Next, ping the IP address of the Ethernet port on the remote computer/bridge/hub/router. This verifies that the networks are connected. At this point, your BridgeLINK is up and operational, and you may skip the following steps, which verify the functionality of your Wide-Area Network.

    • Ping the IP address of the Gateway for your network. This verifies the connection to the Internet access device.

    • Finally, ping an address on the Internet, such as This will verify that your local users can get to the Internet. Bring up your browser and call up a web page on the Internet by its URL. This will verify that your DNS system is working.

  8. Tighten up the installation by grounding the antenna assemblies, securing the RF Cables and the antenna, weather-proofing any Bridge/Radio components that are not indoors, installing the cold shrink tubing, naming the BL units, assigning passwords to BL units with Public IP Addresses, and installing any encryption options purchased with the BL or BL .

  9. If problems arise during this troubleshooting process, contact BridgeLINK Customer Support. In order to best assist us in helping you solve technical issues, please make sure to report the answers to the following questions as thoroughly as possible:

    • About the Product:

    • What BridgeLINK product are you using? What is the part number on the Product Label? What is the driver version?

    • About the Problem:

    • What is the nature of the problem? Please be sure to describe your issue in as much detail including any error messages reported. What troubleshooting steps have you already taken?

    • About the System:

    • What is the accurate distance between bridges? Have you verified line-of-sight? What type of Ethernet device is the bridge connected? Manufacturer? What networking protocols are involved? Have you started a Syslog Service?