BSC Counter Inquiry

7/29/2019 BSC Counter Inquiry

http://slidepdf.com/reader/full/bsc-counter-inquiry 1/33

TV - BSC Counter Inquiry

dn9813406Issue 9-0 en

# Nokia CorporationNokia Proprietary and Confidential

1 (33)

2003319

Nokia BSC/TCSM S11 Product Documentation



The information in this documentation is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia's customers only for the purposes of the agreement under which the documentationis submitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The documentation has been prepared to be used byprofessional and properly trained personnel, and the customer assumes full responsibility whenusing it. Nokia welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the documentation areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

Nokia's liability for any errors in the documentation is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or the

information in it.

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this documentation may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2003. All rights reserved.

2 (33) # Nokia CorporationNokia Proprietary and Confidential





Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

TV: BSC COUNTER INQUIRY 9

1 TVI: INQUIRE AND OUTPUT COUNTERS 11

2 TVO: OUTPUT COUNTERS 19

3 TVS: SHOW DESCRIPTION OF THE COUNTERS 27

4 TVR: RESET THE COUNTERS 31



3 (33)

Contents



List of tables






List of figures



5 (33)

List of figures



Summary of changes

Summary of changes

Changes between document issues are cumulative. Therefore, the latest document

issue contains all changes made to previous issues.

Changes made between issues 9 and 8

TVS Index number values 51000-51153 have been changed to

51000-51154.


57000-57048.

TVS Index number values 700-715 have been changed to 700-720.



51000-51153.


57000-57046.


TVS Index number values 700-714 have been changed to 700-715.

TVR More information on the use of the command TVR added.



7 (33)

Summary of changes



TV: BSC COUNTER INQUIRY

The commands of the command group can be used to interrogate the counter values of the BSC level clear code measurements. They can also be used to

interrogate the description of a certain counter of such measurement, and reset the

counters.

Use the commands of this command group when you want to make an extra

counter data collection.

The use of the commands in the command group is explained in BSC Statistics

Administration .

With these commands you can handle only the BSC level clear code (SERLEV)

measurement, BSC level clear code (PM) measurement, and BSC level clear code

measurement.

Menu of the command group

B S C C O UN T ER I N QU I RY C O MM A ND S

? . .. .. D I SP LA Y M EN U

I : . . .. . I N QU I RE A N D O U TP U T C O UN T ER S

O : . . .. . O U TP U T C O UN T ER S

S : . . .. . S H OW D E SC R IP T IO N O F T H E C O UN T ER S

R : . . .. . R E SE T T H E C O U N T ER SZ ; . .. .. R ET UR N T O M AI N L EV E L


The commands in this command group are:

TVI INQUIRE AND OUTPUT COUNTERS

TVO OUTPUT COUNTERS

TVS SHOW DESCRIPTION OF THE COUNTERS

TVR RESET THE COUNTERS



9 (33)


1 TVI: INQUIRE AND OUTPUT COUNTERS

Function

With the TVI command you inquire the counter values of the BSC level clear

code measurements and output the values to an MML session.

Parameters

measurement number:

call phase,BTS id type,BTS id,BTS name,destination cell type;

Syntax

B T S m e a s u re m e n t s

T V I : < me a s u r em e n t n u m b e r> : , ( , | )< d e s t i na t i o n c e l l

type>...;

B S C m e as u re m en t s (c a se 1 ) :

T V I : < me a s u r e me n t n u m b e r> ;


T V I : < me a s u r e me n t n u m b e r> : < c a ll p h a s e >;

BTS measurements is measurement number 47.

BSC measurements (case 1) is measurement number 48.


The corresponding measurement names and numbers are displayed in the

parameter guide. Below is an example of a parameter guide.



11 (33)

TVI: INQUIRE AND OUTPUT COUNTERS



Parameter explanations

measurement number

With this parameter you indicate the measurement whose

counter values you want to output. The names and the

corresponding numbers of the measurements are displayed in

the parameter guide. The measurement numbers are common

identifiers used in the BSC.

The possible values are 47, 48 and 49.

Example of a parameter guide:

/ * I D EN T IF Y M EA S UR E ME N T:

4 7 B SC L E V EL C L E AR C O D ES M M L (S ER LE V)

MEASUREMENT4 8 B SC L EV EL C LE AR C OD ES M ML (P M)

MEASUREMENT

4 9 B SC L EV EL C LE AR C OD ES M ML M E AS UR E ME NT

T H E P A RA M ET E R I S O B LI G AT O RY

*/

call phase With this parameter you indicate the phase or phases of the

call transaction whose measurement results you want to

inquire. The names and the corresponding numbers of the

phases are displayed in the parameter guide.

The possible values range from 1 to 15. You can use the

grouping characters & and &&.

The parameter can have the following values:

Parameter Value Description

CP 1 PAGING/INITIAL MS (CCCH

AND SDCCH OR TCH)

2 MM-SIGNALLING (SDCCH OR

TCH)

3 BASIC ASSIGNMENT (SDCCH

AND TCH)

4 RELEASE (SDCCH OR TCH)

5 FACCH ASSIGNMENT (TCH)






6 SMS-ESTABLISHMENT (TCH)

7 SMS-ESTABLISHMENT

(SDCCH)

8 CIPHERING (SDCCH OR TCH)

9 EXTERNAL HANDOVER

(SDCCH OR TCH, SOURCE)

10 INTERNAL HANDOVER INTRA


11 INTERNAL HANDOVER INTER


12 EXTERNAL HANDOVER

(SDCCH OR TCH, TARGET)





15 CONVERSATION (TCH)

The parameter is obligatory for the BSC level clear code

measurement.

BTS id type With this parameter you indicate whether you identify the

BTS by its name or number.

The possible values are 1 and 2, where 1 means BTS id and 2

means BTS name.

BTS id With this parameter you indicate by number the BTS whose

measurement results you want to inquire. The possible values

range from 1 to 128 or 1 to 248 depending on the BSC

configuration. You can use the grouping characters & and &&

when you are inquiring the results of the BTS measurements.

BTS name With this parameter you indicate by name the BTS whose

measurement results you want to inquire. The name can

contain from 1 to 15 characters. You can inquire the results of

two separate BTSs by using the grouping character &.



13 (33)




Destination Cell Type

With this parameter you indicate the type of destination cell

whose measurement results you want to inquire. The value is

either 0 or 1.

0 = normal cell

1 = extended cell

Examples

1. Inquire and output counters of BSC LEVEL CLEAR CODES (PM)

measurement.

TVI:48;

2. Inquire and output updated counters in the BSC LEVEL CLEAR CODES

measurement in PAGING/INITIAL MS call phase.

TVI:49:1;

3. Inquire and output updated counters in the measurement BSC LEVEL

CLEAR CODES (SERLEV) MEASUREMENT in a BTS named KILO.

TVI:47:2,KILO,0;

Additional information

The parameter guide and the semantic check are dynamic.

After the semantic check, the DXCMML sends an extra collection message to its

counterpart, PUMMIT. The PUMMIT starts the counter collection from all

relevant computer units.

The DXCMML waits for 40 seconds before it sends a counter request message of

the first inquired object to the PUMMIT. If the counter collection is still running,

the DXCMML repeats the request every three seconds until it receives an

acknowledgement, or the delay of two and a half minutes has run out.

After the DXCMML receives the values of the counters of the first object, it inquires the counters of the other objects (if they have been requested)

sequentially. When the DXCMML receives the values of the counters of the last

objects, it summarises the values of the counters and outputs all those counters

which have a value other than zero.






Execution printouts

The execution printout for the command in example 2 (if there are counters that

have values) is the following:

M EA S I D: 4 9

MEAS NAME:BSC_CLEAR_MML_MEAS_C

P H A S E (S ) : 1 ,

PAGE 1

NUM COUNTER VAL UE NUM COUNTER VALUE

--------------------------------------------------------------------------

300 USER_ACT_BLOCK 1 301 NETW_ACT_BLOCK 2

302 BTS_FAIL_BLOCK 3 303 LAPD_FAIL_BLOCK 4

304 ABIS_FAIL_BLOCK 5 305 ABIS_MSG_CORRUP_TO_BTS 6

306 ASS_FAIL_MSG 7 307 BLOCK_SLAVE 8

308 CH_ACT_NACK 9 309 CH_ACT_NACK_OM_INTER 10

310 CH_ACT_NACK_EQUIP_FAIL 1 1 311 CH_A CT_NA CK _EN CR YP_AL G 12

3 12 C H_ AC T_ NA CK _R AD _C H_ AL R_ A 1 3 3 13 C H_ AC T_ NA CK _S ER V_ NO T_ AV A 1 4

314 CH_ACT_FAIL 15 315 CONN_FAIL 1 6

3 16 C ON N_ FA IL _R AD _I NF _F AI L 1 7 3 17 C ON N_F AI L_R AD _LI NK _F AIL 1 8

318 CONN_FAIL_REM_TRANS_FAIL 19 319 DATA_IND_CORRUP 20

320 ERR_IND 21 321 E STA B_ IN D_F AI L 2 2

322 ESTAB_CONF_FAIL 23 323 HO_FAIL 2 4

324 HO_DETECT_FAIL 25 325 MODE_MOD_NACK 26

326 MODE_MOD_ACK_FAIL 27 32 7 NO_MEAS_RESULT 28

328 NO_RESP_FROM_COPRO 29 32 9 P HY _CONT _CONF _FAIL 30

330 RCS_ALG_START_ACK_FAIL 3 1 331 RCS_ ALG_C L_ ACK _F AIL 32

332 RC0_DISCO_IND 33 333 RF_CH_REL_ACK_FAIL 34

334 REL_IND 35 335 R EL_ IN D_ FAI L 36

PAGE 2


--------------------------------------------------------------------------

920 M_MS_NOT_EQIPPED 181 92 1 M_T R_COD_RAT_AD_UNAV 182

922 M_CIPH_ALG_NOT_SUPP 183 923 M _TE RR _CH AN _A LR_ AL LC 184

924 M_PROT_ERR_B_BSC_MSC 185 925 M _UN EX PEC TE D 1 86

926 M_INVALID_CELL 187 927 M_INVALID_MSG_CONT 1 88

928 M_IE_OR_FIELD_MISSING 1 89 929 M_IN CORRE CT_VA LU E 190

930 M_UNKNOWN_MSG_TYPE 191 931 M _UN KN OW N_I E 192

9 32 M _T RA NS C_ OR _R AT E_ UN AV AI L 1 93 9 33 M _C IP _T YP E_ MI TS MA TC H 1 94

934 M_SWITCH_CICUIT_POOL 195 935 M _SP EE CH_ VE RS ION _U NAV A 196

C O M M A ND E X E C U TE D

Abbreviations used in the execution printouts are:

MEAS ID= measurement identification

MEAS NAME= measurement name



15 (33)




NUM= index number of the counter

COUNTER= name of the counter

The execution printout, if there are no counters which have values, is the

following:

/ ** * N ON E O F T HE C OU NT E RS W A S U PD AT ED * ** /


Semantic error messages

/ * ** B T S N O T E X I ST E NT * * * /

The name used in identifying the BTS does not exist in the Radio Network

Database. Check the BTS name you have given. If the name was given correctlyand the same error message is repeated, the BTS may not exist in the network.

Create the BTS again. For more information on creating a BTS, see Base

Tranceiver Station Handling in BSC .

If some other error occurs, the general semantic error printouts of MML

commands are output. For more information, see General Notice Messages of

MML Session .

Execution error messages

/ * ** C O UN T ER C O L LE C TI O N F A IL E D * * */

The counter collection set by the PUMMIT has failed. Re-enter the command. If

the command execution still does not succeed, the PUMMIT program may not be

running. Restart the program.

/ * ** A N OT H ER C O U NT E R C O LL E CT I O N R U N NI N G

TRY AGAIN * ** /

There is a counter collection running, set by the OMC or the DXCMML. You

cannot set the counter collection before the previous collection has ended.

/ * ** C O UN T ER C O L LE C TI O N D I D N O T S U C C E ED I N G I VE N T I ME * * */

The two and a half minute's delay for counter collection has run out. Try again.

/ * ** N O A N SW E R F R O M C O U N T ER C O LL E CT I O N S Y S T E M * * * /

The counterpart (PUMMIT) does not respond to the inquiry sent by the

DXCMML. Re-enter the command. If the command execution still does not

succeed, the PUMMIT program may not be running. Restart the program.






/ ** * O PT IO N N OT I N U SE * ** /

The inquired measurement is optional and not in use.



17 (33)


2 TVO: OUTPUT COUNTERS

Function

With the TVO command you output the counter values of a BSC level clear code

measurement collected in the previous extra data collection. The extra collection

is activated every time you use the TVI command.

Parameters

measurement number:

call phase,BTS id type,BTS id,BTS name,destination cell type;

Syntax

B T S m e a s u re m e n t s

T V O : < me a s u r em e n t n u m b e r> : , ( | < BT S n a m e > ) ,< d e s t in a t i o n c e l l

type>...;

B S C m e a s u re m en t s (c a se 1 ) :

T V O : < me a s u r em e n t n u m b e r> ;


T V O : < me a s u r e me n t n u m b e r> : < c a ll p h a s e >;

BTS measurements is measurement number 47.



The corresponding names and measurement numbers are displayed in the

parameter guide. Below is an example of a parameter guide.



19 (33)

TVO: OUTPUT COUNTERS




measurement number

With this parameter you indicate the measurement whose

counter values you want to output. The names and the

corresponding numbers of the measurements are displayed in

the parameter guide. The measurement numbers are common

identifiers used in the BSC.

The possible values are 47, 48 and 49.

Example of a parameter guide:

/ * I D EN T IF Y M EA S UR E ME N T:

4 7 B SC L E V EL C L E AR C O D ES M M L (S ER LE V)

MEASUREMENT4 8 B SC L EV EL C LE AR C OD ES M ML (P M)

MEASUREMENT

4 9 B SC L EV EL C LE AR C OD ES M ML M E AS UR E ME NT

T H E P A RA M ET E R I S O B LI G AT O RY

*/

call phase With this parameter you indicate the phase or the phases of

the call transaction whose measurement results you want to

inquire. The names and the corresponding numbers of the

phases are displayed in the parameter guide.

The possible values range from 1 to 15. You can use the

grouping characters & and &&.

The parameter can have the following values:


CP 1 PAGING/INITIAL MS (CCCH

AND SDCCH OR TCH)

2 MM-SIGNALLING (SDCCH OR

TCH)

3 BASIC ASSIGNMENT (SDCCH

AND TCH)

4 RELEASE (SDCCH OR TCH)

5 FACCH ASSIGNMENT (TCH)






6 SMS-ESTABLISHMENT (TCH)

7 SMS-ESTABLISHMENT

(SDCCH)

8 CIPHERING (SDCCH OR TCH)

9 EXTERNAL HANDOVER






12 EXTERNAL HANDOVER






15 CONVERSATION (TCH)

The parameter is obligatory for BSC level clear code

measurement.

BTS id type With this parameter you indicate whether you identify the

BTS by its name or number.

The possible values are 1 and 2, where 1 means BTS id and 2

means BTS name.

BTS id With this parameter you indicate the BTS whose

measurement results you want to inquire. The possible values

range from 1 to 128 or 1 to 248 depending on the BSC

configuration. You can use the grouping characters & and &&

when you are inquiring the results of the BTS measurements.

BTS name With this parameter you indicate by name the BTS whose

measurement results you want to inquire. The name can

contain 1 to 15 characters. You can inquire the results of two

separate BTSs by using the grouping character &.



21 (33)




Destination Cell Type

With this parameter you indicate the type of destination cell

whose measurement results you want to inquire. The value

can be either 0 or 1.

0 = normal cell

1 = extended cell

Examples

1. Inquire and output counters of BSC LEVEL CLEAR CODES (PM)

measurement.

TVO:48;

2. Inquire and output updated counters in the BSC LEVEL CLEAR CODES

measurement in PAGING/INITIAL MS call phase.

TVO:49:1;

3. Inquire and output updated counters in the measurement BSC LEVEL

CLEAR CODES (SERLEV) MEASUREMENT in a BTS named KILO.

TVO:47:2,KILO,0;


The parameter guide and the semantic check are dynamic.

After the semantic check, the DXCMML sends a request for the counters of the

first object included in the inquiry. When the DXCMML receives the values of

the counters of the first object, it requests the counters of the other objects

sequentially. When the DXCMML receives the values of the counters of the last

object, it summarises the values of the counters and outputs all those counters

which have a value other than zero.

If another counter collection is running, the PUMMIT has to carry it out before it

can send an answer to the counter request sent by the DXCMML. In this case the

user is informed by an appropriate guide text and execution of the command caneither be aborted or continued.

Note

Successive output results may differ from each other because of periodical

counter collection.






Execution printouts

The execution printout for the command in example 2 (if there are counters that

have values) is the following:

M EA S I D: 4 9

MEAS NAME:BSC_CLEAR_MML_MEAS_C

P H A S E (S ) : 1 ,

PAGE 1


--------------------------------------------------------------------------

300 USER_ACT_BLOCK 1 301 NETW_ACT_BLOCK 2

302 BTS_FAIL_BLOCK 3 303 LAPD_FAIL_BLOCK 4

304 ABIS_FAIL_BLOCK 5 305 ABIS_MSG_CORRUP_TO_BTS 6

306 ASS_FAIL_MSG 7 307 BLOCK_SLAVE 8308 CH_ACT_NACK 9 309 CH_ACT_NACK_OM_INTER 10

310 CH_ACT_NACK_EQUIP_FAIL 1 1 311 CH_A CT_NA CK _EN CR YP_AL G 12

3 12 C H_ AC T_ NA CK _R AD _C H_ AL R_ A 1 3 3 13 C H_ AC T_ NA CK _S ER V_ NO T_ AV A 1 4

314 CH_ACT_FAIL 15 315 CONN_FAIL 1 6

3 16 C ON N_ FA IL _R AD _I NF _F AI L 1 7 3 17 C ON N_F AI L_R AD _LI NK _F AIL 1 8

318 CONN_FAIL_REM_TRANS_FAIL 19 319 DATA_IND_CORRUP 20

320 ERR_IND 21 321 E STA B_ IN D_F AI L 2 2

322 ESTAB_CONF_FAIL 23 323 HO_FAIL 2 4

324 HO_DETECT_FAIL 25 325 MODE_MOD_NACK 26

326 MODE_MOD_ACK_FAIL 27 32 7 NO_MEAS_RESULT 28

328 NO_RESP_FROM_COPRO 29 32 9 P HY _CONT _CONF _FAIL 30

330 RCS_ALG_START_ACK_FAIL 3 1 331 RCS_ ALG_C L_ ACK _F AIL 32

332 RC0_DISCO_IND 33 333 RF_CH_REL_ACK_FAIL 34

334 REL_IND 35 335 R EL_ IN D_ FAI L 36

PAGE 2


--------------------------------------------------------------------------

920 M_MS_NOT_EQIPPED 181 92 1 M_T R_COD_RAT_AD_UNAV 182

922 M_CIPH_ALG_NOT_SUPP 183 923 M _TE RR _CH AN _A LR_ AL LC 184

924 M_PROT_ERR_B_BSC_MSC 185 925 M _UN EX PEC TE D 1 86

926 M_INVALID_CELL 187 927 M_INVALID_MSG_CONT 1 88

928 M_IE_OR_FIELD_MISSING 1 89 929 M_IN CORRE CT_VA LU E 190

930 M_UNKNOWN_MSG_TYPE 191 931 M _UN KN OW N_I E 192

9 32 M _T RA NS C_ OR _R AT E_ UN AV AI L 1 93 9 33 M _C IP _T YP E_ MI TS MA TC H 1 94

934 M_SWITCH_CICUIT_POOL 195 935 M _SP EE CH_ VE RS ION _U NAV A 196


Abbreviations used in the execution printouts are:

MEAS ID= measurement identification

MEAS NAME= measurement name



23 (33)




NUM= index number of the counter

COUNTER= name of the counter

The execution printout, if there are no counters which have values, is the

following:

/ ** * N ON E O F T HE C OU NT E RS W A S U PD AT ED * ** /


The execution printout, if there is another collection running that is set by the

HSMMML (GSM Measurement Handling) or the OMC, is the following:

A N O TH E R C O UN T ER C O LL E CT I ON I S R U NN I NG . I T M I GH T T A KE T I ME

T O F IN I SH I T.

C O NF I RM E X E CU T IO N : Y / N ?


/ * ** B T S N O T E X I ST E NT * * * /

The name used to identify the BTS does not exist in the Radio Network Database.

Check the BTS name you have given. If the name was given correctly and the

same error message is repeated, the BTS may not exist in the network. Create the

BTS again. For more information on creating a BTS, see Base Tranceiver Station

Handling in BSC .

If some other error occurs, the general semantic error printouts of MML

commands are output. For more information, see General Notice Messages of

MML Session .


/ * ** C O UN T ER C O L LE C TI O N F A IL E D * * */

The counter collection set by the PUMMIT has failed. Re-enter the command. If

the command execution does not succeed, the PUMMIT program may not be

running. Restart the program.

/ * ** N O A N SW E R F R O M C O U N T ER C O LL E CT I O N S Y S T E M * * * /

The counterpart (PUMMIT) does not respond to the inquiry sent by the

DXCMML. Re-enter the command. If the command execution still does not

succeed, the PUMMIT program may not be running. Restart the program.

/ * ** C O UN T ER C O L LE C TI O N D I D N O T S U C C E ED I N G I VE N T I ME * * */






Another collection is running and the two and a half minutes' delay for the

counter collection has run out. Try again.

/ ** * O PT IO N N OT I N U SE * ** /

The inquired measurement is optional and not in use.



25 (33)


3 TVS: SHOW DESCRIPTION OF THE

COUNTERS

Function

With the TVS command you output the description of a specified BSC level clear

code measurement counter.

Parameters

counter number;

Syntax

T VS : < co un te r n um be r> ;


Counter number With this parameter you indicate the counter whosedescription you want to output.

The possible values are the following:


300-374 Clear cause counters set by the

ABIPRB (Abis Interface Program

Block).

400-408 Clear cause counters set by theRCSPRB (Radio Connection

Supervision Program Block).


HASPRB (Handover Attempt

Supervisor Program Block).


AIVPRB (A Interface Signalling

Program Block in BSC).



27 (33)

TVS: SHOW DESCRIPTION OF THE COUNTERS




RC0PRB (Resource Control

Program Block in BSC).

800-829 Clear cause counters set by theSC7PRB (Speech Circuit Control in

GSM BSC A Interface).


MSC.

51000-51154 Clear cause PM counters.

57000-57048 Clear cause SERLEV counters.

The parameter is obligatory.

Examples

1. Display the description of the global_reset counter.

TVS:606;

2. Display the description of the ho_fail counter.

TVS:323;


The DXCMML outputs a short description of the counter. There are also spare

numbers for the counters. In that case the DXCMML outputs the relevant

information.

Execution printouts

The execution printout of the command in example two (when there is a

description for the counter included in the inquiry) is the following:

C O U N T ER : 3 2 3 H O _ F A IL

DESCRIPTION:

T HE H A ND OV E R H AS B EE N F AI LE D A ND T HE M S R ET UR NS T O T HE S OU RC E C HA NN EL .T HE M S H AS S EN T A N A SS I GN ME N T F AI LU RE O R A H AN DO VE R F AI LU RE M ES SA GE T O T HE

N E TW O RK D U R IN G T H E H A ND O V ER .


The execution printout when the counter included in the inquiry is a spare

number, is the following:

C O U N T ER : S P A R E

DESCRIPTION:






/* NO DESCRIPTION

T HI S I S A SP AR E N UM BE R / *



If an error occurs, the general semantic error printouts of MML commands are

output. For more information, see General Notice Messages of MML Session,

Supplementary References.


The command has no execution error printouts.



29 (33)

TVS: SHOW DESCRIPTION OF THE COUNTERS

4 TVR: RESET THE COUNTERS

Function

With the TVR command you reset the counters of a cumulative BSC level clear

code measurement or measurements.

Parameters

measurement type:

measurement id;

Syntax

T V R : < me a s u r em e n t t y p e > : [< m e a s ur e m e n t i d > ] ;


measurement typeWith this parameter you indicate the measurement group

whose measurement(s) you want to reset.

The only possible value for the parameter is 2, which

indicates the cumulative measurements.


measurement id With this parameter you indicate the cumulative measurement

whose counters you want to reset. Give this parameter only

for the cumulative measurements.

The possible values are 0, 1, 2 or 3.


MI 0 Reset counters of all cumulative

measurements.



31 (33)

TVR: RESET THE COUNTERS



1 Reset the counters of BSC clear

code measurement.


code (PM) measurement.


code (SERLEV) measurement.


Examples

1. Reset the counters of all cumulative measurements.

TVR:2:0;2. Reset the counters of BSC clear code measurement.

TVR:2:1;


After you have selected the cumulative measurements, the counters are reset by

sending message 6078 with the reset information. The PUMMIT resets the

counter data of the measurement and sends the acknowledgement message 6031

to the DXCMML.

Note

When the ZTVR command is executed, it resets the counter values only in

PUMPRB memory area, not in RCGSTA. So if the ZTVI command succeeds

after ZTVR, it is not a malfunction since the RCGSTA memory might not be

empty. ZTVI fails only if the RCGSTA memory area is empty as well since then

there is nothing to collect to the PUMPRB memory. Instead of ZTVI, the

command ZTVO should be used to verify PUMPRB memory area reset since it

does not initiate counter collection.

Note

Because the results of periodical measurements are used by the OMC, they

cannot be reset.







/ ** * C OU NT ER S C AN N OT B E R ES ET

TRY AGAIN ***/

The counter reset has failed because the PUMMIT does not handle the reset or the

PUMMIT does not answer the request. Try again.

TVR: RESET THE COUNTERS

BSC Counter Inquiry

Documents

Transcript of BSC Counter Inquiry