IBM Systems Group

© 2005 IBM Corporation

This presentation is intended for the education of IBM and Business Partner sales personnel. It should not be distributed to customers.

IBM Director 5.10Topic : Improved Hardware Alerting (xSeries)

Presenter’s Name : Rajat Jain (rjain@us.ibm.com)and Title

IBM Systems Group

© 2005 IBM Corporationpage 2IBM Systems Group Field Skills & Education

Basic Overview

Provide alerts for problems that occurred during POST

Provide FRU numbers in Alerts

Send a CIM Director alert when an ASR takes place

Differentiate between normal and recovery alerts

IBM Systems Group

© 2005 IBM Corporationpage 3IBM Systems Group Field Skills & Education

Provide Alerts for problems that occurred during POST

Original requirement was to notify that system was running with disabled or non-functioning CPUs.

Additional enhancement was made to monitor system’s physical memory as well.

Details provided on following slides…..

IBM Systems Group

© 2005 IBM Corporationpage 4IBM Systems Group Field Skills & Education

Report CPU problems that may have occurred during POST

Upon every system restart, last known configuration for the number of CPUs is compared with the current. (CPU speed is used as an index)

Alerts are generated for a degraded configuration. Detail is provided for the number of missing/disabled CPUs.

Special cases :– If configuration is enhanced (e.g. addition of CPUs), then a

“normal” alert is generated for the first time only.– On scalable systems, an alert would be generated every time a

partition is re-configured. For example, either CPUs are added to a partition, or removed.

IBM Systems Group

© 2005 IBM Corporationpage 5IBM Systems Group Field Skills & Education

Report Physical Memory problems that may have occurred during POST

Upon every system restart, last known configuration for the physical memory size is compared with the current.

Alerts are generated for a degraded configuration. Detail is provided for the reduced memory size and the FRU Part # of the memory DIMM.

Special cases :– If configuration is enhanced (e.g. addition of DIMMs), then a

“normal” alert is generated for the first time only.– If memory DIMMs are replaced or reconfigured to provide same

size, then no alert is generated. For example, replacing two 256MB DIMMs with one 512 MB DIMM would not generate an alert.

– On scalable systems, an alert would be generated every time a partition is re-configured. For example, either DIMMs are added to a partition, or removed.

No support for Hot swap memory.

IBM Systems Group

© 2005 IBM Corporationpage 6IBM Systems Group Field Skills & Education

Screen Captures

IBM Systems Group

© 2005 IBM Corporationpage 7IBM Systems Group Field Skills & Education

Provide FRU numbers in AlertsThe FRU number shall be included in the Alert text for the CIM

events associated with the following components :

– Power Supply alerts for RSA and IPMI systems– DASD backplane alerts for RSA and IPMI systems – Memory alerts (configuration downgraded or PFA) for any system

where the getfru utility returns a FRU part # for memory.

Agents like DSA/ESA can parse the event text for the delimiters %FRU:1234567%

Sample screen captures provided on following page

IBM Systems Group

© 2005 IBM Corporationpage 8IBM Systems Group Field Skills & Education

IBM Systems Group

© 2005 IBM Corporationpage 9IBM Systems Group Field Skills & Education

IBM Systems Group

© 2005 IBM Corporationpage 10IBM Systems Group Field Skills & Education

Send a CIM Director alert when an ASR takes placeIf an Automatic Server Restart occurs on an IPMI system with

a BMC (e.g. x346, x236, x336, x366), then CIM Alerts are generated upon the next restart of the server.

– Warning - The last system restart was due to the automatic server restart hardware.

– Normal/Recovery - The last system restart was not due to the automatic server restart hardware.

Recovery shall only be possible upon the next system reboot.

IBM Systems Group

© 2005 IBM Corporationpage 11IBM Systems Group Field Skills & Education

Differentiate between normal and recovery alerts

The original requirement was mainly for eliminating redundant normal alerts upon Director agent reboots.

Additional enhancements have been made :– Also consider inband hardware alerts with all severities (warning and

criticals too). – Basically, do not re-report an alert (regardless of the severity), if it has

already been reported before, and the severity state is unchanged.Persistent across rebootsIncludes all inband hardware alertsIf a new hardware component is added, only failures are

reported during the first scan of the component.– Example : Add a new Power Supply, if it is normal, no alerts are

generated.

IBM Systems Group

© 2005 IBM Corporationpage 12IBM Systems Group Field Skills & Education

List of systems / hardware types that are affected

IBM Systems Group

© 2005 IBM Corporationpage 13IBM Systems Group Field Skills & Education

IBM Systems Group

© 2005 IBM Corporationpage 14IBM Systems Group Field Skills & Education

Debugging Tips & Common Pitfalls

IBM Systems Group

© 2005 IBM Corporationpage 15IBM Systems Group Field Skills & Education

List of Known Issues

IBM Systems Group

© 2005 IBM Corporationpage 16IBM Systems Group Field Skills & Education

Questions & Answers