Mass Config Push in Unimus is used to send a set of commands to to a group (or all) of devices in your network. This allows you to roll out mass config changes across your network, or query command outputs from a large set of devices. Before you can push to devices, each device must be in a "discovered" state (normally done one device addition into Unimus). Config push will not be performed to undiscovered devices, and they will be grouped in the "Un-discovered devices" group.
To perform a push, you first need to create a "Push Preset" from the Mass Config Push home page. After a preset is created, you can click "Run now" to push the provided commands to the selected devices.
The commands you specify in the Push Preset are sent to the devices, one line at a time (more info in How commands are sent to devices).
State of device before Push - require "enable" or "configure" CLI mode
You have the option of letting Unimus ensure that each device in the Push Preset is in a desired CLI mode before your specified commands are pushed. You can check "Require enable mode" and/or "Require configure mode" in the Push Preset, and Unimus will make sure the device is in the specified mode before executing your commands. Modes available on devices are discovered during Discovery, using mode credentials configured in the "Credentials" screen. You can check which modes Unimus was able to discover on devices using the "Devices > Info" window.
If a device can not be switched into the specified CLI mode before, Config Push will NOT push the provided commands to the device, and any devices failing the mode switch will be grouped in appropriate "mode not supported" output groups.
Command sending modifiers and control sequences
How commands are sent to devices
Command parsing examples