RUCKUS WAN Gateway

The RUCKUS WAN Gateway (RWG) is an edge platform for your enterprise network, delivering a comprehensive set of critical services required to deploy a secure zero-trust network architecture. Integration with RUCKUS One web provides a single point of access for RWG monitoring and management.
To provide an overview of a feature and its benefits. May require several Concept topics to keep content in short, manageable, and reusable chunks of content.

The intention of this new template is to outline the information that you will need to collect from SMEs and provide to readers.

NOTE: Feature Configuration / Troubleshooting are *not* part of the Feature Concept template. These templates are likely to be part of seperate task/reference templates (to be developed).

General Notes for Concept Topics:
  • Optional sections are to be used with discretion based on the feature characteristics.

Feature Overview

This section is required. Providing detailed and accurate information in the feature overview is crucial as it helps users understand the functionality, benefits, and usage of the feature. Moreover, it ensures consistency in communication across all platforms, enhancing user experience and product perception.
  • What is the name of the feature? (What do users call the feature? If the feature is referred to by an acronym, what is the acronym expansion? What is the formal name to be used in documentation?)
    Note: Typically, the name is used as part of the section titles, such as the overview title and the configuration section titles.
  • Where does the feature fit within our taxonomy? (What are the taxonomy group and sub-group? This information is important for categorizing the feature documentation and incorporating it into the existing document sets.)
  • What standard or standards govern the feature? (Sometimes needed.)
  • Is the feature a new feature or an enhancement to an existing feature?
  • Does the feature replace another feature?
  • What does the feature do? (General description)
  • How does the feature benefit the user?
  • What set of terms do the writer and reader need to know to understand the feature and its use?
  • How does the feature work? (Detailed description, if needed.)

The RUCKUS WAN Gateway (RWG) is a next-generation IP data and voice revenue-generating network gateway, combining the latest technologies to maximize operator profitability and minimize cost. RWG delivers a comprehensive set of critical Enterprise network services such as DNS, DHCP, routing/BGP, policy, firewall, micro segmentation, application performance-based WAN routing, event triggers, automation, orchestration, and more.

As an administrator, you will be able to perform the following actions using your RUCKUS One web interface:

  • Onboard an RWG device using a valid FQDN or IP address and a valid API key from the RWG platform.
  • View and monitor details pertaining to your RUCKUS One managed RWG device at the device level and at the venue level. RWG device-specific data is polled and updated every 5 minutes and you can refresh the data display to obtain real-time data. If RUCKUS One loses connection with RWG for 15 minutes, visual indicators and notifications keep you apprised of status changes. Likewise, if RWG generates any alarms, they are displayed in the RUCKUS One interface.
    Note: RWG data may be incomplete if there are intermittent connection issues between RUCKUS One and RWG. RUCKUS One will stop collecting the periodic RWG data if the RWG API key expires, the RUCKUS license expires, the host name does not exist, or the SSL certificate is invalid. Data collection resumes when the offending condition is resolved
  • Access the RWG platform dashboard to modify the RWG configuration. If single sign-on (SSO) login is enabled in RUCKUS One, then you will not have to reauthenticate on the RWG platform.
    Note: RWG configuration is outside the scope of this document. For more information, refer to RUCKUS WAN Gateway product documentation available on the RUCKUS Support site.
  • Validate the data as per the data validation guidelines. After the data validation is passed, RWG will call the RWG device API to check for a valid associated RUCKUS license.
  • View a list of RWG devices that are connected to RUCKUS One, per venue. RWG device status dashboard in RUCKUS One.
  • Modify the RWG configuration using an SSO from RUCKUS One.
Note: If the RWG device is in status 4, 5, 6, 7, or 8, the RWG service stops to fetch data from that device until there is a new configuration update from RUCKUS One.

Requirements

  • The RWG device must have a valid RUCKUS license.
  • To associate your RWG devices with your RUCKUS One instance, each RWG device must have a fully qualified domain name (FQDN) or public IP address with a valid certificate that is signed by public certificate authority (CA).
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no requirements, use the following default wording:

This feature has no special hardware or software requirements for feature enablement or usage.

If there are requirements, include the applicable below points (depending on product line):

  • What releases support the feature?
    Note: Typically, this is not documented in the configuration guides; however, we need to know where to include the information.
  • What hardware models support the feature?
  • Does the feature require specific modules?
  • Does the feature run only on certain ports?
  • Does the feature have special memory requirements?
  • In an integrated system, can the feature be managed or configured from another device? What are the related release and system requirements?
  • Does the feature introduce new user requirements?
  • Does the feature introduce physical or location-based requirements?

Considerations

  • This feature has no special considerations or limitations pertaining to feature enablement or usage.
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no considerations, use the following default wording:

This feature has no special considerations or limitations pertaining to feature enablement or usage.

If there are considerations, include the applicable below points (depending on product line).

Note: A separate section on Limitations may sometimes be needed.
  • Does the feature replace an existing feature?
  • Does the feature work only with a certain protocol or with a limited set of protocols?
  • Is the feature meant to be used in combination with another feature or a set of features?
  • Is the feature incompatible with any features?
  • What happens when the feature is enabled?
  • What happens when the feature is disabled?
  • Does enabling/disabling the feature enable/disable another feature?
  • What system behavior changes, if any, does the feature introduce?
  • Are performance issues associated with the feature? How can these be mitigated?

Best Practices

This feature has no special recommendations for feature enablement or usage.

This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no best practices (recommendations), use the following default wording:

This feature has no special recommendations for feature enablement or usage.

If there are considerations, include the applicable below points (depending on product line).

  • Brief list of RUCKUS recommendations on product use to optimize performance.

Prerequisites

Make sure you have a valid RUCKUS branded RWG device to connect to RUCKUS One.
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no prerequisites, use the following default wording:

This feature has no prerequisites to feature enablement or usage.

If there are prerequisites, include the applicable below points (depending on product line).

Note: This section is sometimes part of a general overview and sometimes part of a configuration overview.
  • What are the task prerequisites that the user must ensure are met,for configuration? (For example, must you be running certain protocols, or must you configure other features first?)
Parent topic: RUCKUS WAN Gateway (RWG)