Pass the Juniper JNCIP-SP JN0-664 Questions and answers with ExamsMirror

The resolve-vpn parameter is a BGP option that allows a router to resolve labeled VPN-IPv4 routes using unlabeled IPv4 routes received from another BGP peer with family inet labeled-unicast configured. This option enables interprovider VPNs without requiring MPLS labels between ASBRs or using VRF tables on ASBRs. In this scenario, you need to configure the resolve-vpn parameter under [edit protocols bgp group external family inet labeled-unicast] hierarchy level on both ASBRs.

To allow Site 1 to access three VLANs that are located in Site 2 and Site 3, you need to configure three L2VPN routing instances on PE-1, one for each VLAN. Each L2VPN routing instance will have a different VLAN ID and a different VNI for VXLAN encapsulation. Each L2VPN routing instance will also have a different vrf-target export value to identify which VPN routes belong to which VLAN. This way, PE-1 can forward traffic from Site 1 to Site 2 and Site 3 based on the VLAN tags and VNIs.

https://www.juniper.net/documentation/us/en/software/junos/sampling-forwarding-monitoring/bgp/topics/concept/bgp-multipath-unequal-understanding.html

The auto-export parameter is a routing option that allows a routing instance to share routes with other routing instances or the master routing table. The auto-export parameter automatically exports routes from one routing instance to another based on the route target communities attached to the routes. In this scenario, the 10.101.1.0/24 route will be shared if the auto-export parameter is configured under [edit routing-options] hierarchy level.

In the context of Ethernet VPN (EVPN) and the behavior described in the exhibit, it's essential to understand the different EVPN route types and their specific functionalities. Here, CE-2 is receiving unicast traffic on both of its multihomed links to PE-2 and PE-3, but broadcast traffic is received only on one of these links.

**Explanation of EVPN Route Types**:

1. **Type 1 (Ethernet Auto-Discovery Routes)**:

- These routes are used for auto-discovery of Ethernet segments and for advertising VLAN membership.

- They do not directly influence the behavior described in the question.

2. **Type 2 (MAC/IP Advertisement Routes)**:

- These routes are used to advertise MAC addresses and IP-to-MAC bindings within the EVPN.

- They handle unicast traffic forwarding and are crucial for populating the MAC address tables on the PE devices.

- While important, they do not explain the selective broadcast behavior.

3. **Type 3 (Inclusive Multicast Ethernet Tag Routes)**:

- These routes are used to build multicast distribution trees for delivering broadcast, unknown unicast, and multicast (BUM) traffic.

- They ensure that BUM traffic is sent only once per Ethernet segment, preventing duplicate frames from being sent to multihomed CEs.

- This aligns with the behavior described where CE-2 receives broadcast traffic on only one link to prevent duplication.

4. **Type 4 (Ethernet Segment Routes)**:

- These routes are used to advertise the presence of an Ethernet segment and are crucial for Designated Forwarder (DF) election processes in multihoming scenarios.

- While relevant to multihoming, they are not directly responsible for the selective broadcast behavior.

**Conclusion**:

The behavior described, where CE-2 receives broadcast traffic on only one of its multihomed links, is controlled by Type 3 routes. These routes are specifically designed to handle inclusive multicast and broadcast traffic efficiently in EVPN environments, ensuring that such traffic is not duplicated across multiple links to the same CE.

**References**:

- Juniper Networks EVPN Documentation: [EVPN Overview](https://www.juniper.net/documentation/en_US/junos/topics/concept/evpn-overview.html)

- RFC 7432, BGP MPLS-Based Ethernet VPN: [RFC 7432](https://tools.ietf.org/html/rfc7432) provides detailed descriptions of EVPN route types and their functions.

- Junos OS EVPN Configuration Guide: [Junos OS EVPN Configuration Guide](https://www.juniper.net/documentation/en_US/junos/topics/topic-map/evpn.html)

https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/ref/statement/multihop-edit-protocols-bgp.html

IS-IS is an interior gateway protocol that uses link-state routing to exchange routing information among routers within a single autonomous system. IS-IS uses two types of addresses to identify routers and areas: system ID and area address. The system ID is a unique identifier for each router in an IS-IS domain. The system ID is 6 octets long and can be derived from the MAC address or manually configured. The area address is a variable-length identifier for each area in an IS-IS domain. The area address can be 1 to 13 octets long and is composed of high-order octets of the address. An IS-IS instance may be assigned multiple area addresses, which are considered synonymous. Multiple synonymous area addresses are useful when merging or splitting areas in the domain1. In this question, we have a network based on IS-IS with four routers (R1_1, R1_2, R2_1, and R2_2) belonging to area 0001. The area address for area 0001 is 49.0001. The NSEL byte for area 0001 is the last octet of the address, which is 01. The NSEL byte stands for Network Service Access Point Selector (NSAP Selector) and indicates the type of service requested from the network layer2. Therefore, the correct statement in this scenario is that the NSEL byte for area 0001 is 01.