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.