mpls rsvp-te resv-rro transit

Function

The mpls rsvp-te resv-rro transit command specifies the contents of a Record Route Object (RRO) carried in a Resv message on transit node.

The undo mpls rsvp-te resv-rro transit command restores the default RRO contents.

By default, the RRO carried in a Resv message sent by a transit LSP contains the address of the inbound interface and the label allocated to the upstream LSR, LSR ID and the label allocated to the upstream LSR, and address of the outbound interface.

By default, transit LSP RROs carry labels in the following order: Incoming with Label, RouterID with Label, Outgoing. That is, the LSP inbound interface carries labels + RouterID carries labels + LSP outbound interfaces.

Format

mpls rsvp-te resv-rro transit { { incoming | incoming-with-label } | { routerid | routerid-with-label } | { outgoing | outgoing-with-label } } ^*

undo mpls rsvp-te resv-rro transit

Parameters

Parameter	Description	Value
incoming	Incoming interface.	-
incoming-with-label	Incoming interface with label.	-
routerid	Router ID.	-
routerid-with-label	Router ID with label.	-
outgoing	Outgoing interface.	-
outgoing-with-label	Outgoing interface with label.	-

Views

MPLS view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
mpls-te	write

Usage Guidelines

Usage Scenario

When RSVP-TE is used to establish an MPLS TE tunnel, devices of different vendors cannot communicate because the sequence numbers of subobjects in RRO fields of Resv messages sent by these devices are inconsistent. The mpls rsvp-te resv-rro command can be used to adjust the sequence numbers of sub-objects in the RRO fields of Resv messages so that devices of different vendors can communicate.

This command adjusts the RRO subobjects in the following ways:

Sequence of subobjects in RRO
Whether each subobject carries a corresponding tag.
When an upstream non-Huawei device is connected a Huawei device, for example: X1---X2---H1---H2.
You are advised to check LSP information on X1 and observe the Resv RRO sequence of X2. For example, the Resv RRO on X2 carries only the inbound interface address and LSR ID. In this case, you are advised to adjust the Resv RRO sequence on H1 to be the same as that on X2.
On H1, run the mpls rsvp-te resv-rro transit incoming-with-label routerid command or the mpls rsvp-te resv-rro transit incoming-with-label routerid-with-label command.
If the default configuration is used or the mpls rsvp-te resv-rro transit command with the outbound interface address specified, node protection or FRR binding may fail.

Prerequisites

Enable MPLS RSVP-TE.

Configuration Impact

After the configuration, the content and sequence of the RRO in the Resv message are affected.

Precautions

The mpls rsvp-te resv-rro transit command takes effect only for new LSPs, not existing LSPs.

Example

# Set the RRO carried by the transit LSP to the LSR ID, label allocated to the upstream node, inbound interface address, outbound interface address, and label allocated to the downstream node.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls te
[*HUAWEI-mpls] mpls rsvp-te
[*HUAWEI-mpls] mpls rsvp-te resv-rro transit routerid-with-label incoming outgoing-with-label