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

Configuring Link Management Protocol Peers

After you set up TE links, configure LMP network peers with the peer statement at the [edit protocols link-management] hierarchy level. A peer is the network device that your router communicates with when setting up the control and data channels. Often, the peer is an OXC. Designate a peer name, configure the peer’s router ID as the address (often a loopback address), specify the interface that will be used as a control channel, and apply the TE link to be associated with this peer.

You can configure one or more control channels for a peer. The control channels must have point-to-point connectivity with the peer (for example, you can use a point-to-point link or a tunnel). You can also configure the generic routing encapsulation (GRE) tunnel interface of the Routing Engine as a control channel. To configure a static control channel, include the control-channel statement at the [edit protocols link-management peer peer-name] hierarchy level. To configure a control channel that uses control channel management and link property correlation, see Option: Configuring an LMP Control Channel. Without a control channel, the configuration will fail to commit.



[edit]
protocols {


link-management {


peer peer-name { # Configure the name
of your network peer.
address ip-address; # Include the
router ID of the peer.
control-channel interface; # Specify the interface for the control channel.
te-link te-link-name; # Assign a TE
link to this peer.
}


}


}

Note: Although you can configure the gre- tunnel interface on a Routing Engine as a control channel, this interface is not supported, nor is it configurable for other applications.

Note: You can configure either the control-channel statement or the lmp-control-channel statement at the [edit protocols link-management peer peer-name] hierarchy level, but not both statements simultaneously.

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