H3C Technologies H3C S7500E Series Switches - Manual (Page 55)

2-13
z
An MPLS LSR ID is in the format of an IP address and must be unique within an MPLS domain.
You are recommended to use the IP address of a loopback interface as the MPLS LSR ID.
z
At present, the S7500E series switches support enabling MPLS on only VLAN interfaces.
z
As MPLS will encapsulate original packets with single layer or multiple layers of labels, after
enabling MPLS on the VLAN interface of a VLAN, you are recommended to enable the
jumboframe function on the ports of the VLAN and configure a proper jumbo frame length to
prevent packets from being dropped due to size limit. For example, if two layers of MPLS labels
are required for encapsulating FTP packets, you need to configure the jumbo frame length on
related ports to 1544 bytes: 1518 bytes for the FTP packet + 4 bytes × 2 for the MPLS labels + 4
bytes for the VLAN tag + 14 bytes for the Ethernet frame header. For descriptions of the
jumboframe function, see Ethernet Port Configuration in the Layer 2 - LAN Switching
Configuration Guide .
Configuring a Static LSP
The principle of establishing a static LSP is that the outgoing label of an upstream LSR is the incoming
label of its downstream LSR.
Configuration Prerequisites
Before configuring a static LSP, be sure to complete these tasks:
z
Determining the ingress LSR, transit LSRs, and egress LSR for the static LSP.
z
Enabling MPLS on all these LSRs.
Configuration Procedure
Follow these steps to configure a static LSP:
To do… Use the command… Remarks
Enter system view system-view —
Configure a static LSP taking the
current LSR as the ingress
static-lsp ingress lsp-name
destination dest-addr { mask |
mask-length } nexthop
next-hop-addr out-label out-label
Required
Configure a static LSP taking the
current LSR as a transit LSR
static-lsp transit lsp-name
incoming-interface interface-type
interface-number in-label in-label
nexthop next-hop-addr out-label
out-label
Required