Hi,

I´m a TP customer and I have the problem describe below:


This is my actually situation (and working):






After few VM´s in production, we need more ip´s to allocate in new vm server.

Look my new situation:




In single words: new IP´s dont work inside new VM´s (Linux 4)

Anybody can help me?


Tickets without solution: 5725926PLNT, 5720094PLNT

Ricardo AG,
If you are using a /24 subnet mask (255.255.255.0), the 174.133.3.1 gateway should be accessible. The issue here is that the new range was static routed to your physical server's main IP which would normally work. I have asked a supervisor in Technical Support to help move this request along. In ticket 5720094PLNT, it appears that we are waiting on a response from you.

If it is discovered that there is no way to use the new IPs in their current configuration, we may need to rebind them to your environment in a different way.

How did you get ESXi installed as the host OS at The Planet?
(Yes, I know; you cannot resell services with ESXi; good for testing though).

I payed $150 to TP for install.

I don´t resell this services, in our case it´s a better solution to grow up many servers with high cpu demand and low bandwith requirement.

Ah. Too pricey for "just testing." I'll continue to use my local server infrastructure.
Yea, I made the license agreement comment before someone else decided to say it.

Did you actually find a sollution to that?
I have a similar case: I wanted to setup a VMware Server inside my dedicated one, and assign a new block of IPs to it.