Nokia 4A0-104 Dumps

Each router requires 1 VPLS service.

Each router requires 2 VPLS services.

Each router requires 1 SDP with 2 LSPs, one to each of the other 2 routers.

Each router requires 2 SDPs.

Each router requires 3 SDPs

Epipe

Fpipe

Apipe

Ipipe

Cpipe

Gpipe

Epipe

Apipe

Fpipe

Ipipe

Cpipe

ISIS, RIP, OSPF, static routes

BGP, ISIS, RIP, OSPF, static routes

BGP, RIP, OSPF, static routes, OSPF3

ISIS, RIP, OSPF, static routes, OSPF3

A route target is a BGP extended community used to identify the VRF table for a prefix at the receiving PE

A route target is a mechanism from which VPRN controls the distribution of VPN routing information.

Route target attributes are earned in a MP-BGP as attributes of the route.

A route target is used by the PE router to identify the VRF that a VPN-lPv4 prefix is associated with.

All of the above statements describe a route target

None of the above statements describe a route target

To test the ability of reaching the far-end IP address of an SDP within the SDP encapsulation

To determine the path MTU to the far-end IP address over an SDP.

To determine the service MTU of the service using an SDP.

To determine the presence of hosts using the service

2

3

4

5

6

10

vc-type null

vc-type ether

vc-type vlan

vc-type none

Yes. A routing policy is required to advertise routes between PE routers in a VPRN

No. A routing policy is not required; the default behavior on the 7750 SR is to advertise all VPRN routes between PE routers.

A routing policy is required only when BGP is used as the PE-CE routing protocol, as shown in the exhibit.

A CE1 system interface can not be advertised to PE2 since the CE routers are not aware of the VPRN.

1520

1540

1548

1556

Yes, A routing policy is required to advertise routes between PE routers in a VPRN regardless of the CE-PE routing.

Yes, A routing policy is required in this case because BGP is used as the PE-CE routing protocol.

No, a routing policy is not required. By default, the Alcatel-Lucent 7750 SR will advertise all VPRN routes between PE routers.

No, a routing policy is not required on PE1, but an import policy is required on PE2.

Each VRF table contains routes for a single VPRN.

Route targets are used to determine if a prefix belongs to a VRF.

Routes in the VRF table are advertised to the core routers.

VPN labels identify which VRF table should be used for a packet.

It will show the hops taken between service endpoints.

It will test the delay across the service.

It will test the SDPs of a service in both directions.

It will test the round-trip connectivity of the service.

The service label is swapped for a transport label during transport.

The transport label is used to forward packets between PEs.

The service label is used to identify which VPRN a packet belongs to.

Labels are initially added at the ingress PE.

VPN-IFV4 allows multiple customers to have overlapping IP addresses.

CE routers use VPN-IPv4 prefixes to differentiate between services.

PE routers are responsible for creating VPN-IPv4 prefixes.

A VPN-IFV4 prefix is composed of a route distinguisher (RD) and an IPv4 address.

The frame is dropped.

The frame's outer tag is changed to match the SAP, and it is accepted.

The frames outer tag is dropped, and the frame is accepted.

The frame's tags are removed, and the frame is accepted.

Routes from different customers with the same IPv4 address prefix are treated as equivalent by MP-BGP.

MP-BGP will advertise routes to other BGP sessions on the same PE without the need of policies.

The multi-protocol nature of MP-BGP allows VPRN routes to be converted into IPv4 routes in the provider core network.

MP-BGP is an enhanced version of BGP that can carry customer route prefixes for multiple VPRNs.

The labels are of local significance only, so other routers can use the same value.

10.10.10.1 has yet to send its own unique label.

Router R4 is using the same tunnel to send and receive to 10.10.10.1.

The service on 10.10.10.1 is down, so it is rejecting packets.

config>service>ies# interface "to-CE" customer customer-id create

config>service>ies# interface to CE create

config>service>ies# interface to CE

config>service>ies# interface "to-CE" create

sdp-ping

Isp-ping

svc-ping

sdp-mtu

Dedicates a separate port for each customer.

Performs ARP look-ups for each service.

Maintains a different IP routing table for each service.

Maintains a different MAC Forwarding Database for each service.

A-pipe

C-pipe

E-pipe

F-pipe

A VPLS service does not use an FDB.

The router reads the destination MAC address of packets passing through the service.

The router reads the source MAC address of packets passing through the service.

The router uses reverse ARP (RARP) to resolve the MAC addresses for unknown destinations.

The router is programmed with MAC addresses by the network administrator.

Change the service MTU of the VPLS to match the IES.

Set the ip-mtu of the IES service to match the service MTU of the VPLS service.

Change the MTU of the SDP attached to the VPLS to match the service MTU of the VPLS.

Set the DNF flag on the IES service.

The frame egresses from 1/1/1:6 with no VLAN tag.

The frame egresses from 1/1/1:6 with VLAN tag 5.

The frame egresses from 1/1/1:6 with VLAN tag 6.

The frame egresses from 1/1/1:6 with an inner VLAN tag of 5 and an outer VLAN tag of 6.

The default service MTU on a VPLS service is 1514 bytes.

The default IP MTU of an IES is set based on the network port MTU.

During VC label signaling, the VC MTU is verified and must match.

All of the above.

Spoke SDPs prevent loops in a VPLS.

Mesh SDPs and spoke SDPs can be used in the same VPLS.

A spoke SDP does not require the routers at both ends to be directly connected.

A mesh SDP is identical to a spoke SDP except for its flooding behavior.

TRUE

FALSE

TRUE

FALSE

configure router sdp sdp-id

configure service sdp sdp-id create

configure service mpls sdp sdp-id create

configure service gre sdp sdp-id create

configure service sdp sdp-id mpls create

1514

1526

1548

1556

1536

Layer 3 direct Internet access service.

Layer 2 point-to-point service.

Layer 2 multipoint-to-multipoint service.

Layer 3 IP multipoint-to-multipoint VPN service.

An outer label and a transport label.

An inner label and a service label.

A transport label and a service label.

An MPLS transport label

RSVP

IPCP

TLDP

PPP

Either RSVP or LDP

A virtual routing/forwarding table is created per IES service.

Only one IES service can be created for a single customer ID.

More than one IP interface can be created within a single IES service.

All IP interfaces created within the same IES service belong to the same customer

Configuring the physical port in access mode.

Configuring the physical port in network mode.

Enabling the port using the no shutdown command.

Ports are enabled by default, thus no need to use the no shutdown command.

Sdp-ping

Isp-ping

Svc-ping

Sdp-mtu

ADSPEC sets an SDP's MTU to the smallest MTU value found along the LSP path.

RSVP must be enabled on all MPLS routers of a path to use ADSPEC.

ADSPEC can automatically adjust the service MTU.

ADSPEC can be enabled on individual LSPs.

An echo request is sent based on the LSP's label stack.

Echo reply packets may not take the same path as the LSP.

The IP destination address is used to initiate echo requests,

The test fails if the LSP is not operationally up.

0

1

2

3

They reduce the number of SDPs that need to be configured.

They can be used to work around physical topologies that prevent a fully meshed deployment.

They prevent loops that can be introduced by mesh deployments.

They can simplify the implementation of security policy enforcement and packet inspection.

A PE uses the same VRF table for all the VPRN services on it.

A PE uses a VRF to maintain forwarding information.

Information for VRFs can be advertised between PEs by MP-BGP.

A PE uses a VRF to route traffic to CEs.

Isp-trace

Idp-trace

Sdp-ping

Svc-ping

Ping