Document toolboxDocument toolbox

Automation Change Manager (ACM) Triggering Sources

One category of triggering sources involves the Automation Change Manager. When the ACM license is installed into the NetMRI appliance, specific trigger source types are automatically  detected by NetMRI and separately developed jobs are built in to the Triggered Jobs page. The three Triggered Jobs you see after installing the Automation Change Manager license include the following:

  • Provision Bare Metal Device (Issue-driven)
    The ACM Provision Bare Metal job executes auto-configuration of a new device on the network immediately after detection by NetMRI. This job requires approval by the administrator before execution. Also refers to the Perl script, Provision Bare Metal Device, for applying the config template to the new device.
  • Locate Rogue DHCP Server (Issue-driven)
    When NetMRI detects any system running the DHCP protocol that is not on the list of approved DHCP servers or is not considered a sanctioned DHCP server by NIOS, NetMRI executes the job and compiles the information to locate that rogue system on the network. Locate Rogue DHCP Server runs automatically and provides logs when it executes.
  • Isolate Rogue DHCP Server (Issue-driven)
    After NetMRI detects and locates a rogue DHCP server, the discovered device is consigned to a designated isolation VLAN to be dealt with. This job requires approval by the administrator.

Two triggering sources support a single ACM task. The Locate Rogue DHCP Server and Isolate Rogue DHCP Server jobs support the NIOS Dashboard Rogue DHCP Server Remediation task. Locate Rogue DHCP Server executes automatically in response to Automation Change Manager detection of a NIOS DHCPACK Syslog messages on the network. Isolate Rogue DHCP Server jobs require authorization by the administrator to execute.