Use Case: IPAM

Objective

To automatically alert the network operations team when a Subnet Breach occurs or an IP Conflict is detected in the IPAM module, ensuring a quick response to capacity risks and IP duplication issues.

Scenario

A large enterprise manages multiple subnets through IPAM. When a subnet exceeds its utilization threshold or when two devices are assigned the same IP address, this can lead to service outages or network instability.

A trigger is configured to notify technicians whenever critical IPAM events occur.

Configuration Steps

Trigger | Add Trigger Details

Label	Action	Description / Example
Name	Enter trigger name	Example: IP Conflict, Subnet Breach Trigger
Status	Enable the trigger	Turn ON to activate the trigger
Visibility	Select visibility	Choose Public or Private
Customer Name	Select customer	Select relevant tenant/customer
Alert Raises	Select alert mode	Choose Immediately after alert raises
After Correlation	Optional selection	Enable only if alerts must be correlated before notification

Conditions | Add Filter Conditions

Label	Action	Description / Example
Business Hour Profile	Select time profile	Example: 24×7
Trigger only when the Parent Node is up	Toggle ON/OFF	Enable if alert should fire only when the parent device is reachable
Trigger Delay	Optional	Keeps a delay before firing the alert
Seasonal Suppression	Optional	Temporarily suppress alerts during maintenance windows
IF – Severity	Select condition	Set Severity in Critical
AND – Alarm Message	Select condition	Choose IP Conflict Identified and IP Subnet Breached
Criteria Pattern	Define logic	Example: (1 AND 2)

How It Works

Whenever the IPAM scan detects either an IP Conflict or a Subnet Breach with Critical severity, the trigger conditions are matched instantly. The trigger fires immediately based on the configured profile and raises an alert.

The configured actions notify the support team so they can resolve the IP conflict or release/expand subnet capacity before it impacts network operations.