Skip to main content

Issues related to the discovery of a BladeCenter and its modules

These topics address issues that are related to the discovery of a BladeCenter and its modules.

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

BladeCenter SNMP settings must also be configured correctly for a BladeCenter to be discovered and monitored correctly. Follow the instructions in the Lenovo XClarity Integrator Hardware Management Pack for Microsoft System Center Operations Manager Users Guide to set up the SNMP settings for the BladeCenter, and use Operations Manager Discovery Wizard to discover the BladeCenter as a network device.

  • A management server with multiple NICs might not reliably discover a BladeCenter if there is more than one network connection between the BladeCenter AMM and the management server

    If a BladeCenter does not appear as a network device in the Operations Manager Console after a discovery, and if the management server for discovery has more than one network connection to reach the BladeCenter AMM, then the discovery will be impacted by an SNMP on multi-NIC binding problem. As a consequence, a discovery of a BladeCenter can be intermittent.

    Workaround: Use only one network connection between the management server and the BladeCenter AMM by either disabling all the other NICs on the management server or using another means to keep the NICs disconnected from the AMM.

  • Full discovery of a BladeCenter requires adequate time

    After the network device discovery for a BladeCenter finishes, it might take up to 2 hours for the BladeCenter module discovery process to begin. Also, it can take up to 6 hours for all of the BladeCenter module discovery processes to finish, for their initial health state to be initialized, and for all the states and properties to fully populate in the Operations Manager Console.

    Workaround: You can override default monitoring interval values to a shorter interval. See the Operations Manager online help for more information about overrides.