Table of Contents
Advertisement
Implementing SAN Internetworking Solutions
4
Consolidating and Integrating iSCSI Servers and Storage
McDATA Products in a SAN Environment - Planning Manual
4-58
14. Explicitly assign unique mSAN_IDs - When iSAN routing is
implemented, each Eclipse 1620 SAN router comprises an mSAN
(not the case with an Eclipse 2640 SAN router). Each mSAN must
be assigned a unique mSAN_ID. The ID ranges from 0 to 255, and
is typically the last octet of the management port IP address
(although not a requirement). Do not install a SAN router without
changing the default mSAN_ID. Configure a unique ID for both
SAN routers in an extended-distance link.
15. Back up critical data - Always back up SAN router access
passwords, configurations, and zones. This avoids the possibility
of having to reconfigure a SAN router as if it were a new
installation.
The iSCSI protocol defines rules and processes for transporting
block-level small computer systems interface (SCSI) data over a
TCP/IP network. iSCSI is designed as a protocol for an initiator to
send SCSI commands to a target over IP.
iSCSI initiators (servers) include host bus adapters (HBAs) with iSCSI
capability implemented in the hardware adapter card and software
initiators running over standard network interface cards (NICs).
iSCSI targets (storage) include disk storage systems, tape storage
systems, and iSCSI gateways (such as Eclipse-series SAN routers).
Server HBAs and storage array NICs connect iSCSI resources over an
IP network. Core transport layers are managed with existing network
applications and high-level management activities of the iSCSI
protocol (such as permissions, device information, and configuration)
are layered over these applications.
The following sections describe:
•
iSCSI protocol.
•
iSCSI server consolidation.
•
SCSI storage consolidation.
Advertisement
Table of Contents
