R12.1-JA-2025June05

Network Intent Cluster

Network Intent Cluster (NIC) expands Network Intent (NI) scope from a specific network design to one type of network design with similar diagnosis logic.

While NI effectively documents and validates a network design, it applies to only one network device or a set of devices at a time. Therefore, it can take many repetitive efforts to create NIs for a large network. NIC is designed to apply the logic of a NI (seed NI) to the whole network.

What's more, NIC can be triggered to run in the Triggered Automation Framework, and its results can significantly reduce the MTTR. NIC requires no coding skills and has an intuitive user interface for creating and debugging.

Example: You create an NI to monitor whether failover occurs between a pair of HRSP devices, US-BOS-R1 and US-BOS-R2 (the failover often causes the performance issue such as the slow application). Then, NIC can replicate the logic to all pairs of HRSP in the network without any coding.

NIC is composed of a group of NIs (member-NI) cloned from Seed NI via a 7-step, no-code process. A NIC may have thousands of member-NIs, corresponding to a specific network diagnosis. The following diagram is a sample NIC to clone a seed NI to check the HSRP running status for a network site. By creating a NIC to achieve this, you can expand the Diagnosis of one Site to your entire network. Each Member NI has its tag and signature variable, the virtual IP address of HSRP.

Graphical user interface Description automatically generated