Recently Viewed Topics
NNM server does not appear to be operational
- Verify in the SecurityCenter GUI that the NNM server appears as Unable to Connect under Status.
- SSH to the remote NNM host to make sure the underlying operating system is operational.
Confirm that the NNM is running (Linux example below):
# service pvs status
PVS is stopped
PVS Proxy (pid 3142) is running
If the NNM service is not running, start the service:
# service pvs start
Starting PVS Proxy [ OK ]
Starting PVS [ OK ]
Cannot add a NNM server
Confirm that the NNM proxy is listening on the same port as is configured in SecurityCenter (port 8835 by default):
# ss -pan | grep 8835
tcp 0 0 0.0.0.0:8835 0.0.0.0:* LISTEN 406/pvs
- Check connectivity by telnetting from the SecurityCenter console into the NNM server on port 8835 (the NNM listening port). If successful, the response will include: Escape character is '^]'.
No vulnerabilities are being received from the NNM server
- Ensure that the NNM service is running on the NNM host.
- Ensure that the NNM is listed in SecurityCenter under Resources > Passive Scanners and that the status of the NNM is listed as Working. Click Edit to ensure that the IP address or hostname, port, username, password, and selected repositories for the NNM are all correct. Edit any incorrect entries to their correct state and click Submit to attempt to reinitialize the NNM scanning interface.
NNM plugins fail to update
- Manually test a plugin update under Plugins with Update Plugins. If successful, Passive Plugins Last Updated will update to the current date and time.
- Ensure that the SecurityCenter host is allowed outbound HTTPS connectivity to the NNM Plugin Update Site.
- For all other NNM plugin update issues, contact Tenable Support at .