Actions
Bug #4642
openAttempting to set illegal id for FSM instance of type 'OM2000-MO'
Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
07/03/2020
Due date:
% Done:
0%
Spec Reference:
Description
At least with current libosocore, osmo-nitb fails to set the names of OM2000 MOs.
<0005> bts_ericsson_rbs2000.c:118 inp_sig_cb(): Input signal 'TEI-UP' received <0005> bts_ericsson_rbs2000.c:36 bootstrapping OML for BTS 0 <0005> fsm.c:461 OM2000-BTS(0)[0x556f9acf5ca0]{INIT}: Allocated <0005> abis_om2000.c:2322 OM2000-BTS(0)[0x556f9acf5ca0]{INIT}: Received Event START <0005> abis_om2000.c:2163 OM2000-BTS(0)[0x556f9acf5ca0]{INIT}: state_chg to WAIT-CF <001e> fsm.c:391 Attempting to set illegal id for FSM instance of type 'OM2000-MO': "0-CF/00/ff/00" <0005> abis_om2000.c:59 OM2000-BTS(0)[0x556f9acf5ca0]{WAIT-CF}: Received Event CF-DONE <0005> abis_om2000.c:2175 OM2000-BTS(0)[0x556f9acf5ca0]{WAIT-CF}: state_chg to WAIT-TF <001e> fsm.c:391 Attempting to set illegal id for FSM instance of type 'OM2000-MO': "0-TF/00/ff/00" <0005> abis_om2000.c:59 OM2000-BTS(0)[0x556f9acf5ca0]{WAIT-TF}: Received Event TF-DONE <0005> abis_om2000.c:2188 OM2000-BTS(0)[0x556f9acf5ca0]{WAIT-TF}: state_chg to WAIT-CON <001e> fsm.c:391 Attempting to set illegal id for FSM instance of type 'OM2000-MO': "0-CON/00/ff/00" <0005> abis_om2000.c:59 OM2000-BTS(0)[0x556f9acf5ca0]{WAIT-CON}: Received Event CON-DONE <0005> abis_om2000.c:2201 OM2000-BTS(0)[0x556f9acf5ca0]{WAIT-CON}: state_chg to WAIT-IS <001e> fsm.c:391 Attempting to set illegal id for FSM instance of type 'OM2000-MO': "0-IS/00/ff/00" <0005> abis_om2000.c:59 OM2000-BTS(0)[0x556f9acf5ca0]{WAIT-IS}: Received Event IS-DONE <0005> abis_om2000.c:2214 OM2000-BTS(0)[0x556f9acf5ca0]{WAIT-IS}: state_chg to WAIT-TRX <001e> fsm.c:391 Attempting to set illegal id for FSM instance of type 'OM2000-TRX': "0/0" <0005> abis_om2000.c:59 OM2000-BTS(0)[0x556f9acf5ca0]{WAIT-TRX}: Received Event TRX-DONE
Looking at om2k_mo_name()
in osmo-bsc, I would suggest the problem also exists in osmo-bsc.
Updated by laforge almost 4 years ago
- Assignee deleted (
laforge) - Priority changed from Normal to Low
laforge wrote:
Looking at
om2k_mo_name()
in osmo-bsc, I would suggest the problem also exists in osmo-bsc.
it doesn't exist in osmo-bsc -> not really worth investigating
Actions