Installing a Gateway With an Embedded Database in a Veritas High Availability Configuration

Transcription

1 CHAPTER 10 Installing a Gateway With an Embedded Database in a Veritas High Availability Configuration This chapter explains how to install, upgrade, or roll back a Cisco Prime Network 3.9 gateway in a Veritas local redundancy and geographical redundancy high availability (HA) configuration. The Cisco Prime Network installation includes the hardware configuration, OS installation, and installation of the Oracle and Cisco Prime Network applications. In addition to these tasks, an HA solution includes installing the Veritas Software Foundation, configuring Veritas clusters, and configuring additional hardware and OS components. An HA installation requires these roles: Veritas consultant Responsible for installing the Veritas applications (Veritas Volume Manager and Veritas Cluster Server for local redundancy; Veritas Volume Replicator for geographical redundancy). This role requires a high level of Veritas expertise. The Veritas consultant might be asked to assist with setting up external disks and configuring the OS. Veritas administrator Once the Veritas software installation is complete, the Veritas administrator performs ongoing configuration and administration of the cluster, including adding service groups and resources. This chapter highlights the portions of the installation that require the skills of the Veritas consultant or administrator. Topics covered in this chapter includes: Veritas Gateway HA System Requirements, page 10-2, page Upgrading to Cisco Prime Network 3.9 in a Veritas Gateway HA Environment, page Rolling Back to an Earlier Version in a Veritas Gateway HA Environment, page Note The Oracle filenames, paths, and directories listed in this chapter are specific to Oracle 11g. Cisco Prime Network 3.9 also supports Oracle 10g. If you are using Oracle 10g, the filenames and paths will differ. The mount points are identical for Oracle 10g and 11g. 10-1

2 Veritas Gateway HA System Requirements Chapter 10 Note A Cisco Prime Network base license must be registered and activated within 120 days of installation or upgrade for each server in the Cisco Prime Network gateway HA configuration. If there are no valid license files on the gateway server, Cisco Prime Network acts as an evaluation version. This means that it has full functionality for 120 days after installation, and then it expires and UI connections will be disallowed. For Cisco Prime Networklicensing information, see the Cisco Prime Network 3.9 Administrator Guide. Veritas Gateway HA System Requirements This section explains the system requirements for a Veritas-based HA configuration. Veritas HA Gateway Requirements All gateways that will be configured for Veritas-based HA must meet the general Cisco Prime Network gateway requirements specified in System Requirements, page

3 Chapter 10 Veritas Gateway HA System Requirements Veritas Gateway HA Hardware Requirements for Local Redundancy Figure 10-1 illustrates the hardware requirements for the Cisco Prime Network gateway in a dual-node, local redundancy HA solution. Figure 10-1 Cisco Prime Network Local Redundancy HA Hardware Configuration Dual Gigabit Ethernet connections to different switches on LAN backbone for network and backup heartbeat Cisco Prime Network gateway 2 internal disks (1 OS + 1 mirror) Dual Gigabit Ethernet crossover connections for heartbeat Oracle database server 2 internal disks (1 OS + 1 mirror ) Dual connections from each server to the external disk storage unit External storage Database: 1 or more data volumes 1 archive volume 1 redo log volume 1 backup volume (embedded database only) 1 SRL volume, all with mirroring/raid protection Cisco Prime Network: 1 ANA volume with mirroring/raid protection 1 SRL volume with mirroring/raid protection The gateway requires: 2 servers of identical configuration that meet the Cisco Prime Network gateway hardware requirements, plus the following additional hardware requirements: 2 x internal hard disks with at least 73 GB storage. 4 x Gigabit Ethernet ports. 2 to 4 x SCSI/SAS/fiber connectors (depending on the external disk configuration). External disk storage that: Is supported by Veritas Cluster Server (VCS). Contains enough physical disks to provide the following volumes: 1 volume for Cisco Prime Network. 1 volume for the Oracle application and data file(s). 1 volume for Oracle redo logs. 1 volume for Oracle archives. 10-3

4 Veritas Gateway HA System Requirements Chapter 10 1 volume for Oracle backups (only if you are using an embedded database). Note The database administrator determines the size needed for Oracle redo logs and archives. 1 or more volumes for additional data files (optional). Note Oracle disk requirements depend on how much event history the operator wants to retain. See Creating and Configuring an Oracle Database, page 5-2 Contains enough physical disks to implement mirroring or hardware RAID protection for all data and log disks. Contains enough physical disks to ensure optimal performance. It is recommended that Oracle data and logs reside on separate physical disks. Enough SCSI/SAS/fiber connections and cables to implement two connections between each server and each disk external storage unit. 2 x Gigabit Ethernet cables (for LAN connections). 2 x Gigabit Ethernet crossover cables (for the heartbeat). Servers The local cluster consists of two servers. Because Cisco Prime Network3.9 supports running the Oracle database application on a separate server from the gateway, both servers in the cluster are active during normal operation. One server runs the Cisco Prime Network gateway application; the other server runs the Oracle database application. Each server provides backup for the other in case of failure. Connections The Veritas Cluster Server uses Group Membership Services/Atomic Broadcast (GAB) and Low Latency Transport (LLT) to determine cluster membership and maintain communication via heartbeats. The two servers that form the cluster exchange heartbeats over the dual crossover Ethernet cables that connect them. If the connection between the servers fails, the heartbeat is sent across the LAN backbone. For added redundancy, the two servers can be connected to the LAN on separate segments. Storage The local redundancy HA solution requires internal and external storage for the two servers. Internally, each server must contain dual mirrored internal disks with at least 73 GB of storage. The Veritas Volume Manager performs the mirroring. For external disk storage, the dual-node configuration requires five or more shared volumes (depending on how many Oracle data files you want to keep). The volumes must be available for mounting on either of the two servers. The external storage unit housing the disks for these volumes must be supported by the VCS. Beyond these minimum requirements, the data must be protected from disk failure. The five or more shared volumes can be provided to the servers in various ways; the physical implementation is transparent. See the Veritas product documentation for the latest list of supported devices. 10-4

5 Chapter 10 Veritas Gateway HA System Requirements If you use Just a Bunch of Disks (JBOD), redundancy requires that the external storage consist of six to ten separate disks with capacities large enough to provide the necessary volumes. The Veritas Volume Manager (VxVM) provides mirroring between each pair of disks. Oracle data and logs must reside on separate physical disks. The need to create additional Oracle data volumes on a separate disk is determined by the size and performance of the disks. If you use external storage that supports hardware RAID, five or more shared volumes are required; the disk configuration is transparent. Oracle performance requirements can be met with the hardware and without having to place the data and logs on separate physical disks. The need to create additional Oracle data volumes is determined by performance considerations; the size of the initial data volume is not limited by physical disk sizes. Veritas Gateway HA Software Requirements for Local Redundancy For local redundancy, the cluster consists of two nodes. Each node has the following software requirements: 1 x Prime Network Starter Kit. 1 x Veritas Storage Foundation Standard HA Solaris v5.1 (licensing is either per server or per CPU), including: Veritas Cluster Server (VCS) Release 5.1. Veritas Volume Manager (VxVM) Release 5.1. Veritas Cluster Server Oracle Agent Release 5.1. Solaris 10 operating system that meets the Cisco Prime Network gateway software requirements, plus all recommended Solaris 10 patches. Veritas Gateway HA Network Requirements for Local Redundancy Two additional IP addresses are required for the cluster logical addresses of Cisco Prime Network and Oracle. Veritas Gateway HA Hardware Requirements for Geographical Redundancy Figure 10-2 illustrates the hardware requirements for the Cisco Prime Network gateway in a geographical redundancy HA solution. 10-5

6 Veritas Gateway HA System Requirements Chapter 10 Figure 10-2 Cisco Prime Network Geographical Redundancy HA Secondary Site Hardware Configuration Dual Gigabit Ethernet connections to different switches on LAN backbone for network and heartbeat Cisco Prime Network gateway 1 to 2 internal disks (1 OS + 0 or 1 mirror) Dual connections from the server to the external disk storage unit External storage Database: 1 or more data volumes 1 archive volume 1 redo log volume 1 backup volume (embedded database only) 1 SRL volume, all with mirroring/raid protection Cisco Prime Network: 1 ANA volume with mirroring/raid protection 1 SRL volume with mirroring/raid protection The hardware requirements for a single-node, geographical redundancy gateway at the secondary site are in addition to the hardware requirements for the primary site. The secondary gateway requires: 1 server that meets the Cisco Prime Network gateway hardware requirements, plus 2 Gigabit Ethernet ports. External disk storage that: Is supported by VCS. Contains enough physical disks to provide the following volumes: 1 volume for Cisco Prime Network. 1 volume for the Oracle application and data file(s). 1 volume for Oracle redo logs. 1 volume for Oracle archives. 1 volume for Oracle backups (only if you are using an embedded database). Note The database administrator determines the size needed for Oracle redo logs and archives. 1 or more volumes for additional data files (optional). 10-6

7 Chapter 10 Veritas Gateway HA System Requirements Note Oracle disk requirements depend on how much event history the operator wants to retain. See Creating and Configuring an Oracle Database, page volumes for storage replicator logs (SRLs; two per site) that meet the SRL sizing requirements. (See SRL, page 10-8 for the recommended sizes.) Contains enough physical disks to implement mirroring or hardware RAID protection for all data and log disks, including the SRLs at both sites (if you are using Veritas Volume Replicator [VVR]). It is recommended that SRLs (for VVR) reside on separate physical disks. For more information, see the VVR documentation. Contains enough physical disks to ensure optimal performance. It is recommended that Oracle data and logs reside on separate physical disks. Contains disks with enough space that they can be divided into volumes with sizes identical to the volumes at the local site. Is supported by VCS Global Cluster, if you are using storage-based replication instead of VVR. Hardware infrastructure for storage-based data replication, if you are using storage-based replication instead of VVR. Enough SCSI/SAS/fiber connections and cables to implement two connections between each server and each disk external storage unit. 2 x Gigabit Ethernet cables (for LAN connections). Server The secondary site requires only a single server, which runs both the Cisco Prime Network gateway and the Oracle database. Connections For the global cluster, VCS uses Low Latency Transport (LLT) to determine cluster membership and maintain communication via heartbeats. The two clusters that form the global cluster exchange heartbeats over the IP network. For redundancy, the servers are connected to the LAN on separate segments. Storage The geographical redundancy HA solution requires internal and external storage for the remote server. Internally, the server must contain a single internal disk with at least 73 GB of storage. For external disk storage, the single-node configuration requires five or more shared volumes (depending on how many Oracle data files you want to keep). The volumes must be available for mounting on the single server. To allow data replication, the volume sizes at the two sites must be identical. If you are using VVR, each site also requires an additional two volumes (one each for the Prime-Network and Oracle disk groups) for SRLs. The external storage unit housing the disks for these volumes must be supported by VCS. Even though the secondary site is considered temporary, if the primary site fails, the storage at the secondary site becomes the primary copy of the Cisco Prime Network and Oracle data. Therefore, the data must be protected from disk failure. According to the VVR documentation, SRLs must be mirrored. As with the primary site, you determine the level of protection or redundancy for the external disks. 10-7

8 Veritas Gateway HA System Requirements Chapter 10 If you use JBOD disks, the SRLs must reside on separate physical disks. If you use external storage that supports hardware RAID, SRL performance requirements can be met with the hardware and without having to place the SRL on a separate physical disk. You can implement storage-based data replication (either SAN or NAS) between the sites. The requirements for storage-based data replication are in addition to the requirements discussed previously. Replication You can implement data replication between the primary and secondary sites in one of the following ways: Software-based replication (VVR). Storage-based replication (NAS or SAN) External storage supporting replication and the accompanying hardware infrastructure must be in place. This method is more expensive than software-based replication, but provides better performance. SRL A storage replicator log is a circular buffer of write for a replicated volume group (RVG). SRLs store outstanding write until system and network availability sends them across the network to the secondary site. The required size for an SRL is calculated based on the rate of disk writes, network availability, and the length of potential network outages. Cisco Prime Network uses two RVGs one for the Cisco Prime Network data and one for the Oracle data. The following are the recommended SRL sizes, assuming a 24-hour outage: Prime-Network RVG SRL volume size: 20 GB Oracle RVG SRL volume size: 50 GB It is recommended that you reserve extra disk space for future growth. For example, if data reservation is required for more than a 24-hour outage, the SRL size increases linearly. The Oracle SRL volume size might also change according to the Oracle archiving mode. If ARCHIVELOG mode is used, the amount of data being written increases substantially, and the Oracle SRL volume must be adjusted accordingly. After the system is installed and activated, see the Veritas Volume Replicator Advisor User s Guide from Symantec publications to determine the specific SRL log size requirements. Redundancy The single-node cluster is intended to be used only if the primary site fails. Assuming the single-node cluster will be in use for a short time until the primary site is restored, there is no requirement for redundancy, other than mirroring the disk that contains the Cisco Prime Network and Oracle data. However, if the single-node cluster might operate for an extended period of time, or if you want to add redundancy, the cluster can be augmented at the secondary site as follows: Use a dual-node cluster to protect against server failure. Mirror the internal disk to protect against internal disk failure. Add a second connection to each external disk unit to protect against connector failure. 10-8

9 Chapter 10 Veritas Gateway HA System Requirements Veritas Gateway HA Software Requirements for Geographical Redundancy For geographical redundancy, the cluster consists of two nodes at the local site and a single node at the remote site, for a total of three nodes. Each node has the following software requirements: 1 x Prime Network Starter Kit. 1 x Storage Foundation Enterprise HR/DR for Oracle, Solaris v5.1 (licensing is either per server or per CPU), including: Veritas Cluster Server (VCS) Release 5.1. Veritas Volume Manager (VxVM) Release 5.1. Veritas Cluster Server Oracle Agent Release x Veritas Cluster Server Global Cluster option, Solaris. 3 x Veritas Volume Replicator (VVR) Release 5.1 (if you are using software-based replication), or software licenses for storage-based data replication (SAN or NAS). Solaris 10 operating system that meets the Cisco Prime Network gateway software requirements, plus all recommended Solaris 10 patches. Veritas Gateway HA Network Requirements for Geographical Redundancy IP Addresses Two additional IP addresses are required for the wide area connection (WAC) resources used to implement the VCS global cluster one IP address for the local cluster, and one IP address for the remote cluster. An additional IP address is required for a cluster logical address on the remote cluster. Cisco Prime Network Ports and Protocols VCS Ports and Protocols Ports and protocols must be open between the primary and secondary sites to allow communication during a site-to-site failover. Communication between the primary and secondary sites includes: Northbound applications < > gateway Gateway < > units Units < > units Units < > network elements For more information, see Cisco Prime Network Ports Usage, page 2-8. To implement the global cluster, VCS uses the WAC to maintain contact between the clusters. By default, the WAC uses TCP 14155, and the VCS service uses TCP (See Table 10-1.) These ports must remain open between the primary and secondary sites. See the VCS documentation before changing these ports. 10-9

10 Veritas Gateway HA System Requirements Chapter 10 Table 10-1 Port Number TCP TCP Open Ports Between Primary and Secondary Sites Description WAC VCS service VVR Ports and Protocols VVR transmits heartbeats and data between the primary and secondary sites. Heartbeats always use UDP, while data uses UDP (default) or TCP. Table 10-2 lists the default port for each protocol, which must be open between the sites if VVR is used for data replication. You can change the default ports as described in the VVR documentation. Table 10-2 Default Ports for UDP and TCP Port Number Description Data Replication Using UDP UDP 4145 Prime Network-approved port for heartbeat communication between the primary and secondary. TCP 8199 Prime Network-approved port for communication between the vradmind daemons on the primary and secondary. TCP 8989 Communication between the in.vxrsyncd daemons, which are used for differences-based synchronization. UDP anonymous ports (OS-dependent) Ports used for each primary-to-secondary connection for data replication between the primary and secondary. One data port is required on each host. Data Replication Using TCP UDP 4145 IPrime Network-approved port for heartbeat communication between the primary and secondary. TCP 4145 IPrime Network-approved port for the TCP listener port. TCP 8199 IPrime Network-approved port for communication between the vradmind daemons on the primary and secondary. TCP 8989 Communication between the in.vxrsyncd daemons, which are used for differences-based synchronization. TCP anonymous ports Ports used for each primary-to-secondary connection for data replication between the primary and secondary. One data port is required on each host

11 Chapter 10 Installing Cisco Prime Network 3.9 in a Veritas Gateway HA Environment Before starting the installation in Veritas Gateway High Availability environment, check the requirements in Veritas Gateway HA System Requirements, page This section describes how to install Cisco Prime Network in the following HA configurations: For local redundancy, a dual-node cluster is installed at the primary site (see Figure 10-3). For geographical redundancy, an additional single-node cluster is installed at the remote site (see Figure 10-4) and with units (Figure 10-5). In the following figures, the servers represent: Primary site: P1 Primary Cisco Prime Network gateway server/backup Oracle server. P2 Primary Oracle server/backup Cisco Prime Network gateway server. Secondary site: S1 Cisco Prime Network gateway and Oracle server

12 Chapter 10 Figure 10-3 Veritas HA Local Redundancy Setup Dual-node cluster External storage Server P1 (primary Cisco Prime Network) Heartbeat Server P2 (primary Oracle) Cisco Prime Network gateways WWW GUI clients Web clients Customer OSS/BSS Cisco Prime Network units

13 Chapter 10 Figure 10-4 Veritas HA Geographical Redundancy Setup Primary site/ local cluster dual-node cluster Secondary site/remote cluster single-node cluster Server P1 (primary Cisco Prime Network) External storage Server P2 (primary Oracle) Replication Global heartbeat External storage Server S1 Cisco Prime Network gateways Cisco Prime Network gateway WWW GUI clients Web clients Customer OSS/BSS Cisco Prime Network units

14 Chapter 10 Figure 10-5 Veritas HA Geographical Redundancy Setup with Units Primary site/local cluster dual-node cluster + units Secondary site/remote cluster single-node cluster + units Server P1 (primary Cisco Prime Network) External storage Cisco Prime Network gateways Server P2 (primary Oracle) Replication Global heartbeat External storage Server S1 Cisco Prime Network gateway Cisco Prime Network units WWW GUI clients Web clients Customer OSS/BSS Veritas Gateway HA Local Dual-Node Cluster Unless noted otherwise, all steps for the local dual-node cluster pertain to both local redundancy and geographical redundancy HA environments. Hardware Tip The steps in this section might require assistance from the Veritas consultant

15 Chapter 10 Configure the two servers as shown in Figure 10-1, including: Dual Gigabit Ethernet connections for the heartbeat. Dual connections to each external storage unit. Configure the external storage so that all disks or logical unit numbers (LUNs) are accessible from both servers in the cluster. The disk or LUN configuration depends on the type of storage. If you are using JBOD disks, provide enough physical disks to create the following volumes to satisfy the Oracle (and VVR) performance requirements. If you are using storage that supports hardware RAID, divide the physical disks into LUNs so that the following volumes can be created, configured to satisfy the Oracle (and VVR) performance requirements, and protected with RAID5, RAID1, or RAID10. You can create the Oracle volumes on a single LUN. The SRL volumes are relevant only if you are using geographical redundancy with VVR. Table 10-3 Size Requirements for Oracle Volumes Volume Minimum Size Comments Prime Network 50 GB Prime Network SRL See the SRL requirements. Oracle application and data files 10 GB Oracle redo logs 6.4 GB Oracle archives Contact your Cisco account representative to obtain the Cisco Prime Network Capacity Planning Guide. Additional Oracle data files (if used) Based on Cisco Prime Network alarm history needs; see the Capacity Planning Guide. Oracle backup See the Capacity Planning Guide. Note The backup partition is required only if you are using an embedded database. If you are not using an embedded database, it is up to the administrator to back up the database. Oracle SRL See the SRL requirements. Operating System Tip The steps in this section might require assistance from the Veritas consultant. Step 1 Step 2 Install the operating system and all recommended patches on both servers in the cluster. The installation on both servers must be identical. Once the operating system is installed, verify access to all external disks. Divide the internal disks as shown in Table It is recommended but not required that you place the individual directories in separate partitions

16 Chapter 10 Table 10-4 Partition Space (in MB) swap Standard amount of space, as per system configuration / Standard amount of space plus 6144 MB extra /opt Minimum 3072 MB /var (optional) Space for Veritas logs others (optional) Remaining space Step 3 Step 4 Step 5 Step 6 The Cisco Prime Network installation normally requires 1024 MB of additional free space under the root partition. With HA, a temporary copy of Cisco Prime Network is installed under the root partition, which requires an additional 5120 MB of free space, bringing the total free space requirement to 6144 MB. The Veritas software is normally installed under /opt, which requires a minimum of 3072 MB. You can add this amount to the root partition instead of creating a separate partition for /opt. The Veritas logs are normally saved under /var, which you can set up as a separate partition. Verify that neither server has a local partition mounted under /export/home. (During normal cluster operation, the server where Cisco Prime Network is running has the external Prime Network data volume mounted under /export/home; the server where Oracle is running has nothing mounted under /export/home.) Verify that the time is synchronized on both servers. As the root user, enter the following commands on both servers to create the mount points: # mkdir -p /export/home # cd /opt # mkdir db dbarch dbbackup dbdata dblogs The following mount points are created: /export/home /opt/db /opt/dbarch /opt/dbbackup (required only if you are using an embedded database) /opt/dbdata /opt/dblogs Veritas Software and Local Cluster Creation Tip The Veritas consultant should use the product documentation to perform the steps in this section. Step 1 Install the Veritas Storage Foundation HA or Enterprise HA with global cluster option (if you are using disaster recovery) on both servers in the local cluster. Veritas Volume Manager is used to manage the internal storage. It can also be used to manage the external storage if the external storage does not have its own volume management solution

17 Chapter 10 Step 2 Step 3 Step 4 Install the latest Veritas maintenance pack that contains the Veritas patches for Solaris. Install the Veritas High Availability Agent for Oracle. Use VCS to create and configure the local cluster: a. Create a new cluster. b. Set up the LLT heartbeat between the two servers. Disk Groups, Volumes, and Mirroring Tip The steps in this section might require assistance from the Veritas consultant. Step 1 Use Veritas Volume Manager (VxVM) to create two disk groups (one for Prime Network; one for Oracle or the embedded database) as defined in Hardware, page Use the volumes listed in Table If the disks are mirror-protected instead of RAID-protected, include a duplicate set of disks for the mirroring. Table 10-5 Disk Groups, Volumes, and Mount Points Disk Group Volume(s) Mount Point Comments Prime Prime Network /export/home Network Prime Network SRL (VVR only) Oracle or embedded database Oracle application and data files /opt/db Create the volumes using a block size of Oracle redo logs /opt/dblogs Mount the redo logs volume with Convert osync policy=direct. Oracle archives /opt/dbarch Additional Oracle data files (if used) /opt/dbdata Create the volumes using a block size of Oracle backup files /opt/dbbackup Required only when using an embedded database. Oracle SRL (VVR only) Step 2 Step 3 Use VxVM to set up mirroring between the two internal disks on both servers. If you are not using hardware that supports hardware RAID for the external disks, use VxVM to set up mirroring for the external disks (including SRLs). (This task takes a long time and can be deferred to a convenient time during the installation process.) Local Redundancy Dual-Node Cluster Worksheet Use the following worksheet to record all parameters necessary to configure the local dual-node cluster. The parameter names shown in italics will be requested during the actual HA installation

18 Chapter 10 Table 10-6 Parameters Required for the Local Dual-Node Cluster Parameter Name Local-Prime Network-SG-IP Local-Prime-Network-SG-netmask Local-Oracle-SG-IP Local-Oracle-SG-netmask Remote-single-node-IP Network-interface Prime-Network-disk-group Prime-Network-volume-block-device Oracle-disk-group-name Oracle-application-volume-block-device Oracle-archive-file-volume-block-device Oracle-data- volume-block-device Oracle-backup-volume- block-device Oracle-log-volume-block- device ORACLE_HOME Netlsnr-resource-name Prime-Network-IP-resource-name Description Logical IP address of the local cluster Prime Network service group. Netmask of the logical interface of the local cluster Prime-Network service group. Logical IP address of the local cluster Oracle service group. Netmask of the logical interface of the local cluster Oracle service group. Logical IP address of the remote single-node cluster. Name of network interface to which the logical IP address is added. The name must be identical on all servers. Example: bge0. Name of the disk group created with Veritas Volume Manager for the Prime-Network data. Example: anadg. Block device of the volume created for the Prime-Network data. Example: /dev/vx/dsk/anadg/anavol. Name of the disk group created with Veritas Volume Manager for the Oracle data. Example: oradg. Block device of the volume created for the Oracle application. Example: /dev/vx/dsk/oradg/oravol. Block device of the volume created for the Oracle archive logs. Example: /dev/vx/dsk/oradg/oraarchvol. Block device of the volume created for the Oracle data files. Example: /dev/vx/dsk/oradg/oradatavol. Block device of the volume created for the Oracle backup files for the embedded database. Example: /dev/vx/dsk/oradg/orabackupvol. Block device of the volume created for the Oracle redo log files. Example: /dev/vx/dsk/oradg/oralogsvol. Value of the $ORACLE_HOME environment variable, which is the root of the Oracle installation (not the home directory of the user oracle). Example: /opt/db/oracle/ora920. Name of the Netlsnr resource in the Oracle service group. Example: Netlsnr. Name of the IP resource in the Prime-Network service group. Example: ana_ip

19 Chapter 10 Table 10-6 Parameters Required for the Local Dual-Node Cluster (continued) Parameter Name Oracle-IP-resource-name Local-LDAP-URL Local-LDAP-prefix Local-LDAP-suffix Local-LDAP-SSL-usage Description Name of the IP resource in the Oracle service group. Example: ora_ip. Local LDAP server URL (if you are using LDAP authentication and geographical redundancy HA). Example: ldap:// :389. Local LDAP distinguished name prefix (if you are using LDAP authentication and geographical redundancy HA). Example: CN. Local LDAP distinguished name suffix (if you are using LDAP authentication and geographical redundancy HA). Example: CN=Users,DC=,DC=myldapserver,DC=local. Local Prime-Network-LDAP SSL protocol usage (if you are using LDAP authentication and geographical redundancy HA). The boolean value is true if the SSL protocol is used between Prime-Network and the LDAP server. The boolean value is false (the default) if SSL is not used. Local Cluster Configuration Tip The Veritas administrator should perform the steps in this section. Step 1 Use Cluster Manager to add two new service groups to the cluster: ana_sg for Prime-Network and oracle_sg for Oracle. You must use the exact names ana_sg and oracle_sg. Use the following settings: Use failover as the service group type for both service groups. Add both servers to each service group. Determine the server priority according to which server is the primary server for each service group: Service Group P1 Server Priority P2 Server Priority Prime-Network 0 1 Oracle 1 0 Set the resources in the service groups to critical. Note, however, that the resources are initially set to non-critical during the installation process and are made critical once the service groups are built. Step 2 Add the following aliases to the /etc/hosts file on P1 and P2: Local-Prime-Network-SG-IP ana-cluster-ana Local-Oracle-SG-IP ana-cluster-oracle 10-19

20 Chapter 10 Note If the IP address that you enter is not the default one, the database installation updates the hostname in the listener s files. Verify that /etc/hosts is updated with the correct IP address and hostname; the order is important. If more than one hostname is attached to the selected IP address, the first hostname is used. Step 3 To configure the Prime-Network service group, do the following: a. Add a resource of type NIC to the service group with the following configuration: Resource Type: NIC Key Attributes Critical False Type-Specific Attributes Device <network interface> Overridden Attributes None b. Enable the NIC resource. c. Add a resource of type DiskGroup to the service group with the following configuration: Resource Type: DiskGroup Key Attributes Critical False Type-Specific Attributes DiskGroup <Prime-Network disk group> Overridden Attributes None d. Enable the DiskGroup resource. e. Add a resource of type IP with the following configuration: Resource Type: IP 1 Key Attributes Critical False Type-Specific Attributes Device <network interface> Address <local Prime-Network SG IP> NetMask <local Prime-Network SG netmask> Overridden Attributes None 10-20

21 Chapter In addition to the simple IP agent, VCS provides the IPMultiNIC and IPMultiNICB agents, which can be used in place of the IP agent if necessary. This functionality also applies to the NIC agents in the other service groups. f. Enable the IP resource. g. Verify that no partitions from the internal disk are mounted under /export/home on either server. If a partition is mounted, unmount it and comment out the corresponding entry in /etc/vfstab. h. Add a resource of type Mount with the following configuration: Resource Type: Key Attributes Critical Type-Specific Attributes MountPoint BlockDevice Mount False FSType FsckOpt -y Overridden Attributes None /export/home <Prime-Network volume block device> vxfs Step 4 i. Enable the Mount resource. j. Create dependency links between the following resources. (The direction of the arrow indicates the dependency.) IP > NIC Mount > Disk group To configure the Oracle service group, do the following: a. Add a resource of type NIC to the Oracle service group with the following configuration: Resource Type: NIC Key Attributes Critical False Type-Specific Attributes Device <network interface> Overridden Attributes None b. Enable the NIC resource. c. Add a resource of type DiskGroup to the Oracle service group with the following configuration: 10-21

22 Chapter 10 Resource Type: DiskGroup Key Attributes Critical False Type-Specific Attributes DiskGroup <Oracle disk group> Overridden Attributes None d. Enable the DiskGroup resource. e. Add a resource of type IP to the Oracle service group with the following configuration: Resource Type: IP Key Attributes Critical False Type-Specific Attributes Device <network interface> Address <local Oracle SG IP> NetMask <local Oracle SG netmask> Overridden Attributes None f. Enable the IP resource. g. Verify that no partitions from the internal disk are mounted under /opt/db, /opt/dbarch, /opt/dbbackup, /opt/dbdata, or /opt/dblogs on either server. If a partition is mounted, unmount it and comment out the corresponding entry in /etc/vfstab. h. Add four or five resources of type Mount to the Oracle service group with the following configurations: Note The Oracle service group is shown here with five mount resources. Oracle and the embedded database require one volume for binaries and data, one volume for archive files, and one volume for redo logs. The embedded database requires an additional volume for backup files. Adding a fifth volume (or more) for additional data files is optional. Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/db BlockDevice <Oracle application volume block device> 10-22

23 Chapter 10 Resource Type: Mount FSType vxfs FsckOpt -y Overridden Attributes None Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/dbarch BlockDevice <Oracle archive volume block device> FSType vxfs FsckOpt -y Overridden Attributes None Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/dbdata BlockDevice <Oracle data volume block device> FSType vxfs FsckOpt -y Overridden Attributes None Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/dblogs BlockDevice <Oracle logs volume block device> FSType vxfs 10-23

24 Chapter 10 Resource Type: Mount MountOpt convosync=direct FsckOpt -y Overridden Attributes None i. Enable the Mount resource. j. If you are using an embedded database, add an additional resource of type Mount to the Oracle service group with the following configurations: Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/dbbackup BlockDevice <Oracle backup volume block device> FSType vxfs FsckOpt -y Overridden Attributes None k. Enable the Mount resource. l. Create dependency links between the following resources. (The direction of the arrow indicates the dependency.) IP > NIC Mount (1) > Disk group Mount (2) > Disk group Mount (3) > Disk group Mount (4) > Disk group Mount (5) > Disk group (only if you are using an embedded database) Oracle Database Software This section describes how to install the Oracle database software. If you are using an embedded database, skip this section and go to Cisco Prime Network Software, page Install the Oracle database according to the Oracle product documentation and Creating and Configuring an Oracle Database, page 5-2 An HR/DR scenario has additional requirements as described in this section

25 Chapter 10 Tip Throughout this section, the Oracle user is oracle and the Oracle group is dba. Some administrators choose to create the user oracle with the default group oinstall and then create an additional group dba with the user oracle as a member. The group dba can be replaced by oinstall where appropriate. Oracle Preinstallation Requirements in an HR/DR Environment In HR/DR environment, the Oracle database installation requires that you: Create a software owner user and group(s). When doing so: Create the user and group(s) on P2. Place the user s home directory on the root file system of P2. Give the directory the correct ownership. Do not place the user s home directory under /export/home, because the Prime-Network shared volume is mounted there. Set up the Oracle user s environment. Set up the required environment variables in the user s home directory on P2. Configure system parameters in /etc/system on P2. Oracle Preinstallation Tasks in an HR/DR Environment The following preinstallation tasks are specific to gateway server high availability: 1. Verify that you can connect from: P1 to P2 P1 to P1 P2 to P2 P2 to P1 2. Verify that the Oracle listener port (1521 by default) is available on both servers. 3. Verify that the Oracle service group is online on P2 (which is the default for this service group). The Oracle external volumes will be mounted on P2 under /opt/db, /opt/dbarch, and /opt/dbdata. 4. Create the following directories with oracle:dba ownership: /opt/db/oracle /opt/db/orainventory /opt/dbarch/oraarch /opt/dbdata/oradata2 /opt/dblogs/oralogs Oracle Database Installation and Database Creation Step 1 Install the Oracle database software on P2 according to the Oracle product documentation, the guidelines in Creating and Configuring an Oracle Database, page 5-2 any additional performance guidelines provided for Cisco Prime Network, and the following HA-specific requirements: 10-25

26 Chapter 10 Step 2 Set the Oracle base path to /opt/db/oracle. Based on this value, the software location is set automatically to /opt/db/oracle/product/11.2.0/dbhome_1. Set the inventory directory to /opt/db/orainventory. Save the archive logs in /opt/dbarch/oraarch. Save the redo logs in /opt/dblogs/oralogs. If you are using the netca utility to create a listener, edit the /opt/db/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora file on P2 immediately after you create the listener, and before you create the database. If you create the listener and database during the initial Oracle database installation, edit the file at the end of the process. Wherever the hostname of the P2 IP address appears, replace it with the hostname alias of the Oracle service group logical IP address, as follows: # listener.ora Network Configuration File: /opt/db/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora # Generated by Oracle configuration tools. LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = ana-cluster-oracle)(port = 1521)) ) ) ADR_BASE_LISTENER = /opt/db/oracle Step 3 At the end of the database creation process, edit the /opt/db/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora file on P2. Wherever the hostname of the P2 IP address appears, replace it with the hostname alias of the Oracle service group logical IP address, as follows: # tnsnames.ora Network Configuration File: /opt/db/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora # Generated by Oracle configuration tools. LISTENER_MCDB = (ADDRESS = (PROTOCOL = TCP)(HOST = ana-cluster-oracle)(port = 1521)) MCDB = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = ana-cluster-oracle)(port = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = MCDB) ) ) Oracle Postinstallation Tasks in an HA/DR Environment Complete the following HA/DR postinstallation tasks to synchronize the Oracle environment on P1 and P2: Step 1 Synchronize the changes in the following files from P2 to P1: /etc/passwd /etc/shadow 10-26

27 Chapter 10 Step 2 /etc/group /etc/system On P1, create the same home directory for user oracle on the root file system as was created for user oracle on P2. Give the directory oracle:dba ownership. Step 3 On P1, set up the same environment variables for user oracle as were set up for user oracle on P2. Step 4 Copy (overwrite) the following directory and all its files from P2 to P1: /var/opt/oracle Home directory of user oracle Step 5 If necessary, change the owner/mode of all files copied to P1 to match the corresponding files on P2. Step 6 Reboot P1 and P2. Step 7 Step 8 Step 9 Step 10 When P2 restarts, verify that the Oracle service group is online on P2. If the Oracle service group is not online, bring it online on P2. If the database and listener are not running, start them manually on P2 and verify that they start and run correctly. To start the database and listener, enter the following commands as user oracle: % sqlplus /nolog SQL> connect /as sysdba SQL> startup SQL> quit % lsnrctl start If you are using raw devices for the redo logs, add three new redo logs on the designated volumes, one redo log per volume. Force Oracle to switch log files three times so that it uses the first of the new files on the raw devices. You can delete the original temporary log files that were created when the database was created. Shut down the database and listener manually. Step 11 Switch the Oracle service group to P1. Step 12 Start the database and listener manually on P1 and verify that they start correctly. Cisco Prime Network Software Cisco Prime Network must be installed on both servers in the cluster because it affects files on the root partition and on the /export/home partition. This section uses the default names: network user network39. This is the user-defined Cisco Prime Network OS user. The username must start with a letter and contain only the following characters: [A-Z a-z 0-9]. Prime Network Group network Prime Network Home directory network39 If you are not using the default names, substitute the correct values. To install Cisco Prime Network: Step 1 Step 2 Verify that the Prime-Network service group is online on P1 (which is the default for this service group). If you are not installing an embedded database, verify that the Oracle service group is online on P1 and that the Oracle database application and listener are running on P

28 Chapter 10 Step 3 Verify that /etc/passwd, /etc/shadow, and /etc/group files are identical on both servers (and on the server in the remote cluster, if applicable). Step 4 Enter the following command to install Cisco Prime Network on P1: perl install.pl -user network39 -ha Note Step 5 Step 6 Make sure that the port 2148 is free before starting the Veritas HA installation. As the root user, enter the following command to switch users to network39: # su - network39 As the root user, enter the following command to change the password for user network39: # passwd network39 Step 7 Step 8 After the installation is complete, you will be prompted to configure Prime Network. Enter yes to continue or no to configure later using the network-conf command. Enter the following information in the prompts that appear during the configuration: Prime-Network back-end services IP address : When choosing the IP address of the Prime-Network back-end services, choose the logical IP address of the Prime-Network service group. Oracle database IP address: When choosing the IP address of the Oracle database, choose the logical IP address of the Oracle service group. Location of the Oracle data files: If you are using Oracle, use /opt/db/oracle/oradata for the location of the Oracle data files. For an embedded database, enter the given details for the following prompts: Database user home directory: /opt/db/oracle. Datafiles location: /opt/db/oracle/oradata/anadb. Redo logs location: /opt/dblogs/oralogs. While the Prime-Network service group is still online on P1, log into P2 as the root user. Step 9 Enter one of the following commands to install Cisco Prime Network on P2: If you are not using an embedded database, enter: perl install_ha.pl -user network39 If you are using an embedded database, enter: perl install_ha.pl -user network39 -embedded During the installation, you will be asked to enter the following information: Group ID (gid) of group network and the user ID (uid) of the network user on the primary server. To find these values, look for the following line in the /etc/passwd file on P1: network user:x:uid:gid::/export/home/network39:/bin/tcsh The uid and gid are shown in the line corresponding to the networkuser, as indicated in bold in the following example: root:x:0:0:super-user:/root:/bin/tcsh daemon:x:1:1::/: bin:x:2:2::/usr/bin: sys:x:3:3::/: adm:x:4:4:admin:/var/adm: 10-28

29 Chapter 10 nobody4:x:65534:65534:sunos 4.x Nobody:/: admin:x:101:1::/local/admin:/bin/tcsh network39:x:1310:1310::/export/home/network39:/bin/tcsh bos:x:1310:1310:bos Admin:/export/home/sheer/Main/bosconfig/bos_shell_scripts:/export/home/sheer/Main/bosc onfig/bos_shell_scripts/run.csh oracle:x:1311:502::/opt/db/oracle:/bin/tcsh In the preceding output, the network user is network39, the uid of the network user is 1310, and the gid of group network is The oinstall group gid and primary Cisco Prime Network gateway dba. To find these values, look for the following lines in the /etc/group file on P1: oinstall::1311:oracle dba::1312: The oracle user uid on the primary Cisco Prime Network gateway. To find these values, enter the following commands as the oracle user on P1: [~]# id uid=1311(oracle) gid=1312(dba) Step 10 Step 11 Step 12 Step 13 If you are using geographical redundancy HA, On P1, enter the following command as user network39: # ~/Main/scripts/add_secondary_host.pl When you are requested for the IP address of the secondary host, enter the remote-single-node-ip. Switch the Prime-Network service group to P2. The external Prime-Network volume is now mounted on P2 under /export/home. On P2, enter the following command to change the password for user network39. Use the same password as on P1: # passwd network39 Step 14 Verify that Cisco Prime Network starts and runs correctly on P2. Step 15 On P2, enter the following command as user network39: # ~/Main/scripts/edit_registry_for_ha.pl Step 16 Step 17 Step 18 Step 19 Launch the Cisco Prime Network Administration client application and connect using the logical IP address of the Cisco Prime Network service group. Stop Cisco Prime Network on P2 using the normal stop method and switch the Prime-Network service group to P1. Then, start Prime-Network manually using the normal Cisco Prime Network start script on P1 and verify that Cisco Prime Network starts and runs correctly on P1. Using the Cisco Prime Network Administration client application, reconnect using the logical IP address of the Cisco Prime Network service group. If desired, add additional data files to the Oracle database. See Adding Data Files to the Tablespace, page Create the additional data files under /opt/db/oradata and /opt/dbdata/oradata2 (if used). Caution Step 20 If you are using geographical redundancy HA, skip the remaining steps in this section and proceed to VCS Configuration for Oracle and Cisco Prime Network, page With Cisco Prime Network running on P1, as user network39, install any relevant service pack(s) on P1 according to the service pack installation instructions

30 Chapter 10 Step 21 Step 22 Step 23 Add the unit servers to the setup. For the gateway IP address, use the logical IP address of the Cisco Prime Network service group. Install any relevant point patches according to the patch documentation. If you are using LDAP to authenticate Cisco Prime Network users, configure the LDAP settings in Cisco Prime Network Administration. You must set the LDAP values in Cisco Prime Network Administration and on the Prime Network Gateway agent. Step 24 Synchronize the changes in the following files from P1 to P2: /etc/passwd /etc/shadow /etc/group /etc/system VCS Configuration for Oracle and Cisco Prime Network Tip The Veritas administrator should perform the steps in this section. Once Oracle and Cisco Prime Network have been installed, complete the VCS configuration: Step 1 Step 2 From the Cluster Manager GUI, choose File > Import Types and import the Oracle and Cisco Prime Network resource types. By default, the Oracle resource types file resides in /etc/vrtsagents/ha/conf/oracle/oracletypes.cf; the Cisco Prime Network resource types file resides in /etc/vrtsvcs/conf/anatypes.cf. When you are finished, exit the Cluster Manager GUI and restart it. Add a resource of type Oracle to the Oracle service group with the following configuration. Note the overridden attribute: Resource Type: Oracle Key Attributes Critical False Type-Specific Attributes SID MCDB For Oracle anadb For an embedded database Owner oracle Home <ORACLE_HOME> Overridden Attributes OnlineTimeout 1200 Step 3 Step 4 Enable the Oracle resource. Add a resource of type Netlsnr to the Oracle service group with the following configuration: 10-30

31 Chapter 10 Resource Type: Netlsnr Key Attributes Critical False Type-Specific Attributes Owner oracle Home <ORACLE_HOME> Overridden Attributes RestartLimit 1 Step 5 Step 6 Enable the Netlsnr resource. Add a resource of type Prime-NetworkGateway to the Prime Network service group with the following configuration. The four LDAP parameters are required only if you are using LDAP authentication and geographical redundancy HA. (For information on configuring the Prime-NetworkGateway agent, see Using and Configuring the Prime-NetworkGateway Agent, page ) Resource Type: Key Attributes Critical Type-Specific Attributes NetlsnrResourceName Prime-NetworkIPResourceN ame OraIPResourceName LDAPUrl LDAPPrefix LDAPSuffix LDAPUseSSL Overridden Attributes Prime-NetworkGateway False OnlineTimeout 1200 RestartLimit 1 <Netlsrn resource name> <Prime-Network IP resource name> <Oracle IP resource name> <Local LDAP URL> <Local LDAP prefix> <Local LDAP suffix> <Local LDAP SSL usage> Step 7 Step 8 Enable the Prime-NetworkGateway resource. Create dependency links between the following resources in the Oracle service group. (The direction of the arrow indicates the dependency.) Oracle > IP Oracle > Mount (1) Oracle > Mount (2) Oracle > Mount (3) Oracle > Mount (4) 10-31

32 Chapter 10 Step 9 Step 10 Step 11 Oracle > Mount (5) (only if you are using an embedded database) Netlsnr > Oracle Create dependency links between the following resources in the Prime-Network service group. (The direction of the arrow indicates the dependency.) Prime-NetworkGateway > IP Prime-NetworkGateway > Mount Manually switch each service group to the other server and back again to confirm the service groups work correctly. Change all resources in the two service groups to critical. Notifications Tip The Veritas administrator should perform the steps in this section. You can add notifiers (resources of type NotifierMngr ) to send SMTP or SNMP notifications for faults. Notifiers are cluster-level resources and should be added to a separate ClusterService service group, which is created automatically. If the cluster is selected in the GUI, the notifier is created as the ClusterService s resource. Use the Notifier Wizard to create the notifier. Final Cluster Configuration This section marks the end of the configuration process for local redundancy HA. At this point, the cluster resource views should resemble the following figures. The resource names might vary

33 Chapter 10 Figure 10-6 Local Redundancy HA Prime-Network Service Group 10-33

34 Chapter 10 Figure 10-7 Local Redundancy HA Oracle Service Group 10-34

35 Chapter 10 Figure 10-8 Local Redundancy HA Service Groups In Figure 10-8, the ClusterService service group can be used for notifier resources (but is not required). Veritas Gateway HA Remote Single-Node Cluster To implement the geographical redundancy HA (DR) solution, a single-node cluster is created at the remote site and a global cluster is created with the existing local dual-node cluster. Hardware Tip The steps in this section might require assistance from the Veritas consultant. Configure the server as shown in Figure 10-2, including: Dual Gigabit Ethernet connections for the heartbeat. Single or dual connections to each external storage unit. Configure the external storage so that all disks or LUNs are accessible from the server. The disk or LUN configuration depends on the type of storage. If you are using JBOD disks, provide enough physical disks to create volumes identical in size to those in the local cluster. If you are using storage that supports hardware RAID, divide the physical disks into LUNs so that the necessary volumes can be created, 10-35

36 Chapter 10 configured to satisfy the Oracle (and VVR) performance requirements, and protected with RAID5, RAID1, or RAID10. You can create the Oracle volumes on a single LUN. The SRL volumes are relevant only if you are using geographical redundancy with VVR. Operating System Tip The steps in this section might require assistance from the Veritas consultant. Step 1 Step 2 Step 3 Install and configure the operating system on the server in the remote cluster in exactly the same way as it was installed and configured on the local cluster servers. Verify that the time is synchronized with both servers in the local cluster. As the root user, enter the following commands to create the mount points: # mkdir -p /export/home # cd /opt # mkdir db dbarch dbbackup dbdata dblogs The following mount points are created: /export/home /opt/db /opt/dbarch /opt/dbbackup (required only if you are using an embedded database) /opt/dbdata /opt/dblogs Veritas Software Tip The Veritas administrator should perform the steps in this section according to the product documentation. Step 1 Step 2 Step 3 Install the Veritas Storage Foundation Enterprise HA with global cluster option on the server in the remote cluster. Veritas Volume Manager is used to manage the internal storage. It can also be used to manage the external storage if the external storage does not have its own volume management solution. Install the latest Veritas maintenance pack that contains the Veritas patches for Solaris. Install the Veritas High Availability Agent for Oracle

37 Chapter 10 Disk Groups, Volumes, SRLs, and Mirroring Tip The steps in this section might require assistance from the Veritas consultant. Step 1 Step 2 Step 3 Use Veritas Volume Manager (VxVM) to create disk groups and volumes that are identical in size and configuration to those in the local cluster. If the disks are mirror-protected instead of RAID-protected, include a duplicate set of disks for the mirroring. Use VxVM to set up mirroring between the two internal disks on both servers. If you are not using hardware that supports hardware RAID for the external disks, use VxVM to set up mirroring for the external disks (including SRLs). (This task takes a long time and can be deferred to a convenient time during the installation process.) Geographical Redundancy Single-Node Cluster Worksheet Use the following worksheet to record all parameters necessary to create and configure the remote single-node cluster. The parameter names shown in italics will be requested during the actual HA installation. These parameters are in addition to the parameters used in the local dual-node cluster (see Table 10-6). Table 10-7 Parameters Required for the Remote Single-Node Cluster Parameter Name Local-ClusterService-SG-IP Local-ClusterService-SG- netmask Remote-ClusterService-SG-IP Remote-ClusterService-SG- netmask Remote-single-node-IP Remote-single-node-netmask Prime-Network-RVG Oracle-RVG Prime-Network-volume Prime-Network-SRL-volume Oracle-application-volume Description IP address of the local cluster WAC. Netmask of the interface of the local cluster WAC. Example: csgnic. IP address of the remote cluster WAC. Netmask of the interface of the remote cluster WAC. Logical IP address of the remote single-node cluster. Netmask of the logical interface of the remote single-node cluster. Name of the RVG created for the Prime-Network data (VVR only). Example: anarvg. Name of the RVG created for the Oracle data (VVR only). Example: orarvg. Name of the volume for the Prime-Network application or data. Example: anavol. Name of the volume for the Prime-Network SRL. Example: anavol. Name of the volume for the Oracle application. Example: oravol

38 Chapter 10 Table 10-7 Parameters Required for the Remote Single-Node Cluster (continued) Parameter Name Oracle-archive-volume Oracle-data-volume Oracle-backup-volume Oracle-logs-volume Oracle-SRL-volume Oracle-application-volume- block-device Oracle-archive-file-volume- block-device Oracle- data-volume-block- device Oracle-backup-volume-block-device Oracle-logs-volume-block- device Prime-Network-RVG-resource-name Oracle-RVG-resource-name Oracle-SG-Netlsnr-resource- name Single-node-IP-resource-name Domain Remote-LDAP-URL Description Name of the volume for the Oracle archive logs. Example: oraarchvol. Name of the volume for the additional Oracle data files. Example: oravol. Name of the volume for the Oracle backup files. Example: oravol. Name of the volume for the Oracle redo logs. Example: oravol. Name of the volume for the Oracle SRL. Example: orasrlvol. Block device of the volume created for the Oracle application. Example: /dev/vx/dsk/oradg/oravol. Block device of the volume created for the Oracle archive logs. Example: /dev/vx/dsk/oradg/oraarchvol. Name of the volume for the additional Oracle data file. Example: oradatavol. Block device of the volume created for the Oracle backup files for the embedded database. Example: /dev/vx/dsk/oradg/orabackupvol. Block device of the volume created for Oracle redo log files. Example: /dev/vx/dsk/oradg/oralogsvol. Name of the RVG resource for the Prime-Network data (VVR only). Example: ana_rvg. Name of the RVG resource for the Oracle data (VVR only). Example: oracle_rvg. Name of the Netlsnr resource in the Oracle service group. Example: Netlsnr. For a single-node cluster, the name of the IP resource in the VVR service group. Example: single_node_ip. Domain served by the DNS server to be updated with the current IP address of the gateway in case of a site-to-site failover or switchover (if you are configuring a DNS resource). Remote LDAP server URL (if you are using LDAP authentication). Example: ldap:// :

39 Chapter 10 Table 10-7 Parameters Required for the Remote Single-Node Cluster (continued) Parameter Name Remote-LDAP-prefix Remote-LDAP-suffix Remote-LDAP-SSL-usage Description Remote LDAP distinguished name prefix (if you are using LDAP authentication). Example: CN. Remote LDAP distinguished name suffix (if you are using LDAP authentication). Example: CN=Users,DC=,DC=myldapserver,DC=local. Remote Prime-Network-LDAP SSL protocol usage (if you are using LDAP authentication). The boolean value is true if the SSL protocol is used between Prime-Network and the LDAP server. The boolean value is false (the default) if SSL is not used. Remote Cluster Creation Tip The Veritas consultant should perform the steps in this section. Use VCS to enable the global cluster option (WAC): Step 1 Step 2 Step 3 Create a new cluster for the remote site. Create a global cluster that includes the local and remote clusters. As part of the creation process, add a ClusterService service group to the local and remote clusters (if it does not already exist) to manage the global cluster, including all necessary resources. a. Use local-clusterservice-sg-ip and local-clusterservice-sg-netmask for the ClusterService IP resource in the local cluster. b. Use remote-clusterservice-sg-ip and remote-clusterservice-sg-netmask for the ClusterService IP resource in the remote cluster. Remote Cluster Configuration Tip The Veritas administrator should perform the steps in this section. Step 1 Use Cluster Manager to add three new service groups to the remote cluster: ana_sg for Prime-Network, oracle_sg for Oracle, and a replication service group called vvr_sg (if you are using VVR) or replication_sg (if you are not using VVR). You must use the exact names ana_sg, oracle_sg, and vvr_sg or replication_sg. Use the following settings: Use failover as the service group type for all three service groups. Add the single server to each service group. You do not have to set the resources as critical in the service groups for the remote single-node cluster. There is no local failover option within the remote single-node cluster

40 Chapter 10 Step 2 Step 3 For the ana_sg and oracle_sg service groups in the local and remote clusters, use Cluster Manager to make the service groups global. Right-click each service group and use the Configure as global option with the following settings: On the local cluster, add the remote cluster to both service groups and connect to the remote cluster using its ClusterService SG IP address and cluster manager username/password (if in use). On the remote cluster, add the local cluster to both service groups and connect to the local cluster using its ClusterService SG IP address and cluster manager username/password (if in use). Add a resource of type NIC to the remote cluster s replication (VVR) service group with the following configuration: Resource Type: NIC Key Attributes Critical False Type-Specific Attributes Device <network interface> Overridden Attributes None Step 4 Step 5 Enable the NIC resource. Add a resource of type IP to the remote cluster s replication (VVR) service group with the following configuration: Resource Type: IP Key Attributes Critical False Type-Specific Attributes Device <network interface> Address <remote single-node IP> NetMask <remote single-node netmask> Overridden Attributes None Step 6 Step 7 Enable the IP resource. Add two resources of type DiskGroup to the remote cluster s replication (VVR) service group with the following configurations: Resource Type: Key Attributes Critical Type-Specific Attributes DiskGroup DiskGroup False <Prime-Network disk group> 10-40

41 Chapter 10 Resource Type: DiskGroup Overridden Attributes None Resource Type: DiskGroup Key Attributes Critical False Type-Specific Attributes DiskGroup <Oracle disk group> Overridden Attributes None Step 8 Step 9 Step 10 Step 11 Enable the DiskGroup resources. Create a dependency link between the following resources in the remote cluster s replication service group. (The direction of the arrow indicates the dependency.) IP > NIC Verify that no partitions are mounted under /export/home on the server in the remote cluster. If a partition is mounted, unmount it and comment out any corresponding entry in /etc/vfstab. Add a resource of type Mount to the remote cluster s Prime-Network service group with the following configuration: Resource Type: Key Attributes Critical Type-Specific Attributes MountPoint BlockDevice Mount False FSType FsckOpt -y Overridden Attributes None /export/home <Prime-Network volume block device> vxfs Step 12 Step 13 Step 14 Enable the Mount resource. Verify that no partitions are mounted under /opt/db, /opt/dbarch, or /opt/dbdata on either server. If a partition is mounted, unmount it and comment out any corresponding entries in /etc/vfstab. Add four or five resources of type Mount to the service group with the following configurations: 10-41

42 Chapter 10 Note The Oracle service group is shown here with five mount resources. Oracle and the embedded database require one volume for binaries and data, one volume for archive files, and one volume for redo logs. The embedded database requires an additional volume for backup files. Adding a fifth volume (or more) for additional data files is optional. Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/db BlockDevice <Oracle application volume block device> FSType vxfs FsckOpt -y Overridden Attributes None Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/dbarch BlockDevice <Oracle archive volume block device> FSType vxfs FsckOpt -y Overridden Attributes None Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/dbdata BlockDevice <Oracle data volume block device> FSType vxfs FsckOpt -y 10-42

43 Chapter 10 Resource Type: Mount Overridden Attributes None Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/dblogs BlockDevice <Oracle logs volume block device> FSType convosync=direct FsckOpt -y Overridden Attributes None Step 15 Step 16 Enable the Mount resources. If you are using an embedded database, add an additional resource of type Mount to the service group with the following configuration: Resource Type: Mount Key Attributes Critical False Type-Specific Attributes MountPoint /opt/dbbackup BlockDevice <Oracle backup volume block device> FSType vxfs FsckOpt -y Overridden Attributes None Step 17 Step 18 Enable the Mount resource. Add the following aliases to the /etc/hosts file on the server in the remote cluster: remote-single-node-ip ana-cluster-ana ana-cluster-oracle 10-43

44 Chapter 10 Note If the IP address that you enter is not the default one, the database installation updates the hostname in the listener s files. Verify that /etc/hosts is updated with the correct IP address and hostname; the order is important. If more than one hostname is attached to the selected IP address, the first hostname is used. Replication Using VVR Tip The Veritas consultant should perform the steps in this section. This section describes how to use VVR to set up data replication between the local and remote clusters. The initial replication involves copying the entire contents of the two volumes. It is recommended that you perform the initial replication with the local and remote servers connected to the same LAN. After the initial replication is complete, move the server for the remote cluster to its permanent location. If you are not using VVR, skip to Replication Without Using VVR, page Step 1 Step 2 Step 3 Add the following aliases to the /etc/hosts file on both servers in the local dual-node cluster: local-prime-network-sg-ip ana-cluster-ana vvr-local-ana local-oracle-sg-ip ana-cluster-oracle vvr-local-oracle remote-single-node-ip vvr-remote-single Add the following entries to the /etc/hosts file on the server in the remote single-node cluster: local-prime-network-sg-ip vvr-local-ana local-oracle-sg-ip vvr-local-oracle remote-single-node-ip ana-cluster-ana ana-cluster-oracle vvr-remote-single Create two replicated data sets (RDSs) with the following values: RDS Name Prime-Network RDS RVG name Disk group Data volumes SRL volume Oracle RDS RVG name Disk group Values <Prime-Network RVG> <Prime-Network disk group> <Prime-Network volume> <Prime-Network SRL volume> <Oracle RVG> <Oracle disk group> 10-44

45 Chapter 10 RDS Name Data volumes SRL volume Values <Oracle application volume> <Oracle logs volume> <Oracle data volume> <Oracle archive volume> <Oracle backup volume> (if you are using an embedded database) <Oracle SRL volume> Step 4 For each RDS, add the secondary with the following hostnames: RDS Name Prime-Network RDS Primary Secondary Oracle RDS Primary Secondary Values vvr-local-ana vvr-remote-single vvr-local-oracle vvr-remote-single Step 5 If you are using VCS version 5.0, from the Cluster Manager GUI, choose File > Import Types and import the VVR resource types. By default, the VVR resource types file resides in /etc/vrtsvcs/conf/vvrtypes.cf. Import the resource types for both the local and remote clusters. When you are finished, exit the Cluster Manager GUI and restart it. Cluster Configuration for VVR Tip The Veritas administrator should perform the steps in this section. Remote Cluster Service Groups Step 1 Add two resources of type RVG to the remote cluster s VVR service group with the following configuration: Resource Type: RVG Key Attributes Critical False Type-Specific Attributes RVG <Prime-Network RVG> DiskGroup <Prime-Network disk group> 10-45

46 Chapter 10 Resource Type: RVG Overridden Attributes None Resource Type: RVG Key Attributes Critical False Type-Specific Attributes RVG <Oracle RVG> DiskGroup <Oracle disk group> Overridden Attributes None Step 2 Step 3 Step 4 Enable the RVG resource. Create dependency links between the following resources in the remote cluster s VVR service group. (The direction of the arrow indicates the dependency.) RVG (Prime-Network) > IP RVG (Oracle) > IP RVG (Prime-Network) > Disk group (Prime-Network) RVG (Oracle) > Disk group (Oracle) Add a resource of type RVGPrimary to the remote cluster s Prime-Network service group with the following configuration: Resource Type: RVGPrimary Key Attributes Critical False Type-Specific Attributes RVGResourceName <Prime-Network RVG resource name> AutoTakeover 1 AutoResync 0 Overridden Attributes None Step 5 Step 6 Enable the RVGPrimary resource. Create a dependency link between the following resources in the remote cluster s Prime-Network service group. (The direction of the arrow indicates the dependency.) Mount > RVGPrimary 10-46

47 Chapter 10 Step 7 Add a resource of type RVGPrimary to the remote cluster s Oracle service group with the following configuration: Resource Type: RVGPrimary Key Attributes Critical False Type-Specific Attributes RVGResourceName <Oracle RVG resource name> AutoTakeover 1 AutoResync 0 Overridden Attributes None Step 8 Step 9 Enable the RVGPrimary resource. Create dependency links between the following resources in the remote cluster s Oracle service group. (The direction of the arrow indicates the dependency.) Mount (1) > RVGPrimary Mount (2) > RVGPrimary Mount (3) > RVGPrimary Mount (4) > RVGPrimary Mount (5) > RVGPrimary (if you are using an embedded database) Note If you are using raw devices for redo logs, there are no volume resources for the three redo log volumes. Because the RDS includes the three volumes, bringing the RVG online automatically ensures that the redo log volumes are online. Local Cluster Service Groups Step 1 Add two new service groups: ana_vvr_sg and oracle_vvr_sg (if you are using VVR) or ana_replication_sg and oracle_replication_sg (if you are not using VVR). Use the following settings: Use failover as the service group type for both service groups. Add both servers to each service group. Determine the server priority according to which server is the primary server for each service group: Service Group P1 Server Priority P2 Server Priority Prime-Network 0 1 Oracle

48 Chapter 10 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Set the resources in these service groups to critical. Note, however, that the resources are initially set to non-critical during the installation process and are made critical once the service groups are built. Remove the dependency links between the following resources in the local cluster s Prime-Network service groups: Mount > Disk group Prime-NetworkGateway > IP Remove the dependency links between the following resources in the local cluster s Oracle service group: Mount (1) > Disk group Mount (2) > Disk group Mount (3) > Disk group Mount (4) > Disk group Mount (5) > Disk group (if you are using an embedded database) Oracle > IP Move the DiskGroup resource from the ana_sg service group to ana_vvr_sg. To move a resource between groups, do the following from the Cluster Manager: a. When moving the first resource, the target service group does not contain any resources. Therefore, create any type of resource as a placeholder in the target service group. b. Select the resource that you want to move. c. Right-click and choose Copy > Self. d. Right-click and choose Delete. e. Select any resource in the target service group. f. Right-click and choose Paste > Paste. g. Once the final resource has been removed, remove the placeholder resource. Move the IP resource from the ana_sg service group to ana_vvr_sg. Move the NIC resource from the ana_sg service group to ana_vvr_sg. Move the DiskGroup resource from the oracle_sg service group to oracle_vvr_sg. Move the IP resource from the oracle_sg service group to oracle_vvr_sg. Move the NIC resource from the oracle_sg service group to oracle_vvr_sg. Add a resource of type RVG to the local cluster s Prime-Network VVR service group with the following configuration: Resource Type: Key Attributes Critical Type-Specific Attributes RVG DiskGroup RVG False <Prime-Network RVG> <Prime-Network disk group> 10-48

49 Chapter 10 Resource Type: RVG Overridden Attributes None Step 11 Step 12 Enable the RVG resource. Add a resource of type RVG to the local cluster s Oracle VVR service group with the following configuration: Resource Type: RVG Key Attributes Critical False Type-Specific Attributes RVG <Oracle RVG> DiskGroup <Oracle disk group> Overridden Attributes None Step 13 Step 14 Step 15 Step 16 Enable the RVG resource. Create dependency links between the following resources in the local cluster s Prime-Network and Oracle VVR service groups. (The direction of the arrow indicates the dependency.) RVG > Disk group RVG > IP IP > NIC Bring the ana_vvr_sg and oracle_vvr_sg service groups online on their primary servers. Add a resource of type RVGPrimary to the local cluster s Prime-Network service group with the following configuration: Resource Type: RVGPrimary Key Attributes Critical False Type-Specific Attributes RVGResourceName <Prime-Network RVG resource name> AutoTakeover 1 AutoResync 0 Overridden Attributes None Step 17 Step 18 Enable the RVGPrimary resource. Add a resource of type RVGPrimary to the local cluster s Oracle service group with the following configuration: 10-49

50 Chapter 10 Resource Type: RVGPrimary Key Attributes Critical False Type-Specific Attributes RVGResourceName <Oracle RVG resource name> AutoTakeover 1 AutoResync 0 Overridden Attributes None Step 19 Step 20 Step 21 Step 22 Step 23 Enable the RVGPrimary resource. Create a dependency link between the following resources in the local cluster s Prime-Network service group. (The direction of the arrow indicates the dependency.) Mount > RVGPrimary Create dependency links between the following resources in the local cluster s Oracle service group. (The direction of the arrow indicates the dependency.) Mount (1) > RVGPrimary Mount (2) > RVGPrimary Mount (3) > RVGPrimary Mount (4) > RVGPrimary Mount (5) > RVGPrimary (if you are using an embedded database) Bring the new RVGPrimary resources online. Use the VVR management application to start replication for both RDSs. Replication Without Using VVR Tip The Veritas administrator should perform the steps in this section. This section describes how to set up storage-based data replication (without using VVR) between the local and remote clusters. The initial replication involves copying the entire contents of the two volumes. It is recommended that you perform the initial replication with the local and remote servers connected to the same LAN. After the initial replication is complete, move the server for the remote cluster to its permanent location. Step 1 Step 2 For the local cluster, add the resources and create dependency links between the cluster and the storage-based replication system. For the remote cluster, add the resources and create dependency links between the cluster and the storage-based replication system

51 Chapter 10 Step 3 Step 4 Step 5 If you are using raw devices for the redo logs, determine whether the storage-based replication requires volume resources for the redo logs volumes. If volume resources are required, include them in the replication service group. Bring the remote cluster s replication service group online. Start replication between the disks that contain the Cisco Prime Network and Oracle data at the local and remote sites. Do not continue to the next section until replication of all disks is complete. Oracle Database Software This section describes how to install the Oracle database software. If you are using an embedded database, skip this section and go to Installing Cisco Prime Network Software on Geographical Redundancy Nodes, page Step 1 Synchronize the changes in the following files from P2 to S1: Step 2 /etc/passwd /etc/shadow /etc/group /etc/system On S1, create the same home directory for user oracle on the root file system as was created for user oracle on P2. Give the directory oracle:dba ownership. Step 3 On S1, set up the same environment variables for user oracle as were set up for user oracle on P2. Step 4 Copy (overwrite) the following directory and all its files from P2 to S1: /var/opt/oracle Home directory of user oracle Step 5 If necessary, change the owner/mode of all files copied to S1 to match the corresponding files on P2. Step 6 Reboot S1. Installing Cisco Prime Network Software on Geographical Redundancy Nodes Cisco Prime Network must be installed on all servers in the global cluster because it affects files on the root partition and on the /export/home partition. Before installing Cisco Prime Network on S1, verify that a full initial data replication was completed successfully and that the secondary site s data is up-to-date. Step 1 Take the Prime-Network service group offline on P1 (and do not bring it online anywhere else). Step 2 Verify that the Oracle service group is offline on all servers. Step 3 Enter one of the following commands to install Cisco Prime Network on S1: If you are not using an embedded database, enter: perl install_ha.pl -user network39 If you are using an embedded database, enter: 10-51

52 Chapter 10 perl install_ha.pl -user network39 -embedded Step 4 Step 5 Bring the Prime-Network service group online on S1. The remote cluster s external Prime-Network volume is now mounted on S1 under /export/home. On S1, enter the following command as user root to change the password for user network39. Use the same password as on P1 and P2: # passwd network39 Step 6 Synchronize the changes in the following files from P1 to P2: /etc/passwd /etc/shadow /etc/group /etc/system VCS Remote Cluster Configuration for Oracle and Prime-Network Tip The Veritas administrator should perform the steps in this section. Step 1 Bring the Oracle and Prime-Network service groups online on S1. Step 2 Step 3 From the Cluster Manager GUI, choose File > Import Types and import the Oracle and Prime-Network resource types. By default, the Oracle resource types file resides in /etc/vrtsagents/ha/conf/oracle/oracletypes.cf and the Prime-NetworkGateway resource types file resides in /etc/vrtsvcs/conf/anatypes.cf. When you are finished, exit the Cluster Manager GUI and restart it. Add a resource of type Oracle to the remote cluster s Oracle service group with the following configuration. Note the overridden attribute: Resource Type: Oracle Key Attributes Critical False Type-Specific Attributes SID MCDB For Oracle anadb For an embedded database Owner oracle Home <ORACLE_HOME> Overridden Attributes OnlineTimeout 1200 Step 4 Step 5 Enable the Oracle resource. Add a resource of type Netlsnr to the remote cluster s Oracle service group with the following configuration: 10-52

53 Chapter 10 Resource Type: Netlsnr Key Attributes Critical False Type-Specific Attributes Owner oracle Home <ORACLE_HOME> Overridden Attributes RestartLimit 1 Step 6 Step 7 Enable the Netlsnr resource. Add a resource of type Prime-NetworkGateway to the remote cluster s Prime-Network service group with the following configuration. The four LDAP parameters are required only if you are using LDAP authentication. (For information on configuring the Prime-NetworkGateway agent, see Using and Configuring the Prime-NetworkGateway Agent, page ) Resource Type: Key Attributes Critical Type-Specific Attributes NetlsnrResourceName Prime-NetworkIPResourceN ame OraIPResourceName LDAPUrl LDAPPrefix LDAPSuffix LDAPUseSSL Overridden Attributes Prime-NetworkGateway False <Netlsrn resource name> <Single-node IP resource name> Note OnlineTimeout 1200 RestartLimit 1 For a single-node cluster with a single IP resource, the Prime-Network IP resource name is the same as the Oracle IP resource name. <Single-node IP resource name> <Remote LDAP URL> <Remote LDAP prefix> <Remote LDAP suffix> <Remote LDAP SSL usage> Step 8 Step 9 Enable the Prime-NetworkGateway resource. Create dependency links between the following resources in the remote cluster s Oracle service group. (The direction of the arrow indicates the dependency.) Oracle > Mount (1) Oracle > Mount (2) Oracle > Mount (3) Oracle > Mount (4) 10-53

54 Chapter 10 Step 10 Oracle > Mount (5) (if you are using an embedded database) Netlsnr > Oracle Create a dependency link between the following resources in the remote cluster s Prime-Network service group. (The direction of the arrow indicates the dependency.) Prime-NetworkGateway > Mount VVR/Replication Service Group Step 1 If you are using VVR, do the following: a. In the local cluster, create a dependency link from the Prime-Network service group to the Prime-Network VVR service group, and from the Oracle service group to the Oracle VVR service group. (The direction of the arrow indicates the dependency.) Prime-Network service group > Prime-Network VVR service group Relationship: Online local Dependency type: Hard Oracle service group > Oracle VVR service group Relationship: Online local Dependency type: Hard b. In the remote cluster, create a dependency link from the Oracle service group to the VVR service group. (The direction of the arrow indicates the dependency.) Oracle service group > VVR service group Relationship: Online local Dependency type: Firm Note Normally, dependencies from application service groups to the VVR service group have dependency type hard. The single-node cluster does not need a hard dependency; using type firm lets you link both the Oracle and Prime-Network service groups to the single VVR service group. Step 2 Prime-Network service group > VVR service group Relationship: Online local Dependency type: Firm If you are not using VVR, create any necessary links between service groups in the remote cluster

55 Chapter 10 Prime-Network Postinstallation Tasks Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Take the Oracle and Prime-Network service groups offline; then, bring them online on S1 to verify that the gateway starts correctly. Use the Cisco Prime Network Administration client to reconnect using the logical IP address of the remote cluster s Prime-Network service group. As user network39, install any relevant service pack(s) on S1 according to the service pack installation instructions. Add the unit servers to the setup. For the gateway IP address, use the logical IP address of the single-node remote cluster. If you are using LDAP to authenticate Prime-Network users, use Cisco Prime Network Administration to connect to S1 and configure the LDAP settings for the remote site LDAP server. You must set the values once in Cisco Prime Network Administration. To configure the Prime-NetworkGateway resources for the local and remote clusters, use the local LDAP server values for the Prime-NetworkGateway resource on the local side and the remote LDAP server values for the Prime-NetworkGateway resource on the remote side. Switch the Oracle service group to P2 and the Prime-Network service group to P1. For VVR, see Failing Back from the Secondary Site to the Primary Site, page Verify that the gateway starts correctly. Notifications Tip The Veritas administrator should perform the steps in this section. Notifications require a notifier resource in each cluster. As with the local cluster, the notifier must be created as a resource in the ClusterService service group. For a global cluster, this service group already exists in both clusters. If the operator wants to receive notifications, add a notification resource to the ClusterServer service group in the remote cluster. This setup ensures that notifications continue even after failover. DNS Tip The Veritas administrator should perform the steps in this section. In the event of a site-to-site failover or switchover, VCS updates the DNS server with the new address of the gateway. This way, applications that know the gateway by its hostname alias can reconnect without knowing the new IP address. To add a DNS resource, do the following: Step 1 Step 2 Verify that all servers are configured as a DNS client. Add a resource of type DNS to the Prime-Network service group in the local cluster with the following configuration: 10-55

56 Chapter 10 Resource Type: Key Attributes Critical Type-Specific Attributes Domain Alias DNS False Hostname Overridden Attributes None <Domain> <Local cluster Prime-Network SG IP> ana-cluster-ana Step 3 Step 4 Enable the DNS resource. Add a resource of type DNS to the Prime-Network service group in the remote cluster with the following configuration: Resource Type: Key Attributes Critical Type-Specific Attributes Domain Alias DNS False Hostname Overridden Attributes None <Domain> <Local cluster Prime-Network SG IP> ana-cluster-ana Step 5 Enable the DNS resource. Final Cluster Configuration At the end of the configuration process for geographical redundancy HA with VVR, the cluster resource views should resemble the following figures. The resource names might vary. The ClusterService service groups are not shown

57 Chapter 10 Figure 10-9 Geographical Redundancy Local Cluster Prime-Network Service Group 10-57

58 Chapter 10 Figure Geographical Redundancy Local Cluster Oracle Service Group 10-58

59 Chapter 10 Figure Geographical Redundancy Local Cluster Prime-Network VVR Service Group 10-59

60 Chapter 10 Figure Geographical Redundancy Local Cluster Oracle VVR Service Group 10-60

61 Chapter 10 Figure Geographical Redundancy Local Cluster Service Group 10-61

62 Chapter 10 Figure Geographical Redundancy Remote Cluster Prime-Network Service Group 10-62