Login
    Contents x
    Managing Alarms
    • 14 Apr 2022
    • 10 Minutes to read
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Contents

    Managing Alarms

    • Updated on 14 Apr 2022
    • 10 Minutes to read
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Article Summary

    The Skylight sensor: control provides alarm functions to monitor and report on the status of the unit, of the traffic performance and of other components.

    Setting General Alarms


    To set up general alarms

    1. Access the page System ▶ Alarm ▶ General.

    2. Complete the required fields, then click Apply.

      Note: If you modify the alarm settings and then decide to discard those changes, click the Reset button to revert to the last set of saved settings. However, once you have clicked Apply, previous settings can only be restored manually.

    For more information on specific parameters, refer to the following table.

    Alarm Settings (System ▶ Alarm ▶ General)

    1. Click the Number of the alarm that you want to edit.

      The Alarm Configuration page appears.

    2. Complete the required fields, then click Apply.

    Note: If you modify an alarm's configuration, then decide to discard those changes, click Reset to revert to the last set of saved configuration values. Once you click Apply, however, you must manually restore the previous configuration values.

    For more information on specific parameters, refer to the following table.

    Alarm Configuration (System ▶ Alarm ▶ Configuration)

    ParameterDescription
    NumberThe unique number that identifies this alarm. This number is assigned by the Skylight sensor: control and cannot be modified.

    This alarm number is composed of four fields, the remote device ID, the module number, the instance number and the error number. The format is DDDD.AA.BBBB.CC, where the parameters are as follows:

    • DDDD: Remote device ID (0-1500). For Skylight sensor: control local alarms, DDDD is 0.
    • AA: Module number (1-99)
    • BBBB: Instance number (0000-9999).
    • CC: Error number (01-99)

    A module number is assigned for each alarm in the system.

    EnableIndicates whether the alarm is enabled (true) or disabled (false). If enabled, alarms are reported.
    SeverityThe severity of the alarm.
    • Informational: No effect on service. Provides status information.
    • Minor: An error condition has occurred that does not seriously affect system functionality.
    • Major: A serious degradation of service or hardware malfunction has occurred which requires immediate attention to restore system functionality.
    • Critical: A service affecting condition has occurred that requires immediate corrective action.
    Service AffectingAlarms may be displayed as true for service affecting or as false for non-service affecting.
    Device NameName of the device against which the alarm is raised.
    DescriptionTextual description of the alarm. The description is displayed in the Show ▶ Alarm page.

    Viewing Alarms

    This article explains how to view alarms and provides a list of all supported alarms and their default description.

    To view the status of an alarm

    1. Access the page Show ▶ Alarm.

      The alarm status is displayed.

    2. Click the Number of any alarm to show detailed information about that alarm.

    3. Filter the Alarms from the drop-down menu (Number, Presence, Severity, Device Name, Description) and click the Search button.

      The resulting alarms are displayed.

      Note: Enter an asterisk ( * ) as a wildcard to replace one or several characters.

    For more information on specific parameters, refer to the following table.

    Alarm Status (Show ▶ Alarm)

    ParameterDescription
    StatusThe status LED is ON if the alarm is enabled and has been triggered.
    NumberThe unique number identifying this alarm. This number is assigned by the Skylight sensor: control and cannot be modified.

    This alarm number is composed of four fields, the remote device ID, the module number, the instance number and the error number. The format is DDDD.AA.BBBB.CC, where the parameters are as follows:

    • DDDD: Remote device ID (0-1500). For Skylight sensor: control local alarms, DDDD is 0.
    • AA: Module number (1-99)
    • BBBB: Instance number (0001-9999).
    • CC: Error number (01-99)

    A module number is assigned for each alarm in the system.

    PresenceIndicates whether the alarm is currently present (true) or not (false).
    SeverityThe severity of the alarm. Possible values: <UL
  • Informational: No effect on service. Provides status information.
  • Minor: An error condition has occurred that does not seriously affect system functionality.
  • Major: A serious degradation of service or hardware malfunction has occurred which requires immediate attention to restore system functionality.
  • Critical: A service-affecting condition has occurred that requires immediate corrective action.
    • Device NameName of the device against which the alarm is raised.
    Service AffectingIndicates whether the alarm affects the unit's ability to provide service.

    Possible values:

    • yes: The alarm is Service Affecting (SA)
    • no: The alarm is Non-Service Affecting (NSA)
    DescriptionA textual description of the alarm.
    MessageThis is displayed only when the alarm has changed status (the alarm was turned ON or OFF). The message explains why it was turned on or off, e.g. temperature was above the threshold.
    Last ChangeWhen the alarm changed status.

    Refer to the following table for a list of all alarms supported and their default description.

    Supported Alarms: Skylight sensor: control

    Port related alarms
    In this section, aaaa = Port Identifier.

    NumberDefault Description
    dddd.1.aaaa.01Link down on PORT
    dddd.1.aaaa.06Port speed mismatch on port

    SFP related alarms
    In this section, aaaa = Port Identifier.

    NumberDefault Description
    dddd.2.aaaa.01SFP- temperature high alarm
    dddd.2.aaaa.02SFP- temperature low alarm
    dddd.2.aaaa.03SFP- temperature high warning
    dddd.2.aaaa.04SFP- temperature low warning
    dddd.2.aaaa.05SFP- supply voltage high alarm
    dddd.2.aaaa.06SFP- supply voltage low alarm
    dddd.2.aaaa.07SFP- supply voltage high warning
    dddd.2.aaaa.08SFP- supply voltage low warning
    dddd.2.aaaa.09SFP- laser bias current high alarm
    dddd.2.aaaa.10SFP- laser bias current low alarm
    dddd.2.aaaa.11SFP- laser bias current high warning
    dddd.2.aaaa.12SFP- laser bias current low warning
    dddd.2.aaaa.13SFP- transmit power high alarm
    dddd.2.aaaa.14SFP- transmit power low alarm
    dddd.2.aaaa.15SFP- transmit power high warning
    dddd.2.aaaa.16SFP- transmit power low warning
    dddd.2.aaaa.17SFP- receive power high alarm
    dddd.2.aaaa.18SFP- receive power low alarm
    dddd.2.aaaa.19SFP- receive power high warning
    dddd.2.aaaa.20SFP- receive power low warning
    dddd.2.aaaa.21SFP- not present

    CFM related alarms
    In this section, zzzz = CFM instance index.

    NumberDefault Description
    0.4.zzzz.01RDI on down MEP, MEPID , port , VID , level <#>
    0.4.zzzz.03Remote CCM on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.01RDI on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.02MAC status on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.03Remote CCM on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.04Errored CCM on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.05Cross-connected CCM on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.06AIS on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.07One-way delay on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.08One-way average delay on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.09One-way delay variation on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.10One-way average delay variation on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.11Two-way delay on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.12Two-way average delay on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.13Two-way delay variation on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.14Two-way average delay variation on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.15Excessive packet loss on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.19Excessive SLM near end packet loss on down MEP, MEPID , port , VID , level <#>
    dddd.4.zzzz.20Excessive SLM far end packet loss on down MEP, MEPID , port , VID , level <#>

    SyncE related alarms

    NumberDefault Description
    dddd.06.0001.06SyncE Clock: Cannot synchronize to SyncE clock source

    System modules related alarms

    NumberDefault Description
    dddd.06.zzzz.10NTP client lost server communication
    dddd.06.zzzz.30Time-of-day synchronization – May affect delay measurements
    0.7.0004.01VCAgent communication failure with Vision EMS
    0.7.0004.26VCAgent High resolution flowmeter instances validation
    0.7.0004.27VCAgent High Resolution flowmeter statistics buffer full

    Remote devices related alarms

    NumberDefault Description
    dddd.8.0001.03Remote Device no power supply on secondary feed
    dddd.8.0001.30Remote Device temperature sensor not present
    dddd.8.0001.31Remote Device high-temperature warning
    dddd.8.0001.32Remote Device high-temperature Alarm
    dddd.8.0001.40Remote Device FAN 1 not present
    dddd.8.0001.41Remote Device FAN 1 stall alarm
    dddd.8.0001.42Remote Device FAN 1 fan-aging warning
    dddd.8.0002.40Remote Device FAN 2 not present
    dddd.8.0002.41Remote Device FAN 2 stall alarm
    dddd.8.0002.42Remote Device FAN 2 fan-aging warning

    Loss of connectivity with a remote device related alarms

    NumberDefault Description
    dddd.10.aaaa.01Loss of connectivity with
    dddd.10.aaaa.02Device type mismatch with
    dddd.10.aaaa.03Device sent Dying Gasp
    dddd.10.aaaa.04Device override configuration required

    Flow broker related alarms
    In this section, xxxx= Packet Engine Instance.

    NumberDefault Description
    dddd.14.xxxx.01flow broker packet engine server New, connection with client lost (xxxx= Packet Engine Instance)
    0.15.xxxx.01flow broker Analyzer server New1, connection lost (xxxx= Analyser Instance)

    License Server alarms

    NumberDefault Description
    0.16.0000.03Missing one anchor
    0.16.0000.04Missing multiple anchors, licensing function degraded
    0.16.0000.05Missing multiple anchors, licensing function offline
    0.16.0000.07Clock-Windback detected, licensing function degraded
    0.16.0000.08Clock-Windback detected, licensing function offline
    0.16.0000.09Communication loss detected, licensing function degraded
    0.16.0000.10Communication loss detected, licensing function offline
    0.16.0000.11License acquisition process down

    Certificate alarms

    NumberDefault Description
    0.19.1.1One or more certificates is about to expire
    0.19.1.2One or more certificates has expired

    Viewing Chassis Alarms

    To view the status of remote devices chassis-related alarms and information, including power supplies, temperature sensors and fan status

    1. Access the page System ▶ Alarm ▶ Chassis.
      The remote devices chassis' status is displayed.

    For more information on specific parameters, refer to the following table.

    Remote device chassis status and alarms (System ▶ Alarm ▶ Chassis)

    Power Supplies

    ParameterDescription
    Power Feed A and Power Feed BThe status of the power sources for a DC Powered unit: Feed A and Feed B.
    • The Feed B indicator is always green when power to the unit is connected. The Feed B indicator DOES NOT indicate that a feed is connected to the Feed B input.
    • The DC Feed A and DC Feed B lights indicate which DC feeds are in use.
    • A green light indicates that the power source is connected and is operating normally.
    • A red light indicates that the power source is not connected or is not operating normally.

    Temperature Sensors

    ParameterDescription
    PHY, CPU and FPGA Temperature SensorsThe following information is provided for each sensor (PHY, CPU and FPGA):
    • Status: Either Present or Not Present
    • Alarm: Set to In Alarm (if an alarm has been triggered) or None
    • Temperature: The most recent temperature detected by the sensor, expressed in Celsius
    • High-Temperature Warning: The temperature that triggers an overheating warning, expressed in Celsius
    • High-Temperature Alarm: The temperature that triggers an overheating alarm, expressed in Celsius
    • Low Temperature Warning: The temperature that triggers a low temperature warning, expressed in Celsius
    • Low-Temperature Alarm: The temperature that triggers a low-temperature alarm, expressed in Celsius

    For details on any alarms or warnings, access the page Show ▶ Alarm.

    Fan Monitors

    ParameterDescription
    Fan 1 and Fan 2For each fan on the unit (identified as 1 or 2), the following information is provided:

    Status:

    • Present: The fan is connected.
    • Not Present: The fan is not connected.

    Alarm:

    • In Alarm: An alarm has been triggered for this fan.
    • None: No alarm has been triggered for this fan.

    Speed:

    • This the number of rotations per minute made by the fan, expressed in RPM.

    The following threshold information is provided for each fan:

    • Fan-Stall Alarm: This is the fan speed at which the fan stall alarm is triggered, indicating that the fan is no longer functioning. Expressed in RPM.
    • Fan-Aging Warning: This is the fan speed at which the fan aging warning is triggered, indicating that the fan is no longer functioning optimally. Expressed in RPM. Fan-Aging Alarm: This is the fan speed at which the fan aging alarm is triggered. Expressed in RPM.

    For details on any alarms or warnings, access the page Show ▶ Alarm.

    Dying Gasp Alarm

    The Dying Gasp feature is supported on Skylight sensor: module 1G only. The Skylight sensor: SFP compute 1G does not support Dying Gasp since it relies on the SFP host to generate the Dying Gasp.

    Before losing power, at least three Dying Gasp layer-2 defined in 802.ah are sent on both the UNI and NNI ports. Also, a proprietary Dying Gasp message is sent on the management connection from the NNI port towards Skylight sensor: control to raise the Dying Gasp alarms. The Dying Gasp alarm is cleared in Skylight sensor: control when the device is linked.

    © 2024 Accedian Networks Inc. All rights reserved. Accedian®, Accedian Networks®,  the Accedian logo™, Skylight™, Skylight Interceptor™ and per-packet intel™, are trademarks or registered trademarks of Accedian Networks Inc. To view a list of Accedian trademarks visit: http://accedian.com/legal/trademarks/. 

    Was this article helpful?
    What's Next
    Get In Touch
    Learn
    About Us
    Change password!
    Changing your password will log you out immediately. Use the new password to log back in.
    Change profile
    Success!
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.
    Logout