Which three Juniper switch models require an additional workflow to form a Virtual Chassis? (Choose three.)
According to Juniper Mist documentation, the EX2300, EX4650, and QFX5120 switches require a specific additional workflow within the Mist portal to form a Virtual Chassis because these models do not have dedicated Virtual Chassis ports (VCPs). Unlike other EX-series models (such as the EX4100 or EX4400) that possess factory-defined, dedicated VCPs and can form a Virtual Chassis automatically upon physical connection, these three platforms require an administrator to explicitly initiate the 'Form Virtual Chassis' action from the Mist UI.
This workflow is necessary because the system must logically convert standard network uplink ports into Virtual Chassis ports to enable stack communication. To execute this, the switches must first be onboarded to the Juniper Mist cloud as standalone devices and assigned to the same site. Once they are online and their configuration is managed by Mist, the administrator selects the desired members from the switch inventory and clicks More > Form Virtual Chassis.
During this additional workflow, the Mist portal prompts the user to specify which front-panel ports will be repurposed as VCPs and allows for the manual assignment of member IDs and Routing Engine roles. This 'pre-provisioned' method ensures a deterministic setup where roles are not left to chance. Once the command is pushed, the switches reboot to reconfigure their internal hardware logic to treat the selected ports as fabric links. Juniper emphasizes that for these specific models, the 'Form Virtual Chassis' option is the only supported way to establish the stack within Wired Assurance, as it ensures that the cloud-native management plane correctly recognizes the multiple physical chassis as a single logical entity.
Currently there are no comments in this discussion, be the first to comment!