smilint output for ./POLICY-BASED-MANAGEMENT-MIB

Messages:

POLICY-BASED-MANAGEMENT-MIB

   1: -- extracted from rfc4011.txt
   2: -- at Sat Mar 12 06:25:41 2005

 761: 
 762: pmElementTypeRegEntry OBJECT-TYPE

 763:     SYNTAX      PmElementTypeRegEntry
 764:     MAX-ACCESS  not-accessible
 765:     STATUS      current
 766:     DESCRIPTION
 767:         "A registration of an element type.
 768: 
 769:         Note that some values of this table's index may result in an
 770:         instance name that exceeds a length of 128 sub-identifiers,
 771:         which exceeds the maximum for the SNMP protocol.
 772:         Implementations should take care to avoid such values."
 773:     INDEX       { pmElementTypeRegOIDPrefix }
 774:     ::= { pmElementTypeRegTable 1 }
 775: 
 776: PmElementTypeRegEntry ::= SEQUENCE {
 777:     pmElementTypeRegOIDPrefix     OBJECT IDENTIFIER,
 778:     pmElementTypeRegMaxLatency    Unsigned32,
 779:     pmElementTypeRegDescription   PmUTF8String,
 780:     pmElementTypeRegStorageType   StorageType,
 781:     pmElementTypeRegRowStatus     RowStatus
 782: }
 783: 
 784: pmElementTypeRegOIDPrefix OBJECT-TYPE

 785:     SYNTAX      OBJECT IDENTIFIER
 786:     MAX-ACCESS  not-accessible
 787:     STATUS      current
 788:     DESCRIPTION
 789:         "This OBJECT IDENTIFIER value identifies a table in which all
 790:         elements of this type will be found.  Every row in the
 791:         referenced table will be treated as an element for the
 792:         period of time that it remains in the table.  The agent will
 793:         then execute policy conditions and actions as appropriate on
 794:         each of these elements.
 795: 
 796:         This object identifier value is specified down to the 'entry'
 797:         component (e.g., ifEntry) of the identifier.
 798: 
 799:         The index of each discovered row will be passed to each
 800:         invocation of the policy condition and policy action.
 801: 
 802:         The actual mechanism by which instances are discovered is
 803:         implementation dependent.  Periodic walks of the table to
 804:         discover the rows in the table is one such mechanism.  This
 805:         mechanism has the advantage that it can be performed by an
 806:         agent with no knowledge of the names, syntax, or semantics
 807:         of the MIB objects in the table.  This mechanism also serves as
 808:         the reference design.  Other implementation-dependent
 809:         mechanisms may be implemented that are more efficient (perhaps
 810:         because they are hard coded) or that don't require polling.
 811:         These mechanisms must discover the same elements as would the
 812:         table-walking reference design.
 813: 
 814:         This object can contain a OBJECT IDENTIFIER, '0.0'.
 815:         '0.0' represents the single instance of the system
 816:         itself and provides an execution context for policies to
 817:         operate on the 'system element' and on MIB objects
 818:         modeled as scalars.  For example, '0.0' gives an execution
 819:         context for policy-based selection of the operating system
 820:         code version (likely modeled as a scalar MIB object).  The
 821:         element type '0.0' always exists; as a consequence, no actual
 822:         discovery will take place, and the pmElementTypeRegMaxLatency
 823:         object will have no effect for the '0.0' element
 824:         type.  However, if the '0.0' element type is not registered in
 825:         the table, policies will not be executed on the '0.0' element.
 826: 
 827:         When a policy is invoked on behalf of a '0.0' entry in this
 828:         table, the element name will be '0.0', and there is no index
 829:         of 'this element' (in other words, it has zero length).
 830: 
 831:         As this object is used in the index for the
 832:         pmElementTypeRegTable, users of this table should be careful
 833:         not to create entries that would result in instance names with
 834:         more than 128 sub-identifiers."
 835:     ::= { pmElementTypeRegEntry 2 }
...
 932: 
 933: pmRoleEntry OBJECT-TYPE

 934:     SYNTAX      PmRoleEntry
 935:     MAX-ACCESS  not-accessible
 936:     STATUS      current
 937:     DESCRIPTION
 938:          "A role string entry associates a role string with an
 939:          individual element.
 940: 
 941:          Note that some combinations of index values may result in an
 942:          instance name that exceeds a length of 128 sub-identifiers,
 943:          which exceeds the maximum for the SNMP
 944:          protocol.  Implementations should take care to avoid such
 945:          combinations."
 946:     INDEX       { pmRoleElement, pmRoleContextName,
 947:                   pmRoleContextEngineID, pmRoleString }
 948:     ::= { pmRoleTable 1 }
 949: 
 950: PmRoleEntry ::= SEQUENCE {
 951:     pmRoleElement          RowPointer,
 952:     pmRoleContextName      SnmpAdminString,
 953:     pmRoleContextEngineID  OCTET STRING,
 954:     pmRoleString           PmUTF8String,
 955:     pmRoleStatus           RowStatus
 956: }
 957: 
 958: pmRoleElement OBJECT-TYPE

 959:     SYNTAX      RowPointer
 960:     MAX-ACCESS  not-accessible
 961:     STATUS      current
 962:     DESCRIPTION
 963:          "The element with which this role string is associated.
 964: 
 965:          For example, if the element is interface 3, then this object
 966:          will contain the OID for 'ifIndex.3'.
 967: 
 968:          If the agent assigns new indexes in the MIB table to
 969:          represent the same underlying element (re-indexing), the
 970:          agent will modify this value to contain the new index for the
 971:          underlying element.
 972: 
 973:          As this object is used in the index for the pmRoleTable,
 974:          users of this table should be careful not to create entries
 975:          that would result in instance names with more than 128
 976:          sub-identifiers."
 977:     ::= { pmRoleEntry 1 }
...
1047: 
1048: pmCapabilitiesEntry OBJECT-TYPE

1049:     SYNTAX      PmCapabilitiesEntry
1050:     MAX-ACCESS  not-accessible
1051:     STATUS      current
1052:     DESCRIPTION
1053:          "A capabilities entry holds an OID indicating support for a
1054:          particular capability.  Capabilities may include hardware and
1055:          software functions and the implementation of MIB
1056:          Modules.  The semantics of the OID are defined in the
1057:          description of pmCapabilitiesType.
1058: 
1059:          Entries appear in this table if any element in the system has
1060:          a specific capability.  A capability should appear in this
1061:          table only once, regardless of the number of elements in the
1062:          system with that capability.  An entry is removed from this
1063:          table when the last element in the system that has the
1064:          capability is removed.  In some cases, capabilities are
1065:          dynamic and exist only in software.  This table should have an
1066:          entry for the capability even if there are no current
1067:          instances.  Examples include systems with database or WEB
1068:          services.  While the system has the ability to create new
1069:          databases or WEB services, the entry should exist.  In these
1070:          cases, the ability to create these services could come from
1071:          other processes that are running in the system, even though
1072:          there are no currently open databases or WEB servers running.
1073:          Capabilities may include the implementation of MIB Modules
1074:          but need not be limited to those that represent MIB Modules
1075:          with one or more configurable objects.  It may also be
1076:          valuable to include entries for capabilities that do not
1077:          include configuration objects, as that information, in
1078:          combination with other entries in this table, might be used
1079:          by the management software to determine whether to
1080:          install a policy.
1081: 
1082:          Vendor software may also add entries in this table to express
1083:          capabilities from their private branch.
1084: 
1085:          Note that some values of this table's index may result in an
1086:          instance name that exceeds a length of 128 sub-identifiers,
1087:          which exceeds the maximum for the SNMP
1088:          protocol.  Implementations should take care to avoid such
1089:          values."
1090:     INDEX       { pmCapabilitiesType }
1091:     ::= { pmCapabilitiesTable 1 }
1092: 
1093: PmCapabilitiesEntry ::= SEQUENCE {
1094:     pmCapabilitiesType               OBJECT IDENTIFIER
1095: }
1096: 
1097: pmCapabilitiesType OBJECT-TYPE

1098:     SYNTAX      OBJECT IDENTIFIER
1099:     MAX-ACCESS  read-only
1100:     STATUS      current
1101:     DESCRIPTION
1102:          "There are three types of OIDs that may be present in the
1103:          pmCapabilitiesType object:
1104: 
1105:          1) The OID of a MODULE-COMPLIANCE macro that represents the
1106:          highest level of compliance realized by the agent for that
1107:          MIB Module.  For example, an agent that implements the OSPF
1108:          MIB Module at the highest level of compliance would have the
1109:          value of '1.3.6.1.2.1.14.15.2' in the pmCapabilitiesType
1110:          object.  For software that realizes standard MIB
1111:          Modules that do not have compliance statements, the base OID
1112:          of the MIB Module should be used instead.  If the OSPF MIB
1113:          Module had not been created with a compliance statement, then
1114:          the correct value of the pmCapabilitiesType would be
1115:          '1.3.6.1.2.1.14'.  In the cases where multiple compliance
1116:          statements in a MIB Module are supported by the agent, and
1117:          where one compliance statement does not by definition include
1118:          the other, each of the compliance OIDs would have entries in
1119:          this table.
1120:          MIB Documents can contain more than one MIB Module.  In the
1121:          case of OSPF, there is a second MIB Module
1122:          that describes notifications for the OSPF Version 2 Protocol.
1123:          If the agent also realizes these functions, an entry will
1124:          also exist for those capabilities in this table.
1125: 
1126:          2) Vendors should install OIDs in this table that represent
1127:          vendor-specific capabilities.  These capabilities can be
1128:          expressed just as those described above for MIB Modules on
1129:          the standards track.  In addition, vendors may install any
1130:          OID they desire from their registered branch.  The OIDs may be
1131:          at any level of granularity, from the root of their entire
1132:          branch to an instance of a single OID.  There is no
1133:          restriction on the number of registrations they may make,
1134:          though care should be taken to avoid unnecessary entries.
1135: 
1136:          3) OIDs that represent one capability or a collection of
1137:          capabilities that could be any collection of MIB Objects or
1138:          hardware or software functions may be created in working
1139:          groups and registered in a MIB Module.  Other entities (e.g.,
1140:          vendors) may also make registrations.  Software will register
1141:          these standard capability OIDs, as well as vendor specific
1142:          OIDs.
1143: 
1144:          If the OID for a known capability is not present in the
1145:          table, then it should be assumed that the capability is not
1146:          implemented.
1147: 
1148:          As this object is used in the index for the
1149:          pmCapabilitiesTable, users of this table should be careful
1150:          not to create entries that would result in instance names
1151:          with more than 128 sub-identifiers."
1152:     ::= { pmCapabilitiesEntry 1 }
1153: 
1154: -- Capabilities override table
...
1179: 
1180: pmCapabilitiesOverrideEntry OBJECT-TYPE

1181:     SYNTAX      PmCapabilitiesOverrideEntry
1182:     MAX-ACCESS  not-accessible
1183:     STATUS      current
1184:     DESCRIPTION
1185:          "An entry in this table indicates whether a particular
1186:          capability is valid or invalid.
1187: 
1188:          Note that some values of this table's index may result in an
1189:          instance name that exceeds a length of 128 sub-identifiers,
1190:          which exceeds the maximum for the SNMP
1191:          protocol.  Implementations should take care to avoid such
1192:          values."
1193:     INDEX       { pmCapabilitiesOverrideType }
1194:     ::= { pmCapabilitiesOverrideTable 1 }
1195: 
1196: PmCapabilitiesOverrideEntry ::= SEQUENCE {
1197:     pmCapabilitiesOverrideType               OBJECT IDENTIFIER,
1198:     pmCapabilitiesOverrideState              INTEGER,
1199:     pmCapabilitiesOverrideRowStatus          RowStatus
1200: }
1201: 
1202: pmCapabilitiesOverrideType OBJECT-TYPE

1203:     SYNTAX      OBJECT IDENTIFIER
1204:     MAX-ACCESS  not-accessible
1205:     STATUS      current
1206:     DESCRIPTION
1207:          "This is the OID of the capability that is declared valid or
1208:          invalid by the pmCapabilitiesOverrideState value for this
1209:          row.  Any valid OID, as described in the pmCapabilitiesTable,
1210:          is permitted in the pmCapabilitiesOverrideType object.  This
1211:          means that capabilities can be expressed at any level, from a
1212:          specific instance of an object to a table or entire module.
1213:          There are no restrictions on whether these objects are from
1214:          standards track MIB documents or in the private branch of the
1215:          MIB.
1216:          If an entry exists in this table for which there is a
1217:          corresponding entry in the pmCapabilitiesTable, then this entry
1218:          shall have precedence over the entry in the
1219:          pmCapabilitiesTable.  All entries in this table must be
1220:          preserved across reboots.
1221: 
1222:          As this object is used in the index for the
1223:          pmCapabilitiesOverrideTable, users of this table should be
1224:          careful not to create entries that would result in instance
1225:          names with more than 128 sub-identifiers."
1226:     ::= { pmCapabilitiesOverrideEntry 1 }
...
1619: 
1620: pmTrackingPEEntry OBJECT-TYPE

1621:     SYNTAX      PmTrackingPEEntry
1622:     MAX-ACCESS  not-accessible
1623:     STATUS      current
1624:     DESCRIPTION
1625:          "An entry in the pmTrackingPETable.  The pmPolicyIndex in
1626:          the index specifies the policy tracked by this entry.
1627: 
1628:          Note that some combinations of index values may result in an
1629:          instance name that exceeds a length of 128 sub-identifiers,
1630:          which exceeds the maximum for the SNMP
1631:          protocol.  Implementations should take care to avoid such
1632:          combinations."
1633:     INDEX       { pmPolicyIndex, pmTrackingPEElement,
1634:                   pmTrackingPEContextName, pmTrackingPEContextEngineID }
1635:     ::= { pmTrackingPETable 1 }
1636: 
1637: PmTrackingPEEntry ::= SEQUENCE {
1638:     pmTrackingPEElement          RowPointer,
1639:     pmTrackingPEContextName      SnmpAdminString,
1640:     pmTrackingPEContextEngineID  OCTET STRING,
1641:     pmTrackingPEInfo             BITS
1642: }
1643: 
1644: pmTrackingPEElement OBJECT-TYPE

1645:     SYNTAX      RowPointer
1646:     MAX-ACCESS  not-accessible
1647:     STATUS      current
1648:     DESCRIPTION
1649:          "The element that is acted upon by the associated policy.
1650: 
1651:          As this object is used in the index for the
1652:          pmTrackingPETable, users of this table should be careful not
1653:          to create entries that would result in instance names with
1654:          more than 128 sub-identifiers."
1655:     ::= { pmTrackingPEEntry 1 }
...
1734: 
1735: pmTrackingEPEntry OBJECT-TYPE

1736:     SYNTAX      PmTrackingEPEntry
1737:     MAX-ACCESS  not-accessible
1738:     STATUS      current
1739:     DESCRIPTION
1740:          "An entry in the pmTrackingEPTable.  Entries exist for all
1741:          element/policy combinations for which the policy's condition
1742:          matches and only if the schedule for the policy is active.
1743: 
1744:          The pmPolicyIndex in the index specifies the policy
1745:          tracked by this entry.
1746: 
1747:          Note that some combinations of index values may result in an
1748:          instance name that exceeds a length of 128 sub-identifiers,
1749:          which exceeds the maximum for the SNMP protocol.
1750:          Implementations should take care to avoid such combinations."
1751:     INDEX       { pmTrackingEPElement, pmTrackingEPContextName,
1752:                   pmTrackingEPContextEngineID, pmPolicyIndex }
1753:     ::= { pmTrackingEPTable 1 }
1754: 
1755: PmTrackingEPEntry ::= SEQUENCE {
1756:     pmTrackingEPElement          RowPointer,
1757:     pmTrackingEPContextName      SnmpAdminString,
1758:     pmTrackingEPContextEngineID  OCTET STRING,
1759:     pmTrackingEPStatus           INTEGER
1760: }
1761: 
1762: pmTrackingEPElement OBJECT-TYPE

1763:     SYNTAX      RowPointer
1764:     MAX-ACCESS  not-accessible
1765:     STATUS      current
1766:     DESCRIPTION
1767:          "The element acted upon by the associated policy.
1768: 
1769:          As this object is used in the index for the
1770:          pmTrackingEPTable, users of this table should be careful
1771:          not to create entries that would result in instance names
1772:          with more than 128 sub-identifiers."
1773:     ::= { pmTrackingEPEntry 1 }
...
1848: 
1849: pmDebuggingEntry OBJECT-TYPE

1850:     SYNTAX      PmDebuggingEntry
1851:     MAX-ACCESS  not-accessible
1852:     STATUS      current
1853:     DESCRIPTION
1854:          "An entry in the pmDebuggingTable.  The pmPolicyIndex in the
1855:          index specifies the policy that encountered the exception
1856:          that led to this log entry.
1857: 
1858:          Note that some combinations of index values may result in an
1859:          instance name that exceeds a length of 128 sub-identifiers,
1860:          which exceeds the maximum for the SNMP protocol.
1861:          Implementations should take care to avoid such combinations."
1862:     INDEX       { pmPolicyIndex, pmDebuggingElement,
1863:                   pmDebuggingContextName, pmDebuggingContextEngineID,
1864:                   pmDebuggingLogIndex }
1865:     ::= { pmDebuggingTable 1 }
1866: 
1867: PmDebuggingEntry ::= SEQUENCE {
1868:     pmDebuggingElement          RowPointer,
1869:     pmDebuggingContextName      SnmpAdminString,
1870:     pmDebuggingContextEngineID  OCTET STRING,
1871:     pmDebuggingLogIndex         Unsigned32,
1872:     pmDebuggingMessage          PmUTF8String
1873: }
1874: pmDebuggingElement OBJECT-TYPE

1875:     SYNTAX      RowPointer
1876:     MAX-ACCESS  not-accessible
1877:     STATUS      current
1878:     DESCRIPTION
1879:          "The element the policy was executing on when it encountered
1880:          the error that led to this log entry.
1881: 
1882:          For example, if the element is interface 3, then this object
1883:          will contain the OID for 'ifIndex.3'.
1884: 
1885:          As this object is used in the index for the
1886:          pmDebuggingTable, users of this table should be careful
1887:          not to create entries that would result in instance names
1888:          with more than 128 sub-identifiers."
1889:     ::= { pmDebuggingEntry 1 }