
490 IBM BladeCenter JS23 and JS43 Implementation Guide
from IVM we looked at earlier. This data can also be saved by scrolling to the
bottom of the event log and using the Save Log as Text File button. This data
could then be supplied to service and support for further assistance in error
determination.
Figure 12-24 Event log data details
As mentioned above, it is not the intention of this book to explain troubleshooting
processes for an IBM i partition. For those that are curious about this particular
error, it was created by removing the partition assignment of one of the hdisk
units for the partition.
Typically errors of this type in a pure virtual environment are caused by
configuration changes made by the administrator or others that might not be
familiar with the partition configuration. In our example we just added the drive
back into the configuration using the Modify Partition Assignment options and the
partition recovered. Using IVM you can see the tasks performed by the Monitor
Tasks option. This may provide some indication a configuration change was
made that could have caused the error on the partition. Figure 12-25 on
page 490 shows an example of the Monitor Task option.
Figure 12-25 Monitor tasks
While the task may not specifically indicate what exactly was modified, at least
there is an indication something changed possibly around the time of the
partition error.
Removing and adding drives to IBM i partitions can be disastrous to the partition
and may cause system reload conditions if care is not exercised to follow the
correct processes.
Commenti su questo manuale