This is just notes to myself as after downloading the upgrade files for CUCM or Unity or anything else…we all need to follow the same process of combining them and then verifiying the hash value.

Download FCIV.

Download the files as required:

UCS_Install_UCOS_7.1.3.32900-4.sgn.iso_part1of2

UCS_Install_UCOS_7.1.3.32900-4.sgn.iso_part2of2

Run the following command to combine these files into one .iso file

COPY /B C:\UCS_Install_UCOS_7.1.3.32900-4.sgn.iso_part1of2+C:\UCS_Install_UCOS_7.1.3.32900-4.sgn.iso_part2of2 C:\UCSInstall_UCOS_7.1.3.32900-4.sgn.iso

UCSInstall_UCOS_7.1.3.32900-4.sgn.iso

Use a checksum generator to confirm that the MD5 checksum of the reunited file matches the following checksum:

d450666dafbc8f01c111ed0158f748fb

If the values do not match, the reunited file is damaged.

C:\>cd fciv

C:\FCIV>fciv.exe c:\UCSInstall_UCOS_7.1.3.32900-4.sgn.iso
//
// File Checksum Integrity Verifier version 2.05.
//
d450666dafbc8f01c111ed0158f748fb c:\ucsinstall_ucos_7.1.3.32900-4.sgn.iso

C:\FCIV>

Note: Make sure if you are writing it over a CD/DVD then it should be copied as Data and don’t expand it as an image. The file on the CD/DVD should be a .iso file as Call manager only looks for this file.

Now you can run the upgrade process either from OS Admin or CLI. I prefer CLI but any method can be used.

Disable throttle to speed up the process, Throttling prevents call processing degradation during the upgrade but may cause the upgrade to take longer. Throttling gets enabled by default and is necessary if you perform the upgrade during normal business hours.

Upgrade Process from CLI:

First of all disable ios throttle by using command utils iothrottle disable. If it’s not disabled at start, you will be asked during the upgrade as well where you may or may not disable it.

admin:show version active
Active Master Version: 7.1.2.20000-2

Active Version Installed Software Options:
uc-locale-en_GB-7.1.2.0-139.cop
admin:

admin:utils system
utils system boot*
utils system restart
utils system shutdown
utils system switch-version
utils system upgrade*

admin:utils system upg
admin:utils system upgrade ini
admin:utils system upgrade initiate

Warning: Do not close this window without first exiting the upgrade command.

To preserve system stability during upgrades, the system throttles the upgrade process, which may take considerably longer to complete.  If you are performing this upgrade during a maintenance window and want to speed up the upgrade, you can disable throttling.  Additional information is in the Special Upgrade Information section of the release notes.

Would you like to disable I/O throttling (yes/no): yes

Source:

1) Remote Filesystem
2) DVD/CD
q) quit

Please select an option (1 – 2 or “q” ): 1
Directory: \
Server: 10.9.1.3
User Name: cisco
Password: *****
Protocol:

1) sftp
2) ftp
q) quit

Please select an option (1 – 2 or “q” ): 1
Checking for valid upgrades.  Please wait…

Available options and upgrades in “10.9.1.3:\”:

1) UCSInstall_UCOS_7.1.3.32900-4.sgn.iso
q) quit

Please select an option (1 – 1 or “q” ): 1
Accessing the file.  Please wait…

[KDownloaded 2 MB. [KDownloaded 5 MB. [KDownloaded 8 MB. [KDownloaded 11 MB.
[KDownloaded 15 MB. [KDownloaded 18 MB.[KDownloaded 21 MB.[KDownloaded 24 MB.
[KDownloaded 27 MB.[KDownloaded 31 MB.[KDownloaded 34 MB.[KDownloaded 37 MB.
[KDownloaded 40 MB.[KDownloaded 43 MB.[KDownloaded 45 MB.[KDownloaded 48 MB.

.

.

KDownloaded 3206 MB.[KDownloaded 3209 MB.[KDownloaded 3211 MB.[KDownloaded 3214 MB.
[KDownloaded 3216 MB.[KDownloaded 3219 MB.[KDownloaded 3222 MB.[KDownloaded 3225 MB.
[KDownloaded 3227 MB.[KDownloaded 3230 MB.[KDownloaded 3233 MB.[KDownloaded 3236 MB.

Checksumming the file…

KDownloaded 3236 MB.File validated.

A system reboot is required when the upgrade process completes or is canceled.  This will ensure services affected by the upgrade process are functioning properly.

Downloaded: UCSInstall_UCOS_7.1.3.32900-4.sgn.iso
File version: 7.1.3.32900-4
File checksum: d4:50:66:6d:af:bc:8f:01:c1:11:ed:01:58:f7:48:fb

Automatically switch versions if the upgrade is successful (yes/no): no

Start installation (yes/no): yes
The upgrade log is install_log_2010-08-26.10.41.10.log
Upgrading the system.  Please wait…
08/26/2010 10:41:10 file_list.sh|Starting file_list.sh|<LVL::Info>
08/26/2010 10:41:10 file_list.sh|Parse argument method=sftp|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Parse argument source_dir=\|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Parse argument dest_file=/var/log/install/downloaded_versions|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Parse argument remote_host=10.9.1.3|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Parse argument user_name=cisco|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Calling SFTP command with metering off|<LVL::Debug>
08/26/2010 10:41:11 file_list.sh|SFTP command complete (0)|<LVL::Debug>
08/26/2010 10:41:11 file_list.sh|List file (pre-filtered):|<LVL::Debug>
08/26/2010 10:41:11 file_list.sh|(CAPTURE) UCSInstall_UCOS_7.1.3.32900-4.sgn.iso|<LVL::Debug>

.

.

08/26/2010 12:18:22 upgrade_install.sh|CSA Status = 0|<LVL::Debug>
08/26/2010 12:18:22 upgrade_install.sh|/etc/init.d/ciscosec start|<LVL::Info>
08/26/2010 12:18:24 upgrade_install.sh|(CAPTURE) Starting ciscosec:  [  OK  ]|<LVL::Debug>
08/26/2010 12:18:24 upgrade_install.sh|IOWAIT monitor stopped|<LVL::Info>
08/26/2010 12:18:24 upgrade_install.sh|0|<LVL::Debug>
08/26/2010 12:18:24 upgrade_install.sh|Upgrade Complete — (0)|<LVL::Info>

Successfully installed UCSInstall_UCOS_7.1.3.32900-4.sgn.iso

The system upgrade was successful.  Please switch versions to activate the upgrade or reboot the system to ensure services affected by the upgrade process are functioning properly.

admin:

admin:

admin:utils system swi
admin:utils system switch-version

Active Master Version: 7.1.2.20000-2

Inactive Master Version: 7.1.3.32900-4

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 (Thu Aug 26 12:30:09 2010):

The system is going down for reboot NOW!

.

Operation succeeded

RESTART NOW!
admin:

After this restart the server@

admin: utils system restart

Once it come  back up, check the services

admin:utils service list

{ The box I was upgrading was a Subscriber so I had to make sure if replication is all f ine }

Pub:

admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2010_08_26_15_38_33.out

SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
———————————————————————–
g_darcuc_ccm7_1_3_32900_4    2 Active   Local           0
g_goscuc_ccm7_1_3_32900_4    3 Active   Connected       0 Aug 26 15:34:16

————————————————-

No Errors or Mismatches found.
Replication status is good on all available servers.

admin:
admin:
admin:show perf query class “Number of Replicates Created and State of Replication”
==>query class :

– Perf class (Number of Replicates Created and State of Replication) has instances and values:
ReplicateCount  -> Number of Replicates Created   = 427
ReplicateCount  -> Replicate_State                = 2

Sub:

admin:utils dbreplication status

——————– utils dbreplication status ——————–

Replication status check is now running in background.
Use command ‘utils dbreplication runtimestate’ to check its progress

The final output will be in file cm/trace/dbl/sdi/ReplicationStatus.2010_08_26_15_39_17.out

Please use “file view activelog cm/trace/dbl/sdi/ReplicationStatus.2010_08_26_15_39_17.out ” command to see the output
admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2010_08_26_15_39_17.out

SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
———————————————————————–
g_darcuc_ccm7_1_3_32900_4    2 Active   Connected       0 Aug 26 15:34:16
g_goscuc_ccm7_1_3_32900_4    3 Active   Local           0

————————————————-
No Errors or Mismatches found.
Replication status is good on all available servers.

options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 – 20 of 20) :
admin:
admin:
admin:
admin:show perf query class “Number of Replicates Created and State of Replication”
==>query class :

– Perf class (Number of Replicates Created and State of Replication) has instances and values:
ReplicateCount  -> Number of Replicates Created   = 427
ReplicateCount  -> Replicate_State                = 2

If the count is ‘3’ then you may have replication issues. Follow the steps to resolve replication issues:

  • Utils debreplication stop on Subscriber
  • Utils debreplication stop on Publisher (once you stopped Subscriber)
  • Utils dbreplication reset all (from Publisher)
  • If needed restart Subscriber

This will fix the issue. Sometimes I did came across a misleading message after repairing replication. It was like:

admin:utils dbreplication reset all
Replication reset is in progress. Replication setup will continue in background.
Please watch RTMT replication state on all nodes. It should go from 0 to 2.
When all subs have an RTMT Replicate State of 2, replication setup is complete.
If RTMT Replicate State shows 4, there is an error in replication setup.
DbMon correctly signalled
command failed — Enterprise Replication not active (62)

command failed — Enterprise Replication not active (62)

If you come across this, there is no reason to get panic. It’s a Cisco Bug CSCso82088.

The replication has been successful. You can use the above perf query commands to verify replication status. It should be ‘2’ for good replication.


If replication status still not synches try this:

utils dbreplication stop on sub wait for it to stop.
utils dbreplication stop on pub.

utils dbreplication dropadmindb on pub, wait for syscdr to drop.

utils dbreplication dropadmindb on sub.

Once that is done utils dbreplication reset all from pub.

Another useful command to check replication:

admin:utils dbreplication runtimestate

DB and Replication Services: ALL RUNNING

Cluster Replication State: Only available on the PUB

DB Version: ccm7_1_3_32900_4
Number of replicated tables: 427

Cluster Detailed View from SUB (2 Servers):

PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP
SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT)
———–     ————    ——  —-    ———–     —–   ——- —–   —————–
DAR  172.22.6.x    0.352   Yes     Connected       0       match   N/A     (2)
GOS  172.22.5.x    0.026   Yes     Connected       0       match   N/A     (2)

admin:

To check Database Integrity:

show cuc dbconsistency unitydirdb

show cuc tech dbserver integrity

 

Useful Commands for Cluster:

Show tech network hosts

Show network cluster

Show tech dbstateinfo

utils diagnose test

utils network hosts

utils network host xxxxx – you can put the name of the CCM server which will resolve to ip address. if you put ip address this will give you the name of the server. This will prove that DNS is working correctly.

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s