Alcatel-Lucent 7450 Manual page 480

GMPLS Commands
shutdown
Syntax [no] shutdown
Context config>router>gmpls>path
Description
This command disables GMPLS LSPs using the path. All services using these GMPLS LSPs are
affected. Paths are created in the shutdown state.
The no form of this command administratively enables the path. All LSPs, where this path is defined
as primary or defined as standby secondary, are (re)established.
Default no shutdown
hop
Syntax hop hop-index node-id node-id [te-link te-link-id] {strict | loose}
no hop hop-index
Context config>router>gmpls>path
Description This command specifies the node ID of the hops that the GMPLS LSP should traverse on its way to
the egress UNI-C router.
The GMPLS LSP ingress and egress node IDs can be included as the first and the last hop. This is
necessary when interoperating with the Alcatel-Lucent 1830 PSS.
The no form of this command deletes hop list entries for the path. All of the GMPLS LSPs currently
using the path are affected. Additionally, all services actively using these GMPLS LSPs are affected.
The path must be shut down first in order to delete the hop from the hop list. The no hop hop-index
command will not result in any action except a warning message on the console indicating that the
path is administratively up.
Default none
Parameters hop-index — Specifies the order of the hops. The LSP always traverses from the lowest hop index to
node-id — Specified the node ID of the transit GMPLS LSR. This can be an IPv4 address or a 32-bit
loose — Specifies that the route taken by the GMPLS LSP from the previous hop to this hop can
strict — Specifies that the LSP must take a direct path from the previous hop router to this router. No
Page 480
the highest. The hop index does not need to be sequential.
Values 1 — 1024
unsigned integer identifier of the data plane switching node of the adjacent UNI-N.
traverse through other LSRs. Multiple hop entries with the node-id are flagged as errors. Either
the loose or strict keyword must be specified.
transit routers between the previous router and this router are allowed. If the IP address specified
is the interface address, then the LSP must use that interface. If there are direct parallel links
between the previous router and this router, and if the system IP address is specified, then any
one of the available interfaces can be used by the LSP. The user must ensure that the previous
router and this router have a direct link. Multiple hop entries with the same IP address are
flagged as errors. Either the loose or strict keyword must be specified.
7450 ESS MPLS Guide