Troubleshooting runbooks
This topic describes the issues that you might encounter while using the TrueSight Orchestration runbook, and the workarounds to resolve the issues.
Troubleshooting the issues with the invalid assignment details in the task template
When you create a change request (CR) with invalid assignment details in the task template, the following message may be displayed:
The Assignment Information is not valid. Use the menus provided on the Assignee Company, Assignee, Organization and Assignee Group or the type ahead return function on the Assignee Group or Assignee fields fields to select this information.
The assignment issues occur for the following solutions:
- Continuous Compliance for Databases
- Continuous Compliance for Networks
- Continuous Compliance for Servers
- Triage and Remediation
- NetApp Solutions
Solution: Create a change request with valid assignment details in the task template for the runbooks.
Troubleshooting the Continuous Compliance for Servers runbook when the BladeLogic adapter is enabled in the BLCLI tunneling mode
When you enable the BMC Server Automation application adapter in the BMC BladeLogic command-line interface (BLCLI) tunneling mode, the Continuous Compliance for Servers, Closed Loop Server Audit and Closed Loop Server Compliance runbooks fail to execute.
This problem does not affect the Operator Initiated Change and Server Incident Enrichment runbooks.
Solution: To avoid this issue, you must use two instances of the BMC Server Automation adapter.
When the BladeLogic adapter is enabled in BLCLI tunneling mode, the module's BLCLI, which creates a .csv file, creates the same .csv file on the BMC BladeLogic server. The File adapter is not able to read this file since it cannot be configured to read or write files on remote machines. Due to this limitation, the runbook module fails when the BladeLogic adapter is enabled in BLCLI tunneling mode.
To prevent the runbook module from failing, use two instances of the BMC BladeLogic adapter. Configure the first instance in BLCLI tunneling mode and the second in normal mode (supporting nsh). After you configure the adapters, the second adapter instance creates the csv file on the server where the adapter is enabled during BLCLI calls. Using this method, you also leverage the benefits BLCLI tunneling for other BLCLI calls.
To prevent runbook module failures, perform the following procedures:
Note
You must perform these procedures on both affected runbooks: Closed Loop Server Audit (Closed_Loop_Server-SA-Audit) and Closed Loop Server Compliance (Closed_Loop_Server-SA-Compliance).
To set the BLCLI tunneling flag to true:
- Launch TrueSight Orchestration Development Studio, and then select Designer.
- Expand the grid, and then expand the Closed Loop Server runbook that you want to modify.
- Expand configuration, BLADELOGIC, and Runbook_Defaults.
- Navigate to and open the blcli_tunneling configuration item.
- In the Value box, enter true.
Closed Loop Server runbook BLCLI parameter value
To activate two instances of the TrueSight Orchestration application adapter for BMC BladeLogic Server Automation:
Note
You must specify a unique name for each instance of the TrueSight Orchestration application adapter for BMC BladeLogic Server Automation.
- Using Grid Manager, in the adapter configuration, enable the adapter in tunneling mode. See BMC Server Automation adapter for details on enabling the adapter in tunneling mode
- Using TrueSight Orchestration Development Studio, in the Designer mode, navigate to the runbook that you want to modify.
- Expand configuration, BLADELOGIC, Runbook_Defaults, and BL_Connection_Details.
- In the Value box, specify a unique name for this instance of the BMC Server Automation adapter.
Closed Loop runbook application adapter first instance
- On the same peer on which the file adapter is enabled, enable the BMC Network Automation adapter by setting the
<is-cli-tunnel-enabled>
element to false in the adapter configuration to supportnsh.
For more information, see BMC Server Automation adapter. - Navigate to BLADELOGIC > Runbook_Defaults > BL_Connection_Details_Instance_2 parameter.
- In the Value box, specify a unique name for the second instance of the BMC Server Automation adapter.
Closed Loop runbook application adapter second instance
Comments
Log in or register to comment.