Update HPOVLogicalEnclosureFirmware - HewlettPackard/POSH-HPEOneView GitHub Wiki

HPE OneView 4.10 Library

Update-HPOVLogicalEnclosureFirmware

Initiate Logical Enclosure Firmware update.

SYNTAX

Update-HPOVLogicalEnclosureFirmware [-InputObject] <Object> [-Baseline] <HPOneView.Appliance.Baseline> [-FirmwareUpdateProcess] <String>[ [-InterconnectActivationMode] <String>][ [-ForceInstallation] <SwitchParameter>][ [-Async] <SwitchParameter>][ [-ApplianceConnection] <Array>] [-WhatIf] <> [-Confirm] <> [<CommonParameters>]

Detailed Description

You can update firmware from a logical enclosure for shared infrastructure, shared infrastructure and profiles, and OA (Onboard Administrators) only, if any. When you update the firmware for an enclosure associated with a logical enclosure, the firmware baseline configured for the logical enclosure sets the baseline on the enclosure and each of the logical interconnects in the enclosure, as well as the OA. Firmware is updated in the following order:

* Onboard Administrators
* Logical interconnects
* Server hardware and their associated server profiles

The Orchestrated activation option allows nondisruptive updates of interconnects in a production ready, properly configured, and redundant environment. Orchestrated firmware updates do not affect the network traffic and no outages are caused while the update process is in progress as one virtual connect module is always forwarding network traffic, with no or minimal impact to application network connection. A default delay of 8 minutes is set between activating or rebooting interconnect modules. Hypervisor clusters are updated nondisruptively when the orchestrated activation option is chosen. If the logical enclosure contains one or more hypervisor profiles, each hypervisor is serially placed into a maintenance mode before updating. It can take up to 90 minutes to place a hypervisor into the maintenance mode, perform the firmware update, and take it back out of the maintenance mode. Parallel activation activates all the interconnect modules at the same time, resulting in disruption of the network and storage connectivity. It is recommended to perform parallel activation during a maintenance window when you can better coordinate the downtime. When selecting "SharedInfrastructureAndServerProfiles" firmware update process, any servers without profiles will perform an automated offline firmware update. Assigned Server Profiles will require HPE Smart Update Tools (HPSUT, iSUT) to be installed and available. Required Privileges: Infrastructure administrator or Server administrator

Parameters

-ApplianceConnection <Array>

Aliases [-Appliance]

Specify one or more HPOneView.Appliance.Connection object(s) or Name property value(s).

Default Value: ${Global:ConnectedSessions} | ? Default

Aliases Appliance
Required? False
Position? named
Default value (${Global:ConnectedSessions} | ? Default)
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters?    False

-Async <SwitchParameter>

Use this parameter to immediately return the async task. By default, the Cmdlet will wait for the task to complete.

Aliases None
Required? False
Position? named
Default value False
Accept pipeline input? false
Accept wildcard characters?    False

-Baseline <HPOneView.Appliance.Baseline>

The firmware bundle or baseline to install.

Aliases None
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters?    False

-Confirm <>

Aliases cf
Required?
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters?    False

-FirmwareUpdateProcess <String>

Specify the type of firmware update to invoke. Allowed values:

* EnclosureOnly - Will only upgrade enclosure or frame components (c-Class Onboard Administrator, Synergy Frame Link Module)
* SharedInfrastructureOnly
* SharedInfrastructureAndServerProfiles
Aliases None
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters?    False

-ForceInstallation <SwitchParameter>

Force the re-installation or downgrade of components within the baseline.

Aliases None
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters?    False

-InputObject <Object>

The HPOneView.LogicalEnclosure from Get-HPOVLogicalEnclosure.

Aliases le, LogicalEnclosure
Required? true
Position? named
Default value
Accept pipeline input? true (ByValue)
Accept wildcard characters?    False

-InterconnectActivationMode <String>

Specify the logical interconnect activation mode. Choosing "Parallel" is the fastest update operation but will require downtime and servers to be powered off. Allowed values:

* Orchestrated
* Parallel Default: Orchestrated
Aliases None
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters?    False

-WhatIf <>

Aliases wi
Required?
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters?    False

<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Input Types

HPOneView.LogicalEnclosure [System.Management.Automation.PSCustomObject]

Logical enclosure resource from Get-HPOVLogicalEnclosure.

Return Values

HPOneView.Appliance.TaskResource [System.Management.Automation.PSCustomObject]

Asyncronous task resource to monitor.

Examples

 -------------------------- EXAMPLE 1 --------------------------

$Basline = Get-HPOVBaseline -Name "HPE Service Pack for ProLiant" -ErrorAction Stop Get-HPOVLogicalEnclosure -Name Encl1 -ErrorAction Stop | Update-HPOVLogicalEnclosureFirmware -Baseline $Basline -FirmwareUpdateProcess SharedInfrastructureOnly

Get the specified baseline, and update the specified logical enclosure's shared infrastructure only.

Related Links


Top
⚠️ **GitHub.com Fallback** ⚠️