Digital Data

Network
DDN
 Case 2:

MSV5 ONU200 RNU-8C

 In this case, the NT is connected to SUVAR2 card of the ONU200

 Cross connection from the SUVAR2 to the CMM can be :
1.Direct VC12 cross connection from the SUVAR2 to the CMM (CC channel on TS16 will
be transparently transported on the 2 Mb/s line)
2. 64 Kb/s channel of the SUVAR2 cross connected to the CCU. VC12 of the CCU is then cross
connected to the CMM (Remember to cross connect the TS 16 – cc channel !)

 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.
 RNU-8C NT
DDF
1

2 Mb/s
Connection V.35 Interface
(COAXIAL)

DTE I/F –V.35

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

 No of VC12 channel allocation in the CCU:

 CCU 8 – 8 VC12
 CCU 16 – 16 VC12

 Each VC12 channel is sub structured to 31 x 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

 VC12 bandwidth available on the line card:

 CMM – 63 VC12
 CMM
 Similar cross 16E1 – 16 VC12
connection concept applies to other N x 64 Kb/s services (SDSL, SUVAR2, etc)
STRUCTURED 2 Mb/s SIGNAL ON MSV5
DDF

STM-1
VC4

PORT 1 VC12_1 X VC12_1

64K_1

64K_2
X 64K_1

64K_2 VC12 Cross

VC12_2

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_1 64K_1 VC12_7

64K_2 64K_2
VC12_8
64K_3 64K_3

64K_4 64K_4 VC12_63

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:

1.QD2 (TSAP ID)

2.Q3P (LAYER 3 ADDRESS)

3.TCP/IP (NETWORK ELEMENT INTERNET ADDRESS)

 TSAP ID (QD2)

It is divided into 3:

a. SISA Node No:

b. NE Access No:

b. NE Access No (Red SOA):

“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).

For example, 3 nodes having distinctive SISA

1 NE Access No

node number 1, 2 and 3; they share the same NE

Access Number “1” ; will appear as in the figure
(SOA- QD2 Address List). 1 2 3
SISA Node No
 LAYER 3 ADDRESS (Q3P)

Layer 3 address corresponds to NSAP address of the node and SOA (also known as OSI addressing)

Example of NSAP ADDRESS:

4900000000000000000000 0000 0000 0XXXXXXX 01

1. Default Address 3. System ID

2. Area Address

1.The default address is the same for all nodes and also for SOA. (49 and ten pair of zeros).

1.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”.

2.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).

1.The last “01” digit in the NSAP address is the selector byte and it remains the same.

2.Setting done through LMT is as below (example – MS1/4) :

 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:

1.SMA 16 (Series 3) - Device driver restart takes 20 minutes

2.MSH 64 - Device driver restart takes 15 minutes

 DXC:

1.MD202 (Version 4.2.9) - Device driver restart takes 2 hours

 MD202
IN
DDN/ MLCN NETWORK
 Module Interface Remark
CCU Controller Main controller, communication unit
CORE SWITCH MATRIX Switch Switch matrix, synchronization and ITE function
TRANSCIVER Communication External device to have UTP connection to the DCN
2 x STM-1 EL IF STM-1 Electrical interface (2 ports)
MAIN I/F
2 x STM-1 OPT IF STM-1 Electrical interface (2 ports)
UNIT
CP Common Part Channelisation card (STM-1 ----> VC12 -----> 64Kbps)
TRIB I/F UNIT E1 2 Mb/s Total of 63 ports per card
UPPER SHELF CCU 1 PROTECTION LTU

LOWER SHELF CCU 2

 Note:

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:

1. Master IP address: 10.101.16.73

2. Slave IP address: 10.101.16.74
3. Default Gateway IP address: 10.101.16.7

CCU 2:

1. Master IP address: 10.101.16.73

2. Slave IP address: 10.101.16.75
3. Default Gateway IP address: 10.101.16.7

 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!

Master IP: 10.101.16.73 Master IP: 10.101.16.73

1 1 - When CCU 1 is “working” and CCU 2 is “standby”

2 - When CCU 2 is “working” and CCU 1 is “standby”

Slave IP: 10.101.16.74 Slave IP: 10.101.16.75

CCU 1 CCU 2
 Note:

CCU:

Only 2 IP address’s work at one time in the MD202.

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.

2 x STM-1 Electrical and Common part (CP) Unit:

 Each STM-1 card is equipped with 2 STM-1 ports and works together with the CP card.
 2 x STM-1 and Common part works together and side by side
 A total of 4 of this unit can be equipped on the upper shelf.
 A total of 4 of this unit can be equipped on the lower shelf.
 All 4 units can be protected by a single 2xSTM-1 and CP card on slot 6 and slot 7 (1:4
protection).
 Physical indication on CP card:
 Live – Green if live data is available/ No light if otherwise
 Prot – Green if protection group is available/ Red if protection is active
 Alarm – Red if alarm in the data stream/ No light if otherwise.
 P1 P2
Tx Rx Tx Rx Port 2 Port 2

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?:

1.What’s main the difference between MS1/4 and MSV5?

- MS1/4 can support 4 STM-4 cards/ MSV5 2 STM-4 cards
- MS1/4 can drop to 2Mb/s only/ MSV5 can drop to 64Kb/s

2. What’s the difference between AM-2 and TU-2M?

- AM-2 has 21 ports/ TU-2M has 20 ports
- AM-2 is for unstructured 2Mb/s while TU-2M is for structured/unstructured 2Mb/s

3. Why do we need V5CM card on MSV5?

- Create NU-link (for RNU-8C and Onu200 with CMM-16E1)

4. What is the purpose of having AM-64K?

- Channelise the 2Mb/s signal from the TU-2M interface into 64Kb/s signal

5. Why do we need SW4M-24 and SWM64K?

- SW4M-24 is for CC of VC12, VC3 and VC4 level
- SWM64K is for CC of 64Kb/s level

6. What is the purpose of ECC?

- It’s a communication channel that can travel through a 2Mb/s signal.
 What & Why?:

7. Why not traffic interruption when PRM-M is pulled out?

- Traffic is through the Switch card and not the PRM-M

8. What is the available protection group in MSV5 and MS1/4?

- Protection for SW4M-24 is automatically enabled.
- Protection for SWM64K and V5CM works in pair and must be created in the epg.

9. What is the purpose of having NT?

- Convert customer equipment’s interface (V.35) to data.

10. Why do we need so many types of NT’s in ONU200?

1. RNU8C – Coaxial input, max 1984Kbps, V.35 output
2. Mat6d – 2 wire copper, max 128Kbps, V.35 output
3. HDSL – 4 Wire copper, max 2Mb/s or 1984 Kb/s, V.35 output
4. SDSL EL – 2 Wire copper, max 2 Mb/s or 1984 Kb/s, V.35 output
5. SDSL Opt – Fiber (1 core) , output 2Mb/s signal.

11. What is the purpose of CMM-16E1?

- Eliminate the use of MS1/C and ECC connections.

12. Why HDSL is replaced by SDSL?

- 4 wire copper to 2 wire copper with the same output.

13. What is the advantage of having SDSL Opt over SDSL El?
- Distance