IBM AIX 4.3 (rs6000) configuration
Accessing the Configuration repository
To
obtain any configuration files specific to the Solaris platform the
configuration repository must first be made available. To do this carry
out the following steps
Create a mount point using the command “mkdir –p export/home/unixcfg”
a) Add an entry into the file /etc/filesystems as shown below (or use smit)
/export/home/unixcfg:
dev = “/unixcfg”
vfs = nfs
nodename = mainfileserver.domain.local
mount = true
options = bg,soft,intr
account = false
b)
Issue the command “mount –a” which should mount the new file system
entry added in the previous step. You can ignore messages pertaining to
filesystems that are already mounted
c) You should now be able “cd” to the /export/home/unixcfg/ directory to recover any configuration files referenced in the rest of these instructions.
NIS configuration – part 1
To configure the AIX V5 system as a NIS client carry out the following steps
a)
Ensure NFS is installed and the portmapper is running by issuing the
command shown below. Note the status of the portmap service should be
“active”.
#lssrc -s portmap
Subsystem
Group PID Status
portmap portmap 4388 active
#
b) Set the NIS domainname using the command shown below
#chypdom –B domain.local
Nameservice switch configuration
Unlike
many other Unix operating systems AIX does not use a name service
switch configuration file. Rather it uses the much older method of
adding special entries in the local files such as /etc/passwd to
effectively “append” the NIS data to the local file.
Create an append entry in /etc/passwd
We need to append an entry to the
end of the password file to cause NIS data to be processed as well as
data from local files. An example is shown below Note that the
position of the entry determines the order of processing. Putting the
NIS entry at the end means that the local accounts are checked before
NIS is consulted. This is the normal approach adopted.
Create an append entry in /etc/group
We
also to append an entry to the end of the /etc/group file to cause NIS
data to be processed as well as data from the local group file. An
example is shown below
NIS configuration – part 2
The last step of NIS configuration
for the rs6000 involves starting the NIS background processes and
ensuring that they are configured to restart whenever the machine is
re-booted. There are various ways of accomplishing this. A method using
smit is show below
a) Log in to the pSeries system as root
b) Edit the file /etc/rc.nfs and uncomment the lines
#if [ -x /usr/lib/netsvc/yp/ypbind ]; then
# start ypbind /usr/lib/netsvc/yp/ypbind
#fi
c) Enter the IP address of the NIS server
d) Press “Enter” to execute the commands
e)
This should result in the NIS client software having started. You can
test this by issuing a “ypcat passwd” command which should list the NIS
passwd database
Set up “/export/home/users” directory NFS mount
Most users’ home directories will be
on the main file server. Carry out the configuration actions below to
enable users to access their home directories automatically.
Note:
Do not insert any comment lines in to the body of /etc/filesystems as
this may cause aix problems interpreting the file.
a)
Create the /export/home/users mountpoint using the command “mkdir –p
/export/home/users” Note that any “local” contents of the directory
“/export/home/users” will not be visible once this file system is
mounted. Therefore check that “/export/home/users” contains no data at
this time. If it does take steps to preserve or delete it
b) Add an entry into the file /etc/filesystems as shown below (or use smit)
/export/home/users:
dev = “/users”
vfs = nfs
nodename = mainfileserver.domain.local
mount = true
options = bg,soft,intr
account = false
c)
Issue the command “mount –a” which should mount the new file system
entry added in the previous step. You can ignore messages pertaining to
filesystems that are already mounted
d) You should now be able “cd” to
the/export/home/users directory. The individual user directories should
be visible
e) If the directory /home exists create a softlink in this directory pointing to /export/home/users as shown below
#ln –s /export/home/users /home/users
Set up main file server “/export/home/group1” NFS mount
Several
key directories are mapped to the “U” drive on the NAS server. To
enable their use it is necessary to map the NAS server “U” drive to the
“/export/home/hg1” NFS mounted filesystem as shown below
a) Create the /export/home/hg1 mountpoint using the command “mkdir –p /export/home/hg1”
b) Add an entry into the file /etc/filesystems as shown below (or use smit)
/export/home/hg1:
dev = “/homegroup1”
vfs = nfs
nodename = borg
mount = true
options = bg,soft,intr
account = false
c)
Issue the command “mount –a” which should mount the new file system
entry added in the previous step. You can ignore messages pertaining to
filesystems that are already mounted
d) Ensure that if the directory
“/export/home/group1” exists that its contents are either
unneeded or saved.
e) Create a soft link for /export/home/group1 and /home/group1 pointing to /export/home/hg1/ using a command of the form shown below
#ln –s /export/home/hg1/aix5 /home/group1
#ln –s /export/home/hg1/aix5 /export/home/group1
h) You should now be able “cd” to the /home/group1 directory.
Set up “/export/home/source” directory NFS mount
The source directory is on the main file server. This must be mounted on the /export/home/source directory
a)
Create the /export/home/source mountpoint using the command “mkdir –p
/export/home/source” Note that any “local” contents of the directory
“/export/home/source” will not be visible once this file system is
mounted. Therefore check that “/export/home/source” contains no data at
this time. If it does take steps to preserve or delete it
c) Add an entry into the file /etc/filesystems as shown below (or use smit)
/export/home/source:
dev = “/source”
vfs = nfs
nodename = mainfileserver.domain.local
mount = true
options = bg,soft,intr
account = false
d)
Issue the command “mount –a” which should mount the new file system
entry added in the previous step. You can ignore messages pertaining to
filesystems that are already mounted
e) Create a softlink to point /home/source at /export/home/source as shown below
#ln –s /export/home/source /home/source
Set up “/export/home/qatests” directory NFS mount
The qatests directory is on the main file server. This must be mounted on the /export/home/source directory
a)
Create the /export/home/qatests mountpoint using the command “mkdir –p
/export/home/qatests” Note that any “local” contents of the directory
“/export/home/qatests” will not be visible once this file system is
mounted. Therefore check that “/export/home/qatests” contains no data
at this time. If it does take steps to preserve or delete it
b) Add an entry into the file /etc/filesystems as shown below
/export/home/qatests:
dev = “/qatests”
vfs = nfs
nodename = mainfileserver.domain.local
mount = true
options = bg,soft,intr
account = false
c)
Issue the command “mount –a” which should mount the new file system
entry added in the previous step. You can ignore messages pertaining to
filesystems that are already mounted
d) Create a softlink to point /home/qatests at /export/home/qatests as shown below
#ln –s /export/home/qatests /home/qatests
Set up “/export/home/hg1output” directory NFS mount
The qaoutput directory is on the main file server. This must be mounted on the /export/home/source directory
Next (AIX 5.1)
Back to menu
