Forum Discussion
Dave_Mehlberg
Cirrus
CirrusR-Series Tenant - Need to change Vlan tag
I need to change all of the vlans on my LTM-tenant (15.1.10.4) - The changes are on the tag not the name - I need to keep the names the same and change the tag numbers. [ vlan Core 1978 to vlan Core...
What seems to work without affecting anything else is changing the tag in the bigip_base.conf file and reloading system.
CA_Valli
MVP
MVPHello Dave, in my opinion the quickest thing to do would have been rewriting VLAN tag in the F5OS tenant, I'm pretty sure you can do it via command line. This way, every object that references the VLANs that are already configured wouldn't have required any change.
Since you've removed VLANs from the tenant already, then you'll need to manually look for objects that still reference the old VLANS, and then update the configuration to reference the new vlan.
You're likely to find them in these objects:
- Every SELF-IP in the "Network > Self IPs" menu that was referencing the old VLANS must be updated to match one of the new VLAN names
- There might be some VLAN-restricted Virtual Servers that requires updates (quickest way to find them would be CLI command: tmsh list ltm virtual all vlans ). If this is your case, you'll need to modify the "Enabled Vlans" list excluding the old objects
- When you're done with these two steps, try deleting the VLAN object from Network > VLANs menu. If it still won't let you do it,
- There might be some other objects as well that reference those VLANs in the config file, after you "fixed" the two points before, try running this CLI command: more /config/bigip.conf | grep "VLAN_NAME" -B10 to see what object it is and go fix it
Dave_MehlbergCirrus
CirrusThe original VLAN still exists on the tenant. When I tried to delete it, I received an error.
Knowing that, should I try to change the VLAN using CLI and modify the Bigip_Base.conf file?
Dave
- CA_Valli
Hello Dave,
sorry, I meant: since you deleted vlans from the Host already. Since it's the Host that pushes VLANs to configured tenants, you don't need to edit bigip_base.conf file on the tenant, networking configuration will be automatically passed by the F5OS hypervisor.Since now the host has correct VLAN configuration, and new VLANs have been pushed to the tenant, I believe the easiest way to resolve this issue will be matching the "correct" VLANs on network objects.
- Dave_Mehlberg
I am sorry - but the new vlan did not get pushed to the tenant.
The tenant still shows vlan Core tag 1978
Dave
- CA_Valli
Mmm ok i think I get this.
The tenant is still likely using the old vlan subscription (because that's the one that was published first). Since VLAN objects are named identically , the Tenant still thinks it has the correct object .. but since L2 is different, traffic won't flow.The correct way to address this would be deleting the old VLAN from the tenant, removing publication, and adding it back so it's going to create a new subscription. But that's going to take a lot of effort because you need to remove VLAN from every object first (Virtual Servers, and self IP's - which would require you to assign a different vlan temporarily).
So .. in this very specific case it might just be faster to actually just rewrite the tag in the config file
cp /config/bigip.conf /config/bigip.conf.backup sed -i 's/tag 1978/tag 978/g' /config/bigip.conf #repeat w/ other tags more /config/bigip.conf | grep tag tmsh load sys config verify tmsh load sys config tmsh save sys config tmsh list net vlan tag #rollback cp /config/bigip.conf.backup /config/bigip.conf tmsh load sys config tmsh save sys config