Network Requirements

This section describes the ports that must be open on Classic Gateways. These open ports allow communication between managed resources, the Classic Gateways, and the OpsRamp cloud.

1. Enable Communication (Mandatory)

You must refer to the Whitelisted IP document and ensure all required IPs are enabled to secure and uninterrupted communication between the OpsRamp Classic Gateway and OpsRamp SaaS.

2. Inbound Connectivity

NameDescriptionProtocolPort
Admin Web UIAccess the gateway web-based admin UI for administration.TCP5480
SSHTo access Classic Gateways and agent consoles from OpsRamp cloud.TCP22
Agents(Optional). Accept connections from agents if agents are configured to connect to the cloud using the Classic Gateways embedded squid proxy.TCP3128
SNMPAccept SNMP queries to monitor the Classic Gateway.UDP161
SNMP TrapsSNMP traps from managed devices are received by the Classic Gateway's IP address.UDP162
Syslog messagesSyslog messages from managed devices can be received by the Classic Gateway's IP address.TCP/UDP514

3. Outbound Connectivity

NameDescriptionProtocolPort
vProbeConnect to the OpsRamp cloud platform using the public IP addresses.TCP443
DNSTo resolve address *.api.opsramp.com.TCP53
NTPNetwork time protocol is used for clock synchronization using the public IP addresses.UDP123
To find the NTP server public IPs, login to the gateway Web/Command-line interface and check the Date & Time section.

Server Requirements

This section describes the hardware requirements to monitor the resources as per different capacity categories.

Capacity

Number of Managed ResourcesRequired Rerver Capacity
Up to 25 resources2 CPU cores, 4 GB RAM / 40 GB Disk / 1 NIC
Up to 100 resources4 CPU cores, 8 GB RAM / 40 GB Disk / 1 NIC
Up to 500 resources8 CPU cores, 16 GB RAM / 60 GB Disk / 1 NIC
Greater than 500 resources at a single siteDeploy multiple Gateways