Configuring Traffic Engineering Links And Data Bearers - Alcatel-Lucent 7450 Manual

GMPLS
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 7x50 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>lmp-peer then assigns the control of the TE-links to the LMP protocol to
a given 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 configure>router>lmp>lmp-peer.
The hello interval ranges from 1000 to 65535 milliseconds. The default hello interval is
1000 milliseconds.
The hello dead-interval ranges from 3000 to 65535 milliseconds. The default hello dead
interval is 4000 milliseconds.
The retransmission-interval ranges from 10 to 4294967295 milliseconds in 10 millisecond
intervals, with a default of 500 milliseconds.

Configuring Traffic Engineering Links and Data Bearers

Traffic engineering (TE) links are configured under the config>router>lmp with a specific
command, te-link, to create a specific context to hold TE specific configuration information
pertinent to the local and remote identifiers, and physical resources assigned to the te-link.
Only one data bearer per TE link is supported.
The te-link association is the creation of an association between a TE-link and data-bearing
physical ports. Under the TE-link context, different data bearers can be configured via the
data-bearer command. The data bearer is assigned a complete physical port, using port<x/y/z>
(slot-number/MDA-number/port-number) as input.
Note that a data bearer cannot be associated with a port in a LAG.
A TE-link has a unique link-id, which identifies it in RSVP-TE signaling.
The remote-id is the unnumbered link identifier at far-end of the TE link as advertised by the
LMP peer i.e. the UNI-N.
The TE-link has associated physical resources which are assigned to the TE-link by
configuring the data-bearer under the config>router>te-link context.
The operator must also configure the remote data-bearer link identifier under the data bearer
subcontext.
Note that LMP does not correlate the local and remote Layer 2 interface identifiers (such as
MAC addresses) for the data bearer. It only correlates the local and remote TE Link and Data
7450 ESS MPLS Guide Page 439