VLL Services
7705 SAR OS Services Guide Page 237
Description The shutdown command administratively disables an entity. The operational state of the entity is
disabled as well as the operational state of any entities contained within. When disabled, an entity
does not change, reset, or remove any configuration settings or statistics. Many objects must be shut
down before they can be deleted. Many entities must be explicitly enabled using the no shutdown
command.
The no form of this command places the entity into an administratively enabled state.
Services are created in the administratively down (shutdown) state. When a no shutdown command
is entered, the service becomes administratively up and then tries to enter the operationally up state.
Default administrative states for services and service entities are described in the following Special
Cases.
Special Cases
Service Admin State — bindings to an SDP within the service will be put into the out-of-service
state when the service is shut down. While the service is shut down, all customer packets are
dropped and counted as discards for billing and debugging purposes.
Service Operational State — a service is considered operational if at least one SAP and one SDP
are operational.
SDP (global) — when an SDP is shut down at the global service level, all bindings to that SDP are
put into the out-of-service state and the SDP itself is put into the administratively and
operationally down states. Packets that would normally be transmitted using this SDP binding
will be discarded and counted as dropped packets.
SDP (service level) — shutting down an SDP within a service only affects traffic on that service
from entering or being received from the SDP. The SDP itself may still be operationally up for
other services.
To Next Page
Loading...
