HPE NonStop integration with HPE OVO (now managed under OpenText/Micro Focus Operations Bridge and OMi) is natively delivered via the HPE Operations Agent for Nonstop / OpenView Nonstop Server Management (OVNM). This integration handles faults, performance metrics, and configuration data using specific architectural approaches.
The detailed options for connecting, monitoring, and structuring your HPE NonStop environment within an HPE OVO topology are categorized below.
1. Integration Architectures (Deployment Options)
You can orchestrate how the NonStop kernel feeds events back to your centralized OVO Management Server using two primary pathways:
- Proxy-Based Integration (OVNM): Uses an intermediate Linux or Windows proxy host running the OMi Content Pack and Run-time Service Model (RTSM) package. The proxy communicates directly with NonStop subsystems to capture, translate, and pass along structured event messages (
opcmsg). - Direct Subsystem Forwarding (SNMP/OSM): Configures the native NonStop Open System Management (OSM) suite to output trap diagnostics natively. This path redirects critical events straight to the OVO server via standard SNMP listeners.
2. Event and Message Management
This category dictates how Guardian and OSS-level logs are transformed into actionable alerts on the OVO console.
- EMS (Event Management Service) Interception: Collects real-time events straight from the primary NonStop EMS log distribution system. Filters target specific subsystems (e.g., TMF, Expand, Disk, and Process errors) to generate prioritized OVO messages.
- Logfile Policies: Monitors flat text logs residing on the Open System Services (OSS) POSIX-compliant environment.
- Custom Console Automation Scripting: Employs TACL (Tandem Advanced Command Language) macro integrations to programmaticly build specialized event wrappers. It forwards critical operational telemetry through the
opcmsgservice interface.
3. Performance Metric Integration
Because standard OVO Performance Agent dashboards are not universally supported for real-time visualization of all raw NonStop structures, metrics must be collected through explicit channels:
- Measure Subsystem Extraction: Collects hardware/software performance counters (CPU utilization, queue depths, cache hits) from the native NonStop Measure tool.
- Asynchronous Logging: Writes performance trends to a flat data repository on the system before batch-pushing historical intervals to the OVO server.
- Pathway Monitoring: Evaluates the transaction processing health of the HPE NonStop Pathway middleware. It alerts operators when server pools become bottlenecked or freeze entirely.
4. Smart Plug-Ins (SPIs) & Specialized Add-ons
For automated operations, structural logic is pre-packaged into specialized Smart Plug-ins:
- ASAP SPI (Availability Statistics and Analysis Product): Provides pre-configured thresholds and service population schemes that auto-discover and flag processing availability drops across system elements.
- OMi Content Packs: Deploys targeted management templates, mapping rules, and specific tools configured natively to visually unpack NonStop architectural layouts.
5. Network & Communications Infrastructure
These settings ensure the agent pipeline respects the tight security controls mandatory on fault-tolerant hardware:
- Protocol Options (HTTPS Agent Framework): Manages message distribution across secure, certificate-authenticated HTTPS transport mechanisms.
- Custom Port Configuration: Allows modifying the communication ports using management scripts (e.g.,
ovconfchg) if standard network ports conflict with hard-coded firewalls. - CLIM (Cluster I/O Protocol) Isolation: Collects interface layer logging safely from autonomous IP and Storage CLIMs without breaking the isolation boundaries that protect core system resources.
HPE NonStop integration with HPE OVO options for monitoring
PROject Templates 