Introduction to NonStop Operations Management

Change and Configuration Management
Introduction to NonStop Operations Management–125507
7-5
Performing System Configuration Changes
•
Make sure that there is sufficient power. If there is not, schedule time for adding the
power. You might need to add power sockets.
•
Make sure that there is sufficient air conditioning. If there is not, schedule time for
improving the air-conditioning system.
•
Determine whether you need special cables, modems, or cabinets for
communications equipment.
•
Determine whether the change requires down time. If so, schedule the down time
with operations and notify users.
•
If your staff needs help from a Tandem CE, notify the CE at least 30 days in advance
of the change.
•
Determine whether the hardware change requires a new system configuration.
•
Make sure that the necessary operations staff is available to install the change.
Performing System Configuration Changes
A system configuration change is when you install a new operating system release,
install an IPM, add system software (including new Tandem products), or add, remove,
or reconfigure hardware. Follow these guidelines when changing the system
configuration:
•
When changing the hardware configuration, make sure that the system will be as
fault-tolerant as possible. This can help prevent unplanned down time from
occurring when a change is made. The Availability Guide for Problem Management
describes how to audit your system for fault tolerance and how to configure your
hardware and software for fault tolerance.
•
Before making system configuration changes, draw out the changes in a system
diagram. System diagrams help you check your work and prevent mistakes. An
example of a system diagram is shown in Section 4, “Operations Documentation.”
After you finish the system diagram, you might want the change management staff
to approve the changes.
•
To prevent a system outage, determine if the system configuration change can be
installed online.
•
To install updated software to support a new configuration, use the Distributed
Systems Management/Software Configuration Manager (DSM/SCM) product.
DSM/SCM provides for the centralized planning, management, and installation of
software on distributed (target) Tandem systems. DSM/SCM runs on a Tandem
central (host) system and performs the tasks of receiving, archiving, configuring,
and packaging software for target sites. It also runs on each target system, where its
primary function is to apply the software received from the central site.
•
To change a hardware configuration, you can use DSM/SCM.
•
DSM/SCM is used to create a new operating system image (OSI), which
allows you to add and change configurations for all device types; however, you
must stop all processing on the system to load the new OSI.