Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Lolck

    Table 1: Alarm Details

    Parameter

    Description

    Code

    lolck

    Description

    Loss of Lock: The optical channel cannot lock on to the encoded signal received.

    Entities Affected

    Optical channel interfaces (see respective table below).

    Possible Causes

    • The encoding, modulation, or other configured parameter on the interface at the far-end NE does not match the configuration of the same parameter of the interface at the local NE.
    • The signal-to-noise ratio is below specification.

    Default Severity

    Critical

    Service Affecting

    Yes (true).

    Alarm Clearing

    See Clearing a Lolck alarm.

    Related Fault Hierarchy

    See Common fault hierarchy - OTN and CBR ports.

    Table 2: Optical Channel Interfaces

    Entity Name

     

    Fault Indicator

    Module

    Indicator

    Status

    och:<chassis>/<slot>/<2>/<1>/<subport.och>

    UFM6

    Fault LED, 200G line port

    On

    Clearing a Lolck Alarm

    Note: Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide.

    1. Retrieve information for both the local and far-end optical channel interfaces to view configuration data:
      show interface och:identifier detail
    2. Correct the configuration settings where required. For information, see the BTI7800 Series Software Configuration Guide.
    3. Retrieve statistics for the local and far-end optical channel interfaces to view the values of all optical signal-to-noise ratio counters, and ensure that the OSNR is within specification.
      show statistics current och:identifier
    4. If required, improve the signal-to-noise ratio.
    5. Check for alarms on the local interface.
      • If the alarm clears, you have completed this procedure.
      • If the alarm does not clear, contact your next level of support.

    Modified: 2017-07-06