Every network outage, misconfiguration, or performance hiccup leaves behind a valuable lesson—a rule that should have been true to prevent it. These golden rules, along with their verification logic, are what we call network intents.
Intents are self-enforcing network truths—coded versions of your team’s network expertise. They contain a baseline truth and the logic to check it. Network intents codify your operational knowledge into enforceable rules that automatically propagate across your infrastructure – when you solve one problem, the system learns the underlying principle and proactively checks all other devices for similar vulnerabilities, preventing repeat incidents at scale.
For example:
Intents are automated through continuous assessments to proactively enforce all aspects of the network as “this must always be right.”
Intents are the fabric of network automation. Harness Intents in troubleshooting, change, and assessment workflows to keep your network in check.
Imagine:
The Network Intents below are just a few of the top reported uses of NetBrain No-Code Automation applied to real-world customer infrastructures.
Topic | Challenge | Solution |
---|---|---|
Compliance Validation for AWS EC2 Instances | Time-consuming to manually track EC2 instance configuration details. | Intents continuously assess each operating parameter across all instances. |
Native VLAN Compliance Check | Identify trunk ports with non-compliant native VLANs on a regular basis. | Intents verify the configuration of trunk ports to detect non-compliant VLANs enabled. |
# Days Since Interface Down | Manually identifying ALL/ANY inactive physical ports for service provisioning. | Intents assess the number of days since interfaces had active status. |
Administrator password access compliance | Manually identifying device access security across the network. | Intents assess devices with password access violations across the entire network. |
Proactive CISCO ACI Performance & Service Assurance | Widescale deployments of Cisco ACI include thousands of operating parameters that should be verified. | Intents assess the amount of available CPU and memory for the entire fabric. |
Monitoring Transient OSPF Neighbor Flaps Using Log Analysis | Limited ability to detect transient flapping at scale due to size and complexity. | Intents continuously assess OSPF neighbor state changes over time |
Failover and resiliency validation | Difficult to verify the entire failover architecture until it is too late | Intents assess availability and performance for all resiliency pathways; active and backup |