release notes for ringmaster version 8.0.6 notes for ringmaster version 8.0.6.1 3 licensing for...

Release Notes for RingMaster Version 8.0.6.1

Juniper Networks recommends that you familiarize yourself with these release notes and the Juniper Networks RingMaster Quick Start Guide, and the Juniper Networks RingMaster documentation suite before installation. For additional product information, refer to the following documents:

RingMaster Quick Start Guide Version 8.0

RingMaster Planning Guide Version 8.0

RingMaster Configuration Guide Version 8.0

RingMaster Management and Monitoring Guide Version 8.0

Open issues with WLC1200-UMSP are tracked in this document.

Feedback and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2What's New in RingMaster Version 8.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Version Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Licensing for RingMaster Version 8.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Upgrading from RingMaster Version 7.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Downgrading to a Previous RingMaster Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Known Issues for RingMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Open Issues with WLM1200-UMSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Issues Resolved in RingMaster Version 8.0.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Issues Resolved Since RingMaster Version 8.0.5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Issues Resolved Since RingMaster Version 8.0.4.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Issues Resolved Since RingMaster Version 8.0.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Issues Resolved Since RingMaster Version 8.0.1.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Documentation Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Submitting Problem Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Informational Note: Please note that the tracking numbers for issues open and resolved have changed to reflect the Juniper Networks tracking system.

Copyright © 2015, Juniper Networks, Inc. 1


Product Name Changes

Please note that the former Trapeze products now reflect the Juniper Networks product names.

Feedback and Support

Juniper Networks encourages you to provide feedback about your experiences installing and using the product to the Juniper Networks Customer Assistance Center (TAC).

What's New in RingMaster Version 8.0

RingMaster 8.0 has the following enhancements:

WLA532E—The WLA532E is a new access point model that supports external antennas.

Adaptive Channel Planner (Auto-Tune Enhancements)—Adaptive Channel Planner (ACP) dynamically assigns the WLA operating channel so that the wireless network can efficiently adapt to the RF environment conditions. Dynamic assignment can be changed when significant changes are measured in the interference level or in the network topology. Eventually, Wi-Fi bandwidth is maximized and maintains the efficiency of communication over the wireless network.

Transmit Beam-forming—Transmit beam-forming (TxBF) is a technique that uses an array of transmitting antennas to send radio signals with adjusted magnitude and phase at each antenna to achieve a focused beam target to the receiver. TxBF can increase the Signal-to-Noise Ratio (SNR) at the receiver and improve performance. This feature is supported on the WLA532, WLA532E, WLA321, and WLA322.

IPv6 Support —In this release of RingMaster, configuring IPv6 addresses is not supported, but IPv6 clients are supported. The WLC can view IPv6 session information and control IPv6 ACLs.

Device Fingerprinting—This feature supports the ability of RingMaster to detect the type of device used by a client when authenticating on the wireless LAN. Devices include iPads, iPhones, Windows PC, tablets, and more. This feature implements the DHCP fingerprinting method.

Version Compatibility

This version of RingMaster has been verified against MSS Version 8.0.

This version of RingMaster is intended for use with MSS Version 8.0.3.6 or higher only.

Network plans created with RingMaster 7.1 and later are compatible with this version of RingMaster. If you want to use network plans created with previous versions of RingMaster, make sure the option to delete the network plans directory is not checked when you uninstall.

If you are installing for the first time, you will need to install and activate licenses before using RingMaster. If you are upgrading from a previous licensed version, you do not need to reinstall your licenses.

Former Trapeze Name Current Juniper Product Name

MXR-2 WLC2

MX-8 WLC8

MX-200 WLC200

MX-800 WLC800

MX-2800 WLC2800

MP-522 WLA522

MP-632 WLA632

2 Feedback and Support Copyright © 2015, Juniper Networks, Inc.

http://www.juniper.net/customer/support

http://www.juniper.net/customer/support


If you are upgrading from 7.0 or earlier, Juniper Networks recommends that you upgrade to 7.4 first, then upgrade to 7.5, and then to 7.6. Once you’ve installed the latest version of 7.6, you can upgrade to 7.7.

Licensing for RingMaster Version 8.0

Licensing OverviewJuniper sends two kinds of tokens electronically, in e-mail, in response to ordered licenses: Software Serial Numbers, and Authorization Codes. Software Serial numbers are sent when you order a base system (e.g., WLM-RTMS). Authorization Codes ("AuthCodes") are sent when an additional capacity or feature is ordered. Both token types are transacted at the Juniper Networks License Management System (LMS) to provide license key to the customer. The Software Serial Number is also used to gain access to Juniper's software download center. Included in the email are "next steps" instructions that you can follow to complete the process. These instructions also are found on Juniper Licensing page (https://www.juniper.net/generate_license/ ) under the headings Download and Activate Your Software and Activate Your Software Capacity and/or Features.

Software Licensing 1. To get your keys after on receiving the base serial number or AuthCode, go to the generate license keys page

(https://www.juniper.net/lcrs/license.do). Enter your support login information and follow the instructions. Access to the licensing server requires your Juniper Networks Customer Support Center (CSC) loginID.

2. Once you have the license keys, you can activate them online or offline at https://www.juniper.net/lcrs/wlmSelectAuthCodeLicenseType.do and follow the instructions for the “Offline Activation" option.

Appliance Licensing1. Once you receive your appliance, enter the serial number of the appliance in the "WLM Hardware Devices" option on the

license generation page https://www.juniper.net/lcrs/wlmSelectAuthCodeLicenseType.do.You can now access the license information, serial number and license keys, for all licenses that shipped with the appliance.

2. Once you have the license keys, you can perform either an online or offline activation. To activate licenses offline, go to https://www.juniper.net/lcrs/wlmSelectAuthCodeLicenseType.do and follow the "Offline Activation" instructions.

3. Additional licenses, ordered for additional capacity, are considered software licenses and must be activated using the software licensing procedure.

License TypesPlease consult with your sales representative about RingMaster license types. Ringmaster has several licensing levels (SKU):

Informational Note: For Base licenses (WLM-RMTS and WLM-SP-GA-BASE, WLM-RMTS-GLOBAL) the serial number is sufficient to generate a key, an AuthCode is not necessary. The e-mail containing base license serial number may not have an authcode to generate the license key. Authcodes are present for only advanced licenses and are required with the serial number of the advanced license to generate the license key.

Informational Note: There are no AuthCodes generated or required for the products that ship with the appliance; eg. WLM-1200-RMTS ships with WLM-RMTS and WLM-RMTS-250. These licenses are included in the BOM, so they do not require any authcodes and are displayed when you enter the serial number of the appliance.

3 Licensing for RingMaster Version 8.0 Copyright © 2015, Juniper Networks, Inc.

https://www.juniper.net/generate_license/

https://www.juniper.net/lcrs/wlmSelectAuthCodeLicenseType.do



d.�Once the license keys have been retrieved the user can perform either an online or offline activation (go to https://www.juniper.net/lcrs/wlmSelectAuthCodeLicenseType.do and follow the “Offline Activation” option)

d.�Once the license keys have been retrieved the user can perform either an online or offline activation (go to https://www.juniper.net/lcrs/wlmSelectAuthCodeLicenseType.do and follow the “Offline Activation” option)


EVAL — Evaluation license is valid for 90 days and enables support for up to 50 APs, unlimited switches, and planning.

WLM-RMTS — RingMaster Tool Suite (RMTS) license enables support for up to 5 WLAs and one WLC.

WLM-RMTS-10 — Enables support for up to 10 additional WLAs. Requires WLM-RMTS.

WLM-RMTS-50 — Enables support for up to 50 additional WLAs.



WLM-RMTS-500 — Enables support for up to 500 additional WLAs

WLM-RMTS-1000 — Enables support for up to 1000 additional WLAs. Available for RM Versions 6.3 and later.

WLM-RMTS-PLAN — Enables RF planning.

WLM-RMTS-AGENT — Enables RM Agent and supports REST-based API. Requires the purchase of WLM-RMTS.

License ViolationsWhen a RingMaster network plan exceeds the limit of WLAs allowed by installed licenses, RingMaster enters a grace period. This grace period lasts for 60 days where RingMaster runs normally with the additional WLCs and/or WLAs. Appropriate licenses should be purchased and installed during this time. If new licenses are not installed to cover the extra management, RingMaster will automatically begin unmanaging WLAs in the network plan until the licensing situation is corrected.

License HelpFor assistance with evaluation licenses, please contact a sales representative. For assistance with purchased licenses, please contact JTAC. When requesting assistance, please have the output of the hostname command ready and have all license serial numbers and keys available. Screenshots of any errors are also appreciated.

Supported Platforms

Microsoft Windows Server 2003 and 2008, Microsoft Windows XP with Service Pack 1 or higher, Microsoft Windows 2000 with Service Pack 4, Microsoft Windows 7, or Microsoft Vista Enterprise.

SUSE Linux 10.2 and Red Hat WS ES5

Apple MacOS Version 10.4.x. with Java 1.5.

VMWare ESXi Version 4.1 with 64-bit Centos OS

Upgrading from RingMaster Version 7.7

You can install the new version of RingMaster on top of the previously installed one. You do not need to uninstall the previous version. However, you should backup your current network plan in case you have upgrade issues. You can use the backup data to restore your network plan.

Informational Note: When upgrading from RingMaster version 7.0 MR3 (7.0.6.7.0) to RingMaster version 8.0, please upgrade to 7.3 MR2 before upgrading to RingMaster 7.6. The upgrade path is 7.0 MR3 --> 7.0 MR5--> 7.1 MR3 --7.3 MR2 -->7.5 MR1 --> 7.6 MR1 --> 7.7-->8.0.

Informational Note: Before upgrading to RingMaster Version 8.0, please read the Known Issues for RingMaster on page 6

4 Supported Platforms Copyright © 2015, Juniper Networks, Inc.


Upgrading to MSS Version 8.0 In addition to upgrading to RingMaster Version 8.0, you should be aware of the following issues with upgrading to Mobility System Software (MSS) Version 8.0 as well:

Downgrading to a Previous RingMaster Version

If you need to downgrade from a RingMaster 8.0.x version to a previous 7.x.x version, use the following procedure:

1. Uninstall the current RingMaster installation. Select to delete all but the license and the network plans.

2. Install the earlier Ringmaster software version.

3. After installation, use the Restore feature using the backup data you created before upgrading to the next version.

When you start the downgrade version of RingMaster, it opens the Default network plan.

If you need to downgrade the WLCs managed by RingMaster, you can do so before or after the RingMaster downgrade.

JRE 1.6 and RingMaster Java Web Start ClientIf you are using Java Runtime Environment (JRE) 1.6.0_12 when trying to remotely connect to a server with RingMaster software you might experience issues with Java WebStart client failing to start due to the following Java bug:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6808031

This issue potentially affects remote clients on all operating systems with JRE 1.6.0_12 or higher. When starting the Java WebStart client from the desktop icon, an error message is displayed: “Unable to start application” and a set of Java exceptions are thrown.

Customers that encounter this issue must downgrade the Java environment by uninstalling the JRE 1.6.0_12 and creating a fresh install of JRE 1.6.0_11.

If you do not want to downgrade your JRE installation, you can click on the RM Client icon on the RingMaster server page to launch the client.

Informational Note: This release of MSS software no longer supports older MXR-2, MX-8, and MX-8R WLAN controller platforms that were initially built with 32MB of flash. Newer models support 128MB or 256MB. The best method for determining if your controller can support MSS 8.0 is by checking the revision label on the unit:Models MX-8 and MX-8R controller - Revision "P" and aboveModel MXR-2 controller - Revision "N" and aboveAll Juniper-branded equivalents will support MSS 8.0.The following MPs are no longer supported in this version of MSS:MP-71MP-371MP-372 (all models)

Informational Note: Juniper Networks recommends that you do not downgrade to previous RingMaster versions. Database files saved in RingMaster Version 7.0 or higher are converted to the newer version and are not compatible with earlier RingMaster Versions. In addition, MSS features that are new in MSS Version 7.6 are not supported in previous versions of RingMaster. You may also lose Monitoring data and plans may not convert fully to the previous version.

5 Downgrading to a Previous RingMaster Version Copyright © 2015, Juniper Networks, Inc.

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6808031


Known Issues for RingMaster

On a Windows platform, after configuring RingMaster to use more 1408 MB of server memory, RingMaster Services do not start on the platform. [PR833119]

Description — In order to improve RingMaster performance, you can configure different server memory settings on the Windows platform. RingMaster accepts both 2048 MB and 3072 MB as memory settings. However, after you configure the larger settings, RingMaster Services do not start.

Workaround — Configure the Windows platform to use 1408 MB of server memory.

If you have more than 128 WLAs in your network plan, and you attempt to display Client Devices in RingMaster, the incorrect number of WLAs is displayed. [PR812939]

Description — If you have a large network plan, and you click Clients and then Client Devices, the numbers in the Device Types by Time pane are incorrectly displayed as zero or no numbers at all.

Workaround — No workaround at this time.

The RingMaster Client does not launch when you click Launch Client in the interface. [PR811825]

Description — When you go the RingMaster Services Web page, and click Launch Client under Java Web Start Client, the RM Client does not start.

Workaround — Clear the Web browser cache and relaunch the RingMaster Client.

Attempting to generate a Top Client Devices Report for a large network times out on the RingMaster server. [PR811805]

Description — Generating a Top Client Devices report causes the report generation to time out after three hours.

Workaround — No workaround at this time.

You cannot connect more than 15 clients to a RingMaster server. [PR802273]

Description — If you attempt to connect more than 15 RingMaster clients to a RingMaster server, RingMaster returns the error message that it cannot accept additional client connections. Previously connected RingMaster clients are disconnected to allow the additional clients to connect to the RingMaster server.

Workaround — Connect no more than 15 RingMaster clients to a RingMaster server at any time.

The list of selectable Device Types and Device Groups under Clients >Client Devices does not update correctly after it is edited. [PR794540]

Description — If you add a device profile or device group to RingMaster, the list of Device Types or Groups is not automatically updated even after using the Refresh button.

Workaround — You must close the Client Devices tab and open it again to see the changes.

If you remove device types from the Allowed Devices table, the device type does not appear in the table but it still configured in RingMaster. [PR794531]

Description — After configuring a service profile with allowed device types, and the device type is removed from the table, the device is removed but the Clear button is still enabled. If you attempt to undo local changes, the finger print is not removed.

Workaround — None at this time.

Using the RingMaster Java client to connect to a remote server fails to complete the connection process. [PR791864]

Description — If you have upgraded your Java runtime environment to Java 7, the RingMaster client cannot complete the connection to a remote server when the remote server is on a different Java version.

Workaround — Be sure that the Java runtime environment is version 1.6 on the client and server platform. Other versions are not supported by RingMaster in this release.

Adding a wireless client to the Watched Client list may take up to 30 minutes to complete the process. [PR777425]

6 Known Issues for RingMaster Copyright © 2015, Juniper Networks, Inc.


Description — If the RingMaster monitoring database is very large, it may take 20-30 minutes to update with the additional watched clients.

Workaround — Limit the number of watched clients to five wireless clients.

Canceling report generation causes an exception in the RingMaster software. [PR768755]

Description — After upgrading from RingMaster Version 7.6, and you cancel a report while it is generating, RingMaster responds with an exception in the software.

Workaround — First, stop the RingMaster services on the server. Second, navigate to Program Files/JuniperNetworks/RingMaster/conf folder. Locate the report-settings.xml file, and delete it. Lastly, restart the RingMaster Services on the server.

If you encounter this problem on a WLM1200-RM appliance, use SSH to access the appliance and stop the RingMaster Services by using the command rm-services stop. Navigate to the appliance file system using WinScp and locate the report-settings.xml file in the var/ringmaster/conf folder. Delete it from the file system, and restart the RingMaster Services on the appliance.

If you configure a VLAN pool and assign it to a policy on a WLC, the VLAN pool is not applied. [PR742130]

Description — When you configure an Open Service Profile and add a VLAN pool to it, the VLAN pool is not added to the Service Profile.

Workaround — You must reapply the changes to the WLC to add the VLAN pool to the service profile.

Deleting a report generated in RingMaster does not remove it from the hard drive. [PR705488]

Description - After generating a report in .xls format, you cannot delete it from the hard drive even though the report is deleted in RingMaster.

Workaround - You can stop RingMaster Services, delete the file, and then restart RingMaster Services. The report file is located at C:\Program Files\Juniper Networks\RingMaster\report-contents\Default.

When reporting internal application errors from RingMaster, the Problem Report is sent to the wrong e-mail address. [PR703590]

Workaround - To submit Problem Reports, click Report Problem and enter the appropriate information. Instead of sending it via e-mail, click Save, and attach the report to the JTAC support ticket. The problem report is saved to C:\Documents and Settings\username\.RingMaster\bugs\.

Enabling Spectral Mode on a WLA in a Mesh configuration interrupts the services on the WLA. [PR693425]

Description - When a WLA is part of a Mesh configuration, you can enable Spectral mode on it. This causes the radios to go out of service and disrupts the Mesh Services.

Workaround - Best practices indicate that you should not enable Spectral Mode on a WLA configured for Mesh Services. A warning message is now displayed in RingMaster when you attempt to enable Spectral Mode on a Mesh WLA.

If the computer monitor screen resolution is too low, the Spectrogram feature may not display properly. [PR692826]

Description — The Spectrogram for Spectrum Analysis appears to be too large to display on the monitor screen.

Workaround — Be sure that your monitor screen resolution is set to one of the following values:

1680 x 1050 pixels

1440 x 900 pixels

1280 x 1024 pixels

In some cases, the Events panel does not refresh properly and displays erroneous information. [PR676029]

Description — When selecting an event on the Events panel, the panel appears frozen and does not display the selected event.

Copyright © 2015, Juniper Networks, Inc. Known Issues for RingMaster 7


Workaround — You can perform one of the following options:

1. Re-size the event panel manually.

2. Selecting any task in Alarms or Manage task groups also refreshes the UI.

3. Clicking on the search text box at the top right of the alarms details panel also causes the panel to refresh.

4. Select another event in the Events table and then return to the event that was not displayed.

When importing large network plans into RingMaster, error messages are displayed and the import process does not finish. [PR675226}

Description — The RingMaster Import feature cannot import large network plans for use with the application. The Import feature is designed to import incremental changes to network plans.

Workaround — N/A

When merging large network plans into RingMaster, error messages are displayed and the merge process does not finish. [PR675287]

Description — The RingMaster Import feature cannot merge large network plans for use with the application. The Import feature is designed to merge incremental changes to network plans.

Workaround — N/A

When you make changes to a radio profile and then deploy the changes, RingMaster does not update as expected. [PR652753]

Description — When you click Apply, the Apply button remains active in the interface.

Workaround — Click Apply until the button becomes grey (disabled).

When RingMaster is installed on a Linux platform, and you create a SSID Monitoring report, no data is displayed in the report. [PR658227]

Description — After deploying a new WLC in RingMaster, SSID statistics are not immediately collected.

Workaround — Change the polling to a different interval and save the report. Change the polling interval to the original value and save the report. Restart RingMaster services.

When you make multiple changes to radio profiles using RingMaster, the changes are not deployed as expected. [PR68359]

Description — When you move radio profiles from one WLA to another, you may inadvertently delete the radio profile before it is moved to the second WLA. This causes cluster synchronization to fail on the network.

Workaround — After every step of the change process, deploy the changes to the network. This ensures that the steps are deployed in the correct order.

When using spectrum analysis and a WLC2, the spectrogram may not update properly. [PR658239, PR68333]

Description — The spectrogram in RingMaster may not display any data or update properly if the WLA is configured on a WLC2. The WLC2 cannot process the data fast enough to support the spectrogram display.

Workaround — It is recommended to use a WLA on another model of WLC instead of a WLC2.

When a WLC is configured for the Drop Ship feature but you configure a management port other than the default port, you cannot manage the WLC after uploading it. [PR68109]

Description — The Drop Ship feature is used to preconfigure WLCs for placement in the network, and relies on connectivity to RingMaster to work properly.

Workaround — Leave the Management port at the default setting in order to use the Drop Ship feature.

RingMaster does not display the complete roaming history for client sessions on the network. [PR675384]

Description — When a client roams to or from a WLA, the session details of the client does not display the roaming history but just displays the current location.

8 Known Issues for RingMaster Copyright © 2015, Juniper Networks, Inc.


Workaround — None at this time.

If you add an MP that is unsupported by the current network plan, no warning is displayed and you can place the MP in the coverage area. [PR64987]

Description —If you place an MP in a coverage area that does not support the selected MP radio settings, no warning message is displayed that the radio is not supported. For instance, if you create a plan that enables 5 GHz coverage, and you place an MP that supports only 2.5 GHZ into the plan, no warning is displayed.

Workaround — Be sure to place only the MPs supported by the plan configuration to avoid configuration issues.

RingMaster does not import rotated text on a CAD drawing. [PR64663]

Description — If text is rotated 90 degrees from horizontal, the text does not import with the CAD drawing. This appears to be a limitation with the CAD application and not RingMaster.

Workaround — Select the text layer in the CAD drawing and rotate it so the text appears horizontally on the drawing.

If you configure AirTight to use SNMP v3 traps, the traps are not synchronized with RingMaster because a nonstandard implementation of SNMP is used by AirTight. [PR64814]

Description — The AirTight SNMP engine and the RingMaster SNMP engine are not synchronized, therefore the trap that should be received and decoded is out of the 150 second accepted time frame. As such, it is discarded.

Workaround — Configure AirTight to use SNMP v2 or SNMP v1 instead of SNMP v3.

Enabling AAA access to a WLC using RingMaster and downgrading to 7.0 or earlier causes the authentication process to fail, and RingMaster can no longer access the WLC. [PR62913]

Description— After upgrading to RingMaster 7.1or a newer version, and enabling AAA for access to a WLC, if you downgrade to MSS 7.0 or earlier on the WLC, the WLC reverts to the enable password and RingMaster cannot access the WLC using AAA.

Workaround—Disable the AAA feature in RingMaster before downgrading to an earlier software version. See “Downgrading to a Previous RingMaster Version” on page 5.

MP licensing is not updating based on the number of MPs in the network. [PR61050]

Description — If the serial number of an MP is changed, the change is not reflected in RingMaster and the serial number is deprecated from the license.

Workaround — Restart the RingMaster server to reset the licensing.

Because of a limitation in Windows XP that allows no more than 10 half-open connections, running RingMaster services on Windows XP is not recommended if your network plan contains more than 10 devices. If 10 devices in your network plan were unreachable or not responding, Windows XP would exceed its half-open connection limit, and connection attempts to reachable devices might time out as a result.

Workaround— If your network plan contains more than 10 devices, and you want to run RingMaster services on a Windows system, use a server OS, such as Windows 2000 or Windows 2003, instead of Windows XP.

Linux: The default browser is Firefox, which is not included with SuSE. [PR30491]

Description — On SuSE, the default browser executable is Firefox. However, the Firefox browser is not included with the SuSE distribution; only the Konqueror browser is included. The Konqueror browser is not supported by RingMaster.

Workaround— Install a different browser for accessing RingMaster online help. Preferred browsers for Linux are Firefox, Opera, Mozilla, and Netscape.

A Nessus scan might cause junk entries to be listed in the service configuration file. [PR772057]]

Description — The issue occurs when the Nessus scan generates various username and passwords to perform a security check. Junk characters are added to the service configuration file, which corrupts the file.

Copyright © 2015, Juniper Networks, Inc. Known Issues for RingMaster 9


Workaround— Take a backup of the configuration file before the scan and replace the corrupted file with the backup file after the scan is complete.

Issues Resolved in RingMaster Version 8.0.6.1

The power values are not updated for WLA532, WLA532E, WLA321, and WLA322 in H-Table. Apart from this issue, channels 100-124 and 149-165 are disabled for WLA632. [PR 966276: This issue has been resolved.]

Users are unable to use more than 13dbm tx power for 2.4 Ghz, 5 Ghz (Channels 36-64) and 16 dBm is the maximum for 5 Ghz (Channels 100-140) in WLA522-WW with country code DE in the EU regulatory domain. [PR 966627: This issue has been resolved.]

After upgrading from MSS version 8.0.3.6 to 9.0.2.5, it is observed that the transmit power of WLA522E has been lowered from 14 to 13. Because of this power downgrade, Ekahau does not show accurate results for tracking systems. [PR 972714: This issue has been resolved.]

Unable to input space character in LDAP server properties because RingMaster does not support LDAP based DN with space as a character. [PR 1072302: This issue has been resolved.]

Users are unable to upload a new WLC image in RingMaster. While discovering the WLC in RingMaster, the error message appears: failed to process uploaded data. [PR 1080769: This issue has been resolved.]

The radio state for the remote WLAs are disabled in RingMaster when a configuration change is made in MSS CLI and the network changes are accepted in RingMaster. [PR 1087318: This issue has been resolved.]

Issues Resolved Since RingMaster Version 8.0.5.1

The AAA profile name supports special characters such as #, $, &, ?, ", \, ', <, and >. [PR 1058440: This issue has been resolved.]

Maximum output power calculations and maximum transmit power for WLA522E-WW_ANT5007-OUT and WLA522E-IL_ANT7360A-OUT does not match the values mentioned in the product specification. [PR 1058450: This issue has been resolved.]

A blank rogue summary report is generated if you select scope type of the report as Site, Network Plan, or Mobility-domain. [PR1058559: This issue has been resolved.]


Clients connected to an SSID that contains the & character in the SSID name are not displayed correctly. [PR878103: This issue has been resolved.]

Changes to RingMaster could not be deployed because of the verification error "The pre-shared key is invalid". [PR886138: This issue has been resolved.]

Auto-APs do not accept assigned WLA numbers during the auto-AP conversion. [PR896683: This issue has been resolved.]

Java throws NullPointerException java.lang.NullPointerException on com.trapeze.appl.rm.server.fault.FaultDB.b. [PR899095: This issue has been resolved.]

There were no software updates for RingMaster 8.0 in the MR5 release. Therefore, no separate RingMaster 8.0 MR5 release is announced.

10 Issues Resolved in RingMaster Version 8.0.6.1 Copyright © 2015, Juniper Networks, Inc.


The up-time detail chart shows an incorrect up-time that exceeds 100% up-time, which is the maximum up-time. [PR923158: This issue has been resolved.]

RingMaster version 8.0.3.4 does not support the country code MO on WLA632-WW. [PR929466: This issue has been resolved.]

RingMaster version 8.0.3.4 does not display data for 149 through 165 range on the 5-GHz channel. [PR929512: This issue has been resolved.]

If a user enters incorrect credentials during RADIUS authentication, RingMaster automatically tries to connect to the RADIUS server by using the same credentials more than once until the retry count reaches zero. Because of this, the user account gets locked. [PR955637: This issue has been resolved.]

RingMaster services fail to restart when the configuration database is corrupted. [PR959536: This issue has been resolved.]

The SSID Summary Report shows incorrect count for active WLAs. [PR988336: This issue has been resolved.]


Session data from a secondary seed in a cluster configuration was not reported. [PR863795: This issue has been resolved.]

RingMaster used incorrect characters when generating the Audit Trail report. [PR859097: This issue has been resolved.]

Additional alarms were sent if only Severity Major Alarms was selected. [PR851983: This issue has been resolved.]

Certain reports did not generate correctly after upgrading to RingMaster Version 8.0.2.2 from an earlier version. [PR843857: This issue has been resolved.]

Error messages were generated after upgrading to RingMaster Version 8.0.2.2. [PR843597: This issue has been resolved.]

Users with “Monitor Only” privileges were able to reboot WLAs using RingMaster. [PR830390: This issue has been resolved.]

When using the Custom Shape tool to create an RF Zone, RingMaster became unresponsive. [PR829465: This issue has been resolved.]

RingMaster deployed unsupported characters in MSS. [PR827841: This issue has been resolved.]

When using the copy and paste feature to move WLAs in a network plan, the WLAs were removed from the network plan. [PR813397: This issue has been resolved.]

If you configured a VLAN profile with the same name on multiple WLCs in the same plan, changes to the profile are perpetuated across the WLCs. [PR809460: This issue has been resolved.]

High Utilization Alarms were incorrectly reported. [PR778035: This issue has been resolved.]

RingMaster incorrectly displayed radio channel values and you could not sort by channels. [PR734805: This issue has been resolved.]

You could not delete RM Reports from the hard drive without stopping RingMaster services on the platform. [PR705488: This issue has been resolved.]


Port information was missing from a WLC configuration after deleting the WLC and then uploading it again into RingMaster. [PR745638: This issue has been resolved.]

Copyright © 2015, Juniper Networks, Inc. Issues Resolved Since RingMaster Version 8.0.2.2 11


The “Top 5 and Bottom 5 Access Points in terms of Client Count” was missing from the “Client Load by AP” report. [PR750013: This issue has been resolved.]

Alarm information sent by e-mail changed in RM version 7.6 was less specific than in previous releases. [PR775582]

When the country code for a WLA532 was set to France, you were unable to configure the transmit power using RingMaster. [PR780271: This issue has been resolved.]

The report for Top Client Devices did not contain information when generated for a particular scope. [PR790936: This issue has been resolved.]

When using RingMaster planning and selecting 802.11n, only the WLA532 model was displayed. [PR792607: This issue has been resolved.]

You could not select the entire network plan when using the Monitoring feature. [PR807315: This issue has been resolved.]

RingMaster erroneously allowed the configuration of a neighbor list on a cluster member. [PR818500: This issue has been resolved.]

RingMaster did not display the correct number of BSSIDs for a RF neighborhood. [PR826677: This issue has been resolved.]

After installing RingMaster 8.0, the Top WLA Report did not generate and display results. [PR828628: This issue has been resolved.]

Open Issues with WLM1200-UMSP

The Device Fingerprinting feature for SmartPass 8.0 is not available on the WLM1200-UMSP. [PR790991: This issue has been resolved.]

After upgrading the Location Appliance image from version 7.6 to version 7.7, the software images displays the upgraded version as 7.6 instead of 7.7. [PR753769: This issue has been resolved.]

Documentation Improvements

The RingMaster Quick Start Guide now includes a procedure for adding a single WLC to RingMaster.

The RingMaster Configuration Guide now includes a “You are Here” orientation for each section. This will assist with understanding where, in the interface, you are configuring certain features.

KB article 24512 addressing RADIUS configuration in RingMaster is now included in the RingMaster Configuration Guide.

The ability to manually configure a channel on a radio was changed in this version. To manually configure a channel, select the radio and then clear the Auto Channel checkbox. [PR831698]

Submitting Problem Reports

RingMaster can send problem reports to the Juniper Networks TAC (JTAC) team directly when it encounters a problem. You can also send a problem report at any time by selecting Help > Report Problem in RingMaster.

If a problem occurs, the Internal Application Error dialog box appears.

To submit a problem report:

1. Do one of the following:

− In the Internal Application Error dialog box, click Report Problem.

− Select Help > Report Problem.

12 Open Issues with WLM1200-UMSP Copyright © 2015, Juniper Networks, Inc.


The Report Problem to Juniper Networks dialog box appears.

2. Fill out the information in the dialog box.

Provide your name, and enter as much detail as possible about the task you were performing when the problem occurred. You must provide the name of your company. The information goes to [email protected].

3. Click Send Now.

4. If network access for the email report is not available from the RingMaster host, click Save to store the problem report on the RingMaster host.

The problem report is saved as a directory with a name containing the timestamp of the problem report (for example, Thu-Aug-19-13-04-11-PDT-2004). This directory is located in C:\Documents and Settings\user_home_directory\Juniper\.RingMaster\bugs, where user_home_directory is the home directory of the user that is running RingMaster at the time the problem report is generated.

To send the problem report to Juniper Networks, create a zip archive of the problem report directory and send the archive as an attachment to [email protected].

Copyright © 2015, Juniper Networks, Inc. Submitting Problem Reports 13

mailto:[email protected]

mailto:[email protected]