JMF-Ch3: Label Distribution Protocols Flashcards
What is MPLS?
Multi-Protocol Label Switching
A routing technique in that directs data from one node to the next based on short path labels rather than long network addresses, thus avoiding complex lookups in a routing table and speeding traffic flows
What are the three different Label Distribution Protocols (LDPs)?
- RSVP
- LDP
- Seamless MPLS
Describe LDP
Offloads the forwarding plane of core routers by building a full mesh of label switched paths from any node to any other node.
Describe RSVP
- Originally a bandwidth reservation protocol
- Uses IP as its network layer (protocol number 46)
- Extremely extensible
- Signaling protocol, not a routing protocol
What are the RSVP Message type groups?
- LSP Setup
- LSP Tear-down
- Error Handling
What are the RSVP message types for LSP setup?
- Path: request for an LSP to be created or periodic refresh
- Resv: Reserve resources for LSP
What are the RSVP messages used for LSP Tear-down?
- PathTear: Remove path (and corresponding reservation) state
- ResvTear: Remove reservation state
What are the RSVP Message types for Error handling?
- PathErr: Error message sent upstream to sender
- ResvErr: Error message sent downstream
What are some objects included in an RSVP PATH message?
- Session: Uniquely identifies the LSP
- Session attributes: priority, preemption, link/node protection
- Sender T_Spec: requested bandwidth reservation
- RSVP hop: the previous hop the PATH message traversed
- Label Request: request for label binding
- Record route: lists nodes traversed by the LSP
- Explicit Route Object: used to specify the path the LSP should take
What are the steps for creating an LSP?
- RSVP PATH message is sent downstream toward the egress router
- Read by every router along the path
- The egress LSPR sends a RSVP RESV message to the egress LSR including the allocated label
- All transit labels receive a new local label and installs the entry into the label information base
What objects are included in the RSVP RESV message?
- SESSION: Uniquely identifies the LSP being established
- LABEL: label allocated by the previous hop
- STYLE: specifies the reservation style (Fixed-filter, Shared Explicit, Wildcard)
- RECORD_ROUTE: Records the actual path of the LSPs in terms of Nodes & interfaces traversed
- HOP: Indicates the previous hop’s IP address
What signal condition would trigger the RSVP PathErr message?
When an LSR cannot forward the PATH message such as when MPLS is not enabled on the outgoing interface, or when reserving bandwidth if there is not enough free on the outgoing interface
What signal condition would trigger the RSVP ResvErr message?
- When an RESV message is received, but the LSR cannot complete the reservation.
- Can happen during MPLS label allocation failure
Which LSR receives RSVP PathErr messages?
The ingress LSR (Upstream)
Which LSR receives the RSVP ResvErr Message?
The egress LSR (downstream)
Which LSR creates the RSVP PATH message?
ingress LSR
Which LSR creates the RSVP RESV message?
the egress LSR
What is an Explicit Route Object (ERO)?
- Allows the ingress LSR to control the path through which an LSP is established independent of the IGP best path.
- Used for traffic-engineering
When using an ERO, which router receives the PATH message?
- The first hop listed in the ERO
- e.g. Ingress LSR R1 sends RSVP with destination of R7. This will be routed according to the best IGP path to the destination.
What does ERO loose constraint processing do?
When the first constraint cannot be fulfilled, the loose qualifier creates a PATH state, and forwards the message onto the next constraint to be fulfilled using the best IGP route
What action will occur when a router receives a PATH message with an ERO constraint that it can verify?
The fulfilled ERO constraint is removed, and the PATH message is forwarded with the remaining ERO constraints
When the ERO constraint is set to strict, what will occur when the router cannot verify the constraint?
the LSR will send a PathErr message of ‘Wrong Delivery’ back upstream
What is the purpose of the Record Route object (RRO)?
- Provides end-to-end path visibility
- Each nodes adds to the RRO the address of the interface on which the PATH message was received.
How can RRO help to avoid routing loops?
If a node receives a PATH message with one of its own local addresses already listed within the RRO, the LSR sends back a PathErr message indicating a Routing Loop detected and aborts the LSP setup.
What is the minimum required for RSVP Configuration?
- ‘family mpls’ must be configured at the logical unit level
- all interfaces must be listed under ‘[edit protocols mpls]’ level