Cisco MCS-7825-H3-IPC1 Service Guide - Page 131

Chapter 3 Managing and Monitoring the Health of Cisco Unified Communications Manager Systems Platform Monitoring sda2 sda3 sda4 sda5 sda6 0.00 0.00 0.00 0.00 2.71 0.00 0.00 0.00 0.08 14.79 0.00 0.00 0.00 0.01 0.20 0.00 0.00 0.00 0.01 6.84 0.00 0.00 0.00 0.04 23.26 0.00 0.000.00 0.00 0.73 173.24 0.00 0.00 0.00 5.28 0.00 0.00 0.02 0.37 11.63 86.62 10.88 0.00 1.83 64.43 27.92 0.00 1.88 0.00 0.00 0.02 The following CLI can be used to monitor and manage intracluster connections: • admin:utils dbreplication status • admin:utils dbreplication repair all/nodename • admin:utils dbreplication reset all/nodename • admin:utils dbreplication stop • admin:utils dbreplication dropadmindb • admin:utils dbreplication setrepltimeout • show tech dbstateinfo • show tech dbinuse • show tech notify • run sql 2.20 2.20 1.88 0.00 1.67 1.67 283.91 69.81 2.98 0.61 Hardware Migration Customers may wish to migrate their Cisco Unified CM to more powerful hardware, either to prepare for upgrading to a later Cisco Unified CM release that does not support the older hardware, or just to leverage capabilities only available in the more powerful hardware, such as increases in capacity/performance or RAID. The procedure is to backup from the old hardware, install the same Cisco Unified CM release to the new hardware, then restore on the new hardware. Migrating to more powerful hardware may require a migration SKU to cover royalties Cisco owes to third-parties. If you are considering this, have your account team check the Guide to Cisco Unified CM Upgrades and Server Migrations, which is a supplement to the Cisco Unified CM Ordering Guide. Platform Security The following topics are covered in this section: • Locked-down System, page 3-32 • Cisco Security Agent Support, page 3-32 • Security Patching and Updating, page 3-32 • Role-Based Access Control, page 3-32 OL-22523-01 Cisco Unified Communications Manager Managed Services Guide 3-31