11.01.2013 Views

IBM AIX Continuous Availability Features - IBM Redbooks

IBM AIX Continuous Availability Features - IBM Redbooks

IBM AIX Continuous Availability Features - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

To access the SMIT FFDC menu, use the fastpath smitty ffdc. The menu is shown in<br />

Example 3-1.<br />

Example 3-1 Advanced FFDC features<br />

Advanced First Failure Data Capture <strong>Features</strong><br />

Type or select values in entry fields.<br />

Press Enter AFTER making all desired changes.<br />

[Entry Fields]<br />

Advanced First Failure Data Capture <strong>Features</strong> [enabled] +<br />

Run bosboot automatically [no] +<br />

F1=Help F2=Refresh F3=Cancel F4=List<br />

F5=Reset F6=Command F7=Edit F8=Image<br />

F9=Shell F10=Exit Enter=Do<br />

For more information about FFDC, refer to <strong>IBM</strong> eServer p5 590 and 595 System Handbook,<br />

SG24-9119.<br />

3.2 Lightweight memory trace<br />

This section describes how to use lightweight memory trace (LMT). Lightweight memory trace<br />

is a serviceability feature. It is an important first failure data capture tool, and is most useful to<br />

those with <strong>AIX</strong> source-code access or a deep understanding of <strong>AIX</strong> internals.<br />

3.2.1 LMT implementation<br />

As mentioned, Lightweight memory trace (LMT) provides trace information for First Failure<br />

Data Capture (FFDC). It is a constant kernel trace mechanism that records software events<br />

occurring during system life. The system activates LMT at initialization, and then it runs<br />

continuously. Recorded events are saved to per-processor memory trace buffers.<br />

There are two memory trace buffers for each processor: one to record common events, and<br />

one to record rare events. These buffers can be extracted from system dumps or accessed<br />

on a live system by service personnel using the mtrcsave command. The extracted memory<br />

trace buffers can be viewed by using the trcrpt command, with formatting as defined in the<br />

/etc/trcfmt file.<br />

LMT has been carefully implemented such that it has negligible performance impacts. The<br />

impact on the throughput of a kernel-intensive benchmark is just 1%, and is much less for<br />

typical user workloads. LMT requires the consumption of a small amount of pinned kernel<br />

memory. The default amount of memory required for the trace buffers is calculated based on<br />

factors that influence trace record retention.<br />

Lightweight memory trace differs from traditional <strong>AIX</strong> system trace in several ways. First, it is<br />

more efficient. Second, it is enabled by default, and has been explicitly tuned as a First<br />

Failure Data Capture mechanism. Unlike traditional <strong>AIX</strong> system trace, you cannot selectively<br />

record only certain <strong>AIX</strong> trace hook ids with LMT. With LMT, you either record all LMT-enabled<br />

hooks, or you record none.<br />

Chapter 3. <strong>AIX</strong> advanced continuous availability tools and features 57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!