Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Network Configuration Manager (NCM) > Unable to run DISA STIG policy reports

Unable to run DISA STIG policy reports

Updated August 17, 2016

Overview

Unable to run DISA STIG reports on NCM and the Last Update Column for the corresponding report on the NCM compliance page displays ERROR.

Environment

NCM 7.0 and later

Cause 

This occurs when the policy is either set to use a custom property that does not exist or has "nodeid" set as part of the dynamic query.  In either case, the query will not select any nodes.

Resolution

  1. From the Orion Web Console, open the NCM compliance page.
  2. Identify one of the Dist STIG reports displaying ERROR in the Last Update Column.
  3. Go to Manage Reports in upper right corner of the same page.
  4. Select the Report identified in Step 2 and select Edit.
    Note: Using the search option will be useful to narrow the hunt.
  5. Take note of which policies are in the report.  They will show in the Assigned Policies Column.

  6. Return to the Manage Policy Reports screen and go to the Manage Policies tab.

  7. Select the policy or one of the policies in the report and click Edit. 
    In NCM 7.5 you are likely to see something like this: 
    or if imported from Thwack, may look like this:

  8. in the first example, click on the blue hyperlink for all nodes. Use this to select the nodes, be it All nodes, Select nodes, or Dynamic selection. It is recommended to use Dynamic selection and use a rule relevant to the nodes you need this policy to run against (do not use Nodeid).
  9. When using Dynamic selection, select a valid option, such as Vendor, and select a valid vendor, such as Cisco.
  10. Click Submit to save the changes.
  11. Repeat this process for all applicable reports.
  12. From the compliance page, click Update all.
 

 

Last modified

Tags

Classifications

Public