alarm-type
ha-alarm
certificate-expiration
ha-node-down-alarm
ha-primary-down
ha-secondary-down
ncs-cluster-alarm
cluster-subscriber-failure
ncs-dev-manager-alarm
abort-error
bad-user-input
commit-through-queue-blocked
commit-through-queue-failed
commit-through-queue-failed-transiently
commit-through-queue-rollback-failed
configuration-error
connection-failure
final-commit-error
missing-transaction-id
ned-live-tree-connection-failure
out-of-sync
revision-error
ncs-package-alarm
package-load-failure
package-operation-failure
ncs-service-manager-alarm
service-activation-failure
ncs-snmp-notification-receiver-alarm
receiver-configuration-error
time-violation-alarm
transaction-lock-time-violationRecommended Action Verify that the user supplied input are correct.
Clear Condition(s) This alarm is not cleared.
Alarm Message(s)
Resource {resource} doesn't exist
Clear Condition(s) This alarm is cleared when the certificate is no longer loaded.
Alarm Message(s)
Certificate expires in less than {days} day(s)/Certificate has expired.
Recommended Action Verify IP connectivity between cluster nodes.
Clear Condition(s) This alarm is cleared if NCS succeeds to establish a subscription towards the remote node, or when the subscription is explicitly stopped.
Alarm Message(s)
Failed to establish netconf notification subscription to node ~s, stream ~s
Commit queue items with remote nodes will not receive required event notifications.
Clear Condition(s) An alarm raised due to a transient error will be cleared when NCS is able to reconnect to the device.
Alarm Message(s)
Commit queue item ~p is blocked because item ~p cannot connect to ~s
Clear Condition(s) This alarm is not cleared.
Alarm Message(s)
Failed to authenticate towards device {device}: {reason}
Device {dev} is locked
{Reason}
Device {dev} is southbound locked
Commit queue item {CqId} rollback invoked
Commit queue item {CqId} has failed: Operation failed because: inconsistent database
Remote commit queue item ~p cannot be unlocked: cluster node not configured correctly
Recommended Action Resolve with rollback if possible.
Clear Condition(s) This alarm is not cleared.
Alarm Message(s)
Failed to connect to device {dev}: {reason}
Connection to {dev} timed out
Failed to authenticate towards device {device}: {reason}
The configuration database is locked for device {dev}: {reason}
the configuration database is locked by session {id} {identification}
the configuration database is locked by session {id} {identification}
{Dev}: Device is locked in a {Op} operation by session {session-id}
resource denied
Commit queue item {CqId} rollback invoked
Commit queue item {CqId} has failed: Operation failed because: inconsistent database
Remote commit queue item ~p cannot be unlocked: cluster node not configured correctly
Recommended Action Investigate the status of the device and resolve the situation by issuing the appropriate action, i.e., service redeploy or a sync operation.
Clear Condition(s) This alarm is not cleared.
Alarm Message(s)
{Reason}
Recommended Action Verify that the configuration parameters defined in tailf-ncs-devices.yang submodule are consistent for this device.
Clear Condition(s) The alarm is cleared when NCS reads the configuration parameters for the device, and is raised again if the parameters are invalid.
Alarm Message(s)
Failed to resolve IP address for {dev}
the configuration database is locked by session {id} {identification}
{Reason}
Resource {resource} doesn't exist
Recommended Action Verify address, port, authentication, check that the device is up and running. If the error occurs intermittently, increase connect-timeout.
Clear Condition(s) If NCS successfully reconnects to the device, the alarm is cleared.
Alarm Message(s)
The connection to {dev} was closed
Failed to connect to device {dev}: {reason}
Recommended Action Reconcile by comparing and sync-from or sync-to.
Clear Condition(s) If NCS achieves sync with a device, the alarm is cleared.
Alarm Message(s)
The connection to {dev} was closed
External error in the NED implementation for device {dev}: {reason}
Internal error in the NED NCS framework affecting device {dev}: {reason}
Clear Condition(s) This alarm is never automatically cleared and has to be cleared manually when the HA cluster has been restored.
Alarm Message(s)
Lost connection to primary due to: Primary closed connection
Lost connection to primary due to: Tick timeout
Lost connection to primary due to: code {Code}
Clear Condition(s) This alarm is cleared when the secondary node is reconnected to the HA cluster.
Alarm Message(s)
Lost connection to secondary
Recommended Action Verify NACM rules on the concerned device.
Clear Condition(s) If NCS successfully reads a transaction id for which it had previously failed to do so, the alarm is cleared.
Alarm Message(s)
{Reason}
Recommended Action Verify the configuration of the optional NEDs. If the error occurs intermittently, increase connect-timeout.
Clear Condition(s) If NCS successfully reconnects to the managed device, the alarm is cleared.
Alarm Message(s)
The connection to {dev} was closed
Failed to connect to device {dev}: {reason}
Recommended Action Inspect the difference with compare-config, reconcile by invoking sync-from or sync-to.
Clear Condition(s) If NCS achieves sync with a device, the alarm is cleared.
Alarm Message(s)
Device {dev} is out of sync
Out of sync due to no-networking or failed commit-queue commits.
got: ~s expected: ~s.
Clear Condition(s) If NCS successfully loads a package for which an alarm was previously raised, it will be cleared.
Alarm Message(s)
failed to open file {file}: {str}
Specific to the concerned package.
Recommended Action Check the package for the reason.
Clear Condition(s) This alarm is not cleared.
Recommended Action Check the error-message and change the configuration.
Clear Condition(s) This alarm will be cleared when the NCS is configured to successfully receive SNMP notifications
Alarm Message(s)
Configuration has errors.
Clear Condition(s) If all device yang modules are supported by NCS, the alarm is cleared.
Alarm Message(s)
The device has YANG module revisions not supported by NCS. Use the /devices/device/check-yang-modules action to check which modules that are not compatible.
Clear Condition(s) If the service is successfully redeployed, the alarm is cleared.
Alarm Message(s)
Multiple device errors: {str}
Recommended Action Investigate if the transaction is stuck and possibly interrupt it by closing the user session which it is attached to.
Clear Condition(s) This alarm is cleared when the transaction has finished.
Alarm Message(s)
Transaction lock time exceeded threshold.