By default, only SSH interactions work on these devices. If you want to use telnet you have to configure the device through the console or through an SSH session and turn it on.
Cut through or direct access sessions are only supported for SSHv2. You must create an SSHv2 management interface for the device and use it when attempting direct access. If you use SSHv1 the session does not connect (the ArubaOS does not support SSHv1), and if you select telnet, the driver cannot log into the device automatically, and must login manually.
SNMP v2c only supports read operations, not write. SNMP v3 supports both read and write, but not SNMP v3 informs. To manage Aruba devices you must use SNMP v2 or v3. Up to Aruba OS220.127.116.11, SNMPv2c (read-only) and v3 (read-write) are recommended. SNMP v1 does not work correctly.
Although SNMP handles the bulk of the communication with this device, and you must supply the correct SNMP authentication information, some information comes through telnet interaction, so you must supply telnet/SSH authentication too for all device information