Network Information Manager Standards

Features

NIM permits the installation and maintenance of AIX, its basic operating system, and additional software and fixes that may be applied over a period of time over token-ring, ethernet, FDDI, and ATM net works.

NIM also permits the customization of machines both during and after installation . As a result, NIM has eliminated the reliance on tapes and CD-ROMs for software installation; the onus, in NIM’sase, is on the network. NIM will allow one machine to act as a master in the environment. This machine will be responsible for storing information about the clients it supports, the resources it or other servers provide to these clients, and the networks on which they operate.

Benefits

Some of the benefits of NIM are:

• Manageability - It allows central localization of software installation images, thus, making backup and administration easier.
• Central Administration - Administrators can install remote AIX machines without having to physically attend them.
• Scalability - You can install more than one machine at a time, implement a group strategy of machines and resources, and choose how many machines to install at a time.
• Usability - VSM GUI for NIM has been improved so that, now, it can be used to configure NIM groups.
• Availability - Where server down time means loss of profits, NIM provides you with a backup image of all your servers. A new server can be set up and running in just over an hour.
• Non-prompted installation - NIM provides a function to install systems without having to go to the machine, thus, avoiding the sneaker net method.

Installations can be initiated by either the client or master at a convenient time. For example, if a client is unavailable at the time of the install, you can initiate an install when it is back on line, or, if there is less traffic on your network at a certain time, you can initiate the installations to occur then.

It is a relatively faster means of installation than tape or CD-ROM.

NIM provides greater functionality than CD-ROM or tape. Among other things, it allows you to customize an install, initiate a non-prompted install, or install additional software.

TriParadigm's NIM Environment

NIM Server Machines

Each data center currently has one NIM server which serves various resources to the client machines in that data center. Some cross data center communication occurs for the purpose of disaster recovery. The NIM Server machines are:

• Nashville Data Center: mtxapnim01.triparadigm.com
• Van Data Center: pppapnim01.triparadigm.com

No NIM Alternate-Master servers are currently configured, but will be implemented soon. This capability will provide automated redundancy of NIM resources between data centers.

NIM Client Machines

All AIX and linux machines in the TriParadigm enviroment utilize resources originating from the NIM Servers.

NIM Resources

The resources available from the NIM servers include operating systems, OS updates, OS backup and restores, clustering software, applications, device drivers, firmware, and disaster recovery services and information. These resources can be delivered from any NIM server to any NIM client in any TriParadigm data center. Some of the resources available on the NIM Servers include:

• AIX
• Linux
• mksysb repository
• AIX Maintenance Levels
• AIX APAR's
• AIX Fixes
• HACMP
• HACMP-ES
• MQ Series Software
• Tivoli Storage Manager Software
• Linux Toolbox for AIX
• freeware
• Hitachi Sofware
• Performance monitoring software
• firmware updates
• Disaster Recovery hub for AIX

NIM Server Operations

Using the resources previously listed, a wide variety of operations may be peformed on or by a NIM client. These operations include the ability to perform a bare-metal install of a new operating sytem or backup. Other operating system installation options are also available, dependent only upon what the system administrator is attempting to accomplish. For example, using the NIM server, a backup of a production machine can be performed, the backup restored to an alternate-disk on the same production machine, and the operating system on the alternate-disk can be updated to the latest maintenance level, all without interuption or downtime to the production machine. Some of the operations that are regularly performed utilizing the resources provided by the NIM servers include:

NIM Server Structure

To maintain structure and order on the NIM Servers, a specific directory hierarchy has been adopted and utilized. This structure must be observed and practiced when making modifications to the resources provided by the NIM Servers.

The top level directory for storage of NIM resources begins at the directory:

/export

Each resource class provided by the NIM server should exist as a subdirectory under /export. The list of valid NIM resource classes are:

• boot: represents the network boot resource
• nim_script: directory containing customization scripts created by NIM
• spot: Shared Product Object Tree - equivalent to /usr/filesystem
• root: parent directory for client / (root) directories
• paging: parent directory for client paging files
• dump: parent directory for client dump files
• home: parent directory for client /home directories
• shared_home: home directory shared by clients
• tmp: parent directory for client /tmp directories
• exclude_files: files to be excluded when creating a mksysb or savevg image
• lpp_source: source device for optional product images
• installp_bundle: installp bundle file
• fix_bundle: fix (keyword) input file for the cust or fix_query operation
• bosinst_data: config file used during base system installation
• image_data: config file used during base system installation
• vg_data: config file used during volume group restoration
• mksysb: a mksysb image
• script: an executable file which is executed on a client
• resolv_conf: configuration file for name-server information
• savevg: a savevg image
• adapter_def: directory containing secondary adapter definition files
• fb_script: an executable script added to /etc/firstboot and run at first reboot after bos install to configure devices.

Not all NIM resource classes are currently utilized, however when a new resource is utilized, this guide should be followed for the directory naming structure.

The currently implemented NIM resource classes and class instances follow. Naming conventions for class instances are included here and should be adhered to when new class instances are created:

Currently implemented NIM Resource's

---

/export/bosinst_data

The "bosinst_data" resource class is for the configuration files used during the AIX base operating system installation. The default instance shall be named "bosinst_data". Additional instances shall be suffixed with unique identifying information such as the AIX Operating System version number, machine name, user name, application name, etc. Example instances of the "bosinst_data" resource class and file follow:

bosinst_data Resource Names and Subdirectories

Resource Type	Resource Identifier	Version ID	Maintenance Level	NIM Resource Name	Storage Location
Base OS Install Data	bosinst_data	Default		bosinst_data	/export/bosinst_data/bosinst_data
Base OS Install Data	bosinst_data	noprompt		bosinst_data_noprompt	/export/bosinst_data/bosinst_data_noprompt
Base OS Install Data	bosinst_data	mtxtriparadigmapp52		bosinst_data_mtxtriparadigmapp52	/export/bosinst_data/bosinst_data_mtxtriparadigmapp52
Base OS Install Data	bosinst_data	egate		bosinst_data_egate	/export/bosinst_data/bosinst_data_egate
Base OS Install Data	bosinst_data	4330		bosinst_data_4330	/export/bosinst_data/bosinst_data_4330
Base OS Install Data	bosinst_data	4330	10	bosinst_data_4330-10	/export/bosinst_data/bosinst_data_4330-10
Base OS Install Data	bosinst_data	4330	11	bosinst_data_4330-11	/export/bosinst_data/bosinst_data_4330-11
Base OS Install Data	bosinst_data	4330	09	bosinst_data_4330-09	/export/bosinst_data/bosinst_data_4330-09
Base OS Install Data	bosinst_data	4330	10.5	bosinst_data_4330-10_5	/export/bosinst_data/bosinst_data_4330-10_5
Base OS Install Data	bosinst_data	5100		bosinst_data_5100	/export/bosinst_data/bosinst_data_5100
Base OS Install Data	bosinst_data	5100	02	bosinst_data_5100-02	/export/bosinst_data/bosinst_data_5100-02
Base OS Install Data	bosinst_data	5200		bosinst_data_5200	/export/bosinst_data/bosinst_data_5200
Base OS Install Data	bosinst_data	5200	01	bosinst_data_5200-01	/export/bosinst_data/bosinst_data_5200-01
Base OS Install Data	bosinst_data	5200	02	bosinst_data_5200-02	/export/bosinst_data/bosinst_data_5200-02
Base OS Install Data	bosinst_data	5200	04	bosinst_data_5200-04	/export/bosinst_data/bosinst_data_5200-04
Base OS Install Data	bosinst_data	5200	05	bosinst_data_5200-05	/export/bosinst_data/bosinst_data_5200-05
Base OS Install Data	bosinst_data	5300		bosinst_data_5300	/export/bosinst_data/bosinst_data_5300
Base OS Install Data	bosinst_data	5300	01	bosinst_data_5300-01	/export/bosinst_data/bosinst_data_5300-01

When adding an instance of this class to the NIM server, the name of the instance shall contain the prefix "bosinst_data" followed by an underscore "_" and will be suffixed with a unique identifier. The file names used to store the resource shall correspond exactly with the name used to define the resource in the NIM server.

---

/export/image.data

The "image_data" resource class is for the configuration files used during the AIX base operating system installation. The default instance shall be named "image_data". Additional instances shall be suffixed with unique identifying information such as the AIX Operating System version number, machine name, user name, application name, etc. Example instances of the "image_data" resource class and file follow:

image_data Resource Names and Subdirectories

Resource Type	Resource Identifier	Version ID	Maintenance Level	NIM Resource Name	Storage Location
Base OS Install Data	image_data	Default		image_data	/export/image_data/image_data
Base OS Install Data	image_data	noprompt		image_data_noprompt	/export/image_data/image_data_noprompt
Base OS Install Data	image_data	mtxtriparadigmapp52		image_data_mtxtriparadigmapp52	/export/image_data/image_data_mtxtriparadigmapp52
Base OS Install Data	image_data	egate		image_data_egate	/export/image_data/image_data_egate
Base OS Install Data	image_data	4330		image_data_4330	/export/image_data/image_data_4330
Base OS Install Data	image_data	4330	10	image_data_4330-10	/export/image_data/image_data_4330-10
Base OS Install Data	image_data	4330	11	image_data_4330-11	/export/image_data/image_data_4330-11
Base OS Install Data	image_data	4330	09	image_data_4330-09	/export/image_data/image_data_4330-09
Base OS Install Data	image_data	4330	10.5	image_data_4330-10_5	/export/image_data/image_data_4330-10_5
Base OS Install Data	image_data	5100		image_data_5100	/export/image_data/image_data_5100
Base OS Install Data	image_data	5100	02	image_data_5100-02	/export/image_data/image_data_5100-02
Base OS Install Data	image_data	5200		image_data_5200	/export/image_data/image_data_5200
Base OS Install Data	image_data	5200	01	image_data_5200-01	/export/image_data/image_data_5200-01
Base OS Install Data	image_data	5200	02	image_data_5200-02	/export/image_data/image_data_5200-02
Base OS Install Data	image_data	5200	04	image_data_5200-04	/export/image_data/image_data_5200-04
Base OS Install Data	image_data	5200	05	image_data_5200-05	/export/image_data/image_data_5200-05
Base OS Install Data	image_data	5300		image_data_5300	/export/image_data/image_data_5300
Base OS Install Data	image_data	5300	01	image_data_5300-01	/export/image_data/image_data_5300-01

When adding an instance of this class to the NIM server, the name of the instance shall contain the prefix "image_data" followed by an underscore "_" and will be suffixed with a unique identifier. The file names used to store the resource shall correspond exactly with the name used to define the resource in the NIM server.

---

/export/lpp_source

Software filesets and updates are identified in the NIM server as an "lpp_source". The top level directory location to be used for storage of these resources will be "/export/lpp_source". The storage location of these resources will be further divided into subdirectories such as "aix", "hacmp", "hitachi", etc.

---

/export/lpp_source/aix

The "lpp_source" resources stored in the "aix" subdirectory shall be those that are directly related to the AIX operating system. The "lpp_source" resources stored in this directory may consist of a number of different types including the AIX operating system, AIX device drivers, AIX expansion packs, Partition Load Manager, Virtual I/O Server, and others. The following identifiers will be used when defining the lpp_source of this type on the NIM Server and when creating directories to store the lpp_source on the NIM Server:

• aix: AIX Operating System
• aixdoc: AIX Documentation
• dev: AIX Device Drivers
• exppack: AIX Expansion Pack
• plm: Partition Load Manager
• vio: Virtual I/O Server

Each AIX "lpp_source" resource shall be stored in a subdirectory. The name of the resource and subdirectory shall have the following specific format:

The resource identifier (aix, aixdoc, dev, exppack, plm, vio) followed by an underscore "_", followed by the four(4) digit version number of the resource. If the version number of the resource is less than four(4) digits, add zero's(0) to make it a four(4) digit number. If the "lpp_source" resource is a maintenance level, then add a dash "-" followed by the two(2) digit maintenance level number. Base level filesets will not have a maintenance level associated with them. The directory location names for the resource shall correspond exactly with the resource name used in the NIM server.

AIX lpp_source Resource Names and Subdirectories

Resource Type	Resource Identifier	Version Number	Maintenance Level	NIM Resource Name	Storage Location
AIX Operating System	aix	4330		aix_4330	/export/lpp_source/aix/aix_4330
AIX Operating System	aix	4330	10	aix_4330-10	/export/lpp_source/aix/aix_4330-10
AIX Operating System	aix	4330	11	aix_4330-11	/export/lpp_source/aix/aix_4330-11
AIX Operating System	aix	4330	09	aix_4330-09	/export/lpp_source/aix/aix_4330-09
AIX Operating System	aix	4330	10.5	aix_4330-10_5	/export/lpp_source/aix/aix_4330-10_5
AIX Operating System	aix	5100		aix_5100	/export/lpp_source/aix/aix_5100
AIX Operating System	aix	5100	02	aix_5100-02	/export/lpp_source/aix/aix_5100-02
AIX Operating System	aix	5200		aix_5200	/export/lpp_source/aix/aix_5200
AIX Operating System	aix	5200	01	aix_5200-01	/export/lpp_source/aix/aix_5200-01
AIX Operating System	aix	5200	02	aix_5200-02	/export/lpp_source/aix/aix_5200-02
AIX Operating System	aix	5200	04	aix_5200-04	/export/lpp_source/aix/aix_5200-04
AIX Operating System	aix	5200	05	aix_5200-05	/export/lpp_source/aix/aix_5200-05
AIX Operating System	aix	5300		aix_5300	/export/lpp_source/aix/aix_5300
AIX Operating System	aix	5300	01	aix_5300-01	/export/lpp_source/aix/aix_5300-01
AIX Documentation	aixdoc	5300		aixdoc_5300	/export/lpp_source/aix/aixdoc_5300
AIX Device Drivers	dev	4330		dev_4330	/export/lpp_source/aix/dev_4330
AIX Device Drivers	dev	5100		dev_5100	/export/lpp_source/aix/dev_5100
AIX Device Drivers	dev	5200		dev_5200	/export/lpp_source/aix/dev_5200
AIX Expansion Pack	exppack	5300		exppack_5300	/export/lpp_source/aix/exppack_5300
Partition Load Manager	plm	1100		plm_1100	/export/lpp_source/aix/plm_1100
Virtual I/O Server	vio	1100		vio_1100	/export/lpp_source/aix/vio_1100

---

/export/lpp_source/hacmp

The "lpp_source" resources stored in the "hacmp" subdirectory shall be those that are directly related to the HACMP Clustering Software, this does NOT include HACMP ES. The "lpp_source" resources stored in this directory will consist of a number of different versions of the HACMP Clustering software.

Each HACMP "lpp_source" resource shall be stored in a subdirectory. The name of the resource and subdirectory shall have the following specific format:

The resource identifier (hacmp) followed by an underscore "_", followed by the four(4) digit version number of the resource. If the version number of the resource is less than four(4) digits, add zero's(0) to make it a four(4) digit number. If the "lpp_source" resource is a maintenance level, then add a dash "-" followed by the two(2) digit maintenance level number. Base level filesets will not have a maintenance level associated with them. The directory location names for the resource shall correspond exactly with the resource name used in the NIM server.

HACMP lpp_source Resource Names and Subdirectories

Resource Type	Resource Identifier	Version Number	Maintenance Level	NIM Resource Name	Storage Location
HACMP	hacmp	4500		hacmp_4500	/export/lpp_source/hacmp/hacmp_4500

---

/export/lpp_source/hacmpes

The "lpp_source" resources stored in the "hacmpes" subdirectory shall be those that are directly related to the HACMP ES Clustering Software. The "lpp_source" resources stored in this directory will consist of a number of different versions of the HACMP ES Clustering software.

Each HACMP ES "lpp_source" resource shall be stored in a subdirectory. The name of the resource and subdirectory shall have the following specific format:

The resource identifier (hacmpes) followed by an underscore "_", followed by the four(4) digit version number of the resource. If the version number of the resource is less than four(4) digits, add zero's(0) to make it a four(4) digit number. If the "lpp_source" resource is a maintenance level, then add a dash "-" followed by the two(2) digit maintenance level number. Base level filesets will not have a maintenance level associated with them. The directory location names for the resource shall correspond exactly with the resource name used in the NIM server.

HACMP ES lpp_source Resource Names and Subdirectories

Resource Type	Resource Identifier	Version Number	Maintenance Level	NIM Resource Name	Storage Location
HACMP ES	hacmpes	4400		hacmpes_4400	/export/lpp_source/hacmpes/hacmpes_4400
HACMP ES	hacmpes	4410		hacmpes_4410	/export/lpp_source/hacmpes/hacmpes_4410
HACMP ES	hacmpes	4410	01	hacmpes_4410-01	/export/lpp_source/hacmpes/hacmpes_4410-01
HACMP ES	hacmpes	4419		hacmpes_4419	/export/lpp_source/hacmpes/hacmpes_4419
HACMP ES	hacmpes	4500		hacmpes_4500	/export/lpp_source/hacmpes/hacmpes_4500
HACMP ES	hacmpes	4507		hacmpes_4507	/export/lpp_source/hacmpes/hacmpes_4507
HACMP ES	hacmpes	5100		hacmpes_5100	/export/lpp_source/hacmpes/hacmpes_5100
HACMP ES	hacmpes	5200		hacmpes_5200	/export/lpp_source/hacmpes/hacmpes_5200
HACMP ES	hacmpes	5200	01