You're leaving out what your service policy looks like, which is where my hunch says the problem lies.
On Wed, Aug 10, 2011 at 13:28, Jared Gillis <[email protected]>wrote: > Hi all, > > I just ran into an unusual problem when deploying some QoS onto a 7606 in > my network. I was configuring all ports to trust DSCP input, and after > applying the command to all the physical ports, I went to apply it to my the > port-channels. Shortly after I did, IS-IS went down (timeout) on the L3 > links across those port-channels. IS-IS came back when I removed the trust > DSCP command. I've done some searching around and can't find any reference > to this feature/bug/wtf anywhere. Does anyone have any knowledge about why > this would happen? > > Here's my PO config: > interface Port-channel1 > switchport > switchport trunk encapsulation dot1q > switchport trunk allowed vlan 200 > switchport mode trunk > mtu 9216 > load-interval 30 > service-policy input SONIC-DEFAULT-QOS > > And the command I entered was "mls qos trust dscp". > > Thanks > > -Jared > _______________________________________________ > 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/
