25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

► The NFS protocol performs the file I/O to the remote file system.<br />

Both the Mount <strong>and</strong> NFS protocols are RPC applications that implement the<br />

client/server model (see Figure 11-1 on page 409) <strong>and</strong> are transported by both<br />

<strong>TCP</strong> <strong>and</strong> UDP.<br />

Mount protocol<br />

The Mount protocol is an RPC application shipped with NFS <strong>and</strong> uses program<br />

number 100005. The MOUNT comm<strong>and</strong> acts as an RPC server program <strong>and</strong><br />

provides a total of six procedures when accessing remote systems:<br />

NULL Does nothing. Useful for server response testing.<br />

MNT MOUNT function. Returns a file h<strong>and</strong>le pointing to the directory.<br />

DUMP Returns the list of all mounted file systems.<br />

UMNT Removes a mount list entry.<br />

UMNTALL Removes all mount list entries for this client.<br />

EXPORT Returns information about the available file systems.<br />

A file h<strong>and</strong>le is a variable-length array with a maximum length of 64 bytes <strong>and</strong> is<br />

used by clients to access remote files. They are a fundamental part of NFS,<br />

because each directory <strong>and</strong> file are referenced only through file h<strong>and</strong>les. For this<br />

reason, some implementations increase the security of the protocol by<br />

encrypting the h<strong>and</strong>les. The file h<strong>and</strong>les are obtained by executing the MOUNT<br />

application’s MNT procedure, which locates the remote file system within the file<br />

hierarchy, <strong>and</strong> returns the file h<strong>and</strong>le. Following the MOUNT comm<strong>and</strong>, a user<br />

can access the remote file system as though it were a part of the local file<br />

system.<br />

For example, consider two remote hosts:<br />

► HostA implements a hierarchical file system consisting of numerous<br />

directories <strong>and</strong> subdirectories.<br />

► HostB does not implement a hierarchical file system, but instead implements<br />

a series of minidisks, with each minidisk appearing as a separate folder.<br />

A user on HostA issues the MOUNT comm<strong>and</strong> to locally mount a minidisk from<br />

HostB. However, the user does not see the mounted volume as a minidisk, but<br />

instead sees it in the context of the hierarchical file system of HostA.<br />

Although specific implementations can provide additional features, the generic<br />

syntax of the MOUNT comm<strong>and</strong> is as follows:<br />

MOUNT -o options host:rvolume lvolume<br />

Chapter 14. File-related protocols 539

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!