Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hpiDomainReferenceEntry",
"OBJECT-TYPE",
"SYNTAX",
"HpiDomainReferenceEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"The Domain Reference Table (DRT) which provides information about other domains associated with the domain. The two hpiDomainId are used to uniquely identify a domain and a corresponding domain which can be off peer or tiered domain architecture. The DRT contains an entry for each associated domain, and HPI MIB Users may read these entries to discover the presence of additional domains within a 'System'. The discovered domains can, in turn, be used to discover additional resources and domains. The DRT is automatically built and maintained by the HPI implementation. Domain entries in the DRT may change over time if the 'System' configuration changes. There are two types of domain references: - A peer domain architecture, which consists of two or more domains that are expected to contain the same resources and domain references. Each domain in a peer relationship contains an RPT listing all resources present in each domain. - A tiered (child) domain architecture is used when all the resources in a'system' cannot be accessed in a single domain. A 'parent' domain references one or more 'child' domains in its DRT. The 'child' domains may be simple domains containing only resources, or they may themselves be a 'parent' to other 'child' domains. Domains in a tiered relationship are disjointed and do not contain the same resources. Note: When a domain is added to the DRT (SAHPI_DOMAIN_REF_ADDED) and when a domain is removed from the DRT (SAHPI_DOMAIN_REF_REMOVED) an event is generated.\"",
"INDEX",
"{",
"hpiDomainId",
",",
"hpiDomainReferenceDomain",
"}",
"::=",
"{",
"hpiDomainReferenceTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"HpiDomainReferenceEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"The Domain Reference Table (DRT) which provides information about other domains associated with the domain. The two hpiDomainId are used to uniquely identify a domain and a corresponding domain which can be off peer or tiered domain architecture. The DRT contains an entry for each associated domain, and HPI MIB Users may read these entries to discover the presence of additional domains within a 'System'. The discovered domains can, in turn, be used to discover additional resources and domains. The DRT is automatically built and maintained by the HPI implementation. Domain entries in the DRT may change over time if the 'System' configuration changes. There are two types of domain references: - A peer domain architecture, which consists of two or more domains that are expected to contain the same resources and domain references. Each domain in a peer relationship contains an RPT listing all resources present in each domain. - A tiered (child) domain architecture is used when all the resources in a'system' cannot be accessed in a single domain. A 'parent' domain references one or more 'child' domains in its DRT. The 'child' domains may be simple domains containing only resources, or they may themselves be a 'parent' to other 'child' domains. Domains in a tiered relationship are disjointed and do not contain the same resources. Note: When a domain is added to the DRT (SAHPI_DOMAIN_REF_ADDED) and when a domain is removed from the DRT (SAHPI_DOMAIN_REF_REMOVED) an event is generated."
],
null,
null,
[
"INDEX",
[
[
0,
"hpiDomainId"
],
[
0,
"hpiDomainReferenceDomain"
]
]
],
null
]
}