telemetry-snmp 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (131) hide show
  1. checksums.yaml +7 -0
  2. data/.github/workflows/rspec.yml +44 -0
  3. data/.github/workflows/rubocop.yml +28 -0
  4. data/.github/workflows/sourcehawk-scan.yml +20 -0
  5. data/.gitignore +14 -0
  6. data/.rspec +4 -0
  7. data/.rubocop.yml +26 -0
  8. data/CHANGELOG.md +4 -0
  9. data/CODE_OF_CONDUCT.md +75 -0
  10. data/CONTRIBUTING.md +54 -0
  11. data/Gemfile +10 -0
  12. data/INDIVIDUAL_CONTRIBUTOR_LICENSE.md +30 -0
  13. data/LICENSE +201 -0
  14. data/NOTICE.txt +9 -0
  15. data/README.md +54 -0
  16. data/attribution.txt +1 -0
  17. data/config.ru +15 -0
  18. data/exe/snmp_collector +55 -0
  19. data/lib/telemetry/snmp.rb +23 -0
  20. data/lib/telemetry/snmp/api.rb +55 -0
  21. data/lib/telemetry/snmp/auth.rb +54 -0
  22. data/lib/telemetry/snmp/auth/defaults.rb +41 -0
  23. data/lib/telemetry/snmp/client.rb +104 -0
  24. data/lib/telemetry/snmp/controllers/device_creds.rb +105 -0
  25. data/lib/telemetry/snmp/controllers/devices.rb +94 -0
  26. data/lib/telemetry/snmp/controllers/oid_groups.rb +71 -0
  27. data/lib/telemetry/snmp/controllers/oids.rb +80 -0
  28. data/lib/telemetry/snmp/controllers/users.rb +81 -0
  29. data/lib/telemetry/snmp/controllers/walks.rb +89 -0
  30. data/lib/telemetry/snmp/data.rb +69 -0
  31. data/lib/telemetry/snmp/data/default_opts.rb +73 -0
  32. data/lib/telemetry/snmp/data/migrations/001_device_creds.rb +19 -0
  33. data/lib/telemetry/snmp/data/migrations/002_create_devices_table.rb +31 -0
  34. data/lib/telemetry/snmp/data/migrations/003_create_oids_tables.rb +16 -0
  35. data/lib/telemetry/snmp/data/migrations/004_create_oid_groups.rb +15 -0
  36. data/lib/telemetry/snmp/data/migrations/005_create_oids_oid_groups.rb +17 -0
  37. data/lib/telemetry/snmp/data/migrations/006_device_to_oid_group.rb +15 -0
  38. data/lib/telemetry/snmp/data/migrations/007_create_users.rb +20 -0
  39. data/lib/telemetry/snmp/data/migrations/008_create_walks_table.rb +14 -0
  40. data/lib/telemetry/snmp/data/migrations/009_create_tag_name_column.rb +7 -0
  41. data/lib/telemetry/snmp/data/migrations/010_create_user_audit_table.rb +18 -0
  42. data/lib/telemetry/snmp/data/models/device.rb +11 -0
  43. data/lib/telemetry/snmp/data/models/device_cred.rb +11 -0
  44. data/lib/telemetry/snmp/data/models/oid.rb +10 -0
  45. data/lib/telemetry/snmp/data/models/oid_group.rb +10 -0
  46. data/lib/telemetry/snmp/data/models/oid_oid_groups.rb +10 -0
  47. data/lib/telemetry/snmp/data/models/oid_walk.rb +10 -0
  48. data/lib/telemetry/snmp/data/models/user.rb +10 -0
  49. data/lib/telemetry/snmp/data/models/user_audit_log.rb +19 -0
  50. data/lib/telemetry/snmp/mibs/AGENTX-MIB.txt +527 -0
  51. data/lib/telemetry/snmp/mibs/AIRPORT-BASESTATION-3-MIB.txt +461 -0
  52. data/lib/telemetry/snmp/mibs/BRIDGE-MIB.txt +1472 -0
  53. data/lib/telemetry/snmp/mibs/DISMAN-EVENT-MIB.txt +1882 -0
  54. data/lib/telemetry/snmp/mibs/DISMAN-SCHEDULE-MIB.txt +699 -0
  55. data/lib/telemetry/snmp/mibs/DISMAN-SCRIPT-MIB.txt +1764 -0
  56. data/lib/telemetry/snmp/mibs/EtherLike-MIB.txt +1862 -0
  57. data/lib/telemetry/snmp/mibs/HCNUM-TC.txt +118 -0
  58. data/lib/telemetry/snmp/mibs/HOST-RESOURCES-MIB.txt +1540 -0
  59. data/lib/telemetry/snmp/mibs/HOST-RESOURCES-TYPES.txt +389 -0
  60. data/lib/telemetry/snmp/mibs/IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt +123 -0
  61. data/lib/telemetry/snmp/mibs/IANA-LANGUAGE-MIB.txt +123 -0
  62. data/lib/telemetry/snmp/mibs/IANA-RTPROTO-MIB.txt +91 -0
  63. data/lib/telemetry/snmp/mibs/IANAifType-MIB.txt +619 -0
  64. data/lib/telemetry/snmp/mibs/IF-INVERTED-STACK-MIB.txt +149 -0
  65. data/lib/telemetry/snmp/mibs/IF-MIB.txt +1814 -0
  66. data/lib/telemetry/snmp/mibs/INET-ADDRESS-MIB.txt +402 -0
  67. data/lib/telemetry/snmp/mibs/IP-FORWARD-MIB.txt +1277 -0
  68. data/lib/telemetry/snmp/mibs/IP-MIB.txt +4993 -0
  69. data/lib/telemetry/snmp/mibs/IPV6-FLOW-LABEL-MIB.txt +58 -0
  70. data/lib/telemetry/snmp/mibs/IPV6-ICMP-MIB.txt +529 -0
  71. data/lib/telemetry/snmp/mibs/IPV6-MIB.txt +1443 -0
  72. data/lib/telemetry/snmp/mibs/IPV6-TC.txt +67 -0
  73. data/lib/telemetry/snmp/mibs/IPV6-TCP-MIB.txt +211 -0
  74. data/lib/telemetry/snmp/mibs/IPV6-UDP-MIB.txt +141 -0
  75. data/lib/telemetry/snmp/mibs/NET-SNMP-AGENT-MIB.txt +554 -0
  76. data/lib/telemetry/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt +285 -0
  77. data/lib/telemetry/snmp/mibs/NET-SNMP-EXTEND-MIB.txt +325 -0
  78. data/lib/telemetry/snmp/mibs/NET-SNMP-MIB.txt +67 -0
  79. data/lib/telemetry/snmp/mibs/NET-SNMP-PASS-MIB.txt +124 -0
  80. data/lib/telemetry/snmp/mibs/NET-SNMP-TC.txt +128 -0
  81. data/lib/telemetry/snmp/mibs/NET-SNMP-VACM-MIB.txt +154 -0
  82. data/lib/telemetry/snmp/mibs/NOTIFICATION-LOG-MIB.txt +753 -0
  83. data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.md5 +1 -0
  84. data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.my +2293 -0
  85. data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.md5 +1 -0
  86. data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.my +293 -0
  87. data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.md5 +1 -0
  88. data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.my +84 -0
  89. data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.md5 +1 -0
  90. data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.my +68 -0
  91. data/lib/telemetry/snmp/mibs/PAN-LC-MIB.md5 +1 -0
  92. data/lib/telemetry/snmp/mibs/PAN-LC-MIB.my +204 -0
  93. data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.md5 +1 -0
  94. data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.my +305 -0
  95. data/lib/telemetry/snmp/mibs/PAN-TRAPS.md5 +1 -0
  96. data/lib/telemetry/snmp/mibs/PAN-TRAPS.my +7809 -0
  97. data/lib/telemetry/snmp/mibs/RFC-1215.txt +38 -0
  98. data/lib/telemetry/snmp/mibs/RFC1155-SMI.txt +119 -0
  99. data/lib/telemetry/snmp/mibs/RFC1213-MIB.txt +2613 -0
  100. data/lib/telemetry/snmp/mibs/RMON-MIB.txt +3980 -0
  101. data/lib/telemetry/snmp/mibs/SCTP-MIB.txt +1342 -0
  102. data/lib/telemetry/snmp/mibs/SMUX-MIB.txt +160 -0
  103. data/lib/telemetry/snmp/mibs/SNMP-COMMUNITY-MIB.txt +429 -0
  104. data/lib/telemetry/snmp/mibs/SNMP-FRAMEWORK-MIB.txt +526 -0
  105. data/lib/telemetry/snmp/mibs/SNMP-MPD-MIB.txt +145 -0
  106. data/lib/telemetry/snmp/mibs/SNMP-NOTIFICATION-MIB.txt +589 -0
  107. data/lib/telemetry/snmp/mibs/SNMP-PROXY-MIB.txt +294 -0
  108. data/lib/telemetry/snmp/mibs/SNMP-TARGET-MIB.txt +660 -0
  109. data/lib/telemetry/snmp/mibs/SNMP-USER-BASED-SM-MIB.txt +912 -0
  110. data/lib/telemetry/snmp/mibs/SNMP-USM-AES-MIB.txt +62 -0
  111. data/lib/telemetry/snmp/mibs/SNMP-USM-DH-OBJECTS-MIB.txt +532 -0
  112. data/lib/telemetry/snmp/mibs/SNMP-VIEW-BASED-ACM-MIB.txt +830 -0
  113. data/lib/telemetry/snmp/mibs/SNMPv2-CONF.txt +322 -0
  114. data/lib/telemetry/snmp/mibs/SNMPv2-MIB.txt +854 -0
  115. data/lib/telemetry/snmp/mibs/SNMPv2-SMI.txt +344 -0
  116. data/lib/telemetry/snmp/mibs/SNMPv2-TC.txt +772 -0
  117. data/lib/telemetry/snmp/mibs/SNMPv2-TM.txt +176 -0
  118. data/lib/telemetry/snmp/mibs/TCP-MIB.txt +785 -0
  119. data/lib/telemetry/snmp/mibs/TRANSPORT-ADDRESS-MIB.txt +421 -0
  120. data/lib/telemetry/snmp/mibs/TUNNEL-MIB.txt +738 -0
  121. data/lib/telemetry/snmp/mibs/UCD-DEMO-MIB.txt +74 -0
  122. data/lib/telemetry/snmp/mibs/UCD-DISKIO-MIB.txt +171 -0
  123. data/lib/telemetry/snmp/mibs/UCD-DLMOD-MIB.txt +124 -0
  124. data/lib/telemetry/snmp/mibs/UCD-IPFWACC-MIB.txt +327 -0
  125. data/lib/telemetry/snmp/mibs/UCD-SNMP-MIB.txt +1712 -0
  126. data/lib/telemetry/snmp/mibs/UDP-MIB.txt +549 -0
  127. data/lib/telemetry/snmp/publisher.rb +130 -0
  128. data/lib/telemetry/snmp/version.rb +7 -0
  129. data/sourcehawk.yml +4 -0
  130. data/telemetry-snmp.gemspec +48 -0
  131. metadata +456 -0
@@ -0,0 +1,1342 @@
1
+ SCTP-MIB DEFINITIONS ::= BEGIN
2
+
3
+ IMPORTS
4
+ MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Gauge32,
5
+ Counter32, Counter64, mib-2
6
+ FROM SNMPv2-SMI -- [RFC2578]
7
+ TimeStamp, TruthValue
8
+ FROM SNMPv2-TC -- [RFC2579]
9
+ MODULE-COMPLIANCE, OBJECT-GROUP
10
+ FROM SNMPv2-CONF -- [RFC2580]
11
+ InetAddressType, InetAddress, InetPortNumber
12
+ FROM INET-ADDRESS-MIB; -- [RFC3291]
13
+
14
+ sctpMIB MODULE-IDENTITY
15
+ LAST-UPDATED "200409020000Z" -- 2nd September 2004
16
+ ORGANIZATION "IETF SIGTRAN Working Group"
17
+ CONTACT-INFO
18
+ "
19
+ WG EMail: sigtran@ietf.org
20
+
21
+ Web Page:
22
+ http://www.ietf.org/html.charters/sigtran-charter.html
23
+
24
+ Chair: Lyndon Ong
25
+ Ciena Corporation
26
+ 0480 Ridgeview Drive
27
+ Cupertino, CA 95014
28
+ USA
29
+ Tel:
30
+ Email: lyong@ciena.com
31
+
32
+ Editors: Maria-Carmen Belinchon
33
+ R&D Department
34
+ Ericsson Espana S. A.
35
+ Via de los Poblados, 13
36
+ 28033 Madrid
37
+ Spain
38
+ Tel: +34 91 339 3535
39
+ Email: Maria.C.Belinchon@ericsson.com
40
+
41
+ Jose-Javier Pastor-Balbas
42
+ R&D Department
43
+ Ericsson Espana S. A.
44
+ Via de los Poblados, 13
45
+ 28033 Madrid
46
+ Spain
47
+ Tel: +34 91 339 1397
48
+ Email: J.Javier.Pastor@ericsson.com
49
+ "
50
+ DESCRIPTION
51
+ "The MIB module for managing SCTP implementations.
52
+
53
+ Copyright (C) The Internet Society (2004). This version of
54
+ this MIB module is part of RFC 3873; see the RFC itself for
55
+ full legal notices. "
56
+
57
+ REVISION "200409020000Z" -- 2nd September 2004
58
+ DESCRIPTION " Initial version, published as RFC 3873"
59
+ ::= { mib-2 104 }
60
+
61
+ -- the SCTP base variables group
62
+
63
+ sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 }
64
+
65
+ sctpStats OBJECT IDENTIFIER ::= { sctpObjects 1 }
66
+ sctpParams OBJECT IDENTIFIER ::= { sctpObjects 2 }
67
+
68
+ -- STATISTICS
69
+ -- **********
70
+
71
+ -- STATE-RELATED STATISTICS
72
+
73
+ sctpCurrEstab OBJECT-TYPE
74
+ SYNTAX Gauge32
75
+ MAX-ACCESS read-only
76
+ STATUS current
77
+ DESCRIPTION
78
+ "The number of associations for which the current state is
79
+ either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING."
80
+ REFERENCE
81
+ "Section 4 in RFC2960 covers the SCTP Association state
82
+ diagram."
83
+ ::= { sctpStats 1 }
84
+
85
+ sctpActiveEstabs OBJECT-TYPE
86
+ SYNTAX Counter32
87
+ MAX-ACCESS read-only
88
+ STATUS current
89
+ DESCRIPTION
90
+ "The number of times that associations have made a direct
91
+ transition to the ESTABLISHED state from the COOKIE-ECHOED
92
+ state: COOKIE-ECHOED -> ESTABLISHED. The upper layer initiated
93
+ the association attempt."
94
+ REFERENCE
95
+ "Section 4 in RFC2960 covers the SCTP Association state
96
+ diagram."
97
+ ::= { sctpStats 2 }
98
+
99
+ sctpPassiveEstabs OBJECT-TYPE
100
+ SYNTAX Counter32
101
+ MAX-ACCESS read-only
102
+ STATUS current
103
+ DESCRIPTION
104
+ "The number of times that associations have made a direct
105
+ transition to the ESTABLISHED state from the CLOSED state:
106
+ CLOSED -> ESTABLISHED. The remote endpoint initiated the
107
+ association attempt."
108
+ REFERENCE
109
+ "Section 4 in RFC2960 covers the SCTP Association state
110
+ diagram."
111
+ ::= { sctpStats 3 }
112
+
113
+ sctpAborteds OBJECT-TYPE
114
+ SYNTAX Counter32
115
+ MAX-ACCESS read-only
116
+ STATUS current
117
+ DESCRIPTION
118
+ "The number of times that associations have made a direct
119
+ transition to the CLOSED state from any state using the
120
+ primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful
121
+ termination of the association."
122
+ REFERENCE
123
+ "Section 4 in RFC2960 covers the SCTP Association state
124
+ diagram."
125
+ ::= { sctpStats 4 }
126
+
127
+ sctpShutdowns OBJECT-TYPE
128
+ SYNTAX Counter32
129
+ MAX-ACCESS read-only
130
+ STATUS current
131
+ DESCRIPTION
132
+ "The number of times that associations have made a direct
133
+ transition to the CLOSED state from either the SHUTDOWN-SENT
134
+ state or the SHUTDOWN-ACK-SENT state. Graceful termination of
135
+ the association."
136
+ REFERENCE
137
+ "Section 4 in RFC2960 covers the SCTP Association state
138
+ diagram."
139
+ ::= { sctpStats 5 }
140
+
141
+ -- OTHER LAYER STATISTICS
142
+
143
+ sctpOutOfBlues OBJECT-TYPE
144
+ SYNTAX Counter32
145
+ MAX-ACCESS read-only
146
+ STATUS current
147
+ DESCRIPTION
148
+ "The number of out of the blue packets received by the host.
149
+ An out of the blue packet is an SCTP packet correctly formed,
150
+ including the proper checksum, but for which the receiver was
151
+ unable to identify an appropriate association."
152
+ REFERENCE
153
+ "Section 8.4 in RFC2960 deals with the Out-Of-The-Blue
154
+ (OOTB) packet definition and procedures."
155
+ ::= { sctpStats 6 }
156
+
157
+ sctpChecksumErrors OBJECT-TYPE
158
+ SYNTAX Counter32
159
+ MAX-ACCESS read-only
160
+ STATUS current
161
+ DESCRIPTION
162
+ "The number of SCTP packets received with an invalid
163
+ checksum."
164
+ REFERENCE
165
+ "The checksum is located at the end of the SCTP packet as per
166
+ Section 3.1 in RFC2960. RFC3309 updates SCTP to use a 32 bit
167
+ CRC checksum."
168
+ ::= { sctpStats 7 }
169
+
170
+ sctpOutCtrlChunks OBJECT-TYPE
171
+ SYNTAX Counter64
172
+ MAX-ACCESS read-only
173
+ STATUS current
174
+ DESCRIPTION
175
+ "The number of SCTP control chunks sent (retransmissions are
176
+ not included). Control chunks are those chunks different from
177
+ DATA."
178
+ REFERENCE
179
+ "Sections 1.3.5 and 1.4 in RFC2960 refer to control chunk as
180
+ those chunks different from those that contain user
181
+ information, i.e., DATA chunks."
182
+ ::= { sctpStats 8 }
183
+
184
+ sctpOutOrderChunks OBJECT-TYPE
185
+ SYNTAX Counter64
186
+ MAX-ACCESS read-only
187
+ STATUS current
188
+ DESCRIPTION
189
+ "The number of SCTP ordered data chunks sent (retransmissions
190
+ are not included)."
191
+ REFERENCE
192
+ "Section 3.3.1 in RFC2960 defines the ordered data chunk."
193
+ ::= { sctpStats 9 }
194
+
195
+ sctpOutUnorderChunks OBJECT-TYPE
196
+ SYNTAX Counter64
197
+ MAX-ACCESS read-only
198
+ STATUS current
199
+ DESCRIPTION
200
+ "The number of SCTP unordered chunks (data chunks in which the
201
+ U bit is set to 1) sent (retransmissions are not included)."
202
+ REFERENCE
203
+ "Section 3.3.1 in RFC2960 defines the unordered data chunk."
204
+ ::= { sctpStats 10 }
205
+
206
+ sctpInCtrlChunks OBJECT-TYPE
207
+ SYNTAX Counter64
208
+ MAX-ACCESS read-only
209
+ STATUS current
210
+ DESCRIPTION
211
+ "The number of SCTP control chunks received (no duplicate
212
+ chunks included)."
213
+ REFERENCE
214
+ "Sections 1.3.5 and 1.4 in RFC2960 refer to control chunk as
215
+ those chunks different from those that contain user
216
+ information, i.e., DATA chunks."
217
+ ::= { sctpStats 11 }
218
+
219
+ sctpInOrderChunks OBJECT-TYPE
220
+ SYNTAX Counter64
221
+ MAX-ACCESS read-only
222
+ STATUS current
223
+ DESCRIPTION
224
+ "The number of SCTP ordered data chunks received (no duplicate
225
+ chunks included)."
226
+ REFERENCE
227
+ "Section 3.3.1 in RFC2960 defines the ordered data chunk."
228
+ ::= { sctpStats 12 }
229
+
230
+ sctpInUnorderChunks OBJECT-TYPE
231
+ SYNTAX Counter64
232
+ MAX-ACCESS read-only
233
+ STATUS current
234
+ DESCRIPTION
235
+ "The number of SCTP unordered chunks (data chunks in which the
236
+ U bit is set to 1) received (no duplicate chunks included)."
237
+ REFERENCE
238
+ "Section 3.3.1 in RFC2960 defines the unordered data chunk."
239
+ ::= { sctpStats 13 }
240
+
241
+ sctpFragUsrMsgs OBJECT-TYPE
242
+ SYNTAX Counter64
243
+ MAX-ACCESS read-only
244
+ STATUS current
245
+ DESCRIPTION
246
+ "The number of user messages that have to be fragmented
247
+ because of the MTU."
248
+ ::= { sctpStats 14 }
249
+
250
+ sctpReasmUsrMsgs OBJECT-TYPE
251
+ SYNTAX Counter64
252
+ MAX-ACCESS read-only
253
+ STATUS current
254
+ DESCRIPTION
255
+ "The number of user messages reassembled, after conversion
256
+ into DATA chunks."
257
+ REFERENCE
258
+ "Section 6.9 in RFC2960 includes a description of the
259
+ reassembly process."
260
+ ::= { sctpStats 15 }
261
+
262
+ sctpOutSCTPPacks OBJECT-TYPE
263
+ SYNTAX Counter64
264
+ MAX-ACCESS read-only
265
+ STATUS current
266
+ DESCRIPTION
267
+ "The number of SCTP packets sent. Retransmitted DATA chunks
268
+ are included."
269
+ ::= { sctpStats 16 }
270
+
271
+ sctpInSCTPPacks OBJECT-TYPE
272
+ SYNTAX Counter64
273
+ MAX-ACCESS read-only
274
+ STATUS current
275
+ DESCRIPTION
276
+ "The number of SCTP packets received. Duplicates are
277
+ included."
278
+ ::= { sctpStats 17 }
279
+
280
+ sctpDiscontinuityTime OBJECT-TYPE
281
+ SYNTAX TimeStamp
282
+ MAX-ACCESS read-only
283
+ STATUS current
284
+ DESCRIPTION
285
+ "The value of sysUpTime on the most recent occasion at which
286
+ any one or more of this general statistics counters suffered a
287
+ discontinuity. The relevant counters are the specific
288
+ instances associated with this interface of any Counter32 or
289
+ Counter64 object contained in the SCTP layer statistics
290
+ (defined below sctpStats branch). If no such discontinuities
291
+ have occurred since the last re-initialization of the local
292
+ management subsystem, then this object contains a zero value."
293
+ REFERENCE
294
+ "The inclusion of this object is recommended by RFC2578."
295
+ ::= { sctpStats 18 }
296
+
297
+ -- PROTOCOL GENERAL VARIABLES
298
+ -- **************************
299
+
300
+ sctpRtoAlgorithm OBJECT-TYPE
301
+ SYNTAX INTEGER {
302
+ other(1), -- Other new one. Future use
303
+ vanj(2) -- Van Jacobson's algorithm
304
+ }
305
+ MAX-ACCESS read-only
306
+ STATUS current
307
+ DESCRIPTION
308
+ "The algorithm used to determine the timeout value (T3-rtx)
309
+ used for re-transmitting unacknowledged chunks."
310
+ REFERENCE
311
+ "Section 6.3.1 and 6.3.2 in RFC2960 cover the RTO calculation
312
+ and retransmission timer rules."
313
+ DEFVAL {vanj} -- vanj(2)
314
+ ::= { sctpParams 1 }
315
+
316
+ sctpRtoMin OBJECT-TYPE
317
+ SYNTAX Unsigned32
318
+ UNITS "milliseconds"
319
+ MAX-ACCESS read-only
320
+ STATUS current
321
+ DESCRIPTION
322
+ "The minimum value permitted by a SCTP implementation for the
323
+ retransmission timeout value, measured in milliseconds. More
324
+ refined semantics for objects of this type depend upon the
325
+ algorithm used to determine the retransmission timeout value.
326
+
327
+ A retransmission time value of zero means immediate
328
+ retransmission.
329
+
330
+ The value of this object has to be lower than or equal to
331
+ stcpRtoMax's value."
332
+ DEFVAL {1000} -- milliseconds
333
+ ::= { sctpParams 2 }
334
+
335
+ sctpRtoMax OBJECT-TYPE
336
+ SYNTAX Unsigned32
337
+ UNITS "milliseconds"
338
+ MAX-ACCESS read-only
339
+ STATUS current
340
+ DESCRIPTION
341
+ "The maximum value permitted by a SCTP implementation for the
342
+ retransmission timeout value, measured in milliseconds. More
343
+ refined semantics for objects of this type depend upon the
344
+ algorithm used to determine the retransmission timeout value.
345
+
346
+ A retransmission time value of zero means immediate re-
347
+ transmission.
348
+
349
+ The value of this object has to be greater than or equal to
350
+ stcpRtoMin's value."
351
+ DEFVAL {60000} -- milliseconds
352
+ ::= { sctpParams 3 }
353
+
354
+ sctpRtoInitial OBJECT-TYPE
355
+ SYNTAX Unsigned32
356
+ UNITS "milliseconds"
357
+ MAX-ACCESS read-only
358
+ STATUS current
359
+ DESCRIPTION
360
+ "The initial value for the retransmission timer.
361
+
362
+ A retransmission time value of zero means immediate re-
363
+ transmission."
364
+ DEFVAL {3000} -- milliseconds
365
+ ::= { sctpParams 4 }
366
+
367
+ sctpMaxAssocs OBJECT-TYPE
368
+ SYNTAX Integer32 (-1 | 0..2147483647)
369
+ MAX-ACCESS read-only
370
+ STATUS current
371
+ DESCRIPTION
372
+ "The limit on the total number of associations the entity can
373
+ support. In entities where the maximum number of associations
374
+ is dynamic, this object should contain the value -1."
375
+ ::= { sctpParams 5 }
376
+
377
+ sctpValCookieLife OBJECT-TYPE
378
+ SYNTAX Unsigned32
379
+ UNITS "milliseconds"
380
+ MAX-ACCESS read-only
381
+ STATUS current
382
+ DESCRIPTION
383
+ "Valid cookie life in the 4-way start-up handshake procedure."
384
+ REFERENCE
385
+ "Section 5.1.3 in RFC2960 explains the cookie generation
386
+ process. Recommended value is per section 14 in RFC2960."
387
+ DEFVAL {60000} -- milliseconds
388
+ ::= { sctpParams 6 }
389
+
390
+ sctpMaxInitRetr OBJECT-TYPE
391
+ SYNTAX Unsigned32
392
+ MAX-ACCESS read-only
393
+ STATUS current
394
+ DESCRIPTION
395
+ "The maximum number of retransmissions at the start-up phase
396
+ (INIT and COOKIE ECHO chunks). "
397
+ REFERENCE
398
+ "Section 5.1.4, 5.1.6 in RFC2960 refers to Max.Init.Retransmit
399
+ parameter. Recommended value is per section 14 in RFC2960."
400
+ DEFVAL {8} -- number of attempts
401
+ ::= { sctpParams 7 }
402
+
403
+ -- TABLES
404
+ -- ******
405
+
406
+ -- the SCTP Association TABLE
407
+
408
+ -- The SCTP association table contains information about each
409
+ -- association in which the local endpoint is involved.
410
+
411
+ sctpAssocTable OBJECT-TYPE
412
+ SYNTAX SEQUENCE OF SctpAssocEntry
413
+ MAX-ACCESS not-accessible
414
+ STATUS current
415
+ DESCRIPTION
416
+ "A table containing SCTP association-specific information."
417
+ ::= { sctpObjects 3 }
418
+
419
+ sctpAssocEntry OBJECT-TYPE
420
+ SYNTAX SctpAssocEntry
421
+ MAX-ACCESS not-accessible
422
+ STATUS current
423
+ DESCRIPTION
424
+ "General common variables and statistics for the whole
425
+ association."
426
+ INDEX { sctpAssocId }
427
+ ::= { sctpAssocTable 1 }
428
+
429
+ SctpAssocEntry ::= SEQUENCE {
430
+ sctpAssocId Unsigned32,
431
+ sctpAssocRemHostName OCTET STRING,
432
+ sctpAssocLocalPort InetPortNumber,
433
+ sctpAssocRemPort InetPortNumber,
434
+ sctpAssocRemPrimAddrType InetAddressType,
435
+ sctpAssocRemPrimAddr InetAddress,
436
+ sctpAssocHeartBeatInterval Unsigned32,
437
+ sctpAssocState INTEGER,
438
+ sctpAssocInStreams Unsigned32,
439
+ sctpAssocOutStreams Unsigned32,
440
+ sctpAssocMaxRetr Unsigned32,
441
+ sctpAssocPrimProcess Unsigned32,
442
+ sctpAssocT1expireds Counter32, -- Statistic
443
+ sctpAssocT2expireds Counter32, -- Statistic
444
+ sctpAssocRtxChunks Counter32, -- Statistic
445
+ sctpAssocStartTime TimeStamp,
446
+ sctpAssocDiscontinuityTime TimeStamp
447
+ }
448
+
449
+ sctpAssocId OBJECT-TYPE
450
+ SYNTAX Unsigned32 (1..4294967295)
451
+ MAX-ACCESS not-accessible
452
+ STATUS current
453
+ DESCRIPTION
454
+ "Association Identification. Value identifying the
455
+ association. "
456
+ ::= { sctpAssocEntry 1 }
457
+
458
+ sctpAssocRemHostName OBJECT-TYPE
459
+ SYNTAX OCTET STRING (SIZE(0..255))
460
+ MAX-ACCESS read-only
461
+ STATUS current
462
+ DESCRIPTION
463
+ "The peer's DNS name. This object needs to have the same
464
+ format as the encoding in the DNS protocol. This implies that
465
+ the domain name can be up to 255 octets long, each octet being
466
+ 0<=x<=255 as value with US-ASCII A-Z having a case insensitive
467
+ matching.
468
+
469
+ If no DNS domain name was received from the peer at init time
470
+ (embedded in the INIT or INIT-ACK chunk), this object is
471
+ meaningless. In such cases the object MUST contain a zero-
472
+ length string value. Otherwise, it contains the remote host
473
+ name received at init time."
474
+ ::= { sctpAssocEntry 2 }
475
+
476
+ sctpAssocLocalPort OBJECT-TYPE
477
+ SYNTAX InetPortNumber (1..65535)
478
+ MAX-ACCESS read-only
479
+ STATUS current
480
+ DESCRIPTION
481
+ "The local SCTP port number used for this association."
482
+ ::= { sctpAssocEntry 3 }
483
+
484
+ sctpAssocRemPort OBJECT-TYPE
485
+ SYNTAX InetPortNumber (1..65535)
486
+ MAX-ACCESS read-only
487
+ STATUS current
488
+ DESCRIPTION
489
+ "The remote SCTP port number used for this association."
490
+ ::= { sctpAssocEntry 4 }
491
+
492
+ sctpAssocRemPrimAddrType OBJECT-TYPE
493
+ SYNTAX InetAddressType
494
+ MAX-ACCESS read-only
495
+ STATUS current
496
+ DESCRIPTION
497
+ "The internet type of primary remote IP address. "
498
+ ::= { sctpAssocEntry 5 }
499
+
500
+ sctpAssocRemPrimAddr OBJECT-TYPE
501
+ SYNTAX InetAddress
502
+ MAX-ACCESS read-only
503
+ STATUS current
504
+ DESCRIPTION
505
+ "The primary remote IP address. The type of this address is
506
+ determined by the value of sctpAssocRemPrimAddrType.
507
+
508
+ The client side will know this value after INIT_ACK message
509
+ reception, the server side will know this value when sending
510
+ INIT_ACK message. However, values will be filled in at
511
+ established(4) state."
512
+ ::= { sctpAssocEntry 6 }
513
+
514
+ sctpAssocHeartBeatInterval OBJECT-TYPE
515
+ SYNTAX Unsigned32
516
+ UNITS "milliseconds"
517
+ MAX-ACCESS read-only
518
+ STATUS current
519
+ DESCRIPTION
520
+ "The current heartbeat interval..
521
+
522
+ Zero value means no HeartBeat, even when the concerned
523
+ sctpAssocRemAddrHBFlag object is true."
524
+ DEFVAL {30000} -- milliseconds
525
+ ::= { sctpAssocEntry 7 }
526
+
527
+ sctpAssocState OBJECT-TYPE
528
+ SYNTAX INTEGER {
529
+ closed(1),
530
+ cookieWait(2),
531
+ cookieEchoed(3),
532
+ established(4),
533
+ shutdownPending(5),
534
+ shutdownSent(6),
535
+ shutdownReceived(7),
536
+ shutdownAckSent(8),
537
+ deleteTCB(9)
538
+ }
539
+ MAX-ACCESS read-write
540
+ STATUS current
541
+ DESCRIPTION
542
+ "The state of this SCTP association.
543
+
544
+ As in TCP, deleteTCB(9) is the only value that may be set by a
545
+ management station. If any other value is received, then the
546
+ agent must return a wrongValue error.
547
+
548
+ If a management station sets this object to the value
549
+ deleteTCB(9), then this has the effect of deleting the TCB (as
550
+ defined in SCTP) of the corresponding association on the
551
+ managed node, resulting in immediate termination of the
552
+ association.
553
+
554
+ As an implementation-specific option, an ABORT chunk may be
555
+ sent from the managed node to the other SCTP endpoint as a
556
+ result of setting the deleteTCB(9) value. The ABORT chunk
557
+ implies an ungraceful association shutdown."
558
+ REFERENCE
559
+ "Section 4 in RFC2960 covers the SCTP Association state
560
+ diagram."
561
+ ::= { sctpAssocEntry 8 }
562
+
563
+ sctpAssocInStreams OBJECT-TYPE
564
+ SYNTAX Unsigned32 (1..65535)
565
+ MAX-ACCESS read-only
566
+ STATUS current
567
+ DESCRIPTION
568
+ "Inbound Streams according to the negotiation at association
569
+ start up."
570
+ REFERENCE
571
+ "Section 1.3 in RFC2960 includes a definition of stream.
572
+ Section 5.1.1 in RFC2960 covers the streams negotiation
573
+ process."
574
+ ::= { sctpAssocEntry 9 }
575
+
576
+ sctpAssocOutStreams OBJECT-TYPE
577
+ SYNTAX Unsigned32 (1..65535)
578
+ MAX-ACCESS read-only
579
+ STATUS current
580
+ DESCRIPTION
581
+ "Outbound Streams according to the negotiation at association
582
+ start up. "
583
+ REFERENCE
584
+ "Section 1.3 in RFC2960 includes a definition of stream.
585
+ Section 5.1.1 in RFC2960 covers the streams negotiation
586
+ process."
587
+ ::= { sctpAssocEntry 10 }
588
+
589
+ sctpAssocMaxRetr OBJECT-TYPE
590
+ SYNTAX Unsigned32
591
+ MAX-ACCESS read-only
592
+ STATUS current
593
+ DESCRIPTION
594
+ "The maximum number of data retransmissions in the association
595
+ context. This value is specific for each association and the
596
+ upper layer can change it by calling the appropriate
597
+ primitives. This value has to be smaller than the addition of
598
+ all the maximum number for all the paths
599
+ (sctpAssocRemAddrMaxPathRtx).
600
+
601
+ A value of zero value means no retransmissions."
602
+ DEFVAL {10} -- number of attempts
603
+ ::= { sctpAssocEntry 11 }
604
+
605
+ sctpAssocPrimProcess OBJECT-TYPE
606
+ SYNTAX Unsigned32
607
+ MAX-ACCESS read-only
608
+ STATUS current
609
+ DESCRIPTION
610
+ "This object identifies the system level process which holds
611
+ primary responsibility for the SCTP association.
612
+ Wherever possible, this should be the system's native unique
613
+ identification number. The special value 0 can be used to
614
+ indicate that no primary process is known.
615
+
616
+ Note that the value of this object can be used as a pointer
617
+ into the swRunTable of the HOST-RESOURCES-MIB(if the value is
618
+ smaller than 2147483647) or into the sysApplElmtRunTable of
619
+ the SYSAPPL-MIB."
620
+ ::= { sctpAssocEntry 12 }
621
+
622
+ -- Association Statistics
623
+
624
+ sctpAssocT1expireds OBJECT-TYPE
625
+ SYNTAX Counter32
626
+ MAX-ACCESS read-only
627
+ STATUS current
628
+ DESCRIPTION
629
+ "The T1 timer determines how long to wait for an
630
+ acknowledgement after sending an INIT or COOKIE-ECHO chunk.
631
+ This object reflects the number of times the T1 timer expires
632
+ without having received the acknowledgement.
633
+
634
+ Discontinuities in the value of this counter can occur at re-
635
+ initialization of the management system, and at other times as
636
+ indicated by the value of sctpAssocDiscontinuityTime."
637
+ REFERENCE
638
+ "Section 5 in RFC2960."
639
+ ::= { sctpAssocEntry 13 }
640
+
641
+ sctpAssocT2expireds OBJECT-TYPE
642
+ SYNTAX Counter32
643
+ MAX-ACCESS read-only
644
+ STATUS current
645
+ DESCRIPTION
646
+ "The T2 timer determines how long to wait for an
647
+ acknowledgement after sending a SHUTDOWN or SHUTDOWN-ACK
648
+ chunk. This object reflects the number of times that T2- timer
649
+ expired.
650
+
651
+ Discontinuities in the value of this counter can occur at re-
652
+ initialization of the management system, and at other times as
653
+ indicated by the value of sctpAssocDiscontinuityTime."
654
+ REFERENCE
655
+ "Section 9.2 in RFC2960."
656
+ ::= { sctpAssocEntry 14 }
657
+
658
+ sctpAssocRtxChunks OBJECT-TYPE
659
+ SYNTAX Counter32
660
+ MAX-ACCESS read-only
661
+ STATUS current
662
+ DESCRIPTION
663
+ "When T3-rtx expires, the DATA chunks that triggered the T3
664
+ timer will be re-sent according with the retransmissions
665
+ rules. Every DATA chunk that was included in the SCTP packet
666
+ that triggered the T3-rtx timer must be added to the value of
667
+ this counter.
668
+
669
+ Discontinuities in the value of this counter can occur at re-
670
+ initialization of the management system, and at other times as
671
+ indicated by the value of sctpAssocDiscontinuityTime."
672
+ REFERENCE
673
+ "Section 6 in RFC2960 covers the retransmission process and
674
+ rules."
675
+ ::= { sctpAssocEntry 15 }
676
+
677
+ sctpAssocStartTime OBJECT-TYPE
678
+ SYNTAX TimeStamp
679
+ MAX-ACCESS read-only
680
+ STATUS current
681
+ DESCRIPTION
682
+ "The value of sysUpTime at the time that the association
683
+ represented by this row enters the ESTABLISHED state, i.e.,
684
+ the sctpAssocState object is set to established(4). The
685
+ value of this object will be zero:
686
+ - before the association enters the established(4)
687
+ state, or
688
+
689
+ - if the established(4) state was entered prior to
690
+ the last re-initialization of the local network management
691
+ subsystem."
692
+ ::= { sctpAssocEntry 16 }
693
+
694
+ sctpAssocDiscontinuityTime OBJECT-TYPE
695
+ SYNTAX TimeStamp
696
+ MAX-ACCESS read-only
697
+ STATUS current
698
+ DESCRIPTION
699
+ "The value of sysUpTime on the most recent occasion at which
700
+ any one or more of this SCTP association counters suffered a
701
+ discontinuity. The relevant counters are the specific
702
+ instances associated with this interface of any Counter32 or
703
+ Counter64 object contained in the sctpAssocTable or
704
+ sctpLocalAddrTable or sctpRemAddrTable. If no such
705
+ discontinuities have occurred since the last re-initialization
706
+ of the local management subsystem, then this object contains a
707
+ zero value. "
708
+ REFERENCE
709
+ "The inclusion of this object is recommended by RFC2578."
710
+ ::= { sctpAssocEntry 17 }
711
+
712
+ -- Expanded tables: Including Multi-home feature
713
+
714
+ -- Local Address TABLE
715
+ -- *******************
716
+
717
+ sctpAssocLocalAddrTable OBJECT-TYPE
718
+ SYNTAX SEQUENCE OF SctpAssocLocalAddrEntry
719
+ MAX-ACCESS not-accessible
720
+ STATUS current
721
+ DESCRIPTION
722
+ "Expanded table of sctpAssocTable based on the AssocId index.
723
+ This table shows data related to each local IP address which
724
+ is used by this association."
725
+ ::= { sctpObjects 4 }
726
+
727
+ sctpAssocLocalAddrEntry OBJECT-TYPE
728
+ SYNTAX SctpAssocLocalAddrEntry
729
+ MAX-ACCESS not-accessible
730
+ STATUS current
731
+ DESCRIPTION
732
+ "Local information about the available addresses. There will
733
+ be an entry for every local IP address defined for this
734
+
735
+ association.
736
+ Implementors need to be aware that if the size of
737
+ sctpAssocLocalAddr exceeds 114 octets then OIDs of column
738
+ instances in this table will have more than 128 sub-
739
+ identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
740
+ SNMPv3."
741
+ INDEX { sctpAssocId, -- shared index
742
+ sctpAssocLocalAddrType,
743
+ sctpAssocLocalAddr }
744
+ ::= { sctpAssocLocalAddrTable 1 }
745
+
746
+ SctpAssocLocalAddrEntry ::= SEQUENCE {
747
+ sctpAssocLocalAddrType InetAddressType,
748
+ sctpAssocLocalAddr InetAddress,
749
+ sctpAssocLocalAddrStartTime TimeStamp
750
+ }
751
+
752
+ sctpAssocLocalAddrType OBJECT-TYPE
753
+ SYNTAX InetAddressType
754
+ MAX-ACCESS not-accessible
755
+ STATUS current
756
+ DESCRIPTION
757
+ "Internet type of local IP address used for this association."
758
+ ::= { sctpAssocLocalAddrEntry 1 }
759
+
760
+ sctpAssocLocalAddr OBJECT-TYPE
761
+ SYNTAX InetAddress
762
+ MAX-ACCESS not-accessible
763
+ STATUS current
764
+ DESCRIPTION
765
+ "The value of a local IP address available for this
766
+ association. The type of this address is determined by the
767
+ value of sctpAssocLocalAddrType."
768
+ ::= { sctpAssocLocalAddrEntry 2 }
769
+
770
+ sctpAssocLocalAddrStartTime OBJECT-TYPE
771
+ SYNTAX TimeStamp
772
+ MAX-ACCESS read-only
773
+ STATUS current
774
+ DESCRIPTION
775
+ "The value of sysUpTime at the time that this row was
776
+ created."
777
+ ::= { sctpAssocLocalAddrEntry 3 }
778
+
779
+ -- Remote Addresses TABLE
780
+ -- **********************
781
+
782
+ sctpAssocRemAddrTable OBJECT-TYPE
783
+ SYNTAX SEQUENCE OF SctpAssocRemAddrEntry
784
+ MAX-ACCESS not-accessible
785
+ STATUS current
786
+ DESCRIPTION
787
+ "Expanded table of sctpAssocTable based on the AssocId index.
788
+ This table shows data related to each remote peer IP address
789
+ which is used by this association."
790
+ ::= { sctpObjects 5 }
791
+
792
+ sctpAssocRemAddrEntry OBJECT-TYPE
793
+ SYNTAX SctpAssocRemAddrEntry
794
+ MAX-ACCESS not-accessible
795
+ STATUS current
796
+ DESCRIPTION
797
+ "Information about the most important variables for every
798
+ remote IP address. There will be an entry for every remote IP
799
+ address defined for this association.
800
+
801
+ Implementors need to be aware that if the size of
802
+ sctpAssocRemAddr exceeds 114 octets then OIDs of column
803
+ instances in this table will have more than 128 sub-
804
+ identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
805
+ SNMPv3."
806
+ INDEX { sctpAssocId, -- shared index
807
+ sctpAssocRemAddrType,
808
+ sctpAssocRemAddr }
809
+ ::= { sctpAssocRemAddrTable 1 }
810
+
811
+ SctpAssocRemAddrEntry ::= SEQUENCE {
812
+ sctpAssocRemAddrType InetAddressType,
813
+ sctpAssocRemAddr InetAddress,
814
+ sctpAssocRemAddrActive TruthValue,
815
+ sctpAssocRemAddrHBActive TruthValue,
816
+ sctpAssocRemAddrRTO Unsigned32,
817
+ sctpAssocRemAddrMaxPathRtx Unsigned32,
818
+ sctpAssocRemAddrRtx Counter32, -- Statistic
819
+ sctpAssocRemAddrStartTime TimeStamp
820
+ }
821
+
822
+ sctpAssocRemAddrType OBJECT-TYPE
823
+ SYNTAX InetAddressType
824
+ MAX-ACCESS not-accessible
825
+ STATUS current
826
+ DESCRIPTION
827
+ "Internet type of a remote IP address available for this
828
+ association."
829
+ ::= { sctpAssocRemAddrEntry 1 }
830
+
831
+ sctpAssocRemAddr OBJECT-TYPE
832
+ SYNTAX InetAddress
833
+ MAX-ACCESS not-accessible
834
+ STATUS current
835
+ DESCRIPTION
836
+ "The value of a remote IP address available for this
837
+ association. The type of this address is determined by the
838
+ value of sctpAssocLocalAddrType."
839
+ ::= { sctpAssocRemAddrEntry 2 }
840
+
841
+ sctpAssocRemAddrActive OBJECT-TYPE
842
+ SYNTAX TruthValue
843
+ MAX-ACCESS read-only
844
+ STATUS current
845
+ DESCRIPTION
846
+ "This object gives information about the reachability of this
847
+ specific remote IP address.
848
+
849
+ When the object is set to 'true' (1), the remote IP address is
850
+ understood as Active. Active means that the threshold of no
851
+ answers received from this IP address has not been reached.
852
+
853
+ When the object is set to 'false' (2), the remote IP address
854
+ is understood as Inactive. Inactive means that either no
855
+ heartbeat or any other message was received from this address,
856
+ reaching the threshold defined by the protocol."
857
+ REFERENCE
858
+ "The remote transport states are defined as Active and
859
+ Inactive in the SCTP, RFC2960."
860
+ ::= { sctpAssocRemAddrEntry 3 }
861
+
862
+ sctpAssocRemAddrHBActive OBJECT-TYPE
863
+ SYNTAX TruthValue
864
+ MAX-ACCESS read-only
865
+ STATUS current
866
+ DESCRIPTION
867
+ "This object indicates whether the optional Heartbeat check
868
+ associated to one destination transport address is activated
869
+ or not (value equal to true or false, respectively). "
870
+ ::= { sctpAssocRemAddrEntry 4 }
871
+
872
+ sctpAssocRemAddrRTO OBJECT-TYPE -- T3-rtx- Timer
873
+ SYNTAX Unsigned32
874
+ UNITS "milliseconds"
875
+ MAX-ACCESS read-only
876
+ STATUS current
877
+ DESCRIPTION
878
+ "The current Retransmission Timeout. T3-rtx timer as defined
879
+ in the protocol SCTP."
880
+ REFERENCE
881
+ "Section 6.3 in RFC2960 deals with the Retransmission Timer
882
+ Management."
883
+ ::= { sctpAssocRemAddrEntry 5 }
884
+
885
+ sctpAssocRemAddrMaxPathRtx OBJECT-TYPE
886
+ SYNTAX Unsigned32
887
+ MAX-ACCESS read-only
888
+ STATUS current
889
+ DESCRIPTION
890
+ "Maximum number of DATA chunks retransmissions allowed to a
891
+ remote IP address before it is considered inactive, as defined
892
+ in RFC2960."
893
+ REFERENCE
894
+ "Section 8.2, 8.3 and 14 in RFC2960."
895
+ DEFVAL {5} -- number of attempts
896
+ ::= { sctpAssocRemAddrEntry 6 }
897
+
898
+ -- Remote Address Statistic
899
+
900
+ sctpAssocRemAddrRtx OBJECT-TYPE
901
+ SYNTAX Counter32
902
+ MAX-ACCESS read-only
903
+ STATUS current
904
+ DESCRIPTION
905
+ "Number of DATA chunks retransmissions to this specific IP
906
+ address. When T3-rtx expires, the DATA chunk that triggered
907
+ the T3 timer will be re-sent according to the retransmissions
908
+ rules. Every DATA chunk that is included in a SCTP packet and
909
+ was transmitted to this specific IP address before, will be
910
+ included in this counter.
911
+
912
+ Discontinuities in the value of this counter can occur at re-
913
+ initialization of the management system, and at other times as
914
+ indicated by the value of sctpAssocDiscontinuityTime."
915
+ ::= { sctpAssocRemAddrEntry 7 }
916
+
917
+ sctpAssocRemAddrStartTime OBJECT-TYPE
918
+ SYNTAX TimeStamp
919
+ MAX-ACCESS read-only
920
+ STATUS current
921
+ DESCRIPTION
922
+ "The value of sysUpTime at the time that this row was
923
+ created."
924
+ ::= { sctpAssocRemAddrEntry 8 }
925
+
926
+ -- ASSOCIATION INVERSE TABLE
927
+ -- *************************
928
+
929
+ -- BY LOCAL PORT
930
+
931
+ sctpLookupLocalPortTable OBJECT-TYPE
932
+ SYNTAX SEQUENCE OF SctpLookupLocalPortEntry
933
+ MAX-ACCESS not-accessible
934
+ STATUS current
935
+ DESCRIPTION
936
+ "With the use of this table, a list of associations which are
937
+
938
+ using the specified local port can be retrieved."
939
+ ::= { sctpObjects 6 }
940
+
941
+ sctpLookupLocalPortEntry OBJECT-TYPE
942
+ SYNTAX SctpLookupLocalPortEntry
943
+ MAX-ACCESS not-accessible
944
+ STATUS current
945
+ DESCRIPTION
946
+ "This table is indexed by local port and association ID.
947
+ Specifying a local port, we would get a list of the
948
+ associations whose local port is the one specified."
949
+ INDEX { sctpAssocLocalPort,
950
+ sctpAssocId }
951
+ ::= { sctpLookupLocalPortTable 1 }
952
+
953
+ SctpLookupLocalPortEntry::= SEQUENCE {
954
+ sctpLookupLocalPortStartTime TimeStamp
955
+ }
956
+
957
+ sctpLookupLocalPortStartTime OBJECT-TYPE
958
+ SYNTAX TimeStamp
959
+ MAX-ACCESS read-only
960
+ STATUS current
961
+ DESCRIPTION
962
+ "The value of sysUpTime at the time that this row was created.
963
+
964
+ As the table will be created after the sctpAssocTable
965
+ creation, this value could be equal to the sctpAssocStartTime
966
+ object from the main table."
967
+ ::= { sctpLookupLocalPortEntry 1 }
968
+
969
+ -- BY REMOTE PORT
970
+
971
+ sctpLookupRemPortTable OBJECT-TYPE
972
+ SYNTAX SEQUENCE OF SctpLookupRemPortEntry
973
+ MAX-ACCESS not-accessible
974
+ STATUS current
975
+ DESCRIPTION
976
+ "With the use of this table, a list of associations which are
977
+ using the specified remote port can be got"
978
+ ::= { sctpObjects 7 }
979
+
980
+ sctpLookupRemPortEntry OBJECT-TYPE
981
+ SYNTAX SctpLookupRemPortEntry
982
+ MAX-ACCESS not-accessible
983
+ STATUS current
984
+ DESCRIPTION
985
+ "This table is indexed by remote port and association ID.
986
+ Specifying a remote port we would get a list of the
987
+ associations whose local port is the one specified "
988
+ INDEX { sctpAssocRemPort,
989
+ sctpAssocId }
990
+ ::= { sctpLookupRemPortTable 1 }
991
+
992
+ SctpLookupRemPortEntry::= SEQUENCE {
993
+ sctpLookupRemPortStartTime TimeStamp
994
+ }
995
+
996
+ sctpLookupRemPortStartTime OBJECT-TYPE
997
+ SYNTAX TimeStamp
998
+ MAX-ACCESS read-only
999
+ STATUS current
1000
+ DESCRIPTION
1001
+ "The value of sysUpTime at the time that this row was created.
1002
+
1003
+ As the table will be created after the sctpAssocTable
1004
+ creation, this value could be equal to the sctpAssocStartTime
1005
+ object from the main table."
1006
+ ::= { sctpLookupRemPortEntry 1 }
1007
+
1008
+ -- BY REMOTE HOST NAME
1009
+
1010
+ sctpLookupRemHostNameTable OBJECT-TYPE
1011
+ SYNTAX SEQUENCE OF SctpLookupRemHostNameEntry
1012
+ MAX-ACCESS not-accessible
1013
+ STATUS current
1014
+ DESCRIPTION
1015
+ "With the use of this table, a list of associations with that
1016
+ particular host can be retrieved."
1017
+ ::= { sctpObjects 8 }
1018
+
1019
+ sctpLookupRemHostNameEntry OBJECT-TYPE
1020
+ SYNTAX SctpLookupRemHostNameEntry
1021
+ MAX-ACCESS not-accessible
1022
+ STATUS current
1023
+ DESCRIPTION
1024
+ "This table is indexed by remote host name and association ID.
1025
+ Specifying a host name we would get a list of the associations
1026
+ specifying that host name as the remote one.
1027
+
1028
+ Implementors need to be aware that if the size of
1029
+ sctpAssocRemHostName exceeds 115 octets then OIDs of column
1030
+ instances in this table will have more than 128 sub-
1031
+ identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
1032
+ SNMPv3."
1033
+ INDEX { sctpAssocRemHostName,
1034
+ sctpAssocId }
1035
+ ::= { sctpLookupRemHostNameTable 1 }
1036
+
1037
+ SctpLookupRemHostNameEntry::= SEQUENCE {
1038
+ sctpLookupRemHostNameStartTime TimeStamp
1039
+ }
1040
+
1041
+ sctpLookupRemHostNameStartTime OBJECT-TYPE
1042
+ SYNTAX TimeStamp
1043
+ MAX-ACCESS read-only
1044
+ STATUS current
1045
+ DESCRIPTION
1046
+ "The value of sysUpTime at the time that this row was created.
1047
+
1048
+ As the table will be created after the sctpAssocTable
1049
+ creation, this value could be equal to the sctpAssocStartTime
1050
+ object from the main table."
1051
+ ::= { sctpLookupRemHostNameEntry 1 }
1052
+
1053
+ -- BY REMOTE PRIMARY IP ADDRESS
1054
+
1055
+ sctpLookupRemPrimIPAddrTable OBJECT-TYPE
1056
+ SYNTAX SEQUENCE OF SctpLookupRemPrimIPAddrEntry
1057
+ MAX-ACCESS not-accessible
1058
+ STATUS current
1059
+ DESCRIPTION
1060
+ "With the use of this table, a list of associations that have
1061
+ the specified IP address as primary within the remote set of
1062
+ active addresses can be retrieved."
1063
+ ::= { sctpObjects 9 }
1064
+
1065
+ sctpLookupRemPrimIPAddrEntry OBJECT-TYPE
1066
+ SYNTAX SctpLookupRemPrimIPAddrEntry
1067
+ MAX-ACCESS not-accessible
1068
+ STATUS current
1069
+ DESCRIPTION
1070
+ "This table is indexed by primary address and association ID.
1071
+ Specifying a primary address, we would get a list of the
1072
+ associations that have the specified remote IP address marked
1073
+ as primary.
1074
+ Implementors need to be aware that if the size of
1075
+ sctpAssocRemPrimAddr exceeds 114 octets then OIDs of column
1076
+ instances in this table will have more than 128 sub-
1077
+ identifiers and cannot be accessed using SNMPv1, SNMPv2c, or
1078
+ SNMPv3."
1079
+ INDEX { sctpAssocRemPrimAddrType,
1080
+ sctpAssocRemPrimAddr,
1081
+ sctpAssocId }
1082
+ ::= { sctpLookupRemPrimIPAddrTable 1 }
1083
+
1084
+ SctpLookupRemPrimIPAddrEntry::= SEQUENCE {
1085
+ sctpLookupRemPrimIPAddrStartTime TimeStamp
1086
+ }
1087
+
1088
+ sctpLookupRemPrimIPAddrStartTime OBJECT-TYPE
1089
+ SYNTAX TimeStamp
1090
+ MAX-ACCESS read-only
1091
+ STATUS current
1092
+ DESCRIPTION
1093
+ "The value of SysUpTime at the time that this row was created.
1094
+
1095
+ As the table will be created after the sctpAssocTable
1096
+ creation, this value could be equal to the sctpAssocStartTime
1097
+ object from the main table."
1098
+ ::= { sctpLookupRemPrimIPAddrEntry 1 }
1099
+
1100
+ -- BY REMOTE IP ADDRESS
1101
+
1102
+ sctpLookupRemIPAddrTable OBJECT-TYPE
1103
+ SYNTAX SEQUENCE OF SctpLookupRemIPAddrEntry
1104
+ MAX-ACCESS not-accessible
1105
+ STATUS current
1106
+ DESCRIPTION
1107
+ "With the use of this table, a list of associations that have
1108
+ the specified IP address as one of the remote ones can be
1109
+ retrieved. "
1110
+ ::= { sctpObjects 10 }
1111
+
1112
+ sctpLookupRemIPAddrEntry OBJECT-TYPE
1113
+ SYNTAX SctpLookupRemIPAddrEntry
1114
+ MAX-ACCESS not-accessible
1115
+ STATUS current
1116
+ DESCRIPTION
1117
+ "This table is indexed by a remote IP address and association
1118
+ ID. Specifying an IP address we would get a list of the
1119
+ associations that have the specified IP address included
1120
+ within the set of remote IP addresses."
1121
+ INDEX { sctpAssocRemAddrType,
1122
+ sctpAssocRemAddr,
1123
+ sctpAssocId }
1124
+ ::= { sctpLookupRemIPAddrTable 1 }
1125
+
1126
+ SctpLookupRemIPAddrEntry::= SEQUENCE {
1127
+
1128
+ sctpLookupRemIPAddrStartTime TimeStamp
1129
+ }
1130
+
1131
+ sctpLookupRemIPAddrStartTime OBJECT-TYPE
1132
+ SYNTAX TimeStamp
1133
+ MAX-ACCESS read-only
1134
+ STATUS current
1135
+ DESCRIPTION
1136
+ "The value of SysUpTime at the time that this row was created.
1137
+
1138
+ As the table will be created after the sctpAssocTable
1139
+ creation, this value could be equal to the sctpAssocStartTime
1140
+ object from the main table."
1141
+ ::= { sctpLookupRemIPAddrEntry 1 }
1142
+
1143
+ -- 4.1 Conformance Information
1144
+
1145
+ sctpMibConformance OBJECT IDENTIFIER ::= { sctpMIB 2 }
1146
+ sctpMibCompliances OBJECT IDENTIFIER ::= { sctpMibConformance 1 }
1147
+ sctpMibGroups OBJECT IDENTIFIER ::= { sctpMibConformance 2 }
1148
+
1149
+ -- 4.1.1 Units of conformance
1150
+
1151
+ --
1152
+ -- MODULE GROUPS
1153
+ --
1154
+
1155
+ sctpLayerParamsGroup OBJECT-GROUP
1156
+ OBJECTS { sctpRtoAlgorithm,
1157
+ sctpRtoMin,
1158
+ sctpRtoMax,
1159
+ sctpRtoInitial,
1160
+ sctpMaxAssocs,
1161
+ sctpValCookieLife,
1162
+ sctpMaxInitRetr
1163
+ }
1164
+ STATUS current
1165
+ DESCRIPTION
1166
+ "Common parameters for the SCTP layer, i.e., for all the
1167
+ associations. They can usually be referred to as configuration
1168
+ parameters."
1169
+ ::= { sctpMibGroups 1 }
1170
+
1171
+ sctpStatsGroup OBJECT-GROUP
1172
+ OBJECTS { sctpCurrEstab,
1173
+ sctpActiveEstabs,
1174
+ sctpPassiveEstabs,
1175
+ sctpAborteds,
1176
+ sctpShutdowns,
1177
+ sctpOutOfBlues,
1178
+ sctpChecksumErrors,
1179
+ sctpOutCtrlChunks,
1180
+ sctpOutOrderChunks,
1181
+ sctpOutUnorderChunks,
1182
+ sctpInCtrlChunks,
1183
+ sctpInOrderChunks,
1184
+ sctpInUnorderChunks,
1185
+ sctpFragUsrMsgs,
1186
+ sctpReasmUsrMsgs,
1187
+ sctpOutSCTPPacks,
1188
+ sctpInSCTPPacks,
1189
+ sctpDiscontinuityTime,
1190
+ sctpAssocT1expireds,
1191
+ sctpAssocT2expireds,
1192
+ sctpAssocRtxChunks,
1193
+ sctpAssocRemAddrRtx
1194
+ }
1195
+ STATUS current
1196
+ DESCRIPTION
1197
+ "Statistics group. It includes the objects to collect state
1198
+ changes in the SCTP protocol local layer and flow control
1199
+ statistics."
1200
+ ::= { sctpMibGroups 2 }
1201
+
1202
+ sctpPerAssocParamsGroup OBJECT-GROUP
1203
+ OBJECTS { sctpAssocRemHostName,
1204
+ sctpAssocLocalPort,
1205
+ sctpAssocRemPort,
1206
+ sctpAssocRemPrimAddrType,
1207
+ sctpAssocRemPrimAddr,
1208
+ sctpAssocHeartBeatInterval,
1209
+ sctpAssocState,
1210
+ sctpAssocInStreams,
1211
+ sctpAssocOutStreams,
1212
+ sctpAssocMaxRetr,
1213
+ sctpAssocPrimProcess,
1214
+ sctpAssocStartTime,
1215
+ sctpAssocDiscontinuityTime,
1216
+ sctpAssocLocalAddrStartTime,
1217
+ sctpAssocRemAddrActive,
1218
+ sctpAssocRemAddrHBActive,
1219
+ sctpAssocRemAddrRTO,
1220
+ sctpAssocRemAddrMaxPathRtx,
1221
+ sctpAssocRemAddrStartTime
1222
+ }
1223
+ STATUS current
1224
+ DESCRIPTION
1225
+ "The SCTP group of objects to manage per-association
1226
+ parameters. These variables include all the SCTP basic
1227
+ features."
1228
+ ::= { sctpMibGroups 3 }
1229
+
1230
+ sctpPerAssocStatsGroup OBJECT-GROUP
1231
+ OBJECTS
1232
+ { sctpAssocT1expireds,
1233
+ sctpAssocT2expireds,
1234
+ sctpAssocRtxChunks,
1235
+ sctpAssocRemAddrRtx
1236
+ }
1237
+ STATUS current
1238
+ DESCRIPTION
1239
+ "Per Association Statistics group. It includes the objects to
1240
+ collect flow control statistics per association."
1241
+ ::= { sctpMibGroups 4 }
1242
+
1243
+ sctpInverseGroup OBJECT-GROUP
1244
+ OBJECTS { sctpLookupLocalPortStartTime,
1245
+ sctpLookupRemPortStartTime,
1246
+ sctpLookupRemHostNameStartTime,
1247
+ sctpLookupRemPrimIPAddrStartTime,
1248
+ sctpLookupRemIPAddrStartTime
1249
+ }
1250
+ STATUS current
1251
+ DESCRIPTION
1252
+ "Objects used in the inverse lookup tables."
1253
+ ::= { sctpMibGroups 5 }
1254
+
1255
+ -- 4.1.2 Compliance Statements
1256
+
1257
+ --
1258
+ -- MODULE COMPLIANCES
1259
+ --
1260
+
1261
+ sctpMibCompliance MODULE-COMPLIANCE
1262
+ STATUS current
1263
+ DESCRIPTION
1264
+ "The compliance statement for SNMP entities which implement
1265
+ this SCTP MIB Module.
1266
+
1267
+ There are a number of INDEX objects that cannot be represented
1268
+ in the form of OBJECT clauses in SMIv2, but for which we have
1269
+ the following compliance requirements, expressed in OBJECT
1270
+ clause form in this description clause:
1271
+
1272
+ -- OBJECT sctpAssocLocalAddrType
1273
+ -- SYNTAX InetAddressType {ipv4(1), ipv6(2)}
1274
+ -- DESCRIPTION
1275
+ -- It is only required to have IPv4 and IPv6 addresses without
1276
+ -- zone indices.
1277
+ -- The address with zone indices is required if an
1278
+ -- implementation can connect multiple zones.
1279
+ --
1280
+ -- OBJECT sctpAssocLocalAddr
1281
+ -- SYNTAX InetAddress (SIZE(4|16))
1282
+ -- DESCRIPTION
1283
+ -- An implementation is only required to support globally
1284
+ -- unique IPv4 and IPv6 addresses.
1285
+ --
1286
+ -- OBJECT sctpAssocRemAddrType
1287
+ -- SYNTAX InetAddressType {ipv4(1), ipv6(2)}
1288
+ -- DESCRIPTION
1289
+ -- It is only required to have IPv4 and IPv6 addresses without
1290
+ -- zone indices.
1291
+ -- The address with zone indices is required if an
1292
+ -- implementation can connect multiple zones.
1293
+ --
1294
+ -- OBJECT sctpAssocRemAddr
1295
+ -- SYNTAX InetAddress (SIZE(4|16))
1296
+ -- DESCRIPTION
1297
+ -- An implementation is only required to support globally
1298
+ -- unique IPv4 and IPv6 addresses.
1299
+ --
1300
+ " -- closes DESCRIPTION clause of MODULE-COMPLIANCE
1301
+
1302
+ MODULE -- this module
1303
+
1304
+ MANDATORY-GROUPS { sctpLayerParamsGroup,
1305
+ sctpPerAssocParamsGroup,
1306
+ sctpStatsGroup,
1307
+ sctpPerAssocStatsGroup
1308
+ }
1309
+
1310
+ OBJECT sctpAssocRemPrimAddrType
1311
+ SYNTAX InetAddressType { ipv4(1),
1312
+ ipv6(2)
1313
+ }
1314
+ DESCRIPTION
1315
+ "It is only required to have IPv4 and IPv6 addresses
1316
+ without zone indices.
1317
+
1318
+ The address with zone indices is required if an
1319
+ implementation can connect multiple zones."
1320
+
1321
+ OBJECT sctpAssocRemPrimAddr
1322
+ SYNTAX InetAddress (SIZE(4|16))
1323
+ DESCRIPTION
1324
+ "An implementation is only required to support globally
1325
+ unique IPv4 and globally unique IPv6 addresses."
1326
+
1327
+ OBJECT sctpAssocState
1328
+ WRITE-SYNTAX INTEGER { deleteTCB(9) }
1329
+ MIN-ACCESS read-only
1330
+ DESCRIPTION
1331
+ "Only the deleteTCB(9) value MAY be set by a management
1332
+ station at most. A read-only option is also considered to
1333
+ be compliant with this MIB module description."
1334
+
1335
+ GROUP sctpInverseGroup
1336
+ DESCRIPTION
1337
+ "Objects used in inverse lookup tables. This should be
1338
+ implemented, at the discretion of the implementers, for
1339
+ easier lookups in the association tables"
1340
+ ::= { sctpMibCompliances 1 }
1341
+
1342
+ END