customer's requirements]
Refer to exhibit from a customer's Aruba CX switch.
show interface vxlan vni vteps
VNI : 150 VLAN : 150
Routing : Disabled VRF : default
Vxlan-status : operational
VTEPs
Origin Source Destination VTEP-STATUS
static 172.17.255.2 172.17.255.1 static operational
Which statement is true in this scenario?
The correct answer is A. The switch output clearly identifies the VTEP origin as ''static,'' and the VNI is mapped to VLAN 150 with routing disabled. In ArubaOS-CX static VXLAN, the administrator manually configures the VXLAN interface, source IP address, VNI, and peer VTEP. Aruba documentation for static VXLAN states that the peer VTEP IP address is explicitly defined with the vtep-peer command. Option B describes EVPN-VXLAN behavior, where BGP EVPN is used as the control plane to advertise MAC/IP and VTEP reachability dynamically. That is not what the output shows; the displayed origin is static. Option C is unsupported by the exhibit because no license state or scale limit is shown. Option D is incorrect because VXLAN interoperability depends on protocol support, configuration, MTU, underlay reachability, and feature compatibility, not on both sites using the exact same CX switch model. Reference/topics: ArubaOS-CX VXLAN, static VTEP configuration, VNI-to-VLAN mapping, underlay/overlay validation.
Currently there are no comments in this discussion, be the first to comment!