idnits 2.17.1 draft-ietf-syslog-device-mib-17.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1794. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1805. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1812. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1818. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (February 9, 2008) is 5921 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) == Missing Reference: 'RFC3419' is mentioned on line 2008, but not defined == Outdated reference: A later version (-23) exists of draft-ietf-syslog-protocol-21 == Outdated reference: A later version (-12) exists of draft-ietf-syslog-transport-udp-09 == Outdated reference: A later version (-14) exists of draft-ietf-syslog-transport-tls-10 Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Syslog Working Group Glenn Mansfield Keeni 3 INTERNET-DRAFT Cyber Solutions Inc. 4 Intended Status: Proposed Standard 5 Expires: August 8, 2008 February 9, 2008 7 Syslog Management Information Base 8 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This document is a product of the syslog Working Group. Comments 34 should be addressed to the authors or the mailing list at 35 syslog@ietf.org 37 This Internet-Draft will expire on August 8, 2008. 39 Copyright Notice 41 Copyright (C) The IETF Trust (2008). 43 Abstract 45 This memo defines a portion of the Management Information Base (MIB), 46 the Syslog MIB, for use with network management protocols 47 in the Internet community. In particular, the Syslog MIB will be 48 used to monitor and control syslog applications. 50 Table of Contents 52 1. The Internet-Standard Management Framework .... 3 53 2. Background .................................... 3 54 3. The MIB Design ................................ 4 55 4. The Syslog MIB ................................ 6 56 5. Security Considerations ....................... 41 57 6. IANA Considerations ........................... 44 58 7. References .................................... 44 59 8 Acknowledgments ............................... 45 60 9. Author's Addresses ............................ 46 61 10. Full Copyright Statement ...................... 47 62 Appendix ...................................... 49 64 1. The Internet-Standard Management Framework 66 For a detailed overview of the documents that describe the current 67 Internet-Standard Management Framework, please refer to section 7 of 68 RFC 3410 [RFC3410]. 70 Managed objects are accessed via a virtual information store, termed 71 the Management Information Base or MIB. MIB objects are generally 72 accessed through the Simple Network Management Protocol (SNMP). 74 Objects in the MIB are defined using the mechanisms defined in the 75 Structure of Management Information (SMI). This memo specifies a MIB 76 module that is compliant to the SMIv2, which is described in STD 58, 77 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 78 [RFC2580]. 80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 82 document are to be interpreted as described in BCP 14, RFC 2119 83 [RFC2119]. 85 2. Background 87 Operating systems, processes and applications, collectively termed 88 "facilities" in the following, generate messages indicating their own 89 status or the occurrence of events. These messages are handled by 90 what has come to be known as the syslog application[RFCPROT]. A 91 syslog application sends and/or receives syslog messages. The reader 92 is referred to [RFCPROT] for a description of the various roles of a 93 syslog application viz. "sender", "receiver" and "relay". The 94 discussion in this document in general applies to a generic syslog 95 application. For special cases the specific role of the syslog 96 application will be mentioned. 98 This document defines a set of managed objects (MOs) that can be used 99 to monitor a group of syslog applications. 101 The SYSLOG-MIB can be used in conjunction with other MIB modules - in 102 particular the Host Resources MIB[RFC2790]. The generic process 103 related matters e.g. control and monitoring for status, resource 104 usage etc. can be serviced by the corresponding entries in the Host 105 Resources MIB. 107 +------+ 108 Syslog message ----->| App1 | 109 +------+ 111 +------+ 112 Syslog message ----->| App2 |------> Syslog message 113 +------+ 115 +------+ 116 | App3 |------> Syslog message 117 +------+ 119 App1: Syslog collector ( syslog receiver) 120 App2: Syslog relay ( syslog receiver, syslog sender) 121 App3: Syslog originator (syslog sender) 123 Fig.1 Syslog applications modeled by the SYSLOG-MIB 125 The syslog applications modeled by the SYSLOG-MIB are shown in Fig.1. 126 A syslog receiver receives syslog messages. A syslog sender sends 127 syslog messages to other syslog applications. A syslog relay forwards 128 some of the received syslog messages to other syslog applications. A 129 syslog receiver receives a syslog message and processes it. The 130 processing will depend on the internal configuration and may involve 131 relaying the message to one or more syslog applications. Note that a 132 syslog application may have multiple roles. Multiple syslog 133 applications may co-exist on the same host. 135 3. The MIB Design. 137 The purpose of the SYSLOG-MIB is to allow the monitoring of a group 138 of syslog applications. This requires managed objects representing 139 the following elements. 141 o The configuration and status related details of each syslog 142 application. 143 o The statistics on syslog messages received, processed 144 locally, relayed by each syslog application. 146 The MIB contains three subtrees. 147 o The syslogNotifications subtree defines the set of 148 notifications that will be used to asynchronously report 149 the change of status of a syslog application. 150 o The syslogObjects subtree contains three subtrees. 151 - The syslogControlTable subtree deals with the 152 configuration and control information for a syslog 153 application. 154 - The syslogOperationsTable subtree deals with operations 155 and statistical information about syslog messages sent 156 and/or received by a syslog application. 157 o The conformance subtree defines the compliance statements. 159 The SYSLOG-MIB module uses textual conventions defined in INET- 160 ADDRESS-MIB[RFC4001] and SNMP-FRAMEWORK-MIB[RFC3411]. 162 4. The Syslog MIB 164 SYSLOG-MIB DEFINITIONS ::= BEGIN 166 IMPORTS 167 MODULE-IDENTITY, OBJECT-TYPE, 168 Unsigned32, Counter32, Integer32, mib-2, 169 NOTIFICATION-TYPE 170 FROM SNMPv2-SMI 171 RowStatus, StorageType, 172 TEXTUAL-CONVENTION, TimeStamp 173 FROM SNMPv2-TC 174 InetAddressType, InetAddress, InetPortNumber 175 FROM INET-ADDRESS-MIB 176 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 177 FROM SNMPv2-CONF 178 SyslogFacility, SyslogSeverity 179 FROM SYSLOG-TC-MIB 180 SnmpAdminString 181 FROM SNMP-FRAMEWORK-MIB; 183 syslogMIB MODULE-IDENTITY 184 LAST-UPDATED "200703040000Z" -- 4th March, 2007 185 ORGANIZATION "IETF Syslog Working Group" 186 CONTACT-INFO 187 " Glenn Mansfield Keeni 188 Postal: Cyber Solutions Inc. 189 6-6-3, Minami Yoshinari 190 Aoba-ku, Sendai, Japan 989-3204. 191 Tel: +81-22-303-4012 192 Fax: +81-22-303-4015 193 E-mail: glenn@cysols.com 195 Support Group E-mail: syslog@ietf.org 196 " 198 DESCRIPTION 199 "The MIB module for monitoring syslog applications. 201 A syslog application sends and/or receives syslog messages. 202 The reader is referred to [RFCPROT] for a description of 203 the various roles of a syslog application viz. ''sender'', 204 ''receiver'' and ''relay''. The discussion in this 205 document in general applies to a generic syslog application. 207 For special cases the specific role of the syslog 208 application will be mentioned. 210 Copyright (C) The IETF Trust (2008). This version of 211 this MIB module is part of RFC XXXX; see the RFC itself for 212 full legal notices. 213 " 214 -- RFC Ed.: replace XXXX with the actual RFC number & remove this 215 -- note 217 REVISION "200703040000Z" -- 4th March, 2007 218 DESCRIPTION 219 "The initial version, published as RFC XXXX." 221 -- RFC Ed.: replace XXXX with the actual RFC number & remove this 222 -- note 224 ::= { mib-2 YYYY } -- Will be assigned by IANA 226 -- IANA Reg.: Please assign a value for "YYYY" under the 227 -- 'mib-2' subtree and record the assignment in the SMI 228 -- Numbers registry. 230 -- RFC Ed.: When the above assignment has been made, please 231 -- remove the above note 232 -- replace "YYYY" here with the assigned value and 233 -- remove this note. 235 -- ------------------------------------------------------------- 236 -- Textual Conventions 237 -- ------------------------------------------------------------- 238 SyslogRoles ::= TEXTUAL-CONVENTION 239 STATUS current 240 DESCRIPTION 241 "This textual convention enumerates the roles of a 242 syslog application. Note that a syslog application can 243 have multiple roles. 244 " 245 REFERENCE 246 "The Syslog Protocol [RFCPROT] sec. 3. 247 " 248 SYNTAX BITS 249 { 250 sender (0), 251 receiver (1), 252 relay (2) 253 } 255 SyslogEncapsulation ::= TEXTUAL-CONVENTION 256 STATUS current 257 DESCRIPTION 258 "This textual convention enumerates the encapsulations 259 of the syslog message that is used between syslog 260 application endpoints. 261 " 262 REFERENCE 263 "Transmission of syslog messages over UDP [RFCUDPX], 264 TLS Transport Mapping for Syslog [RFCTLSX], 265 Reliable Delivery for syslog [RFC3195]. 266 " 267 SYNTAX INTEGER 268 { 269 other (1), 270 none (2), -- [RFCUDPX] (no encapsulation) 271 tls (3), -- [RFCTLSX] 272 beep (4) -- [RFC3195] 273 } 275 -- syslogMIB - the main groups 276 -- ------------------------------------------------------------- 278 syslogNotifications OBJECT IDENTIFIER 279 ::= { syslogMIB 0 } 281 syslogObjects OBJECT IDENTIFIER 282 ::= { syslogMIB 1 } 284 syslogConformance OBJECT IDENTIFIER 285 ::= { syslogMIB 3 } 287 -- ------------------------------------------------------------- 288 -- syslog application configuration info table 289 -- ------------------------------------------------------------- 290 syslogControlTable OBJECT-TYPE 291 SYNTAX SEQUENCE OF SyslogControlEntry 292 MAX-ACCESS not-accessible 293 STATUS current 294 DESCRIPTION 295 "A table containing the configuration parameters 296 pertaining to the syslog applications serviced by an 297 SNMP agent. 298 " 299 ::= { syslogObjects 1 } 301 syslogControlEntry OBJECT-TYPE 302 SYNTAX SyslogControlEntry 303 MAX-ACCESS not-accessible 304 STATUS current 305 DESCRIPTION 306 "The configuration parameters pertaining to a syslog 307 application. 308 " 309 INDEX { syslogControlIndex } 310 ::= { syslogControlTable 1 } 312 SyslogControlEntry ::= 313 SEQUENCE { 314 syslogControlIndex 315 Unsigned32, 316 syslogControlDescr 317 SnmpAdminString, 318 syslogControlRoles 319 SyslogRoles, 320 syslogControlBindAddrType 321 InetAddressType, 322 syslogControlBindAddr 323 InetAddress, 324 syslogControlBindPort 325 InetPortNumber, 326 syslogControlEncapsulation 327 SyslogEncapsulation, 328 syslogControlMaxMessageSize 329 Unsigned32, 330 syslogControlConfFileName 331 SnmpAdminString, 332 syslogControlStorageType 333 StorageType, 334 syslogControlRowStatus 335 RowStatus 336 } 338 syslogControlIndex OBJECT-TYPE 339 SYNTAX Unsigned32 (1..2147483647) 340 MAX-ACCESS not-accessible 341 STATUS current 342 DESCRIPTION 343 "The Index that uniquely identifies the syslog 344 application in the syslogControlTable. 345 The value of the index for a syslog application may 346 not be the same across system reboots. Users and 347 applications will need to determine the index of a 348 syslog application after system reboots. 349 " 350 ::= { syslogControlEntry 1 } 352 syslogControlDescr OBJECT-TYPE 353 SYNTAX SnmpAdminString 354 MAX-ACCESS read-create 355 STATUS current 356 DESCRIPTION 357 "A user definable description of the syslog application. 358 This description could be used by syslog management 359 applications e.g. in reports or in user interfaces. 360 " 361 ::= { syslogControlEntry 2 } 363 syslogControlRoles OBJECT-TYPE 364 SYNTAX SyslogRoles 365 MAX-ACCESS read-create 366 STATUS current 367 DESCRIPTION 368 "The roles of the syslog application. 369 " 370 ::= { syslogControlEntry 3 } 372 syslogControlBindAddrType OBJECT-TYPE 373 SYNTAX InetAddressType 374 MAX-ACCESS read-create 375 STATUS current 376 DESCRIPTION 377 "The type of Internet address which follows 378 in syslogControlBindAddr. 379 If this syslog application is not a syslog receiver, 380 the value of this object will be 'unknown' (0). 381 " 382 ::= { syslogControlEntry 4 } 384 syslogControlBindAddr OBJECT-TYPE 385 SYNTAX InetAddress 386 MAX-ACCESS read-create 387 STATUS current 388 DESCRIPTION 389 "The specific address the syslog receiver will bind to. 390 The format of the address is specified by the 391 corresponding syslogControlBindAddrType object. 392 If the address is specified in the DNS domain name format 393 [syslogControlBindAddrType = 'dns'], the 394 corresponding IPv4 or IPv6 address obtained at the time 395 of the binding operation by the syslog application, will be 396 used. 397 If this syslog application is not a syslog receiver, the 398 value of this object will be a zero-length string. 399 " 400 ::= { syslogControlEntry 5 } 402 syslogControlBindPort OBJECT-TYPE 403 SYNTAX InetPortNumber 404 MAX-ACCESS read-create 405 STATUS current 406 DESCRIPTION 407 "The port number that this syslog receiver will bind to. 409 If this syslog application is not a syslog receiver the 410 value of this object will be zero. 411 " 412 ::= { syslogControlEntry 6 } 414 syslogControlEncapsulation OBJECT-TYPE 415 SYNTAX SyslogEncapsulation 416 MAX-ACCESS read-create 417 STATUS current 418 DESCRIPTION 419 "The encapsulation that will be used for syslog messages 420 by the syslog receiver. 422 If this syslog application is not a syslog receiver the 423 value of this object will be ''other''. 424 " 425 ::= { syslogControlEntry 7 } 427 syslogControlMaxMessageSize OBJECT-TYPE 428 SYNTAX Unsigned32 429 MAX-ACCESS read-create 430 STATUS current 431 DESCRIPTION 432 "The maximum size of the syslog messages in bytes 433 for this syslog application. 435 A syslog receiver may reject or truncate messages larger 436 than the specified maximum syslog message size. 437 " 438 REFERENCE 439 "The Syslog Protocol [RFCPROT] sec. 6.1. 441 " 442 ::= { syslogControlEntry 8 } 444 syslogControlConfFileName OBJECT-TYPE 445 SYNTAX SnmpAdminString 446 MAX-ACCESS read-create 447 STATUS current 448 DESCRIPTION 449 "The fullpath name of the configuration file where the 450 syslog application's message selection and corresponding 451 action rules will be read from. 452 If the syslog application does not support the specification 453 of a configuration file, the value of this object will 454 be a zero-length string. 455 " 456 DEFVAL { "/etc/syslog.conf" } 457 ::= { syslogControlEntry 9 } 459 syslogControlStorageType OBJECT-TYPE 460 SYNTAX StorageType 461 MAX-ACCESS read-create 462 STATUS current 463 DESCRIPTION 464 "This object defines whether the parameters defined in 465 this row are kept in volatile storage and lost upon 466 reboot or are backed up by non-volatile or permanent 467 storage. 468 Conceptual rows having the value 'permanent' need not 469 allow write-access to any columnar objects in the row. 470 " 471 DEFVAL { nonVolatile } 472 ::= { syslogControlEntry 11 } 474 syslogControlRowStatus OBJECT-TYPE 475 SYNTAX RowStatus 476 MAX-ACCESS read-create 477 STATUS current 478 DESCRIPTION 479 "This object is used to create, modify and delete rows in 480 the syslogControlTable. 481 The value of syslogControlDescr can be changed 482 when this object is in state ''active'' or in 483 ''notInService''. 484 The other objects in a row can be modified only when the 485 value of this object in the corresponding conceptual row 486 is not ''active''. Thus to modify one or more of the 487 objects in this conceptual row, 488 a. change the row status to ''notInService'', 489 b. change the values of the row 490 c. change the row status to ''active'' 491 The syslogControlRowStatus may be changed to 492 ''active'' if all the managed objects in the conceptual 493 row with MAX-ACCESS read-create except 494 syslogControlBindPort and 495 syslogControlEncapsulation have been assigned valid 496 values. 497 " 498 ::= { syslogControlEntry 12 } 500 -- ------------------------------------------------------------- 501 -- syslogOperations 502 -- ------------------------------------------------------------- 503 syslogOperationsTable OBJECT-TYPE 504 SYNTAX SEQUENCE OF SyslogOperationsEntry 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION 508 "A table containing operations information about 509 the syslog applications serviced by an SNMP agent. 510 This table complements the (configuration) information 511 in syslogControlTable . 512 " 513 ::= { syslogObjects 2 } 515 syslogOperationsEntry OBJECT-TYPE 516 SYNTAX SyslogOperationsEntry 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 "The operations information pertaining to a syslog 521 application. 522 " 523 AUGMENTS { syslogControlEntry } 524 ::= { syslogOperationsTable 1 } 526 SyslogOperationsEntry ::= 527 SEQUENCE { 528 syslogOperationsMsgsReceived 529 Counter32, 530 syslogOperationsMsgsTransmitted 531 Counter32, 532 syslogOperationsMsgsRelayed 533 Counter32, 534 syslogOperationsMsgsDropped 535 Counter32, 536 syslogOperationsMsgsMalFormed 537 Counter32, 538 syslogOperationsMsgsDiscarded 539 Counter32, 540 syslogOperationsLastMsgRecdTime 541 TimeStamp, 542 syslogOperationsLastMsgTransmittedTime 543 TimeStamp, 544 syslogOperationsStartTime 545 TimeStamp, 546 syslogOperationsLastError 547 SnmpAdminString, 548 syslogOperationsLastErrorTime 549 TimeStamp, 550 syslogOperationsRunIndex 551 Integer32, 552 syslogOperationsCounterDiscontinuityTime 553 TimeStamp, 554 syslogOperationsStatus 555 INTEGER 556 } 558 syslogOperationsMsgsReceived OBJECT-TYPE 559 SYNTAX Counter32 560 MAX-ACCESS read-only 561 STATUS current 562 DESCRIPTION 563 "The number of messages received by the syslog 564 receiver. This includes messages that were discarded. 565 If this syslog application is not a syslog receiver the 566 value of this object will be zero. 567 Discontinuities in the value of this counter can 568 occur at re-initialization of the management system, 569 and at other times as indicated by the value of 570 syslogOperationsCounterDiscontinuityTime. 571 " 572 ::= { syslogOperationsEntry 1 } 574 syslogOperationsMsgsTransmitted OBJECT-TYPE 575 SYNTAX Counter32 576 MAX-ACCESS read-only 577 STATUS current 578 DESCRIPTION 579 "The number of messages transmitted by the syslog 580 sender. This does not include the messages that could 581 not be queued for transmission by the syslog sender. 582 If this syslog application is not a syslog sender the 583 value of this object will be zero. 584 Discontinuities in the value of this counter can 585 occur at re-initialization of the management system, 586 and at other times as indicated by the value of 587 syslogOperationsCounterDiscontinuityTime. 588 " 589 ::= { syslogOperationsEntry 2 } 591 syslogOperationsMsgsRelayed OBJECT-TYPE 592 SYNTAX Counter32 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION 596 "The number of messages relayed by the syslog 597 relay to other syslog applications. 598 If this syslog application is not a syslog relay the value 599 of this object will be zero. 600 Discontinuities in the value of this counter can 601 occur at re-initialization of the management system, 602 and at other times as indicated by the value of 603 syslogOperationsCounterDiscontinuityTime. 604 " 605 REFERENCE 606 "The Syslog Protocol [RFCPROT] sec. 3. 607 " 608 ::= { syslogOperationsEntry 3 } 610 syslogOperationsMsgsDropped OBJECT-TYPE 611 SYNTAX Counter32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "The number of messages that could not be queued 616 for transmission by the syslog sender. 617 If this syslog application is not a syslog sender the 618 value of this object will be zero. 619 Discontinuities in the value of this counter can 620 occur at re-initialization of the management system, 621 and at other times as indicated by the value of 622 syslogOperationsCounterDiscontinuityTime. 623 " 624 ::= { syslogOperationsEntry 4 } 626 syslogOperationsMsgsMalFormed OBJECT-TYPE 627 SYNTAX Counter32 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "The number of messages received by the syslog 632 receiver which had malformed header. 633 If this syslog application is not a syslog receiver, 634 then this object will have a zero value. 635 Discontinuities in the value of this counter can 636 occur at re-initialization of the management system, 637 and at other times as indicated by the value of 638 syslogOperationsCounterDiscontinuityTime. 639 " 640 REFERENCE 641 "The Syslog Protocol [RFCPROT] sec. 6.3. 642 " 643 ::= { syslogOperationsEntry 5 } 645 syslogOperationsMsgsDiscarded OBJECT-TYPE 646 SYNTAX Counter32 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "The number of messages that were discarded by the 651 syslog receiver. This will include messages that 652 were discarded because the message size was greater 653 than the system's maximum message size. 654 If this syslog application is not a syslog receiver this 655 object will have a zero value. 656 Discontinuities in the value of this counter can 657 occur at re-initialization of the management system, 658 and at other times as indicated by the value of 659 syslogOperationsCounterDiscontinuityTime. 660 " 661 REFERENCE 662 "The Syslog Protocol [RFCPROT] sec. 6.1. 663 " 664 ::= { syslogOperationsEntry 6 } 666 syslogOperationsLastMsgRecdTime OBJECT-TYPE 667 SYNTAX TimeStamp 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "The value of sysUpTime when the last message was 672 received by the syslog receiver. 673 If this syslog application is not a syslog receiver or, 674 if no messages have been received by this syslog 675 application, since the last re-initialization of the 676 local SNMP management subsystem, then this object 677 will have a zero value. 678 " 679 ::= { syslogOperationsEntry 7 } 681 syslogOperationsLastMsgTransmittedTime OBJECT-TYPE 682 SYNTAX TimeStamp 683 MAX-ACCESS read-only 684 STATUS current 685 DESCRIPTION 686 "The value of sysUpTime when the last message 687 was transmitted by the syslog sender. 688 If this syslog application is not a syslog sender or, 689 if no messages have been transmitted by this syslog 690 application, since the last re-initialization of the local 691 management subsystem, then this object will have a 692 zero value. 693 " 694 ::= { syslogOperationsEntry 8 } 696 syslogOperationsStartTime OBJECT-TYPE 697 SYNTAX TimeStamp 698 MAX-ACCESS read-only 699 STATUS current 700 DESCRIPTION 701 "The value of sysUpTime when this syslog application was 702 started. 703 " 704 ::= { syslogOperationsEntry 9 } 706 syslogOperationsLastError OBJECT-TYPE 707 SYNTAX SnmpAdminString 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 "A description of the last error related to sending, 712 receiving or processing a syslog message that was 713 encountered by this syslog application. 714 If no error has been encountered by this syslog 715 application then the value of this object will be a 716 zero-length string. 717 If no error has been encountered by this syslog 718 application since the last re-initialization of the 719 local management subsystem then the value of this 720 object will be a zero-length string. 721 " 722 ::= { syslogOperationsEntry 10 } 724 syslogOperationsLastErrorTime OBJECT-TYPE 725 SYNTAX TimeStamp 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "The value of sysUpTime when the last error was 730 encountered. 731 If no error has been encountered by this syslog 732 application since the last re-initialization of the 733 local management subsystem, then this object will 734 have a zero value. 735 " 736 ::= { syslogOperationsEntry 11 } 738 syslogOperationsRunIndex OBJECT-TYPE 739 SYNTAX Integer32 (0..2147483647) 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "If the Host resource MIB is instantiated on the 744 host then this entry will have the value of the 745 hrSWRunIndex of the corresponding entry in the 746 hrSWRunTable. 747 Note that the hrSWRunIndex is not persistent 748 across system reboots or software restarts. The 749 value of syslogOperationsRunIndex SHOULD 750 reference the latest value of the hrSWRunIndex 751 of the corresponding entry in the hrSWRunTable. 753 The special value of zero indicates that the Host 754 resource MIB is not instantiated. 755 " 756 ::= { syslogOperationsEntry 12 } 758 syslogOperationsCounterDiscontinuityTime OBJECT-TYPE 759 SYNTAX TimeStamp 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "The value of sysUpTime on the most recent occasion 764 at which any one or more of this syslog application's 765 counters, viz., counters with OID prefix 766 'syslogOperationsMsgsReceived' or 767 'syslogOperationsMsgsTransmitted' or 768 'syslogOperationsMsgsRelayed' or 769 'syslogOperationsMsgsDropped' or 770 'syslogOperationsMsgsMalFormed' or 771 'syslogOperationsMsgsDiscarded' suffered a 772 discontinuity. 773 If no such discontinuities have occurred since the 774 last re-initialization of the local management 775 subsystem, then this object will have a zero value. 776 " 777 ::= { syslogOperationsEntry 13 } 779 syslogOperationsStatus OBJECT-TYPE 780 SYNTAX INTEGER { 781 unknown (1), 782 started (2), 783 suspended(3), 784 stopped (4) 785 } 786 MAX-ACCESS read-only 787 STATUS current 788 DESCRIPTION 789 "The status of the syslog application. 790 " 791 DEFVAL { unknown } 792 ::= { syslogOperationsEntry 14 } 794 syslogPriorityTable OBJECT-TYPE 795 SYNTAX SEQUENCE OF SyslogPriorityEntry 796 MAX-ACCESS not-accessible 797 STATUS current 798 DESCRIPTION 799 "A table containing the relay configuration 800 parameters pertaining to the syslog applications 801 serviced by an SNMP agent. 802 " 803 ::= { syslogObjects 3 } 805 syslogPriorityEntry OBJECT-TYPE 806 SYNTAX SyslogPriorityEntry 807 MAX-ACCESS not-accessible 808 STATUS current 809 DESCRIPTION 810 "The relay configuration parameters pertaining to 811 a syslog application. 812 " 813 INDEX { syslogControlIndex, 814 syslogPriorityFacility, 815 syslogPrioritySeverity } 816 ::= { syslogPriorityTable 1 } 818 SyslogPriorityEntry ::= 819 SEQUENCE { 820 syslogPriorityFacility 821 SyslogFacility, 822 syslogPrioritySeverity 823 SyslogSeverity, 824 syslogPriorityDescr 825 SnmpAdminString, 826 syslogPriorityDestinationIndex 827 Unsigned32, 828 syslogPriorityStorageType 829 StorageType, 830 syslogPriorityRowStatus 831 RowStatus 832 } 834 syslogPriorityFacility OBJECT-TYPE 835 SYNTAX SyslogFacility 836 MAX-ACCESS not-accessible 837 STATUS current 838 DESCRIPTION 839 "The facility value of this entry. 840 " 841 ::= { syslogPriorityEntry 1 } 843 syslogPrioritySeverity OBJECT-TYPE 844 SYNTAX SyslogSeverity 845 MAX-ACCESS not-accessible 846 STATUS current 847 DESCRIPTION 848 "The severity value of this entry. 849 " 850 ::= { syslogPriorityEntry 2 } 852 syslogPriorityDescr OBJECT-TYPE 853 SYNTAX SnmpAdminString 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "A textual description of this priority entry. 858 " 859 ::= { syslogPriorityEntry 3 } 861 syslogPriorityDestinationIndex OBJECT-TYPE 862 SYNTAX Unsigned32 863 MAX-ACCESS read-create 864 STATUS current 865 DESCRIPTION 866 "On systems where the priority value in a syslog message 867 indicates the destination to which a syslog message 868 should be relayed, the value of this object will identify 869 the row in syslogRelayTable that contains 870 information about the relay destination to which 871 messages which have the priority value represented by 872 syslogPriorityFacility and syslogPrioritySeverity values 873 of this row will be relayed. 874 A value of 0 will indicate that there is no corresponding 875 row in the syslogRelayTable table. 876 " 877 ::= { syslogPriorityEntry 4 } 879 syslogPriorityStorageType OBJECT-TYPE 880 SYNTAX StorageType 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "This object defines whether the parameters defined in 885 this row are kept in volatile storage and lost upon 886 reboot or are backed up by non-volatile or permanent 887 storage. 888 Conceptual rows having the value 'permanent' need not 889 allow write-access to any columnar objects in the row. 890 " 891 DEFVAL { nonVolatile } 892 ::= { syslogPriorityEntry 5 } 894 syslogPriorityRowStatus OBJECT-TYPE 895 SYNTAX RowStatus 896 MAX-ACCESS read-create 897 STATUS current 898 DESCRIPTION 899 "This object is used to create, modify and delete rows 900 in the syslogPriorityTable. 901 The value of syslogPriorityDescr can be changed 902 when this object is in state ''active'' or in 903 ''notInService''. 904 The other objects in a row can be modified only when the 905 value of this object in the corresponding conceptual row 906 is not ''active''. Thus to modify one or more of the 907 objects in this conceptual row, 908 a. change the row status to ''notInService'', 909 b. change the values of the row 910 c. change the row status to ''active'' 911 The syslogPriorityRowStatus may be changed to 912 ''active'' if all the managed objects in the conceptual 913 row with MAX-ACCESS read-create have been assigned valid 914 values. 915 " 916 ::= { syslogPriorityEntry 6 } 918 syslogRelayTable OBJECT-TYPE 919 SYNTAX SEQUENCE OF SyslogRelayEntry 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "A table containing information for the relay 924 destinations. 925 " 926 ::= { syslogObjects 4 } 928 syslogRelayEntry OBJECT-TYPE 929 SYNTAX SyslogRelayEntry 930 MAX-ACCESS not-accessible 931 STATUS current 932 DESCRIPTION 933 "The information pertaining to a syslog message 934 relay destination. 935 " 936 INDEX { syslogRelayIndex } 937 ::= { syslogRelayTable 1 } 939 SyslogRelayEntry ::= 940 SEQUENCE { 941 syslogRelayIndex 942 Unsigned32, 943 syslogRelayDescr 944 SnmpAdminString, 945 syslogRelayAddrType 946 InetAddressType, 947 syslogRelayAddr 948 InetAddress, 949 syslogRelayPort 950 InetPortNumber, 951 syslogRelayEncapsulation 952 SyslogEncapsulation, 953 syslogRelayMsgsRelayed 954 Counter32, 955 syslogRelayCounterDiscontinuityTime 956 TimeStamp, 957 syslogRelayStorageType 958 StorageType, 959 syslogRelayRowStatus 960 RowStatus 961 } 963 syslogRelayIndex OBJECT-TYPE 964 SYNTAX Unsigned32 (1..2147483647) 965 MAX-ACCESS not-accessible 966 STATUS current 967 DESCRIPTION 968 "The Index that uniquely identifies the syslog 969 relay in the syslogRelayTable. 970 The value of the index for a syslog relay may 971 not be the same across system reboots. Users and 972 applications will need to determine the index of a 973 syslog relay after system reboots. 974 " 975 ::= { syslogRelayEntry 1 } 977 syslogRelayDescr OBJECT-TYPE 978 SYNTAX SnmpAdminString 979 MAX-ACCESS read-create 980 STATUS current 981 DESCRIPTION 982 "A user definable description of the syslog relay. 983 This description could be used by syslog management 984 applications e.g. in reports or in user interfaces. 985 " 986 ::= { syslogRelayEntry 2 } 988 syslogRelayAddrType OBJECT-TYPE 989 SYNTAX InetAddressType 990 MAX-ACCESS read-create 991 STATUS current 992 DESCRIPTION 993 "The type of Internet address which follows 994 in syslogRelayAddr. 995 " 996 ::= { syslogRelayEntry 3 } 998 syslogRelayAddr OBJECT-TYPE 999 SYNTAX InetAddress 1000 MAX-ACCESS read-create 1001 STATUS current 1002 DESCRIPTION 1003 "The address of the syslog relay . 1004 The format of the address is specified by the 1005 corresponding syslogRelayAddrType object. 1006 If the address is specified in the DNS domain name format 1007 [syslogRelayAddrType = 'dns'], the 1008 corresponding IPv4 or IPv6 address obtained at the time 1009 of the relay operation by the syslog application, will be 1010 used. 1011 " 1012 ::= { syslogRelayEntry 4 } 1014 syslogRelayPort OBJECT-TYPE 1015 SYNTAX InetPortNumber 1016 MAX-ACCESS read-create 1017 STATUS current 1018 DESCRIPTION 1019 "The port number of the syslog relay. 1020 " 1021 ::= { syslogRelayEntry 5 } 1023 syslogRelayEncapsulation OBJECT-TYPE 1024 SYNTAX SyslogEncapsulation 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "The encapsulation that will be used for syslog messages 1029 sent by the syslog sender to the relay destination. 1030 " 1031 ::= { syslogRelayEntry 6 } 1033 syslogRelayMsgsRelayed OBJECT-TYPE 1034 SYNTAX Counter32 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "The number of messages relayed by the syslog 1039 relay to this relay destination. 1040 Discontinuities in the value of this counter can 1041 occur at re-initialization of the management system, 1042 and at other times as indicated by the value of 1043 syslogRelayCounterDiscontinuityTime. 1044 " 1045 REFERENCE 1046 "The Syslog Protocol [RFCPROT] sec. 3. 1047 " 1048 ::= { syslogRelayEntry 7 } 1050 syslogRelayCounterDiscontinuityTime OBJECT-TYPE 1051 SYNTAX TimeStamp 1052 MAX-ACCESS read-only 1053 STATUS current 1054 DESCRIPTION 1055 "The value of sysUpTime on the most recent occasion 1056 at which counters with OID prefix 1057 'syslogRelayMsgsRelayed' suffered a 1058 discontinuity. 1060 If no such discontinuities have occurred since the 1061 last re-initialization of the local management 1062 subsystem, then this object will have a zero value. 1063 " 1064 ::= { syslogRelayEntry 8 } 1066 syslogRelayStorageType OBJECT-TYPE 1067 SYNTAX StorageType 1068 MAX-ACCESS read-create 1069 STATUS current 1070 DESCRIPTION 1071 "This object defines whether the parameters defined in 1072 this row are kept in volatile storage and lost upon 1073 reboot or are backed up by non-volatile or permanent 1074 storage. 1075 Conceptual rows having the value 'permanent' need not 1076 allow write-access to any columnar objects in the row. 1077 " 1078 DEFVAL { nonVolatile } 1079 ::= { syslogRelayEntry 9 } 1081 syslogRelayRowStatus OBJECT-TYPE 1082 SYNTAX RowStatus 1083 MAX-ACCESS read-create 1084 STATUS current 1085 DESCRIPTION 1086 "This object is used to create, modify and delete rows 1087 in the syslogRelayTable. 1088 The value of syslogRelayDescr can be changed 1089 when this object is in state ''active'' or in 1090 ''notInService''. 1091 The other objects in a row can be modified only when the 1092 value of this object in the corresponding conceptual row 1093 is not ''active''. Thus to modify one or more of the 1094 objects in this conceptual row, 1095 a. change the row status to ''notInService'', 1096 b. change the values of the row 1097 c. change the row status to ''active'' 1098 The syslogRelayRowStatus may be changed to 1099 ''active'' if all the managed objects in the conceptual 1100 row with MAX-ACCESS read-create have been assigned valid 1101 values. 1102 " 1103 ::= { syslogRelayEntry 10 } 1105 syslogStatusChanged NOTIFICATION-TYPE 1106 OBJECTS { 1107 syslogControlDescr, 1108 syslogControlRoles, 1109 syslogControlBindAddrType, 1110 syslogControlBindAddr, 1111 syslogControlBindPort, 1112 syslogControlEncapsulation, 1113 syslogControlConfFileName, 1114 syslogOperationsStatus 1115 } 1116 STATUS current 1117 DESCRIPTION 1118 "This notification is sent when a syslog application 1119 changes state. For example when the syslog application 1120 starts [syslogOperationsStatus is ''started'' ] 1121 or the syslog application stops [syslogOperationsStatus 1122 is ''suspended'' or ''stopped'']. 1123 The value of syslogOperationsStatus will be the 1124 new status of the syslog application after the change. 1125 The syslog application corresponding to the notification 1126 will be identified by the syslogOperationsIndex 1127 instance identifier of the objects in the notification. 1128 " 1129 ::= { syslogNotifications 1 } 1131 -- ------------------------------------------------------------- 1132 -- Conformance Information 1133 -- ------------------------------------------------------------- 1135 syslogGroups OBJECT IDENTIFIER 1136 ::= { syslogConformance 1 } 1138 syslogCompliances OBJECT IDENTIFIER 1139 ::= { syslogConformance 2 } 1141 -- ------------------------------------------------------------- 1142 -- units of conformance 1143 -- ------------------------------------------------------------- 1145 syslogOperationsGroup OBJECT-GROUP 1146 OBJECTS { 1147 -- syslogOperationsIndex, 1148 syslogOperationsMsgsReceived, 1149 syslogOperationsMsgsTransmitted, 1150 syslogOperationsMsgsRelayed, 1151 syslogOperationsMsgsDropped, 1152 syslogOperationsMsgsMalFormed, 1153 syslogOperationsMsgsDiscarded, 1154 syslogOperationsLastMsgRecdTime, 1155 syslogOperationsLastMsgTransmittedTime, 1156 syslogOperationsStartTime, 1157 syslogOperationsLastError, 1158 syslogOperationsLastErrorTime, 1159 syslogOperationsRunIndex, 1160 syslogOperationsCounterDiscontinuityTime, 1161 syslogOperationsStatus 1162 } 1163 STATUS current 1164 DESCRIPTION 1165 "A collection of objects providing message related 1166 statistics." 1167 ::= { syslogGroups 1} 1169 syslogControlGroup OBJECT-GROUP 1170 OBJECTS { 1171 syslogControlDescr, 1172 syslogControlRoles, 1173 syslogControlBindAddrType, 1174 syslogControlBindAddr, 1175 syslogControlEncapsulation, 1176 syslogControlBindPort, 1177 syslogControlMaxMessageSize, 1178 syslogControlConfFileName, 1179 syslogControlStorageType, 1180 syslogControlRowStatus 1181 } 1182 STATUS current 1183 DESCRIPTION 1184 "A collection of objects representing the run time parameters 1185 for the syslog applications. 1186 " 1187 ::= { syslogGroups 2} 1189 syslogPriorityGroup OBJECT-GROUP 1190 OBJECTS { 1191 syslogPriorityDescr, 1192 syslogPriorityDestinationIndex, 1193 syslogPriorityStorageType, 1194 syslogPriorityRowStatus 1195 } 1196 STATUS current 1197 DESCRIPTION 1198 "A collection of objects representing the priority 1199 groupings of syslog messages. 1200 " 1201 ::= { syslogGroups 3} 1203 syslogRelayGroup OBJECT-GROUP 1204 OBJECTS { 1205 syslogRelayDescr, 1206 syslogRelayAddrType, 1207 syslogRelayAddr, 1208 syslogRelayPort, 1209 syslogRelayEncapsulation, 1210 syslogRelayMsgsRelayed, 1211 syslogRelayCounterDiscontinuityTime, 1212 syslogRelayStorageType, 1213 syslogRelayRowStatus 1214 } 1215 STATUS current 1216 DESCRIPTION 1217 "A collection of objects representing the relay 1218 destinations for syslog messages. 1219 " 1220 ::= { syslogGroups 4} 1222 syslogNotificationGroup NOTIFICATION-GROUP 1223 NOTIFICATIONS { 1224 syslogStatusChanged 1225 } 1226 STATUS current 1227 DESCRIPTION 1228 "A collection of notifications about the operational 1229 state of a syslog application. 1230 " 1231 ::= { syslogGroups 5} 1233 -- ------------------------------------------------------------- 1234 -- compliance statements 1235 -- ------------------------------------------------------------- 1237 syslogFullCompliance1 MODULE-COMPLIANCE 1238 STATUS current 1239 DESCRIPTION 1240 "The compliance statement for SNMP entities which 1241 implement the SYSLOG-MIB with support for writable 1242 objects and notifications. Such an implementation can 1243 be both monitored and configured via SNMP. It can 1244 also send notifications about change in the 1245 operational status of the syslog application. 1246 " 1247 MODULE -- this module 1248 MANDATORY-GROUPS { 1249 syslogNotificationGroup, 1250 syslogOperationsGroup, 1251 syslogControlGroup, 1252 syslogPriorityGroup, 1253 syslogRelayGroup 1254 } 1256 ::= { syslogCompliances 1 } 1258 syslogFullCompliance2 MODULE-COMPLIANCE 1259 STATUS current 1260 DESCRIPTION 1261 "The compliance statement for SNMP entities which 1262 implement the SYSLOG-MIB with support for writable 1263 objects. Such an implementation can 1264 be both monitored and configured via SNMP. 1265 " 1266 MODULE -- this module 1267 MANDATORY-GROUPS { 1268 syslogOperationsGroup, 1269 syslogControlGroup, 1270 syslogPriorityGroup, 1271 syslogRelayGroup 1272 } 1274 ::= { syslogCompliances 2 } 1276 syslogFullCompliance3 MODULE-COMPLIANCE 1277 STATUS current 1278 DESCRIPTION 1279 "The compliance statement for SNMP entities which 1280 implement the SYSLOG-MIB with support for writable 1281 objects but without support for the objects in 1282 syslogPriorityGroup and syslogRelayGroup. Such an 1283 implementation can be both monitored and configured 1284 via SNMP. 1285 " 1286 MODULE -- this module 1287 MANDATORY-GROUPS { 1288 syslogOperationsGroup, 1289 syslogControlGroup 1290 } 1292 ::= { syslogCompliances 3 } 1294 syslogReadOnlyCompliance1 MODULE-COMPLIANCE 1295 STATUS current 1296 DESCRIPTION 1297 "The compliance statement for SNMP entities which 1298 implement the syslog MIB without support 1299 for read-write (i.e. in read-only mode). It can 1300 also send notifications about change in the 1301 operational status of the syslog application. 1302 " 1303 MODULE -- this module 1304 MANDATORY-GROUPS { 1305 syslogNotificationGroup, 1306 syslogOperationsGroup, 1307 syslogControlGroup, 1308 syslogPriorityGroup, 1309 syslogRelayGroup 1310 } 1312 OBJECT syslogControlDescr 1313 MIN-ACCESS read-only 1314 DESCRIPTION 1315 "Write access is not required. 1316 " 1317 OBJECT syslogControlRoles 1318 MIN-ACCESS read-only 1319 DESCRIPTION 1320 "Write access is not required. 1321 " 1323 OBJECT syslogControlBindAddrType 1324 MIN-ACCESS read-only 1325 DESCRIPTION 1326 "Write access is not required. 1327 " 1328 OBJECT syslogControlBindAddr 1329 MIN-ACCESS read-only 1330 DESCRIPTION 1331 "Write access is not required. 1332 " 1333 OBJECT syslogControlBindPort 1334 MIN-ACCESS read-only 1335 DESCRIPTION 1336 "Write access is not required. 1337 " 1338 OBJECT syslogControlEncapsulation 1339 MIN-ACCESS read-only 1340 DESCRIPTION 1341 "Write access is not required. 1342 " 1343 OBJECT syslogControlMaxMessageSize 1344 MIN-ACCESS read-only 1345 DESCRIPTION 1346 "Write access is not required. 1347 " 1348 OBJECT syslogControlConfFileName 1349 MIN-ACCESS read-only 1350 DESCRIPTION 1351 "Write access is not required. 1352 " 1353 OBJECT syslogControlStorageType 1354 MIN-ACCESS read-only 1355 DESCRIPTION 1356 "Write access is not required. 1357 " 1358 OBJECT syslogControlRowStatus 1359 MIN-ACCESS read-only 1360 DESCRIPTION 1361 "Write access is not required. 1362 " 1364 ::= { syslogCompliances 4 } 1366 syslogReadOnlyCompliance2 MODULE-COMPLIANCE 1367 STATUS current 1368 DESCRIPTION 1369 "The compliance statement for SNMP entities which 1370 implement the syslog MIB without support 1371 for read-write (i.e. in read-only mode). 1372 " 1373 MODULE -- this module 1374 MANDATORY-GROUPS { 1375 syslogOperationsGroup, 1376 syslogControlGroup, 1377 syslogPriorityGroup, 1378 syslogRelayGroup 1379 } 1381 OBJECT syslogControlDescr 1382 MIN-ACCESS read-only 1383 DESCRIPTION 1384 "Write access is not required. 1385 " 1386 OBJECT syslogControlRoles 1387 MIN-ACCESS read-only 1388 DESCRIPTION 1389 "Write access is not required. 1390 " 1391 OBJECT syslogControlBindAddrType 1392 MIN-ACCESS read-only 1393 DESCRIPTION 1394 "Write access is not required. 1395 " 1396 OBJECT syslogControlBindAddr 1397 MIN-ACCESS read-only 1398 DESCRIPTION 1399 "Write access is not required. 1400 " 1401 OBJECT syslogControlBindPort 1402 MIN-ACCESS read-only 1403 DESCRIPTION 1404 "Write access is not required. 1405 " 1406 OBJECT syslogControlEncapsulation 1407 MIN-ACCESS read-only 1408 DESCRIPTION 1409 "Write access is not required. 1410 " 1412 OBJECT syslogControlMaxMessageSize 1413 MIN-ACCESS read-only 1414 DESCRIPTION 1415 "Write access is not required. 1416 " 1417 OBJECT syslogControlConfFileName 1418 MIN-ACCESS read-only 1419 DESCRIPTION 1420 "Write access is not required. 1421 " 1422 OBJECT syslogControlStorageType 1423 MIN-ACCESS read-only 1424 DESCRIPTION 1425 "Write access is not required. 1426 " 1427 OBJECT syslogControlRowStatus 1428 MIN-ACCESS read-only 1429 DESCRIPTION 1430 "Write access is not required. 1431 " 1432 OBJECT syslogPriorityDescr 1433 MIN-ACCESS read-only 1434 DESCRIPTION 1435 "Write access is not required. 1436 " 1437 OBJECT syslogPriorityDestinationIndex 1438 MIN-ACCESS read-only 1439 DESCRIPTION 1440 "Write access is not required. 1441 " 1442 OBJECT syslogPriorityStorageType 1443 MIN-ACCESS read-only 1444 DESCRIPTION 1445 "Write access is not required. 1446 " 1447 OBJECT syslogPriorityRowStatus 1448 MIN-ACCESS read-only 1449 DESCRIPTION 1450 "Write access is not required. 1451 " 1452 OBJECT syslogRelayDescr 1453 MIN-ACCESS read-only 1454 DESCRIPTION 1455 "Write access is not required. 1456 " 1458 OBJECT syslogRelayAddrType 1459 MIN-ACCESS read-only 1460 DESCRIPTION 1461 "Write access is not required. 1462 " 1463 OBJECT syslogRelayAddr 1464 MIN-ACCESS read-only 1465 DESCRIPTION 1466 "Write access is not required. 1467 " 1468 OBJECT syslogRelayPort 1469 MIN-ACCESS read-only 1470 DESCRIPTION 1471 "Write access is not required. 1472 " 1473 OBJECT syslogRelayEncapsulation 1474 MIN-ACCESS read-only 1475 DESCRIPTION 1476 "Write access is not required. 1477 " 1478 OBJECT syslogRelayStorageType 1479 MIN-ACCESS read-only 1480 DESCRIPTION 1481 "Write access is not required. 1482 " 1483 OBJECT syslogRelayRowStatus 1484 MIN-ACCESS read-only 1485 DESCRIPTION 1486 "Write access is not required. 1487 " 1488 ::= { syslogCompliances 5 } 1490 syslogReadOnlyCompliance3 MODULE-COMPLIANCE 1491 STATUS current 1492 DESCRIPTION 1493 "The compliance statement for SNMP entities which 1494 implement the syslog MIB without support 1495 for read-write (i.e. in read-only mode) and without 1496 support for the objects in syslogRelayGroup and 1497 syslogPriorityGroup. 1498 " 1499 MODULE -- this module 1500 MANDATORY-GROUPS { 1501 syslogOperationsGroup, 1502 syslogControlGroup 1503 } 1505 OBJECT syslogControlDescr 1506 MIN-ACCESS read-only 1507 DESCRIPTION 1508 "Write access is not required. 1509 " 1510 OBJECT syslogControlRoles 1511 MIN-ACCESS read-only 1512 DESCRIPTION 1513 "Write access is not required. 1514 " 1515 OBJECT syslogControlBindAddrType 1516 MIN-ACCESS read-only 1517 DESCRIPTION 1518 "Write access is not required. 1519 " 1520 OBJECT syslogControlBindAddr 1521 MIN-ACCESS read-only 1522 DESCRIPTION 1523 "Write access is not required. 1524 " 1525 OBJECT syslogControlBindPort 1526 MIN-ACCESS read-only 1527 DESCRIPTION 1528 "Write access is not required. 1529 " 1530 OBJECT syslogControlEncapsulation 1531 MIN-ACCESS read-only 1532 DESCRIPTION 1533 "Write access is not required. 1534 " 1536 OBJECT syslogControlMaxMessageSize 1537 MIN-ACCESS read-only 1538 DESCRIPTION 1539 "Write access is not required. 1540 " 1541 OBJECT syslogControlConfFileName 1542 MIN-ACCESS read-only 1543 DESCRIPTION 1544 "Write access is not required. 1545 " 1546 OBJECT syslogControlStorageType 1547 MIN-ACCESS read-only 1548 DESCRIPTION 1549 "Write access is not required. 1550 " 1551 OBJECT syslogControlRowStatus 1552 MIN-ACCESS read-only 1553 DESCRIPTION 1554 "Write access is not required. 1555 " 1556 ::= { syslogCompliances 6 } 1558 syslogNotificationCompliance MODULE-COMPLIANCE 1559 STATUS current 1560 DESCRIPTION 1561 "The compliance statement for SNMP entities 1562 which implement the SYSLOG-MIB and support 1563 only notifications about change in the 1564 operational status of a syslog application. 1565 " 1566 MODULE -- this module 1567 MANDATORY-GROUPS { 1568 syslogNotificationGroup 1569 } 1571 ::= { syslogCompliances 7 } 1573 END 1575 5. Security Considerations 1577 Syslog plays a very important role in the computer and network 1578 security of an organization. SYSLOG-MIB defines several managed 1579 objects that may be used to monitor, configure and control syslog 1580 applications. As such improper manipulation of the objects 1581 represented by this MIB may lead to an attack on an important 1582 component of the computer and network security infrastructure. The 1583 objects in syslogControlTable, syslogPriorityTable and 1584 syslogRelayTable may be misconfigured to cause syslog messages to be 1585 diverted or lost. 1587 There are a number of management objects defined in this MIB module 1588 with a MAX-ACCESS clause of read-write and/or read-create. Such 1589 objects may be considered sensitive or vulnerable in some network 1590 environments. The support for SET operations in a non-secure 1591 environment without proper protection can have a negative effect on 1592 network operations. These are the tables and objects and their 1593 sensitivity/vulnerability: 1595 o syslogControlTable: The objects in this table 1596 describe the configuration of the syslog applications. 1597 It may be misconfigured to start up a very large 1598 number of syslog applications (processes) and deny the 1599 system of its resources. 1600 o syslogControlBindAddr: This object may be 1601 misconfigured to bind syslog application to the wrong 1602 address. This will cause messages to be lost. 1603 o syslogControlBindPort : This object may be 1604 misconfigured to bind syslog application to the wrong 1605 service (port). This will cause messages to be lost. 1606 o syslogControlMaxMessageSize: This message may be 1607 misconfigured to set the wrong MaxMessageSize for the 1608 syslog application. It may cause syslog messages to be 1609 lost. 1610 o syslogControlConfFileName: This object may be 1611 misconfigured to start the syslog application with the 1612 wrong (rogue) configuration. 1613 o syslogControlStorageType: This object may be 1614 misconfigured to set the wrong storage type. That may 1615 cause confusion, operational errors and/or loss of 1616 information. 1617 o syslogPriorityTable: The objects in this table 1618 link the priority value in a syslog message to the 1619 entry in the syslogRelayTable corresponding to the 1620 syslog collector to which the syslog message should be 1621 relayed. The table may be misconfigured to redirect 1622 a syslog message to a potentially non-existent wrong 1623 destination and/or to redirect a large number of messages 1624 to a particular syslog collector. 1625 o syslogRelayTable: The rows in this table represent 1626 the relays to which syslog messages will be relayed, 1627 depending on the priority value in the respective 1628 syslog messages. The table may be misconfigured to 1629 redirect a syslog message to a potentially non-existent 1630 wrong destination and/or redirect a large number of 1631 messages to a particular syslog collector. 1633 Some of the readable objects in this MIB module (i.e., objects with a 1634 MAX-ACCESS other than not-accessible) may be considered sensitive or 1635 vulnerable in some network environments. It is thus important to 1636 control even GET and/or NOTIFY access to these objects and possibly 1637 to even encrypt the values of these objects when sending them over 1638 the network via SNMP. These are the tables and objects and their 1639 sensitivity/vulnerability: 1641 o syslogOperationsTable: Objects in this table carry 1642 sensitive information. The counters may reveal 1643 information about the deployment and effectiveness of 1644 the relevant security systems. The counters may be 1645 analyzed to tell whether the security systems are able 1646 to detect an event or not. 1648 o syslogOperationsLastError: This object may contain 1649 sensitive information e.g. user-id, password etc. 1650 depending on the implementation of the syslog application. 1651 It may reveal details about the syslog implementation 1652 itself, e.g. version, OS etc. 1654 o syslogPriorityTable: Objects in this table carry 1655 sensitive information. The objects reveal how the 1656 syslog messages are grouped, relayed and/or stored. 1658 o syslogRelayTable: Objects in this table carry sensitive 1659 information. The objects reveal the destination of 1660 syslog messages. 1662 SNMP versions prior to SNMPv3 did not include adequate security. 1663 Even if the network itself is secure (for example by using IPsec), 1664 even then, there is no control as to who on the secure network is 1665 allowed to access and GET/SET (read/change/create/delete) the objects 1666 in this MIB module. 1668 It is RECOMMENDED that implementers consider the security features as 1669 provided by the SNMPv3 framework (see [RFC3410], section 8), 1670 including full support for the SNMPv3 cryptographic mechanisms (for 1671 authentication and privacy). 1673 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1674 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1675 enable cryptographic security. It is then a customer/operator 1676 responsibility to ensure that the SNMP application giving access to 1677 an instance of this MIB module is properly configured to give access 1678 to the objects only to those principals (users) that have legitimate 1679 rights to indeed GET or SET (change/create/delete) them. 1681 6. IANA Considerations 1683 The MIB modules in this document use the following IANA-assigned 1684 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1686 Descriptor OBJECT IDENTIFIER value 1687 ---------- ----------------------- 1689 syslogMIB { mib-2 YYYY } 1691 IANA Reg.: Please assign a value under the 'mib-2' subtree 1692 for the 'syslogMIB' MODULE-IDENTITY and record 1693 the assignment in the SMI Numbers registry. 1695 RFC Ed.: When the above assignments have been made, please 1696 - remove the above note 1697 - replace "YYYY" here with the assigned values and 1698 - remove this note. 1700 7. References 1702 7.1 Normative References 1704 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1705 Requirements Levels", BCP 14, RFC 2119, March 1997. 1707 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1708 Rose, M., and S. Waldbusser, "Structure of Management 1709 Information Version 2 (SMIv2)", STD 58, RFC 2578, 1710 April 1999 1712 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1713 Rose, M., and S. Waldbusser, "Textual Conventions for 1714 SMIv2", STD 58, RFC 2579, April 1999 1716 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1717 Rose, M., and S. Waldbusser, "Conformance Statements for 1718 SMIv2", STD 58, RFC 2580, April 1999 1720 [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture 1721 for Describing Simple Network Management Protocol (SNMP) 1722 Management Frameworks", STD 62, RFC 3411, December 2002. 1724 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and Schoenwaelder, 1725 J., "Textual Conventions for Internet Network Addresses", 1726 RFC 4001, February 2005. 1728 [RFCPROT] Gerhards, R., "The syslog Protocol", 1729 draft-ietf-syslog-protocol-21.txt, work in progress, 1730 June 2006. 1732 [RFCUDPX] Okmianski, A., "Transmission of syslog messages over UDP", 1733 draft-ietf-syslog-transport-udp-09.txt work in progress, 1734 May 2006. 1736 [RFCTLSX] Miao, F., and Yuzhi, M., "TLS Transport Mapping for Syslog", 1737 draft-ietf-syslog-transport-tls-10.txt, work in progress, 1738 December 2006. 1740 [RFC3195] New, D., and Rose, M., "Reliable Delivery for syslog", 1741 RFC 3195, November 2001 1743 7.2 Informative References 1745 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1746 "Introduction and Applicability Statements for the 1747 Internet-Standard Management Framework", RFC 3410, 1748 December 2002. 1750 [RFC2790] Waldbusser, S., and Grillo, P., "Host Resources MIB", 1751 RFC 2790, March 2000. 1753 Note: The strings "PROT", "UDPX" and "TLSX" in this 1754 document will be replaced by the RFC numbers assigned 1755 to the latest versions of 1756 draft-ietf-syslog-protocol-*.txt, 1757 draft-ietf-syslog-transport-udp-*.txt and 1758 draft-ietf-syslog-transport-tls-*.txt, 1759 respectively, and this note will be removed. 1761 8. Acknowledgments 1762 The initial draft of this document was authored by Bruno Pape. 1763 The authors would like to thank Mark Ellison, David Harrington, 1764 Mike MacFaden, Dave T Perkins, Tom Petch, Juergen Schoenwaelder, 1765 Rohit M, Bert Wijnen and members of the WIDE-netman group for 1766 their comments and suggestions. 1768 9. Author's Addresses 1770 Glenn Mansfield Keeni 1771 Cyber Solutions Inc. 1772 6-6-3 Minami Yoshinari 1773 Aoba-ku, Sendai 989-3204 1774 Japan 1776 Phone: +81-22-303-4012 1777 EMail: glenn@cysols.com 1779 10. Full Copyright Statement 1781 Copyright (C) The IETF Trust (2008). 1783 This document is subject to the rights, licenses and restrictions 1784 contained in BCP 78, and except as set forth therein, the authors 1785 retain all their rights. 1787 This document and the information contained herein are provided on 1788 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1789 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 1790 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 1791 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 1792 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY 1793 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1794 PARTICULAR PURPOSE. 1796 Intellectual Property 1798 The IETF takes no position regarding the validity or scope of any 1799 Intellectual Property Rights or other rights that might be claimed 1800 to pertain to the implementation or use of the technology 1801 described in this document or the extent to which any license 1802 under such rights might or might not be available; nor does it 1803 represent that it has made any independent effort to identify any 1804 such rights. Information on the procedures with respect to 1805 rights in RFC documents can be found in BCP 78 and BCP 79. 1807 Copies of IPR disclosures made to the IETF Secretariat and any 1808 assurances of licenses to be made available, or the result of an 1809 attempt made to obtain a general license or permission for the use 1810 of such proprietary rights by implementers or users of this 1811 specification can be obtained from the IETF on-line IPR repository 1812 at http://www.ietf.org/ipr. 1814 The IETF invites any interested party to bring to its attention 1815 any copyrights, patents or patent applications, or other 1816 proprietary rights that may cover technology that may be required 1817 to implement this standard. Please address the information to the 1818 IETF at ietf-ipr@ietf.org. 1820 Acknowledgment 1822 Funding for the RFC Editor function is provided by the IETF 1823 Administrative Support Activity (IASA). 1825 APPENDIX 1827 This section documents the development of the draft. It will be 1828 deleted when the draft becomes an RFC. 1830 Revision History: 1831 Changes from draft-ietf-syslog-device-mib-15.txt 1832 to draft-ietf-syslog-device-mib-16.txt 1833 1. The definitions of the TEXTUAL-CONVENTIONS SyslogFacility and 1834 SyslogSeverity are deleted. These are now imported from 1835 SYSLOG-TC-MIB 1836 2. Two tables 1837 syslogPriorityTable and 1838 syslogRelayTable 1839 have been added. 1840 3. The compliance statements corresponding the new tables 1841 are added. 1842 4. The Security considerations corresponding to the new 1843 yables are added. 1844 Changes from draft-ietf-syslog-device-mib-14.txt 1845 to draft-ietf-syslog-device-mib-15.txt 1846 1. Revised syslogControlService to represent only a port number, 1847 and not a service name 1848 Renamed syslogControlService to syslogControlBindPort 1849 2. Eliminated "entity" wording and used "syslog application". 1850 3. The default objects are removed. 1852 +--syslogSystem(1) 1853 | +-- syslogDefaultService(1) 1854 | +-- syslogDefaultEncapsulation(2) 1855 and the corresponding conformance group 1856 +--syslogGroups(1) 1857 | +--syslogDefaultGroup(1) 1859 4. Descriptions of objects that had references to the default 1860 objects are revised. 1862 5. The Textual Conventions for SyslogSeverity and SyslogFacility 1863 are put back. ( This did not happen in -14.txt though it is 1864 listed in the changes.) 1866 6. The references in the MIB module have been revised to make 1867 the MIB module references independent of the container 1868 document. 1870 7. Noted that the strings "PROT", "UDPX" and "TLSX" in this 1871 document will be replaced by the respective RFC numbers 1872 assigned to the corresponding documents. 1874 Changes from draft-ietf-syslog-device-mib-13.txt 1875 to draft-ietf-syslog-device-mib-14.txt 1877 1. Changed the object hierarchy and naming from 1879 | 1880 +--syslogObjects(1) 1881 | | 1882 | +--syslogSystem(1) 1883 | | 1884 | +--syslogEntity(2) 1885 | | 1886 | +--syslogEntityControlTable(1) 1887 | | 1888 | +--syslogEntityOperationsTable(2) 1890 to 1892 | 1893 +--syslogObjects(1) 1894 | | 1895 | +--syslogSystem(1) 1896 | | 1897 | +--syslogControlTable(2) 1898 | | 1899 | +--syslogOperationsTable(3) 1900 | 1902 2. Removed the reference to UDP transport in section 2. 1903 3. Put back SyslogSeverity and SyslogFacility TCs. 1904 4. Revised the DESCRIPTION of syslogOperationsMsgsReceived 1905 5. Added syslogOperationsMsgsTransmitted 1906 6. Revised the DESCRIPTION of syslogOperationsLastMsgRecdTime 1907 7. Renamed syslogOperationsReference to syslogOperationsRunIndex 1909 Changes from draft-ietf-syslog-device-mib-12.txt 1910 to draft-ietf-syslog-device-mib-13.txt 1912 1. Removed reference to RFC3164. 1913 2. Added TC SyslogEncapsulation 1914 removed syslogDefaultTransportDomain, 1915 syslogEntityControlTransportDomain 1916 Added syslogDefaultEncapsulation, 1917 syslogEntityControlEncapsulation 1919 3. Modified the DESCRIPTION clauses for 1920 syslogEntityControlMaxMessageSize, 1921 syslogEntityOperationsMsgsReceived, 1922 syslogEntityOperationsMsgsRelayed, 1923 syslogEntityOperationsMsgsIllFormed, 1924 syslogEntityOperationsMsgsIgnored, 1926 4. Changed name 1927 from syslogEntityOperationsMsgsIllFormed 1928 to syslogEntityOperationsMsgsMalFormed 1930 from syslogEntityOperationsMsgsIgnored 1931 to syslogEntityOperationsMsgsDiscarded 1933 5. Revised figure 1. 1935 6. Added MO syslogEntityControlRoles 1937 7. renamed syslogEntityControlStatus to 1938 syslogEntityOperationsStatus 1939 moved this object from 1940 syslogEntityControlEntry to 1941 syslogEntityOperationsEntry 1943 8. Removed MOs syslogDefaultFacility 1944 syslogDefaultSeverity 1946 9. Removed TCs SyslogFacility 1947 SyslogSeverity 1949 10. Added the TC SyslogRoles 1951 11. Added the MO syslogEntityControlRoles 1953 12. Replaced references to "local time" by "value 1954 of sysUpTime" 1955 13. Revised the DESCRIPTION syslogEntityStatusChange 1957 14. Revised the DESCRIPTION of the MOs to cover the 1958 exception cases. 1960 15. Revised the text to clear ambiguities about the 1961 role of the "syslog entity". 1962 16. Editorial nits. 1964 Changes from draft-ietf-syslog-device-mib-11.txt 1965 to draft-ietf-syslog-device-mib-12.txt 1967 1. Added text in introduction and in the DESCRIPTION of the MIB 1968 module to explain the terminology used in the document. 1969 Ref. Comment 1.1, 1.2, 1.3, 1.4. 1970 2. Changed "group" to "subtree" in Section 3 (The MIB Design). 1971 Ref. Comment 1.5 1972 3. Removed enumeration "other" from the enumeration for 1973 SyslogSeverity. This case does not arise. 1974 Ref. Comment 1.6 1976 4. Revised DESCRIPTION of syslogEntityControlStorageType 1977 Ref. comment 2.3 1978 5. Revised DESCRIPTION of syslogEntityStatusChanged 1979 Ref. Comment 2.4 1980 6. Updated the boilerplate for the Copyright notice. 1981 Ref. Comment 2.7 1983 7. Changed "should" to "SHOULD" in DESCRIPTION of 1984 syslogEntityOperationsReference 1985 Ref. Comment 3.2 1986 8. Changed RFCPROT to "[RFCPROT]" in REFERENCE of 1987 syslogDefaultTransportDomain 1989 Changes from draft-ietf-syslog-device-mib-9.txt 1990 to draft-ietf-syslog-device-mib-11.txt 1991 [Note: The changes to the mib-9.txt and mib-10.txt are 1992 consolidated below.] 1993 1. Namings changed: 1994 Page-8. 1995 changed the duplicate instances of auth and cron to 1996 auth1, auth2, cron1, cron2 1997 changed: SyslDevOpsEntry -> SyslogEntityOperationsEntry 1998 syslEntOpsEntry -> syslogEntityOperationsEntry 1999 SyslDevCtlEntry -> SyslogEntityControlEntry 2000 syslEntCtlEntry -> syslogEntityControlEntry 2001 syslEntOpsTable -> syslogEntityOperationsTable 2002 syslogDevice -> syslogDevice 2003 syslEntCtlProcDescr -> syslogEntityControlDescr 2004 syslEntOpsLastMsgDeliveredTime -> 2005 syslogEntityOperationsLastMsgTransmittedTime. 2006 syslDevOpsGroup -> syslogEntityOperationsGroup 2008 2. Added TRANSPORT-ADDRESS-MIB[RFC3419] to the text on section 3 2009 (and 7.1 Normative References). 2011 3. MIB. 2012 Fixed MIB nits. 2014 4. Added text about the expected persistency behaviour of the 2015 read-write objects in the corresponding DESCRIPTION clauses. 2016 syslogDefaultTransport 2017 syslogDefaultService 2018 syslogDefaultFacility 2019 syslogDefaultSeverity 2021 5. Replaced 2022 syslogDefaultTransport OBJECT-TYPE 2023 SYNTAX TransportAddressType 2024 and 2025 syslEntCtlTransport OBJECT-TYPE 2026 SYNTAX TransportAddressType 2027 by 2028 syslogDefaultTransportDomain OBJECT-TYPE 2029 SYNTAX TransportDomain 2030 syslogEntityControlTransportDomain OBJECT-TYPE 2031 SYNTAX TransportDomain 2033 6. Changed the ordering of 2034 syslEntOpsTable ::= { syslogDevice 1 } 2035 syslEntCtlTable ::= { syslogDevice 2 } 2036 to 2037 syslogEntityControlTable ::= { syslogEntity 1 } 2038 syslogEntityOperationsTable ::= { syslogEntity 2 } 2040 7. The tree structure is changed 2041 from 2043 syslogSystem OBJECT IDENTIFIER 2044 ::= { syslogMIB 1 } 2046 syslogDevice OBJECT IDENTIFIER 2047 ::= { syslogMIB 2 } 2049 to, 2050 syslogObjects OBJECT IDENTIFIER 2051 ::= { syslogMIB 1 } 2053 syslogSystem OBJECT IDENTIFIER 2054 ::= { syslogObjects 1 } 2056 syslogEntity OBJECT IDENTIFIER 2057 ::= { syslogObjects 2 } 2059 8. syslogEntityOperationsEntry AUGMENTS { syslogEntityControlEntry } 2061 9. Added 2062 syslogEntityOperationsCounterDiscontinuityTime OBJECT-TYPE 2064 to indicate whether 2065 'syslogEntityOperationsMsgsReceived' or 2066 'syslogEntityOperationsMsgsRelayed' or 2067 'syslogEntityOperationsMsgsDropped' or 2068 'syslogEntityOperationsMsgsIllFormed' or 2069 'syslogEntityOperationsMsgsIgnored' suffered a 2070 discontinuity. 2072 Revised the DESCRIPTION of the above Objects. 2074 10. Changed all references of "syslog process", "syslog device" to 2075 "syslog entity". 2077 11. Changed syntax of syslogEntityOperationsReference from 2078 syslEntOpsReference OBJECT-TYPE 2079 SYNTAX Integer32 2080 to 2081 syslogEntityOperationsReference OBJECT-TYPE 2082 SYNTAX Integer32 (0..2147483647) 2083 12. Revised the DESCRIPTION clauses of 2084 syslogEntityControlTable 2085 syslogEntityOperationsReference 2086 syslogEntityControlBindAddrType 2087 syslogEntityControlBindAddr 2088 syslogEntityControlTransportDomain 2089 syslogEntityControlService 2090 syslogEntityControlConfFileName 2091 syslogEntityControlStatus 2092 syslogEntityControlRowStatus 2093 syslogEntityOperationsTable 2094 syslogEntityControlTable 2095 syslogEntityOperationsMsgsDropped 2096 syslogEntityOperationsReference 2097 syslogEntityControlEntry 2099 13. Added DEFVAL { nonVolatile } to syslogEntityControlStorageType 2101 14. Merged the NOTIFICATIONs 2102 syslEntStarted 2103 syslEntStopped 2104 into syslogEntityStatusChanged 2106 15. Overhauled the syslogCompliance tree 2108 16. idnits fixed. 2110 17. IANA considerations section revised. 2112 17. Labels and Captions in figure 1 are revised. 2114 18. Revised DESCRIPTION clauses of 2115 SyslogSeverity 2116 syslogDefaultFacility 2117 syslogDefaultSeverity 2119 19. syslogDefaultMaxMessageSize is deleted 2120 revised the DESCRIPTION of syslogEntityControlMaxMessageSize 2122 20. editorial fixes 2124 The changes upto draft-ietf-syslog-device-mib-9.txt are documented 2125 below in the form of MIB Revision clauses. 2126 REVISION "200609040000Z" -- 9th September 2006 2127 DESCRIPTION 2128 " 2129 o The draft has been aligned with the current 2130 standards track documents syslog-protocol-17.txt 2131 and syslog-transport-udp-07.txt: the REFERNCE 2132 clauses have changed. 2133 o The TEXTUAL-CONVENTION SyslogTransport has been 2134 replaced by the TransportAddressType. 2135 o The TEXTUAL-CONVENTION SyslogFacility and 2136 SyslogSeverity have been aligned with 2137 syslog-protocol-17.txt 2139 o A paragraph has been added to list the related 2140 MIBs from which MOS and TEXTUAL-CONVENTIONs have 2141 been imported. 2142 o The target of this MIB is now called a syslog 2143 entity. [ Earlier it was referred to as a syslog 2144 device.] The prefix syslDev has been changed to 2145 syslEnt 2146 o The DEFVALS have been aligned with the reference 2147 documents. 2148 o The REFERENCE section has been updated. 2149 o The OID for syslogConformance has been changed 2150 from 4 to 3. 2151 " 2153 REVISION "200607250000Z" -- 25th July 2006 2154 DESCRIPTION 2155 "the internet draft's version number has 2156 been changed (7->8). 2157 " 2159 REVISION "200511250000Z" -- 25th November 2005 2160 DESCRIPTION 2161 "A near complete overhaul of the MIB and the document. 2162 The BSD-syslog flavor has been abandoned in favor of a 2163 more generic syslog-protocol document that is under 2164 preparation. 2165 TBD. The reference clauses need to be redone once the 2166 new syslog document is ready. 2168 List of authors changed. Original draft author Bruno 2169 Pape is acknowledged in the Acknowledgments section. 2171 Editorial nits fixed. 2172 " 2174 REVISION "200406160000Z" -- Mon Feb 16 00:00 GMT 2004 2175 DESCRIPTION 2176 "Major change. 2177 The configuration parts have been removed. 2179 Updated the description clauses. 2181 Editorial nits fixed. 2182 " 2184 REVISION "200306250000Z" -- Wed June 25 00:00 GMT 2003 2185 DESCRIPTION 2186 "Changed the type of 2187 syslogProcLastError SnmpAdminString, 2188 from Integer32. 2190 DEFVAL { 0 ] is added to syslogAllowedHostsMaskLen 2192 MO name changed from 2193 syslogCtlSelectionHostname to syslogCtlSelectionHostName 2195 Updated the description clauses. 2197 Fixed nits pointed out in Bert's mails of 20030319 and 2198 revised the document wrt the guidelines in 2199 draft-ietf-ops-mib-review-guidelines-01.txt 2201 Editorial nits fixed. 2202 " 2204 REVISION "200303030000Z" -- Mon March 03 00:00 GMT 2003 2205 DESCRIPTION 2206 "Fixing of nits in descriptions, addition of references, 2207 addition of the following MOs 2208 syslogProcMsgsIllFormed Counter32, 2209 syslogProcStartTime TimeStamp, 2210 syslogProcLastError Integer32, 2211 syslogProcLastErrorTime TimeStamp, 2212 syslDevCtlStorageType StorageType, 2213 syslogCtlFwdActionSrcAddrType InetAddressType, 2214 syslogCtlFwdActionSrcAddr InetAddress, 2215 added enumeration ''suspended(2)'' to 2216 syslDevCtlStatus. 2217 " 2219 REVISION "200212252343Z" -- Wed December 25 23:43 GMT 2002 2220 DESCRIPTION 2221 "Radical revision of the MIB structure and design." 2223 REVISION "200206061841Z" -- Thu Jun 6 18:41 GMT 2002 2224 DESCRIPTION 2225 "The initial version of this MIB module."