cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
75
Views
0
Helpful
1
Replies

Upgrading Unity Connection 14 SU2 to 15 SU2—Filesystem Concerns

dhoskins
Level 1
Level 1

Hi everyone,

We're currently running Cisco Unity Connection Version 14 SU2 as a virtual machine on VMware. We recently learned about field notice FN74144, which states that the SpeechView Transcription Service will stop working after December 30, 2024, and recommends a software upgrade.

Because of this, we need to move off Unity Connection Version 14 SU2 as soon as possible. Our immediate plan is to upgrade to Unity Connection Version 15 SU2, which transitions to the Cisco Webex in-house transcription service. Our Cisco solutions collaboration engineer advised against it for now, suggesting it requires more extensive planning due to its complexity.

We ran the pre-upgrade test, and the only issue that surfaced was related to the ext3 filesystem. I believe we need to use this COP file to change the filesystem from ext3 to ext4: ciscocm.CSCwi52160_15-direct-migration_v1.0.k4.cop.sha512. However, the COP file's description isn't very clear about whether it accomplishes this. Has anyone used this COP file to upgrade the filesystem, and did you encounter any issues during the conversion?

Aside from the filesystem concerns, are there any other significant issues we should be aware of when performing this upgrade?

For additional context, we're also running Call Manager 14 SU3, IM&P 14 SU3, UCCX 12.5.1 SU3, and CER 14 SU3a. If any of this information is relevant to the Unity Connection upgrade, we'd appreciate your insights.

Thanks in advance for your help!

1 Reply 1

AFAIK that COP file doesn’t do anything to the file system. This is what the release note says.

What this COP file provides:
This COP file contains changes or patches to update the Linux Pluggable Module’s system-auth configuration. This COP is
applicable only when we migrate from 10.x/11.x/12.x/14.x to 15, with upgrade history from 8.x(or)9.x.

From what I know you’ll need to either do a fresh install, followed by DRS restore or a data export, followed by a new installation with data import.



Response Signature