When the interface to the peer router is down.

When router R1 has no route to the peer address 10.10.10.2.

When the adjacency between the two routers fails.

When the targeted session is not yet configured.

Enable LDP on the R2-R5 interface.

Configure T-LDP sessions between routers R2 and R5 and R3.

Configure LDP-over-RSVP support on router R2.

Enable MPLS and RSVP on the router R2 network interfaces.

Enable LDP on the R2-R5 and R2-R3 interfaces.

Per-platform label space, conservative retention mode

Per-interface label space, conservative retention mode

Per-platform label space, liberal retention mode

Per-interface label space, liberal retention mode

Label request message

Notification message

Address message

Keepalive message

Initialization message

Hello message

Notification

Session

Discovery

Advertisement

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.

IP routing protocols do not always select the best route to a destination.

IP routing protocols always select multiple routes to a destination.

IP routing protocols do not make use of all available network attributes to select a path

Improper network design results in limited network path redundancy.

Independent control mode.

Ordered control mode.

Liberal label retention.

Conservative label retention.

Downstream on demand

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.

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 penultimate router will POP the top label from the packets.

The eLER will receive packets with a top label value of 3.

The eLER will receive packets with a top label value of 0.

The penultimate router will always receive unlabeled packets.

The penultimate router performs a double lookup on the packet.

Both the primary and secondary paths are explicitly defined.

The primary path is active and the secondary path is in hot standby.

The LSP defined will use the primary path and will signal the secondary path to become active if the primary path fails.

The LSP has the same source and destination for both primary and secondary paths.

A mechanism that implements opaque LSAs.

A mechanism that computes routes based on defined user requirements.

A mechanism that allows the IGP shortest path to be used.

A mechanism that allows RSVP or LDP signaling to use a route other than the IGP best route to establish a LSP.

It is unidirectional.

It is bidirectional.

It must always have a secondary path.

It provides a specific tunnel for a FEC through the network.

It always follows the IGP best path.

It is always a random 16-bit number.

It is always zero for per-interface label space.

It is always non-zero.

It is always zero for per-platform label space.

It is always non-zero for per-platform label space.

Conservative label retention

Liberal label retention

Downstream on demand

Downstream unsolicited

Each PLR signals a protection tunnel that avoids the downstream node.

A single protection tunnel can protect all LSPs that go through the same hop.

A link protection tunnel is signaled if a node protection tunnel cannot be established.

Protection tunnels used in this LSP are also detour tunnels.

It provides the ability to establish connection oriented paths over a connectionless IP network.

It provides a mechanism to engineer network traffic patterns independently of IP routing tables.

It will work over most physical layer protocols.

It can use GRE tunnels to transport data from many different protocols over an IP network.

Each PLR signals a bypass tunnel that avoids the next-hop downstream router.

When a failure occurs, the PLR pushs an additional label onto the label stack.

No bypass tunnel is established if the PLR cannot provide node protection.

The head-end router sets the local protection desired flag in the session attribute object.

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.

125 Mbps

500 Mbps

625 Mbps

2000 Mbps

iLER

LER

LSR

PE

eLER

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

RSVP-TE operates in a downstream unsolicited label advertisement mode.

RSVP-TE makes use of ordered control mode.

RSVP-TE is an MPLS signaling protocol, based on the resource reservation protocol.

RSVP-TE enables the establishment of explicitly routed LSPs that can be automatically routed away from network failures

RSVP-TE supports explicitly routed LSPs using either loose or strict route definitions.

Each PLR signals a detour LSP that avoids the downstream node. If the downstream node cannot be avoided, a detour LSP that avoids the downstream link is signaled.

The detour LSP can take one or more hops before merging back on the protected LSP.

The merge point of the protected LSP must be the next-next-hop node

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 detour LSPs.

The label recording desired flag must be set in the session attribute object in order for the PLR to know what label to swap when using the detour LSP.

The path must include at least one hop.

The path may be used multiple times in a single LSP.

The path may comprise loose hop entries only.

The path must define the LSP's tail end.

The path may be used for multiple LSPs.

An LSP is a bidirectional path across the MPLS domain.

An LSP is a bidirectional path for a particular FEC across the MPLS domain.

An LSP is a unidirectional path across the MPLS domain.

An LSP is a bidirectional path between adjacent LSRs.

An LSP is a unidirectional path between adjacent LSRs.

The LSP will switch to R1-R3-R5-R6 after the resignal timer expires.

The old primary path and its detours are torn down after the new primary path is established.

CSPF must be enabled to find a more optimal path.

The traffic is switched to R1-R3-R5-R6 in an MBB fashion.

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.

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.

It makes use of MPLS resiliency features available within an AS.

It eliminates double route lookups on all routers within an AS.

It eliminates the need to run IGP on all routers within an AS.

It eliminates the need for an iBGP full mesh on all core routers.

LSP-3 takes R1-R3-R5-R6 and LSP-4 takes R1-R2-R4-R6.

LSP-3 takes R1-R2-R4-R6 and LSP-4 takes R1-R3-R5-R6.

LSP-3 takes R1-R3-R5-R6 and LSP-4 has no available path.

LSP-3 takes R1-R2-R4-R6 and LSP-4 has no available path.

Independent control mode, downstream on demand

Independent control mode, downstream unsolicited

Ordered control mode, downstream on demand

Ordered control mode, downstream unsolicited

To reduce the number of LDP sessions

To reduce the number of LIB and LFIB entries

To bypass the LDP exact prefix match rule

To export summarized routes from OSPF to LDP