No relevant resource is found in the selected language.
Your browser version is too early. Some functions of the website may be unavailable. To obtain better user experience, upgrade the browser to the latest version.
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring the RSVP Message Format
Configuring the RSVP Message Format
Context
You can adjust object information in RSVP messages by configuring the RSVP message format. In scenarios where an RSVP-TE tunnel is deployed, when devices from other vendors on the RSVP-TE tunnel use different format of RSVP message, you can modify the format of RSVP messages to be sent by the Huawei device to implement interworking.
You can configure the transit and egress nodes to add the down-reason object in an RSVP message to be sent to the ingress, facilitating fault locating.
Procedure
Configure the Session-Attribute object in a Path message not to carry affinity information.
When an upstream Huawei device on which an affinity is configured for a TE tunnel communicates with a vendor device not supporting an affinity, you need to run the following commands to configure the Session-Attribute object in a Path message not to carry affinity information.
Perform the following steps on the ingress node of an MPLS TE tunnel:
Run system-view
The system view is displayed.
Run mpls
The MPLS view is displayed.
Run mpls rsvp-te send-message session-attribute without-affinity
The device is configured not to carry affinity information in the Session-Attribute object in a Path message.
By default, the Session-Attribute object in a Path message carries affinity information.
Run commit
The configuration is committed.
Configure the format of the Record Route Object (RRO) in a Resv message.
When the format in an Resv message sent by a non-Huawei device connected to the Huawei device is different from that on the Huawei device, run the following command to adjust the format of Resv messages on the Huawei device to be the same as that on the non-Huawei device to implement interworking.
Perform the following configurations on the transit and egress nodes of an MPLS TE tunnel.
Run system-view
The system view is displayed.
Run mpls
The MPLS view is displayed.
Run the following commands as required.
On a transit node, run the mpls rsvp-te resv-rrotransit { { incoming | incoming-with-label } | { routerid | routerid-with-label } | { outgoing | outgoing-with-label } } * command.
On an egress, run the mpls rsvp-te resv-rroegress { { incoming | incoming-with-label } | { routerid | routerid-with-label } } * command.
By default, the labels carried in the transit LSP RRO in turn are inbound interface address with upstream label, LSR ID with upstream label, and outbound interface address. The labels carried in the egress LSP RRO in turn are inbound interface address with upstream label, LSR ID with upstream label.
Run commit
The configuration is committed.
Configure RSVP messages to carry tunnel Down causes.
Perform the following configurations on the transit and egress nodes of an MPLS TE tunnel.
Run system-view
The system view is displayed.
Run mpls
The MPLS view is displayed.
Run undo mpls rsvp-te send-message down-reason disable
RSVP messages are configured to carry tunnel Down causes.
By default, RSVP messages carry tunnel Down causes.
