--> As you are aware we need to create VLANs before assigning the IP address in the F5 LTM.
--> Once you create any VLAN in F5 LTM, It will automatically tag the VLAN or you can change the VLAN number to custom number.
--> By Default, If you use setup utility to set up the F5 LTM then three VLANS will be created automatically.
i) Internal VLAN
ii) External VLAN
iii) HA VLAN
--> After you create VLAN in F5 LTM then you need to assign the interfaces to the specific VLAN.
--> So here comes the actual point of the post, Whether the interface should be configured as an untagged interface or tagged interface.
--> Let me explain you what is the difference between untagged interface and Tagged interface below:
Tagged Interface:
--> If you configure the interface as tagged interface then whatever the frames sent from F5 device to downstream device sent including with tag/dot1q header in it.
--> Usually configured when the other end device is configured as a trunk.
--> Generally used when you have configured one arm deployment mode in F5 LTM.
--> More than one VLAN is associated with an interface in F5 LTM.
Untagged Interface:
--> If you configure the interface as untagged interface then whatever the frames sent from F5 Device to downstream device sent without including with tag/dot1q header in it.
--> Usually configured when the other end device is configured as an access port.
--> Generally used when you have configured Two arm deployment mode or N-Arm deployment mode in F5 LTM.
--> Only one VLAN is associated with an Interface in F5 LTM.
--> However, We can configure an Interface in both the modes: Tagged as well as Untagged but this is not commonly implemented.
Ex:
Assume you have configured the interface with following settings:
F5 Interface Configuration
Tagged:
VLAN 5
VLAN 10
Untagged:
VLAN 15
Switch Interface configuration
Trunk
Native VLAN 15
--> When the F5 sends the traffic for VLAN 5 or VLAN 10 to Switch then It's gonna send it with the tag so that switch can understand the tag and can forward it to proper devices.
--> When the F5 sends the traffic for VLAN 15 to Switch then It's not gonna send it with the tag so that switch can understand that it is native VLAN traffic and forward according to that.
Ref:F5.com
Connect with me on Linkedin: https://www.linkedin.com/in/mahmmad-kareemoddin-7a177342/
--> Once you create any VLAN in F5 LTM, It will automatically tag the VLAN or you can change the VLAN number to custom number.
--> By Default, If you use setup utility to set up the F5 LTM then three VLANS will be created automatically.
i) Internal VLAN
ii) External VLAN
iii) HA VLAN
--> After you create VLAN in F5 LTM then you need to assign the interfaces to the specific VLAN.
--> So here comes the actual point of the post, Whether the interface should be configured as an untagged interface or tagged interface.
--> Let me explain you what is the difference between untagged interface and Tagged interface below:
Tagged Interface:
--> If you configure the interface as tagged interface then whatever the frames sent from F5 device to downstream device sent including with tag/dot1q header in it.
--> Usually configured when the other end device is configured as a trunk.
--> Generally used when you have configured one arm deployment mode in F5 LTM.
--> More than one VLAN is associated with an interface in F5 LTM.
Untagged Interface:
--> If you configure the interface as untagged interface then whatever the frames sent from F5 Device to downstream device sent without including with tag/dot1q header in it.
--> Usually configured when the other end device is configured as an access port.
--> Generally used when you have configured Two arm deployment mode or N-Arm deployment mode in F5 LTM.
--> Only one VLAN is associated with an Interface in F5 LTM.
--> However, We can configure an Interface in both the modes: Tagged as well as Untagged but this is not commonly implemented.
Ex:
Assume you have configured the interface with following settings:
F5 Interface Configuration
Tagged:
VLAN 5
VLAN 10
Untagged:
VLAN 15
Switch Interface configuration
Trunk
Native VLAN 15
--> When the F5 sends the traffic for VLAN 5 or VLAN 10 to Switch then It's gonna send it with the tag so that switch can understand the tag and can forward it to proper devices.
--> When the F5 sends the traffic for VLAN 15 to Switch then It's not gonna send it with the tag so that switch can understand that it is native VLAN traffic and forward according to that.
Ref:F5.com
Connect with me on Linkedin: https://www.linkedin.com/in/mahmmad-kareemoddin-7a177342/
I'm not sure on an untagged interface, it doesn't send a tag. Doesn't it assign a 4093 or 4094 tag by default? We had issues in ACI where the switch was recognizing that 4094 or 4093 and not sending traffic because that VLAN didn't exist to it. In our Nexus7K, I believe it was ignored. ACI port channel was configured with Access(Untagged) for reference.
ReplyDeleteUntagged interfaces on F5 does not send any tag information while sending to frames to switch. It may assign some tag but does not include in the frame.
Deleteto simply say that ..
ReplyDeletetagged interface means Trunk.
untagged interface means just access.