CUCM 9.11 to 9.12 upgrade "Partitions Aligned"

I have a customer who wants to verify if their CUCM 9.1.1 disks Partitions are Aligned prior to proceeding with the 9.1.2 upgrade. Is there a TAC approved procedure that can be performed prior to the upgrade to validate the CUCM Partitions are Aligned?

Cisco TAC provided the following procedure:
•1)      Shutdown the vm
•2)      Logged in using root username/password for ESXi
•3)      cd /vmfs/volume
•4)      ls (to list all my datastores)       Now find the datastore that you used to install the Vms
•5)      cd    Example in my lab : cd datastore2
•6)      ls  (list all the VMs in the datastore)
•7)      cd “VM name”      USE quotes if your VM name contains any spaces
•8)      ls   (you should see a file with .vmdk extension. IT Will word flat before it)
•9)      fdisk –lu  < filename-flat.vmdk>    
The output will be something like this.  The key is too look for partition to start at “128”  This one does.   If its something like 63. Then its not aligned.
                  Device Boot      Start         End      Blocks  Id System
CUCM 10.0 Sub-flat.vmdkp1   *       128  29753343  14876608   83  Linux
Partition 1 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(1852, 15, 19)
CUCM 10.0 Sub-flat.vmdkp2      29753344  59506687  14876672   83  Linux
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(1023, 254, 63) logical=(1852, 15, 20)
Partition 2 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(3704, 30, 38)
CUCM 10.0 Sub-flat.vmdkp3      59506688  60030975    262144   83  Linux
Partition 3 has different physical/logical beginnings (non-Linux?):
     phys=(1023, 254, 63) logical=(3704, 30, 39)
Partition 3 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(3736, 192, 40)
CUCM 10.0 Sub-flat.vmdkp4      60030976 167766794  53867909+   5  Extended
Partition 4 has different physical/logical beginnings (non-Linux?):
     phys=(1023, 254, 63) logical=(3736, 192, 41)
Partition 4 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(10442, 254, 63)
CUCM 10.0 Sub-flat.vmdkp5      60031104  64159680   2064288+  82  Linux swap
CUCM 10.0 Sub-flat.vmdkp6      64159744 167766794  51803525+  83  Linux
Unknown value(s) for: cylinders (settable in the extra functions menu)

Similar Messages

  • How to keep aggregated link interface across live upgrade partitions?

    I'm running Solaris 10 11/06 s10x_u3wos_10 X86 on a 2100. I have nge1 and nge0 in an aggregated link interface aggr1. I have the /etc/hostname.aggr1 file, and aggr1 comes up fine on reboots. I also have a Live Upgrade partition, and it doesn't come up when I activate my Live Upgrade partition. I get a message on the console saying it failed to plumb aggr1, so I can see it was at least trying. I do see the /etc/hostname.aggr1 on the Live Upgrade partition and it has the correct IP & netmask, so that file synchronized fine. I don't have any errors or warnings in /etc/lu/sync.log. My other link interface bge0 (not aggregated) comes up fine on the Live Upgrade partition, it is just the aggregated one that doesn't come up. Also, when I removed the aggregated interface, nge1 and nge0 came up fine on the Live Upgrade partition too. It seems to be just the aggregated interface that has problems. Is there something else I need to do on the original partition to make sure aggr1 will come up on the Live Upgrade partition?
    This seemed similar to bug id 6369648, but I have the patch 120991-02 installed, and I don't lose aggr1 on reboots. I only lose it after activating the other Live Upgrade partition.

    I just found a file /etc/aggregation.conf, which was not added to the Live Upgrade synclist (/etc/lu/synclist). I'm hoping by adding that file, it will get synchronized and the plumb will work.

  • Imaging and partition alignment

    We are using ZCM 10.3.1 and the August 2010 Imaging CD to create and
    restore Windows 7 images to wiped conventional and solid state drives.
    We have been running the Windows 7 Experience Index tool to check disk
    performance. We are in the process of moving towards use of solid state
    drives and want to be sure we are getting the best possible performance.
    We have identical model laptops with the same SSD where some will score
    a 7.1 on the disk performance and others will score 5.9.
    In the process of doing more research on solid state drives, we came
    across some info that mentioned the need to have the partition aligned
    for best performance.
    So far we have found that if a laptop had Windows 7 installed directly
    to the solid state drive from the Windows 7 DVD, the partition is
    aligned (determined by taking the partition starting offset and dividing
    it by 4096 - result should be an integer if aligned). These laptops
    score at least a 6.9 on the Windows 7 disk performance test.
    On a laptop that had an image laid down using Zenworks the partition
    always ends up misaligned. These laptops typically score a 5.9 on the
    Windows 7 disk performance test.
    Has anyone else noticed a partition alignment problem when using
    Zenworks imaging ?

    Or maybe run a chkdsk on a freshly imaged machine to see if there are
    errors ?
    On 10/8/2010 2:25 PM, Chris Granitz wrote:
    > Does anyone have anything to offer on this ?
    >
    > Would someone else mind checking the partition alignment on one of their
    > imaged machines ?
    >
    > On 10/5/2010 1:33 PM, Chris Granitz wrote:
    >> Some additional info...
    >>
    >> We have also noticed that if we run Windows Chkdsk on a laptop that was
    >> restored using a Zenworks image (conventional hard drive or solid state
    >> drive), that there a lot of errors that chkdsk corrects. That is
    >> particularly bothersome. Windows seems to otherwise run fine, but
    >> obviously Windows is not totally happy with some aspect of the image
    >> that Zenworks is laying down.
    >>
    >>
    >> On 10/5/2010 1:12 PM, Chris Granitz wrote:
    >>> We are using ZCM 10.3.1 and the August 2010 Imaging CD to create and
    >>> restore Windows 7 images to wiped conventional and solid state drives.
    >>> We have been running the Windows 7 Experience Index tool to check disk
    >>> performance. We are in the process of moving towards use of solid state
    >>> drives and want to be sure we are getting the best possible performance.
    >>> We have identical model laptops with the same SSD where some will score
    >>> a 7.1 on the disk performance and others will score 5.9.
    >>>
    >>> In the process of doing more research on solid state drives, we came
    >>> across some info that mentioned the need to have the partition aligned
    >>> for best performance.
    >>>
    >>> So far we have found that if a laptop had Windows 7 installed directly
    >>> to the solid state drive from the Windows 7 DVD, the partition is
    >>> aligned (determined by taking the partition starting offset and dividing
    >>> it by 4096 - result should be an integer if aligned). These laptops
    >>> score at least a 6.9 on the Windows 7 disk performance test.
    >>>
    >>> On a laptop that had an image laid down using Zenworks the partition
    >>> always ends up misaligned. These laptops typically score a 5.9 on the
    >>> Windows 7 disk performance test.
    >>>
    >>> Has anyone else noticed a partition alignment problem when using
    >>> Zenworks imaging ?
    >>
    >

  • Partitions alignment using cfdisk

    I have a new hard disk which have advance formatting , and I am not sure if I will cfdisk if the partitions will be aligned correctly.
    is there paramers I need to give to enure the partitions are aligned or I can just use it and the partitions will be aligned?
    Last edited by XDarkAngelX (2014-01-08 16:47:04)

    Alber wrote:
    I'm supposing a SSD.
    From wiki:
    Many of the common partition tools handle partition alignment automatically (assuming users are using an up-to-date version):
    https://wiki.archlinux.org/index.php/So … _Alignment
    Edit:
    About advance formatting
    http://en.wikipedia.org/wiki/Advanced_Format
    https://wiki.archlinux.org/index.php/Advanced_Format
    For advanced format partitioning
    https://wiki.archlinux.org/index.php/Ad … Partitions
    ok but do you know if cfdisk supports Aligning Partitions? as it is not menioned in the wiki and I perfer to use it over fdisk

  • CUCM 8.6.2 to 10 Upgrade

    Hi everyone,
    Didn't have the following situation so far, so need advice:
    I have an upgrade on the way, from CUCM 8.6.2 to CUCM 10, and that's fine,
    But client needs to expand the cluster, by adding additional subscriber nodes.
    Do I go with upgrade first, and then add more subscribers, afterwards?
    or
    Do I add subscribers first, and then do an upgrade?
    Regards
    Vladimir

    Hi Aman,
    Thank you for your prompt response!
    Can you give me the reason, why would you go with adding first, migrate later?
    Since it doubles the effort. Is there any particular reason for the choice?
    I personally would go with migration first, and add subs afterwards...
    Are there any cons with my option?
    Thank you again!
    V

  • Windows 8 Upgrade, Partition Unallocated

    I have a Seagate 3TB Barracuda XT drive on my Asus P6X58D Premium based system using the Marvell 9123 Sata 3 storage controller.  Running Win 7 Pro x64 I had it divided into a a 2TB partition (Basic) as my C volume and a 1TB partition (Basic) as a spare
    volume.  Afterer upgrading to Win 8 Pro x64, the 1TB partition is grayed out and marked as "Unallocated".  Disk Management can do nothing more than display "Properties" on this volume, and neither Paragon nor Easus (spelling?) can manipulate this
    1TB volume at all. I've been searching the web for more info or others experiencing this issue and have not been successful.  Anyone else encountered this?  I'm stumped.
                     John

    HI,  I realize this question was answered in 2012, But, I still need an answer now. I do not have an Asus motherboard and when I accessed the AsusDisk Unlocker per the link the warning states to use this ONLY if you have an Asus motherboard.  I
    have a Dell Optiplex 7010 computer.  I contacted Seagate and the fix they suggested did not work so they said to contact Microsoft... so here I am again looking for the answer.  What do you suggest to fix this problem now in 2014? Any new fixes with
    Windows 8.1?  Seagates Disc Wizard showed the partitions correctly in Windows 7 Pro and when I upgraded to Windows 8 then to 8.1 the partition with the "1 TB" I named as my "E" drive became the "unallocated" partition.  Thank
    you for the help.

  • Upgrade & Partition TC internal hard disk - info howto

    The Time Capsule comes with the disk formatted to a single data partition.. there is no way to change this via tools in the computer or airport utility. Whatever tool is internal on the TC is not accessible.. if you use erase it will reformat the drive and recreate the original partition. 2 of which are hidden.
    There are three partitions in the actual drive.. only one of which you can see.
    APconfig
    APswap
    data (or whatever name is used.. which can be changed via the airport utility).
    You can create a disk image on the internal drive as a method of partitioning it.. not really the same thing.. but for most it works.
    See http://pondini.org/TM/TCQ3.html for the method.
    If you want to alter a TC actual hard disk, you need to remove it from the TC.. this will of course void the warranty. So before jumping, think about it.
    I was asked to install a 3TB drive on a Gen 2 A1302 TC which I undertook with some trepidation as most of my reading of forums suggested hard disk above 2TB were impossible. It may not have worked with older firmware but on 7.6.1 it works just fine.. with this proviso.. the spin down may not work. The TC worked fine with a new 3TB WD green drive. I discovered the one used in the Gen 4 latest model is older WD drive.
    WD30EZRS These are Sata1
    The ones you buy now are WD30EZRX which are sata2 drives.. Swapping them around caused no problems on the Gen 4.. did not try on the Gen2.
    You don't want to know how I found this out.
    Since you are upgrading a drive and have it out.. how nice to actually partition it. This was tricky and I actually found very little info about it.. if any of you know where there is a howto I am glad to reference it.
    I have previously installed new disks with no trouble.. but without the hidden partitions created I think it uses RAM for those files.. and it will toss up disk errors.
    So you need to actually create all the partitions. This isn't hard. Although again ran into trouble with the USB to sata box I was using not being able to read 3TB drives.. so I was forced to directly connect to sata.. this may be difficult for most of you... Make sure you have the equipment to do the work before ordering 3TB drive.. My USB box can do 2TB.. but it recognises the 3TB as 800MB or GB.
    Using disk utility change to 4 partitions.. (or whatever number you want.. 5 or 6 I guess are ok) There are two paritions for internal use.. I created APconfig and APswap .. set the size to .01GB or whatever.. you must type this in directly.. and it will change it to the min possible size partition.. 1.07GB on the 3TB.
    This is a waste as the actual files used are tiny.. but.. you have lots of space.. you need to lose some to gain a lot more.. so be it.
    Name your data partitions something suitable.. TCpart1 TCpart2 TCpart3 or data1 data2 data3
    Make sure you format them using HFS+ and GUID type.
    The TC still kicks up an error about the disk.. this is probably a nasty side effect of Disk Utility creating an EFI partition which is invisible..
    So I am going to need to try again via the Command Line disk utility.. So I can create the partitions without using an EFI.
    So expect further installment.. Anyone with Command Line instructions I would be glad of the help.

    solved by posting elsewhere....
    http://discussions.apple.com/thread.jspa?messageID=7316301#7316301

  • MSDN Win7 upgrade + partitioning + able to use System Recovery. how?

    I have installed throught a clean install on my T400 (recently bought, no important files yet), and I have resized my C drive so I have a new D partition. But after partitioning the system recovery through blue button (ThinkVantage) will not work. I did not purchase a Windows 7 license off lenovo because my University gave us MSDN subscriptions for Win 7 Pro.
    So here I am asking: What is, if there is one, the perfect solution, to upgrade from Vista 32bit (Recovered from backup disks) to Windows 7 x64, and split C: into two partitions, while at the same time, allow F11 at start up to work and recovery C: drive without erasing my other partitions.
    Thank you, I know this is probably one of the most often answered questions on this forum... If there is already a solution to this, sorry about that because I couldn't find a post talking about this ^^;;;
    Solved!
    Go to Solution.

    Hi:
    looks like you wan to run your PC on Windows 7, but also want to have that recovery feature in place.
    You can do one of two options:
    Option A:
    -Perform a clean install of Windows 7
    -Download System Update 4.0 from lenovo.com
    -Select ALL updates indicated from the scan.
    -after those are installed, run Windows Update, install all updates, then install ALL of your additional software.
    -once your PC is completely set up, Run Rescue and Recovery (in the thinkvantage folder); if it is not in your pc, you can download this from Lenovo.com.  Create a harddrive Backup of your PC.
    Youre Done.  You now have a new image installed in your PC that works using the "Blue button" (Rescue and recovery is the program that runs when you press this button).
    Option B:
    If you can get your hands on the New Recovery Discs for Windows 7, you can instal the entire Factory image of New Lenovo Notebooks built after 10/22.  Not only will you have the setup you want, the Enhanced Experience ("EE" rating) given to those new notebooks will apply to your PC as well.  Good Luck, They will be hard to find (unless you can find a person with the new laptop - they can burn the recovery disks for you right from their Notebook.

  • Dualboot archlinux/ubuntu on SSD, partition alignement is so fun

    Hi people.
    I just bought one of those shiny thing called SSD (a Crucial RealSSD C300 64GB) and planning to install Archlinux on it (along with Ubuntu as a test system for running my apps under it and as a backup system, you know for when I'll try the last feature in kernel26-git and will break every thing).
    I setup the disk according Tso's numbers : H=225 S=56
    I tried to align my partition by hand using a 512kiB and create the ext4 filesystems using :
    mkfs.ext4 -b 4096 -E stride=128 /dev/sdaX
    Frankly I think that I misunderstood the head/cylinder thing :
    - I manage to install Ubuntu (I use it currently)
    - but I can't assign partition to mount point in Archlinux installer: it complain about a partition that finishes half of a cylinder.
    So my question are:
    Should I realign my partition using H=32 S=32 or could I ignore the installer error and mounting the partition myself (and will I loose performances if I do so) ?
    Bonus :
    The Archlinux wiki page on SSD (http://wiki.archlinux.org/index.php/SSD … _Alignment) does advise to a blocksize of 4kiB and a stride of 128kiB when creating the filesystem. I think it would be nice to advertise on that and I'm willing to add that myself but I not so sure about SSD and partitions so comments are welcome.

    Answering to myself and from the man page of ext4.
    I was wrong in my previous post, maybe someone will need those informations later so I put them here :
    It look like you need to customize block size and stride for raid only, so in my case I don't need it (don't remember where I read about that but I may have misunderstood something again). Furthermore it look like for a filesystem larger than 512MiB mke2fs will pickup a block size of 4kiB (as stated in the default section /etc/mk2fs.conf) of  but I can't find much information on the -T usage_type parameter.
    Can't someone correct me if I'm wrong ?

  • Problem in upgrading from CUCM 8.5.1 to CUCM 8.6.2

    Unable to upgarde cucm 8.5 to 8.6 ,
    installed referesh upgrade cop file . tried on SFTP and using local DVD same below error displayed . Any one have any solution please share .
    Installation Status
    File
    UCSInstall_UCOS_8.6.2.21900-5.sgn.iso
    Start Time
    Mon Dec 10 14:31:47 GST 2013
    Status
    Error encountered: An unknown error occurred while accessing the upgrade file.
    12/10/2013 13:44:37 file_list.sh|Starting file_list.sh|<LVL::Info>
    12/10/2013 13:44:37 file_list.sh|Parse argument method=remote_sftp|<LVL::Debug>
    12/10/2013 13:44:37 file_list.sh|Parse argument source_dir=/|<LVL::Debug>
    12/10/2013 13:44:37 file_list.sh|Parse argument dest_file=/var/log/install/downloaded_versions|<LVL::Debug>
    12/10/2013 13:44:37 file_list.sh|Parse argument remote_host=10.2.102.68|<LVL::Debug>
    12/10/2013 13:44:37 file_list.sh|Parse argument user_name=cisco|<LVL::Debug>
    12/10/2013 13:44:37 file_list.sh|Process remote SFTP request|<LVL::Info>
    12/10/2013 13:44:37 file_list.sh|Calling SFTP command with metering off|<LVL::Debug>
    12/10/2013 13:44:38 file_list.sh|SFTP command complete (0)|<LVL::Debug>
    12/10/2013 13:44:38 file_list.sh|List file (pre-filtered):|<LVL::Debug>
    12/10/2013 13:44:38 file_list.sh|(CAPTURE) UCSInstall_UCOS_8.6.2.21900-5.sgn.iso|<LVL::Debug>
    12/10/2013 13:44:38 file_list.sh|(CAPTURE) ciscocm.refresh_upgrade_v1.1.cop.sgn|<LVL::Debug>
    12/10/2013 13:44:38 file_list.sh|/opt/cisco/install/bin/filter file=/var/log/install/downloaded_versions|<LVL::Debug>
    12/10/2013 13:44:38 filter|Parse argument file=/var/log/install/downloaded_versions|<LVL::Debug>
    12/10/2013 13:44:38 filter|No patch type specified. Optional.|<LVL::Debug>
    12/10/2013 13:44:38 filter|No upgrade mode specifed. Optional.|<LVL::Debug>
    12/10/2013 13:44:43 filter|Processing filter candidate names|<LVL::Debug>
    12/10/2013 13:44:43 filter|Process "UCSInstall_UCOS_8.6.2.21900-5.sgn.iso"|<LVL::Debug>
    12/10/2013 13:44:43 filter|    Match against patch pattern  (UCSInstall_UCOS_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.iso)|<LVL::Debug>
    12/10/2013 13:44:43 filter|    Match against patch pattern  (UCSInstall_UCOS_UNRST_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.iso)|<LVL::Debug>
    12/10/2013 13:44:43 filter|    Match against patch pattern  (UCSInstall_UCOS_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.sgn.iso)|<LVL::Debug>
    12/10/2013 13:44:43 filter|INorOUT=IN UCSInstall_UCOS_8.6.2.21900-5.sgn.iso: Filter passed.|<LVL::Debug>
    12/10/2013 13:44:43 filter|Process "ciscocm.refresh_upgrade_v1.1.cop.sgn"|<LVL::Debug>
    12/10/2013 13:44:43 filter|    Match against patch pattern  (UCSInstall_UCOS_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.iso)|<LVL::Debug>
    12/10/2013 13:44:43 filter|    Match against patch pattern  (UCSInstall_UCOS_UNRST_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.iso)|<LVL::Debug>
    12/10/2013 13:44:43 filter|    Match against patch pattern Signed Standard upgrade patch file (UCSInstall_UCOS_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.sgn.iso)|<LVL::Debug>
    12/10/2013 13:44:43 filter|    Match against patch pattern  (UCSInstall_UCOS_UNRST_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.sgn.iso)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against es pattern  (UCSInstall_UCOS_ES[0-9]*_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.iso)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against es pattern  (UCSInstall_UCOS_UNRST_ES[0-9]*_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.iso)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against es pattern  (UCSInstall_UCOS_ES[0-9]*_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.sgn.iso)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against es pattern  (UCSInstall_UCOS_UNRST_ES[0-9]*_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.sgn.iso)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against su pattern  (UCSInstall_UCOS_SU[0-9]*_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.iso)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against su pattern  (UCSInstall_UCOS_UNRST_SU[0-9]*_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.iso)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against su pattern  (UCSInstall_UCOS_SU[0-9]*_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.sgn.iso)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against su pattern  (UCSInstall_UCOS_UNRST_SU[0-9]*_[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.sgn.iso)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (dp-ffr.[1-9]-[0-9]-[0-9]+.*.cop)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (dp-ffr.[1-9]-[0-9]-[0-9]+.*.cop.sgn)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (cm-locale-.*_.*-[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (cm-locale-.*_.*-[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop.sgn)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (po-locale-.*_.*-[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (po-locale-.*_.*-[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop.sgn)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (cmterm-devicepack[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (cmterm-devicepack[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop.sgn)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (cmterm-.*\.cop)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (cmterm-.*\.cop\.sgn)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (uc-locale-.*_.*-[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (uc-locale-.*_.*-[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop.sgn)|<LVL::Debug>
    12/10/2013 13:44:44 filter|    Match against cop pattern  (uc-friendly-[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop)|<LVL::Debug>
    12/10/2013 13:44:45 filter|    Match against cop pattern  (uc-friendly-[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[0-9]+.cop.sgn)|<LVL::Debug>
    12/10/2013 13:44:45 filter|    Match against cop pattern  (ciscocm..*.cop)|<LVL::Debug>
    12/10/2013 13:44:45 filter|    Match against cop pattern  (ciscocm..*.cop.sgn)|<LVL::Debug>
    12/10/2013 13:44:45 filter|INorOUT=IN ciscocm.refresh_upgrade_v1.1.cop.sgn: Filter passed.|<LVL::Debug>
    12/10/2013 13:44:45 file_list.sh|List file (post-filtered):|<LVL::Debug>
    12/10/2013 13:44:45 file_list.sh|(CAPTURE) <?xml version="1.0" encoding="UTF-8"?>|<LVL::Debug>
    12/10/2013 13:44:45 file_list.sh|(CAPTURE) <InstallList>|<LVL::Debug>
    12/10/2013 13:44:45 file_list.sh|(CAPTURE)     <InstallItem type="patch" secure-file="UCSInstall_UCOS_8.6.2.21900-5.sgn.iso" version="8.6.2.21900-5" file="UCSInstall_UCOS_8.6.2.21900-5.sgn.iso" reboot="no" signed="yes"/>|<LVL::Debug>
    12/10/2013 13:44:45 file_list.sh|(CAPTURE)     <InstallItem type="cop" secure-file="ciscocm.refresh_upgrade_v1.1.cop.sgn" version="0.0.0.0-0" file="ciscocm.refresh_upgrade_v1.1.cop" reboot="no" signed="yes"/>|<LVL::Debug>
    12/10/2013 13:44:45 file_list.sh|(CAPTURE) </InstallList>|<LVL::Debug>
    12/10/2013 13:44:45 file_list.sh|success|<LVL::Info>
    12/10/2013 13:44:45 file_list.sh|file_list.sh complete (rc=0)|<LVL::Info>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Starting upgrade_validate_file.sh|<LVL::Info>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Parse argument method=remote_sftp|<LVL::Debug>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Parse argument source_dir=/|<LVL::Debug>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Parse argument file_name=UCSInstall_UCOS_8.6.2.21900-5.sgn.iso|<LVL::Debug>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Parse argument remote_host=10.2.102.68|<LVL::Debug>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Parse argument user_name=cisco|<LVL::Debug>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Parse argument file_type=patch|<LVL::Debug>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Parse argument file_signed=yes|<LVL::Debug>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Process remote SFTP request|<LVL::Info>
    12/10/2013 13:44:53 upgrade_validate_file.sh|Get //UCSInstall_UCOS_8.6.2.21900-5.sgn.iso size via sftp|<LVL::Debug>
    12/10/2013 13:44:54 upgrade_validate_file.sh|Size of file obtained from sftp is 4793341952|<LVL::Debug>
    12/10/2013 13:44:54 upgrade_validate_file.sh|Total space needed is 9586683904|<LVL::Debug>
    12/10/2013 13:44:54 upgrade_validate_file.sh|Check free space|<LVL::Info>
    12/10/2013 13:44:54 upgrade_validate_file.sh|There is enough space on device to proceed.|<LVL::Info>
    12/10/2013 13:44:54 upgrade_validate_file.sh|(CAPTURE)   Free space : 25916985344|<LVL::Debug>
    12/10/2013 13:44:54 upgrade_validate_file.sh|(CAPTURE) Space needed : 19827077120|<LVL::Debug>
    12/10/2013 13:44:54 upgrade_validate_file.sh|Remote SFTP request complete (0)|<LVL::Info>
    12/10/2013 13:44:54 upgrade_validate_file.sh|success|<LVL::Info>
    12/10/2013 13:44:54 upgrade_validate_file.sh|upgrade_validate_file.sh complete (rc=0)|<LVL::Info>
    12/10/2013 13:44:54 upgrade_validate_file.sh|Unmount DVD|<LVL::Info>
    12/10/2013 13:44:57 upgrade_get_file.sh|Starting upgrade_get_file.sh|<LVL::Info>
    12/10/2013 13:44:57 upgrade_get_file.sh|Parse argument method=remote_sftp|<LVL::Debug>
    12/10/2013 13:44:57 upgrade_get_file.sh|Parse argument source_dir=/|<LVL::Debug>
    12/10/2013 13:44:57 upgrade_get_file.sh|Parse argument file_name=UCSInstall_UCOS_8.6.2.21900-5.sgn.iso|<LVL::Debug>
    12/10/2013 13:44:57 upgrade_get_file.sh|Parse argument dest_dir=/common/download/|<LVL::Debug>
    12/10/2013 13:44:57 upgrade_get_file.sh|Parse argument remote_host=10.2.102.68|<LVL::Debug>
    12/10/2013 13:44:57 upgrade_get_file.sh|Parse argument user_name=cisco|<LVL::Debug>
    12/10/2013 13:44:57 upgrade_get_file.sh|Parse argument version=8.6.2.21900-5|<LVL::Debug>
    12/10/2013 13:44:57 upgrade_get_file.sh|Parse argument file_type=patch|<LVL::Debug>
    12/10/2013 13:44:57 upgrade_get_file.sh|Parse argument file_signed=yes|<LVL::Debug>
    12/10/2013 13:45:08 upgrade_get_file.sh|Process remote SFTP request|<LVL::Info>
    12/10/2013 13:45:08 upgrade_get_file.sh|source_dir=/, dest_file=/common/download//UCSInstall_UCOS_8.6.2.21900-5.sgn.iso, file_name=UCSInstall_UCOS_8.6.2.21900-5.sgn.iso|<LVL::Debug>
    12/10/2013 13:45:08 upgrade_get_file.sh|Starting SFTP|<LVL::Debug>
    12/10/2013 14:29:34 upgrade_get_file.sh|Mount /common/download//UCSInstall_UCOS_8.6.2.21900-5.sgn.iso on /mnt/source|<LVL::Info>
    12/10/2013 14:29:34 upgrade_get_file.sh|Download of iso file RTMTStart|<LVL::Notice>
    12/10/2013 14:29:34 upgrade_get_file.sh|Create md5 "/common/download/UCSInstall_UCOS_8.6.2.21900-5.sgn.iso.md5"|<LVL::Info>
    12/10/2013 14:30:49 upgrade_get_file.sh|MD5(/common/download/UCSInstall_UCOS_8.6.2.21900-5.sgn.iso)= e8:da:df:9a:3a:61:ee:27:4d:c5:4f:7b:77:78:bc:f1|<LVL::Debug>
    12/10/2013 14:30:49 upgrade_get_file.sh|Create md5 complete|<LVL::Info>
    12/10/2013 14:30:49 upgrade_get_file.sh|Authenticate file "/common/download/8.6.2.21900-5/checksum_file.sgn"|<LVL::Info>
    12/10/2013 14:30:49 upgrade_get_file.sh|File authentication complete|<LVL::Debug>
    12/10/2013 14:30:49 upgrade_get_file.sh|authenticating ISO name, filename=UCSInstall_UCOS_8.6.2.21900-5.sgn.iso, isoname=UCSInstall_UCOS_8.6.2.21900-5.sgn.iso|<LVL::Debug>
    12/10/2013 14:30:49 upgrade_get_file.sh|Download of iso file RTMTFinish|<LVL::Notice>
    12/10/2013 14:30:49 upgrade_get_file.sh|Checking for preflight script|<LVL::Debug>
    12/10/2013 14:30:49 upgrade_get_file.sh|Executing preflight script: /mnt/source/Cisco/install/bin/preflight isolocation=/mnt/source|<LVL::Info>
    12/10/2013 14:30:49 preflight|Starting preflight|<LVL::Info>
    12/10/2013 14:30:49 preflight|Validate preflight data|<LVL::Info>
    12/10/2013 14:30:49 preflight|Preflight data validation complete|<LVL::Info>
    12/10/2013 14:30:49 preflight|Determine upgrade type|<LVL::Info>
    12/10/2013 14:30:50 preflight|Active RH version = 4AS|<LVL::Debug>
    12/10/2013 14:30:50 preflight|New os version(xml) = 5Server|<LVL::Debug>
    12/10/2013 14:30:50 preflight|HW model = VMware|<LVL::Debug>
    12/10/2013 14:30:50 preflight|Upgrade type = RU|<LVL::Debug>
    12/10/2013 14:30:50 preflight|Obtain product type|<LVL::Info>
    12/10/2013 14:30:53 preflight|Obtained product type CallManager|<LVL::Info>
    12/10/2013 14:30:53 preflight|Processing preflight install mode|<LVL::Info>
    12/10/2013 14:30:53 preflight|Set preflight cancel utility|<LVL::Info>
    12/10/2013 14:30:53 preflight|Execute install preflight commands for CallManager:RU from /mnt/source/Cisco/install/preflight.xml|<LVL::Info>
    12/10/2013 14:30:53 preflight|Found 10 preflight commands to execute|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Execute preflight command (1/10): mkdir -p /common/preflight/CM/RU|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command returns 0|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Execute preflight command (2/10): cp -f /usr/local/platform/conf/dynamicConfig.xml /common/preflight/CM/RU/dynamicConfig.xml|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command returns 1|<LVL::Debug>
    12/10/2013 14:30:53 preflight|(CAPTURE) cp: cannot stat `/usr/local/platform/conf/dynamicConfig.xml': No such file or directory|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command did not complete (1). Continuing command processing...|<LVL::Warn>
    12/10/2013 14:30:53 preflight|Execute preflight command (3/10): cp -f /usr/local/thirdparty/jakarta-tomcat/webapps/cmplatform/WEB-INF/pages/install/dynamic.jsp /common/preflight/CM/RU/dynamic.jsp|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command returns 1|<LVL::Debug>
    12/10/2013 14:30:53 preflight|(CAPTURE) cp: cannot stat `/usr/local/thirdparty/jakarta-tomcat/webapps/cmplatform/WEB-INF/pages/install/dynamic.jsp': No such file or directory|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command did not complete (1). Continuing command processing...|<LVL::Warn>
    12/10/2013 14:30:53 preflight|Execute preflight command (4/10): cp -f /usr/local/thirdparty/jakarta-tomcat/webapps/cmplatform/WEB-INF/pages/install/install-confirm-content.jsp /common/preflight/CM/RU/install-confirm-content.jsp|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command returns 0|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Execute preflight command (5/10): cp -f /mnt/source/Cisco/install/dynamicConfig_RU.xml /usr/local/platform/conf/dynamicConfig.xml|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command returns 0|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Execute preflight command (6/10): mkdir -p /usr/local/thirdparty/jakarta-tomcat/webapps/cmplatform/WEB-INF/pages/install|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command returns 0|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Execute preflight command (7/10): cp -f /mnt/source/Cisco/install/dynamic_RU.jsp /usr/local/thirdparty/jakarta-tomcat/webapps/cmplatform/WEB-INF/pages/install/dynamic.jsp|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command returns 0|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Execute preflight command (8/10): cp -f /mnt/source/Cisco/install/install-confirm-content_RU.jsp /usr/local/thirdparty/jakarta-tomcat/webapps/cmplatform/WEB-INF/pages/install/install-confirm-content.jsp|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Preflight command returns 0|<LVL::Debug>
    12/10/2013 14:30:53 preflight|Execute preflight command (9/10): /mnt/source/Cisco/install/bin/tempDynamic.preflight /mnt/source/Cisco/install/dynamic_RU.jsp dynamic.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|Preflight command returns 0|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:53  starting tempDynamic.preflight...|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:53  Source dir/file = /mnt/source/Cisco/install/dynamic_RU.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:53  Destination file name = dynamic.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  Copying /mnt/source/Cisco/install/dynamic_RU.jsp to /usr/local/thirdparty/jakarta-tomcat/temp/1-cmplatform/WEB-INF/pages/install/dynamic.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  added/replaced /usr/local/thirdparty/jakarta-tomcat/temp/1-cmplatform/WEB-INF/pages/install/dynamic.jsp successfully|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  Copying /mnt/source/Cisco/install/dynamic_RU.jsp to /usr/local/thirdparty/jakarta-tomcat/temp/2-cmplatform/WEB-INF/pages/install/dynamic.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  added/replaced /usr/local/thirdparty/jakarta-tomcat/temp/2-cmplatform/WEB-INF/pages/install/dynamic.jsp successfully|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  Copying /mnt/source/Cisco/install/dynamic_RU.jsp to /usr/local/thirdparty/jakarta-tomcat/temp/4-cmplatform/WEB-INF/pages/install/dynamic.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  added/replaced /usr/local/thirdparty/jakarta-tomcat/temp/4-cmplatform/WEB-INF/pages/install/dynamic.jsp successfully|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  ... tempDynamic.preflight completed|<LVL::Debug>
    12/10/2013 14:30:54 preflight|Execute preflight command (10/10): /mnt/source/Cisco/install/bin/tempDynamic.preflight /mnt/source/Cisco/install/install-confirm-content_RU.jsp install-confirm-content.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|Preflight command returns 0|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  starting tempDynamic.preflight...|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  Source dir/file = /mnt/source/Cisco/install/install-confirm-content_RU.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  Destination file name = install-confirm-content.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  Copying /mnt/source/Cisco/install/install-confirm-content_RU.jsp to /usr/local/thirdparty/jakarta-tomcat/temp/1-cmplatform/WEB-INF/pages/install/install-confirm-content.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  added/replaced /usr/local/thirdparty/jakarta-tomcat/temp/1-cmplatform/WEB-INF/pages/install/install-confirm-content.jsp successfully|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  Copying /mnt/source/Cisco/install/install-confirm-content_RU.jsp to /usr/local/thirdparty/jakarta-tomcat/temp/2-cmplatform/WEB-INF/pages/install/install-confirm-content.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  added/replaced /usr/local/thirdparty/jakarta-tomcat/temp/2-cmplatform/WEB-INF/pages/install/install-confirm-content.jsp successfully|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  Copying /mnt/source/Cisco/install/install-confirm-content_RU.jsp to /usr/local/thirdparty/jakarta-tomcat/temp/4-cmplatform/WEB-INF/pages/install/install-confirm-content.jsp|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  added/replaced /usr/local/thirdparty/jakarta-tomcat/temp/4-cmplatform/WEB-INF/pages/install/install-confirm-content.jsp successfully|<LVL::Debug>
    12/10/2013 14:30:54 preflight|(CAPTURE) 12/10/2013 14:30:54  ... tempDynamic.preflight completed|<LVL::Debug>
    12/10/2013 14:30:54 preflight|Exiting with result 0|<LVL::Info>
    12/10/2013 14:30:54 upgrade_get_file.sh|preflight rc=0|<LVL::Debug>
    12/10/2013 14:30:54 upgrade_get_file.sh|Preflight completed successfully|<LVL::Info>
    12/10/2013 14:30:56 upgrade_get_file.sh|success|<LVL::Info>
    12/10/2013 14:30:56 upgrade_get_file.sh|upgrade_get_file.sh complete (rc=0)|<LVL::Info>
    12/30/2014 14:31:49 sd_cancelInstall.sh|Canceling active side processes
    12/30/2014 14:31:49 sd_cancelInstall.sh|Canceling active side processes done
    12/30/2014 14:31:49 sd_cancelInstall.sh|Canceling inactive side processes
    12/30/2014 14:31:50 sd_cancelInstall.sh|Canceling inactive side processes done
    12/10/2013 14:31:55 upgrade_install.sh|Starting Upgrade -- upgrade_install.sh|<LVL::Info>
    12/10/2013 14:31:55 upgrade_install.sh|Parse argument version=8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:31:55 upgrade_install.sh|Parse argument dest_dir=/common/download/|<LVL::Debug>
    12/10/2013 14:31:55 upgrade_install.sh|Parse argument work_dir=/var/log/install|<LVL::Debug>
    12/10/2013 14:31:59 upgrade_install.sh|/usr/local/platform/bin/startcsa status|<LVL::Debug>
    12/10/2013 14:31:59 upgrade_install.sh|CSA Status = 0|<LVL::Debug>
    12/10/2013 14:31:59 upgrade_install.sh|(CAPTURE) Cisco Security Agent is running with pid 23124|<LVL::Debug>
    12/10/2013 14:31:59 upgrade_install.sh|CSA Status = 0|<LVL::Debug>
    12/10/2013 14:31:59 upgrade_install.sh|/etc/init.d/ciscosec stop|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_install.sh|(CAPTURE) Stopping ciscosec:  [  OK  ]|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_install.sh|Upgrade the system|<LVL::Info>
    12/10/2013 14:32:14 upgrade_install.sh|Copy /mnt/source/Cisco/base_scripts/upgrade_manager.sh to /common/download/8.6.2.21900-5/upgrade_manager.sh|<LVL::Info>
    12/10/2013 14:32:14 upgrade_install.sh|Copy /mnt/source/Cisco/base_scripts/upgrade_manager.sh to /common/download/8.6.2.21900-5/upgrade_manager.sh complete|<LVL::Info>
    12/10/2013 14:32:14 upgrade_install.sh|Start upgrade manager|<LVL::Info>
    12/10/2013 14:32:14 upgrade_install.sh|/common/download/8.6.2.21900-5/upgrade_manager.sh type=upgrade basepath=/common/download/8.6.2.21900-5 file_name= logfile=/var/log/install/install_log_2013-12-30.13.44.35.log resultfile=/var/log/install/upgrade-results.xml work_dir=/var/log/install intf_file=/common/download/8.6.2.21900-5/upgrade_manager.xml|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Cleanup data from a prior upgrade attempt|<LVL::Info>
    12/10/2013 14:32:14 upgrade_manager.sh|Removing any /grub/boot/grub/grub.conf.recovery|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Invalidate upgrade partition|<LVL::Info>
    12/10/2013 14:32:14 upgrade_manager.sh|Clean up rpm any stale __db. files in rpmdb on the to side|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Removing any master RPM from /partB|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Removing any /partB/etc/opt/cisco/install.conf|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Invalidate any product configuration file|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Parse argument type=upgrade|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Parse argument basepath=/common/download/8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Parse argument file_name=|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Parse argument logfile=/var/log/install/install_log_2013-12-30.13.44.35.log|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Parse argument resultfile=/var/log/install/upgrade-results.xml|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Parse argument work_dir=/var/log/install|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Parse argument intf_file=/common/download/8.6.2.21900-5/upgrade_manager.xml|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|upgrade_type="upgrade"|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|L2 upgrade|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Initialize install support functions|<LVL::Info>
    12/10/2013 14:32:14 upgrade_manager.sh|Calling "source /mnt/source/Cisco/install/bin/install_func"|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Initialize install support functions complete|<LVL::Info>
    12/10/2013 14:32:14 upgrade_manager.sh|Check for Refresh Upgrade|<LVL::Info>
    12/10/2013 14:32:14 upgrade_manager.sh|Check if /mnt/source/upgradeConfig.xml exists|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Checking RedHat release version (4AS, 5Server)|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Initiate Refresh Upgrade|<LVL::Info>
    12/10/2013 14:32:14 upgrade_manager.sh|Copy /mnt/source/Cisco/install/bin/refresh_upgrade to /common/download/8.6.2.21900-5/refresh_upgrade|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Check that /common/download/8.6.2.21900-5/refresh_upgrade exists and is executable|<LVL::Debug>
    12/10/2013 14:32:14 upgrade_manager.sh|Calling exec /common/download/8.6.2.21900-5/refresh_upgrade type=upgrade basepath=/common/download/8.6.2.21900-5 file_name= logfile=/var/log/install/install_log_2013-12-30.13.44.35.log resultfile=/var/log/install/upgrade-results.xml work_dir=/var/log/install intf_file=/common/download/8.6.2.21900-5/upgrade_manager.xml|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|Parse argument type=upgrade|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|Parse argument basepath=/common/download/8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|Parse argument file_name=|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|Parse argument logfile=/var/log/install/install_log_2013-12-30.13.44.35.log|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|Parse argument resultfile=/var/log/install/upgrade-results.xml|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|Parse argument work_dir=/var/log/install|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|Parse argument intf_file=/common/download/8.6.2.21900-5/upgrade_manager.xml|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|No 'to' version specified. Extracting it from base path.|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|NEW_VERSION updated to 8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:32:14 refresh_upgrade|Refresh Upgrade Starting|<LVL::Info>
    12/10/2013 14:32:14 refresh_upgrade|IOWAIT monitor starting|<LVL::Info>
    12/10/2013 14:32:14 refresh_upgrade|Checksum the upgrade source on /mnt/source|<LVL::Info>
    12/10/2013 14:32:14 refresh_upgrade|Calling sha1sum -c /common/download/8.6.2.21900-5/checksum_file|<LVL::Debug>
    12/10/2013 14:34:14 refresh_upgrade|Checksum complete|<LVL::Info>
    12/10/2013 14:34:14 refresh_upgrade|Initialize staging area|<LVL::Info>
    12/10/2013 14:34:14 refresh_upgrade|Initialize globals for hard drive|<LVL::Debug>
    12/10/2013 14:34:14 refresh_upgrade|Calling rm -rf /common/refresh_upgrade /common/component|<LVL::Debug>
    12/10/2013 14:34:23 refresh_upgrade|Copy /mnt/source to /common/refresh_upgrade|<LVL::Info>
    12/10/2013 14:34:23 refresh_upgrade|Execute find /mnt/source and cpio to /common/refresh_upgrade. This may take several minutes.|<LVL::Debug>
    12/10/2013 14:37:31 refresh_upgrade|Copy source files to staging area complete|<LVL::Info>
    12/10/2013 14:37:31 refresh_upgrade|Initialize staging area complete|<LVL::Info>
    12/10/2013 14:37:31 refresh_upgrade|Prepare Refresh Upgrade support directory|<LVL::Info>
    12/10/2013 14:37:31 refresh_upgrade|Make /common/mnt/product_img mount point|<LVL::Info>
    12/10/2013 14:37:32 refresh_upgrade|Calling umount /common/mnt/product_img|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Setup support directories|<LVL::Info>
    12/10/2013 14:37:33 refresh_upgrade|Calling rm -rf /common/download/8.6.2.21900-5/Cisco|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling mkdir -p /common/download/8.6.2.21900-5/Cisco|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Create /common/cisco link to /common/download/8.6.2.21900-5/Cisco|<LVL::Info>
    12/10/2013 14:37:33 refresh_upgrade|Calling rm -rf /common/cisco|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling ln -s /common/download/8.6.2.21900-5/Cisco /common/cisco|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Copy files from /common/refresh_upgrade/images/product.img to /common/download/8.6.2.21900-5/Cisco|<LVL::Info>
    12/10/2013 14:37:33 refresh_upgrade|Calling mount /common/refresh_upgrade/images/product.img /common/mnt/product_img -o loop|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling cp -rf /common/mnt/product_img/bin/iproduct.sh /common/download/8.6.2.21900-5/Cisco/bin/iproduct.sh|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling cp -rf /common/mnt/product_img/bin/ihardware.sh /common/download/8.6.2.21900-5/Cisco/bin/ihardware.sh|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling cp -rf /common/mnt/product_img/bin/ihistory.sh /common/download/8.6.2.21900-5/Cisco/bin/ihistory.sh|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling cp -rf /common/mnt/product_img/bin/xproduct.sh /common/download/8.6.2.21900-5/Cisco/bin/xproduct.sh|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling cp -rf /common/mnt/product_img/bin/xcomponent.sh /common/download/8.6.2.21900-5/Cisco/bin/xcomponent.sh|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling cp -rf /common/mnt/product_img/bin/xplatformconfig.sh /common/download/8.6.2.21900-5/Cisco/bin/xplatformconfig.sh|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling cp -rf /common/mnt/product_img/bin/install_emailer /common/download/8.6.2.21900-5/Cisco/bin/install_emailer|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling cp -rf /common/mnt/product_img/bin/component_install /common/download/8.6.2.21900-5/Cisco/bin/component_install|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Calling umount /common/mnt/product_img|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|Setup install information in /common/download/8.6.2.21900-5/Cisco|<LVL::Info>
    12/10/2013 14:37:33 refresh_upgrade|Calling ln -s /common/refresh_upgrade/Cisco/install /common/download/8.6.2.21900-5/Cisco/install|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]|<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:33 refresh_upgrade|(CAPTURE) |<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|Setting up cisco specific enviroment|<LVL::Info>
    12/10/2013 14:37:36 refresh_upgrade|PATH=/common/download/8.6.2.21900-5/Cisco/bin:/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/sbin:/home/sftpuser:/root/.security|<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|LD_LIBRARY_PATH=/common/download/8.6.2.21900-5/Cisco/lib:/opt/cisco/install/lib:|<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|PYTHONPATH=/common/download/8.6.2.21900-5/Cisco/python:/usr/local/cm/lib:/usr/local/cm/lib:/usr/local/cm/lib:|<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|CISCO_INSTALL_CONF_PATH=/common/download/8.6.2.21900-5/Cisco/install/conf|<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|CISCO_INSTALL_BIN_PATH=/common/download/8.6.2.21900-5/Cisco/bin /opt/cisco/install/bin /usr/local/bin/base_scripts|<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|CISCO_PLATFORMCONF_PATH=/common/cisco /usr/local/platform/conf|<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|CISCO_INSTALL_LIB_PATH=/usr/local/bin/base_scripts|<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|Set logging globals for upgrade|<LVL::Info>
    12/10/2013 14:37:36 refresh_upgrade|Before: ILOG_CONTEXT="Upgrade", ILOG_FILE="/var/log/install/install_log_2013-12-30.13.44.35.log", ILOG_RESULTS_FILE="/var/log/install/upgrade-results.xml"|<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|After: ILOG_CONTEXT="Upgrade", ILOG_FILE="/common/log/install/install_log_2013-12-30.13.44.35.log", ILOG_RESULTS_FILE="/common/log/install/upgrade-results.xml"|<LVL::Debug>
    12/10/2013 14:37:36 refresh_upgrade|Initialize APIs|<LVL::Info>
    12/10/2013 14:37:36 refresh_upgrade|Initializing the product API|<LVL::Info>
    12/10/2013 14:37:37 refresh_upgrade|Initializing the hardware API|<LVL::Info>
    12/10/2013 14:37:38 ServerApiManager|INITIALIZE: sam_legacy_mode_init=1|<LVL::Debug>
    12/10/2013 14:37:46 ServerApiManager|INITIALIZE: sam_hssi_mode_init=0|<LVL::Debug>
    12/10/2013 14:37:46 refresh_upgrade|Initializing the history log API|<LVL::Info>
    12/10/2013 14:37:46 refresh_upgrade|Initializing the xplatformconfig API|<LVL::Info>
    12/10/2013 14:37:46 refresh_upgrade|Initializing the xproduct API|<LVL::Info>
    12/10/2013 14:37:46 refresh_upgrade|Initialize setup functions|<LVL::Info>
    12/10/2013 14:37:46 refresh_upgrade|Calling "source /common/download/8.6.2.21900-5/Cisco/install/setup/utils.sh"|<LVL::Debug>
    12/10/2013 14:37:46 refresh_upgrade|Initialize setup functions complete|<LVL::Info>
    12/10/2013 14:37:46 refresh_upgrade|Getting deployment ID from active side|<LVL::Info>
    12/10/2013 14:37:46 refresh_upgrade|Copy /usr/local/platform/conf/platformConfig.xml to /common/cisco/platformConfig.xml|<LVL::Info>
    12/10/2013 14:37:46 refresh_upgrade|Calling "cp /usr/local/platform/conf/platformConfig.xml /common/cisco/platformConfig.xml"|<LVL::Debug>
    12/10/2013 14:37:48 refresh_upgrade|Check if the upgrade is allowed|<LVL::Info>
    12/10/2013 14:37:48 refresh_upgrade|Validate hardware for the upgrade|<LVL::Info>
    12/10/2013 14:37:48 refresh_upgrade|Hardware is supported for the upgrade|<LVL::Info>
    12/10/2013 14:37:50 refresh_upgrade|Validate hardware for "callmanager" deployment|<LVL::Info>
    12/10/2013 14:37:50 refresh_upgrade|Hardware is supported for "callmanager" deployment|<LVL::Info>
    12/10/2013 14:37:50 refresh_upgrade|Validate from version 8.5.1.10000-26|<LVL::Info>
    12/10/2013 14:37:50 refresh_upgrade|Upgrade from 8.5.1.10000-26 allowed|<LVL::Info>
    12/10/2013 14:37:50 refresh_upgrade|Validate free space for the upgrade|<LVL::Info>
    12/10/2013 14:37:50 refresh_upgrade|(CAPTURE) Free space: 26040668160, Needed space: 15014745300|<LVL::Debug>
    12/10/2013 14:37:50 refresh_upgrade|Free space validation complete|<LVL::Info>
    12/10/2013 14:37:50 refresh_upgrade|Run component export scripts|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Initializing xproduct.sh API|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Initializing xcomponent.sh API|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Initializing xplatformconfig.sh API|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Parse argument export|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Parse argument mode=refresh-upgrade|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Parse argument install_root=/common/refresh_upgrade/Cisco|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Parse argument data_root=/common|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Run component export scripts, mode refresh-upgrade|<LVL::Info>
    12/10/2013 14:37:50 component_install|Initialize product data, mode refresh-upgrade|<LVL::Info>
    12/10/2013 14:37:50 component_install|Initialize "to" side product version|<LVL::Info>
    12/10/2013 14:37:50 component_install|Access "to" side API|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Got version 8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Initialize "to" side product version complete|<LVL::Info>
    12/10/2013 14:37:50 component_install|Initialize "from" side product version|<LVL::Info>
    12/10/2013 14:37:50 component_install|Access "from" side API|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Got version 8.5.1.10000-26|<LVL::Debug>
    12/10/2013 14:37:50 component_install|Initialize "from" side product version complete|<LVL::Info>
    12/10/2013 14:37:50 component_install|Initialize product data complete|<LVL::Info>
    12/10/2013 14:37:50 component_install|Initialize component data, mode refresh-upgrade|<LVL::Info>
    12/10/2013 14:37:50 component_install|Initialize ucos "to" side version|<LVL::Info>
    12/10/2013 14:37:50 component_install|Access "to" side API|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Got version 8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Initialize ucos "to" side version complete|<LVL::Info>
    12/10/2013 14:37:51 component_install|Initialize ucos "from" side version|<LVL::Info>
    12/10/2013 14:37:51 component_install|Component ucos available on active side|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Access "from" side API|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Got version 8.5.1.10000-26|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Initialize ucos "from" side version complete|<LVL::Info>
    12/10/2013 14:37:51 component_install|Initialize global data complete|<LVL::Info>
    12/10/2013 14:37:51 component_install|Build the command list for ucos|<LVL::Info>
    12/10/2013 14:37:51 component_install|Initialize command list|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Build ucos export phase commands|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Processing ucos export element|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Building the command list for ucos is complete|<LVL::Info>
    12/10/2013 14:37:51 component_install|Command execution for ucos component RTMTStart|<LVL::Notice>
    12/10/2013 14:37:51 component_install|Execute commands in the command list for ucos component|<LVL::Info>
    12/10/2013 14:37:51 component_install|No commands to execute for ucos component|<LVL::Info>
    12/10/2013 14:37:51 component_install|Command execution for ucos component is complete|<LVL::Info>
    12/10/2013 14:37:51 component_install|Command execution for ucos component RTMTFinish|<LVL::Notice>
    12/10/2013 14:37:51 component_install|Initialize component data, mode refresh-upgrade|<LVL::Info>
    12/10/2013 14:37:51 component_install|Initialize ucplatform "to" side version|<LVL::Info>
    12/10/2013 14:37:51 component_install|Access "to" side API|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Got version 8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Initialize ucplatform "to" side version complete|<LVL::Info>
    12/10/2013 14:37:51 component_install|Initialize ucplatform "from" side version|<LVL::Info>
    12/10/2013 14:37:51 component_install|Component ucplatform available on active side|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Access "from" side API|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Got version 8.5.1.10000-26|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Initialize ucplatform "from" side version complete|<LVL::Info>
    12/10/2013 14:37:51 component_install|Initialize global data complete|<LVL::Info>
    12/10/2013 14:37:51 component_install|Build the command list for ucplatform|<LVL::Info>
    12/10/2013 14:37:51 component_install|Initialize command list|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Build ucplatform export phase commands|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Processing ucplatform export element|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Processing ucplatform script element|<LVL::Debug>
    12/10/2013 14:37:51 component_install|Add "security_prepare RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Processing ucplatform script element|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Add "password_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Processing ucplatform script element|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Add "ssh_keys_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Processing ucplatform script element|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Add "installed_options_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Processing ucplatform script element|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Add "platform_certs_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Processing ucplatform script element|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Add "servm_export RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Processing ucplatform script element|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Add "network_files_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Processing ucplatform script element|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Add "drf_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Building the command list for ucplatform is complete|<LVL::Info>
    12/10/2013 14:37:52 component_install|Command execution for ucplatform component RTMTStart|<LVL::Notice>
    12/10/2013 14:37:52 component_install|Execute commands in the command list for ucplatform component|<LVL::Info>
    12/10/2013 14:37:52 component_install|Search path is /common/refresh_upgrade/Cisco/ucplatform/scripts:/usr/local/cm/script|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Checking command /common/refresh_upgrade/Cisco/ucplatform/scripts/security_prepare|<LVL::Debug>
    12/10/2013 14:37:52 component_install|Execute "/common/refresh_upgrade/Cisco/ucplatform/scripts/security_prepare RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Parse arguments|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Validate arguments|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Initialize global variables|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Handle Security Information|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Export security information|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Export /etc/shadow file|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Export login warning message|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Export SFTP data|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Export DRF data|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Export CCM Service Data|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Export IPSec Data|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|get_fips_status returning partB fips_cnf as 0|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Export Racoon Data|<LVL::Debug>
    12/10/2013 14:37:52 security_prepare|Export Tomcat Data|<LVL::Debug>
    12/10/2013 14:37:53 security_prepare|security information prepare successful|<LVL::Info>
    12/10/2013 14:37:53 component_install|Search path is /common/refresh_upgrade/Cisco/ucplatform/scripts:/usr/local/cm/script|<LVL::Debug>
    12/10/2013 14:37:53 component_install|Checking command /common/refresh_upgrade/Cisco/ucplatform/scripts/password_migrate|<LVL::Debug>
    12/10/2013 14:37:53 component_install|Execute "/common/refresh_upgrade/Cisco/ucplatform/scripts/password_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug>
    12/10/2013 14:37:53 password_migrate|Handle password information|<LVL::Debug>
    12/10/2013 14:37:53 password_migrate|Export password information|<LVL::Info>
    12/10/2013 14:37:53 password_migrate|Calling mkdir -p /common/component/ucplatform/etc/pam.d|<LVL::Info>
    12/10/2013 14:37:53 password_migrate|password information migrate successful|<LVL::Info>
    12/10/2013 14:37:53 component_install|Search path is /common/refresh_upgrade/Cisco/ucplatform/scripts:/usr/local/cm/script|<LVL::Debug>
    12/10/2013 14:37:53 component_install|Checking command /common/refresh_upgrade/Cisco/ucplatform/scripts/ssh_keys_migrate|<LVL::Debug>
    12/10/2013 14:37:53 component_install|Execute "/common/refresh_upgrade/Cisco/ucplatform/scripts/ssh_keys_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug>
    12/10/2013 14:37:53 component_install|Search path is /common/refresh_upgrade/Cisco/ucplatform/scripts:/usr/local/cm/script|<LVL::Debug>
    12/10/2013 14:37:53 component_install|Checking command /common/refresh_upgrade/Cisco/ucplatform/scripts/installed_options_migrate|<LVL::Debug>
    12/10/2013 14:37:53 component_install|Execute "/common/refresh_upgrade/Cisco/ucplatform/scripts/installed_options_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug>
    12/10/2013 14:37:55 component_install|Search path is /common/refresh_upgrade/Cisco/ucplatform/scripts:/usr/local/cm/script|<LVL::Debug>
    12/10/2013 14:37:55 component_install|Checking command /common/refresh_upgrade/Cisco/ucplatform/scripts/platform_certs_migrate|<LVL::Debug>
    12/10/2013 14:37:55 component_install|Execute "/common/refresh_upgrade/Cisco/ucplatform/scripts/platform_certs_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug>
    12/10/2013 14:37:55 platform_certs_migrate|Source major version: 8|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|Export platform certificates|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|starting refresh upgrade export certs copy|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|creating /common/component/ucplatform|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|starting refresh upgrade export certs copy|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|creating /common/component/ucplatform|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|exporting certmon config|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|creating /common/component/ucplatform/config|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|copy /usr/local/platform/conf/certMonitorConfig.xml /common/component/ucplatform/conf/|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|Export bulk sftp config|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|sftp config not available|<LVL::Info>
    12/10/2013 14:37:55 platform_certs_migrate|platform certificates migrate successful|<LVL::Info>
    12/10/2013 14:37:55 component_install|Search path is /common/refresh_upgrade/Cisco/ucplatform/scripts:/usr/local/cm/script|<LVL::Debug>
    12/10/2013 14:37:55 component_install|Checking command /common/refresh_upgrade/Cisco/ucplatform/scripts/servm_export|<LVL::Debug>
    12/10/2013 14:37:55 component_install|Execute "/common/refresh_upgrade/Cisco/ucplatform/scripts/servm_export RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug>
    12/10/2013 14:37:56 servm_export|Start servm Export processing|<LVL::Info>
    12/10/2013 14:37:56 servm_export|Copying /usr/local/cm//../platform/conf/activate.conf to /common/component/ucplatform|<LVL::Info>
    12/10/2013 14:37:56 servm_export|Copying /usr/local/cm//../platform/conf/services.conf to /common/component/ucplatform|<LVL::Info>
    12/10/2013 14:37:56 servm_export|SUCCESS: servm Export processing completed|<LVL::Info>
    12/10/2013 14:37:56 component_install|Search path is /common/refresh_upgrade/Cisco/ucplatform/scripts:/usr/local/cm/script|<LVL::Debug>
    12/10/2013 14:37:56 component_install|Checking command /common/refresh_upgrade/Cisco/ucplatform/scripts/network_files_migrate|<LVL::Debug>
    12/10/2013 14:37:56 component_install|Execute "/common/refresh_upgrade/Cisco/ucplatform/scripts/network_files_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug>
    12/10/2013 14:37:56 network_files_migrate|Export network configuration files to /common/component/ucplatform/etc/sysconfig/network-scripts|<LVL::Info>
    12/10/2013 14:37:56 network_files_migrate|Calling mkdir -p /common/component/ucplatform/etc/sysconfig/network-scripts|<LVL::Debug>
    12/10/2013 14:37:56 network_files_migrate|Calling mkdir -p /common/component/ucplatform/common|<LVL::Debug>
    12/10/2013 14:37:56 network_files_migrate|Copy network configuration files|<LVL::Info>
    12/10/2013 14:37:56 network_files_migrate|Copying /etc/sysconfig/network-scripts/ifcfg-eth0 to /common/component/ucplatform/etc/sysconfig/network-scripts/ifcfg-eth0|<LVL::Debug>
    12/10/2013 14:37:56 network_files_migrate|Copying /etc/sysconfig/network to /common/component/ucplatform/etc/sysconfig/network|<LVL::Debug>
    12/10/2013 14:37:56 network_files_migrate|Copying /etc/hosts to /common/component/ucplatform/etc/hosts|<LVL::Debug>
    12/10/2013 14:37:57 network_files_migrate|Copying /etc/resolv.conf to /common/component/ucplatform/etc/resolv.conf|<LVL::Debug>
    12/10/2013 14:37:57 network_files_migrate|Copying //etc/nsswitch.conf to /common/component/ucplatform/etc/nsswitch.conf|<LVL::Debug>
    12/10/2013 14:37:57 network_files_migrate|Copy network configuration files complete|<LVL::Info>
    12/10/2013 14:37:57 network_files_migrate|Export network configuration files complete|<LVL::Info>
    12/10/2013 14:37:57 component_install|Search path is /common/refresh_upgrade/Cisco/ucplatform/scripts:/usr/local/cm/script|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Checking command /common/refresh_upgrade/Cisco/ucplatform/scripts/drf_migrate|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Execute "/common/refresh_upgrade/Cisco/ucplatform/scripts/drf_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Command execution for ucplatform component is complete|<LVL::Info>
    12/10/2013 14:37:57 component_install|Command execution for ucplatform component RTMTFinish|<LVL::Notice>
    12/10/2013 14:37:57 component_install|Initialize component data, mode refresh-upgrade|<LVL::Info>
    12/10/2013 14:37:57 component_install|Initialize ucplatform_cluster "to" side version|<LVL::Info>
    12/10/2013 14:37:57 component_install|Access "to" side API|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Got version 8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Initialize ucplatform_cluster "to" side version complete|<LVL::Info>
    12/10/2013 14:37:57 component_install|Initialize ucplatform_cluster "from" side version|<LVL::Info>
    12/10/2013 14:37:57 component_install|Component ucplatform_cluster available on active side|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Access "from" side API|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Got version 8.5.1.10000-26|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Initialize ucplatform_cluster "from" side version complete|<LVL::Info>
    12/10/2013 14:37:57 component_install|Initialize global data complete|<LVL::Info>
    12/10/2013 14:37:57 component_install|Build the command list for ucplatform_cluster|<LVL::Info>
    12/10/2013 14:37:57 component_install|Initialize command list|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Build ucplatform_cluster export phase commands|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Processing ucplatform_cluster export element|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Processing ucplatform_cluster script element|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Add "platform_sso_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform_cluster /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Building the command list for ucplatform_cluster is complete|<LVL::Info>
    12/10/2013 14:37:57 component_install|Command execution for ucplatform_cluster component RTMTStart|<LVL::Notice>
    12/10/2013 14:37:57 component_install|Execute commands in the command list for ucplatform_cluster component|<LVL::Info>
    12/10/2013 14:37:57 component_install|Search path is /common/refresh_upgrade/Cisco/ucplatform_cluster/scripts:/usr/local/cm/script|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Checking command /common/refresh_upgrade/Cisco/ucplatform_cluster/scripts/platform_sso_migrate|<LVL::Debug>
    12/10/2013 14:37:57 component_install|Execute "/common/refresh_upgrade/Cisco/ucplatform_cluster/scripts/platform_sso_migrate RU Export 8.6.2.21900-5 8.5.1.10000-26 /common/component/ucplatform_cluster /usr/local/cm/ /common/log/install/capture.txt"|<LVL::Debug>
    12/10/2013 14:37:58 platform_sso_migrate|Source major version: 8|<LVL::Info>
    12/10/2013 14:37:58 component_install|Command execution for ucplatform_cluster component is complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Command execution for ucplatform_cluster component RTMTFinish|<LVL::Notice>
    12/10/2013 14:37:58 component_install|Initialize component data, mode refresh-upgrade|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize thirdparty "to" side version|<LVL::Info>
    12/10/2013 14:37:58 component_install|Access "to" side API|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Got version 8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Initialize thirdparty "to" side version complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize thirdparty "from" side version|<LVL::Info>
    12/10/2013 14:37:58 component_install|Component thirdparty available on active side|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Access "from" side API|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Got version 8.5.1.10000-26|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Initialize thirdparty "from" side version complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize global data complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Build the command list for thirdparty|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize command list|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Build thirdparty export phase commands|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Processing thirdparty export element|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Building the command list for thirdparty is complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Command execution for thirdparty component RTMTStart|<LVL::Notice>
    12/10/2013 14:37:58 component_install|Execute commands in the command list for thirdparty component|<LVL::Info>
    12/10/2013 14:37:58 component_install|No commands to execute for thirdparty component|<LVL::Info>
    12/10/2013 14:37:58 component_install|Command execution for thirdparty component is complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Command execution for thirdparty component RTMTFinish|<LVL::Notice>
    12/10/2013 14:37:58 component_install|Initialize component data, mode refresh-upgrade|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize serviceability_core "to" side version|<LVL::Info>
    12/10/2013 14:37:58 component_install|Access "to" side API|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Got version 8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Initialize serviceability_core "to" side version complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize serviceability_core "from" side version|<LVL::Info>
    12/10/2013 14:37:58 component_install|Component serviceability_core available on active side|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Access "from" side API|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Got version 8.5.1.10000-26|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Initialize serviceability_core "from" side version complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize global data complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Build the command list for serviceability_core|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize command list|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Build serviceability_core export phase commands|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Processing serviceability_core export element|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Building the command list for serviceability_core is complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Command execution for serviceability_core component RTMTStart|<LVL::Notice>
    12/10/2013 14:37:58 component_install|Execute commands in the command list for serviceability_core component|<LVL::Info>
    12/10/2013 14:37:58 component_install|No commands to execute for serviceability_core component|<LVL::Info>
    12/10/2013 14:37:58 component_install|Command execution for serviceability_core component is complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Command execution for serviceability_core component RTMTFinish|<LVL::Notice>
    12/10/2013 14:37:58 component_install|Initialize component data, mode refresh-upgrade|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize database "to" side version|<LVL::Info>
    12/10/2013 14:37:58 component_install|Access "to" side API|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Got version 8.6.2.21900-5|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Initialize database "to" side version complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize database "from" side version|<LVL::Info>
    12/10/2013 14:37:58 component_install|Component database available on active side|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Access "from" side API|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Got version 8.5.1.10000-26|<LVL::Debug>
    12/10/2013 14:37:58 component_install|Initialize database "from" side version complete|<LVL::Info>
    12/10/2013 14:37:58 component_install|Initialize global data complete|<LVL::Info>

    hi gupta ,
    admin:run sql car select * from tbl_event_log
    Failed  to get Connection.Connector(NOT CONNECTED:  Driver=com.informix.jdbc.IfxDr                                                 iver;)
    admin:run sql car select * from tbl_system_preferences
    Failed to get Connection.Connector(NOT CONNECTED: Driver=com.informix.jdbc.IfxDriver;)
    restarted the below sevices
    Cisco CDR Agent
    Cisco Database Layer Monitor
    Cisco CDR Repository Manager
    Cisco CAR                 Scheduler
    Cisco SOAP - CDRonDemand                 Service
    Cisco CAR Web                 Service
    while accessing cdr reporting showing below error .
    ------------------------------------------WARNING-----------------------------------------
    *  Cluster wide parameter 'Call Diagnostics Enabled flag' is set  to false.  Hence no QoS information will be generated on calls. If  required,  please configure the same from service parameter page for Call  Manager  service. 
    *  Problem in determining 2M/HWM breach status.  Tbl_System_Preferences  table might be corrupted. Please click on the  'Restore Defaults' button  to update the table with default values. 
    *  Tbl_System_Preferences table is corrupted. Please click on the  'Restore  Defaults' button to update the table with default values. 
    *  Problem in determining Loader Configuration.  Tbl_System_Preferences  table might be corrupted. Please click on the  'Restore Defaults' button  to update the table with default values. 
    -------------------------------------------NOTICE------------------------------------------
    * Problem in determining Billing Tables status. Please check the  CAR DB for tables Tbl_Billing_Data and Tbl_Billing_Error. 
    *  Problem in getting the Mail parameters. It might result in   mails/alerts/notifications not been sent to CAR Administrators. Please   configure this at CAR->System->System Parameters->Mail   Parameters. 
    * Mail  id for 'ccmadmin' is not available. CAR  Reports/Notifications/Alert  Emails might not be able to sent to this  user properly. Please  configure a mail id in end user configuration  page.
    if we apllied Restore Defaults ,geting below error
    Error Code
    Error Description
    30029
    Direct access to this screen is not allowed.
    and try to access system and data base , getting below error
    Error Code
    Error Description
    10012
    Database Error. Contact System Administrator.
    Does any other way to avoid cdr and do the istallation .

  • Problem migrating CUCM 7.1.5 to 9.1(2) (Jump Upgrade)

    Hello all,
    I am facing an issue when trying to upgrade from CUCM 7.1.5.30000-1 to 9.1(2) over UCS following the jump upgrade procedure.
    I have installed 7.1.5 CUCM software on the UCS using the 9.1(2) ova. (two nodes cluster), and after that restored the CUCM backup.
    I have loaded "ciscocm.refresh_upgrade_v1.3.cop" file before the upgrade on both nodes.
    The connectivity with NTP server is good.
    The upgrade file I am using is "UCSInstall_UCOS_9.1.2.11900-12.sgn".
    The installation begins on Publisher but after three hours and when it is ending it fails. I have checked the installation logs and this is what it shows:
    05/23/2014 17:45:51 component_install|(CAPTURE) Fri May 23 17:41:46 2014 cm-dbl-install DEBUG: cm-dbl-install [0]|<LVL::Debug>
    05/23/2014 17:45:51 component_install|(CAPTURE) Fri May 23 17:41:46 2014 cm-dbl-install DEBUG: <--|<LVL::Debug>
    05/23/2014 17:45:51 component_install|File:/opt/cisco/install/bin/component_install:756, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
    05/23/2014 17:45:51 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:269, Function: refresh_upgrade(), failed to refresh_upgrade infrastructure_post components|<LVL::Critical>
    05/23/2014 17:45:51 post_install|File:/opt/cisco/install/bin/post_install:911, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -refresh-upgrade failed (1)|<LVL::Error>
    05/23/2014 17:45:51 post_install|Exiting with result 1|<LVL::Info>
    05/23/2014 17:45:51 post_install|INSTALL_TYPE="Refresh Upgrade"|<LVL::Debug>
    05/23/2014 17:45:51 post_install|Process refresh upgrade failure|<LVL::Info>
    05/23/2014 17:45:51 post_install|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]|<LVL::Debug>
    05/23/2014 17:45:51 post_install|Retore grub.conf from grub.conf.recovery|<LVL::Info>
    05/23/2014 17:45:51 post_install|Copy recovery file, /grub/boot/grub/grub.conf.recovery, to /grub/boot/grub/grub.conf|<LVL::Debug>
    05/23/2014 17:45:51 post_install|Retore of grub.conf complete|<LVL::Info>
    05/23/2014 17:45:51 post_install|Invalidate upgrade partition|<LVL::Info>
    05/23/2014 17:45:51 post_install|Removing master RPM|<LVL::Debug>
    05/23/2014 17:45:52 post_install|Removing /etc/opt/cisco/install.conf|<LVL::Debug>
    05/23/2014 17:45:52 post_install|Invalidate any product configuration file|<LVL::Debug>
    05/23/2014 17:45:52 post_install|Setting product and deployment version attributes in /etc/opt/cisco/install/conf/callmanager_product.conf to 0.0.0.0000-0000|<LVL::Debug>
    05/23/2014 17:45:52 post_install|Cleanup refresh upgrade staging areas|<LVL::Debug>
    05/23/2014 17:46:14 post_install|Parse argument status=upgrade.stage.error|<LVL::Debug>
    05/23/2014 17:46:14 post_install|_set_upgrade_status_attribute: status set to upgrade.stage.error|<LVL::Debug>
    05/23/2014 17:46:14 post_install|File:/opt/cisco/install/bin/post_install:580, Function: handle_refresh_upgrade_failure(), Refresh upgrade failed. Trying to reboot to currently active version.|<LVL::Error>
    05/23/2014 17:47:19 hardware_check.sh|Initializing hardware library on boot|<LVL::Info>
    05/23/2014 17:47:19 ServerApiManager|In main with args -|initialize|- called file |/usr/local/bin/base_scripts/server_api_manager.sh| - and current mode=HSSI_Mode |<LVL::Debug>
    05/23/2014 17:47:19 ServerApiManager||Method: initialize args: |- current mode=HSSI_Mode completed with code [0]|<LVL::Debug>
    05/23/2014 17:47:19 ServerApiManager|In main with args -|initHardwareLibrary|- called file |/usr/local/bin/base_scripts/server_api_manager.sh| - and current mode=HSSI_Mode |<LVL::Debug>
    05/23/2014 17:47:19 ServerApiManager|Sam_reset being called|
    I think it is similar to this other case: https://supportforums.cisco.com/discussion/12181161/cucm-vm-715-912-migration-error#comment-9719721
    Can anyone help me with this? I am stuck on the migration.
    Thanks!!
    Héctor

    Just for the record. I found the solution to my problem. Checking more logs I read this:
    The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.
    "/usr/local/cm/script/cm-dbl-ontape_backup-install RU PostInstall 9.1.2.11900-12 7.1.5.30000-1 /usr/local/cm/ /common/component/database /common/log/install/capture.txt " terminated. Exceeded max time (240)
    The system will now halt.
    So I accessed the Dissaster Recovery Section on CUCM and deleted the tape backup device that was configured there. After deleting it the upgrade went well.

  • CUCM Upgrade from 8.6(2a) / 8.6.2.20000-2 to 8.6.(2a)SU2 (8.6.2.22900-9)

    I'm getting ready to upgrade a client's CUCM cluster from 8.6(2a) / 8.6.2.20000-2 to 
    8.6.(2a)SU2 (8.6.2.22900-9).  They use extension mobilty with UCCX version 8.5.1.11003-32.
    Does anyone know of any issues with ugprading this cluster vis a vis their UCCX version ?
    The current CUCM Version 8.6(2a) / 8.6.2.20000-2 shows a JTAPI shows the following JTAPI version:
    admin:show packages active cm-jtapi-
    Active Side Package(s): for cm-jtapi- package(s)
    cm-jtapi-plugin-8.6.2.10000-2
    From the ReadMe For Cisco Unified Communications Manager Release 8.6(2a)SU2
    http://www.cisco.com/web/software/282074295/93949/cucm-readme-862asu2.pdf
    I see that it shows:
    cm-jtapi-plugin-8.6.2.10000-10.i386.rpm
    Once I have performed the CUCM upgrade - do I need to upgrade the JTAPI plugin on the UCCX Platform?
    TIA

    Mohamed,
    I have not actually peformed the upgrade yet.  If you have done so - please reply with any lessons learned that you have.
    I would upload the file to all the servers in your cluster prior to your upgrade maintenance window.  This should not be service impacting.
    Then during your upgrade maintenance window -
    Step 15 Once the Publisher and the subscribers have been upgraded, a version switch must be completed so                  the servers reboot to the new upgraded partition as follows;
    Web Browse to the Publisher’s OS Administration GUI
    To restart the system and activate the upgrade, choose Settings > Version; then, click Switch Version.
    The system restarts and should be running the upgraded software. Once the Publisher is accessible, proceed with the subscribers.
    Good Luck,
    Amir

  • CUCM 8.6 upgrade to 9.1(2)

    Hello all,
    I've done some 8.5 upgrades to 9.1 so I'm quite familiar with the refresh upgrade process and the additional server downtime vs. say and 8 to 8.5.
    On reading the upgrade guide for CUCM 9.1(1), I stumbled across this line on page 5 -
    "You cannot install upgrade software on your node while the system continues to operate."
    In the past when doing an Linux to Linux upgrade without a refresh required this certainly wasn't the case. You can't make changes and EM should be turned off but the upgrade was always going on in the background and a switch version was run when complete.
    Has this changed?
    Can someone chime in who has done a 8.6 to 9.1(x) upgrade on this?
    I've got a really tight outage/downtime window to get a cluster upgraded and with 2 servers still on MCS, I don't think I can do it if I can't get a change freeze in place and get the Pub upgraded without taking it down. Having to start and finish the Pub, subs and the physicals in the window might not be possible even with a parallel upgrade.
    Thanks
    Jon

    Hi Jon,
    +5 to my friend Aman for his good notes here :)
    This has NOT changed....here is the note from the upgrade guide;
    Linux to Linux (L2) upgrade
    There is very little server downtime during an L2 upgrade.
    An L2 upgrade is accomplished by installing the new software release in the inactive
    partition while the node continues to run and operate on the existing software
    in the active partition.
    The software releases are switched on reboot. The reboot can be either automatic,
    after the new software release is installed, or initiated manually at a later time through
    an administrator command. Some examples of an L2 upgrade are upgrades from
    Release 6.1(3) to 7.1(5), from 7.1(2) to 8.0(3), or from 8.6(1) to 9.1(1).
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/elmuserguide/9_1_1/license_migration/CUCM_BK_CBF8B56A_00_cucm-license-upgrade-guide.pdf
    Cheers!
    Rob

  • Upgrade our 8.0.3 CUCM to version 9.1.X

                       Hi All,
    We are planning to  upgrade the our cucm 8.0.3 to 9.1.x
    Can anyone  tell us the steps for the upgradation. We are using the extension mobility. Prior to upgrade we already upgraded the router IOS to c2900-universalk9-mz.SPA.152-4.M5.bin(cisco 2900 series routers). the upgrade on plan on comming weekend
    regards
    jomyk

    Hi Chris,
    Thanks for the update.following is our hw details. we dont have any plan to upgrade the HW
    HW Platform       : 7825I4
    Processors        : 1
    Type              : Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz
    CPU Speed         : 3000
    Memory            : 4096 MBytes
    Read the document according to that prepared a document. Could you cross check the document whether i missed any thing  to consider the upgradation plan
    III. Upgrade considerations
    Need to apply the refresh upgrade cop file before doing the actual upgrade for the cucm using 9.1 image.
    Sequence for the refresh /upgrade should be
    a-Do the refresh upgrade (install the COP file) on the publisher and on the other node( subscriber).
    b-Do the upgrade (install the ISO image of the 9.1) on the publisher server then directly do the switch version (utils system switch-version) on the publisher server.
    c-Once the switch version is done on the publisher successfully, do the upgrade on the subscriber server and then do a switch version on that subscriber.
    B. When we install upgrade software, there will be a temporary node outage while the Cisco Unified Communications Manager software is installed.
    C. When we upgrade a cluster we will start by upgrading the publisher node. we can begin upgrading subsequent nodes in parallel after the publisher node reaches a specified point in the upgrade. There will be a temporary node outage until all subscriber nodes get upgraded to the new software version.
    d. Disable the Cisco Extension Mobility service by navigating to Cisco Unified Serviceability > Tools > Service Activation
    III. Upgrade from CD Rom
         Create an upgrade disk by burning the upgrade file that you downloaded onto a DVD as an ISO image.
    a.
    Insert the new DVD into the disc   drive on the local server that is to be upgraded.
    b.
    Log in to Cisco Unified Communications   Operating System Administration.
    c.
    Navigate to Software Upgrades   > Install/Upgrade.
    The   Software Installation/Upgrade window displays.
    From the Source list, choose DVD.
    d.
    Enter a slash (/) in the   Directory field.
    e.
    To use the Email Notification   feature, enter your Email Destination and SMTP Server in the fields provided.
    f.
    To continue the upgrade process,   click Next.
    g.
    Choose the upgrade version that   you want to install and click Next.
    h.
    In the next window, monitor the   progress of the download.
    i.
    If you want to run the upgraded   software at the completion of the upgrade process and automatically reboot to   the upgraded partition, choose Switch to new version after upgrade. The   system restarts and is running the upgraded software.
    j.
    If you want to install the   upgrade and then manually switch to the upgraded partition at a later time,   do the following steps:
    •a.          Choose Do not switch to new   version after upgrade.
    •b.          Click Next
    The Upgrade Status window   displays the Upgrade log.
    •c.          When the installation completes,   click Finish.
    •d.          To restart the system and   activate the upgrade, choose Settings > Version; then, click Switch   Version.
    The system restarts running the   upgraded software.
    IV. Post-upgrade   tasks
    •a.         Enable the Cisco Extension Mobility service by navigating to Cisco Unified Serviceability   > Tools > Service Activation.
    •b.         Verify phone functions by making   the following types of calls: 
    •a.          Voice mail
    •b.          Interoffice
    •c.          Mobile phone
    •d.          Local
    •e.          National
    •f.           International
    •g.          Shared line
    c.Test the following   phone features:
    Conference
    Barge
    Transfer
    C-Barge
    Ring   on shared lines
    Do   Not Disturb
    Privacy
    Presence
    CTI   call control
    Busy   Lamp Field
    Thanks
    Jomy

  • Upgrade CUCM Subscriber after the CUCM Publisher, but when ?

    Dear Networkers,
    Whe we do have a CUCM cluster to upgrade, i know that we should start by upgrading the publisher then upgrading the subscribers one by one.
    My question :
    I remember i read somewhere that we can start upgrading the subscriber during the upgrade of the publisher but when the publisher reaches a special step in the displayed status in the output of the OS upgrade web page... I can't remember what was that step..
    Can you please help ?
    Thanks in advance.

    Hi Haouaswajih,
    Upgrade a cluster:
    When you upgrade a cluster to Cisco Unified Communications Manager 9.0(1), begin upgrading the publisher
    node first. You can begin upgrading subsequent nodes in parallel after the publisher node reaches a specified
    point in the upgrade. The remainder of this section describes how to determine when you can begin to upgrade
    the subsequent nodes.
    During the upgrade of the publisher node, view the installation log, install_log_.log, by using
    the Software Installation/Upgrade window in Cisco Unified Communications Operating System Administration
    or the command line interface (CLI). You can begin the upgrade of the subsequent nodes after the following
    information displays in the log:
    PRODUCT_TARGET is
    PRODUCT_NAME is
    PRODUCT_VERSION is
    You can also use the CLI to search for the relevant information in the install log by following this procedure:
    Procedure
    Step 1 List the install logs; for example:
    file list install install_* date
    install_log_2008-10-01.09.41.57.log install_log_2008-10-08.12.59.29.log
    install_log_2008-10-14.09.31.06.log
    dir count = 0, file count = 3
    Step 2 Search the most recent install log for the string PRODUCT_VERSION; for example:
    file search install install_log_2008-10-14.09.31.06.log PRODUCT_VERSION
    Searching path: /var/log/install/install_log_2008-10-14.09.31.06.log
    Searching file: /var/log/install/install_log_2008-10-14.09.31.06.log
    10/14/2008 09:52:14 upgrade_os.sh|PRODUCT_VERSION is
    7.1.0.39000-97|
    Search completed
    Step 3 When the file search command finds the PRODUCT_VERSION string in the install log, you can start the
    upgrade of the subsequent nodes.
    If you want to upgrade the subsequent nodes in parallel with the publisher node, do not choose
    the Reboot to upgraded partition on either publisher node or subsequent nodes while configuring
    the upgrade options. If selected, the publisher node may complete its upgrade and reboot while
    the subsequent nodes are upgrading, which causes the upgrade of the subsequent nodes to fail.
    Caution
    When you are ready to activate the new version, you must activate the new software on the publisher node
    before activating it on all other nodes.
    Refer page 23 onwards in the below link,
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/upgrade/9_0_1/CUCM_BK_U8D523AB_00_upgrade-guide-cucm-90.pdf
    Hope this helps.
    Anand
    Please rate helpful posts !!

Maybe you are looking for