Driver Support Document

EXT_HP (formerly H3C) Corporation switches, routers, & U200 and SecPath firewalls, 3Com Corporation switches 4500G, S4800G, S7900 series, Comware version 3.x, 5.x, 7.10, VRP 8.50

• Internal Driver Name: EXT_H3CJS
• Driver Package: EXT_H3CJS.rdp
  
• Driver Tier: 3
• Vendor: H3C
• Family: HP - H3C
• IPv6 Support: Not Supported

Show Tested Devices Grid

Driver Features Support Grid

Driver Discovery

Release Notes

SNMP Discovery

SNMP Discovery depends on locating the OS or Release version in the SysDescr field, and will fail if the string value is improperly altered.

return to top

General Access

Release Notes

Read-only access (bypassing the Super password)

Some Huawei devices allow the handling of snapshot commands through direct login, without having to enter Super mode. By default, the driver attempts to enter Super mode before trying any commands. If the Super account can not be used, read-only snapshot can be supported by setting the access variable "read_only_access" to "true". If set, the driver will skip the use of the Super command.

Usage of SNMP read only strings

Some H3C devices [particularly the U200] seem to not allow basic read operations for "read" community. Since NA only tries read-only strings for read-only operations, it may fail to access the device. If SNMP is seen to fail when properly confirured, put a "write"-access community string in the entry for "SNMP Read-Only String" section in the Edit Device page.

Role-based authentication in Comware7

Comware7 supports a role-based authentication, and may only use external authentication for certain "super" levels. When entering Super mode, "level-15" will be supplied as the default role to be used. To use a different level, set the "default_super_level" variable to another value, e.g. "level-14". If the value "default" is specified in the variable, "super" will be run with no arguments.

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.

Support for "debug" mode on V1910 models

The V1910 model supports a limited CLI, which does not allow the use of normal commands needed to manage the device. There is an undocumented "debug" command that can be used to activate full access mode, but it requires a specific hardwired password to enter the mode. Because it is undocumented and thus unsupported, this password is not given out by HP support. If the password is known, set the device access variable "debug_password" to the password value, and the driver will issue the command and unlock the device. By entering the password, the user takes full responsibility for any unintended side-effects of using the undocumented mode.

return to top

Retrieve Running Configuration

Release Notes

TFTP/SNMP snapshot

TFTP/SNMP snapshot method is not supported by the 3Com devices listed in the driver.

TFTP Interface specification

H3C devices allow for specification of the interface used for TFTP transmissions. Some device configurations may require this specification to use TFTP. In such cases, the TFTPInterface access variable should be set to the value "source interface <interface>" where <interface> denotes the interface from which the NA TFTP server address can be reached.

VPN instance specification

return to top

Configuration Deployment to Running

Release Notes

Deployment could cause loss of access

H3C configuration deployment operations replace entire configuration, rather than using a merge operation. If configurations are edited in such a way that IP or access information is improperly changed, device access could be lost following a reboot.

return to top

General Access

Release Notes (inherited)

Extra support for drivers that use HTTP

This note applies only for drivers that use HTTP requests for driver functions. HTTP proxy operations are supported by setting the device access variable "http_proxy" to "ip:port", replacing with the IP and port values of the proxy server. SNI-requiring devices (e.g CloudGenix & Cisco Meraki) can be supported by using the device access variable "alternate_host" to contain the DNS name of the host. The host name will be used rather than the normal management IP address for all HTTP requests, effectively supporting SNI.

return to top

Driver Discovery

Release Notes (inherited)

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:
HWCM
Command is sy.*
command:sy.*


User Patterns

These patterns are used to determine the username/IP responsible for a change:
/[uU]ser[:=](\S+?)[;, ]/
/.* STEL user (\S+) .* login/
/.* SSH user (\S+) .*/

return to top