4A0-106 Nokia Virtual Private Routed Networks Questions and Answers

CE2 forwards an unlabeled IP packet to PE2 via the VPRN interface.

PE2 pushes two labels on the IP packet and label-switches the packet to ASBR2.

ASBR2 pops one label from the IP packet and label-switches it to ASBR1.

ASBR1 pushes two labels on the IP packet and label-switches the packet to PEL.

"Spoke.Sites" and "Hub_Site"

"Spoke_Sites"

"Hub_Site"

No communities should be exported

The SoO attribute can be used to uniquely identify the site from which a PE learns routes.

Before a PE redistributes a VPN-IPv4 route, it can assign an SoO attribute to the route.

The SoO attribute can be used to prevent loops from a single site with multiple CE-PE connections.

The SoO attribute can be used as matching criteria when redistributing routes from the CE to the PE.

Distributing customer routing information between sites

Forwarding customer data packets

Providing an integrated billing solution

Maintaining separation between distinct customer networks

Allowing the implementation of Layer 3 devices in the provider core

192.60.100.0

10.10.10.6

10.10.10.3

192.50.1.1

The policy should be applied as an import policy on the PE connected to the main site of Customer 1.

The policy should be applied as an import policy on all the PEs connected to the sites of Customer 1.

The policy should be applied as an export policy on the PE connected to the main site of Customer 1.

The policy should be applied as an export policy on all the PEs connected to the sites of Customer 1.

The route-distinguisher value must be 64496:10 for successful VPRN operation.

An export policy is not required for successful VPRN operation.

The "family vpn-ipv4" command is required under the BGP configuration for successful VPRN operation.

The neighbor address should be 10.10.10.4 under the BGP configuration for successful VPRN operation.

The VPRN configuration on ASBR1 is correct.

Family vpn-ipv4

Family vprn-ipv4

Family vprn

Address-family vpn-ipv4

Address-family vprn-ipv4

Address-family vprn

This configuration is correct and complete.

This configuration is correct, but the interfaces must also be configured in the "configure router mpls" context.

There is no configuration required for LDP in the core network.

This configuration is correct but Targeted-LDP is also required.

T-LDP and LDP sessions with the other VPRN PE routers and the VPLS PE router

T-LDP sessions with the other VPRN PE routers and the VPLS PE router

LDP sessions with the other VPRN PE routers and the VPLS PE router

LDP sessions with the other VPRN PE routers, and both T-LDP and LDP sessions with the VPLS PE router

T-LDP and LDP sessions with the other VPRN PE routers and LDP sessions with the VPLS PE router

No need to build and maintain its own backbone.

The solution scales as the number of serviced customer carriers increases.

The solution scales as the number of VPNs offered by the customer carriers increases.

The ability to manage end-customer services.

The update is accepted and the route installed in the route table.

The update is accepted but the route will not be installed in the route table

The update is rejected

The peer session is dropped

On the CE under the OSPF context

On the PE under the BGP context

On the PE under the OSPF context

On the CE under the BGP context

This policy is not required.

The customer carrier network can be a pure IP network.

The customer carrier can provide Layer 2 and Layer 3 services to its end-customers.

If the customer carrier offers VPRN services, PE routers residing in different customer carrier sites must run iBGP between them to exchange IPv4 routes.

If the customer carrier offers VPRN services, the network provider stores the end-customer routes in its CSC VPRN.

Target:65100:2 and target:65100:3

Target:65100:1 and target:65100:2

Target:65100:1 and target:65100:3

Target:65100:1, target:65100:2 and target:65100:3

Two SDPs must be bound to the VPRN service on each PE.

Three SDPs must be bound to the VPRN service on each PE.

Five SDPs must be bound to the VPRN service on each PE.

Twelve SDPs must be bound to the VPRN service on each PE.

1

5

15

30

45

target:65100:1 only

target:65100:1 and target:65100:2

target:65100:1 and target:65100:3

target:65100:1, target:65100:2, and target:65100:3

ASBR1 includes label 131069 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to PEL

ASBR1 includes labels 131068 and 131069 in the route update sent to ASBR2.

Five routes: the local route, the two BGP routes learned from the local CE, and two tunneled routes.

Six routes: the local route, the two BGP routes learned from the local CE, and three tunneled routes.

Two routes: the local route and one tunneled route.

Three routes: the local route and two tunneled routes.

Two routes: the local route and one BGP route learned from the local CE.

CE2 forwards an unlabeled IP packet to PE2 via the VPRN interface.

PE2 pushes one label on the IP packet and label-switches it to ASBR2.

ASBR2 forwards an unlabeled IP packet to ASBR1.

ASBR1 pushes two labels on the IP packet and label-switches the packet to PE1.

Configuring iBGP sessions between PEs residing in different customer carrier sites.

Configuring a policy on each CSC-CE to advertise local PE addresses to the network provider.

Configuring a CSC VPRN on each CSC-PE with a SAP interface towards the attached CSC-CE.

Configuring an IES service on PEL

The customer carrier does not learn any network provider routes.

The network provider must learn the customer carrier PE and CE system addresses.

Routes exchanged between CSC-CE and CSC-PE are labeled.

The customer carrier PE system addresses are populated in the CSC VRF.

1

2

3

4

Full mesh of MP-BGP between all P devices

Full mesh of MP-BGP between PE devices

Route reflector configuration between PE devices

Confederation configuration between PE devices

ASBR1 includes label 131069 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to PE1.

ASBR1 includes labels 131068 and 131069 in the route update sent to ASBR2.

Customer carrier PE routers residing in different sites must run iBGP between them to exchange customers' routes.

MPLS can be used in the customer carrier network to improve scalability.

The customer carrier network can be a pure IP network.

A CSC VPRN is configured on the CSC-CE to forward data packets to the network provider.

MP-BGP, LDP, RSVP-TE

LDP, RSVP-TE, GRE

MP-BGP, RSVP-TE, GRE

MP-BGP, LDP

MP-BGP only

PE1 advertises 64496:1:192.168.1.0/27 route update to ASBR1.

PE2 advertises 192.168.1.0/27 route update to CE2.

ASBR1 advertises 64496:1:192.168.1.0/27 route update to ASBR2.

ASBR2 advertises 64497:1:192.168.1.0/27 route update to PE2.