Wired Intelligent Edge

Hello everyone,

is it possible to allow unsafe updates via API?

Couldn't find anything in the documentation so far.

Hello everyone,

is it possible to allow unsafe updates via API?

Couldn't find anything in the documentation so far.

I have a Expect script which may be used during staging. 

As you can see it is a reboot after enable the allow-unsafe-updates. I use it as part of ZTP so new firmware is automaticly downloaded and I need to reboot with allow-unsafe-updates if needed.

If you want to use this as part of a upgrade of switches in production, remove the reboot. And perform the firmware upgrade using your standard tools.

#!/usr/bin/expect#Usage  allow-unsafe-upgrade.expect <host> <ssh user> <ssh password>set timeout 60spawn ssh [lindex $argv 1]@[lindex $argv 0]expect "yes/no" {        send "yes\r"        expect "*?assword" { send "[lindex $argv 2]\r" }        } "*?assword" { send "[lindex $argv 2]\r" }expect "# " { send "configure\r" }expect "fig)# " { send "allow-unsafe-updates 20\r" }expect "(y/n)? " { send "y\r" }expect "fig)# " { send "boot system\r" }expect "(y/n)? " {        send "y\r"        expect "(y/n)? " { send "y\r" }        } "(y/n)? " { send "y\r" }expect eof

Hello everyone,

is it possible to allow unsafe updates via API?

Couldn't find anything in the documentation so far.

I have a Expect script which may be used during staging. 

As you can see it is a reboot after enable the allow-unsafe-updates. I use it as part of ZTP so new firmware is automaticly downloaded and I need to reboot with allow-unsafe-updates if needed.

If you want to use this as part of a upgrade of switches in production, remove the reboot. And perform the firmware upgrade using your standard tools.

#!/usr/bin/expect#Usage  allow-unsafe-upgrade.expect <host> <ssh user> <ssh password>set timeout 60spawn ssh [lindex $argv 1]@[lindex $argv 0]expect "yes/no" {        send "yes\r"        expect "*?assword" { send "[lindex $argv 2]\r" }        } "*?assword" { send "[lindex $argv 2]\r" }expect "# " { send "configure\r" }expect "fig)# " { send "allow-unsafe-updates 20\r" }expect "(y/n)? " { send "y\r" }expect "fig)# " { send "boot system\r" }expect "(y/n)? " {        send "y\r"        expect "(y/n)? " { send "y\r" }        } "(y/n)? " { send "y\r" }expect eof

Hello everyone,

is it possible to allow unsafe updates via API?

Couldn't find anything in the documentation so far.

Thanks Arne for the script, that looks like a good workaround.

But my understanding is that the AOS-CX operating system is a fully API featured one, isn't it?

Then it should also be possible to implement this function on the API.

@jonlar, @ArneO: Have you already contacted TAC support about this?

Otherwise I will create a request for this.

I have a Expect script which may be used during staging. 

As you can see it is a reboot after enable the allow-unsafe-updates. I use it as part of ZTP so new firmware is automaticly downloaded and I need to reboot with allow-unsafe-updates if needed.

If you want to use this as part of a upgrade of switches in production, remove the reboot. And perform the firmware upgrade using your standard tools.

#!/usr/bin/expect#Usage  allow-unsafe-upgrade.expect <host> <ssh user> <ssh password>set timeout 60spawn ssh [lindex $argv 1]@[lindex $argv 0]expect "yes/no" {        send "yes\r"        expect "*?assword" { send "[lindex $argv 2]\r" }        } "*?assword" { send "[lindex $argv 2]\r" }expect "# " { send "configure\r" }expect "fig)# " { send "allow-unsafe-updates 20\r" }expect "(y/n)? " { send "y\r" }expect "fig)# " { send "boot system\r" }expect "(y/n)? " {        send "y\r"        expect "(y/n)? " { send "y\r" }        } "(y/n)? " { send "y\r" }expect eof

Hello everyone,

is it possible to allow unsafe updates via API?

Couldn't find anything in the documentation so far.

I know other stuff that doesn't work with the API as well, so they probably have a feature backlog with the API. 

I have not contacted TAC.

Original Message:
Sent: Feb 23, 2024 08:41 AM
From: robin.reinhardt
Subject: AOS-CX allow-unsafe-updates via REST API?

Thanks Arne for the script, that looks like a good workaround.

But my understanding is that the AOS-CX operating system is a fully API featured one, isn't it?

Then it should also be possible to implement this function on the API.

@jonlar, @ArneO: Have you already contacted TAC support about this?

Otherwise I will create a request for this.

Original Message:
Sent: Feb 17, 2024 05:53 AM
From: ArneO
Subject: AOS-CX allow-unsafe-updates via REST API?

I have a Expect script which may be used during staging. 

As you can see it is a reboot after enable the allow-unsafe-updates. I use it as part of ZTP so new firmware is automaticly downloaded and I need to reboot with allow-unsafe-updates if needed.

If you want to use this as part of a upgrade of switches in production, remove the reboot. And perform the firmware upgrade using your standard tools.

#!/usr/bin/expect#Usage  allow-unsafe-upgrade.expect <host> <ssh user> <ssh password>set timeout 60spawn ssh [lindex $argv 1]@[lindex $argv 0]expect "yes/no" {        send "yes\r"        expect "*?assword" { send "[lindex $argv 2]\r" }        } "*?assword" { send "[lindex $argv 2]\r" }expect "# " { send "configure\r" }expect "fig)# " { send "allow-unsafe-updates 20\r" }expect "(y/n)? " { send "y\r" }expect "fig)# " { send "boot system\r" }expect "(y/n)? " {        send "y\r"        expect "(y/n)? " { send "y\r" }        } "(y/n)? " { send "y\r" }expect eof

------------------------------
Arne Opdal

Original Message:
Sent: Dec 13, 2023 01:51 PM
From: robin.reinhardt
Subject: AOS-CX allow-unsafe-updates via REST API?

Hello everyone,

is it possible to allow unsafe updates via API?

Couldn't find anything in the documentation so far.