cluster test using vm2005 | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

cluster test using vm2005

Hi All,
Been trying to set up test cluster for Sql server 2000 on virtual server 2005, found useful link and followed the steps listed below Environment:
HOST OS windows XP SP2
Virtual Server 2005
Each node is running windows 2003 server SP1 In creating two nodes with the same "public" virtual network which uses my host OS network card. when I start both nodes one of the nodes is having problems getting a IP address from DHCP server so remains unconnected, it is conflict. But when create another public virtual netwrok using same network card and assign this node 2 it works fine i.e both have different IP addresses but both the nodes are not able to ping each other. The host machine on which VM2005 is running is able to ping both the nodes. Any ideas would be great Cheers[?]

Don’t use two different public networks. Use the same network for both nodes and set a static IP for each node, don’t use DHCP.
Thx ….i had tried using the same public network with dynamic …will try with static now. cheers
Tried using statis IP for both nodes , but one of the nodes is not able to connect to DHCP when trying to ipconfig /renew. They are not able to recoganize each other as before. Please suggest ??? Cheers
The static option I had enabled was "static Mac address" , in virtual server 2005 for each node using the same public virtual network.
Only with one Public virtual network shared by both nodes worked after removing the private virtual network…seems the private virtual network breaks it or something. Do I need to set up virtual network to achieve windows 2003 clustering and later sql server 2000 clustering ? Also does it make any difference if my test enviornment windows 2003 server are not activated yet ? Cheers
Not static mac address. Static IP, meaning you specify an IP address manually and don’t use DHCP. You should not run ipconfig /renew. Normally your private network is on IPs only used on that network for internal cluster communication (say and Then you have a public network that applications connect on. If you are setting up a test environment I guess you could use one single network that is for both internal cluster communications and for application communication. I’m not sure I understand your last question about active windows 2003.
Thx for the quick response…. you are right setting up IP addresses manually worked. Regarding the private network which would be used by the nodes for internal communication as you mentioned , do they need another network card which they share using the same virtual network or can the use existing one network card used by the nodes for public virtual network ? Yes it is a test environment which eventually will be used as model to build a real one, so want to understand the each stage. The last question is really related to OS installation and subsequent activation which is 60 day time period given by Microsoft..hope now Iam clear. Currently using the public network with two nodes , I was setting up the windows 2003 cluster on both nodes but when creating the cluster using the cluster wizard and it does the validation of both nodes I get the following error Which states for both nodes it gives the same message , any suggestions on this would be great !! –>Node2sat: checking the node feasibility gives error
Error 0x8007170a This computer cannot be made a member of a cluster –>Node2sat: Validating operating system version on thsi node
Error 0x8007170b This computer cannot me made the member of cluster because the
correct version of windows installed. Environment:
———— Microsoft Virtual server 2005
Both Nodes have Windows 2003 SP1 standard
Public network shared on one LAN card
Static IP’s now assigned and part of the domain.

According to this forum , it states that windows version required is windows 2003 Enterprise to set up cluster , is this right ? Can I not do it using the windows 2003 standard ? Cheers
You need one virtual network for the private network (often called heartbeat) and one virtual network for the public traffic. In practice this mean two network cards. Preferably you have even more cards so you can team two ports in failover mode. You need Windows 2003 Enterprise Edition to be able to cluster. The following SQL editions are needed for clustering:
– SQL 2000 needs Enterprise Edition
– SQL 2005 needs Standard Edition for two nodes and Enterprise Edition for 4 or more nodes.
Thx ….again !! Cheers