Specifications

© 2006 Cisco Systems, Inc.
All rights reserved.
Product Features 2-166
NAM / Traffic Analyzer v3.5 Tutorial
© 2006 Cisco Systems, Inc. All rights reserved.
Product Features 2-166
NAM / Traffic Analyzer v3.5 Tutorial
Packet Capture and Decode
Defining Remote Data Storage (NFS)
Packet Capture and Decode
Defining Remote Data Storage (NFS)
Name to define the remote
data storage. Name is used
to select the disk in the GUI
Name to define the remote
data storage. Name is used
to select the disk in the GUI
Server where the remote disk
is located and the directory to
hold the captured packet file
Server where the remote disk
is located and the directory to
hold the captured packet file
NFS Options to define the
transfer protocol, timeout, and
retry values
NFS Options to define the
transfer protocol, timeout, and
retry values
Server where the remote disk
is located and the directory to
hold the captured packet file
Server where the remote disk
is located and the directory to
hold the captured packet file
NOTE: The NFS server must be able to
grant access to the NAM in order to write to
the disk (see notes on procedure)
NOTE: The NFS server must be able to
grant access to the NAM in order to write to
the disk (see notes on procedure)
Defining Remote Data Storage (NFS)
To use a NFS remote disk, click the Create NFS button to define it. Provide a name for the disk (in order to
identify it in the NAM user interface), enter the hostname of the server that has the remote disk, and provide
the directory as to where the capture files should be located.
Note(s):
The NFS server must be configured to grant read and write access to the NAM in order for the NAM to
be able to store capture files on it. The following example shows how to set up an NFS directory
(/home/SomeUserName) on a Linux server for a NAM (at IP address 1.1.1.2) to store capture data.
Locate a UID that has read and write access to the target NFS directory.
For example, if the target NFS directory is /home/SomeUserName, open the /etc/password
file and search for a user entry that contains something like the following:
SomeUserName:x:503:503::/home/SomeUserName:/bin/tcsh
In this example, the UID is 503.
Edit the /etc/exports file and add a line like the following:
/home/SomeUserName 1.1.1.2/255.255.255.255(rw,all_squash,anonuid=503)
Activate the change: type: /usr/bin/exportfs -a
If the NFS directory contains subdirectories that are not writable by the NAM, these subdirectories will
not be listed in NAM capture screens.