[457] | 1 |
|
---|
| 2 | IANATn3270eTC-MIB DEFINITIONS ::= BEGIN
|
---|
| 3 |
|
---|
| 4 | IMPORTS
|
---|
| 5 | MODULE-IDENTITY, mib-2
|
---|
| 6 | FROM SNMPv2-SMI
|
---|
| 7 | TEXTUAL-CONVENTION
|
---|
| 8 | FROM SNMPv2-TC;
|
---|
| 9 |
|
---|
| 10 | ianaTn3270eTcMib MODULE-IDENTITY
|
---|
| 11 | LAST-UPDATED "200005100000Z" -- May 10, 2000
|
---|
| 12 | ORGANIZATION "IANA"
|
---|
| 13 | CONTACT-INFO
|
---|
| 14 | "Internet Assigned Numbers Authority
|
---|
| 15 |
|
---|
| 16 | Postal: ICANN
|
---|
| 17 | 4676 Admiralty Way, Suite 330
|
---|
| 18 | Marina del Rey, CA 90292
|
---|
| 19 |
|
---|
| 20 | Tel: +1 310 823 9358 x20
|
---|
| 21 | E-Mail: iana&iana.org"
|
---|
| 22 | DESCRIPTION
|
---|
| 23 | "This module defines a set of textual conventions
|
---|
| 24 | for use by the TN3270E-MIB and the TN3270E-RT-MIB.
|
---|
| 25 |
|
---|
| 26 | Any additions or changes to the contents of this
|
---|
| 27 | MIB module must first be discussed on the tn3270e
|
---|
| 28 | working group list at: tn3270e&list.nih.gov
|
---|
| 29 | and approved by one of the following TN3270E
|
---|
| 30 | working group contacts:
|
---|
| 31 |
|
---|
| 32 | Ed Bailey (co-chair) - elbailey&us.ibm.com
|
---|
| 33 | Michael Boe (co-chair) - mboe&cisco.com
|
---|
| 34 | Ken White - kennethw&vnet.ibm.com
|
---|
| 35 | Robert Moore - remoore&us.ibm.com
|
---|
| 36 |
|
---|
| 37 | The above list of contacts can be altered with
|
---|
| 38 | the approval of the two co-chairs.
|
---|
| 39 |
|
---|
| 40 | The Textual Conventions defined within this MIB have
|
---|
| 41 | no security issues associated with them unless
|
---|
| 42 | explicitly stated in their corresponding
|
---|
| 43 | DESCRIPTION clause."
|
---|
| 44 |
|
---|
| 45 | -- revision log, in reverse chronological order
|
---|
| 46 |
|
---|
| 47 | REVISION "200005100000Z" -- May 10, 2000
|
---|
| 48 | DESCRIPTION "Fix to import mib-2 instead of experimental."
|
---|
| 49 |
|
---|
| 50 | REVISION "199909011000Z" -- September 1, 1999
|
---|
| 51 | DESCRIPTION
|
---|
| 52 | "Initial version transferred from the TN3270E
|
---|
| 53 | working group to IANA."
|
---|
| 54 |
|
---|
| 55 | ::= { mib-2 61 }
|
---|
| 56 |
|
---|
| 57 |
|
---|
| 58 | -- Textual Conventions
|
---|
| 59 |
|
---|
| 60 | IANATn3270eAddrType ::= TEXTUAL-CONVENTION
|
---|
| 61 | STATUS current
|
---|
| 62 | DESCRIPTION
|
---|
| 63 | "The textual convention for defining the type of a
|
---|
| 64 | client address. The enumeration value unknown(0) is
|
---|
| 65 | also used to indicate that no actual address is present."
|
---|
| 66 | SYNTAX INTEGER {
|
---|
| 67 | unknown(0),
|
---|
| 68 | ipv4(1),
|
---|
| 69 | ipv6(2)
|
---|
| 70 | }
|
---|
| 71 |
|
---|
| 72 | IANATn3270eAddress ::= TEXTUAL-CONVENTION
|
---|
| 73 | STATUS current
|
---|
| 74 | DESCRIPTION
|
---|
| 75 | "Denotes a client address. The type of client address is
|
---|
| 76 | determined by use of the IANATn3270eAddrType textual
|
---|
| 77 | convention.
|
---|
| 78 | The length in octets of a IANATn3270eAddress object is:
|
---|
| 79 |
|
---|
| 80 | IANATn3270eAddrType Address Length
|
---|
| 81 | +++++++++++++++++++ ++++++++++++++
|
---|
| 82 | unknown(0) not specified or unknown; the
|
---|
| 83 | actual length of the
|
---|
| 84 | IANATn3270eAddress octet string
|
---|
| 85 | indicates if an address
|
---|
| 86 | is present
|
---|
| 87 | ipv4(1) 4 OCTETS
|
---|
| 88 | ipv6(2) 16 OCTETS
|
---|
| 89 |
|
---|
| 90 | This textual convention is similar to the TAddress
|
---|
| 91 | TC defined by RFC1903 except that it allows a
|
---|
| 92 | zero-length octet string and is not a full transport
|
---|
| 93 | layer address."
|
---|
| 94 | SYNTAX OCTET STRING (SIZE (0..255))
|
---|
| 95 |
|
---|
| 96 | IANATn3270eClientType ::= TEXTUAL-CONVENTION
|
---|
| 97 | STATUS current
|
---|
| 98 | DESCRIPTION
|
---|
| 99 | "The textual convention for defining the set of
|
---|
| 100 | enumerations used by tn3270eTcpConnClientIdFormat
|
---|
| 101 | in the TN3270E-MIB:
|
---|
| 102 |
|
---|
| 103 | ENUMERATION OCTETs DESCRIPTION
|
---|
| 104 |
|
---|
| 105 | none(1) 0 Not specified
|
---|
| 106 | other(2) 1..512 Implementation specific
|
---|
| 107 | ipv4(3) 6 4-octet IP Address plus
|
---|
| 108 | 2-octet TCP Port
|
---|
| 109 | ipv6(4) 18 16-octet IPv6 Address
|
---|
| 110 | plus 2-octet TCP Port
|
---|
| 111 | domainName(5) 1..512 The DNS name of a
|
---|
| 112 | client.
|
---|
| 113 | truncDomainName(6) 1..512 The (truncated) DNS name
|
---|
| 114 | of a client.
|
---|
| 115 | string(7) 1..512 Unknown Utf8String
|
---|
| 116 | certificate(8) 1..512 certificate
|
---|
| 117 | userId(9) 1..8 Client's userid
|
---|
| 118 | x509dn(10) 1..512 X.509 Distinguished Name
|
---|
| 119 |
|
---|
| 120 | Representation of a certificate(8) may be lead to
|
---|
| 121 | a security exposure and is NOT RECOMMENDED without
|
---|
| 122 | adequate security."
|
---|
| 123 | SYNTAX INTEGER {
|
---|
| 124 | none(1),
|
---|
| 125 | other(2),
|
---|
| 126 | ipv4(3),
|
---|
| 127 | ipv6(4),
|
---|
| 128 | domainName(5),
|
---|
| 129 | truncDomainName(6),
|
---|
| 130 | string(7),
|
---|
| 131 | certificate(8),
|
---|
| 132 | userId(9),
|
---|
| 133 | x509dn(10)
|
---|
| 134 | }
|
---|
| 135 |
|
---|
| 136 | IANATn3270Functions ::= TEXTUAL-CONVENTION
|
---|
| 137 | STATUS current
|
---|
| 138 | DESCRIPTION
|
---|
| 139 | "This textual convention reflects the current set of
|
---|
| 140 | TN3270 and TN3270E functions that can be negotiated
|
---|
| 141 | between a server and its client:
|
---|
| 142 |
|
---|
| 143 | RFC856
|
---|
| 144 | transmitBinary The sender of this command REQUESTS
|
---|
| 145 | permission to begin transmitting, or
|
---|
| 146 | confirms that it will now begin
|
---|
| 147 | transmitting characters which are to
|
---|
| 148 | be interpreted as 8 bits of binary
|
---|
| 149 | data by the receiver of the data.
|
---|
| 150 | RFC860
|
---|
| 151 | timingMark The sender of this command REQUESTS
|
---|
| 152 | that the receiver of this command
|
---|
| 153 | return a WILL TIMING-MARK in the data
|
---|
| 154 | stream at the 'appropriate place'.
|
---|
| 155 | RFC885
|
---|
| 156 | endOfRecord The sender of this command requests
|
---|
| 157 | permission to begin transmission of
|
---|
| 158 | the Telnet END-OF-RECORD (EOR) code
|
---|
| 159 | when transmitting data characters, or
|
---|
| 160 | the sender of this command confirms it
|
---|
| 161 | will now begin transmission of EORs
|
---|
| 162 | with transmitted data characters.
|
---|
| 163 | RFC1091
|
---|
| 164 | terminalType Sender is willing to send terminal
|
---|
| 165 | type information in a subsequent
|
---|
| 166 | sub-negotiation.
|
---|
| 167 |
|
---|
| 168 | RFC1041
|
---|
| 169 | tn3270Regime Sender is willing to send list of
|
---|
| 170 | supported 3270 Regimes in a
|
---|
| 171 | subsequent sub-negotiation.
|
---|
| 172 | RFC2355
|
---|
| 173 | scsCtlCodes (Printer sessions only). Allows the
|
---|
| 174 | use of the SNA Character Stream (SCS)
|
---|
| 175 | and SCS control codes on the session.
|
---|
| 176 | SCS is used with LU type 1 SNA sessions.
|
---|
| 177 | dataStreamCtl (Printer sessions only). Allows the use
|
---|
| 178 | of the standard 3270 data stream. This
|
---|
| 179 | corresponds to LU type 3 SNA sessions.
|
---|
| 180 | responses Provides support for positive and
|
---|
| 181 | negative response handling. Allows the
|
---|
| 182 | server to reflect to the client any and
|
---|
| 183 | all definite, exception, and no response
|
---|
| 184 | requests sent by the host application.
|
---|
| 185 | bindImage Allows the server to send the SNA Bind
|
---|
| 186 | image and Unbind notification to the
|
---|
| 187 | client.
|
---|
| 188 | sysreq Allows the client and server to emulate
|
---|
| 189 | some (or all, depending on the server) of
|
---|
| 190 | the functions of the SYSREQ key in an SNA
|
---|
| 191 | environment."
|
---|
| 192 | SYNTAX BITS {
|
---|
| 193 | transmitBinary(0),-- rfc856
|
---|
| 194 | timemark(1), -- rfc860
|
---|
| 195 | endOfRecord(2), -- rfc885
|
---|
| 196 | terminalType(3), -- rfc1091
|
---|
| 197 | tn3270Regime(4), -- rfc1041
|
---|
| 198 | scsCtlCodes(5), -- rfc2355
|
---|
| 199 | dataStreamCtl(6), -- rfc2355
|
---|
| 200 | responses(7), -- rfc2355
|
---|
| 201 | bindImage(8), -- rfc2355
|
---|
| 202 | sysreq(9) -- rfc2355
|
---|
| 203 | }
|
---|
| 204 |
|
---|
| 205 | IANATn3270ResourceType ::= TEXTUAL-CONVENTION
|
---|
| 206 | STATUS current
|
---|
| 207 | DESCRIPTION
|
---|
| 208 | "The type of resource defined by a resource pool. Refer
|
---|
| 209 | to tn3270eResPoolTable."
|
---|
| 210 | SYNTAX INTEGER {
|
---|
| 211 | other(1),
|
---|
| 212 | terminal(2),
|
---|
| 213 | printer(3),
|
---|
| 214 | terminalOrPrinter(4)
|
---|
| 215 | }
|
---|
| 216 |
|
---|
| 217 | IANATn3270DeviceType ::= TEXTUAL-CONVENTION
|
---|
| 218 | STATUS current
|
---|
| 219 | DESCRIPTION
|
---|
| 220 | "This textual convention defines the list of device
|
---|
| 221 | types that can be set, as defined by RFC 2355."
|
---|
| 222 | SYNTAX INTEGER {
|
---|
| 223 | -- terminals
|
---|
| 224 | ibm3278d2(1), -- (24 row x 80 col display)
|
---|
| 225 | ibm3278d2E(2), -- (24 row x 80 col display)
|
---|
| 226 | ibm3278d3(3), -- (32 row x 80 col display)
|
---|
| 227 | ibm3278d3E(4), -- (32 row x 80 col display)
|
---|
| 228 | ibm3278d4(5), -- (43 row x 80 col display)
|
---|
| 229 | ibm3278d4E(6), -- (43 row x 80 col display)
|
---|
| 230 | ibm3278d5(7), -- (27 row x 132 col display)
|
---|
| 231 | ibm3278d5E(8), -- (27 row x 132 col display)
|
---|
| 232 | ibmDynamic(9), -- (no pre-defined display size)
|
---|
| 233 |
|
---|
| 234 | -- printers
|
---|
| 235 | ibm3287d1(10),
|
---|
| 236 |
|
---|
| 237 | unknown(100)
|
---|
| 238 | }
|
---|
| 239 |
|
---|
| 240 | IANATn3270eLogData ::= TEXTUAL-CONVENTION
|
---|
| 241 | STATUS current
|
---|
| 242 | DESCRIPTION
|
---|
| 243 | "An octet string representing log data as pertaining to
|
---|
| 244 | either a TN3270 or TN3270E Session as reported from a
|
---|
| 245 | TN3270E Server. Log data is stored in an octet string
|
---|
| 246 | in time order (from earliest to latest).
|
---|
| 247 |
|
---|
| 248 | Each log element has the following form:
|
---|
| 249 |
|
---|
| 250 | +------+----+---------+------------+
|
---|
| 251 | !length!type!TimeStamp! data !
|
---|
| 252 | +------+----+---------+------------+
|
---|
| 253 |
|
---|
| 254 | where
|
---|
| 255 |
|
---|
| 256 | length = one-octet length of the data portion of the
|
---|
| 257 | trace element, not including the length,
|
---|
| 258 | type, and TimeStamp fields
|
---|
| 259 | type = one-octet code point characterizing the data.
|
---|
| 260 | TimeStamp = A 4-octet field representing the number of
|
---|
| 261 | TimeTicks since the TN3270E server was last
|
---|
| 262 | activated. The server's last activation time
|
---|
| 263 | is available in the tn3270eSrvrConfLastActTime
|
---|
| 264 | object in the TN3270E MIB, which has the
|
---|
| 265 | syntax DateAndTime.
|
---|
| 266 | data = initial part of a PDU.
|
---|
| 267 |
|
---|
| 268 | length type
|
---|
| 269 |
|
---|
| 270 | 0-255 x'00' - unknown
|
---|
| 271 | 0 x'01' - inactivity timer expired
|
---|
| 272 | 0 x'02' - dynamic timer expired
|
---|
| 273 | 0 x'03' - actlu req
|
---|
| 274 | 0 x'04' - bind req
|
---|
| 275 | 0 x'05' - clear req
|
---|
| 276 | 0 x'06' - dactlu req
|
---|
| 277 | 0 x'07' - warm actpu req
|
---|
| 278 | 0 x'08' - sdt req
|
---|
| 279 | 0 x'09' - unbind req
|
---|
| 280 | 0 x'0A' - notify resp
|
---|
| 281 | 0 x'0B' - reply PSID neg rsp
|
---|
| 282 | 0 x'0C' - reply PSID pos rsp
|
---|
| 283 | 0 x'0D' - unbind rsp
|
---|
| 284 | 0 x'0E' - hierarchical reset
|
---|
| 285 | 0 x'0F' - client connect req
|
---|
| 286 | 0 x'10' - client disconnect req
|
---|
| 287 | 0 x'11' - timingmark received
|
---|
| 288 | 0 x'12' - flowControl timer expired
|
---|
| 289 | 0 x'13' - neg rsp to host
|
---|
| 290 | 0 x'14' - neg rsp from host
|
---|
| 291 | 0 x'15' - data contention
|
---|
| 292 | 0 x'16' - no buffer to send SNA data
|
---|
| 293 | 0 x'17' - receive response while inbound
|
---|
| 294 | 0 x'18' - client protocol error
|
---|
| 295 | 0 x'19' - badClientSequenceReceived
|
---|
| 296 | 1-255 x'1A' - utf8String
|
---|
| 297 | 2 x'1B' - hexCode, implementation dependent
|
---|
| 298 |
|
---|
| 299 | Log element entries have a minimum length of 6 octets.
|
---|
| 300 | The zero-length string indicates that no log data is
|
---|
| 301 | available."
|
---|
| 302 | SYNTAX OCTET STRING (SIZE (0 | 6..2048))
|
---|
| 303 |
|
---|
| 304 | END
|
---|
| 305 |
|
---|
| 306 |
|
---|