Arkivju

Karigi tagged "ONTAP"

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.

Stajt dejjem Għoġobni l-mod li PHP jkollhom paġni funzjoni tagħhom li jagħtu lill-utenti l-kapaċità li jikkummentaw direttament fuq minnhom. Dan jippermetti lin-nies biex jitilqu feedback fuq il-funzjonijiet u l-għodod, u wkoll segwitu ma 'xi użi żejda jew sintassi għal kmandijiet li mhumiex neċessarjament ċar ippubblikat. Nisperaw li dan jista 'iwasslu lura għall-NetApp biex itejbu d-dokumentazzjoni tagħhom.

I d definittivament simili biex jinkoraġġixxu lin-nies biex jikkummentaw fuq il-paġni bniedem ma 'xi ħaġa li tista' tkun utli, u nisperaw li jdaħħlu dan fil-sezzjoni ta 'referenza utli ftit. Ħafna grazzi għal darb'oħra għall-folk NetApp għall tgħin me ma 'dan.

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

Tags: , , , , Kategoriji: Ġenerali , Manwal Pages Tags: , , , ,

aggr

Werrej

ISEM

aggr - jikkmanda għall-ġestjoni aggregati, li juri l-istatus aggregata, u aggregati ikkupjar

Synopsis

l-argument kmand aggr ...

DESKRIZZJONI

Il-familja kmand aggr tamministra aggregati. Il-kmandijiet aggr tista 'toħloq aggregati ġodda, jeqirdu dawk eżistenti, aggregat undestroy qabel meqruda, jimmaniġġjaw plexes fi aggregat riflessa, tibdil fl-istat aggregat, japplikaw l-għażliet għal aggregat, kopja waħda aggregat għall-ieħor, u l-wiri l-istatus tagħhom. Jikkmanda aggregat ta 'spiss jaffettwaw il-volum (i) li jinsabu fi ħdan aggregati.

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 l-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. Il-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. Il-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 jiġi użat 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. The underlying disk technology and RAID type depends on implementation of such external storage arrays. SAS identifies Serial Attached SCSI disks in matching shelves. SATA identifies serial ATA disks in SAS shelves. SCSI stands for Small Computer System Interface, and it is included for backward compatibility with earlier disk technologies.

The -R rpm argument specifies the type of disks to use based on their rotational speed in revolutions per minute (rpm). It is needed only on systems having disks with different rotational speeds. Typical values for rotational speed are 5400, 7200, 10000, and 15000. -R cannot be used together with -d .

ndisks is the number of disks in the aggregate, including the parity disks. The disks in this newly created aggregate come from the pool of spare disks. The smallest disks in this pool join the aggregate first, unless you specify the @ size argument. size is the disk size in GB, and disks that are within 10% of the specified size will be selected for use in the aggregate.

The -m option can be used to specify that the new aggregate be mirrored (have two plexes) upon creation. If this option is given, then the indicated disks will be split across the two plexes. By default, the new aggregate will not be mirrored.

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.

If you use the -d disk1 [ disk2 ... ] argument, the filer creates the aggregate with the specified spare disks disk1 , disk2 , and so on. You can specify a space-separated list of disk names. Two separate lists must be specified if the new aggregate is mirrored. In the case that the new aggregate is mirrored, the indicated disks must result in an equal number of disks on each new plex.

The disks in a plex are not permitted to span spare pools. This behavior can be overridden with the -f option. The same option can also be used to force using disks that do not have matching rotational speed. The -f option has effect only when used with the -d option specifying disks to use.

To create a SnapLock aggregate, specify the -L flag with the aggr create command. This flag is only supported if either SnapLock Compliance or SnapLock Enterprise is licensed. The type of the SnapLock aggregate created, either Compliance or Enterprise, is determined by the installed SnapLock license. If both SnapLock Compliance and SnapLock Enterprise are licensed, use -L compliance or -L enterprise to specify the desired aggregate type.

The -l language_code argument may be used only when creating a traditional volume using option -v . The filer creates the traditional volume with the language specified by the language code. The default is the language used by the filer's root volume. See the vol man page for a list of language codes.

aggr destroy { aggrname | plexname } [ -f ]

Destroys the aggregate named aggrname , or the plex named plexname . Note that if the specified aggregate is tied to a traditional volume, then the traditional volume itself is destroyed as well.

If an aggregate is specified, all plexes in the aggregate are destroyed. The named aggregate must also not contain any flexible volumes, regardless of their mount state (online, restricted, or offline). If a plex is specified, the plex is destroyed, leaving an unmirrored aggregate or traditional volume containing the remaining plex. Before destroying the aggregate, traditional volume or plex, the user is prompted to confirm the operation. The -f flag can be used to destroy an aggregate, traditional volume or plex without prompting the user.

The disks originally in the destroyed object become spare disks. Only offline aggregates, traditional volumes and plexes can be destroyed.

aggr media_scrub status [ aggrname | plexname | groupname ]
[ -v ]

Prints the media scrubbing status of the named aggregate, plex, or group. If no name is given, then status is printed for all RAID groups currently running a media scrub. The status includes a percent-complete and whether it is suspended.

The -v flag displays the date and time at which the last full media scrub completed, the date and time at which the current instance of media scrubbing started, and the current status of the named aggregate, plex, or group. If no name is given, this more verbose status is printed for all RAID groups with active media scrubs.

aggr mirror aggrname
[ -f ]
[ -n ]
[ -v victim_aggrname ]
[ -d disk1 [ disk2 ... ] ]

Turns an unmirrored aggregate into a mirrored aggregate by adding a plex to it. The plex is either newly-formed from disks chosen from a spare pool, or, if the -v option is specified, is taken from another existing unmirrored aggregate. Aggregate aggrname must currently be unmirrored. Use aggr create to make a new, mirrored aggregate from scratch.

Disks may be specified explicitly using -d in the same way as with the aggr create and aggr add commands. The number of disks indicated must match the number present on the existing aggregate. The disks specified are not permitted to span disk pools. This behavior can be overridden with the -f option. The -f option, in combination with -d , can also be used to force using disks that have a rotational speed that does not match that of the majority of existing disks in the aggregate.

If disks are not specified explicitly, then disks are automatically selected to match those in the aggregate's existing plex.

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.

If a plexname is specified, the plex must be part of an online mirrored aggregate. 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.

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.

The only way to remove the root status of an aggregate or traditional volume is to set the root option on another aggregate or traditional volume.

snaplock_compliance

This read only option indicates that the aggregate is a SnapLock Compliance aggregate. Aggregates can only be designated SnapLock Compliance aggregates at creation time.

snaplock_enterprise

This read only option indicates that the aggregate is a SnapLock Enterprise aggregate. Aggregates can only be designated SnapLock Enterprise aggregates at creation time.

snapmirrored off

If SnapMirror is enabled for a traditional volume (SnapMirror is not supported for aggregates that contain flexible volumes), the filer automatically sets this option to on . Set this option to off if SnapMirror is no longer to be used to update the traditional volume mirror. After setting this option to off , the mirror becomes a regular writable traditional volume. This option can only be set to off ; only the filer can change the value of this option from off to on .

snapshot_autodelete on | 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.

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.

All sizes are reported in 1024-byte blocks, unless otherwise requested by one of the -h , -k , -m , -g , or -t options. The -k, -m, -g, and -t options scale each size-related field of the output to be expressed in kilobytes, megabytes, gigabytes, or terabytes respectively.

The following terminology is used by the command in reporting space.

 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 ]

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

CLUSTER CONSIDERATIONS

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.

EŻEMPJI

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

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 

ARA WKOLL

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.

ALTERNATTIVI

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.

ALTERNATTIVI

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

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: , , , ,

but

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.

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.

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 CONSIDERATIONS

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 

ARA WKOLL

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.

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

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.

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.

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

Karatteristiċi Autosupport huma manipulati permezz tal-kmand għażliet (ara l-għażliet). L-għażliet disponibbli huma kif ġej:

autosupport.cifs.verbose
Jekk fuq, jinkludi sessjoni CIFS u jaqsmu l-informazzjoni fil-messaġġi autosupport. Jekk off, dawk is-sezzjonijiet tħallew barra. In-nuqqas huwa off.

autosupport.content
It-tip ta 'kontenut li n-notifika autosupport għandu jkun fih. Valuri permissibbli huma kompleti u minimi. Il-valur ta 'default hija kompluta. L-għażla minima jippermetti l-għoti ta '"sanitizzati" u l-verżjoni iżgħar ta' l-autosupport, fil-ispiża ta 'appoġġ jitnaqqas minn Appliance Netwerk. Jekk jogħġbok ikkuntattja Appliance Netwerk jekk tħoss li għandek bżonn biex tuża l-għażla minimu. L-għażla sħiħa hija l-tradizzjonali (u awtomatiċi) forma ta 'autosupport. Jekk din l-għażla huwa mibdul minn sħiħa lill minimu allura l-messaġġi kollha autosupport preċedenti u sakemm titħassar taħt il-premessa li l-messaġġi sħiħa ma għandhomx jiġu trasmessi.

autosupport.doit
Tikkawża l-daemon autosupport li jibgħat notifika autosupport immedjatament. A kelma test tiddaħħal bħala l-għażla hija mibgħuta fil-linja tas-suġġett tan-notifika u għandha tintuża biex tispjega r-raġuni għan-notifika.

autosupport.enable
Jippermetti / tiddiżattiva l-karatteristiċi notifika autosupport (ara autosupport). In-nuqqas huwa fuq li jikkawża notifiki autosupport li jintbagħtu. Din l-għażla se jwarrab l-għażla autosupport.support.enable.

autosupport.from
Jiddefinixxi l-utent li jiġu nominati bħala l-mittenti tan-notifika. In-nuqqas huwa postmaster@your.domain. Risposti email mill Appliance Netwerk se jintbagħtu f'dan l-indirizz.

autosupport.local.nht_data.enable
Jippermetti / tiddiżattiva l-autosupport data NHT li għandhom jintbagħtu lill-benefiċjarji elenkati fl-għażla autosupport.to. NHT data hija l-, tad-data interna binarja log minn kull disk drive, u b'mod ġenerali, mhuwiex parsable minn minbarra Appliance Netwerk. M'hemm l-ebda data tal-klijent fil-autosupport NHT. Il-default għall din l-għażla huwa off.

autosupport.local.performance_data.enable
Jippermetti / tiddiżattiva-rendiment autosupport li għandhom jintbagħtu lill-benefiċjarji elenkati fl-autosupport.to. Il-autosupport prestazzjoni fih kampjuni kull siegħa ta 'bankijiet prestazzjoni tas-sistema, u b'mod ġenerali huwa biss utli biex Appliance Netwerk. In-nuqqas huwa off.

autosupport.mailhost
Jiddefinixxi l-lista ta 'sa ismijiet mailhost 5. Ikteb l-ismijiet ospitanti bħala lista ta comma-sseparati bl-ebda spazji bejniethom. In-nuqqas huwa lista vojta.

autosupport.minimal.subject.id
Jiddefinixxi t-tip ta 'sekwenza li jintuża fil-porzjon ta' identifikazzjoni tal-linja tas-suġġett meta autosupport.content huwa stabbilit għal minimu. Valuri permissibbli huma systemid u hostname. In-nuqqas huwa systemid.

autosupport.noteto
Jiddefinixxi l-lista tar-riċevituri għall-email autosupport nota qasira. Sa l-indirizzi tal-posta 5 huma permessi. Ikteb l-indirizzi bħala lista ta comma-sseparati bl-ebda spazji bejniethom. In-nuqqas huwa lista vojta li jiskonnettja l-emails nota qasira.

autosupport.nht_data.enable
Jippermetti / tiddiżattiva l-ġenerazzjoni ta 'l-Trigger Saħħa (NHT) id-data autosupport. Default huwa off

autosupport.performance_data.enable
Jippermetti / tiddiżattiva teħid ta 'kampjuni kull siegħa ta' data tal-prestazzjoni tas-sistema, u l-ħolqien ta 'kull ġimgħa ta' autosupport prestazzjoni tad-data. In-nuqqas huwa fuq.

autosupport.retry.count
Numru ta 'drabi biex jippruvaw jigi msewwi l-posta qabel ma jagħti bidu u twaqqa l-posta. Minimu 5; massimu huwa 4294967295; In-nuqqas huwa 15.

autosupport.retry.interval
Ħin fil-minuti għal dewmien qabel tipprova li tibgħat il-autosupport mill-ġdid. Minimu huwa 30 sekonda, massimu huwa 1 jum. Valuri jista 'jispiċċa bil `i", `m' jew 'h" biex tindika sekonda, minuti jew sigħat rispettivament, jekk l-ebda unitajiet huma speċifikati huwa input minn
preżunt li jkun f'sekondi. Il-valur ta 'default 4m.

autosupport.support.enable
Jippermetti / tiddiżattiva-notifika autosupport li Appliance Netwerk In-nuqqas huwa fuq li jikkawża notifiki autosupport li jintbagħat direttament lill Appliance Netwerk kif deskritti mill-għażla autosupport.support.transport. Din l-għażla sostitwiti (megħluba) bil-valur ta autosupport.enable.

autosupport.support.proxy
Tippermetti l-iffissar ta 'prokura bbażata http jekk autosupport.support.transport huwa https jew http. L-inadempjenza
għal din l-għażla huwa l-string vojt, li jimplika l-ebda prokura huwa meħtieġ.

autosupport.support.to
Din l-għażla jinqara biss; dan juri fejn in-notifiki autosupport biex Appliance Netwerk jintbagħtu jekk autosupport.support.transport huwa SMTP.

autosupport.support.transport
Tippermetti li jistabbilixxi l-tip ta 'konsenja mixtieq għan-notifiki autosupport li huma destinati għall-apparat tan-Netwerk. Valuri permessi huma https, http (għall-web diretta bbażata kollokament) jew SMTP (għall-email tradizzjonali). Il-valur ta 'default https. Innota li http u https jistgħu (jiddependi fuq konfigurazzjoni tan-network lokali) jeħtieġu li l-għażla autosupport.support.proxy jiġu stabbiliti b'mod korrett. Ukoll SMTP jeħtieġ li autosupport.mailhosts tiġi kkonfigurata b'mod korrett qabel il-kunsinna autosupport tista 'tkun suċċess.

autosupport.support.url
Din l-għażla jinqara biss; dan juri fejn in-notifiki autosupport biex Appliance Netwerk jintbagħtu jekk autosupport.support.transport huwa https jew http.

autosupport.throttle
Jippermetti throttling autosupport (ara autosupport). Meta autosupports wisq huma mibgħuta fil-qasir wisq żmien, messaġġi addizzjonali tal-istess tip se tkun skartata. Valuri Validu għal din l-għażla huma fuq jew off. Il-valur awtomatiċi għall-din l-għażla hija fuq.

autosupport.to
Jiddefinixxi l-lista tar-riċevituri għall-notifika email autosupport. Sa l-indirizzi tal-posta 5 huma permessi. Ikteb l-indirizzi bħala lista ta comma-sseparati bl-ebda spazji bejniethom. In-nuqqas huwa lista vojta. Innota li huwa m'għadux neċessarju li jużaw li standard Netwerk Appliance autosupport indirizz email f'dan il-qasam sabiex jidderieġu messaġġi autosupport għall Appliance Netwerk. Jekk jogħġbok uża autosupport.support.enable minflok.

WERREJ

A autosupport sħiħa se jkun fiha l-informazzjoni li ġejja. Innota li xi sezzjonijiet huma configurable, u / jew disponibbli jiddependi fuq liema fatturi huma liċenzjati. L-ordni mogħtija hija l-ordni ġenerali ta 'dehra fil-messaġġ autosupport innifsu.

Data Ġenerazzjoni u timestamp

Verżjoni software

Sistema ID

Hostname

SNMP Isem ta 'kuntatt (jekk speċifikat)

Post SNMP (jekk speċifikat)

Sistema sieħeb ID (jekk miġbura)

Msieħba hostname (jekk miġbura)

Node cluster Istatus (jekk miġbura)

Tip lingwa console

sysconfig-output

sysconfig-c-produzzjoni

sysconfig-d produzzjoni

In-Numru Serjali sistema

Liċenzji tas-software (scrambled qabel it-trażmissjoni)

Għażla settings

produzzjoni availtime

ara tissorvelja l-output (jekk miġbura)

ic-prestazzjoni stats output (jekk miġbura ma VIA)

ic stats żball vs Il-produzzjoni (jekk miġbura ma VIA)

snet stats-vs-produzzjoni (jekk miġbura ma SNET)

ifconfig-output

ifstat-output

vlan produzzjoni Eurostat

produzzjoni istatus vif

produzzjoni info nis

nfsstat-ċ ta 'produzzjoni (jekk liċenzjati)

CIFS produzzjoni Eurostat (jekk liċenzjati)

CIFS sessjonijiet fil-qosor (jekk liċenzjati)

CIFS sessjonijiet produzzjoni (jekk liċenzjata u ppermettiet)

CIFS ishma fil-qosor (jekk liċenzjati)

CIFS ishma produzzjoni (jekk liċenzjata u ppermettiet)

vol istatus l (jekk CIFS hija liċenzjata)

produzzjoni httpstat

istatus ta-a vfiler produzzjoni (jekk liċenzjati)

produzzjoni df

df-i produzzjoni

snap produzzjoni sched

vol istatus-vs-produzzjoni

produzzjoni istatus vol

vol istatus ċ-produzzjoni

Scrub vol istatus-vs-produzzjoni

sysconfig-r-output

fcstat produzzjoni fcal_stats

fcstat produzzjoni device_map

fcstat produzzjoni link_stats

ECC Memorja Istatistika scrubber

EMS avveniment istatus produzzjoni

EMS log istatus produzzjoni

valuri tar-reġistru

Perf rapport ta-t-produzzjoni

juru ħażna adapter-output

ħażna juru hub-output

ħażna juru disk output

produzzjoni ħażna drapp juru

produzzjoni ħażna swiċċ juru

ħażna juru port tal-produzzjoni

Log EMS fajl (jekk ppermettiet)

/ Etc / messaġġi kontenut

Informazzjoni Inconsistancy Parità

WAFL_check zkuk

TIPI

It-tipi li ġejjin ta 'messaġġi autosupport, fis-severità assoċjati tagħhom, jistgħu jiġu ġġenerati awtomatikament. It-test messaġġ autosupport huwa b'tipa grassa, u l-valur LOG_XXX huwa l-livell severità syslog. Innota li t-test ta 'ġewwa tal-parentesi kwadri ([]) hija deskrittiva u mhux statiku għal kull messaġġ autosupport partikolari ta' dak it-tip.

BATTERY_LOW!
LOG_ALERT

BMC_EVENT: ERROR BUS
LOG_ERR

BMC_EVENT: ERROR POST
LOG_ERR

Cluster DOWNREV BOOT Firmware
LOG_CRIT

ŻBALL cluster: DISK / BLATA GĦADD diskrepanza LOG_EMERG

Cluster GIVEBACK KOMPLUTA
LOG_INFO

Takeover Cluster KOMPLUTA AWTOMATIKU
LOG_ALERT

Takeover Cluster KOMPLUTA MANWAL
LOG_INFO

Takeover Cluster naqas
LOG_INFO

CONFIGURATION_ERROR!
LOG_ALERT

TWISSIJA fann CPU - [fann]
LOG_WARNING

DEVICE_QUALIFICATION_FAILED
LOG_CRIT

ERROR KONFIGURAZZJONI DISK
LOG_ALERT

DISK RIKOSTRUZZJONI naqas!
LOG_ALERT

DISK_FAIL -! Evitata bl 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 żbalji jistgħux jitħallsu lura
LOG_WARNING

OVER_TEMPERATURE_SHUTDOWN!
LOG_EMERG

OVER_TEMPERATURE_WARNING!
LOG_EMERG

PARTNER ISFEL, xiri IMPOSSIBBLI
LOG_ALERT

RAM BAD POSSIBBLI
LOG_ERR

Inode mhux konessi POSSIBBLI
LOG_ERR

Reboot (xiri cluster)
LOG_ALERT

Reboot (wara WAFL_check)
LOG_INFO

Reboot (wara d-dħul Firmware)
LOG_INFO

Reboot (wara giveback)
LOG_INFO

Reboot (kmand iwaqqfu)
LOG_INFO

Reboot (iwaqqfu interna)
LOG_INFO

Reboot (reboot interna)
LOG_INFO

Reboot (paniku)
LOG_CRIT

Reboot (glitch enerġija)
LOG_INFO

Reboot (enerġija fuq)
LOG_INFO

Reboot (kmand reboot)
LOG_INFO

Reboot (reset għassies)
LOG_CRIT

Reboot
LOG_INFO

Unità tat-tkessiħ BLATA naqas
LOG_EMERG

Unità tat-tkessiħ BLATA naqas
LOG_WARNING

SHELF_FAULT!
LOG_ALERT

JAGĦMEL UŻU SNMP DEFINIT 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 ([jintuza mill-utent minn autosupport.doit]) LOG_INFO

WAFL_check!
LOG_ALERT

WEEKLY_LOG
LOG_INFO

[EMS avveniment]
LOG_INFO

[Fann] FAN_FAIL!
LOG_ALERT

[Mini qalba]
LOG_CRIT

[Provvista ta 'enerġija falliment]
LOG_ALERT

[Provvista ta 'enerġija] POWER_SUPPLY_DEGRADED!
LOG_ALERT

[Ixkaffa fuq it-temperatura kritika]
LOG_EMERG

Cluster KONSIDERAZZJONIJIET

Il-messaġġi email autosupport minn filer fi grupp huma differenti mill-messaġġi email autosupport minn filer standalone fil-modi li ġejjin:

Is-suġġett fil-messaġġi email autosupport minn filer fi grupp jgħid, "notifika Cluster," minflok "Sistema notifika."

Il-messaġġi email autosupport minn filer fi grupp fiha informazzjoni dwar il-partner tagħha, bħall-ID sistema imsieħeb u l-isem ospitanti msieħba.

Fil-modalità ta 'xiri, jekk inti reboot-filer ħajjin, żewġ messaġġi email autosupport jinnotifika lill-riċevituri email ta' l-reboot: wieħed huwa mill-filer ħajjin u waħda hija mill-filer fallew.

Il-filer ħajjin jibgħat messaġġ email autosupport wara li jispiċċa l-proċess ta 'xiri.

ARA WKOLL

għażliet, sieħeb, setup, hosts, RFC821


Werrej






























































auditlog

Werrej

ISEM

auditlog - fih rekord ta 'verifika ta' attività amministrattiva reċenti

Synopsis

<logdir> / auditlog

<logdir> huwa / etc / log għall-filers u / zkuk għal apparati NetCache.

DESKRIZZJONI

Jekk il-auditlog.enable għażla huwa fuq, is-sistema zkuk kull kontribuzzjoni għas-sistema fil-qafas tal-console / telnet u permezz rsh għall-fajl auditlog. L-output tad-data mill jikkmanda esegwiti b'dan il-mod huwa wkoll illoggjat għal auditlog. Invocations amministrattivi servlet (permezz HTTP, tipikament mis FilerView) u API sejħiet li jsiru permezz ta 'l-interface ONTAPI huma wkoll illoggjat għall-auditlog. Messaġġ tipika hija:

Wed Frar 9 17:34:09 GMT [rshd_0: auditlog]: għerq: OUT: data: Wed Frar 9 17:34:09 GMT 2000

Dan jindika li kien hemm sessjoni rsh madwar 9 Frar Wed 17:34:09 GMT li kkawża d-kmand data li għandha tiġi eżegwita. L-utent li jwettqu l-kmand kienet għerq. It-tip ta 'log hija data prodotta mis-sistema kif indikat mill-keyword OUT.

Kmandijiet ittajpjat fil-console tal-filer jew esegwiti mill rsh huma nominati mill-keyword FL kif fi:

Wed Frar 9 17:34:03 GMT [rshd_0: auditlog]:: FI: rsh qoxra: KMAND INPUT RSH hija data

Il-bidu u tmiem ta 'sessjoni rsh huma ddisinjati demarkati kif fil-

Wed Frar 9 17:34:09 GMT [rshd_0: auditlog]: orbit.eng.mycompany.com: għerq: START: qoxra rsh

u

Wed Frar 9 17:34:09 GMT [rshd_0: auditlog]: għerq: TMIEM: rsh qoxra:

Id-daqs massimu tal-fajl auditlog huwa kkontrollat ​​mill-għażla auditlog.max_file_size. Jekk il-fajl gets dan id-daqs, huwa jiddawwar (ara hawn taħt).

Kull is-Sibt fil 24:00, <logdir> / auditlog hija trasferita għall <logdir> / auditlog.0, <logdir> / auditlog.0 hija trasferita għall <logdir> / auditlog.1, u l-bqija. Dan il-proċess jissejjaħ 'rotazzjoni. Fajls Auditlog huma salvati għal total ta 'sitt ġimgħat, jekk ma ifur.

Jekk inti tixtieq li tibgħat messaġġi log verifika għal remoti syslog log ospitanti (wieħed li taċċetta messaġġi syslog permezz tal-protokoll syslog BSD speċifikati fl-RFC 3164), timmodifika l-filer ta / etc / syslog.conf fajl biex jgħaddi messaġġi mill-filer "L local7" faċilità għall-ospitanti remoti. Tagħmel dan billi żieda ta 'linja bħal:

local7 .*
@ 1.2.3.4

għal / etc / syslog.conf. L-indirizz IP ġie użat hawnhekk, iżda isem DNS validu jistgħu jintużaw ukoll. Innota li l-użu ta 'isem DNS jista' ma jirnexxix jekk il-filer ma jkunx jista 'jsolvi l-isem mogħti fil-fajl. Jekk dan iseħħ, il-messaġġi tiegħek mhux ser ikunu mgħoddija.

Fuq il-ġurnal ospitanti, ikollok bzonn li timmodifika konfigurazzjoni fajl tal-daemon syslog biex idawwru traffiku li jagħtu messaġġ syslog mill-"local7" faċilità għall-fajl konfigurazzjoni xierqa. Dan huwa tipikament isir billi żżid linja simili għal dak muri hawn fuq għall-filer:

local7 .*
/ Var / zkuk / filer_auditlogs

Imbagħad jistartja l-daemon fuq il-log ospitanti, jew tibgħat sinjal xieraq għaliha. Ara d-dokumentazzjoni għall-daemon log syslog ospitanti tiegħek għal aktar informazzjoni dwar kif jagħmlu din il-bidla konfigurazzjoni.

FAJLS

<logdir> / auditlog
fajl auditlog għall-ġimgħa kurrenti. <logdir> / auditlog. [0-5] fajls auditlog għall-ġimgħa ta 'qabel

ARA WKOLL

għażliet, syslog.conf


Werrej

Tags: , , , , Kategoriji: Manwal Paġni Tags: , , , ,

Behavior Bad blukkat aċċess tentattivi 2481 fl-aħħar 7 ijiem.

© 2009-2012 Chris Kranz Drittijiet kollha riżervati
Dan is-sit mhuwiex affiljati jew sponsorjati mill NetApp fil xorta jew kwalunkwe kumpanija oħra msemmija ġewwa.