Reference record for OID 1.3.6.1.4.1.36.2.15.3.3.3.5.6.1.3



parent
1.3.6.1.4.1.36.2.15.3.3.3.5.6.1 (lBDomainMembershipEntry)
node code
3
node name
lBDomainMembershipWorkBuf
dot oid
1.3.6.1.4.1.36.2.15.3.3.3.5.6.1.3
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dec(36) ema(2) sysobjid(15) bridges(3) gigaswitch(3) gigaversion1(3) gigaSets(5) lBDomainMembershipTable(6) lBDomainMembershipEntry(1) lBDomainMembershipWorkBuf(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dec(36) ema(2) sysobjid(15) subsys(3) gigaswitch(3) gigaversion1(3) gigaSets(5) lBDomainMembershipTable(6) lBDomainMembershipEntry(1) lBDomainMembershipWorkBuf(3)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) dec(36) ema(2) sysObjectIds(15) bridges(3) gigaswitch(3) gigaversion1(3) gigaSets(5) lBDomainMembershipTable(6) lBDomainMembershipEntry(1) lBDomainMembershipWorkBuf(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) dec(36) ema(2) sysObjectIds(15) subsys(3) gigaswitch(3) gigaversion1(3) gigaSets(5) lBDomainMembershipTable(6) lBDomainMembershipEntry(1) lBDomainMembershipWorkBuf(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) dec(36) ema(2) sysobjid(15) bridges(3) gigaswitch(3) gigaversion1(3) gigaSets(5) lBDomainMembershipTable(6) lBDomainMembershipEntry(1) lBDomainMembershipWorkBuf(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) dec(36) ema(2) sysobjid(15) subsys(3) gigaswitch(3) gigaversion1(3) gigaSets(5) lBDomainMembershipTable(6) lBDomainMembershipEntry(1) lBDomainMembershipWorkBuf(3)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dec(36) ema(2) sysObjectIds(15) bridges(3) gigaswitch(3) gigaversion1(3) gigaSets(5) lBDomainMembershipTable(6) lBDomainMembershipEntry(1) lBDomainMembershipWorkBuf(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dec(36) ema(2) sysObjectIds(15) subsys(3) gigaswitch(3) gigaversion1(3) gigaSets(5) lBDomainMembershipTable(6) lBDomainMembershipEntry(1) lBDomainMembershipWorkBuf(3)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/dec/ema/sysobjid/bridges/gigaswitch/gigaversion1/gigaSets/lBDomainMembershipTable/lBDomainMembershipEntry/lBDomainMembershipWorkBuf
  • /iso/identified-organization/dod/internet/private/enterprise/dec/ema/sysobjid/subsys/gigaswitch/gigaversion1/gigaSets/lBDomainMembershipTable/lBDomainMembershipEntry/lBDomainMembershipWorkBuf
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/dec/ema/sysObjectIds/bridges/gigaswitch/gigaversion1/gigaSets/lBDomainMembershipTable/lBDomainMembershipEntry/lBDomainMembershipWorkBuf
  • /iso/org/dod/internet/private/enterprise/dec/ema/sysObjectIds/subsys/gigaswitch/gigaversion1/gigaSets/lBDomainMembershipTable/lBDomainMembershipEntry/lBDomainMembershipWorkBuf
  • /iso/org/dod/internet/private/enterprises/dec/ema/sysobjid/bridges/gigaswitch/gigaversion1/gigaSets/lBDomainMembershipTable/lBDomainMembershipEntry/lBDomainMembershipWorkBuf
  • /iso/org/dod/internet/private/enterprises/dec/ema/sysobjid/subsys/gigaswitch/gigaversion1/gigaSets/lBDomainMembershipTable/lBDomainMembershipEntry/lBDomainMembershipWorkBuf
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/dec/ema/sysObjectIds/bridges/gigaswitch/gigaversion1/gigaSets/lBDomainMembershipTable/lBDomainMembershipEntry/lBDomainMembershipWorkBuf
  • /iso/iso-identified-organization/dod/internet/private/enterprises/dec/ema/sysObjectIds/subsys/gigaswitch/gigaversion1/gigaSets/lBDomainMembershipTable/lBDomainMembershipEntry/lBDomainMembershipWorkBuf
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/36/2/15/3/3/3/5/6/1/3

    Description by mibdepot

    Managers can specify logical bridge domains as many times as
    needed without effecting the current box configuration using
    this object. Setting this object to a new value is stored
    in a local buffer and the changes are not recorded in the
    nonvolatile memory.

    The new value is copied into lBDomainMembership and
    becomes effective when portGroupAction is set to doUpdate
    and the updating process successfully upgrades the logical
    bridge domains.

    A logical bridge domain is expressed using a shorthand that
    says what learning domains are members of it.

    An examples of a specification is:
    (1,3,5)
    (2-4)

    Commas separate items in a list of learning domains. Hyphens
    are short-hand for specifying a range of numbers. Learning
    domain numbers are specified in decimal.

    A logical bridge domain will read back in a form equivalent to
    the form written. It may not read back exactly as written.

    Without a management set, the default logical bridge domain
    (i.e., domain number 1) contains all learning domains. The
    other logical bridge domains are empty sets. A logical
    bridge domain is created by specifying what learning domains
    are members of it. Specified learning domains are deleted
    from the old logical bridge domain and added to the new
    logical bridge domain. Deletion and addition of the learning
    domains are atomic across the SNMP messages. Learning domains
    left out in the specification will automatically join the
    default logical bridge domain.

    Reconfiguring logical bridge domains is an expensive operation.
    Therefore the manager should not change the configuration
    very often.

    Parsed from file dec_elan20.txt
    Company: None
    Module: DEC-ELAN-MIB

    Description by circitor

    Managers can specify logical bridge domains as many times as
    needed without effecting the current box configuration using
    this object. Setting this object to a new value is stored
    in a local buffer and the changes are not recorded in the
    nonvolatile memory.

    The new value is copied into lBDomainMembership and
    becomes effective when portGroupAction is set to doUpdate
    and the updating process successfully upgrades the logical
    bridge domains.

    A logical bridge domain is expressed using a shorthand that
    says what learning domains are members of it.

    An examples of a specification is:
    (1,3,5)
    (2-4)

    Commas separate items in a list of learning domains. Hyphens
    are short-hand for specifying a range of numbers. Learning
    domain numbers are specified in decimal.

    A logical bridge domain will read back in a form equivalent to
    the form written. It may not read back exactly as written.

    Without a management set, the default logical bridge domain
    (i.e., domain number 1) contains all learning domains. The
    other logical bridge domains are empty sets. A logical
    bridge domain is created by specifying what learning domains
    are members of it. Specified learning domains are deleted
    from the old logical bridge domain and added to the new
    logical bridge domain. Deletion and addition of the learning
    domains are atomic across the SNMP messages. Learning domains
    left out in the specification will automatically join the
    default logical bridge domain.

    Reconfiguring logical bridge domains is an expensive operation.
    Therefore the manager should not change the configuration
    very often.

    Parsed from file DEC-ELAN-MIB.mib
    Module: DEC-ELAN-MIB

    Information by oid_info

    Vendor: DEC
    Module: DEC-ELAN-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    lBDomainMembershipWorkBuf OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION " Managers can specify logical bridge domains as many times as needed without effecting the current box configuration using this object. Setting this object to a new value is stored in a local buffer and the changes are not recorded in the nonvolatile memory. The new value is copied into lBDomainMembership and becomes effective when portGroupAction is set to doUpdate and the updating process successfully upgrades the logical bridge domains. A logical bridge domain is expressed using a shorthand that says what learning domains are members of it. An examples of a specification is: (1,3,5) (2-4) Commas separate items in a list of learning domains. Hyphens are short-hand for specifying a range of numbers. Learning domain numbers are specified in decimal. A logical bridge domain will read back in a form equivalent to the form written. It may not read back exactly as written. Without a management set, the default logical bridge domain (i.e., domain number 1) contains all learning domains. The other logical bridge domains are empty sets. A logical bridge domain is created by specifying what learning domains are members of it. Specified learning domains are deleted from the old logical bridge domain and added to the new logical bridge domain. Deletion and addition of the learning domains are atomic across the SNMP messages. Learning domains left out in the specification will automatically join the default logical bridge domain. Reconfiguring logical bridge domains is an expensive operation. Therefore the manager should not change the configuration very often. " ::= { lBDomainMembershipEntry 3 }

    Information by circitor

    lBDomainMembershipWorkBuf OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION " Managers can specify logical bridge domains as many times as needed without effecting the current box configuration using this object. Setting this object to a new value is stored in a local buffer and the changes are not recorded in the nonvolatile memory. The new value is copied into lBDomainMembership and becomes effective when portGroupAction is set to doUpdate and the updating process successfully upgrades the logical bridge domains. A logical bridge domain is expressed using a shorthand that says what learning domains are members of it. An examples of a specification is: (1,3,5) (2-4) Commas separate items in a list of learning domains. Hyphens are short-hand for specifying a range of numbers. Learning domain numbers are specified in decimal. A logical bridge domain will read back in a form equivalent to the form written. It may not read back exactly as written. Without a management set, the default logical bridge domain (i.e., domain number 1) contains all learning domains. The other logical bridge domains are empty sets. A logical bridge domain is created by specifying what learning domains are members of it. Specified learning domains are deleted from the old logical bridge domain and added to the new logical bridge domain. Deletion and addition of the learning domains are atomic across the SNMP messages. Learning domains left out in the specification will automatically join the default logical bridge domain. Reconfiguring logical bridge domains is an expensive operation. Therefore the manager should not change the configuration very often. " ::= { lBDomainMembershipEntry 3 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.36)

    Ron Bhanukitsiri

    Brothers (2)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.36.2.15.3.3.3.5.6.1.1 lBDomainNumber 0 0 The logical bridge domain number. It is unique within
    this table and must be between 1 and 8.
    1.3.6.1.4.1.36.2.15.3.3.3.5.6.1.2 lBDomainMembership 0 0 This object displays the learning domain numbers which are
    members of the indexed logical bridge domain in the current
    box config…