Packets that are generated by the router are not normally policy routed. However, you can use this command to policy route such packets. You might enable local policy routing if you want packets originated at the router to take a route other than the obvious shortest path.
The ip local policy route-map command identifies a route map to use for local policy routing. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteriathe conditions under which packets should be policy routed. The set commands specify the set actionsthe particular policy routing actions to perform if the criteria enforced by the match commands are met. The no ip local policy route-map command deletes the reference to the route map and disables local policy routing."
If you are expecting the packets from the router to be policy routed, then you must issue the
If this router is generating VOIP traffic, and you want to set precedence to critical, then, you should use the global command for policy routing ....viz....ip local policy route-map set-ip-prec. Because, the normal ip policy route-map command doesnt policy route, packets generated by the router itself.
What traffic are you trying to match ?, you have defined match clauses (VOIP, Permium, Gold, Silver) but do not appear to have defined what these reference (i.e. where are the named ACL's these reference).
Also what direction is the traffic flowing, policy routing is applied on input to an interface so if your traffic is flowing out of FE0/0 then the policy map will not be applied.
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...