
Hi,
In Rfc:2674 (P-BRIDGE MIB), an Table Object, which is having read-write access is later used as an Index for another Table. Is this Correct???
To be more precise, dot1dRegenUserPriority is an object of Dot1dUserPriorityRegenEntry, with read-write access. In later part of the mib, the same dot1dRegenUserPriority is used as an Index for the Table dot1dPortOutboundAccessPriorityTable.
Libsmi is not giving any Warnings/Errors for this?? So can I assume that this is a correct usage?? But the tool we are using gives an error saying Index element should be not-accessible. So which is correct??
Thanks & Regards, Vivekanandan.V
*************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended.
If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ***************************************************************************

Hi!
Vivekanandan> In Rfc:2674 (P-BRIDGE MIB), an Table Object, which is Vivekanandan> having read-write access is later used as an Index for Vivekanandan> another Table. Is this Correct???
Vivekanandan> To be more precise, dot1dRegenUserPriority is an object Vivekanandan> of Dot1dUserPriorityRegenEntry, with read-write access. Vivekanandan> In later part of the mib, the same Vivekanandan> dot1dRegenUserPriority is used as an Index for the Table Vivekanandan> dot1dPortOutboundAccessPriorityTable.
Vivekanandan> Libsmi is not giving any Warnings/Errors for this?? So Vivekanandan> can I assume that this is a correct usage?? But the Vivekanandan> tool we are using gives an error saying Index element Vivekanandan> should be not-accessible. So which is correct??
The authoritative answer gives RFC 2578. In Section 7.7 it says:
Objects which are both specified in the INDEX clause of a conceptual row and also columnar objects of the same conceptual row are termed auxiliary objects. The MAX-ACCESS clause for auxiliary objects is "not-accessible", except in the following circumstances: [...]
Since, in this case the index object is a column of another table, it is not an auxiliary object and does not have to be not-accessible for this reason.
However, you should not assume in general that a MIB for which smilint does not detect any error messages is free of errors.
-frank
participants (2)
-
Frank Strauss
-
Vivekanandan V