Rapid Deployment of an EMS-Configured System through Ignite-UX

One of the challenges for service provider system administrators today is to be able to quickly bring up new

systems that are just like already existing systems. Ignite-UX allows system administrators to do this by

creating and reusing standard configurations. A standard configuration for a system’s OS can be archived,

and then applied to another system through HP’s Ignite-UX product. A system administrator can do this by

following the instructions given in the "Using Golden System Images" chapter of the "Ignite-UX Administrator

Guide" (Part Number B2355-90677). This document can be found at the following location:

http://docs.hp.com/hpux/onlinedocs/B2355-90677/B2355-90677.html

By tailoring an Ignite-UX archive in a particular way, the Event Monitoring Service (EMS) configuration from

a functional EMS system can also be maintained when archiving a system, and then brought forward when

igniting a new system. This can be achieved by following the instructions referred to above, along with some

additional steps given below.

In order for this to be most effective, the systems being ignited should be as close as possible to a clone of

the source system. If this is not the case, then the EMS resource instances might differ and the differing

instances on the target node may not be monitored.

How to include EMS

make_sys_image File Modifications

One of the steps that a system administrator takes when creating the OS archive of a system is to run the

make_sys_image script. After making a copy of the original make_sys_image script, the following items

should be changed in the copy before running the script.

• LEVEL2_RESET

The LEVEL2_RESET variable within the make_sys_image file lists objects that will be reset to their

“newconfig” states in the OS archive. The LEVEL2_RESET variable includes /etc/inittab as one of the

entries in the original file. In order for EMS to function properly, this entry needs to be deleted. EMS

configures the /etc/inittab file with startup information that will be lost unless the “newconfig” state of

/etc/inittab is defeated. Without the EMS startup information in /etc/inittab, EMS will not startup and be

functional following a reboot of the target system.

• LEVEL2_NO_ARCHIVE

The LEVEL2_NO_ARCHIVE variable within the make_sys_image file lists files and directories that should

NOT go into the OS archive. The LEVEL2_NO_ARCHIVE variable includes /etc/resolv.conf as one of the

entries in the original file. In order for EMS to function properly on a target system, the /etc/resolv.conf file

must be saved as a part of the archive image. For this reason, the /etc/resolv.conf entry within the

LEVEL2_NO_ARCHIVE variable must be deleted. If this is not done, then certain notification types will not

be functional. Additionally, the interface for configuring EMS requests will not be available in graphical mode.

Once the above two modifications have been made to a copy of the make_sys_image script, the

make_sys_image script can be executed to create the system archive. For further details, please refer to the

“Step 1: Install HP-UX OS” section within the “Using Golden System Images” chapter within the "Ignite-UX

Administrator Guide".

PAGE 1
Rapid Deployment of an EMS-Configured System through Ignite-UX One of the challenges for service provider system administrators today is to be able to quickly bring up new systems that are just like already existing systems. Ignite-UX allows system administrators to do this by creating and reusing standard configurations. A standard configuration for a system’s OS can be archived, and then applied to another system through HP’s Ignite-UX product.
PAGE 2
os_arch_post_l File Modifications The /opt/ignite/data/scripts/os_arch_post_l file, or a copy of it, is referenced in the Ignite-UX configuration file which describes the OS archive. An example of an OS archive configuration file can be found in /opt/ignite/data/examples/core11.cfg on an Ignite-UX server. In turn, the OS archive configuration file is referenced in the /var/opt/ignite/INDEX file as a part of a specific named configuration.
PAGE 3
- Click the “Add…” button from the Define Configuration window. Click the “Open Template Window…” from the Add Configuration window. Double-click the “Templates for EMS support” description within the Message Source Templates window. Select the “EMS opcmsg” name within the Message Source Templates window (“EMS SNMP Traps” can also be selected). Click “OK” from the Add Configuration window. Click “OK” from the Define Configuration window. This effectively has chosen what to download.