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

192.168.10.1

192.168.20.1

10.10.10.1

10.10.10.6

To reduce the number of VPRN tunnels required.

To allow routes to be exchanged between all, or selected, sites of one VPRN, and all, or selected, sites of a second VPRN.

To simplify the administration of multiple VPRNs.

To allow network access between the headquarter sites of each VPRN service and a shared VPRN service offered by a third party.

eBGP is used for route and label exchange between CSC-CE and CSC-PE routers.

iBGP can be used to distribute routes between CSC-CE and PE routers.

MP-iBGP is used to advertise routes between the CSC-PE routers.

MP-iBGP is used to advertise end-customer and Internet routes directly between the PE routers.

Show service id base

Show router bgp routes

Show service id maximum-routes

Show router status

To limit the number of routes advertised from a customer site

To limit the number of routes learned from other customer sites CTo limit the size of the VRF table

To limit connectivity to selected customer networks

To perform packet filtering

One VPRN, one route distinguisher, and two route targets

Two VPRNs, one route distinguisher, and three route targets

Two VPRNs, two route distinguishers, and three route targets

One VPRN, two route distinguishers, and three route targets

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

ample Policy 3 should be applied as an export policy on the PE connected to the main site of Customer 2

ample Policy 3 should be applied as an export policy on both PEs connected to the main site of Customer 1 and the main site of Customer 2

ample Policy should be applied as an export policy on both PEs connected to the main site of Customer 1 and the main site of Customer 2

ample Policy should be applied as an export policy on all PEs connected to sites of Customer 1

A data packet destined to a remote AS is encapsulated with three labels within the originating AS.

The ASBR redistributes VPN-IPv4 updates to its ASBR eBGP peers.

PE routers in different ASes exchange IPv4 routes directly between each other using eBGP.

The advertising ASBR assigns a new label to the route before sending it via an MP-eBGP update to its ASBR peer.

1

3

5

7

10

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

ASBR1# show router 10 bgp routes vpn-ipv4

ASBR1# show router bgp routes

ASBR1# show router bgp routes vpn-ipv4

ASBR1# show router route-table

Memory exhaustion in the provider core

Route leaking between the customer networks

CPU utilization for route processing

Unwanted packet forwarding between customer networks

True

False

Identify the egress PE in the MPLS domain

Signal the egress VPRN ID

Identify the ingress PE in the MPLS domain

Transport route updates between PEs

It is the most scalable of the Inter-AS models.

VRF configuration is not required on the ASBRs.

Most routers that support VPRN functionality do not support model A by default.

It is not necessary to run MPLS at the boundary between autonomous systems.

The VPRN ID must match the value used in the vrf-target command.

The VPRN ID must match the value used in the route-distinguisher command.

The router-id command should not be used in this context.

The "no shutdown" command must be configured for the VPRN to be operationally UP.

PE1 pushes a VPN label, a BGP label, and an LDP transport label on the IP packet.

CSC-CE1 pops the LDP label and swaps the BGP label.

CSC-PE1 pops the BGP label, swaps the VPN label, and pushes an LDP transport label.

CSC-PE2 pops the LDP and VPN labels and pushes a BGP label.

Configuring labeled eBGP sessions between CSC-CE and CSC-PE routers.

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

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

Advertising the received system addresses of remote PEs using either iBGP or IGP/LDP within each customer carrier site.

“Spoke_Sites”

“Hub_Site”

“Spoke_Sites” and “Hub_Site”

No communities should be imported.

"Spoke.Sites" and "Hub_Site"

"Hub_Site"

"Spoke_Sites"

No communities should be imported

MP-BGP for exchanging customer routes with other PEs.

A routing protocol for exchanging customer routes with the CE.

A label signaling protocol for defining transport tunnels between the PE and CE.

MPLS for exchanging labels with other provider core devices.

RR2 advertises the VPN-IPv4 route update of 192.2.1.0/27 to RR1

RR1 advertises the VPN-IPv4 route update of 192.1.1.0/27 to RR2

RR2 advertises the VPN-IPv4 route update of 192.1.1.0/27 to PE2

PE1 advertises the VPN-IPv4 route update of 192.1.1.0/27 to RR1 and ASBRL

PE1

CE1

PE2 and PE3

CE2 and CE3

The customer carrier network must be MPLS-enabled.

VPRN instances are created on the CSC-CE routers.

All traffic exchanged between end-customers is carried over a single CSC VRF.

Customer carrier PEs residing in different sites must run MP-iBGP between them to exchange customers' routes.

It forwards the packet based on the label signaled by MP-BGP.

It decrements the TTL and forwards the packet based on the inner label.

It swaps the outer label then forwards the packet.

The P router does not perform any operations on labeled packets.

The primary VRF on PE1 contains routes learned from spoke sites.

All traffic between spoke sites must pass through CE1.

The secondary VRF on PE1 is used to route data packets from the hub CE to the spoke sites.

PE1 advertises the primary VRF routes to CE1.

A

B

C

D

PE1 pushes two labels on the IP packet and forwards it to ASBR1.

ASBR1 pops the LDP label, swaps the BGP label and forwards the IP packet to ASBR2.

ASBR2 forwards the IP packet with two labels to PE2.

PE2 pops the labels and forwards the unlabeled IP packet to its destination.

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