Configuring the Triage and Remediation module
The Content Installer provides a default configuration for the module, but you can modify the configuration to customize it for your system. Review the workflow discussions in the next topic before you configure any of the configuration groups in the Triage and Remediation module.
For more information about these modules, see Understanding Triage and Remediation.
To modify the Triage and Remediation for Infrastructure Management module configuration
- Open BMC Atrium Orchestrator Development Studio and click the Designer View icon.
- In the Project Explorer, under Applications, double-click Triage and Remediation to expand it.
- Double-click Configuration to open the Module Configuration Editor.
- Under Configuration, double-click to expand the view and display the configuration group items.
Double-click a group item to view the configuration items within that group.
Verify the value of each configuration item in the following configuration groups, and make the changes as needed for your environment:Configuration group See Runbook Defaults Runbook Defaults group configuration items Configuration Management Configuration Management group configuration items Change Management Change Management group configuration items Incident Management Incident Management group configuration items Event Management Event Management group configuration items Default User Default User group configuration items Task Management Task Management group configuration item OS Disk Space Full OS Disk Space Full group configuration items Host Down Host Down group configuration items ESX Host Not Responding ESX Host not Responding configuration items Server Restart Server Restart configuration items Server Start Server Start configuration items Service Restart Service Restart configuration items DB Tablespace Full DB Tablespace Full configuration items Failed Backup and Recovery Failed Backup and Recovery configuration items Agent Restart Agent Restart configuration - Double-click a configuration item, make the required changes to the value, and click Save.
Runbook Defaults group configuration items
The following table lists the Runbook Defaults configuration items:
Triage and Remediation- Runbook defaults group configuration items
Configuration item | Description |
---|---|
Pause Count | If the workflow includes a wait time, the pause count indicates the length of the wait time in minutes. The default is one minute. |
Urgency Mappings | An XML statement that maps the change request value from the event to ITSM values. An example XML statement follows.
|
Detailed Logging File | Indicates whether detailed logging is enabled for all workflows You can override this value at the workflow level. |
TSM_Locale_Language | The TSM_Locale_Language parameter specifies a valid ISO language code. The code must be a lowercase, two-letter code, as defined by ISO-639. For example, en for English and es for Spanish |
TSM_Locale_Country | The TSM_Locale_Country parameter specifies a valid ISO country code. The code must be an uppercase, two letter code, as defined by ISO-3166. For example, EN for English and ES for Spanish |
Configuration Management group configuration items
The following table lists the Configuration Management group configuration items:
Triage and Remediation- Configuration Management group configuration items
Configuration Item | Description |
---|---|
Platform | BMC_AR_System Specifies the name of the system where the CMDB is managed. |
Enabled | Defines whether CMDB integration is enabled |
Change Management group configuration items
The following table lists the Change Management group configuration items:
Triage and Remediation- Change Management group configuration items
Configuration Item | Description |
---|---|
Platform | BMC_AR_System Specifies the name of the system where change tickets are managed. |
Template | An XML statement that defines the templates that Triage and Remediation Solution uses for creating change management tickets. An example XML statement follows.
|
Timings | An XML statement that defines mappings for types of change for your ARS environment. Customize for your environment. An example XML statement follows.
|
Default Status | Default status used when creating a new change. Default: Request for Authorization |
Default Change Type | Default change type used when creating a new change. Default: Change |
Default Impact | Default impact used when creating a new change. Default: 4 Minor/Localized |
Default Risk Level | Default risk level used when creating a new change. Default: Risk level 2 |
Default Timing | Default timing used when creating a new change. Default: No Impact |
Default Urgency | Default urgency used when creating a new change. Default: Medium |
Incident Management group configuration items
The following table lists the Incident Management group configuration items:
Triage and Remediation- Incident Management group configuration items
Configuration Item | Description |
---|---|
Platform | BMC_AR_System Specifies the name of the system where incident tickets are managed. |
Template | An XML statement that defines the templates that Triage and Remediation Solution uses for creating incident tickets. An example XML statement follows.
|
Default Status | Default status used when creating a new incident. Default: In progress |
Default Service Type | Default service type used when creating a new incident. Default: Infrastructure event |
Default Impact | Default impact used when creating a new incident. Default: 3-Moderate/Limited |
Default Urgency | Default urgency used when creating a new incident. Default: 3-Medium |
Default Reported Source | Default reported source used when creating a new incident. Default: Systems Management |
Default Status Reason | Default status reason used when creating a new incident. Default: Infrastructure Change |
Event Management group configuration items
The following table lists the Event Management group configuration items:
Triage and Remediation- Event Management group configuration items
Configuration Item | Description |
---|---|
Platform | BMC_Event_Manager Specifies the name of the system where events are managed. |
Event Mappings | Defines the mappings between event definitions to enable the workflows to gather data from different event classes. An extract displaying the mappings of an event class is shown in the following graphics: |
Default User group configuration items
The following table lists the Default User group configuration items:
Triage and Remediation - Default user group configuration items
Configuration Item | Description |
---|---|
Username | Default: Allen |
Platform | Default: BMC_AR_System |
Schema | Default: CTM:People |
Adapter | Default: ARSAdapter |
Authentication Query Mappings | An XML statement that maps the user information to the ITSM values. An example XML statement follows.
|
Version | Default: v7.5 |
Task Management group configuration item
The following table lists the Task Management group configuration items:
Triage and Remediation - Task Management group configuration items
Configuration Item | Description |
---|---|
Platform | BMC_AR_System Specifies the name of the system where change tickets are managed. |
OS Disk Space Full group configuration items
The following table lists the OS Disk Space Full group configuration items:
Triage and Remediation - OS Disk Space Full group configuration items
Configuration Item | Description |
---|---|
Triage Commands | Using static values, defines the commands used to determine whether the disk space is full for each supported operating system |
AO Host | The IP address or host name of the BMC Atrium Orchestrator computer |
Remediation Commands | Using static values, defines the commands, such as delete, clean, and compress, that are used to remediate the disk space full issue on different operating systems |
WF_Detailed_Logging_Flag | Indicates whether detailed logging is enabled for this workflow |
Host Down group configuration items
The following table lists the Host Down group configuration items. You must configure these items to match the names or IP addresses of the hosts and the router in your system that you want to use to ping the computer that might be down. If the ping command fails, the ping host from where the ping failed launches a traceroute and collects the traceroute information.
Triage and Remediation - Host Down group configuration items
Configuration Item | Description |
---|---|
Ping Host 1 | The IP address or the name of one of the computers used in 360 degree ping |
Ping Host 2 | The IP address or the name of another of the computers used in 360 degree ping |
Ping Host 3 | The IP address or the name of still another of the computers used in 360 degree ping |
Ping Router | The name of the default router used in the 360 degree ping. The default router is used only if the traceroute command fails to discover any router. |
Ping Command | The Ping command that is appropriate for the routers in your environment. |
WF_Detailed_Logging_Flag | Indicates whether detailed logging is enabled for this workflow |
ESX Host not Responding configuration items
The following table lists the ESX Host not Responding group configuration items. You must configure these items to match the names or IP addresses of the hosts and the router in your system that you want to use to ping the computer that may be down. If the ping command fails, the ping host from where the ping failed launches a traceroute and collects the traceroute information.
Triage and Remediation - ESX Host not Responding group configuration items
Configuration Item | Description |
---|---|
Ping Host 1 | The IP address or the name of one of the computers used in 360 degree ping |
Ping Host 2 | The IP address or the name of another of the computers used in 360 degree ping |
Ping Host 3 | The IP address or the name of yet another of the computers used in 360 degree ping |
Ping Router | The name of the default router used in the 360 degree ping. The default router is used only if the traceroute command fails to discover any router. |
Ping Command | The Ping command that is appropriate for the routers in your environment. |
WF_Detailed_Logging_Flag | Indicates whether detailed logging is enabled for this workflow |
Server Restart configuration items
Triage and Remediation - Server Restart group configuration items
Configuration Item | Description |
---|---|
Restart group | Defines the restart FAT commands for the different operating systems. |
AO_Host | BMC AO host where the Configuration Distribution Peer (CDP) server resides. The restart FAT commands are launched from the AO host system. |
WF_Detailed_Logging_ Flag | Indicates whether detailed logging is enabled for this workflow |
Validation_Pause_Count_Minutes | Time in minutes before the validation process begins to verify that the server has restarted or started. |
Wake_On_Lan | Networking standard used to send a start signal to the server |
Server Start configuration items
The Server Start workflow uses the Validation_Pause_Count_Minutes and Wake_On_Lan configuration items that are defined under the Server Restart configuration module.
Service Restart configuration items
Triage and Remediation - Service Restart group configuration items
Configuration Item | Description |
---|---|
Service_Actions_Aliasing | Aliases that point to the different services which the Service_Restart workflow addresses |
AO_Host | BMC AO host where the Configuration Distribution Peer (CDP) server resides. The service stop/start commands are launched from the AO host system. |
WF_Detailed_Logging_Flag | Indicates whether detailed logging is enabled for this workflow |
Validation_Pause_Count_ Minutes | Time in minutes before the validation process begins to verify that the server has restarted or started. |
DB Tablespace Full configuration items
Triage and Remediation - DB Tablespace Full group configuration items
Configuration Item | Description |
---|---|
AO_Host | BMC AO host where the Configuration Distribution Peer (CDP) server resides. The service stop/start commands are launched from the AO host system. |
WF_Detailed_Logging_Flag | Indicates whether detailed logging is enabled for this workflow |
Datafile_Increment_Size_ MB | Size in megabytes by which the remediation process increases the tablespace size to correct the tablespace full condition |
Failed Backup and Recovery configuration items
Triage and Remediation - Failed Backup and Recovery group configuration items
Configuration Item | Description |
---|---|
AO_Host | BMC AO host where the Configuration Distribution Peer (CDP) server resides. The service stop/start commands are launched from the AO host system. |
WF_Detailed_Logging_Flag | Indicates whether detailed logging is enabled for this workflow |
TSM_Adapter_Name | Name and type of adapter used to communicate with the IBM Tivoli Storage Manager instance |
Extract_log | Contains the different OS forms of the tail command for extracting recent information from log files |
UNIX_Dsmerror_Logpath | File path to Tivoli Storage Manager's dsmerror.logfile on UNIX systemsopt/tivoli/tsm/client/ba/bin/dsmerror.log |
Windows_Dsmerror_Logpath | File path to Tivoli Storage Manager's dsmerror.logfile on Windows systems C:\Program Files\Tivoli\TSM\baclient\dsmerror.log |
Pause_Before_ Reschedule_Min | Wait time in minutes before the backup job is rescheduled to start |
Windows_DsmScheduler_ ServiceName | Name of the Tivoli Storage Manager scheduler service that is started after the workflow reschedules the failed job The default value is TSM Scheduler. |
Comments
Log in or register to comment.