Hello
Just to let everyone know that when you do this upgrade, it could happen that the dur policies miss something.
In our case we were looking at this error
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/8bc9febc00c94d44abfa5f95c59ed504.png)
The fix is easy, it seems that something was there on the allowed vlans, and our client saw something in there, a space! or something
When there is nothing configured you will see this: -
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/4c5a5300b496409eb4af781947b7877d.png)
But in the allowed vlans names on trunk there was nothing, we had to go inside deled that space or whatever there was it and save it so it
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/3d2b9d6730d843d8aef14ef9b3746282.png)
We had to delete that thing, as you can see, it seems its a space.
So the access vlan start working
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/c66073916f58475ea308134d18b25ee8.png)
Now we have a LOT of this but its just affecting like 2 of them for some reason
In all of them we can see the error
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/8bc9febc00c94d44abfa5f95c59ed504.png)
But in just 2 of them its really affecting for the vlans
I don't know if its a bug or whatever it is. But just letting you guys know that if you have DUR that is assigning vlans, this could be your problem
At the beginning i though in just creating it again and that's it, because on my lab it was working fine but well, it seems it was just the space.
Carlos