Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Qos on a 6509 running VSS

I have 2 6506s running IOS version s72033-adventerprisek9_wan-mz.122-33.SXI3.bin with redundant Supervisor Engine 720 10GE. When I enable auto qos voice trust on my uplink ports I get the following messages.

6509-1#(config-if)#auto qos voip trust  
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Warning: rcv cosmap will not be applied in hardware.
  To modify rcv cosmap in hardware, all of the interfaces below
  must be put into 'trust cos' state:
    Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Warning: rcv cosmap will not be applied in hardware.
  To modify rcv cosmap in hardware, all of the interfaces below
  must be put into 'trust cos' state:
    Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Warning: rcv cosmap will not be applied in hardware.
  To modify rcv cosmap in hardware, all of the interfaces below
  must be put into 'trust cos' state:
    Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Warning: rcv cosmap will not be applied in hardware.
  To modify rcv cosmap in hardware, all of the interfaces below
  must be put into 'trust cos' state:
    Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Warning: rcv cosmap will not be applied in hardware.
  To modify rcv cosmap in hardware, all of the interfaces below
  must be put into 'trust cos' state:
    Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Warning: rcv cosmap will not be applied in hardware.
  To modify rcv cosmap in hardware, all of the interfaces below
  must be put into 'trust cos' state:
    Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Warning: rcv cosmap will not be applied in hardware.
  To modify rcv cosmap in hardware, all of the interfaces below
  must be put into 'trust cos' state:
    Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Propagating cos-map configuration to:  Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Warning: rcv cosmap will not be applied in hardware.
  To modify rcv cosmap in hardware, all of the interfaces below
  must be put into 'trust cos' state:
    Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24
Warning: rcv thresholds will not be applied in hardware.
  To modify rcv thresholds in hardware, all of the interfaces below
  must be put into 'trust cos' state:
    Gi2/1/13 Gi2/1/14 Gi2/1/15 Gi2/1/16 Gi2/1/17 Gi2/1/18 Gi2/1/19 Gi2/1/20 Gi2/1/21 Gi2/1/22 Gi2/1/23 Gi2/1/24

So the qos is not being done in hardware and my concern is if I go ahead and apply this to all of my uplink ports the CPU will get hit too hard and cause issues. I don't want to trust all of the ports because I don't know what will be connected to them. The CPU is currently running at around 2% so I know I'm not pushing it right now. I have have 2 nexus 5010 with three 10 gig ports each in etherchannels to the 6506. I also have 5 other uplinks to 3750 stacks in the closets along with some routers and the Call Managers servers that I will have to add this config to.

Has anyone run into this in the past and it this something I need to worry about.

694
Views
0
Helpful
0
Replies