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

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.

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

The VPRN ID must match the value 101 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.

Show router bgp routes

Show router route-table summary

Show router bgp routes vpn-ipv4 detail

Show router route-table

Signaled via MP-BGP and used to identify the egress PE.

Signaled via T-LDP and used to identify the customer VPRN.

Signaled via MP-BGP and used to identify the customer VPRN.

Signaled via RSVP and LDP and used to identify the egress PE.

Signaled via RSVP and LDP and used to identify the customer 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

192.60.100.0

10.10.10.6

10.10.10.3

192.50.1.1

Dual CEs connected to redundant PEs can provide redundancy within a single site.

Site redundancy can be achieved by dual homing a single CE to one or more PEs.

Provider core LSPs can be LDP-based or RSVP-based.

The provider core maintains a full mesh of LSP tunnels and MP-BGP sessions between all P devices.

PE1

PE2, PE3 and PE4

PE1, PE2, PE3 and PE4

This command is not required for the configuration of this PE hub and spoke VPRN.

Memory exhaustion in the provider core

Route leaking between the customer networks

CPU utilization for route processing

Unwanted packet forwarding between customer networks

0

5

10

15

45

the configuration is complete and correct.

'as-override' should be configured under the BGP context.

'as-override' should be configured under the group context.

'as-override' should not be part of this configuration.

MP-BGP, LDP, RSVP-TE

LDP, RSVP-TE, GRE

MP-BGP, RSVP-TE, GRE

MP-BGP, LDP

MP-BGP only

PE1 pushes an LDP transport label.

CSC-PE1 pops the BGP label and pushes two labels: a VPN label and an MPLS transport label.

CSC-PE2 pops the MPLS transport label and pushes a BGP label.

CSC-CE2 pops the BGP label and pushes an LDP transport label.

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.

PE1

RR1

ASBR1

ASBR2

Distributing the customer generated labels between sites

Distributing the customer routing information between

Forwarding the customer originated data packets to the appropriate destination

Forwarding the provider originated data packets to the appropriate customer site

Providing secure layer 3 routing exchange between sites

A

B

C

D

172.12.10.0/24, 172.12.20.0/24 and 172.0.0.0/16

172.12.0.0/16 only

172.12.10.0/24 and 172.12.20.0/24

172.0.0.0/16 only

Full mesh between all CE, PE and P devices

Full mesh between PE and P devices

Full mesh of P devices

Full mesh of PE devices

Full mesh between PE and CE devices

This approach is recommended when multiple sites advertise the same prefix.

This approach limits the opportunities for load balancing.

This approach requires additional memory on the PEs to store more routes.

This approach is recommended for extranet VPN.

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

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.

It defines the VPN membership

It defines which routes are imported into the vrf

It defines which routes are exported from the vrf

It is used to make IPv4 addresses unique

It is used as the VPN label

Router R1

Router R2

Routers R1 and R2

Router R3

Router R4

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

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

ASBR2 swaps the BGP label and pushes an LDP transport label.

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

"Blue-Only"

"Blue-Only" and "Blue-Green"

"Green-Only"

"Extranet-VPN-Green"

"Blue-Green"

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

Red VRF imports only "Internet"

Internet VRF imports only "Red-Only"

Red VRF imports "Internet" and "Red-Only"

Internet VRF imports only "Red-Only"

Red VRF imports only "Red-Only"

Internet VRF imports "Red-Only" and "Internet"

Red VRF imports "Internet" and "Red-Only"

Internet VRF imports only "Internet"

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

ASBR2 sends the IP packet with one label to ASBR1.

ASBR1 sends the IP packet with one label to PEL

PE1 pops one label off the IP packet and forwards it to CE1.