Question 22 - JN0-683 discussion

Understanding the Scenario:

EVPN-VXLAN deployments often involve scenarios where multiple tenants or applications require overlapping VLAN IDs, which can be managed using the mac-vrf routing instance type. This allows you to segregate traffic within the same VLAN ID across different tenants.

Host-facing Interface Configuration:

A . Host-facing interfaces must be configured using a service-provider style configuration: This is correct. In mac-vrf configurations, host-facing interfaces (those connecting end devices) typically follow a service-provider style configuration, where each customer or tenant's traffic is isolated even if overlapping VLAN IDs are used.

B . Host-facing interfaces must be configured using enterprise-style configuration: This is incorrect for mac-vrf instances because enterprise-style configurations are more common in simpler, less segmented networks.

Routing Instance Service Type:

D . The routing-instance service type can be VLAN-based: This is correct. The service type in mac-vrf can indeed be VLAN-based, which is particularly useful in scenarios where VLAN ID overlap is needed between different tenants or services.

Data Center

Reference:

The mac-vrf instance type is powerful for handling complex multi-tenant environments in EVPN-VXLAN, especially when dealing with overlapping VLAN IDs across different segments of the network.