Network limitation...

[ArizonaGeek]

Curious, is there a way to limit network usage for one specific VM guest?

Back story, I have an Win 2000 IIS FTP server that is always being attacked, I moved most of our customers to a new FTP server with MUCH better security but I have 5 users that are taking their time moving. I don't want to deny them access for a few more weeks but I would like to make their downloads much slower to "encourage" them to move to the new server.

Any help would be appreciated!

Cheers
Rob

The answer is always "PEBKAC!

 

[ArizonaGeek]

Oh, forgot to mention ESX 3.5.

Thanks!

The answer is always "PEBKAC!

 

[TechyMcSe2k]

see if they can limit that bandwidth coming in to the FTP site on your router. just thinking out loud

if:
the FTP server a VM instance?
Then:

http://www.vmware.com/support/esx15/doc/esx15_res4.html

else:
third party software or a Squid proxy??

 

[TechyMcSe2k]

That document for 1.5 but place to start.

Also, looking at my 3.5 cluster you can:

try creating another NIC just for that instance to use. You can then set Traffic Shaping to limit the bandwidth it uses

 

[ArizonaGeek]

Eh it is only until November 1 (maybe the 15th) so I don't want to make it real difficult. I can just limit them in IIS but was just curious if there was a way to do it on the ESX side of things.

I saw that link as well, but I think that is too much work for what I need.

Thanks though!

Cheers
Rob

The answer is always "PEBKAC!

 

[SimonDavies]

Surely you can limit this in the FTP server itself? On most other FTP server software configs I have seen (ServU for instance) allows you to limit both inbound and outbound data streams.

Simon

The real world is not about exam scores, it's about ability.

 

[ArizonaGeek]

Surely you can limit this in the FTP server itself?

Read my last post.

Cheers
Rob

The answer is always "PEBKAC!

 

[NickFerrar]

Not read the doc but presumably setting up a new port group specifically for the old FTP VM and throttling the bandwidth for the port group would do it (although that would affect the entire server's bandwidth not just FTP traffic). Much better to do it at the application level though.

 

[thalligan]

Best not to do traffic shaping at all. Flick the lights and tell the users it is EOL time "they don't have to go home but they can't stay here".

But if you want to have fun at no cost, you could create an internal port group "Firewalled". Move the system onto this network (Assuming it not AD integrated blah blah.)

Install a free host based firewall solution like IPCOP (Which has built in Traffic Shaping capability by port) With one adapter in the VM port group and one in the firewalled group. Then slowly ratchet down the traffic and enjoy the sequels.

On the ESX side Traffic shaping is pretty much an all or nothing proposition. Like I said probably best to just show them the door to the new FTP server.