Reference record for OID 1.3.6.1.2.1.124.3


parent
1.3.6.1.2.1.124 (pmMib)
node code
3
node name
pmElementTypeRegTable
dot oid
1.3.6.1.2.1.124.3
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pmMib(124) pmElementTypeRegTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pmMib(124) pmElementTypeRegTable(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) pmMib(124) pmElementTypeRegTable(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) pmMib(124) pmElementTypeRegTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pmMib(124) pmElementTypeRegTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pmMib(124) pmElementTypeRegTable(3)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/pmMib/pmElementTypeRegTable
  • /iso/identified-organization/dod/internet/mgmt/mib/pmMib/pmElementTypeRegTable
  • /iso/org/dod/internet/mgmt/mib-2/pmMib/pmElementTypeRegTable
  • /iso/org/dod/internet/mgmt/mib/pmMib/pmElementTypeRegTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/pmMib/pmElementTypeRegTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/pmMib/pmElementTypeRegTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/124/3

    Description by circitor

    A registration table for element types managed by this
    system.

    The Element Type Registration table allows the manager to
    learn what element types are being managed by the system and
    to register new types, if necessary. An element type is
    registered by providing the OID of an SNMP object (i.e.,
    without the instance). Each SNMP instance that exists under
    that object is a distinct element. The index of the element is
    the index part of the discovered OID. This index will be
    supplied to policy conditions and actions so that this code
    can inspect and configure the element.

    For example, this table might contain the following entries.
    The first three are agent-installed, and the 4th was
    downloaded by a management station:

    OIDPrefix MaxLatency Description StorageType
    ifEntry 100 mS interfaces - builtin readOnly
    0.0 100 mS system element - builtin readOnly
    frCircuitEntry 100 mS FR Circuits - builtin readOnly
    hrSWRunEntry 60 sec Running Processes volatile




    Note that agents may automatically configure elements in this
    table for frequently used element types (interfaces, circuits,
    etc.). In particular, it may configure elements for whom
    discovery is optimized in one or both of the following ways:

    1. The agent may discover elements by scanning internal data
    structures as opposed to issuing local SNMP requests. It is
    possible to recreate the exact semantics described in this
    table even if local SNMP requests are not issued.

    2. The agent may receive asynchronous notification of new
    elements (for example, 'card inserted') and use that
    information to instantly create elements rather than
    through polling. A similar feature might be available for
    the deletion of elements.

    Note that the disposition of agent-installed entries is
    described by the pmPolicyStorageType object.

    Parsed from file POLICY-BASED-MANAGEMENT-MIB.mib
    Module: POLICY-BASED-MANAGEMENT-MIB

    Information by oid_info

    Vendor: IETF RFCs
    Module: POLICY-BASED-MANAGEMENT-MIB (rfc4011-Policy-Based-Management.mib)
    Type: TABLE
    Access: not-accessible
    Syntax: SEQUENCE OF

    Automatically extracted from www.mibdepot.com

    Information by circitor

    pmElementTypeRegTable OBJECT-TYPE SYNTAX SEQUENCE OF PmElementTypeRegEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A registration table for element types managed by this system. The Element Type Registration table allows the manager to learn what element types are being managed by the system and to register new types, if necessary. An element type is registered by providing the OID of an SNMP object (i.e., without the instance). Each SNMP instance that exists under that object is a distinct element. The index of the element is the index part of the discovered OID. This index will be supplied to policy conditions and actions so that this code can inspect and configure the element. For example, this table might contain the following entries. The first three are agent-installed, and the 4th was downloaded by a management station: OIDPrefix MaxLatency Description StorageType ifEntry 100 mS interfaces - builtin readOnly 0.0 100 mS system element - builtin readOnly frCircuitEntry 100 mS FR Circuits - builtin readOnly hrSWRunEntry 60 sec Running Processes volatile Note that agents may automatically configure elements in this table for frequently used element types (interfaces, circuits, etc.). In particular, it may configure elements for whom discovery is optimized in one or both of the following ways: 1. The agent may discover elements by scanning internal data structures as opposed to issuing local SNMP requests. It is possible to recreate the exact semantics described in this table even if local SNMP requests are not issued. 2. The agent may receive asynchronous notification of new elements (for example, 'card inserted') and use that information to instantly create elements rather than through polling. A similar feature might be available for the deletion of elements. Note that the disposition of agent-installed entries is described by the pmPolicyStorageType object." ::= { pmMib 3 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.124.3.1 pmElementTypeRegEntry 5 5 A registration of an element type.

    Note that some values of this table's index may result in an
    instance name that exceeds a leng…

    Brothers (12)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.124.0 pmNotifications 3 3 None
    1.3.6.1.2.1.124.1 pmPolicyTable 1 21 The policy table. A policy is a pairing of a
    policyCondition and a policyAction that is used to apply the
    action to a selected s…
    1.3.6.1.2.1.124.2 pmPolicyCodeTable 1 5 The pmPolicyCodeTable stores the code for policy conditions and
    actions.

    An example of the relationships between the code table a…
    1.3.6.1.2.1.124.4 pmRoleTable 1 6 The pmRoleTable is a read-create table that organizes role
    strings sorted by element. This table is used to create and
    modify ro…
    1.3.6.1.2.1.124.5 pmCapabilitiesTable 1 2 The pmCapabilitiesTable contains a description of
    the inherent capabilities of the system so that
    management stations can learn o…
    1.3.6.1.2.1.124.6 pmCapabilitiesOverrideTable 1 4 The pmCapabilitiesOverrideTable allows management stations
    to override pmCapabilitiesTable entries that have been
    registered by t…
    1.3.6.1.2.1.124.7 pmSchedLocalTime 1 1 The local time used by the scheduler. Schedules that
    refer to calendar time will use the local time indicated
    by this object. A…
    1.3.6.1.2.1.124.8 pmSchedTable 1 12 This table defines schedules for policies.
    1.3.6.1.2.1.124.9 pmTrackingPETable 1 5 The pmTrackingPETable describes what elements
    are active (under control of) a policy. This table is indexed
    in order to optimize…
    1.3.6.1.2.1.124.10 pmTrackingEPTable 1 5 The pmTrackingEPTable describes what policies
    are controlling an element. This table is indexed in
    order to optimize retrieval o…
    1.3.6.1.2.1.124.11 pmDebuggingTable 1 6 Policies that have debugging turned on will generate a log
    entry in the policy debugging table for every runtime
    exception that o…
    1.3.6.1.2.1.124.12 pmConformance 2 7 None