The STM process in a managed device that is part of a cluster setup crashed unexpectedly. This issue was observed in Mobility Masters running ArubaOS The fix ensures that the Mobility Master works as expected. Output of the show switches command displayed the Module Configuration Went into PROCESS_NOT_RESPONDING_CRITICAL state. The CFGM process in a Mobility Master stopped responding and The fix ensures that the managed device works as expected. The managed device running ArubaOS 8.3.0.4. Though the VLAN was not mapped on any node or group on Users were unable to delete the VLAN even The log file listed the reason for this event as kernel panic: Rebooting the AP because of FW ASSERT.
#PORTAL RELOADED TRIGGER BUG SERIES#
This issue was observed Managed devices running ArubaOS 8.3.0.6.ģ00 Series access points running ArubaOS 8.2.2.0 or later versions crashed and rebooted unexpectedly. This issue occurred when the cluster leader receives a deactivate event from DDS of a different managed device that was a previous leader. This issue was observed in Mobility Masters running ArubaOS 8.0.1.0 or later versions.Ī few APs were unable to join a cluster and rebooted with unable to contact switch: HELLO-TIMEOUT error message. The fix ensures that the Mobility Masters work as expected. The profmgr process crashed and the Mobility Master rebooted unexpectedly. The fix ensures that the Remote APs work as expected. The log file listed the reason for this event as, Reboot caused by kernel panic: Fatal exception in interrupt. The fix ensures that the Virtual Mobility Controllers work as expected.Ī few Remote APs running ArubaOS 8.3.0.0 or later versions crashed and rebooted unexpectedly. This issue occurred in AirMatch when invalid utf8 character was used in ap-name string. Some Virtual Mobility Controllers running ArubaOS 8.3.0.0 or later versions crashed unexpectedly. This issue was observed in managed devices running ArubaOS8.6.0.5 or later versions. Some managed devices log the error message, INFO> |dot1x-proc:1| Sending request for Switch IP6 although there are no IPv6 configurations in the network.
This issue was observed in Mobility Masters running ArubaOS 8.4.0.0 or later versions. The fix ensures that WebUI displays the OS and connected to fields. The Dashboard > Overview > Remote Clients page of the WebUI did not display any value for OS and connected to fields. This issue was observed in AP 305 access points running ArubaOS 6.5.1.10 or earlier versions. The fix ensures that AP 305 access points work as expected with high throughput. Some access points did not connect or experienced low throughput. This issue was observed in APs running ArubaOS 8.5.0.9 or later versions in a Mobility Master- Managed Device topology.
The fix ensures that the APs work as expected. The log files listed the reason for the event as Reboot caused by kernel panic: Rebooting the AP. This issue was observed in APs running ArubaOS 8.2.0.0 or later versions.Ī few APs crashed and rebooted unexpectedly. The fix ensures that the APs do not establish tunnels with an incorrect MTU size. This issue occurred when jumbo frames were enabled. This issue was not limited to any specific controller model or ArubaOS release version.ĪPs established tunnels with an incorrect MTU size. This issue occurred when TLS v1.2 was enabled in the SSL protocol of a web server profile. The fix ensures that database synchronization works as expected. The database synchronization between master and standby Mobility Master failed.
Table 1: Resolved Issues in ArubaOS 8.8.0.0 This topic describes the resolved issues in this release.
0 kommentar(er)
