Table of Contents
This folder contains the Device Connection Health Check workflow, which is depicted in the following flowchart.
|A||Wait for a number of seconds (#ofSeconds) before attempting to connect/reconnect device.|
|Connect||Attempt connection to the device and evaluate response.|
|B||If connection is unsuccessful, try reconnecting a number of times (#ofTimes).|
|C||If connection is successful, try connecting to the device for #ofSeconds.|
The workflow that is built connects to a device and attempts to connect for a certain #ofTimes to check stability. If the device is not alive, it will attempt to connect for a certain #ofTimes, after which it ends with a "fail" output. Output is "success" if the device connects successfully. Inputs are validated, and produce a "bad input" error in case of wrong input.
This is how it relates to the flowchart:
This workflow is responsible for:
- Adding a delay for #ofSeconds before connecting to the device (before each retry).
- Attempting to connect to the device and getting a response (isAlive: true/false).
- If device is not alive, retry step 2 for #ofTimes.
- If device is alive, retry connecting consecutively with it #ofTimes (#retries).
- If step 4 fails during this duration, go back to step 3. The #retries for step 4 is reset here to 0 (reset consecutive counter).
- Auto-checks for input formatting errors.
- Connects to the device and determines if the device is alive.
- Waits for a certain amount of time before trying to establish a connection again.
- Retries only for a certain number of times (numberOfRetries).
- If connection to the device is successful, attempts for n - 1 more successful connections to the device (numberOfRetriesStability).
The following job variables are required to start the workflow.
|device||Name of device.|
|pingDelay||Seconds to wait before trying to establish connection with the device again.|
|numberOfRetries||Maximum number of times to attempt for a successful connection with the device.|
|numberOfRetriesStability||The number requirement for consecutive successful connections (to validate interface stability).|
Supported Device Types
Devices residing on any adapter that implement device-broker (Ex. NSO, Ansible) are supported. One may use any device that shows up in Configuration Manager.
- IAP version 2019.01.4
Running the device connection health check is meant to be called from parent workflows during device upgrade or any other maintenance that require verification of connection stability. To test this workflow in stand alone mode:
- Navigate to Workflow Builder.
- Click the play button next to the connection health check workflow.
- Supply the required inputs.
- Click start.