I’m facing an issue when using Unimus for a Mass Config Push on Aruba switches (ArubaOS-CX). During an SCP transfer, the process requires multiple manual confirmations, which interrupts the automation workflow.
Here’s an example of the SCP command:
copy scp://<username>@<hostname>/path/to/image.swi primary
The primary image will be deleted.
Continue (y/n)? y
The authenticity of host '<hostname> (<IP>)' can't be established.
RSA key fingerprint is SHA256:<fingerprint>.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])?
The first "yes" (to confirm deleting the primary image) can be automated using the auto-answer feature on the switch.
However, the second "yes" (to confirm the fingerprint) is not accepted by Unimus. After this step, the process also requires manual entry of the SCP user password.
Questions:
Is there a way to automate the SSH fingerprint confirmation during an SCP push via Unimus?
Can the SCP user password be passed automatically within the Unimus workflow or using any workaround?
If anyone has faced similar challenges with SCP transfers in Unimus or Aruba switches, I’d appreciate your insights or solutions!
Thank you in advance!
Unimus Mass Config Push – Automating SCP Confirmation and Password Entry
Hello
yes there is possibility to automate confirmation in Unimus. Below is example for HP ProCurve 2650 fw upgrade:
copy tftp flash 10.9.21.222 H_10_117.swi primary[/b]
#copy file from tftp server to primary flash memory of device
y$(wait-echo no)
#Unimus will response “y” to confirmation request from device and will not wait for echo from device
boot system flash primary
#reboot device with new firmware – file in primary memory
y
#Unimus response “y” to confirmation request from device
y$(wait-reply no)
#Unimus response “y” to confirmation request from device and will not wait any reply (because device is rebooted and connection will be lost)
You can find information about Unimus variable here: https://wiki.unimus.net/display/UNPUB/Mass+Config+Push
yes there is possibility to automate confirmation in Unimus. Below is example for HP ProCurve 2650 fw upgrade:
copy tftp flash 10.9.21.222 H_10_117.swi primary[/b]
#copy file from tftp server to primary flash memory of device
y$(wait-echo no)
#Unimus will response “y” to confirmation request from device and will not wait for echo from device
boot system flash primary
#reboot device with new firmware – file in primary memory
y
#Unimus response “y” to confirmation request from device
y$(wait-reply no)
#Unimus response “y” to confirmation request from device and will not wait any reply (because device is rebooted and connection will be lost)
You can find information about Unimus variable here: https://wiki.unimus.net/display/UNPUB/Mass+Config+Push