Ipaccess-config » History » Version 3
Anonymous, 02/19/2016 10:48 PM
Add known measurement results
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 | == Setting the Unit ID == |
||
6 | |||
7 | Assuming that your BTS ip-address is 192.168.100.123: |
||
8 | |||
9 | {{{ |
||
10 | ./ipaccess-config -u 1800/0/0 192.168.100.123 |
||
11 | }}} |
||
12 | |||
13 | == Setting the Primary OML address == |
||
14 | |||
15 | Assuming that your BTS ip-address is 192.168.100.123 and your BSC ip address is 192.168.100.11: |
||
16 | |||
17 | {{{ |
||
18 | ./ipaccess-config -o 192.168.100.11 192.168.100.123 |
||
19 | }}} |
||
20 | |||
21 | == Performing a test == |
||
22 | |||
23 | You can perform various BTS tests using the -l option: |
||
24 | |||
25 | 2 | tnt | === Channel usage test === |
26 | 1 | laforge | {{{ |
27 | 2 | tnt | $ ./ipaccess-config -l 64 192.168.100.100 |
28 | 1 | laforge | ipaccess-config (C) 2009 by Harald Welte |
29 | This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY |
||
30 | |||
31 | Trying to connect to ip.access BTS ... |
||
32 | OML link established |
||
33 | [...] |
||
34 | 2 | tnt | <0020> ipaccess-config.c:107 TEST REPORT: test_no=0x40 test_res=SUCCESS |
35 | <0020> ipaccess-config.c:142 ==> ARFCN 4, RxLev 33 |
||
36 | <0020> ipaccess-config.c:142 ==> ARFCN 8, RxLev 6 |
||
37 | <0020> ipaccess-config.c:142 ==> ARFCN 5, RxLev 16 |
||
38 | <0020> ipaccess-config.c:142 ==> ARFCN 11, RxLev 5 |
||
39 | <0020> ipaccess-config.c:142 ==> ARFCN 12, RxLev 8 |
||
40 | <0020> ipaccess-config.c:142 ==> ARFCN 10, RxLev 6 |
||
41 | [...] |
||
42 | }}} |
||
43 | |||
44 | === BCCH usage test === |
||
45 | {{{ |
||
46 | $ ./ipaccess-config -l 65 192.168.100.100 |
||
47 | ipaccess-config (C) 2009 by Harald Welte |
||
48 | This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY |
||
49 | |||
50 | Trying to connect to ip.access BTS ... |
||
51 | OML link established |
||
52 | [...] |
||
53 | <0020> ipaccess-config.c:107 TEST REPORT: test_no=0x41 test_res=SUCCESS |
||
54 | <0020> ipaccess-config.c:142 ==> ARFCN 4, RxLev 32 |
||
55 | <0020> ipaccess-config.c:142 ==> ARFCN 8, RxLev 6 |
||
56 | <0020> ipaccess-config.c:142 ==> ARFCN 12, RxLev 6 |
||
57 | <0020> ipaccess-config.c:142 ==> ARFCN 20, RxLev 9 |
||
58 | <0020> ipaccess-config.c:142 ==> ARFCN 31, RxLev 6 |
||
59 | <0020> ipaccess-config.c:142 ==> ARFCN 37, RxLev 23 |
||
60 | <0020> ipaccess-config.c:142 ==> ARFCN 49, RxLev 7 |
||
61 | <0020> ipaccess-config.c:142 ==> ARFCN 53, RxLev 14 |
||
62 | <0020> ipaccess-config.c:142 ==> ARFCN 57, RxLev 19 |
||
63 | <0020> ipaccess-config.c:142 ==> ARFCN 60, RxLev 63 |
||
64 | <0020> ipaccess-config.c:142 ==> ARFCN 71, RxLev 15 |
||
65 | <0020> ipaccess-config.c:142 ==> ARFCN 90, RxLev 4 |
||
66 | }}} |
||
67 | |||
68 | === Frequency sync test === |
||
69 | {{{ |
||
70 | $ ./ipaccess-config -l 66 192.168.100.100 |
||
71 | [...] |
||
72 | 1 | laforge | <0020> abis_nm.c:1886 PEFORM TEST |
73 | <0020> abis_nm.c:805 OC=RADIO CARRIER(02) INST=(00,00,ff) Software Activated Report |
||
74 | <0020> abis_nm.c:805 OC=RADIO CARRIER(02) INST=(00,00,ff) Test Report |
||
75 | <0020> ipaccess-config.c:107 TEST REPORT: test_no=0x42 test_res=SUCCESS |
||
76 | 2 | tnt | <0020> ipaccess-config.c:130 ==> ARFCN 4, Frequency Error -2 |
77 | <0020> ipaccess-config.c:130 ==> ARFCN 8, Frequency Error -40 |
||
78 | <0020> ipaccess-config.c:130 ==> ARFCN 20, Frequency Error -21 |
||
79 | <0020> ipaccess-config.c:130 ==> ARFCN 31, Frequency Error 1 |
||
80 | <0020> ipaccess-config.c:130 ==> ARFCN 37, Frequency Error -4 |
||
81 | <0020> ipaccess-config.c:130 ==> ARFCN 45, Frequency Error -4 |
||
82 | <0020> ipaccess-config.c:130 ==> ARFCN 53, Frequency Error 22 |
||
83 | <0020> ipaccess-config.c:130 ==> ARFCN 57, Frequency Error 3 |
||
84 | <0020> ipaccess-config.c:130 ==> ARFCN 60, Frequency Error 0 |
||
85 | <0020> ipaccess-config.c:130 ==> ARFCN 69, Frequency Error 2 |
||
86 | <0020> ipaccess-config.c:130 ==> ARFCN 73, Frequency Error 30 |
||
87 | <0020> ipaccess-config.c:130 ==> ARFCN 89, Frequency Error 44 |
||
88 | <0020> ipaccess-config.c:130 ==> ARFCN 90, Frequency Error 8 |
||
89 | <0020> ipaccess-config.c:130 ==> ARFCN 123, Frequency Error 27 |
||
90 | 1 | laforge | }}} |
91 | 3 | laforge | |
92 | === Available tests === |
||
93 | 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. |
||
94 | |||
95 | || Hex value || Decimal || Description || |
||
96 | || 0x40 || 64 || CCCH Utilisation MF || |
||
97 | || 0x41 || 65 || SDCCH Usage MF || |
||
98 | || 0x42 || 66 || Measurement Processing MF || |
||
99 | || 0x43 || 67 || RTP Usage MF || |
||
100 | || 0x44 || 68 || RTP Performance MF || |
||
101 | || 0x45 || 69 || GPRS CCCH MF || |
||
102 | || 0x46 || 70 || PCCCH Utilisation MF || |
||
103 | || 0x47 || 71 || GPRS CCCH Details MF || |
||
104 | || 0x48 || 72 || Establishment MF || |
||
105 | || 0x49 || 73 || Uplink TBF MF || |
||
106 | || 0x4a || 74 || Downlink TBF MF || |
||
107 | || 0x4b || 75 || TBF Details MF || |
||
108 | || 0x4c || 76 || TBF Usage MF || |
||
109 | || 0x4d || 77 || LLC Data MF || |
||
110 | || 0x4e || 78 || PDCH Usage MF || |
||
111 | || 0x4f || 79 || Power Control MF || |
||
112 | || 0x50 || 80 || Link Adaption MF || |
||
113 | || 0x51 || 81 || TCH Usage Details MF || |
||
114 | || 0x52 || 82 || AMR MF || |
||
115 | || 0x53 || 83 || RTP Multiplex Performance MF || |
||
116 | || 0x54 || 84 || RTP Multiplex Usage MF || |
||
117 | || 0x55 || 85 || SRTP Multiplex Usage MF || |
||
118 | || 0x56 || 86 || Abis Traffic MF || |
||
119 | || 0x57 || 87 || ??? || |
||
120 | || 0x58 || 89 || GPRS Multiplex Performance MF || |
||
121 | || 0x59 || 90 || GPRS MUltiplex Usage MF || |