Following are requirement for AD & IP:
Active Directory Requirements
1. Cluster nodes must be member of same Active Directory Domain Services
2. The servers in the cluster must use Domain Name System (DNS) for name resolution
3. Use cluster naming convention for example Production Physical Node: DC1PPSQLNODE01 or Production virtual node DC2PVSQLNODE02
Unsupported Configuration
the following are the unsupported configuration:
1. Do not include cluster name with these characters like <, >, “,’,&
2. Never install SQL server on a Domain Controller
3. Never install cluster services in a domain controller or Forefront TMG 2010
Permission Requirements
System admin or project engineer who will be performing the tasks of creating cluster must be a member of at least Domain Users security group with permission to create domain computers objects in Active Directory and must be a member of administrators group on each clustered server.
Network settings and IP addresses requirements
You need at least two network card in each cluster node. One network card for domain or client connectivity and another network card heartbeat network which is shown below.
IP Requirements for 2 node cluster:
The following are the unique requirements for MS cluster.
1. Use identical network settings on each node such as Speed, Duplex Mode, Flow Control, and Media Type.
2. Ensure that each of these private networks uses a unique subnet.
3. Ensure that each node has heartbeat network with same range of IP address
4. Ensure that each node has unique range of subnet whether they are placed in single geographic location of diverse location.
Domain Network should be configured with IP Address, Subnet Mask, Default Gateway and DNS record.
Heartbeat network should be configured with only IP address and subnet mask.
Additional Requirements
1. Verify that antivirus software is not installed on your WSFC cluster.
2. Ensure that all cluster nodes are configured identically, including COM+, disk drive letters, and users in the administrators group.
3. Verify that you have cleared the system logs in all nodes and viewed the system logs again.
4. Ensure that the logs are free of any error messages before continuing.
5. Before you install or update a SQL Server failover cluster, disable all applications and services that might use SQL Server components during installation, but leave the disk resources online.
6. SQL Server Setup automatically sets dependencies between the SQL Server cluster group and the disks that will be in the failover cluster. Do not set dependencies for disks before Setup.
7. If you are using SMB File share as a storage option, the SQL Server Setup account must have Security Privilege on the file server. To do this, using the Local Security Policy console on the file server, add the SQL Server setup account to Manage auditing and security log rights.