idnits 2.17.1 draft-labarre-iimc-mibii-04.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-18) 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 == The page length should not exceed 58 lines per page, but there was 106 longer pages, the longest (page 0) being 62 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1.2 OVERVIEW OF IIMC' ) ** The document seems to lack a Security Considerations 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 an Authors' Addresses Section. ** There are 156 instances of too long lines in the document, the longest one being 12 characters in excess of 72. ** The abstract seems to contain references ([2], [20], [15], [3], [21], [4], [ISO10165-4], [RFC1442], [22], [17], [23], [18], [5], [24], [7,8,9], [19], [7], [RFC1212], [9], [11], [IIMCOMIBTRANS], [12], [IIMCIMIBTRANS], [1], [ISO10165-1], [14]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 390 has weird spacing: '...SMI and termi...' == Line 2568 has weird spacing: '...ermined to be...' == Line 2569 has weird spacing: '...f `too old' ...' == Line 2588 has weird spacing: '... entry with ...' == Line 2594 has weird spacing: '...icit or other...' == (20 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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 section? 'IIMCOMIBTRANS' on line 243 looks like a reference -- Missing reference section? 'IIMCIMIBTRANS' on line 242 looks like a reference -- Missing reference section? 'IIMCPROXY' on line 27 looks like a reference -- Missing reference section? 'IIMCSEC' on line 27 looks like a reference -- Missing reference section? '14' on line 413 looks like a reference -- Missing reference section? '19' on line 5129 looks like a reference -- Missing reference section? '15' on line 387 looks like a reference -- Missing reference section? '5' on line 140 looks like a reference -- Missing reference section? '7' on line 380 looks like a reference -- Missing reference section? '8' on line 141 looks like a reference -- Missing reference section? '9' on line 414 looks like a reference -- Missing reference section? '12' on line 144 looks like a reference -- Missing reference section? '18' on line 145 looks like a reference -- Missing reference section? '11' on line 379 looks like a reference -- Missing reference section? '17' on line 379 looks like a reference -- Missing reference section? '24' on line 165 looks like a reference -- Missing reference section? '22' on line 230 looks like a reference -- Missing reference section? '20' on line 304 looks like a reference -- Missing reference section? '21' on line 191 looks like a reference -- Missing reference section? '23' on line 214 looks like a reference -- Missing reference section? 'RFC1212' on line 242 looks like a reference -- Missing reference section? 'ISO10165-1' on line 242 looks like a reference -- Missing reference section? 'RFC1442' on line 243 looks like a reference -- Missing reference section? 'ISO10165-4' on line 243 looks like a reference -- Missing reference section? '1' on line 5369 looks like a reference -- Missing reference section? '2' on line 5370 looks like a reference -- Missing reference section? '3' on line 5339 looks like a reference -- Missing reference section? '4' on line 5340 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 8 warnings (==), 30 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT Expires August, 1994 4 ISO/CCITT and Internet Management Coexistence (IIMC): 6 Translation of Internet MIB-II (RFC1213) 7 to ISO/CCITT GDMO MIB 9 (IIMCMIB-II) 11 February, 1994 13 Lee LaBarre (Editor) 15 The MITRE Corporation 16 Burlington Road 17 Bedford, MA 01730 18 cel@mbunix.mitre.org 20 Status of this Memo 22 This document provides information to the network and 23 systems management community. This document is intended as 24 a contribution to ongoing work in the area of multi-protocol 25 management coexistence and interworking. This document is 26 part of a package; see also [IIMCOMIBTRANS] [IIMCIMIBTRANS] 27 [IIMCPROXY] and [IIMCSEC]. Distribution of this document is 28 unlimited. Comments should be sent to the Network Management 29 Forum IIMC working group (iimc@thumper.bellcore.com). 31 This document is an Internet Draft. Internet Drafts are 32 working documents of the Internet Engineering Task Force 33 (IETF), its Areas, and its Working Groups. Note that other 34 groups may also distribute working documents as Internet 35 Drafts. 37 Internet Drafts are draft documents valid for a maximum of 38 six months. Internet Drafts may be updated, replaced, or 39 obsoleted by other documents at any time. It is not 40 appropriate to use Internet Drafts as reference material or 41 to cite them other than as a "working draft" or "work in 42 progress." 44 Please check the 1id-abstracts.txt listing contained in the 45 internet-drafts Shadow Directories on ds.internic.net, 46 nic.nordu.net, ftp.nisc.sri.com, munnari.oz.au to learn the 47 current status of any Internet Draft. 49 DRAFT February, 1994 51 Abstract 53 This document is intended to facilitate the multi-protocol 54 management coexistence and interworking for networks that 55 are managed using the ISO/CCITT Common Management 56 Information Protocol (CMIP) and networks that are managed 57 using the Internet Simple Network Management Protocol 58 (SNMP). This document contains the ISO/CCITT GDMO 59 definition and registration of MIB-II as derived from the 60 Internet MIB-II [14], according to the procedures defined in 61 "Translation of Internet MIBs to ISO/CCITT GDMO MIBs" [19]. 62 In addition, this document includes a translated 63 IPForwarding Table as derived from the Internet definition 64 in [15]. 66 Table of Contents 68 1. INTRODUCTION ..........................................1 70 1.1 PROBLEM STATEMENT.................................1 72 1.2 OVERVIEW OF IIMC..................................2 74 1.3 MIB TRANSLATION PROCEDURES........................3 76 1.4 NATIVE MANAGEMENT MODEL...........................3 78 1.5 PROXY MANAGEMENT MODEL............................5 80 1.6 SCOPE OF THIS DOCUMENT............................6 82 1.7 TERMS AND CONVENTIONS.............................6 84 2. IIMCMIB-II MIB ........................................8 86 -- 2.1 IIMCMIB-II GDMO TEMPLATES......................9 87 -- 2.1.1 IIMCMIB-II Managed Object Classes ........9 88 -- 2.1.2 IIMCMIB-II Attributes ....................20 89 -- 2.1.3 IIMCMIB-II Name Bindings .................87 91 -- 2.2 IIMCMIB-II ASN.1 MODULE........................93 93 3. CONFORMANCE ...........................................98 95 ANNEX A (NORMATIVE): MANAGED OBJECT CONFORMANCE 96 STATEMENTS (MOCS)......................................A-1 98 ANNEX B: GLOSSARY ........................................B-1 100 ANNEX C: REFERENCES ......................................C-1 101 DRAFT February, 1994 103 List of Figures 105 FIGURE 1. MIB TRANSLATION ................................3 107 FIGURE 2. NATIVE MANAGEMENT ..............................4 109 FIGURE 3. PROXY MANAGEMENT ...............................5 111 REVISION HISTORY 113 Issue 1.0, October 1993 115 This is the first issue of this document. The internet draft 116 , dated February, 1994, is 117 identical in content to Issue 1.0, October 1993. It has been 118 reformatted for posting as an internet draft. 120 DRAFT February, 1994 122 1. INTRODUCTION 124 This section provides an overview of ISO/CCITT and Internet 125 Management Coexistence (IIMC) activities, insight into the 126 problem being addressed by IIMC, and a brief introduction to 127 the strategy adopted by IIMC: use of translated MIBs in 128 either a proxy or native implementation. The section 129 concludes by describing the scope of this document, and 130 terms and conventions used by this document. 132 1.1 PROBLEM STATEMENT 134 The need for enterprise network management has been 135 addressed by development of network management standards 136 within various communities, most notably the ISO/CCITT and 137 Internet communities. 139 * The ISO/CCITT community developed the Common Management 140 Information Protocol (CMIP) [5], and related SMI 141 documents [7,8,9]. 143 * The Internet community developed the Simple Network 144 Management Protocol (SNMP) [12], and its successor, 145 SNMPv2 [18]. The Internet SMI is defined in [11] and 146 [17]. 148 These standards share a nearly common management model, but 149 diverge due to differing management philosophies. Although 150 functionally similar, the Internet and ISO/CCITT protocols 151 and SMIs differ in terms of their complexity and specific 152 operations. Business requirements for end-to-end enterprise 153 management include the need to integrate the management of 154 many different devices, potentially owned or administered by 155 many independent organizations. This requires components to 156 be accessed by ISO/CCITT management, Internet management, 157 and proprietary management mechanisms in a manner which 158 presents a unified view of the network, despite protocol and 159 SMI differences. 161 For example, many telecommunications and computer vendors, 162 represented by organizations such as the Network Management 163 Forum (NMF), and the U.S. government, as specified in the 164 Government Network Management Profile (GNMP) Version 1.0 165 [24], have based their enterprise management model on the 166 ISO/CCITT management model. These organizations are 167 particularly interested in integrated management of devices 168 that use the Internet management. This interest is primarily 169 due to the widespread commercial implementation and use of 170 DRAFT February, 1994 172 such devices, especially devices that use the Internet 173 TCP/IP protocol suite. 175 1.2 OVERVIEW OF IIMC 177 The ISO/CCITT and Internet Management Coexistence (IIMC) 178 package includes the following documents. 180 IIMCIMIBTRANS Translation of Internet MIBs to ISO/CCITT 181 GDMO MIBs [19] 183 IIMCOMIBTRANS Translation of ISO/CCITT GDMO MIBs to 184 Internet MIBs [22] 186 IIMCMIB-II Translation of Internet MIB-II (RFC1213) to 187 ISO/CCITT GDMO MIB 189 IIMCPROXY ISO/CCITT to Internet Management Proxy [20] 191 IIMCSEC ISO/CCITT to Internet Management Security[21] 193 These documents together comprise a package aimed at 194 integrating ISO/CCITT-based and Internet-based management 195 systems. 197 IIMC specifications address the problem that end-to-end 198 management requires an integrated, unified view of the 199 managed network, despite differences in management protocol 200 and information structure. Integrated management can be 201 facilitated by the development of "proxy" mechanisms which 202 translate between functionally equivalent service, protocol, 203 and SMI differences to create this unified view. MIB 204 translation procedures can be used to support proxy 205 management, as well as to take advantage of existing MIB 206 definition and avoid duplication of effort. In this way, 207 commercial investment in both ISO/CCITT and Internet-based 208 management technologies can be preserved through deployment 209 of common methods and tools which support integration. 211 This overall strategy was outlined in a joint publication 212 developed by the NM Forum and X/Open entitled "ISO/CCITT and 213 Internet Management: Coexistence and Interworking Strategy" 214 [23]. The documents included in the IIMC package are the 215 next level of detailed specifications which implement 216 several of the methodologies identified in the strategy. 217 Additional specifications may be defined in the future. 219 DRAFT February, 1994 221 1.3 MIB TRANSLATION PROCEDURES 223 The foundation of IIMC is provided by a pair of Management 224 Information Base (MIB) translation procedures. 226 * IIMCIMIBTRANS [19] specifies translation procedures for 227 converting MIBs from Internet MIB macro format into 228 ISO/CCITT GDMO template format. 230 * IIMCOMIBTRANS [22] specifies translation procedures for 231 converting MIBs from ISO/CCITT GDMO template format into 232 Internet MIB macro format. 234 The IIMC approach is to specify direct translation 235 procedures which yield a pair of functionally-equivalent 236 MIBs, as shown in Figure 1. 238 +----------------+ +--------------------+ +----------------+ 239 | Internet MIB | | MIB Translation | | GDMO MIB | 240 | | | Procedures | | | 241 | Format = | | Specified By | | Format = | 242 | [RFC1212] & |---->| [IIMCIMIBTRANS] or |---->| [ISO10165-1] & | 243 | [RFC1442] |<----| [IIMCOMIBTRANS] |<----| [ISO10165-4] | 244 +----------------+ +--------------------+ +----------------+ 246 Figure 1. MIB translation. 248 MIBs translated by these procedures may be used to take 249 advantage of existing MIB definitions when business needs 250 require deployment in a different management environment. 251 Translated MIBs may also be used to provide uniformity when 252 multiple management environments are supported by a single 253 system (e.g., dual stack managers). Finally, IIMC MIB 254 translation procedures may be used to support service 255 emulation by a proxy. 257 1.4 NATIVE MANAGEMENT MODEL 259 The basic model for ISO/CCITT and Internet management is 260 illustrated in the following diagram. 262 DRAFT February, 1994 264 Manager Agent 265 +-----------------------+ +----------------------+ 266 |+---------------------+| |+-------------------+ | 267 || Management || || Managed | | 268 || Applications || || Resources | | 269 |+---------------------+| |+-------------------+ | 270 | | | | | | 271 | | | | | | 272 |+-----------+---------+| |+----------+---------+| 273 || Manager | MIB || || Agent | MIB || 274 |+-----------+---------+| |+----------+---------+| 275 | | | | | | 276 | | Management | | | Management | 277 | | Services | | | Services | 278 +-----------------------+ +----------------------+ 279 | Management Protocol | | Management Protocol | 280 +-----------------------+ +----------------------+ 281 ^ ^ 282 | | 283 +------------------------------------+ 284 Protocol Messages 286 Figure 2. Native management. 288 Within IIMC documents, this model is referred to as the 289 "native" management model. MIBs translated using IIMC 290 procedures can be used by "native" agent implementations. 291 For example, an ISO/CCITT agent can make visible TCP/IP 292 managed resources using the translated GDMO version of the 293 Internet MIB-II [14] specified by [19]. Dual-stack managers 294 or agents may also be implemented which support both the 295 original MIB and the translated MIB generated using IIMC- 296 specified procedures. 298 DRAFT February, 1994 300 1.5 PROXY MANAGEMENT MODEL 302 The basic model for ISO/CCITT to Internet proxy management 303 is illustrated in the following diagram. This proxy is 304 specified by [20]. A similar approach could also be taken to 305 specify an Internet to ISO/CCITT proxy, although no such 306 IIMC document is currently specified. 308 Manager Proxy Agent 309 +-----------------------+ +---------------------+ +------------------ 310 |+---------------------+| |+------+ +----------+| |+----------------- 311 || Management || || GDMO | | Internet || || Managed 312 || Applications || || MIB | | MIB || || Resources 313 |+---------------------+| |+------+ +----------+| |+----------------- 314 | | | |+-------------------+| | | 315 | | | || Service || | | 316 | | | || Emulation || | | 317 | | | ||(scoping) || | | 318 | | | || (filtering) || | | 319 |+-----------+---------+| || (operations) || |+----------+------ 320 || ISO/CCITT | GDMO || || (message || || Internet | Inter 321 || Manager | MIB || || transformation)|| || Agent | MIB 322 |+-----------+---------+| |+-------------------+| |+----------+------ 323 | | | | |CMIS | | | | 324 | | CMIS Services | | |Services | | | | SNMP "Servic 325 | | | | | | | | | 326 | | | | | SNMP| | | | 327 | | | | | "Services"| | | | 328 +-----------------------+ +---------------------+ +------------------ 329 | CMIP | | CMIP | SNMP | | SNMP 330 +-----------------------+ +---------------------+ +------------------ 331 ^ ^ ^ ^ 332 | | | | 333 +---------------------+ +-------------------+ 334 CMIP Messages SNMP Messages 336 Figure 3. Proxy management. 338 This ISO/CCITT to Internet proxy provides emulation of CMIS 339 services by mapping to the corresponding SNMP message(s) 340 necessary to carry out the service request. The service 341 emulation allows management of Internet objects by an 342 ISO/CCITT manager. The left hand side of the proxy behaves 343 like an ISO/CCITT agent, communicating with the ISO/CCITT 344 manager using CMIP protocols. The right hand side of the 345 proxy behaves like an Internet manager, communicating with 346 the Internet agent using SNMP protocols. 348 The proxy relies on the existence of a pair of directly- 349 related MIB definitions, where the Internet MIB has been 350 translated into ISO/CCITT GDMO using the procedures 351 specified in IIMCIMIBTRANS. The proxy uses these MIB 352 definitions and rules to provide run-time translation of 353 DRAFT February, 1994 355 management information carried in service requests and 356 responses. 358 The proxy is designed with a specified interface between the 359 proxy and the underlying protocol stacks, and so deals 360 primarily in terms of CMIS services and SNMP "services". The 361 proxy emulates services such as CMIS scoping and filtering, 362 processing of CMIP operations, and forwarding/logging of 363 CMIS notifications by performing a mapping process which 364 must be tailored for each protocol (for example, SNMPv1 and 365 SNMPv2 are variants of the same protocol mapping process). 367 1.6 SCOPE OF THIS DOCUMENT 369 A major reason for the rapid commercialization of devices 370 manageable via the Internet management protocol is due to 371 the speed with which the vendors in the Internet community 372 have been able to develop MIBs based on the Internet SMI. 373 To capitalize on this continuing Internet MIB development 374 and their deployment in commercial devices, communities 375 interested in integrated management via CMIP/SNMP proxies, 376 and communities interested in using native CMIP agents to 377 manage TCP/IP resources, require the translation of Internet 378 MIBs defined according to the Internet Structure of 379 Management Information (SMI) [11] [17] into MIBs defined 380 according to the ISO SMI [7] and Guidelines for the 381 Definition of Managed Objects (GDMO) [9]. Procedures for 382 such translations are described in [19]. 384 This document (IIMCMIB-II) applies the procedures described 385 in [19] to the translation and registration of the Internet 386 MIB-II as defined in [14], and to the IP Forwarding Table 387 defined in [15]. 389 This document assumes that the reader is familiar with the 390 ISO/CCITT SMI and terminology as well as the Internet to 391 SMI translation defined in [19]. 393 1.7 TERMS AND CONVENTIONS 395 This document assumes that the reader is familiar with the 396 ISO/CCITT SMI and Internet SMI, and the terminology of each. 397 The term SNMP will be used throughout the document to 398 indicate either SNMPv1 or SNMPv2, unless a distinction needs 399 to be made. 401 Other terms and conventions used throughout this document 402 include the following. 404 DRAFT February, 1994 406 Proxy: An intermediate process that provides protocol and 407 SMI translation between two management services and SMIs. 409 DRAFT February, 1994 411 2. IIMCMIB-II MIB 413 The Internet MIB-II objects [14] are recast into ISO/CCITT 414 GDMO templates as defined in [9], and registered, using the 415 procedures defined in [19]. 417 Name Binding templates that define the containment hierarchy 418 for the ISO/CCITT MIB-II managed object classes are listed. 419 A proxy implementation would have multiple instances of the 420 ISO/CCITT system managed object, one for each Internet 421 agent, and one for the proxy itself. 423 A Naming Tree diagram for IIMC MIB-II managed object classes 424 is illustrated below. 426 "CCITT Rec. X.660 | ISO/IEC 9834-1 : 1992": root 427 | (or any other containing class) 428 | 429 |"Rec. X.721 | ISO/IEC 10165-2 : 1992" : system 430 | 431 |-- internetSystem 432 | 433 |-- at --- atEntry 434 | 435 |-- egp --- egpNeighEntry 436 | 437 |-- icmp 438 | 439 |-- interfaces --- ifEntry 440 | 441 |-- ip 442 | |--- ipRouteEntry 443 | |--- ipAddrEntry 444 | |--- ipNetToMediaEntry 445 | |--- ipForwardEntry 446 | 447 |-- snmp 448 | 449 |-- tcp --- tcpConnEntry 450 | 451 |-- udp --- udpEntry 453 The GDMO templates and ASN.1 modules are included here in 454 one section to facilitate automated processing. Comments 455 and subsection headers are included in the form of ASN.1 456 comments, i.e., preceded by "--". 458 This document (IIMCMIB-II) is allocated the following 459 registration identifier for purposes of referencing material 460 contained herein. 462 DRAFT February, 1994 464 iimcRFC12131354 OBJECT IDENTIFIER 465 ::= {iimcAutoDocument 1213 1354} 467 -- 2.1 IIMCMIB-II GDMO TEMPLATES 469 -- 2.1.1 IIMCMIB-II Managed Object Classes 471 at MANAGED OBJECT CLASS 472 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 473 CHARACTERIZED BY 474 atPkg PACKAGE 475 BEHAVIOUR 476 atPkgBehaviour BEHAVIOUR 477 DEFINED AS 478 !BEGINPARSE 479 REFERENCE 480 !!This managed object class maps to the at group 481 with object id {mib-2 3} in RFC1213.!!; 482 DESCRIPTION 483 !!Note however that this group is deprecated by 484 MIB-II. That is, it is being included solely for 485 compatibility with MIB-I nodes, and will most 486 likely be excluded from MIB-III nodes. From MIB-II 487 and onwards, each network protocol group contains 488 its own address translation tables. 490 The Address Translation group contains one table 491 which is the union across all interfaces of the 492 translation tables for converting a NetworkAddress 493 (e.g., an IP address) into a subnetwork-specific 494 address. For lack of a better term, this document 495 refers to such a subnetwork-specific address as a 496 `physical' address. 498 Examples of such translation tables are: for 499 broadcast media where ARP is in use, the 500 translation table is equivalent to the ARP cache; 501 or, on an X.25 network where non-algorithmic 502 translation to X.121 addresses is required, the 503 translation table contains the NetworkAddress to 504 X.121 address equivalences.!!; 505 ENDPARSE!;; 506 ATTRIBUTES 507 atId GET;;; 508 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 3 }; 510 atEntry MANAGED OBJECT CLASS 511 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 512 CHARACTERIZED BY 513 atEntryPkg PACKAGE 514 DRAFT February, 1994 516 BEHAVIOUR 517 atEntryPkgBehaviour BEHAVIOUR 518 DEFINED AS 519 !BEGINPARSE 520 REFERENCE 521 !!This managed object class maps to atEntry object 522 with object id {atTable 1} in RFC1213.!!; 523 DESCRIPTION 524 !!Each entry contains one NetworkAddress to 525 `physical' address equivalence. The delete value 526 is the null string.!!; 527 INDEX RFC1213-MIB.atIfIndex, 528 RFC1213-MIB.atNetAddress; 529 ENDPARSE!;; 530 ATTRIBUTES 531 atEntryId GET, 532 atIfIndex GET, 533 atPhysAddress GET-REPLACE, 534 atNetAddress GET;;; 535 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 3 1 1 }; 537 egp MANAGED OBJECT CLASS 538 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 539 CHARACTERIZED BY 540 egpPkg PACKAGE 541 BEHAVIOUR 542 egpPkgBehaviour BEHAVIOUR 543 DEFINED AS 544 !BEGINPARSE 545 REFERENCE 546 !!This managed object class maps to egp group with 547 object id {mib-2 8} in RFC 1213.!!; 548 ENDPARSE!;; 549 ATTRIBUTES 550 egpId GET, 551 egpInMsgs GET, 552 egpInErrors GET, 553 egpOutMsgs GET, 554 egpOutErrors GET, 555 egpAs GET;;; 556 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 8 }; 558 egpNeighEntry MANAGED OBJECT CLASS 559 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 560 CHARACTERIZED BY 561 egpNeighEntryPkg PACKAGE 562 BEHAVIOUR 563 egpNeighEntryPkgBehaviour BEHAVIOUR 564 DEFINED AS 565 !BEGINPARSE 566 REFERENCE 567 !!This managed object class maps to egpNeighEntry 568 object with object id {egpNeighTable 1} in RFC 569 1213.!!; 570 DRAFT February, 1994 572 DESCRIPTION 573 !!Information about this entity's relationship 574 with a particular EGP neighbor.!!; 575 INDEX RFC1213-MIB.egpNeighAddr; 576 ENDPARSE!;; 577 ATTRIBUTES 578 egpNeighEntryId GET, 579 egpNeighState GET, 580 egpNeighAddr GET, 581 egpNeighAs GET, 582 egpNeighInMsgs GET, 583 egpNeighInErrs GET, 584 egpNeighOutMsgs GET, 585 egpNeighOutErrs GET, 586 egpNeighInErrMsgs GET, 587 egpNeighOutErrMsgs GET, 588 egpNeighStateUps GET, 589 egpNeighStateDowns GET, 590 egpNeighIntervalHello GET, 591 egpNeighIntervalPoll GET, 592 egpNeighMode GET, 593 egpNeighEventTrigger GET-REPLACE;;; 594 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 }; 596 icmp MANAGED OBJECT CLASS 597 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 598 CHARACTERIZED BY 599 icmpPkg PACKAGE 600 BEHAVIOUR 601 icmpPkgBehaviour BEHAVIOUR 602 DEFINED AS 603 !BEGINPARSE 604 REFERENCE 605 !!This managed object class maps to the icmp group 606 with object id {mib-2 5} in RFC 1213.!!; 607 ENDPARSE!;; 608 ATTRIBUTES 609 icmpId GET, 610 icmpInMsgs GET, 611 icmpInErrors GET, 612 icmpInDestUnreachs GET, 613 icmpInTimeExcds GET, 614 icmpInParmProbs GET, 615 icmpInSrcQuenchs GET, 616 icmpInRedirects GET, 617 icmpInEchos GET, 618 icmpInEchoReps GET, 619 icmpInTimestamps GET, 620 icmpInTimestampReps GET, 621 icmpInAddrMasks GET, 622 icmpInAddrMaskReps GET, 623 icmpOutMsgs GET, 624 icmpOutErrors GET, 625 icmpOutDestUnreachs GET, 626 DRAFT February, 1994 628 icmpOutTimeExcds GET, 629 icmpOutParmProbs GET, 630 icmpOutSrcQuenchs GET, 631 icmpOutRedirects GET, 632 icmpOutEchos GET, 633 icmpOutEchoReps GET, 634 icmpOutTimestamps GET, 635 icmpOutTimestampReps GET, 636 icmpOutAddrMasks GET, 637 icmpOutAddrMaskReps GET;;; 638 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 5 }; 640 ifEntry MANAGED OBJECT CLASS 641 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 642 CHARACTERIZED BY ifEntryPkg PACKAGE 643 BEHAVIOUR 644 ifEntryPkgBehaviour BEHAVIOUR 645 DEFINED AS 646 !BEGINPARSE 647 REFERENCE 648 !!This managed object class maps to the ifEntry 649 object with object id {ifTable 1} in RFC 1213.!!; 650 DESCRIPTION 651 !!An interface entry containing objects at the 652 subnetwork layer and below for a particular 653 interface. The Interfaces table contains 654 information on the entity's interfaces. Each 655 interface is thought of as being attached to a 656 `subnetwork'. Note that this term should not be 657 confused with `subnet' which refers to an 658 addressing partitioning scheme used in the 659 Internet suite of protocols.!!; 660 INDEX RFC1213-MIB.ifIndex; 661 ENDPARSE!;; 662 ATTRIBUTES 663 ifEntryId GET, 664 ifIndex GET, 665 ifDescr GET, 666 ifType GET, 667 ifMtu GET, 668 ifSpeed GET, 669 ifPhysAddress GET, 670 ifAdminStatus GET-REPLACE, 671 ifOperStatus GET, 672 ifLastChange GET, 673 ifInOctets GET, 674 ifInUcastPkts GET, 675 ifInNUcastPkts GET, 676 ifInDiscards GET, 677 ifInErrors GET, 678 ifInUnknownProtos GET, 679 ifOutOctets GET, 680 ifOutUcastPkts GET, 681 ifOutNUcastPkts GET, 682 DRAFT February, 1994 684 ifOutDiscards GET, 685 ifOutErrors GET, 686 ifOutQLen GET, 687 ifSpecific GET;;; 688 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 }; 690 interfaces MANAGED OBJECT CLASS 691 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 692 CHARACTERIZED BY interfacesPkg PACKAGE BEHAVIOUR 693 interfacesPkgBehaviour BEHAVIOUR 694 DEFINED AS 695 !BEGINPARSE 696 REFERENCE 697 !!This managed object class maps to the interface 698 group with object id {mib-2 2} in RFC 1213.!!; 699 ENDPARSE!;; 700 ATTRIBUTES 701 interfacesId GET, 702 ifNumber GET;;; 703 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 }; 705 internetSystem MANAGED OBJECT CLASS 706 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 707 CHARACTERIZED BY internetSystemPkg PACKAGE 708 BEHAVIOUR 709 internetSystemPkgBehaviour BEHAVIOUR 710 DEFINED AS 711 !BEGINPARSE 712 REFERENCE 713 !!This managed object class maps to the Internet 714 system group with object id {mib-2 1} in RFC 715 1213.!!; 716 DESCRIPTION 717 !!If an agent is not configured to have a value 718 for any of these variables, a string of length 0 719 is returned. 721 When this object class is implemented in a managed 722 system for use with the ISO/CCITT management 723 protocol (CMIP), this object class shall emit the 724 internetAlarm notification in place of SNMP 725 traps/notifications which are reported using the 726 unconfirmed service, and in place of 727 InformRequests which are reported using the 728 confirmed service. 730 When this object class is implemented in an 731 ISO/CCITT-Internet proxy, the internetAlarm shall 732 be emitted upon receipt of SNMP 733 traps/notifications which are reported using the 734 unconfirmed service, and emitted upon receipt of 735 InformRequests which are reported using the 736 confirmed service.!!; 737 ENDPARSE!;; 738 DRAFT February, 1994 740 ATTRIBUTES 741 internetSystemId GET, 742 sysDescr GET, 743 sysObjectID GET, 744 sysUpTime GET, 745 sysContact GET-REPLACE, 746 sysName GET-REPLACE, 747 sysLocation GET-REPLACE, 748 sysServices GET; 749 NOTIFICATIONS 750 {iimcIIMCIMIBTRANS}:internetAlarm;;; 751 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 1}; 753 ip MANAGED OBJECT CLASS 754 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 755 CHARACTERIZED BY ipPkg PACKAGE 756 BEHAVIOUR 757 ipPkgBehaviour BEHAVIOUR 758 DEFINED AS 759 !BEGINPARSE 760 REFERENCE 761 !!This managed object class maps to the ip group 762 with object id {mib-2 4} in RFC 1213. It includes 763 the ipForwardNumber attribute from RFC1354.!!; 764 DESCRIPTION 765 !!This object class extends the MIB-II ip group by 766 including the ipForwardNumber attribute which is 767 derived from the ipForwardNumber Internet object 768 in RFC1354.!!; 769 ENDPARSE!;; 770 ATTRIBUTES 771 ipId GET, 772 ipForwarding GET-REPLACE, 773 ipDefaultTTL GET-REPLACE, 774 ipInReceives GET, 775 ipInHdrErrors GET, 776 ipInAddrErrors GET, 777 ipForwDatagrams GET, 778 ipInUnknownProtos GET, 779 ipInDiscards GET, 780 ipInDelivers GET, 781 ipOutRequests GET, 782 ipOutDiscards GET, 783 ipOutNoRoutes GET, 784 ipReasmTimeout GET, 785 ipReasmReqds GET, 786 ipReasmOKs GET, 787 ipReasmFails GET, 788 ipFragOKs GET, 789 ipFragFails GET, 790 ipFragCreates GET, 791 ipRoutingDiscards GET, 792 ipForwardNumber GET;;; 793 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 4}; 794 DRAFT February, 1994 796 ipAddrEntry MANAGED OBJECT CLASS 797 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 798 CHARACTERIZED BY ipAddrEntryPkg PACKAGE 799 BEHAVIOUR 800 ipAddrEntryPkgBehaviour BEHAVIOUR 801 DEFINED AS 802 !BEGINPARSE 803 REFERENCE 804 !!This managed object class maps to the 805 ipAddrEntry object with object id {ipAddrTable 1} 806 in RFC 1213.!!; 807 DESCRIPTION 808 !!The addressing information for one of this 809 entity's IP addresses.!!; 810 INDEX RFC1213-MIB.ipAdEntAddr; 811 ENDPARSE!;; 812 ATTRIBUTES 813 ipAddrEntryId GET, 814 ipAdEntAddr GET, 815 ipAdEntIfIndex GET, 816 ipAdEntNetMask GET, 817 ipAdEntBcastAddr GET, 818 ipAdEntReasmMaxSize GET;;; 819 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 4 20 1}; 821 ipForwardEntry MANAGED OBJECT CLASS 822 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 823 CHARACTERIZED BY ipForwardEntryPkg PACKAGE 824 BEHAVIOUR 825 ipForwardEntryPkgBehaviour BEHAVIOUR 826 DEFINED AS 827 !BEGINPARSE 828 REFERENCE 829 !!This managed object class maps to the 830 ipForwardEntry with object id {ipForwardTable 1} 831 in RFC 1354.!!; 832 DESCRIPTION 833 !!A particular route to a particular destination, 834 under a particular policy.!!; 835 INDEX RFC1354-MIB.ipForwardDest, 836 RFC1354-MIB.ipForwardProto, 837 RFC1354-MIB.ipForwardPolicy, 838 RFC1354-MIB.ipForwardNextHop; 839 ENDPARSE!;; 840 ATTRIBUTES 841 ipForwardEntryId GET, 842 ipForwardDest GET, 843 ipForwardMask DEFAULT VALUE 844 IIMCRFC12131354ASN1.c-ipForwardMask 845 GET-REPLACE, 846 ipForwardPolicy GET, 847 ipForwardNextHop GET, 848 ipForwardIfIndex DEFAULT VALUE 849 DRAFT February, 1994 851 IIMCRFC12131354ASN1.c-ipForwardIfIndex 852 GET-REPLACE, 853 ipForwardType DEFAULT VALUE 854 IIMCRFC12131354ASN1.c-ipForwardType 855 GET-REPLACE, 856 ipForwardProto GET, 857 ipForwardAge DEFAULT VALUE 858 IIMCRFC12131354ASN1.c-ipForwardAge 859 GET, 860 ipForwardInfo DEFAULT VALUE 861 IIMCRFC12131354ASN1.c-ipForwardInfo 862 GET-REPLACE, 863 ipForwardNextHopAS DEFAULT VALUE 864 IIMCRFC12131354ASN1.c-ipForwardNextHopAS 865 GET-REPLACE, 866 ipForwardMetric1 DEFAULT VALUE 867 IIMCRFC12131354ASN1.c-ipForwardMetric1 868 GET-REPLACE, 869 ipForwardMetric2 DEFAULT VALUE 870 IIMCRFC12131354ASN1.c-ipForwardMetric2 871 GET-REPLACE, 872 ipForwardMetric3 DEFAULT VALUE 873 IIMCRFC12131354ASN1.c-ipForwardMetric3 874 GET-REPLACE, 875 ipForwardMetric4 DEFAULT VALUE 876 IIMCRFC12131354ASN1.c-ipForwardMetric4 877 GET-REPLACE, 878 ipForwardMetric5 DEFAULT VALUE 879 IIMCRFC12131354ASN1.c-ipForwardMetric5 880 GET-REPLACE;;; 881 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1}; 883 ipNetToMediaEntry MANAGED OBJECT CLASS 884 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 885 CHARACTERIZED BY ipNetToMediaEntryPkg PACKAGE 886 BEHAVIOUR 887 ipNetToMediaEntryPkgBehaviour BEHAVIOUR 888 DEFINED AS 889 !BEGINPARSE 890 REFERENCE 891 !!This managed object class maps to the 892 ipNetToMediaEntry object with object id 893 {ipNetToMediaTable 1} in RFC 1213.!!; 894 DESCRIPTION 895 !!Each entry contains one IpAddress to `physical' 896 address equivalence.!!; 897 INDEX RFC1213-MIB.ipNetToMediaIfIndex, 898 RFC1213-MIB.ipNetToMediaNetAddress; 899 ENDPARSE!;; 900 ATTRIBUTES 901 ipNetToMediaEntryId GET, 902 ipNetToMediaIfIndex GET, 903 ipNetToMediaPhysAddress GET-REPLACE, 904 ipNetToMediaNetAddress GET, 905 DRAFT February, 1994 907 ipNetToMediaType GET-REPLACE;;; 908 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 4 22 1}; 910 ipRouteEntry MANAGED OBJECT CLASS 911 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 912 CHARACTERIZED BY ipRouteEntryPkg PACKAGE 913 BEHAVIOUR ipRouteEntryPkgBehaviour BEHAVIOUR 914 DEFINED AS 915 !BEGINPARSE 916 REFERENCE 917 !!This managed object class maps to the 918 ipRouteEntry object with object id {ipRouteTable 919 1} in RFC 1213.!!; 920 DESCRIPTION 921 !!A route to a particular destination.!!; 922 INDEX RFC1213-MIB.ipRouteDest; 923 ENDPARSE!;; 924 ATTRIBUTES 925 ipRouteEntryId GET, 926 ipRouteDest GET, 927 ipRouteIfIndex GET-REPLACE, 928 ipRouteMetric1 GET-REPLACE, 929 ipRouteMetric2 GET-REPLACE, 930 ipRouteMetric3 GET-REPLACE, 931 ipRouteMetric4 GET-REPLACE, 932 ipRouteNextHop GET-REPLACE, 933 ipRouteType GET-REPLACE, 934 ipRouteProto GET, 935 ipRouteAge GET-REPLACE, 936 ipRouteMask GET-REPLACE, 937 ipRouteMetric5 GET-REPLACE, 938 ipRouteInfo GET;;; 939 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1}; 941 snmp MANAGED OBJECT CLASS 942 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 943 CHARACTERIZED BY 944 snmpPkg PACKAGE 945 BEHAVIOUR snmpPkgBehaviour BEHAVIOUR 946 DEFINED AS 947 !BEGINPARSE 948 REFERENCE 949 !!This managed object class maps to the snmp group 950 with object id {mib-2 11} in RFC 1213.!!; 951 DESCRIPTION 952 !!Some of the attributes defined below will be 953 zero-valued in those SNMP implementations that are 954 optimized to support only those functions specific 955 to either a management agent or a management 956 station. In particular, it should be observed that 957 the attributes below refer to an SNMP entity, and 958 there may be several SNMP entities residing on a 959 managed node (e.g., if the node is hosting acting 960 as a management station).!!; 961 DRAFT February, 1994 963 ENDPARSE!;; 964 ATTRIBUTES 965 snmpId GET, 966 snmpInPkts GET, 967 snmpOutPkts GET, 968 snmpInBadVersions GET, 969 snmpInBadCommunityNames GET, 970 snmpInBadCommunityUses GET, 971 snmpInASNParseErrs GET, 972 snmpInTooBigs GET, 973 snmpInNoSuchNames GET, 974 snmpInBadValues GET, 975 snmpInReadOnlys GET, 976 snmpInGenErrs GET, 977 snmpInTotalReqVars GET, 978 snmpInTotalSetVars GET, 979 snmpInGetRequests GET, 980 snmpInGetNexts GET, 981 snmpInSetRequests GET, 982 snmpInGetResponses GET, 983 snmpInTraps GET, 984 snmpOutTooBigs GET, 985 snmpOutNoSuchNames GET, 986 snmpOutBadValues GET, 987 snmpOutGenErrs GET, 988 snmpOutGetRequests GET, 989 snmpOutGetNexts GET, 990 snmpOutSetRequests GET, 991 snmpOutGetResponses GET, 992 snmpOutTraps GET, 993 snmpEnableAuthenTraps GET-REPLACE;;; 994 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11}; 996 tcp MANAGED OBJECT CLASS 997 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 998 CHARACTERIZED BY 999 tcpPkg PACKAGE 1000 BEHAVIOUR 1001 tcpPkgBehaviour BEHAVIOUR 1002 DEFINED AS 1003 !BEGINPARSE 1004 REFERENCE 1005 !!This managed object class maps to the tcp group 1006 with object id {mib-2 6} in RFC 1213.!!; 1007 DESCRIPTION 1008 !!Note that instances that represent information 1009 about a particular TCP connection are transient; 1010 they persist only as long as the connection in 1011 question.!!; 1012 ENDPARSE!;; 1013 ATTRIBUTES 1014 tcpId GET, 1015 tcpRtoAlgorithm GET, 1016 tcpRtoMin GET, 1017 DRAFT February, 1994 1019 tcpRtoMax GET, 1020 tcpMaxConn GET, 1021 tcpActiveOpens GET, 1022 tcpPassiveOpens GET, 1023 tcpAttemptFails GET, 1024 tcpEstabResets GET, 1025 tcpCurrEstab GET, 1026 tcpInSegs GET, 1027 tcpOutSegs GET, 1028 tcpRetransSegs GET, 1029 tcpInErrs GET, 1030 tcpOutRsts GET;;; 1031 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 6 }; 1033 tcpConnEntry MANAGED OBJECT CLASS 1034 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 1035 CHARACTERIZED BY tcpConnEntryPkg PACKAGE 1036 BEHAVIOUR 1037 tcpConnEntryPkgBehaviour BEHAVIOUR 1038 DEFINED AS 1039 !BEGINPARSE 1040 REFERENCE 1041 !!This managed object class maps to the 1042 tcpConnEntry object with object id {tcpConnTable 1043 1} in RFC 1213.!!; 1044 DESCRIPTION 1045 !!Information about a particular current TCP 1046 connection. An object of this type is transient, 1047 in that it ceases to exist when (or soon after) 1048 the connection makes the transition to the CLOSED 1049 state.!!; 1050 INDEX RFC1213-MIB.tcpConnLocalAddress, 1051 RFC1213-MIB.tcpConnLocalPort, 1052 RFC1213-MIB.tcpConnRemAddress, 1053 RFC1213-MIB.tcpConnRemPort; 1054 ENDPARSE!;; 1055 ATTRIBUTES 1056 tcpConnEntryId GET, 1057 tcpConnState GET-REPLACE, 1058 tcpConnLocalAddress GET, 1059 tcpConnLocalPort GET, 1060 tcpConnRemAddress GET, 1061 tcpConnRemPort GET;;; 1062 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 6 13 1}; 1064 udp MANAGED OBJECT CLASS 1065 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 1066 CHARACTERIZED BY udpPkg PACKAGE 1067 BEHAVIOUR 1068 udpPkgBehaviour BEHAVIOUR 1069 DEFINED AS 1070 !BEGINPARSE 1071 REFERENCE 1072 DRAFT February, 1994 1074 !!This managed object class maps to the udp group 1075 with object id {mib-2 7} in RFC 1213.!!; 1076 ENDPARSE!;; 1077 ATTRIBUTES 1078 udpId GET, 1079 udpInDatagrams GET, 1080 udpNoPorts GET, 1081 udpInErrors GET, 1082 udpOutDatagrams GET;;; 1083 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 7}; 1085 udpEntry MANAGED OBJECT CLASS 1086 DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; 1087 CHARACTERIZED BY udpEntryPkg PACKAGE 1088 BEHAVIOUR 1089 udpEntryPkgBehaviour BEHAVIOUR 1090 DEFINED AS 1091 !BEGINPARSE 1092 REFERENCE 1093 !!This managed object class maps to the udpEntry 1094 object with object id {udpTable 1} in RFC 1213.!!; 1095 DESCRIPTION 1096 !!Information about a particular current UDP 1097 listener. The UDP listener table contains 1098 information about this entity's UDP end-points on 1099 which a local application is currently accepting 1100 datagrams.!!; 1101 INDEX RFC1213-MIB.udpLocalAddress, 1102 RFC1213-MIB.udpLocalPort; 1103 ENDPARSE!;; 1104 ATTRIBUTES 1105 udpEntryId GET, 1106 udpLocalAddress GET, 1107 udpLocalPort GET;;; 1108 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 7 5 1}; 1110 -- 2.1.2 IIMCMIB-II Attributes 1112 atEntryId ATTRIBUTE 1113 WITH ATTRIBUTE SYNTAX 1114 IIMCRFC12131354ASN1.AtEntryIdValue; 1115 MATCHES FOR EQUALITY; 1116 BEHAVIOUR 1117 atEntryIdBehaviour BEHAVIOUR 1118 DEFINED AS 1119 !The naming attribute for object class atEntry.!;; 1120 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 3 1 1}; 1122 atId ATTRIBUTE 1123 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.AtIdValue; 1124 MATCHES FOR EQUALITY; 1125 BEHAVIOUR 1126 DRAFT February, 1994 1128 atIdBehaviour BEHAVIOUR 1129 DEFINED AS 1130 !The naming attribute for object class at.!;; 1131 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 3}; 1133 atIfIndex ATTRIBUTE 1134 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 1135 MATCHES FOR EQUALITY, ORDERING; 1136 BEHAVIOUR 1137 atIfIndexBehaviour BEHAVIOUR 1138 DEFINED AS 1139 !BEGINPARSE 1140 REFERENCE 1141 !!This attribute maps to atIfIndex with object id 1142 {atEntry 1} in RFC1213.;!! 1143 DESCRIPTION 1144 !!The interface on which this entry's equivalence 1145 is effective. The interface identified by a 1146 particular value of this index is the same 1147 interface as identified by the same value of 1148 ifIndex.!!; 1149 ENDPARSE!;; 1150 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 3 1 1 1}; 1152 atNetAddress ATTRIBUTE 1153 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 1154 BEHAVIOUR 1155 atNetAddressBehaviour BEHAVIOUR 1156 DEFINED AS 1157 !BEGINPARSE 1158 REFERENCE 1159 !!This attribute maps to atNetAddress with object 1160 id {atEntry 3} in RFC1213.!!; 1161 DESCRIPTION 1162 !!The NetworkAddress (e.g., the IP address) 1163 corresponding to the media-dependent `physical' 1164 address.!!; 1165 ENDPARSE!;; 1166 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 3 1 1 3}; 1168 atPhysAddress ATTRIBUTE 1169 DERIVED FROM {iimcIIMCIMIBTRANS}:physAddress; 1170 BEHAVIOUR 1171 atPhysAddressBehaviour BEHAVIOUR 1172 DEFINED AS 1173 !BEGINPARSE 1174 REFERENCE 1175 !!This attribute maps to atPhysAddress with object 1176 id {atEntry 2} in RFC1213.!!; 1177 DESCRIPTION 1178 !!The media-dependent `physical' address. Setting 1179 this attribute to a null string (one of zero 1180 length) has the effect of invalidating the 1181 corresponding atEntry. That is, it effectively 1182 DRAFT February, 1994 1184 disassociates the interface identified with said 1185 entry from the mapping identified with said entry. 1186 It is an implementation-specific matter as to 1187 whether the agent removes an invalidated entry 1188 from the table. Accordingly, management stations 1189 must be prepared to receive tabular information 1190 from agents that corresponds to entries not 1191 currently in use. Proper interpretation of such 1192 entries requires examination of the relevant 1193 atPhysAddress attribute.!!; 1194 ENDPARSE!;; 1195 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 3 1 1 2}; 1197 egpAs ATTRIBUTE 1198 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 1199 MATCHES FOR EQUALITY, ORDERING; 1200 BEHAVIOUR 1201 egpAsBehaviour BEHAVIOUR 1202 DEFINED AS 1203 !BEGINPARSE 1204 REFERENCE 1205 !!This attribute maps to egpAs with object id {egp 1206 6} in RFC1213.!!; 1207 DESCRIPTION 1208 !!The autonomous system number of this EGP 1209 entity.!!; 1210 ENDPARSE!;; 1211 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 6}; 1213 egpId ATTRIBUTE 1214 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.EgpIdValue; 1215 MATCHES FOR EQUALITY; 1216 BEHAVIOUR 1217 egpIdBehaviour BEHAVIOUR 1218 DEFINED AS 1219 !The naming attribute for object class egp.!;; 1220 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 8}; 1222 egpInErrors ATTRIBUTE 1223 DERIVED FROM {iimcIIMCIMIBTRANS}:counter32; 1224 BEHAVIOUR 1225 egpInErrorsBehaviour BEHAVIOUR 1226 DEFINED AS 1227 !BEGINPARSE 1228 REFERENCE 1229 !!This attribute maps to egpInErrors with object 1230 id {egp 2} in RFC1213.!!; 1231 DESCRIPTION 1232 !!The number of EGP messages received that proved 1233 to be in error.!!; 1234 ENDPARSE!;; 1235 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 2}; 1237 egpInMsgs ATTRIBUTE 1238 DRAFT February, 1994 1240 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1241 BEHAVIOUR 1242 egpInMsgsBehaviour BEHAVIOUR 1243 DEFINED AS 1244 !BEGINPARSE 1245 REFERENCE 1246 !!This attribute maps to egpInMsgs with object id 1247 {egp 1} in RFC1213.!!; 1248 DESCRIPTION 1249 !!The number of EGP messages received without 1250 error.!!; 1251 ENDPARSE!;; 1252 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 1}; 1254 egpNeighAddr ATTRIBUTE 1255 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 1256 BEHAVIOUR 1257 egpNeighAddrBehaviour BEHAVIOUR 1258 DEFINED AS 1259 !BEGINPARSE 1260 REFERENCE 1261 !!This attribute maps to egpNeighAddr with object 1262 id {egpNeighEntry 2} in RFC1213.!!; 1263 DESCRIPTION 1264 !!The IP address of this entry's EGP neighbor.!!; 1265 ENDPARSE!;; 1266 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 2}; 1268 egpNeighAs ATTRIBUTE 1269 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 1270 MATCHES FOR EQUALITY, ORDERING; 1271 BEHAVIOUR 1272 egpNeighAsBehaviour BEHAVIOUR 1273 DEFINED AS 1274 !BEGINPARSE 1275 REFERENCE 1276 !!This attribute maps to egpNeighAs with object id 1277 {egpNeighEntry 3} in RFC1213.!!; 1278 DESCRIPTION 1279 !!The autonomous system of this EGP peer. Zero 1280 should be specified if the autonomous system 1281 number of the neighbor is not yet known.!!; 1282 ENDPARSE!;; 1283 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 3}; 1285 egpNeighEntryId ATTRIBUTE 1286 WITH ATTRIBUTE SYNTAX 1287 IIMCRFC12131354ASN1.EgpNeighEntryIdValue; 1288 MATCHES FOR EQUALITY; 1289 BEHAVIOUR 1290 egpNeighEntryIdBehaviour BEHAVIOUR 1291 DEFINED AS 1292 !The naming attribute for object class 1293 egpNeighEntry.!;; 1294 DRAFT February, 1994 1296 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 8 5 1}; 1298 egpNeighEventTrigger ATTRIBUTE 1299 WITH ATTRIBUTE SYNTAX 1300 IIMCRFC12131354ASN1.EgpNeighEventTrigger; 1301 MATCHES FOR EQUALITY, ORDERING; 1302 BEHAVIOUR 1303 egpNeighEventTriggerBehaviour BEHAVIOUR 1304 DEFINED AS 1305 !BEGINPARSE 1306 REFERENCE 1307 !!This attribute maps to egpNeighEventTrigger with 1308 object id {egpNeighEntry 15} in RFC1213.!!; 1309 DESCRIPTION 1310 !!A control variable used to trigger operator- 1311 initiated Start and Stop events. When read, this 1312 variable always returns the most recent value that 1313 egpNeighEventTrigger was set to. If it has not 1314 been set since the last initialization of the 1315 network management subsystem on the node, it 1316 returns a value of `stop'. 1318 When set, this variable causes a Start or Stop 1319 event on the specified neighbor, as specified on 1320 pages 8-10 of RFC 904. Briefly, a Start event 1321 causes an Idle peer to begin neighbor acquisition 1322 and a non-Idle peer to reinitiate neighbor 1323 acquisition. A stop event causes a non-Idle peer 1324 to return to the Idle state until a Start event 1325 occurs, either via egpNeighEventTrigger or 1326 otherwise.!!; 1327 ENDPARSE!;; 1328 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 15}; 1330 egpNeighInErrMsgs ATTRIBUTE 1331 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1332 BEHAVIOUR 1333 egpNeighInErrMsgsBehaviour BEHAVIOUR 1334 DEFINED AS 1335 !BEGINPARSE 1336 REFERENCE 1337 !!This attribute maps to egpNeighInErrMsgs with 1338 object id {egpNeighEntry 8} in RFC1213.!!; 1339 DESCRIPTION 1340 !!The number of EGP-defined error messages 1341 received from this EGP peer.!!; 1342 ENDPARSE!;; 1343 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 8}; 1345 egpNeighInErrs ATTRIBUTE 1346 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1347 BEHAVIOUR 1348 egpNeighInErrsBehaviour BEHAVIOUR 1349 DEFINED AS 1350 DRAFT February, 1994 1352 !BEGINPARSE 1353 REFERENCE 1354 !!This attribute maps to egpNeighInErrs with 1355 object id {egpNeighEntry 5} in RFC1213.!!; 1356 DESCRIPTION 1357 !!The number of EGP messages received from this 1358 EGP peer that proved to be in error (e.g., bad EGP 1359 checksum).!!; 1360 ENDPARSE!;; 1361 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 5}; 1363 egpNeighInMsgs ATTRIBUTE 1364 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1365 BEHAVIOUR 1366 egpNeighInMsgsBehaviour BEHAVIOUR 1367 DEFINED AS 1368 !BEGINPARSE 1369 REFERENCE 1370 !!This attribute maps to egpNeighInMsgs with 1371 object id {egpNeighEntry 4} in RFC1213.!!; 1372 DESCRIPTION 1373 !!The number of EGP messages received without 1374 error from this EGP peer.!!; 1375 ENDPARSE!;; 1376 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 4}; 1378 egpNeighIntervalHello ATTRIBUTE 1379 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 1380 MATCHES FOR EQUALITY, ORDERING; 1381 BEHAVIOUR 1382 egpNeighIntervalHelloBehaviour BEHAVIOUR 1383 DEFINED AS 1384 !BEGINPARSE 1385 REFERENCE 1386 !!This attribute maps to the egpNeighIntervalHello 1387 with object id {egpNeighEntry 12} in RFC1213.!!; 1388 DESCRIPTION 1389 !!The interval between EGP Hello command 1390 retransmissions (in hundredths of a second). This 1391 represents the t1 timer as defined in RFC 904.!!; 1392 ENDPARSE!;; 1393 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 12}; 1395 egpNeighIntervalPoll ATTRIBUTE 1396 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 1397 MATCHES FOR EQUALITY, ORDERING; 1398 BEHAVIOUR 1399 egpNeighIntervalPollBehaviour BEHAVIOUR 1400 DEFINED AS 1401 !BEGINPARSE 1402 REFERENCE 1403 !!This attribute maps to egpNeighIntervalPoll with 1404 object id {egpNeighEntry 13} in RFC1213.!!; 1405 DESCRIPTION 1406 DRAFT February, 1994 1408 !!The interval between EGP poll command 1409 retransmissions (in hundredths of a second). This 1410 represents the t3 timer as defined in RFC 904.!!; 1411 ENDPARSE!;; 1412 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 13}; 1414 egpNeighMode ATTRIBUTE 1415 WITH ATTRIBUTE SYNTAX 1416 IIMCRFC12131354ASN1.EgpNeighMode; 1417 MATCHES FOR EQUALITY, ORDERING; 1418 BEHAVIOUR 1419 egpNeighModeBehaviour BEHAVIOUR 1420 DEFINED AS 1421 !BEGINPARSE 1422 REFERENCE !!This attribute maps to egpNeighMode 1423 with object id {egpNeighEntry 14} in RFC1213.!!; 1424 DESCRIPTION 1425 !!The polling mode of this EGP entity, either 1426 passive or active.!!; 1427 ENDPARSE!;; 1428 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 14}; 1430 egpNeighOutErrMsgs ATTRIBUTE 1431 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1432 BEHAVIOUR 1433 egpNeighOutErrMsgsBehaviour BEHAVIOUR 1434 DEFINED AS 1435 !BEGINPARSE 1436 REFERENCE 1437 !!This attribute maps to egpNeighOutErrMsgs with 1438 object id {egpNeighEntry 9} in RFC1213.!!; 1439 DESCRIPTION 1440 !!The number of EGP-defined error messages sent to 1441 this EGP peer.!!; 1442 ENDPARSE!;; 1443 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 9}; 1445 egpNeighOutErrs ATTRIBUTE 1446 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1447 BEHAVIOUR 1448 egpNeighOutErrsBehaviour BEHAVIOUR 1449 DEFINED AS 1450 !BEGINPARSE 1451 REFERENCE 1452 !!This attribute maps to egpNeighOutErrs with 1453 object id {egpNeighEntry 7} in RFC1213.!!; 1454 DESCRIPTION 1455 !!The number of locally generated EGP messages not 1456 sent to this EGP peer due to resource limitations 1457 within an EGP entity.!!; 1458 ENDPARSE!;; 1459 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 7}; 1461 egpNeighOutMsgs ATTRIBUTE 1462 DRAFT February, 1994 1464 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1465 BEHAVIOUR 1466 egpNeighOutMsgsBehaviour BEHAVIOUR 1467 DEFINED AS 1468 !BEGINPARSE 1469 REFERENCE 1470 !!This attribute maps to egpNeighOutMsgs with 1471 object id {egpNeighEntry 6} in RFC1213.!!; 1472 DESCRIPTION 1473 !!The number of locally generated EGP messages to 1474 this EGP peer.!!; 1475 ENDPARSE!;; 1476 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 6}; 1478 egpNeighState ATTRIBUTE 1479 WITH ATTRIBUTE SYNTAX 1480 IIMCRFC12131354ASN1.EgpNeighState; 1481 MATCHES FOR EQUALITY, ORDERING; 1482 BEHAVIOUR 1483 egpNeighStateBehaviour BEHAVIOUR 1484 DEFINED AS 1485 !BEGINPARSE 1486 REFERENCE 1487 !!This attribute maps to egpNeighState 1488 with object id {egpNeighEntry 1} in RFC1213.!!; 1489 DESCRIPTION 1490 !!The EGP state of the local system with respect 1491 to this entry's EGP neighbor. Each EGP state is 1492 represented by a value that is one greater than 1493 the numerical value associated with said state in 1494 RFC 904.!!; 1495 ENDPARSE!;; 1496 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 1}; 1498 egpNeighStateDowns ATTRIBUTE 1499 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1500 BEHAVIOUR 1501 egpNeighStateDownsBehaviour BEHAVIOUR 1502 DEFINED AS 1503 !BEGINPARSE 1504 REFERENCE 1505 !!This attribute maps to egpNeighStateDowns with 1506 object id {egpNeighEntry 11} in RFC1213.!!; 1507 DESCRIPTION 1508 !!The number of EGP state transitions from the UP 1509 state to any other state with this EGP peer.!!; 1510 ENDPARSE!;; 1511 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 11}; 1513 egpNeighStateUps ATTRIBUTE 1514 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1515 BEHAVIOUR 1516 egpNeighStateUpsBehaviour BEHAVIOUR 1517 DEFINED AS 1518 DRAFT February, 1994 1520 !BEGINPARSE 1521 REFERENCE !!This attribute maps to 1522 egpNeighStateUps with object id {egpNeighEntry 10} 1523 in RFC1213.!!; 1524 DESCRIPTION 1525 !!The number of EGP state transitions to the UP 1526 state with this EGP peer.!!; 1527 ENDPARSE!;; 1528 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 5 1 10}; 1530 egpOutErrors ATTRIBUTE 1531 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1532 BEHAVIOUR 1533 egpOutErrorsBehaviour BEHAVIOUR 1534 DEFINED AS 1535 !BEGINPARSE 1536 REFERENCE !!This attribute maps to egpOutErrors 1537 with object id {egp 4} in RFC1213.!!; 1538 DESCRIPTION 1539 !!The number of locally generated EGP messages not 1540 sent due to resource limitations within an EGP 1541 entity.!!; 1542 ENDPARSE!;; 1543 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 4}; 1545 egpOutMsgs ATTRIBUTE 1546 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1547 BEHAVIOUR 1548 egpOutMsgsBehaviour BEHAVIOUR 1549 DEFINED AS 1550 !BEGINPARSE 1551 REFERENCE 1552 !!This attribute maps to egpOutMsgs with object id 1553 {egp 3} in RFC1213.!!; 1554 DESCRIPTION 1555 !!The total number of locally generated EGP 1556 messages.!!; 1557 ENDPARSE!;; 1558 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 8 3}; 1560 icmpId ATTRIBUTE 1561 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.IcmpIdValue; 1562 MATCHES FOR EQUALITY; 1563 BEHAVIOUR 1564 icmpIdBehaviour BEHAVIOUR 1565 DEFINED AS 1566 !The naming attribute for object class icmp.!;; 1567 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 5}; 1569 icmpInAddrMaskReps ATTRIBUTE 1570 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1571 BEHAVIOUR 1572 icmpInAddrMaskRepsBehaviour BEHAVIOUR 1573 DEFINED AS 1574 DRAFT February, 1994 1576 !BEGINPARSE 1577 REFERENCE 1578 !!This attribute maps to icmpInAddrMaskReps with 1579 object id {icmp 13} in RFC1213.!!; 1580 DESCRIPTION 1581 !!The number of ICMP Address Mask Reply messages 1582 received.!!; 1583 ENDPARSE!;; 1584 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 13}; 1586 icmpInAddrMasks ATTRIBUTE 1587 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1588 BEHAVIOUR 1589 icmpInAddrMasksBehaviour BEHAVIOUR 1590 DEFINED AS 1591 !BEGINPARSE 1592 REFERENCE 1593 !!This attribute maps to icmpInAddrMasks with 1594 object id {icmp 12} in RFC1213.!!; 1595 DESCRIPTION 1596 !!The number of ICMP Address Mask Request messages 1597 received.!!; 1598 ENDPARSE!;; 1599 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 12}; 1601 icmpInDestUnreachs ATTRIBUTE 1602 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1603 BEHAVIOUR 1604 icmpInDestUnreachsBehaviour BEHAVIOUR 1605 DEFINED AS 1606 !BEGINPARSE 1607 REFERENCE 1608 !!This attribute maps to icmpInDestUnreachs with 1609 object id {icmp 3} in RFC1213.!!; 1610 DESCRIPTION 1611 !!The number of ICMP Destination Unreachable 1612 messages received.!!; 1613 ENDPARSE!;; 1614 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 3}; 1616 icmpInEchoReps ATTRIBUTE 1617 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1618 BEHAVIOUR 1619 icmpInEchoRepsBehaviour BEHAVIOUR 1620 DEFINED AS 1621 !BEGINPARSE 1622 REFERENCE 1623 !!This attribute maps to icmpInEchoReps with 1624 object id {icmp 9} in RFC1213.!!; 1625 DESCRIPTION 1626 !!The number of ICMP Echo Reply messages 1627 received.!!; 1628 ENDPARSE!;; 1629 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 9}; 1630 DRAFT February, 1994 1632 icmpInEchos ATTRIBUTE 1633 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1634 BEHAVIOUR 1635 icmpInEchosBehaviour BEHAVIOUR 1636 DEFINED AS 1637 !BEGINPARSE 1638 REFERENCE 1639 !!This attribute maps to icmpInEchos with object 1640 id {icmp 8} in RFC 1213.!!; 1641 DESCRIPTION 1642 !!The number of ICMP Echo (request) messages 1643 received.!!; 1644 ENDPARSE!;; 1645 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 8}; 1647 icmpInErrors ATTRIBUTE 1648 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1649 BEHAVIOUR 1650 icmpInErrorsBehaviour BEHAVIOUR 1651 DEFINED AS 1652 !BEGINPARSE 1653 REFERENCE 1654 !!This attribute maps to icmpInErrors with object 1655 id {icmp 2} in RFC1213.!!; 1656 DESCRIPTION 1657 !!The number of ICMP messages which the entity 1658 received but determined as having ICMP-specific 1659 errors (bad ICMP checksums, bad length, etc.).!!; 1660 ENDPARSE!;; 1661 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 2}; 1663 icmpInMsgs ATTRIBUTE 1664 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1665 BEHAVIOUR 1666 icmpInMsgsBehaviour BEHAVIOUR 1667 DEFINED AS 1668 !BEGINPARSE 1669 REFERENCE 1670 !!This attribute maps to icmpInMsgs with object id 1671 {icmp 1} in RFC1213.!!; 1672 DESCRIPTION 1673 !!The total number of ICMP messages which the 1674 entity received. Note that this counter includes 1675 all those counted by icmpInErrors.!!; 1676 ENDPARSE!;; 1677 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 1}; 1679 icmpInParmProbs ATTRIBUTE 1680 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1681 BEHAVIOUR 1682 icmpInParmProbsBehaviour BEHAVIOUR 1683 DEFINED AS 1684 !BEGINPARSE 1685 DRAFT February, 1994 1687 REFERENCE 1688 !!This attribute maps to icmpInParmProbs with 1689 object id {icmp 5} in RFC1213.!!; 1690 DESCRIPTION 1691 !!The number of ICMP Parameter Problem messages 1692 received.!!; 1693 ENDPARSE!;; 1694 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 5}; 1696 icmpInRedirects ATTRIBUTE 1697 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1698 BEHAVIOUR 1699 icmpInRedirectsBehaviour BEHAVIOUR 1700 DEFINED AS 1701 !BEGINPARSE 1702 REFERENCE 1703 !!This attribute maps to icmpInRedirects with id 1704 {icmp 7} in RFC1213.!!; 1705 DESCRIPTION 1706 !!The number of ICMP Redirect messages 1707 received.!!; 1708 ENDPARSE!;; 1709 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 7}; 1711 icmpInSrcQuenchs ATTRIBUTE 1712 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1713 BEHAVIOUR 1714 icmpInSrcQuenchsBehaviour BEHAVIOUR 1715 DEFINED AS 1716 !BEGINPARSE 1717 REFERENCE 1718 !!This attribute maps to icmpInSrcQuenchs with 1719 object id {icmp 6} in RFC1213.!!; 1720 DESCRIPTION 1721 !!The number of ICMP Source Quench messages 1722 received.!!; 1723 ENDPARSE!;; 1724 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 6}; 1726 icmpInTimeExcds ATTRIBUTE 1727 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1728 BEHAVIOUR 1729 icmpInTimeExcdsBehaviour BEHAVIOUR 1730 DEFINED AS 1731 !BEGINPARSE 1732 REFERENCE 1733 !!This attribute maps to icmpInTimeExcds with 1734 object id {icmp 4} in RFC1213.!!; 1735 DESCRIPTION 1736 !!The number of ICMP Time Exceeded messages 1737 received.!!; 1738 ENDPARSE!;; 1739 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 4}; 1740 DRAFT February, 1994 1742 icmpInTimestampReps ATTRIBUTE 1743 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1744 BEHAVIOUR 1745 icmpInTimestampRepsBehaviour BEHAVIOUR 1746 DEFINED AS 1747 !BEGINPARSE 1748 REFERENCE 1749 !!This attribute maps to icmpInTimestampReps with 1750 object id {icmp 11} in RFC1213.!!; 1751 DESCRIPTION 1752 !!The number of ICMP Timestamp Reply messages 1753 received.!!; 1754 ENDPARSE!;; 1755 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 11}; 1757 icmpInTimestamps ATTRIBUTE 1758 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1759 BEHAVIOUR 1760 icmpInTimeStampsBehaviour BEHAVIOUR 1761 DEFINED AS 1762 !BEGINPARSE 1763 REFERENCE 1764 !!This attribute maps to icmpInTimestamps with 1765 object id {icmp 10} in RFC1213.!!; 1766 DESCRIPTION 1767 !!The number of ICMP Timestamp (request) messages 1768 received.!!; 1769 ENDPARSE!;; 1770 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 10}; 1772 icmpOutAddrMaskReps ATTRIBUTE 1773 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1774 BEHAVIOUR 1775 icmpOutAddrMaskRepsBehaviour BEHAVIOUR 1776 DEFINED AS 1777 !BEGINPARSE 1778 REFERENCE 1779 !!This attribute maps to icmpOutAddrMaskReps with 1780 object id {icmp 26} in RFC1213.!!; 1781 DESCRIPTION 1782 !!The number of ICMP Timestamp (request) messages 1783 received. The number of ICMP Address Mask Reply 1784 messages sent.!!; 1785 ENDPARSE!;; 1786 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 26}; 1788 icmpOutAddrMasks ATTRIBUTE 1789 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1790 BEHAVIOUR 1791 icmpOutAddrMasksBehaviour BEHAVIOUR 1792 DEFINED AS 1793 !BEGINPARSE 1794 REFERENCE 1795 DRAFT February, 1994 1797 !!This attribute map to icmpOutAddrMasks with 1798 object id {icmp 25} in RFC1213.!!; 1799 DESCRIPTION 1800 !!The number of ICMP Address Mask Request messages 1801 sent.!!; 1802 ENDPARSE!;; 1803 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 25}; 1805 icmpOutDestUnreachs ATTRIBUTE 1806 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1807 BEHAVIOUR 1808 icmpOutDestUnreachsBehaviour BEHAVIOUR 1809 DEFINED AS 1810 !BEGINPARSE 1811 REFERENCE 1812 !!This attribute maps to icmpOutDestUnreachs with 1813 object id {icmp 16} in RFC1213.!!; 1814 DESCRIPTION 1815 !!The number of ICMP Destination Unreachable 1816 messages sent.!!; 1817 ENDPARSE!;; 1818 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 16}; 1820 icmpOutEchoReps ATTRIBUTE 1821 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1822 BEHAVIOUR 1823 icmpOutEchoRepsBehaviour BEHAVIOUR 1824 DEFINED AS 1825 !BEGINPARSE 1826 REFERENCE 1827 !!This attribute maps to icmpOutEchoReps with 1828 object id {icmp 22} in RFC1213.!!; 1829 DESCRIPTION 1830 !!The number of ICMP Echo Reply messages sent.!!; 1831 ENDPARSE!;; 1832 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 22}; 1834 icmpOutEchos ATTRIBUTE 1835 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1836 BEHAVIOUR 1837 icmpOutEchosBehaviour BEHAVIOUR 1838 DEFINED AS 1839 !BEGINPARSE 1840 REFERENCE 1841 !!This attribute maps to icmpOutEchos with object 1842 id {icmp 21} in RFC1213.!!; 1843 DESCRIPTION 1844 !!The number of ICMP Echo (request) messages 1845 sent.!!; 1846 ENDPARSE!;; 1847 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 21}; 1849 icmpOutErrors ATTRIBUTE 1850 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1851 DRAFT February, 1994 1853 BEHAVIOUR 1854 icmpOutErrorsBehaviour BEHAVIOUR 1855 DEFINED AS 1856 !BEGINPARSE 1857 REFERENCE 1858 !!This attribute maps to icmpOutErrors with object 1859 id {icmp 15} in RFC1213.!!; 1860 DESCRIPTION 1861 !!The number of ICMP messages which this entity 1862 did not send due to problems discovered within 1863 ICMP such as a lack of buffers. This value should 1864 not include errors discovered outside the ICMP 1865 layer such as the inability of IP to route the 1866 resultant datagram. In some implementations there 1867 may be no types of error which contribute to this 1868 counter's value.!!; 1869 ENDPARSE!;; 1870 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 15}; 1872 icmpOutMsgs ATTRIBUTE 1873 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1874 BEHAVIOUR 1875 icmpOutMsgsBehaviour BEHAVIOUR 1876 DEFINED AS 1877 !BEGINPARSE 1878 REFERENCE 1879 !!This attribute maps to icmpOutMsgs with object 1880 id {icmp 14} in RFC1213.!!; 1881 DESCRIPTION 1882 !!The total number of ICMP messages which this 1883 entity attempted to send. Note that this counter 1884 includes all those counted by icmpOutErrors.!!; 1885 ENDPARSE!;; 1886 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 14}; 1888 icmpOutParmProbs ATTRIBUTE 1889 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1890 BEHAVIOUR 1891 icmpOutParmProbsBehaviour BEHAVIOUR 1892 DEFINED AS 1893 !BEGINPARSE 1894 REFERENCE 1895 !!This attribute maps to icmpOutParmProbs with 1896 object id{icmp 18} in RFC1213.!!; 1897 DESCRIPTION 1898 !!The number of ICMP Parameter Problem messages 1899 sent.!!; 1900 ENDPARSE!;; 1901 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 18}; 1903 icmpOutRedirects ATTRIBUTE 1904 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1905 BEHAVIOUR 1906 icmpOutRedirectsBehaviour BEHAVIOUR 1907 DRAFT February, 1994 1909 DEFINED AS 1910 !BEGINPARSE 1911 REFERENCE 1912 !!This attribute maps to icmpOutRedirects with 1913 object id {icmp 20} in RFC1213.!!; 1914 DESCRIPTION 1915 !!The number of ICMP Redirect messages sent. For a 1916 host, this attribute will always be zero, since 1917 hosts do not send redirects.!!; 1918 ENDPARSE!;; 1919 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 20}; 1921 icmpOutSrcQuenchs ATTRIBUTE 1922 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1923 BEHAVIOUR 1924 icmpOutSrcQuenchsBehaviour BEHAVIOUR 1925 DEFINED AS 1926 !BEGINPARSE 1927 REFERENCE 1928 !!This attribute maps to icmpOutSrcQuenchs with 1929 object id {icmp 19} in RFC1213.!!; 1930 DESCRIPTION 1931 !!The number of ICMP Source Quench messages 1932 sent.!!; 1933 ENDPARSE!;; 1934 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 19}; 1936 icmpOutTimeExcds ATTRIBUTE 1937 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1938 BEHAVIOUR 1939 icmpOutTimeExcdsBehaviour BEHAVIOUR 1940 DEFINED AS 1941 !BEGINPARSE 1942 REFERENCE 1943 !!This attribute maps to icmpOutTimeExcds with 1944 object id {icmp 17} in RFC1213.!!; 1945 DESCRIPTION 1946 !!The number of ICMP Time Exceeded messages 1947 sent.!!; 1948 ENDPARSE!;; 1949 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 17}; 1951 icmpOutTimestampReps ATTRIBUTE 1952 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1953 BEHAVIOUR 1954 icmpOutTimestampRepsBehaviour BEHAVIOUR 1955 DEFINED AS 1956 !BEGINPARSE 1957 REFERENCE 1958 !!This attribute maps to icmpOutTimestampReps with 1959 object id {icmp 24} in RFC1213.!!; 1960 DESCRIPTION 1961 !!The number of ICMP Timestamp Reply messages 1962 sent.!!; 1963 DRAFT February, 1994 1965 ENDPARSE!;; 1966 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 24}; 1968 icmpOutTimestamps ATTRIBUTE 1969 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 1970 BEHAVIOUR 1971 icmpOutTimestampsBehaviour BEHAVIOUR 1972 DEFINED AS 1973 !BEGINPARSE 1974 REFERENCE 1975 !!This attribute maps to icmpOutTimestamps with 1976 object id {icmp 23} in RFC1213.!!; 1977 DESCRIPTION 1978 !!The number of ICMP Timestamp (request) messages 1979 sent.!!; 1980 ENDPARSE!;; 1981 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 5 23}; 1983 ifAdminStatus ATTRIBUTE 1984 WITH ATTRIBUTE SYNTAX 1985 IIMCRFC12131354ASN1.IfAdminStatus; 1986 MATCHES FOR EQUALITY, ORDERING; 1987 BEHAVIOUR 1988 ifAdminStatusBehaviour BEHAVIOUR 1989 DEFINED AS 1990 !BEGINPARSE 1991 REFERENCE 1992 !!This attribute maps to ifAdminStatus with object 1993 id {ifEntry 7} in RFC1213.!!; 1994 DESCRIPTION 1995 !!The desired state of the interface. The 1996 testing(3) state indicates that no operational 1997 packets can be passed.!!; 1998 ENDPARSE!;; 1999 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 7}; 2001 ifDescr ATTRIBUTE 2002 DERIVED FROM {iimcIIMCIMIBTRANS}:displayString; 2003 BEHAVIOUR 2004 ifDescrBehaviour BEHAVIOUR 2005 DEFINED AS 2006 !BEGINPARSE 2007 REFERENCE 2008 !!This attribute maps to ifDescr with object id 2009 {ifEntry 2} in RFC 1213.!!; 2010 DESCRIPTION 2011 !!A textual string containing information about 2012 the interface. This string should include the name 2013 of the manufacturer, the product name and the 2014 version of the hardware interface.!!; 2015 ENDPARSE!;; 2016 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 2}; 2018 ifEntryId ATTRIBUTE 2019 DRAFT February, 1994 2021 WITH ATTRIBUTE SYNTAX 2022 IIMCRFC12131354ASN1.IfEntryIdValue; 2023 MATCHES FOR EQUALITY; 2024 BEHAVIOUR 2025 ifEntryIdBehaviour BEHAVIOUR 2026 DEFINED AS 2027 !The naming attribute for object class ifEntry.!;; 2028 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 2 2 1}; 2030 ifIndex ATTRIBUTE 2031 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2032 MATCHES FOR EQUALITY, ORDERING; 2033 BEHAVIOUR 2034 ifIndexBehaviour BEHAVIOUR 2035 DEFINED AS 2036 !BEGINPARSE 2037 REFERENCE 2038 !!This attribute maps to ifIndex with object id 2039 {ifEntry 1} in RFC 1213.!!; 2040 DESCRIPTION 2041 !!A unique value for each interface. Its value 2042 ranges between 1 and the value of ifNumber. The 2043 value for each interface must remain constant at 2044 least from one re-initialization of the entity's 2045 network management system to the next re- 2046 initialization.!!; 2047 ENDPARSE!;; 2048 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 1}; 2050 ifInDiscards ATTRIBUTE 2051 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2052 BEHAVIOUR 2053 ifInDiscardsBehaviour BEHAVIOUR 2054 DEFINED AS 2055 !BEGINPARSE 2056 REFERENCE 2057 !!This attribute maps to ifInDiscards with object 2058 id {ifEntry 13} in RFC1213.!!; 2059 DESCRIPTION 2060 !!The number of inbound packets which were chosen 2061 to be discarded even though no errors had been 2062 detected to prevent their being deliverable to a 2063 higher-layer protocol. One possible reason for 2064 discarding such a packet could be to free up 2065 buffer space.!!; 2066 ENDPARSE!;; 2067 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 13}; 2069 ifInErrors ATTRIBUTE 2070 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2071 BEHAVIOUR 2072 ifInErrorsBehaviour BEHAVIOUR 2073 DEFINED AS 2074 !BEGINPARSE 2075 DRAFT February, 1994 2077 REFERENCE 2078 !!This attribute maps to ifInErrors with object id 2079 {ifEntry 14} in RFC1213.!!; 2080 DESCRIPTION 2081 !!The number of inbound packets that contained 2082 errors preventing them from being deliverable to a 2083 higher-layer protocol.!!; 2084 ENDPARSE!;; 2085 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 14}; 2087 ifInNUcastPkts ATTRIBUTE 2088 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2089 BEHAVIOUR 2090 ifInNUcastPktsBehaviour BEHAVIOUR 2091 DEFINED AS 2092 !BEGINPARSE 2093 REFERENCE 2094 !!This attribute maps to ifInNUcastPkts with 2095 object id {ifEntry 12} in RFC1213.!!; 2096 DESCRIPTION 2097 !!The number of non-unicast (i.e., subnetwork- 2098 broadcast or subnetwork-multicast) packets 2099 delivered to a higher-layer protocol.!!; 2100 ENDPARSE!;; 2101 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 12}; 2103 ifInOctets ATTRIBUTE 2104 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2105 BEHAVIOUR 2106 ifInOctetsBehaviour BEHAVIOUR 2107 DEFINED AS 2108 !BEGINPARSE 2109 REFERENCE 2110 !!This attribute maps to ifInOctets with object id 2111 {ifEntry 10} in RFC1213.!!; 2112 DESCRIPTION 2113 !!The total number of octets received on the 2114 interface, including framing characters.!!; 2115 ENDPARSE!;; 2116 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 10}; 2118 ifInUcastPkts ATTRIBUTE 2119 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2120 BEHAVIOUR 2121 ifInUcastPktsBehaviour BEHAVIOUR 2122 DEFINED AS 2123 !BEGINPARSE 2124 REFERENCE 2125 !!This attribute maps to ifInUcastPkts with object 2126 id {ifEntry 11} in RFC1213.!!; 2127 DESCRIPTION 2128 !!The number of subnetwork-unicast packets 2129 delivered to a higher-layer protocol.!!; 2130 ENDPARSE!;; 2131 DRAFT February, 1994 2133 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 11}; 2135 ifInUnknownProtos ATTRIBUTE 2136 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2137 BEHAVIOUR 2138 ifInUnknownProtosBehaviour BEHAVIOUR 2139 DEFINED AS 2140 !BEGINPARSE 2141 REFERENCE 2142 !!This attribute maps to ifInUnknownProtos with 2143 object id {if Entry 15} in RFC1213.!!; 2144 DESCRIPTION 2145 !!The number of packets received via the interface 2146 which were discarded because of an unknown or 2147 unsupported protocol.!!; 2148 ENDPARSE!;; 2149 REGISTERED AS { iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 15}; 2151 ifLastChange ATTRIBUTE 2152 DERIVED FROM {iimcIIMCIMIBTRANS}: timeTicks; 2153 BEHAVIOUR 2154 ifLastChangeBehaviour BEHAVIOUR 2155 DEFINED AS 2156 !BEGINPARSE 2157 REFERENCE 2158 !!This attribute maps to ifLastChange with object 2159 id {ifEntry 9} in RFC1213.!!; 2160 DESCRIPTION 2161 !!The value of sysUpTime at the time the interface 2162 entered its current operational state. If the 2163 current state was entered prior to the last re- 2164 initialization of the local network management 2165 subsystem, then this attribute contains a zero 2166 value.!!; 2167 ENDPARSE!;; 2168 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 9}; 2170 ifMtu ATTRIBUTE 2171 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2172 MATCHES FOR EQUALITY, ORDERING; 2173 BEHAVIOUR 2174 ifMtuBehaviour BEHAVIOUR 2175 DEFINED AS 2176 !BEGINPARSE 2177 REFERENCE 2178 !!This attribute maps to ifMtu with object id 2179 {ifEntry 4} in RFC1213.!!; 2180 DESCRIPTION 2181 !!The size of the largest datagram which can be 2182 sent/received on the interface, specified in 2183 octets. For interfaces that are used for 2184 transmitting network datagrams, this is the size 2185 of the largest network datagram that can be sent 2186 on the interface.!!; 2187 DRAFT February, 1994 2189 ENDPARSE!;; 2190 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 4}; 2192 ifNumber ATTRIBUTE 2193 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2194 MATCHES FOR EQUALITY, ORDERING; 2195 BEHAVIOUR 2196 ifNumberBehaviour BEHAVIOUR 2197 DEFINED AS 2198 !BEGINPARSE 2199 REFERENCE 2200 !!This attribute maps to ifNumber with object id 2201 {interfaces 1} in RFC1213.!!; 2202 DESCRIPTION 2203 !!The number of network interfaces (regardless of 2204 their current state) present on this system.!!; 2205 ENDPARSE!;; 2206 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 1}; 2208 ifOperStatus ATTRIBUTE 2209 WITH ATTRIBUTE SYNTAX 2210 IIMCRFC12131354ASN1.IfOperStatus; 2211 MATCHES FOR EQUALITY, ORDERING; 2212 BEHAVIOUR 2213 ifOperStatusBehaviour BEHAVIOUR 2214 DEFINED AS 2215 !BEGINPARSE 2216 REFERENCE 2217 !!This attribute maps to ifOperStatus with object 2218 id {ifEntry 8} in RFC1213.!!; 2219 DESCRIPTION 2220 !!The current operational state of the interface. 2221 The testing(3) state indicates that no operational 2222 packets can be passed.!!; 2223 ENDPARSE!;; 2224 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 8}; 2226 ifOutDiscards ATTRIBUTE 2227 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2228 BEHAVIOUR 2229 ifOutDiscardsBehaviour BEHAVIOUR 2230 DEFINED AS 2231 !BEGINPARSE 2232 REFERENCE 2233 !!This attribute maps to ifOutDiscards with object 2234 id {ifEntry 19} in RFC1213.!!; 2235 DESCRIPTION 2236 !!The number of outbound packets which were chosen 2237 to be discarded even though no errors had been 2238 detected to prevent their being transmitted. One 2239 possible reason for discarding such a packet could 2240 be to free up buffer space.!!; 2241 ENDPARSE!;; 2242 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 19}; 2243 DRAFT February, 1994 2245 ifOutErrors ATTRIBUTE 2246 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2247 BEHAVIOUR 2248 ifOutErrorsBehaviour BEHAVIOUR 2249 DEFINED AS 2250 !BEGINPARSE 2251 REFERENCE 2252 !!This attribute maps to ifOutErrors with object 2253 id {ifEntry 20} in RFC1213.!!; 2254 DESCRIPTION 2255 !!The number of outbound packets that could not be 2256 transmitted because of errors.!!; 2257 ENDPARSE!;; 2258 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 20}; 2260 ifOutNUcastPkts ATTRIBUTE 2261 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2262 BEHAVIOUR 2263 ifOutNUcastPktsBehaviour BEHAVIOUR 2264 DEFINED AS 2265 !BEGINPARSE 2266 REFERENCE 2267 !!This attribute maps to ifOutNUcastPkts with 2268 object id {ifEntry 18} in RFC1213.!!; 2269 DESCRIPTION 2270 !!The total number of packets that higher-level 2271 protocols requested be transmitted to a non- 2272 unicast (i.e., a subnetwork-broadcast or 2273 subnetwork-multicast) address, including those 2274 that were discarded or not sent.!!; 2275 ENDPARSE!;; 2276 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 18}; 2278 ifOutOctets ATTRIBUTE 2279 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2280 BEHAVIOUR 2281 ifOutOctetsBehaviour BEHAVIOUR 2282 DEFINED AS 2283 !BEGINPARSE 2284 REFERENCE 2285 !!This attribute maps to ifOutOctets with object 2286 id {ifEntry 16} in RFC1213.!!; 2287 DESCRIPTION 2288 !!The total number of octets transmitted out of 2289 the interface, including framing characters.!!; 2290 ENDPARSE!;; 2291 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 16}; 2293 ifOutQLen ATTRIBUTE 2294 DERIVED FROM {iimcIIMCIMIBTRANS}: gauge32; 2295 BEHAVIOUR 2296 ifOutQLenBehaviour BEHAVIOUR 2297 DEFINED AS 2298 DRAFT February, 1994 2300 !BEGINPARSE 2301 REFERENCE 2302 !!This attribute maps to ifOutQLen with object id 2303 {ifEntry 21} in RFC1213.!!; 2304 DESCRIPTION 2305 !!The length of the output packet queue (in 2306 packets).!!; 2307 ENDPARSE!;; 2308 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 21}; 2310 ifOutUcastPkts ATTRIBUTE 2311 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2312 BEHAVIOUR 2313 ifOutUcastPktsBehaviour BEHAVIOUR 2314 DEFINED AS 2315 !BEGINPARSE 2316 REFERENCE 2317 !!This attribute maps to ifOutUcastPkts with 2318 object id {ifEntry 17} in RFC1213.!!; 2319 DESCRIPTION 2320 !!The total number of packets that higher-level 2321 protocols requested be transmitted to a 2322 subnetwork-unicast address, including those that 2323 were discarded or not sent.!!; 2324 ENDPARSE!;; 2325 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 17}; 2327 ifPhysAddress ATTRIBUTE 2328 DERIVED FROM {iimcIIMCIMIBTRANS}:physAddress; 2329 BEHAVIOUR 2330 ifPhysAddressBehaviour BEHAVIOUR 2331 DEFINED AS 2332 !BEGINPARSE 2333 REFERENCE 2334 !!This attribute maps to ifPhysAddress with object 2335 id {ifEntry 6} in RFC 1213.!!; 2336 DESCRIPTION 2337 !!The interface's address at the protocol layer 2338 immediately `below' the network layer in the 2339 protocol stack. For interfaces which do not have 2340 such an address (e.g., a serial line), this 2341 attribute should contain an octet string of zero 2342 length.!!; 2343 ENDPARSE!;; 2344 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 6}; 2346 ifSpecific ATTRIBUTE 2347 WITH ATTRIBUTE SYNTAX 2348 IIMCRFC12131354ASN1.ObjectIdentifier; 2349 MATCHES FOR EQUALITY, ORDERING; 2350 BEHAVIOUR 2351 ifSpecificBehaviour BEHAVIOUR 2352 DEFINED AS 2353 !BEGINPARSE 2354 DRAFT February, 1994 2356 REFERENCE 2357 !!This attribute maps to ifSpecific with object id 2358 {ifEntry 22} in RFC1213.!!; 2359 DESCRIPTION 2360 !!A reference to MIB definitions specific to the 2361 particular media being used to realize the 2362 interface. For example, if the interface is 2363 realized by an ethernet, then the value of this 2364 attribute refers to a document defining attributes 2365 specific to ethernet. If this information is not 2366 present, its value should be set to the OBJECT 2367 IDENTIFIER { 0 0 }, which is a syntactically valid 2368 object identifier, and any conformant 2369 implementation of ASN.1 and BER must be able to 2370 generate and recognize this value.!!; 2371 ENDPARSE!;; 2372 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 22}; 2374 ifSpeed ATTRIBUTE 2375 DERIVED FROM {iimcIIMCIMIBTRANS}:gauge32; 2376 BEHAVIOUR 2377 ifSpeedBehaviour BEHAVIOUR 2378 DEFINED AS 2379 !BEGINPARSE 2380 REFERENCE 2381 !!This attribute maps to ifSpeed with object id 2382 {ifEntry 5} in RFC 1213.!!; 2383 DESCRIPTION 2384 !!An estimate of the interface's current bandwidth 2385 in bits per second. For interfaces which do not 2386 vary in bandwidth or for those where no accurate 2387 estimation can be made, this attribute should 2388 contain the nominal bandwidth.!!; 2389 ENDPARSE!;; 2390 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 5}; 2392 ifType ATTRIBUTE 2393 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.IfType; 2394 MATCHES FOR EQUALITY, ORDERING; 2395 BEHAVIOUR 2396 ifTypeBehaviour BEHAVIOUR 2397 DEFINED AS 2398 !BEGINPARSE 2399 REFERENCE 2400 !!This attribute maps to ifType with object id 2401 {ifEntry 3} in RFC1213.!!; 2402 DESCRIPTION 2403 !!The type of interface, distinguished according 2404 to the physical/link protocol(s) immediately 2405 `below' the network layer in the protocol 2406 stack.!!; 2407 ENDPARSE!;; 2408 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 2 2 1 3}; 2409 DRAFT February, 1994 2411 interfacesId ATTRIBUTE 2412 WITH ATTRIBUTE SYNTAX 2413 IIMCRFC12131354ASN1.InterfacesIdValue; 2414 MATCHES FOR EQUALITY; 2415 BEHAVIOUR 2416 interfacesIdBehaviour BEHAVIOUR 2417 DEFINED AS 2418 !The naming attribute for object class 2419 interfaces.!;; 2420 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 2}; 2422 internetSystemId ATTRIBUTE 2423 WITH ATTRIBUTE SYNTAX 2424 IIMCRFC12131354ASN1.InternetSystemIdValue; 2425 MATCHES FOR EQUALITY; 2426 BEHAVIOUR 2427 internetSystemIdBehaviour BEHAVIOUR 2428 DEFINED AS 2429 !The naming attribute for object class 2430 internetSystem.!;; 2431 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 1}; 2433 ipAddrEntryId ATTRIBUTE 2434 WITH ATTRIBUTE SYNTAX 2435 IIMCRFC12131354ASN1.IpAddrEntryIdValue; 2436 MATCHES FOR EQUALITY; 2437 BEHAVIOUR 2438 ipAddrEntryIdBehaviour BEHAVIOUR 2439 DEFINED AS 2440 !The naming attribute for object class 2441 ipAddrEntry.!;; 2442 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 4 20 1}; 2444 ipAdEntAddr ATTRIBUTE 2445 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 2446 BEHAVIOUR 2447 ipAdEntAddrBehaviour BEHAVIOUR 2448 DEFINED AS 2449 !BEGINPARSE 2450 REFERENCE 2451 !!This attribute maps to ipAdEntAddr with object 2452 id {ipAddrEntry 1} in RFC1213.!!; 2453 DESCRIPTION 2454 !!The IP address to which this entry's addressing 2455 information pertains.!!; 2456 ENDPARSE!;; 2457 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 20 1 1}; 2459 ipAdEntBcastAddr ATTRIBUTE 2460 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2461 MATCHES FOR EQUALITY, ORDERING; 2462 BEHAVIOUR 2463 ipAdEntBcastAddrBehaviour BEHAVIOUR 2464 DEFINED AS 2465 DRAFT February, 1994 2467 !BEGINPARSE 2468 REFERENCE 2469 !!This attribute maps to ipAdEntBcastAddr with 2470 object id {ipAddrEntry 4} in RFC1213.!!; 2471 DESCRIPTION 2472 !!The value of the least-significant bit in the IP 2473 broadcast address used for sending datagrams on 2474 the (logical) interface associated with the IP 2475 address of this entry. For example, when the 2476 Internet standard all-ones broadcast address is 2477 used, the value will be 1. This value applies to 2478 both the subnet and network broadcasts addresses 2479 used by the entity on this (logical) interface.!!; 2480 ENDPARSE!;; 2481 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 20 1 4}; 2483 ipAdEntIfIndex ATTRIBUTE 2484 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2485 MATCHES FOR EQUALITY, ORDERING; 2486 BEHAVIOUR 2487 ipAdEntIfIndexBehaviour BEHAVIOUR 2488 DEFINED AS 2489 !BEGINPARSE 2490 REFERENCE 2491 !!This attribute maps to ipAdEntIfIndex with 2492 object id {ipAddrEntry 2} in RFC1213.!!; 2493 DESCRIPTION 2494 !!The index value which uniquely identifies the 2495 interface to which this entry is applicable. The 2496 interface identified by a particular value of this 2497 index is the same interface as identified by the 2498 same value of ifIndex.!!; 2499 ENDPARSE!;; 2500 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 20 1 2}; 2502 ipAdEntNetMask ATTRIBUTE 2503 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 2504 BEHAVIOUR 2505 ipAdEntNetMaskBehaviour BEHAVIOUR 2506 DEFINED AS 2507 !BEGINPARSE 2508 REFERENCE 2509 !!This attribute maps to ipAdEntNetMask with 2510 object id {ipAddrEntry 3} in RFC1213.!!; 2511 DESCRIPTION 2512 !!The subnet mask associated with the IP address 2513 of this entry. The value of the mask is an IP 2514 address with all the network bits set to 1 and all 2515 the hosts bits set to 0.!!; 2516 ENDPARSE!;; 2517 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 20 1 3}; 2519 ipAdEntReasmMaxSize ATTRIBUTE 2520 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer64k; 2521 DRAFT February, 1994 2523 MATCHES FOR EQUALITY, ORDERING; 2524 BEHAVIOUR 2525 ipAdEntReasmMaxSizeBehaviour BEHAVIOUR 2526 DEFINED AS 2527 !BEGINPARSE 2528 REFERENCE 2529 !!This attribute maps to ipAdEntReasmMaxSize with 2530 object id {ipAddrEntry 5} in RFC1213.!!; 2531 DESCRIPTION 2532 !!The size of the largest IP datagram which this 2533 entity can re-assemble from incoming IP fragmented 2534 datagrams received on this interface.!!; 2535 ENDPARSE!;; 2536 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 20 1 5}; 2538 ipDefaultTTL ATTRIBUTE 2539 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2540 MATCHES FOR EQUALITY, ORDERING; 2541 BEHAVIOUR 2542 ipDefaultTTLBehaviour BEHAVIOUR 2543 DEFINED AS 2544 !BEGINPARSE 2545 REFERENCE 2546 !!This attribute maps to ipDefaultTTL with object 2547 id {ip 2} in RFC1213.!!; 2548 DESCRIPTION 2549 !!The default value inserted into the Time-To-Live 2550 field of the IP header of datagrams originated at 2551 this entity, whenever a TTL value is not supplied 2552 by the transport layer protocol.!!; 2553 ENDPARSE!;; 2554 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 2}; 2556 ipForwardAge ATTRIBUTE 2557 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2558 MATCHES FOR EQUALITY, ORDERING; 2559 BEHAVIOUR 2560 ipForwardAgeBehaviour BEHAVIOUR 2561 DEFINED AS 2562 !BEGINPARSE 2563 REFERENCE 2564 !!This attribute maps to ipForwardAge with object 2565 id {ipForwardEntry 8} in RFC1354.!!; 2566 DESCRIPTION 2567 !!The number of seconds since this route was last 2568 updated or otherwise determined to be correct. 2569 Note that no semantics of `too old' can be 2570 implied except through knowledge of the routing 2571 protocol by which the route was learned.!!; 2572 ENDPARSE!;; 2573 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 8}; 2575 ipForwardDest ATTRIBUTE 2576 DERIVED FROM {iimcIIMCIMIBTRANS}: ipAddress; 2577 DRAFT February, 1994 2579 BEHAVIOUR 2580 ipForwardDestBehaviour BEHAVIOUR 2581 DEFINED AS 2582 !BEGINPARSE 2583 REFERENCE 2584 !!This attribute maps to ipForwardDest with object 2585 id {ipForwardEntry 1} in RFC1354.!!; 2586 DESCRIPTION 2587 !!The destination IP address of this route. An 2588 entry with a value of 0.0.0.0 is considered a 2589 default route. 2591 This attribute may not take a Multicast (Class D) 2592 address value. 2594 Any assignment (implicit or otherwise) of an 2595 instance of this attribute to a value x must be 2596 rejected if the bitwise logical-AND of x with the 2597 value of the corresponding instance of the 2598 ipForwardMask attribute is not equal to x.!!; 2599 ENDPARSE!;; 2600 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 1}; 2602 ipForwardEntryId ATTRIBUTE 2603 WITH ATTRIBUTE SYNTAX 2604 IIMCRFC12131354ASN1.IpForwardEntryIdValue; 2605 MATCHES FOR EQUALITY; 2606 BEHAVIOUR 2607 ipForwardEntryIdBehaviour BEHAVIOUR 2608 DEFINED AS 2609 !The naming attribute for object class 2610 ipForwardEntry.!;; 2611 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 4 24 2 1}; 2613 ipForwardIfIndex ATTRIBUTE 2614 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2615 MATCHES FOR EQUALITY, ORDERING; 2616 BEHAVIOUR 2617 ipForwardIfIndexBehaviour BEHAVIOUR 2618 DEFINED AS 2619 !BEGINPARSE 2620 REFERENCE 2621 !!This attribute maps to ipForwardIfIndex with 2622 object id {ipForwardEntry 5} in RFC1354.!!; 2623 DESCRIPTION 2624 !!The ifIndex value which identifies the local 2625 interface through which the next hop of this 2626 route should be reached.!!; 2627 ENDPARSE!;; 2628 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 5}; 2630 ipForwardInfo ATTRIBUTE 2631 WITH ATTRIBUTE SYNTAX 2632 IIMCRFC12131354ASN1.ObjectIdentifier; 2633 DRAFT February, 1994 2635 MATCHES FOR EQUALITY, ORDERING; 2636 BEHAVIOUR 2637 ipForwardInfoBehaviour BEHAVIOUR 2638 DEFINED AS 2639 !BEGINPARSE 2640 REFERENCE 2641 !!This attribute maps to ipForwardInfo with object 2642 id {ipForwardEntry 9} in RFC1354.!!; 2643 DESCRIPTION 2644 !!A reference to MIB definitions specific to the 2645 particular routing protocol which is responsible 2646 for this route, as determined by the value 2647 specified in the route's ipForwardProto value. If 2648 this information is not present, its value should 2649 be set to the OBJECT IDENTIFIER {0 0 }, which is a 2650 syntactically valid object identifier, and any 2651 implementation conforming to ASN.1 and the Basic 2652 Encoding Rules must be able to generate and 2653 recognize this value.!!; 2654 ENDPARSE!;; 2655 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 9}; 2657 ipForwarding ATTRIBUTE 2658 WITH ATTRIBUTE SYNTAX 2659 IIMCRFC12131354ASN1.IpForwarding; 2660 MATCHES FOR EQUALITY, ORDERING; 2661 BEHAVIOUR 2662 ipForwardingBehaviour BEHAVIOUR 2663 DEFINED AS 2664 !BEGINPARSE 2665 REFERENCE 2666 !!This attribute maps to ipForwarding with object 2667 id {ip 1} in RFC 1213.!!; 2668 DESCRIPTION 2669 !!The indication of whether this entity is acting 2670 as an IP gateway in respect to the forwarding of 2671 datagrams received by, but not addressed to, this 2672 entity. IP gateways forward datagrams. IP hosts do 2673 not (except those source-routed via the host). 2675 Note that for some managed nodes, this attribute 2676 may take on only a subset of the values possible. 2677 Accordingly, it is appropriate for an agent to 2678 return a `badValue' response if a management 2679 station attempts to change this attribute to an 2680 inappropriate value.!!; 2681 ENDPARSE!;; 2682 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 1}; 2684 ipForwardMask ATTRIBUTE 2685 DERIVED FROM {iimcIIMCIMIBTRANS}: ipAddress; 2686 BEHAVIOUR 2687 ipForwardMaskBehaviour BEHAVIOUR 2688 DEFINED AS 2689 DRAFT February, 1994 2691 !BEGINPARSE 2692 REFERENCE 2693 !!This attribute maps to ipForwardMask with object 2694 id {ipForwardEntry 2} in RFC1354.!!; 2695 DESCRIPTION 2696 !!Indicate the mask to be logical- ANDed with the 2697 destination address before being compared to the 2698 value in the ipForwardDest field. For those 2699 systems that do not support arbitrary subnet 2700 masks, an agent constructs the value of the 2701 ipForwardMask by reference to the IP Address 2702 Class. 2704 Any assignment (implicit or otherwise) of an 2705 instance of this attribute to a value x must be 2706 rejected if the bitwise logical-AND of x with the 2707 value of the corresponding instance of the 2708 ipForwardDest attribute is not equal to 2709 ipForwardDest.!!; 2710 ENDPARSE!;; 2711 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 2}; 2713 ipForwardNextHop ATTRIBUTE 2714 DERIVED FROM {iimcIIMCIMIBTRANS}: ipAddress; 2715 BEHAVIOUR 2716 ipForwardNextHopBehaviour BEHAVIOUR 2717 DEFINED AS 2718 !BEGINPARSE 2719 REFERENCE 2720 !!This attribute maps to ipForwardNextHop with 2721 object id {ipForwardEntry 4} in RFC1354.!!; 2722 DESCRIPTION 2723 !!On remote routes, the address of the next system 2724 en route; Otherwise, 0.0.0.0.!!; 2725 ENDPARSE!;; 2726 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 4}; 2728 ipForwardNextHopAS ATTRIBUTE 2729 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2730 MATCHES FOR EQUALITY, ORDERING; 2731 BEHAVIOUR 2732 ipForwardNextHopASBehaviour BEHAVIOUR 2733 DEFINED AS 2734 !BEGINPARSE 2735 REFERENCE 2736 !!This attribute maps to ipForwardNextHopAS with 2737 object id {ipForwardEntry 10} in RFC1354.!!; 2738 DESCRIPTION 2739 !!The Autonomous System Number of the Next Hop. 2740 When this is unknown or not relevant to the 2741 protocol indicated by ipForwardProto, zero.!!; 2742 ENDPARSE!;; 2743 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 10}; 2744 DRAFT February, 1994 2746 ipForwardNumber ATTRIBUTE 2747 DERIVED FROM {iimcIIMCIMIBTRANS}: gauge32; 2748 BEHAVIOUR 2749 ipForwardNumberBehaviour BEHAVIOUR 2750 DEFINED AS 2751 !BEGINPARSE 2752 REFERENCE 2753 !!This attribute maps to ipForwardNumber with 2754 object id {ipForward 1} in RFC1354.!!; 2755 DESCRIPTION 2756 !!The number of current ipForward entries that are 2757 not invalid.!!; 2758 ENDPARSE!;; 2759 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 1}; 2761 ipForwardMetric1 ATTRIBUTE 2762 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2763 MATCHES FOR EQUALITY, ORDERING; 2764 BEHAVIOUR 2765 ipForwardMetric1Behaviour BEHAVIOUR 2766 DEFINED AS 2767 !BEGINPARSE 2768 REFERENCE 2769 !!This attribute maps to ipForwardMetric1 with 2770 object id {ipForwardEntry 11} in RFC1354.!!; 2771 DESCRIPTION 2772 !!The primary routing metric for this route. 2773 The semantics of this metric are determined by the 2774 routing-protocol specified in the route's 2775 ipForwardProto value. If this metric is not used, 2776 its value should be set to -1.!!; 2777 ENDPARSE!;; 2778 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 11}; 2780 ipForwardMetric2 ATTRIBUTE 2781 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2782 MATCHES FOR EQUALITY, ORDERING; 2783 BEHAVIOUR 2784 ipForwardMetric2Behaviour BEHAVIOUR 2785 DEFINED AS 2786 !BEGINPARSE 2787 REFERENCE 2788 !!This attribute maps to ipForwardMetric2 with 2789 object id {ipForwardEntry 12} in RFC1354.!!; 2790 DESCRIPTION 2791 !!An alternate routing metric for this route. 2792 The semantics of this metric are determined by 2793 the routing-protocol specified in the route's 2794 ipForwardProto value. If this metric is not used, 2795 its value should be set to -1.!!; 2796 ENDPARSE!;; 2797 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 12}; 2799 ipForwardMetric3 ATTRIBUTE 2800 DRAFT February, 1994 2802 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2803 MATCHES FOR EQUALITY, ORDERING; 2804 BEHAVIOUR 2805 ipForwardMetric3Behaviour BEHAVIOUR 2806 DEFINED AS 2807 !BEGINPARSE 2808 REFERENCE 2809 !!This attribute maps to ipForwardMetric3 with 2810 object id {ipForwardEntry 13} in RFC1354.!!; 2811 DESCRIPTION 2812 !!An alternate routing metric for this route. The 2813 semantics of this metric are determined by the 2814 routing-protocol specified in the route's 2815 ipForwardProto value. If this metric is not used, 2816 its value should be set to -1.!!; 2817 ENDPARSE!;; 2818 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 13}; 2820 ipForwardMetric4 ATTRIBUTE 2821 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2822 MATCHES FOR EQUALITY, ORDERING; 2823 BEHAVIOUR 2824 ipForwardMetric4Behaviour BEHAVIOUR 2825 DEFINED AS 2826 !BEGINPARSE 2827 REFERENCE 2828 !!This attribute maps to ipForwardMetric4 with 2829 object id {ipForwardEntry 14} in RFC1354.!!; 2830 DESCRIPTION 2831 !!An alternate routing metric for this route. The 2832 semantics of this metric are determined by the 2833 routing-protocol specified in the route's 2834 ipForwardProto value. If this metric is not used, 2835 its value should be set to -1.!!; 2836 ENDPARSE!;; 2837 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 14}; 2839 ipForwardMetric5 ATTRIBUTE 2840 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2841 MATCHES FOR EQUALITY, ORDERING; 2842 BEHAVIOUR 2843 ipForwardMetric5Behaviour BEHAVIOUR 2844 DEFINED AS 2845 !BEGINPARSE 2846 REFERENCE 2847 !!This attribute maps to ipForwardMetric5 with 2848 object id {ipForwardEntry 15} in RFC1354.!!; 2849 DESCRIPTION 2850 !!An alternate routing metric for this route. The 2851 semantics of this metric are determined by the 2852 routing-protocol specified in the route's 2853 ipForwardProto value. If this metric is not used, 2854 its value should be set to -1.!!; 2855 ENDPARSE!;; 2856 DRAFT February, 1994 2858 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 15}; 2860 ipForwardPolicy ATTRIBUTE 2861 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 2862 MATCHES FOR EQUALITY, ORDERING; 2863 BEHAVIOUR 2864 ipForwardPolicyBehaviour BEHAVIOUR 2865 DEFINED AS 2866 !BEGINPARSE 2867 REFERENCE 2868 !!This attribute maps to ipForwardPolicy with 2869 object id {ipForwardEntry 3} in RFC1354.!!; 2870 DESCRIPTION 2871 !!The general set of conditions that would cause 2872 the selection of one multipath route (set of next 2873 hops for a given destination) is referred to as 2874 'policy'. 2876 Unless the mechanism indicated by ipForwardProto 2877 specifies otherwise, the policy specifier is the 2878 IP TOS Field. The encoding of IP TOS is as 2879 specified by the following convention. Zero 2880 indicates the default path if no more specific 2881 policy applies. 2883 IP TOS IP TOS 2884 Field Policy Field Policy 2885 Contents Code Contents Code 2886 0 0 0 0 ==> 0 0 0 0 1 ==> 2 2887 0 0 1 0 ==> 4 0 0 1 1 ==> 6 2888 0 1 0 0 ==> 8 0 1 0 1 ==> 10 2889 0 1 1 0 ==> 12 0 1 1 1 ==> 14 2890 1 0 0 0 ==> 16 1 0 0 1 ==> 18 2891 1 0 1 0 ==> 20 1 0 1 1 ==> 22 2892 1 1 0 0 ==> 24 1 1 0 1 ==> 26 2893 1 1 1 0 ==> 28 1 1 1 1 ==> 30 2895 Protocols defining 'policy' otherwise must either 2896 define a set of values which are valid for this 2897 attribute or must implement an integer-instanced 2898 policy table for which this attribute's value acts 2899 as an index.!!; 2900 ENDPARSE!;; 2901 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 3}; 2903 ipForwardProto ATTRIBUTE 2904 WITH ATTRIBUTE SYNTAX 2905 IIMCRFC12131354ASN1.IpForwardProto; 2906 MATCHES FOR EQUALITY, ORDERING; 2907 BEHAVIOUR 2908 ipForwardProtoBehaviour BEHAVIOUR 2909 DEFINED AS 2910 !BEGINPARSE 2911 REFERENCE 2912 DRAFT February, 1994 2914 !!This attribute maps to ipForwardProto with 2915 object id {ipForwardEntry 7} in RFC1354.!!; 2916 DESCRIPTION 2917 !!The routing mechanism via which this route was 2918 learned. Inclusion of values for gateway routing 2919 protocols is not intended to imply that hosts 2920 should support those protocols.!!; 2921 ENDPARSE!;; 2922 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 7}; 2924 ipForwardType ATTRIBUTE 2925 WITH ATTRIBUTE SYNTAX 2926 IIMCRFC12131354ASN1.IpForwardType; 2927 MATCHES FOR EQUALITY, ORDERING; 2928 BEHAVIOUR 2929 ipForwardTypeBehaviour BEHAVIOUR 2930 DEFINED AS 2931 !BEGINPARSE 2932 REFERENCE 2933 !!This attribute maps to ipForwardType with object 2934 id {ipForwardEntry 6} in RFC1354.!!; 2935 DESCRIPTION 2936 !!The type of route. Note that local(3) refers 2937 to a route for which the next hop is the final 2938 destination; remote(4) refers to a route for which 2939 the next hop is not the final destination. 2941 Setting this attribute to the value invalid(2) has 2942 the effect of invalidating the corresponding 2943 ipForwardEntry. That is, it effectively 2944 disassociates the destination identified with said 2945 entry from the route identified with said entry. 2946 It is an implementation-specific matter as to 2947 whether the agent removes an invalidated entry 2948 from the table. Accordingly, management stations 2949 must be prepared to receive tabular information 2950 from agents that corresponds to entries not 2951 currently in use. Proper interpretation of such 2952 entries requires examining the relevant 2953 ipForwardType attribute.!!; 2954 ENDPARSE!;; 2955 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 24 2 1 6}; 2957 ipForwDatagrams ATTRIBUTE 2958 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2959 BEHAVIOUR 2960 ipForwDatagramsBehaviour BEHAVIOUR 2961 DEFINED AS 2962 !BEGINPARSE 2963 REFERENCE 2964 !!This attribute maps to ipForwDatagrams with 2965 object id {ip 6} in RFC1213.!!; 2966 DESCRIPTION 2967 DRAFT February, 1994 2969 !!The number of input datagrams for which this 2970 entity was not their final IP destination, as a 2971 result of which an attempt was made to find a 2972 route to forward them to that final destination. 2973 In entities which do not act as IP Gateways, this 2974 counter will include only those packets which were 2975 Source-Routed via this entity, and the Source- 2976 Route option processing was successful.!!; 2977 ENDPARSE!;; 2978 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 6}; 2980 ipFragCreates ATTRIBUTE 2981 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2982 BEHAVIOUR 2983 ipFragCreatesBehaviour BEHAVIOUR 2984 DEFINED AS 2985 !BEGINPARSE 2986 REFERENCE 2987 !!This attribute maps to ipFragCreates with object 2988 id {ip 19} in RFC1213.!!; 2989 DESCRIPTION 2990 !!The number of IP datagram fragments that have 2991 been generated as a result of fragmentation at 2992 this entity.!!; 2993 ENDPARSE!;; 2994 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 19}; 2996 ipFragFails ATTRIBUTE 2997 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 2998 BEHAVIOUR 2999 ipFragFailsBehaviour BEHAVIOUR 3000 DEFINED AS 3001 !BEGINPARSE 3002 REFERENCE 3003 !!This attribute maps to ipFragFails with object 3004 id {ip 18} in RFC1213.!!; 3005 DESCRIPTION 3006 !!The number of IP datagrams that have been 3007 discarded because they needed to be fragmented at 3008 this entity but could not be, e.g., because their 3009 Don't Fragment flag was set.!!; 3010 ENDPARSE!;; 3011 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 18}; 3013 ipFragOKs ATTRIBUTE 3014 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3015 BEHAVIOUR 3016 ipFragOKsBehaviour BEHAVIOUR 3017 DEFINED AS 3018 !BEGINPARSE 3019 REFERENCE 3020 !!This attribute maps to ipFragOKs with object id 3021 {ip 17} in RFC1213.!!; 3022 DRAFT February, 1994 3024 DESCRIPTION 3025 !!The number of IP datagrams that have been 3026 successfully fragmented at this entity.!!; 3027 ENDPARSE!;; 3028 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 17}; 3030 ipId ATTRIBUTE 3031 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.IpIdValue; 3032 MATCHES FOR EQUALITY; 3033 BEHAVIOUR 3034 ipIdBehaviour BEHAVIOUR 3035 DEFINED AS 3036 !The naming attribute for object class ip.!;; 3037 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 4}; 3039 ipInAddrErrors ATTRIBUTE 3040 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3041 BEHAVIOUR 3042 ipInAddrErrorsBehaviour BEHAVIOUR 3043 DEFINED AS 3044 !BEGINPARSE 3045 REFERENCE 3046 !!This attribute maps to ipInAddrErrors with 3047 object id {ip 5} in RFC1213.!!; 3048 DESCRIPTION 3049 !!The number of input datagrams discarded because 3050 the IP address in their IP header's destination 3051 field was not a valid address to be received at 3052 this entity. This count includes invalid addresses 3053 (e.g., 0.0.0.0) and addresses of unsupported 3054 Classes (e.g., Class E). For entities which are 3055 not IP Gateways and therefore do not forward 3056 datagrams, this counter includes datagrams 3057 discarded because the destination address was not 3058 a local address.!!; 3059 ENDPARSE!;; 3060 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 5}; 3062 ipInDelivers ATTRIBUTE 3063 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3064 BEHAVIOUR 3065 ipInDeliversBehaviour BEHAVIOUR 3066 DEFINED AS 3067 !BEGINPARSE 3068 REFERENCE 3069 !!This attribute maps to ipInDelivers with object 3070 id {ip 9} in RFC1213.!!; 3071 DESCRIPTION 3072 !!The total number of input datagrams successfully 3073 delivered to IP user-protocols (including 3074 ICMP).!!; 3075 ENDPARSE!;; 3076 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 9}; 3077 DRAFT February, 1994 3079 ipInDiscards ATTRIBUTE 3080 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3081 BEHAVIOUR 3082 ipInDiscardsBehaviour BEHAVIOUR 3083 DEFINED AS 3084 !BEGINPARSE 3085 REFERENCE 3086 !!This attribute maps to ipInDiscards with object 3087 id {ip 8} in RFC1213.!!; 3088 DESCRIPTION 3089 !!The number of input IP datagrams for which no 3090 problems were encountered to prevent their 3091 continued processing, but which were discarded 3092 (e.g., for lack of buffer space). Note that this 3093 counter does not include any datagrams discarded 3094 while awaiting re-assembly.!!; 3095 ENDPARSE!;; 3096 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 8}; 3098 ipInHdrErrors ATTRIBUTE 3099 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3100 BEHAVIOUR 3101 ipInHdrErrorsBehaviour BEHAVIOUR 3102 DEFINED AS 3103 !BEGINPARSE 3104 REFERENCE 3105 !!This attribute maps to ipInHdrErrors with object 3106 id {ip 4} in RFC1213.!!; 3107 DESCRIPTION 3108 !!The number of input datagrams discarded due to 3109 errors in their IP headers, including bad 3110 checksums, version number mismatch, other format 3111 errors, time-to-live exceeded, errors discovered 3112 in processing their IP options, etc.!!; 3113 ENDPARSE!;; 3114 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 4}; 3116 ipInReceives ATTRIBUTE 3117 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3118 BEHAVIOUR 3119 ipInReceivesBehaviour BEHAVIOUR 3120 DEFINED AS 3121 !BEGINPARSE 3122 REFERENCE 3123 !!This attribute maps to ipInReceives with object 3124 id {ip 3} in RFC1213.!!; 3125 DESCRIPTION 3126 !!The total number of input datagrams received 3127 from interfaces, including those received in 3128 error.!!; 3129 ENDPARSE!;; 3130 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 3}; 3132 ipInUnknownProtos ATTRIBUTE 3133 DRAFT February, 1994 3135 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3136 BEHAVIOUR 3137 ipInUnknownProtosBehaviour BEHAVIOUR 3138 DEFINED AS 3139 !BEGINPARSE 3140 REFERENCE 3141 !!This attribute maps to ipInUnknownProtos with 3142 object id {ip 7} in RFC1213.!!; 3143 DESCRIPTION 3144 !!The number of locally-addressed datagrams 3145 received successfully but discarded because of an 3146 unknown or unsupported protocol.!!; 3147 ENDPARSE!;; 3148 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 7}; 3150 ipNetToMediaEntryId ATTRIBUTE 3151 WITH ATTRIBUTE SYNTAX 3152 IIMCRFC12131354ASN1.IpNetToMediaEntryIdValue; 3153 MATCHES FOR EQUALITY; 3154 BEHAVIOUR 3155 ipNetToMediaEntryIdBehaviour BEHAVIOUR 3156 DEFINED AS 3157 !The naming attribute for object class 3158 ipNetToMediaEntry.!;; 3159 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 4 22 1}; 3161 ipNetToMediaIfIndex ATTRIBUTE 3162 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 3163 MATCHES FOR EQUALITY, ORDERING; 3164 BEHAVIOUR 3165 ipNetToMediaIfIndexBehaviour BEHAVIOUR 3166 DEFINED AS 3167 !BEGINPARSE 3168 REFERENCE 3169 !!This attribute maps to ipNetToMediaIfIndex with 3170 object id {ipNetToMediaEntry 1} in RFC1213.!!; 3171 DESCRIPTION 3172 !!The interface on which this entry's equivalence 3173 is effective. The interface identified by a 3174 particular value of this index is the same 3175 interface as identified by the same value of 3176 ifIndex.!!; 3177 ENDPARSE!;; 3178 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 22 1 1}; 3180 ipNetToMediaNetAddress ATTRIBUTE 3181 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 3182 BEHAVIOUR 3183 ipNetToMediaNetAddressBehaviour BEHAVIOUR 3184 DEFINED AS 3185 !BEGINPARSE 3186 REFERENCE 3187 DRAFT February, 1994 3189 !!This attribute maps to ipNetToMediaNetAddress 3190 with object id {ipNetToMediaEntry 3} in 3191 RFC1213.!!; 3192 DESCRIPTION 3193 !!The IpAddress corresponding to the media- 3194 dependent `physical' address.!!; 3195 ENDPARSE!;; 3196 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 22 1 3}; 3198 ipNetToMediaPhysAddress ATTRIBUTE 3199 DERIVED FROM {iimcIIMCIMIBTRANS}:physAddress; 3200 BEHAVIOUR 3201 ipNetToMediaPhysAddressBehaviour BEHAVIOUR 3202 DEFINED AS 3203 !BEGINPARSE 3204 REFERENCE 3205 !!This attribute maps to ipNetToMediaPhysAddress 3206 with object id {ipNetToMediaEntry 2} in 3207 RFC1213.!!; 3208 DESCRIPTION 3209 !!The media-dependent `physical' address.!!; 3210 ENDPARSE!;; 3211 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 22 1 2}; 3213 ipNetToMediaType ATTRIBUTE 3214 WITH ATTRIBUTE SYNTAX 3215 IIMCRFC12131354ASN1.IpNetToMediaType; 3216 MATCHES FOR EQUALITY, ORDERING; 3217 BEHAVIOUR 3218 ipNetToMediaTypeBehaviour BEHAVIOUR 3219 DEFINED AS 3220 !BEGINPARSE 3221 REFERENCE 3222 !!This attribute maps to ipNetToMediaType with 3223 object id {ipNetToMediaEntry 4} in RFC1213.!!; 3224 DESCRIPTION 3225 !!The type of mapping. Setting this attribute to 3226 the value invalid(2) has the effect of 3227 invalidating the corresponding entry in the 3228 ipNetToMediaTable. That is, it effectively 3229 disassociates the interface identified with said 3230 entry from the mapping identified with said entry. 3231 It is an implementation-specific matter as to 3232 whether the agent removes an invalidated entry 3233 from the table. Accordingly, management stations 3234 must be prepared to receive tabular information 3235 from agents that corresponds to entries not 3236 currently in use. Proper interpretation of such 3237 entries requires examination of the relevant 3238 ipNetToMediaType attribute.!!; 3239 ENDPARSE!;; 3240 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 22 1 4}; 3242 ipOutDiscards ATTRIBUTE 3243 DRAFT February, 1994 3245 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3246 BEHAVIOUR 3247 ipOutDiscardsBehaviour BEHAVIOUR 3248 DEFINED AS 3249 !BEGINPARSE 3250 REFERENCE 3251 !!This attribute maps to ipOutDiscards with object 3252 id ip 11} in RFC1213.!!; 3253 DESCRIPTION 3254 !!The number of output IP datagrams for which no 3255 problem was encountered to prevent their 3256 transmission to their destination, but which were 3257 discarded (e.g., for lack of buffer space). Note 3258 that this counter would include datagrams counted 3259 in ipForwDatagrams if any such packets met this 3260 (discretionary) discard criterion.!!; 3261 ENDPARSE!;; 3262 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 11}; 3264 ipOutNoRoutes ATTRIBUTE 3265 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3266 BEHAVIOUR 3267 ipOutNoRoutesBehaviour BEHAVIOUR 3268 DEFINED AS 3269 !BEGINPARSE 3270 REFERENCE 3271 !!This attribute maps to ipOutNoRoutes with object 3272 id {ip 12} in RFC1213.!!; 3273 DESCRIPTION 3274 !!The number of IP datagrams discarded because no 3275 route could be found to transmit them to their 3276 destination. Note that this counter includes any 3277 packets counted in ipForwDatagrams which meet this 3278 `no-route' criterion. Note that this includes any 3279 datagrams which a host cannot route because all of 3280 its default gateways are down.!!; 3281 ENDPARSE!;; 3282 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 12}; 3284 ipOutRequests ATTRIBUTE 3285 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3286 BEHAVIOUR 3287 ipOutRequestsBehaviour BEHAVIOUR 3288 DEFINED AS 3289 !BEGINPARSE 3290 REFERENCE 3291 !!This attribute maps to ipOutRequests with object 3292 id {ip 10}.!!; 3293 DESCRIPTION 3294 !!The total number of IP datagrams which local IP 3295 user-protocols (including ICMP) supplied to IP in 3296 requests for transmission. Note that this counter 3297 does not include any datagrams counted in 3298 ipForwDatagrams.!!; 3299 DRAFT February, 1994 3301 ENDPARSE!;; 3302 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 10}; 3304 ipReasmFails ATTRIBUTE 3305 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3306 BEHAVIOUR 3307 ipReasmFailsBehaviour BEHAVIOUR 3308 DEFINED AS 3309 !BEGINPARSE 3310 REFERENCE 3311 !!This attribute maps to ipReasmFails with objects 3312 id {ip 16} in RFC1213.!!; 3313 DESCRIPTION 3314 !!The number of failures detected by the IP re- 3315 assembly algorithm (for whatever reason: timed 3316 out, errors, etc). Note that this is not 3317 necessarily a count of discarded IP fragments 3318 since some algorithms (notably the algorithm in 3319 RFC 815) can lose track of the number of fragments 3320 by combining them as they are received.!!; 3321 ENDPARSE!;; 3322 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 16}; 3324 ipReasmOKs ATTRIBUTE 3325 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3326 BEHAVIOUR 3327 ipReasmOKsBehaviour BEHAVIOUR 3328 DEFINED AS 3329 !BEGINPARSE 3330 REFERENCE 3331 !!This attribute maps to ipReasmOKs with object id 3332 {ip 15} in RFC1213.!!; 3333 DESCRIPTION 3334 !!The number of IP datagrams successfully re- 3335 assembled.!!; 3336 ENDPARSE!;; 3337 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 15}; 3339 ipReasmReqds ATTRIBUTE 3340 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3341 BEHAVIOUR 3342 ipReasmReqdsBehaviour BEHAVIOUR 3343 DEFINED AS 3344 !BEGINPARSE 3345 REFERENCE 3346 !!This attribute maps to ipReasmReqds with object 3347 id {ip 4} in RFC1213.!!; 3348 DESCRIPTION 3349 !!The number of IP fragments received which needed 3350 to be reassembled at this entity.!!; 3351 ENDPARSE!;; 3352 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 14}; 3354 ipReasmTimeout ATTRIBUTE 3355 DRAFT February, 1994 3357 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 3358 MATCHES FOR EQUALITY, ORDERING; 3359 BEHAVIOUR 3360 ipReasmTimeoutBehaviour BEHAVIOUR 3361 DEFINED AS 3362 !BEGINPARSE 3363 REFERENCE 3364 !!This attribute maps to ipReasmTimeout with 3365 object id {ip 13} in RFC1213.!!; 3366 DESCRIPTION 3367 !!The maximum number of seconds which received 3368 fragments are held while they are awaiting 3369 reassembly at this entity.!!; 3370 ENDPARSE!;; 3371 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 13}; 3373 ipRouteAge ATTRIBUTE 3374 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 3375 MATCHES FOR EQUALITY, ORDERING; 3376 BEHAVIOUR 3377 ipRouteAgeBehaviour BEHAVIOUR 3378 DEFINED AS 3379 !BEGINPARSE 3380 REFERENCE 3381 !!This attribute maps to ipRouteAge with object id 3382 {ipRouteEntry 10} in RFC1213.!!; 3383 DESCRIPTION 3384 !!The number of seconds since this route was last 3385 updated or otherwise determined to be correct. 3386 Note that no semantics of `too old' can be implied 3387 except through knowledge of the routing protocol 3388 by which the route was learned.!!; 3389 ENDPARSE!;; 3390 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 10}; 3392 ipRouteDest ATTRIBUTE 3393 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 3394 BEHAVIOUR 3395 ipRouteDestBehaviour BEHAVIOUR 3396 DEFINED AS 3397 !BEGINPARSE 3398 REFERENCE 3399 !!This attribute maps to ipRouteDest with object 3400 id {ipRouteEntry 1} in RFC1213.!!; 3401 DESCRIPTION 3402 !!The destination IP address of this route. An 3403 entry with a value of 0.0.0.0 is considered a 3404 default route. Multiple routes to a single 3405 destination can appear in the table, but access to 3406 such multiple entries is dependent on the table- 3407 access mechanisms defined by the network 3408 management protocol in use.!!; 3409 ENDPARSE!;; 3410 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 1}; 3411 DRAFT February, 1994 3413 ipRouteEntryId ATTRIBUTE 3414 WITH ATTRIBUTE SYNTAX 3415 IIMCRFC12131354ASN1.IpRouteEntryIdValue; 3416 MATCHES FOR EQUALITY; 3417 BEHAVIOUR 3418 ipRouteEntryIdBehaviour BEHAVIOUR 3419 DEFINED AS !The naming attribute for object class 3420 ipRouteEntry.!;; 3421 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 4 21 1}; 3423 ipRouteIfIndex ATTRIBUTE 3424 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 3425 MATCHES FOR EQUALITY, ORDERING; 3426 BEHAVIOUR 3427 ipRouteIfIndexBehaviour BEHAVIOUR 3428 DEFINED AS 3429 !BEGINPARSE 3430 REFERENCE 3431 !!This attribute maps to ipRouteIfIndex with 3432 object id {ipRouteEntry 2} in RFC1213.!!; 3433 DESCRIPTION 3434 !!The index value which uniquely identifies the 3435 local interface through which the next hop of this 3436 route should be reached. The interface identified 3437 by a particular value of this index is the same 3438 interface as identified by the same value of 3439 ifIndex.!!; 3440 ENDPARSE!;; 3441 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 2}; 3443 ipRouteInfo ATTRIBUTE 3444 WITH ATTRIBUTE SYNTAX 3445 IIMCRFC12131354ASN1.ObjectIdentifier; 3446 MATCHES FOR EQUALITY, ORDERING; 3447 BEHAVIOUR 3448 ipRouteInfoBehaviour BEHAVIOUR 3449 DEFINED AS 3450 !BEGINPARSE 3451 REFERENCE 3452 !!This attribute maps to ipRouteInfo with object 3453 id {ipRouteEntry 13} in RFC1213.!!; 3454 DESCRIPTION 3455 !!A reference to MIB definitions specific to the 3456 particular routing protocol which is responsible 3457 for this route, as determined by the value 3458 specified in the route's ipRouteProto value. If 3459 this information is not present, its value should 3460 be set to the OBJECT IDENTIFIER { 0 0 }, which is 3461 a syntactically valid object identifier, and any 3462 conformant implementation of ASN.1 and BER must be 3463 able to generate and recognize this value.!!; 3464 ENDPARSE!;; 3465 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 13}; 3466 DRAFT February, 1994 3468 ipRouteMask ATTRIBUTE 3469 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 3470 BEHAVIOUR 3471 ipRouteMaskBehaviour BEHAVIOUR 3472 DEFINED AS 3473 !BEGINPARSE 3474 REFERENCE 3475 !!This attribute maps to ipRouteMask with object 3476 id {ipRouteEntry 11} in RFC1213.!!; 3477 DESCRIPTION 3478 !!Indicate the mask to be logical-ANDed with the 3479 destination address before being compared to the 3480 value in the ipRouteDest field. For those systems 3481 that do not support arbitrary subnet masks, an 3482 agent constructs the value of the ipRouteMask by 3483 determining whether the value of the correspondent 3484 ipRouteDest field belong to a class-A, B, or C 3485 network, and then using one of: 3487 mask network 3488 255.0.0.0 class-A 3489 255.255.0.0 class-B 3490 255.255.255.0 class-C 3492 If the value of the ipRouteDest is 0.0.0.0 (a 3493 default route), then the mask value is also 3494 0.0.0.0. It should be noted that all IP routing 3495 subsystems implicitly use this mechanism.!!; 3496 ENDPARSE!;; 3497 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 11}; 3499 ipRouteMetric1 ATTRIBUTE 3500 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 3501 MATCHES FOR EQUALITY, ORDERING; 3502 BEHAVIOUR 3503 ipRouteMetric1Behaviour BEHAVIOUR 3504 DEFINED AS 3505 !BEGINPARSE 3506 REFERENCE 3507 !!This attribute maps to ipRouteMetric1 with 3508 object id {ipRouteEntry 3} in RFC1213.!!; 3509 DESCRIPTION 3510 !!The primary routing metric for this route. The 3511 semantics of this metric are determined by the 3512 routing-protocol specified in the route's 3513 ipRouteProto value. If this metric is not used, 3514 its value should be set to -1.!!; 3515 ENDPARSE!;; 3516 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 3}; 3518 ipRouteMetric2 ATTRIBUTE 3519 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 3520 MATCHES FOR EQUALITY, ORDERING; 3521 DRAFT February, 1994 3523 BEHAVIOUR 3524 ipRouteMetric2Behaviour BEHAVIOUR 3525 DEFINED AS 3526 !BEGINPARSE 3527 REFERENCE 3528 !!This attribute maps to ipRouteMetric with object 3529 id {ipRouteEntry 4} in RFC1213.!!; 3530 DESCRIPTION 3531 !!An alternate routing metric for this route. The 3532 semantics of this metric are determined by the 3533 routing-protocol specified in the route's 3534 ipRouteProto value. If this metric is not used, 3535 its value should be set to -1.!!; 3536 ENDPARSE!;; 3537 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 4}; 3539 ipRouteMetric3 ATTRIBUTE 3540 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 3541 MATCHES FOR EQUALITY, ORDERING; 3542 BEHAVIOUR 3543 ipRouteMetric3Behaviour BEHAVIOUR 3544 DEFINED AS 3545 !BEGINPARSE 3546 REFERENCE 3547 !!This attribute maps to ipRouteMetric3 with 3548 object id {ipRouteEntry 5} in RFC1213.!!; 3549 DESCRIPTION 3550 !!An alternate routing metric for this route. The 3551 semantics of this metric are determined by the 3552 routing-protocol specified in the route's 3553 ipRouteProto value. If this metric is not used, 3554 its value should be set to -1.!!; 3555 ENDPARSE!;; 3556 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 5}; 3558 ipRouteMetric4 ATTRIBUTE 3559 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 3560 MATCHES FOR EQUALITY, ORDERING; 3561 BEHAVIOUR 3562 ipRouteMetric4Behaviour BEHAVIOUR 3563 DEFINED AS 3564 !BEGINPARSE 3565 REFERENCE 3566 !!This attribute maps to ipRouteMetric4 with 3567 object id {ipRouteEntry 6} in RFC1213.!!; 3568 DESCRIPTION 3569 !!An alternate routing metric for this route. The 3570 semantics of this metric are determined by the 3571 routing-protocol specified in the route's 3572 ipRouteProto value. If this metric is not used, 3573 its value should be set to -1.!!; 3574 ENDPARSE!;; 3575 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 6}; 3576 DRAFT February, 1994 3578 ipRouteMetric5 ATTRIBUTE 3579 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 3580 MATCHES FOR EQUALITY, ORDERING; 3581 BEHAVIOUR 3582 ipRouteMetric5Behaviour BEHAVIOUR 3583 DEFINED AS 3584 !BEGINPARSE 3585 REFERENCE 3586 !!This attribute maps to ipRouteMetric5 with 3587 object id {ipRouteEntry 12} in RFC1213.!!; 3588 DESCRIPTION 3589 !!An alternate routing metric for this route. The 3590 semantics of this metric are determined by the 3591 routing-protocol specified in the route's 3592 ipRouteProto value. If this metric is not used, 3593 its value should be set to -1.!!; 3594 ENDPARSE!;; 3595 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 12}; 3597 ipRouteNextHop ATTRIBUTE 3598 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 3599 BEHAVIOUR 3600 ipRouteNextHopBehaviour BEHAVIOUR 3601 DEFINED AS 3602 !BEGINPARSE 3603 REFERENCE 3604 !!This attribute maps to ipRouteNextHop with 3605 object id {ipRouteEntry 7} in RFC1213.!!; 3606 DESCRIPTION 3607 !!The IP address of the next hop of this route. 3608 (In the case of a route bound to an interface 3609 which is realized via a broadcast media, the value 3610 of this field is the agent's IP address on that 3611 interface.)!!; 3612 ENDPARSE!;; 3613 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 7}; 3615 ipRouteProto ATTRIBUTE 3616 WITH ATTRIBUTE SYNTAX 3617 IIMCRFC12131354ASN1.IpRouteProto; 3618 MATCHES FOR EQUALITY, ORDERING; 3619 BEHAVIOUR 3620 ipRouteProtoBehaviour BEHAVIOUR 3621 DEFINED AS 3622 !BEGINPARSE 3623 REFERENCE 3624 !!This attribute maps to ipRouteProto with object 3625 id {ipRouteEntry 9} in RFC1213.!!; 3626 DESCRIPTION 3627 !!The routing mechanism via which this route was 3628 learned. Inclusion of values for gateway routing 3629 protocols is not intended to imply that hosts 3630 should support those protocols.!!; 3631 ENDPARSE!;; 3632 DRAFT February, 1994 3634 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 9}; 3636 ipRouteType ATTRIBUTE 3637 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.IpRouteType; 3638 MATCHES FOR EQUALITY, ORDERING; 3639 BEHAVIOUR 3640 ipRouteTypeBehaviour BEHAVIOUR 3641 DEFINED AS 3642 !BEGINPARSE 3643 REFERENCE 3644 !!This attribute maps to ipRouteType with object 3645 id {ipRouteEntry 8} in RFC1213.!!; 3646 DESCRIPTION 3647 !!The type of route. Note that the values 3648 direct(3) and indirect(4) refer to the notion of 3649 direct and indirect routing in the IP 3650 architecture. 3652 Setting this attribute to the value invalid(2) has 3653 the effect of invalidating the corresponding 3654 ipRouteEntry. That is, it effectively 3655 disassociates the destination identified with said 3656 entry from the route identified with said entry. 3657 It is an implementation-specific matter as to 3658 whether the agent removes an invalidated entry 3659 from the table. Accordingly, management stations 3660 must be prepared to receive tabular information 3661 from agents that corresponds to entries not 3662 currently in use. Proper interpretation of such 3663 entries requires examination of the relevant 3664 ipRouteType attribute.!!; 3665 ENDPARSE!;; 3666 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 21 1 8}; 3668 ipRoutingDiscards ATTRIBUTE 3669 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3670 BEHAVIOUR 3671 ipRoutingDiscardsBehaviour BEHAVIOUR 3672 DEFINED AS 3673 !BEGINPARSE 3674 REFERENCE 3675 !!This attribute maps to ipRoutingDiscards with 3676 object id {ip 23} in RFC1213.!!; 3677 DESCRIPTION 3678 !!The number of routing entries which were chosen 3679 to be discarded even though they are valid. One 3680 possible reason for discarding such an entry could 3681 be to free-up buffer space for other routing 3682 entries.!!; 3683 ENDPARSE!;; 3684 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 4 23}; 3686 snmpEnableAuthenTraps ATTRIBUTE 3687 DRAFT February, 1994 3689 WITH ATTRIBUTE SYNTAX 3690 IIMCRFC12131354ASN1.SnmpEnableAuthenTraps; 3691 MATCHES FOR EQUALITY, ORDERING; 3692 BEHAVIOUR 3693 snmpEnableAuthenTrapsBehaviour BEHAVIOUR 3694 DEFINED AS 3695 !BEGINPARSE 3696 REFERENCE 3697 !!This attribute maps to snmpEnableAuthenTraps 3698 with object id {snmp 30} in RFC1213.!!; 3699 DESCRIPTION 3700 !!Indicates whether the SNMP agent process is 3701 permitted to generate authentication-failure 3702 traps. The value of this attribute overrides any 3703 configuration information; as such, it provides a 3704 means whereby all authentication-failure traps may 3705 be disabled. 3707 Note that it is strongly recommended that this 3708 attribute be stored in non-volatile memory so that 3709 it remains constant between re-initializations of 3710 the network management system.!!; 3711 ENDPARSE!;; 3712 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 30}; 3714 snmpId ATTRIBUTE 3715 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.SnmpIdValue; 3716 MATCHES FOR EQUALITY; 3717 BEHAVIOUR 3718 snmpIdBehaviour BEHAVIOUR 3719 DEFINED AS 3720 !The naming attribute for object class snmp.!;; 3721 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 11}; 3723 snmpInASNParseErrs ATTRIBUTE 3724 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3725 BEHAVIOUR 3726 snmpInASNParseErrsBehaviour BEHAVIOUR 3727 DEFINED AS 3728 !BEGINPARSE 3729 REFERENCE 3730 !!This attribute maps to snmpInASNParseErrs with 3731 object id {snmp 6} in RFC1213.!!; 3732 DESCRIPTION 3733 !!The total number of ASN.1 or BER errors 3734 encountered by the SNMP protocol entity when 3735 decoding received SNMP Messages.!!; 3736 ENDPARSE!;; 3737 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 6}; 3739 snmpInBadCommunityNames ATTRIBUTE 3740 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3741 BEHAVIOUR 3742 snmpInBadCommunityNamesBehaviour BEHAVIOUR 3743 DRAFT February, 1994 3745 DEFINED AS 3746 !BEGINPARSE 3747 REFERENCE 3748 !!This attribute maps to snmpInBadCommunityNames 3749 with object id {snmp 4} in RFC1213.!!; 3750 DESCRIPTION 3751 !!The total number of SNMP Messages delivered to 3752 the SNMP protocol entity which used a SNMP 3753 community name not known to said entity.!!; 3754 ENDPARSE!;; 3755 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 4}; 3757 snmpInBadCommunityUses ATTRIBUTE 3758 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3759 BEHAVIOUR 3760 snmpInBadCommunityUsesBehaviour BEHAVIOUR 3761 DEFINED AS 3762 !BEGINPARSE 3763 REFERENCE 3764 !!This attribute maps to snmpInBadCommunityUses 3765 with object id {snmp 5} in RFC1213.!!; 3766 DESCRIPTION 3767 !!The total number of SNMP Messages delivered to 3768 the SNMP protocol entity which represented an SNMP 3769 operation which was not allowed by the SNMP 3770 community named in the Message.!!; 3771 ENDPARSE!;; 3772 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 5}; 3774 snmpInBadValues ATTRIBUTE 3775 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3776 BEHAVIOUR 3777 snmpInBadValuesBehaviour BEHAVIOUR 3778 DEFINED AS 3779 !BEGINPARSE 3780 REFERENCE 3781 !!This attribute maps to the snmpInBadValues with 3782 object id {snmp 10} in RFC1213.!!; 3783 DESCRIPTION 3784 !!The total number of SNMP PDUs which were 3785 delivered to the SNMP protocol entity and for 3786 which the value of the error-status field is 3787 `badValue'.!!; 3788 ENDPARSE!;; 3789 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 10}; 3791 snmpInBadVersions ATTRIBUTE 3792 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3793 BEHAVIOUR 3794 snmpInBadVersionsBehaviour BEHAVIOUR 3795 DEFINED AS 3796 !BEGINPARSE 3797 REFERENCE 3798 DRAFT February, 1994 3800 !!This attribute maps to the snmpInBadVersions 3801 with object id {snmp 3} in RFC1213.!!; 3802 DESCRIPTION 3803 !!The total number of SNMP Messages which were 3804 delivered to the SNMP protocol entity and were for 3805 an unsupported SNMP version.!!; 3806 ENDPARSE!;; 3807 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 3}; 3809 snmpInGenErrs ATTRIBUTE 3810 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3811 BEHAVIOUR 3812 snmpInGenErrsBehaviour BEHAVIOUR 3813 DEFINED AS 3814 !BEGINPARSE 3815 REFERENCE 3816 !!This attribute maps to the snmpInGenErrs with 3817 object id {snmp 12} in RFC1213.!!; 3818 DESCRIPTION 3819 !!The total number of SNMP PDUs which were 3820 delivered to the SNMP protocol entity and for 3821 which the value of the error-status field is 3822 `genErr'.!!; 3823 ENDPARSE!;; 3824 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 12}; 3826 snmpInGetNexts ATTRIBUTE 3827 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3828 BEHAVIOUR 3829 snmpInGetNextsBehaviour BEHAVIOUR 3830 DEFINED AS 3831 !BEGINPARSE 3832 REFERENCE 3833 !!This attribute maps to the snmpInGetNexts with 3834 object id {snmp 16} in RFC1213.!!; 3835 DESCRIPTION 3836 !!The total number of SNMP Get-Next PDUs which 3837 have been accepted and processed by the SNMP 3838 protocol entity.!!; 3839 ENDPARSE!;; 3840 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 16}; 3842 snmpInGetRequests ATTRIBUTE 3843 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3844 BEHAVIOUR 3845 snmpInGetRequestsBehaviour BEHAVIOUR 3846 DEFINED AS 3847 !BEGINPARSE 3848 REFERENCE 3849 !!This attribute maps to the snmpInGetRequests 3850 with object id {snmp 15} in RFC1213.!!; 3851 DESCRIPTION 3852 DRAFT February, 1994 3854 !!The total number of SNMP Get-Request PDUs which 3855 have been accepted and processed by the SNMP 3856 protocol entity.!!; 3857 ENDPARSE!;; 3858 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 15}; 3860 snmpInGetResponses ATTRIBUTE 3861 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3862 BEHAVIOUR 3863 snmpInGetResponsesBehaviour BEHAVIOUR 3864 DEFINED AS 3865 !BEGINPARSE 3866 REFERENCE 3867 !!This attribute maps to the snmpInGetResponses 3868 with object id {snmp 18} in RFC1213.!!; 3869 DESCRIPTION 3870 !!The total number of SNMP Get-Response PDUs which 3871 have been accepted and processed by the SNMP 3872 protocol entity.!!; 3873 ENDPARSE!;; 3874 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 18}; 3876 snmpInNoSuchNames ATTRIBUTE 3877 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3878 BEHAVIOUR 3879 snmpInNoSuchNamesBehaviour BEHAVIOUR 3880 DEFINED AS 3881 !BEGINPARSE 3882 REFERENCE 3883 !!This attribute maps to the snmpInNoSuchNames 3884 with object id {snmp 9} in RFC1213.!!; 3885 DESCRIPTION 3886 !!The total number of SNMP PDUs which were 3887 delivered to the SNMP protocol entity and for 3888 which the value of the error-status field is 3889 `noSuchName'.!!; 3890 ENDPARSE!;; 3891 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 9}; 3893 snmpInPkts ATTRIBUTE 3894 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3895 BEHAVIOUR 3896 snmpInPktsBehaviour BEHAVIOUR 3897 DEFINED AS 3898 !BEGINPARSE 3899 REFERENCE 3900 !!This attribute maps to snmpInPkts with object id 3901 {snmp 1} in RFC1213.!!; 3902 DESCRIPTION 3903 !!The total number of Messages delivered to the 3904 SNMP entity from the transport service.!!; 3905 ENDPARSE!;; 3906 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 1}; 3907 DRAFT February, 1994 3909 snmpInReadOnlys ATTRIBUTE 3910 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3911 BEHAVIOUR 3912 snmpInReadOnlysBehaviour BEHAVIOUR 3913 DEFINED AS 3914 !BEGINPARSE 3915 REFERENCE 3916 !!This attribute maps to the snmpInReadOnlys with 3917 object id {snmp 11} in RFC1213.!!; 3918 DESCRIPTION 3919 !!The total number valid SNMP PDUs which were 3920 delivered to the SNMP protocol entity and for 3921 which the value of the error-status field is 3922 `readOnly'. It should be noted that it is a 3923 protocol error to generate an SNMP PDU which 3924 contains the value `readOnly' in the error-status 3925 field, as such this attribute is provided as a 3926 means of detecting incorrect implementations of 3927 the SNMP.!!; 3928 ENDPARSE!;; 3929 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 11}; 3931 snmpInSetRequests ATTRIBUTE 3932 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3933 BEHAVIOUR 3934 snmpInSetRequestsBehaviour BEHAVIOUR 3935 DEFINED AS 3936 !BEGINPARSE 3937 REFERENCE 3938 !!This attribute maps to snmpInSetRequests with 3939 object id {snmp 17} in RFC1213.!!; 3940 DESCRIPTION 3941 !!The total number of SNMP Set-Request PDUs which 3942 have been accepted and processed by the SNMP 3943 protocol entity.!!; 3944 ENDPARSE!;; 3945 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 17}; 3947 snmpInTooBigs ATTRIBUTE 3948 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3949 BEHAVIOUR 3950 snmpInTooBigsBehaviour BEHAVIOUR 3951 DEFINED AS 3952 !BEGINPARSE 3953 REFERENCE 3954 !!This attribute maps to snmpInTooBigs with object 3955 id {snmp 8} in RFC1213.!!; 3956 DESCRIPTION 3957 !!The total number of SNMP PDUs which were 3958 delivered to the SNMP protocol entity and for 3959 which the value of the error-status field is 3960 `tooBig'.!!; 3961 ENDPARSE!;; 3962 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 8}; 3963 DRAFT February, 1994 3965 snmpInTotalReqVars ATTRIBUTE 3966 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3967 BEHAVIOUR 3968 snmpInTotalReqVarsBehaviour BEHAVIOUR 3969 DEFINED AS 3970 !BEGINPARSE 3971 REFERENCE 3972 !!This attribute maps to snmpInTotalReqVars with 3973 object id {snmp 13} in RFC1213.!!; 3974 DESCRIPTION 3975 !!The total number of MIB objects which have been 3976 retrieved successfully by the SNMP protocol entity 3977 as the result of receiving valid SNMP Get-Request 3978 and Get-Next PDUs.!!; 3979 ENDPARSE!;; 3980 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 13}; 3982 snmpInTotalSetVars ATTRIBUTE 3983 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 3984 BEHAVIOUR 3985 snmpInTotalSetVarsBehaviour BEHAVIOUR 3986 DEFINED AS 3987 !BEGINPARSE 3988 REFERENCE 3989 !!This attribute maps to snmpInTotalSetVars with 3990 object id {snmp 14} in RFC1213.!!; 3991 DESCRIPTION 3992 !!The total number of MIB objects which have been 3993 altered successfully by the SNMP protocol entity 3994 as the result of receiving valid SNMP Set-Request 3995 PDUs.!!; 3996 ENDPARSE!;; 3997 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 14}; 3999 snmpInTraps ATTRIBUTE 4000 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4001 BEHAVIOUR 4002 snmpInTrapsBehaviour BEHAVIOUR 4003 DEFINED AS 4004 !BEGINPARSE 4005 REFERENCE 4006 !!This attribute maps to snmpInTraps with object 4007 id {snmp 19}.!!; 4008 DESCRIPTION 4009 !!The total number of SNMP Trap PDUs which have 4010 been accepted and processed by the SNMP protocol 4011 entity.!!; 4012 ENDPARSE!;; 4013 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 19}; 4015 snmpOutBadValues ATTRIBUTE 4016 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4017 BEHAVIOUR 4018 DRAFT February, 1994 4020 snmpOutBadValuesBehaviour BEHAVIOUR 4021 DEFINED AS 4022 !BEGINPARSE 4023 REFERENCE 4024 !!This attribute maps to snmpOutBadValues with 4025 object id {snmp 22} in RFC1213.!!; 4026 DESCRIPTION 4027 !!The total number of SNMP PDUs which were 4028 generated by the SNMP protocol entity and for 4029 which the value of the error-status field is 4030 `badValue'.!!; 4031 ENDPARSE!;; 4032 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 22}; 4034 snmpOutGenErrs ATTRIBUTE 4035 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4036 BEHAVIOUR 4037 snmpOutGenErrsBehaviour BEHAVIOUR 4038 DEFINED AS 4039 !BEGINPARSE 4040 REFERENCE 4041 !!This attribute maps to snmpOutGenErrs with 4042 object id {snmp 24} in RFC1213.!!; 4043 DESCRIPTION 4044 !!The total number of SNMP PDUs which were 4045 generated by the SNMP protocol entity and for 4046 which the value of the error-status field is 4047 `genErr'.!!; 4048 ENDPARSE!;; 4049 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 24}; 4051 snmpOutGetNexts ATTRIBUTE 4052 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4053 BEHAVIOUR 4054 snmpOutGetNextsBehaviour BEHAVIOUR 4055 DEFINED AS 4056 !BEGINPARSE 4057 REFERENCE 4058 !!This attribute maps to snmpOutGetNexts with 4059 object id {snmp 26} in RFC1213.!!; 4060 DESCRIPTION 4061 !!The total number of SNMP Get-Next PDUs which 4062 have been generated by the SNMP protocol 4063 entity.!!; 4064 ENDPARSE!;; 4065 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 26}; 4067 snmpOutGetRequests ATTRIBUTE 4068 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4069 BEHAVIOUR 4070 snmpOutGetRequestsBehaviour BEHAVIOUR 4071 DEFINED AS 4072 !BEGINPARSE 4073 REFERENCE 4074 DRAFT February, 1994 4076 !!This attribute maps to snmpOutGetRequests with 4077 object id {snmp 25} in RFC1213.!!; 4078 DESCRIPTION 4079 !!The total number of SNMP Get-Request PDUs which 4080 have been generated by the SNMP protocol 4081 entity.!!; 4082 ENDPARSE!;; 4083 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 25}; 4085 snmpOutGetResponses ATTRIBUTE 4086 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4087 BEHAVIOUR 4088 snmpOutGetResponsesBehaviour BEHAVIOUR 4089 DEFINED AS 4090 !BEGINPARSE 4091 REFERENCE 4092 !!This attribute maps to snmpOutGetResponses with 4093 object id {snmp 28} in RFC1213.!!; 4094 DESCRIPTION 4095 !!The total number of SNMP Get-Response PDUs which 4096 have been generated by the SNMP protocol 4097 entity.!!; 4098 ENDPARSE!;; 4099 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 28}; 4101 snmpOutNoSuchNames ATTRIBUTE 4102 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4103 BEHAVIOUR 4104 snmpOutNoSuchNamesBehaviour BEHAVIOUR 4105 DEFINED AS 4106 !BEGINPARSE 4107 REFERENCE 4108 !!This attribute maps to snmpOutNoSuchNames with 4109 object id {snmp 21} in RFC1213.!!; 4110 DESCRIPTION 4111 !!The total number of SNMP PDUs which were 4112 generated by the SNMP protocol entity and for 4113 which the value of the error-status is 4114 `noSuchName'.!!; 4115 ENDPARSE!;; 4116 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 21}; 4118 snmpOutPkts ATTRIBUTE 4119 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4120 BEHAVIOUR 4121 snmpOutPktsBehaviour BEHAVIOUR 4122 DEFINED AS 4123 !BEGINPARSE 4124 REFERENCE 4125 !!This attribute maps to snmpOutPkts with object 4126 is {snmp 2} in RFC1213.!!; 4127 DESCRIPTION 4128 DRAFT February, 1994 4130 !!The total number of SNMP Messages which were 4131 passed from the SNMP protocol entity to the 4132 transport service.!!; 4133 ENDPARSE!;; 4134 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 2}; 4136 snmpOutSetRequests ATTRIBUTE 4137 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4138 BEHAVIOUR 4139 snmpOutSetRequestsBehaviour BEHAVIOUR 4140 DEFINED AS 4141 !BEGINPARSE 4142 REFERENCE 4143 !!This attributes maps to snmpOutSetRequests with 4144 object id {snmp 27} in RFC1213.!!; 4145 DESCRIPTION 4146 !!The total number of SNMP Set-Request PDUs which 4147 have been generated by the SNMP protocol 4148 entity.!!; 4149 ENDPARSE!;; 4150 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 27}; 4152 snmpOutTooBigs ATTRIBUTE 4153 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4154 BEHAVIOUR 4155 snmpOutTooBigsBehaviour BEHAVIOUR 4156 DEFINED AS 4157 !BEGINPARSE 4158 REFERENCE 4159 !!This attribute maps to snmpOutTooBigs with 4160 object id {snmp 20} in RFC1213.!!; 4161 DESCRIPTION 4162 !!The total number of SNMP PDUs which were 4163 generated by the SNMP protocol entity and for 4164 which the value of the error-status field is 4165 `tooBig.'!!; 4166 ENDPARSE!;; 4167 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 20}; 4169 snmpOutTraps ATTRIBUTE 4170 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4171 BEHAVIOUR 4172 snmpOutTrapsBehaviour BEHAVIOUR 4173 DEFINED AS 4174 !BEGINPARSE 4175 REFERENCE 4176 !!This attribute maps to snmpOutTraps with object 4177 id {snmp 29} in RFC1213.!!; 4178 DESCRIPTION 4179 !!The total number of SNMP Trap PDUs which have 4180 been generated by the SNMP protocol entity.!!; 4181 ENDPARSE!;; 4182 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 11 29}; 4183 DRAFT February, 1994 4185 sysContact ATTRIBUTE 4186 DERIVED FROM {iimcIIMCIMIBTRANS} :displayString; 4187 BEHAVIOUR 4188 sysContactBehaviour BEHAVIOUR 4189 DEFINED AS 4190 !BEGINPARSE 4191 REFERENCE 4192 !!This attribute maps to sysContact with object id 4193 {system 4} in RFC1213.!!; 4194 DESCRIPTION 4195 !!The textual identification of the contact person 4196 for this managed node, together with information 4197 on how to contact this person.!!; 4198 ENDPARSE!;; 4199 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 1 4}; 4201 sysDescr ATTRIBUTE 4202 DERIVED FROM {iimcIIMCIMIBTRANS} :displayString; 4203 BEHAVIOUR 4204 sysDescrBehaviour BEHAVIOUR 4205 DEFINED AS 4206 !BEGINPARSE 4207 REFERENCE 4208 !!This attribute maps to sysDescr with object id 4209 {system 1} in RFC1213.!!; 4210 DESCRIPTION 4211 !!A textual description of the entity. This value 4212 should include the full name and version 4213 identification of the system's hardware type, 4214 software operating-system, and networking 4215 software. It is mandatory that this only contain 4216 printable ASCII characters.!!; 4217 ENDPARSE!;; 4218 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 1 1}; 4220 sysLocation ATTRIBUTE 4221 DERIVED FROM {iimcIIMCIMIBTRANS} :displayString; 4222 BEHAVIOUR 4223 sysLocationBehaviour BEHAVIOUR 4224 DEFINED AS 4225 !BEGINPARSE 4226 REFERENCE 4227 !!This attribute maps to sysLocation with object 4228 id {system 6} in RFC 1213.!!; 4229 DESCRIPTION 4230 !!The physical location of this node (e.g., 4231 `telephone closet, 3rd floor').!!; 4232 ENDPARSE!;; 4233 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 1 6}; 4235 sysName ATTRIBUTE 4236 DERIVED FROM {iimcIIMCIMIBTRANS} :displayString; 4237 BEHAVIOUR 4238 sysNameBehaviour BEHAVIOUR 4239 DRAFT February, 1994 4241 DEFINED AS 4242 !BEGINPARSE 4243 REFERENCE 4244 !!This attribute maps to sysName with object id 4245 {system 5} in RFC1213.!!; 4246 DESCRIPTION 4247 !!An administratively-assigned name for this 4248 managed node. By convention, this is the node's 4249 fully-qualified domain name.!!; 4250 ENDPARSE!;; 4251 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 1 5}; 4253 sysObjectID ATTRIBUTE 4254 WITH ATTRIBUTE SYNTAX 4255 IIMCRFC12131354ASN1.ObjectIdentifier; 4256 MATCHES FOR EQUALITY, ORDERING; 4257 BEHAVIOUR 4258 sysObjectIDBehaviour BEHAVIOUR 4259 DEFINED AS 4260 !BEGINPARSE 4261 REFERENCE 4262 !!This attribute maps to sysObjectID with object 4263 id {system 2} in RFC1213.!!; 4264 DESCRIPTION 4265 !!The vendor's authoritative identification of the 4266 network management subsystem contained in the 4267 entity. This value is allocated within the SMI 4268 enterprises subtree (1.3.6.1.4.1) and provides an 4269 easy and unambiguous means for determining `what 4270 kind of box' is being managed. For example, if 4271 vendor `Flintstones, Inc.' was assigned the 4272 subtree 1.3.6.1.4.1.4242, it could assign the 4273 identifier 1.3.6.1.4.1.4242.1.1 to its `Fred 4274 Router'.!!; 4275 ENDPARSE!;; 4276 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 1 2}; 4278 sysServices ATTRIBUTE 4279 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer128; 4280 MATCHES FOR EQUALITY, ORDERING; 4281 BEHAVIOUR 4282 sysServicesBehaviour BEHAVIOUR 4283 DEFINED AS 4284 !BEGINPARSE 4285 REFERENCE 4286 !!This attribute maps to sysServices with object 4287 id {system 7}.!!; 4288 DESCRIPTION 4289 !!A value which indicates the set of services that 4290 this entity primarily offers. 4292 The value is a sum. This sum initially takes the 4293 value zero, Then, for each layer, L, in the range 4294 1 through 7, that this node performs transactions 4295 DRAFT February, 1994 4297 for, 2 raised to (L - 1) is added to the sum. For 4298 example, a node which performs primarily routing 4299 functions would have a value of 4 (2^(3-1)). In 4300 contrast, a node which is a host offering 4301 application services would have a value of 72 4302 (2^(4-1) + 2^(7-1)). Note that in the context of 4303 the Internet suite of protocols, values should be 4304 calculated accordingly: 4306 layer functionality 4307 1 physical (e.g., repeaters) 4308 2 datalink/subnetwork (e.g., bridges) 4309 3 internet (e.g., IP gateways) 4310 4 end-to-end (e.g., IP hosts) 4311 7 applications (e.g., mail relays) 4313 For systems including OSI protocols, layers 5 and 4314 6 may also be counted.!!; 4315 ENDPARSE!;; 4316 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 1 7}; 4318 sysUpTime ATTRIBUTE 4319 DERIVED FROM {iimcIIMCIMIBTRANS}: timeTicks; 4320 BEHAVIOUR 4321 sysUpTimeBehaviour BEHAVIOUR 4322 DEFINED AS 4323 !BEGINPARSE 4324 REFERENCE 4325 !!This attribute maps to sysUpTime with object id 4326 {system 3} in RFC1213.!!; 4327 DESCRIPTION 4328 !!The time (in hundredths of a second) since the 4329 network management portion of the system was last 4330 re-initialized.!!; 4331 ENDPARSE!;; 4332 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 1 3}; 4334 tcpActiveOpens ATTRIBUTE 4335 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4336 BEHAVIOUR 4337 tcpActiveOpensBehaviour BEHAVIOUR 4338 DEFINED AS 4339 !BEGINPARSE 4340 REFERENCE 4341 !!This attribute maps to tcpActiveOpens with 4342 object id {tcp 5} in RFC1213.!!; 4343 DESCRIPTION 4344 !!The number of times TCP connections have made a 4345 direct transition to the SYN-SENT state from the 4346 CLOSED state!!; 4347 ENDPARSE!;; 4348 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 5}; 4350 tcpAttemptFails ATTRIBUTE 4351 DRAFT February, 1994 4353 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4354 BEHAVIOUR 4355 tcpAttemptFailsBehaviour BEHAVIOUR 4356 DEFINED AS 4357 !BEGINPARSE 4358 REFERENCE 4359 !!This attribute maps to tcpAttemptFails with 4360 object id {tcp 7} in RFC1213.!!; 4361 DESCRIPTION 4362 !!The number of times TCP connections have made a 4363 direct transition to the CLOSED state from either 4364 the SYN-SENT state or the SYN-RCVD state, plus the 4365 number of times TCP connections have made a direct 4366 transition to the LISTEN state from the SYN-RCVD 4367 state.!!; 4368 ENDPARSE!;; 4369 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 7}; 4371 tcpConnEntryId ATTRIBUTE 4372 WITH ATTRIBUTE SYNTAX 4373 IIMCRFC12131354ASN1.TcpConnEntryIdValue; 4374 MATCHES FOR EQUALITY; 4375 BEHAVIOUR 4376 tcpConnEntryIdBehaviour BEHAVIOUR 4377 DEFINED AS 4378 !The naming attribute for object class 4379 tcpConnEntry.!;; 4380 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 6 13 1}; 4382 tcpConnLocalAddress ATTRIBUTE 4383 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 4384 BEHAVIOUR 4385 tcpConnLocalAddressBehaviour BEHAVIOUR 4386 DEFINED AS 4387 !BEGINPARSE 4388 REFERENCE 4389 !!This attribute maps to tcpConnLocalAddress with 4390 object id {tcpConnEntry 2} in RFC1213.!!; 4391 DESCRIPTION 4392 !!The local IP address for this TCP connection. In 4393 the case of a connection in the listen state which 4394 is willing to accept connections for any IP 4395 interface associated with the node, the value 4396 0.0.0.0 is used.!!; 4397 ENDPARSE!;; 4398 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 13 1 2}; 4400 tcpConnLocalPort ATTRIBUTE 4401 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer64k; 4402 MATCHES FOR EQUALITY, ORDERING; 4403 BEHAVIOUR 4404 tcpConnLocalPortBehaviour BEHAVIOUR 4405 DEFINED AS 4406 !BEGINPARSE 4407 DRAFT February, 1994 4409 REFERENCE 4410 !!This attribute maps to tcpConnLocalPort with 4411 object id {tcpConnEntry 3} in RFC1213.!!; 4412 DESCRIPTION 4413 !!The local port number for this TCP 4414 connection.!!; 4415 ENDPARSE!;; 4416 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 13 1 3}; 4418 tcpConnRemAddress ATTRIBUTE 4419 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 4420 BEHAVIOUR 4421 tcpConnRemAddressBehaviour BEHAVIOUR 4422 DEFINED AS 4423 !BEGINPARSE 4424 REFERENCE 4425 !!This attribute maps to tcpConnRemAddress with 4426 object id {tcpConnEntry 4} in RFC1213.!!; 4427 DESCRIPTION 4428 !!The remote IP address for this TCP 4429 connection.!!; 4430 ENDPARSE!;; 4431 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 13 1 4}; 4433 tcpConnRemPort ATTRIBUTE 4434 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer64k; 4435 MATCHES FOR EQUALITY, ORDERING; 4436 BEHAVIOUR 4437 tcpConnRemPortBehaviour BEHAVIOUR 4438 DEFINED AS 4439 !BEGINPARSE 4440 REFERENCE 4441 !!This attribute maps to tcpConnRemPort with 4442 object id {tcpConnEntry 5} in RFC1213.!!; 4443 DESCRIPTION 4444 !!The remote port number for this TCP 4445 connection.!!; 4446 ENDPARSE!;; 4447 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 13 1 5}; 4449 tcpConnState ATTRIBUTE 4450 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.TcpConnState; 4451 MATCHES FOR EQUALITY, ORDERING; 4452 BEHAVIOUR 4453 tcpConnStateBehaviour BEHAVIOUR 4454 DEFINED AS 4455 !BEGINPARSE 4456 REFERENCE 4457 !!This attribute maps to tcpConnState with object 4458 id {tcpConnEntry 1} in RFC1213.!!; 4459 DESCRIPTION 4460 !!The state of this TCP connection. The only value 4461 which may be set by a management station is 4462 deleteTCB(12). Accordingly, it is appropriate for 4463 DRAFT February, 1994 4465 an agent to return a `badValue' response if a 4466 management station attempts to set this attribute 4467 to any other value. If a management station sets 4468 this attribute to the value deleteTCB(12), then 4469 this has the effect of deleting the TCB (as 4470 defined in RFC 793) of the corresponding 4471 connection on the managed node, resulting in 4472 immediate termination of the connection. As an 4473 implementation-specific option, a RST segment may 4474 be sent from the managed node to the other TCP 4475 endpoint (note however that RST segments are not 4476 sent reliably).!!; 4477 ENDPARSE!;; 4478 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 13 1 1}; 4480 tcpCurrEstab ATTRIBUTE 4481 DERIVED FROM {iimcIIMCIMIBTRANS}: gauge32; 4482 BEHAVIOUR 4483 tcpCurrEstabBehaviour BEHAVIOUR 4484 DEFINED AS 4485 !BEGINPARSE 4486 REFERENCE 4487 !!This attribute maps to tcpCurrEstab with object 4488 id {tcp 9} in RFC1213.!!; 4489 DESCRIPTION 4490 !!The number of TCP connections for which the 4491 current state is either ESTABLISHED or CLOSE- 4492 WAIT.!!; 4493 ENDPARSE!;; 4494 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 9}; 4496 tcpEstabResets ATTRIBUTE 4497 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4498 BEHAVIOUR 4499 tcpEstabResetsBehaviour BEHAVIOUR 4500 DEFINED AS 4501 !BEGINPARSE 4502 REFERENCE 4503 !!This attribute maps to tcpEstabResets with 4504 object id {tcp 8} in RFC1213.!!; 4505 DESCRIPTION 4506 !!The number of times TCP connections have made a 4507 direct transition to the CLOSED state from either 4508 the ESTABLISHED state or the CLOSE-WAIT state.!!; 4509 ENDPARSE!;; 4510 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 8}; 4512 tcpId ATTRIBUTE 4513 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.TcpIdValue; 4514 MATCHES FOR EQUALITY; 4515 BEHAVIOUR 4516 tcpIdBehaviour BEHAVIOUR 4517 DEFINED AS 4518 !The naming attribute for object class tcp.!;; 4519 DRAFT February, 1994 4521 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 6}; 4523 tcpInErrs ATTRIBUTE 4524 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4525 BEHAVIOUR 4526 tcpInErrsBehaviour BEHAVIOUR 4527 DEFINED AS 4528 !BEGINPARSE 4529 REFERENCE 4530 !!This attribute maps to tcpInErrs with object id 4531 {tcp 14} in RFC1213.!!; 4532 DESCRIPTION 4533 !!The total number of segments received in error 4534 (e.g., bad TCP checksums).!!; 4535 ENDPARSE!;; 4536 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 14}; 4538 tcpInSegs ATTRIBUTE 4539 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4540 BEHAVIOUR 4541 tcpInSegsBehaviour BEHAVIOUR 4542 DEFINED AS 4543 !BEGINPARSE 4544 REFERENCE 4545 !!This attribute maps to tcpInSegs with object id 4546 {tcp 10} in RFC1213.!!; 4547 DESCRIPTION 4548 !!The total number of segments received, including 4549 those received in error. This count includes 4550 segments received on currently established 4551 connections.!!; 4552 ENDPARSE!;; 4553 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 10}; 4555 tcpMaxConn ATTRIBUTE 4556 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 4557 MATCHES FOR EQUALITY, ORDERING; 4558 BEHAVIOUR 4559 tcpMaxConnBehaviour BEHAVIOUR 4560 DEFINED AS 4561 !BEGINPARSE 4562 REFERENCE 4563 !!This attribute maps to tcpMaxConn with object id 4564 {tcp 4} in RFC1213.!!; 4565 DESCRIPTION 4566 !!The limit on the total number of TCP connections 4567 the entity can support. In entities where the 4568 maximum number of connections is dynamic, this 4569 attribute should contain the value -1.!!; 4570 ENDPARSE!;; 4571 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 4}; 4573 tcpOutRsts ATTRIBUTE 4574 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4575 DRAFT February, 1994 4577 BEHAVIOUR 4578 tcpOutRstsBehaviour BEHAVIOUR 4579 DEFINED AS 4580 !BEGINPARSE 4581 REFERENCE 4582 !!This attribute maps to tcpOutRsts with object id 4583 {tcp 15} in RFC1213.!!; 4584 DESCRIPTION 4585 !!The number of TCP segments sent containing the 4586 RST flag.!!; 4587 ENDPARSE!;; 4588 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 15}; 4590 tcpOutSegs ATTRIBUTE 4591 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4592 BEHAVIOUR 4593 tcpOutSegsBehaviour BEHAVIOUR 4594 DEFINED AS 4595 !BEGINPARSE 4596 REFERENCE 4597 !!This attribute maps to tcpOutSegs with object id 4598 {tcp 11} in RFC1213.!!; 4599 DESCRIPTION 4600 !!The total number of segments sent, including 4601 those on current connections but excluding those 4602 containing only retransmitted octets.!!; 4603 ENDPARSE!;; 4604 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 11}; 4606 tcpPassiveOpens ATTRIBUTE 4607 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4608 BEHAVIOUR 4609 tcpPassiveOpensBehaviour BEHAVIOUR 4610 DEFINED AS 4611 !BEGINPARSE 4612 REFERENCE 4613 !!This attribute maps to tcpPassiveOpens with 4614 object id {tcp 6} in RFC1213.!!; 4615 DESCRIPTION 4616 !!The number of times TCP connections have made a 4617 direct transition to the SYN-RCVD state from the 4618 LISTEN state.!!; 4619 ENDPARSE!;; 4620 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 6}; 4622 tcpRetransSegs ATTRIBUTE 4623 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4624 BEHAVIOUR 4625 tcpRetransSegsBehaviour BEHAVIOUR 4626 DEFINED AS 4627 !BEGINPARSE 4628 REFERENCE 4629 !!This attribute maps to tcpRetransSegs with 4630 object id {tcp 12} in RFC1213.!!; 4631 DRAFT February, 1994 4633 DESCRIPTION 4634 !!The total number of segments retransmitted - 4635 that is, the number of TCP segments transmitted 4636 containing one or more previously transmitted 4637 octets.!!; 4638 ENDPARSE!;; 4639 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 12}; 4641 tcpRtoAlgorithm ATTRIBUTE 4642 WITH ATTRIBUTE SYNTAX 4643 IIMCRFC12131354ASN1.TcpRtoAlgorithm; 4644 MATCHES FOR EQUALITY, ORDERING; 4645 BEHAVIOUR 4646 tcpRtoAlgorithmBehaviour BEHAVIOUR 4647 DEFINED AS 4648 !BEGINPARSE 4649 REFERENCE 4650 !!This attribute maps to tcpRtoAlgorithm with 4651 object id {tcp 1} in RFC1213.!!; 4652 DESCRIPTION 4653 !!The algorithm used to determine the timeout 4654 value used for retransmitting unacknowledged 4655 octets.!!; 4656 ENDPARSE!;; 4657 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 1}; 4659 tcpRtoMax ATTRIBUTE 4660 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 4661 MATCHES FOR EQUALITY, ORDERING; 4662 BEHAVIOUR 4663 tcpRtoMaxBehaviour BEHAVIOUR 4664 DEFINED AS 4665 !BEGINPARSE 4666 REFERENCE 4667 !!This attribute maps to tcpRtoMax with object id 4668 {tcp 3} in RFC1213.!!; 4669 DESCRIPTION 4670 !!The maximum value permitted by a TCP 4671 implementation for the retransmission timeout, 4672 measured in milliseconds. More refined semantics 4673 for attributes of this type depend upon the 4674 algorithm used to determine the retransmission 4675 timeout. In particular, when the timeout algorithm 4676 is rsre(3), an attribute of this type has the 4677 semantics of the UBOUND quantity described in RFC 4678 793.!!; 4679 ENDPARSE!;; 4680 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 3}; 4682 tcpRtoMin ATTRIBUTE 4683 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer; 4684 MATCHES FOR EQUALITY, ORDERING; 4685 BEHAVIOUR 4686 tcpRtoMinBehaviour BEHAVIOUR 4687 DRAFT February, 1994 4689 DEFINED AS 4690 !BEGINPARSE 4691 REFERENCE 4692 !!This attribute maps to tcpRtoMin with object id 4693 {tcp 2} in RFC1213.!!; 4694 DESCRIPTION 4695 !!The minimum value permitted by a TCP 4696 implementation for the retransmission timeout, 4697 measured in milliseconds. More refined semantics 4698 for attributes of this type depend upon the 4699 algorithm used to determine the retransmission 4700 timeout. In particular, when the timeout algorithm 4701 is rsre(3), an attribute of this type has the 4702 semantics of the LBOUND quantity described in RFC 4703 793.!!; 4704 ENDPARSE!;; 4705 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 6 2}; 4707 udpEntryId ATTRIBUTE 4708 WITH ATTRIBUTE SYNTAX 4709 IIMCRFC12131354ASN1.UdpEntryIdValue; 4710 MATCHES FOR EQUALITY; 4711 BEHAVIOUR 4712 udpEntryIdBehaviour BEHAVIOUR 4713 DEFINED AS 4714 !The naming attribute for object class 4715 udpEntry.!;; 4716 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 7 5 1}; 4718 udpId ATTRIBUTE 4719 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.UdpIdValue; 4720 MATCHES FOR EQUALITY; 4721 BEHAVIOUR 4722 udpIdBehaviour BEHAVIOUR 4723 DEFINED AS 4724 !The naming attribute for object class udp.!;; 4725 REGISTERED AS {iimcAutoName 1 3 6 1 2 1 7}; 4727 udpInDatagrams ATTRIBUTE 4728 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4729 BEHAVIOUR 4730 udpInDatagramsBehaviour BEHAVIOUR 4731 DEFINED AS 4732 !BEGINPARSE 4733 REFERENCE 4734 !!This attribute maps to udpInDatagrams with 4735 object id {udp 1} in RFC1213.!!; 4736 DESCRIPTION 4737 !!The total number of UDP datagrams delivered to 4738 UDP users.!!; 4739 ENDPARSE!;; 4740 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 7 1}; 4742 udpInErrors ATTRIBUTE 4743 DRAFT February, 1994 4745 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4746 BEHAVIOUR 4747 udpInErrorsBehaviour BEHAVIOUR 4748 DEFINED AS 4749 !BEGINPARSE 4750 REFERENCE 4751 !!This attribute maps to udpInErrors with object 4752 id {udp 3} in RFC1213.!!; 4753 DESCRIPTION 4754 !!The number of received UDP datagrams that could 4755 not be delivered for reasons other than the lack 4756 of an application at the destination port.!!; 4757 ENDPARSE!;; 4758 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 7 3}; 4760 udpLocalAddress ATTRIBUTE 4761 DERIVED FROM {iimcIIMCIMIBTRANS}:ipAddress; 4762 BEHAVIOUR 4763 udpLocalAddressBehaviour BEHAVIOUR 4764 DEFINED AS 4765 !BEGINPARSE 4766 REFERENCE 4767 !!This attribute maps to udpLocalAddress with 4768 object id {udpEntry 1} in RFC1213.!!; 4769 DESCRIPTION 4770 !!The local IP address for this UDP listener. In 4771 the case of a UDP listener which is willing to 4772 accept datagrams for any IP interface associated 4773 with the node, the value 0.0.0.0 is used.!!; 4774 ENDPARSE!;; 4775 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 7 5 1 1}; 4777 udpLocalPort ATTRIBUTE 4778 WITH ATTRIBUTE SYNTAX IIMCRFC12131354ASN1.Integer64k; 4779 MATCHES FOR EQUALITY, ORDERING; 4780 BEHAVIOUR 4781 udpLocalPortBehaviour BEHAVIOUR 4782 DEFINED AS 4783 !BEGINPARSE 4784 REFERENCE 4785 !!This attribute maps to udpLocalPort with object 4786 id {udpEntry 2} in RFC 1213.!!; 4787 DESCRIPTION 4788 !!The local port number for this UDP listener.!!; 4789 ENDPARSE!;; 4790 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 7 5 1 2}; 4792 udpNoPorts ATTRIBUTE 4793 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4794 BEHAVIOUR 4795 udpNoPortsBehaviour BEHAVIOUR 4796 DEFINED AS 4797 !BEGINPARSE 4798 REFERENCE 4799 DRAFT February, 1994 4801 !!This attribute maps to udpNoPorts with object id 4802 {udp 2} in RFC1213.!!; 4803 DESCRIPTION 4804 !!The total number of received UDP datagrams for 4805 which there was no application at the destination 4806 port.!!; 4807 ENDPARSE!;; 4808 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 7 2}; 4810 udpOutDatagrams ATTRIBUTE 4811 DERIVED FROM {iimcIIMCIMIBTRANS} :counter32; 4812 BEHAVIOUR 4813 udpOutDatagramsBehaviour BEHAVIOUR 4814 DEFINED AS 4815 !BEGINPARSE 4816 REFERENCE 4817 !!This attribute maps to udpOutDatagrams with 4818 object id {udp 4} in RFC1213.!!; 4819 DESCRIPTION 4820 !!The total number of UDP datagrams sent from this 4821 entity.!!; 4822 ENDPARSE!;; 4823 REGISTERED AS {iimcAutoObjAndAttr 1 3 6 1 2 1 7 4}; 4825 -- 2.1.3 IIMCMIB-II Name Bindings 4827 at-systemNB NAME BINDING 4828 SUBORDINATE OBJECT CLASS at AND SUBCLASSES ; 4829 NAMED BY SUPERIOR OBJECT CLASS 4830 "Rec. X.721 | ISO/IEC 10165-2 : 1992" :system 4831 AND SUBCLASSES; 4832 WITH ATTRIBUTE atId; 4833 BEHAVIOUR 4834 at-systemNBBehaviour BEHAVIOUR 4835 DEFINED AS 4836 !BEGINPARSE 4837 INDEX NULL; 4838 ENDPARSE!;; 4839 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 3 }; 4841 atEntry-atNB NAME BINDING 4842 SUBORDINATE OBJECT CLASS atEntry AND SUBCLASSES ; 4843 NAMED BY SUPERIOR OBJECT CLASS at AND SUBCLASSES; 4844 WITH ATTRIBUTE atEntryId; 4845 BEHAVIOUR 4846 atEntry-atNBBehaviour BEHAVIOUR 4847 DEFINED AS 4848 !BEGINPARSE 4849 INDEX RFC1213-MIB.atIfIndex, 4850 RFC1213-MIB.atNetAddress; 4851 DELETEATT atPhysAddress; 4852 DELETEVALUE ''h; 4853 DRAFT February, 1994 4855 ENDPARSE!;; 4856 CREATE WITH-AUTOMATIC-INSTANCE-NAMING, 4857 WITH-REFERENCE-OBJECT; 4858 DELETE DELETES-CONTAINED-OBJECTS; 4859 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 3 1 1}; 4861 egp-systemNB NAME BINDING 4862 SUBORDINATE OBJECT CLASS egp AND SUBCLASSES; 4863 NAMED BY SUPERIOR OBJECT CLASS 4864 "Rec. X.721 | ISO/IEC 10165-2 : 1992" :system 4865 AND SUBCLASSES; 4866 WITH ATTRIBUTE egpId; 4867 BEHAVIOUR 4868 egp-systemNBBehaviour BEHAVIOUR 4869 DEFINED AS 4870 !BEGINPARSE 4871 INDEX NULL; 4872 ENDPARSE!;; 4873 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 8 }; 4875 egpNeighEntry-egpNB NAME BINDING 4876 SUBORDINATE OBJECT CLASS egpNeighEntry AND SUBCLASSES; 4877 NAMED BY SUPERIOR OBJECT CLASS egp AND SUBCLASSES; 4878 WITH ATTRIBUTE egpNeighEntryId; 4879 BEHAVIOUR 4880 egpNeighEntry-egpNBBehaviour BEHAVIOUR 4881 DEFINED AS 4882 !BEGINPARSE 4883 INDEX RFC1213-MIB.egpNeighAddr; 4884 ENDPARSE!;; 4885 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 8 5 1}; 4887 icmp-systemNB NAME BINDING 4888 SUBORDINATE OBJECT CLASS icmp AND SUBCLASSES; 4889 NAMED BY SUPERIOR OBJECT CLASS 4890 "Rec. X.721 | ISO/IEC 10165-2 : 1992" :system 4891 AND SUBCLASSES; 4892 WITH ATTRIBUTE icmpId; 4893 BEHAVIOUR 4894 icmp-systemNBBehaviour BEHAVIOUR 4895 DEFINED AS 4896 !BEGINPARSE 4897 INDEX NULL; 4898 ENDPARSE!;; 4899 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 5 }; 4901 ifEntry-interfacesNB NAME BINDING 4902 SUBORDINATE OBJECT CLASS ifEntry AND SUBCLASSES; 4903 NAMED BY SUPERIOR OBJECT CLASS interfaces AND 4904 SUBCLASSES; 4905 WITH ATTRIBUTE ifEntryId; 4906 BEHAVIOUR 4907 ifEntry-interfacesNBBehaviour BEHAVIOUR 4908 DEFINED AS 4909 DRAFT February, 1994 4911 !BEGINPARSE 4912 INDEX RFC1213-MIB.ifIndex; 4913 ENDPARSE!;; 4914 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 2 2 1}; 4916 interfaces-systemNB NAME BINDING 4917 SUBORDINATE OBJECT CLASS interfaces AND SUBCLASSES; 4918 NAMED BY SUPERIOR OBJECT CLASS 4919 "Rec. X.721 | ISO/IEC 10165-2 : 1992" :system 4920 AND SUBCLASSES; 4921 WITH ATTRIBUTE interfacesId; 4922 BEHAVIOUR 4923 interfaces-systemNBBehaviour BEHAVIOUR 4924 DEFINED AS 4925 !BEGINPARSE 4926 INDEX NULL; 4927 ENDPARSE!;; 4928 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 2 }; 4930 internetSystem-systemNB NAME BINDING 4931 SUBORDINATE OBJECT CLASS internetSystem AND 4932 SUBCLASSES; 4933 NAMED BY SUPERIOR OBJECT CLASS 4934 "Rec. X.721 | ISO/IEC 10165-2 : 1992" :system 4935 AND SUBCLASSES; 4936 WITH ATTRIBUTE internetSystemId; 4937 BEHAVIOUR 4938 internetSystem-systemNBBehaviour BEHAVIOUR 4939 DEFINED AS 4940 !BEGINPARSE 4941 INDEX NULL; 4942 ENDPARSE!;; 4943 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 1 }; 4945 ip-systemNB NAME BINDING 4946 SUBORDINATE OBJECT CLASS ip AND SUBCLASSES; 4947 NAMED BY SUPERIOR OBJECT CLASS 4948 "Rec. X.721 | ISO/IEC 10165-2 : 1992" :system 4949 AND SUBCLASSES; 4950 WITH ATTRIBUTE ipId; 4951 BEHAVIOUR 4952 ip-systemNBBehaviour BEHAVIOUR 4953 DEFINED AS 4954 !BEGINPARSE 4955 INDEX NULL; 4956 ENDPARSE!;; 4957 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 4}; 4959 ipAddrEntry-ipNB NAME BINDING 4960 SUBORDINATE OBJECT CLASS ipAddrEntry AND 4961 SUBCLASSES; 4962 NAMED BY SUPERIOR OBJECT CLASS ip AND SUBCLASSES; 4963 WITH ATTRIBUTE ipAddrEntryId; 4964 BEHAVIOUR 4965 DRAFT February, 1994 4967 ipAddrEntry-ipNBBehaviour BEHAVIOUR 4968 DEFINED AS 4969 !BEGINPARSE 4970 INDEX RFC1213-MIB.ipAdEntAddr; 4971 ENDPARSE!;; 4972 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 4 20 1}; 4974 ipForwardEntry-ipNB NAME BINDING 4975 SUBORDINATE OBJECT CLASS ipForwardEntry AND 4976 SUBCLASSES; 4977 NAMED BY SUPERIOR OBJECT CLASS ip AND SUBCLASSES; 4978 WITH ATTRIBUTE ipForwardEntryId; 4979 BEHAVIOUR 4980 ipForwardEntry-ipNBBehaviour BEHAVIOUR 4981 DEFINED AS 4982 !BEGINPARSE 4983 INDEX RFC1354-MIB.ipForwardDest, 4984 RFC1354-MIB.ipForwardProto, 4985 RFC1354-MIB.ipForwardPolicy, 4986 RFC1354-MIB.ipForwardNextHop; 4987 DELETEATT ipForwardType; 4988 DELETEVALUE 2; 4989 ENDPARSE!;; 4990 CREATE WITH-AUTOMATIC-INSTANCE-NAMING, 4991 WITH-REFERENCE-OBJECT; 4992 DELETE DELETES-CONTAINED-OBJECTS; 4993 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 4 24 2 1}; 4995 ipNetToMediaEntry-ipNB NAME BINDING 4996 SUBORDINATE OBJECT CLASS ipNetToMediaEntry AND 4997 SUBCLASSES; 4998 NAMED BY SUPERIOR OBJECT CLASS ip AND SUBCLASSES; 4999 WITH ATTRIBUTE ipNetToMediaEntryId; 5000 BEHAVIOUR 5001 ipNetToMediaEntry-ipNBBehaviour 5002 BEHAVIOUR 5003 DEFINED AS 5004 !BEGINPARSE 5005 INDEX RFC1213-MIB.ipNetToMediaIfIndex, 5006 RFC1213-MIB.ipNetToMediaNetAddress; 5007 DELETEATT ipNetToMediaType; 5008 DELETEVALUE 2; 5009 ENDPARSE!;; 5010 CREATE WITH-AUTOMATIC-INSTANCE-NAMING, 5011 WITH-REFERENCE-OBJECT; 5012 DELETE DELETES-CONTAINED-OBJECTS; 5013 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 4 22 1}; 5015 ipRouteEntry-ipNB NAME BINDING 5016 SUBORDINATE OBJECT CLASS ipRouteEntry AND 5017 SUBCLASSES; 5018 NAMED BY SUPERIOR OBJECT CLASS ip AND SUBCLASSES; 5019 WITH ATTRIBUTE ipRouteEntryId; 5020 BEHAVIOUR 5021 DRAFT February, 1994 5023 ipRouteEntry-ipNBBehaviour BEHAVIOUR 5024 DEFINED AS 5025 !BEGINPARSE 5026 INDEX RFC1213-MIB.ipRouteDest; 5027 DELETEATT ipRouteType; 5028 DELETEVALUE 2; 5029 ENDPARSE!;; 5030 CREATE WITH-AUTOMATIC-INSTANCE-NAMING, 5031 WITH-REFERENCE-OBJECT; 5032 DELETE DELETES-CONTAINED-OBJECTS; 5033 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 4 21 1}; 5035 snmp-systemNB NAME BINDING 5036 SUBORDINATE OBJECT CLASS snmp AND SUBCLASSES; 5037 NAMED BY SUPERIOR OBJECT CLASS 5038 "Rec. X.721 | ISO/IEC 10165-2 : 1992" :system 5039 AND SUBCLASSES; 5040 WITH ATTRIBUTE snmpId; 5041 BEHAVIOUR 5042 snmp-systemNBBehaviour BEHAVIOUR 5043 DEFINED AS 5044 !BEGINPARSE 5045 INDEX NULL; 5046 ENDPARSE!;; 5047 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 11}; 5049 tcp-systemNB NAME BINDING 5050 SUBORDINATE OBJECT CLASS tcp AND SUBCLASSES; 5051 NAMED BY SUPERIOR OBJECT CLASS 5052 "Rec. X.721 | ISO/IEC 10165-2 : 1992" :system 5053 AND SUBCLASSES; 5054 WITH ATTRIBUTE tcpId; 5055 BEHAVIOUR 5056 tcp-systemNBBehaviour BEHAVIOUR 5057 DEFINED AS 5058 !BEGINPARSE 5059 INDEX NULL; 5060 ENDPARSE!;; 5061 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 6 }; 5063 tcpConnEntry-tcpNB NAME BINDING 5064 SUBORDINATE OBJECT CLASS tcpConnEntry AND 5065 SUBCLASSES; 5066 NAMED BY SUPERIOR OBJECT CLASS tcp AND SUBCLASSES; 5067 WITH ATTRIBUTE tcpConnEntryId; 5068 BEHAVIOUR 5069 tcpConnEntry-tcpNBBehaviour BEHAVIOUR 5070 DEFINED AS 5071 !BEGINPARSE 5072 INDEX RFC1213-MIB.tcpConnLocalAddress, 5073 RFC1213-MIB.tcpConnLocalPort, 5074 RFC1213-MIB.tcpConnRemAddress, 5075 RFC1213-MIB.tcpConnRemPort; 5076 ENDPARSE!;; 5077 DRAFT February, 1994 5079 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 6 13 1}; 5081 udp-systemNB NAME BINDING 5082 SUBORDINATE OBJECT CLASS udp AND SUBCLASSES; 5083 NAMED BY SUPERIOR OBJECT CLASS 5084 "Rec. X.721 | ISO/IEC 10165-2 : 1992" :system 5085 AND SUBCLASSES; 5086 WITH ATTRIBUTE udpId; 5087 BEHAVIOUR 5088 udp-systemNBBehaviour BEHAVIOUR 5089 DEFINED AS 5090 !BEGINPARSE 5091 INDEX NULL; 5092 ENDPARSE!;; 5093 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 7}; 5095 udpEntry-udpNB NAME BINDING 5096 SUBORDINATE OBJECT CLASS udpEntry AND SUBCLASSES; 5097 NAMED BY SUPERIOR OBJECT CLASS udp AND SUBCLASSES; 5098 WITH ATTRIBUTE udpEntryId; 5099 BEHAVIOUR 5100 udpEntry-udpNBBehaviour BEHAVIOUR 5101 DEFINED AS 5102 !BEGINPARSE 5103 INDEX RFC1213-MIB.udpLocalAddress, 5104 RFC1213-MIB.udpLocalPort; 5105 ENDPARSE!;; 5106 REGISTERED AS {iimcAutoNameBinding 1 3 6 1 2 1 7 5 1}; 5108 -- 2.2 IIMCMIB-II ASN.1 MODULE 5110 IIMCRFC12131354ASN1 {iso(1) member-body(2) 124 forum(360501) 5111 iimcAutoTrans(14) 5112 iimcAutoModule(0) 1213 1354} DEFINITIONS IMPLICIT TAGS ::= 5113 BEGIN 5114 IMPORTS 5115 iimcAutoDocument, iimcAutoModule, 5116 iimcAutoObjAndAttr, 5117 iimcAutoNameBinding, iimcAutoName 5118 FROM IimcAssignedOIDs 5119 {iso(1) member-body(2) 124 forum(360501) 5120 iimcManual(15) iimcModule(0) 1} 5121 Integer, Integer128, Integer64k, ObjectIdentifier 5122 FROM IimcCommonDef 5123 {iso(1) member-body(2) 124 forum(360501) 5124 iimcManual(15) iimcModule(0) 2} 5125 IpAddress 5126 FROM SNMPv2-SMI; 5128 -- The following registration identifier is assigned to 5129 -- this document using procedures defined in [19]: 5131 DRAFT February, 1994 5133 iimcRFC12131354 OBJECT IDENTIFIER ::= {iimcAutoDocument 1213 5134 1354} 5136 AtEntryIdValue ::= SEQUENCE { 5137 atIfIndex [1] Integer, 5138 atNetAddress [2] IpAddress 5139 } 5141 AtIdValue ::= NULL 5143 c-ipForwardMask IpAddress ::= '00000000'H 5144 c-ipForwardIfIndex Integer ::= 0 5145 c-ipForwardType IPForwardType ::= 2 -- invalid 5146 c-ipForwardAge Integer ::= 0 5147 c-ipForwardInfo ObjectIdentifier ::= { 0 0 } 5148 c-ipForwardNextHopAS Integer ::= 0 5149 c-ipForwardMetric1 Integer ::= -1 5150 c-ipForwardMetric2 Integer ::= -1 5151 c-ipForwardMetric3 Integer ::= -1 5152 c-ipForwardMetric4 Integer ::= -1 5153 c-ipForwardMetric5 Integer ::= -1 5155 EgpIdValue ::= NULL 5157 EgpNeighEntryIdValue ::= SEQUENCE { 5158 egpNeighAddr [1] IpAddress 5159 } 5161 EgpNeighEventTrigger ::= INTEGER { 5162 start(1), 5163 stop(2) 5164 } 5166 EgpNeighMode ::= INTEGER { 5167 active(1), 5168 passive(2) 5169 } 5171 EgpNeighState ::= INTEGER { 5172 idle(1), 5173 acquisition(2), 5174 down(3), 5175 up(4), 5176 cease(5) 5177 } 5179 IcmpIdValue ::= NULL 5181 IfAdminStatus ::= INTEGER { 5182 up(1), -- ready to pass packets 5183 down(2), 5184 testing(3) -- in some test mode 5185 } 5186 DRAFT February, 1994 5188 IfEntryIdValue ::= SEQUENCE { 5189 ifIndex [1] Integer 5190 } 5192 IfOperStatus ::= INTEGER { 5193 up(1),-- ready to pass packets 5194 down(2), 5195 testing(3)-- in some test mode 5196 } 5198 IfType ::= INTEGER { 5199 other(1), -- none of the following 5200 regular1822(2), 5201 hdh1822(3), 5202 ddn-x25(4), 5203 rfc877-x25(5), 5204 ethernet-csmacd(6), 5205 iso88023-csmacd(7), 5206 iso88024-tokenBus(8), 5207 iso88025-tokenRing(9), 5208 iso88026-man(10), 5209 starLan(11), 5210 proteon-10Mbit(12), 5211 proteon-80Mbit(13), 5212 hyperchannel(14), 5213 fddi(15), 5214 lapb(16), 5215 sdlc(17), 5216 ds1(18), 5217 e1(19),-- european equivalent of T-1 5218 basicISDN(20), 5219 primaryISDN(21),-- proprietary serial 5220 propPointToPointSerial(22), 5221 ppp(23), 5222 softwareLoopback(24), 5223 eon(25), -- CLNP over IP 5224 ethernet-3Mbit(26), 5225 nsip(27), -- XNS over IP 5226 slip(28), -- generic SLIP 5227 ultra(29), -- ULTRA technologies 5228 ds3(30), -- T-3 5229 sip(31), -- SMDS 5230 frame-relay(32) 5231 } 5233 InterfacesIdValue ::= NULL 5235 InternetSystemIdValue ::= NULL 5237 IpAddrEntryIdValue ::= SEQUENCE { 5238 ipAdEntAddr [1] IpAddress 5239 } 5241 IpForwardEntryIdValue ::= 5242 DRAFT February, 1994 5244 SEQUENCE { 5245 ipForwardDest [1] IpAddress, 5246 ipForwardProto [2] IpForwardProto, 5247 ipForwardPolicy [3] Integer, 5248 ipForwardNextHop [4] IpAddress 5249 } 5251 IpForwarding ::= INTEGER { 5252 forwarding(1),-- acting as a gateway 5253 not-forwarding(2)-- NOT acting as a gateway 5254 } 5256 IpForwardType ::= INTEGER { 5257 other (1), -- not specified by this MIB 5258 invalid (2), -- logically deleted 5259 local (3), -- local interface 5260 remote (4) -- remote destination 5261 } 5263 IpForwardProto ::= INTEGER { 5264 other (1), -- not specified 5265 local (2), -- local interface 5266 netmgmt (3), -- static route 5267 icmp (4), -- result of ICMP Redirect 5268 -- the following are all dynamic 5269 -- routing protocols 5270 egp (5), -- Exterior Gateway Protocol 5271 ggp (6), -- Gateway-Gateway Protocol 5272 hello (7), -- FuzzBall HelloSpeak 5273 rip (8), -- Berkeley RIP or RIP-II 5274 is-is (9), -- Dual IS-IS 5275 es-is (10), -- ISO 9542 5276 ciscoIgrp (11), -- Cisco IGRP 5277 bbnSpfIgp (12), -- BBN SPF IGP 5278 ospf (13), -- Open Shortest Path First 5279 bgp (14), -- Border Gateway Protocol 5280 idpr (15) -- InterDomain Policy Routing 5281 } 5283 IpIdValue ::= NULL 5285 IpNetToMediaEntryIdValue ::= 5286 SEQUENCE { 5287 ipNetToMediaIfIndex [1] Integer, 5288 ipNetToMediaNetAddress [2] IpAddress 5289 } 5291 IpNetToMediaType ::= INTEGER { 5292 other(1), -- none of the following 5293 invalid(2),-- an invalidated mapping 5294 dynamic(3), 5295 static(4) 5296 } 5297 DRAFT February, 1994 5299 IpRouteEntryIdValue ::= SEQUENCE { 5300 ipRouteDest [1] IpAddress 5301 } 5303 IpRouteProto ::= INTEGER { 5304 other(1), -- none of the following 5305 local(2), -- configured entries 5306 netmgmt(3), -- mgmt protocol 5307 icmp(4), -- obtained via ICMP, 5308 -- e.g., redirect 5309 egp(5), 5310 ggp(6), 5311 hello(7), 5312 rip(8), 5313 is-is(9), 5314 es-is(10), 5315 ciscoIgrp(11), 5316 bbnSpfIgp(12), 5317 ospf(13), 5318 bgp(14) 5319 } 5321 IpRouteType ::= INTEGER { 5322 other(1), -- none of the following 5323 invalid(2), -- an invalidated route 5324 direct(3), -- route to directly connected subnetwork 5325 indirect(4) -- route to a non-local host/network/subnet 5326 } 5328 SnmpEnableAuthenTraps ::= INTEGER { 5329 enabled (1), 5330 disabled (2) 5331 } 5333 SnmpIdValue ::= NULL 5335 TcpConnEntryIdValue ::= 5336 SEQUENCE { 5337 tcpConnLocalAddress [1] IpAddress, 5338 tcpConnLocalPort [2] Integer64k, 5339 tcpConnRemoteAddress [3] IpAddress, 5340 tcpConnRemotePort [4] Integer64k 5341 } 5343 TcpConnState ::= INTEGER { 5344 closed(1), 5345 listen(2), 5346 synSent(3), 5347 synReceived(4), 5348 established(5), 5349 finWait1(6), 5350 finWait2(7), 5351 DRAFT February, 1994 5353 closeWait(8), 5354 lastAck(9), 5355 closing(10), 5356 timeWait(11), 5357 deleteTCP(12) } 5359 TcpIdValue ::= NULL 5361 TcpRtoAlgorithm ::= INTEGER { 5362 other(1), -- none of the following 5363 constant(2), -- a constant rto 5364 rsre(3), -- MIL-STD-1778, Appendix B 5365 vanj(4) -- Van Jacobsons alg. 5366 } 5368 UdpEntryIdValue ::= SEQUENCE { 5369 udpLocalAddress [1] IpAddress, 5370 udpLocalPort [2] Integer64k 5371 } 5373 UdpIdValue ::= NULL 5375 END 5376 DRAFT February, 1994 5378 3. CONFORMANCE 5380 An implementation claiming conformance to the translated 5381 ISO/CCITT GDMO MIB-II {iimcRFC12131354} shall conform to the 5382 all of the requirements stated in the corresponding MOCS 5383 proforma specified by Annex A. 5385 DRAFT February, 1994 5387 ANNEX A (NORMATIVE): MANAGED OBJECT CONFORMANCE STATEMENTS (MOCS) 5389 This section available only in Postscript Format. 5391 DRAFT February, 1994 5393 ANNEX B: GLOSSARY 5395 ASN.1 Abstract Syntax Notation One 5396 CCITT Consultative Committee on Telephony and Telegraphy 5397 CMIP Common Management Information Protocol 5398 CMIS Common Management Information Service 5399 GDMO Guidelines for the Definition of Managed Objects 5400 GNMP Government Network Management Profile 5401 IIMC ISO/CCITT and Internet Management Coexistence 5402 ISO International Standards Organization 5403 MIB Management Information Base 5404 MOCS Managed Object Conformance Statement 5405 NMF Network Management Forum 5406 OID Object Identifier 5407 OSI Open Systems Interconnection 5408 PDU Protocol Data Unit 5409 RFC Request For Comments 5410 SMI Structure of Management Information 5411 SNMP Simple Network Management Protocol 5412 SNMPv1 Simple Network Management Protocol Version 1 5413 SNMPv2 Simple Network Management Protocol Version 2 5414 TCP/IP Transmission Control Protocol/Internetwork Protocol 5415 DRAFT February, 1994 5417 ANNEX C: REFERENCES 5419 1) CCITT Recommendation X.700, Management Framework 5420 Definition for Open Systems Interconnection (OSI). 5422 ISO/IEC 7498-4: 1989, Information Processing Systems -- 5423 Open Systems Interconnection -Basic Reference Model Part 5424 4 -- Management Framework. 5426 2) ISO/IEC 8824: Information Technology -- Open System 5427 Interconnection -- Specification of Abstract Syntax 5428 Notation One (ASN.1),1990. 5430 3) CCITT Recommendation X.209 (1988), Specification of basic 5431 encoding rules for abstract syntax notation one (ASN.1). 5433 ISO/IEC 8825: 1990, Information Technology -- Open System 5434 Interconnection -- Specification of Basic Encoding Rules 5435 for Abstract Syntax Notation One (ASN.1). 5437 4) CCITT Recommendation X.710, (1991), Common Management 5438 Information Service Definition for CCITT Applications. 5440 ISO/IEC 9595: 1991, Information Technology -- Open System 5441 Interconnection -- Common Management Information Service 5442 Definition. 5444 5) CCITT Recommendation X.711 | ISO/IEC 9596-1: 1991, 5445 Information Technology -- Open Systems Interconnection -- 5446 Common Management Information Protocol -- Part 1: 5447 Specification. 5449 6) CCITT Recommendation X.733 (1992) | ISO/IEC 10164-4: 5450 1992, Information Technology -- Open Systems 5451 Interconnection -- Systems Management -- Part 4: Alarm 5452 Reporting Function. 5454 7) CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1: 5455 1992, Information Technology -- Open Systems 5456 Interconnection -- Structure of Management Information -- 5457 Part 1: Management Information Model. 5459 8) CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2: 5460 1992, Information Technology -- Open Systems 5461 Interconnection -- Structure of Management Information -- 5462 Part 2: Definition of Management Information. 5464 9) CCITT Recommendation X.721 (1992) | ISO/IEC 10165-4: 5465 1992, Information Technology -- Open Systems 5466 Interconnection -- Structure of Management Information -- 5467 Part 4: Guidelines for the Definition of Managed Objects. 5469 DRAFT February, 1994 5471 10) CCITT Recommendation X.723 (1993) | ISO/IEC 10165-6: 5472 1993, Information Technology -- Open Systems 5473 Interconnection -- Structure of Management Information -- 5474 Part 6: Requirements and Guidelines for Implementation 5475 Conformance Statement Proformas associated with OSI 5476 Management. 5478 11) RFC1155, M. Rose and K. McCloghrie, Structure and 5479 Identification of Management Information for TCP/IP based 5480 internets, May 1990. 5482 12) RFC1157, J.D. Case, M.S. Fedor, M.L. Schoffstall,C. 5483 Davin, Simple Network Management Protocol (SNMP), May 5484 1990. 5486 13) RFC1212, M. Rose, K. McCloghrie -- Editors, Concise MIB 5487 Definitions, March 1991. 5489 14) RFC1213, K. McCloghrie and M. Rose -- Editors, 5490 Management Information Base for Network Management of 5491 TCP/IP-based internets: MIB-II, March 1991. 5493 15) RFC1354, F. Baker - Editor, IP Forwarding Table MIB, 5494 July, 1992. 5496 16) RFC1441, J.D. Case, K. McCloghrie, M.T. Rose, 5497 S.L.Waldbusser, Introduction to version 2 of the 5498 Internet-standard Network Management Framework, April 5499 1993. 5501 17) RFC1442, J.D. Case, K. McCloghrie, M.T. Rose, 5502 S.L.Waldbusser, Structure of Management Information for 5503 version 2 of the Simple Network Management Protocol 5504 (SNMPv2), April 1993. 5506 18) RFC1448, J.D. Case, K. McCloghrie, M.T. Rose, 5507 S.L.Waldbusser, Protocol Operations for version 2 of the 5508 Simple Network Management Protocol (SNMPv2), April 1993. 5510 19) Network Management Forum: Forum 026, Translation of 5511 Internet MIBs to ISO/CCITT GDMO MIBs, Issue 1.0, October 5512 1993. 5514 20) Network Management Forum: Forum 028, ISO/CCITT to 5515 Internet Management Proxy, Issue 1.0, 1993. 5517 21) Network Management Forum: Forum 027, ISO/CCITT to 5518 Internet Management Security, Issue 1.0, October 1993. 5520 22) Network Management Forum: Forum 030, Translation of 5521 ISO/CCITT GDMO MIBs to Internet MIBs, Issue 1.0, October 5522 1993. 5524 DRAFT February, 1994 5526 23) NM Forum and X/Open, ISO/CCITT and Internet Management: 5527 Coexistence and Interworking Strategy, Issue 1.0, 5528 October, 1992. 5530 24) Federal Information Processing Standards Publication 5531 179 -- Government Network Management Profile v1.0, 5532 December 1992.