smilint output for ./APM-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| change recommended | 1 |
| warning | 5 |
| Message Types |
|---|
| Type | Count |
|---|
| index-exceeds-too-large (warning) | 3 |
| module-identity-registration (change recommended) | 1 |
| type-without-format (warning) | 2 |
Messages:
APM-MIB
1: -- extracted from rfc3729.txt
2: -- at Tue Mar 2 06:17:22 2004
19:
20: apm MODULE-IDENTITY
20: change recommended -
warning: uncontrolled MODULE-IDENTITY registration
21: LAST-UPDATED "200402190000Z" -- February 19, 2004
22: ORGANIZATION "IETF RMON MIB Working Group"
23: CONTACT-INFO
24: "Author:
25: Steve Waldbusser
26:
27: Phone: +1-650-948-6500
28: Fax : +1-650-745-0671
29: Email: waldbusser@nextbeacon.com
30:
31: Working Group Chair:
32: Andy Bierman
33: Cisco Systems, Inc.
34: Postal: 170 West Tasman Drive
35: San Jose, CA USA 95134
36: Tel: +1 408 527-3711
37: E-mail: abierman@cisco.com
38:
39: Working Group Mailing List: <rmonmib@ietf.org>
40: To subscribe send email to: <rmonmib-request@ietf.org>
41: "
42: DESCRIPTION
43: "The MIB module for measuring application performance
44: as experienced by end-users.
45:
46: Copyright (C) The Internet Society (2004). This version of
47: this MIB module is part of RFC 3729; see the RFC itself for
48: full legal notices."
49:
50: REVISION "200402190000Z" -- February 19, 2004
51: DESCRIPTION
52: "The original version of this MIB Module, published as
53: RFC3729."
54:
55: ::= { rmon 23 }
...
62:
63: AppLocalIndex ::= TEXTUAL-CONVENTION
63: warning -
warning: type `AppLocalIndex' has no format specification
64: STATUS current
65: DESCRIPTION
66: "A locally arbitrary unique identifier associated with an
67: application or application verb.
68:
69: All objects of type AppLocalIndex are assigned by the agent
70: out of a common number space. In other words, AppLocalIndex
71: values assigned to entries in one table must not overlap with
72: AppLocalIndex values assigned to entries in another
73: table. Further, every protocolDirLocalIndex value registered
74: by the agent automatically assigns the same value out of the
75: AppLocalIndex number space.
76:
77: For example, if the protocolDirLocalIndex values { 1, 3, 5, 7 }
78: have been assigned, and the apmHttpFilterAppLocalIndex values
79: { 6, 8, 9 } have been assigned:
80:
81: - Assignment of new AppLocalIndex values must not use the
82: values { 1, 3, 5, 6, 7, 8, 9 }.
83: - AppLocalIndex values { 1, 3, 5, 7 } are automatically
84: assigned and are associated with the identical value of
85: protocolDirLocalIndex. In particular, an entry in the
86: apmAppDirTable indexed by a value provides further
87: information about a protocol indexed by the same value
88: in the protocolDirTable of RMON2.
89:
90: The value for each supported application must remain constant
91: at least from one re-initialization of the entity's network
92: management system to the next re-initialization, except that
93: if an application is deleted and re-created, it must be
94: re-created with a new value that has not been used since the
95: last re-initialization.
96:
97: The specific value is meaningful only within a given SNMP
98: entity. An AppLocalIndex value must not be re-used until the
99: next agent restart."
100: SYNTAX Unsigned32 (1..2147483647)
...
142:
143: RmonClientID ::= TEXTUAL-CONVENTION
143: warning -
warning: type `RmonClientID' has no format specification
144: STATUS current
145: DESCRIPTION
146: "A long-lived unique ID assigned to an end-system. This ID is
147: assigned by the agent using an implementation-specific
148: algorithm.
149:
150: Because a client machine may be assigned multiple addresses
151: over any time period it can be difficult to attribute
152: behavior to a particular client based solely on its
153: address. A ClientID may be assigned to provide a more
154: stable handle for referencing that client. The entity that
155: assigns the ClientID may use various implementation
156: techniques to keep track of a client but if the assigning
157: entity is unable to track client address mappings, it may map
158: client identifiers to client addresses rather than to
159: distinct client machines.
160:
161: This is named ClientID because it helps to solve a problem
162: seen in network clients (servers usually have well-known,
163: long-lived addresses). However, ClientID's may be assigned to
164: any end-system regardless of its role on the network."
165: SYNTAX Unsigned32 (0..4294967295)
166:
...
913:
914: apmNameEntry OBJECT-TYPE
914: warning -
warning: index of row `apmNameEntry' can exceed OID size limit by 154 subidentifier(s)
915: SYNTAX ApmNameEntry
916: MAX-ACCESS not-accessible
917: STATUS current
918: DESCRIPTION
919: "An entry in the APM name table. An entry exists for each
920: period of time that a client has been associated with a
921: particular address.
922:
923: The protocolDirLocalIndex value in the index identifies
924: the network layer protocol for the ClientAddress for this
925: entry.
926:
927: Note that some combinations of index values may result in an
928: index that exceeds 128 sub-identifiers in length which exceeds
929: the maximum for the SNMP protocol. Implementations should take
930: care to avoid such combinations."
931: INDEX { apmNameClientID,
932: protocolDirLocalIndex, apmNameClientAddress,
933: apmNameMappingStartTime }
934: ::= { apmNameTable 1 }
935:
936: ApmNameEntry ::= SEQUENCE {
937: apmNameClientID RmonClientID,
938: apmNameClientAddress ProtocolDirNetworkAddress,
939: apmNameMappingStartTime DateAndTime,
940: apmNameMachineName SnmpAdminString,
941: apmNameUserName SnmpAdminString
942: }
...
1368:
1369: apmReportEntry OBJECT-TYPE
1369: warning -
warning: index of row `apmReportEntry' can exceed OID size limit by 146 subidentifier(s)
1370: SYNTAX ApmReportEntry
1371: MAX-ACCESS not-accessible
1372: STATUS current
1373: DESCRIPTION
1374: "A conceptual row in the apmReportTable.
1375: The apmReportControlIndex value in the index identifies the
1376: apmReportControlEntry on whose behalf this entry was created.
1377: The apmReportIndex value in the index identifies which report
1378: (in the series of reports) this entry is a part of.
1379: The apmAppDirAppLocalIndex value in the index identifies
1380: the common application of the transactions aggregated in this
1381: entry.
1382: The apmAppDirResponsivenessType value in the index
1383: identifies the type of responsiveness metric reported by
1384: this entry and uniquely identifies this entry when more
1385: than one responsiveness metric is measured for a flow.
1386: Entries will only exist in this table for those
1387: combinations of AppLocalIndex and ResponsivenessType
1388: that are configured 'on(1)'.
1389: The protocolDirLocalIndex value in the index identifies
1390: the network layer protocol of the apmReportServerAddress.
1391: When the associated apmReportControlAggregationType value is
1392: equal to applications(4) or clients(2), this
1393: protocolDirLocalIndex value will equal 0.
1394: The apmReportServerAddress value in the index identifies the
1395: network layer address of the server in transactions aggregated
1396: in this entry.
1397: The apmNameClientID value in the index identifies the
1398: client in transactions aggregated in this entry. If the
1399: associated apmReportControlAggregationType is equal to
1400: applications(4) or servers(3), then this protocolDirLocalIndex
1401: value will equal 0.
1402:
1403: An example of the indexing of this entry is
1404: apmReportTransactionCount.3.15.3.1.8.4.192.168.1.2.3232235788
1405:
1406: Note that some combinations of index values may result in an
1407: index that exceeds 128 sub-identifiers in length which exceeds
1408: the maximum for the SNMP protocol. Implementations should take
1409: care to avoid such combinations."
1410: INDEX { apmReportControlIndex, apmReportIndex,
1411: apmAppDirAppLocalIndex,
1412: apmAppDirResponsivenessType,
1413: protocolDirLocalIndex, apmReportServerAddress,
1414: apmNameClientID }
1415: ::= { apmReportTable 1 }
1416:
1417: ApmReportEntry ::= SEQUENCE {
1418: apmReportIndex Unsigned32,
1419: apmReportServerAddress ProtocolDirNetworkAddress,
1420: apmReportTransactionCount Unsigned32,
1421: apmReportSuccessfulTransactions Unsigned32,
1422: apmReportResponsivenessMean Unsigned32,
1423: apmReportResponsivenessMin Unsigned32,
1424: apmReportResponsivenessMax Unsigned32,
1425: apmReportResponsivenessB1 Unsigned32,
1426: apmReportResponsivenessB2 Unsigned32,
1427: apmReportResponsivenessB3 Unsigned32,
1428: apmReportResponsivenessB4 Unsigned32,
1429: apmReportResponsivenessB5 Unsigned32,
1430: apmReportResponsivenessB6 Unsigned32,
1431: apmReportResponsivenessB7 Unsigned32
1432: }
...
1609:
1610: apmTransactionEntry OBJECT-TYPE
1610: warning -
warning: index of row `apmTransactionEntry' can exceed OID size limit by 145 subidentifier(s)
1611: SYNTAX ApmTransactionEntry
1612: MAX-ACCESS not-accessible
1613: STATUS current
1614: DESCRIPTION
1615: "A conceptual row in the apmTransactionTable.
1616:
1617: The apmAppDirAppLocalIndex value in the index identifies
1618: the application of the transaction represented by this entry.
1619: The apmAppDirResponsivenessType value in the index
1620: identifies the type of responsiveness metric reported by
1621: this entry and uniquely identifies this entry when more
1622: than one responsiveness metric is measured for a flow.
1623: Entries will only exist in this table for those
1624: combinations of AppLocalIndex and ResponsivenessType
1625: that are configured 'on(1)'.
1626: The protocolDirLocalIndex value in the index identifies
1627: the network layer protocol of the apmTransactionServerAddress.
1628: The apmTransactionServerAddress value in the index identifies
1629: the network layer address of the server in the transaction
1630: represented by this entry.
1631: The apmNameClientID value in the index identifies the
1632: client in the transaction represented by this entry.
1633:
1634: An example of the indexing of this entry is
1635: apmTransactionCount.3.1.8.4.192.168.1.2.3232235788.2987
1636:
1637: Note that some combinations of index values may result in an
1638: index that exceeds 128 sub-identifiers in length which exceeds
1639: the maximum for the SNMP protocol. Implementations should take
1640: care to avoid such combinations."
1641: INDEX { apmAppDirAppLocalIndex,
1642: apmAppDirResponsivenessType,
1643: protocolDirLocalIndex, apmTransactionServerAddress,
1644: apmNameClientID, apmTransactionID }
1645: ::= { apmTransactionTable 1 }
1646:
1647: ApmTransactionEntry ::= SEQUENCE {
1648: apmTransactionServerAddress ProtocolDirNetworkAddress,
1649: apmTransactionID Unsigned32,
1650: apmTransactionResponsiveness Unsigned32,
1651: apmTransactionAge TimeInterval,
1652: apmTransactionSuccess TruthValue
1653: }