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

Configuring the Remote ID for the Traffic Engineering Link

The local ID for the traffic engineering link is automatically assigned by LMP. The port identifier and labels for the interfaces (resources) in the traffic engineering link are also assigned automatically. However, you need to explicitly configure the remote ID for the traffic engineering link and the remote ID traffic engineering link interface. The remote ID for the interface must be based on the post-ID assignment of the peer node. The remote IDs are needed for static mapping of remote labels to local labels.

Before you can obtain the remote IDs for the traffic engineering link and traffic engineering link interface on the peer node, you must first configure the LMP peer, as described in Configuring LMP Peers. Once you have configured the LMP peer, you can obtain the traffic engineering link local ID and interface local ID by issuing the show link-management te-link command. Once you have these IDs, you can configure them as the remote IDs on the peer node.

To configure the remote ID for a traffic engineering link and for the traffic engineering link interface, include the remote-id statement:




te-link te-link-name {



interface interface-name {

remote-id id-number;
}



remote-id id-number;
}

For a list of hierarchy levels at which you can include this statement, see the statement summary section for this statement.

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