This KB describes a scenario where a two‑member Virtual Chassis (VC) needs to be split so that each device operates as a standalone unit. However, even after the split, the Mist dashboard continues to display the devices as if they are still part of a VC, despite the fact that each one is no longer functioning as a VC member.
There are scenarios where a Virtual Chassis (VC) must be split—either because each member will operate as a standalone device or for other operational reasons. When managing a VC through Mist, the recommended workflow is to use the “Modify Virtual Chassis” option. This workflow leverages Junos pre‑provisioning, which configures the role and serial number of all members in the VC. For more information, please refer to the documentation:
https://www.juniper.net/documentation/us/en/software/mist/mist-wired/topics/topic-map/modify-vc-preprovisioned.html
In this case, however, the VC was pre‑provisioned manually via CLI commands. Mist subsequently pushed the configuration and recognized both members as part of a VC. Example of configuration pushed:
When the VC was later intended to be split, the CLI configuration was removed, VC ports were disconnected and unconfigured, and each member was reactivated as a standalone device through CLI. Despite this, the Mist inventory continued to display both devices as part of a VC.
Because the VC was pre‑provisioned via CLI and not through the “Modify Virtual Chassis” option, Mist retained stale information in its inventory. As a result, it was not possible to release each member individually from the site or from Mist.
The solution in this scenario is to release the entire VC from Mist and then re‑adopt each member individually. Once re‑added, the devices will correctly appear as standalone units. For more information about the Mist switch adoption process, please visit:
https://supportportal.juniper.net/s/article/Mist-switch-adoption-process