[EX/QFX] Commit warning generated in virtual chassis

Summary:

A commit warning is generated in the virtual chassis in EX4300, EX4600, and QFX5100 devices.

warning: rcp failed(Unknown error: 0)
warning: srcpath=node0:/config/juniper.conf+.gz destpath=/var/tmp/juniper.conf+.gz mgmt_peer_name=<unknown>
warning: pull configuration failed, fallback to push configuration method

This article explains how to work around the issue.

Cause:

This issue may be related to [irsd- dcd - bme] ARP programming. Under a problematic scenario, there are no ARP entries for 128.0.0.5 and 128.0.0.6 on the primary.

The command that is issued during a commit is a pull_af from backup.

/bin/rcp -l -Ji -p fpc1:/config/juniper.conf+.gz /var/tmp/juniper.conf+.gz

This becomes stalled because there is no ARP entry on the primary.

Solution:

Restart the irsd process on the primary.

root@QFX5100-VC# run show virtual-chassis
Preprovisioned Virtual Chassis
Virtual Chassis ID: 1f6e.b031.0b41
Virtual Chassis Mode: Enabled
                                                Mstr           Mixed Route Neighbor List
Member ID  Status   Serial No    Model          prio  Role      Mode  Mode ID  Interface
0 (FPC 0)  Prsnt    TA3715260057 qfx5100-48s-6q 129   Master*      N  VC   1  vcp-255/0/24
                                                                           1  vcp-255/0/25
1 (FPC 1)  Prsnt    VB3715410107 qfx5100-96s-8q 129   Backup       N  VC   0  vcp-255/0/94

```
vcp-255/0/95
```

root@QFX5100-VC# run show arp no-resolve
MAC Address       Address         Interface         Flags
02:00:00:00:00:0b 128.0.0.5       bme0.0                   permanent
02:00:00:00:00:0b 128.0.0.6       bme0.0                   permanent
02:00:00:00:00:0b 128.0.0.17      bme0.0                   permanent

root@QFX5100-VC# run show system processes extensive | match irsd
1621 root        1  96    0  5440K  3288K select   0:02  0.00% irsd

root@QFX5100-VC:RE:0% kill -9 1621

Modification History:

2020-08-12: Article reviewed for accuracy; no changes required; article valid and relevant
2021-03-25: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives.

Knowledge Base