idnits 2.17.1 draft-ietf-charmib-rs232-mib-03.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-19) 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: ---------------------------------------------------------------------------- == Line 573 has weird spacing: '... dte mea...' == Line 578 has weird spacing: '... dce mea...' == Line 590 has weird spacing: '... nrz for...' == Line 591 has weird spacing: '... nrzi for ...' == Line 603 has weird spacing: '...trolled when ...' == (2 more instances...) -- 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 10921 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) ** 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' Summary: 14 errors (**), 0 flaws (~~), 7 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 RS-232-like 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 RS-232-like 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 RS-232-like 30 devices. 32 draft RS-232-like 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 RS-232-like MIB 26 May 1994 67 3. Overview 69 The RS-232-like Hardware Device MIB applies to interface ports that 70 might logically support the Interface MIB, a Transmission MIB, or the 71 Character MIB. The most common example is an RS-232 port with modem 72 signals. 74 The RS-232-like Hardware Device MIB is mandatory for all systems that 75 have such a hardware port supporting services managed through some other 76 MIB. 78 The MIB includes multiple similar types of hardware, and as a result 79 contains objects not applicable to all of those types. The compliance 80 definitions herein thus have a general group for all implementations, 81 and separate groups for the different types of ports, such as 82 asynchronous and synchronous. 84 The RS-232-like Hardware Port MIB includes RS-232, RS-422, RS-423, V.35, 85 and other asynchronous or synchronous, serial physical links with a 86 similar set of control signals. 88 The MIB contains objects that relate to physical layer connections. 89 Such connections may provide interesting hardware signals (other than 90 for basic data transfer), such as RNG and DCD. Hardware ports also have 91 such attributes as speed and bits per character. 93 The MIB comprises one base object and four tables, detailed in the 94 following sections. The tables contain objects for all ports, 95 asynchronous ports, and input and output control signals. 97 3.1. Relationship to Interface MIB 99 The RS-232-like MIB is one of many MIBs designed for layered use as 100 described in the Interface MIB [5]. In most implementations where it is 101 present, it will be in the lowest interface sublayer, that is, the RS- 102 232-like MIB represents the physical layer, providing service to higher 103 layers such as the Character MIB [6] or PPP MIB [7]. 105 The Interface MIB's ifTestTable and ifRcvAddressTable are not relevant 106 to the RS-232-like MIB. 108 The RS-232-like MIB is relevant for ifType values rs232(33), v35(45), 109 and perhaps others. 111 draft RS-232-like MIB 26 May 1994 113 The RS-232-like MIB requires the conformance groups ifGeneralGroup, and 114 ifFixedLengthGroup. 116 The value of ifSpeed is the same as rs232PortOutSpeed. 118 Usefulness of error counters in this MIB depends on the octet counters 119 in ifFixedLengthGroup. 121 draft RS-232-like MIB 26 May 1994 123 4. Definitions 125 RS-232-MIB DEFINITIONS ::= BEGIN 127 IMPORTS 128 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 129 Counter32, Integer32 130 FROM SNMPv2-SMI 131 InterfaceIndex 132 FROM IF-MIB 133 transmission 134 FROM RFC1213-MIB 135 MODULE-COMPLIANCE, OBJECT-GROUP 136 FROM SNMPv2-CONF; 138 rs232 MODULE-IDENTITY 139 LAST-UPDATED "9405261700Z" 140 ORGANIZATION "IETF Character MIB Working Group" 141 CONTACT-INFO 142 " Bob Stewart 143 Postal: Xyplex, Inc. 144 295 Foster Street 145 Littleton, MA 01460 147 Tel: 508-952-4816 148 Fax: 508-952-4887 149 E-mail: rlstewart@eng.xyplex.com" 150 DESCRIPTION 151 "The MIB module for RS-232-like hardware devices." 152 ::= { transmission 33 } 154 draft RS-232-like MIB 26 May 1994 156 -- Generic RS-232-like information 158 rs232Number OBJECT-TYPE 159 SYNTAX Integer32 160 MAX-ACCESS read-only 161 STATUS current 162 DESCRIPTION 163 "The number of ports (regardless of their current 164 state) in the RS-232-like general port table." 165 ::= { rs232 1 } 167 -- RS-232-like General Port Table 169 rs232PortTable OBJECT-TYPE 170 SYNTAX SEQUENCE OF Rs232PortEntry 171 MAX-ACCESS not-accessible 172 STATUS current 173 DESCRIPTION 174 "A list of port entries. The number of entries is 175 given by the value of rs232Number." 176 ::= { rs232 2 } 178 rs232PortEntry OBJECT-TYPE 179 SYNTAX Rs232PortEntry 180 MAX-ACCESS not-accessible 181 STATUS current 182 DESCRIPTION 183 "Status and parameter values for a port." 184 INDEX { rs232PortIndex } 185 ::= { rs232PortTable 1 } 187 Rs232PortEntry ::= 188 SEQUENCE { 189 rs232PortIndex 190 InterfaceIndex, 191 rs232PortType 192 INTEGER, 193 rs232PortInSigNumber 194 Integer32, 195 rs232PortOutSigNumber 196 Integer32, 197 rs232PortInSpeed 198 Integer32, 199 rs232PortOutSpeed 201 draft RS-232-like MIB 26 May 1994 203 Integer32, 204 rs232PortInFlowType 205 INTEGER, 206 rs232PortOutFlowType 207 INTEGER 208 } 210 rs232PortIndex OBJECT-TYPE 211 SYNTAX InterfaceIndex 212 MAX-ACCESS read-only 213 STATUS current 214 DESCRIPTION 215 "The value of ifIndex for the port. By convention 216 and if possible, hardware port numbers map directly 217 to external connectors. The value for each port must 218 remain constant at least from one re-initialization 219 of the network management agent to the next." 220 ::= { rs232PortEntry 1 } 222 rs232PortType OBJECT-TYPE 223 SYNTAX INTEGER { other(1), rs232(2), rs422(3), 224 rs423(4), v35(5), x21(6) } 225 MAX-ACCESS read-only 226 STATUS current 227 DESCRIPTION 228 "The port's hardware type." 229 ::= { rs232PortEntry 2 } 231 rs232PortInSigNumber OBJECT-TYPE 232 SYNTAX Integer32 233 MAX-ACCESS read-only 234 STATUS current 235 DESCRIPTION 236 "The number of input signals for the port in the 237 input signal table (rs232PortInSigTable). The table 238 contains entries only for those signals the software 239 can detect and that are useful to observe." 240 ::= { rs232PortEntry 3 } 242 rs232PortOutSigNumber OBJECT-TYPE 243 SYNTAX Integer32 244 MAX-ACCESS read-only 245 STATUS current 246 DESCRIPTION 247 "The number of output signals for the port in the 249 draft RS-232-like MIB 26 May 1994 251 output signal table (rs232PortOutSigTable). The 252 table contains entries only for those signals the 253 software can assert and that are useful to observe." 254 ::= { rs232PortEntry 4 } 256 rs232PortInSpeed OBJECT-TYPE 257 SYNTAX Integer32 258 MAX-ACCESS read-write 259 STATUS current 260 DESCRIPTION 261 "The port's input speed in bits per second. Note that 262 non-standard values, such as 9612, are probably not allowed 263 on most implementations." 264 ::= { rs232PortEntry 5 } 266 rs232PortOutSpeed OBJECT-TYPE 267 SYNTAX Integer32 268 MAX-ACCESS read-write 269 STATUS current 270 DESCRIPTION 271 "The port's output speed in bits per second. Note that 272 non-standard values, such as 9612, are probably not allowed 273 on most implementations." 274 ::= { rs232PortEntry 6 } 276 rs232PortInFlowType OBJECT-TYPE 277 SYNTAX INTEGER { none(1), ctsRts(2), dsrDtr(3) } 278 MAX-ACCESS read-write 279 STATUS current 280 DESCRIPTION 281 "The port's type of input flow control. 'none' 282 indicates no flow control at this level. 283 'ctsRts' and 'dsrDtr' indicate use of the indicated 284 hardware signals." 285 ::= { rs232PortEntry 7 } 287 rs232PortOutFlowType OBJECT-TYPE 288 SYNTAX INTEGER { none(1), ctsRts(2), dsrDtr(3) } 289 MAX-ACCESS read-write 290 STATUS current 291 DESCRIPTION 292 "The port's type of output flow control. 'none' 293 indicates no flow control at this level. 294 'ctsRts' and 'dsrDtr' indicate use of the indicated 295 hardware signals." 297 draft RS-232-like MIB 26 May 1994 299 ::= { rs232PortEntry 8 } 301 draft RS-232-like MIB 26 May 1994 303 -- RS-232-like Asynchronous Port Table 305 rs232AsyncPortTable OBJECT-TYPE 306 SYNTAX SEQUENCE OF Rs232AsyncPortEntry 307 MAX-ACCESS not-accessible 308 STATUS current 309 DESCRIPTION 310 "A list of asynchronous port entries. Entries need 311 not exist for synchronous ports." 312 ::= { rs232 3 } 314 rs232AsyncPortEntry OBJECT-TYPE 315 SYNTAX Rs232AsyncPortEntry 316 MAX-ACCESS not-accessible 317 STATUS current 318 DESCRIPTION 319 "Status and parameter values for an asynchronous 320 port." 321 INDEX { rs232AsyncPortIndex } 322 ::= { rs232AsyncPortTable 1 } 324 Rs232AsyncPortEntry ::= 325 SEQUENCE { 326 rs232AsyncPortIndex 327 InterfaceIndex, 328 rs232AsyncPortBits 329 INTEGER, 330 rs232AsyncPortStopBits 331 INTEGER, 332 rs232AsyncPortParity 333 INTEGER, 334 rs232AsyncPortAutobaud 335 INTEGER, 336 rs232AsyncPortParityErrs 337 Counter32, 338 rs232AsyncPortFramingErrs 339 Counter32, 340 rs232AsyncPortOverrunErrs 341 Counter32 343 } 345 rs232AsyncPortIndex OBJECT-TYPE 346 SYNTAX InterfaceIndex 347 MAX-ACCESS read-only 349 draft RS-232-like MIB 26 May 1994 351 STATUS current 352 DESCRIPTION 353 "A unique value for each port. Its value is the 354 same as rs232PortIndex for the port." 355 ::= { rs232AsyncPortEntry 1 } 357 rs232AsyncPortBits OBJECT-TYPE 358 SYNTAX INTEGER (5..8) 359 MAX-ACCESS read-write 360 STATUS current 361 DESCRIPTION 362 "The port's number of bits in a character." 363 ::= { rs232AsyncPortEntry 2 } 365 rs232AsyncPortStopBits OBJECT-TYPE 366 SYNTAX INTEGER { one(1), two(2), 367 oneAndHalf(3), dynamic(4) } 368 MAX-ACCESS read-write 369 STATUS current 370 DESCRIPTION 371 "The port's number of stop bits." 372 ::= { rs232AsyncPortEntry 3 } 374 rs232AsyncPortParity OBJECT-TYPE 375 SYNTAX INTEGER { none(1), odd(2), even(3), 376 mark(4), space(5) } 377 MAX-ACCESS read-write 378 STATUS current 379 DESCRIPTION 380 "The port's sense of a character parity bit." 381 ::= { rs232AsyncPortEntry 4 } 383 rs232AsyncPortAutobaud OBJECT-TYPE 384 SYNTAX INTEGER { enabled(1), disabled(2) } 385 MAX-ACCESS read-write 386 STATUS current 387 DESCRIPTION 388 "A control for the port's ability to automatically 389 sense input speed. 391 When rs232PortAutoBaud is 'enabled', a port may 392 autobaud to values different from the set values for 393 speed, parity, and character size. As a result a 394 network management system may temporarily observe 395 values different from what was previously set." 397 draft RS-232-like MIB 26 May 1994 399 ::= { rs232AsyncPortEntry 5 } 401 rs232AsyncPortParityErrs OBJECT-TYPE 402 SYNTAX Counter32 403 MAX-ACCESS read-only 404 STATUS current 405 DESCRIPTION 406 "Total number of characters with a parity error, 407 input from the port since system re-initialization 408 and while the port state was 'up' or 'test'." 409 ::= { rs232AsyncPortEntry 6 } 411 rs232AsyncPortFramingErrs OBJECT-TYPE 412 SYNTAX Counter32 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "Total number of characters with a framing error, 417 input from the port since system re-initialization 418 and while the port state was 'up' or 'test'." 419 ::= { rs232AsyncPortEntry 7 } 421 rs232AsyncPortOverrunErrs OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "Total number of characters with an overrun error, 427 input from the port since system re-initialization 428 and while the port state was 'up' or 'test'." 429 ::= { rs232AsyncPortEntry 8 } 431 draft RS-232-like MIB 26 May 1994 433 -- RS-232-like Synchronous Port Table 435 rs232SyncPortTable OBJECT-TYPE 436 SYNTAX SEQUENCE OF Rs232SyncPortEntry 437 MAX-ACCESS not-accessible 438 STATUS current 439 DESCRIPTION 440 "A list of asynchronous port entries. Entries need 441 not exist for synchronous ports." 442 ::= { rs232 4 } 444 rs232SyncPortEntry OBJECT-TYPE 445 SYNTAX Rs232SyncPortEntry 446 MAX-ACCESS not-accessible 447 STATUS current 448 DESCRIPTION 449 "Status and parameter values for a synchronous 450 port." 451 INDEX { rs232SyncPortIndex } 452 ::= { rs232SyncPortTable 1 } 454 Rs232SyncPortEntry ::= 455 SEQUENCE { 456 rs232SyncPortIndex 457 InterfaceIndex, 458 rs232SyncPortClockSource 459 INTEGER, 460 rs232SyncPortFrameCheckErrs 461 Counter32, 462 rs232SyncPortTransmitUnderrunErrs 463 Counter32, 464 rs232SyncPortReceiveOverrunErrs 465 Counter32, 466 rs232SyncPortInterruptedFrames 467 Counter32, 468 rs232SyncPortAbortedFrames 469 Counter32, 470 rs232SyncPortRole 471 INTEGER, 472 rs232SyncPortEncoding 473 INTEGER, 474 rs232SyncPortRTSControl 475 INTEGER, 476 rs232SyncPortRTSCTSDelay 477 Integer32, 479 draft RS-232-like MIB 26 May 1994 481 rs232SyncPortMode 482 INTEGER, 483 rs232SyncPortIdlePattern 484 INTEGER, 485 rs232SyncPortMinFlags 486 Integer32 487 } 489 rs232SyncPortIndex OBJECT-TYPE 490 SYNTAX InterfaceIndex 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "A unique value for each port. Its value is the 495 same as rs232PortIndex for the port." 496 ::= { rs232SyncPortEntry 1 } 498 rs232SyncPortClockSource OBJECT-TYPE 499 SYNTAX INTEGER { internal(1), external(2), split(3) } 500 MAX-ACCESS read-write 501 STATUS current 502 DESCRIPTION 503 "Source of the port's bit rate clock. 'split' means 504 the tranmit clock is internal and the receive clock 505 is external." 506 ::= { rs232SyncPortEntry 2 } 508 rs232SyncPortFrameCheckErrs OBJECT-TYPE 509 SYNTAX Counter32 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 "Total number of frames with an invalid frame check 514 sequence, input from the port since system 515 re-initialization and while the port state was 'up' 516 or 'test'." 517 ::= { rs232SyncPortEntry 3 } 519 rs232SyncPortTransmitUnderrunErrs OBJECT-TYPE 520 SYNTAX Counter32 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "Total number of frames that failed to be 525 transmitted on the port since system 527 draft RS-232-like MIB 26 May 1994 529 re-initialization and while the port state was 'up' 530 or 'test' because data was not available to the 531 transmitter in time." 532 ::= { rs232SyncPortEntry 4 } 534 rs232SyncPortReceiveOverrunErrs OBJECT-TYPE 535 SYNTAX Counter32 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "Total number of frames that failed to be received 540 on the port since system re-initialization and while 541 the port state was 'up' or 'test' because the 542 receiver did not accept the data in time." 543 ::= { rs232SyncPortEntry 5 } 545 rs232SyncPortInterruptedFrames OBJECT-TYPE 546 SYNTAX Counter32 547 MAX-ACCESS read-only 548 STATUS current 549 DESCRIPTION 550 "Total number of frames that failed to be received 551 or transmitted on the port due to loss of modem 552 signals since system re-initialization and while the 553 port state was 'up' or 'test'." 554 ::= { rs232SyncPortEntry 6 } 556 rs232SyncPortAbortedFrames OBJECT-TYPE 557 SYNTAX Counter32 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "Number of frames aborted on the port due to 562 receiving an abort sequence since system 563 re-initialization and while the port state was 'up' 564 or 'test'." 565 ::= { rs232SyncPortEntry 7 } 567 rs232SyncPortRole OBJECT-TYPE 568 SYNTAX INTEGER { dte(1), dce(2) } 569 MAX-ACCESS read-write 570 STATUS current 571 DESCRIPTION 572 "The role the device is playing that is using this port. 573 dte means the device is performing the role of 575 draft RS-232-like MIB 26 May 1994 577 data terminal equipment 578 dce means the device is performing the role of 579 data circuit-terminating equipment." 580 DEFVAL { dce } 581 ::= { rs232SyncPortEntry 8 } 583 rs232SyncPortEncoding OBJECT-TYPE 584 SYNTAX INTEGER { nrz(1), nrzi(2) } 585 MAX-ACCESS read-write 586 STATUS current 587 DESCRIPTION 588 "The bit stream encoding technique that is in effect 589 for this port. 590 nrz for Non-Return to Zero encoding 591 nrzi for Non-Return to Zero Inverted encoding." 592 DEFVAL { nrz } 593 ::= { rs232SyncPortEntry 9 } 595 rs232SyncPortRTSControl OBJECT-TYPE 596 SYNTAX INTEGER { controlled(1), constant(2) } 597 MAX-ACCESS read-write 598 STATUS current 599 DESCRIPTION 600 "The method used to control the Request To Send (RTS) 601 signal. 603 controlled when the DTE is asserts RTS each time 604 data needs to be transmitted and drops 605 RTS at some point after data 606 transmission begins. 608 If rs232SyncPortRole is 'dte', the 609 RTS is an output signal. The device 610 will issue a RTS and wait for a CTS 611 from the DCE before starting to 612 transmit. 614 If rs232SyncPortRole is 'dce', the 615 RTS is an input signal. The device 616 will issue a CTS only after having 617 received RTS and waiting the 618 rs232SyncPortRTSCTSDelay interval. 620 constant when the DTE constantly asserts RTS." 621 DEFVAL { constant } 623 draft RS-232-like MIB 26 May 1994 625 ::= { rs232SyncPortEntry 10 } 627 rs232SyncPortRTSCTSDelay OBJECT-TYPE 628 SYNTAX Integer32 629 MAX-ACCESS read-write 630 STATUS current 631 DESCRIPTION 632 "The interval (in milliseconds) that the DCE must wait 633 after it sees RTS asserted before asserting CTS. This 634 object exists in support of older synchronous devices 635 that cannot recognize CTS within a certain interval 636 after it asserts RTS." 637 DEFVAL { 0 } 638 ::= { rs232SyncPortEntry 11 } 640 rs232SyncPortMode OBJECT-TYPE 641 SYNTAX INTEGER { fdx(1), hdx(2), simplex-receive(3), 642 simplex-send(4) } 643 MAX-ACCESS read-write 644 STATUS current 645 DESCRIPTION 646 "The mode of operation of the port with respect to the 647 direction and simultaneity of data transfer. 649 fdx when frames on the data link can be 650 transmitted and received at the same 651 time 653 hdx when frames can either be received 654 from the data link or transmitted 655 onto the data link but not at the 656 same time. 658 simplex-receive when frames can only be received on 659 this data link. 661 simplex-send when frames can only be sent on this 662 data link." 663 DEFVAL { fdx } 664 ::= { rs232SyncPortEntry 12 } 666 rs232SyncPortIdlePattern OBJECT-TYPE 667 SYNTAX INTEGER { mark(1), space(2) } 668 MAX-ACCESS read-write 669 STATUS current 671 draft RS-232-like MIB 26 May 1994 673 DESCRIPTION 674 "The bit pattern used to indicate an idle line." 675 DEFVAL { space } 676 ::= { rs232SyncPortEntry 13 } 678 rs232SyncPortMinFlags OBJECT-TYPE 679 SYNTAX Integer32 680 MAX-ACCESS read-write 681 STATUS current 682 DESCRIPTION 683 "The minimum number of flag patterns this port needs in 684 order to recognize the end of one frame and the start 685 of the next. Plausible values are 1 and 2." 686 DEFVAL { 2 } 687 ::= { rs232SyncPortEntry 14 } 689 draft RS-232-like MIB 26 May 1994 691 -- Input Signal Table 693 rs232InSigTable OBJECT-TYPE 694 SYNTAX SEQUENCE OF Rs232InSigEntry 695 MAX-ACCESS not-accessible 696 STATUS current 697 DESCRIPTION 698 "A list of port input control signal entries 699 implemented and visible to the software on the port, 700 and useful to monitor." 701 ::= { rs232 5 } 703 rs232InSigEntry OBJECT-TYPE 704 SYNTAX Rs232InSigEntry 705 MAX-ACCESS not-accessible 706 STATUS current 707 DESCRIPTION 708 "Input control signal status for a hardware port." 709 INDEX { rs232InSigPortIndex, rs232InSigName } 710 ::= { rs232InSigTable 1 } 712 Rs232InSigEntry ::= 713 SEQUENCE { 714 rs232InSigPortIndex 715 InterfaceIndex, 716 rs232InSigName 717 INTEGER, 718 rs232InSigState 719 INTEGER, 720 rs232InSigChanges 721 Counter32 722 } 724 rs232InSigPortIndex OBJECT-TYPE 725 SYNTAX InterfaceIndex 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "The value of rs232PortIndex for the port to which 730 this entry belongs." 731 ::= { rs232InSigEntry 1 } 733 rs232InSigName OBJECT-TYPE 734 SYNTAX INTEGER { rts(1), cts(2), dsr(3), dtr(4), ri(5), 735 dcd(6), sq(7), srs(8), srts(9), 737 draft RS-232-like MIB 26 May 1994 739 scts(10), sdcd(11) } 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "Identification of a hardware signal, as follows: 745 rts Request to Send 746 cts Clear to Send 747 dsr Data Set Ready 748 dtr Data Terminal Ready 749 ri Ring Indicator 750 dcd Received Line Signal Detector 751 sq Signal Quality Detector 752 srs Data Signaling Rate Selector 753 srts Secondary Request to Send 754 scts Secondary Clear to Send 755 sdcd Secondary Received Line Signal Detector 756 " 757 REFERENCE 758 "EIA Standard RS-232-C, August 1969." 759 ::= { rs232InSigEntry 2 } 761 rs232InSigState OBJECT-TYPE 762 SYNTAX INTEGER { none(1), on(2), off(3) } 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION 766 "The current signal state." 767 ::= { rs232InSigEntry 3 } 769 rs232InSigChanges OBJECT-TYPE 770 SYNTAX Counter32 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "The number of times the signal has changed from 775 'on' to 'off' or from 'off' to 'on'." 776 ::= { rs232InSigEntry 4 } 778 draft RS-232-like MIB 26 May 1994 780 -- Output Signal Table 782 rs232OutSigTable OBJECT-TYPE 783 SYNTAX SEQUENCE OF Rs232OutSigEntry 784 MAX-ACCESS not-accessible 785 STATUS current 786 DESCRIPTION 787 "A list of port output control signal entries 788 implemented and visible to the software on the port, 789 and useful to monitor." 790 ::= { rs232 6 } 792 rs232OutSigEntry OBJECT-TYPE 793 SYNTAX Rs232OutSigEntry 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "Output control signal status for a hardware port." 798 INDEX { rs232OutSigPortIndex, rs232OutSigName } 799 ::= { rs232OutSigTable 1 } 801 Rs232OutSigEntry ::= 802 SEQUENCE { 803 rs232OutSigPortIndex 804 InterfaceIndex, 805 rs232OutSigName 806 INTEGER, 807 rs232OutSigState 808 INTEGER, 809 rs232OutSigChanges 810 Counter32 811 } 813 rs232OutSigPortIndex OBJECT-TYPE 814 SYNTAX InterfaceIndex 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "The value of rs232PortIndex for the port to which 819 this entry belongs." 820 ::= { rs232OutSigEntry 1 } 822 rs232OutSigName OBJECT-TYPE 823 SYNTAX INTEGER { rts(1), cts(2), dsr(3), dtr(4), ri(5), 824 dcd(6), sq(7), srs(8), srts(9), 826 draft RS-232-like MIB 26 May 1994 828 scts(10), sdcd(11) } 829 MAX-ACCESS read-only 830 STATUS current 831 DESCRIPTION 832 "Identification of a hardware signal, as follows: 834 rts Request to Send 835 cts Clear to Send 836 dsr Data Set Ready 837 dtr Data Terminal Ready 838 ri Ring Indicator 839 dcd Received Line Signal Detector 840 sq Signal Quality Detector 841 srs Data Signaling Rate Selector 842 srts Secondary Request to Send 843 scts Secondary Clear to Send 844 sdcd Secondary Received Line Signal Detector 845 " 846 REFERENCE 847 "EIA Standard RS-232-C, August 1969." 848 ::= { rs232OutSigEntry 2 } 850 rs232OutSigState OBJECT-TYPE 851 SYNTAX INTEGER { none(1), on(2), off(3) } 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "The current signal state." 856 ::= { rs232OutSigEntry 3 } 858 rs232OutSigChanges OBJECT-TYPE 859 SYNTAX Counter32 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 "The number of times the signal has changed from 864 'on' to 'off' or from 'off' to 'on'." 865 ::= { rs232OutSigEntry 4 } 867 draft RS-232-like MIB 26 May 1994 869 -- conformance information 871 rs232Conformance OBJECT IDENTIFIER ::= { rs232 7 } 873 rs232Groups OBJECT IDENTIFIER ::= { rs232Conformance 1 } 874 rs232Compliances OBJECT IDENTIFIER ::= { rs232Conformance 2 } 876 -- compliance statements 878 rs232Compliance MODULE-COMPLIANCE 879 STATUS current 880 DESCRIPTION 881 "The compliance statement for SNMPv2 entities 882 which have RS-232-like hardware interfaces." 884 MODULE -- this module 885 MANDATORY-GROUPS { rs232Group } 887 GROUP rs232AsyncGroup 888 DESCRIPTION 889 "The Asynch group is mandatory only for those 890 SNMPv2 entities which have asynchronous 891 interfaces Rs-232-like." 893 GROUP rs232SyncGroup 894 DESCRIPTION 895 "The Synch group is mandatory only for those 896 SNMPv2 entities which have synchronous 897 interfaces Rs-232-like." 898 ::= { rs232Compliances 1 } 900 draft RS-232-like MIB 26 May 1994 902 -- units of conformance 904 rs232Group OBJECT-GROUP 905 OBJECTS { rs232Number, rs232PortIndex, rs232PortType, 906 rs232PortInSigNumber, rs232PortOutSigNumber, 907 rs232PortInSpeed, rs232PortOutSpeed, 908 rs232PortInFlowType, rs232PortOutFlowType, 909 rs232InSigPortIndex, rs232InSigName, 910 rs232InSigState, rs232InSigChanges, 911 rs232OutSigPortIndex, rs232OutSigName, 912 rs232OutSigState, rs232OutSigChanges } 913 STATUS current 914 DESCRIPTION 915 "A collection of objects providing information 916 applicable to all RS-232-like interfaces." 917 ::= { rs232Groups 1 } 919 rs232AsyncGroup OBJECT-GROUP 920 OBJECTS { rs232AsyncPortIndex, rs232AsyncPortBits, 921 rs232AsyncPortStopBits, rs232AsyncPortParity, 922 rs232AsyncPortAutobaud, rs232AsyncPortParityErrs, 923 rs232AsyncPortFramingErrs, rs232AsyncPortOverrunErrs } 924 STATUS current 925 DESCRIPTION 926 "A collection of objects providing information 927 applicable to asynchronous RS-232-like interfaces." 928 ::= { rs232Groups 2 } 930 rs232SyncGroup OBJECT-GROUP 931 OBJECTS { rs232SyncPortIndex, rs232SyncPortClockSource, 932 rs232SyncPortFrameCheckErrs, 933 rs232SyncPortTransmitUnderrunErrs, 934 rs232SyncPortReceiveOverrunErrs, 935 rs232SyncPortInterruptedFrames, 936 rs232SyncPortAbortedFrames } 937 STATUS current 938 DESCRIPTION 939 "A collection of objects providing information 940 applicable to synchronous RS-232-like interfaces." 941 ::= { rs232Groups 3 } 943 rs232SyncSDLCGroup OBJECT-GROUP 944 OBJECTS { rs232SyncPortRole, 945 rs232SyncPortEncoding, 946 rs232SyncPortRTSControl, 948 draft RS-232-like MIB 26 May 1994 950 rs232SyncPortRTSCTSDelay, 951 rs232SyncPortMode, 952 rs232SyncPortIdlePattern, 953 rs232SyncPortMinFlags } 954 STATUS current 955 DESCRIPTION 956 "A collection of objects providing information 957 applicable to synchronous RS-232-like interfaces 958 running SDLC." 959 ::= { rs232Groups 4 } 961 END 962 draft RS-232-like MIB 26 May 1994 964 5. Acknowledgements 966 This memo was produced by the IETF Character MIB Working Group. 968 draft RS-232-like MIB 26 May 1994 970 6. References 972 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 973 of Management Information for version 2 of the Simple Network 974 Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes 975 LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon 976 University, April 1993. 978 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 979 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 980 RFC 1213, Hughes LAN Systems, Performance Systems International, 981 March 1991. 983 [3] Galvin, J., and K. McCloghrie, "Administrative Model for version 2 984 of the Simple Network Management Protocol (SNMPv2)", RFC 1445, 985 Trusted Information Systems, Hughes LAN Systems, April 1993. 987 [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 988 Operations for version 2 of the Simple Network Management Protocol 989 (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes LAN Systems, Dover 990 Beach Consulting, Inc., Carnegie Mellon University, April 1993. 992 [5] McCloghrie, K., and F.J. Kastenholz, "Evolution of the Interfaces 993 Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, 994 January 1994. 996 [6] Stewart, B., "Definitions of Managed Objects for Character Stream 997 Devices", RFC ????, Xyplex, Inc., ?Mon?, 1994. 999 [7] Kastenholz, F., "The Definitions of Managed Objects for the Link 1000 Control Protocol of the Point-to-Point Protocol", RFC 1471, FTP 1001 Software, Inc., June, 1993. 1003 draft RS-232-like MIB 26 May 1994 1005 7. Security Considerations 1007 Security issues are not discussed in this memo. 1009 8. Author's Address 1011 Bob Stewart 1012 Xyplex, Inc. 1013 295 Foster Street 1014 Littleton, MA 01460 1016 Tel: 508-952-4816 1017 Fax: 508-952-4887 1018 E-mail: rlstewart@eng.xyplex.com 1020 Phone: 508-952-4816 1021 Email: rlstewart@eng.xyplex.com 1023 draft RS-232-like MIB 26 May 1994 1025 Table of Contents 1027 1 Introduction .................................................... 2 1028 2 The SNMPv2 Network Management Framework ......................... 3 1029 2.1 Object Definitions ............................................ 3 1030 3 Overview ........................................................ 4 1031 3.1 Relationship to Interface MIB ................................. 4 1032 4 Definitions ..................................................... 6 1033 5 Acknowledgements ................................................ 27 1034 6 References ...................................................... 28 1035 7 Security Considerations ......................................... 29 1036 8 Author's Address ................................................ 29