84
Installation
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 telnet 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 CLI cable as described in
and
.
Configure controller network ports
IMPORTANT:
If you used the default 10.0.0.2/10.0.0.3 addresses to access the guided setup, it is important to
consider changing those IPv4 addresses to avoid an IP conflict should you have more than one ME4 Series array on
your network.
You can manually set static IP addressing parameters for network ports or you can specify that IP values be set
automatically using DHCP for IPv4 or Auto for IPv6, which uses DHCPv6 and/or SLAAC. When setting IP
values, you can choose either IPv4 or IPv6 formatting for each controller. Additionally, you can set the addressing
mode and IP version differently for each controller and use them concurrently. For example, you could set IPv4 on
controller A to Manual to enable static IP addressing, and IPv6 on controller B to Auto to enable automatic IP
addressing.
When using DHCP mode, the system obtains values for the network port IP address, subnet mask, and gateway
from a DHCP server if one is available. If a DHCP server is unavailable, current addressing is unchanged. You
must have some means of determining what addresses have been assigned, such as the list of bindings on the
DHCP server. When using Auto mode, addresses are retrieved from both DHCP and Stateless address
auto-configuration (SLAAC). DNS settings are also automatically retrieved from the network.
Each controller has the following factory-default IP settings:
•
IP address source: DHCP
•
Controller A IP address: 10.0.0.2
•
Controller B IP address: 10.0.0.3
•
IP subnet mask: 255.255.255.0
•
Gateway IP address: 10.0.0.1
When DHCP is enabled in the storage system, the following initial values are set and remain set until the system is
able to contact a DHCP server for new addresses:
•
Controller IP addresses: 169.254.x.x (where the value of x.x is the lowest 16 bits of the controller serial
number)
•
IP subnet mask: 255.255.0.0
•
Gateway IP address: 10.0.0.0
169.254.x.x addresses (including gateway 169.254.0.1) are on a private subnet that is reserved for unconfigured
systems and the addresses are not rout-able. This prevents the DHCP server from reassigning the addresses and
possibly causing a conflict where two controllers have the same IP address. As soon as possible, change these IP
values to proper values for your network.
