telemetry-snmp 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- 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,176 @@
|
|
|
1
|
+
SNMPv2-TM DEFINITIONS ::= BEGIN
|
|
2
|
+
|
|
3
|
+
IMPORTS
|
|
4
|
+
MODULE-IDENTITY, OBJECT-IDENTITY,
|
|
5
|
+
snmpModules, snmpDomains, snmpProxys
|
|
6
|
+
FROM SNMPv2-SMI
|
|
7
|
+
TEXTUAL-CONVENTION
|
|
8
|
+
FROM SNMPv2-TC;
|
|
9
|
+
|
|
10
|
+
snmpv2tm MODULE-IDENTITY
|
|
11
|
+
LAST-UPDATED "200210160000Z"
|
|
12
|
+
ORGANIZATION "IETF SNMPv3 Working Group"
|
|
13
|
+
CONTACT-INFO
|
|
14
|
+
"WG-EMail: snmpv3@lists.tislabs.com
|
|
15
|
+
Subscribe: snmpv3-request@lists.tislabs.com
|
|
16
|
+
|
|
17
|
+
Co-Chair: Russ Mundy
|
|
18
|
+
Network Associates Laboratories
|
|
19
|
+
postal: 15204 Omega Drive, Suite 300
|
|
20
|
+
Rockville, MD 20850-4601
|
|
21
|
+
USA
|
|
22
|
+
EMail: mundy@tislabs.com
|
|
23
|
+
phone: +1 301 947-7107
|
|
24
|
+
|
|
25
|
+
Co-Chair: David Harrington
|
|
26
|
+
Enterasys Networks
|
|
27
|
+
postal: 35 Industrial Way
|
|
28
|
+
P. O. Box 5005
|
|
29
|
+
Rochester, NH 03866-5005
|
|
30
|
+
USA
|
|
31
|
+
EMail: dbh@enterasys.com
|
|
32
|
+
phone: +1 603 337-2614
|
|
33
|
+
|
|
34
|
+
Editor: Randy Presuhn
|
|
35
|
+
BMC Software, Inc.
|
|
36
|
+
postal: 2141 North First Street
|
|
37
|
+
San Jose, CA 95131
|
|
38
|
+
USA
|
|
39
|
+
EMail: randy_presuhn@bmc.com
|
|
40
|
+
phone: +1 408 546-1006"
|
|
41
|
+
DESCRIPTION
|
|
42
|
+
"The MIB module for SNMP transport mappings.
|
|
43
|
+
|
|
44
|
+
Copyright (C) The Internet Society (2002). This
|
|
45
|
+
version of this MIB module is part of RFC 3417;
|
|
46
|
+
see the RFC itself for full legal notices.
|
|
47
|
+
"
|
|
48
|
+
REVISION "200210160000Z"
|
|
49
|
+
DESCRIPTION
|
|
50
|
+
"Clarifications, published as RFC 3417."
|
|
51
|
+
REVISION "199601010000Z"
|
|
52
|
+
DESCRIPTION
|
|
53
|
+
"Clarifications, published as RFC 1906."
|
|
54
|
+
REVISION "199304010000Z"
|
|
55
|
+
DESCRIPTION
|
|
56
|
+
"The initial version, published as RFC 1449."
|
|
57
|
+
::= { snmpModules 19 }
|
|
58
|
+
|
|
59
|
+
-- SNMP over UDP over IPv4
|
|
60
|
+
|
|
61
|
+
snmpUDPDomain OBJECT-IDENTITY
|
|
62
|
+
STATUS current
|
|
63
|
+
DESCRIPTION
|
|
64
|
+
"The SNMP over UDP over IPv4 transport domain.
|
|
65
|
+
The corresponding transport address is of type
|
|
66
|
+
SnmpUDPAddress."
|
|
67
|
+
::= { snmpDomains 1 }
|
|
68
|
+
|
|
69
|
+
SnmpUDPAddress ::= TEXTUAL-CONVENTION
|
|
70
|
+
DISPLAY-HINT "1d.1d.1d.1d/2d"
|
|
71
|
+
STATUS current
|
|
72
|
+
DESCRIPTION
|
|
73
|
+
"Represents a UDP over IPv4 address:
|
|
74
|
+
|
|
75
|
+
octets contents encoding
|
|
76
|
+
1-4 IP-address network-byte order
|
|
77
|
+
5-6 UDP-port network-byte order
|
|
78
|
+
"
|
|
79
|
+
SYNTAX OCTET STRING (SIZE (6))
|
|
80
|
+
|
|
81
|
+
-- SNMP over OSI
|
|
82
|
+
|
|
83
|
+
snmpCLNSDomain OBJECT-IDENTITY
|
|
84
|
+
STATUS current
|
|
85
|
+
DESCRIPTION
|
|
86
|
+
"The SNMP over CLNS transport domain.
|
|
87
|
+
The corresponding transport address is of type
|
|
88
|
+
SnmpOSIAddress."
|
|
89
|
+
::= { snmpDomains 2 }
|
|
90
|
+
|
|
91
|
+
snmpCONSDomain OBJECT-IDENTITY
|
|
92
|
+
STATUS current
|
|
93
|
+
DESCRIPTION
|
|
94
|
+
"The SNMP over CONS transport domain.
|
|
95
|
+
The corresponding transport address is of type
|
|
96
|
+
SnmpOSIAddress."
|
|
97
|
+
::= { snmpDomains 3 }
|
|
98
|
+
|
|
99
|
+
SnmpOSIAddress ::= TEXTUAL-CONVENTION
|
|
100
|
+
DISPLAY-HINT "*1x:/1x:"
|
|
101
|
+
STATUS current
|
|
102
|
+
DESCRIPTION
|
|
103
|
+
"Represents an OSI transport-address:
|
|
104
|
+
|
|
105
|
+
octets contents encoding
|
|
106
|
+
1 length of NSAP 'n' as an unsigned-integer
|
|
107
|
+
(either 0 or from 3 to 20)
|
|
108
|
+
2..(n+1) NSAP concrete binary representation
|
|
109
|
+
(n+2)..m TSEL string of (up to 64) octets
|
|
110
|
+
"
|
|
111
|
+
SYNTAX OCTET STRING (SIZE (1 | 4..85))
|
|
112
|
+
|
|
113
|
+
-- SNMP over DDP
|
|
114
|
+
|
|
115
|
+
snmpDDPDomain OBJECT-IDENTITY
|
|
116
|
+
STATUS current
|
|
117
|
+
DESCRIPTION
|
|
118
|
+
"The SNMP over DDP transport domain. The corresponding
|
|
119
|
+
transport address is of type SnmpNBPAddress."
|
|
120
|
+
::= { snmpDomains 4 }
|
|
121
|
+
|
|
122
|
+
SnmpNBPAddress ::= TEXTUAL-CONVENTION
|
|
123
|
+
STATUS current
|
|
124
|
+
DESCRIPTION
|
|
125
|
+
"Represents an NBP name:
|
|
126
|
+
|
|
127
|
+
octets contents encoding
|
|
128
|
+
1 length of object 'n' as an unsigned integer
|
|
129
|
+
2..(n+1) object string of (up to 32) octets
|
|
130
|
+
n+2 length of type 'p' as an unsigned integer
|
|
131
|
+
(n+3)..(n+2+p) type string of (up to 32) octets
|
|
132
|
+
n+3+p length of zone 'q' as an unsigned integer
|
|
133
|
+
(n+4+p)..(n+3+p+q) zone string of (up to 32) octets
|
|
134
|
+
|
|
135
|
+
For comparison purposes, strings are
|
|
136
|
+
case-insensitive. All strings may contain any octet
|
|
137
|
+
other than 255 (hex ff)."
|
|
138
|
+
SYNTAX OCTET STRING (SIZE (3..99))
|
|
139
|
+
|
|
140
|
+
-- SNMP over IPX
|
|
141
|
+
|
|
142
|
+
snmpIPXDomain OBJECT-IDENTITY
|
|
143
|
+
STATUS current
|
|
144
|
+
DESCRIPTION
|
|
145
|
+
"The SNMP over IPX transport domain. The corresponding
|
|
146
|
+
transport address is of type SnmpIPXAddress."
|
|
147
|
+
::= { snmpDomains 5 }
|
|
148
|
+
|
|
149
|
+
SnmpIPXAddress ::= TEXTUAL-CONVENTION
|
|
150
|
+
DISPLAY-HINT "4x.1x:1x:1x:1x:1x:1x.2d"
|
|
151
|
+
STATUS current
|
|
152
|
+
DESCRIPTION
|
|
153
|
+
"Represents an IPX address:
|
|
154
|
+
|
|
155
|
+
octets contents encoding
|
|
156
|
+
1-4 network-number network-byte order
|
|
157
|
+
5-10 physical-address network-byte order
|
|
158
|
+
11-12 socket-number network-byte order
|
|
159
|
+
"
|
|
160
|
+
SYNTAX OCTET STRING (SIZE (12))
|
|
161
|
+
|
|
162
|
+
-- for proxy to SNMPv1 (RFC 1157)
|
|
163
|
+
|
|
164
|
+
rfc1157Proxy OBJECT IDENTIFIER ::= { snmpProxys 1 }
|
|
165
|
+
|
|
166
|
+
rfc1157Domain OBJECT-IDENTITY
|
|
167
|
+
STATUS deprecated
|
|
168
|
+
DESCRIPTION
|
|
169
|
+
"The transport domain for SNMPv1 over UDP over IPv4.
|
|
170
|
+
The corresponding transport address is of type
|
|
171
|
+
SnmpUDPAddress."
|
|
172
|
+
::= { rfc1157Proxy 1 }
|
|
173
|
+
|
|
174
|
+
-- ::= { rfc1157Proxy 2 } this OID is obsolete
|
|
175
|
+
|
|
176
|
+
END
|
|
@@ -0,0 +1,785 @@
|
|
|
1
|
+
TCP-MIB DEFINITIONS ::= BEGIN
|
|
2
|
+
|
|
3
|
+
IMPORTS
|
|
4
|
+
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32,
|
|
5
|
+
Gauge32, Counter32, Counter64, IpAddress, mib-2
|
|
6
|
+
FROM SNMPv2-SMI
|
|
7
|
+
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
|
|
8
|
+
InetAddress, InetAddressType,
|
|
9
|
+
InetPortNumber FROM INET-ADDRESS-MIB;
|
|
10
|
+
|
|
11
|
+
tcpMIB MODULE-IDENTITY
|
|
12
|
+
LAST-UPDATED "200502180000Z" -- 18 February 2005
|
|
13
|
+
ORGANIZATION
|
|
14
|
+
"IETF IPv6 MIB Revision Team
|
|
15
|
+
http://www.ietf.org/html.charters/ipv6-charter.html"
|
|
16
|
+
CONTACT-INFO
|
|
17
|
+
"Rajiv Raghunarayan (editor)
|
|
18
|
+
|
|
19
|
+
Cisco Systems Inc.
|
|
20
|
+
170 West Tasman Drive
|
|
21
|
+
San Jose, CA 95134
|
|
22
|
+
|
|
23
|
+
Phone: +1 408 853 9612
|
|
24
|
+
Email: <raraghun@cisco.com>
|
|
25
|
+
|
|
26
|
+
Send comments to <ipv6@ietf.org>"
|
|
27
|
+
DESCRIPTION
|
|
28
|
+
"The MIB module for managing TCP implementations.
|
|
29
|
+
|
|
30
|
+
Copyright (C) The Internet Society (2005). This version
|
|
31
|
+
of this MIB module is a part of RFC 4022; see the RFC
|
|
32
|
+
itself for full legal notices."
|
|
33
|
+
REVISION "200502180000Z" -- 18 February 2005
|
|
34
|
+
DESCRIPTION
|
|
35
|
+
"IP version neutral revision, published as RFC 4022."
|
|
36
|
+
REVISION "9411010000Z"
|
|
37
|
+
DESCRIPTION
|
|
38
|
+
"Initial SMIv2 version, published as RFC 2012."
|
|
39
|
+
REVISION "9103310000Z"
|
|
40
|
+
DESCRIPTION
|
|
41
|
+
"The initial revision of this MIB module was part of
|
|
42
|
+
MIB-II."
|
|
43
|
+
::= { mib-2 49 }
|
|
44
|
+
|
|
45
|
+
-- the TCP base variables group
|
|
46
|
+
|
|
47
|
+
tcp OBJECT IDENTIFIER ::= { mib-2 6 }
|
|
48
|
+
|
|
49
|
+
-- Scalars
|
|
50
|
+
|
|
51
|
+
tcpRtoAlgorithm OBJECT-TYPE
|
|
52
|
+
SYNTAX INTEGER {
|
|
53
|
+
other(1), -- none of the following
|
|
54
|
+
constant(2), -- a constant rto
|
|
55
|
+
rsre(3), -- MIL-STD-1778, Appendix B
|
|
56
|
+
vanj(4), -- Van Jacobson's algorithm
|
|
57
|
+
rfc2988(5) -- RFC 2988
|
|
58
|
+
}
|
|
59
|
+
MAX-ACCESS read-only
|
|
60
|
+
STATUS current
|
|
61
|
+
DESCRIPTION
|
|
62
|
+
"The algorithm used to determine the timeout value used for
|
|
63
|
+
retransmitting unacknowledged octets."
|
|
64
|
+
::= { tcp 1 }
|
|
65
|
+
|
|
66
|
+
tcpRtoMin OBJECT-TYPE
|
|
67
|
+
SYNTAX Integer32 (0..2147483647)
|
|
68
|
+
UNITS "milliseconds"
|
|
69
|
+
MAX-ACCESS read-only
|
|
70
|
+
STATUS current
|
|
71
|
+
DESCRIPTION
|
|
72
|
+
"The minimum value permitted by a TCP implementation for
|
|
73
|
+
the retransmission timeout, measured in milliseconds.
|
|
74
|
+
More refined semantics for objects of this type depend
|
|
75
|
+
on the algorithm used to determine the retransmission
|
|
76
|
+
timeout; in particular, the IETF standard algorithm
|
|
77
|
+
rfc2988(5) provides a minimum value."
|
|
78
|
+
::= { tcp 2 }
|
|
79
|
+
|
|
80
|
+
tcpRtoMax OBJECT-TYPE
|
|
81
|
+
SYNTAX Integer32 (0..2147483647)
|
|
82
|
+
UNITS "milliseconds"
|
|
83
|
+
MAX-ACCESS read-only
|
|
84
|
+
STATUS current
|
|
85
|
+
DESCRIPTION
|
|
86
|
+
"The maximum value permitted by a TCP implementation for
|
|
87
|
+
the retransmission timeout, measured in milliseconds.
|
|
88
|
+
More refined semantics for objects of this type depend
|
|
89
|
+
on the algorithm used to determine the retransmission
|
|
90
|
+
timeout; in particular, the IETF standard algorithm
|
|
91
|
+
rfc2988(5) provides an upper bound (as part of an
|
|
92
|
+
adaptive backoff algorithm)."
|
|
93
|
+
::= { tcp 3 }
|
|
94
|
+
|
|
95
|
+
tcpMaxConn OBJECT-TYPE
|
|
96
|
+
SYNTAX Integer32 (-1 | 0..2147483647)
|
|
97
|
+
MAX-ACCESS read-only
|
|
98
|
+
STATUS current
|
|
99
|
+
DESCRIPTION
|
|
100
|
+
"The limit on the total number of TCP connections the entity
|
|
101
|
+
can support. In entities where the maximum number of
|
|
102
|
+
connections is dynamic, this object should contain the
|
|
103
|
+
value -1."
|
|
104
|
+
::= { tcp 4 }
|
|
105
|
+
|
|
106
|
+
tcpActiveOpens OBJECT-TYPE
|
|
107
|
+
SYNTAX Counter32
|
|
108
|
+
MAX-ACCESS read-only
|
|
109
|
+
STATUS current
|
|
110
|
+
DESCRIPTION
|
|
111
|
+
"The number of times that TCP connections have made a direct
|
|
112
|
+
transition to the SYN-SENT state from the CLOSED state.
|
|
113
|
+
|
|
114
|
+
Discontinuities in the value of this counter are
|
|
115
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
116
|
+
::= { tcp 5 }
|
|
117
|
+
|
|
118
|
+
tcpPassiveOpens OBJECT-TYPE
|
|
119
|
+
SYNTAX Counter32
|
|
120
|
+
MAX-ACCESS read-only
|
|
121
|
+
STATUS current
|
|
122
|
+
DESCRIPTION
|
|
123
|
+
"The number of times TCP connections have made a direct
|
|
124
|
+
transition to the SYN-RCVD state from the LISTEN state.
|
|
125
|
+
|
|
126
|
+
Discontinuities in the value of this counter are
|
|
127
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
128
|
+
::= { tcp 6 }
|
|
129
|
+
|
|
130
|
+
tcpAttemptFails OBJECT-TYPE
|
|
131
|
+
SYNTAX Counter32
|
|
132
|
+
MAX-ACCESS read-only
|
|
133
|
+
STATUS current
|
|
134
|
+
DESCRIPTION
|
|
135
|
+
"The number of times that TCP connections have made a direct
|
|
136
|
+
transition to the CLOSED state from either the SYN-SENT
|
|
137
|
+
state or the SYN-RCVD state, plus the number of times that
|
|
138
|
+
TCP connections have made a direct transition to the
|
|
139
|
+
LISTEN state from the SYN-RCVD state.
|
|
140
|
+
|
|
141
|
+
Discontinuities in the value of this counter are
|
|
142
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
143
|
+
::= { tcp 7 }
|
|
144
|
+
|
|
145
|
+
tcpEstabResets OBJECT-TYPE
|
|
146
|
+
SYNTAX Counter32
|
|
147
|
+
MAX-ACCESS read-only
|
|
148
|
+
STATUS current
|
|
149
|
+
DESCRIPTION
|
|
150
|
+
"The number of times that TCP connections have made a direct
|
|
151
|
+
transition to the CLOSED state from either the ESTABLISHED
|
|
152
|
+
state or the CLOSE-WAIT state.
|
|
153
|
+
|
|
154
|
+
Discontinuities in the value of this counter are
|
|
155
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
156
|
+
::= { tcp 8 }
|
|
157
|
+
|
|
158
|
+
tcpCurrEstab OBJECT-TYPE
|
|
159
|
+
SYNTAX Gauge32
|
|
160
|
+
MAX-ACCESS read-only
|
|
161
|
+
STATUS current
|
|
162
|
+
DESCRIPTION
|
|
163
|
+
"The number of TCP connections for which the current state
|
|
164
|
+
is either ESTABLISHED or CLOSE-WAIT."
|
|
165
|
+
::= { tcp 9 }
|
|
166
|
+
|
|
167
|
+
tcpInSegs OBJECT-TYPE
|
|
168
|
+
SYNTAX Counter32
|
|
169
|
+
MAX-ACCESS read-only
|
|
170
|
+
STATUS current
|
|
171
|
+
DESCRIPTION
|
|
172
|
+
"The total number of segments received, including those
|
|
173
|
+
received in error. This count includes segments received
|
|
174
|
+
on currently established connections.
|
|
175
|
+
|
|
176
|
+
Discontinuities in the value of this counter are
|
|
177
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
178
|
+
::= { tcp 10 }
|
|
179
|
+
|
|
180
|
+
tcpOutSegs OBJECT-TYPE
|
|
181
|
+
SYNTAX Counter32
|
|
182
|
+
MAX-ACCESS read-only
|
|
183
|
+
STATUS current
|
|
184
|
+
DESCRIPTION
|
|
185
|
+
"The total number of segments sent, including those on
|
|
186
|
+
current connections but excluding those containing only
|
|
187
|
+
retransmitted octets.
|
|
188
|
+
|
|
189
|
+
Discontinuities in the value of this counter are
|
|
190
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
191
|
+
::= { tcp 11 }
|
|
192
|
+
|
|
193
|
+
tcpRetransSegs OBJECT-TYPE
|
|
194
|
+
SYNTAX Counter32
|
|
195
|
+
MAX-ACCESS read-only
|
|
196
|
+
STATUS current
|
|
197
|
+
DESCRIPTION
|
|
198
|
+
"The total number of segments retransmitted; that is, the
|
|
199
|
+
number of TCP segments transmitted containing one or more
|
|
200
|
+
previously transmitted octets.
|
|
201
|
+
|
|
202
|
+
Discontinuities in the value of this counter are
|
|
203
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
204
|
+
::= { tcp 12 }
|
|
205
|
+
|
|
206
|
+
tcpInErrs OBJECT-TYPE
|
|
207
|
+
SYNTAX Counter32
|
|
208
|
+
MAX-ACCESS read-only
|
|
209
|
+
STATUS current
|
|
210
|
+
DESCRIPTION
|
|
211
|
+
"The total number of segments received in error (e.g., bad
|
|
212
|
+
TCP checksums).
|
|
213
|
+
|
|
214
|
+
Discontinuities in the value of this counter are
|
|
215
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
216
|
+
::= { tcp 14 }
|
|
217
|
+
|
|
218
|
+
tcpOutRsts OBJECT-TYPE
|
|
219
|
+
SYNTAX Counter32
|
|
220
|
+
MAX-ACCESS read-only
|
|
221
|
+
STATUS current
|
|
222
|
+
DESCRIPTION
|
|
223
|
+
"The number of TCP segments sent containing the RST flag.
|
|
224
|
+
|
|
225
|
+
Discontinuities in the value of this counter are
|
|
226
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
227
|
+
::= { tcp 15 }
|
|
228
|
+
|
|
229
|
+
-- { tcp 16 } was used to represent the ipv6TcpConnTable in RFC 2452,
|
|
230
|
+
-- which has since been obsoleted. It MUST not be used.
|
|
231
|
+
|
|
232
|
+
tcpHCInSegs OBJECT-TYPE
|
|
233
|
+
SYNTAX Counter64
|
|
234
|
+
MAX-ACCESS read-only
|
|
235
|
+
STATUS current
|
|
236
|
+
DESCRIPTION
|
|
237
|
+
"The total number of segments received, including those
|
|
238
|
+
received in error. This count includes segments received
|
|
239
|
+
|
|
240
|
+
on currently established connections. This object is
|
|
241
|
+
the 64-bit equivalent of tcpInSegs.
|
|
242
|
+
|
|
243
|
+
Discontinuities in the value of this counter are
|
|
244
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
245
|
+
::= { tcp 17 }
|
|
246
|
+
|
|
247
|
+
tcpHCOutSegs OBJECT-TYPE
|
|
248
|
+
SYNTAX Counter64
|
|
249
|
+
MAX-ACCESS read-only
|
|
250
|
+
STATUS current
|
|
251
|
+
DESCRIPTION
|
|
252
|
+
"The total number of segments sent, including those on
|
|
253
|
+
current connections but excluding those containing only
|
|
254
|
+
retransmitted octets. This object is the 64-bit
|
|
255
|
+
equivalent of tcpOutSegs.
|
|
256
|
+
|
|
257
|
+
Discontinuities in the value of this counter are
|
|
258
|
+
indicated via discontinuities in the value of sysUpTime."
|
|
259
|
+
::= { tcp 18 }
|
|
260
|
+
|
|
261
|
+
-- The TCP Connection table
|
|
262
|
+
|
|
263
|
+
tcpConnectionTable OBJECT-TYPE
|
|
264
|
+
SYNTAX SEQUENCE OF TcpConnectionEntry
|
|
265
|
+
MAX-ACCESS not-accessible
|
|
266
|
+
STATUS current
|
|
267
|
+
DESCRIPTION
|
|
268
|
+
"A table containing information about existing TCP
|
|
269
|
+
connections. Note that unlike earlier TCP MIBs, there
|
|
270
|
+
is a separate table for connections in the LISTEN state."
|
|
271
|
+
::= { tcp 19 }
|
|
272
|
+
|
|
273
|
+
tcpConnectionEntry OBJECT-TYPE
|
|
274
|
+
SYNTAX TcpConnectionEntry
|
|
275
|
+
MAX-ACCESS not-accessible
|
|
276
|
+
STATUS current
|
|
277
|
+
DESCRIPTION
|
|
278
|
+
"A conceptual row of the tcpConnectionTable containing
|
|
279
|
+
information about a particular current TCP connection.
|
|
280
|
+
Each row of this table is transient in that it ceases to
|
|
281
|
+
exist when (or soon after) the connection makes the
|
|
282
|
+
transition to the CLOSED state."
|
|
283
|
+
INDEX { tcpConnectionLocalAddressType,
|
|
284
|
+
tcpConnectionLocalAddress,
|
|
285
|
+
tcpConnectionLocalPort,
|
|
286
|
+
tcpConnectionRemAddressType,
|
|
287
|
+
tcpConnectionRemAddress,
|
|
288
|
+
tcpConnectionRemPort }
|
|
289
|
+
::= { tcpConnectionTable 1 }
|
|
290
|
+
|
|
291
|
+
TcpConnectionEntry ::= SEQUENCE {
|
|
292
|
+
tcpConnectionLocalAddressType InetAddressType,
|
|
293
|
+
tcpConnectionLocalAddress InetAddress,
|
|
294
|
+
tcpConnectionLocalPort InetPortNumber,
|
|
295
|
+
tcpConnectionRemAddressType InetAddressType,
|
|
296
|
+
tcpConnectionRemAddress InetAddress,
|
|
297
|
+
tcpConnectionRemPort InetPortNumber,
|
|
298
|
+
tcpConnectionState INTEGER,
|
|
299
|
+
tcpConnectionProcess Unsigned32
|
|
300
|
+
}
|
|
301
|
+
|
|
302
|
+
tcpConnectionLocalAddressType OBJECT-TYPE
|
|
303
|
+
SYNTAX InetAddressType
|
|
304
|
+
MAX-ACCESS not-accessible
|
|
305
|
+
STATUS current
|
|
306
|
+
DESCRIPTION
|
|
307
|
+
"The address type of tcpConnectionLocalAddress."
|
|
308
|
+
::= { tcpConnectionEntry 1 }
|
|
309
|
+
|
|
310
|
+
tcpConnectionLocalAddress OBJECT-TYPE
|
|
311
|
+
SYNTAX InetAddress
|
|
312
|
+
MAX-ACCESS not-accessible
|
|
313
|
+
STATUS current
|
|
314
|
+
DESCRIPTION
|
|
315
|
+
"The local IP address for this TCP connection. The type
|
|
316
|
+
of this address is determined by the value of
|
|
317
|
+
tcpConnectionLocalAddressType.
|
|
318
|
+
|
|
319
|
+
As this object is used in the index for the
|
|
320
|
+
tcpConnectionTable, implementors should be
|
|
321
|
+
careful not to create entries that would result in OIDs
|
|
322
|
+
with more than 128 subidentifiers; otherwise the information
|
|
323
|
+
cannot be accessed by using SNMPv1, SNMPv2c, or SNMPv3."
|
|
324
|
+
::= { tcpConnectionEntry 2 }
|
|
325
|
+
|
|
326
|
+
tcpConnectionLocalPort OBJECT-TYPE
|
|
327
|
+
SYNTAX InetPortNumber
|
|
328
|
+
MAX-ACCESS not-accessible
|
|
329
|
+
STATUS current
|
|
330
|
+
DESCRIPTION
|
|
331
|
+
"The local port number for this TCP connection."
|
|
332
|
+
::= { tcpConnectionEntry 3 }
|
|
333
|
+
|
|
334
|
+
tcpConnectionRemAddressType OBJECT-TYPE
|
|
335
|
+
SYNTAX InetAddressType
|
|
336
|
+
MAX-ACCESS not-accessible
|
|
337
|
+
STATUS current
|
|
338
|
+
DESCRIPTION
|
|
339
|
+
"The address type of tcpConnectionRemAddress."
|
|
340
|
+
::= { tcpConnectionEntry 4 }
|
|
341
|
+
|
|
342
|
+
tcpConnectionRemAddress OBJECT-TYPE
|
|
343
|
+
SYNTAX InetAddress
|
|
344
|
+
MAX-ACCESS not-accessible
|
|
345
|
+
STATUS current
|
|
346
|
+
DESCRIPTION
|
|
347
|
+
"The remote IP address for this TCP connection. The type
|
|
348
|
+
of this address is determined by the value of
|
|
349
|
+
tcpConnectionRemAddressType.
|
|
350
|
+
|
|
351
|
+
As this object is used in the index for the
|
|
352
|
+
tcpConnectionTable, implementors should be
|
|
353
|
+
careful not to create entries that would result in OIDs
|
|
354
|
+
with more than 128 subidentifiers; otherwise the information
|
|
355
|
+
cannot be accessed by using SNMPv1, SNMPv2c, or SNMPv3."
|
|
356
|
+
::= { tcpConnectionEntry 5 }
|
|
357
|
+
|
|
358
|
+
tcpConnectionRemPort OBJECT-TYPE
|
|
359
|
+
SYNTAX InetPortNumber
|
|
360
|
+
MAX-ACCESS not-accessible
|
|
361
|
+
STATUS current
|
|
362
|
+
DESCRIPTION
|
|
363
|
+
"The remote port number for this TCP connection."
|
|
364
|
+
::= { tcpConnectionEntry 6 }
|
|
365
|
+
|
|
366
|
+
tcpConnectionState OBJECT-TYPE
|
|
367
|
+
SYNTAX INTEGER {
|
|
368
|
+
closed(1),
|
|
369
|
+
listen(2),
|
|
370
|
+
synSent(3),
|
|
371
|
+
synReceived(4),
|
|
372
|
+
established(5),
|
|
373
|
+
finWait1(6),
|
|
374
|
+
finWait2(7),
|
|
375
|
+
closeWait(8),
|
|
376
|
+
lastAck(9),
|
|
377
|
+
closing(10),
|
|
378
|
+
timeWait(11),
|
|
379
|
+
deleteTCB(12)
|
|
380
|
+
}
|
|
381
|
+
MAX-ACCESS read-write
|
|
382
|
+
STATUS current
|
|
383
|
+
DESCRIPTION
|
|
384
|
+
"The state of this TCP connection.
|
|
385
|
+
|
|
386
|
+
The value listen(2) is included only for parallelism to the
|
|
387
|
+
old tcpConnTable and should not be used. A connection in
|
|
388
|
+
LISTEN state should be present in the tcpListenerTable.
|
|
389
|
+
|
|
390
|
+
The only value that may be set by a management station is
|
|
391
|
+
deleteTCB(12). Accordingly, it is appropriate for an agent
|
|
392
|
+
to return a `badValue' response if a management station
|
|
393
|
+
attempts to set this object to any other value.
|
|
394
|
+
|
|
395
|
+
If a management station sets this object to the value
|
|
396
|
+
deleteTCB(12), then the TCB (as defined in [RFC793]) of
|
|
397
|
+
the corresponding connection on the managed node is
|
|
398
|
+
deleted, resulting in immediate termination of the
|
|
399
|
+
connection.
|
|
400
|
+
|
|
401
|
+
As an implementation-specific option, a RST segment may be
|
|
402
|
+
sent from the managed node to the other TCP endpoint (note,
|
|
403
|
+
however, that RST segments are not sent reliably)."
|
|
404
|
+
::= { tcpConnectionEntry 7 }
|
|
405
|
+
|
|
406
|
+
tcpConnectionProcess OBJECT-TYPE
|
|
407
|
+
SYNTAX Unsigned32
|
|
408
|
+
MAX-ACCESS read-only
|
|
409
|
+
STATUS current
|
|
410
|
+
DESCRIPTION
|
|
411
|
+
"The system's process ID for the process associated with
|
|
412
|
+
this connection, or zero if there is no such process. This
|
|
413
|
+
value is expected to be the same as HOST-RESOURCES-MIB::
|
|
414
|
+
hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some
|
|
415
|
+
row in the appropriate tables."
|
|
416
|
+
::= { tcpConnectionEntry 8 }
|
|
417
|
+
|
|
418
|
+
-- The TCP Listener table
|
|
419
|
+
|
|
420
|
+
tcpListenerTable OBJECT-TYPE
|
|
421
|
+
SYNTAX SEQUENCE OF TcpListenerEntry
|
|
422
|
+
MAX-ACCESS not-accessible
|
|
423
|
+
STATUS current
|
|
424
|
+
DESCRIPTION
|
|
425
|
+
"A table containing information about TCP listeners. A
|
|
426
|
+
listening application can be represented in three
|
|
427
|
+
possible ways:
|
|
428
|
+
|
|
429
|
+
1. An application that is willing to accept both IPv4 and
|
|
430
|
+
IPv6 datagrams is represented by
|
|
431
|
+
|
|
432
|
+
a tcpListenerLocalAddressType of unknown (0) and
|
|
433
|
+
a tcpListenerLocalAddress of ''h (a zero-length
|
|
434
|
+
octet-string).
|
|
435
|
+
|
|
436
|
+
2. An application that is willing to accept only IPv4 or
|
|
437
|
+
IPv6 datagrams is represented by a
|
|
438
|
+
tcpListenerLocalAddressType of the appropriate address
|
|
439
|
+
type and a tcpListenerLocalAddress of '0.0.0.0' or '::'
|
|
440
|
+
respectively.
|
|
441
|
+
|
|
442
|
+
3. An application that is listening for data destined
|
|
443
|
+
only to a specific IP address, but from any remote
|
|
444
|
+
system, is represented by a tcpListenerLocalAddressType
|
|
445
|
+
of an appropriate address type, with
|
|
446
|
+
tcpListenerLocalAddress as the specific local address.
|
|
447
|
+
|
|
448
|
+
NOTE: The address type in this table represents the
|
|
449
|
+
address type used for the communication, irrespective
|
|
450
|
+
of the higher-layer abstraction. For example, an
|
|
451
|
+
application using IPv6 'sockets' to communicate via
|
|
452
|
+
IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would
|
|
453
|
+
use InetAddressType ipv4(1))."
|
|
454
|
+
::= { tcp 20 }
|
|
455
|
+
|
|
456
|
+
tcpListenerEntry OBJECT-TYPE
|
|
457
|
+
SYNTAX TcpListenerEntry
|
|
458
|
+
MAX-ACCESS not-accessible
|
|
459
|
+
STATUS current
|
|
460
|
+
DESCRIPTION
|
|
461
|
+
"A conceptual row of the tcpListenerTable containing
|
|
462
|
+
information about a particular TCP listener."
|
|
463
|
+
INDEX { tcpListenerLocalAddressType,
|
|
464
|
+
tcpListenerLocalAddress,
|
|
465
|
+
tcpListenerLocalPort }
|
|
466
|
+
::= { tcpListenerTable 1 }
|
|
467
|
+
|
|
468
|
+
TcpListenerEntry ::= SEQUENCE {
|
|
469
|
+
tcpListenerLocalAddressType InetAddressType,
|
|
470
|
+
tcpListenerLocalAddress InetAddress,
|
|
471
|
+
tcpListenerLocalPort InetPortNumber,
|
|
472
|
+
tcpListenerProcess Unsigned32
|
|
473
|
+
}
|
|
474
|
+
|
|
475
|
+
tcpListenerLocalAddressType OBJECT-TYPE
|
|
476
|
+
SYNTAX InetAddressType
|
|
477
|
+
MAX-ACCESS not-accessible
|
|
478
|
+
STATUS current
|
|
479
|
+
DESCRIPTION
|
|
480
|
+
"The address type of tcpListenerLocalAddress. The value
|
|
481
|
+
should be unknown (0) if connection initiations to all
|
|
482
|
+
local IP addresses are accepted."
|
|
483
|
+
::= { tcpListenerEntry 1 }
|
|
484
|
+
|
|
485
|
+
tcpListenerLocalAddress OBJECT-TYPE
|
|
486
|
+
SYNTAX InetAddress
|
|
487
|
+
MAX-ACCESS not-accessible
|
|
488
|
+
STATUS current
|
|
489
|
+
DESCRIPTION
|
|
490
|
+
"The local IP address for this TCP connection.
|
|
491
|
+
|
|
492
|
+
The value of this object can be represented in three
|
|
493
|
+
possible ways, depending on the characteristics of the
|
|
494
|
+
listening application:
|
|
495
|
+
|
|
496
|
+
1. For an application willing to accept both IPv4 and
|
|
497
|
+
IPv6 datagrams, the value of this object must be
|
|
498
|
+
''h (a zero-length octet-string), with the value
|
|
499
|
+
of the corresponding tcpListenerLocalAddressType
|
|
500
|
+
object being unknown (0).
|
|
501
|
+
|
|
502
|
+
2. For an application willing to accept only IPv4 or
|
|
503
|
+
IPv6 datagrams, the value of this object must be
|
|
504
|
+
'0.0.0.0' or '::' respectively, with
|
|
505
|
+
tcpListenerLocalAddressType representing the
|
|
506
|
+
appropriate address type.
|
|
507
|
+
|
|
508
|
+
3. For an application which is listening for data
|
|
509
|
+
destined only to a specific IP address, the value
|
|
510
|
+
of this object is the specific local address, with
|
|
511
|
+
tcpListenerLocalAddressType representing the
|
|
512
|
+
appropriate address type.
|
|
513
|
+
|
|
514
|
+
As this object is used in the index for the
|
|
515
|
+
tcpListenerTable, implementors should be
|
|
516
|
+
careful not to create entries that would result in OIDs
|
|
517
|
+
with more than 128 subidentifiers; otherwise the information
|
|
518
|
+
cannot be accessed, using SNMPv1, SNMPv2c, or SNMPv3."
|
|
519
|
+
::= { tcpListenerEntry 2 }
|
|
520
|
+
|
|
521
|
+
tcpListenerLocalPort OBJECT-TYPE
|
|
522
|
+
SYNTAX InetPortNumber
|
|
523
|
+
MAX-ACCESS not-accessible
|
|
524
|
+
STATUS current
|
|
525
|
+
DESCRIPTION
|
|
526
|
+
"The local port number for this TCP connection."
|
|
527
|
+
::= { tcpListenerEntry 3 }
|
|
528
|
+
|
|
529
|
+
tcpListenerProcess OBJECT-TYPE
|
|
530
|
+
SYNTAX Unsigned32
|
|
531
|
+
MAX-ACCESS read-only
|
|
532
|
+
STATUS current
|
|
533
|
+
DESCRIPTION
|
|
534
|
+
"The system's process ID for the process associated with
|
|
535
|
+
this listener, or zero if there is no such process. This
|
|
536
|
+
value is expected to be the same as HOST-RESOURCES-MIB::
|
|
537
|
+
hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some
|
|
538
|
+
row in the appropriate tables."
|
|
539
|
+
::= { tcpListenerEntry 4 }
|
|
540
|
+
|
|
541
|
+
-- The deprecated TCP Connection table
|
|
542
|
+
|
|
543
|
+
tcpConnTable OBJECT-TYPE
|
|
544
|
+
SYNTAX SEQUENCE OF TcpConnEntry
|
|
545
|
+
MAX-ACCESS not-accessible
|
|
546
|
+
STATUS deprecated
|
|
547
|
+
DESCRIPTION
|
|
548
|
+
"A table containing information about existing IPv4-specific
|
|
549
|
+
TCP connections or listeners. This table has been
|
|
550
|
+
deprecated in favor of the version neutral
|
|
551
|
+
tcpConnectionTable."
|
|
552
|
+
::= { tcp 13 }
|
|
553
|
+
|
|
554
|
+
tcpConnEntry OBJECT-TYPE
|
|
555
|
+
SYNTAX TcpConnEntry
|
|
556
|
+
MAX-ACCESS not-accessible
|
|
557
|
+
STATUS deprecated
|
|
558
|
+
DESCRIPTION
|
|
559
|
+
"A conceptual row of the tcpConnTable containing information
|
|
560
|
+
about a particular current IPv4 TCP connection. Each row
|
|
561
|
+
of this table is transient in that it ceases to exist when
|
|
562
|
+
(or soon after) the connection makes the transition to the
|
|
563
|
+
CLOSED state."
|
|
564
|
+
INDEX { tcpConnLocalAddress,
|
|
565
|
+
tcpConnLocalPort,
|
|
566
|
+
tcpConnRemAddress,
|
|
567
|
+
tcpConnRemPort }
|
|
568
|
+
::= { tcpConnTable 1 }
|
|
569
|
+
|
|
570
|
+
TcpConnEntry ::= SEQUENCE {
|
|
571
|
+
tcpConnState INTEGER,
|
|
572
|
+
tcpConnLocalAddress IpAddress,
|
|
573
|
+
tcpConnLocalPort Integer32,
|
|
574
|
+
tcpConnRemAddress IpAddress,
|
|
575
|
+
tcpConnRemPort Integer32
|
|
576
|
+
|
|
577
|
+
}
|
|
578
|
+
|
|
579
|
+
tcpConnState OBJECT-TYPE
|
|
580
|
+
SYNTAX INTEGER {
|
|
581
|
+
closed(1),
|
|
582
|
+
listen(2),
|
|
583
|
+
synSent(3),
|
|
584
|
+
synReceived(4),
|
|
585
|
+
established(5),
|
|
586
|
+
finWait1(6),
|
|
587
|
+
finWait2(7),
|
|
588
|
+
closeWait(8),
|
|
589
|
+
lastAck(9),
|
|
590
|
+
closing(10),
|
|
591
|
+
timeWait(11),
|
|
592
|
+
deleteTCB(12)
|
|
593
|
+
}
|
|
594
|
+
MAX-ACCESS read-write
|
|
595
|
+
STATUS deprecated
|
|
596
|
+
DESCRIPTION
|
|
597
|
+
"The state of this TCP connection.
|
|
598
|
+
|
|
599
|
+
The only value that may be set by a management station is
|
|
600
|
+
deleteTCB(12). Accordingly, it is appropriate for an agent
|
|
601
|
+
to return a `badValue' response if a management station
|
|
602
|
+
attempts to set this object to any other value.
|
|
603
|
+
|
|
604
|
+
If a management station sets this object to the value
|
|
605
|
+
deleteTCB(12), then the TCB (as defined in [RFC793]) of
|
|
606
|
+
the corresponding connection on the managed node is
|
|
607
|
+
deleted, resulting in immediate termination of the
|
|
608
|
+
connection.
|
|
609
|
+
|
|
610
|
+
As an implementation-specific option, a RST segment may be
|
|
611
|
+
sent from the managed node to the other TCP endpoint (note,
|
|
612
|
+
however, that RST segments are not sent reliably)."
|
|
613
|
+
::= { tcpConnEntry 1 }
|
|
614
|
+
|
|
615
|
+
tcpConnLocalAddress OBJECT-TYPE
|
|
616
|
+
SYNTAX IpAddress
|
|
617
|
+
MAX-ACCESS read-only
|
|
618
|
+
STATUS deprecated
|
|
619
|
+
DESCRIPTION
|
|
620
|
+
"The local IP address for this TCP connection. In the case
|
|
621
|
+
of a connection in the listen state willing to
|
|
622
|
+
accept connections for any IP interface associated with the
|
|
623
|
+
node, the value 0.0.0.0 is used."
|
|
624
|
+
::= { tcpConnEntry 2 }
|
|
625
|
+
|
|
626
|
+
tcpConnLocalPort OBJECT-TYPE
|
|
627
|
+
SYNTAX Integer32 (0..65535)
|
|
628
|
+
MAX-ACCESS read-only
|
|
629
|
+
STATUS deprecated
|
|
630
|
+
DESCRIPTION
|
|
631
|
+
"The local port number for this TCP connection."
|
|
632
|
+
::= { tcpConnEntry 3 }
|
|
633
|
+
|
|
634
|
+
tcpConnRemAddress OBJECT-TYPE
|
|
635
|
+
SYNTAX IpAddress
|
|
636
|
+
MAX-ACCESS read-only
|
|
637
|
+
STATUS deprecated
|
|
638
|
+
DESCRIPTION
|
|
639
|
+
"The remote IP address for this TCP connection."
|
|
640
|
+
::= { tcpConnEntry 4 }
|
|
641
|
+
|
|
642
|
+
tcpConnRemPort OBJECT-TYPE
|
|
643
|
+
SYNTAX Integer32 (0..65535)
|
|
644
|
+
MAX-ACCESS read-only
|
|
645
|
+
STATUS deprecated
|
|
646
|
+
DESCRIPTION
|
|
647
|
+
"The remote port number for this TCP connection."
|
|
648
|
+
::= { tcpConnEntry 5 }
|
|
649
|
+
|
|
650
|
+
-- conformance information
|
|
651
|
+
|
|
652
|
+
tcpMIBConformance OBJECT IDENTIFIER ::= { tcpMIB 2 }
|
|
653
|
+
|
|
654
|
+
tcpMIBCompliances OBJECT IDENTIFIER ::= { tcpMIBConformance 1 }
|
|
655
|
+
tcpMIBGroups OBJECT IDENTIFIER ::= { tcpMIBConformance 2 }
|
|
656
|
+
|
|
657
|
+
-- compliance statements
|
|
658
|
+
|
|
659
|
+
tcpMIBCompliance2 MODULE-COMPLIANCE
|
|
660
|
+
STATUS current
|
|
661
|
+
DESCRIPTION
|
|
662
|
+
"The compliance statement for systems that implement TCP.
|
|
663
|
+
|
|
664
|
+
A number of INDEX objects cannot be
|
|
665
|
+
represented in the form of OBJECT clauses in SMIv2 but
|
|
666
|
+
have the following compliance requirements,
|
|
667
|
+
expressed in OBJECT clause form in this description
|
|
668
|
+
clause:
|
|
669
|
+
|
|
670
|
+
-- OBJECT tcpConnectionLocalAddressType
|
|
671
|
+
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
|
|
672
|
+
-- DESCRIPTION
|
|
673
|
+
-- This MIB requires support for only global IPv4
|
|
674
|
+
|
|
675
|
+
-- and IPv6 address types.
|
|
676
|
+
--
|
|
677
|
+
-- OBJECT tcpConnectionRemAddressType
|
|
678
|
+
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
|
|
679
|
+
-- DESCRIPTION
|
|
680
|
+
-- This MIB requires support for only global IPv4
|
|
681
|
+
-- and IPv6 address types.
|
|
682
|
+
--
|
|
683
|
+
-- OBJECT tcpListenerLocalAddressType
|
|
684
|
+
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
|
|
685
|
+
-- ipv6(2) }
|
|
686
|
+
-- DESCRIPTION
|
|
687
|
+
-- This MIB requires support for only global IPv4
|
|
688
|
+
-- and IPv6 address types. The type unknown also
|
|
689
|
+
-- needs to be supported to identify a special
|
|
690
|
+
-- case in the listener table: a listen using
|
|
691
|
+
-- both IPv4 and IPv6 addresses on the device.
|
|
692
|
+
--
|
|
693
|
+
"
|
|
694
|
+
MODULE -- this module
|
|
695
|
+
MANDATORY-GROUPS { tcpBaseGroup, tcpConnectionGroup,
|
|
696
|
+
tcpListenerGroup }
|
|
697
|
+
GROUP tcpHCGroup
|
|
698
|
+
DESCRIPTION
|
|
699
|
+
"This group is mandatory for systems that are capable
|
|
700
|
+
of receiving or transmitting more than 1 million TCP
|
|
701
|
+
segments per second. 1 million segments per second will
|
|
702
|
+
cause a Counter32 to wrap in just over an hour."
|
|
703
|
+
OBJECT tcpConnectionState
|
|
704
|
+
SYNTAX INTEGER { closed(1), listen(2), synSent(3),
|
|
705
|
+
synReceived(4), established(5),
|
|
706
|
+
finWait1(6), finWait2(7), closeWait(8),
|
|
707
|
+
lastAck(9), closing(10), timeWait(11) }
|
|
708
|
+
MIN-ACCESS read-only
|
|
709
|
+
DESCRIPTION
|
|
710
|
+
"Write access is not required, nor is support for the value
|
|
711
|
+
deleteTCB (12)."
|
|
712
|
+
::= { tcpMIBCompliances 2 }
|
|
713
|
+
|
|
714
|
+
tcpMIBCompliance MODULE-COMPLIANCE
|
|
715
|
+
STATUS deprecated
|
|
716
|
+
DESCRIPTION
|
|
717
|
+
"The compliance statement for IPv4-only systems that
|
|
718
|
+
implement TCP. In order to be IP version independent, this
|
|
719
|
+
compliance statement is deprecated in favor of
|
|
720
|
+
tcpMIBCompliance2. However, agents are still encouraged
|
|
721
|
+
to implement these objects in order to interoperate with
|
|
722
|
+
the deployed base of managers."
|
|
723
|
+
|
|
724
|
+
MODULE -- this module
|
|
725
|
+
MANDATORY-GROUPS { tcpGroup }
|
|
726
|
+
OBJECT tcpConnState
|
|
727
|
+
MIN-ACCESS read-only
|
|
728
|
+
DESCRIPTION
|
|
729
|
+
"Write access is not required."
|
|
730
|
+
::= { tcpMIBCompliances 1 }
|
|
731
|
+
|
|
732
|
+
-- units of conformance
|
|
733
|
+
|
|
734
|
+
tcpGroup OBJECT-GROUP
|
|
735
|
+
OBJECTS { tcpRtoAlgorithm, tcpRtoMin, tcpRtoMax,
|
|
736
|
+
tcpMaxConn, tcpActiveOpens,
|
|
737
|
+
tcpPassiveOpens, tcpAttemptFails,
|
|
738
|
+
tcpEstabResets, tcpCurrEstab, tcpInSegs,
|
|
739
|
+
tcpOutSegs, tcpRetransSegs, tcpConnState,
|
|
740
|
+
tcpConnLocalAddress, tcpConnLocalPort,
|
|
741
|
+
tcpConnRemAddress, tcpConnRemPort,
|
|
742
|
+
tcpInErrs, tcpOutRsts }
|
|
743
|
+
STATUS deprecated
|
|
744
|
+
DESCRIPTION
|
|
745
|
+
"The tcp group of objects providing for management of TCP
|
|
746
|
+
entities."
|
|
747
|
+
::= { tcpMIBGroups 1 }
|
|
748
|
+
|
|
749
|
+
tcpBaseGroup OBJECT-GROUP
|
|
750
|
+
OBJECTS { tcpRtoAlgorithm, tcpRtoMin, tcpRtoMax,
|
|
751
|
+
tcpMaxConn, tcpActiveOpens,
|
|
752
|
+
tcpPassiveOpens, tcpAttemptFails,
|
|
753
|
+
tcpEstabResets, tcpCurrEstab, tcpInSegs,
|
|
754
|
+
tcpOutSegs, tcpRetransSegs,
|
|
755
|
+
tcpInErrs, tcpOutRsts }
|
|
756
|
+
STATUS current
|
|
757
|
+
DESCRIPTION
|
|
758
|
+
"The group of counters common to TCP entities."
|
|
759
|
+
::= { tcpMIBGroups 2 }
|
|
760
|
+
|
|
761
|
+
tcpConnectionGroup OBJECT-GROUP
|
|
762
|
+
OBJECTS { tcpConnectionState, tcpConnectionProcess }
|
|
763
|
+
STATUS current
|
|
764
|
+
DESCRIPTION
|
|
765
|
+
"The group provides general information about TCP
|
|
766
|
+
connections."
|
|
767
|
+
::= { tcpMIBGroups 3 }
|
|
768
|
+
|
|
769
|
+
tcpListenerGroup OBJECT-GROUP
|
|
770
|
+
OBJECTS { tcpListenerProcess }
|
|
771
|
+
STATUS current
|
|
772
|
+
DESCRIPTION
|
|
773
|
+
"This group has objects providing general information about
|
|
774
|
+
TCP listeners."
|
|
775
|
+
::= { tcpMIBGroups 4 }
|
|
776
|
+
|
|
777
|
+
tcpHCGroup OBJECT-GROUP
|
|
778
|
+
OBJECTS { tcpHCInSegs, tcpHCOutSegs }
|
|
779
|
+
STATUS current
|
|
780
|
+
DESCRIPTION
|
|
781
|
+
"The group of objects providing for counters of high speed
|
|
782
|
+
TCP implementations."
|
|
783
|
+
::= { tcpMIBGroups 5 }
|
|
784
|
+
|
|
785
|
+
END
|