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

FAQ_User — Wed, 19 Nov 2014 22:54:00 GMT

Article ID: 10323

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

Changes
Issued the '

code:

set cos settings

index

code:

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:

code:

iso.org.dod.internet.private.enterprises.enterasys.etsysMibs.etsysModules.etsysCosMIB.

code:

etsysCosObjects.etsysCos.etsysCosTable.etsysCosEntry.etsysCosIndex

code:

1.3.6.1.4.1.5624.1.2.55.1.3.5.1.1

code:

etsysCosIndex OBJECT-TYPE

code:

SYNTAX Unsigned Integer ( 0..32767 )

code:

MAX-ACCESS No Access

code:

STATUS Current

code:

DESCRIPTION

code:

A unique class of service identifier for this CoS setting.

code:

For reasons of backward compatibility indexes 0-7 MUST exist

code:

and be configured with a etsysCos8021dPriority which

code:

matches the etsysCosIndex.

code:

::= { etsysCosEntry 1 }

code:

MODULE ENTERASYS-CLASS-OF-SERVICE-MIB

code:

FILE

code:

enterasys-class-of-service-mib.txt

code:

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.

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

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