Hi
Actually, archival in mgmt_junos works using SCP but there's a quirk you need to work around.
There's no need to leak em0 from mgmt_junos to inet.0.
Config:
set system archival configuration transfer-on-commit
set system archival configuration routing-instance mgmt_junos
set system archival configuration archive-sites scp://
user@172.30.101.12:/home/user password <password>
When you add the last line, Junos will try and connect to the host to accept the SSH key, this will fail with no route to host.
If you manually add the ssh host key it will work just fine.
set security ssh-known-hosts host 172.30.101.12 <host-key-type> <host-key>
One comment as you're running MC-LAG, backup-liveness-detection via OOB doesn't work with mgmt_junos, for that use case you need to leak interface-routes from mgmt_junos to inet.0 for it to work.
Regards
Roger
------------------------------
ROGER WIKLUND
------------------------------
Original Message:
Sent: 10-07-2020 01:56
From: Unknown User
Subject: Re: Configuration archival using host n routing-instance
Thanks for the quick reply.
So, the setting "system archive configuration routing-instance" basically doesn't so anything then?
So what would be my best strategy here? The reason I activated the "management-instance" was because I have these two switches setup in a MC-LAG using the vlan approach, and I wanted to separate the management from the ICL/ICCP traffic.
Should I have gone the other way around instead? Put the ICL/ICCP in a separate routing-instance, or maybe better yet, put each of them in their own routing-instance?
Best regards,
Johan Christensson