Planning for firewall traffic between an MBean dashboard and data grid servers

You can also plan for data grid traffic between an MBean dashboard and data grid servers.

The examples illustrate where you must allow communication between these servers. You should read the port properties and values that are defined in Planning for network ports

Figure 1. Administration traffic consists of traffic from a host running an MBean dashboard. Communication between the dashboard and data grid servers must be allowed through any firewall.

MB1: Only the host that runs the MBean dashboard can initiate traffic.: If a Java Management Extensions (JMX) service port is not configured for a catalog server, it will default to 1099. If a JMX service port is not configured for a container server, a dynamic port is chosen and this port can vary each time the container server is restarted. In this example, the JMX service port is set to 1099. Outbound traffic uses source port: ephemeral, destination port is set to 1099, and return traffic from the data grid server flows over the same connection.

MB2: Only the host that runs the MBean dashboard can initiate traffic.: In this example, a JMX connector port is set to use 32701. Outbound traffic uses source port: ephemeral, destination port: 32701, and return traffic from the data grid server flows over the same connection.

Note:

If Secure Socket Layer (SSL) is not configured, but a JMX connector port is configured, firewall traffic uses the JMX connector port.
If SSL is not configured and a JMX connector port is not configured, firewall traffic uses the JMX service port.
If SSL is configured, but a JMX connector port is not configured, an ephemeral port is chosen. This port can vary each time that the server is restarted. Firewall traffic flows over the ephemeral port.