If you look at the documentation for the Sup2T it does actually specify default trust when I looked yesterday. I was rather surprised myself.
-Blake On Fri, Jul 13, 2012 at 4:26 AM, selamat pagi <[email protected]> wrote: > You are right, according to 6500 documentation (not specific to sup2T or > 15.0) it should be untrusted by default. > > However, checking on a switch with no qos configured, we get the output > below. > > I assume that means all ports are trusted ...?? > > > VSS#sh queueing interface gi 1/2/1 > Interface GigabitEthernet1/2/1 queueing strategy: Weighted Round-Robin > > Port QoS is disabled globally > Queueing on Gi1/2/1: Tx Disabled Rx Disabled > > Trust boundary disabled > > Trust state: trust DSCP > Trust state in queueing: trust COS > Extend trust state: not trusted [COS = 0] > Default COS is 0 > Queueing Mode In Tx direction: mode-cos > > cheers, keti > > > On Thu, Jul 12, 2012 at 4:48 PM, Phil Mayers <[email protected] > >wrote: > > > On 12/07/12 15:02, selamat pagi wrote: > > > >> Hi > >> > >> On the interface level, I believe the command > >> *platform qos trust none remark * > >> can be used to ignore/discard incoming dscp/cos-value > >> > >> Is there a global command to disable trust ? > >> > > > > Isn't it the default? It was on sup720/Earl7 modules. > > > > ______________________________**_________________ > > cisco-nsp mailing list [email protected] > > https://puck.nether.net/**mailman/listinfo/cisco-nsp< > https://puck.nether.net/mailman/listinfo/cisco-nsp> > > archive at http://puck.nether.net/**pipermail/cisco-nsp/< > 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/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
