Example: Configuring Traffic Engineering Link and Interface Identifiers

Figure 1 shows where the IDs come from and where you must assign them. This example highlights the connections between Router A and OXC1, but the same configuration concepts apply to all pairs of peers.

First, you configure a traffic engineering link named TE1 on Router A, which contains the local address 10.1.1.1, remote address 10.1.1.2, data channel interface so-0/0/0, and control channel interfaces so-0/0/2 and so-0/0/3. You also configure a traffic engineering link named TE2 on OXC1, which contains the local address 10.1.1.2, remote address 10.1.1.1, data channel interface so-0/0/1, and control channel interfaces so-0/0/2 and so-0/0/3. When the traffic engineering links are enabled on Router A and OXC1, these two peer devices each generate two local IDs: one for the traffic engineering link itself and one for the logical interface.

If Router A has a local ID of 12345 for its traffic engineering link and a local ID of 23456 for its interface, you must configure 12345 as the traffic engineering link remote-ID and 23456 as the interface remote-ID on the TE2 traffic engineering link of OXC1. Similarly, if OXC1 has local IDs of 98765 for its traffic engineering link and 54321 for its interface, you configure Router A’s TE1 traffic engineering link with 98765 as the traffic engineering link remote-ID and 54321 as the interface remote-ID.

To complete the full data path, you need to enable LMP on each link in the path. This means you must configure remote-ID and local-ID pairs between linked devices.