Procedures for LSR overload protection
Page 588 7450 ESS MPLS Guide
FEC TLV containing the Typed Wildcard FEC Element for the specified FEC type. The
Message may be sent to one or more peers.
3. After it has notified overload status ON for a FEC type, the overloaded upstream LSR
MAY send Label Release for a set of FEC elements to respective downstream LSRs to off
load its LIB below certain watermark.
4. When an upstream LSR that was overloaded for a FEC type before, detects that it is no
longer overloaded then it MUST send a LDP Notification Message with S bit OFF in LSR
Overload Status TLV and FEC TLV containing the Typed Wildcard FEC Element for the
specified FEC type.
5. When an upstream LSR has notified as overloaded for a FEC type, then a downstream
LSR MUST NOT send new Label Mappings for the specified FEC type to the upstream
LSR.
6. When a downstream LSR receives LSR Overload Notification from a peering LSR with
status OFF for a FEC type then the receiving LSR MUST send any label mappings for the
FEC type which were pending to the upstream LSR or which are eligible to be sent now.
7. When an upstream LSR is overloaded for a FEC type and it receives Label Mapping for
that FEC type from a downstream LSR then it MAY send Label Release to the
downstream for the received Label Mapping with LDP Status Code as
No_Label_Resources as defined in RFC 5036.
To Next Page
Loading...
