Unity Connection 8.6(2) to 8.6(2a) upgrade failed

OK, so I upgraded from CUCM 8.6(2) to CUCM 8.6(2a) tonight.  No problems.  Tried doing the same thing with UCXN, but failed with the following entries in the log:


10/11/2011 19:32:43 upgrade_manager.sh|Check if the upgrade is allowed|
10/11/2011 19:32:43 upgrade_manager.sh|Validate hardware for the upgrade|
10/11/2011 19:32:43 upgrade_manager.sh|Hardware is supported for the upgrade|
10/11/2011 19:32:49 upgrade_manager.sh|Validate hardware for "connection" deployment|
10/11/2011 19:32:50 upgrade_manager.sh|File:/common/download/8.6.2.20000-2/upgrade_manager.sh:1048, Function: validate_upgrade_allowed(), This server is not supported for use with the version of "connection" that you are trying to install. For information on supported servers, see the applicable version of the "connection" Supported Platforms List at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html|

Seems weird that the hardware is supported for the upgrade, but not for the "connection" deployment.  Can someone explain that to me?

Also, I always use VMware Workstation 7 running on Windows 7 64-bit in my lab.  I tried bumping up the RAM for this VM from 2GB to 4GB, but got the same error.  I saw some NetPro posts about increasing the hard drive size, but I think that was on ESXi and you needed a rescue CD.  I remembered that after I installed 8.6(2), I had changed the number of cores per processor from 1 to 2.

I powered off the VM, then set the number of cores per processor to 1.  I powered the VM back up, ran the upgrade again and it worked just fine.

I know its not supported, but it is interesting that I want to give more CPU power to the VM, but in doing that, it is supported?  Oh well.  I'm running 8.6(2a) on both CUCM and UCXN now.

Contact is in Terminated/Connected State

I came across this error the other day on a new UCCX 8 install.  You call into any of the triggers, but disconnects immediately.  Doing a reactive debug shows that it fails on the Accept step in the script with the following error:

Contact ID:x, Channel ID:y, Contact is in Terminated/Connected state.

You will notice that x and y will change based on your call attempts.  I tried upgrading to 8.5(1)SU1 and 8.5(1)SU2, but didn't help.

Also, in the trace files that you can grab via RTMT, you will see the following entry:

4323: Oct 01 10:25:12.495 CDT %MIVR-SS_TEL-7-UNK:CallID:4 MediaId:5937/2 Task:17000000003, CallCtlConnFailed, Inbound call, callctl cause:107, [6612:PT_Internal:1/(P1-jtapi_1) GCID=(2,4323)->ACTIVE]->FAILED

Now, ask anyone else, any you will most likely be told that it is a codec issue 99% of the time with a callctl cause of 107.  That is true.  But, in this case, it is not.

The fix is to create a new Media Termination Dialog Group and apply it to your triggers.  TAC said it has something to do with the fact that if your licensing is messed up when you setup the initial Media Termination Dialog Group, it won't work and you have to recreate it once your licensing are setup correctly.

Thanks,

IPTBuzz

Network connectivity issues in VMware with UC products

If you are like me, then you probably have some type of home lab running the UC products such as CUCM, UCXN, CUPS, UCCX, etc, in either VMware Workstation or ESXi.  I have seen an issue on CUCM, but now almost everytime after I reboot UCCX 8.x and higher, I can't ping to or from the UCCX server.  From the CLI of the UCCX server, I can only ping it's eth0 address and can't ping anything else.  From other devices, I can't ping UCCX.  Rebooting doesn't help.  The only way I can get network connectivity is to run the set network status eth0 down command followed by the set network status eth0 up command.  After a few seconds, everything works just fine.

Anyone know how to get around this without having to take the eth0 interface down and up?

***ADDED ON 10/16/2011***
I had the same issue on CUPS when I upgraded to CUPS 8.6.1.10000-34.  I would lose network connectivity to the CUPS server in the VM.  From the console, I could the address I have on eth0, but can't ping it from the VMware host or gateway.  Unfortunately, the set network status eth0 down and up commands were unsuccessful to get it pinging again.  After reading through the CLI docs and typing a ? at the CLI and looking at the commands, this is what fixed it for me:


set network restore eth0 10.10.10.15 255.255.255.0 10.10.10.1


Now, anytime I reboot the server, I lose connectivity and I always have to enter this command after the server comes back up in order to use it.

Thanks,

IPTBuzz

Bad RAID controller on UCS C210 M2 chassis

If you have a UCS chassis where the VMs go offline and you can't access the VMs with vSphere, you may have to reboot the chassis via the IMC web interface.  But, when you reboot it and watch it via the IP KVM console, this is what you don't want to see:

LSI MegaRAID SAS-MFI BIOS

Version 3.20.00 (Build November 19, 2010)

Copyright(c) 2010 LSI Corporation

HA -0 (Bus 14 Dev 0) LSI MegaRAID SAS 9261-8i

FW package: 12.12.0-0038

Multibit ECC errors were detected on the RAID controller.

The DIMM on the controller needs replacement.

Please contact technical support to resolve this issue.

If you continue, data corruption can occur.

Press 'X' to continue or else power off the system and replace the

DIMM module and reboot. If you have replaced the DIMM press 'X' to continue.

OK, so get TAC on the phone and have them send you the replacement controller.  Hopefully, you have 4 hour response.  Here is the link to replace the RAID controller in the UCS chassis:

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C200M1/install/replace.html#wp1109809

After replacing the RAID controller, you will want to make sure to copy the drive configuration to the newly replaced controller.  This was not documented in the card replacement documentation.  Here is the link to do this.  Follow the instructions EXACTLY:

https://supportforums.cisco.com/docs/DOC-16321

Verify the virtual devices show up on the RAID controller during bootup.  Things still might go south.  The vSphere client may show CUCM and UCXN as missing.  This is because the datastores are not there.  TAC will need to re-add the datastores for you, possibly via CLI.  More than likely, the file system will have errors on the VMs.  It may be so bad that the won't boot, so you will need to mount the Recovery CD, boot to it, then choose the option to fix the file system errors.  After that, grab a beer. The servers should come up just fine.

Thanks,

IPTBuzz

Switch version doesn't switch

I ran into an issue recently running UCCX, although this has also happened to me on CUCM as well.  Let me make it known that these are running in VMware Workstation in a home lab.  In my recent attempt, I upgraded UCCX 8.5(1)SU1 to UCCX 8.5(1)SU2.  After the upgrade, I tried to perform a switch version from the OS Administration GUI.  But, watching from the CLI, nothing was happening.  So, I tried to switch it from the CLI with the utils system switch-version command, but got the following output:


admin: utils system switch-version


Active Master Version: 8.5.1.11001-35


Inactive Master Version: 8.5.1.11002-22




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.


Modified configurations will not be migrated in case you are
downgrading this server to an earlier release level




Do you really want to switch between versions ?


Enter (yes/no)? yes


 Switching Version and Restarting the Applicance ...


Switch version duration can vary depending on the database size
and platform configuration.  Please continue to monitor
the switchover process from here.




Waiting ................................


Operation failed


ERROR: Acquiring lock failed
admin:

Well, I couldn't find anything on Google, Netpro, or anywhere.  This resolution to fix this was simply rebooting normally with the utils system restart command.  Then, after the reboot, I was able to run the utils system switch-version command again, and this time it correctly switched to the other partition which made the upgraded 8.5(1)SU2 partition be the active one.  Not sure what happened, but this is what fixed it for me.  I think I had this one other time on CUCM when upgrading 8.6(1) to 8.6(2).

Another option for you if you can't switch versions is to boot to the Recovery CD for the application you are working with, then choose the option to switch version there.  I've typically used the Recovery CD to run the file system check if the server goes down hard and puts the file system in a read-only state.  But, you can also use it to switch between the active and inactive partitions.

Thanks!
IPTBuzz

How to SSH into a Cisco IP Phone

Here are the steps to let you SSH into a Cisco IP Phone.  In this example, the phone model is a 7961.

On the phone's device page in ccmadmin, scroll down to the Secure Shell Information section and type in a username and password for the Secure Shell User and Secure Shell Password. I simply used cisco and cisco.

Then, scroll down to the bottom and set the SSH Access drop-down box to Enabled.  Don't forget to Save and Apply Config.

Scroll back up to the top of the page and get the phone's IP address.

Open an SSH session to the phone's IP address.  You will probably get a typical key message window that you will have to accept.

Enter the username and password that you specified in the Secure Shell User and Secure Shell Password boxes on the phone's device page in ccmadmin.

You will then be prompted for another login and pasword from within your SSH session window.  Enter default for the login and user for the password and press enter.  You should then be at a $ dollar sign prompt.

Now that you are in, let's see what you can do!

$ ping 10.10.10.1

ping: reply received from 10.10.10.1, time = 1ms

ping: reply received from 10.10.10.1, time = 0ms

ping: reply received from 10.10.10.1, time = 0ms

ping: reply received from 10.10.10.1, time = 0ms

ping: packets - sent = 4, received = 4, lost = 0, ( 0 % lost )

time - total = 10 msec, avg = 2 msec/pkt

$

OK, what about the file and folder structure?

$ cd /

$ ls

bin     dev     flash0  home    root    tmp     usr

cnu     etc     flash1  modules sbin    ubin    var

$

Let's see what's in the the flash0 directory.

$ cd flash0

$ ls

Monospace.font  apps            home            sc-font.xml     syslog

RMS             bin             local           sec             ubin

Unicode.font    etc             modules         ssh

$

How about the bin directory?

$ cd /

$ cd bin

$ ls -l

total 5983

-rwxr-xr-x  1 root      sys           260 Jul 11 2005 AUTH.png

-rwxr-xr-x  1 root      sys          1738 Dec 06 2006 BGRND.png

-rwxr-xr-x  1 root      sys           218 Jul 11 2005 BLANK.png

-rwxr-xr-x  1 root      sys           252 Jul 11 2005 DOWNL.png

-rwxr-xr-x  1 root      sys           258 Jul 11 2005 ERROR.png

-rwxr-xr-x  1 root      sys           250 Jul 11 2005 NETWK.png

-rwxr-xr-x  1 root      sys           204 Dec 05 2006 P2P.png

-rwxr-xr-x  1 root      sys           280 Jul 11 2005 WAIT.png

-rwxr-xr-x  1 root      sys           225 Jul 11 2005 WRITE.png

-rwxr-xr-x  1 root      sys         13188 Nov 13 2008 cat

-rwxr-xr-x  1 root      sys         24496 Nov 13 2008 chmod

-rwxr-xr-x  1 root      sys         23704 Nov 13 2008 chown

-rwxr-xr-x  1 root      sys          5002 Jan 11 2007 ciscoerror.png

-rwxr-xr-x  1 root      sys          5014 Jan 11 2007 ciscoreboot.png

-rwxr-xr-x  1 root      sys          5055 Jan 11 2007 ciscostart.png

-rwxr-xr-x  1 root      sys         13052 Nov 13 2008 cmp

-rwxr-xr-x  1 root      sys         88092 May 11 13:10 cnush

-rwxr-xr-x  1 root      sys         26248 Nov 13 2008 cp

-rwxr-xr-x  1 root      sys         39724 Nov 13 2008 cvw

-rwxr-xr-x  1 root      sys         20540 Mar 28 19:55 date

-rwxr-xr-x  1 root      sys        141936 May 11 13:10 debugsh

-rwxr-xr-x  1 root      sys         24936 Nov 13 2008 df

-rwxr-xr-x  1 root      sys         23160 Nov 13 2008 du

-rwxr-xr-x  1 root      sys          5564 Nov 13 2008 echo

-rwxr-xr-x  1 root      sys          8636 Nov 13 2008 ethmibs

-rwxr-xr-x  1 root      sys          8300 Nov 13 2008 ethstats

-rwxr-xr-x  1 root      sys         87860 May 11 13:09 ewCmd

-rwxr-xr-x  1 root      sys            26 May 31 2005 groups

-rwx--x--x  1 root      sys          6836 Nov 13 2008 halt

-rwxr-xr-x  1 root      sys         10636 Nov 13 2008 head

-rwxr-xr-x  1 root      sys         28404 Nov 13 2008 hexdump

-rwxr-xr-x  1 root      sys         15504 Nov 13 2008 id

-rwxr-xr-x  1 root      sys         19572 Mar 28 19:57 imgui

-rwxr-xr-x  1 root      sys         15400 Mar 28 19:56 ipcstat

-rwxr-xr-x  1 root      sys         15136 May 11 13:08 ipv6

-rwxr-xr-x  1 root      sys         10136 Nov 13 2008 kill

-rwxr-xr-x  1 root      sys          9248 Nov 13 2008 kldstat

-rwxr-xr-x  1 root      sys         10644 Nov 13 2008 ln

-rws--s--x  1 root      sys         15604 Mar 28 19:56 login

-rwxr-xr-x  1 root      sys         43356 Nov 13 2008 ls

-rwxr-xr-x  1 root      sys         18604 Nov 13 2008 mfg

-rwxr-xr-x  1 root      sys         10068 Mar 28 19:56 mib2

-rwxr-xr-x  1 root      sys         14656 Nov 13 2008 mkdir

-rwxr-xr-x  1 root      sys         12732 Nov 13 2008 mkfifo

-rwxr-xr-x  1 root      sys         21052 Nov 13 2008 more

-rwxr-xr-x  1 root      sys         23232 Nov 13 2008 mount

-rwxr-xr-x  1 root      sys         20876 Nov 13 2008 mv

-rwxr-xr-x  1 root      sys          9536 Nov 13 2008 nice

-rwxr-xr-x  1 root      sys           124 Mar 03 2010 nologin

-rwxr-xr-x  1 root      sys         41268 Mar 28 19:57 ntp

-rwxr-xr-x  1 root      sys         79712 Mar 28 19:56 ping

-rwxr-xr-x  1 root      sys        133872 Mar 28 19:57 ping6

-rwxr-xr-x  1 root      sys         29532 Mar 28 19:56 ps

-rwx--x--x  1 root      sys          6836 Nov 13 2008 reboot

-rwxr-xr-x  1 root      sys         27332 Nov 13 2008 rm

-rwxr-xr-x  1 root      sys          8084 Nov 13 2008 rmdir

-rwsr-s--x  1 security  sec        847916 May 11 13:03 secd

-rwxr-xr-x  1 root      sys         36072 Nov 13 2008 settmask

-rwxr-xr-x  1 root      sys        172556 Mar 28 19:58 sh

-rwxr-xr-x  1 root      sys          6768 Nov 13 2008 sleep

-rwxr-xr-x  1 root      sys         10136 Nov 13 2008 slog

-rwxr-xr-x  1 root      sys         19424 Mar 28 19:57 sostat

-rwsr-x--x  1 security  sec        184748 Mar 28 19:54 sshd

-rwxr-xr-x  1 root      sys         24472 Nov 13 2008 stty

-rwxr-xr-x  1 root      sys          4676 Nov 13 2008 sync

-rwxr-xr-x  1 root      sys         18440 Nov 13 2008 tail

-rwxr-xr-x  1 root      sys        156076 Nov 13 2008 tar

-rwxr-xr-x  1 root      sys         33304 Mar 28 19:57 tftp

-rwxr-xr-x  1 root      sys         80068 May 11 13:09 tftpClient

-rwsr-sr--  1 syslog    sys        159160 Nov 13 2008 tnpdisp

-rwxr-xr-x  1 root      sys         17904 Nov 13 2008 touch

-rwxr-xr-x  1 root      sys         17704 Nov 13 2008 umount

-rwxr-xr-x  1 root      sys          9680 Nov 13 2008 uname

-rwxr-xr-x  1 root      sys         28108 Mar 28 19:57 vm

-rwxr-xr-x  1 root      sys         10496 Nov 13 2008 which

-rwxr-xr-x  1 root      sys            17 May 31 2005 whoami

$ 

We can TFTP some files if we wanted to.

$ tftp

   TFTP: usage - tftp -s address srcFile dstFile

        tftpAddr = address of tftp server - ex: 10.1.1.1

        srcFile  = file to be retrieved - ex: sepxxx.cnf.xml

        dstFile  = filename in CNU file system - ex: /bin/sepxxx.cnf.xml

$

Let's check the processes taking up the CPU.

$ ps

format --> ps [-acCehjklmrSTuvwx] [-L] [-M core] [-O fmt] [-o fmt] [-p pid] [-U username]

$

$ ps -a

 pid %cpu   state tty command

   9  0.0     run   0 /bin/sh

   2  0.0     run   0 /sbin/syslogd

   0 85.3     run   0 sysIdle

  11  0.0     run   0 /sbin/inetd

  13  0.0     run   0 /sbin/rtsold

  25  0.0     run   0 /ubin/dsp

  19  0.0     run   0 /bin/login

  22  0.0     run   0 /bin/secd

  21  0.0     run   0 /bin/tftpClient

  24  0.0     run   0 /ubin/vieo

   6  0.1     run   0 /sbin/strace

  15  0.0     run   0 /sbin/dhcp6

  14  0.0     run   0 /sbin/cdp

  16  0.0     run   0 /sbin/pae

  17  0.0     run   0 /sbin/imgauthd

  20  0.0     run   0 /sbin/dhcp

  23  0.0     run   0 /bin/ntp

  29  0.0     run   0 /sbin/dns

   1  0.0     run   0 /sbin/init

   3 11.2     run   0 /tmp/sunvm.unzip/sunvm.cnu

  26  0.0     run   0 /sbin/ewcl

   5  0.0     run   0 /sbin/espd

  31 20.0     run   0 /bin/ps

  18  2.5     run   0 /bin/sshd

$

So, that is just an intro to how you can SSH into a phone and some basic ways to navigate around.  Brush up on your Linux commands and try them.  On newer models of phones (8900 and 9900 series), there are some commands that Cisco put in, such as viewing the call histories and watching the key presses on the phone.  More to come on my next post!

Cisco Phone Designer in Windows 7 64-bit

By default, you cannot run Cisco Phone Designer on Windows 7 64-bit.  Even if you try to set the compatibility mode to XP, it still won't work.  Here is the solution.

Open a command prompt, and type the following:

"C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\x64\corflags.exe" "C:\Program Files (x86)\Cisco Systems\Cisco Unified Phone Application\phonedesigner.exe" /32BIT+ /force

Once you enter this command, you will see this output:
C:\>"C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\x64\corflags.exe" "C:\Pro
gram Files (x86)\Cisco Systems\Cisco Unified Phone Application\phonedesigner.exe
" /32BIT+ /force
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  3.5.21022.8
Copyright (c) Microsoft Corporation.  All rights reserved.


Note - The path may be different, so you may have to browse your folder structure to find the actual location of corflags.exe on your PC.  Any recently updated Windows 7 PC should have it.  I believe you get it with the .NET downloads and/or associated SDKs.

Service Not Available in WebEx Connect

I came across this error message when trying to use either the softphone or deskphone control in WebEx Connect.  On the Phone tab, you will see an error message stating:

SERVICE NOT AVAILABLE
Your Communications Manager account is not configured correctly.  Please check your settings.  If you still have problems, contact your system administrator.

I made sure I had the latest CUCI Connect installed, then after quite a bit of troubleshooting including verifying the IP address and username and password of my CUCM account, phone and user association in ccmadmin, etc., I remembered I had recently installed the CUPC (Cisco Unified Personal Communicator) for troubleshooting a customer's network.  These 2 applications apparently conflict with each other.

Fix / Resolution / Workaround:

Uninstall the Cisco Unified Personal Communicator application.