The following checks involve checking all or some nodes (Subscriber and Publisher) in the UC application cluster for the selected
customer.
Even if one node fails while executing a check, the entire check fails and cross-mark appears in the Status column. See the Recommended Action and perform the recommended action if there is a failure and execute the check again.
Available Common Partition Space
Checks for the availability of minimum 25 GB of common partition space.
Check
|
Displays the available space in the cluster.
|
Check Result
|
These are the results for the check:
-
Application Name: Specifies the node name.
-
Available Space: Specifies the available space in the common partition.
-
Used Space: Specifies the used space in the common partition.
-
Status:
|
Status and Recommended Action
|
If the check fails, clear the space so that the minimum available partition space is 25 GB.
Run the show diskusage common command to check the amount of used space.
|
CLI Diagnostics
Runs multiple tests to verify the disk status, Tomcat process status, and NTP status and so on. Log into HCM-F interface and
run the utils diagnose test command on all nodes within the cluster with the admin credentials.
Check
|
Displays result of the tests run by the utils diagnose test command.
|
Check Result
|
The results of the check are:
-
Application Name: Specifies the node name.
-
Test Name: Specifies the test run by utils diagnose test command.
-
Result: Indicates if the test passed or failed.
-
Status:
-
Pass: Indicates that the tests run as part of utils diagnose test command passed or skipped in the cluster.
-
Fail: Indicates that the test executed as part of utils diagnose test command failed in the cluster.
|
Status and Recommended Action
|
If the check fails, check the node connectivity.
|
CTI Device Count
Records the total number of CTI devices, which includes CTI ports and Route Points.
Use this information for comparison post upgrade.
Check
|
Displays the CTI device count.
|
Check Result
|
The results of the check are:
-
Application Name: Specifies the node name.
-
CTI Device Status: Collects CTI device count for the following status:
-
Registered
-
Partially Registered
-
Unregistered
-
Rejected
-
CTI Device Count: Specifies the CTI device count for the preceding status.
-
Status:
|
Status and Recommended Action
|
If the status fails, check cluster reachability and the credentials using the Cisco Unified CM user interface.
|
CTI Route Point Status
Displays the CTI route point status and the IP address of the third-party application to which the route point is registered.
Use this information for comparison post upgrade.
Check
|
Displays the CTI Route point name, Route point status and IP address of the application to which the route point is registered.
|
Check Result
|
The results of the check are:
-
Application Name: Specifies the route point name.
-
CTI Route Status: Displays the CTI route point status:
-
IP Address: Specifies the IP address of the third-party application that is registered.
|
Status and Recommended Action
|
If the status fails, check cluster reachability and the credentials using the Cisco Unified CM user interface.
|
Certificate Status Information
Displays the Certificate information that is collected from the Certificate Monitor, and verifies the certificate status information.
Certificates are sorted based on the number of days to expire.
Check
|
Displays the certificate status.
|
Check Result
|
|
Status and Recommended Action
|
If the certificates that are collected by certificate monitor is older than seven days, then the overall status fails. Check
the certificate validity and Recommended Actions.
|
Check Cluster Status
Checks if the publisher server has Primary status and subscriber server has Secondary status. This check is applicable only
for Cisco Unity Connection.
Check
|
Displays the publisher and subscriber server name and status. |
Result
|
Following are the result details:
-
Application Name: Specifies the node name. It is applicable only for publisher.
-
Server Name: Specifies the publisher and subscriber server name.
-
Server State: Specifies that one server node has publisher (Primary status) and the other has subscriber (Secondary status).
-
Internal State: Specifies if the server is active or inactive.
-
Status:
-
Pass: Indicates that one node of the cluster is in Primary role and the other node is in secondary role. Also, both the nodes
are online.
-
Fail: Indicates failure for the following server states:
|
Status and Recommended Action
|
Check the Recommended Action for failure.
Run the show cuc cluster status command, to view the cluster status.
|
Cluster Version Information
Checks if all the applications for the selected cluster are available.
Check
|
Displays the application version and cluster node count.
|
Check Result
|
Following are the result details:
-
Application Name: Specifies the node name.
-
Application Version: Specifies the UC application version installed on the node.
-
Cluster Nodes Count: Specifies the number of nodes in the cluster. This entry is available only for publisher node.
-
Status:
|
Status and Recommended Action
|
If the check fails, check node connectivity and credentials. Add the missing applications for the cluster.
Run the show version active command, to view the version information and run the show network cluster command to get details of the cluster.
|
DB Consistency State
Checks the consistency of tables and validates indexes for the unitydirdb, unitydyndb, unitymbxdb1, and unityrptdb database
in Unity Connection. This check runs on all nodes in the cluster.
Use this information from the check for comparison post upgrade.
Check
|
Checks the consistency of tables and validates indexes for the database in Unity Connection. Run the show cuc dbconsistency <dbname> command on each database using the HCM-F admin credentials.
|
Check Result
|
These are result for the check:
|
Status and Recommended Action
|
If the check fails, check the table for inconsistencies, disabled indexes or invalid index entries.
Run these commands to check for inconsistencies:
-
show cuc dbconsistency unitydirdb
-
show cuc dbconsistency unitydyndb
-
show cuc dbconsistency unityrptdb
-
show cuc dbconsistency unitymbxdb1
|
Disaster Recovery System Backup
Checks if Disaster Recovery System (DRS) is configured and backup is complete.
Check
|
Displays the feature considered for backup with their status.
|
Check Result
|
These are the results for the check:
-
Application name: Specifies the node name.
-
Backup Filename: Specifies the backup filename with file extension as .tar.
-
Features: Lists the backup features separated by comma.
-
Backup Status: Specifies backup status with the percentage completed. Displays the percentage of backup completed, if the
backup is in progress.
-
Status:
|
Status and Recommended Action
|
If the status fails, check if DRS is configured and run the scheduled or manual backup on all features.
Run the utils disaster_recovery status backup command to check the backup status.
|
Enterprise Service Parameters
Displays all the enterprise service parameters for Unified Communications Manager and IM and P.
Check
|
Collects the service parameter values.
|
Check Result
|
These are the results for the check:
-
Application Name: Specifies the node name.
-
Service Parameter: Specifies the service parameter name and the service name separated by PIPE (|||). Format of the output
is <Service Parameter Name>||| <Service Name>.
-
Value: Specifies present value of the service parameter.
-
Status:
|
Status and Recommended Action
|
If the status fails, then check if the nodes in the selected cluster are reachable from HCM-F.
Run the show tech params enterprise command, to view the service parameters that are configured for each of the services.
|
Health of Network Within the Cluster
Checks the network reachability among nodes in the selected cluster.
Check
|
Displays the node name and its reachability status.
|
Check Result
|
These are the results for the check:
|
Status and Recommended Action
|
If the check fails, check the node connectivity and credentials.
Log into each cluster node and run the utils network ping <node-host-name> command to check the network connectivity with the other nodes.
|
Installed COP Files
Checks if the required COP files are available for the upgrade.
The required COP file while upgrading from Cisco Unity Connection Release 10(x)/11(x) to 12.5(x) is ciscocm.cuc_upgrade_12_0_v1.2.k3.cop.
Check
|
Displays the COP files available in the cluster.
|
Check Result
|
These are the results for the check:
|
Status and Recommended Action
|
If the check fails, install the required COP files for upgrading Cisco Unified Communications Manager. Run the show version active command to check the version of the COP file.
|
LDAP Details
Checks the last sync status of all LDAPs and their network connectivity.
Check
|
Displays LDAPs network connectivity and last sync status.
|
Check Result
|
These are the results for the check:
-
Application Name: Specifies the node name.
-
LDAP Server: Specifies the LDAP server name.
-
LDAP Status: Specifies the sync status and connectivity of all the LDAPs.
-
Status:
|
Status and Recommended Action
|
If LDAP sync fails, update the LDAP credentials and rerun the sync. If LDAP is not in network, add LDAP to the network. Log
into Cisco Unified CM Admin page and check the LDAP configuration and its network connectivity.
|
List of Services
Checks and displays the status all the services.
Check
|
Displays the status all the services.
|
Check Result
|
These are the results for the check:
-
Application Name: Specifies the node name.
-
Service Name: Lists the services available in the cluster.
-
Service Status: Specifies if the service is started or if it is stopped.
-
Status:
|
Status and Recommended Action
|
If the check fails, check the cluster credentials and its reachability.
For Cisco Emergency Responder, check if the SNMP master Agent is running else the check fails.
Run the utils service list command to display the status of all the services present on cluster nodes.
|
Network Connectivity (DNS, SMTP, and NTP)
Checks if SMTP and DNS (Primary and Secondary) are configured and reachable. The DNS reachability and SMTP reachability fields
display the server address along with the reachability status. The NTP status shows whether the UC application is synchronized
with the configured NTP servers.
Note |
The check ignores the status, if DNS, SMTP or NTP protocols are not configured.
|
Check
|
Displays the DNS (Primary and Secondary), SMTP reachability status along with the NTP synchronization status.
|
Check Result
|
Following are the result details for the check:
-
Application Name: Specifies the node name.
-
DNS Reachability: Specifies the DNS configuration and reachability status. Only if DNS is configured, Primary and Secondary
DNS reachability status are displayed.
-
SMTP Reachability: Specifies the SMTP configuration and reachability status.
-
NTP Status: Specifies the UC application synchronization with the NTP server.
-
Status:
|
Status and Recommended Action
|
If the check fails, check the network connectivity with the configured DNS and SMTP. Diagnose NTP server configuration using
the diagnostic modules.
-
Run the show network eth0 command to view details on the configured DNS server and run the utils network host <node-host-name> command to check the connectivity with the DNS.
-
Run the show smtp command to view details of the configured SMTP server.
-
Run the utils ntp status command to view details of the configured NTP server.
|
Phone Count
Displays the phone count with status.
Use this information for comparison post upgrade.
Check
|
Displays the phone count with status.
|
Check Result
|
Following are the result details for the check:
-
Application Name: Specifies the node name.
-
Phone Status: Collects phone count for the following phone status:
-
Registered
-
Partially Registered
-
Rejected
-
UnRegistered
-
Phone Count: Specifies the phone count for the preceding status.
-
Status
|
Status and Recommended Action
|
If the status fails, check if the node is reachable from HCM-F and run the check again.
|
Port Information
Displays the active ports and the total ports that are configured on the nodes. This check runs on all nodes in the cluster
and is applicable only to Cisco Unity Connection.
Use this information for comparison post upgrade.
Check
|
Displays the active ports and the total ports that are configured on the nodes.
|
Check Result
|
Following are the result details for the check:
|
Status and Recommended Action
|
If the check fails, check the connectivity to Cisco Unity Connection, administrator credentials, node version, and test the
multiple network address.
|
Run Pre-Upgrade Test
Performs the pre-upgrade checks and displays the result. This check is applicable only for Cisco Unity Connection.
Check
|
Performs the pre-upgrade checks and displays the result.
|
Result
|
-
Application Name: Specifies the node name.
-
Test name: Lists the executed tests:
-
Result: Specifies the status of the tests that is listed in the Test Name.
-
Status:
|
Status and Recommended Action
|
Check the Recommended Actions to understand the failure reason.
Run the run cuc preupgrade test command to execute the pre-upgrade check.
|
State of Database Replication
Checks the status of the database replication between publisher and subscriber nodes for Cisco Unified Communications Manager
and IM and Presence.
Check
|
Displays the status of the database replication between publisher and subscriber nodes for Cisco Unified Communications Manager
and IM and P.
|
Check Result
|
These are the details of the check:
|
Status and Recommended Action
|
If the status fails, check the connectivity between publisher and subscriber nodes in the cluster. Also, check the reachability
of cluster from HCM-F.
-
To trigger the database replication, run the utils dbreplication status command.
-
To check the status of the triggered database replication, run the utils dbreplication runtimestate command.
Ensure that the output displays “(2) Setup Completed” status for all the cluster nodes.
|
SIP Trunk Information
Checks if the configured SIP Trunks are in service, and the destination is reachable.
Use this information for comparison post upgrade.
Check
|
Records the total number of SIP trunks that are configured in the network.
|
Check Result
|
These are the result of the check:
-
Trunk Name: Specifies the trunk name.
-
Destination Detail: Specifies the IPV6/IPV4 address of the destination, if it is configured.
Note
|
The Destination Detail displays the SIP Trunk Service type name for these trunk types: Call Control Discovery, Extension Mobility
Cross Cluster, and Cisco Intercompany Media Engine instead of the destination address.
|
-
Trunk Status:
|
Status and Recommended Action
|
If the check fails, see the Verify & Troubleshoot section in these guides:
|
Note |
The report contains SIP Security Profile Properties, SIP Profile Properties, and Recording enabled information along with
the SIP Trunk Name, Status, and Destination details.
|
Syslog Information
Checks if the Syslog Configuration parameters are configured, and the remote servers are reachable.
Use this information for comparison post upgrade.
Check
|
Displays the Syslog parameters that are configured in the Cisco Unified CM Administrator user interface for message logging.
|
Check Result
|
The results of the check are:
|
Status and Recommended Action
|
If the status fails, run these commands from the Cisco Unified CM CLI interface:
|
VCenter and ESXi and UCS Details
Collects the information about ESXi (host configuration) for understanding the supported and unsupported versions of vCenter,
ESXi and VM hardware.
Check
|
Use this information to understand the supported and unsupported versions.
|
Check Result
|
Following are the result details:
-
Application Name: Specifies the node name.
-
ESXi/Host Configuration: Displays the following information:
-
VCenter version
-
ESXi version
-
VM hardware version
-
Blade model
-
VM Tools running
-
Pass: Indicates that the node was reachable for collection.
-
Fail: Indicates that the node was not reachable for collection.
|
Status and Recommended Action
|
If the check fails, check the node connectivity and credentials.
|
VM Configurations
Checks the VM configuration and verifies if the OVA is compatible with the target upgrade version for each of the UC applications.
Check
|
Use this information to understand if the VM configuration meets the target upgrade requirements.
|
Check Result
|
Following are the result details:
-
Application Name: Specifies the node name.
-
VM Configuration: Displays the following information:
-
Users—Displays the number of licensed users and the maximum number of supported users for the VM configurations when the publisher
node is Unified CM. For all other nodes, it displays the maximum number of supported users related to the VM configuration.
-
Actual—Displays the current VM configuration information such as Number of CPU, Memory in GB, Hard Disk Size in GB.
-
Required—Displays the required VM configuration information such as Number of CPU, Memory in GB, Hard Disk Size in GB.
-
Pass: Indicates that the node meets the requirements.
-
Fail: Indicates that the node does not meet the requirement and must be re-configured before you trigger an upgrade.
Note
|
The OVA check compares the current ova type (small,medium,large) in the HCS environment with the corresponding ova type in
the targeted upgrade version.
|
|
Status and Recommended Action
|
If the check fails, check the VM requirement for each UC application using these links:
|