Cisco Ser

A

P P E N D I X E

Veritas Cluster Server

Revised: September 23, 2015

IntroductionThis appendix provides basic guidelines for configuring the Veritas Cluster Server (VCS) in a Subscriber Manager cluster installation. It assumes basic knowledge of the VCS environment; it does not replace the VCS user guide. This appendix does not cover installation of the cluster or of the Subscriber Manager cluster agents.

This appendix lists the software and hardware system requirements for the VCS. It also describes how to configure the Subscriber Manager cluster using the VCS configuration tools. Most of the examples are based on using the Java Veritas Manager GUI. However, you can perform the operations by using the Veritas command-line utilities.

The Subscriber Manager supports Veritas Cluster Server versions 5.x and 6.0 on Red-Hat Linux machines.

• Veritas Cluster Servers, page E-2

• Configuring Subscriber Manager Cluster Resources, page E-6

• Adding Subscriber Manager Cluster Resources, page E-11

• Useful Operations, page E-20

• Linking the Resources, page E-23

• Verifying that the Service Group is Online, page E-24

• SNMP Support, page E-25

• Configuring the SnmpConsole Attribute, page E-28

• Examples, page E-29

E-1vice Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Veritas Cluster Servers

Veritas Cluster ServersThis section consists of these topics:

• Veritas Cluster Server System Requirements, page E-2

• Veritas Cluster Server Nodes on Remote Sites, page E-2

• Replication Configuration Guidelines, page E-3

Veritas Cluster Server System RequirementsFor your convenience, the following Veritas Cluster Server System Requirements are extracted from the Symantec website:

http://www.symantec.com/

• Supported Platforms:

Red Hat Linux 5.5 and later, or 6.x

Centos 5.5 and later or 6.x

• Networking:

Public Network: 1G Ethernet

Private Network: 1G Ethernet

• Ethernet Controllers:

Requires at least three independent Ethernet connections per system

• Memory:

Each Veritas Cluster Server system requires at least 128 MB of RAM (256 MB of RAM is recommended)

• Supported Server Hardware:

Please refer to http://www.symantec.com/business/support/index.jsp or contact your Symantec sales representative for the latest list of certified server hardware.

– Red Hat Linux 5.5 and later, or 6.0

– Centos 5.5 and later, or 6.x

• Supported Storage Hardware:

Please refer to http://www.symantec.com/business/support/index.jsp or contact your Symantec sales representative for the latest list of certified storage hardware.

– Sun

– Red Hat Linux

Veritas Cluster Server Nodes on Remote SitesVeritas Cluster Server nodes establish heartbeat links, which communicate using the Low Latency Transport (LLT) Ethernet/dlpi protocol. The nodes transmit Ethernet broadcasts. The nodes must be on the same broadcast network. Each heartbeat link can support a separate Layer 2 switch.

E-2Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Replication Configuration Guidelines

The distance between Veritas Cluster Server nodes depends a number of factors including LLT network connectivity, latency, and performance. LLT requires Direct Layer 2 low latency connections that have a maximum round-trip time of 500 milliseconds. You must design large campus clusters, or metropolitan area clusters, to provide two completely separate paths for heartbeat to prevent a single fiber optic or fiber bundle failure from removing the heartbeat links.

Although the database replication network uses IP as its transport, it must have two separate connection paths between the nodes that provide at least 10Mbps for the subscriber data replication.

When planning a Subscriber Manager Cluster topology in which the nodes are at a distance from each other, please consult Veritas support.

Replication Configuration Guidelines• Replication Scheme Setup, page E-3

• Replication Network Configuration, page E-3

• Veritas Cluster Server Configuration Guidelines, page E-5

Replication Scheme Setup

After the replication network has been set up (as described in the “Replication Network Configuration” section on page E-3), you must implement the replication scheme in the database. Implement the replication scheme by using the p3db CLU:

>p3db --set-rep-scheme

This operation configures the database to send every subscriber-data update to the peer machine.

If the setup operation fails because an existing replication scheme is already established, run the following CLU to drop the previous replication scheme. Then implement the new scheme:

>p3db --drop-rep-scheme

Start the replication agent by configuring and running the VCS agent of the replication agent or by running the p3db --rep-start CLU.

Replication Network Configuration

Plan carefully the configuration of the replication private network between the two Subscriber Managers of the cluster. This section describes guidelines for performing the configuration.

The Subscriber Manager database replication agent uses hostnames to implement fail-over between the two replication NICs. The agent uses the first IP address of the hostname supplied to the agent to connect to the other agent. If the connection fails and cannot be reconstructed on the first IP, the replication agent tries the next IP addresses assigned to this hostname, and so on.

Editing the /etc/hosts file to assign hostnames to IP addresses.

You must use the predefined hostnames SM_REP1 and SM_REP2 as the hostnames for replication.

Note In the operating system configuration files, verify that the /etc/hosts file is used before using a name server.

Example:

E-3Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Replication Configuration Guidelines

Figure E-1 illustrates a replication network.

Figure E-1 Veritas Replication Network Configuration

To configure the replication network shown in Figure E-1, do the following:

• Configure the IP addresses of each of the replication NICs (each in a different network). In this example, the IP addresses of the Machine1 replication NICs are 10.1.1.1 and 10.2.1.1.

• Assign a hostname SM_REP1 to both of the local replication NIC IP addresses. In this example, the hostname SM_REP1 is assigned to the IP addresses of the replication NICs on Machine1. In the /etc/hosts file, also assign the local hostname (Machine1) to the local replication NICs. Ensure that there are no empty lines between the lines containing the local hostname.

• Assign a hostname SM_REP2 to both of the remote replication NIC IP addresses. In this example, the hostname SM_REP2 is assigned to the IP addresses of the replication NICs of Machine2

• The /etc/hosts file on Machine1 should appear as follows:

127.0.0.1 localhost1.1.1.1 Machine1 loghost10.1.1.1 Machine1 SM_REP1 REP_1_NIC_110.2.1.1 Machine1 SM_REP1 REP_1_NIC_210.1.1.2 SM_REP2 REP_2_NIC_110.2.1.2 SM_REP2 REP_2_NIC_2

• The /etc/hosts file on Machine2 should appear as follows:

127.0.0.1 localhost1.1.2.1 Machine2 loghost10.1.1.2 Machine2 SM_REP2 REP_2_NIC_110.2.1.2 Machine2 SM_REP2 REP_2_NIC_210.1.1.1 SM_REP1 REP_1_NIC_110.2.1.1 SM_REP1 REP_1_NIC_2

Public networkVIP 1.1.3.1

Heartbeat network

Replcation Network

10.1.1.1 10.1.1.2

10.2.1.1 10.2.1.2

SM_REP1 SM_REP2

Machine 1 Machine 2

1.1.1.1 1.1.2.1

3036

84

REP_1_NIC_1 REP_1_NIC_2

REP_2_NIC_1 REP_2_NIC_2

E-4Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Replication Configuration Guidelines

Note When configuring the /etc/hosts file on both the primary and secondary machines, you must list all entries for a particular host sequentially. This is particularly important when deploying two NICs in each machine for replication redundancy.

Note Ensure that the system uses the /etc/hosts file before it performs DNS or any other name service operation.

Veritas Cluster Server Configuration Guidelines

The following procedures assume that the listed operations are performed before starting the VCS configuration:

• Installation of the VCS on both machines. As part of this installation, the following tasks must be completed:

– Each machine is given a hostname, which is used as the system name for the VCS configuration.

– The machines are configured to recognize each other’s hostname.

• An IP address is allocated for the cluster (hereafter, the cluster’s IP).

• The Subscriber Manager and the Subscriber Manager database are installed on both machines.

• The Subscriber Manager VCS agents are installed on each machine.

• The VCS manager Java console is installed on the administrator PC.

Note that in a Subscriber Manager cluster, two Subscriber Manager machines are connected to each other in a fully redundant way. The connection uses four cables, two for the VCS heartbeat mechanism, and two for the Subscriber Manager database replication mechanism. Each machine is connected to the network by way of one of two redundant NICs. To access the cluster, you should use the cluster IP address, which is a virtual IP managed by the VCS. For management operations, you should use the local IP address of each machine.

E-5Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Configuring Subscriber Manager Cluster Resources

Configuring Subscriber Manager Cluster ResourcesTo configure the VCS with the Subscriber Manager cluster resources, perform the procedures described in the following sections.

• Adding Clusters, page E-6

• Adding Service Groups, page E-7

• Setting Auto-start, page E-8

Adding Clusters

Step 1 Open the VCS cluster manager Java console by choosing Start > Programs > Veritas Cluster Manager > Cluster Manager (Java console).

Step 2 Add a new cluster by choosing File > New Cluster (Figure E-2).

Figure E-2 Cluster Monitor: New Cluster

Step 3 Configure the cluster (Figure E-3).

Figure E-3 Adding a Cluster

• Cluster Alias—Cluster name

• Host name—One of the machine's IP addresses or hostname. Do not use the VIP here.

Step 4 Log in to the cluster.

E-6Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Adding Service Groups

Adding Service Groups

Step 1 In the cluster explorer, from the service group tab, right-click the cluster, and choose Add Service Group.

The Add Service Group window appears as shown in Figure E-4.

Figure E-4 Adding a Service Group

Step 2 Enter a name for the service group.

Step 3 Add the two machines as part of the service group and define their priority in the cluster.

Step 4 Click OK.

E-7Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Setting Auto-start

Setting Auto-startThis section describes how to set the auto-start parameters that specify which machine will start after a boot of both nodes. If you do not set these parameters, when both nodes boot, the cluster remains offline.

Step 1 From the service group display, click Show All Attributes..

Step 2 Ensure that both nodes are defined in the AutoStartList (Figure E-5 and Figure E-6).

Figure E-5 AutoStart List

Figure E-6 AutoStart List Values

E-8Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Setting Auto-start

Step 3 Specify which node will start by defining the AutoStartPolicy parameter (Figure E-7 and Figure E-8).

Figure E-7 AutoStart Policy

Figure E-8 AutoStart Policy Values

E-9Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Setting Auto-start

Step 4 Ensure that the AutoStart parameter is set to true (if false, both nodes will come up as standby) (Figure E-9 and Figure E-10).

Figure E-9 AutoStart

Figure E-10 AutoStart Values

E-10Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Adding Subscriber Manager Cluster Resources

Adding Subscriber Manager Cluster ResourcesThis section describes how to add the various Subscriber Manager cluster resources.

• Adding Resources—General Guidelines, page E-11

• Adding Network NICs, page E-12

• Adding Network VIPs, page E-14

• Adding Subscriber Manager Resources, page E-15

• Adding Subscriber Manager Database Daemon Resources, page E-16

• Adding Subscriber Manager Database Replication Agent Resources, page E-17

Adding Resources—General Guidelines

Step 1 From the right-click menu of the service group, click Add Resource as shown in Figure E-11.

Figure E-11 Adding Resources - General Guidelines

The Add Resource screen appears as shown in Figure E-12.

Figure E-12 Adding MultiNICA Resource: Select MultiNICA

E-11Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Adding Network NICs

Step 2 On the Add Resource screen, from the Resource Type drop-down list, choose the resource type and enter a name for the resource.

Step 3 Configure required attributes.

Step 4 When you are finished, click OK.

Adding Network NICsYou must configure the network NICs because the Veritas will automatically push a virtual IP on the online cluster's element.

Step 1 Decide which two network interfaces to use for the network connection.

Step 2 Add a MultiNICA resource called Network-NICs to the service group.

Step 3 Define the Device and NetMask parameters.

• Device—Write the names of the Network NICs in the KEY column and their corresponding IP addresses in the VALUE column.

Note Use the LOCAL option and configure each machine separately because the IP addresses are different in each machine.

In the following illustration, bge0 and bge3 are the network NICs (Figure E-13).

Figure E-13 Adding Network NIC: Device Attribute 1

E-12Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Adding Network NICs

Figure E-14 Adding Network NIC: Device Attribute 2

• NetMask—Assign a relevant network mask. For example, you can specify 255.255.255.255 as a network mask (Figure E-15).

Figure E-15 Adding Network NIC: NetMask Attribute

Step 4 Click the Enabled and Critical attributes of the resource as shown in Figure E-16.

E-13Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Adding Network VIPs

Figure E-16 Adding Network NIC: Setting Attributes

Adding Network VIPsYou must configure the Network VIPs because the VERITAS will automatically set a virtual IP on the online cluster’s element.

Step 1 Select an IP address of the cluster.

Step 2 Add an IPMultiNIC resource called Network-VIP to the service group.

E-14Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Adding Subscriber Manager Resources

Step 3 Define the Address, NetMask, and MultiNICAResName parameters (Figure E-17).

• Address—Enter the Cluster IP address.

• NetMask—Enter the network-mask you want to use for this IP.

• MultiNICAResName—Enter Network-NICs to specify the relevant NICs.

Figure E-17 Adding Network VIP Resource

Step 4 Check the Enabled and Critical check boxes.

See Figure E-16

Adding Subscriber Manager Resources

Step 1 Import the SubscriberManager agent's type from the file /opt/VRTSvcs/bin/SubscriberManager/SubscriberManager.cf.

Step 2 Add a SubscriberManager resource called Subscriber Manager to the service group.

E-15Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Adding Subscriber Manager Database Daemon Resources

Step 3 Define the SmBinPathName and SmDebugLevel parameters (Figure E-18).

• SmBinPathName—Enter the path to the bin directory under the Subscriber Manager installation directory, for example, /opt/pcube/sm/server/bin/.

• SmDebugLevel—Enter a number between 1 and 4 to view debug messages. Enter 0 to disable debug messages.

Figure E-18 Adding Subscriber Manager Resource

Note When adding the following resources, you must check the Critical check box:MultiNICANetwork-VIPSM-ClusterSubscriber Manager database Deamon

Adding Subscriber Manager Database Daemon Resources

Step 1 Import the OnOnlyProcess agent's type from file /opt/VRTSvcs/bin/OnOnlyProcess/OnOnlyProcess.cf.

Step 2 Add an OnOnlyProcess resource called TimesTenDaemon to the service group.

E-16Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Adding Subscriber Manager Database Replication Agent Resources

Step 3 Define the OnlineCmd, PathName, and Arguments parameters (Figure E-19).

• OnlineCmd—Enter the Subscriber Manager database Daemon start command: /etc/init.d/tt_pcubesm22 start.

• PathName—Enter the Subscriber Manager database Daemon process path, for example, /opt/pcube/lib/tt/TimesTen/pcubesm22/bin/timestend.

• Arguments—To view the arguments, run the following operating system command:

ps –eaf | grep timestend

• For example, the arguments can be: -initfd 13

Figure E-19 Adding Subscriber Manager Database Daemon Resource

Adding Subscriber Manager Database Replication Agent Resources

Step 1 Import the TimesTenRep agent's type from the file /opt/VRTSvcs/bin/TimesTenRep/TimesTenRep.cf.

Step 2 Add a TimesTenRep resource called ReplicationAgent to the service group.

E-17Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Sample main.cf File

Step 3 Define the TtBinPathName and TtDebugLevel parameters (Figure E-20).

• TtBinPathName—Enter the TimesTen bin directory path, for example, /opt/pcube/lib/tt/TimesTen/pcubesm22/bin.

• TtDebugLevel—Enter a number in the range of 1-4 for viewing debug messages. Enter 0 to disable the debug messages.

Figure E-20 Adding Subscriber Manager Database Replication Agent

Note Ensure that the Critical check box is unchecked when you add the ReplicationAgent resource.

Sample main.cf FileBelow is sample main.cf file:

include "types.cf"include "OnOnlyProcess.cf"include "SubscriberManager.cf"include "TimesTenRep.cf"

cluster SM-Cluster (UserNames = { admin = gJKcJEjGKfKKiSKeJH }Administrators = { admin })

system Machine1 ()

system Machine2 ()

group Bush (SystemList = { Machine1 = 2, Machine2 = 1 }

E-18Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Sample main.cf File

AutoStartList = { Machine1, Machine2 }AutoStartPolicy = Priority)

IPMultiNIC Network-VIP (Address = "1.1.3.1"MultiNICAResName = Network_NICNetMask = "255.0.0.0")

MultiNICA Network_NIC (Device @Machine1 = { bge0 = "1.1.1.1" }Device @Machine2 = { bge0 = "1.1.2.1" }NetMask = "255.0.0.0")

OnOnlyProcess TimesTenDaemon (OnlineCmd = "/etc/init.d/tt_pcubesm22 start"PathName = "/opt/pcube/lib/tt/TimesTen/pcubesm22/bin/timestend"Arguments = " -initfd 13")

SubscriberManager SM (SmBinPathName = "/opt/pcube/sm/server/bin")

TimesTenRep ReplicationAgent (Critical = 0TtBinPathName = "/opt/pcube/lib/tt/TimesTen/pcubesm22/bin")

Network-VIP requires Network_NICSM requires Network-VIPSM requires ReplicationAgentSM requires TimesTenDaemon

// resource dependency tree//// group Bush// {// SubscriberManager SM// {// IPMultiNIC Network-VIP// {// MultiNICA Network_NIC// }// TimesTenRep ReplicationAgent// OnOnlyProcess TimesTenDaemon// }// }

E-19Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Useful Operations

Useful OperationsThe following sections describe operations that are useful for managing the VCS.

• Logging into the Cluster, page E-20

• Saving the Configuration, page E-20

• Closing the Configuration, page E-20

• Importing Types, page E-21

Logging into the ClusterAfter you add a cluster, you are required to log in to the cluster.

Step 1 Click the login icon ( ).

A login window appears.

Step 2 Log in with the initial user and password.

The initial user is admin, the initial password is password.

Saving the ConfigurationBefore exiting the VCS, be sure to save your configuration; otherwise, your configuration will be lost.

Step 1 Click the icon, or choose File > Save Configuration.

Closing the ConfigurationBefore exiting the VCS, ensure your configuration is closed. Some operations (like rebooting the system) could fail or a configuration conflict could occur if the configuration is in read/write mode.

Step 1 Click the icon, or choose File > Close Configuration.

Before exiting the VCS, ensure your configuration is closed. Some operations (like rebooting the system) could fail or a configuration conflict could occur if the configuration is in read/write mode.

E-20Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Importing Types

Importing TypesTo configure the Subscriber Manager Veritas agents, first you must import the type file of these agents.

Step 1 From the File menu, choose Import Types.

A navigation window appears as shown in Figure E-21.

Figure E-21 Importing Types

The window enables you to navigate through one of the cluster-system's file system (Figure E-22).

Step 2 Go to the agent directory under /opt/VRTSvcs/bin/<agent-dir>.

In the agent directory, there is a file with a .cf extension.

Figure E-22 Importing Types: Select File

E-21Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Importing Types

Step 3 Select the file with the .cf extension.

The resource parameters are shown in Figure E-23.

Figure E-23 Importing Types: Resource Parameters

E-22Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Linking the Resources

Linking the ResourcesWhen you link resources, you establish the sequence by which resources initialize and shutdown. For example, the Network-VIP resource does not start its initialization process until the Network-NICs resource is set. Additionally, the Network-NICs agent shutdown process does not start until the Network-VIP agent finishes its shut-down operation.

Step 1 Select the service group and enter the Resources tab.

Step 2 To link two resources, click once on one resource, pull the line to the second resource, and click once over the icon of the second resource.

The final links should look like those in Figure E-24.

Figure E-24 Linked Resources

E-23Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Verifying that the Service Group is Online

Verifying that the Service Group is Online

Step 1 Check that all of the resources are online/offline according to the system and the resource type.

Note The Subscriber Manager database Daemon, the NICs, and the Subscriber Manager database Replication Agent should all be online on all of the systems.

The state should be similar to the one shown in Figure E-25.

Figure E-25 Verifying Service Group is Online

E-24Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server SNMP Support

SNMP SupportVCS provides a method for notifying you of important events such as a resource or system fault. For this purpose, VCS supplies a NotifierMngr agent that enables the reception of messages from VCS and the delivery of those messages to SNMP consoles. This section describes configuring NotifierMngr in order to enable SNMP support.

• Configuring NotifierMngr, page E-25

• Adding NotifierMngr Resource, page E-25

• Configuring the NotifierMngr Attributes, page E-26

Configuring NotifierMngrAdd and configure NotifierMngr using either the command line or the Cluster Manager Java Console.

When started from the command line, the VCS does not control the Notifier process.

For optimal results, use the NotifierMngr agent that is bundled with VCS to configure Notifier as part of a highly available service group. Then you can activate, monitor, and shutdown the Notifier.

The following sections describe how to configure the Notifier by using the Cluster Manager Java Console.

Adding NotifierMngr Resource

Step 1 Add a NotifierMngr resource called Notifier to the service group (Figure E-26).

Figure E-26 Adding Notifier Manager Resource: Add Resource

E-25Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Configuring the NotifierMngr Attributes

The Add Resource screen appears as shown in Figure E-27.

Figure E-27 Adding Notifier Manager Resource: Select NotifierMngr

Step 2 From the Add Resource screen, choose NotifierMngr as the resource type.

Configuring the NotifierMngr AttributesAfter adding the NotifierMngr resource, configure its attributes.

Step 1 Select NotifierMngr as the resource type.

The Properties View: Notifier screen appears as shown in Figure E-28.

Figure E-28 Configuring Notifier Manager Attributes

E-26Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Configuring the NotifierMngr Attributes

Step 2 Define the SnmpConsoles, SnmpdTrapPort, and SnmpCommunity parameters.

• SnmpConsoles—Specify the machine name of the SNMP manager and the severity level of messages to be delivered to the SNMP manager. The severity levels of messages are Information, Warning, Error, and SevereError. Specifying a severity level for messages generates delivery of all messages of equal or higher severity.

• SnmpdTrapPort—Specify the port to which the SNMP traps are sent. The value specified for this attribute is used for all consoles if more than one SNMP console is specified. The default is 162.

• SnmpCommunity—Specify the community ID (a string scalar) for the SNMP manager. The default is public.

E-27Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Configuring the SnmpConsole Attribute

Configuring the SnmpConsole AttributeThe SnmpConsole attribute specifies the IP addresses to which you want the SNMP traps sent. You can specify different trap severity for each IP address (Figure E-29).

Figure E-29 Configuring SNMP Console Attributes

Linking to IPMultiNIC

Viewing Traps

After adding and configuring NotifierMngr, it sends traps, according to the configured severity, to the destinations configured by the SnmpConsole Attribute.

View these traps using SNMP trap viewer/MIB Browser (for example, AdventNet MibBrowser).

For a complete list of traps/severities, see Chapter 10 of the VERITAS Cluster Server User Guide.

Step 1 Using the resources viewer, connect the Notifier to the Network-VIP resource so that it will be online after the VIP.

For more information, see Figure E-20 in Adding Subscriber Manager database Replication Agent Resources.

E-28Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Examples

ExamplesFigure E-30 shows an instance in which the cluster is 1nfigured, and all resources are working.

• Network-NICs, ReplicationAgent and Subscriber Manager database Daemon are online on both machines.

• Network-VIP and Subscriber Manager are online on the 2nd Machine, which is currently Active.

Figure E-30 Properly Configured Cluster

E-29Cisco Service Control Subscriber Manager User Guide

Appendix E Veritas Cluster Server Examples

Figure E-31 shows a cluster in which the VCS on one side (Server 1) is disabled, which indicates the following consequences:

• The GUI indicates that PQB_AL_RACK27-HP3 is AutoDisabled.

• ReplicationAgent and Subscriber Manager database Daemon are online on both machines because they are configured as OnOnly processes.

To recover, you should start the VCS on “PQB_AL_RACK27-HP3” by issuing the /opt/VRTSvcs/bin/hastart command.

Figure E-31 Improperly Configured Cluster

E-30Cisco Service Control Subscriber Manager User Guide