Field Notice: FN - 72030 - Replication Address Issue Upon BroadWorks Startup on AS, NS, and RI Network Server - Software Upgrade Recommended

Available Languages

Updated:February 15, 2021
Document ID:FN72030

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

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.08
NON-IOS
Application Patches
23.0
23.0.2020.08
NON-IOS
Application Patches
22.0
22.0.2020.08

Defect Information

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

Problem Description

After applying the platform patch ap372854 on a Network Server (NS), an Application Server (AS), or a deployment of Release Independent (RI) Network Server 2020.07, the replication addresses of peers are removed from the database upon BroadWorks startup. This only affects redundancy setups that are configured using the peerctl setReplicationAddress command, often used to allow TimesTen replication on a different network interface.

Upon the application of the ap372854 platform patch or the deployment of RI Network Server 2020.07 followed by starting BroadWorks, the replication address as listed by the peerctl showReplicationRouting command is reset to its default value.

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

Once the replication address is cleared, if the default interface used for TimesTen replication is blocked, secondary peers cannot connect to the primary peer anymore. This prevents replication startup and database import operations.

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

If affected by the issue, the workaround is to remove ap372854 until ap376147 is available.

Another workaround that allows importing a remote database (such as during an upgrade) with the replication address is:

  1. With the replication started and BroadWorks running on the primary, verify with the ttRepAdmin -showconfig NetworkServer or ttRepAdmin -showconfig AppServer command that the replication addresses are used correctly in the "Replication Route Information" section.
  2. If they are not set correctly, stop BroadWorks, set the replication addresses for all peers correctly (with the peerctl setReplicationAddress command), and then restart the replication.
  3. With the replication addresses now set properly, start BroadWorks.
  4. Upon starting BroadWorks, replication addresses are cleared. Set the replication addresses again with the peerctl setReplicationAddress command.
  5. The remote peers can now be patched properly and the database can be imported from the primary peer to the remote peers.

The second workaround is applicable on RI Network Server 2020.07 as there is no patch to remove, and there is no previous version to revert to.

Patches

Platform patch ap376147 is now available on Xchange to address this issue. The fix is also available as part of the Network Server Release 2020.08 and later.

These patches are now available through the Cisco Software Download Center:

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:

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.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco