EMC® AutoStart™

Version 5.4.3

Installation Guide
300-014-101
REV A01

EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 1998 - 2012 EMC Corporation. All rights reserved.

Published May, 2012.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED „AS IS.‰ EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION,
AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section
on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

2 EMC AutoStart Installation Guide

 Preface

As part of an effort to improve and enhance the performance and capabilities of its product
line, EMC from time to time releases revisions of its hardware and software. Therefore, some
functions described in this guide may not be supported by all revisions of the software or
hardware currently in use. For the most up-to-date information on product features, refer to
your product release notes.
If a product does not function properly or does not function as described in this guide, please
contact your EMC representative.

Note: AutoStart runs on the following Windows and UNIX platforms: Windows, Solaris,
HP-UX, AIX, and Linux.

Audience The information in this guide is intended for use by system administrators who are
responsible for installing software and maintaining the servers and clients on a
network.

Related The latest updates of product documentation are available at:

documentation
http://Powerlink.EMC.com
Most of the documents are in Adobe Acrobat Portable Document Format (PDF), and
can be viewed by downloading and installing the Adobe Acrobat Reader. The Reader
is available directly from Adobe at www.adobe.com.
Documents specifically related to AutoStart include:
◆ EMC AutoStart Release Notes
◆ EMC AutoStart Concepts Guide
◆ EMC AutoStart Administrator’s Guide

Conventions used in EMC uses the following conventions for notes, cautions, warnings, and danger
this guide notices.

Note: A note presents information that is important, but not hazard-related.

! CAUTION
A caution contains information essential to avoid data loss or damage to the system
or equipment. The caution may apply to hardware or software.

EMC AutoStart Installation Guide 3

Preface

! IMPORTANT
An important notice contains information essential to operation of the software.
The important notice applies only to software.

Typographical conventions
EMC uses the following type style conventions in this document:
Normal In running text:
• Interface elements (for example, button names, dialog box
names) outside of procedures
• Items that user selects outside of procedures
• Java classes and interface names
• Names of resources, attributes, pools, Boolean expressions,
buttons, DQL statements, keywords, clauses, environment
variables, filenames, functions, menu names, utilities
• Pathnames, URLs, filenames, directory names, computer
names, links, groups, service keys, file systems, environment
variables (for example, command line and text), notifications
Bold In procedures:
• Names of dialog boxes, buttons, icons, menus, fields
• Selections from the user interface, including menu items and
field entries
• Key names
• Window names
In running text:
• Command names, daemons, options, programs, processes,
notifications, system calls, man pages, services,
applications, utilities, kernels
Italic Used for:
• Full publications titles referenced in text
• Unique word usage in text
Bold italic Anything requiring extra emphasis
Courier Used for:
• System output
• Filenames
• Complete paths
• Command-line entries
• URLs
Courier bold Used for:
• User entry
• Options in command-line syntax
Courier italic Used for:
• Arguments used in examples of command-line syntax
• Variables in examples of screen or file output
• Variables in path names
Courier bold, Variables used in a command-line sample
italic
<> Angle brackets enclose parameter or variable values supplied by
the user
[] Square brackets enclose optional values

4 EMC AutoStart Installation Guide

 Preface

| Vertical bar indicates alternate selections - the bar means “or”

{} Braces indicate content that you must specify (that is, x or y or z)
... Ellipses indicate nonessential information omitted from the
example

Where to get help EMC support, product, and licensing information can be obtained as follows.
Product information — For documentation, release notes, software updates, or for
information about EMC products, licensing, and service, go to the EMC online web
site (registration required) at:
http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on

Powerlink. To open a service request through the online support website, you must
have a valid support agreement. Please contact your EMC sales representative for
details about obtaining a valid support agreement or to answer any questions about
your account.

EMC AutoStart Installation Guide 5

Preface

6 EMC AutoStart Installation Guide

 Contents

Preface

Chapter 1 Introduction
About AutoStart....................................................................................................... 10

Chapter 2 Planning the AutoStart Domain

Primary and secondary agent nodes ..................................................................... 14
IP addresses ............................................................................................................... 15
Processes and services.............................................................................................. 16
Requirements............................................................................................................. 17

Chapter 3 Installing AutoStart on Windows

Overview.................................................................................................................... 22
System requirements ................................................................................................ 23
Performing a fresh installation ............................................................................... 24
Performing a rolling upgrade ................................................................................. 29
Performing a concurrent upgrade.......................................................................... 32
Downgrading to the previous release.................................................................... 34
Uninstalling AutoStart ............................................................................................. 37

Chapter 4 Installing AutoStart on Solaris

AutoStart installation .............................................................................................. 52
System requirements ............................................................................................... 53
Performing a fresh installation ............................................................................... 44
Performing a rolling upgrade ................................................................................. 50
Performing a concurrent upgrade.......................................................................... 54
Downgrading to the previous release.................................................................... 57
Uninstalling AutoStart ............................................................................................. 60

Chapter 5 Installing AutoStart on Linux

AutoStart installation ............................................................................................... 62
System requirements ................................................................................................ 63
Performing a fresh installation ............................................................................... 64
Performing a rolling upgrade ................................................................................. 70
Performing a concurrent upgrade.......................................................................... 73
Downgrading to the previous release.................................................................... 76

EMC AutoStart Installation Guide 7

Contents

Uninstalling AutoStart .............................................................................................79

Chapter 6 Installing AutoStart on HP-UX

Overview ...................................................................................................................81
System requirements................................................................................................82
Performing a fresh installation...............................................................................83
Performing a rolling upgrade.................................................................................88
Performing a concurrent upgrade .........................................................................92
Downgrading to the previous release ...................................................................95
Uninstalling AutoStart ............................................................................................98

Chapter 7 Installing AutoStart on AIX

Overview ..................................................................................................................100
System requirements...............................................................................................101
Performing a fresh installation..............................................................................102
Performing a rolling upgrade................................................................................107
Performing a concurrent upgrade ........................................................................ 111
Downgrading to the previous release ..................................................................114
Uninstalling AutoStart ...........................................................................................117

Chapter 8 Installing AutoStart in Virtual environments

Supported virtual environments...........................................................................120
AutoStart installation..............................................................................................121

Chapter 9 Silent Install

Summary ..................................................................................................................124
Silent Installation on Windows .............................................................................125
Silent Upgrade on Windows..................................................................................131
Silent Uninstallation on Windows ........................................................................133
Error handling .........................................................................................................135
Silent Installation on Unix/Linux.........................................................................136
Silent Uninstallation on Unix/Linux ...................................................................138
Limitations ...............................................................................................................139

Chapter 10 Troubleshooting
Agent installation error messages.........................................................................142
Console startup error messages ............................................................................144
Agent startup error messages................................................................................146
Turning off UNIX console messages ....................................................................148
Restoring configuration using DEF file................................................................149

8 EMC AutoStart Installation Guide

 1
Invisible Body Tag

Introduction

This chapter provides background information on EMC AutoStart. Throughout this

document, the product is referred to as AutoStart:
◆ About AutoStart ................................................................................. 10

Introduction 9
Introduction

About AutoStart
The EMC® AutoStart™ architecture is built on the concepts of nodes, which are
grouped in domains. One or more nodes can be grouped to form the AutoStart
domain. All operations performed by AutoStart takes place within the domain.

Nodes
The node is a machine with an AutoStart agent installed on it and running. The node
is the basic building block within AutoStart. All the applications to be managed by
AutoStart are installed on the node. Other non-managed applications may also run
on the node.

Domain
A domain is the set of nodes that AutoStart manages. AutoStart domains should not
be confused with the Windows NT domain, which defines a group of
Windows-based machines on a Local Area Network (LAN). If AutoStart is running
on a Windows machine, the AutoStart domain may span one or more Windows NT
domains.
An AutoStart domain may contain a maximum of five primary agents and five
secondary agents (one agent per node). There are typically two to five primary agent
nodes in a domain. Other nodes in a domain run as secondary agents.
A node can be a member of only one AutoStart domain. Each domain name must be
unique so that it can be identified easily. All the management activities that AutoStart
performs take place within the domain.

Agents
Each node has an AutoStart agent installed in it. The agent provides the monitoring
and management capabilities within the node. AutoStart uses two types of agents:
primary agents and secondary agents. The node configuration determines the type of
agent on it. There must be at least one primary agent in an AutoStart domain.

10 EMC AutoStart Installation Guide

 Introduction

Primary agents
A primary agent manages services and processes, executes rules, manages resource
groups, monitors the state of nodes and the processes running on nodes, and
maintains the AutoStart replicated database. Each primary agent includes the
following components:
◆ Agent Process
◆ Process Monitor
◆ Rule Interpreter
◆ Replicated Database
The agent process, process monitor, and rule interpreter form the Events and Rules
Engine, which provides management and monitoring capabilities for rules and
resource groups in the domain.
Primary agents cannot be deleted from the domain, but can be demoted to secondary
agents and then deleted.

Secondary agents
A secondary agent provides the full level of management and monitoring capabilities
as a primary agent, but does not execute rules or maintain a copy of the replicated
database. Each secondary agent includes the following components:
◆ Agent Process
◆ Process Monitor
Secondary agents can be promoted to primary agents.

Console
The console is a graphical administrative tool used to access information and initiate
operations on an agent, thus enabling management and monitoring of the domain
from a central location. The console may be installed on any machine in the network,
regardless of whether an agent has been installed on the machine.
The console is separate from the AutoStart agent. The information displayed in the
console is reported from the AutoStart agents. Likewise, all operations initiated
through the console are processed by the agent to which it is connected.

About AutoStart 11
Introduction

12 EMC AutoStart Installation Guide

 2
Invisible Body Tag

Planning the AutoStart

Domain

Before installing AutoStart, spend some time planning the AutoStart domain. This
chapter provides the information required to plan an AutoStart domain. It contains
the following sections:
◆ Primary and secondary agent nodes ............................................... 14
◆ IP addresses......................................................................................... 15
◆ Processes and services ....................................................................... 16
◆ Requirements ...................................................................................... 17

Planning the AutoStart Domain 13

Planning the AutoStart Domain

Primary and secondary agent nodes

When planning an AutoStart domain, it is important to plan the number of primary
agent nodes. A domain can contain as many as five primary agents and five
secondary agents (one agent per node). For a single-node domain, the agent installed
on the node must be a primary agent since the primary agent maintains a copy of the
database and runs a rule interpreter.
In domains of two or more nodes, EMC recommends two to five primary agents in
the domain. A system of two to five node primary agents provides a healthy level of
replication in the event of any node failures, and provides adequate assurances
against network partitions and other reliability issues.
Domains with more than one node should have at least two primary agents. A
domain with only one primary agent exposes a single point of failure, and when that
primary agent fails for any reason in a domain with only one primary agent defined,
all secondary agents lose their connection and must wait until the primary agent
returns. When more than five primary agents are present in a single AutoStart
domain, it creates unnecessary network traffic. The additional network traffic
overhead may cause performance degradation on the network without any
appreciable benefit in AutoStart reliability.
Other nodes in the domain must run as secondary agents. Secondary agents monitor
for node failure, process failure, and manage recovery. They do not maintain a copy
of the database or run rules, instead rely on primary agents to perform these tasks. As
the network overhead of a secondary agent is low, they are more suitable for
scalability to create larger domains.

14 EMC AutoStart Installation Guide

 Planning the AutoStart Domain

IP addresses
Before creating an AutoStart domain, the IP addresses to be used should be planned.
Each node in the domain should have at least one IP address for every interface to be
used by AutoStart.
Managed IP addresses, that are used in resource groups to migrate IP addresses from
node to node to provide high availability to applications which communicate to
clients using a TCP/IP or UDP based IP address, must also be reserved.
When configuring a high availability solution in an existing environment, some
applications may need to be reconfigured to use the managed IP address rather than
the static IP address that might be currently in use.

Note: While installing AutoStart on the new node, all domain lines configured on the first node
should be up.

Due to the nature of IP address operation, each static and managed IP address can
only be assigned to one node at a time. If an IP address is assigned to two nodes at the
same time, only the first node can use the IP address. Because of these limitations,
AutoStart cannot assign the same IP address on multiple nodes at a time. Therefore,
ensure that there are enough IP addresses to cover both the static and managed IP
addresses.

IP addresses 15
Planning the AutoStart Domain

Processes and services

All applications managed by AutoStart must be installed on all nodes on which they
can run. Typically, only one instance of a process or service runs at one time, but the
process or service must be available to execute on each node.

16 EMC AutoStart Installation Guide

 Planning the AutoStart Domain

Requirements
Network communication is critical to the proper operation of AutoStart. Proper
configuration and implementation of the network is extremely important. Redundant
networks, whether on a single subnet or multiple subnets, provide fault tolerance in
the event of failure. Network communication between all nodes in the domain must
be ensured.

Redundancy
EMC strongly recommends the use of redundant networks within AutoStart
domains. Without redundant networks, the network is a single point of failure, and
the risk of network partitions increases greatly.
AutoStart fully supports redundant networks and provides automatic failover for
communication in the event of a network failure.

Naming conventions for DNS hosts

DNS hostnames can consist of only alphanumeric characters (A-Z, 0-9) and multiple
hyphens (-). The last and first character cannot be a hyphen. Blank spaces are not
allowed. Windows nodes that do not conform to this standard will not operate
correctly in a heterogeneous environment.The hostname should conform with
NetBIOS standards.

Hostname resolution
AutoStart agents use hostnames to locate other AutoStart nodes in the domain. To
ensure proper operation of the domain, it is critical that each node can lookup the
hostname of every other node in the domain. In addition, the name lookup for each
node must return an IP address for each network used by AutoStart for domain
communication. For example, if two domain/heartbeat networks are being used,
both IP addresses must be returned. The EMC AutoStart Administrator’s Guide
provides more information about domain networks. The AutoStart agent resolves the
partner hostnames by using an internally generated FT_HOSTS file and then the
standard Operating System resolution methods.

FT_HOSTS file
To provide proper hostname resolution for an AutoStart domain, the FT_HOSTS
functionality must be configured. FT_HOSTS is a simple text filename lookup that
only applies to name lookups done by AutoStart agents.
Standard name lookups are compatible and supported, but the following issues
should be addressed:
◆ Name lookup orders and behaviors are operating system dependent. On UNIX
systems, the name lookups are generally performed by a combination of host
files, DNS, and NIS. On Windows operating systems, host files, DNS, WINS, and
NetBIOS broadcasts provide name resolution. With these operating systems, only
some of the name lookup methods provide the ability to look up multiple IP
addresses (corresponding to the domain networks) for a given hostname. For
example, a name lookup on Windows that uses the local hosts file can only return
one IP address per hostname in the hosts file. All other IP addresses mapped to
this name in the hosts file are ignored.

Requirements 17
Planning the AutoStart Domain

◆ Network name services (DNS, NIS, and WINS) must be configured to be

redundant both in terms of physical hardware (highly available DNS, NIS, or
WINS servers) and in terms of alternate network paths.
The FT_HOSTS functionality provides an alternate name lookup method for
AutoStart in environments where the above issues cannot be addressed. The
existence of the FT_HOSTS file automatically enables this feature.
To set up FT_HOSTS, install the AutoStart Agent, and then create a file called
FT_HOSTS in the systems /etc directory (on windows, this file exists in
%WINDIR%\system32\drivers\etc folder). The format of this file is identical to
standard hosts file as shown next.

#**********
# Sample FT_HOSTS file
#
10.10.10.20 nodeA
192.168.1.20 nodeA
10.10.10.30 nodeB
192.168.1.30 nodeB
#
# End Sample FT_HOSTS
#**********

while creating FT_HOSTS file, remember:

◆ „#‰ indicates the beginning of a comment.
◆ Each line's format is <IP_ADDRESS> <HOST_NAME> (white space separated).
Any text after the hostname will be ignored.
◆ If the IP Address is invalid, that line is discarded without warning.
If the FT_HOSTS file exists in the proper directory on an AutoStart node, then the
AutoStart Agent will use this first for name resolution of other nodes. If the name
lookup succeeds, then all IP addresses for that hostname will be passed to the
AutoStart Agent. If this file does not exist or the node's hostname is not found in
the FT_HOSTS file, then the standard operating system dependent name lookup
will occur.
A fully configured AutoStart domain will contain one FT_HOSTS file on every
AutoStart Agent node. The FT_HOSTS file should contain one or more IP-hostname
entries for each node in the AutoStart domain. The number of IP/hostname entries
for a node is based on the number of Domain Networks that have been configured in
the environment. For example, if nodeA is using IP addresses 10.10.10.20 and
192.168.1.20 as AutoStart domain lines, two entries should be entered in the
FT_HOSTS file for this node. In general, there needs to be one entry for each Source IP
address defined as a Domain Network in the nodeÊs Failure Detection and Mirroring
tab in the console.
Name lookups avoid split brain scenarios and false failures. If a node's hostname can
only be resolved to one IP address, and that network is down, the nodes will not be
able to form a domain even though there may be another redundant network
available. The FT_HOSTS file is used solely by the AutoStart Agent for hostname
lookups. FT_HOSTS has no effect on lookups for any other purpose, including
AutoStart lookups of hostnames for IP Address Management:

Note: If user has a problem with name resolution, rename the file 01UpdHosts.pl to
_01UpdHosts.pl and manually edit the FT_HOST file as given below:

1. Go to %WINDIR%\system32\drivers\etc and open the FT_HOST file.

18 EMC AutoStart Installation Guide

 Planning the AutoStart Domain

2. Edit the FT_HOST file as below:

a. "#" indicates the beginning of a comment.
b. Each line's format is <IP_ADDRESS> <HOST_NAME>.
c. Example of host file:
#**********
# Sample FT_HOSTS file
#
10.10.10.20 nodeA
192.168.1.20 nodeA
10.10.10.30 nodeB
192.168.1.30 nodeB
#
# End Sample FT_HOSTS
#**********
3. Save and close the file.

DNS server
Using a DNS server ensures that the hostname resolves to all IP addresses in use for
all network interface cards (NICs) on a node. DNS resolution must be in place for all
network addresses. NetBIOS name resolution is not adequate to provide the complete
list of IP addresses for resolution and should not be relied upon for proper operation.
Similarly, the hosts file only works correctly for single network configurations (which
are not recommended in production environments).
To eliminate DNS as a single point of failure, multiple DNS servers should be
configured. If multiple subnets are in use, the DNS servers should not reside on a
single subnet. For example, if the node uses both the 1.2.3.0 and 1.2.4.0 subnets, a
DNS server should reside on each subnet.
If the DNS server is on a subnet which does not match the network subnets used on
the node, a default gateway must be designated to allow a router to forward
messages to the DNS server. A secondary gateway should be specified to provide a
redundant network path in case communication through the default gateway does
not work.

Network integrity
Before installing the AutoStart agents, complete network connectivity must be
ensured between all nodes to be added to the AutoStart domain. All nodes, both
primary and secondary, must be able to resolve the name of all agents in the domain.
Additionally, all nodes must be able to communicate over all networks to be used by
AutoStart. The nslookup command can be used to verify if the DNS is functioning
properly:
nslookup node_name

The ping command can be used to verify network connectivity between nodes:
ping node_name

All IPs on all machines to be used by AutoStart must be reachable and should be
verified with ping command.

Requirements 19
Planning the AutoStart Domain

IP multicast
The network configuration for the domain may be on one network subnet, or span
multiple subnets with communication through a router. Heartbeats used for failure
detection use IP multicasts by default. If the router supports multicast forwarding,
AutoStart communicates normally without modification. If the router does not
support multicasts, the domain can still span multiple subnets by using AutoStartÊs
point-to-point heartbeat option for failure detection.

Managed IP addresses
When using managed IP addresses, the IP address must match the subnet of the static
IP address defined for the NIC. If the domain consists of 10 nodes, half can be on the
1.2.3 subnet, and the other half on the 1.2.4 subnet. If the managed IP address to be
moved is 1.2.3.255, the address can be assigned on the fives nodes that are part of the
1.2.3 subnet, but cannot be assigned on the five nodes in the 1.2.4 subnet.

Port numbers
AutoStart uses four ports for its internal communication between nodes. The port
numbers that are used are defined during the installation of the first node in the
domain. These ports should not be used by any other application on any node in the
domain. The port numbers must be chosen such that they are not in use, and not
likely to be used in future on any node.

Note: When setting up port numbers in a heterogeneous environment, to ensure that Windows
can use the ports, EMC recommends using the default port number of 8042, and above.

During installation, only the initial port number is specified. AutoStart automatically
uses the next three port numbers.

Firewall Settings for AutoStart

Currently, AutoStart is not qualified for use on any server that runs a firewall.
However, if you are using a firewall, refer to the configuring Firewall section for
important guidelines in the latest EMC AutoStart Administrator’s Guide.
For AutoStart installation to go through when Firewall is enabled, the default port
(8042) and the subsequent ports (8043, 8044 and 8045) should be added to the
exception list in the firewall settings.

20 EMC AutoStart Installation Guide

 3
Invisib Tag

Installing AutoStart on
Windows

Before installing AutoStart, be sure to spend some time planning the AutoStart
domain. Chapter 2, "Planning the AutoStart Domain," provides more information.
This chapter explains how to install AutoStart on Windows. It contains the following
topics:
◆ Overview ............................................................................................. 22
◆ System requirements ......................................................................... 23
◆ Performing a fresh installation......................................................... 24
◆ Performing a rolling upgrade........................................................... 29
◆ Performing a concurrent upgrade ................................................... 32
◆ Downgrading to the previous release ............................................. 34
◆ Uninstalling AutoStart ...................................................................... 37

Installing AutoStart on Windows 21

Installing AutoStart on Windows

Overview
There are two components in the AutoStart installation, the agent and the console.
◆ An AutoStart agent monitors and manages nodes and processes in the domain. It
manages resource objects such as managed IP addresses, node aliases, and data
sources as well. A primary agent executes rules, maintains replicated copies of the
database, and monitors other agents in the domain.
◆ An AutoStart console is a graphical administrative tool which accesses
information from an agent. It also initiates operations on an agent, enabling
management of the domain from a single location.
Install the agent and the console at the same time. Once the agent is installed, it
automatically passes information about the domain to the console installation.
The first three agents you install on nodes in the domain are installed as primary
agents. Subsequent nodes are installed as secondary agents. Secondary agents can be
promoted to primary agents after installation is complete.
When you install subsequent agents, the name of the node must be registered in the
console before the new agent can be brought online. AutoStart performs this
operation automatically if the user installing the AutoStart software is registered in
the AutoStart domain Security Manager.

Security
There are two Windows services that run during operation: Backbone and Agent. By
default, these services run under the Local System account. It is a Microsoft security
best practice to not assign specific user accounts other than the Local System for these
services. Optionally, two additional services can be running based on the
configuration of the domain. These services also should be run under the same
account as the Agent and Backbone.

22 EMC AutoStart Installation Guide

 Installing AutoStart on Windows

System requirements
Note: For most up-to-date information on System requirements, Operating systems, Agent and
Console requirements, and Service Pack versions, refer to EMC AutoStart Compatibility Guide
available on the EMC Powerlink® website (http://Powerlink.emc.com).

Operating systems, agent, console, and mirroring requirements for installing

AutoStart on Windows are as follows.

Agent requirements To run an AutoStart agent, each machine in the domain must meet the following
requirements:
◆ Minimum of 128 MB RAM.
◆ Minimum of 250 MB free disk space.
◆ A DNS server must be used for hostname resolution.
◆ DHCP cannot be used in the network configuration of any AutoStart network.
◆ Public network link. The server must be connected to the public network link.
◆ There may be additional requirements depending on the data source used in the
environment, for example the EMC Mirroring for Windows data source. The
Administration guide provides more information on mirroring requirements.
AutoStart 5.4.3 installation requires the Microsoft Visual C++ 2010 Redistributable
Package.

Note: The EMC AutoStart 5.4.x installation or upgrade will automatically install the above
Redistributable Package. For a x86 system, Microsoft VC++ 2010 re-distributable (x86) will be
installed.

Console The following are the requirements to run an AutoStart console:

requirements ◆ Windows Server 2003 R2 or Windows Server 2008 (SP2 or later) or Windows
Server 2008 R2.
◆ Minimum of 128 MB RAM.
◆ Minimum of 150 MB free disk space.

Network The following are the requirements of Network Connections:

Connections A minimum of two network connections for cluster communication:
◆ One NIC for the production network and AutoStart domain line.
◆ One NIC for a private network used as an AutoStart domain line.

Note: A dedicated third network connection is necessary if using EMC Mirroring for Windows
for shared data access.

Note: For more information, refer to EMC AutoStart Administrator's Guide available on on the
Powerlink website (http://Powerlink.EMC.com)

System requirements 23
Installing AutoStart on Windows

Performing a fresh installation

This section covers a fresh installation of the AutoStart agent and console, which are
installed from a single executable file. For an upgrade installation, go to "Performing
a rolling upgrade" on page 29 and "Performing a concurrent upgrade" on page 32.

Note: "System requirements" on page 23 provides more information before you perform a fresh
installation.

The first three agents installed in the domain are installed as primary agents. After
the third installation, the agents are installed as secondary agents, which contact a
primary agent to get information about the domain. You can promote a secondary
agent to a primary agent after installation is complete. This procedure is described in
the EMC AutoStart Administrator’s Guide.
As the agent installation modifies Windows registry entries on the installation node,
you must install the agent on every node in the AutoStart domain. The AutoStart
agent installation requires the server name to be NetBIOS compliant. Server names
can contain multiple hyphens.
The AutoStart console can be installed on a node with or without an agent, and can
manage any domain as long as a TCP/IP network connection can be made to a
primary agent in the domain and the user connecting to the domain is configured as
an authorized user. Conversely, a node with an agent installed does not require a
console installed on it.
If AutoStart is installed on the servers previously, you must check and manually
remove the following user and system variables, if present:
◆ FT_DBDIR
◆ FT_DIR
◆ FT_DOMAIN
◆ FT_LNODE
◆ FTC_FT_DIR

24 EMC AutoStart Installation Guide

 Installing AutoStart on Windows

Follow the steps below to perform a fresh installation.

1. Log in as system administrator. If you log in as a different user, make sure that
account has adminstrative privileges on the server.
2. Locate the download folder and double-click EAS543_WIN_x86.exe or
EAS543_WIN_x64.exe.
A Window with „EMC AutoStart 5.4.3 is preparing the InstallShield Wizard for
the program setup process‰ appears, followed by the Welcome screen.
3. Click Next to continue.
The EMC License Agreement screen appears. Read this information carefully.
Click ÂI Accept the terms in the license agreement’ to continue the installation
process.
4. Click Next to continue. The Custom Setup screen appears.

Note: For custom path installations, do not use special characters such as "#" in the
installation directory, as this may cause the console window to hang.

5. Select the program features and components you want to install. Installing the
Filter Driver Based component requires a restart of the system after installation.
Click Next.
6. If Agent was chosen for installation, the Agent connect information screen
appears. Specify whether this is the first node to be installed in the AutoStart
domain.
Enter the name of the AutoStart domain and the base port number for AutoStart
domain communication. The default domain name is eas543 and port number is
8042.
Click Next to continue

Note: Domain names with special characters like hyphen (-), blank space, comma (,) are
not allowed. Only alphanumeric characters and underscores are allowed. The maximum
length of the domain name is eight characters.

7. If this is not the first agent in the domain, select that there is an existing node in
the domain. Follow the instructions on the window to specify a primary node
where there is a primary agent for the domain. The node name is the nodeÊs DNS
hostname.

Note: From second node onwards, give the NetBIOS name of the first node. Even if you
provide the fully qualified domain name, AutoStart automatically takes NetBIOS name of
the first node.

8. After entering the node name, click Next. The Mirroring Network Configuration
and Module Licensing screen appears.
9. Optionally, choose the IP address of the network that the node is to use for
mirroring. (Be sure to select this same network for the other machine that will pair
with this machine for mirroring.)
10. Select AutoStart Product or Module from the drop-down list box. The license key
information appears in the text box. By default the evaluation licence key
appears. If a license key is not available, then the evaluation licenses can be

Performing a fresh installation 25

Installing AutoStart on Windows

picked up from the drop-down list box. The corresponding keys also appear in
the License text box. These evaluation licenses are valid for a period of 90 days.
The base product license is mandatory for the AutoStart installation to continue.
11. Click Add. The Confirm Settings screen appears.
12. Check the settings and if satisfied, click Install. The Installing AutoStart screen
appears and begins copying the installation files.
13. The window Windows Security appears, displaying the message „Would you
like to install this device software?‰. Check the box which says „Always trust
software from EMC Corporation‰ and click Install to continue.
14. If Don’t Install is clicked, then a window appears, saying „User has selected not
to install the AutoStart Transport Driver. Some of the AutoStart feature(s) may not
work. Do you want to install the driver again?‰
„Click Yes to install. Click No to continue anyway.‰
If Yes is clicked, follow the procedure in step 14. If No is clicked, the VncTransport
driver will not be installed and indirectly some of the AutoStart feature(s) will not
work.
15. Click Finish when the InstallShield Wizard Completed screen appears.
16. If the Filter Driver Based component was chosen in step 6, a machine restart is
required. Select Yes in the next screen to restart the machine for the installation to
take effect. If the Filter Driver Based component is not chosen during installation,
the Agent and Backbone services will be started by the AutoStart installer.
Refer to Chapter 1, "Introduction," and Chapter 2, "Planning the AutoStart Domain,"
for initial information on AutoStart product and AutoStart domain.

Starting the agent

The Agent service automatically starts when the system is restarted. The agent can be
started by starting the ÂEMC AutoStart Agent Service’ service from the Services
Control Panel or start the agent from the command prompt using
net start <DomainName>_AGENT

Note: Use domain names that are consistent in case-sensitivity.

On the primary agent nodes, if the AutoStart Backbone process is not running,
performing either action starts the Backbone service. On a secondary agent node, the
AutoStart Backbone is installed, but does not need to run. Only primary agents
require the AutoStart Backbone service to run.
If the agent fails to start, then check the Windows application event log on that node.
There may be event information regarding the failure to start. The event source for
the Agent is named AutoStart. The Backbone event source is also named AutoStart.
AutoStart provides a startup parameter, -noisolationdetection. This parameter can
be supplied to override the agentÊs initial isolation detection check. This parameter
may be necessary if the set of IP addresses entered for isolation detection are incorrect
or when they are no longer accessible on the network.

26 EMC AutoStart Installation Guide

 Installing AutoStart on Windows

Stopping the agent

To shut down the agent and related processes, stop the ÂEMC AutoStart Agent
Service’ service from the Services Control Panel or from the command prompt by
issuing the following command net stop <DomainName>_AGENT.
Shutting down the agent in this way only shuts down the agent processes. Primary
agent nodes also run the AutoStart Backbone service, which does not shut down
automatically when the agent shuts down.
To shut down the Backbone and the Agent together, stop the ÂEMC AutoStart
BackboneService’ service from the Services Control Panel or from the command
prompt by typing the following command:
net stop <DomainName>_BACKBONE

How to establish a connection to the domain

Before you can use the console to manage an AutoStart domain, it must first be
connected to the AutoStart domain. By default, a console is connected to the domain
on the node where the console opens. To see other domains, you must connect to
them.
Follow the steps below to connect the console to a domain:
1. Launch the console from the Start button by selecting Start > Programs > EMC
AutoStart 5.4.3 > EMC AutoStart Console.
2. In the Domain Name text box, type the name of the domain that the console is
going to connect to.
3. In the Description text box, optionally type a brief description of the domain.
4. In the Node List text box, type the primary agents that the console should connect
to. Separate the primary agents using commas.
5. In the Domain Port text box, type the domain port number. The domain port
number is the base port number that was typed during agent installation.
6. Click Apply.
7. In the domain tree, right-click on the domain name and select Connect to
Domain.
Connection to the domain is established.
8. Click the Licensing/Security tab.
9. In the User Name text box, type the name of the users who are going to use the
console.
10. In the Domain/Node text box, type the Windows domain name or node names of
the machines running the console.

Note: When you are installing the first node, you setup the first user with administrative
privileges. So, this user gains access to every other additional node that gets added to the
domain. However, if your organization uses Windows Workgroups, after you setup your
first node with administrator privilege, additional nodes will not be recognized for that
first node. Follow the steps under "Setting up nodes in Windows workgroups" on page 28
as a workaround to correct this problem.

11. Select an access right level.

Performing a fresh installation 27

Installing AutoStart on Windows

Note: Select Administrator for the first user that you setup.

There are three levels of security:

a. User · Users can view objects, but cannot execute, modify, or delete objects.
b. Operator · Operators can view and execute objects, but cannot modify or
delete objects.
c. Administrator · Administrators can define, delete, and modify any object in
the domain.
12. In the Description text box, type a brief description of this user.
13. Click Add to add the user to the Security Manager Table.
14. Repeat steps 9 through 13 for each new user.
15. Click Apply.

Setting up nodes in Windows workgroups

To setup nodes in Windows workgroups, follow steps 1 through 3. Remember that
you should perform these steps only when working in a Windows Workgroup, not in
a Windows Domain:
1. From the console, highlight the domain in the tree-view pane.
2. Click the Licensing/Security tab.
3. In the Domain/Node field, enter a Â.’ (period) or enter LOCALSYSTEM.

Modifying an Program Maintenance screen-Modify option can be used to modify the program
existing installation features that are installed on your system.
For example, if you already have the AutoStart console installed on your system, and
now you only want to add the agent (and you want to keep the console installed),
then you can do so by selecting Modify on the Program Maintenance screen, and then
clicking Next to come to the Custom Setup screen. On the Custom Setup screen, do
not uncheck the console. If it is not checked, it removes the installed console from
your system. You should specify the required parameters for the installation to
continue.

28 EMC AutoStart Installation Guide

 Installing AutoStart on Windows

Performing a rolling upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a rolling
upgrade to move to the latest AutoStart 5.4.3 software. Rolling Upgrade is a method
in which the nodes in an AutoStart domain are upgraded one at a time. Upgrading a
cluster in a rolling fashion helps avoid application downtime and prevents any loss of
High Availability during the domain upgrade time. The AutoStart domain is fully
functional in the midst of a rolling upgrade. However the new functionality
introduced by the upgraded version will not be enabled until all the nodes in the
cluster have been upgraded. It is recommended that an upgraded console be used to
manage a cluster that is in the midst of a rolling upgrade.
The AutoStart 5.4.3 installer will create a backup copy of the previous configuration
under the new installation directory. The previous installation will be completely
removed and the configuration migrated.

Note: For installations running older supported product versions, an upgrade to 5.4.0 needs to
be done in a concurrent fashion first before they can be upgraded to 5.4.3.

WARNING
A rolling upgrade from AutoStart 5.3 SP5 or older installations is not supported.
Unpredictable behavior can result from running different AutoStart versions in older
AutoStart domains.

Note: Only a one level rolling upgrade is supported. A one level rolling upgrade is a
configuration wherein all the nodes in the cluster can only be at one of the two possible levels:
either at a particular lower software release version or at the upgraded higher software release
version.

Before you begin

AutoStart requires a reboot at the end of each version or service pack upgrade. An
appropriate service/maintenance window is required to upgrade an AutoStart node
to a newer software version.

Note: The upgrade to AutoStart 5.4.3 requires a reboot at the end of the upgrade procedure. All
Resource Groups that are online on the node to be upgraded, should be relocated to other valid
nodes or made offline before initiating an upgrade procedure. An appropriate
service/maintenance outage is required to upgrade any AutoStart node to AutoStart 5.4.3.

WARNING
Special precautions have to be taken if you are upgrading an existing module
instance of Exchange 2010. Refer to the section “DAG Node Maintenance Procedure”
under AutoStart Exchange Server 2010 module in the latest EMC AutoStart
Administrator’s Guide.

There are various methods to upgrade, which may help minimize the length of the
service/maintenance window. Contact EMC Technical Support for assistance with
planning the best method to upgrade an existing AutoStart environment.

Performing a rolling upgrade 29

Installing AutoStart on Windows

Installing the software on an upgrade

The following steps are for installing the AutoStart agent and console on a rolling
upgrade from 5.4.0 or higher to 5.4.3:
1. Ensure that the AutoStart agent on the node is running. This will help in
AutoStart taking a back up of the most recent configuration during the upgrade.
2. Log in as system administrator. If you log in as a different user, make sure that
account has adminstrative privileges on the server.
3. Locate the download folder and double-click EAS543_WIN_x86.exe or
EAS543_WIN_x64.exe.
4. A message box appears saying „This setup will perform an upgrade to AutoStart
5.4.3 Do you want to continue?‰. Click Yes to continue.
5. The Welcome screen appears. Click Next to continue.
6. The EMC License Agreement screen appears. Read this information carefully.
Select ÂI accept the terms in the license agreementÊ to continue the installation
process. Click Next to continue.
7. The Custom Setup screen appears. Select the program features you want to
install. Click Next.

Note: It is important that you upgrade all components that are already installed on the
machine.

8. Click Install at the Confirm Settings screen.

9. A message box appears saying „Upgrading to AutoStart 5.4.3 will uninstall the
current version and migrate the existing configuration to the new environment.
Are you sure you want to continue?‰. Click Yes to continue

Note: The above step will be a point of no return.

10. Click Finish in the InstallShield Wizard Completed screen.

11. Click Yes when prompted for restart.
After the node is rebooted, the AutoStart agent service will be up and the node re-
joins the AutoStart cluster. The node is now online and the user can relocate any
Resource Groups to the upgraded node.

Note: The Agent Release Version and the current Agent Operating Version of the nodes
will be displayed in the node properties tab of the AutoStart console.

12. Upgrade the nodes in the AutoStart domain one by one. Using the above
procedure all the nodes can be upgraded to 5.4.3 now or at a later point of time.
13. After all the nodes have been upgraded to 5.4.3, the Agent Operating Version
changes to 5.4.3 and all the new functionalities in the upgraded version will be
enabled.

30 EMC AutoStart Installation Guide

 Installing AutoStart on Windows

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

Performing a rolling upgrade 31

Installing AutoStart on Windows

Performing a concurrent upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a concurrent
upgrade to move to the latest AutoStart 5.4.3 software. For installations running older
supported product versions an upgrade to 5.4.0 needs to be done in a concurrent
fashion first before they can be upgraded to 5.4.3.
Concurrent Upgrade is a method in which all the agents in the AutoStart domain are
shutdown down and each node upgraded to the new software at the same time. The
cluster is not operational during the software upgrade period.
The AutoStart 5.4.3 installer will create a backup copy of the previous configuration
under the new installation directory. The previous installation will be completely
removed and the configuration migrated.

Note: For AutoStart installations running product versions 5.4.0 or higher, a rolling upgrade
can be used to minimize downtime. Refer section "Performing a rolling upgrade" on page 29.

Before you begin

AutoStart requires a reboot at the end of each version or service pack upgrade. An
appropriate service/maintenance window is required to upgrade an AutoStart
environment to a newer version. Upgrading an AutoStart environment requires that
every node be upgraded to the same version. When upgrading multiple nodes,
considerations must be made to prevent the nodes from running different versions at
the same time. Before rebooting the node, the user must ensure that all the nodes in
the cluster have been upgraded to AutoStart 5.4.3.

Note: The upgrade to AutoStart 5.4.3 requires a reboot at the end of the upgrade procedure. All
Resource Groups should be made offline before initiating an upgrade procedure. An
appropriate service/maintenance outage is required to upgrade any AutoStart domain to
AutoStart 5.4.3.

Note: Before upgrading to 5.4.3, make sure that you have a saved copy of the old version of the
AutoStart package. The old package will be needed in case you want to do a downgrade later.

WARNING
Unpredictable behavior can result from running different AutoStart versions in an
AutoStart Domain.

WARNING
Special precautions have to be taken if you are upgrading an existing module
instance of Exchange 2003 or Exchange 2007. Refer to the latest EMC AutoStart
Administrator’s Guide.

There are various methods to upgrade, which may help minimize the length of the
service/maintenance window. Contact EMC Technical Support for assistance with
planning the best method to upgrade an existing AutoStart environment.

32 EMC AutoStart Installation Guide

 Installing AutoStart on Windows

Install the software on an upgrade

The following steps are for installing the AutoStart agent and console on a
Concurrent (single step) upgrade from 5.4.0 onwards:
1. All Resource Groups should be made offline before initiating an upgrade
procedure.
2. Ensure that the primary and secondary AutoStart agents in the domain are
running. This will help in AutoStart taking a back up of the most recent
configuration during the upgrade.
3. Log in as system administrator. If you log in as a different user, make sure that
account has adminstrative privileges on the server.
4. Locate the download folder and double-click EAS543_WIN_x86.exe or
EAS543_WIN_x64.exe.
5. A message box appears saying „This setup will perform an upgrade to AutoStart
5.4.3 Do you want to continue?‰. Click Yes to continue.
6. The Welcome screen appears. Click Next to continue.
7. The EMC License Agreement screen appears. Read this information carefully.
Select ÂI accept the terms in the license agreementÊ to continue the installation
process. Click Next to continue.
8. The Custom Setup screen appears. Select the program features you want to
install. Click Next.

Note: It is important that you upgrade all components that are already installed on the
machine.

9. Click Install at the Confirm Settings screen.

10. A message box appears saying „Upgrading to AutoStart 5.4.3 will uninstall the
current version and migrate the existing configuration to the new environment.
Are you sure you want to continue?‰. Click Yes to continue

Note: The above step will be a point of no return.

11. Click Finish in the InstallShield Wizard Completed screen.

12. Click No when prompted for restart.
13. Upgrade the next node in the AutoStart domain.
14. Restart all the machines manually, one after the other when all nodes in the
cluster are upgraded.

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

Performing a concurrent upgrade 33

Installing AutoStart on Windows

Downgrading to the previous release

Downgrade steps
The objective of the downgrade procedure is to restore the node/domain back to a
state that existed prior to carrying out the 5.4.3 upgrade. The exact downgrade steps
to be used will vary based on the previous software version from which an upgrade
to 5.4.3 was carried out and the current state of the cluster. Check your domain
configuration and choose the appropriate downgrade strategy from one of the two
options below.

Note: Make sure that you have the old version of the AutoStart package. The package will need
to be installed again as part of the downgrade procedure.

Note: An appropriate service/maintenance outage is required to carry out the above

downgrade procedure.

Mixed version domain

A mixed version domain is one where some nodes have been upgraded to AutoStart
5.4.3, while the remaining nodes are at the older version and have not yet been
upgraded. The AutoStart domain is in the midst of a rolling upgrade. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher. One or all of the
upgraded nodes can be downgraded. The objective of the node downgrade is to
restore the node to the original software version but with the current active domain
configuration. A successful downgrade will restore the node to the old version but
there will be no change in the domain configuration.
To downgrade a 5.4.3 node in a mixed version domain, follow the below steps
1. All Resource Groups that are online on this node should be relocated to other
valid nodes or made offline before initiating the downgrade procedure.
2. Go to %FT_DIR%\bin and copy DowngradeNode.exe to any convenient location
outside the AutoStart install directory.

Note: The AutoStart install directory will be deleted when you uninstall AutoStart 5.4.3.
Hence it is essential to copy the DowngradeNode.exe to a location outside the AutoStart
install directory.

3. Run DowngradeNode.exe and you will be shown two options. Select the first
option, Backup the existing AutoStart configuration for a downgrade, to backup
the existing AutoStart configuration.
This will backup the current registry and other configuration files. By default
DowngradeNode.exe will backup the configuration in %APPDATA% folder.
User can give his own custom path for the same.

Note: In UAC enabled machines, the DowngradeNode.exe must be run as an

administrator.

4. Uninstall the existing AutoStart 5.4.3 and reboot the node.

34 EMC AutoStart Installation Guide

 Installing AutoStart on Windows

5. Install the old version of AutoStart on this node. The old version here refers to the
product version from which an upgrade was done and is the same version to
which the node is being downgraded to. While installing the old version, select
one of the existing nodes as a primary node. Make sure that you are clicking NO
when prompted for a reboot.
6. Again run the saved DowngradeNode.exe. Select the second option, Restore
from the backed up AutoStart configuration, to recover the previously backed
up AutoStart configuration.

Note: If you have given a custom path while backing up the configuration, you are
expected to give the same path during the recovery.

7. Reboot the node.

Note: Before you reboot the node, ensure that at least one primary agent is up and running.
When the newly downgraded node joins the cluster, the agent on the node retrieves the
current active domain configuration from the cluster.

WARNING
The newly downgraded node must never form the cluster; it should only join an
already up and running cluster. Doing otherwise will lead to a loss of
configuration data.

Fully upgraded domain

A fully upgraded domain is one where all the nodes have been upgraded to
AutoStart 5.4.3 and the domain is currently operating at 5.4.3 level. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher or higher.
All the upgraded nodes have to be downgraded at the same time. A downgrade
would restore all the nodes to the state at that "point in time" when the last node was
upgraded to 5.4.3. The objective of the downgrade procedure is to restore the domain
to the same configuration as that existed just prior to the last node getting upgraded
to 5.4.3.
The downgrade procedure involves the following steps.
1. Uninstall AutoStart 5.4.3 on all the nodes. Reboot the nodes when prompted.

Note: Before you uninstall AutoStart, make sure you have read the instructions refered to
in step 3. The exported def file on the last upgraded node needs to be backed up before
doing an actual uninstall.

2. Reinstall the old AutoStart version on all the nodes. Reboot the nodes when
prompted.
3. Restore the latest old configuration from the last upgraded node. The latest old
configuration refers to the backed up configuration on the last node upgraded to
5.4.3. For the exact steps on how to recover the old configuration using an
exported def file, refer "Restoring configuration using DEF file" on page 149.

Note: Different nodes may have been upgraded at different points of time. The installer
backs up the current configuration at the time of upgrade. So to have the latest
configuration, it is important to do a restore operation from the last upgraded node.

Downgrading to the previous release 35

Installing AutoStart on Windows

4. After the configuration has been successfully restored from the last upgraded
node, manually restart the agents on all other nodes. This ensures that the
downgraded agent versions are correctly propagated.

Note: An appropriate service/maintenance outage is required to carry out the above

downgrade procedure.

36 EMC AutoStart Installation Guide

 Installing AutoStart on Windows

Uninstalling AutoStart
Uninstalling the AutoStart software removes agent files: installed files, configuration
files, replicated database, and temporary files.

Note: Before you uninstall AutoStart, make sure that you backup any files you would like to
retain, as AutoStart uninstall removes all files, including log and configuration files.

To uninstall AutoStart:
◆ Remove the agent only
◆ Remove the console only
Follow the steps below to perform one of the procedures listed above:
1. Click Start on your machine.
2. Go to Settings > Control Panel.
3. Double-click Add/Remove Programs.
4. Select AutoStart 5.4.3 and click Change.
5. Click Next at the Welcome to the EMC AutoStart 5.4.3 Maintenance Installation
screen.
The Program Maintenance screen appears.

Note: If you have only the agent or console installed, you will come to the Program
Maintenance screen, which allows you to add either the console or agent, or remove
AutoStart from your machine.

The Remove option The Remove option on the Program Maintenance screen allows you to uninstall the
entire AutoStart product. You cannot do a partial uninstall using the Remove option.
However, if you want to perform a partial uninstall, then use "Uninstalling
AutoStart" on page 37.
Follow the Remove option steps mentioned below:
1. Select Remove on the Program Maintenance screen.
2. Click Next.
3. Click Remove at the Remove the Program screen.
If you selected to remove any program features, the InstallShield Wizard
completes the uninstall process.

Note: Uninstalling the AutoStart agent or driver requires a system reboot.

4. Click Finish at the InstallShield Wizard Completed screen.

5. At the dialog box, click Yes to restart your computer.

The Modify option In addition to installing either the agent or the console (the component not previously
installed), the Modify option lets you do either a partial or a complete uninstallation:
1. At the Program Maintenance screen, select Modify and click Next.

Uninstalling AutoStart 37
Installing AutoStart on Windows

2. At the Custom Setup screen, choose the component to uninstall by clicking on the
pull-down arrow and highlighting the red X followed by This feature will not be
available. You can do this for either the agent or console or both the agent and the
console.

Note: Uninstalling the AutoStart agent or driver requires a system reboot.

3. Click Next.
4. Click Remove in the Remove the Program screen.
5. Click Finish in the InstallShield Wizard Completed screen.

Note: If needed, this product may install required Microsoft VC redistributable side-by-side
assemblies. In the event that the product is uninstalled, any installed Microsoft VC
redistributable side-by-side assemblies will remain.

Note: Installing AutoStart on Windows creates a system event log file. This log file can be
found at C:\Windows\System32\Winevt\Logs\AutoStart.evtx. Uninstalling AutoStart does
not delete this file since it is a system generated file. This means events from all AutoStart
installation instances would remain unless the file is deleted. Delete the log file if you don’t
want events from previous installations to show up in Windows Event Viewer.

38 EMC AutoStart Installation Guide

 Installing AutoStart on Windows

Uninstalling AutoStart 39
Installing AutoStart on Windows

40 EMC AutoStart Installation Guide

 4
Invisible Body Tag

Installing AutoStart on
Solaris

Before installing AutoStart, refer to Chapter 2, "Planning the AutoStart Domain."

This chapter explains how to install AutoStart on Solaris. It contains the following
sections:
◆ AutoStart installation......................................................................... 42
◆ System requirements ......................................................................... 43
◆ Performing a fresh installation......................................................... 44
◆ Performing a rolling upgrade........................................................... 50
◆ Performing a concurrent upgrade ................................................... 54
◆ Downgrading to the previous release ............................................. 57
◆ Uninstalling AutoStart ...................................................................... 60

Installing AutoStart on Solaris 41

Installing AutoStart on Solaris

AutoStart installation
There are two components in the AutoStart installation, the agent and the console.
AutoStart agents monitor and manage nodes and processes in the domain. Resource
objects such as managed IP addresses, node aliases, and data sources are managed as
well. Primary agents execute rules, maintain replicated copies of the AutoStart
database, and monitor other agents in the domain.
The AutoStart console is a graphical administrative tool which accesses information
from an agent. It also initiates operations on an agent, enabling management of the
domain from a single location.
When installing both an agent and the console on the same node, install the agent
first, followed by the console. If an agent is already installed when the console
installation takes place, information about the domain is passed to the console
automatically.
The first three nodes installed in the domain are primary agents. Subsequent nodes
are installed as secondary agents. Secondary agents can be promoted to primary
agents after installation is complete.
When installing subsequent agents, the name of the node must be registered in the
console before the new agent can be brought online.

42 EMC AutoStart Installation Guide

 Installing AutoStart on Solaris

System requirements
Note: For most up-to-date information on System requirements, Operating systems, Console
requirements, and Service Pack versions, refer to EMC AutoStart Compatibility Guide
available on the Powerlink web site (http://Powerlink.emc.com)

Note: Before you install AutoStart, you must install the Curses library on your machine.

To run AutoStart, each Solaris machine in the domain must meet the following
requirements:
◆ Minimum of 250 MB free disk space.
◆ The console requires Motif 2.1 and X11R5 releases. The console is officially
supported to run under the window manager MWM (the Motif Window
Manager) on Solaris.

Network The following are the requirements of Network Connections:

Connections A minimum of two network connections for cluster communication:
◆ One NIC for the production network and AutoStart domain line.
◆ One NIC for a private network used as an AutoStart domain line.

Note: For more information, refer to EMC AutoStart Administrator's Guide available on
the Powerlink web site (http://Powerlink.emc.com

System requirements 43
Installing AutoStart on Solaris

Performing a fresh installation

The following sections cover a fresh installation for the agent and console. For an
upgrade installation, refer to "Performing a rolling upgrade" on page 50 and
"Performing a concurrent upgrade" on page 54.

Note: If the console is to run on a node with an agent installed, EMC recommends that the base
directory for the console matches the install directory for the agent.

Installing the agent For Solaris nodes, the files must be extracted from the .tar file, if applicable, and
and console unpacked from the distribution media before installation can take place:
1. At the # prompt, type:
./install.sh
2. Press Enter.
The following text appears:
We will be checking if you have any AutoStart packages
installed on your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or
higher
- If you have a version of AutoStart prior to 5.4.0, you must
either upgrade first to AutoStart 5.4.0, before upgrading to
AutoStart 5.4.3. or Remove the older version completely and
then install AutoStart 5.4.3.
The following message appears:
Checking if the AutoStart console package is installed ...
AutoStart 5.4 console is not installed.
Checking if the AutoStart agent package is installed ...
AutoStart 5.4 agent is not installed.
When the system determines that you are doing a fresh install, you will see this
message:
Would you like to install AutoStart 5.4.3 agent? (y/n)
3. Type y and press Enter.
The following message appears:
you have chosen to install AutoStart 5.4.3 agent
Path to install EMC AutoStart 5.4.3 [/opt/EMCas543]: [?]
4. Type the path and press Enter. You will see the message
Processing package instance <EMCasa> from </path>
The EMC License Agreement screen appears. Read this information carefully.
5. If you accept the license terms, type y and press Enter.
The Agent installation starts and you can see the message,
Installing EMC AutoStart Agent as <EMCasa>
When the installation is complete it shows,

44 EMC AutoStart Installation Guide

 Installing AutoStart on Solaris

AutoStart agent installation is successful.

The system installs the agent. Upon completion, you are prompted:
Would you like to install AutoStart 5.4.3 console? (y/n)
6. Type y and press Enter.
The following message appears:
you have decided to install the AutoStart 5.4.3 console
Path to install EMC AutoStart 5.4.3 [/opt/EMCas543]: [?]
7. Type the path and press Enter. You will see the message
Processing package instance <EMCasa> from </path>
The EMC License Agreement screen appears. Read this information carefully.
8. If you accept the license terms, type y and press Enter.
The console installation starts and you can see the message,
Installing EMC AutoStart Management Console as <EMCasmc>
When the installation is complete it shows,
AutoStart console installation is successful.

Agent setup
To install the AutoStart 5.4.3 agent software (Bourne Shell):
1. Log in as root.
2. Set the FT_DIR environment variable to the directory selected when the agent
was installed:
FT_DIR=install-directory-path
export FT_DIR
Several AutoStart programs and scripts reference the FT_DIR environment
variable, which must be set to the pathname of the AutoStart software installation
directory. While installation requires only that the variable is set, for normal
operation the FT_DIR environment variable should always be set in the .profile
file.

Note: Multiple domains are not permitted on a single node running from a single
$FT_DIR. Each domain installation must run from a unique $FT_DIR.

3. Set the FT_DOMAIN environment variable to the AutoStart domain name. Type:
FT_DOMAIN=myDomain
export FT_DOMAIN

Note: The domain names are case-sensitive. Once the FT_DOMAIN environment variable is
set, there is no need to specify the domain name when starting the agent. Each AutoStart
domain must have a different name.

4. Change the working directory to the bin directory located under $FT_DIR. Type:
cd $FT_DIR/bin

Performing a fresh installation 45

Installing AutoStart on Solaris

5. Check the installation by running the verify_install script. The script verifies the
installation of the agent files and directories.
6. Execute ft_setup. At the # prompt, type:
./ft_setup
7. The following message appears:
Enter the name of the domain:
Type the domain name.
Domain names must be eight characters or less and they are case-sensitive.
8. The script prompts for the name of a primary agent node:
Enter the name of Primary Agent Node:
Use simple node names to specify the primary agent node. Do not specify a
nodeÊs DNS name extension or an IP address.
And you can see the message, Performing a primary node configuration
9. Next the user is asked, Specify the first of the 4 port numbers:
Enter the default port number, [8042]. The following message appears:
Ports 8042, 8043, 8044 and 8045 will be used.
10. Supply the network port numbers required for agent process communication. The
numbers can be generated either manually or automatically.
Agent processes communicate with each other using all four TCP/IP ports. The
port numbers that are selected must be available and identical on all nodes in the
domain.
The ft_setup script generates the port numbers and runs to completion.
To automatically generate the ports, ft_setup looks for unused TCP/IP port
numbers beginning at 8042. If available, it uses ports 8042 through 8045.
When manually specifying the port, make certain that the selected port number
and the next three port numbers in sequence are available on all primary agent
nodes before starting the agent.

Note: The ft_setup script cannot guarantee that the ports chosen either manually or
automatically are not reserved for a process that is currently not running, nor can it verify
that the ports are available on all other primary nodes.

11. If this is the first node in the domain, AutoStart prompts for the license key. Enter
the license key and press Enter.
12. To receive email notifications from AutoStart, enter the name of the SMTP
hostname. Otherwise, leave this field blank. This setting can be modified later.
Press Enter.
13. When the installation is complete, you can see the message:
Installation for this node is complete.
To start the Agent run the "ft_startup" command.
14. Execute ft_startup. At the # prompt, type:
./ft_startup
15. The following message appears:

46 EMC AutoStart Installation Guide

 Installing AutoStart on Solaris

Starting Backbone......
Backbone started successfully.
Starting Agent....
Agent started successfully.
The Agent setup is completed successfully.

Environment variable files

During setup, AutoStart creates two files in the $FT_DIR/bin directory: envsh and
envcsh. These can be invoked using the ./envsh command to add the AutoStart
related environment variables to the local environment.

Starting the agent

After installing and configuring the AutoStart agent, it must be started. To add a
primary agent node, first install the agent as a secondary, and then promote it. All
agent node names must be added to the replicated database before the agent can be
run:
1. If the current node is not the first node in the domain, from a running node ensure
that the node name has been added to the replicated database.
2. To start an agent on a node, use the ft_startup command. The command is found in
the $FT_DIR/bin directory. If $FT_DIR/bin is added to the path, the command runs
from any directory. Enter:
cd $FT_DIR/bin
./ft_startup
The ft_startup command has the following syntax and options.
ft_startup [-d domain_name][-x][-h]

The command options to ft_startup are summarized below:

a. Use the -d domain-name option to specify the domain. The -d argument is
optional if the FT_DOMAIN environment variable is set. If the -d argument and
the FT_DOMAIN environment variable are both specified, then the domain
name following the -d argument takes precedence.
b. Use the -x (xterm) option to tell ft_startup to start the agent processes in
their own xterm windows for debugging or to become familiar with
AutoStart. The DISPLAY environment variable must be set to use this option.
When tracing is turned on and appropriately configured, all tracing output is
displayed directly to stdout of the respective agent process. Therefore, to be
able to view the destination of the output, EMC recommends that each agent
process is brought up in its own window with the -x option to ft_startup.
c. Use the -h option to display the help for ft_startup.
d. To verify that an agent is running on a node, run the console from any node in
the domain and display the Node Console, or issue the CLI command
listNodes.
The agent exits if the node on which it is running has not been previously defined in
the AutoStart replicated database. All secondary agents must be added to the domain
using the console or ftcli.

Performing a fresh installation 47

Installing AutoStart on Solaris

EMC recommends adding the following commands to the system startup file for each
node:
FT_DOMAIN=domain-name
export FT_DOMAIN
FT_DIR=install-directory-path
export FT_DIR
${FT_DIR}/bin/ft_startup
This command starts the agent on the local node. Because AutoStart depends on
other system utilities, this command should be run late in the startup procedure
when the operating system and network are fully initialized.
The environment variable FT_DIR must be set prior to running any of the AutoStart
programs and scripts. This variable allows AutoStart to find various configuration,
log, and database files, as well as other utility programs.
Run the ft_startup command from each node in the domain to start an agent on the
node. If this is the first time an agent has ever run on the node and the node has been
designated in the ft_setup script to run a primary agent, an instance of the replicated
database is created on the node in a directory named as follows:
$FT_DIR/domain-name_node-name.

Startup parameters
AutoStart provides startup parameters that can be used to modify the default
behavior of the agent. These parameters should be used with care:
◆ -noisolationdetection · Overrides the agentÊs initial isolation detection
check. This parameter may be necessary if the set of IP addresses entered for
isolation detection are incorrect or are no longer accessible on the network.
◆ -realtime · By default, the AutoStart agent on Solaris nodes runs at the
timeshare priority. This parameter allows the AutoStart backbone and agent to
run at the higher, realtime priority on some Solaris systems. This parameter
should only be used if failures are occurring because AutoStart cannot get the
necessary CPU cycles.

Stopping the agent

The shutdown procedure should be used to ensure that no data is lost. By properly
shutting down the agent, the agent enters the shut down state rather than the failed
state.
To shut down a primary agent on a node, use the ft_shutdown command. The
command is found in the $FT_DIR/bin directory. If $FT_DIR/bin is added to the
path, the command runs from any directory. Enter:
cd $FT_DIR/bin
./ft_shutdown
The ft_shutdown command has the following syntax and options:
ft_shutdown [-backbone]

The argument to ft_shutdown is summarized below.

Use the -backbone option to tell ft_shutdown to stop both the agent processes and the
AutoStart backbone from the domain. By default the ft_shutdown command only
stops the agent processes on the node.

48 EMC AutoStart Installation Guide

 Installing AutoStart on Solaris

The FT_DOMAIN environment variable must be set before using this command.

Installing the console

The console can be installed on any network node, with or without a primary or
secondary agent.
Refer to "Installing the agent and console" on page 44 for the installation steps.

How to establish a connection to the domain

Before the console can be used to manage an AutoStart domain, it must first be
connected to the AutoStart domain.
Follow the steps below to connect the console to a domain:
1. Launch the console by entering:
installDir/console/bin/ftconsole
2. If you need to create a new domain at this time, follow step a through step e
below, or proceed to step 3:
a. In the Domain Name text box, enter the name of the domain that the console
is going to connect to.
b. In the Description text box, optionally enter a brief description of the domain.
c. In the Node List text box, enter the primary agents that the console should
connect to. Separate the primary agents using commas.
d. In the Domain Port text box, enter the domain port number. The domain port
number is the base port number that was entered during agent installation.
e. Click Apply.
3. In the domain tree, right-click on the domain name and select Connect to
Domain. Connection to the domain is established.
4. Click the Licensing Security tab.
5. In the User Name text box, enter the name of the users who are going to use the
console.
6. In the Domain/Node text box, enter the domain name or node names of the
machines running the console. The wildcard „*‰ can be used to gain access to all
nodes.
7. Select an access right level.
There are three levels of security: User, Operator, and Administrator:
a. User · Users can view objects, but cannot execute, modify, or delete objects.
b. Operator · Operators can view and execute objects, but cannot modify or
delete objects.
c. Administrator · Administrators can define, delete, and modify any object in
the domain.
8. In the Description text box, enter a brief description of this user.
9. Click Add to add the user to the Security Manager Table.
10. Repeat steps 5 through 9 for each new user.

Performing a fresh installation 49

Installing AutoStart on Solaris

Performing a rolling upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a rolling
upgrade to move to the latest AutoStart 5.4.3 software. Rolling Upgrade is a method
in which the nodes in an AutoStart domain are upgraded one at a time. Upgrading a
cluster in a rolling fashion helps avoid application downtime and prevents any loss of
High Availability during the domain upgrade time. The AutoStart domain is fully
functional in the midst of a rolling upgrade. However the new functionality
introduced by the upgraded version will not be enabled until all the nodes in the
cluster have been upgraded. It is recommended that an upgraded console be used to
manage a cluster that is in the midst of a rolling upgrade.

Note: For installations running older supported product versions, an upgrade to 5.4.0 needs to
be done in a concurrent fashion first before they can be upgraded to 5.4.3.

WARNING
A rolling upgrade from AutoStart 5.3 SP5 or older installations is not supported.
Unpredictable behavior can result from running different AutoStart versions in older
AutoStart domains.

Note: Only a one level rolling upgrade is supported. A one level rolling upgrade is a
configuration wherein all the nodes in the cluster can only be at one of the two possible levels:
either at a particular lower software release version or at the upgraded higher software release
version.

Before you begin

During the AutoStart upgrade process, the applications and resources running on the
node do not need to be shut down, thus requiring no application downtime.
However, for the short period of time that the agent is down during the upgrade,
AutoStart cannot monitor the applications and resources. If High availability of the
application is important then relocate the resource groups to other valid nodes before
initiating the upgrade.
Upgrading Solaris nodes requires a number of steps. This procedure ensures that a
new installation does not overwrite the previous one, so that the upgrade can
progress normally. The AutoStart installer will create a backup copy of the previous
configuration under the AutoStart installation directory.

Note: The upgrade to AutoStart 5.4.3 requires a restart of the agent at the end of the upgrade
procedure. An appropriate service/maintenance outage is required to upgrade any AutoStart
node to AutoStart 5.4.3.

Unpacking the software

Follow the steps below to unpack the AutoStart software:
1. Log in as root.

50 EMC AutoStart Installation Guide

 Installing AutoStart on Solaris

2. Download the software package. You should see the EAS543_SOLARIS.tar.Z file
in your directory.
3. Uncompress and extract the EAS543_SOLARIS.tar.Z file.

Installing the software on an upgrade

Follow the steps below to install the AutoStart agent and console on an upgrade:
1. Set the environment variables:
d. Set the FT_DIR environment variable to the directory selected when the agent
was installed. Type:
FT_DIR=AutoStart Installed directory
export FT_DIR

e. Set the FT_DOMAIN environment variable to the AutoStart domain name.

Type:
FT_DOMAIN=myDomain
export FT_DOMAIN
2. At the # prompt, type:
./install.sh
3. Press Enter. The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must either
upgrade first to AutoStart 5.4.0, before upgrading to AutoStart
5.4.3. or Remove the older version completely and then install
AutoStart 5.4.3.

When the software finds a previous agent installed on the system, it asks:
Would you like to upgrade the agent to AutoStart 5.4.3? (y/n)

4. Type y to upgrade to AutoStart 5.4.3. The following message appears:

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Do you want to continue with upgrade (y/n) [y]:

5. Type y to continue with the upgrade process. The following message appears:
Saving current Autostart agent configuration...

The operation causes EMC AutoStart to shut down and restart:

Continue? (y/n).
6. Type y and press Enter.

Note: This will be a point of no return.

Messages such as the following appear:

Shutting down the Agent...
Agent shutdown successfully.

Shutting down the Backbone...

Shutting down any active process of Autostart agent ...

Performing a rolling upgrade 51

Installing AutoStart on Solaris

Stopping EMC AutoStart daemons

EMC AutoStart package successfully removed.

FT_DIR=/opt/EMCas542 will now be removed.

Installing AutoStart 5.4.3 agent...

Restoring current Autostart agent configuration ...

Please set your FT_DIR variable to new /opt/EMCas543

EMC Autostart 5.4.3 agent is installed.

Agent upgrade successful.

EMC Autostart console will be upgraded to 5.4.3 .

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Saving current Autostart console configuration...

Installing AutoStart 5.4.3 console...

Restoring current Autostart console configuration...

Console upgrade successful

7. When the Installation is complete, the next question appears:

Restart the AutoStart Agent? (y/n).
8. Type y and press Enter. Output similar to the following appears:
About to start AutoStart. Please wait.
EMC AutoStart startup script.

Setting environment from /opt/EMCas543/config/agent_env.Solaris

Starting agent for domain Sample_Domain

Starting Backbone...
...
Backbone started successfully.

Starting Agent...

Agent started successfully.

9. Manually set FT_DIR to the new value.

10. After the AutoStart agent service is up, the node re- joins the AutoStart cluster.
The node is now online and the user can relocate any Resource Groups to the
upgraded node.

Note: The Agent Release Version and the current Agent Operating Version of the nodes
will be displayed in the node properties tab of the AutoStart console.

11. Upgrade the nodes in the AutoStart domain one by one. Using the above
procedure all the nodes can be upgraded to 5.4.3 now or at a later point of time.
12. After all the nodes have been upgraded to 5.4.3, the Agent Operating Version
changes to 5.4.3 and all the new functionalities in the upgraded version will be
enabled.

Note: The newly upgraded AutoStart 5.4.3 is installed under the default path /opt/EMCas543
regardless of the prior install location.

52 EMC AutoStart Installation Guide

 Installing AutoStart on Solaris

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

Performing a rolling upgrade 53

Installing AutoStart on Solaris

Performing a concurrent upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a concurrent
upgrade to move to the latest AutoStart 5.4.3 software. For installations running older
supported product versions an upgrade to 5.4.0 needs to be done in a concurrent
fashion first before they can be upgraded to 5.4.3.
Concurrent Upgrade is a method in which all the agents in the AutoStart domain are
shutdown down and each node upgraded to the new software at the same time. The
cluster is not operational during the software upgrade period.

Note: For AutoStart installations running product versions 5.4.0 or higher, a rolling upgrade
can be used to minimize downtime. Refer to the section "Performing a rolling upgrade" on
page 50.

Before you begin

To upgrade AutoStart from a previous release, each node in the AutoStart domain
must be upgraded. To upgrade a node, shut down the agent and then perform the
upgrade. Upgrade all nodes in the domain before restarting the upgraded agents. An
upgraded agent will not start while nodes running the older agent are still active.
During the AutoStart upgrade process, the applications and resources running on the
node do not need to be shut down, thus requiring no application downtime.
However, for the short period of time that the agent is down during the upgrade,
AutoStart cannot monitor the applications and resources. If an application fails
during the upgrade, AutoStart will detect the failure when the agent comes back
online and reacts accordingly.
Upgrading Solaris nodes requires a number of steps. This procedure ensures that a
new installation does not overwrite the previous one, so that the upgrade can
progress normally.

Note: The upgrade to AutoStart 5.4.3 requires restart of the agent at the end of the upgrade
procedure. An appropriate service/maintenance outage is required to upgrade any AutoStart
domain to AutoStart 5.4.3.

Note: Before upgrading to 5.4.3, make sure that you have a saved copy of the old version of the
AutoStart package. The old package will be needed in case you want to do a downgrade later.

Unpacking the software

Follow the steps below to unpack the AutoStart software:
1. Log in as root.
2. Download the software package. You should see the EAS543_SOLARIS.tar.Z file
in your directory.
3. Uncompress and extract the EAS543_SOLARIS.tar.Z file.

54 EMC AutoStart Installation Guide

 Installing AutoStart on Solaris

Installing the software on an upgrade

Follow the steps below to install the AutoStart agent and console on an upgrade:
1. Set the environment variables:
a. Set the FT_DIR environment variable to the directory selected when the agent
was installed. Type:
FT_DIR=AutoStart Installed directory
export FT_DIR

b. Set the FT_DOMAIN environment variable to the AutoStart domain name.

Type:
FT_DOMAIN=myDomain
export FT_DOMAIN
2. At the # prompt type the following command. This generates a configuration
backup.
$FT_DIR/bin/ftcli -d $FT_DOMAIN -cmd “backup”

3. Shut down the AutoStart agent and any open console.

4. At the # prompt, type:
./install.sh
5. Press Enter. The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must either
upgrade first to AutoStart 5.4.0, before upgrading to AutoStart
5.4.3. or Remove the older version completely and then install
AutoStart 5.4.3.

When the software finds a previous agent installed on the system, it asks:
Would you like to upgrade the agent to AutoStart 5.4.3? (y/n)

6. Type y to upgrade to AutoStart 5.4.3. The following message appears:

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Do you want to continue with upgrade (y/n) [y]:

7. Type y to continue with the upgrade process. The following message appears:
Saving current Autostart agent configuration...

The operation causes EMC AutoStart to shut down and restart:

Continue? (y/n).
8. Type y and press Enter.

Note: This will be a point of no return.

Messages such as the following appear:

Shutting down the Agent...
Agent shutdown successfully.

Shutting down the Backbone...

Performing a concurrent upgrade 55

Installing AutoStart on Solaris

Shutting down any active process of Autostart agent ...

Stopping EMC AutoStart daemons

EMC AutoStart package successfully removed.

FT_DIR=/opt/EMCas542 will now be removed.

Installing AutoStart 5.4.3 agent...

Restoring current Autostart agent configuration ...

Please set your FT_DIR variable to new /opt/EMCas543

EMC Autostart 5.4.3 agent is installed.

Agent upgrade successful.

EMC Autostart console will be upgraded to 5.4.3 .

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Saving current Autostart console configuration...

Installing AutoStart 5.4.3 console...

Restoring current Autostart console configuration...

Console upgrade successful

9. When the Installation is complete, the next question appears:

Restart the AutoStart Agent? (y/n).
10. Type n and press Enter.
11. After all nodes in the cluster have been upgraded manually restart the Agent one
after the other. The upgrade is only valid for the current node; repeat this
procedure for every node in the domain.

Note: The newly upgraded AutoStart 5.4.3 is installed under the default path /opt/EMCas543
regardless of the prior install location.

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

56 EMC AutoStart Installation Guide

 Installing AutoStart on Solaris

Downgrading to the previous release

Downgrade steps
The objective of the downgrade procedure is to restore the node/domain back to a
state that existed prior to carrying out the 5.4.3 upgrade. The exact downgrade steps
to be used will vary based on the previous software version from which an upgrade
to 5.4.3 was carried out and the current state of the cluster. Check your domain
configuration and choose the appropriate downgrade strategy from one of the two
options below.

Note: Make sure that you have the old version of the AutoStart package. The package will need
to be installed again as part of the downgrade procedure.

Note: An appropriate service/maintenance outage is required to carry out the above

downgrade procedure.

Mixed version domain

A mixed version domain is one where some nodes have been upgraded to AutoStart
5.4.3, while the remaining nodes are at the older version and have not yet been
upgraded. The AutoStart domain is in the midst of a rolling upgrade. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher. One or all of the
upgraded nodes can be downgraded. The objective of the node downgrade is to
restore the node to the original software version but with the current active domain
configuration. A successful downgrade will restore the node to the old version but
there will be no change in the domain configuration.
To downgrade a 5.4.3 agent in a mixed version domain, follow the below steps
1. Uninstall AutoStart 5.4.3 on the node you want to downgrade.
2. Install a previous version of AutoStart Agent on the node.
3. Run ft_setup and provide one of the primary agent node name that was not
upgraded to 5.4.3 for the Primary Agent Node prompt.
4. Start the AutoStart agent
5. Apply any AutoStart Hotfixes if necessary.
6. Repeat steps one through five for all the nodes to be downgraded.

Note: Before you restart the agent, ensure that at least one primary agent is up and
running. When the newly downgraded node joins the cluster, the agent on the node
retrieves the current active domain configuration from the cluster.

WARNING
The newly downgraded agent must never form the cluster; it should only join an
already up and running cluster. Doing otherwise will lead to a loss of
configuration data.

Downgrading to the previous release 57

Installing AutoStart on Solaris

Fully upgraded domain

A fully upgraded domain is one where all the nodes have been upgraded to
AutoStart 5.4.3 and the domain is currently operating at 5.4.3 level. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher.
All the upgraded nodes have to be downgraded at the same time. A downgrade
would restore all the nodes to the state at that "point in time" when the last node was
upgraded to 5.4.3. The objective of the downgrade procedure is to restore the domain
to the same configuration as that existed just prior to the last node getting upgraded
to 5.4.3. The downgrade procedure involves downgrading to the old AutoStart
version and restoring the latest old configuration. The latest old configuration refers
to the backed up configuration on the last node upgraded to 5.4.3.
To downgrade a 5.4.3 AutoStart domain, follow the below steps:
1. Take all Resource Groups offline and shutdown the agents on all the nodes.
2. One the node that was upgrade last, copy the backed up Domain configuration
files to a location outside $FT_DIR folder using the following command:
# cp -Rf $FT_DIR/backup /backup_prev_ver

3. Save all license files.

4. Uninstall AutoStart 5.4.3 on the node.
5. Install a previous version of AutoStart Agent on the node.
6. Run ft_setup and start the AutoStart agent
7. Apply any AutoStart Hotfixes if necessary.
8. Repeat steps three through six for all the remaining nodes.
9. On the node that was upgraded last, restore the configuration backed up in step
two.
To restore the configuration you can use either AutoStart Console or AutoStart
ftcli.
Using AutoStart Console:
1. Input AutoStart licenses by choosing the appropriate product from the
AutoStart console dropdown list under the Licensing/Security tab.
2. Configure settings under Mirroring and Failure Detection Setting. Ensure
that all the mirroring and domain line settings are the same as before.
3. Select the required domain in the AutoStart console and import the
backup.def file located under /backup_prev_ver.
Using AutoStart ftcli:
1. Import the licenses saved earlier using the following ftcli command:
addLicense -product=<product_name> <License>

2. Import backup.def located under backup/backup_prev_ver using the following

ftcli command:
import /backup_prev_ver/backup.def -skipfail

58 EMC AutoStart Installation Guide

 Installing AutoStart on Solaris

WARNING
If the previous setup had an EMC mirroring data source, that data source would be
created afresh and hence a complete sync would be required when attached. This
would be done automatically when the RG is brought online. So a longer
maintenance window would be required. If a SRDF or a MirrorView data source was
used, a discovery would be performed during the import operation of the def file.

Downgrading to the previous release 59

Installing AutoStart on Solaris

Uninstalling AutoStart
Uninstalling the AutoStart software removes the installed files, configuration files,
replicated database files, and any temporary files AutoStart writes to the node.

Note: Before you uninstall AutoStart, make sure that you backup any files you would like to
retain, as AutoStart uninstall removes all files, including log and configuration files.

AutoStart can be uninstalled from a Solaris node using the supplied ft_uninstall
script found in the $FT_DIR/bin. This script removes all the files generated by the
AutoStart agent. Once completed, the rest of the files placed on the machine are
removed as a package.
EMC recommends that you invoke the ft_uninstall script to uninstall the agent
software. The FT_DIR and FT_DOMAIN environment variables must be set in order to
invoke the script. Follow the steps below:
1. At the # prompt, type:
./ft_uninstall
2. Press Enter.
3. Click y at the question to remove the domain.
4. Click y at the question to remove EMC AutoStart from your machine.
5. Click y at the question to remove the agent package.
6. Click y at the question to remove the console package.
You receive the message that AutoStart was removed successfully.
The script removes any files created by the operation of the agent processes,
including database, configuration, and temporary files. Once database, configuration,
and temporary files are removed, the software files can be removed.
You can also use the package remove application. Ensure that the agent for the
domain to be removed is no longer running when executing the command. Ensure
that the agent is no longer running by entering ft_shutdown -backbone at the
command prompt. If the FT_DIR and FT_DOMAIN environment variables are not
set, provide a full path to stop the backbone:
1. Enter the package remove command: pkgrm
If multiple packages are included on the machine, a long list of package numbers
are shown. Scroll through the list to view the components. Press Ctrl-D to escape
from the list and go directly to the prompt.
2. Enter the package numbers for removal, separated by spaces.
3. For each package, the application prompts for verification before the package is
removed. Enter y to verify.
4. You must have super user (su) access to remove the package. If you are logged in
as an su user, enter y.
If the agent or console is still running, the packages are not removed correctly.

60 EMC AutoStart Installation Guide

 5
Invisible Body Tag

Installing AutoStart on
Linux

Before installing AutoStart, refer to Chapter 2, "Planning the AutoStart Domain."

This chapter explains how to install AutoStart on SUSE Linux, Red Hat Linux and
Oracle Enterprise Linux (OEL). It contains the following sections:
◆ AutoStart installation......................................................................... 62
◆ System requirements ......................................................................... 63
◆ Performing a fresh installation......................................................... 64
◆ Performing a rolling upgrade........................................................... 70
◆ Performing a concurrent upgrade ................................................... 73
◆ Downgrading to the previous release ............................................. 76
◆ Uninstalling AutoStart ...................................................................... 79

Installing AutoStart on Linux 61

Installing AutoStart on Linux

AutoStart installation
There are two components in the AutoStart installation, the agent and the console.
AutoStart agents monitor and manage nodes and processes in the domain. Resource
objects such as managed IP addresses, node aliases, and data sources are managed as
well. Primary agents execute rules, maintain replicated copies of the AutoStart
database, and monitor other agents in the domain.
The AutoStart console is a graphical administrative tool which accesses information
from an agent. It also initiates operations on an agent, enabling management of the
domain from a single location.
When installing both an agent and the console on the same node, install the agent
first, followed by the console. If an agent is already installed when the console
installation takes place, information about the domain is passed to the console
automatically.
The first three nodes installed in the domain are primary agents. Subsequent nodes
are installed as secondary agents. Secondary agents can be promoted to primary
agents after installation is complete.
When installing subsequent agents, the name of the node must be registered in the
console before the new agent can be brought online.

62 EMC AutoStart Installation Guide

 Installing AutoStart on Linux

System requirements
Note: For most up-to-date information on System requirements, Operating systems, Console
requirements, and Service Pack versions, refer to EMC AutoStart Compatibility Guide
available on the Powerlink web site (http://Powerlink.emc.com)

To run AutoStart, each SUSE Linux, Red Hat Linux or Oracle Enterprise Linux (OEL)
machine in the domain must meet the following requirements:
◆ Minimum of 250 MB free disk space.
◆ The console requires Motif 2.1 and X11R5 releases. The console is officially
supported to run under the window manager MWM (the Motif Window
Manager) on SUSE Linux, Red Hat Linux and Oracle Enterprise Linux (OEL).
◆ AutoStart 5.4.1 requires 32-bit libstdc++.so.6 shared library, which isnÊt part of the
default system install on certain 64-bit Linux platforms. Install the 32-bit
libstdc++.so.6 shared library manually if it is not present.

Network The following are the requirements of Network Connections:

Connections A minimum of two network connections for cluster communication:
◆ One NIC for the production network and AutoStart domain line.
◆ One NIC for a private network used as an AutoStart domain line.

Note: For more information, refer to the EMC AutoStart Administrator's Guide available
on the Powerlink web site (http://Powerlink.emc.com)

System requirements 63
Installing AutoStart on Linux

Performing a fresh installation

The following sections cover a fresh installation for the agent and console. For an
upgrade installation, refer to "Performing a rolling upgrade" on page 70 and
"Performing a concurrent upgrade" on page 73.

Note: If the console is to run on a node with an agent installed, EMC recommends that the base
directory for the console matches the install directory for the agent.

Installing the agent and console packages

For SUSE Linux, Red Hat Linux and Oracle Enterprise Linux (OEL) nodes, the files
must be extracted from the .tar file, if applicable, and unpacked from the distribution
media before installation can take place.
1. At the # prompt, type:
./install.sh
2. Press Enter.
The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must
either upgrade first to AutoStart 5.4.0, before upgrading to
AutoStart 5.4.3. or Remove the older version completely and then
install AutoStart 5.4.3.
The following message appears:
Checking if the AutoStart console package is installed ...
AutoStart console is not installed.
Checking if the AutoStart agent package is installed ...
AutoStart agent is not installed.
When the system determines that you are doing a fresh install, you will see this
message:
Would you like to install AutoStart 5.4.3 agent? (y/n)
3. Type y and press Enter.
The following message appears:
you have chosen to install AutoStart 5.4.3 agent
4. When the Agent installation completes you can see the message,
AutoStart agent installation is successful.
The system installs the agent. Upon completion, you are prompted:
Would you like to install AutoStart 5.4.3 console? (y/n)
5. Type y and press Enter.
The following message appears:
you have chosen to install the AutoStart 5.4.3 console

64 EMC AutoStart Installation Guide

 Installing AutoStart on Linux

The console installation starts and you can see the message when the installation
finishes,
AutoStart console installation is successful.

Agent setup
To install the AutoStart 5.4.3 agent software (Bourne Shell):
1. Log in as root.
2. Set the FT_DIR environment variable to the directory selected when the agent
was installed:
FT_DIR=install-directory-path
export FT_DIR
Several AutoStart programs and scripts reference the FT_DIR environment
variable, which must be set to the pathname of the AutoStart software installation
directory. While installation requires only that the variable is set, for normal
operation the FT_DIR environment variable should always be set in the .profile
file.

Note: Multiple domains are not permitted on a single node running from a single
$FT_DIR. Each domain installation must run from a unique $FT_DIR.

3. Set the FT_DOMAIN environment variable to the AutoStart domain name. Type:
FT_DOMAIN=myDomain
export FT_DOMAIN

Note: The domain names are case-sensitive. Once the FT_DOMAIN environment variable is
set, there is no need to specify the domain name when starting the agent. Each AutoStart
domain must have a different name.

4. Change the working directory to the bin directory located under $FT_DIR. Type:
cd $FT_DIR/bin
5. Check the installation by running the verify_install script. The script verifies the
installation of the agent files and directories.
6. Execute ft_setup. At the # prompt, type:
./ft_setup
7. The following message appears:
Enter the name of the domain:
Type the domain name.
Domain names must be eight characters or less and they are case-sensitive.
8. The script prompts for the name of a primary agent node:
Enter the name of Primary Agent Node:
Use simple node names to specify the primary agent node. Do not specify a
nodeÊs DNS name extension or an IP address.
And you can see the message, Performing a primary node configuration
9. Next the user is asked, Specify the first of the 4 port numbers:

Performing a fresh installation 65

Installing AutoStart on Linux

Enter the default port number, [8042]. The following message appears:
Ports 8042, 8043, 8044 and 8045 will be used.
10. Supply the network port numbers required for agent process communication. The
numbers can be generated either manually or automatically.
Agent processes communicate with each other using all four TCP/IP ports. The
port numbers that are selected must be available and identical on all nodes in the
domain.
The ft_setup script generates the port numbers and runs to completion.
To automatically generate the ports, ft_setup looks for unused TCP/IP port
numbers beginning at 8042. If available, it uses ports 8042 through 8045.
When manually specifying the port, make certain that the selected port number
and the next three port numbers in sequence are available on all primary agent
nodes before starting the agent.

Note: The ft_setup script cannot guarantee that the ports chosen either manually or
automatically are not reserved for a process that is currently not running, nor can it verify
that the ports are available on all other primary nodes.

11. If this is the first node in the domain, AutoStart prompts for the license key. Enter
the license key and press Enter.
12. To receive email notifications from AutoStart, enter the name of the SMTP
hostname. Otherwise, leave this field blank. This setting can be modified later.
Press Enter.
13. When the installation is complete, you can see the message:
Installation for this node is complete.
To start the Agent run the "ft_startup" command.
14. Execute ft_startup. At the # prompt, type:
./ft_startup
15. The following message appears:
Starting Backbone......
Backbone started successfully.
Starting Agent....
Agent started successfully.
The Agent setup is completed successfully.

Environment variable files

During setup, AutoStart creates two files in the $FT_DIR/bin directory: envsh and
envcsh. These can be invoked using the ./envsh command to add the AutoStart
related environment variables to the local environment.

66 EMC AutoStart Installation Guide

 Installing AutoStart on Linux

Starting the agent

After installing and configuring the AutoStart agent, it must be started. To add a
primary agent node, first install the agent as a secondary, and then promote it. All
agent node names must be added to the replicated database before the agent can be
run:
1. If the current node is not the first node in the domain, from a running node,
ensure that the node name has been added to the replicated database.
2. To start an agent on a node, use the ft_startup command. The command is
found in the $FT_DIR/bin directory. If $FT_DIR/bin is added to the path, the
command runs from any directory. Enter:
cd $FT_DIR/bin
./ft_startup
The ft_startup command has the following syntax and options.
ft_startup [-d domain_name][-x][-h]

The command options to ft_startup are summarized next.

a. Use the -d domain-name option to specify the domain. The -d argument is
optional if the FT_DOMAIN environment variable is set. If the -d argument and
the FT_DOMAIN environment variable are both specified, then the domain
name following the -d argument takes precedence.
b. Use the -x (xterm) option to tell ft_startup to start the agent processes in their
own xterm windows for debugging or to become familiar with AutoStart. The
DISPLAY environment variable must be set to use this option. When tracing is
turned on and appropriately configured, all tracing output is displayed
directly to stdout of the respective agent process. Therefore, to be able to view
the destination of the output, EMC recommends that each agent process is
brought up in its own window with the -x option to ft_startup.
c. Use the -h option to display the help for ft_startup.
d. To verify that an agent is running on a node, run the console from any node in
the domain and display the Node Console, or issue the CLI command
listNodes.
The agent exits if the node on which it is running has not been previously defined in
the AutoStart replicated database. All secondary agents must be added to the domain
using the console or ftcli.
EMC recommends adding the following commands to the system startup file for each
node:
FT_DOMAIN=domain-name
export FT_DOMAIN
FT_DIR=install-directory-path
export FT_DIR
${FT_DIR}/bin/ft_startup
This command starts the agent on the local node. Because AutoStart depends on
other system utilities, this command should be run late in the startup procedure
when the operating system and network are fully initialized.

Performing a fresh installation 67

Installing AutoStart on Linux

The environment variable FT_DIR must be set prior to running any of the AutoStart
programs and scripts. This variable allows AutoStart to find various configuration,
log, and database files, as well as other utility programs.
Run the ft_startup command from each node in the domain to start an agent on the
node. If this is the first time an agent has ever run on the node and the node has been
designated in the ft_setup script to run a primary agent, an instance of the replicated
database is created on the node in a directory named as follows:
$FT_DIR/domain-name_node-name.

Startup parameters
AutoStart provides startup parameters that can be used to modify the default
behavior of the agent. These parameters should be used with care:
◆ -noisolationdetection · Overrides the agentÊs initial isolation detection
check. This parameter may be necessary if the set of IP addresses entered for
isolation detection are incorrect or are no longer accessible on the network.
◆ -realtime · By default the AutoStart agent on SUSE Linux and Red Hat Linux
nodes runs at the timeshare priority. This parameter allows the AutoStart
backbone and agent to run at the higher, realtime priority on some SUSE Linux
and Red Hat Linux systems. This parameter should only be used if failures are
occurring because AutoStart cannot get the necessary CPU cycles.

Stopping the agent

The shut down procedure should be used to ensure that no data is lost. By properly
shutting down the agent, the agent enters the shut down state rather than the failed
state.
To shut down a primary agent on a node, use the ft_shutdown command. The
command is found in the $FT_DIR/bin directory. If $FT_DIR/bin is added to the path,
the command runs from any directory. Enter:
cd $FT_DIR/bin
./ft_shutdown
The ft_shutdown command has the following syntax and options.
ft_shutdown [-backbone]

The argument to ft_shutdown is summarized below.

Use the -backbone option to tell ft_shutdown to stop both the agent processes and
the AutoStart backbone from the domain. By default the ft_shutdown command
only stops the agent processes on the node.
The FT_DOMAIN environment variable must be set before using this command.

Installing the console

The console can be installed on any network node, with or without a primary or
secondary agent.
Refer to "Installing the agent and console packages" on page 64 for the installation
steps.

68 EMC AutoStart Installation Guide

 Installing AutoStart on Linux

How to establish a connection to the domain

Before the console can be used to manage an AutoStart domain, it must first be
connected to the AutoStart domain:
Follow the steps below to connect the console to a domain.
1. Launch the console by entering:
installDir/console/bin/ftconsole
2. If you need to create a new domain at this time, follow step a through step e
below, or proceed to step 3:
a. In the Domain Name text box, enter the name of the domain that the console
is going to connect to.
b. In the Description text box, optionally enter a brief description of the domain.
c. In the Node List text box, enter the primary agents that the console should
connect to. Separate the primary agents using commas.
d. In the Domain Port text box, enter the domain port number. The domain port
number is the base port number that was entered during agent installation.
e. Click Apply.
3. In the domain tree, right-click on the domain name and select Connect to
Domain.
Connection to the domain is established.
4. Click the Licensing Security tab.
5. In the User Name text box, enter the name of the users who are going to use the
console.
6. In the Domain/Node text box, enter the domain name or node names of the
machines running the console. The wildcard „*‰ can be used to gain access to all
nodes.
7. Select an access right level.
There are three levels of security: User, Operator, and Administrator:
a. User · Users can view objects, but cannot execute, modify, or delete objects.
b. Operator · Operators can view and execute objects, but cannot modify or
delete objects.
c. Administrator · Administrators can define, delete, and modify any object in
the domain.
8. In the Description text box, enter a brief description of this user.
9. Click Add to add the user to the Security Manager Table.
10. Repeat steps 5 through 9 for each new user.

Performing a fresh installation 69

Installing AutoStart on Linux

Performing a rolling upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a rolling
upgrade to move to the latest AutoStart 5.4.3 software. Rolling Upgrade is a method
in which the nodes in an AutoStart domain are upgraded one at a time. Upgrading a
cluster in a rolling fashion helps avoid application downtime and prevents any loss of
High Availability during the domain upgrade time. The AutoStart domain is fully
functional in the midst of a rolling upgrade. However the new functionality
introduced by the upgraded version will not be enabled until all the nodes in the
cluster have been upgraded. It is recommended that an upgraded console be used to
manage a cluster that is in the midst of a rolling upgrade.

Note: For installations running older supported product versions, an upgrade to 5.4.0 needs to
be done in a concurrent fashion first before they can be upgraded to 5.4.3.

WARNING
A rolling upgrade on AutoStart 5.3 SP5 or older installations is not supported.
Unpredictable behavior can result from running different AutoStart versions in older
AutoStart domains.

Note: Only a one level rolling upgrade is supported. A one level rolling upgrade is a
configuration wherein all the nodes in the cluster can only be at one of the two possible levels:
either at a particular lower software release version or at the upgraded higher software release
version.

Before you begin

During the AutoStart upgrade process, the applications and resources running on the
node do not need to be shut down, thus requiring no application downtime.
However, for the short period of time that the agent is down during the upgrade,
AutoStart cannot monitor the applications and resources. If High availability of the
application is important then relocate the resource groups to other valid nodes before
initiating the upgrade.
Upgrading SUSE Linux and Red Hat Linux nodes requires a number of steps. This
procedure ensures that a new installation does not overwrite the previous one, so that
the upgrade can progress normally. The AutoStart installer will create a backup copy
of the previous configuration under the AutoStart installation directory.

Note: The upgrade to AutoStart 5.4.3 requires restart of the agent at the end of the upgrade
procedure. An appropriate service/maintenance outage is required to upgrade any AutoStart
node to AutoStart 5.4.3.

Unpacking the software

Follow the steps below to unpack the AutoStart software:
1. Log in as root.

70 EMC AutoStart Installation Guide

 Installing AutoStart on Linux

2. Download the software package.

If AutoStart is being installed on a 64-bit variant of SUSE, Red Hat Linux or
Oracle Enterprise Linux download and use EAS543_LINUX_x64.tar.gz. For all
other supported Linux operating systems download and use
EAS543_LINUX.tar.gz.
3. Uncompress and extract the previously selected tar file.

Installing the software on an upgrade

Follow the steps below to install the AutoStart agent and console on an upgrade:
1. Set the environment variables:
d. Set the FT_DIR environment variable to the directory selected when the agent
was installed. Type:
FT_DIR=AutoStart Installed directory
export FT_DIR

e. Set the FT_DOMAIN environment variable to the AutoStart domain name.

Type:
FT_DOMAIN=myDomain
export FT_DOMAIN
2. At the # prompt, type:
./install.sh
3. Press Enter. The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must either
upgrade first to AutoStart 5.4.0, before upgrading to AutoStart
5.4.3. or Remove the older version completely and then install
AutoStart 5.4.3.

When the software finds a previous agent installed on the system, it asks:
Would you like to upgrade the agent to AutoStart 5.4.3? (y/n)

4. Type y to upgrade to AutoStart 5.4.3. The following message appears:

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Do you want to continue with upgrade (y/n) [y]:

5. Type y to continue with the upgrade process. The following message appears:
Saving current Autostart agent configuration...

The operation causes EMC AutoStart to shut down and restart:

Continue? (y/n).
6. Type y and press Enter.

Note: This will be a point of no return.

Messages such as the following appear:

Shutting down the Agent...
Agent shutdown successfully.

Performing a rolling upgrade 71

Installing AutoStart on Linux

Shutting down the Backbone...

Shutting down any active process of Autostart agent ...

Stopping EMC AutoStart daemons

EMC AutoStart package successfully removed.

FT_DIR=/opt/EMCas542 will now be removed.

Installing AutoStart 5.4.3 agent...

Restoring current Autostart agent configuration ...

Please set your FT_DIR variable to new /opt/EMCas543

EMC Autostart 5.4.3 agent is installed.

Agent upgrade successful.

EMC Autostart console will be upgraded to 5.4.3 .

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Saving current Autostart console configuration...

Installing AutoStart 5.4.3 console...

Restoring current Autostart console configuration...

Console upgrade successful

7. When the Installation is complete, the next question appears:

Restart the AutoStart Agent? (y/n).
8. Type n and press Enter.
9. Manually set FT_DIR to the new value.
10. After the AutoStart agent service is up, the node re- joins the AutoStart cluster.
The node is now online and the user can relocate any Resource Groups to the
upgraded node.

Note: The Agent Release Version and the current Agent Operating Version of the nodes
will be displayed in the node properties tab of the AutoStart console.

11. Upgrade the nodes in the AutoStart domain one by one. Using the above
procedure all the nodes can be upgraded to 5.4.3 now or at a later point of time.
12. After all the nodes have been upgraded to 5.4.3, the Agent Operating Version
changes to 5.4.3 and all the new functionalities in the upgraded version will be
enabled.

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

72 EMC AutoStart Installation Guide

 Installing AutoStart on Linux

Performing a concurrent upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a concurrent
upgrade to move to the latest AutoStart 5.4.3 software. For installations running older
supported product versions an upgrade to 5.4.0 needs to be done in a concurrent
fashion first before they can be upgraded to 5.4.3.
Concurrent Upgrade is a method in which all the agents in the AutoStart domain are
shutdown down and each node upgraded to the new software at the same time. The
cluster is not operational during the software upgrade period.

Note: For AutoStart installations running product versions 5.4.0 or higher, a rolling upgrade
can be used to minimize downtime. Refer to the section "Performing a rolling upgrade" on
page 70.

Before you begin

To upgrade AutoStart from a previous release, each node in the AutoStart domain
must be upgraded. To upgrade a node, shut down the agent and then perform the
upgrade. Upgrade all nodes in the domain before restarting the upgraded agents. An
upgraded agent will not start while nodes running the older agent are still active.
During the AutoStart upgrade process, the applications and resources running on the
node do not need to be shut down, thus requiring no application downtime.
However, for the short period of time that the agent is down during the upgrade,
AutoStart cannot monitor the applications and resources. If an application fails
during the upgrade, AutoStart will detect the failure when the agent comes back
online and reacts accordingly.
Upgrading SUSE and Red Hat Linux nodes requires a number of steps. This
procedure ensures that a new installation does not overwrite the previous one, so that
the upgrade can progress normally.

Note: The upgrade to AutoStart 5.4.3 requires a restart of the agent at the end of the upgrade
procedure. An appropriate service/maintenance outage is required to upgrade any AutoStart
domain to AutoStart 5.4.3.

Note: Before upgrading to 5.4.3, make sure that you have a saved copy of the old version of the
AutoStart package. The old package will be needed in case you want to do a downgrade later.

Unpacking the software

Follow the steps below to unpack the AutoStart software:
1. Log in as root.
2. Download the software package.
If AutoStart is being installed on a 64-bit variant of SUSE, Red Hat Linux or
Oracle Enterprise Linux download and use EAS543_LINUX_x64.tar.gz. For all
other supported Linux operating systems download and use
EAS543_LINUX.tar.gz.

Performing a concurrent upgrade 73

Installing AutoStart on Linux

3. Uncompress and extract the previously selected tar file.

Installing the software on an upgrade

Follow the steps below to install the AutoStart agent and console on an upgrade:
1. Set the environment variables:
a. Set the FT_DIR environment variable to the directory selected when the agent
was installed. Type:
FT_DIR=AutoStart Installed directory
export FT_DIR

b. Set the FT_DOMAIN environment variable to the AutoStart domain name.

Type:
FT_DOMAIN=myDomain
export FT_DOMAIN
2. At the # prompt type the following command. This generates a configuration
backup.
$FT_DIR/bin/ftcli -d $FT_DOMAIN -cmd “backup”

3. Shut down the AutoStart agent and any open console.

4. At the # prompt, type:
./install.sh
5. Press Enter. The following text appears:
We will be checking if you have any AutoStart packages
installed on your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or
higher
- If you have a version of AutoStart prior to 5.4.0, you must
either upgrade first to AutoStart 5.4.0, before upgrading to
AutoStart 5.4.3. or Remove the older version completely and
then install AutoStart 5.4.3.
When the software finds a previous agent installed on the system, it asks:
Would you like to upgrade the agent to AutoStart 5.4.3?
(y/n)
6. Type y to upgrade to AutoStart 5.4.3. The following message appears:
This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Do you want to continue with upgrade (y/n) [y]:

7. Type y to continue with the upgrade process. The following message appears:
Saving current Autostart agent configuration...

The operation causes EMC AutoStart to shut down and restart:

Continue? (y/n).
8. Type y and press Enter.

Note: This will be a point of no return.

74 EMC AutoStart Installation Guide

 Installing AutoStart on Linux

Messages such as the following appear:

Shutting down the Agent...
Agent shutdown successfully.

Shutting down the Backbone...

Shutting down any active process of Autostart agent ...

Stopping EMC AutoStart daemons

EMC AutoStart package successfully removed.

FT_DIR=/opt/EMCas542 will now be removed.

Installing AutoStart 5.4.3 agent...

Restoring current Autostart agent configuration ...

Please set your FT_DIR variable to new /opt/EMCas543

EMC Autostart 5.4.3 agent is installed.

Agent upgrade successful.

EMC Autostart console will be upgraded to 5.4.3 .

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Saving current Autostart console configuration...

Installing AutoStart 5.4.3 console...

Restoring current Autostart console configuration...

Console upgrade successful

9. When the Installation is complete, the next question appears:

Restart the AutoStart Agent? (y/n).
10. Type n and press Enter.
11. Manually set FT_DIR to the new value.
12. After all nodes in the cluster have been upgraded manually restart the Agent one
after the other. The upgrade is only valid for the current node; repeat this
procedure for every node in the domain.

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

Performing a concurrent upgrade 75

Installing AutoStart on Linux

Downgrading to the previous release

Downgrade steps
The objective of the downgrade procedure is to restore the node/domain back to a
state that existed prior to carrying out the 5.4.3 upgrade. The exact downgrade steps
to be used will vary based on the previous software version from which an upgrade
to 5.4.3 was carried out and the current state of the cluster. Check your domain
configuration and choose the appropriate downgrade strategy from one of the two
options below.

Note: Make sure that you have the old version of the AutoStart package. The package will need
to be installed again as part of the downgrade procedure.

Note: An appropriate service/maintenance outage is required to carry out the above

downgrade procedure.

Mixed version domain

A mixed version domain is one where some nodes have been upgraded to AutoStart
5.4.3, while the remaining nodes are at the older version and have not yet been
upgraded. The AutoStart domain is in the midst of a rolling upgrade. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher. One or all of the
upgraded nodes can be downgraded. The objective of the node downgrade is to
restore the node to the original software version but with the current active domain
configuration. A successful downgrade will restore the node to the old version but
there will be no change in the domain configuration.
To downgrade a 5.4.3 agent in a mixed version domain, follow the below steps
1. Uninstall AutoStart 5.4.3 on the node you want to downgrade.
2. Install a previous version of AutoStart Agent on the node.
3. Run ft_setup and provide one of the primary agent node name that was not
upgraded to 5.4.3 for the Primary Agent Node prompt.
4. Start the AutoStart agent
5. Apply any AutoStart Hotfixes if necessary.
6. Repeat steps one through five for all the nodes to be downgraded.

Note: Before you restart the agent, ensure that at least one primary agent is up and
running. When the newly downgraded node joins the cluster, the agent on the node
retrieves the current active domain configuration from the cluster.

WARNING
The newly downgraded agent must never form the cluster; it should only join an
already up and running cluster. Doing otherwise will lead to a loss of
configuration data.

76 EMC AutoStart Installation Guide

 Installing AutoStart on Linux

Fully upgraded domain

A fully upgraded domain is one where all the nodes have been upgraded to
AutoStart 5.4.3 and the domain is currently operating at 5.4.3 level. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher.
All the upgraded nodes have to be downgraded at the same time. A downgrade
would restore all the nodes to the state at that "point in time" when the last node was
upgraded to 5.4.3. The objective of the downgrade procedure is to restore the domain
to the same configuration as that existed just prior to the last node getting upgraded
to 5.4.3. The downgrade procedure involves downgrading to the old AutoStart
version and restoring the latest old configuration. The latest old configuration refers
to the backed up configuration on the last node upgraded to 5.4.3.
To downgrade a 5.4.3 AutoStart domain, follow the below steps
1. Take all Resource Groups offline and shutdown the agents on all the nodes.
2. One the node that was upgrade last, copy the backed up Domain configuration
files to a location outside $FT_DIR folder using the following command:
# cp -Rf $FT_DIR/backup /backup_prev_ver

3. Save all license files.

4. Uninstall AutoStart 5.4.3 on the node.
5. Install a previous version of AutoStart Agent on the node.
6. Run ft_setup and start the AutoStart agent
7. Apply any AutoStart Hotfixes if necessary.
8. Repeat steps three through six for all the remaining nodes.
9. On the node that was upgraded last, restore the configuration backed up in step
two.
To restore the configuration you can use either AutoStart Console or AutoStart
ftcli.
Using AutoStart Console:
1. Input AutoStart licenses by choosing the appropriate product from the
AutoStart console dropdown list under the Licensing/Security tab.
2. Configure settings under Mirroring and Failure Detection Setting. Ensure
that all the mirroring and domain line settings are the same as before.
3. Select the required domain in the AutoStart console and import the
backup.def file located under /backup_prev_ver.
Using AutoStart ftcli:
1. Import the licenses saved earlier using the following ftcli command:
addLicense -product=<product_name> <License>

2. Import backup.def located under backup/backup_prev_ver using the following

ftcli command:
import /backup_prev_ver/backup.def -skipfail

Downgrading to the previous release 77

Installing AutoStart on Linux

WARNING
If the previous setup had an EMC mirroring data source, that data source would be
created afresh and hence a complete sync would be required when attached. This
would be done automatically when the RG is brought online. So a longer
maintenance window would be required. If a SRDF or a MirrorView data source was
used, a discovery would be performed during the import operation of the def file.

78 EMC AutoStart Installation Guide

 Installing AutoStart on Linux

Uninstalling AutoStart
Uninstalling the AutoStart software removes the installed files, configuration files,
replicated database files, and any temporary files AutoStart writes to the node.

Note: Before you uninstall AutoStart, make sure that you backup any files you would like to
retain, as AutoStart uninstall removes all files, including log and configuration files.

AutoStart can be uninstalled from a Linux node using the supplied ft_uninstall script
found in the $FT_DIR/bin. This script removes all the files generated by the
AutoStart agent. Once completed, the rest of the files placed on the machine are
removed as a package.
EMC recommends that you invoke the ft_uninstall script to uninstall the agent
software. The FT_DIR and FT_DOMAIN environment variables must be set in order to
invoke the script. Follow the steps below:
1. At the # prompt, type:
./ft_uninstall
2. Press Enter.
3. Click y at the question to remove the domain.
4. Click y at the question to remove EMC AutoStart from your machine.
5. Click y at the question to remove the agent package.
6. Click y at the question to remove the console package.
You receive the message that AutoStart was removed successfully.
The script removes any files created by the operation of the agent processes,
including database, configuration, and temporary files. Once database, configuration,
and temporary files are removed, the software files can be removed.
You can also use the package remove application. Ensure that the agent for the
domain to be removed is no longer running when executing the command. Ensure
that the agent is no longer running by entering ft_shutdown -backbone at the
command prompt. If the FT_DIR and FT_DOMAIN environment variables are not
set, provide a full path to stop the backbone:
1. To remove the EMC agent and console packages, after you perform the
./ft_uninstall, select y at the question, "Do you want to remove EMC AutoStart
from this machine‰. Or at the # prompt, type:
2. rpm -e EMCasa for the agent
Press Enter.
3. rpm -e EMCasmc for the console
Press Enter.
If the agent or console is still running, the packages are not removed correctly.

Uninstalling AutoStart 79
 6
Invisible Body Tag

Installing AutoStart on
HP-UX

Before installing AutoStart, refer to Chapter 2, "Planning the AutoStart Domain."

This chapter explains how to install AutoStart on HP-UX IA 64. It contains the
following sections:
◆ Overview ............................................................................................. 81
◆ System requirements ......................................................................... 82
◆ Performing a fresh installation......................................................... 83
◆ Performing a rolling upgrade........................................................... 88
◆ Performing a concurrent upgrade ................................................... 92
◆ Downgrading to the previous release ............................................. 95
◆ Uninstalling AutoStart ...................................................................... 98

Installing AutoStart on HP-UX 80

 Installing AutoStart on HP-UX

Overview
There are two components in the AutoStart installation, the agent and the console.
AutoStart agents monitor and manage nodes and processes in the domain. Resource
objects such as managed IP addresses, node aliases, and data sources are managed as
well. Primary agents execute rules, maintain replicated copies of the AutoStart
database, and monitor other agents in the domain.
The AutoStart console is a graphical administrative tool which accesses information
from an agent. It also initiates operations on an agent, enabling management of the
domain from a single location.
When installing both an agent and the console on the same node, install the agent
first, followed by the console. If an agent is already installed when the console
installation takes place, information about the domain is passed to the console
automatically.
The first three nodes installed in the domain are primary agents. Subsequent nodes
are installed as secondary agents. Secondary agents can be promoted to primary
agents after installation is complete.
When installing subsequent agents, the name of the node must be registered in the
console before the new agent can be brought online.

Overview 81
Installing AutoStart on HP-UX

System requirements
Note: For most up-to-date information on System requirements and Service Pack versions refer
to EMC AutoStart Compatibility Guide available on the Powerlink web site
(http://Powerlink.emc.com).

Note: Before you install AutoStart, you must install the Xcurses library on your machine.

Each HP-UX IA 64 version requires a minimum of 325 MB free disk space. In

addition, approximately 700 MB of free disk space is needed for the .tar file and the
files extracted from the .tar file.
The console requires Motif 2.1 and X11R5 releases. The console is officially supported
to run under the window manager MWM (the Motif Window Manager) on HP-UX.

Unpacking the software

Follow the steps below to unpack the software:
1. Log in as root.
2. Download the software package. You should see the EAS543_HPUX_ia64.tar.Z
for HP_UX IA 64 in your directory.
3. Type the following command to uncompress:
uncompress EAS543_HPUX_ia64.tar.Z
4. Press Enter.
5. Type the following command to extract:
tar -xvf EAS543_HPUX_ia64.tar
6. Press Enter.
After running install.sh, the files are placed in the /opt directory.

Network The following are the requirements of Network Connections:

Connections A minimum of two network connections for cluster communication:
◆ One NIC for the production network and AutoStart domain line.
◆ One NIC for a private network used as an AutoStart domain line.

Note: For more information, refer to EMC AutoStart Administrator's guide available on
on the Powerlink web site (http://Powerlink.emc.com).

82 EMC AutoStart Installation Guide

 Installing AutoStart on HP-UX

Performing a fresh installation

The following sections cover a fresh installation for the agent and console. For an
upgrade installation, refer to "Performing a rolling upgrade" on page 88 and
"Performing a concurrent upgrade" on page 92.

Note: If the console is to run on a node with an agent installed, EMC recommends that the base
directory for the console matches the install directory for the agent.

Installing the agent 1. At the # prompt, type:

and console ./install.sh
2. Press Enter.
The install uses the HP-UX package system to install the software.
3. The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must either
upgrade first to AutoStart 5.4.0, before upgrading to AutoStart
5.4.3. or Remove the older version completely and then install
AutoStart 5.4.3.

4. When the system determines that you are doing a fresh install, you will see this
message:
Would you like to install AutoStart 5.4.3 agent? (y/n)
5. Type y and press Enter.
The system installs the agent. Upon completion, you are prompted:
AutoStart agent installation was successful.
Would you like to install AutoStart 5.4.3 console? (y/n)
6. Type y and press Enter.
7. The console installation completes with this message:
AutoStart console installation was successful.

Agent setup
To install the AutoStart 5.4.3 agent software (Bourne Shell):
1. Log in as root.
2. Set the FT_DIR environment variable to the directory selected when the agent
was installed.
Several AutoStart programs and scripts reference the FT_DIR environment
variable, which must be set to the pathname of the AutoStart software installation
directory. While installation requires only that the variable is set, for normal
operation the FT_DIR environment variable should always be set in the .profile
file.

Performing a fresh installation 83

Installing AutoStart on HP-UX

Note: Multiple domains are not permitted on a single node running from a single $FT_DIR.
Each domain installation must run from a unique $FT_DIR.

3. Set the FT_DOMAIN environment variable to the AutoStart domain name. Enter:
FT_DOMAIN=myDomain
export FT_DOMAIN

Note: The domain names are case-sensitive. Once the FT_DOMAIN environment variable is set,
there is no need to specify the domain name when starting the agent. Each AutoStart domain
must have a different name.

4. Change the working directory to the bin directory located under $FT_DIR. Enter:
cd $FT_DIR/bin
5. Check the installation by running the verify_install script. The script verifies the
installation of the agent files and directories.
6. Execute ft_setup. At the # type:
./ft_setup
7. At the Enter the name of the domain: prompt, type the domain name.
Domain names must be eight characters or less; they are case-sensitive.
8. The script prompts for the name of a primary agent node:
Enter the name of Primary Agent Node:
Use simple node names to specify the primary agent node. Do not specify a
nodeÊs DNS name extension or an IP address.
9. Supply the network port numbers required for agent process communication. The
numbers can be generated either manually or automatically.
Agent processes communicate with each other using all four TCP/IP ports. The
port numbers that are selected must be available and identical on all nodes in the
domain.
The ft_setup script generates the port numbers and runs to completion.
To automatically generate the ports, ft_setup looks for unused TCP/IP port
numbers beginning at 8042. If available, it uses ports 8042 through 8045.
When manually specifying the port, make certain that the selected port number
and the next three port numbers in sequence are available on all primary agent
nodes before starting the agent.

Note: The ft_setup script cannot guarantee that the ports chosen either manually or
automatically are not reserved for a process that is currently not running, nor can it verify
that the ports are available on all other primary nodes.

10. If this is the first node in the domain, AutoStart prompts for the license key. Enter
the license key and press Enter.
11. To receive email notifications from AutoStart, enter the name of the SMTP
hostname. Otherwise, leave this field blank. This setting can be modified later.
Press Enter.
12. Run the ft_setup script on all nodes that have local copies of the AutoStart
software distribution.

84 EMC AutoStart Installation Guide

 Installing AutoStart on HP-UX

Environment variable files

During setup, AutoStart creates two files in the $FT_DIR/bin directory: envsh and
envcsh. These can be invoked using the ./envsh command to add the AutoStart related
environment variables to the local environment.

Starting the agent

After installing and configuring the AutoStart agent, it must be started. To add a
primary agent node, first install the agent as a secondary, and then promote it. All
agent node names must be added to the replicated database before the agent can be
run:
1. If the current node is not the first node in the domain, from a running node,
ensure that the node name has been added to the replicated database.
2. To start an agent on a node, use the ft_startup command. The command is
found in the $FT_DIR/bin directory. If $FT_DIR/bin is added to the path, the
command runs from any directory. Enter:
cd $FT_DIR/bin
./ft_startup
The ft_startup command has the following syntax and options.
ft_startup [-d domain_name][-x][-h]

The command options to ft_startup are summarized next.

a. Use the -d domain-name option to specify the domain. The -d argument is
optional if the FT_DOMAIN environment variable is set. If the -d argument and
the FT_DOMAIN environment variable are both specified, then the domain
name following the -d argument takes precedence.
b. Use the -x (xterm) option to tell ft_startup to start the agent processes in their
own xterm windows for debugging or to become familiar with AutoStart. The
DISPLAY environment variable must be set to use this option. When tracing is
turned on and appropriately configured, all tracing output is displayed
directly to stdout of the respective agent process. Therefore, to be able to view
the destination of the output, EMC recommends that each agent process is
brought up in its own window with the -x option to ft_startup.
c. Use the -h option to display the help for ft_startup.
d. To verify that an agent is running on a node, run the console from any node in
the domain and display the Node Console, or issue the CLI command
listNodes.
The agent exits if the node on which it is running has not been previously defined in
the AutoStart replicated database. All secondary agents must be added to the domain
using the console or ftcli.
EMC recommends adding the following commands to the system startup file for each
node:
FT_DOMAIN=domain-name
export FT_DOMAIN
FT_DIR=install-directory-path
export FT_DIR

Performing a fresh installation 85

Installing AutoStart on HP-UX

${FT_DIR}/bin/ft_startup
This command starts the agent on the local node. Because AutoStart depends on
other system utilities, this command should be run late in the startup procedure
when the operating system and network are fully initialized.
The environment variable FT_DIR must be set prior to running any of the AutoStart
programs and scripts. This variable allows AutoStart to find various configuration,
log, and database files, as well as other utility programs.
Run the ft_startup command from each node in the domain to start an agent on the
node. If this is the first time an agent has ever run on the node and the node has been
designated in the ft_setup script to run a primary agent, an instance of the
replicated database is created on the node in a directory named as follows:
$FT_DIR/domain-name_node-name.

Startup parameters
AutoStart provides startup parameters that can be used to modify the default
behavior of the agent. These parameters should be used with care:
◆ -noisolationdetection · Overrides the agentÊs initial isolation detection
check. This parameter may be necessary if the set of IP addresses entered for
isolation detection are incorrect or are no longer accessible on the network.
◆ -realtime · By default the AutoStart agent on SuSE Linux nodes runs at the
timeshare priority. This parameter allows the AutoStart backbone and agent to
run at the higher, realtime priority on some SuSE Linux systems. This parameter
should only be used if failures are occurring because AutoStart cannot get the
necessary CPU cycles.

Stopping the agent

The shut down procedure should be used to ensure that no data is lost. By properly
shutting down the agent, the agent enters the shut down state rather than the failed
state.
To shut down a primary agent on a node, use the ft_shutdown command. The
command is found in the $FT_DIR/bin directory. If $FT_DIR/bin is added to the path,
the command runs from any directory. Enter:
cd $FT_DIR/bin
./ft_shutdown
The ft_shutdown command has the following syntax and options.
ft_shutdown [-backbone]

The argument to ft_shutdown is summarized below.

Use the -backbone option to tell ft_shutdown to stop both the agent processes and
the AutoStart backbone from the domain. By default the ft_shutdown command
only stops the agent processes on the node.
The FT_DOMAIN environment variable must be set before using this command.

How to establish a connection to the domain

Before the console can be used to manage an AutoStart domain, it must first be
connected to the AutoStart domain.
Follow the steps below to connect the console to a domain:

86 EMC AutoStart Installation Guide

 Installing AutoStart on HP-UX

1. Launch the console by entering:

installDir/console/bin/ftconsole
2. If you need to create a new domain at this time, follow step a through step e
below, or proceed to step 3:
a. In the Domain Name text box, enter the name of the domain that the console
is going to connect to.
b. In the Description text box, optionally enter a brief description of the domain.
c. In the Node List text box, enter the primary agents that the console should
connect to. Separate the primary agents using commas.
d. In the Domain Port text box, enter the domain port number. The domain port
number is the base port number that was entered during agent installation.
e. Click Apply.
3. In the domain tree, right-click on the domain name and select Connect to
Domain.
Connection to the domain is established.
4. Click the Licensing Security tab.
5. In the User Name text box, enter the name of the users who are going to use the
console.
6. In the Domain/Node text box, enter the domain name or node names of the
machines running the console. The wildcard „*‰ can be used to gain access to all
nodes.
7. Select an access right level:
There are three levels of security: User, Operator, and Administrator.
a. User · Users can view objects, but cannot execute, modify, or delete objects.
b. Operator · Operators can view and execute objects, but cannot modify or
delete objects.
c. Administrator · Administrators can define, delete, and modify any object in
the domain.
8. In the Description text box, enter a brief description of this user.
9. Click Add to add the user to the Security Manager Table.
10. Repeat steps 5 through 9 for each new user.

Performing a fresh installation 87

Installing AutoStart on HP-UX

Performing a rolling upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a rolling
upgrade to move to the latest AutoStart 5.4.3 software. Rolling Upgrade is a method
in which the nodes in an AutoStart domain are upgraded one at a time. Upgrading a
cluster in a rolling fashion helps avoid application downtime and prevents any loss of
High Availability during the domain upgrade time. The AutoStart domain is fully
functional in the midst of a rolling upgrade. However the new functionality
introduced by the upgraded version will not be enabled until all the nodes in the
cluster have been upgraded. It is recommended that an upgraded console be used to
manage a cluster that is in the midst of a rolling upgrade.

Note: For installations running older supported product versions, an upgrade to 5.4.0 needs to
be done in a concurrent fashion first before they can be upgraded to 5.4.3.

WARNING
A rolling upgrade on AutoStart 5.3 SP5 or older installations is not supported.
Unpredictable behavior can result from running different AutoStart versions in older
AutoStart domains.

Note: Only a one level rolling upgrade is supported. A one level rolling upgrade is a
configuration wherein all the nodes in the cluster can only be at one of the two possible levels:
either at a particular lower software release version or at the upgraded higher software release
version.

Before you begin

During the AutoStart upgrade process, the applications and resources running on the
node do not need to be shut down, thus requiring no application downtime.
However, for the short period of time that the agent is down during the upgrade,
AutoStart cannot monitor the applications and resources. If High availability of the
application is important then relocate the resource groups to other valid nodes before
initiating the upgrade.
Upgrading HP-UX nodes requires a number of steps. This procedure ensures that a
new installation does not overwrite the previous one, so that the upgrade can
progress normally. The AutoStart installer will create a backup copy of the previous
configuration under the AutoStart installation directory.

Note: The upgrade to AutoStart 5.4.3 requires restart of the agent at the end of the upgrade
procedure. An appropriate service/maintenance outage is required to upgrade any AutoStart
node to AutoStart 5.4.3.

Unpacking the software

Follow the steps below to unpack the AutoStart software:
1. Log in as root.

88 EMC AutoStart Installation Guide

 Installing AutoStart on HP-UX

2. Download the software package. You should see the EAS543_HPUX_ia64.tar.Z

file in your directory.
3. Uncompress and extract the EAS543_HPUX_ia64.tar.Z file.

Installing the software on an upgrade

Follow the steps below to install the AutoStart agent and console on an upgrade:
1. Set the environment variables:
d. Set the FT_DIR environment variable to the directory selected when the agent
was installed. Type:
FT_DIR=AutoStart Installed directory
export FT_DIR

e. Set the FT_DOMAIN environment variable to the AutoStart domain name. Type:
FT_DOMAIN=myDomain
export FT_DOMAIN
2. At the # prompt, type:
./install.sh
3. Press Enter. The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must either
upgrade first to AutoStart 5.4.0, before upgrading to AutoStart
5.4.3. or Remove the older version completely and then install
AutoStart 5.4.3.

When the software finds a previous agent installed on the system, it asks:
Would you like to upgrade the agent to AutoStart 5.4.3? (y/n)

4. Type y to upgrade to AutoStart 5.4.3. The following message appears:

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Do you want to continue with upgrade (y/n) [y]:

5. Type y to continue with the upgrade process. The following message appears:
Saving current Autostart agent configuration...

The operation causes EMC AutoStart to shut down and restart:

Continue? (y/n).
6. Type y and press Enter.

Note: This will be a point of no return.

Messages such as the following appear:

Shutting down the Agent...
Agent shutdown successfully.

Shutting down the Backbone...

Shutting down any active process of Autostart agent ...

Performing a rolling upgrade 89

Installing AutoStart on HP-UX

Stopping EMC AutoStart daemons

EMC AutoStart package successfully removed.

FT_DIR=/opt/EMCas542 will now be removed.

Installing AutoStart 5.4.3 agent...

Restoring current Autostart agent configuration ...

Please set your FT_DIR variable to new /opt/EMCas543

EMC Autostart 5.4.3 agent is installed.

Agent upgrade successful.

EMC Autostart console will be upgraded to 5.4.3 .

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Saving current Autostart console configuration...

Installing AutoStart 5.4.3 console...

Restoring current Autostart console configuration...

Console upgrade successful

7. When the Installation is complete, the next question appears:

Restart the AutoStart Agent? (y/n).
8. Type y and press Enter. Output similar to the following appears:
About to start AutoStart. Please wait.
EMC AutoStart startup script.

Setting environment from /opt/EMCas543/config/agent_env.HP-UX

Starting agent for domain Sample_Domain

Starting Backbone...
...
Backbone started successfully.

Starting Agent...

Agent started successfully.

9. Manually set FT_DIR to the new value.

10. After the AutoStart agent service is up, the node re- joins the AutoStart cluster.
The node is now online and the user can relocate any Resource Groups to the
upgraded node.

Note: The Agent Release Version and the current Agent Operating Version of the nodes
will be displayed in the node properties tab of the AutoStart console.

11. Upgrade the nodes in the AutoStart domain one by one. Using the above
procedure all the nodes can be upgraded to 5.4.3 now or at a later point of time.
12. After all the nodes have been upgraded to 5.4.3, the Agent Operating Version
changes to 5.4.3 and all the new functionalities in the upgraded version will be
enabled.

90 EMC AutoStart Installation Guide

 Installing AutoStart on HP-UX

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

Performing a rolling upgrade 91

Installing AutoStart on HP-UX

Performing a concurrent upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a concurrent
upgrade to move to the latest AutoStart 5.4.3 software. For installations running older
supported product versions an upgrade to 5.4.0 needs to be done in a concurrent
fashion first before they can be upgraded to 5.4.3.
Concurrent Upgrade is a method in which all the agents in the AutoStart domain are
shutdown down and each node upgraded to the new software at the same time. The
cluster is not operational during the software upgrade period.

Note: For AutoStart installations running product versions 5.4.0 or higher, a rolling upgrade
can be used to minimize downtime. Refer to the section "Performing a rolling upgrade" on
page 88.

Before you begin

To upgrade AutoStart from a previous release, each node in the AutoStart domain
must be upgraded. To upgrade a node, shut down the agent and then perform the
upgrade. Upgrade all nodes in the domain before restarting the upgraded agents. An
upgraded agent will not start while nodes running the older agent are still active.
During the AutoStart upgrade process, the applications and resources running on the
node do not need to be shut down, thus requiring no application downtime.
However, for the short period of time that the agent is down during the upgrade,
AutoStart cannot monitor the applications and resources. If an application fails
during the upgrade, AutoStart will detect the failure when the agent comes back
online and reacts accordingly.
Upgrading HP-UX nodes requires a number of steps. This procedure ensures that a
new installation does not overwrite the previous one, so that the upgrade can
progress normally.

Note: The upgrade to AutoStart 5.4.3 requires restart of the agent at the end of the upgrade
procedure. An appropriate service/maintenance outage is required to upgrade any AutoStart
domain to AutoStart 5.4.3.

Note: Before upgrading to 5.4.3, make sure that you have a saved copy of the old version of the
AutoStart package. The old package will be needed in case you want to do a downgrade later.

Unpacking the software

Follow the steps below to unpack the AutoStart software:
1. Log in as root.
2. Download the software package. You should see the EAS543_HPUX_ia64.tar.Z
file in your directory.
3. Uncompress and extract the EAS543_HPUX_ia64.tar.Z file.

92 EMC AutoStart Installation Guide

 Installing AutoStart on HP-UX

Installing the software on an upgrade

Follow the steps below to install the AutoStart agent and console on an upgrade:
1. Set the environment variables:
a. Set the FT_DIR environment variable to the directory selected when the agent
was installed. Type:
FT_DIR=AutoStart Installed directory
export FT_DIR

b. Set the FT_DOMAIN environment variable to the AutoStart domain name. Type:
FT_DOMAIN=myDomain
export FT_DOMAIN
2. At the # prompt type the following command. This generates a configuration
backup.
$FT_DIR/bin/ftcli -d $FT_DOMAIN -cmd “backup”

3. Shut down the AutoStart agent and any open console.

4. At the # prompt, type:
./install.sh
5. Press Enter. The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must either
upgrade first to AutoStart 5.4.0, before upgrading to AutoStart
5.4.3. or Remove the older version completely and then install
AutoStart 5.4.3.

When the software finds a previous agent installed on the system, it asks:
Would you like to upgrade the agent to AutoStart 5.4.3? (y/n)

6. Type y to upgrade to AutoStart 5.4.3. The following message appears:

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Do you want to continue with upgrade (y/n) [y]:

7. Type y to continue with the upgrade process. The following message appears:
Saving current Autostart agent configuration...

The operation causes EMC AutoStart to shut down and restart:

Continue? (y/n).
8. Type y and press Enter.

Note: This will be a point of no return.

Messages such as the following appear:

Shutting down the Agent...
Agent shutdown successfully.

Shutting down the Backbone...

Shutting down any active process of Autostart agent ...

Performing a concurrent upgrade 93

Installing AutoStart on HP-UX

Stopping EMC AutoStart daemons

EMC AutoStart package successfully removed.

FT_DIR=/opt/EMCas542 will now be removed.

Installing AutoStart 5.4.3 agent...

Restoring current Autostart agent configuration ...

Please set your FT_DIR variable to new /opt/EMCas543

EMC Autostart 5.4.3 agent is installed.

Agent upgrade successful.

EMC Autostart console will be upgraded to 5.4.3 .

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Saving current Autostart console configuration...

Installing AutoStart 5.4.3 console...

Restoring current Autostart console configuration...

Console upgrade successful

9. When the Installation is complete, the next question appears:

Restart the AutoStart Agent? (y/n).
10. Type n and press Enter.
11. Installation finishes and exits to command line prompt.
12. After all nodes in the cluster have been upgraded manually restart the Agent one
after the other. The upgrade is only valid for the current node; repeat this
procedure for every node in the domain.

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

94 EMC AutoStart Installation Guide

 Installing AutoStart on HP-UX

Downgrading to the previous release

Downgrade steps
The objective of the downgrade procedure is to restore the node/domain back to a
state that existed prior to carrying out the 5.4.3 upgrade. The exact downgrade steps
to be used will vary based on the previous software version from which an upgrade
to 5.4.3 was carried out and the current state of the cluster. Check your domain
configuration and choose the appropriate downgrade strategy from one of the two
options below.

Note: Make sure that you have the old version of the AutoStart package. The package will need
to be installed again as part of the downgrade procedure.

Note: An appropriate service/maintenance outage is required to carry out the above

downgrade procedure.

Mixed version domain

A mixed version domain is one where some nodes have been upgraded to AutoStart
5.4.3, while the remaining nodes are at the older version and have not yet been
upgraded. The AutoStart domain is in the midst of a rolling upgrade. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher. One or all of the
upgraded nodes can be downgraded. The objective of the node downgrade is to
restore the node to the original software version but with the current active domain
configuration. A successful downgrade will restore the node to the old version but
there will be no change in the domain configuration.
To downgrade a 5.4.3 agent in a mixed version domain, follow the below steps
1. Uninstall AutoStart 5.4.3 on the node you want to downgrade.
2. Install a previous version of AutoStart Agent on the node.
3. Run ft_setup and provide one of the primary agent node name that was not
upgraded to 5.4.3 for the Primary Agent Node prompt.
4. Start the AutoStart agent
5. Apply any AutoStart Hotfixes if necessary.
6. Repeat steps one through five for all the nodes to be downgraded.

Note: Before you restart the agent, ensure that at least one primary agent is up and
running. When the newly downgraded node joins the cluster, the agent on the node
retrieves the current active domain configuration from the cluster.

WARNING
The newly downgraded agent must never form the cluster; it should only join an
already up and running cluster. Doing otherwise will lead to a loss of
configuration data.

Downgrading to the previous release 95

Installing AutoStart on HP-UX

Fully upgraded domain

A fully upgraded domain is one where all the nodes have been upgraded to
AutoStart 5.4.3 and the domain is currently operating at 5.4.3 level. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher.
All the upgraded nodes have to be downgraded at the same time. A downgrade
would restore all the nodes to the state at that "point in time" when the last node was
upgraded to 5.4.3. The objective of the downgrade procedure is to restore the domain
to the same configuration as that existed just prior to the last node getting upgraded
to 5.4.3. The downgrade procedure involves downgrading to the old AutoStart
version and restoring the latest old configuration. The latest old configuration refers
to the backed up configuration on the last node upgraded to 5.4.3.
To downgrade a 5.4.3 AutoStart domain, follow the below steps
1. Take all Resource Groups offline and shutdown the agents on all the nodes.
2. One the node that was upgrade last, copy the backed up Domain configuration
files to a location outside $FT_DIR folder using the following command:
# cp -Rf $FT_DIR/backup /backup_prev_ver

3. Save all license files.

4. Uninstall AutoStart 5.4.3 on the node.
5. Install a previous version of AutoStart Agent on the node.
6. Run ft_setup and start the AutoStart agent
7. Apply any AutoStart Hotfixes if necessary.
8. Repeat steps three through six for all the remaining nodes.
9. On the node that was upgraded last, restore the configuration backed up in step
two.
To restore the configuration you can use either AutoStart Console or AutoStart
ftcli.
Using AutoStart Console:
1. Input AutoStart licenses by choosing the appropriate product from the
AutoStart console dropdown list under the Licensing/Security tab.
2. Configure settings under Mirroring and Failure Detection Setting. Ensure
that all the mirroring and domain line settings are the same as before.
3. Select the required domain in the AutoStart console and import the
backup.def file located under /backup_prev_ver.
Using AutoStart ftcli:
1. Import the licenses saved earlier using the following ftcli command:
addLicense -product=<product_name> <License>

2. Import backup.def located under backup/backup_prev_ver using the following

ftcli command:
import /backup_prev_ver/backup.def -skipfail

96 EMC AutoStart Installation Guide

 Installing AutoStart on HP-UX

WARNING
If the previous setup had an EMC mirroring data source, that data source would be
created afresh and hence a complete sync would be required when attached. This
would be done automatically when the RG is brought online. So a longer
maintenance window would be required. If a SRDF or a MirrorView data source was
used, a discovery would be performed during the import operation of the def file.

Downgrading to the previous release 97

Installing AutoStart on HP-UX

Uninstalling AutoStart
Uninstalling the AutoStart software removes the installed files, configuration files,
replicated database files, and any temporary files AutoStart writes to the node.

Note: Before you uninstall AutoStart, make sure that you backup any files you would like to
retain, as AutoStart uninstall removes all files, including log and configuration files.

AutoStart can be uninstalled from a HP-UX node using the supplied ft_uninstall
script found in the $FT_DIR/bin. This script removes all the files generated by the
AutoStart agent. Once completed, the rest of the files placed on the machine are
removed as a package.
EMC recommends that you invoke the ft_uninstall script to uninstall the agent
software. The FT_DIR and FT_DOMAIN environment variables must be set in order to
invoke the script. Follow the steps below:
1. At the # prompt, type:
./ft_uninstall
2. Press Enter.
3. Click y at the question to remove the domain.
4. Click y at the question to remove EMC AutoStart from your machine.
5. Click y at the question to remove the agent package.
6. Click y at the question to remove the console package.
You receive the message that AutoStart was removed successfully.
The script removes any files created by the operation of the agent processes,
including database, configuration, and temporary files. Once database, configuration,
and temporary files are removed, the software files can be removed. The system also
prompts you for both an agent and console uninstall. The ft_uninstall script provides
the option to remove the package files.

Uninstalling the AutoStart console

Perform the following steps to uninstall the AutoStart console:
1. At the # prompt, type:
swremove EMCasmc
2. Press Enter.
Uninstall messages appear.

98 EMC AutoStart Installation Guide

 7
Invisible Body Tag

Installing AutoStart on
AIX

Before installing AutoStart, refer to Chapter 2, "Planning the AutoStart Domain."

This chapter explains how to install AutoStart on AIX. It contains the following
sections:
◆ Overview ........................................................................................... 100
◆ System requirements ....................................................................... 101
◆ Performing a fresh installation....................................................... 102
◆ Performing a rolling upgrade......................................................... 107
◆ Performing a concurrent upgrade ................................................. 111
◆ Downgrading to the previous release ........................................... 114
◆ Uninstalling AutoStart .................................................................... 117

Installing AutoStart on AIX 99

Installing AutoStart on AIX

Overview
There are two components in the AutoStart installation, the agent and the console.
AutoStart agents monitor and manage nodes and processes in the domain. Resource
objects such as managed IP addresses, node aliases, and data sources are managed as
well. Primary agents execute rules, maintain replicated copies of the AutoStart
database, and monitor other agents in the domain.
The AutoStart console is a graphical administrative tool which accesses information
from an agent. It also initiates operations on an agent, enabling management of the
domain from a single location.
When installing both an agent and the console on the same node, install the agent
first, followed by the console. If an agent is already installed when the console
installation takes place, information about the domain is passed to the console
automatically.
The first three nodes installed in the domain are primary agents. Subsequent nodes
are installed as secondary agents. Secondary agents can be promoted to primary
agents after installation is complete.
When installing subsequent agents, the name of the node must be registered in the
console before the new agent can be brought online.

100 EMC AutoStart Installation Guide

 Installing AutoStart on AIX

System requirements
Note: For most up-to-date information on System requirements and Service Pack versions refer
EMC AutoStart Compatibility Guide available on the Powerlink web site
(http://Powerlink.emc.com).

Note: Before you install AutoStart, you must install the termcap library on your machine.

To run AutoStart, each AIX machine in the domain must meet the following
requirements:
◆ Minimum of 250 MB free disk space
◆ The console requires Motif 2.1 and X11R5 releases. The console is officially
supported to run under the window manager MWM (the Motif Window
Manager) on AIX.

Network The following are the requirements of Network Connections:

Connections A minimum of two network connections for cluster communication:
◆ One NIC for the production network and AutoStart domain line.
◆ One NIC for a private network used as an AutoStart domain line.

Note: For more information, refer "Redundant networks in the domain" section in the
EMC AutoStart Administrator's guide available on the Powerlink web site
(http://Powerlink.emc.com).

System requirements 101

Installing AutoStart on AIX

Performing a fresh installation

The following sections cover a fresh installation for the agent and console. For an
upgrade installation, refer to "Performing a rolling upgrade" on page 107 and
"Performing a concurrent upgrade" on page 111.

Note: If the console is to run on a node with an agent installed, EMC recommends that the base
directory for the console matches the install directory for the agent.

Installing the agent For AIX nodes, the files must be extracted from the tar file, if applicable, and
and console unpacked from the distribution media before installation can take place:
1. At the # prompt, type:
./install.sh
2. Press Enter.
The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must either
upgrade first to AutoStart 5.4.0, before upgrading to AutoStart
5.4.3. or Remove the older version completely and then install
AutoStart 5.4.3.

The following message appears:

Checking if the AutoStart console package is installed ...
AutoStart console is not installed.
Checking if the AutoStart agent package is installed ...
AutoStart agent is not installed.
When the system determines that you are doing a fresh install, you will see this
message:
Would you like to install AutoStart 5.4.3 agent? (y/n)
3. Type y and press Enter. The EMC License Agreement screen appears.
If you accept the license terms, type y and press Enter.
4. The system installs the agent. Upon completion, you are prompted:
AutoStart agent installation was successful.
Would you like to install AutoStart 5.4.3 console? (y/n)
5. Type y and press Enter. The EMC License Agreement screen appears. Read this
information carefully.
If you accept the license terms, type y and press Enter.
6. The following message appears when the Installation completes:
Autostart console installation is successful.

Agent setup
To install the AutoStart 5.4.3 agent software (Bourne Shell):

102 EMC AutoStart Installation Guide

 Installing AutoStart on AIX

1. Log in as root.
2. Set the FT_DIR environment variable to the directory selected when the agent
was installed.
Several AutoStart programs and scripts reference the FT_DIR environment
variable, which must be set to the pathname of the AutoStart software installation
directory. While installation requires only that the variable is set, for normal
operation the FT_DIR environment variable should always be set in the .profile
file.

Note: Multiple domains are not permitted on a single node running from a single $FT_DIR.
Each domain installation must run from a unique $FT_DIR.

3. Set the FT_DOMAIN environment variable to the AutoStart domain name. Enter:
FT_DOMAIN=myDomain
export FT_DOMAIN

Note: The domain names are case-sensitive. Once the FT_DOMAIN environment variable is set,
there is no need to specify the domain name when starting the agent. Each AutoStart domain
must have a different name.

4. Change the working directory to the bin directory located under $FT_DIR. Enter:
cd $FT_DIR/bin
5. Check the installation by running the verify_install script. The script verifies the
installation of the agent files and directories.
6. Execute ft_setup. At the # type:
./ft_setup
7. At the Enter the name of the domain: prompt, type the domain name.
Domain names must be eight characters or less; they are case-sensitive.
8. The script prompts for the name of a primary agent node:
Enter the name of Primary Agent Node:
Use simple node names to specify the primary agent node. Do not specify a
nodeÊs DNS name extension or an IP address.
9. Supply the network port numbers required for agent process communication. The
numbers can be generated either manually or automatically.
Agent processes communicate with each other using all four TCP/IP ports. The
port numbers that are selected must be available and identical on all nodes in the
domain.
The ft_setup script generates the port numbers and runs to completion.
To automatically generate the ports, ft_setup looks for unused TCP/IP port
numbers beginning at 8042. If available, it uses ports 8042 through 8045.
When manually specifying the port, make certain that the selected port number
and the next three port numbers in sequence are available on all primary agent
nodes before starting the agent.

Note: The ft_setup script cannot guarantee that the ports chosen either manually or
automatically are not reserved for a process that is currently not running, nor can it verify
that the ports are available on all other primary nodes.

Performing a fresh installation 103

Installing AutoStart on AIX

10. If this is the first node in the domain, AutoStart prompts for the license key. Enter
the license key and press Enter.
11. To receive email notifications from AutoStart, enter the name of the SMTP
hostname. Otherwise, leave this field blank. This setting can be modified later.
Press Enter.
12. Run the ft_setup script on all nodes that have local copies of the AutoStart
software distribution.

Environment variable files

During setup, AutoStart creates two files in the $FT_DIR/bin directory: envsh and
envcsh. These can be invoked using the ./envsh command to add the AutoStart related
environment variables to the local environment.

Starting the agent

After installing and configuring the AutoStart agent, it must be started. To add a
primary agent node, first install the agent as a secondary, and then promote it. All
agent node names must be added to the replicated database before the agent can be
run:
1. If the current node is not the first node in the domain, from a running node,
ensure that the node name has been added to the replicated database.
2. To start an agent on a node, use the ft_startup command. The command is
found in the $FT_DIR/bin directory. If $FT_DIR/bin is added to the path, the
command runs from any directory. Enter:
cd $FT_DIR/bin
./ft_startup
The ft_startup command has the following syntax and options.
ft_startup [-d domain_name][-x][-h]

The command options to ft_startup are summarized next.

a. Use the -d domain-name option to specify the domain. The -d argument is
optional if the FT_DOMAIN environment variable is set. If the -d argument and
the FT_DOMAIN environment variable are both specified, then the domain
name following the -d argument takes precedence.
b. Use the -x (xterm) option to tell ft_startup to start the agent processes in their
own xterm windows for debugging or to become familiar with AutoStart. The
DISPLAY environment variable must be set to use this option. When tracing is
turned on and appropriately configured, all tracing output is displayed
directly to stdout of the respective agent process. Therefore, to be able to view
the destination of the output, EMC recommends that each agent process is
brought up in its own window with the -x option to ft_startup.
c. Use the -h option to display the help for ft_startup.
d. To verify that an agent is running on a node, run the console from any node in
the domain and display the Node Console, or issue the CLI command
listNodes.
The agent exits if the node on which it is running has not been previously defined in
the AutoStart replicated database. All secondary agents must be added to the domain
using the console or ftcli.

104 EMC AutoStart Installation Guide

 Installing AutoStart on AIX

EMC recommends adding the following commands to the system startup file for each
node:
FT_DOMAIN=domain-name
export FT_DOMAIN
FT_DIR=install-directory-path
export FT_DIR
${FT_DIR}/bin/ft_startup
This command starts the agent on the local node. Because AutoStart depends on
other system utilities, this command should be run late in the startup procedure
when the operating system and network are fully initialized.
The environment variable FT_DIR must be set prior to running any of the AutoStart
programs and scripts. This variable allows AutoStart to find various configuration,
log, and database files, as well as other utility programs.
Run the ft_startup command from each node in the domain to start an agent on the
node. If this is the first time an agent has ever run on the node and the node has been
designated in the ft_setup script to run a primary agent, an instance of the
replicated database is created on the node in a directory named as follows:
$FT_DIR/domain-name_node-name.

Startup parameters
AutoStart provides startup parameters that can be used to modify the default
behavior of the agent. These parameters should be used with care:
◆ -noisolationdetection · Overrides the agentÊs initial isolation detection
check. This parameter may be necessary if the set of IP addresses entered for
isolation detection are incorrect or are no longer accessible on the network.
◆ -realtime · By default the AutoStart agent on SuSE Linux nodes runs at the
timeshare priority. This parameter allows the AutoStart backbone and agent to
run at the higher, realtime priority on some SuSE Linux systems. This parameter
should only be used if failures are occurring because AutoStart cannot get the
necessary CPU cycles.

Stopping the agent

The shut down procedure should be used to ensure that no data is lost. By properly
shutting down the agent, the agent enters the shut down state rather than the failed
state.
To shut down a primary agent on a node, use the ft_shutdown command. The
command is found in the $FT_DIR/bin directory. If $FT_DIR/bin is added to the path,
the command runs from any directory. Enter:
cd $FT_DIR/bin
./ft_shutdown
The ft_shutdown command has the following syntax and options.
ft_shutdown [-backbone]

The argument to ft_shutdown is summarized below.

Use the -backbone option to tell ft_shutdown to stop both the agent processes and
the AutoStart backbone from the domain. By default the ft_shutdown command
only stops the agent processes on the node.

Performing a fresh installation 105

Installing AutoStart on AIX

The FT_DOMAIN environment variable must be set before using this command.

How to establish a connection to the domain

Before the console can be used to manage an AutoStart domain, it must first be
connected to the AutoStart domain:
Follow the steps below to connect the console to a domain.
1. Launch the console by entering:
installDir/console/bin/ftconsole
2. If you need to create a new domain at this time, follow step a through step e
below, or proceed to step 3:
a. In the Domain Name text box, enter the name of the domain that the console
is going to connect to.
b. In the Description text box, optionally enter a brief description of the domain.
c. In the Node List text box, enter the primary agents that the console should
connect to. Separate the primary agents using commas.
d. In the Domain Port text box, enter the domain port number. The domain port
number is the base port number that was entered during agent installation.
e. Click Apply.
3. In the domain tree, right-click on the domain name and select Connect to
Domain.
Connection to the domain is established.
4. Click the Licensing Security tab.
5. In the User Name text box, enter the name of the users who are going to use the
console.
6. In the Domain/Node text box, enter the domain name or node names of the
machines running the console. The wildcard „*‰ can be used to gain access to all
nodes.
7. Select an access right level.
There are three levels of security: User, Operator, and Administrator:
a. User · Users can view objects, but cannot execute, modify, or delete objects.
b. Operator · Operators can view and execute objects, but cannot modify or
delete objects.
c. Administrator · Administrators can define, delete, and modify any object in
the domain.
8. In the Description text box, enter a brief description of this user.
9. Click Add to add the user to the Security Manager Table.
10. Repeat steps 5 through 9 for each new user.

106 EMC AutoStart Installation Guide

 Installing AutoStart on AIX

Performing a rolling upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a rolling
upgrade to move to the latest AutoStart 5.4.3 software. Rolling Upgrade is a method
in which the nodes in an AutoStart domain are upgraded one at a time. Upgrading a
cluster in a rolling fashion helps avoid application downtime and prevents any loss of
High Availability during the domain upgrade time. The AutoStart domain is fully
functional in the midst of a rolling upgrade. However the new functionality
introduced by the upgraded version will not be enabled until all the nodes in the
cluster have been upgraded to AutoStart 5.4. It is recommended that an upgraded
console be used to manage a cluster that is in the midst of a rolling upgrade.

Note: For installations running older supported product versions, an upgrade to 5.4.0 needs to
be done in a concurrent fashion first before they can be upgraded to 5.4.3.

WARNING
A rolling upgrade on AutoStart 5.3 SP5 or older installations is not supported.
Unpredictable behavior can result from running different AutoStart versions in older
AutoStart domains.

Note: Only a one level rolling upgrade is supported. A one level rolling upgrade is a
configuration wherein all the nodes in the cluster can only be at one of the two possible levels:
either at a particular lower software release version or at the upgraded higher software release
version.

Before you begin

During the AutoStart upgrade process, the applications and resources running on the
node do not need to be shut down, thus requiring no application downtime.
However, for the short period of time that the agent is down during the upgrade,
AutoStart cannot monitor the applications and resources. If High availability of the
application is important then relocate the resource groups to other valid nodes before
initiating the upgrade.
Upgrading AIX nodes requires a number of steps. This procedure ensures that a new
installation does not overwrite the previous one, so that the upgrade can progress
normally. The AutoStart installer will create a backup copy of the previous
configuration under the AutoStart installation directory.

Note: The upgrade to AutoStart 5.4.3 requires restart of the agent at the end of the upgrade
procedure. An appropriate service/maintenance outage is required to upgrade any AutoStart
node to AutoStart 5.4.3.

Performing a rolling upgrade 107

Installing AutoStart on AIX

Unpacking the software

Follow the steps below to unpack the AutoStart software:
1. Log in as root.
2. Download the software package. You should see the EAS543_AIX.tar.Z file in
your directory.
3. Uncompress and extract the EAS543_AIX.tar.Z file.

Installing the software on an upgrade

Follow the steps below to install the AutoStart agent and console on an upgrade:
1. Set the environment variables:
d. Set the FT_DIR environment variable to the directory selected when the agent
was installed. Type:
FT_DIR=AutoStart Installed directory
export FT_DIR

e. Set the FT_DOMAIN environment variable to the AutoStart domain name. Type:
FT_DOMAIN=myDomain
export FT_DOMAIN
2. At the # prompt, type:
./install.sh
3. Press Enter. The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must either
upgrade first to AutoStart 5.4.0, before upgrading to AutoStart
5.4.3. or Remove the older version completely and then install
AutoStart 5.4.3.

When the software finds a previous agent installed on the system, it asks:
Would you like to upgrade the agent to AutoStart 5.4.3? (y/n)

4. Type y to upgrade to AutoStart 5.4.3. The following message appears:

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Do you want to continue with upgrade (y/n) [y]:

5. Type y to continue with the upgrade process. The following message appears:
Saving current Autostart agent configuration...

The operation causes EMC AutoStart to shut down and restart:

Continue? (y/n).
6. Type y and press Enter.

Note: This will be a point of no return.

Messages such as the following appear:

108 EMC AutoStart Installation Guide

 Installing AutoStart on AIX

Shutting down the Agent...

Agent shutdown successfully.

Shutting down the Backbone...

Shutting down any active process of Autostart agent ...

Stopping EMC AutoStart daemons

EMC AutoStart package successfully removed.

FT_DIR=/opt/EMCas542 will now be removed.

Installing AutoStart 5.4.3 agent...

Restoring current Autostart agent configuration ...

Please set your FT_DIR variable to new /opt/EMCas543

EMC Autostart 5.4.3 agent is installed.

Agent upgrade successful.

EMC Autostart console will be upgraded to 5.4.3 .

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Saving current Autostart console configuration...

Installing AutoStart 5.4.3 console...

Restoring current Autostart console configuration...

Console upgrade successful

7. When the Installation is complete, the next question appears:

Restart the AutoStart Agent? (y/n).
8. Type y and press Enter. Output similar to the following appears:
About to start AutoStart. Please wait.
EMC AutoStart startup script.

Setting environment from /opt/EMCas543/config/agent_env.AIX

Starting agent for domain Sample_Domain

Starting Backbone...
...
Backbone started successfully.

Starting Agent...

Agent started successfully.

9. Manually set FT_DIR to the new value.

10. After the AutoStart agent service is up, the node re- joins the AutoStart cluster.
The node is now online and the user can relocate any Resource Groups to the
upgraded node.

Note: The Agent Release Version and the current Agent Operating Version of the nodes
will be displayed in the node properties tab of the AutoStart console.

11. Upgrade the nodes in the AutoStart domain one by one. Using the above
procedure all the nodes can be upgraded to 5.4.3 now or at a later point of time.

Performing a rolling upgrade 109

Installing AutoStart on AIX

12. After all the nodes have been upgraded to 5.4.3, the Agent Operating Version
changes to 5.4.3 and all the new functionalities in the upgraded version will be
enabled.

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

110 EMC AutoStart Installation Guide

 Installing AutoStart on AIX

Performing a concurrent upgrade

Overview
If you are currently running AutoStart 5.4.0 or higher you can perform a concurrent
upgrade to move to the latest AutoStart 5.4.3 software. For installations running older
supported product versions an upgrade to 5.4.0 needs to be done in a concurrent
fashion first before they can be upgraded to 5.4.3.
Concurrent Upgrade is a method in which all the agents in the AutoStart domain are
shutdown down and each node upgraded to the new software at the same time. The
cluster is not operational during the software upgrade period.

Note: For AutoStart installations running product versions 5.4.0 or higher, a rolling upgrade
can be used to minimize downtime. Refer to the section "Performing a rolling upgrade" on
page 107.

Before you begin

To upgrade AutoStart from a previous release, each node in the AutoStart domain
must be upgraded. To upgrade a node, shut down the agent and then perform the
upgrade. Upgrade all nodes in the domain before restarting the upgraded agents. An
upgraded agent will not start while nodes running the older agent are still active.
During the AutoStart upgrade process, the applications and resources running on the
node do not need to be shut down, thus requiring no application downtime.
However, for the short period of time that the agent is down during the upgrade,
AutoStart cannot monitor the applications and resources. If an application fails
during the upgrade, AutoStart will detect the failure when the agent comes back
online and reacts accordingly.
Upgrading AIX nodes requires a number of steps. This procedure ensures that a new
installation does not overwrite the previous one, so that the upgrade can progress
normally.

Note: The upgrade to AutoStart 5.4.3 requires restart of the agent at the end of the upgrade
procedure. An appropriate service/maintenance outage is required to upgrade any AutoStart
domain to AutoStart 5.4.3.

Note: Before upgrading to 5.4.3, make sure that you have a saved copy of the old version of the
AutoStart package. The old package will be needed in case you want to do a downgrade later.

Unpacking the software

When unpacking the software, make sure that the following packages are located in a
folder or directory that does not contain the packages from a previous installation:
EMAS.agent-5.4.3.bff
EMCas.console-5.4.3.bff
EAS_5.4.3.patch
install.sh

Performing a concurrent upgrade 111

Installing AutoStart on AIX

1. Log in as root.
2. Download the software package. You should see the EAS543_AIX.tar.Z file in
your directory.
3. Uncompress and extract EAS543_AIX.tar.Z.

Installing the software on an upgrade

Follow the steps below to install the AutoStart agent and console on an upgrade:
1. Set the environment variables:
a. Set the FT_DIR environment variable to the directory selected when the agent
was installed. Type:
FT_DIR=AutoStart Installed directory
export FT_DIR

b. Set the FT_DOMAIN environment variable to the AutoStart domain name. Type:
FT_DOMAIN=myDomain
export FT_DOMAIN
2. At the # prompt type the following command. This generates a configuration
backup.
$FT_DIR/bin/ftcli -d $FT_DOMAIN -cmd “backup”

3. Shut down the AutoStart agent and any open console.

4. At the # prompt, type:
./install.sh
5. Press Enter. The following text appears:
We will be checking if you have any AutoStart packages installed on
your system.
- Upgrade to 5.4.3 is supported only from Autostart 5.4.0 or higher
- If you have a version of AutoStart prior to 5.4.0, you must either
upgrade first to AutoStart 5.4.0, before upgrading to AutoStart
5.4.3. or Remove the older version completely and then install
AutoStart 5.4.3.

When the software finds a previous agent installed on the system, it asks:
Would you like to upgrade the agent to AutoStart 5.4.3? (y/n)

6. Type y to upgrade to AutoStart 5.4.3. The following message appears:

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Do you want to continue with upgrade (y/n) [y]:

7. Type y to continue with the upgrade process. The following message appears:
Saving current Autostart agent configuration...

The operation causes EMC AutoStart to shut down and restart:

Continue? (y/n).
8. Type y and press Enter.

Note: This will be a point of no return.

112 EMC AutoStart Installation Guide

 Installing AutoStart on AIX

Messages such as the following appear:

Shutting down the Agent...
Agent shutdown successfully.

Shutting down the Backbone...

Shutting down any active process of Autostart agent ...

Stopping EMC AutoStart daemons

EMC AutoStart package successfully removed.

FT_DIR=/opt/EMCas542 will now be removed.

Installing AutoStart 5.4.3 agent...

Restoring current Autostart agent configuration ...

Please set your FT_DIR variable to new /opt/EMCas543

EMC Autostart 5.4.3 agent is installed.

Agent upgrade successful.

EMC Autostart console will be upgraded to 5.4.3 .

This upgrade will completely remove the existing installation,
and restore the current configuration to new environment.

Saving current Autostart console configuration...

Installing AutoStart 5.4.3 console...

Restoring current Autostart console configuration...

Console upgrade successful

9. When the Installation is complete, the next question appears:

Restart the AutoStart Agent? (y/n).
10. Type n and press Enter.
11. Installation finishes and exits to command line prompt.
12. After all nodes in the cluster have been upgraded manually restart the Agent one
after the other. The upgrade is only valid for the current node; repeat this
procedure for every node in the domain.

! IMPORTANT
If AutoStart’s installation directory, i.e., $FT_DIR, changes during the upgrade
process, you have to manually edit any user defined Process Proxy definition prior
to starting them.

Performing a concurrent upgrade 113

Installing AutoStart on AIX

Downgrading to the previous release

Downgrade steps
The objective of the downgrade procedure is to restore the node/domain back to a
state that existed prior to carrying out the 5.4.3 upgrade. The exact downgrade steps
to be used will vary based on the previous software version from which an upgrade
to 5.4.3 was carried out and the current state of the cluster. Check your domain
configuration and choose the appropriate downgrade strategy from one of the two
options below.

Note: Make sure that you have the old version of the AutoStart package. The package will need
to be installed again as part of the downgrade procedure.

Note: An appropriate service/maintenance outage is required to carry out the above

downgrade procedure.

Mixed version domain

A mixed version domain is one where some nodes have been upgraded to AutoStart
5.4.3, while the remaining nodes are at the older version and have not yet been
upgraded. The AutoStart domain is in the midst of a rolling upgrade. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher. One or all of the
upgraded nodes can be downgraded. The objective of the node downgrade is to
restore the node to the original software version but with the current active domain
configuration. A successful downgrade will restore the node to the old version but
there will be no change in the domain configuration.
To downgrade a 5.4.3 agent in a mixed version domain, follow the below steps
1. Uninstall AutoStart 5.4.3 on the node you want to downgrade.
2. Install a previous version of AutoStart Agent on the node.
3. Run ft_setup and provide one of the primary agent node name that was not
upgraded to 5.4.3 for the Primary Agent Node prompt.
4. Start the AutoStart agent
5. Apply any AutoStart Hotfixes if necessary.
6. Repeat steps one through five for all the nodes to be downgraded.

Note: Before you restart the agent, ensure that at least one primary agent is up and
running. When the newly downgraded node joins the cluster, the agent on the node
retrieves the current active domain configuration from the cluster.

WARNING
The newly downgraded agent must never form the cluster; it should only join an
already up and running cluster. Doing otherwise will lead to a loss of
configuration data.

114 EMC AutoStart Installation Guide

 Installing AutoStart on AIX

Fully upgraded domain

A fully upgraded domain is one where all the nodes have been upgraded to
AutoStart 5.4.3 and the domain is currently operating at 5.4.3 level. The upgraded
nodes would have originally been running AutoStart 5.4.0 or higher.
All the upgraded nodes have to be downgraded at the same time. A downgrade
would restore all the nodes to the state at that "point in time" when the last node was
upgraded to 5.4.3. The objective of the downgrade procedure is to restore the domain
to the same configuration as that existed just prior to the last node getting upgraded
to 5.4.3. The downgrade procedure involves downgrading to the old AutoStart
version and restoring the latest old configuration. The latest old configuration refers
to the backed up configuration on the last node upgraded to 5.4.3.
To downgrade a 5.4.3 AutoStart domain, follow the below steps
1. Take all Resource Groups offline and shutdown the agents on all the nodes.
2. One the node that was upgrade last, copy the backed up Domain configuration
files to a location outside $FT_DIR folder using the following command:
# cp -Rf $FT_DIR/backup /backup_prev_ver

3. Save all license files.

4. Uninstall AutoStart 5.4.3 on the node.
5. Install a previous version of AutoStart Agent on the node.
6. Run ft_setup and start the AutoStart agent
7. Apply any AutoStart Hotfixes if necessary.
8. Repeat steps three through six for all the remaining nodes.
9. On the node that was upgraded last, restore the configuration backed up in step
two.
To restore the configuration you can use either AutoStart Console or AutoStart
ftcli.
Using AutoStart Console:
1. Input AutoStart licenses by choosing the appropriate product from the
AutoStart console dropdown list under the Licensing/Security tab.
2. Configure settings under Mirroring and Failure Detection Setting. Ensure
that all the mirroring and domain line settings are the same as before.
3. Select the required domain in the AutoStart console and import the
backup.def file located under /backup_prev_ver.
Using AutoStart ftcli:
1. Import the licenses saved earlier using the following ftcli command:
addLicense -product=<product_name> <License>

2. Import backup.def located under backup/backup_prev_ver using the following

ftcli command:
import /backup_prev_ver/backup.def -skipfail

Downgrading to the previous release 115

Installing AutoStart on AIX

WARNING
If the previous setup had an EMC mirroring data source, that data source would be
created afresh and hence a complete sync would be required when attached. This
would be done automatically when the RG is brought online. So a longer
maintenance window would be required. If a SRDF or a MirrorView data source was
used, a discovery would be performed during the import operation of the def file.

116 EMC AutoStart Installation Guide

 Installing AutoStart on AIX

Uninstalling AutoStart
Uninstalling the AutoStart software removes the installed files, configuration files,
replicated database files, and any temporary files AutoStart writes to the node.

Note: Before you uninstall AutoStart, make sure that you backup any files you would like to
retain, as AutoStart uninstall removes all files, including log and configuration files.

AutoStart can be uninstalled from a AIX node using the supplied ft_uninstall script
found in the $FT_DIR/bin. This script removes all the files generated by the
AutoStart agent. Once completed, the rest of the files placed on the machine are
removed as a package.
EMC recommends that you invoke the ft_uninstall script to uninstall the agent
software. The FT_DIR and FT_DOMAIN environment variables must be set in order to
invoke the script. Follow the steps below:
1. At the # prompt, type:
./ft_uninstall
2. Press Enter.
3. Click y at the question to remove the domain.
4. Click y at the question to remove EMC AutoStart from your machine.
5. Click y at the question to remove the agent package.
6. Click y at the question to remove the console package.
You receive the message that AutoStart was removed successfully.
The script removes any files created by the operation of the agent processes,
including database, configuration, and temporary files. The ft_uninstall script
provides the option to remove the package files. Once database, configuration, and
temporary files are removed, the software files can be removed. The system also
prompts you for both an agent and console uninstall.

Note: When you invoke ./ft_uninstall, this does not offline resources and resource groups. You
must first offline resources and resource groups prior to invoking ./ft_uninstall.

Uninstalling the AutoStart console

When only the console is installed, you must manually remove the console package,
or install the agent and then remove both the agent and the console. The commands
(for AIX only) to manually remove the console are as follows:
To check whether console package is installed or not:
# lslpp -p | grep EMCas.console
To remove the console package:
# installp -u EMCas.console

Uninstalling AutoStart 117

Installing AutoStart on AIX

118 EMC AutoStart Installation Guide

 8
Invisible Bodytart

Installing AutoStart in
Virtual environments

This chapter explains how to install AutoStart in Virtual environments. It contains the
following sections:
◆ Supported virtual environments.................................................... 120
◆ AutoStart installation....................................................................... 121

Installing AutoStart in Virtual environments 119

Installing AutoStart in Virtual environments

Supported virtual environments

AutoStart 5.4.3 supports installation on the Guest or on the host Hypervisor for
specific platforms and combinations. Table 1 lists the supported virtual environment
configurations:

Table 1 Supported virtual environments

Architecture Virtualization Platform Virtual OS

Windows 2003 R2, SP1, SP2 (32-bit)

Windows 2008 SP2 (32-bit)
x86 VMware ESX 4.1, 4.0 (32-bit) Red Hat Enterprise Linux 5.x, 6.x (32-bit)
Oracle Enterprise Linux 5.x, 6.x (32-bit)
SUSE Linux Enterprise Server 10.x, 11.x (32-bit)

Windows 2003 R2 (32- and 64-bit) (VMware only)

Windows 2008 SP2 (32- and 64-bit)
Windows 2008 R2, SP1 (64-bit)
Vmware ESX 4.1, 4.0 (32 and 64-bit)
x64 Red Hat Enterprise Linux 5.x (32- and 64-bit)
Windows Hyper-V Server 2008, 2008 R2 (64-bit)
Red Hat Enterprise Linux 6.x (32 and 64-bit) (VMware only)
Oracle Enterprise Linux 5.x, 6.x (32- and 64-bit) (VMware only)
SUSE Linux Enterprise Server 10.x, 11.x (32- and 64-bit)

Note: For most up-to-date information on System requirements, Operating systems, Console
requirements, and Service Pack versions, refer to EMC AutoStart Compatibility Guide
available on the Powerlink web site http://Powerlink.emc.com

120 EMC AutoStart Installation Guide

 Installing AutoStart in Virtual environments

AutoStart installation
There are two components in the AutoStart installation, the agent and the console.
AutoStart agents monitor and manage Virtual Machines and processes in the domain.
Resource objects such as managed IP addresses, node aliases, and data sources are
managed as well. Primary agents execute rules, maintain replicated copies of the
AutoStart database, and monitor other agents in the domain.
The AutoStart console is a graphical administrative tool which accesses information
from an agent. It also initiates operations on an agent, enabling management of the
domain from a single location.
When installing both an agent and the console on the same Virtual Machine, install
the agent first, followed by the console. If an agent is already installed when the
console installation takes place, information about the domain is passed to the
console automatically.
The first three Virtual machines installed in the domain are primary agents.
Subsequent Virtual machines are installed as secondary agents. Secondary agents can
be promoted to primary agents after installation is complete.
When installing subsequent agents, the name of the Virtual machine must be
registered in the console before the new agent can be brought online.
The following AutoStart packages have to be installed as per the platform to be
supported:
◆ Windows Guest Operating System on VMware ESX server.
EAS543_WIN_x86.exe* or EAS543_WIN_x64.exe*
◆ Linux Guest Operating System on VMware ESX server.
EAS543_LINUX.tar.gz** or EAS543_LINUX_x64.tar.gz**
◆ VMware ESX hypervisor.
EAS543_LINUX.tar.gz** or EAS543_LINUX_x64.tar.gz**
◆ Windows Guest Operating System on Microsoft Hyper-V
EAS543_WIN_x86.exe* or EAS543_WIN_x64.exe*
◆ AutoStart on Microsoft Hyper-V in the Parent Partition.
EAS543_WIN_x86.exe* or EAS543_WIN_x64.exe*

*Refer to "Installing AutoStart on Windows" on page 21 for installation instructions

on Windows.
** Refer to"Installing AutoStart on Linux" on page 61 for installation instructions on
Linux.

AutoStart installation 121

Installing AutoStart in Virtual environments

122 EMC AutoStart Installation Guide

 9

Silent Install

Silent Install for AutoStart is an installation process that does not require user
interaction during the install procedure. Silent Install is used in environments where
the install procedure is driven by an automated script or tool.
This chapter describes AutoStart support for Silent Install and provides information
on the following topics:
◆ Summary ........................................................................................... 124
◆ Silent Installation on Windows ...................................................... 125
◆ Silent Upgrade on Windows........................................................... 131
◆ Silent Uninstallation on Windows ................................................. 133
◆ Error handling .................................................................................. 135
◆ Silent Installation on Unix/Linux.................................................. 136
◆ Silent Uninstallation on Unix/Linux ............................................ 138
◆ Limitations ........................................................................................ 139

Silent Install 123

Silent Install

Summary
AutoStart Silent Install feature allows you install AutoStart through the CLI
(command line interface), where installation parameters are passed to the installer.
The Silent Install feature supports the following:
◆ Silent Installation
◆ Upgrade through Silent Installation
◆ Silent Uninstallation
AutoStart provides a common installer for both Silent Install and graphical
installation.
The rest of this document describes the Silent Install feature in more detail. The
document also describes the list of commands supported and the way in which the
user can specify the parameters for successful Installation and Uninstallation.

Platform support Note: For most up-to-date information on System requirements, Operating systems, Agent and
Console requirements, and Service Pack versions, refer to EMC AutoStart Compatibility Guide
available on the EMC Powerlink website (http://Powerlink.EMC.com)

The AutoStart 5.4.3 Release Notes available on the EMC Powerlink provides
information about the operating systems and VMware versions supported by
AutoStart.

124 EMC AutoStart Installation Guide

 Silent Install

Silent Installation on Windows

The AutoStart Installer executable runs from the Windows CLI. The inputs that you
provide through the AutoStart GUI installation wizard must be passed to the Installer
through the CLI. Silent Installation requires the following steps:
1. Open the Windows Command shell.
2. Run the AutoStart installer from the command shell. The installer silently installs
the product. The Command Syntax section provides the command syntax, used
for invoking the installer.
3. Type the following command to reboot the node:
‘shutdown –r’
4. After you reboot the node, all the AutoStart services are automatically up and
running. You may configure your domain from the AutoStart console.

Command Syntax The command format for invoking Silent Install for AutoStart is as follows:
start <sp> /wait <sp> <AutoStart_Installer> <sp> /s <sp> /v”/qn <sp> /l*v <sp>
C:\AS543.log <sp> <Required Arguments> <sp> [Optional Arguments]”
<sp> denotes one or more „space‰ characters. The Table 1 on page 125 describes each
of the command tokens listed above.
Table 1 Command description

Token Description

start The Windows command that launches the

executable file (AutoStart Installer).

/wait Blocks the Start command until Silent Install

completes.

/s Performs installation in silent mode.

/v Passes all options and arguments between “...” to the

installer.

/qn Runs the installer in silent mode.

/l*v Generates the log file in a verbose format. You can

specify a custom log file name. Under Command
Syntax, the log file has been defined to C:\AS543.log

"Required Each argument is a <name>=<value> pair. All the

arguments for required arguments must be passed to the Installer.
Silent Installation
on Windows"

"Optional Each argument is a <name>=<value> pair. These

arguments for are optional arguments. You can pass them based
Silent Installation on a need basis.
on Windows"

Note the following important points:

◆ Do not use spaces between /v”/qn while invoking the installer.

Silent Installation on Windows 125

Silent Install

◆ All arguments specified in the section „Required Arguments for Silent

Installation‰ must be passed.
◆ If any of the arguments use double quotes („..‰), the quotes need to be escaped by
Â\Ê.
◆ You must login with administrator credentials to install AutoStart.
◆ You must reboot the node after installation.
◆ You may create your own script files, instead of passing arguments from the
command line.

Required arguments for Silent Installation on Windows

The required arguments that you must specify are listed in Table 2 on page 126

Table 2 Required arguments for Silent Installation on Windows

Argument heading Possible values Description

AS_DOMAINNAME AutoStart domain name

INSTALLDIR C:\Program Files\ EMC\AutoStart Folder where AutoStart must be

installed. You can specify your own
custom paths.

AS_NODENAMELOCAL Name of the node where the

installation is done.

AS_FIRSTNODE 1 or 0 For installation on the first node

(primary node) in the domain, you
must set the value to 1. For
installation on subsequent nodes,
you must set the value to 0.

AS_NODENAMEPRIMARY Primary Node Name This argument is used to specify

the primary node name while
doing the installation on
subsequent nodes.

Note: Installation on the primary

node does not require this
argument.

126 EMC AutoStart Installation Guide

 Silent Install

Table 2 Required arguments for Silent Installation on Windows

Argument heading Possible values Description

ADDLOCAL ALL / Agent / Console54 Specify this value as:

• ALL for complete installation
• Agent for Agent installation
only
• Console54 for Console
installation only

USERNAME Administrator The person with administrator

credentials who performs the
installation.

AS_LICENSEKEYBASE Eval license is AMEVAL. AutoStart base product license.

User could specify the eval license
or the product license procured
from EMC.

Note: Licenses must be specified

only during the primary node (first
node) installation. Installation on
subsequent nodes does not
require the license.

Optional arguments for Silent Installation on Windows

Optional arguments that you may specify during installation are listed in the Table 3
on page 127

Note: License keys are optional arguments and should be specified only during the primary
node (first node) installation.

Table 3 Optional arguments for Silent Installation

Argument heading Possible values Description

AS_PORTNUMBER 8042 AutoStart uses default port numbers

8042 through 8045. If unavailable,
you must specify a different starting
port number for AutoStart.

AS_LICENSEKEYEXCHANGE2003 Eval license is E3EVAL. By default, no license is installed for

the Exchange 2003 module. You may
specify the license at install time or
configure later.

AS_LICENSEKEYEXCHANGE2007 Eval license is E7EVAL. By default, no license is installed for

the Exchange 2007 module. You may
specify the license at install time or
configure later.

AS_LICENSEKEYEXCHANGE2010 Eval license is EAEVAL By default, no license is installed for

the Exchange 2007 module. You may
specify the license at install time or
configure later.

Silent Installation on Windows 127

Silent Install

Argument heading Possible values Description

AS_LICENSEKEYMIRRORVIEW Eval license is MVEVAL. By default, no license is installed for

the Exchange 2003 module. You may
specify the license at install time or
configure later.

AS_LICENSEKEYORACLE31 Eval license is OWEVAL. By default, no license is installed for

the Oracle module. You may specify
the license at install time or configure
later.

AS_LICENSEKEYSQLSERVER2005 Eval license is S5EVAL By default, no license is installed for

the SQL 2005 module. You may
specify the license at install time or
configure later.

AS_LICENSEKEYSRDF Eval license is EMEVAL By default, no license is installed for

the SRDF module. You may specify
the license at install time or configure
later.

AS_MIRRORADDRESSIP IP Address The local IP address that is used for

the dedicated Mirroring link. You
could specify the Mirroring IP at
install time or configure later.

Examples The following examples refer to installation on a 64-bit Windows OS. The installer
captures all the log messages in the installer log file. This log file contains all the
command line arguments passed to installer and the installation status.
Steps for First Node with no optional arguments

1. At the # prompt, type:

cd <EXE_LOCATION_FOLDER>
2. Type the following command:

start /wait EAS543_WIN_x64.exe /s /v"/qn /L*v

C:\AutoStart.log AS_DOMAINNAME=<domain_name>
INSTALLDIR=\"C:\Program Files\EMC\AutoStart\"
AS_NODENAMELOCAL=<host_name> AS_FIRSTNODE=1
USERNAME=<logged_in_user_name> AS_LICENSEKEYBASE=AMEVAL
AS_MIRRORADDRESSIP=<Node Mirroring Line> ADDLOCAL=ALL
REBOOT=Suppress

Step 2 installs the software.

3. Type shutdown –r and press Enter to reboot the node.
Steps for Second Node with No Optional Arguments:

1. At the # prompt type:

cd <EXE_LOCATION_FOLDER> and press Enter.
2. Type the following command:

start /wait EAS543_WIN_x64.exe /s /v"/qn /L*v

C:\AutoStart.log AS_DOMAINNAME=<domain_name>
INSTALLDIR=\"C:\Program Files\EMC\AutoStart\"
AS_NODENAMELOCAL=<host_name> AS_FIRSTNODE=0

128 EMC AutoStart Installation Guide

 Silent Install

AS_NODENAMEPRIMARY=<Primary_Node_Name>
USERNAME=<logged_in_user_name> AS_MIRRORADDRESSIP=<Node
Mirroring Line> ADDLOCAL=ALL REBOOT=Suppress

Step 2 installs the software on the second node.

3. Type shutdown –r and press Enter to reboot the node.
Steps for only Agent installation (First Node):
1. At the # prompt, type:
cd <EXE_LOCATION_FOLDER>
2. Type the following command:

start /wait EAS543_WIN_x64.exe /s /v"/qn /L*v

C:\AutoStart.log AS_DOMAINNAME=<domain_name>
INSTALLDIR=\"C:\Program Files\EMC\AutoStart\"
AS_NODENAMELOCAL=<host_name> AS_FIRSTNODE=1
USERNAME=<logged_in_user_name> AS_LICENSEKEYBASE=AMEVAL
AS_MIRRORADDRESSIP=<Node Mirroring Line> ADDLOCAL=Agent
REBOOT=Suppress

Step 2 installs the software.

3. Type shutdown –r and press Enter to reboot the node.
Steps for only Agent installation (Second Node):

1. At the # prompt, type:

cd <EXE_LOCATION_FOLDER> and press Enter.
2. Type the following command:

start /wait EAS543_WIN_x64.exe /s /v"/qn /L*v

C:\AutoStart.log AS_DOMAINNAME=<domain_name>
INSTALLDIR=\"C:\Program Files\EMC\AutoStart\"
AS_NODENAMELOCAL=<host_name> AS_FIRSTNODE=0
AS_NODENAMEPRIMARY=<Primary_Node_Name>
USERNAME=<logged_in_user_name> AS_MIRRORADDRESSIP=<Node
Mirroring Line> ADDLOCAL=Agent REBOOT=Suppress

Step 2 installs the software on the second node.

3. Type shutdown –r and press Enter to reboot the node.
Steps for only Console installation:

1. At the # prompt, type:

cd <EXE_LOCATION_FOLDER> and press Enter.
2. Type the following command:
start /wait EAS543_WIN.exe /s /v"/qn /L*v C:\AutoStart.log
INSTALLDIR=\"C:\Program
Files\EMC\AutoStart\"AS_DOMAINNAME=<domain_name>USERNAME=<l
ogged_in_user_name> ADDLOCAL=Console54

Silent Installation on Windows 129

Silent Install

Steps for First Node with Optional Arguments:

1. At the # prompt, type:

cd <EXE_LOCATION_FOLDER> and press Enter.
Type the following command:

start /wait EAS543_WIN_x64.exe /s /v"/qn /L*v

C:\AutoStart.log AS_DOMAINNAME=<domain_name>
INSTALLDIR=\"C:\Program Files\EMC\AutoStart\"
AS_NODENAMELOCAL=<host_name> AS_FIRSTNODE=1 ADDLOCAL=ALL
USERNAME=clusteradmin AS_LICENSEKEYBASE=AMEVAL
AS_LICENSEKEYEXCHANGE2003=E3EVAL
AS_LICENSEKEYEXCHANGE2007=E7EVAL
AS_LICENSEKEYMIRRORVIEW=MVEVAL AS_LICENSEKEYORACLE31=OWEVAL
AS_LICENSEKEYSQLSERVER2005=S5EVAL AS_LICENSEKEYSRDF=EMEVAL
AS_MIRRORADDRESSIP=<Node Mirroring Line>"
2. Type shutdown –r and press Enter to reboot the node.
Steps for Second Node with Optional Arguments:

1. At the # prompt, type:

cd <EXE_LOCATION_FOLDER> and press Enter.
2. Type the following command:

start /wait EAS543_WIN_x64.exe /s /v"/qn /L*v

C:\AutoStart.log AS_DOMAINNAME=<domain_name>
INSTALLDIR=\"C:\Program Files\EMC\AutoStart\"
AS_NODENAMELOCAL=<host_name> AS_FIRSTNODE=0
AS_NODENAMEPRIMARY=<primary_Node_Name> ADDLOCAL=ALL
USERNAME=<logged_in_user_name> AS_MIRRORADDRESSIP=<Node
Mirroring Line>"
3. Type shutdown –r and press Enter to reboot the node.

130 EMC AutoStart Installation Guide

 Silent Install

Silent Upgrade on Windows

Perform the following steps to upgrade AutoStart from 5.4.0 silently:
1. Open the Windows Command shell.
2. Run the AutoStart Installer from the command shell specifying additional
parameters. The exact command syntax to use for invoking the installer is
described in the next section.
3. Type shutdown -r and press Enter to reboot the node.

Command Syntax The command format for silently upgrading AutoStart is described below:
start <sp> /wait <sp> <AutoStart_Installer> <sp>/s<sp>/v”/qn <sp> /l*v <sp>
C:\AS543.log <sp> <Required Arguments> <sp> [Optional Arguments]”
<sp> denotes one or more „space‰ characters. Table 4 on page 131 describes each of
the command tokens listed above.
Table 4 Command description

Token Description

start Launches the executable file (AutoStart

Installer).

/wait This option makes the start command to block

(wait) till the installation is complete.

/s Perform silent installation / upgrade

/v Passes all subsequent arguments to the

installer. All the options and arguments between
“...” are directly passed to the installer.

/qn Runs the installer in silent mode.

/l*v This option generates the log file in a verbose

format. The user can specify a custom log
filename. In the above, the log file has been
defined to C:\AS543.log.

"Required arguments Each argument is a <name>=<value> pair. All

for Silent Upgrade on the required arguments must be passed to the
Windows" Installer.

"Optional arguments Each argument is a <name>=<value> pair.

for Silent Upgrade on These are optional arguments. You can pass
Windows" them based on a need basis.

Required arguments for Silent Upgrade on Windows

The required arguments that you must specify are listed in Table 5 on page 132.

Silent Upgrade on Windows 131

Silent Install

Table 5 Required arguments for Silent Upgrade on Windows

Argument heading Possible values Description

AS_ISUPGRADE 1 Specifies that this is an upgrade that

should be done by the silent
installation procedure.

REBOOT Suppress This argument is used to avoid

automatic reboot.

Optional arguments for Silent Upgrade on Windows

Optional arguments that you may specify during upgrade through silent installation
are listed in Table 6 on page 132.
Table 6 Optional arguments for Silent Upgrade on Windows

Argument heading Possible values Description

INSTALLDIR C:\Program Files\ Folder where AutoStart must be

EMC\AutoStart installed. You can specify your own
custom paths.

Note the following important points:

◆ Do not use spaces between /v"/qn while invoking the installer.
◆ You must login as administrator to upgrade AutoStart.
◆ You must reboot the node for the upgrade to complete.
Example The following examples refer to upgrade on a 64-bit Windows OS. The installer
captures all the log messages in the installer log file. This log file contains all the
command line arguments passed to installer and the status of upgrade.
Steps for Upgrade
1. At the # prompt, type: cd <EXE_LOCATION_FOLDER> and press Enter.
2. Type the following command:
start /wait EAS543_WIN_x64.exe /s /v"/qn /l*v C:\AS.log
INSTALLDIR=\"C:\Program Files\EMC\AutoStart\" AS_ISUPGRADE=1
REBOOT=Suppress"
3. Press Enter. Upgrade process would begin. No user intervention is required.
4. Type shutdown –r and press Enter to reboot the node.

Note: The upgrade procedure is the same for both the primary node and the secondary node.

132 EMC AutoStart Installation Guide

 Silent Install

Silent Uninstallation on Windows

Perform the following steps for an AutoStart Silent Uninstallation on Windows:
1. Open the Windows Command shell.
2. Run the AutoStart Installer from the command shell. The installer needs to be
invoked with the uninstall option. The exact command syntax to use for invoking
the Installer is described in the next section.
3. Type shutdown –r and press Enter to reboot the node. All AutoStart files are
removed.

Command Syntax
The command format for silently uninstalling AutoStart is described below:
start <sp> /wait <sp> <AutoStart_Installer> <sp>/s<sp>/v"/qn <sp> /l*v <sp>
C:\AS543.log<sp> <Required Arguments>”
<sp> denotes one or more „space‰ characters. Table 7 on page 133 describes each of
the command tokens listed above.

Table 7 Command description

Token Description

start The Windows command that launches the executable file (AutoStart Installer).

/wait Blocks the Start command until Silent Install completes.

/s Performs uninstallation in silent mode.

/x Uninstalls the product.

/v Passes all subsequent arguments to the installer. All the options and
arguments between “...” are directly passed to the installer.

/qn Runs the installer in silent mode.

/l*v This option generates the log file in a verbose format. The user can specify a
custom log filename. In the above, the log file has been defined to
C:\AS543.log.

Command description Each argument is a <name>=<value> pair. All the required arguments must
be passed to the Installer.

Required arguments for Silent Uninstallation on Windows

The required arguments that you must specify are listed Table 8 on page 134.

Silent Uninstallation on Windows 133

Silent Install

Table 8 Required arguments for Silent Uninstallation

Argument heading Possible values Description

REBOOT Suppress This argument is used to avoid

automatic reboot.

REMOVE ALL / Agent / Console54 Specify this value as:

• ALL for complete uninstallation
• Agent for Agent uninstallation
only
• Console54 for Console
uninstallation only

Example The following examples refer to uninstallation on a 64-bit Windows OS. The installer
captures all the log messages in the installer log file. This log file contains all the
command line arguments passed to installer and the status of uninstallation.
Steps for Uninstallation
1. At the # prompt, type:
cd <EXE_LOCATION_FOLDER> and press Enter.
2. Type the following command:
start /wait EAS543_WIN_x64.exe /s /v”/qn /L*v C:\AutoStart.log
REMOVE=ALL REBOOT=Suppress”
or
start /wait EAS543_WIN_x64.exe /s /x /v”/qn /L*v C:\AutoStart.log
REBOOT=Suppress”
3. Press Enter. Uninstall messages appear.
4. Type shutdown –r and press Enter to reboot the node.

Note: The Uninstallation procedure is the same for both the primary node and the secondary
node.

134 EMC AutoStart Installation Guide

 Silent Install

Error handling
Errors that occur during a Silent Installation or a Silent Uninstallation are not
reported. For example, if you specify an invalid value for AS_FTDIR which causes the
installation to fail, you will not see any error messages in the command shell.
To ensure a successful installation or uninstallation, proceed as follows:
◆ Execute the echo %errorlevel% command after the completion of the install
procedure.
• A zero value indicates that the installation (or uninstallation) was successful.
Reboot the node for the installation (or uninstallation) to be completed.
• If the above command returns with a non-zero value, then the install
procedure was not successful. Examine the installer log files for errors.

Note: If the tag “1: FAIL/ERROR” is present in the installer log files, it means that some
of the AutoStart custom action executed within the Windows Installer package are
causing errors.

Note: In some cases, uninstallation returns „3010‰ value. This implies that the
requested operation was successful. However, changes will not be effective until the
system is rebooted.

If the Silent Installation is done through user scripts, the script must check for the
error status (%errorlevel%) returned by the AutoStart installer.
For more information on %errorlevel% values and descriptions, visit the following
link:
http://msdn.microsoft.com/en-us/library/aa368543%28v=vs.85%29.aspx

Error handling 135

Silent Install

Silent Installation on Unix/Linux

AutoStart provides a script called install.sh which handles the task of installing,
upgrading and uninstalling AutoStart on all Unix platforms. With special switches, it
also installs AutoStart silently (non-interactively).
1. Open a command shell window.
2. Run the script from the command shell. The script silently installs the product.
The Command Syntax section provides the command syntax, used for invoking
the installer.

Command Syntax The command format for invoking silent install for AutoStart is as follows:
install.sh -s [-a | -c]

Note: You can use the -h switch to display command usage information on screen.

Table 9 on page 136 describes each of the command switches listed above.
Table 9 Switch descriptions

Switch Description

-s Performs installation in silent mode. Installs both

agent and console.

-a Optional: Installs AutoStart agent only.

-c Optional. Installs AutoStart console only.

Note that you must login with administrator credentials to install AutoStart.
Examples The following examples refer to installation on a 64-bit Unix system.
1. At the command prompt, type:
install -s

This installs AutoStart agent and console to the default location.

2. Use the following command to set FT_DIR varieble to install directory:
export FT_DIR=/opt/EMCas543
3. Now navigate to the binary executable directory:
cd $FT_DIR/bin

4. Use the following command to run ft_setup silently on the first node of the cluster:
./ft_setup -domain=<domain name> -hostname=<current hostname>
-port1=8042 -licensekey=<license key> -mailserver=<mail server
name> -primaryagent=<first cluster node name>

5. Use the following command to run ft_setup silently on subsequent nodes of the
cluster:
./ft_setup -domain=<domain name> -hostname=<current hostname>
-port1=8042 -primaryagent=<first cluster node name>

6. Use the following command to run ft_setup silently on the nodes of the cluster to
overwrite previous configuration:

136 EMC AutoStart Installation Guide

 Silent Install

./ft_setup -domain=<domain name> -hostname=<current hostname>

-port1=8042 -primaryagent=<first cluster node name> -upgrade=n
-noprompt=y

7. When all nodes are installed, start AutoStart using:

./ft_startup

Silent Installation on Unix/Linux 137

Silent Install

Silent Uninstallation on Unix/Linux

Uninstalling the AutoStart software removes the installed files, configuration files,
replicated database files, and any temporary files AutoStart writes to the node.

Note: Before you uninstall AutoStart, make sure that you backup any files you would like to
retain, as AutoStart uninstall removes all files, including log and configuration files.

1. Open a command shell window.

2. Run the script from the command shell. The script silently uninstalls the product.
The Command Syntax section provides the command syntax, used for invoking
the installer.

Command Syntax The command format for invoking silent install for AutoStart is as follows:
install.sh -s -u [-a | -c]

Note: You can use the -h switch to display command usage information on screen.

Table 10 on page 138 describes each of the command switches listed above.
Table 10 Switch descriptions

Switch Description

-s -u Performs uninstallation in silent mode. Uninstalls

both agent and console.

-a Optional. Uninstalls AutoStart agent only.

-c Optional. Uninstalls AutoStart console only.

Note that you must login with administrator credentials to uninstall AutoStart.

138 EMC AutoStart Installation Guide

 Silent Install

Limitations
Silent install includes the below limitation.
AutoStart does not support domain names of more than eight characters or domain
names with a hyphen. You must specify the correct argument values.

Limitations 139
Silent Install

140 EMC AutoStart Installation Guide

 10
Invisible Body Tag

Troubleshooting

This chapter contains some of the more common warning and error messages which
may occur during AutoStart installation. The errors are broken up by the type of
action that causes the error message to appear.
This chapter contains the following sections:
◆ Agent installation error messages.................................................. 142
◆ Console startup error messages ..................................................... 144
◆ Agent startup error messages......................................................... 146
◆ Turning off UNIX console messages ............................................. 148
◆ Restoring configuration using DEF file ........................................ 149

Troubleshooting 141
Troubleshooting

Agent installation error messages

This section contains error messages common to the installation process of the
AutoStart agent software. These messages appear during the InstallShield process.

Message
Warning:[Err:13029] Unable to connect due to domain name mismatch.

Description
The domain name specified in the Enter Domain Name dialog box of the AutoStart
installation does not match a domain on the primary node specified for connection.
However, the primary node responds correctly to the supplied port number.

Resolution
Verify the name of the domain name and port setting on the primary agent node by
reading $FT_DIR/config/domain-name-sites. The port setting is the first number
after the colon (:) on any line in the domain-name-sites file. Domain names are
case-sensitive. On the newly installed node, uninstall the AutoStart agent through the
Start Menu AutoStart Domain folder and reinstall specifying the correct domain
name.

Message
Warning: No Agents were found that would accept our connection.
Connection unsuccessfully attempted at: Hostname:IP_address

Description
A domain was not found on the specified port on Hostname.

Resolution
1. Verify that the agent software in the primary agent node specified during setup is
running.
2. This error is likely due to an incorrect port number specified on the Enter Initial
Port Number dialog box of the AutoStart setup. Verify the domain configuration
on the primary node (Hostname) by checking the file
$FT_DIR\config\domain-name-sites on the primary agent node. The correct
port numbers immediately follow the colon (:) on each node entry in the list. Do
not attempt to edit this file. If the port number is incorrect, on the newly installed
node, uninstall the AutoStart agent through the Start Menu AutoStart Domain
folder and reinstall specifying the correct port number.
3. This error also occurs if the node specified as the primary node in the Define
AutoStart Primary Node screen of AutoStart Setup is actually a secondary node.
To verify this, check the Agent Type for the node specified in the Node Console of
the AutoStart console. If this is the case, uninstall the AutoStart agent on the new
node through the Start Menu AutoStart Domain folder and reinstall specifying a
primary node.

Message
Warning: [$FT_DIR/config/domain-name-sites:1]
Invalid host: (Hostname)
[Err:15028] All nodes in sites file are invalid

Description
Error 15028 indicates that there was a problem connecting to Hostname, which is the
node name specified in the Define AutoStart Primary Node dialog box from the
AutoStart installation. This indicates that either the hostname was not entered
correctly or that name resolution failed.

142 EMC AutoStart Installation Guide

 Troubleshooting

Resolution
Verify that the Hostname displayed in the error message matches the string returned
by the hostname command run on the primary node to which a connection was
attempted. If the hostname does not match, on the newly installed node, uninstall the
AutoStart agent through the Start Menu AutoStart Domain folder and reinstall
specifying the correct hostname.
If Hostname does match the primary node's hostname, test the name resolution from
the machine on which you were attempting to install. Run the command ping
Hostname from the command prompt. If the ping command is unable to resolve the
address, update your DNS server with the correct name and IP address for that host.
Using the host file works if only a single network interface exists on this node;
however, if your node supports multiple interfaces, DNS must be used to provide all
pertinent IP addresses.

Agent installation error messages 143

Troubleshooting

Console startup error messages

This section contains error messages common to the AutoStart console during
connection to the AutoStart domain.

Message
Invalid Login

Description
The entered username and/or password are invalid.

Resolution
Enter a valid username and password.

Message
AutoStart console Error: Unable to start the console.
$FT_DIR subdirectory [$FT_CONSOLE_DIR\config] does not contain “sites”
file, or “sites” file could not be opened.

Description
Nodes that are not members of the AutoStart domain may still host the AutoStart
console. However, a domain_name-sites file must be copied to this node from a
primary or secondary member of the domain.

Resolution
Copy a current domain_name-sites file from the $FT_DIR\config directory of a
primary or secondary agent of the domain to the $FT_CONSOLE_DIR\config
directory on the local machine.

Message
AutoStart console Error: Unable to start the console.
Sites file for domain domain_name contained no valid node names.

Description
None of the hostnames listed in the sites file on the local machine are successfully
resolving to IP addresses.

Resolution
Verify name resolution is working on this node, either through a DNS server or by the
hosts file. This node must be able to successfully resolve the name to an IP address.
Verify by running the ping Hostname from a command prompt for each of the nodes
in the domain_name-sites file.

Message
AutoStart console Error
Could not connect to any active Primary Agents in domain domain_name
using port PORT#.

Description
The AutoStart console was able to contact the nodes specified in the sites file.
However, none of the agents on these nodes responded.

Resolution
Verify that the AutoStart domain is running by checking that the agent service is
started on the primary nodes. The serviceÊs state can be checked from the
Windows NT Services Control Panel.
Verify that the local sites file where the AutoStart console is to be run is up to date.
Promotion and demotion of agents could cause a mismatch where there are no longer
any active primary nodes as specified in the local sites file. To update the site file,

144 EMC AutoStart Installation Guide

 Troubleshooting

copy a current domain_name-sites file from the $FT_DIR\config directory of a

primary or secondary agent in the domain to the $FT_CONSOLE_DIR\config directory
on the local machine.

Message
AutoStart console Error: Undefined keysym.

Description
AutoStart on UNIX expects to find a xkeysymdb file. The file is not found in the
expected location.

Resolution
Define the environment variable $XKEYSYMDB to point to the version of the XKeysymDB
file that is shipped with the console. Enter:
setenv XKEYSYMDB $FT_CONSOLE_DIR/misc/XKeysymDB

Message
Warning! The libthread.so on your system is an older version than the
one this VM was tested with. Please read the install documentation for
patch installation instructions. Could not create the Java virtual
machine.

Description
The latest version of libthread.so is not installed. The console may fail to start on
Solaris systems running older versions of libthread.so.

Resolution
Install the latest version of libthread.so. This file is available as a patch from Sun.

Console startup error messages 145

Troubleshooting

Agent startup error messages

This section contains error messages common to the startup of the AutoStart software
agent and Backbone services. The error messages in this section are also posted in the
Windows NT Application Event log.
If either a primary or secondary agent does not start properly, check the Windows
Application Event Log for error messages. For primary agents, events are posted
from two different sources, FTBB (domain_name) for the AutoStart Backbone and
AutoStart (domain_name) for the AutoStart agent. Secondary agent nodes only run the
AutoStart agent, so only AutoStart (domain_name) event log messages are posted.
Always verify that the AutoStart node name matches the TCP/IP hostname of each
node and that name resolution is working.
Application event log error messages display the source, and the event log
description.

Message
AutoStart (domain_name): AutoStart (Agent)
FATAL: An agent can not be started on this node until it is defined as
a member of the domain. Use the management console (ftconsole) to add
the node.

Description
The TCP/IP hostname does not match the AutoStart node name registered in the
AutoStart replicated database.

Resolution
1. If the TCP/IP hostname has been changed inadvertently, reset it through the
Network Control Panel and restart the agent.

Note: Any changes in the Network Control Panel may affect your managed IP address
place holders.

2. If the TCP/IP hostname cannot be changed, then the node must be removed from
the domain and reinstate it in domain with the correct name. If this is a primary
agent node, it must be demoted before it can be removed. Restart the AutoStart
agent on the renamed node and promote to a primary through the console.

Message
AutoStart (domain_name): AutoStart (Agent)
[$FT_DIR/config/domain_name-sites:1] Invalid host: (Hostname)

Description
Hostname cannot be resolved to an IP address.

Resolution
Verify that Hostname is the correct name for a primary node in the AutoStart domain.
If so, configure name resolution on the node where the error occurs so that Hostname
is successfully mapped to an IP address. Run ping Hostname from the command
prompt to verify. This error is not fatal for the agent if it can resolve other hostnames.
However, this causes conflict within the domain since two of the nodes are unable to
communicate.

Message
AutoStart (domain_name): AutoStart (Agent)
FATAL: Cannot read sites file: All nodes in sites file are invalid

146 EMC AutoStart Installation Guide

 Troubleshooting

Description
None of the node entries in the sites file could resolve to IP addresses.

Resolution
Configure name resolution on the node where the error occurs so that all node names
in the $FT_DIR\config\domain_name-sites file are successfully mapped to an IP
address. Run ping Hostname from the command prompt to verify.

Message
FTBB(domain_name): AutoStart Backbone info date can't extract
intersite-hdr

Description
The domain-sites file on this primary node contains a AutoStart node name that
cannot be successfully resolved to an IP address.

Resolution
Test name resolution from this for each node name specified in the local sites file.
Configure DNS to resolve any names that do not properly respond.

Agent startup error messages 147

Troubleshooting

Turning off UNIX console messages

On UNIX platforms, AutoStart information and error messages are automatically
sent to the console by default. These messages can be turned off through the use of
the FT_NO_CONSOLE_TRACE environment variable.
To turn off AutoStart messages:
1. Locate the agent-env.platform_NameOS in \FT_DIR\config directory.
2. Add the following lines to the file:
FT_NO_CONSOLE_TRACE=True
export FT_NO_CONSOLE_TRACE

148 EMC AutoStart Installation Guide

 Troubleshooting

Restoring configuration using DEF file

If customers are facing issues after an automatic upgrade to AutoStart 5.4.3, the
following steps could be followed to manually restore the old configuration:
1. Backup the folder “backup” located under the AutoStart install location. This
folder will be removed if AutoStart 5.4.3 is uninstalled. This folder contains
important information about the previous configuration.
2. Save the current installed licenses. You could view the installed licenses by
selecting the Licensing/Security tab after opening the console. You could also use
the ftcli command listlicenses to view all the installed licenses.

Note: If you started the upgrade process with 5.3 SP5 or earlier, the previous licenses
would have already been saved in the file dbm_lice.txt, located under
“backup\dump”.

3. If you have an upgraded version, first uninstall the 5.4.x version and then do a
fresh installation of the required product version on all the nodes. Refer to section
„Performing Fresh Installation‰ corresponding to the respective platforms.

Note: Please ensure that you are using the same domain name that was used in the
previous installation.

4. To restore the AutoStart configuration corresponding to the previous installation,

the old configuration can be imported using either the AutoStart console or
AutoStart ftcli.
5. Using the AutoStart console:
• Key in the AutoStart licenses by choosing the appropriate product from the
AutoStart console drop down list in the Licensing/Security tab.
• Configure the Mirroring and Failure Detection Setting tab manually. Ensure
that all the mirroring and domain line settings have been configured as before.
• Select the required domain in the AutoStart console and import the
backup.def file located in the “backup” folder. This re-creates the entire
configuration.
6. Using the AutoStart ftcli:
• Import the licenses saved earlier. To import the license use the following ftcli
command:
addLicense –product=<product_name> <License>
Examples:
addLicense –product=PrintServices_1.1 <License>
addLicense –product= oraclewindows_3.1 <License>
addLicense –product=Exchange2003_2.0 <License>
• The previous configuration can be re-created by importing the backup.def
file, located in the “backup” folder. To import the def file use the following ftcli
command:
import <PATH >/backup.def –skipfail

Restoring configuration using DEF file 149

Troubleshooting

WARNING
If the previous setup had an EMC mirroring data source, the data source would be
created afresh and hence a complete sync would be required when attached. This
would be automatically done when the RG is brought online. So a longer
maintenance window would be required. If a SRDF or a Mirrorview data source was
used, a discovery would be performed during the import operation of the def file.

150 EMC AutoStart Installation Guide

 Index

A processes and services 2-4

Agent 1-2
installation E
Solaris 5-7, 6-7, 7-7, 8-7, 9-7, 10-7 envcsh file
installation troubleshooting 11-2 Solaris 5-9, 6-9, 7-9, 8-9, 9-9, 10-9
primary 1-3 Environment variable files
secondary 1-3 Solaris 5-9, 6-9, 7-9, 8-9, 9-9, 10-9
shutting down Environment variables
Solaris 5-11, 6-11, 7-12, 8-11, 9-11, 10-11 Solaris 5-5, 5-7, 5-8, 6-5, 6-7, 7-5, 7-7, 8-5, 8-7, 8-8, 9-5,
Windows 2000 3-14 9-7, 10-5, 10-7
Windows NT 3-14 $FT_DIR 5-11, 6-10, 7-10, 8-10, 9-10, 10-10
starting envsh file
Solaris 5-9, 6-9, 7-9, 8-9, 9-9, 10-9 Solaris 5-9, 6-9, 7-9, 8-9, 9-9, 10-9
startup parameters
Solaris 5-11, 6-11, 7-12, 8-11, 9-11, 10-10, 10-11
Windows 3-12 F
Agent troubleshooting 11-6 FT_DOMAIN environment variable
AutoStart Console Solaris 5-5, 5-8, 6-5, 6-7, 7-5, 7-7, 8-5, 8-8, 9-5, 9-7, 10-5,
troubleshooting 11-4 10-7
AutoStart Console installation ft_setup command
Solaris 5-12, 6-12 Solaris 5-8, 6-8, 7-8, 8-8, 9-8, 10-8
AutoStart Console troubleshooting 11-4 ft_shutdown command (UNIX)
Solaris 5-11, 6-11, 7-12, 8-11, 9-11, 10-11
ft_startup command
C Solaris 5-9, 6-9, 7-9, 8-9, 9-9, 10-9
Commands ft_uninstall command
Solaris Solaris 5-15, 6-15, 7-15, 8-14, 9-14, 10-14
ft_setup 5-8, 6-8, 7-8, 8-8, 9-8, 10-8
ft_shutdown 5-11, 6-11, 7-12, 8-11, 9-11, 10-11
ft_startup 5-9, 6-9, 7-9, 8-9, 9-9, 10-9 I
ft_uninstall 5-15, 6-15, 7-15, 8-14, 9-14, 10-14 Installation
verify_install 5-8, 6-8, 7-8, 8-8, 9-8, 10-8 agent
Solaris 5-7, 6-7, 7-7, 8-7, 9-7, 10-7
AutoStart Console
D Solaris 5-12, 6-12
DNS servers for Windows 2000 3-2, 8-2, 9-2, 10-2
using multiple 2-7 for Windows NT 3-2, 8-2, 9-2, 10-2
Domain Installation troubleshooting 11-2
defined 1-2 IP addresses
Domain planning planning 2-3
IP addresses 2-3
network integrity 2-8
network issues 2-5 N
primary vs. secondary agents 2-2 Network integrity

EMC AutoStart Installation Guide 151

Index

checking 2-8 Solaris 5-15, 6-15, 7-14, 8-13, 9-13, 10-13

Network issues Solaris 5-15, 6-15, 7-14, 8-13, 9-13, 10-13
checking integrity 2-8 Upgrade
integrity 2-8 Solaris 5-4, 6-4, 7-4, 8-4, 9-4, 10-3
planning 2-5 Windows 2000 3-6
Nodes 1-2 Windows NT 3-6
-noisolationdetection agent startup parameter
Solaris 5-11, 6-11, 7-12, 8-11, 9-11, 10-10
Windows 3-12
Windows 2000 3-12
Windows NT 3-12

P
Primary agents 1-3
planning 2-2
Processes
planning 2-4

R
-realtime agent startup parameter
Solaris 5-11, 6-11, 7-12, 8-11, 9-11, 10-11

S
Secondary agents 1-3
planning 2-2
Services
planning 2-4
Shutting down the agent
Solaris 5-11, 6-11, 7-12, 8-11, 9-11, 10-11
Windows 2000 3-14
Windows NT 3-14
Starting
agent
Solaris 5-9, 6-9, 7-9, 8-9, 9-9, 10-9
Windows 2000 3-12
Windows NT 3-12
Startup parameters
-noisolationdetection
Solaris 5-11, 6-11, 7-12, 8-11, 9-11, 10-10
Windows 3-12
Windows 2000 3-12
Windows NT 3-12
-realtime
Solaris 5-11, 6-11, 7-12, 8-11, 9-11, 10-11
System Requirements
Solaris 5-3, 6-3, 7-3, 8-3, 9-3, 10-3
Windows 2000 3-3
Windows NT 3-3

T
Troubleshooting
agent installation 11-2
agent startup 11-6
AutoStart Console startup 11-4

U
Uninstall
Agent

152 EMC AutoStart Installation Guide