Can you post your firmware versions? I've recently been exploring anomalous behavior which seems to follow firmware version differences; these odd behaviors seem to have the greatest affects on the 139/140 type units used in GPRS-enabled configurations.
Inclusive of the issues I've seen are a few 140-model units which simply do not respond to any GPRS-related configurations with a connection to the SGSN. My suspicion lies strongly in the firmware either not supporting GPRS or there being a different mechanism to invoke it. While it may be beyond the scope of the list to discuss issues relating to vendor firmware, I am eager to solicit an off-list discussion with anyone with more "experience" with firmware issues. The ideal end result would ideally be two-fold: 1) To discover how firmware version affects interoperability with openbsc 2) Ultimately help more people get their setups working on the variety of hardware floating out and about -MM On Fri, Sep 30, 2011 at 10:56 AM, Gus Bourg <[email protected]> wrote: > Hello all, > > Looking for ideas. I have a NanoBTS Model 140 which doesn't seem to > work with GPRS. It never connects to the SGSN. The openbsc/sgsn > environment is ok - I can swap in another nano and it works fine. > I've taken some log captures: > > From the nano on startup: > http://pastebin.com/qLatWdtB > > OpenBSC Startup: > http://pastebin.com/bXEhizAG > > moi::states: > http://pastebin.com/9MiRRGP0 > > In the nano startup - the two things that stand out are the complains > about flag 3 and the NSE: > > 27855:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: BTS:0 flag 3 not > setting or set! > 27855:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: GPRS NSE:0 flag > 3 not setting or set! > > 42142:DBG:GBHSS_STACK:bgp_error_reporter() : PROTO_ERR: > Msg=GPRS_BGP_RL_UL_UNITDATA_REQ, Err=GPRS_NSEI_NOT_OPERATIONAL > 42142:DBG:GBHSS_STACK:bgp_process_msg failed : > msg=GPRS_BGP_NM_BVC_RESET_REQ err=GPRS_NSEI_NOT_OPERATIONAL > > Any thoughts or additional data points I should collect? > > Thanks, > Gus > >
