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
|
Group Name Standards
This document describes the standards for assigning group names and
GID numbers in Mt Xia's AIX environment. A single standard has been
developed for use in standalone, High Availability, and Disaster
Recovery environments. This group naming standard provides the
mechanism to assign enterprise wide unique group names to all AIX
groups's and will eliminate naming conflicts in the event of a manual or
automated failover, or if multiple instances of an application are
running on a single server.
Groups are normally divided into two major categories on a Unix
system, administration and normal user groups. Applications such as
databases, SAP, MQSeries, etc may require an administration group. With
each new group created on a Unix system a group ID number is assigned to
that group, this group ID number is referred to as the GID number and is
normally unique to that group on that one Unix system. When building
highly available and/or recoverable systems, the group name and GID
number must be enterprise wide unique values. Therefore a centralized
group management system must be implemented to manage groups and GID
numbers to ensure that no two groups have the same group name or UID
number.
This centralized group management function is performed in Mt Xia's
environment by LDAP. All group requests and assignments must be
performed through the centralized group management system via the LDAP
servers.
|
|
|
