https://community.extremenetworks.com/t5/extremecontrol/policy-bug-case-dependent-vlan-names/m-p/91796#M280 <P>I just ran across this issue today.&nbsp; We are running XOS&nbsp;30.2.0.29 and XMC&nbsp;8.5.2.6.</P><P>I moved a switch from one policy domain to another and tried to Enforce but got an error.&nbsp; The issue ended up being a case difference in VLAN names.</P><P>On the switch, vlan 1123 was named vsh-1</P><P>On all other switches and in the policy, vlan 1123 was named vSH-1</P><P>I tried renaming the vlan - config vlan 1123 name vSH-1 - but was told it already existed by that name.</P><P>I then fixed the issue by renaming the vlan to something else, then to the uppercase name.</P><P>No more Enforce issue.</P> Wed, 10 Mar 2021 04:40:35 GMT Robert_Fredette 2021-03-10T04:40:35Z https://community.extremenetworks.com/t5/extremecontrol/policy-bug-case-dependent-vlan-names/m-p/91796#M280 <P>I just ran across this issue today.&nbsp; We are running XOS&nbsp;30.2.0.29 and XMC&nbsp;8.5.2.6.</P><P>I moved a switch from one policy domain to another and tried to Enforce but got an error.&nbsp; The issue ended up being a case difference in VLAN names.</P><P>On the switch, vlan 1123 was named vsh-1</P><P>On all other switches and in the policy, vlan 1123 was named vSH-1</P><P>I tried renaming the vlan - config vlan 1123 name vSH-1 - but was told it already existed by that name.</P><P>I then fixed the issue by renaming the vlan to something else, then to the uppercase name.</P><P>No more Enforce issue.</P> Wed, 10 Mar 2021 04:40:35 GMT https://community.extremenetworks.com/t5/extremecontrol/policy-bug-case-dependent-vlan-names/m-p/91796#M280 Robert_Fredette 2021-03-10T04:40:35Z