| Symptom | Possible Cause | Test/Remedy |
|---|
New sensor is not connecting to Pulse.
| Sensor has not been registered. | Register sensor locally. |
| Sensor does not have an outbound connection. | Check outbound connections by running px-connection-dr script* |
| Sensor has not been approved in Pulse. | Approve sensor in Pulse. |
| An existing sensor is no longer connecting to Pulse. | Sensor has lost power. | Check sensor power. |
| Sensor no longer has outbound connectivity. | Check outbound connections by running px-connection-dr script*. |
| Cycle power to sensor by turning sensor off for 30 seconds and turning back on. |
| An expected alert is not triggering. | Alert is not properly set. | Check alert settings. |
| Alert is not enabled or subscribed. | Ensure alert is enabled and has been subscribed. |
| Device is out of range. | For wired devices, ensure the appropriate subnet can be seen by the sensor. |
For wireless devices, ensure that the device is within range of the sensor. |
| OpenVAS Scan not showing expected vulnerabilities | Scan Task not configured properly | Check scan configuration to ensure it is set to scan the correct subnets. |
| Network configuration issue | Ensure target networks can be seen on network by sensor. |
| Scan traffic being blocked | Ensure proper exclusions set on firewall/IDS solution. |
| Scan not complete | Allow more time to complete scan. |