DvR Leaf to vIST Migration in OneStepp

[Sanktis]

Hello,

I am currently trying to switch our DVR Leaf Nodes from DVR to vIST clustering. Since we have a number of nodes that need to be converted, I am looking for a way to do this remotely without requiring console access.

We are using XIQ SE. I tried to solve this using a script that I would execute, but unfortunately, I can't find a way to do it in a script without requiring a reboot between disabling the DVR flag (no dvr) and applying the vIST configuration.

When I run the script manually, I get stuck as follows:

vsp4-cf-1:1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
vsp4-cf-1:1(config)#no router isis enable
WARNING:Disable ISIS will cause traffic disruption
Do you want to continue (y/n) ? y
WARNING: All ACLs and ACE entries under the ACLs will be disabled when DVR Leaf is deleted
vsp4-cf-1:1(config)#router isis
vsp4-cf-1:1(config-isis)#no spbm 1 smlt-peer-system-id
vsp4-cf-1:1(config-isis)#no spbm 1 smlt-virtual-bmac
vsp4-cf-1:1(config-isis)#no boot config flags dvr-leaf-mode
Warning: dvr-leaf-mode flag is disabled
Warning: Please save configuration and reboot the switch
for this to take effect.
vsp4-cf-1:1(config)#no dvr leaf virtual-ist
vsp4-cf-1:1(config)#no dvr leaf
vsp4-cf-1:1(config)#show dvr
************************************************************************************
Command Execution Time: Thu Aug 20 17:21:45 2026 CEST
************************************************************************************
There is no DVR instance.
vsp4-cf-1:1(config)#
vsp4-cf-1:1(config)#router isis
vsp4-cf-1:1(config-isis)#spbm 1 smlt-virtual-bmac 00:xx:xx:xx:xx:FF
vsp4-cf-1:1(config-isis)#spbm 1 smlt-peer-system-id xxxx.xxxx.xxxx 
vsp4-cf-1:1(config-isis)#spbm 1 ip enable
Error: IP commands are not supported on DVR Leaf

The alternative option would be to simply load the new configuration and perform a reboot. This works in principle. However, after the reboot, I still have to run the following two commands again. After that, the vIST config works—even though those commands are already included in the configuration.

virtual-ist peer-ip x.x.x.x vlan xxx
router isis enable
sa co

* MAC, IDs, IPs were masked in this commands.

Used VOSS Version 9.4.1.0.

Is anyone aware of a way to perform the migration from DVR Leaf to VIST without having to make further adjustments via console cable after the reboot?

Cheers 
Florian

[veduapks]

for a topic like dvr leaf to vist migration in onestepp, vedu  can be described as a simple entertainment app that focuses on giving users an easy way to explore and enjoy movies and tv content. its clean layout makes navigation simple while keeping the overall experience smooth and user friendly.

[netmirrorapp78]

If you are moving a DvR Leaf pair to a new vIST domain, the process should be done carefully because both Leaf nodes must remain in the same DvR domain for vIST to work. First disable IS-IS on both Leafs and then disable DvR. After that configure both switches with the new DvR domain ID and recreate the vIST settings using the correct local and peer IP addresses and cluster ID. Finally enable IS-IS again and verify the show dvr output to confirm the new domain and vIST status. From a Netmirror -style perspective, think of it as a clean migration: remove the old network relationship → configure the new DvR domain → rebuild vIST → restore connectivity → verify. Make sure you have the current configuration backed up before starting because disabling DvR removes the vIST configuration on that Leaf and it must be configured again.

[WillyHe]

Hello Visitor,

vIST is NOT a DVR domain, it is a LAG feature like M-LAG for LACP.

[Michael_Morey]

Florian,

In my research for this, it appears that the issue you are seeing is by design as the commands:

virtual-ist peer-ip x.x.x.x vlan xxx
router isis enable

are the very LAST commands that need to be ran to configure the vIST.

When the config is replayed at boot it is done top down and when these are hit, the structure has not been setup yet for the first time vIST use.  You may need to setup the config file a little different to get this to work:

1.) VLAN creation should be done first

- vIST VLAN - I-SID Mapping and IP addressing

2.) B-VLAN (which I assume you already have setup

3.) SPBM and ISIS Parameters

4.) ISIS NNI port config

THEN

virtual-ist peer-ip x.x.x.x vlan xxx

router isis enable 

Hopefully that helps