Scribd Logo
Upload

Welcome to Scribd!

  • Wrong Parameter Set in NQ2 Lead To ODU0 - PM - SSF Alarm of TOG

    Uploaded by

    Maggie Kloss
    12 views2 pages
    1. A TN52TOG and TN54NQ2 placed in an OSN8800 reported an ODU0_PM_SSF alarm after configuring an ODU0 between them. 2. Checking the NQ2 parameters revealed the Line Rate mode was set to Speedup Mode instead of Normal Mode. 3. Changing the NQ2 Line Rate mode from Speedup to Normal cleared the alarm, as the Speedup Mode violated the G.709 protocol by mapping ODU0 to ODU2e to OTU2v.

    Original Description:

    Original Title

    Wrong parameter set in NQ2 lead to ODU0_PM_SSF alarm of TOG

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    1. A TN52TOG and TN54NQ2 placed in an OSN8800 reported an ODU0_PM_SSF alarm after configuring an ODU0 between them. 2. Checking the NQ2 parameters revealed the Line Rate mode was set to Speedup Mode instead of Normal Mode. 3. Changing the NQ2 Line Rate mode from Speedup to Normal cleared the alarm, as the Speedup Mode violated the G.709 protocol by mapping ODU0 to ODU2e to OTU2v.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    12 views2 pages

    Wrong Parameter Set in NQ2 Lead To ODU0 - PM - SSF Alarm of TOG

    Uploaded by

    Maggie Kloss
    1. A TN52TOG and TN54NQ2 placed in an OSN8800 reported an ODU0_PM_SSF alarm after configuring an ODU0 between them. 2. Checking the NQ2 parameters revealed the Line Rate mode was set to Speedup Mode instead of Normal Mode. 3. Changing the NQ2 Line Rate mode from Speedup to Normal cleared the alarm, as the Speedup Mode violated the G.709 protocol by mapping ODU0 to ODU2e to OTU2v.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 2

    Wrong parameter set in NQ2 lead to

    ODU0_PM_SSF alarm of TOG


    Publication Date:  2012-07-25 Views:  0 Downloads:  0 References:  0

    Issue Description

    A TN52TOG and TN54NQ2 placed in slot16 and slot5 of OSN8800

    (V100R002C02SPC800), the TN52TOG report ODU0_PM_SSF alarm

    after configuring ODU0 between TN52TOG and TN54NQ2.The

    service is interrupted.

    Alarm Information

    TN52TOG report ODU0_PM_SSF alarm

    Handling Process

    1 Checked alarm, had no the other alarms in this NE.

    2 Checked the parameter of NQ2; we found the Line Rate mode is

    Speedup Mode. Changed the parameter from     Speedup Mode to

    Normal Mode, the ODU0_PM_SSF alarm disappeared. The service is

    OK.

    Root Cause

    1 R-LOS,ODUk_TCMn_SSF, ODUk_TCMn_LCK, ODUk_TCMn_OCI,

    ODUk_TCMn_AIS, ODUk_TCMn_LTC, ODUk_TCMn_TIM or OTUk_TIM


    cause ODU0_PM_SSF.

    2 the wrong parameter set in NQ2.

    Suggestions

    According to G.709 protocol, OUD0 service cannot map from ODU0

    ---> ODU2e ---> OTU2v, so the Speedup Mode  of NQ2  lead to

    ODU0_PM_SSF alarm of TOG.

    You might also like