Home About BC DR HA Support Training Download
You are here: Home/ Business-Continuity/ Please Login or Register

Additional documents of interest

  • Successful Business Continuity - Part 1 - Users and Groups
    This article was published in the April 2005 issue of AIX Update magazine and discusses system administration needs and requirements oriented around users and groups. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters, such as user names, group names, UID and GID numbers.
  • Successful Business Continuity - Part 2 - Machine and Host Names
    This article was published in the May 2005 issue of AIX Update magazine and discusses naming structures for machines, systems, adapters, and aliases. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters.
  • Successful Business Continuity - Part 3 - Volume Names
    This article was published in the December 2005 issue of AIX Update magazine and discusses naming structures for volume groups, logical volumes, log logical volumes, directory mount points, etc. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters.
  • Successful Business Continuity - Part 4 - MQ Series, Startup/Shutdown Scripts, Error Processing
    This article was published in the April 2006 issue of AIX Update magazine and discusses how to implement AIX in an environment dedicated to business continuity. The topic of this article is the assignment of MQ Series queue names and aliases, resource group startup and shutdown script names (Application startup/shutdown script names), error logging, and error notification.
  • Successful Business Continuity - Part 5 - Miscellaneous topics
    This article was published in the August 2006 issue of AIX Update magazine and discusses how to implement AIX in an environment dedicated to business continuity. A variety of topics is discussed in this article including automated documentation generation and management.
  • Automated Microcode Management System
    One of the most difficult administration tasks in an AIX environment is attempting to keep the firmware and microcode up-to-date. Mt Xia has devised an automated method of gathering the Microcode information, determining which microcode needs to be updated, generating reports, and uploading the required microcode updates to each individual system.
  • Calculating the size of a Virtual Processor
    This document describes the algorithms used to calculate the size of a virtual processor when using shared processors in an LPAR. The IBM documentation describes how to calculate CPU utilization, NOT how to size for configuration, this document clarifies this process. A description of the HMC input fields for the processor tab is included.
  • Basics of Partition Load Manager Setup
    This presentation was provided by Ron Barker from IBM regarding the PLM Basic setup.
  • ppt
  • pdf
  • 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.


    Mt Xia'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:

    • Boston Data Center: bosapnim01.tu.com
    • Dallas Data Center: dalapnim01.tu.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 Mt Xia 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 Mt Xia 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:

  • Network boot server
  • AIX operating system installation
  • AIX operating system maintenance level updates
  • AIX operating system APAR updates
  • AIX operating system efix updates
  • AIX mksysb repository
  • AIX mksysb installation
  • AIX alt-clone installation
  • AIX alt-clone maintenance level updates
  • AIX alt-disk installation
  • Linux operating system installation
  • Linux operating rpm updates
  • Oracle database installation
  • Application installation and updates
  • Script Server
  • Disaster Recovery information gathering
  • Disaster Recovery information distribution
  • Disaster Recovery automated documentation generator

  • 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 bosmtxapp52   bosinst_data_bosmtxapp52 /export/bosinst_data/bosinst_data_bosmtxapp52
    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 bosmtxapp52   image_data_bosmtxapp52 /export/image_data/image_data_bosmtxapp52
    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 hacmpes_5200-01 /export/lpp_source/hacmpes/hacmpes_5200-01


  • /export/lpp_source/hitachi

    The "lpp_source" resources stored in the "hitachi" subdirectory shall be those that are directly related to the Hitachi SAN Subsystems. The "lpp_source" resources stored in this directory may consist of a number of different types including the AIX ODM software, DLM Drivers, HDLM Drivers, Hitachi's MPIO Drivers, and Hitachi's performance monitoring software. 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:

    • aixodm: Hitachi's AIX ODM Software
    • dlm: DLM Drivers
    • hdlm: HDLM Drivers
    • hdsmpio: Hitachi's MPIO Drivers
    • lunstat: Performance Monitoring

    Each Hitachi "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 (aixodm, dlm, hdlm, hdsmpio, lunstat) followed by an underscore "_", followed by the four(4) digit version number of the resource. The version number of the Hitachi filesets should be taken from the filenames, NOT from the media on which the software was delivered. 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.

    Hitachi lpp_source Resource Names and Subdirectories
    Resource
    Type
    Resource
    Identifier
    Version
    Number
    Maintenance
    Level
    NIM
    Resource Name
    Storage
    Location
    AIX ODM Software aixodm 5000   aixodm_5000 /export/lpp_source/hitachi/aixodm_5000
    AIX ODM Software aixodm 5001   aixodm_5001 /export/lpp_source/hitachi/aixodm_5001
    AIX ODM Software aixodm 5002   aixodm_5002 /export/lpp_source/hitachi/aixodm_5002
    AIX ODM Software aixodm 5004   aixodm_5004 /export/lpp_source/hitachi/aixodm_5004
    AIX ODM Software aixodm 5014   aixodm_5014 /export/lpp_source/hitachi/aixodm_5014
    DLM Drivers dlm 2430   dlm_2430 /export/lpp_source/hitachi/dlm_2430
    DLM Drivers dlm 2530   dlm_2530 /export/lpp_source/hitachi/dlm_2530
    HDLM Drivers hdlm 5024   hdlm_5024 /export/lpp_source/hitachi/hdlm_5024
    HDLM Drivers hdlm 5112   hdlm_5112 /export/lpp_source/hitachi/hdlm_5112
    HDLM Drivers hdlm 5231   hdlm_5231 /export/lpp_source/hitachi/hdlm_5231
    HDLM Drivers hdlm 5251   hdlm_5251 /export/lpp_source/hitachi/hdlm_5251
    HDLM Drivers hdlm 5411   hdlm_5411 /export/lpp_source/hitachi/hdlm_5411
    Hitachi MPIO Driver hdsmpio 5400   hdsmpio_5400 /export/lpp_source/hitachi/hdsmpio_5400
    Performance Monitoring lunstat 122   lunstat_122 /export/lpp_source/hitachi/lunstat_122


  • /export/lpp_source/mqseries

    The "lpp_source" resources stored in the "mqseries" subdirectory shall be those that are directly related to the MQ Series software. Each MQ Series "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 (mq) 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.

    MQ Series lpp_source Resource Names and Subdirectories
    Resource
    Type
    Resource
    Identifier
    Version
    Number
    Maintenance
    Level
    NIM
    Resource Name
    Storage
    Location
    MQ Series mq 5300   mq_5300 /export/lpp_source/mqseries/mq_5300


  • /export/lpp_source/performance

    The "lpp_source" resources stored in the "performance" subdirectory shall be those that are related to performance monitoring and management. Each Performance related "lpp_source" resource shall be stored in a subdirectory. The name of the resource and subdirectory will depend upon the resource and may deviate from those identified in this document. The resource identifiers shall have the following specific format:

    The resource identifier (perfaide, perftoolbox, etc) 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.

    Performance related lpp_source Resource Names and Subdirectories
    Resource
    Type
    Resource
    Identifier
    Version
    Number
    Maintenance
    Level
    NIM
    Resource Name
    Storage
    Location
    Performance perfaide 3100   perfaide_3100 /export/lpp_source/performance/perfaide_3100
    Performance perftoolbox 3100   perftoolbox_3100 /export/lpp_source/performance/perftoolbox_3100


  • /export/lpp_source/tsm

    The "lpp_source" resources stored in the "tsm" subdirectory shall be those that are directly related to the Tivoli Storage Manager(TSM). The "lpp_source" resources stored in this directory will consist of a number of different versions of the TSM software.

    Each TSM "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 (tsmclient,tsmserver) 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.

    Tivoli Storage Manager related lpp_source Resource Names and Subdirectories
    Resource
    Type
    Resource
    Identifier
    Version
    Number
    Maintenance
    Level
    NIM
    Resource Name
    Storage
    Location
    TSM tsmclient 42125   tsmclient_42125 /export/lpp_source/tsm/tsmclient_42125
    TSM tsmclient 4221   tsmclient_4221 /export/lpp_source/tsm/tsmclient_4221
    TSM tsmclient 5162   tsmclient_5162 /export/lpp_source/tsm/tsmclient_5162


  • /export/mksysb

    The "mksysb" resource class is for AIX mksysb backups of the "rootvg" volume group. "mksysb" resources can be used by the NIM server to perform a new installation or restore a machine to a known state. The "mksysb" images are specific to an individual machine at a particular point in time.

    Each "mksysb" resource shall be stored under the "/export/mksysb" subdirectory. The name of the resource shall have the following specific format:

    The resource identifier (mksysb) followed by an underscore "_", followed by the machine name from which the "mksysb" image was generated. If multiple versions are desired, follow the machine name with an underscore "_", followed by the 4 digit year, 2 digit month number, 2 digit day of the month, 2 digit hour of the day, 2 digit minute of the hour, and 2 digit seconds. If this level of granularity is not required, the date/time identifer can be truncated as necessary, but should remain in the stated sequence and format.

    mksysb Resource Names and Subdirectories
    Resource
    Type
    Resource
    Identifier
    Originating
    Machine
    Date/Time
    Stamp
    NIM
    Resource Name
    Storage
    Location
    Backup mksysb dalaaega01   mksysb_dalaaega01 /export/mksysb/mksysb_dalaaega01
    Backup mksysb dalaaega02   mksysb_dalaaega02 /export/mksysb/mksysb_dalaaega02
    Backup mksysb dalpocdb01   mksysb_dalpocdb01 /export/mksysb/mksysb_dalpocdb01
    Backup mksysb bosmtxapp80 20050412 mksysb_bosmtxapp80_20050412 /export/mksysb/mksysb_bosmtxapp80_20050412
    Backup mksysb bosmtxapp80 20050414 mksysb_bosmtxapp80_20050414 /export/mksysb/mksysb_bosmtxapp80_20050414


  • /export/resolv_conf

    The "resolv_conf" resource class is the configuration file for the Domain Name Server (DNS) information. A instance of this class shall be defined for each data center and may contain DNS information for multiple data centers. Example instances of the "resolv_conf" resource class and file follow:

    resolv_conf Resource Names and Subdirectories
    Resource
    Type
    Resource
    Identifier
    Datacenter
    ID
    Maintenance
    Level
    NIM
    Resource Name
    Storage
    Location
    DNS Resolution resolv_conf Default   resolv_conf /export/resolv_conf/resolv_conf
    DNS Resolution resolv_conf dal   resolv_conf_dal /export/resolv_conf/resolv_conf_dal
    DNS Resolution resolv_conf bos   resolv_conf_bos /export/resolv_conf/resolv_conf_bos

    When adding an instance of this class to the NIM server, the name of the instance shall contain the prefix "resolv_conf" 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/spot

    The "spot" resource class is for the bootable images to use for network booting a machine and OS installation. Each "spot" image is specific to a particular version and maintenance level of AIX or other operating system and shall be identified accordingly. The resource identifier for the AIX "spot" images is "aixspot". The reason "aixspot" is used for this identifier instead of just "spot" is because Linux spots are also be included in this resource class and are identified by the brand of Linux such as "susespot", "redhatspot", "debianspot", etc. These resource identifiers shall be be used to identify each instance as follows:

    The resource identifier (aixspot) followed by an underscore "_", followed by the four(4) digit version number of the AIX OS 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.

    Spot Resource Names and Subdirectories
    Resource
    Type
    Resource
    Identifier
    Version
    Number
    Maintenance
    Level
    NIM
    Resource Name
    Storage
    Location
    AIX Spot aixspot 4330   aixspot_4330 /export/spot/aixspot_4330
    AIX Spot aixspot 5100   aixspot_5100 /export/spot/aixspot_5100
    AIX Spot aixspot 5200   aixspot_5200 /export/spot/aixspot_5200
    AIX Spot aixspot 5200 02 aixspot_5200-02 /export/spot/aixspot_5200-02
    AIX Spot aixspot 5200 05 aixspot_5200-05 /export/spot/aixspot_5200-05
    AIX Spot aixspot 5300   aixspot_5300 /export/spot/aixspot_5300
    Suse Spot slesspot 9000   slesspot_9000 /export/spot/slesspot_9000

  • -
    Standards
    -
     

    Policies
    Guidelines
    Procedures


    LPAR Leasing
    Lease an AIX / i5 LPAR
    Reduce your costs

    www.mtxia.com

    Server Leasing
    Lease a Server off-site
    Reduce your costs

    www.mtxia.com

    Data Center Automation
    Business Continuity and DR
    Virtualization/Consolidation

    www.mtxia.com

    HMC Service
    Hardware Management Console
    Manage Remote AIX / i5 LPARs

    www.siteox.com

    Business Web Site Hosting
    $3.99 / month includes Tools,
    Shopping Cart, Site Builder

    www.siteox.com

    FREE Domain Registration
    included with Web Site Hosting
    Tools, Social Networking, Blog

    www.siteox.com

    Disaster Recovery
    Small Business Oriented
    Off-Site Facilities

    www.mtxia.com

    IBM pSeries / iSeries
    Reduce your Costs
    Off-Site Server Hosting

    www.mtxia.com