Announcement

Collapse
No announcement yet.

Clustering configuration

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Clustering configuration

    am trying to setup a simple environment (virtual) to prove that when a Node in a cluster goes down, the other picks up.
    After much pain I think I may have this however I would love for people here to see if I have setup the system correctly?

    I want to make sure that for example, the disks are correctly configured. It's a
    simple 2 Node cluster on WS2008 R2.

    Configuration
    DC
    1 Private NIC
    IP: 192.168.1.2 Sub: 255.255.255.0 DNS Server: 127.0.0.1

    Node 1
    2 NICs. 1 NIC is a public nic.
    Private Nic 1: IP: 192.168.1.3 Sub: 255.255.255.0 Gateway: 192.168.106.1 <-- this is a VMWare thing I believe DNS: 192.168.1.2

    Node2
    2 NICs. 1 NIC is a public nic.
    Private Nic 1: IP: 192.168.1.4 Sub: 255.255.255.0 Gateway: 192.168.106.1 <-- this is a VMWare thing I believe DNS: 192.168.1.2

    VSAN
    So I am using Starwind to create iSCSI storage/targets on this virtual machine. Oh - I dont have much clue about iSCSI!

    VSAN IP: 192.168.1.5
    Sub: 255.255.255.0
    Gateway: 192.168.106.1
    DNS: 192.168.1.2
    I have 4 targets here.


    Clustering Info

    There are 2 nodes in this cluster, as you gathered from above.

    ClusterIP: 192.168.1.16
    ClusterName: w2k8r2-clstr


    Now, in regards to the disks, I see them as different volumes.
    Cluster Disk 1 is a Witness in Quorum
    Available Storage: Cluster Disk 2, 3, 4

    I see that if I reboot Node 1, the disks appear in my computer on Node 2 If Node 2 is rebooted, I see the disks appear in my computer on Node 1
    is this the correct behavior? Have I missed something? wrong configuration?

    Thats all for now. I REALLY hope someone can help, I would appreciate it

  • #2
    Re: Clustering configuration

    What services are you using the Windows 2008 R2 cluster for? File services, Printers etc.

    By the sounds of it, the failover is happening as generally, only one node can own the disks at a time, which by the sounds of it, are iScsi targets. The best test is to see if the services remain available that the cluster is providing redundancy for.

    Comment


    • #3
      Re: Clustering configuration

      thanks.
      i encountered severe errors for some reason regarding the disks. sometimes they randomly failed to come online when both servers were idiling

      the test environment will be used for MSMQ. maybe file services also. but definately MSMQ

      im now sitting here, AGAIN, recreating the cluster.

      am I correct in saying that the VSAN, Node1 and Node2 should have a dedicated iSCSI NIC?
      if so, then I take it that from the Node1 and Node2 using the iSCSI initiator, I should use that iSCSI NIC IP (set in the VSAN) to connect to it?

      After that, do I make the disks go online, initialise it and format it as NTFS on Node1? (It would then mount it there) - after this I am guessing I need to run the validator for the cluster and start to create a cluster

      currently using Starwind to create the target and 3 disk images and then initialising and connecting them from the Node1 and Node2

      Comment


      • #4
        Re: Clustering configuration

        Yes, use a dedicated NIC for iScsi for Node1 and Node2. Ideally, you want it to support iScsi-3 for the SAN.

        On the SAN, you will present the disks (volumes) to both nodes and then ensure both nodes have the iScsi initiator configured.

        On one of the nodes, format the volumes (disks) as required.

        Install the Failover clustering feature on each node.

        Then validate the cluster configuration.

        Create the cluster configuration.

        Configure the cluster for the service you are making highly available.

        Comment


        • #5
          Re: Clustering configuration

          Great! Thank you. no wonder you are an MVP , truly deserve it

          OK, so I already get a DNS problem in the clustering events:

          Cluster network name resource 'Cluster Name' failed to update the DNS record for name 'w2k8r2-clstr.test.me.com' over adapter 'Local Area Connection'. The error code was 'DNS bad key. (9017)'. Ensure that a DNS server is accessible from this cluster node and contact your DNS server administrator to verify the cluster identity can update the DNS record 'w2k8r2-clstr.test.me.com'.

          thoughts?

          I am viewing this on Node1.

          Node1 network details:

          LAN

          IP: 192.168.106.150 + 152 (Auto assigned. probably from VMWare)

          Sub: 255.255.255.0

          DNS: 192.168.106.2



          LAN2 (Domain)

          IP: 192.168.1.3

          Sub: 255.255.255.0

          gateway: 192.168.106.1

          DNS: 192.168.1.2



          iSCSI NIC

          IP: 192.168.20.3

          Sub: 255.255.255.0

          Comment


          • #6
            Re: Clustering configuration

            Thanks for the comment. I am not actually an MVP but have been an MVM on here before. Verify that Node 1 and 2 and the DNS server are in the same subnet or IP routable to each other. If I was you, use static IP addresses. The DNS server IPs and subnet are different for LAN and LAN2. What LAN does the nodes in the cluster and DC (also DNS server I assume) sit on? Worth doing a ping test and doing an nslookup to see if you can query the DNS server. The cluster will rely on AD and DNS.

            Comment


            • #7
              Re: Clustering configuration

              all the computers can ping each other no problem.
              The DNS Server is on the DC and all NICs have static IP's assigned to them and believe they are all in the same subnet.

              Here is the configuration:

              DC
              LAN
              IP: 192.168.1.2
              Subnet: 255.255.255.0
              DNS: 127.0.0.1



              Cluster Node1
              LAN (auto config)
              IP: 192.168.106.150
              Subnet: 255.255.255.0
              DNS: 192.168.106.2

              LAN 2 (domain)
              IP: 192.168.1.3
              Subnet: 255.255.255.0
              DNS: 192.168.1.2
              Gateway: 192.168.106.1


              Cluster Node2
              LAN (auto config)
              IP: 192.168.106.151
              Subnet: 255.255.255.0
              DNS: 192.168.106.2

              LAN 2 (domain)
              IP: 192.168.1.4
              Subnet: 255.255.255.0
              DNS: 192.168.1.2
              Gateway: 192.168.106.1

              Comment

              Working...
              X