Project

General

Profile

DUL 20 » History » Version 12

laforge, 11/03/2020 03:24 PM
add toc

1 12 laforge
{{>toc}}
2
3 1 laforge
h1. DUL 20
4
5 5 roh
DUL is a Digital Unit for LTE.  It contains the eNodeB function down to the baseband processing.
6 1 laforge
7
{{thumbnail(DUL20_01_front_complete.jpg, size=900)}}
8
9 7 roh
{{>toc}}
10
11 1 laforge
h2. Connectors
12
13
h3. PWR
14 7 roh
15 1 laforge
48V DC connector.  The negative rail is towards the edge of the unit.  Also seems to power up fine at 36V
16
17 9 laforge
The connectory type is https://www.te.com/usa-en/product-1982299-3.html with associated crimp contacts.
18
19 8 roh
{{thumbnail(DUL20_01_DC_in_detail.jpg, size=400)}}
20
21 1 laforge
h3. GPS (RJ45)
22
23
Connection for an Ericsson GPS module, contains 1PPS and UART signals
24
25 8 roh
{{thumbnail(DUL20_01_LMTA_GPS_detail.jpg, size=400)}}
26
27 1 laforge
h3. EC (RJ45)
28
29
Environment Control? Probably some RS-485 to control fans, power management, UPS, ...
30
31
h3. AUX (RJ45)
32
33
?
34
35
h3. LMT A (RJ45)
36
37
A RS-232 on RJ45 for Local Maintenane use.  IT provides access to COLI (COmmand LIne).
38
39 10 laforge
The pinout is shown below.  Please note it is *different from RBS3000!*, but identical to that of the [[DUG 20]]
40 1 laforge
41
|_.RJ45|_.DB9|_.Name|
42 3 laforge
|1|5|GND|
43
|2|3|TXD (of PC)|
44 1 laforge
|3|2|RXD (of PC)|
45
46 10 laforge
The [default?] baud rate settings are 9600 8N1.
47
48
This port provides RS-232 access to the [[OSE]] shell
49 1 laforge
50
h3. LMT B (RJ45)
51
52
_Site LAN_ Ethernet, for adminstrative purpose
53
54 11 laforge
This is the interface used for configuration of the DUL during installation.
55
56 8 roh
{{thumbnail(DUL20_01_LED_TNA_LMTB_detail.jpg, size=400)}}
57
58 1 laforge
h3. TN A (RJ45)
59
60
_Transmission_ Ethernet, i.e. the back-haul interface for S1. RJ-45
61
62
h3. TN B (SFP)
63
64
_Transmission_ Ethernet for optical back-haul. Can use normal SFP modules.
65
66 8 roh
{{thumbnail(DUL20_01_TNB_IDL_detail.jpg, size=400)}}
67
68 1 laforge
h3. IDL (HSIO)
69
70
Inter-DU-Link for cross-connecting multiple DU.
71
72 4 tnt
h3. RI A..F (SFP)
73 1 laforge
74
Radio Interface (CPRI) using either SFP transceivers for RRU connection or copper interconnect cables for RU.
75 8 roh
76
{{thumbnail(DUL20_01_SFP_detail.jpg, size=400)}}
77
78
h2. Overview Pictures
79
80
{{thumbnail(DUL20_01_front_perspective.jpg, size=400)}}
81
{{thumbnail(DUL20_01_left_perspective.jpg, size=400)}}
82
{{thumbnail(DUL20_01_right_perspective.jpg, size=400)}}
83
{{thumbnail(DUL20_01_back_perspective.jpg, size=400)}}
84
{{thumbnail(DUL20_01_bottom_complete.jpg, size=400)}}
85 1 laforge
86 2 laforge
h2. Accessing it
87
88
h3. SSH via LMT-B
89
90
It appears the DUL will always respond to 169.254.1.10/16, no matter what kind of real/other IP address has been set.
91
92
You have to use the following SSH config to speak the ancient cipher/key-exchange:
93
<pre>
94
Host dul
95
        HostName 169.254.1.10
96
        KexAlgorithms diffie-hellman-group1-sha1
97
        Ciphers 3des-cbc
98
</pre>
99
100
and then log in as the 'rbs' user with 'rbs' password.
Add picture from clipboard (Maximum size: 48.8 MB)