Cisco Unified Communications Manager

Testing upgrading Unified Communications Manager 6.0 to 6.1 to 7.0 to 7.0.0.39771-4 to 7.0.1.10000-28 to 7.0.1.11000-2

*The server that we are going to use to test have currently a working copy of Unified Communications Manager 6.1.1.2000-3
*The hardware that we are using is a 7816H3.
*We will install a new copy of Unified communications Manager 6.0.1.2000-3 then using the "Upgrade Retrieval Mechanism" we will try to upgrade our server to Unified Communications Manager 6.1.1.2000-13, then to 7.0.1.10000-28 bypassing (7.0.0.39771-4 file).
*I will also do a fresh installation of UC 7.0.0.39771-4 then try to apply the UC 7.0.1.10000-28 patch using the Upgrade Retrieval Mechanism.
From these test’s I have learned that while it is possible to upgrade a current installation of UC 6.0.1.2000-3 to 6.1.1.2000-13. It’s not possible to apply the UC 7.0.1.10000-28 patch using the Upgrade Retrieval Mechanism.
Also when I did a fresh Installation of UC 7.0.0.39771-4 and try to apply the UC 7.0.1.10000-28 patch using the Upgrade Retrieval Mechanism the patch didn’t applied correctly then I try to apply the patch using the Cisco Unified OS Administration but the patch didn’t apply successfully. Although the UC 7.0.1.11000-2 patch successfully was applied to the UC 7.0.0.39771-4 under the same conditions.
To clarify this issue with the UC patches I will do another test which it will consist in doing a fresh install of UC 7.0.0.39771-4 then apply the UC 7.0.1.10000-28 and then apply the UC 7.0.1.11000-2 using a web browser via the Cisco Unified OS administration.
Also what I noticed is that while I was running UC 7.0.1.11000-2 if for some reason you hard reboot the server more than once , some errors will appear during the booting process which I think the errors are related to the journal sector which it will halt the booting process, rebooting with the UC 6 System Recovery CD, swapping partitions and then once the server has succesfully restarted using the old UC version, and proceeding to login into the Unified Communications Manager and issuing the following command to revert back to the new partition (utils system switch-versions) will fix this booting error.
NOTE: Please keep in mind that this is a TEST only. I will strongly suggest you not to do this procedure in a working/operational cluster UNLESS you think it is going to be an stable environment. Furthermore I will suggest you to read the entire document before doing anything.
This test took approximately 12 hours
***********************************************************************************
Step 1
-Boot Server
-Insert DVD
The system will recognize that there is a DVD in the DRIVE
and it will ask you if you want to perform a media check.
The exact message is
******************** DVD Found *********************
A media check is recommended once before installation.
Do you wish to perform a media check?
YES or NO
****************************************************
Because I am using a brand new ucm installation DVD
and I know the media estate is good I will select NO
But If I had downloaded the UCM installation software in
that case and for my own sanity I will select YES
Step 2
Proceed with Install
The system will now give you the following message
******************************************************
Version on the Hard Drive: 6.1.1.2000-3
The version on this DVD is: 6.0.1.2000-3
Do you want to overwrite the hard drive?
YES NO
******************************************************
Note: Remember that in my case I am wiping a box that currently have Unified Communications Manager 6.1.1.2000-3 so if this is a new install for you, you may not see this message
Ok so in my case I will say yes
Step 3
A message will appear
*******************************************************
This wizard sets up the initial configuration of the platform.
Use and to navigate between text entry field and buttons, and press or to press a button.
Choose to skip the configuration until later
Chose to the end the installation
*******************************************************
-Select Proceed

Step 4
A message will appear
Apply Patch
The system will now ask you if you want to apply an upgrade patch as part of this installation?
The system installation will install the software and then it will ask you for the location of the patch

I selected YES, but if you dont want to apply an upgrade after the install you will select NO
Step 5
The install continues, because I am overwriting a hard drive with a previous installation, the system will format my drive.
Step 6
After formatting the drive, the platform installation will start
Step 7
Once the process has been completed, the DVD will eject and the server will eventually reboot.
Step 8
The following Message will appear
******************Application Pre-Install***************
Installing packages
***************************************************
The installation process will continue
Step 9
A message will appear
*****Install Upgrade Retrieval Mechanism Configuration*****
Select the desired upgrade retrieval Mechanism:
()SFTP
()FTP
(*)Local
OK BACK
****************************************************
I will insert the upgrade DVD containing XXXXXXXXXX in the drive
Using the bar key I will select Local and then OK
Step 10
A message will appear
********Install Upgrade Patch Selection Validation**********
Upgrade patch
"Local_UCSInstall_UCOS_6.1.2.1000-13.sgn.iso" was found.
Should we continue to update the system with this patch?
CONTINUE
*****************************************************
I will select Continue and enter.
Step 11
The DVD will eject after sometime of blue screen a message will appear
*************Upgrading OS*************
Unpacking /root/os.tar.gz
**************************************
Step 12
A message will appear
*********Upgrading OS*****************
Backup new OS on Partition B
**************************************

Step 13
Cisco Unified Communications manager will reboot and this time it will reboot as Unified Communications Manager 6.1.2.1000-13
Step 14
A message will appear
***********Application Pre install************

**********************************************
Step 15
A message will appear
**********Pre-existing Configuration Information*****
If you have any pre-existing configuration information
on a USB key or floppy, insert the media before continuing.
Pre existing configurations include a platformConfig.xml file
containing configuration answers previously collected by another
means and/or a DMABackupInfo.info file created by the Windows DMA
backup tool used in a Windows to Linux upgrade.
**********************************************
If you don’t have a pre-existing configuration information, continue and
you will be prompted for it.
CONTINUE
*******************************************************
Here if you are doing an upgrade from CCM 4.x to 6. you will insert the CD/DVD containing the DMA info, so all the configuration from windows will be converted to new UCM platform.
In my case I am doing a fresh install so I will not insert anything and I will select continue

Step 16
A message will appear
********Platform Installation Wizard********
This wizard sets up the initial configuration of the Platform.
Before proceeding, complete the pre-installation
tasks outlined in the the installation guide.
Choose to continue with the wizard
Choose to end the installation
PROCEED CANCEL
*********************************************
In my case I am doing a fresh install of everything so I don’t have anything to do other than get this
SERVER up and running in the network that i have configured for this test

Step 17
A message will appear
**********Apply Patch***********
Would you like to apply an upgrade patch as part of
this installation?
This option will install the software from the DVD and
the prompt you for the location of the additional
patch to apply after the system reboots.
YES NO BACK
*************************************
Well because this is a test and “technically” I am testing Why not I will insert my newly created UC 7 Upgrade DVD containing UC 7.0.1.10000.28 and see what happens
Then I selected YES
Step 18
A message will appear
**********Install Upgrade Retrieval Mechanism Configuration***
Select the desired Upgrade Retrieval Mechanism:
()SFTP
()FTP
(*)LOCAL
OK BACK
*******************************************************
I will Select local and OK
Step 19
A message will appear
*********Install Upgrade Patch Selection Validation*****
Upgrade patch
"LOCAL_UCSInstall_UCOS_7.0.1.10000-28.sgn.iso" was found.
Should we continue to update the system with this patch?
CONTINUE BACK
********************************************************
Excellent UCM was able to recognize the UC 7.0.1.10000-28 patch, so I selected Continue
Step 20
After sometime the DVD will eject and a message will appear
***********Apply patch**********
Would you like to apply an upgrade patch as part of this installation?
This option will install the software from the DVD and then prompt you for the location of the additional patch to apply after the system reboots.
YES NO Back
*******************************
I selected NO
Step 21
A message will appear
********************************************
Would you like to import data from a windows version of the Cisco Unified communications Manager?
This option allows you to import data from an existing Windows system as a data file created by the DATA Migration Assistant (DMA). It asks for information necessary to retrieve the DMA file, installs the software from the DVD and then imports the configuration into the system
YES NO BACK
***********************************************
I selected no
Step 22
A message will appear
***********Basic Install*******************
This is the "Basic" installation option. This option
installs the software version from the DVD and does
not use any imported data. It asks for configuration
information and then completes the install
CONTINUE
*********************************************
I selected Continue
Step 23
A message will appear
**********Timezone Configuration***************
Choose the correct time zone from the following list:
Select your appropriate TIMEZONE and select OK
Step 24
A message will appear
********Auto Negotiation Configuration*********
Do you want to enable automatic negociation of ethernet NIC speed and Duplex?
YES NO Back Help
**********************************************
Because this is a test box I selected YES
Step 25
A message will appear
*************MTU Configuration***************
Do you want to change the MTU size from the OS
default?
NO YES BACK HELP
********************************************
I selected NO
Step 26
A message will appear
************DHCP Configuration**************
Do you want to use Dynamic Host configuration
Protocol (DHCP) on this machine?
YES NO BACK HELP
*******************************************
I selected NO

Step 27
A message will appear
********Static Network Configuration********
Proceed to enter your appropriate network information
HOST NAME_______________
IP ADDRESS______________
IP MASK ________________
GW Address______________
******************************************
I will USE the following info
hostname : 7816H3CTILAB
IP address: 192.168.1.102
IP mask:255.255.255.0
GW address: 192.168.1.1
Then I selected ok and I got an error message
*********Error*****************
Invalid hostname 7816H3CTILAB. Must be alphanumeric or `-`. Cannot be "Localhost" or an IP address.
I proceed to change the amount of characters of the hostname to just CTICLTLAB1 by reducing it to 10
characters.. And it works.
Step 28
A message will appear
***********DNS Client Configuration***********
Do you want to enable Domain Name System (DNS) client on this machine?
YES NO BACK help
**********************************************
I selected NO, If I would have selected YES the message below will have appear, the reason I didn’t select YES is because this is a test box and if I need to add the DNS info later I can use and SSH client to do so via the UCM console.
************DNS Client Configuration********

PRIMARY DNS ________________
Secondary DNs (optional)____________
Domain _____________________
OK BACK
******************************************
Once you have entered your DNS information and selected Ok the UCM configuration
process will continue
Step 29
A message will appear
*********configure and Setup Network********
Checking Network connectivity
********************************************
Step 30
A message will appear
********Administrator Login Configuration*********
Enter the Platform administration Username and password.
Choose help for username and password guidelines.
Administrator ID _____________
Password ________________
Confirm Password_______________

OK BACK HELP
***********************************************
I proceeded to enter the requested information
Step 31
A message will appear
*******Certificate Information*********
Organization _________________-
Unit__________________________
Location______________________
State_________________________
Country_______________________
OK BACK HELP
***************************************
Please proceed to enter the information
Step 32
A message will appear
*******First Node configuration*********
Is this server the First Node in the Cluster?
YES NO BACK HELP
****************************************
I selected YES, because I will make this test server my publisher .
Step 33
A message will appear
****Network time Protocol client Configuration***
Do you want to set up external Network Time Protocol (NTP) servers (s)?
Cisco strongly recommends that you use external NTP servers to ensure that system time is kept accurate.
YES NO BACK HELP
I selected YES
Step 34
A message will appear
*****Network time protocol Client Configuration***
NTP server 1_________
NTP Server 2_________
NTP Server 3_________
NTP Server 4_________
NTP server 5_________
TEST PROCEED BACK HELP
************************************************
For testing purposes I proceeded to enter 3 NTP servers from the NTP pool project at www.pool.ntp.org
72.3.139.115
209.67.219.106
72.51.27.50
And I proceeded to select the TEST button just to make sure the NTP servers are accessible
Unified Communications Manager Proceed to test the NTP servers and we are good to go, the NTP servers are accessible now, so I proceeded to select Proceed.
Step 35
A message will appear
******Database Access Security Configuration********
Enter the system security password. This password is used to secure communications between cluster nodes.
Choose help for username and password guidelines.
Security password___________
Confirm password____________
OK BACK HELP
****************************************************
To keep it simple I proceeded to use the same password that I use for the Administrator user. Of course you can change this password for something more secure, after all this is the password that will be use by the UCM servers to communicate each other. So when you are installing a subscriber this will be the password that you will need to enter during the subscriber install, in order for the subscriber to be able to communicate with the publisher and exchange data/information
Step 36
A message will appear
**********Security Configuration ********
*****************************************
Step 37
A message will appear
***********SMTP Host Configuration*******
Do you want to configure a Simple Mail Transfer
Protocol (SMTP) host for this machine?
YES NO BACK HELP
******************************************
I selected NO
Step 38
A message will appear
************Application User Configuration*****
The application username and password are used to log into the application administrative webpage(s)/

Application user Username__________________
Application user password__________________
Confirm application user password__________
OK BACK HELP
***********************************************
Because I don’t want to keep it too simple I will use a different username this time to access UCM
via a webpage.
Step 39
A message will appear
************Platform configuration Confirmation*****
The platform Configuration is complete
Select OK to continue of Back to change the Configuration
Warning: once you select OK, you will no longer be able to modify the Platform Configuration.
OK BACK CANCEL
*****************************************************
I selected Ok
Step 40
A message will appear
**********Product licensing*****************
This message will contain the MAC address of the NIC, so please recorded in case you need it later,
Although most likely your server will have a white label that have the following info
LAN 1 ID: XXXXXXXXXX
LAN 2 ID: XXXXXXXXXX
I will suggest you to copy the mac address that this page gives you, based on my experiences and
Fellow engineers experiences, sometimes the MAC address that shows in the white label is wrong, as
Such you may encounter some issues at the moment that your are registering your product and installing the license file.
Step 41
A message will appear
********Application Post install*************
*********************************************
Step 42
The UCM console appeared but it shows.
Cisco Unified Communications Manager 6.1.2.1000-13
Will proceed to login to UCM and restart the server to see what happens
Admin : utils system restart
Step 43
The system still restarts as Cisco Unified Communications Manager 6.1.2.1000-13
To check further investigate I will issue the following commands
Admin : show version active
Active Master Version: 6.1.2.1000-13
Active Version Installed Software Options:
No Installed Software Options Found.
Admin :show version inactive
Executed command unsuccessfully
No Inactive side available
Admin :show hardware
HW Platform : 7816H3
Processors : 1
Type : Intel(R) Celeron(R) D CPU 3.20GHz
CPU Speed : 3200
Memory : 2048 Mbytes
Object ID : 1.3.6.1.4.1.9.1.900
OS Version : UCOS 3.0.0.0-60
RAID Version :
Firmware version not known
BIOS Information :
Vendor: HP
Version: W04
Release Date: 04/13/2007

RAID Details :
RAID not configured
Admin :
Admin :show tech system software
-------------------- show platform system --------------------

Software Release Version: 6.1.2.1000-13
Platform Release Version: 2.0.0.1-1
admin:
software: system versions
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05)
Java HotSpot(TM) Client VM (build 1.5.0_13-b05, mixed mode, sharing)

Tomcat "5.5.17-0"
Admin :

I then decided to login to UCM via web to look further. Indeed the system version still says 6.1.2.1000-13, We will now proceed to upgrade to UCM 7 via the Cisco Unified OS Administration page but first I will quickly configure a Route list, a Route Pattern and why not configure a Mobile voice Access DN so I also had created a Mobile-Voice-Acces _PT partition, just to see if the info will pass to UC7, if our test indeed works.
-Using the SSH console I issue the following command to make sure my 911 Route pattern is there
Output is in file cm/trace/dbl/showtechroutepatterns15745.out
Admin :show tech route patterns
-------------------- show tech routepatterns --------------------
Route Patterns
Output is in file cm/trace/dbl/showtechroutepatterns15745.out
admin:file view activelog cm/trace/dbl/showtechroutepatterns15745.out
Show tech RoutePattern output
=============================
pkid,dnorpattern,route_filter_clause,route_partition,device_name,description
"91f128aa-db34-7df7-851b-bd0217d1512b","9.911","TEST_RL","TEST RL prior upgrade"
end of the file reached
-Using a web browser, I navigated to the Cisco Unified OS Administration
I proceeded to login
-Selected the Software Upgrades TAB
-Select the Install/Upgrade TAB
-I proceeded to insert the Cisco Unified Communications Manager 7.0 and selected/enter the following information.
-Source* [DVD/CD]
Directory* \
Server*blank
I leave the rest as default
-Selected Next
The following message appear in the screen
*************************************************************
Status: Ready
Software location
Options/Upgrades* LOCAL_UCSInstall_UCOS_7.0.0.39771-4.sgn.iso
CANCEL NEXT
*************************************************************
I selected Next
The following message Appear
*************************************************************************************
Warning: To ensure the integrity of the installation file, please verify the MD5 hash value against the Cisco Systems web site
Warning: A backup is highly recommended before proceeding
File Checksum DetailsFile LOCAL_UCSInstall_UCOS_7.0.0.39771-4.sgn.iso
MD5 Hash Value -
Version InformationCurrent Version 6.1.2.1000-13
Upgrade Version 7.0.0.39771-4
()Reboot Options Reboot to upgraded partition
()Do not reboot after upgrade
- indicates required item.
*************************************************************************************
So at this point in the Reboot Options I proceeded to select “Do not reboot after upgrade” and I selected this option because I want to be able to access the console and check my active and inactive partitions
After approximately 16 to 20 minutes the DVD will eject and the installation continues…
After approximately 1 hour my screen shows the following message
**********************************************************************
Installation StatusFile LOCAL_UCSInstall_UCOS_7.0.0.39771-4.sgn.iso
Start Time Sat Sep 13 20:46:11 EDT 2008
Status Complete
**********************************************************************
To confirm couple of things I will issue the following commands via the SSH console
Admin: show active version
Executed command unsuccessfully
No valid command entered
admin: show inactive version
Using the SSH console I will restart the server
admin: utils system restart
Do you really want to restart ?
Enter (yes/no)? yes
Appliance is being Restarted ...
Warning: Restart could take up to 5 minutes.
********************************************************************
Because during the upgrade process I select it "Do not reboot after upgrade" it is most likely that the server will restart using Unified Communications Manager 6.1.2.1000-13 and I will have to console
to the server and issue the command utils system switch-version (the server will reboot
after a period of time)
Indeed the server restarted as Cisco Unified communications Manager
6.1.2.1000-13, now let me console to the server and verify a couple of things
admin:show active version

Executed command unsuccessfully
No valid command entered
admin:show inactive version
Executed command unsuccessfully
No valid command entered
-Because I want to make sure that indeed this is what’s happening using a KVM I connected to the server
and issue the same commands
admin:show version active
Active Master Version: 6.1.2.1000-13
Active Version Installed Software Options:
No installed Software Options Found.
admin:show version inactive
Inactive Master Version: 7.0.0.39771-4
Inactive Version Installed Software options:
No Installed Software Options Found.
-For some reason as you see above via the SSH console UCM was telling me that either there was nothing installed in the active or inactive partition but using the KVM UCM it shows the active and inactive partitions as suppose to, also for some reason when I was typing the command I had to type twice a character in order to post to the screen
-I went ahead and issue the utils system switch-version command to see what’s happens
After sometime the system proceeded to reboot and the following message appear while booting
Welcome to Cisco unified Communications Manager 7.0.0.39771-4
While Unified Communications Manager was booting I noticed that the iLO2 Firmware was updated.
-Once it completed the booting process in my KVM screen appear
Cisco Unified Communications Manager 7.0.0.39771-4
CTICLTLAB1 login:
-To confirm I proceeded to issue the following commands
admin:show version active
Active Master Version: 7.0.0.39771-4
Active Version Installed Software Options:
No Installed Software Options Found.
admin:show version inactive
Inactive Master Version: 6.1.2.1000-13
Inactive Version Installed Software Options:
No Installed Software Options Found.
admin:
-I proceed it to login to UCM via webpage, and sure enough this is Unified Communications Manager 7.0.0.39771-4
To check my licenses I proceeded to go to the System TAB
-Select Licensing
-Select license Unit Report
The following screen show up
*************************************************************************************
License Unit DistributionDevice License FeatureLicense Server Units Authorized Units Used Units Remaining Units Pending
CTICLTLAB1 50 0 50 0
Total Units for Feature 50 0 50 0
CCM Node License FeatureLicense Server Units Authorized Units Used Units Remaining
CTICLTLAB1 1 0 1
Total Units for Feature 1 0 1
Software License VersionLicense Server SW Version
CTICLTLAB1 6.0
*************************************************************************************
It shows 50 DLUS and one server license unit, and this is probably because i haven’t started the call
Manager services yet, let's go ahead and do that by navigating to the Cisco Unified Serviceability
-Select the tools TAB
-Select the Service Activation TAB and start the appropriate services.
Sure enough now my server license unit is now consumed, because we started the call manager Service
Remember the basic configuration I created?, well all the basic configuration that I created is now in the Unified Communications Manager 7.0.0.39771-4.
Also remember the UC7 patch that I applied earlier and it didn’t work? Well let’s go ahead an
Upgrade UC7.0.0.39771-4 with the patch UC 7.0.1.10000.28 by navigating to Cisco Unified OS Administration
-Proceed to Login
-Select Software Upgrades
-Select Install/Upgrade
-I proceeded to insert the DVD containing the UC 7.0.1.10000.28 Patch
-I was presented with a message
********************************************************************
Status: Ready
Software Location
Source* DVD/CD
Directory* \
*******************************************************************
Select NEXT
I now I am being presented with another message
Status: Ready
Software Location
Options/Upgrades* LOCAL_UCSInstall_UCOS_7.0.1.10000-28.sgn.is0
-I selected NEXT
-I now I was presented with the following message
**************************************************************************
Status Warning: To ensure the integrity of the installation file, please verify the MD5 hash value against the Cisco Systems web site
Warning: A backup is highly recommended before proceeding
File Checksum DetailsFile LOCAL_UCSInstall_UCOS_7.0.1.10000-28.sgn.iso
MD5 Hash Value -
Version InformationCurrent Version 7.0.0.39771-4
Upgrade Version 7.0.1.10000-28
(*) Reboot Options Reboot to upgraded partition
() Do not reboot after upgrade
-This time I selected the "Reboot to upgraded partition" option, because I want Unified Communications
Manager to reboot automatically after the completion of the UPGRADE.
-The upgrade process starts.
After approximately 10 minutes the DVD will eject and the upgrade process will continue 3 minutes after the status changed to :
Status: Error encountered: An unknown error occurred while access the upgrade file.
-I proceed to restart the server via web to see what will be impact.
Cisco Unified Communications Manager restarted as Cisco Unified Communications Manager
7.0.0.39771-4
-To confirm I went to the SSH console and issue the following commands
admin: show version active
Active Master Version: 7.0.0.39771-4
Active Version Installed Software Options:
No Installed Software Options Found.
admin: show version inactive
Inactive Master Version: 6.1.2.1000-13
Inactive Version Installed Software Options:
No Installed Software Options Found.
Admin :
-Indeed the patch didn’t applied successfully, to eliminate all possibilities I want to go ahead and I apply the patch again but this time I will select during the upgrade process to not to reboot after upgrade
-After about 35 minutes I was presented with the following message
**********************************************************************************
Installation Status File LOCAL_UCSInstall_UCOS_7.0.1.10000-28.sgn.iso
Start Time Sat Sep 13 23:51:42 EDT 2008
Status Error encountered: An unknown error occurred while accessing the upgrade file.
***********************************************************************************
-So at this point is either the upgrade file that we have is corrupted or simply we have an issue with our Unified Communications Manager files, basically I think that it could be an error with the way we apply the UC 7 patch initially trying to bypass the original and initial upgrade file UC 7.0.0.39771-4.
-At this point we will proceed to do a fresh install of UC 7.0.0.39771-4 and then Upgrade to 7.0.1.10000-28 using our DVD.
-I proceeded to insert the DVD in the server and restart the Server, sure enough the server recognized that it was a bootable DVD.
Step 1
A message appear
****************************DVD Found************************
A media check is recommended once before the installation.
Do you wish to perform a media check?
YES NO
*************************************************************
-I selected NO, because I know this DVD media integrity is good.
Step 2
A message appear
********* Product Deployment Selection************************
The Cisco Unified Communications product suite will be installed.
----------------------------------------------------------------
Products not supported on current hardware:
----------------------------------------------------------------
Cisco Unity Connection
Cisco Unified Communications Manager Business Edition
OK
**************************************************************
-I proceeded to select OK
Step 3
A message will appear
**************Proceed with Install******************
Versions on the hard drive: 7.0.0.39771-4
6.1.2.1000-13
The version on this DVD is : 7.0.0.39771-4
Do you want to overwrite the hard drive?
YES NO
************************************************
-Because I want to wipe my hard drive completely and do a fresh install and then apply the Patch, I selected YES

Step 4
**********Platform Installation Wizard***************
The wizard sets up the initial configuration of the platform.
Before proceeding, complete the pre-installation tasks outlined in the installation guide.
Choose to continue with the wizard
Choose to skip the configuration until later
Choose to end the installation
PROCEED SKIP CANCEL
**********************************************
-I selected Proceed
Step 5
***********Apply patch ***********************
Would you like to apply an upgrade patch as part of this installation?
This option will install the software from the DVD and then prompt you for the location of the additional patch to apply after the system reboots.
YES NO
*******************************************
-Since this is a TEST, and I want to "test" I will select YES and see if this time the patch applies correctly which I think it will unless I have a bad patch file, I could have also selected NO and then upgrade UC 7 via web but what I am looking for is for the hard drive to completely format and why not test the upgrade mechanism.
Step 6
-The DVD will eject from the drive and the server will reboot
Step 7
The server will come back up and the following message will appear
**************Application Pre Install ***********************
Installing Packages

*************************************************************
Step 8
A message will appear
***************Install Upgrade Retrieval Mechanism Configuration****
Select the desired Upgrade retrieval Mechanism:
()SFTP
()FTP
(*)LOCAL
OK CANCEL
***************************************************************
-I proceeded to insert the DVD containing the PATCH and I also selected LOCAL and then OK
Step 9
A message will appear
************Install Upgrade Patch Selection Validation*****************
Upgrade patch
"LOCAL_UCSInstall_UCOS_7.0.1.10000-28.sgn.iso" was found. Should we
continue to update the system with this patch?
CONTINUE BACK
***********************************************************************
-I selected CONTINUE
-The system will authenticate the patch file and the installation will continue
The DVD will eject from the Drive
Step 10
A message will appear
*************Apply patch*******************
Would you like to apply an upgrade patch as part of this installation?
This option will install the software from the DVD and then prompt you for the location of the additional patch to apply after the system reboots.
YES NO
*****************************************
At this point I don’t have any other patch to apply yet, so I selected NO
Step 11
A message will appear
***********Import Windows Data***************
Would you like to import data from a Windows version of the Cisco Unified Communications Manager?
this option allows you to import data from an existing windows system as a data file created by the Data Migration Assistant (DMA). It asks for information necessary to retrieve the DMA file, installs the software from the DVD and then imports the configuration into the system
YES NO
*********************************************
-I selected NO
Step 12
A message will appear
**************BASIC INSTALL********************
this is a "Basic" installation option. This option installs the software version from the DVD and does
not use any imported data. It asks for configuration information and then completes the install
CONTINUE
**********************************************
-I selected CONTINUE
Step 13

A message will appear
***********TIMEZONE CONFIGURATION***************
Choose the correct time zone from the following list:
*
*
*
*
OK BACK HELP
*************************************************
Step 14
************ Auto Negociation Configuration*******
Do you want to enable automatic negociation of ethernet NIC speed and duplex?
YES NO BACK
*********************************************
-I selected YES
Step 15
A message will appear
********************MTU Configuration**************
Do you want to change the MTU size from the OS default?
NO YES BACK
**************************************************
-I selected NO
Step 16
A message will appear

********Static Network Configuration********
Proceed to enter your appropriate network information
HOST NAME_______________
IP ADDRESS______________
IP MASK ________________
GW Address______________
OK BACK Help
*******************************************
I will USE the following info
Hostname : CTICLTLAB1
IP address: 192.168.1.102
IP mask:255.255.255.0
GW address: 192.168.1.1
-Then I selected OK
Step 17
A message will appear
***********DNS Client Configuration***********
Do you want to enable Domain Name System (DNS) client on this machine?
YES NO BACK help
**********************************************
I selected NO, If I would have selected YES the message below will have appear, the reason I didn’t select YES is because this is a test server and I may add the DNS info later using the SSH console. Remember I am “testing”
************DNS Client Configuration********
PRIMARY DNS ________________
Secondary DNs (optional)____________
Domain _____________________
OK BACK
****************************************
-Once you have entered your DNS information and selected Ok the UCM configuration process will continue
Step 18
A message will appear
********Administrator Login Configuration*********
Enter the Platform administration Username and password.
Choose help for username and password guidelines.
Administrator ID _____________
Password ________________
Confirm Password_______________
OK BACK HELP
***********************************************
-This is the credentials that you will use to access the SSH Console and the Cisco Unified OS Administration from a web browser.
Step 19
A message will appear
*******Certificate Information*********
Organization _________________-
Unit__________________________
Location______________________
State_________________________
Country_______________________
OK BACK HELP
*********************************
-Please proceed to enter the information
Step 20
A message will appear
*******First Node configuration*********
Is this server the First Node in the Cluster?
YES NO BACK HELP
***********************************
I selected YES, because I will make this test server my publisher
Step 21
A message will appear
****Network time Protocol client Configuration***
Do you want to set up external Network Time Protocol (NTP) servers (s)?
Cisco strongly recommends that you use external NTP servers to ensure that system time is kept accurate.
YES NO BACK HELP
******************************************
I selected YES
Step 22
A message will appear
*****Network time protocol Client Configuration***
NTP server 1_________
NTP Server 2_________
NTP Server 3_________
NTP Server 4_________
NTP server 5_________
TEST PROCEED BACK HELP
*******************************************
-For testing purposes I proceeded to enter 3 NTP servers from the NTP pool project at www.pool.ntp.org
72.3.139.115
209.67.219.106
72.51.27.50
-And I proceeded to select the TEST button just to make sure the NTP servers are accessible
Unified Communications Manager Proceed to test the NTP servers and we are good to go, the NTP servers are accessible now, so I proceeded to select Proceed.
Step 23
A message will appear
******Database Access Security Configuration********
Enter the system security password. This password is used to secure communication between cluster nodes.
Choose help for username and password guidelines.
Security password___________
Confirm password____________
OK BACK HELP
*************************************************
-To keep it simple I proceeded it to use the same password that I use for the Administrator user. Of course you can change this password for something more secure, after all this is the password that will be use by the UCM servers to communicate each other. So when you are installing a subscriber this will be the password that you will need to enter during the subscriber install, in order for the subscriber to be able to communicate with the publisher and exchange data/information
Step 24
A message will appear
***********SMTP Host Configuration*******
Do you want to configure a Simple Mail Transfer Protocol (SMTP) host for this machine?
YES NO BACK HELP
******************************************
-I selected NO
Step 25
A message will appear
************Application User Configuration*****
The application username and password are used to log into the application administrative webpage(s)/
Application user Username__________________-
Application user password__________________
Confirm application user password__________
OK BACK HELP
********************************************
-Because I don’t want to keep it too simple I will use a different username this time to access UCM
via a web browser
Step 26
A message will appear
************Platform configuration Confirmation*****
The platform Configuration is complete
Select OK to continue of Back to change the Configuration
Warning: once you select OK, you will no longer be able to modify the Platform Configuration.
OK BACK CANCEL
***********************************************
-I selected Ok

Step 27
A message will appear
**********Product licensing*****************
This message will contain the MAC address of the NIC, please recorded in case you need it later,
Although most likely your server will have a white label that have the following info, see below
LAN 1 ID: XXXXXXXXXX
LAN 2 ID: XXXXXXXXXX
-I will suggest you to copy the MAC address that this page gives you, based on my experiences and
Fellow engineers experiences, sometimes the MAC address that shows in the white label is wrong, as
Such you may encounter some issues at the moment or registering your product and installing the license.
-The installation process will continue
Step 28
-Once the installation completed the server rebooted, but it rebooted under Cisco Unified Communications Manager 7.0.0.39771-4, so apparently once again it didn’t took the upgrade patch.
-I proceeded to try to upgrade the server once again via a web browser this time, since we have a complete fresh install, this will isolate the possible issue with the "bypass upgrade" that we did.
-Again the upgrade patch 7.0.1.10000-28 failed!!
A message appear
************************************************************************
Installation StatusFile LOCAL_UCSInstall_UCOS_7.0.1.10000-28.sgn.iso
Start Time Sun Sep 14 02:15:51 EDT 2008
Status Error encountered: An unknown error occurred while accessing the upgrade file.
*************************************************************************
09/14/2008 02:32:34 upgrade_manager.sh|file=./HP/firmware/libcpqimgr.so, dir=./HP/firmware, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./HP/firmware|
09/14/2008 02:32:34 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./HP/firmware/libcpqimgr.so" to "/common/rpm-archive/7.0.1.10000-28/vendor/./HP/firmware"|
09/14/2008 02:32:34 upgrade_manager.sh|file=./HP/firmware/libhwmim3.so, dir=./HP/firmware, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./HP/firmware|
09/14/2008 02:32:34 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./HP/firmware/libhwmim3.so" to "/common/rpm-archive/7.0.1.10000-28/vendor/./HP/firmware"|
09/14/2008 02:32:35 upgrade_manager.sh|file=./HP/firmware/libossingleton.so, dir=./HP/firmware, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./HP/firmware|
09/14/2008 02:32:35 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./HP/firmware/libossingleton.so" to "/common/rpm-archive/7.0.1.10000-28/vendor/./HP/firmware"|
09/14/2008 02:32:35 upgrade_manager.sh|file=./HP/tape/add_scsi_device, dir=./HP/tape, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./HP/tape|
09/14/2008 02:32:35 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./HP/tape/add_scsi_device" to "/common/rpm-archive/7.0.1.10000-28/vendor/./HP/tape"|
09/14/2008 02:32:35 upgrade_manager.sh|file=./HWTABLE.data, dir=., dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/.|
09/14/2008 02:32:35 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./HWTABLE.data" to "/common/rpm-archive/7.0.1.10000-28/vendor/."|
09/14/2008 02:32:35 upgrade_manager.sh|file=./HWTABLE.data.old, dir=., dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/.|
09/14/2008 02:32:35 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./HWTABLE.data.old" to "/common/rpm-archive/7.0.1.10000-28/vendor/."|
09/14/2008 02:32:35 upgrade_manager.sh|file=./misc/bin/abort.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:35 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/abort.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/bios_raid_flash.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/bios_raid_flash.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/diskcheck, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/diskcheck" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/done.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/done.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/done-noReboot.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/done-noReboot.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/ethtool, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/ethtool" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/getFirmwareInfo.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/getFirmwareInfo.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/get_primary_interface_name.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/get_primary_interface_name.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/HP-IDE.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/HP-IDE.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/HP-SAS.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/HP-SAS.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/HP-SCSI.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/HP-SCSI.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/hwcheck, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/hwcheck" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/hwdetect, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/hwdetect" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/hw_disk_check.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/hw_disk_check.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/hw_raiddetect.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/hw_raiddetect.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/hw_recovery.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/hw_recovery.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/hw_setup.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/hw_setup.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/hw_vendor_func.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/hw_vendor_func.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/IBM-ATA.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/IBM-ATA.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/IBM-SAS.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/IBM-SAS.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/IBM-SCSI.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/IBM-SCSI.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/iLO_flash.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/iLO_flash.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/mfg_bios_reset.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/mfg_bios_reset.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/SATA.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/SATA.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/sd_hwdetect, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/sd_hwdetect" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/sd_VMwaredetect, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/sd_VMwaredetect" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/unsupported.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:36 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/unsupported.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:36 upgrade_manager.sh|file=./misc/bin/warn.sh, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:37 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/warn.sh" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:37 upgrade_manager.sh|file=./misc/bin/xml, dir=./misc/bin, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin|
09/14/2008 02:32:37 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/bin/xml" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/bin"|
09/14/2008 02:32:37 upgrade_manager.sh|file=./misc/data/Catalogue.xml, dir=./misc/data, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/data|
09/14/2008 02:32:37 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/data/Catalogue.xml" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/data"|
09/14/2008 02:32:37 upgrade_manager.sh|file=./misc/data/InstallMenuHelp.txt, dir=./misc/data, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/data|
09/14/2008 02:32:37 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/data/InstallMenuHelp.txt" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/data"|
09/14/2008 02:32:37 upgrade_manager.sh|file=./misc/data/MainMenuHelp.txt, dir=./misc/data, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/data|
09/14/2008 02:32:37 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/data/MainMenuHelp.txt" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/data"|
09/14/2008 02:32:37 upgrade_manager.sh|file=./misc/data/raidcmd.conf, dir=./misc/data, dest_dir=/common/rpm-archive/7.0.1.10000-28/vendor/./misc/data|
09/14/2008 02:32:37 upgrade_manager.sh|Copying "/mnt/source/./Cisco/vendor/./misc/data/raidcmd.conf" to "/common/rpm-archive/7.0.1.10000-28/vendor/./misc/data"|
09/14/2008 02:32:37 upgrade_manager.sh|Copying symbolic link files|
09/14/2008 02:32:37 upgrade_manager.sh|Cleanup mounted DVD or ISO|
09/14/2008 02:32:37 upgrade_manager.sh|Found mount point, /mnt/source, source filesystem /dev/hda|
09/14/2008 02:32:37 upgrade_manager.sh|Unmount /mnt/source|
09/14/2008 02:32:38 upgrade_manager.sh|Ejecting DVD (/dev/hda)|
09/14/2008 02:32:42 upgrade_manager.sh|Checking free space for the upgrade|
09/14/2008 02:32:42 upgrade_manager.sh|Free space check complete|
09/14/2008 02:32:42 upgrade_manager.sh|Upgrading platform|
09/14/2008 02:32:42 upgrade_manager.sh|/common/rpm-archive/7.0.1.10000-28/base_scripts/upgrade_os.sh|
09/14/2008 02:32:42 upgrade_manager.sh|-r-xr-xr-x 1 root root 83620 Sep 14 02:16 /common/rpm-archive/7.0.1.10000-28/base_scripts/upgrade_os.sh|
09/14/2008 02:32:42 upgrade_manager.sh|Invoking OS upgrade script|
09/14/2008 02:32:42 upgrade_manager.sh|/common/rpm-archive/7.0.1.10000-28/base_scripts/upgrade_os.sh basepath=/common/rpm-archive/7.0.1.10000-28|
09/14/2008 02:32:42 upgrade_os.sh|(CAPTURE) Parse argument basepath=/common/rpm-archive/7.0.1.10000-28|
09/14/2008 02:32:42 upgrade_os.sh|(CAPTURE) Initialize logging|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/check_root_cron_job.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/configure_core_and_syslogd.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/create_jdk_links.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/disable_ntp_from_dhcp.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/disable_services.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/fix_issue.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/initialize_logging.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/install_master_rpm.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/install_platform_prefs.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/ipmi_service.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/net-snmp_service.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/nscd_service.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/product_info.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/relocate_java.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/setup_java_api.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/setup_root_access.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/setup_services.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/swap_nic_if.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/TEMPLATE.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/temp_workaround.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/update_install_conf.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/update_iptables.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/update_rc_sysinit.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Calling "source /common/rpm-archive/7.0.1.10000-28/install/setup/utils.sh"|
09/14/2008 02:32:42 upgrade_os.sh|Upgrade OS RTMTStart|
09/14/2008 02:32:42 upgrade_os.sh|Upgrade OS starting|
09/14/2008 02:32:42 upgrade_os.sh|Initialize internal data|
09/14/2008 02:32:42 upgrade_os.sh|Initialize install.conf variable|
09/14/2008 02:32:42 upgrade_os.sh|/common/rpm-archive/7.0.1.10000-28/install.conf does not exist|
09/14/2008 02:32:42 upgrade_manager.sh|Platform upgrade failed|
09/14/2008 02:32:42 upgrade_install.sh|Cleaning up download...|
09/14/2008 02:32:42 upgrade_install.sh|Removing /common/download/7.0.1.10000-28|
09/14/2008 02:32:42 upgrade_install.sh|Cleaning up rpm_archive...|
09/14/2008 02:32:42 upgrade_install.sh|Removing /common/rpm-archive/7.0.1.10000-28|
09/14/2008 02:32:46 upgrade_install.sh|CSA Status = 0|
09/14/2008 02:32:46 upgrade_install.sh|/etc/init.d/ciscosec start|

-To eliminate the questions about "why did you use the apply patch mechanism" we will Proceed to upgrade UC 7 to a later release UC 7.0.1.11000-2.
To do this we will navigate to Cisco Unified OS Administration menu
-Select software upgrades
-Select Install/Upgrade
-Insert the DVD containing the UC 7.0.1.11000-2 patch
-Select Source* DVD/CD
-Enter "\" for the Directory field
-Select Next
A message will appear
****************************************************************
Status: Ready
Software Location
Options/Upgrades* LOCAL_UCSInstall_UCOS_7.0.1.11000-2.sgn.iso
****************************************************************
-Select Next
A message appears
****************************************************************
Status Warning: To ensure the integrity of the installation file, please verify the MD5 hash value against the Cisco Systems web site
Warning: A backup is highly recommended before proceeding
File Checksum DetailsFile LOCAL_UCSInstall_UCOS_7.0.1.11000-2.sgn.iso
MD5 Hash Value -
Version InformationCurrent Version 7.0.0.39771-4
Upgrade Version 7.0.1.11000-2
() Reboot Options Reboot to upgraded partition
(*) Do not reboot after upgrade
CANCEL NEXT

*************************************************************************************

-I will select the "Do not reboot after upgrade" option and click NEXT -After about an hour and 10 minutes the Upgrade process completed and a message appear
********************************************************************
Installation StatusFile LOCAL_UCSInstall_UCOS_7.0.1.11000-2.sgn.iso
Start Time Sun Sep 14 12:03:59 EDT 2008
Status Complete
********************************************************************
-To confirm the upgrade, I use my SSH client to connect to the Unified Communications
Manager Console and issue the following commands.
admin: show version active
Active Master Version: 7.0.0.39771-4
Active Version Installed Software Options:
No Installed Software Options Found.
admin:show version inactive
Inactive Master Version: 7.0.1.11000-2
Inactive Version Installed Software Options:
No Installed Software Options Found.
-Apparently the new patch have successfully applied to Unified Communications Manager.
Now we still need to tell Unified Communications Manager to reboot using the new
Release, because when we started the upgrade process we told Unified Communications
Manager not to reboot after the upgrade has completed, to do this I will use my SSH client to the
Unified Communications Manager Console and issue the following commands
Admin :utils system switch-version
Active Master Version: 7.0.0.39771-4
Inactive Master Version: 7.0.1.11000-2
-If you are switching to an earlier release, you must run:
utils dbreplication reset all
from the publisher after all the nodes are switched over.
Do you really want to switch between versions ?
Enter (yes/no)? yes
Switching Version and Restarting the Appliance ...
Switch version duration can vary depending on the database size and platform configuration. Please continue to monitor the switchover process from here.
Waiting ..............................................................
Broadcast message from root (Sun Sep 14 13:20:08 2008):
The system is going down for reboot NOW!
Operation succeeded
RESTART NOW!

-The server rebooted and the following message appeared
Welcome to Unified Communications Manager 7.0.1.11000-2
To verify that the patch is indeed running in our server I issue the following commands via an SSH client to the Console.
admin:show version active
Active Master Version: 7.0.1.11000-2
Active Version Installed Software Options:
No Installed Software Options Found.
admin:show version inactive
Inactive Master Version: 7.0.0.39771-4
Inactive Version Installed Software Options:
No Installed Software Options Found.
-I decided to check the License unit report to see what we have available and the following message appeared.
License Unit DistributionPhone License FeatureLicense Server Units Authorized Units Used Units Remaining Units Pending
CTICLTLAB 50 0 50 0
Total Units for Feature 50 0 50 0
CCM Node License FeatureLicense Server Units Authorized Units Used Units Remaining
CTICLTLAB 1 0 1
Total Units for Feature 1 0 1
Software License VersionLicense Server SW Version
CTICLTLAB 7.0
/Cesar Fiestas/

Cesar Fiestas
Network Engineer

Mobile Voice Access Using a Hairpinning Configuration

PSTN - GW < MGCP --> CUCM
<-- H.323 -->
*The Unified Communications Manager Version used in this document was 6.1.2.1000-13
*A Publisher and a Subscriber servers were used in this configuration
*The voice gateway used was a Cisco 2821 with the following hardware
2 Gigabit Ethernet Interfaces
48 Serial interfaces
4 Channelized T1/PRI ports
4 Voice FXO Interfaces
4 Voice FXS interfaces
*The IOS version used in our gateway was 12.4(3f)
-For the following example we will using 5311 as our incoming DID from the PSTN (4 digits)
-Our Mobile voice access number will be 3511
-The gateway used in this example was only configured as an MGCP gateway on our Unified Communications Manager, this gateway was also used to interconnect a ROLM 9755 using a CAS T1 connection.
It is assumed that you have already configured an RDP profile along with an Remote Destination Number as well the necessary settings have been applied to the UCM test user in CallManager.

Step 1.
Go to the UCM administration page
-Select the System TAB
-Select the Service parameters TAB
-For the server field, select the hostname/ip address of the publisher
-For the service field, select Cisco Callamanager
-Under Clusterwide Parameters (System-Mobility)
-Set the "Enable Enterprise Feature Access" parameter to True
-Set the "Enable Mobile Voice Access" parameter to True
-Proceed to Enter the Mobile Voice Access number that you are going to use in our case will be 3511
-Set the "Matching Caller ID with Remote Destination" parameter to "complete match" (by selecting this parameter the gateway will look for a "complete match" of digits coming from the PSTN and it will decide if is a complete match of an existing Destination Number then the user will be prompted for it's CCM user PIN number, if is not a complete match then the user will be prompted to enter its Remote Destination Number followed by the pound sign.
-In the other hand if you set the "Matching Caller ID with Remote Destination" parameter to "Partial Match" then the gateway is suppose to match the number of digits that you decide against an existing Destination number but will ONLY WORK WITH A DEDICATED H.323 GATEWAY and it will not work using a hairpinning set up which is our case.
Note: When setting the "Matching Caller ID with Remote Destination" parameter to "Partial Match" in this setup (a hairpinning set up) the Remote Destination user calling from a device that match a remote destination number will experience a silence when dialing our MVA DID
-Click save.
Step 2
-Go to the Media Resources TAB
-Select the Mobile Voice Access TAB
-On the Mobile Voice Access Directory Number field enter 3511
-On the Mobile voice Access Partition select a partition that is an accessible partition
-Proceed to select the desire Locale.
Step 3
-Telnet or SSH to the gateway that you are going to use.
-Under config mode proceed to enter the following command
!
Voice service voip
Allow-connections h323 to h323
!
Voice class h323 1
H225 timeout tcp establish 3
!
Application
Service cmm http://ip address of your publisher:8080/ccmivr/pages/IVRMainpage.vxml
!
Step 4
-To verify that the vxml script along with the correct english locale was successfully loaded into our gateway issue the following commands
Yourgateway#sh call appl voic cmm
A sign that the vxml script and our English locate is properly configured and loaded will be

*if you are seeing the following code

Check the cmm url characters under application, if your url is incorrect proceed to make the necessary changes with the correct url also, visit the UCM administration page, select the Media Resources TAB , select Mobile Voice Access and click save, this will push out the vxml script to the voice gateway, you will also need to reboot your gateway, in order for the script to show correctly in your Voice Gateway.
Step 5
We will now proceed to create our Dial-Peers
!
dial-peer voice 5311 voip
service cmm
session target ipv4:ip address of the publisher
incoming called-number 5311 <------our incoming DID from the PSTN
codec g711ulaw
!
dial-peer voice 3511 voip
preference 1
destination-pattern 3511 <------our Mobile Voice Access DN
voice-class h323 1
session target ipv4:ip address of the publisher
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 3512 voip
preference 2
destination-pattern 3511 <------our Mobile Voice Access DN
voice-class h323 1
session target ipv4:ip address of the subscriber
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 5312 voip
service cmm
session target ipv4:ip address of the subscriber
incoming called-number 5311 <------our incoming DID from the PSTN
codec g711ulaw
!
Step 6
We will now proceed to create our h323 gateway in our UCM.
-Go to the UCM Administration page
-Select the Device TAB
-Select Gateway
-Select Add New
-For our gateway Type parameter select H.323 Gateway, click Next

Enter the MGCP gateway ip address for the Device Name* parameter
-Proceed to the Select the desire Device pool
-Proceed to select the Correct Media Resource Group List, in my case I use
-Proceed to select the appropriate Location
-Proceed to check the Media Termination Point Required* field.
-Proceed to select the appropriate parameters for the Call routing information - Inbound Calls fields.
-For testing and for this example I am using the following parameters
Calling Search Space Local-CSS
AAR Calling Search Space Local-CSS
-Select Save.
Step 7
-For this example I will be using a Route Group Called "RG-Local" which will contain our H323 gateway IP address .
-For this example I have created a Route List called "RL_MVA_Devices" which have the RG-Local selected as a Route Group.
Step 8
-We will now proceed to create a route pattern that matches our inbound DID from the PSTN.
-For the route pattern* field we will enter our inbound DID number which for this document is 5311
-Proceed to select the appropriate route partition, for this example I have selected an open/default partition
-For the Gateway/Route List* Field we will select "RL_MVA_Devices"
-Route this pattern
-Call Clasification* "OffNet"
-Provide Outside Dial Tone
-Select Save.
Step 9
Finally we will need to add our Mobile-Voice-Access_RP partition to the Calling Search Space that we use in our H323 gateway
-Go to the UCM Administration page
-Go to the Call Routing Tab
-Go to the Class of Control Tab
-Select Calling Search Space
-Look for the Calling Search Space that you use for your H.323 gateway, in our case I use "Local-CSS"
-Proceed to add the appropriate Mobile Voice Access Partition to the selected partitions for the "Local-CSS", in my case I will add the Mobile-Voice-Access-RP partition and I will put it on the 3rd level.
First my 911_PT
Second my Internal_PT
Third it will be our Mobile-Voice-Access_RP partition
-Click save.
At this point you should be able to dial the DID used to access the MVA, depending on your call manager service parameters configured, Unified Communications Manager /MVA IVR will answer the call and you will be prompted for enter your Remote Destination number followed by the pound sign, then you will be prompted to enter your PIN, once authenticated you will be able to start using the MVA feature at which point you can start dialing as if you were using an internal IP Phone.
While you are logged into MVA and during a call you can use the following default dtmf codes to.
Put a call in hold *81
Put a call in an exclusive hold *82
To resume a call *83
To transfer a call *84
To conference a party *85
*************************************************************************************
Notes: You can Multiple DID's and Gateways for MVA, what you will need to do is for each DID/ GW pair, create a route pattern matching the did and route that call to its corresponding gateway, each gateway configuration will be similar to the one we configured. The incoming called-number statement has to match the DID local to that Site. The second dial-peer which matches destination-pattern XXXX will be same on all routers.
I have successfully reproduced the same configuration on a 3825 Voice Gateway located in Europe using an E1 with framing NO-CRC4, under mgcp conditions, with IOS version 12.4(11)xw5
For troubleshooting you may use
CCM SDI and SDL traces, MVA traces
Debug isdn q931, debug voice ccapi inout, debug voice application vxml application, debug voice application vxml all
For more information please the following documents
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmfeat/fsmobmgr.pdf
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmfeat/fsmobmgr.html#wp1144476

/Cesar Fiestas/

Cesar Fiestas
Network Engineer

The following notes were taken from my personal field notes.

*Upgrade time from the time you insert the DVD containing the correct ios files: 1hr 15minutes to 1hr 20minutes (per server)

*ISO file url link:

http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=6.1(2)&mdfid=281023410&sftType=Unified+Communications+Manager+Updates&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unified+Communications+Manager+Version+6.1&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=Y&imst=N&lr=Y

*The following notes were created using a vmware machine as well a cluster of 2 unified communications servers with version 6.0(1).

*This upgrade notes correspond to an upgrade conducted while UCM was in operation/production

*Downtime : Between 5 to 10minutes depending on your UCM hardware configuration.

*This upgrade notes correspond to an upgrade conducted on a cluster containing multiple locales.

Step 1.

-Adquire a blank DVD

Step 2.

-Create a folder in your computer.

For example (Upgrade-ucm), this is the folder that you will use to save the 2 files that you are going to download from cisco.com

Step 3

-Visit the above Cisco url in order to download the proper files and save them into the appropriate folder in your pc.

UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part1of2

UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part2of2

Step 4

-Once you have succesfully downloaded the 2 files needed to upgrade UCM proceed to the next step.

Step 5

-Go to your computer and open CMD

In CMD navigate to the folder containing the 2 upgrade files

Step 6

-Once in the folder enter the following command

COPY /
B UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part1of2+UCSInstall_UCOS_6.1.2.1000-13.s
gn.iso_part2of2 UCSInstall_UCOS_6.1.2.1000-13.sgn.iso

Once the windows task has been completed, your cmd screen will look something like this

C:\Documents and Settings\Cesar Fiestas\My Documents\Software\Upgrade-ucm>COPY /
B UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part1of2+UCSInstall_UCOS_6.1.2.1000-13.s
gn.iso_part2of2 UCSInstall_UCOS_6.1.2.1000-13.sgn.iso
UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part1of2
UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part2of2
1 file(s) copied.

C:\Documents and Settings\Cesar Fiestas\My Documents\Software\Upgrade-ucm>

Now please proceed to the next step

Step 7

-Procced to write the image to the DVD

The image file name should be UCSInstall_UCOS_6.1.2.1000-13.sgn and it should be located in the same folder that contains the 2 files that you downloaded from cisco.com

I used ImgBurn and it work great.

Step 8

-At this point we are ready to upgrade our Cisco Unified Communications Manager Servers. Of coure I highly recommend you to back up your UCM configurations first.

We will start first with our Publisher Server.

Please visit the Cisco Unified CM Administration page of the publisher.

Navigate to the Cisco Unifed OS Administration

-Proceed to login

-Select the Software Upgrade Tab

-Select the Install/Upgrade Tab

-Insert DVD on the publisher.

-Under Software location select DVD

-Under Directory Enter the path location of the our ISO file which in our case should be

/UCSInstall_UCOS_6.1.2.1000-13.sgn.iso

-Select Next

-Select Next

-In this screen you will have the option to either select to "auto reboot after the upgrade is complete" or "not to reboot the server after the upgrade process has been complete".

-In our case we wanted to minimize our downtime window as well we had an outage window of approx 15 minutes. Meaning that when the upgrade process was running in both servers while our UCM cluster was operational all we had to do once the upgrade proccess was completed succesfully was only to reboot our UCM servers accordinally.

-If you choose to auto reboot after the upgrade process was completed then the servers will reboot after the process is completed

-After aproximately 15 to 20 minutes the DVD will eject automatically(although the upgrade process will continue) in which time you can proceed to use the DVD to start the upgrade process in your Subscriber.

Step 9

-UCM will print a message on your screen stating that the upgrade process status is now complete.

Step 10

-SSH to the publisher, login and enter the following command

admin: show version active

this command will show you the current active version running in your UCM

admin:show version inactive

this command will show you the version of UCM running in the inactive partition

which now that the upgrade process has been completed it should be

Inactive Master Version: 6.1.2.1000-13

After that you have indeed verified the active and inactive versions of UCM procceed to the next step.

Step 11

-In my case I had a cluster of 2 UCM servers a PUB and a SUB

To minimize risks I waited for the SUB upgrade process to finish. Once the SUB upgrade process was completed I SSH to the Sub and verify the versions using the same commmands.

I then proceeded to connect my KVM to the Sub server and I unplug the network cable.

Step 12

-On the Pub Using the SSH console I proceeded to issue the following command

admin :utils system switch-version

enter yes

-It will take approx 3 to 6 minutes for the Pub Server to auto restart, The pub server should now boot using the new version.

Step 13

-Once the Publisher server has fully complete the Boot process, Using a KVM that was plugged to the Sub server I procceeded to enter the following command.

admin:utils system switch-version

This command will have the same effect as on our Publisher server.

The subcriber server should now boot using the new Cisco Unified Communications version.

/Cesar Fiestas/

Cesar Fiestas
Network Engineer