Alarms

This chapter provides description, severity, and troubleshooting procedure for each commonly encountered alarm in Cisco Optical Site Manager.

DBBACKUP-IN-PROGRESS

Default Severity: Warning, Non-Service-Affecting (NSA)

Resource Type: SYSTEM

The DBBACKUP-IN-PROGRESS alarm is triggered when the user initiates the database backup procedure.

Clear the DBBACKUP-IN-PROGRESS Alarm

Procedure

The alarm is cleared automatically when the database backup procedure is completed.

If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).

DBREST-IN-PROGRESS

Default Severity: Warning, Non-Service-Affecting (NSA)

Resource Type: SYSTEM

The DBREST-IN-PROGRESS alarm is triggered when the user initiates the database restore procedure.

Clear the DBREST-IN-PROGRESS Alarm

Procedure

The alarm is cleared automatically when the database restore procedure is completed.

If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).

DISK-SPACE-FULL

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Resource Type: SYSTEM

The No Space Left On Device (DISK-SPACE-FULL) alarm is triggered when the Cisco Optical Site Manager specific disk quota is exceeded. This serves as a preventive measure and does not necessarily indicate that the physical disk has reached its maximum capacity.

Clear the DISK-SPACE-FULL Alarm

The DISK-SPACE-FULL alarm is triggered when disk usage exceeds 6,500,000 Kb. This alarm is cleared once enough disk space is freed up.

Follow these steps to clear the alarm:

Procedure

Run the cisco-opt-dev server-resources disk-monitoring max-disc-size <value> command on the active Cisco Optical Site Manager node to remove large diagnostic files or core dumps to free up space or increase the Cisco Optical Site Manager disk quota.

If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447). Provide the logs collected in Step 1 to Cisco TAC.

DISK-SPACE-LOW

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Resource Type: SYSTEM CARD

The Low Disk Space Remaining On Device (DISK-SPACE-LOW) alarm is triggered when the disk occupation reaches a specific threshold, raising attention to potential space issues on both devices and Cisco Optical Site Manager container disk occupation.

Clear the DISK-SPACE-LOW Alarm

The alarm is cleared when the available disk space exceeds the configured threshold. The DISK-SPACE-LOW threshold is set at 90% of the configured value.

Follow these steps to clear the alarm:

Procedure

Run the cisco-opt-dev server-resources disk-monitoring max-disc-size <value> command on the active Cisco Optical Site Manager node to increase the threshold or to remove large diagnostic files or core dumps to free up space or increase the Cisco Optical Site Manager disk quota.

If the alarm does not clear, log into the Technical Support Website at https://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447). Provide the logs collected in Step 1 to Cisco TAC.

LOCAL-CERT-CHAIN-VERIFICATION-FAILED

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Resource Type: SYSTEM

The Local cert chain verification failed (LOCAL-CERT-CHAIN-VERIFICATION-FAILED) alarm is triggered whenever local certificate chain verification fails.

Clear the LOCAL-CERT-CHAIN-VERIFICATION-FAILED Alarm

Procedure

The alarm is cleared once a valid certificate chain is installed and verified.

If the alarm does not clear, log into the Technical Support Website at https://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447). Provide the logs collected in Step 1 to Cisco TAC.

LOCAL-CERT-EXPIRED

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Resource Type: SYSTEM

The Local certificate expired (LOCAL-CERT-EXPIRED) alarm is triggered whenever a local certificate expires.

Clear the LOCAL-CERT-EXPIRED Alarm

Procedure

The alarm is cleared once the expired certificate is renewed and activated.

If the alarm does not clear, log into the Technical Support Website at https://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447). Provide the logs collected in Step 1 to Cisco TAC.

LOCAL-CERT-EXPIRING-WITHIN-30-DAYS

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Resource Type: SYSTEM

The Local cert expiring within 30 days (LOCAL-CERT-EXPIRING-WITHIN-30-DAYS) alarm is triggered whenever a local certificate is within 30 days of expiration.

Clear the LOCAL-CERT-EXPIRING-WITHIN-30-DAYS Alarm

Procedure

The alarm is cleared once the certificate is renewed before expiry.

If the alarm does not clear, log into the Technical Support Website at https://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447). Provide the logs collected in Step 1 to Cisco TAC.

LOCAL-CERT-ISSUED-FOR-FUTURE-DATE

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Resource Type: SYSTEM

The Local cert issued for future date (LOCAL-CERT-ISSUED-FOR-FUTURE-DATE) alarm is triggered whenever a local certificate has a future-dated validity start time.

Clear the LOCAL-CERT-ISSUED-FOR-FUTURE-DATE Alarm

Procedure

The alarm is cleared once system time and certificate validity dates are corrected.

If the alarm does not clear, log into the Technical Support Website at https://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447). Provide the logs collected in Step 1 to Cisco TAC.

MEM-LOW

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Resource Type: CARD/ SYSTEM

The MEM-LOW alarm is triggered when the Cisco Optical Site Manager active containers experience either low Docker RAM availability or when disk usage for the /usr/nso/data/COSM directory exceeds the defined threshold.

Clear the MEM-LOW Alarm

The alarm is cleared when memory utilization returns to the normal operating range. The MEM_LOW threshold is set at 90% of RAM usage.

Follow these steps to clear the alarm:

Procedure

Run the docker stats command to gather and review docker statistics, including RSS (Resident Set Size) for Java and ncs.smp, to address sizing and high memory usage.

If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447). Provide the logs collected in Step 1 to Cisco TAC.

NE-DISCONNECTED

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Resource Type: NE

The Connection To Managed NE Lost (NE-DISCONNECTED) alarm is triggered whenever the connection to a managed network element is lost. It takes up to 2 minutes or less for the NE-DISCONNECTED alarm to be raised after the connection loss is detected.

Clear the NE-DISCONNECTED Alarm

Procedure

Step 1

Determine why connectivity to the device is lost. Check if the issue is due to a network problem or if the device itself is unstable or unreachable.

Step 2

The NE-DISCONNECTED alarm is cleared automatically once connectivity to the managed network element is restored.

Step 3

Restart the relevant management application or service and verify network connectivity and device stability.

If the alarm does not clear, log into the Technical Support Website at https://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447). Provide the logs collected in Step 1 to Cisco TAC.

NE-EVENT-DISCONNECTED

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Resource Type: NE

The Event Channel To Managed NE Lost (NE-EVENT-DISCONNECTED) alarm is triggered whenever the event channel from a managed network element is lost. The event channel refers to the communication path through which COSM receives telemetry or syslog updates from the device. If COSM is unable to receive these automatic updates, this alarm is raised.

In this scenario, it should still be possible to reach the device and perform configuration changes manually. However, automatic updates from the device will not be reflected in COSM until this alarm is cleared.

This list provides the condition / additional text and meaning / potential cause for the NE-EVENT-DISCONNECTED alarm conditions:

  • Addresses config is not correct: The required COSM IP address or port registration is missing from the device configuration.

  • Telemetry configuration is wrong: The destination, sensor, or subscription settings on the device are incorrectly configured.

  • Telemetry not received: Data is not reaching COSM due to potential network connectivity issues or incorrect device configuration.

  • No manager registered: No COSM manager is currently configured to receive data from the device.

  • Other manager registered: Unexpected or unauthorized COSM managers have been detected on the device.

  • Communication failure: The device is either locked or currently unreachable by the COSM application.

Clear the NE-EVENT-DISCONNECTED Alarm

Procedure

The alarm is cleared once the event channel to the managed network element is restored. This involves ensuring that the syslog and telemetry processes on the device are functioning correctly.

If the alarm does not clear, log into the Technical Support Website at https://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447). Provide the logs collected in Step 1 to Cisco TAC.

NE-NOT-AUTH-ACCESS

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Resource Type: NE

The NE-NOT-AUTH-ACCESS alarm is raised when a XR device has more than one syslog (configuration) logging and/or telemetry destination entries on port 7514.

Clear the NE-NOT-AUTH-ACCESS alarm

The alarm clears when the incorrect syslog and/or telemetry destination entries, which have a destination other than the current Cisco Optical Site Manager IP, are removed from the XR device

Follow these steps to clear the alarm:

Procedure

Step 1

Run the show run command to display the currently active configuration.

Step 2

Check the command output for multiple Cisco Optical Site Manager logging and model-driven telemetry server entries that use port 7514.

The example output highlights the multiple Cisco Optical Site Manager logging and model-driven telemetry in the command output in bold. 

RP/0/RP0/CPU0:1014-txp-246#show run          
!! Building configuration...
!! IOS XR Configuration 25.3.1.39I
!! Last configuration change at Mon Sep  8 11:57:24 2025 by cisco
!
hostname 1014
logging 10.1.1.1 vrf default severity all port 7514 source-address 10.1.1.1
logging 10.1.1.11 vrf default severity all port 7514 source-address 10.1.1.11
service timestamps log datetime localtime msec show-timezone year
username cisco
 group root-lr
 group cisco-support
 secret 10 $6$/25p40lFhVIP640.$nyB6.WUJUj2HlEGFwITSFs1l.M9cd40fVq9bk8ENHeGRzPUU56kUXqIWByEDluxNgHa3mmU8WTPlV2KFoc.UA1
!
grpc
!
telemetry model-driven
 include empty values
 destination-group COSM-DESTINATION
  address-family ipv4 10.1.1.1 port 7514
   encoding json
   protocol udp
  !
  destination 10.1.1.1 port 7514
   encoding json
   protocol udp
telemetry model-driven
 include empty values
 destination-group COSM-DESTINATION
  address-family ipv4 10.1.1.11 port 7514
   encoding json
   protocol udp
  !
  destination 10.1.1.11 port 7514
   encoding json
   protocol udp
  !
 !
 sensor-group COSM-FPD-GROUP
  sensor-path Cisco-IOS-XR-show-fpd-loc-ng-oper:show-fpd/locations/location/fpds/fpd/fpd-info-detail/status
 !

Step 3

Run the no logging command to remove the incorrect configuration.

Example:

RP/0/RP0/CPU0:1014(config)#no logging 10.1.1.11 vrf default severity all port 7514 source-address 10.1.1.11

Step 4

Run the no telemetry model-driven to remove the incorrect configuration for model-driven telemetry.

Example:

RP/0/RP0/CPU0(config):1014#no telemetry model-driven destination-group COSM-DESTINATION address-family ipv4 10.1.1.11 port 7514
no telemetry model-driven destination-group COSM-DESTINATION destination 10.1.1.11 port 7514

If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447).

PROTNA

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Resource Type: CARD / SYSTEM

The Protection Unit Not Available (PROTNA) alarm is raised when the link between the Cisco Optical Site Manager active and standby application is lost. This can happen due to any of these reasons.

  • The device hosting the standby application is not discoverable or unreachable.

  • There is a cut in the fiber cable connecting to the device hosting the standby application.

Clear the PROTNA Alarm

The alarm is cleared when the link between the Cisco Optical Site Manager Active and Standby application is restored.

To clear the alarm:

Procedure

Step 1

Ensure the device hosting the standby application is discoverable and reachable by the device hosting the active application.

Step 2

Check and repair any cuts in the fiber cable connecting to the device hosting the standby application.

If the alarm does not clear, log into the Technical Support Website at for more information or call Cisco TAC (1 800 553-2447).

RAMAN-CALIBRATION-FAILED

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Resource Type: RAMAN_AMPLIFIER

The RAMAN-CALIBRATION-FAILED alarm is raised on the EDRA-1-xx, EDRA-2-xx, and RAMAN-CTP cards when automatic Raman pump calibration is failed and will not run again. The alarm indicates insufficient Raman Amplification by customer fibre. The Raman calibration can also fail due to the setup issues that include:

  • Wrong patch-cords or cabling

  • Incorrect ANS

  • Missing communication channel between nodes.

Clear the RAMAN-CALIBRATION-FAILED Alarm

SUMMARY STEPS

  1. Use optical time domain reflectometer (OTDR) to identity any excess loss between the Raman card LINE-RX port and the customer fibre. After the inspection, a new Raman Calibration is triggered and if the physical problem is fixed, the alarm will clear.
  2. If the alarm is caused by a set-up problem, re-verify all node installation steps and manually trigger a Raman Calibration.

DETAILED STEPS

Step 1

Use optical time domain reflectometer (OTDR) to identity any excess loss between the Raman card LINE-RX port and the customer fibre. After the inspection, a new Raman Calibration is triggered and if the physical problem is fixed, the alarm will clear.

Step 2

If the alarm is caused by a set-up problem, re-verify all node installation steps and manually trigger a Raman Calibration.

If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447).

SYSBOOT

Default Severity:

Major (MJ), Service-Affecting (SA)

Minor (MN), Non-Service-Affecting (NSA)

The COSM application restarts when the system object, or Sysboot, is triggered. This can occur automatically or as a result of a user action.

If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/c/en/us/support/index.html for more information or call Cisco TAC (1 800 553-2447).


Note

SYSBOOT is an informational alarm. It only requires troubleshooting if it does not clear.

UNTRUSTED-APPLICATION

Default Severity: Critical (CR), Non-Service-Affecting (NSA)

Resource Type: SYSTEM

The Trust Not Established With CSLU/CSSM (UNTRUSTED-APPLICATION) alarm is triggered when Smart License is configured in the Smart Transport or CSLU or Offline mode and trust is not established with Cisco Smart Software Manager (CSSM) has not been established.

Clear the UNTRUSTED-APPLICATION Alarm

The alarm is cleared once trust is established between with the CSSM.

To clear the alarm:

Procedure

Ensure that trust is established with CSSM.

For more details on how to establish trust with CSSM, see Configure Smart Transport.

If the alarm does not clear, log into the Technical Support Website at for more information or call Cisco TAC (1 800 553-2447).

USAGE-NOT-REPORTED

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Resource Type: SYSTEM

The Licenses Usage Is Not Reported (USAGE-NOT-REPORTED) alarm is triggered when the Cisco Optical Site Manager is unable to communicate with the Cisco Smart Software Manager (CSSM) or Cisco Smart Licensing Utility (CSLU).

Clear the USAGE-NOT-REPORTED Alarm

To clear the alarm:

Procedure

Step 1

Verify whether trust has been properly established with CSSM.

Step 2

Verify that CSSM is accessible from Cisco Optical Site Manager, either directly or through CSLU.

If the alarm does not clear, log into the Technical Support Website at for more information or call Cisco TAC (1 800 553-2447).