Interconnect health statuses and states

When adding an interconnect, the appliance checks if an interconnect resource exists for the indicated location and if one does not exist, it creates one. Then the interconnect is identified and compared against the expected IO bay occupancy as indicated in the controlling logical interconnect. Based on the results the interconnect is placed into the appropriate state. Note that a resource is always created for the location regardless of whether the bay should be occupied or not.

Interconnect operation details

Health status

Activity

State

Description

Unknown

Task Active

Adding

Adding is nondestructive in that an existing interconnect resource could transition to the Adding state without undergoing a reset.

Critical

N/A

AddedWithErrors

Indicates that there should be an interconnect present but there was a problem communicating with the actual resource or in completing the initial discovery.

OK

N/A

Configured

The interconnect is configured and available to provide its intended service.

OK

N/A

Monitored

An interconnect is present and basic hardware information has been obtained.

OK

Task Active

Configuring

A new or updated configuration is being applied or reapplied to the interconnect.

Critical/Warning

N/A

ConfigError

An error occurred while configuring an interconnect. The appliance will attempt to return the interconnect to its previous configuration state, but it may need to be manually configured, or, refreshed by reapplying the interconnect configuration or an enclosure refresh.

Critical

N/A

Absent

The bay should contain an interconnect but is currently empty.

Unknown

N/A

Inventory

An interconnect physically resided in an IO bay which the appliance expects to be empty. This could be an accident or deliberate as in the case where an interconnect is intended to be managed outside of the appliance. Physically removing the interconnect from the enclosure will cause it to be deleted from the appliance.

Critical

N/A

Unsupported

The bay is supposed to be managed but the interconnect in the bay is not a supported interconnect type.

See the HPE OneView Support Matrix for a list of supported interconnects.

Critical

N/A

Unmanaged

The type of interconnect is supported, but the manager is not able to manage or configure the interconnect because the available capabilities do not meet the minimum desired. One reason for entering this state is if the discovered interconnect type does not match the desired interconnect type defined in the interconnect bay map. Another reason could be that the installed firmware is either not supported or does not provide for the minimum capabilities desired.

(Same as in previous state)

Task Active

Maintenance

Indicates that an interconnect is undergoing an automated or manual procedure that cannot be interrupted. Interconnect power, configuration, and status are not available while in this state. If configurations are pushed to the interconnect, they will be queued and applied once the interconnect has moved out of the Maintenance state.

When the interconnect is powered off, it goes into the Maintenance state so that configuration changes are not sent to an interconnect that is not powered on.

(Same as in previous state)

Task Active

Removing

The interconnect resource will be deleted from the database and the physical interconnect will be reset returning it to factory defaults. This can be initiated either explicitly by the user or implicitly.

Critical

N/A

Remove-Failed

The appliance is not able to communicate with an interconnect during a remove operation. The entity remains in database but it will not be managed. You may request a retry or forced delete to resolve this state.