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

Traditional BGP loop detection mechanisms may detect a loop in the VPRN scenario, which in fact is not present.

The Nokia 7750 SR accepts routes containing AS_PATH loops by default.

When the CLI command "config>router>bgp# loop-detect discard-route" is used, the Nokia 7750 SR sends a notification to the remote peer and drops the BGP session.

In VPRN implementations where the CE-PE protocol is BGP, it is possible for separate sites of the same customer to use the same BGP autonomous system number.

Show service all

Show service id detail

Show service id base

Show service id bindings

Show service sap-using

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

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.

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.

These routes will not appear on CE-B

Type 1 LSAs

Type 3 LSAs

Type 5 LSAs

Type 7 LSAs

VPN-IPv4 routes for all PE system addresses in AS 1000

BGP labeled IPv4 routes for all PE system addresses in AS 1000

VPN-IPv4 routes for all PE system addresses in AS 5000

BGP labeled IPv4 routes for all PE system addresses in AS 5000

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

MP-eBGP exchange of VPN-IPv4 routes between ASBRs residing in different autonomous systems.

MP-eBGP exchange of labeled IPv4 routes between route reflectors residing in different autonomous systems.

A VRF-to-VRF connection at the autonomous system border routers.

MP-eBGP exchange of VPN-IPv4 routes between PEs residing in different autonomous systems.

The VPRN ID must be the same value as is used in the vrf-target command

The VPRN ID must be the same value as is used in the route-distinguisher command

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

The vrf-target command is mandatory

There is nothing wrong with this configuration

0 BGP and 2 MP-BGP sessions

2 BGP and 0 MP-BGP sessions

2 BGP and 1 MP-BGP sessions

2 BGP and 2 MP-BGP sessions

1 BGP and 2 MP-BGP sessions

An MP-BGP update carries an MPLS label that is used as the service label for a VPRN.

There can be multiple Route Targets per route in an MP-BGP update.

There can only be one Route Distinguisher per route in an MP-BGP update.

On a specific PE, the MP-BGP updates for prefixes from a single VPRN carry different labels.

Traditional BGP attributes and MP-BGP attributes are present in an MP-BGP update.

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.

One label per route

One label per next-hop

One label per VRF

One label per prefix

One label per tunnel

Open

Update

Route Refresh

Notification

show router 10 bgp routes vpn-ipv4

show router bgp routes

show router bgp routes vpn-ipv4

show router route-table

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

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

Either a hub and spoke or an extranet VPRN

An extranet VPRN

A hub and spoke VPRN

Either a full mesh or a hub and spoke VPRN

MP-iBGP is used between PE1 and ASBR1 to exchange VPN-IPv4 routes.

eBGP is used between ASBR1 and ASBR2 to exchange IPv4 routes.

MP-eBGP is used between PE1 and PE2 to exchange VPN-IPv4 routes.

MP-eBGP is used between ASBR1 and ASBR2 to exchange labeled IPv4 routes.

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.

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.

iBGP

eBGP

MP-iBGP

MP-eBGP

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 route update sent from PE1.

The route update sent from PE2.

The route update sent from ASBR1.

The route update sent from ASBR2.

It requires the configuration of back-to-back VRFs between ASBR routers in different autonomous systems

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

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

It uses conventional eBGP to distribute unlabeled IPv4 routes between ASBR routers in different autonomous systems.

The ability to offer Internet connectivity and a variety of services over a single CSC VPRN interface.

The ability to maintain its own backbone.

The ability to learn system addresses of network provider PEs.

There is no need to manage end-customer services.

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