For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Radboud_Veld's avatar
Radboud_Veld
Icon for Altostratus rankAltostratus
Aug 29, 2024

R2600: how to deal with vlans in tenant's partition's

Hey all,

 

I'm in the process of replacing an old 4200 with a new R-series 2600 for a customer.

The current config in the 4200 consists of several partitions, and in the to be deployed tenant we want to keep using partitions.


When deploying a tenant in the R2600, I can select which vlans I want to "pass on" towards the tenant.
They will then automatically show up in the /Common of the tenant. So far it all works nice.

However, I need some of these vlans to end up in a specific partition.

So how do I go about that?


I can manually create these vlans under the desired partition, but I don't think it's possible if they already exist in /Common.
So, catch-22?


I won't return to clients site for a while, and currently don't have acces to a home lab or something of the like.
So I was hoping to get some clarity on this, to better prepare myself.

regards,




application delivery

8 Replies

    • Radboud_Veld's avatar
      Radboud_Veld
      Icon for Altostratus rankAltostratus
      Aug 30, 2024

      Thanks 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. 


      • Nikoolayy1's avatar
        Nikoolayy1
        Icon for MVP rankMVP
        Aug 30, 2024

        Yes 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.

         

         

  • Radboud_Veld's avatar
    Radboud_Veld
    Icon for Altostratus rankAltostratus
    Sep 27, 2024

    Thanks all, I forgot about the existince of Route-domains in order to keep the traffic separated. Works like a charm now...

    Still having some issues with loading my Journey-modified UCS file, but I'll try and start a case for that with F5

     

  • Stefan_Klotz's avatar
    Stefan_Klotz
    Icon for Cumulonimbus rankCumulonimbus
    Oct 13, 2025

    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.
    Now 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 we select the appropriate trunk-interface from the interface list.

    As already mentioned in another post it might be related that the interfaces are not correctly shown within the tenand. At least nobody could answer if this is a "normal" behavior.

    Within the trunk details the correct physical interfaces from F5OS will be displayed:

    But on the Interface list they are missing:

    That's why also the error message makes (theoretically) sense:
    ERROR: Unable to find interface object for configured trunk member 3.0



    Where is this coming from and how can this be fixed?
    Thank you!

    Regards,
    Stefan :)