|
MOUNT
The MOUNT protocol is used to initiate client
access to a server supporting the Network File System (NFS)
application. It handles local operating system specifics such
as path name format and user authentication. Clients desiring
access to the NFS program first call the MOUNT program to obtain
a file handle suitable for use with NFS.
Frames
MOUNT frames may be one of the following
types:
| [no operation] |
Performs no operation. |
| [add mount entry] |
Requests file handle for NFS. |
| [get all mounts] |
Requests list of mounts for
the client. |
| [del mount entry] |
Requests deletion of mount entry. |
| [del all mounts] |
Requests removal of mounts for
client. |
| [get export list] |
Requests group permissions for
mounts. |
| [mount added] |
Supplies file handle for use
with NFS. |
| [give all mounts] |
Supplies list of mounts for
the client. |
| [mount deleted] |
Confirms deletion of mount entry. |
| [mounts deleted] |
Confirms deletion of all client
mounts. |
| [give export list] |
Lists group permissions for
mounts. |
Frame Parameters
MOUNT frames can have the following parameters:
Path name
The server path name of the mounted directory displayed
in double quotes.
File handle
The 32-byte file handle used to access the mounted directory.
Failure to mount on a UNIX system can lead
to the display of the error message UNIX Error xxxx,
where xxxx is a standard UNIX operating system error.
Interested in more
details about testing this protocol?
PMAP
The Port Mapper (PMAP) protocol manages
the allocation of transport layer ports to network server applications.
Server applications obtain a port by requesting a port assignment.
Clients wanting to access an application first call the PMAP
program (on a well-known port) to obtain the transport port
registered to the application. The client then calls the application
directly using the registered port. Use of PMAP eliminates
the need to reserve permanently a port number for each application.
Only the PMAP application itself requires a reserved port.
Frames
PMAP frames may be one of the following
types:
| [no operation] |
Performs no operation. |
| [set port number] |
Attempt to register an application. |
| [unset port numb] |
Attempt to unregister an application. |
| [get port number] |
Requests registered port number. |
| [get all ports] |
Requests all registered ports. |
| [call program] |
Direct call to a registered
application. |
| [port assigned] |
Registers an application to
a port. |
| [port unassigned] |
Unregisters an application. |
| [give port number] |
Informs client of registered
port. |
| [give all ports] |
Informs client of all registered
ports. |
| [program called] |
Returns information from called
program. |
Frame Parameters
PMAP frames can contain the following parameters:
Transport port
Transport layer port assigned to
the specified application.
Program number
Application program number.
Program version
Version number of the program.
Transport protocol
Transport layer protocol the program is registered to use.
Procedure
Procedure number within the called program.
If the program number is unregistered, the
message {Program is unregistered} is displayed.
Interested in more
details about testing this protocol?
YP (NIS)
The Sun Yellow Pages (YP) protocol, now
known as Network Information Service (NIS), is a directory
service used for name look-up and general table enumeration.
Each YP database consists of key-value pairs, maps, and domains.
The key is the index e.g., name, to which YP maps values such
as a phone number. Because keys and values mapped to them can
be any arbitrary string of bytes, a YP server can contain a
wide variety of database types.
YP defines a set of key-value pairs as a
map. Each map belongs to a domain that is a category of maps.
This hierarchy of key-value pairs, maps, and domains provides
a generic structure for modeling a database of information.
An optional component to a YP server database
implementation is the YP binder (YPbind) server. YP uses YP
binder servers to provide addressing information about YP database
servers to potential clients. A client desiring access to a
YP database server can call the YP binder service with a domain
name and receive the IP address and transport port of the YP
server for that domain. If clients can more easily obtain this
information elsewhere, the YP binder service is not needed.
Frames
YP and YPbind frames may be one of the following
commands:
| [no operation] |
Performs no operation. |
| [domain serve query1] |
Asks whether or not the specified
domain is served. |
| [domain serve query2] |
Asks only for servers that serve
the specified domain. |
| [get key value] |
Asks for value associated with
the specified key. |
| [get first key pair] |
Requests the first key-value
pair in map. |
| [get next key pair] |
Requests the next key-value
pair in map. |
| [transfer map] |
Requests a new copy of the map
to be transferred. |
| [reset YP server] |
Requests the YP server to reset
its internal state. |
| [get all keys in map] |
Requests all key-value pairs
in specified map. |
| [get map master name] |
Requests the name of master
YP database server. |
| [get map number] |
Requests the creation time of
the specified map. |
| [get all maps] |
Requests all maps in the specified
domain. |
| [domain serve reply1] |
Response to domain serve query1. |
| [give key value] |
Returns value for specified
key. |
| [give first key pair] |
Returns the first key-value
pair in map. |
| [give next key pair] |
Returns the next key-value pair
in map. |
| [map transferred] |
Reports map transfer status. |
| [YP server reset] |
Reports server reset status. |
| [give all keys in map] |
Returns listing of all keys
in map. |
| [give map master name] |
Returns name of master YP database
server. |
| [give map number] |
Returns creation date of map. |
| [give all maps] |
Returns listing of all maps
in domain. |
| [no operation] |
Performs no operation. |
| [get current binding] |
Requests YP addressing information
for the specified domain. |
| [set domain binding] |
Installs YP addressing information
for the specified domain. |
| [give current binding] |
Returns YP addressing information
for a domain. |
| [domain binding set] |
Returns status of YP addressing
installation. |
Frame Parameters
YP and YPbind frames can contain the following
parameters:
Bind address
IP address of the YP binder server.
Bind port
Transport port used by the YP binder
server.
Created
Creation time of the map.
Domain
Domain name in use.
Key
Key index used to search for a value.
Map
Map name in use.
Master
Name of the master YP database server.
Peer
Server name of a peer YP server.
Transfer ID
Transfer ID used to reference map
transfers.
Program
RPC program number used for map transfer.
Port
Transport layer port number used
for map transfer.
Value
Value associated with a key.
Status
Map transfer status.
Version
YPbind protocol version.
Response Frames
YP response frames can contain the following
status messages:
| {OK} |
Request completed successfully. |
| {Bad request arguments} |
Request parameters invalid. |
| {Domain not supported} |
Domain not supported by this
YP server. |
| {General failure} |
Unspecified failure. |
| {Invalid operation} |
Request invalid. |
| {No more entries in map} |
No more key-value pairs in map. |
| {No such map in domain} |
Specified map not in domain. |
| {No such key in map} |
Specified key not in map. |
| {Server database is bad} |
Server database corrupt. |
| {YP server error} |
Internal YP server error. |
| {YP version mismatch} |
YP server versions do not match. |
YPbind response frames can contain the following
messages:
| {OK} |
Request completed successfully. |
| {Internal error} |
Local YP binder error. |
| {No bound server for domain} |
No YP database servers known
for the domain. |
| {Can’t alloc system resource} |
YP binder resource error. |
Transfer Status Frames
YPbind transfer status frames can contain
the following messages:
| {Transfer successful} |
Transfer completed successfully. |
| {Bad request arguments} |
Request parameters invalid. |
| {Can’t clear YP server} |
Cannot clear the local YP server. |
| {Can’t find server f/map} |
Cannot find YP server for map. |
| {Can’t get master addr.} |
Cannot get YP master server
address. |
| {Domain not supported} |
Domain not supported by this
YP server. |
| {Local database failure} |
Local YP server database failure. |
| {Local file I/O error} |
Local YP server file I/O error. |
| {Map version mismatch} |
Map versions skewed in transfer. |
| {Master dbase not newer} |
Master database is not newer. |
| {Must override defaults} |
Must override default settings. |
| {Resource alloc failure} |
Resource allocation failure. |
| {RPC to server failed} |
No RPC response from server. |
| {Server/map dbase error} |
YP server or map database error. |
| {Server refused transfer} |
YP server refused to transfer
database. |
| {YP transfer error} |
Error occurred during database
transfer. |
Interested in more details about testing
this protocol?
 1 2 3 4 
SUN Protocols Information
MNTV1 | Mntv3 | MOUNT | NFS | NFS2 | NFS3 | NFSv4 | NLMv4 | NLP | NSMv1 | PMAP | RPC | RPCBv3 | RPCBV4 | RPCmap | RPCSEC
GSS | YP (NIS)
|
