Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

Data ONTAP 8: How does disk ownership of NetApp Shared Storage work and what are the requirements?

Views:
1,314
Visibility:
Public
Votes:
1
Category:
data-ontap-8
Specialty:
core
Last Updated:

Applies to

  • Clustered Data ONTAP 8
  • Data ONTAP 8 7-Mode

Answer

Disk ownership of NetApp Shared Storage

Assign or show disk ownership of a NetApp Shared Storage

Disks need to be assigned after being replaced

What are the requirements for enabling sanown / software disk-based ownership?

NetApp Shared Storage follows the software-based ownership model. The basics of the ownership model are:

  • Disks are explicitly assigned to a storage system
  • Ownership information is written to the disk
  • Once assigned, storage systems use reservations to keep other storage systems from touching the disk
  • Some disks may stay unowned. Unowned disks will not have new firmware downloaded
  • Disks must be assigned to be used as a spare

The requirements for enabling software ownership (sanown) are:

  • A Data ONTAP version that supports sanown
  • CompactFlash boot based filer
  • DS14, DS14mk2 shelf

To assign disk ownership of a NetApp Shared Storage:

  • Data ONTAP 8 7-Mode:  

disk assign <diskname> [-f] [-p  ] [- o <ownername>] [-s <sysid>]

    1. Normal usage is to assign ownership of unowned disks to local storage system:

disk assign 0b.16
disk assign 0b.17 -p 1

    1. To assign disk owned by local storage system back to unowned:

disk assign 0b.16 -s unowned -f

    1. To assign ownership to another storage system:

disk assign 0b.16 -o otherguy -f

Should use higher-level functionality (vFiler migrate) to do this, unless disk is a spare

    1. If receiving storage system is unable to communicate with the donor storage system, there will be warnings about rescan messages.
       
  • Data ONTAP 8 Cluster-Mode: 
    'disk reassign' is an advanced command.

::> set adv
::*> disk reassign ?
  (storage disk reassign)
  [[-home] <text>]            Current Home Name
  [ -newhome <nodename> ]     New Home Name
  [ -homeid <nvramid> ]       Current Home ID
  [ -newhomeid <nvramid> ]    New Home ID
  [ -force [{true|false}] ]   Force

To display the disk ownership of a NetApp Shared Storage:

  • Data ONTAP 8 7-Mode:  

disk show [-o <hostname> | -s <sysid> | -n | -v | -a ]

Display information for disks:

  • with matching owner name
  • with matching system id
  • not owned by any system
  • verbose listing of all disks
  • owned by any storage system

For example, seeing every disk's ownership:

cfo-u37> disk show -v

DISK         OWNER                  POOL   SERIAL NUMBER  
------------ -------------          -----  -------------  
9b.19        cfo-u37   (50408384)   Pool0  3HZ6RA1B00007426SWC9
8b.107       cfo-u39   (50408359)   Pool0  3HZ6SF3L000074289QWS
2b.49        cfo-u38   (50408371)   Pool0  3HZ6SD55000074289R4R
3a.22        cfo-u37   (50408384)   Pool0  3HZ6YDGM000074310Z3A
9b.68        cfo-u39   (50408359)   Pool0  3HZ6SEGL00007428B70G
8a.20        cfo-u39   (50408359)   Pool0  3HZ6P9PG0000740529DS
3b.99        cfo-u36   (50408412)   Pool0  414R6372           
3b.108       cfo-u36   (50408412)   Pool0  414W6158           
3b.98        cfo-u36   (50408412)   Pool0  414W5818           
3b.49        cfo-u36   (50408412)   Pool0  413M5089      

  • Data ONTAP 8 Cluster-Mode: 

::> disk show

Available options are :

  (storage disk show)
  [ -classic | -instance | -longop | -physical | -port | -raid | -sanown |
    -v | -fields <fieldname>, ... ]
  [[-disk] <disk path name>]                   Disk
  [ -physicalsize <integer> ]                  Physical Size (MB)
  [ -usedsize <integer> ]                      Used Size (MB)
  [ -type <disk type> ]                        Type
  [ -vendor <text>]                            Vendor
  [ -serialnumber <text> ]                     Serial Number
  [ -model <text> ]                            Model
  [ -revision <text> ]                         Firmware Revision
  [ -rpm <integer> ]                           RPM
  [ -bps <integer> ]                           Bytes Per Sector
  [ -checksum <text> ]                         Checksum Compatibility
  [ -shelf <integer> ]                         Shelf
  [ -bay <integer> ]                           Bay
  [ -state <disk state> ]                      State
  [ -detailstate <text>]                       Detail State
  [ -raidtype {pending|parity|dparity|data} ]  Raid Type
  [ -raidgroup <text> ]                        Raid Group
  [ -plex <text> ]                             Plex
  [ -aggregate <aggregate name> ]              Aggregate
  [ -home <nodename> ]                         Home         

Additional Information

N/A

 

Scan to view the article on your device