idnits 2.17.1 draft-ietf-charmib-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (26 May 1994) is 10927 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '5' is defined on line 823, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 827, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 830, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1442 (ref. '1') (Obsoleted by RFC 1902) ** Downref: Normative reference to an Historic RFC: RFC 1445 (ref. '3') ** Obsolete normative reference: RFC 1448 (ref. '4') (Obsoleted by RFC 1905) ** Obsolete normative reference: RFC 1573 (ref. '5') (Obsoleted by RFC 2233) -- Possible downref: Non-RFC (?) normative reference: ref. '6' -- Possible downref: Non-RFC (?) normative reference: ref. '7' Summary: 14 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Character MIB 3 26 May 1994 5 Bob Stewart 6 Xyplex, Inc. 7 rlstewart@eng.xyplex.com 9 11 Status of this Memo 13 This document is an Internet Draft. Internet Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its Areas, and 15 its Working Groups. Note that other groups may also distribute working 16 documents as Internet Drafts. 18 Internet Drafts are valid for a maximum of six months and may be 19 updated, replaced, or obsoleted by other documents at any time. It is 20 inappropriate to use Internet Drafts as reference material or to cite 21 them other than as a "work in progress". 23 draft Character MIB 26 May 1994 25 1. Introduction 27 This memo defines an extension to the Management Information Base (MIB) 28 for use with network management protocols in the Internet community. In 29 particular, it defines objects for the management of character stream 30 devices. 32 draft Character MIB 26 May 1994 34 2. The SNMPv2 Network Management Framework 36 The SNMPv2 Network Management Framework consists of four major 37 components. They are: 39 o RFC 1442 [1] which defines the SMI, the mechanisms used for 40 describing and naming objects for the purpose of management. 42 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 43 objects for the Internet suite of protocols. 45 o RFC 1445 [3] which defines the administrative and other 46 architectural aspects of the framework. 48 o RFC 1448 [4] which defines the protocol used for network access to 49 managed objects. 51 The Framework permits new objects to be defined for the purpose of 52 experimentation and evaluation. 54 2.1. Object Definitions 56 Managed objects are accessed via a virtual information store, termed the 57 Management Information Base or MIB. Objects in the MIB are defined 58 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 59 SMI. In particular, each object object type is named by an OBJECT 60 IDENTIFIER, an administratively assigned name. The object type together 61 with an object instance serves to uniquely identify a specific 62 instantiation of the object. For human convenience, we often use a 63 textual string, termed the descriptor, to refer to the object type. 65 draft Character MIB 26 May 1994 67 3. Overview 69 The Character MIB applies to ports that carry a character stream, 70 whether physical or virtual, serial or parallel, synchronous or 71 asynchronous. The most common example of a character stream device is a 72 hardware terminal port with an RS-232 interface. Another common 73 hardware example is a parallel printer port, say with a Centronics 74 interface. The concept also includes virtual terminal ports, such as a 75 software connection point for a remote console. 77 The Character MIB is mandatory for all systems that offer character 78 stream ports. This includes, for example, terminal servers, general- 79 purpose time-sharing hosts, and even such systems as a bridge with a 80 (virtual) console port. It may or may not include character ports that 81 do not support network sessions, depending on the system's needs. 83 The Character MIB's central abstraction is a port. Physical ports have 84 a one-to-one correspondence with hardware ports. Virtual ports are 85 software entities analogous to physical ports, but with no hardware 86 connector. 88 Each port supports one or more sessions. A session represents a virtual 89 connection that carries characters between the port and some partner. 90 Sessions typically operate over a stack of network protocols. A typical 91 session, for example, uses Telnet over TCP. 93 The MIB comprises one base object and two tables, detailed in the 94 following sections. The tables contain objects for ports and sessions. 96 The MIB intentionally contains no distinction between what is often 97 called permanent and operational or volatile data bases. For the 98 purposes of this MIB, handling of such distinctions is implementation 99 specific. 101 3.1. Relationship to Interface MIB 103 The Character MIB does not relate directly to the Interface MIB [1], 104 since it is not intrinsically a network interface. On the other hand, 105 in most implementations where it is present, it will be above a physical 106 sublayer interface, such as the RS-232-like [2] or Parallel-printer-like 107 [3] MIBs. Such physical interfaces typically are represented by a row 108 in the interface table (ifTable), identified by a value of ifIndex. 110 draft Character MIB 26 May 1994 112 4. Definitions 114 CHARACTER-MIB DEFINITIONS ::= BEGIN 116 IMPORTS 117 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 118 Counter32, Integer32, Gauge32, TimeTicks 119 FROM SNMPv2-SMI 120 AutonomousType, InstancePointer 121 FROM SNMPv2-TC 122 InterfaceIndex 123 FROM IF-MIB 124 transmission, mib-2 125 FROM RFC1213-MIB 126 MODULE-COMPLIANCE, OBJECT-GROUP 127 FROM SNMPv2-CONF; 129 char MODULE-IDENTITY 130 LAST-UPDATED "9405261700Z" 131 ORGANIZATION "IETF Character MIB Working Group" 132 CONTACT-INFO 133 " Bob Stewart 134 Postal: Xyplex, Inc. 135 295 Foster Street 136 Littleton, MA 01460 138 Tel: 508-952-4816 139 Fax: 508-952-4887 140 E-mail: rlstewart@eng.xyplex.com" 141 DESCRIPTION 142 "The MIB module for character stream devices." 143 ::= { mib-2 19 } 145 PortIndex ::= TEXTUAL-CONVENTION 146 DISPLAY-HINT "d" 147 STATUS current 148 DESCRIPTION 149 "A unique value, greater than zero, for each 150 character port in the managed system. It is 151 recommended that values are assigned contiguously 152 starting from 1. The value for each interface sub- 153 layer must remain constant at least from one re- 154 initialization of the entity's network management 155 system to the next re-initialization. 157 draft Character MIB 26 May 1994 159 In a system where the character ports are attached 160 to hardware represented by an ifIndex, it is 161 conventional, but not required, to make the 162 character port index equal to the corresponding 163 ifIndex." 164 SYNTAX Integer32 166 draft Character MIB 26 May 1994 168 -- Generic Character information 170 charNumber OBJECT-TYPE 171 SYNTAX Integer32 172 MAX-ACCESS read-only 173 STATUS current 174 DESCRIPTION 175 "The number of entries in charPortTable, regardless 176 of their current state." 177 ::= { char 1 } 179 -- the Character Port table 181 charPortTable OBJECT-TYPE 182 SYNTAX SEQUENCE OF CharPortEntry 183 MAX-ACCESS not-accessible 184 STATUS current 185 DESCRIPTION 186 "A list of port entries. The number of entries is 187 given by the value of charNumber." 188 ::= { char 2 } 190 charPortEntry OBJECT-TYPE 191 SYNTAX CharPortEntry 192 MAX-ACCESS not-accessible 193 STATUS current 194 DESCRIPTION 195 "Status and parameter values for a character port." 196 INDEX { charPortIndex } 197 ::= { charPortTable 1 } 199 CharPortEntry ::= 200 SEQUENCE { 201 charPortIndex 202 PortIndex, 203 charPortName 204 DisplayString, 205 charPortType 206 INTEGER, 207 charPortHardware 208 AutonomousType, 209 charPortReset 210 INTEGER, 211 charPortAdminStatus 213 draft Character MIB 26 May 1994 215 INTEGER, 216 charPortOperStatus 217 INTEGER, 218 charPortLastChange 219 TimeTicks, 220 charPortInFlowType 221 INTEGER, 222 charPortOutFlowType 223 INTEGER, 224 charPortInFlowState 225 INTEGER, 226 charPortOutFlowState 227 INTEGER, 228 charPortInCharacters 229 Counter32, 230 charPortOutCharacters 231 Counter32, 232 charPortAdminOrigin 233 INTEGER, 234 charPortSessionMaximum 235 INTEGER, 236 charPortSessionNumber 237 Gauge32, 238 charPortSessionIndex 239 INTEGER, 240 charPortInFlowTypes 241 OCTET STRING, 242 charPortOutFlowTypes 243 OCTET STRING, 244 charPortLowerIfIndex 245 InterfaceIndex 246 } 248 charPortIndex OBJECT-TYPE 249 SYNTAX PortIndex 250 MAX-ACCESS read-only 251 STATUS current 252 DESCRIPTION 253 "A unique value for each character port, perhaps 254 corresponding to the same value of ifIndex when the 255 character port is associated with a hardware port 256 represented by an ifIndex." 257 ::= { charPortEntry 1 } 259 charPortName OBJECT-TYPE 260 draft Character MIB 26 May 1994 262 SYNTAX DisplayString (SIZE (0..32)) 263 MAX-ACCESS read-write 264 STATUS current 265 DESCRIPTION 266 "An administratively assigned name for the port, 267 typically with some local significance." 268 ::= { charPortEntry 2 } 270 charPortType OBJECT-TYPE 271 SYNTAX INTEGER { physical(1), virtual(2) } 272 MAX-ACCESS read-only 273 STATUS current 274 DESCRIPTION 275 "The port's type, 'physical' if the port represents 276 an external hardware connector, 'virtual' if it does 277 not." 278 ::= { charPortEntry 3 } 280 charPortHardware OBJECT-TYPE 281 SYNTAX AutonomousType 282 MAX-ACCESS read-only 283 STATUS current 284 DESCRIPTION 285 "A reference to hardware MIB definitions specific to 286 a physical port's external connector. For example, 287 if the connector is RS-232, then the value of this 288 object refers to a MIB sub-tree defining objects 289 specific to RS-232. If an agent is not configured 290 to have such values, the agent returns the object 291 identifier: 293 nullHardware OBJECT IDENTIFIER ::= { 0 0 } 294 " 295 ::= { charPortEntry 4 } 297 charPortReset OBJECT-TYPE 298 SYNTAX INTEGER { ready(1), execute(2) } 299 MAX-ACCESS read-write 300 STATUS current 301 DESCRIPTION 302 "A control to force the port into a clean, initial 303 state, both hardware and software, disconnecting all 304 the port's existing sessions. In response to a 305 get-request or get-next-request, the agent always 306 returns 'ready' as the value. Setting the value to 308 draft Character MIB 26 May 1994 310 'execute' causes a reset." 311 ::= { charPortEntry 5 } 313 charPortAdminStatus OBJECT-TYPE 314 SYNTAX INTEGER { enabled(1), disabled(2), off(3), 315 maintenance(4) } 316 MAX-ACCESS read-write 317 STATUS current 318 DESCRIPTION 319 "The port's desired state, independent of flow 320 control. 'enabled' indicates that the port is 321 allowed to pass characters and form new sessions. 322 'disabled' indicates that the port is allowed to 323 pass characters but not form new sessions. 'off' 324 indicates that the port is not allowed to pass 325 characters or have any sessions. 'maintenance' 326 indicates a maintenance mode, exclusive of normal 327 operation, such as running a test. 329 'enabled' corresponds to ifAdminStatus 'up'. 330 'disabled' and 'off' correspond to ifAdminStatus 331 'down'. 'maintenance' corresponds to ifAdminStatus 332 'test'." 333 ::= { charPortEntry 6 } 335 charPortOperStatus OBJECT-TYPE 336 SYNTAX INTEGER { up(1), down(2), 337 maintenance(3), absent(4), active(5) } 338 MAX-ACCESS read-only 339 STATUS current 340 DESCRIPTION 341 "The port's actual, operational state, independent 342 of flow control. 'up' indicates able to function 343 normally. 'down' indicates inability to function 344 for administrative or operational reasons. 345 'maintenance' indicates a maintenance mode, 346 exclusive of normal operation, such as running a 347 test. 'absent' indicates that port hardware is not 348 present. 'active' indicates up with a user present 349 (e.g. logged in). 351 'up' and 'active' correspond to ifOperStatus 'up'. 352 'down' and 'absent' correspond to ifOperStatus 353 'down'. 'maintenance' corresponds to ifOperStatus 354 'test'." 356 draft Character MIB 26 May 1994 358 ::= { charPortEntry 7 } 360 charPortLastChange OBJECT-TYPE 361 SYNTAX TimeTicks 362 MAX-ACCESS read-only 363 STATUS current 364 DESCRIPTION 365 "The value of sysUpTime at the time the port entered 366 its current operational state. If the current state 367 was entered prior to the last reinitialization of 368 the local network management subsystem, then this 369 object contains a zero value." 370 ::= { charPortEntry 8 } 372 -- charPortInFlowType is deprecated in favor of 373 -- charPortInFlowTypes 375 charPortInFlowType OBJECT-TYPE 376 SYNTAX INTEGER { none(1), xonXoff(2), hardware(3), 377 ctsRts(4), dsrDtr(5) } 378 MAX-ACCESS read-write 379 STATUS deprecated 380 DESCRIPTION 381 "The port's type of input flow control. 'none' 382 indicates no flow control at this level or below. 383 'xonXoff' indicates software flow control by 384 recognizing XON and XOFF characters. 'hardware' 385 indicates flow control delegated to the lower level, 386 for example a parallel port. 388 'ctsRts' and 'dsrDtr' are specific to RS-232-like 389 ports. Although not architecturally pure, they are 390 included here for simplicity's sake." 391 ::= { charPortEntry 9 } 393 -- charPortOutFlowType is deprecated in favor of 394 -- charPortOutFlowTypes 396 charPortOutFlowType OBJECT-TYPE 397 SYNTAX INTEGER { none(1), xonXoff(2), hardware(3), 398 ctsRts(4), dsrDtr(5) } 399 MAX-ACCESS read-write 400 STATUS deprecated 401 DESCRIPTION 402 "The port's type of output flow control. 'none' 404 draft Character MIB 26 May 1994 406 indicates no flow control at this level or below. 407 'xonXoff' indicates software flow control by 408 recognizing XON and XOFF characters. 'hardware' 409 indicates flow control delegated to the lower level, 410 for example a parallel port. 412 'ctsRts' and 'dsrDtr' are specific to RS-232-like 413 ports. Although not architecturally pure, they are 414 included here for simplicy's sake." 415 ::= { charPortEntry 10 } 417 charPortInFlowState OBJECT-TYPE 418 SYNTAX INTEGER { none(1), unknown(2), stop(3), go(4) } 419 MAX-ACCESS read-only 420 STATUS current 421 DESCRIPTION 422 "The current operational state of input flow control 423 on the port. 'none' indicates not applicable. 424 'unknown' indicates this level does not know. 425 'stop' indicates flow not allowed. 'go' indicates 426 flow allowed." 427 ::= { charPortEntry 11 } 429 charPortOutFlowState OBJECT-TYPE 430 SYNTAX INTEGER { none(1), unknown(2), stop(3), go(4) } 431 MAX-ACCESS read-only 432 STATUS current 433 DESCRIPTION 434 "The current operational state of output flow 435 control on the port. 'none' indicates not 436 applicable. 'unknown' indicates this level does not 437 know. 'stop' indicates flow not allowed. 'go' 438 indicates flow allowed." 439 ::= { charPortEntry 12 } 441 charPortInCharacters OBJECT-TYPE 442 SYNTAX Counter32 443 MAX-ACCESS read-only 444 STATUS current 445 DESCRIPTION 446 "Total number of characters detected as input from 447 the port since system re-initialization and while 448 the port operational state was 'up', 'active', or 449 'maintenance', including, for example, framing, flow 450 control (i.e. XON and XOFF), each occurrence of a 452 draft Character MIB 26 May 1994 454 BREAK condition, locally-processed input, and input 455 sent to all sessions." 456 ::= { charPortEntry 13 } 458 charPortOutCharacters OBJECT-TYPE 459 SYNTAX Counter32 460 MAX-ACCESS read-only 461 STATUS current 462 DESCRIPTION 463 "Total number of characters detected as output to 464 the port since system re-initialization and while 465 the port operational state was 'up', 'active', or 466 'maintenance', including, for example, framing, flow 467 control (i.e. XON and XOFF), each occurrence of a 468 BREAK condition, locally-created output, and output 469 received from all sessions." 470 ::= { charPortEntry 14 } 472 charPortAdminOrigin OBJECT-TYPE 473 SYNTAX INTEGER { dynamic(1), network(2), local(3), 474 none(4) } 475 MAX-ACCESS read-write 476 STATUS current 477 DESCRIPTION 478 "The administratively allowed origin for 479 establishing session on the port. 'dynamic' allows 480 'network' or 'local' session establishment. 'none' 481 disallows session establishment." 482 ::= { charPortEntry 15 } 484 charPortSessionMaximum OBJECT-TYPE 485 SYNTAX INTEGER (-1..2147483647) 486 MAX-ACCESS read-write 487 STATUS current 488 DESCRIPTION 489 "The maximum number of concurrent sessions allowed 490 on the port. A value of -1 indicates no maximum. 491 Setting the maximum to less than the current number 492 of sessions has unspecified results." 493 ::= { charPortEntry 16 } 495 charPortSessionNumber OBJECT-TYPE 496 SYNTAX Gauge32 497 MAX-ACCESS read-only 498 STATUS current 500 draft Character MIB 26 May 1994 502 DESCRIPTION 503 "The number of open sessions on the port that are in 504 the connecting, connected, or disconnecting state." 505 ::= { charPortEntry 17 } 507 charPortSessionIndex OBJECT-TYPE 508 SYNTAX INTEGER (0..2147483647) 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The value of charSessIndex for the port's first or 513 only active session. If the port has no active 514 session, the agent returns the value zero." 515 ::= { charPortEntry 18 } 517 charPortInFlowTypes OBJECT-TYPE 518 SYNTAX OCTET STRING (SIZE (1)) 519 MAX-ACCESS read-write 520 STATUS current 521 DESCRIPTION 522 "The port's types of input flow control at the 523 software level. Hardware-level flow control is 524 independently controlled by the appropriate 525 hardware-level MIB. 527 A value of zero indicates no flow control. 528 Depending on the specific implementation, any or 529 all combinations of flow control may be chosen by 530 adding the values: 532 128 xonXoff, recognizing XON and XOFF characters 533 64 enqHost, ENQ/ACK to allow input to host 534 32 enqTerm, ACK to allow output to port 535 " 536 ::= { charPortEntry 19 } 538 charPortOutFlowTypes OBJECT-TYPE 539 SYNTAX OCTET STRING (SIZE (1)) 540 MAX-ACCESS read-write 541 STATUS current 542 DESCRIPTION 543 "The port's types of output flow control at the 544 software level. Hardware-level flow control is 545 independently controlled by the appropriate 546 hardware-level MIB. 548 draft Character MIB 26 May 1994 550 A value of zero indicates no flow control. 551 Depending on the specific implementation, any or 552 all combinations of flow control may be chosen by 553 adding the values: 555 128 xonXoff, recognizing XON and XOFF characters 556 64 enqHost, ENQ/ACK to allow input to host 557 32 enqTerm, ACK to allow output to port 558 " 559 ::= { charPortEntry 20 } 561 charPortLowerIfIndex OBJECT-TYPE 562 SYNTAX InterfaceIndex 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "The ifIndex value of the lower level hardware supporting 567 this character port, zero if none." 568 ::= { charPortEntry 21 } 570 -- the Character Session table 572 charSessTable OBJECT-TYPE 573 SYNTAX SEQUENCE OF CharSessEntry 574 MAX-ACCESS not-accessible 575 STATUS current 576 DESCRIPTION 577 "A list of port session entries." 578 ::= { char 3 } 580 charSessEntry OBJECT-TYPE 581 SYNTAX CharSessEntry 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "Status and parameter values for a character port 586 session." 587 INDEX { charSessPortIndex, charSessIndex } 588 ::= { charSessTable 1 } 590 CharSessEntry ::= 591 SEQUENCE { 592 charSessPortIndex 593 PortIndex, 595 draft Character MIB 26 May 1994 597 charSessIndex 598 INTEGER, 599 charSessKill 600 INTEGER, 601 charSessState 602 INTEGER, 603 charSessProtocol 604 AutonomousType, 605 charSessOperOrigin 606 INTEGER, 607 charSessInCharacters 608 Counter32, 609 charSessOutCharacters 610 Counter32, 611 charSessConnectionId 612 InstancePointer, 613 charSessStartTime 614 TimeTicks 615 } 617 charSessPortIndex OBJECT-TYPE 618 SYNTAX PortIndex 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The value of charPortIndex for the port to which 623 this session belongs." 624 ::= { charSessEntry 1 } 626 charSessIndex OBJECT-TYPE 627 SYNTAX INTEGER (1..2147483647) 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "The session index in the context of the port, a 632 non-zero positive integer. Session indexes within a 633 port need not be sequential. Session indexes may be 634 reused for different ports. For example, port 1 and 635 port 3 may both have a session 2 at the same time. 636 Session indexes may have any valid integer value, 637 with any meaning convenient to the agent 638 implementation." 639 ::= { charSessEntry 2 } 641 charSessKill OBJECT-TYPE 642 draft Character MIB 26 May 1994 644 SYNTAX INTEGER { ready(1), execute(2) } 645 MAX-ACCESS read-write 646 STATUS current 647 DESCRIPTION 648 "A control to terminate the session. In response to 649 a get-request or get-next-request, the agent always 650 returns 'ready' as the value. Setting the value to 651 'execute' causes termination." 652 ::= { charSessEntry 3 } 654 charSessState OBJECT-TYPE 655 SYNTAX INTEGER { connecting(1), connected(2), 656 disconnecting(3) } 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "The current operational state of the session, 661 disregarding flow control. 'connected' indicates 662 that character data could flow on the network side 663 of session. 'connecting' indicates moving from 664 nonexistent toward 'connected'. 'disconnecting' 665 indicates moving from 'connected' or 'connecting' to 666 nonexistent." 667 ::= { charSessEntry 4 } 669 charSessProtocol OBJECT-TYPE 670 SYNTAX AutonomousType 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "The network protocol over which the session is 675 running. Other OBJECT IDENTIFIER values may be 676 defined elsewhere, in association with specific 677 protocols. However, this document assigns those of 678 known interest as of this writing." 679 ::= { charSessEntry 5 } 681 wellKnownProtocols OBJECT IDENTIFIER ::= { char 4 } 683 protocolOther OBJECT IDENTIFIER ::= { wellKnownProtocols 1 } 684 protocolTelnet OBJECT IDENTIFIER ::= { wellKnownProtocols 2 } 685 protocolRlogin OBJECT IDENTIFIER ::= { wellKnownProtocols 3 } 686 protocolLat OBJECT IDENTIFIER ::= { wellKnownProtocols 4 } 687 protocolX29 OBJECT IDENTIFIER ::= { wellKnownProtocols 5 } 688 protocolVtp OBJECT IDENTIFIER ::= { wellKnownProtocols 6 } 689 draft Character MIB 26 May 1994 691 charSessOperOrigin OBJECT-TYPE 692 SYNTAX INTEGER { unknown(1), network(2), local(3) } 693 MAX-ACCESS read-only 694 STATUS current 695 DESCRIPTION 696 "The session's source of establishment." 697 ::= { charSessEntry 6 } 699 charSessInCharacters OBJECT-TYPE 700 SYNTAX Counter32 701 MAX-ACCESS read-only 702 STATUS current 703 DESCRIPTION 704 "This session's subset of charPortInCharacters." 705 ::= { charSessEntry 7 } 707 charSessOutCharacters OBJECT-TYPE 708 SYNTAX Counter32 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "This session's subset of charPortOutCharacters." 713 ::= { charSessEntry 8 } 715 charSessConnectionId OBJECT-TYPE 716 SYNTAX InstancePointer 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "A reference to additional local MIB information. 721 This should be the highest available related MIB, 722 corresponding to charSessProtocol, such as Telnet. 723 For example, the value for a TCP connection (in the 724 absence of a Telnet MIB) is the object identifier of 725 tcpConnState. If an agent is not configured to have 726 such values, the agent returns the object 727 identifier: 729 nullConnectionId OBJECT IDENTIFIER ::= { 0 0 } 730 " 731 ::= { charSessEntry 9 } 733 charSessStartTime OBJECT-TYPE 734 SYNTAX TimeTicks 735 MAX-ACCESS read-only 737 draft Character MIB 26 May 1994 739 STATUS current 740 DESCRIPTION 741 "The value of sysUpTime in MIB-2 when the session 742 entered connecting state." 743 ::= { charSessEntry 10 } 745 draft Character MIB 26 May 1994 747 -- conformance information 749 charConformance OBJECT IDENTIFIER ::= { char 5 } 751 charGroups OBJECT IDENTIFIER ::= { charConformance 1 } 752 charCompliances OBJECT IDENTIFIER ::= { charConformance 2 } 754 -- compliance statements 756 charCompliance MODULE-COMPLIANCE 757 STATUS current 758 DESCRIPTION 759 "The compliance statement for SNMPv2 entities 760 which have Character hardware interfaces." 762 MODULE -- this module 763 MANDATORY-GROUPS { charGroup } 764 ::= { charCompliances 1 } 766 draft Character MIB 26 May 1994 768 -- units of conformance 770 charGroup OBJECT-GROUP 771 OBJECTS { charNumber, charPortIndex, charPortName, 772 charPortType, charPortHardware, charPortReset, 773 charPortAdminStatus, charPortOperStatus, 774 charPortLastChange, 775 charPortInFlowState, charPortOutFlowState, 776 charPortAdminOrigin, charPortSessionMaximum, 777 charPortInFlowTypes, charPortOutFlowTypes, 778 charPortInCharacters, charPortOutCharacters, 779 charPortSessionNumber, charPortSessionIndex, 780 charPortLowerIfIndex, 781 charSessPortIndex, charSessIndex, 782 charSessKill, charSessState, 783 charSessProtocol, charSessOperOrigin, 784 charSessInCharacters, charSessOutCharacters, 785 charSessConnectionId, charSessStartTime } 786 STATUS current 787 DESCRIPTION 788 "A collection of objects providing information 789 applicable to all Character interfaces." 790 ::= { charGroups 1 } 792 END 793 draft Character MIB 26 May 1994 795 5. Acknowledgements 797 This memo was produced by the IETF Character MIB Working Group. 799 draft Character MIB 26 May 1994 801 6. References 803 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 804 of Management Information for version 2 of the Simple Network 805 Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes 806 LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon 807 University, April 1993. 809 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 810 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 811 RFC 1213, Hughes LAN Systems, Performance Systems International, 812 March 1991. 814 [3] Galvin, J., and K. McCloghrie, "Administrative Model for version 2 815 of the Simple Network Management Protocol (SNMPv2)", RFC 1445, 816 Trusted Information Systems, Hughes LAN Systems, April 1993. 818 [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 819 Operations for version 2 of the Simple Network Management Protocol 820 (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes LAN Systems, Dover 821 Beach Consulting, Inc., Carnegie Mellon University, April 1993. 823 [5] McCloghrie, K., and F.J. Kastenholz, "Evolution of the Interfaces 824 Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, 825 January 1994. 827 [6] Stewart, B., "Definitions of Managed Objects for RS-232-like 828 Hardware Devices", RFC ????, Xyplex, Inc., ?Mon?, 1994. 830 [7] Stewart, B., "Definitions of Managed Objects for Parallel-printer- 831 like Hardware Devices", RFC ????, Xyplex, Inc., ?Mon?, 1994. 833 draft Character MIB 26 May 1994 835 7. Security Considerations 837 Security issues are not discussed in this memo. 839 8. Author's Address 841 Bob Stewart 842 Xyplex, Inc. 843 295 Foster Street 844 Littleton, MA 01460 846 Tel: 508-952-4816 847 Fax: 508-952-4887 848 E-mail: rlstewart@eng.xyplex.com 850 Phone: 508-952-4816 851 Email: rlstewart@eng.xyplex.com 853 draft Character MIB 26 May 1994 855 Table of Contents 857 1 Introduction .................................................... 2 858 2 The SNMPv2 Network Management Framework ......................... 3 859 2.1 Object Definitions ............................................ 3 860 3 Overview ........................................................ 4 861 3.1 Relationship to Interface MIB ................................. 4 862 4 Definitions ..................................................... 5 863 5 Acknowledgements ................................................ 22 864 6 References ...................................................... 23 865 7 Security Considerations ......................................... 24 866 8 Author's Address ................................................ 24