Workflow

During the discovery process and AP onboarding, RUCKUS Network Director maintains different stages of communication between the AP, RND, and SZ.
  1. The customer's provisioning system configures the RND through the RUCKUS Network Director Admin portal or by using APIs. RND can preconfigure the APs into a cluster. APs can be mapped to the SZ cluster and zone in RND based on the AP serial number, AP model, IP address range using the subnet, or a combination of IP/subnet mask and one or more AP models for AP discovery.
  2. The regional DHCP server provides the RND address to the AP.
  3. The AP connects to RND and sends a discovery request. RND preprovisions the AP record on the SZ cluster and zone through the SZ management interface.
  4. The AP sends the discovery request again to RND. After RND recognizes the SZ to which the AP is assigned, RND streams the AP request to the SZ cluster without unpacking the network packets. RND proxies AP discovery to the vSZ control interface so that the AP has the correct key when it joins the vSZ. The AP receives the SSH certificate and control plane IP list from SZ.

    RND proxies the SZv4 or SZv6 IP address or addresses to connect an AP or a group of APs to the SZ cluster based on the following criteria:

    • If an AP connects with an IPv4 address, RND proxies AP discovery to the vSZ control interface IPv4 and the AP gets the correct key to join the vSZ.
    • If an AP connects with an IPv4 address and IPv6 Link-Local address, RND proxies AP discovery to the vSZ control interface IPv4 and the AP gets the correct key to join the vSZ.
    • If an AP connects with an IPv4, IPv6 Link-Local address, and DHCPv6-assigned IPv6 address, RND proxies AP discovery to the vSZ control interface IPv6 and AP gets the correct key to join the vSZ.
    • If an AP connects only with an IPv6 address, RND proxies AP discovery to the vSZ control interface IPv6 and AP gets the correct key to join the vSZ.
    • In a dual-stack zone, if an AP connects with an IPv6 address and the SZ zone is configured with IPv6, RND proxies AP discovery to the vSZ control interface IPv6 and the AP gets the correct key to join the vSZ. If the SZ zone is not configured with IPv6, RND checks SZ for IPv4 registration rules and proxies AP discovery to the vSZ control interface IPv4 so that the AP can join the vSZ. If the SZ zone does not have IPv6 or IPv4 registration rules, RND moves the AP to the configured RND default cluster.

  5. The AP performs a certificate exchange with SZ and proceeds to register with SZ using one of the control plane IP addresses provided by SZ.

In this section:

  1. AP Onboarding Deployment Scenarios and System Behavior
    Different deployment scenarios affect system behavior during AP onboarding.
  2. RND Supports VMware vSphere vMotion
    4.0 supports vSphere vMotion for managing virtual machines on vSphere. You can migrate between vSphere servers without making the service offline. Before migrating, make sure that the original vSphere and target vSphere servers are of the same version.
  3. Migrating RUCKUS Network Director Node from VMware vMotion
Parent topic: RUCKUS Network Director Overview