--- title: "Manage Alarms" slug: "managing-alarms-lt" tags: ["alarm", "management", "assurance sensor 24.07", "Assurance Sensors", "Assurance Sensor LT-S"] updated: 2026-11-05T16:40:37Z published: 2026-11-05T16:40:37Z canonical: "docs.crossworkassurance.cisco.com/managing-alarms-lt" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.crossworkassurance.cisco.com/llms.txt > Use this file to discover all available pages before exploring further. # Manage Alarms The unit 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**. For more information on specific parameters, refer to the following table. **Alarm Settings (System ▶Alarm ▶General)** **Notification** | Parameter | Description | | --- | --- | | Enable LED Reporting | Enables the reporting of alarms by activating the appropriate LED on the unit that corresponds to the severity, e.g. minor, major or critical. This option also enables alarm reporting in the GUI banner. The physical LEDs (unit's front panel) and the pseudo-LEDs (banner) are linked. | | Enable Syslog Reporting | Enables the reporting of alarms by creating entries in the syslog. | | Enable SNMP Reporting | Enables the reporting of alarms via SNMP traps from Cisco's private MIB. | | Enable 802.3ah Reporting | Enables reporting of alarms via 802.3ah OAMPDUs using organization-specific events. | **Thresholds** | Parameter | Description | | --- | --- | | Threshold On (Soaking time in msecs) | The delay after an event is detected before the alarm notification occurs. | | Threshold Off (Soaking time in msecs) | The delay after an event clears before the alarm notification clears. | ### Customizing Alarms **To customize an alarm** 1. Access the page **System ▶Alarm ▶Configuration**. The settings for all alarms are displayed. 2. Click the **Number** of the alarm that you want to edit. The Alarm Configuration page appears. 3. 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)** | Parameter | Description | | --- | --- | | Number | The unique number that identifies this alarm. This number is assigned by the unit and cannot be modified. This alarm number is composed of three fields, the module number, the instance number and the error number. The format is AA.BBBB.CC, where the parameters are as follows: - **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 and may be one of the following: - **1:** Port module for link down and other related alarms - **2**: SFP module for Rx/Tx power, temp, VCC and LBC alarms and warnings - **3**: PAA module for Continuity Check, Delay, Frame Loss and other related alarms - **4**: SOAM module for Continuity Check, Delay, Packet Loss and other related alarms - **5**: Unassigned - **6**: Synchronization, including NTP, PTP and GPS - **6**: SyncE (LT-S only) - **7**: System modules, such as NTP and other agents - **7**: System modules, such as the Vision Collect Agent and other agents - **8**: Environmental module for power supplies, temperature sensors and dry contact - **9**: ERP module - **10**: Unassigned - **11**: TWAMP - **12**: Unassigned - **13**: Loop detection - **14**: flow broker - **14**: Unassigned - **15**: Unassigned - **16**:Unassigned - **17**: Unassigned - **18**:Unassigned | | Enable | Indicates whether the alarm is enabled (true) or disabled (false). If enabled, alarms are reported. | | Severity | The 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 that requires immediate attention to restore system functionality. - **Critical:** A service-affecting condition has occurred that requires immediate corrective action. If LED reporting is enabled in the **Alarm ▶General** page, the Minor, Major and Critical alarms are indicated on the unit's front panel LEDs. | | Service Affecting | Alarms may be displayed as true for **service affecting** or as false for **non-service affecting**. | | Description | Textual description of the alarm. The description is displayed in the **Show ▶Alarm** page. ***Note:** This description cannot be modified.* | ### Viewing Alarms **To view the status of an alarm** 1. Access the page **Show ▶Alarm** The alarm status is displayed. For more information on specific parameters, refer to the following table. **Alarm Status (Show ▶Alarm)** | Parameter | Description | | --- | --- | | Status | The status LED is ON if the alarm is enabled and has been triggered. | | Number | The unique number identifying this alarm. This number is assigned by the unit and cannot be modified. This alarm number is composed of three fields, the module number, the instance number and the error number. The format is AA.BBBB.CC, where the parameters are as follows: - **AA:** Module number (1–99) - **BBBB:** Instance number (0001–9999). - **CC:** Error number (01–99) | | Presence | Indicates whether the alarm is currently present (**true**) or not (**false**). | | Severity | The severity of the alarm. Possible values: - **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 that requires immediate attention to restore system functionality. - **Critical:** A service-affecting condition has occurred that requires immediate corrective action. | | Service Affecting | Indicates 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). | | Description | A textual description of the alarm. | | Message | This 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 Change | When the alarm changed status. | Refer to the following table for a list of all alarms supported and their default description. **Supported Alarms: Cisco® LT-S** **Port module for link down and other related alarms Cisco LT-S** | Parameter | Default Description | | --- | --- | | 1.0001.01 | Link down on PORT-1 port | | 1.0001.02 | Loopback on port PORT-1 | | 1.0001.04 | Fault propagation caused link down on port PORT-1 | | 1.0002.01 | Link down on PORT-2 port | | 1.0002.02 | Loopback on port PORT-2 | | 1.0002.04 | Fault propagation caused link down on port PORT-2 | | 1.0003.01 | Link down on PORT-3 port | | 1.0003.02 | Loopback on port PORT-3 | | 1.0003.04 | Fault propagation caused link down on port PORT-3 | | 1.0004.01 | Link down on PORT-4 port | | 1.0004.02 | Loopback on PORT-4 | | 1.0004.04 | Fault propagation caused link down on port PORT-4 | | 1.0005.01 | Link down on PORT-5 port | | 1.0005.02 | Loopback on port PORT-5 | | 1.0005.04 | Loopback on port PORT-5 | | 1.0006.01 | Link down on PORT-6 port | | 1.0006.02 | Loopback on port PORT-6 | | 1.0006.04 | Fault propagation caused link down on port PORT-6 | | 1.0007.01 | Link down on PORT-7 port | | 1.0007.02 | Loopback on PORT-7 port | | 1.0007.04 | Fault propagation caused link down on port PORT-7 | | 1.0008.01 | Link down on PORT-8 port Link down on TRAFFIC-2-2 | | 1.0008.02 | Loopback on PORT-8 port | | 1.0008.04 | Fault propagation caused link down on port PORT-8 | | 1.0008.05 | PORT-8 Ingress rate limited to 1Gbps | | 1.0009.01 | Link down on PORT-9 port Link down on LAG-1 port | | 1.0009.02 | Loopback on PORT-9 port | | 1.0009.04 | Fault propagation caused link down on port PORT-9 | | 1.0010.01 | Link down on PORT-10 port | | 1.0010.02 | Loopback on PORT-10 port | | 1.0010.04 | Fault propagation caused link down on port PORT-10 | | 1.0011.01 | Link down on PORT-11 port | | 1.0011.02 | Loopback on PORT-11 port | | 1.0011.04 | Fault propagation caused link down on port PORT-11 | | 1.0012.01 | Link down on PORT-12 port | | 1.0012.02 | Loopback on PORT-12 port | | 1.0012.04 | Fault propagation caused link down on port PORT-12 | | 1.0013.01 | Link down on Management port | | 1.0014.01 | Link down on LAG-1 port | | 1.0014.02 | Loopback on LAG-1 port | | 1.0014.03 | Sub-port speed mismatch on port LAG-1 | | 1.0014.04 | Fault propagation caused link down on port LAG-1 | | 1.0015.01 | Link down on LAG-2 port | | 1.0015.02 | Loopback on LAG-2 port | | 1.0015.03 | Sub-port speed mismatch on port LAG-2 | | 1.0015.04 | Fault propagation caused link down on port LAG-2 | | 1.0016.01 | Link down on LAG-3 port | | 1.0016.02 | Loopback on LAG-3 port | | 1.0016.03 | Sub-port speed mismatch on port LAG-3 | | 1.0016.04 | Fault propagation caused link down on port LAG-3 | | 1.0017.01 | Link down on LAG-4 port | | 1.0017.02 | Loopback on LAG-4 port | | 1.0017.03 | Sub-port speed mismatch on port LAG-4 | | 1.0017.04 | Fault propagation caused link down on port LAG-4 | | 1.0018.01 | Link down on LAG-5 port | | 1.0018.02 | Loopback on LAG-5 port | | 1.0018.03 | Sub-port speed mismatch on port LAG-5 | | 1.0018.04 | Fault propagation caused link down on port LAG-5 | | 1.0019.01 | Link down on LAG-6 port | | 1.0019.02 | Loopback on LAG-6 port | | 1.0019.03 | Sub-port speed mismatch on port LAG-6 | | 1.0019.04 | Fault propagation caused link down on port LAG-6 | **SFP module for Rx/Tx power, temperature, VCC and LBC alarms and warnings In this section, yyyy = SFP module, where 0001 = SFP-1, 0002 = SFP-2, 0005 = SFP-5, 0006 = SFP-6where 0001 = SFP-1, 0002 = SFP-2, 0003 = SFP-3 [...] 0011 = SFP-11, 0012 = SFP-12.** | Parameter | Default Description | | --- | --- | | 2.yyyy.01 | temperature high alarm | | 2.yyyy.02 | temperature low alarm | | 2.yyyy.03 | temperature high alarm | | 2.yyyy.04 | temperature low alarm | | 2.yyyy.05 | supply voltage high alarm | | 2.yyyy.06 | supply voltage low alarm | | 2.yyyy.07 | supply voltage high alarm | | 2.yyyy.08 | supply voltage low alarm | | 2.yyyy.09 | laser bias current high alarm | | 2.yyyy.10 | laser bias current low alarm | | 2.yyyy.11 | laser bias current high alarm | | 2.yyyy.12 | laser bias current low alarm | | 2.yyyy.13 | transmit power high alarm | | 2.yyyy.14 | transmit power low alarm | | 2.yyyy.15 | transmit power high alarm | | 2.yyyy.16 | transmit power low alarm | | 2.yyyy.17 | receive power high alarm | | 2.yyyy.18 | receive power low alarm | | 2.yyyy.19 | receive power high alarm | | 2.yyyy.20 | receive power low warning | | 2.yyyy.21 | not present | **Performance Assurance Agent alarms In this section, yyyy = PAA instance index.** | Parameter | Default Description | | --- | --- | | 3.yyyy.01 | PAA_CC_ALERT | | 3.yyyy.02 | PAA_PL_ALERT | | 3.yyyy.03 | PAA_OW_DELAY_ALERT | | 3.yyyy.04 | PAA_OW_AVG_DELAY_ALERT | | 3.yyyy.05 | PAA_OW_DV_ALERT | | 3.yyyy.06 | PAA_OW_AVG_DV_ALERT | | 3.yyyy.07 | PAA_TW_DELAY_ALERT | | 3.yyyy.08 | PAA_TW_AVG_DELAY_ALERT | | 3.yyyy.09 | PAA_TW_DV_ALERT | | 3.yyyy.10 | PAA_TW_AVG_DV_ALERT | | 3.yyyy.11 | PAA_VLAN1_ID_ALERT | | 3.yyyy.12 | PAA_VLAN2_ID_ALERT | | 3.yyyy.13 | PAA_VLAN1_PRIO_ALERT | | 3.yyyy.14 | PAA_VLAN2_PRIO_ALERT | | 3.yyyy.15 | PAA_DSCP_ALERT | **SOAM module for Continuity Check, Delay, Packet Loss and other related alarms In this section, zzzz = CFM instance index.** | Parameter | Default Description | | --- | --- | | 4.zzzz.01 | RDI on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.02 | MAC status on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.03 | Remote CCM on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.04 | Errored CCM on down MEP, MEPID < ID >, port < port name >, VID < ID >, level <#> | | 4.zzzz.05 | Cross-connected CCM on down MEP, MEPID < ID >, port < port name >, VID , level <#> | | 4.zzzz.06 | AIS on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.07 | One-way delay on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.08 | One-way average delay on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.09 | One-way delay variation on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.10 | One-way average delay variation on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.11 | Two-way delay on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.12 | Two-way average delay on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.13 | Two-way delay variation on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.14 | Two-way average delay variation on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.15 | Excessive packet loss on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.16 | CSF-LOS on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.17 | CSF-FDI/AIS on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.18 | CSF-RDI on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.19 | Excessive SLM near-end packet loss on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | | 4.zzzz.20 | Excessive SLM far-end packet loss on down MEP, MEPID < ID >, port < port name >, VID < ID >, level < # > | **SyncE Synchronization, including NTP, PTP and GPS** | Parameter | Default Description | | --- | --- | | 6.0001.01 | SyncE loss of primary reference clock | | 6.0001.02 | SyncE loss of secondary reference clock | | 6.0001.03 | SyncE Forced to Free-Running or Local Clock | | 6.0001.04 | SyncE ESMC QL failure of Primary Reference Clock | | 6.0001.5 | SyncE ESMC QL failure of Secondary Reference Clock | | 6.0001.10 | NTP client lost server communication | | 6.0001.11 | NTP client used interface without timestamp capability | | 6.0001.12 | Remote NTP server used an interface without timestamp capability | | 6.0001.15 | No GPS fix | | 6.0001.20 | PTP slave failure communication with master | | 6.0001.21 | PTP slave used interface without timestamp capability | | 6.0001.30 | Time-of-day synchronization - May affect one-way delay measurements | **System modules, such as the VCAgent, NTP and other agents** | Parameter | Default Description | | --- | --- | | 7.0001.01 | NTP client lost server communication | | 7.0001.02 | NTP Time-of-day synchronization – May affect one-way delay measurements | | 7.0001.03 | GPS communication – May affect one-way delay measurements | | 7.0001.04 | PTP failure of communication with master clock | | 7.0001.05 | PTP Time-of-day synchronization – May affect one-way delay measurements | | 7.0001.06 | NTP client used interface without timestamp capability | | 7.0001.07 | PTP slave clock used interface without timestamp capability | | 7.0001.08 | Remote NTP server used an interface without timestamp capability | | 7.0004.01 | VCAgent communication failure with Vision EMS | | 7.0004.02 | VCAgent High Resolution Policy instances validation | | 7.0004.03 | VCAgent High Resolution Regulator instances validation | | 7.0004.04 | VCAgent High Resolution PAA instances validation | | 7.0004.05 | VCAgent High Resolution SOAM PL instances validation | | 7.0004.06 | VCAgent High Resolution SOAM DMM instances validation | | 7.0004.07 | VCAgent High Resolution SOAM SA instances validation | | 7.0004.08 | VCAgent High Resolution SOAM SA Metrics instances validation | | 7.0004.09 | VCAgent High Resolution SOAM SLM instances validation | | 7.0004.10 | VCAgent Policy statistics buffer full | | 7.0004.11 | VCAgent Regulator statistics buffer full | | 7.0004.12 | VCAgent PAA statistics buffer full | | 7.0004.13 | VCAgent SOAM PL statistics buffer full | | 7.0004.14 | VCAgent SOAM DMM statistics buffer full | | 7.0004.15 | VCAgent SOAM SA statistics buffer full | | 7.0004.16 | VCAgent SOAM SA Metrics statistics buffer full | | 7.0004.17 | VCAgent SOAM SLM statistics buffer full | | 7.0004.18 | VCAgent High resolution TWAMP-GEN instances validation | | 7.0004.19 | VCAgent TWAMP-GEN statistics buffer full | | 7.0004.20 | VCAgent High Resolution TWAMP instances validation | | 7.0004.21 | VCAgent TWAMP statistics buffer full | | 7.0004.22 | VCAgent High Resolution shaper instances validation | | 7.0004.23 | VCAgent shaper statistics buffer full | | 7.0004.24 | VCAgent High Resolution port instances validation | | 7.0004.25 | VCAgent Port statistics buffer full | | 7.0004.28 | VCAgent SFP statistics buffer full | | 7.0004.29 | VCAgent System Health statistics buffer full | **NE Alarms** | Parameter | Default Description | | --- | --- | | 8.0000.80 | Troubleshooting tool is running. ***Note:** This alarm is raised when either a troubleshooting tool is running or the Remote Syslog feature is enabled. The alarm is cleared only when both (troubleshooting tool and Remote Syslog feature) are disabled.* | **Environmental module for power supplies, temperature sensors and dry contact** | Parameter | Default Description | | --- | --- | | 8.0000.70 | Input 1 Active | | 8.0000.71 | Input 2 Active | | 8.0000.72 | Input 3 Active | | 8.0000.73 | Input 4 Active | | 8.0001.20 | Power feed A not present alarm | | 8.0001.30 | PCB temperature sensor not present alarm | | 8.0001.31 | PCB high-temperature warning | | 8.0001.32 | PCB high-temperature alarm | | 8.0001.40 | Fan 1 not present alarm | | 8.0001.41 | Fan 1 fan-stall alarm | | 8.0001.42 | Fan 1 fan-aging warning | | 8.0001.43 | Fan 1 fan-aging alarm | | 8.0002.20 | Power feed B not present alarm | | 8.0002.30 | CPU temperature sensor not present alarm | | 8.0002.31 | CPU high-temperature warning | | 8.0002.32 | CPU high-temperature alarm | | 8.0002.40 | Fan 2 not present alarm | | 8.0002.41 | Fan 2 fan-stall alarm | | 8.0002.42 | Fan 2 fan-aging warning | | 8.0002.43 | Fan 2 fan-aging alarm | | 8.0003.30 | FPGA temperature sensor not present alarm | | 8.0003.31 | FPGA high-temperature warning | | 8.0003.32 | FPGA high-temperature alarm | **ERP module In this section, xxxx = ERP instance index.** | Parameter | Default Description | | --- | --- | | 9.xxxx.01 | ERP protocol version mismatch | | 9.xxxx.02 | ERP force switch | | 9.xxxx.03 | ERP manual switch | | 9.xxxx.04 | ERP signal failed | **TWAMP Generator module In this section, xxxx = TWAMP instance index.** | Parameter | Default Description | | --- | --- | | 11.xxxx.01 | Max two-way delay | | 11.xxxx.02 | Average two-way delay | | 11.xxxx.03 | Max two-way delay variation | | 11.xxxx.04 | Average two-way delay variation | | 11.xxxx.05 | Max near-end one-way delay | | 11.xxxx.06 | Average near-end one-way delay | | 11.xxxx.07 | Max near-end one-way delay variation | | 11.xxxx.08 | Average near-end one-way delay variation | | 11.xxxx.09 | Max far-end one-way delay | | 11.xxxx.10 | Average far-end one-way delay | | 11.xxxx.11 | Max far-end one-way delay variation | | 11.xxxx.12 | Average far-end one-way delay variation | | 11.xxxx.13 | Continuity loss alert | | 11.xxxx.14 | Excessive packet loss alert | | 11.xxxx.01 | cell | | 11.xxxx.01 | cell | **Loop Detection feature In this section, xxxx = Loop Detection instance index.** | Parameter | Default Description | | --- | --- | | 13.xxxx.01 | Loop detected on Link/Tunnel instance x | | 13.xxxx.02 | Traffic discarded because of loop detection on instance < Loop detection name > | | 13.xxxx.03 | Loop detection instance not operational | **Flow broker Packet Engine** | Parameter | Default Description | | --- | --- | | 14.0001.01 | flow broker Packet Engine Server default-broker-server, connection with client lost | | 14.0001.02 | flow broker Packet Engine Server default-broker-server, out of streaming resources | | 14.0001.03 | flow broker Packet Engine Server default-broker-server, low streaming resources | | 14.0001.21 | flow broker Packet Engine Server default-broker-server, not streaming because of lack of synchronization | | 16.0000.52 | Unable to secure requested flowmeter 10 ms license | **Advertisement Inventory Alarm module** | Parameter | Default Description | | --- | --- | | 18.0001.01 | Inventory entries list is almost full | | 18.0001.02 | Inventory entries list is full | **Certificate Alarms** | Parameter | Default Description | | --- | --- | | 19.0000.01 | One or more certificates is about to expire | | 19.0000.02 | One or more certificates has expired | **To view the detailed status of an alarm** 1. Access the page **Show ▶Alarm**. 2. Click the alarm **Number** to view its detailed status. For more information on specific parameters, refer to the table "Alarm Status (**Show ▶Alarm**)". ### Viewing Chassis Alarms **To view the status of chassis-related alarms and information, including power supplies and temperature sensors** 1. Access the page **System ▶Alarm ▶Chassis**. The chassis alarms' status is displayed. For more information on specific parameters, refer to the following tables. **Power Supplies and Temperature Sensors (System ▶Alarm ▶Chassis) Power Supplies & Voltage Regulators, Temperature Sensors and Fan Monitors (System ▶Alarm ▶Chassis)** **Power Supplies** | Parameter | Description | | --- | --- | | Power Feed A and Power Feed B | The status of the various power sources for AC or DC (AUX), Feed A and Feed B. For an AC Powered unit: - 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. | | Voltage Regulators | For a **DC Powered** (AUX) unit: - 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. | | Voltage Regulators | For each of the voltage regulators that has been configured to report its status here, the following information is provided: - **Present**: The voltage regulator is connected. - **Not Present:** The voltage regulator is not connected. - **In Alarm**: An alarm has been triggered for this voltage regulator. - **None:** No alarm has been triggered for this voltage regulator. - **Voltage**: The current reading for this voltage regulator. For each of the voltage regulators that has been configured to report its status here, the following threshold information is provided: - **High-Voltage Warning:** Any voltage higher than this value triggers a warning. Expressed in Volts. - **High-Voltage Alarm:** Any voltage higher than this value triggers an alarm. Expressed in Volts. - **Low-Voltage Warning:** Any voltage lower than this value triggers a warning. Expressed in Volts. - **Low-Voltage Alarm:** Any voltage lower than this value triggers an alarm. Expressed in Volts. For details on any alarms or warnings, access the page **Show ▶Alarm**. | **Temperature Sensors** | Parameter | Description | | --- | --- | | PCB and FPGA Temperature Sensors | The following information is provided for each sensor (**PCB** 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** | Parameter | Description | | --- | --- | | Fan 1 and Fan 2 | For 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**. | ### Performing a Fan Test **To perform a fan test** 1. Access the page **System ▶Alarm ▶Chassis**. The chassis alarms' status is displayed. 2. Click the **Start** button to immediately initiate a fan test. The latest results for both Fan 1 and Fan 2 are displayed **Note:** The fan test retry period can be modified by changing the value in the "Retry period (hours)" field. For more information on specific parameters, refer to the table below. **Fan Test (System ▶Alarm ▶Chassis)** | Parameter | Description | | --- | --- | | Start button | Clicking on the Start button will initiate a fan test immediately. | | Retry period (hours) | 1–24. Default is 1 hour. If a fan test fails, this value will be used to set the retry period of the fan test. | | Latest Results | Shows for both fans if the test passed or failed. If the test failed, the rpm will be shown as well. | To access **all** alarm definitions, see [Alarm Definitions](https://docs.accedian.io/skylight-legacy-documentation/docs/skylight-alarm-definitions). **© 2026 Cisco and/or its affiliates. All rights reserved.** For more information about trademarks, please visit: [Cisco trademarks](https://www.cisco.com/c/en/us/about/legal/trademarks.html)[](https://www.cisco.com/c/en/us/about/legal/trademarks.html) For more information about legal terms, please visit: [Cisco legal terms](https://www.cisco.com/c/en/us/about/legal/terms-conditions.html)