Wednesday, January 9, 2019

Cisco Call Manager (CUCM) and Unity Connection (CUC) - Create Bootable ISO

The ISO Disks we get from Cisco are not bootable. In this example we will use the  UCSInstall_UCOS_11.5.1.13901-3.sgn.iso.

PowerISO and UltraISO are both great tools that you can create bootable ISOs, but they come with a cost.  

In our case we will only use the 7zip for extracting the ISO and cdrtfe to burn our ISO Image. 

We will also need the isolinux folder from another Cisco Bootable ISO

Extract the ISO files to a new folder using 7zip and navigate to Cisco\install\conf





Navigate to Cisco\install\conf and open the callmanager_product.conf file using Notepad++



The CUCM Installation validates the Hardware available on our System and specific settings are required to pass the validation. For example trying to install CUCM/CUC in Oracle VirtualBox will fail by default.   


On a real life scenario we must use OVA Template to create our VM. The OVA file will ensure the correct settings (RAM, CPU, Disk etc.). 

If we don't follow those strict settings, then it is possible that Cisco won't be able to provide support to our system when we open a TAC Case, until we adjust those settings. 


In our lab environment, we can under-provision our system, in order to save some of our lab resources. Typically, you will get this error when you try to install the OS on a non-supported system.

There are different rules for different application, for example in the file there is also the CUC. Below you can see the CUCM models supported.  



VAL means that it can pass validation, while NOT fail. We will change both NOT that are on the MODEL column to VAL and the MAX MEMORY to * (which means any)

In the first example, we can see that if the maximum RAM is less than 2047 then the installation will fail. 

TYPE   MODEL   CLOCK   MIN/MAX MEM   MIN/MAX DISK1   MIN/MAX DISK2   COUNT 
NOT,   VMware,     *,      *, 2047,      *,     *,      *,    *,      *
VAL,        *,     *,      *,    *,      *,     *,      *,    *,      *

For Cisco Unity Connection (CUC) we have more restrictions 

VAL,   VMware,     *,   8191,    *,    290,   510,    290,  510,      7
VAL,   VMware,     *,   6143,    *,    140,   510,    140,  510,      4
VAL,   VMware,     *,   6143,    *,    190,   510,      *,    0,      2
VAL,   VMware,     *,   4095,    *,    150,   510,      *,    0,      2
VAL,   VMware,     *,   4095,    *,    150,   510,      *,    0,      1
VAL,   VMware,     *,   2559,    *,     90,   510,      *,    0,      1
NOT,   VMware,     *,      *,    *,      *,     *,      *,    *,      *

 Now replace the isolinux to the Main folder 



We will open the cdrtfe and select options. 

We will specify the same of the new bootable ISO Image Bootable_UCSInstall_UCOS_11.5.1.13901-3.sgn.iso.
and also specify do not burn to Disk and press OK. 



Then go to Filesystem and enable "create boot disk". Select No disc emulation. The boot image is the isolinux.bin on the \isolinux disk we copied earlier to the main extracted ISO. 



We will copy or drag and drop all the files of the Extracted ISO to under the Blank Disk and then press Start to burn the ISO. 


We are good to go




No comments:

Post a Comment

Cisco Call Manager - Create Unattended File

CUC and CUCM installation wizard has a lot of steps that require user's input. Luckily we can specify an unattende...