2020-09-18 09:00:27 +00:00
|
|
|
#!rsc by RouterOS
|
2019-01-02 21:27:31 +00:00
|
|
|
# RouterOS script: unattended-lte-firmware-upgrade
|
2022-01-01 20:38:15 +00:00
|
|
|
# Copyright (c) 2018-2022 Christian Hesse <mail@eworm.de>
|
2020-06-19 20:17:42 +00:00
|
|
|
# https://git.eworm.de/cgit/routeros-scripts/about/COPYING.md
|
2019-01-02 21:27:31 +00:00
|
|
|
#
|
|
|
|
|
# schedule unattended lte firmware upgrade
|
2020-03-27 20:51:21 +00:00
|
|
|
# https://git.eworm.de/cgit/routeros-scripts/about/doc/unattended-lte-firmware-upgrade.md
|
2019-01-02 21:27:31 +00:00
|
|
|
|
2022-05-10 13:17:17 +00:00
|
|
|
:foreach Interface in=[ /interface/lte/find where running ] do={
|
global: variable names are CamelCase
___ _ ___ __
/ _ )(_)__ _ / _/__ _/ /_
/ _ / / _ `/ / _/ _ `/ __/
/____/_/\_, / /_/ \_,_/\__/
_ __ /___/ _ __
| | / /___ __________ (_)___ ____ _/ /
| | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ /
| |/ |/ / /_/ / / / / / / / / / / /_/ /_/
|__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_)
/____/
RouterOS has some odd behavior when it comes to variable names. Let's
have a look at the interfaces:
[admin@MikroTik] > / interface print where name=en1
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
0 RS en1 ether 1500 1598
That looks ok. Now we use a script:
{ :local interface "en1";
/ interface print where name=$interface; }
And the result...
[admin@MikroTik] > { :local interface "en1";
{... / interface print where name=$interface; }
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
0 RS en1 ether 1500 1598
... still looks ok.
We make a little modification to the script:
{ :local name "en1";
/ interface print where name=$name; }
And the result:
[admin@MikroTik] > { :local name "en1";
{... / interface print where name=$name; }
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
0 RS en1 ether 1500 1598
1 S en2 ether 1500 1598
2 S en3 ether 1500 1598
3 S en4 ether 1500 1598
4 S en5 ether 1500 1598
5 R br-local bridge 1500 1598
Ups! The filter has no effect!
That happens whenever the variable name ($name) matches the property
name (name=).
And another modification:
{ :local type "en1";
/ interface print where name=$type; }
And the result:
[admin@MikroTik] > { :local type "en1";
{... / interface print where name=$type; }
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
Ups! Nothing?
Even if the variable name ($type) matches whatever property name (type=)
things go wrong.
The answer from MikroTik support (in Ticket#2019010222000454):
> This is how scripting works in RouterOS and we will not fix it.
To get around this we use variable names in CamelCase. Let's hope
Mikrotik never ever introduces property names in CamelCase...
*fingers crossed*
2019-01-03 16:45:43 +00:00
|
|
|
:local Firmware;
|
2022-05-10 13:17:17 +00:00
|
|
|
:local IntName [ /interface/lte/get $Interface name ];
|
2019-02-11 14:15:21 +00:00
|
|
|
:do {
|
2022-05-10 13:17:17 +00:00
|
|
|
:set Firmware [ /interface/lte/firmware-upgrade $Interface once as-value ];
|
2019-01-02 21:27:31 +00:00
|
|
|
} on-error={
|
global: variable names are CamelCase
___ _ ___ __
/ _ )(_)__ _ / _/__ _/ /_
/ _ / / _ `/ / _/ _ `/ __/
/____/_/\_, / /_/ \_,_/\__/
_ __ /___/ _ __
| | / /___ __________ (_)___ ____ _/ /
| | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ /
| |/ |/ / /_/ / / / / / / / / / / /_/ /_/
|__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_)
/____/
RouterOS has some odd behavior when it comes to variable names. Let's
have a look at the interfaces:
[admin@MikroTik] > / interface print where name=en1
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
0 RS en1 ether 1500 1598
That looks ok. Now we use a script:
{ :local interface "en1";
/ interface print where name=$interface; }
And the result...
[admin@MikroTik] > { :local interface "en1";
{... / interface print where name=$interface; }
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
0 RS en1 ether 1500 1598
... still looks ok.
We make a little modification to the script:
{ :local name "en1";
/ interface print where name=$name; }
And the result:
[admin@MikroTik] > { :local name "en1";
{... / interface print where name=$name; }
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
0 RS en1 ether 1500 1598
1 S en2 ether 1500 1598
2 S en3 ether 1500 1598
3 S en4 ether 1500 1598
4 S en5 ether 1500 1598
5 R br-local bridge 1500 1598
Ups! The filter has no effect!
That happens whenever the variable name ($name) matches the property
name (name=).
And another modification:
{ :local type "en1";
/ interface print where name=$type; }
And the result:
[admin@MikroTik] > { :local type "en1";
{... / interface print where name=$type; }
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
Ups! Nothing?
Even if the variable name ($type) matches whatever property name (type=)
things go wrong.
The answer from MikroTik support (in Ticket#2019010222000454):
> This is how scripting works in RouterOS and we will not fix it.
To get around this we use variable names in CamelCase. Let's hope
Mikrotik never ever introduces property names in CamelCase...
*fingers crossed*
2019-01-03 16:45:43 +00:00
|
|
|
:log debug ("Could not get latest LTE firmware version for interface " . $IntName . ".");
|
2019-01-02 21:27:31 +00:00
|
|
|
}
|
|
|
|
|
|
2021-02-26 11:21:38 +00:00
|
|
|
:if ([ :typeof $Firmware ] = "array") do={
|
|
|
|
|
:if (($Firmware->"installed") != ($Firmware->"latest")) do={
|
|
|
|
|
:log info ("Scheduling LTE firmware upgrade for interface " . $IntName . ".");
|
2022-08-03 22:41:16 +00:00
|
|
|
|
2021-02-26 11:21:38 +00:00
|
|
|
:global LTEFirmwareUpgrade do={
|
|
|
|
|
:global LTEFirmwareUpgrade;
|
|
|
|
|
:set LTEFirmwareUpgrade;
|
2022-08-03 22:41:16 +00:00
|
|
|
|
2022-05-10 13:17:17 +00:00
|
|
|
/system/scheduler/remove ($1 . "-firmware-upgrade");
|
|
|
|
|
/interface/lte/firmware-upgrade $1 upgrade=yes;
|
2022-08-03 22:41:16 +00:00
|
|
|
:log info ("LTE firmware upgrade on '" . $1 . "' finished, waiting for reset.");
|
2022-09-21 14:36:54 +00:00
|
|
|
:delay 240s;
|
2022-08-03 22:41:16 +00:00
|
|
|
:local Firmware [ /interface/lte/firmware-upgrade $1 once as-value ];
|
|
|
|
|
:if (($Firmware->"installed") != ($Firmware->"latest")) do={
|
|
|
|
|
:log warning ("LTE firmware versions still differ. Resetting again...");
|
|
|
|
|
/interface/lte/at-chat $1 input="AT+RESET";
|
|
|
|
|
}
|
2021-02-26 11:21:38 +00:00
|
|
|
}
|
2022-08-03 22:41:16 +00:00
|
|
|
|
2022-05-10 13:17:17 +00:00
|
|
|
/system/scheduler/add name=($IntName . "-firmware-upgrade") start-time=startup interval=2s \
|
2021-02-26 11:21:38 +00:00
|
|
|
on-event=(":global LTEFirmwareUpgrade; \$LTEFirmwareUpgrade \"" . $IntName . "\";");
|
|
|
|
|
} else={
|
|
|
|
|
:log info ("The LTE firmware is up to date on interface " . $IntName . ".");
|
2020-10-13 16:52:01 +00:00
|
|
|
}
|
2021-02-26 10:58:28 +00:00
|
|
|
} else={
|
2021-02-26 11:21:38 +00:00
|
|
|
:log info ("No LTE firmware information available for interface " . $IntName . ".");
|
2019-01-02 21:27:31 +00:00
|
|
|
}
|
|
|
|
|
}
|