The following existing device issues have been discovered within other releases. In most cases, a resolution is included to address the issue.
-
When sending a config line by line using Telnet or SSH, sending an ip-mgmt interface address command causes the terminal session to drop. Due to this, the driver will intentionally filter out any configuration line that starts with ip-mgmt interface address when sending in line by line mode.
-
When sending a config line by line using Telnet or SSH, it is not clear whether commands that change passwords are processed correctly because password commands in the command-line interface are normally interactive. Due to this, any job that sends a password command line by line receives a warning message. The command is sent but the job result will note that the command may not be processed correctly.
-
The local AAA system only supports a total of 10 user accounts. When rolling users/passwords, if the new user does not already exist, the driver first attempts to reuse the old user account if it exists. If the old user account does not exist, the driver looks for one available user account out of the possible 10. If there are no available user accounts, no changes are made and the job will fail.
-
The HP GbE2c Bladeswitch has console logging enabled by default and sends console messages immediately upon login. This can cause automated logins to fail in certain circumstances. It is advisable to permanently turn off console logging on any GbE2c device that is to be managed. In most cases the driver still manages to login, but the messages slow down the login procedure dramatically. For best performance, turn off console logging permanently using the following:
-
configure terminal
-
no logging console
-
end
-
save running-config startup-config
-