3. Requirements and Considerations for Configuration
Sample System Diagram
[Figure] Example of System Configuration
Table of Contents
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
It is recommended 3 NICs(Network Interface Card) as below are needed to configure a mirror disk.
NIC for Service
NIC for Heartbeat
NIC for Mirror
It is recommended 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.
Windows 2008 Standard, Enterprise Edition SP2 32bit or 64bit
Windows 2008 R2 Standard, Enterprise Edition SP1
Windows 2012 Standard, Datacenter Edition
Windows 2012 R2 Standard, Datacenter Edition
Windows 7 Enterprise SP1 32bit or 64bit
Windows 8 Enterprise ,Windows 8.1 Enterprise 32bit or 64bit
Note
MCCS dose not support Windows 2008 SMB and 2012 Essential Edition
Pre-installation Consideration
MCCS supporting browsers
MCCS provided the web management console through a web browser. The following types of browsers are supported.
Internet Explorer 8.0 or higher
Google Chrome 7 or higher
Firefox 4 or higher
Operating System and Software
Two servers should have the same environment as below for server redundancy.
Windows OS version, Service Pack & Windows update (both)
Same WorkGroup/Domain Environment
Same administrator account and password
Same OS time
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.
Three processes which are Mccs Web Console.exe, MccsServer.exe, and MccsAgentService.exe are registered in the window firewall during installation automatically.
The ports that are registered during installation automatically: 137, 138, 139, 445, 9999, plus ports in the 10000 to 10025 range, depending upon which volume letters you plan on replicating.
