Using the same router/config I noted previously, I see an "empty" config per T6084.

admin@removed# cat /run/opennhrp/opennhrp.conf
# Created by VyOS - manual changes will be overwritten

I then modified the nhrp vyos config and saved, and the opennhrp.conf was re-populated. Upon reboot, the file reverted to "empty".

Instead of that sysrq stuff, how does it work if you try these 3 tests?

If I comment out this line then everything works.

Thanks - yes - there were in fact 3 "passive-interface" entries for old interfaces, which I should have tidied. Having deleted them, the migration completed.

Check opennhrp.conf file
Could be bug if the ispec in the config T6084

https://github.com/vyos/vyos-1x/pull/3073

@fernando I think you mixed up ospf vs ospfv3.

Still broken in 1.4.0-epa1 (self-built).

If the peer reconnects after the first disconnect - does the local VTI interface go "UP" again?

https://github.com/vyos/vyos-1x/pull/3072

The motivation here was from T5660, for which it was not needed. However, a version of the constructions in the branch above will be useful for development of the modern commit algorithm and comparison with the idiosyncrasies of legacy (T5492). Put on hold for now.

PR https://github.com/vyos/vyos-1x/pull/2157 closed due to long standing conflicting files.

PR: https://github.com/vyos/vyos-1x/pull/3068

You don't have eth0.150

is it possible to extend this feature to json api of vyos?

Rebooting the failed image (I did not redo the upgrade - the failed image remained on the router) produces:-

itconsult@ha-r02a:~$ cat /tmp/vyos-configd-script-stdout

https://github.com/vyos/vyos-1x/pull/3066