Altostratus
MVPBetter test the vCMP way deleting them from Common and creating them under the desired partition. If you see issues contact support, so first test. Other than that better run the latest F5OS version.
Moving an inherited VLAN to an alternate partition in a vCMP guest (f5.com)
AltostratusThanks for your answer.
I have occasionally administered vCMP's but not with partitions on the guest.
Anyway, shouldn't these vlans (under partitions in the tenants) also "exist" on the appliance when deploying a tenant?
How else will they connect to the outside world.
I'm probably missing something here... I'll give your advice a go when I'm back on-site.
MVPYes you have to create and assign them to the tenant from the appliance, this is why you will see them in Partition Common when you access the tenant as they will be autopopulated.
AltostratusThanks again so far,
Sorry but it's still a bit unclear for me, probably bad wording on my side;
1) When I remove vlan's from the /Common (because I need it in a partition), shouldn't I also remove them from vlan(list) on the appliance to prevent them from being re-added, when, eg., we need a new vlan on the tenant?
2) When removing said vlans from the appliance, won't this break outside connectivity?
Regards,
MVPAs I mentioned better have the latest F5OS , create a test tenant where you have assigned a test vlan then log into the tenant , create a partition then just from the tenant delete the Vlan that should be autopopulated in Common and recreate it in your partition(don't delete the vlan from the appliance or remove it from the tenant under the appliance).
You can follow the article for vCMP except the step with the route domains if you don't need this for your partitions and plan to use Route Domain 0 :