[c-nsp] QoS with Traffic shaping on ATM OC3 on 7206

[Nasses, Gus]

Aha, Tim. After upgrading IOS here was an error in the log that did not show
up when entering commands. Here it is: 

*Oct 22 12:18:52:  GTS : Not supported over ATM VCs

I cannot apply this policy to either the ATM subinterface, or major ATM
interface, as it won't accept the command and tells me that CBWFQ is not
supported. 

So, I guess the question is how to do traffic shaping at all? I REALLY need
to as this is an OC3 on this end, but only 3xT1 bundle on the other end of
this particular traffic and it can certainly be assymetrical, with a response
to their request sending more data than the remote can handle which would be
bad especially with the real-time traffic. This is the first remote site we
want to cut to this infrastructure, but there are likely to be more of
varying speeds but all significantly lower speeds than the OC3 end. 

-----Original Message-----
From: Tim Franklin [mailto:tim at pelican.org] 
Sent: Thursday, October 22, 2009 10:17 AM
To: Nasses, Gus
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] QoS with Traffic shaping on ATM OC3 on 7206

> I am having trouble getting a policy-map with traffic shaping and a
> child QoS policy to apply to an ATM OC3 interface on 7206 router.
> Cisco TAC recommended IOS upgrade (as always) to 12.4(25b) but this
> did not help. The PVC on the subinterface will take the command, and
> if I do a 'do show run' I see it as applied, but a 'do show policy-map
> int' shows no output and as soon as I exit out of command mode the
> command does not show in running-config. I suspect that somehow this
> is not supported on PVC and not giving a clear error message, but it
> errors when tried to apply to subinterface or main interface.
> If so, does anyone know if there is another way to accomplish this? 

In respect of the "no error", have you tried "show log"?  I've had issues
before with silent-fail QoS config that doesn't print anything to the
terminal, but does log the reason in the background.

In terms of making it work, I believe you either want the nested policy
applied to the sub-interface rather than the VC (and let the outer shaper
provide the back-pressure), or apply just the inner policy to the VC (and let
the vbr-nrt settings provide the back-pressure).

Regards,
Tim.