idnits 2.17.1 draft-ietf-entmib-entmib-00.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-03-28) 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (17 November 1995) is 10359 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: 'RFC-1447' on line 468 == Unused Reference: '7' is defined on line 1083, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1442 (ref. '1') (Obsoleted by RFC 1902) ** Downref: Normative reference to an Historic RFC: RFC 1445 (ref. '3') ** Obsolete normative reference: RFC 1448 (ref. '4') (Obsoleted by RFC 1905) ** Downref: Normative reference to an Historic RFC: RFC 1447 (ref. '5') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '6') ** Obsolete normative reference: RFC 1573 (ref. '7') (Obsoleted by RFC 2233) Summary: 16 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Draft Entity MIB November 17 1995 3 Entity MIB 4 6 17 November 1995 8 Keith McCloghrie 9 Cisco Systems Inc. 10 kzm@cisco.com 12 Andy Bierman 13 Bierman Consulting 14 abierman@west.net 16 Status of this Memo 18 This document is an Internet-Draft. Internet-Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its areas, and 20 its working groups. Note that other groups may also distribute working 21 documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet- Drafts as reference material 26 or to cite them other than as ``work in progress.'' 28 To learn the current status of any Internet-Draft, please check the 29 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 30 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 31 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 33 Draft Entity MIB November 17 1995 35 1. Introduction 37 This memo defines an experimental portion of the Management Information 38 Base (MIB) for use with network management protocols in the Internet 39 community. In particular, it describes managed objects used for 40 managing multiple logical entities managed by a single SNMP agent. 42 Draft Entity MIB November 17 1995 44 2. The SNMPv2 Network Management Framework 46 The SNMPv2 Network Management Framework consists of four major 47 components. They are: 49 o RFC 1442 [1] which defines the SMI, the mechanisms used for 50 describing and naming objects for the purpose of management. 52 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 53 objects for the Internet suite of protocols. 55 o RFC 1445 [3] which defines the administrative and other 56 architectural aspects of the framework. 58 o RFC 1448 [4] which defines the protocol used for network access to 59 managed objects. 61 The Framework permits new objects to be defined for the purpose of 62 experimentation and evaluation. 64 2.1. Object Definitions 66 Managed objects are accessed via a virtual information store, termed the 67 Management Information Base or MIB. Objects in the MIB are defined 68 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 69 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 70 an administratively assigned name. The object type together with an 71 object instance serves to uniquely identify a specific instantiation of 72 the object. For human convenience, we often use a textual string, 73 termed the descriptor, to refer to the object type. 75 Draft Entity MIB November 17 1995 77 3. Overview 79 There is a need for a standardized way of representing a single agent 80 which supports multiple instances of one MIB. This is already true for 81 at least 3 standard MIBs, and is likely to become true for more and more 82 MIBs as time passes. For example: 84 - multiple instances of a bridge supported within a single device 85 having a single agent; 87 - multiple repeaters supported by a single agent; 89 - multiple OSPF backbone areas, each one operating as part of its own 90 Autonomous System, and each identified by the same area-id (e.g., 91 0.0.0.0), supported inside a single router with one agent. 93 The fact that it is a single agent in each of these cases implies there 94 is some relationship which binds all of these entities together. 95 Effectively, there is some "overall" physical entity which houses the 96 sum of the things managed by that one agent, i.e., there are multiple 97 "logical" entities within a single physical entity. Sometimes, the 98 overall physical entity contains multiple (smaller) physical entities 99 and each logical entity is associated with a particular such physical 100 entity. Sometimes, the overall physical entity is a "compound" of 101 multiple physical entities (e.g., a stack of stackable hubs). 103 What is needed is a way to determine exactly what logical entities are 104 managed by the agent (either by SNMPv1 or SNMPv2), and thereby to be 105 able to communicate with the agent about a particular logical entity. 106 When different logical entities are associated with different physical 107 entities within the overall physical entity, it is also useful to be 108 able to use this information to distinguish between logical entities. 110 In these situations, there is no need for varbinds for multiple logical 111 entities to be referenced in the same SNMP message (although that might 112 be useful in the future). Rather, it is sufficient, and in some 113 situations preferable, to have the context/community in the message 114 identify the logical entity to which the varbinds apply. 116 3.1. Relationship to Contexts 118 For SNMPv2, in simple scenarios, a SNMPv2 context [5] will correspond 119 directly to a logical entity. However, in the general case, there is a 120 Draft Entity MIB November 17 1995 122 many-to-many correspondence between an entry in the contextTable and an 123 entry in the entLogicalTable. 125 On the one hand, each logical entity is associated with exactly one 126 value of contextLocalEntity. However, it is possible to have multiple 127 logical entities associated with the same value of contextLocalEntity. 128 For example, the logical entities, 'bridge1' and 'repeater1', may be 129 represented in an agent's main context, even though different contexts 130 may be used to represent logical entities 'bridge2' and 'repeater2'. 132 On the other hand, a single value of contextLocalEntity can be 133 associated with multiple contexts (multiple entries in the contextTable) 134 when each has the same value of contextLocalEntity, but a different 135 value of contextLocalTime. 137 3.2. Relationship to Community Strings 139 For SNMPv1, distinguishing between different logical entities is one 140 (but not the only) purpose of the community string [6]. This is 141 accommodated by representing each community string as a logical entity. 143 3.3. Relationship to a Chassis MIB 145 Some readers may recall that a previous IETF working group attempted to 146 define a Chassis MIB. No consensus was reached by that working group, 147 possibly because its scope was too broad. As such, it is not the 148 purpose of this MIB to be a "Chassis MIB replacement", nor is it within 149 the scope of this MIB to contain all the information which might be 150 necessary to manage a "chassis". On the other hand, the entities 151 represented by an implementation of this MIB might well be contained in 152 a chassis. 154 3.4. Relationship to the Interfaces MIB 156 The Entity MIB contains a mapping table identifying physical components 157 that have 'external values' (e.g. ifIndex) associated with them within a 158 given context. This table can be used to identify the physical location 159 of each interface in the ifTable. Since ifIndex values in different 160 contexts are not related to one another, the interface to physical 161 component associations are relative to a specific logical entity within 162 Draft Entity MIB November 17 1995 164 the agent. 166 3.5. Relationship to the Other MIBs 168 The Entity MIB contains a mapping table identifying physical components 169 that have identifiers from other standard MIBs associated with them. 170 For example, this table can be used along with the physical mapping 171 table to identify the physical location of each repeater port in the 172 rptrPortTable, each bridge port in the dot1dBasePortTable, or each 173 ifIndex in the ifTable. 175 3.6. Re-Configuration of Entities 177 All the MIB objects defined in this MIB have at most a read-only MAX- 178 ACCESS clause, i.e., none are write-able. This is another conscious 179 decision by the authors to limit this MIB's scope. It is possible that 180 this restriction could be lifted after implementation experience. 182 3.7. MIB Structure 184 This MIB contains four tables: the entPhysicalTable and the 185 entLogicalTable each provide a list of entities. The entLPMappingTable 186 provides mappings between logical and physical entities. The 187 entAliasMappingTable provides mappings between physical components and 188 associated identifiers from other MIBs. For example, a physical repeater 189 port may be associated with an instance of 'rptrPortGroupIndex.1.5', or 190 'ifIndex.12', or both. 192 The entPhysicalTable contains one row per physical entity, and should 193 always contains at least one row for an "overall" physical entity. Each 194 row is indexed by an arbitrary, small integer, and contains a 195 description and type of the physical entity. It also optionally 196 contains the index number of another row in the same table indicating a 197 containment relationship between the two. 199 The entLogicalTable contains one row per logical entity. Each row is 200 indexed by an arbitrary, small integer and contains a name, description, 201 and type of the logical entity. It also contains information to allow 202 SNMPv2 and/or SNMPv1 access to the MIB information for the logical 203 Draft Entity MIB November 17 1995 205 entity. 207 The entLPMappingTable contains mappings between entLogicalIndex values 208 (logical entities) and entPhysicalIndex values (the physical components 209 supporting that entity). A logical entity can map to more than one 210 physical component, and more than one logical entity can map to (share) 211 the same physical component. 213 The entAliasMappingTable contains mappings between entPhysicalIndex, 214 entLogicalIndex pairs and 'alias' object identifier values. This allows 215 resources managed with other MIBs (e.g. repeater ports, bridge ports, 216 physical and logical interfaces) to be identified in the physical entity 217 hierarchy. 219 3.8. Multiple Agents 221 Even though a primary motivation for this MIB is to represent the 222 multiple logical entities supported by a single agent, it is also 223 possible to use it to represent multiple logical entities supported by 224 multiple agents (in the same "overall" physical entity). Indeed, it is 225 implicit in the SNMP architecture, that the number of agents is 226 transparent to a network management station. 228 Draft Entity MIB November 17 1995 230 4. Definitions 232 ENTITY-MIB DEFINITIONS ::= BEGIN 234 IMPORTS 235 MODULE-IDENTITY, OBJECT-TYPE, experimental, 236 IpAddress 237 FROM SNMPv2-SMI 238 DisplayString, AutonomousType, TruthValue 239 FROM SNMPv2-TC 240 Context 241 FROM SNMPv2-PARTY-MIB 242 MODULE-COMPLIANCE, OBJECT-GROUP 243 FROM SNMPv2-CONF; 245 entityMIB MODULE-IDENTITY 246 LAST-UPDATED "9511170000Z" 247 ORGANIZATION "IETF ENTMIB Working Group" 248 CONTACT-INFO 249 " Keith McCloghrie 250 Cisco Systems Inc. 251 170 West Tasman Drive 252 San Jose, CA 95134 253 408-526-5260 254 kzm@cisco.com 256 Andy Bierman 257 Bierman Consulting 258 1200 Sagamore Lane 259 Ventura, CA 93001 260 805-648-2028 261 abierman@west.net" 262 DESCRIPTION 263 "The MIB module for representing multiple logical 264 entities supported by a single SNMP agent." 265 ::= { experimental xx } 267 entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 } 268 Draft Entity MIB November 17 1995 270 -- The Physical Entity Table 272 entPhysicalTable OBJECT-TYPE 273 SYNTAX SEQUENCE OF EntPhysicalEntry 274 MAX-ACCESS not-accessible 275 STATUS current 276 DESCRIPTION 277 "This table contains one row per physical entity. There is 278 always at least one row for an 'overall' physical entity." 279 ::= { entityMIBObjects 1 } 281 entPhysicalEntry OBJECT-TYPE 282 SYNTAX EntPhysicalEntry 283 MAX-ACCESS not-accessible 284 STATUS current 285 DESCRIPTION 286 "Information about a particular physical entity. An agent 287 is expected to represent physical components in as much 288 detail as possible. If more than one agent within a chassis 289 implements the Entity MIB, the information retrieved from 290 each agent must be consistent, but not necessarily 291 identical." 292 INDEX { entPhysicalIndex } 293 ::= { entPhysicalTable 1 } 295 EntPhysicalEntry ::= SEQUENCE { 296 entPhysicalIndex INTEGER, 297 entPhysicalDescr DisplayString, 298 entPhysicalVendorType AutonomousType, 299 entPhysicalContainedIn INTEGER, 300 entPhysicalIsRemovable TruthValue, 301 entPhysicalClass AutonomousType 302 } 304 entPhysicalIndex OBJECT-TYPE 305 SYNTAX INTEGER (1..2147483647) 306 MAX-ACCESS not-accessible 307 STATUS current 308 DESCRIPTION 309 "The value of this object uniquely identifies the physical 310 entity. The value is a small positive integer; index values 311 for different physical entities are not necessarily 312 contiguous." 313 ::= { entPhysicalEntry 1 } 315 Draft Entity MIB November 17 1995 317 entPhysicalDescr OBJECT-TYPE 318 SYNTAX DisplayString 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "A textual description of physical entity." 323 ::= { entPhysicalEntry 2 } 325 entPhysicalVendorType OBJECT-TYPE 326 SYNTAX AutonomousType 327 MAX-ACCESS read-only 328 STATUS current 329 DESCRIPTION 330 "An indication of the vendor-specific hardware type of the 331 physical entity. Note that this is different from the 332 definition of MIB-II's sysObjectID. 334 An agent should set this object to a enterprise-specific 335 registration identifier value indicating the specific 336 equipment type in detail. The associated instance of the 337 entPhysicalClass object should be used to indicate the 338 general type of hardware device. 340 If no vendor-specific registration identifier exists for 341 this physical entity, then the value { 0 0 } is returned. If 342 the value is unknown by this agent, then the special value 343 'entPClassUnknown' is returned." 344 ::= { entPhysicalEntry 3 } 346 entPhysicalContainedIn OBJECT-TYPE 347 SYNTAX INTEGER (0..2147483647) 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The value of entPhysicalIndex for the physical entity which 352 'contains' this physical entity. A value of zero indicates 353 this physical entity is not contained in any other physical 354 entity. Note that the set of 'containment' relationships 355 define a strict hierarchy; that is, recursion is not 356 allowed." 357 ::= { entPhysicalEntry 4 } 359 entPhysicalIsRemovable OBJECT-TYPE 360 SYNTAX TruthValue 361 MAX-ACCESS read-only 363 Draft Entity MIB November 17 1995 365 STATUS current 366 DESCRIPTION 367 "An indication of the physical characteristics of specified 368 component. A value of 'true(1)' indicates that this 369 entPhysicalEntry represents a field-replaceable unit. A 370 value of 'false(2)' indicates a physical component that 371 cannot be replaced by a user or equipment installer." 372 ::= { entPhysicalEntry 5 } 374 entPhysicalClass OBJECT-TYPE 375 SYNTAX AutonomousType 376 MAX-ACCESS read-only 377 STATUS current 378 DESCRIPTION 379 "An indication of the general hardware type of the physical 380 entity. 382 An agent should set this object to a standard registration 383 identifier value (from the entPClassTypes sub-tree) which 384 most accurately indicates the general class of the physical 385 entity. 387 If no appropriate standard registration identifier exists 388 for this physical entity, then the value { 0 0 } is 389 returned. If the value is unknown by this agent, then the 390 special value 'entPClassUnknown' is returned." 391 ::= { entPhysicalEntry 6 } 393 Draft Entity MIB November 17 1995 395 -- The Logical Entity Table 396 entLogicalTable OBJECT-TYPE 397 SYNTAX SEQUENCE OF EntLogicalEntry 398 MAX-ACCESS not-accessible 399 STATUS current 400 DESCRIPTION 401 "This table contains one row per logical entity." 402 ::= { entityMIBObjects 2 } 404 entLogicalEntry OBJECT-TYPE 405 SYNTAX EntLogicalEntry 406 MAX-ACCESS not-accessible 407 STATUS current 408 DESCRIPTION 409 "Information about a particular logical entity. Entities 410 may be managed by this agent or other SNMP agents (possibly) 411 in the same chassis." 412 INDEX { entLogicalIndex } 413 ::= { entLogicalTable 1 } 415 EntLogicalEntry ::= SEQUENCE { 416 entLogicalIndex INTEGER, 417 entLogicalDescr DisplayString, 418 entLogicalType AutonomousType, 419 entLogicalLocalEntityName OCTET STRING, 420 entLogicalContext Context, 421 entLogicalCommunity OCTET STRING, 422 entLogicalIpAddress IpAddress 423 } 425 entLogicalIndex OBJECT-TYPE 426 SYNTAX INTEGER (1..2147483647) 427 MAX-ACCESS not-accessible 428 STATUS current 429 DESCRIPTION 430 "The value of this object uniquely identifies the logical 431 entity. The value is a small positive integer; index values 432 for different logical entities are are not necessarily 433 contiguous." 434 ::= { entLogicalEntry 1 } 436 Draft Entity MIB November 17 1995 438 entLogicalDescr OBJECT-TYPE 439 SYNTAX DisplayString 440 MAX-ACCESS read-only 441 STATUS current 442 DESCRIPTION 443 "A textual description of logical entity." 444 ::= { entLogicalEntry 2 } 446 entLogicalType OBJECT-TYPE 447 SYNTAX AutonomousType 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "An indication of the type of logical entity. This will 452 typically be the OBJECT IDENTIFIER name of the node in the 453 SMI's naming hierarchy which represents the major MIB 454 module, or the majority of the MIB modules, supported by the 455 logical entity. For example: 456 a logical entity of a regular host/router -> mib-2 457 a logical entity of a 802.1d bridge -> dot1dBridge 458 a logical entity of a 802.3 repeater -> 459 snmpDot3RptrMgmt" 460 ::= { entLogicalEntry 3 } 462 entLogicalLocalEntityName OBJECT-TYPE 463 SYNTAX OCTET STRING (SIZE(0..255)) 464 MAX-ACCESS read-only 465 STATUS current 466 DESCRIPTION 467 "A name associated with the logical entity. This name and 468 the SNMPv2 contextLocalEntity [RFC-1447] for the 469 corresponding local context have the same value. Note that 470 multiple contexts may have the same value of 471 contextLocalEntity, each having a different value of 472 contextLocalTime. 474 A conformant SNMPv2 agent may wish to conserve contexts by 475 representing multiple logical entities in a single 'main' 476 context. This is possible when the logical entities 477 represented by the same value of contextLocalEntity have no 478 object instances in common. For example, 'bridge1' and 479 'repeater1' may be part of the main context, but two 480 additional entries are needed to represent 'bridge2' and 481 'repeater2'. 483 Draft Entity MIB November 17 1995 485 Logical entities 'bridge1' and 'repeater1' would be 486 represented by sysOREntries associated with the 'main' 487 context. 489 For agents not accessible via SNMPv2, the value of this 490 object is the empty string." 491 ::= { entLogicalEntry 4 } 493 entLogicalContext OBJECT-TYPE 494 SYNTAX Context 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "An SNMPv2 context containing detailed management 499 information for this logical entity. If more than one 500 context is associated with this logical entity, then the 501 agent should choose a 'primary' context for the logical 502 entity; e.g. the context whose associated value of 503 contextLocalTime is equal to 'currentTime'. 505 Other contexts (for different values of contextLocalTime) 506 may be derived from the entLogicalLocalEntityName according 507 to whatever conventions are used for context naming. 509 For agents not accessible via SNMPv2, this object would have 510 the value 0.0. 512 [TBD 1: the issue of which Parties to use along with this 513 context is considered beyond the scope of the Entity MIB. 514 TBD 2: this part of the entLogicalTable will change to 515 reflect the new SNMPv2 administrative model.] " 516 ::= { entLogicalEntry 5 } 518 entLogicalCommunity OBJECT-TYPE 519 SYNTAX OCTET STRING 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION 523 "A SNMPv1 community-string which can be used to access 524 detailed management information for this logical entity. 525 The agent should allow read access with this community 526 string (to an appropriate subset of all managed objects) and 527 may also choose to return a community string based on the 528 privileges of the request used to read this object (e.g. 529 only return a string having read-write privileges when 531 Draft Entity MIB November 17 1995 533 accessed with read-write privileges). 535 For agents not accessible via SNMPv1, the value of this 536 object is the empty-string." 537 ::= { entLogicalEntry 6 } 539 entLogicalIpAddress OBJECT-TYPE 540 SYNTAX IpAddress 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 "The IP-address of the SNMPv1 agent from which detailed 545 management information for this logical entity can be 546 obtained. For agents not accessible via SNMPv1, the value 547 of this object is 0.0.0.0." 548 ::= { entLogicalEntry 7 } 550 Draft Entity MIB November 17 1995 552 -- entLPMappingTable: for each entity index, there are N 553 -- rows, each representing a physical component 554 -- that is associated with the indicated entity 555 -- 556 -- entity to component table 557 entLPMappingTable OBJECT-TYPE 558 SYNTAX SEQUENCE OF EntLPMappingEntry 559 MAX-ACCESS not-accessible 560 STATUS current 561 DESCRIPTION 562 "This table contains zero or more rows of logical entity to 563 physical equipment associations." 564 ::= { entityMIBObjects 3 } 566 entLPMappingEntry OBJECT-TYPE 567 SYNTAX EntLPMappingEntry 568 MAX-ACCESS not-accessible 569 STATUS current 570 DESCRIPTION 571 "Information about a particular logical entity to physical 572 equipment binding." 573 INDEX { entLogicalIndex, entLPPhysicalIndex } 574 ::= { entLPMappingTable 1 } 576 EntLPMappingEntry ::= SEQUENCE { 577 entLPPhysicalIndex INTEGER 578 } 580 entLPPhysicalIndex OBJECT-TYPE 581 SYNTAX INTEGER (1..2147483647) 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "The value of this object identifies a particular 586 entPhysicalEntry associated with the indicated 587 entLogicalEntity." 588 ::= { entLPMappingEntry 1 } 590 Draft Entity MIB November 17 1995 592 -- logical entity/component to alias table 593 entAliasMappingTable OBJECT-TYPE 594 SYNTAX SEQUENCE OF EntAliasMappingEntry 595 MAX-ACCESS not-accessible 596 STATUS current 597 DESCRIPTION 598 "This table contains zero or more rows of logical entity, 599 and physical component to external identifier associations." 600 ::= { entityMIBObjects 4 } 602 entAliasMappingEntry OBJECT-TYPE 603 SYNTAX EntAliasMappingEntry 604 MAX-ACCESS not-accessible 605 STATUS current 606 DESCRIPTION 607 "Information about a particular physical equipment, logical 608 entity to external identifier binding. Note that the same 609 physical component-logical entity pair may have an arbitrary 610 number of external identifier (alias) bindings." 611 INDEX { entPhysicalIndex, entLogicalIndex, entAliasMappingIndex } 612 ::= { entAliasMappingTable 1 } 614 EntAliasMappingEntry ::= SEQUENCE { 615 entAliasMappingIndex INTEGER, 616 entAliasIdentifier OBJECT IDENTIFIER 617 } 619 entAliasMappingIndex OBJECT-TYPE 620 SYNTAX INTEGER (1..2147483647) 621 MAX-ACCESS not-accessible 622 STATUS current 623 DESCRIPTION 624 "The value of this object uniquely identifies the particular 625 binding for a specific logical entity on a particular 626 physical component. The value is a small positive integer; 627 index values for different entAlias mappings are not 628 necessarily contiguous." 629 ::= { entAliasMappingEntry 1 } 631 entAliasIdentifier OBJECT-TYPE 632 SYNTAX OBJECT IDENTIFIER 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "The value of this object identifies a particular MIB 638 Draft Entity MIB November 17 1995 640 instance associated with the indicated entPhysicalEntry and 641 entLogicalEntry pair. 643 For example, suppose a physical port was represented by 644 entPhysicalEntry.3, and entLogicalEntry.1 existed for a 645 repeater, entLogicalEntry.2 existed for a bridge, and the 646 bridge port was also represented in the ifTable. Then there 647 might be three associated instances of entAliasIdentifier: 648 entAliasIdentifier.3.1.1 == rptrPortGroupIndex.5.2 649 entAliasIdentifier.3.2.1 == dot1dBasePort.2 650 entAliasIdentifier.3.2.2 == ifIndex.2 " 651 ::= { entAliasMappingEntry 2 } 653 Draft Entity MIB November 17 1995 655 -- standard OBJECT IDENTIFIER values for entPhysicalClass 656 -- 657 -- this section needs a lot of work 658 -- the following identifiers are intended to be a 659 -- starting point for WG discussion, and should not be 660 -- considered complete 661 -- 662 entPClassTypes OBJECT IDENTIFIER ::= { entityMIBObjects 5 } 664 entPClassUnknown OBJECT IDENTIFIER ::= { entPClassTypes 1 } 666 entPClassChassis OBJECT IDENTIFIER ::= { entPClassTypes 2 } 668 entPClassBackplanes OBJECT IDENTIFIER ::= { entPClassTypes 3 } 670 entPClassNetBackplane OBJECT IDENTIFIER ::= { entPClassBackplanes 1 } 672 entPClassPowerBackplane OBJECT IDENTIFIER ::= { entPClassBackplanes 2 } 674 entPClassSlot OBJECT IDENTIFIER ::= { entPClassTypes 4 } 676 entPClassPowerSupply OBJECT IDENTIFIER ::= { entPClassTypes 5 } 678 entPClassFan OBJECT IDENTIFIER ::= { entPClassTypes 6 } 680 entPClassSensors OBJECT IDENTIFIER ::= { entPClassTypes 7 } 682 entPClassTempSensor OBJECT IDENTIFIER ::= { entPClassSensors 1 } 684 entPClassGenModules OBJECT IDENTIFIER ::= { entPClassTypes 8 } 686 entPClassNetModules OBJECT IDENTIFIER ::= { entPClassTypes 9 } 688 entPClassNetRepeater OBJECT IDENTIFIER ::= { entPClassNetModules 1 } 690 entPClassNetRouter OBJECT IDENTIFIER ::= { entPClassNetModules 2 } 692 entPClassNetBridge OBJECT IDENTIFIER ::= { entPClassNetModules 3 } 694 entPClassTermServer OBJECT IDENTIFIER ::= { entPClassNetModules 4 } 696 entPClassPort OBJECT IDENTIFIER ::= { entPClassTypes 10 } 697 Draft Entity MIB November 17 1995 699 -- conformance information 701 entityConformance OBJECT IDENTIFIER ::= { entityMIB 2 } 703 entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 } 704 entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 } 706 -- compliance statements 708 entityCompliance MODULE-COMPLIANCE 709 STATUS current 710 DESCRIPTION 711 "The compliance statement for SNMPv2 entities 712 which implement the Entity MIB." 713 MODULE -- this module 714 MANDATORY-GROUPS { entityGroup } 715 ::= { entityCompliances 1 } 717 -- units of conformance 719 entityGroup OBJECT-GROUP 720 OBJECTS { entPhysicalDescr, entPhysicalVendorType, 721 entPhysicalContainedIn, entPhysicalIsRemovable, 722 entPhysicalClass, 723 entLogicalDescr, entLogicalType, 724 entLogicalLocalEntityName, entLogicalContext, 725 entLogicalCommunity, entLogicalIpAddress, 726 entLPPhysicalIndex, entAliasIdentifier 727 } 728 STATUS current 729 DESCRIPTION 730 "The collection of objects which are used to 731 represent the multiple logical entities, 732 physical components, interfaces, and port 733 alias identifiers for which a single agent 734 provides MIB information." 735 ::= { entityGroups 1 } 737 END 738 Draft Entity MIB November 17 1995 740 5. Usage Examples 742 5.1. Router/Bridge 744 A bi-lingual (SNMPv1 and SNMPv2) router containing two slots. Each slot 745 contains a 3 port router/bridge module. Each port is represented in the 746 ifTable. There are two logical instances of OSPF running and two 747 logical bridges: 749 Physical entities -- entPhysicalTable: 750 1 Field-replaceable physical chassis: 751 entPhysicalDescr.1 == "Acme Chassis Model 100" 752 entPhysicalVendorType.1 == acmeProducts.chassisTypes.1 753 entPhysicalContainedIn.1 == 0 754 entPhysicalIsRemovable.1 == true(1) 755 entPhysicalClass.1 == entPClassChassis 757 2 slots within the chassis: 758 entPhysicalDescr.2 == "Acme Router Chassis Slot 1" 759 entPhysicalVendorType.2 == acmeProducts.slotTypes.1 760 entPhysicalContainedIn.2 == 1 761 entPhysicalIsRemovable.2 == false(2) 762 entPhysicalClass.2 == entPClassSlot 764 entPhysicalDescr.3 == "Acme Router Chassis Slot 2" 765 entPhysicalVendorType.3 == acmeProducts.slotTypes.1 766 entPhysicalContainedIn.3 == 1 767 entPhysicalIsRemovable.3 == false(2) 768 entPhysicalClass.3 == entPClassSlot 770 2 Field-replaceable modules: 771 Slot 1 contains a module with 3 ports: 772 entPhysicalDescr.4 == "Acme Router Module Model 10" 773 entPhysicalVendorType.4 == acmeProducts.moduleTypes.14 774 entPhysicalContainedIn.4 == 2 775 entPhysicalIsRemovable.4 == true(1) 776 entPhysicalClass.4 == entPClassNetRouter 778 entPhysicalDescr.5 == "Acme Router Ethernet Port 1" 779 entPhysicalVendorType.5 == acmeProducts.portTypes.2 780 entPhysicalContainedIn.5 == 4 781 entPhysicalIsRemovable.5 == false(2) 782 entPhysicalClass.5 == entPClassPort 784 Draft Entity MIB November 17 1995 786 entPhysicalDescr.6 == "Acme Router Ethernet Port 2" 787 entPhysicalVendorType.6 == acmeProducts.portTypes.2 788 entPhysicalContainedIn.6 == 4 789 entPhysicalIsRemovable.6 == false(2) 790 entPhysicalClass.6 == entPClassPort 792 entPhysicalDescr.7 == "Acme Router Fddi Port 3" 793 entPhysicalVendorType.7 == acmeProducts.portTypes.3 794 entPhysicalContainedIn.7 == 4 795 entPhysicalIsRemovable.7 == false(2) 796 entPhysicalClass.7 == entPClassPort 798 Slot 2 contains another 3-port module: 799 entPhysicalDescr.8 == "Acme Router Module Model 11" 800 entPhysicalVendorType.8 == acmeProducts.moduleTypes.15 801 entPhysicalContainedIn.8 == 3 802 entPhysicalIsRemovable.8 == true(1) 803 entPhysicalClass.8 == entPClassNetRouter 805 entPhysicalDescr.9 == "Acme Router Fddi Port 1" 806 entPhysicalVendorType.9 == acmeProducts.portTypes.3 807 entPhysicalContainedIn.9 == 8 808 entPhysicalIsRemovable.9 == false(2) 809 entPhysicalClass.9 == entPClassPort 811 entPhysicalDescr.10 == "Acme Router Ethernet Port 2" 812 entPhysicalVendorType.10 == acmeProducts.portTypes.2 813 entPhysicalContainedIn.10 == 8 814 entPhysicalIsRemovable.10 == false(2) 815 entPhysicalClass.10 == entPClassPort 817 entPhysicalDescr.11 == "Acme Router Ethernet Port 3" 818 entPhysicalVendorType.11 == acmeProducts.portTypes.2 819 entPhysicalContainedIn.11 == 8 820 entPhysicalIsRemovable.11 == false(2) 821 entPhysicalClass.11 == entPClassPort 823 Logical entities -- entLogicalTable 824 2 OSPF instances: 825 entLogicalDescr.1 == "ospf-1" 826 entLogicalType.1 == ospf 827 entLogicalLocalEntityName.1 == "wan-gwty" 828 entLogicalContext.1 == { initialContextId 829 124 125 126 127 10 } 830 entLogicalCommunity.1 == "public-ospf1" 832 Draft Entity MIB November 17 1995 834 entLogicalIpAddress.1 == 124.125.126.127 836 entLogicalDescr.2 == "ospf-2" 837 entLogicalType.2 == ospf 838 entLogicalLocalEntityName.2 == "wan-gwty-ospf2" 839 entLogicalContext.2 == { initialContextId 840 124 125 126 127 11 } 841 entLogicalCommunity.2 == "public-ospf2" 842 entLogicalIpAddress.2 == 124.125.126.127 844 2 logical bridges: 845 entLogicalDescr.3 == "bridge1" 846 entLogicalType.3 == dod1dBridge 847 entLogicalLocalEntityName.3 == "wan-gwty-bridge1" 848 entLogicalContext.3 == { initialContextId 849 124 125 126 127 101 } 850 entLogicalCommunity.3 == "public-bridge1" 851 entLogicalIpAddress.3 == 124.125.126.127 853 entLogicalDescr.4 == "bridge2" 854 entLogicalType.4 == dod1dBridge 855 entLogicalLocalEntityName.4 == "wan-gwty-bridge2" 856 entLogicalContext.4 == { initialContextId 857 124 125 126 127 102 } 858 entLogicalCommunity.4 == "public-bridge2" 859 entLogicalIpAddress.4 == 124.125.126.127 861 Logical to Physical Mappings: 862 1st OSPF instance: uses module 1-port 1 863 entLPPhysicalIndex.1.5 == 5 865 2nd OSPF instance: uses module 2-port 1 866 entLPPhysicalIndex.2.9 == 9 868 1st bridge group: uses module 1, all ports 869 entLPPhysicalIndex.3.5 == 5 870 entLPPhysicalIndex.3.6 == 6 871 entLPPhysicalIndex.3.7 == 7 873 2nd bridge group: uses module 2, all ports 874 entLPPhysicalIndex.4.9 == 9 875 entLPPhysicalIndex.4.10 == 10 876 entLPPhysicalIndex.4.11 == 11 878 Physical/Logical to Alias Mappings -- entAliasMappingTable: 880 Draft Entity MIB November 17 1995 882 Bridge 1 uses Ports 1..3 on Slot 1 883 entAliasIdentifier.5.3.1 == dot1dBasePort.1 884 entAliasIdentifier.5.3.2 == ifIndex.1 885 entAliasIdentifier.6.3.1 == dot1dBasePort.2 886 entAliasIdentifier.6.3.2 == ifIndex.2 887 entAliasIdentifier.7.3.1 == dot1dBasePort.3 888 entAliasIdentifier.7.3.2 == ifIndex.3 889 Bridge 2 uses Ports 1..3 on Slot 2; uses same Bridge MIB and ifIndex 890 values as Bridge 1, but in a different context, and representing 891 different physical ports: 892 entAliasIdentifier.9.4.1 == dot1dBasePort.1 893 entAliasIdentifier.9.4.2 == ifIndex.1 894 entAliasIdentifier.10.4.1 == dot1dBasePort.2 895 entAliasIdentifier.10.4.2 == ifIndex.2 896 entAliasIdentifier.11.4.1 == dot1dBasePort.3 897 entAliasIdentifier.11.4.2 == ifIndex.3 899 5.2. Repeaters 901 An SNMPv1 only, 3-slot Hub with 2 backplane ethernet segments. Slot 902 three is empty, and the remaining slots contain ethernet repeater 903 modules. 905 Physical entities -- entPhysicalTable: 906 1 Field-replaceable physical chassis: 907 entPhysicalDescr.1 == "Acme Repeater Chassis Model 110" 908 entPhysicalVendorType.1 == acmeProducts.chassisTypes.2 909 entPhysicalContainedIn.1 == 0 910 entPhysicalIsRemovable.1 == true(1) 911 entPhysicalClass.1 == entPClassChassis 913 2 Chassis Ethernet Backplanes: 914 entPhysicalDescr.2 == "Ethernet Backplane 1" 915 entPhysicalVendorType.2 == acmeProducts.backplaneTypes.1 916 entPhysicalContainedIn.2 == 1 917 entPhysicalIsRemovable.2 == false(2) 918 entPhysicalClass.2 == entPClassNetBackplane 920 entPhysicalDescr.3 == "Ethernet Backplane 2" 921 entPhysicalVendorType.3 == acmeProducts.backplaneTypes.1 922 entPhysicalContainedIn.3 == 1 923 entPhysicalIsRemovable.3 == false(2) 924 entPhysicalClass.3 == entPClassNetBackplane 926 Draft Entity MIB November 17 1995 928 3 slots within the chassis: 929 entPhysicalDescr.4 == "Acme Hub Slot 1" 930 entPhysicalVendorType.4 == acmeProducts.slotTypes.5 931 entPhysicalContainedIn.4 == 1 932 entPhysicalIsRemovable.4 == false(2) 933 entPhysicalClass.4 == entPClassSlot 935 entPhysicalDescr.5 == "Acme Hub Slot 2" 936 entPhysicalVendorType.5 == acmeProducts.slotTypes.5 937 entPhysicalContainedIn.5 == 1 938 entPhysicalIsRemovable.5 == false(2) 939 entPhysicalClass.5 == entPClassSlot 941 entPhysicalDescr.6 == "Acme Hub Slot 3" 942 entPhysicalVendorType.6 == acmeProducts.slotTypes.5 943 entPhysicalContainedIn.6 == 1 944 entPhysicalIsRemovable.6 == false(2) 945 entPhysicalClass.6 == entPClassSlot 947 Slot 1 contains a plug-in module with 4 10-BaseT ports: 948 entPhysicalDescr.7 == "10Base-T Module Model 14" 949 entPhysicalVendorType.7 == acmeProducts.moduleTypes.32 950 entPhysicalContainedIn.7 == 4 951 entPhysicalIsRemovable.7 == true(1) 952 entPhysicalClass.7 == entPClassNetRepeater 954 entPhysicalDescr.8 == "10Base-T Port 1" 955 entPhysicalVendorType.8 == acmeProducts.portTypes.10 956 entPhysicalContainedIn.8 == 7 957 entPhysicalIsRemovable.8 == false(2) 958 entPhysicalClass.8 == entPClassPort 960 entPhysicalDescr.9 == "10Base-T Port 2" 961 entPhysicalVendorType.9 == acmeProducts.portTypes.10 962 entPhysicalContainedIn.9 == 7 963 entPhysicalIsRemovable.9 == false(2) 964 entPhysicalClass.9 == entPClassPort 966 entPhysicalDescr.10 == "10Base-T Port 3" 967 entPhysicalVendorType.10 == acmeProducts.portTypes.10 968 entPhysicalContainedIn.10 == 7 969 entPhysicalIsRemovable.10 == false(2) 970 entPhysicalClass.10 == entPClassPort 972 entPhysicalDescr.11 == "10Base-T Port 4" 974 Draft Entity MIB November 17 1995 976 entPhysicalVendorType.11 == acmeProducts.portTypes.10 977 entPhysicalContainedIn.11 == 7 978 entPhysicalIsRemovable.11 == false(2) 979 entPhysicalClass.11 == entPClassPort 981 Slot 2 contains another ethernet module with 2 ports. 982 entPhysicalDescr.12 == "Acme 10Base-T Module Model 4" 983 entPhysicalVendorType.12 == acmeProducts.moduleTypes.30 984 entPhysicalContainedIn.12 = 5 985 entPhysicalIsRemovable.12 = true(1) 986 entPhysicalClass.12 == entPClassNetRepeater 988 entPhysicalDescr.13 == "802.3 AUI Port 1" 989 entPhysicalVendorType.13 == acmeProducts.portTypes.11 990 entPhysicalContainedIn.13 == 5 991 entPhysicalIsRemovable.13 == false(2) 992 entPhysicalClass.13 == entPClassPort 994 entPhysicalDescr.14 == "10Base-T Port 2" 995 entPhysicalVendorType.14 == acmeProducts.portTypes.10 996 entPhysicalContainedIn.14 == 5 997 entPhysicalIsRemovable.14 == false(2) 998 entPhysicalClass.14 == entPClassPort 1000 Logical entities -- entLogicalTable 1001 Repeater 1--comprised of any ports attached to backplane 1 1002 entLogicalDescr.1 == "repeater1" 1003 entLogicalType.1 == snmpDot3RptrMgt 1004 entLogicalLocalEntityName.1 == "" 1005 entLogicalContext.1 == { 0.0 } 1006 entLogicalCommunity.1 "public-repeater1" 1007 entLogicalIpAddress.1 124.125.126.128 1009 Repeater 2--comprised of any ports attached to backplane 2: 1010 entLogicalDescr.2 == "repeater2" 1011 entLogicalType.2 == snmpDot3RptrMgt 1012 entLogicalLocalEntityName.2 == "" 1013 entLogicalContext.2 == { 0.0 } 1014 entLogicalCommunity.2 == "public-repeater2" 1015 entLogicalIpAddress.2 == 124.125.126.128 1017 Logical to Physical Mappings -- entLPMappingTable: 1019 repeater1 uses backplane 1, slot 1-ports 1 & 2, slot 2-port 1 1020 entLPPhysicalIndex.1.2 == 2 1022 Draft Entity MIB November 17 1995 1024 entLPPhysicalIndex.1.8 == 8 1025 entLPPhysicalIndex.1.9 == 9 1026 entLPPhysicalIndex.1.13 == 13 1028 repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2 1029 entLPPhysicalIndex.2.3 == 3 1030 entLPPhysicalIndex.2.10 == 10 1031 entLPPhysicalIndex.2.11 == 11 1032 entLPPhysicalIndex.2.14 == 14 1034 Physical/Logical to Alias Mappings -- entAliasMappingTable: 1035 repeater1 uses slot 1-ports 1 & 2, slot 2-port 1 1036 entAliasIdentifier.8.1.1 == rptrPortGroupIndex.1.1 1037 entAliasIdentifier.9.1.1 == rptrPortGroupIndex.1.2 1038 entAliasIdentifier.13.1.1 == rptrPortGroupIndex.2.1 1040 repeater2 uses slot 1-ports 3 & 4, slot 2-port 2 1041 entAliasIdentifier.10.2.1 == rptrPortGroupIndex.1.3 1042 entAliasIdentifier.11.2.1 == rptrPortGroupIndex.1.4 1043 entAliasIdentifier.14.2.1 == rptrPortGroupIndex.2.2 1045 Draft Entity MIB November 17 1995 1047 6. Acknowledgements 1049 This document was produced by the IETF Entity MIB Working Group. 1051 Draft Entity MIB November 17 1995 1053 7. References 1055 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 1056 of Management Information for version 2 of the Simple Network 1057 Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes 1058 LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon 1059 University, April 1993. 1061 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1062 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1063 RFC 1213, Hughes LAN Systems, Performance Systems International, 1064 March 1991. 1066 [3] Galvin, J., and K. McCloghrie, "Administrative Model for version 2 1067 of the Simple Network Management Protocol (SNMPv2)", RFC 1445, 1068 Trusted Information Systems, Hughes LAN Systems, April 1993. 1070 [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1071 Operations for version 2 of the Simple Network Management Protocol 1072 (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes LAN Systems, Dover 1073 Beach Consulting, Inc., Carnegie Mellon University, April 1993. 1075 [5] McCloghrie, K., and J. Galvin, "Party MIB for Version 2 of the 1076 Simple Network Management Protocol (SNMPv2)", RFC 1447, Hughes LAN 1077 Systems, Trusted Information Systems, April 1993. 1079 [6] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1080 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1081 International, MIT Laboratory for Computer Science, May 1990. 1083 [7] McCloghrie, K., and Kastenholtz, F., "Interfaces Group Evolution", 1084 RFC 1573, Hughes LAN Systems, FTP Software, January 1994. 1086 Draft Entity MIB November 17 1995 1088 8. Security Considerations 1090 Security issues are not discussed in this memo. 1092 9. Authors' Addresses 1094 Keith McCloghrie 1095 cisco Systems, Inc. 1096 170 West Tasman Drive 1097 San Jose, CA 95134 1098 Phone: 408-526-5260 1099 Email: kzm@cisco.com 1101 Andy Bierman 1102 Bierman Consulting 1103 1200 Sagamore Lane 1104 Ventura, CA 93001 1105 Phone: 805-648-2028 1106 Email: abierman@west.net 1108 Draft Entity MIB November 17 1995 1110 Table of Contents 1112 1 Introduction .................................................... 2 1113 2 The SNMPv2 Network Management Framework ......................... 3 1114 2.1 Object Definitions ............................................ 3 1115 3 Overview ........................................................ 4 1116 3.1 Relationship to Contexts ...................................... 4 1117 3.2 Relationship to Community Strings ............................. 5 1118 3.3 Relationship to a Chassis MIB ................................. 5 1119 3.4 Relationship to the Interfaces MIB ............................ 5 1120 3.5 Relationship to the Other MIBs ................................ 6 1121 3.6 Re-Configuration of Entities .................................. 6 1122 3.7 MIB Structure ................................................. 6 1123 3.8 Multiple Agents ............................................... 7 1124 4 Definitions ..................................................... 8 1125 5 Usage Examples .................................................. 21 1126 5.1 Router/Bridge ................................................. 21 1127 5.2 Repeaters ..................................................... 24 1128 6 Acknowledgements ................................................ 28 1129 7 References ...................................................... 29 1130 8 Security Considerations ......................................... 30 1131 9 Authors' Addresses .............................................. 30