Recursos para Profissionais de TI >
Página Inicial dos Fóruns
>
Clustering
>
Adding multiple Subnets
Adding multiple Subnets
Does anyone know how to add multiple subnets to the cluster, i have two network adapters one is private network the other is public. the public ip range differs to the ip range i would like the add a service, they are on the same vlan but i am restricted to only adding services to same subnet as the public nic.
I have tried adding an additional ip address to the nic but this fails, is there another way of doing it? i was thinking another nic and setup routing but this seems a bit ott for a task which seems so simple.
Respostas
- You will not need to set up an additional route. When your server has a destination IP address it will AND it with both of your subnet masks/addresses to determine if it is local trafficbefore it attempts to send it to the gateway. What will happen is if your node needs to go to something on the 10.10.10.x network it will know that it's local and drop it on the line because it will determine it belongs to this network. If you are going to the 10.10.11.x network it also know it's local and drop on the line. If you are using a network address that's not in either of these it will send it to the gateway you have set up on your 10.10.10.x address because the ANDing for both of your masks with the IPs will determine that it is foreign.As far as why both addresses don't show up in cluster administrator under network I'm not sure. The column may just pull from the first IP settings, and never looks at the advanced properties of TCP/IP on that NIC. As mentioned it didn't prevent me from being able to use it with the additional subnet.... so you should be ok.
- Marcado como RespostaTim Quan - MSFTMSFT, Moderadorsegunda-feira, 30 de novembro de 2009 2:09
Todas as Respostas
- Maybe I'm not understanding. The first paragraph of your post is a tad garbled.... You have two network adapters on two different subnets?If that's the case there's really nothing special to this. If you look in your cluster configuration under network you should see the nic you have patched in to the other subnet. As long as it's there you can just create a new resource of type IP address. If you put a valid IP for that subnet it will automatically select the proper netmask and bind to the proper Network.Is this what you are doing? If so, what is the error you are getting when you try to add the ip resource?
- Sorry let me re-write it.
I have a cluster (two node) each node has 2 nics, one is for a private network (the heartbeat,etc) the second is for client file server traffic etc.
They both have different ips and are on different subnets, the public network is a member of say ip range 10.10.10.0/24 and the second node public is a member of the same ip range (with a different ip). Whenever i add a service it must be part of the 10.10.10.0 subnet, how do i add services that are on different subnets such as 10.10.11.0 as i cannot manually assign the ip address i am stuck on subnet 10.10.10.0. i assume this is because the public network adapter is on this range and i can only assign that.
I have tried adding another ip to the public nic on both nodes but that does not work, i can either use one or the other subnet not both on that same nic. Do i need to add another nic to each node on different ip range to use that subnet? - I just tested this on a DEV cluster, and it worked fine for me. Here's exactly what I did:1) Through TCP/IP properties I went into advanced and added a new IP for 192.168.1.10 mask 255.255.255.02) I opened cluster administrator and created a new cluster group called test... I enabled it for only the local node I was working on.3) I created a new IP resource in the cluster group with the address 192.168.1.99 mask 255.255.255.0... I ensured that this was using the NIC I configured the extra IP on in step 1... again I made the possible owners only the local node. I did receive a warning that the subnet mask could not be validated, but I continued anyway.4) Brought the IP resource online5) Pinged locally 192.168.1.10 and 192.168.1.99... both tests successful.While my test doesn't prove that there was network connectivity since I didn't do this on one of the other nodes, I'm fairly certain this worked like you are trying to make it work. I think the next question is what is failing when you add the second IP to the public nic. If you do that on both nodes you should be able to ping each other without going through your gateway.... you should probably do a tracert to verify that.If that works can you set up a new IP resource? I'm rereading your post now, and I don't see any mention that you created an IP resource after creating the new IP on the public NIC. While your NIC may have the new IP if your service is running as a cluster resource it will probably require a cluster resource IP address to work.
I tried to create a new ip source but again i can only see one ip subnet not them both on the same adapter, when i go to the network group in the cluster admin it only shows one subnet. I dont have to wait a few minutes or wait for it to scan to show two subnets do i as i waited about 1 min and only one subnet appeared.
When you entered in an IP, did you just enter ip and gateway?
I assume you have both nodes on the same subnet or are the nodes on different subnets?- I will try to rerun my test a little later this morning to see how the networks are represented in the network portion of cluster administrator.... When I entered the IP I entered IP and mask. You cannot have multiple gateways.... You can, however, set up additional routes if you need to force certain traffic through another gateway.Did you run the ping and tracert test after adding the NIC?Did you try adding the cluster resource?Both nodes have two networks. One is the heartbeat on one subnet, and the other is the public on another subnet. This sounds exactly like you have it set up, correct?
- yes that is correct in terms of the two networks.
The same subnet is not on both the private and the public.
i can add the cluster resource fine and i can manually enter in the ip address however when adding the ip address you can see the subnet you are adding the ip address to and i know the subnet display is incorrect. I also understand if i add another nic i can set out routes but i will be stuck with something similar and that is having the same subnet on both nics which is not good.
How are you adding more than one ip range/ subnet to your cluster as i can only seem to add one at a time, if i add two only one is displayed. - I just tested this completely with failover, and it does work. I am able to communicate over that new subnet between my cluster nodes using all IP addresses.... Both nodes, and the resource IP. I failed it over and was still able to communicate to all addresses from each node.You are correct. When looking at the networks within clusteradministrator you will only see one IP bound to your NIC. However, as long as you've added the second IP address you can use it.In your case you would do the following:NodeA:NicPubexisting IP 10.10.10.10 mask 255.255.255.0additional IP 10.10.11.10 mask 255.255.255.0NodeB:NicPubexisting IP 10.10.10.20 mask 255.255.255.0additional IP 10.10.11.20 mask 255.255.255.0Now you add a new IP resource with the IP 10.10.11.100 mask 255.255.255.0What are you doing different than I am?
- Sugerido como RespostaTome Tanasovski quarta-feira, 25 de novembro de 2009 16:32
- No that is exactly what i am doing but because you cannot see the see one ip bound to the nic and one subnet i stopped and thought it should display 2 as there is plenty of room for it to list the additional ip ranges. I will give it ago and see if it works, i was just a little concerned if you had to set up additional routing between the ip addresses
- You will not need to set up an additional route. When your server has a destination IP address it will AND it with both of your subnet masks/addresses to determine if it is local trafficbefore it attempts to send it to the gateway. What will happen is if your node needs to go to something on the 10.10.10.x network it will know that it's local and drop it on the line because it will determine it belongs to this network. If you are going to the 10.10.11.x network it also know it's local and drop on the line. If you are using a network address that's not in either of these it will send it to the gateway you have set up on your 10.10.10.x address because the ANDing for both of your masks with the IPs will determine that it is foreign.As far as why both addresses don't show up in cluster administrator under network I'm not sure. The column may just pull from the first IP settings, and never looks at the advanced properties of TCP/IP on that NIC. As mentioned it didn't prevent me from being able to use it with the additional subnet.... so you should be ok.
- Marcado como RespostaTim Quan - MSFTMSFT, Moderadorsegunda-feira, 30 de novembro de 2009 2:09
- Thats great thanks for your help, i did just what you said before posting and thought because the cluster admin does not report there being another ip range it would not work but it does.
What is really stange is, it works but when i come to adding another service on the previous ip range it works again but the ip range is no longer displayed!
