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

TE enabled OSPF routers

Backbone router only

ABR only

ASBR only

A PUSH label stack operation must be performed.

The outgoing interface and next-hop address will be determined from the FIB.

The packet can be forwarded as a labeled or unlabeled packet.

A POP label stack operation may be performed.

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.

Router address

Traffic engineering metric

Maximum bandwidth

Link

Admin Group

A router will never receive a packet containing this label value.

Request a new label from the peer that provided this label.

Pop the label.

PUSH an additional label onto the label stack.

Signal a new label to the peer that sent the packet.

Independent control mode.

Ordered control mode.

Liberal label retention.

Conservative label retention.

Downstream on demand

Label bindings are distributed to other routers when explicitly requested.

Label bindings are distributed to all neighbors including non-downstream routers.

Label bindings are distributed if labels have not been received from downstream routers.

All labels received from downstream neighbors are stored in the LIB.

The egress RSVP interface has 80 percent bandwidth unreserved.

LSPs can reserve an additional 9.9 Gbps bandwidth on this RSVP interface.

The head end reserves 100Mbps for the LSP.

The egress RSVP interface has 1Gbps bandwidth unreserved.

Type 9 LSA ?Link local LSA

Type 10 LSA ?Area local LSA

Type 8 LSA ?TE router LSA

Type 11 LSA ?Network LSA

The Hello protocol can speed up convergence without reducing refresh time.

Hello messages are sent after at least one RSVP session is active on the interface.

An interface with multiple RSVP sessions sends Hello messages for each session.

An RSVP neighbor is declared down if Hello messages are not received within the Hello timeout.

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.

The router does not have a route to reach to the peer 10.10.10.2/32.

The router does not have a route to reach to the prefix 192.10.1.2/32.

The router does not have an export policy defined to export the prefix 192.10.1.2/32 into LDP.

The router receives an invalid label for the prefix 192.10.1.2/32 from its peer.

Send a PATH Tear message toward router R6.

Send a PATH Tear message toward router R1.

Send a PATH Error message toward router R6.

Send a PATH Error message toward router R1.

Selected labels from the FIB are populated to the LFIB.

Selected labels from the RIB are populated to the FIB.

Selected labels from the LIB are populated to the FIB.

Selected labels from the LIB are populated to the LFIB.

All routers along the path, R1, R2, and R3 can be PLRs.

If the R1-R2 link fails, router R4 becomes an MP.

If the R2-R3 link fails, router R3 becomes a PLR.

Router R1 is the LSP head-end and can be a PLR.

Enable the Idp-over-rsvp feature on all PEs and ABRs along the LSP tunnel.

Configure Link-LDP sessions between each PE-ABR and ABR-ABR pair.

Configure RSVP-TE LSPs in each area between each PE-ABR and ABR-ABR pair.

Configure T-LDP sessions with the tunneling option.

Router R1

Router R2

Router R3

Router R4

Router R5

Incoming label

Outgoing label

Incoming interface

Outgoing interface

R3 and R5 become DMPs; R6 becomes MP.

R3 and R5 become DMPs; R4 becomes MP.

R3, R5, and R6 become DMPs; R4 becomes MP.

R1, R3, and R5 becomes DMPs; R4 and R6 become MPs.

T-LDP is used to provide an end-to-end session between two PE routers.

T-LDP is used to signal service labels for Layer 2 services.

T-LDP is used to establish transport tunnels for Layer 2 services.

T-LDP is used in LDP over RSVP solution.

CAC is used when the LSP path has not been computed by CSPF.

CAC is used when the LSP path has been computed by CSPF.

CAC is used to perform a bandwidth check on each egress interface of the downstream router.

CAC is used to perform a bandwidth check based on the router's LSDB.

An LSR may answer requests for label mappings immediately, without waiting for a label mapping from the next-hop.

An LSR may advertise label mappings to all peers for which it might be a next-hop for a given FEC.

An LSR propagates a label mapping downstream for a FEC, only if it has a label mapping for the FEC next-hop.

An LSR will only distribute a label for a FEC when it has been requested to do so.

0x4

0x5

0x10

0xa

It uses a UDP connection with an arbitrary port number.

It uses a UDP connection with well-known port number 646.

It uses a TCP connection with an arbitrary port number.

It uses a TCP connection with well-known port number 646.

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.

RSVP-TE supports Connection Admission Control (CAC).

RSVP-TE enables simplified configuration of LSPs.

RSVP-TE supports path calculations that do not use IGP cost.

RSVP-TE provides support for traffic protection features.

Push an additional label onto the label stack.

Pop the label.

Swap the label.

Pop the label and push an additional label onto the label stack.

Liberal label retention mode

Conservative label retention mode

Ordered control mode

Independent control mode

RSVP generates a summary refresh message for each LSP.

Message-IDs replace individual refresh messages.

An LSP state change causes the Message-ID to be incremented.

RSVP refresh reduction is disabled by default.

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"

Router R1

Router R2

Router R3

Router R4

Router R5

CSPF must be enabled at head-end on fast reroute protected loose path LSPs

Fast reroute must first be enabled on the downstream routers.

CSPF must be enabled on all downstream loose hop routers.

Global revertive path optimization must be enabled so the path will be re-optimized around a failed node.

Each implementation can use them as they see fit.

They are used to carry the Ethertype value.

They are used to carry the TTL value.

They are used to carry QoS classification.

They are used to carry fragmentation flag information