Cisco Bug: CSCvh79847 - Some diagnostics failure conditions do not generate traps
Jul 02, 2018
- Cisco Policy Suite for Mobile
Known Affected Releases
Symptom: Some example alerts in diagnostics, which all arose because the qns user could not log in: Could not connect to port 9091 on qns20 (CPS Admin port)...[FAIL] Corrective Action(s): 1. Ensure qns is running with: runonone.sh qns20 /etc/init.d/qns status 2. If CPS is not running. Attempt to start it with: startqns.sh qns20 and monitor the logs for errors. 3. If CPS is running, the port may not be open in the firewall on qns20. To fix, edit the firewall configuration and rerun puppet qns user not able to login without password on lb01...[FAIL] Corrective Action: run pupdate Checking swap space for all VMs.../var/qps/bin/support/diag_functions.sh: line 336: [: -eq: unary operator expected [PASS] Checking memory from lb01...[FAIL] Checking CPU Count on lb01...[FAIL] CPU Count on lb01 is currently 0. It is recommended to be 2 (minimum 2) Conditions: In this case it was because of a login failure. However, this cdet should address all conditions that diagnostics.sh checks. If any of these fail, an snmp trap should be generated.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases