Currently doing an off line upgrade of a customer CUCM 8.6 system. After building the VMs using the 10.5 OVA template, we found that the software would NOT load as it would fail during install. Root cause was tracked down to an issue with the VM NIC. 10.5 builds this nic as a VMXNET3. It was necessary to change this to E1000 to get the software to load.
Is it a problem leaving this as an E1000 vNIC going into production? Or do we really need to back it up and rebuild it, or swap out the vNIC to have it be officially supported?
Gack!!!! Once again burned by obscure information being located in an unexpected place.
The procedure to modify the vNIC is in there, but it didn't really address the install on the v10 OVA with older software. I found I could change it to an E1000 type, install the v8 software, then use the procedure in the readme to modify it to the VMXNET 3 adapter type. That, and the need for the COP to recognize the media as valid really should have been made a lot more obvious.
Seems like it would be a lot simpler to just include the COP files you might need on the ISO image, but I guess that would create something else to manage they really don't want to.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...