root 3801210 3866772 0 Oct 04 -
0:00 /usr/sbin/hostmibd
root 3866772 1 0 Oct 04 -
0:00 /usr/sbin/srcmstr root 3932286 3866772
0 Oct 04 - 0:0
0 /usr/sbin/portmap
root 3997832 3866772 0 Oct 04 -
0:00 /usr/sbin/aixmibd
root 4063420 1 0 Oct 04 -
0:44 /usr/sbin/getty /dev/consol
e
root 4128936 3866772 0 Oct 04 -
0:03 sendmail: accepting connect
ions
root 4259980 3866772 0 Oct 04 -
0:00 /usr/sbin/snmpmibd
root 4325556 1 0 Oct 04 -
0:02 /usr/sbin/cron
root 4391124 3866772 0 Oct 04 -
0:03 /usr/sbin/rsct/bin/vac8/IBM.
CSMAgentRMd
root 4522176 1 0 Oct 04 -
0:00 /usr/bin/dsmcad
root 4718774 3866772 0 Oct 04 -
0:00 /usr/sbin/rpc.lockd -d 0
root 4784284 2424972 0 Oct 04 -
1:10 xmtopas -p3
root 4980888 3866772 0 Oct 04 -
0:00 /usr/sbin/biod 6
root 5177506 3866772 0 Oct 04 -
0:00 /usr/sbin/nfsd 3891
root 5243046 3866772 0 Oct 04 -
0:00 /usr/sbin/rpc.mountd
root 5439672 3866772 0 Oct 04 -
0:04 /usr/sbin/rsct/bin/rmcd -a IBM.
LPCommands -r
root 5570560 1 0 Oct 04 -
0:00 bin/nonstop_aix @config/nonstop.
properties
root 5701822 2097342 208 Oct 04 -
938:56 dsmserv quiet
root 5832888 1 0 Oct 04 -
0:02 /usr/local/sbin/sshd
root 5898436 3866772 0 Oct 04 -
0:00 /usr/sbin/qdaemon
root 5963972 1 0 Oct 04 -
0:00 /usr/sbin/uprintfd
root 6095040 3866772 0 Oct 04 -
0:00 /usr/sbin/writesrv
root 6160590 3866772 0 Oct 04 -
0:08 /usr/sbin/pcmsrv
root 6291682 3866772 0 Oct 04 -
0:00 /usr/sbin/rsct/bin/IBM.DRMd
the server rather than across the network. You can run
the application from the console and see if the response
time is similar to when you connect across the network.
If the application uses a client/server model, you can do
some basic testing from the client using ping server_IP_
address (see Listing 8).
Listing 8. Ping by IP address
ping 192.168.168.30PING 192.168.168.30:
(192.168.168.30): 56 data bytes
64 bytes from 192.168.168.30: icmp_seq=0 ttl=255
time=0 ms
64 bytes from 192.168.168.30: icmp_seq=1 ttl=255
time=0 ms
64 bytes from 192.168.168.30: icmp_seq=2 ttl=255
time=0 ms
64 bytes from 192.168.168.30: icmp_seq=3 ttl=255
time=0 ms
----192.168.168.30 PING Statistics----
4 packets transmitted, 4 packets received, 0%
packet loss
round-trip min/avg/max = 0/0/0 ms
A ping by IP address can help identify if the issue is
related to Domain Name System (DNS) configuration. If
you suspect network problems, a diagram or description
of the network configuration is a useful starting point.
What vendor applications are involved?
It is important to know what vendor applications are
used on a system that is performing poorly. Often there
are operating system tunables, recommended kernel
settings, and other environmental variables that you
should use for some applications. There also may be
patches for the application that fix known performance
issues. You should know what version/release/level of the
vendor application is installed and if the application has
been updated recently.
General advice
The perfpmr documentation recommends providing
a clear written statement of a simple specific instance
of the problem. It also recommends separating the
symptoms and facts from theories, ideas, and your
own conclusions. As the documentation says, “If all the
facts are available, the performance team can quickly
eliminate the unrelated ones.”
Another piece of advice is to ensure the correct machine
is being used for information gathering. In large sites—
and especially with so many virtualized environments—
it can be easy to collect data from the wrong system.
As the documentation says, “This makes it very hard to
investigate the problem.”
To identify the machine model and serial number, you
can use the lsconf command.
