Hi Deepak,
You have defined same priority values on both master and backup.
May be your backup device has become master . To validate just provide following information.
>show virtual-chassis status
>show virtual-chassis vc-port
To switchover the mastership you can use the following command.
>request chassis routing-engine master switch
Make sure you have backup configuration before applying above command.
Best Regards,
naveen
------------------------------
NAVEEN M
------------------------------
Original Message:
Sent: 08-23-2023 17:06
From: Unknown User
Subject: Question on Virtual Chassis
Hi
When I create a virtual chassis, why does my login session go the the backup RE?
I am configuring a virtual chassis with 2 EX4300s.
I have converted 2 uplink ports of both switches into vc ports.
Now, on EX1 I enable the new VC ports:
request virtual-chassis vc-port set interface vcp-255/1/0 member 0
request virtual-chassis vc-port set interface vcp-255/1/1 member 0
I then commit the following configuration on EX1:
virtual-chassis {
no-split-detection;
traceoptions {
file me;
flag me detail;
}
member 0 {
mastership-priority 255;
}
member 1 {
mastership-priority 255;
}
}
I then go to EX2 and enable its VC ports:
request virtual-chassis vc-port set interface vcp-255/1/0 member 0
request virtual-chassis vc-port set interface vcp-255/1/1 member 0
Now a virtual chassis is created with EX1 as master and EX2 as backup.
However, I lose my connectivity to EX1. I try logging back into EX1, and I log into the VC backup RE, as evidenced by the CLI prompt.
{backup:1}
lab@ex1>
I then execute "request session member 0" to move to the master and then everything seems fine.
But is it expected behaviour that after the VC is formed I will be logging into the backup RE by default?
Thanks,
Deepak