The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Description |
Audit event is generated by this application. |
Explanation |
Failed to write into the primary file path. |
Recommended Action |
Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path. |
Parameter |
Type |
Help |
---|---|---|
UserID |
String |
UserID |
ClientAddress |
String |
ClientAddress |
Severity |
String |
Severity |
EventType |
String |
EventType |
ResourceAccessed |
String |
ResourceAccessed |
EventStatus |
String |
EventStatus |
AuditDetails |
String |
AuditDetails |
ComponentID |
String |
ComponentID |
CompulsoryEvent |
String |
CompulsoryEvent |
AuditCategory |
String |
AuditCategory |
Description |
Audit event is generated by this application |
Explanation |
Failed to write into the primary file path. |
Recommended Action |
Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path. |
Parameter |
Type |
Help |
---|---|---|
UserID |
String |
UserID |
ClientAddress |
String |
ClientAddress |
Severity |
String |
Severity |
EventType |
String |
EventType |
ResourceAccessed |
String |
ResourceAccessed |
EventStatus |
String |
EventStatus |
AuditDetails |
String |
AuditDetails |
ComponentID |
String |
ComponentID |
CompulsoryEvent |
String |
CompulsoryEvent |
AuditCategory |
String |
AuditCategory |
Description |
Audit event is generated by this application |
Explanation |
Failed to write into the primary file path. |
Recommended Action |
Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path. |
Parameter |
Type |
Help |
---|---|---|
UserID |
String |
UserID |
ClientAddress |
String |
ClientAddress |
Severity |
String |
Severity |
EventType |
String |
EventType |
ResourceAccessed |
String |
ResourceAccessed |
EventStatus |
String |
EventStatus |
AuditDetails |
String |
AuditDetails |
ComponentID |
String |
ComponentID |
CompulsoryEvent |
String |
CompulsoryEvent |
AuditCategory |
String |
AuditCategory |
Description |
Duplex Mismatch Alarm |
Explanation |
This alarm is generated by Cisco CDP for a duplex mismatch between the local interface and the switch interface. |
Recommended Action |
Ensure that duplex settings are set to auto or full on both the local and switch interfaces. |
Parameter |
Type |
Help |
---|---|---|
SwitchDuplex |
String |
Switch Duplex Settings |
LocalInterfaceDuplex |
String |
Local Interface Duplex Settings |
Description |
Failed to connect to database. |
Explanation |
An operation to connect to the database failed. |
Recommended Action |
Verify that the database is running. |
Description |
Failed to connect to a JMS Broker. |
Explanation |
A service is failing to connect to the JMS broker. |
Recommended Action |
Verify that the JMS broker is running. |
Description |
This information alarm indicates that a certificate validity period is approaching and the expiry date is within the notification window configured. |
Explanation |
Certificate expiry date is approaching shortly and certificate will be invalid. |
Recommended Action |
Regenerate the certificate that is about to expire from Certificate Management UI from CUOS Administration web page. If the certificate is issued by a CA, generate a CSR, submit the CSR to CSA, obtain a fresh certificate from CA, and upload it to Cisco Unified Communications Manager. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
Certificate has expired and must be changed. |
Explanation |
The validity date for the specified certificate is over and the certificate is expired. |
Recommended Action |
Regenerate the certificate that is about to expire from Certificate Management UI from CUOS Administration web page. If the certificate is issued by a CA, obtain a fresh certificate from CA and upload it to Cisco Unified Communications Manager. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
The certificate is about to expire in less than 24 hours or has already expired. |
Explanation |
The validity of the certificate indicated in the notification message is less than 24 hours. |
Recommended Action |
Regenerate the certificate that is about to expire from Certificate Management UI from CUOS Administration web page. If the certificate is issued by a CA, generate a CSR, submit the CSR to CA, obtain a fresh certificate from CA, and upload it to Cisco Unified Communications Manager. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
The certificate has expired or will expire in less than seven days. |
Explanation |
The certificate is invalid or validity of the certificate indicated in the notification is less than 7 days. |
Recommended Action |
Regenerate the certificate that is about to expire from Certificate Management UI from CUOS Administration web page. If the certificate is issued by a CA, generate a CSR, submit the CSR to CA, obtain a fresh certificate from CA, and upload it to Cisco Unified Communications Manager. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
Alarm to debug certificate management. |
Explanation |
Alarm used for debug purpose. |
Recommended Action |
None |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
Indicates errors in certificate expiry monitor process. |
Explanation |
Certificate is expiring. |
Recommended Action |
Regenerate or re-import the certificate. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
Indicates that certificate expiry is approaching but expiry date is more than 30 days. |
Explanation |
This information alarm indicates that a certificate validity period is approaching and validity of the certificate is more than 30 days. |
Recommended Action |
Regenerate the certificate that is about to expire from Certificate Management UI from CUOS Administration web page. If the certificate is issued by a CA, generate a CSR, submit the CSR to CA, obtain a fresh certificate from CA, and upload it to Cisco Unified Communications Manager. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
Alarm that indicates certificate will expire in 30 days or less. |
Explanation |
The expiry date of the certificate indicated in the notification is less than a month. |
Recommended Action |
Regenerate the certificate that is about to expire from Certificate Management UI from CUOS Administration web page. If the certificate is issued by a CA, generate a CSR, submit the CSR to CA, obtain a fresh certificate from CA, and upload it to Cisco Unified Communications Manager. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
Alarm that indicates that the Tomcat certificate is regenerated. |
Explanation |
This alarm indicates that the Tomcat certificate has been regenerated or the CA signed Tomcat certificate has been uploaded. |
Recommended Action |
Restart the Tomcat service for the new Tomcat certificate to be effective. If EMCC feature is enabled for the communication across the clusters, perform the bulk certificate management provisioning for the Tomcat unit from Cisco Unified OS Administration Web page. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
Indicates that the recently uploaded certificate is revoked and must be changed at the earliest opportunity. |
Explanation |
This alarm indicates that the recently uploaded third party signed certificate or trust certificate is revoked. |
Recommended Action |
Delete the revoked trust certificate and re-upload it from Cisco Unified OS Administration Webpage. In case of third party signed (own) certificate, just re-upload the new certificate. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
Indicates that Cisco Unified Communications Manager could not determine the OCSP revocation status of the recently uploaded certificate. |
Explanation |
This alarm indicates that Cisco Unified Communications Manager failed to determine the revocation status of the recently uploaded third party signed certificate or trust certificate. |
Recommended Action |
Evaluate the reason for the certificate revocation failure. Delete and re-upload the certificate, if required. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message |
Description |
DRF uses ipsec truststore certificate for securing communication between the MA and LA service. This certificate is missing on the node. |
Explanation |
DRF uses ipsec truststore certificate for securing communication between the MA and LA service. This certificate is missing on the node. Therefore, DRF LA cannot connect to MA. |
Recommended Action |
Download the ipsec.pem file from Publisher, upload it as ipsec-trust only on the missing node, then restart the Cisco DRF Local service. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF Master Agent running on the Publisher has received a client connection request from an unknown server outside the cluster. The request has been rejected. |
Explanation |
The DRF Master Agent running on the Publisher has received a client connection request from an unknown server outside the cluster.The request has been rejected. |
Recommended Action |
Remove the suspect server from the network. Refer to the Reason section for suspect servers: Hostname and IP Address. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF System has detected a malicious pattern which could result in a security violation. |
Explanation |
The DRF Network Message contains a malicious pattern which could result in a security violation like code injection or directory traversal. The DRF Network Message has been blocked. |
Recommended Action |
Stop the Cisco DRF Master and Cisco DRF Local Agent Services. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF Master Agent was unable to start because it was unable to open port 4040. |
Explanation |
DRF Master Agent was unable to start because it was unable to open port 4040. |
Recommended Action |
Verify that port 4040 is not already in use. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port 4040. |
Explanation |
DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port 4040. |
Recommended Action |
Verify that the CiscoDRFMaster and CiscoDRFLocal services are running. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF Local Agent is not able to connect to Master Agent. |
Explanation |
DRF Local Agent is not able to connect to Master Agent. |
Recommended Action |
Verify that the Master Agent is up and the port is authorized. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
Master Agent was unable to send a backup/restore request to the local agent. |
Explanation |
Master Agent was unable to send a backup/restore request to the local agent. |
Recommended Action |
Restart the corresponding local agents and the master agent. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The Cisco DRF backup process failed. |
Explanation |
The DRF backup process encountered errors. |
Recommended Action |
Review the DRF logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF restore process failed. |
Explanation |
The DRF restore process encountered errors. |
Recommended Action |
Review the DRF logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF backup process failed due to backup device error. |
Explanation |
The DRF backup process failed due to backup device error. |
Recommended Action |
Ensure that the proper device has been specified in the DRF configuration. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF is unable to access tape device. |
Explanation |
DRF is unable to access tape device. |
Recommended Action |
Ensure that the tape drive is working properly and it contains a valid tape. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF is unable to access local device. |
Explanation |
DRF is unable to access local device. |
Recommended Action |
Ensure that the local location exists and is accessible. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF internal process has encountered an error. |
Explanation |
DRF internal process has encountered an error. |
Recommended Action |
Review the DRF logs for details. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF restore operation has encountered an error. The restore operation was cancelled internally. |
Explanation |
The DRF restore operation has encountered an error. The restore operation was cancelled internally. |
Recommended Action |
Review the DRF logs for details. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF was unable to back up at least one component. |
Explanation |
DRF requested a component to back up its data. However, there was an error during the backup process and the component was not backed up. |
Recommended Action |
Review the component backup logs and if required, contact support. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF was unable to restore at least one component. |
Explanation |
DRF requested a component to restore its data. However, there was an error during the restore process and the component was not restored. |
Recommended Action |
Review the component restore logs and if required, contact support. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The node being backed up disconnected from the Master Agent before it was fully backed up. |
Explanation |
The DRF Master Agent was running a backup operation on a CCM cluster, when one of the nodes disconnected before the backup operation completed. |
Recommended Action |
Check the computer that disconnected during backup. If the computer was accidentally shutdown, restart the backup. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
No registered components available, backup failed. |
Explanation |
DRF backup failed because registered components were not available. |
Recommended Action |
Ensure that at least one component is registered before attempting a backup. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
No feature selected for backup. |
Explanation |
No feature selected for backup. |
Recommended Action |
Ensure that at least one feature is configured before attempting a backup. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The node being restored disconnected from the Master Agent before it was fully restored. |
Explanation |
The DRF Master Agent was running a restore operation on a CCM cluster, when one of the nodes disconnected before the restore operation completed. |
Recommended Action |
Check the computer that disconnected during restore. If the computer was accidentally shutdown, restart the restore. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF SFTP operation failed. |
Explanation |
The DRF SFTP operation failed. |
Recommended Action |
Ensure that the destination server is available, has appropriate permissions, and that the SFTP daemon is running. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF registration operation failed. |
Explanation |
The DRF registration operation failed. |
Recommended Action |
DRF registration failed for a component due to an internal error. Review the DRF logs and if required, contact support. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF backup operation encountered an error. The backup was cancelled internally. |
Explanation |
The DRF backup operation encountered an error. The backup was cancelled internally. |
Recommended Action |
Review the DRF logs for details. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF could not access the log directory. |
Explanation |
DRF could not access the log directory. |
Recommended Action |
Ensure that the DRF user has required permission and enough space exists in the DRF Log and Trace directory. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF successfully deregistered the requested component. |
Explanation |
DRF successfully deregistered the requested component. |
Recommended Action |
Ensure that the deregistered component is not required for further backup and restore operations. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF deregistration request for a component failed. |
Explanation |
The DRF deregistration request for a component failed. |
Recommended Action |
Review the DRF logs and if required, contact support. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF automatically deregistered all the components for a server. |
Explanation |
This server might have been disconnected from the CCM cluster. |
Recommended Action |
None |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF Scheduler is disabled because configured features were not available for backup. |
Explanation |
DRF Scheduler is disabled because configured features were not available for backup. |
Recommended Action |
Ensure at least one feature is configured for the scheduled backup to run. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF successfully registered the requested component. |
Explanation |
DRF successfully registered the requested component. |
Recommended Action |
Ensure that the registered component is needed for backup and restore operations. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF scheduled backup configuration is updated automatically due to feature deregistration. |
Explanation |
DRF scheduled backup configuration is updated automatically due to feature deregistration. |
Recommended Action |
Ensure that the new configuration is appropriate for the backup or restore operation. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF backup completed successfully. |
Explanation |
DRF backup completed successfully. |
Recommended Action |
Ensure that the backup operation completed successfully. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
DRF restore completed successfully. |
Explanation |
DRF restore completed successfully. |
Recommended Action |
Ensure that the restore operation completed successfully. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
The DRF backup or restore process failed. |
Explanation |
The DRF backup or restore process encountered errors. |
Recommended Action |
Review the DRF logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
A valid backup of the current system was not found. |
Explanation |
A valid backup of the current system was not found after an upgrade/migration or fresh installation. |
Recommended Action |
Cisco recommends that you perform a backup using the Disaster Recovery System. |
Parameter |
Type |
Help |
---|---|---|
Reason |
String |
Reason for error |
Description |
Cannot distinguish between multiple SNMP DefaultCredentials in the database. One has been arbitrarily selected for the device entity. |
Explanation |
Multiple DefaultCredentials are defined with the same EquipmentType/SNMPAccessType. |
Recommended Action |
Remove one DefaultCredential for the duplicated EquipmentType/SNMPAccessType. |
Parameter |
Type |
Help |
---|---|---|
ApplicationType |
String |
The type of application with multiple credentials |
Description |
Cannot distinguish between multiple SNMP Credentials in the database. One has been arbitrarily selected for the device entity. |
Explanation |
Multiple SNMP Credentials are defined for the device. |
Recommended Action |
Remove one SNMP Credential for device. |
Parameter |
Type |
Help |
---|---|---|
ApplicationType |
String |
The type of application with multiple credentials. |
DevicePK |
String |
Primary Key in SDR of the device with multiple credentials. |
DeviceName |
String |
Name in SDR of the device with multiple credentials. |
Description |
Cannot distinguish between multiple ADMIN DefaultCredentials in the database. One has been arbitrarily selected for the device entity. |
Explanation |
Multiple DefaultCredentials are defined for the same EquipmentType. |
Recommended Action |
Remove one DefaultCredential for the EquipmentType. |
Parameter |
Type |
Help |
---|---|---|
ApplicationType |
String |
The type of application with multiple credentials. |
Description |
Cannot distinguish between multiple ADMIN Credentials in the database. One has been arbitrarily selected for the device entity. |
Explanation |
Multiple ADMIN Credentials are defined for the device. |
Recommended Action |
Remove one ADMIN Credential for device. |
Parameter |
Type |
Help |
---|---|---|
ApplicationType |
String |
The type of application with multiple credentials. |
DevicePK |
String |
Primary Key in SDR of the device with multiple credentials. |
DeviceName |
String |
Name in SDR of the device with multiple credentials. |
Description |
Monitored customer count exceeds the Prime Collaboration limit. |
Explanation |
See attached current customer count. |
Recommended Action |
Move one or more customers to be monitored by another Prime Collaboration. |
Parameter |
Type |
Help |
---|---|---|
CustomerCount |
String |
Current customer count on the Prime Collaboration |
CountPercentagePassed |
String |
The count percentage for customers that has been exceeded. |
MaxCustomersAllowed |
String |
The maximum allowed customers on the Prime Collaboration. |
PrimeCollabAddress |
String |
The address of the Prime Collaboration that has exceeded customer limits. |
PrimeCollabName |
String |
The name of the Prime Collaboration that has exceeded customer limits. |
Description |
Monitored device count exceeds the Prime Collaboration limit. |
Explanation |
See attached current device count. |
Recommended Action |
Move one or more devices to be monitored by another Prime Collaboration. |
Parameter |
Type |
Help |
---|---|---|
DeviceCount |
String |
Current device count on the Prime Collaboration |
CountPercentagePassed |
String |
The count percentage for devices that has been exceeded. |
MaxDevicesAllowed |
String |
The maximum allowed devices on the Prime Collaboration. |
PrimeCollabAddress |
String |
The address of the Prime Collaboration that has exceeded device limits. |
PrimeCollabName |
String |
The name of the Prime Collaboration that has exceeded device limits. |
Description |
Subscriber count exceeds the Prime Collaboration limit. |
Explanation |
See attached current subscriber count. |
Recommended Action |
Move one or more CUCM clusters to be monitored by another Prime Collaboration. |
Parameter |
Type |
Help |
---|---|---|
SubscriberCount |
String |
Current subscriber count on the Prime Collaboration |
CountPercentagePassed |
String |
The count percentage for subscribers that has been exceeded. |
MaxSubscribersAllowed |
String |
The maximum allowed subscribers on the Prime Collaboration. |
PrimeCollabAddress |
String |
The address of the Prime Collaboration that has exceeded subscriber limits. |
PrimeCollabName |
String |
The name of the Prime Collaboration that has exceeded subscriber limits. |
Description |
The CUCDMSync service failed to Initialize; a service restart is required. |
Explanation |
A problem arose during CUCDMSync service initialization. |
Recommended Action |
Verify that the Shared Data Repository and the server are set up correctly. |
Description |
CUCDMSync failed to access the Shared Data Repository database. |
Explanation |
The Shared Data Repository failure cased an issue during CUCDMSync. |
Recommended Action |
Verify that the Shared Data Repository database is set up correctly. |
Parameter |
Type |
Help |
---|---|---|
ReasonCode |
String |
A code indicating the reason the association is under scrutiny. |
ReasonText |
String |
Text indicating the reason the association is under scrutiny. |
Description |
CUCDMSync detected an issue with a Shared Data Repository field. |
Explanation |
A specific field in the Shared Data Repository contains an issue. |
Recommended Action |
Verify that the Shared Data Repository entry is configured with the correct value. |
Parameter |
Type |
Help |
---|---|---|
EntryType |
String |
A code indicating which SDR entry has detected an issue. |
ReasonText |
String |
Text indicating the reason the association is under scrutiny. |
Description |
CUCDMSync detected that the Cisco HCS Fulfillment service change notification service is out of service. |
Explanation |
The Cisco HCS Fulfillment service monitors the SDR for configuration changes. When detected, the Fulfillment service notifies other services of SDR changes. The CUCDMSync service received an indication that the change notify service provided by Cisco HS Fulfillment is not active. |
Recommended Action |
Verify that the Cisco HCS Fulfillment service is running. |
Parameter |
Type |
Help |
---|---|---|
EntryType |
String |
A code indicating which SDR Entry has detected an issue. |
ReasonText |
String |
Text indicating the reason the association is under scrutiny. |
Description |
CUCDMSync failed to access the Cisco Unified Communications Domain Manager server. |
Explanation |
CUCDMSync unable to connect to the Cisco Unified Communications Domain Manager server. |
Recommended Action |
Verify that the Cisco Unified Communications Domain Manager server is online and reachable. Verify the username and password are configured correctly. |
Parameter |
Type |
Help |
---|---|---|
CUCDMServer |
String |
Identity of the CUCDM server under scrutiny. |
ReasonCode |
String |
A code indicating the reason the association is under scrutiny. |
ReasonText |
String |
Text indicating the reason the association is under scrutiny. |
Description |
CUCDMSync did not complete successfully. |
Explanation |
A transient error was encountered during a CUCDMSync operation. |
Recommended Action |
Retry the CUCDMSync operation. If the error continues to occur, collect the CUCDMSync logs for further evaluation. |
Parameter |
Type |
Help |
---|---|---|
Agent ID |
String |
The Agent ID that was stuck. |
Reason Text |
String |
Text indicating the reason the association is under scrutiny. |
Description |
Exhausted the maximum retries. |
Explanation |
A request that was sent to DMA-SA failed. |
Recommended Action |
Verify configuration of the device and connectivity to Cisco Prime Collaboration Assurance. |
Parameter |
Type |
Help |
---|---|---|
DeviceName |
String |
Name of the device related to the alarm |
EntityType |
String |
SDR entity type |
Entity Key |
String |
The primary key for the SDR entity |
RetryReason |
String |
The reason for retrying |
Description |
A problem exists with the SDR association between a device and a virtual machine. |
Explanation |
The system failed to automatically handle the association between a device and a virtual machine. |
Recommended Action |
Verify that the Cisco CDM service is running. If the error persists, restart the Cisco HCS Fulfillment service. |
Parameter |
Type |
Help |
---|---|---|
DeviceName |
String |
Name of the device related to the alarm |
EntityKey |
String |
The primary key for the SDR entity |
ReasonText |
String |
Text indicating the reason the association is under scrutiny |
Description |
A problem exists with the SDR association between ESXiHost and blade. |
Explanation |
The system failed to automatically handle the association between ESXiHost and blade. |
Recommended Action |
Verify that the Cisco CDM service is running. If the error persists, restart the Cisco HCS Fulfillment service. |
Parameter |
Type |
Help |
---|---|---|
ESXiHostName |
String |
Name of the ESXiHost related to the alarm |
EntityKey |
String |
The primary key for the SDR entity |
ReasonText |
String |
Text indicating the reason the association is under scrutiny |
Description |
The Link Service exhausted the number of retries for a particular link type. |
Explanation |
The Link Service failed to establish association between two entities after the specified number of retries. |
Recommended Action |
Verify that the Cisco CDM service is running. If the error persists, restart the Cisco HCS Fulfillment service. |
Parameter |
Type |
Help |
---|---|---|
NumOfRetry |
String |
Number of retry attempts |
Linkage |
String |
The entity being linked |
Description |
A problem exists with the SDR association between a customer and a Prime Collaboration. |
Explanation |
The system failed to automatically handle the association between a customer and a Prime Collaboration. |
Recommended Action |
If excessive Prime Collaboration utilization is the cause, then either add additional Prime Collaborations or reduce utilization on existing Prime Collaborations. |
Parameter |
Type |
Help |
---|---|---|
CustomerName |
String |
Name of the customer related to the alarm |
EntityType |
String |
SDR entity type |
EntityKey |
String |
The primary key for the SDR entity |
ReasonText |
String |
Text indicating the reason the association is under scrutiny |
Description |
Fail to Connect to SDR Database. |
Explanation |
An operation to connect to the SDR database has failed. |
Recommended Action |
Verify the 'Cisco CDM Database' service is running. If it is not running, start the service; if it is running, stop and then start the service. If the cause is VCenterDBReadFailure, verify the vCenter configuration is correct in the Infrastructure Manager. The credentials user ID and password must be correctly configured as ADMIN credentials, and the correct IP address or host/domain names must be configured as SERVICE_PROVIDER_SPACE. If the cause is a Job or JobEntity related failure, restart the IPA and/or SDR service. If the problem persists, check IPA logs. |
Parameter |
Type |
Help |
---|---|---|
VCenter |
String |
Path of the VCenter (Host Short Name, FQDN, or IP Address) related to the alarm |
Cause |
String |
Parameter |
Type |
Help |
---|---|---|
VCenter |
String |
Name of the vCenter related to the alarm |
Cause |
String |
Description |
Data Center resources are unavailable. |
Explanation |
A Data Center resource is unavailable. This indicates that an expected resource changed or disappeared after the IPA Job began. |
Recommended Action |
Verify that the resource identified by the resource name and cause is online and reachable. Resend the IPA Provisioning request with changes to the XML if necessary. If the problem persists, restart the IPA Service. |
Parameter |
Type |
Help |
---|---|---|
VCenter |
String |
Name of the vCenter related to the Alarm. |
ResourceName |
String |
Name of the resource as defined by the Cause |
Cause |
String |
Description |
Failure while communicating with VCenter. |
Explanation |
Internal Failure while executing a vCenter operation after the connection was opened. |
Recommended Action |
Verify vCenter is online, reachable, and in an operational state. If a VmWareTools error, check to ensure it is running on the necessary VMs. Mount, UnMount, or ChangePortGroup failure indicates a problem occurred while reconfiguring the VM. Ensure that the vCenter is operational and vCenter networking configuration is valid. If problem persists, restart the IPA Service and check the IPA logs. |
Parameter |
Type |
Help |
---|---|---|
ResourceName |
String |
Name of the resource. If cause is VmToolsNotRunning, this is the VM name. Otherwise, it is the VCenter name. |
Cause |
String |
Description |
No permission to perform necessary action in vCenter. |
Explanation |
No permission to execute required vCenter operation with the given username. |
Recommended Action |
Add the necessary permissions to the vCenter user or switch to a user with the necessary permissions. The required privileges: Add the necessary permissions to the vCenter user or switch to a user with the necessary permissions. The required privileges: Datastore.AllocateSpace, Datastore.AllocateSpace, Datastore.Browse, Datastore.FileManagement, Resource.AssignVMToPool, System.Anonymous, System.Read, System.View, VirtualMachine.Config.EditDevice, VirtualMachine.Config.ResetGuestInfo, VirtualMachine.Config.Settings, VirtualMachine.GuestOperations.Execute, VirtualMachine.GuestOperations.Modify, VirtualMachine.GuestOperations.Query, VirtualMachine.Interact.DeviceConnection, VirtualMachine.Interact.PowerOff, VirtualMachine.Interact.PowerOn, VirtualMachine.Interact.Reset, VirtualMachine.Interact.SetCDMedia, VirtualMachine.Interact.SetFloppyMedia, VirtualMachine.Interact.ToolsInstall, VirtualMachine.Inventory.Create, VirtualMachine.Inventory.CreateFromExisting, VirtualMachine.Inventory.Delete, VirtualMachine.Provisioning.DeployTemplate |
Parameter |
Type |
Help |
---|---|---|
VCenter |
String |
Name of the vCenter related to the alarm. |
UserName |
String |
The username used to connect to the vCenter. |
Parameter |
Type |
Help |
---|---|---|
JobID |
String |
ID of the Job related to the alarm |
Description |
The Cisco Unified Communications Manager DB service is not operational on the VM. |
Explanation |
While checking that the DB service was active on the Cisco Unified Communications Manager VM, the operation failed or timed out. |
Recommended Action |
Manually delete VMs associated with the job and re-submit the job. If the problem persists, try running cloning/identity manually on VMs. |
Parameter |
Type |
Help |
---|---|---|
CustomerName |
String |
Name of the customer with the failed Cisco Unified Communications Manager VM |
VmName |
String |
Name of the Cisco Unified Communications Manager VM |
Description |
The Cisco Unified Communications Manager VM did not come online. |
Explanation |
While waiting for the Cisco Unified Communications Manager VM to come online, the operation failed or timed out. |
Recommended Action |
Check that the network settings for the Customer VMs are correct. Manually delete VMs associated with the job and re-submit the job. |
Parameter |
Type |
Help |
---|---|---|
CustomerName |
String |
Name of the customer with the failed Cisco Unified Communications Manager VM |
VmName |
String |
Name of the Cisco Unified Communications Manager VM |
Description |
Generic HLM Alarm. |
Explanation |
This alarm indicates a problem within HLM has occurred. |
Recommended Action |
Check the HLM logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
The Message given by the Alarm |
Description |
HLM Assign Fail Alarm. |
Explanation |
Assign a UC cluster to a Prime License Manager has failed. |
Recommended Action |
Determine that the cluster is eligible to be assigned to the specified Prime License Manager. |
Parameter |
Type |
Help |
---|---|---|
PLMName |
String |
The Prime License Manager to which the cluster was to be assigned |
ComponentName |
String |
Name of the UC cluster that failed to be assigned |
Message |
String |
The Message given by the Alarm |
Description |
HLM Unassign Fail Alarm. |
Explanation |
Unassign a UC cluster from a Prime License Manager has failed. |
Recommended Action |
Ensure that the UC cluster is up and can be reached from the HLM. |
Parameter |
Type |
Help |
---|---|---|
PLMName |
String |
The Prime License Manager to which the component was to be unassigned |
ComponentName |
String |
Name of the UC cluster that failed to be unassigned |
Message |
String |
The Message given by the Alarm |
Description |
HLM Audit Warning Alarm. |
Explanation |
An issue has been discovered while running the HLM periodic audit. |
Recommended Action |
Check the HLM logs for further details. |
Parameter |
Type |
Help |
---|---|---|
IssueType |
String |
The type of issue that was discovered during audit |
WarningMessage |
String |
Message that describes the discovered issue |
Description |
HLM Set Deployment Mode Error Alarm. |
Explanation |
Failed to set a component deployment mode. |
Recommended Action |
Ensure that the component is reachable. |
Parameter |
Type |
Help |
---|---|---|
DeploymentMode |
String |
The deployment mode value |
ComponentName |
String |
Name of the component (Prime License Manager/Cluster) that failed to be set |
Description |
HLM Change Notify Alarm. |
Explanation |
An operation that was performed on a component is observed. |
Recommended Action |
None. |
Parameter |
Type |
Help |
---|---|---|
OperationType |
String |
Type of operation being performed on this component. |
ComponentName |
String |
Name of the component that was affected. |
Description |
The assigned cluster and Platform License Manager could be incompatible. |
Explanation |
Potential license sync failure due to the assigned cluster and Platform License Manager are incompatible in version. |
Recommended Action |
Try to assign the cluster to the Platform License Manager in same version. |
Parameter |
Type |
Help |
---|---|---|
Issue Type |
String |
The type of incompatible issue that was discovered during cluster assign. |
Description |
Generating a license report failed. |
Explanation |
HLM failed to generated the requested license reports. |
Recommended Action |
Parameter |
Type |
Help |
---|---|---|
Report Type |
enum |
The type of the requested report. |
Report Level |
enum |
The level of the requested report. |
Format Type |
enum |
The format type of the requested report. |
Message |
String |
Report fail reason. |
Description |
HLM disk space allotment exceeded. |
Explanation |
HLM license report repository disk space usage exceeded the configured value. |
Recommended Action |
Remove superfluous files using the CLI or increase the HLM disk space allotment using the CLI. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Contains the warning of HLM disk space usage. |
Description |
Failed to Initialize CHPA, a service restart is required. |
Explanation |
An issue was found during CHPA Service Initialization. |
Recommended Action |
Verify SDR and the CHPA server is setup correctly. |
Description |
Error during a CHPA operation. |
Explanation |
Error occurred when attempting to perform operation. |
Recommended Action |
See the associated Recommended Action field in the generated Alarm. |
Parameter |
Type |
Help |
---|---|---|
Server |
String |
Identity of the associated server |
ReasonText |
String |
Text indicating the reason error was generated |
RecommendedAction |
String |
Diagnostic steps to attempt to resolve the problem |
Description |
Generic Service Inventory Alarm |
Explanation |
This Alarm indicates a problem within Service Inventory has occurred. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
The Message given by the Alarm |
Description |
Service Inventory SFTP Alarm. |
Explanation |
Transfer of files from Service Inventory to destination has failed. |
Recommended Action |
Please determine that the destination host can be reached by Service Inventory and credentials are correct. |
Parameter |
Type |
Help |
---|---|---|
Destination |
String |
The destination for which the files were to be sent. |
FileName |
String |
Name of the file that failed transfer. |
Message |
String |
The message given by the Alarm. |
Description |
File History Audit Alarm. |
Explanation |
An error has occurred while running the file history audit. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
ExceptionType |
String |
The type of captured exception. |
ExceptionMessage |
String |
Message contained within the exception. |
Description |
Service Inventory Scheduler Alarm. |
Explanation |
An error has occurred while configuring the Service Inventory scheduler. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message received from the scheduler |
Description |
CUCDM Configuration Alarm |
Explanation |
Service Inventory's CUCDM configuration data has not been properly provisioned. |
Recommended Action |
Please ensure that the CUCDM credentials and settings are provisioned correctly. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message from SI explaining the configuration error. |
Description |
SI Host Configuration Alarm |
Explanation |
Service Inventory's Host configuration data has not been properly provisioned. |
Recommended Action |
Please ensure that the Service Inventory Host settings are provisioned correctly. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Message from SI explaining the configuration error. |
Description |
CUCDM Report Alarm. |
Explanation |
Service Inventory could not retrieve a report from CUCDM. |
Recommended Action |
Please ensure that the CUCDM credentials and settings are provisioned correctly. Verify connectivity between the SI host and the CUCDM host. |
Parameter |
Type |
Help |
---|---|---|
ExceptionType |
String |
The type of captured exception |
ExceptionMessage |
String |
Message contained within the exception |
Description |
File Transfer Alarm. |
Explanation |
Service Inventory file transfer caught an exception. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Error Message Received |
Description |
CUCDM Report File Processing Alarm. |
Explanation |
Service Inventory caught an exception while processing the report received from CUCDM. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Filename |
String |
The name of the file for which the error occurred |
ExceptionType |
String |
The type of captured exception |
ExceptionMessage |
String |
Message contained within the exception |
Description |
Advanced Services Plugin Alarm. |
Explanation |
Service Inventory caught an exception while running the AS Plugin script. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Command |
String |
Command called to run the AS plugin |
ReturnCode |
String |
Return Code captured from the AS plugin script |
Message |
String |
Message received from the AS plugin |
Description |
File Splitting Alarm. |
Explanation |
Service Inventory caught an exception while spitting the processed reports. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Filename |
String |
The name of the file for which the error occurred |
ExceptionMessage |
String |
Message contained within the exception |
Description |
Service Inventory Command Alarm. |
Explanation |
Service Inventory caught an exception while running an internal command. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Command |
String |
Command called internally |
ExceptionType |
String |
The type of captured exception |
ExceptionMessage |
String |
Message contained within the exception |
Description |
Service Inventory Configuration Initialization Alarm. |
Explanation |
Service Inventory caught an exception initializing the Service Inventory configuration file. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
ExceptionType |
String |
The type of captured exception |
ExceptionMessage |
String |
Message contained within the exception |
Description |
CUCDM Report Timeout Alarm. |
Explanation |
Service Inventory timed out waiting for a report from CUCDM. |
Recommended Action |
Please ensure that the CUCDM credentials and settings are provisioned correctly. Verify connectivity between the SI host and the CUCDM host. |
Parameter |
Type |
Help |
---|---|---|
AuditInterval |
String |
Audit interval in minutes at which the scheduler checks for the report file from CUCDM |
FileAttempts |
String |
Number of attempts the scheduler made to look for the file |
MinutesElapsed |
String |
Number of minutes elapsed waiting for the report from CUCDM |
Description |
UC Report Alarm. |
Explanation |
Service Inventory encountered an error while processing the UC Application report. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Error Message Received |
Description |
UC App Processing Alarm. |
Explanation |
Service Inventory was unable to gather the data necessary to process the UC Application. |
Recommended Action |
Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
UCApp |
String |
UC App undergoing processing |
Message |
String |
Error Message Received |
Description |
CHPA Connection Alarm. |
Explanation |
An exception occurred while interacting with CHPA. |
Recommended Action |
Please check the Service Inventory and CHPA logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Error Message Received |
Description |
UCPA Alarm. |
Explanation |
An exception occurred while interacting with UCPA. |
Recommended Action |
Please check the Service Inventory and UCPA logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Error Message Received |
Description |
CDM Config Alarm. |
Explanation |
Data in CDM is not correctly configured. |
Recommended Action |
Verify the configuration in CDM. Please check the Service Inventory logs for further details. |
Parameter |
Type |
Help |
---|---|---|
Message |
String |
Error Message Received |
Description |
Failed to connect to SDR. |
Explanation |
Failed to connect to SDR. |
Recommended Action |
Verify the 'Cisco CDM Database' service is running. If it is not running, start the service; if it is running, stop and then start the service. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm. |
Description |
Failed to read UCS Manager configuration data from SDR. |
Explanation |
Failed to read UCS Manager configuration data from SDR. |
Recommended Action |
Verify the 'Cisco CDM Database' service is running and verify the UCS Manager is configured correctly in Infrastructure Manager. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Configuration is missing for credentials (user ID, password) or network address. |
Explanation |
Configuration is missing for credentials (user ID, password) or network address. |
Recommended Action |
Check UCS Manager 'UCSMName' configuration in Infrastructure Mananger. Verify the correct user ID and password are configured as ADMIN credentials. Verify the correct IP address or host/domain names are configured as SERVICE_PROVIDER_SPACE. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' due to bad credentials. |
Explanation |
Failed to connect to 'UCSMName' due to bad credentials. |
Recommended Action |
Verify UCS Manager 'UCSMName' user ID and password are correctly configured as ADMIN credentials in Infrastructure Manager |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName'. Specific cause is unknown. |
Explanation |
Failed to connect to 'UCSMName'. Specific cause is unknown. |
Recommended Action |
Check the network address configuration of UCS Manager 'UCSMName' in Infrastructure Manager. Verify the correct IP address or host/domain name are configured as type SERVICE_PROVIDER_SPACE. Verify network connectivity between HCM-F and the UCS Manager. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' due to a bind exception. |
Explanation |
Failed to connect to 'UCSMName' due to a bind exception. |
Recommended Action |
This error indicates a problem on the local HCM-F server, and is typically caused when a local port is already in use. It can also happen if the local IP address is not configured, or all outbound ports are in use. First step is to restart the UCS ManagerSync service. If the problem persists, reboot the server. Be sure to do this during off-hours to avoid disrupting service. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' due to a connection exception. |
Explanation |
Failed to connect to 'UCSMName' due to a connection exception. |
Recommended Action |
Check the network address configuration of UCS Manager 'UCSMName' in Infrastructure Manager. Verify the correct IP address or host/domain names are configured as type SERVICE_PROVIDER_SPACE. Verify network connectivity between HCM-F and the UCS Manager. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' due to an unknown host error. |
Explanation |
Failed to connect to 'UCSMName' due to an unknown host error. |
Recommended Action |
Check the network address configuration of UCS Manager 'UCSMName' in Infrastructure Manager. Verify the correct host/domain names are configured as type SERVICE_PROVIDER_SPACE. Verify the DNS server is reachable from HCM-F and is configured with this hostname. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' because the host was unreachable. |
Explanation |
Failed to connect to 'UCSMName' because the host was unreachable. |
Recommended Action |
Check the network address configuration of UCS Manager 'UCSMName' in Infrastructure Manager. Verify the correct IP address or host/domain name are configured as type SERVICE_PROVIDER_SPACE. Verify network connectivity between HCM-F and the UCS Manager. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' due to a malformed URL. |
Explanation |
Failed to connect to 'UCSMName' due to a malformed URL. |
Recommended Action |
Check the network address configuration of UCS Manager 'UCSMName' in Infrastructure Manager. Verify the correct IP address or host/domain names are configured as type SERVICE_PROVIDER_SPACE. If this error persists, restart the UCS ManagerSync service. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' because the port was unreachable. |
Explanation |
Failed to connect to 'UCSMName' because the port was unreachable. |
Recommended Action |
Check port configuration of UCS Manager 'UCSMName' in Infrastructure Manager. Verify the correct port number is configured, or no port is configured if not needed to access the UCS Manager. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' due to a remote exception. |
Explanation |
Failed to connect to 'UCSMName' due to a remote exception. |
Recommended Action |
Check the network address configuration of UCS Manager 'UCSMName' in Infrastructure Manager. Verify the correct IP address or host/domain names are configured as type SERVICE_PROVIDER_SPACE. Verify network connectivity between HCM-F and the UCS Manager. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' due to a connection timeout. |
Explanation |
Failed to connect to 'UCSMName' due to a connection timeout. |
Recommended Action |
This error can happen if the UCS Manager is down or the wrong IP address or hostname is configured. Verify 'UCSMName' is up and operational, and can be reached over the network. Also verify the correct IP address or host/domain names are configured as a SERVICE_PROVIDER_SPACE network address. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' because the connection was refused. |
Explanation |
Failed to connect to 'UCSMName' because the connection was refused. |
Recommended Action |
Check the network address configuration of UCS Manager 'UCSMName' in Infrastructure Manager. Verify the correct IP address or host/domain names are configured as type SERVICE_PROVIDER_SPACE. Verify the UCS Manager services are running on 'UCSMName'. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failed to connect to 'UCSMName' due to a read timeout. |
Explanation |
Failed to connect to 'UCSMName' due to a read timeout. |
Recommended Action |
This error can happen if the UCS Manager is busy or the network connection is slow. Check the number of users logged on to 'UCSMName' and if there are many users, retry the operation when there are fewer users. Check the network between the HCM-F server and 'UCSMName' and verify that the round-trip time is below 1 second (ping is useful for this). |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Maximum login sessions have been exceeded for 'UCSMName'. |
Explanation |
Maximum login sessions have been exceeded for 'UCSMName'. |
Recommended Action |
Disable auto-sync for 'UCSMName' and wait 10 minutes to allow other sessions to expire. Then enable auto-sync or perform a manual sync. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Login session was not found for 'UCSMName'. |
Explanation |
Login session was not found for 'UCSMName'. |
Recommended Action |
If auto-sync is enabled, no action is necessary; a new session will be created automatically. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Error parsing a response from 'UCSMName'. |
Explanation |
Error parsing a response from 'UCSMName'. |
Recommended Action |
If this error persists, examine the UCS ManagerSync log files for further troubleshooting. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Failure logging in to 'UCSMName'; the specific cause is unknown. |
Explanation |
Failure logging in to 'UCSMName'; the specific cause is unknown. |
Recommended Action |
If this error persists, examine the UCS ManagerSync log files for further troubleshooting. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Successfully connected to 'UCSMName' but failed to start updating. |
Explanation |
Successfully connected to 'UCSMName' but failed to start updating. |
Recommended Action |
Stop and then start the UCS ManagerSync service. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Sync did not complete within 5 minutes. |
Explanation |
Sync did not complete within 5 minutes. |
Recommended Action |
Stop and then start the UCS ManagerSync service. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Unable to securely connect to "UCSMName" because of hostname mismatch. |
Explanation |
Unable to securely connect to "UCSMName" because of a mismatch between the hostname and the CN in its certificate. |
Recommended Action |
Ensure that the configured name ("UCSMName") matches the CN indicated in its security certificate. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Unable to securely connect to "UCSMName" because a local certificate matching the incoming certificate was not found. |
Explanation |
Unable to securely connect to "UCSMName" because a local certificate matching the incoming certificate was not found. |
Recommended Action |
Ensure UCSMName's certificate has been imported into the local tomcat trusted keystore. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Unable to securely connect to "UCSMName" because it did not recognize the ssl communication. |
Explanation |
Unable to securely connect to "UCSMName" because of a mismatch between it did no recognize our ssl communication. |
Recommended Action |
Ensure that "UCSMName" has secure communication enabled or disable local certificate requirement for UCSManagerSync service. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Unknown exception. |
Explanation |
Unknown exception. |
Recommended Action |
Stop and then start the UCS ManagerSync service. |
Parameter |
Type |
Help |
---|---|---|
UCSMName |
String |
Name of the UCS Manager related to the Alarm |
Description |
Two virtual machines (VMs) with the same name were detected during a vCenter sync operation, one of them will be deleted from NameOfVCenterOwningOldDuplicateVM. |
Explanation |
HCS requires that virtual machines have unique names to ensure service assurance can accurately perform service impact analysis. The previous copy of the duplicate VM will be deleted and the new copy will be created in the SDR database. This may be caused by the Site Recovery Manager (SRM) which will migrate a virtual machine to a backup vCenter during disaster recovery. This is a valid scenario and the removal of the old VM from the SDR database is acceptable. However, if SRM is not deployed, then this alarm may signify improper configuration. Verify that all of the virtual machines configured in the two vCenters listed in the alarm have unique names. |
Recommended Action |
If a Site Recovery Manager operation is in progress, no action necessary. If SRM is not deployed or operational, then check both vCenters listed in the alarm and ensure all virtual machines have globally unique names. |
Parameter |
Type |
Help |
---|---|---|
Name Of VCenter Owning Old Duplicate VM |
String |
Name of the VCenter which owns the duplicate Virtual Machine that will be deleted. |
Name Of VCenter Owning New Duplicate VM |
String |
Name of the VCenter which owns the duplicate Virtual Machine that will be created. |
Name Of Duplicate VM |
String |
Name of the duplicate VM. |
Description |
Failed to connect to SDR. |
Explanation |
Failed to connect to SDR. |
Recommended Action |
Verify the 'Cisco CDM Database' service is running. If it is not running, start the service; if it is running, stop and then start the service. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to read VCenter configuration data from SDR. |
Explanation |
Failed to read VCenter configuration data from SDR. |
Recommended Action |
Verify the 'Cisco CDM Database' service is running and verify the VCenter is configured correctly in Infrastructure Manager. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Configuration is missing for credentials (user ID, password) or network address. |
Explanation |
Configuration is missing for credentials (user ID, password) or network address. |
Recommended Action |
Check VCenter 'VCenterName' configuration in Infrastructure Mananger. Verify the correct user ID and password are configured as ADMIN credentials. Verify the correct IP address or host/domain names are configured as SERVICE_PROVIDER_SPACE. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' due to bad credentials. |
Explanation |
Failed to connect to 'VCenterName' due to bad credentials. |
Recommended Action |
Verify VCenter 'VCenterName' user ID and password are correctly configured as ADMIN credentials in Infrastructure Manager. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName'. Specific cause is unknown. |
Explanation |
Failed to connect to 'VCenterName'. Specific cause is unknown. |
Recommended Action |
Check the network address configuration of VCenter 'VCenterName' in Infrastructure Manager. Verify the correct IP address or host/domain name are configured as type SERVICE_PROVIDER_SPACE. Verify network connectivity between HCM-F and the VCenter. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' due to a bind exception. |
Explanation |
Failed to connect to 'VCenterName' due to a bind exception. |
Recommended Action |
This error indicates a problem on the local HCM-F server, and is typically caused when a local port is already in use. It can also happen if the local IP address is not configured, or all outbound ports are in use. First step is to restart the VCenterSync service. If the problem persists, reboot the server. Be sure to do this during off-hours to avoid disrupting service. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' due to a connection exception. |
Explanation |
Failed to connect to 'VCenterName' due to a connection exception. |
Recommended Action |
Check the network address configuration of VCenter 'VCenterName' in Infrastructure Manager. Verify the correct IP address or host/domain names are configured as type SERVICE_PROVIDER_SPACE. Verify network connectivity between HCM-F and the VCenter. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' due to an unknown host error. |
Explanation |
Failed to connect to 'VCenterName' due to an unknown host error. |
Recommended Action |
Check the network address configuration of VCenter 'VCenterName' in Infrastructure Manager. Verify the correct host/domain names are configured as type SERVICE_PROVIDER_SPACE. Verify the DNS server is reachable from HCM-F and is configured with this hostname. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' because the host was unreachable. |
Explanation |
Failed to connect to 'VCenterName' because the host was unreachable. |
Recommended Action |
Check the network address configuration of VCenter 'VCenterName' in Infrastructure Manager. Verify the correct IP address or host/domain name are configured as type SERVICE_PROVIDER_SPACE. Verify network connectivity between HCM-F and the VCenter. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' due to a malformed URL. |
Explanation |
Failed to connect to 'VCenterName' due to a malformed URL. |
Recommended Action |
Check the network address configuration of VCenter 'VCenterName' in Infrastructure Manager. Verify the correct IP address or host/domain names are configured as type SERVICE_PROVIDER_SPACE. If this error persists, restart the VCenterSync service. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' because the port was unreachable. |
Explanation |
Failed to connect to 'VCenterName' because the port was unreachable. |
Recommended Action |
Check port configuration of VCenter 'VCenterName' in Infrastructure Manager. Verify the correct port number is configured, or no port is configured if not needed to access the VCenter. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' due to a remote exception. |
Explanation |
Failed to connect to 'VCenterName' due to a remote exception. |
Recommended Action |
Check the network address configuration of VCenter 'VCenterName' in Infrastructure Manager. Verify the correct IP address or host/domain names are configured as type SERVICE_PROVIDER_SPACE. Verify network connectivity between HCM-F and the VCenter. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' due to a connection timeout. |
Explanation |
Failed to connect to 'VCenterName' due to a connection timeout. |
Recommended Action |
This error can happen if the VCenter is down or the wrong IP address or hostname is configured. Verify 'VCenterName' is up and operational, and can be reached over the network. Also verify the correct IP address or host/domain names are configured as a SERVICE_PROVIDER_SPACE network address. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' because the connection was refused. |
Explanation |
Failed to connect to 'VCenterName' because the connection was refused. |
Recommended Action |
Check the network address configuration of VCenter 'VCenterName' in Infrastructure Manager. Verify the correct IP address or host/domain names are configured as type SERVICE_PROVIDER_SPACE. Verify the VCenter services are running on 'VCenterName'. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failed to connect to 'VCenterName' due to a read timeout. |
Explanation |
Failed to connect to 'VCenterName' due to a read timeout. |
Recommended Action |
This error can happen if the VCenter is busy or the network connection is slow. Check the number of users logged on to 'VCenterName' and if there are many users, retry the operation when there are fewer users. Check the network between the HCM-F server and 'VCenterName' and verify that the round-trip time is below 1 second (ping is useful for this). |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Maximum login sessions have been exceeded for 'VCenterName'. |
Explanation |
Maximum login sessions have been exceeded for 'VCenterName'. |
Recommended Action |
Disable auto-sync for 'VCenterName' and wait 10 minutes to allow other sessions to expire. Then enable auto-sync or perform a manual sync. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Login session was not found for 'VCenterName'. |
Explanation |
Login session was not found for 'VCenterName'. |
Recommended Action |
If auto-sync is enabled, no action is necessary; a new session will be created automatically. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Error parsing a response from 'VCenterName'. |
Explanation |
Error parsing a response from 'VCenterName'. |
Recommended Action |
If this error persists, examine the VCenterSync log files for further troubleshooting. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Failure logging in to 'VCenterName'; the specific cause is unknown. |
Explanation |
Failure logging in to 'VCenterName'; the specific cause is unknown. |
Recommended Action |
If this error persists, examine the VCenterSync log files for further troubleshooting. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Successfully connected to 'VCenterName' but failed to start updating. |
Explanation |
Successfully connected to 'VCenterName' but failed to start updating. |
Recommended Action |
Stop and then start the VCenterSync service. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Sync did not complete within 5 minutes. |
Explanation |
Sync did not complete within 5 minutes. |
Recommended Action |
Stop and then start the VCenterSync service. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
Unknown exception. |
Explanation |
Unknown exception. |
Recommended Action |
Stop and then start the VCenterSync service. |
Parameter |
Type |
Help |
---|---|---|
VCenterName |
String |
Name of the VCenter related to the Alarm |
Description |
The current total number of processes and threads has exceeded the maximum number of tasks configured for Cisco RIS Data Collector service parameter. This situation could indicate some process is leaking or some process has thread leaking. |
Explanation |
The current total number of processes and threads has exceeded the maximum number of tasks. This situation could indicate some process is leaking or some process has thread leaking. |
Recommended Action |
Check the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads, to see if the parameter has been set to a low value. If it has been set to a low value, set the value higher or use the default value. Another possible action is that when a new Cisco product is integrated into Cisco Unified Communications Manager (Unified CM), new processes or threads are added to the system. Even in the normal process load situation, it's possible that the total number of processes and threads has exceeded the configured or default value of the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. Set that parameter to the maximum allowed value. You can also review the details of this alarm to check the ProcessWithMostThreads description and the ProcessWithMostInstances description to discover which processes have the most threads and the most instances. Determine whether these values are reasonable for this process; if not, contact the owner of the process to troubleshoot the reasons why the thread count or the number of process instances is so high. It is also possible that Cisco RIS Data Collector sent a false alarm, which would indicate a defect in the Cisco RIS Data Collector service. To determine if this is the cause of the alarm - after you have checked all the other recommended actions described here - use RTMT to check the System object for performance counters Total Threads and Total Processes to confirm that the values in those counters do not exceed the value configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. If the counters do not show a value that is higher than what is configured in the service parameter, restart Cisco RIS Data Collector service. If the alarm persists after restarting the service, go to Cisco Unified Serviceability and collect trace logs (Trace > Configuration) for Cisco Syslog, Cisco RIS Data Collector, Cisco AMC Service, and Cisco RIS Perfmon Logs and contact Cisco Technical Assistance Center (TAC) for detailed assistance. |
Parameter |
Type |
Help |
---|---|---|
NumberOfProcesses |
String |
Number of processes |
NumberOfThreads |
String |
Number of threads |
Reason |
String |
Reason |
ProcessWithMostInstances |
String |
Process with the most instances |
Description |
The current total number of processes and threads is less than the maximum number of tasks configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. |
Explanation |
The current total number of processes and threads is less than the maximum number of tasks that has been configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. This can occur because a product which was integrated into Cisco Unified Communications Manager has been disabled or deactivated, which reduces the total number of processes and threads running on the system. Another cause for the number of processes or thread to decrease is that one or more processes has been stopped, which reduces the total number of processes and threads running on the system. |
Recommended Action |
This alarm is for information purposes only; no action is required. |
Parameter |
Type |
Help |
---|---|---|
NumberOfProcesses |
String |
Number of processes |
NumberOfThreads |
String |
Number of threads |
Reason |
String |
Reason |
Description |
RTMT Alert |
Explanation |
A Real-Time Monitoring Tool (RTMT) process in the AMC service uses the alarm mechanism to facilitate delivery of RTMT alerts in RTMT AlertCentral or via email. |
Recommended Action |
Check AlertCentral in RTMT or any alerts that you have received via email to determine what issue has occurred and learn the recommended actions to resolve it. In AlertCentral, right-click the alert to open the alert information. |
Parameter |
Type |
Help |
---|---|---|
AlertName |
String |
Alert name |
AlertDetail |
String |
Alert details |
Description |
Alert Email Notification Failure. |
Explanation |
Alert notification mechanism using e-mails has failed. |
Recommended Action |
Email notification of alerts failed due to a mis-configured SMTP Settings/SMTP server down. Check SMTP Server configuration and examine the AMC service log files to determine the exact reason for failure. |
Parameter |
Type |
Help |
---|---|---|
FailureReason |
String |
Failure reason |
Description |
The configured Syslog alarm/message string had matched. |
Explanation |
Cisco Syslog Agent had detected an alarm which matches the configured string. |
Recommended Action |
Take the necessary action based on the received string matched event. |
Parameter |
Type |
Help |
---|---|---|
StringMatch |
String |
MatchedString |
MatchedEvent |
String |
MatchedEvent |
Description |
Hardware failure alarm is received. |
Explanation |
Cisco Syslog Agent had detected a hardware failure alarm. |
Recommended Action |
Take the necessary action based on the received hardware failure event. |
Parameter |
Type |
Help |
---|---|---|
hwStringMatch |
String |
hwStringMatch |
Description |
The configured Syslog alarm/message severity had matched. |
Explanation |
Cisco Syslog Agent had detected an alarm which matches the configured severity. |
Recommended Action |
Take the necessary action based on the received hardware failure event. |
Parameter |
Type |
Help |
---|---|---|
SeverityMatch |
String |
MatchedSeverity |
MatchedEvent |
String |
MatchedEvent |
Description |
The percentage of used disk space in the log partition has exceeded the configured low water mark. |
Explanation |
The percentage of used disk space in the log partition has exceeded the configured low water mark. |
Recommended Action |
Login into RTMT and check the configured threshold value for LogPartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each of the application in trace configuration page under CCM Serviceability. If the number of configured traces/logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old using cli "file delete" or using Remote Browse from RTMT Trace and Log Central function. |
Parameter |
Type |
Help |
---|---|---|
UsedDiskSpace |
String |
Used disk space |
MessageString |
String |
Additional Message [Optional] |
Description |
The percentage of used disk space in the log partition has exceeded the configured high water mark. |
Explanation |
The percentage of used disk space in the log partition has exceeded the configured high water mark. Some of the core file and/or trace files will be purged until the percentage of used disk space in the log partition gets below the configured low water mark. |
Recommended Action |
Login into RTMT and check the configured threshold value for LogPartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the 1st alert, check for the disk usage for Common partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in LogPartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition. |
Parameter |
Type |
Help |
---|---|---|
UsedDiskSpace |
String |
Used disk space |
MessageString |
String |
Additional Message [Optional] |
Description |
The search string has been found in the log file. |
Explanation |
Trace and Log Central has found the search string that the user has configured. |
Recommended Action |
If sysadmin is interested in collecting the traces around the time of generation of alert, use Trace and Log Central to collect the traces for that service. |
Parameter |
Type |
Help |
---|---|---|
SearchString |
String |
Search string |
Description |
The number of Log Collection Jobs have exceeded the allowed limit |
Explanation |
The number of concurrent trace collection from the server has exceeded the allowed limit of trace collection. The allowed limit is defined in the documentation for Trace and Log Central, however this limit can not be changed by sysadmin. |
Recommended Action |
Cancel one or more of the currently running queries and try again to configure the trace collection. |
Parameter |
Type |
Help |
---|---|---|
JobType |
String |
Job type |
Description |
An error occurred while executing scheduled collection. |
Explanation |
Scheduled collection encountered an error during execution. |
Recommended Action |
Review configuration for scheduled collection job under Job Status window. |
Parameter |
Type |
Help |
---|---|---|
JobID |
String |
JobID |
Reason |
String |
Reason |
Description |
One or more new core dump files have been found in the system. |
Explanation |
A component crashed and generated a core dump. Use admin cli or RTMT to fetch the backtrace. |
Recommended Action |
This serious internal error should be investigated by the Cisco Technical Assistance Center (TAC). Before contacting TAC, log in to cli on CCM serve and run "active analyze core file name" to generate the backtrace of the core dump. The core file name is listed in the alert details. After you execute the analyze command, collect the backtrace using cli command "file get activelog analyze" or "Collect Traces" option in RTMT. Send these backtraces to Cisco TAC for further analysis. |
Parameter |
Type |
Help |
---|---|---|
TotalCoresFound |
String |
Total cores found |
CoreDetails |
String |
Core details |
Core1 |
String |
Core 1 |
Core2 |
String |
Core 2 |
Core3 |
String |
Core 3 |
Core4 |
String |
Core 4 |
Core5 |
String |
Core 5 |
Core6 |
String |
Core 6 |
Description |
The percentage of used disk space in the spare partition has exceeded the configured low water mark. |
Explanation |
The percentage of used disk space in the spare partition has exceeded the configured low water mark. |
Recommended Action |
Log in to RTMT and check the configured threshold value for SparePartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each application in the trace configuration page under CCM Serviceability. If the number of configured traces/logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old. Clean up the traces using cli "file delete" or using Remote Browse from RTMT Trace & Log Central function. |
Parameter |
Type |
Help |
---|---|---|
UsedDiskSpace |
String |
Used disk space |
MessageString |
String |
Additional Message [Optional]. |
Description |
The percentage of used disk space in the spare partition has exceeded the configured high water mark. |
Explanation |
The percentage of used disk space in the spare partition has exceeded the configured high water mark. Some of the trace files will be purged until the percentage of used disk space in the spare partition falls below the configured low water mark |
Recommended Action |
Log in to RTMT and check the configured threshold value for SparePartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the first alert, check the disk usage for Spare partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in SparePartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition. |
Parameter |
Type |
Help |
---|---|---|
UsedDiskSpace |
String |
Used disk space |
MessageString |
String |
Additional Message [Optional]. |