Accessibilty ProblemsAccessibility ProblemsThis is a general trace for Accessibility Problems. No load concern is taken for the trace. Hicap most likely needed.

The BB traces can be used when having problems with Accessibility.

Accessibility problem traces in RACAccessibility Problem traces in BB

L2/RLC/RRCc: lhsh gcpu00768 te e bus_send UpDlRlcPeFt_SRB_PDU lhsh gcpu00256 te e bus_receive UpUlRlcPeFt_SRB_PDU lhsh gcpu00768 te e bus_receive bus_send UpDlRrcCPeFt_RANDOM_ACCESS lhsh gcpu00768 te e bus_receive bus_send UpDlRrcCPeFt_PAGING

UPC: lhsh gcpu01024 te all UpcUlCellCeFt_RANDOM_ACCESS (HEAVY, Potential High Load )

MAC: lhsh gcpu00768 te e trace1 trace5 UpDlMacPeBl_SraMsg2 lhsh gcpu00768 te e trace1 trace5 UpDlMacPeBl_Scom lhsh gcpu00768 te e trace1 trace5 UpDlMacPeBl_Spaging

DLphy: lhsh gcpu00768 te e trace1 UpDlL1Pe*

Accessibility Problem trace in BB using MTD

mtd peek -target dlL1Pe -ps UP_DL_MAC_PE_EI_MIB_DATA_INDmtd peek -target dlL1Pe -ps UP_ULCELLPE_EI_CELL_BUFFER_READY_INDmtd peek -target dlL1Pe -ps UP_DLMACPE_CI_PDCCH_INDmtd peek -target dlL1Pe -ps UP_DLMACPE_CI_RA_MSG2_ALLOC_INDmtd peek -target dlL1Pe -ps UP_DLMACPE_CI_DL_CCH_ALLOC_IND

ULPHY for Throughput and Accessibility:

mtd peek -target ulL1Pe -ps LPP_UP_ULL1PE_EI_ALLOCATION_INDmtd peek -target ulL1Pe -ps LPP_UP_ULL1PE_EI_DATA_INDmtd peek -target ulL1Pe -ps LPP_UP_ULMACPE_CI_UL_L1_MEAS2_DL_INDmtd peek -target ulL1Pe -ps LPP_UP_ULMACPE_CI_UL_L1_MEAS2_UL_IND

Add CellAdd CellA general trace that can be used when adding a cell.

Note that cell has to be added in order to get full benefit of the trace.

Trace Setup1. Functional traces: te e all CELL_CONFIG

2. A trace that can be used in live network, e.g: te e trace6 trace7 rnhRadioConfCellRegisterC te e trace6 trace7 rnhCellCtrlC te e trace6 trace7 rnhRadioConfCellCtxtC te e all ncLocalCellSwU lhsh gcpu00768 te e all UpDlRrcCPeFt_SYSTEM_INFO

3. Detailed trace, e.g: te e all rnhRadioConfCellRegisterC te e all rnhCellCtrlC te e all rnhRadioConfCellCtxtC te e all ncLocalCellSwU lhsh gcpu00768 te e all UpDlRrcCPeFt_SYSTEM_INFO

Cell Setup Problem trace in BB using MTD

mtd peek -target bbCellMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_SETUP_REQ mtd peek -target bbCellMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_SETUP_CFM

mtd peek -target bbCellMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_SETUP_REJmtd peek -target bbCellMeBl -ps BBMC_BBCELLME_MI_CELL_SETUP_COMPLETE_REQmtd peek -target bbCellMeBl -ps BBMC_BBCELLME_MI_CELL_SETUP_COMPLETE_CFMmtd peek -target bbCellMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_ACTIVATE_REQ mtd peek -target bbCellMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_ACTIVATE_CFM mtd peek -target bbCellMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_DEACTIVATE_REQ mtd peek -target bbCellMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_DEACTIVATE_CFMmtd peek -target bbCellMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_RELEASE_REQ mtd peek -target bbCellMeBl -ps

LPP_BBMC_BBCELLME_DCI_CELL_RELEASE_CFM

mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_SETUP_REQ mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_SETUP_CFM mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_SETUP_REJmtd peek -target upMeBl -ps BBMC_BBCELLME_MI_CELL_SETUP_COMPLETE_REQ mtd peek -target upMeBl -ps BBMC_BBCELLME_MI_CELL_SETUP_COMPLETE_CFM mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_ACTIVATE_REQ

mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_ACTIVATE_CFM mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_DEACTIVATE_REQ mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_DEACTIVATE_CFM mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_RELEASE_REQ mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_RELEASE_CFM

mtd peek -target upcMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_SETUP_REQ mtd peek -target upcMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_SETUP_CFM mtd peek -target upcMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_SETUP_REJ mtd peek -target upcMeBl -ps BBMC_BBCELLME_MI_CELL_SETUP_COMPLETE_REQ mtd peek -target upcMeBl -ps BBMC_BBCELLME_MI_CELL_SETUP_COMPLETE_CFM mtd peek -target upcMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_ACTIVATE_REQ mtd peek -target upcMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_ACTIVATE_CFM mtd peek -target upcMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_DEACTIVATE_REQ mtd peek -target upcMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_DEACTIVATE_CFM mtd peek -target upcMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_RELEASE_REQ

mtd peek -target upcMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_RELEASE_CFM

Auto Integration TraceAuto IntegrationThis is a general trace for Auto Integration. It is asumed that no traffic is executed so in general no consideration is taken to any load scenario.

To turn on trace groups; enter, return, trace1, trace3 and trace5 for everything under se.ericsson.lte.rbs.omf.mao.rbsconfiguration:

te enable enter return trace1 trace3 trace5

se.ericsson.lte.rbs.omf.mao.rbsconfiguration:*

See what traces are on for se.ericsson.lte.rbs.omf.mao.rbsconfiguration:

te search se.ericsson.lte.rbs.omf.mao.rbsconfiguration:*

In order for the traces to survive restarts during Auto Integration perform:

te save *

Trace Setup1. With Functional traces: te e all CELL_CONFIG te e all S1_CONN_SETUP (not working at the moment) te e all S1_PLUG_AND_PLAY

2. A trace that can be used in live network: te e trace6 trace7 omf.mao.rbsconfiguration:* te e trace6 trace7 se.ericsson.omf.mao.rbsconfiguration:* te e all cpxSctpFiC te e all cpxSctpIC te e all Scc_SctpHost_proc te e all Scc_SctpAdmMain_proc te e all cpxDriC te e all Cello_driServer_proc te e all rnhPnpS1ConnC te e all uehNwIfMmeRegisterC te e all uehNwIfTapDispatcherTopC te e all uehNwIfTapDispatcherFroHandlerC te e all uehNwIfTapDispatcherEpHndlC

3. Detailed trace: te e trace6 trace7 omf.mao.rbsconfiguration:* te e trace6 trace7 se.ericsson.omf.mao.rbsconfiguration:* te e all cpxSctpFiC te e all cpxSctpIC te e all Scc_SctpHost_proc te e all Scc_SctpAdmMain_proc te e all cpxDriC te e all Cello_driServer_proc te e all rnhPnpS1ConnC te e all uehNwIfMmeRegisterC

te e all uehNwIfTapDispatcherTopC te e all uehNwIfTapDispatcherFroHandlerC te e all uehNwIfTapDispatcherEpHndlC

Baseband Startup ProblemBaseband startup problemThis is a general trace for Accessibility Problems. No load concern is taken for the trace. Hicap most likely needed.

The BB traces can be used when having problems with Accessibility.

Baseband startup problem tracesFor startup problems the following measures should be taken to collect the necessary data from the baseband elements responsible for Load and Create:

te enable all bbmcBbOmMeSwUlhsh gcpu00256 te enable all bbmcBbUnitOmMeThreadlhsh gcpu00512 te enable all bbmcBbUnitOmMeThreadlhsh gcpu00768 te enable all bbmcBbUnitOmMeThreadlhsh gcpu01024 te enable all bbmcBbUnitOmMeThread

Bearer Stup And ReleaseBearer Setup and releaseThis is a general trace for Bearer setup and release problems. No load concern is taken for the trace. Hicap most likely needed.

The BB traces can be used when having problems with Bearer setup and release.

Bearer setup and release traces in RACte e all S1AP_ASN te e all RRC_ASN te e all UE_ERAB_SETUP te e all UE_ERAB_RELEASE ue enable -allcell -allUe

Bearer seup and release traces in BB Bearer seup and release in BB using MTD

mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_SIG_RADIO_BEARER_REQmtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_SIG_RADIO_BEARER_CFMmtd peek -target bbUeMeBl -ps

LPP_BBMC_BBUEME_UEMI_ADD_SIG_RADIO_BEARER_REJ mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_RADIO_BEARER_REQ mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_RADIO_BEARER_CFM mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_RADIO_BEARER_REJmtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_RELEASE_RADIO_BEARER_REQmtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_RELEASE_RADIO_BEARER_CFM

mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_SIG_RADIO_BEARER_REQ mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_SIG_RADIO_BEARER_CFM mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_SIG_RADIO_BEARER_REJmtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_RADIO_BEARER_REQ mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_RADIO_BEARER_CFM mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_RADIO_BEARER_REJ mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_RELEASE_RADIO_BEARER_REQmtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_RELEASE_RADIO_BEARER_CFM

mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_SIG_RADIO_BEARER_REQ mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_SIG_RADIO_BEARER_CFM mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_SIG_RADIO_BEARER_REJmtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_RADIO_BEARER_REQ mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_RADIO_BEARER_CFM mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_ADD_RADIO_BEARER_REJmtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_RELEASE_RADIO_BEARER_REQmtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_RELEASE_RADIO_BEARER_CFM

Dropped CallDropped call problemsThis is a general trace for Dropped Call Problems. No load concern is taken for the trace. Hicap most likely needed.

The BB traces can be used when having problems with Dropped calls.

Dropped Call traces in RACte e all S1AP_ASN te e all RRC_ASN te e all UE_RAC_MEASUREMENTS

Dropped Call traces in BB lhsh gcpu00768 te e all UpDlRlcPeFt_RETRANSM (HEAVY load)

Dropped Call trace in BB using MTDL2/RLC/RRCc:

Monitor RlcDeliveryFailure:

mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_RLC_DELIVERY_FAILURE_IND -dir OUTGOING

Monitor incoming handover in target node:

mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_HANDOVER_DETECTED_IND -dir OUTGOING

Inactivity SupervisionInactivity Supervision

This is a general trace for Inactivity Supervision. No load concern is taken for the trace. Hicap most lilkely needed.

The BB traces can be used when having problems with inactivity supervision. The RAC trace basically shows if the release cause is due to inactivity.

Inctivity Trace in RAC

Inactivity Supervision can be seen with normal RRC trace, e.g. RRC_ASN and UE_RLC_FAILURE where cause value in RRC Conection release will indicate "user inactivity". te e all RRC_ASN te e all UE_RLC_FAILURE

ue enable -allcell -allUe

Inctivity Trace in BB lhsh gcpu00512 te enable all UpUpMeBl lhsh gcpu00512 te enable all UpUpMeFt_INACTIVITY_SUPERVISION

Inctivity Trace in BB using MTDmtd peek -target upMeBl -ps UP_UPME_MI_REPORT_ACTIVITY_SV_IND mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_DRB_INACTIVITY_IND mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_DRB_ACTIVITY_IND mtd peek -target upMeBl -ps BBMC_BBUEME_MI_ACTIVATE_RADIO_BEARER_REQ mtd peek -target upMeBl -ps BBMC_BBUEME_MI_ACTIVATE_RADIO_BEARER_CFM mtd peek -target upMeBl -ps BBMC_BBUEME_MI_DEACTIVATE_RADIO_BEARER_REQ mtd peek -target upMeBl -ps BBMC_BBUEME_MI_DEACTIVATE_RADIO_BEARER_CFM mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_ACTIVATE_REQ mtd peek -target upMeBl -ps LPP_BBMC_BBCELLME_DCI_CELL_DEACTIVATE_REQ

L 2 General TraceL2 General traceFor all L2 type of problem, it is very useful to enable for all relevant traceobjects the following tracegroup: TRACE_TRAFFIC_ABNORMAL (trace1)

Other interesting trace objects for all L2 type of problems, enable: lhsh gcpu00256 te e all UpUlPdcpPeFt_DISCARD lhsh gcpu00256 te e all UpUlRlcPeFt_DISCARD lhsh gcpu00768 te e all UpDlPdcpPeFt_DISCARD lhsh gcpu00768 te e all UpDlRlcPeFt_DISCARD

Note: No load concern due to trace activation is taken. Most likely Hicap is needed.

Performance MonitoringTraces on PM counters and events

This is a general trace for PM counters and events. Currently no load concens are taken into account.

PM counter Trace in RACPM Process traces

check: Not used.

error: This trace group contains the Error trace.

enter:Used sometimes when entering an operation. Not recommended, but is sometime used.

return: Not recommended but should be used together with enter.

info:Should not be used since it cannot be switched off. However, it is used sparingly.

interface: Not used.

param: Not used.

object: Not used.

trace1:Same as TRACE_ABNORMAL. Used for faulty behaviours which the system can handle.

trace2: Same as TRACE_TIMER. Used for timers.

trace3: Same as TRACE_MISC. Used for information that is not a decision.

trace4: Not used.

trace5:Same as TRACE_DECISION. Used for information that is a decision (state change in the state diagram).

trace6: Same as TRACE_SEND. Used when sedning a message.

trace7: Same as TRACE_REC. Used when receiving a message.

trace8: Not used.

trace9: Not used.

state_change: Not used.

bus_send: Not used.

bus_receive: Not used.

rec_sig: Not used.

send_sig: Not used.

user1: Not used.

user2: Not used.

user3: Not used.

user4: Not used.

Trace Objects

System Trace Objects (only used sparingly):

PM_COUNTERS, PM_EVENTS, PM_EXCEPTION

OmfPm Trace Objects:

omfPmAgentIfUomfPmAgentSwUomfPmApplicationIfUomfPmApplicationProxySwUomfPmCommonLUomfPmControllerIfUomfPmControllerSwUomfPmControllerSupportSwUomfPmControllerProxySwU

OmfMon Trace Objects:

omfMonEventIfUomfMonEventLUomfMonIfUomfMonSwUomfMonIdRegFacSwU

OmfFro Trace Objects:

omfFroPmEventServiceIfUomfFroPmEventServiceSwU

LMMONITORPT:

te enable|disable|config <all|Trace Groups..> LmMonitorPT

LMOSETESTPROBEPT:

te enable|disable|config <all|Trace Groups..> LmOseTestProbePT

PM_COUNTERS

te enable|disable|config <all|Trace Groups..> PM_COUNTERS

PM_EVENTS.

te enable|disable|config <all|Trace Groups..> PM_EVENTS

PM_EXCEPTION:

te enable|disable|config <all|Trace Groups..> PM_EXCEPTION

PM_FRAMEWORK:

te enable|disable|config <all|Trace Groups..> PM_FRAMEWORK

MAIN_THREAD:

te enable|disable|config <all|Trace Groups..> main_thread

PM Java traceserror: This trace group contains the Error trace.

return: Not used.

info: This trace group contains the Information trace.

param: Trace of parameter values in signals received or sent.

trace1:Same as TRACE_ABNORMAL. Used for faulty behaviours which the system can handle.

trace2: Same as TRACE_TIMER. Used for timers.

trace3:Trace of general program flow messages, less important than info but more important than debug.

trace4: Not used.

trace5: Trace of debug messages to ease troubleshooting.

trace6: Not used.

trace7: Not used.

trace8: Not used.

trace9: Not used.

PM

te enable|disable|config <Trace Groups..> se.ericsson.lte.rbs.omf.pm:*

PMAPPLICATION:

te enable|config|disable <Trace Groups..> se.ericsson.lte.rbs.omf.pmapplication:*

PMCOMMON:

te enable|disable|config <Trace Groups..> se.ericsson.lte.rbs.omf.pmcommon:*

PMEVENT:

te enable|disable|config <Trace Groups..> se.ericsson.lte.rbs.omf.pmevent:*

PMPROXY:

te enable|disable|config <Trace Groups..> se.ericsson.lte.rbs.omf.pmproxy:*

PMSTATISTICS

te enable|disable|config <Trace Groups..> se.ericsson.lte.rbs.omf.pmstatistics:*

PM event traces in RAC (they are also base for EHB and Exception)te enable all MON_EVENTSte enable all MON_EVENTS_DETAILED

PM counter traces in BB using MTD

Take the following steps: 1. Identify the faulty counter, e.g. PM_EVENT_PARAM_UE_ACTIVE_TIME and its ID in 10/1022-HRB105500. 2. Lookup owning RAN class in proper UCR (Or UP or UPC class specifications in future.) 3. Enable PM-tracing on the correct GCPU on the responsible RAN-class according to:

te enable <RANClass>Ft_MCS_COUNTER_INCREMENT all

where RANClass should be replaced with the name of the owning class e.g. UpUpMe. Look for the faulty counter's ID in the logs.

Throughput ProblemsThroughput ProblemsThis is a general trace for Throughput Problems. No load concern is taken for the trace. Hicap most likely needed.

The BB traces can be used when having problems with Throughput.

Throughput problem traces in RACThroughput Problem traces in BB

L2/RLC/RRCc:

lhsh gcpu00768 te e all UpDlRlcPeFt_RETRANSMlhsh gcpu00768 te e all UpDlRlcPeFt_DEADLINE_MISSED

MAC:

lhsh gcpu00768 te e all UpDlMacPeFt_DEADLINE_MISSED lhsh gcpu00256 te e all UpUlMacPeFt_DEADLINE_MISSED

lhsh gcpu00768 te e bus_send UpDlMacPeFt_PDU (HEAVY, gets data for all transport blocks sent DL) lhsh gcpu00256 te e bus_receive UpUlMacPeFt_PDU (HEAVY, gets data for all Trans blocks received UL)lhsh gcpu00768 te e trace5 UpDlMacPeBl (trace for each sent TB in DL, but not the actual data in the TBlhsh gcpu00256 te e trace5 UpUlMacPeFt_PDU (trace for each recieved TB in UL, but not data)

To see information about incorrect TB:s due to syntax or CRC faults, enable:

lhsh gcpu00256 te e trace1 UpUlMacPeBl_Smac (for normal UE messages)lhsh gcpu00256 te e trace9 UpUlMacPeBl_Smac (for RaMsg3 messages with incorrect CRC)

If it is suspected that the ulL1 processing takes too long, it would be interesting to enable the following trace: ( check which ULMA to use for traces !!)

lhsh gcpu00256 te e trace2 UpUlL1PeBlMaster_Spusch

DLphy:

lhsh gcpu00768 te e trace1 UpDlL1Pe*

Throughput Problem trace in BB using MTD

ULPHY for Throughput and Accessibility:

mtd peek -target ulL1Pe -ps LPP_UP_ULL1PE_EI_ALLOCATION_INDmtd peek -target ulL1Pe -ps LPP_UP_ULL1PE_EI_DATA_INDmtd peek -target ulL1Pe -ps LPP_UP_ULMACPE_CI_UL_L1_MEAS2_DL_INDmtd peek -target ulL1Pe -ps LPP_UP_ULMACPE_CI_UL_L1_MEAS2_UL_IND

DLphy:

mtd peek -target dlL1Pe -ps UP_DLMACPE_CI_DL_UE_ALLOC_INDmtd peek -target dlL1Pe -ps UP_DLL1PE_EI_DL_L1_DATA_INDmtd peek -target dlL1Pe -ps UP_ULCELLPE_EI_CELL_BUFFER_READY_INDmtd peek -target dlL1Pe -ps UP_DLMACPE_CI_PDCCH_IND

Monitor userdata activitity:

mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_DRB_INACTIVITY_IND -dir OUTGOINGmtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_DRB_ACTIVITY_IND -dir OUTGOING

mtd peek -target ulL1Pe -ps LPP_UP_ULL1PE_EI_ALLOCATION_INDmtd peek -target ulL1Pe -ps LPP_UP_ULL1PE_EI_DATA_INDmtd peek -target ulL1Pe -ps LPP_UP_ULMACPE_CI_UL_L1_MEAS2_DL_INDmtd peek -target ulL1Pe -ps LPP_UP_ULMACPE_CI_UL_L1_MEAS2_UL_IND

Ue Setup And ReleaseUe Setup ad releaseThis is a general trace for Ue setup and release problems. No load concern is taken for the trace. Hicap most likely needed.

The BB traces can be used when having problems with Ue setup and release.

Ue setup and release traces in RACte e all S1AP_ASN te e all RRC_ASN ue enable -allcell -allUe

Ue seup and release traces in BB Ue seup and release traces in BB using MTD

mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_SETUP_REQ mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_SETUP_CFM mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_SETUP_REJ mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_RELEASE_REQ mtd peek -target bbUeMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_RELEASE_CFM

mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_SETUP_REQ mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_SETUP_CFM mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_SETUP_REJ mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_RELEASE_REQ mtd peek -target upMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_RELEASE_CFM

mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_SETUP_REQ mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_SETUP_CFM mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_SETUP_REJ mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_RELEASE_REQ mtd peek -target upcMeBl -ps LPP_BBMC_BBUEME_UEMI_UE_RELEASE_CFM

UPC General TraceGeneric Traces in UPC for all problem types This is a general trace for UPC Problems. No load concern is taken for the trace. Hicap most likely needed.

PM of Interest for UPCEVENT_PARAM_PER_ACTIVE_UE_DL_SUM EVENT_PARAM_PER_SCHED_ACTIVITY_CELL_DL EVENT_PARAM_PER_SCHED_ACTIVITY_UE_DL EVENT_PARAM_PER_UE_THP_TIME_DL

UPC traces in BB lhsh gcpu01024 te e trace1 Upc* lhsh gcpu01024 te e CHECK Upc*

S1-CP Connection HandlingTable of Contents

Last known applicable SW/HW Use Case Realization Reference

o Trace Setup 1 o Trace Setup 2 o Trace Setup 3

Trace Setup 1DescriptionThe trace can be used for: * RANUC077.N Update MMEs - Retain existing* RANUC077.A1 Update MMEs - renew existing in MME list* RANUC077.A2 Update MMEs – renew all existing MMEs * RANUC077.A4 Periodic DNS lookup for MMEs – Changed MMEs

Traces1. Functional trace: te e all S1AP_ASN te e all S1_COMMON_SIGNALING te e all S1_PLUG_AND_PLAY

2. Trace that can be used in live network: te e trace7 rnhRadioConfCellRegisterC te e trace7 rnhCellCtrlC

3. Detailed trace (mainly for STP): te e all rnhRadioConfCellRegisterC te e all rnhCellCtrlC>

eNB ConfigurationNot Applicable

Trace ResultsNot Applicable

Trace Setup 2

DescriptionThe trace can be used for: * RANUC078: Disconnect by O&M* RANUC080: MME Releases Connection* RANUC081: Connection to Mme Break* RANUC082: Reset from MME* RANUC083: Lock MME Connection from operator

1. Functional trace: te e all S1AP_ASN te e all S1_COMMON_SIGNALING te e all S1_PLUG_AND_PLAY

2. Trace that can be used in live network: te e trace7 rnhRadioConfCellRegisterC te e trace7 rnhCellCtrlC

3. Detailed trace (mainly for STP): te e all rnhRadioConfCellRegisterC te e all rnhCellCtrlC te e all trace1 trace2 trace3 trace4 trace5 trace6 trace7 trace8 trace9 rec_sig send_sig param state_change nc* trace config -run enter return trace1 trace2 trace3 trace4 trace5 trace6 trace7 trace8 info se.ericsson.lte.rbs.omf.aue:*

NTP SycnhronizationNTP Synchronization problems

This is a general trace for NTP synchronization Problems. No load concern is taken for the trace.

The trace collects timestamps T1-T4 according to NTP specification. The trace is mostly useful to design. They use the traces in combination with Matlab script to plot and analyse the data.

NTP Synchronization traces

te e trace5 NSS_CBM_TUM2_TUREG

Another useful trace to get state changes is.

te e trace9 NSS_CBM_TUM2_TUREG

Sector And Cell PowerSector and cell power tracesThis is a general trace for Sector and cell power Problems. No load concern is taken for the trace. Hicap most likely needed.

A good way to check the RUL power capability is to check:

lhsh BXP_X_Y db list /board/powerClassUsage

The output power of the cell is dependent on the following parameters:

The licensed output power EUtranCellFDD.partOfRadioPower MO parameter SectorEquipmentFunction.confOutputPower MO parameter The capability of the Radio Unit (RU) board

When the Sector is unlocked the confOutputPower is requested from the license handler. The Sector is either assigned the requested outputpower or if it is not available or the licenseserver is down, it receives the basic value 20W. The Sector will compare this value to the capability of the Radio HW and then based on that comparison store the value of power per Radio Unit that it may use. If the Sector receives less than the requested output power (confOutputPower) it will become degraded and an alarm will be generated.

When a Cell is unlocked in the Sector it will request the wanted output power as a percentage of the radios HW capability (partofradiopower = percent of RU HW max). It will also check if this amount of power per RU is available to use in the Sector. If so the Cell is unlocked and the Sector will subtract the power that the cell is using per RU from the power that is has available. If the cell does not get the amount of output power it requested it will become degraded and an alarm will be generated.

Note: All cells located in the Sector must share the output power that the Sector is configured to use (based on output power license, value of SectorEquipmentFunction.confOutputPower and RU HW).

Sector and cell power traces in RACThe trace should be active at sector deblock.

te config all omfLicenseHandlerOutputPowerCte e all ncSectorSwUte e all ncLocalCellSwUte e all CELL_CONFIGte e all CELL_RESOURCE_HANDLING

te e all CELL_TIMINGte e all CELL_POWER_SETTINGte e all CELL_DATA_DISTRIBUTIONte e all CELL_SI_DISTRte e all CELL_ANR_MEASte e all SECTOR_CONFIG