Skip to Content
avatar image
Former Member

MSCS installation

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Jun 30, 2008 at 10:07 PM

    Hi Mani, what you are looking to do is actually.

    Prep the MSCS:

    1. You don't need multiple NICs. You just need to bind muliple IPs to the same NIC. You can have multiple NICS but it will be for stuff like NIC teaming (high availability setup). But it's completely optional.

    2. You will need a physical IP on each of the physical nodes.

    3. In addition, you will need 3 more static IPs.

    - 1 static IP for the MSCS virtual name.

    - 1 static IP for the SQL virtual name.

    - 1 static IP for the SAP virtual name.

    4. Create 2 seperate cluster groups: SQL and SAP

    Install SQL:

    SQL 2005 cluster install allows you to install SQL on all nodes on the MSCS all at the same time. This means, you run the install on cluster node 1 and this will install the SQL engine on the entire MSCS. No need to reinstall SQL engine again on cluster node 2.

    1. Run the SQL 2005 install on cluster node 1. Choose to install both SQL engine and client components. After this step, you will have a MSCS with SQL 2005 engine running (and able to failover between different MSCS nodes), and client tools installed on cluster node 1.

    2. You will however still need to install SQL 2005 client tools on cluster node 2. Just run the SQL install again, but choose only client tools.

    3. Make sure MSDTC is a resource in SQL MSCS group.

    Install SAP:

    1. Do a cluster install. When referencing the SQL server, make sure to reference not the physical node name but use the virtual name.

    2. After the cluster install, verify that SAP is not installed w/ cluster node physical name. Make sure SAP is using a virtual name too.

    central instance - in classic sense, it's a instance w/ message server and a ENQ dialog process. SAP introduced a SCS (SAP Central Services) instance, which is basically the message server and ENQ as individual processes. SCS is used if you want to use replicated enqueue.

    replicated enqueue server needs to run on all nodes. I am not sure which DVD you will find this, but it is definitely not on the SQL server DVD. This is a SAP technology.

    Hope this helps.

    Edited by: Kevin Lin on Jul 1, 2008 12:07 AM

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      We can't post mail address here, the system won't allow you to and is against the rules. If you have any ideas on how I can verify your install, please let me know. Thanks.