Cisco Cisco Aironet 350 Wireless Bridge 기술 매뉴얼
Connectivity Failure
Lack of connectivity means that traffic cannot pass from site to site. You can loose connectivity after a long
period of successful operation, or at any time after the units are physically deployed. In either situation,
troubleshooting is the same. Issue the ping utility from a command line of the operating system from your
computer in order to isolate the point where connectivity is lost. Do not immediately try to make a big step
from end to end. Instead, take smaller steps to determine where connectivity is lost. These steps, used in
order, can help to isolate the loss of connectivity.
period of successful operation, or at any time after the units are physically deployed. In either situation,
troubleshooting is the same. Issue the ping utility from a command line of the operating system from your
computer in order to isolate the point where connectivity is lost. Do not immediately try to make a big step
from end to end. Instead, take smaller steps to determine where connectivity is lost. These steps, used in
order, can help to isolate the loss of connectivity.
Ping yourself (the PC).
A successful reply indicates that the IP stack on the PC works correctly. Complete these steps if you
cannot ping yourself:
cannot ping yourself:
Check the cable between your PC and the hub or switch to which it is connected.
a.
Check the IP properties of your network connection.
b.
Check the drivers and any accompanying utilities for your network card.
c.
Contact the manufacturer of your network card or operating system as needed.
d.
1.
Ping the local bridge at your site.
A successful reply indicates that the LAN local to you works correctly. Complete these steps if you
cannot ping your local bridge:
cannot ping your local bridge:
Check the cabling between your bridge and the hub or switch to which it is connected.
a.
If the Ethernet interface on the bridge or the port on your hub or switch is set to auto speed or
auto−duplex, specify a speed and duplex setting instead. Configure it the same on both
devices, then try to ping the local bridge at your site again.
auto−duplex, specify a speed and duplex setting instead. Configure it the same on both
devices, then try to ping the local bridge at your site again.
b.
2.
Ping the remote bridge at the far site.
A successful reply indicates that the radio frequency connection between the two bridges works
correctly. Complete these steps if you cannot ping the remote bridge:
correctly. Complete these steps if you cannot ping the remote bridge:
Verify that the two bridges are associated.
a.
Verify that only one bridge has the root parameter turned on.
In a bridged network, only one bridge at a time can be the root bridge.
b.
Verify that the Service Set Identifier (SSID) is the same in both bridges.
c.
If Wireless Encryption Protocol (WEP) is enabled, disable it temporarily until you can
establish connectivity, then re−enable it once you have resolved other problems. This ensures
that the WEP key mismatch is on the root and the non−root bridge is not the root cause of the
problem.
establish connectivity, then re−enable it once you have resolved other problems. This ensures
that the WEP key mismatch is on the root and the non−root bridge is not the root cause of the
problem.
Note: Refer to Troubleshooting Connectivity in a Wireless LAN Network for more
information on troubleshooting connectivity in a wireless network. The Bridge section of this
document is helpful at this point.
information on troubleshooting connectivity in a wireless network. The Bridge section of this
document is helpful at this point.
Also, refer to Wireless Bridges Point−to−Point Link Configuration Example for additional
information.
information.
d.
If you can ping, but not with 100 percent accuracy, or if the ping times are excessively long, see the
Poor Throughput section of this document.
Poor Throughput section of this document.
3.
Ping your final target, the remote PC.
A successful reply indicates that the remote LAN works correctly. Complete these steps if you cannot
4.