About aborzenkov

aborzenkov · ‎2012-06-20

Yes with QSM, no with VSM

aborzenkov · ‎2012-06-19

BMC does not have own users, it “inherits” them from Data ONTAP. Password for BMC “naroot” is the same as password for Data ONTAP “root”. So yes, you need to complete Data ONTAP setup at least once to sync users with BMC. At least, I do not know other way. May be, Scott knows some other tricks.

aborzenkov · ‎2012-06-18

Naroot is default user for BMC, not for Data ONTAP. BMC does not support HTTP(S) - the only protocol is SSH and the only way to access Data ONTAP from BMC is to open console session.

aborzenkov · ‎2012-06-18

Your data won’t be lost. You can find detailed description in Upgrade and Revert Guide for target Data ONTAP version as well as in Upgrade Advisor in My Autosupport.

aborzenkov · ‎2012-06-18

Does it still happen if you try to disable option ip.fastpath?

aborzenkov · ‎2012-06-18

Update to the current Data ONTAP 7.3.7. 7.0.6 is really old.

aborzenkov · ‎2012-06-18

Does the following work? cf.hw_assist.partner.address “” otherwise if hw_assist is disabled, this option is irrelevant anyway. Why do you want to clear it explicitly?

aborzenkov · ‎2012-06-17

Such tool is available internally and to NetApp partners. Otherwise this information is stored in NetApp database, and can be used to troubleshoot performance issues.

aborzenkov · ‎2012-06-16

I noticed the following in Block Management Guide (Mapping read-only LUNs to hosts at SnapMirror destinations): The destination LUN is also assigned a new serial number. I always thought that LUN serial is LUN property kept together with LUN itself. But then how can it be changed on fundamentally read-only destination? Or is it kept in some external global location?

aborzenkov · ‎2012-06-16

Well, I have deleted message.

aborzenkov · ‎2012-06-16

Release notes for RLM 4.1 mention this bug, but it does not have public information. Anyone can explain what it does? Does it add support for configuration of RLM interface from within RLM CLI itself? Because we could always "manually" configure RLM from Data ONTAP.

aborzenkov · ‎2012-06-15

You could try takeover/giveback (which is in effect rebooting controller). But in general changing shelf configuration is twilight zone where everyone tends to be on the safe side and say it must be done offline.

aborzenkov · ‎2012-06-15

From snapshot or backup.

aborzenkov · ‎2012-06-15

Such names are seen in case of duplicate shelf id. Verify that shelf has unique id. And yes, to change SAS shelf id you need poser cycle it.

aborzenkov · ‎2012-06-14

10 thousands of microseconds is not huge. It is just 10ms, which is not spectacular, but far below "huge".

aborzenkov · ‎2012-06-14

Because it has routing table telling it to do so.Double check it.

aborzenkov · ‎2012-06-14

beyond enabling it for igroup - no.

aborzenkov · ‎2012-06-14

This depends on path grouping policy in multipathd configuration.

aborzenkov · ‎2012-06-14

What exactly do you mean? You can access the same LUN via either FCP or iSCSI or both; there is no need to convert anything.

aborzenkov · ‎2012-06-10

Yes, you can mix shelves in this case. I believe the latest wireguage 2.1.1-16032012.1324 should be fixed to not complain on FAS2240, but I cannot find any changelog. Thanks to Aaron, here is readme for the latest WireGauge: WireGauge 2.1.1 --------------- * False warning when IOM3 and IOM6 modules are mixed in the same stack for Vespa platform is resolved.

aborzenkov · ‎2012-06-08

Of course, 8.1 adds fourth possibility - convert 32 to 64 in place

aborzenkov · ‎2012-06-08

Two controllers are mostly independent. No configuration is propagated to partner; each is configured separately. For network failover you have to ensure that both controllers have access to the same VLANs and interfaces in the same VLANs are mutually marked as "partner". But physical configuration of these interfaces can be different. In your case it makes sense to make configuration symmetrical, it is easy to administer. Keep in mind, that ports from different controllers cannot be in the same LACP port group, communication won't work.

aborzenkov · ‎2012-06-08

iscsi was free on all controllers back then and cifs setup would have worked the based on that That's most likely reason.

aborzenkov · ‎2012-06-08

That’s correct, block protocol licenses enable some CIFS functionality; but I have never heard it was possible with NFS only filer.

aborzenkov · ‎2012-06-08

Yes, you can add new shelves online.

Re: Can multiple source volumes be snapmirror into a single destination volume

Re: onTap 8.1.7 on 2040 - default ssh password / no htttp access

Re: onTap 8.1.7 on 2040 - default ssh password / no htttp access

Re: Oncommand System Manager for Data Ontap 7.0.6

Re: Route added automaticly ??

Re: Oncommand System Manager for Data Ontap 7.0.6

Re: How to clear the options setting of cf.hw_assist.partner.address

Re: How do I read a notification from NetApp Appliance

Are LUN serials kept in separate location from LUN itself?

Re: FAS2050 and SSD

Bug 571684: Manual configuration of RLM eth port?

Re: Funny disk name

Re: Wrfile on /etc/messages

Re: Funny disk name

Re: PA and protocol latency reporting

Re: BUG on autosupport on 8.1RC2. When it will be fixed?

Re: Alua enabled linux igroup

Re: Alua enabled linux igroup

Re: Any Procedure to convert FC to ISCSI and vice-versa in netapp?

Re: FAS2240-2 4243 and 2246 on same loops?

Re: Best method to migrate data from 32 bit aggregates to 64 bit aggregates?

Re: FAS2240-2 setup

Re: Manage a Filer with a AD account without a CIFS License

Re: Manage a Filer with a AD account without a CIFS License

Re: Adding disk shelf with root volume to other filer