Introduction
1-15
3610-A2-GB91-90
July 1999
The DPII and ADp protocols both use link-level
network addressing. In a DMC environment, however,
each DSU and modem has a unique overall network
address. This address is determined automatically by
ANALYSIS based upon the SDU, local DSU, and remote
DSU addresses prior to firmware version 4.25. Firmware
version 4.25 or greater is no longer based upon the SDU;
each DSU has its own unique address.
If earlier versions of the 3600 Series DSUs are part of
your network, Table 1-5 summarizes the addresses
displayed by the DSU when a specific protocol is
selected.
Table 1-5
Protocols and Addressing
DSU SW ver
Address Displayed
3.xx or below
All protocols:
Addressing was carrier and
slot dependent.
Network address was the
tributary’s address.
4.xx or 5.xx
All protocols:
Control address could be set
from the DCP or SDCP.
ADp Address displayed:
Table 1-6
used to convert
ADp address to DPII
address
Table 1-7
used to convert
ADp address to DMC
address
6.xx
ADp mode – ADp address
DPII mode – DPII address
DMC mode –
Table 1-7
used
to convert ADp address to
DMC address.
Control Network Address
A control DSU’s network address can be within a
range of 1 to 255 when using ADp. Although an attached
DBM occupies the same slot as its parent DSU, it is a
separate addressable entity that is assigned its own
address (the DSU’s address plus 1). The System
Controller and the 6700 or 6800 Series NMS support
256 addresses on each control channel (CC). Refer to
Table 1-6
. When the control DSU is using ADp, the range
of network addresses is 1 through 255; if the DSU is using
DPII, the range of network addresses would be 11 through
77.
The control DSUs on a single network interface
(control channel) may be assigned addresses in whatever
order you decide. For example, a DSU in Slot 1 of a
carrier may be assigned an address of 149, a DSU in
Slot 2 may be assigned an address of 85, and so on.
However, it is recommended that only odd numbers be
assigned to DSUs, thereby allowing for the addition of
DBMs.
The address entered at the DCP is either the ADp or
DPII network address. When addressing commands from
an NMS and the DPII or DMC protocol is used, the ADp
network address must be converted to the
DATAPHONE II or DMC address.
DPII protocol does not accept addresses ending in
0 or 9. Refer to
Table 1-7
to convert the ADp network
address to a DATAPHONE II address.
Prior to firmware version 4.25, DMC protocol was
carrier and slot dependent. For firmware version 4.25 or
greater, each control DSU has a unique hexadecimal
address. Refer to
Table 1-7
to convert the ADp network
address to the DMC address (remember that carrier and
slot only apply to firmware versions less than 5.0). This
table shows address conversions for a control DSU. To
determine the tributary DSU addresses, convert the
control DSU address to the DMC address, and increment
the DMC address by one for each tributary on the circuit.
For example, a control DSU ADp address of 32 is
equivalent to a DMC address of 800. The control DSU’s
tributary addresses are 801, 802, 803, etc.
Содержание COMSPHERE 3610
Страница 4: ...COMSPHERE 3600 Series Data Service Units C July 1999 3610 A2 GB91 90 Notices ...
Страница 16: ...COMSPHERE 3600 Series Data Service Units x July 1999 3610 A2 GB91 90 ...
Страница 27: ...Introduction 1 11 3610 A2 GB91 90 July 1999 Figure 1 4 NMS Interfaces to the SDU 1 of 2 ...
Страница 120: ...COMSPHERE 3600 Series Data Service Units 4 40 July 1999 3610 A2 GB91 90 This page intentionally left blank ...
Страница 128: ...COMSPHERE 3600 Series Data Service Units 5 6 July 1999 3610 A2 GB91 90 ...
Страница 186: ...COMSPHERE 3600 Series Data Service Units 6 58 July 1999 3610 A2 GB91 90 ...
Страница 187: ...A 1 3610 A2 GB91 90 July 1999 Data Service Unit Menu A ...
Страница 188: ...COMSPHERE 3600 Series Data Service Units A 2 July 1999 3610 A2 GB91 90 ...
Страница 189: ...Data Service Unit Menu A 3 3610 A2 GB91 90 July 1999 ...
Страница 190: ...COMSPHERE 3600 Series Data Service Units A 4 July 1999 3610 A2 GB91 90 ...
Страница 192: ...COMSPHERE 3600 Series Data Service Units B 2 July 1999 3610 A2 GB91 90 This page intentionally left blank ...
Страница 224: ...COMSPHERE 3600 Series Data Service Units C 22 July 1999 3610 A2 GB91 90 ...
Страница 246: ...COMSPHERE 3600 Series Data Service Units E 2 July 1999 3610 A2 GB91 90 Figure E 1 Control Channel ...
Страница 247: ...Network Management Connectivity E 3 3610 A2 GB91 90 July 1999 Figure E 2 Extended Control Channel ...
Страница 259: ...Pin Assignments F 11 3610 A2 GB91 90 July 1999 Figure F 8 EIA 232 D Crossover Cable 4951 035F ...
Страница 263: ...Troubleshooting G 3 3610 A2 GB91 90 July 1999 Figure G 2 No Signal NS Condition Troubleshooting ...
Страница 265: ...Troubleshooting G 5 3610 A2 GB91 90 July 1999 Figure G 4 Out of Frame OOF Condition Troubleshooting ...
Страница 272: ...COMSPHERE 3600 Series Data Service Units H 6 July 1999 3610 A2 GB91 90 ...
Страница 278: ...COMSPHERE 3600 Series Data Service Units I 6 July 1999 3610 A2 GB91 90 ...
Страница 280: ...COMSPHERE 3600 Series Data Service Units J 2 July 1999 3610 A2 GB91 90 ...
Страница 292: ...COMSPHERE 3600 Series Data Service Units L 10 July 1999 3610 A2 GB91 90 ...