Atp bsc logging_v1 0

HTM ATP SBS & CPDS Diagnostic Logging

RF Engineering, Nortel Vietnam

May. 14th, 2007

2

Contents

> SBS/CPDS Diagnostic Logging Overview

> SBS/CPDS Diagnostic Logging• SBS Diagnostic Logging—GUI• SBS Diagnostic Logging—Command Line• CPDS Diagnostic Logging—GUI• CPDS Diagnostic Logging—Command Line

> HTM ATP SBS/CPDS Diagnostic Logging Attributes

3

> Granularity• SBS Diagnostic logs can be configured/enabled on per-shelf basis

> Conditional Logging• Selected attributes are collected for list of mobile IMSI specified in MTX table

CDMAICC• Usually need to collect logs on all SBS shelves to ensure all desired calls are

captured• Normally used conditional logging for drive testing• Caution must be taken at MTX boundaries as IMSI are removed from the

CDMAICC table when a mobile crosses the MTX boundary

> Unconditional Logging• Selected attributes collected for all calls• Used to get a sampling of calls• Normally collects attributes on 8 to 12 shelves

SBS/CPDS Diagnostic Logging Overview

4

> Log template must first be created and saved• defines the attributes and how the attributes are to be logged, conditional or

unconditional, for a specified subsystem(s)• Template is used to create actual log

> Number of logs and size of logs controlled by BSSM Log Version Policy

• Section by Time • creation of a new log file is determined by the age of the current log file.

When an upload occurs, the time stamp of the existing log file is compared to the current time. If the current time is greater than the timestamp on the existing log file by the amount defined, then a new log file is created, else the uploaded log is appended to the existing file.

• Section by Size • creation of a new log file is determined by the size of the current log file.

When an upload occurs, the size of the existing log file is compared to the defined value. If the size is greater than the defined value, then a new log file is created, else the uploaded log is appended to the existing file.

SBS/CPDS Diagnostic Log Creation

!!!

5

> Log buffer fill-up behavior on an individual card is controlled by Subsystem Log Full Behavior

• Continuous • when the buffer is filled up, the BSSM will initiate the upload of the log

buffer. During upload, most attributes being logged will be placed in a temporary buffer and transferred to the log buffer when uploading is complete

• Halt • when the buffer is filled up, logging is suspended on the card. The BSSM

operator will initiate uploading at a later time

• Wrap • this will treat the log buffer as a circular buffer. When the buffer fills up it will

start overwriting at the beginning.

SBS/CPDS Diagnostic Log Creation

6

> Conditional logging datafill on MTX• After MTX login, type

• >CDMAICC

• To add an IMSI to CDMAICC table for conditional log, type• >ADD <IMSI> on on off • Example: ADD 450052081000153 on on off

• To check the IMSI in table, type • >list all

SBS/CPDS Diagnostic Logging Process

7

> SBS/CPDS diagnostic logging steps

• Creating SBS/CPDS Log Templates

• Creating SBS/CPDS Logs

• Starting SBS/CPDS Logs

• Suspending SBS/CPDS Logs

• Uploading SBS/CPDS Logs

• Checking SBS/CPDS Log Status

SBS/CPDS Diagnostic Logging Process

8

SBS Diagnostic Logging—GUI

9

> Creating SBS Log Templates

• Start the GUI, from UNIX command line prompt type buinavapp

• Expand the Tree with the right mouse button, and select element SelectorSubsystem1

• Entire path structure for the SBS shelf selector card subsystem is:

CBS1SBSs1 SBSCSubsystem1 Root1 SBS1 SelectorSubsystem1


10


11


> Open Log Template Editor• From the main GUI, select Log Creation from the Logging menu on

the top tool bar

12


> Log Template Editor

13


> Select desired Loggable Attributes

1. Select Attribute Name

2. Click Generate/Update

3. Attribute path name appears below

14


> Check required attributes selected

15


> Saving SBS Log Template• Use names that identify both the logging task & the shelf or shelves

logged

16


> Creating SBS Logs• Specify the Log Name, template to use, and log creation

parameters (size/time, conditional / unconditional)

17


> Starting SBS Logs• SBS Log can be started from

the Log Template Editor and Log Management in the GUI

18


> Suspending SBS Logs• SBS logs must be suspended

first, before uploading data is possible. Stopping the log will result in a loss of any data remaining in the selector card.

19


> Uploading SBS Logs• Only Suspended Logs can be

Uploaded, uploading takes the remaining log data in the selector card 0.5 Mb buffer and copies it to the log file on the BSM.

20


> Deleting SBS Logs• After downloading all the log

file to local PC, the log file can be deleted.

21

SBS Diagnostic Logging—Command Line

22

> Creating SBS Log Command Line Scripts• Open the Excel file “SBSLog_ScriptGen.xls” comes with CROS• Datafill the log name, logging type, attributes to be logged, log file

size, number of log files… Also datafill the shelves to be logging in spreadsheet “SBS Shelves”.

• Click button “Generate CLI Script”, 6 script files will generated in Output script folder

• In spreadsheet “Log Attributes” contains all log attributes name, type number, sequence number and description


Microsoft Excel Worksheet

23

> Uploading all 6 script files to active BSM• Need to do dos2unix for script files in BSM!!!

• From UNIX command line prompt type dos2unix filename filename

> Entering command line mode on BSM• From UNIX command line prompt type cliapp


24

> SBS logging steps• Creating log template

• >script –ce <templates_script>;

• Creating log• >script –ce <create_script>;

• Starting log• >script –ce <start_script>;

• Suspending log• >script –ce <stop_script>;

• Uploading log• >script –ce <upload_script>;

• Deleting log• >script –ce <delete_script>;

• Checking log status• >logstate;


25

> After the log starting, check the log status, make sure all shelves log status are “Active”. The log file can be seen under directory:/opt/bsm/log

> After DT finished, suspend the log and log status change to “Suspended”. When upload the log and the log status change to “UploadInProgress” then “Ready”.

> When all log status change to “Ready”, go to directory /opt/bsm/log and combine all shelves log file into 1 file. • htc1cems2% cat ATP* > sbslog20070511.sbs

> Or don’t want to combine the file into 1 file• htc1cems2% tar –cvf sbslog20070511.tar ATP*• htc1cems2% gzip sbslog20070511.tar

> After downloading above file to local PC, run “Deleting Log” step. Don’t move (mv) or delete (rm) log files!!

> In next time to start the log, just begin with “Creating Log” steps

SBS Diagnostic Logging—Considerations

26

CPDS Diagnostic Logging—GUI

27

> Install CEMS application desktop on client PC• Download the installation package from BSM directory:

/opt/cems/install/cems_pkgCAD/setup_cemsbld1210fl.zip• Install the above package on your PC.

• Start the CEMS application from PC. • Start All Programs Nortel CDMA C-EMS12.1 C-EMS

Application Desktop


28


29


> Open Log Template Editor• From Network Navigator top tool bar menu, select Configuration—

Logs—Log Template Editor

30


> Log Template Editor

31


> Select desired Loggable Attributes

1.Type in Template Name

2.Select the MO for Logging

3.Select Attribute Name

4. Click Add

5. Attribute path name appears below

32


> Creating CPDS Log Template• Use names that identify both the logging task & the NE logged

33


> Creating CPDS Logs• Specify the Log Name, logging NE (Multi card selection by holding

CTRL key), then push the button “Assign”

34


> Starting CPDS Logs• CPDS Log are created first time with status “INITIALIZED”.• CPDS Log can be started from the Log Template Editor and Log

Manager in the GUI• Select the log and right click, choose “Start/Resume”

35


> Suspending CPDS Logs• CPDS logs must be suspended first, before uploading data is

possible. Stopping the log will result in a loss of any data remaining in the DSFP card.

36


> Uploading CPDS Logs• Only Suspended Logs can be Uploaded. Uploading takes the

remaining log data in the DSFP card buffer and copies it to the log file on the BSM.

37


> Deleting CPDS Logs• Only “READY” Logs can be deleted. Deleting will delete the log in

the log manager and the log file under directory /opt/cems/log.

38


> Flush CPDS Logs• Only Suspended Logs can be Flushed. Flushing will erase the

remaining log data in the DSFP card buffer and erase the data in log file under directory /opt/cems/log. But log will keep in the log manager.

39

CPDS Diagnostic Logging—Command Line

40

> CPDS diagnostic log template• Log template can NOT be created in CPDS command line mode.

The log template has to been built in C-EMS GUI

> Entering command line mode on C-EMS• From UNIX command line prompt type cemscli• Checking log status command line must be run under Generic Card,

for example DSFP or PCU card.• Enter DSFP card NE in command line by type

• > cd Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10


41

> CPDS logging steps• Creating log

• >action InitLog -e <NE> -l LogName <NAME> TemplateId <TEMPLATENAME> -y• For example in Hanoi have 2 DSFP Card

• action InitLog -e Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10 -l LogName MyCLITest TemplateId HNI_ATP_CPDS -y

• action InitLog -e Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.11 -l LogName MyCLITest TemplateId HNI_ATP_CPDS -y

• Starting log• >action StartLog -e <NE> -l LogId <NAME>• >action StartLog -e Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10 -l LogId dlog.MyCLITest

• Suspending log• >action SuspendLog -e <NE> -l LogId <NAME>• >action SuspendLog -e Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10 -l LogId dlog.MyCLITest

• Uploading log• >action UploadLog -e <NE> -l LogId <NAME>• >action UploadLog -e Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10 -l LogId dlog.MyCLITest


42

> CPDS logging steps• Flushing log

• >action FlushLog -e <NE> -l LogId <NAME>• >action FlushLog -e Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10 -l LogId dlog.MyCLITest

• Stopping log• >action StopLog -e <NE> -l LogId <NAME>• >action StopLog -e Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10 -l LogId dlog.MyCLITest

• Resetting log• >action ResetLog -e <NE> -l LogId <NAME>• >action ResetLog -e Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10 -l LogId dlog.MyCLITest

• Deleting log• >action DeleteLog -e <NE> -l LogId <NAME>• >action DeleteLog -e Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10 -l LogId dlog.MyCLITest

• Check log status• >cd Network.1:SubNetwork.1:eBSC.1:eBSCShelf.1:DSFPCard.10• >get logs


43

> After the log starting, check the log status, make sure the log status are “Active”. Also the log file are available under directory:/opt/cems/log

> After DT finished, suspend the log and log status change to “Suspended”. When upload the log and the log status change to “Uploading” then “Ready”.

> When all log status change to “Ready”, download the log file to local PC.

> Before next time to start the log, run the steps (a)Starting Log, (b)Suspend Log, (c)Flushing Log. The Flushing will erase the log data in the DSFP card buffer and erase the data in log file but keep the log in the C-EMS. Don’t move (mv) or delete (rm) log files!! Then begin with “Starting Log” steps for next drive test.

> The default log template defines1 day section of time and 1 section file. If uploading the log file happened after 24hrs, keep in mind change those 2 numbers >1

CPDS Diagnostic Logging—Considerations

!!!

44

HTM ATP SBS/CPDS Diagnostic Log Attributes

> SBS Diagnostic Log Attributes

LogSBSActiveSetChange LogSBSForwardLinkFER

LogSBSNeighborListTuningArray LogSBSForwardMarkovData

LogSBSRoundTripDelay LogSBSReverseLinkFER

LogSBSVitalData LogSBSReverseMarkovData

LogCallDropData LogSBSReceivedMuxDecision

LogLinkFERData Log3GPowerControlData

LogMCTACDAData LogSBS3GRevFrameInfo

IS95Messages LogSBSMarkovData

LogSBSPowerControl LogCallSummary

LogConfigData LogMCTACDADataEnhanced

LogSBSCallAssociation

45

HTM ATP SBS/CPDS Diagnostic Log Attributes

> CPDS Diagnostic Log Attributes

LogCallAssociation LogLinkFERData

LogActiveSetChange LogRevSCHTrafficFrameInfo

LogForwardLinkFER LogFwdSCHTrafficFrameInfo

LogPowerControl Log3GPowerControlData

LogReceivedMuxDecision Log3GRevFrameInfo

IS95Messages LogSCHActiveSetChange

LogReverseLinkFER LogSCHFrameSelectionData

LogTransmitMuxOption LogMCTACDADataEnhanced

LogRoundTripDelay LogMCTACDAData

LogVitalData LogForwardRLPData

LogNeighborListTuningArray LogReverseRLPData

LogConfigData LogForwardRLPSignaling

LogCallDropData LogReverseRLPSignaling

46

Thanks!

Atp bsc logging_v1 0

Documents

Transcript of Atp bsc logging_v1 0