QUESTION: 21

You are using a single tenant data center with a bridged overlay architecture. In this scenario, how do hosts of the different virtual networks communicate with each other?

off-fabric using an external device
using anycast gateway addresses configured on the leaf devices
using EVPN Type 5 routes
using virtual gateway addresses configured on the spine

Answer(s): A

Explanation:

Understanding Bridged Overlay Architecture:
In a single-tenant data center using a bridged overlay architecture, virtual networks (VLANs) are typically isolated within the fabric, with traffic between these VLANs handled outside the fabric.

Communication Between Different Virtual Networks:
A . off-fabric using an external device: This is correct. In many bridged overlay architectures, communication between different virtual networks is handled off-fabric, often using an external router or firewall that connects the different VLANs. The fabric itself primarily provides Layer 2 connectivity within each VLAN, leaving inter-VLAN routing to be handled externally.
Data Center

Reference:

This design is common in smaller or simpler data center environments where a single tenant does not require complex on-fabric routing and prefers to handle inter-VLAN routing through dedicated devices.

Reveal Solution Next Question

QUESTION: 22

A local VTEP has two ECMP paths to a remote VTEP
Which two statements are correct when load balancing is enabled in this scenario? (Choose two.)

The inner packet fields are not used in the hash for load balancing.
The destination port in the UDP header is used to load balance VXLAN traffic.
The source port in the UDP header is used to load balance VXLAN traffic.
The inner packet fields are used in the hash for load balancing.

Answer(s): C,D

Explanation:

Load Balancing in VXLAN:
VXLAN uses UDP encapsulation to transport Layer 2 frames over an IP network. For load balancing across Equal-Cost Multi-Path (ECMP) links, various fields in the packet can be used to ensure even distribution of traffic.
Key Load Balancing Fields:
C . The source port in the UDP header is used to load balance VXLAN traffic: This is correct. The source UDP port in the VXLAN packet is typically calculated based on a hash of the inner packet's fields. This makes the source port vary between packets, enabling effective load balancing across multiple paths.
D . The inner packet fields are used in the hash for load balancing: This is also correct. Fields such as the source and destination IP addresses, source and destination MAC addresses, and possibly even higher-layer protocol information from the inner packet can be used to generate the hash that determines the ECMP path.
Incorrect Statements:
A . The inner packet fields are not used in the hash for load balancing: This is incorrect as the inner packet fields are indeed critical for generating the hash used in load balancing. B . The destination port in the UDP header is used to load balance VXLAN traffic: This is incorrect because the destination UDP port in VXLAN packets is typically fixed (e.g., port 4789 for VXLAN), and therefore cannot be used for effective load balancing.
Data Center

Reference:

Effective load balancing in VXLAN is crucial for ensuring high throughput and avoiding congestion on specific links. By using a combination of the source UDP port and inner packet fields, the network can distribute traffic evenly across available paths.

Reveal Solution Next Question

QUESTION: 23

Exhibit.

Host A is connected to vlan 100 on lead. Host B is connected to vlan 200 on leaf1. Host A and Host B ate unable to communicate. You have reviewed the touting and your hosts have the correct default route (.1)
Referring to the exhibit, which two commands will solve the problem? (Choose two.)

delete vlans vn200 13-interface irb.200
set interfaces irb unit 100 family inet address 192-168.100.1
set routing-options static route 0.0.0.0/0 next-hop 192.168.200.10
set vlans vn100 13-interface irb.100

Answer(s): C,D

Explanation:

In the provided network configuration, Host A is in VLAN 100 and Host B is in VLAN 200. The issue arises because these two hosts are unable to communicate, which indicates that either the interfaces are not properly linked to their respective VLANs, or there is a missing static route required for inter- VLAN routing.
Step-by-Step Analysis:
VLAN Assignment:
The exhibit shows that irb.200 is correctly associated with VLAN 200 in the configuration. However, there is no corresponding irb.100 for VLAN 100. Without irb.100, the network lacks the logical interface to handle routing for VLAN 100. Thus, adding irb.100 to VLAN 100 is necessary.
Command to solve this:

set vlans vn100 13-interface irb.100
Static Route Configuration:
For inter-VLAN routing to occur, a static route needs to be configured that allows traffic to pass between different subnets (in this case, between VLAN 100 and VLAN 200). The command set routing-options static route 0.0.0.0/0 next-hop 192.168.200.10 would add a static route that directs all traffic from VLAN 100 to the correct gateway (192.168.200.10), which is necessary to route traffic between the two VLANs.
Command to solve this:

set routing-options static route 0.0.0.0/0 next-hop 192.168.200.10 Explanation of Incorrect Options:
Option A (delete vlans vn200 13-interface irb.200): This would remove the logical interface associated with VLAN 200, which is not desired because we need VLAN 200 to remain active and properly routed.
Option B (set interfaces irb unit 100 family inet address 192-168.100.1): This command would incorrectly assign an IP address that does not correspond with the subnet of VLAN 100 (192.168.200.1/24). This could create a misconfiguration, leading to routing issues.
Data Center

Reference:

For a Data Center, proper VLAN management and static routing are crucial for ensuring that different network segments can communicate effectively, especially when dealing with separated subnets or zones like in different VLANs. This aligns with best practices in DCIM (Data Center Infrastructure Management) which stress the importance of proper network configuration to avoid downtime and ensure seamless communication between all critical IT infrastructure components. Ensuring that the correct interfaces are associated with the correct VLANs and having the proper static routes in place are both essential steps in maintaining a robust and reliable data center network.
This detailed analysis reflects best practices as noted in standard data center design and network configuration guides.

Reveal Solution Next Question

QUESTION: 24

Exhibit.

You want to enable the border leaf device to send Type 5 routes of local networks to the border leaf device in another data center.
What must be changed to the configuration shown in the exhibit to satisfy this requirement?

Move vrf-target target: 65000:1 to the evpn hierarchy.
Add a VLAN configuration with an 13-interface to the tenant1 routing instance.
Add encapsulation vxlan to the evpn hierarchy.
Change: 5001 in the route-distinguisher to : 10010.

Answer(s): A

Explanation:

In this scenario, you want the border leaf device to advertise Type 5 EVPN routes to another border leaf in a different data center. Type 5 routes in EVPN are used to advertise IP prefixes, which means that for proper route advertisement, you need to configure the correct settings within the evpn hierarchy.
Step-by-Step Analysis:
Understanding EVPN Type 5 Routes:
EVPN Type 5 routes are used to advertise IP prefixes across EVPN instances, which allow different data centers or networks to exchange routing information effectively.
VRF Target Setting:
The vrf-target configuration is crucial because it defines the export and import policies for the VRF within the EVPN instance. For EVPN Type 5 routes to be advertised to other border leaf devices, the vrf-target needs to be correctly configured under the evpn hierarchy, not just within the routing instance.
Command to solve this:

move vrf-target target:65000:1 to evpn
Other Options:
Option B: Adding a VLAN configuration would not address the requirement to advertise Type 5 routes.
Option C: Adding VXLAN encapsulation may be necessary for other scenarios but does not directly address the Type 5 route advertisement.
Option D: Changing the route-distinguisher will differentiate routes but does not impact the advertisement of Type 5 routes to other data centers. By moving the vrf-target to the evpn hierarchy, you enable the proper route advertisement, ensuring that the Type 5 routes for local networks are shared with other data center border leaf devices. This is aligned with best practices for multi-data center EVPN implementations, which emphasize the correct placement of routing policies within the EVPN configuration.

Reveal Solution Next Question

Free JN0-683 Exam Braindumps (page: 6)

QUESTION: 21

Explanation:

Reference:

QUESTION: 22

Explanation:

Reference:

QUESTION: 23

Explanation:

Reference:

QUESTION: 24

Explanation: