Alcatel-Lucent 7450 Manual page 438

Configuring LMP
messages if a peer-loopback address is not subsequently configured. The local GMPLS Router
ID is used as the source address.
In Release 13.0, a static route must have previously been configured to this peer router ID.
Dynamic routing e.g. using OSPF over the IPCC in order to resolve routes to the peer GMPLS
router ID, is not supported. In addition, the local loopback address to use as the local GMPLS
Router ID should also be configured.
The LMP messages are sent over the interface corresponding to the IPCC that has been
configured previously. The LMP session can be associated with one or more TE links that
have been configured previously.
A control channel to an LMP Peer is configured using the config>router>lmp>lmp-peer
peer-cp-node-id>control-channel context. Control channels are indexed using the lmp-cc-id
parameter, which corresponds to the lmpCcId object in the LMP MIB.
The following CLI tree illustrates the key commands for configuring LMP.
config
If peer-loopback-address is entered, then this is used as the routable peer address, otherwise
the peer-cp-node-id is assumed to correspond to a routable peer loopback.
The peer-interface-address is mandatory and is the destination address of the IPCC on the
peer UNI-N used to reach the GMPLS Router ID of the peer. It corresponds to the
Page 438
router
[no] lmp
[no] te-link te-link-id
link-name te-link-name
remote-id id
[no] data-bearer data-bearer-id
port port-id
remote-id id
[no] shutdown
[no] shutdown
gmpls-loopback-address local-gmpls-loopback-address
[no] lmp-peer peer-cp-node-id
peer-loopback-address peer-loopback-address
retransmission-interval interval
retry-limit limit
[no] control-channel lmp-cc-id
peer-interface-address ipcc-destination-addr
hello interval interval dead-interval interval
passive
[no] shutdown
te-link te-link-id
te-link te-link-id
[no] shutdown
lmp-peer lmp-peer-address
...
[no] shutdown
[no] shutdown
7450 ESS MPLS Guide