4A0-106 Exam Dumps - Nokia Virtual Private Routed Networks

The BGP session from PE to P is not operational

The BGP session between PEs is operational

The BGP session between PE and CE is not operational

The BGP session from PE to CE is operational

The BGP session between PEs is not operational

The route with the lowest MED.

The route with the shortest AS Path.

The route received from the lowest peer IP address.

The route with the lowest Origin.

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

oam vprn-ping source destination

oam vprn-ping source destination

vprn-ping router

Ping source

0

5

10

15

45

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.

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

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

Router R1

Router R2

Routers R1 and R2

Router R3

Router R4

Reduced number of VPN tunnels that need to be managed.

Optimal routing between all sites.

Limited configuration required on the hub PE device.

Site to site redundancy support.

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

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

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

The Nokia 7750 SR allows the setting of the maximum number of routes that can be accepted in a VRF for a VPRN service.

The "maximum-routes" command is used to specify the maximum number of remote routes that can be held within a VRF for a VPRN service.

When the "maximum-routes" command is used with the "log-only" parameter, new routes are still learned.

Once the "threshold" value is reached, no new routes are added to the VRF.

There will be increased memory usage on the PE

There will be increased CPU utilization on the PE

The CE will reject the overlapping prefix

The PE will not recognize the prefixes as being different

There is no issue with overlapping address space in a traditional Layer 3 VPN

Model B does not require the configuration of VPRN instances on ASBRs.

The ASBRs peer with each other to transport VPN-IPv4 routes between autonomous systems.

PE routers distribute VPN-IPv4 routes to their local ASBR.

One single ASBR is required in each AS to hold the routes for all VPRNs.

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

It is best used when a single VPN is required to provide Internet access, as well as to maintain VPN connectivity between different customer sites.

If there is no requirement for the VRF to contain the full Internet routing table, a default route to the Internet gateway router is sufficient.

Only one interface on the CE is required for both VPN and Internet connectivity.

The Nokia 7750 SR supports route leaking in full mesh and extranet VPRN topologies only.

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.

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.

A 32-bit Route Target followed by a 32-bit IPv4 address.

BGP sessions established between RR2 and the PEs support IPv4 and VPN-IPv4 address families.

BGP sessions established between RR1 and the PEs support the IPv4 address family only.

BGP sessions established between RR1 and the PEs support IPv4 and VPN-IPv4 address families.

BGP sessions established between RR2 and the PEs support the IPv4 address family only.

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.

The route update sent from PE1.

The route update sent from PE2.

The route update sent from ASBR1.

The route update sent from ASBR2.

Each customer site has a logically direct route to every other customer site.

It provides optimal routing between all sites.

It allows access between all CE devices and all sites participating in the same VRF.

It requires a full BGP mesh in the provider core.

The route with the shortest AS path.

The route with the lowest route or tunnel table cost to the NEXT_HOP.

The route with the highest local preference.

The route with the lowest originator ID or BGP identifier.

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.

MP-iBGP sessions must be configured between the PE routers in each AS.

LDP must be configured in each AS.

MP-eBGP sessions must be configured between the ASBRs.

The ASBRs must be configured with "enable-inter-as-vpn".

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.

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