Driver Support Document

HP ProCurve switches 3500, 5400, 6600ml & 8200 series, OS version K.14.x & K.15.x; 6120 series, OS version Z.14.x; 3800 series, OS version KA.15.xx (OBSOLETE PLEASE REDISCOVER)

Show Tested Devices Grid

SYSOID Mapping
SYSOID MODEL OS VERSION
 1.3.6.1.4.1.11.2.3.7.11.58 3500yl-24G-PWR(J8692A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.59 3500yl-48G-PWR(J8693A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.50 5406zl(J8697A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.51 5412zl(J8698A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.60 6200yl(J8992A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.72 8212zl(J8715A,J9091A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.98 6600ml-24XG(J9265A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.100 6600ml-24G(J9263A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.101 6600ml-24G-4XG K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.105 6600-48G-4XG(J9452A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.106 6600-48G(J9451A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.109 3500-24-PoE(J9471A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.111 3500-24(J9470A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.113 8206zl(J9477A) K.14.x, K.15.x
 1.3.6.1.4.1.11.2.3.7.11.114 3500yl-24G-PoE (J9310A) K.14.x, K.15.03
 1.3.6.1.4.1.11.2.3.7.11.115 3500yl-48G-PoE (J9311A ) K.14.x, K.15.03
 1.3.6.1.4.1.11.2.3.7.11.112 3500-48 (J9472A ) K.14.x, K.15.03
 1.3.6.1.4.1.11.2.3.7.11.110 3500-48-PoE (J9473A) K.14.x, K.15.03
 1.3.6.1.4.1.11.2.3.7.11.107 6120XG (516733-B21) Z.14.04
 1.3.6.1.4.1.11.2.3.7.11.108 6120G/XG (498358-B21) Z.14.04
 1.3.6.1.4.1.11.2.3.7.11.119 3800-24G-PoE+-2SFP+ (J9573A) KA.15.03
 1.3.6.1.4.1.11.2.3.7.11.120 3800-48G-PoE+-4SFP+ (J9574A) KA.15.03
 1.3.6.1.4.1.11.2.3.7.11.121 3800-24G-2SFP+ (J9575A) KA.15.03
 1.3.6.1.4.1.11.2.3.7.11.122 3800-48G-4SFP+ (J9576A) KA.15.03
 1.3.6.1.4.1.11.2.3.7.11.123 3800-24SFP-2SFP+ (J9584A) KA.15.03
 1.3.6.1.4.1.11.2.3.7.8.5.2 3800 Stack KA.15.03

Driver Features Support Grid

Driver FeaturesAccess Methods
(X signifies feature support)CLISNMPTFTPCLI+TFTPSNMP+TFTPFTPCLI+FTPSNMP+FTPCLI+SFTPSCPCLI+SCPSNMP+SCPHTTP/HTTPS
  Driver Discovery release notes                          
X General Access release notes
(CLI protocols: telnet, ssh2, console)
Supports SecurID 		X     X           X      
Configuration
X Retrieve Running Configuration release notes X     X           X      
X Retrieve Startup Configuration   X     X           X      
  Retrieve Binary Configuration                            
X Device information parsing  
X Enhanced Layer2 Basic IP information parsing  
X Configuration Deployment to Running release notes       X           X      
X Configuration Deployment to Startup         X           X      
  Binary Configuration Deployment                            
Diagnostics
X Routing Table   X                        
X OSPF Neighbors   X                        
X Interfaces   X                        
X Modules and Inventory   X                        
  Flash Storage Space                            
X File System   X                        
X Uptime     X                      
X ICMP Test   X                        
X Topology Parsing   X                        
X Duplex Parsing   X                        
X Enhanced VLAN Parsing  
Features
X Software Center         X             X    
X Software Image Synchronization         X           X      
X Password Management  
(Can modify: full username, full password, read-only community strings, read/write community strings) 		X                        
X Syslog Configuration and Change Detection   Syslog patterns X                        
X Custom Scripts and Diagnostics  
Bulk deploy available 		X                        
X ACL Parsing  
X ACL Provisioning   X                        
X VLAN Provisioning   X                        
X Configlet Parsing  
X QoS Parsing  
  VRF Parsing  
  Context Management                            

General Access

Release Notes

Adding the device to the system

In order to add HP ProCurve switches to the system, operator and manager username must be the same. Then, you can change them using Deploy Password functionality.

Modifying the hostname

The default exec and enable prompt of the HP ProCurve switches include the ">" and "#" as ending characters, respectively. Although the hostname of HP ProCurve switches can contain these two characters by design, they should be omitted, otherwise, the system could potentially get out of sync during any task.

return to top

Retrieve Running Configuration

Release Notes

CLI and SCP configurations variations

A configuration captured via CLI might differ when compared to a configuration captured via SCP. This inconsistency could occur due to the different interpretation/formatting by the device of the banner command between the two configuration retrieval modes.

return to top

Configuration Deployment to Running

Release Notes

Deploy to running configuration task

When you select the 'Deploy to running configuration' option for HP ProCurve switches, the task could return warning messages due to invalid commands in the configuration.

Workaround:

Edit the configuration before deploying it.

Deploy to startup configuration task

The HP ProCurve switches reboot automatically after a startup configuration deployment. If the device's configuration contains invalid commands, the configuration is not deployed to the device when running a Deploy to startup configuration task.

Banner deployment is not supported

Banner deployment requires special handling that cannot be automated. As a result, the driver does not support banner deployment when running the "Deploy to running configuration" task through the CLI.

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

return to top