About fletch2007

fletch2007 · ‎2015-03-26

In 8.1.2 this works: disk assign 6b.71 -s unowned -f ref: https://kb.netapp.com/index?page=content&id=1010853&actp=LIST_POPULAR cheers!

fletch2007 · ‎2014-11-03

Hi, I've got the exact same issue - how did you end up disabling SNMP v1 and v2, configuring v3 on the filer and converting your Zabbix monitoring to use v3? Thanks! Fletcher

fletch2007 · ‎2013-09-19

I used to click on the http://support.netapp.com/myautosupport/index.html link But that page has a FAQ and no data about my filers... Where are my filers (and health etc) thanks

fletch2007 · ‎2013-03-20

Again in the position where my source aggregate is 32 bit and destination is 64 bit and this prevents vfiler online migration. Last year this was a priv set diag command aggr 64bit-upgrade start aggr1 -mode grow-all http://www.gossamer-threads.com/lists/netapp/toasters/11820 In test mode, this completed the 64 bit upgrade quickly and without error. Anyone done this in production? (Ontap 8.1) this will hopefully make our vfiler migrations pass the pre-flight checks. thanks http://vmadmin.info

fletch2007 · ‎2013-03-18

Much appreciated for those links/tools In related vfiler migration news, is there an online method to migrate 32bit aggr vfilers to 64 bit aggr destinations? This restriction is very constraining for us and essentially requires downtime to migrate off 32 bit aggregates, which defeats the benefits of online datamotion. thanks!

fletch2007 · ‎2013-03-18

Hi Adai, 5.1 Online migration attempt of 8.1.2 3270 vfiler to 8.1 3270 (maybe that was the issue 8.1.2->8.1)? SAS->FCAL Since this was a non-critical vfiler I bypassed the error by choosing offline migration and it proceeded. Also today in consultation with Netapp support, I off-lined services on our 5 year old DFM Server and instantiated a fresh instance to get rid of the 5 years of accumulated detritus - vfiler migrations are proceeding much better now. I'd still like to know the origin of this "disk type '' " error thanks

fletch2007 · ‎2013-03-18

have not seen this error before - I'm beginning to think my DFM database needs to be cleared (disk type '' ?) - I tried dfm host discover to refresh, but got the same error Conformance Results === SEVERITY === Error: Source volume 'vdi-vf-01:/vdivms'(5674) disk type is ''. This disk type is not supported for Automated Online Migration. Please try offline migration. === REASON === Migration not supported (Error 23509) === SUGGESTION === No suggested corrective action is available. Anyone seen a solution for this? I have other DFM database issues (with a case open) - can I simply clear the database and start fresh ? thanks

fletch2007 · ‎2013-03-13

DFM database has stale information for a host (it believes snapmirror sync is not licensed - blocking vfiler migrations to this 3250 Ontap 8.1.2 node) When I attempt the dfm host delete -f <ID> I get the following error: C:\>dfm service stop Service: watchdog stopped. Service: server stopped. Service: scheduler stopped. Service: monitor stopped. Service: eventd stopped. Service: http stopped. Service: webui stopped. Service: sql stopped. C:\>dfm service start sql Service: sql started. C:\>dfm host delete -f 152 Error in DELETE FROM objects FROM objects, volumes, vfilers WHERE volumes.hostId = vfilers.vfId AND volumes.volId = objects.objId AND ( vfilers.vfId = 152 OR vfilers.vfHostId = 152 ) : (-198) [Sybase][ODBC Driver][SQL Anywhere]Primary key for row in table 'obj ects' is referenced by foreign key 'objId' in table 'objectToDisplayItemMap' Error: Failed to remove irt-na02.stanford.edu(152). [Sybase][ODBC Driver][SQL Anywhere]Primary key for row in table 'objects' is r eferenced by foreign key 'objId' in table 'objectToDisplayItemMap' C:\>dfm host list -a na02 ID Type Host Name Host Address ProductId Deleted ---- ------------------------ ----------------------------------- ----------------------------------------- ------------ -------- 152 Active/Active Controller na02 11.65.64.114 1573765081 Yes Any idea how to resolve this? I opened case 2004057388 on this If I attempt to re-add/refresh, the stale license info persists for this node (the delete, re-add worked for the partner node) thanks

fletch2007 · ‎2013-03-13

New vFiler migration failure: Pre-flight check FCAL->SAS aggregate fails. The destination has ONLY SAS disk. I opened a case 2004057379 to request a test-point bypass for this check so we can proceed. Ontap 8.1.2, OnCommand 5.1, NMC 3.1 Will this be possible? thanks

fletch2007 · ‎2013-03-12

yes - prefixing with partner showed vfiler and ifconfig as expected thanks!

fletch2007 · ‎2013-03-12

Yes, adding that line resulted in a successful (vfiler NFS remained uninterrupted while the parent node rebooted) While in takeover mode I issue a "vfiler status" on cci-na02: cci-na02(takeover)*> vfiler status vfiler0 running I expect to see the vfiler cci-vf-02 it took over, but I don't. Similarly I issue "ifconfig -a" on cci-na02 and expect to see the ip address of the taken over vfiler, but I do not. Is this hidden in the registry too? thanks

fletch2007 · ‎2013-03-11

cci01-vif0-205 and cci02-vif0-205 are in the same ipspace "v205" - is there a TR doc on this? - thanks cci-na01> ipspace list Number of ipspaces configured: 2 default-ipspace (e0a e0b e1a e2a e3a e3b e0M losk cci01-vif0 cci01-vif0-3162) v205 (cci01-vif0-205) cci-na02> ipspace list Number of ipspaces configured: 2 default-ipspace (e0a e0b e1a e2a e3a e3b e0M losk cci02-vif0 cci02-vif0-3162) v205 (cci02-vif0-205)

fletch2007 · ‎2013-03-11

I'm getting this error during the vFiler migration pre-flight checks: Conformance Results === SEVERITY === Error: Synchronous Snapmirror license required on storage system 'na01'(151) for Automated Online Migration. === REASON === Migration not supported (Error 23509) === SUGGESTION === No suggested corrective action is available. Snapmirror is licensed on na01 and snapmirror_sync shows ENABLED I did a dfm host discover na01 in case it was a stale DFM DB issue - no change thanks for any tips!

fletch2007 · ‎2013-03-11

I'm getting these errors on cci-na02 (where I initiated the "cf takeover" to test): cci01-vif0 is not mapped to a local ifgrp ipspace command cannot be run in partner mode ipspace command cannot be run in partner mode ifconfig: 'cci01-vif0-205' cannot be configured: Address does not match any partner interface. ifconfig: cci01-vif0-205: no such interface Do the ifgrp names need to match? What am I missing? - thanks Here is the cci-na02 /etc/rc #Auto-generated by zapi_net_config Mon Mar 4 11:26:51 PST 2013 hostname cci-na02 ifgrp create single cci02-vif0 e1b e2b vlan create cci02-vif0 205 ipspace create v205 ipspace assign v205 cci02-vif0-205 vlan create cci02-vif0 3162 ifconfig cci02-vif0-3162 `hostname`-cci02-vif0-3162 netmask 255.255.254.0 partner cci01-vif0-3162 up route add net default 10.39.22.1 1 options dns.enable on options nis.enable off savecore cci-na01's /etc/rc #Auto-generated by zapi_net_config Mon Mar 4 11:26:51 PST 2013 hostname cci-na01 ifgrp create single cci01-vif0 e1b e2b vlan create cci01-vif0 205 ipspace create v205 ipspace assign v205 cci01-vif0-205 vlan create cci01-vif0 3162 ifconfig cci01-vif0-3162 `hostname`-cci01-vif0-3162 netmask 255.255.254.0 partner cci02-vif0-3162 up ifconfig cci01-vif0-205 `hostname`-cci01-vif0-205 netmask 255.255.255.0 partner cci02-vif0-205 up vfiler run cci-vf-02 route add net default 172.25.124.1 1 route add net default 10.39.252.1 1 options dns.enable on options nis.enable off savecore

fletch2007 · ‎2013-03-08

Ok, I destroyed and re-created - and the only line it added was the ifconfig line. Turns out I had a duplicate /etc/rc line which interfered on the last reboot test. This time it all came up clean thanks!

fletch2007 · ‎2013-03-08

So I used the command line vfiler create <vfilername> -s <ipspace> -i ipaddress <path> then was PROMPTED for additional settings like netmask etc. What /etc/rc form do those PROMPTED variables take? If I used System Manager instead of the command line, would it write those /etc/rc lines for me? thanks!

fletch2007 · ‎2013-03-08

I chose a new vlan for the default-ipspace. Now I am vetting my new "ipspace-ified" /etc/rc file Q: Previously each vfiler used to have an /etc/rc line "ifconfig <interface> alias <vfilerIPaddress..." What is the ipspace-ified version (since the command I used to assign IP was during the vfiler create stage - but obviously the create is a one time operation so not appropriate for the /etc/rc file) Or are these ifconfig alias cmds no longer required with ipspaces? thanks!

fletch2007 · ‎2013-03-07

Thanks - I worked that out just now. So I have migrated a vfiler (destroyed it, and created it in v205 with the original volume and the exports file restored) from the default-ipspace to the v205 space where vlan 205 is defined. Now, I need to assign an IP to the default-ipspace so I can administer this head so does this need to be a unique vlan? Or can the same vlan exist in multiple ipspaces? cci-na01> ipspace list Number of ipspaces configured: 2 default-ipspace (e0a e0b e1a e2a e3a e3b e0M losk cci01-vif0) v205 (cci01-vif0-205) thanks

fletch2007 · ‎2013-03-07

I'm reading up on ipspaces - assign ipspacename interface-list Assigns the named interface(s) to the named ipspace. The named interface(s) must not be configured with any addresses. Trunked interfaces and base VLAN interfaces cannot have their ipspace reassigned. All interfaces start off by being in the default-ipspace. Does this imply ipspaces must have dedicated physical interfaces? We only have 2 x 10g (e1b, e2b) interfaces and use a single mode interface group for redundancy. How would you configure this with multiple ipspaces sharing the same 2 physical nics? thanks

fletch2007 · ‎2013-03-04

Scott - turns out you posted the solution in this thread https://communities.netapp.com/thread/17394 dfm option set discovervfilers=yes For some reason this was disabled ! "Failed to discover the destination vFiler unit." turned out to be the most relevant error I've seen in a long while! Now onto testing migration to ip-spaces - fun! thanks!

fletch2007 · ‎2013-02-27

Thanks Scott - With the 32->64bit check passed (by going 64->64bit), my test data motion is now failing on "Failed to discover the destination vFiler unit." Job Started. Successfully provisioned flexible volume 'cci-na01:/stride4'(5194) of size 25.0 GB with space guarantee set to 'volume' on aggregate 'cci-na01:aggr0'(5041). Online Migration initiated, waiting for baseline transfer to complete... An error occured: cci-na01: Failed to discover the destination vFiler unit. Clearing the destination IP bindings of vFiler unit stride-vf-04 Destroyed the provisioned volume 'cci-na01:/stride4'(5194) on 'cci-na01'(5040). Job completed with errors. on the console of the destination (cci-na01) - I see: Sun Jun 17 08:51:38 PDT [cci-na01:ndmp.authentication.accept:info]: ndmpd(authtype+password) allowed for version = 4, sessionId = 35482, from src ip = 11.65.64.19, dst ip = 12.25.124.84, src port = 3938, dst port = 10000 Sun Jun 17 08:51:38 PDT [cci-na01:ndmp.connection.close:info]: ndmpd session closed successfully for version = 4, sessionId = 35482, from src ip = 11.65.64.19, dst ip = 12.25.124.84, src port = 3938, dst port = 10000 Sun Jun 17 08:51:42 PDT [api_mpool_05:warning]: registry: Unexpected error in rollback in regx_commit - Error: No such file or directory (name=options.files.snapmirror.conf.cci-na01:stride4) Sun Jun 17 08:51:43 PDT [cci-na01:wafl.vvol.offline:info]: Volume 'stride4' has been set temporarily offline Sun Jun 17 08:51:43 PDT [cci-na01:wafl.vvol.destroyed:info]: Volume stride4 destroyed. Any ideas how to resolve? thanks!

fletch2007 · ‎2013-02-27

Ok, we took delivery of a new 3250 running 8.1.2 7-mode - for some reason the forum is not showing me the option to create a NEW post, so I'll reply to this thread from 2011. I am trying a test vfiler migration from our 3270 (8.1 7-mode) to the 3250. Its failing on this check (below) Is is the 32->64bit or the FC to SAS or 3270->3250, or something else? Successful non-disruptive vFiler migration from the 3270 to 3250 will make a BIG difference in planning (downtime) and customer impact thanks Conformance Results === SEVERITY === Error: Failed to select a resource. === ACTION === Select a destination resource for migrating === REASON === Storage system : 'cci-na01'(5040): - There are no aggregates with enough space and reliability/label match for all the volumes in the vFiler unit. Storage capacity configurations and reliability requirements of volumes in the vFiler unit: Volume 'stride-vf-04:/stride4'(5036): Used space: 1.45 MB Current size: 50.0 GB (volume guarantee) Block type: 32-bit Disk type: FCAL Aggregates, their capacities and configurations: Storage system 'cci-na01'(5040): Aggregate 'cci-na01:aggr0'(5041): Used space: 237 GB Total capacity: 24.5 TB Committed size: 227 GB Block type: 64-bit Disk type: SAS Configuration: Double disk failure protection === SUGGESTION === Suggestions related to storage system 'cci-na01'(5040): - Add more resources to the resource pool or select a different storage system.

fletch2007 · ‎2012-11-06

Thanks for the link - I checked all the VAAI boxes and cloned a VM on NFS datastore - no esxtop VAAI counters moved In fact, you can see the NFS counters are '-' instead of zero - @that1guynick commented 11 months ago "doing some deep testing of NFS VAAI offload that will be supported in the next (8.1) release of DataONTAP coming soon!" Well I guess that schedule slipped - we are on 8.1.1 and still no NFS VAAI support? (even though the NFS datastore is listed as "supported" in vCenter)

fletch2007 · ‎2012-10-31

Thanks - I was testing this in our DR cluster, I'll see if our account folks can hook us up with pre-GA access

fletch2007 · ‎2012-10-31

Was very excited to see VSC 4.1 scan my NFS datastores and select unaligned VMs for migration to "optimized" datastores Was less excited to see VSC 4.1 still does not support migration TO optimized NFS datastores (only iSCSI and FC currently - which we don't use) I wrote up our experiences testing VSC 4.1 Optimization and Migration (aka alignment) here: http://www.vmadmin.info/2012/10/aligning-vms-via-netapp-vsc-41.html

Re: how to reassign disks

Re: Disable SNMPv1/2c authentication. Use SNMPv 3 only

How to launch myautosupport (MyASUP)?

upgrade 32->64 bit aggr/vols non-disruptively, without adding disk

Re: vfiler migration error, disk type is ''. This disk type is not supported for Automated Online Mi...

Re: vfiler migration error, disk type is ''. This disk type is not supported for Automated Online Mi...

vfiler migration error, disk type is ''. This disk type is not supported for Automated Online Migrat...

Re: Netapp Operations Manager 4.0.0 - Not reporting on two filers

Re: vFiler migrate fails with FAS3270 not supported as destination

Re: Multistore failover

Re: Multistore failover

Re: Multistore failover

Synchronous Snapmirror license required on storage system

Re: Multistore failover

Re: Migrating a VFiler to a new IPspace

Re: Migrating a VFiler to a new IPspace

Re: Migrating a VFiler to a new IPspace

Re: Migrating a VFiler to a new IPspace

Re: Migrating a VFiler to a new IPspace

Re: vfiler Migration fails: maximum of 4 volumes for Automated Online Migration

Re: vfiler Migration fails: maximum of 4 volumes for Automated Online Migration

Re: vfiler Migration fails: maximum of 4 volumes for Automated Online Migration

Re: VSC 4 missing VAAI and getting no VMs for aligned/not aligned

Re: VSC 4.1 still not able to align NFS VMs

VSC 4.1 still not able to align NFS VMs