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.

unique, each offered its own interface to manage and control the Electronic Service Agent<br />

and its functions. Since networks can have different platforms with different operating<br />

systems, administrators had to learn a different interface for each different platform and<br />

operating system in their network. Multiple interfaces added to the burden of administering<br />

the network and reporting problem service information to <strong>IBM</strong> support.<br />

In contrast, Electronic Service Agent 6.1 installs on platforms running different operating<br />

systems. ESA 6.1 offers a consistent interface to reduce the burden of administering a<br />

network with different platforms and operating systems. Your network can have some clients<br />

running the Electronic Service Agent 6.1 product and other clients running the previous<br />

Electronic Service Agent product.<br />

If you have a mixed network of clients running Electronic Service Agent 6.1 and previous<br />

Electronic Service Agent products, you need to refer to the information specific to each<br />

Electronic Service Agent product for instructions on installing and administering that product.<br />

To access Electronic Service Agent user guides, go to the Electronic Services Web site and<br />

select Electronic Service Agent from the left navigation. In the contents pane, select<br />

Reference Guides > Select a platform > Select an Operating System or Software.<br />

Alternatively, you can use the following SMIT fastpath:<br />

smitty esa_main<br />

Further information is available at the following site:<br />

http://publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/eicbd/eicbd_aix.pdf<br />

2.6.2 Other tools for monitoring a system<br />

There are also other tools that are useful for system monitoring; here are a few examples:<br />

► vmstat - Overall system statistics<br />

► netstat - Network statistics<br />

► no - Network tuning<br />

► sar - Overall system statistics<br />

► iostat - Disk and CPU statistics (needs to be enabled to collect statistics)<br />

► lsconf - List and document the machine<br />

► filemon - Find the busy filesystems and files<br />

► fileplace - Check for scrambled files<br />

► lparstat - Check on shared processor LPARs<br />

► perfpmr - Report performance issues<br />

► lvmstat - Check high-use disks<br />

► ioo - Configures I/O tuning parameters<br />

► tuncheck - Validates a tunable file with tunchange, tundefault,tunrestore, and tunsave<br />

commands<br />

You can write shell scripts to perform data reduction on the command output, warn of<br />

performance problems, or record data on the status of a system when a problem is occurring.<br />

For example, a shell script can test the CPU idle percentage for zero (0), a saturated<br />

condition, and execute another shell script for when the CPU-saturated condition occurred.<br />

2.6.3 The topas command<br />

The topas command reports vital statistics about the activity on the local system, such as real<br />

memory size and the number of write system calls. This command uses the curses library to<br />

Chapter 2. <strong>AIX</strong> continuous availability features 49

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

Saved successfully!

Ooh no, something went wrong!