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.
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, 7x50 will use
lmp-peer-node-id (i.e. LmpNbrNodeId as per RFC 4631) as the dstIpAddr in the IP-header for the peer-specific messages (i.e. Link summary msgs, RSVP msgs). Note that 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.
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.
The no version of this command re-instates the default value for the delay timer.
The no form of this command reverts to the default value.
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.
The no form of this command removes any configured end-to-end recovery, and the GMPLS LSP becomes unprotected.
Use the config router gmpls lsp lsp-name no shutdown command to bring up the path after the retry limit is exceeded.
The no form of this command reverts the parameter to the default value.
The no form of the command reverts the timer to the default value.
The no form of the command removes the working-path definition.
The no form of the command removes the protect-path definition.
The no form of the command udates the bandwidth to zero.
The no form of the command removes the list of SRLG groups to exclude.
The no form of the command removes the list of SRLG groups to exclude.
The no form of this command removes the configued segement recovery, reverting to unprotected.
The no form of this command returns the timer to the default value.
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.
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.
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.
The no form of this command deletes the configuration.
The no form of this command sets the
hello-interval to the default of 3000 milliseconds. A value of 0 disables RSVP hellos.
The no form of the command reverts the hold-timer to the default value.
The no form of this command reverts to the default value.
The no form of this command reverts to the default value.
The no form of this command reverts to the default value.
The no form of this command reverts to the default value.
The no form of this command removes the tunnel group. All memebers of a GMPLS tunnel group must be removed and the tunnel group shutdown before the tunnel group can be deleted.
The no form of this command removes the description.
The no form of this command removes the far-end address
The no form of this command removes the member.
The no form of this command removes the member.
The member-threshold is the number of member GMPLS LSPs that must be operationally up before the GMPLS tunnel group is considered operationally up. If that number is not reached, then the GMPLS tunnel group is taken operationally down.
The no form of this command reverts the member threshold to 0.
In load-sharing mode, traffic is load-shared across the member GMPLS LSPs of the tunnel group. The same hashing algorithm is used as for LAG (see the "LAG and ECMP hashing" chapter of the Alcatel-Lucent 7450 ESS OS / 7750 SR OS / 7710 SR OS Interface Configuration Guides). If load-sharing is configured, then all of the GMPLS LSPs must terminate on the same far-end node. All of the ports used by GMPLS LSPs must be equivalent in that they must have the same named QoS policy, bandwidth, etc. Once more than one gLSP is associated with a tunnel group, the QoS policy / scheduler policy cannot be changed for any of the ports. All GMPLS LSPs must be unprotected end-to-end. Segment protection is allowed for GMPLS LSPs associated in a load sharing mode tunnel group.
In active-standby mode, only one member gLSP can be associated with the tunnel group.
The no form of this command removes the member.
