System (ID 135058219) using the 'disk show' and 'disk assign'
WARNING: there do not appear to be any disks attached to the system.Ĭheck that disks have been assigned ownership to this Portions Copyright (C) 2002-2006 Network Appliance Inc.ĬPU Type: Mobile Intel(R) Celeron(R) CPU 2.20GHz All Rights ReservedĬopyright (C) 2000,2001,2002,2003 Broadcom Corporation. Portions Copyright (C) 2006 Network Appliance, Inc. I hookup up the serial connection, and saw the following:Ĭopyright (C) 1985-2006, American Megatrends, Inc. I began by examining the output of the boot process.
HOW TO NETBOOT NETAPP FILER HOW TO
Hence, I had myself a very expensive piece of useless storage.īecause my experience with NetApp filers has been relatively minimal up until this point, I needed to dive into it deeply to figure out how the root volume works, why NetApp has placed it onto the ‘data’ disks (and not onto the CompactFlash storage), and most important, how to fix this mess. Without the SAS-disks in place, which hold aggr0 and the root volume (vol0), there wasn’t much to boot from. They were added to a second FAS2020 (FLR1), which is running all the production VM’s and thus has more benefit from the 300GB 10K SAS disks than FLR2, which was going to do only SnapMirror replication from FLR1 over a 20 Mbit internet connection. After hooking up the fibre channel interconnect to a second diskshelf (containing SATA-disks), I noticed that all disks from the onboard shelf were missing. For sake of argument, let’s call this filer FLR2. I went to a customer today to configure a NetApp FAS2020 for SnapMirror replication.
0 kommentar(er)
