Hi,
I've got another question regarding Custom Backup Flows. We have several Calix E-7 in our environment and want to fully backup them. So there is a driver available, but I also want to extract the local database via a Custom Backup Flow to a FTP Server. Is there a way to put any variables in the Backup Flow to differ them ? and to add a username / passwort combination ?
thank in advance
Christian
[Solved] Custom Backup Flows
Christian,
There currently isn't anything in Unimus that can be used for dynamically updating a filename (that I can think of). If the E-7s support some kind of variable/scripting inside of their CLI you could achieve your goals that way.
You can apply a variable to each of the E-7s that contains a password to obfuscate the username/password from the Mass Config Push menu. That said, you will need to apply the variables to each E-7 and anyone who has access to the E-7s in Unimus will be able to see those variables. (You could work around this a bit if you could place all of your E-7s into their own Zone which does currently support Variable Inheritance)
We are working on expanding the variable system. We are currently working on Dynamic Variables per device that will contain:
$[address]
$[description]
$[vendor]
$[type]
$[model]
$[timestamp-unix]
$[timestamp-iso]
As well as Variable inheritance from Tags which would greatly simplify the management of things like this.
There currently isn't anything in Unimus that can be used for dynamically updating a filename (that I can think of). If the E-7s support some kind of variable/scripting inside of their CLI you could achieve your goals that way.
You can apply a variable to each of the E-7s that contains a password to obfuscate the username/password from the Mass Config Push menu. That said, you will need to apply the variables to each E-7 and anyone who has access to the E-7s in Unimus will be able to see those variables. (You could work around this a bit if you could place all of your E-7s into their own Zone which does currently support Variable Inheritance)
We are working on expanding the variable system. We are currently working on Dynamic Variables per device that will contain:
$[address]
$[description]
$[vendor]
$[type]
$[model]
$[timestamp-unix]
$[timestamp-iso]
As well as Variable inheritance from Tags which would greatly simplify the management of things like this.
-
cschnappinger
- Posts: 10
- Joined: Thu Oct 30, 2025 2:55 pm
Hi Tommy,
is it possible to enter a password in a prompt ?
in that case, I could handle the backups via a config-push preset
thanks a lot
is it possible to enter a password in a prompt ?
in that case, I could handle the backups via a config-push preset
thanks a lot
Absolutely,
Whatever you have in Mass Config Push will be sent to the device. So you can have something like:
(Pseudo code)
save running-config to storage new-backup.bak
sftp [email protected] password=123abc send=new-backup.bak
This would allow you to have the device push it's backup (new-backup.bak) to the FTP server using router-backup as the username and 123abc as the password.
You could even automate this with a scheduled Mass Config Push if you wished.
That said, you still would have to have some way to create unique names for your backups. Either through your Calix E-7's scripting or you could have a separate script on the FTP server that checks the backup folder and renames the backups to be unique.
Whatever you have in Mass Config Push will be sent to the device. So you can have something like:
(Pseudo code)
save running-config to storage new-backup.bak
sftp [email protected] password=123abc send=new-backup.bak
This would allow you to have the device push it's backup (new-backup.bak) to the FTP server using router-backup as the username and 123abc as the password.
You could even automate this with a scheduled Mass Config Push if you wished.
That said, you still would have to have some way to create unique names for your backups. Either through your Calix E-7's scripting or you could have a separate script on the FTP server that checks the backup folder and renames the backups to be unique.
-
cschnappinger
- Posts: 10
- Joined: Thu Oct 30, 2025 2:55 pm
ja got you, but the password is requested after my backup command what looks like:
extract backup to-host 1.2.3.4 username backup directory /
then a prompt appears like
password:
I have to insert the password in the prompt
UPDATE... just adding the password in the next line works, sorry for any confusions and thanks a lot
extract backup to-host 1.2.3.4 username backup directory /
then a prompt appears like
password:
I have to insert the password in the prompt
UPDATE... just adding the password in the next line works, sorry for any confusions and thanks a lot
Hello,
maybe the problem is that the switch isn't discovered as a Calix E7-2 EXA. The switch is discovered as a E7 (2-Slot Chassis) what is basically right but in my opinion it makes a difference whether there is a EXA or a AXOS firmware inside. In my case there are two GE-24 EXA cards in the shelf.
I think that it wouldn't be that problem for you to automate the commands that cschnappinger metioned. It is clear that there can only full backup done, because you "can't look" in the database, whether there have been changes or not. I would make it then so that there are 3 files for each calix switch and if the version 4 is backuped then version 1 will be deleted. (I hope that I wrote it so that it is clear for you).
Best regards
Georg
maybe the problem is that the switch isn't discovered as a Calix E7-2 EXA. The switch is discovered as a E7 (2-Slot Chassis) what is basically right but in my opinion it makes a difference whether there is a EXA or a AXOS firmware inside. In my case there are two GE-24 EXA cards in the shelf.
I think that it wouldn't be that problem for you to automate the commands that cschnappinger metioned. It is clear that there can only full backup done, because you "can't look" in the database, whether there have been changes or not. I would make it then so that there are 3 files for each calix switch and if the version 4 is backuped then version 1 will be deleted. (I hope that I wrote it so that it is clear for you).
Best regards
Georg