Juniper JN0-351 - Enterprise Routing and Switching Specialist (JNCIS-ENT)

The exhibit shows the configuration of BFD liveness detection for BGP at the global level, which applies to all BGP neighbors by default 1 .  However, this configuration does not specify the session mode, which determines whether BFD uses single-hop or multihop mode to communicate with a neighbor 2 .

For single-hop BGP neighbors, which are directly connected on the same subnet, the session mode can be either automatic or single-hop.  For multihop BGP neighbors, which are not directly connected and require multiple hops to reach, the session mode must be multihop 2 .

Since your BGP neighbors are in different countries, they are likely to be multihop neighbors.  Therefore, you need to configure the session mode as multihop for each neighbor individually at the [edit protocols bgp group group-name neighbor address bfd-liveness-detection] hierarchy level 2 . For example:

protocols { bgp { group usa { neighbor 192.0.2.1 { bfd-liveness-detection { session-mode multihop; } } } group france { neighbor 198.51.100.1 { bfd-liveness-detection { session-mode multihop; } } } } }

If you do not configure the session mode for multihop neighbors, BFD will use the default mode of automatic, which will try to use single-hop mode and fail to establish a BFD session with the remote neighbor 2 . This will prevent BGP from using BFD to detect liveliness and failover.

Therefore, the answer  B  is correct, as you need to configure the BFD liveness detection on the BGP neighbor level with the appropriate session mode for multihop neighbors.

A RIB group is a configuration that allows a routing protocol to install routes into multiple routing tables in Junos OS. A RIB group consists of an import-rib statement, which specifies the source routing table, and an export-rib statement, which specifies the destination routing table or group.  A RIB group can also include an import-policy statement, which specifies one or more policies to control which routes are imported into the destination routing table or group 1 .

An import policy is a policy statement that defines the criteria for accepting or rejecting routes from the source routing table. An import policy can also modify the attributes of the imported routes, such as preference, metric, or community.  An import policy can be applied to a RIB group by using the import-policy statement under the [edit routing-options rib-groups] hierarchy level 1 .

Therefore, option A is correct, because an import policy is applied to the RIB group to control which routes are installed in the destination routing table or group. Option B is incorrect, because all routes in the source routing table are imported into the destination routing table or group, unless filtered by an import policy. Option C is incorrect, because a firewall filter is not used to install routes in the RIB groups; a firewall filter is used to filter packets based on various criteria. Option D is incorrect, because an export policy is not applied to the RIB group; an export policy is applied to a routing protocol to control which routes are advertised to other devices.

Link-state update packets are used to flood link-state advertisements (LSAs) among OSPF routers. The destination IP address of these packets depends on the network type and the state of the interface. On broadcast and point-to-point networks, OSPF uses two IP multicast addresses: 224.0.0.5 for all OSPF routers and 224.0.0.6 for all designated routers (DRs) and backup designated routers (BDRs)12. If the interface state is DR or BDR, the link-state update packets are sent to 224.0.0.5. Otherwise, they are sent to 224.0.0.63. On non-broadcast networks, such as Frame Relay or ATM, link-state update packets are sent as unicasts to each adjacent neighbor3. Therefore, the correct answer is A and D. References: Understanding OSPF Areas | Junos OS, How OSPF Works - IP Routing [Book] - O’Reilly Media, Link state packet - Wikipedia

An aggregate route is a route that summarizes multiple more specific routes into a single route advertisement. For example, an aggregate route to 10.0.0.0/8 can represent many routes to 10.x.x.x/24 subnets. An aggregate route has several purposes, such as:

To decrease the number of route advertisements: By consolidating multiple routes into one, an aggregate route reduces the size of the routing table and the amount of routing updates that need to be exchanged between routers. This can improve the scalability and efficiency of the network12.

To hide internal routes from external peers: By advertising only the aggregate route and not the more specific routes, an aggregate route can provide a level of abstraction and security for the internal network topology. This can prevent external peers from knowing the details of the internal routes and avoid potential attacks or misconfigurations13.

The other options are not correct because:

C. To allow external peers to see internal routes: This is the opposite of what an aggregate route does. An aggregate route hides the internal routes from external peers, not exposes them13.

D. To increase the number of route advertisements: This is also the opposite of what an aggregate route does. An aggregate route decreases the number of route advertisements, not increases them12.

Option A suggests that the MTU is not at least 1492 bytes.  This is correct because IS-IS requires a minimum MTU of 1492 bytes to establish adjacencies 1 .  If the MTU is less than this, IS-IS adjacencies will not be established 1 .

Option D suggests that the lo0 interface is not included as an IS-IS interface.  This is also correct because the loopback interface (lo0) is typically used as the router ID in IS-IS 1 .  If the loopback interface is not included in IS-IS, it could prevent IS-IS adjacencies from being established 1 .

Therefore, options A and D are correct.

The two reasons for the failure to form an adjacency in a network running IS-IS could be:

B. There is no configured ISO address on any IS-IS interface. IS-IS requires each router interface to have an ISO address configured.  Without this address, the routers cannot form an adjacency 1 .

D. The family iso configuration is missing from the adjacency interface. The ‘family iso’ configuration is essential for IS-IS to function correctly.  If this configuration is missing from the adjacency interface, it could prevent the formation of an adjacency 1 .

These explanations are based on the Enterprise Routing and Switching Specialist (JNCIS-ENT) documents and learning resources available at Juniper Networks 2 3 .

The output shown in the exhibit is a brief display of the Ethernet switching table, which shows the learned Layer 2 MAC addresses for each VLAN and interface 1 .

The command  show ethernet-switching table  displays the Ethernet switching table with brief information, such as the destination MAC address, the VLAN name, the forwarding state, and the interface name 1 .

The command  show route forwarding-table  displays the routing table information for each protocol family, such as inet, inet6, mpls, iso, and so on 2 . It does not show the Ethernet switching table or the MAC addresses.

The command  show ethernet-switching table extensive  displays the Ethernet switching table with extensive information, such as the destination MAC address, the VLAN name, the forwarding state, the interface name, the VLAN index, and the tag type 1 . It shows more details than the brief output shown in the exhibit.

The command  show route forwarding-table family ethernet-switching  displays the routing table information for the ethernet-switching protocol family, which shows the destination MAC address, the next-hop MAC address, and the interface name 3 . It does not show the VLAN name or the forwarding state.