Export (0) Print
Expand All

How to Create Diagnostics and Recoveries

Updated: May 22, 2009

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

You can add tasks to your management pack that can be run to help diagnose issues and assist in recovery. In this topic, you will add a diagnostic task to your sample management pack and then test it.

noteNote
This topic assumes that you are using the management pack created in the How to Create a Management Pack With a Discovery Using the Windows Registry Template and subsequent topics.

Create the Diagnostic Task

  1. In the Health Model space of the main authoring console window, expand the Tasks node, and then clickt Diagnostics.

  2. Right-click in the Diagnostics list, then click New on the context menu, and then click Command Line Task.

  3. On the Command Line Task page, enter AuthoringConsole.MyFirstMP.DiagnosticTask in the ID field.

  4. Enter Diagnostic Task in the Display Name field.

  5. Select AvailabilityHealth from the Category drop-down list, and then click Next.

    16ae30a4-c9da-46ab-9854-a55647f50ee6
  6. On the Trigger Settings page, select AuthoringConsole.MyFirstMP.LOBApplication from the Target drop-down list.

  7. Select AuthoringConsole.MyFirstMP.MonitorConnectionState from the Monitor drop-down list.

  8. Select Warning from the Monitor Health State drop-down list, and then click Next to display the Configure Command Line Execution Settings page.

    d4b80e4d-eb94-4234-89a0-9d5b778d3597
  9. On the Configure Command Line Execution Settings page:

    • Enter c:\windows\system32\ipconfig.exe in the Full path to file field.

      noteNote
      This path may be different on your system. You can also enter %Windir%\system32\ipconfig.exe in this step.

    • Enter /all in the Parameters field.

    • Click Finish to save the diagnostic and return to the Diagnostics list view.

    21ab85c1-f2a4-40c6-9b2e-3b727bc0254a
  10. Save the management pack.

  11. Upload the management pack to the management group by clicking Tools, and then clicking Upload to management group from the authoring console menu.

  12. Type the name of or select the appropriate server from the Connect To Server dialog box, and then click Connect.

    d41a088d-3a66-4369-a76f-16d2d71f0daf

Test the Diagnostic

  1. In the Operations Console, click the Monitoring button.

  2. On the monitored server, run the following command from a command line:

    EventCreate /id 201 /t information /d Test

  3. Observe the state of the LOB Application instance as it becomes unhealthy.

    e66df2ba-4eaf-4b66-81e8-1e16bf0fa54e
  4. Right-click the LOB Application in the LOB Application State list view, click Open, and then click Health Explorer for AuthoringConsole.MyFirstApp.LOBApplication from the context menu.

  5. Expand the Entity Health and Availability nodes in the Health Monitors list on the left side of the authoring console window, and then click the LOB Application Connection State monitor.

    ddb9f00a-2091-45cd-805b-3a6c5cc18ca4
  6. Click the State Change Events tab, and then select the warning event in the list view.

  7. In the Details area, locate the diagnostic task you just defined, click it, and then click Yes to confirm that you want to run the diagnostic task.

    f4a31186-c3b0-43fc-9a7e-c509ff9f27a1
  8. The diagnostic output displays in the details view.

    411aa27c-6a3e-4404-a553-c821f397b84a

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft