Project

General

Profile

DUL 20 » History » Version 11

laforge, 08/09/2020 03:09 PM

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