Refer to the exhibit. The OTV adjacency fails to come up. Which set of commands on each switch resolves the issue?

Question

Exhibits

Options

• Aotv extend-vlan 5
• Botv extend-vlan 5
• Cotv extend-vlan 5
• Dno otv site-vlan 5,10-11

• A
  3% (1)
• B
  3% (1)
• C
  10% (3)
• D
  83% (24)

Explanation

Option D resolves the issue because OTV site-VLANs are never extended across the overlay - they exist solely for intra-site communication between OTV Edge Devices at the same physical location. If VLANs 5, 10, and 11 are designated as site-VLANs via otv site-vlan, OTV will actively block them from being stretched over the overlay fabric, which prevents the adjacency from forming when those VLANs are needed for extension. Running no otv site-vlan 5,10-11 removes that local-only restriction, allowing the VLANs to participate in the OTV overlay and the adjacency to come up.

Options A, B, and C (otv extend-vlan 5) are wrong because simply adding VLAN 5 to the extend list does not fix the underlying conflict - a VLAN configured as a site-VLAN cannot be extended regardless of what the extend-vlan list says; the site-VLAN designation takes precedence and will continue to suppress it.

Memory tip: Think of it as a "stay home" flag - otv site-vlan tells OTV those VLANs must stay home at the local site and will never leave over the overlay. If a VLAN has been told to stay home, telling it to also extend (otv extend-vlan) is a contradiction OTV resolves by keeping it local. Remove the flag first with no otv site-vlan, then it can travel.

No community discussion yet for this question.