f5 r5600 appliance issue with adding trunk to vlan

The tenant is actually KVM VM and you should find the real interfaces under the r5600 F5OS and create LAG as that is the new name 😉

See:

rSeries Networking

Similar issue here as well.
We have a r5600 with F5OS 1.8 and tenants running on 17.5.0.
We created a LAG with interfaces 3.0 & 7.0 and 4.0 & 8.0 (to share the internal pipelines). And we created also some VLANs and assigned them to the LAGs as required.
Now within the tenants we see the VLANs and also the trunks. But the VLANs do NOT show any reference in the "Tagged Interface" column:

And also for the trunks the "Capacity" column shows 0:

Is this really normal behavior or do I miss something on F5OS-level?

If I try then to assign the VLAN to the trunk within the tenant configuration I also get the same error message.
Then I tried if ping is maybe working without any further configurations within the tenant, but this is also not working.
Therefor something seems to be still wrong or missing.
Configuration of F5OS looks like this:

Are there any other/additional information available, how VLAN and Trunk/LAG configuration is working and shared between F5OS and tenants?
Thank you!

Regards Stefan :)

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

So what's going wrong internal here???
Thank you!

Regards,
Stefan :)

Ok, issue is solved on our side.
There was a mismatch of the mapping between the switch ports and the assigned VLANs.
Once corrected ping is working.
This means there is NO additional configuration required in regards to trunks or VLANs within the tenant. Only the IP-addresses must be created and assigned to the VLANs. Everything else is handled and managed via F5OS.
But can still someone confirm the look and feel of the Interface and Trunks menu within the tenant? From an operational point of view this doesn't feels intuitive or is this something "normal" with virtualization? Maybe this can be optimized in next versions?
Thank you!

Regards,
Stefan :)

The issue/error message is back again :(
We need to setup different VLANs in dedicated partitions/Route Domains.
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 name like in F5OS.
But then we get again the 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 :)