Solved: DS14MK2 AT-FCx failed Disk

maxuptime · ‎2016-01-02

Hello,

in my testsystem with Data Ontap 7 one of my disks faild in DS14mk2 FC.

The sysconfig output shows me the failed disk is

X276_S10K7288F10

Now my question, it must be exactly this disk , or is there a matrix Which other disk that work for this configiruation???

slot 0: FC Host Adapter 0a (QLogic 2432 rev. 2, L-port, <UP>)
                Firmware rev:      4.5.2
                Host Loop Id:      7
                FC Node Name:      5:00a:098000:28756b
                SFP Vendor:        AVAGO
                SFP Part Number:   AFBR-57R6APZ-NA1
                SFP Serial Number: B91052AJB3
                SFP Capabilities:  1, 2 or 4 Gbit
                Link Data Rate:    2 Gbit
                 16  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR1B3V300007619BP0N)
                 17  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR1845Q00007618BGUG)
                 18  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR1B4RE00007618E2F5)
                 19  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR19A3X000076195SCS)
                 20  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR1AYFM00007619BMMY)
                 21  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR17ZT700007619TKTQ)
                 22  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR1ARVS00007619TLRA)
                 23  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR1AZ1Y00007619R3RJ)
                 24  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR19M0R00007619BL92)
                 25  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR18BBD000076197C80)
                 26  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR1AT6N000076195RWL)
                 27  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (Failed)
                 28  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR13YKT00007614NY91)
                 29  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLWZWR4C)
                 32  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR185KK000076199H3P)
                 33  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR1BRKX00007609F8HV)
                 34  : NETAPP   X276_S10K7288F10 NA07 272.0GB 520B/sect (3KR1BPPE00007620N3TW)
                 35  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLXAYJHC)
                 36  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLXB8DRC)
                 37  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLXAZPNC)
                 38  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLX9Z64C)
                 39  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLX9Z6XC)
                 40  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLXBG7HC)
                 41  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLXBNZAC)
                 42  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLXB9SJE)
                 43  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLXB9GHC)
                 44  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLXT797C)
                 45  : NETAPP   X279_HVPBP288F15 NA02 272.0GB 520B/sect (JLXBNP7C)
                Shelf 1: ESH4  Firmware rev. ESH A: 14  ESH B: 14
                Shelf 2: ESH4  Firmware rev. ESH A: 14  ESH B: 14
                        I/O base 0x0000ee00, size 0x100
                        memory mapped I/O base 0xd9200000, size 0x4000

thanks for help and the right infomation.

Greetings,

Stefan

niels · ‎2016-01-04

Hi Stefan,

the part number X276 refers to a 300GB 10k RPM FC disk.

This specific one is from Seagate, but any other NetApp-provided 300GB FC disk would work.

As you see from the sysconfig output you also have 300GB 15k RPM FC disks in the system, which have the part number X279.

Both X276 and X279 are valid replacements for your failed disk.

NetApp has a dual-source policy, meaning you might get replacement parts from different vendors. But as long as the NetApp part number matches, there is no issue.

regards, Niels

View solution in original post

niels · ‎2016-01-04

Hi Stefan,

the part number X276 refers to a 300GB 10k RPM FC disk.

This specific one is from Seagate, but any other NetApp-provided 300GB FC disk would work.

As you see from the sysconfig output you also have 300GB 15k RPM FC disks in the system, which have the part number X279.

Both X276 and X279 are valid replacements for your failed disk.

NetApp has a dual-source policy, meaning you might get replacement parts from different vendors. But as long as the NetApp part number matches, there is no issue.

regards, Niels

maxuptime · ‎2016-01-04

Hi Niels,

thanks a lot for your message, it hepls me. I don' t find this information in the netapp knowlegebase.

regards, Stefan

maxuptime · ‎2016-01-04

when i right understand, this is the matrix on the basis of one can search the hard disks?

http://mysupport.netapp.com/NOW/download/tools/diskfw/

niels · ‎2016-01-04

Hi Stefan,

that's just the list of available firmware for the different drives.

I think what you are looking for might better be found in the Hardware Universe (HWU):

http://hwu.netapp.com/Drives/Index

regards, Niels

maxuptime · ‎2016-01-04

Niels, perfect. Thank you very much. That is it.

Regards

Stefan

maxuptime · ‎2016-01-05

another question, i've found the raid has taken a disk from a different shelf . all disks are FC , replacing is a SAS disk . my question , I should remove it from the SAS raid so that they will again be replaced by a FC disk ? Or does it not matter?

nodea> sysconfig -r
Aggregate aggr0_fc (online, raid_dp) (block checksums)
  Plex /aggr0_fc/plex0 (online, normal, active)
    RAID group /aggr0_fc/plex0/rg0 (normal)

      RAID Disk Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      --------- ------          ------------- ---- ---- ---- ----- --------------    --------------
      dparity   0a.35           0a    2   3   FC:A   -  FCAL 15000 272000/557056000  274845/562884296
      parity    0a.17           0a    1   1   FC:A   -  FCAL 10000 272000/557056000  280104/573653840
      data      0c.00.10        0c    0   10  SA:A   -  SAS  15000 272000/557056000  274845/562884296
      data      0a.21           0a    1   5   FC:A   -  FCAL 10000 272000/557056000  280104/573653840
      data      0a.25           0a    1   9   FC:A   -  FCAL 10000 272000/557056000  280104/573653840
      data      0a.23           0a    1   7   FC:A   -  FCAL 10000 272000/557056000  280104/573653840
      data      0a.19           0a    1   3   FC:A   -  FCAL 10000 272000/557056000  280104/573653840
      data      0a.32           0a    2   0   FC:A   -  FCAL 10000 272000/557056000  280104/573653840
      data      0a.33           0a    2   1   FC:A   -  FCAL 10000 272000/557056000  280104/573653840
      data      0a.34           0a    2   2   FC:A   -  FCAL 10000 272000/557056000  280104/573653840
      data      0a.37           0a    2   5   FC:A   -  FCAL 15000 272000/557056000  274845/562884296
      data      0a.29           0a    1   13  FC:A   -  FCAL 15000 272000/557056000  274845/562884296
      data      0a.36           0a    2   4   FC:A   -  FCAL 15000 272000/557056000  274845/562884296

Aggregate aggr1_sas (online, raid_dp) (block checksums)
  Plex /aggr1_sas/plex0 (online, normal, active)
    RAID group /aggr1_sas/plex0/rg0 (normal)

      RAID Disk Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      --------- ------          ------------- ---- ---- ---- ----- --------------    --------------
      dparity   0c.00.0         0c    0   0   SA:A   -  SAS  15000 272000/557056000  274845/562884296
      parity    0c.00.1         0c    0   1   SA:A   -  SAS  15000 272000/557056000  274845/562884296
      data      0c.00.2         0c    0   2   SA:A   -  SAS  15000 272000/557056000  274845/562884296
      data      0c.00.3         0c    0   3   SA:A   -  SAS  15000 272000/557056000  274845/562884296
      data      0c.00.4         0c    0   4   SA:A   -  SAS  15000 272000/557056000  274845/562884296
      data      0c.00.5         0c    0   5   SA:A   -  SAS  15000 272000/557056000  274845/562884296
      data      0c.00.6         0c    0   6   SA:A   -  SAS  15000 272000/557056000  274845/562884296
      data      0c.00.7         0c    0   7   SA:A   -  SAS  15000 272000/557056000  274845/562884296
      data      0c.00.8         0c    0   8   SA:A   -  SAS  15000 272000/557056000  274845/562884296
      data      0c.00.9         0c    0   9   SA:A   -  SAS  15000 272000/557056000  274845/562884296


Spare disks

RAID Disk       Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------       ------          ------------- ---- ---- ---- ----- --------------    --------------
Spare disks for block or zoned checksum traditional volumes or aggregates
spare           0a.27           0a    1   11  FC:A   -  FCAL 10000 272000/557056000  280104/573653840 (zeroing, 11% done)
spare           0a.38           0a    2   6   FC:A   -  FCAL 15000 272000/557056000  274845/562884296
spare           0a.39           0a    2   7   FC:A   -  FCAL 15000 272000/557056000  274845/562884296
spare           0c.00.11        0c    0   11  SA:A   -  SAS  15000 272000/557056000  274845/562884296

regards,

Stefan

niels · ‎2016-01-05

Please have a look here for details:

http://www.netapp.com/us/media/tr-3548.pdf

Page 38

Excerpt:

######

NetApp recommends NOT mixing "old and new" compatible drive technologies. In the context of fabric MetroCluster, this implies that:
- NetApp does not recommend creating an aggregate with a mix of DS14MK4 FC disks and SAS disks, but it is supported.
- NetApp does not recommend expanding existing DS14MK4 FC aggregates with SAS disks, but it is supported.
- NetApp does not recommend creating SyncMirror relationships between DS14MK4 FC disks and SAS disks, but it is supported.

######

As you are dealing with a test system here I wouldn't see an issue.

If you want the aggregate to be comprised of FC disks only, just use the following command:

disk replace start 0c.00.10 0a.27

If you want to prevent from SAS disks to replace broken FC disks check the following option:

options raid.mix.hdd.disktype.capacity on

on = allow FC and SAS to replace each other

off= keep aggregate homogeneous

Kind regards, Niels

maxuptime · ‎2016-01-05

Hi Niels,

thank you for the information, thats help me. I am changing the disks.

The options

options raid.mix.hdd.disktype.capacity on

is in Ontap 7 not available.

Regards

Stefan

niels · ‎2016-01-05

Well - I verified that command on a 7-mode MetroCLuster, but it may be running a different version than yours.

Just try the command "options raid" and look for a similar looking option. It should definitely be there.

Kind regards, Niels

maxuptime · ‎2016-01-05

Hi Niels,

nodea> options raid
raid.background_disk_fw_update.enable on         (value might be overwritten in takeover)
raid.disk.background_fw_update.raid4.enable on         (value might be overwritten in takeover)
raid.disk.copy.auto.enable   on         (value might be overwritten in takeover)
raid.disktype.enable         off        (value might be overwritten in takeover)
raid.media_scrub.enable      on         (value might be overwritten in takeover)
raid.media_scrub.rate        600        (value might be overwritten in takeover)
raid.media_scrub.spares.enable on         (value might be overwritten in takeover)
raid.min_spare_count         1          (value might be overwritten in takeover)
raid.mirror_read_plex_pref   local      (value might be overwritten in takeover)
raid.reconstruct.perf_impact medium     (value might be overwritten in takeover)
raid.reconstruct.wafliron.enable on         (value might be overwritten in takeover)
raid.resync.perf_impact      medium     (value might be overwritten in takeover)
raid.rpm.ata.enable          off        (value might be overwritten in takeover)
raid.rpm.fcal.enable         on         (value might be overwritten in takeover)
raid.scrub.duration          360
raid.scrub.enable            on
raid.scrub.perf_impact       low        (value might be overwritten in takeover)
raid.scrub.schedule
raid.timeout                 24         (value might be overwritten in takeover)
raid.verify.perf_impact      low        (value might be overwritten in takeover)

i think the option raid.disktype.enable set to on.

Regards

Stefan

niels · ‎2016-01-05

Yes - that's the respective option.

Details on how these options work on both ONTAP 8.1 and 8.2 is described here:https://kb.netapp.com/support/index?page=content&id=3013616&locale=en_USRegards, Niels

maxuptime · ‎2016-01-05

Niels, thank you for your great support.

Regards

Stefan