4A0-115 Nokia Ethernet Virtual Private Network Services Questions and Answers

The PE has proxy-ARP and dynamic-populate enabled for the VPLS.

The proxy-ARP table is populated by snooping IP packets received from remote PEs.

When the PE learns a local host IP address, it adds an entry into its proxy-ARP table.

The PE advertises a MAC/IP route that includes the MAC and IP address of a local host.

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.

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.

PEI advertises an EVPN IP-Prefix route for prefix 10.10.1.0/24 to PE3. The BGP update includes MAC-OI as on overlay index.

PEI advertises an EVPN MAC route for MAC-OI to PE3. The BGP update includes the route-target value configured for VPRN 15.

PE3 advertises a VPN-IPv4 route for prefix 10.10.1.0/24 to PE4. The BGP update includes an MPLS service label.

PE4 advertises an EVPN IP-Prefix route for prefix 10.10.1.0/24 to PE2. The BGP update includes MAC-04 as an overlay index.

PEI

PE2

PE3

PE4

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.

The local AC tag ID configured on PE2 must match the local AC tag ID configured on PEI.

The remote AC tag ID configured on PE2 must match the remote AC tag ID configured on PE3.

The local AC tag ID and the remote AC tag ID configured on PE2 must match.

The local AC tag ID configured on PEI must match the local AC tag ID configured on PE3.

The same tag ID must be configured for the local attachment circuit (AC) at each PE.

Each PE advertises a MAC route and an A-D per EVI route when its local AC becomes operationally UP.

The advertised A-D per EVI route includes a non-zero tag ID and a non-zero MPLS label.

Each PE verifies that the received tag ID matches its configured local AC tag ID.

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.