CS Core & PS Core Optimization Interest Group

CS Core & PS Core Optimization Interest Group

4,258 members
  • Join

    When you join a group, other members will be able to see your profile and message you. The group logo will be visible on your profile unless you change that setting.

  • Information and settings

Have something to say? Join LinkedIn for free to participate in the conversation. When you join, you can comment and post your own discussions.

Anbu

HUAWEI : Cause Value / Cause Code Display Manager's Choice

CanGo Networks

ZTUT: CLR; , Ericsson EOS is quite familiar to most of you all. It is easy to get the current value of EOS/ Clear Code from both NSN/Ericsson switches.

Do we have anything to get the current CV (Cause Code/Value) of Huawei Switches?

Something like DSP CV??

Currently,I see most of the operators loading OSS (M2000) through queries to get the values.

  • Comment (24)
  • August 18, 2011
  • Close viewer

Comments

  • Adanel G.

    Adanel

    Adanel G.

    Expert at Globe Telecom

    that's also our concern when it comes to the MSOFT platform..
    There's no command to display the current cause values. you have to fetch it in the M2000.

  • Rauf A.

    Rauf

    Rauf A.

    Technical Manager at Digicel

    With respect, I don't agree with you here.

    For troubleshooting, you can get the cause value from traces, for reading you can get complete list of cause values from Huawei Performance KPI reference manual. For O&M there are many commands in MSOFTX for listing cause value, toneIds corresponding to each cause value, mapping protocol cause value with custom one etc etc. Few of them are given below:
    LST CST
    LST CAUSETONE
    LST CAUSECHG
    LST CVTCAU
    LST CVTSIPCAU ------------ SIP Cause Conversions

    I hope it helps and clears this misconception.

  • Adanel G.

    Adanel

    Adanel G.

    Expert at Globe Telecom

    He's asking for the command to display the current count like the ZTUT of NSN.. I think the commands you've given is for cause code mapping purposes. :)

  • Anbu G.

    Anbu

    Anbu G.

    CanGo Networks

    Thanks Rauf, as Adanel mentioned it is a useful one to map the cause code.RANAP, DTAP, BSSAP etc.,

  • Muhammad S.

    Muhammad

    Muhammad S.

    Manager Performance Management Team – NOC at Mobilink

    Hi Anbu, yes there is nothing like TUT:CLR in Huawei MML, but as a comparable solution on Huawei side can be placed by setting of performance measurement for Global-Failure-Causes for 15 minutes interval. TUT:CLR also gives cumulative value of 15 mins. So this will be a comparable solution but not exactly like NSN CLR

    One thing I must mention here that NSN-Clear Codes are more comprehensive than Huawei Release Causes. (This is my personnel understanding on my experience). It does not mean that NSN is better of Huawei is weaker but actually the architecture and monitoring styles of both switches are different. NSN architecture is based on Clear Codes but Huawei is based on performance measurements. Also note that Huawei Imanager is much faster and friendly than NSN-netact. So it’s very easy to trace problems in Huawei by using Imanager. Even without Imanager the performance measurements can be fetched using Local Maintenance tool (LMT) that is equally easy and friendly.

    I hope this will add little clarity.

  • Anbu G.

    Anbu

    Anbu G.

    CanGo Networks

    Hi Muhammad,

    Thanks for your detailed explanation. I agree with you on the architecture and ease of use. Well, I see a draw back though when it comes to Failure Cause analysis. (My personal view and could be my ignorance)

    Do you have the experience of turning on the trace for a particular Cause Value (Say 175) and capturing more details about it similar to the Clear Code (NSN) or EoS (Ericsson).

    Without this trace feature, I see no value addition in having Failure cause measurement.

    Rauf, Adanel,

    Please feel free to share your experiences as well.

  • Muhammad S.

    Muhammad

    Muhammad S.

    Manager Performance Management Team – NOC at Mobilink

    Hi Anbu, Unfortunately I have not found any procedure so far to capture more signaling details about a specific Failure Cause like OBSFAILA in NSN. Yes this is making troubleshooting more difficult in Huawei Nodes. I believe Huawei have some separate solution for capturing this but that will require additional CAPEX. Huawei sales team can provide more info regarding this.

Have something to say? Join LinkedIn for free to participate in the conversation. When you join, you can comment and post your own discussions.

Feedback