MSCS installation

Question

Hi,
Im planning for new MSCS clustter installation of ECC 6.0 with SQL 2005 on windows 2003 server.
There is two nodes with one shred drive.
Assuming both nodes are MSCS clustterd and I need to start with SAP installation -
Had gone thru Inst docs too and have few pts to discuss-
Plz correct me if im wrong -
On Node 1st
   - install SQL server on 1st node
   - install central service instance
   - install central service instance for ABAP
   -  clustter first node
   - install central instance
On Node 2nd
   - install SQL server on 1st node
   - install central service instance
   - install central service instance for ABAP
   - clustter 2nd node
   - install dialoge instance
Plz clarify these pts -
1.what is the difference between
    - central instance
    - central service instance
    - central service instance for ABAP
2. Do we need to install Enqueue replication server on all nodes. If yes, can I find it in SQL server DVD?
3. about IPs assigment -
  - do we need to have two network card on each nodes
- do wee need to have different range of IP for node to node communication and LAN access
  e.g    IPs         Host name      IPs      Host name
          10.0.0.1   nodeA       10.0.0.2  nodeB (direct commu)
         192.168.0.1 LANa    192.168.0.2 LANb (LAN commu.)
how do we assign IPs to -
cluster grp
sap cluster grp
database cluster grp
Many Thanks
Mani

Answer 1

Here are the details which may help you.
First, some cluster items.
1. You must have a IP which is free.  This needs to be able to be created in MSCS as a cluster resource and failed back and forth between nodes A and B.  Just right click and select create new resource, type IP Address I believe, and enter the IP you were given and the network mask.  Enable it, ping it, fail it over, ping it again.  After this is successful, delete the IP from cluster (SQL install will add it back in).
2.  You need to have the data drives (where you are going to store the data file for SAP - here, we use E for backup, F for tlogs, H, I, J, K ... N for data, O for log, and T for tempdb), and SQL master, msdb, tempdb, model data drive (here, we use W) in place.  All of these drives needs to be MSCS resources and able to be failed back and forth between nodes A and B.
3.  You should create a cluster group called "SQL Group" or something, ahead of time.  Put all the shared drives in this group as resources.
First, before you start, make sure you are logged into only node A and no one is logged into node B.
Components to Install Screen:
- SQL Server Database Services + Create a SQL Server failover cluster = both checked.
- Analysis Services = Not checked.
- Create an Analysis Server failover cluster = Not checked.
- Notification Services = Not checked.
- Integration Services = Checked.
- Workstation Components = Checked (why not, might as well be able to administer the database while logged into the database).
Feature Selection Screen:
- We disable full-text search, we just don't use it.
- Select the "Database Services" primary node and enter a local drive (e.g. D:\.  Don't worry about the folder, SQL will automatically create the folder stucture here.  SQL won't just dump everything on root of D:\)
- Select the "Data Files" sub-node and enter the shared MSCS drive you will be using for SQL master, msdn, tempdb, and model data files. (e.g. W:\)
- Select the "Client Components" primary node, enter another local drive with folder name (e.g. D:\MSSQL_Tools.  In this area, SQL does not automatically append the directory structure.)
Next Screens:
- Select default instance, it's fine.
- Enter Virtual Name.
- Enter the shared IP you tested from steps above.
- Select the cluster group for SQL you created (In this same screen, make sure you remember to select the shared drive for the SQL master, msdb, model, and tempdb - our example is W: drive).
- In the available nodes, select node B and click on Add.  (Node B should not be listed as unavailable, make sure MSCS is 100% functional before starting SQL setup).
- Enter an account and password that's admin on both nodes (probably you, the sys admin).
- Enter service account SQL will run under - Should not be your account
- For the domain groups for clustered services, it's just asking for default sysadmin in the database.  Just enter "Administrator" for both Server and Server Agent.  If it won't accept this, try "BUILTIN\Administrators".
- Pick authentication mode, doesn't really matter here, depends on your implementation.
- Select the "Binary order for code-point comparison, for use with the 850 (Multilingual) code page" (unicode) code page.
Install!