4A0-103 Nokia Multi Protocol Label Switching Questions and Answers

Node protection tunnels detour around a failed next downstream router.

Node protection tunnels can only be requested for a primary LSP path.

Node protection tunnels are only used by one-to-one Fast Reroute.

Link protection tunnels are established if a router is unable to establish node protection tunnels.

If Shared Explicit reservation style is used, 400Mbps is reserved.

If Shared Explicit reservation style is used, 700Mbps is reserved.

If Fixed Filter reservation style is used, 400Mbps is reserved.

If Fixed Filter reservation style is used, 300Mbps is reserved.

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.

MPLS data traffic will be discarded until the IGP finds a new next-hop to router R3.

MPLS data traffic will be discarded unless the LDP tunnel has a standby secondary path.

MPLS data traffic will not be discarded because router R1 received labels from both next-hops, routers R2 and R3.

MPLS data traffic will not be discarded because of fast reroute capability on router R2.

It allows link LDP to be configured on the edge devices only.

It is used to signal the transport labels in the provider core.

It allows selective control over which devices are configured for LDP.

It is used to signal the service labels in the provider core.

MPLS Echo Request packets are sent within the RSVP-TE tunnel that is signaled for "lsp-toR2".

MPLS Echo Request packets are sent within the LDP tunnel that is signaled for Mlsp-toR2".

MPLS Echo Request packets are IP-routed to the destination address of "lsp-toR2".

MPLS Echo Request packets are sent to the destination address of "lsp-toR2" over TCP.

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.

Enable traffic engineering on all routers along the LSP path.

Enable CSPF on the head-end router.

Configure a path definition on all routers along the LSP path.

Enable MPLS and RSVP on all routers along the LSP path.

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.

The DMP sends the DMP_Object in each detour's PATH messages.

The DMP summarizes PATH messages, giving each detour its own MSGJD.

The DMP identifies itself as the previous hop in each detour's PATH message.

The DMP sends a single PATH message containing the merged DETOUR_Objects.

Assign an admin group to a MPLS interface.

Configure CSPF on the LSP.

Configure at least one strict hop on the LSP path.

Configure an "include" or "exclude" statement on the LSP path.

The penultimate router will forward packets to the eLER, based on the IP header.

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

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

The penultimate router will pop the top label from the packets.

Independent control mode.

Ordered control mode.

Liberal label retention.

Conservative label retention.

Downstream on demand

Label values may be dynamically assigned by LDP.

Label values may be dynamically assigned by RSVP-TE.

Label values may be reserved for special uses.

Label values may be dynamically assigned by IGP.

Label

Frame check sequence

Traffic Class (previously called Experimental)

Time To live

Bottom of stack bit

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.

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.

Liberal label retention mode

T-LDP enabled with peers to which load balancing is desired.

ECMP enabled in the config>router context.

Hashing used to select the egress label.

Export policy applied to advertise multiple labels for a given FEC.

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.

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.

A POP label stack operation may 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 PUSH label stack operation may be performed.

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

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

The outer label TTL will be 251 and the inner label TTL will be 251.

The outer label TTL will be 251 and the inner label TTL will be 252.

Static LSPs

Reserved use

Vendor proprietary use

Management LSPs

Dynamic LSPs

RIB

FIB

LIB

LFIB

Conservative label retention

Liberal label retention.

Downstream on demand.

Downstream unsolicited.

3000ms

9000ms

30000ms

120000ms

show router ldp default

show router ldp parameters

show router ldp settings

show router mpls settings

show router mpls label-options

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.

CSPF looks for the delta bandwidth, taking down the first path if necessary.

CSPF looks for the delta bandwidth, implementing make-before-break.

After 5 failed attempts to find the bandwidth requested, the head end disables the LSP.

CSPF looks for the entire bandwidth requested, implementing MBB.

Router R1 is the LSP originator and is also a PLR.

With one-to-one link or node protection, the detour LSP path is R1-R4-R5-R2-R3.

With one-to-one link or node protection, the detour LSP path is R1-R4-R5-R3.

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

None of the nodes can be protected with FRR.

Label allocation and management.

Label swapping.

Pushing a label on an unlabeled packet.

Label signaling.

Routing lookups.

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

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 adjacency forms with the lower timeout value

The "show router Idp session" command output displays the adjacency in state "init"

The adjacency forms with the higher timeout value

The adjacency times out after 30 seconds