12-08-2008
Determining IP address of NFS server on client
Hi. We use an Isilon cluster system to provide our NAS. The Isilon uses a round-robin DNS setup to spread mount requests across the many nodes of the cluster. When a node needs work, the filesystems that are mounted to it need to be moved to other nodes prior to shutting the node down. I haven't been able to determine a way to identify what IP address a client is mounting to. Output from df or the mount command simply report the DNS name for the cluster, the that address that was selected. Does anyone know of a way on a Solaris client to determine what IP address a mount point is using?
9 More Discussions You Might Find Interesting
1. Programming
Hi All,
When I connect to a unix server from a client machine,
how can I get the IP address of the client?
One way of retrieving IP address of client which initiates an active connection to the server is through /var/adm/utmpx file
upon login; client's IP address and other info would have... (4 Replies)
Discussion started by: matrixmadhan
4 Replies
2. Linux
Hi,
my problem is that I am not able to grand the nfs directory on a Fedora 7 server to a standard solaris client.
I always got the messages no permission.
Important: No change on the client (Solaris) is possible! So I am not able to change the NFS Version on the client side to force the... (3 Replies)
Discussion started by: joerg
3 Replies
3. Solaris
Hello,
I have a centos as nfs server, its name is centos_A.
After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/*
But,
My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies
4. AIX
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
5. Red Hat
Hi all,
i have some doubts in a situation that i fail to get an answer in Google.
I have a solaris 10 nfs server and 5 centos 6.0 nfs clients.
The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Discussion started by: blast
5 Replies
6. Solaris
Hi,
I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server.
On the NFS Server, in /etc/dfs/, I added following line to dfstab file.
& then ran the following
On the client machine, while running the mount command, I am... (0 Replies)
Discussion started by: SunilB2011
0 Replies
7. Red Hat
Hi,
I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server.
On the NFS Server, in /etc/dfs/, I added following line to dfstab file.
share -F nfs -o rw /var/share
& then ran the following
svcadm -v enable -r... (3 Replies)
Discussion started by: SunilB2011
3 Replies
8. AIX
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
9. Solaris
I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
Discussion started by: Hiroshi
1 Replies
info(4) Kernel Interfaces Manual info(4)
NAME
info - diskless client configuration information file
DESCRIPTION
The file is a POSIX shell sourceable file which contains parameter definitions used at boot time. Typically, it will be an empty file and
default values will be used for all parameters. Following is the list of parameters which can be defined in the file:
Specifies the IP address of the client's private root server. If this is not
specified, the client's private root server defaults to the boot server.
Specifies the pathname to the client's private root on the private root
server. If this is not specified, the client's private root path defaults to
Specifies the NFS mount options to mount the client's private root from
the private root server. If this is not specified, the mount options default to
Specifies the NFS mount options to mount the client's
directory from the boot server. If this is not specified, the mount options default to
Specifies whether NFS should be configured as primary swap. (NOTE: In
order to swap to NFS, a diskless kernel must be configured with tunable parameter set to 1.) If a diskless
machine has a local swap disk and swap to NFS is not desired, the parameter should be set to the value of 1
and the diskless kernel should be configured without setting to 1. If this parameter is not specified in
the file and the kernel tunable parameter is set to 1, then NFS will be configured as primary swap.
If not set, this parameter defaults to a value of 1, and results in the
removal of all swapfiles above the configured swap minimum (swap is specified in the client's when a disk-
less client boots. This ensures that extraneous swapfiles at boot time are removed, thus freeing disk
space. If is set to 0 in the file, removal of extra swapfiles is disabled. This may result in faster boot
times due to the time savings in creating additional swap files.
The file resides in the same directory as the client's kernel () on the boot server and is retrieved at boot time using command. By
default, when a diskless client is created, an empty file is placed in the client's kernel directory. This ensures that all parameters
revert to their default values (see above). If the file is not present, this is an error.
EXAMPLES
An example file is shown below:
FILES
info(4)