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

Discovering Local Identifiers and Configuring Remote Identifiers

Once LMP is enabled on a router, the router automatically assigns two local IDs: one at the te-link level, the other at the interface level. You must configure these port-to-label mappings manually for LMP on both the router and its peer. To configure, set the local IDs of one device (such as the router) as remote IDs on the peer device (such as an OXC) with the remote-id statement at the [edit protocols link-management te-link te-link-name] and [edit protocols link-management te-link te-link-name interface interface-name] hierarchy levels.

You can view the TE link and interface local IDs by using the show link-management te-link command. Once you have learned these IDs, configure them as remote-id statements at the corresponding te-link and interface levels on the peer.

Because peers vary, check with your OXC vendor for the configuration statements and location of the local ID information for your specific optical peer device. If you do not manage the peer device, ask the peer’s administrator to enable LMP and generate the IDs for you. GMPLS will not work unless these local IDs from both the router and the peer are configured as remote IDs on the opposite device.

To disable an entire TE link for administrative purposes, include the disable statement at the [edit protocols link-management te-link te-link-name] hierarchy level. To disable an interface within a TE link, include the disable statement at the [edit protocols link-management te-link te-link-name interface interface-name] hierarchy level.



[edit]
protocols {


link-management {


te-link te-link-name {
disable; # Disable the entire TE link.
remote-id id-number; # TE link ID
number of the peer device.


interface interface-name { # Name
of the interface used for data transfer.
disable; # Disable an interface in the TE link.
remote-id id-number; # ID number of
the remote device.
}


}


}


}

Figure 20: TE Link and Interface ID Example

Image g017149.gif

Figure 20 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 TE 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 TE 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 TE links are enabled on Router A and OXC1, these two peer devices each generate two local IDs: one for the TE link itself and one for the logical interface.

If Router A has a local ID of 12345 for its TE link and a local ID of 23456 for its interface, you must configure 12345 as the TE link remote-ID and 23456 as the interface remote-ID on the TE2 TE link of OXC1. Similarly, if OXC1 has local IDs of 98765 for its TE link and 54321 for its interface, you configure Router A’s TE1 TE link with 98765 as the TE 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.

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