Wireless is rapidly developed technology. However, it encounters many problems mostly related to troubleshoot.
There are three major wireless bridge problem categories that are found commonly:
- Basic operation failure
- Connectivity failure
- Poor throughput
When thinking about the wireless bridges, the device we keep in mind is Cisco Aironet Equipment and the supporting drivers and software is essential. Therefore, there are chances that problems can arise in hardware or software components used for the wireless connection.
Below is the detail description about the three major problems we have discussed earlier about the Wireless bridges:
Basic Operation Failure:
The main symptoms of basic operation failure are:
- Unidentifiable and negative LED patterns
- Error messages occur at the console and constant rebooting.
These symptoms are catastrophic and after some time period requires the bridge replacement. The Cisco technical support can provide the knowledge about ship to address and serial number of the bridges. Along with that, in the hardware ware support, Cisco technical support provides the bridges that need to be replaced.
Second major issue that occurs most often is the connectivity failure. Connectivity lack means that traffic is not able to pass from one site to another and so on. There are chances to loose connectivity after any successful operation or soon after the units are physically arranged. In both the cases, troubleshooting is the problem. The Ping command from the computer system using the command prompt can be helpful to resolve the specific issue. It helps to determine the isolated point from where the connectivity is failed or lost.
It would be a good option to take small steps rather than pinging through end to end. Try to find out the lost of connectivity pint and then ping at that point first to solve the issue.
You can follow the three step procedure in order to establish the lost connection:
- First of all, ping your own PC. The successful replay indicates that your problem is sorted out. In addition to this, check the cables between the hubs and switches.
- Check and configure the IP properties of the connection
- Check for the drivers or any other accessory attached with your Network card.
- If you require, contact the card provider or connection providers for further details and help.
- Secondly, Ping the bridge at your site also known as the local bridge.
- If the ping is unable to solve the problem, then try to check the cables, hubs and switches of your network. Check the Ethernet specifications. If it is set on automated speed and duplex, then try to change its specifications or rearrange them. Configure them same at the both side of the devices and then again ping the local bridge.
- Afterwards, ping the last end bridge
- The successful replay will be that radio connectivity works proper between the two bridges. If this does not work then, try to verify that the two bridges connected are associated with each other. Check that only one bridges has the option of root parameter on because as we know that in the wireless bridges, only one bridge at a time is activated as a root bridge.
- Check that SSID (Service Set Identifier) is same in the both bridges.
- Finally ping the remote PC. Check for the ping results, check the hubs, cables and switches and check for the IP properties of the network connection.
It is very difficult to sort out the problems regarding bridges because there are many variables involved in the maintenance of the connection. Mostly bridges have built-in software that helps to solve the problem of the troubleshooting and throughput. However, they are not strong enough. The best approach you can us it to increase the transmit power at the site of the non-rooted bridge. Moreover, you can set the distance greater at the side of the root bridge if it is less than 1km.