22WIRELESS LAN SWITCH AND CONTROLLER MSS VERSION 6.0.4.6 RELEASE NOTES

Mesh Issues

The Ethernet port is not brought up on the bridge link if it was not up when the mesh link is established. (46037)

If the mesh AP is brought up without the Ethernet port connected, after the mesh link is established, the bridge link will not come up and no traffic will flow through the AP to the Ethernet port. To work around this issue and restore connectivity, reset the mesh AP ensuring that the Ethernet port is always up by connecting a hub or switch to the mesh AP Ethernet port.

MAP IssuesDistributed MAPs and Link Autonegotiation (16726)

The Ethernet interfaces on a MAP are configured to autonegotiate the link speed (10 Mbps or 100 Mbps) and mode (half duplex or full duplex). The setting cannot be changed. A common setting on third-party switches is 100 Mbps, with full duplex. If you connect a Distributed MAP to a port that is set for 100 Mbps with full duplex, the MAP operates at 100 Mbps with half duplex. This results in an unusable link. Configure the port on the other device to autonegotiate.

Wireless clients connected to directly attached APs may not display as connected in the show system output information. (41792)

When connected to the network using an Intel 2100 wireless network card, large file transfers may cause the wireless client to disconnect.

(40721)

A distributed AP may not successfully boot if Port 1 of the AP has an operational Ethernet link, but an WX is unreachable via this data link. (38807)

All other combinations of power and data connectivity are fully supported.

Distributed MAP can change IP addresses during boot sequence in environments with multiple DHCP servers. (16499)

To become fully active, a Distributed MAP does a full restart after downloading its software image. The first time the MAP is powered up, it sends a DHCP discover for an IP address, uses DNS to find its configured WX switch, and then downloads its software image from that WX.

After downloading the image, the MAP restarts itself with the downloaded image and sends a second DHCP discover to again obtain its IP address. In a network containing more than one DHCP server, it is possible for the MAP to use one IP address when downloading the image, but end up with a second IP address after rebooting the second time. This can occur if the DHCP server that responds to the DHCP request after the second reboot is not the same server that responded to the first request.

This issue does not prevent the MAP from operating normally but can make managing the MAP more difficult if the address the MAP receives the second time is not predictable. To prevent the MAP from using more than one address, use static address assignment in your DHCP server.