There are a number of connectivity requirements that must be met before you can use WhatsUp Gold 360. These ensure that data can be collected and presented successfully from managed devices and that issues are reported when detected.

To use WhatsUp Gold 360, you must deploy at least one Connector in your network to monitor your application delivery infrastructure. This Connector reports back network metrics to WhatsUp Gold 360. To enable this, you must allow communication from the Connector to WhatsUp Gold 360. This communication requires HTTPS traffic to be sent. Appropriate firewall rules should be present to enable this outbound communication.

Once it is deployed, the Connector is responsible for monitoring and gathering metrics from managed WhatsUp Golds. To enable this, the HTTPS RESTful API is used. This requires HTTPS communication from the Connector to the admin interface (typically on port 443) on WhatsUp Gold. In addition to this, WhatsUp Gold sends syslog messages to the Connector using UDP port 514.

Important: In general, best practice is to configure firewall rules based on the domains listed in the previous table. Some IP addresses are dynamic (particularly the ones marked with double asterisks (**)) so it is best to use the domains in these cases.
The table below outlines all of the communication requirements:
Source Destination Public IP Address Protocol Port
Connector WhatsUp Gold 360 HTTP(s) 443
api-portal.kemp.ax 20.126.170.207 TCP
Connector NTP Pool These IP addresses are region-dependent NTP 123
pool.ntp.org** UDP
Connector WhatsUp Gold HTTP(s) 443
TCP
WhatsUp Gold Connector syslog 514
Connector connect.kemp.ax 20.103.161.175 TCP 443
Connector axfconnector.azurecr.io**

axfconnector.westeurope.data.azurecr.io**

axfconncector.eastus.data.azurecr.io**

20.61.97.161

20.61.97.136

20.62.128.30

TCP 443
Connector data.kemp.ax 20.76.253.12 HTTPS 9200
Connector cdn.kemp.ax 20.76.253.12 HTTPS 443
Connector * git.rancher.io 34.208.213.149

52.36.54.134

TCP 443

* The URLs in the rows with asterisks (*) next to Connector will be removed soon.

** In general, best practice is to configure firewall rules based on the domains listed in the previous table. Some IP addresses are dynamic (particularly the ones marked with double asterisks (**)) so it is best to use the domains in these cases.