Sponsored Content
Operating Systems AIX AIX NFS Server and NFS Client Post 302960056 by penchev on Tuesday 10th of November 2015 10:44:40 AM
Old 11-10-2015
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
Code:
mkdir /tmp/test
chgrp staff /tmp/test
chmod 775 /tmp/test

-- create export directory (fs)
Code:
mknfsexp -d /tmp/test -t ro

exportfs -va
show mount -e
[
root@host1]:/# exportfs -av
exports: 1831-187 re-exported /tmp/test
mknfs -B


2. Step by step on NFS Client ( AIX 7.1 node)

Code:
[root@host2]:/# ping host1
PING host1: (10.4.12.111): 56 data bytes
64 bytes from 10.4.12.111: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 10.4.12.111: icmp_seq=1 ttl=255 time=0 ms
64 bytes from 10.4.12.111: icmp_seq=2 ttl=255 time=0 ms
64 bytes from 10.4.12.111: icmp_seq=3 ttl=255 time=0 ms

--- host1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms[/HTML][HTML][root@host2]:/# showmount -e host1
export list for host1:
/tmp/test (everyone)

[root@host2]:/# mount host1:tmp/test /test
nfsmnthelp: 1831-019 host1: System call error number -1.

mount: 1831-008 giving up on:
host1:/tmp/test
System call error number -1.

i try and with ip address but some error


where wrong ?

sorry for my mistake english

---------- Post updated at 05:44 PM ---------- Previous update was at 04:11 PM ----------

Ops, i fix my problem

add cross ip and hostname between nodes /etc/hosts

Last edited by Don Cragun; 11-11-2015 at 03:10 AM.. Reason: Change HTML and PHP tags to CODE tags.
 

9 More Discussions You Might Find Interesting

1. Linux

NFS Server FC7 Solaris client problems!

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

2. UNIX for Advanced & Expert Users

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... (2 Replies)
Discussion started by: rascalrick
2 Replies

3. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

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

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

5. Red Hat

Memory problems in NFS client server

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

Can't access NFS Share on Solaris Server from a Linux Client

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. AIX

AIX NFS Client Logging

My AIX NFS client failed to mount a Windows server NFS service today. Is NFS client logging enabled by default on AIX? If not, is there a way to enable NFS client logging on AIX6.1. Thanks. (0 Replies)
Discussion started by: famasutika
0 Replies

8. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies

9. Solaris

Solaris 10 NFS client cannot mount a share from a Windows server

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
scconf_dg_rawdisk(1M)					  System Administration Commands				     scconf_dg_rawdisk(1M)

NAME
scconf_dg_rawdisk - add, change or update raw-disk device group configuration SYNOPSIS
scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,...] [,localonly=true] scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,...] [,localonly=true | false] scconf -c -D name=diskgroup,autogen=true scconf -r -D device_service_name [,nodelist=node[:node]...] [,globaldev=gdev1,...] DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The following information is specific to the scconf command. To use the equivalent object-oriented commands, see the cldevicegroup(1CL) man page. The scconf_dg_rawdisk utility adds, changes or updates raw-disk device group configuration A raw disk is a disk that is not being used as part of a volume manager volume or metadevice. Raw-disk device groups allow you to define a set of disks within a disk device group. At system boot, by default, a raw-disk device group is created for every Disk ID pseudo driver (DID) device in the configuration. By con- vention, the raw-disk device group names are assigned at initialization and are derived from the DID names. For every node added to a raw- disk disk device group, the scconf utility verifies that every device in the group is physically ported to the node. The scconf -a (add) command can be used to create a raw-disk device group with multiple disk devices configured in it. A raw-disk device group is created for every disk device in the cluster at boot time. Before you can add a new raw-disk device group, devices to be used in the new group must be removed from the device group created at boot time. Then a new raw-disk device group can be created containing these devices. This is accomplished by creating a list of these devices in the globaldev option of scconf along with a potential primary node preference list in the nodelist option. If the device group already exists, only new nodes and global devices will be added and nodes or devices which are part of an existing device group will be ignored. If the preferenced suboption is not given with the-a option to create a new device group, then it is, by default, false. However, if the preferenced suboption is specified for the existing device group with a value of true or false, an error is returned. This is done in order to maintain the existing nodelist preference state. If a device group should be mastered by only a particular node then it should be configured with the otheroption set to localonly=true. Only one node can be specified in the node list to create a localonly device group. The scconf -c (change) command is used to change the order of the potential primary node preference, to enable or disable failback, to set the desired number of secondaries, and to add more global devices to the device group. If you want to change the order of node preference list, then all the nodes currently existing in the device group must be specified in the nodelist. In addition, if you are changing the order of node preference, you must also set the preferenced suboption to true. If the preferenced suboption is not specified with the change, the already established true or false setting is used. New nodes cannot be added using the change form of the command. Change option can also be used for changing a device group to localonly device group and vice-versa. To change a device group to a localonly device group, set otheroption to localonly=true. Specify localonly=false to set it back to not the localonly device group. nodelist must already be set to a list of one node, or an error results. It is legal to specify a nodelist with the change form of the command, when you set localonly to true. This is, however, redundant, since the list can only contain the single node that is already configured. It would be an error to specify any other than the node that is already configured. The scconf -r (remove) command can be used to remove the nodes, global devices, and the device group name from the cluster device-group configuration. If nodes or global devices are specified with the device-group name, they are removed from the device group first. After the last device and node are removed from the device group, the device group is also removed from cluster configuration. If only the name of the device group is given (no nodes or devices at all), the entire device group is removed. If a raw-disk device name is registered in a raw-disk device group, then it cannot be registered in a Solaris Volume Manager device group or a VERITAS Volume Manager device group. OPTIONS
See the scconf(1M) man page for the list of supported generic options. The following action options are used to describe the actions performed by the command. Only one action option is allowed in the command. The following action options are supported: -a Add a new raw-disk device group to the cluster configuration. You can also use this option to change the device group configuration. -c Change the ordering of the node preference list, change preference and failback policy, change the desired number of secondaries, and also add more devices to the device group with the globaldev option. It is also used to set a device group as local only. -r Remove the raw-disk device group name from the cluster. The autogen flag is an indicator of the scconf command. This command does not list devices with the autogen property unless the -v command line option is used. When a device is used with the change form of the scconf command, the device's autogen property is reset, or set to false, unless autogen=true is also specified. EXAMPLES
Example 1 Using scconf Commands The following scconf commands create a raw-disk device group, change the order of the potential primary nodes, change preference and fail- back policy, change the desired number of secondaries, and remove the raw-disk device group from the cluster configuration. host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1:host2:host3,preferenced=false,failback=enabled, numsecondaries=,globaldev=d1,globaldev=d2 host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1,globaldev=d1,globaldev=d2,localonly=true, globaldev=d1,globaldev=d2 host1# scconf -c -D name=rawdisk_groupname, nodelist=host3:host2:host1,preferenced=true,failback=disabled, numsecondaries=2,globaldev=d4,globaldev=d5 host1# scconf -c -D name=rawdisk_groupname,localonly=true host1# scconf -r -D name=rawdisk_groupname host1# scconf -r -D name=rawdisk_groupname,nodelist=host1,host2 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevicegroup(1CL), scconf(1M), attributes(5) Sun Cluster 3.2 13 Aug 2007 scconf_dg_rawdisk(1M)
All times are GMT -4. The time now is 05:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy