Configuration archival using host n routing-instance

Hi.

I have two ex4600 that are running 18.4R3-S3 and I have activated the management routing-instance mgmt_junos.

I have got it to work with RADIUS and SNMP without any issues, but when I'm trying to add archival of configuration using "transfer-on-commit" I draw a blank.

There is a command that seemd to be promising:

But this seems to have no affect.

When ever I try to add the archival site the following command:

I get the following error message: "ssh: connect to host 172.xxx.xxx.xxx port 22: No route to host".

I'm able to ping the SCP server using "ping 172.xxx.xxx.xxx routing-instance mgmt_junos", so the routing is working as expected.

Have someone managed to get this to work?

Best regards,

Johan Christensson