Filter
Top Products
Chapter 2 NAS Head 2-135
3. At the CLI, enter “load netm”. Then type “menu” to configure capture and capture
packets.
4. Press the spacebar until “Packet Capture” is displayed under “Extensions” at the
lower right.
5. Select the letter corresponding to “Packet Capture”.
6. Select option “1”, Edit Fields.
The available options are as follows:
■ Capture File - Where to save the capture file.
</volumename/directory/filename>
■ Frame Size (B) - Size in bytes of each frame to capture. The default is normally
used.
■ IP Packet Filter - “No” captures all traffic, “Yes” allows you to filter what is
received. A filter allows you to select which IP address or addresses you will
capture traffic from. You can also filter on a particular TCP or UDP port.
■ Dump Enable - Select “Yes” to allow StorEdge to save the capture in the event of
a problem.
7. After configuring these options, select option “7”, “Start Capturing”
8. Reproduce the network event you wish to capture.
9. Select option “7”, “Stop Capture”.
10. Access the file via NFS or SMB and copy the file as needed.
How do I access command history at the CLI?
When typing commands at the CLI, it is sometimes desirable to access previously
typed commands. StorEdge has several command history options available. Note
that the CLI does not provide Unicode support. The features described here are
intended for use with ASCII characters only.
1. To access the StorEdge CLI, connect to the StorEdge via Telnet or serial console.
2. Type “admin” at the [menu] prompt and enter the administrator password.
The history list contains a maximum of 32 entries and will be saved to
/cvol/log/history whenever the exit or quit commands are issued. The contents of
/cvol/log/history will be read on boot. The shell built-in history command can be
used to display a numbered list of previously executed commands. Previous
commands can be executed by entering “!nn” at the CLI, where nn is the entry
number. The history command is not displayed in the help list.