HP MSA 2050 User Manual page 41

For example, to ping the gateway in the examples above:
# ping 192.168.0.1
Info: Pinging 192.168.0.1 with 4 packets.
Success: Command completed successfully. - The remote computer responded with 4 packets.
10. In the host computer's command window, type the following command to verify connectivity, first for controller A and
then for controller B:
ping controller-IP-address
If you cannot access your system for at least three minutes after changing the IP address, your network might require
you to restart the Management Controller(s) using the CLI. When you restart a Management Controller,
communication with it is temporarily lost until it successfully restarts.
Type the following command to restart the management controller on both controllers:
restart mc both
11. When you are done using the CLI, exit the emulator.
12. Retain the new IP addresses to access and manage the controllers, using either the SMU or the CLI.
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
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 http://www.hpe.com/support/downloads.
step 2 on page 39.
Obtaining IP values 41