Sample System Diagram
[Figure] Example of System Configuration
이 페이지의 주요 내용
System Requirements
Hardware
CPU
At least 1Ghz or faster 32-bit (x86) or 64-bit (x64) processor.
Memory
Following memory capacity is needed to run MCCS service.
At least 1GB or more memory for system
At least 200MB or more for MCCS service
Disk
At least 500MB is needed.
Network Interface Card
At least 3 NICs (Network Interface Card) as below are needed to configure a mirror disk.
- NIC for Service
- NIC for Heartbeat
- NIC for Mirror
At least 2 NICs (Network Interface Card) as below are needed to configure a shared disk.
- NIC for service
- NIC for Heartbeat
Operating system
MCCS supports the following operating system.
- Up to Redhat Enterprise Linux 5 Update 6 x86 or x64
- Up to Redhat Enterprise Linux 6 x86 or x64 (Only supports Red Hat Enterprise Linux 6 x64 for PowerLinux.)
- Up to CentOS Linux 5 Update 6 x86 or x64
- Up to CentOS Linux 6 x86 or x64
Pre-installation Consideration
Common Information
MCCS 4.0 지원 브라우저
MCCS4.0 에서는 웹 브라우저를 통한 웹관리 콘솔을 제공합니다.지원하는 브라우저는 다음과 같습니다.
- Internet Explorer 8.0 이상
- Google Chrome 7 이상
- Fire Fox 4 이상.
Operating System and Software
Server redundancy for high availability is subject to the following two server environment must be configured identically.
- The sameOS version, Kernel Version
SE Linux must be disabled.
Network Manager service must be disabled.
If kernel modules that are used by the resources of the MCCS is ONDEMAND type, before resource online the module must be active.
In order to use MirrorDisk resource, you should pre-install DRBD 8.3.13.
For more details about DRBD installation, please refer to“8- Appendix DRBD Installation”of this document.)
IBM PowerLinux must be configured as below:
PowerLinux required Above PowerLinux JDK 1.8.0 64 bit version for installation.
PowerLinux required ZIP package to gather MCCS log.
PowerLinux does not support network cad that uses ehea driver module.
PowerLinux does not support mirror disk environment.
PowerLinux only supports Red Hat Enterprise Linux 6 x64.
Network Interface Card
At least 2 NICS as listed below are needed for shared disk environment.
- NIC for service : Used to client connection. This is also used for 2nd heartbeat.
- NIC for heartbeat : Used to communication path between nodes.
At least 3 NICs as listed below are needed for mirror disk environment.
- NIC for service : Used to client connection. This is also used for 3rd heartbeat.
- NIC for heartbeat : Used to communication path between nodes.
- NIC for mirror : Used to replicate the data of local disk to target disk. This is also used for 2nd heartbeat.
(Number of virtual IP can be different according to the customer's environment)
When configure Active-Standby server environment, virtual IP for service is managed in cluster and it should be the same bandwidth as IP of active and standby server.
Giga LAN is recommended for network for data mirroring.
Before installing MCCS, all network connection should be checked first through Ping test. Latest driver installation of NIC manufacturer is recommended for driver of network card.
When you assign an IP address on each NIC for service, heartbeat and mirror, Each IP address should not be on the same subnet among them. But each pair of them between nodes must be on the same subnet.
IP Address
Each node in a cluster should have at least one IP address for every NIC to be used by MCCS. Virtual IP addresses which is switchable between nodes which communicate to clients also should be reserved. (The number of virtual IP address can be variable according to the clients' needs.)
When you reserve virtual IP addresses, this must be on the same subnet as the real IP address of the NIC of node. For example, if the real IP address of the NIC is 10.10.10.10/255.255.255.0, virtual IP addresses that MCCS uses on that NIC must be in the form 10.10.10.x/255.255.255.0 where x is any unassigned number from 1 to 254.
Firewall
MCCS basically uses TCP/UDP port from 14321 to 14324 and it is done mostly automatically.
That ports are registered in linux iptables during installation automatically.
웹포트 및 미러 디스크 관련 포트는 방화벽에 자동 등록되지 않습니다. 또한 기본 포트를 변경했을 경우, 방화벽에 사용자가 변경해야 합니다.
Disk
Mirror Disk
- Either volume size should be the same on both servers or volume size of standby server should be bigger for mirror disk environment.
- MCCS supports DAS, SAN, iSCSI
(However, MCCS does not replicate the data on network driver like NAS.)
Shared Disk
- Support SAN, DAS and iSCSI.
스카시 예약 디스크
- SAN 프로토콜 중에서 SCSI3-PR을 지원하는 공유 스토리지를 지원합니다.
User Program
MCCS detects not only the physical resources but also the user program listed below.
- Process service in a form of single process.
- Application service that consists of several processes of application.
- 리눅스에서 실행되는 리눅스 서비스
When failure occurred in a group, MCCS will online the service resources on the standby which runs the same resources on the active. Users need to add the service resources mentioned above to manage by MCCS.
Please refer to "7-Resource of MCCS User Guide" for more details about adding a resource by the user .
Before adding a resource, user should decide what kind of service of resource and read the following in advance and these attributes will be set.
- Process Service
- Directory where program of Process is registered
- Program name in a form of single process that executable
- The name of the account that you want to run
- Application Service
- Directory location of script files of the program to register Application
(Please refer to " 7-Resource of MCCS User Guide" for more details.) - The name of the account that you want to run
- Directory location of script files of the program to register Application
- 리눅스 서비스
- 리눅스 서비스 관리자에 등록된 해당 서비스의 시작 레벨을 'OFF'으로 변경
- 리눅스 서비스 관리자에 등록된 양 노드의 동일한 서비스명
Checklist for Installation and Configuration
Following is the checklist for installation and configuration for MCCS.
구성요소 | Node1 | Node2 | ||
---|---|---|---|---|
Active(Source) | Standby(Target) | |||
Network Info. | Hostname | |||
Service Network | NIC Name | |||
IP Address | ||||
Subnet Mask | ||||
Virtual IP Address | ||||
Heartbeat Network | NIC Name | |||
IP Address | ||||
Subnet Mask | ||||
Heartbeat Network | NIC Name | |||
IP Address | ||||
Subnet Mask | ||||
Disk Info. | Shared Disk Volume | |||
Mount Point | ||||
Application Info. | Protection Service | |||
Protection Process | ||||
Protection Application |
Following is a sample checklist for MCCS installation and configuration..
구성요소 | Node1 | Node2 | ||
| Active (Soruce) | Standby (Target) | ||
Network Info.
| Hostname | tom | jerry | |
Service Network
| NIC Name | eth0 | eth0 | |
IP Address | 210.169.4.2 | 210.169.4.3 | ||
Subnet Mask | 255.255.255.0 | 255.255.255.0 | ||
Virtual IP Address | 210.169.4.1 / 255.255.255.0 |
| ||
Heartbeat Network
| NIC Name | eth1 | eth1 | |
IP Address | 10.10.10.1 | 10.10.10.2 | ||
Subnet Mask | 255.255.255.0 | 255.255.255.0 | ||
Heartbeat Network
| NIC Name | eth2 | eth2 | |
IP Address | 20.20.20.1 | 20.20.20.1 | ||
Subnet Mask | 255.255.255.0 | 255.255.255.0 | ||
Disk Info. | Shared Disk Volume |
| /dev/sdd1 |
|
Mount Point | /Oracle | |||
Application Info.
| Protection Service |
| vsftpd |
|
Protection process | Custom Process | |||
Protection application |
| Oracle |
|