HP Web Jetadmin Software Manuale Utente Scaricare il pdf (Pagina 11)

This same Firmware upgrade options window allows for defining multiple threads to perform firmware

upgrades in a parallel fashion rather than serially by using the Maximum concurrent upgrades setting.

The default setting is to upgrade 8 devices simultaneously. For HP Web Jetadmin 10.3 SR8 and later,

this setting can be increased to 50 devices in a single task.

WARNING! Increasing the Maximum concurrent upgrades to a value above 10 should only be done

on powerful servers that have limited tasks beside the firmware upgrades.

Note If the maximum number of concurrent firmware upgrades is set to 11 or higher, the

FirmwareUpgradeThreadsize section in the PerfomanceTuning.config.xml file must also

be changed to match the value specified in the Maximum concurrent upgrades box. For

instructions on changing the FirmwareUpgradeThreadsize section, see Increase the

firmware upgrade thread pool size on page 12.

Firmware installation is faster when multiple devices are upgraded at the same time, but more network

traffic is generated. Operating limitations might also restrict how many devices can receive upgrades

simultaneously. This setting applies to the number of devices inside a single task or multiple tasks; 50

tasks is the maximum regardless.

If it is still taking too long to perform batch firmware upgrades, one additional technique can be used

to significantly decrease the time it takes to complete a batch firmware upgrade process. There is a

trade-off in the accuracy of reporting status, but the gains in time can be very significant.

The normal process for upgrading device firmware involves opening a thread, sending the firmware

file through either a port 9100 connection or Web Services connection, monitoring the upgrade

status on the device until it completes its power cycle and reports that the new firmware is in place,

and then closing the thread. If the maximum thread count is set to 10, after all 10 threads complete

the process, 10 more threads are attempted. This technique allows HP Web Jetadmin to very

accurately report success or failure. However, the constant status checking after delivering the

firmware file can take upwards of 90% of the total time to complete the process.

HP Web Jetadmin 10.3 SR2 and later allows for manipulating the same FirmwareUpgrade.config.xml

file mentioned in the previous section to bypass the status-checking portion of the upgrade process.

This means that HP Web Jetadmin delivers the firmware file to the device and reports success after the

file is delivered in its entirety. This can eliminate potentially 90% of the transaction time per device,

meaning many more devices

are completed in a fraction of

the time when status checking is

employed.

Edit the following entries in the

FirmwareUpgrade.config.xml

file in the directory provided in

the previous section, and

change the settings to False to

bypass status checking for HP

Jetdirect and device firmware

and significantly speed up

batch upgrades:

<property

name="IsJetdirectMonitorRequired">

<type>HP.Imaging.Wjp.Sdk.Core.Framework.ConfigurationItemString

</type>

<value>False</value>

</property

<type>HP.Imaging.Wjp.Sdk.Core.Framework.ConfigurationItemString

Figure 15

—Firmware upgrade options

1 2 ... 6 7 8 9 10 11 12 13 14 15 16 ... 20 21

Commenti su questo manuale

Nessun commento

HP Web Jetadmin Software Manuale Utente Pagina 11

Commenti su questo manuale

Prodotti e manuali riguardandi no HP Web Jetadmin Software