WGB_1#sh ip int brief
ProtocolStatusMethodOK?IP AddressInterface
upupDHCPYES209.165.200.225BVI1
downadmindownunsetYESunassignedDot11Radio0
upupTFTPYESunassignedDot11Radio1
upupotherYESunassignedDot11Radio1.184
upupunsetYESunassignedDot11Radio1.185
upupotherYESunassignedFastEthernet0
upupunsetYESunassignedFastEthernet0.184
upupunsetYESunassignedFastEthernet0.185
upupTFTPYESunassignedVirtual-Dot11Radio0
upupunsetYESunassignedVirtual-Dot11Radio0.184
upupunsetYESunassignedVirtual-Dot11Radio0.185
Troubleshooting Tips
If a WGB client does not associate with the WGB, note these tips to troubleshoot the problem:
• The native VLAN that is configured on the WGB needs to be the same VLAN on the switch to which
the WGB is connected. The switch port connected to the WGB should be Trunk.
• Verify the client configuration and ensure that the client configuration is correct.
• Check the show bridge command output in the autonomous AP and confirm that the AP is reading the
client MAC address in the right interface.
• Confirm that the subinterfaces that correspond to specific VLANs and different subinterfaces are mapped
to the bridge group.
• WGB reads the switch port behind as a client in its MAC address table.
• If required, clear the bridge entry using the clear bridge command (remember that this command will
remove all the wired and wireless clients associated with the WGB and make them associated again).
• Ensure that the WGB has not exceeded its 20-client limitation.
Cisco Mesh Access Points, Design and Deployment Guide, Release 7.3
256 OL-27593-01
Managing Mesh Access Points with Cisco Prime Infrastructure
Multiple VLAN and QoS Support for WGB Wired Clients