Forum Discussion
R2600 device and tenant/partition configuration
- Remove vlans from partition Common
- Create vlan in selected Partition (be sure that vlan name is same as in 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.
- pietrucha92Feb 18, 2025
Altocumulus
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:
https://www.linkedin.com/pulse/f5-lab-119-configuring-route-domain-deni-ramdani-xivqc/
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:
https://techdocs.f5.com/en-us/f5os-a-1-8-0/f5-rseries-systems-administration-configuration/title-tenant-management.html- AnjaliJFeb 18, 2025
Nimbostratus
pietrucha92Thank you for your brief explanation that helped a lot! :)
- Stefan_KlotzOct 13, 2025
Cumulonimbus
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 :)- pietrucha92Oct 13, 2025
Altocumulus
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.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com