
Setting network port IP addresses using the CLI port and cable
You can set network port IP addresses manually using the command-line interface port and cable. If you have not done
so already, you need to enable your system for using the command-line interface port (see also
cable — known issues on Windows" on page
).
For Linux systems, see
"Preparing a Linux system for cabling to the CLI port" on page
. For Windows systems, see
"Preparing a Windows system for cabling to the CLI port" on the previous page
Network ports on controller module A and controller module B are configured with the following factory-default IPv4 IP
settings:
l
IP Address: 10.0.0.2 (Controller A), 10.0.0.3 (Controller B)
l
IP Subnet Mask: 255.255.255.0
l
Gateway IP Address: 10.0.0.1
Network ports on controller module A and controller module B are configured with the following factory-default IPv6 IP
settings:
Controller A
l
Autoconfig: Enabled
l
Gateway: ::
l
Link-Local Address: fe80::2c0:ffff:fe44:952f
l
Autoconfig IP: 6::2c0:ffff:fe44:952f
Controller B
l
Autoconfig: Enabled (controller B)
l
Gateway: ::
l
Link-Local Address: fe80::2c0:ffff:fe44:7010
l
Autoconfig IP: 6::2c0:ffff:fe44:7017
If the default IP addresses are not compatible with your network, you must set a valid 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. After new IP addresses are set, you 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 your 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 you can specify them whenever you 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-B male
connector plugs into the CLI port as shown in
(generic controller module is shown).
42
Chapter 5
Connecting to the controller CLI port