After OS is booted failover is implemented using multipathing support on OS level. You have to configure OS to use redundant pseudo-device and not physical paths. If your question is about ESX, VMs usually are not even aware of multiple paths. They just see VMDK presented as connected to single controller. Here failover is completely handled by hypervisor. Could you provide link to Emulex Multi-Port Failover Boot description?
... View more
Actually, the guide is quite clear. Controller-to-stack connections: Each storage system controller is connected to each stack of disk shelves through a dedicated Ethernet port: - Controller 1/A always connects to the top shelf IOM A square port in a stack. - Controller 2/B always connects to the bottom shelf IOM B circle port in a stack. In essence, you daisy all IOMs of all shelves and then connect two remaining ports to both controllers. If you have single controller, you connect just one port. How exactly you daisy chain does not really matter, but keeping suggested order makes it easier to support.
... View more
Most TRs are available on http://www.netapp.com/library; no account is needed to access them. Some are restricted access and can be downloaded from fieldportal only; you need to be partner to have access to fieldportal.
... View more
When disk failed, aggregate should have been rebuilt on spare. Now new disk will become spare. If auto assignment did not happen (e.g. because stack is shared by two controllers), you need to assign disk to controller explicitly using “disk assign” command.
... View more
8.0P3 is really old now; do you have any reasons to not upgrade to the latest stable 8.0.2P6? But we have these problem also in pure Windows environment, without any NetApp involved, so I suspect this is Microsoft issue.
... View more
Just curious - which default? In CLI you have to list initiators explicitly. FileView last time I tried it presented only initiators connected to local filer. May be OCSM behavior has changed, but I do not dare to use it for configuration
... View more
It is not in any way Cisco specific. Emulex HBA could use it since the very first day I met them (I think at least Linux dropped support for IP now). Brocade switches always supported in-band management as well (and of course could forward IPoFC from HBA). Actually, even NetApp used it for SnapMirror over FC
... View more
Yes, it is possible. You may have issues with home directories though; see if these articles help: https://kb.netapp.com/support/index?page=content&id=1011050 https://kb.netapp.com/support/index?page=content&actp=LIST&id=2012332
... View more
It is not possible to give blanket answer. Less snapshots will likely take up less space, and the longer snapshot is kept the more difference is accumulated (i.e. snapshot “grows”). But again - it is possible that there is large amount of transient data generated at specific (time of) day which is captured by frequent snapshots, but weekly snapshot capture mostly the same static information and so does not take any space at all. YMMV … you have to experiment what is better suited for your specific conditions.
... View more
I noticed that for SAS shelves load balancing is done per-shelf, as opposed to per-disk for DS14 (i.e. all disks in one shelf are shown as having the same primary port). Just wanted to confirm - is it by design? This is with 8.0.2P6 7-Mode.
... View more
Well, you have one (or combination) of - disk writeback is too slow - your filer receives more data than it can physically write to disks So the first step is to analyze disk write performance. In the former case it may be possible to increase it without adding more hardware (e.g. fragmentation may impact disk performance by inducing more disk IO than is necessary). In the latter I am afraid throwing in more hardware and redistributing data between old and new is the only option.
... View more