idnits 2.17.1 draft-chandramouli-eman-rfc4133bis-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 17 instances of too long lines in the document, the longest one being 3 characters in excess of 72. -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 10, 2012) is 4307 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2119' is mentioned on line 65, but not defined == Missing Reference: 'RFC2037' is mentioned on line 175, but not defined ** Obsolete undefined reference: RFC 2037 (Obsoleted by RFC 2737) == Unused Reference: 'RFC4133' is defined on line 3169, but no explicit reference was found in the text == Unused Reference: 'EMAN-FMWK' is defined on line 3200, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2737 (Obsoleted by RFC 4133) ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) -- Obsolete informational reference (is this intentional?): RFC 1493 (Obsoleted by RFC 4188) -- Obsolete informational reference (is this intentional?): RFC 1516 (Obsoleted by RFC 2108) -- Obsolete informational reference (is this intentional?): RFC 3406 (Obsoleted by RFC 8141) == Outdated reference: A later version (-19) exists of draft-ietf-eman-framework-04 Summary: 4 errors (**), 0 flaws (~~), 7 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Bierman 3 INTERNET-DRAFT Yumaworks 4 Category: Standards Track D. Romascanu 5 Expires: January 11, 2013 AVAYA 6 J. Quittek 7 NEC Europe Ltd. 8 Mouli Chandramouli 9 Cisco Systems, Inc. 10 July 10, 2012 12 Entity MIB (Version 4) 13 draft-chandramouli-eman-rfc4133bis-01.txt 15 Abstract 17 This memo defines a portion of the Management Information Base (MIB) for 18 use with network management protocols in the Internet community. In 19 particular, it describes managed objects used for managing multiple 20 logical and physical entities managed by a single SNMP agent. This 21 document specifies version of the Entity MIB, which obsoletes version 3 22 (RFC 4133). 24 Status of This Memo 26 This Internet-Draft is submitted to IETF in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering Task 30 Force (IETF), its areas, and its working groups. Note that other groups 31 may also distribute working documents as Internet-Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference material 36 or to cite them other than as "work in progress." 38 The list of current Internet-Drafts can be accessed at 39 http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft 40 Shadow Directories can be accessed at http://www.ietf.org/shadow.html 42 This Internet-Draft will expire on January 3, 2013 43 rfc4133bis Entity MIB (Version 4) July 10, 2012 45 Copyright Notice 47 Copyright (c) 2012 IETF Trust and the persons identified as the document 48 authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal Provisions 51 Relating to IETF Documents (http://trustee.ietf.org/license-info) in 52 effect on the date of publication of this document. Please review these 53 documents carefully, as they describe your rights and restrictions with 54 respect to this document. Code Components extracted from this document 55 must include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Conventions used in this document 61 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 62 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 63 "OPTIONAL" in this document are to be interpreted as described in RFC 64 2119 [RFC2119]. 66 rfc4133bis Entity MIB (Version 4) July 10, 2012 68 Table of Contents 70 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 71 2.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 72 2.2. Relationship to Community Strings . . . . . . . . . . . . 6 73 2.3. Relationship to SNMP Contexts . . . . . . . . . . . . . . 6 74 2.4. Relationship to Proxy Mechanisms . . . . . . . . . . . . . 7 75 2.5. Relationship to a Chassis MIB . . . . . . . . . . . . . . 7 76 2.6. Relationship to the Interfaces MIB . . . . . . . . . . . . 7 77 2.7. Relationship to the Other MIBs . . . . . . . . . . . . . . 8 78 2.8. Relationship to Naming Scopes . . . . . . . . . . . . . . 8 79 2.9. Multiple Instances of the Entity MIB . . . . . . . . . . . 8 80 2.10. Re-Configuration of Entities . . . . . . . . . . . . . . 9 81 2.11. Textual Convention Change . . . . . . . . . . . . . . . . 9 82 2.12. MIB Structure . . . . . . . . . . . . . . . . . . . . . . 9 83 2.12.1. entityPhysical Group . . . . . . . . . . . . . . . . 10 84 2.12.2. entityLogical Group . . . . . . . . . . . . . . . . . 12 85 2.12.3. entityMapping Group . . . . . . . . . . . . . . . . . 12 86 2.12.4. entityGeneral Group . . . . . . . . . . . . . . . . . 13 87 2.12.5. entityNotifications Group . . . . . . . . . . . . . . 13 88 2.13. Multiple Agents . . . . . . . . . . . . . . . . . . . . . 13 89 2.14. Changes Since RFC 2037 . . . . . . . . . . . . . . . . . 13 90 2.14.1. Textual Conventions . . . . . . . . . . . . . . . . . 13 91 2.14.2. New entPhysicalTable Objects . . . . . . . . . . . . 13 92 2.14.3. New entLogicalTable Objects . . . . . . . . . . . . . 14 93 2.14.4. Bug Fixes . . . . . . . . . . . . . . . . . . . . . . 14 94 2.15. Changes Since RFC 2737 . . . . . . . . . . . . . . . . . 14 95 2.15.1. Textual Conventions . . . . . . . . . . . . . . . . . 14 96 2.15.2. New Objects . . . . . . . . . . . . . . . . . . . . . 14 97 2.15.3. Bug Fixes . . . . . . . . . . . . . . . . . . . . . . 15 98 2.16. Changes Since RFC 4133 . . . . . . . . . . . . . . . . . 15 99 2.16.1. MIB module addtion . . . . . . . . . . . . . . . . . 15 100 2.16.2. Modification to some of the MIB objects . . . . . . . 15 101 3. MIB Definitions . . . . . . . . . . . . . . . . . . . . . . . 15 102 3.1. ENTITY MIB . . . . . . . . . . . . . . . . . . . . . . . . 15 103 3.2. IANA-ENTITY-MIB . . . . . . . . . . . . . . . . . . . . . . 45 104 4. Usage Examples . . . . . . . . . . . . . . . . . . . . . . . . 49 105 4.1. Router/Bridge . . . . . . . . . . . . . . . . . . . . . . 49 106 4.2. Repeaters . . . . . . . . . . . . . . . . . . . . . . . . 55 107 5. Security Considerations . . . . . . . . . . . . . . . . . . . 62 108 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 109 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 64 110 8. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 64 111 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 112 9.1. Normative References . . . . . . . . . . . . . . . . . . . 64 113 9.2. Informative References . . . . . . . . . . . . . . . . . . 65 114 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 66 116 rfc4133bis Entity MIB (Version 4) July 10, 2012 118 1. The SNMP Management Framework 120 For a detailed overview of the documents that describe the current 121 Internet-Standard Management Framework, please refer to section 7 of 122 RFC 3410 [RFC3410]. 124 Managed objects are accessed via a virtual information store, termed 125 the Management Information Base or MIB. MIB objects are generally 126 accessed through the Simple Network Management Protocol (SNMP). 127 Objects in the MIB are defined using the mechanisms defined in the 128 Structure of Management Information (SMI). This memo specifies a MIB 129 module that is compliant to the SMIv2, which is described in STD 58, 130 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 131 [RFC2580]. 133 2. Overview 135 There is a need for a standardized way of representing a single 136 agent, which supports multiple instances of one MIB. This is 137 presently true for at least 3 standard MIBs, and is likely to become 138 true for more and more MIBs as time passes. For example: 140 - multiple instances of a bridge supported within a single device 141 that has a single agent; 143 - multiple repeaters supported by a single agent; 145 - multiple OSPF backbone areas, each operating as part of its own 146 Autonomous System, and each identified by the same area-id (e.g., 147 0.0.0.0), supported inside a single router with one agent. 149 The single agent present in each of these cases implies a 150 relationship binds these entities. Effectively, there is some 151 "overall" physical entity which houses the sum of the things managed 152 by that one agent, i.e., there are multiple "logical" entities within 153 a single physical entity. Sometimes, the overall physical entity 154 contains multiple (smaller) physical entities, and each logical 155 entity is associated with a particular physical entity. Sometimes, 156 the overall physical entity is a "compound" of multiple physical 157 entities (e.g., a stack of stackable hubs). 159 What is needed is a way to determine exactly which logical entities 160 are managed by the agent (with some version of SNMP) in order to 161 communicate with the agent about a particular logical entity. When 162 different logical entities are associated with different physical 163 entities within the overall physical entity, it is also useful to be 164 able to use this information to distinguish between logical entities. 166 rfc4133bis Entity MIB (Version 4) July 10, 2012 168 In these situations, there is no need for varbinds for multiple 169 logical entities to be referenced in the same SNMP message (although 170 that might be useful in the future). Rather, it is sufficient, and 171 in some situations preferable, to have the context/community in the 172 message identify the logical entity to which the varbinds apply. 174 Version 2 of this MIB addresses new requirements, which have emerged 175 since the publication of the first Entity MIB (RFC 2037 [RFC2037]). 176 There is a need for a standardized way of providing non-volatile, 177 administratively-assigned identifiers for physical components 178 represented with the Entity MIB. There is also a need to align the 179 Entity MIB with the SNMPv3 administrative framework (STD 62, RFC 3411 180 [RFC3411]). Implementation experience has shown that additional 181 physical component attributes are also desirable. 183 Version 3 of this MIB addresses new requirements, which have emerged 184 since the publication of the second Entity MIB (RFC 2737 [RFC2737]). 185 There is a need to identify physical entities that are central 186 processing units (CPUs) and a need to provide a textual convention 187 that identifies an entPhysicalIndex value or zero, where the value 188 zero has application-specific semantics. Two new objects have been 189 added to the entPhysicalTable to identify the manufacturing date and 190 provide additional URIs for a particular physical entity. 192 2.1. Terms 194 Some new terms are used throughout this document: 196 - Naming Scope 197 A "naming scope" represents the set of information that may be 198 potentially accessed through a single SNMP operation. All 199 instances within the naming scope share the same unique identifier 200 space. For SNMPv1, a naming scope is identified by the value of the 201 associated 'entLogicalCommunity' instance. For SNMPv3, the term 202 'context' is used instead of 'naming scope'. The complete 203 definition of an SNMP context can be found in section 3.3.1 of RFC 204 3411 [RFC3411]. 206 - Multi-Scoped Object 207 A MIB object, for which identical instance values identify 208 different managed information in different naming scopes, is called 209 a "multi-scoped" MIB object. 211 - Single-Scoped Object 212 A MIB object, for which identical instance values identify the same 213 managed information in different naming scopes, is called a 214 "single-scoped" MIB object. 216 rfc4133bis Entity MIB (Version 4) July 10, 2012 218 - Logical Entity 219 A managed system contains one or more logical entities, each 220 represented by at most one instantiation of each of a particular 221 set of MIB objects. A set of management functions is associated 222 with each logical entity. Examples of logical entities include 223 routers, bridges, print-servers, etc. 225 - Physical Entity 226 A "physical entity" or "physical component" represents an 227 identifiable physical resource within a managed system. Zero or 228 more logical entities may utilize a physical resource at any given 229 time. Determining which physical components are represented by an 230 agent in the EntPhysicalTable is an implementation-specific matter. 231 Typically, physical resources (e.g., communications ports, 232 backplanes, sensors, daughter-cards, power supplies, the overall 233 chassis), which can be managed via functions associated with one or 234 more logical entities, are included in the MIB. 236 - Containment Tree 237 Each physical component may be modeled as 'contained' within 238 another physical component. A "containment-tree" is the conceptual 239 sequence of entPhysicalIndex values that uniquely specifies the 240 exact physical location of a physical component within the managed 241 system. It is generated by 'following and recording' each 242 'entPhysicalContainedIn' instance 'up the tree towards the root', 243 until a value of zero indicating no further containment is found. 245 2.2. Relationship to Community Strings 247 For community-based SNMP, differentiating logical entities is one 248 (but not the only) purpose of the community string (RFC 1157 249 [RFC1157]). This is accommodated by representing each community 250 string as a logical entity. 252 Note that different logical entities may share the same naming scope 253 and, therefore, the same values of entLogicalCommunity. This is 254 possible, providing they have no need for the same instance of a MIB 255 object to represent different managed information. 257 2.3. Relationship to SNMP Contexts 259 Version 2 of the Entity MIB contains support for associating SNMPv3 260 contexts with logical entities. Two new MIB objects, defining an 261 SnmpEngineID and ContextName pair, are used together to identify an 262 SNMP context associated with a logical entity. This context can be 263 used (in conjunction with the entLogicalTAddress and 264 entLogicalTDomain MIB objects) to send SNMPv3 messages on behalf of a 265 particular logical entity. 267 rfc4133bis Entity MIB (Version 4) July 10, 2012 269 2.4. Relationship to Proxy Mechanisms 271 The Entity MIB is designed to allow functional component discovery. 272 The administrative relationships between different logical entities 273 are not visible in any Entity MIB tables. A Network Management 274 System (NMS) cannot determine whether MIB instances in different 275 naming scopes are realized locally or remotely (e.g., via some proxy 276 mechanism) by examining any particular Entity MIB objects. 278 The management of administrative framework functions is not an 279 explicit goal of the Entity MIB WG at this time. This new area of 280 functionality may be revisited after some operational experience with 281 the Entity MIB is gained. 283 Note that for community-based versions of SNMP, a network 284 administrator will likely be able to associate community strings with 285 naming scopes that have proprietary mechanisms, as a matter of 286 configuration. There are no mechanisms for managing naming scopes 287 defined in this MIB. 289 2.5. Relationship to a Chassis MIB 291 Some readers may recall that a previous IETF working group attempted 292 to define a Chassis MIB. No consensus was reached by that working 293 group, possibly because its scope was too broad. As such, it is not 294 the purpose of this MIB to be a "Chassis MIB replacement", nor is it 295 within the scope of this MIB to contain all the information which 296 might be necessary to manage a "chassis". On the other hand, the 297 entities represented by an implementation of this MIB might well be 298 contained in a chassis. 300 2.6. Relationship to the Interfaces MIB 302 The Entity MIB contains a mapping table identifying physical 303 components that have 'external values' (e.g., ifIndex) associated 304 with them within a given naming scope. This table can be used to 305 identify the physical location of each interface in the ifTable (RFC 306 2863 [RFC2863]). Because ifIndex values in different contexts are 307 not related to one another, the interface to physical component 308 associations are relative to the same logical entity within the 309 agent. 311 The Entity MIB also contains 'entPhysicalName' and 'entPhysicalAlias' 312 objects, which approximate the semantics of the 'ifName' and 313 'ifAlias' objects (respectively) from the Interfaces MIB [RFC2863], 314 for all types of physical components. 316 rfc4133bis Entity MIB (Version 4) July 10, 2012 318 2.7. Relationship to the Other MIBs 320 The Entity MIB contains a mapping table identifying physical 321 components that have identifiers from other standard MIBs associated 322 with them. For example, this table can be used along with the 323 physical mapping table to identify the physical location of each 324 repeater port in the rptrPortTable, or each interface in the ifTable. 326 2.8. Relationship to Naming Scopes 328 There is some question as to which MIB objects may be returned within 329 a given naming scope. MIB objects which are not multi-scoped within 330 a managed system are likely to ignore context information in 331 implementation. In such a case, it is likely such objects will be 332 returned in all naming scopes (e.g., not just the 'default' naming 333 scope or the SNMPv3 default context). 335 For example, a community string used to access the management 336 information for logical device 'bridge2' may allow access to all the 337 non-bridge related objects in the 'default' naming scope, as well as 338 a second instance of the Bridge MIB (RFC 1493 [RFC1493]). 340 The isolation of single-scoped MIB objects by the agent is an 341 implementation-specific matter. An agent may wish to limit the 342 objects returned in a particular naming scope to only the multi- 343 scoped objects in that naming scope (e.g., system group and the 344 Bridge MIB). In this case, all single-scoped management information 345 would belong to a common naming scope (e.g., 'default'), which itself 346 may contain some multi-scoped objects (e.g., system group). 348 2.9. Multiple Instances of the Entity MIB 350 It is possible that more than one agent may exist in a managed 351 system. In such cases, multiple instances of the Entity MIB 352 (representing the same managed objects) may be available to an NMS. 354 In order to reduce complexity for agent implementation, multiple 355 instances of the Entity MIB are not required to be equivalent or even 356 consistent. An NMS may be able to 'align' instances returned by 357 different agents by examining the columns of each table, but vendor- 358 specific identifiers and (especially) index values are likely to be 359 different. Each agent may be managing different subsets of the 360 entire chassis as well. 362 When all of a physically-modular device is represented by a single 363 agent, the entry (for which entPhysicalContainedIn has the value 364 zero) would likely have 'chassis' as the value of its 365 entPhysicalClass. Alternatively, for an agent on a module where the 367 rfc4133bis Entity MIB (Version 4) July 10, 2012 369 agent represents only the physical entities on that module (not those 370 on other modules), the entry (for which entPhysicalContainedIn has 371 the value zero) would likely have 'module' as the value of its 372 entPhysicalClass. 374 An agent implementation of the entLogicalTable is not required to 375 contain information about logical entities managed primarily by other 376 agents. That is, the entLogicalTAddress and entLogicalTDomain 377 objects in the entLogicalTable are provided to support an historical 378 multiplexing mechanism, not to identify other SNMP agents. 380 Note that the Entity MIB is a single-scoped MIB, in the event an 381 agent represents the MIB in different naming scopes. 383 2.10. Re-Configuration of Entities 385 Most of the MIB objects defined in this MIB have, at most, a read- 386 only MAX-ACCESS clause. This is a conscious decision by the working 387 group to limit this MIB's scope. The second version of the Entity 388 MIB allows a network administrator to configure some common 389 attributes of physical components. 391 2.11. Textual Convention Change 393 Version 1 of the Entity MIB contains three MIB objects defined with 394 the (now obsolete) DisplayString textual convention. In version 2 of 395 the Entity MIB, the syntax for these objects has been updated to use 396 the (now preferred) SnmpAdminString textual convention. 398 The entmib working group (which was in charge with the document at 399 that point) realized that this change is not strictly supported by 400 SMIv2. In their judgment, the alternative of deprecating the old 401 objects and defining new objects would have had a more adverse impact 402 on backward compatibility and interoperability, given the particular 403 semantics of these objects. 405 2.12. MIB Structure 407 The Entity MIB contains five groups of MIB objects: 409 - entityPhysical group 410 Describes the physical entities managed by a single agent. 412 - entityLogical group 413 Describes the logical entities managed by a single agent. 415 rfc4133bis Entity MIB (Version 4) July 10, 2012 417 - entityMapping group 418 Describes the associations between the physical entities, logical 419 entities, interfaces, and non-interface ports managed by a single 420 agent. 422 - entityGeneral group 423 Describes general system attributes shared by potentially all types 424 of entities managed by a single agent. 426 - entityNotifications group 427 Contains status indication notifications. 429 2.12.1. entityPhysical Group 431 This group contains a single table to identify physical system 432 components, called the entPhysicalTable. 434 The entPhysicalTable contains one row per physical entity, and must 435 always contain at least one row for an "overall" physical entity, 436 which should have an entPhysicalClass value of 'stack(11)', 437 'chassis(3)' or 'module(9)'. 439 Each row is indexed by an arbitrary, small integer, and contains a 440 description and type of the physical entity. It also optionally 441 contains the index number of another entPhysicalEntry, indicating a 442 containment relationship between the two. 444 Version 2 of the Entity MIB provides additional MIB objects for each 445 physical entity. Some common read-only attributes have been added, 446 as well as three writable string objects. 448 - entPhysicalAlias 449 This string can be used by an NMS as a non-volatile identifier for 450 the physical component. Maintaining a non-volatile string for 451 every physical component represented in the entPhysicalTable can be 452 costly and unnecessary. An agent may algorithmically generate 453 'entPhysicalAlias' strings for particular entries (e.g., based on 454 the entPhysicalClass value). 456 - entPhysicalAssetID 457 This string is provided to store a user-specific asset identifier 458 for removable physical components. In order to reduce the non- 459 volatile storage needed by a particular agent, a network 460 administrator should only assign asset identifiers to physical 461 entities that are field-replaceable (i.e., not permanently 462 contained within another physical entity). 464 rfc4133bis Entity MIB (Version 4) July 10, 2012 466 - entPhysicalSerialNum 467 This string is provided to store a vendor-specific serial number 468 string for physical components. This writable object is used when 469 an agent cannot identify the serial numbers of all installed 470 physical entities, and a network administrator wishes to configure 471 the non-volatile serial number strings manually (via an NMS 472 application). 474 Version 3 of the Entity MIB provides two additional MIB objects for 475 each physical entity: 477 - entPhysicalMfgDate 478 This object contains the date of manufacturing of the managed 479 entity. If the manufacturing date is unknown or not supported the 480 object is not instantiated. The special value '0000000000000000'H 481 may also be returned in this case. 483 - entPhysicalUris 484 This object provides additional identification information about 485 the physical entity. 487 This object contains one or more Uniform Resource Identifiers 488 (URIs) and, therefore, the syntax of this object must conform to 489 RFC 3986 [RFC3986] section 2. Uniform Resource Names (URNs), RFC 490 3406 [RFC3406], are resource identifiers with the specific 491 requirements for enabling location independent identification of a 492 resource, as well as longevity of reference. URNs are part of the 493 larger URI family with the specific goal of providing persistent 494 naming of resources. URI schemes and URN name spaces are 495 registered by IANA (see http://www.iana.org/assignments/uri-schemes 496 and http://www.iana.org/assignments/urn-namespaces). 498 For example, the entPhysicalUris object may be used to encode a URI 499 containing a Common Language Equipment Identifier (CLEI) URN for 500 the managed physical entity. The URN name space for CLEIs is 501 defined in [RFC4152], and the CLEI format is defined in 502 [T1.213][T1.213a]. For example, an entPhysicalUris instance may 503 have the value of 505 URN:CLEI:D4CE18B7AA 507 [RFC3986] and [RFC4152] identify this as a URI in the CLEI URN name 508 space. The specific CLEI code, D4CE18B7AA, is based on the example 509 provided in [T1.213a]. 511 Multiple URIs may be present and are separated by white space 512 characters. Leading and trailing white space characters are 513 ignored. 515 rfc4133bis Entity MIB (Version 4) July 10, 2012 517 If no additional identification information is known about the 518 physical entity or supported, the object is not instantiated. 520 2.12.2. entityLogical Group 522 This group contains a single table to identify logical entities, 523 called the entLogicalTable. 525 The entLogicalTable contains one row per logical entity. Each row is 526 indexed by an arbitrary, small integer and contains a name, 527 description, and type of the logical entity. It also contains 528 information to allow access to the MIB information for the logical 529 entity. This includes SNMP versions that use a community name (with 530 some form of implied context representation) and SNMP versions that 531 use the SNMP ARCH [RFC3411] method of context identification. 533 If an agent represents multiple logical entities with this MIB, then 534 this group must be implemented for all logical entities known to the 535 agent. 537 If an agent represents a single logical entity, or multiple logical 538 entities within a single naming scope, then implementation of this 539 group may be omitted by the agent. 541 2.12.3. entityMapping Group 543 This group contains three tables to identify associations between 544 different system components. 546 - entLPMappingTable 547 This table contains mappings between entLogicalIndex values 548 (logical entities) and entPhysicalIndex values (the physical 549 components supporting that entity). A logical entity can map to 550 more than one physical component, and more than one logical entity 551 can map to (share) the same physical component. If an agent 552 represents a single logical entity, or multiple logical entities 553 within a single naming scope, then implementation of this table may 554 be omitted by the agent. 556 - entAliasMappingTable 557 This table contains mappings between entLogicalIndex, 558 entPhysicalIndex pairs, and 'alias' object identifier values. This 559 allows resources managed with other MIBs (e.g., repeater ports, 560 bridge ports, physical and logical interfaces) to be identified in 561 the physical entity hierarchy. Note that each alias identifier is 562 only relevant in a particular naming scope. If an agent represents 563 a single logical entity, or multiple logical entities within a 565 rfc4133bis Entity MIB (Version 4) July 10, 2012 567 single naming scope, then implementation of this table may be 568 omitted by the agent. 570 - entPhysicalContainsTable 571 This table contains simple mappings between 572 'entPhysicalContainedIn' values for each container/'containee' 573 relationship in the managed system. The indexing of this table 574 allows an NMS to quickly discover the 'entPhysicalIndex' values for 575 all children of a given physical entity. 577 2.12.4. entityGeneral Group 579 This group contains general information relating to the other object 580 groups. 582 At this time, the entGeneral group contains a single scalar object 583 (entLastChangeTime), which represents the value of sysUptime when any 584 part of the Entity MIB configuration last changed. 586 2.12.5. entityNotifications Group 588 This group contains notification definitions relating to the overall 589 status of the Entity MIB instantiation. 591 2.13. Multiple Agents 593 Even though a primary motivation for this MIB is to represent the 594 multiple logical entities supported by a single agent, another 595 motivation is to represent multiple logical entities supported by 596 multiple agents (in the same "overall" physical entity). Indeed, it 597 is implicit in the SNMP architecture that the number of agents is 598 transparent to a network management station. 600 However, there is no agreement at this time as to the degree of 601 cooperation that should be expected for agent implementations. 602 Therefore, multiple agents within the same managed system are free to 603 implement the Entity MIB independently. (For more information, refer 604 to Section 2.9, "Multiple Instances of the Entity MIB".) 606 2.14. Changes Since RFC 2037 608 2.14.1. Textual Conventions 610 The PhysicalClass TC text has been clarified, and a new enumeration 611 to support 'stackable' components has been added. The 612 SnmpEngineIdOrNone TC has been added to support SNMPv3. 614 2.14.2. New entPhysicalTable Objects 615 rfc4133bis Entity MIB (Version 4) July 10, 2012 617 The entPhysicalHardwareRev, entPhysicalFirmwareRev, and 618 entPhysicalSoftwareRev objects have been added for revision 619 identification. 621 The entPhysicalSerialNum, entPhysicalMfgName, entPhysicalModelName, 622 and entPhysicalIsFru objects have been added for better vendor 623 identification for physical components. In the event the agent 624 cannot identify this information, the entPhysicalSerialNum object can 625 be set by a management station. 627 The entPhysicalAlias and entPhysicalAssetID objects have been added 628 for better user component identification. These objects are intended 629 to be set by a management station and preserved by the agent across 630 restarts. 632 2.14.3. New entLogicalTable Objects 634 The entLogicalContextEngineID and entLogicalContextName objects have 635 been added to provide an SNMP context for SNMPv3 access on behalf of 636 a logical entity. 638 2.14.4. Bug Fixes 640 A bug was fixed in the entLogicalCommunity object. The subrange was 641 incorrect (1..255) and is now (0..255). The description clause has 642 also been clarified. This object is now deprecated. 644 The entLastChangeTime object description has been changed to 645 generalize the events that cause an update to the last change 646 timestamp. 648 The syntax was changed from DisplayString to SnmpAdminString for the 649 entPhysicalDescr, entPhysicalName, and entLogicalDescr objects. 651 2.15. Changes Since RFC 2737 653 2.15.1. Textual Conventions 655 The PhysicalIndexOrZero TC has been added to allow objects to 656 reference an entPhysicalIndex value or zero. The PhysicalClass TC 657 has been extended to support a new enumeration for central processing 658 units. 660 2.15.2. New Objects 662 The entPhysicalMfgDate object has been added to the entPhysicalTable 663 to provide the date of manufacturing of the managed entity. 665 rfc4133bis Entity MIB (Version 4) July 10, 2012 667 The entPhysicalUris object has been added to the entPhysicalTable to 668 provide additional identification information about the physical 669 entity, such as a Common Language Equipment Identifier (CLEI) URN. 671 2.15.3. Bug Fixes 673 The syntax was changed from INTEGER to Integer32 for the 674 entPhysicalParentRelPos, entLogicalIndex, and 675 entAliasLogicalIndexOrZero objects, and from INTEGER to 676 PhysicalIndexOrZero for the entPhysicalContainedIn object. 678 2.16. Changes Since RFC 4133 680 2.16.1. MIB module addtion Creation of a new MIB module IANA-ENTITY-MIB 681 which makes the PhysicalIndex TC an IANA-maintained Textual 682 Convention. Over time, there is the need to add new enumerated values 683 for PhysicalClass. If the syntax of IANAPhysicalClass were defined 684 in this MIB module then a new version of this MIB would have to be 685 re-issued in order to define new values. 687 2.16.2. Modification to some of the MIB objects 689 Creation of a new MODULE-COMPLIANCE module entity4LowCompliance for 690 devices with constrained resources like batteries, which might 691 require a limited number of objects to be supported 692 (entPhysicalIndex, entPhysicalName, entIANAPhysicalClass, 693 entPhysicalUris) with the entPhysicalUris object read-only and 694 restricted to a fixed size to allow only for RFC 4122 [RFC4122] 695 compliant values. 697 3. MIB Definitions 699 3.1. ENTITY MIB 701 ENTITY-MIB DEFINITIONS ::= BEGIN 703 IMPORTS 704 MODULE-IDENTITY, OBJECT-TYPE, mib-2, NOTIFICATION-TYPE, 705 Integer32 706 FROM SNMPv2-SMI 707 TDomain, TAddress, TEXTUAL-CONVENTION, 708 AutonomousType, RowPointer, TimeStamp, TruthValue, 709 DateAndTime 710 FROM SNMPv2-TC 711 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 712 FROM SNMPv2-CONF 713 SnmpAdminString 714 FROM SNMP-FRAMEWORK-MIB 716 rfc4133bis Entity MIB (Version 4) July 10, 2012 718 Uri 719 FROM URI-TC-MIB 720 IANAPhysicalClass 721 FROM IANA-ENTITY-MIB; 723 entityMIB MODULE-IDENTITY 724 LAST-UPDATED "201207100000Z" 725 ORGANIZATION "IETF Energy Management Working Group" 726 CONTACT-INFO 727 " WG E-mail: eman@ietf.org 728 Mailing list subscription info: 729 http://www.ietf.org/mailman/listinfo/eman 731 Andy Bierman 732 Yumaworks 733 andy@yumaworks.com 735 Dan Romascanu 736 AVAYA 737 Park Atidim, Bldg. #3 738 Tel Aviv, 61581 739 Israel 740 Phone: +972-3-6458414 741 dromasca@avaya.com 743 Juergen Quittek 744 NEC Europe Ltd. 745 Network Research Division 746 Kurfuersten-Anlage 36 747 Heidelberg 69115 748 DE 749 Phone: +49 6221 4342-115 750 Email: quittek@neclab.eu 752 Mouli Chandramouli 753 Cisco Systems, Inc. 754 Sarjapur Outer Ring Road 755 Bangalore 561013 756 IN 757 Phone: +91 80 4426 3947 758 Email: moulchan@cisco.com" 760 DESCRIPTION 761 "The MIB module for representing multiple logical 762 entities supported by a single SNMP agent. 764 Copyright (C) The Internet Society (2012). This 765 version of this MIB module is part of RFC xxxx; see 767 rfc4133bis Entity MIB (Version 4) July 10, 2012 769 the RFC itself for full legal notices." 771 REVISION "201207100000Z" 772 DESCRIPTION 773 "Entity MIB (Version 4). 774 This revision obsoletes RFC 4133. 775 Additions: 776 - 777 Changes: 778 - according to comments made on draft-chandramouli-00 779 This version published as RFC xxxx." 781 REVISION "201206100000Z" 782 DESCRIPTION 783 "Initial Version of Entity MIB (Version 4). 784 This revision obsoletes RFC 4133. 785 Additions: 786 - 787 Changes: 788 - 789 This version published as RFC xxxx." 791 REVISION "200508100000Z" 792 DESCRIPTION 793 "Initial Version of Entity MIB (Version 3). 794 This revision obsoletes RFC 2737. 795 Additions: 796 - cpu(12) enumeration added to IANAPhysicalClass TC 797 - DISPLAY-HINT clause to PhysicalIndex TC 798 - PhysicalIndexOrZero TC 799 - entPhysicalMfgDate object 800 - entPhysicalUris object 801 Changes: 802 - entPhysicalContainedIn SYNTAX changed from 803 INTEGER to PhysicalIndexOrZero 805 This version published as RFC 4133." 807 REVISION "199912070000Z" 808 DESCRIPTION 809 "Initial Version of Entity MIB (Version 2). 810 This revision obsoletes RFC 2037. 811 This version published as RFC 2737." 813 REVISION "199610310000Z" 814 DESCRIPTION 816 rfc4133bis Entity MIB (Version 4) July 10, 2012 818 "Initial version (version 1), published as 819 RFC 2037." 820 ::= { mib-2 47 } 822 entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 } 824 -- MIB contains four groups 825 entityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 } 826 entityLogical OBJECT IDENTIFIER ::= { entityMIBObjects 2 } 827 entityMapping OBJECT IDENTIFIER ::= { entityMIBObjects 3 } 828 entityGeneral OBJECT IDENTIFIER ::= { entityMIBObjects 4 } 830 -- Textual Conventions 831 PhysicalIndex ::= TEXTUAL-CONVENTION 832 DISPLAY-HINT "d" 833 STATUS current 834 DESCRIPTION 835 "An arbitrary value that uniquely identifies the physical 836 entity. The value should be a small, positive integer. 837 Index values for different physical entities are not 838 necessarily contiguous." 839 SYNTAX Integer32 (1..2147483647) 841 PhysicalIndexOrZero ::= TEXTUAL-CONVENTION 842 DISPLAY-HINT "d" 843 STATUS current 844 DESCRIPTION 845 "This textual convention is an extension of the 846 PhysicalIndex convention, which defines a greater than zero 847 value used to identify a physical entity. This extension 848 permits the additional value of zero. The semantics of the 849 value zero are object-specific and must, therefore, be 850 defined as part of the description of any object that uses 851 this syntax. Examples of the usage of this extension are 852 situations where none or all physical entities need to be 853 referenced." 854 SYNTAX Integer32 (0..2147483647) 856 SnmpEngineIdOrNone ::= TEXTUAL-CONVENTION 857 STATUS current 858 DESCRIPTION 859 "A specially formatted SnmpEngineID string for use with the 860 Entity MIB. 862 rfc4133bis Entity MIB (Version 4) July 10, 2012 864 If an instance of an object of SYNTAX SnmpEngineIdOrNone has 865 a non-zero length, then the object encoding and semantics 866 are defined by the SnmpEngineID textual convention (see STD 867 62, RFC 3411 [RFC3411]). 869 If an instance of an object of SYNTAX SnmpEngineIdOrNone 870 contains a zero-length string, then no appropriate 871 SnmpEngineID is associated with the logical entity (i.e., 872 SNMPv3 is not supported)." 873 SYNTAX OCTET STRING (SIZE(0..32)) -- empty string or SnmpEngineID 875 -- The Physical Entity Table 876 entPhysicalTable OBJECT-TYPE 877 SYNTAX SEQUENCE OF EntPhysicalEntry 878 MAX-ACCESS not-accessible 879 STATUS current 880 DESCRIPTION 881 "This table contains one row per physical entity. There is 882 always at least one row for an 'overall' physical entity." 883 ::= { entityPhysical 1 } 885 entPhysicalEntry OBJECT-TYPE 886 SYNTAX EntPhysicalEntry 887 MAX-ACCESS not-accessible 889 STATUS current 890 DESCRIPTION 891 "Information about a particular physical entity. 893 Each entry provides objects (entPhysicalDescr, 894 entPhysicalVendorType, and entIANAPhysicalClass) to help an 895 NMS identify and characterize the entry, and objects 896 (entPhysicalContainedIn and entPhysicalParentRelPos) to help 897 an NMS relate the particular entry to other entries in this 898 table." 899 INDEX { entPhysicalIndex } 900 ::= { entPhysicalTable 1 } 902 EntPhysicalEntry ::= SEQUENCE { 903 entPhysicalIndex PhysicalIndex, 904 entPhysicalDescr SnmpAdminString, 905 entPhysicalVendorType AutonomousType, 906 entPhysicalContainedIn PhysicalIndexOrZero, 907 entPhysicalClass IANAPhysicalClass, 908 entPhysicalParentRelPos Integer32, 910 rfc4133bis Entity MIB (Version 4) July 10, 2012 912 entPhysicalName SnmpAdminString, 913 entPhysicalHardwareRev SnmpAdminString, 914 entPhysicalFirmwareRev SnmpAdminString, 915 entPhysicalSoftwareRev SnmpAdminString, 916 entPhysicalSerialNum SnmpAdminString, 917 entPhysicalMfgName SnmpAdminString, 918 entPhysicalModelName SnmpAdminString, 919 entPhysicalAlias SnmpAdminString, 920 entPhysicalAssetID SnmpAdminString, 921 entPhysicalIsFRU TruthValue, 922 entPhysicalMfgDate DateAndTime, 923 entPhysicalUris Uri 925 } 927 entPhysicalIndex OBJECT-TYPE 928 SYNTAX PhysicalIndex 929 MAX-ACCESS not-accessible 930 STATUS current 931 DESCRIPTION 932 "The index for this entry." 933 ::= { entPhysicalEntry 1 } 935 entPhysicalDescr OBJECT-TYPE 936 SYNTAX SnmpAdminString 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 941 "A textual description of physical entity. This object 942 should contain a string that identifies the manufacturer's 943 name for the physical entity, and should be set to a 944 distinct value for each version or model of the physical 945 entity." 946 ::= { entPhysicalEntry 2 } 948 entPhysicalVendorType OBJECT-TYPE 949 SYNTAX AutonomousType 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "An indication of the vendor-specific hardware type of the 954 physical entity. Note that this is different from the 955 definition of MIB-II's sysObjectID. 957 An agent should set this object to an enterprise-specific 959 rfc4133bis Entity MIB (Version 4) July 10, 2012 961 registration identifier value indicating the specific 962 equipment type in detail. The associated instance of 963 entIANAPhysicalClass is used to indicate the general type of 964 hardware device. 966 If no vendor-specific registration identifier exists for 967 this physical entity, or the value is unknown by this agent, 968 then the value { 0 0 } is returned." 969 ::= { entPhysicalEntry 3 } 971 entPhysicalContainedIn OBJECT-TYPE 972 SYNTAX PhysicalIndexOrZero 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "The value of entPhysicalIndex for the physical entity which 977 'contains' this physical entity. A value of zero indicates 978 this physical entity is not contained in any other physical 979 entity. Note that the set of 'containment' relationships 980 define a strict hierarchy; that is, recursion is not 981 allowed. 983 In the event that a physical entity is contained by more 984 than one physical entity (e.g., double-wide modules), this 985 object should identify the containing entity with the lowest 986 value of entPhysicalIndex." 987 ::= { entPhysicalEntry 4 } 989 entPhysicalClass OBJECT-TYPE 990 SYNTAX IANAPhysicalClass 991 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "An indication of the general hardware type of the physical 996 entity. 998 An agent should set this object to the standard enumeration 999 value that most accurately indicates the general class of 1000 the physical entity, or the primary class if there is more 1001 than one entity. 1003 If no appropriate standard registration identifier exists 1004 for this physical entity, then the value 'other(1)' is 1005 returned. If the value is unknown by this agent, then the 1006 value 'unknown(2)' is returned." 1008 rfc4133bis Entity MIB (Version 4) July 10, 2012 1010 ::= { entPhysicalEntry 5 } 1012 entPhysicalParentRelPos OBJECT-TYPE 1013 SYNTAX Integer32 (-1..2147483647) 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "An indication of the relative position of this 'child' 1018 component among all its 'sibling' components. Sibling 1019 components are defined as entPhysicalEntries that share the 1020 same instance values of each of the entPhysicalContainedIn 1021 and entPhysicalClass objects. 1023 An NMS can use this object to identify the relative ordering 1024 for all sibling components of a particular parent 1025 (identified by the entPhysicalContainedIn instance in each 1026 sibling entry). 1028 If possible, this value should match any external labeling 1029 of the physical component. For example, for a container 1030 (e.g., card slot) labeled as 'slot #3', 1031 entPhysicalParentRelPos should have the value '3'. Note 1032 that the entPhysicalEntry for the module plugged in slot 3 1033 should have an entPhysicalParentRelPos value of '1'. 1035 If the physical position of this component does not match 1036 any external numbering or clearly visible ordering, then 1037 user documentation or other external reference material 1038 should be used to determine the parent-relative position. 1039 If this is not possible, then the agent should assign a 1040 consistent (but possibly arbitrary) ordering to a given set 1041 of 'sibling' components, perhaps based on internal 1042 representation of the components. 1044 If the agent cannot determine the parent-relative position 1045 for some reason, or if the associated value of 1046 entPhysicalContainedIn is '0', then the value '-1' is 1047 returned. Otherwise, a non-negative integer is returned, 1048 indicating the parent-relative position of this physical 1049 entity. 1051 Parent-relative ordering normally starts from '1' and 1052 continues to 'N', where 'N' represents the highest 1053 positioned child entity. However, if the physical entities 1054 (e.g., slots) are labeled from a starting position of zero, 1056 rfc4133bis Entity MIB (Version 4) July 10, 2012 1058 then the first sibling should be associated with an 1059 entPhysicalParentRelPos value of '0'. Note that this 1060 ordering may be sparse or dense, depending on agent 1061 implementation. 1063 The actual values returned are not globally meaningful, as 1064 each 'parent' component may use different numbering 1065 algorithms. The ordering is only meaningful among siblings 1066 of the same parent component. 1068 The agent should retain parent-relative position values 1069 across reboots, either through algorithmic assignment or use 1070 of non-volatile storage." 1071 ::= { entPhysicalEntry 6 } 1073 entPhysicalName OBJECT-TYPE 1074 SYNTAX SnmpAdminString 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "The textual name of the physical entity. The value of this 1079 object should be the name of the component as assigned by 1080 the local device and should be suitable for use in commands 1081 entered at the device's `console'. This might be a text 1082 name (e.g., `console') or a simple component number (e.g., 1083 port or module number, such as `1'), depending on the 1084 physical component naming syntax of the device. 1086 If there is no local name, or if this object is otherwise 1087 not applicable, then this object contains a zero-length 1088 string. 1090 Note that the value of entPhysicalName for two physical 1091 entities will be the same in the event that the console 1092 interface does not distinguish between them, e.g., slot-1 1093 and the card in slot-1." 1094 ::= { entPhysicalEntry 7 } 1096 entPhysicalHardwareRev OBJECT-TYPE 1097 SYNTAX SnmpAdminString 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "The vendor-specific hardware revision string for the 1102 physical entity. The preferred value is the hardware 1103 revision identifier actually printed on the component itself 1105 rfc4133bis Entity MIB (Version 4) July 10, 2012 1107 (if present). 1109 Note that if revision information is stored internally in a 1110 non-printable (e.g., binary) format, then the agent must 1111 convert such information to a printable format, in an 1112 implementation-specific manner. 1114 If no specific hardware revision string is associated with 1115 the physical component, or if this information is unknown to 1116 the agent, then this object will contain a zero-length 1117 string." 1118 ::= { entPhysicalEntry 8 } 1120 entPhysicalFirmwareRev OBJECT-TYPE 1121 SYNTAX SnmpAdminString 1122 MAX-ACCESS read-only 1123 STATUS current 1124 DESCRIPTION 1125 "The vendor-specific firmware revision string for the 1126 physical entity. 1128 Note that if revision information is stored internally in a 1129 non-printable (e.g., binary) format, then the agent must 1130 convert such information to a printable format, in an 1131 implementation-specific manner. 1133 If no specific firmware programs are associated with the 1134 physical component, or if this information is unknown to the 1135 agent, then this object will contain a zero-length string." 1136 ::= { entPhysicalEntry 9 } 1138 entPhysicalSoftwareRev OBJECT-TYPE 1139 SYNTAX SnmpAdminString 1140 MAX-ACCESS read-only 1141 STATUS current 1142 DESCRIPTION 1143 "The vendor-specific software revision string for the 1144 physical entity. 1146 Note that if revision information is stored internally in a 1148 non-printable (e.g., binary) format, then the agent must 1149 convert such information to a printable format, in an 1150 implementation-specific manner. 1152 If no specific software programs are associated with the 1154 rfc4133bis Entity MIB (Version 4) July 10, 2012 1156 physical component, or if this information is unknown to the 1157 agent, then this object will contain a zero-length string." 1158 ::= { entPhysicalEntry 10 } 1160 entPhysicalSerialNum OBJECT-TYPE 1161 SYNTAX SnmpAdminString (SIZE (0..32)) 1162 MAX-ACCESS read-write 1163 STATUS current 1164 DESCRIPTION 1165 "The vendor-specific serial number string for the physical 1166 entity. The preferred value is the serial number string 1167 actually printed on the component itself (if present). 1169 On the first instantiation of an physical entity, the value 1170 of entPhysicalSerialNum associated with that entity is set 1171 to the correct vendor-assigned serial number, if this 1172 information is available to the agent. If a serial number 1173 is unknown or non-existent, the entPhysicalSerialNum will be 1174 set to a zero-length string instead. 1176 Note that implementations that can correctly identify the 1177 serial numbers of all installed physical entities do not 1178 need to provide write access to the entPhysicalSerialNum 1179 object. Agents which cannot provide non-volatile storage 1180 for the entPhysicalSerialNum strings are not required to 1181 implement write access for this object. 1183 Not every physical component will have a serial number, or 1184 even need one. Physical entities for which the associated 1185 value of the entPhysicalIsFRU object is equal to 'false(2)' 1186 (e.g., the repeater ports within a repeater module), do not 1187 need their own unique serial number. An agent does not have 1188 to provide write access for such entities, and may return a 1189 zero-length string. 1191 If write access is implemented for an instance of 1192 entPhysicalSerialNum, and a value is written into the 1193 instance, the agent must retain the supplied value in the 1194 entPhysicalSerialNum instance (associated with the same 1195 physical entity) for as long as that entity remains 1196 instantiated. This includes instantiations across all 1197 re-initializations/reboots of the network management system, 1198 including those resulting in a change of the physical 1200 entity's entPhysicalIndex value." 1201 ::= { entPhysicalEntry 11 } 1203 rfc4133bis Entity MIB (Version 4) July 10, 2012 1205 entPhysicalMfgName OBJECT-TYPE 1206 SYNTAX SnmpAdminString 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION 1210 "The name of the manufacturer of this physical component. 1211 The preferred value is the manufacturer name string actually 1212 printed on the component itself (if present). 1214 Note that comparisons between instances of the 1215 entPhysicalModelName, entPhysicalFirmwareRev, 1216 entPhysicalSoftwareRev, and the entPhysicalSerialNum 1217 objects, are only meaningful amongst entPhysicalEntries with 1218 the same value of entPhysicalMfgName. 1220 If the manufacturer name string associated with the physical 1221 component is unknown to the agent, then this object will 1222 contain a zero-length string." 1223 ::= { entPhysicalEntry 12 } 1225 entPhysicalModelName OBJECT-TYPE 1226 SYNTAX SnmpAdminString 1227 MAX-ACCESS read-only 1228 STATUS current 1229 DESCRIPTION 1230 "The vendor-specific model name identifier string associated 1231 with this physical component. The preferred value is the 1232 customer-visible part number, which may be printed on the 1233 component itself. 1235 If the model name string associated with the physical 1236 component is unknown to the agent, then this object will 1237 contain a zero-length string." 1238 ::= { entPhysicalEntry 13 } 1240 entPhysicalAlias OBJECT-TYPE 1241 SYNTAX SnmpAdminString (SIZE (0..32)) 1242 MAX-ACCESS read-write 1243 STATUS current 1244 DESCRIPTION 1245 "This object is an 'alias' name for the physical entity, as 1246 specified by a network manager, and provides a non-volatile 1247 'handle' for the physical entity. 1249 On the first instantiation of a physical entity, the value 1251 rfc4133bis Entity MIB (Version 4) July 10, 2012 1253 of entPhysicalAlias associated with that entity is set to 1254 the zero-length string. However, the agent may set the 1255 value to a locally unique default value, instead of a 1256 zero-length string. 1258 If write access is implemented for an instance of 1259 entPhysicalAlias, and a value is written into the instance, 1260 the agent must retain the supplied value in the 1261 entPhysicalAlias instance (associated with the same physical 1262 entity) for as long as that entity remains instantiated. 1263 This includes instantiations across all 1264 re-initializations/reboots of the network management system, 1265 including those resulting in a change of the physical 1266 entity's entPhysicalIndex value." 1267 ::= { entPhysicalEntry 14 } 1269 entPhysicalAssetID OBJECT-TYPE 1270 SYNTAX SnmpAdminString (SIZE (0..32)) 1271 MAX-ACCESS read-write 1272 STATUS current 1273 DESCRIPTION 1274 "This object is a user-assigned asset tracking identifier 1275 (as specified by a network manager) for the physical entity, 1276 and provides non-volatile storage of this information. 1278 On the first instantiation of a physical entity, the value 1279 of entPhysicalAssetID associated with that entity is set to 1280 the zero-length string. 1282 Not every physical component will have an asset tracking 1283 identifier, or even need one. Physical entities for which 1284 the associated value of the entPhysicalIsFRU object is equal 1285 to 'false(2)' (e.g., the repeater ports within a repeater 1286 module), do not need their own unique asset tracking 1287 identifier. An agent does not have to provide write access 1288 for such entities, and may instead return a zero-length 1289 string. 1291 If write access is implemented for an instance of 1292 entPhysicalAssetID, and a value is written into the 1293 instance, the agent must retain the supplied value in the 1294 entPhysicalAssetID instance (associated with the same 1295 physical entity) for as long as that entity remains 1296 instantiated. This includes instantiations across all 1297 re-initializations/reboots of the network management system, 1298 including those resulting in a change of the physical 1299 entity's entPhysicalIndex value. 1301 rfc4133bis Entity MIB (Version 4) July 10, 2012 1303 If no asset tracking information is associated with the 1304 physical component, then this object will contain a 1305 zero-length string." 1306 ::= { entPhysicalEntry 15 } 1308 entPhysicalIsFRU OBJECT-TYPE 1309 SYNTAX TruthValue 1310 MAX-ACCESS read-only 1311 STATUS current 1312 DESCRIPTION 1313 "This object indicates whether or not this physical entity 1314 is considered a 'field replaceable unit' by the vendor. If 1315 this object contains the value 'true(1)' then this 1316 entPhysicalEntry identifies a field replaceable unit. For 1317 all entPhysicalEntries that represent components 1318 permanently contained within a field replaceable unit, the 1319 value 'false(2)' should be returned for this object." 1320 ::= { entPhysicalEntry 16 } 1322 entPhysicalMfgDate OBJECT-TYPE 1323 SYNTAX DateAndTime 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "This object contains the date of manufacturing of the 1328 managed entity. If the manufacturing date is unknown or not 1329 supported, the object is not instantiated. The special 1330 value '0000000000000000'H may also be returned in this 1331 case." 1332 ::= { entPhysicalEntry 17 } 1334 entPhysicalUris OBJECT-TYPE 1335 SYNTAX Uri 1336 MAX-ACCESS read-write 1337 STATUS current 1338 DESCRIPTION 1339 "This object contains additional identification information 1340 about the physical entity. The object contains URIs and, 1341 therefore, the syntax of this object must conform to RFC 1342 3986, section 2. 1344 Multiple URIs may be present and are separated by white 1345 space characters. Leading and trailing white space 1346 characters are ignored. 1348 If no additional identification information is known 1349 about the physical entity or supported, the object is not 1350 instantiated. A zero length octet string may also be 1352 rfc4133bis Entity MIB (Version 4) July 10, 2012 1354 returned in this case." 1355 REFERENCE 1356 "RFC 3986, Uniform Resource Identifiers (URI): Generic 1357 Syntax, section 2, August 1998." 1359 ::= { entPhysicalEntry 18 } 1361 -- The Logical Entity Table 1362 entLogicalTable OBJECT-TYPE 1363 SYNTAX SEQUENCE OF EntLogicalEntry 1364 MAX-ACCESS not-accessible 1365 STATUS current 1366 DESCRIPTION 1367 "This table contains one row per logical entity. For agents 1368 that implement more than one naming scope, at least one 1369 entry must exist. Agents which instantiate all MIB objects 1370 within a single naming scope are not required to implement 1371 this table." 1372 ::= { entityLogical 1 } 1374 entLogicalEntry OBJECT-TYPE 1375 SYNTAX EntLogicalEntry 1376 MAX-ACCESS not-accessible 1377 STATUS current 1378 DESCRIPTION 1379 "Information about a particular logical entity. Entities 1380 may be managed by this agent or other SNMP agents (possibly) 1381 in the same chassis." 1382 INDEX { entLogicalIndex } 1383 ::= { entLogicalTable 1 } 1385 EntLogicalEntry ::= SEQUENCE { 1386 entLogicalIndex Integer32, 1387 entLogicalDescr SnmpAdminString, 1388 entLogicalType AutonomousType, 1389 entLogicalCommunity OCTET STRING, 1390 entLogicalTAddress TAddress, 1391 entLogicalTDomain TDomain, 1392 entLogicalContextEngineID SnmpEngineIdOrNone, 1393 entLogicalContextName SnmpAdminString 1394 } 1396 entLogicalIndex OBJECT-TYPE 1397 SYNTAX Integer32 (1..2147483647) 1398 MAX-ACCESS not-accessible 1399 STATUS current 1400 DESCRIPTION 1402 rfc4133bis Entity MIB (Version 4) July 10, 2012 1404 "The value of this object uniquely identifies the logical 1405 entity. The value should be a small positive integer; index 1406 values for different logical entities are not necessarily 1407 contiguous." 1408 ::= { entLogicalEntry 1 } 1410 entLogicalDescr OBJECT-TYPE 1411 SYNTAX SnmpAdminString 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "A textual description of the logical entity. This object 1416 should contain a string that identifies the manufacturer's 1417 name for the logical entity, and should be set to a distinct 1418 value for each version of the logical entity." 1419 ::= { entLogicalEntry 2 } 1421 entLogicalType OBJECT-TYPE 1422 SYNTAX AutonomousType 1423 MAX-ACCESS read-only 1424 STATUS current 1425 DESCRIPTION 1426 "An indication of the type of logical entity. This will 1427 typically be the OBJECT IDENTIFIER name of the node in the 1428 SMI's naming hierarchy which represents the major MIB 1429 module, or the majority of the MIB modules, supported by the 1430 logical entity. For example: 1431 a logical entity of a regular host/router -> mib-2 1432 a logical entity of a 802.1d bridge -> dot1dBridge 1433 a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt 1434 If an appropriate node in the SMI's naming hierarchy cannot 1435 be identified, the value 'mib-2' should be used." 1436 ::= { entLogicalEntry 3 } 1438 entLogicalCommunity OBJECT-TYPE 1439 SYNTAX OCTET STRING (SIZE (0..255)) 1440 MAX-ACCESS read-only 1441 STATUS deprecated 1442 DESCRIPTION 1443 "An SNMPv1 or SNMPv2C community-string, which can be used to 1444 access detailed management information for this logical 1445 entity. The agent should allow read access with this 1446 community string (to an appropriate subset of all managed 1447 objects) and may also return a community string based on the 1448 privileges of the request used to read this object. Note 1449 that an agent may return a community string with read-only 1450 privileges, even if this object is accessed with a 1451 read-write community string. However, the agent must take 1453 rfc4133bis Entity MIB (Version 4) July 10, 2012 1455 care not to return a community string that allows more 1456 privileges than the community string used to access this 1457 object. 1459 A compliant SNMP agent may wish to conserve naming scopes by 1460 representing multiple logical entities in a single 'default' 1461 naming scope. This is possible when the logical entities, 1462 represented by the same value of entLogicalCommunity, have 1463 no object instances in common. For example, 'bridge1' and 1464 'repeater1' may be part of the main naming scope, but at 1465 least one additional community string is needed to represent 1466 'bridge2' and 'repeater2'. 1468 Logical entities 'bridge1' and 'repeater1' would be 1469 represented by sysOREntries associated with the 'default' 1470 naming scope. 1472 For agents not accessible via SNMPv1 or SNMPv2C, the value 1473 of this object is the empty string. This object may also 1474 contain an empty string if a community string has not yet 1475 been assigned by the agent, or if no community string with 1476 suitable access rights can be returned for a particular SNMP 1477 request. 1479 Note that this object is deprecated. Agents which implement 1480 SNMPv3 access should use the entLogicalContextEngineID and 1481 entLogicalContextName objects to identify the context 1482 associated with each logical entity. SNMPv3 agents may 1483 return a zero-length string for this object, or may continue 1484 to return a community string (e.g., tri-lingual agent 1485 support)." 1486 ::= { entLogicalEntry 4 } 1488 entLogicalTAddress OBJECT-TYPE 1489 SYNTAX TAddress 1490 MAX-ACCESS read-only 1491 STATUS current 1492 DESCRIPTION 1493 "The transport service address by which the logical entity 1494 receives network management traffic, formatted according to 1495 the corresponding value of entLogicalTDomain. 1497 For snmpUDPDomain, a TAddress is 6 octets long: the initial 1498 4 octets contain the IP-address in network-byte order and 1499 the last 2 contain the UDP port in network-byte order. 1500 Consult 'Transport Mappings for the Simple Network 1501 Management Protocol' (STD 62, RFC 3417 [RFC3417]) for 1502 further information on snmpUDPDomain." 1504 rfc4133bis Entity MIB (Version 4) July 10, 2012 1506 ::= { entLogicalEntry 5 } 1508 entLogicalTDomain OBJECT-TYPE 1509 SYNTAX TDomain 1510 MAX-ACCESS read-only 1511 STATUS current 1512 DESCRIPTION 1513 "Indicates the kind of transport service by which the 1514 logical entity receives network management traffic. 1515 Possible values for this object are presently found in the 1516 Transport Mappings for Simple Network Management Protocol' 1517 (STD 62, RFC 3417 [RFC3417])." 1518 ::= { entLogicalEntry 6 } 1520 entLogicalContextEngineID OBJECT-TYPE 1521 SYNTAX SnmpEngineIdOrNone 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "The authoritative contextEngineID that can be used to send 1526 an SNMP message concerning information held by this logical 1527 entity, to the address specified by the associated 1528 'entLogicalTAddress/entLogicalTDomain' pair. 1530 This object, together with the associated 1531 entLogicalContextName object, defines the context associated 1532 with a particular logical entity, and allows access to SNMP 1533 engines identified by a contextEngineId and contextName 1534 pair. 1536 If no value has been configured by the agent, a zero-length 1537 string is returned, or the agent may choose not to 1538 instantiate this object at all." 1539 ::= { entLogicalEntry 7 } 1541 entLogicalContextName OBJECT-TYPE 1542 SYNTAX SnmpAdminString 1543 MAX-ACCESS read-only 1544 STATUS current 1545 DESCRIPTION 1546 "The contextName that can be used to send an SNMP message 1547 concerning information held by this logical entity, to the 1548 address specified by the associated 1549 'entLogicalTAddress/entLogicalTDomain' pair. 1551 This object, together with the associated 1552 entLogicalContextEngineID object, defines the context 1553 associated with a particular logical entity, and allows 1555 rfc4133bis Entity MIB (Version 4) July 10, 2012 1557 access to SNMP engines identified by a contextEngineId and 1558 contextName pair. 1560 If no value has been configured by the agent, a zero-length 1561 string is returned, or the agent may choose not to 1562 instantiate this object at all." 1563 ::= { entLogicalEntry 8 } 1565 entLPMappingTable OBJECT-TYPE 1566 SYNTAX SEQUENCE OF EntLPMappingEntry 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "This table contains zero or more rows of logical entity to 1571 physical equipment associations. For each logical entity 1572 known by this agent, there are zero or more mappings to the 1573 physical resources, which are used to realize that logical 1574 entity. 1576 An agent should limit the number and nature of entries in 1577 this table such that only meaningful and non-redundant 1578 information is returned. For example, in a system that 1579 contains a single power supply, mappings between logical 1580 entities and the power supply are not useful and should not 1581 be included. 1583 Also, only the most appropriate physical component, which is 1584 closest to the root of a particular containment tree, should 1585 be identified in an entLPMapping entry. 1587 For example, suppose a bridge is realized on a particular 1588 module, and all ports on that module are ports on this 1589 bridge. A mapping between the bridge and the module would 1590 be useful, but additional mappings between the bridge and 1591 each of the ports on that module would be redundant (because 1592 the entPhysicalContainedIn hierarchy can provide the same 1593 information). On the other hand, if more than one bridge 1594 were utilizing ports on this module, then mappings between 1595 each bridge and the ports it used would be appropriate. 1597 Also, in the case of a single backplane repeater, a mapping 1598 for the backplane to the single repeater entity is not 1599 necessary." 1600 ::= { entityMapping 1 } 1602 entLPMappingEntry OBJECT-TYPE 1603 SYNTAX EntLPMappingEntry 1604 MAX-ACCESS not-accessible 1606 rfc4133bis Entity MIB (Version 4) July 10, 2012 1608 STATUS current 1609 DESCRIPTION 1610 "Information about a particular logical entity to physical 1611 equipment association. Note that the nature of the 1612 association is not specifically identified in this entry. 1613 It is expected that sufficient information exists in the 1614 MIBs used to manage a particular logical entity to infer how 1615 physical component information is utilized." 1616 INDEX { entLogicalIndex, entLPPhysicalIndex } 1617 ::= { entLPMappingTable 1 } 1619 EntLPMappingEntry ::= SEQUENCE { 1620 entLPPhysicalIndex PhysicalIndex 1621 } 1623 entLPPhysicalIndex OBJECT-TYPE 1624 SYNTAX PhysicalIndex 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "The value of this object identifies the index value of a 1629 particular entPhysicalEntry associated with the indicated 1630 entLogicalEntity." 1631 ::= { entLPMappingEntry 1 } 1633 -- logical entity/component to alias table 1634 entAliasMappingTable OBJECT-TYPE 1635 SYNTAX SEQUENCE OF EntAliasMappingEntry 1636 MAX-ACCESS not-accessible 1637 STATUS current 1638 DESCRIPTION 1639 "This table contains zero or more rows, representing 1640 mappings of logical entity and physical component to 1641 external MIB identifiers. Each physical port in the system 1642 may be associated with a mapping to an external identifier, 1643 which itself is associated with a particular logical 1644 entity's naming scope. A 'wildcard' mechanism is provided 1645 to indicate that an identifier is associated with more than 1646 one logical entity." 1647 ::= { entityMapping 2 } 1649 entAliasMappingEntry OBJECT-TYPE 1650 SYNTAX EntAliasMappingEntry 1651 MAX-ACCESS not-accessible 1652 STATUS current 1653 DESCRIPTION 1654 "Information about a particular physical equipment, logical 1656 rfc4133bis Entity MIB (Version 4) July 10, 2012 1658 entity to external identifier binding. Each logical 1659 entity/physical component pair may be associated with one 1660 alias mapping. The logical entity index may also be used as 1661 a 'wildcard' (refer to the entAliasLogicalIndexOrZero object 1662 DESCRIPTION clause for details.) 1664 Note that only entPhysicalIndex values that represent 1665 physical ports (i.e., associated entPhysicalClass value is 1666 'port(10)') are permitted to exist in this table." 1667 INDEX { entPhysicalIndex, entAliasLogicalIndexOrZero } 1668 ::= { entAliasMappingTable 1 } 1670 EntAliasMappingEntry ::= SEQUENCE { 1671 entAliasLogicalIndexOrZero Integer32, 1672 entAliasMappingIdentifier RowPointer 1673 } 1675 entAliasLogicalIndexOrZero OBJECT-TYPE 1676 SYNTAX Integer32 (0..2147483647) 1677 MAX-ACCESS not-accessible 1678 STATUS current 1679 DESCRIPTION 1680 "The value of this object identifies the logical entity 1681 that defines the naming scope for the associated instance 1682 of the 'entAliasMappingIdentifier' object. 1684 If this object has a non-zero value, then it identifies the 1685 logical entity named by the same value of entLogicalIndex. 1687 If this object has a value of zero, then the mapping between 1688 the physical component and the alias identifier for this 1689 entAliasMapping entry is associated with all unspecified 1690 logical entities. That is, a value of zero (the default 1691 mapping) identifies any logical entity that does not have 1692 an explicit entry in this table for a particular 1693 entPhysicalIndex/entAliasMappingIdentifier pair. 1695 For example, to indicate that a particular interface (e.g., 1696 physical component 33) is identified by the same value of 1697 ifIndex for all logical entities, the following instance 1698 might exist: 1700 entAliasMappingIdentifier.33.0 = ifIndex.5 1702 In the event an entPhysicalEntry is associated differently 1703 for some logical entities, additional entAliasMapping 1704 entries may exist, e.g.: 1706 rfc4133bis Entity MIB (Version 4) July 10, 2012 1708 entAliasMappingIdentifier.33.0 = ifIndex.6 1709 entAliasMappingIdentifier.33.4 = ifIndex.1 1710 entAliasMappingIdentifier.33.5 = ifIndex.1 1711 entAliasMappingIdentifier.33.10 = ifIndex.12 1713 Note that entries with non-zero entAliasLogicalIndexOrZero 1714 index values have precedence over zero-indexed entries. In 1715 this example, all logical entities except 4, 5, and 10, 1716 associate physical entity 33 with ifIndex.6." 1717 ::= { entAliasMappingEntry 1 } 1719 entAliasMappingIdentifier OBJECT-TYPE 1720 SYNTAX RowPointer 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 "The value of this object identifies a particular conceptual 1725 row associated with the indicated entPhysicalIndex and 1726 entLogicalIndex pair. 1728 Because only physical ports are modeled in this table, only 1729 entries that represent interfaces or ports are allowed. If 1730 an ifEntry exists on behalf of a particular physical port, 1731 then this object should identify the associated 'ifEntry'. 1732 For repeater ports, the appropriate row in the 1733 'rptrPortGroupTable' should be identified instead. 1735 For example, suppose a physical port was represented by 1736 entPhysicalEntry.3, entLogicalEntry.15 existed for a 1737 repeater, and entLogicalEntry.22 existed for a bridge. Then 1738 there might be two related instances of 1739 entAliasMappingIdentifier: 1740 entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2 1741 entAliasMappingIdentifier.3.22 == ifIndex.17 1742 It is possible that other mappings (besides interfaces and 1743 repeater ports) may be defined in the future, as required. 1745 Bridge ports are identified by examining the Bridge MIB and 1746 appropriate ifEntries associated with each 'dot1dBasePort', 1747 and are thus not represented in this table." 1748 ::= { entAliasMappingEntry 2 } 1750 -- physical mapping table 1751 entPhysicalContainsTable OBJECT-TYPE 1752 SYNTAX SEQUENCE OF EntPhysicalContainsEntry 1753 MAX-ACCESS not-accessible 1754 STATUS current 1756 rfc4133bis Entity MIB (Version 4) July 10, 2012 1758 DESCRIPTION 1759 "A table that exposes the container/'containee' 1760 relationships between physical entities. This table 1761 provides all the information found by constructing the 1762 virtual containment tree for a given entPhysicalTable, but 1763 in a more direct format. 1765 In the event a physical entity is contained by more than one 1766 other physical entity (e.g., double-wide modules), this 1767 table should include these additional mappings, which cannot 1768 be represented in the entPhysicalTable virtual containment 1769 tree." 1770 ::= { entityMapping 3 } 1772 entPhysicalContainsEntry OBJECT-TYPE 1773 SYNTAX EntPhysicalContainsEntry 1774 MAX-ACCESS not-accessible 1775 STATUS current 1776 DESCRIPTION 1777 "A single container/'containee' relationship." 1778 INDEX { entPhysicalIndex, entPhysicalChildIndex } 1779 ::= { entPhysicalContainsTable 1 } 1781 EntPhysicalContainsEntry ::= SEQUENCE { 1782 entPhysicalChildIndex PhysicalIndex 1783 } 1785 entPhysicalChildIndex OBJECT-TYPE 1786 SYNTAX PhysicalIndex 1787 MAX-ACCESS read-only 1788 STATUS current 1789 DESCRIPTION 1790 "The value of entPhysicalIndex for the contained physical 1791 entity." 1792 ::= { entPhysicalContainsEntry 1 } 1794 -- last change time stamp for the whole MIB 1795 entLastChangeTime OBJECT-TYPE 1796 SYNTAX TimeStamp 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "The value of sysUpTime at the time a conceptual row is 1801 created, modified, or deleted in any of these tables: 1802 - entPhysicalTable 1803 - entLogicalTable 1804 - entLPMappingTable 1805 - entAliasMappingTable 1807 rfc4133bis Entity MIB (Version 4) July 10, 2012 1809 - entPhysicalContainsTable 1810 " 1811 ::= { entityGeneral 1 } 1813 -- Entity MIB Trap Definitions 1814 entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 } 1815 entityMIBTrapPrefix OBJECT IDENTIFIER ::= { entityMIBTraps 0 } 1817 entConfigChange NOTIFICATION-TYPE 1818 STATUS current 1819 DESCRIPTION 1820 "An entConfigChange notification is generated when the value 1821 of entLastChangeTime changes. It can be utilized by an NMS 1822 to trigger logical/physical entity table maintenance polls. 1824 An agent should not generate more than one entConfigChange 1825 'notification-event' in a given time interval (five seconds 1826 is the suggested default). A 'notification-event' is the 1827 transmission of a single trap or inform PDU to a list of 1828 notification destinations. 1830 If additional configuration changes occur within the 1831 throttling period, then notification-events for these 1832 changes should be suppressed by the agent until the current 1833 throttling period expires. At the end of a throttling 1834 period, one notification-event should be generated if any 1835 configuration changes occurred since the start of the 1836 throttling period. In such a case, another throttling 1837 period is started right away. 1839 An NMS should periodically check the value of 1840 entLastChangeTime to detect any missed entConfigChange 1841 notification-events, e.g., due to throttling or transmission 1842 loss." 1843 ::= { entityMIBTrapPrefix 1 } 1845 -- conformance information 1846 entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 } 1848 entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 } 1849 entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 } 1851 -- compliance statements 1852 entityCompliance MODULE-COMPLIANCE 1853 STATUS deprecated 1855 rfc4133bis Entity MIB (Version 4) July 10, 2012 1857 DESCRIPTION 1858 "The compliance statement for SNMP entities that implement 1859 version 1 of the Entity MIB." 1860 MODULE -- this module 1861 MANDATORY-GROUPS { 1862 entityPhysicalGroup, 1863 entityLogicalGroup, 1864 entityMappingGroup, 1865 entityGeneralGroup, 1866 entityNotificationsGroup 1867 } 1868 ::= { entityCompliances 1 } 1870 entity2Compliance MODULE-COMPLIANCE 1871 STATUS deprecated 1872 DESCRIPTION 1873 "The compliance statement for SNMP entities that implement 1874 version 2 of the Entity MIB." 1875 MODULE -- this module 1876 MANDATORY-GROUPS { 1877 entityPhysicalGroup, 1878 entityPhysical2Group, 1879 entityGeneralGroup, 1880 entityNotificationsGroup 1881 } 1882 GROUP entityLogical2Group 1883 DESCRIPTION 1884 "Implementation of this group is not mandatory for agents 1885 that model all MIB object instances within a single naming 1886 scope." 1888 GROUP entityMappingGroup 1889 DESCRIPTION 1890 "Implementation of the entPhysicalContainsTable is mandatory 1891 for all agents. Implementation of the entLPMappingTable and 1892 entAliasMappingTables are not mandatory for agents that 1893 model all MIB object instances within a single naming scope. 1895 Note that the entAliasMappingTable may be useful for all 1896 agents; however, implementation of the entityLogicalGroup or 1897 entityLogical2Group is required to support this table." 1899 OBJECT entPhysicalSerialNum 1900 MIN-ACCESS not-accessible 1901 DESCRIPTION 1902 "Read and write access is not required for agents that 1903 cannot identify serial number information for physical 1904 entities, and/or cannot provide non-volatile storage for 1906 rfc4133bis Entity MIB (Version 4) July 10, 2012 1908 NMS-assigned serial numbers. 1910 Write access is not required for agents that can identify 1911 serial number information for physical entities, but cannot 1912 provide non-volatile storage for NMS-assigned serial 1913 numbers. 1915 Write access is not required for physical entities for which 1916 the associated value of the entPhysicalIsFRU object is equal 1917 to 'false(2)'." 1919 OBJECT entPhysicalAlias 1920 MIN-ACCESS read-only 1921 DESCRIPTION 1922 "Write access is required only if the associated 1923 entPhysicalClass value is equal to 'chassis(3)'." 1925 OBJECT entPhysicalAssetID 1926 MIN-ACCESS not-accessible 1927 DESCRIPTION 1928 "Read and write access is not required for agents that 1929 cannot provide non-volatile storage for NMS-assigned asset 1930 identifiers. 1932 Write access is not required for physical entities for which 1933 the associated value of the entPhysicalIsFRU object is equal 1934 to 'false(2)'." 1936 OBJECT entPhysicalClass 1937 SYNTAX INTEGER { 1938 other(1), 1939 unknown(2), 1940 chassis(3), 1941 backplane(4), 1942 container(5), 1943 powerSupply(6), 1944 fan(7), 1945 sensor(8), 1946 module(9), 1947 port(10), 1948 stack(11) 1949 } 1950 DESCRIPTION 1951 "Implementation of the 'cpu(12)' enumeration is not 1952 required." 1954 ::= { entityCompliances 2 } 1956 rfc4133bis Entity MIB (Version 4) July 10, 2012 1958 entity3Compliance MODULE-COMPLIANCE 1959 STATUS current 1960 DESCRIPTION 1961 "The compliance statement for SNMP entities that implement 1962 version 3 and 4 (full compliance) of the Entity MIB." 1963 MODULE -- this module 1964 MANDATORY-GROUPS { 1965 entityPhysicalGroup, 1966 entityPhysical2Group, 1967 entityGeneralGroup, 1968 entityNotificationsGroup 1969 } 1970 GROUP entityLogical2Group 1971 DESCRIPTION 1972 "Implementation of this group is not mandatory for agents 1973 that model all MIB object instances within a single naming 1974 scope." 1976 GROUP entityMappingGroup 1977 DESCRIPTION 1978 "Implementation of the entPhysicalContainsTable is mandatory 1979 for all agents. Implementation of the entLPMappingTable and 1980 entAliasMappingTables are not mandatory for agents that 1981 model all MIB object instances within a single naming scope. 1983 Note that the entAliasMappingTable may be useful for all 1984 agents; however, implementation of the entityLogicalGroup or 1985 entityLogical2Group is required to support this table." 1987 OBJECT entPhysicalSerialNum 1988 MIN-ACCESS not-accessible 1989 DESCRIPTION 1990 "Read and write access is not required for agents that 1991 cannot identify serial number information for physical 1992 entities, and/or cannot provide non-volatile storage for 1993 NMS-assigned serial numbers. 1995 Write access is not required for agents that can identify 1996 serial number information for physical entities, but cannot 1997 provide non-volatile storage for NMS-assigned serial 1998 numbers. 2000 Write access is not required for physical entities for 2001 which the associated value of the entPhysicalIsFRU object 2002 is equal to 'false(2)'." 2004 OBJECT entPhysicalAlias 2006 rfc4133bis Entity MIB (Version 4) July 10, 2012 2008 MIN-ACCESS read-only 2009 DESCRIPTION 2010 "Write access is required only if the associated 2011 entPhysicalClass value is equal to 'chassis(3)'." 2013 OBJECT entPhysicalAssetID 2014 MIN-ACCESS not-accessible 2015 DESCRIPTION 2016 "Read and write access is not required for agents that 2017 cannot provide non-volatile storage for NMS-assigned asset 2018 identifiers. 2020 Write access is not required for physical entities for which 2021 the associated value of entPhysicalIsFRU is equal to 2022 'false(2)'." 2023 ::= { entityCompliances 3 } 2025 entity4CRCompliance MODULE-COMPLIANCE 2026 STATUS current 2027 DESCRIPTION 2028 "The compliance statement for SNMP entities that implement 2029 version 4 of the Entity MIB on devices with constrained 2030 resources." 2031 MODULE -- this module 2032 MANDATORY-GROUPS { 2033 entityPhysicalCRGroup 2034 } 2036 OBJECT entPhysicalUris 2037 SYNTAX Uri (SIZE (0 | 45)) 2038 MIN-ACCESS read-only 2039 DESCRIPTION 2040 "Write access is not required for agents that 2041 implement version 4 of the Entity MIB on devices with 2042 constrained resources. 2044 Size is constrained to 45 to allow only for RFC 4122 2045 compliant values and 0 for cases when the object is 2046 not instantiated." 2048 ::= { entityCompliances 4 } 2050 rfc4133bis Entity MIB (Version 4) July 10, 2012 2052 -- MIB groupings 2053 entityPhysicalGroup OBJECT-GROUP 2054 OBJECTS { 2055 entPhysicalDescr, 2056 entPhysicalVendorType, 2057 entPhysicalContainedIn, 2058 entPhysicalClass, 2059 entPhysicalParentRelPos, 2060 entPhysicalName 2061 } 2062 STATUS current 2063 DESCRIPTION 2064 "The collection of objects used to represent physical 2065 system components, for which a single agent provides 2066 management information." 2067 ::= { entityGroups 1 } 2069 entityLogicalGroup OBJECT-GROUP 2070 OBJECTS { 2071 entLogicalDescr, 2072 entLogicalType, 2073 entLogicalCommunity, 2074 entLogicalTAddress, 2075 entLogicalTDomain 2076 } 2077 STATUS deprecated 2078 DESCRIPTION 2079 "The collection of objects used to represent the list of 2080 logical entities, for which a single agent provides 2081 management information." 2083 ::= { entityGroups 2 } 2085 entityMappingGroup OBJECT-GROUP 2086 OBJECTS { 2087 entLPPhysicalIndex, 2088 entAliasMappingIdentifier, 2089 entPhysicalChildIndex 2090 } 2091 STATUS current 2092 DESCRIPTION 2093 "The collection of objects used to represent the 2094 associations between multiple logical entities, physical 2095 components, interfaces, and port identifiers, for which a 2096 single agent provides management information." 2097 ::= { entityGroups 3 } 2099 rfc4133bis Entity MIB (Version 4) July 10, 2012 2101 entityGeneralGroup OBJECT-GROUP 2102 OBJECTS { 2103 entLastChangeTime 2104 } 2105 STATUS current 2106 DESCRIPTION 2107 "The collection of objects used to represent general entity 2108 information, for which a single agent provides management 2109 information." 2110 ::= { entityGroups 4 } 2112 entityNotificationsGroup NOTIFICATION-GROUP 2113 NOTIFICATIONS { entConfigChange } 2114 STATUS current 2115 DESCRIPTION 2116 "The collection of notifications used to indicate Entity MIB 2117 data consistency and general status information." 2118 ::= { entityGroups 5 } 2120 entityPhysical2Group OBJECT-GROUP 2121 OBJECTS { 2122 entPhysicalHardwareRev, 2123 entPhysicalFirmwareRev, 2124 entPhysicalSoftwareRev, 2125 entPhysicalSerialNum, 2126 entPhysicalMfgName, 2127 entPhysicalModelName, 2128 entPhysicalAlias, 2129 entPhysicalAssetID, 2130 entPhysicalIsFRU 2131 } 2132 STATUS current 2134 DESCRIPTION 2135 "The collection of objects used to represent physical 2136 system components, for which a single agent provides 2137 management information. This group augments the objects 2138 contained in the entityPhysicalGroup." 2139 ::= { entityGroups 6 } 2141 entityLogical2Group OBJECT-GROUP 2142 OBJECTS { 2143 entLogicalDescr, 2144 entLogicalType, 2145 entLogicalTAddress, 2146 entLogicalTDomain, 2148 rfc4133bis Entity MIB (Version 4) July 10, 2012 2150 entLogicalContextEngineID, 2151 entLogicalContextName 2152 } 2153 STATUS current 2154 DESCRIPTION 2155 "The collection of objects used to represent the 2156 list of logical entities, for which a single SNMP entity 2157 provides management information." 2158 ::= { entityGroups 7 } 2160 entityPhysicalCRGroup OBJECT-GROUP 2161 OBJECTS { 2162 entPhysicalName, 2163 entPhysicalMfgDate, 2164 entPhysicalUris 2165 } 2166 STATUS current 2167 DESCRIPTION 2168 "The collection of objects used to represent physical 2169 system components for constrained resourced devices, 2170 for which a single agent provides 2171 management information." 2172 ::= { entityGroups 8 } 2174 END 2176 3.2. IANA-ENTITY-MIB 2177 IANA-ENTITY-MIB DEFINITIONS ::= BEGIN 2179 IMPORTS 2180 MODULE-IDENTITY, mib-2 2181 FROM SNMPv2-SMI 2182 TEXTUAL-CONVENTION 2183 FROM SNMPv2-TC 2184 ; 2186 ianaEntityMIB MODULE-IDENTITY 2187 LAST-UPDATED "201206100000Z" -- June 10, 2011 2188 ORGANIZATION "IANA" 2189 CONTACT-INFO " Internet Assigned Numbers Authority 2191 Postal: ICANN 2192 4676 Admiralty Way, Suite 330 2193 Marina del Rey, CA 90292 2195 rfc4133bis Entity MIB (Version 4) July 10, 2012 2197 Tel: +1-310-823-9358 2198 EMail: iana&iana.org" 2200 DESCRIPTION 2201 "This MIB module 2203 Copyright (C) The IETF Trust (2012). 2204 The initial version of this MIB module was published in 2205 RFC yyyy; for full legal notices see the RFC itself. 2206 Supplementary information may be available at: 2207 http://www.ietf.org/copyrights/ianamib.html" 2209 REVISION "201206100000Z" -- June 10, 2012 2210 DESCRIPTION "Initial version of this MIB as published in 2211 RFC yyyy." 2213 ::= { mib-2 xxx } 2215 -- RFC Editor, please replace xxx with the IANA allocation for 2216 -- this MIB module and yyyy with the number of the approved RFC 2218 -- Textual Conventions 2220 IANAPhysicalClass ::= TEXTUAL-CONVENTION 2221 STATUS current 2222 DESCRIPTION 2223 "An enumerated value which provides an indication of the 2224 general hardware type of a particular physical entity. 2225 There are no restrictions as to the number of 2226 entPhysicalEntries of each entPhysicalClass, which must 2227 be instantiated by an agent. 2229 The enumeration 'other' is applicable if the physical 2230 entity class is known, but does not match any of the 2231 supported values. 2233 The enumeration 'unknown' is applicable if the physical 2234 entity class is unknown to the agent. 2236 The enumeration 'chassis' is applicable if the physical 2237 entity class is an overall container for networking 2238 equipment. Any class of physical entity, except a stack, 2239 may be contained within a chassis; and a chassis may only 2240 be contained within a stack. 2242 rfc4133bis Entity MIB (Version 4) July 10, 2012 2244 The enumeration 'backplane' is applicable if the physical 2245 entity class is some sort of device for aggregating and 2246 forwarding networking traffic, such as a shared backplane 2247 in a modular ethernet switch. Note that an agent may model 2248 a backplane as a single physical entity, which is actually 2249 implemented as multiple discrete physical components 2250 (within a chassis or stack). 2252 The enumeration 'container' is applicable if the physical 2253 entity class is capable of containing one or more removable 2254 physical entities, possibly of different types. For 2255 example, each (empty or full) slot in a chassis will be 2256 modeled as a container. Note that all removable physical 2257 entities should be modeled within a container entity, such 2258 as field-replaceable modules, fans, or power supplies. 2259 Note that all known containers should be modeled by the 2260 agent, including empty containers. 2262 The enumeration 'powerSupply' is applicable if the physical 2263 entity class is a power-supplying component. 2265 The enumeration 'fan' is applicable if the physical entity 2266 class is a fan or other heat-reduction component. 2268 The enumeration 'sensor' is applicable if the physical 2269 entity class is some sort of sensor, such as a temperature 2270 sensor within a router chassis. 2272 The enumeration 'module' is applicable if the physical 2273 entity class is some sort of self-contained sub-system. If 2274 the enumeration 'module' is removable, then it should be 2275 modeled within a container entity, otherwise it should be 2276 modeled directly within another physical entity (e.g., a 2277 chassis or another module). 2279 The enumeration 'port' is applicable if the physical entity 2280 class is some sort of networking port, capable of receiving 2281 and/or transmitting networking traffic. 2283 The enumeration 'stack' is applicable if the physical entity 2284 class is some sort of super-container (possibly virtual), 2285 intended to group together multiple chassis entities. A 2286 stack may be realized by a 'virtual' cable, a real 2287 interconnect cable, attached to multiple chassis, or may in 2288 fact be comprised of multiple interconnect cables. A stack 2289 should not be modeled within any other physical entities, 2290 but a stack may be contained within another stack. Only 2291 chassis entities should be contained within a stack. 2293 rfc4133bis Entity MIB (Version 4) July 10, 2012 2295 The enumeration 'cpu' is applicable if the physical entity 2296 class is some sort of central processing unit. 2298 The enumeration ?energyObject? is applicable if the 2299 physical entity is some sort of a energy object i.e. a piece 2300 of equipment that is part of or attached to a communications 2301 network that is monitored, controlled, or aids in the 2302 management of another device for Energy Management. 2304 The enumeration ?battery? is applicable of the physical 2305 entity class is some sort of an energy battery device. " 2307 SYNTAX INTEGER { 2308 other(1), 2309 unknown(2), 2310 chassis(3), 2311 backplane(4), 2312 container(5), -- e.g., chassis slot or daughter-card holder 2313 powerSupply(6), 2314 fan(7), 2315 sensor(8), 2316 module(9), -- e.g., plug-in card or daughter-card 2317 port(10), 2318 stack(11), -- e.g., stack of multiple chassis entities 2319 cpu(12), 2320 energyObject(13), 2321 battery (14) 2322 } 2324 END 2326 rfc4133bis Entity MIB (Version 4) July 10, 2012 2328 4. Usage Examples 2330 The following sections iterate the instance values for two example 2331 networking devices. These examples are kept simple to make them more 2332 understandable. Auxiliary components such as fans, sensors, empty 2333 slots, and sub-modules are not shown, but might be modeled in real 2334 implementations. 2336 4.1. Router/Bridge 2338 The first example is a router containing two slots. Each slot 2339 contains a 3 port router/bridge module. Each port is represented in 2340 the ifTable. There are two logical instances of OSPF running and two 2341 logical bridges: 2343 Physical entities -- entPhysicalTable: 2344 1 Field-replaceable physical chassis: 2345 entPhysicalDescr.1 == 'Acme Chassis Model 100' 2346 entPhysicalVendorType.1 == acmeProducts.chassisTypes.1 2347 entPhysicalContainedIn.1 == 0 2348 entPhysicalClass.1 == chassis(3) 2349 entPhysicalParentRelPos.1 == 0 2350 entPhysicalName.1 == '100-A' 2351 entPhysicalHardwareRev.1 == 'A(1.00.02)' 2352 entPhysicalSoftwareRev.1 == '' 2353 entPhysicalFirmwareRev.1 == '' 2354 entPhysicalSerialNum.1 == 'C100076544' 2355 entPhysicalMfgName.1 == 'Acme' 2356 entPhysicalModelName.1 == '100' 2357 entPhysicalAlias.1 == 'cl-SJ17-3-006:rack1:rtr-U3' 2358 entPhysicalAssetID.1 == '0007372293' 2359 entPhysicalIsFRU.1 == true(1) 2360 entPhysicalMfgDate.1 == '2002-5-26,13:30:30.0,-4:0' 2361 entPhysicalUris.1 == 'URN:CLEI:CNME120ARA' 2362 2 slots within the chassis: 2363 entPhysicalDescr.2 == 'Acme Chassis Slot Type AA' 2364 entPhysicalVendorType.2 == acmeProducts.slotTypes.1 2365 entPhysicalContainedIn.2 == 1 2366 entPhysicalClass.2 == container(5) 2367 entPhysicalParentRelPos.2 == 1 2368 entPhysicalName.2 == 'S1' 2369 entPhysicalHardwareRev.2 == 'B(1.00.01)' 2370 entPhysicalSoftwareRev.2 == '' 2371 entPhysicalFirmwareRev.2 == '' 2372 entPhysicalSerialNum.2 == '' 2373 entPhysicalMfgName.2 == 'Acme' 2374 entPhysicalModelName.2 == 'AA' 2375 entPhysicalAlias.2 == '' 2377 rfc4133bis Entity MIB (Version 4) July 10, 2012 2379 entPhysicalAssetID.2 == '' 2380 entPhysicalIsFRU.2 == false(2) 2381 entPhysicalMfgDate.2 == '2002-7-26,12:22:12.0,-4:0' 2382 entPhysicalUris.2 == 'URN:CLEI:CNME123ARA' 2384 entPhysicalDescr.3 == 'Acme Chassis Slot Type AA' 2385 entPhysicalVendorType.3 = acmeProducts.slotTypes.1 2386 entPhysicalContainedIn.3 == 1 2387 entPhysicalClass.3 == container(5) 2388 entPhysicalParentRelPos.3 == 2 2389 entPhysicalName.3 == 'S2' 2390 entPhysicalHardwareRev.3 == '1.00.07' 2391 entPhysicalSoftwareRev.3 == '' 2392 entPhysicalFirmwareRev.3 == '' 2393 entPhysicalSerialNum.3 == '' 2394 entPhysicalMfgName.3 == 'Acme' 2395 entPhysicalModelName.3 == 'AA' 2396 entPhysicalAlias.3 == '' 2397 entPhysicalAssetID.3 == '' 2398 entPhysicalIsFRU.3 == false(2) 2399 entPhysicalMfgDate.3 == '2002-7-26,12:12:12.0,-4:0' 2400 entPhysicalUris.3 == 'URN:CLEI:CNME123ARA' 2402 2 Field-replaceable modules: 2403 Slot 1 contains a module with 3 ports: 2404 entPhysicalDescr.4 == 'Acme Router-100' 2405 entPhysicalVendorType.4 == acmeProducts.moduleTypes.14 2406 entPhysicalContainedIn.4 == 2 2407 entPhysicalClass.4 == module(9) 2408 entPhysicalParentRelPos.4 == 1 2409 entPhysicalName.4 == 'M1' 2410 entPhysicalHardwareRev.4 == '1.00.07' 2411 entPhysicalSoftwareRev.4 == '1.4.1' 2412 entPhysicalFirmwareRev.4 == 'A(1.1)' 2413 entPhysicalSerialNum.4 == 'C100087363' 2414 entPhysicalMfgName.4 == 'Acme' 2415 entPhysicalModelName.4 == 'R100-FE' 2416 entPhysicalAlias.4 == 'rtr-U3:m1:SJ17-3-eng' 2417 entPhysicalAssetID.4 == '0007372462' 2418 entPhysicalIsFRU.4 == true(1) 2419 entPhysicalMfgDate.4 == '2003-7-18,13:30:30.0,-4:0' 2420 entPhysicalUris.4 == 'URN:CLEI:CNRU123CAA' 2422 entPhysicalDescr.5 == 'Acme Ethernet-100 Port' 2423 entPhysicalVendorType.5 == acmeProducts.portTypes.2 2424 entPhysicalContainedIn.5 == 4 2425 entPhysicalClass.5 == port(10) 2426 entPhysicalParentRelPos.5 == 1 2428 rfc4133bis Entity MIB (Version 4) July 10, 2012 2430 entPhysicalName.5 == 'P1' 2431 entPhysicalHardwareRev.5 == 'G(1.02)' 2432 entPhysicalSoftwareRev.5 == '' 2433 entPhysicalFirmwareRev.5 == '1.1' 2434 entPhysicalSerialNum.5 == '' 2435 entPhysicalMfgName.5 == 'Acme' 2436 entPhysicalModelName.5 == 'FE-100' 2437 entPhysicalAlias.5 == '' 2438 entPhysicalAssetID.5 == '' 2439 entPhysicalIsFRU.5 == false(2) 2440 entPhysicalMfgDate.5 == '2003-7-18,14:20:22.0,-4:0' 2441 entPhysicalUris.5 == 'URN:CLEI:CNMES23ARA' 2443 entPhysicalDescr.6 == 'Acme Ethernet-100 Port' 2444 entPhysicalVendorType.6 == acmeProducts.portTypes.2 2445 entPhysicalContainedIn.6 == 4 2446 entPhysicalClass.6 == port(10) 2447 entPhysicalParentRelPos.6 == 2 2448 entPhysicalName.6 == 'P2' 2449 entPhysicalHardwareRev.6 == 'G(1.02)' 2450 entPhysicalSoftwareRev.6 == '' 2451 entPhysicalFirmwareRev.6 == '1.1' 2452 entPhysicalSerialNum.6 == '' 2453 entPhysicalMfgName.6 == 'Acme' 2454 entPhysicalModelName.6 == 'FE-100' 2455 entPhysicalAlias.6 == '' 2456 entPhysicalAssetID.6 == '' 2457 entPhysicalIsFRU.6 == false(2) 2458 entPhysicalMfgDate.6 == '2003-7-19,10:15:15.0,-4:0' 2459 entPhysicalUris.6 == 'URN:CLEI:CNMES23ARA' 2461 entPhysicalDescr.7 == 'Acme Router-100 FDDI-Port' 2462 entPhysicalVendorType.7 == acmeProducts.portTypes.3 2463 entPhysicalContainedIn.7 == 4 2464 entPhysicalClass.7 == port(10) 2465 entPhysicalParentRelPos.7 == 3 2466 entPhysicalName.7 == 'P3' 2467 entPhysicalHardwareRev.7 == 'B(1.03)' 2468 entPhysicalSoftwareRev.7 == '2.5.1' 2469 entPhysicalFirmwareRev.7 == '2.5F' 2470 entPhysicalSerialNum.7 == '' 2471 entPhysicalMfgName.7 == 'Acme' 2472 entPhysicalModelName.7 == 'FDDI-100' 2473 entPhysicalAlias.7 == '' 2474 entPhysicalAssetID.7 == '' 2475 entPhysicalIsFRU.7 == false(2) 2477 rfc4133bis Entity MIB (Version 4) July 10, 2012 2479 Slot 2 contains another 3-port module: 2480 entPhysicalDescr.8 == 'Acme Router-100 Comm Module' 2481 entPhysicalVendorType.8 == acmeProducts.moduleTypes.15 2482 entPhysicalContainedIn.8 == 3 2483 entPhysicalClass.8 == module(9) 2484 entPhysicalParentRelPos.8 == 1 2485 entPhysicalName.8 == 'M2' 2486 entPhysicalHardwareRev.8 == '2.01.00' 2487 entPhysicalSoftwareRev.8 == '3.0.7' 2488 entPhysicalFirmwareRev.8 == 'A(1.2)' 2489 entPhysicalSerialNum.8 == 'C100098732' 2490 entPhysicalMfgName.8 == 'Acme' 2491 entPhysicalModelName.8 == 'C100' 2492 entPhysicalAlias.8 == 'rtr-U3:m2:SJ17-2-eng' 2493 entPhysicalAssetID.8 == '0007373982' 2494 entPhysicalIsFRU.8 == true(1) 2495 entPhysicalMfgDate.8 == '2002-5-26,13:30:15.0,-4:0' 2496 entPhysicalUris.8 == 'URN:CLEI:CNRT321MAA' 2498 entPhysicalDescr.9 == 'Acme Fddi-100 Port' 2499 entPhysicalVendorType.9 == acmeProducts.portTypes.5 2500 entPhysicalContainedIn.9 == 8 2501 entPhysicalClass.9 == port(10) 2502 entPhysicalParentRelPos.9 == 1 2503 entPhysicalName.9 == 'FDDI Primary' 2504 entPhysicalHardwareRev.9 == 'CC(1.07)' 2505 entPhysicalSoftwareRev.9 == '2.0.34' 2506 entPhysicalFirmwareRev.9 == '1.1' 2507 entPhysicalSerialNum.9 == '' 2508 entPhysicalMfgName.9 == 'Acme' 2509 entPhysicalModelName.9 == 'FDDI-100' 2510 entPhysicalAlias.9 == '' 2511 entPhysicalAssetID.9 == '' 2512 entPhysicalIsFRU.9 == false(2) 2514 entPhysicalDescr.10 == 'Acme Ethernet-100 Port' 2515 entPhysicalVendorType.10 == acmeProducts.portTypes.2 2516 entPhysicalContainedIn.10 == 8 2517 entPhysicalClass.10 == port(10) 2518 entPhysicalParentRelPos.10 == 2 2519 entPhysicalName.10 == 'Ethernet A' 2520 entPhysicalHardwareRev.10 == 'G(1.04)' 2521 entPhysicalSoftwareRev.10 == '' 2522 entPhysicalFirmwareRev.10 == '1.3' 2523 entPhysicalSerialNum.10 == '' 2524 entPhysicalMfgName.10 == 'Acme' 2525 entPhysicalModelName.10 == 'FE-100' 2526 entPhysicalAlias.10 == '' 2528 rfc4133bis Entity MIB (Version 4) July 10, 2012 2530 entPhysicalAssetID.10 == '' 2531 entPhysicalIsFRU.10 == false(2) 2532 entPhysicalMfgDate.10 == '2002-7-26,13:30:15.0,-4:0' 2533 entPhysicalUris.10 == 'URN:CLEI:CNMES23ARA' 2535 entPhysicalDescr.11 == 'Acme Ethernet-100 Port' 2536 entPhysicalVendorType.11 == acmeProducts.portTypes.2 2537 entPhysicalContainedIn.11 == 8 2538 entPhysicalClass.11 == port(10) 2539 entPhysicalParentRelPos.11 == 3 2540 entPhysicalName.11 == 'Ethernet B' 2541 entPhysicalHardwareRev.11 == 'G(1.04)' 2542 entPhysicalSoftwareRev.11 == '' 2543 entPhysicalFirmwareRev.11 == '1.3' 2544 entPhysicalSerialNum.11 == '' 2545 entPhysicalMfgName.11 == 'Acme' 2546 entPhysicalModelName.11 == 'FE-100' 2547 entPhysicalAlias.11 == '' 2548 entPhysicalAssetID.11 == '' 2549 entPhysicalIsFRU.11 == false(2) 2550 entPhysicalMfgDate.11 == '2002-8-16,15:35:15.0,-4:0' 2551 entPhysicalUris.11 == 'URN:CLEI:CNMES23ARA' 2553 Logical entities -- entLogicalTable; no SNMPv3 support 2554 2 OSPF instances: 2555 entLogicalDescr.1 == 'Acme OSPF v1.1' 2556 entLogicalType.1 == ospf 2557 entLogicalCommunity.1 == 'public-ospf1' 2558 entLogicalTAddress.1 == 192.0.2.1:161 2559 entLogicalTDomain.1 == snmpUDPDomain 2560 entLogicalContextEngineID.1 == '' 2561 entLogicalContextName.1 == '' 2563 entLogicalDescr.2 == 'Acme OSPF v1.1' 2564 entLogicalType.2 == ospf 2565 entLogicalCommunity.2 == 'public-ospf2' 2566 entLogicalTAddress.2 == 192.0.2.1:161 2567 entLogicalTDomain.2 == snmpUDPDomain 2568 entLogicalContextEngineID.2 == '' 2569 entLogicalContextName.2 == '' 2571 2 logical bridges: 2572 entLogicalDescr.3 == 'Acme Bridge v2.1.1' 2573 entLogicalType.3 == dot1dBridge 2574 entLogicalCommunity.3 == 'public-bridge1' 2575 entLogicalTAddress.3 == 192.0.2.1:161 2576 entLogicalTDomain.3 == snmpUDPDomain 2577 entLogicalContextEngineID.3 == '' 2579 rfc4133bis Entity MIB (Version 4) July 10, 2012 2581 entLogicalContextName.3 == '' 2583 entLogicalDescr.4 == 'Acme Bridge v2.1.1' 2584 entLogicalType.4 == dot1dBridge 2585 entLogicalCommunity.4 == 'public-bridge2' 2586 entLogicalTAddress.4 == 192.0.2.1:161 2587 entLogicalTDomain.4 == snmpUDPDomain 2588 entLogicalContextEngineID.4 == '' 2589 entLogicalContextName.4 == '' 2591 Logical to Physical Mappings: 2592 1st OSPF instance: uses module 1-port 1 2593 entLPPhysicalIndex.1.5 == 5 2595 2nd OSPF instance: uses module 2-port 1 2596 entLPPhysicalIndex.2.9 == 9 2598 1st bridge group: uses module 1, all ports 2600 [ed. -- Note that these mappings are included in the table because 2601 another logical entity (1st OSPF) utilizes one of the 2602 ports. If this were not the case, then a single mapping 2603 to the module (e.g., entLPPhysicalIndex.3.4) would be 2604 present instead.] 2605 entLPPhysicalIndex.3.5 == 5 2606 entLPPhysicalIndex.3.6 == 6 2607 entLPPhysicalIndex.3.7 == 7 2609 2nd bridge group: uses module 2, all ports 2610 entLPPhysicalIndex.4.9 == 9 2611 entLPPhysicalIndex.4.10 == 10 2612 entLPPhysicalIndex.4.11 == 11 2614 Physical to Logical to MIB Alias Mappings -- entAliasMappingTable: 2615 Example 1: ifIndex values are global to all logical entities 2616 entAliasMappingIdentifier.5.0 == ifIndex.1 2617 entAliasMappingIdentifier.6.0 == ifIndex.2 2618 entAliasMappingIdentifier.7.0 == ifIndex.3 2619 entAliasMappingIdentifier.9.0 == ifIndex.4 2620 entAliasMappingIdentifier.10.0 == ifIndex.5 2621 entAliasMappingIdentifier.11.0 == ifIndex.6 2623 Example 2: ifIndex values are not shared by all logical entities; 2624 (Bridge-1 uses ifIndex values 101 - 103 and Bridge-2 uses 2625 ifIndex values 204-206.) 2626 entAliasMappingIdentifier.5.0 == ifIndex.1 2627 entAliasMappingIdentifier.5.3 == ifIndex.101 2628 entAliasMappingIdentifier.6.0 == ifIndex.2 2630 rfc4133bis Entity MIB (Version 4) July 10, 2012 2632 entAliasMappingIdentifier.6.3 == ifIndex.102 2633 entAliasMappingIdentifier.7.0 == ifIndex.3 2634 entAliasMappingIdentifier.7.3 == ifIndex.103 2635 entAliasMappingIdentifier.9.0 == ifIndex.4 2636 entAliasMappingIdentifier.9.4 == ifIndex.204 2637 entAliasMappingIdentifier.10.0 == ifIndex.5 2638 entAliasMappingIdentifier.10.4 == ifIndex.205 2639 entAliasMappingIdentifier.11.0 == ifIndex.6 2640 entAliasMappingIdentifier.11.4 == ifIndex.206 2642 Physical Containment Tree -- entPhysicalContainsTable 2643 chassis has two containers: 2644 entPhysicalChildIndex.1.2 == 2 2645 entPhysicalChildIndex.1.3 == 3 2647 container 1 has a module: 2648 entPhysicalChildIndex.2.4 == 4 2650 container 2 has a module: 2651 entPhysicalChildIndex.3.8 == 8 2653 module 1 has 3 ports: 2654 entPhysicalChildIndex.4.5 == 5 2655 entPhysicalChildIndex.4.6 == 6 2656 entPhysicalChildIndex.4.7 == 7 2658 module 2 has 3 ports: 2659 entPhysicalChildIndex.8.9 == 9 2660 entPhysicalChildIndex.8.10 == 10 2661 entPhysicalChildIndex.8.11 == 11 2663 4.2. Repeaters 2665 The second example is a 3-slot Hub with 2 backplane ethernet 2666 segments. Slot three is empty, and the remaining slots contain 2667 ethernet repeater modules. 2669 Note that this example assumes an older Repeater MIB implementation, 2670 (RFC 1516 [RFC1516]) rather than the new Repeater MIB (RFC 2108 2671 [RFC2108]). The new version contains an object called 2672 'rptrPortRptrId', which should be used to identify repeater port 2673 groupings, rather than using community strings or contexts. 2675 Physical entities -- entPhysicalTable: 2676 1 Field-replaceable physical chassis: 2677 entPhysicalDescr.1 == 'Acme Chassis Model 110' 2678 entPhysicalVendorType.1 == acmeProducts.chassisTypes.2 2679 entPhysicalContainedIn.1 == 0 2681 rfc4133bis Entity MIB (Version 4) July 10, 2012 2683 entPhysicalClass.1 == chassis(3) 2684 entPhysicalParentRelPos.1 ==0 2685 entPhysicalName.1 == '110-B' 2686 entPhysicalHardwareRev.1 == 'A(1.02.00)' 2687 entPhysicalSoftwareRev.1 == '' 2688 entPhysicalFirmwareRev.1 == '' 2689 entPhysicalSerialNum.1 == 'C100079294' 2690 entPhysicalMfgName.1 == 'Acme' 2691 entPhysicalModelName.1 == '110' 2692 entPhysicalAlias.1 == 'bldg09:floor1:rptr18:0067eea0229f' 2693 entPhysicalAssetID.1 == '0007386327' 2694 entPhysicalIsFRU.1 == true(1) 2696 2 Chassis Ethernet Backplanes: 2697 entPhysicalDescr.2 == 'Acme Ethernet Backplane Type A' 2698 entPhysicalVendorType.2 == acmeProducts.backplaneTypes.1 2699 entPhysicalContainedIn.2 == 1 2700 entPhysicalClass.2 == backplane(4) 2701 entPhysicalParentRelPos.2 == 1 2702 entPhysicalName.2 == 'B1' 2703 entPhysicalHardwareRev.2 == 'A(2.04.01)' 2704 entPhysicalSoftwareRev.2 == '' 2705 entPhysicalFirmwareRev.2 == '' 2706 entPhysicalSerialNum.2 == '' 2707 entPhysicalMfgName.2 == 'Acme' 2708 entPhysicalModelName.2 == 'BK-A' 2709 entPhysicalAlias.2 == '' 2710 entPhysicalAssetID.2 == '' 2711 entPhysicalIsFRU.2 == false(2) 2713 entPhysicalDescr.3 == 'Acme Ethernet Backplane Type A' 2714 entPhysicalVendorType.3 == acmeProducts.backplaneTypes.1 2715 entPhysicalContainedIn.3 == 1 2716 entPhysicalClass.3 == backplane(4) 2717 entPhysicalParentRelPos.3 == 2 2718 entPhysicalName.3 == 'B2' 2719 entPhysicalHardwareRev.3 == 'A(2.04.01)' 2720 entPhysicalSoftwareRev.3 == '' 2721 entPhysicalFirmwareRev.3 == '' 2722 entPhysicalSerialNum.3 == '' 2723 entPhysicalMfgName.3 == 'Acme' 2724 entPhysicalModelName.3 == 'BK-A' 2725 entPhysicalAlias.3 == '' 2726 entPhysicalAssetID.3 == '' 2727 entPhysicalIsFRU.3 == false(2) 2729 rfc4133bis Entity MIB (Version 4) July 10, 2012 2731 3 slots within the chassis: 2732 entPhysicalDescr.4 == 'Acme Hub Slot Type RB' 2733 entPhysicalVendorType.4 == acmeProducts.slotTypes.5 2734 entPhysicalContainedIn.4 == 1 2735 entPhysicalClass.4 == container(5) 2736 entPhysicalParentRelPos.4 == 1 2737 entPhysicalName.4 == 'Slot 1' 2738 entPhysicalHardwareRev.4 == 'B(1.00.03)' 2739 entPhysicalSoftwareRev.4 == '' 2740 entPhysicalFirmwareRev.4 == '' 2741 entPhysicalSerialNum.4 == '' 2742 entPhysicalMfgName.4 == 'Acme' 2743 entPhysicalModelName.4 == 'RB' 2744 entPhysicalAlias.4 == '' 2745 entPhysicalAssetID.4 == '' 2746 entPhysicalIsFRU.4 == false(2) 2748 entPhysicalDescr.5 == 'Acme Hub Slot Type RB' 2749 entPhysicalVendorType.5 == acmeProducts.slotTypes.5 2750 entPhysicalContainedIn.5 == 1 2751 entPhysicalClass.5 == container(5) 2752 entPhysicalParentRelPos.5 == 2 2753 entPhysicalName.5 == 'Slot 2' 2754 entPhysicalHardwareRev.5 == 'B(1.00.03)' 2755 entPhysicalSoftwareRev.5 == '' 2756 entPhysicalFirmwareRev.5 == '' 2757 entPhysicalSerialNum.5 == '' 2758 entPhysicalMfgName.5 == 'Acme' 2759 entPhysicalModelName.5 == 'RB' 2760 entPhysicalAlias.5 == '' 2761 entPhysicalAssetID.5 == '' 2762 entPhysicalIsFRU.5 == false(2) 2764 entPhysicalDescr.6 == 'Acme Hub Slot Type RB' 2765 entPhysicalVendorType.6 == acmeProducts.slotTypes.5 2766 entPhysicalContainedIn.6 == 1 2767 entPhysicalClass.6 == container(5) 2768 entPhysicalParentRelPos.6 == 3 2769 entPhysicalName.6 == 'Slot 3' 2770 entPhysicalHardwareRev.6 == 'B(1.00.03)' 2771 entPhysicalSoftwareRev.6 == '' 2772 entPhysicalFirmwareRev.6 == '' 2773 entPhysicalSerialNum.6 == '' 2774 entPhysicalMfgName.6 == 'Acme' 2775 entPhysicalModelName.6 == 'RB' 2776 entPhysicalAlias.6 == '' 2777 entPhysicalAssetID.6 == '' 2778 entPhysicalIsFRU.6 == false(2) 2780 rfc4133bis Entity MIB (Version 4) July 10, 2012 2782 Slot 1 contains a plug-in module with 4 10-BaseT ports: 2783 entPhysicalDescr.7 == 'Acme 10Base-T Module 114' 2784 entPhysicalVendorType.7 == acmeProducts.moduleTypes.32 2785 entPhysicalContainedIn.7 == 4 2786 entPhysicalClass.7 == module(9) 2787 entPhysicalParentRelPos.7 == 1 2788 entPhysicalName.7 == 'M1' 2789 entPhysicalHardwareRev.7 == 'A(1.02.01)' 2790 entPhysicalSoftwareRev.7 == '1.7.2' 2791 entPhysicalFirmwareRev.7 == 'A(1.5)' 2792 entPhysicalSerialNum.7 == 'C100096244' 2793 entPhysicalMfgName.7 == 'Acme' 2794 entPhysicalModelName.7 = '114' 2795 entPhysicalAlias.7 == 'bldg09:floor1:eng' 2796 entPhysicalAssetID.7 == '0007962951' 2797 entPhysicalIsFRU.7 == true(1) 2799 entPhysicalDescr.8 == 'Acme 10Base-T Port RB' 2800 entPhysicalVendorType.8 == acmeProducts.portTypes.10 2801 entPhysicalContainedIn.8 == 7 2802 entPhysicalClass.8 == port(10) 2803 entPhysicalParentRelPos.8 == 1 2804 entPhysicalName.8 == 'Ethernet-A' 2805 entPhysicalHardwareRev.8 == 'A(1.04F)' 2806 entPhysicalSoftwareRev.8 == '' 2807 entPhysicalFirmwareRev.8 == '1.4' 2808 entPhysicalSerialNum.8 == '' 2809 entPhysicalMfgName.8 == 'Acme' 2810 entPhysicalModelName.8 == 'RB' 2811 entPhysicalAlias.8 == '' 2812 entPhysicalAssetID.8 == '' 2813 entPhysicalIsFRU.8 == false(2) 2815 entPhysicalDescr.9 == 'Acme 10Base-T Port RB' 2816 entPhysicalVendorType.9 == acmeProducts.portTypes.10 2817 entPhysicalContainedIn.9 == 7 2818 entPhysicalClass.9 == port(10) 2819 entPhysicalParentRelPos.9 == 2 2820 entPhysicalName.9 == 'Ethernet-B' 2821 entPhysicalHardwareRev.9 == 'A(1.04F)' 2822 entPhysicalSoftwareRev.9 == '' 2823 entPhysicalFirmwareRev.9 == '1.4' 2824 entPhysicalSerialNum.9 == '' 2825 entPhysicalMfgName.9 == 'Acme' 2826 entPhysicalModelName.9 = 'RB' 2827 entPhysicalAlias.9 == '' 2828 entPhysicalAssetID.9 == '' 2829 entPhysicalIsFRU.9 == false(2) 2831 rfc4133bis Entity MIB (Version 4) July 10, 2012 2833 entPhysicalDescr.10 == 'Acme 10Base-T Port RB' 2834 entPhysicalVendorType.10 == acmeProducts.portTypes.10 2835 entPhysicalContainedIn.10 == 7 2836 entPhysicalClass.10 == port(10) 2837 entPhysicalParentRelPos.10 == 3 2838 entPhysicalName.10 == 'Ethernet-C' 2839 entPhysicalHardwareRev.10 == 'B(1.02.07)' 2840 entPhysicalSoftwareRev.10 == '' 2841 entPhysicalFirmwareRev.10 == '1.4' 2842 entPhysicalSerialNum.10 == '' 2843 entPhysicalMfgName.10 == 'Acme' 2844 entPhysicalModelName.10 == 'RB' 2845 entPhysicalAlias.10 == '' 2846 entPhysicalAssetID.10 == '' 2847 entPhysicalIsFRU.10 == false(2) 2849 entPhysicalDescr.11 == 'Acme 10Base-T Port RB' 2850 entPhysicalVendorType.11 == acmeProducts.portTypes.10 2851 entPhysicalContainedIn.11 == 7 2852 entPhysicalClass.11 == port(10) 2853 entPhysicalParentRelPos.11 == 4 2854 entPhysicalName.11 == 'Ethernet-D' 2855 entPhysicalHardwareRev.11 == 'B(1.02.07)' 2856 entPhysicalSoftwareRev.11 == '' 2857 entPhysicalFirmwareRev.11 == '1.4' 2858 entPhysicalSerialNum.11 == '' 2859 entPhysicalMfgName.11 == 'Acme' 2860 entPhysicalModelName.11 == 'RB' 2861 entPhysicalAlias.11 == '' 2862 entPhysicalAssetID.11 == '' 2863 entPhysicalIsFRU.11 == false(2) 2865 Slot 2 contains another ethernet module with 2 ports. 2866 entPhysicalDescr.12 == 'Acme 10Base-T Module Model 4' 2867 entPhysicalVendorType.12 == acmeProducts.moduleTypes.30 2868 entPhysicalContainedIn.12 = 5 2869 entPhysicalClass.12 == module(9) 2870 entPhysicalParentRelPos.12 == 1 2871 entPhysicalName.12 == 'M2' 2872 entPhysicalHardwareRev.12 == 'A(1.01.07)' 2873 entPhysicalSoftwareRev.12 == '1.8.4' 2874 entPhysicalFirmwareRev.12 == 'A(1.8)' 2875 entPhysicalSerialNum.12 == 'C100102384' 2876 entPhysicalMfgName.12 == 'Acme' 2877 entPhysicalModelName.12 == '4' 2878 entPhysicalAlias.12 == 'bldg09:floor1:devtest' 2879 entPhysicalAssetID.12 == '0007968462' 2880 entPhysicalIsFRU.12 == true(1) 2882 rfc4133bis Entity MIB (Version 4) July 10, 2012 2884 entPhysicalDescr.13 == 'Acme 802.3 AUI Port' 2885 entPhysicalVendorType.13 == acmeProducts.portTypes.11 2886 entPhysicalContainedIn.13 == 12 2887 entPhysicalClass.13 == port(10) 2888 entPhysicalParentRelPos.13 == 1 2889 entPhysicalName.13 == 'AUI' 2890 entPhysicalHardwareRev.13 == 'A(1.06F)' 2891 entPhysicalSoftwareRev.13 == '' 2892 entPhysicalFirmwareRev.13 == '1.5' 2893 entPhysicalSerialNum.13 == '' 2894 entPhysicalMfgName.13 == 'Acme' 2895 entPhysicalModelName.13 == '' 2896 entPhysicalAlias.13 == '' 2897 entPhysicalAssetID.13 == '' 2898 entPhysicalIsFRU.13 == false(2) 2900 entPhysicalDescr.14 == 'Acme 10Base-T Port RD' 2901 entPhysicalVendorType.14 == acmeProducts.portTypes.14 2902 entPhysicalContainedIn.14 == 12 2903 entPhysicalClass.14 == port(10) 2904 entPhysicalParentRelPos.14 == 2 2905 entPhysicalName.14 == 'E2' 2906 entPhysicalHardwareRev.14 == 'B(1.01.02)' 2907 entPhysicalSoftwareRev.14 == '' 2908 entPhysicalFirmwareRev.14 == '2.1' 2909 entPhysicalSerialNum.14 == '' 2910 entPhysicalMfgName.14 == 'Acme' 2911 entPhysicalModelName.14 == '' 2912 entPhysicalAlias.14 == '' 2913 entPhysicalAssetID.14 == '' 2914 entPhysicalIsFRU.14 == false(2) 2916 Logical entities -- entLogicalTable; with SNMPv3 support 2917 Repeater 1--comprised of any ports attached to backplane 1 2918 entLogicalDescr.1 == 'Acme repeater v3.1' 2919 entLogicalType.1 == snmpDot3RptrMgt 2920 entLogicalCommunity.1 'public-repeater1' 2921 entLogicalTAddress.1 == 192.0.2.1:161 2922 entLogicalTDomain.1 == snmpUDPDomain 2923 entLogicalContextEngineID.1 == '80000777017c7d7e7f'H 2924 entLogicalContextName.1 == 'repeater1' 2926 Repeater 2--comprised of any ports attached to backplane 2: 2927 entLogicalDescr.2 == 'Acme repeater v3.1' 2928 entLogicalType.2 == snmpDot3RptrMgt 2929 entLogicalCommunity.2 == 'public-repeater2' 2930 entLogicalTAddress.2 == 192.0.2.1:161 2931 entLogicalTDomain.2 == snmpUDPDomain 2933 rfc4133bis Entity MIB (Version 4) July 10, 2012 2935 entLogicalContextEngineID.2 == '80000777017c7d7e7f'H 2936 entLogicalContextName.2 == 'repeater2' 2938 Logical to Physical Mappings -- entLPMappingTable: 2940 repeater1 uses backplane 1, slot 1-ports 1 & 2, slot 2-port 1 2941 [ed. -- Note that a mapping to the module is not included, 2942 because this example represents a port-switchable hub. 2943 Even though all ports on the module could belong to the 2944 same repeater as a matter of configuration, the LP port 2945 mappings should not be replaced dynamically with a single 2946 mapping for the module (e.g., entLPPhysicalIndex.1.7). 2947 If all ports on the module shared a single backplane connection, 2948 then a single mapping for the module would be more appropriate.] 2950 entLPPhysicalIndex.1.2 == 2 2951 entLPPhysicalIndex.1.8 == 8 2952 entLPPhysicalIndex.1.9 == 9 2953 entLPPhysicalIndex.1.13 == 13 2955 repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2 2956 entLPPhysicalIndex.2.3 == 3 2957 entLPPhysicalIndex.2.10 == 10 2958 entLPPhysicalIndex.2.11 == 11 2959 entLPPhysicalIndex.2.14 == 14 2961 Physical to Logical to MIB Alias Mappings -- entAliasMappingTable: 2962 Repeater Port Identifier values are shared by both repeaters: 2963 entAliasMappingIdentifier.8.0 == rptrPortGroupIndex.1.1 2964 entAliasMappingIdentifier.9.0 == rptrPortGroupIndex.1.2 2965 entAliasMappingIdentifier.10.0 == rptrPortGroupIndex.1.3 2966 entAliasMappingIdentifier.11.0 == rptrPortGroupIndex.1.4 2967 entAliasMappingIdentifier.13.0 == rptrPortGroupIndex.2.1 2968 entAliasMappingIdentifier.14.0 == rptrPortGroupIndex.2.2 2970 Physical Containment Tree -- entPhysicalContainsTable 2971 chassis has two backplanes and three containers: 2972 entPhysicalChildIndex.1.2 == 2 2973 entPhysicalChildIndex.1.3 == 3 2974 entPhysicalChildIndex.1.4 == 4 2975 entPhysicalChildIndex.1.5 == 5 2976 entPhysicalChildIndex.1.6 == 6 2978 container 1 has a module: 2979 entPhysicalChildIndex.4.7 == 7 2981 container 2 has a module 2982 entPhysicalChildIndex.5.12 == 12 2984 rfc4133bis Entity MIB (Version 4) July 10, 2012 2986 [ed. -- in this example, container 3 is empty.] 2988 module 1 has 4 ports: 2989 entPhysicalChildIndex.7.8 == 8 2990 entPhysicalChildIndex.7.9 == 9 2991 entPhysicalChildIndex.7.10 == 10 2992 entPhysicalChildIndex.7.11 == 11 2994 module 2 has 2 ports: 2995 entPhysicalChildIndex.12.13 == 13 2996 entPhysicalChildIndex.12.14 == 14 2998 5. Security Considerations 3000 There are a number of management objects defined in this MIB that 3001 have a MAX-ACCESS clause of read-write and/or read-create. Such 3002 objects may be considered sensitive or vulnerable in some network 3003 environments. The support for SET operations in a non-secure 3004 environment without proper protection can have a negative effect on 3005 network operations. 3007 There are a number of managed objects in this MIB that may contain 3008 sensitive information. These are: 3010 entPhysicalDescr 3011 entPhysicalVendorType 3012 entPhysicalHardwareRev 3013 entPhysicalFirmwareRev 3014 entPhysicalSoftwareRev 3015 entPhysicalSerialNum 3016 entPhysicalMfgName 3017 entPhysicalModelName 3019 These objects expose information about the physical entities 3020 within a managed system, which may be used to identify the vendor, 3021 model, and version information of each system component. 3023 entPhysicalAssetID 3025 This object can allow asset identifiers for various system 3026 components to be exposed, in the event this MIB object is actually 3027 configured by an NMS application. 3029 entLogicalDescr 3030 entLogicalType 3032 These objects expose the type of logical entities present in the 3033 managed system. 3035 rfc4133bis Entity MIB (Version 4) July 10, 2012 3037 entLogicalCommunity 3039 This object exposes community names associated with particular 3040 logical entities within the system. 3042 entLogicalTAddress 3043 entLogicalTDomain 3045 These objects expose network addresses that can be used to 3046 communicate with an SNMP agent on behalf of particular logical 3047 entities within the system. 3049 entLogicalContextEngineID 3050 entLogicalContextName 3052 These objects identify the authoritative SNMP engine that contains 3053 information on behalf of particular logical entities within the 3054 system. 3056 It is thus important to control even GET access to these objects 3057 and possibly to even encrypt the values of these object when 3058 sending them over the network via SNMP. Not all versions of SNMP 3059 provide features for such a secure environment. 3061 SNMPv1 by itself is not a secure environment. Even if the network 3062 itself is secure (for example by using IPSec), even then, there is 3063 no control as to who on the secure network is allowed to access and 3064 GET/SET (read/change/create/delete) the objects in this MIB. 3066 It is recommended that the implementers consider the security 3067 features as provided by the SNMPv3 framework. Specifically, the 3068 use of the User-based Security Model RFC 3414 [RFC3414] and the 3069 View-based Access Control Model RFC 3415 [RFC3415] is recommended. 3071 It is then a customer/user responsibility to ensure that the SNMP 3072 entity giving access to an instance of this MIB, is properly 3073 configured to give access to the objects only to those principals 3074 (users) that have legitimate rights to indeed GET or SET 3075 (change/create/delete) them. 3077 6. IANA Considerations 3079 The MIB module in this document uses the following IANA-assigned 3080 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 3082 Descriptor OBJECT IDENTIFIER value 3083 ---------- ----------------------- 3084 entityMIB { mib-2 47 } 3086 rfc4133bis Entity MIB (Version 4) July 10, 2012 3088 7. Acknowledgements 3090 The first three versions of RFCs on the ENTITY MIB were authored by 3091 A. Bierman and K. McCloghrie. The authors would like thank A. Bierman 3092 and K. McCloghrie for the earlier versions of ENTITY MIB. 3094 The motivation for the extension to RFC 4133 stems from the 3095 requirements of the EMAN WG at IETF. 3097 The authors also thank Juergen Schoenwaelder for his review and 3098 comments on this draft. 3100 8. Open Issues 3102 Open issue 1: entPhysicalUUID object with a compact UUID 3103 representation instead of using the URI format. 3105 9. References 3107 9.1. Normative References 3109 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3110 "Structure of Management Information Version 2 3111 (SMIv2)", STD 58, RFC 2578, April 1999. 3113 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3114 "Textual Conventions for SMIv2", STD 58, RFC 2579, 3115 April 1999. 3117 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3118 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3119 April 1999. 3121 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 3122 Architecture for Describing Simple Network Management 3123 Protocol (SNMP) Management Frameworks", STD 62, RFC 3124 3411, December 2002. 3126 [RFC3417] Presuhn, R., "Transport Mappings for the Simple Network 3127 Management Protocol (SNMP)", STD 62, RFC 3417, December 3128 2002. 3130 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, 3131 "Uniform Resource Identifier (URI): Generic Syntax", 3132 STD 66, RFC 3986, January 2005. 3134 [RFC2737] McCloghrie, K. and A. Bierman, "Entity MIB (Version 3136 rfc4133bis Entity MIB (Version 4) July 10, 2012 3138 2)", RFC 2737, December 1999. 3140 [RFC4133] McCloghrie, K. and A. Bierman, "Entity MIB (Version 3141 3)", RFC 4133, August 2005. 3143 9.2. Informative References 3145 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 3146 "Simple Network Management Protocol", STD 15, RFC 1157, 3147 May 1990. 3149 [RFC1493] Decker, E., Langille, P., Rijsinghani, A., and K. 3150 McCloghrie, "Definitions of Managed Objects for 3151 Bridges", RFC 1493, July 1993. 3153 [RFC1516] McMaster, D. and K. McCloghrie, "Definitions of Managed 3154 Objects for IEEE 802.3 Repeater Devices", RFC 1516, 3155 September 1993. 3157 [RFC4122] Leach, P., Mealling, M., Salz, R., "A Universally 3158 Unique IDentifier (UUID) URN Namespace", RFC 4122, July 3159 2005. 3161 [RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K. 3162 McCloghrie, "Definitions of Managed Objects for IEEE 3163 802.3 Repeater Devices using SMIv2", RFC 2108, February 3164 1997. 3166 [RFC2737] McCloghrie, K. and A. Bierman, "Entity MIB (Version 3167 2)", RFC 2737, December 1999. 3169 [RFC4133] McCloghrie, K. and A. Bierman, "Entity MIB (Version 3170 3)", RFC 4133, August 2005. 3172 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3173 MIB", RFC 2863, June 2000. 3175 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. 3176 Faltstrom, "Uniform Resource Names (URN) Namespace 3177 Definition Mechanisms", BCP 66, RFC 3406, October 2002. 3179 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3180 "Introduction and Applicability Statements for 3181 Internet-Standard Management Framework", RFC 3410, 3182 December 2002. 3184 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 3185 Model (USM) for version 3 of the Simple Network 3187 rfc4133bis Entity MIB (Version 4) July 10, 2012 3189 Management Protocol (SNMPv3)", STD 62, RFC 3414, 3190 December 2002. 3192 [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 3193 Access Control Model (VACM) for the Simple Network 3194 Management Protocol (SNMP)", STD 62, RFC 3415, December 3195 2002. 3197 [RFC4152] Tesink, K. and R. Fox, "A Uniform Resource Name (URN) 3198 Namespace for the CLEI Code", RFC 4152, August 2005. 3200 [EMAN-FMWK] Parello, J. Claise, B. Schoening, B. Quittek, J. and 3201 Nordman, B. "Energy Management Framework", draft-ietf- 3202 eman-framework-04, March 2012. 3204 [T1.213] ATIS T1.213-2001, "Coded Identification of Equipment 3205 Entities in the North American Telecommunications 3206 System for Information Exchange", 2001, www.ansi.org. 3208 [T1.213a] ATIS T1.213a, "Supplement to T1.213-2001, Coded 3209 Identification of Equipment Entities in the North 3210 American Telecommunications System for Information 3211 Exchange, to correct the representation of the Basic 3212 Code in Figure B.1", 2001, www.ansi.org. 3214 Authors' Addresses 3216 Andy Bierman 3217 Yumaworks 3218 andy@yumaworks.com 3220 Dan Romascanu 3221 AVAYA 3222 Park Atidim, Bldg. #3 3223 Tel Aviv, 61581 3224 Israel 3226 +972-3-6458414 3227 dromasca@avaya.com 3229 Juergen Quittek 3230 NEC Europe Ltd. 3231 Network Research Division 3232 Kurfuersten-Anlage 36 3233 Heidelberg 69115 3234 DE 3236 rfc4133bis Entity MIB (Version 4) July 10, 2012 3238 Phone: +49 6221 4342-115 3239 Email: quittek@neclab.eu 3241 Mouli Chandramouli 3242 Cisco Systems, Inc. 3243 Sarjapur Outer Ring Road 3244 Bangalore 561013 3245 IN 3247 Phone: +91 80 4426 3947 3248 Email: moulchan@cisco.com