Troubleshooting BMC Network Automation integration to BMC Remedy ITSM
Note the following requirements for successful BMC Network Automation integration to BMC Remedy ITSM:
- BMC Network Automation relies on templates named Network Change, Network Incident, and Network Task. If you choose not to follow the template naming convention, you must consult for additional setup instructions (making the changes in the BMC Atrium Orchestrator Grid Manager application).
- The Support Group assigned to the embedded BMC Atrium Orchestrator Remedy user account (named orchestrationuser or ccnuser) must match the Authoring Groups assigned to the Network Change and Network Incident templates. The default is Change Management.
- The Assignee Group in the Network Task template must match the group assigned in the embedded BMC Atrium Orchestrator task query. The task query populates the BMC Remedy inbox with incident-related changes and BMC Remedy-initiated changes, pending service by BMC Network Automation users.
- The default Assignee Group is Change Management. Most likely you will define a unique Assignee Group for BMC Network Automation (for example, Network Engineering). If you elect to change the Assignee Group, you must consult for additional setup instructions (making the changes in the BMC Atrium Orchestrator Grid Manager application).
To troubleshoot issues with BMC Network Automation integration to BMC Remedy ITSM, complete the steps shown in the following table:
Step | Description |
|---|---|
Step 1: Collect the logs |
|
Step 2: Verify BMC Remedy User account |
|
Step 3: Verify templates | Verify the following templates were created by the BMC Remedy administrator (not automatically created by installation process):
|
Step 4: Verify Federated Links |
|
Step 5: Verify CMDB integration | Verify that the BMC Network Automation BMC Atrium CMDB integration is installed by performing the following steps:
|
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*