- 18 Oct 2024
-
DarkLight
-
PDF
Software Upgrade (IOS) - Operations Manager
- Updated on 18 Oct 2024
-
DarkLight
-
PDF
You have now built out all of the different pieces for this exercise: a JSON Form as well as a workflow with both a child job and a newly-created Transformation. Next we will create an Operations Manager automation that will tie this together with a manual trigger.
Operations Manager Video
Step 1
From the IAP Home Page, click on Operations Manager.
Step 2
Operations Manager allows users to control when, how, and with what data a workflow should run.
Create a new automation by clicking the + at the top of the left navigation panel.
Step 3
The Create Automation window opens. Enter Lab – Software Upgrade – IOS – XX for the name, then click Create.
Step 4
Enter Lab – Software Upgrade in the Workflow search box and then select the Lab – Software Upgrade – IOS – XX workflow from the workflow dropdown box.
Step 5
Click the + under Triggers to add a trigger to your automation.
Step 6
Enter Manual for the name. Select Manual in the type dropdown
Step 7
Enter Lab – Software Upgrade in the Form search box. Select Lab – Software Upgrade – IOS – XX.
Click the Save Changes button at the bottom of the screen.
Step 8
Click the Run Manually button.
Step 9
Fill out the form data.
- Auto Approve – unchecked
- Device – IOS
- Version – Select the version your device is currently not configured with.
- Flash Memory - bootflash:
Click the Run Manually button.
Step 10
The automation has started. You can track the automation’s progress in the Job Details window or on the workflow’s canvas.
In the Job Details window, right click the 3 dots next to Run Child Job and select Open.
Step 11
The Itential Pre-Built workflow, Software Upgrade – IOS, displays. Here, you can track the progress of the individual tasks of the workflow, both in the Job Details window and on the canvas. At this stage, the workflow is verifying the file.
Click the Start Auto-Work button. This will enable you to interact with actionable tasks automatically
Step 12
The File Verification child job task includes a command template that requires user input. After verifying all commands and rules have passed, click the button.
Step 13
Our automation will conduct pre-checks next. This child job task also includes a command template that requires manual intervention. After verifying all Commands and Rules have passed, click the Success button.
Step 14
Our automation will continue to run through boot file configuration. Click the Provision button.
Step 15
Then device reload. It will then verify the new file version is on the device after reboot.
Step 16
Verify the new file version is on the device after reboot.
Step 17
It will then complete a post-check of the device, which will require manual intervention. Click the Success button once you have verified the command and all rules have passed.
Step 18
The automation will continue and conduct a post check. The results of the post check will be presented to the user and will require manual intervention for the automation to continue. Click the Success button after you have verified all commands and rules have passed.
Step 19
The automation will then evaluate the pre check and post check and prepare a diff report for the user. Once you are satisfied with the changes, click the Proceed button.
Step 20
Congratulations, your automation is now complete.