[cisco-voip] Upgrade from UCCX 7.0(1)SR5 to UCCX 8.5.1.11002-22

[Buchanan, James]

My experience in this migration is that phase 2 required the use of the username and password configured in UCCX as an administrator. If for some reason it cannot talk to UCM due to either a version incompatibility or other issue, it won't let you login. 

James Buchanan| UC Technology Manager | Presidio South | Presidio Networked Solutions 
12 Cadillac Dr Ste 130 Brentwood, TN 37027 | jbuchanan at presidio.com
D: 615-866-5729 | F:615-866-5781  www.presidio.com


-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan LaFountain (rlafount)
Sent: Tuesday, July 10, 2012 7:55 AM
To: Jonathan Charles; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Upgrade from UCCX 7.0(1)SR5 to UCCX 8.5.1.11002-22

Hi Jonathan, 

Unfortunately, I don't think there is a way to verify that Phase II has been completed from the CLI. You can look at the MCVD logs to see if the import is still running, but I would troubleshoot why you can't login first. 

Phase I of the import should've configured UCCX to use the same AXL provider as was in your 7.x cluster. The AppAdmin administrator should've been the same too. After Phase I was done, the Application User you specified during the install is no longer authorized to login to AppAdmin.

So, it could be the following:

1. UCCX can't contact the AXL provider server.

2. UCCX can't authenticate using the AXL provider user. I think it is this because of the error message you're getting.

3. UCCX can't authenticate the AppAdmin administrator specified.

If you attempt to login, and pull the MADM logs 'file list activelog /uccx/log/MADM' LIB_AXL is enabled in these by default, so you should be able to see what is happening between UCCX and CUCM.

If the authentication of the AXL provider user is actually failing, it means that the password is incorrect for the AXL provider, the Application User is missing in CUCM or the user doesn't have AXL API rights. The logs should show you what username UCCX is attempting to use for the AXL provider, but the password will be hidden.

Thank you, 

Ryan LaFountain
Unified Contact Center
Cisco Services
Direct: +1 919 392 9898
Email: rlafount at cisco.com
Hours: M ­ F 9:00am ­ 5:00pm




On 7/10/12 7:02 AM, "Jonathan Charles" <jonvoip at gmail.com> wrote:

>
>
>
>After importing the data, and phase 1 completes, the 8.5.1 server logs 
>you off the setup and sends you to appadmin where you are supposed to 
>login and monitor the remainder of the restore using a pre-upgrade 
>username and password; however, you cannot login  any more using any 
>appadmin account.
>
>
>in fact, it appears all of the accounts disappear... the clean install 
>appadmin account and the old appadmin accounts from the backup:
>
>
>admin:show uccx appadmin administrators  Command successful.
>admin:
>
>
>
>It also says to not reboot until the restore is complete... we are 
>going on 10 hours now, with no signs of life from this thing...
>
>
>
>
>How can you monitor if the restore is working without being able to 
>login to appadmin?
>
>
>Creating new accounts via the command line also has no effect:
>
>
>                  
>admin:set uccx appadmin administrator crsadmin Successfully set user as 
>AppAdmin Administrator  Command successful.
>admin:
>
>
>
>And all attempts to login to appadmin get this error:
>
>
>AXL Authentication failed.Please try again.
>
>
>
>
>
>I have confirmed the axl provider is the live CCM.
>
>
>admin:show uccx provider ip axl
> Cisco Unified Communications Manager IP is 10.10.33.8
>
>
> Command successful.
>admin:
>
>
>
>What else can I check before calling TAC?
>
>
>
>
>
>
>Jonathan


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
This message w/attachments (message) is intended solely for the use of the intended recipient and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments.  Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.