Alert monitor for IBM BladeCenter SAS I/O zoning problems
This monitor watches for a BladeCenter event that indicates that an I/O module does not have the same active zone configuration that another I/O module has.
You can disable this monitor through the Operations Manager's Operations Console. See the "Disable monitors" topic in the Operations Manager's Operations User's Guide for more information.
The BladeCenter event is delivered to this monitor asynchronously. There is no monitoring interval to configure for this monitor.
The BladeCenter event is delivered to this monitor from the AMM (Advanced Management Module) of the BladeCenter via the SNMP (Simple Network Management Protocol) protocol. It also goes through the BladeCenter runtime support of the Hardware Management Pack installed on the management server that was designated to manage the BladeCenter during the Network Device Discovery process.
For the proper BladeCenter AMM SNMP settings that are required for the Hardware Management Pack to discover BladeCenter modules and report events, consult the Hardware Management Pack's User's Guide.
All I/O modules in the chassis must have the same active zone configuration. When an I/O module does not have the same active zone configuration that another I/O module has, the BladeCenter's AMM generates a hardware event. The health state of this monitor is then set to the Critical or Warning state.
For a particular incident, review the history in the State Changes tab. Consult the relevant hardware knowledge articles listed below, keeping in mind the relevant event data.
The relevant IBM hardware knowledge articles are available on a system with the IBM Hardware Management Pack package installed.
Active zone pointers
I/O Module "Instance Number"'s current user defined zone configuration was not activated since the zone configuration was not created for this chassis
Setting of the active zone configuration number failed for I/O Module "Instance Number"
All zoning has been disabled for I/O Module "Instance Number"
I/O Module "Instance Number" has no active zone configuration since neither the AMM nor the I/O Module have an active zone configuration
The "Instance Number" can be found as the numeric part of the name/description for an alert or event, and it reflects the number of the bay/module. For instance, "I/O Module [Instance Number]'s current user defined zone configuration was not activated since the zone configuration was not created for this chassis" could actually mean "I/O Module 01's current user defined zone configuration was not activated since the zone configuration was not created for this chassis".
Review the relevant IBM hardware knowledge articles listed above for information about how to resolve the hardware problem for a particular incident.
When the I/O module doesn't have the same active zone configuration that another I/O module has, the monitor generates an alert when its health state changes to either Critical or Warning. After the active zone configuration issue is resolved, manually reset the health state of this monitor. See the "Reset Health" topic in the Operations Manager's Operations User's Guide for more information. Any outstanding corresponding alerts will be automatically closed when the health state of this monitor returns to the Healthy state.
For the proper AMM SNMP settings needed for the Hardware Management Pack, see the "Configuring BladeCenter SNMP settings" topic in the IBM Hardware Management Pack for Microsoft System Center Operations Manager Installation and User's Guide.
Links to IBM resources
Target | IBM.BladeCenter.IOModule | ||
Parent Monitor | System.Health.ConfigurationState | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | IBM.BladeCenter.SNMPTrap.3StateMonitorTypeForModule | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="IBM.BladeCenter.IOZoning.Failed" Accessibility="Public" Enabled="true" Target="IBM.BladeCenter.IOModule" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="IBM.BladeCenter.SNMPTrap.3StateMonitorTypeForModule" ConfirmDelivery="false">
<Category>Custom</Category>
<AlertSettings AlertMessage="IBM.BladeCenter.IOZoning.Failed.AlertMessageID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/SnmpVarBinds/SnmpVarBind[OID='1.3.6.1.4.1.2.6.158.3.1.1.8'][1]/Value$</AlertParameter1>
<AlertParameter2>$Data/Context/SnmpVarBinds/SnmpVarBind[OID='1.3.6.1.4.1.2.6.158.3.1.1.14'][1]/Value$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="ComponentSuccess" MonitorTypeStateID="SuccessEventRaised" HealthState="Success"/>
<OperationalState ID="ComponentWarning" MonitorTypeStateID="WarningEventRaised" HealthState="Warning"/>
<OperationalState ID="ComponentError" MonitorTypeStateID="ErrorEventRaised" HealthState="Error"/>
</OperationalStates>
<Configuration>
<EventIds>24542438[5-9]|24542439[0-4]|24542464[1-9]|245424650|24543104[1-9]|245431050|24543129[7-9]|24543130[0-6]|24543206[5-9]|24543207[0-4]</EventIds>
</Configuration>
</UnitMonitor>