6500 in VSS QoS problem

[Difan Zhao]

Hi experts,

I have two 6500 in VSS. I have WAN connection connected on port on Sup card on each chassis and they are in a port-channel. Sup is VS-SUP2T-10G and it is in slot 5. The ports are Gi1/5/3 and Gi2/5/3. IOS is 15.0(1)SY1

I am trying to apply queueing configuration on the interface but failed. I got this error message

(config-if)# wrr-queue bandwidth 1 80 20

HWIF-QOS: QoS configs are not allowed on VSL Portgroup

I googled and some threads say that in VSS I can't configure queueing on sup card ports. They are always disabled. Is it true? Is it only limitation on sup ports or is it on other ports as well?

Thanks!

Difan

[Joseph W. Doherty]

Disclaimer

The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.

Liability Disclaimer

In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.

Posting

Unsure about VSS on a sup2T, but on VSS with VS-S720, you cannot manually set QoS for the VSL ports.

[Difan Zhao]

Thanks Joseph. However my VSL is built on different ports (but on the same Sup card too) Te1/5/4 and Te1/5/5.. The one I am trying to configure is Gi1/5/3. This port is not part of VSL configuration and it is simply used to connect with WAN vendor (since it is the only Giga port we have on the chassis...).

[Reza Sharifi · Accepted solution]

Hi Difan,

This is an issue with all sup-720-VS and even Sup-2T.  If you configure a 10Gig port as part of VSL links, you can not apply any QOS config to any other port on the Sup.  This is not an issue with Gig line cards.

HTH

[Difan Zhao]

Thanks Reza. Are you saying that if I move the connection to WS-X6816-10GE card, I will be fine to apply the config?

[Reza Sharifi]

That is correct.  If you move the VSL connection to a X6816-10G or X6808-10G blade, then you should be able to apply the QOS. Are both of your VSL links on the Sup?  Best practice is to have one 10Gig from a blade and one 10Gig from the Sup for your VSL links.

HTH

[Joseph W. Doherty]

Disclaimer

The   Author of this posting offers the information contained within this   posting without consideration and with the reader's understanding that   there's no implied or expressed suitability or fitness for any purpose.   Information provided is for informational purposes only and should not   be construed as rendering professional advice of any kind. Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In   no event shall Author be liable for any damages whatsoever (including,   without limitation, damages for loss of use, data or profit) arising  out  of the use or inability to use the posting's information even if  Author  has been advised of the possibility of such damage.

Posting

Reza is correct about VSS, at least on a VS-S720 (unsure about VSS on a sup2T), by default VSS "slaves" all the sup's ports QoS when one port is used for VSL.  However I recall there is a command (again at least on the VS-S720) to change this.  Also however, I also recall, it might only "unslave" the sup's gig ports.

[Reza Sharifi]

Joe,

I actually tried the same QOS command on a Sup-2T, and the result is that I get the same error message as Sup-720-VS

HTH

[Joseph W. Doherty]

Disclaimer

The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.

Liability Disclaimer

In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.

Posting

I looked up the QoS issue for VSS and take note of the last sentence (might also address your issue) . . .

Configuring VSL QoS

The VSS automatically configures VSL ports for trust CoS, using default  CoS mappings (you cannot change the mappings on VSL ports).

For switching modules that support per-ASIC configuration, the VSL  configuration applies to all ports on the same ASIC (including any  non-VSL ports).

The VSS disables the QoS commands on VSL ports (and any non-VSL ports on  the same ASIC). For example, you cannot use QoS queuing or map commands  on VSL ports.

To ensure that all eight QoS receive queues are enabled for the 10-Gigabit Ethernet ports on the supervisor engine, enter the mls qos 10g-only global configuration command.

In Cisco IOS Release 12.2(33)SXI and later releases, when the mls qos 10g-only command is entered and only one of the two 10-Gigabit Ethernet ports on  the supervisor engine is a VSL port, the non-VSL 10-Gigabit Ethernet  port can be configured for QoS.

[Difan Zhao]

Thanks. Where do I apply this command? I got an error when trying to apply it globally or on the interface...

core(config)#mls qos ?
% Unrecognized command
core(config)#mls
shc-e06005-core(config)#mls ?
% Unrecognized command
core(config)#int g1/5/3
core(config-if)#mls qo?
% Unrecognized command

As a matter of fact, my core doesn't even support anything starting with "mls..."

Thanks,

[Joseph W. Doherty]

Disclaimer

The   Author of this posting offers the information contained within this   posting without consideration and with the reader's understanding that   there's no implied or expressed suitability or fitness for any purpose.   Information provided is for informational purposes only and should not   be construed as rendering professional advice of any kind. Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In   no event shall Author be liable for any damages whatsoever (including,   without limitation, damages for loss of use, data or profit) arising  out  of the use or inability to use the posting's information even if  Author  has been advised of the possibility of such damage.

Posting

Yours is a sup2t?  If so, I don't know whether it's supported on that sup.

If a vs-s720, are you on the minimum IOS version?

On one or our vs-s720s:

vs-s720(config)#mls qos ?

  10g-only           qos pure 10G mode

  aggregate-policer  Named aggregate policer

  map                qos map keyword

  marking            marking keyword

  police             police keyword

  protocol           protocol keyword

  queueing-only      queueing-only (no QoS rewrite,  no policing)

  rewrite            packet qos rewrite enable/disable

  statistics-export  qos statistics data export

  tunnel             tunnel keyword

[Difan Zhao]

VS-SUP2T-10G

Cisco IOS Software, s2t54 Software (s2t54-ADVIPSERVICESK9-M), Version 15.0(1)SY1, RELEASE SOFTWARE (fc4)

cisco WS-C6509-E (M8572) processor (revision ) with 1769472K/262144K bytes of memory.

Thanks,

[Reza Sharifi]

Difan,

That command is not available for on Sup-2T, as the QOS architecture of the Sup-2T is completely different from Sup-720-VS.

According to Table-3 in this link, you can change the 10Gig ports on the Sup-2T-10G-XL to 10Gig only mode, but I don't have XL to test this.  Is your Sup-2T-10G-XL?

"sh int ten 1/5/4 capa" or sh module will show you that.

http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/white_paper_c11-652042.html

HTH

[hugolinko]

This is not true actually->#

For switching modules that support per-ASIC configuration, the VSL  configuration applies to all ports on the same ASIC (including any  non-VSL ports).

I have VSL link on 1/5/4 and 2/5/4

and look at the status of my ten 1/5/5 and gig1/5/3:

CM-310-BA-CORE-VSS01-PRI#show queueing int gig1/5/3

Interface GigabitEthernet1/5/3 queueing strategy:  Weighted Round-Robin

Port QoS is enabled globally

Queueing on Gi1/5/3: Tx Enabled Rx Enabled

Trust boundary disabled

Port is untrusted

CM-310-BA-CORE-VSS01-PRI#show queueing int ten1/5/5

Interface TenGigabitEthernet1/5/5 queueing strategy:  Weighted Round-Robin

Port QoS is enabled globally

Queueing on Te1/5/5: Tx Enabled Rx Enabled

Trust boundary disabled

Port is untrusted

Anyone knows, how to apply the same damned config on the "same-asic" ports on my

VS-S720-10G?

I just want to have mls qos trust cos, as well on any non VSL links, the same way

IOS inserted it on to my VSL link configuration.

When I try to configure it on NON VSL links I get that discussed error

CM-310-BA-CORE-VSS01(config)#int port-c 3

CM-310-BA-CORE-VSS01(config-if)#mls qos trust cos

HWIF-QOS: QoS configs are not allowed on VSL Portgroup

TenGigabitEthernet1/5/5 is member of the port-channel which is part of the VSL Portgroup

CM-310-BA-CORE-VSS01(config-if)#

Although there is mls qos trust cos on VSL links as well.

interface TenGigabitEthernet1/5/4

description VSL link for VSS Core Pribinova DO NOT CHANGE!!!

no switchport

no ip address

mls qos trust cos

no cdp enable

channel-group 1 mode on

end

Thanks for the answer

Leo

[Joseph W. Doherty]

Disclaimer

The   Author of this posting offers the information contained within this   posting without consideration and with the reader's understanding that   there's no implied or expressed suitability or fitness for any purpose.   Information provided is for informational purposes only and should not   be construed as rendering professional advice of any kind. Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In   no event shall Author be liable for any damages whatsoever (including,   without limitation, damages for loss of use, data or profit) arising  out  of the use or inability to use the posting's information even if  Author  has been advised of the possibility of such damage.

Posting

If I understand your posting, your show commands appear to show a different trust state then the VSL port on the same ASIC, which would also appear to disagree with Cisco documentation.  If that's your concern, sounds like something you might need to open a TAC case for.  (Either all the ports on the VSL port's ASIC don't work alike, or there might be a cosmetic bug with the show command for those non-VSL ports.)