Print | Rate this content

HPE MSA 1050 Storage - How to Setup Network Port IP Addresses Using the CLI Port and Cable

Setting network port IP addresses using the CLI port and cable

User can set network port IP addresses manually using the Command-Line interface port and cable. If user have not done so already, user need to enable users system for using the Command-Line interface port.

NOTE: For Linux systems, see “Preparing a Linux computer for cabling to the CLI port. For windows systems see “Preparing a windows computer for cabling to the CLI port”.

Network ports on controller module A and controller module B are configured with the following Factory-Default IP settings:

  • Management Port IP Address: 10.0.0.2 (Controller A), 10.0.0.3 (Controller B)

  • IP Subnet Mask: 255.255.255.0

  • Gateway IP Address: 10.0.0.1

If the default IP addresses are not compatible with users network, user must set an IP address for each network port using the command-line interface.

Use the CLI commands described in the steps below to set the IP address for the network port on each controller module. Once new IP addresses are set, user can change them as needed using the SMU.

NOTE: Changing IP settings can cause management hosts to lose access to the storage system.
  1. From users network administrator, obtain an IP address, subnet mask, and gateway address for controller A, and another for controller B.

    Record these IP addresses so that user can specify them whenever user manage the controllers using the SMU or the CLI.

  2. Use the provided USB cable to connect controller A to a USB port on a host computer. The USB mini 5 male connector plugs into the CLI port.

  3. Enable the CLI port for subsequent communication.

    If the USB device is supported natively by the operating system.

    • Linux users should enter the command syntax provided in "Preparing a Linux computer for cabling to the CLI port".

    • Windows users should locate the downloaded device driver described in "Preparing a Windows computer for cabling to the CLI port".

  4. Start and configure a terminal emulator, such as HyperTerminal or VT-100, using the display settings in Table 5 and the connection settings in Table 6 (Also, see the note following this procedure).

    Parameter
    Value
    Terminal emulation mode
    VT-100 or ANSI (For color support)
    Font
    Terminal
    Translations
    None
    Columns
    80
    Parameter
    Value
    Connector
    COM3 (For example)1,2
    Baud rate
    115,200
    Data bits
    8
    Parity
    None
    Stop bits
    1
    Flow control
    None
    NOTE:
    1. users server or laptop configuration determines which COM port is used for Disk Array USB port.
    2. Verify the appropriate COM port for use with the CLI.
  5. In the terminal emulator, connect to controller A.

  6. Press Enter to display the CLI prompt (#).

    The CLI displays the system version, MC version, and login prompt:

    • At the login prompt, enter the default user manage.

    • Enter the default password !manage.

    If the default user or password - or both - have been changed for security reasons, enter the secure login credentials instead of the defaults shown above.

  7. At the prompt, type the following command to set the values user obtained in step 1 for each network port, first for controller A and then for controller B:

    set network-parameters ip address netmask netmask gateway gateway controller a|b where:

    • address is the IP address of the controller

    • netmask is the subnet mask

    • gateway is the IP address of the subnet router

    • a|b specifies the controller whose network parameters user are setting

    For example:

    • # set network-parameters ip 192.168.0.10 netmask 255.255.255.0 gateway 192.168.0.1 controller a

    • # set network-parameters ip 192.168.0.11 netmask 255.255.255.0 gateway 192.168.0.1 controller b

  8. Type the following command to verify the new IP addresses:

    "show network-parameters"

    Network parameters, including the IP address, subnet mask, and gateway address are displayed for each controller.

  9. Use the ping command to verify network connectivity.

    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 user cannot access users system for at least three minutes after changing the IP address, users network might require user to restart the Management Controller(s) using the CLI. When user 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 user 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

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 Click here to access the "HPESC website" for more information .

top

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.

    • Using Device Manager, locate the COMn port assigned to the Disk Array Port.

    • Right-click on the hung Disk Array USB Port (COMn), and select Disable.

    • 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.

  4. Set network port IP addresses using the CLI.

NOTE: When using Windows 10/Server 2016 with PuTTY, the XON/XOFF setting must be disabled, or the COM port will not open.

top

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!
Document title: HPE MSA 1050 Storage - How to Setup Network Port IP Addresses Using the CLI Port and Cable
Document ID: emr_na-a00082134en_us-1
How helpful was this document?
How can we improve this document?
Note: Only English language comments can be accepted at this time.
Please wait while we process your request.