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

eesun_276598's avatar
eesun_276598
Icon for Cirrus rankCirrus
Dec 06, 2017

VLAN ID and tag

Hi Anyone can make it clear the concept with relation between VLAN ID and its tag in f5. In Cisco switch, vlan id is vlan number, such as vlan 10, vlan 20, vlan 30 etc. And tag is used when two switc...
application delivery
BIG-IP
PK_Bhatia's avatar
PK_Bhatia
Icon for Nimbostratus rankNimbostratus
Dec 11, 2017

It is due to 802.1Q tagging also called Dot1q tagging. It is required to tag the VLANs in hardware f5 but not in VE. Try searching for 802.1q.

 

  • eesun_276598's avatar
    eesun_276598
    Icon for Cirrus rankCirrus
    Dec 18, 2017

    You are right. In VE, when configuring vlan as untagged, the vlan interface can work well, but if it configured as tagged, it cannot work(no connection). Can you tell why? Thanks

     

  • PK_Bhatia's avatar
    PK_Bhatia
    Icon for Nimbostratus rankNimbostratus
    Dec 18, 2017

    Because you are already assigning VLAN to the network interface you assign to VE f5. I think VMWare workstation support it if you assign interface with VLAN 4096 (cisco), not sure about other virtualization vendors.

     

  • eesun_276598's avatar
    eesun_276598
    Icon for Cirrus rankCirrus
    Dec 18, 2017

    Right, but if configuring it as tagged in F5, why it cannot have connection? Can I say it is becuase VMWare workstation interface is not trunk? Thank you

     

  • PK_Bhatia's avatar
    PK_Bhatia
    Icon for Nimbostratus rankNimbostratus
    Dec 18, 2017

    short answer vmware virtual switch basically act as hub and you can't route traffic between vlans without layer 3.