Forum Discussion
Nimbostratusf5 r5600 appliance issue with adding trunk to vlan
So i get this error when I'm trying to add trunk to the ha vlan that i created-
ERROR: Unable to find interface object for configured trunk member 3.0
What does this mean?
When i look under the interfaces for the tenant (17.5.0) i do not see the actual interfaces which are supposed to be 1.0, 2.0, 3.0 - - - - 10.0 instead i only see 0.1, 0.2, 0.3 - - 0.6 is that the reason why it shows the error?
Also why does it even show 0.1, 0.2 - - - 0.6 instead of the 1.0, 2.0, 3.0, - - - - 10.0??
This makes no sense to me.
Thank You
4 Replies
- Stefan_Klotz
Cumulonimbus
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 :) - Stefan_Klotz
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 :) - Stefan_Klotz
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 :) - Nikoolayy1
MVP
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:
