Common Gateway Enhancements
The following enhancements and bug fixes are applicable to both Classic Gateway and NextGen Gateway.
Enhancements
Network Configuration Backup Support for Cisco FPR-3120 (FX-OS)
Network configuration backup support added for Cisco FPR-3120 (FX-OS). Earlier, these devices were not supported by OpsRamp Gateway. With this update, OpsRamp collects configuration backup for FPR-3120 firewall devices.
Gateway OVA Compatibility with VMware ESXi 7
The Gateway OVA now supports deployment on VMware ESXi version 7 and later. Earlier ESXi versions are no longer supported as they have reached end of life (EOL). If you are running an older ESXi version, you must upgrade to ESXi 7 or above to continue deploying or updating Gateway OVAs.
Bug Fixes
Ping Monitoring Accuracy
Issue: Duplicate device responses were incorrectly processed during ping monitoring, causing inaccurate availability data for other devices.
Resolution: Ping monitoring now correctly filters out duplicate responses. This ensures that availability results are accurate for all devices monitored by the Gateway.
Impact: You will see improved reliability and correctness in device availability reports.
VNX Discovery Timeout Handling
Issue: The VNX discovery process sometimes timed out for larger devices with bigger response payloads, leading to incomplete discoveries.
Resolution: The Gateway now waits longer during VNX discovery, allowing it to process larger response payloads and discover all devices as expected.
Impact: Greater completeness and accuracy during VNX device discovery, especially for large devices.
vCenter CPU Consumption
Issue: vCenter monitoring causing high CPU consumption on the vCenter server, impacting performance.
Resolution: The monitoring logic has been optimized so the OpsRamp Gateway now collects vCenter data more efficiently, reducing CPU overhead on the vCenter server.
Impact: Lower CPU utilization during monitoring operations, leading to improved stability and smoother performance in VMware environments.
Classic Gateway Updates
Enhancements
Unmanaged Disks to Managed Disks in Azure Gateways
You can now migrate OpsRamp Gateways on Azure from unmanaged disks to managed disks with official support. After September 30, 2025, Azure will deprecate unmanaged disks, and VMs using them will be deallocated until migrated. This update ensures your Gateway VMs can be safely transitioned, avoiding downtime and taking advantage of the reliability and scalability of managed disks.
See Migrate Linux VM from Unmanaged Disks to Managed Disks for more information.
Bug Fixes
NTP Server Update API
Issue: Updates made through the NTP Server Update API were not applied correctly. Users who updated NTP configurations through this API found that the changes were not reflected, and the Gateway continued using previous settings.
Resolution: The API has been fixed so that updated NTP server configurations are now saved and applied as expected.
Impact: This fix affects only users who manage NTP settings through the API. If you previously relied on this API, your updates will now be applied reliably without manual intervention.
NextGen Gateway Updates
Enhancements
Configurable File Descriptors for Proxy
Previously, the Squid proxy on Gateways was limited to 4,096 file descriptors (about 2,048 agent connections). This fixed cap was often insufficient for high-scale deployments and could lead to connection drops, while in smaller environments it could result in wasted resources. With this release, you can configure the Squid proxy file descriptor limit during Gateway registration on the NextGen Gateways. This flexibility lets you scale proxy capacity to reliably support large agent volumes or optimize usage in smaller environments without manual workarounds.
Automatic update of DHCP to Static IP as part of Gateway Deployments
When you deploy a new OpsRamp Gateway (Classic or NextGen) using ISO or OVA, the installer now automatically converts the DHCP-assigned IP address into a static IP during first boot. This removes the need to log in and reconfigure the network manually, making deployments faster and less error-prone. The feature is available for both Classic and NextGen Gateways, and no additional configuration is required. If DHCP is not available, you must log in through the VM’s console to assign the static IP manually. In environments with multiple NICs, verify that the correct NIC received the static IP and update it if necessary.
Automatic VMware Tools Installation in Gateway ISO
When you deploy a Classic or NextGen Gateway using the ISO image on VMware, VMware Tools is now installed automatically if the environment is detected as VMware. This package enables you to view details such as IP address and hostname directly in the VMware console, ensures smoother operations like shutdown and restart, and prevents duplicate device entries in the OpsRamp portal when VMware integration is enabled. This enhancement is available only for ISO-based deployments on VMware platforms, reflecting customer requests for VMware Tools support.
Enhanced DNS Connectivity Validation
The NextGen Gateway now includes an init container that ensures CoreDNS is up and resolving correctly before other containers start. Previously, in some cases the vprobe container would start before CoreDNS was ready, causing DNS failures and blocking communication with APP/API servers. With this update, container startup order is enforced so DNS resolution is always available, reducing deployment failures and improving startup reliability.
Zero-Touch Onboarding Validation
The NextGen Gateway now validates your Zero-Touch Onboarding YAML configuration before processing it. Previously, if the YAML file was invalid, onboarding silently failed without showing any error, leaving you unaware of what went wrong. With this enhancement, invalid YAML is detected early, and a clear error message is displayed, so you can fix issues immediately and complete onboarding successfully.
Collector Bootstrap Tool Enhancements
The collector bootstrap tool now supports configurable flags for runtime diagnostics. You can set log levels to debug, warn, or trace, and generate heap and thread dumps in a single step. Previously, you had to run manual commands for dumps and couldn’t adjust log levels dynamically, which made troubleshooting time-consuming. With these enhancements, you can quickly toggle detailed logging and capture diagnostic data on demand, making it easier to identify issues, reduce manual effort, and gain deeper insights into Gateway performance.
See Use Bootstrap Tool to Install the NextGen Gateway and Install the k3s and Enable HA for NextGen Gateway for more information.
Service Type Configuration for squid-proxy and nextgen-gw Services
You can now configure service types for squid-proxy and nextgen-gw services independently.Previously, both services shared a single service type, which limited your flexibility for different deployment scenarios. With this enhancement, you can assign different service types for each service, giving you more granular control over network exposure and access. When installing or upgrading using Helm, pass the following flags as needed:
--set service.gatewayServiceType=LoadBalancer--set service.squidproxyServiceType=LoadBalancer
See Registering nextgen gateway by using yaml config file for more information.
Custom CA Certificate Support in NextGen Gateway Updater Pod
We fixed an issue in the NextGen Gateway Updater Pod where custom CA certificates could not be imported due to permission errors. The updater now copies customer-provided certificates from /tmp to /usr/local/share/ca-certificates and runs the update-ca-certificates command successfully. With this fix, you can add your own trusted CA certificates without manual intervention, ensuring secure communication in environments that require custom certificate authorities.
Bug Fixes
Custom CA Certificate Import in Updater Pod
Issue: Custom CA certificates could not be imported in the NextGen Gateway Updater Pod due to permission errors. This blocked secure communication in environments requiring custom certificate authorities.
Resolution: The Updater Pod now correctly imports and updates custom CA certificates, ensuring secure communication with your trusted certificate authorities.
Impact: You can add your own CA certificates without manual intervention, supporting secure operations in custom environments.