Help with applying service-policy to Fast Eth interface

[bigjerms]

I am trying to apply an inbound policy map on a Fast Ethernet interface to set the dscp values of certain packets (VOIP QoS)

when I issue the: 'service-policy input "policy-name"' command the router acts like it takes the command, but when I do a show run, or a show policy-map interface fasteth0 it does not show the policy bound on to that interface.

This is a cisco 1700 router running IOS 12.1(5)T15.

I have verified that the interface is in it's default queuing mode (FIFO.)

I'm not sure where else to look, I've done a lot of searching on google and cisco and am drawing a blank.

Here are the corresponding snipps from the config:

access-list 100 permit udp any any range 16384 32000
access-list 100 permit tcp any any eq 1720
access-list 101 permit tcp any any eq 3389
access-list 102 permit tcp any any eq 80
access-list 110 permit ip any any
!
class-map voip
match access-group 100
class-map terminal-svcs
match access-group 101
class-map http
match access-group 102
class-map default
match access-group 110
exit
!
policy-map dscp_marking
class voip
set ip dscp 46
class terminal-svcs
set ip dscp 12
class http
set ip dscp 26
class default
set ip dscp 0

I am applying it to the FastEth interface witht the following command:

service-policy input dscp_marking

Any help would be appreciated.

 

[KiscoKid]

I've seen this happen on interfaces where the interface didn't have some kind of bandwidth or shaping defined on it. In particular, if you apply a service policy to an ATM interface with some kind of PVC shaping in place (e.g. ubr, cbr etc). However I've never seen it on Ethernet interfaces except when someone has tried to take more bandwidth with CBWFQ than is available on the bandwidth (that's not the case here as you've made no bandwidth allocations at all however).

Therefore the only thing I can recommend is a combination of the following:

1. You're running pretty old IOS so I would review the bug toolkit on cisco.com for your IOS release and try and see how many service policy-related bugs there are. I would say over the amount of time since that IOS was released, there will be a few.


2. Upgrade to the IOS to something more recent and try the operation again.

I honestly cannot think why this is not working for you as I've applied service policies to all kind of interfaces before and I've only seen what you've described once before(as above)

 

[KiscoKid]

Had another thought about this. In case you're not aware, you can't deploy CBWFQ on Ethernet sub-interfaces. Is this what you are trying to do (albeit I would expect it to generate an error if you were) but the IOS is pretty old so maybe not.

 

[bigjerms]

Thank you for the reply, I will look into the bug-track @ Cisco.