Arsip

Arsip untuk Kategori 'Halaman Manual'

NetApp Man Halaman

7 Juli 2009

NetApp telah menyempatkan memberi saya izin untuk menerbitkan halaman manual mereka di sini. Mereka masih perlu sedikit merapikan, tapi kuantitas semata-mata berarti akan membawa saya beberapa saat untuk mendapatkan mereka semua diurutkan dan lintas-referensi benar, mohon maaf masalah visual untuk saat ini. Aku menulis sebuah alat parsing cepat untuk mendapatkan semua info di sini, jadi mungkin ada beberapa masalah akibat yang masih.

Aku selalu menyukai cara bahwa PHP memiliki halaman fungsi mereka memberikan pengguna kemampuan untuk berkomentar secara langsung ke mereka. Hal ini memungkinkan orang untuk meninggalkan umpan balik pada fungsi dan alat, dan juga menindaklanjuti dengan beberapa penggunaan tambahan atau sintaks untuk perintah yang tidak selalu jelas dipublikasikan. Semoga ini bisa memberi makan kembali ke dalam NetApp untuk meningkatkan dokumentasi mereka.

Saya pasti ingin mendorong orang untuk mengomentari halaman manual dengan apa pun yang mungkin berguna, dan semoga membangun ini ke dalam bagian referensi yang berguna sedikit. Banyak terima kasih lagi untuk rakyat NetApp untuk membantu saya dengan ini.

VN: F [1.9.11_1134]
Menilai posting ini:
Penilaian: 8.8 / 10 (19 votes cast)

Umum , Halaman manual , , , ,

aggr

7 Juli 2009

Daftar isi

NAMA

aggr - perintah untuk mengelola agregat, menampilkan status agregat, agregat dan menyalin

SINOPSIS

aggr perintah argumen ...

URAIAN

Keluarga perintah aggr mengelola agregat. Perintah aggr dapat membuat agregat baru, menghancurkan yang sudah ada, undestroy sebelumnya hancur agregat, mengelola plexes dalam agregat cermin, mengubah status agregat, menerapkan pilihan untuk agregat, agregat salinan satu ke yang lain, dan menampilkan status mereka. Perintah Agregat sering mempengaruhi volume (s) yang terkandung dalam agregat.

Keluarga perintah aggr yang baru dalam Data ONTAP 7.0. Keluarga perintah vol diberikan kontrol atas u vol_ tradisional mes yang menyatu sistem pengguna-terlihat file tunggal dan wadah tunggal RAID tingkat penyimpanan (agregat) ke unit terpisahkan, dan masih tidak. Untuk memungkinkan penggunaan lebih fleksibel penyimpanan, agregat kini juga mendukung kemampuan untuk mengandung beberapa, file sistem independen level user bernama volume fleksibel.

Data ONTAP 7,0 sepenuhnya mendukung volume tradisional dan fleksibel. Keluarga perintah aggr adalah metode yang disukai untuk mengelola agregat sebuah filer, termasuk mereka yang tertanam dalam volume tradisional.

Perhatikan bahwa sebagian besar perintah aggr berlaku untuk kedua jenis agregat yang berisi volume fleksibel dan jenis yang terikat erat untuk membentuk volume tradisional. Dengan demikian, agregat Istilah ini sering digunakan di sini untuk mengacu pada kedua kelas penyimpanan. Dalam kasus tersebut, ia menyediakan singkatan untuk "agregat dan volume tradisional" kalimat panjang dan lebih berat.

Agregat dapat berupa cermin atau tidak di mirror. Kompleks adalah salinan fisik dari penyimpanan WAFL dalam agregat. Sebuah cermin agregat terdiri dari dua plexes; tidak di mirror agregat mengandung kompleks tunggal. Untuk membuat agregat cermin, Anda harus memiliki konfigurasi filer yang mendukung RAID tingkat mirroring. Ketika mirroring diaktifkan pada filer tersebut, disk cadangan dibagi menjadi dua kolam disk. Ketika suatu agregat dibuat, semua disk dalam kompleks tunggal harus datang dari kolam disk yang sama, dan dua plexes dari agregat cermin harus terdiri dari disk dari kolam terpisah, karena hal ini memaksimalkan isolasi kesalahan. Kebijakan ini dapat diganti dengan f-pilihan untuk menciptakan aggr, aggr menambah dan cermin aggr, tetapi tidak dianjurkan.

Sebuah nama agregat dapat berisi huruf, angka, dan karakter garis bawah (_), tetapi karakter pertama harus huruf atau underscore. Sebanyak dikombinasikan hingga 200 agregat (termasuk yang tertanam dalam volume tradisional) dapat dibuat pada filer masing-masing.

Kompleks mungkin menjadi online atau offline. Jika sedang offline, tidak tersedia untuk membaca atau menulis akses. Plexes bisa dalam kombinasi dari status berikut:

kelompok RAID yang normal Semua dalam kompleks adalah fungsional.

gagal Setidaknya salah satu kelompok RAID di kompleks telah gagal.

kosong kompleks ini merupakan bagian dari agregat yang sedang dibuat, dan satu atau lebih disk ditargetkan untuk agregat harus memusatkan perhatian sebelum ditambahkan ke kompleks tersebut.

aktif kompleks ini tersedia untuk digunakan.

tidak aktif
Kompleks ini tidak tersedia untuk digunakan.

resyncing
Isi kompleks itu saat ini ketinggalan zaman dan sedang dalam proses untuk disinkronisasi dengan isi dari kompleks lain dari agregat (berlaku untuk agregat cermin saja).

menambahkan disk
Disk selalu ditambahkan ke kompleks itu RAID kelompok (s).

tdk terpakai lagi
Kondisi ini hanya terjadi pada agregat cermin di mana salah satu plexes telah gagal. Para kompleks non-gagal akan berada dalam keadaan ini jika perlu disinkronisasi pada saat rumit lainnya gagal.

Sebuah kompleks yang diberi nama menggunakan nama agregat, pembatas karakter garis miring, dan nama kompleks tersebut. Sistem secara otomatis akan memilih nama kompleks pada saat penciptaan. Misalnya, kompleks pertama dibuat dalam aggr0 agregat akan aggr0/plex0.

Agregat terbang dapat online, dibatasi, atau offline. Ketika suatu agregat is offline, tidak membaca atau menulis akses yang diperbolehkan. Ketika suatu agregat adalah terbatas, operasi tertentu diperbolehkan (seperti copy agregat, recomputation paritas RAID atau rekonstruksi) tetapi akses data tidak diperbolehkan. Agregat yang bukan merupakan bagian dari volume tradisional hanya dapat dibatasi atau offlined jika mereka tidak mengandung volume fleksibel.

Agregat dapat di kombinasi dari status berikut:

agregat aggr adalah agregat modern; ia mampu mengandung nol atau lebih volume fleksibel.

penyalinan
Agregat saat ini agregat target operasi copy aggr aktif.

terdegradasi
Agregat berisi setidaknya satu kelompok RAID terdegradasi yang tidak sedang diperbaiki.

asing
Disk yang mengandung agregat dipindahkan ke filer arus dari filer lain.

pertumbuhan
Disk adalah dalam proses yang ditambahkan ke agregat.

menginisialisasi
Agregat adalah dalam proses diinisialisasi.

cacat
Agregat tidak berisi volume dan tidak dapat ditambahkan. Biasanya ini terjadi hanya setelah operasi copy dibatalkan agregat.

setrika
Sebuah cek konsistensi WAFL sedang dilakukan pada agregat ini.

terdegradasi cermin
Agregat adalah agregat cermin, dan salah satu plexes adalah offline atau resyncing.

cermin
Agregat adalah cermin dan semua kelompok RAID nya yang fungsional.

kebutuhan memeriksa
Sebuah cek konsistensi WAFL perlu dilakukan pada agregat.

sebagian
Setidaknya satu disk ditemukan untuk agregat, tetapi dua atau lebih disk yang hilang.

raid0 agregat terdiri dari RAID-0 (no parity) kelompok RAID (V-Series dan NetCache saja).

raid4 agregat terdiri dari RAID-4 kelompok RAID.

raid_dp
Agregat terdiri dari RAID-DP (Paritas Double) kelompok RAID.

merekonstruksi
Setidaknya satu kelompok RAID secara agregat sedang direkonstruksi.

redirect
Realokasi agregat atau realokasi file dengan opsi-p sudah dimulai pada agregat. Baca kinerja untuk volume dalam agregat mungkin terdegradasi.

resyncing
Salah satu plexes dari agregat cermin sedang disinkronisasi.

snapmirrored
Agregat adalah replika snapmirrored agregat lain. Kondisi ini hanya dapat timbul jika agregat adalah bagian dari volume tradisional.

trad agregat ini menyatu dengan volume tunggal. Ini juga disebut sebagai volume tradisional dan akan persis sama dengan volume yang ada sebelum Data ONTAP 7.0. Volume fleksibel tidak dapat diciptakan dalam agregat ini.

memverifikasi
Sebuah cermin RAID operasi verifikasi saat ini sedang berjalan di agregat.

WAFL tidak konsisten
Agregat telah ditandai rusak. Silahkan hubungi Customer Support jika Anda melihat agregat di negara ini.

PENGGUNAAN

Perintah berikut tersedia dalam suite aggr:

   menambahkan cermin membatasi undestroy menyalin scrub online memverifikasi membuat show_space secara online menghancurkan pilihan membagi media_scrub statusnya ganti nama 

aggr add aggrname
[-F]
[-N]
[-G {raidgroup | baru | all}]
{Ndisks [@ size]
|
-D disk1 [disk2 ... ] [-D diskn [diskn +1 ... ]]}

Menambahkan disk ke aggrname bernama agregat. Tentukan disk dengan cara yang sama seperti untuk perintah create aggr. Jika agregat adalah cermin, maka argumen-d harus digunakan dua kali (jika sama sekali).

Jika opsi-g tidak digunakan, disk ditambahkan ke kelompok RAID yang terakhir dibuat util penuh, dan kemudian satu atau lebih kelompok RAID baru diciptakan dan disk yang tersisa ditambahkan ke kelompok baru. Setiap kelompok RAID lainnya yang sudah ada yang tidak penuh tetap terisi sebagian.

-G pilihan memungkinkan spesifikasi kelompok RAID (misalnya, rg0) yang disk yang ditunjukkan harus ditambahkan, atau metode dimana disk ditambahkan ke kelompok RAID baru atau yang sudah ada.

Jika opsi-g digunakan untuk menentukan grup RAID, bahwa kelompok RAID harus sudah ada. Disk ditambahkan dengan util kelompok RAID penuh. Setiap disk yang tersisa akan diabaikan.

Jika opsi-g diikuti oleh baru, Data ONTAP menciptakan satu atau lebih kelompok RAID baru dan menambahkan disk untuk mereka, bahkan jika disk akan masuk ke dalam kelompok RAID yang ada. Setiap kelompok RAID yang sudah ada yang tidak penuh tetap terisi sebagian. Nama dari kelompok RAID baru dipilih secara otomatis. Hal ini tidak mungkin untuk menentukan nama untuk kelompok RAID baru.

Jika opsi-g diikuti oleh semua, Data ONTAP menambahkan disk tertentu untuk kelompok RAID yang ada pertama. Setelah semua kelompok RAID yang ada penuh, menciptakan satu atau lebih kelompok RAID baru dan menambahkan disk tertentu ke kelompok baru.

Opsi-n dapat digunakan untuk menampilkan perintah bahwa sistem akan mengeksekusi, tanpa benar-benar membuat perubahan. Hal ini berguna untuk menampilkan disk secara otomatis dipilih, misalnya.

Secara default, filer terisi satu kelompok RAID dengan disk sebelum memulai kelompok RAID. Misalkan suatu agregat saat ini memiliki satu kelompok RAID 12 dan RAID disk ukuran kelompok adalah 14. Jika Anda menambahkan 5 disk untuk agregat ini, akan memiliki satu kelompok RAID dengan 14 disk dan kelompok lain dengan 3 RAID disk. Filer tidak merata mendistribusikan disk antara kelompok RAID.

Anda tidak dapat menambahkan disk untuk agregat cermin jika salah satu plexes sedang offline.

Disk di sebuah kompleks tidak diizinkan untuk rentang kolam disk. Perilaku ini dapat diganti dengan f-bendera bila digunakan bersama dengan-d argumen ke daftar disk untuk menambahkan. F-bendera, dalam kombinasi dengan-d, juga dapat digunakan untuk memaksa menambahkan disk yang memiliki kecepatan rotasi yang tidak cocok dengan mayoritas disk yang ada secara agregat.

aggr salinan membatalkan [-h] operation_number | semua

Menghentikan operasi copy agregat. Para opera_ t parameter yang menentukan ion_number operasi untuk mengakhiri. Jika Anda menentukan semua, semua operasi copy agregat aktif dihentikan.

aggr salinan awal
[-S |-s snapshot] [-C]
sumber tujuan

Salinan semua data, termasuk foto dan volume fleksibel, dari satu agregat yang lain. Jika S-bendera yang digunakan, perintah copy semua foto dalam sumber agregat agregat tujuan. Untuk menentukan snapshot tertentu untuk menyalin, menggunakan-bendera diikuti dengan nama snapshot. Jika Anda menggunakan baik-S atau-bendera di perintah, filer menciptakan snapshot pada saat copy aggr perintah mulai dieksekusi dan salinan hanya itu snapshot untuk agregat tujuan.

The-C bendera diperlukan jika sumber agregat telah memiliki ruang bebas defragmentasi dilakukan di atasnya, atau jika agregat tujuan akan bebas-ruang defragmented. Ruang bebas defragmentasi dapat dilakukan pada agregat dengan menggunakan perintah realokasi.

Salinan Agregat hanya dapat dilakukan antara agregat yang host volume fleksibel. Agregat yang tertanam dalam volume tradisional tidak dapat berpartisipasi.

Agregat sumber dan tujuan dapat berada di filer sama atau pelapor yang berbeda. Jika sumber atau tujuan agregat adalah pada filer selain yang di mana Anda memasukkan perintah aggr salinan awal, tentukan nama agregat dalam filer_name ini: aggre_ g Format ate_name.

Para pelapor yang terlibat dalam salinan agregat harus memenuhi persyaratan berikut untuk perintah copy awal aggr akan selesai dengan sukses:

Agregat sumber harus online dan agregat tujuan harus dibatasi.

Jika salinan tersebut antara dua pelapor, filer masing-masing harus didefinisikan sebagai host yang terpercaya dari filer lainnya. Artinya, nama filer itu harus dalam / etc / hosts.equiv file dari filer lainnya.

Jika salinan tersebut pada filer sama, localhost harus dimasukkan dalam / etc filer s / hosts.equiv file. Juga, alamat loopback harus di / etc file filer ini / hosts. Jika tidak, filer tidak dapat mengirim paket ke sendiri melalui alamat loopback ketika mencoba untuk menyalin data.

Ruang disk yang dapat digunakan agregat tujuan harus lebih besar dari atau sama dengan ruang disk yang dapat digunakan agregat sumber. Gunakan df-Perintah pathname untuk melihat jumlah ruang disk yang dapat digunakan agregat tertentu.

Setiap salinan aggr perintah mulai menghasilkan dua operasi copy agregat: satu untuk membaca data dari agregat sumber dan satu untuk menulis data ke agregat tujuan. Setiap filer mendukung hingga empat operasi copy simultan agregat.

aggr salinan Status [operation_number]

Menampilkan kemajuan satu atau semua operasi copy aggr. Operasi diberi nomor dari 0 sampai 3.

Restart informasi centang untuk semua transfer juga ditampilkan.

aggr salinan throttle [operation_number] nilai

Mengontrol kinerja operasi copy aggr. Nilainya berkisar dari 10 (kecepatan penuh) untuk 1 (satu sepersepuluh dari kecepatan penuh). Nilai default dijaga dalam pilihan aggr.copy.throttle yang Filer dan ditetapkan 10 (full speed) di pabrik. Anda dapat menerapkan nilai kinerja terhadap operasi ditentukan oleh parameter operation_number. Jika Anda tidak menentukan jumlah operasi dalam perintah throttle salinan aggr, perintah berlaku untuk semua operasi copy aggr.

Gunakan perintah ini untuk membatasi kecepatan operasi copy aggr jika Anda menduga bahwa operasi copy aggr menyebabkan masalah kinerja pada filer Anda. Secara khusus, throttle dirancang untuk membantu membatasi penggunaan CPU dari operasi copy aggr. Hal ini tidak dapat digunakan untuk menyempurnakan pola konsumsi bandwidth jaringan.

Salinan aggr perintah throttle hanya memungkinkan Anda untuk mengatur kecepatan sebuah operasi copy aggr yang sedang berlangsung. Untuk mengatur aggr standar kecepatan salinan untuk digunakan oleh operasi penyalinan berikutnya, gunakan perintah pilihan untuk mengatur pilihan aggr.copy.throttle.

aggr menciptakan aggrname
[-F]
[-M]
[-N]
[-T raidtype]
[-R raidsize]
[-T disk type]
[-R rpm]
[-L [kepatuhan | perusahaan]]
[-V]
[-L-bahasa kode]
{Ndisks [@ size]

|
-D disk1 [disk2 ... ] [-D diskn [diskn +1 ... ]]}

Membuat aggrname bernama baru agregat. Nama agregat dapat berisi huruf, angka, dan karakter garis bawah (_), tetapi karakter pertama harus huruf atau underscore. Hingga 200 agregat dapat dibuat pada filer masing-masing. Jumlah ini termasuk mereka agregat yang tertanam dalam volume tradisional.

Agregat tertanam dapat dibuat sebagai bagian dari volume tradisional menggunakan-v pilihan. Tidak dapat berisi volume fleksibel.

Sebuah agregat biasa, yang diciptakan tanpa v-pilihan, hanya dapat berisi volume fleksibel. Ini tidak dapat dimasukkan ke dalam volume tradisional, dan tidak mengandung volume segera setelah penciptaan. Volume fleksibel baru dapat dibuat menggunakan perintah create vol.

-T argumen raidtype menentukan jenis RAID kelompok (s) yang akan digunakan untuk membuat agregat. Jenis RAID mungkin kelompok yang raid4 untuk RAID-4, raid_dp untuk RAID-DP (Paritas Double), dan raid0 untuk striping sederhana tanpa perlindungan paritas. Para raidtype default untuk agregat dan volume tradisional pada pelapor adalah raid_dp. Mengatur raidtype tidak diizinkan pada V-Series sistem; default raid0 selalu digunakan.

-R argumen raidsize menentukan jumlah maksimum disk di setiap kelompok RAID secara agregat. Nilai maksimum dan default raidsize adalah tergantung platform, berdasarkan pertimbangan kinerja dan kehandalan. Lihat pilihan aggr raidsize untuk lebih jelasnya.

T-disk-tipe argumen menentukan jenis disk untuk digunakan saat membuat agregat baru. Hal ini diperlukan hanya pada sistem terhubung ke disk dari berbagai jenis. Jenis disk yang mungkin adalah: ATA, FCAL, Lun, SAS, SATA, dan SCSI. Disk pencampuran dari berbagai jenis dalam satu agregat tidak diperbolehkan-T. Tidak dapat digunakan bersama-sama dengan-d.

Tipe Disk mengidentifikasi teknologi disk dan jenis konektivitas ATA mengidentifikasi disk ATA dengan baik IDE atau antarmuka serial ATA di rak terhubung dalam FCAL (Fibre Channel penengah loop). FCAL mengidentifikasi disk FC di rak terhubung dalam FC-AL. Lun mengidentifikasi disk virtual diekspor dari. penyimpanan eksternal array. Teknologi disk yang mendasari dan RAID jenis tergantung pada pelaksanaan seperti array penyimpanan eksternal SAS mengidentifikasi Serial Attached SCSI disk di rak yang cocok.. SATA mengidentifikasi disk serial ATA di rak SAS. SCSI singkatan Interface Sistem Komputer Kecil, dan itu sudah termasuk untuk kompatibilitas dengan teknologi disk sebelumnya.

-R argumen rpm menentukan jenis disk digunakan menurut kecepatan rotasi dalam revolusi per menit (rpm). Hal ini diperlukan hanya pada sistem yang memiliki disk dengan kecepatan rotasi yang berbeda. Nilai-nilai khas untuk kecepatan rotasi adalah 5400, 7200, 10000, dan 15000.-R tidak dapat digunakan bersama-sama dengan-d.

ndisks adalah jumlah disk secara agregat, termasuk disk paritas. Disk dalam agregat yang baru dibuat berasal dari kolam disk cadang. Disk terkecil di kolam ini bergabung dengan agregat pertama, kecuali jika Anda menentukan ukuran argumen @. Ukuran adalah ukuran disk dalam GB, dan disk yang berada dalam 10% dari ukuran tertentu akan dipilih untuk digunakan dalam agregat.

M-pilihan dapat digunakan untuk menentukan bahwa agregat baru dicerminkan (memiliki dua plexes) atas penciptaan. Jika opsi ini diberikan, maka disk yang ditunjukkan akan dibagi di dua plexes. Secara default, agregat baru tidak akan dicerminkan.

Opsi-n dapat digunakan untuk menampilkan perintah bahwa sistem akan mengeksekusi, tanpa benar-benar membuat perubahan. Hal ini berguna untuk menampilkan disk secara otomatis dipilih, misalnya.

Jika Anda menggunakan-d disk1 [disk2 ... ] Argumen, filer menciptakan agregat dengan disk cadang, yang ditentukan disk1 disk2, dan sebagainya. Anda dapat menentukan daftar dipisahkan dengan spasi dari nama disk. Dua daftar terpisah harus ditentukan jika agregat baru dicerminkan. Dalam hal agregat baru adalah cermin, disk yang ditunjukkan harus menghasilkan jumlah yang sama dari disk pada setiap kompleks baru.

Disk di sebuah kompleks tidak diizinkan untuk rentang kolam cadang. Perilaku ini dapat diganti dengan opsi-f. Pilihan yang sama juga dapat digunakan untuk memaksa menggunakan disk yang tidak ada pencocokan kecepatan rotasi. Opsi-f berpengaruh hanya bila digunakan dengan-d menentukan pilihan disk untuk digunakan.

Untuk membuat agregat SnapLock, tentukan L-bendera dengan aggr yang membuat perintah. Flag ini hanya didukung jika salah SnapLock Kepatuhan atau Enterprise SnapLock berlisensi. Jenis agregat SnapLock dibuat, baik Kepatuhan atau Enterprise, ditentukan oleh lisensi SnapLock diinstal. Jika kedua Kepatuhan SnapLock dan Enterprise SnapLock dilisensikan, gunakan-L atau-L kepatuhan perusahaan untuk menentukan jenis agregat yang diinginkan.

-L argumen language_code hanya dapat digunakan saat membuat volume tradisional menggunakan opsi-v. Filer menciptakan volume tradisional dengan bahasa yang ditentukan oleh kode bahasa. Default adalah bahasa yang digunakan oleh volume akar filer ini. Lihat vol halaman manual untuk daftar kode bahasa.

aggr menghancurkan {aggrname | plexname} [-f]

Menghancurkan aggrname bernama agregat, atau plexname bernama kompleks. Perhatikan bahwa jika agregat yang ditentukan terkait dengan volume tradisional, maka volume tradisional itu sendiri hancur juga.

Jika suatu agregat yang ditentukan, semua plexes secara agregat hancur. Agregat bernama juga harus tidak mengandung volume fleksibel, terlepas dari keadaan mount (online, terbatas, atau offline). Jika kompleks tersebut ditentukan, kompleks ini hancur, meninggalkan volume tidak di mirror agregat atau tradisional yang mengandung kompleks yang tersisa. Sebelum menghancurkan volume, agregat tradisional atau kompleks, pengguna diminta untuk mengkonfirmasi operasi. F-bendera dapat digunakan untuk menghancurkan volume, agregat tradisional atau kompleks tanpa disuruh pengguna.

Disk awalnya di objek dihancurkan menjadi disk cadang. Hanya agregat offline, volume tradisional dan plexes dapat dihancurkan.

aggr media_scrub Status [aggrname | plexname | groupname]
[-V]

Mencetak status Media scrubbing dari agregat bernama, kompleks, atau kelompok. Jika nama tidak diberikan, maka statusnya dicetak untuk semua kelompok RAID sedang berjalan scrub media. Status ini mencakup persen-lengkap dan apakah itu ditangguhkan.

-V bendera menampilkan tanggal dan waktu di mana media penuh terakhir Scrub selesai, tanggal dan waktu di mana contoh saat media menggosok dimulai, dan status saat ini agregat bernama, kompleks, atau kelompok. Jika nama tidak diberikan, status ini lebih verbose dicetak untuk semua kelompok RAID dengan scrub media yang aktif.

aggr cermin aggrname
[-F]
[-N]
[-V victim_aggrname]
[-D disk1 [disk2 ... ]]

Ternyata agregat tidak di mirror ke dalam agregat cermin dengan menambahkan kompleks untuk itu. Kompleks ini baik yang baru terbentuk dari disk yang dipilih dari kolam cadang, atau, jika opsi-v yang ditentukan, diambil dari yang lain agregat tidak di mirror yang ada. Aggrname Agregat saat ini harus tidak di mirror. Gunakan aggr membuat membuat baru, mencerminkan agregat dari awal.

Disk dapat ditentukan secara eksplisit menggunakan-d dengan cara yang sama seperti dengan menciptakan aggr dan perintah aggr menambahkan. Jumlah disk yang ditunjukkan harus cocok dengan jumlah hadir pada agregat yang ada. Disk yang ditentukan tidak diizinkan untuk rentang kolam disk. Perilaku ini dapat diganti dengan opsi-f. Opsi-f, dalam kombinasi dengan-d, juga dapat digunakan untuk memaksa menggunakan disk yang memiliki kecepatan rotasi yang tidak cocok dengan mayoritas disk yang ada secara agregat.

Jika disk tidak ditentukan secara eksplisit, maka disk secara otomatis dipilih untuk mencocokkan mereka yang kompleks yang ada kelompok agregasi.

The -v option can be used to join victim_aggrname back into aggrname to form a mirrored aggregate. The result is a mirrored aggregate named aggrname which is otherwise identical to aggrname before the operation. Victim_aggrname is effectively destroyed. Victim_aggrname must have been previously mirrored with aggrname , then separated via the aggr split command. Victim_aggrname must be offline. Combined with the -v option, the -f option can be used to join aggrname and vic_ t im_aggrname without prompting the user.

The -n option can be used to display the command that the system will execute without actually making any changes. This is useful for displaying the automatically selected disks, for example.

aggr offline { aggrname | plexname }
[ -t cifsdelaytime ]

Takes the aggregate named aggrname (or the plex named plexname ) offline. The command takes effect before returning. If the aggregate is already in restricted state, then it is already unavailable for data access, and much of the following description does not apply.

If the aggregate contains any flexible volumes, then the operation is aborted unless the filer is in maintenance mode.

Except in maintenance mode, the aggregate containing the current root volume may not be taken offline. An aggregate containing a volume that has been marked to become root (using vol options vol_ n ame root ) also cannot be taken offline.

If the aggregate is embedded in a traditional volume that has CIFS shares, users should be warned before taking the aggregate (and hence the entire traditional volume) offline. Use the -t switch for this. The cifsdelaytime argument specifies the number of minutes to delay before taking the embedded aggregate offline, during which time CIFS users of the traditional volume are warned of the pending loss of service. A time of 0 means take the aggregate offline immediately with no warnings given. CIFS users can lose data if they are not given a chance to terminate applications gracefully.

If a plexname is specified, the plex must be part of a mirrored aggregate and both plexes must be online. Prior to offlining a plex, the system will flush all internally-buffered data associated with the plex and create a snapshot that is written out to both plexes. The snapshot allows for efficient resynchronization when the plex is subsequently brought back online.

Sejumlah operasi yang dilakukan pada volume tradisional kelompok agregasi dapat mencegah aggr offline dari berikutnya, untuk berbagai panjang waktu. Bila operasi itu ditemukan, akan ada menunggu satu detik untuk operasi tersebut sampai akhir. Jika tidak, perintahnya adalah dibatalkan.

Sebuah cek juga dibuat untuk file dalam volume yang terkait tradisional kelompok agregasi dibuka oleh proses OnTap internal. Perintah ini dibatalkan jika ada ditemukan.

aggr secara online {aggrname | plexname}
[-F]

Membawa aggrname bernama agregat (atau kompleks bernama plexname) online. Perintah ini akan segera berlaku. Jika agregat ditentukan tertanam dalam volume tradisional, volume juga juga membawa online.

Jika aggrname sebuah ditentukan, harus saat ini sedang tertutup, terbatas, atau asing. Jika agregat adalah asing, akan dibuat asli sebelum dibawa online. Sebuah "asing" agregat merupakan agregat yang terdiri dari disk dipindahkan dari filer lain dan yang belum pernah dibawa online di filer saat ini. Agregat yang tidak asing dianggap "asli."

Jika agregat tidak konsisten, tetapi tidak kehilangan data, pengguna akan diperingatkan dan diminta sebelum membawa online agregat. F-bendera dapat digunakan untuk menimpa perilaku ini. Dianjurkan untuk menjalankan WAFL_check (atau melakukan inisialisasi SnapMirror dalam hal agregat tertanam dalam volume tradisional) sebelum dinyalakan online agregat konsisten. Membawa online agregat konsisten meningkatkan risiko korupsi sistem file lebih lanjut. Jika agregat tidak konsisten dan telah mengalami kemungkinan hilangnya data, tidak dapat dibawa online kecuali WAFL_check (atau SnapMirror initialize dalam kasus tertanam) telah berjalan di agregat.

Jika plexname tersebut ditentukan, kompleks harus menjadi bagian dari agregat cermin online. Sistem akan memulai sinkronisasi dari kompleks sebagai bagian dari pengolahan online.

aggr pilihan aggrname [OPTNAME optval]

Menampilkan pilihan yang telah ditetapkan untuk aggrname agregat, atau menetapkan opsi bernama OPTNAME dari aggrname bernama agregat ke optval nilai. Perintah tetap berlaku setelah filer tersebut reboot, sehingga tidak perlu untuk menambahkan opsi aggr perintah ke file / etc / rc. Beberapa opsi yang memiliki nilai angka. Some options have values that may be on (which can also be expressed as yes , true , or 1 ) or off (which can also be expressed as no , false , or 0 ). A mixture of uppercase and lowercase characters can be used when typing the value of an option. The aggr status command displays the options that are set per aggregate.

The following describes the options and their possible values:

fs_size_fixed on | off

Pilihan ini hanya berlaku untuk agregat yang tertanam dalam volume tradisional. Hal ini menyebabkan sistem file tetap sama ukuran dan tidak tumbuh atau menyusut ketika hubungan Volume SnapMirrored rusak, atau add aggr dilakukan di atasnya. Pilihan ini secara otomatis ditetapkan menjadi pada saat volume tradisional menjadi volume SnapMirrored. Ini akan tetap pada setelah perintah istirahat SnapMirror dikeluarkan untuk volume tradisional. Hal ini memungkinkan volume tradisional untuk SnapMirrored kembali ke sumber tanpa perlu menambahkan disk untuk volume sumber tradisional. Jika ukuran volume tradisional adalah lebih besar dari ukuran file sistem, mematikan opsi ini akan memaksa sistem file untuk tumbuh dengan ukuran volume tradisional. Pengaturan default tidak aktif.

ignore_inconsistent on | off

Perintah ini hanya dapat digunakan dalam modus pemeliharaan. Jika opsi ini diset, ini memungkinkan terpadu yang memuat volume akar untuk dibawa online di booting, meskipun tidak konsisten. Pengguna memperingatkan bahwa membawa secara online sebelum menjalankan WAFL_check atau wafliron dapat mengakibatkan inkonsistensi sistem file lebih lanjut.

nosnap on | off

Jika opsi ini aktif, ia mematikan snapshot otomatis pada agregat. Pengaturan default tidak aktif.

raidsize jumlah

The value of this option is the maximum size of a RAID group that can be created in the aggregate. Changing the value of this option will not cause existing RAID groups to grow or shrink; it will only affect whether more disks will be added to the last existing RAID group and how large new RAID groups will be.

Legal values for this option depend on raidtype . For example, raid_dp allows larger RAID groups than raid4 . Limits and default values are also different for different types of filer appliances and different types of disks. Following tables define limits and default values for raidsize .

 —————————————— raid4 raidsize min default max —————————————— R100 2 8 8 R150 2 6 6 FAS250 2 7 14 other (FCAL disks) 2 8 14 other (ATA disks) 2 7 7 —————————————— —————————————— raid_dp raidsize min default max —————————————— R100 3 12 12 R150 3 12 16 other (FCAL disks) 3 16 28 other (ATA disks) 3 14 16 —————————————— 

Those values may change in future releases of Data ONTAP.

raidtype raid4 | raid_dp | raid0

Sets the type of RAID used to protect against disk failures. Use of raid4 provides one parity disk per RAID group, while raid_dp provides two. Changing this option immediately changes the RAID type of all RAID groups within the aggregate. When upgrading RAID groups from raid4 to raid_dp , each RAID group begins a reconstruction onto a spare disk allocated for the second `dparity' parity disk.

Changing this option also changes raidsize to a more suitable value for new raidtype . When upgrading from raid4 to raid_dp , raidsize will be increased to the default value for raid_dp . When downgrading from raid_dp to raid4 , raidsize will be decreased to the size of the largest existing RAID group if it is between the default value and the limit for raid4 . If the largest RAID group is above the limit for raid4 , the new raidsize will be that limit. If the largest RAID group is below the default value for raid4 , the new raidsize will be that default value. If raidsize is already below the default value for raid4 , it will be reduced by 1.

resyncsnaptime number

This option is used to set the mirror resynchronization snapshot frequency (in minutes). The default value is 60 minutes.

root

If this option is set on a traditional volume, then the effect is identical as that defined in vol man page. Otherwise, if this option is set on an aggregate capable of containing flexible volumes, then that aggregate is marked as being the one that will also contains the root flexible volume on the next reboot. This option can be used on only one aggregate or traditional volume at any given time. The existing root aggregate or traditional volume will become a non-root entity after the reboot.

Until the system is rebooted, the original aggregate and/or traditional volume will continue to show root as one of its options, and the new root aggregate or traditional volume will show diskroot as an option. In general, the aggregate that has the diskroot option is the one that will contain the root flexible volume following the next reboot.

Satu-satunya cara untuk menghapus status akar volume agregat atau tradisional adalah untuk mengatur opsi root pada volume lain agregat atau tradisional.

snaplock_compliance

Ini telah dibaca satunya pilihan menunjukkan bahwa agregat adalah agregat Kepatuhan SnapLock. Agregat hanya dapat ditunjuk agregat Kepatuhan SnapLock pada saat penciptaan.

snaplock_enterprise

Ini telah dibaca satunya pilihan menunjukkan bahwa agregat adalah agregat Perusahaan SnapLock. Agregat hanya dapat ditunjuk agregat Perusahaan SnapLock pada saat penciptaan.

snapmirrored off

Jika SnapMirror diaktifkan untuk volume tradisional (SnapMirror tidak didukung untuk agregat yang mengandung volume fleksibel), filer secara otomatis mengatur opsi ini untuk di. Set opsi ini untuk off jika SnapMirror tidak lagi digunakan untuk memperbarui cermin volume yang tradisional. Setelah menyetel opsi ini ke off, cermin menjadi volume tradisional biasa ditulis. Opsi ini hanya dapat diatur ke off, hanya filer dapat mengubah nilai dari opsi ini dari off ke on.

snapshot_autodelete on | off

Pilihan ini digunakan untuk mengatur apakah snapshot secara otomatis dihapus dalam aggr tersebut. Jika diaktifkan maka foto dapat dihapus dalam aggr untuk memulihkan penyimpanan yang diperlukan. Jika diatur ke off maka snapshot di aggr ini tidak otomatis dihapus untuk memulihkan penyimpanan. Perhatikan bahwa snapshot masih mungkin dihapus karena alasan lain, seperti menjaga jadwal snapshot untuk aggr, atau menghapus foto-foto yang berkaitan dengan operasi khusus yang tidak perlu lagi snapshot. Untuk memungkinkan snapshot untuk dihapus pada waktu yang tepat jumlah foto aggr terbatas ketika snapshot_autodelete diaktifkan. Karena itu, jika ada snapshot terlalu banyak dalam sebuah aggr kemudian beberapa foto harus dihapus sebelum pilihan snapshot_autodelete dapat diaktifkan.

aggr mengubah nama aggrname newname

Mengganti nama tersebut aggrname bernama agregat newname. Jika agregat ini tertanam dalam volume tradisional, maka nama bahwa volume yang juga berubah.

aggr membatasi aggrname
[-T cifsdelaytime]

Pasang aggrname bernama agregat dalam keadaan terbatas, mulai dari baik negara online atau offline. Perintah berlaku sebelum kembali.

Jika agregat mengandung volume fleksibel, operasi dibatalkan kecuali filer dalam modus pemeliharaan.

Jika agregat tertanam dalam volume tradisional yang memiliki saham CIFS, pengguna harus diperingatkan sebelum membatasi agregat (dan karenanya volume tradisional seluruh). Gunakan-t saklar untuk ini. Argumen cifsdelaytime menentukan jumlah menit untuk menunda sebelum mengambil secara offline agregat tertanam, selama waktu CIFS pengguna dari volume tradisional memperingatkan hilangnya tertunda pelayanan. Sebuah waktu dari 0 berarti mengambil secara offline agregat secepatnya tanpa peringatan yang diberikan. Pengguna CIFS bisa kehilangan data jika mereka tidak diberi kesempatan untuk mengakhiri aplikasi anggun.

aggr scrub CV [aggrname | plexname | groupname]

Resume scrubbing paritas pada agregat bernama, kompleks, atau kelompok. Jika nama tidak diberikan, melanjutkan kelompok RAID semua saat ini menjalani scrubbing paritas yang telah ditangguhkan.

aggr scrub awal [aggrname | plexname | groupname]

Mulai menggosok paritas pada agregat secara online bernama. Scrubbing Paritas membandingkan data ke disk paritas disk (s) dalam kelompok RAID mereka, mengoreksi isi paritas disk sebagai diperlukan. Jika nama tidak diberikan, scrubbing paritas dimulai pada semua agregat online. Jika nama agregat diberikan, scrubbing yang dimulai pada semua kelompok RAID yang terkandung dalam agregat. Jika nama kompleks diberikan, scrubbing yang dimulai pada semua kelompok RAID yang terdapat dalam kompleks itu.

aggr Status scrub [aggrname | plexname | groupname] [-v]

Prints the status of parity scrubbing on the named aggregate, plex, or group; all RAID groups currently undergoing parity scrubbing if no name is given. The status includes a percent-complete, and the scrub's suspended status.

The -v flag displays the date and time at which the last full scrub completed along with the current status on the named aggregate, plex, or group; all RAID groups if no name is given.

aggr scrub stop [ aggrname | plexname | groupname ]

Stops parity scrubbing on the named aggregate, plex, or group; if no name is given, on all RAID groups currently undergoing a parity scrubbing.

aggr scrub suspend [ aggrname | plexname | groupname ]

Suspends parity scrubbing on the named aggregate, plex, or group; if no name is given, on all RAID groups currently undergoing parity scrubbing.

aggr show_space [ -h | -k | -m | -g | -t | -b ] < aggrname >

Displays the space usage in an aggregate. Unlike df, this command shows the space usage for each flexible volume within an aggregate If aggrname is specified, aggr show_space only runs on the corresponding aggregate, otherwise it reports space usage on all the aggregates.

Semua ukuran dilaporkan dalam blok 1024-byte, kecuali diminta oleh salah satu-h,-k, m, g, atau-t pilihan. -K,-m,-g, dan-t pilihan skala ukuran masing-masing bidang terkait dari output yang akan dinyatakan dalam kilobyte, megabyte, gigabyte, atau terabyte masing-masing.

Terminologi berikut digunakan oleh perintah dalam melaporkan ruang.

      Total space This is the amount of total disk space that the aggregate has. WAFL reserve WAFL reserves a percentage of the total total disk space for aggregate level metadata. The space used for maintaining the volumes in the aggregate comes out of the WAFL reserve. Snap reserve Snap reserve is the amount of space reserved for aggregate snapshots. Usable space This is the total amount of space that is available to the aggregate for provisioning. This is computed as Usable space = Total space – WAFL reserve – Snap reserve df displays this as the 'total' space. BSR NVLOG This is valid for Synchronous SnapMirror destinations only. This is the amount of space used in the aggregate on the destination filer to store data sent from the source filer(s) before sending it to disk. Allocated This is the sum of the space reserved for the volume and the space used by non reserved data. For volume guaranteed volumes, this is at least the size of the volume since no data is unreserved. For volumes with space guarantee of none, this value is the same as the 'Used' space (explained below) since no unused space is reserved. The Allocated space value shows the amount of space that the volume is taking from the aggregate. This value can be greater than the size of the volume because it also includes the metadata required to maintain the volume. Used This is the amount of space that is taking up disk blocks. This value is not the same as the 'used' space displayed by the df command. The Used space in this case includes the metadata required to maintain the flexible volume. Avail Total amount of free space in the aggregate. This is the same as the avail space reported by df. 

aggr split plexname aggrname
[ -r oldvol newvol ] [ -r ... ]
[ -s suffix ]

Removes plexname from a mirrored aggregate and creates a new unmirrored aggregate named aggrname that contains the plex. The original mirrored aggregate becomes unmirrored. The plex to be split from the original aggregate must be functional (not partial), but it could be inactive, resyncing, or outof-date. Aggr split can therefore be used to gain access to a plex that is not up to date with respect to its partner plex, if its partner plex is currently failed.

If the aggregate in which plexname resides is embedded in a traditional volume, aggr split behaves identically to vol split . The new aggregate is embedded in a new traditional volume of the same name.

If the aggregate in which plexname resides contains exactly one flexible volume, aggr split will by default rename the flexible volume image in the split-off plex to be the same as the new aggregate.

If the aggregate in which plexname resides contains more than one flexible volume, it is necessary to specify how to name the volumes in the new aggregate resulting from the split. The -r option can be used repeatedly to give each flexible volume in the resulting aggregate a new name. In addition, the -s option can be used to specify a suffix that is added to the end of all flexible volume names not covered by a -r .

If the original aggregate is restricted at the time of the split, the resulting aggregate will also be restricted. If the restricted aggregate is hosting flexible volumes, they are not renamed at the time of the split. Flexible volumes will be renamed later, when the name conflict is detected while bringing an aggregate online. Flexible volumes in the aggregate that is brought online first keep their names. That aggregate can be either the original aggregate, or the aggregate resulting from the split. When the other aggregate is brought online later, flexible volumes in that aggregate will be renamed.

If the plex of an aggregate embedded within a traditional volume is offline at the time of the split, the resulting aggregate will be offline. When splitting a plex from an aggregate that hosts flexible volumes, if that plex is offline, but the aggregate is online, the resulting aggregate will come online, and its flexible volumes will be renamed. It is not allowed to split a plex from an offline aggregate.

A split mirror can be joined back together via the -v option to aggr mirror .

aggr status [ aggrname ]
[ -r | -v | -d | -c | -b | -s | -f | -i ]

Displays the status of one or all aggregates on the filer. If aggrname is used, the status of the specified aggregate is printed; otherwise the status of all aggregates in the filer are printed. By default, it prints a one-line synopsis of the aggregate which includes the aggregate name, whether it contains a single traditional volume or some number of flexible volumes , if it is online or offline, other states (for example, partial , degraded , wafl inconsistent , and so on) and peraggregate options. Per-aggregate options are displayed only if the options have been changed from the system default values by using the aggr options command, or by the vol options command if the aggregate is embedded in a traditional volume. If the wafl inconsistent state is displayed, please contact Customer Support.

The -v flag shows the on/off state of all peraggregate options and displays information about each volume, plex and RAID group contained in the aggregate.

The -r flag displays a list of the RAID information for that aggregate. If no aggrname is specified, it prints RAID information about all aggregates, information about file system disks, spare disks, and failed disks. For more information about failed disks, see the -f switch description below.

The -d flag displays information about the disks in the specified aggregate. The types of disk information are the same as those from the sysconfig -d command.

The -c flag displays the upgrade status of the Block Checksums data integrity protection feature.

The -b is used to get the size of source and destination aggregates for use with aggr copy . The output contains the storage in the aggregate and the possibly smaller size of the aggregate. The aggregate copy command uses these numbers to determine if the source and destination aggregate sizes are compatible. The size of the source aggregate must be equal or smaller than the size of the destination aggregate.

The -s flag displays a listing of the spare disks on the filer.

The -f flag displays a list of the failed disks on the filer. The command output includes the disk failure reason which can be any of following:

The -i flag displays a list of the flexible volumes contained in an aggregate.

 unknown Failure reason unknown. failed Data ONTAP failed disk due to a fatal disk error. admin failed User issued a 'disk fail' command for this disk. labeled broken Disk was failed under Data ONTAP 6.1.X or an earlier version. init failed Disk initialization sequence failed. admin removed User issued a 'disk remove' command for this disk. not responding Disk not responding to requests. pulled Disk was physically pulled, or no data path exists on which to access the disk. bypassed Disk was bypassed by ESH. 

aggr undestroy [ -n ] < aggrname >

Undestroy a partially intact or previously destroyed aggregate or traditional volume. The command prints a list of candidate aggregates and traditional volumes matching the given name, which can be potentially undestroyed.

The -n option prints the list of disks contained by the aggregate or by the traditional volume, which can be potentially undestroyed. This option can be used to display the result of command execution, without actually making any changes.

aggr verify resume [ aggrname ]

Resumes RAID mirror verification on the named aggregate; if no aggregate name is given, on all aggregates currently undergoing a RAID mirror verification that has been suspended.

aggr verify start [ aggrname ] [ -f plexnumber ]

Starts RAID mirror verification on the named online mirrored aggregate. If no name is given, then RAID mirror verification is started on all online mirrored aggregates. Verification compares the data in both plexes of a mirrored aggregate. In the default case, all blocks that differ are logged, but no changes are made. If the -f flag is given, the plex specified is fixed to match the other plex when mismatches are found. A name must be specified with the -f plexnumber option.

aggr verify stop [ aggrname ]

Stops RAID mirror verification on the named aggregate; if no aggregate name is given, on all aggregates currently undergoing a RAID mirror verification.

aggr verify status [ aggrname ]

Prints the status of RAID mirror verification on the named aggregate; on all aggregates currently undergoing RAID mirror verification if no aggregate name is given. The status includes a percent-complete, and the verification's suspended status.

aggr verify suspend [ aggrname ]

Menunda RAID cermin verifikasi pada agregat bernama, jika tidak ada nama agregat diberikan, pada semua agregat saat ini menjalani verifikasi RAID cermin.

KLASTER PERTIMBANGAN

Agregat pada pelapor yang berbeda dalam sebuah cluster dapat memiliki nama yang sama. Sebagai contoh, kedua pelapor dalam sebuah cluster dapat memiliki agregat bernama aggr0.

Namun, memiliki nama yang unik agregat dalam sebuah cluster membuat lebih mudah untuk bermigrasi agregat antara pelapor di cluster.

CONTOH

aggr menciptakan aggr1-r 10 20

Menciptakan agregat bernama aggr1 dengan 20 disk. Kelompok RAID secara agregat ini dapat berisi hingga 10 disk, jadi ini agregat baru memiliki dua kelompok RAID. Filer menambahkan disk cadang saat ini ke agregat baru, dimulai dengan disk terkecil.

aggr membuat aggr1 20 @ 9

Menciptakan agregat bernama aggr1 dengan 20 9-GB disk. Karena tidak ada ukuran kelompok RAID yang ditentukan, ukuran default (8 disk) yang digunakan. Agregat baru dibentuk berisi kelompok RAID dua dengan 8 disk dan kelompok ketiga dengan empat disk.

aggr menciptakan aggr1-d 8a.1 8a.2 8a.3

Menciptakan agregat bernama aggr1 dengan tiga disk yang ditentukan.

aggr membuat aggr1 10
aggr options aggr1 raidsize 5

The first command creates an aggregate named aggr1 with 10 disks which belong to one RAID group. The second command specifies that if any disks are subsequently added to this aggregate, they will not cause any current RAID group to have more than five disks. Each existing RAID group will continue to have 10 disks and no more disks will be added to that RAID group. When new RAID groups are created, they will have a maximum size of five disks.

aggr show_space -h ag1

Displays the space usage of the aggregate `ag1′ and scales the unit of space according to the size.

 Aggregate 'ag1′ Total space WAFL reserve Snap reserve Usable space BSR NVLOG 66GB 6797MB 611MB 59GB 65KB Space allocated to volumes in the aggregate Volume Allocated Used Guarantee vol1 14GB 11GB volume vol2 8861MB 8871MB file vol3 6161MB 6169MB none vol4 26GB 25GB volume vol1_clone 1028MB 1028MB (offline) Aggregate Allocated Used Avail Total space 55GB 51GB 3494MB Snap reserve 611MB 21MB 590MB WAFL reserve 6797MB 5480KB 6792MB 

aggr status aggr1 -r

Displays the RAID information about aggregate aggr1 . In the following example, we see that aggr1 is a RAID-DP aggregate protected by block checksums. It is online, and all disks are operating normally. The aggregate contains four disks -two data disks, one parity disk, and one doubleparity disk. Two disks are located on adapter 0b, and two on adapter 1b. The disk shelf and bay numbers for each disk are indicated. All four disks are 10, 000 RPM FibreChannel disks attached via disk channel A. The disk "Pool" attribute is displayed only if SyncMirror is licensed, which is not the case here (if SyncMirror were licensed, Pool would be either 0 or 1). The amount of disk space that is used by Data ONTAP (“Used”) and is available on the disk (“Phys”) is displayed in the rightmost columns.

  Aggr aggr1 (online, raid_dp) (block checksums) Plex /aggr1/plex0 (online, normal, active) RAID group /aggr1/plex0/rg0 (normal) RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) ——— —— ————- —- —- —- —– ————– ————– dparity 0b.16 0b 1 0 FC:A – FCAL 10000 136000/278528000 137104/280790184 parity 1b.96 1b 6 0 FC:A – FCAL 10000 136000/278528000 139072/284820800 data 0b.17 0b 1 1 FC:A – FCAL 10000 136000/278528000 139072/284820800 data 1b.97 1b 6 1 FC:A – FCAL 10000 136000/278528000 139072/284820800 

SEE ALSO

vol , partner , snapmirror , sysconfig .


Table of Contents






















































Manual Pages , , , ,

cf

July 7th, 2009

Table of Contents

NAME

cf – controls the takeover and giveback operations of the filers in a cluster

SYNOPSIS

cf [ disable | enable | forcegiveback | forcetakeover [ -df ] | giveback [ -f ] | hw_assist [ status | test stats [ clear ] ] | monitor | partner | status [ -t ] takeover [ -f ] | [ -n ]]

cf nfo [ enable | disable ] disk_shelf

cf nfo status

URAIAN

The cf command controls the cluster failover monitor, which determine when takeover and giveback operations take place within a cluster.

The cf command is available only if your filer has the cluster license.

OPTIONS

disable
Disables the takeover capability of both filers in the cluster.

enable
Enables the takeover capability of both filers in the cluster.

forcegiveback
forcegiveback is dangerous and can lead to data corruption; in almost all cases, use cf giveback -f instead.

Forces the live filer to give back the resources of the failed filer even though the live filer determines that doing so might result in data corruption or cause other severe problems. giveback will refuse to giveback under these conditions. Using the forcegiveback option forces a giveback. When the failed filer reboots as a result of a forced giveback, it displays the following message:

partner giveback incomplete, some data may be lost

forcetakeover [-f] forcetakeover is dangerous and can lead to data corruption; in almost all cases, use cf takeover instead.

Forces one filer to take over its partner even though the filer detects an error that would otherwise prevent a takeover. For example, normally, if a detached or faulty ServerNet cable between the filers causes the filers' NVRAM contents to be unsynchronized, takeover is disabled. However, if you enter the cf forcetakeover command, the filer takes over its partner despite the unsynchronized NVRAM contents. This command might cause the filer being taken over to lose client data. If you use the -f option, the cf command allows such a forcetakeover to proceed without requiring confirmation by the operator.

forcetakeover -d[f] Forces a filer to take over its partner in all cases where a forcetakeover would fail. In addition it will force a takeover even if some partner mailbox disks are inaccessible. It can only be used when cluster_remote is licensed.

forcetakeover -d is very dangerous. Not only can it cause data corruption, if not used carefully, it can also lead to a situation where both the filer and it's partner are operational (split brain). As such, it should only be used as a means of last resort when the takeover and forcetakeover commands are unsuccessful in achieving a takeover. The operator must ensure that the partner filer does not become operational at any time while a filer is in a takeover mode initiated by the use of this command. In conjunction with RAID mirroring, it can allow recovery from a disaster when the two filers in the cluster are located at two distant sites. The use of -f option allows this command to proceed without requiring confirmation by the operator.

giveback [ -f ]
Initiates a giveback of partner resources. Once the giveback is complete, the automatic takeover capability is disabled until the partner is rebooted. A giveback fails if outstanding CIFS sessions, active system dump processes, or other filer operations makes a giveback dangerous or disruptive. If you use the -f option, the cf command allows such a giveback to proceed as long as it would not result in data corruption or filer error.

hw_assist [ status | test | stats [ clear ] ] Displays information related to the hardware-assisted takeover functionality. Use the cf hw_assist status command to display the hardware-assisted functionality status of the local as well as the partner filer. If hardware-assisted status is inactive, the command displays the reason and if possible, a corrective action. Use the cf hw_assist test command to validate the hardware-assisted takeover configuration. An error message is printed if hardware-assisted takeover configuration can not be validated. Use the cf hw_assist stats command to display the statistics for all hw_assist alerts received by the filer. Use cf hw_assist stats clear to clear hardware-assisted functionality statistics.

monitor
Displays the time, the state of the local filer and the time spent in this state, the host name of the partner and the state of cluster failover monitor (whether enabled or disabled). If the partner has not been taken over currently, the status of the partner and that of the interconnect are displayed and any ongoing giveback or scheduled takeover operations are reported.

partner
Displays the host name of the partner. If the name is unknown, the cf command displays “ partner .”

status
Displays the current status of the local filer and the cluster. If you use the -t option, displays the status of the node as time master or slave.

takeover [ -f ] | [ -n ]
Initiates a takeover of the partner. If you use the -f option, the cf command allows such a takeover to proceed even if it will abort a coredump on the other filer.

If you use the -n option, the cf command allows a takeover to proceed even if the partner node was running an incompatible version of Data ONTAP. The partner node must be cleanly halted in order for this option to succeed. This is used as part of a nondisruptive upgrade process.

nfo [ enable | disable ] disk_shelf
Enables or disables negotiated failover on disk shelf count mismatch.

This command is obsolete. Option cf.takeover.on_disk_shelf_miscompare replaces it.

Negotiated failover is a general facility which supports negotiated failover on the basis of decisions made by various modules. disk_shelf is the only negotiated failover module currently implemented. When communication is first established over the interconnect between the local filer and its partner, a list of disk shelves seen by each node on its A and B loops is exchanged. If a filer sees that the count of shelves that the partner sees on its B loops is greater than the filer's count of shelves on its A loops, the filer concludes that it is “impaired” (as it sees fewer of its shelves than its partner does) and asks the partner to take it over. If the partner is not itself impaired, it will accept the takeover request and, in turn, ask the requesting filer to shut down gracefully. The partner takes over after the requesting node shuts down, or after a time-out period of approximately 3 minutes expires. The comparison of disk shelves is only done when communication between the filers is established or re-established (for example, after a node reboots).

nfo status
Displays the current negotiated failover status.

This command is obsolete. Use cf status instead.

SEE ALSO

partner


Table of Contents



Manual Pages , , , ,

bootfs

July 7th, 2009

Table of Contents

NAME

bootfs – boot file system accessor command (ADVANCED)

SYNOPSIS

bootfs chkdsk disk

bootfs core [ -v ] disk

bootfs dir [ -r ] path

bootfs dump { disk | drive } { sector | cluster }

bootfs fdisk disk partition1sizeMB [ partition2sizeMB ] [ partition3sizeMB ] [ partition4sizeMB ]

bootfs format drive [ label ]

bootfs info disk

bootfs sync [ -f ] { disk | drive }

bootfs test [ -v ] disk

DESCRIPTION

The bootfs command allows content viewing and format manipulation of the the boot device.

Using the bootfs command, you may perform four important functions. You may check the integrity of the boot device via the chkdsk subcommand. You may view the contents of your boot device via the dir , dump , and info subcommands. You may alter the partition sizes and format types present on the boot device via the fdisk subcommand. You may reformat the partitions present on the boot device via the format command. You may sync all in memory contents to the physical media via the sync subcommand. Lastly, you may diagnose the health of your boot device via the test subcommand.

OPTIONS

-v
Turns on verbose output.

-r
Recursively lists directories and files.

path
A path consists of a drive, optional directories, and an optional file name. Directories are separated by a /. To discover your boot drive's name, use " bootfs help subcommand ".

disk
A disk is a physical object, probably a compact flash in this case. A disk name is generally of the form [PCI slot number]a.0, eg 0a.0. To discover your boot disk's name, use " bootfs help subcommand ".

drive
A drive is a formatted partition on the disk. A disk may contain up to four drives. A drive name is generally of the form [PCI slot number]a.0:[partition
number]:,
eg 0a.0:1:. To discover your boot drive's name, use " bootfs help sub_ c ommand ".

sector
Disks are divided into sectors. Sectors are based at 0.

cluster
Drives are divided into clusters. Clusters are based at 2, though the root directory can be thought to reside at cluster 0.

partitionNsizeMB
The size of partition N in megabytes. There can be at most four partitions per disk.

label
An 11-character or less string which names the drive.

CLUSTER CONSIDERATIONS

The bootfs command cannot be used on a clustered system's partner.

EXAMPLES

The dir subcommand lists all files and subdirectories contained in the path provided. The information presented for each file and subdirectory is (in this column order) name, size, date, time, and cluster.

bootfs dir 0a.0:1:/x86/kernel/

 Volume Label in Drive 0a.0:1: is KERNEL Volume Serial Number is 716C-E9F8 Directory of 0a.0:1:/x86/kernel/ . DIR 02-07-2003 2:37a 2 .. DIR 02-07-2003 2:37a 3 PRIMARY.KRN 9318400 04-07-2003 6:53p 4 2187264 bytes free 

The dump subcommand lists either a sector on a disk or a cluster on a drive, depending on the command line arguments provided. The sector or cluster is listed in both hexadecimal and ASCII form.

bootfs dump 0a.0 110

  sector 110 absolute byte 0xdc00 on disk 0a.0 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 0123456789abcdef —-++————————————————++—————- 0000 00 90 ba 5e b4 01 00 80 7b 0c 00 7d 05 ba 51 b4 …^….{..}..Q. 0010 01 00 83 7b 04 00 74 0a 8b 47 24 a3 dc ce 01 00 …{..t..G$….. 0020 eb 0a c7 05 dc ce 01 00 00 00 e0 fe 83 c4 fc ff ……………. 0030 35 dc ce 01 00 52 68 80 b4 01 00 e8 26 b0 ff ff 5….Rh…..&… 0040 a1 dc ce 01 00 8b 90 f0 00 00 00 80 ce 01 89 90 ……………. [etc.] bootfs dump 0a.0:1: 5 cluster 5 absolute byte 0x25a00 on drive 0a.0:1: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 0123456789abcdef —-++————————————————++—————- 0000 0a 19 12 00 19 0f 00 01 00 64 00 00 00 00 00 00 ………d…… 0010 a1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ……………. 0020 00 00 00 00 5a 44 5a 44 00 10 00 00 00 00 01 b0 ….ZDZD…….. 0030 20 04 00 10 20 05 00 01 20 06 00 02 20 07 00 13 … … … … 0040 fc ef 00 00 fc b1 20 80 fc d0 20 80 4a 63 c0 55 …… … .Jc.U [etc.] 

The fdisk subcommand creates drives within a disk. A maximum of four drives may be created per disk. The sum of the drives must be less than the size of the disk. Note that most disk manufacturers define a megabyte as 1000*1000 bytes, resulting in a disk being smaller than the size advertised (for example, a 32 MB disk is really 30.5 MB). Performing an fdisk destroys all data on the disk.

bootfs fdisk 0a.0 30

The format subcommand formats a drive to the FAT file system standard. A drive must be formatted before it can store files.

bootfs format 0a.0:1: NETAPP

The info subcommand prints information about a disk. The location of various elements and sizes of sections is displayed.

bootfs info 0a.0

  ——————————————————————– partition: 1 2 3 4 ——————————————————————– file system: 0×01 0×01 0×01 0×01 bytes per cluster: 4096 4096 4096 4096 number of clusters: 2809 2809 2042 251 total bytes: 11534336 11534336 8388608 1048576 usable bytes: 11501568 11501568 8359936 1024000 free bytes: 11505664 11505664 8364032 1028096 FAT location: 512 512 512 512 root location: 9728 9728 6656 1536 data location: 26112 26112 23040 17920 

The test subcommand read and writes to/from every byte on the disk. The test subcommand can be used if you suspect your disk is faulty. A faulty disk would, for example, result in a download command failure.

bootfs test -v 0a.0

 [.................................] disk 0a.0 passed I/O test 

SEE ALSO

download


Table of Contents

Manual Pages , , , ,

boot

July 7th, 2009

Table of Contents

NAME

boot – directory of Data ONTAP executables

SYNOPSIS

/etc/boot

DESCRIPTION

The boot directory contains copies of the executable files required to boot the filer. The download command (see download ) copies these files from /etc/boot into the filer's boot block, from which the system boots.

FILES

/etc/boot
directory of Data ONTAP executables. Files are place in /etc/boot after the tar or setup.exe has decompressed them. These files vary from release to release.

SEE ALSO

download


Table of Contents

Copyright © 1994-2008 NetApp, Inc. Legal Information

VN: F [1.9.11_1134]
Rate this post:
Rating: 0.0 / 10 (0 votes cast)

Manual Pages , , , ,

BMC

July 7th, 2009

Table of Contents

NAME

bmc – commmands for use with a Baseboard Management Controller (BMC)

SYNOPSIS

bmc help

bmc reboot

bmc setup

bmc status

bmc test autosupport

DESCRIPTION

The bmc command is used to manage and test a Baseboard Management Controller (BMC), if one is present.

OPTIONS

help
Display a list of Baseboard Management Controller (BMC) commands.

reboot
The reboot command forces the BMC to reboot itself and perform a self-test. If your console connection is through the BMC it will be dropped.

setup
Interactively configure the BMC local-area network (LAN) setttings.

status
Display the current status of the BMC.

test autosupport
Test the BMC autosupport by commanding the BMC to send a test autosupport to all autosupport email addresses in the option lists autosupport.to , autosupport.noteto , and autosupport.support.to .

CLUSTER CONSIDERATIONS

This command only acts upon the Baseboard Management Controller (BMC) that is local to the system.

EXAMPLES

bmc status

might produce:

              Baseboard Management Controller: Firmware Version: 1.0 IPMI version: 2.0 DHCP: on BMC MAC address: 00:a0:98:05:2b:4a IP address: 10.98.144.170 IP mask: 255.255.255.0 Gateway IP address: 10.98.144.1 BMC ARP interval: 10 seconds BMC has user: naroot ASUP enabled: on ASUP mailhost: mailhost@netapp.com ASUP from: postmaster@netapp.com ASUP recipients: dl-qa-autosupport@netapp.com 

SEE ALSO

setup , options

NOTES

Some of these commands might pause before completing while the Baseboard Management Controller (BMC) is queried. This is normal behavior.


Table of Contents

Copyright © 1994-2008 NetApp, Inc. Legal Information

VN: F [1.9.11_1134]
Rate this post:
Rating: 0.0 / 10 (0 votes cast)

Manual Pages , , , ,

backuplog

July 7th, 2009

Table of Contents

NAME

backuplog – captures significant events during file system backup/recovery activities.

SYNOPSIS

/etc/log/backup

DESCRIPTION

Filer captures significant dump/restore-related events and the respective times at which they occur. All events are recorded in one-line messages in /etc/log/backup.

The following are the events filer monitors:

Start
Dump/restore starts.

Restart
Restart of a dump/restore.

End
Dump/restore completes successfully.

Abort
The operation aborts.

Kesalahan
Dump/restore hits an unexpected event.

Options
Logs the options as users specify.

Tape_open
Output device is opened successfully.

Tape_close
Output device is closed successfully.

Phase_change
As dump/restore completes a stage.

Dump specific events:

Snapshot
When the snapshot is created or located.

Base_dump
When a valid base dump entry is located.

Logging events:

Start_logging Logging begins.

Stop_logging
Logging ends.

Each event record is in the following format:

TYPE TIME_STAMP IDENTIFIER EVENT (EVENT_INFO)

TYPE
Either dmp(dump), rst(restore) or log events.

TIME_STAMP
Shows date and time at which event occurs.

IDENTIFIER
Unique ID for the dump/restore.

EVENT
The event name.

EVENT_INFO
Event specific information.

A typical event record message looks like:

dmp Thu Apr 5 18:54:56 PDT 2001 /vol/vol0/ home(5) Start (level 0, NDMP)

In the particular example:

TYPE
= dmp

TIME_STAMP
= Thu Apr 5 18:54:56 PDT 2001

IDENTIFER
= /vol/vol0/ home(5)

EVENT
= Start

EVENT_INFO
= level 0, NDMP

All event messages go to /etc/log/backup. On every Sunday at 00:00, backup is roated to backup.0 and backup.0 is moved to backup.1 and so on. Up to 6 log files(spanning up to 6 weeks) are kept.

The registry option backup.log.enable controls the enabling and disabling of the logging with values on and off respectively. The functionality is enabled by default. (See options for how to set options.)

FILES

/etc/log/backup
backup log file for current week. /etc/log/backup.[0-5] backup log files for previous weeks

SEE ALSO

dump , restore , options


Table of Contents

Manual Pages , , , ,

backup

July 7th, 2009

Table of Contents

NAME

backup – manages backups

SYNOPSIS

backup status [ <ID> ]

backup terminate <ID>

DESCRIPTION

The backup commands provide facilities to list and manipulate backups on a filer.

A backup job runs on a filer as a process that copies a file system or a subset of it to secondary media, usually tapes. Data can be restored from the secondary media in case the original copy is lost. There are several types of backup processes that run on the filers:

dump
runs natively on the filer.

NDMP
driven by a 3rd party client through NDMP protocol.

RESTARTABLE A failed dump that can be restarted.

USAGE

backup status [ <ID> ]
displays all active instances of backup jobs on the filer. For each backup, the backup status command lists the following information:

ID
The unique ID that is assigned to the backup and persists across reboots until the backup completes successfully or is terminated. After that, the ID can be recycled for another backup.

State
The state can either be ACTIVE or RESTARTABLE. ACTIVE state indicates that the process is currently running; RESTARTABLE means the process is suspended and can be resumed.

Type
Either dump or NDMP.

Device
The current device. It is left blank for RESTARTABLE dumps since they are not running and thus do not have a current device.

Start Date The time and date that the backup first started.

Level
The level of the backup.

Path
Points to the tree that is being backed up.

An example of the backup status command output:

 ID State Type Device Start Date Level Path — ———– —- —— ———— —– ————— 0 ACTIVE NDMP urst0a Nov 28 00:22 0 /vol/vol0/ 1 RESTARTABLE dump Nov 29 00:22 1 /vol/vol1/ 

If a specific ID is provided, the backup status command displays more detailed information for the corresponding backup.

backup terminate <ID>
A RESTARTABLE dump, though not actively running, retains a snapshot and other file system resources. To release the resources, user can explicitly terminate a RESTARTABLE dump. Once terminated, it cannot be restarted again.

SEE ALSO

membuang


Table of Contents



Manual Pages , , , ,

autosupport

July 7th, 2009

Table of Contents

NAME

autosupport – notification daemon

SYNOPSIS

Data ONTAP is capable of sending automated notification to Customer Support at Network Appliance and/or to other designated addressees in certain situations. The notification contains useful information to help them solve or recognize problems quickly and proactively. The system can also be configured to send a short alert notification containing only the reason for the alert to a separate list of recipients. This notification is sent only for critical events that might require some corrective action and can be useful for Administrators with alphanumeric pagers that can accept short email messages.

DESCRIPTION

The autosupport mechanism will use SMTP if there are any (user configured) destination email addresses set in the autosupport.to option. If autosupport.support.enable is on then autosupports will also be sent to Network Appliance. Autosupports sent to Network Appliance may be transmitted by SMTP or by HTTP as specified in the autosupport.support.transport option.

If SMTP is used then the autosupport mechanism contacts a mail host that is listening on the SMTP port (25) to send email. A list of up to 5 mailhosts can be specified by using the autosupport.mailhosts option, and they will be accessed in the order specified until one of them answers as a mailhost. It will then send email through the successful mailhost connection to the destination email address specified in the autosupport.to option. Note that the autosupport.to option only allows 5 email address. To send to more than 5 recipients, create a local alias, or distribution list, and add that as the recipient.

If autosupport.support.enable is on then a copy of the autosupport message is also sent to Network Appliance as follows:

If autosupport.support.transport is smtp then the copy of the autosupport is emailed to the destination specified in autosupport.support.to and the same mailhost picking algorithm is used as above.

If autosupport.support.transport is http then a direct connection to the location specified in autosupport.support.url is made and the autosupport is transmitted to Network Appliance via HTTP POST.

The autosupport mechanism is triggered automatically once a week by the kernel to send information before backing up the messages file. It can also be invoked to send the information through the options command. Autosupport mail will also be sent on events that require corrective action from the System Administrator. And finally, the autosupport mechanism will send notification upon system reboot from disk.

To accommodate multiple delivery methods and destinations and to preserve time dependent values, the outgoing autosupport messages are now spooled in /etc/log/autosupport . Autosupport processing will attempt to deliver all (currently undelivered) messages until the autosupport.retry.count has been reached or until subsequent autosupport messages "fill the spool" such that the oldest (undelivered) messages are forced to be dropped. The spool size is currently 40 messages.

The subject line of the mail sent by the autosupport mechanism contains a text string to identify the reason for the notification. The subject also contains a relative prioritization of the message, using syslog severity levels from DEBUG to EMERGENCY (see syslog.conf ). The messages and other information in the notification should be used to check on the problem being reported.

The setup command tries to configure autosupport as follows:

If a mailhost is specified, it adds an entry for mailhost to the /etc/hosts file.

Setup also queries for autosupport.from information.

OPTIONS

Autosupport features are manipulated through the options command (see options ). The available options are as follows:

autosupport.cifs.verbose
If on , includes CIFS session and share information in autosupport messages. If off , those sections are omitted. The default is off .

autosupport.content
The type of content that the autosupport notification should contain. Allowable values are complete and minimal . The default value is complete . The minimal option allows the delivery of a "sanitized" and smaller version of the autosupport, at the cost of reduced support from Network Appliance. Please contact Network Appliance if you feel you need to use the minimal option. The complete option is the traditional (and default) form of autosupport. If this option is changed from complete to minimal then all previous and pending autosupport messages will be deleted under the assumption that complete messages should not be transmitted.

autosupport.doit
Triggers the autosupport daemon to send an autosupport notification immediately. A text word entered as the option is sent in the notification subject line and should be used to explain the reason for the notification.

autosupport.enable
Enables/disables the autosupport notification features (see autosupport ). The default is on to cause autosupport notifications to be sent. This option will override the autosupport.support.enable option.

autosupport.from
Defines the user to be designated as the sender of the notification. The default is postmaster@your.domain . Email replies from Network Appliance will be sent to this address.

autosupport.local.nht_data.enable
Enables/disables the NHT data autosupport to be sent to the recipients listed in the autosupport.to option. NHT data is the binary, internal log data from each disk drive, and in general, is not parsable by other than Network Appliance. There is no customer data in the NHT autosupport. The default for this option is off .

autosupport.local.performance_data.enable
Enables/disables performance data autosupport to be sent to the recipients listed in autosupport.to . The performance autosupport contains hourly samples of system performance counters, and in general is only useful to Network Appliance. The default is off .

autosupport.mailhost
Defines the list of up to 5 mailhost names. Enter the host names as a comma-separated list with no spaces in between. The default is an empty list.

autosupport.minimal.subject.id
Defines the type of string that is used in the identification portion of the subject line when autosupport.content is set to minimal . Allowable values are systemid and hostname . The default is systemid .

autosupport.noteto
Defines the list of recipients for the autosupport short note email. Up to 5 mail addresses are allowed. Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list to disable short note emails.

autosupport.nht_data.enable
Enables/disables the generation of the Health Trigger (NHT) data autosupport. Default is off

autosupport.performance_data.enable
Enables/disables hourly sampling of system performance data, and weekly creation of a performance data autosupport. The default is on .

autosupport.retry.count
Number of times to try resending the mail before giving up and dropping the mail. Minimum is 5; maximum is 4294967295 ; The default is 15 .

autosupport.retry.interval
Time in minutes to delay before trying to send the autosupport again. Minimum is 30 seconds, maximum is 1 day. Values may end with `s', `m' or `h' to indicate seconds, minutes or hours respectively, if no units are specified than input is
assumed to be in seconds. The default value is 4m .

autosupport.support.enable
Enables/disables the autosupport notification to Network Appliance The default is on to cause autosupport notifications to be sent directly to Network Appliance as described by the autosupport.support.transport option. This option is superceded (overridden) by the value of autosupport.enable .

autosupport.support.proxy
Allows the setting of an http based proxy if autosupport.support.transport is https or http . The default
for this option is the empty string, implying no proxy is necessary.

autosupport.support.to
This option is read only; it shows where autosupport notifications to Network Appliance are sent if autosupport.support.transport is smtp .

autosupport.support.transport
Allows setting the type of delivery desired for autosupport notifications that are destined for Network Appliance. Allowed values are https , http (for direct web based posting) or smtp (for traditional email). The default value is https . Note that http and https may (depending on local network configuration) require that the autosupport.support.proxy option be set correctly. Also smtp requires that autosupport.mailhosts be configured correctly before autosupport delivery can be successful.

autosupport.support.url
This option is read only; it shows where autosupport notifications to Network Appliance are sent if autosupport.support.transport is https or http .

autosupport.throttle
Enables autosupport throttling (see autosupport ). When too many autosupports are sent in too short a time, additional messages of the same type will be dropped. Valid values for this option are on or off . The default value for this option is on .

autosupport.to
Defines the list of recipients for the autosupport email notification. Up to 5 mail addresses are allowed. Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list. Note that it is no longer necessary to use the standard Network Appliance autosupport email address in this field to direct autosupport messages to Network Appliance. Please use autosupport.support.enable instead.

CONTENTS

A complete autosupport will contain the following information. Note that some sections are configurable, and/or available depending on what features are licensed. The order given is the general order of appearance in the autosupport message itself.

Generation date and timestamp

Software Version

System ID

Hostname

SNMP contact name (if specified)

SNMP location (if specified)

Partner System ID (if clustered)

Partner Hostname (if clustered)

Cluster Node Status (if clustered)

Console language type

sysconfig -a output

sysconfig -c output

sysconfig -d output

System Serial Number

Software Licenses (scrambled prior to transmission)

Option settings

availtime output

cf monitor all output (if clustered)

ic stats performance output (if clustered with VIA)

ic stats error -v output (if clustered with VIA)

snet stats -v output (if clustered with SNET)

ifconfig -a output

ifstat -a output

vlan stat output

vif status output

nis info output

nfsstat -c output (if licensed)

cifs stat output (if licensed)

cifs sessions summary (if licensed)

cifs sessions output (if licensed and enabled)

cifs shares summary (if licensed)

cifs shares output (if licensed and enabled)

vol status -l (if cifs is licensed)

httpstat output

vfiler status -a output (if licensed)

df output

df -i output

snap sched output

vol status -v output

vol status output

vol status -c output

vol scrub status -v output

sysconfig -r output

fcstat fcal_stats output

fcstat device_map output

fcstat link_stats output

ECC Memory Scrubber Statistics

ems event status output

ems log status output

registry values

perf report -t output

storage show adapter -a output

storage show hub -a output

storage show disk -a output

storage show fabric output

storage show switch output

storage show port output

EMS log file (if enabled)

/etc/messages content

Parity Inconsistancy information

WAFL_check logs

TYPES

The following types of autosupport messages, with their associated severity, can be generated automatically. The autosupport message text is in bold, and the LOG_XXX value is the syslog severity level. Note that text inside of square brackets ([]) is descriptive and is not static for any given autosupport message of that type.

BATTERY_LOW!!!
LOG_ALERT

BMC_EVENT: BUS ERROR
LOG_ERR

BMC_EVENT: POST ERROR
LOG_ERR

CLUSTER DOWNREV BOOT FIRMWARE
LOG_CRIT

CLUSTER ERROR: DISK/SHELF COUNT MISMATCH LOG_EMERG

CLUSTER GIVEBACK COMPLETE
LOG_INFO

CLUSTER TAKEOVER COMPLETE AUTOMATIC
LOG_ALERT

CLUSTER TAKEOVER COMPLETE MANUAL
LOG_INFO

CLUSTER TAKEOVER FAILED
LOG_INFO

CONFIGURATION_ERROR!!!
LOG_ALERT

CPU FAN WARNING - [fan]
LOG_WARNING

DEVICE_QUALIFICATION_FAILED
LOG_CRIT

DISK CONFIGURATION ERROR
LOG_ALERT

DISK RECONSTRUCTION FAILED!!
LOG_ALERT

DISK_FAIL!!! - Bypassed by ESH
LOG_ALERT

DISK_FAIL!!!
LOG_ALERT

DISK_FAILURE_PREDICTED!!!
LOG_ALERT

DISK_FIRMWARE_NEEDED_UPDATE!!!
LOG_EMERG

DISK_IO_DEGRADED
LOG_WARNING

DISK_LOW_THRUPUT
LOG_NOTICE

DISK_RECOVERED_ERRORS
LOG_WARNING

DISK_SCRUB!!!
LOG_EMERG

FC-AL LINK_FAILURE!!!
LOG_ERR

FC-AL RECOVERABLE ERRORS
LOG_WARNING

OVER_TEMPERATURE_SHUTDOWN!!!
LOG_EMERG

OVER_TEMPERATURE_WARNING!!!
LOG_EMERG

PARTNER DOWN, TAKEOVER IMPOSSIBLE
LOG_ALERT

POSSIBLE BAD RAM
LOG_ERR

POSSIBLE UNLINKED INODE
LOG_ERR

REBOOT (CLUSTER TAKEOVER)
LOG_ALERT

REBOOT (after WAFL_check)
LOG_INFO

REBOOT (after entering firmware)
LOG_INFO

REBOOT (after giveback)
LOG_INFO

REBOOT (halt command)
LOG_INFO

REBOOT (internal halt)
LOG_INFO

REBOOT (internal reboot)
LOG_INFO

REBOOT (panic)
LOG_CRIT

REBOOT (power glitch)
LOG_INFO

REBOOT (power on)
LOG_INFO

REBOOT (reboot command)
LOG_INFO

REBOOT (watchdog reset)
LOG_CRIT

REBOOT
LOG_INFO

SHELF COOLING UNIT FAILED
LOG_EMERG

SHELF COOLING UNIT FAILED
LOG_WARNING

SHELF_FAULT!!!
LOG_ALERT

SNMP USER DEFINED TRAP
LOG_INFO

SPARE_FAIL!!!
LOG_ALERT

SYSTEM_CONFIGURATION_CRITICAL_ERROR
LOG_CRIT

SYSTEM_CONFIGURATION_ERROR
LOG_ERR

UNDER_TEMPERATURE_SHUTDOWN!!!
LOG_EMERG

UNDER_TEMPERATURE_WARNING!!!
LOG_EMERG

USER_TRIGGERED ([user input from autosupport.doit]) LOG_INFO

WAFL_check!!!
LOG_ALERT

WEEKLY_LOG
LOG_INFO

[EMS event]
LOG_INFO

[fan] FAN_FAIL!!!
LOG_ALERT

[mini core]
LOG_CRIT

[power supply failure]
LOG_ALERT

[power supply] POWER_SUPPLY_DEGRADED!!!
LOG_ALERT

[shelf over temperature critical]
LOG_EMERG

CLUSTER CONSIDERATIONS

The autosupport email messages from a filer in a cluster are different from the autosupport email messages from a standalone filer in the following ways:

The subject in the autosupport email messages from a filer in a cluster reads, “Cluster notification, ” instead of “System notification.”

The autosupport email messages from a filer in a cluster contains information about its partner, such as the partner system ID and the partner host name.

In takeover mode, if you reboot the live filer, two autosupport email messages notify the email recipients of the reboot: one is from the live filer and one is from the failed filer.

The live filer sends an autosupport email message after it finishes the takeover process.

SEE ALSO

options , partner , setup , hosts , RFC821


Table of Contents






























































Manual Pages , , , ,

auditlog

July 7th, 2009

Table of Contents

NAME

auditlog – contains an audit record of recent administrative activity

SYNOPSIS

<logdir>/auditlog

<logdir> is /etc/log for filers and /logs for NetCache appliances.

DESCRIPTION

If the option auditlog.enable is on, the system logs all input to the system at the console/telnet shell and via rsh to the auditlog file. The data output by commands executed in this fashion is also logged to auditlog. Administrative servlet invocations (via HTTP, typically from FilerView) and API calls made via the ONTAPI interface are also logged to the auditlog. A typical message is:

Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:OUT:date: Wed Feb 9 17:34:09 GMT 2000

This indicates that there was an rsh session around Wed Feb 9 17:34:09 GMT which caused the date command to be executed. The user performing the command was root. The type of log is data output by the system as indicated by the OUT keyword.

Commands typed at the filer's console or executed by rsh are designated by the IN keyword as in:

Wed Feb 9 17:34:03 GMT [rshd_0:auditlog]: :IN:rsh shell: RSH INPUT COMMAND is date

The start and end of an rsh session are specially demarcated as in

Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:START:rsh shell:orbit.eng.mycompany.com

and

Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:END:rsh shell:

The maximum size of the auditlog file is controlled by the auditlog.max_file_size option. If the file gets to this size, it is rotated (see below).

Every Saturday at 24:00, <logdir>/auditlog is moved to <logdir>/auditlog.0, <logdir>/auditlog.0 is moved to <logdir>/auditlog.1 , and so on. This process is called rotation. Auditlog files are saved for a total of six weeks, if they do not overflow.

If you want to forward audit log messages to a remote syslog log host (one that accepts syslog messages via the BSD Syslog protocol specified in RFC 3164), modify the filer's /etc/syslog.conf file to forward messages from the filer's "local7" facility to the remote host. Do this by adding a line like:

local7.*
@1.2.3.4

to /etc/syslog.conf. An IP address has been used here, but a valid DNS name could also be used. Note that using a DNS name can fail if the filer is unable to resolve the name given in the file. If that happens, your messages will not be forwarded.

On the log host, you'll need to modify the syslog daemon's configuration file to redirect syslog message traffic from the "local7" facility to the appropriate configuration file. That is typically done by adding a line similar to the one shown above for the filer:

local7.*
/var/logs/filer_auditlogs

Then restart the daemon on the log host, or send an appropriate signal to it. See the documentation for your log host's syslog daemon for more information on how to make that configuration change.

FILES

<logdir>/auditlog
auditlog file for current week. <logdir>/auditlog.[0-5] auditlog files for previous weeks

SEE ALSO

options , syslog.conf


Table of Contents

Manual Pages , , , ,



This site is not affiliated or sponsored in anyway by NetApp or any other company mentioned within.

Bad Behavior has blocked 2837 access attempts in the last 7 days.

© 2009-2012 Chris Kranz All Rights Reserved
This site is not affiliated or sponsored in anyway by NetApp or any other company mentioned within.