Same as I understood from a juniper update. Dual RE on a single chassis is only possible if there is no VC/VCF. It is intended to do a ISSU with a single unit. ISSU is hitless in best case. There is a soft-reset on the PFE.
So in your VC with two QFX5100's there will be only two RE's, one on each unit. -- Kind regards, Peter Tavenier > Op 21 mrt. 2015 om 17:07 heeft Nitzan Tzelniker <nitzan.tzelni...@gmail.com> > het volgende geschreven: > > AFAIK The second RE is spawn only during the upgrade and shutdown after the > upgrade > > Nitzan > > > On Sat, Mar 21, 2015 at 4:45 PM, Octavio Alfageme < > octavio.alfag...@gmail.com> wrote: > >> Hello everyone, >> >> Soon I'm gonna have to configure a virtual-chassis of two QFX5100s. I'd be >> grateful if you could help me with a couple of doubts I haven't been able >> to solve with the manuals: >> >> * Are both REs, each one running as a different virtual-machine over Linux >> KVM, enabled by default when the QFX5100 boots for the first time? If not, >> what does it have to be done to get it? >> * If I need to set a virtual-chassis (not a virtual-chassis fabric) between >> both QFX5100 switches, how many members do I have to consider? If both REs >> are active, then I suppose the answer would be four (QFX5000_1_RE0, >> QFX5000_1_RE1, QFX5000_2_RE0, QFX5000_2_RE1). However, I haven't seen any >> example considering the redundant RE on each QFX5100. >> >> Thanks in advance >> >> Kind regards >> >> Octavio >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp