Bug ID Description
93737 Symptom: The ERROR: IGMP configuration failed error message was displayed when the IGMP proxy was configured using the WebUI. This issue is resolved by ensuring that only one of the following radio buttons –Enable IGMP, Snooping, or Proxy under the Configuration > Network > IP > IP Interface > Edit VLAN page of the WebUI is enabled.
Scenario: This issue was not limited to any specific controller model or release version.
Table 150: IGMP Snooping Fixed Issues
Licensing
Bug ID Description
87424 Symptom: The licenses on a standby master controller causing the configuration on the local controller to be lost. Caching the master controller's license limits on the standby controller for a maximum of 30 days resolved this issue.
Scenario: This issue occurred when the standby comes up before the master after a reboot. This may also occur in an all master-local topology when running ArubaOS 6.3 or later.
Table 151: Licensing Fixed Issues
PPPoE
Bug ID Description
94356 Symptom: PPPoE connection with IP NAT inside configuration failed. Changes to the logic that prevented NAT to occur in datapath fixed this issue.
Scenario: This issue was observed on controllers with uplink as a PPPoE interface, and the client VLAN with IP NAT inside.
Table 152: PPPoE Fixed Issues
ArubaOS 6.3.1.13 | Release Notes Resolved Issues |104
105 | Resolved Issues ArubaOS 6.3.1.13 | Release Notes
RADIUS
Bug ID Description
93689 Symptom: When clients run a script on their windows phone for 802.1x authentication, the controller sent an EAP Failure message. This issue is resolved by removing the EAP-Failure messages when the client timed out during 802.1X authentication.
Scenario: This issue was not limited to any specific controller model or release version.
Table 153: RADIUS Fixed Issues
Remote AP
Bug ID Description
82015 Symptom: An AP associated with a controller did not age out as expected when the heartbeat threshold and interval parameters were modified. Changes in the internal code resolved this issue.
Scenario: This issue occurred when the heartbeat threshold and interval parameters in the AP's system profile were changed while the AP status was indicated as UP in the controller. This issue was not limited to any specific controller, AP model, or ArubaOS release version.
86934 Symptom: An AP failed during boot up when the Huawei® modem E1371 was used. This issue was caused by an internal code error when using this modem. The fix ensures that the Remote AP (RAP) does not fail during reboot when using this modem.
Scenario: This issue was observed in RAP-108 and RAP-109 running ArubaOS 6.3.
90355 Symptom: AP-70 and RAP-108 access points connecting to the network using a cellular uplink were not able to achieve a 3G connection. This issue is resolved by improvements to the AP boot process, and changes that allow cellular modems to support multiple ports on the AP.
Scenario: This issue was observed in ArubaOS 6.3.0.x and 6.2.0.x, when AP-70 and RAP-108 access points connected to a Huawei® E220 Modem.
91292 Symptom: A Remote AP (RAP) failed over from backup LMS to primary and did not shutdown wired port.
This issue is fixed by ensuring that the wired port is shut down initially when a failover occurs from backup LMS to primary LMS and then reconnects to primary LMS. This ensures that the wired port is enabled and the DHCP process is initiated.
Scenario: This issue occurred when wired clients retained the old IP address retrieved from backup LMS and connected to primary LMS with LMS pre-emption enabled. This issue was observed in RAPs running ArubaOS 6.3.1.0.
94140 Symptom: The IAP whitelist database on the controller did not allow multiple APs in the same branch to share a common remote IP.
Scenario: This issue was caused by a typecasting error that prevented smaller IP addresses from being allowed.
94703 Symptom: The IAP-VPN connection disconnected intermittently. This issue is resolved by preventing the IAP database from storing more than six subnets per branch.
Scenario: This issue was observed when IAP database had more than six subnets-per-branch, although a maximum of only six was allowed. IAP-VPN branch with six subnets exceeded the idle timeout, and when it was up, it had different DHCP profiles, this led to more than six subnet entries for the branch in the IAP database.
Table 154: Remote AP Fixed Issues
SNMP
Bug ID Description
94205 Symptom: The sysExtFanSTatus MIB could not be queried. This issue is resolved by initializing the value of the fanCount.
Scenario: This issue was triggered when the hwMon process did not return the proper value for fanStatus SNMP queries. This issue occurred in 7200 Series controllers running ArubaOS 6.3.1.1.
Table 155: SNMP Fixed Issues
Station Management
Bug ID Description 85662
84880 88009 88319 89321 91963 92164 93243 93388 93389 93984
Symptom: The state of APs were displayed as down on the master controller although they were connected and UP. Internal code changes resolved this issue.
Scenario: This issue was observed when AP’s system profile had a local controller as the primary Primary-LMS and master controller was configured as a backup Backup-LMS. This issue was not limited to any specific controller model and occurred in ArubaOS running 6.3 or later.
Table 156: Station Management Fixed Issues
VLAN
Bug ID Description
95622 Symptom: The even VLAN distribution did not work correctly as the VLAN assignment number and the AP VLAN usage number did not match. The fix ensures that the VLAN assignment and AP VLAN usage numbers match.
Scenario: This issue was observed in clients that were frequently roaming when even VLAN distribution was enabled. This issue was observed in controllers running ArubaOS 6.3.1.2.
Table 157: VLAN Fixed Issues
ArubaOS 6.3.1.13 | Release Notes Resolved Issues |106
107 | Resolved Issues ArubaOS 6.3.1.13 | Release Notes
WebUI
Bug ID Description
76439 Symptom: When the Spectrum monitor saved in the preference file was not available on the controller, a pop-up was displayed intermittently with the message, reconnecting. This pop-up is eliminated by making code level changes.
Scenario: This issue occurred in ArubaOS 6.2.0.0, when AP-105 access point in hybrid AP mode failed to appear as a connected spectrum monitor in the controller WebUI.
90264 Symptom: Layer 2 Tunneling Protocol (L2TP) pool was not displayed when the user-role was configured in the WebUI of a controller without an AP license. This issue is fixed by removing the WLAN_REMOTE_AP license validation while configuring L2TP pool.
Scenario: This issue was triggered by Policy Enforcement Firewall (PEF) license with WLAN_REMOTE_AP validation while configuring L2TP pool on a controller. This issue was not limited to any specific controller model or release version.
Table 158: WebUI Fixed Issues