VERITAS Cluster Server for UNIX,

Fundamentals

Lesson 7
Preparing Services for VCS
Course Overview
 Lesson 1: High Availability Concepts
 Lesson 2: VCS Building Blocks
 Lesson 3: Preparing a Site for VCS
 Lesson 4: Installing VCS
 Lesson 5: VCS Operations
 Lesson 6: VCS Configuration Methods
 Lesson 7: Preparing Services for VCS
 Lesson 8: Online Configuration
 Lesson 9: Offline Configuration
 Lesson 10: Sharing Network Interfaces
 Lesson 11: Configuring Notification
 Lesson 12: Configuring VCS Response to Faults
 Lesson 13: Cluster Communications
 Lesson 14: System and Communication Faults
 Lesson 15: I/O Fencing
 Lesson 16: Troubleshooting
Lesson Topics and Objectives

Topic After completing this lesson, you

will be able to:
Preparing Applications for Prepare applications for the VCS
VCS environment.
Performing One-Time Perform one-time configuration tasks.
Configuration Tasks
Testing the Application Test the application services before
Service placing them under VCS control.
Stopping and Migrating a Stop resources and manually migrate a
Service service.
Validating the Design Validate the design worksheet using
Worksheet configuration information.
Topic 1: Preparing Applications for VCS

After completing this topic, you

will be able to prepare
applications for the VCS
environment.
Application Service Overview

IP Address

NIC
Network
End Users

Process
File System
Application
Volume
Disk Group

Storage
Identifying Components

Application
 Start, stop, and monitor processes
 File locations Process
Storage
IP Mount
Network  IP addresses
 Network interfaces
NIC Volume

DiskGroup

 Disk group and volume devices

 File systems
 Mount point directories
Topic 2: Performing One-Time
Configuration Tasks

After completing this topic, you

will be able to perform one-time
configuration tasks.
Configuration and Migration Procedure
Before configuring VCS in production environments:
 Fully test each service on each startup or failover
target system.
 Configure services on a test cluster, if possible.

Perform one-time
configuration tasks on
each system.

N
Start, verify, and Y
More Ready for
stop services on
Systems? VCS
one system at a time.
Documenting Attributes
As you configure components:
 Use a design worksheet to document details needed to
configure VCS resources.
 Note differences among systems, such as network
interface device names.

Resource Definition Sample Value

Service Group Name DemoSG
Resource Name DemoIP Process

Resource Type IP
IP Mount
Required Attributes
Device eri0 NIC Volume
Solaris
Address 10.10.21.198
Optional Attributes DiskGroup
NetMask 255.0.0.0
Checking Resource Attributes
While documenting the configuration, verify that:
 Recorded attribute values match configured values
 All required attributes have values
Resource Definition Sample Value
Process Service Group Name DemoSG
Resource Name DemoMount
192.... /Demo Resource Type Mount
Fix!
Required Attributes
eri0 DemoVol
MountPoint /demo
BlockDevice /dev/vx/dsk. . .
DemoDG
FSType vxfs
FsckOpt -y
BARGs: Optional Attributes Solaris
MountOpt
Solaris AIX HP-UX Linux
Configuring Shared Storage
From One System
Initialize disks. vxdisksetup -i disk_dev

Create a disk group. vxdg init DemoDG DemoDG01=disk_dev

Create a volume. vxassist -g DemoDG make DemoVol 1g

Make a file system. mkfs args vxfs /dev/vx/rdsk/DemoDG/DemoVol

Make a mount point. mkdir /Demo Each System

Volume Manager Example

Solaris AIX HP-UX Linux

Configuring the Application
Install and configure applications identically on each
target system.
 Determine file locations: Resource Definition Sample Value
– Shared or local storage Service Group Name DemoSG

– Binaries, data, Resource Name DemoProcess

configuration Resource Type Process
 Follow application Required Attributes
installation and PathName /opt/orderproc
configuration guidelines. Optional Attributes
 Identify startup, monitor, Arguments start
and shutdown
procedures.
Topic 3: Testing the Application Service

After completing this topic, you

will be able to test the application
services before placing them
under VCS control.
Testing the Application Service

N
Ready for
Bring up resources. S1 VCS

More
Start up all resources
Systems?
in dependency order.
Y
Shared storage

Virtual IP address S2
S2…Sn

Stop resources.
Application software

Test the application.

Test the application.

Stop resources. Bring up resources.

Bringing Up Resources: Online
To bring shared storage resources online:
1. Import the disk group:
vxdg –t import DemoDG
2. Start the volume:
vxvol –g DemoDG start DemoVol
3. Mount the file system:
Solaris
mount –F vxfs /dev/vx/dsk/DemoDG/DemoVol /Demo

 Do not automount file systems controlled by VCS.

 Solaris example: Verify /etc/vfstab has no entries
 Virtual IP Addresses

http://eweb.com Failed

DNS

web.com = 10.10.21.198

ifconfig eri0 addif 10.10.21.198 up

Virtual IP configured by IP resource eri0:1

S2
Admin IP configured at boot eri0

10.10.21.8
S1
Solaris
 Virtual IP Address Migration

http://eweb.com

DNS
ifconfig eri0 addif 10.10.21.198 up

web.com = 10.10.21.198 Virtual IP configured by IP resource

eri0:1

eri0 Admin IP configured at boot

Failed 10.10.21.9
S2

After Failover
S1
Bringing Up Application (Virtual) IP Addresses
An application IP address is:
 Added as virtual IP address to a virtual public
network device
 Associated with an application service
 Resolved by a naming service
 Controlled by the high availability software
 Migrated to other systems by VCS
 Also called service group or floating IP addresses

Procedure Solaris AIX HP-UX Linux

Starting the Application
Manually start the application for testing
purposes.
 Example command line for an application:
/opt/orderproc start
 Ensure no automatic startup files exist:
– Solaris: /etc/rc2.d
– HP-UX: /sbin/rc2.d
– Linux: /etc/rc3.d
– AIX: /etc/rc.d/rc2.d
Verifying Resources: Monitor

Verify the disk group. vxdg list DemoDG

Verify the volume. dd if=/dev/vx/rdsk/DemoDG/DemoVol \

of=/dev/null count=1 bs=128

Verify the file system. mount | grep /Demo

Verify the NIC. ping 10.10.21.8

Verify the virtual IP. ifconfig –a | grep 10.10.21.198

Solaris
Verify the application. ps -ef | grep "/opt/orderproc"
Testing the Integrated Components
Test the application real-world scenarios.
 Involve key users of the application.
 Test network connectivity from client
systems on different subnets. Failed

192.168.21.198
S2

S1
Topic 4: Stopping and Migrating a Service

After completing this topic, you

will be able to stop resources and
manually migrate a service.
Stopping Application Components: Offline
Stop resources in order
from top down.
Stop the application.

/opt/orderproc stop

Take down the virtual IP. Unmount the file system.

ifconfig eri0 removeif 10.10... umount /Demo

Solaris
Stop the volume.

vxvol –g DemoDG stop DemoVol

Deport the disk group.

vxdg deport DemoDG

Manually Migrating an Application Service

IP Address
Network
NIC

Process
Application
File
S1 System S2

Storage
Topic 5: Validating the Design Worksheet

After completing this topic, you

will be able to validate the design
worksheet using configuration
information.
Documenting Resource Dependencies
 Determine parent and child relationships according
to service group diagrams.
 Verify that the dependencies match the online and
offline tests you performed.

Resource Dependency Definition

Service Group DemoSG
Process Parent Resource Requires Child Resource
IP Mount DemoVol DemoDG
DemoMount DemoVol
NIC Volume
DemoIP DemoNIC
DemoProcess DemoMount
DiskGroup DemoProcess DemoIP
Validating Service Group Attributes

Service Group Definition Sample Value

Startup System Group DemoSG
Required Attributes
FailOverPolicy Priority
DemoSG SystemList S1=0, S2=1
Parallel 0
S2
Optional Attributes
AutoStartList S1
S1
Failover System
Lesson Summary
 Key Points
– Prepare each component of a service and
document attributes.
– Test services in preparation for configuring
VCS service groups.
 Reference Materials
– VERITAS Cluster Server Bundled Agents
Reference Guide
– VERITAS Cluster Server User's Guide
What Did You Learn?
 You are about to be
asked a series of
questions related to the
current topic.
 Click Answer to see
solutions.
One of the most important tasks in preparing
application services for VCS is:
A. Starting and stopping the service under VCS
control before creating the SystemList
B. Making sure all resources in the service group
can be probed
C. Manually testing each service on each system
that is a startup or failover target before placing
the service under VCS control
D. Testing all services on the same system
before placing under VCS control

Answer
One of the most important tasks in preparing
application services for VCS is:
A. Starting and stopping the service under VCS
control before creating the SystemList
B. Making sure all resources in the service group
can be probed
C. Manually testing each service on each system
that is a startup or failover target before placing
the service under VCS control
D. Testing all services on the same system
before placing under VCS control
The correct answer is C.

Next >>
When testing resource components, start the
components:
A. In any order; the order for starting resources
is irrelevant
B. Based on whether they are storage or network
resources
C. According to the inherent component
dependencies
D. From the top of the resource dependency tree

Answer
When testing resource components, start the
components:
A. In any order; the order for starting resources
is irrelevant
B. Based on whether they are storage or network
resources
C. According to the inherent component
dependencies
D. From the top of the resource dependency tree
The correct answer is C.

Next >>
In VCS, application IP addresses are added as
virtual IP addresses to the network interface,
and are:
A. Configured to come up outside of VCS control
when the application comes up
B. Migrated to other systems if the current
system or application service fails
C. The same as the Administrative IP address for
each system
D. Configured to come up when the operating
system is started

Answer
In VCS, application IP addresses are added as
virtual IP addresses to the network interface,
and are:
A. Configured to come up outside of VCS control
when the application comes up
B. Migrated to other systems if the current
system or application service fails
C. The same as the Administrative IP address for
each system
D. Configured to come up when the operating
system is started
The correct answer is B.

Next >>
Why is an administrative IP address required if
HA services require network access?
A. The application (virtual) IP address cannot be
configured without an administrative IP address.
B. The administrative IP address migrates between
systems during failover.
C. The Web GUI uses the administrative IP address
to initiate failover.
D. VCS updates the DNS server with the
administrative IP address during failover.

Answer
Why is an administrative IP address required if
HA services require network access?
A. The application (virtual) IP address cannot be
configured without an administrative IP address.
B. The administrative IP address migrates between
systems during failover.
C. The Web GUI uses the administrative IP address
to initiate failover.
D. VCS updates the DNS server with the
administrative IP address during failover.
The correct answer is A.

Next >>
Which shared storage configuration task must
be performed on each system?
A. Creating the file system.
B. Creating a volume.
C. Making a disk group.
D. Making a mount point.

Answer
Which shared storage configuration task must
be performed on each system?
A. Creating the file system.
B. Creating a volume.
C. Making a disk group.
D. Making a mount point.
The correct answer is D.

Next >>
Lab 7: Preparing Application Services

/bob1/loopy /sue1/loopy

NIC while true while true NIC

do do
IP Address echo “…” echo “…” IP Address
done done

bobDG1 sueDG1
/bob1 bobVol1
disk1 sueVol1 /sue1
disk2

Disk/Lun Disk/Lun

See next slide for classroom values.

Lab 7 Assignments
Fill in the table at the beginning of the Lab 7 in
Appendix A or B.
 Source location for loopy script:
______________________________________________

 Disk assignments:
– Node 1:
______________________________________________
– Node 2:
______________________________________________
End of Presentation
Appendix

This appendix contains slides that are platform

specific, and may be reviewed per the viewer’s
discretion and interest, or you may optionally end
the presentation now.
Configuring Shared Storage on Solaris

From One System

Initialize disk(s). vxdisksetup -i c1t8d0

Create a disk group. vxdg init DemoDG DemoDG01=c1t8d0

Create a volume. vxassist -g DemoDG make DemoVol 1g

Make a file system. mkfs -F vxfs /dev/vx/rdsk/DemoDG/DemoVol

Make a mount point. mkdir /Demo Each System

Configuring Shared Storage on AIX

From One System

Initialize disk(s). vxdisksetup -i c1t8d0

Create a disk group. vxdg init DemoDG DemoDG01=c1t9d0

Create a volume. vxassist -g DemoDG make DemoVol 1g

Make a file system. mkfs -V vxfs /dev/vx/rdsk/DemoDG/DemoVol

Make a mount point. mkdir /Demo Each System

Volume Manager Example

Configuring Shared Storage on HP-UX

From One System

Initialize disk(s). vxdisksetup -i c1t8d0

Create a disk group. vxdg init DemoDG DemoDG01=c1t8d0

Create a volume. vxassist -g DemoDG make DemoVol 1g

Make a file system. mkfs -F vxfs /dev/vx/rdsk/DemoDG/DemoVol

Make a mount point. mkdir /Demo Each System

Volume Manager Example

Configuring Shared Storage on Linux

From One System

Initialize disk(s). vxdisksetup -i sda

Create a disk group. vxdg init DemoDG DemoDG01=sda

Create a volume. vxassist -g DemoDG make DemoVol 1g

Make a file system. mkfs -t vxfs /dev/vx/rdsk/DemoDG/DemoVol

Make a mount point. mkdir /Demo Each System

Volume Manager Example

Configuring an Application IP Address on
Solaris
To set up manually for testing purposes:
1. Plumb the virtual interface and bring up the IP
on the next available logical interface:
ifconfig eri0 addif 10.10.21.198 up
2. Edit /etc/hosts to assign a virtual hostname
(application service name) to the IP address.
10.10.21.198 demo_services
Configuring an Application IP Address on AIX
To set up manually for testing purposes:
1. Create an alias for the virtual interface and bring up
the IP on the next available logical interface:
ifconfig en1 inet 10.10.21.198 netmask \
255.0.0.0 alias
2. Edit /etc/hosts to assign a virtual hostname
(application service name) to the IP address.
10.10.21.198 demo_services
Configuring an Application IP Address on HP-
UX
To set up manually for testing purposes:
1. Configure IP address using the ifconfig
command.
ifconfig lan2:1 inet 10.10.21.198
3. Use ifconfig to manually configure the IP
address to test the configuration without rebooting.
ifconfig lan2:1 up
2. Edit /etc/hosts and assign a virtual host name
(application service name) to the virtual IP address.
10.10.21.198 demo_services
Configuring an Application IP Address on Linux
Device eth0:1 is used for the first virtual IP
address on the eth0 interface, eth0:2 is used for
the second IP address.
1. Configure the IP address using the ifconfig
command.
ifconfig eth0:1 10.10.21.198
ifconfig eth0:1 up
2. Edit /etc/hosts to assign a virtual host name
(application service name) to the IP address.
10.10.21.198 demo_services
Configuring an Administrative IP Address
For public network access to high availability services,
you must configure an administrative IP address
associated with the physical network interface.
 Each system needs a unique administrative IP address for
each interface.
 Configure the operating system to bring up the
administrative IP address during system boot.
 The IP addresses are used by VCS to monitor network
interfaces.
 These addresses are also sometimes referred to as base,
maintenance, or test IP addresses.
The administrative IP address may already be
configured and only needs to be verified.

Procedure Solaris AIX HP-UX Linux

Configuring an Administrative IP Address on
Solaris
1. Create /etc/hostname.interface with the desired
interface name so the IP address is configured during
system boot:
train14_eri0
2. Edit /etc/hosts and assign an IP address to the
interface name.
192.12.25.3 train14_eri0
3. Use ifconfig to manually configure the IP address to
test the configuration without rebooting:
ifconfig eri0 inet 192.12.25.3 netmask 255.255.255.0 +
A
ifconfig eri0 up
Configuring an Administrative IP Address on
AIX
1. Use SMIT or mktcpip to configure the IP address to
come up during system boot.
2. Edit /etc/hosts and assign an IP address to the
interface name.
192.12.25.3 train14_en1
3. Use ifconfig to manually configure the IP address or
it will be configured during the next reboot.
ifconfig en1 inet 192.12.25.3 netmask 255.255.255.0 +
ifconfig en1 up
Configuring an Administrative IP Address on
HP-UX
1. Add an entry in /etc/rc.config.d/netconf to include the
configuration information for the interface.
INTERFACE_NAME[0]=lan2
IP_ADDRESS[0]=192.12.25.3
SUBNET_MASK[0]=“255.255.255.0”
BROADCAST_ADDRESS[0]=“”
DHCP_ENABLE[0]=“0”
2. Edit /etc/hosts and assign an IP address to the interface name.
192.12.25.3 train14_lan2
3. Use ifconfig to manually configure the IP address to test the
configuration without rebooting:
ifconfig lan2 inet 192.12.25.3 netmask 255.255.255.0
ifconfig lan2 up
Configuring an Administrative IP Address on
Linux
1. Add an entry in the appropriate file in
/etc/sysconfig/networking/devices to include the interface.
# cd /etc/sysconfig/networking/devices
# ls
ifcfg-eth0 ifcfg-eth1 ifcfg-eth2 ifcfg-eth3
# more ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
BROADCAST=192.12.25.3
IPADDR=192.12.25.3
NETMASK=255.255.255.0
NETWORK=192.12.25.0
. . .
2. Edit /etc/hosts and assign an IP address to the interface name.
192.12.25.3 train14_lan2
3. Use ifconfig to manually configure the IP address to test the
configuration without rebooting:
ifconfig eth2 192.12.25.3 netmask 255.255.255.0