Ipaccess-config » History » Revision 4
Revision 3 (Anonymous, 02/19/2016 10:48 PM) → Revision 4/6 (Anonymous, 02/19/2016 10:48 PM)
ipaccess-config is a small command line tool to configure an ip.access nanoBTS.
You can use this tool to perform basic operations such as setting NVRAM parameters or performing tests
== Setting the Unit ID ==
Assuming that your BTS ip-address is 192.168.100.123:
{{{
./ipaccess-config -u 1800/0/0 192.168.100.123
}}}
== Setting the Primary OML address ==
Assuming that your BTS ip-address is 192.168.100.123 and your BSC ip address is 192.168.100.11:
{{{
./ipaccess-config -o 192.168.100.11 192.168.100.123
}}}
== Performing a test ==
You can perform various BTS tests using the -l option:
=== Channel usage test ===
{{{
$ ./ipaccess-config -l 64 192.168.100.100
ipaccess-config (C) 2009 by Harald Welte
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY
Trying to connect to ip.access BTS ...
OML link established
[...]
<0020> ipaccess-config.c:107 TEST REPORT: test_no=0x40 test_res=SUCCESS
<0020> ipaccess-config.c:142 ==> ARFCN 4, RxLev 33
<0020> ipaccess-config.c:142 ==> ARFCN 8, RxLev 6
<0020> ipaccess-config.c:142 ==> ARFCN 5, RxLev 16
<0020> ipaccess-config.c:142 ==> ARFCN 11, RxLev 5
<0020> ipaccess-config.c:142 ==> ARFCN 12, RxLev 8
<0020> ipaccess-config.c:142 ==> ARFCN 10, RxLev 6
[...]
}}}
=== BCCH usage test ===
{{{
$ ./ipaccess-config -l 65 192.168.100.100
ipaccess-config (C) 2009 by Harald Welte
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY
Trying to connect to ip.access BTS ...
OML link established
[...]
<0020> ipaccess-config.c:107 TEST REPORT: test_no=0x41 test_res=SUCCESS
<0020> ipaccess-config.c:142 ==> ARFCN 4, RxLev 32
<0020> ipaccess-config.c:142 ==> ARFCN 8, RxLev 6
<0020> ipaccess-config.c:142 ==> ARFCN 12, RxLev 6
<0020> ipaccess-config.c:142 ==> ARFCN 20, RxLev 9
<0020> ipaccess-config.c:142 ==> ARFCN 31, RxLev 6
<0020> ipaccess-config.c:142 ==> ARFCN 37, RxLev 23
<0020> ipaccess-config.c:142 ==> ARFCN 49, RxLev 7
<0020> ipaccess-config.c:142 ==> ARFCN 53, RxLev 14
<0020> ipaccess-config.c:142 ==> ARFCN 57, RxLev 19
<0020> ipaccess-config.c:142 ==> ARFCN 60, RxLev 63
<0020> ipaccess-config.c:142 ==> ARFCN 71, RxLev 15
<0020> ipaccess-config.c:142 ==> ARFCN 90, RxLev 4
}}}
=== Frequency sync test ===
{{{
$ ./ipaccess-config -l 66 192.168.100.100
[...]
<0020> abis_nm.c:1886 PEFORM TEST
<0020> abis_nm.c:805 OC=RADIO CARRIER(02) INST=(00,00,ff) Software Activated Report
<0020> abis_nm.c:805 OC=RADIO CARRIER(02) INST=(00,00,ff) Test Report
<0020> ipaccess-config.c:107 TEST REPORT: test_no=0x42 test_res=SUCCESS
<0020> ipaccess-config.c:130 ==> ARFCN 4, Frequency Error -2
<0020> ipaccess-config.c:130 ==> ARFCN 8, Frequency Error -40
<0020> ipaccess-config.c:130 ==> ARFCN 20, Frequency Error -21
<0020> ipaccess-config.c:130 ==> ARFCN 31, Frequency Error 1
<0020> ipaccess-config.c:130 ==> ARFCN 37, Frequency Error -4
<0020> ipaccess-config.c:130 ==> ARFCN 45, Frequency Error -4
<0020> ipaccess-config.c:130 ==> ARFCN 53, Frequency Error 22
<0020> ipaccess-config.c:130 ==> ARFCN 57, Frequency Error 3
<0020> ipaccess-config.c:130 ==> ARFCN 60, Frequency Error 0
<0020> ipaccess-config.c:130 ==> ARFCN 69, Frequency Error 2
<0020> ipaccess-config.c:130 ==> ARFCN 73, Frequency Error 30
<0020> ipaccess-config.c:130 ==> ARFCN 89, Frequency Error 44
<0020> ipaccess-config.c:130 ==> ARFCN 90, Frequency Error 8
<0020> ipaccess-config.c:130 ==> ARFCN 123, Frequency Error 27
}}}
=== Available tests ===
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.
|| Hex value || Decimal || Description ||
|| 0x40 || 64 || CCCH Utilisation MF ||
|| 0x41 || 65 || SDCCH Usage MF ||
|| 0x42 || 66 || Measurement Processing MF ||
|| 0x43 || 67 || RTP Usage MF ||
|| 0x44 || 68 || RTP Performance MF ||
|| 0x45 || 69 || GPRS CCCH MF ||
|| 0x46 || 70 || PCCCH Utilisation MF ||
|| 0x47 || 71 || GPRS CCCH Details MF ||
|| 0x48 || 72 || Establishment MF ||
|| 0x49 || 73 || Uplink TBF MF ||
|| 0x4a || 74 || Downlink TBF MF ||
|| 0x4b || 75 || TBF Details MF ||
|| 0x4c || 76 || TBF Usage MF ||
|| 0x4d || 77 || LLC Data MF ||
|| 0x4e || 78 || PDCH Usage MF ||
|| 0x4f || 79 || Power Control MF ||
|| 0x50 || 80 || Link Adaption MF ||
|| 0x51 || 81 || TCH Usage Details MF ||
|| 0x52 || 82 || AMR MF ||
|| 0x53 || 83 || RTP Multiplex Performance MF ||
|| 0x54 || 84 || RTP Multiplex Usage MF ||
|| 0x55 || 85 || SRTP Multiplex Usage MF ||
|| 0x56 || 86 || Abis Traffic MF ||
|| 0x57 || 87 || ??? ||
|| 0x58 || 89 || GPRS Multiplex Performance MF ||
|| 0x59 || 90 || GPRS MUltiplex Usage MF ||
== Firmware Analysis ==
{{{
./ipaccess-config -f firmware-file
}}}
The above command will parse the given firmware file and report on the content. It will print version numbers, length and subparts.
== Software Load ==
{{{
./ipaccess-config -d firmware-file -r 192.168.100.23
}}}
The above command will attempt to load the new firmware, set it as default and reboot the BTS.