There is a big push for all UC Appliances to go virtual. This push comes from all the awesome benefits/features of virtualization, Cisco emerging and exploding in the server hardware arena, and from the IT architects and directors who want to stay current or push the envelope.
So you want Cisco UC to be virtual, but where do you start and where are the instructions? From an information/instruction perspective, Cisco is moving towards Online Wiki's because of the speed in which they may publish information. The old days of 4-month literary approvals and information releases are gone. The snail's pace of releasing documentation doesn't make sense in a rapidly advancing and evolving arena such as virtualized Unified Communications.
Start here:
1) Considerations
You want to make sure that what you're about to buy is compatible. The question is how compatible do you want it to be? There is Super Compatible (down to a gnat's ass), then there's Compatible (okay it works *fingers crossed*), and then there's Incompatible (this thing just doesn't work).
Tested Reference Configurations (TRC) - Super Compatible!
- http://docwiki.cisco.com/wiki/Tested_Reference_Configurations_%28TRC%29
- TRC's are for these type of customers
- lower levels of virtualization proficiency
- require guaranteed UC app virtual machine performance when the solution elements under Cisco UC's control are configured correctly per UC support policy
- desire Cisco to handle hardware sizing, determining hardware specs and translating those specs into a hardware parts list to ensure the above guarantee
- are willing to accept as tradeoffs for the guarantee less choices for hardware and less choices for virtual machine deployment options.
- TRC's typically come packaged in a single part number - yay!!
Specs-Based VMware Hardware Support - Compatible
- http://docwiki.cisco.com/wiki/Specification-Based_Hardware_Support
- Specs-Based is intended for customers with extensive expertise in virtualization and server/storage who wish to use their own hardware standards.
- The hardware choices have not be directly tested/documented by Cisco (since they didn't choose the configurations... you did!!)
- Cisco is not responsible for the screw-ups you caused. That being said, I think it would be difficult to pin-point many issues back to the hardware configuration unless you did a pretty shoddy job of choosing and sizing.
- A good rule of thumb is to follow the TRC specs or choose hardware better than what the TRC has tested.
Sizing Network Hardware and QoS Considerations
- QoS - http://docwiki.cisco.com/wiki/QoS_Design_Considerations_for_Virtual_UC_with_UCS
- Review the NIC teaming and functions of each NIC
- Review trunking - 802.1q recommended over ISL
- LAN Traffic Sizing
- QoS Design Considerations
- Storage - http://docwiki.cisco.com/wiki/Shared_Storage_Considerations
- Review Storage TRC vs. Supported Storage for Specs-based Support
- Best Practices
2) Implementing
So your hardware has arrived, but now what?
Configuring Hardware Platforms
- Raid configuration, BIOS settings, firmware upgrades/configuration and monitoring of hardware health
Installation
- Installation on C-Series Servers
- Installation on B-Series Servers
- CUCM on Virtualized Servers
- Important Installation Notes!!
- Currently only VMware vSphere ESXi 4.1 and later is supported, but you must DISABLE LRO
- How to disable LRO - http://docwiki.cisco.com/wiki/Disable_LRO
- ESXi 4.x and below do not support 2 TB LUNs
- If you present a 2 terabyte (TB) or larger LUN to one or more ESXi hosts, you will experience issues!!
- Since TRC bundled C-series servers come with four 1TB hard drives, you have to configure RAID10 so that it reduces the 4TB size down to 1.8TB and gives storage resilience.
- http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=3371739
- RAID 10 is a combination of RAID0 and RAID1, and consists of stripes across mirrored drives. This provides for high data transfer rates and complete data redundancy, but requires twice as many drives as other RAID levels (except RAID1)
- http://www.cisco.com/en/US/docs/unified_computing/ucs/3rd-party/lsi/mrsas/userguide/LSI_MR_SAS_SW_UG.pdf
- Configuring RAID 10 (hard drive controller card needed)
3) Building UC Appliances
You've installed ESXi 4.1 and vSphere. Now after all of that, you still need to build out your UC applications!
Building the VMs
- OVA/OVF (Open Virtualization Appliance/Format) is a game changer.
- These small files can be downloaded on Cisco.com under the appliance you're looking to install. The OVA templates build out the required virtual hardware specs that are supported by Cisco.
- You don't have to build or spec out the hardware. Just deploy the OVA!!
- Once your machines are built you can proceed with the standard install procedures.
- Do not use Snapshots (especially Snapshots with memory) as they are not supported for Cisco UC applications and they can take your system down and take up hard drive space.
- Use cloning or templates!
- Make sure you are fully licensed
- The trial runs out in 60 days and then your VMs won't turn on!
- Configure the auto power-on sequence upon host start-up
- Again, no Snapshots!
- Set alarms/alerts so that you're kept in the loop on the health of your host(s)
- Setup vCenter if you have more than one host
- Upgrade VMware tools!!
- Configure backups for your UC appliances
- Make sure to review the system utilization (hard drive, memory, CPU, etc.)
.
No comments:
Post a Comment