OK, I have sort of figured out a way to do the outbound part of this. Think 1811, with 1 downstream to server 2 upstreams to core router, 1 with BGP - Private AS taking routing feed of Peering routes (about 4000) Other upstream default route for anything not on peering - link QoS'd to 1 MB.
This seems conceptually ok for outbound...but Problem... inbound. How does the inbound traffic know which link to go back in. Any thoughts? ...Skeeve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Skeeve Stevens Sent: Monday, 6 August 2007 1:30 AM To: 'Cisco NSP' Subject: [c-nsp] Is destination based rate-limting (QoS?) possible Hey all, I have a situation where it has called for a single Ethernet port into either a 3550, 3560G or 3750G (have all 3), where we want to provide an Ethernet service which is rate-limited to 1MB for normal traffic, and at 100MB for peering traffic (based on a BGP feed). Basically, a single server with a single Ethernet connection. We want them to be able to use the peering traffic at full speed, but normal transit limited to a specific amount - i.e. 1MB. This might need more explanation.. please ask away. -- Skeeve Stevens, RHCE [EMAIL PROTECTED] / www.skeeve.org Cell +61 (0)414 753 383 / skype://skeeve eintellego - [EMAIL PROTECTED] - www.eintellego.net -- I'm a groove licked love child king of the verse Si vis pacem, para bellum _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
