Answer: B. Virtual Chassis on the Juniper MX can only be used with Trio-based MPC line cards.
Answer: C. The VC-B member of
the virtual chassis has the privilege of running the kernel
synchronization process on both routing engines. Recall that the VC-B
ksyncd on the VC-Bm so
that it can be synchronized with the VC-Mm. The VC-Bb will also need
to run another copy of
that it can keep synchronized with the VC-Bm in case there’s a
Answer: B. Only the VC-Mm
routing engine will respond on its
fxp0 interface while all other routing
engines will not. You must use the console or the
request routing-engine login command to
login to other routing engines.
Answer: B. The chassis serial number is used when configuring a preprovisioned virtual chassis. No other serial number is valid.
Answer: C. Recall that the global FPC number = (member-id * 12) + local FPC. In this case, the answer would be (2 * 12) + 7 = 33.
Answer: B. There’s no mastership election process when the VC-Mb fails. The only two routing engines that would cause a mastership election process in the event of a failure are the VC-Mm and VC-Bm.
Answer: A. The new apply-group naming convention for routing engines in a virtual chassis is member0-re0, member0-re0, member1-re0, member1-re1, so on and so forth.
Answer: B,C. Trick question. The Juniper MX VCCP implementation builds the SPF tree per chassis and uses the system MAC address as the identifier.