My guess is that shapers not supported on port-channel interfaces. We've got a similar issue and it's on my to-do list to convert the port-channel back to a single interface to test and see if this is indeed the problem with the shaper (you've just reminded me I need to do this !).
regards, Tony. >________________________________ > From: CiscoNSP List <[email protected]> >To: "[email protected]" <[email protected]> >Sent: Friday, 13 September 2013 5:58 PM >Subject: [c-nsp] policy map shape being "ignored"? > > >Hi Guys/Girls, > >7200/G1, have other policy-maps/shaping working without issue, but the >following one seems to be ignored? > >policy-map 10M >class class-default > shape average 9800000 104000 0 > >interface Port-channel1.1019 >encapsulation dot1Q 1019 >ip address xxx.xxx.xxx.117 255.255.255.252 >service-policy output 10M > > >#sh policy-map int po1.1019 >Port-channel1.1019 > Service-policy output: 10M > Class-map: class-default (match-any) > 1664453 packets, 1933030626 bytes > 30 second offered rate 55140000 bps, drop rate 0 bps > Match: any > Queueing > queue limit 64 packets > (queue depth/total drops/no-buffer drops) 0/0/0 > (pkts output/bytes output) 0/0 > shape (average) cir 9800000, bc 104000, be 0 > target shape rate 9800000 > >IOS bug? > > > >_______________________________________________ >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/
