MSM7xx Controllers Release Notes v6.3.0.1

• (Applies to MSM422.) When an AP is configured to egress traffic on a given VLAN, the wireless
clients connecting to the AP fail to receive an IP address from the external DHCP server.
• (Applies to HP 425, MSM410, MSM422, MSM430, MSM460, MSM466, MSM466-R.) An
access controlled VSC using MAC-based authentication with the MAC filtering ALLOW option
enabled, allows clients to connect.
• In some cases, the network subnet information about rogue APs reported by the intrusion detection
system (IDS) is incorrect. The IP address will display as 0.0.0.0.
• The MSM Controller reboots after running WPA Termination for an extended period of time (longer
than 24 hours).
• (Applies to teaming.) Enabling Access Control on a VSC with WPA termination and using MTM
tunnel user traffic to home VLAN may cause a controller reboot.
• An MSM Controller does not send disassociation messages from a Bradford Sentry authenticator
to a wireless user.
• When an AP is configured to egress traffic on a given VLAN, the wireless clients connecting to
the AP fail to receive an IP address from the external DHCP server.
• When upgrading from Version 5.5.x to 6.0.x, the Zero Config feature is disabled and needs to
be re-enabled in order to be used.
• When IMC is used to manage the controller, APs may appear grayed out on the Controller >>
Controlled APs page.
Known issues
These issues are present in this release:
• RF Manager 6.7 does not recognize the HP 425 Access Point as an HP branded device.
Information about the HP 425 being adopted by the controller is sent to RF Manager, but the
information does not get into the RF Manager authorized AP list. As a workaround, in RF Manager,
manually authorize all SSIDs associated with the HP 425.
• When using option Public IP addresses for Guest Access, and there are more wireless clients than
available public IP addresses, the wireless clients with a public IP address already assigned might
lose their address to a new wireless client. As a workaround, make sure that you provision enough
public IP addresses to cover the largest anticipated number of concurrent users.
• In some conditions, the controller can experience issues at boot time. If you have more than five
VLAN interfaces with IP addresses, HP strongly recommends that you use Static IP addresses on
your VLANs.
• The “%” character causes random characters to appear in the name on the controller when used
in creating a profile name. As a workaround, do not use the “%” character when creating a
profile name.
• (Applies to MSM410, HP 425, MSM430, MSM460, MSM466, MSM466-R.) When Intrusion
Detection System (IDS) is enabled, AP radios on that (team of) controller(s) should not be configured
in Access Point and Local Mesh or Local Mesh only. As a workaround, IDS must be disabled on
the controller if Access Point and Local Mesh or Local Mesh only operation is required.
• If using teaming while an access controlled VSC with 802.1x authentication and the WPA
termination option is enabled, wireless clients may not be able to connect via a team member
controller. As a workaround, disable WPA termination or use WPA termination with Mobility
Traffic Manager (MTM) enabled and access control disabled.
• When IMC establishes a connection to the MSM7xx Controller, the following error messages are
displayed on the system log:
err pmmclient: setVLANSubsectionIndexFromVLANNetworkProfileName: Unknown
vlan name 'Internet port network'.
8 Known issues