Creating workflows for Cisco Prime Infrastructure assets

Let Oomnitza be your single source of truth!

You'll get visibility of your assets as data from Cisco Prime Infrastructure is automatically transformed into consumable information and actionable insights.

Connect Oomnitza and Cisco Prime Infrastructure in minutes

Get the information and insights that you need by creating configurable workflows for creating, updating, and deleting TACACS+ servers.

Navigation

Before you start

Creating workflows

Before you start

Before you can create the integration with Oomnitza, you need to have added your Cisco Prime Infrastructure credentials to Oomnitza.

You will need at least NBI Write permissions to run workflows.

Creating workflows

Create asset workflows

To create an asset workflow, you must complete these steps:  

1. Click Configuration > Workflows.
2. Click Add (+) and select Assets.
3. Enter the name and description of the workflow.
4. Edit the Begin Block and add rules to trigger the workflow. For example, if you set the Actions to New you can trigger a workflow every time a new asset is created. Refer to Using the Begin block.
5. Drag and drop the API block onto the Sandbox.
6. Click Edit on the API block and enter Cisco Prime Infrastructure in the search field. 
7. Select a preset from the list below. To choose a preset, click the forward arrow (>).
   
   • Cisco Prime Infrastructure Add Server
   • Cisco Prime Infrastructure Update Server
   • Cisco Prime Infrastructure Delete Server
8. Select the credentials that you created in  Creating an extended integration for Cisco Prime Infrastructure assets
9. Enter any mandatory information when prompted.
10. Select Advanced Mode.
11. Select the Body tab. Review and ensure that the properties referenced in this location, are populated with the correct information before you run this workflow. 
12. Select the Response tab. You can map the entire response by placing {{response}} in the Response field and mapping it to an Oomnitza field.
13. Connect the Blocks. 
14. Save, validate, and activate your workflow.

Using the Cisco Prime Infrastructure Add Server preset

The Cisco Prime Infrastructure Add Server preset adds a new TACACS+ server.

Request Payload Parameters	Description
Authentication Type	Authentication method. Permitted values PAP CHAP
Local Interface IP	IP address of the local interface
Number of Tries	The number of attempts to access the server. The value should be in the range of 0 and 3
Port	IP port of the TACACS+ server. The value should be in the range of 1 and 65535
Retransmit Timeout	The delay between attempts in seconds. The value should be in the range of 2 and 15
Secret Key	The secret key. The value can be ASCII or HEX.
Secret Key Type	The type of secret key. Permitted values ASCII HEX
Server Host Name	FQDN of the TACACS+ server. Either the Server IP or Server Hostname is required.
Address	IP Address of the TACACS+ server. Either the Server IP or Server Hostname is required.

Sample JSON Request Payload

 {
  "tacacsPlusServer" : {
    "authenticationType" : "PAP",
    "localInterfaceIp" : {
      "address" : "192.168.115.243"
    },
    "numberOfTries" : 1,
    "port" : 1,
    "retransmitTimeout" : 1,
    "secretKey" : "String value",
    "secretKeyType" : "ASCII",
    "serverHostName" : "String value",
    "serverIp" : {
      "address" : "192.168.115.243"
    }
  }
}

Sample JSON Response Payload

  "mgmtResponse" : {
    "@requestUrl" : "https://localhost/webacs/api/v4/op/aaa/tacacsPlusServer",
    "@responseType" : "operation",
    "@rootUrl" : "https://localhost/webacs/api/v4/op",
    "serverResultItem" : [ {
      "operationSucceeded" : true,
      "resultMessage" : "String value",
      "server" : {
        "authenticationType" : "PAP",
        "localInterfaceIp" : {
          "address" : "192.168.115.243"
        },
        "numberOfTries" : 1,
        "port" : 1,
        "retransmitTimeout" : 1,
        "secretKey" : "String value",
        "secretKeyType" : "ASCII",
        "serverHostName" : "String value",
        "serverIp" : {
          "address" : "192.168.115.243"
        }
      }
    } ]
  }
}

Using the Cisco Prime Infrastructure Update Server preset

The Cisco Prime Infrastructure Update Server preset updates a Cisco Prime Infrastructure server. Refer to the Add Server preset for the required input. The Update Server preset has the same JSON Request and Response Payload as the Add Server preset. 

Using the Cisco Prime Infrastructure Delete Server preset

The Cisco Prime Infrastructure Delete Server preset deletes a Cisco Prime Infrastructure server. 

The server to be deleted is referenced in the Advanced Mode > Params tab in the property{{ip_address}} and {{server_host_name}}.You can run the Cisco Prime Infrastructure extended asset integration to retrieve this information before you run this workflow.

Sample JSON Response Payload

{
  "mgmtResponse" : {
    "@requestUrl" : "https://localhost/webacs/api/v4/op/aaa/tacacsPlusServer?serverIp=192.168.115.243",
    "@responseType" : "operation",
    "@rootUrl" : "https://localhost/webacs/api/v4/op",
    "deleteServerResult" : [ {
      "operationSucceeded" : true,
      "resultMessage" : "String value",
      "serverHostName" : "String value",
      "serverIp" : "String value"
    } ]
  }
}

Reference articles for workflows

• Mapping positive and negative responses
• Troubleshooting workflows 
• Using the API block