Issues related to the health monitoring of a BladeCenter

These topics address issues that are related to the health monitoring of a BladeCenter.

It is essential to have the latest firmware level for BladeCenter Advanced Management Module (AMM). If you have an outdated firmware level for the AMM, this can prevent getting all the health states needed. For information about upgrading AMM firmware, see http://pic.dhe.ibm.com/infocenter/director/v5r2/index.jsp?topic=/bofm_1.00/ btp0_bofm_t_upgrading_firmware.html.

For a BladeCenter to be monitored correctly, the BladeCenter SNMP settings must be configured correctly. Review the settings by referring to the instructions in the Lenovo XClarity Integrator Hardware Management Pack for Microsoft System Center Operations Manager Users Guide about specifying the BladeCenter SNMP settings.

• Operations Manager 2007 cannot receive SNMP trap data on Windows Server 2008

  If you can discover a BladeCenter successfully with an Operations Manager management server running Windows Server 2008, SNMP traps from the BladeCenter might not propagate to Operations Manager unless a specific fix pack available for Systems Center Operations Manager 2007 has been installed.

  For more information, see: Microsoft Support – System Center Operations Manager 2007 cannot receive SNMP trap data when you use a Windows Server 2008-based computer or a Windows Vista-based computer as a proxy agent for SNMP devices Web site.

  Workaround: Install the fix pack for Windows Server 2008 on the Operations Manager management server designated to manage the BladeCenter.

• A critical "SNMP Trap Generated Alert" is reported for each BladeCenter event regardless of its severity, if Microsoft's Network Device Monitoring Library is imported

  Microsoft System Center Network Device Monitoring Library management pack for System Center Essentials 2007, treats every SNMP trap it receives as a critical error and does not capture enough relevant data from the SNMP trap. This management pack does not manage a BladeCenter and can confuse IT administrators.

  Workaround: Delete the Network Device Monitoring Library management pack from Operations Manager.

• BladeCenter storage modules are not monitored

  BladeCenter storage modules are not monitored with Lenovo XClarity Integrator Hardware Management Pack.

  Workaround: To manage the BladeCenter storage modules and their disk drives, use the RAID SAS Switch Module (RSSM) in the BladeCenter.

• Removing the primary management module in a BladeCenter does not generate an alert to Operations Manager

  The primary management module of a BladeCenter cannot generate an alert to Operations Manager when it is removed physically from the BladeCenter, because the original connection to its Operations Manager management server no longer exists.

  Note

  The standby management module must have a different IP address from the primary management module.

  Workaround: Configure Operations Manager to monitor the standby management module in addition to the primary management module. Although you will miss the event of the primary management module removal, you can maintain full coverage of health monitoring of the BladeCenter. You must temporarily make the standby management module the active management module when adding the BladeCenter to be managed through the standby management module.

• BladeCenter multi-slot wide blades are reported as single-slot wide

  If the AMM of a BladeCenter is running at the firmware level BPET50C, the BladeCenter multi-slot wide blades are reported as single-slot width.

  Workaround: Either upgrade the AMM firmware to level BPET54D or later version, or downgrade to level BPET48N. See http://pic.dhe.ibm.com/infocenter/director/v5r2/index.jsp?topic=/bofm_1.00/ btp0_bofm_t_upgrading_firmware.html.

• BladeCenter Media Module reports empty values for the part number and serial number of the Media Tray

  The BladeCenter Media Module reports empty values for the part number and serial number of the Media Tray.

  Workaround: Upgrade the AMM firmware to the latest firmware level. See http://pic.dhe.ibm.com/infocenter/director/v5r2/index.jsp?topic=/bofm_1.00/ btp0_bofm_t_upgrading_firmware.html.

• BladeCenter might not send out all of the SNMP traps when the AMM is overloaded

  There are extreme conditions that might cause the AMM of a BladeCenter to be overloaded, making it unable to send out all of the SNMP traps required for Hardware Management Pack to report to Operations Manager.

  Note

  Such cases of extreme activity are rare and occur only in extreme conditions such as a catastrophic failure of all the components in a BladeCenter chassis.

• BladeCenter Media Module might indicate "Not available" for its module name for a period of time

  The module name of a BladeCenter Media Module is gathered on a timed interval basis. Because the alert source for a Media Module is the module name, the alert source for a newly inserted Media Module might be displayed as Not available for alerts that occur in the time between the insertion of the module and the time the module name is gathered during the next interval.

  Workaround: No workaround is available at this time.