Digital Data Network DDN
Digital Data Network DDN
Digital Data Network DDN
Network
DDN
ONU 200 (DCC via SMA-16)
SMA-16
STM-1
Connection
Note:
C C SU SU SU SU SU SU SU SU SU SU SU SU SU C
ONU200
TMU PS
M M C /SU
M M U
1 2
201 202 203 204 205 206 207 208 209 210 211 212 214 215 216 217 218 219
213
ONU 200 (NU-LINK)
2 Mb/s DDF
MSV5
CPM-ECC
CPM-AM
Connection 1
2
3
4
5
6
..
20
AM64K
TU2M
SWM64k-A
SWM64k-B
LM4
LM4
SWM4M-A
SWM4M-B
FOREIGN
V5CM-B
V5CM-A
SDH
PRM
NETWORK
DDF
1
2
3 CMM-16E1
4
5
6
7
8
9
10
ONU200
…
16
C C SU SU SU SU SU SU SU SU SU SU SU SU SU C TMU PS
M M C /SU
M M U
1 2
201 202 203 204 205 206 207 208 209 210 211 212 214 215 216 217 218 219
213
ONU 200 (NU-LINK)
2 Mb/s DDF
MSV5
CPM-ECC
CPM-AM
Connection 1
2
3
4
5
6
..
20
AM64K
TU2M
SWM64k-A
SWM64k-B
LM4
LM4
SWM4M-A
SWM4M-B
FOREIGN
V5CM-B
V5CM-A
SDH
PRM
NETWORK
DDF
1
2
3 CMM-16E1
4
5
6
7
8
9
10
ONU200
…
16
C C SU SU SU SU SU SU SU SU SU SU SU SU SU C TMU PS
M M C /SU
M M U
1 2
201 202 203 204 205 206 207 208 209 210 211 212 214 215 216 217 218 219
213
ONU 200 (NU-LINK) :
ONU200 requirement:
CCU-16 and CMM-16E1
Software version – DMP 3.6 or higher
MSV5 requirement:
TU-2M, AM64K and V5CM
Software version – DMP 3.6 or higher
Connection between ONU200 and MSV5 is through 2 Mb/s connection via foreign SDH network
Once the NU-Link has been established, “CC-Channel Error” alarm will clear and link would be “operational”
RNU-8C:
NT RNU-8C can be made online through 2 types a connection to the V5 card of the MSV5:
Case 1:
MSV5 RNU-8C
In this case, the NT is connected to one of the 20 TU-2M ports in MSV5.
Physical connection between them, would be coaxial cable (4 wires); terminated on the DDF.
First of all, the NT must be assigned an unique number called NU-ID (also called SISA node number).
When the physical connection is through, “LOS” alarm on both the MSV5 and NT will clear.
Create a new NU-link with the same NU-ID as in RNU-8C (Make sure no similar NU-ID present in
MSV5 !) from the V5 manager.
The newly created NU-link must be referenced to the TU-2M port, physically connected to MSV5.
Define the CC channel used to communicate to the NT:
TS 16 – DMP 3.5.4 and lower (other 30 channels can be used for data)
TS 0 – DMP 3.5.5 and higher (other 31 channels can be used for data)
“RED” LED light on the NT will stop blinking and turned off, once it’s online.
RNU-8C:
NT RNU-8C can be made online through 2 types a connection to the V5 card of the MSV5:
Case 1:
MSV5 RNU-8C
In this case, the NT is connected to one of the 20 TU-2M ports in MSV5.
Physical connection between them, would be coaxial cable (4 wires); terminated on the DDF.
First of all, the NT must be assigned an unique number called NU-ID (also called SISA node number).
When the physical connection is through, “LOS” alarm on both the MSV5 and NT will clear.
Create a new NU-link with the same NU-ID as in RNU-8C (Make sure no similar NU-ID present in
MSV5 !) from the V5 manager.
The newly created NU-link must be referenced to the TU-2M port, physically connected to MSV5.
Define the CC channel used to communicate to the NT:
TS 16 – DMP 3.5.4 and lower (other 30 channels can be used for data)
TS 0 – DMP 3.5.5 and higher (other 31 channels can be used for data)
“RED” LED light on the NT will stop blinking and turned off, once it’s online.
RNU-8C:
NT RNU-8C can be made online through 2 types a connection to the V5 card of the MSV5:
Case 1:
MSV5 RNU-8C
In this case, the NT is connected to one of the 20 TU-2M ports in MSV5.
Physical connection between them, would be coaxial cable (4 wires); terminated on the DDF.
First of all, the NT must be assigned an unique number called NU-ID (also called SISA node number).
When the physical connection is through, “LOS” alarm on both the MSV5 and NT will clear.
Create a new NU-link with the same NU-ID as in RNU-8C (Make sure no similar NU-ID present in
MSV5 !) from the V5 manager.
The newly created NU-link must be referenced to the TU-2M port, physically connected to MSV5.
Define the CC channel used to communicate to the NT:
TS 16 – DMP 3.5.4 and lower (other 30 channels can be used for data)
TS 0 – DMP 3.5.5 and higher (other 31 channels can be used for data)
“RED” LED light on the NT will stop blinking and turned off, once it’s online.
Case 2:
NT must be assigned an unique number called NU-ID (also called SISA node number).
Create a new NU-link with the same NU-ID as in RNU-8C (Make sure no similar NU-ID present in
MSV5 !) from the V5 manager.
The newly created NU-link must be referenced to TU-2M port, physically connected to MSV5.
Define the CC channel used to communicate to the NT:
TS 16 – DMP 3.5.4 and lower (other 30 channels can be used for data)
TS 0 – DMP 3.5.5 and higher (other 31 channels can be used for data)
“RED” LED light on the NT will stop blinking and turned off, once it’s online.
2 Wire Termination from the MDF
MDF MAT 6D Total of 16 NT’s can connected
Data rate can be selected (64Kb/s or
128Kb/s)
V.35 Interface
Note:
Connection type for all the ISDN port (B1, B2 and D channel) must be changed
to “flexible” instead of “V5”.
SU-16UKoQ
MDF WATSON
V.35 Interface
4 Wire Termination from the MDF
Total of 2 NT’s can connected
Data rate can be selected
2 Mb/s
N x 64 Kb/s (N= max 31)
Note:
EPI-1(1st 2-wire) and EP1-2 (2nd 2-wire) alarm will clear when all 4-wires has been terminated
LED of the NT will change from red to orange as soon as it comes “online”
SU-2 HDSL NT must not be online when change of data rate is done (between structured and
unstructured)
MDF SDSL -EL
V.35 Interface
2 Wire Termination from the MDF
Total of 8 NT’s can connected
Data rate can be selected
2 Mb/s
N x 64 Kb/s (N= max 31)
Note:
“V35” light on the NT will be permanently ON when test signal is pumped into
SU-8SDSL to the V.35 interface.
RNU-8C NT
DDF
1
2 Mb/s
Connection V.35 Interface
(COAXIAL)
Note:
S2M SUVAR2 card can be equipped with 2 sub modules (S2M, V.35, etc)
SUB-S2M
2 Mb/s G.703 signal
Substructure can be changed between 2 Mb/s (unstructured) or N x 64Kb/s (structured)
V.35 RNU-8C can be connected to this interface with a data rate of N x 64 Kb/s (N= max 31)
SUB-V35
Provides a DTE interface for V.35 test signal
SUVAR2 Data rate can be N x 64 Kb/s (N= max 31) or
Data rate can be 2Mb/s
VC12 Cross Connection
VC12_1
STM-1
VC12_1
X 64K_1
64K_2
64K_3
VC12_2
64K_31
VC12_3
VC12_2
VC12_4 64K_1
VC12_5
VC12_6 PORT 1
X 64K_2
64K_3
64K_4
B1
VC12_7 64K_31
B2
64 K Cross Connection
VC12_8
PORT 2 VC12_8
VC12_9 B1
VC12_63 B2
PORT 3
B1 CCU-8
CMM-OPT B2
PORT 16
B1
MAT 6D B2
V.35 interface
Data Rate of 128 Kb/s
SU-16UkOQ
Note:
Each “B” channel on the SU-16UKoQ card corresponds to 64 Kb/s data channel
In order to provide 128 Kb/s traffic data via MAT-6D, Both B1 and B2 channel must be cross connected.
64 Kb/s channel from the MAT-6D port is cross connected to one of the 64 Kb/s channel in the CCU
The corresponding VC12 channel is then cross connected to any VC12 channel on the Line card (CMM)
of the ONU200
STM-1
VC4
64K_1
64K_2
X 64K_1
Connection VC12_3
64K_3 64K_3
64Kb/s Cross (SW4M-24)
64K_31 64K_31 VC12_5
Connection
PORT 2 (SWM64K) VC12_2 VC12_6
64K_31 64K_31
PORT 20 VC12_20
AM –STM1 OPT
TU – 2M AM 64K
ONLINE
VIA
SOA
Note:
All DMP equipments have a unique online method on SOA and most important elements are:
It is divided into 3:
b. NE Access No:
“SISA node no” is a unique number assigned to every node. SOA system administrators recognizes
the node using this node number.
The “NE Access No” of nodes, interconnected together will be similar. This number is provided by
the SOA system administrator; also known as sisa number.
NE Access No for redundant SOA is useful when two SOA servers are in service (Worker and
protection).
Layer 3 address corresponds to NSAP address of the node and SOA (also known as OSI addressing)
2. Area Address
1.The default address is the same for all nodes and also for SOA. (49 and ten pair of zeros).
2.Area address depends on the configured DCN; It will be similar as the gateway router area address.
For example alor setar area address is “0203”.
3.The first 4 digits of the system ID varies and depends on type of equipment:
a. 0000 – MS1/4
b. 0001 – MSV5
c. 0002 – ONU200
d. 0003 – MS1/C
1.The last 7 digits of the system ID is the same as subrack ID (can be obtained by checking the
LMT / written on the subrack itself).
2.The last “01” digit in the NSAP address is the selector byte and it remains the same.
Mode : Manual
NSAP Length: 20
System ID: 6
NE: 49 00000000000000000000 xxxx 0000 0xxxxxxx Provided by the SOA
SOA: 49 00000000000000000000 0001 0101 01000045 system administrator
SOA (RES): 49 00000000000000000000 0002 0101 01064045
7. It is possible to check the communication link between the equipment and the connected SOA
server by performing an “OSIPING” of the NSAP address.
NETWORK ELEMENT INERNET ADDRESS (TCP/IP)
TCP/IP is related to the IP address and is relevant if the equipment is directly connected to the
DCN via LAN interface .
The IP address of the SOA main server (which the node is made online) and the backup server is
set on the network element.
The IP address of the network element is also assigned to node on the “Network Element TCP/IP
connection” .
The default gateway IP address is similar as the IP address of the gateway router.
It is possible to check the communication link between the network and the connected SOA server
by performing a “PING” of the IP address.
Note:
All SDH (transport) and DXC (MD202) equipments have a unique online method on SOA and
most importantly, they use a device driver (software):
Transport Equipment:
DXC:
CCU:
Each MD202 is equipped with 2 CCU’s (CCU 1-Slot 12 and CCU 2-slot 24)
The working CCU (master) will have a “Yellow” LED turned on.
Three sets of IP address are configured in each CCU as per example below:
CCU 1:
CCU 2:
The master IP address and the default gateway IP address would be the same for both CCU’s.
MD202 is made online on SOA through the master IP address only!
The default gateway IP address is the same the Gateway router IP address; where the
equipment is connected.
IP PING!
CCU 1 CCU 2
Note:
CCU:
Case 1:
Upper CCU (CCU 1) is “providing service” and lower CCU (CCU 2) is on “standby”
Physically, the working CCU would have it’s “traffic” LED (Yellow) turned on.
Master IP address of the “working” CCU (CCU 1) will be active.
Slave IP address of the “standby” CCU (CCU 2) will be active.
Case 2:
Lower CCU (CCU2) is “providing service” and upper CCU (CCU 1) is on “standby”
Physically, the working CCU would have it’s “traffic” LED (Yellow) turned on.
Master IP address of the “working” CCU (CCU 2) will be active.
Slave IP address of the “standby” CCU (CCU 1) will be active.
Note:
Switch Matrix:
Total 2 switch units are available (1 in upper shelf and 1 in lower shelf)
Any one of the switch card can be the “working” unit (either Slot 5 or Slot 17)
Physical indication:
Synch – Green if synch source is available/ Red if free- running.
Live – Green if live data if available/ No light if otherwise (No cross connection).
Master – Green if unit is working/ No light if unit is standby.
Alarm – Red if alarm present/ No light if otherwise.
Port 4
Port 1
Port 1
Worker LTU is located exactly at the back of the 2x
STM-1 electrical unit.
Protection LTU is located on slot 6 (from the right) of Port 3
the back panel.
Interface of the worker LTU is connected to the
“worker” port on the protection LTU
“Line” port on the protection LTU is terminated to
DDF.
“COM” LED will be turned off when protection group
is available.
“PROT” LED on the protection LTU will be turned on
when protection group is active.
Protection Worker
What & Why?:
13. What is the advantage of having SDSL Opt over SDSL El?
- Distance