How To Set Up 1-Touch For AIX-优快云博客

本文详细介绍了使用Simpana 8.0在两台IBM p5510服务器上配置和设置1-Touch客户端和服务器的过程。内容涵盖了NIM Master的准备、名称解析的配置、文件大小限制的设定、NIM Master的设置、检查NIM Master是否支持特定版本的AIX、创建新的lpp_source、创建SPOT资源、空间考虑、NIM客户端的名称解析配置、检查文件系统大小、启用1-Touch恢复等步骤。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

How To Set Up 1-Touch For AIX

Published 09/29/2009 05:15 PM | Updated 08/06/2010 06:00 PM

This document will cover the process to setup 1-Touch for AIX using Simpana 8.0. This document should in no way be treated as the “End All” procedure. It is merely provided as a template on how this process can be accomplished.

The entire setup will be performed on two IBM 9110-510 (p5 510) servers

ibmaix01 will be the 1-Touch client and is running AIX 5.300-06
ibmaix02 will be the 1-Touch server running the NIM Master server environment on AIX 5.300-08

Resolution:

NIM Master preparation

AIX 1-Touch is based on IBM's NIM (Network Installation Management). The machines you want to manage in the NIM environment, their resources, and the networks through which the machines communicate are all represented as objects within a central database that resides on the master. Problems may result if the NIM master and the NIM clients use different orders when querying sources for name resolution. Problems may also arise if a name service is available to one machine but not to another, causing different name resolution sources to be used. During a 1-Touch recovery only DNS/ local /etc/host files are available for resolving hostnames.

Configure name resolution on the NIM Master

It is possible to overirde the default system-wide order that AIX and NIM use to resolve hostnames. This can be done by setting the NSORDER environment variable. The /etc/environment file contains variables specifying the basic environment for all processes.

1. Check if NSORDER environment variable is set

# grep ^NSORDER /etc/environment /etc/netsvc.conf
/etc/environment:NSORDER=bind,local

2. Check if DNS is configured

# cat /etc/resolv.conf
nameserver 172.16.12.203
domain prace.commvault.net

3. Check entries in the local /etc/host file

# grep -v ^# /etc/hosts
127.0.0.1               loopback localhost      # loopback (lo0) name/address
172.16.12.242   ibmaix02        # NIM Master
172.16.12.240   ibmaix01        # NIM Client

Configuring file size limits

1-Touch for AIX subclient uses the mksysb utility to back up the root volume group along with the information for all the affected volume groups. It may happen that the mksysb file will be larger than the file size limit is set to. To set the file size limits to unlimited set the following values in /etc/security/limits

default:

fsize = -1
core = -1
cpu = -1
data = 262144
rss = 65536
stack = 65536
nofiles = 2000

NIM Master setup

In this scenario, we will use the EZNIM option to configure the NIM Master environment on ibmaix02 for the first time. The configuration involves creating the NIM database and populating it with several default entries. Several basic NIM resources will then be created and defined in the NIM database. To successfully complete this task the AIX 5.3-ML 08 media must be placed in the DVD ROM drive.

Log on as root and type:

# smitty eznim

Select Configure as NIM Master

Select: Setup the NIM Master environment

Verify default selections for software source, volume group, and file system are correct for your environment. In this scenario we will leave everything at the default settings.

Before pressing enter Enter ensure that the AIX 5.3-ML08 installation media is in the DVD ROM drive. Pressing Enter will start the configuration of the NIM Master environment. After finishing the NIM Master setup you can view the resource that have been created with the show the NIM environment or issue lsnim from command line.

# lsnim
master                 machines        master
boot                   resources       boot
nim_script             resources       nim_script
master_net             networks        ent
5300-08master_sysb     resources       mksysb
master_net_conf        resources       resolv_conf
5300-08bid_ow          resources       bosinst_data
530lpp_res             resources      lpp_source
530spot_res            resources       spot
basic_res_grp          groups          res_group

From the output of the command you can see the NIM object name, the NIM object class and the NIM object type of the created objects. One of the fundamental resource in the NIM environment is the SPOT resources. The SPOT resources provides:

/usr file ssystem
AIX kernel
executable commands
shared libraries

To be able to restore an AIX 5.3-ML06 client our NIM master must control a SPOT resources that has the same oslevel_r then the client machine where you want to enable the 1-Touch recovery.

Check if the NIM Master controls a SPOT resource with the same oslevel of the client

Log on to the client and issue

# oslevel -r
5300-06

Log on to the NIM master server and issue:

Looking at the oslevel_r record we can conclude that the NIM Master is not configured to successfull run a 1-Touch recovery of the 5.300-06 client.

Adding a lpp_source for 5.300-06 clients

To create a complete lpp_source that contains the AIX base -installation file sets you need the AIX base-installation media. During the NIM master setup there is already one lpp_source on the master that contains the file sets to install AIX 5.300-08 on an AIX machine.

Insert the AIX 5.300-06 installation media in the DVDROM and issue the following command to add an 5.300-06 lpp_source to the NIM Master.

# nim -o define -t lpp_source -a source=/dev/cd0 \
> -a server=master -a location=/export/eznim/530-06lpp_res 530-06_lpp_res

Preparing to copy install images (this will take several minutes)...

After the command finished you can check if the lpp_source has been created on the NIM Master.

# lsnim -l -t lpp_source
530lpp_res:
   class       = resources
   type        = lpp_source
   arch        = power
   Rstate      = ready for use
   prev_state = unavailable for use
   location    = /export/eznim/lpp_source/530lpp_res
   simages     = yes
alloc_count = 0
   server      = master
530-06_lpp_res:
   class       = resources
   type        = lpp_source
   arch        = power
   Rstate      = ready for use
   prev_state = unavailable for use
   location    = /export/eznim/530-06lpp_res
   simages     = yes
   alloc_count = 0
   server      = master

Creating a SPOT location from the newly created lpp_source

Everything that a machine requires in a /usr file system, such as the AIX® kernel, executable commands, libraries, and applications are included in the SPOT. For a 1-Touch recovery we need a SPOT resource that is not tight to any mksysb. The next step now is creating the SPOT resource for the 530-06 clients from the LPP resource created in the previous step. On the NIM-Master issue the following command:

# nim -o define -t spot -a server=master \
-a location=/export/eznim/530-06spot_res -a source=530-06_lpp_res \
-a installp_flags=-aQg spot530-06spot_res

After the command succeeded you can verify that the additional SPOT resources is available:

# lsnim -l -t spot
530spot_res:
   class         = resources
   type          = spot
   plat_defined = chrp
   arch          = power
   bos_license   = yes
   Rstate        = ready for use
   prev_state    = verification is being performed
   location      = /export/eznim/spot/530spot_res/usr
   version       = 5
   release       = 3
   mod           = 8
   oslevel_r     = 5300-08
   alloc_count   = 0
   server        = master
   if_supported = chrp.mp ent
   Rstate_result = success
spot530-06spot_res:
   class         = resources
   type          = spot
plat_defined = chrp
   arch          = power
   bos_license   = yes
   Rstate        = ready for use
   prev_state    = verification is being performed
   location      = /export/eznim/530-06spot_res/spot530-06spot_res/usr
   version       = 5
   release       = 3
   mod           = 0
   oslevel_r     = 5300-06
   alloc_count   = 0
   server        = master
   if_supported = chrp.mp ent
   Rstate_result = success

Looking at the oslevel_r record shows the operating system version for the available SPOT resources on the NIM-Master.

Space considerations for 1-Touch recovery

During a full backup for a client configured for 1-Touch for AIX, the default subclient uses the mksysb utility to back up the root volume group along with the information for all the affected volume groups. The mksysb utility backs up all the files on the root volume group including data files.

To check the available disk space on the NIM-Master ibmaix02 type:

# df -m /export/eznim
Filesystem MB blocks Free %Used Iused %Iused Mounted on
/dev/fslv00 3200.00 188.39 95% 14233 25% /export/eznim

To determine the rootvg size of the 1-Touch client ibmaix01 type:

# du -g
2.20

To perform. a 1-Touch recovery of the given client the /export/eznim needs to be at least 2.20GB + 30MB. To increase the filesystem holding the NIM resources type the following:

# chfs -a size=+3G /export/eznim
Filesystem size changed to 12845056
# df -g /export/eznim
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/fslv00 6.12 3.18 49% 14233 2% /export/eznim

As you can see from the output of the df command the filesystem size increased by 3GB.

NIM-Client Setup

Check name resolution order on the NIM Client. Problems may result if the NIM master and the NIM clients use different orders when querying sources for name resolution. Problems may also arise if a name service is available to one machine but not to another, causing different name resolution sources to be used.

During a 1-Touch recover only bind, hosts files are available for resolving host names.

1. Check if NSorder environment variable is set

# grep ^NSORDER /etc/environment /etc/netsvc.conf
/etc/environment:NSORDER=bind,local

2. Check if DNS is configured

# cat /etc/resolv.conf
nameserver 172.16.12.203
domain prace.commvault.net

3. Check entries in the local /etc/host file

# grep -v ^# /etc/hosts
127.0.0.1               loopback localhost      # loopback (lo0) name/address
172.16.12.242           ibmaix02        # NIM master
172.16.12.240           ibmaix01        # NIM Client

Checking file size limits

# ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         131072
stack(kbytes)        32768
memory(kbytes)       32768
coredump(blocks)     unlimited
nofiles(descriptors) 2000
threads(per process) unlimited
processes(per user) unlimited

Verify that if the bos.sysmgt.nim.client fileset is installed.

#lslpp -L bos.sysmgt.nim.client
Fileset                      Level State Type Description (Uninstaller)
----------------------------------------------------------------------------
bos.sysmgt.nim.client      6.1.1.1    C     F    Network Install Manager -
                                                   Client Tools

State codes:
A -- Applied.
B -- Broken.
C -- Committed.
E -- EFIX Locked.
O -- Obsolete. (partially migrated to newer version)
? -- Inconsistent State...Run lppchk -v.

Type codes:
F -- Installp Fileset
P -- Product
C -- Component
T -- Feature
R -- RPM Package
E -- Interim Fix

AIX clients should have configured network cards so they can boot from a NIM-master.

1-Touch Setup

To enable 1-Touch recovery on ibmaix01 the 1-Touch Boot Server Agent must be installed on ibmaix02. After installing the 1-Touch boot server Agent software on the NIM-Master you can enable 1-Recovery in the CommCell Console on the client. Ensure that the AIX File System iDataAgent is installed on the client computer. If you do not see the 1-Touch Recovery tab on the sublient "Properties" you need to log off and login again into the CommCell Console or press F5 in the CommCell Browser window. Prior of configuring a subclient for 1-Touch ensure that Simpana is installed on the rootvg on the client in question.

Check if Simpana is installed on the rootvg on ibmaix01

1. Type the following commnad in a terminal session:

ibmaix01# simpana list
+----------------------------------+-------+-----------------------------------+
| Service name                     | PID | Service command                   |
+----------------------------------+-------+-----------------------------------+
| cvd                              | 27457 | /opt/simpana/Base/cvd             |
|                                  | 4     |                                   |
+----------------------------------+-------+-----------------------------------+
| EvMgrC                           | 22543 | /opt/simpana/Base/EvMgrC          |
|                                  | 2     |                                   |
+----------------------------------+-------+-----------------------------------+

Looking at the Service Command Column you know need to check if the path to the executable resides on the rootvg.

2. To display all volume groups type:

ibmaix01# lsvg
rootvg

3. To list all logical volume information including mount points type:

ibmaix01# lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs     PPs     PVs LV STATE      MOUNT POINT
hd5                 boot       1       1       1    closed/syncd N/A
hd6                 paging     4       4       1    open/syncd    N/A
hd8                 jfs2log    1       1       1    open/syncd    N/A
hd4                 jfs2       2       2       1    open/syncd    /
hd2                 jfs2       13      13      1    open/syncd    /usr
hd9var              jfs2       9       9       1    open/syncd    /var
hd3                 jfs2       5       5       1    open/syncd    /tmp
hd1                 jfs2       1       1       1    open/syncd    /home
hd10opt             jfs2       9       9       1    open/syncd    /opt
hd11admin           jfs2       1       1       1    open/syncd    /admin
fwdump            jfs2       2       2       1    open/syncd   /var/adm/ras/platform

Looking at the row hd10opt we can conclude that Simpana resides on the rootvg on this machine.

Configure the Subclient for 1-Touch

To configure the subclient for 1-Touch:

1. From the CommCell Browser, right-click the appropriate (usually the default) subclient and then click "Properties" from the shortcut menu.

2. From the Subclient Properties (1-Touch Recovery) tab, click 1-Touch Recovery

3. Accept or select the name of the 1-Touch Server in the 1-Touch Server field.

1-Touch server directory

1-Touch server directory equals to the file system for resources specified during the eznim configuration earlier. In this scenario it must be set to /export/eznim.