Dot Hill Systems II 200 FC 사용자 설명서
4-26 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
■
Use the show network-parameters CLI command. Refer to the SANscape CLI
User's Guide for more information. If the RAID controller is not on a network
connected to an active DHCP server, an IP address of 0.0.0.0 is displayed. Refer to
the SANscape CLI User's Guide for more information.
User's Guide for more information. If the RAID controller is not on a network
connected to an active DHCP server, an IP address of 0.0.0.0 is displayed. Refer to
the SANscape CLI User's Guide for more information.
■
Use the Change Network Settings window in SANscape. Refer to the “Updating the
Configuration” chapter in the SANscape User’s Guide for more information.
Configuration” chapter in the SANscape User’s Guide for more information.
■
Enable the controller firmware to send event messages using SNMP. Event
messages sent as SNMP traps to the email address you specify contain the IP
address of the array from which it is sent. Refer to the “Configuration Parameters”
chapter in the SANnet II Family RAID Firmware User's Guide for more information.
messages sent as SNMP traps to the email address you specify contain the IP
address of the array from which it is sent. Refer to the “Configuration Parameters”
chapter in the SANnet II Family RAID Firmware User's Guide for more information.
Once you have determined the RAID controller’s IP address using one of these
methods, you can establish a telnet session to that IP address. However, because of the
dynamic nature of DHCP-assigned IP addresses, the RAID array’s IP address might
change in the event of a controller reset, a network outage, or if the DHCP server is
rebooted. If this happens, telnet sessions to the previous IP address can no longer
communicate with the array, and it is necessary to use one of the methods described
above to determine the new IP address.
methods, you can establish a telnet session to that IP address. However, because of the
dynamic nature of DHCP-assigned IP addresses, the RAID array’s IP address might
change in the event of a controller reset, a network outage, or if the DHCP server is
rebooted. If this happens, telnet sessions to the previous IP address can no longer
communicate with the array, and it is necessary to use one of the methods described
above to determine the new IP address.
If you do not have an active DHCP server on the same network as the RAID array, or
if you prefer to have a fixed IP address, use the procedures in “Setting Up Out-of-
Band Management Over Ethernet” on page 4-28.
if you prefer to have a fixed IP address, use the procedures in “Setting Up Out-of-
Band Management Over Ethernet” on page 4-28.
4.10
Configuring a Host COM Port to Connect to a
RAID Array
RAID Array
The RS-232 COM (serial) port on either controller module can be used to configure
and monitor the RAID array using the controller firmware. It can be connected to a
VT100 terminal, terminal emulation program, terminal server, or the serial port of a
server.
and monitor the RAID array using the controller firmware. It can be connected to a
VT100 terminal, terminal emulation program, terminal server, or the serial port of a
server.
1. Use a null modem serial cable to connect the COM port of the RAID array to the serial
port on a host workstation.
A null modem serial cable is included in your package.
A null modem serial cable is included in your package.
2. Set the serial port parameters on the workstation as follows:
■
38,400 baud
■
8 bit
■
1 stop bit
■
No parity
If your host uses the Solaris operating system, see “Using the tip Command for
Local Access to the Array” on page E-2 for instructions about setting up a tip session
to communicate using the COM port.
To see platform-specific details for other operating systems, see the appendix that
describes the operating system your server uses.
Local Access to the Array” on page E-2 for instructions about setting up a tip session
to communicate using the COM port.
To see platform-specific details for other operating systems, see the appendix that
describes the operating system your server uses.