http://tinyurl.com/n3qoq55
Ingress Queuing is only supported on the 24x10GE module, none of the 100GE or 36x10GE modules (either -SE or -TR) support it. Ingress queueing is not something a lot of hardware supports. The 2x100GE module uses a separate ingress NP and egress NP, but the amount of memory needed to queue packets coming in at 100Gbps for even a small amount of time is enormous. I would check with the account team but I would be surprised if the linecards ever supported it. Phil On 7/16/13 8:45 PM, "Harvey Young" <[email protected]> wrote: >Hello Experts, > >I am trying to configure ingress QoS on a 2 x 100 GIG- SE (typhoon) module >on the ASR to test ingress classification and honoring > >Using the latest code 4.3.1. > >What I have created is an ingress class map and associated it to a policy >policy map. Then applied the policy map to the interface. The command >fails. > >LC/0/1/CPU0:Jul 16 16:38:31.388 : qos_ma_ea[318]: >%QOS-QOS_EA_VERIFY-6-ERROR : QoS EA verify policy failed, error Policy: p0 >class: ef depth: 0 action: bandwidth not supported by platform: 'qos-ea' >detected the 'warning' condition 'Ingress queueing features is not >supported on this line card' > >The same policy can be applied to a 10 GIGE (typhoon) interface. > >Anyone know why ingress qos is not supported on the 2 x 100 G? Is there >another way to configure this? I looked through the user manual, no dice. > >Harvey >_______________________________________________ >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/
