Create reusable configuration command sets and push them to one or many network devices in a single operation. Supports immediate execution and scheduled deployment, with a full execution history for every push.
NCM Configlets allow network administrators to define a set of configuration commands once and execute them across any number of devices without logging into each one individually. This is the feature to be used when you need to enforce a consistent configuration change at scale, such as updating NTP server addresses across all routers, pushing a revised ACL to every firewall, or enabling SNMPv3 on a group of switches.
Configlets are managed under Network → NCM → Configlets, which itself has three views: Configlets (the list of saved configlets, where they are created and executed), Scheduled Tasks (recurring configlet runs), and Execution History (a log of every past run). Each configlet can be executed immediately from the Configlet Table or scheduled to run on a recurring interval. All runs are logged in the Execution History view with per-device output, giving you a complete audit trail of every configuration push. Before executing configlets, ensure SSH or Telnet credentials are configured for the target devices. Refer to Network Configuration Management for credential setup.
Navigate to Network → NCM → Configlets and click Add. Fill in the fields as follows:
| Field | Description |
| Name* | A descriptive name for the configlet, such as "Update NTP Servers" or "Enable SNMPv3 on Cisco Switches". |
| Description | An optional description explaining what the configlet does and which devices it targets. |
| Vendor* | The device vendor this configlet is written for. Configlets are vendor-specific because command syntax differs between manufacturers such as Cisco IOS, Juniper JunOS, and Aruba. A configlet written for Cisco IOS will not work correctly on an Aruba device. |
| Execution Mode | Choose Basic for straightforward command sequences, or Advanced for configlets requiring conditional logic or variable substitution. |
| Command* | The configuration command or commands to push to the device. Click the + button to add multiple commands. For example, to replace an NTP server on a Cisco device: ntp server 10.0.0.1 followed by no ntp server 10.0.0.2. |
Click Save. The configlet appears in the Configlet Table and is ready for execution or scheduling.
The Configlet Table at Network → NCM → Configlets lists every saved configlet with its name, description, vendor, and execution mode. Each row has actions to View the configlet's commands, Execute it immediately, Schedule a recurring run, or Duplicate it as a starting point for a similar configlet.
To execute a configlet immediately, click the execute icon in the Actions column. Cloudmon pushes the commands to the target devices using the NCM protocol and credentials configured for each device. Check the Execution History view for results, showing per-device status, whether each command was accepted, and the full session output. This is the first place to look if a configlet runs but the configuration change does not appear to have applied.
To run a configlet on a recurring basis, click the schedule icon next to that configlet in the Actions column and fill in the scheduling fields. The schedule is tied to the configlet you clicked from, so there is no separate field to select which configlet runs.
| Field | Description |
| Schedule Name* | A name to identify this scheduled task in the Scheduled Tasks view. |
| Description | An optional description for this scheduled task. |
| Vendor* | The device vendor for this scheduled execution. |
| Interval* | How often the configlet runs. Options are Daily, Weekly, and Monthly. |
| Schedule Time | The time of day the scheduled run will execute, set using an hour selector with an AM/PM toggle. |
Click Save. All scheduled tasks are visible under the Scheduled Tasks view where they can be viewed, edited, or deleted.
| Issue | What to check |
| Execution fails on all target devices | Check the Execution History view for the session error. Authentication failures indicate the credential does not have sufficient privilege to enter configuration mode. Confirm the Enable Password is set for devices requiring privilege mode access. |
| Execution reports success but configuration did not apply | Verify the command syntax is correct for the selected vendor. A Cisco IOS command may not be valid on Cisco IOS XE or NX-OS. Review the session output in Execution History to confirm each command was accepted without error by the device. |
| Execution fails on some devices but not others | Failing devices may be running a different firmware version or feature set. Check the per-device output in Execution History and create a separate configlet with adjusted syntax for devices with different command requirements. |
| Scheduled configlet not running at the expected time | Verify the task exists in the Scheduled Tasks view and the interval, schedule time, and AM/PM setting are correct. Confirm the Cloudmon controller's system time and timezone are correct, as scheduled tasks run based on the controller's local time. |
| Execution History shows "There is no execution history" | No configlet has been executed yet within the selected time range, or the time range filter is too narrow. Run a configlet using Execute or wait for a scheduled run, then widen the time range filter in the top right of the Execution History view if needed. |