Hello,
I’m working with configuration on r2600 where is one tenant with multiple vlans.
On tenant perspective I want to add each vlan to specific partition.
How to do this in correct way for rSeries?
There is a bug Bug ID 1231889
which says that all vlans need to be in Common partition.
On vCMP or bare metal there was an option to create vlan in partition, add it to route domain and then configure all other things (IP, routes, etc).
So - what is proper way?
Where can I find F5 document?
Hi @pietrucha92 ,
First and foremost, welcome to the DevCentral Community! It’s great that you found us and wants answers to your questions. Fret not, the community will reach out to you to answer your question.
Right now, I’ve found a technical document from F5 related to your query. You can read more here.
Let me know if this helps at all!
Thanks!
I’m glad to be with DevCentral community 
About your answer: attached link describe F5OS part which is super clear for me.
Problem is related to very specific case where we use r2600 device with TMOS tenant which have configured few partitions and each partition its own vlan.
In attached BugID there is an info: Partitions other than the Common partition cannot have VLANs
For me is something new because in vCMP or on baremetal appliances I could create vlan in any partition I want.
So main question is: how to prepare vlan config for partition?
1. As always: create rd, create partition, create vlan in partition? (/partition/vlan)
2. Based on BugID: create rd, create partition, add /common/vlan to /common/rd and do not create vlan object in /partition?
I have opened a case and waiting for ground explaining but maybe other member hitted same issue and have good solution for that.
I suggest reading [F5OS-A] After recreating VLANs in tenant on r2000/r4000, traffic is not passing. and [F5OS-A] How to set a trunk vlan to multiple Interfaces on rSeries 2000/4000 series? as you need to delete the assigned from the appliance to the the tenant vlans in the Tenant as they will be by default in the Common partition (do not delete from the Appliance) but you will need to also assign the correct interfaces to the Vlans as r2600 is different than the bigger rSeries devices.
Hello @pietrucha92 if my reply helped you please mark it as a solution.
Hello @pietrucha92
We have the same case in the deployment so can you please help to understand how did you fix the domain route with for partition as all VLAN are in common partition?
In my case there were 2 problems:
That solved all problems
you just created vlan in partition same as F5OS ?
Hi @pietrucha92 ,
We tried deleting vlan from common partition on tenant and created new vlan in different partition same as F5OS host. Also created route domain ,self ip and default route for that new partition but still we are unable to ping our default gateway from partition.
Could you please suggest if we are missing anything here.
What do you want to accomplish?
Partition != Route Domain.
Partitions are primarly use to give proper permissions for different administrator groups.
RouteDomain is VRF in F5 world and is necessary to use same IP subnets for different domain.
Here is good example of Route Domain configuration:
For r2600:
1. Create tenant on F5OS level; select all necessary vlans*
2. When tenant is UP, start with preparing partition/rd
3. Remove vlans from Common and recreate each in specified partition/rd
4. Then rest of configuration: SelfIP, routing, etc but always select proper partition or use %RD notation for IP addresses
*there was a limitation that vlan can belong to one interface (phys/LAG), changed in F5OS 1.8.0:
@pietrucha92 Thank you for your brief explanation that helped a lot!
@pietrucha92
We need to setup different VLANs in dedicated partitions/Route Domains (right now on r5600, but later also on r2600).
Therefor we created first the VLANs on F5OS and assigned them to the tenant.
Then these VLANs will correctly shown within the tenant, but by default in the Common partition.
We deleted the VLAN in Common, switched to the required partition and tried to recreate it there as well using the exact same name like in F5OS.
But then we get the ERROR: Unable to find interface object for configured trunk member 3.0
For your reference, we have two LAGs created in F5OS, one for heartbeat with interfaces 4.0 & 8.0 and another for user traffic with interfaces 3.0 & 7.0.
When creating the VLAN within the tenant I select the appropriate trunk-interface from the interface list.
Where is this coming from and how can this be fixed?
Thank you!
Regards,
Stefan
I assume you’re trying to select an interface while adding a VLAN from the TMOS perspective.
Please try the following steps:
Add the VLAN to the tenant on the F5OS level.
After that, the VLAN should be visible on the TMOS level under the Common partition.
Remove the VLAN from the Common partition.
Switch to the selected partition.
Add a new VLAN – provide only two values: name and tag (leave all other fields empty).
I tried this in my environment and didn’t get any errors.
Thank you @pietrucha92
Add a new VLAN – provide only two values: name and tag (leave all other fields empty).
This was exactly doing the trick!
Once done, I also noticed for all the other VLANs, which were still assigned in the Common partition, that they also have no value in the “Untagged/Tagged Interface” column.
From a management/troubleshooting perspective this is not really optimal. I would recommend (or at list wish) that these information will also be correctly visible within the tenant. Otherwise remove the columns and configuration options to avoid misunderstandings or mistakes.
I will proceed with further testing, especially IP-connectivity.
Regards,
Stefan