Chapter 5
Connecting to the controller CLI port
45
NOTE Using HyperTerminal with the CLI on a Microsoft Windows host:
On a host computer connected to a controller module’s mini-USB CLI port, incorrect command syntax in a
HyperTerminal session can cause the CLI to hang. To avoid this problem, use correct syntax, use a different terminal
emulator, or connect to the CLI using SSH rather than the mini-USB cable.
Be sure to close the HyperTerminal session before shutting down the controller or restarting its Management Controller.
Otherwise, the host’s CPU cycles may rise unacceptably.
If communication with the CLI is disrupted when using an out-of-band cable connection, communication can sometimes
be restored by disconnecting and reattaching the mini-USB cable as described in step 2 on page 44.
NOTE If using a Windows operating system version older than Windows 10/Server 2016, access the USB device driver
download from the HPE MSA support website at
.
Using the CLI port and cable — known issues on Windows
When using the CLI port and cable for setting controller IP addresses and other operations, be aware of the following
known issues on Microsoft Windows platforms.
Problem
On Windows operating systems, the USB CLI port may encounter issues preventing the terminal emulator from
reconnecting to storage after the Management Controller (MC) restarts or the USB cable is unplugged and reconnected.
Workaround
Follow these steps when using the mini-USB cable and USB Type B CLI port to communicate out-of-band between the
host and controller module for setting network port IP addresses.
To restore a hung connection when the MC is restarted (any supported terminal emulator):
1. If the connection hangs, disconnect and quit the terminal emulator program.
a. At the login prompt, enter your secure login username.
b. Enter your secure login password.
c. Wait for the port to disable.
2. Right-click on the previously hung—now disabled—Disk Array USB Port (COMn), and select Enable.
3. Start the terminal emulator and connect to the COM port.
NOTE When using Windows 10/Server 2016 with PuTTY, the XON/XOFF setting must be disabled, or the COM port will
not open.