Field Notice: FN - 72067 - Patch ap358246 Fails to Apply on Cluster When Patched Simultaneously With ap367517 - Software Upgrade Recommended

Notice

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Revision History

Revision	Publish Date	Comments
1.0	08-Feb-21	Initial Release

Products Affected

Affected OS Type	Affected Software Product	Affected Release	Affected Release Number	Comments
NON-IOS	Application Patches	22.0	22.0.2020.01

Defect Information

Defect ID	Headline
CSCvw92855	There were no defects filed with this field notice at the time of publication.

Problem Description

Patch ap358246 fails to apply on the last cluster node when patching a Network Database Server (NDS), Network Functions Manager (NFM), or Unified Messaging Server (UMS) cluster with both ap358246 and ap367517 in the same patching operation. Both of those patches upgrade MariaDB database. When ap358246 stops MariaDB on the last cluster node in preparation for the MariaDB upgrade, the cluster nodes with ap367517 begin to use the latest replication protocol which is not backward compatible with the MariaDB version (10.1.32) in ap358246 resulting in a failure to start MariaDB making the patch activation fail.

Background

Note: This field notice was originally posted in the BroadSoft Xchange portal and has been moved over to Cisco.com as-is for historical purposes.

Problem Symptom

The patch fails to apply when applied individually, or when applied as part of a patch bundle.

MariaDB fails to start and join the cluster.

Workaround/Solution

BroadWorks patches can now be downloaded through the Cisco Software Download Center after logging in with your Cisco.com (CCO) account.

The version of BroadWorks that is currently deployed as well as the patches currently activated can be checked by executing the get versions all command from the CLI. More information on how to check the patch level can be found in the Cisco BroadWorks Maintenance Guide.

Workaround

In order to avoid this issue, all cluster nodes should be patched with ap358246 before proceeding with the activation of ap367517.

Patch

In the event that ap358246 and ap367517 are applied simultaneously and an error occurs on the last cluster node, then this last node needs to be isolated using these steps:

1. Stop BroadWorks on the node to isolate. (stopbw)
2. Stop MariaDB on the node to isolate. (mdbctl stop)
3. Delete all peers on the node to isolate. (peerctl del <peer>)
4. Block incoming connections by blocking port 3306. IP Tables can be used to block a network port.
5. With the node isolated, both patches can be applied.
6. Once the patches are active, stop MariaDB. (mdbctl stop)
7. Add all peers. (peerctl add <peer> <peer>)
8. Restore access to port 3306 by reverting step #4.

Rejoin the cluster using the mdbctl join command. This will trigger a complete transfer of the database from an existing cluster member.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

• Open a service request on Cisco.com
• By email or telephone

Receive Email Notification For New Field Notices

My Notifications—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.