Tsunami MP-8100 Installation and Management Guide 183
8.4.14 VLAN Operation Issues
The correct VLAN configuration can be verified by “pinging” both wired and wireless hosts from both sides of the device and
the network switch. Traffic can be “sniffed” on the wired (Ethernet), if configured. Bridge frames generated by wireless
clients and viewed on one of the backbones should contain IEEE 802.1Q compliant VLAN headers or tags. The VLAN ID in the
headers should correspond to one of the VLAN User IDs configured for the unit.
The correct VLAN assignment can be verified by pinging:
• The unit to ensure connectivity
• The switch to ensure VLAN properties This should be checking not pinging
• Hosts past the switch to confirm the switch is functional
Ultimately, traffic can be “sniffed” on the Ethernet interface using third-party packages. Most problems can be avoided by
ensuring that 802.1Q compliant VLAN tags containing the proper VLAN ID have been inserted in the bridged frames. The
VLAN ID in the header should correspond to the assigned VLAN.
What if network traffic is being directed to a nonexistent host?
• All sessions are disconnected, traffic is lost, and a manual override is necessary.
• Workaround: You can configure the switch to mimic the nonexistent host.
I have just configured the Management ID and now I can't manage the device.
• Check to ensure your password is correct. If your password is incorrect or all inbound packets do NOT have the correct
tag, then a Forced Reload is necessary.
CAUTION: The Forced Reload procedure disconnects all users and resets all values to factory defaults.
8.4.15 Changes Do Not Take Effect
Changes made in the Web Interface do not take effect:
1. Restart your Web browser.
2. Log into the radio unit again and make changes.
3. Reboot the radio unit when prompted to do so.
Wait until the reboot is completed before accessing the unit again.
8.4.16 Link Problems
While wireless networking emerges more and more, the number of wireless connections to networks grows every day. To
successfully use the connections, technicians must be able to troubleshoot the system effectively. This section gives hints on
how a Quick Bridge network could be analyzed in the case of “no link”, a situation in which the customer thinks that the link
is down because there is no traffic being passed.
The four general reasons that a wireless link may not work are related to:
• Hardware
• Configuration
• Path issues (such as distance, cable loss, obstacles)
• Environment (anything that is outside the equipment and not part of the path itself)
You have tested the equipment in the office and have verified that the hardware and configurations are sound. The path
calculation has been reviewed, and the path has been double-checked for obstacles and canceling reflections. Still, the user
reports that the link does not work.
Most likely, the problem reported is caused by the environment or by improper tests to verify the connection. The test
method, cabling, antennas, and antenna alignment have been checked. Always do this before checking the environment.
To Next Page
Loading...