Method of assigning scan-log dump in a Logical Partition environment.
Original Publication Date: 2002-Jul-12
Included in the Prior Art Database: 2003-Jun-21
Disclosed is a method to manage the assignment of the system's scan-log dump to a logical partition successfully booted its AIX Operating System (OS). The scan-log dump is the data collected by the Converged Service Processor (CSP) during a fatal system failure such as a checkstop or hang . Scan-log dump data contains system chip(s) scan rings, trace arrays, Scan Communication (SCOM) registers, etc.. This data is used by system developers to analyze and solve field problems. The scan-log dump data will be stored in the CSP's local memory. The address of the scan-log dump data is stored in the "scan-log" partition in Non-Volatile Random Access Memory (NVRAM). Whenever there is a checkstop or hang, if the scan-log dump policy is set to "Always" or "As Needed", the CSP generates the scan-log dump and sets the valid byte in NVRAM. Upon reboot, if the valid byte is set, the scan-log open firmware property is set in the device tree which indicates to the Operating System that there is a scan-log dump available. In Logical partitioning (LPAR) mode, multiple Operating Systems will be running in their logical partitions. Only Global firmware and Hypervisor has access to this "scan-log" NVRAM area. The global firmware's partition manager will maintain a flag called "SCANLOG". Its values indicates whether there is any scan-log dump, or the scan-log dump is assigned to a partition, or the scan-log is unassigned. The SCANLOG flag is initialized to "no scanlog" when the Partition Manager's open firmware node is created. Partition Manager queries the CSP for any scan-log dump, and then sets the SCANLOG flag to "scanlog unassigned" before starting any logical partitions.