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

To create a LAG interface, you need to perform two actions: enable LAG on the chassis and on each member interface. The first action is to configure the chassis stanza with the aggregated-devices statement and specify the number of LAG interfaces and the link-speed for each interface. The second action is to configure each member interface with the family ethernet-switching statement and the aggregated-ether-options statement with the lacp option. The name of the first LAG interface is not relevant, as long as it matches the name of the aggregated interface under the interfaces stanza. The name can be ae0, ae1, or any other valid name. References:

Enterprise Routing and Switching, Specialist (JNCIS-ENT) - Juniper Networks

Enterprise Routing and Switching, Specialist (JNCIS-ENT) - Juniper Networks

[Junos OS Layer 2 Configuration Guide - TechLibrary - Juniper Networks]

[Junos OS Layer 2 Configuration Guide - TechLibrary - Juniper Networks]

B  is correct because duplex and speed settings are required to match on both participating devices.  According to the Juniper Networks documentation 1 , all the interfaces in a LAG must have the same speed and be in full-duplex mode. This ensures that the LAG can operate as a single logical link without any performance or compatibility issues.

C  is correct because member links are not required to be contiguous ports.  According to the Juniper Networks documentation 2 , you can group any Ethernet interfaces on a switch into a LAG, regardless of their physical location or slot number. This provides flexibility and scalability for configuring LAGs on switches.

 References:

Enterprise Routing and Switching, Specialist (JNCIS-ENT) - Juniper Networks

Enterprise Routing and Switching, Specialist (JNCIS-ENT) - Juniper Networks

Juniper Networks Certified Specialist, Enterprise Routing & Switching …

Juniper Networks Certified Specialist, Enterprise Routing & Switching …

[Configuring Layer 2 Firewall Filters - TechLibrary - Juniper Networks]

[Understanding Firewall Filter Terms - TechLibrary - Juniper Networks]

BGP has a simple loop prevention mechanism for eBGP that checks the AS path for its own AS number. However, this mechanism does not work for iBGP, since all routers in the same AS have the same AS number. Therefore, iBGP has two additional rules to prevent routing loops within an autonomous system:

A router does not advertise a route learned from an iBGP neighbor to another iBGP neighbor. This rule ensures that a route does not loop back to the original iBGP router through another iBGP path.

A router does not accept a route learned from an iBGP neighbor if the next hop is not reachable via an IGP. This rule ensures that a router does not forward packets to an unreachable next hop.

These two rules imply that iBGP sessions must be configured as a logical full mesh, meaning that every iBGP router must have a direct iBGP session with every other iBGP router in the same AS. This way, every iBGP router can learn the best route from the eBGP routers and use the IGP to reach the next hop. A logical full mesh does not require a physical full mesh, meaning that iBGP routers do not have to be directly connected. They can use intermediate routers to establish iBGP sessions, as long as the IGP can reach the next hop.

A logical full mesh can be challenging to scale and maintain, especially for large ASes with many iBGP routers. Therefore, some alternatives to the full mesh requirement have been developed, such as route reflectors and confederations. These alternatives relax the iBGP rules and introduce additional attributes and mechanisms to prevent routing loops, such as originator ID and cluster list. References:

BGP Fundamentals

BGP - eBGP loop prevention mechanism same AS number

Loop Prevention in BGP Routing

A  is correct because the interface is configured as a disabled port. A disabled port does not forward any traffic, including DHCP packets.  Therefore, DHCP snooping cannot learn any MAC addresses or lease information from a disabled port 1 .

C  is correct because the interface is configured as a trunk port.  By default, all trunk ports on the switch are trusted for DHCP snooping 2 . This means that DHCP snooping does not inspect or filter any DHCP packets received on a trunk port.  Therefore, DHCP snooping does not add any entries to the snooping database for a trunk port 2 .

The static route to the 0.0.0.0/0 network has a next hop of xe-0/0/0.0, which is a local interface. BGP does not accept static routes with a local interface as the next hop, because it cannot advertise them to other BGP peers. BGP requires a valid IP address as the next hop for static routes that are redistributed into BGP. To fix this issue, the static route should have a next hop of an IP address that is reachable via the xe-0/0/0.0 interface, such as the IP address of the eBGP neighbor. Alternatively, the next hop can be modified by using a route map when redistributing the static route into BGP12.

The other options are not correct because:

The as-path parameter is not required for redistributing static routes into BGP. The as-path attribute is automatically set by BGP when advertising routes to other BGP peers3.

A community string is not required for redistributing static routes into BGP. A community is an optional attribute that can be used to group routes and apply policies to them4.

The no-readvertise feature is not specified in the configuration. The no-readvertise feature is used to prevent routes learned from one iBGP peer from being advertised to another iBGP peer5.