Subject: [Bridge-mib] FW: ieee8023-lag-mib : dot3adAggActorSystemPriority and dot3adAgg PortActorSystemPriority definition

From: "Wijnen, Bert (Bert)" <[email-masked]>
Date: Thu, 27 Feb 2003 01:41:15 +0100

Does this actually better belong on the bridgmib mailing list?

Thanks,
Bert 

-----Original Message-----
From: Rohit Rohit [mailto:[email-masked]]
Sent: woensdag 26 februari 2003 23:55
To: [email-masked]
Subject: ieee8023-lag-mib : dot3adAggActorSystemPriority and
dot3adAggPortActorSystemPriority definition

Hi, 

  I am not sure if this is the right group for this question;
  but mail to [email-masked]' does not seem
  to work.

  I see the following inconsistency between the dot3adAggActorSystemPriority 
  and dot3adAggPortActorSystemPriority.
  
  dot3adAggPortActorSystemPriority is defined to be 2 octets; but
  its range is only from 0 to 255. ( IMHO, it should be 0 .. 65535 ).

 > dot3adAggPortActorSystemPriority OBJECT-TYPE
 >   SYNTAX       INTEGER (0..255)
 >   MAX-ACCESS   read-write
 >   STATUS       current
 >   DESCRIPTION
 >       "A 2-octet read-write value used to define the priority
 >       value associated with the Actor's System ID."
 >   REFERENCE
 >       "IEEE 802.3 Subclause 30.7.2.1.2"
 >   ::= { dot3adAggPortEntry 2 }

  while dot3adAggActorSystemPriority is also defined to be
  2 octets; but its range is from 0..65535.

  Any reason for this inconsistency ?

> dot3adAggActorSystemPriority OBJECT-TYPE
>    SYNTAX       INTEGER (0..65535)
>    MAX-ACCESS   read-write
>    STATUS       current
>    DESCRIPTION
>        "A 2-octet read-write value indicating the priority
>        value associated with the Actor's System ID."
>    REFERENCE
>        "IEEE 802.3 Subclause 30.7.1.1.5"
>    ::= { dot3adAggEntry 3 }

Thanks
Rohit
_______________________________________________
Bridge-mib mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/bridge-mib