Sie sind auf Seite 1von 5

PRODUCT RELEASE NOTES

PRODUCT: ARRAY OPERATING SYSTEM


RELEASE DATE: 29 OCTOBER 2018
VERSION: 8.5.1 – 7572

CONTENTS
1) New Features
2) Fixed Problems
3) Known Issues
4) Limitations and Conditions
5) Hardware and Software Requirements
6) Contacting Support

1) NEW FEATURES
• Support for XH2-240
• WDS on 802.11ac Wave2 APs
• UPoE (Universal Power over Ethernet) support for XD4-240/XA4-240
• Station to station blocking per SSID
• Bug-fixes

2) FIXED PROBLEMS
• 33883 – 802.11ac Wave 2 APs restart intermittently when WMM-ACM voice/video is
enabled in global settings
• 33886 – For 2.4GHz connections to 802.11ac Wave 1 APs, the AP shows a lower RSSI for
a station than the station does. This reduces performance.
• 33889 – WDS link doesn't work with XH2-240 as the host. Client AP is unable to form
link to XH2’s SSID if its encryption is WPA2-PSK.
• 33907 – On 802.11ac Wave 2 radios, when bonding is changed from 20 Mhz to 40 MHz,
currently associated stations stay at the 20 MHz data rate (other bonding width changes
did not have this problem).
• 33909 – Can't disable transmit beamforming (tx-bf) on IAP1 of the XD2-230.
• AOS-81 (33401) – On 802.11ac Wave 2 APs using WPA2/EAP authentication, station can
associate but is sometimes unable to re-associate later on. Identity is sent, but the
station can’t reconnect.
• AOS-91 - Application Control, process was restarting frequently. Syslog shows, “Process
restart required: Application Control, restarting process.”
• AOS-153 (33870) – A non-80211w capable station (such as Samsung Galaxy Tab A) is
intermittently unable to fully associate when AP is set to 11w capable. Station is able to
authenticate, but doesn't associate.
• AOS-168 (33891) –Wave 1 APs are not able to transmit packets at some .11ac data rates
when .11ac capable Chromebooks are associated.
• AOS-175 – When using an Active Directory server for client authentication, in some
cases a warning is not issued if the Hostname max length of 15 characters is exceeded.
• AOS-177 – DNS server settings are blanked out (reset to null) in the following situation:
the DNS server is set to static (use-dhcp off) and GIG1 uses DHCP, then the problem
occurs if the DHCP server does not send DNS server values along with the IP address.
• AOS-197 – Stations experiencing problems connecting to Wave 2 APs. Fixed by process
serialization of its messaging to the lower layers.
• Character set (XMSC-2268) – When entering text fields such as AP Location, you are
currently restricted to the Latin character set.

3) KNOWN ISSUES
• 33141 / 33399 – Clients associated to 802.11ac Wave1 APs with arp-filter proxy
configured are unable to IPv6 ping each other
• 33398 – Wave1 APs with arp-filter set to proxy is rebroadcasting ARP request packets
from wireless clients.
• 33663 / 33817 – Stations may get disassociated due to a radio reset. The syslog will
show "Low activity condition detected on IAP iap1. Resetting IAP." message.
• 33821 – EAP stations may stop passing traffic until client re-associates
• 33827 – EAP clients on wave2 APs may stop passing traffic until client re-associates
• 33828 – When there are many stations associated to radio1 on an XD2-230, they are
experiencing poor performance, high ping loss and delay and video freezes
• 33833 – XD2-230 may send unnecessary CTS packets when 802.11g devices are present
in the environment
• 33851 – Some stations are unable to pass traffic when MU-MIMO is enabled
• 33878 – Beacon Intervals and RSSI levels on 802.11ac are not consistent in 2.4GHz.
• 33893 – On 802.11ac Wave 2 APs, changing the 802.11k (Radio Resource Management)
in global settings doesn’t take effect until after a reboot.
• 33896 – 802.11r capable iPads are not able to associate to an SSID when 802.11r (fast
roaming) and .11w (Protected Management Frames) are enabled.
• 33924 - Stations connected to Wave 2 APs occasionally can’t pass traffic. On the station,
turning Wi-Fi off and on will fix the problem.

2
• 33925 – When Wave 2 APs with certain Timeshare monitor mode settings are stressed
with a high volume of traffic, the radio can go into a reset loop causing station
connectivity problems.
• 33926 - WDS Link recovery is slow on Wave 2 APs after replacing a WDS client or host
AP - it takes a long time to re-establish a WDS link. After configuration of the new unit is
complete, reboot the APs on both sides of the link to prevent this delay.
• 33929 - On XH2-240 AP, loading a configuration file via the CLI gives an error for "reset-
button on". The config file is loaded and the CLI continues to the next statement.
• AOS-111 – For Radius Mac authentication, the Session Timeout is not honored, thus the
session doesn’t timeout.
• AOS-206 – On Wave 2 APs, Location Positioning information is not supported.

4) LIMITATIONS AND CONDITIONS


• 28675 - Packet Counts for a DNS redirect filter may sometimes be less than the actual
number of DNS packets modified.
• 30392 - Bonjour – AppleTV is not able to service a client on SSID with VLAN when
AppleTV is on the Bridged wired network. It is not recommended that you place
AppleTV on the Bridged Management LAN segment. This will cause a lot of multicast
traffic to be processed by the Array on the Management VLAN and can affect
performance of the Array. Isolation of Multicast Traffic is recommended to be handled
in VLANs that are not part of the Array Management VLAN.
• AOS-89 – In some situations, multiple DHCP requests from AP result in DHCP server
assigning 2 or 3 IP addresses to the same AP. This can exhaust a DHCP pool during a
simultaneous reboot of all APs
• WDS – When doing a software upgrade, WDS client (remote) APs must be upgraded
before WDS host (network-connected) APs. XMS-Cloud will not automatically apply
upgrades in this order for you.
• WDS - Using WDS between different families of APs (e.g., WDS between an XD AP and
an XR AP, or between Wave 1 and Wave 2 XD APs) is not recommended. If you must
create a link between different radio types, set the most advanced AP type as the host.

5) HARDWARE AND SOFTWARE REQUIREMENTS


• XI-AC3470 is equipped with 4 Tx chains, Rx chains and 4 spatial streams. Depending on the Access Point
capacity, the AOS will automatically configure each radio module to obtain optimal functionality. The table
below lists different operating modes based on the HD modular AP and number of radios installed.

• Wave 2 Radio Module Operating Modes

Tx Rx
Model Streams Tx power per radio
Chains Chains

XR-2247 4 4 4 No Tx power restrictions

3
Tx Rx
Model Streams Tx power per radio
Chains Chains

Mon + 5G + 5G + 2.4G 13 dBm(default)


5G + 5G + 5G + Mon 12 dBm
5G + 5G + 5G + 5G 12 dBm
XR-2447 3 4 3
5G + 5G + 5G + 2.4G 13 dBm
5G + 5G + 2.4G + 2.4G 14 dBm
5G + 2.4G + 2.4G + 2.4G 15 dBm

XR-4447 4 4 4 No Tx power restrictions

XR-4847 4 4 4 No Tx power restrictions

Mon + 2 2.4G + 5 5G 18 dBm (default)


XR-6847 4 4 4 All configurations + Mon 18 dBm
All radios with no Mon No Tx power restrictions

Mon + 3 2.4G + 8 5G 18 dBm (default)


XR-7247 4 4 4 All configurations + Mon 18 dBm
All radio with no Mon No Tx power restrictions

Mon + 3 2.4G + 12 5G 12 dBm (default)


Mon + 2 2.4G + 13 5G 10 dBm
XR-7647 4 4 4
Mon + 1 2.4G + 14 5G 8 dBm
Mon + 15 5G 6 dBm

• Wave 2 Radio Module Upgrade Configurations. The table below summarize power requirements
and configurations for installing XI-AC3470 radios in an XR modular AP.

# Radios
Upgraded Which Slots to Use (RF
Model Series after Watts / Injector Models
Model No Slot #s)
Upgrade
30W, PoE+
XR-2000 XR-2247 2 0, 2 XP1-MSI-30, XP1-MSI-75M, XP8-MSI-
70M, XT-5024/5048
40W
XR-2000 XR-2447 4 All slots XP8-MSI-70M,
XP1-MSI-75/75M
75W
XR-4000 XR-4447 4 1, 3, 5, 7 XP8-MSI-70M,
XP1-MSI-75/75M
75W
XR-4000 XR-4847 8 All slots
XP1-MSI-75/75M

4
# Radios
Upgraded Which Slots to Use (RF
Model Series after Watts / Injector Models
Model No Slot #s)
Upgrade
95W
XR-6000 XR-6847 8 0, 2, 4, 6, 8, 10, 12,14
XP2-MSI-95M (one port)
0, 1, 2, 4, 5, 6, 8, 9,10, 95W
XR-7000 XR-7247 12
12,13,14 XP2-MSI-95M (two ports)
95W
XR-7000 XR-7647 16 All Slots
XP2-MSI-95M (two ports)

6) CONTACTING RIVERBED SUPPORT


Visit the Riverbed Support site to download software updates and documentation, browse our
library of Knowledge Base articles and manage your account. To open a support case, choose
one of the options below.
Phone
Riverbed provides phone support at 1-888-RVBD-TAC (1-888-782-3822). Outside the U.S. dial
+1 415 247 7381.
Online
You can also submit a support case online
Email
Send email to support@riverbed.com. A member of the support team will reply as quickly as
possible.

©2018 Riverbed Technology. All rights reserved. Riverbed and any Riverbed product or service name or logo
used herein are trademarks of Riverbed Technology. All other trademarks used herein belong to their respective
owners. The trademarks and logos displayed herein may not be used without the prior written consent of
Riverbed Technology or their respective owners.