[Fixed in 2.0.3] updating banner MOTD
Hi,
Can you please collect debug logs for the failed push?
Please enabled both "Debug logging" and "Device output logging" in "Zones > Your Zone > Debug Mode".
Re-run the push job, and after it fails, please download both log files.
Please create a ticket on our Portal with the logs, and we will be happy to investigate why the push failed.
Thanks in advance!
Can you please collect debug logs for the failed push?
Please enabled both "Debug logging" and "Device output logging" in "Zones > Your Zone > Debug Mode".
Re-run the push job, and after it fails, please download both log files.
Please create a ticket on our Portal with the logs, and we will be happy to investigate why the push failed.
Thanks in advance!
Just an update on this issue:
When doing "banner motd ^" on Cisco / Aruba, the problem is that the device doesn't output anything and just waits for you to send the lines that should be the new banner. This is problematic with Unimus, since Unimus expects the device to output some know output (like a prompt) after each sent line. This is documented here: Config Push - How commands are sent to devices
We have added a new modifier to Config Push to support this: "$[no-wait]". Documentation:
Config Push - Command sending modifiers and control sequences
I have also added an example to the Wiki of how to edit MOTD on devices:
Config Push - Command parsing examples
This new modifier will be available starting with 2.0.3-Beta3, including after 2.0.3 is released into the Stable release channel.
When doing "banner motd ^" on Cisco / Aruba, the problem is that the device doesn't output anything and just waits for you to send the lines that should be the new banner. This is problematic with Unimus, since Unimus expects the device to output some know output (like a prompt) after each sent line. This is documented here: Config Push - How commands are sent to devices
We have added a new modifier to Config Push to support this: "$[no-wait]". Documentation:
Config Push - Command sending modifiers and control sequences
I have also added an example to the Wiki of how to edit MOTD on devices:
Config Push - Command parsing examples
This new modifier will be available starting with 2.0.3-Beta3, including after 2.0.3 is released into the Stable release channel.