Customer configuration scenarios – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 393
![background image](/manuals/361646/393/background.png)
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
369
53-1003031-02
Configurable LDP router ID overview
2
The LDP protocol uses the new IP address specified by feature as LSR-ID only when this IP address
is configured on one of the enabled loopback interfaces. When this IP address is not configured in
enabled state on any of the loopback interface, LDP protocol will continues in the disabled state.
LDP protocol will be enabled as soon as this IP address is configured on one of the enabled
loopback interfaces.
When you decide to disable the feature, the LSR-ID selection procedure falls back to default
behavior of selecting an LSR-ID for LDP protocol when LDP protocol is enabled, which is same as
the behavior of NetIron Release 05.400 products.
Customer configuration scenarios
NetIron Release 05.500 behavior of the feature is illustrated in different scenarios. When “feature”
is mentioned, it means “configurable LDP LSR-ID” feature and its configuration.
4.
a) Precondition: LDP protocol has default configuration.
b) Action: Feature is enabled with an IP address.
c) Post condition: When the LDP protocol is already using the same IP address specified by
the feature as LSR-ID for LDP protocol, LDP continues to work without restarting LDP
protocol. This is because LDP protocol is already using the LSR-ID user intend to configure
for LDP protocol.
When LDP protocol is using another value as LSR-ID, LDP protocol restarts. During restart,
the LSR-ID selected for LDP protocol is the same IP address as set by the feature. In cases
where the feature configured value is not present on any of the enabled loopback
interfaces, LDP protocol continues in the disabled state.
5.
a) Precondition: LDP protocol is disabled & feature is configured.
b) Action: Feature configured IP address is configured on one of enabled loopback interface,
such as when user configures IP address to be used as LSR-ID as on one of the loopback
interface.
c) Post condition: LDP protocol is enabled with LSR-ID as configured for the feature.
6.
a) Precondition: LDP protocol is enabled and feature is configured.
b) Action: IP address same as LSR-ID is deleted from loopback interface OR loopback
interface containing IP address configured by feature is disabled, or deleted.
c) Post condition: LDP protocol is disabled and continues to remain in that state until the
feature configured IP address is reconfigured on one of the enabled loopback interfaces.
7.
a) Precondition: LDP protocol is enabled and the feature is configured.
b) Action: The feature configuration is changed to another address.
8.
a) Precondition: LDP protocol is enabled and the feature is configured.
b) Action: The feature is disabled.
c) Post condition: The LDP protocol will continue to function without restart but features
functionality will be disabled. Please make a note that LSR-ID selection process will fall
back to default behavior when attempt is made to restart LDP protocol. Since no attempt is
made to restart LDP protocol, the LSR-ID for LDP protocol will continue to remain UP at the
time of disabling the feature. The reason for this behavior is to minimize the number of
restart for LDP protocol.