telemetry-snmp 0.1.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.github/workflows/rspec.yml +44 -0
- data/.github/workflows/rubocop.yml +28 -0
- data/.github/workflows/sourcehawk-scan.yml +20 -0
- data/.gitignore +14 -0
- data/.rspec +4 -0
- data/.rubocop.yml +26 -0
- data/CHANGELOG.md +4 -0
- data/CODE_OF_CONDUCT.md +75 -0
- data/CONTRIBUTING.md +54 -0
- data/Gemfile +10 -0
- data/INDIVIDUAL_CONTRIBUTOR_LICENSE.md +30 -0
- data/LICENSE +201 -0
- data/NOTICE.txt +9 -0
- data/README.md +54 -0
- data/attribution.txt +1 -0
- data/config.ru +15 -0
- data/exe/snmp_collector +55 -0
- data/lib/telemetry/snmp.rb +23 -0
- data/lib/telemetry/snmp/api.rb +55 -0
- data/lib/telemetry/snmp/auth.rb +54 -0
- data/lib/telemetry/snmp/auth/defaults.rb +41 -0
- data/lib/telemetry/snmp/client.rb +104 -0
- data/lib/telemetry/snmp/controllers/device_creds.rb +105 -0
- data/lib/telemetry/snmp/controllers/devices.rb +94 -0
- data/lib/telemetry/snmp/controllers/oid_groups.rb +71 -0
- data/lib/telemetry/snmp/controllers/oids.rb +80 -0
- data/lib/telemetry/snmp/controllers/users.rb +81 -0
- data/lib/telemetry/snmp/controllers/walks.rb +89 -0
- data/lib/telemetry/snmp/data.rb +69 -0
- data/lib/telemetry/snmp/data/default_opts.rb +73 -0
- data/lib/telemetry/snmp/data/migrations/001_device_creds.rb +19 -0
- data/lib/telemetry/snmp/data/migrations/002_create_devices_table.rb +31 -0
- data/lib/telemetry/snmp/data/migrations/003_create_oids_tables.rb +16 -0
- data/lib/telemetry/snmp/data/migrations/004_create_oid_groups.rb +15 -0
- data/lib/telemetry/snmp/data/migrations/005_create_oids_oid_groups.rb +17 -0
- data/lib/telemetry/snmp/data/migrations/006_device_to_oid_group.rb +15 -0
- data/lib/telemetry/snmp/data/migrations/007_create_users.rb +20 -0
- data/lib/telemetry/snmp/data/migrations/008_create_walks_table.rb +14 -0
- data/lib/telemetry/snmp/data/migrations/009_create_tag_name_column.rb +7 -0
- data/lib/telemetry/snmp/data/migrations/010_create_user_audit_table.rb +18 -0
- data/lib/telemetry/snmp/data/models/device.rb +11 -0
- data/lib/telemetry/snmp/data/models/device_cred.rb +11 -0
- data/lib/telemetry/snmp/data/models/oid.rb +10 -0
- data/lib/telemetry/snmp/data/models/oid_group.rb +10 -0
- data/lib/telemetry/snmp/data/models/oid_oid_groups.rb +10 -0
- data/lib/telemetry/snmp/data/models/oid_walk.rb +10 -0
- data/lib/telemetry/snmp/data/models/user.rb +10 -0
- data/lib/telemetry/snmp/data/models/user_audit_log.rb +19 -0
- data/lib/telemetry/snmp/mibs/AGENTX-MIB.txt +527 -0
- data/lib/telemetry/snmp/mibs/AIRPORT-BASESTATION-3-MIB.txt +461 -0
- data/lib/telemetry/snmp/mibs/BRIDGE-MIB.txt +1472 -0
- data/lib/telemetry/snmp/mibs/DISMAN-EVENT-MIB.txt +1882 -0
- data/lib/telemetry/snmp/mibs/DISMAN-SCHEDULE-MIB.txt +699 -0
- data/lib/telemetry/snmp/mibs/DISMAN-SCRIPT-MIB.txt +1764 -0
- data/lib/telemetry/snmp/mibs/EtherLike-MIB.txt +1862 -0
- data/lib/telemetry/snmp/mibs/HCNUM-TC.txt +118 -0
- data/lib/telemetry/snmp/mibs/HOST-RESOURCES-MIB.txt +1540 -0
- data/lib/telemetry/snmp/mibs/HOST-RESOURCES-TYPES.txt +389 -0
- data/lib/telemetry/snmp/mibs/IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt +123 -0
- data/lib/telemetry/snmp/mibs/IANA-LANGUAGE-MIB.txt +123 -0
- data/lib/telemetry/snmp/mibs/IANA-RTPROTO-MIB.txt +91 -0
- data/lib/telemetry/snmp/mibs/IANAifType-MIB.txt +619 -0
- data/lib/telemetry/snmp/mibs/IF-INVERTED-STACK-MIB.txt +149 -0
- data/lib/telemetry/snmp/mibs/IF-MIB.txt +1814 -0
- data/lib/telemetry/snmp/mibs/INET-ADDRESS-MIB.txt +402 -0
- data/lib/telemetry/snmp/mibs/IP-FORWARD-MIB.txt +1277 -0
- data/lib/telemetry/snmp/mibs/IP-MIB.txt +4993 -0
- data/lib/telemetry/snmp/mibs/IPV6-FLOW-LABEL-MIB.txt +58 -0
- data/lib/telemetry/snmp/mibs/IPV6-ICMP-MIB.txt +529 -0
- data/lib/telemetry/snmp/mibs/IPV6-MIB.txt +1443 -0
- data/lib/telemetry/snmp/mibs/IPV6-TC.txt +67 -0
- data/lib/telemetry/snmp/mibs/IPV6-TCP-MIB.txt +211 -0
- data/lib/telemetry/snmp/mibs/IPV6-UDP-MIB.txt +141 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-AGENT-MIB.txt +554 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt +285 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-EXTEND-MIB.txt +325 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-MIB.txt +67 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-PASS-MIB.txt +124 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-TC.txt +128 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-VACM-MIB.txt +154 -0
- data/lib/telemetry/snmp/mibs/NOTIFICATION-LOG-MIB.txt +753 -0
- data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.my +2293 -0
- data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.my +293 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.my +84 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.my +68 -0
- data/lib/telemetry/snmp/mibs/PAN-LC-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-LC-MIB.my +204 -0
- data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.my +305 -0
- data/lib/telemetry/snmp/mibs/PAN-TRAPS.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-TRAPS.my +7809 -0
- data/lib/telemetry/snmp/mibs/RFC-1215.txt +38 -0
- data/lib/telemetry/snmp/mibs/RFC1155-SMI.txt +119 -0
- data/lib/telemetry/snmp/mibs/RFC1213-MIB.txt +2613 -0
- data/lib/telemetry/snmp/mibs/RMON-MIB.txt +3980 -0
- data/lib/telemetry/snmp/mibs/SCTP-MIB.txt +1342 -0
- data/lib/telemetry/snmp/mibs/SMUX-MIB.txt +160 -0
- data/lib/telemetry/snmp/mibs/SNMP-COMMUNITY-MIB.txt +429 -0
- data/lib/telemetry/snmp/mibs/SNMP-FRAMEWORK-MIB.txt +526 -0
- data/lib/telemetry/snmp/mibs/SNMP-MPD-MIB.txt +145 -0
- data/lib/telemetry/snmp/mibs/SNMP-NOTIFICATION-MIB.txt +589 -0
- data/lib/telemetry/snmp/mibs/SNMP-PROXY-MIB.txt +294 -0
- data/lib/telemetry/snmp/mibs/SNMP-TARGET-MIB.txt +660 -0
- data/lib/telemetry/snmp/mibs/SNMP-USER-BASED-SM-MIB.txt +912 -0
- data/lib/telemetry/snmp/mibs/SNMP-USM-AES-MIB.txt +62 -0
- data/lib/telemetry/snmp/mibs/SNMP-USM-DH-OBJECTS-MIB.txt +532 -0
- data/lib/telemetry/snmp/mibs/SNMP-VIEW-BASED-ACM-MIB.txt +830 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-CONF.txt +322 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-MIB.txt +854 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-SMI.txt +344 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-TC.txt +772 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-TM.txt +176 -0
- data/lib/telemetry/snmp/mibs/TCP-MIB.txt +785 -0
- data/lib/telemetry/snmp/mibs/TRANSPORT-ADDRESS-MIB.txt +421 -0
- data/lib/telemetry/snmp/mibs/TUNNEL-MIB.txt +738 -0
- data/lib/telemetry/snmp/mibs/UCD-DEMO-MIB.txt +74 -0
- data/lib/telemetry/snmp/mibs/UCD-DISKIO-MIB.txt +171 -0
- data/lib/telemetry/snmp/mibs/UCD-DLMOD-MIB.txt +124 -0
- data/lib/telemetry/snmp/mibs/UCD-IPFWACC-MIB.txt +327 -0
- data/lib/telemetry/snmp/mibs/UCD-SNMP-MIB.txt +1712 -0
- data/lib/telemetry/snmp/mibs/UDP-MIB.txt +549 -0
- data/lib/telemetry/snmp/publisher.rb +130 -0
- data/lib/telemetry/snmp/version.rb +7 -0
- data/sourcehawk.yml +4 -0
- data/telemetry-snmp.gemspec +48 -0
- metadata +456 -0
@@ -0,0 +1,549 @@
|
|
1
|
+
UDP-MIB DEFINITIONS ::= BEGIN
|
2
|
+
|
3
|
+
IMPORTS
|
4
|
+
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, Counter64,
|
5
|
+
Unsigned32, IpAddress, mib-2 FROM SNMPv2-SMI
|
6
|
+
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
|
7
|
+
InetAddress, InetAddressType,
|
8
|
+
InetPortNumber FROM INET-ADDRESS-MIB;
|
9
|
+
|
10
|
+
udpMIB MODULE-IDENTITY
|
11
|
+
LAST-UPDATED "200505200000Z" -- May 20, 2005
|
12
|
+
ORGANIZATION
|
13
|
+
"IETF IPv6 Working Group
|
14
|
+
http://www.ietf.org/html.charters/ipv6-charter.html"
|
15
|
+
CONTACT-INFO
|
16
|
+
"Bill Fenner (editor)
|
17
|
+
|
18
|
+
AT&T Labs -- Research
|
19
|
+
75 Willow Rd.
|
20
|
+
Menlo Park, CA 94025
|
21
|
+
|
22
|
+
Phone: +1 650 330-7893
|
23
|
+
Email: <fenner@research.att.com>
|
24
|
+
|
25
|
+
John Flick (editor)
|
26
|
+
|
27
|
+
Hewlett-Packard Company
|
28
|
+
8000 Foothills Blvd. M/S 5557
|
29
|
+
Roseville, CA 95747
|
30
|
+
|
31
|
+
Phone: +1 916 785 4018
|
32
|
+
Email: <john.flick@hp.com>
|
33
|
+
|
34
|
+
Send comments to <ipv6@ietf.org>"
|
35
|
+
DESCRIPTION
|
36
|
+
"The MIB module for managing UDP implementations.
|
37
|
+
Copyright (C) The Internet Society (2005). This
|
38
|
+
version of this MIB module is part of RFC 4113;
|
39
|
+
see the RFC itself for full legal notices."
|
40
|
+
REVISION "200505200000Z" -- May 20, 2005
|
41
|
+
DESCRIPTION
|
42
|
+
"IP version neutral revision, incorporating the
|
43
|
+
following revisions:
|
44
|
+
|
45
|
+
- Added udpHCInDatagrams and udpHCOutDatagrams in order
|
46
|
+
to provide high-capacity counters for fast networks.
|
47
|
+
- Added text to the descriptions of all counter objects
|
48
|
+
to indicate how discontinuities are detected.
|
49
|
+
- Deprecated the IPv4-specific udpTable and replaced it
|
50
|
+
with the version neutral udpEndpointTable. This
|
51
|
+
table includes support for connected UDP endpoints
|
52
|
+
and support for identification of the operating
|
53
|
+
system process associated with a UDP endpoint.
|
54
|
+
- Deprecated the udpGroup and replaced it with object
|
55
|
+
groups representing the current set of objects.
|
56
|
+
- Deprecated udpMIBCompliance and replaced it with
|
57
|
+
udpMIBCompliance2, which includes the compliance
|
58
|
+
information for the new object groups.
|
59
|
+
|
60
|
+
This version published as RFC 4113."
|
61
|
+
REVISION "199411010000Z" -- November 1, 1994
|
62
|
+
DESCRIPTION
|
63
|
+
"Initial SMIv2 version, published as RFC 2013."
|
64
|
+
REVISION "199103310000Z" -- March 31, 1991
|
65
|
+
DESCRIPTION
|
66
|
+
"The initial revision of this MIB module was part of
|
67
|
+
MIB-II, published as RFC 1213."
|
68
|
+
::= { mib-2 50 }
|
69
|
+
|
70
|
+
-- the UDP group
|
71
|
+
|
72
|
+
udp OBJECT IDENTIFIER ::= { mib-2 7 }
|
73
|
+
|
74
|
+
udpInDatagrams OBJECT-TYPE
|
75
|
+
SYNTAX Counter32
|
76
|
+
MAX-ACCESS read-only
|
77
|
+
STATUS current
|
78
|
+
DESCRIPTION
|
79
|
+
"The total number of UDP datagrams delivered to UDP
|
80
|
+
users.
|
81
|
+
|
82
|
+
Discontinuities in the value of this counter can occur
|
83
|
+
at re-initialization of the management system, and at
|
84
|
+
other times as indicated by discontinuities in the
|
85
|
+
value of sysUpTime."
|
86
|
+
::= { udp 1 }
|
87
|
+
|
88
|
+
udpNoPorts OBJECT-TYPE
|
89
|
+
SYNTAX Counter32
|
90
|
+
MAX-ACCESS read-only
|
91
|
+
STATUS current
|
92
|
+
DESCRIPTION
|
93
|
+
"The total number of received UDP datagrams for which
|
94
|
+
there was no application at the destination port.
|
95
|
+
|
96
|
+
Discontinuities in the value of this counter can occur
|
97
|
+
at re-initialization of the management system, and at
|
98
|
+
other times as indicated by discontinuities in the
|
99
|
+
value of sysUpTime."
|
100
|
+
::= { udp 2 }
|
101
|
+
|
102
|
+
udpInErrors OBJECT-TYPE
|
103
|
+
SYNTAX Counter32
|
104
|
+
MAX-ACCESS read-only
|
105
|
+
STATUS current
|
106
|
+
DESCRIPTION
|
107
|
+
"The number of received UDP datagrams that could not be
|
108
|
+
delivered for reasons other than the lack of an
|
109
|
+
application at the destination port.
|
110
|
+
|
111
|
+
Discontinuities in the value of this counter can occur
|
112
|
+
at re-initialization of the management system, and at
|
113
|
+
other times as indicated by discontinuities in the
|
114
|
+
value of sysUpTime."
|
115
|
+
::= { udp 3 }
|
116
|
+
|
117
|
+
udpOutDatagrams OBJECT-TYPE
|
118
|
+
SYNTAX Counter32
|
119
|
+
MAX-ACCESS read-only
|
120
|
+
STATUS current
|
121
|
+
DESCRIPTION
|
122
|
+
"The total number of UDP datagrams sent from this
|
123
|
+
entity.
|
124
|
+
|
125
|
+
Discontinuities in the value of this counter can occur
|
126
|
+
at re-initialization of the management system, and at
|
127
|
+
other times as indicated by discontinuities in the
|
128
|
+
value of sysUpTime."
|
129
|
+
::= { udp 4 }
|
130
|
+
|
131
|
+
udpHCInDatagrams OBJECT-TYPE
|
132
|
+
SYNTAX Counter64
|
133
|
+
MAX-ACCESS read-only
|
134
|
+
STATUS current
|
135
|
+
DESCRIPTION
|
136
|
+
"The total number of UDP datagrams delivered to UDP
|
137
|
+
users, for devices that can receive more than 1
|
138
|
+
million UDP datagrams per second.
|
139
|
+
|
140
|
+
Discontinuities in the value of this counter can occur
|
141
|
+
at re-initialization of the management system, and at
|
142
|
+
other times as indicated by discontinuities in the
|
143
|
+
value of sysUpTime."
|
144
|
+
::= { udp 8 }
|
145
|
+
|
146
|
+
udpHCOutDatagrams OBJECT-TYPE
|
147
|
+
SYNTAX Counter64
|
148
|
+
MAX-ACCESS read-only
|
149
|
+
STATUS current
|
150
|
+
DESCRIPTION
|
151
|
+
"The total number of UDP datagrams sent from this
|
152
|
+
entity, for devices that can transmit more than 1
|
153
|
+
million UDP datagrams per second.
|
154
|
+
|
155
|
+
Discontinuities in the value of this counter can occur
|
156
|
+
at re-initialization of the management system, and at
|
157
|
+
other times as indicated by discontinuities in the
|
158
|
+
value of sysUpTime."
|
159
|
+
::= { udp 9 }
|
160
|
+
|
161
|
+
--
|
162
|
+
-- { udp 6 } was defined as the ipv6UdpTable in RFC2454's
|
163
|
+
-- IPV6-UDP-MIB. This RFC obsoletes RFC 2454, so { udp 6 } is
|
164
|
+
-- obsoleted.
|
165
|
+
--
|
166
|
+
|
167
|
+
-- The UDP "Endpoint" table.
|
168
|
+
|
169
|
+
udpEndpointTable OBJECT-TYPE
|
170
|
+
SYNTAX SEQUENCE OF UdpEndpointEntry
|
171
|
+
MAX-ACCESS not-accessible
|
172
|
+
STATUS current
|
173
|
+
DESCRIPTION
|
174
|
+
"A table containing information about this entity's UDP
|
175
|
+
endpoints on which a local application is currently
|
176
|
+
accepting or sending datagrams.
|
177
|
+
|
178
|
+
The address type in this table represents the address
|
179
|
+
type used for the communication, irrespective of the
|
180
|
+
higher-layer abstraction. For example, an application
|
181
|
+
using IPv6 'sockets' to communicate via IPv4 between
|
182
|
+
::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use
|
183
|
+
InetAddressType ipv4(1).
|
184
|
+
|
185
|
+
Unlike the udpTable in RFC 2013, this table also allows
|
186
|
+
the representation of an application that completely
|
187
|
+
specifies both local and remote addresses and ports. A
|
188
|
+
listening application is represented in three possible
|
189
|
+
ways:
|
190
|
+
|
191
|
+
1) An application that is willing to accept both IPv4
|
192
|
+
and IPv6 datagrams is represented by a
|
193
|
+
udpEndpointLocalAddressType of unknown(0) and a
|
194
|
+
udpEndpointLocalAddress of ''h (a zero-length
|
195
|
+
octet-string).
|
196
|
+
|
197
|
+
2) An application that is willing to accept only IPv4
|
198
|
+
or only IPv6 datagrams is represented by a
|
199
|
+
udpEndpointLocalAddressType of the appropriate
|
200
|
+
address type and a udpEndpointLocalAddress of
|
201
|
+
'0.0.0.0' or '::' respectively.
|
202
|
+
|
203
|
+
3) An application that is listening for datagrams only
|
204
|
+
for a specific IP address but from any remote
|
205
|
+
system is represented by a
|
206
|
+
udpEndpointLocalAddressType of the appropriate
|
207
|
+
address type, with udpEndpointLocalAddress
|
208
|
+
specifying the local address.
|
209
|
+
|
210
|
+
In all cases where the remote is a wildcard, the
|
211
|
+
udpEndpointRemoteAddressType is unknown(0), the
|
212
|
+
udpEndpointRemoteAddress is ''h (a zero-length
|
213
|
+
octet-string), and the udpEndpointRemotePort is 0.
|
214
|
+
|
215
|
+
If the operating system is demultiplexing UDP packets
|
216
|
+
by remote address and port, or if the application has
|
217
|
+
'connected' the socket specifying a default remote
|
218
|
+
address and port, the udpEndpointRemote* values should
|
219
|
+
be used to reflect this."
|
220
|
+
::= { udp 7 }
|
221
|
+
|
222
|
+
udpEndpointEntry OBJECT-TYPE
|
223
|
+
SYNTAX UdpEndpointEntry
|
224
|
+
MAX-ACCESS not-accessible
|
225
|
+
STATUS current
|
226
|
+
DESCRIPTION
|
227
|
+
"Information about a particular current UDP endpoint.
|
228
|
+
|
229
|
+
Implementers need to be aware that if the total number
|
230
|
+
of elements (octets or sub-identifiers) in
|
231
|
+
udpEndpointLocalAddress and udpEndpointRemoteAddress
|
232
|
+
exceeds 111, then OIDs of column instances in this table
|
233
|
+
will have more than 128 sub-identifiers and cannot be
|
234
|
+
accessed using SNMPv1, SNMPv2c, or SNMPv3."
|
235
|
+
INDEX { udpEndpointLocalAddressType,
|
236
|
+
udpEndpointLocalAddress,
|
237
|
+
udpEndpointLocalPort,
|
238
|
+
udpEndpointRemoteAddressType,
|
239
|
+
udpEndpointRemoteAddress,
|
240
|
+
udpEndpointRemotePort,
|
241
|
+
udpEndpointInstance }
|
242
|
+
::= { udpEndpointTable 1 }
|
243
|
+
|
244
|
+
UdpEndpointEntry ::= SEQUENCE {
|
245
|
+
udpEndpointLocalAddressType InetAddressType,
|
246
|
+
udpEndpointLocalAddress InetAddress,
|
247
|
+
udpEndpointLocalPort InetPortNumber,
|
248
|
+
udpEndpointRemoteAddressType InetAddressType,
|
249
|
+
udpEndpointRemoteAddress InetAddress,
|
250
|
+
udpEndpointRemotePort InetPortNumber,
|
251
|
+
udpEndpointInstance Unsigned32,
|
252
|
+
udpEndpointProcess Unsigned32
|
253
|
+
}
|
254
|
+
|
255
|
+
udpEndpointLocalAddressType OBJECT-TYPE
|
256
|
+
SYNTAX InetAddressType
|
257
|
+
MAX-ACCESS not-accessible
|
258
|
+
STATUS current
|
259
|
+
DESCRIPTION
|
260
|
+
"The address type of udpEndpointLocalAddress. Only
|
261
|
+
IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
|
262
|
+
unknown(0) if datagrams for all local IP addresses are
|
263
|
+
accepted."
|
264
|
+
::= { udpEndpointEntry 1 }
|
265
|
+
|
266
|
+
udpEndpointLocalAddress OBJECT-TYPE
|
267
|
+
SYNTAX InetAddress
|
268
|
+
MAX-ACCESS not-accessible
|
269
|
+
STATUS current
|
270
|
+
DESCRIPTION
|
271
|
+
"The local IP address for this UDP endpoint.
|
272
|
+
|
273
|
+
The value of this object can be represented in three
|
274
|
+
|
275
|
+
possible ways, depending on the characteristics of the
|
276
|
+
listening application:
|
277
|
+
|
278
|
+
1. For an application that is willing to accept both
|
279
|
+
IPv4 and IPv6 datagrams, the value of this object
|
280
|
+
must be ''h (a zero-length octet-string), with
|
281
|
+
the value of the corresponding instance of the
|
282
|
+
udpEndpointLocalAddressType object being unknown(0).
|
283
|
+
|
284
|
+
2. For an application that is willing to accept only IPv4
|
285
|
+
or only IPv6 datagrams, the value of this object
|
286
|
+
must be '0.0.0.0' or '::', respectively, while the
|
287
|
+
corresponding instance of the
|
288
|
+
udpEndpointLocalAddressType object represents the
|
289
|
+
appropriate address type.
|
290
|
+
|
291
|
+
3. For an application that is listening for data
|
292
|
+
destined only to a specific IP address, the value
|
293
|
+
of this object is the specific IP address for which
|
294
|
+
this node is receiving packets, with the
|
295
|
+
corresponding instance of the
|
296
|
+
udpEndpointLocalAddressType object representing the
|
297
|
+
appropriate address type.
|
298
|
+
|
299
|
+
As this object is used in the index for the
|
300
|
+
udpEndpointTable, implementors of this table should be
|
301
|
+
careful not to create entries that would result in OIDs
|
302
|
+
with more than 128 subidentifiers; else the information
|
303
|
+
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3."
|
304
|
+
::= { udpEndpointEntry 2 }
|
305
|
+
|
306
|
+
udpEndpointLocalPort OBJECT-TYPE
|
307
|
+
SYNTAX InetPortNumber
|
308
|
+
MAX-ACCESS not-accessible
|
309
|
+
STATUS current
|
310
|
+
DESCRIPTION
|
311
|
+
"The local port number for this UDP endpoint."
|
312
|
+
::= { udpEndpointEntry 3 }
|
313
|
+
|
314
|
+
udpEndpointRemoteAddressType OBJECT-TYPE
|
315
|
+
SYNTAX InetAddressType
|
316
|
+
MAX-ACCESS not-accessible
|
317
|
+
STATUS current
|
318
|
+
DESCRIPTION
|
319
|
+
"The address type of udpEndpointRemoteAddress. Only
|
320
|
+
IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
|
321
|
+
unknown(0) if datagrams for all remote IP addresses are
|
322
|
+
accepted. Also, note that some combinations of
|
323
|
+
|
324
|
+
udpEndpointLocalAdressType and
|
325
|
+
udpEndpointRemoteAddressType are not supported. In
|
326
|
+
particular, if the value of this object is not
|
327
|
+
unknown(0), it is expected to always refer to the
|
328
|
+
same IP version as udpEndpointLocalAddressType."
|
329
|
+
::= { udpEndpointEntry 4 }
|
330
|
+
|
331
|
+
udpEndpointRemoteAddress OBJECT-TYPE
|
332
|
+
SYNTAX InetAddress
|
333
|
+
MAX-ACCESS not-accessible
|
334
|
+
STATUS current
|
335
|
+
DESCRIPTION
|
336
|
+
"The remote IP address for this UDP endpoint. If
|
337
|
+
datagrams from any remote system are to be accepted,
|
338
|
+
this value is ''h (a zero-length octet-string).
|
339
|
+
Otherwise, it has the type described by
|
340
|
+
udpEndpointRemoteAddressType and is the address of the
|
341
|
+
remote system from which datagrams are to be accepted
|
342
|
+
(or to which all datagrams will be sent).
|
343
|
+
|
344
|
+
As this object is used in the index for the
|
345
|
+
udpEndpointTable, implementors of this table should be
|
346
|
+
careful not to create entries that would result in OIDs
|
347
|
+
with more than 128 subidentifiers; else the information
|
348
|
+
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3."
|
349
|
+
::= { udpEndpointEntry 5 }
|
350
|
+
|
351
|
+
udpEndpointRemotePort OBJECT-TYPE
|
352
|
+
SYNTAX InetPortNumber
|
353
|
+
MAX-ACCESS not-accessible
|
354
|
+
STATUS current
|
355
|
+
DESCRIPTION
|
356
|
+
"The remote port number for this UDP endpoint. If
|
357
|
+
datagrams from any remote system are to be accepted,
|
358
|
+
this value is zero."
|
359
|
+
::= { udpEndpointEntry 6 }
|
360
|
+
|
361
|
+
udpEndpointInstance OBJECT-TYPE
|
362
|
+
SYNTAX Unsigned32 (1..'ffffffff'h)
|
363
|
+
MAX-ACCESS not-accessible
|
364
|
+
STATUS current
|
365
|
+
DESCRIPTION
|
366
|
+
"The instance of this tuple. This object is used to
|
367
|
+
distinguish among multiple processes 'connected' to
|
368
|
+
the same UDP endpoint. For example, on a system
|
369
|
+
implementing the BSD sockets interface, this would be
|
370
|
+
used to support the SO_REUSEADDR and SO_REUSEPORT
|
371
|
+
socket options."
|
372
|
+
::= { udpEndpointEntry 7 }
|
373
|
+
|
374
|
+
udpEndpointProcess OBJECT-TYPE
|
375
|
+
SYNTAX Unsigned32
|
376
|
+
MAX-ACCESS read-only
|
377
|
+
STATUS current
|
378
|
+
DESCRIPTION
|
379
|
+
"The system's process ID for the process associated with
|
380
|
+
this endpoint, or zero if there is no such process.
|
381
|
+
This value is expected to be the same as
|
382
|
+
HOST-RESOURCES-MIB::hrSWRunIndex or SYSAPPL-MIB::
|
383
|
+
sysApplElmtRunIndex for some row in the appropriate
|
384
|
+
tables."
|
385
|
+
::= { udpEndpointEntry 8 }
|
386
|
+
|
387
|
+
-- The deprecated UDP Listener table
|
388
|
+
|
389
|
+
-- The deprecated UDP listener table only contains information
|
390
|
+
-- about this entity's IPv4 UDP end-points on which a local
|
391
|
+
-- application is currently accepting datagrams. It does not
|
392
|
+
-- provide more detailed connection information, or information
|
393
|
+
-- about IPv6 endpoints.
|
394
|
+
|
395
|
+
udpTable OBJECT-TYPE
|
396
|
+
SYNTAX SEQUENCE OF UdpEntry
|
397
|
+
MAX-ACCESS not-accessible
|
398
|
+
STATUS deprecated
|
399
|
+
DESCRIPTION
|
400
|
+
"A table containing IPv4-specific UDP listener
|
401
|
+
information. It contains information about all local
|
402
|
+
IPv4 UDP end-points on which an application is
|
403
|
+
currently accepting datagrams. This table has been
|
404
|
+
deprecated in favor of the version neutral
|
405
|
+
udpEndpointTable."
|
406
|
+
::= { udp 5 }
|
407
|
+
|
408
|
+
udpEntry OBJECT-TYPE
|
409
|
+
SYNTAX UdpEntry
|
410
|
+
MAX-ACCESS not-accessible
|
411
|
+
STATUS deprecated
|
412
|
+
DESCRIPTION
|
413
|
+
"Information about a particular current UDP listener."
|
414
|
+
INDEX { udpLocalAddress, udpLocalPort }
|
415
|
+
::= { udpTable 1 }
|
416
|
+
|
417
|
+
UdpEntry ::= SEQUENCE {
|
418
|
+
udpLocalAddress IpAddress,
|
419
|
+
udpLocalPort Integer32
|
420
|
+
|
421
|
+
}
|
422
|
+
|
423
|
+
udpLocalAddress OBJECT-TYPE
|
424
|
+
SYNTAX IpAddress
|
425
|
+
MAX-ACCESS read-only
|
426
|
+
STATUS deprecated
|
427
|
+
DESCRIPTION
|
428
|
+
"The local IP address for this UDP listener. In the
|
429
|
+
case of a UDP listener that is willing to accept
|
430
|
+
datagrams for any IP interface associated with the
|
431
|
+
node, the value 0.0.0.0 is used."
|
432
|
+
::= { udpEntry 1 }
|
433
|
+
|
434
|
+
udpLocalPort OBJECT-TYPE
|
435
|
+
SYNTAX Integer32 (0..65535)
|
436
|
+
MAX-ACCESS read-only
|
437
|
+
STATUS deprecated
|
438
|
+
DESCRIPTION
|
439
|
+
"The local port number for this UDP listener."
|
440
|
+
::= { udpEntry 2 }
|
441
|
+
|
442
|
+
-- conformance information
|
443
|
+
|
444
|
+
udpMIBConformance OBJECT IDENTIFIER ::= { udpMIB 2 }
|
445
|
+
udpMIBCompliances OBJECT IDENTIFIER ::= { udpMIBConformance 1 }
|
446
|
+
udpMIBGroups OBJECT IDENTIFIER ::= { udpMIBConformance 2 }
|
447
|
+
|
448
|
+
-- compliance statements
|
449
|
+
|
450
|
+
udpMIBCompliance2 MODULE-COMPLIANCE
|
451
|
+
STATUS current
|
452
|
+
DESCRIPTION
|
453
|
+
"The compliance statement for systems that implement
|
454
|
+
UDP.
|
455
|
+
|
456
|
+
There are a number of INDEX objects that cannot be
|
457
|
+
represented in the form of OBJECT clauses in SMIv2, but
|
458
|
+
for which we have the following compliance
|
459
|
+
requirements, expressed in OBJECT clause form in this
|
460
|
+
description clause:
|
461
|
+
|
462
|
+
-- OBJECT udpEndpointLocalAddressType
|
463
|
+
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
|
464
|
+
-- ipv6(2), ipv4z(3),
|
465
|
+
-- ipv6z(4) }
|
466
|
+
-- DESCRIPTION
|
467
|
+
-- Support for dns(5) is not required.
|
468
|
+
-- OBJECT udpEndpointLocalAddress
|
469
|
+
|
470
|
+
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
|
471
|
+
-- DESCRIPTION
|
472
|
+
-- Support is only required for zero-length
|
473
|
+
-- octet-strings, and for scoped and unscoped
|
474
|
+
-- IPv4 and IPv6 addresses.
|
475
|
+
-- OBJECT udpEndpointRemoteAddressType
|
476
|
+
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
|
477
|
+
-- ipv6(2), ipv4z(3),
|
478
|
+
-- ipv6z(4) }
|
479
|
+
-- DESCRIPTION
|
480
|
+
-- Support for dns(5) is not required.
|
481
|
+
-- OBJECT udpEndpointRemoteAddress
|
482
|
+
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
|
483
|
+
-- DESCRIPTION
|
484
|
+
-- Support is only required for zero-length
|
485
|
+
-- octet-strings, and for scoped and unscoped
|
486
|
+
-- IPv4 and IPv6 addresses.
|
487
|
+
"
|
488
|
+
MODULE -- this module
|
489
|
+
MANDATORY-GROUPS { udpBaseGroup, udpEndpointGroup }
|
490
|
+
GROUP udpHCGroup
|
491
|
+
DESCRIPTION
|
492
|
+
"This group is mandatory for systems that
|
493
|
+
are capable of receiving or transmitting more than
|
494
|
+
1 million UDP datagrams per second. 1 million
|
495
|
+
datagrams per second will cause a Counter32 to
|
496
|
+
wrap in just over an hour."
|
497
|
+
::= { udpMIBCompliances 2 }
|
498
|
+
|
499
|
+
udpMIBCompliance MODULE-COMPLIANCE
|
500
|
+
STATUS deprecated
|
501
|
+
DESCRIPTION
|
502
|
+
"The compliance statement for IPv4-only systems that
|
503
|
+
implement UDP. For IP version independence, this
|
504
|
+
compliance statement is deprecated in favor of
|
505
|
+
udpMIBCompliance2. However, agents are still
|
506
|
+
encouraged to implement these objects in order to
|
507
|
+
interoperate with the deployed base of managers."
|
508
|
+
MODULE -- this module
|
509
|
+
MANDATORY-GROUPS { udpGroup }
|
510
|
+
::= { udpMIBCompliances 1 }
|
511
|
+
|
512
|
+
-- units of conformance
|
513
|
+
|
514
|
+
udpGroup OBJECT-GROUP
|
515
|
+
OBJECTS { udpInDatagrams, udpNoPorts,
|
516
|
+
udpInErrors, udpOutDatagrams,
|
517
|
+
udpLocalAddress, udpLocalPort }
|
518
|
+
STATUS deprecated
|
519
|
+
DESCRIPTION
|
520
|
+
"The deprecated group of objects providing for
|
521
|
+
management of UDP over IPv4."
|
522
|
+
::= { udpMIBGroups 1 }
|
523
|
+
|
524
|
+
udpBaseGroup OBJECT-GROUP
|
525
|
+
OBJECTS { udpInDatagrams, udpNoPorts, udpInErrors,
|
526
|
+
udpOutDatagrams }
|
527
|
+
STATUS current
|
528
|
+
DESCRIPTION
|
529
|
+
"The group of objects providing for counters of UDP
|
530
|
+
statistics."
|
531
|
+
::= { udpMIBGroups 2 }
|
532
|
+
|
533
|
+
udpHCGroup OBJECT-GROUP
|
534
|
+
OBJECTS { udpHCInDatagrams, udpHCOutDatagrams }
|
535
|
+
STATUS current
|
536
|
+
DESCRIPTION
|
537
|
+
"The group of objects providing for counters of high
|
538
|
+
speed UDP implementations."
|
539
|
+
::= { udpMIBGroups 3 }
|
540
|
+
|
541
|
+
udpEndpointGroup OBJECT-GROUP
|
542
|
+
OBJECTS { udpEndpointProcess }
|
543
|
+
STATUS current
|
544
|
+
DESCRIPTION
|
545
|
+
"The group of objects providing for the IP version
|
546
|
+
independent management of UDP 'endpoints'."
|
547
|
+
::= { udpMIBGroups 4 }
|
548
|
+
|
549
|
+
END
|