Ipaccess-config » History » Version 5
Anonymous, 02/19/2016 10:48 PM
Document firmware related bits.
1 | 1 | laforge | ipaccess-config is a small command line tool to configure an ip.access nanoBTS. |
---|---|---|---|
2 | |||
3 | You can use this tool to perform basic operations such as setting NVRAM parameters or performing tests |
||
4 | |||
5 | |||
6 | 5 | laforge | h2. Setting the Unit ID |
7 | |||
8 | |||
9 | 1 | laforge | Assuming that your BTS ip-address is 192.168.100.123: |
10 | |||
11 | 5 | laforge | <pre> |
12 | 1 | laforge | ./ipaccess-config -u 1800/0/0 192.168.100.123 |
13 | 5 | laforge | </pre> |
14 | 1 | laforge | |
15 | |||
16 | 5 | laforge | h2. Setting the Primary OML address |
17 | |||
18 | |||
19 | 1 | laforge | Assuming that your BTS ip-address is 192.168.100.123 and your BSC ip address is 192.168.100.11: |
20 | |||
21 | 5 | laforge | <pre> |
22 | 1 | laforge | ./ipaccess-config -o 192.168.100.11 192.168.100.123 |
23 | 5 | laforge | </pre> |
24 | 1 | laforge | |
25 | |||
26 | 5 | laforge | h2. Performing a test |
27 | |||
28 | |||
29 | 1 | laforge | You can perform various BTS tests using the -l option: |
30 | |||
31 | 5 | laforge | |
32 | h3. Channel usage test |
||
33 | |||
34 | <pre> |
||
35 | 1 | laforge | $ ./ipaccess-config -l 64 192.168.100.100 |
36 | ipaccess-config (C) 2009 by Harald Welte |
||
37 | This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY |
||
38 | |||
39 | Trying to connect to ip.access BTS ... |
||
40 | OML link established |
||
41 | [...] |
||
42 | <0020> ipaccess-config.c:107 TEST REPORT: test_no=0x40 test_res=SUCCESS |
||
43 | 5 | laforge | <0020> ipaccess-config.c:142 ==> ARFCN 4, [[RxLev]] 33 |
44 | <0020> ipaccess-config.c:142 ==> ARFCN 8, [[RxLev]] 6 |
||
45 | <0020> ipaccess-config.c:142 ==> ARFCN 5, [[RxLev]] 16 |
||
46 | <0020> ipaccess-config.c:142 ==> ARFCN 11, [[RxLev]] 5 |
||
47 | <0020> ipaccess-config.c:142 ==> ARFCN 12, [[RxLev]] 8 |
||
48 | <0020> ipaccess-config.c:142 ==> ARFCN 10, [[RxLev]] 6 |
||
49 | 2 | tnt | [...] |
50 | 5 | laforge | </pre> |
51 | 2 | tnt | |
52 | 5 | laforge | |
53 | h3. BCCH usage test |
||
54 | |||
55 | <pre> |
||
56 | 2 | tnt | $ ./ipaccess-config -l 65 192.168.100.100 |
57 | ipaccess-config (C) 2009 by Harald Welte |
||
58 | This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY |
||
59 | |||
60 | Trying to connect to ip.access BTS ... |
||
61 | OML link established |
||
62 | [...] |
||
63 | <0020> ipaccess-config.c:107 TEST REPORT: test_no=0x41 test_res=SUCCESS |
||
64 | 5 | laforge | <0020> ipaccess-config.c:142 ==> ARFCN 4, [[RxLev]] 32 |
65 | <0020> ipaccess-config.c:142 ==> ARFCN 8, [[RxLev]] 6 |
||
66 | <0020> ipaccess-config.c:142 ==> ARFCN 12, [[RxLev]] 6 |
||
67 | <0020> ipaccess-config.c:142 ==> ARFCN 20, [[RxLev]] 9 |
||
68 | <0020> ipaccess-config.c:142 ==> ARFCN 31, [[RxLev]] 6 |
||
69 | <0020> ipaccess-config.c:142 ==> ARFCN 37, [[RxLev]] 23 |
||
70 | <0020> ipaccess-config.c:142 ==> ARFCN 49, [[RxLev]] 7 |
||
71 | <0020> ipaccess-config.c:142 ==> ARFCN 53, [[RxLev]] 14 |
||
72 | <0020> ipaccess-config.c:142 ==> ARFCN 57, [[RxLev]] 19 |
||
73 | <0020> ipaccess-config.c:142 ==> ARFCN 60, [[RxLev]] 63 |
||
74 | <0020> ipaccess-config.c:142 ==> ARFCN 71, [[RxLev]] 15 |
||
75 | <0020> ipaccess-config.c:142 ==> ARFCN 90, [[RxLev]] 4 |
||
76 | </pre> |
||
77 | 2 | tnt | |
78 | 5 | laforge | |
79 | h3. Frequency sync test |
||
80 | |||
81 | <pre> |
||
82 | 1 | laforge | $ ./ipaccess-config -l 66 192.168.100.100 |
83 | [...] |
||
84 | <0020> abis_nm.c:1886 PEFORM TEST |
||
85 | <0020> abis_nm.c:805 OC=RADIO CARRIER(02) INST=(00,00,ff) Software Activated Report |
||
86 | 2 | tnt | <0020> abis_nm.c:805 OC=RADIO CARRIER(02) INST=(00,00,ff) Test Report |
87 | <0020> ipaccess-config.c:107 TEST REPORT: test_no=0x42 test_res=SUCCESS |
||
88 | <0020> ipaccess-config.c:130 ==> ARFCN 4, Frequency Error -2 |
||
89 | <0020> ipaccess-config.c:130 ==> ARFCN 8, Frequency Error -40 |
||
90 | <0020> ipaccess-config.c:130 ==> ARFCN 20, Frequency Error -21 |
||
91 | <0020> ipaccess-config.c:130 ==> ARFCN 31, Frequency Error 1 |
||
92 | <0020> ipaccess-config.c:130 ==> ARFCN 37, Frequency Error -4 |
||
93 | <0020> ipaccess-config.c:130 ==> ARFCN 45, Frequency Error -4 |
||
94 | <0020> ipaccess-config.c:130 ==> ARFCN 53, Frequency Error 22 |
||
95 | 3 | laforge | <0020> ipaccess-config.c:130 ==> ARFCN 57, Frequency Error 3 |
96 | <0020> ipaccess-config.c:130 ==> ARFCN 60, Frequency Error 0 |
||
97 | <0020> ipaccess-config.c:130 ==> ARFCN 69, Frequency Error 2 |
||
98 | <0020> ipaccess-config.c:130 ==> ARFCN 73, Frequency Error 30 |
||
99 | <0020> ipaccess-config.c:130 ==> ARFCN 89, Frequency Error 44 |
||
100 | <0020> ipaccess-config.c:130 ==> ARFCN 90, Frequency Error 8 |
||
101 | 1 | laforge | <0020> ipaccess-config.c:130 ==> ARFCN 123, Frequency Error 27 |
102 | 5 | laforge | </pre> |
103 | 1 | laforge | |
104 | 5 | laforge | |
105 | h3. Available tests |
||
106 | |||
107 | 3 | laforge | This was extracted from the packet-gsm1221.c file of the ipaccess wireshark sources. A more detailed description of these tests is not available and some of them seem to send the BTS into the nirvana as well. |
108 | 1 | laforge | |
109 | || Hex value || Decimal || Description || |
||
110 | || 0x40 || 64 || CCCH Utilisation MF || |
||
111 | || 0x41 || 65 || SDCCH Usage MF || |
||
112 | || 0x42 || 66 || Measurement Processing MF || |
||
113 | 3 | laforge | || 0x43 || 67 || RTP Usage MF || |
114 | || 0x44 || 68 || RTP Performance MF || |
||
115 | || 0x45 || 69 || GPRS CCCH MF || |
||
116 | || 0x46 || 70 || PCCCH Utilisation MF || |
||
117 | || 0x47 || 71 || GPRS CCCH Details MF || |
||
118 | || 0x48 || 72 || Establishment MF || |
||
119 | || 0x49 || 73 || Uplink TBF MF || |
||
120 | || 0x4a || 74 || Downlink TBF MF || |
||
121 | || 0x4b || 75 || TBF Details MF || |
||
122 | || 0x4c || 76 || TBF Usage MF || |
||
123 | || 0x4d || 77 || LLC Data MF || |
||
124 | || 0x4e || 78 || PDCH Usage MF || |
||
125 | || 0x4f || 79 || Power Control MF || |
||
126 | || 0x50 || 80 || Link Adaption MF || |
||
127 | || 0x51 || 81 || TCH Usage Details MF || |
||
128 | || 0x52 || 82 || AMR MF || |
||
129 | || 0x53 || 83 || RTP Multiplex Performance MF || |
||
130 | || 0x54 || 84 || RTP Multiplex Usage MF || |
||
131 | || 0x55 || 85 || SRTP Multiplex Usage MF || |
||
132 | || 0x56 || 86 || Abis Traffic MF || |
||
133 | || 0x57 || 87 || ??? || |
||
134 | || 0x58 || 89 || GPRS Multiplex Performance MF || |
||
135 | || 0x59 || 90 || GPRS MUltiplex Usage MF || |
||
136 | 4 | laforge | |
137 | |||
138 | 5 | laforge | h2. Firmware Analysis |
139 | |||
140 | |||
141 | <pre> |
||
142 | 4 | laforge | ./ipaccess-config -f firmware-file |
143 | 5 | laforge | </pre> |
144 | 4 | laforge | |
145 | The above command will parse the given firmware file and report on the content. It will print version numbers, length and subparts. |
||
146 | |||
147 | |||
148 | 5 | laforge | h2. Software Load |
149 | |||
150 | |||
151 | <pre> |
||
152 | 1 | laforge | ./ipaccess-config -d firmware-file -r 192.168.100.23 |
153 | 5 | laforge | </pre> |
154 | 1 | laforge | |
155 | The above command will attempt to load the new firmware, set it as default and reboot the BTS. |