Junos OS

Quite new to Junos and are setting up my first couple of QFX 5120 i virtual chassis setup.  Version 20.4R3.8 on both.
They will be upgraded later when I've done some basic configurations. 

Have separated traffic from management ports to the recomended mgmt_junos vrf and are trying to get backups to work, either with events or Archival functions. 

My problem is that the switches do not seem to use the vrf when trasfering the file.  I get the following errors in syslog when trying archival.

 SWITCH pfed: ACCT_TRANSFER_FILE_FAILED_ITER: Error <256> uploading file '/var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz'. Remaining retry attempts = 1, retry in 135 seconds..
SWITCH logger: transfer-file failed to transfer /var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz rc 1
SWITCH fetch: fetch-secure: ftp://juniper@10.10.10.1/SWITCH/SWITCH_20240822_060558_juniper.conf.gz: Can't assign requested address

Configuration for Archival is:
 show system archival 
configuration {
    transfer-interval 15;
    routing-instance mgmt_junos;
    archive-sites {
        "ftp://username@10.10.10.1/SWITCH" password "redacted"; ## SECRET-DATA
    }
}

I've also tried "transfer-on-commit" with the same errors.

Doing it manually from operational mode works. 

file copy /var/transfer/config/SWITCH_20240822_053328_juniper.conf.gz ftp://usernamer@10.10.10.1/SWITCH/ routing-instance mgmt_junos

Looking on the Filezilla logs on the server, I can't see any connection attemts on the failed connections, making me think that archival do not honour the "routing-instance mgmt_junos" statement. 

I'm also trying the same with event-options, but here I can't specify route-instance mgmt_junos for the destination. 
Same error in the logs.
SWITCH fetch: fetch-secure: ftp://juniper@10.10.189.207:*: Can't assign requested address

Any ideas where I can have gone wrong, or if this is a know problem? 

------------------------------
ANDREAS JANSSON
------------------------------

Hi Andreas,

Before conducting any further investigation, I recommend upgrading to version 23.4R2-S1 (the recommended release). Many bugs present in 20.4R3 have been resolved in newer releases.

Quite new to Junos and are setting up my first couple of QFX 5120 i virtual chassis setup.  Version 20.4R3.8 on both.
They will be upgraded later when I've done some basic configurations. 

Have separated traffic from management ports to the recomended mgmt_junos vrf and are trying to get backups to work, either with events or Archival functions. 

My problem is that the switches do not seem to use the vrf when trasfering the file.  I get the following errors in syslog when trying archival.

 SWITCH pfed: ACCT_TRANSFER_FILE_FAILED_ITER: Error <256> uploading file '/var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz'. Remaining retry attempts = 1, retry in 135 seconds..
SWITCH logger: transfer-file failed to transfer /var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz rc 1
SWITCH fetch: fetch-secure: ftp://juniper@10.10.10.1/SWITCH/SWITCH_20240822_060558_juniper.conf.gz: Can't assign requested address

Configuration for Archival is:
 show system archival 
configuration {
    transfer-interval 15;
    routing-instance mgmt_junos;
    archive-sites {
        "ftp://username@10.10.10.1/SWITCH" password "redacted"; ## SECRET-DATA
    }
}

I've also tried "transfer-on-commit" with the same errors.

Doing it manually from operational mode works. 

file copy /var/transfer/config/SWITCH_20240822_053328_juniper.conf.gz ftp://usernamer@10.10.10.1/SWITCH/ routing-instance mgmt_junos

Looking on the Filezilla logs on the server, I can't see any connection attemts on the failed connections, making me think that archival do not honour the "routing-instance mgmt_junos" statement. 

I'm also trying the same with event-options, but here I can't specify route-instance mgmt_junos for the destination. 
Same error in the logs.
SWITCH fetch: fetch-secure: ftp://juniper@10.10.189.207:*: Can't assign requested address

Any ideas where I can have gone wrong, or if this is a know problem? 

------------------------------
ANDREAS JANSSON
------------------------------

Hi Kalle,

Thank you. I'll wait with more troubleshooting until I've uppgraded the units. 

Wanted to upgrade as much as possible first to see the impact of an upgrade :)

Hi Andreas,

Before conducting any further investigation, I recommend upgrading to version 23.4R2-S1 (the recommended release). Many bugs present in 20.4R3 have been resolved in newer releases.

Quite new to Junos and are setting up my first couple of QFX 5120 i virtual chassis setup.  Version 20.4R3.8 on both.
They will be upgraded later when I've done some basic configurations. 

Have separated traffic from management ports to the recomended mgmt_junos vrf and are trying to get backups to work, either with events or Archival functions. 

My problem is that the switches do not seem to use the vrf when trasfering the file.  I get the following errors in syslog when trying archival.

 SWITCH pfed: ACCT_TRANSFER_FILE_FAILED_ITER: Error <256> uploading file '/var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz'. Remaining retry attempts = 1, retry in 135 seconds..
SWITCH logger: transfer-file failed to transfer /var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz rc 1
SWITCH fetch: fetch-secure: ftp://juniper@10.10.10.1/SWITCH/SWITCH_20240822_060558_juniper.conf.gz: Can't assign requested address

Configuration for Archival is:
 show system archival 
configuration {
    transfer-interval 15;
    routing-instance mgmt_junos;
    archive-sites {
        "ftp://username@10.10.10.1/SWITCH" password "redacted"; ## SECRET-DATA
    }
}

I've also tried "transfer-on-commit" with the same errors.

Doing it manually from operational mode works. 

file copy /var/transfer/config/SWITCH_20240822_053328_juniper.conf.gz ftp://usernamer@10.10.10.1/SWITCH/ routing-instance mgmt_junos

Looking on the Filezilla logs on the server, I can't see any connection attemts on the failed connections, making me think that archival do not honour the "routing-instance mgmt_junos" statement. 

I'm also trying the same with event-options, but here I can't specify route-instance mgmt_junos for the destination. 
Same error in the logs.
SWITCH fetch: fetch-secure: ftp://juniper@10.10.189.207:*: Can't assign requested address

Any ideas where I can have gone wrong, or if this is a know problem? 

------------------------------
ANDREAS JANSSON
------------------------------

Hello 

I don't know if an upgrade will help because I have the same problem on MX204 

Hi Kalle,

Thank you. I'll wait with more troubleshooting until I've uppgraded the units. 

Wanted to upgrade as much as possible first to see the impact of an upgrade :)

Hi Andreas,

Before conducting any further investigation, I recommend upgrading to version 23.4R2-S1 (the recommended release). Many bugs present in 20.4R3 have been resolved in newer releases.

Quite new to Junos and are setting up my first couple of QFX 5120 i virtual chassis setup.  Version 20.4R3.8 on both.
They will be upgraded later when I've done some basic configurations. 

Have separated traffic from management ports to the recomended mgmt_junos vrf and are trying to get backups to work, either with events or Archival functions. 

My problem is that the switches do not seem to use the vrf when trasfering the file.  I get the following errors in syslog when trying archival.

 SWITCH pfed: ACCT_TRANSFER_FILE_FAILED_ITER: Error <256> uploading file '/var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz'. Remaining retry attempts = 1, retry in 135 seconds..
SWITCH logger: transfer-file failed to transfer /var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz rc 1
SWITCH fetch: fetch-secure: ftp://juniper@10.10.10.1/SWITCH/SWITCH_20240822_060558_juniper.conf.gz: Can't assign requested address

Configuration for Archival is:
 show system archival 
configuration {
    transfer-interval 15;
    routing-instance mgmt_junos;
    archive-sites {
        "ftp://username@10.10.10.1/SWITCH" password "redacted"; ## SECRET-DATA
    }
}

I've also tried "transfer-on-commit" with the same errors.

Doing it manually from operational mode works. 

file copy /var/transfer/config/SWITCH_20240822_053328_juniper.conf.gz ftp://usernamer@10.10.10.1/SWITCH/ routing-instance mgmt_junos

Looking on the Filezilla logs on the server, I can't see any connection attemts on the failed connections, making me think that archival do not honour the "routing-instance mgmt_junos" statement. 

I'm also trying the same with event-options, but here I can't specify route-instance mgmt_junos for the destination. 
Same error in the logs.
SWITCH fetch: fetch-secure: ftp://juniper@10.10.189.207:*: Can't assign requested address

Any ideas where I can have gone wrong, or if this is a know problem? 

------------------------------
ANDREAS JANSSON
------------------------------

Quite new to Junos and are setting up my first couple of QFX 5120 i virtual chassis setup.  Version 20.4R3.8 on both.
They will be upgraded later when I've done some basic configurations. 

Have separated traffic from management ports to the recomended mgmt_junos vrf and are trying to get backups to work, either with events or Archival functions. 

My problem is that the switches do not seem to use the vrf when trasfering the file.  I get the following errors in syslog when trying archival.

 SWITCH pfed: ACCT_TRANSFER_FILE_FAILED_ITER: Error <256> uploading file '/var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz'. Remaining retry attempts = 1, retry in 135 seconds..
SWITCH logger: transfer-file failed to transfer /var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz rc 1
SWITCH fetch: fetch-secure: ftp://juniper@10.10.10.1/SWITCH/SWITCH_20240822_060558_juniper.conf.gz: Can't assign requested address

Configuration for Archival is:
 show system archival 
configuration {
    transfer-interval 15;
    routing-instance mgmt_junos;
    archive-sites {
        "ftp://username@10.10.10.1/SWITCH" password "redacted"; ## SECRET-DATA
    }
}

I've also tried "transfer-on-commit" with the same errors.

Doing it manually from operational mode works. 

file copy /var/transfer/config/SWITCH_20240822_053328_juniper.conf.gz ftp://usernamer@10.10.10.1/SWITCH/ routing-instance mgmt_junos

Looking on the Filezilla logs on the server, I can't see any connection attemts on the failed connections, making me think that archival do not honour the "routing-instance mgmt_junos" statement. 

I'm also trying the same with event-options, but here I can't specify route-instance mgmt_junos for the destination. 
Same error in the logs.
SWITCH fetch: fetch-secure: ftp://juniper@10.10.189.207:*: Can't assign requested address

Any ideas where I can have gone wrong, or if this is a know problem? 

------------------------------
ANDREAS JANSSON
------------------------------

Quite new to Junos and are setting up my first couple of QFX 5120 i virtual chassis setup.  Version 20.4R3.8 on both.
They will be upgraded later when I've done some basic configurations. 

Have separated traffic from management ports to the recomended mgmt_junos vrf and are trying to get backups to work, either with events or Archival functions. 

My problem is that the switches do not seem to use the vrf when trasfering the file.  I get the following errors in syslog when trying archival.

 SWITCH pfed: ACCT_TRANSFER_FILE_FAILED_ITER: Error <256> uploading file '/var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz'. Remaining retry attempts = 1, retry in 135 seconds..
SWITCH logger: transfer-file failed to transfer /var/transfer/config/SWITCH_20240822_060558_juniper.conf.gz rc 1
SWITCH fetch: fetch-secure: ftp://juniper@10.10.10.1/SWITCH/SWITCH_20240822_060558_juniper.conf.gz: Can't assign requested address

Configuration for Archival is:
 show system archival 
configuration {
    transfer-interval 15;
    routing-instance mgmt_junos;
    archive-sites {
        "ftp://username@10.10.10.1/SWITCH" password "redacted"; ## SECRET-DATA
    }
}

I've also tried "transfer-on-commit" with the same errors.

Doing it manually from operational mode works. 

file copy /var/transfer/config/SWITCH_20240822_053328_juniper.conf.gz ftp://usernamer@10.10.10.1/SWITCH/ routing-instance mgmt_junos

Looking on the Filezilla logs on the server, I can't see any connection attemts on the failed connections, making me think that archival do not honour the "routing-instance mgmt_junos" statement. 

I'm also trying the same with event-options, but here I can't specify route-instance mgmt_junos for the destination. 
Same error in the logs.
SWITCH fetch: fetch-secure: ftp://juniper@10.10.189.207:*: Can't assign requested address

Any ideas where I can have gone wrong, or if this is a know problem? 

------------------------------
ANDREAS JANSSON
------------------------------