OnCommand System Manager became far more responsive in 2.0.1. So if you experience slowness, it is probably due to lack of name resolution. ... View more

PCI cards are fixed mode - either target or initiator. There is no way to configure it. ... View more

Firmware and Data ONTAP are different things. Data ONTAP upgrades include firmware which today gets installed automatically (on reboot); for older Data ONTAP versions you may need to manually flash firmware. Firmware is also available separately in case you need it before it is included in next full Data ONTAP update. ... View more

Well ... as long as NetApp cannot speak with DC, it also cannot resolve names. You have to solve this issue first. ... View more

OK, so it is not the problem I suspected (lack of NT-to-Unix mapping for non-admin users). ... View more

It does not really look good. And "cifs testdc"? ... View more

What is the value of options wafl.nt_admin_priv_map_to_root and wafl.default_unix_user and content of /etc/passwd? ... View more

So far my only idea is - primary had so much data at some point and secondary did not yet catch up. Ho w often is snapmirror run? ... View more

For a start - is it VSM or QSM? ... View more

Is the system also snapmirror destination? It appears to be extremely busy writing to disks. Tape is unlikely to be bottleneck here. You could try dump to null just to test how fast it can read from disks. There was KB article how to do it, search kb.netapp.com. ... View more

lun show -v and look for “Occupied size”. If it is no there, you have too old Data ONTAP version. ... View more

You probably mean “volume”. System Manager has no way to know how full LUN is. Showing output of “df -k” and “df -r” would be helpful. ... View more

In OCSM – Tools > Options > Browser path ... View more

You just had to do "software install" instead of "software update". "software install" only "unpacks" bundle without trying to perform any post-processing. ... View more

Have you tried to click "Auto Configure"? ... View more

Yes, I noticed too that 2.0.1 became much more responsive. Good to see it is improving ☺ ... View more

Thanks. I guess, it won’t help in this case – we have 12TB of data limping along with 25MB/s. Yes, source aggregate is busy. Attempt to enable VeryHigh priority for system IO did not help. May be at ~170 IOPS per data disk it won’t help much anyway. Unfortunately this has to finish till weekend and we do not have time to open case, because whatever happens it will never be resolved in time to finish (possibly, restarted) replication. We can only hope that source won’t run out of space until initialize is finished. ... View more

Until Data ONTAP 8.x it was not supported to configure both base and VLAN interfaces at the same time. May be, OCSM still does not expect it. Which Data ONTAP version do you have? Make sure to install the latest OCSM 2.0.1; if you still can reproduce it, post on System Manager community. ... View more

Actually specifying existing snapshot is a must in any case - otherwise it will copy active file system which already contains incorrect data. ... View more

It still shows interface c0a, c0b and e0P and makes impression as if you can manage them. I strongly believe those must be hidden, at least from Configuration/Network/Network Interfaces panel. ... View more

These are snapmirror messages (messages come from failed attempt to update snapmirror). I have no idea which is the second source, I do not have access to DOT internals Which information could I provide additionally to help identify the second source? ... View more

The only way I can think of is to use QSM. Start with oldest snapshot, create snapshot on destination, update using next oldest snapshot, create snapshot on destination etc. ... View more