Actions
Bug #6019
open"PCU version PCU socket has LOST connection connected"
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
04/28/2023
Due date:
% Done:
0%
Spec Reference:
Description
This is what I see in the output of show bts command:
OsmoBSC> show bts 0 BTS 0 is of osmo-bts type in band GSM900, has CI 0 LAC 1, BSIC 63 (NCC=7, BCC=7) and 1 TRX Description: (null) ARFCNs: 85 PCU version PCU socket has LOST connection connected ...
what means that somehow bts->pcu_version[] contains PCU socket has LOST connection. I am also seeing this in logging:
апр 28 19:14:07 DELL osmo-bsc[543401]: DNM NOTICE abis_nm.c:348 OC=BTS(01) INST=(00,ff,ff): Reported connected PCU version 1.2.0.31-33a1bf3 ... апр 28 19:14:10 DELL osmo-bsc[543401]: DNM NOTICE abis_nm.c:348 OC=BTS(01) INST=(00,ff,ff): Reported connected PCU version PCU socket has LOST connection
This looks a bit confusing, maybe we should just say "PCU state"?
Updated by fixeria about 1 month ago
The following code snippet from osmo-bsc suggests that the OML report body is expected to be empty on disconnection:
static inline void handle_manufact_report(struct gsm_bts *bts, const uint8_t *p_val, const char *type,
const char *severity, const char *text)
{
enum abis_mm_event_causes cause = osmo_load16be(p_val + 1);
switch (cause) {
case OSMO_EVT_PCU_VERS:
if (text) {
LOGPMO(&bts->mo, DNM, LOGL_NOTICE, "Reported connected PCU version %s\n", text);
osmo_strlcpy(bts->pcu_version, text, sizeof(bts->pcu_version));
} else {
LOGPMO(&bts->mo, DNM, LOGL_ERROR, "Reported PCU disconnection.\n");
bts->pcu_version[0] = '\0';
}
break;
default:
log_oml_fail_rep(bts, type, severity, p_val, text);
};
}
Actions
