Change disk ownership

What to do if a disk has been inserted into a Netapp Clustered Ontap system and that disk already has a disk ownership assigned to it. Remove the disk ownership and re-assign this disk to the new node. netapp1::> Set diag netapp1::*> disk assign -disk NODE2:2c.10.0 -owner NODE1 -force-owner true If this command does not work or you get the following Error: command failed: Failed to find node ID for node, you can use these 2 commands to remove ownership or modify ownership: netapp1::*> disk removeowner -disk NODE2-2c.10.0 -force true netapp1::*> disk modify -disk NODE2:2c.10.0 -owner NODE2 -force-owner true

Cannot remove node from cluster when auditing active

When you have the issue “Failed to disable cluster-scoped metadata volume support prior to unjoin operation”: clA::*> cluster unjoin -node clA-01 -force true Warning: This command will forcibly unjoin node “clA-01” from the cluster. You must unjoin the failover partner as well. This will permanently remove from the cluster any volumes that remain on that node and any logical interfaces with that node as the home-node. Contact support for additional guidance. Do you want to continue? {y|n}: y [Job 1819] Checking prerequisites Error: command failed: [Job 1819] Job failed: Failed to disable cluster-scoped metadata volume support prior to unjoin operation. Reason: All cluster-scoped volumes are still online. Remove all the volumes onRead More

What if the e0M is connected to the same subnet as data?

Sometime you can have problems like: Network performance over ethernet networks after reboot/maintenance has degraded. Slow backup and transfer issues are reported on a storage system when performing the following backup and transfers: NDMP backup SnapMirror transfer SnapVault transfer Messages and EMS logs will warn with the following messages (IPv4 or/and IPv6 accordingly): [netapp: netmon_main: net.if.mgmt.sameSubnet:warning]: ifconfig: IP address ‘x.x.x.x’ configured on dedicated management port ‘e0M’ is on the same subnet as IP address ‘x.x.x.x’ configured on data port Prod1. Management IP addresses must be on dedicated management subnets. [net.if.mgmt.defaultGateway:warning] route: Static or default route with gateway ‘x.x.x.x’ is targeted to dedicated management interface ‘e0M’. Data traffic using this routeRead More

Collect diagnostic information from AIX and PowerVM

Utilize the NetApp nSANity tool that comes in one of two formats, a Windows based GUI tool and a command line tool, available for both Windows and BASH command lines. AIX hosts need to have data gathered from any host needing analyzed that has SAN access. If the LPAR is a PowerVM guest partition, the information will need to be gathered from the PowerVM hosts through hwich the LPAR makes connection to the SAN. If the LPAR accesses the SAN through hdisks presented through vSCSI, it is still reccomended to gather LPAR data in addition to the PowerVM hosts. In the GUI tool, you will need to populate each of the fields appropriate toRead More

Guest OS tunings for a VMware vSphere deployment

One of the important considerations for deploying NetApp storage to interoperate effectively with the VMware ESX/ESXi guest operating systems in a SAN/NFS environment is to utilize the NetApp recommended guest OS tunings in the virtual machines. This article describes the guest OS tunings utilized and the settings recommended by NetApp to help improve interoperability. The article also describes the purpose of updating guest OS tunings from the previous settings and provides guidance on adopting the updated guest OS tunings. Why are guest OS tunings required? The following are some reasons why guest OS tunings are required: To help improve error handling and interoperability during storage controller failover events. To improve recoveryRead More