Print | Rate this content

HPE MSA 2040 SAN Storage - Connecting to the Controller CLI Port

Device description

The MSA 2040 controllers feature a command-line interface port used to cable directly to the controller and initially setIP addresses, or perform other configuration tasks. This port employs a mini-USB Type B form factor, requiring a cablethat is supplied with the controller, and additional support, so that a server or other computer running a Linux orWindows operating system can recognize the controller enclosure as a connected device. Without this support, thecomputer might not recognize that a new device is connected, or might not be able to communicate with it.

For Linuxcomputers, no new driver files are needed, but a Linux configuration file must be created or modified.

For Windows computers, the Windows USB device driver must be downloaded from a CD or HPE website, and installedon the computer that will be cabled directly to the controller command-line interface port.

NOTE: Directly cabling to the CLI port is an out-of-band connection because it communicates outside the data pathsused to transfer information from a computer or network to the controller enclosure.

top

Preparing a Linux computer before cabling to the CLI port

Although Linux operating systems do not require installation of a device driver, certain parameters must beprovided during driver loading to enable recognition of the MSA 2040 controller enclosures. To load theLinux device driver with the correct parameters, the following command is required:

modprobe usbserial vendor=0x210c product=0xa4a7 use_acm=1

Optionally, the information can be incorporated into the /etc/modules.conf file
.

top

Downloading a device driver for Windows computers

A Windows USB device driver download is provided for communicating directly with the controllercommand-line interface port using a USB cable to connect the controller enclosure and the computer.

NOTE: Access the download from the HPE MSA support page. Click here to view the support page for MSA 2040 SAN Storage .

The USB device driver is also available from the Software Support and Documentation CD that shippedwith the product.

top

Obtaining IP values

One method of obtaining IP values for the system is to use a network management utility to discover HPEMSA Storage devices on the local LAN through SNMP. Alternative methods for obtaining IP values forthe system are described in the following subsections.

Setting network port IP addresses using DHCP

In DHCP mode, network port IP address, subnet mask, and gateway values are obtained from a DHCPserver if one is available. If a DHCP server is unavailable, current addressing is unchanged.

  1. Look in the DHCP server’s pool of leased addresses for two IP addresses assigned to HPE MSAStorage.

  2. Use a ping broadcast to try to identify the device through the ARP table of the host.If a DHCP server is not available, then there is a need to ask the system administrator to allocate two IPaddresses, and set them using the command-line interface during initial configuration.

Setting network port IP addresses using the CLI port and cable

Set network port IP addresses manually using the command-line interface port and cable. If not done so already, then need to enable the system for using the command-line interface port.

Network ports on controller module A and controller module B are configured with the followingfactory-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 the network, set an IP address for eachnetwork port using the command-line interface embedded in each controller module. The command-lineinterface enables to access the system using the USB (Universal Serial Bus) communication interfaceand terminal emulation software. The USB cable and CLI port support USB version 2.0.

Use the CLI commands described in the steps below to set the IP address for the network port on eachcontroller module. Once new IP addresses are set, change them as needed using the SMU. Besure to change the IP address via the SMU before changing the network configuration.

NOTE: Changing IP settings can cause management hosts to lose access to the storage system.
  1. From the network administrator, obtain an IP address, subnet mask, and gateway address forcontroller A, and another for controller B.Record these IP addresses so that they can be specified whenever the controllers are managed using theSMU or the CLI.

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

    Figure 1: Connecting a USB cable to the CLI port

  3. Enable the CLI port for subsequent communication:
    • Linux users should enter the command syntax provided in Preparing a Linux computer beforecabling to the CLI port (see above).

    • Windows users should locate the downloaded device driver described in Downloading adevice driver for Windows computers (see above), and follow the instructions provided for properinstallation.

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

    Table 1: Terminal emulator display settings
    Parameter
    Value
    Terminal emulation mode
    VT-100 or ANSI (for color support)
    Font
    Terminal
    Translations
    None
    Columns
    80
    Table 2: Terminal emulator connection settings
    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: The 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:
    1. At the login prompt, enter the default user manage.

    2. Enter the default password !manage.

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

    NOTE: The following CLI commands enable to set the management mode to v3 or v2:
    • Use set protocols
      to change the default management mode.

    • Use set cli-parameters
      to change the current management mode for the CLI session.

    The system defaults to v3 for new users and v2 for existing users. Click here to view the CLI Reference Guide for more information .

  7. At the prompt, type the following command to set the values obtained in step 1 for each networkport, 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 are setting

    For example:

    # set network-parameters ip 192.168.0.10 netmask 255.255.255.0 gateway192.168.0.1 controller a

    # set network-parameters ip 192.168.0.11 netmask 255.255.255.0 gateway192.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 foreach controller.

  9. Use the ping
    command to verify network connectivity.

    For example:

    # ping 192.168.0.1 (gateway)

    Info: Pinging 192.168.0.1 with 4 packets.

    Success: Command completed successfully. - The remote computer responded with 4packets.

  10. In the host computer's command window, type the following command to verify connectivity, first forcontroller A and then for controller B:

    ping controller-IP-address

    If the system cannot be accessed for at least three minutes after changing the IP address, the networkmight require user to restart the Management Controller(s) using the CLI. When aManagement Controller is restarted, 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 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 aHyperTerminal session can cause the CLI to hang. To avoid this problem, use correct syntax, use a differentterminal emulator, or connect to the CLI using telnet rather than the mini-USB cable.

Be sure to close the HyperTerminal session before shutting down the controller or restarting its ManagementController. Otherwise, the host’s CPU cycles may rise unacceptably.

If communication with the CLI is disrupted when using an out-of-band cable connection, communicationcan sometimes be restored by disconnecting and reattaching the mini-USB cable as described in step 2 (see above).

The USB device driver is also available from the Software Support and Documentation CD that shippedwith the product.

NOTE: Access the download from the HPE MSA support page. Click here to view the support page for MSA 2040 SAN Storage .

top

Using the CLI port and cable - Known issues on Windows

When using the CLI port and cable for setting controller IP addresses, be aware of the following knownissues on Microsoft Windows platforms.

Problem

On Windows operating systems, the USB CLI port may encounter issues preventing the terminal emulatorfrom reconnecting to storage after the Management Controller (MC) restarts or the USB cable is unpluggedand reconnected.

Workaround

Follow these steps when using the mini-USB cable and USB Type B CLI port to communicate out-of-bandbetween the host and controller module for setting network port IP addresses.

To create a new connection or open an existing connection (HyperTerminal):

  1. From the Windows Control Panel, select Device Manager.

  2. Connect using the USB COM port and Detect Carrier Loss option.

    1. Select Connect To > Connect using: > pick a COM port from the list.

    2. Select the Detect Carrier Loss check box.

    The Device Manager page should show Ports (COM & LPT) with an entry entitled Disk Array USBPort (COMn) where, n is the system’s COM port number.

  3. Set network port IP addresses using the CLI (For procedure see above)

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.

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

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

    3. 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 (For procedure see above).

top

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!