RND Checklist

You can consult the following brief checklist before you start using RUCKUS Network Director. The objective of the checklist is to help you to review your settings and configurations before using RND and prevent encountering unexpected system behavior.
  • Network latency between nodes: RND supports two-node clusters. When the nodes are deployed in different areas, you want to make sure to have an environment with low network latency. It is recommended that you keep the network latency between the nodes less than 60 ms.
  • Before you deploy RND on your network, you must add the following ports to your user environment and keep them open at all times. The RND uses the following ports to communicate with itself, the Cluster, the SZ, and the APs:
    • Ports for RND communication with APs and SZ: 443, 7443, 8443
    • Ports for RND communication by itself for AP onboarding and forwarding: 443, 445, 8444, 3000
    • Ports for RND cluster communication between nodes (for installation, database synchronization and health checks): 22, 5432, 9000, 9898 , 9999
    • Port for RND access license server and register license: 443
    • Ports for RND communication with DNS: Ports 53 or depends on Customer Environment
    • Ports for RND communication with NTP: Ports 123 or depends on Customer Environment
  • Ensure the following configurations and SZ status are part of the AP onboarding preparations:
    • SZ is online. You can check the SZ status on the RND user interface.
    • The APs in the same NAT belong to the same SZ cluster. You cannot redirect APs in the same NAT to different SZ clusters.
    • All registration rules are ready and the AP can be redirected to the appropriate SZ and zone.
  • After AP onboarding:
    • Wait for 15 minutes after AP onboarding to make sure that RND syncs up data from SZ.
    • Make sure that no APs exist in the staging zone. This can be monitored from the GUI.
    • Ensure that there are no unmanaged APs. This can be monitored from the GUI.