- 4 minutes to read

What DataPower Gateway versions are supported?

IBM DataPower Gateway firmware 7.0+ is fully supported, including:

  • IDG 7.x - Legacy firmware still in production
  • IDG 10.x - Current major version with enhanced security features
  • 2018.4.1.x - Cloud-native releases optimized for container deployments

Supported Deployment Models

The Nodinite DataPower Monitoring Agent connects via standard protocols (SNMP traps + SOMA XML Management Interface), ensuring compatibility across all deployment models:

Physical Appliances

  • IBM DataPower Gateway 9235 - Entry-level hardware appliance
  • IBM DataPower Gateway 9250 - Mid-range appliance for departmental deployments
  • IBM DataPower Gateway 9255 - High-performance enterprise appliance

Virtual Appliances

  • VMware ESXi - DataPower Virtual Edition on vSphere infrastructure
  • Microsoft Hyper-V - DataPower on Windows Server virtualization
  • KVM - DataPower on Linux virtualization platforms (RHEL, Ubuntu)

Container Deployments

  • Docker - DataPower Gateway container images for development/testing
  • Kubernetes - Production container orchestration (OpenShift, AKS, EKS, GKE)
  • IBM Cloud Kubernetes Service - Managed Kubernetes with DataPower

Cloud Deployments

  • AWS (Amazon Web Services) - DataPower Gateway AMI on EC2 instances
  • Microsoft Azure - DataPower Gateway on Azure Virtual Machines
  • IBM Cloud - DataPower Gateway as a Service (managed offering)
  • Google Cloud Platform - DataPower Gateway on Compute Engine

Monitoring Protocol Consistency

The agent uses standard protocols that work across all DataPower versions and deployment models:

  • SNMP traps - Real-time event notifications (certificate expiration, failed logins, service state changes)
  • SOMA XML Management Interface - HTTPS-based polling for metrics (CPU, memory, disk, service health)

This protocol-based approach ensures:

  • No firmware-specific customization required - Same agent configuration works with DataPower 7.x, 10.x, and 2018.4.1.x
  • No deployment model dependencies - Monitor physical appliances, virtual appliances, containers, and cloud instances using identical agent setup
  • Future-proof compatibility - New DataPower firmware versions inherit SNMP/SOMA API compatibility (IBM backwards-compatible commitment)

Older Firmware Versions

If running DataPower firmware 6.x or earlier, contact Nodinite support for compatibility guidance:

  • Email: support@nodinite.com
  • Subject line: "DataPower 6.x compatibility inquiry - [Your Company Name]"
  • Include: Current firmware version, deployment model (physical/virtual), integration requirements

DataPower 6.x uses earlier SOMA API schema versions that may require agent configuration adjustments.

Version Detection

The Nodinite agent automatically detects DataPower firmware version during initial connection:

  1. Agent sends SOMA API request: <dp:request><dp:get-status class="FirmwareVersion"/></dp:request>
  2. DataPower responds with firmware details: Version, build date, deployment model
  3. Agent logs version information in Nodinite Log Database for inventory tracking
  4. Version displayed in Monitor Views (useful for multi-appliance environments with mixed firmware versions)

Example: Monitor View "DataPower Appliance Inventory" shows:

  • Prod-Primary: IDG 10.0.5.0 (Physical 9250)
  • Prod-Secondary: IDG 10.0.5.0 (Physical 9250)
  • Dev-Test: 2018.4.1.15 (Docker container on Linux)
  • DMZ-External: IDG 7.8.2.0 (VMware ESXi)

Next Steps

To ensure your DataPower Gateway monitoring is configured for your specific firmware versions, follow these steps:

  1. Verify Your Current Firmware - Log into each DataPower appliance WebGUI (System → Information) to confirm firmware version (7.x, 10.x, or 2018.4.1.x).

  2. Confirm SOMA API Availability - Ensure your firmware version has SOMA XML Management Interface enabled (port 5550), which is standard on all supported versions.

  3. Configure the Monitoring Agent - Deploy Nodinite DataPower Monitoring Agent and verify automatic firmware version detection during initial connection (check agent logs for FirmwareVersion SOMA API call).

  4. Create Inventory View - Build a Monitor View showing all DataPower appliances with their firmware versions, deployment models (physical/virtual/container), and last update date for compliance audits.

  5. Plan Firmware Upgrades - Use the appliance inventory to identify DataPower instances approaching end-of-support dates, and plan upgrades to DataPower 10.x for enhanced security features.