nerdexam
F5

101 · Question #551

A BIG IP Administrator wants to add a new VLAN (VLAN 40) to an LACP trunk (named LACP01) connected to the BIG-IP device Mufti VLANS exist on LACPO1. Which TMSH command should the BIG IP Administrator

The correct answer is B. create net vlan VLAN40 {interfaces replace-all-with {LACP01{tagged}} tag 40}. To add a new VLAN to an existing LACP trunk carrying multiple VLANs, the VLAN must be created with tagged interfaces since 802.1Q tagging is required when multiple VLANs share a single trunk.

Section 2: F5 Solutions and Technology

Question

A BIG IP Administrator wants to add a new VLAN (VLAN 40) to an LACP trunk (named LACP01) connected to the BIG-IP device Mufti VLANS exist on LACPO1. Which TMSH command should the BIG IP Administrator issue to add the new VLAN to the existing LACP trunk?

Options

  • Acreate net vlan VLAN40 (interfaces add (LACP01 {lagged)) tag 40}
  • Bcreate net vlan VLAN40 {interfaces replace-all-with {LACP01{tagged}} tag 40}
  • Ccreate net vlan VLAN40 interfaces replace all with {LACP01 {untagged)} tag 40}
  • Dcreate net vlan VLAN40 {interfaces add {LACP01 {untagged}} tag 40}

How the community answered

(16 responses)
  • A
    6% (1)
  • B
    75% (12)
  • C
    13% (2)
  • D
    6% (1)

Why each option

To add a new VLAN to an existing LACP trunk carrying multiple VLANs, the VLAN must be created with tagged interfaces since 802.1Q tagging is required when multiple VLANs share a single trunk.

Acreate net vlan VLAN40 (interfaces add (LACP01 {lagged)) tag 40}

Option A uses the invalid keyword 'lagged' instead of 'tagged', which is not valid TMSH syntax for specifying a tagged trunk interface.

Bcreate net vlan VLAN40 {interfaces replace-all-with {LACP01{tagged}} tag 40}Correct

The command uses 'replace-all-with' which is the correct TMSH syntax for specifying interfaces during a create operation, and specifies 'tagged' because LACP01 already carries multiple VLANs - IEEE 802.1Q tagging is required to distinguish frames from different VLANs on the shared trunk.

Ccreate net vlan VLAN40 interfaces replace all with {LACP01 {untagged)} tag 40}

Option C uses 'untagged' which would only allow a single VLAN on the interface - this directly conflicts with the fact that multiple VLANs already share LACP01, since an interface can only be untagged for one VLAN.

Dcreate net vlan VLAN40 {interfaces add {LACP01 {untagged}} tag 40}

Option D also uses 'untagged', which is incompatible with a multi-VLAN trunk because untagged membership is limited to one VLAN per physical or aggregate interface.

Concept tested: BIG-IP TMSH VLAN creation on tagged LACP trunk

Source: https://techdocs.f5.com/en-us/bigip-16-1-0/big-ip-tmsh-reference/modules/net/net-vlan.html

Topics

#TMSH#LACP trunk#VLAN#interface configuration

Community Discussion

No community discussion yet for this question.

Full 101 Practice