MeshOS 4.

Release Notes
Copyright
2014 Aruba Networks, Inc. Aruba Networks trademarks include , Aruba Networks, Aruba Wireless Networks,
the registered Aruba the Mobile Edge Company logo, Aruba Mobility Management System, Mobile Edge Architecture, People Move.
Networks Must Follow, RFProtect, Green Island. All rights reserved. All other trademarks are the property of their respective owners.
Open Source Code
Certain Aruba products include Open Source software code developed by third parties, including software code subject to the GNU
General Public License (GPL), GNU Lesser General Public License (LGPL), or other Open Source Licenses. Includes software from Litech
Systems Design. The IF-MAP client library copyright 2011 Infoblox, Inc. All rights reserved. This product includes software developed by
Lars Fenneberg et al. The Open Source code used can be found at this site:
http://www.arubanetworks.com/open_source
Legal Notice
The use of Aruba Networks, Inc. switching platforms and software, by all individuals or corporations, to terminate other vendors VPN
client devices constitutes complete acceptance of liability by that individual or corporation for this action and indemnifies, in full, Aruba
Networks, Inc. from any and all legal actions that might be taken against it with respect to infringement of copyright on behalf of those
vendors.
Warranty
This hardware product is protected by an Aruba warranty. For details, see Aruba Networks standard warranty terms and conditions.

www.arubanetworks.com
1344 Crossman Avenue
Sunnyvale, California 94089
Phone: 408.227.4500
Fax 408.227.4550

MeshOS 4.7 | Release Notes 0511346-01 | May 2013

 Contents

Chapter 1 Release Overview .................................................................................... 5

Release Note Overview .........................................................................................5
Contacting Support ...............................................................................................5

Chapter 2 Whats New in this Release .................................................................... 7

Improved Channel Assignment .............................................................................7
WMI .................................................................................................................7
CLI...................................................................................................................7
Interference Detection and Avoidance for Backhaul Radios.................................8
WMI .................................................................................................................8
CLI...................................................................................................................8
CLI Improvement ...................................................................................................8
Improvement on Manually Restoring the Factory Default State............................9

Chapter 3 Fixed Issues ........................................................................................... 11

Chapter 4 Known Issues......................................................................................... 13

MeshOS 4.7 | Release Notes | 3

4 | MeshOS 4.7 | Release Notes
 Chapter 1

Release Overview

MeshOS 4.7 is a major software release that introduces enhancements and fixes to many known or
outstanding issues. For details on all of the features described in the following sections, refer to the Aruba
MeshOS 4.7 User Guide and the Aruba MeshOS 4.7 Command Reference Guide.

Release Note Overview

Chapter 2, Whats New in this Release on page7 describes the new features introduced in this release.
Chapter 3, Fixed Issues on page11 describes the issues that have been fixed in this release.
Chapter 4, Known Issues on page13 provides descriptions and workarounds for outstanding issues in
MeshOS 4.7.

Contacting Support
Table 1 Contact Information

Main Site arubanetworks.com

Support Site support.arubanetworks.com

Airheads Social Forums and community.arubanetworks.com

Knowledge Base

North American Telephone 1-800-943-4526 (Toll Free)

1-408-754-1200

International Telephones http://www.arubanetworks.com/support-services/support-program/

contact-support

Software Licensing Site licensing.arubanetworks.com

End of Support information http://www.arubanetworks.com/support-services/end-of-life-products/

end-of-life-policy/

Wireless Security Incident http://www.arubanetworks.com/support-services/security-bulletins/

Response Team (WSIRT)

Support Email Addresses

Americas, APAC, and EMEA support@arubanetworks.com

WSIRT Email wsirt@arubanetworks.com

Please email details of any
security problem found in an
Aruba product.

MeshOS 4.7 | Release Notes Release Overview | 5

6 | Release Overview MeshOS 4.7 | Release Notes
 Chapter 2

Whats New in this Release

The MeshOS 4.7 release includes the following new features and enhancements:
Improved Channel Assignment on page7.
Interference Detection and Avoidance for Backhaul Radios on page8.
Interference Detection and Avoidance for Backhaul Radios on page8.
Improvement on Manually Restoring the Factory Default State on page9.

Improved Channel Assignment

The channel assignment algorithm has been improved by considering more about a channels interference
when assigning channel to a radio. Each channels interference information will be collected and used in
channel assignment process. The channel assignment has also been improved by trying to avoid any two
radios channel overlap with each other (If two radios channels are less than 20MHz from each other, they
are considered to overlap with each other).

WMI
No change in the WMI.

CLI
MeshOS 4.7 includes show mesh channel-information [dot11radio <r>] command to display the
interference information of a channel.
The following example shows the use of the command:
(host)# show mesh channel-information dot11radio 1
Column name abbreviation
NF: channel's noise floor;
UTIL: channel's total utilization;
WIFI: channel's WIFI utilization;
INTF: channel's interference utilization;
INTF-L: interference level, for detection and avoidance;
NGH-CNT: channel's backhaul neighbor count/connecting to me;
ADJ-UTIL: channel's adjusted utility, for channel selecting;
FLAGS: channel flags;
A - Allowed channel;
D - DFS channel;
W - Weather radar channel;
R - Radar detected;
I - Heavy interference channel;
O - Overlap with other radio;
C - Candidate channel;
Radio 1 channel list:
Channel NF UTIL WIFI INTF INTF-L NGH-CNT ADJ-UTIL FLAGS
20 -119 3% 2% 1% 0 1/0 10% AO
21 -118 5% 3% 2% 1 0/0 2% AO
22 -118 4% 3% 1% 0 0/0 1% AO
23 -117 30% 27% 3% 1 0/0 7% AO
24 -117 0% 0% 0% 0 0/0 0% AC

MeshOS 4.7 | Release Notes Whats New in this Release | 7

 25 -118 1% 0% 1% 0 0/0 0% AC
26 -118 0% 0% 0% 0 0/0 0% AC
149 -107 2% 1% 1% 4 1/1 0% AC
153 -107 0% 0% 0% 4 0/0 0% AC
157 -107 5% 2% 3% 5 2/0 15% AO
161 -107 0% 0% 0% 4 0/0 0% AC
165 -107 2% 1% 1% 4 2/0 14% AC

Interference Detection and Avoidance for Backhaul Radios

This feature allows users to see the working and scanning channels interference information, such as
channel utilization, WiFi utilization, interference utilization and etc. This feature also allows users to
configure the interference threshold and enable/disable the interference avoidance function.
When the interference avoidance is enabled (by default, the interference avoidance is disabled), if the
current working channels interference level is larger than the interference avoidance threshold value (by
default, the interference avoidance threshold value is 30), the radio channel will be switched to another
channel. In the channel assignment process, when the channels interference level is larger than the
configured interference threshold, the channel will not be assigned.

It is recommended to disable interference avoidance when a lot of non-wireless interference exists in the
environment.
NOTE

WMI
No change in the WMI.

CLI
MeshOS 4.7 includes four new CLI command as follows:
The show interface dot11radio <r> current-channel metric command to show wireless
environment of working channels.
The interference-threshold <1-100> command to configure the wireless interference threshold
value.
(host)> enable
(host)# configure terminal
(host)(config)# mesh
(host)(config-mesh)# interference-threshold 17
(host)(config-mesh)#
The interference-avoidance command to configure the interference avoidance feature for the
backhaul radio.
The no interference-avoidance command to disable the interference avoidance feature.

CLI Improvement
MeshOS 4.7 adds the show mesh paths [option] command to show the paths to all routers or a specific
hostname or Site-ID in the mesh. This command is very useful to troubleshoot the dot11radio interface.

8 | Whats New in this Release MeshOS 4.7 | Release Notes

 Improvement on Manually Restoring the Factory Default State
Prior to MeshOS 4.7, if a device is powered off and then powered on for six times, waiting 60 seconds
between each time, the device will revert to the factory default state without any configuration reserved.
With MeshOS 4.7, the device now will revert to the factory default state with the following user-defined
configuration reserved:
Hostname
Mesh-ID
Authentication open key-management wpa2
psk ascii <key string>

When a device is manually restored to the factory default state by the 6-times power cycling method, if the default
SSID of the BSS of the router is deleted, its configuration of authentication open key-management wpa2 will not be
NOTE reserved.

However, if a device has experienced 6 times power cycling once before, when this device goes through the
6 times power cycling again, it will revert to the factory default state without any configuration reserved.

MeshOS 4.7 | Release Notes Whats New in this Release | 9

10 | Whats New in this Release MeshOS 4.7 | Release Notes
 Chapter 3

Fixed Issues

The following issues and limitations have been fixed in the MeshOS 4.7 release:.

Table 1 Fixed in MeshOS 4.7

Bug ID Description

11551 Symptom: The debug dot11radio 0 scan command used to scan available APs in a network
displays inaccurate data.
Scenario: This issue occurred because the calculation method of the signal is changed. This issue
was seen in MeshOS 4.6

11583 Symptom: An issue in the WRM may sometimes cause MSR4000 to reboot automatically.
Scenario: This issue was seen in MeshOS 4.5.

11594 This bug is the duplicate of the bug 11589 and has been solved in MeshOS 4.6.0.1.
Symptom: The mesh point APs need 1-3 hours to resend a WDS link request to the gateway AP
when the existing WDS link fails.
Scenario: This issue was seen in MeshOS 4.6.

11598 This bug is the duplicate of the bug 11551.

Symptom: The debug dot11radio 0 scan command used to scan available APs in a network
displays inaccurate data.
Scenario: This issue occurred because the calculation method of the signal is changed. This issue
was seen in MeshOS 4.6

11612 Symptom: No method to quickly and accurately debug VPLM data path problem.
Scenario: This issue occurred when VLANs fail to ping each other in a VPLM enabled mesh
network. This issue was seen in MeshOS 4.6.

11635 Symptom: If a gateway AP in a network is down, mesh point APs can not associate to another
gateway AP in the same network.
Scenario: This issue was seen in MeshOS 4.6.

11640 Symptom: MSR routers cannot forward multicast traffic from an AP to a client.
Scenario: This issue was seen in MSR4000 and MSR2000 running MeshOS 4.5 or later.

11642 Symptom: If there are two APs and one AP is physically farther to the gateway than the other AP
and when the AP farther to the gateway is upgraded from MeshOS 4.5 to 4.6 but the other AP
remains at MeshOS 4.5 version, the AP that got upgraded can not connect back to the AP with
MeshOS 4.5.
Scenario: This issue was seen when upgrading an AP from MeshOS 4.5 to 4.6.

11648 Symptom: When multiple clients get associated to a radio with the same SSID and if one of the
clients is powered off, the other clients experience latency and may get disassociated.
Scenario: This issue is known to exist in all MeshOS releases. The cause was attributed to large
amount of RTS packets that are sent from the AP to the client that is powered off.

11650 Symptom: When upgrading image from MeshOS4.5 to 4.6.0.1, two of the MSR routers found
kernel crash, and caused to factory default configuration.
Scenario: This issue was seen when upgrading an AP from MeshOS 4.5 to 4.6.

MeshOS 4.7 | Release Notes Fixed Issues | 11

 Table 1 Fixed in MeshOS 4.7

Bug ID Description

11652 Symptom: Sometimes one of the radios used to provide BSS access had no response. This issue
is still exist when shutting down the radio port but will be gone after rebooting the device.
Scenario: This issue was seen in MeshOS 4.6.

11653 Symptom: Improper alignment of the 1st line of the command output in the WebUI of the
MSR2000 under maintenance > troubleshooting tools.
Scenario: This issue was seen in MeshOS 4.6.

11667 Symptom: An issue in the WRM cause tx-buffer leak.

Scenario: This issue was seen in MeshOS 4.6.

11670 Symptom: Very high frame loss was found across L2 VPLM mesh with redundant portals.
Scenario: This issue was seen in MeshOS 4.6.

11674 Symptom: PA got burned out in BSS/WDS mode and lots of power spikes were observed when
dual radios on a same MSR router working in 5.8GHz band with bidirectional traffic.
Scenario: This issue was seen in MeshOS 4.6.

11678 Symptom: When setting the WPA2-PSK, the CLI doesnt accept space in the key setting while the
WebUI accept the space. For example, users cant execute command wpa-type psk ascii
12345 6789 in CLI mode but they can set this in WEBUI.
Scenario: This issue was seen in MeshOS 4.6.

11679 Symptom: The rts threshold command need to be added for STA- mode.
Scenario: The required command is added in MeshOS 4.7.

11692 Symptom: When two MSR routers can't build WDS link due to mismatched mesh PSK, the
displayed reason of the WDS link failure is incorrect.
Scenario: This issue was seen in MeshOS 4.6.

11697 Symptom: If a device is powered off and then powered on for six times, waiting less than 60
seconds between each time, the device will revert to the factory default state without any
configuration reserved. This need to be changed into the device will revert to the factory default
state with the configuration of hostname, Mesh-ID, Authentication open key-management wpa2
and psk ascii <key string> reserved.
Scenario: The required configuration is added in MeshOS 4.7.

11704 Symptom: VPLM set some node's vlan as 0 in mac-address-table. When a MSR router want to
send layer2 packets, the router will check mac-address-table and decide which node the packets
should be sent to. However, if MSR found the vlan is 0 in mac-address-table, it won't send out the
packets and therefore the two MSR nodes couldn't ping each other.
Scenario: This issue was seen in MeshOS 4.6.

12 | Fixed Issues MeshOS 4.7 | Release Notes

 Chapter 4

Known Issues

The following are the known issues and limitations for this release of MeshOS. Applicable bug IDs and
workarounds are included:

Table 2 Known Issues and Limitations

Bug ID Description Workaround

10040 Cross VLAN roaming is not supported. A client has to stay None
within the same VLAN.

10566 When an AP is working in VPLM mode with MOTRIX
enabled, the supplicant is working in bridge mode, and
DHCP is configured in the VLAN interface, MOTRIX may take
a supplicant, which is brought online after a while, offline
every minute.
Disable MOTRIX in Layer- 2
network. In the case of cross IP
subnet Layer- 3 roaming, a client-
list is helpful to avoid this issue.

10879 If the channel-list on both sides of the WDS are not alike, Set same channel-list on both
mesh links may not form. sides.

10906 The show mesh route command fails to get a mesh route None
via Ethernet link if Ethernet is working on backhaul mode.

11098 MSR client roaming may sometimes fail in Layer-3 mesh None
network.

11371 The audio for the Antenna Alignment Tool does not work Use either Internet Explorer or
well on Safari browser and mobility platform. Mozilla Firefox.

11401 The 20 MHz DFS channels may take more than 5 minutes to Use the channel-list.
come up.

11402 The 40 MHz weather DFS channels may take more than 30 Use the channel-list.
minutes to come up.

11507 AWR cannot broadcast static routes in VPLM mode. This is a Use DHCP or manually set static
limitation in MeshOS. route.

11519 In a VPLM network, if the Site-ID value is 0 for a wired AP, None
the output of the show vplm mac-address-table
command shows the value 0 for the Site-ID of all local
clients (wired and wireless). This is a limitation in MeshOS.

11539 The PLCP information in the radio statistics differed for the None
MSR devices and Aruba devices, which were in the same
room.

11541 A VPLM network drops the first packet that comes into the Try the session again.
wired interface, which is used for MAC learning. This causes
some of the sessions to terminate. This is a limitation in
MeshOS.

11586 When the VPLM mode is configured, Adaptive Wireless None

Routing (AWR) should not broadcast the access side (VLAN
interface) routes. The current behavior of the VPLM is not
consistent with this.

MeshOS 4.7 | Release Notes Known Issues | 13

 Table 2 Known Issues and Limitations (Continued)

Bug ID Description Workaround

11683 The rts threshold configuration need to be added in Use CLI command rts
WebUI for STA and Mesh mode to solve hidden nodes issue. threshold

14 | Known Issues MeshOS 4.7 | Release Notes