Common Pitfalls
Network
- 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)
- The Ethernet port ETH2 for controller A and controller B
should be in one segment.
- The Ethernet port ETH3 for controller A and controller B
should be in different network segment.
- Be careful if you are using DHCP on more than one
interface. Both interfaces can end up on the same subnet, depending on the
configuration of the DHCP server
Failover
- Failover
requires that the iSCSI port IP address be static. Make sure DHCP is not
enabled if the customer has a failover configuration
- At this time only ipfailover
(remote mode) is supported. Make sure customer is running the controllers
in “remote” mode.
- Ensure the OS timeout value
for failover is set to 180 (B4 hex). See Storage Configuration.
- If an iSCSI HBA (QLA4010) is
present the ARP Redirect setting and the KeepAliveTO value need to be
changed (See Storage Configuration.)
- ARP redirect enabled
- KATO value set to 180
- There is no DSM (Device
Specific Module) at this time for the DS300. Only ipfailover is supported.
Logical
Units
- Both DS300 and DS400 are based
on the Asynchronous Logical Unit Access (ALUA). However, the
SetTargetGroup command is not currently supported on the DS300
- Logical Units are bound to an
IP address and can only be accessed using that IP address
- If logical drive ownership
change is required (that is from current owner to preferred owner) the CLI
“array move” command needs to be invoked. This operation cannot be done
from ServeRAID manager for the DS300.
- When a logical drive is moved,
all of the initiators bound to that drive need to be removed and re-added
using the IP address of the alternate controller
- Host not detecting LUs may be
caused by the drive not being assigned to the host in the ACL (Access
control List) in ServeRAID manager.
Arrays
- Do not delete alien or foreign
arrays
- Alien arrays can occur if
controller configuration does not match that of the disks’.
- Foreign arrays can occur if
there is no configuration present on a controller but present on the
disks.
- Foreign and alien arrays can
be recovered using the Controller Clear procedure.
Controllers
- Do not swap controllers from
one slot to the other.
- Do not swap controllers from
another enclosure. Doing so may cause Alien arrays.
Back to the top