I think what you are looking for is a packet trace. Here's the command:

fas6070a*> pktt
Usage: pktt start   <if>|all [-d dir] [-m pklen] [-b bsize] [-i ipaddr -i ...]
       pktt pause   <if>|all
       pktt dump   [<if>|all [-d dir]] | [<if> [-f file]]
       pktt stop    <if>|all
       pktt status [<if>|all] [-v]
       pktt delete [filename.trc]+
       pktt list
fas6070a*>

{do the network connecction that you want to trace; try to be quick so that you don't have so much traffic to analyze.)

The file will be created at the root of the root volume. (or you can specify the directory to write the file with the -d option)

You can read the file with Ethereal or any packet trace analyzer.

Would like to know if this works for you!

From: Pazder, Steve B [mailto:Steve.B.Pazder@dynegy.com]
Sent: Tuesday, April 24, 2007 9:38 AM
To: toasters@mathworks.com
Subject: network troubleshooting

Our Network admin has been working with Cisco to troubleshoot some issues (limited to 1 switch on 1 particular floor). While our Filers are not involved in this issue, fingers are generally pointed in that direction just because they exist....on the network. Our network admin is looking for information from the Filers that would be akin to a TCP dump. Ifstat, netstat and statit output are not providing the information being looked for (handshake info, etc). I haven't run across this particular issue before and don't recall ever seeing it presented to Toasters. Does anyone know of a way to get the actual communication dumps (again, a TCP dump) from a Filer?