NFS Performance Tuning for HP-UX 11.0 and 11i Systems

nfs performance tuning for hp-ux 11.0 and 11i systems page 6
Notes:
Page 6July 22, 2002
Copyright 2002 Hewlett- Packard Company
Analyze Network Layout
Familiarize yourself with the physical layout (i.e. how
many network hops separate the client and server?)
Ø OpenView Network Node Manager
Ø traceroute
Ø ping -o
MTU sizes of the various network hops
Ø netstat -in
network
An important early step in troubleshooting any NFS performance issue is to learn
as much as possible about the physical layout of the underlying network topology.
How many network hops (i.e. bridges, hubs, routers, switches, etc.) exist between
the client and the server? What is the speed of each link separating these systems?
Do packets sent from the client to the server take the same route through the
network as the packets sent from the server back to the client?
While the network administrator should be the best source of knowledge about the
layout and capabilities of the underlying network, even they are not always up-to-
date on the current state of the network. In many large corporate environments, the
physical network is constantly evolving as new equipment replaces old, new
backbone technologies replace antiquated ones, new systems are added to
existing networks, new subnets are created, etc. Whenever there is any uncertainty
as to the physical layout of the network separating the NFS clients and servers, a
network layout analysis should be performed.