SNI-NT-CLUSTER-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SNI-NT-CLUSTER-MIB

Category: Server and Host Management, Siemens Nixdorf Server Management

Description: Manages Siemens Nixdorf Windows NT cluster node status, resource groups, and failover configuration.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is SNI-NT-CLUSTER-MIB?

SNI-NT-CLUSTER-MIB is a Siemens Nixdorf (later Fujitsu Siemens) enterprise MIB for monitoring Microsoft Cluster Server (MSCS)-based Windows NT server clusters running on SNI server hardware. It exposes cluster identity and version data along with the operational state of the cluster service itself, plus quorum-resource identification used to determine which node currently owns the cluster. Its monitoring focus is software/service availability of the cluster: sniWpAgentClusterServiceState reveals whether the cluster service on a node is running, stopped, or in an error state, and the quorum-resource fields let an admin confirm which physical resource is acting as the tie-breaker, both critical for diagnosing a failover or split-brain condition. It depends on the underlying Microsoft Cluster Server architecture for the concepts it surfaces, translated into an SNI-proprietary MIB rather than a Microsoft-standard one. It was deployed on Siemens Nixdorf/Fujitsu Siemens Windows NT server clusters in enterprise environments requiring high-availability failover, where SNI-NT-CLUSTER-MIB SNMP monitoring supplemented native Windows cluster administration tools with visibility into cluster health.

IPNetwork Monitor allows you to monitor SNMP objects defined in SNI-NT-CLUSTER-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Siemens Nixdorf / Fujitsu Siemens Windows NT server cluster node

Monitoring Examples

An admin would poll sniWpAgentClusterServiceState on each node to confirm the cluster service is running before assuming automatic failover will work, and check sniWpClusterQuorumResourceName/sniWpClusterQuorumResourceDevice to verify the quorum disk resource is correctly identified. A node reporting a non-running cluster service state while its peer is healthy would indicate that node has dropped out of the cluster and needs investigation.

What Can Be Monitored

  • cluster service operational state
  • quorum resource identity
  • cluster name/version/build
  • agent version
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

IpAddress
enterprises

From RFC1213-MIB

DisplayString
mib-2

From SNI-TRAP-MIB

sniServerNameOBJECT-TYPE
sniTrapTimeOBJECT-TYPE
OIDs

RFC description

Provides read-only monitoring of Microsoft Wolfpack cluster API including nodes, groups, resources, and network interfaces.

Start monitoring Siemens Nixdorf / Fujitsu Siemens Windows NT server cluster node (MSCS cluster service/quorum status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SNI-NT-CLUSTER-MIB