[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring the LMP Control Channel Interface for the Peer

In an environment that uses LMP to establish and maintain an LMP control channel between peers, you can configure a number of attributes associated with LMP. To configure the interface to be associated with the LMP control channel for the peer, include the lmp-control-channel statement:




lmp-control-channel control-channel-interface;

You can configure this statement at the following hierarchy levels:

[edit protocols link-management peer peer-name]
[edit logical-systems logical-system-name protocols link-management peer peer-name]

You can configure a generic routing encapsulation (GRE) interface for the LMP control channel. This type of interface does not require a Tunnel PIC.

Note: You can configure GRE interfaces only for GMPLS control channels. GRE interfaces are not supported or configurable for other applications. For more information, see the JUNOS Network Interfaces Configuration Guide.

When this LMP control channel interface comes up, the peers use LMP to negotiate channel parameters and configure the control channel.

The local peer repeatedly sends a Config message to the remote peer. The Config message contains the local control channel ID, the local peer’s node ID, a message ID, and a CONFIG object that includes hello message attributes (the hello interval and the hello dead interval).

The channel is activated when the remote peer responds with a ConfigAck message. The remote peer does so only when its own configured hello interval and hello dead interval match the values in the received Config message or the default values. If these values do not match, the remote peer responds with a ConfigNack message. The local peer logs this event and resends the Config message until the message retry limit is reached. When the message retry limit is reached, the local peer logs that event and restarts the configuration process.

[Contents] [Prev] [Next] [Index] [Report an Error]