Project

General

Profile

Actions

Bug #4861

closed

frame_relay: logging needs context

Added by laforge over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
libosmogb
Target version:
-
Start date:
11/14/2020
Due date:
% Done:

100%

Spec Reference:

Description

When running a Gb interface based on the frame_relay.c code, I get log messages like

<0024> frame_relay.c:729 DLCI 18 is not active (yet), discarding
<0024> frame_relay.c:729 DLCI 19 is not active (yet), discarding
<0024> frame_relay.c:729 DLCI 16 is not active (yet), discarding
<0024> frame_relay.c:729 DLCI 17 is not active (yet), discarding

Those are only useful if the DLCI is globally unique - for which there is no requirment. Every frame relay bearer (E1 line) could very well use the same DLCI numbers, and at which point it would be impossible to distinguish them in the logs.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)