Ethernet Switches & Routers

Reply
Contributor
Posts: 69
Registered: ‎10-14-2011

Foundry IronCore 8000 and Enabling Trust dscp?

I've got an Ironcore 8000 BigIron setup with phones I need to enable the trust boundry at the port level.

I've remapped COS6 -->DSCP46.

If I run the show qos-tos

I see trust level untrusted. I cant seem to enable a trust boundry at the port level

I tried qos-tos trust dscp and qos tos trust dscp. Neither of these commands exist.

Anyone have any idea's no how to enable the trust level?

Your help would be appreciated.

Thanks,

Patman

Contributor
Posts: 69
Registered: ‎10-14-2011

Re: Foundry IronCore 8000 and Enabling Trust dscp?

Cmon, somone has to know how to get those old BigIron switches to trust DSCP values that come into a port!

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: Foundry IronCore 8000 and Enabling Trust dscp?

Ok I will see what I can find, but please post a 'show version'

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: Foundry IronCore 8000 and Enabling Trust dscp?

Hope this helps you out.

Enabling Advanced ToS-Based QoS

To enable advanced ToS-based QoS on an interface, enter the following command at the configuration level for the interface:

NOTE: Advanced ToS-Based QoS cannot be used on an interface that has ACLs.

BigIron(config-if-1/1)# qos-tos

Syntax: qos-tos

NOTE: You must use this command if you want to configure the trust level or marking.

NOTE: When port priority is enabled, Brocade devices will use the higher of the 802.1p and DSCP priority for its internal system priority. To override this internal system priority, apply the qos-tos mark cos command on the interface where advanced ToS-based QoS was enabled. The true internal system priority will then be based on

how the qos-tos trust command is configured on that interface. (See “Specifying the Trust Level” on page 4-7.)

If the port for incoming traffic is a tagged port, then the outgoing 802.1p priority will be the "merged" priority even though the type of marking configured on the interface is actually lower than the “merged” priority for that port. If the port for the incoming traffic is an untagged port and the port for outgoing traffic is an 802.1p port, then the marking configured on these ports will be used. This is useful in the case where the port priority (via priority command under interface CLI) is higher and the user wants to mark all IP packets with a lower priority. Hence, the non-IP packets will continue to use the higher 802.1p priority.

Specifying the Trust Level

The trust level specifies where you want the device to get the QoS value for a packet received on the interface. To set the trust level for an interface to IP Precedence, enter the following command at the configuration level for the interface:

BigIron(config-if-1/1)# qos-tos trust ip-prec

Syntax: qos-tos trust cos | ip-prec | dscp

The cos | ip-prec | dscp parameter specifies the trust level.

  • cos – The device uses the 802.1p (CoS) priority value in the packet’s Ethernet frame header. Use this trust option when you plan to mark the packet’s DSCP value based on the incoming 802.1p value.
    • NOTE: This trust level is not supported on 10 Gigabit Ethernet modules.
  • ip-prec – The device uses the three most-significant bits in the packet’s ToS field and interprets them as an IP precedence value. Use this trust option when the incoming packet is from a device that does not support DSCP and you need to mark the packet for QoS on DSCP devices.
  • dscp – The device uses the six most-significant bits in the packet’s ToS field and interprets them as a DSCP value. This is the default.

Thanks

Michael.

Contributor
Posts: 69
Registered: ‎10-14-2011

Re: Foundry IronCore 8000 and Enabling Trust dscp?

Here you go, Version info below..

SW: Version 07.8.02eT53 Copyright (c) 1996-2006 Foundry Networks, Inc.
      Compiled on Dec 21 2006 at 11:23:19 labeled as B2R07802e
      (3758893 bytes) from Primary B2R07802e.bin
  HW: BigIron 8000 Router, SYSIF version 21, Serial #: Non-exist
==========================================================================
SL 1: B24E Copper Switch Module
      Serial #: Non-exist
2048 KB BRAM, SMC version 2, BM version 21
  256 KB PRAM(256K+0K) and 2048*8 CAM entries for DMA  0, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA  1, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA  2, version 0808
==========================================================================
SL 2: B24E Copper Switch Module
      Serial #: Non-exist
2048 KB BRAM, SMC version 2, BM version 21
  256 KB PRAM(256K+0K) and 2048*8 CAM entries for DMA  4, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA  5, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA  6, version 0808
==========================================================================
SL 3: B24E Copper Switch Module
      Serial #: Non-exist
2048 KB BRAM, SMC version 2, BM version 21
  256 KB PRAM(256K+0K) and 2048*8 CAM entries for DMA  8, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA  9, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA 10, version 0808
==========================================================================
SL 4: B24E Copper Switch Module
      Serial #: Non-exist
2048 KB BRAM, SMC version 2, BM version 21
  256 KB PRAM(256K+0K) and 2048*8 CAM entries for DMA 12, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA 13, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA 14, version 0808
==========================================================================
SL 5: B24E Copper Switch Module
      Serial #: Non-exist
2048 KB BRAM, SMC version 2, BM version 21
  256 KB PRAM(256K+0K) and 2048*8 CAM entries for DMA 16, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA 17, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA 18, version 0808
==========================================================================
SL 6: B24E Copper Switch Module
      Serial #: Non-exist
2048 KB BRAM, SMC version 2, BM version 21
  256 KB PRAM(256K+0K) and 2048*8 CAM entries for DMA 20, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA 21, version 0808
  256 KB PRAM(256K+0K) and shared CAM entries for DMA 22, version 0808
==========================================================================
SL 8: B8GMR Fiber Management Module, SYSIF 2, M3, ACTIVE
      Serial #:   CH12010803
4096 KB BRAM, SMC version 1, BM version 21
  512 KB PRAM(512K+0K) and 2048*8 CAM entries for DMA 28, version 0209
  512 KB PRAM(512K+0K) and shared CAM entries for DMA 29, version 0209
  512 KB PRAM(512K+0K) and 2048*8 CAM entries for DMA 30, version 0209
  512 KB PRAM(512K+0K) and shared CAM entries for DMA 31, version 0209
==========================================================================
Active management module:
  400 MHz Power PC processor 740 (version 8/8302) 66 MHz bus
  512 KB boot flash memory
8192 KB code flash memory
  256 KB SRAM
  256 MB DRAM

Contributor
Posts: 69
Registered: ‎10-14-2011

Re: Foundry IronCore 8000 and Enabling Trust dscp?

It looks like I only have some functionality look below:

switch-01(config-if-e100-1/21)#qos-tos
  map   IPv4 ToS based QoS mappings
telnet@noc-switch-01(config-if-e100-1/21)

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: Foundry IronCore 8000 and Enabling Trust dscp?

have you tried to

switch-01(config-if-e100-1/21)#qos-tos (then press enter)

Then check to see if trust appears as a command?

just entering qos-tos on the port enables the advanced mode.

Also note that you can not use advanced mode if you also have rate limiting enable on the port.

Thanks

Michael.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.