Dot Hill Systems SANnet II 200 Service Manual Page 86

  • Download
  • Add to my manuals
  • Print
  • Page
    / 210
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 85
5-4 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual March 2005
Caution – If you keep the default loop mode and connect to a fabric switch, the array
automatically shifts to public loop mode. As a result, communication between the
array and the switched fabric runs in half duplex (send or receive) instead of providing
the full duplex (send and receive) performance of point-to-point mode.
Check the host IDs on all the channels to ensure that there is only one ID per
channel (on the primary controller or on the secondary controller) for point-to-point
mode. When viewing the host IDs, there should be one primary controller ID (PID)
or one secondary controller ID (SID); the alternate port ID should display N/A.
Proper point-to-point mode allows only one ID per channel.
On the SANnet II 200 SATA or SATA SE array, if one of the dual-ports of channel
0 is connected to a switch (port FC 0), the other FC 0 port on that controller and the
two FC0 ports on a redundant controller cannot be used. Similarly, if one of the
channel 1 ports is connected with a switch (port FC 1), the other FC 1 port on that
controller, and the two FC 1 port on a redundant controller cannot be used.
If you change the mode to Point-to-point only and attempt to add a second ID, the
controller does not allow you to add an ID to the same controller and channel. For
example, if you have ID 40 on CH 0 PID, and N/A on CH 0 SID, the controller does
not allow you to add another PID to CH 0.
The controller displays a warning if the user is in point-to-point mode and tries to
add an ID to the same channel but on the other controller. The warning is displayed
because you have the ability to disable the internal connection between the channels
on the primary and secondary controller using the SANscape CLI
set inter-
controller link
command and, by doing this, you can have one ID on the
primary and another ID on the secondary as a legal operation.
However, if you ignore this warning and add an ID to the other controller, the RAID
controller does not allow a login as a Fabric Loop (FL) port because this would be
illegal in a point-to-point configuration.
The firmware application allows you to add up to eight IDs per channel (four IDs on
each controller), which forces the fabric switch port type to become fabric loop. To
ensure F-port behavior (full fabric/full duplex) when attaching to a switch, only one
ID must be present on each channel and the array port must be set to point-to-point
mode.
Do not connect more than one port per channel on an array to a fabric switch.
Caution – In point-to-point mode or in public loop mode, only one switch port is
allowed per channel. Connecting more than one port per channel to a switch can
violate the point-to-point topology of the channel, force two switch ports to “fight”
over an AL_PA (arbitrated loop physical address) value of 0 (which is reserved for
loop-to-fabric attachment), or both.
With four host channels and four host IDs, you should load balance the host ID
setup so that half the IDs are on the primary controller and half the IDs are on the
secondary controller. When setting up LUNs, map each LUN to either two PIDs or
two SIDs. The hosts are in turn dual-pathed to the same two switched fabrics. When
Page view 85
1 2 ... 81 82 83 84 85 86 87 88 89 90 91 ... 209 210

Comments to this Manuals

No comments