4A0-103 Alcatel-Lucent Multi Protocol Label Switching Questions and Answers

The inner label is the IPv4 Explicit Null. The outer label is the MPLS transport label,

The inner label is an MPLS transport label. The outer label is the IPv4 Explicit Null.

The inner label is the IPv6 Explicit Null. The outer label is an MPLS transport label.

The inner label is an MPLS transport label. The outer label is the IPv6 Explicit Null.

The LSP will switchover to another path if a failure occurs.

The LSP will switchover to a better path as soon as it is available.

CSPF must be enabled for this LSP to attempt to find a better path.

The LSP will switchover to a better path in a MBB fashion.

They are multicast to the All Hosts address.

They are broadcast to the subnet broadcast address.

They are multicast to the All Routers address.

They are broadcast or multicast, depending on the physical media.

Enable fast-reroute on all routers along the path. R1, R2, R4, and R6.

Enable both link-protection and node-protection on router R1.

Enable fast-reroute with either one-to-one or facility mode on this LSP.

Enable link-protection only on router R4.

The TC field is set based on the value of the DSCP field inside the customer packet.

The TC field is set to a specific value via explicit administrative configuration.

The TC field is set to a system generated random number.

The TC field is set by the eLER.

Fast reroute requires you to manually define detour paths.

Fast reroute provides path protection close to the failure point

Fast reroute performs automatic path calculation and signaling.

Fast reroute protects both primary and secondary paths.

It identifies the FEC.

It specifies the packet's header length

It identifies the origin of the packet.

It specifies the type of data contained in the packet

Message-IDs replace individual refresh messages.

Refresh reduction applies only to reservation messages.

RSVP generates a summary-refresh message for each LSP.

An LSP state change causes an incremented Message-ID.

Send a PathTear message towards router R6.

Send a PathTear message towards router R1.

Send a ResvTear message toward router R6.

Send a ResvTear message toward router R1.

The time router R2 takes to receive a PATH Error message from router R4.

The time router R2 takes to find out a number of RSVP Hello messages have been missed.

The time router R2 takes to send a PATH Tear message to the head-end router.

The time router R2 takes to receive a PATH message from router R4 after a PATH refresh interval.

The customer's Layer 2 header is preserved at the iLER for Layer 2 services.

The customer's Layer 2 Header is preserved at the iLER for Layer 3 services.

The service provider's Layer 2 header is added at the iLER for Layer 2 services.

The service provider's Layer 2 header is added at the iLER for Layer 3 services.

A separate label is used for each interface that the FEC is advertised on.

It uses fewer label resources than a per-interface label space.

It is typically used when the device has ATM or Frame Relay interfaces.

It uses more label resources than a per-interface label space.

A single label may be assigned to an FEC and used across all interfaces of the same router.

It is only valid when the LDP peers are directly connected over an interface, and the label is only going to be used for traffic sent over that interface.

The router must build the Path State Block (PSB).

The router must build the Reservation State Block (RSB).

The router must build the Session State Block (SSB)

The router must send the second RESV refresh message.

The router must receive the second PATH refresh message.

Each PLR will signal a bypass tunnel that avoids the next-hop node or link.

When a failure occurs, the PLR will push an additional label onto the label stack and start forwarding traffic onto its bypass tunnel.

The ingress router will include a RRO object in the path message to indicate the routers that should be PLRs and MPs along the protected path.

The ingress router will set the local protection desired flag in the session attribute object of the path message to inform all routers along the protected LSP path to establish bypass tunnels.

When the bypass tunnel is in use, the MP will include the RRO object in its PathErr message, with the local protection in use flag set to notify the ingress router that it is using the bypass tunnel.

Send a PathTear message towards router R6.

Send a PathTear message towards router R1.

Send a ResvTear message toward router R6.

Send a ResvTear message toward router R1.

Link-based and T-LDP sessions may be configured on the same LSR.

T-LDP supports sessions between non-directly connected devices.

T-LDP can be configured between directly connected devices.

T-LDP Hello messages are sent to a multicast address.

Static LSPs

Reserved use

Vendor proprietary use

Management LSPs

Dynamic LSPs

A packet arriving with label 131066 will be forwarded out interface 1 /1 /4 with label 131070.

The router is an egress router for FEC 10.10.10.221/32.

There are multiple LSPs to reach FEC 10.10.10.244/32.

The router's system address is 10.10.10.242/32.

Disable route summarization on router R3.

Enable LDP aggregate prefix match.

Create an import policy to accept 10.10.10.2/32 and 10.10.10.4/32.

Disable LDP exact match on 10.10.10.2/32 and 10.10.10.4/32.

The adjacency forms with the lower timeout value.

The adjacency forms with the higher timeout value.

The adjacency is in init state.

The adjacency times out after 30 seconds.

Independent control mode

Ordered control mode

Liberal label retention

Conservative label retention

Downstream on demand.

show router mpls Isp "LSP 1" originate

show router mpls Isp "LSP 1" path detail

show router rsvp session originate

show router rsvp session "LSP 1"

The packet will be label switched; the outer label TTL will be 249 and the inner label TTL will be 250.

The packet will be label switched; the outer label TTL will be 249 and the inner label TTL will be 251.

The packet will be label switched; both the outer label TTL and the inner label TTL will be 250.

The packet will be label switched; both the outer label TTL and the inner label TTL will be 249, because they must be the same.

RIPv2-TE

CSPF

OSPF-TE

ISIS-TE

RSVP-TE

R1, R2, and R4 can be PLRs; R6 is the MP.

R1, R2, and R4 can be PLRs; R2, R4, and R6 are MPs.

R1, R2, R3, R4, and R5 can be PLRs; R6 is the MP.

R1, R2, R3. R4, and R5 can be PLRs; R2, R4, and R6 is the MP.

A mechanism that implements opaque LSAs.

A mechanism that computes routes based on specified requirements.

A mechanism that ensures the IGP best route is used.

A mechanism that enables LDP signaling to use a route other than the IGP best route.

When the reserved bandwidth goes above 80M.

When the reserved bandwidth goes above 40M.

When an additional 80M bandwidth is reserved.

When an additional 40M bandwidth is reserved.

Label space mode

Label retention

Control mode

Keepalive factor

Fast reroute is used when redundant links are not available.

Fast reroute provides path protection close to the failure point.

Fast reroute provides fast failure detection to the head-end router.

Fast reroute protects both primary and secondary paths.

Router R1 will switch traffic to the secondary path immediately.

Router R1 will discard traffic until a new IGP route to router R6 is re-calculated.

Router R1 will discard traffic because the secondary path isnot a fully strict path.

Router R1 will signal the secondary path and switch traffic to it.

1

2

3

4

LDP is not configured on R2.

R2 does not have a route to 10.10.10.3.

LDP is not configured on R3's interface to R2.

The targeted session is not configured on R2.

Router R3 swaps both the RSVP-TE LSP label and LDP transport label received with new labels.

Router R3 swaps the VPN service label received with a new label.

Router R3 uses the same RSVP-TE LSP label as the one received from router R2.

Router R3 uses the same LDP transport label as the one received from router R2.

The PLR issues an RSVP PATH message to the tail-end requesting the address of the MP.

The PLR learns the address of the MP from the ERO.

The PLR learns the address of the MP from the RRO.

The PLR learns the address of the MP from the targeted RSVP Hello message.

The PLR knows the address of the MP is the same as the tail-end router.