This article explains how to use the function, 'configuration transfer-on-commit' on a non-default VR.

When using this function, the configuration is sent to the FTP server at every commit.

Topology:

SRX(blue-vr:ge-0/0/3:10.75.252.105)-----WAN-----(10.141.25.62)FTP Server

Configuration:

set system archival configuration transfer-on-commit
set system archival configuration archive-sites "ftp://root:[email protected]"​

set routing-options interface-routes rib-group inet test
set routing-options static rib-group test
set routing-options static route 0.0.0.0/0 next-hop 10.75.252.251
set routing-options rib-groups test import-rib inet.0
set routing-options rib-groups test import-rib blue-vr.inet.0
set routing-instances blue-vr instance-type virtual-router
set routing-instances blue-vr interface ge-0/0/3.0
set routing-instances blue-vr routing-options interface-routes rib-group inet test​

This function selects the IP address in default zone automatically to send the packet, which causes traffic failure. We need to change the IP address in default zone to the IP address in VR zone, which is connected to the FTP server.

Add Source NAT from junos-host to the VR interface zone

set security nat source rule-set r1 from zone junos-host
set security nat source rule-set r1 to zone blue-trust
set security nat source rule-set r1 rule r1 match destination-address 10.141.25.62/32
set security nat source rule-set r1 rule r1 match application junos-ftp
set security nat source rule-set r1 rule r1 then source-nat interface

• transfer-on-commit