FD 100/320Gbps NT and FX NT IHub Services Guide Services OverviewIssue: 13 3HH-11985-AAAA-TQZZA 853.17.3.7 signalingTable 14 signaling command3.17.3.8 shutdownTable 15 shutdown commandItem DescriptionSyntax signaling {off | tldp}Context configure>service>sdp sdp-idDescription This command specifies the signaling protocol used to obtain the ingress and egress labels inframes transmitted and received on the SDP. When signaling is off then labels are manuallyconfigured when the SDP is bound to a service. The signaling value can only be changed whilethe administrative status of the SDP is down.The no form of this command is not applicable. To modify the signaling configuration, the SDPmust be administratively shut down and then the signaling parameter can be modified andre-enabled.Default tdlpParameters off — Ingress and egress signal auto-labeling is not enabled. If this parameter is selected, theneach service using the specified SDP must manually configure VPN labels. This configurationis independent of the SDP’s transport type, GRE, MPLS (RSVP or LDP).tldp — Ingress and egress signaling auto labeling is enabled.Item DescriptionSyntax signaling {off | tldp}Context configure>service>sdp sdp-idDescription This command administratively disables an entity. When disabled, an entity does not change,reset, or remove any configuration settings or statistics.The operational state of the entity is disabled as well as the operational state of any entitiescontained within. Many objects must be shut down before they may be deleted.Services are created in the administratively down (shutdown) state. When a no shutdowncommand is entered, the service becomes administratively up and then tries to enter theoperationally up state. Default administrative states for services and service entities isdescribed below in Special Cases.The no form of this command places the entity into an administratively enabled state.(1 of 2)
