Dont want to sound stupid here, but this has really got me confused. I have assigned ip addresses under the configuration to the vps external network list. If I then goto the ip address list and view vps external ip addresses I see the addresses I have added. In the db I see the addresses, the serverid is “nul” and the poolid is “3” this is 100% ok.
I then goto the user where I want to assign the ip address, click on hyper-v, then select vps menu > external network > then select allocate ip addresses, and zero addresses appear. and no matter what I do I cannot assign addresses, the quota says I still can assign 41 more addresses. Then if I look in the database at the ip address that is showing from previous additions when we were on 1.4.1 I see the ip is identified in the db as server “4” which is a remote hyperv core server, our second one we added, if I set the ips that I added to server id “4” in the db then I can allocate them to the user. If I try any other server id, they just dont show at all.
So My question is why are the ips not showing up unless they are assigned to this “4” server, which is a remote, and not even the primary vps server that controlling the other vps servers. And secondly surely there should be no server address assigned, untill you have allocated the ips to the users account and then added them to a vps surely.
It sounds like a possible issue with the hosting plan and its use of virtual servers. Can you confirm for me if you have a virtual server with both of the HyperV servers added?
How the code was created is once you assign a hosting plan to a customer it will then assign 1 server from the virtual servers to the plan (for each provider). What you are finding matches this as the server assigned to the hosting plan doesn’t have the IPs assigned to it which is why none are showing up.
At the current moment the best way to handle this is to assign a bunch IPs to each server and it will then use that pool for the server selected to get an ip address.
- Views963 times
- Answers3 answers