[an error occurred while processing this directive][an error occurred while processing this directive]

Displaying 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 the mapping, 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 traffic engineering 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 traffic engineering 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 traffic engineering 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.}}}}

Published: 2010-04-15

[an error occurred while processing this directive]