Sponsored Content
Operating Systems AIX AIX 5.3 NFS export not mounting, rpcinfo hang/timeout on server Post 303038768 by MadeInGermany on Friday 13th of September 2019 01:59:46 AM
Old 09-13-2019
Yes, rpcbind/portmap is needed, and rpcinfo -p must show mountd and nfs and their udp/tcp ports.
Please check the following:
AIX for System Administrators
 

10 More Discussions You Might Find Interesting

1. Solaris

Mounting a NFS network file system across platforms - Solaris to AIX

Hi all, Kind of an emergency situation, I have to NFS mount an AIX filesystem on to a Sun Solaris OS (5.10). Typically from Sun to Sun is: mount -F nfs <remote file system>/dir <mount point> Which of course doesn't work if the remote file system is another OS (like AIX). Is there... (1 Reply)
Discussion started by: jeffpas
1 Replies

2. AIX

How to export AIX File system NFS to Windows ?

Hello, Can someone please point to an easy document or steps how to export AIX file system /whatever to Windows O/S Basically Windows should see this filesystem / directory and should be able to write in this filesystem / directory Thanks (2 Replies)
Discussion started by: filosophizer
2 Replies

3. AIX

ftp timeout valiue in AIX 5.3 server !

Dear Friends, I am using AIX 5.3 server . In AIX , I want to increase the timeout value of the ftp service . But I cannot find any configuration file with ftp related in AIX 5.3 server . Would anybody plz tell me , How can I increase the default timeout value in AIX ? (2 Replies)
Discussion started by: shipon_97
2 Replies

4. Solaris

Could I re-export a NFS resource to a third server ?

Hey Guys. Could someone said if is possible take a NFS resource get it from a original Server a export it and mount it in a third server ? Thank in Advace.... SUN ADMIN (3 Replies)
Discussion started by: aggadtech08
3 Replies

5. UNIX for Dummies Questions & Answers

Is it possible to set a timeout for rpcinfo?

I've created a script that checks the health of a piece of equipment out in the field by first establishing that it is pingable, and then parsing log files to gather information. Today I realized that there are times where the equipment may be pingable, and will not show any immediate issues in... (1 Reply)
Discussion started by: DeCoTwc
1 Replies

6. Solaris

Df -h hang cant see any NFS storage

Hi all I had a server, when run the df -h command, it hang, and need to press "crtl+c" to terminate it. i cant other NFS filesystem anymore. but i try at other server, the NFS filesystem is work properly any idea on this? # mount -p /dev/md/dsk/d0 - / ufs - no... (1 Reply)
Discussion started by: SmartAntz
1 Replies

7. AIX

can not mount from aix client to linux nfs server

Hi, I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error: # mount 128.127.11.121:/aix /to_be_del mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper failure - RPC: 1832-008 Timed out mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies

8. AIX

CIFS Mount not mounting on my AIX server

Dear Experts, Im facing a unique situation. We got a windows server folder cifs mounted on my AIX server. Before restarting the win server I tried unmounting the cifs mount. It got hanged and win server was restarted however. Now Im trying to mount the same. It prompts for password... (3 Replies)
Discussion started by: jayadeava
3 Replies

9. Red Hat

Mounting NFS filesystem on Windows server

Hello Can someone please suggest how should I configure Samba to share the drive from Linux to Window server, and Windows server is in AD environment. is this require winbind to be installed ?? Thanks, (0 Replies)
Discussion started by: bobby320
0 Replies

10. AIX

AIX NFS Server and NFS Client

Hi 2 ALL, try to run NFS Server in AIX 7.1 : 1. Step by step on NFS Server node mkdir /tmp/test chgrp staff /tmp/test chmod 775 /tmp/test-- create export directory (fs) mknfsexp -d /tmp/test -t ro exportfs -va show mount -e :/# exportfs -av exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies
RPCINFO(8)						    BSD System Manager's Manual 						RPCINFO(8)

NAME
rpcinfo -- report RPC information SYNOPSIS
rpcinfo [-m | -s] [host] rpcinfo -p [host] rpcinfo -T transport host prognum [versnum] rpcinfo -l [-T transport] host prognum [versnum] rpcinfo [-n portnum] -u host prognum [versnum] rpcinfo [-n portnum] [-t] host prognum [versnum] rpcinfo -a serv_address -T transport prognum [versnum] rpcinfo -b [-T transport] prognum versnum rpcinfo -d [-T transport] prognum versnum DESCRIPTION
rpcinfo makes an RPC call to an RPC server and reports what it finds. In the first synopsis, rpcinfo lists all the registered RPC services with rpcbind on host. If host is not specified, the local host is the default. If -s is used, the information is displayed in a concise format. In the second synopsis, rpcinfo lists all the RPC services registered with rpcbind, version 2. Also note that the format of the information is different in the first and the second synopsis. This is because the second synopsis is an older protocol used to collect the information displayed (version 2 of the rpcbind protocol). The third synopsis makes an RPC call to procedure 0 of prognum and versnum on the specified host and reports whether a response was received. transport is the transport which has to be used for contacting the given service. The remote address of the service is obtained by making a call to the remote rpcbind. The prognum argument is a number that represents an RPC program number. If a versnum is specified, rpcinfo attempts to call that version of the specified prognum. Otherwise, rpcinfo attempts to find all the registered version numbers for the specified prognum by calling version 0, which is presumed not to exist; if it does exist, rpcinfo attempts to obtain this information by calling an extremely high version number instead, and attempts to call each registered version. Note: the version number is required for -b and -d options. OPTIONS
-T transport Specify the transport on which the service is required. If this option is not specified, rpcinfo uses the transport specified in the NETPATH environment variable, or if that is unset or null, the transport in the netconfig(5) database is used. This is a generic option, and can be used in conjunction with other options as shown in the SYNOPSIS. -a serv_address Use serv_address as the (universal) address for the service on transport to ping procedure 0 of the specified prognum and report whether a response was received. The -T option is required with the -a option. If versnum is not specified, rpcinfo tries to ping all available version numbers for that program number. This option avoids calls to remote rpcbind to find the address of the service. The serv_address is specified in universal address format of the given trans- port. -b Make an RPC broadcast to procedure 0 of the specified prognum and versnum and report all hosts that respond. If transport is speci- fied, it broadcasts its request only on the specified transport. If broadcasting is not supported by any transport, an error message is printed. Use of broadcasting should be limited because of the potential for adverse effect on other systems. -d Delete registration for the RPC service of the specified prognum and versnum. If transport is specified, unregister the service on only that transport, otherwise unregister the service on all the transports on which it was registered. Only the owner of a service can delete a registration, except the super-user who can delete any service. -l Display a list of entries with a given prognum and versnum on the specified host. Entries are returned for all transports in the same protocol family as that used to contact the remote rpcbind. -m Display a table of statistics of rpcbind operations on the given host. The table shows statistics for each version of rpcbind (ver- sions 2, 3 and 4), giving the number of times each procedure was requested and successfully serviced, the number and type of remote call requests that were made, and information about RPC address lookups that were handled. This is useful for monitoring RPC activi- ties on host. -n portnum Use portnum as the port number for the -t and -u options instead of the port number given by rpcbind. Use of this option avoids a call to the remote rpcbind to find out the address of the service. This option is made obsolete by the -a option. -p Probe rpcbind on host using version 2 of the rpcbind protocol, and display a list of all registered RPC programs. If host is not specified, it defaults to the local host. Note: Version 2 of the rpcbind protocol was previously known as the portmapper protocol. -s Display a concise list of all registered RPC programs on host. If host is not specified, it defaults to the local host. -t Make an RPC call to procedure 0 of prognum on the specified host using TCP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis. -u Make an RPC call to procedure 0 of prognum on the specified host using UDP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis. EXAMPLES
To show all of the RPC services registered on the local machine use: example% rpcinfo To show all of the RPC services registered with rpcbind on the machine named klaxon use: example% rpcinfo klaxon The information displayed by the above commands can be quite lengthy. Use the -s option to display a more concise list: example$ rpcinfo -s klaxon program version(s) netid(s) service owner 100000 2,3,4 local,tcp,udp,tcp6,udp6 rpcbind super-user 100008 1 udp,tcp,udp6,tcp6 walld super-user 100002 2,1 udp,udp6 rusersd super-user 100001 2,3,4 udp,udp6 rstatd super-user 100012 1 udp,tcp sprayd super-user 100007 3 udp,tcp ypbind super-user To show whether the RPC service with program number prognum and version versnum is registered on the machine named klaxon for the transport TCP use: example% rpcinfo -T tcp klaxon prognum versnum To show all RPC services registered with version 2 of the rpcbind protocol on the local machine use: example% rpcinfo -p To delete the registration for version 1 of the walld (program number 100008 ) service for all transports use: example# rpcinfo -d 100008 1 or example# rpcinfo -d walld 1 SEE ALSO
rpc(3), netconfig(5), rpc(5), rpcbind(8) August 18, 1992
All times are GMT -4. The time now is 11:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy