JN0-351 Exam Dumps - Juniper JNCIS-ENT Questions and Answers

The default hello interval on an OSPF interface depends on the network type of the interface. For point-to-point and broadcast network types, the default hello interval is 10 seconds. For non-broadcast and point-to-multipoint network types, the default hello interval is 30 seconds. The hello interval is the time between sending hello packets to establish and maintain neighbor adjacencies. The hello interval can be configured manually on each interface using the  ip ospf hello-interval  command. References:

OSPF Hello and Dead Interval - NetworkLessons.com

OSPF Hello and Dead Interval: Operation and Configuration

Adjusting OSPF Timers - Cisco IOS Cookbook, 2nd Edition

ospf timer hello - WLAN AC V200R010C00 Command Reference - Huawei

OSPF Timers – Hello and Dead Intervals - Packet Lab

A route reflector is a BGP router that is allowed to break the iBGP loop avoidance rule and advertise routes received from an iBGP peer to another iBGP peer under specific conditions 1 .  A route reflector can have three types of peerings: EBGP neighbor, IBGP client neighbor, and IBGP non-client neighbor 2 .  A cluster is a group of route reflectors and their clients that are fully meshed 3 .  The cluster ID is a 4-byte value that identifies the route reflector cluster and is carried in the ORIGINATOR_ID attribute of the BGP update message 4 . The cluster ID is used to prevent routing loops among route reflectors and their clients.  If a route reflector receives a route with its own cluster ID, it discards the route 5 . Therefore, the cluster ID is required to prevent routing loops when using route reflectors.

The maximum allowable MTU size for a default GRE tunnel without IPv4 traffic fragmentation is 1476 bytes 1 .  This is because GRE packets are formed by the addition of the original packets and the required GRE headers 1 .  These headers are 24-bytes in length and since these headers are added to the original frame, depending on the original size of the packet we may run into IP MTU problems 1 .  The most common IP MTU is 1500-bytes in length (Ethernet) 1 .  When the tunnel is created, it deducts the 24-bytes it needs to encapsulate the passenger protocols and that is the IP MTU it will use 1 .  For example, if we are forming a tunnel over FastEthernet (IP MTU 1500) the IOS calculates the IP MTU on the tunnel as: 1500-bytes from Ethernet - 24-bytes for the GRE encapsulation = 1476-Bytes 1 .

The exhibit shows the output of the command  show vlans brief , which displays brief information about VLANs and their associated interfaces 1 .

The output has four columns: Routing instance, VLAN name, Interfaces, and Tagging.

The * symbol indicates that the interface is active, meaning that it is up and forwarding traffic 1 .  This can be verified by the command  show interfaces terse , which displays the status of the interfaces 2 .

BGP is a routing protocol that operates between autonomous systems (AS). An AS is a group of routers under a single administrative control. BGP can be classified into two types: internal BGP (IBGP) and external BGP (EBGP). IBGP is the BGP communication between routers within the same AS, while EBGP is the BGP communication between routers in different AS. BGP uses the AS_PATH attribute to record the AS numbers that the route has passed through, and uses it to prevent routing loops and select the best path.

In this scenario, you want to add a second ISP connection and remove the default route to the existing ISP. This means that you want to have more control over the routing decisions and use BGP to exchange routes with both ISPs. To do this, you need to deploy the BGP protocol in your network and configure both IBGP and EBGP sessions. The correct statements about BGP in this scenario are:

IBGP peers advertise routes received from EBGP peers to other IBGP peers. This is the default behavior of IBGP, as it allows the routers within the same AS to learn the routes from different EBGP peers and select the best exit point. However, IBGP has a rule that it does not advertise routes received from IBGP peers to other IBGP peers, to avoid creating routing loops. Therefore, option B is correct and option C is incorrect. To overcome this rule, IBGP requires a full mesh topology, where every IBGP router is directly connected to every other IBGP router, or a route reflector or confederation design, where some IBGP routers act as intermediaries to reflect or aggregate the routes to other IBGP routers.

EBGP peers advertise routes received from IBGP peers to other EBGP peers. This is the default behavior of EBGP, as it allows the routers in different AS to exchange routes and reachability information. However, EBGP has a rule that it does not advertise routes received from EBGP peers to other EBGP peers, to avoid creating routing loops. Therefore, option D is correct and option A is incorrect. To overcome this rule, EBGP uses the AS_PATH attribute to filter out the routes that contain its own AS number, or uses route maps or policies to control the route advertisement. IBGP does not update the next-hop attribute to ensure reachability within an AS, as the next-hop attribute is preserved by IBGP. Instead, IBGP relies on an underlying IGP (Interior Gateway Protocol) to provide reachability to the next-hop.

Redundant Trunk Groups (RTGs) on EX Series switches provide a simple solution for network recovery when a trunk port on a switch goes down 1 .  They are configured on the access switch and contain two links: a primary or active link, and a secondary link 1 .  Therefore, option B is correct because if the active link fails, the secondary link automatically starts forwarding data traffic without waiting for normal spanning-tree protocol convergence 1 .

Option D is also correct.  In a typical enterprise network composed of distribution and access layers, RTGs are used where one Access switch is connected to two different uplink switches 2 .  This implies that RTGs must be connected to the same aggregation switch 2 .

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 .

B  is correct because the loops do not exist is one of the conditions that are verified by the receiving router to ensure that the received BGP route is valid.  A loop in BGP means that a route has been advertised by the same AS more than once, which can cause routing instability and inefficiency 1 .  To prevent loops, BGP uses the AS-path attribute, which lists the AS numbers that a route has traversed from the origin to the destination 2 .  The receiving router checks the AS-path attribute of the received route and discards it if it finds its own AS number in the list 2 . This way, BGP avoids accepting routes that contain loops.

C  is correct because the next hop is reachable is one of the conditions that are verified by the receiving router to ensure that the received BGP route is valid.  The next hop is the IP address of the next router that is used to forward packets to the destination network 3 .  The receiving router checks the next hop attribute of the received route and verifies that it has a valid route to reach it 3 .  If the next hop is not reachable, the received route is not usable and is rejected by the receiving router 3 . This way, BGP ensures that only feasible routes are accepted.