Understanding on SNMP Traps, Syslogs, and Squid Proxy Inbound IP Addresses

The inbound IP address for services such as SNMP traps, Syslogs, and the Squid proxy depends on the deployment architecture of the Nextgen Gateway and the underlying infrastructure setup:

1. OpsRamp-Provided ISO/OVA Deployments

• Single-node cluster (default setup):
  • All inbound traffic for SNMP traps, Syslogs, and the Squid proxy listens directly on the node’s IP address.
• Multi-node cluster:
  • A dedicated load balancer IP address is automatically allocated:
    • One shared IP for SNMP traps and Syslogs
    • A separate IP for the Squid proxy

This ensures traffic is properly routed to the respective services across the cluster.

2. Custom or Bring-Your-Own Kubernetes (BYOK) Clusters

If you are using your own Kubernetes cluster instead of the OpsRamp-provided ISO/OVA:

• The inbound IP allocation depends entirely on how you’ve configured the Kubernetes Services, particularly:
  • Whether you’re using LoadBalancer, NodePort, or Ingress resources.
  • How your external load balancer (e.g., MetalLB, cloud-native LB) is set up to route traffic.
    

3. Managed Kubernetes Clusters (e.g., EKS, AKS, GKE)

In managed Kubernetes environments:

• The Service type LoadBalancer is typically used for SNMP, Syslogs, and Squid proxy services
• IP addresses are automatically provisioned by the cloud provider’s load balancer infrastructure
• The actual public or private IP address depends on:
  • The Kubernetes Service configuration
  • The networking mode (e.g., VPC-native, public vs private subnet)
  • Any internal or external LoadBalancerClass defined in your cloud setup

⚠️ It is essential to ensure firewall and security group rules allow ingress on the expected ports for SNMP Traps (usually UDP 162), Syslogs (UDP/TCP 514), and Squid (default HTTP 3128) depending on your use case.

Understanding on Outbound Traffic from the NextGen Gateway

Outbound traffic from the Nextgen Gateway refers to all communication initiated by the gateway toward customer-managed infrastructure and devices. This includes - but is not limited to:

• Discovery of network devices, servers, and applications
• Monitoring data collection (e.g., SNMP polling, WMI queries, API calls, etc.)
• Performance metric collection and status polling

Essentially, this is how the gateway reaches out to pull data from customer-managed assets.

IP Behavior in Multi-Node Cluster

In a multi-node Kubernetes cluster, the gateway pod (which performs discovery and monitoring) is scheduled dynamically across available nodes. This has direct implications for outbound traffic:

• Outbound traffic from the gateway will originate from the node’s IP where the gateway pod is currently running.
• In case of:
  • Pod restart
  • Node failure
  • Cluster rescheduling

The gateway pod may move to a different node, changing the source IP for outbound connections.

OpsRamp Recommendation

To ensure uninterrupted data collection and monitoring:
OpsRamp strongly recommends whitelisting all node IP addresses in the Kubernetes cluster within the customer’s:

• Perimeter firewall
• Internal firewalls (if any)
• End device access control lists (ACLs), security groups, etc.

This ensures that regardless of where the gateway pod is scheduled, it can consistently initiate outbound connections to customer infrastructure without being blocked.

Additional Considerations

• In cloud-based or managed Kubernetes clusters, source IP behavior may depend on:
  • Network plugins (e.g., Calico, Cilium, AWS VPC CNI)
  • Whether NAT gateways, egress proxies, or egress load balancers are in use
• If outbound NAT or proxying is in place, you may need to:
  • Whitelist the egress IP or NAT gateway IP instead of each node
  • Ensure source IP preservation if devices enforce strict ACLs
• For environments with network segmentation or zero trust, ensure:
  • Routing and firewall rules allow each node to access the required device subnets and ports
  • DNS resolution is functional from all nodes (if hostname-based targets are used)

Summary

Note

Note