In an Virtual-chassis setup, when the devices are configured with statements "set chassis redundancy routing-engine master" and "set chassis redundancy routing-engine backup", the configuration does not take effect on the Virtual-chassis
The below configuration when set on Virtual chassis , it doesn’t take effect ,
set chassis redundancy routing-engine 0 backupset chassis redundancy routing-engine 1 master
Below are the test scenarios conducted to confirm this on a 2 member VC and a standalone box with dual Routing Engine
>>The below configuration is added on VC where customer was expecting FPC1 to be master and FPC0 to be backup
labroot@jtac-qfx5110-48s-4c-r2072> show configuration chassis |display set
set chassis redundancy routing-engine 0 backup
set chassis redundancy routing-engine 1 master
set chassis redundancy graceful-switchover
>>However when we see the behaviour on VC , we always see FPC0 comes as master and FPC1 as back even after reboot of the VC
labroot@jtac-qfx5110-48s-4c-r2072> show chassis routing-engine | no-more
Routing Engine status:
Slot 0:
Current state Master
Temperature 40 degrees C / 104 degrees F
CPU temperature 40 degrees C / 104 degrees F
DRAM 3863 MB (4096 MB installed)
Memory utilization 15 percent
5 sec CPU utilization:
User 1 percent
Background 0 percent
Kernel 2 percent
Interrupt 0 percent
Idle 97 percent
1 min CPU utilization:
Kernel 1 percent
Idle 98 percent
5 min CPU utilization:
15 min CPU utilization:
Model RE-QFX5110-48S-4C
Serial ID BUILTIN
Start time 2024-03-14 14:25:25 IST
Uptime 2 days, 7 hours, 59 minutes, 37 seconds
Last reboot reason 0x4000:VJUNOS reboot
Load averages: 1 minute 5 minute 15 minute
0.37 0.29 0.26
Slot 1:
Current state Backup
DRAM 3862 MB
Memory utilization 13 percent
User 0 percent
Start time 2024-03-14 14:25:11 IST
Uptime 2 days, 7 hours, 59 minutes, 51 seconds
0.08 0.11 0.13
>>Even though the FPC0 is master , we do not see any alarms set on the device . I.e "Backup RE active" is not seen on the VC even with configuration mentioned above
>>No Back UP RE active alarm seen on the VC setup
{master:0}
labroot@jtac-qfx5110-48s-4c-r2072> show chassis alarms
2 alarms currently active
Alarm time Class Description
2024-03-14 14:27:44 IST Major FPC Management1 Ethernet Link Down
2024-03-14 14:27:24 IST Major FPC1: PEM 1 Not Powered
labroot@jtac-qfx5110-48s-4c-r2072> show virtual-chassis status
Preprovisioned Virtual Chassis
Virtual Chassis ID: c904.7bc1.47e1Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID Interface
0 (FPC 0) Prsnt WS3720290028 qfx5110-48s-4c 129 Master* N VC 1 vcp-255/0/48
1 vcp-255/0/49
1 (FPC 1) Prsnt WS3720290213 qfx5110-48s-4c 129 Backup N VC 0 vcp-255/0/48
VC configs:
labroot@jtac-qfx5110-48s-4c-r2072> show configuration virtual-chassis | display set
set virtual-chassis preprovisioned
set virtual-chassis member 0 role routing-engine
set virtual-chassis member 0 serial-number WS3720290028
set virtual-chassis member 1 role routing-engine
set virtual-chassis member 1 serial-number WS3720290213
>>This is persistent across reboots .
On Dual RE modular QFX10008 device, the same configuration has be set .
labroot@jtac-qfx10008-r2003-re1> show version invoke-on all-routing-engines | match "Junos:"Junos: 22.4R2-S2.6
Junos: 22.4R2-S2.6
>>Once the device is rebooted after the configs are set , the device will come up with RE1 being master and RE0 being back as configured under chassis hierarchy
labroot@jtac-qfx10008-r2003-re1> show configuration chassis | display set
labroot@jtac-qfx10008-r2003-re1> show chassis routing-engine
Temperature 39 degrees C / 102 degrees F
DRAM 11667 MB (12288 MB installed)
Memory utilization 8 percent
Idle 99 percent
Model RE-QFX10008
Serial ID ACPD7517
Start time 2024-03-16 11:04:47 IST
Uptime 11 hours, 36 minutes, 40 seconds
0.24 0.18 0.16
Temperature 35 degrees C / 95 degrees F
Memory utilization 6 percent
Serial ID ACNV4577
Start time 2024-03-16 08:49:37 IST
Uptime 13 hours, 51 minutes, 58 seconds
Last reboot reason 0x2000:hypervisor reboot
0.43 0.32 0.26
>>If we switchover the mastership and make RE0 as master, we see the alarm being set for “Backup RE” Active.
labroot@jtac-qfx10008-r2003-re1> request chassis routing-engine master switch
Toggle mastership between routing engines ? [yes,no] (no) yes
After toggling mastership ,
labroot@jtac-qfx10008-r2003-re0> show chassis alarms
14 alarms currently active
2024-03-16 22:44:32 IST Minor Backup RE Active
labroot@jtac-qfx10008-r2003-re0> show chassis routing-engine
Temperature 38 degrees C / 100 degrees F
Memory utilization 10 percent
Uptime 11 hours, 41 minutes, 30 seconds
0.52 0.42 0.27
Temperature 33 degrees C / 91 degrees F
Memory utilization 7 percent
Uptime 13 hours, 56 minutes, 25 seconds
0.16 0.24 0.24
Conclusion :
Based on the tests carried out we see the configuration "set chassis redundancy routing-engine 0 backup/Master" will not take effect on Virtual-chassis and these configuration can be only can applied on devices where we have Dual Routing Engines.