Field Notice: FN - 72405 - NFM NodeLifecycle Instantiation Fails - Workaround Provided

Available Languages

Updated:June 8, 2022
Document ID:FN72405

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
01-Jun-22
Initial Release

Products Affected

Affected OS Type Affected Software Product Affected Release Affected Release Number Comments
NON-IOS
Base Software
RI
RI.2022.04
Cisco BroadWorks Release Independent 24

Defect Information

Defect ID Headline
CSCwb77224 NFM NodeLifecycle instantiation no longer works

Problem Description

For BroadWorks Network Function Manager (NFM) that runs Release Independent version 2022.04, the NodeLifecycle application is not able to instantiate a BroadWorks node.

Background

When the NFM node lifecycle management is used to instantiate a node, the operation fails because the License Manager Daemon (LMD) cannot reach out to the NFM. Therefore, the instantiated node cannot get its license from the NFM.

Problem Symptom

Node instantiation fails and the log shows Failed to get license from NFM.

 

Log example:

2022.04.19 07:19:45:395 UTC | Info | Generic | LicenseManager | 40

checkServerTrusted [192.168.1.2] result: NotTrusted, No trusted certificate found

2022.04.19 07:19:45:401 UTC | Warn | HTTP | LicenseManager | 41

Executing the request failed: No trusted certificate found

2022.04.19 07:19:45:402 UTC | Warn | LicenseManager | LicenseManager | 42

NFMClient: Cannot connect to = /192.168.1.2:443
Cause: No trusted certificate found

2022.04.19 07:19:45:402 UTC | Warn | LicenseManager | LicenseManager | 43

NFMClient: Route is unusable.

2022.04.19 07:19:45:402 UTC | Warn | LicenseManager | LicenseManager | 44

NFMClient: Getting license bundle failed. HTTP response code = 503

2022.04.19 07:19:45:402 UTC | Warn | LicenseManager | LicenseManager | 45

Failed to get license from NFM

Workaround/Solution

Workaround

Do not upgrade to NFM_Rel_2022.04_1.341. If you have already done so, revert to your previous release.

 

Solution

A fix will be available in NFM_Rel_2022.04_1.343.

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

This Document Applies to These Products