A Host Container node is used to model a system that is logically partitioned into a number of hosts, but is not a directly discoverable host itself. Systems that contain a number of physically separate devices, such as blade enclosures, are modeled as a Hardware Container node.
Host Container nodes always have a relationship to the Pattern node corresponding to their maintaining pattern.
Host Container Lifecycle
The following section describes the scenarios in which a Host Container is created, updated or removed.
Host Containers are created when a pattern discovers conditions which enable it to detect a contained host. Once found, the pattern creates the Host Container that it needs. A relationship link is automatically created to the Host node and the Host Container will have a key generated. The generated key for a Host Container node is entirely dependent on the type of Host Container.
The update procedure for a Host Container is also under full control of patterns. When the pattern has identified a contained host, a key is generated for the Host Container. If a Host Container with that key already exists, the Host Container is updated accordingly.
The default destruction of a Host Container is not under the control of patterns. A Host Container node is removed when the last remaining contained Host node is unlinked and there is no longer any evidence for that host or any of its relationships, for example, to network devices, management controllers or any other root node kind. This is a Cascade Removal type, see Cascade Removal.
Host Container node attributes
The attributes of a Host Container node are as described in the following table:
Type of host container.
Hardware vendor of the Host Container.
Serial number of the Host Container.
Range of host ids contained in this container.
IBM Power Systems System Identifier.
Not displayed in UI
Dell asset tag.
Globally unique key.
The name that the Host Container is known by.
The short name.
Description of the Host Container. Legacy attribute not currently used. Can be used by patterns if desired.
URL for information about the Host Container. Legacy attribute not currently used. Can be used by patterns if desired.
Business Continuity Critical
If true, the Host Container is critical to operation of the business. Legacy attribute not currently used. Can be used by patterns if desired.
Supported by 3rd Party
If true, the Host Container is supported by a third party. Legacy attribute not currently used. Can be used by patterns if desired.
Other names by which this Host Container is known. Legacy attribute not currently used. Can be used by patterns if desired.
Host Container node relationships
The relationships on a Host Container node are as described in the following table:
Hosts that are within this container.
Network Device Members
Network Devices that are within this container.
SNMP Managed Device Members
SNMP Managed Devices that are within this container.
Management Controller Members
Management Controllers that are within this container.
Managed by Software Instance
Software Instances that manage this container.
Managed by SNMP Managed Device
SNMP Managed Device that manages this container.
Managed by Management Controller
Management Controller that manages this container.
Not displayed in UI
Pattern that is maintaining this container.
Details for this container.
Hardware Reference Data
Hardware Reference data corresponding to this container.
Hardware Support Detail related to this container.
Not displayed in UI
A file attached to this element.
The lifecycle status of this element.
The recovery time specified for this element.
Family of this element.
The Organizational Unit that this element belongs to.
Location of this element.
The person responsible for the support of this element.
The person responsible for this element from a business perspective.
The person responsible for this element from an IT perspective.