Did you try using the "_netdev" option in fstab for NFS mounts?
Quote:
_netdev
The filesystem resides on a device that requires network access (used to prevent
the system from attempting to mount these filesystems until the network has been
enabled on the system).
Hello Everyone,
I have a pseries machine running AIX 4.3.3 that has an invalid IP in /etc/hosts. During a boot the system hangs because it's trying to mount an NFS share to this invalid IP.
I've tried to boot the system from a mksysb (not sure if the device was defined as rmt0) and AIX CD... (0 Replies)
Hi, I have a Unix box running HP-UX 10.20 and it suddenly won't boot. Every time it goes down the boot checklist, it hangs on "NFS client subsystem" and just continues to say busy/wait. I have read something about the /etc/auto_master but don't quite understand what has to happen to fix it. ... (4 Replies)
Hi,
Can someone help me on this?
I'm not able to enable a well working mounting process for NFS filesystems on boot time.
On the server side (AIX 5.2) everything seems to be OK and correctly exported, seeing other clients (AIX 5.2) are able to mount normally on boot time.
On a client in... (5 Replies)
Hi,
I have 12 AIX P series servers. One has the NFS DB2data and the others are client mounts. NFS is not in /etc/filesystem because if NFS DB2data not up the client takes 7+ minutes to give up on nfsmnt and boot up.
I'd like to check that nfs is up, then do the client mount all from a startup... (0 Replies)
Hello Experts,
I'm trying to boot my AIX server via network using another AIX as a boot server. I use tcpdump to monitor the process. After my boot client received .info file and mounted nfs resource (checked by 'showmount -a' from boot server) it hung. I noticed a lot of following entries:
... (0 Replies)
we have a Solaris 8 nfs server that exported two shares. entries are in /etc/dfs/dfstab.
clients have been accessing these shares for several years.
we just rebooted this nfs server and noticed that no share gets exported. I don't see relevant messages from dmsg nor messages file, is there... (6 Replies)
Hello, I am looking for some assistance in mounting an nfs drive on boot, on a Solaris 11 machine.
On my Solaris 9/10 machines, I have an entry for my nfs mount in /etc/vfstab, however when I add the same entry to my vfstab on Solaris 11, the drive will not mount on boot. After booting up, I... (5 Replies)
Hello,
I am facing some issues during boot process of rhel 6.2
It takes too long time (~10 min) for the node to come up...
The boot process stuck while it trying to start NFS and does not continue until timeout.
In the boot.log file i see
Starting NFS quotas: Cannot register service:... (2 Replies)
I have several Solaris 11.2 zones. when I reboot them I have to go in and do mountall to mount the NFS mounts.
any ideas where to troubleshoot why they are not automounting? (2 Replies)
Discussion started by: os2mac
2 Replies
LEARN ABOUT HPUX
nfssec
nfssec(5) File Formats Manual nfssec(5)NAME
nfssec - overview of NFS security modes
DESCRIPTION
The mount_nfs(1M) and share_nfs(1M) commands each provide a way to specify the security mode to be used on an NFS filesystem through the
option. mode can be either or These security modes may also be added to the automount maps. Note that mount_nfs(1M) and automount(1M) do
not support at this time.
The option on the share_nfs(1M) command line establishes the security mode of NFS servers. If the NFS connection uses the NFS Version 3
protocol, the NFS clients must query the server for the appropriate mode to use. If the NFS connection uses the NFS Version 2 protocol,
then the NFS client uses the default security mode, which is currently NFS clients may force the use of a specific security mode by speci-
fying the option on the command line. However, if the filesystem on the server is not shared with that security mode, the client may be
denied access.
If the NFS client wants to authenticate the NFS server using a particular (stronger) security mode, the client wants to specify the secu-
rity mode to be used, even if the connection uses the NFS Version 3 protocol. This guarantees that an attacker masquerading as the server
does not compromise the client.
The NFS security modes are described below. Of these, the modes use the Kerberos V5 protocol for authenticating and protecting the shared
filesystems. Before these can be used, the system must be configured to be part of a Kerberos realm.
Use authentication. The user's UNIX user-id and group-ids are passed in the clear on the network, unauthenticated by the NFS server
. This is the simplest security method and requires no additional administration. It is the default used by HP-UX NFS Version 2
clients and HP-UX NFS servers.
Use a Diffie-Hellman public key system
which is referred to as in the forthcoming Internet RFC).
Use Kerberos V5 protocol to authenticate users before granting access
to the shared filesystem.
Use Kerberos V5 authentication with integrity checking (checksums) to
verify that the data has not been tampered with.
User Kerberos V5 authentication, integrity checksums, and privacy protection
(encryption) on the shared filesystem. This provides the most secure filesystem sharing, as all traffic is encrypted. It should
be noted that performance might suffer on some systems when using depending on the computational intensity of the encryption
algorithm and the amount of data being transferred.
Use null authentication
NFS clients using have no identity and are mapped to the anonymous user by NFS servers. A client using a security mode other
than the one with which an HP-UX NFS server shares the filesystem has its security mode mapped to In this case, if the filesystem
is shared with users from the client are mapped to the anonymous user.
WARNINGS
lists the NFS security services. Do not edit this file. It is not intended to be user-configurable.
FILES
NFS security service configuration file
SEE ALSO automount(1M), mount_nfs(1M), share_nfs(1M), rpc_clnt_auth(3N), secure_rpc(3N), nfssec.conf(4).
nfssec(5)