Unable to write to primary BE host on port 2012 warning in EPM

Products

• VMware Smart Assurance

Issue/Introduction

After upgrading to M&R 7.9.0.1, you see an "Unable to write to primary BE host on port 2012" warning within EPM (Events-Processing-Manager).

Environment

Watch4net|M&R 7.9.0.1

Cause

Smarts EPM is configured to write events to the Alerting Backend (BE). During the upgrade, the alerting.xml configuration file was updated incorrectly, which causes the service to stop listening on port 2012.

Resolution

To resolve this warning, you must restore the alerting.xml file from a known working backup and restart the Alerting BE service.

1. Locate a valid, pre-upgrade backup of your alerting.xml file.
2. Replace the current alerting.xml file with the backup version.
3. Restart the Alerting BE service.
4. Verify that the service is successfully listening on port 2012.

Note: If the issue persists, ensure that no other processes are conflicting with port 2012 on the primary BE host. If you require further assistance or if the configuration files were not backed up, please contact Broadcom Support for guidance on recreating the default configuration.