Skip to main content
A newer release of this product is available.

network trace start

Contributors
Suggest changes
PDFs

trace start

Availability: This command is available to cluster and Vserver administrators at the admin privilege level.

Description

The network trace start command starts packet tracing with the given parameters. The best practice is to temporarily disable Snapshots on the root volume while the network trace is running.

Parameters

-node {<nodename>|local} - Node Name

Use this parameter to specify the node on which the packet trace should run.

-port {<netport>|<ifgrp>} - Port

Use this parameter to specify the network interface for packet tracing.

[-address <IP Address>] - IP Address

Use this parameter to optionally specify the address for packet tracing.

[-protocol-port <integer>] - Protocol Port Number

Use this parameter to optionally specify the protocol port number for packet tracing.

[-buffer-size <integer>] - Buffer Size in KB

Use this parameter to optionally specify the buffer size for packet tracing. The default buffer size is 4 KB.

[-file-size <integer>] - Trace File Size in MB

Use this parameter to optionally specify the trace file size for packet tracing. The default trace file size is 1 GB.

[-rolling-traces <integer>] - Number of Rolling Trace Files

Use this parameter to optionally specify the number of rolling trace files for packet tracing. The default number of rolling trace files is 2.

Examples

The following example starts packet tracing on node "node1" with address "10.98.16.164", network port "e0c", buffer size "10 KB", and protocol port number "10000":

cluster1::> network trace start -node node1
    -address 10.98.16.164 -port e0c -buffer-size 10 -protocol-port 10000

The following example disables Snapshots on the root volume. Snapshots should be re-enabled after the trace is stopped.

cluster1::> node run -node node1 vol options vol0 nosnap on