General Information on setting up your DS300 for network connection
The following sections provide general information on setting up your DS300 for connection to the network using the Command Line Interface (CLI).
Management port (ETH0) IP setup
- CLI example to set up a new IP address for the management port
Setting up iSCSI port IP addresses
The factory default settings for the DS300 are as follows.
Domain Name: ibm.com
Timezone[GMT]: GMT-5
New Administrator password: passw0rd (the 0 in passw0rd is the number 0)
Default Gateway: 0.0.0.0
DNS servers: NO
Use DHCP: NO
Management i/f IP address: 192.168.70.12X (where X=3,4 respectively for controller A and B)
Management i/f IP netmask: 255.255.0.0
Management i/f broadcast address: 192.168.255.255
Management port (ETH0) IP setup
The factory default IP address for the management port for Controller A is 192.168.70.123 (ETH0[A]). The management port for Controller B defaults to 192.168.70.124 (ETH0[B]). If you want to change these addresses, establish a Telnet session to the respective management port. Once connected, the CLI prompt will appear. For additional information on the CLI see Using the CLI.
If a session cannot be established via Telnet, the CLI can be run from a terminal session by connecting to the left most serial port jack. Use serial cable FRU PN 13N1792 (not supplied). The terminal settings are as follows:
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: Off
Note: You need to be in administrator mode to change the IP addresses. Default PW is passw0rd (zero – not an O)
CLI example to set up a new IP address for the management port
Make sure you are in administrator mode. To check the current settings of controller A management port (ETH0[A]) do the following:
DS300[A]> ad (log in as administrator)
DS300[A]# interface manage eth0[A] info
----[ Interface 'eth0[A]' ]-------------------------------------------------------
Services: management
Alternative name: eth0[A]
Status: Enabled
MAC address: 00:00:D1:DD:B6:8C
DHCP DISABLED
IP address: 192.168.70.123
Netmask: 255.255.0.0
Broadcast: 10.1.0.255
MTU: 1500
Speed: AUTO
Note: Make sure the Status is “Enabled” and DHCP is disabled to set static addresses.
To set up a new address:
DS300[A]# interface manage eth0[A] ip 192.168.100.54
Please wait.
Interface values are now:
IP address: 192.168.100.54
Broadcast address: 192.168.255.255
Netmask: 255.255.255.0
The IP address for the management station has been changed to 192.168.100.54. To make this address permanent, save the configuration.
Note: Any changes in IP addresses are valid only for the current session. If a DS300 is power cycled or rebooted, the IP address will revert back to the initial values. In order to save the new IP addresses do the following from a CLI prompt:
DS300[A]> administrator (if not already in ad mode)
DS300[A]# save
After the next enclosure reboot (or power cycle) the new IP addresses will be permanent.
Important: Do not assign the iSCSI ports to the same subnet as the management interface (except for RL model). In addition, each iSCSI port needs to be on a different subnet.
Setting up iSCSI port IP addresses
To set iSCSI port IP addresses, perform the following general steps:
1. Connect the management port to a system.
Note: Ensure that the system NIC is set up with the same subnet as the management port and that the NIC link speed and that of the management port are the same.
2. Start
a Telnet session to connect to the controller management port and to access the
Command Line Interface (CLI). Refer to the following figure for port
identification.
3. From the CLI prompt, set the IP addresses as shown in the following example.
Note: The IP addresses given are samples.
DS300[A]# administrator
DS300[A]# interface info
----[ Interface 'eth2' ]-------------------------------------------------------
Services: iscsi
Alternative name: eth2
Status: Enabled
MAC address: 00:00:D1:DD:B2:66
DHCP DISABLED
IP address: xxx.xxx.xxx.xxx
Netmask: 255.255.255.0
Broadcast: 10.1.0.255
MTU: 1500
Notes:
1. Make sure that the Status is Enabled and that DHCP is disabled to set static addresses.
2. Failover requires that the iSCSI port IP address be static. Do not enable DHCP if you have a failover configuration
3. Do not assign the iSCSI ports to the same network segment as the management interface (except for RL model). In addition, each iSCSI port on the respective controller needs to be on a different network segment (ETH2 and ETH3 cannot be on the same segment for that controller)
4. The Ethernet port ETH2 for controller A and controller B should be in one segment.
5. The Ethernet port ETH3 for controller A and controller B should be in different network segment.
DS300[A]# interface manage eth2 ip 191.1.9.2
Please wait.
Interface values are now:
IP address: 191.1.9.2
Broadcast address: 10.1.0.255
Netmask: 255.255.255.0
DS300[A]# interface manage eth3 ip 181.1.8.4
Please wait.
Interface values are now:
IP address: 181.1.8.4
Broadcast address: 10.1.0.255
Netmask: 255.255.255.0
DS300[A]# interface list
eth0[A] 192.168.100.54 management
eth2 191.1.9.2 iscsi
eth3 181.1.8.4 iscsi
Note: When running the following test, do not connect any cables to the iSCSI ports.
Use the commands shown in the following example to verify that the IP addresses for the management ports are set correctly.
DS300[A]# diag ping 191.1.9.2 count 4 interface eth0[A] [pinging from eth0[A] to eth2]
Pinging 191.1.9.2 using interface eth0[A] (192.168.100.54) SUCCEEDED
Pinging 191.1.9.2 using interface eth0[A] (192.168.100.54) SUCCEEDED
Pinging 191.1.9.2 using interface eth0[A] (192.168.100.54) SUCCEEDED
Pinging 191.1.9.2 using interface eth0[A] (192.168.100.54) SUCCEEDED
DS300[A]# diag ping 181.1.8.4 count 4 interface eth0[A] [pinging from eth0[A] to eth3]
Pinging 181.1.8.4 using interface eth0[A] (192.168.100.54) SUCCEEDED
Pinging 181.1.8.4 using interface eth0[A] (192.168.100.54) SUCCEEDED
Pinging 181.1.8.4 using interface eth0[A] (192.168.100.54) SUCCEEDED
Pinging 181.1.8.4 using interface eth0[A] (192.168.100.54) SUCCEEDED
DS300[A]# diag ping 181.1.8.4 count 4 interface eth2 [pinging from eth2 to eth3]
Pinging 181.1.8.4 using interface eth2 (191.1.9.2) SUCCEEDED
Pinging 181.1.8.4 using interface eth2 (191.1.9.2) SUCCEEDED
Pinging 181.1.8.4 using interface eth2 (191.1.9.2) SUCCEEDED
Pinging 181.1.8.4 using interface eth2 (191.1.9.2) SUCCEEDED
DS300[A]# diag ping 191.1.9.2 count 4 interface eth3 [pinging from eth3 to eth2]
Pinging 191.1.9.2 using interface eth3 (181.1.8.4) SUCCEEDED
Pinging 191.1.9.2 using interface eth3 (181.1.8.4) SUCCEEDED
Pinging 191.1.9.2 using interface eth3 (181.1.8.4) SUCCEEDED
Pinging 191.1.9.2 using interface eth3 (181.1.8.4) SUCCEEDED
Perform the crossport test to verify the ETH ports functionality. Connect an Ethernet cable (straight through) from ETH2 to ETH3. If you are accessing the CLI via the serial port you can also connect ETH0[X] to the other ports.
Syntax
diag connection <from> <to>
'from' and 'to' are the interfaces (i.e. eth0[A], eth2, eth3) and must be specified. The same interface may be used as 'from' and 'to'.
The test either reports success or failure.
To check that the IP addresses have been successfully set up and that there is an active connection do the following:
If the DS300 has a second controller, repeat the procedure shown above.
Note: In a dual controller enclosure, it is recommended that a single Telnet session be active to only one controller. The management of both controllers can take place through that single connection. You can log on to a controller from the current controller session by doing a “Controller Set”. See Using the CLI – Controller Commands.