A registration table for element types managed by this
system.
Before registering an element type, it is the responsibility
of a manager to inspect the table and see if it is already
registered (by the agent or another manager). Note that
entries that differ only in the last OID (which specifies
which object in an entry) are effectively duplicates and
should be treated as such by the manager.
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.
Parsed from file POLICY-MANAGEMENT-MIB-snmpconf-05.txt
Company: None
Module: POLICY-MANAGEMENT-MIB
The role string table with element as the major index.
Parsed from file POLICY-MANAGEMENT-MIB.mib
Module: POLICY-MANAGEMENT-MIB
pmElementTypeRegTable OBJECT-TYPE SYNTAX SEQUENCE OF PmElementTypeRegEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A registration table for element types managed by this system. Before registering an element type, it is the responsibility of a manager to inspect the table and see if it is already registered (by the agent or another manager). Note that entries that differ only in the last OID (which specifies which object in an entry) are effectively duplicates and should be treated as such by the manager. 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." ::= { policyMgt 3 }
pmRoleESTable OBJECT-TYPE SYNTAX SEQUENCE OF PmRoleESEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The role string table with element as the major index." ::= { policyMgt 3 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.3.107.3.1 | pmElementTypeRegEntry, pmRoleESEntry | 6 | 6 | A registration of an element type. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.3.107.1 | pmPolicyTable | 1 | 21 | The policy table. A policy is a pairing of a policyFilter and a policyAction which is used to apply the action to a selected set … |
| 1.3.6.1.3.107.2 | pmPolicyCodeTable, pmElementTypeRegTable | 1 | 5 | A registration table for element types managed by this system. |
| 1.3.6.1.3.107.4 | pmRoleTable, pmRoleSETable | 1 | 7 | The role string table. The agent must store role string associations in nonvolatile storage. |
| 1.3.6.1.3.107.5 | pmCapabilitiesTable | 1 | 8 | The pmCapabilitiesTable contains a description of the inherent capabilities of the system. |
| 1.3.6.1.3.107.6 | pmCapabilitiesTable, pmCapabilitiesOverrideTable, pmTrackingPolicyToElementTable | 1 | 8 | The pmTrackingPolicyToElementTable describes what elements are under control of a policy. |
| 1.3.6.1.3.107.7 | pmSchedLocalTime, pmTrackingElementToPolicyTable | 1 | 3 | The pmTrackingElementToPolicyTable describes what policies are controlling an element. |
| 1.3.6.1.3.107.8 | pmSchedTable, pmDebuggingTable | 1 | 16 | This table defines schedules for policies. |
| 1.3.6.1.3.107.9 | pmTrackingPolicyToElementTable, pmTrackingPETable | 1 | 5 | The pmTrackingPolicyToElementTable describes what elements are under control of a policy. This table is indexed in order to optim… |
| 1.3.6.1.3.107.10 | pmTrackingElementToPolicyTable, pmTrackingEPTable | 1 | 5 | The pmTrackingElementToPolicyTable describes what policies are controlling an element. This table is indexed in order to optimize… |
| 1.3.6.1.3.107.11 | pmDebuggingTable | 1 | 6 | The pmDebuggingTable logs debugging messages when policies experience run-time exceptions in either the filter or action code and… |
| 1.3.6.1.3.107.12 | pmNotificationRegTable, pmNotifications | 3 | 7 | A manager that wishes to receive notifications about new roles or capabilities on an agent places an entry in the notification re… |
| 1.3.6.1.3.107.13 | pmNotifications | 2 | 2 | None |
| 1.3.6.1.3.107.20 | pmConformance | 2 | 7 | None |