To keep everything stable, you need to always change the configuration either only via CLI or only via MIST cloud. Do not use both methods at the same time, because MIST cloud does not know anything about what you have changed via CLI. If you change something via MIST cloud, your previous configuration will be overwritten, and some of the configuration you have done via CLI may disappear. You need to add a switch with factory default configuration to MIST cloud, and then configure it only via MIST cloud.
If you going to use MIST for configuration you have to use provisioned VC configuration.
Manage a Virtual Chassis Using Mist (Add, Delete, Replace, and Modify Members)
| Juniper |
remove preview |
|
| Manage a Virtual Chassis Using Mist (Add, Delete, Replace, and Modify Members) |
| You can use the Modify Virtual Chassis option on the switch details page to manage your Virtual Chassis. The operations you can perform include renumbering and replacing the Virtual Chassis members and adding new members to a Virtual Chassis. |
| View this on Juniper > |
|
|
If you need to use non-provisioned VC configuration you have to use CLI.
Removing or Replacing a Member Switch of a Virtual Chassis Configuration
| Juniper |
remove preview |
|
| Removing or Replacing a Member Switch of a Virtual Chassis Configuration |
| You can remove or replace a member switch in a Virtual Chassis without disrupting network service on the other member switches. |
| View this on Juniper > |
|
|
------------------------------
IHOR SHTANKO
------------------------------
Original Message:
Sent: 10-25-2024 16:27
From: Anonymous User
Subject: Mist - replace master switch on Virtual Chassis
This message was posted by a user wishing to remain anonymous
I ran the following commands on the switches:
request virtual-chassis vc-port set pic-slot 1 port 2
request virtual-chassis vc-port set pic-slot 1 port 3
After that, I added the switches to the inventory and assigned them to the site, and then configured them in Mist.
I inherited the company with the switches configured this way, and there are over 100 sites like this.
Is there a solution to replace the master switch FPC0 while they are still nonprovision?
Original Message:
Sent: 10-24-2024 02:17
From: IHOR SHTANKO
Subject: Mist - replace master switch on Virtual Chassis
How did you configure your VC ( before adding switches to MIST or you added switch to MIST and after that configured VC)? What is the reason using non-provisioned configuration in your case?
------------------------------
IHOR SHTANKO
Original Message:
Sent: 10-23-2024 14:43
From: Anonymous
Subject: Mist - replace master switch on Virtual Chassis
This message was posted by a user wishing to remain anonymous
Hello Allyn,
This is problematic for me, as it needs to work in a non-provisioned configuration. I need a solution for replacing the master switch while keeping the setup as non-provisioned, and ensuring it continues to work in the same configuration after the replacement.
Original Message:
Sent: 10-23-2024 02:08
From: IHOR SHTANKO
Subject: Mist - replace master switch on Virtual Chassis
Hi man,
You can use following procedure:
https://www.juniper.net/documentation/us/en/software/mist/mist-wired/topics/topic-map/modify-vc-preprovisioned.html
------------------------------
BR,
IHOR SHTANKO
Original Message:
Sent: 10-22-2024 16:20
From: Anonymous User
Subject: Mist - replace master switch on Virtual Chassis
This message was posted by a user wishing to remain anonymous
I have a virtual chassis with three members (unit 0, unit 1, and unit 2), where unit 0 is currently the master. The virtual chassis is configured as non-provisioned:
The switches are managed by Mist.
What is the best procedure to replace the master switch?