User guide

AirWave 7.4.0 |Release Notes 15
Known Issues
The following are known issues for AirWave 7.4.0:
DE10070 For IOS APs, the AP Include fields have been removed from the APs/Devices > Manage page and
from the list of available variables in the template pages.
DE10182 AMP now properly restricts the firmware download protocol for Aruba AirMesh to FTP-only.
DE10266 VisualRF: Previously, editing could become locked when a user with the AP Manager role with read-
write access to VisualRF and read-only access to devices tries to add a deployed AP.
Only AMP Administrators and AP Device managers with read-write access to the device could edit
floorplans.
Now AMP retrieves the user role permission to determine if a user can perform write actions.
Table 8 Known Issues in AirWave 7.4.0
ID Description
The following are known issues with stacking support for the Aruba Mobility Access Switch and other
stackable switches:
 Aruba recommends keeping Aruba switches and Aruba controllers in separate groups due to
overlaps in configuration.
 When an Aruba member switch is physically removed from a stack and the primary/master no
longer reports information about it, AMP shows the message “Unexpected LAN MAC <failed to
fetch> rather than a clear statement that the member has simply been removed. The user-friendly
statement is shown correctly for Alcatel-Lucent switches.
 AMP sets a switch role to “Unknown” if a member switch it does not appear in member discovery
payloads, but this may result in minor interface monitoring issues. For instance, two members in a
stack might have the same AP index (which identifies a member’s place in a stack) and interfaces
may display on the wrong member switch.
 If a Cisco 3750 stack is down and the master is brought up, non-persistent page crashes may
result. The problem usually resolves after a few minutes.
DE10102 Clients wired to line cards are displaying in AMP as being associated to the Primary switch. This does
not affect client count and bandwidth usage statistics, but affects slot differentiation.
DE10565 VisualRF: Clients of Aruba Instant IAPs may appear on the wrong floor plan.
DE10629 The Trigger Definition “Total Radius Authenticatiuon Issues” is missing a Supress until
Acknowledged field.
DE10657 Stacked line card (member) switches may report a mismatch. The desired behavior is that primary/
master switches should handle configuration, and line cards should always should a “Good”
configuration status.
DE10658 AirWave has not yet universally changed the terminology for switches from master/member to primary/
secondary/line card in some buttons and list columns.
DE10669 VisualRF: Switches and controllers display as down after restoring from backup until VisualRF is
restarted.
DE10670 VisualRF: Floor plans need to be refreshed to display the heatmap after autoprovisioning APs.
DE10673 VisualRF: If APs are brought up from the down status, the AP radio may display an error.
DE10674 VisualRF: Restart is required to view overlays after importing a controller’s floor plan backup.
DE10685 When attempting to view a rogue detail page from a Master Console using the rogue client report, an
Access Denied page may display.
DE10686 VisualRF: Restart is required if a device override is applies for all client devices. If done individually,
only a page reload is needed.
Table 7 Resolved Issues in AirWave 7.4b1 (Continued)
ID Description