Most Recent Juniper JN0-664 Exam Dumps

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

PIM sparse mode (PIM-SM) is a multicast routing protocol that uses a pull model to deliver multicast traffic. In PIM-SM, routers with receivers send join messages to their upstream neighbors toward a rendezvous point (RP) or a source-specific tree (SPT). The RP or SPT acts as the root of a shared distribution tree for a multicast group. Traffic is only forwarded to routers that request to join the distribution tree by sending join messages. PIM-SM does not flood traffic to all routers or prune routers without receivers, as PIM dense mode does.

EVPN is a solution that provides Ethernet multipoint services over MPLS networks. EVPN uses BGP to distribute endpoint provisioning information and set up pseudowires between PE devices. EVPN uses different route types to convey different information in the control plane. The following are the main EVPN route types:

Type 1 - Ethernet Auto-Discovery Route: This route type is used for network-wide messaging and discovery of other PE devices that are part of the same EVPN instance. It also carries information about the redundancy mode and load balancing algorithm of the PE devices.

Type 2 - MAC/IP Advertisement Route: This route type is used for MAC and IP address learning and advertisement between PE devices. It also carries information about the Ethernet segment identifier (ESI) and the label for forwarding traffic to the MAC or IP address.

Type 3 - Inclusive Multicast Ethernet Tag Route: This route type is used for broadcast, unknown unicast, and multicast (BUM) traffic forwarding. It also carries information about the multicast group and the label for forwarding BUM traffic.

Type 4 - Ethernet Segment Route: This route type is used for multihoming scenarios, where a CE device is connected to more than one PE device. It also carries information about the ESI and the designated forwarder (DF) election process.

To reduce the impact of suboptimal routing in OSPF and OSPFv3 after devices reboot, you can use the overload feature to prevent a router from being used as a transit router for a specified period of time. This allows the router to stabilize its routing table before forwarding traffic for other routers. To enable the overload feature, you need to do the following:

For OSPF, configure the overload statement under [edit protocols ospf] hierarchy level. You can also specify a timeout value in seconds to indicate how long the router should remain in overload state after it boots up. For example, set protocols ospf overload timeout 900 means that the router will be in overload state for 15 minutes after it boots up.

For OSPFv3, configure the overload statement under [edit protocols ospf3] hierarchy level. You can also specify a realm (ipv4-unicast or ipv6-unicast) and a timeout value in seconds to indicate how long the router should remain in overload state after it boots up for each realm. For example, set protocols ospf3 realm ipv4-unicast overload timeout 900 means that the router will be in overload state for 15 minutes after it boots up for IPv4 unicast routing.

Intermediate System to Intermediate System (IS-IS) is a link-state routing protocol that supports Level 1 (L1), Level 2 (L2), or both (L1/L2) operations. The way IS-IS sends Hello (IIH) packets depends on whether the interface is point-to-point (P2P) or broadcast (LAN).

Evaluating the Answer Choices

Option A: 'If a point-to-point interface is in both L1 and L2, separate hello messages are sent for each level.'

Incorrect!

On point-to-point (P2P) interfaces, only one combined Hello message is sent for both L1 and L2.

IS-IS P2P Hellos include both Level 1 and Level 2 TLVs in the same message.

This statement is incorrect.

Option B: 'If a point-to-point interface is in both L1 and L2, one combined hello message is sent for both levels.'

Correct!

On point-to-point (P2P) links, IS-IS sends a single Hello message that includes TLVs for both L1 and L2.

This reduces overhead and simplifies adjacency formation.

This statement is correct.

Option C: 'If a broadcast interface is in both L1 and L2, separate hello messages are sent for each level.'

Correct!

On broadcast (LAN) interfaces, IS-IS sends separate Hello messages for L1 and L2.

This is because L1 and L2 use separate Designated IS (DIS) elections and different multicast addresses:

L1 Hellos: Sent to AllL1IS (01:80:C2:00:00:14)

L2 Hellos: Sent to AllL2IS (01:80:C2:00:00:15)

This statement is correct.

Option D: 'If a broadcast interface is in both L1 and L2, one combined hello message is sent for both levels.'

Incorrect!

As stated above, IS-IS sends separate Hello messages for L1 and L2 on broadcast interfaces because they have independent DIS elections.

This statement is incorrect.

Final Answer:

B. If a point-to-point interface is in both L1 and L2, one combined hello message is sent for both levels. C. If a broadcast interface is in both L1 and L2, separate hello messages are sent for each level.

Verification from Juniper Documentation

Juniper IS-IS Configuration Guide confirms:

Point-to-Point (P2P) interfaces send one combined Hello for both levels.

Broadcast interfaces send separate L1 and L2 Hellos due to separate DIS elections.

RFC 1195 (IS-IS Extensions for IPv4) specifies that broadcast networks require distinct Hellos per level.