3.17. GMPLS Configuration Command Reference

This command creates a context for the configuration of the Link Management Protocol (LMP) on the system.

This command specifies the GMPLS Loopback Address to be used by LMP. A corresponding gmpls-loopback interface must have been configured for LMP to be enabled.

This command creates a context to enable the specification of the LMP peer parameters. It also specifies the LMP peer node. For a GMPLS UNI, this is the UNI-N node at the far end of the IP control channel for the GMPLS UNI. If the peer loopback address is entered using the peer-loopback-address command, then this is used as the routable peer address; otherwise the peer-node-id is assumed to correspond to a routable peer loopback

This command enables the context for configuring an IP control channel for use by GMPLS UNI control plane (RSVP and LMP).

This command configures the transmission interval for LMP Hello packets. The dead-interval specifies the period after which the IPCC is declared down if no hello packets are received from the LMP peer.

This command configures the mandatory peer-interface-address. It is the destination address of the IPCC on the peer UNI-N used to reach the GMPLS Router ID of the UNI-N peer. It corresponds to the lmpCcRemoteIpAddr in RFC 4631.

This command specifies whether this node takes the active or the passive role in establishing the LMP session to the peer over a GMPLS UNI.

This command administratively enables or disables the IP control channel.

This command configures the time to live (TTL) for all packets (GMPLS RSVP and LMP) on the IP control channel, which allows the TTL to be optimized for multi-hop communication networks between the GMPLS UNI-C and UNI-N.

This command configures a control channel router instance on the CPM to use as the endpoint of the GMPLS IP control channel (IPCC). If a control channel router that is not “Base” is configured, then the gmpls-loopback-address command must be configured to refer to the GMPLS loopback IP interface configured within the control channel router.

The config>router>gmpls>peer peer-node-id command must specify a peer that is reachable via a control channel router instance configured for LMP.

The no form of the command removes the IPCC from the control channel router instance.

This command configures a loopback address to refer to the GMPLS loopback IP interface configured within the control channel router.

The no form of the command removes the configured loopback address.

The IP address corresponding to the GMPLS loopback address configured on the LMP peer. If peer-loopback-address is entered, then this is used as the routable peer address, otherwise the peer-node-id is assumed to correspond to a routable peer loopback.

peer-loopback-address is an optional configurable field. If peer-loopback-address is not configured, the router will use lmp-peer-node-id (that is LmpNbrNodeId as per RFC 4631) as the dstIpAddr in the IP-header for the peer-specific messages (that is, Link summary msgs, RSVP msgs).

Note: The peer-interface-address is mandatory; it is the destination address of the IPCC on the peer UNI-N used to reach the GMPLS Router ID of the UNI-N peer. It corresponds to the lmpCcRemoteIpAddr in RFC 4631.

This command specifies the interval between resubmitted LMP messages.

This command specifies how many times LMP resends a message before restarting the process.

This command administratively enables or disables LMP with a given peer.

This command assigns a Traffic Engineering (TE) Link to a given LMP peer. The TE Link with ID te-link-id must already have been created under config>router>lmp>te-link.

This command administratively enables or disables the TE Link.

This command creates a Traffic Engineering (TE) Link in LMP across a GMPLS UNI. An unsigned integer TE link ID must be specified when the TE Link is first created. Once the link is created, the user can configure the link name (that is 'link-name te-link-name'). From here, the user can refer to this TE Link by either the unsigned integer or the ASCII name.

This command creates a data bearer assigned to a TE Link. Only one data bearer may be configured within a given TE Link.

This command configures the port associated with the data bearer. The port must be a physical black and white Ethernet port.

This command configures the identifier assigned to the data-bearer at the LMP peer node. For a GMPLS UNI, this is the UNI-N node.

This command administratively enables or disables the data bearer.

This command configures text names for the TE Link.

This command configures the identifier assigned to the TE Link at the LMP peer node. For a GMPLS UNI, this is the UNI-N node.

This command administratively enables or disables LMP.

This command enables the context to configure GMPLS parameters. GMPLS is not enabled by default and must be explicitly enabled using no shutdown. The shutdown command administratively disables GMPLS.

The no form of this command deletes this GMPLS protocol instance; this will remove all configuration parameters for this GMPLS instance.

GMPLS must be shut down before the GMPLS instance can be deleted. If GMPLS is not shut down when the no gmpls command is executed, a warning message on the console indicates that GMPLS is still administratively up.

This command configures the local values for the max-recovery and the max-restart intervals used in the RSVP Graceful Restart Helper feature when applied to a GMPLS UNI.

The values are configured globally in GMPLS.

The no version of this command re-instates the default value for the delay timer.

This command configures the integer used by RSVP to declare that a reservation is down or the neighbor is down.

The no form of this command resets the configuration to the default value.

This command creates a GMPLS LSP that is signaled dynamically by the router.

When the LSP is created, the egress router must be specified using the to command and a working-path must be specified.

GMPLS LSPs are created in the administratively down (shutdown) state.

The no form of this command deletes the GMPLS LSP. All configuration information associated with this GMPLS LSP is lost. The GMPLS LSP must be administratively shut down before it can be deleted.

This command defines the end-to-end recovery type for the gLSP. This is the recovery model between the source and terminating UNI-C nodes of the GMPLS LSP.

The no form of this command removes any configured end-to-end recovery, and the GMPLS LSP becomes unprotected.

This command configures the encoding type of the payload carried by the GMPLS LSP; line is the only supported type.

This command configures the type of payload carried by the gLSP. Standard ethertype values are used for packet and Ethernet LSPs (see RFC 3471).

This command specifies the protect path for a GMPLS LSP. At least one protect path must be specified if a GMPLS LSP uses 1-to-N end-to-end protection. The path-name parameter must correspond to a path defined under config>router>gmpls>path.

The no form of the command removes the protect-path definition.

This command specifies the bandwidth to be signaled for the path of the GMPLS LSP. Bandwidth is specified in terms of the RFC 3471 signal type name.

If an empty path is configured or the first hop TE Link is not configured, the system will automatically select a TE Link to use for a GMPLS LSP path based on the lowest available TE Link ID with a matching bandwidth (if a bandwidth is configured for the GMPLS LSP). During a data-bearer link allocation request, an RSVP-requested GMPLS LSP BW can be either a non-zero value as per RFC 3471 signal-type, or it can be zero). There are the following cases:

The no form of the command updates the bandwidth to zero.

This command specifies a list of one to five SRLG groups in the optical network which the router can request to the UNI-N that the GMPLS LSP path should avoid by signaling it in the XRO of the RSVP path message. Each group-name must have been defined under config>router>if-attribute>srlg-group.

The no form of the command removes the list of SRLG groups to exclude.

This command specifies a peer node to use for the first hop of the GMPLS LSP. If specified, this command forces the GMPLS LSP to use a specific UNI-N node on ingress to the optical network. This command is only applicable if 1toN end to end protection is used.

The no form of the command removes the list of SRLG groups to exclude.

This command defines the requested segment recovery type for the gLSP path. This is the recovery capability requested by the router UNI-C to the UNI-N for recovery in segments of the optical network between ingress and egress UNI-N nodes.

The no form of this command removes the configured segment recovery, reverting to unprotected.

This command administratively enables or disables the GMPLS LSP path.

This optional command specifies the number of attempts software should make to re-establish the GMPLS LSP after it has failed. After each successful attempt, the counter is reset to zero.

When the specified number is reached, no more attempts are made and the GMPLS LSP path is put into the shutdown state.

Use the config router gmpls lsp lsp-name no shutdown command to bring up the path after the retry limit is exceeded.

This command configures the time (in s), for LSP re-establishment attempts after it has failed. The retry time is jittered to +/- 25% of its nominal value.

The no form of this command resets the parameter to the default value.

This command configures the time (in s), for LSP reversion attempts after it has failed.

The no form of the command resets the timer to the default value.

This command administratively enables or disables the GMPLS LSP.

This command configures the type of switching required for the gLSP. As defined in RFC 3471. The default CLI value is dcsc, which indicates that Digital Channel Switch Capable (DCSC) should be signaled.

This command specifies the GMPLS loopback address of the far-end UNI-C router for a GMPLS LSP. When creating a GMPLS LSP, this command is mandatory.

This command specifies the working path for a GMPLS LSP. One working path must be specified for each GMPLS LSP. The path-name parameter must correspond to a path defined under config>router>gmpls>path.

The no form of the command removes the working-path definition.

This command configures the initial GMPLS LSP path retry timer.

The new GMPLS LSP path initial retry timer is used instead of the retry-timer to abort the retry cycle when no RESV is received. The retry-timer exclusively governs the time between two retry cycles and to handle retrying of a GMPLS LSP path in a failure case with PATH errors or RESVTear.

The no form of this command returns the timer to the default value.

This command creates the path to be used for a GMPLS LSP. A path can be used by multiple GMPLS LSPs. A path can specify some or all hops from ingress to egress and they can be either strict or loose.

Paths are created in a no shutdown state. A path must be shut down before making any changes (adding or deleting hops) to the path. When a path is shut down, any GMPLS LSP using the path becomes operationally down.

The no form of this command deletes the path and all its associated configuration information. All the GMPLS LSPs that are currently using this path will be affected. A path must be shut down and unbound from all GMPLS LSPs using the path before it can be deleted. The no path path-name command will not result in any action except a warning message on the console indicating that the path may be in use.

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 inter-operating with the Nokia 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.

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.

This command specifies parameters for the RSVP session to a neighboring GMPLS UNI-N node. The peer-node-id is the control plane identifier for the adjacent UNI-N node.

The no form of this command deletes the configuration.

This command configures the RSVP hello packet interval (in ms), towards the peer UNI-N node.

The no form of this command sets the hello-interval to the default value. A value of 0 disables RSVP hellos.

This command specifies the amount of time that the ingress node holds before programming its data plane and declaring a GMPLS LSP up. This occurs anytime the ingress UNI-C node brings up a GMPLS LSP path or reroutes a GMPLS LSP. The hold-time value should be configured to reflect the data path programming time for the optical technology used between the ingress and egress UNI-N nodes.

The no form of the command resets the configuration to the default value.

This command disables or enables RSVP adjacency with the neighboring UNI-N peer node.

This command configures the value of the Rapid Retransmission Interval. It is used in the re-transmission mechanism to handle unacknowledged message_id objects and is based on an exponential back-off timer.

Re-transmission interval of a RSVP message with the same message_id = 2 * rapid-retransmit-time interval of time.

The node stops re-transmission of unacknowledged RSVP messages:

The Rapid Retransmission Interval must be smaller than the regular refresh interval configured in config>router>gmpls>refresh-time.

The no form of this command resets the configuration to the default value.

This command configures the value of the Rapid Retry Limit. This is used in the retransmission mechanism based on an exponential backoff timer in order to handle unacknowledged message_id objects. The RSVP message with the same message_id is retransmitted every 2 * rapid-retransmit-time interval of time. The node will stop retransmission of unacknowledged RSVP messages whenever the updated backoff interval exceeds the value of the regular refresh interval, or the number of retransmissions reaches the value of the rapid-retry-limit parameter, whichever comes first.

The no form of this command resets the configuration to the default value.

This command configures the interval (in s), between the successive Path and Resv refresh messages. RSVP declares the session down after it misses a consecutive number of refresh messages equal to the configured keep-multiplier number.

The no form of this command resets the command to the default value.

This command disables or enables GMPLS.

This command enables the use of a Traffic Engineering (TE) Link (which has previously been configured under config>router>lmp) in GMPLS.

The no form of this command resets the configuration to the default value.

This command enables or disables the TE Link in GMPLS.