Thanks Thanks:  1
Showing results 1 to 4 of 4

Thread: rrc failure in huawei due to processor load

  1. #1
    Member Reputation: 78
    Join Date
    2009-10-27
    Posts
    194


    Default rrc failure in huawei due to processor load

    hello dears

    is there any counter to measure rrc failure due high processor load in huawei RAN13 & RAN15

  2. # ADS
    Circuit advertisement
    Join Date
    Always
    Posts
    Many
     

  3. #2
    Junior Member Reputation: 10
    Join Date
    2013-12-15
    Posts
    4


    Default Re: rrc failure in huawei due to processor load

    I have same question.

  4. #3
    Member Reputation: 58
    Join Date
    2010-01-07
    Posts
    64


    Default Re: rrc failure in huawei due to processor load

    If you have hedex, read topic "flow control". You can find all the counters related to RRC rejection due to high XPU load.

    Other way, (Total RRC rejection - (RRC rej due to CE + RRC rej due to IUB + RRC rej due to Code + RRC rej due to Power))

  5. Thanks gunpowder thanked for this post
  6. #4
    Member Reputation: 114
    Join Date
    2012-09-07
    Posts
    41


    Lightbulb Re: rrc failure in huawei due to processor load

    Hi,
    Actually this is very interesting topic and I am currently working at such problem.

    In the initial post it is not clear about which CPU high load there is a talk - WMPT board(NodeB side) or SPU (RNCside).
    Both cases can be present.
    1) WMPT board overload - can be measured with NodeB counters VS.BRD.CPULOAD.MEAN, VS.BRD.CPULOAD.OVER.
    If the mean load higher than 65-70% there is a possibility that NodeB is not processing all the RRC requests successfully. Here you should pay attention to the counter VS.RlSetup.Reject.CP.Cong, which is showing total number of radio link setup rejections in the NodeB due to congestion on the control plane, that is, CPU overload. Also you can refer to E2E Flow control feature description - there are a lot of details there.
    2) SPU board overload - as it is already mentioned above - good described in features Flow control. If it is enabled you can refer to counters:
    - VS.RRC.FC.Num.CPU.OverLoad
    - VS.RRC.FC.Num.CPU.CPUS
    One important thing - usually Flow control and E2E Flow control algorithms turned off by default, so my suggestion (if you don't want to enable this feature as they are actually not very good for KPIs) - make CPU load monitoring periodically and expand capacity or perform another actions in time
    For SPU load use counter - VS.XPU.CPULOAD.MEAN.

    Best regards!

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
  •