Page 2 of 2 FirstFirst 12
Showing results 11 to 15 of 15

Thread: Huawei CDMA BSC6680 and Neighboring Cell Measurement Tracing?

  1. #11
    Member Reputation: 78
    Join Date
    2009-01-23
    Posts
    99


    Default Re: Huawei CDMA BSC6680 and Neighboring Cell Measurement Tracing?

    Quote Originally Posted by T_ADD View Post
    What tool do you use to analyse the NBRSTATRACE.dat file?
    That is the question I also want to know it

  2. #12
    Member Reputation: 730
    Join Date
    2011-04-12
    Posts
    633


    Default Re: Huawei CDMA BSC6680 and Neighboring Cell Measurement Tracing?

    Looking forward to more info on NBRSTATRACE, DANCESTORM.
    Edify...

  3. #13
    Member Reputation: 16
    Join Date
    2011-03-04
    Posts
    19


    Default Re: Huawei CDMA BSC6680 and Neighboring Cell Measurement Tracing?

    Hello everyone, I need material on CDMA BSC6900 cell measurement tracing

  4. #14
    Member Reputation: 264
    Join Date
    2012-01-26
    Posts
    311


    Default Re: Huawei CDMA BSC6680 and Neighboring Cell Measurement Tracing?

    I get this Info about NBRSTAT but I still didn't know the diffrence between this and The PSMMTRACE command
    For me I used to use SET PSMMTRACE.

    Set Neighboring Cell Measurement Tracing

    Command Name
    SET NBRSTAT
    Description
    This command is executed to set the neighbor cell statistics task.

    Remarks

    1. The neighbor cell statistics task does not support task append. Only one task can be started each time. When you need to start a new task, you must stop the original task and clear the directory for saving neighbor cell statistics files. The default path is F:\cdma2000\TRACE\NBRSTAT\NBRSTATRACE.dat.
    2. If you start the statistics task when the system load is heavy, this may increase the system load. Therefore, be careful to use this function.
    3. If the system performs flow control, any data reported at the moment is not measured.
    4. When the statistics task is on the go, if the active SPU of a specified module is reset or switched over, the task of this module does not stop.
    5. The information of different frequency in the ROUTE UPDATE message is not measured.
    6. You can start the neighbor cell statistics task for the specified model. However, when you stop a statistics task, the task of all modules configured stops.
    7. After the statistics task is started, a tracing data file is generated and saved in the corresponding directory. The file is in the lock state before the task stops. You cannot delete, move, or modify it.
    8. The statistics task reports the collected data at 2:20 every morning. After that, clear the counter of neighbor cell object.
    9. The current file of neighbor cell statistics is backed up at 3:00 every morning. The backup file is also in the lock state till the task stops.
    10. You can execute the forcible report command to obtain the data of the current neighbor cell object. After the data is reported, do not clear the counter. Every time you execute the forcible report command, a data file is generated in the corresponding neighbor cell statistics file directory. This file is unlocked, and you can delete it at any time.

    1111.jpg





    Examples
    Example 1: Start the neighbor cell statistics task. Subrack number: 2; Slot number: 2; SPUO subsystem number: 0; NbrSystem Type: PARA0(1X); NbrFreq Type: PARA0(IDENTITY CARRIER); NbrCfg Type: PARA1(NOT CONFIGURED); Trace Time(day): 2.
    SET NBRSTAT: SWITCH=START, FSS="2&2&0", NBRSYSTYE=PARA0, NBRFREQTYE=PARA0, NBRCFGTYE=PARA1, DURATION=2;
    Example 2: Stop the neighbor cell statistics task.
    SET NBRSTAT: SWITCH=STOP;

    Related Commands

    Query Neighbor Cell Statistics Task Information DSP NBRSTAT
    Upload Neighbor Cell Statistics Data Forcibly UPD NBRSTAT
    Last edited by hamody2005; 2013-01-24 at 06:18 AM

  5. #15
    Member Reputation: 264
    Join Date
    2012-01-26
    Posts
    311


    Default Re: Huawei CDMA BSC6680 and Neighboring Cell Measurement Tracing?

    I have exp. with three vendor (ZTE,Huawei,LG_lucent), Huawei is worst one With NBR tracing for this reason:-
    1. The BSC can't Trace All PSMM from all user.
    2. They use special software to do the analysis .
    3. The result isn't accurate, you must review before Adding missed NBRs or (Call drop will increase).
    4. you cant get the PSMM at any time (you must start PSMMTRACE before).
    5. They ask for large number($) for a PSMM analysis tool wherein the other is included it in basic function of BS
    6. The result is just Indicator it doesn't reveal the accurate number.

Bookmarks

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •