Software Installation Manual For Ovation 1.8 OS180 - 10: January 2007

Software Installation Manual for Ovation 1.
8
OS180_10
Version 2
January 2007
Copyright Notice
Since the equipment explained in this has a variety of uses, the user and those responsible for
applying this equipment must satisfy themselves as to the acceptability of each application and
use of the equipment. Under no circumstances will Emerson Process Management be
responsible or liable for any damage, including indirect or consequential losses resulting from the
use, misuse, or application of this equipment.
The text, illustrations, charts, and examples included in this manual are intended solely to explain
®
the use and application of the Ovation unit. Due to the many variables associated with specific
uses or applications, Emerson Process Management cannot assume responsibility or liability for
actual use based upon the data provided in this manual.
No patent liability is assumed by Emerson Process Management with respect to the use of
circuits, information, equipment, or software described in this manual.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, including electronic, mechanical, photocopying, recording or otherwise
without the prior express written permission of Emerson Process Management.
The document is the property of and contains Proprietary Information owned by Emerson Process
Management and/or its subcontractors and suppliers. It is transmitted in confidence and trust, and
the user agrees to treat this document in strict accordance with the terms and conditions of the
agreement under which it was provided.
This manual is printed in the USA and is subject to change without notice.
Ovation and WEStation are registered trademarks of Emerson Process Management. All other
trademarks or registered trademarks are the property of their respective holders.
Copyright © Emerson Process Management Power & Water Solutions, Inc. All rights reserved.
Emerson Process Management
Power & Water Solutions
200 Beta Drive
Pittsburgh, PA 15238
USA
E-Mail: Technical.Communications@EmersonProcess.com
Website: https://www.ovationusers.com
SUMMARY OF CHANGES
Software Installation Manual for Ovation 1.8
OS180_10
January 2007
Version 2 of Software Installation Manual for Ovation 1.8 includes the following new information:
Changes to the procedure To Configure Ovation Release Software (see page 31).
Contents
1 Introduction to Ovation software installation 1

1.1 Understanding the software installation process for Solaris-based Ovation systems ........ 1
2 Planning Ovation hardware installation 3

2.1 What are the hardware requirements? ............................................................................... 3
2.2 Configuring a monitor.......................................................................................................... 3
2.3 Configuring a keyboard ....................................................................................................... 3
2.4 Connecting a CDROM drive................................................................................................ 4
2.5 Connecting a cartridge tape drive ....................................................................................... 4
2.6 What is a SCSI device? ...................................................................................................... 5
2.6.1 To connect a SCSI device to a drop ................................................................. 5
3 Planning Ovation software installation 7

3.1 What are the software requirements?................................................................................. 7
3.2 Planning for your Ovation Security Server.......................................................................... 8
3.3 Licensing for an Ovation Solaris-based system.................................................................. 9
4 Loading a Standalone Ovation Security Server 11

4.1 Installing Solaris 10 for Security Servers .......................................................................... 11
4.2 To install Solaris 10 on an Ovation Security Server ......................................................... 11
4.3 Installing Solaris 10 Patches ............................................................................................. 14
4.3.1 To install Solaris 10 Patches ........................................................................... 14
4.4 Installing Ovation release software on a Security Server ................................................. 16
4.4.1 To install Ovation release software on a Security Server ............................... 16
4.5 Configuring Ovation Security Server software .................................................................. 17
4.5.1 To configure Ovation Security Server software............................................... 17
4.6 Accessing the Ovation Security Builder ............................................................................ 19
5 Loading an Ovation Software Server 21

5.1 Installing Solaris 10 for Software Servers ......................................................................... 21
5.1.1 To install Solaris 10 on a Software Server ...................................................... 21
5.1.2 Installing Solaris 10 Patches and Third-Party software .................................. 28
5.1.3 To install Solaris 10 Patches and Third-Party software .................................. 28
5.2 Installing Ovation release software on a Software Server ................................................ 30
5.2.1 To install Ovation release software on a Software Server .............................. 30
5.3 Configuring Ovation release software............................................................................... 31
5.3.1 To configure Ovation release software ........................................................... 31
OS180_10 i
Table of Contents
5.4 Installing Third-Party software on a Software Server ....................................................... 38

5.4.1 To install Third-Party software on a Software Server...................................... 38
6 Loading workstations that contain at least 384 MB of RAM 39

6.1 Installing Solaris 10, Solaris 10 patches, and Ovation software ....................................... 39
6.1.1 To install software on Fast Ethernet system drops ......................................... 39
6.1.2 To install software on FDDI system drops ...................................................... 40
6.2 Installing Third-Party software........................................................................................... 42
6.2.1 To install Third-Party software......................................................................... 43
7 Loading workstations that contain less than 384 MB of RAM 45

7.1 Installing Solaris 10, Solaris 10 patches, and Ovation software ....................................... 45
7.1.1 To install software on Fast Ethernet system drops ......................................... 45
7.2 Installing Third-Party software........................................................................................... 47
7.2.1 To install Third-Party software......................................................................... 47
8 Installing AutoCAD 49
8.1 What is AutoCAD? ............................................................................................................ 49
8.2 To install AutoCAD............................................................................................................ 49
9 Updating your Ovation Software Server 51

9.1 What are software updates? ............................................................................................. 51
9.2 Updating Solaris 10 patches (Software Server)................................................................ 51
9.2.1 To update Solaris 10 patches (Software Server) using the Software
Maintenance Tool................................................................................................. 51
9.3 Updating Ovation release software (Software Server) ..................................................... 53
9.3.1 To update Ovation release software (Software Server) using the Software
Maintenance Tool................................................................................................. 53
9.4 Updating Third-Party software (Software Server) ............................................................. 56
9.4.1 To update Third-Party software (Software Server) ......................................... 56
10 Updating all other Ovation workstations 57

10.1 Updating Solaris 10 patches (workstations)...................................................................... 57
10.1.1 To update Solaris 10 patches (workstations) .................................................. 57
10.2 What are Software updates? ............................................................................................ 57
10.3 Updating Ovation release software (workstations) ........................................................... 58
10.3.1 To update Ovation release software (workstation) ......................................... 58
10.4 Updating Third-Party software (workstation)..................................................................... 58
10.4.1 To update Third-Party software (workstation) ................................................. 58
11 Upgrading your Ovation System 59

11.1 What is a system upgrade?............................................................................................... 59
11.1.1 To upgrade an Ovation system from Ovation 1.x to 1.8 ................................. 59
ii OS180_10
Table of Contents
11.1.2 To upgrade an Ovation system from 1.7.x to 1.8 ............................................ 60

11.1.3 To upgrade drivers for computers with Znyx cards ......................................... 61
11.1.4 To upgrade drivers for computers with Linksys cards..................................... 62
11.1.5 To add an Ultra 25, 45 workstation to the network using a Solaris 10
(Version 3/05) Server ........................................................................................... 64
11.1.6 To upgrade a Software Server from 1.7 to 1.8 (Standalone Security Server
on a multiple network) .......................................................................................... 65
11.1.7 To upgrade a Software Server from 1.7 to 1.8 (Combination Software
Server/Security Server on a single network) ....................................................... 67
12 Backing up the system 71

12.1 What is a system backup? ................................................................................................ 71
12.2 Using OCBT to backup the system................................................................................... 71
12.2.1 To use OCBT .................................................................................................. 71
12.2.2 OCBT configuration table ................................................................................ 75
12.2.3 To use the Setup window ................................................................................ 78
12.3 Using command lines to backup the system..................................................................... 79
12.3.1 To backup the Ovation Security Server .......................................................... 79
12.3.2 To backup the Software Server....................................................................... 79
12.3.3 To backup a complete database (using Oracle Export program exp) ............ 81
12.3.4 To backup the Ovation Historian (HSR).......................................................... 82
12.3.5 To backup a partial database (using PowerTools Export program ptdbexp).. 82
12.3.6 To backup the Control Builder (CB) drawings................................................. 83
12.3.7 Backing up printer information......................................................................... 83
12.3.8 Backing up the Data Link files ......................................................................... 84
12.3.9 Backing up Third-Party software licensing information ................................... 84
13 Restoring the Ovation system 85

13.1 Ovation restoration overview............................................................................................. 85
13.2 To restore the Ovation Security Server............................................................................. 85
13.3 To restore the Software Server......................................................................................... 86
13.4 To restore all drops (except the Software Server) ............................................................ 87
13.5 Restoring the Ovation Historian (HSR) ............................................................................. 88
13.5.1 To restore the Ovation Historian (HSR) drop .................................................. 88
13.6 Restoring the Power Tools database files ........................................................................ 89
13.6.1 Restoring a complete database ...................................................................... 89
13.6.2 Advantages of restoring a complete database................................................ 90
13.6.3 Disadvantages of restoring a complete database ........................................... 90
13.6.4 To restore a complete database ..................................................................... 90
13.6.5 Restoring a partial database ........................................................................... 91
13.6.6 Advantages of restoring a partial database..................................................... 91
13.6.7 Disadvantages of restoring a partial database................................................ 92
13.6.8 To restore a partial database .......................................................................... 92
13.7 Restoring the Control Builder drawings ............................................................................ 92
13.7.1 To restore Control Builder drawings after a complete database restoration... 92
13.7.2 To restore Control Builder drawings after a partial database restoration ....... 93
OS180_10 iii
Table of Contents
14 Using the Software Maintenance Tool 95

14.1 What is the Software Maintenance Tool? ......................................................................... 96
14.1.1 Software Maintenance Tool window (showing details) ................................... 98
14.2 Accessing the Software Maintenance Tool....................................................................... 99
14.3 Updating the Software Server ........................................................................................... 99
14.3.1 To match a cluster of packages .................................................................... 100
14.4 Adding/removing individual package(s) .......................................................................... 102
14.4.1 To choose a cluster ....................................................................................... 103
14.4.2 To customize a cluster .................................................................................. 103
14.4.3 To complete the installation........................................................................... 103
14.5 Locating modified software on a disk.............................................................................. 106
14.5.1 To locate modified software on a disk........................................................... 106
14.6 After using the Software Maintenance Tool .................................................................... 106
15 Formatting the hard disk 107

15.1 When do you need to format the hard disk? ................................................................... 107
15.1.1 To format the hard disk ................................................................................. 107
Index 113
iv OS180_10
S E C T I O N 1
INTRODUCTION TO OVATION SOFTWARE INSTALLATION
IN THIS SECTION
Understanding the software installation process for Solaris-based Ovation systems ........ 1
1.1 UNDERSTANDING THE SOFTWARE INSTALLATION PROCESS FOR SOLARIS-

B A S E D O V A T I O N S Y ST E M S
The process of installing and maintaining the required software on your Ovation system consists
of several operations.
1. Verify that the required hardware (see page 3) has been installed and configured and you
know the applicable hard disk information.
2. Ensure you have the necessary software (see page 7) media.
3. Load Solaris 10 (see page 21) onto the Software Server from the Solaris CDROMs or DVD.
If your Server is an Ultra 25 or 45, you need to use Solaris 10 (version 6/06 or later) on that
machine.
If the target machine you want to load from the Server is an Ultra 25 or 45, be sure that the
cd_image you use is Solaris 10 (version 6/06 or later).
Refer to the following table to determine the Solaris version you need.
Choosing Solaris Operating System
SOFTW ARE SERVER SOLARIS T ARGET OPERATING SYSTEM

HARDWARE OPERATING COMPUTER ON CD_IM AG E
SYSTEM HARDWARE
Sun Blade or UltraSPARC Version 3/05 or 3/06 Sun Blade or Version 3/05 or 3/06
UltraSPARC
Sun Blade or UltraSPARC Version 3/05 or 3/06 Ultra 25 or 45 Version 6/06
Sun Blade or UltraSPARC Version 6/06 Ultra 25 or 45 Version 6/06
Ultra 25 or 45 Version 6/06 Sun Blade, Version 6/06
UltraSPARC, Ultra
25, or Ultra 45
4. Load the Solaris patches (see page 14) onto the Software Server from the Ovation Patches
CDROM.
5. Install third-party software (see page 14) on the Software Server.
6. Load Ovation software (see page 30) from the Ovation release CDROM onto the Software
Server.
7. Configure (see page 31) the Ovation software on the Software Server.
OS180_10 1
1.1 Understanding the software installation process for Solaris-based Ovation systems
8. Load all other workstations (see page 39) from the Server by booting the workstations over
the network. The following occurs automatically:
Solaris is loaded from the Software Server.
Solaris patches are loaded from the Software Server.
Ovation software is loaded from the Software Server.
9. Install third-party software (see page 42) on the other workstations as needed.
Note: If you plan to run the Control Builder on a drop, you need to install AutoCAD on the drop.
You must install AutoCAD individually on each machine that runs Control Builder.
10. You may also want to use some or all of the following procedures:
Updating (see page 51) the Ovation software on your Software Server.
Updating (see page 57) all other Ovation workstations.
Overview of upgrading (see page 59) your entire system.
Backing up (see page 71) your Ovation system.
Restoring (see page 85) your Ovation system.
Note: Always refer to the applicable Ovation software manual for complete instructions on
configuring software on your Ovation system.
2 OS180_10
S E C T I O N 2
PLANNING OVATION HARDWARE INSTALLATION
IN THIS SECTION
What are the hardware requirements? ............................................................................... 3

Configuring a monitor.......................................................................................................... 3
Configuring a keyboard ....................................................................................................... 3
Connecting a CDROM drive................................................................................................ 4
Connecting a cartridge tape drive ....................................................................................... 4
What is a SCSI device? ...................................................................................................... 5
2.1 WHAT ARE THE HARDWARE REQUIREMENTS?
This section describes the hardware needed to load the Ovation workstation drops with the
appropriate software (it is assumed that the internal hardware for the Sun workstation being used
as an Ovation workstation has been already installed). The drop being loaded may not have the
peripheral devices required for the loading procedure. The following pieces of equipment may be
required to initialize a drop:
Sun or Sun-equivalent computer.
Note: The computer used as a Software Server must have at least 512 MB of RAM (Random
Access Memory).
CRT monitor (for viewing commands and messages).

Keyboard (for communicating with the processor).
CDROM device (for installing software provided on CDROM or DVD).
Cartridge tape drive (for backing up your system).
2.2 CONFIGURING A MONITOR
If a monitor is not connected to the drop to be loaded, connect a monitor to the drop at the normal
connection points. (See Planning Your Ovation System.)
2.3 CONFIGURING A K E YB O A R D
If a keyboard is not connected to the drop to be loaded, connect the keyboard to the drop at the
normal connection points. (See Planning Your Ovation System.)
If the drop was previously running without the keyboard, it may be necessary to cycle the power
to the drop, and to change the “input device” parameter so that the drop recognizes the keyboard.
OS180_10 3
2.4 Connecting a CDROM drive
2.4 CONNECTING A CDROM DRIVE
A CDROM drive is used to install software, and typically, a workstation comes with a CDROM
drive installed. If a CDROM drive is not installed in the drop to be loaded, connect a CDROM to
the drop at the normal connection points. (See Planning Your Ovation System.)
If the CDROM is connected as an external device, it must be cabled into the SCSI chain (see
page 5).
Determine the unit number located on the back of the CDROM drive. For example, if it is set to
six (6), the device name will be /dev/dsk/c0t6d0s2.
where:
dev = device
dsk = disk
c = SCSI (device being used is 0)
t = target (switch setting being used is 6)
d = disk (disk used is typically zero)
s = slice (entire disk is indicated by 2)
2.5 CONNECTING A CARTRIDGE TAPE DRIVE
A cartridge tape drive is a storage device that is typically used to backup your configured software
to be used in case of a system malfunction. If a tape drive is not installed in the drop to be loaded,
connect a tape drive to the drop at the normal connection points. (See Planning Your Ovation
System.)
If the tape drive is connected as an external device, it must be cabled into the SCSI chain (see
page 5).
Determine the unit number located on the back of the tape drive. For example, if it is set to six
(6), the device name will be /dev/dsk/c0t6d0s2.
where:
dev = device
dsk = disk
c = SCSI (device being used is 0)
t = target (switch setting being used is 6)
d = disk (disk used is typically zero)
s = slice (entire disk is indicated by 2)
4 OS180_10
2.6 What is a SCSI device?
2.6 WHAT IS A SCSI D EV I C E ?
A Small Computer System Interface (SCSI) is the interface standard name for a peripheral device
such as a hard disk drive. The SCSI hard disk drive (typically part of the workstation chassis) is
able to communicate quickly with other peripherals through the SCSI port.
SCSI devices typically include tape drives, hard disk drives, read/write optical peripherals, and
CDROM units. During Ovation workstation assembly, these devices are assigned address values
in the range of zero (0) through seven (7).
Note: Shut down all external devices from the SCSI port of the workstation before attempting to
load Solaris.
2.6.1 T O CONNECT A SCSI DEVICE TO A DROP

1. After the operating system is installed, log in as root.
2. Enter init 0 to halt the machine. A system prompt appears when the drop processor is
safely stopped.
3. Turn off the power to the machine.
4. Connect the SCSI device to the drop.
5. Turn on the power to the machine.
6. During the “Testing” message, press Stop and a. If a system prompt appears, enter b -r.
If an “ok” prompt appears, enter boot -r.
7. To remove a SCSI device, halt the machine, turn off the power to the machine, disconnect the
SCSI device, turn on the power to the machine, and then reboot (as described in Step 6).
OS180_10 5
S E C T I O N 3
PLANNING OVATION SOFTWARE INSTALLATION
IN THIS SECTION
What are the software requirements?................................................................................. 7

Planning for your Ovation Security Server.......................................................................... 8
Licensing for an Ovation Solaris-based system.................................................................. 9
3.1 WHAT ARE THE SOFTWARE REQUIREMENTS?
Ensure you have the following software media before you begin to install your system:
CDROMs (five) or the DVD (one) containing the Solaris 10 Operating System.
Ovation release CDROMs (three) containing the following:
Ovation 1.8 release CDROM
Solaris 10 patches CDROM
Ovation third-party software CDROM
Necessary license keys.
Control Builder/AutoCAD CDROM (needed for Ovation Control Builder)
OS180_10 7
3.2 Planning for your Ovation Security Server
3.2 PLANNING FOR YOUR OVATION SECURITY SERVER

Security for an Ovation system is designed to prevent unauthorized use and unauthorized actions
on an Ovation control system. This is accomplished by using a domain concept plus the
assignment of security roles for users and computers in the domain.
A domain is a logical collection of computers and users on a single or multiple network that share
a common security database. All the computers and users in the domain are managed by a
server, known as an Ovation Security Server (OSS), that contains the security database.
Security roles are collections of rules that control the behavior and functionality of users and
computers in a domain. When a role is applied to a user/computer account, then security settings
for that user/computer are the same as for any user/computer that has that same role applied.
This simplifies the configuration and management of security for Ovation systems.
You can store group policies plus computer and user information in a central database on the
Security Server and they are shared by all domain members on a network. This type of system is
easy to manage because of the centralized administrative nature. For example, user accounts
need to be created only once on a Security Server and all other workstations on the network can
then share the user accounts.
You need to decide how you want to define and configure your Security Server. There are several
choices:
Standalone Security Server
The standalone Security Server (see page 11) is typically used in a multiple network system. By
using this approach, a standalone Security Server contains and administrates all the security
information for each network in an Ovation domain.
Combination Security Server
The combination Security Server (see page 31) is typically used in a single network system and
resides on the network's Software Server.
8 OS180_10
3.3 Licensing for an Ovation Solaris-based system
3.3 LICENSING FOR AN OVATION SOLARIS-BASED SYSTEM
You must assign a license key to every Ovation system. This key defines how many drops of
each drop type category are allowed in the system (such as Solaris-based Stations, Windows-
based Operator Stations, Controllers, and SIM Controllers). You enter license key information in
the Init Tool during the software installation process.
Plan your software installation or upgrade to ensure you will have key codes or license files
readily available when they are needed during the installation. These licenses are available during
normal work hours from Emerson. Contact Emerson prior to installations or upgrades to ensure
the availability of required key codes or licenses.
If you are planning to perform a new installation, you would typically contact your project
engineer.
If you are planning to perform an upgrade, you would typically contact your Field Service
engineer or possibly your after-market representative.
Note: If your system was initially loaded at the Emerson plant, the license codes used for the
load procedures will be provided in your Software and Licensing Kit binder.
If you are performing an emergency reload, you can call 1-800-445-9723 for license
assistance. Be prepared to provide your name, your project or company name, and the exact
nature of your installation needs. Your call will be evaluated for emergency status and then
forwarded to the appropriate support department. You will receive a response as soon as
possible, based on your need and on the level of your Support Agreement with Emerson.
The following software packages require licensing:
Solaris - A CDROM or DVD containing the Solaris 10 operating system is needed. The
license is included in the media.
Ovation - A license key is needed during the installation. To obtain a license key, contact the
Software Licensing Administrator at Emerson with the host ID of the Software Server and the
number of drops of each drop type category. If a valid license key is not entered, you will not
be able to add drops.
AutoCAD (only needed for the Control Builder application) - A license key is needed during
the installation. After the AutoCAD application is installed, a prompt appears asking if you
want to install the AutoCAD license. Select (y)es and a group of numbers appears. To obtain
a license key, send this group of numbers, along with your project number, AutoCAD serial
number (located on the CDROM), drop number where AutoCAD is installed, and hostid to the
License Administrator at Emerson.
OS180_10 9
S E C T I O N 4
LOADING A STANDALONE OVATION SECURITY SERVER
IN THIS SECTION
Installing Solaris 10 for Security Servers .......................................................................... 11

To install Solaris 10 on an Ovation Security Server.......................................................... 11
Installing Solaris 10 Patches ............................................................................................. 14
Installing Ovation release software on a Security Server ................................................. 16
Configuring Ovation Security Server software .................................................................. 17
Accessing the Ovation Security Builder ............................................................................ 19
4.1 I N S T A L L I N G S O L A R I S 10 FOR SECURITY SERVERS

You must use a Sun workstation that contains at least 512 MB of RAM as the Security Server for
your Ovation system. This ensures that the Security Server will have enough memory to perform
all the Server functions smoothly and efficiently.
4.2 TO INSTALL S O L A R I S 10 ON AN OVATION SECURITY SERVER

Use the following procedure to load the Solaris 10 Operating System on an Ovation Security
Server (some directions may also be provided on screen during the procedure):
Note: There are no Shelltool or Command tool windows in Solaris 10. Instead, there are
Terminal windows. You can access a Terminal window by typing /usr/dt/bin/dtterm.
1. Insert the Solaris 10 Software CDROM (disk 1 of 5) or the Solaris 10 Operating System DVD
into the CDROM player.
2. Press the Stop and a keys simultaneously on the Sun keyboard in order to halt the Sun
processor (if this has been disabled, try entering init 0 in a terminal window).
3. At the system prompt, enter boot cdrom, then press Enter (this is the applicable entry
for most Sun machines).
4. After the workstation boots from the CDROM, the Select a Language prompt appears. Select
the appropriate language. Select the Enter button.
5. The Identify This System window appears. Select the Continue button.
6. The Welcome window appears. Select the Next button.
7. The Network Connectivity window appears. Select Networked. Select the Next button.
8. The DHCP window appears. Select No. Select the Next button.
9. The Host Name window appears. You must enter this host name as drop (with a lowercase
d), followed by the desired drop number (valid range is 1 through 253). Leading zeros are not
permitted.
Enter the name of the drop (for example, drop212). Select the Next button.
OS180_10 11
4.2 To install Solaris 10 on an Ovation Security Server
10. The IP Address window appears. Each drop must have a unique network IP address
assigned to it. See your Project Engineer or System Administrator for the correct network
address.
Select the Next button.
11. The Netmask window appears.
If this drop will not be connected to an existing Ethernet network, then leave the Netmask
value as 255.255.255.0.
OR
If this drop will be connected to an existing Ethernet network, see the Project Engineer or
System Administrator for the correct network address.
12. The IPv6 window appears. Select No. Select the Next button.
13. The Set the Default Route window appears.
If this drop will not be connected to the Internet at this time, select None.
OR
f this drop will be connected to the Internet, select Specify One. Select Next. The second Set
the Default Route window appears. Enter the IP address for the default router. See the
Project Engineer or System Administrator for the correct IP address. Select Next.
14. The Kerberos window appears. Select No. Select the Next button.
15. The Name Service window appears. Select None. Select the Next button.
16. The Time Zone window appears. Select Geographic Continent. Select the Next button.
17. The Continent and Country window appears. Use the tree to select the appropriate
Continent, Country, and Time Zone. Select Next.
18. The Date and Time window appears. If the date and time are correct, select Next. If they are
incorrect, make the necessary changes and select Next.
19. The Root Password window appears. Enter the desired password. Select Next.
20. The Confirm Information window appears. The previously entered information displays. Verify
that the correct data has been entered. Select the Confirm button.
If the information is not correct, select the Back button and redo Step 16 through Step 19.
Note: If you need to format the drop hard disk, the message "Corrupt label - wrong magic
number" appears during the drop reboot. If this occurred, select Exit. This provides the
opportunity to format the disk (see instructions on hard disk formatting (see page 107)).
21. A Welcome screen appears. Select Next.

22. The Installer Options window appears. Select Reboot automatically and Eject a CD/DVD
automatically. Select Next.
23. The Specify Media window appears. Select the appropriate media (typically, CD/DVD). Select
Next. An initializing message appears.
24. The License Agreement window appears. Select Accept and then Next.
25. The Select Upgrade or Initial Install window appears. Select Initial Install. Select the Next
button.
26. The Select Type of Install window appears. Select Custom Install. Select Next.
12 OS180_10
4.2 To install Solaris 10 on an Ovation Security Server
27. The Select Software Localizations window appears. Select the appropriate localizations.
Select Next.
28. The Select System Locale window appears. Select the appropriate locale. Select Next.
29. The Select Products window appears. Make sure the check boxes are empty. Select Next.
30. The Additional Products window appears. Select None. Select Next.
31. The Select Solaris Software Group window appears. Select End User Group (Custom
Packages). Select Next.
32. The Select Clusters and Packages window appears.
In addition to the options that are already selected as defaults, select the following
options in this order (make sure the selection boxes contain check marks):
¾ Basic Networking
¾ Programming tools and libraries
¾ Solaris PPP
¾ NIS Server for Solaris (root)
¾ NIS Server for Solaris (usr)
After all the applicable choices are selected, select Next.
33. The Disk Selection window appears. Select all the disks (one at a time) listed in the
Available Disks list, and use the Add (>>) button to move them to the Selected Disks list.
34. If the Preserve Data window appears, select the No button. Select Next.
35. The Lay Out File Systems window appears. Select Modify.
36. The Disks window appears. Typically, only one disk is available in a drop. Any drop that
functions as an Historian or Power Tools Database Server may contain multiple disks.
The following table identifies an example for a typical Security Server.
After you have completed the partitioning, proceed to Step 37.
TYPE SYSTEM DISK OTHER DISKS
Standalone Security Example A N/A

Software Server
Example A. 9 GB or
Greater Disk
Slice Mount Point Size (MBs)
0 / 1000 (minimum)
1 swap 1000 (minimum)
3 0
4 0
5 0
6 /usr 3000 (minimum)
7 /export/wdpf Remainder of disk (4000
minimum)
OS180_10 13
4.3 Installing Solaris 10 Patches
37. After the slice sizes and Mount Point names have been properly configured, select OK.
The Lay Out File System window appears again. The previously entered information is
displayed. If the information is correct, select Next.
OR
If the information is not correct, select the Modify button and redo the incorrect steps.
38. The Ready to Install window appears. Select Install Now.
39. Installation of Solaris 10 begins (CDROM 1 of 5 or the DVD). After a period of time, the
system reboots. A prompt appears asking if you need to override the system's default NFS
version 4 domain name. Select No. Select the Enter button.
Messages appear informing you as software is installed.
Note: If you are installing Solaris 10 from the Solaris 10 DVD, skip to Step 41 after the
installation is complete.
40. After the installation is complete, perform the following when the Specify Media window
appears:
a) Select the appropriate media (typically, CD/DVD). Select Next.
b) Insert the second Solaris 10 CDROM (disk 2 of 5). Select OK.
c) Installation of Solaris 10 begins (disk 2 of 5). The Installing Solaris Software window
appears. Select Install Now.
d) A Pausing window appears. Select Continue.
e) Repeat Step a through Step d for each consecutive CDROM (disks 3,4, and 5).
41. The Installation Summary window appears. Select Next.
42. The Specify Media window for languages appears. Select Skip if you are using English (or
specify the appropriate language).
Select Skip Installation. A Pausing window appears. Select Continue.
43. The Reboot window appears. Select Reboot Now.
44. After the reboot is completed, the Solaris login prompt appears. Enter root. The Password
prompt appears.
Type in the <applicable password>.
45. Proceed to install the Solaris 10 Patches (see page 14).
4.3 I N S T A L L I N G S O L A R I S 10 P A T C H E S
Sun has supplied software modification patches for the Solaris 10 Operating System.
The patches applicable to the Ovation workstation drops are distributed on the Ovation Patches
CDROM. Install these patches at the Security Server.
4.3.1 T O INSTALL S OLARIS 10 P ATCHES

1. Insert the Ovation 1.8 Patches CDROM into the CDROM drive.
2. After the Common Desktop Environment (CDE) starts, if prompted, select CDE and OK.
If prompted for Registration, select Cancel and Yes.
14 OS180_10
4.3 Installing Solaris 10 Patches
3. Right-click in the background and select Tools and then Terminal.

4. Enter the following in the Terminal window to access the Software Maintenance Tool:
/cdrom/cdrom0/swmaint &
(Do NOT cd to the cdrom directory. This might generate errors regarding the mounting of the
CDROM.
5. Use the Software Maintenance Tool to select and install the required Solaris patches onto the
Software Server.
Perform the following in the Software Maintenance Tool:
a) Select the Clusters menu item.
b) Select Solaris Patch Clusters.
c) Select Solaris 2.10 Solaris Patches.
d) Select the Check menu item.
e) Select Check Software Server Against Selected Packages and
Patches.
f) Unselect all WEStation Packages options.
g) Select all Solaris Patch options.
h) Select the Start Checking button.
i) The Software Server Differences window appears.
j) Select the Select All button
k) Select the Update Software Server button.
l) After the update is complete, select the File menu item on the main window.
m) Select Exit.
6. To install the Solaris patches into the Solaris Operating System on the Security Server, enter
the following in the Terminal Window:
/cdrom/cdrom0/setup_scripts/install_patches
7. Type the following to reboot the Software Server:
reboot
8. After rebooting, the Solaris login prompt appears. Type the following:
root
9. The Password prompt appears. Type in the <applicable password>.
10. Right-click in the background and select Tools and then Terminal. Type eject in the
Terminal window.
11. Install the Ovation release software (see page 16).
OS180_10 15
4.4 Installing Ovation release software on a Security Server
4.4 INSTALLING OVATION RELEASE SOFTWARE ON A SECURITY SERVER

Install the Ovation release software on the Software Server, configure the software as needed,
and then download it to the other workstations in the system. This process allows an entire
Ovation system to be loaded from one Software Server.
The Ovation release software required by the workstations is supplied on the Ovation Release
CDROM.
4.4.1 T O INSTALL O VATION RELEASE SOFTWARE ON A S ECURITY S ERVER

1. Insert the Ovation Release CDROM into the CDROM drive.
2. If a Terminal is not open, right-click in the background and select Tools and then Terminal.
Enter the following in the Terminal window:
/cdrom/cdrom0/setup_scripts/setup -Security
CDROM.
4. Use the Software Maintenance Tool to select and install the desired Ovation software
packages onto the Security Server.
a) Select the Clusters (Standalone Security Server) menu item.
b) Select WEStation Package Clusters -> Ovation Security Server Packages.
c) Select the desired cluster.
e) Select Check Software Server Against Selected Packages and Patches.
f) Select Check Package Dependencies for WEStation Packages.
g) Select Check Installed Versions for WEStation Packages.
h) Unselect all Solaris Patch options.
i) Select the Start Checking button.
j) The Security Server Differences window appears.
k) Select the Select All button.
l) Select the Update Software Server button.
m) After the update is complete, select the File menu item on the main window.
n) Select Exit.
5. Enter eject in the terminal window to eject the CDROM.
16 OS180_10
4.5 Configuring Ovation Security Server software
4.5 CONFIGURING OVATION SECURITY SERVER SOFTWARE
After the Ovation software has been loaded, some initial configuration is necessary before the
system can function as an Ovation Security Server.
The Ovation Highway Interface (OHI) software permits a pair of physical Ethernet ports to be
combined into a single, redundant, logical interface. The OHI software can joint the onboard eri0
interface with an additional interface (such as the add-in Linksys afe0 card). The resulting
interface is known as ohi0. You must configure this driver based on the Network Interface Cards
(NIC) that the workstation is using.
4.5.1 T O CONFIGURE O VATION S ECURITY S ERVER SOFTWARE

1. If a Terminal is not open, right-click in the background and select Tools and then Terminal.
2. Enter the following command at the Security Server (as root) in a Terminal window:
cd /export/wdpf/rel/ssw/load_kit/bin
./configure –Security
Note: Ignore the CDE message that appears and check the indicated box so that the message
will not appear again. Select Continue.
3. The License Existence window appears. Select Confirm to accept the terms of the Emerson
license agreement.
4. The following message appears:
“This level of Ovation software supports a common Security

Server for multiple networks. If you choose to use the
common Security Server you must configure all of your
Ovation networks to have the same Domain Name. Also each
network needs to know the name and IP address of the
Security Server, this will need to be configured through the
InitTool.
We now need to know the configuration of this drop, three

choices are currently available:
[1] Standalone Security Server
[2] Ovation Software Server/ Security Server
[3] Ovation Software Server
Enter this Drop Configuration <2> : “

Enter “1” for a Standalone Security Server.
5. The Ovation Domain Setup Procedure window displays in a Terminal window. The following
message appears:
Enter the Domain name that this computer will be part of

<Ovation.domain.com>
Enter a name for your Domain or select the Enter key to accept the default
Ovation.domain.com.
OS180_10 17
4.5 Configuring Ovation Security Server software
Please enter the Ovation Domain Administrator (admin)

password
New Password:
Re-enter New Password:.
Enter the desired password and re-enter the password.
A message prompts you to Hit "Return" to continue.
7. While still in the Terminal window, if you use any combination of network interface cards (NIC)
as outlined in the following table, in order to configure the OHI driver, you must enter the
following command at a command prompt.
/sbin/ohisetup <primary NIC> <backup NIC>
WORKSTATION TYPE PRIM ARY NIC BACKUP NIC
Sun Blade with external card afe0 (Linksys) eri0 (onboard)
UltraSPARC 5, 10, 60 afe0 (Linksys) hme0
UltraSPARC 5, 10, 60 hme0 hme1
Sun Blade with Znyx card tu0 tu1
Ultra 25, 45 with onboard cards bge0 bge1
8. If the machine is configured with a redundant Ethernet Connector or any FDDI network
connector, type one of the following commands in a Terminal window to adjust the
/etc/hostname file for the applicable hardware configuration. If the machine is not configured
with a redundant Ethernet connector or an FDDI connector, skip to Step 9.
WORKSTATION SYSTEM COMM AND

TYPE TYPE
Sun Blade Fast Ethernet mv /etc/hostname.eri0

/etc/hostname.zrl0
Sun Blade Fast Ethernet mv /etc/hostname.eri0
/etc/hostname.ohi0
(using
external card)
Sun Blade FDDI mv /etc/hostname.eri0
/etc/hostname.skfp0
UltraSPARC 5, Fast Ethernet mv /etc/hostname.hme0

10,60 /etc/hostname.ohi0
(using
external card)
UltraSPARC 5,10,60 Fast Ethernet mv /etc/hostname.hme0
/etc/hostname.zrl0
18 OS180_10
4.6 Accessing the Ovation Security Builder

TYPE TYPE
UltraSPARC 5,10,60 FDDI mv /etc/hostname.hme0

/etc/hostname.skfp0
Ultra 25 and 45 Fast Ethernet mv /etc/hostname.bge0

/etc/hostname.ohi0
9. Reboot the machine by typing the following: init 6

10. After rebooting, log into the Server as admin with the appropriate password.
11. After the Common Desktop Environment (CDE) starts, if prompted, select CDE and OK.
12. If prompted, for Registration, select Cancel and Yes.
4.6 ACCESSING THE O VA T I O N S EC U R I T Y B U I L D E R

The administrator may access the Ovation Security Builder from the workspace dropdown menu
as follows:
Ovation > Security Builder
Or by typing the following in a Terminal window:
/wdpf/rel/ssw/db/bin/security_builder &
OS180_10 19
S E C T I O N 5
LOADING AN OVATION SOFTWARE SERVER
IN THIS SECTION
Installing Solaris 10 for Software Servers ......................................................................... 21

Installing Ovation release software on a Software Server ................................................ 30
Configuring Ovation release software............................................................................... 31
Installing Third-Party software on a Software Server........................................................ 38
5.1 I N S T A L L I N G S O L A R I S 10 FOR SOFTWARE SERVERS

You must use a Sun workstation that contains at least 512 MB of RAM as the Software Server for
your Ovation system. This ensures that the Software Server will have enough memory to perform
all the Server functions smoothly and efficiently.
5.1.1 T O INSTALL S OLARIS 10 ON A S OFTWARE S ERVER
Use the following procedure to load the Solaris 10 Operating System on an Ovation Software
Server (some directions may also be provided on screen during the procedure):
into the CDROM player.
processor (if this has been disabled, try entering init 0 in a Terminal window).
3. At the system prompt, enter boot cdrom, then press Enter (this is the applicable entry
for most Sun machines).
4. After the workstation boots from the CDROM, the Select a Language prompt appears. Select
the appropriate language. Select the Enter button.
5. The Identify This System window appears. Select the Continue button.
6. The Welcome window appears. Select the Next button.
7. The Network Connectivity window appears. Select Networked. Select the Next button.
8. The DHCP window appears. Select No. Select the Next button.
9. The Host Name window appears. Enter this host name as drop (with a lowercase d),
followed by the desired drop number (valid range is 1 through 253). Leading zeros are not
permitted.
Enter the name of the drop (for example, drop212). Select the Next button.
OS180_10 21
5.1 Installing Solaris 10 for Software Servers
10. The IP Address window appears. Each drop must have a unique network IP address
assigned to it. See your Project Engineer or System Administrator for the correct address.
If this drop will not be connected to an existing ethernet network, then leave the Netmask
value as 255.255.255.0.
OR
If this drop will be connected to an existing Ethernet network, see the Project Engineer or
System Administrator for the correct network address.
OR
If this drop will be connected to the Internet, select Specify One. Select Next. The second
Set the Default Route window appears. Enter the IP address for the default router. See
the Project Engineer or System Administrator for the correct IP address. Select Next.
14. The Kerberos window appears. Select No. Select the Next button.
17. The Continent and Country window appears. Use the tree to select the appropriate
Continent, Country, and Time Zone. Select Next.
18. The Date and Time window appears. If the date and time are correct, select Next. If they are
incorrect, make the necessary changes and select Next.
19. The Root Password window appears. Enter the desired password. Select Next.
20. The Confirm Information window appears. The previously entered information is displayed.
Verify the correct data has been entered. Select the Confirm button.
If the information is not correct, select the Back button and redo Step 16 through Step 19.
Note: If you need to format the drop hard disk, the message “Corrupt label - wrong magic
number” appears during the drop reboot. If this occurred, select Exit. This provides the
opportunity to format the disk (see instructions on hard disk formatting (see page 107)).

22. The Installer Options window appears. Select Reboot automatically and Eject a CD/DVD
automatically. Select Next.
23. The Specify Media window appears. Select the appropriate media (typically, CD/DVD). Select
Next. An initializing message appears.
24. The License Agreement window appears. Select Accept and then Next.
25. The Select Upgrade or Initial Install window appears. Select Initial Install. Select the Next
button.
26. The Select Type of Install window appears. Select Custom Install. Select Next.
22 OS180_10
27. The Select Software Localizations window appears. Select the appropriate localizations.
Select Next.
28. The Select System Locale window appears. Select the appropriate locale. Select Next.
29. The Select Products window appears. Make sure the check boxes are empty. Select Next.
30. The Additional Products window appears. Select None. Select Next.
31. The Select Solaris Software Group window appears. Select End User Group (Custom
Packages). Select Next.
32. The Select Clusters and Packages window appears.
In addition to the options that are already selected as defaults, select the following
options in this order (make sure the selection boxes contain check marks):
¾ Audio Drivers and Applications
(if sample sounds are to be used for audible alarms).
¾ Basic Networking
¾ On-line Manual Pages
¾ Programming tools and libraries
¾ Solaris PPP
¾ SunOS Header Files
¾ NIS Server for Solaris (root)
¾ NIS Server for Solaris (usr)
De-select the following default selections (make sure the selection boxes are
completely GRAY):
¾ Power Management OW Utilities
¾ Power Management Software
Click on the triangle to the left of the CDE Runtime Software item to display all the
options. Deselect the System Boot for Desktop Login option.
After all the applicable choices are selected, select Next.
33. The Disk Selection window appears. Select all the disks (one at a time) listed in the
Available Disks list, and use the Add (>>) button to move them to the Selected Disks list.
34. If the Preserve Data window appears, select the No button. Select Next.
35. The Lay Out File Systems window appears. Select Modify.
36. The Disks window appears. Typically, only one disk is available in a drop. Any drop that
functions as an Historian or Power Tools Database Server may contain multiple disks.
The following table identifies what example should be used to configure the disk(s) for each
workstation type. The workstation types are the standard Ovation release drop types. If
desired, you can create new drop types as described in Ovation Init and Admin Tools User
Guide. The examples are described following the table:
Set the disk partitioning to match the applicable Example (A, B, C, D, E, F, G, or H):
After you have completed the partitioning, proceed to Step 37.
OS180_10 23
DROP TYPE SYSTEM DISK OTHER DISKS
Operator Workstation (OPWS) Example B N/A
Operator Workstation with membrane kybd (OPWM) Example B N/A
Engineering Workstation (ENWS) Example B N/A
Engineering/Software Server (ENSV) Example A N/A
Engineering/Software/Security Server (ENSV) Example A Example F
Engineering/Software/Security/Power Tools Server Example A Example F

(ESPT) (Multiple disks)
Engineering/Software/Power Tools Server (ESPT) Example A Example F

(Multiple disks)
Power Tools Database Server (PTSV) Example B Example F
Historian Report Server (HSRS) Example E Example G
Engineer/Software/Power Tools/Operator/Historian Example C Example D

Report Server (OMNI)
All other workstations (that is, non-servers) Example B N/A
Engineering/Software/Power Tools Server (ESPT) Example H N/A

(One disk)
Example A. 9 GB or Greater Disk
0 / 1000 (minimum)
3 0
4 0
5 0
7 /export/wdpf Remainder of disk (4000 minimum)
Example B. 5 GB or Greater Disk

0 / 1000 (minimum)
2 xxxx
3 0
4 0
5 0
6 /usr Remainder of disk (3000 minimum)
7 0
24 OS180_10
DROP TYPE SYSTEM DISK OTHER DISKS
Example C. 10 GB or Greater Disk
Note: In the following example,

(n = HSR partition number [0, 1, 2, 3] - normally "part_00")
(y = Oracle optional disks [0, 1, 2, 3] - normally "Lv00")

0 / 1000 (minimum)
2 xxxx
3 0
4 0
5 /usr/wdpf/hsr/archive/sec/part_0n 1000 (minimum)
6 /usr Remainder of disk (3000 minimum)
7 /export/wdpf 4000 (minimum)
Example D. 6 GB or Greater Disk


0
1
2 xxxx
3
4
5 /usr/wdpf/hsr/archive/sec/part_0n Remainder of disk
6 /Lv0y 6000 (minimum)
7 0
OS180_10 25
Example E. 7 GB or Greater Disk


0 / 1000 (minimum)
2 xxxx
3
4 0
5 /usr/wdpf/hsr/archive/sec/part_0n Remainder of disk (2000 minimum)
7 0
Example F. 6 GB or Greater Disk


0 0
1 0
2 xxxx
3 0
4 0
5 0
7 0
26 OS180_10
Example G. 4 GB or Greater Disk


0 0
1 0
2 xxxx
3 0
4
5 /usr/wdpf/hsr/archive/sec/part_0n 2000 (minimum)
6 0
7 0
Example H. 15 GB or Greater Disk


0 / 1000 (minimum)
2
3
4
7 /export/wdpf Remainder of disk (4000 minimum)
37. After the slice sizes and Mount Point names have been properly configured, select OK.
The Lay Out File System window appears again. The previously entered information is
displayed. If the information is correct, select Next.
OR
If the information is not correct, select the Modify button and redo the incorrect steps.
38. The Ready to Install window appears. Select Install Now.
39. Installation of Solaris 10 begins (CDROM 1 of 4 or the DVD). After a period of time, the
system reboots. A prompt appears asking if you need to override the system’s default NFS
version 4 domain name. Select No. Select the Enter button.
Messages appear informing the user as software is installed.
OS180_10 27
40. After the installation is complete, perform the following when the Specify Media window
appears:
a) Select the appropriate media (typically, CD/DVD). Select Next.
b) Insert the second Solaris 10 CDROM (disk 2 of 5). Select OK.
c) Installation of Solaris 10 begins (disk 2 of 5). The Installing Solaris Software window
appears. Select Install Now.
d) A Pausing window appears. Select Continue.
e) Repeat Step a through Step d for each consecutive CDROM (disks 3, 4, and 5).
41. The Installation Summary window appears. Select Next.
42. The Specify Media window for languages appears. Select Skip if you are using English (or
specify the appropriate language).
Select Skip Installation. A Pausing window appears. Select Continue.
43. The Reboot window appears. Select Reboot Now.
44. After the reboot is completed, a “drop<num>console login:” prompt appears. Type in
root. The Password prompt appears.
Type in the <applicable password>. The “#” prompt appears.
45. Proceed to install the Solaris 10 Patches and Third Party Software.
5.1.2 I NSTALLING S OLARIS 10 P ATCHES AND T HIRD -P ARTY SOFTWARE
Sun has supplied software modification patches for the Solaris 10 Operating System.
The patches applicable to the Ovation workstation drops are distributed on the Ovation Patches
CDROM. Install these patches at the Software Server.
You also need the Third-Party disk at this time to prepare the Server for installation of drivers and
Oracle partitioning. You will use the Third-Party disk later to install Third-Party application
programs.
5.1.3 T O INSTALL S OLARIS 10 P ATCHES AND T HIRD -P ARTY SOFTWARE

1. Insert the Ovation 1.8 Patches CDROM into the CDROM drive.
2. Start the CDE environment by entering the following:
/usr/dt/bin/dtlogin
3. Login as root. After CDE starts, enter root for the user name and the password. If
prompted, select CDE and OK. Right-click in the background and select Tools and then
Terminal.
CDROM.
28 OS180_10
5. Use the Software Maintenance Tool to select and install the required Solaris patches onto the
Software Server.
b) Select Solaris Patch Clusters.
c) Select Solaris 2.10 Solaris Patches.
e) Select Check Software Server Against Selected Packages and
Patches.
i) The Software Server Differences window appears.
j) Select the Select All button
m) Select Exit.
6. To install the Solaris patches into the Solaris Operating System on the Software Server, enter
the following in the Command Tool:
/cdrom/cdrom0/setup_scripts/install_patches
7. Type the following to reboot the Software Server:
reboot
8. After rebooting, a drop<num>console login: prompt appears. Type the
following:
root
9. The “Password” prompt appears. Type in the <applicable password>. The “#”
prompt appears. Type eject. Remove the Patches disk and insert the Third-Party disk.
You need the Third-Party disk at this time to prepare the Server for installation of drivers and
Oracle partitioning. You will use the Third-Party disk later to install Third-Party application
programs.
10. Enter the following in the Terminal window:
/cdrom/cdrom0/setup_scripts/setup
11. After some additional software packages are installed, the Software Server reboots.
12. After rebooting, a drop<num>console login: prompt appears. Type the following:
root
The Password prompt appears. Type in the <applicable password>.
The # prompt appears. Type eject to eject the Ovation 1.8 Third-Party Software CDROM.
13. Install the Ovation release software.
OS180_10 29
5.2 Installing Ovation release software on a Software Server
5.2 INSTALLING OVATION RELEASE SOFTWARE ON A SOFTWARE SERVER

Install the Ovation release software on the Software Server, configure the software as needed,
and then download it to the other workstations in the system. This process allows an entire
Ovation system to be loaded from one Software Server.
The Ovation release software required by the workstations is supplied on the Ovation Release
CDROM.
5.2.1 T O INSTALL O VATION RELEASE SOFTWARE ON A S OFTWARE S ERVER

1. Insert the Ovation Release CDROM into the CDROM drive.
2. Start the Common Desktop Environment (CDE) by entering the following:
/usr/dt/bin/dtlogin
3. Login as root. After CDE starts, enter root for the user name and for the password. If
prompted, select CDE and OK. Right-click in the background and select Tools and then
Terminal.
CDROM.
5. Use the Software Maintenance Tool to select and install the desired Ovation software
packages onto the Software Server.
a) Select the Clusters (1.8) menu item.
b) Select WEStation Package Clusters.
j) The Software Server Differences window appears.
n) Select Exit.
6. Enter eject in the Terminal window to eject the CDROM.
7. Configure and start the Software Server.
30 OS180_10
5.3 Configuring Ovation release software
5.3 CONFIGURING OVATION RELEASE SOFTWARE
After the Ovation workstation release software has been loaded, some initial configuration is
necessary before the system workstations can function as Ovation workstations.
The Ovation software release provides a workstation Graphical User Interface (GUI) package that
allows you to quickly and efficiently perform configuration functions. These functions are
performed through two utilities provided with the Ovation release and appearing initially as two
icons on a workstation screen. These utilities are the Initialization (Init) Tool and the
Administrative (Admin) Tool.
The Init Tool defines the drops in the Ovation system and defines what software packages will be
used on each drop.
The Admin tool configures the software packages and downloads software to the drops.
5.3.1 T O CONFIGURE O VATION RELEASE SOFTWARE
Use the following procedure to configure the Ovation release software (See Ovation Init and
Admin Tools User Guide.):
into the CDROM drive at the Software Server.
2. Enter the following command at the Software Server to display the icons for the Ovation Init
and Admin Tools (as superuser):
./configure &
Note: Ignore the CDE message that appears and check the indicated box so that the message
will not appear again. Select Continue.
3. The License Existence window appears. Select Confirm to accept the terms of the Emerson
license agreement.
OS180_10 31
message appears:

InitTool.


Enter 2 for a Software Server/Security Server combination
OR
Enter 3 for a Software Server only.

Ovation.domain.com.
6. The following message appears if you selected option 2 (Ovation Software Server/Security
Server combination):

password
New Password:
Re-enter New Password:.
Select Return and skip to Step 8.
7. If you selected option 3 (Ovation Software Server), no message appears.
Select Return and proceed to Step 8.
32 OS180_10
WARNING: No licenses installed. Some functionality will be

disabled.
Select the Acknowledge button.
9. Access the Init Tool and perform the license installations.
a) Every Ovation system must be assigned a license key. This key defines how many drops
of each drop type category are allowed in the system (such as Solaris-based Stations,
Windows-based Operator Stations, Controllers, and SIM Controllers). You enter
license key information in the Init Tool during the software installation process.
b) To obtain a license key, you must contact the Software Licensing Administrator at
Emerson and provide the host ID of the Software Server and the number of drops of each
drop category.
c) Perform the following to install a license:
¾ Select the Show/Install Licenses button. The License Information window appears.
¾ Enter the license key code (provided by Emerson) in the Enter Key Code entry field.
¾ Select the Install License button.
¾ The License Existence window appears. Select Confirm.
10. Use the Init Tool to define the network(s), units, domain, and drops as described in the
Ovation Init and Admin Tools User Guide. Select the Init Tool icon. The Ovation Initialization
Utility (Init) window appears:
11. Select Define Networks/Units from the Function dropdown menu. The Networks and Units
window appears.
a) Select the Insert/Modify Network button on the Networks and Units window. The
Insert/Modify Network window appears.
b) Enter the Network Name in the applicable entry field. Up to eight characters can be
used.
c) Enter a corresponding Network Index in the applicable entry field.
d) Enter a Network Alias.
e) Pull down the Insert menu, and select either Before or After to position the new local
Network entry in the Local Networks scrolling list.
Note: Currently, only one local network is allowed.
f) Select the Apply button. (The Cancel button closes the window without saving any of the
changes.) The new network appears in the Local Networks scrolling list on the Networks
and Units window.
When you click on the network in the scrolling list, the entry fields below the list (Network
Index and Network Alias) display the applicable information as it pertains to the selected
network.
12. Select the Insert Unit button on the Networks and Units window. The Insert Unit window
appears.
a) Enter the New Unit Name and corresponding Unit Index in the applicable entry fields
(the Index value (0 through 15) is used by the Database to identify the Unit).
OS180_10 33
b) Pull down the Insert menu, and select either Before or After to position the new unit
entry in the Units scrolling list. This positioning feature is only used to place the new unit
in the Units list, it has no affect on software functions. The units do not have to be in any
special order.
c) Select the Apply button. The new unit appears in the Units scrolling list on the Networks
and Units window. When you click on the unit in the scrolling list, the entry field below the
list (Unit Index) displays the applicable information as it pertains to the selected unit.
d) Click the menu button in the upper left corner of the Networks and Units window and
select Close to close the Networks and Units window.
13. Select Define Domain from the Function dropdown menu in the Init window. The Define NIS
Domain Information window appears.
a) Enter the Domain Server Host Name and the Domain Server IP Address. (This is the
name and IP address of the Security Server for your system. If this is a combination
Software Server/Security Server, use the Software Server name and IP address.)
b) Click the Apply button.
14. Select the Insert Drop button in the Init window.
a) Pull down the Drop Type menu and select the desired Software Server drop type:
¾ Engineering /Software Server
¾ Engineering/Software/Power Tools Server
¾ Engineering/Software/Security Server (This selection also places the Security Server
on the Software Server.)
¾ Engineering/Software/Security/Power Tools Server (This selection also places the
Security Server on the Software Server.)
b) Enter the appropriate information in the following entry fields (fields not applicable to the
selected drop type are grayed out):
¾ Enter an Ovation Network IP Address.
¾ Enter an Ovation Network name.
¾ Enter an Ovation Network Ethers Address.
¾ Enter an Ovation Unit name.
¾ Enter the Ovation Network Interface Type. The choices are:
SBUS FDDI (nf0)
PCI Bus FDDI (skfp0)
High-Speed Ethernet (hme0)
ZNYX Dual Ethernet (zrl0)
SunBlade (eri0)
Ovation Highway Interface (ohi0)
¾ Enter a Processor Hostid.
¾ Enter the type of hardware Architecture.
¾ Enter the appropriate Disk Partitioning choice.
¾ Select the Apply button.
¾ Select the Save Configuration to Disk button.
34 OS180_10
15. After you have defined the Software Server, you must define one other workstation at this
time, but other drops may be defined later. You must define the other workstation at this time
in order that an image of the Solaris disks can be copied to the Software Server.
16. Access and use the Admin Tool to configure the following workstation parameters. (See
Ovation Init and Admin Tools User Guide.) Set the following items during the initial installation
to ensure security can be properly configured by the administrator.
a) DDB Setting:
Function: Define Software Configuration
Filter: Base Software
Topic: Ovation DDB Configuration
Make sure that the DDB Interface is set to the appropriate interface.
Make sure that the DDB Interface is set to the appropriate interface. If you are using an OHI
driver, and select Ovation Highway Interface (ohi0), you must choose the settings that are
appropriate for your computer. The available interface choices for the OHI driver are defined
in the following table:
PRIM ARY BACKUP DESCRIPTION OF H ARDW ARE FOR DDB INTERFACE

INTERFACE INTERFACE
afe0 (Linksys) eri0 Linksys card and onboard connection on SunBlade

afe0 (Linksys) bge0 Linksys card and onboard connection on Ultra 25 , 45
eri0 hme0 Onboard on SunBlade and port on SCSI card
afe0 (Linksys) hme0 Linksys card and onboard connection on UltraSPARC 5, 10,
60
hme0 hme1 Onboard on UltraSPARC 5, 10, 60 and port on SCSI card
afe0 (Linksys) afe1 (Linksys) Two Linksys cards
tu0 (Znyx) tu1 (Znyx) Two ports on Znyx card
bge0 bge1 Two onboard ports on Ultra 25, 45
b) Controller Setting:
Filter: Controller Software
Topic: Controller Configuration Parameters
The OCR400 Controller is the default Controller. Make sure the correct Controller type is
selected.
c) Service Settings:
Topic: Service Configuration
Make sure that all the items in the Service Configuration window are set to Enable
Service.
d) Select the Install Configuration on Software Server function, all filters, and all topics to
install the configuration changes on the Software Server.
e) Select the Install button.
OS180_10 35
17. After the installation is completed, perform the following (as superuser):
a) Type eject at the Software Server to eject the Solaris disk (1 of 5).
b) Insert the Solaris CDROM (disk 2 of 5) into the CDROM drive at the Software Server.
c) Type the following at the Server:
cd /cdrom/cdrom0/Solaris_10/Tools
d) Then type the following:
./add_to_install_server /export/wdpf/solaris/cd_image
e) Type cd to change to the default directory.
f) After the image is copied to the disk, type “eject” at the Software Server to eject the
Solaris disk (2 of 5).
g) Repeat Step b through Step f for each consecutive Solaris CDROM (disks 3, 4, and 5).
18. After the installation is complete, select the Properties button in the Admin Tool window. The
Properties window appears.
Select No for Preview Downloaded Files (since this is a complete download, preview is not
necessary). Select Build for Build/Verify Configuration. Select the Apply button.
19. Use the Admin Tool to select the Download Configuration to Drops function, All filters, and
the Drop Number for the Software Server. Select Download.
A pop-up window appears with the message “The Program ss_rpc is not running.” Select the
Start ss_rpc button. The Start ss_rpc window appears. Enter the root password and select
the Start ss_rpc button.
20. Repeat Download:
Function: Download Configuration to Drops
Filter: Select All
Drop: Software Server
Download
36 OS180_10
21. If the machine is configured with a redundant Ethernet connector or any FDDI network
connector, type one of the following commands in a Terminal window to adjust the
/etc/hostname file for the applicable hardware configuration.
If the machine is not configured with a redundant Ethernet connector or an FDDI connector,
skip to Step 22.

TYPE TYPE
Redundant Sun Fast Ethernet mv /etc/hostname.eri0

Blade /etc/hostname.zrl0
Redundant Fast Ethernet mv /etc/hostname.hme0
UltraSPARC 5, /etc/hostname.ohi0
10,60 (using ohi0
card)
Redundant Sun Fast Ethernet mv /etc/hostname.eri0
Blade /etc/hostname.ohi0
(using ohi0
card)
Redundant Ultra 25 Fast Ethernet mv /etc/hostname.bge0
and 45 /etc/hostname.ohi0
Non-redundant Fast Ethernet /etc/hostname.hme0

UltraSPARC 5, 10,
60 (no change is needed)
Non-redundant Sun Fast Ethernet /etc/hostname.eri0

Blade
(no change is needed)
Non-redundant Ultra Fast Ethernet /etc/hostname.bge0
25 and 45
(no change is needed)
UltraSPARC FDDI mv /etc/hostname.hme0
5,10,60 /etc/hostname.skfp0
Sun Blade FDDI mv /etc/hostname.eri0
machines /etc/hostname.skfp0
22. Reboot the machine by typing the following:

init 6
23. After rebooting, the workstation will come up as an Ovation Software Server displaying the
Ovation user interfaces.
24. Install the Third-Party Software.
OS180_10 37
5.4 Installing Third-Party software on a Software Server
5.4 I N S T A L L I N G T H I R D -P A R T Y SOFTWARE ON A SOFTWARE SERVER

Many systems use Third-Party software that works with the Ovation release software to support
various functions. An example of this is the use of Applix software to create reports.
You need to install Third-Party software on the Ovation Software Server if Third-Party software is
needed to support functions on the Software Server.
For Ovation releases 1.8 and greater, the Third-Party software is provided on and accessed from
the Ovation 1.8 Third-Party Software CDROM.
5.4.1 T O INSTALL T HIRD -P ARTY SOFTWARE ON A S OFTWARE S ERVER

1. Open a Terminal window.
2. Become the root user at the Software Server:
su
<applicable password>
3. Insert the Ovation Third-Party Software CDROM into the CDROM drive.
4. Enter the following at the Software Server to install the third- party script:
/etc/wdpf_config/install_third_party
A list of available software packages appears. Select the desired package by typing the name
of the package.
5. When you have completed the installation of the desired packages, enter eject in the
Terminal window to eject the CDROM.
Note: If you plan to run Ovation Control Builder on the Server, you need to install AutoCAD on
the Server. You must install AutoCAD individually on each machine that runs Control Builder.
38 OS180_10
S E C T I O N 6
LOADING WORKSTATIONS THAT CONTAIN AT LEAST 384 MB

OF RAM
IN THIS SECTION
Installing Solaris 10, Solaris 10 patches, and Ovation software ....................................... 39

Installing Third-Party software........................................................................................... 42
6.1 I N S T A L L I N G S O L A R I S 10, S O L A R I S 10 PA T C H E S , A N D OVATION SOFTWARE
Software installed on the Ovation Software Server is downloaded to Ovation workstations from
the Server. This can be done only after you install the following software on the Software Server:
Solaris 10 software has been loaded on the Software Server.
Solaris patches have been loaded on the Software Server.
Ovation release software has been loaded onto the Software Server.
The workstation being loaded has been defined by the Init Tool and installed on the Software
Server by the Admin Tool. (See Ovation Init and Admin Tools User Guide.)
6.1.1 T O INSTALL SOFTWARE ON F AST E THERNET SYSTEM DROPS
processor (if this has been disabled, try entering init 0 in a terminal window).
2. The “ok” prompt appears.
3. If loading a redundant UltraSPARC 5, 10, 60 or Sun Blade machine on a Fast Ethernet
system, do the following:
a) Temporarily disconnect one cable from the Zynx card and connect it to the onboard
Ethernet port for that drop.
b) Enter the command boot net - install at the “ok” prompt. This loads the
drop. After the drop has been successfully loaded, it will boot up with the Ovation Desktop
being displayed.
c) Disconnect the cable from the Ethernet port, and reconnect it to the Zynx card.
4. If loading a non-redundant UltraSPARC 5, 10, 60 or Sun Blade machine on a Fast Ethernet
system, enter the following command at the “ok” prompt:
boot net - install
5. The Select a Language prompt appears.
Select the appropriate language. Select the Enter button.
OS180_10 39
6.1 Installing Solaris 10, Solaris 10 patches, and Ovation software

7. The Host Name for eri0 window appears. Select Next.
8. The IP Address window appears. Select Next.
9. The Netmask window appears. Enter the Netmask address in the entry field. See the Project
Engineer or System Administrator for the correct Netmask address.
OR
If this drop will be connected to the Internet, select Specify One. Select Next.
The second Set the Default Route window appears. Enter the IP address for the default
router. See the Project Engineer or System Administrator for the correct IP address.
12. The Kerberos window appears. Select No.
15. The Continent and Country window appears. Select the appropriate timezones. Select Next.
16. The Date and Time window appears. If the displayed information is correct, select Next.
If the displayed information is not correct, enter the correct information, and select Next.
17. The Root Password window appears. Enter the root password and then enter it again. Select
Next.
18. The Confirm Information window appears. The previously entered information is displayed.
Verify that the information is correct. If the information is not correct, use the Back button to
go back and correct the errors as needed.
19. After you have confirmed that the information is correct, select Confirm.
21. This procedure will then install Solaris 10, Solaris 10 patches, and the Ovation workstation
release software across the network from the Software Server to the workstation.
Note: During the installation, login messages may appear. Ignore these messages.
22. The workstation automatically reboots and comes up as an Ovation workstation.
6.1.2 T O INSTALL SOFTWARE ON FDDI SYSTEM DROPS
1. Press the Stop and the a key simultaneously on the Sun keyboard in order to halt the Sun
40 OS180_10
3. You must use an Ethernet connection to load a workstation on an FDDI system:

a) Use an Ethernet cable to connect the drop to be loaded and the Software Server to an
Ethernet Hub or use a direct Ethernet connection between the drop and the Software
Server.
b) Become superuser at the Software Server and enter at the prompt:
cd /etc <Enter>
(For UltraSPARC 5, 10, 60)
mv hostname.skfp0 hostname.hme0 <Enter>
(For Sun Blade)
mv hostname.skfp0 hostname.eri0 <Enter>
init 6 <Enter>
c) The Software Server reboots. After the Server comes back up, halt the drop that is to be
loaded
(Stop + a), and enter the following at the “ok” prompt:
boot net - install
d) Answer the prompts appropriately until you are asked if the information is correct, and
then select YES.
e) After the drop has been successfully loaded, it will boot up with the Ovation Desktop
being displayed.
f) Disconnect the Ethernet cable.
g) At the Software Server, enter the following to switch back from Ethernet to FDDI
connection:
cd /etc <Enter>
(For UltraSPARC 5, 10, 60)
mv hostname.hme0 hostname.skfp0 <Enter>
(For Sun Blade)
mv hostname.eri0 hostname.skfp0 <Enter>
init 6 <Enter>
4. The Select a Language prompt appears.
Select the appropriate language. Select the Enter button.
6. The Host Name for eri0 window appears. Select Next.
7. The IP Address window appears. Select Next.
If this drop will not be connected to an existing Ethernet network, then leave the Netmask
value as 255.255.255.0.
Note: If this drop will be connected to an existing Ethernet network, see the Project Engineer or
System Administrator for the correct Netmask address.

OS180_10 41
6.2 Installing Third-Party software

OR
If this drop will be connected to the Internet, select Specify One.
Select Next.
The second Set the Default Route window appears. Enter the IP address for the default
router. See the Project Engineer or System Administrator for the correct IP address.
11. The Kerberos window appears. Select No.
14. The Continent and Country window appears. Select the appropriate timezones. Select Next.
15. The Date and Time window appears. If the displayed information is correct, select Next.
If the displayed information is not correct, enter the correct information, and select Next.
16. The Root Password window appears. Enter the root password and then enter it again. Select
Next.
17. The Confirm Information window appears. The previously entered information displays. Verify
that the information is correct. If the information is not correct, use the Back button to go back
and correct the errors as needed.
18. After you have confirmed that the information is correct, select Confirm.
20. This procedure will then install Solaris 10, Solaris 10 patches, and the Ovation workstation
release software across the network from the Software Server to the workstation.
21. After the operating system is loaded, a message appears prompting for the initial entry for the
system administrator (root or superuser) password. Enter the <applicable password>. A
prompt appears again. Enter the <applicable password> again.
22. The workstation will automatically reboot and come up as an Ovation workstation.
6.2 I N S T A L L I N G T H I R D -P A R T Y SOFTWARE
Many systems use third-party software that works with the Ovation release software to support
You need to install third-party software on the Ovation Software Server if third-party software is
needed to support functions on the Ovation workstation.
For Ovation releases 1.8 and greater, the third-party software is provided on and accessed from
42 OS180_10
6.2.1 T O INSTALL T HIRD -P ARTY SOFTWARE

1. Insert the Third-Party Software CDROM into the CDROM player at the Ovation workstation.
2. Enter the following at the workstation where the software is to be installed:
su
3. A list of available software packages appear. Select the desired package by typing the name
of the package.
OS180_10 43
S E C T I O N 7
LOADING WORKSTATIONS THAT CONTAIN LESS THAN 384

MB OF RAM
IN THIS SECTION
Installing Solaris 10, Solaris 10 patches, and Ovation software ....................................... 45

Installing Third-Party software........................................................................................... 47
7.1 I N S T A L L I N G S O L A R I S 10, S O L A R I S 10 PA T C H E S , A N D OVATION SOFTWARE
Software installed on the Ovation Software Server is downloaded to Ovation workstations from
the Server. This can be done only after you install the following software on the Software Server:
Solaris 10 software has been loaded on the Software Server.
Solaris patches have been loaded on the Software Server.
Ovation release software has been loaded onto the Software Server.
The workstation being loaded has been defined by the Init Tool and installed on the Software
Server by the Admin Tool. (See Ovation Init and Admin Tools User Guide.)
7.1.1 T O INSTALL SOFTWARE ON F AST E THERNET SYSTEM DROPS
3. If loading a redundant UltraSPARC 5, 10, 60 or Sun Blade machine on a Fast Ethernet
system, do the following:
a) Temporarily disconnect one cable from the Zynx card and connect it to the onboard
Ethernet port for that drop.
b) Enter the command boot net - install at the “ok” prompt. This will load the
drop. After the drop has been successfully loaded, it will boot up with the Ovation Desktop
being displayed.
c) Disconnect the cable from the Ethernet port, and re-connect it to the Zynx card.
4. If loading a non-redundant UltraSPARC 5, 10, 60 or Sun Blade machine on a Fast Ethernet
system, enter the following command at the “ok” prompt:
boot net - install
5. The Select a Language prompt appears. Select the appropriate language. Select the Enter
button.
OS180_10 45
6. The Solaris Installation Program window appears. Select F2.
Note: Use your computer arrow keys to navigate in these windows. Select the F2 key to
continue, the F4 key to go back, and the Space Bar to select a choice.
7. The Identify this System window appears. Select F2.

8. The IPV6 for eri0 window appears. Select No. Select F2.
9. The Set Default Route for eri0 window appears.
OR
If this drop will be connected to the Internet, select Specify One. Select F2.
The IP Address prompt appears. Enter the IP address for the default router. See the Project
Engineer or System Administrator for the correct IP address. Select F2.
10. The Configuring Security window appears. Select No. Select F2.
11. The Confirmation Information window appears. If the information is correct, select F2. If the
information is not correct, select F4 to go back and correct the information.
12. The Name Service window appears. Select None. Select F2.
14. The Subnet window appears. Select Yes and F2.
15. The Netmask window appears. Enter the appropriate netmask. Select F2.
16. The Time Zone window appears. Select the appropriate choice from the Continents and
Oceans list. Select F2.
17. The Country or Region window appears. Select the appropriate choice from the Countries
and Regions list. Select F2.
18. The Date and Time window appears. If the settings are correct, select F2. If the settings are
not correct, edit them and select F2.
20. Solaris is loaded from the Software Server. The workstation will reboot.
21. A prompt appears asking if you need to override the system’s default NFS version 4 domain
name. Select No. Messages appear informing the user as software is installed.
22. Ovation is loaded from the Software Server. The workstation will reboot.
23. Ovation configuration is loaded from the Software Server. The workstation will reboot.
24. The workstation will automatically reboot and come up as an Ovation workstation.
46 OS180_10
7.2 I N S T A L L I N G T H I R D -P A R T Y SOFTWARE
Many systems use third-party software that works with the Ovation release software to support
You need to install third-party software on the Ovation Software Server if third-party software is
needed to support functions on the Ovation workstation.
For Ovation releases 1.8 and greater, the third-party software is provided on and accessed from
7.2.1 T O INSTALL T HIRD -P ARTY SOFTWARE

1. Insert the Third-Party Software CDROM into the CDROM player at the Ovation workstation.
2. Enter the following at the workstation where the software is to be installed:
su
3. A list of available software packages appear. Select the desired package by typing the name
of the package.
OS180_10 47
S E C T I O N 8
INSTALLING AUTOCAD
IN THIS SECTION
What is AutoCAD? ............................................................................................................ 49

To install AutoCAD............................................................................................................ 49
8.1 WHAT IS A U T O CAD?

AutoCAD is a full-featured program used for computer-aided design (CAD). The Ovation Control
Builder (OCB) runs on top of the AutoCAD package and provides functions that are used to build
the control sheets used by the Control Builder.
8.2 TO INSTALL A U T O CAD

The Control Builder requires the AutoCAD package to create its control sheets. AutoCAD is
provided on a CDROM along with your system. This CD contains the install shield for AutoCAD,
the AutoCAD license, and the Uninstall AutoCAD License programs.
Note: You must install AutoCAD individually on each machine that runs the Control Builder.
1. Insert the Control Builder/AutoCAD CDROM in the CDROM drive and type the following in a
Terminal window:
cd / <enter>
su - <enter>
cd /cdrom/cdrom0 <enter>
./InstallAcad <enter>
2. The system will request the destination path for the AutoCAD installation. Type the following:
/usr <enter>
3. The system will display the available disk space and ask if it is acceptable. Type the following:
y <enter>
4. After the program installation is complete, the system will ask if you wish to install the license.
Type the following:
y <enter>
5. The system will request the destination path for the license. Type the following:
/usr <enter>
6. The system will ask how many licenses to install. Enter the number of licenses that your
Project has requested.
OS180_10 49
8.2 To install AutoCAD
Note: You may have one license but more than one Engineering Station drop. In this
configuration, only one Control Builder program can run at a time on a first come - first served
basis. You must install AutoCAD on the other Engineering Station drops using the Licensed
Host Drop number as its license.
OR
You may have more than one license if you require multiple users on AutoCAD at the same
time. Again, you must install AutoCAD on the other Engineering Station drops using the
Licensed Host Drop number as its license. The number of licenses determines how many
Control Builders can be used at the same time.
7. The system will display a series of numbers and ask for the License Key.
Record the series of numbers, your project number, drop number, and hostid and send the
information to the License Administrator at Emerson Process Management.
8. Once your License Key is received, enter the following to return to the License Installation
section:
cd /cdrom/cdrom0 <enter>
./InstallLicense <enter>
9. When prompted for the License Key, enter the license numbers for your drop.
10. To verify the installation and that the licenses are valid, start the Control Builder using the
following path:
<Top Level for Role>Functions menu
Tools menu
Power Tools menu
Control Builder.
11. For multiple license users, start the Control Builder on each of the Engineering Station drops
and verify that the number of licenses entered is the maximum number of Control Builders
that can be opened at one time.
12. If you have only one license, but other Engineering Station drops, verify that each drop can
start the Control Builder (provided that no one else is using the license).
Note: If the Control Builder Configuration menu fails to open, look in the General Message
Display window (located at the Operator Station) for information about the cause of failure.
Typically, the license was not correct or there are more users than there are valid licenses.
50 OS180_10
S E C T I O N 9
UPDATING YOUR OVATION SOFTWARE SERVER
IN THIS SECTION
What are software updates? ............................................................................................. 51

Updating Solaris 10 patches (Software Server)................................................................ 51
Updating Ovation release software (Software Server) ..................................................... 53
Updating Third-Party software (Software Server) ............................................................. 56
9.1 WHAT ARE SOFTWARE UPDATES?
Software updates are patches and updates to existing software packages. Updates are not
upgrades (see page 59).
Emerson periodically distributes updates to Solaris 10 patches, Ovation release software, and
third-party software on Ovation release CDROMs.
Prior to the availability of a periodic Ovation release CDROM, updates may be distributed via
tape, floppy, CDROM, e-mail, ftp site, or Intranet.
9.2 U P D A T I N G S O L A R I S 10 PATCHES (S O F T W A R E S E R V E R )
Sun supplies and updates software modification patches for the Solaris 10 Operating System.
Updates to the patches applicable to the Ovation workstation drops may be distributed on Ovation
release CDROMs, tape, floppy, CDROM, e-mail, ftp site, or Intranet.
9.2.1 T O UPDATE S OLARIS 10 PATCHES (S OFTWARE S ERVER ) USING THE S OFTWARE

M AINTENANCE T OOL
1. If the patch updates are being loaded from a CDROM, insert the CDROM into the CDROM
drive and access the Software Maintenance Tool by entering the following in a Terminal
window:
su
Proceed to Step 2.
OR
OS180_10 51
9.2 Updating Solaris 10 patches (Software Server)
If the patch updates are being loaded from a tape, floppy, or CDROM, extract the patch
update files by entering the following in a Terminal window:
su
cd /export/wdpf/patch_updates
tar xvf xxxxxx
where (xxxxxx is the tape, floppy, or CD device name)
Then, access the Software Maintenance Tool by entering the following in a Terminal window:
/export/wdpf/swmaint/swmaint &
Proceed to Step 2.
OR
If the patch updates are being loaded from a file distributed via e-mail, ftp site, or Intranet,
copy the file to the /tmp directory. Extract the patch update files by entering the following in
a Terminal window:
su
cd /export/wdpf/patch_updates
tar xvf /tmp/xxxxxx
where (xxxxxx is the filename)
Then, access the Software Maintenance Tool by entering:
Proceed to Step 2.
2. To update an entire cluster of Solaris patches, perform the following in the Software
Maintenance Tool:
b) Select the Solaris Patch Clusters menu item.
c) Select the desired Solaris Cluster from the list of available clusters.
i) The Software Server Differences window appears. Select the Select All button.
j) Select the Update Software Server button.
k) After the update is complete, select the File menu item on the main window.
l) Select Exit and skip to Step 4.
3. To update individual Solaris patch(s), perform the following in the Software Maintenance
Tool:
a) Select the View menu item.
b) Select Details of Solaris Patches Available for Installation (where more recent
patches exist).
c) On the scrolling list of more recent patches, select the desired patch to update.
52 OS180_10
9.3 Updating Ovation release software (Software Server)
d) Select the Select Revision XXXX button to select the desired revision of the patch.
e) Repeat Steps c and d to select all desired patch updates.
f) Select the Check menu item.
g) Select Check Software Server Against Selected Packages and Patches.
h) Unselect all WEStation Packages options.
i) Select all Solaris Patch options.
j) Select the Start Checking button.
k) The Software Server Differences window appears. Select the desired patch(s).
n) Select Exit.
4. To install the Solaris patches into the Solaris Operating System on the Software Server, enter
the following in a Command Tool window (use one line to enter the following):
cp /export/wdpf/rel/ssw/load_kit/boot_server
/S91_LOAD_PATCHES /etc/rc3.d
5. Type the following command to reboot the Software Server:
reboot
6. If the Solaris patch update(s) were installed using the /export/wdpf/patch_updates
directory, perform the following:
a) Remove the tar.Z file(s) from /export/wdpf/patch_updates.
b) Remove the corresponding patch information file(s) for the removed tar.Z file(s) from the
info subdirectory under /export/wdpf/patch_updates.
9.3 UPDATING OVATION RELEASE SOFTWARE (S O F T W A R E S E R V E R )

Emerson distributes updates to the Ovation release software on Ovation release CDROMs, tape,
floppy, CDROM, e-mail, ftp site, or Intranet.
9.3.1 T O UPDATE O VATION RELEASE SOFTWARE (S OFTWARE S ERVER ) USING THE

S OFTWARE M AINTENANCE T OOL
1. If the Ovation release software updates are being loaded from an Ovation release CDROM,
insert the CDROM into the CDROM drive and access the Software Maintenance Tool by
entering the following in a Terminal window:
su
Proceed to Step 2.
OR
OS180_10 53
If the Ovation release software updates are being loaded from a tape, floppy, or CDROM,
extract the Ovation release software update files by entering the following in a Terminal
window:
su
cd /export/wdpf/wdpf_updates
tar xvf xxxxxx
where (xxxxxx is the tape, floppy, or CD device name)
Proceed to Step 2.
OR
If the Ovation release software updates are being loaded from a file distributed via e-mail, ftp
site, or Intranet, copy the file to the /tmp directory. Extract the Ovation release software
update files by entering the following in a Terminal window:
su
cd /export/wdpf/wdpf_updates
tar xvf /tmp/xxxxxx
where (xxxxxx is the filename)
Proceed to Step 2.
2. To update an entire cluster of Ovation WEStation patches, perform the following in the
Software Maintenance Tool:
b) Select the WEStation Package Clusters menu item.
c) Select the desired WEStation Cluster from the list of available clusters.
Note: Check for any modified files that should be saved.

i) Select the Start Checking button. The Software Server Differences window appears.
CAUTION! Confirm that ALL the actions in the scrolling list are desired. For example,
packages might be selected for removal that should not be removed.
j) Select the Select All button.

54 OS180_10
m) Select Exit and skip to Step 4.

3. To update individual Ovation patches, perform the following in the Software Maintenance
Tool:
a) Select the View menu item.
b) Select Details of WEStation Packages Available for Installation (where more recent
patches exist).
c) On the scrolling list of more recent WEStation packages, select the desired WEStation
package to update.
d) Select the Information for Revision button for the desired revision of the WEStation
package.
e) Select the Select Revision XXXX button to select the desired revision of the WEStation
package.
f) Repeat Steps C and D to select all desired WEStation package updates.
g) Select the Check menu item.
h) Select Check Software Server Against Selected Packages and Patches.
Note: Check for any modified files that should be saved.
i) Select Check Package Dependencies for WEStation Packages.

j) Select Check Installed Versions for WEStation Packages.
k) Unselect all Solaris Patch options.
l) Select the Start Checking button. The Software Server Differences window appears.
CAUTION! Confirm that ALL the actions in the scrolling list are desired. For example,
packages might be selected for removal that should not be removed.
m) Select the Select All button.

n) Select the Update Software Server button.
o) After the update is complete, select the File menu item on the main window.
p) Select Exit.
4. Access and use the Admin Tool. (See Ovation Init and Admin Tool User Guide.):
a) Select the Install Configuration on Software Server function, All filters, and All topics
to install the configuration on the Software Server.
b) Select the Download Configuration to Drops function, All filters, and the Drop Number
for the Software Server. Select the Download button.
c) Select the Bootstrap Drops button to reboot the Software Server.
5. After rebooting, the Software Server will start up using the updated Ovation release software.
6. If the Ovation release software update(s) were installed using the
/export/wdpf/wdpf_updates directory, perform the following:
a) Remove the tar.Z file(s) from /export/wdpf/wdpf_updates.
b) Remove the corresponding Ovation release software information file(s) for the removed
tar.Z file(s) from the info subdirectory under /export/wdpf/wdpf_updates.
OS180_10 55
9.4 Updating Third-Party software (Software Server)
9.4 U P D A T I N G T H I R D -P A R T Y SOFTWARE (S O F T W A R E S E R V E R )
Updates to third-party software are distributed periodically on Ovation 10 Third-Party Software
and Patches CDROMs.
Updating third-party software on the Software Server is only necessary if third-party software is
needed to support functions on the Software Server.
9.4.1 T O UPDATE T HIRD -P ARTY SOFTWARE (S OFTWARE S ERVER )

1. Enter the following to become the root user at the Software Server :
su
2. Insert the Ovation 10 Third Party Software CDROM into the CDROM player at the Software
Server.
3. Enter the following at the Software Server to install the Third-Party script:
A list of available software packages appears. Select the desired package by typing the name
of the package.
56 OS180_10
S E C T I O N 10
UPDATING ALL OTHER OVATION WORKSTATIONS
IN THIS SECTION
Updating Solaris 10 patches (workstations)...................................................................... 57

What are Software updates?............................................................................................. 57
Updating Ovation release software (workstations) ........................................................... 58
Updating Third-Party software (workstation)..................................................................... 58
10.1 U P D A T I N G S O L A R I S 10 PATCHES (WORKSTATIONS)

Sun supplies and updates software modification patches for the Solaris 10 Operating System.
Updates to the patches applicable to the Ovation workstation drops may be distributed on Ovation
release CDROMs, tape, floppy, CDROM, e-mail, ftp site, or Intranet.
Before updates to Solaris 10 patches can be loaded on Ovation workstations other than the
Software Server, the Solaris patch updates must first be loaded on the Software Server.
10.1.1 T O UPDATE S OLARIS 10 PATCHES ( WORKSTATIONS )

1. Enter the following to become the root user at the Ovation workstation where the patch
updates are to be installed:
su
2. Copy the file that will install the Solaris patches during the next reboot:
cp /etc/wdpf_config/S91_LOAD_PATCHES /etc/rc3.d
3. Reboot the Ovation workstation:
reboot
10.2 W H A T ARE SOFTWARE UPDATES?
Software updates are patches and updates to existing software packages. Updates are not
upgrades (see page 59).
Emerson periodically distributes updates to Solaris 10 patches, Ovation release software, and
third-party software on Ovation release CDROMs.
Prior to the availability of a periodic Ovation release CDROM, updates may be distributed via
tape, floppy, CDROM, e-mail, ftp site, or Intranet.
OS180_10 57
10.3 Updating Ovation release software (workstations)
10.3 U P D A T I N G O V A T I O N RELEASE SOFTWARE ( W O R K ST A T I O N S )

Updates to the Ovation release software may be distributed on Ovation release CDROMs, tape,
floppy, CDROM, e-mail, ftp site, or Intranet.
Before updates to Ovation release software can be loaded on Ovation workstations other than the
Software Server, the Ovation release software updates must first be loaded on the Software
Server.
10.3.1 T O UPDATE O VATION RELEASE SOFTWARE ( WORKSTATION )

1. At the Software Server, access and use the Admin Tool. (See Ovation Init and Admin Tools
User Guide.):
a) Select the Download Configuration to Drops function, All filters, and Drop Number for
the Ovation workstation.
b) Select the Download button.
c) Select the Bootstrap Drops button to reboot the Ovation workstation.
2. After rebooting, the Ovation workstation starts using the updated Ovation release software.
10.4 U P D A T I N G T H I R D -P A R T Y SOFTWARE (WORKSTATION)

Updates to third-party software are distributed periodically on Ovation 10 Third-Party Software
CDROMs.
Updating third-party software on an Ovation workstation is only necessary if third-party software is

needed to support functions on that workstation.
10.4.1 T O UPDATE T HIRD -P ARTY SOFTWARE ( WORKSTATION )

1. Insert the Ovation 10 Third-Party Software CDROM into the CDROM player at the Software
Server or at the workstation.
2. Enter the following at the Ovation workstation where the third-party software is to be installed:
su
3. A list of available software packages appears. Select the desired package by typing the name
of the package.
58 OS180_10
S E C T I O N 11
UPGRADING YOUR OVATION SYSTEM
IN THIS SECTION
What is a system upgrade?............................................................................................... 59
11.1 W H A T IS A SYSTEM UPGRADE?
A system upgrade occurs when you replace your current Ovation software release with a new
Ovation release. Typically, an Emerson field engineer performs the upgrade to ensure that the
system functionality is maintained after the upgrade. Upgrades are not updates (see page 57).
11.1.1 T O UPGRADE AN O VATION SYSTEM FROM O VATION 1. X TO 1.8
The following procedure is an overview of the steps used to upgrade an Ovation system from 1.x
(not 1.7 (see page 60)) to Ovation 1.8:
1. Back up your existing system data using the Backup procedures described in the Ovation
Software Installation Manual provided for your existing system. The following information
should be backed up and stored in a safe location where it will not be lost or corrupted during
the upgrade:
Power Tools database (Oracle files)
Use both exp (Oracle utility that performs a complete backup and retains the System IDs)
and ptdbexp (Power Tools utility that performs a partial backup). You can then choose
the type of restoration that is best for your upgrading situation.
Custom graphics
Control Builder Drawings
HSR Pic files
Log Reports
All applicable licensing information (make sure you have recorded all the license codes
you will need to re-install Ovation and third-party packages that are licensed applications.
These codes are typically issued by the Emerson Software Licensing Administrator).
Note: After completing your upgrade to Ovation 1.8, you can then use the standard Backup
procedures (see page 71) for all your future system backups.
2. Install Solaris 10 at your Software Server (see page 21) or workstation (see page 39).
Reformat the disks as needed. It is recommended that you increase the disk partition size for
the disk that will contain the Oracle files to a minimum of 6 gigabytes.
3. Install the Solaris 10 patches at your Software Server (see page 14) or workstation (see page
39).
OS180_10 59
11.1 What is a system upgrade?
4. Install the Ovation software at your Software Server (see page 30) or workstation (see page
39).
5. Re-install AutoCAD (see page 49) at any drop the runs the Control Builder.
6. Install the third-party software at your Software Server (see page 38) or workstation (see
page 47).
7. After you have upgraded Solaris and Ovation software, restore (see page 89) the Oracle
database from your database backups (performed in Step 1).
8. Reload the Ovation Control Builder drawings (see page 92).
9. Install all other Ovation software packages (such as ODBC Server) that were on the
workstation and were configured through the Admin Tool. Make sure you re-install these
packages before any configuration of the new software is done through the Admin Tool.
10. Use the Drop Loader to Clear and Load the drops and Controllers. (See Ovation Init and
Admin Tools User Guide.)
11.1.2 T O UPGRADE AN O VATION SYSTEM FROM 1.7. X TO 1.8
The following procedure is an overview of the steps used to upgrade an Ovation system from
1.7.x to Ovation 1.8 (for upgrades of systems prior to 1.7, see To Upgrade an Ovation System
(see page 59)".
1. Back up your existing system data using the Backup procedures described in the Ovation
Software Installation Manual installation Manual provided for your existing system. The
following information should be backed up and stored in a safe location where it will not be
lost or corrupted during the upgrade:
Power Tools database (Oracle files)
Use both exp (Oracle utility that performs a complete backup and retains the System IDs)
and ptdbexp (Power Tools utility that performs a partial backup). You can then choose
the type of restoration that is best for your upgrading situation.
Custom graphics
Control Builder Drawings
HSR Pic files
Log Reports
All applicable licensing information (make sure you have recorded all the license codes
you will need to re-install Ovation and third-party packages that are licensed applications.
These codes are typically issued by the Emerson Software Licensing Administrator).
Note: After completing your upgrade to Ovation 1.8, you can then use the standard Backup
procedures (see page 71) for all your future system backups.
2. Install the Ovation software at your Software Server (see page 30) or workstation (see page
39).
3. Upgrade Ethernet Znyx drivers to Tulip drivers:
Update drivers on computers with Znyx cards (see page 61).
Update drivers on computers with Linksys cards (see page 62).
Install the Solaris 10 patches at your Software Server or workstation.
60 OS180_10
11.1.3 T O UPGRADE DRIVERS FOR COMPUTERS WITH Z NYX CARDS

1. Insert the 1.8 Third-Party CDROM into the CDROM drive at the Software Server.
2. Enter the following in a Terminal window to copy the new tu and ohi drivers to the Server:
su
cd /export/wdpf/solaris/required_add_on
cp /cdrom/cdrom0/required_add_on/WXtu.tar.Z .
cp /cdrom/cdrom0/required_add_on/WXohi.tar.Z .
3. Enter the following in a Terminal window to delete the old Znyx driver from the Server:
rm ZNYXnb.tar.Z
4. Perform Steps 4 - 13 on all drops in the network that use Znyx cards:
a) Enter the following in a Terminal window to setup the drop to run on the onboard driver.
Use the following table to determine the appropriate hostname file extension to use in
the command lines.
mv /etc/hostname.zrl0
/etc/hostname.<network_interface_name>
Hostname File Choices
HARDWARE TYPE <NETWORK_INTERF ACE_NAM E>
UltraSPARC 5,10, 60 hme0

Sun Blade 150 eri0
Ultra 25, 45 bge0
b) Enter the following in a Terminal window to manually change the IFNAME=zrl0 entry:
vi /etc/rc2.d/S84ddb
IFNAME=<network_interface_name>
c) Reboot the drop.
5. Copy or ftp two software packages from the Server to /tmp directory on each drop:
su
cd /tmp
cp /export/wdpf/solaris/required_add_on/WXtu.tar.Z
cp /export/wdpf/solaris/required_add_on/WXohi.tar.Z
6. Uncompress and untar the two packages on each drop:
uncompress WXtu.tar.Z
uncompress WXohi.tar.Z
tar xvf WXtu.tar

tar xvf WXohi.tar
7. Remove old ohi and Znyx packages from each drop:
pkgrm WXohi
pkgrm ZNYXnb
OS180_10 61
8. Enter the following in a Terminal window to install the new tu and ohi packages on each drop:
cd /tmp
pkgadd -d . (Follow the prompts to install both the WXohi and WXtu packages.)
9. Copy the oldest .net-physical file over the net-physical file at each drop:
cd /lib/svc/method/
ls -a .net-physical*
cp .net-physical.<Date_Time> net-physical
10. Reboot the drop.
11. Reconfigure the drop for ohi with tu.
a) Access the Init Tool and set the following:
Ovation Network Interface Type: Ovation Highway Interface (ohi0)
b) Access the Admin Tool and set the following:
Topic: Ovation DDB Configuration
In the Ovation DDB Configuration window that appears, set the following:
DDB Interface:Ovation Highway Interface (ohi0)
Enter OHI Interfaces: Primary - tu0(Znyx), Backup - tu1(Znyx)
c) Select the Install Configuration on Software Server function, All filters, and All topics.
d) Select the Download Configuration to Drops function, All filters, and the Software
Server drop number.
12. Setup the drop to run on the OHI driver.
a) Rename the hostname file.
mv /etc/hostname.<network_interface_name>
/etc/hostname.ohi0
b) Enter the following in a Terminal window to verify that DDB is set to ohi0:
grep IFNAME=/etc/rc2.d/S84ddb
The following response should appear:

IFNAME=ohi0
11.1.4 T O UPGRADE DRIVERS FOR COMPUTERS WITH L INKSYS CARDS

1. Insert the 1.8 Third-Party CDROM into the CDROM drive at the Software Server.
2. Enter the following in a Terminal window to copy the new tu and ohi drivers to the Server:
su
cd /export/wdpf/solaris/required_add_on
cp /cdrom/cdrom0/required_add_on/WXtu.tar.Z .
cp /cdrom/cdrom0/required_add_on/WXohi.tar.Z .
3. Enter the following in a Terminal window to delete the old Znyx driver from the Server:
rm ZNYXnb.tar.Z
62 OS180_10
4. Perform Steps 4 - 13 on all drops in the network that use Linksys cards:
a) Enter the following in a Terminal window to setup the drop to run on the onboard driver.
Use the following table to determine the appropriate hostname file extension to use in
the command line.
mv /etc/hostname.ohi0
/etc/hostname.<network_interface_name>
Hostname File Choices
HARDWARE TYPE <NETWORK_INTERF ACE_NAM E>
UltraSPARC 5,10, 60 hme0

Sun Blade 150 eri0
Ultra 25, 45 bge0
b) Enter the following in a Terminal window to manually change the IFNAME=ohi0 entry:
vi /etc/rc2.d/S84ddb
IFNAME=<network_interface_name>
c) Reboot the drop.
5. Copy or ftp two software packages from the Server to /tmp directory on each drop:
su
cd /tmp
cp /export/wdpf/solaris/required_add_on/WXohi.tar.Z
6. Uncompress and untar the package on each drop:
uncompress WXohi.tar.Z
tar xvf WXohi.tar

7. Remove old ohi and Znyx packages from each drop:
pkgrm WXohi
pkgrm ZNYXnb
8. Enter the following in a Terminal window to install the new ohi package on each drop:
cd /tmp
pkgadd -d . (Follow the prompts to install the WXohi package.)
9. Copy the oldest .net-physical file over the net-physical file at each drop:
cd /lib/svc/method/
ls -a .net-physical*
cp .net-physical.<Date_Time> net-physical
11. Access the Admin tool and select the Download Configuration to Drops function, All filters,
and the Software Server drop number.
OS180_10 63
12. Setup the drop to run on the OHI driver:

a) Rename the hostname file.
mv /etc/hostname.<network_interface_name>
/etc/hostname.ohi0
b) Enter the following in a Terminal window to verify that DDB is set to ohi0:
grep IFNAME=/etc/rc2.d/S84ddb
The following response should appear:

IFNAME=ohi0
11.1.5 T O ADD AN U LTRA 25, 45 WORKSTATION TO THE NETWORK USING A S OLARIS 10

(V ERSION 3/05) S ERVER
If you have a Software Server that is loaded with Solaris 10 (version 3/05) and you want to use
that server to add an Ultra 25 or 45 workstation, you need to copy Solaris 10 (version 6/06) to the
cd_image of the Server.
1. Enter the following in a Terminal window at the Server to delete the Solaris 10 (version 3/05)
image:
su
cd /export/wdpf/solaris/
rm -rf cd_image
2. Recreate the cd_image directory:
mkdir cd_image
3. Insert the Solaris 10 (version 6/06) DVD or CDROM disk 1 into the DVD drive.
4. Enter the following to access the Admin Tool:
/bin/csh
source ~wdpf/.cshrc
./configure &
5. From the Admin Tool, install the Solaris 10 (version 6/06) image on the Server:
Function: Install Configuration on Software Server
Filters: All
Topics: All
Note: If you are installing Solaris 10 from the Solaris DVD, skip to Step 7 after the installation is
complete.
6. If you are installing Solaris 10 from the Solaris CDROMs, follow the instructions in "To
Configure Ovation Release Software," Step 2 (see page 31)1 for copying the CD image to the
Server.
7. Refer to the procedure in "To Install Software on Fast Ethernet System Drops" (see page 39)
for complete instructions on loading the new workstation.
64 OS180_10
11.1.6 T O UPGRADE A S OFTWARE S ERVER FROM 1.7 TO 1.8 (S TANDALONE S ECURITY

S ERVER ON A MULTIPLE NETWORK )
1. Create a standalone Ovation Security Server (see page 11).
2. Go to the Software Server and insert the Ovation 1.8 Release CDROM into the CDROM
drive.
CDROM.
4. Use the Software Maintenance Tool to select and install the Ovation software packages onto
the Software Server.
n) Select Exit.
6. As root, type the following in the Terminal window:
/usr/lib/netsvc/yp/ypstop
rm /wdpf/rel/data/load_kit/data/.domainname
7. Configure and start the Software Server
cd /wdpf/rel/ssw/load_kit/bin
./configure
OS180_10 65

InitTool.


Enter “3” for the Ovation Software Server.
message appears:

Ovation.domain.com. If this is a multiple network, make sure all networks have the same
Domain name.
10. Access the Init Tool. From the Function dropdown menu, select Define Domain.
11. The Define NIS Domain Information window appears:
a) Enter the Domain Name, the Security Server Host Name, and the Security Server IP
Address. (This is the name and IP Address of the Software Server.)
b) Select Apply.
12. Access the Admin Tool:
a) From the Function drop-down menu, select Install Configuration on Software Server.
b) Select the applicable filters and topics.
c) Select the Install button. This places the software changes on the Software Server.
13. Before you install the 1.8 Ovation software on each Solaris drop, do the following at each
drop:
a) Login as root.
b) If the /admin directory does not exist, create the admin directory:
mkdir /admin
66 OS180_10
c) Remove the OppList and localmem.dat files:

rm /usr/wdpf/dpu/data/OppList
rm /usr/wdpf/dpu/data/localmem.dat
a) From the Function drop-down menu, select Download Configuration to Drops.
b) Select the applicable filters and drops.
c) Select the Download button. This places the software changes on the designated drops.
d) Select the Bootstrap Drops button. This restarts the software on the drops.
11.1.7 T O UPGRADE A S OFTWARE S ERVER FROM 1.7 TO 1.8 (C OMBINATION S OFTWARE

S ERVER /S ECURITY S ERVER ON A SINGLE NETWORK )
There is now an Ovation Security Server (OSS) drop type for the 1.8 release. The Software
Server on a single network system acts as the Ovation Security Server.
Use the following procedure to upgrade a 1.7 Software Server to a combination 1.8 Software
Server/Security Server.
1. Go to the Software Server and Insert the Ovation 1.8 Release CDROM into the CDROM
drive.
CDROM.
3. Use the Software Maintenance Tool to select and install the Ovation software packages onto
n) Select Exit.
OS180_10 67
5. As root, type the following in the Terminal window:

/usr/lib/netsvc/yp/ypstop
rm /wdpf/rel/data/load_kit/data/.domainname
6. Configure and start the Software Server:
cd /wdpf/rel/ssw/load_kit/bin
./configure
7. The Ovation Domain Setup Procedure window displays in a Terminal window. Note the
following message that appears:

InitTool.


8. Respond to the message in Step 7 by entering “2” for the Ovation Software Server.

Ovation.domain.com.

password
New Password:
Re-enter New Password:

A message prompts you to Hit Return to continue.
10. Access the Init Tool. From the Function dropdown menu, select Define Domain.
11. The Define NIS Domain Information window appears:
a) Enter the Domain Name, the Security Server Host Name, and the Security Server IP
Address. (This is the name and IP Address of the Software Server.)
b) Select Apply.
68 OS180_10
12. Return to the Init window:

a) Select your current Software Server drop from the Drop Configuration list.
b) From the Function dropdown menu, select the Modify/Add/Delete Drop Type selection.
13. The Modify/Add/Delete Drop Types window appears.
a) Select Ovation Security Server from the Available Packages list and add it to the current
drop type.
b) Select the Save to Disk button to save your configuration to disk.
14. Return to the Init window:
a) Select the Save Configuration to Disk button.
16. Before you download the 1.8 Ovation software on each Solaris drop, do the following at each
drop:
a) Login as root.
b) If the /admin directory does not exist, create the admin directory:
mkdir /admin
c) Use the following command to re-enter the admin password:
passwd admin
d) Remove the OppList and localmem.dat files:
rm /usr/wdpf/dpu/data/OppList
rm /usr/wdpf/dpu/data/localmem.dat
When the upgrade to the Ovation 1.8 software is complete, you must update your Security
Builder with all the current user and security information.
18. Login as admin at the Software Server.
19. Access the User Login/Menu and select the following options to access the Security Builder:
Tools
Command Line Access
Cmdtool...
A Terminal window appears. Enter the following at the command line prompt:
cd /wdpf/rel/ssw/db/bin
./security_manager
20. When the Security Builder appears, select Merge Configuration from the File menu. The
Merge Configuration window appears.
OS180_10 69
21. Navigate to the /wdpf/rel/config/db/config directory and select the initial_security.xml file.
Select Merge. This imports your existing users and security data.
22. Select the Networks tab.
a) Enter the Network Alias and IP Address of your Software Server.
b) Select the Configure Network button.
23. Select the Users tab and perform the following for each user:
a) Enter a password for each user and verify that the correct role is selected for each user.
b) Select the Configure User button.
24. Engineering Functions are new to Ovation 1.8 and are maintained by the Security Builder.
Select the Roles tab and update the default Engineering Functions. Select the Configure
Role button.
25. The Security Builder maintains the menu files for each Engineering role. If desired, you can
modify these menus through the Edit button on the Roles tab.
26. After all the desired edits are completed, you must send the updated security data to each
network's database. Select the Save Configuration option from the File menu.
27. Use the Admin Tool to download the changes to each workstation.
70 OS180_10
S E C T I O N 12
BACKING UP THE SYSTEM
IN THIS SECTION
What is a system backup? ................................................................................................ 71

Using OCBT to backup the system................................................................................... 71
Using command lines to backup the system..................................................................... 79
12.1 W H A T IS A SYSTEM BACKUP?
A system backup consists of saving all the important system data so that a system could be
restored in case of a system malfunction where data is lost.
Ovation systems should be backed up at the following times:

After a system has been loaded and configured. This prevents any loss of important data, in
case there is a hardware or software failure in the system that causes a disk crash.
Periodically, to ensure that system changes are not lost in case there is a system malfunction
and data is lost.
Before a System Upgrade occurs.
There are different methods available for backing up system data:
Using the Ovation Configuration Backup Tool (OCBT).
Using command lines.
Using a Third-Party Backup Tool (refer to the documentation provided by the third-party
vendor for instructions on reloading the system).
Note: The Software Maintenance Tool can be used to identify any project specific files that
should be backed up.
12.2 U S I N G OCBT TO BACKUP THE SYSTEM
The Ovation Configuration Backup Tool (OCBT) is a Graphical User Interface (GUI) that can be
used to safely save the system application data. The information in the backup can then be
restored after a data loss or a hard disk failure.
OCBT offers several configuration options depending on your available hardware and time
schedule for backups. The tool creates UNIX tar files which can be compressed or uncompressed
depending on your system configuration.
12.2.1 T O USE OCBT

1. Access the Admin Tool window from the Engineer Station.
2. Select Maintain Project Data from the Function pull-down menu.
OS180_10 71
12.2 Using OCBT to backup the system
3. Select the Backup Tool button. The OCBT main window appears. The fields are described in
the Backup Tool Window table (see page 75).
Figure 1: OCBT Main Window
4. Choose an Output Media (file, tape, or floppy).

5. Select a Frequency for the backup (Onetime, Daily, or Weekly).
6. Select the files to backup from the list of Ovation System Data files and Ovation System
Config files.
7. Select an Output Type (Compress or Uncompressed).
72 OS180_10
8. Press the Save button if any changes were made to the window. If the Save button is not
pressed, the following window displays.
Figure 2: Backup Tool Warning Window
If Yes is selected, the changes are saved and you may continue. If No is selected, the values
are reverted back to their last-saved state. This function is in place so the tool can keep track
of the configuration even if you exit the tool and restart it again.
9. If the default settings in the Backup window are satisfactory, skip to Step 10.
OR
If you want to view or change the default settings, use the Setup window (see page 78).
10. Press the Start button. OCBT then performs the following actions:
Checks the configuration for changes, and prompts you to save the changes if any are
found.
Runs the time calculations to determine the time of the backup.
Carries out the Backup Function.
Checks that the proper configuration is defined on the main and Setup windows (devices,
directories, and so forth). This is to avoid errors by running the tool with an improper
configuration. If inconsistencies are found, an error window displays and prompts you to
press OK before beginning the Start function. The Error window displays the parameter
that is wrong. Correct the situation, and press the Start button again.
Figure 3: Consistency Check Error Window
OS180_10 73
If no errors are found, the Backup Tool Start Procedure window displays. This window
serves as a user interface to verify the actions the backup tool is performing. After
completion, it saves this data as a log file (backup.log) for reference. The log file name is
configurable in the Setup window.
Figure 4: Backup Tool Start Procedure Window
11. The following buttons are available (if needed) on the Start window:
Reset — resets the start function to the beginning of the procedure.
Cancel — cancels the backup process. Note that this may take a few minutes since the
file that is being backed up when the Cancel button was pressed will finish processing.
Update — updates the Time Remaining fields.
Time Remaining — shows the hours and minutes remaining until the next backup.
12. If you have selected a Backup Frequency of Onetime, once the backup is complete, exit the
main Backup Tool window by pressing the Dismiss button.
If you have selected a Backup Frequency of Daily or Weekly, do NOT use the Dismiss button
to exit the tool. Instead, close the tool to an icon so it remains running and the Backups are
performed at the scheduled times.
74 OS180_10
12.2.2 OCBT CONFIGURATION TABLE
Ovation Configuration Backup Tool Window Fields
FIELD DESCRIPTION
Output Media Determines the type of media to use to store the data.
File Default Media. Output files are stored in the directory specified in the Backup
Tool Setup window. The file specified in this window becomes the log file of
the backup and contain a list of all the backup transactions. Even if tape or
floppy is selected as the output media, a default file is still specified in the
system (backup.log) since the OCBT first writes data to a file and then
sends it to the tape or floppy device.
Tape Saves disk space by sending the backup data to an external tape drive. The
tool first writes the data to a file (in tar format), and then sends it to the tape
and erase the file afterwards. This is to allow you to save disk space while
creating the backup. Note that if “File” is selected as the Output Media and a
backup is performed, you may still send the file to a tape using the Copy
button on the main Backup Tool window. In this way, another backup does not
have to be run.
Enter a device filename in the Setup window to handle the I/O for the
particular tape drive (for example, /dev/rst4 or /dev/rmt/0).
CAUTION! If you do not enter the non-rewinding device (nrst4 or

rmt/0n), the finished tape will only contain the last backup option
selected.
Floppy Similar to the tape option, but has less space to store files. When using a
floppy, OCBT displays any errors related to a disk full condition. However, the
tool performs no calculations before sending the files to the floppy. You must
be aware of the size of the compressed or uncompressed files before sending
them to the device. If you select Floppy as the output media, the Backup Tool
Setup window expects the "Enter a device file name" in the Setup window that
handles the I/O to that particular floppy drive (typically, /dev/rfd0a).
Frequency Determines the intervals at which the backups are performed.
Onetime Creates immediate backups without waiting for a scheduling program. Select
Onetime and then Start. The Backup Tool Start Procedure window appears
and the backup proceeds as instructed. You can cancel the backup at
anytime.
Daily Runs a backup on a daily basis. The time is defined in the Setup window. The
valid options are 00-24 for hours: 00-50 for minutes (note that minutes are
selected in increments of ten).
The default value for hours and minutes is 00:00.
When you press the Start button on the main Backup tool window, the tool
calculates whether or not that time has already passed for the day. If the
answer is YES, then it schedules the backup for tomorrow at the same time. If
the answer is NO, then it schedules the backup for today at the time specified.
After the backup is performed, you can either press the Reset button (on the
Startup window), or the tool resets itself ten minutes after the backup is
completed. The Reset function automatically reschedules a new backup for
the next day at the same time. The Startup window also contains an Update
function which displays the hours and minutes remaining before the next
backup starts.
OS180_10 75
FIELD DESCRIPTION
Weekly Functions similarly to the Daily option, but on a weekly basis. This is normally
used when the system has a solid configuration and only occasionally
undergoes minor changes. When the Weekly frequency is selected, you must
also select the day of the week and the time when the backup is performed.
The default day is Friday.
Ovation Lists the Ovation System data files that can be saved.
System Data
Files When the directory name starts with rel, OCBT appends the
/export/wdpf path to it. This is done to perform relative backups instead
of absolute backups (an absolute backup is when the backup is taken from
the exact directory entered). Relative backups can be extracted with ease and
can be installed on any other system without overriding existing data. When
the backup starts, OCBT changes the current directory to /export/wdpf
and performs the backup from there using the directories and files specified.
If the directory path does not start with rel, then the backup is absolute.
You can change the default directories through the Setup window.
Custom Filename: dgraph.tar
Graphics
Default Directory: rel/data/mmi/diag
Control Filename: dcb.tar
Drawings
Default Directory: rel/data/cbdata
HSR Pic Files Filename: dhsr.tar
Default Directory: rel/data/hsr
Log Reports Filename: dlog.tar
Default Directory: rel/data/ls
MMI Data Filename: dmmi.tar
Files
Default Directory: rel/data/mmi/config
Oracle Filename: dora.tar
Database
Default Directory: rel/data/db
OCBT tries to export the Oracle database and then performs the backup.
If the Software Server drop holds the Oracle database, no extra steps are
needed.
If a separate drop is used to hold the database, insert dropxxx: before
the directory name (where “xxx” is the drop number that holds the database).
The directory path may use the relative or absolute path following the drop
number string.
Other Files Filename: doth1.tar, doth2.tar
Default Directory: None
76 OS180_10
FIELD DESCRIPTION
Ovation Lists the Ovation System configuration files that can be saved.
System
Config Files When the directory name starts with rel, OCBT appends the
/export/wdpf path to it. This is done to perform relative backups instead
of absolute backups (an absolute backup is when the backup is taken from
the exact directory entered). Relative backups can be extracted with ease and
can be installed on any other system without overriding existing data. When
the backup starts, OCBT changes the current directory to /export/wdpf
and performs the backup from there using the directories and files specified.
If the directory path does not start with rel, then the backup is absolute.
You can change the default directories through the Setup window.
HSR Filename: chsr.tar
Configuration
Default Directory: rel/config/hsr
Log Server Filename: clog.tar
Default Directory: rel/config/ls
MMI Filename: cmmi.tar
Configuration
Default Directory: rel/config/mmi
Data Link Filename: clink.tar
Files
Simulation Filename: csim.tar
Files
Perf Calc Filename: ccalc.tar
Files
Output Type Allows you to select between compressed and uncompressed backup files.
Default value is compressed.
Save button Saves current configuration on the window. Note that this does not start the
backup process.
Setup button Displays the Backup Tool Setup window that allows you to modify the default
window settings.
Start button Begins the backup process.
Copy button Copies the existing backup files to tape (used if File is selected as the Output
Media so another backup does not have to be run).
Dismiss Exits the backup tool. If any changes were made to the window, a notice
button window appears asking you if the changes should be saved.
OS180_10 77
12.2.3 T O USE THE S ETUP WINDOW
You can use the Backup Tool Setup window to change the default directories, times, and media
devices for the options in the main Backup Tool window.
1. Access the Setup window by selecting the Setup button on the main Backup Tool window.
The Setup window appears.
Figure 5: Backup Tool Setup Window
2. Based on the Output Media selected on the Backup window, enter a new filename or a media
device name.
Note: The log filename is mandatory. The directory where this file is located is where the
backup tar files will be stored (default = /usr/user4/backup.log)
3. Based on the Frequency selected on the Backup window, use the pull-down menus to select
a time and, if applicable, a day of the week to run the backup.
78 OS180_10
12.3 Using command lines to backup the system
4. Based on the files selected on the Backup window, enter the appropriate directories to point
to the files. Only those files selected on the main Backup window are active (not grayed out).
See the Ovation Configuration Backup Tool Window table (see page 75) for a list of default
directories.
5. When all of the information has been entered, select one of the following buttons:
Save — Saves the changes to the Setup window. This save function also ensures that
your entries for directories and/or devices are valid.
Set Default — Resets the main Backup Tool window to use the default values.
Dismiss — Exits the Setup window and takes you back to the main Backup Tool window.
12.3 U S I N G COMMAND LINES TO BACKUP THE SYSTEM
You can also use command lines to backup the Ovation system. Enter the command lines in a
Terminal window.
12.3.1 T O BACKUP THE O VATION S ECURITY S ERVER

1. Insert a blank tape into the tape drive at the Ovation Security Server.
2. Open a Terminal window.
3. Enter the following at the command prompt:
su
cd /export/wdpf
tar cvf /dev/rst4 ./sccs ./rel/data/oss/data
./rel/data/yp/Ovation ./rel/users
(or the appropriate tape device name)
12.3.2 T O BACKUP THE S OFTWARE S ERVER

1. Enter the following in a Terminal window:
su
cd /etc/wdpf_config
./backup_disk
A script appears and prompts for the tape device to be used and what directories should be
backed up (directory sizes, in megabytes, are displayed). The directory choices are listed as
follows:
Workstation released software (ssw) and project data (data)
Solaris patches (patches)
SCCS Directory (sccs)
2. Determine how many tapes will be needed to backup the directories listed and label the tapes
accordingly (for some systems, all the directories will fit on one tape):
Example:
Project Name - Drop xxx (xxx = number)
Backup #1 of Software Server (Backup #2, etc.)
Date
3. Insert a tape into the tape drive and select (from the messages and prompts) the directories
that will fit on one tape.
OS180_10 79
4. Select the defaults that are listed by entering a carriage return after each prompt. This selects
/dev/rst4 as the tape device and proceeds to backup the selected directories.
Note: If the tape drive is not set to SCSI address 4, enter the correct device name for the tape
drive.
5. Repeat Steps 1 through 4 until all the directories are backed up.
su
cd /etc/wdpf_config
tar cvf /dev/rst4 *
7. If there is a file in this directory named <project #>.config that contains the disk
partitioning information for the Software Server, print out this file to use as a reference during
a reload of the Software Server. Keep this printout with the tapes that were created in Steps 1
through 5.
OR
If the file <project #>.config does not exist, perform the following:
a) Enter the following in a Terminal window:
su
format
b) Specify the disk by entering the disk number.
c) Select the Partition Menu by entering the following:
partition
d) Display the current partition table by entering the following:
print
e) Note the partition, tag name, and size of each partition for use in the event of a system
reload.
f) Repeat Steps a) through e) for each disk in the Software Server.
80 OS180_10
12.3.3 T O BACKUP A COMPLETE DATABASE ( USING O RACLE E XPORT PROGRAM EXP )
There are two programs available for backing up the PowerTools database (exp and ptdbexp). It
is recommended that you use both tools to backup the database so you will have two types of
database backups. Then you can select the best type for the restoration you need to perform.
The tool exp saves the entire database, all of the structure, and all of the content; alternately, it
can also be used to save selected portions. Existing point SIDs and network addressing
assignments are retained. Following a restoration, the state of the database (structure and
contents) is exactly what it was when the export was taken.
Use exp to back up the database so that it can be completely restored in case there is a system
disruption such as disk crash or operating system reload.
This type of backup is generally not portable from one Ovation job to the next. It should not be
used to copy a database between a Master Database and an External Database. Additionally,
special steps must be taken if a database restoration is performed during an Ovation software
upgrade.
1. Log in as user ptadmin at the workstation that is being used as the Power Tools server
(you can also remotely log in by using the rlogin command):
su - ptadmin
(the default password for the ptadmin UNIX user is wdpf)
2. Insert a blank tape into the tape drive.
Note: The tape size needed depends upon the size of your database. Approximately 2 kilobytes
per point are used (500 bytes when compressed).
3. Export the contents of the Oracle database with the following command:
exp USERID=system/manager FILE=<exportfile> FULL=Y
COMPRESS=N LOG=<logfile>
where
<exportfile> = user-defined filename for the backup file
<logfile> = user-defined output log file of the screen output
This creates a file named <exportfile>.
4. Compress the file with the following command:
compress <exportfile>
This creates a compressed file named <exportfile.Z>.
5. Tar the compressed <exportfile.Z> to a tape.
tar cvf /dev/rst4 ./<exportfile.Z>
(The device name may differ depending upon SCSI address and tape density.)
6. Remove the tape from the tape drive and label it appropriately.
7. After saving the backup file to a tape, remove the file from the system to conserve space.
rm <exportfile.Z>
OS180_10 81
12.3.4 T O BACKUP THE O VATION H ISTORIAN (HSR)
This procedure backs up the files necessary to locate historical files on the secondary disk(s), and
all optical disks. These steps are not intended to backup the data contained on the secondary
disk(s), since the historical data is written to optical disk.
1. Make sure that all the data is backed up to an optical disk:

a) Restart the HSR from the HSR Status & Control User Interface.
b) Wait until all the data is backed up to an optical disk. To verify that this has been done,
bring up the System Time Ranges UI and verify that the end times for the HSR
subsystems on the secondary storage match the end times for the subsystems on the
tertiary storage.
2. Backup the contents of the following directories to tape for each HSR drop:
/usr/wdpf/hsr/archive/db (volume database information for all
HSRs)
/usr/wdpf/hsr/archive/recovery (redundant HSRs only)
Note: If the tape drive is located on another machine, ftp the directory specified in Step 2 to the
drop with the tape drive.
3. If an optical drive which requires a license is configured for your system, make note of the
license key. You would need to use this key in case you would need to reload the driver for
your optical drive.
12.3.5 T O BACKUP A PARTIAL DATABASE ( USING P OWER T OOLS E XPORT PROGRAM

PTDBEXP )
There are two programs available for backing up the PowerTools database (exp and ptdbexp). It
is recommended that you use both tools to backup the database so you have two types of
database backups. Then you can select the best type for the restoration you need to perform.
The tool ptdbexp saves all of the database configuration and point information into an ASCII file.
None of the database structure is saved. Following a restoration, point SIDs and network
addressing assignments will be changed.
This tool is recommended when an Ovation software upgrade of the PowerTools server requires
a complete reload of that drop.
If the Software Server and PowerTools Server are separate drops, the PowerTools Server can be
upgraded without reloading the drop. If necessary, the database schema is changed during a
query/download of the upgraded software and no restore operations are needed.
However, if for any reason the PowerTools Server is completely reloaded, it is recommended that
the database be populated with the PowerTools export file and that applicable Control Builder
scripts be executed (to load control sheet information into the database).
1. Log in as user wdpf at the workstation that is being used as the Power Tools server (you
can also remotely log in by using the rlogin command):
su - wdpf
(the default password is wdpf)
82 OS180_10
2. Insert a blank tape into the tape drive.
Note: The tape size needed will depend upon the size of your database. Approximately 3
kilobytes per point are used (600 bytes when compressed).
3. Run the ptdbexp program:

/usr/wdpf/db/bin/ptdbexp ptadmin <exportfile>
(where <exportfile> is the user-defined filename for the backup file)
This creates a file named <exportfile>.
4. Compress the file with the following command:
compress <exportfile>
This creates a compressed file named <exportfile.Z>.
5. Tar the compressed <exportfile.Z> to a tape.
tar cvf /dev/rst4 ./<exportfile.Z>
rm <exportfile.Z>
12.3.6 T O BACKUP THE C ONTROL B UILDER (CB) DRAWINGS
Use this procedure to backup the Control Builder drawings:
1. Insert a blank tape into the tape drive at the Ovation Engineering Station.
2. Use the Login Menu system to open a Command Tool:
Access the applicable User Login menu and login according to your role:
Select Tools
Select Command Line Access
Select Cmdtool
3. Type the following at the command prompt to copy the Control Builder drawings to a tape:
(This produces the following file that should be saved
/wdpf/rel/data/cbdata/import_sheet_order.sql)
source ~ptadmin/.cshrc
cd /wdpf/rel/data/cbdata
sqlplus ptadmin/ptadmin@ptdb
@/usr/wdpf/cb/bin/export_sheet_order.sql
cd /wdpf/rel/data
tar cvf cbdata.tar cbdata
compress cbdata.tar
tar cvf /dev/rst4 cbdata.tar.Z
rm cbdata.tar.Z
12.3.7 B ACKING UP PRINTER INFORMATION

1. Use the Solaris admintool to identify any print spoolers defined for the device.
OS180_10 83
2. Record the configuration information for each spooler device. Either record or print a
screencopy of the Solaris admintool window associated with each spooler.
3. For Ethernet printers, record the IP address and hostname(s) of the printer from the
/etc/hosts file of the printer “host” drop.
12.3.8 B ACKING UP THE D ATA L INK FILES

1. Save the Data Link binaries, configuration files, and initialization files from the following
directories:
/usr/wdpf/dl/bin
/usr/wdpf/dl/config
/usr/wdpf/dl/init
cd /usr/wdpf/dl
tar cvf /dev/rst4 ./bin ./config ./init
12.3.9 B ACKING UP T HIRD -P ARTY SOFTWARE LICENSING INFORMATION
You must reload third-party software and drivers when you reload Solaris 10. Make a note of any
licensing information and activation strings for third-party software which you need to enter during
reloading.
84 OS180_10
S E C T I O N 13
RESTORING THE OVATION SYSTEM
IN THIS SECTION
Ovation restoration overview............................................................................................. 85

To restore the Ovation Security Server............................................................................. 85
To restore the Software Server ......................................................................................... 86
To restore all drops (except the Software Server) ............................................................ 87
Restoring the Ovation Historian (HSR) ............................................................................. 88
Restoring the Power Tools database files ........................................................................ 89
Restoring the Control Builder drawings ............................................................................ 92
13.1 O V A T I O N RESTORATION OVERVIEW
Occasionally, Ovation workstation systems must be reloaded due to system malfunctions. The
backup tapes are used to accomplish a successful reload.
After a system malfunction (such as a disk crash), the following must be done at the drop where
the crash occurred:
Install Solaris 10
Install Ovation
Install Oracle
Install the Data backup tapes
Use the Admin Tool to install the configuration on the Software Server and then download it to
the appropriate drops.
This section provides reload procedures for the Ovation systems.
Note: The purpose of these procedures are to restore a system to its known, previously backed-
up state. These procedures are typically NOT Upgrades (the exception to this is the procedure
for reloading a partial Power Tools database during a system upgrade).
13.2 T O RESTORE THE OVATION SECURITY SERVER

1. Install the Solaris 10 Operating System.
2. Install the Ovation Security Server software. Ensure that you name your domain exactly as it
was named in the system that you backed up (see page 79).
3. Load the backup tapes for the Security Server (these tapes were created in the Backup
procedure).
4. Insert the tape(s) of the Security server into the tape drive.
OS180_10 85
13.3 To restore the Software Server
5. Enter the following in a terminal window:

su
cd /export/wdpf
tar xvf /dev/rst4 (or the appropriate tape device name)
6. You must now use the Admin Tool on each network defined in your domain to rebuild the NIS
Server Configuration.
a) Access the Admin Tool
b) From the Function menu, select the Install Configuration on Software Server.
c) Select the Base Software filter.
d) Select the Base NIS Server Configuration topic.
e) Select the Install button.
7. Access the Security Builder on the Security Server drop.
8. Select the Users tab. Select any user and make a modification of some type. This alerts the
system that a change has been made and data must be distributed.
9. Select the Configure User button at the bottom of the screen. The changes are applied to the
user account.
10. Select File -> Save to save the changes to the database. This action rebuilds the entire user
database and redistributes the data to every drop defined in your domain.
13.3 T O RESTORE THE SOFTWARE SERVER

1. Install the Solaris 10 Operating System.
2. Partition the disk(s) EXACTLY as they were originally partitioned, rather than following the
instructions in this manual.
If available, use the printout (see page 79) of the Software Server <project #>.config
file in order to determine the original disk partitions. (This printout was created in the Backup
procedure.)
If the printout of <project #>.config is not available, use the information specified in the
“format” command (see page 79) during backup to determine the original disk partitions.
The “filesys” commands in this file describe the original partitioning of the hard disk(s). For
example, the command:
filesys c0t3d0s7 512 /export/wdpf
where:
c0 = SCSI device being used is 0
t3 = Target ID is 3
s7 = (partition) slice is 7
256 = partition size
/export/wdpf = partition name
means that the /export/wdpf partition resides on the c0t3d0 hard drive as (partition)
slice 7 with a 512 Mbytes size length assigned. If the size length assigned is listed as
“free,” this means that ALL remaining unassigned space on the hard disk should be
assigned to that (partition) slice.
3. Load the Ovation software.
86 OS180_10
13.4 To restore all drops (except the Software Server)
4. Load the Backup tapes for the Software Server (these tapes were created in the Backup
procedure.)
5. Insert the tape(s) of the Software Server into the tape drive.
su
cd /export/wdpf
tar xvf /dev/rst4 (or the appropriate tape device name)
Repeat the tar command for each additional tape.
7. Insert the backup tape containing the /etc/wdpf_config directory into the
tape drive.
mkdir /etc/wdpf_config
cd /etc/wdpf_config
tar xvf /dev/rst4
9. Copy the S91 _patch from the /etc/wdpf _config directory to the
/etc/rc3.d directory and reboot the Software Server by entering
the following in a Terminal window:
cd /etc/wdpf_config
cp S91_patch /etc/rc3.d
reboot
The machine reboots, the Solaris Patches and Ovation workstation software is installed,
and the machine is configured as a Software Server.
10. Access the Admin Tool. Perform the following to recreate the system configuration files:
a) Select the Install Configuration on Software Server function.
b) Select All filters and All topics.
c) Select the Install button.
Note: The configuration files are rebuilt to the configuration state that existed when they were
backed up.
d) Select the Download Configuration to Drops function.

e) Select the appropriate target drop number(s) to be downloaded. Be certain to include
f) Select the Download button.
13.4 T O RESTORE ALL DROPS (EXCEPT THE SOFTWARE SERVER)

The Software Server loads the drop (see page 39) with Solaris, Solaris patches, and Ovation
software.
1. Install the Solaris 10 Operating System, the Solaris patches, and the Ovation release
software.
OS180_10 87
13.5 Restoring the Ovation Historian (HSR)
2. Use the appropriate backup tape or printout to install any or all of the following additional
application software:
HSR volume database
/usr/wdpf/hsr/archive/db tape
Data Link files
/usr/wdpf/dl tape
Solaris Print spooler information is provided by the backup printout.
Third-Party Software licensing information.
Reload the Power Tools Database files.
13.5 R E S T O R I N G THE O VA T I O N H I S T O R I A N (HSR)

Since the Ovation HSR does not have a time update, it is important not to let the HSR start up
automatically, and perhaps lose data. This can be done by renaming the statmgrsuper file and
thereby preventing the HSR start-up file from locating it and starting up. Ensure that the HSRs will
not start up on their own before the data is reloaded.
13.5.1 T O RESTORE THE O VATION H ISTORIAN (HSR) DROP

1. On the Software Server, move (rename) the statmgrsuper binary file to
statmgrsuper.orig by typing the following (use one line to enter the following):
mv /wdpf/rel/ssw/hsr/stat_mgr/bin/statmgrsuper
/wdpf/rel/ssw/hsr/stat_mgr/bin/statmgrsuper.orig
(when this file is downloaded to /usr/wdpf/hsr/stat_mgr/bin/statmgrsuper.orig
on the HSRs, it will not start since the start-up file will be looking for the name statmgrsuper
not statmgrsuper.orig)
2. Type one of the following commands to reload the HSR drop:
Commands for Reloading HSR
WORKSTATION TYPE SYSTEM TYPE COMM AND
UltraSPARC 5, 10, 60 Fast Ethernet boot net - install

Sun Blade Fast Ethernet boot net - install
SPARC 5, 10, 20 FDDI boot /iommu/sbus/nf -
UltraSPARC 1, 2 install
Ultra SPARC 5, 10, 60 FDDI boot /sbus/nf - install
3. Make sure the optical driver for the HP Optical Disk has been defined, installed on the
Software Server, and downloaded to the appropriate drops (See Ovation Init and Admin Tool
User Guide.)
4. On each HSR drop, reload the directories that were saved to backup tape:
/usr/wdpf/hsr/archive/db (volume database information for all HSRs)
/usr/wdpf/hsr/archive/recovery (redundant HSRs only)
5. Make sure that the secondary partitions are configured correctly in the
/etc/vfstab file on each HSR
88 OS180_10
13.6 Restoring the Power Tools database files
6. Then on the Software Server, move (rename) the statmgrsuper.orig binary file back to
statmgrsuper by typing the following (use one line to enter the following):
mv /wdpf/rel/ssw/hsr/stat_mgr/bin/statmgrsuper.orig
/wdpf/rel/ssw/hsr/stat_mgr/bin/statmgrsuper
7. Download the statmgrsuper file to the HSRs.
8. On each HSR, reload the Optical drivers, if necessary. If conversions of optical disks are
required, contact Emerson service personnel before proceeding.
9. Now you can start up the HSR from the HSR Status/Control User Interface without losing any
data.
13.6 R E S T O R I N G THE POWER TOOLS DATABASE FILES
Reload the backed up database files after the following has been done at the drop that is being
reloaded:
Solaris Operating System has been installed.
Ovation software has been installed.
Oracle has been installed.
Reload the Power Tools databases using one of the following methods:
Reload the complete database (see page 90) using Oracle import.
Reload the partial database (see page 91) using PowerTools import.
Each of these restorations has advantages and disadvantages and it is up to the user performing
the reload to determine which method is appropriate for each individual situation.
13.6.1 R ESTORING A COMPLETE DATABASE
The Power Tools Server is the drop where the Oracle database is located. This drop may also be
the Software Server. If the workstation being loaded is also a Software Server, reload the
Software Server functions first.
This type of database reload utilizes an Oracle export file which has been previously created. This
method restores the entire database (for example, points, control sheet information, project
configurations, Ovation reference information, and the actual internal structure of the Ovation
PowerTools database) to whatever is contained in the Oracle export file.
The primary reason for using this type of database reload is to recover from a system failure (for
example, following the loss of a system hard disk). Due to the data content in the Oracle export
file, this method is generally NOT portable from one Ovation system to another or when used in
the context of a software upgrade (see page 59).
There is no network DDB deadspace recovery and no improvement in the time required for a
cleared Operator Station to become fully functional (that is, the time during which the station is
“waiting for the database to redistribute”). Additional (and very necessary) steps are required
following the Oracle import to ensure that the internal database structure (that is, schema
revision) and the Ovation reference information is compatible and consistent with the currently
installed Ovation software release whenever this type of reload is performed in the context of a
software upgrade.
OS180_10 89
13.6.2 A DVANTAGES OF RESTORING A COMPLETE DATABASE
Restoring a complete database provides the following advantages:

Network information (that is, Ovation Dynamic Data Block (DDB) assignments) and System
IDs (SIDS) remain the same following reload. Custom Graphics do not need to be recompiled.
Since the Oracle backup contains Control Sheet data tables, no extra Control Builder script
processing needs to be performed to specifically re-add control information to the database.
Note that if this reload is being performed in the context of a software upgrade, there may be
Control Builder Maintenance scripts which may still need to be performed based on the level
of the previous Ovation System Release level. Refer to the applicable Control Builder
upgrade notes for more information.
This is the quickest method to return to full database functionality when dealing with the same
Ovation System at the same Ovation Software Release level.
13.6.3 D ISADVANTAGES OF RESTORING A COMPLETE DATABASE
Restoring a complete database provides the following disadvantages:

Since network information will remain the same, there will be no “repacking” of Ovation
Network DDBs. For example, if the system utilized 500 DDBs for normal Ovation process
points with 50% deadspace prior to the upgrade, the system will have the same network
characteristics after the upgrade. (Note that DDB deadspace occurs during system
engineering changes whenever an Ovation process point is moved between drops or has its
frequency changed.)
Since all Oracle PowerTools tables are restored, this will include the tables associated with
the database distribution to the Ovation Operator Stations. The maximum distributed
database sequence number will remain the same following the upgrade. (Note that a cleared
Ovation Operator or Engineering Station will need to process all distributed database change
messages from the Ovation PowerTools Server before its Operator Station software is fully
functional.)
The internal structure of the Oracle database is equivalent to what it was at the time the
Oracle export was performed. This ties the export file to the Ovation software level which was
in place at the time the export was performed.
The reference information (for example, a list of supported I/O modules) is equivalent to what
it was at the time the Oracle export was performed. This ties the export file to the Ovation
software level which was in place at the time the export was performed.
13.6.4 T O RESTORE A COMPLETE DATABASE
Use the following procedure to reload the Power Tools complete database (including structure)
from a backup tape.
1. Log in as user ptadmin at the workstation that is being used as the Power Tools server
(you can also remotely log in by using the rlogin command:
su - ptadmin
(the default password for the ptadmin UNIX user is wdpf)
2. Insert the Power Tools database backup tape into the tape drive.
90 OS180_10
3. Untar the saved <exportfile.Z> from the tape.

cd <appropriate_directory>
tar xvf /dev/rst4
(where <appropriate_directory> is a directory large enough to hold the file)
4. Uncompress the backup file with the following command:
uncompress <exportfile.Z>
5. Enter the following command to restore the backup:
/usr/ptadmin/do_full_import <exportfile>
6. Remove the backup file from the system to conserve space.
7. Reboot the Power Tools server drop.
13.6.5 R ESTORING A PARTIAL DATABASE
The Power Tools Server is the drop where the Oracle database is located. This may also be the
Software Server. If the workstation being loaded is also a Software Server, reload the Software
Server functions first.
This type of database reload utilizes a PowerTools (text-based) import file which has been
previously created.
Since the PowerTools export file contains only table configurations and Ovation process points,
additional operations are required to restore complete functionality to the Ovation system.
Specifically, control information must be restored using the Ovation Control Builder.
The PowerTools export file does not contain the Ovation network (DDB) or System ID
assignments for the process points or the internal database structure (that is, database schema
revision). As a result, this type of database restore is portable from one Ovation system to
another or if used in the context of a software upgrade.
Network DDB information is reassigned and subsequently compressed. The database tables
used in the distribution of information to Operator Stations is regenerated and subsequently
compressed. These result in a reduction in the time required for future clear/reboot of Operator
Stations due to a consolidation of the Oracle distributed database tables.
This database restoration process is slightly more involved and time-consuming.
13.6.6 A DVANTAGES OF RESTORING A PARTIAL DATABASE
Restoring a partial database provides the following advantages:

The primary source of the database restoration (the PowerTools export file) is portable from
one Ovation system to another and across different release levels of Ovation software.
Network information is regenerated starting with new DDB IDs. This typically results in a lower
number of overall network DDBs (as compared to the network DDB assignments prior to the
restore or compared to the Ovation system from which the PowerTools export file was taken)
and a corresponding decrease in the network bandwidth associated with the Ovation DDBs.
The database distribution tables are regenerated following the initial loading of the Ovation
point originators. The result is a lower overall maximum distributed database sequence
number and a corresponding reduction in the time required for a cleared Ovation Operator
Station to be fully functional.
OS180_10 91
13.7 Restoring the Control Builder drawings
13.6.7 D ISADVANTAGES OF RESTORING A PARTIAL DATABASE
Restoring a partial database provides the following disadvantages:

Control information must be re-added to the PowerTools Database tables. This requires
execution of Control Builder scripts.
Since Ovation System IDs are reassigned, all custom graphics must be recompiled.
13.6.8 T O RESTORE A PARTIAL DATABASE
Use the following procedure to reload the Power Tools partial database (none of the structure)
from the backup tape.
1. Log in as user wdpf at the workstation that is being used as the Power Tools server (you
can also remotely log in by using the rlogin command:
su - wdpf
(the default password is wdpf)
2. Insert the Power Tools database backup tape into the tape drive.
3. Untar the saved <exportfile.Z> from the tape.
cd <appropriate_directory>
tar xvf /dev/rst4
(where <appropriate_directory> is a directory large enough to hold the file)
4. Uncompress the backup file with the following command:
uncompress <exportfile.Z>
5. Run the import program:
/usr/wdpf/db/bin/ptdbimp ptadmin <exportfile>
6. After the database has been restored, restore the Control Builder drawings (these contain the
control strategy for the system).
7. Clear and reload each drop in the system with the drop loader tool (See Ovation Init and
Admin Tools User Guide.)
13.7 R E S T O R I N G THE CONTROL BUILDER DRAWINGS
Restore Control Builder drawings at an Ovation Engineering Station from a backup tape. You can
reload the drawings after a complete database or a partial database has been restored.
13.7.1 T O RESTORE C ONTROL B UILDER DRAWINGS AFTER A COMPLETE DATABASE

RESTORATION
1. Insert the Control Builder drawings backup tape into the tape drive.
2. Extract and uncompress the saved cbdata.tar.Z from the tape.
cd /wdpf/rel/data
tar xvf /dev/rst4
uncompress cbdata.tar.Z
tar xvf cbdata.tar
92 OS180_10
13.7 Restoring the Control Builder drawings
13.7.2 T O RESTORE C ONTROL B UILDER DRAWINGS AFTER A PARTIAL DATABASE

RESTORATION
Use the following procedure to reload the Control Builder drawings after the Power Tools partial
database (only data, no structure) has been reloaded:
1. Use the Login Menu system to open the Control Builder:

Access the applicable User Login menu
Select Tools
Select Power Tools
Select Control Builder
(this will initialize the parameters for Control Builder)
2. Quit the Control Builder.
3. Use the Login Menu system to open a Command Tool:
Access the applicable User Login menu
Select Tools
Select Command Line Access
Select Cmdtool
4. Type the following at the command prompt:
source ~wdpf/.cshrc
/usr/wdpf/cb/bin/load_all.csh DBASE
source ~ptadmin/.cshrc
cd /wdpf/rel/data/dbdata
sqlplus ptadmin/ptadmin@ptdb @import_sheet_order.sql
A prompt will appear asking if you want to continue. Enter C to continue. Another prompt will
appear. Enter C to continue.
5. The reloading process begins. The drawing sheets are checked for errors and each drawing
sheet takes approximately two to four minutes to process. The command prompt returns when
the sheets have all been processed.
6. Any errors are located in the following file:
/wdpf/rel/data/cbdata/dropnnn/*.err
(where nnn is the drop number)
7. Use the Ovation Admin Tool’s Download Configuration to Drops function to
Query/Download the monitor graphics to the appropriate drops.
OS180_10 93
S E C T I O N 14
USING THE SOFTWARE MAINTENANCE TOOL
IN THIS SECTION
What is the Software Maintenance Tool? ......................................................................... 96

Accessing the Software Maintenance Tool....................................................................... 99
Updating the Software Server ........................................................................................... 99
Adding/removing individual package(s) .......................................................................... 102
Locating modified software on a disk.............................................................................. 106
After using the Software Maintenance Tool .................................................................... 106
OS180_10 95
14.1 What is the Software Maintenance Tool?
14.1 W H A T IS THE SOFTWARE MAINTENANCE TOOL?

The Software Maintenance Tool provides a Graphical User Interface (GUI) that allows you to view
and modify the revisions of the software packages that are extracted from the CDROM.
Use the Menu Bar in the Main window to select the software packages that are required for the
system. This window is shown in the following picture and is described in the following table. A
scrolling list displays the selected packages. Below the scrolling list is an area that displays
details for the selected package.
Note: THE MAIN WINDOW SHOWS THE SOFTWARE THAT YOU HAVE SELECTED, NOT
THE SOFTWARE THAT EXISTS ON THE MACHINE. To compare your selections with the
current software on the machine, use the Check function.
Figure 6: Software Maintenance Tool Main Window
Maintenance Tool Main Window Functions
FUNCTION DESCRIPTION
File Provides a means to exit from the GUI.
96 OS180_10
FUNCTION DESCRIPTION
View View selects the level of detail (see page 98) that is shown in the body of the
main window.
Select Overview of Selected Clusters, Packages, and Patches to display a
Software Overview window. Select one of the more detailed items to display a
scrolling list of packages. Below the scrolling list is an area that displays details
for the selected packages. The possible levels are:
Overview of Selected Clusters, Packages, and Patches - The least amount
of detail, only the major pieces (clusters) are listed, along with the packages
that were added to or removed from the cluster.
Details of WEStation Packages Available for Installation - Complete
information about all the available WEStation Software Packages.
Details of WEStation Packages Available for Installation (where more
recent packages exist) - Shows a subset of available WEStation packages.
This subset lists the most recent versions of any packages if they are not
already loaded on your system, and ignores versions already on your system.
Details of Solaris Patches Available for Installation - Complete details about
all the available Solaris Patches.
Details of Solaris Patches Available for Installation (where more recent
patches exist) - Shows a subset of available Solaris packages. This subset
lists the most recent versions of any packages if they are not already loaded on
your system, and ignores versions already on your system.
Clusters Selects a complete group of software packages (cluster). Submenus from this
item allow you to select any of the predefined clusters of WEStation software or
Solaris Patches that are available.
Check Compares software available on the CD with software which currently exists on
the Software Server. You can install or remove packages until the selected and
actual packages match.
Log Displays a log file that contains a list of all the installed/removed software
packages and patches on this Server.
Help Provides online help for the user.
OS180_10 97
14.1.1 S OFTWARE M AINTENANCE T OOL WINDOW ( SHOWING DETAILS )
This section describes the documentation details available for a software package when you
select an option from the View menu that provides additional details.
Figure 7: Software Maintenance Tool Window (showing details)
Software Maintenance Tool Window Fields
FIELD DESCRIPTION
Selected Revision Indicates the revision of the software package that has been selected for the
project.
Installed Revision Indicates the revision of the software package that is currently installed for the
project.
Name Name of the software package.
Description Description of the software package. The fields Information for Revision,
Installation, Dependencies, and Summary, apply to one specific revision of the
software package.
98 OS180_10
14.2 Accessing the Software Maintenance Tool
FIELD DESCRIPTION
Information for Revision Revision of the software for which the information is being displayed. This choice
can be changed via the Select Revision button.
Installation Indication of whether or not this revision of software should be installed. This field
can contain the following values:
Base - this revision of the software was included in the initial release,
(validated version), of the package.
Optional - the installation of this revision is optional and is up to the discretion
of the user.
Suggested - this revision is suggested and the use of previous revisions is
discouraged.
Summary Reason for this revision of the software package.
Dependencies Lists other package revisions which are required with the selected package.
Select Revision button Selects the software revision.
14.2 A C C E S S I N G THE SOFTWARE MAINTENANCE TOOL
Note: If the Init or the Admin Tool is running, QUIT the Tool before accessing the Software
Maintenance Tool.
In order to access the Software Maintenance Tool, open a Terminal window and type the
following at the prompt:
su
# cd /
# /cdrom/cdrom0/swmaint &
14.3 U P D A T I N G THE SOFTWARE SERVER

Ovation software and Solaris Patches are distributed in sets named “Clusters.” Each of these
clusters is given a name and the Software Maintenance GUI allows you to select the clusters by
name.
OS180_10 99
14.3 Updating the Software Server
14.3.1 T O MATCH A CLUSTER OF PACKAGES

1. Access the Software Maintenance Tool (see page 99).
Figure 8: Software Maintenance Tool Main Window
2. From the View menu, select Overview of Selected Clusters, Packages, and Patches.
3. From the Clusters menu, select the appropriate cluster. Note that the clusters are separated
into WEStation packages and Solaris Patches. Choose a WEStation cluster and a Solaris
Patch cluster.
100 OS180_10
14.3 Updating the Software Server
4. Select the Check item to display the Check Software Server Against Selected Packages
and Patches pop-up window.
Figure 9: Check Software Server Against Selected Packages and Patches
5. From the WEStation Packages menu in the pop-up window, select the Check Package
Dependencies and Check Installed Versions boxes for the type of cluster you are adding.
6. On the pop-up window, select the Start Checking button. This compares your selections with
the software currently on your Software Server. If any differences are found, the Software
Server Differences pop-up window appears.
7. The Software Server Differences pop-up window contains a list of actions to take to resolve
the differences between your selections and the software currently on your Software Server.
Select those items which you wish to have corrected, and press the Update Software Server
button.
OS180_10 101
14.4 Adding/removing individual package(s)
CAUTION! Scroll through the entire list before selecting the Update Software Server button,
to ensure that no software will be unintentionally removed.
Figure 10: Software Server Differences Window
8. If an additional pop-up window appears indicating an error has occurred, do the following:
a) Acknowledge the pop-up message.
b) In the Compare with Software Server window, note the dependent packages and
revisions.
c) From the View menu on the main window, select Details of WEStation Packages
Available for Installation or Details of Solaris Patches Available for Installation.
d) Select the packages and revisions as noted above.
e) Return to Step 4.
14.4 A D D I N G / R E M O V I N G INDIVIDUAL PACKAGE(S)
WEStation software and Solaris Patches are distributed in sets named Clusters. Each of these
clusters is given a name and the Software Maintenance GUI allows you to select the clusters by
name. If any of the clusters do not correspond exactly to the configuration desired, you can “fine
tune” the cluster configuration by adding or deleting individual packages.
102 OS180_10
14.4.1 T O CHOOSE A CLUSTER

2. From the View menu, select Overview of Selected Clusters, Packages, and Patches.
3. From the Clusters menu, select the desired cluster. Note that the clusters are separated into
WEStation Software and Solaris Patches. Choose a WEStation cluster and a Solaris Patch
cluster.
14.4.2 T O CUSTOMIZE A CLUSTER

2. From the View menu, select one of the more detailed views.
3. On the scrolling list of the main window, select the package you want to add or remove. This
displays the information associated with the package at the bottom of the window.
4. To add a package, select the revision you wish to install.
To remove a package, select the revision named None.
5. Press the button labeled Select Revision XXXX to record your selection.
6. Repeat Steps 2, 3, and 4 until you reach the desired configuration.
As packages are selected, they are removed from the window.
14.4.3 T O COMPLETE THE INSTALLATION

OS180_10 103
2. Select the Check item to display the Check Software Server Against Selected Packages and
Patches pop-up window.
Figure 11: Check Software Server Against Selected Packages and Patches
3. On the pop-up window, select the Check Package Dependencies and Check Installed
Versions boxes for the type of cluster you are adding.
104 OS180_10
4. On the pop-up window, select the Start Checking button. This compares your selections with
the current software on the Software Server. If any differences are found, the Software Server
Differences pop-up window displays.
Figure 12: Software Server Differences Window
5. If the Software Server Differences window appears, it contains a list of actions to take to
resolve differences between your selections and the current software on the Software Server.
Select those items that you wish to correct, and press the Update Software Server button.
Note: If a Discrepancy error occurs during the Start Comparing Process, proceed to Step 6.
6. If an additional pop-up window appears indicating a dependency error has occurred, do the
following:
a) Acknowledge the pop-up message.
b) In the Compare with Software Server window, note the dependent packages and
revisions.
c) From the View menu on the main window, select one of the more detailed views.
d) Select the packages and revisions that you noted in Step b.
e) Return to Step 4.
OS180_10 105
14.5 Locating modified software on a disk
14.5 L O C A T I N G M O D I F I E D S O F T W A R E O N A D I SK
The Software Maintenance tool allows you to query the software on your system to determine if
any software has been changed. For example, some files on your system may be customized
project specific files. Loading new software may overwrite these files. Therefore, you should
check for these files and make a backup of each of them.
14.5.1 T O LOCATE MODIFIED SOFTWARE ON A DISK

2. Select the Check function on the Menu Bar of the main window . The pop-up Check Software
Server Against Selected Packages and Patches window (see page 100) displays.
3. Select Check for Modified Files and press the Start Checking button.
4. If modified files are detected, another window appears detailing the file information.
5. Backup these files to some other media before updating the Software Server.
14.6 A F T E R USING THE SOFTWARE MAINTENANCE TOOL

If Ovation workstation software packages have been installed/removed, perform the following:
1. Access the Ovation Admin Tool.

2. Re-install all packages on the Software Server and download to all drops.
If Solaris Patches have been installed/removed, perform the following;
1. Copy the S91_Load_Patches script to the correct start-up directory.

2. Reboot the drop.
106 OS180_10
S E C T I O N 15
FORMATTING THE HARD DISK
IN THIS SECTION
When do you need to format the hard disk? ................................................................... 107
15.1 W H E N DO YOU NEED TO FORMAT THE HARD DISK?
During rebooting of a drop, a warning message similar to the following appears if the disk is not
properly formatted.
Corrupt label - wrong magic number
If this occurs, the hard disk must be reformatted. This section provides a procedure for formatting
the hard disk.
15.1.1 T O FORMAT THE HARD DISK
Note: The sequence of prompts may vary depending on the previous formatting of the disk and
the configuration of the workstation.
1. If you are not in the process of installing Solaris, and the disk needs to be formatted, become
Superuser (root) and skip to Step 3.
OR
If you are in the process of installing Solaris, and the disk needs to be formatted, proceed to
Step 2.
2. Select Exit from the Install Solaris Software - Initial window.
A prompt appears asking the following:
Really exit install (y/n)?

Enter y or yes.
3. Type in format.
This provides the opportunity to format the disk.
Note: If the drop is a Historian Report Server (HSRS), Power Tools Database Server (PTSV), or
an Engineer/Software/Power Tools/Operator/Historian Report Server (OMNI), with multiple
disks, you must format each disk separately.
OS180_10 107
15.1 When do you need to format the hard disk?
4. A list of Available Disk Selections displays along with the name of the disk. A prompt appears
to enter the number of the disk to be formatted:
Specify disk (enter its number)

Enter the applicable number (typically 0).
5. If the disk is unlabeled, a prompt may appear asking whether to label the disk. Enter y. The
disk will be automatically labeled.
If the disk is unable to be labeled, type format at the format prompt, and then enter y.
6. The Format Menu appears.
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition- select (define)a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
quit
At the format prompt, enter type.
7. A list of Available Drive Types appears. A prompt appears to enter the type of the disk to be
formatted:
Specify disk type (enter its number).
Select the “Auto configure” option (typically designated as 0).
A prompt appears asking the following:
Disk not labeled. Label it now?
Enter y
108 OS180_10
8. The format prompt appears.

Enter “?” to display the Format Menu:
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define)a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
quit
At the format prompt, enter defect.
9. The Defect Menu appears.
DEFECT MENU:
primary - extract manufacturer’s defect list
grown - extract manufacturer’s and repaired defects lists
both - extract both primary and grown defects lists
print - display working list
dump - dump working list to file
quit
At the defect prompt, enter both. A message similar to the following appears:
Extracting both primary and grown defect lists... Extraction
complete. Current defect list updated, Total of xx defects (where xx
represents the number of defects found by the system).
10. At the defect prompt, enter q.
11. At the format prompt, enter partition.
12. The Partition Menu appears:
PARTITION MENU:0- change ‘0’ partition
1 - change ‘1’ partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
quit
At the partition prompt, enter print.
OS180_10 109
13. The Current Partition Table appears (where xx represents values entered by the system):
PART T AG FLAG CYLINDERS SIZE BLOCKS
0 xx xx 0 0 (0/0/0)
1 xx xx 0 0 (0/0/0)
2 xx xx 0 0 (0/0/0)
3 xx xx 0 0 (0/0/0)
4 xx xx 0 0 (0/0/0)
5 xx xx 0 0 (0/0/0)
6 xx xx 0 0 (0/0/0)
7 xx xx 0 0 (0/0/0)
At the partition prompt, enter 2. The following appears:
2 xx xx 0 0 (x/x/x)
14. The following prompts appear and should be answered in the following manner:
Enter partition id Tag <backup>: Press Return.
Enter partition permission flag [wm or wu]: Press Return.
Enter new starting cy [0]: Press Return.
Enter partition size [xb, xc, x.xmb): Press Return.
15. At the partition prompt, enter 6. The following appears:
6 xx xx x x (x/x/x)
16. The following prompts appear and should be answered in the following manner:
Enter partition id Tag <usr>: Press Return.
Enter partition permission flag [wm or wu]: Press Return.
Enter new starting cy [0]: Press Return.
Enter partition size [xb, xc, x.xmb): Press Return.
17. At the partition prompt, enter print. The following appears:
0 xx xx 0 0 0/0/0
1 xx xx 0 0 0/0/0
2 xx xx 0 xxxxxxxx.xxm xxxx/0/0
b
3 xx xx 0 0 0/0/0
4 xx xx 0 0 0/0/0
5 xx xx 0 0 0/0/0
6 xx xx 0 xxxxxxxx.xxm xxxx/0/0
b
7 xx xx 0 0 0/0/0
110 OS180_10
18. At the partition prompt, enter q.

19. The format prompt appears. Enter label. The following prompt appears:
Ready to label disk, continue?
Enter y or yes.
20. At the format prompt, enter analyze.
The Analyze Menu appears:
ANALYZE MENU
read - read only test (doesn’t harm SunOS)
refresh - read then write (doesn’t harm data)
test - pattern testing (doesn’t harm data)
write - write then read (corrupts data)
compare - write, read, compare (corrupts data)
purge - write, read, write (corrupts data)
print - display data buffer
setup - set analysis parameters
config - show analysis parameters
quit
21. At the Analyze prompt, enter setup.
The following setup prompts appear and should be answered as follows:
Analyze entire disk [yes]? Enter y or yes.
Loop continuously [no]? Press Return.
Enter number of passes [2]: Press Return.
Repair defective blocks [yes]? Press Return.
Stop after first error [no]? Press Return.
Use random bit patterns [no]? Press Return.
Enter number of blocks for transfer [xx /xx/xx]: Press Return
(where xx is the default value).
Verify media after formatting [yes]? Press Return.
Enable extended messages [no]? Press Return.
Restore defective list [yes]? Press Return.
Restore disk label [yes]? Press Return.
22. At the Analyze prompt, enter compare. The following message appears:
Ready to analyze (will corrupt data. This
takes a long time, but is interruptable
with CTRL-C. Continue?
Enter y or yes.
23. A message similar to the following appears:
pass 0 - pattern = 0xc6dec6de
2441/13/28
pass 1 - pattern = 0x6db6db6d
2441/13/28
Enter q to exit the analyze menu.
Enter q to exit the format menu.
24. Enter suninstall to return to the Solaris Installation menu.
25. Continue to install Solaris 10 (see page 21).
OS180_10 111
INDEX
Installing Solaris 10 Patches and Third-Party

A software • 28
Accessing the Ovation Security Builder • 19 Installing Solaris 10, Solaris 10 patches, and
Accessing the Software Maintenance Tool • Ovation software • 39, 45
99 Installing Third-Party software • 42, 47
Adding/removing individual package(s) • 102 Installing Third-Party software on a Software
Advantages of restoring a complete Server • 38
database • 90 Introduction to Ovation software installation •
Advantages of restoring a partial database • 1
91
L
After using the Software Maintenance Tool •
106 Licensing for an Ovation Solaris-based
system • 9
B Loading a Standalone Ovation Security
Backing up printer information • 83 Server • 11
Backing up the Data Link files • 84 Loading an Ovation Software Server • 21
Backing up the system • 71 Loading workstations that contain at least
Backing up Third-Party software licensing 384 MB of RAM • 39
information • 84 Loading workstations that contain less than
384 MB of RAM • 45
C Locating modified software on a disk • 106
Configuring a keyboard • 3 O
Configuring a monitor • 3
Configuring Ovation release software • 31 OCBT configuration table • 75
Configuring Ovation Security Server Ovation restoration overview • 85
software • 17
P
Connecting a cartridge tape drive • 4
Connecting a CDROM drive • 4 Planning for your Ovation Security Server • 8
Copyright Notice • 2 Planning Ovation hardware installation • 3
Planning Ovation software installation • 7
D
R
Disadvantages of restoring a complete
database • 90 Restoring a complete database • 89
Disadvantages of restoring a partial Restoring a partial database • 91
database • 92 Restoring the Control Builder drawings • 92
Restoring the Ovation Historian (HSR) • 88
F Restoring the Ovation system • 85
Formatting the hard disk • 107 Restoring the Power Tools database files •
89
I
S
Installing AutoCAD • 49
Installing Ovation release software on a Software Maintenance Tool window
Security Server • 16 (showing details) • 98
Installing Ovation release software on a Summary of Changes • 3
Software Server • 30
T
Installing Solaris 10 for Security Servers • 11
Installing Solaris 10 for Software Servers • To add an Ultra 25, 45 workstation to the
21 network using a Solaris 10 (Version 3/05)
Installing Solaris 10 Patches • 14 Server • 64
OS180_10 113
Index
To backup a complete database (using To update Solaris 10 patches (Software

Oracle Export program exp) • 81 Server) using the Software Maintenance
To backup a partial database (using Tool • 51
PowerTools Export program ptdbexp) • 82 To update Solaris 10 patches (workstations)
To backup the Control Builder (CB) drawings • 57
• 83 To update Third-Party software (Software
To backup the Ovation Historian (HSR) • 82 Server) • 56
To backup the Ovation Security Server • 79 To update Third-Party software (workstation)
To backup the Software Server • 79 • 58
To choose a cluster • 103 To upgrade a Software Server from 1.7 to
To complete the installation • 103 1.8 (Combination Software
To configure Ovation release software • 31 Server/Security Server on a single
To configure Ovation Security Server network) • 67
software • 17 To upgrade a Software Server from 1.7 to
To connect a SCSI device to a drop • 5 1.8 (Standalone Security Server on a
To customize a cluster • 103 multiple network) • 65
To format the hard disk • 107 To upgrade an Ovation system from 1.7.x to
To install AutoCAD • 49 1.8 • 60
To install Ovation release software on a To upgrade an Ovation system from Ovation
Security Server • 16 1.x to 1.8 • 59
To install Ovation release software on a To upgrade drivers for computers with
Software Server • 30 Linksys cards • 62
To install software on Fast Ethernet system To upgrade drivers for computers with Znyx
drops • 39, 45 cards • 61
To install software on FDDI system drops • To use OCBT • 71
40 To use the Setup window • 78
To install Solaris 10 on a Software Server •
21 U
To install Solaris 10 on an Ovation Security Understanding the software installation
Server • 11 process for Solaris-based Ovation
To install Solaris 10 Patches • 14 systems • 1
To install Solaris 10 Patches and Third-Party Updating all other Ovation workstations • 57
software • 28 Updating Ovation release software
To install Third-Party software • 43, 47 (Software Server) • 53
To install Third-Party software on a Software Updating Ovation release software
Server • 38 (workstations) • 58
To locate modified software on a disk • 106 Updating Solaris 10 patches (Software
To match a cluster of packages • 100 Server) • 51
To restore a complete database • 90 Updating Solaris 10 patches (workstations) •
To restore a partial database • 92 57
To restore all drops (except the Software Updating the Software Server • 99
Server) • 87 Updating Third-Party software (Software
To restore Control Builder drawings after a Server) • 56
complete database restoration • 92 Updating Third-Party software (workstation)
To restore Control Builder drawings after a • 58
partial database restoration • 93 Updating your Ovation Software Server • 51
To restore the Ovation Historian (HSR) drop Upgrading your Ovation System • 59
• 88 Using command lines to backup the system
To restore the Ovation Security Server • 85 • 79
To restore the Software Server • 86 Using OCBT to backup the system • 71
To update Ovation release software Using the Software Maintenance Tool • 95
(Software Server) using the Software
Maintenance Tool • 53 W
To update Ovation release software
What are software updates? • 51
(workstation) • 58
What are Software updates? • 57
What are the hardware requirements? • 3
114 OS180_10
Index
What are the software requirements? • 7

What is a SCSI device? • 5
What is a system backup? • 71
What is a system upgrade? • 59
What is AutoCAD? • 49
What is the Software Maintenance Tool? •
96
When do you need to format the hard disk? •
107
OS180_10 115

Software Installation Manual For Ovation 1.8 OS180 - 10: January 2007

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Installation Manual For Ovation 1.8 OS180 - 10: January 2007

Uploaded by

Copyright:

Available Formats

Software Installation Manual for Ovation 1.

1 Introduction to Ovation software installation 1

2 Planning Ovation hardware installation 3

3 Planning Ovation software installation 7

4 Loading a Standalone Ovation Security Server 11

5 Loading an Ovation Software Server 21

5.4 Installing Third-Party software on a Software Server ....................................................... 38

6 Loading workstations that contain at least 384 MB of RAM 39

7 Loading workstations that contain less than 384 MB of RAM 45

9 Updating your Ovation Software Server 51

10 Updating all other Ovation workstations 57

11 Upgrading your Ovation System 59

11.1.2 To upgrade an Ovation system from 1.7.x to 1.8 ............................................ 60

12 Backing up the system 71

13 Restoring the Ovation system 85

14 Using the Software Maintenance Tool 95

15 Formatting the hard disk 107

INTRODUCTION TO OVATION SOFTWARE INSTALLATION

1.1 UNDERSTANDING THE SOFTWARE INSTALLATION PROCESS FOR SOLARIS-

Choosing Solaris Operating System

SOFTW ARE SERVER SOLARIS T ARGET OPERATING SYSTEM

PLANNING OVATION HARDWARE INSTALLATION

What are the hardware requirements? ............................................................................... 3

2.1 WHAT ARE THE HARDWARE REQUIREMENTS?

 CRT monitor (for viewing commands and messages).

2.2 CONFIGURING A MONITOR

2.4 CONNECTING A CDROM DRIVE

2.5 CONNECTING A CARTRIDGE TAPE DRIVE

2.6 WHAT IS A SCSI D EV I C E ?

2.6.1 T O CONNECT A SCSI DEVICE TO A DROP

PLANNING OVATION SOFTWARE INSTALLATION

What are the software requirements?................................................................................. 7

3.1 WHAT ARE THE SOFTWARE REQUIREMENTS?

3.2 PLANNING FOR YOUR OVATION SECURITY SERVER

Standalone Security Server

Combination Security Server

3.3 LICENSING FOR AN OVATION SOLARIS-BASED SYSTEM

LOADING A STANDALONE OVATION SECURITY SERVER

Installing Solaris 10 for Security Servers .......................................................................... 11

4.1 I N S T A L L I N G S O L A R I S 10 FOR SECURITY SERVERS

4.2 TO INSTALL S O L A R I S 10 ON AN OVATION SECURITY SERVER

21. A Welcome screen appears. Select Next.

TYPE SYSTEM DISK OTHER DISKS

Standalone Security Example A N/A

4.3.1 T O INSTALL S OLARIS 10 P ATCHES

3. Right-click in the background and select Tools and then Terminal.

4.4 INSTALLING OVATION RELEASE SOFTWARE ON A SECURITY SERVER

4.4.1 T O INSTALL O VATION RELEASE SOFTWARE ON A S ECURITY S ERVER

4.5 CONFIGURING OVATION SECURITY SERVER SOFTWARE

4.5.1 T O CONFIGURE O VATION S ECURITY S ERVER SOFTWARE

“This level of Ovation software supports a common Security

We now need to know the configuration of this drop, three

[1] Standalone Security Server

[2] Ovation Software Server/ Security Server

[3] Ovation Software Server

Enter this Drop Configuration <2> : “

Enter the Domain name that this computer will be part of

6. The following message appears:

Please enter the Ovation Domain Administrator (admin)

WORKSTATION TYPE PRIM ARY NIC BACKUP NIC

Sun Blade with external card afe0 (Linksys) eri0 (onboard)

UltraSPARC 5, 10, 60 afe0 (Linksys) hme0

UltraSPARC 5, 10, 60 hme0 hme1

CRT monitor (for viewing commands and messages).