120 likes | 356 Views
Preparing a Site for VCS Implementation. Topic 1: Planning for Implementation. After completing this topic, you will be able to plan for implementing VCS. The Implementation Plan. Prepare a plan stating the impact of VCS implementation on running services and operations.
E N D
Topic 1: Planning for Implementation After completing this topic, you will be able to plan for implementing VCS.
The Implementation Plan • Prepare a plan stating the impact of VCS implementation on running services and operations. For example, you may need to add network interfaces, patch the operating system, or upgrade applications. • Determine how to minimize downtime for existing services, taking into consideration the time needed for operational testing. • Plan any actions necessary to prepare the environment for VCS installation as described throughout this lesson. Consider how these activities may affect running services. • Prepare or complete a design worksheet that is used during VCS installation and configuration, if this worksheet is not provided.
Topic 2: Hardware Requirements and Recommendations After completing this topic, you will be able to describe general VCS hardware requirements.
Hardware Requirements and Recommendations • Hardware requirements: • Supported hardware (HCL) • Minimum configurations • Redundant cluster interconnect • Hardware recommendations: • Redundant public network interfaces and infrastructures • Redundant HBAs for shared storage (Fibre or SCSI) • Redundant storage arrays • Uninterruptible power supplies • Identically configured systems • System type • Network interface cards • Storage HBAs • support.veritas.com • www.veritas.com
5 7 SCSI Controller Configuration Requirements • Not applicable for fibre attached storage • If using SCSI for shared storage: • Use unique SCSI IDs for each system. • Check the controller SCSI ID on both systems and the SCSI IDs of the disks in shared storage. • Change the controller SCSI ID on one system, if necessary. • Shut down, cable shared disks, and reboot. • Verify that both systems can see all the shared disks. scsi-initiator-id scsi-initiator-id Typical default 7 Solaris AIX HP-UX Linux
Hardware Verification Inspect the hardware: • Confirm that the hardware being used in the implementation is supported. • Cable the cluster interconnect. • Ensure that the hardware is configured properly for the HA environment: • Confirm public network connectivity for each system. • Confirm that multiple channels to storage exist. • Can the operating system detect all storage? • Are arrays configured properly?
Topic 3: Software Requirements and Recommendations After completing this topic, you will be able to describe general VCS software requirements.
Software Requirements and Recommendations • Software requirements: • Determine supported software. • Modify the PATH environment variable. • Software recommendations: • Use the same operating system version and patch level on all systems. • Use identical configurations: • Configuration files • User accounts • Disabled abort sequence (Solaris) • ssh or rsh configured during installation • Use volume management software for storage. • support.veritas.com • www.veritas.com
Software Verification Inspect the software: • Confirm that the operating system version is supported. • Verify that the necessary patches are installed. • Verify that software licenses are available or installed for VCS and applications. • Verify that the operating system and network configuration files are the same. • vlicense.veritas.com • Sales representative • Technical Support for upgrades
Topic 4: Preparing Cluster Information After completing this topic, you will be able to prepare your environment for VCS installation.
Preparing Cluster Information Verify that you have the information needed for the VCS installation procedure: System names License keys Cluster name, ID number Network interfaces for cluster interconnect VCS user names and passwords Network interface for Web GUI IP address for Web GUI SMTP server name and e-mail addresses SNMP Console name and message levels Root and authentication broker nodes for security Optional