Análisis e interpretación de resultados

This describes common call logs and their meanings.

Table 7-13 lists the common call logs and their meanings.

Table 7-13 Call logs and meanings

Log Meaning

Err: Message pointer is NULL!, MsgType: ADD_REQ

The ADD_REQ message received from the CMU is a null pointer.

Err: No IP resource!, MsgType:

ADD_REQ

The VPU has no IP resource when receiving the ADD_REQ message from the CMU.

Err: VPU GE fault!, MsgType:

ADD_REQ

The GE channel of the VPU is faulty when receiving the ADD_REQ message from the CMU.

Err: Alloc TID failed!, MsgType:

ADD_REQ

Allocating TID termination resources fails when the ADD_REQ message from the CMU is received.

Err: Analyze TLV message failed!, MsgType: ADD_REQ

Analyzing the TLV fails when the ADD_REQ message from the CMU is received.

Err: Codec and Payload change failed!, MsgType: ADD_REQ

Checking codec and payload fails when the ADD_REQ message from the CMU is received.

Err: Service switch failed!, MsgType:

ADD_REQ

Service switchover fails when the ADD_REQ message from the CMU is received.

Err: Alloc memory failed!, MsgType:

ADD_REQ

Applying for memory fails during message reply, after the ADD_REQ message from the CMU is received.

Err: Send message failed!, MsgType:

ADD_REQ

Sending the reply message fails after the ADD_REQ message from the CMU is received.

Err: Message pointer is NULL!, MsgType: MODIFY_REQ

The MODIFY_REQ message received from the CMU is a null pointer.

Err: Check msg header failed!, MsgType:

MODIFY_REQ

Resolving the message header fails when the MODIFY_REQ message from the CMU is received.

Err: TID status is error!, MsgType:

MODIFY_REQ

The TID status is incorrect when the MODIFY_REQ message from the CMU is received.

Err: Analyze TLV message failed!, MsgType: MODIFY_REQ

Analyzing the TLV fails when the

MODIFY_REQ message from the CMU is received.

Log Meaning Err: Codec and Payload change failed!,

MsgType: MODIFY_REQ

Checking codec and payload fails when the MODIFY_REQ message from the CMU is received.

Err: service switch failed, MsgType:

MODIFY_REQ

Service switchover fails when the

MODIFY_REQ message from the CMU is received.

Err: TID status is error, MsgType:

MODIFY_REQ

The TID status is incorrect when the MODIFY_REQ message from the CMU is received.

Err: Alloc memory failed!, MsgType:

MODIFY_REQ

Applying for memory fails during message reply, after the MODIFY_REQ message from the CMU is received.

Err: Send message failed!, MsgType:

MODIFY_REQ

Sending the reply message fails after the MODIFY_REQ message from the CMU is received.

Err: Message pointer is NULL!, MsgType: CHANGE_TOPO_REQ

The CHANGE_TOPO_REQ message received from the CMU is a null pointer.

Err: Check msg header failed!, MsgType:

CHANGE_TOPO_REQ

Resolving the message header fails when the CHANGE_TOPO_REQ message from the CMU is received.

Err: TID status is error!, MsgType:

CHANGE_TOPO_REQ

The TID status is incorrect when the

CHANGE_TOPO_REQ message from the CMU is received.

Err: length of TOPO_INFO msg is error!, MsgType: CHANGE_TOPO_REQ

The length of the TOPO_INFO message received from the CMU is incorrect.

Err: Get FlowId Error, MsgType:

CHANGE_TOPO_REQ

The obtained FLOWID is incorrect when the CHANGE_TOPO_REQ message from the CMU is received.

Err: Mux Tid info error!, MsgType:

CHANGE_TOPO_REQ

The MUX termination information contained (mainly used on the VGU) is incorrect when the CHANGE_TOPO_REQ message from the CMU is received.

Err: Topo modify failed!, MsgType:

CHANGE_TOPO_REQ

Modifying TOPO fails when the

CHANGE_TOPO_REQ message from the CMU is received.

Err: Alloc memory failed!, MsgType:

CHANGE_TOPO_REQ

Applying for memory fails during message reply, after the CHANGE_TOPO_REQ message from the CMU is received.

Err: Send message failed!, MsgType:

CHANGE_TOPO_REQ

Sending the reply message fails after the CHANGE_TOPO_REQ message from the CMU is received.

Log Meaning Calllog: 9 1C1984 Pid69 Cmd180

C432008 T590 E36 cal_intr9966

The timeslot allocation request at the user termination fails because the context in the command does not comply with related rules.

Calllog: 9 1C2125 Pid69

CallRspPv8NetRefreshReqProc: Pv8Fn 35 FrmMode 1

The frame in which PV8 35 is installed is not the main frame, and thus update of PV8 network connection fails.

Calllog: 9 1C2125 Pid69

CallRspPv8NetRefreshReqProc: Pv8Fn:

4 pstPv8FrmInfo is NULL

Internal error occurs to processing of the frame in which PV8 4 is installed, and thus services of this frame are affected.

Calllog: 9 1C2125 Pid69

CallRspPv8NetRefreshReqProc: Pv8Fn:

5 SpfBrdNo: 2 is invalid

The SPF board No., 2, indicated by the frame in which PV8 5 is installed is invalid.

Calllog: 9 1C2125 Pid69

CallPv8NetRefreshForGivenFrame for Pv8Fn 5 retcode: 212

The error code is 212. Inconsistency of the frame operation and the frame mode results in failure of PV8 5 network connection.

Calllog: 9 1C1984 Pid69 Cmd125 TC45012 OC43256 NC46784 T123 E36 cal_proc 2016

The TDM termination control module fails to send the context change request to the MTNU, because the context in the command does not comply with related rules.

Calllog: 9 1C1984 Pid69 Cmd125 TC45012 OC43256 NC46784 T2A1 E207 cal_proc 4063

The TDM termination control module fails to send the context change request to the user termination, because the context of the user termination does not comply with related rules.

Calllog: 9 1C2125 Pid74 TID1023 receive the address cmd in linestate

The status of the No.5 signaling sent by the MGC does not match that on the UMG8900.

7.3 Running Log

This describes the formats and related information of running logs.

7.3.1 Log Format

This describes the formats of running logs.

7.3.2 Common Running Logs and Meanings

This describes common running logs and their meanings.

7.3.1 Log Format

This describes the formats of running logs.

Run LST LOG: LTP=RUN; to check running logs. The result is as follows:

1 7 Front OMU 2005-03-09 15:35:13 30 5 Runlog: FN 1 SN 7 BT MOMU AUTOSAVE CFG

The first line records the basic information of the log report unit. The following table describes the basic meaning of each field.

Frame

No. Slot No. Board

Position Board

Type Record

Time Module

No. Level

1 7 Front OMU 2005-03-1

0 11:32:50

30 5

Runlog: at the beginning of the second line is the running log flag. FN indicates the frame No.;

SN indicates the slot No.; BT indicates the board type; the remaining is the detailed content of the running log.