Cisco Cisco Unified MeetingPlace 7.0 Guida Alla Risoluzione Dei Problemi

Changes to either the software workload or the physical hardware, to troubleshoot or resolve
application performance problems. Examples of when these changes might be required are UC VM
receiving insufficient CPU, Memory, network, disk capacity or storage IOPS from the hardware.

• 

Examples of what these changes look like in an actual deployment are listed below.

Software: temporary power-down of non-critical VMs to facilitate performance
troubleshooting

♦ 

Software: move critical VMs and/or non-critical VMs to alternate virtualization host /
physical server as temporary or permanent solution.

Temporarily reduce the number of virtual machines running on a host if Cisco deems
necessary for troubleshooting purposes.

◊ 

Permanently reduce the number of virtual machines running on a host if Cisco
determines the host is overloaded.

◊ 

Splitting a dense UC app VM into multiple less-dense VMs, then moving those
less-dense VMs to alternate host. E.g. splitting a CUCM 10K user OVA into multiple
CUCM 7.5K user OVAs, then relocating some of those CUCM 7.5K user OVAs.

◊ 

♦ 

These approaches allow reducing the software workload on an overloaded virtualization host /
physical server, so that the workload is no longer starved for hardware resources.

♦ 

• 

Hardware: additions/upgrades to "fix" an overloaded host as an alternative to powering-down VMs or
moving VMs.

E.g. adding more physical disks to increase storage capacity and/or provide IOPS

♦ 

E.g. adding more physical memory or more physical CPU cores

♦ 

E.g. adding physical NIC interfaces to address LAN congestion.

♦ 

These approaches allow "upgrading" the overloaded hardware to accommodate the
resource-starved software workload.

♦ 

• 

Cisco's provision of support is contingent upon customer maintaining a current and fully paid support contract
with Cisco.

• 

• 

• 

• 

• 

• 

• 

Contacts & Feedback | Help | Site Map
© 2015 - 2016 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of Cisco
Systems, Inc.

Updated: May 11, 2012

Document ID: 113520