Run a Network Intent at the Backend Automatically

Like other automation objects such as Qapps, NIs can be triggered by condition or ticket to run at the backend automatically. More commonly, NIs can be triggered to run by:

• 3rd-party System
• Preventive Automation via ADT
• Schedule Intent Directly
• Flash Probe

Triggered by 3rd-Party System

Three ways to define triggered NI by a 3rd-party system:

• Use Triggered Automation to trigger NI:
  
  
• Use API Stub to trigger NI.
  The typical use case is that the 3rd-party system will trigger NetworkBrain Runbook Template execution, including an NI node. For example, a ticket is created since a BGP neighbor of a core device is flapping, which triggers an API call to the NetworkBrain System, and the device name and BGP are sent to NetworkBrain as a keyword. A NetworkBrain Runbook can filter NIs related to this device and BGP and execute these NIs.
  
  
• Use Event Template to trigger NI:
  
  

Triggered by Preventive Automation via ADT

Intents can be triggered by the following three ways in preventive automation:

Note: See Preventive Automation via ADT for more information.

• Looking Glass Probe:
  
  
• Primary Probe:
  
  
• Intent Timer:
  
  

Schedule Intent Directly

Intent can also be scheduled to run at backend automatically.

Triggered by Flash Probe

A Flash Probe can be added to an NI and a backend process can monitor the whole network's status periodically. When a flash alert occurs, the system will further execute NIs. You can view the triggered NI results with the flash probe via Execution Tree. For example, HRSP NI can be installed as triggered automation of the HSRP state flash probe of the device BJ-L2-Core-A. When an alert occurs on the flash probe, you can trigger the NI to execute automatically.