Common Gateway - Security Fixes

The following security fixes apply to both Classic Gateway and NextGen Gateway.

UCM Service Monitoring

In Gateway version 17.2.0, a fallback mechanism was introduced where, if an IP-based connection fails, the tool attempts to connect using the hostname.

We fixed an issue where manual component selection in UCM Service Monitoring did not work for newly onboarded devices when the connection was established using the hostname instead of the IP address.

• Devices that already had monitoring templates applied were not affected.
• The fix now ensures that manual component selection works correctly even when the connection is made via hostname.

VMware Alarm Monitoring

In Gateway version 19.1.0, we made changes to VMware alarm monitoring to support alarms containing special characters in their alarm names.

However, this update caused an issue where system alarms were not processed, and only user-defined alarms were captured. The issue is now fixed to ensures both system alarms and user-defined alarms are processed correctly.