78 Connecting hosts
8. Enter 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 for
each controller.
9. Use the ping command to verify connectivity to the gateway address.
For example:
# ping 192.168.0.1
Info: Pinging 192.168.0.1 with 4 packets.
Success: Command completed successfully. - The remote computer responded
with 4 packets.(2011-12-19 10:20:37)
10. In the host computer's command window, type the following command to verify connectivity, first for
controller A and then for controller B:
ping controller-IP-address
If you cannot access your system for at least three minutes after changing the IP address, you might
need to restart the Management Controller(s) using the serial CLI.
When you restart a Management Controller, communication with it is temporarily lost until it
successfully restarts.
Enter the following command to restart the Management Controller in both controllers:
restart mc both
IMPORTANT: When configuring an iSCSI system or a system using a combination of FC and iSCSI
SFPs, do not restart the Management Controller or exit the terminal emulator session until
configuring the CNC ports as described in Change the CNC port mode on page 78.
11. When you are done using the CLI, exit the emulator.
12. Retain the IP addresses (recorded in step 1) for accessing and managing the controllers using the SMC,
RAIDar, 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 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 step 2
and Figure 79 on page 76.
Change the CNC port mode
This subsection applies to 4824/4834/4844/4854 models only. While the USB cable is still connected
and the terminal emulator session remains active, perform the following steps to change the CNC port
mode from the default setting (FC), to either iSCSI or FC-and-iSCSI used in combination.
When using FC SFPs and iSCSI SFPs in combination, host ports 0 and 1 are set to FC (either both 16
Gbits/s or both 8 Gbit/s), and host ports 2 and 3 must be set to iSCSI (either both 10GbE or both 1
Gbit/s).
Set CNC port mode to iSCSI
To set the CNC port mode for use with iSCSI SFPs, run the following command at the command prompt:
set host-port-mode iSCSI
To Next Page
Loading...