[c-nsp] mls qos trust dscp on 7600 port-channel breaks IS-IS?

[Andrew Jones]

perhaps you should open a TAC case?

Andrew Jones
Alphawest

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jared Gillis
Sent: Wednesday, 31 August 2011 4:58 AM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] mls qos trust dscp on 7600 port-channel breaks IS-IS?

Still looking for input on this issue. It's still a problem, and I can't figure out why trusting DSCP on a port-channel would break my IGP.

On 08/12/2011 09:52 AM, Jared Gillis wrote:
> Does anyone have any thoughts on this at all? Known Cisco bug?
> 
> I really doubt it's the service-policy, as the policy is running on the Port-Channel right now with no problem. IS-IS only stops working across the interface when I add the mls qos trust dscp command to it.
> 
> I have the exact same queueing and trust config on other physical (non port-channel) ports on the same chassis with no issue.
> 
> On 08/10/2011 12:55 PM, Jared Gillis wrote:
>> My service policy only sets internal queueing values based on source/dest IP or input DSCP.
>>
>> policy-map SONIC-DEFAULT-QOS
>>   class SONIC-PRIORITY-QUEUE
>>    set dscp cs6
>>   class SONIC-EXPEDITED-QUEUE
>>    set dscp cs4
>>   class CUSTOMER-EXPEDITED-QUEUE
>>    set dscp cs2
>>   class DEFAULT-QUEUE
>>    set dscp default
>>
>> I also have no COPP or other control-plane config enabled.
>>
>> On 08/10/2011 12:00 PM, Dmitry Valdov wrote:
>>>
>>>
>>> But.. ISIS uses CLNS, not IP. I'm confused :-)
>>>
>>>
>>> On Wed, 10 Aug 2011, Blake Dunlap wrote:
>>>
>>>> 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 <jared.a.gillis at gmail.com>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  cisco-nsp at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>>>
>>>> _______________________________________________
>>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>>
>>>
>>
> 

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/