Pass the Nokia Service Routing Architect 4A0-115 Questions and answers with ExamsMirror

PEI consults the FDB of RVPLS 1 and forwards the traffic to the local interface of VPRN 11.

PEI encapsulates the packet with two labels: an outer transport label and an inner service label.

PE2 inspects the service label and determines that it is associated with RVPLS 2.

PE2 consults the FDB of RVPLS 2 and forwards the traffic to Host 2.

PEI populates this information into the local VPLS FDB.

Neighbors 10.10.10.2 and 10.10.10.3 have proxy-ARP enabled for the VPLS.

Neighbors 10.10.10.2 and 10.10.10.3 have a service that uses a network identifier of 10.

PEI uses VXLAN tunnels to reach neighbors 10.10.10.2 and 10.10.10.3.

VPLS 10 must be configured with two BGP instances on PE3 and PE4.

On PE3 and PE4, VPLS 10 must be configured with two different route-distinguisher values: one for VXLAN and another for MPLS.

On PE3 and PE4, VPLS 10 must be configured with two different route-target values: one for VXLAN and another for MPLS.

A BGP export policy is required on PE3 and PE4 to ensure that IMET routes originated with VXLAN encapsulation are not advertised to the peer across the core network.

All VPLS instances must be configured on all PES regardless of whether they have a local host or not.

EVPN IP-Prefix routes are used to populate the VPRN VRF tables.

The egress PE does not perform any Layer-3 route look up to forward traffic.

The ingress PE performs both Layer-2 and Layer-3 look ups when forwarding traffic between subnets.

The flooding list maintained by PEI for VPLS 20 contains three entries: PE2, PE3, and PE4.

PE3 advertises an IMET route to PEI when its VPLS 20's mesh-SDP becomes operationally UP.

PE3 signals a service label to PE4 when its VPLS 20 is enabled and is bound to an operational SDP.

PEI advertises a MAC route for MAC-OI when its VPLS 2(Ys SAP becomes operationally UP.

PE2 advertises this BGP update for a locally-configured VPWS service.

PEI uses this BGP update to build the flooding list of the associated service.

PEI uses MPLS label 524284 when sending traffic destined to

Neighbor 10.10.10.2 is connected to a multi-homed CE.

EVPN routes are advertised with a service label associated with the SBD VPLS.

IP-Prefix routes exchanged between PES include a non-zero gateway IP address as an overlay index.

EVPN MAC/IP routes are used to advertise the MAC and IP addresses of local hosts.

EVPN MAC/IP routes are used to advertise the MAC and IP addresses of SBD IRB interfaces.

An MP-BGP session that supports the advertisement of VPN-IPv4 routes is established between PE3 and PE4.

An MP-BGP session that supports the advertisement of EVPN routes is established between PEI and PE2.

On PE3, the routing table for VPRN 15 contains an entry for 10.10.1.0/24. This entry is resolved to MAC-OI as an overlay index.

On PE3, the routing table for VPRN 15 contains an entry for 10.10.4.0/24. This entry is resolved using a transport tunnel towards PEA.

The service distinguisher (label or VNI) is advertised with the MAC/IP EVPN update.

Route targets are used to uniquely identify routes between EVIS in the case of MAC address overlaps.

A PE uses a single MP-BGP session with a remote peer to exchange the routes for all EVIs.

A PE advertises locally-learned MAC addresses to remote PES using EVPN type-2 routes.

A PE uses the received updates to create aliasing lists to PES that are part of an all-active Ethernet segment.

A PE advertises an A-D per EVI route for each operational service defined on an Ethernet segment.

The updates include an Ethernet tag ID that is set to zero.

The updates are used to discover all the PES associated with an Ethernet segment.