Cucm 11.5 Iso

Pada pembahasan sekarang kita menggunakan cisco CUCM versi 11.5(x), untuk mendapatkan file virtual machine template dan iso cucm bisa buka link berikut: Virtual Machine Template Cisco CUCM 11.5 Iso Cisco CUCM 11.5. Pertama kita login ke VMware Esxinya untuk menambahkan vm template cucm yang sudah kita download. CUCM 6.0 has a built-in trial license that is more than adequate for a home lab, but it will not support clustering. At the time of this writing, I recommend using CUCM version 6.1 for your home lab. If you have the installation discs, you can go through the laborious process of installing CUCM from scratch. Hopefully, your Cisco SE or one of.

721-0063-000 Rev. C January 2020 Spectralink Versity Smartphone Cisco Unified Communications Manager (CUCM) Spectralink Versity COP File Interoperability Guide.

The key thing is that you must use a 'machine' id of 'pc-1.3' or it will say your hardware is not supported.

Additionally you MUST use a virtio disk or you will get a ks_pre.sh error as soon as the install starts (a look at logs will show it can't find a disk). This is funny because even though the OS finds the disk and an fdisk -l shows it, it looks like the script looks for a /dev/vda device (virtio) and nothing else, so if you didn't use Virtio as your disk and you have a /dev/sda it won't work. Or follow the step below to change the search pattern of vd to sd

In Promxox you will have to edit your config file like this:

bootdisk: sata0 cores: 12 ide2: local:iso/Bootable_UCSInstall_UCOS_12.iso,media=cdrom,size=3523684K machine: pc-1.3 memory: 8096 name: ciscouc net0: virtio=DE:C3:A0:F8:50:11,bridge=vmbr0 numa: 0 ostype: l26 scsihw: virtio-scsi-pci smbios1: uuid=99bf1ee3-b527-4ea2-bf68-179bee9699b1 sockets: 1 unused0: thin:vm-124-disk-1 virtio0: thin:vm-124-disk-2,size=90G

Raw QEMU-KVM execution:

qemu-system-x86_64 -boot dc -smp 4 -machine pc-1.3 -vnc :1 -m 8096 -drive file=cucum86.img,if=virtio -cdrom Bootable_UCSInstall_UCOS_12.iso

The following assumes you are mounting your CUCM iso into 'cucmmount'

#we make the following directories (cucmmount is where we mount the iso and cucmeditiso is where we copy the files to so we can modify and recreate the .iso)

mkdir cucmmount

mount -o loop yourcucm.iso cucmmount

#we copy our iso files to cucmeditiso

cp -a cucmmount cucmeditiso

cd cucmeditiso cd Cisco/hssi/server_implementation rm -rf OpenStack VMWARE cd KVM rm -rf HAL RHEV cd ../../../..

vi Cisco/hssi/shared/bin/hssi_api.sh
#change
case '$isFound' in '0') echo '$($impl HWModel): passed detection validation' >&2 append_inDataFile_forKey_value $hssi_api_state_file 'hardware_implementation_paths' $impl hw_model='$($impl HWModel)' ((validated_count++)) ;;
#to
echo 'HSSI_API $impl returned $isFound and errors=$validation_errors ' >&2 case '$isFound' in '0') echo '$($impl HWModel): passed detection validation' >&2 append_inDataFile_forKey_value $hssi_api_state_file 'hardware_implementation_paths' $impl hw_model='$($impl HWModel)' ((validated_count++)) ;; '2') echo '$($impl HWModel): passed detection validation' >&2 append_inDataFile_forKey_value $hssi_api_state_file 'hardware_implementation_paths' $impl hw_model='$($impl HWModel)' ((validated_count++)) ;;
vi Cisco/base_scripts/ihardware.sh
#change
function hasHwSnmpMonitoring() { local method='hasHwSnmpMonitoring' _forwardToSAM $method $@ }
#to
function hasHwSnmpMonitoring() { return 1 }
mv Cisco/hssi/server_implementation/KVM/QEMU/shared/bin/api_implementation.sh.proposed Cisco/hssi/server_implementation/KVM/QEMU/shared/bin/api_implementation.sh vi Cisco/hssi/server_implementation/KVM/QEMU/shared/bin/api_implementation.sh
#find this
return $rc
}

#add this below the }
function postBootHardwareSetup() { local rc=$HSSI_TRUE (super postBootHardwareSetup $*) local src=$? # Abort if there is a critical failure if [ $src -eq 1 ]; then return $src fi rm -f /etc/udev/rules.d/70-persistent-net.rules 2> /dev/null # # remove hwaddr field from config in case mac address changed. # sed -i 's/^HWADDR.*//' /etc/sysconfig/network-scripts/ifcfg-eth* 2> /dev/null sed -i 's/^NM_CON.*/NM_CONTROLLED='no'/' /etc/sysconfig/network-scripts/ifcfg-eth* 2> /dev/null sed -i 's/^ONBOOT.*/ONBOOT='yes'/' /etc/sysconfig/network-scripts/ifcfg-eth* 2> /dev/null return $rc }

#follow this step if you want it to work with a NON virtio disk (eg. Virtualbox)

vi ./Cisco/hssi/server_implementation/KVM/QEMU/shared/bin/api_implementation.sh

################################### ### SERVER SPECIFIC OVERRIDES BELOW ################################### VDX_PATTERN='vd' KVM_SDX_PATTERN='sd' DX_INDEX=(a b c d e)

change VDX_PATTERN='vd' to VDX_PATTERN='sd'

################################### ### SERVER SPECIFIC OVERRIDES BELOW ################################### VDX_PATTERN='sd' KVM_SDX_PATTERN='sd' DX_INDEX=(a b c d e)

Now we generate our new .iso

genisoimage -o /tmp/KVMenabled-by-realtechtalk.com.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -J -R -iso-level 4 .

Errors:

ks_pre.sh error

Normally caused by not having your VDX pattern changed as above.

The Cisco Unified Communications disc was not found in any of your CDROM drives. Please insert the Cisco Unified Communications disc and press OK to retry.

Caused by lack of presence of the .discinfo text file from the root of cucmmount not being copied to your new iso root at cucmeditiso.

cp -a cucmmount/.discinfo cucmeditiso/

How To Modify the ISO to enable KVM

Tested on UCS 8.6 and 12

mkdir mountcucm mount -o loop Bootable_UCSInstall_UCOS_UNRST_8.6.2.10000-14.sgn.iso mountcucm/

Cucm 11.5 Iso Download Free

#we need to copy the contents because we cannot directly edit a mounted (read-only) iso

cp -a mountcucm cucmedit

cd cucmedit

# we are enabling the KVM/QEMU by changing the api_implementation.sh.proposed to .sh

mv Cisco/hssi/server_implementation/KVM/QEMU/shared/bin/api_implementation.sh.proposed Cisco/hssi/server_implementation/KVM/QEMU/shared/bin/api_implementation.sh

#follow this step if you want it to work with a NON virtio disk (eg. in Virtualbox)

vi ./Cisco/hssi/server_implementation/KVM/QEMU/shared/bin/api_implementation.sh ################################### ### SERVER SPECIFIC OVERRIDES BELOW ################################### VDX_PATTERN='vd' KVM_SDX_PATTERN='sd' DX_INDEX=(a b c d e)

change VDX_PATTERN='vd' to VDX_PATTERN='sd'

################################### ### SERVER SPECIFIC OVERRIDES BELOW ################################### VDX_PATTERN='sd' KVM_SDX_PATTERN='sd' DX_INDEX=(a b c d e)

vi Cisco/base_scripts/ihardware.sh

#change this function hasHwSnmpMonitoring() { local method='hasHwSnmpMonitoring' _forwardToSAM $method $@ } #to function hasHwSnmpMonitoring() { return 1 }

cd Cisco/hssi/server_implementation

#delete everything other than KVM

total 40K drwxrwxr-x 8 900711 floppy 4.0K Aug 22 2011 . drwxrwxr-x 5 900711 floppy 4.0K Aug 22 2011 .. drwxrwxr-x 5 900711 floppy 4.0K Aug 22 2011 HP drwxrwxr-x 6 900711 floppy 4.0K Aug 22 2011 IBM drwxrwxr-x 5 900711 floppy 4.0K Aug 22 2011 KVM -r--r--r-- 1 900711 floppy 92 Dec 13 2008 README.TXT drwxrwxr-x 4 900711 floppy 4.0K Aug 22 2011 shared -r--r--r-- 1 900711 floppy 1.5K Aug 22 2011 TRANS.TBL drwxrwxr-x 4 900711 floppy 4.0K Aug 22 2011 VMWARE drwxrwxr-x 4 900711 floppy 4.0K Aug 22 2011 VOLARIS

#:/var/lib/vz/template/iso/cucm8.6kvm/Cisco/hssi/server_implementation# rm -rf HP/ IBM/ VMWARE/ VOLARIS/

#you may need to do this:

#fix this file vi Cisco/hssi/server_implementation/KVM/shared/bin/KVM.data #change expected_manufacturer=QEMU|Bochs #to expected_manufacturer=QEMU|Bochs|Seabios

#use mkisofs or genisoimage

genisoimage -o /var/lib/vz/template/iso/Bootable_UCSInstall_UCOS_UNRST_8.6.2.10000-14.sgn-KVMenabled-by-realtechtalk.com.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -J -R -iso-level 4 .

Tags:

cisco, cucm, ucsinstall, kvm, proxmoxthe, quot, pc, hardware, supported, additionally, virtio, disk, ks_pre, sh, install, logs, os, fdisk, dev, vda, didn, sda, promxox, edit, config, bootdisk, sata, cores, ide, iso, bootable_ucsinstall_ucos_, cdrom, ciscouc, vmbr, numa, ostype, scsihw, scsi, pci, smbios, uuid, bf, ee, ea, sockets, unused, vm, qemu, execution, _, dc, smp, vnc, cucum, img, modify, enable, ucs, mkdir, mountcucm, mount, bootable_ucsinstall_ucos_unrst_, sgn, mountcucum, mv, hssi, server_implementation, bin, api_implementation, vi, base_scripts, ihardware, hashwsnmpmonitoring, method, _forwardtosam, mkisofs, genisoimage, var, lib, vz, template, kvmenabled, realtechtalk, isolinux, emul, info, delete, drwxrwxr, floppy, aug, hp, ibm, dec, readme, txt, trans, tbl, vmware, volaris, rm, rf, expected_manufacturer, bochs, seabios,

This checklist gives you quick overview of all the steps you need to do for CUCM upgrade 11.5.x to 12.5.x. I will list existing resources available on the Internet and add few things from my experience.
Before making any changes, please consult with Cisco TAC or do your own research /testing in lab environment.

Please dont consider this as step by step guide and be open to possibility that I may have missed few points:

I performed the upgrade few months ago so I might have forgot few things. I am human 🙂
You may not have identical environment.
You may even hit different issues which I didnt come across.

In short, I am not responsible for any disaster 🙂

Look for BRKUCC-2011 on Cisco live library, there are 2 prez/sessions contain all screenshots/details. Cisco live on demand library is very useful, informative and free. Just logon with your cco account or signup.

Keep Official upgrade guide handy for exhaustive list:

Note – On CUCM12.5 SU2, we are facing the bug CSCth35648 ( and a few others), causing ITL issues.
Run this command and if you see the error on the last line, then you are facing the bug. Contact Cisco TAC as they need to fix the permission issue using the root account. Also a few other things maybe.
In version 12.X we expect to have itl and ctl signed by ITLRecovery cert, if you don’t see it then it also needs to be fixed.
Rather than explain in detail, I let you contact Cisco TAC with bug ID and then will help you with actions, based on your scenario/specific issue.
admin: show itl
“Failed or interrupted I/O operations.
Error parsing the ITL File.”

Pre-req

Figure out your target version. Know your WHY. Check release notes for open bug / open security vulnerabilities.
Check your Platform / server hardware compatibility with target version.
https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-version-12-5/model.html#CompatibilityInformation
Check your esxi version compatibility with target version. ( check BRKUCC-2011 prez).
Check if any OVA template changes required ( RAM, CPU increase changes recommended or required).
https://www.cisco.com/web/software/283088407/145119/cucm.ova.README.pdf
https://docwiki.cisco.com/docwiki-eol.html#VMware_vSphere_ESXi_Version_Support_for_Call_Processing_and_System_Management_Applications
Check compatibility of other applications relying on CUCM/CUC/UCCX with target version ( SBC, Voice GW, 3rd party apps..).
Check the list of Deprecated Phone models listed in document, if you have any, take care of that in advance ( upgrade, replacement ..).
Migrate your ELM/PLM licensing to Smart licensing. Check Cisco live BRKUCC-2725 for more details.
If you decide, Deploy CSSM in advance.

For some servers/devices only Smart licensing is the option after specific version ( e.g. CUCM 12.5.x) , for some its still optional ( UCCX 12.5.x).
In Plain English, With Smart licensing, Cisco sync your license status/inventory to cloud rather than PAK based/ tied to your device offline mode ( so no pain when you change general setting and license mac changes). You need to decide whether you want to sync your Infra devices to Cisco licensing portal directly ( device having internet access), via http proxy or you can deploy CSSM on prem ( lightweight VM) which can sync license from Cisco and with your infra ( Man in the middle 🙂 ).

Smart licensing goes beyond UC servers You can deploy 1 CSSM and use for entire Org. You will need to organize and clarify the Smart Account Structure in advance. Check Cisco live BRKUCC-2725 for more details.

Example – Top – Smart account = ABC.com
Sub level:
Virtual account = AP Collab
Virtual account = EU Collab

CSSM is simply a router/proxy which talks to internal devices with identifier and sync available licenses for your Smart accounts.

If you decide to use CSSM with Smart licensing, I suggest create a Smart account with Cisco and deploy/configure CCSM in advance then focus on license migration.

BRKUCC-2725 has all details on how to do license migration. If you get the error while doing the migration, open a case with licensing ( few times I got an error and licensing team helped doing from back end), they will deposit the licenses to your smart account. Probably you will need to provide, Smart account name, Smart account domain name, Virtual account name.

Cucm 11.5 Eos

Plan your upgrade

Plan your change window, open a change etc etc.
Keep note that with RU upgrade, Server is down while upgrade is taking place on inactive partition. RU = refresh upgrade = Underlying Linux version is changing. Plan your downtime window accordingly.
Decide your upgrade method – Direct or PCD. PCD = Prime Collaboration Deployment, VM you can deploy to orchestrate the migration/upgrades for you.
Download the Software images and keep on sftp server. Notice the difference in between Restricted VS Unrestricted version, use the correct image.
https://software.cisco.com/download/home/286322286/type/286319236/release/12.5(1)SU3
Keep a OVA file/ bootable image of your existing version on sftp just in case you will need to rebuild the server. If you have Enterprise Agreement with Cisco, you can download by yourself or else, open a Cisco TAC and ask for images.
Bootable images arent available/same under download page.
From 12.x CUCM and Unity connection ISO are separate.
Either verify that you have rights to deploy new VM or keep your team ready who can create a new VM in change window, if you have to rebuild a server ( worst case scenario).
If your server has a uptime of more than 365 days, Its nice to plan and give it a reboot in advance to your upgrade.
Verify you have rights to remove existing/old VM snapshots before upgrade.
Verify the free space. You will need ~43 GB space. Some ways to clean space are:
Run a cop file which cleanup the space( may need to do in downtime). Ask Cisco TAC before you do it, it might delete your inactive partition sw.
Reduce the log size.
https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200581-Procedure-to-Adjust-WaterMark-in-RTMT-of.html
Delete unused load files from CUCM O.S admin –> load management.
Open a Cisco TAC case for support in advance and inform them to requeue the case to engineer who is available in your change window. Put basic details about what you are doing in that case, it will save your time in change window.
Note that you may need to call TAC frontline and may or may not need to raise a Sev in change window as Cisco TAC could be busy with multiple cases.
Read the upgrade guide carefully.
Review the Recommended Sequence in advance from upgrade doc. See some notes here:
Publisher node MUST be Upgraded first.
Switchover options depends on the collaboration product.
CUCM Publisher can be switched over before Subscriber(s) Upgrade Startup.
DRU Only –> Switchover IM&P Publisher after CUCM Cluster Database Replication Completes.
CUC Publisher must NOT be switched over before Subscriber Upgrade Completes.
Try the upgrade in lab/ Pre-pod to avoid any surprises.
Prepare your test plan in advance. What you are gonna test and how are you gonna test it.

Bootable Cucm 11.5 Iso

1 day before or in same change window

Cucm 11.5 Bootable Iso Download

Verify/take your fresh backup. Back Up Custom Ringtones and Background Images.
Ensure SFTP is up. Please use SFTP in same location to CUCM to minimize the delay( upgrade iso is ~4G).
Keep your O.S /Cluster password and SFTP password handy.

In change window ( Pre-upgrade tasks)

Run Pre-upgrade check cop file. It checks many pre-req but common issue you may see is NTP/Free space/Expire cert/ Simple password, fix issues before upgrade.
If you are using Win NTP or Stratum 4 or above, you may see error. Fix your cert. Change of password. Check upgrade guide for more.
Verify your backup. Take details/screenshots of registered device count/ VG/ SIP trunks.
Make VM/OVA related changes RAM/CPU if needed.
Change VM compatibility. CUCM 12.5 needs ESXi 6.5 ( 13). Note that once you change, you might not be able to roll this back.
Change Guest OS type. See the doc, you will nee to change it to CentOS 7 (64 bit). Its under VM general setting, if its greyed out maybe because you need to shutdown the server first. Should be done before CUCM upgrade.
Change adapter type to VMXNet3 ( if its not already).
Update to the latest Vmware tools.
Remove old VM snapshots.

Upgrade

Cucm 11.5 Su7

You can disable TFTP services and do few other tweaks mentioned in document to expedite/smooth the upgrade.
Do the upgrade from O.S admin. Follow the seq mentioned in doc ( Upgrade Pub –> Sub1 –> Sub2 …, Switch version Pub –> Sub1 –> Sub2 ..). Be aware of some known issues, with CUC, even if you select do not reboot after upgrade, it might 🙂
For CUC, you may need to run a pre-req cop file as ISO file is changing. Ask TAC.
When you do uccx es release, verify the procedure from the doc, it maybe recommended to do from cli ( as there maybe known issue with tomcat).
Note – In RU, DB replication may take some time, be patient or ask TAC.

Cucm 11.5 Su3

Post upgrade

Run the post upgrade COP.
Reset any parameters you changed to optimize the upgrade ( TFTP, enterprise parameters). Check upgrade doc for more details.
Upgrade your RTMT.
Check Device count/ Trunk/ Vg status.
Check all the services. Check all the integration ( CCX, CUC …)
Optional : Switch from Native to Open Vmware Tools via OS Admin CLI –> utils vmtools switch open
Change Transport Settings for CUCM for Smart Licensing ( you can find the URL from CSSM or from doc or google it).
Common issue you might face is DNS resolution for CSSM , so use IP address and port 80. If your DNS and Cert is all good then it could be different issue, like reachability ( IP/Port).
Create or copy existing registration token from CSSM or Smart Software Manager satellite server to CUCM.
Do your usual testing.

If you find have any feedback, suggestions, please feel free to put the comment or DM me on LinkedIn.