other(1) - This entry is currently in use, but the
conditions under which it will remain so are different
from each of the following values. Like other uses
of 'other' in MIBs, this value may not be assigned to
the object.
invalid(2) - Writing this value to the object removes the entry
permanent(3) - Writing this value to the object indicates that
the entry is preserved across a bridge reset.
deleteOnReset(4) - Writing this value removes the permanent
entry characteristic. The entry is deleted upon the
next bridge reset (SCP or GIGAswitch failure).
Writing deleteOnReset is not supported. SNMP does not
currently model viewing the non-volatile and volatile
data structures independently, which can lead to
unexpectedly having no filter if a reset occurs while
temporarily trying a change to an existing filter.
Writes of this value will result in a bad value return
status. It is present for consistency with the Bridge
MIB (RFC 1286), which describes address filters.
deleteOnTimeout(5) - Writing this value removes the permanent
entry characteristic. Since the timers used for aging
information within the bridge are hidden from the user,
the change may in fact take place immediately.
Writing deleteOnTimeout is not supported. SNMP does not
currently model viewing the non-volatile and volatile
data structures independently, which can lead to
unexpectedly having no filter if a reset occurs while
temporarily trying a change to an existing filter.
Writes of this value will result in a bad value return
status. It is present for consistency with the Bridge
MIB (RFC 1286), which describes address filters.
Parsed from file GIGASWITCH-MIB.mib.txt
Company: None
Module: GIGASWITCH-MIB
other(1) - This entry is currently in use, but the
conditions under which it will remain so are different
from each of the following values. Like other uses
of 'other' in MIBs, this value may not be assigned to
the object.
invalid(2) - Writing this value to the object removes the entry
permanent(3) - Writing this value to the object indicates that
the entry is preserved across a bridge reset.
deleteOnReset(4) - Writing this value removes the permanent
entry characteristic. The entry is deleted upon the
next bridge reset (SCP or GIGAswitch failure).
Writing deleteOnReset is not supported. SNMP does not
currently model viewing the non-volatile and volatile
data structures independently, which can lead to
unexpectedly having no filter if a reset occurs while
temporarily trying a change to an existing filter.
Writes of this value will result in a bad value return
status. It is present for consistency with the Bridge
MIB (RFC 1286), which describes address filters.
deleteOnTimeout(5) - Writing this value removes the permanent
entry characteristic. Since the timers used for aging
information within the bridge are hidden from the user,
the change may in fact take place immediately.
Writing deleteOnTimeout is not supported. SNMP does
not currently model viewing the non-volatile and
volatile data structures independently, which can lead
to unexpectedly having no filter if a reset occurs
while temporarily trying a change to an existing
filter. Writes of this value will result in a bad
value return status. It is present for consistency
with the Bridge MIB (RFC 1286), which describes address
filters.
Parsed from file DEC-ELAN-MIB.mib
Module: DEC-ELAN-MIB
Vendor: DEC
Module: DEC-ELAN-MIB
[Automatically extracted from oidview.com]
ebrNportSANameStatus OBJECT-TYPE SYNTAX INTEGER { other(1), invalid(2), permanent(3), deleteOnReset(4), deleteOnTimeout(5) } ACCESS read-write STATUS mandatory DESCRIPTION " other(1) - This entry is currently in use, but the conditions under which it will remain so are different from each of the following values. Like other uses of 'other' in MIBs, this value may not be assigned to the object. invalid(2) - Writing this value to the object removes the entry permanent(3) - Writing this value to the object indicates that the entry is preserved across a bridge reset. deleteOnReset(4) - Writing this value removes the permanent entry characteristic. The entry is deleted upon the next bridge reset (SCP or GIGAswitch failure). Writing deleteOnReset is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. deleteOnTimeout(5) - Writing this value removes the permanent entry characteristic. Since the timers used for aging information within the bridge are hidden from the user, the change may in fact take place immediately. Writing deleteOnTimeout is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. " ::= { ebrNportSANameEntry 5 }
ebrNportSANameStatus OBJECT-TYPE SYNTAX INTEGER { other(1), invalid(2), permanent(3), deleteOnReset(4), deleteOnTimeout(5) } ACCESS read-write STATUS mandatory DESCRIPTION " other(1) - This entry is currently in use, but the conditions under which it will remain so are different from each of the following values. Like other uses of 'other' in MIBs, this value may not be assigned to the object. invalid(2) - Writing this value to the object removes the entry permanent(3) - Writing this value to the object indicates that the entry is preserved across a bridge reset. deleteOnReset(4) - Writing this value removes the permanent entry characteristic. The entry is deleted upon the next bridge reset (SCP or GIGAswitch failure). Writing deleteOnReset is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. deleteOnTimeout(5) - Writing this value removes the permanent entry characteristic. Since the timers used for aging information within the bridge are hidden from the user, the change may in fact take place immediately. Writing deleteOnTimeout is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. " ::= { ebrNportSANameEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.36.2.15.3.3.3.2.1.5.1.1 | ebrNportSAName | 0 | 0 | This name for a portion of a filter is whatever the user likes, as long as it is a unique ebrNportSAName. The combination of ebrN… |
| 1.3.6.1.4.1.36.2.15.3.3.3.2.1.5.1.2 | ebrNportSANameSA | 0 | 0 | The six-byte source address. Changes to ebrNportStaticSATable for this address are denied while filtering of the address is speci… |
| 1.3.6.1.4.1.36.2.15.3.3.3.2.1.5.1.3 | ebrNportSAMatrixName | 0 | 0 | A ebrNportMatrixName. Multiple matrices for the same address are combined using an elementwise-OR operator. |
| 1.3.6.1.4.1.36.2.15.3.3.3.2.1.5.1.4 | ebrNportSANameDisp | 0 | 0 | This object specifies how to interpret the ebrNportPortNum and the ebrNportSAMatrixName objects. portMask(1) : The static filteri… |