Actions
Feature #5593
closedLet's not log at level ERROR due to Fault Reports.
Start date:
06/28/2022
Due date:
% Done:
100%
Spec Reference:
Description
For no real reason other than it is annoying me to have logging at level ERROR:
I attach two pcaps of observed Fault Reports that deny the current code.
This one:
DNM DEBUG abis_om2000.c:2796 Rx MO=CF/00/ff/00 Fault Report, MO State: STARTED DNM DEBUG abis_om2000.c:2843 Rx MO=CF/00/ff/00 Fault Report: External Condition Map Class 2 (6) DNM DEBUG abis_om2000.c:2843 Rx MO=CF/00/ff/00 Fault Report: Replacement Unit Map (15) DNM DEBUG abis_om2000.c:2843 Rx MO=CF/00/ff/00 Fault Report: Internal Fault Map Class 2A Extension (10,21) DNM ERROR abis_om2000.c:2898 Rx MO=CF/00/ff/00 Fault Report: invalid tlv element!
and this one:
Jun 20 13:36:54 huautla-bsc osmo-bsc[12475]: DNM ERROR abis_om2000.c:2888 Rx MO=TRXC/00/ff/03 Fault Report: too many tlv elements! Jun 20 13:36:54 huautla-bsc osmo-bsc[12475]: DNM DEBUG abis_om2000.c:1111 Tx MO=TRXC/00/ff/03 Fault Report ACK
I have been unable unable to find documentation on TLV element 0xd2
Files
Actions