Adding servers on a different network from your base monitor
Published 08 March 2018
You can use SQL Monitor to monitor servers on a different network from your base monitor, for example those hosted on Azure or Amazon EC2.
Certain firewall requirements must be met before you can do this. If you want to monitor clusters, you also need to set up DNS.
Firewall requirements
The SQL Monitor base monitor needs to be able to connect to the following TCP ports on each machine you want to monitor
Port | Target |
---|---|
135 | Remote Procedure Call (RPC) |
445 | Server Message Block (SMB) |
1433 | The TCP port for each SQL Server instance on the machine. 1433 is the default |
Note: Named SQL Server instances use dynamic ports by default, so you need to configure a specific TCP port for each named instance. For more information, see Configure a Server to Listen on a Specific TCP Port
WMI access
Restrictions | Instructions | ||
---|---|---|---|
Dynamic ports | Not applicable for:
| Follow How to configure RPC dynamic port allocation to work with firewalls | |
Static ports |
2. Follow steps in this MSDN article: Setting Up a Fixed Port for WMI 3. Ensure either:
OR
|
Further requirements for machines hosted in the cloud
If you want to monitor machines hosted in the cloud, you need to either:
- set up a VPN connection between the network that hosts the base monitor and the network that hosts the machines you want to monitor
or
set up corresponding inbound rules for the firewall ports listed above, using your cloud provider's management tool
For instructions on how to do this if you're using Azure or Amazon EC2, see the table below.
Azure - classic deployment model |
|
---|---|
Azure - Resource Manager deployment model |
|
Amazon EC2 |
|
DNS (required for monitoring clusters)
If you want to monitor clusters on a different network from your base monitor, you need to set up DNS. This means that on the Add SQL Server screen, when you enter the name of a cluster or node, SQL Monitor can detect all the nodes on the cluster.
If you're only monitoring standalone machines, you don't need to set up DNS. Instead, on the Add SQL Server screen, enter the IP address of the machine you want to monitor.
Latency
If your base monitor is in a different region from your monitored servers (eg if it's in America and you're monitoring servers in Asia), you might experience latency. Depending on the impact of the latency, it might be useful to set up a base monitor in the same region as the servers you're monitoring.
Troubleshooting
Please see the testing data collection methods page to troubleshoot any connectivity problems you may be having.