Configuring Static Segments; Prerequisites; Configuring A Static Adjacency Segment - H3C SR6600 Command Reference Manual

2. Configuring an MPLS TE tunnel to use static SRLSPs

Configuring static segments

Prerequisites

Before you configure static segments for a static SRLSP, perform the following tasks:
•
Determine the ingress node, transit nodes, and egress node of the static SRLSP.
•
Determine the incoming label for the adjacency segment from a node to next hop of the node.
Determine the incoming label of the prefix segment for the destination IP address on each node.
On a device, a static SRLSP, a static LSP, and a static CRLSP cannot use the same incoming
label. For more information about CRLSP, see MPLS TE configuration in MPLS Configuration
Guide.
•
Enable MPLS on all nodes and interfaces that will participate in MPLS forwarding. For
information about enabling MPLS, see MPLS basics configuration in MPLS Configuration
Guide.

Configuring a static adjacency segment

Restrictions and guidelines
This task is required on all nodes of a static SRLSP.
Multiple static SRLSPs can share an adjacency segment.
If you specify the next hop address for a static adjacency segment, make sure the following
requirements are met:
•
The device has a route to the next hop address.
•
MPLS is enabled on the output interface of the route.
If you specify an output interface for a static adjacency segment, make sure the following
requirements are met:
•
The interface is up.
•
The interface can receive direct routes.
•
MPLS is enabled on the interface.
A static adjacency segment must use a different incoming label than existing static LSPs, static PWs,
and static CRLSPs. If not, the configured adjacency segment is unavailable. The adjacency segment
cannot become available even if you change the incoming label of the static LSP, static PW, or static
CRLSP. To resolve this problem, you must delete the existing adjacency segment and configure a
new one with a different incoming label.
Procedure
1. Enter system view.
system-view
2. Configure a static adjacency segment.
static-sr-mpls adjacency adjacency-path-name in-label label-value
{ nexthop ip-address | outgoing-interface interface-type
interface-number }
The next hop address for a static adjacency segment cannot be a local public IP address.
8