Skip to main content

HP ProCurve (Telnet)

Connector name

agtprocurve

Connector type

PSLang script

Type (UI field value)

HP ProCurve (telnet)

Connector status / support

Customer-Verified

Clients may contact Bravura Security support for assistance with this connector. Troubleshooting and testing must be completed in the client's test environment as Bravura Security does not maintain internal test environments for the associated target system.

Installation / setup

Bravura Security Fabric performs operations on HP ProCurve using the agtprocurve connector. This connector consists of a PSLang script, agtprocurve.psl and a scripted platform definition file, agtprocurve-telnet.con, that associates the script with the Telnet connector (agttelnet) to access HP ProCurve via Telnet.

The following Bravura Security Fabric operations are supported by this connector (depending on your product license and version):

  • administrator reset password

  • get server information

  • List:

    • accounts

    • attributes

For a full list and explanation of each connector operation, see connector operations.

See also

  • Alternatively, the agtprocurve-ssh.con file associates the script with the SSH connector (agtssh) to access HP ProCurve via SSH. See HP ProCurve (SSH) for details about this method.

  • See TCP Telnet HTTP or HTTPS Access for details about agttelnet .

Targeting the HP ProCurve system

For each HP ProCurve system, add a target system in Bravura Security Fabric (Manage the System > Resources > Target systems):

  • Type is HP ProCurve (telnet)

  • Address uses options described in the table below.

The full list of target system parameters is explained in Target System Options .

Table 1. HP ProCurve (Telnet) address configuration

Option

Description

Options marked with a redstar.png are required.

Script file redstar.png

Must be set to agtprocurve.psl

(key: script)

Server redstar.png

The IP address/domain name of the HP ProCurve system.

(key: server)

Target system’s internal hostname or prompt redstar.png

This is the internally-defined host name that, along with the logged in user’s name, comprises the HP ProCurve prompt. The script generates the expected prompt using this value, then uses the generated prompt to know when commands have completed.

(key: name)

Save target system configuration

Select this to commit changes made to this target to permanent storage on the router, otherwise it will be stored in memory. This is selected by default.

(key: docommit)

Advanced

Port

TCP port number. Typical TCP port numbers are:

  • 23 - Telnet (default)

  • 80 - HTTP

  • 443 - HTTPS

    (key: port)

Connection over SSL

This is a generic Telnet target field that is ignored for HP ProCurve target systems.

Validate the server’s certificate when connecting

This is a generic Telnet target field that is ignored for HP ProCurve target systems.

Terminal type

This is a generic Telnet target field that is ignored for HP ProCurve target systems.

Telnet special write option

This is a generic Telnet target field that is ignored for HP ProCurve target systems.

Directory containing PEM-formatted CA certificate files

This is a generic Telnet target field that is ignored for HP ProCurve target systems.

PEM-formatted CA certificate file

This is a generic Telnet target field that is ignored for HP ProCurve target systems.

Timeout for connection

Amount of time in seconds the connector will wait for a response. Default is 300 seconds.

(key: timeout)



Setting up a target system administrator

Bravura Security Fabric requires 2 administrative credentials on HP ProCurve to perform Bravura Security Fabric operations. This includes credentials to connect to the HP ProCurve router, as well as a system (enable) password for elevated privileges.

There are different credential scenarios available for targeting HP ProCurve:

  1. Default

    • operator

    • manager (Identify as System password )

  2. Renamed account

    It is possible to give the accounts different names. One or both may be renamed. However the accounts are still listed with their default names so it must be manually associated.

    Associate the renamed operator and manager account to ’ operator ’ and ’ manager ’ from managed accounts, respectively.

  3. Direct Manager login

    It is not necessary to use both accounts, if desired the agent can be configured to manage the target using only the manager account . Ensure that System password is unchecked.