ONTAP 9.1RC1 on 6-node cluster

HI,

I just notice on my cluster, an SVM has the following routes:

ntap01::> network route show
Vserver             Destination     Gateway         Metric
------------------- --------------- --------------- ------
vs1
                    0.0.0.0/0       172.25.0.1      20
                    0.0.0.0/0       192.168.87.1    20

The SVM has LIFs on these two subnets (one for data and the other for backup traffic). I am wondering the above routes pose any risks espeicially they both have same metric value. Is it smart enough to know that if the LIF is on 172.25.0.0 subnet, use the 1st route for outgoing traffic and if the LIF is on 192.168.87.0 subnet, use the 2nd route?

Thanks,

1)In the below ypwhich o/p is "Not bound to any nis server" does this confirm nis not in use

2) How to confirm in current environment what are the services nis is providing (whether its hosts,netgroup,groups,password services)

raman1*> options nis

nis.domainname               bpxa

nis.enable                   on

nis.group_update.enable      on

nis.group_update_schedule    6,7,8,9,10,11,12,13,14,15,16,17,18,24

nis.netgroup.domain_search.enable on

nis.netgroup.legacy_nisdomain_search.enable on

nis.servers                  161.99.65.8,161.99.65.10

nis.slave.enable             off

ramancss003*> ypwhich

Not bound to any NIS server.

ramancss003*>

raman4> options nis

nis.domainname               bpxa

nis.enable                   on

nis.group_update.enable      on

nis.group_update_schedule    6,7,8,9,10,11,12,13,14,15,16,17,18,24

nis.netgroup.domain_search.enable on

nis.netgroup.legacy_nisdomain_search.enable on

nis.servers                  161.99.65.8,161.99.65.10

nis.slave.enable             off

ramancss004*> ypwhich

Not bound to any NIS server.

ramancss004*>

Looking at a customers CIFS SVMs we note that some of the DCs connected to the SVM report as slow an one unavailable.

Is there any detail about these conditions and what tests the SVM uses to determine the condition of a discovered server.  i.e. if a DC is labled as slow, what is the definition of slow that has been used?

Possible DC statis results

OK

Unavailable

Slow

Expired

Undetermined

Unreachable

Anyone know if there is any cmdlets available output volume full and nearly full thresholds?

I noticed that it is now available for Aggregates ( v8.3+) for cDOT from Get-NcAggrOption ( full_threshold,nearly_full_threshold), but did not see the equivalent properties for Volumes from Get-NcVolOption. It will be handy and much easier to have such attributes from ONTAP directly other than going through OCUM. I am still using DataONTAP PSTK v3.2.0, not sure if this version matters.

Thanks,

Timothy

Hi.

On my FAS2554 cluster running Data Ontap 8.2.3P9 I reached maxdirsize on one directory of a volume.

For now I increased the maxdirsize value for this volume and now I am archiving some old data just to solve the immediate problem, but I need to definitively solve this problem to avoid it in the future.

The problem is that I cannot predict how many files will be added to this directory, just because they are thousands of new static files each days, automatically created depending on new contents created by the systems (they are attachments of contents). The value of new content every day is not regular.

I was thinking about organizing these files in a subdirectories tree, but NetApp Support told me that this would not solve the problem as the maxdirsize is calculated on the parent directory and all subdirectories are taken for its calculation.

So how I can solve this problem without creating new volumes? I want to apply a scalable way, and I wish the only limitation to be the volume size and not any other parameters I could not manage automatically.

Could you help me please?

Thanks!

Hi all,

I'm in a process of writing a DR procedure for a customer and I would like to propose it the SVM DR solution for their CIFS Share instead of multiple SnapMirror Volume replication.

All the FAS are running the latest ONTAP 9.1, the SVM DR is running perfectly but I wonder if the future roadmap include the possibility to manage an activated DR SVM from the destination SystemManager, in case of a long disaster scenario.

From now, even when I start the destination SVM and stop the source one, I cannot manage the volume, share or quota with web interface. For a customer point of view, it would be very more efficient, intuitive and user-friendly to access the configuration of the destination SVM from SysMgr

Hi all,

does anybody have a Cisco 9148 RCF for an 8-Node MetroCluster using 6500N Attos? I'm about to write the config by myself, but I first want to ask the community if maybe somebody already did this, because on the support page you only find RCF for 4-Node Metroclusters!

Thank you!

Regards,

Netsu

Is it possible to alter the default TCP window size on a snapmirror initialize?   We have a need to migrate clients to a new IDC,  The link has signficiant latency and the snapmirror process is extremely slow and runs for days.  Normal production snapmirror between DR sites is fine and i don't want to impact current production..    I would like to test a larger TCP Window size for an individual replication.    I have read that an individual transfer can have an altered TCP window size as defined in the snapmirror.conf file.   The problem migrations are 'one and done' type operations,  the cli is used to run the 'snapmirror initialize' command.  Is there a way to altrer the TC{ window size in the initialize command ?   Is there a way to have the initialize command read the snapmirror.conf file?    Any suggestions woulld be appreciated.   currently testing in 7-mode envrionment running 8.2.3P2,   eventually Cdot environments will likely need to be addressed as well.     

Hi all,

I am working on automation to monitor all 7mode/cmode storage systems we have by checking for netport port status. Through the automation, we want to check if the ports part of ifgroup are up and working, MTU settings and if there are any CRC errors. 

Using NMSDK, i can get ifgroup and MTU details of the interfaces. I found no option to get CRC errors listed for an interface in the system. Is there any option we have to get CRC error details from netapp API? 

RECEIVE
Frames/second: 25446 | Bytes/second: 16472k | Errors/minute: 0
Discards/minute: 0 | Total frames: 137g | Total bytes: 281t
Total errors: 0 | Total discards: 0 | Multi/broadcast: 0
No buffers: 0 | Non-primary u/c: 0 | L2 terminate: 0
Tag drop: 0 | Vlan tag drop: 0 | Vlan untag drop: 0
Vlan forwards: 0 | Vlan broadcasts: 0 | Vlan unicasts: 0
CRC errors: 0 | Runt frames: 0 | Fragment: 0
Long frames: 0 | Jabber: 0 | Bus overruns: 0
Queue drop: 0 | Xon: 0 | Xoff: 0
Jumbo: 2833m

Hi All

Just a quick question about removing snapmirrored/vaulted volumes as I have had an issue in the past and just wanted to confirm the correct steps to be taken.

The previous issue I had was related to deleting a snapvault relationship after clearing an old relationship. This relationship sat on our destination filer and vaults from a snapmirror relationship which is also replicated to this filer. It had originally removed from view but reappeared. When trying to release the relationship I was getting a message saying "no releaseable destination found that matches those parameters".

We have 2 NetApp filers at 2 separate sites, snapmirror occurs on the volumes from Site A to Site B, on Site B we then use SnapVault to a separate volume for retention backups. We are using 7-mode 8.2.3P3 on both filers.

I normally follow the below steps when removing volumes. All of our volumes are fibre channels LUNs presented to VMware for serving datastores to our virtual machines.

1. Perform VMware tasks such as unmounting and deleting the datastores in the vSphere web client
2. Break snapmirror relationship for volume being decommissioned by doing a quiesce followed by a break, I normally do this from the source filer. Check relationship is removed from view in Production and DR filers using On command system manager.
3. On Source NetApp filer, go to LUNs, and offline the LUN in question, followed by deletion of LUN.
4. On source NetApp filer, go to volumes, offline the volume and then delete the volume.
5. On destination filer remove any schedules for the snapvault relationship to be removed.
6. On destination filer stop the related snapvault relationship, followed by release.
7. Once snapvault relationship deleted, remove snapvault source and destination volume once sufficient snaps have built up by offline LUN, delete LUN, offline volume and delete volume.

Any steps I have missed of any advice if there is a better way to do this would be much appreciated.

Many Thanks in advance for your help.

I have  case opened with NetApp but their explanation of...

this is a cosmetic, presentational blip. Everything is working fine on the backend and those blocks in the snapshots are OK. To counter any confusion with monitoring/reporting, the volume-level snapshot consumption can be manually verified using “df -fs-type snapshot -h”.

...does not sit well with me.

Of my 50+ volumes across 15 aggregates, only one (1) volume exhibits this behavior.  Other volumes on the same aggr as the troubled volume ALL have snapshot size values > 0B

My daily snapshots since 20170505 all show 0B in size.  Snapshots on that volume from 20170316 to 20170504 show values in the 100s of GB.  So clearly something happened between May 4th and 5th.

Has anyone else seen this behavior on such a limited scale - only 1 volume?  I get the whole "block reclaimation" explanation, but I find it hard to believe that after 36 days THIS ONE volume is having trouble completing the process when all other volumes (volumes busier, more utilized, etc.) show no 0B snapshots.

Thank you for any feedback you may be able to lend here.

Snapshot list:

(Abbreviated for your protection)

                                                             ---Blocks---
Vserver  Volume   Snapshot                           Size    Total% Used%
-------- -------- ---------------------------------- ------- ------ -----
SVM_01   vol_02
                  smvi_Daily_novmsnap_20170316030002 187.2GB      1% 4%
                  smvi_Daily_novmsnap_20170317030002 83.80GB      0% 2%
                  smvi_Daily_novmsnap_20170318030001 79.50GB      0% 2%
                  smvi_Daily_novmsnap_20170319030002 94.93GB      0% 2%
                  smvi_Daily_novmsnap_20170320030002 76.66GB      0% 2%
                  smvi_Daily_novmsnap_20170321030001 101.6GB      0% 2%
                  smvi_Daily_novmsnap_20170322030002 111.7GB      1% 2%

                                          ...

                                          ...
                  smvi_Daily_novmsnap_20170429030002 87.34GB      0% 2%
                  smvi_Daily_novmsnap_20170430030003 79.46GB      0% 2%
                  smvi_Daily_novmsnap_20170501030002 88.73GB      0% 2%
                  smvi_Daily_novmsnap_20170502030002 159.5GB      1% 4%
                  smvi_Daily_novmsnap_20170503030002 77.27GB      0% 2%
                  smvi_Daily_novmsnap_20170504030002 80.65GB      0% 2%
                  smvi_Daily_novmsnap_20170505030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170506030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170507030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170508030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170509030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170510030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170511030001      0B      0% 0%
                  smvi_Daily_novmsnap_20170512030003      0B      0% 0%
                  smvi_Daily_novmsnap_20170513030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170514030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170515030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170516030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170517030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170518030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170519030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170520030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170521030003      0B      0% 0%
                  smvi_Daily_novmsnap_20170522030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170523030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170524030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170525030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170526030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170527030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170528030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170529030001      0B      0% 0%
                  smvi_Daily_novmsnap_20170530030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170531030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170601030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170602030001      0B      0% 0%
                  smvi_Daily_novmsnap_20170603030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170604030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170605030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170606030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170607030002      0B      0% 0%
                  smvi_Daily_novmsnap_20170608030001      0B      0% 0%

85 entries were displayed.

Just a quick question I hope.  I am migrating an older ONTAP 8.2 (7-mode)  filer.  I believe it had SLAG enabled on a UNIX volume primarily to enable CIFS auditing.

This SLAG setup may have been present when the filer was initially at 7.x levels, but that is a guess and before my time.

I suspect that at ONTAP  9.x  SLAG is not required for auditing.  When I searched the CIFS and NFS Auditing guide for SLAG I found no references to SLAG.

So am I correct in believing that SLAG is nolonger required for UNIX (NFS) auditing because of the nfsv4  acls be available now ? 

I would ideally like to simplify the auditing and remove the SLAG if its not needed for enabling auditing anymore.

Rgds AndyP

Hi

I installed ONTAP 9.2RC on our lab system and I feel like System Manager got worse than in ONTAP 9.1.

Simple trick, can you please find where I can view information about snapshots in SM 9.2? I clicked menues for 2-3 minutes till find where I can do that? What does marketing say about simple interface?

There are many things changed in 9.2 interface and most of them are not straight forward to find/understand IMHO. I feel tab like interface was better.

What do you think?

Nick

I logged a support call via NETAPP partner program (IBM)  I believe they then pass on cases to NETAPP they do not solve.   I was

told 7MTT was not supported.

"I'm sorry to inform you but apparently we do not support the migration process nor the 7MTT tool."

So my question is I need some guidance on this 7MTT warning,  I have already migrated 14 vfiler and filer and not seen this

warning before.

PreCheck:

warning (21062)   Failed to collect the CIFS Share ACLs configuration from the following 7-Mode storage systems.

Any advice welcome.

Rgds AndyP

Hello,

With ONTAP Select Deploy 2.3 and 2.4, I got an error when creating a Cluster. The node cannot be created with the following error.

I tried with Web GUI and CLI.

How to solve this issue ?

ONTAP Select deploy Event :

ClusterNodeCreateFailed: One of the node create operations failed during cluster "CLU_TEST" create.

NodeCreateFailed: Node "CLU_TEST-node1" create failed: Cannot create VM 'CLU_TEST-node1' (errType=InvalidRequest).

sdotadmin_server.log :

2017-06-09 09:16:40,046|DEBUG response body: {"code":56,"details":"Cannot create VM 'CLU_TEST-node1' (errType=InvalidRequest)","type":"VmCreateOvfErr"}
response body: {"code":56,"details":"Cannot create VM 'CLU_TEST-node1' (errType=InvalidRequest)","type":"VmCreateOvfErr"}
2017-06-09 09:16:40,060|ERROR |client_api_helper.py|183:vm_create| Error: NodeCreateFailed: Node "CLU_TEST-node1" create failed: Cannot create VM 'CLU_TEST-node1' (errType=InvalidRequest).
|client_api_helper.py|183:vm_create| Error: NodeCreateFailed: Node "CLU_TEST-node1" create failed: Cannot create VM 'CLU_TEST-node1' (errType=InvalidRequest).
2017-06-09 09:16:46,431|DEBUG response body: {"code":13,"details":"<vmname> invalid - no vm named 'CLU_TEST-node1' on host 'nte-esx01.mqt02.mqt'","type":"InvalidArg"}
response body: {"code":13,"details":"<vmname> invalid - no vm named 'CLU_TEST-node1' on host 'nte-esx01.mqt02.mqt'","type":"InvalidArg"}
2017-06-09 09:16:46,844|ERROR |cluster_tasks.py|519:_create_nodes| Cluster [CLU_TEST]: one or more of node create tasks failed, initiating rollback
|cluster_tasks.py|519:_create_nodes| Cluster [CLU_TEST]: one or more of node create tasks failed, initiating rollback
2017-06-09 09:16:46,845|ERROR |cluster_tasks.py|520:_create_nodes| Error: ClusterNodeCreateFailed: One of the node create operations failed during cluster "CLU_TEST" create.
|cluster_tasks.py|520:_create_nodes| Error: ClusterNodeCreateFailed: One of the node create operations failed during cluster "CLU_TEST" create.
2017-06-09 09:16:46,845|ERROR |cluster_tasks.py|277:create_cluster| Cluster [CLU_TEST]: cluster create failed
|cluster_tasks.py|277:create_cluster| Cluster [CLU_TEST]: cluster create failed
2017-06-09 09:16:46,849| INFO |cluster_tasks.py|292:create_cluster| initiating rollback of failed cluster (CLU_TEST)
|cluster_tasks.py|292:create_cluster| initiating rollback of failed cluster (CLU_TEST)
2017-06-09 09:16:46,856|DEBUG |cluster_tasks.py|331:delete_cluster| Delete cluster "CLU_TEST"
|cluster_tasks.py|331:delete_cluster| Delete cluster "CLU_TEST"
2017-06-09 09:16:46,885| INFO |cluster_tasks.py|421:delete_cluster| Cluster [CLU_TEST]: all nodes in cluster are deleted, deleting cluster db
|cluster_tasks.py|421:delete_cluster| Cluster [CLU_TEST]: all nodes in cluster are deleted, deleting cluster db
2017-06-09 09:16:46,886| INFO |cluster_tasks.py|427:delete_cluster| cluster (CLU_TEST) deleted

Regards,

Cyrille

Did you know you can...

Quickly update your version of ONTAP using OnCommand System Manager?

1. Log in to OnCommand System Manager.
2. Click Configurations> Cluster Update.
3. Follow the steps in the Cluster Update wizard to perform the upgrade.

For more information, please see the ONTAP 9 documentation center.

Did you know you can...

Secure data at rest using software encryption and the onboard key manager?

If you have existing infrastructure and want to encrypt your data for compliance or standard security best practices, use the NVE software-based data-at-rest encryption feature for any SSD or disk type:

1. Install the NetApp volume encryption (NVE) license for each node.

  system license add -license-code license_key

2. Start the key manager setup wizard.

  security key-manager setup

3. Create a new volume and enable encryption on the volume.

   volume create -vserver SVM_name -volume volume_name 
  -aggregate aggregate_name -encrypt true

Example: cluster1::> volume create -vserver vs1 -volume vol1 -aggregate aggr1 -encrypt true

4. Verify that the volume is enabled for encryption.

  volume show -is-encrypted true

For more information, please see the ONTAP 9 documentation center.

Did you know you can…

Prioritize business critical applications using QoS Min?

QoS allows you to isolate business-critical applications to ensure they meet required performance. To set up QoS Min in your system:

1. Log in to OnCommand System Manager.
2. Select the Business-Critical Volume followed by Actions, Storage QoS.
3. Set the Minimum Throughput to 40,000IOPS .

4. From the performance dashboard observe that the service level guarantee of 40,000 IOPS is met and latency is reduced.

     Note that the test and dev workloads may see impacts meaning fewer IOPS and higher latencies.

 For more on QoS watch:

For more information, please see the ONTAP 9 documentation center.

Hello,

I am wondering what happens in a multple SVM scenario when SVM A destroy a volume X.  Then if SVM B creates a new volumes Y where blocks previously belonging to volume X  are now belonging to Y.  Is the data from volume X available through volume Y ?

Basically, how can I reassure a very cautious tenant about the security of his data.  Is there official documentastion on this ?

Thank you, 

Simple.... A pair of Windows 2012 with clustering turned on has a LUN presented via vmware RDM (ram device mapping). I know VSC is required for ESX. Should HOST UTILITIES be installed. Whether needed??? or good for future diagnostics? Official stance?
     *** Running CDOT 8.3.1... ESX 5.5 with LUNs presented via FCoE...
The Install Doc states: "enable you to connect host computers to virtual disks (LUNs) on NetApp storage systems"... but then goes on to talk about HBA's which don't exists in my case [at least not at the guest level].