Saltar al contenido principal

Issues related to the discovery of a server and its hardware components

These topics address issues that are related to the discovery of a server or its hardware components.

1. It can take several minutes for all of the hardware components to appear in the Operations Manager state views after a managed system is added to Operations Manager​

After a managed system is added to Operations Manager, it can take 3 minutes or longer before the system appears in the Operations Manager Console. It can take up to 6 hours for all of the hardware components and all of the health states to fully populate in Operations Manager.

To limit the CPU demands on the managed systems for hardware health monitoring, Lenovo XClarity Integrator Hardware Management Pack implements a staged discovery of the hardware components in servers. It will take time for a newly added system to complete the initial discovery.

Solutions
In a controlled lab environment, you can override the discovery intervals with a shorter interval (through the Operations Manager Authoring Console) to speed up the process. Note that such overrides should be performed with care to avoid overloading the processor of the managed systems. See the Operations Manager online help for information about overrides.

Another option is to perform manual refreshes in the Operations Manager Console periodically to force the console to catch up with the latest data.

2. Older Systems that have RSA-II without BMC in Director Agent 6.1.x or later have critical alerts with Director Agent's compatibility even if the RSA-II daemon is installed and running​

Director Agent 6.1.x and later does not support systems that have only RSA-II and no BMC. Lenovo XClarity Integrator Hardware Management Pack deliberately raises alerts for systems in this situation even if the RSA daemon is installed and running without problems.

Hardware health of systems in that situation will not be monitored correctly.

Workaround
Use the Director Core Services 5.20.31 for systems that have only RSA-II and no BMC.

3. Hardware components of a certain class of System x systems are not discovered with the Microsoft IPMI driver​

The Microsoft Intelligent Platform Management Interface (IPMI) driver requires a system BIOS to expose the Baseboard Management Controller (BMC) in the designated ACPI namespace for the driver to be able to communicate with the BMC.

For a system with Microsoft IPMI driver running, but not having a BIOS level that exposes the BMC in the designated ACPI namespace, there will be a critical alert that flags the needed BIOS update.

For a list of the latest System x servers that are in this category, see http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=MIGR-5075267.

Workarounds
Do not run these systems with Microsoft IPMI driver. Instead use the OSA IPMI driver.
Note
The OSA IPMI driver is supported on Windows Server 2003 or earlier, but is not supported on Windows 2008 or later. Without a proper IPMI stack, the hardware health of the system will not be available.

4. No power supplies, fans, temperature sensors, or voltage sensors are discovered for blade servers​

In a BladeCenter, power supplies, cooling fans, temperature sensors, and voltage sensors are all shared components of the chassis. Because a blade server itself does not have information that goes beyond the server, there are no instances of power supplies, fans, temperature sensors, or voltage sensors being discovered for a blade server.

Solution
First monitor BladeCenter with the BladeCenter management pack included in Hardware Management Pack and then use the M/T-S/N value of the blade server to locate the corresponding BladeCenter and watch the health conditions of these shared components of BladeCenter.

5. No power supplies are discovered on xSeries 335 systems with Director Core services 5.20.31​

No power supply instances are discovered on xSeries 335 systems with Director Core Services 5.20.31.

Solution/Workaround
None available at this time.

6. No power supplies are discovered on IBMSystem x3755 M3 systems with Director Platform Agent 6.2.1 and later​

No power supply instances are discovered on IBMSystem x3755 M3 systems with Director Platform Agent 6.2.1 and later.

Solution/Workaround
No workaround is available at this time.

7. Some RAID controller names might display as serial numbers instead of readable text​

Instance names for IBM System Storage (ServeRAID-MR, MegaRAID, ServeRAID-BR, or Integrated RAID) might display as a serial number and not in readable text, such as the LSI MegaRAID SAS Adapter. Instead it might display as IBM.500605B000A8F214 in the following views:

  • Instance Detail
  • Health Explorer
  • Alert Source
Solution/Workaround
No workaround is available at this time.

8. Older management controllers (service processors) are not discovered​

Older service processors, including the Advanced Systems Management (ASM) PCI Adapter, the ASM processor (ASMP), and Integrated Systems Management Processor (ISMP) are not discovered by Hardware Management Pack. However, hardware components that these older service processors manage can still be discovered and monitored with a version of Director Agent that supports these configurations (for example, 5.20.31).

Solution
To achieve full coverage of hardware health of your IT infrastructure, upgrade to a newer system equipped with a Baseboard Management Controller (BMC) service processor, Remote Supervisor Adapter (RSA) II, or with the Integrated Management Module (IMM). Also install the latest supported firmware for the management controller.

9. Power capping support limitations on multi-node and multi-instance machines​

The Set Power Capping task in Microsoft System Center Operations Manager does not support multi-node and multi-instance power systems, such as two-node servers and servers with an attached MAX5 memory expansion unit. On multi-node systems, the Set Power Capping task only affects the first or primary node in the system and any related power capping data applies only to the first or primary node.

If you attempt to run the Set Power Capping task on a multi-instance system with an attached MAX5 unit, the task may fail with a generic firmware-based error code of 255. A power cap cannot be set on a system with an attached MAX5 unless the MAX5 is first removed from the server.

10. The value of Power Capping Capable is false although other Power Capping properties such as Power Maximum, Power Minimum, or Power Cap have non-zero values​

The Power Capping Capable property is the only property that indicates whether the server is Power Capping Capable or not. Some servers may provide non-zero values in their Power Capping properties information, such as Power Maximum, Power Minimum, or Power Cap despite the fact that they do not support power capping.

These non-zero values do not indicate that the server is Power Capping Capable. If the Power Capping feature is desired for this server, review the "Installing IBM Power CIM Provider" and "Troubleshooting" sections of the Lenovo XClarity Integrator Hardware Management Pack for Microsoft System Center Operations Manager Installation and User's Guide.

11. The value of Power Maximum, Power Minimum, or Power Cap are zero​

Sometimes Lenovo XClarity Integrator Hardware Management Pack cannot collect the correct Power Capping properties due to an exception of the IBM Power CIM Provider on a managed server.

Solution/workaround
If the Power Capping feature is required for a server, complete the following applicable steps to resolve this issue.
  • Reboot the managed server.
  • If rebooting the managed server does not work, see the "Installing IBM Power CIM Provider" and "Troubleshooting" sections of the Lenovo XClarity Integrator Hardware Management Pack for Microsoft System Center Operations Manager Installation and User's Guide.

12. The Set Power Capping task does not work in the SCOM console​

The Set Power Capping task might fail because the PowerCapping option is not enabled. The following message is displayed: ERROR - Failed to enable Power Capping.

Solution/Workaround
Complete these steps.
  1. When trying to enable PowerCapping, verify the Pcap value is between Pmax and Pmin.
  2. Reboot the managed server.
  3. Reinstall the IBM Power CIM Provider on the managed server.

If after completing these steps the PowerCapping task still does not work, refer to the "Troubleshooting" section in Lenovo XClarity Integrator Hardware Management Pack for Microsoft System Center Operations Manager Installation and User's Guide to set the value manually.