I personally use inbound policy maps for policing traffic. I don't know what type of service that you have from your ISP, but mine doesn't create policies to help us out. They only allow us to pass tags that they tell us they'll support and I have policies based around those. Policing inbound allows me to drop excess traffic. For example, I have SEP servers that sometimes users will come across the wan to get updates, but downloading those can take up a lot of the link. I have a policy that matches on my SEP servers source addresses and only allows them 10% of the link before it starts dropping traffic. Outbound on both ends of the link is fine for two-way communication in most scenarios.
In your scenario, your routed port is your egress port, so you could apply outbound there. Where is the current policy? Is it on your switch or router? I'd put it on my router and mark there if you're not doing an L2 markings.
My QoS policy is apply on the routed port on the router for outbound. My major problem is the user downloads the file and take up lots of bandwidth. My policy is allowed 15% of the link. Is it a good idea to apply the same outbound policy for the inbound in the same serial interface on the router? I just want the users to have under 15% bandwidth when they download and I can live with other inbound traffic. Any better way to implement? Any sample configuration is appriciated.
It's going to be very difficult to do what you're wanting if you don't know the source addresses. What happens is that once you go out to the internet, you'll be natting somewhere. You'll need to control what comes back into your public side and not to the private addresses. For example, if you nat 192.168.10.50 to 220.127.116.11, outbound you can control 192.168.10.50, but inbound you'll have to control what comes into 18.104.22.168. And not knowing the source address means that you can't differentiate downloads from normal web browsing.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...