LMP is used to establish and maintain an IPCC between adjacent peers, as well as to correlate the local and remote identifiers for the TE links that it controls. Some attributes must be configured locally on a per-peer basis, such as the LMP peer information, TE link information, and per-peer protocol related parameters.
The config>router>lmp>peer peer-cp-node-id command creates a context per LMP peer. The peer-cp-node-id parameter specifies the control plane identifier of the adjacent UNI-N. It is an IPv4 or unsigned integer-formatted address that is used by the UNI-C for LMP and RSVP-TE messages if a peer-loopback address is not subsequently configured. The local GMPLS router ID is used as the source address.
A static route must have previously been configured to this peer router ID. Dynamic routing (for example, using OSPF over the IPCC to resolve routes to the peer GMPLS router ID) is not supported. 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 command. 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
— 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] 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
— [no] shutdown
— peer lmp-peer-address
— ...
— [no] shutdown
— [no] shutdown
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 lmpCcRemoteIpAddr in RFC 4631. If the peer-interface-address is used as the destination IP address in the IP packet on the IPCC, then the router local interface address is used as the source IP address.
A te-link is configured under config>router>lmp>te-link. The te-link parameter under config>router>lmp>peer then assigns the control of the TE-links to the LMP protocol to a specific peer. Each TE-Link can only be assigned to a single LMP peer.
The LMP protocol-specific attributes such as timers and retransmission retries are configured for each LMP peer under config>router>lmp>peer.
The hello interval ranges from 1000 to 65 535 ms. The default hello interval is 1000 ms.
The hello dead-interval ranges from 3000 to 65 535 ms. The default hello dead interval is 4000 ms.
The retransmission-interval ranges from 10 to 4 294 967 295 ms in 10-ms intervals, with a default of 500 ms.
The ttl command allows the user to configure the TTL of the IP control channel for RSVP and LMP packets to a value other than 1 (default). The range of values is 2 - 255. This enables multi-hop data communication networks between the UNI-C and UNI-N.
To configure an IPCC to a specific LMP peer to use an OES Ethernet port on the CPM, then the configuration must refer to a GMPLS loopback IP address that exists within a virtual management router that has an interface on that CPM Ethernet port. The IPCC to a specific LMP peer is created within a named management virtual router as follows:
config>router>lmp
— peer peer-node-id
— control-channel-router router-name
— gmpls-loopback-address ipv4-address
The default router instance is ‟Base”.
The router-name parameter specifies the 64-byte name of a virtual router instance.