Starting Cisco CallManager...

Tokyo's first early riser would be picking up a phone in sixty seconds.

Two weeks. For a hotel chain with 24/7 operations across eight time zones. That wasn't an option.

The problem? Their legacy Cisco Unified Communications Manager (CUCM) cluster—three physical MCS servers, affectionately nicknamed "Big Yellow," "Old Blue," and "The Grouch"—had finally given up. Big Yellow had suffered a catastrophic RAID failure at 4:00 PM. The vendor quoted two weeks for a replacement part.

CUCM is picky about MAC addresses. Change a virtual NIC's MAC after installation, and the entire node's certificate chain explodes. She'd learned that the hard way during testing. Tonight, she triple-checked the port group settings: VLAN 10 for PUB, VLAN 11 for SUB1, VLAN 12 for SUB2. The Cisco switchports were pre-configured with spanning-tree portfast and switchport voice vlan . The VMs would never know they weren't physical.

Mariana sipped her cold coffee, staring at the blinking yellow light on her laptop. It was 11:47 PM. Across the globe, the Tokyo office was waking up, and in fifteen minutes, their first wave of calls would hit the system.

By clicking accept, you understand that we use cookies to improve your experience on our website. For more details, please see our Cookie Policy.