Hi Alex Cat65k with SUP2-T does actually support configuration similar to MQC, its called C3PL. The issue you got is nothing card related, this is how QoS on the new Cat65k with SUP2T works, you cannot configure egress qos on Etherchannel Interfaces, it has to be done on the physical interfaces. You can get the Info here: http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/qoscampuscat6500sup2taag.html#wp1053910
" Ingress QoS policies on the Cisco Catalyst 6500 are configured on the logical Port-Channel interface (typically these are simply to enable DSCP trust, which is enabled by default on the Sup2T) , while egress QoS policies are configured on the physical port-member interfaces." regards Michel On 5 June 2013 13:05, Alex K. <[email protected]> wrote: > Hello everybody, > > > Some interesting problem I ran into recently – MQC not supported in output > direction on Sup-2T & WS-X6908-10G? > > Let consider following simple configuration: > > class-map AF1X > match ip dscp af11 af12 af13 > > class-map AF2X > match ip dscp af21 af22 af23 > > policy-map TEST > class AF1X > class AF2X > > interface po1 > service-policy output TEST > MQC features are not supported in output direction for this interface > > > > > As far as I know, the following combination – 6513E + Sup-2T + WS-X6908-10G > – does support MQC. I tried this configuration on 2 different boxes (same > hardware, different s/w) – same error. > > Any ideas will be appreciated. > _______________________________________________ > 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/
