Alcatel-Lucent 7450 Manual page 87

MPLS and RSVP
<if-name> could be numbered or unnumbered interface using an Ethernet port.
<src-tunnel-num> is a mandatory create time parameter for mpls-tp tunnels, and has to be assigned
by the user based on the configured range of tunnel ids. The src-global-id used for the LSP ID is
derived from the node-wide global-id value configured under config>router>mpls>mpls-tp. A
tunnel can not be un shutdown unless the global-id is configured.
The from address of an LSP to be used in the tunnel identifier is taken to be the local node's node-
id/global-id, as configured under config>router>mpls>mpls-tp. If that is not explicitly configured,
either, then the default value of the system interface IPv4 address is used
The to node-id address may be entered in 4-octet IPv4 address format or unsigned 32-bit format.
This is the far-end node-id for the LSP, and does do need to be routable IP addresses.
The from and to addresses are used as the from and to node-id in the MPLS-TP Tunnel Identifier
used for the MEP ID.
Each LSP consists of a working-tp-path and, optionally, a protect-tp-path. The protect-tp-path
provides protection for the working-tp-path is 1:1 linear protection is configured (see below).
Proactive OAM, such as BFD, is configured under the MEP context of each path. Protection for
the LSP is configured under the protect-tp-path MEP context.
The to global-id is an optional parameter. If it is not entered, then the destination global ID takes
the default value of 0. Global ID values of 0 are allowed and indicate that the node's configured
Global ID should be used. If the local global ID value is 0, then the remote to global ID must also
be 0. The to global ID value cannot be changed if an LSP is in use by an SDP.
The to tunnel number is an optional parameter. If it is not entered, then it is taken to be the same
value as the source tunnel number.
LSPs are assumed to be bidirectional and co-routed. Therefore, the system will assume that the
incoming interface is the same as the out-link.
The next-hop ip-address can only be configured if the out-link if-name refers to a numbered IP
interface. In this case, the system will determine the interface to use to reach the configured next-
hop, but will check that the user-entered value for the out-link corresponds to the link returned by
the system. If they do not correspond, then the path will not come up. Note that if a user changes
the physical port referred to in the interface configuration, then BFD, if configured on the LSP,
will go down. Users should therefore ensure that an LSP is moved to a different interface with a
different port configuration in order to change the port that it uses. This is enforced by blocking
the next-hop configuration for an unnumbered interface.
There is no check made that a valid ARP entry exists before allowing a path to be un shut.
Therefore, a path will only be held down if BFD is down. If static ARP is not configured for the
interface, then it is assumed that dynamic ARP is used. The result is that if BFD is not configured,
a path can come up before ARP resolution has completed for an interface. If BFD is not used, then
7450 ESS MPLS Guide Page 87