Filter
Top Products
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Commands and Trouble-Clearing Aids
Page 8-5busyout data-module
8
busyout data-module
This command puts the specified data module in a maintenance busy state, even
uninstalled data modules. No periodic or scheduled tests is performed on the
busied out data module or data channel until it is released and no call
processing can be executed on the data modules or over the data channels.
Warning alarms are generated (error type 18) on each maintenance object
busied out, so that INADS can access the state of the objects. The release data
module command returns the specified data module (or data channel) to
operation.
On a system with the duplication option, a busyout of a Network Control Data
Channel (DATA-CHL) or a Processor Interface Port Data Channels (PI-PT) are
preserved across SPE interchanges. The data channel extension must be
released before the data channel can be brought back into service.
Output
The following example shows the output from the busyout data-module 300
command.
Alt. Name
Alternate way to identify maintenance objects.
If the Object is The field contains
station extension
trunk
xxx/yyy
(where
xxx
= trunk group number
and
yyy
= member number)
private CO line
P/xxx
(where
xxx
= private CO line group
number)
Result
Test result: Pass, Abort, or Fail
Error Code
Numeric code explaining why the release failed or aborted. Refer
to the detailed list of the codes by test number for each MO.
Action/Object Qualifier Qualifier Description Permissions Defaults
Feature
Interactions
busyout
data-module
extension
Extension number (per
dial-plan)
Example:
busyout data-module 31300
init
inads
craft
nms
None None