IMHO it's a lot easier to simply implement traffic shaping to the one
machine that's doing the FTP transfers. Let's say your connected via
T1, well then just allocate 384K to that machine's IP number. I have
never found the prioritization stuff to work worth a damn unless you
had a link like a point-to-point link where the link was guarenteed
bandwidth.
Granted this restriction is in force at night too even when you have
the bandwidth - but it sounds like you don't want to do these transfers
at night.
If it was me I'd just simply restrict them to at night and let
the fools squawk about it. Even if your dumping a full T1 to your
clients during the day, unless they themselves have multiple T1s
your going to be tossing their Internet connection into the
toilet right when their own users want to use it.
Ted
-----Original Message-----
From: cisc...@puck.nether.net
[mailto:cisc...@puck.nether.net]On Behalf Of
ni...@precisionmillworks.com
Sent: Monday, January 03, 2005 3:11 PM
To: cisc...@puck.nether.net
Subject: [c-nsp] Cisco 3550 QoS to limit FTP
I'm trying to implement QoS on a 3550, here's the situation. I've got
about 400 hosts on my network. One machine is used to ftp large
files(2-4gig) to clients. Currently we only transfer these files at night
now, because it causes packet loss on our network. I want to be able to
give all of the FTP traffic coming from this machine a low priority,
telnet traffic on the entire network the highest priority and all other
traffic a medium priority, I don't mind giving all FTP traffic on the
network the lowest priority but it isn't needed. What's the best way to
approach this? I've looked at a lot of the documentation but it's a
little overwhelming with all of the options. Thanks for any input.
Nick Travis
3 messages in net.nether.puck.cisco-nsp[c-nsp] Cisco 3550 QoS to limit FTP
