Network monitoring system requirements
Requirements to use the Network Collector to monitor your network depend on several variables, such as the volume of data to display in the browser.
This topic contains:
SolarWinds Observability SaaS general requirements
The following table lists browser requirements and recommendations for using the SolarWinds Observability SaaS web application.
Performance of the computer and internet speed where you open the browser significantly influences the speed of SolarWinds Observability SaaS.
| Software Requirements | |
|---|---|
| Web browsers |
SolarWinds Observability SaaS supports the two most recent versions of the following web browsers:
|
| Browser requirements |
The following must be enabled in your browser:
|
Firewall or access control requirements
The browser you are using to access SolarWinds Observability SaaS's basic features must have unrestricted access to the following locations:
- https://my.xx-yy.cloud.solarwinds.com and all subfolders (where
xx-yyis determined by the URL you use to access SolarWinds Observability SaaS, described in Data centers and endpoint URIs) - https://documentation.solarwinds.com/ and all subfolders
- https://agent-binaries.cloud.solarwinds.com/ and all subfolders
The clients and agents installed when monitoring network devices must be able to communicate with the SolarWinds Observability collector to report collected data.
Open your firewall or access control configuration to permit TCP/HTTPS/TLS outbound connections to the following endpoints (where xx-yy is determined by the URL you use to access SolarWinds Observability SaaS, described in Data centers and endpoint URIs) using port 443:
uams.xx-yy.cloud.solarwinds.comotel.collector.xx-yy.cloud.solarwinds.comagent-binaries.cloud.solarwinds.com
If you are using Platform Connect to get SolarWinds Observability Self-Hosted data to SolarWinds Observability SaaS, open the following URLs in your firewall:
*.amazontrust.com:80*.ss2.us:80
These endpoints are used for online certificate status validation. See Online Certificate Status Protocol for details.
Review the following port requirements. See also port requirements for other areas of SolarWinds Observability SaaS and for on-prem devices in SolarWinds Platform Self-Hosted requirements.
| Default port | Protocol | Direction | Description |
|---|---|---|---|
| 161 | UDP, TCP | Outbound | Port used by the Network Collector for sending and receiving SNMP data from network devices. |
| 443 | HTTPS | Outbound | Port used for communication with cloud endpoints. See also Endpoints and Public IP addresses used by SolarWinds Observability SaaS per data center. |
| 443 | TCP | Inbound | Optional: Port used by the Network Collector Web Console. Required only for remote access to the website. |
| 1433 | TCP | Outbound | Optional: Port used for communication between the Network Collector and the SQL Server. Required only if the SQL server is deployed on a stand-alone machine, such as in High Availability scenarios. See Configure deployed Network Collector for High Availability installation. |
| 2055 | UDP | Inbound | Port for receiving flows on the Network Collector. See NetFlow port requirements. |
| 17777, 17778 | TCP | Inbound | Special case: If the Network Collector and SolarWinds Observability Agent are installed on different servers, inbound rules for these ports are needed. |
Network Collector requirements
You can only install the Network Collector on a server with a supported Windows version.
See Review Network Collector requirements and scalability information.
By default, the Network Collector installer also deploys the SQL Server Express database.
| Requirement type | Network Collector requirement |
|---|---|
| Operating system |
|
| CPU |
Minimum: 4 CPU cores Recommended: 8 CPU cores |
| Memory |
Minimum: 16 GB RAM Recommended: 32 GB RAM |
| Storage | 40 GB |
| Network Latency |
The latency (RTT) between the Network Collector and the database server should be below 200 ms. Degradation may begin around 100 ms, depending on your utilization and the size of your deployment. In general, higher latency will impact larger deployments more than smaller deployments. Ping the database server to find the current latency and ensure a reliable static connection between the server and the regions. |
| Other software |
.NET Framework 4.8 - You can download the installer (online or offline) from Download .NET Framework 4.8. SQL Server Express - Installed automatically with the Network Collector deployment. If you deploy SQL Server Express on a virtual machine, the VM must also meet SQL Server system requirements. For example, if SQL Server requires a sector size of 512 or 4,096 bytes, the Azure VM must not have a sector size of 8,192 bytes. For details, see this Microsoft article. |