7.8 Troubleshooting Health Reports

When I schedule a report, health reports are generated for some servers and an error report is logged for other servers.

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Health Reports
Possible Cause: The Health Report server collects the health information data from the trending agents. Based on the associated profile of the report, you might need to run particular agents on the servers from where the Health Reports are expected.

The profile-agent list is:

  • NetWare Profile - nma
  • Windows Profile - ntma
  • Ethernet Profile - lanz
  • Token Ring Profile - lanz
  • FDDI Profile - lanz
  • Linux Profile - advtrend
Action: Make sure that respective agents are running on the server from where you want to see the health reports.

If the agents are running, check for the connectivity:

  1. Atlas > Action > MIB Browser.

  2. Set the SNMP Preferences according to the server settings of the server where the Health Report is not being generated.

  3. Try to tree-walk the system table; if you are unable to do so it means the server where you want to generate the Health Report has some basic connectivity problem that is not related to ZENworks Server Management.

  4. Resolve the connectivity issue of the agent by checking the NIC card.

Action: If the connectivity is working and the agents are running, but you are unable to see the Health Report being generated, go to ConsoleOne in Atlas and find the server where the Health Report is not getting generated (click Atlas > Find). In the ConsoleOne right pane, right-click the server, then click View > Trend.

If you see no data in the Trend view, it means that the trending agent does not have the history of the data collected and you might need to wait for about 24 hours and regenerate the Health Report by clicking Now.

If you are able to see the data in the Trend and if you are still not able to see Health Reports, synchronize the server time with that of the Site Server time.

When I schedule a report, all the servers display the error report.

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Health Reports
Possible Cause: This could indicate that there is an issue with the site server communication with other servers.
Explanation: The Health Report server creates a list of agents running requested service, such as the following is profile-agent-service list:
  • NetWare Profile - ManageWise_NovellLANalyzerAgentService
  • Windows Profile - ManageWise_WindowsNTManagement
  • Ethernet Profile - CIM_EthernetSegment
  • Token Ring Profile - CIM_TokenRingSegment
  • FDDI Profile - ManageWise_FDDISegment
  • Linux Profile - ManageWise_LinuxManagementAgentService
Action: To find the services running on the given server:

  1. In ConsoleOne, find the server where the Health Report is not being generated (click Atlas > Find). In the ConsoleOne right pane, right-click the server, then click the Properties > Computer Attributes tab to check the Service option.

  2. Ensure that server is running the required service. If the service is not running, the discovery is still going on and you might need to wait for the discovery to stabilize.

  3. If the service is found and you still do not see Health Reports, there might be some temporary problem with the site server. Try running the Health Report again by clicking Now.

The Health report is generated but does not contain sufficient data

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Health Reports
Possible Cause: The agents such as nma, ntma, and lanz where the trend data is collected do not contain sufficient data.
Explanation: The Health Report Server collects the Health data from predefined agents. These agents collect the history data, but the availability of the requested data depends on how long these agents have been running.
Action: Ensure that sufficient data is available. To check this, view the trend data using the MIB browser or view the Trend View on the NetWare server.

I am unable to schedule the Health report

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Health Reports
Possible Cause: If the reports are successfully generated for a few days and then stop being generated, the Health reports encountered an error while running on some of the servers. This means that current run of the Health reports has not completed successfully, so the next run of Health report cannot occur.
Action: In the Health Report [name] section of the latest sloader.log file, check to see if every started message has a corresponding completed message. If it does not, the Health report has not successfully completed its run, and the next run cannot take place.

Consolidation destroys health reports

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Health Reports
Possible Cause: When the topology is in being built, the Health Report settings are lost because of consolidation. This is because of the change in the ID of the object.
Action: After the topology stabilizes, reconfigure the Health Report.

Health Reports have stopped generating

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Health Reports
Possible Cause: If you scheduled a daily report on Monday, and the reports were generated for Monday and Tuesday but have stopped generating after Tuesday, it indicates that the Health Report encountered problems for some of the servers during one of the runs.
Action: Do the following:

  1. Stop and start sloader.

  2. Reconfigure the Health Reports.