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

show service id base

show router Idp bindings

show service id sdp detail

show service id vc-mtu

The prefix is located in an Autonomous System directly connected to this router.

There is a single Autonomous System between the local AS and the AS that originated the prefix.

There are two Autonomous Systems between the local AS and the AS that originated the prefix.

The prefix is located in Autonomous System 65100.

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.

The route learned from an eBGP peer.

The route with the lowest Origin.

The route with the lowest originator ID or BGP Identifier.

The route with the shortest AS path.

This command is required on all PE routers to distribute labeled IPv4 routes directly to PEs in remote AS.

This command is required on the ASBRs to exchange labeled IPv4 routes between the ASs.

This command is required on the route reflectors to exchange customer routes between ASs as labeled IPv4 routes.

This command is required on all PE routers to distribute labeled IPv4 routes to connected CEs.

iBGP

eBGP

MP-iBGP

MP-eBGP

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.

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.

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.

The routes learned from CE3 and PE1.

The route learned from CE3 only.

The routes learned from PE1 and PE2.

The routes learned from CE3 and PE2.

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.

On the PE facing the CE neighbor

On the CE facing the PE neighbor

On the P facing the PE neighbor

On the PE facing the PE neighbor

“Spoke_Sites”

“Hub_Site”

“Spoke_Sites” and “Hub_Site”

No communities should be imported.

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.

PE1 sends the data packet with three labels: the bottom label is a service label, the middle label is a BGP label, and the top label is an LDP label.

ASBR1 sends the data packet with one label: the BGP label.

ASBR1 sends the data packet with one label: the service label.

ASBR2 sends the data packet with three labels: the bottom label is a service label, the middle label is a BGP label, and the top label is an LDP label.

A 32 bit IPv4 address followed by a 64 bit Route Target

A 32 bit IPv4 address followed by a 64 bit Route Distinguisher

A 64 bit Route Target followed by a 32 bit IPv4 address

A 64 bit Route Distinguisher followed by a 32 bit IPv4 address

A 32 bit Route Distinguisher followed by a 32 bit IPv4 address FA 32 bit Route Target followed by a 32 bit IPv4 address

Identify the customer network on the egress PE

Establish the LSPs between PE devices

Identify the egress PE in the MPLS domain

Identify the customer network on the ingress PE

Memory exhaustion in the provider core

Route leaking between the customer networks

CPU utilization for route processing

Unwanted packet forwarding between customer networks

In the CSC VPRN, configure an eBGP session between CSC-PE and CSC-CE and use the "advertise-label vpn-ipv4" CLI command to enable the advertisement of VPN-IPv4 routes.

When the customer carrier uses the same autonomous system number in various sites, use the "loop-detect off" CLI command to disable the loop detection functionality on CSC-CE and PE routers.

On the CSC-PE routers, use the "carrier-carrier-vpn" CLI command to configure the VPRN service as CSC.

Configure an iBGP session between PE1 and PE2 and use the "family vpn-ipv4" CLI command to directly exchange end-customer routes learned from CE1 and CE2.

OSPF

ISIS

MP-BGP

BGP

Targeted LDP

When the route is first received at the P from the PE

When the route from the CE is populated into the VRF at the PE

When the route from the PE is populated into the VRF at the CE

When the route is propagated from the PE to the CE

When the route is exported into the MP-BGP table from the VRF

A P router may forward customer packets to their destination without the presence of a route to that destination

The ingress PE router may forward customer packets to their destination without the presence of a route to that destination

The egress PE router may forward customer packets to their destination without the presence of a route to that destination

Any provider core router (P or PE) may forward customer packets to their destination without the presence of a route to that destination

It is an 8 byte value containing 3 fields

The Route Distinguisher must have the same value as the Route Target.

The Administrator field contains either an AS number or an IP number

To ensure uniqueness, Route Distinguishers are assigned by the IANA.

The Route Distinguisher is not used if the customer addresses do not overlap

The Assigned Number field must contain a public IP address

Participate in service provider core routing

P devices are not required to be MPLS enabled. MPLS is only required on the PE devices

Run a common routing protocol with the CE router

Must support MP-BGP

Do not have any connections to the CE

Must be aware of the VPRNs

Sap 1/1/1 create

Sap 1/1/1 customer 10 create

No shutdown

Neighbor 192.168.1.2

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.

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

1

3

5

7

10

Any CE device

Any PE device

Any P device

Any router in the service provider core

Any customer router