1HP-ENTITY-MIB DEFINITIONS ::= BEGIN 2 3IMPORTS 4 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE 5 FROM SNMPv2-SMI 6 TDomain, TAddress, DisplayString, TEXTUAL-CONVENTION, 7 AutonomousType, RowPointer, TimeStamp 8 FROM SNMPv2-TC 9 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 10 FROM SNMPv2-CONF 11 icf 12 FROM HP-ICF-OID; 13 14hpEntityMIB MODULE-IDENTITY 15 LAST-UPDATED "200011030636Z" -- November 3, 2000 16 ORGANIZATION "Hewlett Packard Company, 17 Network Infrastructure Solutions" 18 CONTACT-INFO 19 "Hewlett Packard Company 20 8000 Foothills Blvd. 21 Roseville, CA 95747" 22 DESCRIPTION 23 "The MIB module for representing multiple logical 24 entities supported by a single SNMP agent. 25 26 This is an exact copy of draft 7 of the IETF 27 Entity MIB. The only changes are to actually 28 assign an OID to it, and add hp to the beginning 29 of all the labels. This was done only because 30 a product that uses this MIB is scheduled to ship 31 before the IETF MIB will be published as an RFC, 32 and we needed to give it an OID. 33 34 It is expected that this MIB module will only be 35 supported until the IETF actually publishes the 36 official version as an RFC. At that time, we will 37 support the IETF version of this MIB." 38 39 REVISION "200011030636Z" -- November 3, 2000 40 DESCRIPTION 41 "Update division name. Since this MIB was only 42 supported on a single product, and all subsequent 43 products now support the IETF Entity MIB, mark the 44 entire MIB as obsolete." 45 46 REVISION "9703060326Z" -- March 6, 1997 47 DESCRIPTION 48 "Uncommented NOTIFICATION-GROUP, and add import." 49 50 REVISION "9609062135Z" -- September 6, 1996 51 DESCRIPTION 52 "Initial (and probably only) revision of this MIB module. 53 Released with the AdvanceStack 10BaseT Switching Hubs." 54 ::= { icf 9 } 55 56hpEntityMIBObjects OBJECT IDENTIFIER ::= { hpEntityMIB 1 } 57 58-- MIB contains four groups 59 60 61 62 63 64 65 66 67 68 69 70hpEntityPhysical OBJECT IDENTIFIER ::= { hpEntityMIBObjects 1 } 71hpEntityLogical OBJECT IDENTIFIER ::= { hpEntityMIBObjects 2 } 72hpEntityMapping OBJECT IDENTIFIER ::= { hpEntityMIBObjects 3 } 73hpEntityGeneral OBJECT IDENTIFIER ::= { hpEntityMIBObjects 4 } 74 75 76-- Textual Conventions 77PhysicalIndex ::= TEXTUAL-CONVENTION 78 STATUS current 79 DESCRIPTION 80 "An arbitrary value which uniquely identifies the physical 81 entity. The value is a small positive integer; index values 82 for different physical entities are not necessarily 83 contiguous." 84 SYNTAX INTEGER (1..2147483647) 85 86 87PhysicalClass ::= TEXTUAL-CONVENTION 88 STATUS current 89 DESCRIPTION 90 "An enumerated value which provides an indication of the 91 general hardware type of a particular physical entity." 92 SYNTAX INTEGER { 93 other(1), 94 unknown(2), 95 chassis(3), 96 backplane(4), 97 container(5), -- e.g. slot or daughter-card holder 98 powerSupply(6), 99 fan(7), 100 sensor(8), 101 module(9), -- e.g. plug-in card or daughter-card 102 port(10) 103 } 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126-- The Physical Entity Table 127 128hpEntPhysicalTable OBJECT-TYPE 129 SYNTAX SEQUENCE OF HpEntPhysicalEntry 130 MAX-ACCESS not-accessible 131 STATUS obsolete 132 DESCRIPTION 133 "This table contains one row per physical entity. There is 134 always at least one row for an 'overall' physical entity." 135 ::= { hpEntityPhysical 1 } 136 137hpEntPhysicalEntry OBJECT-TYPE 138 SYNTAX HpEntPhysicalEntry 139 MAX-ACCESS not-accessible 140 STATUS obsolete 141 DESCRIPTION 142 "Information about a particular physical entity. 143 144 Each entry provides objects (hpEntPhysicalDescr, 145 hpEntPhysicalVendorType, and hpEntPhysicalClass) to help an NMS 146 identify and characterize the entry, and objects 147 (hpEntPhysicalContainedIn and hpEntPhysicalParentRelPos) to help 148 an NMS relate the particular entry to other entries in this 149 table." 150 INDEX { hpEntPhysicalIndex } 151 ::= { hpEntPhysicalTable 1 } 152 153HpEntPhysicalEntry ::= SEQUENCE { 154 hpEntPhysicalIndex PhysicalIndex, 155 hpEntPhysicalDescr DisplayString, 156 hpEntPhysicalVendorType AutonomousType, 157 hpEntPhysicalContainedIn INTEGER, 158 hpEntPhysicalClass PhysicalClass, 159 hpEntPhysicalParentRelPos INTEGER, 160 hpEntPhysicalName DisplayString 161} 162 163hpEntPhysicalIndex OBJECT-TYPE 164 SYNTAX PhysicalIndex 165 MAX-ACCESS not-accessible 166 STATUS obsolete 167 DESCRIPTION 168 "The index for this entry." 169 ::= { hpEntPhysicalEntry 1 } 170 171 172 173 174 175 176 177 178 179 180 181 182hpEntPhysicalDescr OBJECT-TYPE 183 SYNTAX DisplayString 184 MAX-ACCESS read-only 185 STATUS obsolete 186 DESCRIPTION 187 "A textual description of physical entity. This object 188 should contain a string which identifies the manufacturer's 189 name for the physical entity, and should be set to a 190 distinct value for each version or model of the physical 191 entity. " 192 ::= { hpEntPhysicalEntry 2 } 193 194hpEntPhysicalVendorType OBJECT-TYPE 195 SYNTAX AutonomousType 196 MAX-ACCESS read-only 197 STATUS obsolete 198 DESCRIPTION 199 "An indication of the vendor-specific hardware type of the 200 physical entity. Note that this is different from the 201 definition of MIB-II's sysObjectID. 202 203 An agent should set this object to a enterprise-specific 204 registration identifier value indicating the specific 205 equipment type in detail. The associated instance of 206 hpEntPhysicalClass is used to indicate the general type of 207 hardware device. 208 209 If no vendor-specific registration identifier exists for 210 this physical entity, or the value is unknown by this agent, 211 then the value { 0 0 } is returned." 212 ::= { hpEntPhysicalEntry 3 } 213 214hpEntPhysicalContainedIn OBJECT-TYPE 215 SYNTAX INTEGER (0..2147483647) 216 MAX-ACCESS read-only 217 STATUS obsolete 218 DESCRIPTION 219 "The value of hpEntPhysicalIndex for the physical entity which 220 'contains' this physical entity. A value of zero indicates 221 this physical entity is not contained in any other physical 222 entity. Note that the set of 'containment' relationships 223 define a strict hierarchy; that is, recursion is not 224 allowed." 225 ::= { hpEntPhysicalEntry 4 } 226 227 228 229 230 231 232 233 234 235 236 237 238hpEntPhysicalClass OBJECT-TYPE 239 SYNTAX PhysicalClass 240 MAX-ACCESS read-only 241 STATUS obsolete 242 DESCRIPTION 243 "An indication of the general hardware type of the physical 244 entity. 245 246 An agent should set this object to the standard enumeration 247 value which most accurately indicates the general class of 248 the physical entity, or the primary class if there is more 249 than one. 250 251 If no appropriate standard registration identifier exists 252 for this physical entity, then the value 'other(1)' is 253 returned. If the value is unknown by this agent, then the 254 value 'unknown(2)' is returned." 255 ::= { hpEntPhysicalEntry 5 } 256 257hpEntPhysicalParentRelPos OBJECT-TYPE 258 SYNTAX INTEGER (-1..2147483647) 259 MAX-ACCESS read-only 260 STATUS obsolete 261 DESCRIPTION 262 "An indication of the relative position of this 'child' 263 component among all its 'sibling' components. Sibling 264 components are defined as hpEntPhysicalEntries which share the 265 same instance values of each of the hpEntPhysicalContainedIn 266 and hpEntPhysicalClass objects. 267 268 An NMS can use this object to identify the relative ordering 269 for all sibling components of a particular parent 270 (identified by the hpEntPhysicalContainedIn instance in each 271 sibling entry). 272 273 This value should match any external labeling of the 274 physical component if possible. For example, for a module 275 labeled as 'card #3', hpEntPhysicalParentRelPos should have 276 the value '3'. 277 278 If the physical position of this component does not match 279 any external numbering or clearly visible ordering, then 280 user documentation or other external reference material 281 should be used to determine the parent-relative position. If 282 this is not possible, then the the agent should assign a 283 284 285 286 287 288 289 290 291 292 293 294 consistent (but possibly arbitrary) ordering to a given set 295 of 'sibling' components, perhaps based on internal 296 representation of the components. 297 298 If the agent cannot determine the parent-relative position 299 for some reason, or if the associated value of 300 hpEntPhysicalContainedIn is '0', then the value '-1' is 301 returned. Otherwise a non-negative integer is returned, 302 indicating the parent-relative position of this physical 303 entity. 304 305 Parent-relative ordering normally starts from '1' and 306 continues to 'N', where 'N' represents the highest 307 positioned child entity. However, if the physical entities 308 (e.g. slots) are labeled from a starting position of zero, 309 then the first sibling should be associated with a 310 hpEntPhysicalParentRelPos value of '0'. Note that this 311 ordering may be sparse or dense, depending on agent 312 implementation. 313 314 The actual values returned are not globally meaningful, as 315 each 'parent' component may use different numbering 316 algorithms. The ordering is only meaningful among siblings 317 of the same parent component. 318 319 The agent should retain parent-relative position values 320 across reboots, either through algorithmic assignment or use 321 of non-volatile storage." 322 ::= { hpEntPhysicalEntry 6 } 323 324 325hpEntPhysicalName OBJECT-TYPE 326 SYNTAX DisplayString 327 MAX-ACCESS read-only 328 STATUS obsolete 329 DESCRIPTION 330 "The textual name of the physical entity. The value of this 331 object should be the name of the component as assigned by 332 the local device and should be suitable for use in commands 333 entered at the device's `console'. This might be a text 334 name, such as `console' or a simple component number (e.g. 335 port or module number), such as `1', depending on the 336 physical component naming syntax of the device. 337 338 If there is no local name, or this object is otherwise not 339 340 341 342 343 344 345 346 347 348 349 350 applicable, then this object contains a zero-length string. 351 352 Note that the value of hpEntPhysicalName for two physical 353 entities will be the same in the event that the console 354 interface does not distinguish between them, e.g., slot-1 355 and the card in slot-1." 356 ::= { hpEntPhysicalEntry 7 } 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406-- The Logical Entity Table 407hpEntLogicalTable OBJECT-TYPE 408 SYNTAX SEQUENCE OF HpEntLogicalEntry 409 MAX-ACCESS not-accessible 410 STATUS obsolete 411 DESCRIPTION 412 "This table contains one row per logical entity. At least 413 one entry must exist." 414 ::= { hpEntityLogical 1 } 415 416hpEntLogicalEntry OBJECT-TYPE 417 SYNTAX HpEntLogicalEntry 418 MAX-ACCESS not-accessible 419 STATUS obsolete 420 DESCRIPTION 421 "Information about a particular logical entity. Entities 422 may be managed by this agent or other SNMP agents (possibly) 423 in the same chassis." 424 INDEX { hpEntLogicalIndex } 425 ::= { hpEntLogicalTable 1 } 426 427HpEntLogicalEntry ::= SEQUENCE { 428 hpEntLogicalIndex INTEGER, 429 hpEntLogicalDescr DisplayString, 430 hpEntLogicalType AutonomousType, 431 hpEntLogicalCommunity OCTET STRING, 432 hpEntLogicalTAddress TAddress, 433 hpEntLogicalTDomain TDomain 434} 435 436hpEntLogicalIndex OBJECT-TYPE 437 SYNTAX INTEGER (1..2147483647) 438 MAX-ACCESS not-accessible 439 STATUS obsolete 440 DESCRIPTION 441 "The value of this object uniquely identifies the logical 442 entity. The value is a small positive integer; index values 443 for different logical entities are are not necessarily 444 contiguous." 445 ::= { hpEntLogicalEntry 1 } 446 447hpEntLogicalDescr OBJECT-TYPE 448 SYNTAX DisplayString 449 MAX-ACCESS read-only 450 STATUS obsolete 451 452 453 454 455 456 457 458 459 460 461 462 DESCRIPTION 463 "A textual description of the logical entity. This object 464 should contain a string which identifies the manufacturer's 465 name for the logical entity, and should be set to a distinct 466 value for each version of the logical entity. " 467 ::= { hpEntLogicalEntry 2 } 468 469hpEntLogicalType OBJECT-TYPE 470 SYNTAX AutonomousType 471 MAX-ACCESS read-only 472 STATUS obsolete 473 DESCRIPTION 474 "An indication of the type of logical entity. This will 475 typically be the OBJECT IDENTIFIER name of the node in the 476 SMI's naming hierarchy which represents the major MIB 477 module, or the majority of the MIB modules, supported by the 478 logical entity. For example: 479 a logical entity of a regular host/router -> mib-2 480 a logical entity of a 802.1d bridge -> dot1dBridge 481 a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt 482 If an appropriate node in the SMI's naming hierarchy cannot 483 be identified, the value 'mib-2' should be used." 484 ::= { hpEntLogicalEntry 3 } 485 486hpEntLogicalCommunity OBJECT-TYPE 487 SYNTAX OCTET STRING (SIZE (1..255)) 488 MAX-ACCESS read-only 489 STATUS obsolete 490 DESCRIPTION 491 "An SNMPv1 or SNMPv2C community-string which can be used to 492 access detailed management information for this logical 493 entity. The agent should allow read access with this 494 community string (to an appropriate subset of all managed 495 objects) and may also choose to return a community string 496 based on the privileges of the request used to read this 497 object. Note that an agent may choose to return a community 498 string with read-only privileges, even if this object is 499 accessed with a read-write community string. However, the 500 agent must take care not to return a community string which 501 allows more privileges than the community string used to 502 access this object. 503 504 A compliant SNMP agent may wish to conserve naming scopes by 505 representing multiple logical entities in a single 'main' 506 naming scope. This is possible when the logical entities 507 508 509 510 511 512 513 514 515 516 517 518 represented by the same value of hpEntLogicalCommunity have no 519 object instances in common. For example, 'bridge1' and 520 'repeater1' may be part of the main naming scope, but at 521 least one additional community string is needed to represent 522 'bridge2' and 'repeater2'. 523 524 Logical entities 'bridge1' and 'repeater1' would be 525 represented by sysOREntries associated with the 'main' 526 naming scope. 527 528 For agents not accessible via SNMPv1 or SNMPv2C, the value 529 of this object is the empty-string." 530 ::= { hpEntLogicalEntry 4 } 531 532hpEntLogicalTAddress OBJECT-TYPE 533 SYNTAX TAddress 534 MAX-ACCESS read-only 535 STATUS obsolete 536 DESCRIPTION 537 "The transport service address by which the logical entity 538 receives network management traffic, formatted according to 539 the corresponding value of hpEntLogicalTDomain. 540 541 For snmpUDPDomain, a TAddress is 6 octets long, the initial 542 4 octets containing the IP-address in network-byte order and 543 the last 2 containing the UDP port in network-byte order. 544 Consult 'Transport Mappings for Version 2 of the Simple 545 Network Management Protocol' (RFC 1906 [8]) for further 546 information on snmpUDPDomain." 547 ::= { hpEntLogicalEntry 5 } 548 549hpEntLogicalTDomain OBJECT-TYPE 550 SYNTAX TDomain 551 MAX-ACCESS read-only 552 STATUS obsolete 553 DESCRIPTION 554 "Indicates the kind of transport service by which the 555 logical entity receives network management traffic. 556 Possible values for this object are presently found in the 557 Transport Mappings for SNMPv2 document (RFC 1906 [8])." 558 ::= { hpEntLogicalEntry 6 } 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574hpEntLPMappingTable OBJECT-TYPE 575 SYNTAX SEQUENCE OF HpEntLPMappingEntry 576 MAX-ACCESS not-accessible 577 STATUS obsolete 578 DESCRIPTION 579 "This table contains zero or more rows of logical entity to 580 physical equipment associations. For each logical entity 581 known by this agent, there are zero or more mappings to the 582 physical resources which are used to realize that logical 583 entity. 584 585 An agent should limit the number and nature of entries in 586 this table such that only meaningful and non-redundant 587 information is returned. For example, in a system which 588 contains a single power supply, mappings between logical 589 entities and the power supply are not useful and should not 590 be included. 591 592 Also, only the most appropriate physical component which is 593 closest to the root of a particular containment tree should 594 be identified in an hpEntLPMapping entry. 595 596 For example, suppose a bridge is realized on a particular 597 module, and all ports on that module are ports on this 598 bridge. A mapping between the bridge and the module would be 599 useful, but additional mappings between the bridge and each 600 of the ports on that module would be redundant (since the 601 hpEntPhysicalContainedIn hierarchy can provide the same 602 information). If, on the other hand, more than one bridge 603 was utilizing ports on this module, then mappings between 604 each bridge and the ports it used would be appropriate. 605 606 Also, in the case of a single backplane repeater, a mapping 607 for the backplane to the single repeater entity is not 608 necessary." 609 ::= { hpEntityMapping 1 } 610 611hpEntLPMappingEntry OBJECT-TYPE 612 SYNTAX HpEntLPMappingEntry 613 MAX-ACCESS not-accessible 614 STATUS obsolete 615 DESCRIPTION 616 "Information about a particular logical entity to physical 617 equipment association. Note that the nature of the 618 association is not specifically identified in this entry. It 619 620 621 622 623 624 625 626 627 628 629 630 is expected that sufficient information exists in the MIBs 631 used to manage a particular logical entity to infer how 632 physical component information is utilized." 633 INDEX { hpEntLogicalIndex, hpEntLPPhysicalIndex } 634 ::= { hpEntLPMappingTable 1 } 635 636HpEntLPMappingEntry ::= SEQUENCE { 637 hpEntLPPhysicalIndex PhysicalIndex 638} 639 640hpEntLPPhysicalIndex OBJECT-TYPE 641 SYNTAX PhysicalIndex 642 MAX-ACCESS read-only 643 STATUS obsolete 644 DESCRIPTION 645 "The value of this object identifies the index value of a 646 particular hpEntPhysicalEntry associated with the indicated 647 hpEntLogicalEntity." 648 ::= { hpEntLPMappingEntry 1 } 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686-- logical entity/component to alias table 687hpEntAliasMappingTable OBJECT-TYPE 688 SYNTAX SEQUENCE OF HpEntAliasMappingEntry 689 MAX-ACCESS not-accessible 690 STATUS obsolete 691 DESCRIPTION 692 "This table contains zero or more rows, representing 693 mappings of logical entity and physical component to 694 external MIB identifiers. Each physical port in the system 695 may be associated with a mapping to an external identifier, 696 which itself is associated with a particular logical 697 entity's naming scope. A 'wildcard' mechanism is provided to 698 indicate that an identifier is associated with more than one 699 logical entity." 700 ::= { hpEntityMapping 2 } 701 702hpEntAliasMappingEntry OBJECT-TYPE 703 SYNTAX HpEntAliasMappingEntry 704 MAX-ACCESS not-accessible 705 STATUS obsolete 706 DESCRIPTION 707 "Information about a particular physical equipment, logical 708 entity to external identifier binding. Each logical 709 entity/physical component pair may be associated with one 710 alias mapping. The logical entity index may also be used as 711 a 'wildcard' (refer to the hpEntAliasLogicalIndexOrZero object 712 DESCRIPTION clause for details.) 713 714 Note that only hpEntPhysicalIndex values which represent 715 physical ports (i.e. associated hpEntPhysicalClass value is 716 'port(10)') are permitted to exist in this table." 717 INDEX { hpEntPhysicalIndex, hpEntAliasLogicalIndexOrZero } 718 ::= { hpEntAliasMappingTable 1 } 719 720HpEntAliasMappingEntry ::= SEQUENCE { 721 hpEntAliasLogicalIndexOrZero INTEGER, 722 hpEntAliasMappingIdentifier RowPointer 723} 724 725hpEntAliasLogicalIndexOrZero OBJECT-TYPE 726 SYNTAX INTEGER (0..2147483647) 727 MAX-ACCESS not-accessible 728 STATUS obsolete 729 DESCRIPTION 730 "The value of this object uniquely identifies the logical 731 732 733 734 735 736 737 738 739 740 741 742 entity which defines the naming scope for the associated 743 instance of the 'hpEntAliasMappingIdentifier' object. 744 745 If this object has a non-zero value, then it identifies the 746 logical entity named by the same value of hpEntLogicalIndex. 747 748 If this object has a value of zero, then the mapping between 749 the physical component and the alias identifier for this 750 hpEntAliasMapping entry is associated with all unspecified 751 logical entities. That is, a value of zero (the default 752 mapping) identifies any logical entity which does not have 753 an explicit entry in this table for a particular 754 hpEntPhysicalIndex/hpEntAliasMappingIdentifier pair. 755 756 For example, to indicate that a particular interface (e.g. 757 physical component 33) is identified by the same value of 758 ifIndex for all logical entities, the following instance 759 might exist: 760 761 hpEntAliasMappingIdentifier.33.0 = ifIndex.5 762 763 In the event an hpEntPhysicalEntry is associated differently 764 for some logical entities, additional hpEntAliasMapping 765 entries may exist, e.g.: 766 767 hpEntAliasMappingIdentifier.33.0 = ifIndex.6 768 hpEntAliasMappingIdentifier.33.4 = ifIndex.1 769 hpEntAliasMappingIdentifier.33.5 = ifIndex.1 770 hpEntAliasMappingIdentifier.33.10 = ifIndex.12 771 772 Note that entries with non-zero hpEntAliasLogicalIndexOrZero 773 index values have precedence over any zero-indexed entry. In 774 this example, all logical entities except 4, 5, and 10, 775 associate physical entity 33 with ifIndex.6." 776 ::= { hpEntAliasMappingEntry 1 } 777 778 779hpEntAliasMappingIdentifier OBJECT-TYPE 780 SYNTAX RowPointer 781 MAX-ACCESS read-only 782 STATUS obsolete 783 DESCRIPTION 784 "The value of this object identifies a particular conceptual 785 row associated with the indicated hpEntPhysicalIndex and 786 hpEntLogicalIndex pair. 787 788 789 790 791 792 793 794 795 796 797 798 Since only physical ports are modeled in this table, only 799 entries which represent interfaces or ports are allowed. If 800 an ifEntry exists on behalf of a particular physical port, 801 then this object should identify the associated 'ifEntry'. 802 For repeater ports, the appropriate row in the 803 'rptrPortGroupTable' should be identified instead. 804 805 For example, suppose a physical port was represented by 806 hpEntPhysicalEntry.3, hpEntLogicalEntry.15 existed for a 807 repeater, and hpEntLogicalEntry.22 existed for a bridge. Then 808 there might be two related instances of 809 hpEntAliasMappingIdentifier: 810 hpEntAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2 811 hpEntAliasMappingIdentifier.3.22 == ifIndex.17 812 It is possible that other mappings (besides interfaces and 813 repeater ports) may be defined in the future, as required. 814 815 Bridge ports are identified by examining the Bridge MIB and 816 appropriate ifEntries associated with each 'dot1dBasePort', 817 and are thus not represented in this table." 818 ::= { hpEntAliasMappingEntry 2 } 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854-- physical mapping table 855hpEntPhysicalContainsTable OBJECT-TYPE 856 SYNTAX SEQUENCE OF HpEntPhysicalContainsEntry 857 MAX-ACCESS not-accessible 858 STATUS obsolete 859 DESCRIPTION 860 "A table which exposes the container/containee relationships 861 between physical entities. This table provides equivalent 862 information found by constructing the virtual containment 863 tree for a given hpEntPhysicalTable but in a more direct 864 format." 865 ::= { hpEntityMapping 3 } 866 867hpEntPhysicalContainsEntry OBJECT-TYPE 868 SYNTAX HpEntPhysicalContainsEntry 869 MAX-ACCESS not-accessible 870 STATUS obsolete 871 DESCRIPTION 872 "A single container/containee relationship." 873 INDEX { hpEntPhysicalIndex, hpEntPhysicalChildIndex } 874 ::= { hpEntPhysicalContainsTable 1 } 875 876HpEntPhysicalContainsEntry ::= SEQUENCE { 877 hpEntPhysicalChildIndex PhysicalIndex 878} 879 880hpEntPhysicalChildIndex OBJECT-TYPE 881 SYNTAX PhysicalIndex 882 MAX-ACCESS read-only 883 STATUS obsolete 884 DESCRIPTION 885 "The value of hpEntPhysicalIndex for the contained physical 886 entity." 887 ::= { hpEntPhysicalContainsEntry 1 } 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910-- last change time stamp for the whole MIB 911hpEntLastChangeTime OBJECT-TYPE 912 SYNTAX TimeStamp 913 MAX-ACCESS read-only 914 STATUS obsolete 915 DESCRIPTION 916 "The value of sysUpTime at the time any of these events 917 occur: 918 * a conceptual row is created or deleted in any 919 of these tables: 920 - hpEntPhysicalTable 921 - hpEntLogicalTable 922 - hpEntLPMappingTable 923 - hpEntAliasMappingTable 924 - hpEntPhysicalContainsTable 925 926 * any instance in the following list of objects 927 changes value: 928 - hpEntPhysicalDescr 929 - hpEntPhysicalVendorType 930 - hpEntPhysicalContainedIn 931 - hpEntPhysicalClass 932 - hpEntPhysicalParentRelPos 933 - hpEntPhysicalName 934 - hpEntLogicalDescr 935 - hpEntLogicalType 936 - hpEntLogicalCommunity 937 - hpEntLogicalTAddress 938 - hpEntLogicalTDomain 939 - hpEntAliasMappingIdentifier " 940 ::= { hpEntityGeneral 1 } 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966-- Entity MIB Trap Definitions 967hpEntityMIBTraps OBJECT IDENTIFIER ::= { hpEntityMIB 2 } 968hpEntityMIBTrapPrefix OBJECT IDENTIFIER ::= { hpEntityMIBTraps 0 } 969 970hpEntConfigChange NOTIFICATION-TYPE 971 STATUS obsolete 972 DESCRIPTION 973 "An hpEntConfigChange trap is sent when the value of 974 hpEntLastChangeTime changes. It can be utilized by an NMS to 975 trigger logical/physical entity table maintenance polls. 976 977 An agent must not generate more than one hpEntConfigChange 978 'trap-event' in a five second period, where a 'trap-event' 979 is the transmission of a single trap PDU to a list of trap 980 destinations. If additional configuration changes occur 981 within the five second 'throttling' period, then these 982 trap-events should be suppressed by the agent. An NMS should 983 periodically check the value of hpEntLastChangeTime to detect 984 any missed hpEntConfigChange trap-events, e.g. due to 985 throttling or transmission loss." 986 ::= { hpEntityMIBTrapPrefix 1 } 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022-- conformance information 1023hpEntityConformance OBJECT IDENTIFIER ::= { hpEntityMIB 3 } 1024 1025hpEntityCompliances OBJECT IDENTIFIER ::= { hpEntityConformance 1 } 1026hpEntityGroups OBJECT IDENTIFIER ::= { hpEntityConformance 2 } 1027 1028-- compliance statements 1029 1030hpEntityCompliance MODULE-COMPLIANCE 1031 STATUS obsolete 1032 DESCRIPTION 1033 "The compliance statement for SNMP entities which implement 1034 the Entity MIB." 1035 MODULE -- this module 1036 MANDATORY-GROUPS { hpEntityPhysicalGroup, 1037 hpEntityLogicalGroup, 1038 hpEntityMappingGroup, 1039 hpEntityGeneralGroup, 1040 hpEntityNotificationsGroup } 1041 ::= { hpEntityCompliances 1 } 1042 1043-- MIB groupings 1044 1045hpEntityPhysicalGroup OBJECT-GROUP 1046 OBJECTS { 1047 hpEntPhysicalDescr, 1048 hpEntPhysicalVendorType, 1049 hpEntPhysicalContainedIn, 1050 hpEntPhysicalClass, 1051 hpEntPhysicalParentRelPos, 1052 hpEntPhysicalName 1053 } 1054 STATUS obsolete 1055 DESCRIPTION 1056 "The collection of objects which are used to represent 1057 physical system components, for which a single agent 1058 provides management information." 1059 ::= { hpEntityGroups 1 } 1060 1061hpEntityLogicalGroup OBJECT-GROUP 1062 OBJECTS { 1063 hpEntLogicalDescr, 1064 hpEntLogicalType, 1065 hpEntLogicalCommunity, 1066 hpEntLogicalTAddress, 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 hpEntLogicalTDomain 1079 } 1080 STATUS obsolete 1081 DESCRIPTION 1082 "The collection of objects which are used to represent the 1083 list of logical entities for which a single agent provides 1084 management information." 1085 ::= { hpEntityGroups 2 } 1086 1087hpEntityMappingGroup OBJECT-GROUP 1088 OBJECTS { 1089 hpEntLPPhysicalIndex, 1090 hpEntAliasMappingIdentifier, 1091 hpEntPhysicalChildIndex 1092 } 1093 STATUS obsolete 1094 DESCRIPTION 1095 "The collection of objects which are used to represent the 1096 associations between multiple logical entities, physical 1097 components, interfaces, and port identifiers for which a 1098 single agent provides management information." 1099 ::= { hpEntityGroups 3 } 1100 1101hpEntityGeneralGroup OBJECT-GROUP 1102 OBJECTS { 1103 hpEntLastChangeTime 1104 } 1105 STATUS obsolete 1106 DESCRIPTION 1107 "The collection of objects which are used to represent 1108 general entity information for which a single agent provides 1109 management information." 1110 ::= { hpEntityGroups 4 } 1111 1112hpEntityNotificationsGroup NOTIFICATION-GROUP 1113 NOTIFICATIONS { hpEntConfigChange } 1114 STATUS obsolete 1115 DESCRIPTION 1116 "The collection of notifications used to indicate Entity MIB 1117 data consistency and general status information." 1118 ::= { hpEntityGroups 5 } 1119 1120 1121END 1122