Sensor, hybrid appliance, or compute node cannot connect to broker

Problem

A sensor, hybrid appliance, or compute node is unable to establish a connection with a broker.

Reason

The following are probable reasons for the problem:

The sensor, hybrid appliance, or broker is unable to communicate with the enrollment service.
The broker IP address is not configured correctly.
The broker IP address does not match the IP address configured for the submission interface or cluster interface on the broker.
Network settings are not configured correctly.
Network deployment is preventing connectivity.
A reason identified in the show mvx node status full command output. For a list of error codes, see CCD Ok in Output fields.

Action

To correct the problem:

Verify that broker information is displayed in the show mvx cluster enrollment status command output. If no broker information is displayed, troubleshoot the enrollment service.
Verify that the broker node IP address is correct. If the IP address is incorrect, troubleshoot the Central Management connection or the enrollment service.
If the sensor or hybrid appliance cannot connect to the broker node, verify that the IP address configured for the broker node matches the IP address configured for the submission interface on the broker node.
If a compute node cannot connect to a broker node, verify that the broker node IP address matches the IP address configured for the cluster interface on the broker node.
Try to ping the broker IP address:
If a compute node or another broker node cannot reach the broker node:
```
ping -I <cluster interface> <broker address>
```
If a sensor or hybrid appliance cannot reach the broker node:
```
ping -I <submission interface> <broker address>
```
where
- <cluster interface> is he name of the broker cluster interface.
- <submission interface> is the name of the broker submission interface.
- <broker address> is the IP address of the broker node.
If the interface cannot be reached, fix network connectivity and network settings.
- If the interface can be reached, but the connection cannot be established (because the connection timed out or was refused), make sure that TCP port 22 is not blocked by a firewall.
- If the connection still cannot be established, the problem could be authentication failure or internal error. Examine the system logs and contact Technical Support if you need assistance.