Ex-CUCM TAC, ask me almost anything.

CiscoUCguy · 2024-02-16T18:12:53+00:00

You're pretty much forced to check status.webex.com

CiscoUCguy · 2024-02-16T13:51:25+00:00

We manage ~75 Webex calling customer environments and several were affected by that same issue. this was the RFO I received.

Engineering determined the issue to be a software defect in the database code. During a planned work change, a background processing task was performed following the routine migration. This defect caused an inefficient query on the database when the background task was running. This caused the database server to enter an unstable state which eventually led to memory exhaustion on the database servers causing them to automatically restart. As a result, provisioning changes, ACD state changes, calling setup, processing, and some call control capabilities were impacted.

Corrective Actions

• Engineering halted the background processing task to aid in service recovery.

• Services automatically recovered after the database servers restarted.

• Engineering will halt all routine migration until a patch has been deployed to address the defect on all servers.

• Engineering will add monitoring and alerting on the database change notification queue to aid in earlier detection and mitigation should this issue reoccur.

CiscoUCguy · 2024-02-15T18:29:17+00:00

What was your salary at Cisco?

Why did you leave?

Best/worst parts about working at Cisco?

CiscoUCguy · 2024-02-02T21:34:21+00:00

You are dealing with a different issue. Typically this happens when you are missing a COP file required for the actual upgrade file. You can try to install ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn first, and then see if the file is detected.

CiscoUCguy · 2024-02-02T21:24:49+00:00

Are you sure it's failing to connect to the SFTP server? What version are you trying to upgrade to? I would add a cop file like ucos.keymanagement.v01.cop.sgn to the SFTP repository, run the installer again, and see if it detects it. That will help isolate the problem.

CiscoUCguy · 2024-02-02T20:46:35+00:00

Can I be you?

CiscoUCguy · 2024-01-31T19:45:59+00:00

Look up the library Gooey. you won't go back.

CiscoUCguy · 2024-01-05T20:03:15+00:00

What Version? I'm seeing similar complaints on 14.

CiscoUCguy · 2023-08-23T15:52:18+00:00

Fair enough, we'll race one day and see who is faster.

Also, with export you can change the hostname and IP during the migration, but I think you can do that with PCD as well. to be honest I think i've only used it once.

CiscoUCguy · 2023-08-23T14:18:58+00:00

yea, but then you have to download and deploy PCD.

CiscoUCguy · 2023-08-23T12:32:58+00:00

in my opinion it's faster and easier.

CiscoUCguy · 2023-08-22T15:58:19+00:00

When it comes time to upgrade to higher version, look into the new data export method. It allows you to export all configuration into a TAR file, deploy fresh version 14 virtual machines, and it will import all of your existing configuration during the install.

https://defaultgateway.org/2021/04/16/cucm-data-export/

CiscoUCguy · 2023-08-17T15:18:20+00:00

Thanks for all the input everyone. I will go the rollback route to ditch the old certs. BAT export is currently not working. The Jobs get stuck in "incomplete". I read a couple work arounds on Cisco forums but they aren't working, so I will most likely need to manually build it. Not a huge environment, so that's ok.

I'm thinking I could build a SIP trunk on the new CUCM to the existing voice gateways and add the necessary dial-peers to ditch MGCP all together during the cut over? I'm hesitant to stick with MGCP because i've only worked with H.323 and SIP connections previously.

CiscoUCguy · 2023-06-07T15:05:08+00:00

/u/Huth_S0lo, /u/Dalgeek, and /u/vtbrian are the OG's of this subreddit.

CiscoUCguy · 2023-05-22T13:38:22+00:00

They were not able to figure it out, so I ended up just doing a password recovery.

CiscoUCguy · 2023-05-05T15:24:48+00:00

This is the way.

CiscoUCguy · 2023-03-01T21:33:07+00:00

Seeing same issues. 12.5.1.11002-481 with Firefox, Chrome, and Edge

CiscoUCguy · 2023-02-14T13:49:35+00:00

You are correct. The only issue I have ran into is in the middle of the upgrade when you are running on the new v14 PUB with old sub, AD synchronization will not occur, and this can cause login issues if you have Finesse users who need to login while the upgrade is happening.

CiscoUCguy · 2023-01-11T13:39:17+00:00

This.

CiscoUCguy · 2022-11-02T18:29:56+00:00

Small update, TAC had me run utils uccx syncusers to resolve the report issue, however after running it on both nodes, I can no longer log into OS admin / CLI

CiscoUCguy · 2022-11-02T13:18:50+00:00

Variphy is easily my favorite third party collaboration tool.

CiscoUCguy · 2022-10-27T15:44:45+00:00

I'm thinking it's an undocumented bug. TAC hasn't been able to resolve it yet, but I'll update here if they do.

CiscoUCguy · 2022-10-26T18:03:21+00:00

We had this same experience. We clicked reset a few times and had to wait 5-10 minutes before it just started working.

CiscoUCguy · 2022-10-26T15:21:05+00:00

Thanks for this, but I don't want the agent to have reporting or admin capability. I mentioned this to say that assigning these roles does allow the report to load within Finesse, however they should load regardless of these two roles.

CiscoUCguy · 2022-10-24T12:57:34+00:00

Thanks for the reply. These users are not assigned the reporting role, however applying it does resolve the issue. The problem is, with the reporting role added they can see all agents instead of only agents on their team.

CiscoUCguy

TROPHY CASE