New in This Document

Use the New In This Document topic in the following situations:

  • You are republishing an existing RUCKUS document for a new or updated release.
  • You are adding, updating, or deleting features in existing RUCKUS documents.
  • You are adding, updating, or deleting commands to a command reference document.
  • The New in This Document topic should not be used as a Document History table.
  • The New In This Document topic should not be used for Command Reference Guides.
  • If there are no changes in the document, there should be no indication in the table to the effect that “No changes or updates were made to the guide.” Nor should the table show “None” in the rows. Doing so leaves the reader to wonder why the document was rereleased if there were no changes to it. You want to also avoid leaving the table cells blank.
  • For complete New In This Document guidelines see https://commscope.sharepoint.com/:b:/r/sites/ARR_CSS/TechPubs/SDL/Documents/new-in-this-document-guidelines-v1.0.pdf

The New in This Document section normally appears in the About This Document chapter.

The Key Features and Enhancements table is the main feature of the New in This Document section.

The table title includes the release number (and version number if warranted) and the publication date of the document, as shown in the following example.

  • Feature Column

    The Feature column shows the name of each new, updated, or deleted feature in a separate row.

  • Description Column

    The Description column shows a brief description of the new, updated, or deleted feature.

    The Description need not be too lengthy. Begin each description with the notation New, Updated, or Deleted before including a description of the feature or change.

    Note: Keep in mind that the descriptions are likely to be used in the release notes too.

  • Reference Column

    The Reference column shows a cross-reference (live link whenever possible) to the appropriate section in the document.

Key Features and Enhancements in RUCKUS Network Director 4.5.0.65

Feature Description Reference

TACACS+ Configuration Workflow Improvement

The TACACS+ configuration workflow has been enhanced to include the Enable TACACS+ option while adding a TACACS+ server, allowing administrators to enable or disable authentication without editing the server after it is added.

Configuring TACACS+ Settings
Bidirectional Synchronization of Default Cluster Settings

Provided bidirectional synchronization between cluster-level and system-level Default Cluster settings. Enabling or disabling the default cluster in either location now automatically updates the other setting, ensuring a consistent UI state and correct AP onboarding behavior.

Adding a Cluster and Managing System Settings
Updated RUCKUS Networks Branding New: RUCKUS Network Director now displays the updated RUCKUS Networks logo to align with corporate branding standards. Throughout the Guide

Key Features and Enhancements in RUCKUS Network Director 4.5.0.32

Feature Description Reference
SNMPv3 support for RND New: RUCKUS Network Director offers support for SNMP version 3, providing significant security enhancements critical for sensitive operations. It supports authentication (using MD5 or SHA) and encryption (using DES or AES) to ensure data integrity and confidentiality. SNMP Support for RND
Geo Redundancy New: RUCKUS Network Director (RND) supports Geo Redundancy that enhances network resilience by enabling operational clusters to synchronize with geo-redundant clusters in geographically separated data centers. This capability ensures that if the operational (primary) data center experiences a failure, the cluster in the geo-redundant (secondary) data center can seamlessly take over. Geo Redundancy

Key Features and Enhancements in RUCKUS Network Director 4.5.0.30

Feature Description Reference
TACACS+ authentication Updated: Enhanced TACACS+ authentication support by adding the Default Role Mapping option, which enables automatic role assignment for TACACS+ users. When this feature is disabled, TACACS+ users must be manually mapped to the RND local database with matching TACACS+ attributes. When enabled, TACACS+ users are automatically assigned a default local admin role in RND. Configuring TACACS+ Settings

Key Features and Enhancements in RUCKUS Network Director 4.5.0.26

Feature Description Reference
TACACS+ authentication New: RND supports Terminal Access Controller Access-Control System Plus (TACACS+) as a secure mechanism for authenticating RND administrators, expanding secure access options. Configuring TACACS+ Settings

Key Features and Enhancements in RUCKUS Network Director 4.5.0.22

Feature Description Reference
Editorial updates and corrections

Updated: Editorial corrections were made throughout the guide.

Throughout the guide

Key Features and Enhancements in RUCKUS Network Director 4.5.0.13

Feature Description Reference
RND Upgrade

Updated: RUCKUS Network Director can be upgraded only using encrypted .pkg (package) file.

Upgrading the RUCKUS Network Director Version

Key Features and Enhancements in RUCKUS Network Director 4.5

Feature Description Reference
SNMP support for RND

New: RUCKUS Network Director offers support for SNMP version 2, providing essential capabilities for network monitoring and management.

SNMP Support for RND.
Default Registration Rule New: Default Registration Rule enhances flexibility in managing APs that do not match any of the other configured registration rules (based on AP serial number, AP model, and IP address range using subnet for AP discovery). This rule ensures that the APs are appropriately managed before being redirected to the default cluster or staging zone. Configuring Default Registration Rules
RND AP diagnostics

The diagnostics capability of RND provides extensive visibility into AP redirection processes in RND, including detailed error messages associated with failed redirection attempts to designated clusters, AP Zones, and AP Groups.

Monitoring AP Details and Diagnostic Information

There must be some indication of what has been updated in the released document because there must be some form of change that requires the republication of the document. For documents in which there are no new features or only minor changes, some mention of updates to the guide should be included in the table. For example, some forms of general updates could be listed in the following ways:

  • Editorial updates and corrections
  • Addressing reported defects
  • Unsupported software
  • Unsupported hardware
  • Unsupported feature

The reference to these types of changes could be “Throughout the guide” or “References have been removed throughout the guide.” The goal is to indicate that the change or deletion has occurred throughout the document.