URLs to be Allowed in Firewall for RUCKUS AI (formerly known as RUCKUS Analytics)

vasanth_edward — Wed, 21 Feb 2024 08:36:52 GMT

To ensure proper communication between the vSZ/SZ, APs and switches with RUCKUS AI, customers must allow port 443 and some URLs in their Firewall.

Customer Environment

Any SZ with RUCKUS AI where SZ is behind a firewall and inbound/outbound traffic needs to be allowed for successful communication between SmartZone and RUCKUS AI

Symptoms

SZ is not onboarding/communicating in RA.

Resolution

The endpoints for RA are as follows:

For firewall ports, only outbound 443 needs to be opened from the SZ.

For US

https://ruckus.cloud (34.102.183.44) is used for the administration portal of Ruckus Cloud.

https://messagehub.analytics.ruckus.cloud (34.69.139.151) is used by the SZ to send analytics data to the cloud.

https://serviceloc.ruckuswireless.com (23.236.63.97) is used by the SZ to determine the correct endpoints to connect to. No analytical data will flow to this endpoint but connectivity is required for service discovery.

For EU

https://eu.ruckus.cloud (34.107.197.242) is used for the administration portal of Ruckus Cloud.

https://messagehub.analytics.eu.ruckus.cloud (34.89.193.24) is used by the SZ to send analytics data to the cloud.

For ASIA

https://asia.ruckus.cloud (35.190.34.117) is used for the administration portal of Ruckus Cloud.

https://messagehub.analytics.asia.ruckus.cloud (34.96.208.196) is used by the SZ to send analytics data to the cloud.

The above-mentioned IP addresses are subjected to change in future, please use FQDN wherever possible.

If an IP address will change, we will update this content.

topic URLs to be Allowed in Firewall for RUCKUS AI (formerly known as RUCKUS Analytics) in RUCKUS Self-Help

URLs to be Allowed in Firewall for RUCKUS AI (formerly known as RUCKUS Analytics)