Arkivju

Archive għall-kategorija l-"Paġni Manwal"

Man Paġni NetApp

NetApp jkollhom ġentilment tani permess li jerġgħu jiġu paġni bniedem tagħhom hawn. Huma għad għandhom bżonn ftit żbarazzar, iżda l-kwantità innifisha mezzi li ser tieħu me awhile biex tikseb minnhom kollha magħżula u trans-referenzjata kif suppost, jekk jogħġbok skuża xi kwistjonijiet viżwali għall-mument. I kiteb għodda parsing malajr biex tikseb l-info hawn fuq, u għalhekk jista 'jkun hemm ftit kwistjonijiet li jirriżultaw minn din xorta.

I've always liked the way that PHP have their function pages giving users the ability to comment directly onto them. This allows people to leave feedback on functions and tools, and also follow up with some extra uses or syntax for commands that aren't necessarily clearly published. Hopefully this can feed back into NetApp to improve their documentation.

I'd definitely like to encourage people to comment on the man pages with anything that may be useful, and hopefully build this into a useful little reference section. Many thanks again for the NetApp folk for helping me with this.

VN:F [1.9.11_1134]
Rata din il-kariga:
Rating: 8.8/ 10 (19 votes cast)

Categories: General , Manual Pages Tags: , , , ,

aggr

July 7th, 2009 Chris Kranz No comments

Werrej

ISEM

aggr – commands for managing aggregates, displaying aggregate status, and copying aggregates

Synopsis

aggr command argument …

DESKRIZZJONI

The aggr command family manages aggregates . The aggr commands can create new aggregates, destroy existing ones, undestroy previously destroyed aggregate, manage plexes within a mirrored aggregate, change aggregate status, apply options to an aggregate, copy one aggregate to another, and display their status. Aggregate commands often affect the volume(s) contained within aggregates.

Il-familja kmand aggr huwa ġdid fil Data ONTAP 7.0. Il-familja kmand vol basta kontroll fuq l-mes U tradizzjonali vol_ li mdewba wieħed mill-utent viżibbli fajl tas-sistema u wieħed RAID-livell ħażna tal-kontenituri (aggregati) fi unità indiviżibbli, u għadhom ma. Biex jippermettu użu aktar flessibbli ta 'ħażna, l-aggregati issa wkoll tappoġġja l-kapaċità li jkun fihom, indipendenti multipli utent livell sistemi fajl imsemmi volumi flessibbli.

Data ONTAP 7.0 jappoġġja bis-sħiħ iż-żewġ volumi tradizzjonali u flessibbli. Il-familja kmand aggr huwa l-metodu preferut għall-ġestjoni aggregati a filer, inklużi dawk li huma integrati fil-volumi tradizzjonali.

Innota li ħafna mill-kmandi aggr japplikaw ugwalment għaż-żewġ-tip ta 'aggregati li fiha volumi flessibbli u t-tip li hija strettament marbuta li jiffurmaw volum tradizzjonali. Għalhekk, l-aggregat terminu hija spiss użata hawn biex jirreferi għaż-żewġ klassijiet ta 'ħażna. F'dawk il-każijiet, tipprovdi fil-qosor għal l-itwal u aktar dens frażi "l-aggregati u l-volumi tradizzjonali".

Aggregati jistgħu jew jiġu riflessi jew unmirrored. A plessi hija kopja fiżika tal-ħażna WAFL fi ħdan l-aggregat. A aggregat riflessa tikkonsisti f'żewġ plexes; aggregati unmirrored fihom plessi wieħed. Sabiex jinħoloq aggregat riflessa, irid ikollok konfigurazzjoni filer li jappoġġja RAID-livell riflessjoni. Meta duplikazzjoni hija ppermettiet fuq il-filer, il-diski parts huma maqsuma pools disk tnejn. Meta aggregat huwa maħluq, kollha tal-diski fl-plessi wieħed għandu jiġi mill-pool istess diska, u l-plexes żewġ ta 'aggregat riflessa għandu jikkonsisti diski minn pools separati, għaliex dan jimmassimizza iżolament tort. Din il-politika tista 'tiġi megħluba bil-f-għażla li aggr joħolqu, aggr żid u mera aggr, iżda mhuwiex rakkomandat.

Isem aggregat jista 'jkun fihom ittri, numri, u l-karattru jenfasizzaw (_), iżda l-ewwel karattru għandu jkun ta' ittra jew enfasizzati. A total kombinat ta 'sa 200 aggregati (inklużi dawk inkorporati fil-volumi tradizzjonali) jistgħu jiġu maħluqa fuq kull filer.

A plessi tista 'tkun online jew offline. Jekk huwa offline, ma jkunx disponibbli għall jaqraw jew jiktbu aċċess. Plexes jista 'jkun fil-kombinazzjonijiet ta' l-istati li ġejjin:

normali Il-gruppi kollha RAID fil-kumplessi huma funzjonali.

naqset Mill-inqas wieħed mill-gruppi RAID fil-plessi naqas.

Battal il-plessi hija parti minn aggregat li qed jinħolqu, u wieħed jew aktar mill-diski fil-mira għall-aggregat bżonn li jiġi zeroed qabel qed jiżdiedu mal-plessi.

attiva Il-plessi hija disponibbli għall-użu.

inattivi
Il-plessi ma tkunx disponibbli għall-użu.

resyncing
Kontenut tal-kumplessi bħalissa huma skaduti u huma fil-proċess li jiġu resynchronized mal-kontenut ta 'l-plessi oħra ta' l-aggregat (tapplika għall-aggregati riflessa biss).

diski żżid
Diski qed jiġu miżjuda mal-kumplessi tal-RAID grupp (i).

barra mill-data
Dan l-istat biss jiġri fl-aggregati riflessa fejn wieħed mill-plexes naqas. The plessi mhux naqset se jkunu f'dan l-istat jekk meħtieġa sabiex jiġu resynchronized fil-mument plessi oħra naqset.

A plessi huwa msemmi jużaw l-isem ta 'l-aggregat, il delimetru karattru mmejla, u l-isem tal-plessi. Is-sistema awtomatikament tagħżel ismijiet plessi fil-ħin ħolqien. Per eżempju, l-plessi ewwel maħluqa fl aggr0 aggregat ikun aggr0/plex0.

Aggregat jista 'jkun fuq l-internet, ristretta, jew offline. Meta aggregat offline, l-ebda taqra jew tikteb l-aċċess huwa permess. Meta aggregat huwa ristrett, ċerti operazzjonijiet huma permessi (bħal kopja aggregat, komputazzjoni mill-ġdid jew rikostruzzjoni RAID parità) iżda aċċess għad-data ma jkunx permess. Aggregati li mhumiex parti ta 'volum tradizzjonali tista' biss tkun ristretta jew offlined jekk dawn ma jkunx fihom kull volum flessibbli.

Aggregati jista 'jkun fil-kombinazzjonijiet ta' l-istati li ġejjin:

aggr L-aggregat huwa aggregat moderna ta 'kuljum; huwa jista' jesa 'żero jew aktar volumi flessibbli.

ikkupjar
L-aggregat hija attwalment l-aggregat mira ta 'operazzjoni kopja attiva aggr.

degradati
L-aggregat ikun fih mill-inqas wieħed degradati raid grupp li ma jkunx qed rikostruwit.

barranin
-Diski li l-aggregat fih tmexxew għall-filer attwali minn Stat filer.

tkabbir
Diski huma fil-proċess li jiġu miżjuda ma 'l-aggregat.

initializing
L-aggregat huwa fil-proċess li tiġi initialized.

invalida
L-aggregat fiha l-ebda volumi u l-ebda jistgħu jiġu miżjuda. Tipikament, dan jiġri biss wara operazzjoni kopja abortiti aggregat.

mogħdija
Kontroll konsistenza WAFL jkun qed isir dwar dan l-aggregat.

mera degradata
L-aggregat huwa aggregat riflessa, u wieħed mill plexes tagħha huwa offline jew resyncing.

riflessa
L-aggregat huwa rifless u kollha ta 'gruppi RAID tagħha huma funzjonali.

bżonnijiet verifika
Kontroll konsistenza WAFL jeħtieġ li jitwettqu fuq il-aggregat.

parzjali
Mill-inqas wieħed disk instab għall-aggregat, imma tnejn jew aktar diski huma nieqsa.

raid0 L-aggregat jikkonsisti RAID-0 (l-ebda parità) gruppi RAID (V-Serje u NetCache biss).

raid4 L-aggregat tikkonsisti minn gruppi RAID RAID-4.

raid_dp
L-aggregat jikkonsisti RAID-DP (Parità Double) gruppi RAID.

tibni mill-ġdid
Mill-inqas wieħed RAID grupp b'kollox qed rikostruwit.

direzzjoni ġdida
Riallokazzjoni aggregat jew rijallokazzjoni fajl bl-p-għażla ġiet mibdija fuq l-aggregat. Aqra prestazzjoni għal volumi b'kollox tista 'tiġi degradata.

resyncing
Wieħed mill-plexes ta 'aggregat riflessa qed resynchronized.

snapmirrored
L-aggregat huwa r-replika ta 'snapmirrored ieħor aggregat. Dan l-istat tista 'tinħoloq biss jekk il-medja hija parti ta' volum tradizzjonali.

trad L-aggregat huwa magħluq ma 'volum wieħed. Dan huwa wkoll referut bħala volum tradizzjonali u huwa eżattament ekwivalenti għall-volumi li kienet teżisti qabel tad-Data OnTAP 7.0. Volumi flessibbli ma tistax tiġi maħluqa fl-intern ta 'dan l-aggregat.

verifika
A RAID mera verifika operazzjoni bħalissa qed jimxu fuq il-aggregat.

wafl inkonsistenti
L-aggregat tkun ġiet immarkata korrotta. Jekk jogħġbok ikkuntattja Customer Support jekk tara xi aggregat f'dan l-istat.

UŻU

Il-kmandijiet li ġejjin huma disponibbli fis-suite aggr:

  żid mera jillimitaw undestroy kopja Scrub offline tivverifika joħolqu show_space onlajn jeqirdu għażliet maqsuma media_scrub istatus semmi mill-ġdid 

aggr żid aggrname
[F ']
[N]
['G {raidgroup | ġdid | Kollha}]
{Ndisks [@ daqs]
|
D-Disk1 [disk2 ... ] [D-diskn [diskn 1 ... ]]}

Iżżid diski għall-aggrname aggregat msemmija. Speċifika l-diski bl-istess mod kif għall-kmand aggr joħolqu. Jekk l-aggregat huwa rifless, allura l-argument għandu d jintuża darbtejn (jekk xejn).

Jekk il-g-għażla ma tkunx użata, il-diski huma miżjuda mal-aktar reċentement ħolqot grupp Util RAID huwa sħiħ, u mbagħad wieħed jew aktar gruppi RAID ġodda huma maħluqa u l-diski li fadal huma miżjuda ma 'gruppi ġodda. Gruppi oħra eżistenti RAID li mhumiex sħiħa jibqgħu parzjalment mimli.

-G-għażla tippermetti ispeċifikazzjoni ta 'grupp RAID (per eżempju, rg0) li l-diski indikat għandu jkun miżjud, jew metodu li bih il-diski huma miżjuda mal-gruppi RAID ġodda jew eżistenti.

Jekk il-g għażla tkun użata sabiex tispeċifika grupp RAID, dak il-grupp RAID irid ikun diġà jeżistu. L-diski huma miżjuda ma 'dik Util grupp RAID huwa sħiħ. Kull diski li fadal huma injorati.

Jekk il-g-għażla huwa segwit mill-ġdid, tad-Data ONTAP toħloq grupp wieħed jew aktar RAID ġodda u żżid l-diski li, anki jekk il-diski jkunu tajbin fi grupp RAID eżistenti. Xi gruppi RAID eżistenti li mhumiex sħiħa jibqgħu parzjalment mimli. L-isem tal-gruppi RAID ġodda huma magħżula awtomatikament. Mhuwiex possibbli li jiġu speċifikati l-ismijiet għall-gruppi RAID ġodda.

Jekk il-g-għażla hija segwita minn dawk kollha, tad-Data ONTAP żżid il-diski speċifikat għall-gruppi RAID eżistenti ewwel. Wara l-gruppi kollha RAID eżistenti huma sħiħa, joħloq grupp wieħed jew aktar RAID ġodda u żżid l-diski speċifikat għall-gruppi ġodda.

-N-għażla jistgħu jintużaw biex juru l-kmand li s-sistema għandha tesegwixxi, mingħajr ma attwalment tagħmel xi modifiki. Dan huwa utli għall-wiri-diski awtomatikament magħżula, per eżempju.

Konvenzjonalment, l-filer jimla grupp RAID wieħed ma diski qabel ma tibda grupp ieħor RAID. Ejja ngħidu aggregat bħalissa għandha wieħed RAID grupp ta '12 diski u d-daqs tal-grupp RAID huwa 14. Jekk inti żid 5 diski għal dan l-aggregat, se jkollhom waħda RAID grupp ma '14 diski u grupp ieħor RAID bi 3 diski. The filer ma indaqs jiddistribwixxu diski fost gruppi RAID.

Inti ma tista 'żżid diski għal aggregat riflessa jekk waħda mill-plexes offline.

L-diski fil-kumplessi mhumiex permessi li jivvjaġġaw pools disk. Din l-imġiba tista 'tiġi megħluba bil-f-bandiera meta jintuża flimkien ma' l-argument li d lista diski li żżid. -F-bandiera, flimkien ma 'd, jista' jintuża wkoll għall-seħħ żżid diski li jkollhom veloċità rotazzjonali li ma taqbilx ma 'dik tal-maġġoranza ta' diski eżistenti fl-aggregat.

aggr kopja abort [-h] operation_number | kollha

Itemm l-operazzjonijiet kopja aggregat. The opera_ t parametru ion_number jispeċifika li l-operazzjoni li jittermina. Jekk inti tispeċifika kollha, l-operazzjonijiet kollha aggregat kopja attivi jiġu tterminati.

aggr kopja tibda
[-S |-i stampa] [-C]
destinazzjoni sors

Kopji data kollha, inklużi Snapshots u l-volumi flessibbli, minn aggregat għall-ieħor. Jekk il-bandiera l-S huwa użat, il-kmand kopji kollha Snapshots fl-aggregat għajn sa l-aggregat destinazzjoni. Li tispeċifika stampa partikolari li kopja, uża l-i-bandiera segwit bl-isem ta 'l-istampa. Jekk tuża la l-S lanqas-i bandiera fil-kmand, il-filer toħloq stampa fil-ħin meta l-kmand aggr bidu kopja hija esegwita u l-kopji biss li stampa lill-aggregat destinazzjoni.

L-emendament C-bandiera huwa meħtieġ jekk it-total sors kellu-ispazju ħieles deframmentazzjoni li jsiru fuqu, jew jekk l-aggregat destinazzjoni ser ikun ħieles ispazju defragmented. Free-ispazju deframmentazzjoni jistgħu jitwettqu fuq aggregat użu tal-kmand talloka mill-ġdid.

Kopji aggregata tista 'titwettaq biss bejn l-aggregati li jospita volumi flessibbli. Aggregati li huma integrati fil-volumi tradizzjonali ma jistgħux jipparteċipaw.

L-aggregati sors u destinazzjoni jista 'jkun fuq il-filer istess jew filers differenti. Jekk is-sors jew destinazzjoni aggregat huwa fuq filer differenti minn dak li inti tidħol fil-kmand aggr bidu kopja, speċifika l-isem aggregat fil-filer_name: Format aggre_ ate_name ġ.

The filers involuti fi kopja aggregat għandu jissodisfa l-ħtiġiet li ġejjin għall-kmand aggr jibdew kopja li għandhom jitlestew b'suċċess:

L-aggregat għajn għandha tkun fuq l-internet u l-aggregat destinazzjoni għandu jkun ristrett.

Jekk il-kopja hija bejn żewġ filers, kull filer għandhom jiġu definiti bħala ospitanti fdati mill-filer oħra. Dan huwa, isem il-filer trid tkun fil-eċċ / / hosts.equiv fajl tal-filer oħra.

Jekk il-kopja hija fuq il-filer istess, localhost għandhom jiġu inklużi fil-filer tal-/ etc / hosts.equiv fajl. Ukoll, l-indirizz loopback għandu jkun fil-filer ta / etc / hosts fajl. Inkella, il-filer ma tistax tibgħat pakketti għalih innifsu permezz tal-indirizz loopback meta jippruvaw kopja tad-data.

L-ispazju disk użabbli tal-aggregat destinazzjoni għandu jkun akbar minn jew ugwali għall-disk ispazju utilizzabbli ta 'l-aggregat sors. Uża l-DF-A kmand pathname biex tara d-ammont ta 'spazju disk użabbli ta' aggregat partikolari.

Kull kmand aggr tibda kopja tiġġenera żewġ operazzjonijiet aggregat kopja: waħda għall-qari tad-data mis-sors aggregata u waħda għall-kitba tad-data għall-aggregat destinazzjoni. Kull filer jappoġġja sa erba 'operazzjonijiet simultanji kopja aggregat.

aggr istatus kopja [operation_number]

Juri l-progress ta 'wieħed jew l-operazzjonijiet kollha kopja aggr. L-operazzjonijiet huma numerati mill 0 sa 3.

Nerġgħu informazzjoni punt ta 'kontroll għal kull trasferiment hija wkoll murija.

aggr kopja throttle [operation_number] Valur

Jikkontrolla l-prestazzjoni ta 'l-operazzjoni kopja aggr. Il-valur tvarja minn 10 (veloċità sħiħa) sa 1 (wieħed minn għaxra ta 'veloċità sħiħa). Il-valur standard jinżamm fl-għażla aggr.copy.throttle the filer u huwa stabbilit 10 (veloċità sħiħa) fil-fabbrika. Inti tista 'tapplika l-valur ta' prestazzjoni għal operazzjoni speċifikat mill-parametru operation_number. Jekk inti ma jispeċifikawx numru kooperazzjoni fil-kmand aggr throttle kopja, il-kmand tapplika għall-operazzjonijiet kollha kopja aggr.

Uża dan il-kmand li jillimita l-veloċità ta 'l-operazzjoni kopja aggr jekk tissuspetta li l-operazzjoni kopja aggr qed tikkawża problemi ta' prestazzjoni fuq filer tiegħek. B'mod partikolari, it-throttle hija mfassla biex tgħin tillimita l-użu CPU tal-operazzjoni kopja aggr. Ma jistax jintuża biex tirfina mudelli netwerk konsum bandwidth.

Il-kmand tat-throttle aggr kopja biss jgħinuk biex jistabilixxu l-veloċità ta 'operazzjoni kopja aggr li tkun għaddejja. Biex tissettja l-inadempjenza aggr kopja ta 'veloċità li għandu jintuża mill-operazzjonijiet kopja futuri, uża l-kmand għażliet li tiffissa l-għażla aggr.copy.throttle.

aggr joħolqu aggrname
[F ']
[M]
[N]
[-T raidtype]
[Raidsize-r]
[T-diska tat-tip]
[R rpm]
[L-[konformità | intrapriża]]
[-V]
[L-lingwa tal-kodiċi]
{Ndisks [@ daqs]

|
D-Disk1 [disk2 ... ] [D-diskn [diskn 1 ... ]]}

Joħloq sistema ġdida aggrname aggregata msemmija. L-isem aggregat jista 'jkun fihom ittri, numri, u l-karattru jenfasizzaw (_), iżda l-ewwel karattru għandu jkun ta' ittra jew enfasizzati. Sa 200 aggregati jistgħu jiġu maħluqa fuq kull filer. Dan in-numru jinkludi dawk l-aggregati li jinsabu fi ħdan il-volumi tradizzjonali.

Aggregat integrati jistgħu jinħolqu bħala parti ta 'volum tradizzjonali bl-użu tal vs-għażla. Ma jistax ikun fihom kull volum flessibbli.

A aggregat regolari, maħluqa mingħajr il-vs-għażla, jista 'jkun fihom biss volumi flessibbli. Ma jistax jiġi inkorporat fis-volum tradizzjonali, u fih l-ebda volumi immedjatament wara l-ħolqien. Volumi flessibbli ġdida tista 'tkun maħluqa bl-użu tal-kmand joħolqu vol.

L-argument t raidtype tispeċifika t-tip ta 'RAID grupp (i) li għandhom jintużaw biex joħolqu l-aggregat. It-tipi possibbli grupp RAID huma raid4 għal RAID-4, raid_dp għal RAID-DP (Parità Double), u raid0 għall striping sempliċi mingħajr protezzjoni parità. The raidtype default għall-aggregati u l-volumi tradizzjonali fuq filers huwa raid_dp. Twaqqif tal-raidtype mhux permess fuq il-V-Serje sistemi; in-nuqqas tat raid0 huwa dejjem użat.

-R-argument raidsize jispeċifika n-numru massimu ta 'diski f'kull grupp RAID fl-aggregat. Il-valuri massimi u nuqqas ta 'raidsize huma pjattaforma dipendenti, ibbażata fuq il-prestazzjoni u l-konsiderazzjonijiet affidabbiltà. Tara l-għażliet aggr raidsize għal aktar dettalji.

It-T-diska tat-tip l-argument tispeċifika t-tip ta 'diski li jużaw meta jinħoloq aggregat ġdid. Huwa meħtieġ biss fuq is-sistemi konnessi ma 'diski ta' tipi differenti. Tipi disk possibbli huma: ATA, FCAL, Lun, SAS, SATA, u SCSI. Diski It-taħlit ta 'tipi differenti wieħed aggregat mhux permess.' T ma jistax jintuża flimkien ma 'd.

Tip disk jidentifika teknoloġija disk u t-tip konnettività. ATA jidentifika diski ATA ma 'jew IDE jew serial interface ATA fl-ixkafef konnessi FCAL (Kanal Fibra arbitraġġ Loop). FCAL jidentifika diski FC fl-ixkafef konnessi FC AL. Lun tidentifika diski virtwali esportati mill- matriċi estern tal-ħażna. It-teknoloġija disk sottostanti u t-tip RAID jiddependi mill-implimentazzjoni ta 'arrays tali ħażna esterna. SAS tidentifika Serial MehmuŜ SCSI diski fl-ixkafef tqabbil. SATA tidentifika diski tas-serje ATA fl-ixkafef SAS. SCSI stands għall-Interface tas-Sistema Żgħar Kompjuter, u hija inkluża għall-kompatibilità b'lura ma 'teknoloġiji disk preċedenti.

Il-R argument rpm tispeċifika t-tip ta 'diski għall-użu bbażat fuq il-veloċità tar-rotazzjoni tagħhom f'dawriet fil-minuta (rpm). Huwa meħtieġ biss fuq is-sistemi li jkollhom diski ma 'veloċitajiet rotazzjonali differenti. Valuri tipiċi għall-veloċità rotazzjonali huma 5400, 7200, 10000, u 15000. R ma jistgħux jintużaw flimkien ma 'd.

ndisks huwa n-numru ta 'diski b'kollox, inklużi l-diski parità. L-diski fl-dan l-aggregat ġodda ġejjin mill-grupp ta 'diski żejda. L-diski iżgħar din il-ġabra jissieħbu fl-aggregat ewwel, sakemm inti tispeċifika l-argument daqs @. D-daqs huwa d-daqs disk GB, u diski li huma sa 10% tad-daqs speċifikati se jkunu magħżula għall-użu fl-aggregat.

-M-għażla jista 'jiġi użat biex jispeċifika li l-aggregat ġodda jiġu riflessi (għandhom żewġ plexes) fuq ħolqien. Jekk din l-għażla huwa mogħti, allura l-diski indikati se jkunu maqsuma madwar l-plexes tnejn. Konvenzjonalment, l-aggregat ġodda mhux se jkunu riflessi.

-N-għażla jistgħu jintużaw biex juru l-kmand li s-sistema għandha tesegwixxi, mingħajr ma attwalment tagħmel xi modifiki. Dan huwa utli għall-wiri-diski awtomatikament magħżula, per eżempju.

Jekk inti tuża l-Disk1 d [disk2 ... ] Argument, il-filer joħloq l-aggregat mal-diski żejda speċifikat Disk1, disk2, u l-bqija. Tista 'tispeċifika lista fl-ispazju separata ta' ismijiet disk. Żewġ listi separati għandhom ikunu speċifikati jekk it-total l-ġdida hija riflessa. Fil-każ li l-aggregat ġdid huwa rifless, il-diski indikati għandhom twassal għal numru ugwali ta 'diski fuq kull plessi ġodda.

L-diski fil-plessi mhumiex permessi li jivvjaġġaw pools żejda. Din l-imġiba tista 'tiġi megħluba bil-f-għażla. L-istess għażla jista 'jintuża wkoll għall-seħħ bl-użu ta diski li ma jkollhomx tqabbil veloċità rotazzjonali. -F-għażla għandha effett biss meta użat ma 'l-għażla li tispeċifika d diski għall-użu.

Biex jinħoloq aggregat SnapLock, tispeċifika l-L-bandiera ma 'l-aggr joħolqu kmand. Din il-bandiera hija biss appoġġjati jekk jew Konformità SnapLock jew SnapLock Intrapriża hija liċenzjata. It-tip ta 'l-aggregat SnapLock maħluqa, jew Konformità jew Intrapriża, huwa ddeterminat mil-liċenzja SnapLock installat. Jekk iż-żewġ Konformità SnapLock u l-Intrapriża SnapLock huma liċenzjati, uża L konformità jew 'L-intrapriża li tispeċifika t-tip aggregat mixtieqa.

L-l-argument language_code jista 'jintuża biss meta jinħoloq volum tradizzjonali li jużaw l-għażla' vs. The filer joħloq il-volum tradizzjonali mal-lingwa speċifikata mill-kodiċi tal-lingwa. Il-mankanza huwa l-lingwa użata mill-volum għerq il-filer tal. Ara l-vol paġna bniedem għal lista ta 'kodiċijiet tal-lingwa.

aggr jeqirdu {aggrname | plexname} [f ']

Jeqred l-aggrname aggregata msemmija, jew il-plexname plessi msemmija. Innota li jekk l-aggregat speċifikat huwa marbut ma 'volum tradizzjonali, allura l-volum tradizzjonali nnifisha hija meqruda ukoll.

Jekk aggregat huwa speċifikat, l plexes fit-total huma meqruda. L-aggregat imsemmija trid ukoll jkunx fihom xi volumi flessibbli, irrispettivament mill-istat impunjazzjoni tagħhom (onlajn, ristretta, jew offline). Jekk plessi hija speċifikata, il-plessi hija meqruda, li jħallu volum unmirrored aggregat jew tradizzjonali li fihom l-plessi li jifdal. Qabel ma jeqirdu l-aggregat, il-volum tradizzjonali jew plessi, l-utent huwa imħeġġa biex jikkonfermaw l-operazzjoni. -F-bandiera jista 'jintuża biex jeqred aggregat, volum tradizzjonali jew kumplessi mingħajr tħeġġeġ l-utent.

-Diski oriġinarjament fl-oġġett meqruda jsiru diski żejda. Biss aggregati offline, il-volumi tradizzjonali u plexes jistgħu jiġu meqruda.

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

Prints l-istatus scrubbing tal-midja ta 'l-aggregati msemmija, plessi, jew grupp. Jekk l-ebda isem huwa mogħti, allura l-istatus huwa stampat għall-gruppi kollha RAID bħalissa għaddej Scrub midja. L-istatus tinkludi persentaġġ kompleta u jekk huwa sospiż.

Il-V-bandiera juri d-data u l-ħin li fih l-midja kollha aħħar Scrub tlestew, id-data u l-ħin meta l-istanza attwali tal-midja iscrubbing beda, u l-istatus attwali ta 'l-aggregat jismu, plessi, jew grupp. Jekk l-ebda isem huwa mogħti, dan l-istatus verbose aktar huwa stampat għall-gruppi kollha RAID ma Scrubs midja attiva.

aggr mera aggrname
[F ']
[N]
[-V victim_aggrname]
[-D Disk1 [disk2 ... ]]

Dawriet aggregat unmirrored fi aggregat riflessa billi żżid plessi lilha. The kumplessi hija jew għadha kemm ġiet iffurmata minn diski magħżula minn grupp ta 'rikambju, jew, jekk il-vs-għażla huwa speċifikat, hija meħuda minn Stat aggregat unmirrored eżistenti. Aggrname aggregat għandu attwalment ikunu unmirrored. Uża aggr joħolqu biex tagħmel ġdid, li jirriflettu ruħhom aggregat mill-bidu.

Diski jista 'jkun speċifikat b'mod espliċitu billi jintuża d-bl-istess mod kif il-joħolqu aggr u l-kmandi aggr żid. In-numru ta 'diski indikati għandhom jaqblu man-numru preżenti fuq il-aggregat eżistenti. L-diski speċifikati m'humiex permessi li jivvjaġġaw pools disk. Din l-imġiba tista 'tiġi megħluba bil-f-għażla. -F 'għażla, flimkien ma' d, jista 'jintuża wkoll għall-seħħ bl-użu ta diski li jkollhom veloċità rotazzjonali li ma taqbilx ma' dik tal-maġġoranza ta 'diski eżistenti fl-aggregat.

Jekk diski mhumiex speċifikati b'mod espliċitu, allura diski huma awtomatikament magħżula biex jaqblu ma 'dawk fil plessi eżistenti l-aggregat tal.

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.

A number of operations being performed on the aggregate's traditional volume can prevent aggr offline from succeeding, for various lengths of time. If such operations are found, there will be a one-second wait for such operations to finish. If they do not, the command is aborted.

A check is also made for files in the aggregate's associated traditional volume opened by internal ONTAP processes. The command is aborted if any are found.

aggr online { aggrname | plexname }
[ -f ]

Brings the aggregate named aggrname (or the plex named plexname ) online. This command takes effect immediately. If the specified aggregate is embedded in a traditional volume, the volume is also also brought online.

If an aggrname is specified, it must be currently offline, restricted, or foreign. If the aggregate is foreign, it will be made native before being brought online. A “foreign” aggregate is an aggregate that consists of disks moved from another filer and that has never been brought online on the current filer. Aggregates that are not foreign are considered “native.”

If the aggregate is inconsistent, but has not lost data, the user will be cautioned and prompted before bringing the aggregate online. The -f flag can be used to override this behavior. It is advisable to run WAFL_check (or do a snapmirror initialize in case of an aggregate embedded in a traditional volume) prior to bringing an inconsistent aggregate online. Bringing an inconsistent aggregate online increases the risk of further file system corruption. If the aggregate is inconsistent and has experienced possible loss of data, it cannot be brought online unless WAFL_check (or snapmirror initialize in the embedded case) has been run on the aggregate.

Jekk plexname huwa speċifikat, il-plessi għandhom ikunu parti minn aggregat riflessa fuq l-internet. The system will initiate resynchronization of the plex as part of online processing.

aggr options aggrname [ optname optval ]

Displays the options that have been set for aggregate aggrname , or sets the option named optname of the aggregate named aggrname to the value optval . The command remains effective after the filer is rebooted, so there is no need to add aggr options commands to the /etc/rc file. Some options have values that are numbers. 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

This option only applies to aggregates that are embedded in traditional volumes. It causes the file system to remain the same size and not grow or shrink when a SnapMirrored volume relationship is broken, or an aggr add is performed on it. This option is automatically set to be on when a traditional volume becomes a SnapMirrored volume. It will remain on after the snapmirror break command is issued for the traditional volume. This allows a traditional volume to be SnapMirrored back to the source without needing to add disks to the source traditional volume. If the traditional volume size is larger than the file system size, turning off this option will force the file system to grow to the size of the traditional volume. The default setting is off .

ignore_inconsistent on | off

This command can only be used in maintenance mode. If this option is set, it allows the aggregate containing the root volume to be brought online on booting, even though it is inconsistent. The user is cautioned that bringing it online prior to running WAFL_check or wafliron may result in further file system inconsistency.

nosnap on | off

If this option is on , it disables automatic snapshots on the aggregate. The default setting is off .

raidsize number

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.

Valuri legali għal din l-għażla tiddependi fuq raidtype. Per eżempju, raid_dp jippermetti gruppi akbar RAID minn raid4. Limiti u valuri awtomatiċi huma wkoll differenti għal tipi differenti ta 'apparat filer u tipi differenti ta' diski. Tabelli li ġejjin jiddefinixxu l-limiti u valuri awtomatiċi għall-raidsize.

  -------------- Raid4 raidsize inadempjenza min max -------------- R100 2 8 8 R150 2 6 6 FAS250 2 7 14 oħra (diski FCAL) 2 8 14 oħra (diski ATA) 2 7 7 -------------- -------------- raid_dp mass raidsize inadempjenza min ------ -------- R100 3 12 12 R150 3 12 16 oħra (diski FCAL) 3 16 28 oħra (diski ATA) 3 14 16 ---------- ---- 

Dawk il-valuri jistgħu jinbidlu fi stqarrijiet għall-futur ta 'ONTAP tad-Data.

raidtype raid4 | raid_dp | raid0

Settijiet tat-tip ta 'RAID jintuża biex jipproteġi kontra disk fallimenti. Użu ta 'raid4 tipprovdi wieħed parità diska RAID għal kull grupp, filwaqt li raid_dp jipprovdi żewġ. Nibdlu din l-għażla immedjatament bidliet RAID-tip tal-gruppi kollha RAID fi ħdan l-aggregat. Meta l-aġġornament gruppi RAID minn raid4 għal raid_dp, kull grupp RAID jibda rikostruzzjoni fuq disk żejda allokati għat-tieni `dparity diska parità".

Nibdlu din l-għażla wkoll bidliet raidsize għal valur aktar adattati għal raidtype ġodda. Meta aġġornament minn raid4 għal raid_dp, raidsize se jiżdied il-valur awtomatiċi għall-raid_dp. Meta degrad minn raid_dp għal raid4, raidsize se tonqos id-daqs tal-grupp RAID akbar eżistenti jekk huwa bejn il-valur ta 'default u l-limitu għall raid4. Jekk il-grupp RAID akbar huwa ogħla mil-limitu għall raid4, il-raidsize ġdid se jkun dak il-limitu. Jekk il-grupp RAID akbar huwa inqas mill-valur ta 'default għall raid4, il-raidsize ġdida se jkun il-valur awtomatiku. Jekk raidsize hija diġà taħt il-valur awtomatiċi għall raid4, se jkun imnaqqas b '1.

numru resyncsnaptime

Din l-għażla jintuża biex titwaqqaf il-mera resynchronization stampa frekwenza (f'minuti). Il-valur ta 'default 60 minuta.

għeruq

Jekk din l-għażla huwa stabbilit fuq volum tradizzjonali, allura l-effett huwa identiku bħal dak definit fil vol paġna bniedem. Inkella, jekk din l-għażla huwa stabbilit fuq aggregat kapaċi li jkun fiha volumi flessibbli, allura li l-aggregat huwa mmarkat bħala dak li se tinkludi wkoll il-volum għerq flessibbli fuq il-reboot li jmiss. Din l-għażla jista 'jintuża fuq wieħed biss minn volum aggregat jew tradizzjonali fi kwalunkwe ħin partikolari. L-aggregat għerq eżistenti jew volum tradizzjonali ser issir entità non-għerq wara l-reboot.

Sakemm is-sistema huwa fasslu, l-aggregat oriġinali u / jew il-volum tradizzjonali se tkompli turi għerq bħala waħda mill-għażliet tagħha, u l-aggregat għerq ġdid jew volum tradizzjonali se juri diskroot bħala għażla. B'mod ġenerali, l-aggregat li għandu l-għażla diskroot huwa dak li se jkun fiha l-volum għerq flessibbli li jsegwi l-reboot li jmiss.

L-uniku mod sabiex jitneħħew l-istatus għerq ta 'volum aggregat jew tradizzjonali huwa li jiġu stabbiliti l-għażla għerq fuq ieħor volum aggregat jew tradizzjonali.

snaplock_compliance

Dan jaqra unika għażla jindika li l-aggregat huwa aggregat Konformità SnapLock. Aggregati jistgħu jiġu indikati biss aggregati Konformità SnapLock fil-ħin ħolqien.

snaplock_enterprise

Dan jaqra unika għażla jindika li l-aggregat huwa aggregat Intrapriża SnapLock. Aggregati jistgħu jiġu indikati biss aggregati Intrapriża SnapLock fil-ħin ħolqien.

snapmirrored barra

Jekk SnapMirror hija ppermettiet għal volum tradizzjonali (SnapMirror ma hija sostnuta għall-aggregati li fihom volumi flessibbli), il-filer awtomatikament settijiet din l-għażla fuq. Issettja din l-għażla off jekk SnapMirror m'għadux jintuża biex taġġorna l-mera volum tradizzjonali. Wara li stabbiliet din l-għażla għal off, il-mera isir volum regolari tradizzjonali writable. Din l-għażla jista 'jiġi ffissat biss għal off; biss il-filer jistgħu jbiddlu l-valur ta' din l-għażla mill-off li fuq.

snapshot_autodelete fuq | off

This option is used to set whether snapshot are automatically deleted in the aggr. If set to on then snapshots may be deleted in the aggr to recover storage as necessary. If set to off then snapshots in the aggr are not automatically deleted to recover storage. Note that snapshots may still be deleted for other reasons, such as maintaining the snapshot schedule for the aggr, or deleting snapshots that are associated with specific operations that no longer need the snapshot. To allow snapshots to be deleted in a timely manner the number of aggr snapshots is limited when snapshot_autodelete is enabled. Because of this, if there are too many snapshots in an aggr then some snapshots must be deleted before the snapshot_autodelete option can be enabled.

aggr rename aggrname newname

Renames the aggregate named aggrname to newname . If this aggregate is embedded in a traditional volume, then that volume's name is also changed.

aggr restrict aggrname
[ -t cifsdelaytime ]

Put the aggregate named aggrname in restricted state, starting from either online or offline state. The command takes effect before returning.

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

If the aggregate is embedded in a traditional volume that has CIFS shares, users should be warned before restricting the aggregate (and hence the entire traditional volume). 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.

aggr scrub resume [ aggrname | plexname | groupname ]

Resumes parity scrubbing on the named aggregate, plex, or group. If no name is given, resume all RAID groups currently undergoing a parity scrubbing that has been suspended.

aggr scrub start [ aggrname | plexname | groupname ]

Starts parity scrubbing on the named online aggregate. Parity scrubbing compares the data disks to the parity disk(s) in their RAID group, correcting the parity disk's contents as necessary. If no name is given, parity scrubbing is started on all online aggregates. If an aggregate name is given, scrubbing is started on all RAID groups contained in the aggregate. If a plex name is given, scrubbing is started on all RAID groups contained in the plex.

aggr scrub status [ 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.

tieqaf Scrub aggr [aggrname | plexname | groupname]

Waqfiet scrubbing parità fuq l-aggregat jismu, plessi, jew grupp; jekk l-ebda isem huwa mogħti, lill-gruppi kollha RAID bħalissa għaddejja minn iscrubbing parità.

Scrub aggr tissospendi [aggrname | plexname | groupname]

Tissospendi scrubbing parità fuq l-aggregat jismu, plessi, jew grupp; jekk l-ebda isem huwa mogħti, lill-gruppi kollha RAID bħalissa għaddejja iscrubbing parità.

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

Juri l-użu l-ispazju fl-aggregat. B'differenza df, dan il-kmand turi l-użu spazju għal kull volum flessibbli fi ħdan aggregat Jekk aggrname huwa speċifikat, aggr show_space biss timxi fuq il-aggregati li jikkorrespondu, inkella rapporti użu spazju fuq l-aggregati.

Daqsijiet kollha huma rrappurtati 1024 bytes blokki, sakemm ma jkunx mitlub minn wieħed mill-h-,-k, m-,-g, jew ta 'għażliet t. Il-K-, m-,-g, u l-għażliet t skala kull qasam marbuta mad-daqs tal-bejgħ li għandu jiġi espress kilobytes, megabytes, gigabytes, jew ta'Terabytes rispettivament.

It-terminoloġija li ġej huwa użat mill-kmand fir-rappurtar ispazju.

      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 ]

Tneħħi plexname minn aggregat riflessa u toħloq unmirrored ġdid aggrname aggregata msemmija li fiha l-plessi. L-aggregat riflessi oriġinali isir unmirrored. The plessi li tkun maqsuma minn l-aggregat oriġinali għandha tkun funzjonali (mhux parzjali), iżda tista 'tkun inattivi, resyncing, jew outof-data. Maqsuma aggr jistgħu għalhekk jintużaw biex jinkiseb aċċess għal plessi li mhix aġġornata fir-rigward plessi msieħba tagħha, jekk plessi sħab tagħha bħalissa fallew.

Jekk l-aggregat jirrisjedi plexname li fihom hu mdaħħal fil-volum tradizzjonali, maqsuma aggr iġib ruħu b'mod identiku għall-volum maqsuma. L-aggregat ġdid huwa inkorporat fil-volum tradizzjonali ġdid ta 'l-istess isem.

Jekk l-aggregat jirrisjedi plexname fejn fih eżattament volum wieħed flessibbli, maqsuma aggr se awtomatikament semmi mill-ġdid l-immaġini volum flessibbli fil-plessi qasma-off li tkun l-istess bħall-aggregat ġodda.

Jekk l-aggregat jirrisjedi plexname fejn fih aktar minn volum wieħed flessibbli, huwa meħtieġ li jiġi speċifikat kif l-isem l-volumi fl-aggregat ġodda li jirriżultaw mill-qasma. -R-għażla tista 'tintuża ripetutament biex jagħti kull volum flessibbli fl-aggregat li jirriżulta isem ġdid. Barra minn hekk, l-għażla i jistgħu jintużaw biex jispeċifikaw suffiss li huwa miżjud fl-aħħar ta 'l-ismijiet volum flessibbli ma jkunux koperti minn-r.

Jekk it-total oriġinali huwa ristrett fil-waqt tal-qasma, l-aggregat li jirriżulta se jkun ristrett. Jekk l-aggregat ristrett qed tospita volumi flessibbli, huma ma semmiet fil-waqt tal-qasma. Volumi flessibbli se jingħata l-isem iktar tard, meta l-kunflitt isem jinstab filwaqt li jinġiebu online aggregat. Volumi flessibbli fit-total li jittella 'online ewwel jżommu l-ismijiet tagħhom. Li l-aggregat jista 'jkun jew it-total oriġinali, jew l-aggregati li jirriżultaw mill-qasma. Meta l-aggregati jinġieb onlajn aktar tard, il-volumi flessibbli f'dak aggregat se jingħata l-isem.

Jekk il-plessi ta 'aggregat inkorporati fi volum tradizzjonali offline fil-ħin tal-qasma, l-aggregat li jirriżulta se jkun offline. Meta qsim a plessi minn aggregat li tospita volumi flessibbli, jekk dan plessi offline, iżda l-aggregat huwa online, l-aggregat li jirriżulta se jidħlu fuq l-internet, u l-volumi flessibbli tiegħu se jingħata l-isem. Mhuwiex permess li jaqsam plessi minn aggregat offline.

A mera maqsuma jistgħu jiġu magħquda lura flimkien permezz tal-vs-għażla li mera aggr.

istatus aggr [aggrname]
[-R |-vs |-d |-c |-b |-i |-f |-f]

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.

       mhux magħruf mhux magħruf raġuni Nuqqas.  naqset data ONTAP naqset diska minħabba żball diska fatali.  Utent admin naqset maħruġa kmand "jonqsu diska" għal din il-disk.  ttikkettjati Disk imkisser kienet falliet fil Dejta ONTAP 6.1.X jew verżjoni preċedenti.  Iniz naqset sekwenza inizjalizzazzjoni Disk fallew.  Utent admin jitneħħew ħarġet kmand "tneħħi diska" għal din il-disk.  ma jkunx irrisponda Disk ma jkunx jirrispondi għal talbiet.  Disk jinġibed kien fiżikament miġbuda, jew l-ebda passaġġ teżisti dejta li jkollhom aċċess għad-disk.  Disk evitata kienet evitata bl-ESH. 

aggr undestroy [n] <aggrname>

Undestroy volum parzjalment intatti jew li qabel kienu meqruda aggregat jew tradizzjonali. Il-kmand stampi lista ta 'l-aggregati kandidati u l-volumi tradizzjonali li jaqblu l-isem mogħti, li jistgħu jkunu potenzjalment undestroyed.

-N-għażla prints l-lista ta 'diski li jinsabu mill-aggregat jew bil-volum tradizzjonali, li jistgħu jkunu potenzjalment undestroyed. Din l-għażla jista 'jintuża sabiex juri r-riżultat ta' eżekuzzjoni kmand, mingħajr ma attwalment tagħmel xi modifiki.

aggr tivverifika jerġa [aggrname]

Jerġa 'jibda mera RAID verifika fuq it-total imsemmi; jekk l-ebda isem aggregat hija mogħtija, fuq l-aggregati kollha bħalissa għaddejja minn verifika mera RAID li ġie sospiż.

aggr tivverifika bidu [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 ]

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

Cluster KONSIDERAZZJONIJIET

Aggregates on different filers in a cluster can have the same name. For example, both filers in a cluster can have an aggregate named aggr0 .

However, having unique aggregate names in a cluster makes it easier to migrate aggregates between the filers in the cluster.

EXAMPLES

aggr create aggr1 -r 10 20

Creates an aggregate named aggr1 with 20 disks. The RAID groups in this aggregate can contain up to 10 disks, so this new aggregate has two RAID groups. The filer adds the current spare disks to the new aggregate, starting with the smallest disk.

aggr create aggr1 20@9

Creates an aggregate named aggr1 with 20 9-GB disks. Because no RAID group size is specified, the default size (8 disks) is used. The newly-created aggregate contains two RAID groups with 8 disks and a third group with four disks.

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

Creates an aggregate named aggr1 with the specified three disks.

aggr create aggr1 10
aggr options aggr1 raidsize 5

L-ewwel kmand joħloq aggregata msemmija aggr1 b'10 diski li jappartjenu għall-grupp RAID wieħed. Il-kmand second jispeċifika li jekk xi diski huma sussegwentement miżjuda ma 'dan l-aggregat, dawn mhux se jikkawża xi grupp RAID attwali li jkollhom aktar minn ħames diski. Kull grupp RAID eżistenti se jkompli jkollu 10 diski u l-ebda diski aktar se jiġu miżjuda ma dak il-grupp RAID. Meta l-gruppi RAID ġodda huma maħluqa, dawn se jkollu daqs massimu ta 'ħames diski.

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

Turi l-informazzjoni dwar RAID aggr1 aggregat. Fl-eżempju li ġej, naraw li aggr1 hija RAID-DP aggregat protetti minn checksums blokk. Huwa online, u kollha diski qed joperaw normalment. L-aggregat fih diski four diski tnejn u tad-data, disk parità waħda, u disk doubleparity wieħed. Żewġ diski jinsabu fuq adapter 0b, u tnejn fuq 1b adapter. L-ixkaffa disk u numri bajja għal kull diska huma indikati. Kollha diski erba huma 10, diski RPM 000 FibreChannel mwaħħla permezz ta 'diska kanal A. L-diska "Pool" attribut hija murija biss jekk SyncMirror hija lliċenzjata, li mhuwiex il-każ hawnhekk (jekk SyncMirror ġew liċenzjati, Pool ikun jew 0 jew 1) . L-ammont ta 'spazju disk li jintuża mill-Data ONTAP ("Użati") u huwa disponibbli fuq id-diska ("Phys") hija murija fil-kolonni lemini.

  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 .


Werrej






















































Categories: Manual Pages Tags: , , , ,

cf

July 7th, 2009 Chris Kranz No comments

Werrej

ISEM

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

DESKRIZZJONI

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.

ARA WKOLL

partner


Werrej



Categories: Manual Pages Tags: , , , ,

bootfs

July 7th, 2009 Chris Kranz No comments

Werrej

ISEM

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

DESKRIZZJONI

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.

triq
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 KONSIDERAZZJONIJIET

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

EŻEMPJI

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 

ARA WKOLL

download


Werrej

Categories: Manual Pages Tags: , , , ,

boot

July 7th, 2009 Chris Kranz No comments

Werrej

ISEM

boot – directory of Data ONTAP executables

Synopsis

/ Etc / boot

DESKRIZZJONI

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.

FAJLS

/ Etc / boot
direttorju ta 'executables ONTAP tad-Data. Fajls huma post fi / etc / boot wara l-qatran jew setup.exe għandha decompressed minnhom. Dawn il-fajls jvarjaw minn rilaxx għal rilaxx.

ARA WKOLL

download


Werrej

Copyright © 1994-2008 NetApp, Inc Informazzjoni Legali

VN:F [1.9.11_1134]
Rata din il-kariga:
Rating: 0.0 / 10 (0 voti mitfugħa)

Categories: Manual Pages Tags: , , , ,

bmc

July 7th, 2009 Chris Kranz No comments

Werrej

ISEM

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

Synopsis

bmc help

bmc reboot

bmc setup

bmc status

bmc test autosupport

DESKRIZZJONI

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

ALTERNATTIVI

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 KONSIDERAZZJONIJIET

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

EŻEMPJI

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.


Werrej

Copyright © 1994-2008 NetApp, Inc Informazzjoni Legali

VN:F [1.9.11_1134]
Rata din il-kariga:
Rating: 0.0 / 10 (0 voti mitfugħa)

Categories: Manual Pages Tags: , , , ,

backuplog

July 7th, 2009 Chris Kranz No comments

Werrej

ISEM

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

Synopsis

/etc/log/backup

DESKRIZZJONI

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.

Error
Dump/restore hits an unexpected event.

Għażliet
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

ARA WKOLL

dump , restore , options


Werrej

Categories: Manual Pages Tags: , , , ,

backup

July 7th, 2009 Chris Kranz No comments

Werrej

ISEM

backup – manages backups

Synopsis

backup status [ <ID> ]

backup terminate <ID>

DESKRIZZJONI

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.

Tip
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.

ARA WKOLL

dump


Werrej



Categories: Manual Pages Tags: , , , ,

autosupport

July 7th, 2009 Chris Kranz 2 comments

Werrej

ISEM

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.

DESKRIZZJONI

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.

ALTERNATTIVI

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 . Il-valur awtomatiċi għall-din l-għażla hija fuq.

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 KONSIDERAZZJONIJIET

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


Werrej






























































Categories: Manual Pages Tags: , , , ,

auditlog

July 7th, 2009 Chris Kranz No comments

Werrej

ISEM

auditlog – contains an audit record of recent administrative activity

Synopsis

<logdir>/auditlog

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

DESKRIZZJONI

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

u

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.

FAJLS

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

ARA WKOLL

options , syslog.conf


Werrej

Categories: Manual Pages Tags: , , , ,

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

© 2009-2012 Chris Kranz All Rights Reserved
Dan is-sit mhuwiex affiljati jew sponsorjati mill NetApp fil xorta jew kwalunkwe kumpanija oħra msemmija ġewwa.