Onboarding, Authentication and Authorization for RUCKUS One
The RUCKUS Edge onboarding flow encompasses the steps required to integrate and
configure RUCKUS devices within a network. This process ensures seamless connectivity
and
optimal performance by guiding users through setup, configuration, and validation
stages.
- Setting static IP and gateway on Edge.
- Configuring DNS server on Edge.
- Verifying connectivity.
- Onboarding RUCKUS Edge to RUCKUS One.
- Note:
- Management: RUCKUS Edge can only be managed by RUCKUS One. Configurations from RUCKUS One are stored in persistent memory and survive reboots.
- Default Behavior: Before onboarding RUCKUS One, Edge runs DHCP client on all interfaces. Recommended to keep only one interface UP to use a single DHCP IP for connectivity with RUCKUS One.
- Static IP Option: For deployments requiring static IP, Edge provides basic network CLI commands (IP, subnet mask, gateway, DNS) to enable connectivity to RUCKUS One.
- Temporary Config: CLI-based network settings are not persistent and will be lost after reboot.
- Post-Onboarding: Once Edge connects to RUCKUS One, admin should configure ports via RUCKUS One so that settings are saved in persistent memory.
CLI Command Summary
- Add the RUCKUS Virtual Edge to
RUCKUS
One as per your platform preference:
- RUCKUS One web interface - Refer to Adding a RUCKUS Edge through the Web User Interface for detailed instructions.
- RUCKUS One mobile application - Refer to Adding RUCKUS Edge through the Mobile Application for detailed instructions.
- Authorize and authenticate the RUCKUS Virtual Edge device using a one-time password - Refer to Authenticating the RUCKUS Virtual Edge Using the OTP for detailed instructions.