CUCM Migration to New BE6K
Budget: ₹75,000 – ₹95,000 INR
I need an experienced Cisco UC engineer to move our entire Cisco Unified Communications Manager 11.5 cluster from the current pair of UCS servers to a fresh BE6K-M6-K9 platform. The goal is a like-for-like migration: two nodes in an active / passive arrangement, keeping every dial plan entry, device pool, SRST reference, certificate, and license exactly as they are today.
I’m looking for full, end-to-end assistance. That includes planning the cut-over, exporting and restoring the DRS backup (or using Prime Collaboration Deployment if that proves cleaner), rebuilding the cluster on the BE6K hardware, and validating that phones, trunks, voicemail integrations, and presence services all register with zero loss of service. The passive node must mirror the current HA behaviour; no new backup features are required, just the same resiliency we enjoy today.
You will need to:
• Capture a reliable pre-migration backup and sanity-check its integrity
• Provision ESXi (if needed) on the BE6K and deploy the CUCM 11.5 OVA in line with Cisco sizing guidelines
• Restore the data, confirm replication, and real-time database sync between the two nodes
• Conduct failover tests so users experience no interruption when the active node is taken offline
• Supply concise documentation of the final build and the exact rollback plan we can keep on file
Acceptance is simple: every phone, hunt group, and SIP trunk works exactly as before, call recording and voicemail integrations remain intact, and both servers show healthy replication status for 48 hours after cut-over.
If you have recent hands-on experience migrating CUCM on BE6K hardware, please outline a rough timeline and any prerequisites you’ll need from me.
I’m looking for full, end-to-end assistance. That includes planning the cut-over, exporting and restoring the DRS backup (or using Prime Collaboration Deployment if that proves cleaner), rebuilding the cluster on the BE6K hardware, and validating that phones, trunks, voicemail integrations, and presence services all register with zero loss of service. The passive node must mirror the current HA behaviour; no new backup features are required, just the same resiliency we enjoy today.
You will need to:
• Capture a reliable pre-migration backup and sanity-check its integrity
• Provision ESXi (if needed) on the BE6K and deploy the CUCM 11.5 OVA in line with Cisco sizing guidelines
• Restore the data, confirm replication, and real-time database sync between the two nodes
• Conduct failover tests so users experience no interruption when the active node is taken offline
• Supply concise documentation of the final build and the exact rollback plan we can keep on file
Acceptance is simple: every phone, hunt group, and SIP trunk works exactly as before, call recording and voicemail integrations remain intact, and both servers show healthy replication status for 48 hours after cut-over.
If you have recent hands-on experience migrating CUCM on BE6K hardware, please outline a rough timeline and any prerequisites you’ll need from me.