I have just configured an EX4600 and EX4300 mixed chassis. THere are 2 EX4600's and 1 EX4300. I have configured the VC using the preprovisioned method of
Set virtual-chassis member # serial-number 123456 role master/linecard
The EX4600 are both set to routing engine roles and the EX4300 is a line card. When running everything looks well and configured interfaces work correctly. However, I just shutdown the VC to move some hardware and when powering back up I did not power up the EX4300. I assumed that the VC would come up fine and that simply the EX4300 would show as not present.
Instead, on boot up of just the 2 EX4600's with the EX4300 remaining off, I received the message:
warning: This chassis is operating in a non-master role as part of a virtual-chassis system....
Then on login to the master it shows as linecard:0. Show virtual-chassis then shows both the EX4600 as linecard roles and the EX4300 is not present (as suspected)
Only when I boot up the EX4300 does the VC appear to become active again, the EX4600's become master and backup as they should, and then traffic starts flowing (configured ports become active),
What is causing this? My thought with VC is it should be redundant and should handle a switch failure or removal, especially of a linecard switch?
How these switches interconnected ?
virtual-chassis no-split-detection configured ?
Ok it turns out that the EX4600's do eventually take on the role of master and backup and all interfaces then come back up.
However, this takes about 15 min! If I plug the EX4300 in, it happens within a minute or so.
Why does this take so long for the 2 EX4600's to work out the master/backup role when the EX4300 is not connected? Can this be sped up?
To answer the questions: THese switches are interconnected via 40gb vcp ports, single links. no-split-detection is not currently configured, however it was initially present during the first powerup without the EX4300, because I had initially configured no split detect when first setting up the VC (just had the 2 EX4600;s). The issue is present with or without the no split option.
What version JUNOS are you running? Look at PR1225696. I recall until one of the more recent 14.1X53 releases it taking 10+ minutes for a newly-rebooted EX4300 VC to come up--perhaps related to your issue.
This turned out to be a bug with the version of junos I was running. Upgraded the Junos version to D45 as you suggested and the issue is resolved. thanks
The otherthing, which you may want to try is non-provisioned virtual chassis where in you will not bind the serail numbers in vc config.
Just define FPC number and associate the priority and test.
Similar issue, we did observed for EX 4300 of older JUNOS