Nokia 4A0-106 Dumps

PE1 pushes an LDP transport label.

CSC-CE1 pops the LDP label and pushes a BGP label.

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

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

CE1 forwards the data packet to PE1 via the VPRN 20 interface.

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

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

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

Allow routes to be exchanged between all or selected sites of one VPRN and all or selected sites of a second VPRN

Allow the service provider to provide multiple VPRNs with Internet access

Reduce the number of VPRN tunnels required

Simplify the administration of multiple VPRNs

Force all traffic in multiple VPRNs to pass through a single device

The ORF configuration must be done under the BGP neighbor context only.

When sending is enabled, the ORF function takes the route target list configured in all outbound policies and pushes this list to the peer by default.

When configuring ORF, the session with the peer must be cleared/reset for the new capability negotiation to take place.

When Outbound Route Filtering is configured, both the sending and acceptance of ORF are enabled by default.

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

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

Targeted-LDP

BGP

MP-BGP

RSVP-TE

Family vpn-ipv4

Family vprn-ipv4

Family vprn

Address-family vpn-ipv4

Address-family vprn-ipv4

Address-family vprn

The PE will install a maximum of 40 prefixes into the customer vrf and generate a log message when 40 routes are received

The PE will install a maximum of 40 prefixes into the customer vrf, and generate a log message both when 30 and 41 routes are received

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 10 routes are received and disable learning of new routes at 41

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 10 routes are received and drop the connection at 41

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 4 routes are received and disable learning of new routes at 41

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

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.

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.

"Spoke.Sites" and "Hub_Site"

"Spoke_Sites"

"Hub_Site"

No communities should be exported

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.

This configuration is correct and complete.

This configuration is correct, but the interfaces must also be configured in the "configure router mpls" context.

There is no configuration required for LDP in the core network.

This configuration is correct but Targeted-LDP is also required.

OSPF is not configured on the CE router

There is a problem with OSPF authentication

The operational MTU does not match

The PE and CE router have different OSPF interface types configured

None of the above

ASBR1 includes label 131069 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to PEL

ASBR1 includes labels 131068 and 131069 in the route update sent to ASBR2.

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.

Model B requires the configuration of back-to-back VRFs between the ASBRs in different autonomous systems.

Model B is highly scalable because the VPN-IPv4 routes are neither maintained, nor distributed by, the ASBRs.

There is a dependency between the route target used in different autonomous systems.

Model B supports the exchange of labeled IPv4 routes between ASBRs.

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.

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.

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.

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".

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.

“Spoke_Sites”

“Hub_Site”

“Spoke_Sites” and “Hub_Site”

No communities should be imported.

An MP-eBGP session between route reflectors in different autonomous systems to exchange IPv4 routes.

An MP-eBGP session between ASBRs to exchange labeled IPv4 routes.

An eBGP session between ASBRs to exchange IPv4 routes.

An MP-eBGP session between ASBRs to exchange VPN-IPv4 routes.

"Spoke.Sites" and "Hub_Site"

"Hub_Site"

"Spoke_Sites"

No communities should be imported

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.

iBGP

eBGP

MP-iBGP

MP-eBGP

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

1

2

3

4

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.