1 / 48

Ionix ControlCenter 6.1 in a Cluster

Ionix ControlCenter 6.1 in a Cluster. Jim Stringer Ionix Corporate System Engineer April 29, 2010. Introduction. Jim Stringer Principle Corporate System Engineer Ionix Services Engineering, Ionix Engineering Joined Engineering 2007 Experience with ControlCenter Since 2002

rayya
Download Presentation

Ionix ControlCenter 6.1 in a Cluster

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ionix ControlCenter 6.1in a Cluster Jim Stringer Ionix Corporate System Engineer April 29, 2010

  2. Introduction • Jim Stringer • Principle Corporate System Engineer • Ionix Services Engineering, Ionix Engineering • Joined Engineering 2007 • Experience with ControlCenter • Since 2002 • Started with ControlCenter 5.0.3 • Sr. Solutions Architect • SME for • ControlCenter HA and HA/R • ControlCenter Environments exceed P&S Guidelines

  3. What is a Cluster

  4. Cluster Basics (Physical) • Two or more Hosts (Windows 2003 Enterprise or Datacenter) • C:\ is local (not shared) • Two or more SAN Storage devices • Q:\ - Quorum (500 mb) • E:\ - ECC • F:\ - ECCbackup • Two or more NICs per Host • Public Traffic • Internal Cluster Communications • Member of an Active Directory domain • DNS is resolution for Public network Host A Host B C:\ C:\ E:\ NIC NIC NIC NIC F:\ Q:\

  5. Cluster Basics (Virtual) • Cluster Administration • Virtual IP-Address • Virtual Network Name • Service User Account (non-expiring password) • Cluster Application • Physical IP-Address – Primary NIC • Network Name for the physical IP-Address • Will registry with DNS • Physical IP-Address – Alternate NIC or Heartbeat NIC with Cross-over cable • Network Name for the physical IP-Address

  6. What Cluster Configuration is supported • Microsoft Cluster configuration that is supported • As many nodes as Microsoft Cluster supports • Active / Passive ONLY • Any Shared SAN Storage • ControlCenter High Availability (HA) • Within a datacenter • What EMC Engineering has tested • Active / Passive • Two Node Cluster • Symmetrix SAN Storage • CLARiiON SAN Storage Node A Active NODE B Passive C:\ C:\ E:\ NIC NIC NIC NIC Heartbeat F:\ Q:\ ControlCenter HA

  7. What HA/DR Cluster Configuration is supported • ControlCenter High Availability (HA) • Within a datacenter NODE B Passive Node A Active Primary Datacenter Disaster Recovery Datacenter NIC NIC NIC NIC Heartbeat C:\ C:\ SRDF/CE or MV/CE E:\ E:\ R1 R2 SRDF/S MirrorView F:\ F:\ ControlCenter HA/DR Q:\ Q:\

  8. Cluster Administration • Cluster Group is for Cluster Administration only • Cluster Network IP and Name • Q:\ Quorum Disk

  9. Configuring the IP Networks

  10. Key Services Cluster Admin Account Service needed to start the cluster MSDTC is not needed Leave Disabled Delete from Cluster

  11. ControlCenter Components Supported in a Cluster • These ControlCenter Components are supported on a Cluster • CC Server • CC Repository • Key Management Server • Repository Monitor Service • API Server • Tomcat Web Server • Store • StorageScope Server • StorageScope Repository • Master Agent • WLA Archiver

  12. Preparing the Cluster to Install ControlCenter

  13. Preparing the Cluster for ControlCenter • Establish a ControlCenter Resource Group • Move the E:\ (ECC) and F:\ (ECCbackup) share Disks into this group

  14. Preparing the Cluster for ControlCenter • Establish a ControlCenter Resource Group • Move the E:\ (ECC) and F:\ (ECCbackup) share Disks into this group • Add the Virtual APP IP-address & Network Name which will be used by ControlCenter

  15. Handling Node B Pause Node B to prevent any cluster fail-over during the installation and during all maintenance periods Node B Paused

  16. Install ControlCenter • The node selected to install ControlCenter on becomes Node A • Primary Node • The Node for all maintenance • Install ControlCenter as it would be installed normally • Use the Application Virtual Network name as the Primary Network

  17. Install ControlCenter • Alternate Network • Select “none” when InstallShield asks for the Alternate Networks

  18. Install ControlCenter • Alternate Network • Select “none” when InstallShield asks for the Alternate Networks • Answer the InstallShield question • Let the installation run to the Finish screen • Select Reboot to finish the installation

  19. Modifications needed • Ecc_server.ini • Add the physical Network IP-Address to the name server aliases name server aliases = 10.247.52.152,10.247.52.153,192.168.30.152,192.168.30.153 • Ecc-Store.ini • Set the Store to use only “Fixed Ports” • Improves stability of the Store communications • Change the fixed port setting to “true” use fixed port = true • CTG.ini • Modify the Master Agent to be cluster aware • Add the following statement to the CTG.ini section marked [Default]… cluster = true

  20. ControlCenter Registry Dependencies • Edit the ControlCenter registry • Remove the DependsOnService Multi-String Value • Dependencies will be handled by the Cluster • HKLM\System\CurrentControlSet001\Services • EMC ControlCenter Repository • EMC ControlCenter Server • EMC ControlCenter Web Server • EMC ControlCenter StorageScope • Search and remove from all “ControlCenter” instances • Do not edit the EMC ControlCenter Master Agent Registry key

  21. Replication of Node A to Node B Replication Steps • Resume Node B • Run ClusterSave.bat • (\ecc\tools\utils) • Reboot Node A  Cluster will fail-over to Node B • Login to Node B • Run ClusterLoad.bat • (\ecc\tools\utils) • Reboot Node B  Cluster will fail-back to Node A • Login to Node A

  22. Putting ControlCenter into the HA Cluster • Add ControlCenter to the ControlCenter Resource Group • This is an example of an All-in-One ControlCenter Environment • The Host Agent is not supported in this configuration

  23. Building Cluster Dependencies E:\ Virtual IP-address F:\ Virtual Network Name

  24. Building Cluster Dependencies E:\ Virtual IP-address F:\ CC Oracle Repository Virtual Network Name Oracle TNS Listener STS Oracle Repository

  25. Building Cluster Dependencies E:\ Virtual IP-address F:\ CC Oracle Repository Virtual Network Name Oracle TNS Listener STS Oracle Repository ControlCenter Server

  26. Building Cluster Dependencies E:\ Virtual IP-address F:\ CC Oracle Repository Virtual Network Name Oracle TNS Listener STS Oracle Repository ControlCenter Server StorageScope Server

  27. Building Cluster Dependencies E:\ Virtual IP-address F:\ CC Oracle Repository Virtual Network Name Oracle TNS Listener STS Oracle Repository ControlCenter Key Management Server ControlCenter Server ControlCenter Repository ControlCenter API Server StorageScope Server ControlCenter Store ControlCenter Master Agent

  28. Building Cluster Dependencies E:\ Virtual IP-address F:\ CC Oracle Repository Virtual Network Name Oracle TNS Listener STS Oracle Repository ControlCenter Key Management Server ControlCenter Server ControlCenter Repository ControlCenter Web Server ControlCenter API Server StorageScope Server ControlCenter Store ControlCenter Master Agent

  29. Creating a Cluster Resource • Open the Services Applet • Select the Service you want to move to the Cluster • Note :Clustersave.bat scripts sets all ControlCenter related services to “Manual” • Copy the Service’s Display Name • Close the Service properties window

  30. Creating a Cluster Resource Cluster Administrator Applet • In the right plane, right-click • Select New, Resource

  31. Creating a Cluster Resource • Provide a Name and description • Resource Type is Generic Service • Group is the ControlCenter Group name Leave unchecked

  32. Creating a Cluster Resource • Possible Owners  Node A and Node B • Dependencies  Follow the dependencies given on slides 23 - 28

  33. Creating a Cluster Resource • Paste in the Service Name copied from the Service Applet  Hit Next • Leave the Registration Replication screen blank  Hit Finish Leave blank Leave unchecked

  34. Creating a Cluster Resource • Registry Replication • Leave Blank • Select “Finish” to add the resource • Resource will be add and left offline

  35. Bring the Cluster Resource Online With the ControlCenter Cluster group selected – Hit Bring Online

  36. ControlCenter 6.1 Maintenance

  37. Controlling Cluster Resources • Taking Resources Offline & Online

  38. Controlling Cluster Resources • ControlCenter is down, Oracle is up • ControlCenter is ready for patches to be installed

  39. Patching ControlCenter in a Cluster Rules • Patching ControlCenter in a Microsoft Cluster • All maintenance mustbe installed on Node A with Node B Paused • Patches and SQL Scripts can be installed without removing ControlCenter from the cluster. • Upgrades, Update Bundles and OCPU patches MUST have ControlCenter deleted from the Cluster • Services are started and stopped during the install process Node B Paused Delete this cluster resource will remove ControlCenter from the cluster

  40. Cluster Fail-over • Cluster Fail-over triggered by a problem • Under 20 seconds (HA) – Physical • Under 2-minutes (HA/DR with SRDF/S & SRDF/CE) • Cluster Move Group • Orderly shutdown and startup • About 4-minutes for an All-in-1 HA cluster to move

  41. Click on the image below to watch this 2-minute cluster move video…

  42. Resource Advanced Properties • Controls the Resource triggers • All testing and certification has been done using the defaults • Do not make changes for troubleshooting • Verify settings to this screen shot

  43. Opening a Cluster • Using the Open Cluster button • Find the cluster name in the drop-down bown • If not listed  enter a “.”

  44. ControlCenter 6.1 HA & HA/DR Examples

  45. What is a HA/DR solution • High Availability (HA) Cluster across two different Datacenters (DR) • With Symmetrix RDF connections using SRDF/CE • SRDF/S • SRDF/A • With CLARiiON Mirror View Connections using MV/CE • Solution is documented as a PS Engagement • PS_SRDFCE_PSCUSEMC.PDF

  46. ControlCenter HA Cluster Example Datacenter ControlCenter 6.1 Server Repository Master Agent Node A Active NODE B Passive C:\ C:\ Store-1 Store-2 VM E:\ E:\ NIC NIC NIC ControlCenter 6.1 Store Master Agent Host Agent NIC ControlCenter 6.1 Store Master Agent Host Agent Heartbeat F:\ BCV F:\ Q:\ ControlCenter 6.1 STS Server FLR Archiver DSS Repository Master Agent Host Agent WLA Archiver ControlCenter 6.1 Master Agent Host Agent WLA Archiver STS Server DSS VM VM E:\ E:\ E:\ E:\ F:\ BCV BCV F:\

  47. ControlCenter HA/DR Cluster Example ControlCenter 6.1 Server Repository Master Agent WLA Archiver E:\ NODE B Passive Node A Active BCV Primary Datacenter Disaster Recovery Datacenter F:\ Store-1 Store-3 NIC NIC NIC NIC Heartbeat C:\ C:\ SRDF/CE or MV/CE VM VM Deploy New VM and Recover ControlCenter 6.1 STS Server DSS Repository Master Agent Host Agent STS Server DSS ControlCenter 6.1 Store Master Agent Host Agent ControlCenter 6.1 Store Master Agent Host Agent E:\ E:\ R1 R2 VM SRDF/S MirrorView F:\ F:\ Store-2 Store-4 E:\ Q:\ Q:\ F:\ VM VM

  48. ^ virtualized

More Related