Network Considerations
The following network topology factors
should be taken into consideration when deploying RUCKUS Network Director in the network
along with High-Scale SZ controllers and APs.
Port and Interface Mapping:
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
All traffic to RND systems is over HTTPS. The HTTP requests will be redirected to HTTPS with port 8443.
Firewall Ports
| From | To | Port# |
|---|---|---|
| AP | RND | HTTPS 443 |
| RND | SZ | HTTPS 443, HTTPS 8443, and HTTPS 7443 |
| User Browsers | RND | HTTPS 8443 |
| AP | SZ | HTTPS 443 |
| RND (AP onboarding and forwarding) | RND (AP onboarding and forwarding) | 433, 445, 8444, 3000 |
| RND (for installation, DB connection and health check) | RND (for installation, DB connection and health check) | 22, 5432, 9000, 9898, 9999 |
| RND | License Server | HTTPS 443 |
| RND | DNS | Port 53 or depends on Customer Environment |
| RND | NTP | Port 123 or depends on Customer Environment |