Disruptive Diagnostics; Mixed Diagnostics - Paradyne COMSPHERE 3610 Operator's Manual

COMSPHERE 3600 Series Data Service Units

Disruptive Diagnostics

In a disruptive diagnostic network, the same channel
(that is the primary channel) that carries user-transmitted
data between the control and tributary DSUs also carries
diagnostic data. Since diagnostic data is transmitted on the
primary channel, this may interrupt user-transmitted data
and cause errors in transmission. Retransmission of data
blocks may be required. (Most diagnostic disruptions are
less than 0.5 seconds in duration and should not cause loss
of the communication session.)
If there is a dialed connection between the control and
tributary via the DBMs and the customer data is still
routed on the DDS link, the standby facility (Standby
mode) provides a nondisruptive channel for diagnostic
traffic.
A tributary, whether a standalone or carrier-mounted
model, can receive disruptive tests and commands from its
local DCP as well as from the control for point-to-point
circuits. Local health and status commands are
nondisruptive. Commands directed to a tributary DSU
from the NMS or a control DSU's DCP may cause data
errors requiring retransmission of the data.

Mixed Diagnostics

This method is used primarily for multipoint
configurations, with the advantage that it uses a standard
non-reduced data clock while still providing nondisruptive
health and status updates. It supports a combination of
nondisruptive and disruptive techniques. Health and status
information is sent nondisruptively (using the upstream
technique described for the Multipoint Circuit), while
user-initiated commands and tests are sent disruptively. To
use Mixed diagnostics in a point-to-point configuration,
you must configure the DSUs for multipoint operation
using the LinkConfig (Link Configuration) configuration
option as described in Table 6-4,
Configuration Options, in Chapter 6.
Addressing
A Model 3611 DSU has two addresses:
Physical address
Control network address (user-definable)
The physical address is determined by the location of
the DSU in the COMSPHERE 3000 Series Carrier cabinet
configuration. It is only used for commands issued from
1-14
Diagnostic General
July 1999
the SDCP and it consists of the carrier number and slot
number.
The ADp control network address is used by the NMS
to access the DSU. A control network address is any
number in the range from 1 through 255 with the
following exceptions:
The number 192 is reserved as a broadcast address
and must not be assigned as a network control
address.
The numbers 191 and 255 may not be assigned to
any DSU with an attached DBM. (The DBM
address is always the DSU's network address
plus 1.)
This range of addresses is valid for any position the
DSU occupies in the network (control, tributary, extended
control, extended tributary).
NOTE
When using DPII protocol, a
tributary DSU must have an
address in the range of 1 through
80. (Address 80 cannot be
assigned to a DSU with an
attached DBM.)
The control network address is protocol-dependent, as
explained in the Control Network Address
follows.
You must assign a unique network address for each of
the following:
Each control DSU on the same control channel.
Each extended control DSU attached to a single
tributary.
Each tributary in a multipoint circuit.
A tributary DSU also has a network address, which
follows the same addressing scheme as the control
network address.
An NMS can access a tributary DSU by first
addressing the control DSU and then addressing the
tributary DSU from the control. An address issued by the
NMS is defined as control channel/control network
address/tributary network address (e.g., 1/157/1). This
type of addressing is called link-level network addressing.
section that
3610-A2-GB91-90