HP 1606 Fabric OS MIB Reference v6.4.0 (53-1001768-01, June 2010) - Page 150

4 entLogicalTDomain 1.3.6.1.2.1.47.1.2.1.1.6 entLogicalTDomain 1.3.6.1.2.1.47.1.2.1.1.6 Indicates the kind of transport service by which the logical entity receives network management traffic. Possible values for this object are currently found in the Transport Mappings for SNMPv2 document (RFC1906). entLogicalContextEngineID 1.3.6.1.2.1.47.1.2.1.1.7 The authoritative contextEngineID that can be used to send an SNMP message concerning information held by this logical entity to the address specified by the associated entLogicalTAddress/entLogicalTDomain pair. This object, together with the associated entLogicalContextName object, defines the context associated with a particular logical entity; it allows access to SNMP engines identified by a contextEngineId and contextName pair. If no value has been configured by the agent, a zero-length string is returned, or the agent might choose not to instantiate this object at all. entLogicalContextName 1.3.6.1.2.1.47.1.2.1.1.8 The contextName that can be used to send an SNMP message concerning information held by this logical entity to the address specified by the associated entLogicalTAddress/entLogicalTDomain pair. This object, together with the associated entLogicalContextEngineID object, defines the context associated with a particular logical entity and allows access to SNMP engines identified by a contextEngineId and contextName pair. If no value has been configured by the agent, a zero-length string is returned, or the agent might choose not to instantiate this object at all. Entity Mapping group entLPMappingTable 1.3.6.1.2.1.47.1.3.1 This table contains zero or more rows of logical entity to physical equipment associations. For each logical entity known by this agent, there are zero or more mappings to the physical resources used to realize that logical entity. An agent should limit the number and nature of entries in this table such that only meaningful and nonredundant information is returned. For example, in a system that contains a single power supply, mappings between logical entities and the power supply are not useful and should not be included. Also, only the most appropriate physical component that is closest to the root of a particular containment tree should be identified in an entLPMapping entry. 132 Fabric OS MIB Reference 53-1001768-01