Hi guys
We have to increase the number of XenApp servers drastically which leads the IP address in our PVS LAN being not enough. Our method is to change the subnet mask of PVS LAN dhcp scope so that we can get more IP addresses to use. However I have to evaluate the risk of doing it. I need your help.
I'd like to introduce our IT environment to you first. We have a cluster with tens of Hyper-V hosts. We have 2 PVS servers, about 50 XenApp servers(for public desktop) and other management servers. There will be about 6,000 users using public desktops delivered by XenApp servers. And all the XenApp servers are connected will Business LAN and PVS LAN (the target of this work). Now I have to change the subnet mask of all the XenApp servers(change only happens on PVS Nic), the PVS servers(change only happens on PVS Nic) and also the hosts.
My plan is Step 1: I will change the mask subnet of all hosts first by using vmotion function. I mean I will migrant the VMs from host A to host B and change the subnet mask of host A, then get ex-host A VMs back meanwhile move the VMs on hosts B to host A so that I can do the same thing on host B. Here is a problem. If I changed the subnet of host A(just NIC for PVS), can I really get ex-host A VMs back from host B?
Step 2: I am gonna change the subnet mask of my Slave PVS server. I think it will not affect anything.
Step 3: As I did in step 1, I plan to change subnet mask of XenAPP servers by similar method. I mean I will cut the network of XenApp server 1 off so that users will use other XenApp servers except XenApp server 1. Then I can change the subnet mask of XenApp server 1 with no user using this server. The rest can be done in same manner I think.
Step 4: Finally I will deal with the main PVS server.
Certainly I have to change the subnet mask of the rest management servers by turns.
I am not sure if you could understand my plan. If you could or have such experience, put judge it for or give me some advice.
Thank you