Bug ID Description
100856 Symptom: WebUI user certificate authentication does not work after upgrade to ArubaOS 6.3.1.5.
Scenario: This issue is observed in 7200 Series controller that uses certificate-based web authentication.
Platform: 7200 Series.
Reported Version: ArubaOS 6.3.1.7.
Workaround: Use user name and password-based authentication.
Table 216: Certificate Manager Known Issues
Configuration
Bug ID Description
93922 Symptom: A custom banner with the # delimiter is added as part of the show running-config command output.
Scenario: This issue is observed when an administrator configures the banner using the banner motd command in the controller with the # delimiter. This issue is not limited to any specific controller model and is observed in ArubaOS 6.3.1.1.
Platform: All platforms.
Reported Version: ArubaOS 6.3.1.1.
Workaround: None.
107978 Symptom: Information in the tech-support-logs file on the controller is missing.
Scenario: This issue is observed in 7220 controllers running ArubaOS 6.3.1.4.
Platform: 7220 controllers.
Reported Version: ArubaOS 6.3.1.4.
Workaround: None.
Table 217: Configuration Known Issues
Controller-Datapath
Bug ID Description
93817 Symptom: An internal error occurs in the master controller while provisioning APs associated with a specific local controller.
Scenario: This issue is observed in 3200XM controllers running ArubaOS 6.3.1.1 in a master-local topology.
Symptom: A master controller crashes. The log files for the event listed the reason as datapath timeout.
Scenario: This issue is observed in 7220 controllers running ArubaOS 6.3.1.1.
Platform: 7200 Series.
Reported Version: ArubaOS 6.3.1.1.
Workaround: None.
108007 Symptom: An AP does not connect to a master controller. This issue occurs when an AP and master controller are located in different locations and are connected through IPsec tunnel.
Scenario: This issue is observed in 3600 controllers running ArubaOS 6.3.1.9.
Platform: 3600 controllers.
Reported Version: ArubaOS 6.3.1.9.
Workaround: None.
108152 Symptom: A controller stops responding and reboots. The log files for the event listed the reason for the crash as datapath timeout.
Scenario: This issue is observed in M3 controllers running ArubaOS 6.3.1.5.
Platform: M3 controllers.
Reported Version: ArubaOS 6.3.1.5.
Workaround: None.
Table 218: Controller-Datapath Known Issues
ArubaOS 6.3.1.13 | Release Notes Known Issues and Limitations |136
137 | Known Issues and Limitations ArubaOS 6.3.1.13 | Release Notes
Controller-Platform
Bug ID Description
100707 Symptom: A controller reboots unexpectedly while executing cache instruction and the reason for the reboot is kernel panic.
Scenario: This issue is observed in 3600 controller in a master-local topology.
Platform: 3600 controllers.
Reported Version: ArubaOS 6.3.1.4.
Workaround: None.
103456 Symptom: A local controller reboots unexpectedly. The log files for the event listed the reason for the reboot as Control Processor Kernel Panic. This issue is caused by tty related function.
Scenario: This issue is observed in 7220 controllers running ArubaOS 6.3.1.7 in a master-local topology.
Platform: All platforms.
Reported Version: ArubaOS 6.3.1.7.
Workaround: None.
103970 Symptom: Some local controllers do not form IPsec link with the master controller. Although restarting IKE process on the affected local controller helps to form the IPsec link, other local controllers randomly get disconnected from the master controller.
Scenario: This issue is observed in controllers running ArubaOS 6.3.1.8 in master-local topology.
Platform: All platforms.
Reported Version: ArubaOS 6.3.1.8.
Workaround: Restart IKE process in the affected controller.
104139 104729 107907 108026 108194
Symptom: WMS and database modules reboot unexpectedly.
Scenario: This issue is observed in all controllers running ArubaOS 6.3.x and later versions.
Platform: All platforms.
Symptom: The httpd module crashes and restarts unexpectedly.
Scenario: This issue is observed in 7240 controllers running ArubaOS 6.3.1.8 and is caused by high CPU utilization during Captive Portal authentication.
Platform: 7240 controllers.
Reported Version: ArubaOS 6.3.1.8.
Workaround: None.
107989 Symptom: A controller reboots unexpectedly. The log file for the event listed the reason as Reboot Cause: kernel panic.
Scenario: This issue occurs when a 3000 Series controller is upgraded from ArubaOS 6.3.1.7 to ArubaOS 6.3.1.10.
Platform: 3000 Series controller.
Reported Version: ArubaOS 6.3.1.10.
Workaround: None.
Table 219: Controller-Platform Known Issues
IPsec
Bug ID Description
108038 Symptom: When the RAP rebootstrap threshold is high and if the RAP rebootstraps and moves to a different controller because of load balancer, the GRE tunnels on the previous controller to the inner IP of the RAP persists until the RAP rebootstrap is detected. This may result in some BC/MC traffic that is directed to the inner IP of the RAP to be sent in clear text.
Scenario: This issue is observed when GRE tunnels exist for the inner IP of a RAP even though there is no IPsec security association.
Platform: All platforms.
Reported Version: ArubaOS 6.3.1.6.
Workaround: None.
Table 220: IPsec Known Issues
Licensing
Bug ID Description
100234 Symptom: The ACL configuration on the local controller is out of sync with the master controller, when both the master and standby controller are rebooted simultaneously.
Scenario: This issue is observed in a master-standby topology where all the licenses are installed on the master controller. This issue is not limited to a specific controller model and is observed in ArubaOS 6.3.1.5.
Platform: All platforms.
Reported Version: ArubaOS 6.3.1.5.
Workaround: None.
Table 221: Licensing Known Issues
Remote AP
Bug ID Description
107527 Symptom: Wired bridge user is mapped with incorrect ACLs even though the wired bridge user is mapped with correct user role.
Scenario: This issue is observed in RAPs connected to controllers running ArubaOS 6.3.1.8.
Platform: All platforms.
Reported Version: ArubaOS 6.3.1.8.
Workaround: Allow all traffic to internal DHCP pool IP address of RAP on unauthenticated role.
108030 Symptom: RAP does not come up on the controller.
Scenario: This issue is observed in a master-local topology on 7220 controllers running ArubaOS 6.3.1.7
Platform: 7220 controllers.
Reported Version: ArubaOS 6.3.1.7.
Workaround: None.
Table 222: Remote AP Known Issues
ArubaOS 6.3.1.13 | Release Notes Known Issues and Limitations |138
139 | Known Issues and Limitations ArubaOS 6.3.1.13 | Release Notes
Station Management
Bug ID Description
107980 Symptom: The STM process on a local controller crashes and reboots. The log file for the event listed the reason as Reboot Cause: illegal instruction.
Scenario: This issue is observed on 7240 controllers running ArubaOS 6.3.1.10.
Platform: 7240 controllers.
Reported Version: ArubaOS 6.3.1.10.
Workaround: None.
108299 Symptom: Clients are unable to connect to the bridge-mode SSID of RAP and the output of the show auth-tracebuf command displays the received eapol-pkt before assos error. Also, the output of the show aaa authentication-server radius statistics command displays an incorrect value for average response time (AvgRspTme ).
Scenario: This issue is observed when multiple re-authentication requests are sent to a RAP connected in bridge mode.
Platform: All platforms.
Reported Version: ArubaOS 6.3.1.9.
Workaround: Upgrade to ArubaOS 6.4.2.x.
Table 223: Station Management Known Issues