solution Contentsolution Content

HP Web Jetadmin - Volatile Configuration and HP Web Jetadmin Configuration Templates

Some actions performed remotely on devices can cause the device to automatically power cycle or change in some other way that can impact the success of further configuration.

Consider the case where you are attempting to configure several device parameters, including one parameter that causes the device to reset itself, which also causes HP Web Jetadmin to lose communication with the device for a time. Changing a device's IP parameters is a good example. The device (in many cases) re-initializes and stops communicating for a time.

HP Web Jetadmin has several configuration elements that are known to cause device interrupts and, therefore, cause a configuration to become volatile or unstable. These items are programmatically marked in such a way that HP Web Jetadmin always uses them last in a configuration. These configuration items are:

  • Security > LDAP - Accessing the Server

  • Digital Sending > Activity Log

  • Fax > Fax Reports and Logs (print or clear activity log)

  • Security > Disable Direct Ports

  • Network > Protocol Stacks

  • Network > IPv4 Information, which includes Subnet Mask and Gateway (both single and batch configurations)

  • Wireless > 802.11 a/b/g

  • Network > Link Setting

  • File System > File System Password

  • Security > Get Community Name

  • Security > Set Community Name

  • Security > SNMP Version Access Control

In any configuration, whether it is performed for a single device, for multiple devices, or with a configuration template, these settings are always sent to the device last to improve the chance of successful configurations. The following considerations should be made with these settings:

  • The chances of a configuration failure increase when these settings are used in the same configuration.

  • HP Web Jetadmin only marks these items to run last. HP Web Jetadmin does not put these items in any order relative to the other items listed here.

  • Device behaviors, while sometimes predictable, are not fully documented with these known configuration items.

In summary, not all of the HP Web Jetadmin configurations can guarantee a positive and stable result at the physical device. You might need to test individual configuration options to understand the effects on various HP device models and determine if an HP Web Jetadmin configuration is successful. HP will continue best effort practices in documenting these and other known configuration characteristics.