Driver Support Document

EXT_HP & Aruba ProCurve switches, OS versions A.14, A.15, E.8-11, F.4-5, G.07, H.7-10, I.7-10, J.14, J.15, K.11-K.15, KA.15-16, KB.15-16, L.10-11, M.08, M.10, N.11, Q.11, RA.15-16, S.14, S.15, T.11, T.12, T.13, U.11, W.14, W.15, Y.11, Z.14,YA.15,WB.15

• Internal Driver Name: EXT_HP_ProCurve
• Driver Package: EXT_HP_ProCurve.rdp
  
• Driver Tier: 3
• Vendor: HPE
• Family: HP ProCurve
• IPv6 Support: Yes

Show Tested Devices Grid

Driver Features Support Grid

General Access

Release Notes

Separate username for enable mode

ProCurve devices support using a separate named account when entering enable mode from a limited privilege account. If a separate username is required, set the device access variable "enable_username" to contain this account name. If no variable is set and a username prompt is encountered by the 'enable' command, the login username will be used.

Disabling context management

The context management feature adds independent device entries for contexts on the device automatically by using the inventory diagnostic. This feature can be disabled by adding the access variable "disable_context" and setting it to true. Disabling the feature will remove any previously created context devices permanently and will result in the inability to directly manage contexts with NA. Changes will take effect the next time the NA Module Status diagnostic task is run.

return to top

Retrieve Running Configuration

Release Notes

CLI and SCP configurations variations

Some ProCurve devices report their configuration slightly differenly when collected with SCP versus CLI methods. This inconsistency often manifests as different interpretation/formatting of the banner command between the two configuration retrieval modes.

return to top

Software Center

Release Notes

Update Device Software task

Some ProCurve models do not support setting a default boot image after software update. When rebooted the device will always reboot to the "Primary" flash image.

return to top

Driver Discovery

Release Notes

More prompt causes an unexpected disconnection

Discovery tasks for Javascript drivers handle More prompts by using timeouts, which can cause problems with the third-party SSH client code, which interprets the timeout as a disconnection. There are two options to work around the problem. Setting the RCX option [<option name="Driver/Discovery/UsePollRead">true</option>] in site_options.rcx will effect the workaround for all affected devices. Alternatively, it could be applied to a single device by setting the device access variable "PollRead" to "true".

Wakeup Ctrl-U character can cause discovery to fail

Discovery tasks for Javascript drivers use wakeup characters are sent during device connection, to ensure that the device is responding. Normally, these characters do not echo to the console, but some devices may echo them. In this case, this causes the prompt detection phase to fail, which in turn can cause More prompts to not be handled properly, and discovery may fail. If these characters are echoed from the device [check the session log to see this], then set the device access variable "skip_ctrl_u" to skip the sending of the wakeup characters. Note that setting this option on a previously working device could cause discovery tasks to fail, but it only affects CLI discovery. SNMP discovery is unaffected.

return to top

Syslog Triggering

Trigger Patterns

Devices supported by this driver trigger changes using the following patterns:
MANAGER Mode
device status changed ?:
Running Config Change
SME TELNET from


User Patterns

These patterns are used to determine the username/IP responsible for a change:
/User '(\S+)' logged in from/
/User-Name='(\S+?)'/

return to top