SNAX/XF and SNAX/APN Configuration and Management Manual

Objects for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
12-13
States for Other Types of Objects
STARTED
When an object is in the STARTED state, it either is ready to accept user data traffic or
is in the process of handling user data traffic. The STARTED state applies to LINE, LU,
and PU objects that have been defined through the ADD command and initialized with
the START command, and to SUBSYS objects that have been initialized with the
START command. SESSION and PROCESS objects are always in the STARTED
state.
STARTING
An object is in the STARTING state when a START command is issued for the object
and the object is being initialized. The STARTING state is a transition state between
the STOPPED and STARTED states. An object is usually in the STARTING state when
it is awaiting the completion of certain initialization protocols, such as PU and LU
activation. Once these events are completed, the object is placed in the STARTED
state.
STOPPED
The STOPPED state refers either to configured objects that have been added with the
ADD command but have not been started or to a service manager and lines that were
defined with the SCF ADD DEVICE command but have not been started. No data
traffic can flow while an object is in the STOPPED state. Most configuration attributes
can be altered only while the object is in the STOPPED state.
STOPPING
The STOPPING state refers to objects that have been defined and started but are now
being quiesced with the STOP command. Data and session traffic is not disrupted
abruptly, and there is no loss of data. Once all quiescing operations have taken place,
the object is placed in the STOPPED state.
If a START command is entered on behalf of the object while it is in the STOPPING
state, the object can be placed in the STARTED state again. Thus, it is not necessary
for the object to first be in the STOPPED state before being restarted