search cancel

NFA Not Connecting After Upgrading PM r3.7.16

book

Article ID: 201898

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

Upgraded NFA from r10.0.2 to r10.0.4 and PM from r3.7.15 to r3.7.16.  NFA was deleted from CAPC as a data source before starting either upgrade.

After the  upgrade, I re-created NFA as a data source and the status shows "Awaiting bind"

Cause

NFA was configured to use HTTPS before the upgrade.  After the NFA upgrade NFA is configured to use HTTP.  HTTPS needs to be reconfigured.

Environment

Release : 20.2

Component : IM Reporting / Admin / Configuration

Resolution

HTTPS needs to be reconfigured after upgrading NFA.  A script is available to that can accomplish this and is available here:

https://knowledge.broadcom.com/external/article?articleId=201630

Attachments