Port Information for Firewalls

Basic Access for ExtremeCloud Services

This is required for ExtremeCloud applications to run properly on ExtremeCloud Edge RDC.

Access

Note

Rancher connection is required for day-to-day service operation. (It creates a tunnel to Kubernetes cluster for CloudOps remote access/management.)

For NAT deployments where you deploy your cluster with private addressing, you must provide the CloudOps team with direct admin access to the cluster nodes in your internal network. Use the mappings in the following table to map inbound ports on the public side of the NAT router to specific cluster nodes and ports in your private network.

Note

Make sure to let the CloudOps team know which IP address you are using for inbound connections. As a best practice, use the first public IP address, although you can use another address, including a public IP address that is dedicated to this connection type.

Note

For SSH or UCP Remote access, inbound access is needed only on-demand for the initial deployment, software upgrade, or issue troubleshooting. For <rdc>-inlets, inbound access is needed on an ongoing basis.

Access for Production Sanity Verification

The Extreme QA team will run production santify verification after the release upgrade to make sure all of the services are still working properly. The following table shows the connection info they'll use, including the public-facing IPs from which they'll connect (column 1) and the destination ports mappings to access the cluster (column 5).