Alarms are not generating after robot migration to a new proxy hub

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

After migration of our secondary hubs to a new gateway/proxy hub via running the DMZ wizard on the hubs, the robot alarms are not being generated in the alarm window. The other seemingly related issue was with emails not being sent out when alarms are generated in the new environment. 

emailgtw: message before replacing html tags = SMTP server(s) not responding: Failed sending data to the peer

Environment

• DX UIM 23.4 CU3
•  Proxy Hub 23.4.2
• robot (controller) 23.4.0

Cause

• Hub and robot versions were different

Resolution

The public IP in question displayed in the Tunnel proxy hub was the correct IP however when the customer upgraded the Proxy Hub version to 23.4.2 but the controller was still running 23.4.0, this caused a problem. When the customer updated the controller as requested the connection was then re-established to the migrated clients.

The customer worked with their network team trying to resolve what was causing the email failures "emailgtw: message before replacing html tags = SMTP server(s) not responding: Failed sending data to the peer"

emailgtw v2.91 GA has the most recent fixes included.

• Resolved an issue with the emailgtw probe where emails sent via the SMTP server were not in the correct format if the email content exceeded 998 characters.
• Resolved an issue with the emailgtw probe where it could not connect to the SMTP server due to authentication failure. Added the raw config setting 'enable_auth' to specify the authentication type for the server.
• Resolved an issue with the emailgtw probe where emails were sent by default using multipart. Added the option to send emails without multipart using the raw config setting 'disable_multipart'