Introducing Network File System Version 4 on HP-UX 11i v3

6
Figure 4. SETCLIENTID opcode reply
The client identifier assigned by the server to this client appears on line 11 in Figure 4.
Because NFSv4 is a stateful protocol, some opcodes require the client to identify itself by passing its
client identifier to the server. For example, because file locks are associated with a client (and
therefore a client identifier), the locking opcodes, LOCK, LOCKU, and LOCKT, all require the client to
send its client identifier as part of the operation.
To see the list of opcodes defined as part of NFSv4, execute the nfsstat command. The nfsstat
command has been enhanced to display NFSv4 statistics. For example, Figure 5 displays the NFSv4
opcodes executed after the initial NFSv4 mount.