This documentation refers to a previously released version of BMC Discovery.
See the information on this topic for the latest version (11.3) or version 11.1.

A Host Container node is used to model a system that acts as a container for hosts but is not a host itself. For example, a blade enclosure which is discovered via a management controller, or a hardware container for logical hosts such as a Oracle (Sun) StarFire system.

Blade enclosures are typically hardware containers which contain a number of physical hosts, a management controller, and various network modules such as network and/or SAN switches.

In Oracle (Sun) StarFire systems, a single hardware device is partitioned into a number of logical hosts. The existence of the hardware device can be inferred from the details of the logical hosts, but it is never directly seen as a network connected device.

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.

Creation (blade enclosure)

When a chassis Management controller is discovered, this is modeled as a Management Controller node. The creation of a Management Controller node triggers an additional pattern which creates the Host Container node and collects additional information on the contents of the enclosure, and triggers further patterns to relate the components (physical hosts, a management controller, and various network modules such as network and/or SAN switches).

Some host containers, such as the Sun Blade 6000 system, may need to be scanned twice before all relationships are created.

Creation (physical container of logical hosts)

Host Containers of this type 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.

Update (blade enclosure)

When a Management Controller node is updated, the related Host Container is updated accordingly.

Update (physical container of logical hosts)

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.

Removal (blade enclosure)

A Host Container node is removed when it no longer contains any hosts and it no longer has an associated Network Device or management controller.

Removal (physical container of logical hosts)

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:

UI Name
Attribute Name and Type

Description

Type
type string

Type of host container.

Hardware Vendor
vendor string

Hardware vendor of the Host Container.

Model
model string

Hardware model.

Serial Number
serial string

Serial number of the Host Container.

Not displayed in UI
hostid_range list:string

Range of host ids contained in this container.

System Identifier
systemid string

IBM Power Systems System Identifier.

Not displayed in UI
asset_tag string

Dell asset tag.

Key
key string

Globally unique key.

Name
name string

The name that the Host Container is known by.

Short Name
short_name string

The short name.

Description
description string

Description of the Host Container. Legacy attribute not currently used. Can be used by patterns if desired.

URL
url string

URL for information about the Host Container. Legacy attribute not currently used. Can be used by patterns if desired.

Business Continuity Critical
business_continuity_critical boolean

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
third_party_support boolean

If true, the Host Container is supported by a third party. Legacy attribute not currently used. Can be used by patterns if desired.

Synonyms
synonyms string

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:

UI name

Relationship

Description

Host Members

HostContainer:
HostContainer:
HostContainment:
ContainedHost:
Host

Hosts that are within this container.

Network Device Members

HostContainer:
HostContainer:
HostContainment:
Contained:
NetworkDevice

Network Devices that are within this container.

SNMP Managed Device Members

HostContainer:
HostContainer:
HostContainment:
Contained:
SNMPManagedDevice

SNMP Managed Devices that are within this container.

Management Controller Members

HostContainer:
HostContainer:
HostContainment:
ContainedHost:
ManagementController

Management Controllers that are within this container.

Managed by Software Instance

HostContainer:
ManagedElement:
Management:
Manager:
SoftwareInstance

Software Instances that manage this container.

Managed by SNMP Managed Device

HostContainer:
ManagedElement:
Management:
Manager:
SNMPManagedDevice

SNMP Managed Device that manages this container.

Managed by Management Controller

HostContainer:
ManagedElement:
Management:
Manager:
ManagementController

Management Controller that manages this container.

Not displayed in UI

HostContainer:
Element:
Maintainer:
Pattern:
Pattern

Pattern that is maintaining this container.

Details

HostContainer:
ElementWithDetail:
Detail:
Detail:
Detail

Details for this container.

Not displayed in UI

HostContainer:
AttachmentContainer:
Attachment:
Attachment:
Attachment

A file attached to this element.

Status

HostContainer:
ElementInCategory:
ElementCategory:
Category:
LifecycleStatus

The lifecycle status of this element.

Recovery Time

HostContainer:
ElementInCategory:
ElementCategory:
Category:
RecoveryTime

The recovery time specified for this element.

Family

HostContainer:
ElementInCategory:
ElementCategory:
Category:
Family

Family of this element.

Organizational Unit

HostContainer:
OwnedItem:
Ownership:
Owner:
OrganisationalUnit

The Organizational Unit that this element belongs to.

Location

HostContainer:
ElementInLocation:
Location:
Location:
Location

Location of this element.

Support Manager

HostContainer:
OwnedItem:
Ownership:
SupportOwner:
Person

The person responsible for the support of this element.

Business Owner

HostContainer:
OwnedItem:
Ownership:
BusinessOwner:
Person

The person responsible for this element from a business perspective.

IT Owner

HostContainer:
OwnedItem:
Ownership:
ITOwner:
Person

The person responsible for this element from an IT perspective.

Processor Information

HostContainer:
HostContainer:
Detail:
Hardware:
ProcessorInfo

Processor information.

Was this page helpful? Yes No Submitting... Thank you
  • No labels
© Copyright 2004 - 2019 BMC Software, Inc.
Legal notices