User`s guide

Protocol Analyzer
Using the protanal Command
406 5967–9446
Examples The following command creates and arms an instance called crc_errors
on agent lanprobe3, using a filter/settings file called
/home/keith/filters/crc_errors.protanal.settings:
protanal -agent lanprobe3 -arm -instance crc_errors \
-setting /home/keith/filters/crc_errors.protanal.settings
The following command creates and starts an instance called nfs_capt on
agent mickey.nashua.hp.com, using a filter/settings file called
/usr/netm/data/nfsfilter.protanal.settings:
protanal -agent 15.59.144.98 -start \
-instance nfs_capt -setting \
/usr/netm/data/nfsfilter.protanal.setting
–stop
Stops the instance named instname, but does not remove it. Protocol
Analyzer is not launched. For local mode, you can also use the
protanal_kill command.
–remove
Removes the instance named instname, discarding any captured packets
for that instance. Protocol Analyzer is not launched. For local mode, you
can also use the protanal_remove command.
–instance instname
Specifies the instance name to use. If you do not also specify –arm,
–start, –stop, or –remove, Protocol Analyzer launches and attaches to the
instance instname.
–setting settingsfile
Loads the specified settings/filter file. If –arm or –start is specified, the
instance is armed or started with the settings and filter contained in the
file. For information on creating settings/filter files, refer to page 400.
–list
Lists all available instances for the specified agent without launching
Protocol Analyzer. Although this option is valid for local mode, the
protanal_list command gives the same information in more detail.
–datafile tracefile
Launches Protocol Analyzer and loads the specified trace file,
automatically opening a packet decodes window to display the
information contained in the trace.