Quantcast
Channel: All ONTAP Discussions posts
Viewing all 19174 articles
Browse latest View live

Name mapping Windows -- Unix

$
0
0

 

Our cDor Cluster runs on  NetApp Release 8.3.2P6. What we ould like to archieve is that we can map a Windows User to any defined Unix User. As you can see below the mapping is configured so that Windows User Dom1\hula sould be mappe to Unix User 1412 (1412 is a different unix user than hula, hula unix user also exists but has different uis)

 

Unfortunately it doesn't work and DOM1\\hula user will get mapped to pcuser, whcih basically is teh default user. It seems that the mapping rules 2 never takes place (tehre is no mapping rule 1 withing the win-unix direction so Position 2 is the first rule).

 

Basically name mapping seems to work becaus if we remove position 2, then the user DOM1\\hula will get map to the unix user hula (which is actually also present in the ldap server where all our unix user are, windows user are in AD and AD doen't have any Unix user information).

 

Was anybody able to map a Windows User to a different Unix user ?

 

 

 

test::vserver name-mapping> show -vserver test01 -direction win-unix
Vserver        Direction Position
-------------- --------- --------
test01         win-unix  2        Pattern: DOM1\\hula
                              Replacement: 1412
test01         win-unix  4        Pattern: DOM1\\(.+)
                              Replacement: \1
test01         win-unix  5        Pattern: DOM2\\(.+)
                              Replacement: \1
3 entries were displayed.

test::vserver name-mapping>

 

 


Re: Powershell Add-NcCifsServer keeps failing - Cannot find an appropriate domain controller

$
0
0

Hello!

 

Plaese run 'DCDIAG /testDNS' utility on Your nearest domain controller and check its output for any issue.

 

It seems to me You have some problems with Your AD.

 

Re: Powershell Add-NcCifsServer keeps failing - Cannot find an appropriate domain controller

$
0
0

Thanks for the suggestion.  Ran dcdiag /test:dns and everything passed.  Everything works fine from the NetApp CLI or with AD in general.  It seems that when the Powershell toolkit issues its calls to Active Directory those calls don't seem to be able to get all the information needed.  I'm not sure what would be different from doing the same thing in Powershell versus the CLI but there seems to be something different.  Thank you.

 

2552 8.2.2 7-Mode > Ontap 9

$
0
0

Been using a 2-node FAS2552 for quite some time for basic NFS/CIFS exports. It's running in 7-mode 8.2.2 at the moment.

 

Snapvault custom schedueles are being used for retention (creating snapshots) and some OSSV jobs running as integrated part of that.

Nothing fancy but I do have some SSD cache disks and 2x fully loaded 2240 behind it.

 

I need advice on whether it would be possible to upgrade to Ontap9? Will I loose any features? If I have a service contract am I entitled to do so without further expenses?

It is my understanding that the entire system must be rebuilt.

 

My primary goal is to gain advantage of the redesigned deduplication and probably a handful of other improved features.

 

It's primary use is as part of a Disaster Recovery site.

This non-critical role makes it possible for me to scratch the whole thing and resync the data afterwards. Meanwhile I can use other resources to retain RTO in my DR.

 

Been reading a lot about the differences between 7-mode and Cluster Ontap mode and still I am unsure if 7-mode actually holds anything that Cluster/Ontap9 can't provide?

 

Also what would be the quickest way to reinstall the system? Must be rather simple as no Copy Based or Copy Free transition is needed.

 

 

Re: 2552 8.2.2 7-Mode > Ontap 9

$
0
0
cDOT does not support OSSV and you cannot use cDOT as disaster recovery partner for 7-Mode (well, you probably can, but just once).

Reinstall is simple, but you need cluster license for this.

Re: Change Managment IP addresses in c-mode

$
0
0

Just an update on this - for cDOT 8.3.  I had some issues finding the correct command with NetApp documentation.  You can change the e0M network interface IP/subnet with the following command (Run this from console connection)

 

CLUSTER::> network interface show -curr-port e0M

displays entries that can be modified for the e0M management port for proper command syntax

CLUSTER::> set advance

advance command structure - approve

CLUSTER::> network interface modify -vserver -lif LIFNAME -home-node HOMENODE -home-port e0M -address IPADDRESS -netmask NETMASK

you may have to include -force-subnet-assocation

The subnet should be created prior to moving IPs from my experience.

Netapp Web GUI Admin and SNMP Monitoring for Displaying Critical Warning Status

$
0
0

We tested the NetApp Storage by shutting down one of its Controller Power Supply and/or its Disk Shelf Power Supply, and we find that sometimes the Web GUI and its SNMP can missed out reflecting the critical warning status properly, and only its Console Command is working properly to display the Critical Warnining status.

 

Our Storage is NetAapp 8.3.1P1.

 

Could there be any latency of the Web GUI and its SNMP to reflect the latest Critical Warning Status, OR the Console Command is a better way to do the Monitoring????

 

Please advise, thanks.

SnapDrive for ONTAP 9.0P1

$
0
0

Hi,

 

I had my FAS2552 upgraded to ONTAP 9.0P1 last week and since then I have gotten a lot of problems that I think originates from SnapDrive. I have updated to version 7.1.3P3.

 

I have Hyper-V servers running over SMB3.0 to the Netapp and the virtual machines still work without problem.

 

However SnapManager for Hyper-V does not work. It is not able to connect to the volumes. So now I don't have any backups...

 

Failed to take backup of VM VMNAME[Hyper-V] as SnapDrive for Windows is unable to enumerate the following components(s) : (Snapshot location is not valid. This could mean the VM may have an unsupported storage configuration. Please confirm that VM's snapshot file location reside on NetApp storage.) for the VM on Hyper-V host HOSTNAME.

 

I think it is because when I open SnapDrive and try to set the Transport protocol settings I am not able to add the NetApps IP adresses.

 

Unable to modify or add transport protocol. Failed to get Data ONTAP version running on the storage system <ip-address>. Error description: Can't connect to host (err=10061).

 

Any tips on what I can try?

Just tested to uninstall and re-install SnapDrive and Snapmanager with no improvment.

 

 


RIP-2 Poisoning Routing Table Modification

$
0
0

Hello colleagues,

 

we are perfroming vulscan against our NetApp systems and there is this finding identified

 

https://w3.secintel.ibm.com/vscan/refs/refs.php?vuln_id=120499

 

I started to investigate its background and its risen one key question, Im not able to find answer to it.

 

What version of RIP protocol Data ONTAP 7mode uses? Is there any way how to determine it on the system?

 

Or do I understand it completely wrong, and RIP version used is not being defined by the NAS at all?

 

 

My current version is 8.2.4P1.

 

Regards

Petr

 

 

fsecurity show UNIX Security

$
0
0

We have an issue with volumes created on our NetApp and the ability to access them from Linux workstations

Background information
- NetApp Release 8.2.1  7 Mode

- NFS v3

 

Having created a new volume with associated share and export, we are mounting them to Ubuntu 14.04 using the umount command.  We have noticed that some of the more recently created volumes are mounted correctly, but it is not possible to access them from the mount point, it returns a message that you do not have sufficient permissions.

 

We have checked the following in he NetApp OnCommand System Manager.....

- The share access controls are everyone - Full control

- The client permissions for Export are set so the UNIX security has the clients All hosts with the permissions Allow Read Write

 

However, we are still not able to resolve the issue.  We have looked into the fsecurity on the SAN and noticed the following.......

 

     The volume James is accessible with read/write permissions from both a windows client and also a Unix workstation (when mounted), so as far as we are concerned, it is set up as we need it to be

 

SAN0D> fsecurity show /vol/James

[/vol/James - Directory (inum 64)]

  Security style: Mixed

  Effective style: Unix

 

  DOS attributes: 0x0030 (---AD---)

 

  Unix security:

    uid: 1000 (projname)

    gid: 1000

    mode: 0777 (rwxrwxrwx)

 

  No security descriptor available.

 

     The James2 volume can be mounted, but is not accessible from the Linux workstation

 

SAN0D> fsecurity show /vol/James2

[/vol/James2 - Directory (inum 64)]

  Security style: Mixed

  Effective style: Unix

 

  DOS attributes: 0x0010 (----D---)

 

  Unix security:

    uid: 0 (root)

    gid: 0

    mode: 0755 (rwxr-xr-x)

 

  No security descriptor available.

 

 

The difference we have noticed is in the Unix Security section with the uid, the gid and the mode.

 

Assuming that this the correct diagnosis of the issue, how do we go about making changes to these settings?

 

 

 

 

 

Re: 2552 8.2.2 7-Mode > Ontap 9

$
0
0

Hi 

 

 

1. Cluster data ontap doesn't support OSSV.

2. You can not maintain snapmirror DR replication between 7-mode and c-mode systems.

3. You can install c-mode dataontap on your old storage frame, for that you need to perchase cluster license and other licenses.

4. All your data will be wiped if you do that.

5. It is better to purchase 2 new controller heads and perform transation to that.

6. You can use copy based and copy free transition from 7-mode to c-mode to migrate all the volumes. Apart from that you can also use cluster snapmirror transition to perform single volume migration from 7-mode to c-mode.

 

Copy based : It uses snapmirror technology to migrate the data from 7-mode to c-mode.

 

Copy free     : We will perform some configurations and later we will swap the disk shelves from 7-mode to c-mode controllers.

 

 

 

Naveenkumar pusuluru

Storage Lead | C3i Healthcare connections

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

 

Re: fsecurity show UNIX Security

$
0
0

Hi 

 

NetApp suggested not to use mixed security style. You can keep ntfs or unix security style and make volume or qtree accessable by giving appropriate entries on usermap.cfs and password file.

 

rdfile /etc/usermap.cfg

 

rdfile /etc/passwd

 

Also please post the output of exportfs and rdfile /etc/exports.

Re: fsecurity show UNIX Security

$
0
0

^^

 

Exactly, you need to pick one, NTFS or Unix.  If this isn't a mixed mount then straight unix security style.

 

If it's a multi-protocol share, NTFS, and then all the permissions are controlled via AD

Re: fsecurity show UNIX Security

$
0
0
What exactly "not accessible" means? Paste exact command and its output (error message) that demonstrates it.

Re: 2552 8.2.2 7-Mode > Ontap 9

$
0
0

Agreed with the others here, OSSV is your main issue as there is no equivalent with ONTAP now.  If you can host the OSSV elsewhere (or use another solution), you'll want to request a Cluster Base license from your partner/rep (it should be free as long as you're under a NetApp Support agreement still).  That said, I've attached a cheat sheet that shows the details on how to set ONTAP to boot to 7-mode or Clustered ONTAP - I can't find the original reference, but again your partner/rep should be able to point you in the right direction should you need more help with the details.

 

Also, for reference the FAS2xxx series is NOT supported for Copy-Free Transition; the explaination I was given is that the engineers writing the procedures and doing the testing didn't realize you could convert a FAS2240-x to a shelf originally and since new hardware has been released a few times since (such as your FAS2552 and the new FAS2650), I suppose they expect smaller customers would still be better off just purchasing a new system and using copy-based transitions.

 

Good luck!


Re: 2552 8.2.2 7-Mode > Ontap 9

$
0
0
Thanks guys. Very informative. I did 8.2.4P4 today and think I will stick with it for now. OSSV is just to vital a part of my strategy. We cant afford to lose it right now.

Re: Name mapping Windows -- Unix

Re: How to suggest right storage and model to customer

Re: increase Volume size in SVM DR

$
0
0

The only time it won't "automatically" grow is if it is in the process of a snapmirror transfer/initilize. 

Re: Netapp cdot 8.3 AV Connector Install

$
0
0

Thank you, it worked for me. Its only a Windows issue.

Viewing all 19174 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>