You are on page 1of 252

Veritas Cluster

Server 6.0 for UNIX:
Cluster Management

100-002685-E

COURSE DEVELOPERS

Bilge Gerrits
Steve Hoffer
Siobhan Seeger
Pete Toemmes

LEAD SUBJECT MATTER
EXPERTS

Graeme Gofton
Sean Nockles
Brad Willer

TECHNICAL
CONTRIBUTORS AND
REVIEWERS

Copyright © 2012 Symantec Corporation. All rights reserved.

Geoff Bergren
Kelli Cameron
Tomer Gurantz
Anthony Herr
James Kenney
Gene Henriksen
Bob Lucas
Paul Johnston
Rod Pixley
Clifford Barcliff
Danny Yonkers
Antonio Antonucci
Satoko Saito
Feng Liu

2

Copyright © 2012 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, and VERITAS are trademarks or
registered trademarks of Symantec Corporation or its affiliates in
the U.S. and other countries. Other names may be trademarks of
their respective owners.
THIS PUBLICATION IS PROVIDED “AS IS” AND ALL
EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS
AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR
INCIDENTAL OR CONSEQUENTIAL DAMAGES IN
CONNECTION WITH THE FURNISHING, PERFORMANCE,
OR USE OF THIS PUBLICATION. THE INFORMATION
CONTAINED HEREIN IS SUBJECT TO CHANGE WITHOUT
NOTICE.
No part of the contents of this book may be reproduced or
transmitted in any form or by any means without the written
permission of the publisher.
Veritas Cluster Server 6.0 for UNIX: Cluster Management
Symantec Corporation
World Headquarters
350 Ellis Street
Mountain View, CA 94043
United States
http://www.symantec.com

Table of Contents
Course Introduction
Lesson 1: Service Group Dependencies
Common application relationships ............................................................... 1-3
Service group dependencies........................................................................ 1-7
Service group dependency examples .......................................................... 1-9
Configuring service group dependencies ................................................... 1-12
Alternative methods of controlling interactions........................................... 1-16
Lesson 2: Reconfiguring Cluster Membership
Adding a system to a cluster ........................................................................ 2-3
Merging clusters ........................................................................................... 2-6
Additional reconfiguration tasks ................................................................. 2-10
Lesson 3: Startup and Failover Policies
Startup rules and policies ............................................................................. 3-3
Failover rules and policies.......................................................................... 3-10
Limits and Prerequisites ............................................................................. 3-18
Modeling startup and failover policies ........................................................ 3-22
Lesson 4: Alternate Network Configurations
Multiple service groups with NIC resources ................................................. 4-3
Multiple public interfaces .............................................................................. 4-8

Copyright © 2012 Symantec Corporation. All rights reserved.

Lesson 5: High Availability in the Enterprise
Veritas Operations Manager ........................................................................ 5-3
Disaster recovery enhancements................................................................. 5-8
Virtualization support.................................................................................. 5-15

3

Appendix A: Labs
Lab 1: Service group dependencies............................................................ A-3
Lab 2: Merging clusters .............................................................................. A-13
Lab 3: Failover policies............................................................................... A-25
Lab 4: Creating a parallel network service group ....................................... A-37
Appendix B: Lab Solutions
Lab 1: Service group dependencies............................................................ B-3
Lab 2: Merging clusters .............................................................................. B-37
Lab 3: Failover policies............................................................................... B-65
Lab 4: Creating a parallel network service group ....................................... B-89
Appendix C: Supplemental Content
Service group dependencies—Failover process......................................... C-2

Table of Contents

i
Copyright © 2012 Symantec Corporation. All rights reserved.

Copyright © 2012 Symantec Corporation. All rights reserved.

4

ii

Veritas Cluster Server 6.0 for UNIX: Cluster Management
Copyright © 2012 Symantec Corporation. All rights reserved.

Copyright © 2012 Symantec Corporation. All rights reserved.

Course Introduction

5

focusing on two-node clusters running application and database services. • Veritas Cluster Server for UNIX: Install and Configure This course covers installation and configuration of common VCS environments. • Veritas Cluster Server eLearning Library The eLearning Library is available with bundled training options and includes content on advanced high availability and disaster recovery features. 6 1–2 Veritas Cluster Server 6. • Veritas Cluster Server for UNIX: Manage and Administer This course focuses on multinode VCS clusters and advanced topics related to managing more complex cluster configurations. . All rights reserved. The instructor may opt to present some or all of this material in class. – Veritas Cluster Server for UNIX: Cluster Management This guide provides detailed information about configuring and managing more complex clusters. All rights reserved. depending on time constraints and student interest.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.Veritas Cluster Server curriculum path Copyright © 2012 Symantec Corporation. The course includes two participant guides: – Veritas Cluster Server for UNIX: Example Application Configurations This guide provides examples of common service group configurations. The Veritas Cluster Server for UNIX curriculum is a series of courses that are designed to provide a full range of expertise with Veritas Cluster Server (VCS) high availability solutions—from design through implementation.

Each aspect of the cluster configuration is described in greater detail where applicable in course lessons.Lab design for the course The diagram shows a conceptual view of the cluster design used as an example throughout this course and implemented in hands-on lab exercises. The cluster consists of: • Four nodes • Several high availability services • Fibre connections to SAN shared storage from each node through a switch • Two Ethernet interfaces for the cluster interconnect • Ethernet connections to the public network 7 Additional complexity is added to the design to illustrate certain aspects of cluster configuration in later lessons. . All rights reserved. Course Introduction 1–3 Copyright © 2012 Symantec Corporation. All rights reserved. Copyright © 2012 Symantec Corporation.

All rights reserved. . The course focuses on multinode VCS clusters and advanced topics related to more complex cluster configurations. 8 1–4 Veritas Cluster Server 6.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. All rights reserved. such as service group dependencies and workload management. This training provides comprehensive instruction on the deployment of advanced features of Veritas Cluster Server (VCS).Course overview Copyright © 2012 Symantec Corporation.

Copyright © 2012 Symantec Corporation. All rights reserved. Lesson 1 Service Group Dependencies 9 .

All rights reserved. . 10 1–2 Veritas Cluster Server 6. All rights reserved.Copyright © 2012 Symantec Corporation.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.

then the application. All rights reserved. The relationships between these application service groups must be managed by VCS to ensure that startup. 1–3 . you must also consider which systems should run which applications. All rights reserved. Lesson 1 Service Group Dependencies Copyright © 2012 Symantec Corporation. shutdown. • The Web server relies on an application that processes client requests. as shown in the following examples. 11 The inherent relationships require that the database is started and running first. The example in the slide shows a typical three-tier model where: • A Web server provides an interface to network clients. In a cluster environment. and failover procedures are coordinated properly. and finally the Web server. Copyright © 2012 Symantec Corporation. • The application processes requests from the Web server and relies on the database to manage information.Common application relationships Multitier services In most high availability environments. a collection of applications work together to provide a service.

0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. the Web server must then be brought online on that same failover target system. Copyright © 2012 Symantec Corporation. the services may need to use interprocess communication (IPC) mechanisms to exchange data. If the application faults and fails over to another cluster node. Furthermore.Example 1: Online on the same system In this example of a two-tier service. followed by the Web server. . For example. the application must come online first. both the Web server and the application must be online on the same system. All rights reserved. All rights reserved. 12 1–4 Veritas Cluster Server 6.

For example. In this scenario. but they cannot run on the same system. the database must come online first. as long as the application is not restarted on that same system. and you want to ensure that they run on separate systems. All rights reserved. both the database and the application must be online. All rights reserved. 1–5 . Copyright © 2012 Symantec Corporation. and then the application is started only after the database is running. 13 Lesson 1 Service Group Dependencies Copyright © 2012 Symantec Corporation. the database can stay online on the original system.Example 2: Online on different systems In this example of a two-tier service. If the application faults and fails over to another cluster node. the combined resource requirements of each application may exceed the capacity of the systems.

including manual offline. . The only requirement is that the other application cannot be online on a system when one application is brought online.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. switch. online.Example 3: Offline on the same system One example relationship is where you have a test version of an application and want to ensure that it does not interfere with the production version. All rights reserved. Copyright © 2012 Symantec Corporation. and failover. You want to give the production application precedence over the test version for all operations. 14 1–6 Veritas Cluster Server 6. The difference between this example and the previous example. All rights reserved. neither application requires the other to be online. is that in this case.

Service group dependency definitions 15 There are four basic criteria for defining how services interact when using service group dependencies. All rights reserved. or remote determines where the parent can come online relative to where the child is online. Failover behavior of linked service groups is specified by designating the relationship soft. there is no requirement for either service group to start first.Service group dependencies VCS provides service group dependencies to manage application relationship requirements in multi-application environments. the child group must be online in order for the parent to start. 1–7 . Parent groups depend on child groups. • You can determine the startup order for service groups by designating one group the child and another a parent. If service group B requires service group A to be online in order to start. firm. All rights reserved. then B is the parent and A is the child. – For all online dependencies. Detailed information about how these dependencies impact service group operations is provided in Veritas Cluster Server Administrator’s Guide. • A service group can require another group to be online or offline in order to start and run. global. • You can specify where the groups must be online or offline. The child group must be offline for the parent to come online. Copyright © 2012 Symantec Corporation. – For offline local. Lesson 1 Service Group Dependencies Copyright © 2012 Symantec Corporation. A location of local. or hard.

. Soft dependency A soft dependency means that VCS does not immediately take the parent offline if the child group faults. The child remains online if the parent group faults. All rights reserved. • If the parent group faults. Specifically: • The parent group must be taken offline when the child group faults. global. remote). the parent group can be taken offline while the child is online.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. • When the child is brought online on another system.Failover types The dependency type determines failover behavior for linked service groups. 1–8 Veritas Cluster Server 6. the child continues to run. Likewise. the parent group is brought online on a system determined by the location type (local. When both groups are online. Firm dependency Copyright © 2012 Symantec Corporation. All rights reserved. A firm dependency means that VCS imposes additional constraints on the parent and child service groups. The parent remains online if the child group faults and cannot fail over. the child group can be taken offline while the parent is online. 16 Hard dependency A hard dependency means that VCS takes the other service group offline when either the child or parent group faults.

1–9 . the child service group is taken offline if the parent service group faults. Copyright © 2012 Symantec Corporation. the parent is then also started on that system Online local hard In an online local hard dependency. All rights reserved. Online local soft An online local soft dependency designates that the parent service group remains online when the child service group faults. except the parent service group is taken offline when the child faults. Online local firm 17 An online local firm is similar to soft. a child service group must be online on the same system before the parent service group can come online on that system. the parent service group is then migrated to that same system. If the child fails over and is restarted on another system. Online local is the only dependency supporting the hard type. Lesson 1 Service Group Dependencies Copyright © 2012 Symantec Corporation. If the child service group fails over and is brought online on another system. All rights reserved.Service group dependency examples Online local example In an online local dependency.

as long as the child service group chooses another system on which to fail over.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. Online remote soft An online remote soft dependency designates that the parent service group remains online when the child service group faults. An online remote firm is similar to soft. 18 1–10 Veritas Cluster Server 6. the parent service group is migrated to any other available system. a child service group must be online on a remote system before the parent service group can come online on the local system. All rights reserved. Online remote firm Copyright © 2012 Symantec Corporation.Online remote example In an online remote dependency. All rights reserved. except the parent service group is taken offline when the child faults. . If the child service group chooses to fail over to the system where the parent was online.

1–11 . All rights reserved. the child can only be started if the parent is offline on the local system. All rights reserved. In an offline local dependency. 19 Lesson 1 Service Group Dependencies Copyright © 2012 Symantec Corporation. the parent service group can be started only if the child service group is offline on the local system. This prevents conflicting applications from running on the same system. Similarly. This is commonly used when you have a test version of an application running on the failover target system for the production version of the application.Offline local example Copyright © 2012 Symantec Corporation.

• Service groups cannot have cyclical dependencies.Configuring service group dependencies Service group dependency rules Copyright © 2012 Symantec Corporation.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. This means that an application service can have multiple other application services depending on it. This means that an application service can be dependent on one or more application services. • A group dependency tree can be no more than five levels deep. 20 1–12 Veritas Cluster Server 6. All rights reserved. You can use service group dependencies to implement parent/child relationships between applications. . review the rules governing these dependencies: • The child service group always has priority over the parent group. • A service group can have multiple child service groups. All rights reserved. • Service groups can have multiple parent service groups. Before using service group dependencies to implement the relationships between multiple application services.

because only one dependency is allowed between two service groups. if the child group is also online. the parent group must be offline. Removing service group dependencies When removing a dependency. or using the Cluster Manager Java GUI. service group dependencies are firm by default. All rights reserved. the parent and child may not be linked in such a way that their online states conflict with the type of link between the parent and child. To link a parent and child group with firm dependency. link the groups and specify the relationship (dependency) type. 1–13 . All rights reserved. However. firm. Linking constraints 21 To link a parent and child group with soft dependency. Copyright © 2012 Symantec Corporation. Lesson 1 Service Group Dependencies Copyright © 2012 Symantec Corporation. or the parent and child group must be online in such a way that their online states do not conflict with the type of link between the parent and child. you do not need to specify the type of dependency. you can either right-click the parent service group and select Link to display the Link Service Groups view that is shown on the slide. or hard. If not specified. using Veritas Operations Manager Web GUI. To create a dependency. it is not required that the child group be online if the parent is online. indicating whether it is soft. To configure service group dependencies using the Cluster Manager Java GUI.Creating service group dependencies You can create service group dependencies from the command-line interface using the hagrp command. or you can use the Service Group View.

All rights reserved. You can use the Simulator on Windows to model how different types of links affect service group behavior.Modeling service group dependencies Copyright © 2012 Symantec Corporation. This enables you to fully understand the implications and the effects of different dependency configurations before you configure links in your production environment. All rights reserved.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. 22 1–14 Veritas Cluster Server 6. .

23 Lesson 1 Service Group Dependencies Copyright © 2012 Symantec Corporation. All rights reserved. 1–15 . Copyright © 2012 Symantec Corporation.Online and offline of linked service groups You can use the -propagate option to the hagrp command to simplify bringing linked service groups online and offline. You can also combine -propagate with the -any and -sys options for specifying where the service groups are brought online. Note that propagation is supported only with local service group dependencies type. All rights reserved.

For example. .0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. to enable the preonline trigger for groupa. All rights reserved. • The postonline script is run after a service group is brought online. Consider implementing triggers only after investigating whether VCS native facilities can be used to configure the desired behavior. 24 The postonline and postoffline triggers are enabled automatically if the script is present in the $VCS_HOME/bin/triggers directory. All rights reserved. When present. requiring programming skills as opposed to simply configuring VCS objects and attributes. type: hagrp -modify GroupB PreOnline 1 The preonline script must start the service group with the -nopre option to hagrp. Triggers add complexity. these triggers apply to all service groups. Be sure to copy triggers to all systems in the cluster. These triggers are useful for managing relationships between service groups: • VCS runs the preonline script before bringing a service group online. The PreOnline trigger must be enabled for each applicable service group by setting the PreOnline service group attribute. • The postoffline script is run after a service group is taken offline. 1–16 Veritas Cluster Server 6. as described in the previous example.Alternative methods of controlling interactions Using triggers to control service group interactions Copyright © 2012 Symantec Corporation. VCS provides several event triggers that can be used to enforce service group relationships where dependencies cannot be configured.

as well. 25 Lesson 1 Service Group Dependencies Copyright © 2012 Symantec Corporation. All rights reserved. Each tier needs to have HA of its own – it should be able to independently handle the resilience of the application component running in that tier. One of the key tenets of a multitier architecture is the operational independence of each layer—each tier can make its own decisions without relying on an external brain. 1–17 . All rights reserved. This applies to high availability.Managing multitier applications Copyright © 2012 Symantec Corporation.

Finally.1 and later. for example. Copyright © 2012 Symantec Corporation. . If something happens in the database tier. 26 The middle tier is an application cluster running on several servers in parallel in order to meet user demands. Symantec ApplicationHA is managing high availability for the Apache Web servers running on Windows. Additionally. A Virtual Business Service represents the multi-tier application as a single consolidated entity and builds on the high availability and disaster recovery provided for the individual tiers by Symantec products such as Veritas Cluster Server and Symantec ApplicationHA. All rights reserved. VCS provide local high availability in this tier and manages the dependencies on the database. you would find the database to be shared across multiple services as well. Typically.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. VCS ensures the database is failed over to another node in the cluster. In the example shown in the slide. the database cluster is the lowest level tier and is the most critical component in this service. VBS is configured and managed using Veritas Operations Manager (VOM) version 4. an active server fails or the database runs into software issues on one of the servers.Virtual Business Services Virtual Business Services provide continuous high availability and reduce frequency and duration of service disruptions for multi-tier business applications running on heterogeneous operating systems and virtualization technologies. All rights reserved. 1–18 Veritas Cluster Server 6. the web server top tier is running on Vmware virtual machines. disaster recovery may be configured so that if the production site goes down. VCS fails the database over to the DR site.

All rights reserved. In the example configuration shown in the slide. the fault is propagated to other clusters similarly to service group dependencies. if oracle_sg faults. oracle_apps_sg restarts. All rights reserved. and no fault policy action is needed. Copyright © 2012 Symantec Corporation. A restart type dependency is specific to a VBS configuration. If or when the oracle_sg restarts and is in a running state. oracle_apps_sg ignores the fault and continues to run.Fault propagation between clusters When a service group that is running on a cluster that is a member of a Virtual Business Service faults. In other words. 1–19 . Lesson 1 Service Group Dependencies Copyright © 2012 Symantec Corporation. 27 This type of dependency is used when only start or stop ordering is required. the parent service group with a restart dependency on a child service group takes no action when a child service group faults until the child is restarted.

• “Lab 1: Service group dependencies. 1–20 Veritas Cluster Server 6. All rights reserved.” page B-3. . 28 Labs and solutions for this lesson are located on the following pages. All rights reserved.Copyright © 2012 Symantec Corporation.” page A-3. • “Lab 1: Service group dependencies.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.

Copyright © 2012 Symantec Corporation. All rights reserved. Lesson 2 Reconfiguring Cluster Membership 29 .

.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.Copyright © 2012 Symantec Corporation. All rights reserved. All rights reserved. 30 2–2 Veritas Cluster Server 6.

2–3 . these assumptions are used in describing how to perform this task: • The VCS cluster consists of two or more systems. All rights reserved. • There are multiple service groups configured in the cluster. • The storage devices can be connected to all systems.Adding a system to a cluster Adding a system to a running VCS cluster The objective of this task is to add a new system to a running VCS cluster with no or minimal impact on application services. • The new system to be added to the cluster does not have any VCS software. • The new system has the same version of operating system and VERITAS Storage Foundation as the systems in the cluster. All rights reserved. all of which are up and running. Ensure that the cluster configuration is modified so that the application services can make use of the new system in the cluster. All of the service groups are online somewhere in the cluster. Assumptions 31 For illustration purposes. Copyright © 2012 Symantec Corporation. • The new system may not have all the required application software. Lesson 2 Reconfiguring Cluster Membership Copyright © 2012 Symantec Corporation.

All rights reserved. .0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. Procedure for adding a system to a running cluster 32 2–4 Veritas Cluster Server 6.Copyright © 2012 Symantec Corporation. All rights reserved.

2–5 . All rights reserved.Copyright © 2012 Symantec Corporation. All rights reserved. 33 Lesson 2 Reconfiguring Cluster Membership Copyright © 2012 Symantec Corporation.

• There are multiple service groups configured in both clusters. • The clusters do not necessarily have the same application services software. ensure that the cluster configuration is modified so that the application services can make use of the systems from both clusters. • The storage devices can be connected to all systems. All service groups are online somewhere in the cluster. Also.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. assume that two two-node clusters are merged into a single fournode cluster. 2–6 Veritas Cluster Server 6. • The cluster interconnects of both clusters are isolated before the merger.Merging clusters Merging two running VCS clusters The objective of this task is to merge two running VCS clusters with no or minimal impact on application services. 34 For this example. Assumptions Copyright © 2012 Symantec Corporation. The following is a list of assumptions that you need to take into account while planning a procedure for this task: • All the systems in both clusters are up and running. • All the systems have the same version of operating system and Veritas Storage Foundation. All rights reserved. • New application software can be installed on the systems to support application services of the other cluster. All rights reserved. .

Procedure for merging two running clusters 35 Lesson 2 Reconfiguring Cluster Membership Copyright © 2012 Symantec Corporation. All rights reserved. 2–7 . All rights reserved.Copyright © 2012 Symantec Corporation.

. All rights reserved. 36 2–8 Veritas Cluster Server 6.Copyright © 2012 Symantec Corporation.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. All rights reserved.

All rights reserved. 37 Lesson 2 Reconfiguring Cluster Membership Copyright © 2012 Symantec Corporation.Copyright © 2012 Symantec Corporation. 2–9 . All rights reserved.

All rights reserved.Additional reconfiguration tasks Reconfiguring triggers and service groups The objective of this task is to update the cluster configuration so that the application services can make use of the systems from both clusters.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. Assumptions Copyright © 2012 Symantec Corporation. The following is a list of assumptions that you need to take into account while planning a procedure for this task: • Application resources have been prepared • Service group definitions have been merged • Agents have been installed 38 2–10 Veritas Cluster Server 6. All rights reserved. .

2–11 . All rights reserved.Copyright © 2012 Symantec Corporation. All rights reserved. Procedure for updating triggers and service groups 39 Lesson 2 Reconfiguring Cluster Membership Copyright © 2012 Symantec Corporation.

All rights reserved.Copyright © 2012 Symantec Corporation. All rights reserved. . 40 2–12 Veritas Cluster Server 6.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.

• “Lab 2: Merging clusters. • “Lab 2: Merging clusters.” page A-13. All rights reserved.Copyright © 2012 Symantec Corporation. All rights reserved. 41 Labs and solutions for this lesson are located on the following pages. 2–13 . Lesson 2 Reconfiguring Cluster Membership Copyright © 2012 Symantec Corporation.” page B-37.

All rights reserved. All rights reserved. .Copyright © 2012 Symantec Corporation. 42 2–14 Veritas Cluster Server 6.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.

Copyright © 2012 Symantec Corporation. Lesson 3 Startup and Failover Policies 43 . All rights reserved.

Copyright © 2012 Symantec Corporation. . All rights reserved. All rights reserved.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. 44 3–2 Veritas Cluster Server 6.

the service group cannot be frozen. 3–3 . • And dependencies on child service groups must have been met before a service group can be automatically started. In addition. • All of the systems in the service group’s SystemList must be in the running state so that the service group can be probed on all systems in SystemList. Rules for automatic service group startup 45 The following conditions must be satisfied for a service group to be automatically started: • The service group AutoStart attribute must be set to the default value of 1. All rights reserved. the service group definition must have at least one system in its AutoStartList attribute. VCS autodisables the service group until it is probed on all the systems. Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation. If this attribute is changed to 0. • If there are systems on which the service group can run that have not joined the cluster yet.Startup rules and policies Copyright © 2012 Symantec Corporation. All rights reserved. Also. VCS leaves the service group offline and waits for an administrative command to be issued to bring the service group online.

– Systems where the service group has a faulted status are eliminated. as described in detail later in the lesson. All rights reserved. . 2 Systems are culled from this initial list according to these criteria: – Frozen systems are eliminated. The startup system for a service group is chosen as follows: 1 All systems included in the AutoStartList attribute are initial candidates for service group startup. 46 3–4 Veritas Cluster Server 6. 3 The target system is then chosen from this list based on the startup policy defined for the service group. – Systems that do not meet the service group requirements are eliminated. All rights reserved.Startup system selection Copyright © 2012 Symantec Corporation.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.

and Load. Note: The configuration must be open to change service group attributes. • Load: The system with the highest available capacity is selected. hagrp -modify group AutoStartPolicy policy 47 where possible values for policy are Order. The autostart policies are described in more detail in the following pages. Priority. This is the default policy for every service group.Automatic startup policies You can set the AutoStartPolicy attribute of a service group to one of these three values: • Order: Systems are chosen in the order in which they are defined in the AutoStartList attribute. execute: Copyright © 2012 Symantec Corporation. Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation. the system with the lowest priority number in SystemList is selected. 3–5 . • Priority: Of the systems listed in the AutoStartList attribute. You can also set this attribute using Veritas Operations Manager or the Cluster Manager Java GUI. To configure the AutoStartPolicy attribute of a service group. All rights reserved. All rights reserved.

Similarly.cf file. the A service group is brought online on s1. and the C service group is brought online on s3 because these are the first systems listed in the AutoStartList attributes of the corresponding service groups.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. . In the example shown on the slide. the first system available in AutoStartList is selected to bring the service group online. it is not listed in the service group definitions in the main. Copyright © 2012 Symantec Corporation. All rights reserved. although it is the system with the highest priority number in SystemList. the B service group is brought online on s2. 48 3–6 Veritas Cluster Server 6. All rights reserved. Note: Because Order is the default value for the AutoStartPolicy attribute.AutoStartPolicy=Order When the AutoStartPolicy attribute of a service group is set to the default value of Order. The priority numbers in SystemList are ignored.

Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation.AutoStartPolicy=Priority When the AutoStartPolicy attribute of a service group is set to Priority. Copyright © 2012 Symantec Corporation. although the SystemList and AutoStartList attributes are the same for these two examples. the B service group is brought online on s1 (with priority number 0). The same example service groups are now modified to use the Priority AutoStartPolicy. 49 Notice how the startup systems have changed for the service groups by changing the AutoStartPolicy attribute. the order of systems in the AutoStartList is ignored. All rights reserved. the A service group is brought online on s3. 3–7 . which has the lowest priority number in SystemList even though it is listed as the last system in AutoStartList. In this example. the system with the lowest priority number in the SystemList that also appears in the AutoStartList is selected as the target system during start-up. as shown on the slide. Similarly. In this case. All rights reserved. and the C service group is brought online on s1 (with priority number 1).

200. In the example displayed on the slide. VCS determines the target system based on the existing workload of each system listed in the AutoStartList attribute and the load that is added by the service group.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. respectively. All rights reserved. This value is based on how much of the system capacity is required to run the application service that is managed by the service group. and 100. 50 Determining Load and Capacity You must determine a value for Load for each service group. Copyright © 2012 Symantec Corporation. three servers have Capacity set to 300. • AvailableCapacity is a system attribute maintained by VCS that quantifies the remaining available system load. • Load is a user-defined service group attribute that defines the amount of capacity required to run the service group. These attributes control load-based startup: • Capacity is a user-defined system attribute that contains a value representing the total amount of load that the system can handle. All rights reserved.AutoStartPolicy=Load When AutoStartPolicy is set to Load. The s2 system is selected as the target system for starting C because it has the highest AvailableCapacity value of 200 after A and B are started on s1. 3–8 Veritas Cluster Server 6. .

3–9 . and AvailableCapacity is updated to reflect the difference. Both the Capacity attribute of a system and the Load attribute of a service group are static user-defined attributes based on your design criteria. All rights reserved. All rights reserved. 51 Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation.Copyright © 2012 Symantec Corporation. When a service group is brought online. the value of its Load attribute is subtracted from the system Capacity value.

The ManageFaults attribute must be set to All. 52 3–10 Veritas Cluster Server 6. • At least one of the systems in the service group’s SystemList attribute must be in a running state. • The service group AutoFailOver attribute must be set to the default value of 1. All rights reserved. . VCS leaves the service group offline and waits for an administrative command to be issued to bring the service group online. • The service group cannot be frozen. The following conditions must be satisfied for a service group to be automatically failed over after a fault: • The service group must contain a critical resource.Failover rules and policies Rules for automatic service group failover Copyright © 2012 Symantec Corporation.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. the default setting. All rights reserved. If this attribute is changed to 0. and that resource must fault or be a parent of a faulted resource.

Failover system selection Copyright © 2012 Symantec Corporation. 2 Systems that do not meet the service group requirements are eliminated. All rights reserved. The failover system for the service group is chosen as follows: 1 A subset of systems listed in the SystemList attribute is created first. – Systems that do not meet the service group requirements are eliminated. All rights reserved. 53 Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation. including: – Frozen systems – Systems where the service group has a faulted status are eliminated from the list. as described in detail later in the lesson. 3–11 . 3 The target system is chosen from this list based on the failover policy defined for the service group.

The policies are described in more detail in the following pages. All rights reserved. The policy is configured by setting the FailOverPolicy attribute to one of these values: • Priority: The system with the lowest priority number is preferred for failover (default).0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. All rights reserved. . Copyright © 2012 Symantec Corporation. • Load: The system with the highest value of the AvailableCapacity system attribute is selected for failover. • RoundRobin: The system with the least number of active service groups is selected for failover.Failover policies VCS supports a variety of policies that determine how a system is selected when service groups must migrate due to faults. 54 3–12 Veritas Cluster Server 6.

VCS selects the system with the lowest assigned value from the SystemList attribute. s2=2} AutoStartList = {s3. The C service group is initially started on s3 because it is the first system in AutoStartList. Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation. If C faults on s3. s1. VCS selects s1 as the failover target because it has the lowest priority value for the remaining available systems. s2} Copyright © 2012 Symantec Corporation. All rights reserved. the C service group has three systems configured in the SystemList attribute and the same order for AutoStartList values: SystemList = {s3=0. 3–13 . s1=1. 55 Priority policy is the default behavior and is ideal for simple two-node clusters or small clusters with few service groups.FailOverPolicy=Priority When FailOverPolicy is set to Priority. For example. All rights reserved.

. • A service group that is in the process of being brought online is not considered an active service group until it is completely online. The RoundRobin policy is ideal for large clusters running many service groups with essentially the same server load characteristics (for example. similar databases or applications). Copyright © 2012 Symantec Corporation. if two failover target systems have the same number of service groups running. including RoundRobin. All rights reserved. All rights reserved. 3–14 Veritas Cluster Server 6. the system listed first in the SystemList attribute is selected for failover.FailOverPolicy=RoundRobin The RoundRobin policy selects the system running the fewest service groups as the failover target.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. For example. 56 Ties are determined by the order of systems in the SystemList attribute. Take into account these properties of the RoundRobin policy: • Only systems listed in the SystemList attribute for the service group are considered when VCS selects a failover target for all failover policies.

57 In the example displayed in the slide. Copyright © 2012 Symantec Corporation. 200. the three servers that remain running after the s3 system fails have Capacity set to 300. Each service group has a fixed load defined by the user. All rights reserved. • Load is a service group attribute that defines the amount of capacity required to run the service group. VCS checks the value of AvailableCapacity on each potential target—each system in the SystemList attribute for the service group— and starts the service group on the system with the highest value. When failover occurs. These attributes control load-based failover: • Capacity is a system attribute that contains a value representing the total amount of load that the system can handle. Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation. and 100. All rights reserved. VCS determines the target system based on the existing workload of each system listed in the SystemList attribute and the load that is added by the service group. Note: In the event that no system has a high enough AvailableCapacity value for a service group load. • AvailableCapacity is a system attribute maintained by VCS that quantifies the remaining available system load. which is subtracted from the system capacity to find the AvailableCapacity value of a system. the service group still fails over to the system with the highest value for AvailableCapacity. even if the resulting AvailableCapacity value is zero or a negative number. 3–15 .FailOverPolicy=Load When FailOverPolicy is set to Load.

0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. use the hagrp -modify command as shown in this example: Copyright © 2012 Symantec Corporation.Configuring Load and Capacity You can use VOM. hagrp -modify dbsg Load 75 58 3–16 Veritas Cluster Server 6. All rights reserved. All rights reserved. . To set Capacity from the command-line interface. use the hasys -modify command as shown in this example: hasys -modify s1 Capacity 300 To set Load from the CLI. the Cluster Manager Java GUI. or the command-line interface to set the Capacity system attribute and the Load service group attribute.

3–17 . You can copy the sample trigger script from /opt/VRTSvcs/ bin/sample_triggers as a starting point. 59 To configure the loadwarning trigger: 1 Create a loadwarning script in the /opt/VRTSvcs/bin/triggers directory. in seconds. LoadWarningLevel before the trigger is run Default is 600 seconds Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation. that a system must remain at. All rights reserved. expressed as a percentage of the Capacity attribute Default is 80 percent – LoadTimeThreshold: Length of time. All rights reserved. You can configure the loadwarning trigger to provide notification that a system has sustained a predetermined load level for a specified period of time. 2 Set the loadwarning attributes for the system: – Capacity: Load capacity for the system – LoadWarningLevel: The level at which load has reached a critical limit. and then modify it according to your requirements.The loadwarning trigger Copyright © 2012 Symantec Corporation. or above.

VCS keeps track of the available resources on a system by subtracting the resources already in use by service groups online on each system from the maximum capacity for that resource. You can use any keyword for a resource as long as you use the same keyword on all systems and service groups. Note: The resources that you define are arbitrary—they do not need to correspond to physical or software resources. 3–18 Veritas Cluster Server 6. semaphores. All rights reserved. VCS checks these available resources against service group prerequisites. 60 Limits The Limits system attribute is used to define the resources and the corresponding capacity of each system for that resource. and the number of processors or application instances are all examples of resources that can be defined on a system. When a new service group is brought online.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. Copyright © 2012 Symantec Corporation. Shared memory. multiapplication services environment. In a multinode. All rights reserved. the service group cannot be brought online on a system that does not have enough available resources to support the application services.Limits and Prerequisites Startup example VCS enables you to define the available resources on each system and the corresponding requirements for these resources for each service group. You then define the corresponding prerequisites for a service group to come online on a system. .

3–19 . All rights reserved. All rights reserved. Service group Prerequisites Prerequisites is a service group attribute that defines the set of resources needed to run the service group. a value of 0 is assumed for service groups that do not have some or all of the resources defined in their Prerequisites attribute. Similarly. Prerequisites are used to determine a subset of eligible systems on which a service group can be started during failover or startup. For example.cf is: Limits = { DBs=2 } • On the second two systems.cf is: Limits = { DBs=0 } This value of DBs in this example is used to control how many Oracle service groups can run on a system.cf configuration corresponds to the E service group in the diagram: Prerequisites = { DBs=1 } CurrentLimits CurrentLimits is an attribute maintained by VCS that contains the value of the remaining available resources for a system.The example values displayed in the slide are set as follows: • On the first system. the Limits attribute setting in main. the Limits attribute setting in main. HAD then follows the configured policy for autostart or failover. the Limits attribute setting in main. Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation. 61 Note: A value of 0 is assumed for systems that do not have some or all of the resources defined in their Limits attribute. This main.cf is: Limits = { DBs=1 } • On the fourth system. if the limit for DBs is 2 and the A service group is online with a DBs prerequisite of 1. These values correspond to the Limits system attribute and are set by the Prerequisites service group attribute. When a list of eligible systems is created. the CurrentLimits setting for DBs is 1: CurrentLimits = { DBs=1 } Selecting a target system Copyright © 2012 Symantec Corporation.

If the AvailableCapacity value is not high enough to satisfy the Load requirement for a service group.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. Contrast this with the Load and Capacity. Copyright © 2012 Symantec Corporation. All rights reserved. An example case is an environment where licensing restrictions prevent two instances of an application or database from running on a system. Therefore. C stays offline. System Limits are hard values. meaning that if a system does not meet the requirements specified in the Prerequisites attribute for a service group.Failover example The configuration in the slide shows how a failover target system is selected for the C service group when the s3 system faults. even if the AvailableCapacity becomes a negative value. VCS still fails over the service group. the service group cannot be started on that system. which are soft limits. using Limits and Prerequisites may be a better method for controlling service group startup and failover in cases where hard limits must be enforced. 62 3–20 Veritas Cluster Server 6. . All rights reserved. Because C has a prerequisite of 1 for DBs and there are no systems with a high enough CurrentLimits value for DBs to support running the group.

All rights reserved.Configuring Limits and Prerequisites You can use the VCS GUI or command-line interface to set the Limits system attribute and the Prerequisites service group attribute. open the VCS configuration to enable read/ write mode and ensure that the service groups that are already online on a system do not violate the restrictions. hagrp -modify DBSG Prerequisites DBs 1 63 Notes: • To be able to set these attributes. use the hagrp -modify command as shown in this example: Copyright © 2012 Symantec Corporation. use the hasys -modify command as shown in the following example: hasys -modify s2 Limits DBs 2 To set Prerequisites from the CLI. To set Limits from the command-line interface. • The order that the resources are defined within the Limits or Prerequisites attributes is not important. All rights reserved. 3–21 . Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation.

0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.Modeling startup and failover policies Using the Simulator Copyright © 2012 Symantec Corporation. All rights reserved. The VCS Simulator for Windows is a good tool for modeling the behavior that you require before making changes to the running configuration. All rights reserved. 64 3–22 Veritas Cluster Server 6. This enables you to fully understand the implications and the effects of different workload management configurations. .

All rights reserved. • “Lab 3: Failover policies. Lesson 3 Startup and Failover Policies Copyright © 2012 Symantec Corporation. 65 Labs and solutions for this lesson are located on the following pages. 3–23 .” page B-65. All rights reserved.Copyright © 2012 Symantec Corporation. • “Lab 3: Failover policies.” page A-25.

0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. . All rights reserved. 66 3–24 Veritas Cluster Server 6.Copyright © 2012 Symantec Corporation. All rights reserved.

Copyright © 2012 Symantec Corporation. Lesson 4 Alternate Network Configurations 67 . All rights reserved.

0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. All rights reserved.Copyright © 2012 Symantec Corporation. . 68 4–2 Veritas Cluster Server 6. All rights reserved.

you must change the Device attribute for each NIC resource monitoring that interface. each containing NIC resources that monitor the same physical network interface. creating unnecessary overhead and network traffic. In addition to the overhead of many monitor cycles for the same resource. 4–3 .Multiple service groups with NIC resources NIC resources in multiple service groups Many clusters have multiple service groups. Copyright © 2012 Symantec Corporation. in the event the interface fails). All rights reserved. 69 Lesson 4 Alternate Network Configurations Copyright © 2012 Symantec Corporation. VCS monitors the same network interface—say e1000g0 on Solaris—many times. a disadvantage of this configuration is the effect of changes in NIC hardware. If you must change the network interface (for example. In this case. All rights reserved.

All rights reserved. All rights reserved. TargetResName. 70 4–4 Veritas Cluster Server 6. Copyright © 2012 Symantec Corporation. The Proxy resource mirrors the status of another resource in a different service group.Using Proxy resources You can use a Proxy resource to allow multiple service groups to monitor the same network interfaces. This reduces the network traffic that results from having multiple NIC resources in different service groups monitor the same interface. the local system is used as the target system. . If no system is specified. is the name of the resource whose status is reflected by the Proxy resource.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. TargetSysName is an optional attribute specifies the name of the system on which the target resource status is monitored. The required attribute.

cf file and add Parallel = 1 to the service group definition. 71 To create a new parallel service group in a running cluster. A network service group can be configured as a parallel service group because the NIC resource is persistent and can be online on multiple systems. Lesson 4 Alternate Network Configurations Copyright © 2012 Symantec Corporation. With this configuration. A parallel service group is managed like any other service group in VCS. in effect. all the other service groups are configured with a Proxy to the NIC resource on their local system. 4–5 . This is accomplished by VCS starting up the parallel group on the target system. A parallel service group can also fail over.Parallel network service groups Parallel service groups run on multiple systems simultaneously. set the Parallel attribute to 1 (true) and then add resources. if the service group faults on a system and there is an available system (listed in the SystemList attribute) that is not already running the service group. Copyright © 2012 Symantec Corporation. The group is only started on a system listed in the AutoStartList and the SystemList attributes. You cannot change an existing failover service group that contains resources to a parallel service group except by using the offline configuration procedure to edit the main. except that it cannot be switched. All rights reserved. All rights reserved.

the status of the service group is shown as online. even if the persistent resources are running properly. . if a service group has only persistent resources. VCS considers the group offline. When a Phantom resource is added.Using Phantom resources Copyright © 2012 Symantec Corporation. Therefore. A service group shows an online status only when all of its nonpersistent resources are online. All rights reserved. 72 4–6 Veritas Cluster Server 6. The example network service group also requires a Phantom resource in order to ensure that the service group status is displayed properly.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. All rights reserved.

when using the CLI. An attribute whose value applies on a per-system basis is local in scope. type: hares -local netnic Device Copyright © 2012 Symantec Corporation. a GUI. All rights reserved. Some attributes can be localized to enable you to specify different values for different systems. All rights reserved. In the example displayed in the slide. 4–7 . Network-related resources are common examples for local attributes. For example. all attributes are global. After creating the resource. the Device attribute for the NIC resource is localized to enable you to specify a different interface for each system. Lesson 4 Alternate Network Configurations Copyright © 2012 Symantec Corporation. you can localize attribute values using the hares command. or an offline configuration method. By default.Localizing a NIC resource An attribute whose value applies to all systems is global in scope. hares -modify netnic Device eth0 -sys s1 73 hares -modify netnic Device eth4 -sys s2 Any attribute can be localized.

you can use the VCS NIC agent to monitor a bond-type interface and an IP resource to bring up a virtual IP address on the virtual bond interface. All rights reserved.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. 74 4–8 Veritas Cluster Server 6. . you can use the bond driver to treat multiple network interfaces as one logical interface. In this case. For example. This is often referred to as port trunking or interface bonding. All rights reserved. on Linux. Copyright © 2012 Symantec Corporation.Multiple public interfaces Trunked or bonded interfaces Most UNIX operating systems have the capability to create a logical network interface that represents a collection of physical network interfaces.

10.10.10. 4–9 .0 BOOTPROTO=none IPADDR=10.2. NIC bond0nic ( 75 Device = bond0 ) An advantage of using the Linux bond interface is that you can aggregate interfaces to increase bandwidth.10.0 The corresponding sample /etc/modules.conf file contains: alias eth0 e1000 alias eth1 e1000 alias bond0 bonding options bond0 miimom=100 mode=2 The following VCS resource definitions are contained in a service group to monitor the bond0 interface and manage the virtual IP address.255.255 GATEWAY=10.2.10. All rights reserved.The following table shows an example configuration where eth0 and eth1 are controlled by the bond0 interface. ifcfg-eth0 ifcfg-eth1 ifcfg-bond0 DEVICE=eth0 ONBOOT=yes BOOTPROTO=no ne USERCTL=no PEERDNS=no TYPE=Ethernet MASTER=bond0 SLAVE=yes DEVICE=eth1 ONBOOT=yes BOOTPROTO=no ne USERCTL=no PEERDNS=no TYPE=Ethernet MASTER=bond0 SLAVE=yes DEVICE=bond0 ONBOOT=yes USERCTL=no TYPE=Ethernet MTU="" NETMASK=255.2. All rights reserved.255. IP webip ( Device = bond0 Address = "10.10.0. Lesson 4 Alternate Network Configurations Copyright © 2012 Symantec Corporation.1 NETWORK=10.20 BROADCAST=10.21" ) Copyright © 2012 Symantec Corporation.

4–10 Veritas Cluster Server 6. MultiNICA and IPMultiNIC. Local interface failover can drastically reduce service interruptions to the clients. 76 Failover between local interfaces can be completely transparent to users for some applications. Some applications have time-consuming shutdown and startup processes that result in substantial downtime when the application fails over from one system to another. . All rights reserved. Using multiple networks also makes it possible to eliminate any switch or hub failures causing service group failover as long as the multiple interfaces on the system are connected to separate hubs or switches. Advantages of local interface failover Copyright © 2012 Symantec Corporation. By allocating more than one network interface to a service group. you can potentially avoid failover of the entire service group if the interface fails. All rights reserved. VCS provides this type of local failover with the MultiNICB and IPMultiNICB resources for the Solaris. it is common to have many network interfaces on each system.Local network interface failover With the availability of inexpensive network adapters. By moving the IP address on the failed interface to another interface on the local system.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. you can eliminate or minimize downtime. All platforms also support legacy resource types. for local interface failover. and HP-UX platforms. AIX.

The dependency between these resources is the same as the dependency between IP and NIC resources. and if one of these interfaces faults. 77 The MultiNICB and IPMultiNICB agents provide similar functionality to the MultiNICA and IPMultiNIC agents with many additional features. these additional features are provided: • Support for the Solaris IPMP daemon • Support for trunked network interfaces on Solaris See the Veritas Cluster Server Bundled Agents Reference Guide for your platform for complete details about configuring these resource types. All rights reserved. All rights reserved. VCS fails over the IP address defined by the IPMultiNIC resource to the next available public network adapter. such as: • Support for faster failover • Support for active/active interfaces • Support for failback On Solaris only. Lesson 4 Alternate Network Configurations Copyright © 2012 Symantec Corporation. Copyright © 2012 Symantec Corporation. 4–11 .Network resources overview The MultiNICA agent is capable of monitoring multiple network interfaces. The IPMultiNIC and MultiNICA resources provide essentially the same service as the IP and NIC resources. but these resources monitor multiple interfaces instead of a single interface.

• MultiNICB failover is many times faster than that of MultiNICA.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. All rights reserved. . • MultiNICB and IPMultiNICB support failback of IP addresses. interface groups. for these interfaces. • MultiNICA does not require all interfaces to be part of a single IP subnet. MultiNICB and IPMultiNICB support IPMP. 78 On Solaris. and trunked ge and qfe interfaces. supporting an active/passive configuration. • Support for single and multiple interfaces eliminates the need for separate pairs of NIC and IP. Copyright © 2012 Symantec Corporation. • MultiNICB and IPMultiNICB support manual movement of IP addresses between working interfaces under the same MultiNICB resource without changing the VCS configuration or disabling resources. or MultiNICA and IPMultiNIC. All rights reserved. Advantages of using MultiNICB and IPMultiNICB • All interfaces under a particular MultiNICB resource are always configured and have test IP addresses to speed failover.Comparing MultiNICA and MultiNICB Advantages of using MultiNICA and IPMultiNIC • Physical interfaces can be plumbed as needed by the agent. • MultiNICA requires only one base IP address for the set of interfaces under its control. This address can also be used as the administrative IP address for the system. 4–12 Veritas Cluster Server 6.

Copyright © 2012 Symantec Corporation. • “Lab 4: Creating a parallel network service group.” page A-37.” page B-89. All rights reserved. Lesson 4 Alternate Network Configurations Copyright © 2012 Symantec Corporation. All rights reserved. • “Lab 4: Creating a parallel network service group. 4–13 . 79 Labs and solutions for this lesson are located on the following pages.

All rights reserved. All rights reserved. 80 4–14 Veritas Cluster Server 6.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. .Copyright © 2012 Symantec Corporation.

Copyright © 2012 Symantec Corporation. Lesson 5 High Availability in the Enterprise 81 . All rights reserved.

82 5–2 Veritas Cluster Server 6. . All rights reserved.Copyright © 2012 Symantec Corporation.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. All rights reserved.

Veritas Operations Manager (VOM) enables you to perform administrative tasks and analysis for all clusters in an environment.Veritas Operations Manager Veritas Operations Manager provides a single. Veritas Operations Manager enables administrators to centrally manage diverse data center environments. centralized management console for the Veritas Storage Foundation and High Availability products. Simplified cluster management Copyright © 2012 Symantec Corporation. You can use it to monitor. All rights reserved. 83 You can also use Veritas Operations Manager to visualize the state of multi-tier applications and all subcomponents components and to start or stop the entire logical application in an ordered fashion. Virtual Business Services provides this capability of associating service groups across clusters and managing the relationships in a high availability and disaster recovery environment. All rights reserved. Lesson 5 High Availability in the Enterprise Copyright © 2012 Symantec Corporation. You can also use Veritas Operations Manager to manage hosts that do not have Storage Foundation and High Availability products installed. and generate reports. and manage storage and cluster resources. visualize. virtual environments. 5–3 . across physical locations. and operating system platforms.

0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. presented upon login. stores. starting with the concise dashboard view shown in the slide. VOM uses a Web browser-based user interface to present information in a layered form.VOM functional overview VOM collects. . The dashboard view. 84 5–4 Veritas Cluster Server 6. All rights reserved. and application resources at a glance. but having one or more failed components that could result in faulting if a further component failure occurs). server. Graphics and color coding are both used to draw attention to resources that require attention because they are either faulted (not functioning) or are at risk (configured to be fault-tolerant. contains highly summarized information about all managed storage. and presents state information for all Storage Foundation HA resources in a variety of views. All rights reserved. Copyright © 2012 Symantec Corporation. consolidates.

such as by applying the same change to many clusters with one command. a new user account. Copyright © 2012 Symantec Corporation.Distributed commands in a VOM domain VOM provides centralized cluster visualization. 5–5 .x nodes running a connector agent VOM increases administrator efficiencies and reduces configuration errors by enabling centralized deployment of configuration changes. All rights reserved. and control of the entire distributed environment.x or 5. monitoring. OraOper. 85 Lesson 5 High Availability in the Enterprise Copyright © 2012 Symantec Corporation. All rights reserved. In the example shown in the slide. is given service group operator privileges for all clusters containing Oracle service groups. The components of a VOM domain—the scope of a Storage Foundation High Availability management environment—include: • Management servers—stand-alone peer servers or clusters • One or more Web consoles • Managed hosts: VCS 4.

warning messages are issued every four hours until the system is configured as a managed host. the warning mechanism is only disabled when you install Storage Foundation and add the host to the VOM domain. All rights reserved.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. . A 60 day grace period is allowed to set up the VOM environment and configure SFHA systems as managed hosts. Copyright © 2012 Symantec Corporation. After 60 days.License deployment policies and reporting When using keyless licensing. Note: Although you can install VCS without Storage Foundation and select keyless licensing. all cluster nodes must become managed hosts in a VOM environment. All rights reserved. You can use VOM license deployment policies and reports to ensure all systems in the data center meet licensing requirements. 86 5–6 Veritas Cluster Server 6. The licenses can then be tracked using the license deployment reporting feature in VOM.

VOM Deployment Management enables you to install a solution on selected hosts. or on both.symantec. After a solution is installed. When you run the installation process. To deploy solutions you must have domain administrative privileges. a deployment request is sent. Lesson 5 High Availability in the Enterprise Copyright © 2012 Symantec Corporation. Any solutions available in the repository can be installed on the Management Server. You can view that deployment request in the Deployment Requests page. These solutions are grouped into the following categories: • Add-on • Package • Patch • Hotfix 87 A core group of add-ons are bundled in VOM solutions repository. 5–7 . Veritas Operations Manager solutions are independent and optional feature packs that you can download and use to enhance the functionality of Veritas Operations Manager. you must enable the solution to use the management tools within the add-on. managed hosts. Other add-ons must be downloaded from sort. All rights reserved.VOM solutions Copyright © 2012 Symantec Corporation. or a selected platform (for example AIX). All rights reserved.com and then uploaded to your VOM repository.

Note: The Percentage in slide based on “Symantec Disaster Recovery Study” published 22 November 2010.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. These fire drill service groups are modified to use copies of the primary site’s data so that the applications can be started and tested without affecting the production service groups. the resources: 1 Create a snapshot of the replicated volume. 3 Start the application or database. . EMC SRDF and Hitachi Truecopy agents are enhanced to take advantage of device tagging in Volume Manager. 88 VCS logs any errors to enable you to identify configuration problems in your DR site. All rights reserved. All rights reserved. Starting with VCS 5. 5–8 Veritas Cluster Server 6. A fire drill is implemented by configuring a clone service group with specialpurpose resources.0. This enables hardware snapshots to be imported and used for a fire drill capability without any scripting or tasks required to be used outside of VCS. 2 Mount the snapshot file system. When you bring a fire drill service group online. as shown in the following examples. Copyright © 2012 Symantec Corporation.Disaster recovery enhancements Testing disaster recovery Disaster recovery fire drill is a feature provided with the Global Cluster Option for VCS that enables you to anticipate and address configuration problems at the DR site prior to encountering an actual disaster.

In this case. and the database is running using data files on the snapshot volumes. You can configure the VCS Management Console to run regularly scheduled fire drills to ensure you are continuously validating your DR environment. All rights reserved. 89 Lesson 5 High Availability in the Enterprise Copyright © 2012 Symantec Corporation. all resources came online. Copyright © 2012 Symantec Corporation. All rights reserved. 5–9 .Successful fire drill example The slide shows example VCS Engine log file entries for a successful fire drill test of an Oracle service group named oragrp_fd.

All rights reserved. This DBA is not aware that the volume needs to be added to the replication configuration. so the tablespace is not replicated to the secondary site. a database administrator adds a volume to a disk group on the primary site. In this example. 90 5–10 Veritas Cluster Server 6.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. .DR configuration problem example One common DR configuration problem is storage configuration drift—an object is changed at the primary site and that change is not propagated to the secondary site. Copyright © 2012 Symantec Corporation. All rights reserved. and then creates a new tablespace.

which is not present at the secondary site.Failed fire drill example This slide shows VCS engine log entries indicating the problem with the fire drill caused by data created on the primary site but not replicated to the secondary site.dbf file. The log includes the Oracle startup output resulting from bringing the Oracle (Orafd3_fd) resource online on the secondary site. All rights reserved. The Oracle error output identifies a problem with the /oradata2/tb2. Copyright © 2012 Symantec Corporation. All rights reserved. Other examples of configuration drift that cause problems for site migration include: • Expired licenses • Operating system and application patch version mismatches • Configuration files not synchronized 91 Lesson 5 High Availability in the Enterprise Copyright © 2012 Symantec Corporation. 5–11 .

and 5. Copyright © 2012 Symantec Corporation.Managing replication You can use VOM to simplify configuration of storage and replication objects used in replicated data clusters (RDCs) and global clusters with both 4. download the Add-on for Veritas Volume Replicator Bandwidth Reporting from sort. . All rights reserved. All rights reserved. After you upload the add-on to the VOM repository.symantec. To generate reports about the details of data transfer between source and target replication hosts.x-based systems.x. 92 5–12 Veritas Cluster Server 6.com. you can deploy the solution to the management server and all hosts with replication solutions.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.

All rights reserved. with automatic notification of administrators when faults occur. 5–13 . 93 Lesson 5 High Availability in the Enterprise Copyright © 2012 Symantec Corporation. All rights reserved. Perhaps most important in a DR environment.Site-wide notification and migration VOM simplifies management of disaster recovery. The Management Console also provides valuable diagnostic tools. such as: • Uptime analysis • Configuration analysis • Agent inventory • Additional predefined reports that can be scheduled and saved Copyright © 2012 Symantec Corporation. VOM enables you to perform an entire site migration and recovery with a single action. providing policy-based monitoring of critical events.

By scanning systems across the data center to ensure that existing HA/DR plans are applied seamless. Copyright © 2012 Symantec Corporation. databases. clusters. Disaster Recovery Advisor helps to limit the risk of infrastructure and application downtime. the software alerts the system administrator so the issues can be resolved before business operations are impacted. and replication infrastructures using a knowledge base containing over 4. . DRA scans storage.600 risk signatures. All rights reserved. operating in read-only mode. the implementation of Disaster Recovery Advisor is unobtrusive and non-disruptive. When gaps are discovered.Disaster Recovery Advisor Veritas Disaster Recovery Advisor (DRA) monitors high availability and disaster recovery configurations to ensure data center recoverability. All rights reserved. As an agentless solution. servers. Monitoring and management is simple with status dashboards that provide detailed insight into the data center's environment. 94 5–14 Veritas Cluster Server 6.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.

All rights reserved. • Hosted hypervisor has hosted operating system running on the server and a hypervisor running within the OS. each running an operating system. and virtual I/O. VMware ESX server is an example of this technology.Virtualization support Copyright © 2012 Symantec Corporation. allocating resources to partitions. All rights reserved. Server virtualization approaches 95 Most customers are using more than one virtualization methodology within their IT infrastructure. operating system container technology allows for the partitioning of the OS into containers to control access to the applications running within the containers. The slide illustrates four virtualization approaches and examples of platforms that utilize that type of virtualization. Sun Domains and HP nPartitions are example solutions using this technology. • Finally. • Bare metal hypervisor consists of a hypervisor process running directly on the server hardware. I/O flows from the virtual machines. Linux KVM and Solaris LDOM are examples using this technology. Lesson 5 High Availability in the Enterprise Copyright © 2012 Symantec Corporation. to the local operating system drivers. each with unique terms such as control domain. which enables creating and maintaining virtual machines. Each major UNIX operating system vendor has a virtualization technology. through the hypervisor. guest. host. and then to the server hardware. 5–15 . • Hardware partitioning subdivides a server.

0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. however clusters cannot contain both VMs and the physical machine hosting VMs. • Hosted hypervisor Storage Foundation and VCS can run on both the host operating system and virtual machines. The VMs may be migrated to different physical servers by virtualization HA technology.Symantec solutions for virtualization Copyright © 2012 Symantec Corporation. 96 5–16 Veritas Cluster Server 6. . All rights reserved. VCS can be used to make VMs highly available. The slide shows how Storage Foundation and VCS works in each of the virtualization environments. All rights reserved. • Operating system containers Storage Foundation and VCS can run on the host operating system and can control the startup of the security container as well as the applications within them. • Hardware partitioning Storage Foundation and VCS run within partitions and generally partitions are not migrated between physical machines. • Bare metal hypervisor Storage Foundation and VCS run within the virtual machines.

As shown in the diagram. different SFHA components can be deployed on hosts or on virtual machines running supported guest operating systems. 97 Lesson 5 High Availability in the Enterprise Copyright © 2012 Symantec Corporation. All rights reserved. Veritas Operations Manager can be used to manage storage and clustering in both physical and virtual environments. Copyright © 2012 Symantec Corporation. 5–17 .0 can be deployed in a number of configurations in both physical and virtual environments. All rights reserved.Symantec across physical and virtual environments Storage Foundation High Availability 6.

0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. and storage platforms. Organizations can manage entire business services end-to-end with built in resiliency. even if the business service is run across multiple virtualization technologies. Copyright © 2012 Symantec Corporation. All rights reserved. All products in the portfolio are tightly integrated to help IT organizations move confidently to a private cloud architecture. and making them available ondemand for infrastructure HA or management solutions to take appropriate action to maintain service continuity. 98 5–18 Veritas Cluster Server 6. operating systems. All rights reserved.Building resiliant private clouds The Storage Foundation High Availability solutions from Symantec enable IT organizations to build resilient private clouds by transforming their existing infrastructure. . by pooling information resources even across heterogeneous infrastructure. SFHA extends the core concepts of virtualization.

All rights reserved.Summary Copyright © 2012 Symantec Corporation. All rights reserved. 99 Lesson 5 High Availability in the Enterprise Copyright © 2012 Symantec Corporation. 5–19 . and Veritas Operations Manager that specifically enhance high availability and disaster recovery solutions in enterprise data centers. This lesson summarized some of the features of Veritas Cluster Server. Storage Foundation.

.Copyright © 2012 Symantec Corporation. All rights reserved.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. 100 5–20 Veritas Cluster Server 6. All rights reserved.

All rights reserved. Appendix A Labs 101 .Copyright © 2012 Symantec Corporation.

Copyright © 2012 Symantec Corporation. 102 A–2 Veritas Cluster Server 6.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. All rights reserved. All rights reserved. .

Copyright © 2012 Symantec Corporation. All rights reserved. Exercise 5: Service group dependencies scenario 3 A typical multi-child service group dependency is configured so that one service group has two child service group dependencies causing a service group to have preference being online on startup and failover. All rights reserved. Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. 103 Exercise 3: Service group dependencies scenario 1 A typical service group dependency is configured so that one service group will have multiple parents causing one service group to have preference being online on startup and failover over another service group. Online and offline service group propagation is also examined. This lab contains the following exercises: Exercise 1: Checking lab prerequisites A verification that the virtual machines needed for this lab are powered on and functioning is performed. A–3 . Exercise 4: Service group dependencies scenario 2 A typical service group dependency is configured with a three level dependency causing one service group to have preference being online on startup and failover over another service group.Lab 1: Service group dependencies In this lab. Exercise 2: Service group and resource orientation The service groups and resources in the east cluster are examined. you will examine a variety of service group dependency configurations and behaviors.

1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Veritas Cluster Server 5. It is not necessary to label the terminal windows and you may decide which is terminal1 and which is terminal2. that you are logged in using the proper account and that any needed terminal windows are opened. Copyright © 2012 Symantec Corporation. All rights reserved. For example: sym1:terminal1. sym1 and sym2. – sym3 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. Note: If you are completing the lab exercises in order. and power on and log into sym3 and sym4. . – mgt › There is no need to log into this virtual machine at this time.Exercise 1: Checking lab prerequisites In this exercise. sym1:terminal2. this will require you to shutdown cps. 104 A–4 2 If you have machines running that are not used in this lab. and sym2:terminal2. 1 Verify that the following virtual machines shown are powered on. you verify that the virtual machines needed for this lab are powered on and functioning. – sym4 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. sym2:terminal1. Note: The terminal windows are referred to as hostname:terminal# throughout the labs. that you are logged using the indicated account and that the indicated terminal windows are opened. All rights reserved. shut down the operating system and power the machines off.

Modify to their default value if necessary. 5 Open the cluster configuration for update.east. sym3 Note: The appsg and testappsg service groups were added in an early Install and Configure lab using the Veritas Cluster Manager – Java Console. run the hastatus command in order to observe cluster changes as they happen in subsequent exercises. If any resources are set to non critical then modify them. 3 Determine if all resources in all service groups other than the ClusterService service group are set to critical. – Verifying that there are no service group dependencies. Open.lab05 1 From sym3:terminal1. 6 From sym3:terminal2. – Verifying that all service groups are online on the sym3 system and switching any that need to be switched. 105 2 Display the state of all resources by listing the resources for each service group and the dependencies between each resource in each service group. All rights reserved. A–5 . Open. – Listing the state of each service group. then consult with your instructor on how to copy in a replacement main. you examine the service groups and resources in the east cluster. save and close the cluster configuration as appropriate.cf file located at: /student/labs/vcs/vcs60/maincf/IC/ main. 4 Confirm that the FaultPropagation and ManageFaults service group attributes are set to 1 and ALL respectively for each service group. All rights reserved. Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation.cf. perform a summary status on the cluster by: Copyright © 2012 Symantec Corporation. If those lab exercises were skipped. save and close the cluster configuration as appropriate.Exercise 2: Service group and resource orientation In this exercise.

while not necessary. Copyright © 2012 Symantec Corporation. then ensure that all three service groups are brought online on sym3. The hagrp -wait commands. appsg. Can all three service groups be brought offline using just one command? If not. appsg. .Exercise 3: Service group dependencies scenario 1 In this exercise. 4 Use a single hagrp command to take the dbsg. you configure a typical service group dependency so that one service group will have multiple parents causing one service group to have preference being online on startup and failover over another service group. have been included to be consistent with other lab exercises. take all of the service groups except the ClusterService service group offline on all cluster systems. 1 From sym3:terminal1. then ensure that all three service groups are brought offline on sym3. Save but do not close the VCS configuration. and websg service groups offline on sym3. Veritas Cluster Server 5. – appsg depends on dbsg (online local firm) – websg depends on dbsg (online local firm) 106 A–6 3 Use a single hagrp command with the propagate option to bring the dbsg.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. sym3 Note: The service groups in this exercise will come online and go offline very quickly. All rights reserved. 2 Create and confirm dependencies between the appsg and dbsg and between the websg and dbsg service groups as indicated below. and websg service groups online on sym3. Can all three service groups be brought online using just one command? If not. All rights reserved.

5

Using a single hagrp command with the propagate option, bring the dbsg
and websg service groups online on sym3. Attempt to bring the appsg service
group online on sym4. Were you successful? If not successful, then bring the
appsg service group online on sym3.

6

Fault the appsg service group by removing the /var/tmp/appip file
followed by a probe of the appip resource on sym3. Do any service groups
failover?

7

Clear the appip resource fault and bring the appsg service group back online
on sym3.

8

Fault the dbsg service group by removing the /var/tmp/dbip file followed
by a probe of the dbip resource on sym3. Do any service groups failover?

9

Clear the dbip resource fault and take the dbsg, websg, appsg, and testappsg
service groups offline on any system they may be online.

10 Link the testappsg service group as a parent of the appsg service group with
Copyright © 2012 Symantec Corporation. All rights reserved.

an offline local dependency. Save, but do not close the VCS configuration.

107

Note: This will configure a preference for the appsg service group running on
a system over the testappsg service group and force the testappsg to
switch upon a successful failover of the appsg service group.

Lab 1: Service group dependencies
Copyright © 2012 Symantec Corporation. All rights reserved.

A–7

11 Bring the dgsg, appsg, and websg service groups online on sym3. Attempt to

bring the testappsg service group online on sym3. Were you successful? If
not, attempt to bring the testappsg service group online on sym4.

12 Fault the dbsg service group by removing the /var/tmp/dbip file followed

by a probe of the dbip resource on sym3. Do any service groups failover?

13 Take the testappsg service group offline on sym3 and clear the dbip resource

fault. Then, use a single command to take the dbsg, websg, appsg, and
testappsg service groups offline on any system where they may be online.
14 Unlink the service group dependencies between the testappsg and appsg

Copyright © 2012 Symantec Corporation. All rights reserved.

service groups and between the dbsg, websg and appsg service groups. Save,
but do not close the VCS configuration.

108 A–8

Veritas Cluster Server 5.1 for UNIX: Install and Configure
Copyright © 2012 Symantec Corporation. All rights reserved.

Exercise 4: Service group dependencies scenario 2
In this exercise, you configure a typical service group dependency with a three
level dependency causing one service group to have preference being online on
startup and failover over another service group.

sym3
Note: The service groups in this exercise will come online and go offline very
quickly. The hagrp -wait commands, while not necessary, have been
included to be consistent with other lab exercises.

1

From sym3:terminal1, create dependencies between the appsg and dbsg
service groups, between the websg and appsg service groups and between the
testappsg and appsg service groups as indicated below. Save but do not close
the VCS configuration.
– appsg depends on dbsg (online local firm)
– websg depends on appsg (online local firm)
– testappsg depends on appsg (offline local)
Bring the testappsg service group online on sym3. Use a single hagrp
command with the propagate option to bring the dbsg, appsg, and websg
service groups online on sym3. Were you successful? If not, then switch the
testappsg service group to sym4 and retry. Can all three service groups be
brought online using just one command? If not, then ensure that all three
service groups are brought online on sym3.

Copyright © 2012 Symantec Corporation. All rights reserved.

2

109

Lab 1: Service group dependencies
Copyright © 2012 Symantec Corporation. All rights reserved.

A–9

Copyright © 2012 Symantec Corporation. All rights reserved.

110

A–10

3

Using a single hagrp command with the propagate option, take the dbsg,
appsg, and websg service groups offline on sym3. Can all three service
groups be brought offline using just one command? If not, then ensure that all
three service groups are brought offline on sym3.

4

Using a single hagrp command with the propagate option, bring the dbsg,
appsg, and websg service groups online on sym3.

5

Fault the appsg service group by removing the /var/tmp/appip file
followed by a probe of the appip resource on sym3. Do any service groups
failover?

6

Clear the appip resource fault and use a single hagrp command with the
propagate option to bring the appsg service group back online on sym3.

7

Fault the dbsg service group by removing the /var/tmp/dbip file followed
by a probe of the dbip resource on sym3. Do any service groups failover?

8

Take the testappsg service group offline on sym3 and clear the dbip resource
fault. Then, use a single command to bring the dbsg, websg, appsg, and
testappsg service groups offline on any system they may be online.

9

Unlink the service group dependencies between the testappsg and appsg
service groups, between the dbsg and appsg service groups and between the
websg and appsg service groups. Save, but do not close the VCS
configuration.

Veritas Cluster Server 5.1 for UNIX: Install and Configure
Copyright © 2012 Symantec Corporation. All rights reserved.

Exercise 5: Service group dependencies scenario 3
In this exercise, you configure a typical multi-child service group dependency so
that one service group has two child service group dependencies causing a service
group to have preference being online on startup and failover.

sym3
Note: The service groups in this exercise will come online and go offline very
quickly. The hagrp -wait commands, while not necessary, have been
included to be consistent with other lab exercises.

1

From sym3:terminal1, create dependencies between the websg and appsg
service groups and websg and dbsg service groups as indicated below. Save but
do not close the VCS configuration.

Copyright © 2012 Symantec Corporation. All rights reserved.

– websg depends on appsg (online local firm)
– websg depends on dbsg (online local firm)
– testappsg depends on appsg (offline local)

111

2

Bring the testappsg service group online on sym4. Using a single hagrp
command with the propagate option, bring the dbsg, appsg, and websg
service groups online on sym3. Were you able to bring the websg, dbsg, and
appsg service groups online with the online propagate option?

3

Using a single hagrp command with the propagate option, take the websg,
dbsg, and appsg and service groups offline on sym3. Can all three service
groups be brought offline using just one command? If not, then ensure that all
three service groups are brought offline on sym3.

Lab 1: Service group dependencies
Copyright © 2012 Symantec Corporation. All rights reserved.

A–11

4

Using a single hagrp command with the propagate option, bring the dbsg,
appsg, and websg service groups online on sym3.

5

Fault the websg service group by removing the /var/tmp/webvip file
followed by a probe of the webvip resource on sym3. Do any service groups
failover?

6

Clear the webvip resource fault and bring the websg service group back online
on sym3.

7

Fault the dbsg service group by removing the /var/tmp/dbip file followed
by a probe of the dbip resource on sym3. Do any service groups failover?

8

Take the appsg service group offline on sym3. Then, bring the websg, appsg,
and dbsg service groups online on sym4. Account for the testappsg service
group.

9

Clear the dbip resource fault.

10 Unlink the service group dependencies between the testappsg and appsg

Copyright © 2012 Symantec Corporation. All rights reserved.

service groups, between the dbsg and appsg service groups, and between the
websg and appsg service groups. Save and close the VCS configuration.

112

11 From sym3:terminal2, terminate the hastatus command.

End of lab

A–12

Veritas Cluster Server 5.1 for UNIX: Install and Configure
Copyright © 2012 Symantec Corporation. All rights reserved.

.Lab 2: Merging clusters In this lab. Exercise 3: Merging cluster infrastructure The systems from one cluster are added to another cluster. This lab contains the following exercises: Exercise 1: Checking lab prerequisites A verification that the virtual machines needed for this lab are powered on and functioning is performed. Lab 2: Merging clusters A–13 Copyright © 2012 Symantec Corporation. Exercise 2: Merge cluster preparation Two clusters are prepared for merging. Copyright © 2012 Symantec Corporation. you will merge the east cluster to the west cluster forming one four-node west cluster. 113 Exercise 4: Adding service groups and resources The service groups and resources from one of the original are added to the merged cluster. All rights reserved. Exercise 5: Merged cluster verification The merged cluster is verified. All rights reserved.

and sym2:terminal2. – sym2 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. sym2:terminal1. All rights reserved. 114 Verify that the following virtual machines shown are powered on. . 1 – mgt › There is no need to log into this virtual machine at this time. you verify that the virtual machines needed for this lab are powered on and functioning. All rights reserved. For example: sym1:terminal1. that you are logged using the indicated account and that the indicated terminal windows are opened. sym1:terminal2. that you are logged in using the proper account and that any needed terminal windows are opened. Copyright © 2012 Symantec Corporation. It is not necessary to label the terminal windows and you may decide which is terminal1 and which is terminal2. – sym3 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Note: The terminal windows are referred to as hostname:terminal# throughout the labs.Exercise 1: Checking lab prerequisites In this exercise. – sym1 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. – sym4 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. A–14 Veritas Cluster Server 5.

shut down the operating system and power the machines off. Note: If you are completing the lab exercises in order. All rights reserved. 115 Lab 2: Merging clusters A–15 Copyright © 2012 Symantec Corporation.2 If you have machines running that are not used in this lab. . this will require you to power on and log into sym1 and sym2. All rights reserved. Copyright © 2012 Symantec Corporation.

Exercise 2: Merge cluster preparation
In this exercise, you prepare two clusters for merging.

sym1
Note: In this lab there are no iSCSI LUNs that are visible to all four systems, so
merging enabled I/O fencing using disks cannot be part of the cluster
merge lab. Therefore, for lab purposes, I/O fencing is re-configured to
disabled mode on both clusters.

1

From sym1:terminal1, navigate to the /opt/VRTS/install directory and
run the installsfha script with the fencing option using the following
information.
– Reconfigure fencing in disabled mode.
– Stop VCS and apply the fencing changes.
– Do not view the summary file.

2

Use the gabconfig and service vxfen status commands to confirm
that I/O fencing is configured. Use the vxfenadm command to confirm that
I/O fencing is running in disabled mode.

sym3

Copyright © 2012 Symantec Corporation. All rights reserved.

3

116

From sym3:terminal1, navigate to the /opt/VRTS/install directory and
run the installsfha script with the fencing option using the following
information.
– Reconfigure fencing in disabled mode.
– Stop VCS and apply the fencing changes.
– Do not view the summary file.

4

A–16

Use the gabconfig and service vxfen status commands to confirm
that I/O fencing is configured. Use the vxfenadm command to confirm that
I/O fencing is running in disabled mode.

Veritas Cluster Server 5.1 for UNIX: Install and Configure
Copyright © 2012 Symantec Corporation. All rights reserved.

Note: In this lab, there is a conflicting duplicate named appsg service group in
both the west and east clusters. This would cause errors during a merge.
The appsg service group in the west cluster would have precedence so the
appsg service group in the east cluster must be renamed or, as performed
in this lab, deleted from the configuration.
5

Take the appsg service group offline and list its resources and dependencies.

6

Open the VCS configuration for update and delete each resource in the appsg
service group in resource dependency order. Then, delete the appsg service
group and save and close the VCS configuration.

7

Navigate to the /etc/VRTSvcs/conf/config directory and use the
hacf -cftocmd command to create a main.cmd file. Copy the
main.cmd file to eastmain.cmd.

8

Edit the eastmain.cmd file to remove all commands other than those
related to the websg, testappsg, dbsg service groups, their resources, and their
resource dependencies.

Copyright © 2012 Symantec Corporation. All rights reserved.

Note: Alternatively, copy the
/student/labs/vcs/vcs60/maincf/CM/eastmain.cmd
file to /etc/VRTSvcs/conf/config/eastmain.cmd.

117

After you have made the edits the contents of the file should be:
hagrp -add dbsg
hagrp -modify dbsg SystemList sym3 0 sym4 1
hagrp -modify dbsg AutoStartList sym3 sym4
hagrp -modify dbsg SourceFile "./main.cf"
hares -add dbdg FileOnOff dbsg
hares -modify dbdg PathName "/var/tmp/dbdg"
hares -modify dbdg Enabled 1
hares -add dbip FileOnOff dbsg
hares -modify dbip PathName "/var/tmp/dbip"
hares -modify dbip Enabled 1
hares -add dblistener FileOnOff dbsg
hares -modify dblistener PathName "/var/tmp/
dblistener"
hares -modify dblistener Enabled 1
hares -add dbmnt FileOnOff dbsg
hares -modify dbmnt PathName "/var/tmp/dbmnt"

Lab 2: Merging clusters

A–17
Copyright © 2012 Symantec Corporation. All rights reserved.

Copyright © 2012 Symantec Corporation. All rights reserved.

hares -modify dbmnt Enabled 1
hares -add dbnic FileOnOff dbsg
hares -modify dbnic PathName "/var/tmp/dbnic"
hares -modify dbnic Enabled 1
hares -add dboracle FileOnOff dbsg
hares -modify dboracle PathName "/var/tmp/
dboracle"
hares -modify dboracle Enabled 1
hares -add dbvol FileOnOff dbsg
hares -modify dbvol PathName "/var/tmp/dbvol"
hares -modify dbvol Enabled 1
hagrp -add testappsg
hagrp -modify testappsg SystemList sym3 0 sym4 1
hagrp -modify testappsg AutoStartList sym3 sym4
hagrp -modify testappsg Operators oper
hagrp -modify testappsg SourceFile "./main.cf"
hares -add testappdg FileOnOff testappsg
hares -modify testappdg PathName "/var/tmp/
testappdg"
hares -modify testappdg Enabled 1
hares -add testappmnt FileOnOff testappsg
hares -modify testappmnt PathName "/var/tmp/
testappmnt"
hares -modify testappmnt Enabled 1
hares -add testappnic FileOnOff testappsg
hares -modify testappnic PathName "/var/tmp/
testappnic"
hares -modify testappnic Enabled 1
hares -add testappproc FileOnOff testappsg
hares -modify testappproc PathName "/var/tmp/
testappproc"
hares -modify testappproc Enabled 1
hares -add testappip FileOnOff testappsg
hares -modify testappip PathName "/var/tmp/
testappip"
hares -modify testappip Enabled 1
hares -add testappvol FileOnOff testappsg
hares -modify testappvol PathName "/var/tmp/
testappvol"
hares -modify testappvol Enabled 1

118

A–18

Veritas Cluster Server 5.1 for UNIX: Install and Configure
Copyright © 2012 Symantec Corporation. All rights reserved.

Copyright © 2012 Symantec Corporation. All rights reserved.

119

hagrp -add websg
hagrp -modify websg SystemList sym3 0 sym4 1
hagrp -modify websg AutoStartList sym3 sym4
hagrp -modify websg Operators oper
hagrp -modify websg SourceFile "./main.cf"
hares -add webapache FileOnOff websg
hares -modify webapache PathName "/var/tmp/
webapache"
hares -modify webapache Enabled 1
hares -add webdg FileOnOff websg
hares -modify webdg PathName "/var/tmp/webdg"
hares -modify webdg Enabled 1
hares -add webmnt FileOnOff websg
hares -modify webmnt PathName "/var/tmp/webmnt"
hares -modify webmnt Enabled 1
hares -add webnic FileOnOff websg
hares -modify webnic PathName "/var/tmp/webnic"
hares -modify webnic Enabled 1
hares -add webvip FileOnOff websg
hares -modify webvip PathName "/var/tmp/webvip"
hares -modify webvip Enabled 1
hares -add webvol FileOnOff websg
hares -modify webvol PathName "/var/tmp/webvol"
hares -modify webvol Enabled 1
hares -link dbip dbnic
hares -link dblistener dbip
hares -link dblistener dboracle
hares -link dbmnt dbvol
hares -link dboracle dbmnt
hares -link dbvol dbdg
hares -link testappmnt testappvol
hares -link testappproc testappmnt
hares -link testappproc testappip
hares -link testappip testappnic
hares -link testappvol testappdg
hares -link webapache webmnt
hares -link webapache webvip
hares -link webmnt webvol
hares -link webvip webnic
hares -link webvol webdg
Lab 2: Merging clusters

A–19
Copyright © 2012 Symantec Corporation. All rights reserved.

9

Shutdown VCS, IO fencing, GAB, and LLT on both nodes of the east cluster.

10 Rename the /etc/VRTSvcs/conf/config/main.cf file to

main.cf.east on sym3 and sym4.

Copyright © 2012 Symantec Corporation. All rights reserved.

Note: In order for the merge utility to work correctly, the main.cf files on
the east cluster nodes must not exist.

120 A–20

Veritas Cluster Server 5.1 for UNIX: Install and Configure
Copyright © 2012 Symantec Corporation. All rights reserved.

4 Use the vxfenadm command to check I/O fencing. sym1 1 From sym1:terminal1. Use eth4 and eth5 as the private links and eth0 as the low priority link. – – – – – Enter sym1 as the name of one node of the west cluster.Exercise 3: Merging cluster infrastructure In this exercise. . navigate to the /opt/VRTS/install directory and run the . 6 Display the contents of the /etc/llttab. Optionally. 3 Use the gabconfig command to check GAB status. and /etc/gabtab files. Copyright © 2012 Symantec Corporation. you add the systems from one cluster to another cluster. review the log file. Log file: 121 2 Perform a summary status of the cluster noting that none of the former east cluster service groups have been added. performed this step on all cluster nodes. Optionally. Lab 2: Merging clusters A–21 Copyright © 2012 Symantec Corporation. perform this step on all cluster nodes. Enter sym3 and sym4 as the systems to be added to the west cluster. All rights reserved. All rights reserved. 5 Use the lltstat command to check the LLT configured and active status. Optionally. – Do not view the summary file./installsfha -addnode command taking note of the merge pre-requisites and using the following information. Use eth0 as the public NIC used for the cluster virtual IP. /etc/llthosts. Record the log file located in the /opt/VRTS/install/logs directory.

cf file noticing the following elements.10. – The websg.2. All four systems are defined as cluster members.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. The cluster virtual ip is 10. All rights reserved. \ The cluster name is west. Copyright © 2012 Symantec Corporation. – – – – 122 A–22 Veritas Cluster Server 5. nfssg. – The appsg. . and orasg service groups from the original west cluster are configured and remain restricted to sym1 and sym2. and testappsg from the east cluster are not configured.51. dbsg. All rights reserved.7 Display the /etc/VRTSvcs/conf/config/main. The SystemList and AutoStartList service group attributes for the ClusterService service group configure all four cluster systems.

All rights reserved. Note: The oper user add is not part of the eastmain. navigate to the /etc/VRTSvcs/conf/config directory and open the VCS configuration for update 2 Run the sh -x .cmd command and observe the output taking notice of the VCS warning when failing to add the VCS user named oper as an Operator for the testappsg and websg service groups. All rights reserved. Save and close the VCS configuration.cmd file and would need to be re-added and re-configured later on. you add the service groups and resources from one of the original clusters to the merged cluster.Exercise 4: Adding service groups and resources In this exercise. ./eastmain. Copyright © 2012 Symantec Corporation. sym3 1 From sym3:terminal1. 3 123 Lab 2: Merging clusters A–23 Copyright © 2012 Symantec Corporation.

. – The SystemList and AutoStartList service group attributes for the websg. and dbsg service groups remain set to sym3 and sym4. you verify the merged cluster.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. – The SystemList and AutoStartList service group attributes for the ClusterService service group have been modified for all four cluster systems. Copyright © 2012 Symantec Corporation. End of lab 124 A–24 Veritas Cluster Server 5.Exercise 5: Merged cluster verification In this exercise. – The oper user from the old east cluster is not defined nor is the Operator service group attribute for the testappsg and websg service groups set to the oper user. sym3 1 From sym3:terminal1. Note: Consideration needs to be given to activated triggers configured at any service group and/or resource level if the service group is going to be re-configured to run on a new cluster system. Note: These service groups cannot be online on sym3 and sym4 due to shared LUN restrictions. All rights reserved. testappsg. All rights reserved. 2 Display /etc/VRTSvcs/conf/config/main. perform a summary status on the cluster taking note of the service groups that are not online. and orasg service groups remain set to sym1 and sym2.cf file and notice the following. Note: These service groups could be online on sym1 and sym2 and could be modified to accommodate that. nfssg. – The SystemList and AutoStartList service group attributes for the appsg.

Exercise 4: Testing load failover policy The load failover policy is examined.cf file to show how to configure and test failover policies using the Veritas Cluster Manager Java Console.Lab 3: Failover policies In this lab. Exercise 6: Stopping the simulator The simulation used in the lab is examined and the Veritas VCS Simulator is terminated. 125 Exercise 3: Testing priority failover policy The default priority failover policy is examined. . This lab contains the following exercises: Exercise 1: Checking lab prerequisites A verification that the virtual machines needed for this lab are powered on and functioning is performed. Exercise 5: Testing prerequisites and limits Prerequisites and limits are examined and added to the load failover policy settings. you use the Veritas Cluster Server Simulator with a preconfigured main. Lab 3: Failover policies A–25 Copyright © 2012 Symantec Corporation. All rights reserved. Copyright © 2012 Symantec Corporation. All rights reserved. Exercise 2: Starting the simulator The simulation used in the lab is examined and the Veritas VCS Simulator is started.

that you are logged using the indicated account and that the indicated terminal windows are opened. . shut down the operating system and power the machines off. All rights reserved. that you are logged in using the proper account and that any needed terminal windows are opened. All rights reserved. 1 Verify that the following virtual machines shown are powered on. and sym2:terminal2. – mgt › There is no need to log into this virtual machine at this time. It is not necessary to label the terminal windows and you may decide which is terminal1 and which is terminal2. sym3 and sym4. – winclient › Log in with credentials: Account: Administrator Password: veritas Note: The terminal windows are referred to as hostname:terminal# throughout the labs. 2 126 A–26 If you have machines running that are not used in this lab. sym1:terminal2. you verify that the virtual machines needed for this lab are powered on and functioning. For example: sym1:terminal1. Note: If you are completing the lab exercises in order. Copyright © 2012 Symantec Corporation.Exercise 1: Checking lab prerequisites In this exercise.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. and power on and log into winclient. Veritas Cluster Server 5. this will require you to shutdown sym1. sym2. sym2:terminal1.

3 Without making any changes. 127 5 Verify the wlm simulation. 2 Open the main. 6 Start the wlm simulation. you examine the simulation used in the lab and start the Veritas VCS Simulator. Copyright © 2012 Symantec Corporation. . All rights reserved.Exercise 2: Starting the simulator In this exercise. 7 Launch the VCS – Java Console and log in using the following credentials. – User name: admin – Password: password Lab 3: Failover policies A–27 Copyright © 2012 Symantec Corporation.cf file using the WordPad application. Note: The VCS Simulator may take a moment to display as it discovers any running simulations even thought there will not be any. All rights reserved. Note: The status of the cluster name will have a green check mark upon successful startup. Then. review the contents of the main. winclient 1 From the winclient desktop.cf file. 4 Start the Veritas VCS Simulator. use Windows Explorer to navigate to the C:\Progam Files (x86)\VERITAS\VCS Simulator\wlm\ conf\config folder. close the Wordpad and Windows Explorer windows.

S4 (3) S2 B2 S1 (4). S2 (1). . S4 (4) S1 A2 S1 (1). S4 (1) S4 Copyright © 2012 Symantec Corporation. Service Group Member Systems (Priority) AutoStartList A1 S1 (1). S2 (4). S3 (4). S3 (2). S3 (3). S3 (2). S4 (1) S4 D2 S1 (2). S4 (2) S3 C2 S1 (3). S4 (4) S1 B1 S1 (4). S2 (3). All rights reserved.From the Java Console. 8 128 A–28 Veritas Cluster Server 5. S2 (4). S2 (2). S3 (1). S2 (1). S2 (3). S2 (2). verify that the Member Systems and their Priority and their AutoStartList attribute are set to the values shown in the following table. All rights reserved. S3 (4). S4 (2) S3 D1 S1 (2). S3 (3).1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. S3 (1). S4 (3) S2 C1 S1 (3).

. Lab 3: Failover policies A–29 Copyright © 2012 Symantec Corporation.Exercise 3: Testing priority failover policy In this exercise. Service Group A1 will fail over to: 6 Clear the faults in the A1 service group. 3 Service Group System S1 A1 Online A2 Online System S2 B1 Online B2 Online System S3 C1 Online C2 Online System S4 D1 Online D2 Online If it faults. where will the A1 service group fail over to? Verify this failover by faulting a critical resource in the A1 service group. 2 Verify that all service groups are online as shown in the following table. winclient 1 From the Java Console. verify that the failover policy of all service groups is Priority. All rights reserved. All rights reserved. Service Group A1 will fail over to: Copyright © 2012 Symantec Corporation. 4 129 If the A1 service group faults again without clearing the previous fault. you examine the default priority failover policy. Service Group A1 will fail over to: 5 Clear the faults in the A1 service group. Where will the service group fail over to now? Verify the failover by faulting a critical resource in the A1 service group. where should it fail over? Verify the failover by faulting a critical resource in the A1 service group.

you examine the load failover policy. Service Group AvailableCapacity S1 50 S2 50 S3 0 S4 0 Veritas Cluster Server 5.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. 3 Set the Load attribute for each service group as shown in the following table. All rights reserved. 2 Set the FailOverPolicy attribute to Load for the eight service groups.Exercise 4: Testing load failover policy In this exercise. 5 Verify that the system’s AvailableCapacity attribute is as shown in the following table. . open the cluster configuration for update. Note: The S3 and S4 systems’ Capacity attribute will not be changed and defaults to 100. 4 130 A–30 Service Group Load A1 75 A2 75 B1 75 B2 75 C1 50 C2 50 D1 50 D2 50 Set the S1 and S2 systems’ Capacity attributes to 200. Copyright © 2012 Symantec Corporation. All rights reserved. winclient 1 From the Java Console.

6 Save the configuration changes. where will the A1. 10 If the S2 system fails. . Service Group A1 will fail over to: 9 Verify that the system’s AvailableCapacity attribute is as shown in the following table. where will the A1 service group fail over to? Verify this failover by faulting a critical resource in the A1 service group. All rights reserved. B1 and B2 service groups that are 131 Online on S2 fail over? Verify this failover by powering off the S2 system in Cluster Manager. The A1 service group will fail over to: The B1 service group will fail over to: The B2 service group will fail over to: Lab 3: Failover policies A–31 Copyright © 2012 Symantec Corporation. 7 Verify that all service groups are online as shown in the following table. All rights reserved. Service Group AvailableCapacity S1 125 S2 -25 S3 0 S4 0 Copyright © 2012 Symantec Corporation. 8 Service Group System S1 A1 Online A2 Online System S2 B1 Online B2 Online System S3 C1 Online C2 Online System S4 D1 Online D2 Online If it faults.

13 Verify that the system’s AvailableCapacity attribute is as shown in the following table. . if you want to view the modifications to the main. However.cf file then save the changes. and return the service groups to their startup locations. Service Group AvailableCapacity S1 50 S2 50 S3 0 S4 0 14 Save and close the configuration changes. Copyright © 2012 Symantec Corporation. All rights reserved. All rights reserved.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Service Group AvailableCapacity S1 -25 S2 200 S3 -75 S4 0 12 Power up the S2 system. Note: Saving changes to the configuration is not necessary for purposes of this lab. clear all faults.11 Verify that the system’s AvailableCapacity attribute is as shown in the following table. 132 A–32 Veritas Cluster Server 5.

2 Set the Limits attribute for each system to the key ABGroup with a value of 3. open the cluster configuration for update. 3 Set the Prerequisites attribute for the A1. All rights reserved. The A2 service group will fail over to: 133 Lab 3: Failover policies A–33 Copyright © 2012 Symantec Corporation. 4 Save the configuration changes. and D2 service groups. Explain the failover actions that occurred. C2. where will the A1 and A2 service groups that are Online on S1 fail over? Verify this failover by powering off the S1 system in Cluster Manager. CAUTION Do not modify the Prerequisites attribute for the C1. . All rights reserved. 5 If the S1 system fails.Exercise 5: Testing prerequisites and limits In this exercise. winclient 1 From the Java Console. A2. you examine the prerequisites and limits and add them to the load failover policy settings. The A1 service group will fail over to: Copyright © 2012 Symantec Corporation. D1. B1 and B2 service groups to be ABGroup with a value of 1.

Note: Saving changes to the configuration is not necessary for purposes of this lab. The A1 service group will fail over to: The B1 service group will fail over to: The B2 service group will fail over to: 7 If the S3 system fails. where will the A2.cf file then save the changes. if you want to view the modifications to the main. C1 and C2 service groups that are Online on S3 fail over? Verify this failover by powering off the S3 system in Cluster Manager.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Veritas Cluster Server 5. 8 134 A–34 S4 Save and close the configuration changes. However. All rights reserved. B1 and B2 service groups that are Online on S2 fail over? Verify this failover by powering off the S2 system in Cluster Manager. where will the A1. Explain the failover actions that occurred. The A2 service group will fail over to: The B1 service group will fail over to: The C1 service group will fail over to: The C2 service group will fail over to: Copyright © 2012 Symantec Corporation. Explain the failover actions that occurred.6 If the S2 system fails. All rights reserved. B1. .

you must ensure the main. You can verify the configuration only in the Simulator GUI after the cluster is stopped. stop the wlm cluster. Note: The Veritas Cluster Manager Java Console should close as well. 4 Close the Simulator Java Console. If it does not then close it manually.cf syntax is correct. Copyright © 2012 Symantec Corporation. End of lab 135 Lab 3: Failover policies A–35 Copyright © 2012 Symantec Corporation. All rights reserved. . winclient 1 Log out from Cluster Explorer. All rights reserved. 2 From the Simulator Java Console. you terminate the simulation and the Veritas VCS Simulator. Note: If you intend to move this configuration in to a running cluster. 3 Verify the configuration.Exercise 6: Stopping the simulator In this exercise.

All rights reserved.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. 136 A–36 Veritas Cluster Server 5. All rights reserved. .Copyright © 2012 Symantec Corporation.

Lab 4: Creating a parallel network service group In this lab application networking is reconfigured to be more efficient. 137 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation. This lab contains the following exercises: Exercise 1: Checking lab prerequisites A verification that the virtual machines needed for this lab are powered on and functioning is performed. All rights reserved. All rights reserved. Exercise 2: Configuring a common parallel network service group A common parallel network service group and resources is configured. Copyright © 2012 Symantec Corporation. A–37 . Exercise 3: Replacing NIC resources with Proxy resources The pre-existing resources of type NIC supporting application VIPs in each application service group are replaced with resources of type Proxy.

– sym2 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. – sym3 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. – mgt › There is no need to log into this virtual machine at this time. and sym2:terminal2. that you are logged using the indicated account and that the indicated terminal windows are opened. sym1:terminal2. For example: sym1:terminal1. that you are logged in using the proper account and that any needed terminal windows are opened. All rights reserved.Exercise 1: Checking lab prerequisites In this exercise. 1 138 A–38 Verify that the following virtual machines shown are powered on. All rights reserved. . Copyright © 2012 Symantec Corporation. Veritas Cluster Server 5. Note: The terminal windows are referred to as hostname:terminal# throughout the labs. – sym1 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. sym2:terminal1. – sym4 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. you verify that the virtual machines needed for this lab are powered on and functioning. It is not necessary to label the terminal windows and you may decide which is terminal1 and which is terminal2.

139 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation.2 If you have machines running that are not used in this lab. sym2. sym3 and sym4. and power on and log into sym1. All rights reserved. this will require you to shutdown winclient. shut down the operating system and power the machines off. Note: If you are completing the lab exercises in order. A–39 . All rights reserved. Copyright © 2012 Symantec Corporation.

5 Modify the Parallel service group to configure the netsg service group as a parallel service group.Exercise 2: Configuring a common parallel network service group In this exercise. 7 Save the VCS configuration. but do not close it. 2 Use the hagrp command to create a service group named netsg. – Device is eth0 – Critical set to 0 (zero) 10 Display the resource attribute values for the netnic resource to confirm your input and key default resource attribute values. 8 Add a resource of type NIC named netnic to the netsg service group. All rights reserved. use the haconf command to open the cluster configuration for update. All rights reserved. 6 Display the service group attributes for the netsg service group to confirm your input and key default service group attribute values. . Veritas Cluster Server 5. and sym4 in that order. 9 Modify the Device and Critical resource attributes for the netnic resource using the following information. sym3. Copyright © 2012 Symantec Corporation. sym1 140 A–40 1 From sym1:terminal1.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. sym2. 3 Modify the SystemList to allow the netsg service group to run on the sym1. 4 Modify the AutoStartList attribute to allow the service group to start on all systems. you configure a common parallel network service group and resources.

12 Display the state of the netsg service group. but do not close it. 141 Note: The service group state is offline even though the NIC resource state is online. but do not close it. 17 Enable the netphantom resource and verify that it is enabled. Copyright © 2012 Symantec Corporation. Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation.11 Enable the netnic resource and verify that it is enabled. Note: It is not necessary to bring a resource of type Phantom online. Note: It is not necessary to bring a resource of type NIC online. 19 Save the VCS configuration. 16 Display the resource attribute values for the netphantom resource to confirm your input and key default resource attribute values. This is because VCS does not consider persistent resources when determining the state of a service group. 13 Save the VCS configuration. 15 Set the Critical resource attribute to 0 (zero) for the netphantom resource. All rights reserved. 14 Add a resource of type Phantom named netphantom to the netsg service group. All rights reserved. Display the state of the netphantom resource to ensure that it is online on both cluster systems. Display the state of the netnic resource to ensure that it is online on both cluster systems. A–41 . This is because VCS does not consider persistent resources when determining the state of a service group. Note: The service group state is offline even though the NIC resource state is online. 18 Display the state of the netsg service group.

– – – – Set the Critical attribute to 0 (zero). All rights reserved. Set the TargetResName attribute to netnic. you replace the pre-existing resources of type NIC that supporting application VIPs in each application service group with resources of type Proxy. Set the Critical attribute to 0 (zero). sym1 1 From sym1:terminal1. Set Enabled to 1 (one). identify the names of the resources of type NIC that are configured. – – – – 142 A–42 5 Set the Critical attribute to 0 (zero). list the resource dependencies associated with the listed resources of type NIC.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. All rights reserved. Link to the notifier and webip resources. Link to the nfsip resource.Exercise 3: Replacing NIC resources with Proxy resources In this exercise. . – – – – 4 Replace the resource of type NIC named csgnic with a resource of type Proxy named csgproxy using the following information. Link to the appip resource. Copyright © 2012 Symantec Corporation. Replace the resource of type NIC named nfsnic with a resource of type Proxy named nfsproxy using the following information. 2 Ignoring the resource of type NIC named netnic. Veritas Cluster Server 5. Set Enabled to 1 (one). 3 Replace the resource of type NIC named appnic with a resource of type Proxy named appproxy using the following information. Set the TargetResName attribute to netnic. Set the TargetResName attribute to netnic. Set Enabled to 1 (one).

Copyright © 2012 Symantec Corporation. Set Enabled to 1 (one). End of lab 143 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation.6 Replace the resource of type NIC named oranic with a resource of type Proxy named oraproxy using the following information. – – – – 7 Set the Critical attribute to 0 (zero). A–43 . All rights reserved. Set the TargetResName attribute to netnic. All rights reserved. Link to the oraip resource. Save and close the VCS configuration.

All rights reserved. . 144 A–44 Veritas Cluster Server 5.Copyright © 2012 Symantec Corporation.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. All rights reserved.

All rights reserved.Copyright © 2012 Symantec Corporation. Appendix B Lab Solutions 145 .

Copyright © 2012 Symantec Corporation. All rights reserved. All rights reserved. 146 B–2 Veritas Cluster Server 6. .0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.

Lab 1: Service group dependencies In this lab. Exercise 2: Service group and resource orientation The service groups and resources in the east cluster are examined. Copyright © 2012 Symantec Corporation. All rights reserved. B–3 . Exercise 4: Service group dependencies scenario 2 A typical service group dependency is configured with a three level dependency causing one service group to have preference being online on startup and failover over another service group. This lab contains the following exercises: Exercise 1: Checking lab prerequisites A verification that the virtual machines needed for this lab are powered on and functioning is performed. you will examine a variety of service group dependency configurations and behaviors. Exercise 5: Service group dependencies scenario 3 A typical multi-child service group dependency is configured so that one service group has two child service group dependencies causing a service group to have preference being online on startup and failover. Exercise 3: Service group dependencies scenario 1 A typical service group dependency is configured so that one service group will have multiple parents causing one service group to have preference being online on startup and failover over another service group. Online and offline service group propagation is also examined. All rights reserved. 147 Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation.

1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Veritas Cluster Server 5. Copyright © 2012 Symantec Corporation. sym1 and sym2. that you are logged using the indicated account and that the indicated terminal windows are opened. It is not necessary to label the terminal windows and you may decide which is terminal1 and which is terminal2. – sym4 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. 1 Verify that the following virtual machines shown are powered on. All rights reserved. All rights reserved. – mgt › There is no need to log into this virtual machine at this time. you verify that the virtual machines needed for this lab are powered on and functioning. that you are logged in using the proper account and that any needed terminal windows are opened. – sym3 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. For example: sym1:terminal1. shut down the operating system and power the machines off. Note: If you are completing the lab exercises in order. this will require you to shutdown cps. sym1:terminal2. and sym2:terminal2.Exercise 1: Checking lab prerequisites In this exercise. sym2:terminal1. . and power on and log into sym3 and sym4. Note: The terminal windows are referred to as hostname:terminal# throughout the labs. 148 B–4 2 If you have machines running that are not used in this lab.

a b hastatus -sum -.lab05 1 From sym3:terminal1. sym3 Note: The appsg and testappsg service groups were added in an early Install and Configure lab using the Veritas Cluster Manager – Java Console. Solution Copyright © 2012 Symantec Corporation. you examine the service groups and resources in the east cluster. perform a summary status on the cluster by: – Listing the state of each service group.SYSTEM STATE -. All rights reserved.System State Frozen A A RUNNING RUNNING 0 0 sym3 sym4 -.Group System Probed AutoDisabled State B B B B B B B B B B sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Y Y Y Y Y Y Y Y Y Y N N N N N N N N N N ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg hagrp -dep VCS WARNING V-16-1-50035 No Group dependencies are configured End of Solution 149 Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. then consult with your instructor on how to copy in a replacement main. – Verifying that there are no service group dependencies.cf. All rights reserved. If those lab exercises were skipped.Exercise 2: Service group and resource orientation In this exercise. B–5 .east. – Verifying that all service groups are online on the sym3 system and switching any that need to be switched.GROUP STATE -.cf file located at: /student/labs/vcs/vcs60/maincf/IC/ main.

All rights reserved. . All rights reserved.2 Display the state of all resources by listing the resources for each service group and the dependencies between each resource in each service group. Solution Copyright © 2012 Symantec Corporation. a 150 B–6 hares -state #Resource appdg appdg appmnt appmnt appnic appnic appproc appproc appip appip appvol appvol csgnic csgnic dbdg dbdg dbip dbip dblistener dblistener dbmnt dbmnt dbnic dbnic dboracle dboracle dbvol dbvol notifier notifier testappdg testappdg testappmnt testappmnt testappnic testappnic testappproc testappproc testappip testappip testappvol testappvol webapache webapache webdg webdg webip webip webmnt webmnt webnic webnic webvip webvip webvol webvol Attribute State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE ONLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE Veritas Cluster Server 5.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.

g 151 hares -dep | grep dbsg dbsg dbsg dbsg dbsg dbsg dbsg h dbip dblistener dblistener dbmnt dboracle dbvol dbnic dboracle dbip dbvol dbmnt dbdg hagrp -resources testappsg testappproc testappdg testappmnt testappnic testappip testappvol Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. All rights reserved.b hagrp -resources ClusterService webip csgnic notifier c hares -dep | grep ClusterService ClusterService notifier ClusterService webip d csgnic csgnic hagrp -resources appsg appproc appdg appmnt appnic appip appvol e hares -dep | grep "^appsg" appsg appsg appsg appsg appsg f appmnt appproc appproc appip appvol appvol appip appmnt appnic appdg hagrp -resources dbsg dbdg dbip dblistener dbmnt dbnic dboracle dbvol Copyright © 2012 Symantec Corporation. All rights reserved. B–7 .

Modify to their default value if necessary. If any resources are set to non critical then modify them. Open.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. save and close the cluster configuration as appropriate. Veritas Cluster Server 5. save and close the cluster configuration as appropriate.i hares -dep | grep testappsg testappsg testappsg testappsg testappsg testappsg j testappmnt testappproc testappproc testappip testappvol testappvol testappip testappmnt testappnic testappdg hagrp -resources websg webapache webdg webmnt webnic webvip webvol k hares -dep | grep websg websg websg websg websg websg webapache webapache webmnt webvip webvol webvip webmnt webvol webnic webdg End of Solution 3 Determine if all resources in all service groups other than the ClusterService service group are set to critical. . Copyright © 2012 Symantec Corporation. Open. Solution 152 B–8 a hares -list Critical=0 Group=appsg b hares -list Critical=0 Group=dbsg c hares -list Critical=0 Group=testappsg d hares -list Critical=0 Group=websg End of Solution 4 Confirm that the FaultPropagation and ManageFaults service group attributes are set to 1 and ALL respectively for each service group. All rights reserved. All rights reserved.

------------------- Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation.-------------------. Copyright © 2012 Symantec Corporation. B–9 . Solution 153 hastatus testappproc sym4 OFFLINE testappip sym3 ONLINE testappip sym4 OFFLINE ------------------------------------------------------------------------testappvol sym3 ONLINE testappvol sym4 OFFLINE webapache sym3 OFFLINE webapache sym4 ONLINE webdg sym3 OFFLINE ------------------------------------------------------------------------webdg sym4 ONLINE group resource system message --------------. All rights reserved.Solution hagrp -display -attribute ManageFaults FaultPropagation #Group ClusterService ClusterService # appsg appsg # dbsg dbsg # testappsg testappsg # websg websg Attribute FaultPropagation ManageFaults System global global Value 1 ALL FaultPropagation ManageFaults global global 1 ALL FaultPropagation ManageFaults global global 1 ALL FaultPropagation ManageFaults global global 1 ALL FaultPropagation ManageFaults global global 1 ALL End of Solution 5 Open the cluster configuration for update. run the hastatus command in order to observe cluster changes as they happen in subsequent exercises. All rights reserved.-------------------. Solution haconf -makerw End of Solution 6 From sym3:terminal2.

1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. All rights reserved. . End of Solution 154 B–10 Veritas Cluster Server 5. All rights reserved.webmnt sym3 OFFLINE webmnt sym4 ONLINE webnic sym3 OFFLINE webnic sym4 ONLINE ------------------------------------------------------------------------webvip sym3 OFFLINE webvip sym4 ONLINE webvol sym3 OFFLINE webvol sym4 ONLINE Copyright © 2012 Symantec Corporation.

you configure a typical service group dependency so that one service group will have multiple parents causing one service group to have preference being online on startup and failover over another service group. All rights reserved. d 155 hagrp -offline testappsg -any VCS NOTICE V-16-1-50733 Attempting to offline group on system sym3 e hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| End of Solution Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. Solution a hagrp -offline dbsg -any VCS NOTICE V-16-1-50733 Attempting to offline group on system sym3 b hagrp -offline appsg -any VCS NOTICE V-16-1-50733 Attempting to offline group on system sym3 c hagrp -offline websg -any VCS NOTICE V-16-1-50733 Attempting to offline group on system sym3 Copyright © 2012 Symantec Corporation. B–11 . take all of the service groups except the ClusterService service group offline on all cluster systems. All rights reserved. have been included to be consistent with other lab exercises. 1 From sym3:terminal1. sym3 Note: The service groups in this exercise will come online and go offline very quickly. The hagrp -wait commands.Exercise 3: Service group dependencies scenario 1 In this exercise. while not necessary.

Both top level parent service groups are independent so only one of the parents and the shared child dbsg service group can be brought online using the propagate option. Copyright © 2012 Symantec Corporation.2 Create and confirm dependencies between the appsg and dbsg and between the websg and dbsg service groups as indicated below. All rights reserved. then ensure that all three service groups are brought online on sym3. Can all three service groups be brought online using just one command? If not. All rights reserved. and websg service groups online on sym3. . b hagrp -wait websg State ONLINE -sys sym3 c hagrp -state #Group ClusterService ClusterService appsg Attribute State State State System sym3 sym4 sym3 Value |ONLINE| |OFFLINE| |OFFLINE| Veritas Cluster Server 5. Save but do not close the VCS configuration. – appsg depends on dbsg (online local firm) – websg depends on dbsg (online local firm) Solution a hagrp -link appsg dbsg online local firm b hagrp -link websg dbsg online local firm c hagrp -dep #Parent appsg websg d Child dbsg dbsg Relationship online local firm online local firm haconf -dump End of Solution 3 Use a single hagrp command with the propagate option to bring the dbsg.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Solution 156 B–12 a hagrp -online -propagate websg -sys sym3 VCS NOTICE V-16-1-40147 Attempting to online group(s) websg dbsg on system sym3. appsg.

All three service groups can be taken offline with one command. and websg service groups offline on sym3. All rights reserved. VCS NOTICE V-16-1-40147 Attempting to online group(s) appsg on system sym3. e hagrp -wait appsg State ONLINE -sys sym3 f hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE| End of Solution Copyright © 2012 Symantec Corporation. B–13 . Can all three service groups be brought offline using just one command? If not. 4 157 Use a single hagrp command to take the dbsg. b hagrp -wait dbsg State OFFLINE -sys sym3 Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. All rights reserved. The results are the same as hagrp -online appsg -sys sym3.appsg dbsg dbsg testappsg testappsg websg websg d State State State State State State State sym4 sym3 sym4 sym3 sym4 sym3 sym4 |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE| hagrp -online -propagate appsg -sys sym3 Note: The propagate option is not required nor is it invalid. Solution a hagrp -offline -propagate dbsg -sys sym3 VCS NOTICE V-16-1-40158 Attempting to offline group(s) dbsg websg appsg on system sym3. then ensure that all three service groups are brought offline on sym3. appsg.

VCS NOTICE V-16-1-40147 Attempting to online group(s) websg dbsg on system sym3. . 158 B–14 b hagrp -wait websg State ONLINE -sys sym3 c hagrp -online appsg -sys sym4 VCS WARNING V-16-1-10163 Group dependency is not met if group appsg goes online on system sym4 d hagrp -online appsg -sys sym3 e hagrp -wait appsg State ONLINE -sys sym3 f hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg Attribute State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| Veritas Cluster Server 5. Were you successful? If not successful. All rights reserved.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. The appsg service group cannot be brought online on sym4 due to service group dependencies.c hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| End of Solution 5 Using a single hagrp command with the propagate option. bring the dbsg and websg service groups online on sym3. then bring the appsg service group online on sym3. Attempt to bring the appsg service group online on sym4. All rights reserved. Solution a hagrp -online -propagate websg -sys sym3 Copyright © 2012 Symantec Corporation.

All rights reserved. Solution a rm /var/tmp/appip b hares -probe appip -sys sym3 c hagrp -wait appsg State "OFFLINE|FAULTED" -sys sym3 d hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |OFFLINE|FAULTED| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE| Copyright © 2012 Symantec Corporation. Neither the dbsg nor websg failover or change state. Do any service groups failover? Only appsg faults. All rights reserved. Solution a hares -clear appip -sys sym3 b hagrp -online appsg -sys sym3 c hagrp -wait appsg State ONLINE -sys sym3 Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation.testappsg testappsg websg websg State State State State sym3 sym4 sym3 sym4 |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE| End of Solution 6 Fault the appsg service group by removing the /var/tmp/appip file followed by a probe of the appip resource on sym3. End of Solution 159 7 Clear the appip resource fault and bring the appsg service group back online on sym3. B–15 .

d hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE| End of Solution 8 Fault the dbsg service group by removing the /var/tmp/dbip file followed by a probe of the dbip resource on sym3. Solution 160 B–16 a rm /var/tmp/dbip b hares -probe dbip -sys sym3 c hagrp -wait dbsg State 'OFFLINE|FAULTED' -sys sym3 d hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE|STOPPING| |OFFLINE| |OFFLINE|FAULTED| |OFFLINE| |OFFLINE| |OFFLINE| |ONLINE|STOPPING| |OFFLINE| e hagrp -wait appsg State ONLINE -sys sym4 f hagrp -state #Group ClusterService ClusterService appsg Attribute State State State System sym3 sym4 sym3 Value |ONLINE| |OFFLINE| |OFFLINE| Veritas Cluster Server 5. Copyright © 2012 Symantec Corporation. Do any service groups failover? The dbsg service group faults.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. The appsg and websg service groups are taken offline on sym3. . All rights reserved. All rights reserved. All three service groups failover to sym4.

appsg
dbsg
dbsg
testappsg
testappsg
websg
websg

State
State
State
State
State
State
State

sym4
sym3
sym4
sym3
sym4
sym3
sym4

|ONLINE|
|OFFLINE|FAULTED|
|ONLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|ONLINE|

End of Solution

9

Clear the dbip resource fault and take the dbsg, websg, appsg, and testappsg
service groups offline on any system they may be online.
Solution

a

hares -clear dbip -sys sym3

b

hagrp -offline -propagate dbsg -any
VCS NOTICE V-16-1-40173 Attempting to offline group(s) dbsg websg appsg on
system sym4.

c

hagrp -wait dbsg State OFFLINE -sys sym4

d

hagrp -state
#Group
ClusterService
ClusterService
appsg
appsg
dbsg
dbsg
testappsg
testappsg
websg
websg

Attribute
State
State
State
State
State
State
State
State
State
State

System
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4

Value
|ONLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|

Copyright © 2012 Symantec Corporation. All rights reserved.

End of Solution

161

10 Link the testappsg service group as a parent of the appsg service group with

an offline local dependency. Save, but do not close the VCS configuration.
Note: This will configure a preference for the appsg service group running on
a system over the testappsg service group and force the testappsg to
switch upon a successful failover of the appsg service group.
Solution

a

hagrp -link testappsg appsg offline local

Lab 1: Service group dependencies
Copyright © 2012 Symantec Corporation. All rights reserved.

B–17

b

hagrp -dep
#Parent
appsg
testappsg
websg
haconf -dump

c

Child
dbsg
appsg
dbsg

Relationship
online local firm
offline local
online local firm

haconf -dump

End of Solution

11 Bring the dgsg, appsg, and websg service groups online on sym3. Attempt to

bring the testappsg service group online on sym3. Were you successful? If
not, attempt to bring the testappsg service group online on sym4.
The testappsg service group cannot be brought online on the same system as the
appsg service group.
Solution

a

hagrp -online -propagate websg -sys sym3

Copyright © 2012 Symantec Corporation. All rights reserved.

VCS NOTICE V-16-1-40147 Attempting to online group(s) websg dbsg on system
sym3.

162 B–18

b

hagrp -wait websg State ONLINE -sys sym3

c

hagrp -online appsg -sys sym3

d

hagrp -wait appsg State ONLINE -sys sym3

e

hagrp -state
#Group
ClusterService
ClusterService
appsg
appsg
dbsg
dbsg
testappsg
testappsg
websg
websg

f

Attribute
State
State
State
State
State
State
State
State
State
State

System
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4

Value
|ONLINE|
|OFFLINE|
|ONLINE|
|OFFLINE|
|ONLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|ONLINE|
|OFFLINE|

hagrp -online testappsg -sys sym3
VCS WARNING V-16-1-10163 Group dependency is not met if group testappsg goes
online on system sym3

Veritas Cluster Server 5.1 for UNIX: Install and Configure
Copyright © 2012 Symantec Corporation. All rights reserved.

g

hagrp -online testappsg -sys sym4

h

hagrp -wait testappsg State ONLINE -sys sym4

i

hagrp -state
#Group
ClusterService
ClusterService
appsg
appsg
dbsg
dbsg
testappsg
testappsg
websg
websg

Attribute
State
State
State
State
State
State
State
State
State
State

System
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4

Value
|ONLINE|
|OFFLINE|
|ONLINE|
|OFFLINE|
|ONLINE|
|OFFLINE|
|OFFLINE|
|ONLINE|
|ONLINE|
|OFFLINE|

End of Solution

12 Fault the dbsg service group by removing the /var/tmp/dbip file followed

by a probe of the dbip resource on sym3. Do any service groups failover?
The dbsg service group faults. The appsg and websg service groups are taken offline
on sym3. The testappsg service group is switched from sym4 to sym3. The dbsg,
appsg, and websg service groups failover to sym4.

Copyright © 2012 Symantec Corporation. All rights reserved.

Solution

163

a

rm /var/tmp/dbip

b

hares -probe dbip -sys sym3

c

hagrp -wait dbsg State 'OFFLINE|FAULTED' -sys sym3

d

hagrp -state
#Group
ClusterService
ClusterService
appsg
appsg
dbsg
dbsg
testappsg
testappsg
websg
websg

Attribute
State
State
State
State
State
State
State
State
State
State

System
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4

Value
|ONLINE|
|OFFLINE|
|PARTIAL|STOPPING|
|OFFLINE|
|OFFLINE|FAULTED|
|OFFLINE|
|OFFLINE|
|ONLINE|
|PARTIAL|STOPPING|
|OFFLINE|

Note: Depending on your timing, appsg may show OFFLINE on both
systems.

Lab 1: Service group dependencies
Copyright © 2012 Symantec Corporation. All rights reserved.

B–19

e

hagrp -wait appsg State ONLINE -sys sym4

f

hagrp -state
#Group
ClusterService
ClusterService
appsg
appsg
dbsg
dbsg
testappsg
testappsg
websg
websg

Attribute
State
State
State
State
State
State
State
State
State
State

System
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4

Value
|ONLINE|
|OFFLINE|
|OFFLINE|
|ONLINE|
|OFFLINE|FAULTED|
|ONLINE|
|ONLINE|
|OFFLINE|
|OFFLINE|
|ONLINE|

End of Solution

13 Take the testappsg service group offline on sym3 and clear the dbip resource

fault. Then, use a single command to take the dbsg, websg, appsg, and
testappsg service groups offline on any system where they may be online.
Solution

a

hagrp -offline testappsg -sys sym3

b

hares -clear dbip -sys sym3

c

hagrp -offline -propagate dbsg -any

Copyright © 2012 Symantec Corporation. All rights reserved.

VCS NOTICE V-16-1-40173 Attempting to offline group(s) dbsg websg appsg on
system sym4.

164 B–20

d

hagrp -wait dbsg State OFFLINE -sys sym4

e

hagrp -state
#Group
ClusterService
ClusterService
appsg
appsg
dbsg
dbsg
testappsg
testappsg
websg
websg

Attribute
State
State
State
State
State
State
State
State
State
State

System
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4
sym3
sym4

Value
|ONLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|
|OFFLINE|

End of Solution

Veritas Cluster Server 5.1 for UNIX: Install and Configure
Copyright © 2012 Symantec Corporation. All rights reserved.

14 Unlink the service group dependencies between the testappsg and appsg

service groups and between the dbsg, websg and appsg service groups. Save,
but do not close the VCS configuration.
Solution

a

hagrp -unlink testappsg appsg

b

hagrp -unlink websg dbsg

c

hagrp -unlink appsg dbsg

d

hagrp -dep
VCS WARNING V-16-1-50035 No Group dependencies are configured

e

haconf -dump

Copyright © 2012 Symantec Corporation. All rights reserved.

End of Solution

165

Lab 1: Service group dependencies
Copyright © 2012 Symantec Corporation. All rights reserved.

B–21

All rights reserved. All rights reserved. . between the websg and appsg service groups and between the testappsg and appsg service groups as indicated below. 1 From sym3:terminal1. while not necessary. have been included to be consistent with other lab exercises. create dependencies between the appsg and dbsg service groups. Solution 166 B–22 a hagrp -link appsg dbsg online local firm b hagrp -link websg appsg online local firm c hagrp -link testappsg appsg offline local d hagrp -dep #Parent appsg testappsg websg e Child dbsg appsg appsg Relationship online local firm offline local online local firm haconf -dump End of Solution Veritas Cluster Server 5. – appsg depends on dbsg (online local firm) – websg depends on appsg (online local firm) – testappsg depends on appsg (offline local) Copyright © 2012 Symantec Corporation. you configure a typical service group dependency with a three level dependency causing one service group to have preference being online on startup and failover over another service group. The hagrp -wait commands.Exercise 4: Service group dependencies scenario 2 In this exercise.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Save but do not close the VCS configuration. sym3 Note: The service groups in this exercise will come online and go offline very quickly.

All rights reserved. Can all three service groups be brought online using just one command? If not. It could. The dbsg service group is brought online. Solution a hagrp -online testappsg -sys sym3 b hagrp -wait testappsg State ONLINE -sys sym3 c hagrp -online -propagate websg -sys sym3 Copyright © 2012 Symantec Corporation. Use a single hagrp command with the propagate option to bring the dbsg. g hagrp -wait websg State ONLINE -sys sym3 h hagrp -state #Group ClusterService ClusterService appsg appsg dbsg Attribute State State State State State System sym3 sym4 sym3 sym4 sym3 Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. 167 d hagrp -switch testappsg -to sym4 e hagrp -wait testappsg State ONLINE -sys sym4 f hagrp -online -propagate websg -sys sym3 VCS NOTICE V-16-1-40147 Attempting to online group(s) websg appsg dbsg on system sym3. All three service groups can be brought online using a single command.2 Bring the testappsg service group online on sym3. followed by the appsg service group and finally the websg service group. Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| B–23 . but it cannot just come online there with the testappsg already online. The testappsg is already online on sym3 through normal mechanisms so the appsg service group cannot come online there. under the proper circumstances. VCS WARNING V-16-1-40148 Cannot online group appsg on system sym3. then ensure that all three service groups are brought online on sym3. Were you successful? If not. fail over to sym3 preferentially. and websg service groups online on sym3. appsg. then switch the testappsg service group to sym4 and retry. All rights reserved.

dbsg testappsg testappsg websg websg State State State State State sym4 sym3 sym4 sym3 sym4 |OFFLINE| |OFFLINE| |ONLINE| |ONLINE| |OFFLINE| End of Solution 3 Using a single hagrp command with the propagate option. All rights reserved. Solution a hagrp -offline -propagate dbsg -sys sym3 Copyright © 2012 Symantec Corporation. bring the dbsg. 168 B–24 b hagrp -wait dbsg State OFFLINE -sys sym3 c hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| End of Solution 4 Using a single hagrp command with the propagate option. . and websg service groups offline on sym3. All three service groups can be taken offline with one command. Can all three service groups be brought offline using just one command? If not. then ensure that all three service groups are brought offline on sym3. take the dbsg. Veritas Cluster Server 5. The testappsg service group remains online. VCS NOTICE V-16-1-40158 Attempting to offline group(s) dbsg appsg websg on system sym3. appsg. appsg.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Solution a hagrp -online -propagate websg -sys sym3 VCS NOTICE V-16-1-40147 Attempting to online group(s) websg appsg dbsg on system sym3. All rights reserved. and websg service groups online on sym3.

The websg is taken offline. B–25 . No service groups fail over. Do any service groups failover? The appsg faults.b hagrp -wait websg State ONLINE -sys sym3 c hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |ONLINE| |OFFLINE| End of Solution 5 Fault the appsg service group by removing the /var/tmp/appip file followed by a probe of the appip resource on sym3. All rights reserved. All rights reserved. Solution 169 a rm /var/tmp/appip b hares -probe appip -sys sym3 c hagrp -wait appsg State "OFFLINE|FAULTED" -sys sym3 d hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |OFFLINE|FAULTED| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |PARTIAL|STOPPING| |OFFLINE| End of Solution Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. Solution Copyright © 2012 Symantec Corporation.

The Copyright © 2012 Symantec Corporation. Do any service groups failover? The dbsg service group faults. All rights reserved. and websg service groups failover to sym4.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. dbsg. All rights reserved. The appsg and websg service groups are brought offline on sym3. Solution a hares -clear appip -sys sym3 b hagrp -online -propagate websg -sys sym3 c hagrp -wait websg State ONLINE -sys sym3 d hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |ONLINE| |OFFLINE| End of Solution 7 Fault the dbsg service group by removing the /var/tmp/dbip file followed by a probe of the dbip resource on sym3. 170 B–26 Solution a rm /var/tmp/dbip b hares -probe dbip -sys sym3 c hagrp -wait dbsg State 'OFFLINE|FAULTED' -sys sym3 d hagrp -state #Group Attribute ClusterService State ClusterService State System sym3 sym4 Value |ONLINE| |OFFLINE| Veritas Cluster Server 5. The testappsg service group is switched from sym4 to sym3. .6 Clear the appip resource fault and use a single hagrp command with the propagate option to bring the appsg service group back online on sym3. appsg.

and testappsg service groups offline on any system they may be online.appsg appsg dbsg dbsg testappsg testappsg websg websg State State State State State State State State sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 |ONLINE|STOPPING| |OFFLINE| |OFFLINE|FAULTED| |OFFLINE| |OFFLINE| |ONLINE| |ONLINE| |OFFLINE| e hagrp -wait appsg State ONLINE -sys sym4 f hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE|FAULTED| |ONLINE| |PARTIAL|STARTING| |OFFLINE| |OFFLINE| |ONLINE| End of Solution 8 Take the testappsg service group offline on sym3 and clear the dbip resource fault. d hagrp -wait dbsg State OFFLINE -sys sym4 e hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg Attribute State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. Solution 171 a hagrp -offline testappsg -sys sym3 b hares -clear dbip -sys sym3 c hagrp -offline -propagate dbsg -any VCS NOTICE V-16-1-40173 Attempting to offline group(s) dbsg appsg on system sym4. Then. Value |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| B–27 . All rights reserved. All rights reserved. websg. Copyright © 2012 Symantec Corporation. use a single command to bring the dbsg. appsg.

websg websg State State sym3 sym4 |OFFLINE| |OFFLINE| End of Solution 9 Unlink the service group dependencies between the testappsg and appsg service groups. Solution a hagrp -unlink testappsg appsg b hagrp -unlink websg appsg c hagrp -unlink appsg dbsg d hagrp -dep VCS WARNING V-16-1-50035 No Group dependencies are configured e haconf -dump Copyright © 2012 Symantec Corporation. End of Solution 172 B–28 Veritas Cluster Server 5. .1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Save. All rights reserved. but do not close the VCS configuration. between the dbsg and appsg service groups and between the websg and appsg service groups. All rights reserved.

– websg depends on appsg (online local firm) – websg depends on dbsg (online local firm) – testappsg depends on appsg (offline local) Copyright © 2012 Symantec Corporation. have been included to be consistent with other lab exercises. while not necessary. create dependencies between the websg and appsg service groups and websg and dbsg service groups as indicated below. you configure a typical multi-child service group dependency so that one service group has two child service group dependencies causing a service group to have preference being online on startup and failover. All rights reserved. The hagrp -wait commands. sym3 Note: The service groups in this exercise will come online and go offline very quickly. 1 From sym3:terminal1. Solution 173 a hagrp -link websg appsg online local firm b hagrp -link websg dbsg online local firm c hagrp -link testappsg appsg offline local d hagrp -dep #Parent testappsg websg websg e Child appsg appsg dbsg Relationship offline local online local firm online local firm haconf -dump End of Solution Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation.Exercise 5: Service group dependencies scenario 3 In this exercise. All rights reserved. Save but do not close the VCS configuration. B–29 .

Were you able to bring the websg. dbsg. All rights reserved. Can all three service groups be brought offline using just one command? If not. appsg. Veritas Cluster Server 5. take the websg. and appsg and service groups offline on sym3. and websg service groups online on sym3. Using a single hagrp command with the propagate option.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. The appsg service group needs to be taken offline explicitly in this case. d hagrp -wait websg State ONLINE -sys sym3 e hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |ONLINE| |OFFLINE| Copyright © 2012 Symantec Corporation. Solution a hagrp -online testappsg -sys sym4 b hagrp -wait testappsg State ONLINE -sys sym4 c hagrp -online -propagate websg -sys sym3 VCS NOTICE V-16-1-40147 Attempting to online group(s) websg appsg dbsg on system sym3. End of Solution 174 B–30 3 Using a single hagrp command with the propagate option. All rights reserved. and appsg service groups online with the online propagate option? Yes. the online propagate option worked as expected.2 Bring the testappsg service group online on sym4. dbsg. then ensure that all three service groups are brought offline on sym3. bring the dbsg. all three service groups cannot be taken offline with one command. No. .

B–31 . End of Solution 175 4 Using a single hagrp command with the propagate option. Solution a hagrp -online -propagate websg -sys sym3 VCS NOTICE V-16-1-40147 Attempting to online group(s) websg appsg dbsg on system sym3. All rights reserved.Solution a hagrp -offline -propagate dbsg -sys sym3 VCS NOTICE V-16-1-40158 Attempting to offline group(s) dbsg websg on system sym3. and websg service groups online on sym3. bring the dbsg. appsg. Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. All rights reserved. b hagrp -wait dbsg State OFFLINE -sys sym3 c hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| d hagrp -offline appsg -sys sym3 e hagrp -wait appsg State OFFLINE -sys sym3 f hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| Copyright © 2012 Symantec Corporation.

Copyright © 2012 Symantec Corporation. All rights reserved. No service groups change state or fail over. Do any service groups failover? The websg faults. Solution 176 B–32 a rm /var/tmp/webvip b hares -probe webvip -sys sym3 c hagrp -wait websg State "OFFLINE|FAULTED" -sys sym3 d hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE|FAULTED| |OFFLINE| End of Solution Veritas Cluster Server 5. All rights reserved.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.b hagrp -wait websg State ONLINE -sys sym3 c hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |ONLINE| |OFFLINE| End of Solution 5 Fault the websg service group by removing the /var/tmp/webvip file followed by a probe of the webvip resource on sym3. .

All rights reserved. The appsg service group is unaffected and no failover occurs. The testappsg Copyright © 2012 Symantec Corporation. 177 Solution a rm /var/tmp/dbip b hares -probe dbip -sys sym3 c hagrp -wait dbsg State 'OFFLINE|FAULTED' -sys sym3 d hagrp -state #Group Attribute ClusterService State ClusterService State System sym3 sym4 Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. All rights reserved.6 Clear the webvip resource fault and bring the websg service group back online on sym3. The websg service group is taken offline on sym3. Do any service groups failover? The dbsg service group faults on sym3. service group remains online on sym4. Solution a hares -clear webvip -sys sym3 b hagrp -online websg -sys sym3 c hagrp -wait websg State ONLINE -sys sym3 d hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |ONLINE| |OFFLINE| End of Solution 7 Fault the dbsg service group by removing the /var/tmp/dbip file followed by a probe of the dbip resource on sym3. Value |ONLINE| |OFFLINE| B–33 .

Then.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Account for the testappsg service group. VCS NOTICE V-16-1-40147 Attempting to online group(s) websg appsg on system sym4.appsg appsg dbsg dbsg testappsg testappsg websg websg State State State State State State State State sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 |ONLINE| |OFFLINE| |OFFLINE|FAULTED| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |OFFLINE| End of Solution 8 Take the appsg service group offline on sym3. Solution a hagrp -offline appsg -sys sym3 b hagrp -wait appsg State OFFLINE -sys sym3 c hagrp -switch testappsg -to sym3 d hagrp -wait testappsg State OFFLINE -sys sym3 e hagrp -online -propagate websg -sys sym4 Copyright © 2012 Symantec Corporation. and dbsg service groups online on sym4. 178 B–34 f hagrp -wait websg State ONLINE -sys sym4 g hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE|FAULTED| |ONLINE| |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| End of Solution Veritas Cluster Server 5. All rights reserved. appsg. All rights reserved. bring the websg. .

All rights reserved. B–35 . All rights reserved. and between the websg and appsg service groups. VCS WARNING V-16-1-50035 No Group dependencies are configured 179 e haconf -dump -makero End of Solution Lab 1: Service group dependencies Copyright © 2012 Symantec Corporation. Save and close the VCS configuration. Solution a hagrp -unlink testappsg appsg b hagrp -unlink websg appsg c hagrp -unlink websg dbsg d hagrp -dep Copyright © 2012 Symantec Corporation. Solution a hares -clear dbip -sys sym3 b hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |ONLINE| |OFFLINE| |OFFLINE| |ONLINE| End of Solution 10 Unlink the service group dependencies between the testappsg and appsg service groups. between the dbsg and appsg service groups.9 Clear the dbip resource fault.

terminate the hastatus command. All rights reserved. End of lab 180 B–36 Veritas Cluster Server 5. Solution From sym3:terminal2.11 From sym3:terminal2. All rights reserved. . press Ctrl-C. End of Solution Copyright © 2012 Symantec Corporation.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.

Exercise 2: Merge cluster preparation Two clusters are prepared for merging. Copyright © 2012 Symantec Corporation. All rights reserved.Lab 2: Merging clusters In this lab. All rights reserved. Exercise 3: Merging cluster infrastructure The systems from one cluster are added to another cluster. This lab contains the following exercises: Exercise 1: Checking lab prerequisites A verification that the virtual machines needed for this lab are powered on and functioning is performed. Exercise 5: Merged cluster verification The merged cluster is verified. Lab 2: Merging clusters B–37 Copyright © 2012 Symantec Corporation. 181 Exercise 4: Adding service groups and resources The service groups and resources from one of the original are added to the merged cluster. . you will merge the east cluster to the west cluster forming one four-node west cluster.

Exercise 1: Checking lab prerequisites In this exercise. – sym2 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. that you are logged in using the proper account and that any needed terminal windows are opened. All rights reserved. that you are logged using the indicated account and that the indicated terminal windows are opened. For example: sym1:terminal1. you verify that the virtual machines needed for this lab are powered on and functioning. and sym2:terminal2. – sym3 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. – sym1 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. Copyright © 2012 Symantec Corporation. – mgt › There is no need to log into this virtual machine at this time. Note: The terminal windows are referred to as hostname:terminal# throughout the labs. It is not necessary to label the terminal windows and you may decide which is terminal1 and which is terminal2. Veritas Cluster Server 5. 1 182 B–38 Verify that the following virtual machines shown are powered on.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. sym1:terminal2. All rights reserved. . – sym4 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. sym2:terminal1.

All rights reserved. 183 Lab 2: Merging clusters B–39 Copyright © 2012 Symantec Corporation. . Copyright © 2012 Symantec Corporation. this will require you to power on and log into sym1 and sym2. All rights reserved.2 If you have machines running that are not used in this lab. Note: If you are completing the lab exercises in order. shut down the operating system and power the machines off.

... Done VCS installation on sym1 ... Veritas Cluster Server 5......0. Cluster information verification: 184 B–40 Cluster Name: west Cluster ID Number: 5 Systems: sym1 sym2 Would you like to configure I/O fencing on the cluster? [y... .. – Reconfigure fencing in disabled mode... sym1 Note: In this lab there are no iSCSI LUNs that are visible to all four systems.. you prepare two clusters for merging. release compatibility on sym1 ......000 communication on sym2 ... – Do not view the summary file..... Solution a cd /opt/VRTS/install b ....... All rights reserved./installsfha -fencing Checking communication on sym1 Checking release compatibility on sym1 Checking VCS installation on sym1 Copyright © 2012 Symantec Corporation.....n..... Version 6...........000.................q] c y Checking Done Checking Checking Checking communication on sym1 . I/O fencing is re-configured to disabled mode on both clusters................. for lab purposes. so merging enabled I/O fencing using disks cannot be part of the cluster merge lab..... 1 From sym1:terminal1.... – Stop VCS and apply the fencing changes. Therefore.... navigate to the /opt/VRTS/install directory and run the installsfha script with the fencing option using the following information.......... All rights reserved......Exercise 2: Merge cluster preparation In this exercise..1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.......

. Done Stopping Fencing on sym2 ............................................ Are you ready to stop VCS and apply fencing configuration on all nodes at this time? [y..0.......................... installsfha log files..........q] (y) d y Fencing configuration 1) Configure Coordination Point client based fencing 2) Configure disk based fencing 3) Configure fencing in disabled mode 4) Online fencing migration Select the fencing mechanism to be configured in this Application Cluster: e 3 Installer will stop VCS before applying fencing configuration............................b] (y) f y Deleting Coordination Point Agent Service Group westfensg . Version 6............. All rights reserved..........................................n.... All rights reserved.cf without fencing ........ summary file............. Done Checking VCS installation on sym2 .....................n...... I/O Fencing configuration ............ Done Starting VCS on sym1 ........................ and response file are saved at: /opt/VRTS/install/logs/installsfha-201112081226AJb Would you like to view the summary file? [y............................q] (n) g n End of Solution Lab 2: Merging clusters B–41 Copyright © 2012 Symantec Corporation..000 Fencing is already started in enabled mode....000...... unfreeze any frozen service group and unmount the mounted file systems in the cluster.......................... Done Starting VCS on sym2 ....................................... Done Stopping VCS on sym1 .........n....... Done Stopping VCS on sym2 .... To make sure VCS shuts down successfully............... Done Configuring fencing in disabled mode on sym2 .......Done Checking release compatibility on sym2 ... 185 Done I/O Fencing configuration completed successfully .. ... Done Copyright © 2012 Symantec Corporation..... do you want to reconfigure it? [y..q.................... Done Updating main. Done Stopping Fencing on sym1 .. Done Configuring fencing in disabled mode on sym1 ..........................

– Stop VCS and apply the fencing changes. navigate to the /opt/VRTS/install directory and run the installsfha script with the fencing option using the following information. Solution a gabconfig -a GAB Port Memberships =============================================================== Port a gen 1b5701 membership 01 Port b gen 1b5707 membership 01 Port h gen 1b570a membership 01 b service vxfen status running c vxfenadm -d I/O Fencing Cluster Information: ================================ Fencing Protocol Version: 201 Fencing Mode: Disabled Cluster Members: * 0 (sym1) 1 (sym2) RFSM State Information: node 0 in state 8 (running) node 1 in state 8 (running) End of Solution sym3 Copyright © 2012 Symantec Corporation. – Do not view the summary file. All rights reserved. Solution a cd /opt/VRTS/install Veritas Cluster Server 5. . – Reconfigure fencing in disabled mode.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.2 Use the gabconfig and service vxfen status commands to confirm that I/O fencing is configured. Use the vxfenadm command to confirm that I/O fencing is running in disabled mode. All rights reserved. 3 186 B–42 From sym3:terminal1.

................. Version 6..0................ Stopping VCS on sym4 ..........000..0. Starting VCS on sym4 .......cf without fencing ................ Done Done Done Done Done Done Done Done Done I/O Fencing configuration ................q] c y Checking Done Checking Checking Checking Done Checking Checking communication on sym3 .......................... unfreeze any frozen service group and unmount the mounted file systems in the cluster.n....... To make sure VCS shuts down successfully....................................... release compatibility on sym4 ......... Configuring fencing in disabled mode on sym4 .......................b] (y) f y Stopping VCS on sym3 ........... Version 6........000 Fencing is already started in enabled mode...... Updating main..............n........................... ........... e 187 3 Installer will stop VCS before applying fencing configuration..../installsfha -fencing Checking communication on sym3 Checking release compatibility on sym3 Checking VCS installation on sym3 Cluster information verification: Cluster Name: east Cluster ID Number: 777 Systems: sym3 sym4 Would you like to configure I/O fencing on the cluster? [y......... Starting VCS on sym3 ..................... Stopping Fencing on sym3 ........ Configuring fencing in disabled mode on sym3 ......... All rights reserved..............000 communication on sym4 ..........................000....... Done VCS installation on sym4 ....... release compatibility on sym3 ........................................... Stopping Fencing on sym4 ................................................... do you want to reconfigure it? [y................ All rights reserved.............................q.. Done Lab 2: Merging clusters B–43 Copyright © 2012 Symantec Corporation...q] (y) d y Fencing configuration 1) Configure Coordination Point client based fencing 2) Configure disk based fencing 3) Configure fencing in disabled mode 4) Online fencing migration Select the fencing mechanism to be configured in this Application Cluster: Copyright © 2012 Symantec Corporation... Done VCS installation on sym3 ................................. Are you ready to stop VCS and apply fencing configuration on all nodes at this time? [y........b ..n...

q] (n) g n End of Solution 4 Use the gabconfig and service vxfen status commands to confirm that I/O fencing is configured... Use the vxfenadm command to confirm that I/O fencing is running in disabled mode. The appsg service group in the west cluster would have precedence so the appsg service group in the east cluster must be renamed or. All rights reserved. /opt/VRTS/install/logs/installsfha-201112081226Zat Would you like to view the summary file? [y. deleted from the configuration. Solution a gabconfig -a GAB Port Memberships =============================================================== Port a gen 1b5701 membership 01 Port b gen 1b5707 membership 01 Port h gen 1b570a membership 01 b service vxfen status running Copyright © 2012 Symantec Corporation. there is a conflicting duplicate named appsg service group in both the west and east clusters. All rights reserved. Veritas Cluster Server 5. . as performed in this lab.I/O Fencing configuration completed successfully .n. c 188 B–44 vxfenadm -d I/O Fencing Cluster Information: ================================ Fencing Protocol Version: 201 Fencing Mode: Disabled Cluster Members: * 0 (sym3) 1 (sym4) RFSM State Information: node 0 in state 8 (running) node 1 in state 8 (running) End of Solution Note: In this lab.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. This would cause errors during a merge.

. All rights reserved. All rights reserved. Solution a hagrp -state #Group ClusterService ClusterService appsg appsg dbsg dbsg testappsg testappsg websg websg b Attribute State State State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| hagrp -dep VCS WARNING V-16-1-50035 No Group dependencies are configured c hagrp -offline appsg -any Attempting to offline group on system sym3 d hagrp -wait appsg State OFFLINE -sys sym3 e hagrp -state appsg #Group appsg appsg Copyright © 2012 Symantec Corporation. f 189 Attribute State State System sym3 sym4 Value |OFFLINE| |OFFLINE| hagrp -resources appsg appdg appmnt appnic appproc appip appvo g hares -dep | grep "^appsg" appsg appsg appsg appsg appsg appmnt appproc appproc appip appvol appvol appip appmnt appnic appdg End of Solution Lab 2: Merging clusters B–45 Copyright © 2012 Symantec Corporation.5 Take the appsg service group offline and list its resources and dependencies.

All rights reserved.6 Open the VCS configuration for update and delete each resource in the appsg service group in resource dependency order. k 190 B–46 Attribute State State State State State State State State System sym3 sym4 sym3 sym4 sym3 sym4 sym3 sym4 Value |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| |ONLINE| |OFFLINE| haconf -dump -makero End of Solution 7 Navigate to the /etc/VRTSvcs/conf/config directory and use the hacf -cftocmd command to create a main.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Solution a cd /etc/VRTSvcs/conf/config b hacf -cftocmd . Veritas Cluster Server 5. All rights reserved.cmd file. Solution a haconf -makerw b hares -delete appproc c hares -delete appmnt d hares -delete appvol e hares -delete appdg f hares -delete appip g hares -delete appnic h hagrp -resources appsg i hagrp -delete appsg j hagrp -state #Group ClusterService ClusterService dbsg dbsg testappsg testappsg websg websg Copyright © 2012 Symantec Corporation.cmd. Copy the main. Then. delete the appsg service group and save and close the VCS configuration.cmd file to eastmain. .

cmd file to /etc/VRTSvcs/conf/config/eastmain.cf" hares -add dbdg FileOnOff dbsg hares -modify dbdg PathName "/var/tmp/dbdg" hares -modify dbdg Enabled 1 hares -add dbip FileOnOff dbsg hares -modify dbip PathName "/var/tmp/dbip" hares -modify dbip Enabled 1 hares -add dblistener FileOnOff dbsg hares -modify dblistener PathName "/var/tmp/ dblistener" hares -modify dblistener Enabled 1 hares -add dbmnt FileOnOff dbsg hares -modify dbmnt PathName "/var/tmp/dbmnt" hares -modify dbmnt Enabled 1 hares -add dbnic FileOnOff dbsg hares -modify dbnic PathName "/var/tmp/dbnic" hares -modify dbnic Enabled 1 hares -add dboracle FileOnOff dbsg hares -modify dboracle PathName "/var/tmp/ dboracle" hares -modify dboracle Enabled 1 hares -add dbvol FileOnOff dbsg Lab 2: Merging clusters B–47 Copyright © 2012 Symantec Corporation. copy the /student/labs/vcs/vcs60/maincf/CM/eastmain. 191 After you have made the edits the contents of the file should be: hagrp -add dbsg hagrp -modify dbsg SystemList sym3 0 sym4 1 hagrp -modify dbsg AutoStartList sym3 sym4 hagrp -modify dbsg SourceFile ".cmd eastmain. All rights reserved. testappsg.cmd d ls *. and their resource dependencies. All rights reserved. .cmd main. Note: Alternatively. Copyright © 2012 Symantec Corporation.cmd file to remove all commands other than those related to the websg.cmd.c cp -p main./main.cmd End of Solution 8 Edit the eastmain. their resources. dbsg service groups.cmd eastmain.

cf" hares -add testappdg FileOnOff testappsg hares -modify testappdg PathName "/var/tmp/ testappdg" hares -modify testappdg Enabled 1 hares -add testappmnt FileOnOff testappsg hares -modify testappmnt PathName "/var/tmp/ testappmnt" hares -modify testappmnt Enabled 1 hares -add testappnic FileOnOff testappsg hares -modify testappnic PathName "/var/tmp/ testappnic" hares -modify testappnic Enabled 1 hares -add testappproc FileOnOff testappsg hares -modify testappproc PathName "/var/tmp/ testappproc" hares -modify testappproc Enabled 1 hares -add testappip FileOnOff testappsg hares -modify testappip PathName "/var/tmp/ testappip" hares -modify testappip Enabled 1 hares -add testappvol FileOnOff testappsg hares -modify testappvol PathName "/var/tmp/ testappvol" hares -modify testappvol Enabled 1 hagrp -add websg hagrp -modify websg SystemList sym3 0 sym4 1 hagrp -modify websg AutoStartList sym3 sym4 hagrp -modify websg Operators oper hagrp -modify websg SourceFile ". All rights reserved./main.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. 192 B–48 hares -modify dbvol PathName "/var/tmp/dbvol" hares -modify dbvol Enabled 1 hagrp -add testappsg hagrp -modify testappsg SystemList sym3 0 sym4 1 hagrp -modify testappsg AutoStartList sym3 sym4 hagrp -modify testappsg Operators oper hagrp -modify testappsg SourceFile "./main. All rights reserved. .cf" hares -add webapache FileOnOff websg hares -modify webapache PathName "/var/tmp/ webapache" hares -modify webapache Enabled 1 Veritas Cluster Server 5.Copyright © 2012 Symantec Corporation.

cmd b Remove the appropriate lines. 193 hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares hares -add webdg FileOnOff websg -modify webdg PathName "/var/tmp/webdg" -modify webdg Enabled 1 -add webmnt FileOnOff websg -modify webmnt PathName "/var/tmp/webmnt" -modify webmnt Enabled 1 -add webnic FileOnOff websg -modify webnic PathName "/var/tmp/webnic" -modify webnic Enabled 1 -add webvip FileOnOff websg -modify webvip PathName "/var/tmp/webvip" -modify webvip Enabled 1 -add webvol FileOnOff websg -modify webvol PathName "/var/tmp/webvol" -modify webvol Enabled 1 -link dbip dbnic -link dblistener dbip -link dblistener dboracle -link dbmnt dbvol -link dboracle dbmnt -link dbvol dbdg -link testappmnt testappvol -link testappproc testappmnt -link testappproc testappip -link testappip testappnic -link testappvol testappdg -link webapache webmnt -link webapache webvip -link webmnt webvol -link webvip webnic -link webvol webdg Solution a vi eastmain.Copyright © 2012 Symantec Corporation. All rights reserved. Lab 2: Merging clusters B–49 Copyright © 2012 Symantec Corporation. . All rights reserved.

1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. IO fencing. Solution a hastop -all b gabconfig -a GAB Port Memberships =============================================================== Port a gen a9e001 membership 01 Port b gen a9e007 membership 01 c service vxfen stop Stopping vxfen.. All rights reserved. Done d ssh sym4 service vxfen stop Stopping vxfen. g 194 B–50 service llt stop Stopping LLT: h ssh sym4 service llt stop Stopping LLT: i gabconfig -a GAB gabconfig ERROR V-15-2-25022 unknown error j ssh sym4 gabconfig -a GAB gabconfig ERROR V-15-2-25022 unknown error Veritas Cluster Server 5. ...c From the vi editor in command mode. GAB. Stopping vxfen. Stopping vxfen. All rights reserved. Done e service gab stop Stopping GAB: f ssh sym4 service gab stop Stopping GAB: Copyright © 2012 Symantec Corporation.. and LLT on both nodes of the east cluster. type: :wq End of Solution 9 Shutdown VCS.

All rights reserved. the main.cf.east b ls -l main.k lltstat -nvv configured LLT lltstat ERROR V-14-2-15000 open /dev/llt failed: No such file or directory l ssh sym4 lltstat -nvv configured LLT lltstat ERROR V-14-2-15000 open /dev/llt failed: No such file or directory End of Solution 10 Rename the /etc/VRTSvcs/conf/config/main. .east d ssh sym4 ls -l /etc/VRTSvcs/conf/config/main. Solution a mv main.cf.cf main. Note: In order for the merge utility to work correctly.cf ls: main.cf main.east on sym3 and sym4.cf. All rights reserved.cf file to main.cf files on the east cluster nodes must not exist.cf No such file or directory c ssh sym4 mv /etc/VRTSvcs/conf/config/main. End of Solution 195 Lab 2: Merging clusters B–51 Copyright © 2012 Symantec Corporation.cf: No such file or directory Copyright © 2012 Symantec Corporation.cf /etc/VRTSvcs/conf/config/main.

Use eth0 as the public NIC used for the cluster virtual IP. Optionally. you add the systems from one cluster to another cluster. navigate to the /opt/VRTS/install directory and run the . Record the log file located in the /opt/VRTS/install/logs directory. – – – – – Enter sym1 as the name of one node of the west cluster.Exercise 3: Merging cluster infrastructure In this exercise. Use eth4 and eth5 as the private links and eth0 as the low priority link. Copyright © 2012 Symantec Corporation. review the log file. – Do not view the summary file. Enter sym3 and sym4 as the systems to be added to the west cluster. . All rights reserved. Log file: The log file will be in the form of installsfha-yyyymmddhhmmxxx Solution a cd /opt/VRTS/install b . Following are the prerequisites to add a node to the cluster: 196 B–52 * The cluster to which you want to add the node must have all required SFHA rpms installed * New node must have all required SFHA rpms installed * SFHA must be running on the cluster to which you want to add a node * There should be no prior running SFHA processes on the new node * New node must have the same SFHA version as that of the existing cluster nodes Refer to the SFHA Installation Guide for more details Press [Enter] to continue: Veritas Cluster Server 5. sym1 1 From sym1:terminal1.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. All rights reserved./installsfha -addnode command taking note of the merge pre-requisites and using the following information./installsfha -addnode Logs are being written to /var/tmp/installsfha-201112081249IHO while installsfha is in progress.

...................................... Done communication on sym4 ... Done Checking VCS running state on sym1 .... SFHA 6............ To connect to the existing node(s) properly...n......... release compatibility on sym4 ..................0...... Done Checking release compatibility on sym1 ............... Enter one node of the SFHA cluster to which you would like to add one or more new nodes: d sym1 Checking communication on sym1 ......... SFHA 6....... Discovering NICs on sym3 .............. Discovered eth0 eth1 eth2 eth3 eth4 eth5 Enter the NIC for the first private heartbeat link on sym3: [q.000 packages on sym3 .q] (y) e y Checking communication on sym2 ....... All rights reserved............ SFHA 6.................................... Done product on sym4 ................................ Done Checking VCS running state on sym2 ........0......... Done Following cluster information detected: Cluster Name: west Cluster ID: 5 Systems: sym1 sym2 Is this information correct? [y......q..............?] (eth4) h eth4 Enter the NIC for the second private heartbeat link on sym3: [b.......n.............................................000........... each new node is required to be configured with 2 private and 1 low-priority heartbeat links.............. release compatibility on sym3 ..... .....0.q] (y) Copyright © 2012 Symantec Corporation................000.... Done Enter the system names separated by spaces to add to the cluster: f sym3 sym4 Checking Done Checking Checking Done Checking communication on sym3 ...........?] (eth5) Lab 2: Merging clusters B–53 Copyright © 2012 Symantec Corporation. Done Each node to be added to the cluster should have the same LLT heartbeat configuration as the existing node(s)...............000 packages on sym4 ....... Done Do you want to add the system(s) sym3 sym4 to the cluster west? [y..c Press Enter. g 197 y Checking Checking Checking Checking Checking installed installed installed installed installed product on cluster west ...000 product on sym3 ..... All rights reserved...........000.........

..... All rights reserved.......................n..... ..................................... ..q..............................n. vxfen on sym4 ........q] (y) l y Cluster Virtual IP is configured on the cluster west A public NIC device is required by following services on each of the newly added nodes: Cluster Virtual IP Active NIC devices discovered on sym3: eth0 eth1 eth2 eth3 eth4 eth0 Copyright © 2012 Symantec Corporation............... All rights reserved................. webip resource ..............q] (y) n y Starting llt Starting Starting Starting Done Checking Updating Updating Starting Starting on sym3 ....... seed Done Done Done Done Veritas Cluster Server 5. ........................................................ Done gab on sym4 .................. Enter the NIC for the VCS to use on sym3: (eth0) 198 B–54 m eth0 Is eth0 the public NIC used by other new nodes? [y........ ..q..... Checking GAB control port csgnic resource ...........i eth5 Enter the NIC for the low-priority heartbeat link on sym3: [b......... Done llt on sym4 ...........................................................?] k y Checking Checking Checking Checking Checking Checking media media media media media media speed speed speed speed speed speed Private Heartbeat NICs link1=eth4 link2=eth5 Low-Priority Heartbeat link-lowpri1=eth0 Private Heartbeat NICs link1=eth4 link2=eth5 Low-Priority Heartbeat link-lowpri1=eth0 for for for for for for eth4 eth5 eth4 eth5 eth4 eth5 on on on on on on sym3 sym3 sym4 sym4 sym1 sym1 .........1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation......... GAB control port seed ........ Done gab on sym3 .......b...................................?] (eth0) j eth0 Are you using the same NICs for private heartbeat links on all systems? [y... 1000Mb/s 1000Mb/s 1000Mb/s 1000Mb/s 1000Mb/s 1000Mb/s for sym3: NIC for sym3: for sym4: NIC for sym4: Is this information correct? [y.n... ........ vxfen on sym3 ......................................................... ......................................................

.................. .Group System B B B B B B B B B B sym1 sym2 sym3 sym4 sym1 sym2 sym1 sym2 sym1 sym2 ClusterService ClusterService ClusterService ClusterService appsg appsg nfssg nfssg orasg orasg Probed Y Y Y Y Y Y Y Y Y AutoDisabled N N N N N N N N N Y N State ONLINE OFFLINE OFFLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE Copyright © 2012 Symantec Corporation....SYSTEM STATE -...... All rights reserved.......... summary file............ ....System State Frozen A A A A RUNNING RUNNING RUNNING RUNNING 0 0 0 0 sym1 sym2 sym3 sym4 -....................................... Done Done Done Done Addnode completed successfully installsfha log files.................. ........ Solution hastatus -sum -.............. ................ All rights reserved..Starting Starting Starting Starting amf had amf had on on on on sym3 sym3 sym4 sym4 ....................... Solution gabconfig -a GAB Port Memberships =============================================================== Port a gen 1b5702 membership 0123 Port b gen 1b5709 membership 0123 Port h gen 1b570c membership 0123 End of Solution Lab 2: Merging clusters B–55 Copyright © 2012 Symantec Corporation.........GROUP STATE -... End of Solution 199 3 Use the gabconfig command to check GAB status. and response file are saved at: /opt/VRTS/install/logs/installsfha-201112081249IHO End of Solution 2 Perform a summary status of the cluster noting that none of the former east cluster service groups have been added.....

1 sym2 200 B–56 Link Status Address eth4 eth5 eth0 UP UP UP 00:0C:29:5A:B1:16 00:0C:29:5A:B1:20 00:0C:29:5A:B1:EE eth4 eth5 eth0 UP UP UP 00:0C:29:2D:77:9A 00:0C:29:2D:77:A4 00:0C:29:2D:77:72 eth4 eth5 eth0 UP UP UP 00:0C:29:97:FB:5D 00:0C:29:97:FB:67 00:0C:29:97:FB:35 eth4 eth5 eth0 UP UP UP 00:0C:29:C4:1D:0A 00:0C:29:C4:1D:14 00:0C:29:C4:1D:E2 OPEN 2 sym3 OPEN 3 sym4 b State OPEN OPEN lltstat -nvv active LLT node information: Node * 0 sym1 State OPEN Link eth4 eth5 Status UP UP Address 00:0C:29:5A:B1:16 00:0C:29:5A:B1:20 Veritas Cluster Server 5.4 Use the vxfenadm command to check I/O fencing. Solution vxfenadm -d I/O Fencing Cluster Information: ================================ Fencing Protocol Version: 201 Fencing Mode: Disabled Cluster Members: * 0 1 2 3 (sym1) (sym2) (sym3) (sym4) RFSM State Information: node 0 in state 8 (running) node 1 in state 8 (running) node 2 in state 8 (running) node 3 in state 8 (running) End of Solution 5 Use the lltstat command to check the LLT configured and active status. . All rights reserved. All rights reserved. Optionally. Solution a lltstat -nvv configured LLT node information: Node * 0 sym1 Copyright © 2012 Symantec Corporation. performed this step on all cluster nodes.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.

ether . The SystemList and AutoStartList service group attributes for the ClusterService service group configure all four cluster systems. /etc/llthosts. – – – – The cluster name is west.cf file noticing the following elements. Optionally. nfssg.51. . dbsg.1 sym2 eth0 UP 00:0C:29:5A:B1:EE eth4 eth5 eth0 UP UP UP 00:0C:29:2D:77:9A 00:0C:29:2D:77:A4 00:0C:29:2D:77:72 eth4 eth5 eth0 UP UP UP 00:0C:29:97:FB:5D 00:0C:29:97:FB:67 00:0C:29:97:FB:35 eth4 eth5 eth0 UP UP UP 00:0C:29:C4:1D:0A 00:0C:29:C4:1D:14 00:0C:29:C4:1D:E2 OPEN 2 sym3 OPEN 3 sym4 OPEN End of Solution 6 Display the contents of the /etc/llttab.link-lowpri eth0 eth-00:0c:29:97:fb:35 . All rights reserved. Lab 2: Merging clusters B–57 Copyright © 2012 Symantec Corporation. The cluster virtual ip is 10.- c cat /etc/gabtab /sbin/gabconfig -c -n4 Copyright © 2012 Symantec Corporation. – The appsg.2. perform this step on all cluster nodes.link eth5 eth-00:0c:29:97:fb:67 . and orasg service groups from the original west cluster are configured and remain restricted to sym1 and sym2. All four systems are defined as cluster members. All rights reserved. \ Solution a cat /etc/llthosts 0 1 2 3 b sym1 sym2 sym3 sym4 cat /etc/llttab set-node sym3 set-cluster 5 link eth4 eth-00:0c:29:97:fb:5d .ether . and testappsg from the east cluster are not configured.ether . and /etc/gabtab files. – The websg. End of Solution 201 7 Display the /etc/VRTSvcs/conf/config/main.10.

.cf ..cf file though the ClusterService service group definition is shown.cf" "SybaseTypes.0" ) NIC csgnic ( Device = eth0 ) NotifierMngr notifier ( SmtpServer = "mgt.255. sym2. more /etc/VRTSvcs/conf/config/main.example. group ClusterService ( SystemList = { sym1 = 0. sym3. include include include include include "OracleASMTypes.. All rights reserved.com" SmtpServerVrfyOff = 1 SmtpRecipients = { student = Warning } ) notifier requires csgnic webip requires csgnic .cf" "Db2udbTypes.51" Administrators = { admin } ) system sym1 ( ) system sym2 ( ) system sym3 ( ) system sym4 ( ) Copyright © 2012 Symantec Corporation.255. sym4 } OnlineRetryLimit = 3 OnlineRetryInterval = 120 ) 202 B–58 IP webip ( Device = eth0 Address = "10..cf" "OracleTypes.cf" "types.2. End of Solution Veritas Cluster Server 5. All rights reserved. sym3 = 2.2. .1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.cf" cluster west ( UserNames = { admin = bQRjQLqNRmRRpZRlQO } ClusterAddress = "10. sym2 = 1. sym4 = 3 } AutoStartList = { sym1.10.10.51" NetMask = "255.Solution Note: Only the main.

All rights reserved. Note: The oper user add is not part of the eastmain.cmd + hagrp -add dbsg VCS NOTICE V-16-1-10136 Group added. you add the service groups and resources from one of the original clusters to the merged cluster.cf + hares -add dbdg FileOnOff dbsg VCS NOTICE V-16-1-10242 Resource added./main. Enabled attribute must be set before agent monitors + hares -modify dbdg PathName /var/tmp/dbdg + hares -modify dbdg Enabled 1 + hares -add dbip FileOnOff dbsg VCS NOTICE V-16-1-10242 Resource added. Copyright © 2012 Symantec Corporation./eastmain.cmd command and observe the output taking notice of the VCS warning when failing to add the VCS user named oper as an Operator for the testappsg and websg service groups. Enabled attribute must be set before agent monitors + hares -modify dbip PathName /var/tmp/dbip 203 Lab 2: Merging clusters B–59 Copyright © 2012 Symantec Corporation. populating SystemList and setting the Parallel attribute recommended before adding resources + hagrp -modify dbsg SystemList sym3 0 sym4 1 + hagrp -modify dbsg AutoStartList sym3 sym4 + hagrp -modify dbsg SourceFile ./eastmain.cmd file and would need to be re-added and re-configured later on. Solution sh -x .Exercise 4: Adding service groups and resources In this exercise. . All rights reserved. navigate to the /etc/VRTSvcs/conf/config directory and open the VCS configuration for update Solution a cd /etc/VRTSvcs/conf/config b haconf -makerw End of Solution 2 Run the sh -x . sym3 1 From sym3:terminal1.

All rights reserved. populating SystemList and setting the Parallel attribute recommended before adding resources + hagrp -modify testappsg SystemList sym3 0 sym4 1 + hagrp -modify testappsg AutoStartList sym3 sym4 + hagrp -modify testappsg Operators oper VCS WARNING V-16-1-50109 User oper is not a valid Cluster user + hagrp -modify testappsg SourceFile .cf + hares -add testappdg FileOnOff testappsg VCS NOTICE V-16-1-10242 Resource added.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. All rights reserved. Enabled attribute must be set before agent monitors + hares -modify testappmnt PathName /var/tmp/testappmnt + hares -modify testappmnt Enabled 1 + hares -add testappnic FileOnOff testappsg VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors + hares -modify dblistener PathName /var/tmp/dblistener + hares -modify dblistener Enabled 1 + hares -add dbmnt FileOnOff dbsg VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors + hares -modify dbmnt PathName /var/tmp/dbmnt + hares -modify dbmnt Enabled 1 + hares -add dbnic FileOnOff dbsg VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors + hares -modify dbvol PathName /var/tmp/dbvol + hares -modify dbvol Enabled 1 + hagrp -add testappsg VCS NOTICE V-16-1-10136 Group added. 204 B–60 + hares -modify dbip Enabled 1 + hares -add dblistener FileOnOff dbsg VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors + hares -modify testappdg PathName /var/tmp/testappdg + hares -modify testappdg Enabled 1 + hares -add testappmnt FileOnOff testappsg VCS NOTICE V-16-1-10242 Resource added.Copyright © 2012 Symantec Corporation. Enabled attribute must be set before agent monitors + hares -modify dbnic PathName /var/tmp/dbnic + hares -modify dbnic Enabled 1 + hares -add dboracle FileOnOff dbsg VCS NOTICE V-16-1-10242 Resource added. populating SystemList and setting the Veritas Cluster Server 5. Enabled attribute must be set before agent monitors + hares -modify testappproc PathName /var/tmp/testappproc + hares -modify testappproc Enabled 1 + hares -add testappip FileOnOff testappsg VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors + hares -modify dboracle PathName /var/tmp/dboracle + hares -modify dboracle Enabled 1 + hares -add dbvol FileOnOff dbsg VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors + hares -modify testappip PathName /var/tmp/testappip + hares -modify testappip Enabled 1 + hares -add testappvol FileOnOff testappsg VCS NOTICE V-16-1-10242 Resource added. . Enabled attribute must be set before agent monitors + hares -modify testappvol PathName /var/tmp/testappvol + hares -modify testappvol Enabled 1 + hagrp -add websg VCS NOTICE V-16-1-10136 Group added./main. Enabled attribute must be set before agent monitors + hares -modify testappnic PathName /var/tmp/testappnic + hares -modify testappnic Enabled 1 + hares -add testappproc FileOnOff testappsg VCS NOTICE V-16-1-10242 Resource added.

Enabled attribute must be agent monitors + hares -modify webapache PathName /var/tmp/webapache + hares -modify webapache Enabled 1 + hares -add webdg FileOnOff websg VCS NOTICE V-16-1-10242 Resource added. All rights reserved. Enabled attribute must be agent monitors + hares -modify webdg PathName /var/tmp/webdg + hares -modify webdg Enabled 1 + hares -add webmnt FileOnOff websg VCS NOTICE V-16-1-10242 Resource added. All rights reserved. Enabled attribute must be agent monitors + hares -modify webvol PathName /var/tmp/webvol + hares -modify webvol Enabled 1 + hares -link dbip dbnic + hares -link dblistener dbip + hares -link dblistener dboracle + hares -link dbmnt dbvol + hares -link dboracle dbmnt + hares -link dbvol dbdg + hares -link testappmnt testappvol + hares -link testappproc testappmnt + hares -link testappproc testappip + hares -link testappip testappnic + hares -link testappvol testappdg + hares -link webapache webmnt + hares -link webapache webvip + hares -link webmnt webvol + hares -link webvip webnic + hares -link webvol webdg set before set before set before set before set before set before End of Solution 3 Save and close the VCS configuration. Parallel attribute recommended before adding resources + hagrp -modify websg SystemList sym3 0 sym4 1 + hagrp -modify websg AutoStartList sym3 sym4 + hagrp -modify websg Operators oper VCS WARNING V-16-1-50109 User oper is not a valid Cluster user + hagrp -modify websg SourceFile .Copyright © 2012 Symantec Corporation. Enabled attribute must be agent monitors + hares -modify webvip PathName /var/tmp/webvip + hares -modify webvip Enabled 1 + hares -add webvol FileOnOff websg VCS NOTICE V-16-1-10242 Resource added.cf + hares -add webapache FileOnOff websg VCS NOTICE V-16-1-10242 Resource added./main. Enabled attribute must be agent monitors + hares -modify webmnt PathName /var/tmp/webmnt + hares -modify webmnt Enabled 1 + hares -add webnic FileOnOff websg VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be agent monitors + hares -modify webnic PathName /var/tmp/webnic + hares -modify webnic Enabled 1 + hares -add webvip FileOnOff websg VCS NOTICE V-16-1-10242 Resource added. . Solution haconf -dump -makero End of Solution 205 Lab 2: Merging clusters B–61 Copyright © 2012 Symantec Corporation.

. All rights reserved. All rights reserved. perform a summary status on the cluster taking note of the service groups that are not online. Solution Copyright © 2012 Symantec Corporation. – The oper user from the old east cluster is not defined nor is the Operator service group attribute for the testappsg and websg service groups set to the oper user.System State Frozen A A A A RUNNING RUNNING RUNNING RUNNING 0 0 0 0 sym1 sym2 sym3 sym4 -. sym3 1 From sym3:terminal1.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Veritas Cluster Server 5. you verify the merged cluster.Group System B B B B B B B B B B B B B B B B sym1 sym2 sym3 sym4 sym1 sym2 sym3 sym4 sym1 sym2 sym1 sym2 sym3 sym4 sym3 sym4 ClusterService ClusterService ClusterService ClusterService appsg appsg dbsg dbsg nfssg nfssg orasg orasg testappsg testappsg websg websg Probed Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y AutoDisabled N N N N N N N N N N N N N N N N State ONLINE OFFLINE OFFLINE OFFLINE ONLINE OFFLINE OFFLINE OFFLINE ONLINE OFFLINE ONLINE OFFLINE OFFLINE OFFLINE OFFLINE OFFLINE End of Solution 2 Display /etc/VRTSvcs/conf/config/main. hastatus -sum 206 B–62 -.SYSTEM STATE -.GROUP STATE -.cf file and notice the following.Exercise 5: Merged cluster verification In this exercise.

.. group appsg ( SystemList = { sym1 = 0.. more /etc/VRTSvcs/conf/config/main. sym2 = 1 } AutoStartList = { sym1. sym2 = 1 } AutoStartList = { sym1.51" Administrators = { admin } ) .. testappsg.10. RESFAULT } TriggersEnabled @sym2 = { NOFAILOVER.. and orasg service groups remain set to sym1 and sym2. sym2. Note: These service groups could be online on sym1 and sym2 and could be modified to accommodate that. All rights reserved. sym3. Solution Copyright © 2012 Symantec Corporation. sym2 = 1 } AutoStartList = { sym1. sym2 } TriggersEnabled @sym1 = { NOFAILOVER. sym4 } OnlineRetryLimit = 3 OnlineRetryInterval = 120 ) . group ClusterService ( SystemList = { sym1 = 0.. nfssg. .2. All rights reserved. cluster west ( UserNames = { admin = bQRjQLqNRmRRpZRlQO } ClusterAddress = "10.cf . – The SystemList and AutoStartList service group attributes for the websg.. Note: Consideration needs to be given to activated triggers configured at any service group and/or resource level if the service group is going to be re-configured to run on a new cluster system. RESFAULT } ) . sym2 } 207 Lab 2: Merging clusters B–63 Copyright © 2012 Symantec Corporation. sym3 = 2. Note: These service groups cannot be online on sym3 and sym4 due to shared LUN restrictions... group orasg ( SystemList = { sym1 = 0. sym4 = 3 } AutoStartList = { sym1. sym2 } ) . group nfssg ( SystemList = { sym1 = 0. – The SystemList and AutoStartList service group attributes for the appsg.– The SystemList and AutoStartList service group attributes for the ClusterService service group have been modified for all four cluster systems.. sym2 = 1. and dbsg service groups remain set to sym3 and sym4.

. sym4 } . All rights reserved. sym4 = 1 } AutoStartList = { sym3. sym4 = 1 } AutoStartList = { sym3. sym4 } ) .. group websg ( SystemList = { sym3 = 0. sym4 } ) . End of lab 208 B–64 Veritas Cluster Server 5... group testappsg ( SystemList = { sym3 = 0.. sym4 = 1 } AutoStartList = { sym3...1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.) .. group dbsg ( SystemList = { sym3 = 0.. All rights reserved. End of Solution Copyright © 2012 Symantec Corporation.

. All rights reserved. Exercise 5: Testing prerequisites and limits Prerequisites and limits are examined and added to the load failover policy settings. 209 Lab 3: Failover policies B–65 Copyright © 2012 Symantec Corporation.Lab 3: Failover policies In this lab. Exercise 4: Testing load failover policy The load failover policy is examined. All rights reserved. Exercise 2: Starting the simulator The simulation used in the lab is examined and the Veritas VCS Simulator is started. This lab contains the following exercises: Exercise 1: Checking lab prerequisites A verification that the virtual machines needed for this lab are powered on and functioning is performed. Exercise 3: Testing priority failover policy The default priority failover policy is examined. Copyright © 2012 Symantec Corporation.cf file to show how to configure and test failover policies using the Veritas Cluster Manager Java Console. Exercise 6: Stopping the simulator The simulation used in the lab is examined and the Veritas VCS Simulator is terminated. you use the Veritas Cluster Server Simulator with a preconfigured main.

that you are logged using the indicated account and that the indicated terminal windows are opened. this will require you to shutdown sym1.Exercise 1: Checking lab prerequisites In this exercise. shut down the operating system and power the machines off. and power on and log into winclient. sym3 and sym4. and sym2:terminal2. Note: If you are completing the lab exercises in order. sym2. – winclient › Log in with credentials: Account: Administrator Password: veritas Note: The terminal windows are referred to as hostname:terminal# throughout the labs. that you are logged in using the proper account and that any needed terminal windows are opened. For example: sym1:terminal1. All rights reserved. sym2:terminal1. – mgt › There is no need to log into this virtual machine at this time. you verify that the virtual machines needed for this lab are powered on and functioning. Copyright © 2012 Symantec Corporation. sym1:terminal2. . 2 210 B–66 If you have machines running that are not used in this lab.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. It is not necessary to label the terminal windows and you may decide which is terminal1 and which is terminal2. Veritas Cluster Server 5. All rights reserved. 1 Verify that the following virtual machines shown are powered on.

winclient 1 From the winclient desktop. d Clear Always use the selected program to open this kind of file. e Select WordPad.cf file and select Open. Solution 211 a Right-click the main. b From the pop-up window. Copyright © 2012 Symantec Corporation. End of Solution Lab 3: Failover policies B–67 Copyright © 2012 Symantec Corporation. . b From the left pane. All rights reserved. Solution a From the desktop.cf file using the WordPad application.Exercise 2: Starting the simulator In this exercise. expand and select Computer > C: > Program Files (x86) > VERITAS > VCS Simulator > wlm > conf > config. use Windows Explorer to navigate to the C:\Progam Files (x86)\VERITAS\VCS Simulator\wlm\ conf\config folder. End of Solution 2 Open the main. you examine the simulation used in the lab and start the Veritas VCS Simulator. c Click OK. double-click the Computer icon. All rights reserved. select Select a program from a list of installed programs. f Click OK.

Note: Alternately. review the contents of the main. End of Solution Veritas Cluster Server 5. End of Solution 4 Start the Veritas VCS Simulator. click the Close button that appears as an X in the upper right hand corner of the window. from the start bar. Solution a From the Wordpad window. review the contents of the main. click OK. All rights reserved.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. double-click the Veritas VCS Simulator – Java Console icon.3 Without making any changes. select Start > All programs > Symantec > Veritas VCS Simulator – Java Console. close the Wordpad and Windows Explorer windows. click Verify Configuration. c From the Windows Explorer window. Then. from the left pane list. Solution a From the Symantec Veritas Cluster Server Simulation window. . select wlm. c From the pop-up window.cf file. Copyright © 2012 Symantec Corporation. b From the task (right) pane. Note: The VCS Simulator may take a moment to display as it discovers any running simulations even thought there will not be any. Solution From the desktop.cf file. b Click the Close button that appears as an X in the upper right hand corner of the window. End of Solution 212 B–68 5 Verify the wlm simulation. All rights reserved.

Solution a From the left pane list. select wlm. type: password e Click OK. All rights reserved. type: admin d In the Password field. . – User name: admin – Password: password Solution a From the left pane list. All rights reserved. Copyright © 2012 Symantec Corporation. b From the task (right) pane. c In the User name field. b From the task (right) pane. Click Launch Console. Click Start Cluster. select wlm.6 Start the wlm simulation. Note: The status of the cluster name will have a green check mark upon successful startup. End of Solution 213 Lab 3: Failover policies B–69 Copyright © 2012 Symantec Corporation. End of Solution 7 Launch the VCS – Java Console and log in using the following credentials.

S3 (1). S2 (2). D1 and D2 service groups. C1. S2 (1). S3 (4). Copyright © 2012 Symantec Corporation. . S2 (1). S4 (4) S1 B1 S1 (4). S2 (4). S2 (3). S2 (2). C2. b From the right pane. S2 (4). S4 (1) S4 D2 S1 (2). S4 (3) S2 B2 S1 (4). S3 (2). End of Solution 214 B–70 Veritas Cluster Server 5. Service Group Member Systems (Priority) AutoStartList A1 S1 (1). S4 (1) S4 Solution a From the left pane. verify that the Member Systems and their Priority and their AutoStartList attribute are set to the values shown in the following table. B1. All rights reserved. S4 (2) S3 C2 S1 (3). d From the System Details section. S3 (3). e Repeat steps a through d for the A2. S4 (4) S1 A2 S1 (1). S4 (2) S3 D1 S1 (2). All rights reserved. S3 (2). c Verify the AutoStartList attribute. B2.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. S3 (4).8 From the Java Console. select wlm > A1. S3 (1). S3 (3). verify Member Systems and their Priority. S4 (3) S2 C1 S1 (3). select the Properties tab. S2 (3).

D1 and D2 service groups. All rights reserved. Lab 3: Failover policies B–71 Copyright © 2012 Symantec Corporation. C1. winclient 1 From the Java Console. verify that the FailOverPolicy attribute is set to Priority. b From the right pane. Service Group System S1 A1 Online A2 Online System S2 B1 Online B2 Online System S3 C1 Online C2 Online System S4 D1 Online D2 Online Solution a From the left pane. . select wlm > A1. you examine the default priority failover policy. B2. C2. select wlm.Exercise 3: Testing priority failover policy In this exercise. Solution a From the left pane. End of Solution Copyright © 2012 Symantec Corporation. c Repeat steps a and b for the A2. verify that the failover policy of all service groups is Priority. 2 215 Verify that all service groups are online as shown in the following table. All rights reserved. B1.

c Verify the service groups are online as shown in the above table. click Yes. b Right-click wlm > A1 > FileOnOff > A1File and select Fault Resource > S1. . End of Solution Copyright © 2012 Symantec Corporation.b From the right pane. d From the right pane. All rights reserved.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Note: This view is referred to as the Cluster Status view. where will the A1 service group fail over to? Verify this failover by faulting a critical resource in the A1 service group. but Online on S2. Veritas Cluster Server 5. where should it fail over? Verify the failover by faulting a critical resource in the A1 service group. right-click wlm > A1> FileOnOff > A1File and select Fault Resource > S2. select the Status tab. b From the pop-up window. notice that the A1 service group shows faulted on S1. click Yes. All rights reserved. expand wlm > A1 > FileOnOff > A1File. Service Group A1 will fail over to: S3 Solution a From the left pane. Service Group A1 will fail over to: S2 Solution a From left pane. 4 216 B–72 If the A1 service group faults again without clearing the previous fault. End of Solution 3 If it faults. c From the pop-up window.

but Online on S1. b Right-click wlm > A1 > FileOnOff > A1File and select Fault Resource > S3. notice that the A1 service group shows faulted on S3. From the left pane. All rights reserved. c From the pop-up window.c From the right pane. notice that the A1 service group shows faulted on S1. All rights reserved. . Where will the service group fail over to now? Verify the failover by faulting a critical resource in the A1 service group. and S2 but Online on S3. End of Solution 6 Clear the faults in the A1 service group. right-click wlm > A1 > FileOnOff > A1File and select Clear Fault > Auto. Solution Copyright © 2012 Symantec Corporation. d From the right pane. right-click wlm > A1 > FileOnOff > A1File and select Clear Fault > Auto. Service Group A1 will fail over to: S1 Solution a From the left pane. click Yes. 217 End of Solution Lab 3: Failover policies B–73 Copyright © 2012 Symantec Corporation. End of Solution 5 Clear the faults in the A1 service group.

winclient 1 From the Java Console.Exercise 4: Testing load failover policy In this exercise. All rights reserved. select wlm > A1. Solution From the menu. Note: The drop-down menu will appear when you click in the Scaler Value field. B1. D1 and D2 service groups. C1. Copyright © 2012 Symantec Corporation. open the cluster configuration for update. c To the right of the FailOverPolicy attribute click the Edit button. select Load. from the Scaler Value drop-down menu. . B2.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. select File > Open Configuration. d From the Edit Attribute window. All rights reserved. Solution 218 B–74 a From the left pane. b From the right pane. End of Solution Veritas Cluster Server 5. f Repeat steps a through e for the A2. C2. select the Properties tab. e Click OK. End of Solution 2 Set the FailOverPolicy attribute to Load for the eight service groups. you examine the load failover policy.

D1 and D2 service groups using the Load value shown in the table above. End of Solution 4 Set the S1 and S2 systems’ Capacity attributes to 200. Solution a From the left pane. Solution 219 a From the left pane. B1. d Scroll to the Load attribute and click the Edit icon. g Close the Attributes View window. C2. Lab 3: Failover policies B–75 Copyright © 2012 Symantec Corporation. B2. type: 75 f Click OK. Note: The S3 and S4 systems’ Capacity attribute will not be changed and defaults to 100. select wlm > A1. select the Properties tab. h Repeat steps a through g for the A2. C1. e From the Edit Attribute window. . in the Scaler Value field. c Click Show all attributes. Service Group Load A1 75 A2 75 B1 75 B2 75 C1 50 C2 50 D1 50 D2 50 Copyright © 2012 Symantec Corporation. b From the right pane. All rights reserved. select the Systems tab.3 Set the Load attribute for each service group as shown in the following table. All rights reserved.

Service Group AvailableCapacity S1 50 S2 50 S3 0 S4 0 Copyright © 2012 Symantec Corporation. c From the right pane.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. type: 200 g Click OK. h Close the Attributes View window. in the Scaler Value field. End of Solution Veritas Cluster Server 5. f From the pop-up window. . e Scroll to the Capacity attribute and click the Edit icon. d Verify that the AvaliableCapacity is set to the value shown in the table above. b From the right pane. e Close the Attributes View window. End of Solution 5 Verify that the system’s AvailableCapacity attribute is as shown in the following table. S3 and S4 systems. All rights reserved. select wlm > S1. f Repeat steps a through e for the S2. d Click Show all attributes. All rights reserved. i Repeat steps a through h for the S2 system.b Select wlm > S1. Solution 220 B–76 a From the left pane. select the Properties tab. c Click Show all attributes. select the Properties tab.

End of Solution 8 If it faults. Lab 3: Failover policies B–77 Copyright © 2012 Symantec Corporation. where will the A1 service group fail over to? Verify this failover by faulting a critical resource in the A1 service group. End of Solution 7 Verify that all service groups are online as shown in the following table.6 Save the configuration changes. select File >Save Configuration. select the Service Groups tab. Solution 221 a From the left pane. a Select wlm. select the Status tab. . All rights reserved. b From the right pane. expand wlm > A1 > FileOnOff > A1File. All rights reserved. c Verify the service groups are online as shown in the above table. Solution From the menu. Service Group System S1 A1 Online A2 Online System S2 B1 Online B2 Online System S3 C1 Online C2 Online System S4 D1 Online D2 Online Copyright © 2012 Symantec Corporation. Service Group A1 will fail over to: S2 Solution a From left pane.

c From the pop-up window. Service Group AvailableCapacity S1 125 S2 -25 S3 0 S4 0 Copyright © 2012 Symantec Corporation. select the Systems tab. All rights reserved. End of Solution Veritas Cluster Server 5. d Click Show all attributes. End of Solution 9 Verify that the system’s AvailableCapacity attribute is as shown in the following table. e Verify that the AvaliableCapacity is set to the value shown in the table above. b Select wlm > S1. c From the right pane. Solution 222 B–78 a From the left pane. f Close the Attributes View window. d From the right pane. S3 and S4 systems. .1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. g Repeat steps b through e for the S2. All rights reserved. but Online on S2. select the Properties tab. notice that the A1 service group shows faulted on S1.b Right-click wlm > A1 > FileOnOff > A1File and select Fault Resource > S1. click Yes.

223 Lab 3: Failover policies B–79 Copyright © 2012 Symantec Corporation. Service Group AvailableCapacity S1 -25 S2 200 S3 -75 S4 0 Solution a From the left pane. select the Status tab. where will the A1. c From the right pane. d Verify that the AvaliableCapacity is set to the value shown in the table above.10 If the S2 system fails. c Click Show all attributes. select wlm > S1. e Notice that the B1 and B2 service groups show Online on S1. right-click wlm > S2 and select on Power Off. e Close the Attributes View window. following table. End of Solution 11 Verify that the system’s AvailableCapacity attribute is as shown in the Copyright © 2012 Symantec Corporation. B1 and B2 service groups that are Online on S2 fail over? Verify this failover by powering off the S2 system in Cluster Manager. b Select wlm. All rights reserved. All rights reserved. . select the Properties tab. The A1 service group will fail over to: S3 The B1 service group will fail over to: S1 The B2 service group will fail over to: S1 Solution a From the left pane. d Notice that the A1 service group shows faulted on S1. but Online on S3. b From the right pane.

click Yes. c Right-click wlm > A1 and select Clear Fault > Auto. and return the service groups to their startup locations. S3 and S4 systems. following table. End of Solution 12 Power up the S2 system. Veritas Cluster Server 5. h Right-click wlm > B2 and select Switch To > S2. click Yes. f Right-click wlm > B1 and select Switch To > S2.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. click Yes. g From the pop-up window. All rights reserved. Solution a From the left pane.f Repeat steps b through f for the S2. d Right-click wlm > A1 and select Switch To > S1. i From the pop-up window. e From the pop-up window. . b Select wlm > S1. Solution 13 Verify that the system’s AvailableCapacity attribute is as shown in the Copyright © 2012 Symantec Corporation. clear all faults. b Select the Service Groups tab. 224 B–80 Service Group AvailableCapacity S1 50 S2 50 S3 0 S4 0 Solution a From the left pane. right-click wlm > S2 and select Up > S2. select the Systems tab. All rights reserved.

if you want to view the modifications to the main. g Repeat steps b through f for the S2. S3 and S4 systems. e Verify that the AvaliableCapacity is set to the value shown in the table above. select the Properties tab.cf file then save the changes. Solution From the menu. . d Click Show all attributes.c From the right pane. End of Solution 14 Save and close the configuration changes. However. f Close the Attributes View window. All rights reserved. select File >Close Configuration. All rights reserved. End of Solution 225 Lab 3: Failover policies B–81 Copyright © 2012 Symantec Corporation. Copyright © 2012 Symantec Corporation. Note: Saving changes to the configuration is not necessary for purposes of this lab.

click the add an element button. All rights reserved. .Exercise 5: Testing prerequisites and limits In this exercise. open the cluster configuration for update. select the Systems tab. you examine the prerequisites and limits and add them to the load failover policy settings. type: 3 i Click OK. b Select wlm > S1. f From the Edit Attribute window.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Solution From the menu. End of Solution 2 Set the Limits attribute for each system to the key ABGroup with a value of 3. g In the Key field. type: ABGroup h In the Value field. c From the right pane. k Repeat steps b through j for the S2. Copyright © 2012 Symantec Corporation. All rights reserved. e Scroll to the Limits attribute and click the Edit icon. select the Properties tab. select File > Open Configuration. winclient 1 From the Java Console. End of Solution Veritas Cluster Server 5. j Close the Attributes View window. Solution 226 B–82 a From the left pane. S3 and S4 systems. d Click Show all Attributes.

3 Set the Prerequisites attribute for the A1. and D2 service groups. k Repeat steps b through j for the A2. CAUTION Do not modify the Prerequisites attribute for the C1. j Close the Attributes View window. . b Select wlm > A1. click the add an element button. C2. Solution From the menu. select the Service Groups tab. c From the right pane. type: ABGroup h In the Value field. type: 1 i Click OK. e Scroll to the Prerequisites attribute and click the Edit icon. B1 and B2 service groups. End of Solution 227 Lab 3: Failover policies B–83 Copyright © 2012 Symantec Corporation. A2. B1 and B2 service groups to be ABGroup with a value of 1. D1. select File >Save Configuration. All rights reserved. f From the Edit Attribute window. g In the Key field. d Click Show all Attributes. Copyright © 2012 Symantec Corporation. select the Properties tab. All rights reserved. Solution a From the left pane. End of Solution 4 Save the configuration changes.

and B2 failed over to S4 due to the values of the Load attribute on each system. select the Systems tab. e Select wlm. select the Status tab. b Select wlm. Explain the failover actions that occurred. All rights reserved. B1 failed over to S3.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Explain the failover actions that occurred. right-click wlm > S1 and select on Power Off. All rights reserved. B1 and B2 service groups that are Online on S2 fail over? Verify this failover by powering off the S2 system in Cluster Manager. End of Solution Copyright © 2012 Symantec Corporation. where will the A1 and A2 service groups that are Online on S1 fail over? Verify this failover by powering off the S1 system in Cluster Manager. but A2 failed over to S3 because the limit was reached on S2. The A1 service group will fail over to: S4 The B1 service group will fail over to: S3 The B2 service group will fail over to: S4 A1 failed over to S4. 6 228 B–84 If the S2 system fails.5 If the S1 system fails. The A1 service group will fail over to: S2 The A2 service group will fail over to: S3 A1 failed over to S2. where will the A1. g Notice that the A1 service group shows Online on S2. Veritas Cluster Server 5. c From the right pane. f From the right pane. . h Notice that the A2 service group show Online on S3. d From the left pane. select the Status tab. Solution a From the left pane.

B1 is the last group to attempt to fail over to S4. All rights reserved. The A2 service group will fail over to: S4 The B1 service group will fail over to: B1 does not fail over and stays offline The C1 service group will fail over to: S4 The C2 service group will fail over to: S4 All service groups fail over to S4 except B1. where will the A2. it cannot fail over. c From the right pane. right-click wlm > S3 and select on Power Off. select the Status tab. and B2 can run on the same system. e Notice that the B1 service group shows Offline on all systems. All rights reserved. right-click wlm > S2 and select on Power Off. e Notice that the B1 service group show Online on S3. d Notice that the A2 service group shows Online on S4. b Select wlm. Solution a From the left pane. 229 Lab 3: Failover policies B–85 Copyright © 2012 Symantec Corporation. . select the Status tab. d Notice that the A1 service group shows Online on S4. b Select wlm. End of Solution 7 If the S3 system fails. B1 stays offline. B1. A1. f Notice that the B2 service group show Online on S4. Copyright © 2012 Symantec Corporation. B1. c From the right pane. C1 and C2 service groups that are Online on S3 fail over? Verify this failover by powering off the S3 system in Cluster Manager. A2. Explain the failover actions that occurred. Since B1 has a prerequisite that cannot be met on S4.Solution a From the left pane.

However. Copyright © 2012 Symantec Corporation. End of Solution 8 Save and close the configuration changes.cf file then save the changes.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Solution From the menu. select File >Close Configuration. All rights reserved. .f Notice that the C1 service group show Online on S4. g Notice that the C2 service group show Online on S4. End of Solution 230 B–86 Veritas Cluster Server 5. Note: Saving changes to the configuration is not necessary for purposes of this lab. All rights reserved. if you want to view the modifications to the main.

click Verify Configuration. End of Solution 2 From the Simulator Java Console. you terminate the simulation and the Veritas VCS Simulator. Solution a From the left pane list. stop the wlm cluster.Exercise 6: Stopping the simulator In this exercise. . Note: If you intend to move this configuration in to a running cluster. Solution a From the task (right) pane. you must ensure the main. You can verify the configuration only in the Simulator GUI after the cluster is stopped. End of Solution Copyright © 2012 Symantec Corporation. select wlm. click OK. b From the task (right) pane. 3 231 Verify the configuration. All rights reserved. b From the pop-up window. select File >Log Out. Solution From the menu. click Stop Cluster. All rights reserved.cf syntax is correct. End of Solution Lab 3: Failover policies B–87 Copyright © 2012 Symantec Corporation. winclient 1 Log out from Cluster Explorer.

4 Close the Simulator Java Console. All rights reserved. . Note: The Veritas Cluster Manager Java Console should close as well. End of Solution Copyright © 2012 Symantec Corporation. All rights reserved. End of lab 232 B–88 Veritas Cluster Server 5.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. If it does not then close it manually. Solution Click the Close button that appears as an X in the upper right hand corner of the window.

All rights reserved. This lab contains the following exercises: Exercise 1: Checking lab prerequisites A verification that the virtual machines needed for this lab are powered on and functioning is performed. Exercise 3: Replacing NIC resources with Proxy resources The pre-existing resources of type NIC supporting application VIPs in each application service group are replaced with resources of type Proxy. Exercise 2: Configuring a common parallel network service group A common parallel network service group and resources is configured.Lab 4: Creating a parallel network service group In this lab application networking is reconfigured to be more efficient. Copyright © 2012 Symantec Corporation. 233 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation. B–89 . All rights reserved.

All rights reserved. It is not necessary to label the terminal windows and you may decide which is terminal1 and which is terminal2. – sym2 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. – sym1 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. – sym4 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. Copyright © 2012 Symantec Corporation. that you are logged using the indicated account and that the indicated terminal windows are opened. sym2:terminal1. . Note: The terminal windows are referred to as hostname:terminal# throughout the labs. – mgt › There is no need to log into this virtual machine at this time. Veritas Cluster Server 5. – sym3 › Log in with credentials: Account: root Password: veritas › Two terminal windows should be active on this server. All rights reserved. For example: sym1:terminal1.Exercise 1: Checking lab prerequisites In this exercise. you verify that the virtual machines needed for this lab are powered on and functioning. that you are logged in using the proper account and that any needed terminal windows are opened. sym1:terminal2. and sym2:terminal2. 1 234 B–90 Verify that the following virtual machines shown are powered on.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.

and power on and log into sym1.2 If you have machines running that are not used in this lab. B–91 . sym3 and sym4. 235 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation. Note: If you are completing the lab exercises in order. shut down the operating system and power the machines off. sym2. Copyright © 2012 Symantec Corporation. All rights reserved. All rights reserved. this will require you to shutdown winclient.

Solution haconf -makerw End of Solution 2 Use the hagrp command to create a service group named netsg. Solution hagrp -modify netsg SystemList sym1 0 sym2 1 sym3 2 sym4 3 End of Solution Veritas Cluster Server 5. All rights reserved. sym2. 3 236 B–92 Modify the SystemList to allow the netsg service group to run on the sym1. sym3. Solution hagrp -add netsg VCS NOTICE V-16-1-10136 Group added. . and sym4 in that order.Exercise 2: Configuring a common parallel network service group In this exercise. you configure a common parallel network service group and resources. All rights reserved.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. use the haconf command to open the cluster configuration for update. sym1 1 From sym1:terminal1. populating SystemList and setting the Parallel attribute recommended before adding resources Solution Copyright © 2012 Symantec Corporation.

Solution hagrp -modify netsg Parallel 1 End of Solution 6 Display the service group attributes for the netsg service group to confirm your input and key default service group attribute values.4 Modify the AutoStartList attribute to allow the service group to start on all systems. All rights reserved.. 2 Attribute AdministratorGroups Administrators Authority AutoFailOver AutoRestart AutoStart AutoStartIfPartial AutoStartList AutoStartPolicy ClusterFailOverPolicy System global global global global global global global global global global Value Parallel global 1 SystemList sym4 global 0 1 1 1 1 sym1 Order Manual sym1 sym2 0 sym3 sym4 sym2 1 3 End of Solution 237 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation.. netsg ... Solution Copyright © 2012 Symantec Corporation.. Solution hagrp -modify netsg AutoStartList sym1 sym2 sym3 sym4 End of Solution 5 Modify the Parallel service group to configure the netsg service group as a parallel service group. B–93 . hagrp -display netsg | more #Group netsg netsg netsg netsg netsg netsg netsg netsg netsg netsg . netsg sym3 .. All rights reserved.

. Solution hares -add netnic NIC netsg VCS NOTICE V-16-1-10242 Resource added. but do not close it.. All rights reserved.. 238 B–94 Solution hares -display netnic | more #Resource netnic netnic netnic netnic netnic . All rights reserved. Solution haconf -dump End of Solution 8 Add a resource of type NIC named netnic to the netsg service group.. netnic . .1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. – Device is eth0 – Critical set to 0 (zero) Solution a hares -modify netnic Device eth0 b hares -modify netnic Critical 0 End of Solution 10 Display the resource attribute values for the netnic resource to confirm your Copyright © 2012 Symantec Corporation. Enabled attribute must be set before agent monitors End of Solution 9 Modify the Device and Critical resource attributes for the netnic resource using the following information.7 Save the VCS configuration. input and key default resource attribute values. Attribute Group Type AutoStart Critical Enabled System global global global global global Value netsg NIC 1 0 0 Device global eth0 End of Solution Veritas Cluster Server 5.

Solution a hares -modify netnic Enabled 1 b hares -value netnic Enabled 1 c hares -state netnic #Resource netnic netnic netnic netnic Attribute State State State State System sym1 sym2 sym3 sym4 Value ONLINE ONLINE ONLINE ONLINE End of Solution 12 Display the state of the netsg service group. This is because VCS does not consider persistent resources when determining the state of a service group. Note: It is not necessary to bring a resource of type NIC online. Display the state of the netnic resource to ensure that it is online on both cluster systems. Solution Copyright © 2012 Symantec Corporation. hagrp -state netsg #Group netsg netsg netsg netsg Attribute State State State State System sym1 sym2 sym3 sym4 Value |OFFLINE| |OFFLINE| |OFFLINE| |OFFLINE| End of Solution 13 Save the VCS configuration.11 Enable the netnic resource and verify that it is enabled. but do not close it. All rights reserved. Solution haconf -dump End of Solution 239 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation. Note: The service group state is offline even though the NIC resource state is online. B–95 . All rights reserved.

Solution hares -display netphantom | more #Resource netphantom netphantom netphantom netphantom netphantom .1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation.. All rights reserved. Solution hares -modify netphantom Critical 0 End of Solution 16 Display the resource attribute values for the netphantom resource to confirm your input and key default resource attribute values. . Note: It is not necessary to bring a resource of type Phantom online.14 Add a resource of type Phantom named netphantom to the netsg service group. Attribute Group Type AutoStart Critical Enabled System global global global global global Value netsg Phantom 1 0 0 Copyright © 2012 Symantec Corporation. Solution hares -add netphantom Phantom netsg VCS NOTICE V-16-1-10242 Resource added. All rights reserved. End of Solution 240 B–96 17 Enable the netphantom resource and verify that it is enabled. Solution a hares -modify netphantom Enabled 1 b hares -value netphantom Enabled 1 Veritas Cluster Server 5. Display the state of the netphantom resource to ensure that it is online on both cluster systems. Enabled attribute must be set before agent monitors End of Solution 15 Set the Critical resource attribute to 0 (zero) for the netphantom resource..

Solution hagrp -state netsg #Group netsg netsg netsg netsg Attribute State State State State System sym1 sym2 sym3 sym4 Value |ONLINE| |ONLINE| |ONLINE| |ONLINE| End of Solution 19 Save the VCS configuration. All rights reserved. B–97 . All rights reserved. Solution haconf -dump Copyright © 2012 Symantec Corporation. End of Solution 241 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation. Note: The service group state is offline even though the NIC resource state is online.c hares -state netphantom #Resource netphantom netphantom netphantom netphantom Attribute State State State State System sym1 sym2 sym3 sym4 Value ONLINE ONLINE ONLINE ONLINE End of Solution 18 Display the state of the netsg service group. but do not close it. This is because VCS does not consider persistent resources when determining the state of a service group.

you replace the pre-existing resources of type NIC that supporting application VIPs in each application service group with resources of type Proxy.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. sym1 1 From sym1:terminal1. . identify the names of the resources of type NIC that are configured. All rights reserved.Exercise 3: Replacing NIC resources with Proxy resources In this exercise. All rights reserved. list the resource dependencies associated with the listed resources of type NIC. Solution hares -dep appnic csgnic nfsnic oranic #Group ClusterService ClusterService appsg nfssg orasg Parent notifier webip appip nfsip oraip Child csgnic csgnic appnic nfsnic oranic End of Solution Veritas Cluster Server 5. Solution hares -list Type=NIC appnic appnic csgnic csgnic csgnic csgnic netnic netnic netnic netnic nfsnic nfsnic oranic oranic sym1 sym2 sym1 sym2 sym3 sym4 sym1 sym2 sym3 sym4 sym1 sym2 sym1 sym2 End of Solution Copyright © 2012 Symantec Corporation. 2 242 B–98 Ignoring the resource of type NIC named netnic.

Enabled attribute must be set before agent monitors c hares -modify appproxy Critical 0 d hares -modify appproxy TargetResName netnic e hares -display appproxy | more #Resource appproxy appproxy appproxy appproxy appproxy . Set Enabled to 1 (one). B–99 ..3 Replace the resource of type NIC named appnic with a resource of type Proxy named appproxy using the following information.. – – – – Set the Critical attribute to 0 (zero). 1 h hares -state appproxy #Resource appproxy appproxy Attribute State State System sym1 sym2 i hares -link appip appproxy j hares -dep | grep appproxy appsg appip Value ONLINE ONLINE appproxy End of Solution 243 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation. appproxy . Attribute Group Type AutoStart Critical Enabled System global global global global global Value appsg Proxy 1 0 0 TargetResName global netnic f hares -modify appproxy Enabled 1 g hares -value appproxy Enabled Copyright © 2012 Symantec Corporation. Solution a hares -delete appnic b hares -add appproxy Proxy appsg VCS NOTICE V-16-1-10242 Resource added. All rights reserved. All rights reserved.. Set the TargetResName attribute to netnic. Link to the appip resource..

.. Enabled attribute must be set before agent monitors c hares -modify csgproxy Critical 0 d hares -modify csgproxy TargetResName netnic e hares -display csgproxy | more #Resource csgproxy csgproxy csgproxy csgproxy csgproxy .1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. Set the TargetResName attribute to netnic. 1 244B–100 h hares -state csgproxy #Resource csgproxy csgproxy csgproxy csgproxy Attribute State State State State System sym1 sym2 sym3 sym4 i hares -link webip csgproxy j hares -link notifier csgproxy Value ONLINE ONLINE ONLINE ONLINE Veritas Cluster Server 5.4 Replace the resource of type NIC named csgnic with a resource of type Proxy named csgproxy using the following information. All rights reserved. Solution a hares -delete csgnic b hares -add csgproxy Proxy ClusterService VCS NOTICE V-16-1-10242 Resource added. . Attribute Group Type AutoStart Critical Enabled System global global global global global Value ClusterService Proxy 1 0 0 TargetResName global netnic f hares -modify csgproxy Enabled 1 g hares -value csgproxy Enabled Copyright © 2012 Symantec Corporation.. Set Enabled to 1 (one). csgproxy . Link to the notifier and webip resources. All rights reserved.. – – – – Set the Critical attribute to 0 (zero).

. Attribute Group Type AutoStart Critical Enabled System global global global global global Value nfssg Proxy 1 0 0 TargetResName global netnic f hares -modify nfsproxy Enabled 1 g hares -value nfsproxy Enabled 1 h hares -state nfsproxy #Resource nfsproxy nfsproxy Attribute State State 245 Lab 4: Creating a parallel network service group System sym1 sym2 Value ONLINE ONLINE Copyright © 2012 Symantec Corporation. All rights reserved. nfsproxy .. VCS NOTICE V-16-1-10242 Resource added.. Enabled attribute must be set before agent monitors c hares -modify nfsproxy Critical 0 d hares -modify nfsproxy TargetResName netnic e hares -display nfsproxy | more #Resource nfsproxy nfsproxy nfsproxy nfsproxy nfsproxy . Link to the nfsip resource. All rights reserved.. Set Enabled to 1 (one). Set the TargetResName attribute to netnic.k hares -dep | grep csgproxy ClusterService notifier ClusterService webip csgproxy csgproxy End of Solution 5 Replace the resource of type NIC named nfsnic with a resource of type Proxy named nfsproxy using the following information. Solution a hares -delete nfsnic b hares -add nfsproxy Proxy nfssg Copyright © 2012 Symantec Corporation. – – – – Set the Critical attribute to 0 (zero). B–101 .

i hares -link nfsip nfsproxy j hares -dep | grep nfsproxy nfssg nfsip nfsproxy End of Solution 6 Replace the resource of type NIC named oranic with a resource of type Proxy named oraproxy using the following information.1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. . Attribute Group Type AutoStart Critical Enabled System global global global global global Value orasg Proxy 1 0 0 TargetResName global netnic f hares -modify oraproxy Enabled 1 g hares -value oraproxy Enabled 1 h hares -state oraproxy #Resource oraproxy oraproxy Attribute State State System sym1 sym2 Value ONLINE ONLINE Veritas Cluster Server 5. Enabled attribute must be set before agent monitors 246 B–102 c hares -modify oraproxy Critical 0 d hares -modify oraproxy TargetResName netnic e hares -display oraproxy | more #Resource oraproxy oraproxy oraproxy oraproxy oraproxy . VCS NOTICE V-16-1-10242 Resource added. Solution a hares -delete oranic b hares -add oraproxy Proxy orasg Copyright © 2012 Symantec Corporation. oraproxy . – – – – Set the Critical attribute to 0 (zero). All rights reserved. All rights reserved. Set Enabled to 1 (one)... Set the TargetResName attribute to netnic.. Link to the oraip resource..

All rights reserved.i hares -link oraip oraproxy j hares -dep | grep oraproxy orasg oraip oraproxy End of Solution 7 Save and close the VCS configuration. B–103 . All rights reserved. End of lab 247 Lab 4: Creating a parallel network service group Copyright © 2012 Symantec Corporation. Solution haconf -dump -makero End of Solution Copyright © 2012 Symantec Corporation.

1 for UNIX: Install and Configure Copyright © 2012 Symantec Corporation. 248 B–104 Veritas Cluster Server 5. .Copyright © 2012 Symantec Corporation. All rights reserved. All rights reserved.

All rights reserved. Appendix C Supplemental Content 249 .Copyright © 2012 Symantec Corporation.

0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation.Copyright © 2012 Symantec Corporation. All rights reserved. All rights reserved. Service group dependencies—Failover process 250 C–2 Veritas Cluster Server 6. .

if the faulted service group has an online local (firm or soft) dependency with a child service group that is online only on that system. C–3 . These service groups can be parent service groups that are linked with an offline local dependency or online remote soft dependency. In either case. 5. Appendix C Supplemental Content Copyright © 2012 Symantec Corporation. All rights reserved. or 7 and brings the parent service group online on an available system. For example. 2 Then a failover target is chosen from the SystemList of the service group based on the failover policy and the restrictions brought by the service group dependencies. 7 After the service group is brought online successfully on the target system. online global firm. Note that if the faulted service group is also the parent service group in a service group dependency relationship. first the child service group and then the service group that initiated the failover are brought online. or online local hard). both the child service group and all of the parents that were already taken offline remain offline. 9 If there are no target systems available to fail over the parent service group that has been taken offline. All rights reserved. 5 VCS then checks if there are any conflicting parent service groups that are already online on the target system. the parent service group is taken offline to enable the child service group to start on that system. no failover targets are available. the service group dependency has an impact on the choice of a target system. 3 If there are no other systems to which the service group can fail over. the parent service group remains offline.Copyright © 2012 Symantec Corporation. online remote firm. 4 If there is a failover target then VCS takes any child service group with an online local hard dependency offline. 251 The following steps describe what happens when a service group in a service group dependency relationship is faulted due to a critical resource fault: 1 The entire service group is taken offline due to the critical resource fault together with any of its parent service groups that have an online firm or hard dependency (online local firm. 6 If there is any child service group with an online local hard dependency. VCS takes any parent service groups offline that have an online local soft dependency to the failed-over child. 8 Finally. VCS selects a failover target for any parent service groups that may have been taken offline during steps 1.

All rights reserved. . All rights reserved.0 for UNIX: Cluster Management Copyright © 2012 Symantec Corporation. 252 C–4 Veritas Cluster Server 6.Copyright © 2012 Symantec Corporation.