SecureStack will not accept Cos Settings: "Could not set the COS parameter

  • 0
  • 1
  • Article
  • Updated 4 years ago
  • (Edited)
Article ID: 10323 

Products
SecureStack C5, C3, C2, B5, B3, B2

Changes
Issued the 'set cos settings <index> priority...' command.

Symptoms
The command was not accepted.
"Could not set the COS parameter"

For example:
    C3(rw)->set cos settings 6 priority 6 tos-value 64
    Could not set the COS parameter
    C3(rw)->
Cause
The Class of Service MIB (may be downloaded within mibs.zip) includes the following definition:

iso.org.dod.internet.private.enterprises.enterasys.etsysMibs.etsysModules.etsysCosMIB.
etsysCosObjects.etsysCos.etsysCosTable.etsysCosEntry.etsysCosIndex
1.3.6.1.4.1.5624.1.2.55.1.3.5.1.1

etsysCosIndex OBJECT-TYPE
SYNTAX Unsigned Integer ( 0..32767 )
MAX-ACCESS No Access
STATUS Current
DESCRIPTION

          A unique class of service identifier for this CoS setting.
          For reasons of backward compatibility indexes 0-7 MUST exist
          and be configured with a etsysCos8021dPriority which
          matches the etsysCosIndex.

::= { etsysCosEntry 1 }

MODULE ENTERASYS-CLASS-OF-SERVICE-MIB
FILE  enterasys-class-of-service-mib.txt
PATH ftp://ftp.enterasys.com/pub/snmp/mibs

The command in question is defined as follows:
    set cos settings  <Class of Service index 0-255>
        [priority  <Priority 0-7 to be associated with the CoS>]
        [tos-value  <TOS Byte value 0-255 to be written for the CoS>]
        [irl-reference  <Inbound Rate Limiter 0-99 to be associated with the CoS>]
When a CoS Index value within the range of 0-7 is used, then it may be treated as a Class of Service or as a Priority (a legacy 802.1p Priority has a value within the range of 0-7), because for this range these concepts are synonymous.

When a CoS Index value within the range of 8-255 is used, then it may be treated as a Class of Service which has a defined Priority value (0-7) associated with it.

When a CoS Index value within the range of 0-255 is used, then it may optionally be associated with a TOS Rewrite value and/or an Inbound Rate Limiter.

Solution/Workaround
FAD (Functions as Designed)

In order to avoid the stated cli error condition, it is necessary to
    Use a CoS Index value within the range of 0-7 only when it is desired that the resulting Priority match the index value;
          -and-
    When using a CoS Index value within the range of 0-7 do not specify a Priority value.
The solution for the example given above is to omit the Priority parameter:
    C3(rw)->set cos settings 6 tos-value 64
    C3(rw)->
Note that most often, NetSight Policy Manager - rather than the cli - is used to configure Policy and Class of Service.
Photo of FAQ User

FAQ User, Official Rep

  • 13,610 Points 10k badge 2x thumb

Posted 4 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.