Free JN0-649 Exam Dumps Preview

internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) are the Multicast Group Membership Discovery (MGMD) protocols

Type 2 route, MAC with IP advertisement route--Type 2 routes are per-VLAN routes, so only PEs that are part of a VNI need these routes. EVPN allows an end host's IP and MAC addresses to be advertised within the EVPN Network Layer reachability information (NLRI). This allows for control plane learning of ESI MAC addresses. Because there are many Type 2 routes, a separate route-target auto-derived per VNI helps to confine their propagation. This route type is supported by all EVPN switches and routers. Type 5 route, IP prefix Route--An IP prefix route provides encoding for inter-subnet forwarding. In the control plane, EVPN Type 5 routes are used to advertise IP prefixes for inter-subnet connectivity across data centers. To reach a tenant using connectivity provided by the EVPN Type 5 IP prefix route, data packets are sent as Layer 2
Ethernet frames encapsulated in the VXLAN header over the IP network across the data centers.

The forbidden mode does not register or declare VLANs. You can change the registration mode of a specific interface to forbidden. An interface in forbidden registration mode does not participate in MVRP even if MVRP is enabled on the switch. https://www.juniper.net/documentation/us/en/software/junos/multicast-l2/topics/topic-map/mvrp.html MVRP is disabled by default on the switches and, when enabled, affects only trunk interfaces. Once you enable MVRP, all VLAN interfaces on the switch belong to MVRP (the default normal registration mode) and those interfaces accept PDU messages and send their own PDU messages. forbidden--The interface does not register or declare VLANS (except statically configured VLANs).

BUM Traffic Forwarding
Junos devices that use MPLS encapsulation for EVPNs can only use ingress replication at this time.
Ingress replication means, to flood traffic to remote PE routers, the traffic has to be replicated, once for
each remote PE router.
The EVPN label for this BUM traffic is learned per PE router from the route type 3, inclusive multicast Ethernet tag route.
This table shows the format of the inclusive multicast Ethernet tag route.
All-Active Redundancy (4)
This diagram shows the format of the type 1 route, A-D route per ES. The split horizon label is advertised as part of an extended community attached to the type 1 route. The split horizon label is also called the ESI label. The extended community also indicates what type of redundancy mode is used for this given ESI: single-active represented by binary 1 or active-active represented by binary 0.

Access interfaces in an L2PT-enabled VLAN should not receive L2PT-tunneled PDUs. If an access interface does receive L2PT-tunneled PDUs, there might be a loop in the network, and the device will shut down the interface.

https://www.juniper.net/documentation/us/en/software/junos/multicast-l2/topics/topic-map/layer-2-protocol-tunneling.html

https://www.juniper.net/documentation/us/en/software/junos/user-access/topics/topic-map/mac-radius-authentication-switching-devices.html

You can configure MAC RADIUS authentication on an interface that also allows 802.1X authentication, or you can configure either authentication method alone.

If both MAC RADIUS and 802.1X authentication are enabled on the interface, the switch first sends the host three EAPoL requests to the host. If there is no response from the host, the switch sends the host's MAC address to the RADIUS server to check whether it is a permitted MAC address. If the MAC address is configured as permitted on the RADIUS server, the RADIUS server sends a message to the switch that the MAC address is a permitted address, and the switch opens LAN access to the nonresponsive host on the interface to which it is connected.

You can set up captive portal authentication on your switch to redirect all Web browser requests to a login page that requires users to input a username and password before they are allowed access. Upon successful authentication, users are allowed access to the network and redirected to the original page requested. Junos OS provides a customizable template for the captive portal window that allows you to easily design and modify the look of the captive portal login page. You can modify the design elements of the template to change the look of your captive portal login page and to add instructions or information to the page. You can also modify any of the design elements of a captive portal login page. The first screen displayed before the captive login page requires the user to read the terms and conditions of use. By clicking the Agree button, the user can access the captive portal login page.
https://www.juniper.net/documentation/us/en/software/junos/user-access/topics/topic-map/user-authentication-captive-portal.html