IBM-SVC-MIB

Description: IBM MIB for the IBM SAN Volume Controller (SVC) providing storage virtualization status, volume, and node management.

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.

IBM-SVC-MIB defines the private MIB extensions for the IBM SAN Volume Controller (SVC, formerly known internally as TSVE), a storage virtualization appliance that sits between hosts and physical storage arrays in a SAN. This module is used specifically to receive traps from the SVC rather than for general polling, so its objects primarily carry fault and identity information bundled into notifications. Its monitoring focus is squarely on hardware/software fault reporting: tsveERRI and tsveERRC carry error identifiers/codes, tsveERRS gives an error string, tsveSWVE reports the software version, tsveFRUP identifies the affected Field Replaceable Unit, and tsveMACH/tsveSERI/tsveCLUS/tsveNODE identify the machine type, serial number, cluster, and node involved in the event — together letting an admin pinpoint exactly which SVC node/cluster/component failed and why. tsveTIME timestamps each reported event for correlation with other logs. As an IBM storage MIB it is deployed on IBM SAN Volume Controller clusters within SAN-based storage virtualization environments, and it depends on IBM's broader storage enterprise MIB tree (ibmProd) for its OID placement. Engineers can download the IBM-SVC-MIB file directly to load it into their MIB browser.

A management station would receive SNMP traps carrying tsveERRI and tsveERRC to identify the specific error condition on the SVC, alongside tsveERRS for a readable description, tsveFRUP naming the failed field-replaceable unit (e.g., a specific node canister or battery), and tsveCLUS/tsveNODE identifying which cluster and node in the SVC generated the alert. tsveMACH and tsveSERI would be checked to confirm the exact hardware machine type and serial number affected, while tsveSWVE reveals the SVC software version running at the time, useful when correlating a fault with a known firmware bug. tsveTIME provides the event timestamp for cross-referencing against other storage or SAN fabric logs.

IBM enterprise SNMP MIB module that defines managed objects for IBM SAN Volume Controller (SVC) systems, enabling reception and processing of SNMP traps and notifications from IBM Storage Virtualize Systems.