Displaying DAFS status

About displaying DAFS status

To display the status of the DAFS service, NICs, and sessions, you use the dafs status command. The command syntax and functions provided are as follows:

The dafs status -v command displays in detail the state of the DAFS service.
The dafs status -vn command displays the details about the VI NICs associated with the DAFS service.
The dafs status -n command displays a list of all VI NICs associated with the DAFS service and their current states.
The dafs status -sn command displays the state of all sessions associated with VI NICs that use the DAFS service.
The dafs status -sr command displays the state of the DAFS service, basic information for client sessions, and current DAFS requests.
The dafs status -sv command displays the state of the DAFS service and details of the client sessions.
The dafs status -a command displays the state of the DAFS service, VI NIC status, and client session status.

For more information, see the na_dafs(1) man page.

Displaying the state of DAFS service

To display in detail the state of the DAFS service, complete the following step.

Step	Action
1	At the filer command line, enter the following command: dafs status -v Result The display shows the details (verbose option) of the state of the DAFS service for server sessions, server requests, and data transfers. Example: filer> dafs status -v DAFS service is started Sessions: 2, disconnected: 0, max disconnected: 32 Server Requests: curr: 0, limit: 4096, pend: 0, max pend: 128 Max requests per session: 1024, NICs active: 1 Bytes in: 2668, bytes out: 10964 Direct bytes in: 0, direct bytes out: 0

Step

Action

At the filer command line, enter the following command:

dafs status -v

Result

The display shows the details (verbose option) of the state of the DAFS service for server sessions, server requests, and data transfers.

Example:

filer> dafs status -v

DAFS service is started

Sessions: 2, disconnected: 0, max disconnected: 32 
Server Requests: curr: 0, limit: 4096, pend: 0, max   
pend: 128

Max requests per session: 1024, NICs active: 1

Bytes in: 2668, bytes out: 10964

Direct bytes in: 0, direct bytes out: 0

Explanation of dafs status -v output

The dafs status -v command displays the following output:

State of the DAFS service
Current number of sessions
Number of disconnected sessions
Maximum number of disconnected sessions

The server request information shows the following:

Current number of requests being processed
Current limit on dispatching new requests
Number of pending requests due to limit restriction
Maximum limit of pending requests
Maximum number of requests that a session can have at one time
Note
The dispatch limit on starting new requests prevents DAFS from overloading the filer. Requests are pended if they cannot be dispatched.
Number of attached VI NICs

The data transfer information shows the following:

Count of bytes in and out of the filer.
Count of direct bytes in and out of the filer. Direct bytes are RDMA transfers.

Displaying detailed status of VI NICs

To display detailed status for all VI NICs associated with the DAFS service, complete the following step.

Step	Action
1	At the filer command line, enter the following command: dafs status -vn Result The display shows the details about all the VI NICs associated with the DAFS service. This command is useful for checking VI NIC IP addresses and verifying whether the NICs are attached to the DAFS service. Note If you have multiple VI NICs and want to view the same level of detail status for one specific NIC, enter the following command: `dafs status -vn vinic` vinic is a VI NIC network interface name, for example, `dafs status -vn e5` Example filer> dafs status -vn DAFS service is started NIC: e4 Device: e4 State: ATTACHED Listen Address: 10.40.132.109:DAFS Requests in: 27 Bytes in: 2668, bytes out: 10964 Direct bytes in: 0, direct bytes out: 0 Request daemons: 2 Descriptor Cache: T:2, S:2, M:0, L:0, RM:0 Cache Hit/Miss: T:24/2, S:5/8, M:2/2, L:0/0 RM:0/0 Send pending highwater: 1, limit: 921 Request flowcontrol: 0, flowcontrol timeout: 0

Step

Action

At the filer command line, enter the following command:

dafs status -vn

Result

The display shows the details about all the VI NICs associated with the DAFS service. This command is useful for checking VI NIC IP addresses and verifying whether the NICs are attached to the DAFS service.

Note
If you have multiple VI NICs and want to view the same level of detail status for one specific NIC, enter the following command:

dafs status -vn vinic
vinic is a VI NIC network interface name, for example,
dafs status -vn e5

Example

filer> dafs status -vn

DAFS service is started

NIC: e4         Device: e4              State: ATTACHED

Listen Address: 10.40.132.109:DAFS

  Requests in: 27

  Bytes in: 2668, bytes out: 10964

  Direct bytes in: 0, direct bytes out: 0

  Request daemons: 2

  Descriptor Cache: T:2, S:2, M:0, L:0, RM:0

  Cache Hit/Miss: T:24/2, S:5/8, M:2/2, L:0/0 RM:0/0

  Send pending highwater: 1, limit: 921

  Request flowcontrol: 0, flowcontrol timeout: 0

Explanation of dafs status -vn output

The dafs status -vn command displays the following output:

NIC transport information--Specifies the listen address
Data transfer information--Requests in, bytes in and out, direct bytes in and out, and request daemons
Cache and flow control information--Each NIC has a cache of VI descriptors reused between sessions. There are five cache buckets based on the following sizes: T (tiny), S (small), M (medium), L (large), and RM (descriptor packets received in multiple segments). The statistics show the number of descriptors in the cache and the hits and misses for each bucket.

Displaying list of VI NICs

To display the list of all VI NICs associated with the DAFS service, complete the following step.

Step	Action
1	At the filer command line, enter the following command: dafs status -n Result The display shows the state of the DAFS service and a list of all VI NICs that use the DAFS service and their current states. Example filer> dafs status -n DAFS service is started NIC: e4 Device: e4 State: ATTACHED NIC: e5 Device: e5 State: ATTACHED

Step

Action

At the filer command line, enter the following command:

dafs status -n

Result

The display shows the state of the DAFS service and a list of all VI NICs that use the DAFS service and their current states.

Example

filer> dafs status -n

DAFS service is started

NIC: e4         Device: e4              State: ATTACHED

NIC: e5         Device: e5              State: ATTACHED

Displaying sessions associated with VI NICs

To display all sessions associated with VI NICs that use the DAFS service, complete the following step.

Step	Action
1	At the filer command line, enter the following command: `dafs status -sn` Result The display shows the state of the DAFS service and the status of all sessions associated with VI NICs that use the DAFS service. Example: filer> dafs status -sn DAFS service is started NIC: e5 Device: e5 State: ATTACHED Sessions -------- Session ID State Flags 300100008b700002 CONNECTED auth,trust,endian-diff 500100008b700002 CONNECTED auth,trust,endian-diff 2 session(s) found NIC: e9 Device: e9 State: ATTACHED Sessions -------- Session ID State Flags 400100008b700002 CONNECTED auth,trust,endian-diff 1 session(s) found Note If you have multiple VI NICs and want to view the session status for one specific NIC, enter the following command: `dafs status -sn vinic` vinic is a VI NIC interface name, for example, `dafs status -sn e5`

Step

Action

At the filer command line, enter the following command:

dafs status -sn

Result

The display shows the state of the DAFS service and the status of all sessions associated with VI NICs that use the DAFS service.

Example:

filer> dafs status -sn

DAFS service is started

NIC: e5        Device: e5             State: ATTACHED

Sessions

--------

Session ID                 State Flags

300100008b700002       CONNECTED auth,trust,endian-diff

500100008b700002       CONNECTED auth,trust,endian-diff

2 session(s) found

NIC: e9        Device: e9             State: ATTACHED

Sessions

--------

Session ID                 State Flags

400100008b700002       CONNECTED auth,trust,endian-diff

1 session(s) found

Note
If you have multiple VI NICs and want to view the session status for one specific NIC, enter the following command:

dafs status -sn vinic
vinic is a VI NIC interface name, for example,
dafs status -sn e5

Displaying all sessions and DAFS requests

To display all sessions associated with the DAFS service and any DAFS requests for a session, complete the following step.

Step	Action
1	At the filer command line, enter the following command: dafs status -sr Result The display shows the state of the DAFS service, basic information for client sessions, and current DAFS requests. Example: filer> dafs status -sr DAFS service is started Sessions -------- Session ID State Flags 010000008b700002 CONNECTED auth,trust,endian-diff Request: Read Inline, state: RESPONSE_PENDING, stream/seq: 0/220 1 session(s) found Note If you have multiple sessions and want to view the requests active in a specific session, enter the following command: `dafs status -sr session` session is a session ID, for example, `dafs status -sr 010000008b700002`

Step

Action

At the filer command line, enter the following command:

dafs status -sr

Result

The display shows the state of the DAFS service, basic information for client sessions, and current DAFS requests.

Example:

filer> dafs status -sr

DAFS service is started

Sessions

--------

Session ID                 State Flags

010000008b700002       CONNECTED auth,trust,endian-diff

Request: Read Inline, state: RESPONSE_PENDING, 
stream/seq: 0/220

1 session(s) found

Note
If you have multiple sessions and want to view the requests active in a specific session, enter the following command:

dafs status -sr session
session is a session ID, for example,
dafs status -sr 010000008b700002

Displaying client sessions

To display the details of all client sessions associated with the DAFS service, complete the following step.

Step	Action
1	At the filer command line, enter the following command: dafs status -sv Result The display shows the state of the DAFS service and details of all client sessions associated with the DAFS service. Example: filer> dafs status -sv DAFS service is started Sessions -------- 0400000048720002 CONNECTED auth,trust,endian- diff,rescache Remote name: dbclient-viip0 Client identifier: DTS-CLIENT2 Idle: 12 second(s) Max request size: 14000, max response size: 5192 Max requests: 100, current requests: 0, nreq: 1 Registered Credentials, max: 10, current: 1. 0300000048720002 CONNECTED auth,trust,endian- diff,rescache Remote name: dbclient-viip0 Client identifier: DTS-CLIENT Idle: 109 second(s) Max request size: 14000, max response size: 5192 Max requests: 100, current requests: 0, nreq: 1 Registered Credentials, max: 10, current: 1. 2 session(s) found

Step

Action

At the filer command line, enter the following command:

dafs status -sv

Result

The display shows the state of the DAFS service and details of all client sessions associated with the DAFS service.

Example:

filer> dafs status -sv

DAFS service is started

Sessions

--------

0400000048720002       CONNECTED auth,trust,endian-
diff,rescache

  Remote name: dbclient-viip0

  Client identifier: DTS-CLIENT2

  Idle: 12 second(s)

  Max request size: 14000, max response size: 5192

  Max requests: 100, current requests: 0, nreq: 1

  Registered Credentials, max: 10, current: 1.

0300000048720002       CONNECTED auth,trust,endian-
diff,rescache

  Remote name: dbclient-viip0

  Client identifier: DTS-CLIENT

  Idle: 109 second(s)

  Max request size: 14000, max response size: 5192

  Max requests: 100, current requests: 0, nreq: 1

  Registered Credentials, max: 10, current: 1.

2 session(s) found

Explanation of dafs status -sv output

The dafs status -sv command displays the following output:

State of the DAFS service
Session ID--A cluster-wide unique ID
State of the session--CONNECTED or DISCONNECTED
You might also see the following interim states:
- IDLE--The session was created but the connection was not completed.
- DISCONNECT PENDING--The filer is clearing any remaining operations before disconnecting and removing the session.
- MORIBUND--The session is being disconnected as a result of an error. The filer is clearing remaining operations before disconnecting the session. After operations are cleared, the session state is DISCONNECTED.
Remote host name (as resolved from transport)
Client identifier--Supplied by the client in DAFS_PROC_CLIENT_CONNECT calls
Idle time
Negotiated limits for requests
Number of sessions found

The session flags (or state flags) list the properties for a particular session. The possible properties are

back--The session has a back channel.
rdmard--The session has an RDMA_READ channel.
cksum--Checksums are enabled for the session.
auth--The session is authenticated.
trust--The session is trusted.
endian-diff--The session is endian different, indicating byte swapping to maintain byte order.
rescache--The session has the response cache enabled. The filer holds completed client operations in the response cache. If a client session terminates, the client can check the response cache upon reconnecting for a record of completed operations.

Displaying all DAFS status information

To display all DAFS status information for the DAFS service, VI NICs, and client sessions, complete the following step.

Step	Action
1	At the filer command line, enter the following command: dafs status -a

Step

Action

At the filer command line, enter the following command:

dafs status -a

Example

The following lines shows the output of dafs status -a:

DAFS service is started.

  Sessions: 0, disconnected: 0, max disconnected: 32

  Server Requests: curr: 0, limit: 1024, pend: 0, max pend: 512

  Max requests per session: 50, NICs active: 1

  Bytes in: 0, bytes out: 0

  Direct bytes in: 0, direct bytes out: 0

NIC: e4         Device: e4              State: ATTACHED

  Listen Address: 192.168.1.2:DAFS

  Requests in: 0

  Bytes in: 0, bytes out: 0

  Direct bytes in: 0, direct bytes out: 0

  Request daemons: 2

  Descriptor Cache: T:0, S:1, M:0, L:0, RM:0

  Cache Hit/Miss: T:0/0, S:0/1, M:0/0, L:0/0 RM:0/0

  Send pending highwater: 0, limit: 3686, exceed: 0

  Request flowcontrol: 0, flowcontrol timeout: 0

Sessions

--------

Session ID                 State Flags

0 session(s) found

Channels

--------

Channel    Type      State    Session          NIC    Flags

0x361e1b60 PRIMARY   UNUSED   <none>           e4     0x189

  VI: 0x361b18b8, Remote name:

  flags: has_vi,endian_diff,dyn_nreq,recv_multi

  max_requests:0 nreq:0 sendsize:0 recvsize:0

  post_send:0, post_recv:0 loaned_recv:0

1 channel(s) found

Memory Stats

Memory pool: allocs: 471 frees: 441 current: 30

VI memory: allocs: 2 frees: 1 current: 1

Channels : allocs: 2 frees: 1 current: 1 total mem: 276

Requests : allocs: 0 frees: 0 current: 0 unused: 0 total mem: 0

Sessions : allocs: 0 frees: 0 current: 0 unused: 0 total mem: 0

MBUF pool: allocs: 0 used: 0 unused: 0

WAFL buffers: steal: 0 unsteal: 0 current: 0

VI Register: 0, Deregister: 2

VI Non-WAFL Register: 0, Deregister: 0

Max large descriptors cached/NIC: 100