# OpenVswitch VLAN persistence **URL:** \ **Category:** Product Support\ **Created:** [December 5, 2017, 2:43pm UTC](https://forum.opennebula.io/t/openvswitch-vlan-persistence/5382 "2017-12-05T14:43:54Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Mohamed\_Imran\_K\_R](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/mohamed_imran_k_r/32/6184_2.png) [@Mohamed\_Imran\_K\_R](https://forum.opennebula.io/u/Mohamed_Imran_K_R)\ **Post date:** [December 5, 2017, 2:43pm UTC](https://forum.opennebula.io/t/openvswitch-vlan-persistence/5382/1 "2017-12-05T14:43:54Z")
VLANs are not persistent across soft reboot. If we reboot the instance via ssh, all VLAN tags on openvswitch are lost. * * * **Versions of the related components and OS (frontend, hypervisors, VMs):** - I am using OpenNebula 5.2 on production and 5.4 on our staging environments. We use a mix of mostly xen along with KVM deployments - OpenVSwitch 2.3.1 **Steps to reproduce:** - Login to any of the VM (which has vlan tagged interfaces) via ssh and do a reboot manually on cmd. **Current results:** - The VM would shutdown and come up on its own normally but all the VLAN info would be lost - We have to poweroff/poweron the VM again from sunstone to apply the VLAN tags correctly again **Expected results:** - VLANs should be persstent across reboots. - The deployment.cfg file should have he VLAN tag present as part of the VIF ---
**Author:** ![Mohamed\_Imran\_K\_R](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/mohamed_imran_k_r/32/6184_2.png) [@Mohamed\_Imran\_K\_R](https://forum.opennebula.io/u/Mohamed_Imran_K_R)\ **Post date:** [August 2, 2019, 3:35pm UTC](https://forum.opennebula.io/t/openvswitch-vlan-persistence/5382/2 "2019-08-02T15:35:39Z")
We wrote a script. The script queries the opennebula API and gets the VLAN and applies the same