Hi Harald,
I uploaded the pcap and the associated BSC log:
https://we.tl/t-bwe48b47HF
I also did some measurements for how much time does it takes for the SW to load:
1. After the NOKIA_BTS_RESET command, it takes about 60-70 sec. for
the OML to wait for LAPD.
2. After the NOKIA_BTS_START_DOWNLOAD_REQ it can take another 40-50
seconds for TRX to load the SW and be ready for RSL LAPD.
Do you happen to know what "NOKIA_BTS_MF_REQ" means? The rest of the
commands are self explanatory, but I can't figure out what this does.
A few interesting things in the log:
After the initial OML bootstrap where we only send NOKIA_BTS_RESET_REQ
and we close the LAPD after the ACK, the BSC tries to do another OML
bootstrap while the BTS is being reset and the bts_reset_timer is not
yet counted down.
If you look at the RSL LAPD activation part:
DLLAPD input/lapd.c:245 (0:2-T1-S0): LAPD Allocating SAP for SAPI=0 /
TEI=1 (dl=0x5610bcd19e00, sap=0x5610bcd19de0)
DLLAPD input/lapd.c:255 (0:2-T1-S0): k=2 N200=3 N201=260 T200=1.0 T203=10.0
DLLAPD input/lapd.c:519 (0:2-T1-S0): LAPD DL-ESTABLISH request TEI=1 SAPI=0
DLLAPD lapd_core.c:421 (0:2-T1-S0) sending MDL-ERROR-IND cause 1 from
state LAPD_STATE_IDLE
DLLAPD input/lapd.c:658 (0:2-T1-S0) LAPD DL-RELEASE indication TEI=1 SAPI=0
DLLAPD input/lapd.c:282 (0:2-T1-S0): LAPD Freeing SAP for SAPI=0 /
TEI=1 (dl=0x5610bcd19e00, sap=0x5610bcd19de0)
The above clearly happens because it is issued before the RSL link is
able to accept any LAPD connections (TRX SW is not finished loading
yet).
What is interesting is that although the "NOKIA_BTS_CONF_COMPL"
message arrives way late (the RSL LAPD timed out a long time ago), but
it does arrive after the TRX SW is loaded correctly. Maybe this would
be a good trigger to wait for before the RSL bootstrap begins? Either
this or a similar timer for the RSL as we have for the OML.
Regards,
Csaba