Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

Dell PowerVault ME5 Series Storage System Deployment Guide

Set a network port IP address using the micro USB port

You can manually set the static IP addresses for each controller module. Alternatively, you can specify that IP addresses should be set automatically for both controllers through communication with a Dynamic Host Configuration Protocol (DHCP) server. In DHCP mode, the network port IP address, subnet mask, and gateway are obtained from a DCHP server. If a DHCP server is not available, the current network addresses are not changed. To determine the addresses that are assigned to the controller modules, use the list of bindings on the DHCP server.

About this task

If you did not use DHCP to set network port IP address, you can set them manually using the CLI port. You can use a generic micro-USB cable and the USB CLI port. If you plan on using a micro-USB cable, you must enable the USB CLI port for communication.

Network ports on controller module A and controller module B are configured with the following default values:

  • Network 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 your network, you must set an IP address for each network port using the CLI.

NOTE To connect to the micro USB port on a controller module, see Micro-USB device connection.
NOTE If you are using a host computer running Linux, prepare the USB port as described in Linux drivers.

Use the CLI commands described in the following steps to set the IP address for the network port on each controller module:

NOTE When new IP addresses are set, you can change them as needed using the PowerVault Manager. Be sure to change the IP address before changing the network configuration.

Steps

  1. From your network administrator, obtain an IP address, subnet mask, and gateway address for controller A and another for controller B.
  2. Connect a micro-USB cable from a host computer to the USB CLI port on controller A.
  3. Start a terminal emulator and configure it to use the display and connection settings shown in the following tables.
    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

    1 Your host computer configuration determines which COM port is used for the Disk Array USB Port.

    2 Verify the appropriate COM port for use with the CLI.

  4. Press Enter to display login prompt if necessary.
    The CLI displays the system version, Management Controller version, and login prompt.
  5. If you are connecting to a storage system that has not been deployed:
    1. Type setup at the login prompt and press Enter.
    2. Do not type anything at the Password prompt and press Enter.
    3. Type Y at the prompt to continue.
    If you are connecting to a storage system that has been deployed:
    1. Type the username of a user with the manage role at the login prompt and press Enter.
    2. Type the password for the user at the Password prompt and press Enter.
  6. Set the network port using either DHCP or set a static address using IPv4.
    1. To use DHCP to set network port IP addresses, type the following command at the prompt:
      set network-parameters dhcp
    2. To use custom static IP IPv4 addresses, type the following CLI command to set the values you obtained in step 1:
      NOTE Run the command for controller module A first, and then run the command for controller module B.

      set network-parameters ip <address> netmask <netmask> gateway <gateway> controller <a|b>

      where:

      • address is the IP address of the controller module

      • netmask is the subnet mask

      • gateway is the IP address of the subnet router

      • a|b specifies the controller whose network parameters you 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
    NOTE See the CLI Reference Guide for information about IPv6 and the commands used to add IPv6 addresses and set IPv6 network parameters. The ipv6 term is included within each relevant command name
  7. Type the following CLI command to verify the new IP addresses:
    For IPv4: show network-parameters

    For IPv6: show ipv6-network-parameters

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

  8. Use the CLI ping command to verify connectivity to the gateway address.
    For example:
    ping 192.168.0.1
  9. Open a command window on the host computer and type the following command to verify connectivity to controller A and controller B:
    ping controller-IP-address
    If you cannot access your storage system for at least three minutes after changing the IP address, restart the controllers using the CLI.
    NOTE When you restart a Management Controller, communication with it is temporarily lost until it successfully restarts.

    Type the following CLI command to restart the Management Controller in both controllers:

    restart mc both
  10. Record the IP address for the controller modules to use when connecting to the storage system using PowerVault Manager.
  11. When you are done using the CLI, close the terminal emulator.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\