Arhiiv

Ametikohad Merkatut "mees"

NetApp Man Pages

NetApp on lahkelt andnud mulle luba taasavaldamine oma mees lehekülge siin. Nad vajavad veel pisut korrastada, kuid õhuke kogus tähendab, et võtan mind mõnda aega, et saada kõiki neid sorteerida ja ristviidetega korralikult, siis vabandage igasuguse visuaalse küsimusi hetkel. Kirjutasin kiire parsing vahend, et saada kogu info on siin, nii et seal võib olla mõned küsimused, mis tulenevad nimetatud ikka.

Mulle on alati meeldinud nii, et PHP on oma funktsioon lehekülgi andes kasutajatele võimaluse kommenteerida otse neile. See võimaldab inimestel lahkuda tagasisidet funktsioone ja tööriistu, samuti jälgida mõned ekstra kasutamiseks või süntaks käske, mis ei pruugi olla selgelt avaldatud. Loodetavasti see saab toita tagasi NetApp parandada oma dokumentatsiooni.

Ma kindlasti tahaksin julgustada inimesi kommenteerida mees lehekülgi midagi, mis võib olla kasulik, ja loodetavasti ehitama seda arvesse kasulik vähesel osa. Suur tänu veelkord NetApp folk, et aitate mind sellega.

VN: F [1.9.11_1134]
Hinda seda postitust:
Hinnang: 8,8 / 10 (19 votes cast)

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

aggr

July 7th, 2009 Chris Kranz No comments

Sisukord

NAME

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

SYNOPSIS

aggr command argument …

DESCRIPTION

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.

Aggr käsk perekond on uued andmed ONTAP 7,0. Vol käsk pere ette üle traditsioonilise vol_ u mes et sulatatud ühe kasutaja nähtav failisüsteemi ja ühe RAID taseme säilitamise konteiner (kogusumma) arvesse jagamatu üksus, ja ikka teeb. Võimaldada paindlikumat kasutamist ladustamise, agregaatide nüüd toetada ka võime olla mitu, iseseisev kasutaja tasemel failisüsteemi nimega paindlik köidet.

Andmed ONTAP 7,0 toetab täielikult nii traditsioonilisi kui ka paindlik köidet. Aggr käsk pere on eelistatud haldamise meetod filer oma agregaadid, sealhulgas need, mis on põimitud tavapärasest mahust.

Pange tähele, et enamik aggr käsud kehtivad võrdselt nii täitematerjali tüüp, mis sisaldab paindlik kogused ja tüüp, mis on tihedalt seotud, moodustades traditsiooniline maht. Seega sõna kokku kasutatakse sageli siin viidata nii ladustamiseks klassid. Sellistel juhtudel annab see lühendvormina pikem ja kohmakas fraas "agregaatide ja traditsiooniliste mahtude".

Agregaatide võib olla kas peegeldatud või unmirrored. Plex on füüsiline koopia WAFL ladustamine kokku. Peegelpildis kokku koosneb kahest plexes; unmirrored agregaadid sisaldavad ühe plex. Et luua peegelpildis kokku peab teil olema filer konfiguratsiooni, mis toetab RAID taseme peegeldamist. Kui peegeldamine on lubatud filer, vaba kettad on jagatud kahte ketta basseinid. Kui kokku on loodud, kõik kettad ühe plex peab tulema sama ketas bassein ja 2 plexes on peegelpildis kokku peab koosnema kettad eraldi basseinid, kuna see maksimeerib tõrke. See poliitika võib olla kaalu koos-f võtit selle aggr luua, aggr add ja aggr peegel, kuid see ei ole soovitatav.

Kokku nimi võib sisaldada tähti, numbreid ja alakriips (_), kuid esimene märk peab olema täht või alakriips. Või kokku kuni 200 agregaatide (sh varjatud tavapärastest mahtudest) saab luua iga filer.

Plex võib olla online või offline. Kui see on offline, siis ei ole saadaval lugeda ega kirjutada juurdepääs. Plexes võivad olla kombinatsioonid järgmised riigid:

normaalne Kõik RAID rühmade plex on funktsionaalsed.

suutnud Vähemalt üks RAID gruppide plex on ebaõnnestunud.

tühi plex on osa kokku, et on loodud, ja üht või mitut kettad suunatud kokku tuleb nullida enne lisanduvad keerulised.

aktiivne plex on kasutusvalmis.

passiivne
Plex ei kasutata.

resyncing
Plex sisu on praegu aegunud ja on parasjagu resynchronized sisuga muud plex täitematerjali (kehtib peegelpildis agregaatide puhul).

lisades kettad
Disks lisatavad plex s RAID grupi (s).

out-of-date
See riik tekib ainult peegelpildis agregaadid, kus üks plexes on ebaõnnestunud. Mitte ebaõnnestunud plex on selles, kas see tuli resynchronized ajal muud plex ebaõnnestus.

Plex on oma nime kasutades nime kokku, kaldkriipsuga eraldaja ja nimi plex. Süsteem valib plex nimed at loomine aega. Näiteks 1. plex loodud kokku aggr0 oleks aggr0/plex0.

Kokku võib olla online, piiratud või offline. Kui ühine on offline, ei lugeda ega kirjutada juurdepääs on lubatud. Kui kokku on piiratud teatud toimingud on lubatud (näiteks kokku koopia, võrdsus ümberarvutamise või RAID rekonstrueerimine), kuid andmetele juurdepääsu ei ole lubatud. Agregaadid, mis ei ole osa traditsiooniline maht saab ainult piiratud või offlined kui nad ei sisalda paindlik köidet.

Agregaadid võivad olla kombinatsioonid järgmised riigid:

aggr kokku on tänapäeva kokku, see on võimeline sisaldavad null või paindlikum köidet.

kopeerimine
Kokku on praegu eesmärk kokku aktiivse aggr kopeerimisel.

halvenenud
Kokku vähemalt üks lagunenud RAID gruppi, mida ei ole taastatud.

välis-
Kettaid, et kokku sisaldab koliti praeguse filer teise filer.

kasvab
Kettaid on parasjagu lisatud kokku.

initsialiseerimisel
Kokku on parasjagu käivitub.

kehtetu
Kokku ei sisalda mahud ja keegi ei saa lisada. Tavaliselt see juhtub alles pärast katkestatud kokku kopeerimisel.

triikimine
WAFL järjepidevuse kontroll viiakse läbi selle kokku.

peegel halvenenud
Kokku on peegelpildis kokku ja üks tema plexes on offline või resyncing.

peegeldatud
Kokku on peegeldatud ja kõik selle RAID rühmad on funktsionaalne.

vajaduste kontroll
WAFL järjepidevuse kontroll tuleb läbi viia kokku.

osaline
Vähemalt üks ketas leiti kokku, kuid kaks või enam kettaid on puudu.

RAID0 kokku koosneb RAID-0 (ei ole pariteet) RAID gruppi (V-seeria ja NetCache ainult).

raid4 kokku koosneb RAID-4 RAID gruppi.

raid_dp
Kokku koosneb RAID-DP (Double Võrdsust) RAID gruppi.

taastama
Vähemalt üks RAID gruppi kokku on taastatud.

suunata
Aggregate ümberjaotamise või faili ümberjaotamine koos-p võimalus on alustatud kokku. Loe jõudluse maht kokku võib olla halvenenud.

resyncing
Üks plexes on peegelpildis kokku on resynchronized.

snapmirrored
Kokku on snapmirrored replica muu kokku. See riik saab tekkida ainult siis, kui kokku on osa traditsioonilise maht.

trad kokku on sulatatud ühte kohta. Seda nimetatakse ka traditsioonilisi mahu ja on täpselt samaväärne mahud, mis olid olemas enne andmete ONTAP 7,0. Paindlik mahud ei saa luua sees see kokku.

kontrollida
RAID peegel kontrollid praegu töötavad üheskoos.

wafl vastuolus
Kokku on märgitud vigaseks. Palun pöörduge klienditoe kui näed kokku selles riigis.

KASUTAMINE

Järgmised käsud on saadaval aggr suite:

  lisada peegel piirata undestroy kopeerida offline nühkima kontrollida luua online show_space hävitada võimalusi jagada media_scrub ümbernimetamine staatus 

aggr add aggrname
[-F]
[-N]
[-G {raidgroup | uus | kõik}]
{Ndisks [@ size]
|
-D disk1 [disk2 ... ] [-D diskn [diskn 1 ... ]]}

Lisab kettaid kokku nimega aggrname. Täpsustada kettad samal viisil nagu aggr Loo käsk. Kui lähteproov on peegelpildis, siis-d argument tuleb kasutada kaks korda (kui üldse).

Kui g võimalust ei kasutata, kettaid lisada hiljuti loodud RAID gruppi util see on täis, ja siis ühe või mitme uue RAID rühmad on loodud ja ülejäänud kettaid lisatakse uusi gruppe. Olemasolevad RAID rühmad, mis ei ole täis jääb osaliselt täidetud.

-G valik võimaldab spetsifikatsioon RAID gruppi (näiteks rg0), millele märgitud kettaid tuleks lisada, või meetodit, mille kettaid lisatakse uue või olemasoleva RAID gruppi.

Kui-g võtmega saab määrata RAID gruppi, mis RAID grupp on juba olemas. Kettad on lisatud, et RAID gruppi util see on täis. Kõik ülejäänud kettaid ignoreeritakse.

Kui g võimalust järgneb uus, Data ONTAP tekitab ühe või mitme uue RAID rühmad ja lisab kettaid, isegi kui kettaid sobiks olemasolevasse RAID gruppi. Kõik olemasolevad RAID rühmad, mis ei ole täis jääb osaliselt täidetud. Nimi uus RAID rühmad valitakse automaatselt. Ei ole võimalik määrata nimed uue RAID gruppi.

Kui g võimalus järgnevad kõik, Data ONTAP lisab nimetatud kettaid olemasolevate RAID rühma esimene. Pärast kõigi olemasolevate RAID rühmad on täis, see tekitab ühe või mitme uue RAID rühmad ja lisab nimetatud kettaid uusi gruppe.

-N võimalust saab kasutada, et kuvada käsk, et süsteem täidab, ilma tegelikult teha mingeid muudatusi. See on kasulik väljapanek automaatselt valitud kettaid, näiteks.

Vaikimisi on filter täitub 1 RAID gruppi kettaid enne teise RAID gruppi. Oletame, et kokku on hetkel 1 RAID gruppi 12 plaati ja RAID grupi suurus on 14. Kui lisate 5 kettaid sellele kogusummale, siis on 1 RAID gruppi 14 plaati ja teine ​​RAID gruppi 3 kettaid. Filer ei jaotuks ühtlaselt kettad seas RAID gruppi.

Sa ei saa lisada kettaid peegelpildis kokku, kui üks plexes on offline.

Kettad plex ei ole lubatud span disk basseinid. Selline käitumine võib olla kaalu koos-f lipu kui seda kasutatakse koos-d argument nimekirja kettaid lisada. -F lipu koos-d, saab kasutada ka sundida lisada kettaid, mis on pöörlemiskiirus, mis ei sobi, et enamiku olemasolevate ketaste kogumis.

aggr koopia katkestada [-h] operation_number | kõik

Lõpetab kokku koopia operatsioone. Opera_ t ion_number parameeter määrab, mis operatsiooni lõpetada. Kui määrate, kõik kokku aktiivne koopia tegevuse lõpetamisest.

aggr koopia start
[-S |-s snapshot] [-C]
allikas sihtkoht

Kopeerib kõik andmed, sealhulgas pilte ja paindlik mahud, ühest kokku teise. Kui-S lippu kasutatakse, käsk kopeerib kõik pilte päritolus kokku sihtpunkti kokku. Et määratleda konkreetse pildi kopeerida, kasutada-s lipu järgneb nimi snapshot. Kui te kasutate ei-S ega-s lippu käsk, filer loob läbilõike hetkel aggr koopia start käsu täitnud ja koopiad ainult, et snapshot sihtpunkti kokku.

-C lipp on nõutav, kui allikas kokku olnud vaba ruumi killustatuse läbi, või kui sihtkohta kokku on vaba ruumi defragmented. Vaba ruumi killustatuse teha saab kokku kasutades ümber käsk.

Aggregate koopiaid võib teha ainult vahel agregaatide, et võõrustada paindlik köidet. Agregaadid, mis on paigaldatud traditsioonilise mahud ei saa osaleda.

Allikas ja sihtpunkt kokkuvõtlikke näitajaid saab samal filer või erinevate filers. Kui allikana või sihtkohana kokku on filer va 1, kus sisestad aggr koopia käivitamiskorraldus täpsustada kokku nime filer_name: aggre_ g ate_name formaadis.

Filers kaasatud kokku koopia peab vastama järgmistele nõuetele aggr koopia käivitamiskorraldus täidetakse edukalt:

Allikas kokku peab olema online ja sihtkoht kokku peab olema piiratud.

Kui koopia on kahe filers iga filter tuleb määratleda usaldusväärse hulk muid filer. See tähendab, et filer nimi peab olema / etc / hosts.equiv pilti teiste filer.

Kui koopia on samal filer, localhost tuleb lisada filer s / etc / hosts.equiv faili. Samuti loopback aadress peab olema filer s / etc / hosts faili. Muidu filer ei saa saata pakette ise läbi loopback aadress, kui nad üritavad kopeerida.

Kasutada kettaruumi sihtkohta kokku olema suurem või võrdne kasutatav kettaruum allika kokku. Kasuta df-failinimega käsk, et näha kogus, mida kettaruumi eriti kokku.

Iga aggr koopia käivitamiskorraldus genereerib 2 kokku koopia toiminguid: 1 andmete lugemiseks allikas kokku ja 1 kirjutamiseks andmete sihtkoht kokku. Iga filer toetab kuni 4 üheaegne kokku koopia operatsioone.

aggr koopia staatus [operation_number]

Näitab edu ühe või kõik aggr koopia operatsioone. Tegevus on numbritega 0 kuni 3.

Restart kontrollpunkti teavet kõigi ülekandeid ka näidata.

aggr koopia throttle [operation_number] väärtus

Kontrollib täitmist aggr kopeerimisel. Väärtus ulatub 10 (täiskiirusel) kuni 1 (ühe kümnendiku täiskiirusel). Vaikimisi väärtus püsib filer oma aggr.copy.throttle valik ning on määratud 10 (täiskiirusel) tehases. Teil on võimalik taotleda täitmise väärtust operatsioon määratud operation_number parameetrit. Kui te ei määra töö number aggr koopia throttle käsk, käsk kehtib kõigi aggr koopia operatsioone.

Kasuta seda käsku, et piirata kiirus aggr koopia operatsiooni, kui te kahtlustate, et aggr kopeerimine põhjustab jõudluse probleeme oma filer. Eelkõige throttle eesmärk on aidata vähendada CPU kasutus aggr kopeerimisel. Seda ei saa kasutada peensusteni ribalaiust tarbimisharjumusi.

Aggr koopia throttle käsk vaid võimaldab teil määrata kiiruse aggr koopia operatsioon, mis on pooleli. Vaikimisi aggr kopeerimiskiirus, mida kasutatakse tulevaste koopia toimimise, kasutamise võimalusi käsu seada aggr.copy.throttle valik.

aggr create aggrname
[-F]
[-M]
[-N]
[-T raidtype]
[-R raidsize]
[-T disk-type]
[-R rpm]
[-L [vastavuse | ettevõtte]]
[-V]
[-L keelest code]
{Ndisks [@ size]

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

Loob uue kokku nimega aggrname. Kokku nimi võib sisaldada tähti, numbreid ja alakriips (_), kuid esimene märk peab olema täht või alakriips. Kuni 200 agregaatide saab luua iga filer. See arv hõlmab ka selliseid agregaadid, mis on kinnistatud traditsioonilise köidet.

Varjatud kokku saab luua osana traditsiooniline mahtu kasutades-v valik. See ei tohi sisaldada paindlik köidet.

Regulaarselt kokku, mis on loodud ilma-v variant, võib olla ainult paindlik köidet. Ei saa lisada traditsiooniline maht ja see ei sisalda mahud kohe pärast loomist. New paindlik maht saab luua kasutades vol Loo käsk.

-T raidtype argument määrab tüüpi RAID gruppi (s), mida kasutatakse, et luua kokku. Võimalik RAID gruppi tüübid on raid4 RAID-4, raid_dp RAID-DP (Double Võrdsust) ja RAID0 lihtsaid striping ilma pariteet kaitse. Default raidtype täitematerjalide ja traditsiooniliste köidet filers on raid_dp. Milles raidtype ei lubatud V-seeria süsteemid; maksejõuetusest RAID0 kasutatakse alati.

-R raidsize argument määrab maksimaalse arvu kettaid iga RAID gruppi kogumis. Maksimaalne ja vaikimisi väärtused raidsize on platvormist sõltuv, mis põhineb tulemuslikkuse ja usaldusväärsuse kaalutlustel. Vaata aggr võimalusi raidsize rohkem üksikasju.

-T disk-type argument määrab tüüpi kettaid kasutama, kui loote uue kokku. On vaja ainult süsteemid ühendatud kettaid erinevad. Võimalik ketas liigid on: ATA, FCAL, Lun, SAS, SATA ja SCSI. Segamine kettaid erinevate ühes kokku ei ole lubatud.-T ei saa kasutada koos-d.

Disk tüüpi tuvastab ketta tehnoloogia ja ühenduvus tüüp. ATA tuvastab ATA ketastel kas IDE või Serial ATA liides riiulid ühendatud FCAL (Fibre Channel vahekohtu Loop). FCAL tuvastab FC kettad riiulid ühendatud FC-AL. LUN identifitseerib virtuaalse kettaid eksporditud väline ladustamine massiivid. Aluseks olevate ketaste tehnoloogiat ja RAID tüüpi sõltub rakendamisest selliste väliste salvestamise massiivid. SAS tuvastab Serial Attached SCSI kettad sobivad riiulid. SATA tuvastab serial ATA kettad SAS riiulid. SCSI tähendab Small Computer System Interface, ja see on lisatud Tagasiühilduvuse varasemate ketas tehnoloogiaid.

-R rpm argument määrab tüüpi kettaid kasutada põhineb nende pöörlemiskiirus on pööret minutis (rpm). On vaja ainult süsteemid, millel kettaid erinevate pöörlemissagedusel. Tüüpilised väärtused pöörlemiskiirus on 5400, 7200, 10000 ja 15000.-R ei saa kasutada koos-d.

ndisks on mitmed kettad kokku, sh pariteedi kettaid. Kettad on uued kokku tulevad basseini vaba kettaid. Väikseim kettaid selles basseini liituda kokku esimese, kui te just @ suurus argument. Suurus on ketta suurus GB ja kettaid, mis jäävad 10% määratletud suurus valitakse kasutamiseks kogumis.

M variant saab määrata, et uus liitkaristus olla peegeldatud (kaks plexes) pärast loomist. Kui see võimalus on antud, siis näidatud kettad jagatakse üle 2 plexes. Vaikimisi on uus liitkaristus ei ole peegelpildis.

-N võimalust saab kasutada, et kuvada käsk, et süsteem täidab, ilma tegelikult teha mingeid muudatusi. See on kasulik väljapanek automaatselt valitud kettaid, näiteks.

Kui kasutate-d disk1 [disk2 ... ] Argument, filer loob kokku kindlaksmääratud vaba kettad disk1, disk2, ja nii edasi. Saate määrata tühikutega eraldatud loetelu disk nimed. Kaks eraldi nimekirjad tuleb täpsustada, kui uus kokku peegeldub. Juhul kui uus liitkaristus on peegelpildis, näidatud kettad tulemusena tuleb võrdne arv kettaid iga uue plex.

Kettad plex ei ole lubatud span vaba basseinid. Selline käitumine võib olla kaalu koos-f valik. Sama võimalust saavad kasutada ka jõudu kasutades plaati, mis ei oleks sobivad pöörlemiskiirus. -F valik on kasutatav vaid siis, kui kasutada-d valik täpsustatakse kettaid kasutada.

Luua Snaplock kokku, täpsustada-L lipp aggr luua käsuga. See lipp on toetatud ainult kui üks Snaplock vastavuse või Snaplock Enterprise litsents. Tüüpi Snaplock kokku loodud, kas vastavuse või Enterprise, määrab paigaldatud Snaplock litsentsi. Kui mõlemad Snaplock täitmine ja Snaplock Enterprise on litsentseeritud, kasutamise-L vastavuse või-L ettevõtte täpsustada soovitud täitematerjali tüüp.

-L language_code argument võib kasutada ainult siis, kui luua traditsiooniline mahtu kasutades valikut-v. Filer loob traditsioonilise märgini poolt määratud keeles keele koodi. Vaikimisi keel on kasutatud filer juur maht. Vaata vol mees lehel nimekirja keelekoode.

aggr hävitada {aggrname | plexname} [-f]

Hävitab kokku nimega aggrname või plex nimega plexname. Pange tähele, et kui määratud kogusumma on seotud traditsiooniliste mahu, siis traditsioonilised maht ise on hävinud ka.

Kui kokku on määratud, kõik plexes kogumis on hävitatud. Nimega kokku ei tohi ka sisaldada paindlik mahus, hoolimata nende mount riik (online, piiratud või offline). Kui plex on määratud, siis plex on hävinud, jättes unmirrored kokku või traditsiooniline maht sisaldavad ülejäänud plex. Enne hävitamist kokku traditsiooniline mahu või plex, kasutaja palutakse kinnitada operatsiooni. -F lipp saab hävitada kokku traditsiooniline mahu või plex küsimata kasutaja.

Kettaid algselt hävitatud objekt muutub varuosad kettaid. Ainult offline agregaatide tavapärastest mahtudest ja plexes võib hävitada.

aggr media_scrub staatus [aggrname | plexname | grupinimi]
[-V]

Prindib meedia puhastamine staatuse nimega kokku, plex või grupp. Kui nime ei ole antud, siis staatus on trükitud kõigi RAID rühmad praegu töötavad meedia nühkima. Staatus sisaldab protsenti-complete ja kas see on peatatud.

-V lipp kuvab kuupäeva ja kellaaega, mil viimase täieliku meedia nühkima lõpetatud, kuupäev ja kellaaeg, mil praegune näiteks meedia puhastamine alustatud, ja hetkeseisu nimega kokku, plex või grupp. Kui nime ei andnud, seda enam verbose staatus on trükitud kõigi RAID rühmade aktiivse meedia puhastamine.

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

-V valik saab liituda victim_aggrname tagasi aggrname moodustada peegelpildis kokku. Tulemuseks on peegelpildis kokku nimega aggrname mis on identne aggrname enne operatsiooni. Victim_aggrname on tegelikult hävitatud. Victim_aggrname peab olema eelnevalt olnud peegeldas koos aggrname, siis eraldatakse kaudu aggr split käsk. Victim_aggrname tuleb offline. Koos-v variant,-f võtit saab liituda aggrname ja vic_ t im_aggrname küsimata kasutaja.

-N võimalust saab kasutada, et kuvada käsk, et süsteem täidab ilma tegelikult teha mingeid muudatusi. See on kasulik väljapanek automaatselt valitud kettaid, näiteks.

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

Võtab kokku nimega aggrname (või plex nimega plexname) offline. Käsk jõustumise naasid. Kui lähteproov on juba riigi piiratud, siis on see juba saadaval andmetele juurdepääsu ja palju järgmisele kirjeldusele ei kohaldata.

Kui kokku sisalda paindlik mahud, siis operatsiooni katkestada, kui filter on hooldusrežiimis.

Va hooldus-režiimis kokku sisaldavad praeguse root maht ei tohi võtta offline. Kokku sisaldavad maht, mis on märgitud, et saada root (kasutades vol võimalusi vol_ n ame root) ka ei saa võtta offline.

Kui kokku on põimitud traditsioonilised maht, mis on CIFS aktsiate kasutajaid tuleks hoiatas enne kokku (ja seega ka kogu traditsioonilist maht) offline. Kasuta-t switch selle eest. Cifsdelaytime argument määrab, mitu minutit viivitada enne varjatud kokku offline, mille jooksul CIFS kasutajate traditsiooniline maht on hoiatanud kuni kaotus teenust. Aeg 0 tähendab võtta kokku offline kohe ilma hoiatusi. CIFS kasutajat võivad kaotada andmeid, kui nad ei ole antud võimalus lõpetada taotluse nõtkelt.

Kui plexname on määratud, siis plex peab olema osa peegelpildis kokku ja nii plexes tuleb online. Enne offlining plex, süsteem loputage kõik sisemiselt puhverdatud andmed seotud keerulised ja luua läbilõige, mis on kirjutatud nii plexes. Snapshot võimaldab tõhusat resynchronization kui plex hiljem tagasi toonud online.

Tehingute arv jõusolevate kokku traditsioonilise maht võib takistada aggr offline õnnestumiseks erinevatel ajavahemikel. Kui selline tegevus on leitud, seal on 1-2. Oodata selliseid toiminguid lõpuni. Kui nad seda ei tee, käsk on katkestatud.

Kontrolli ka failide kokku kaasneva traditsiooniline maht avatud sise ONTAP protsesse. Käsu katkestada, kui mõni leidub.

aggr internetis {aggrname | plexname}
[-F]

Toob kokku nimega aggrname (või plex nimega plexname) online. See käsk jõustub kohe. Kui määratud kokku põimitud traditsioonilised maht maht on samuti toonud ka online.

Kui aggrname on määratud, siis tuleb praegu foorumis, piiratud või Valuutas. Kui lähteproov on välisriigi, siis tuleb native enne tuuakse online. "Võõra" kokku on kokku mis koosneb kettad kolis teise filer ja et pole kunagi toonud võrgus praegu filer. Agregaadid, mis ei ole välisriigi peetakse "emakeel".

Kui lähteproov on vastuolulised, kuid ei ole kaotanud andmeid, kasutaja saab hoiatada ja küsitakse enne tuues kokku online. -F lipp saab alistada sellist käitumist. Soovitav on käivitada WAFL_check (või teha snapmirror initsialiseerida puhul kokku põimitud traditsioonilised maht) enne toovad ole kokku online. Asja ole kokku võrgus suurendab veelgi failisüsteemi korruptsiooni. Kui lähteproov on vastuoluline ja on olnud võimalik andmete kadumise, ei saa viia Interneti kui WAFL_check (või snapmirror initsialiseerida sisse põimitud puhul) on sõita kokku.

Kui plexname on määratud, siis plex peab olema osa online peegelpildis kokku. Süsteem alustab resynchronization of plex osana online töötlemiseks.

aggr võimalusi aggrname [optname optval]

Kuvab valikud, mis on seatud kokku aggrname või seab võimalus nimega optname täitematerjali nimega aggrname väärtuses optval. Käsk jääb kehtima pärast filer käivitub uuesti, nii et ei ole vaja lisada aggr võimalusi käsud / etc / rc faili. Mõni on väärtused, mis on numbrid. Mõni on väärtused, mis võivad olla (mida võib väljendada ka jah, tõsi, või 1) või välja (mis võib väljendada ka mitte, false või 0). Segu suur-ja väiketähed saab kasutada, kui kirjutada väärtus valik. Aggr status käsuga näitab võimalusi, mis on esitatud ühe kokku.

Järgnevalt on kirjeldatud võimalusi ja nende võimalikud väärtused:

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.

Õiguslik väärtusi see valik sõltub raidtype. Näiteks raid_dp võimaldab suuremate RAID rühmad kui raid4. Piirangud ja vaikeväärtused on ka erinevad eri tüüpi filer seadmed ja erinevaid kettaid. Järgmistes tabelites määratleda piirid ja vaikeväärtused raidsize.

  -------------- Raid4 raidsize min default max -------------- R100 2 8 8 R150 2 6 6 FAS250 2 7 14 Muud (FCAL kettaid) 2 8 14 Muud (ATA kettaid) 2 7 7 ---------------------------- raid_dp raidsize min default max ------ -------- R100 3 12 12 R150 3 12 16 muud (FCAL kettad) 3 16 28 muud (ATA kettaid) 3 14 16 ---------- ---- 

Need väärtused võivad muutuda tulevikus releases of Data ONTAP.

raidtype raid4 | raid_dp | RAID0

Määrab tüüpi RAID kasutatakse kaitseks ketas ebaõnnestumisi. Kasuta raid4 annab 1 pariteedi ketta kohta RAID gruppi, samas raid_dp pakub kahte. Selle muutmine kohe muudab RAID tüüp kõik RAID rühmad kokku. Kui ümberehitamise RAID rühmad raid4 et raid_dp iga RAID gruppi algab rekonstrueerimine peale vaba ketta eraldatud 2. `dparity" pariteedi disk.

Selle muutmine muudab ka raidsize et sobivam hinna uus raidtype. Kui värskendage raid4 et raid_dp, raidsize suurendatakse vaikeväärtust raid_dp. Kui alandamise alates raid_dp et raid4, raidsize väheneb suuruse suurim olemasolev RAID gruppi, kui see on vahel vaikimisi väärtust ja tähtaeg raid4. Kui suurim RAID gruppi ületab piirmäära raid4 uus raidsize on seda piiri. Kui suurim RAID gruppi jääb alla vaikeväärtust raid4 uus raidsize saab seda vaikeväärtust. Kui raidsize on juba allpool vaikeväärtust raid4, seda vähendatakse 1.

resyncsnaptime number

Seda võimalust saab määrata peegli resynchronization snapshot sagedus (minutites). Vaikimisi väärtus on 60 minutit.

juur

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

See lugeda ainult valik näitab, et kokku on Snaplock Enterprise kokku. Agregaatide saab määrata ainult Snaplock Enterprise koondnäitajad loomine aega.

snapmirrored välja

Kui SnapMirror on lubatud traditsiooniline maht (SnapMirror ei toeta agregaadid, mis sisaldavad paindlikke mahud), filer määrab automaatselt selle valiku kohta. Määra see valik välja, kui SnapMirror enam kasutada uuendamiseks traditsiooniline maht peegel. Kui seate selle valiku ära, peegel muutub regulaarselt kirjutatav traditsiooniline maht. See valik on võimalik ainult välja lülitatud; ainult filer võib väärtuse muutmiseks seda võimalust põlema läheb.

snapshot_autodelete ON | OFF

Seda võimalust kasutatakse, et määrata, kas snapshot kustutatakse automaatselt sisse aggr. Kui sisse lülitatud, siis pilte saab kustutada aggr tagasi ladustamine on vajalik. Kui välja lülitatud siis pilte ka aggr ei kustutatakse automaatselt taastuda ladustamiseks. Pange tähele, et pilte võib siiski välja jätta muud põhjused, näiteks säilitades snapshot ajakava aggr või kustutada pilte, mis on seotud eritoimingud, et ei vaja enam snapshot. Võimaldada pilte kustutamisele õigeaegselt arvu aggr pilte on piiratud, kui snapshot_autodelete on lubatud. Seetõttu, kui on liiga palju pilte on aggr siis mõned pilte tuleb kustutada varem snapshot_autodelete valik saab olema lubatud.

aggr ümbernimetamine aggrname newname

Nimetab kokku nimega aggrname et newname. Kui see kokku on põimitud traditsioonilised maht, siis see maht nimi on ka muutunud.

aggr piirata aggrname
[-T cifsdelaytime]

Pane kokku nimega aggrname piiratud olekus, alates kas online või offline olekus. Käsk jõustumise naasid.

Kui kokku sisalda paindlik mahud, töö katkeb, kui filter on hooldusrežiimis.

Kui kokku on põimitud traditsioonilised maht, mis on CIFS aktsiate kasutajaid tuleks hoiatas enne piirates kokku (ja seega ka kogu traditsioonilist maht). Kasuta-t switch selle eest. 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 ]

Peatub pariteedi puhastamine on nimega kokku, plex või rühma kui nime ei antud, kõigil RAID rühmad praegu pariteedi puhastamine.

aggr nühkima peatada [aggrname | plexname | grupinimi]

Peatab pariteedi puhastamine on nimega kokku, plex või rühma kui nime ei antud, kõigil RAID rühmad praegu pariteedi puhastamine.

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

Näitab ruumi kasutamine kokku. Erinevalt df, see käsk näitab ruumikasutuse iga paindlik maht jooksul kokku Kui aggrname on määratud, aggr show_space töötab ainult vastava kokku, muidu ta aru ruumikasutuse kõigi agregaadid.

Kõik suurused on kajastatud 1024-baidist plokid, kui ei ole teisiti nõutud üks-h,-k,-m, g, või-t võimalusi. -K,-m, g ja-t valikute skaala iga suurusega seotud valdkonnas toodangut väljendatakse kilobaiti, MB, GB või TB võrra.

Järgmised terminoloogia kasutab käsk aruandlus ruumi.

      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 .

Kui algne kogusumma on piiratud ajal suhe, mille tulemusena kokku ka piiratud. 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.

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

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

aggr show_space -h ag1

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

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

aggr status aggr1 -r

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

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

SEE ALSO

vol , partner , snapmirror , sysconfig .


Table of Contents






















































Tags: , , , , Kategooriad: Manual Pages Tags: , , , ,

cf

July 7th, 2009 Chris Kranz No comments

Sisukord

NAME

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

SYNOPSIS

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

cf nfo [ enable | disable ] disk_shelf

cf nfo status

DESCRIPTION

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

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

OPTIONS

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

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

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

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

partner giveback incomplete, some data may be lost

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

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

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

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

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

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

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

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

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

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

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

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

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

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

nfo status
Displays the current negotiated failover status.

This command is obsolete. Use cf status instead.

SEE ALSO

partner


Table of Contents



Categories: Manual Pages Tags: , , , ,

bootfs

July 7th, 2009 Chris Kranz No comments

Sisukord

NAME

bootfs – boot file system accessor command (ADVANCED)

SYNOPSIS

bootfs chkdsk disk

bootfs core [ -v ] disk

bootfs dir [ -r ] path

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

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

bootfs format drive [ label ]

bootfs info disk

bootfs sync [ -f ] { disk | drive }

bootfs test [ -v ] disk

DESCRIPTION

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

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

OPTIONS

-v
Turns on verbose output.

-r
Recursively lists directories and files.

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

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

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

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

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

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

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

CLUSTER CONSIDERATIONS

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

EXAMPLES

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

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

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

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

bootfs dump 0a.0 110

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

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

bootfs fdisk 0a.0 30

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

bootfs format 0a.0:1: NETAPP

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

bootfs info 0a.0

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

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

bootfs test -v 0a.0

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

SEE ALSO

lae


Table of Contents

Categories: Manual Pages Tags: , , , ,

boot

July 7th, 2009 Chris Kranz No comments

Sisukord

NAME

boot – directory of Data ONTAP executables

SYNOPSIS

/etc/boot

DESCRIPTION

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

FILES

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

SEE ALSO

lae


Table of Contents

Copyright © 1994-2008 NetApp, Inc. Legal Information

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

Categories: Manual Pages Tags: , , , ,

bmc

July 7th, 2009 Chris Kranz No comments

Sisukord

NAME

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

SYNOPSIS

bmc help

bmc reboot

bmc setup

bmc status

bmc test autosupport

DESCRIPTION

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

OPTIONS

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

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

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

status
Display the current status of the BMC.

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

CLUSTER CONSIDERATIONS

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

EXAMPLES

bmc status

might produce:

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

SEE ALSO

setup , options

MÄRKUSED

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


Table of Contents

Copyright © 1994-2008 NetApp, Inc. Legal Information

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

Categories: Manual Pages Tags: , , , ,

backuplog

July 7th, 2009 Chris Kranz No comments

Sisukord

NAME

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

SYNOPSIS

/etc/log/backup

DESCRIPTION

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

The following are the events filer monitors:

Start
Dump/restore starts.

Restart
Restart of a dump/restore.

End
Dump/restore completes successfully.

Abort
The operation aborts.

Error
Dump/restore hits an unexpected event.

Valikud
Logs the options as users specify.

Tape_open
Output device is opened successfully.

Tape_close
Output device is closed successfully.

Phase_change
As dump/restore completes a stage.

Dump specific events:

Snapshot
When the snapshot is created or located.

Base_dump
When a valid base dump entry is located.

Logging events:

Start_logging Logging begins.

Stop_logging
Logging ends.

Each event record is in the following format:

TYPE TIME_STAMP IDENTIFIER EVENT (EVENT_INFO)

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

TIME_STAMP
Shows date and time at which event occurs.

IDENTIFIER
Unique ID for the dump/restore.

EVENT
The event name.

EVENT_INFO
Event specific information.

A typical event record message looks like:

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

In the particular example:

TYPE
= dmp

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

IDENTIFER
= /vol/vol0/ home(5)

EVENT
= Start

EVENT_INFO
= level 0, NDMP

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

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

FILES

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

SEE ALSO

dump , restore , options


Table of Contents

Categories: Manual Pages Tags: , , , ,

backup

July 7th, 2009 Chris Kranz No comments

Sisukord

NAME

backup – manages backups

SYNOPSIS

backup status [ <ID> ]

backup terminate <ID>

DESCRIPTION

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

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

dump
runs natively on the filer.

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

RESTARTABLE A failed dump that can be restarted.

USAGE

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

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

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

Liik
Either dump or NDMP.

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

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

Level
The level of the backup.

Path
Points to the tree that is being backed up.

An example of the backup status command output:

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

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

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

SEE ALSO

prügila


Table of Contents



Categories: Manual Pages Tags: , , , ,

autosupport

July 7th, 2009 Chris Kranz 2 comments

Sisukord

NAME

autosupport – notification daemon

SYNOPSIS

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

DESCRIPTION

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

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

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

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

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

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

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

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

The setup command tries to configure autosupport as follows:

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

Setup also queries for autosupport.from information.

OPTIONS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

CONTENTS

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

Generation date and timestamp

Software Version

System ID

Hostname

SNMP contact name (if specified)

SNMP location (if specified)

Partner System ID (if clustered)

Partner Hostname (if clustered)

Cluster Node Status (if clustered)

Console language type

sysconfig -a output

sysconfig -c output

sysconfig -d output

System Serial Number

Software Licenses (scrambled prior to transmission)

Option settings

availtime output

cf monitor all output (if clustered)

ic stats performance output (if clustered with VIA)

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

snet stats -v output (if clustered with SNET)

ifconfig -a output

ifstat -a output

vlan stat output

vif status output

nis info output

nfsstat -c output (if licensed)

cifs stat output (if licensed)

cifs sessions summary (if licensed)

cifs sessions output (if licensed and enabled)

cifs shares summary (if licensed)

cifs shares output (if licensed and enabled)

vol status -l (if cifs is licensed)

httpstat output

vfiler status -a output (if licensed)

df output

df -i output

snap sched output

vol status -v output

vol status output

vol status -c output

vol scrub status -v output

sysconfig -r output

fcstat fcal_stats output

fcstat device_map output

fcstat link_stats output

ECC Memory Scrubber Statistics

ems event status output

ems log status output

registry values

perf report -t output

storage show adapter -a output

storage show hub -a output

storage show disk -a output

storage show fabric output

storage show switch output

storage show port output

EMS log file (if enabled)

/etc/messages content

Parity Inconsistancy information

WAFL_check logs

TYPES

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

BATTERY_LOW!!!
LOG_ALERT

BMC_EVENT: BUS ERROR
LOG_ERR

BMC_EVENT: POST ERROR
LOG_ERR

CLUSTER DOWNREV BOOT FIRMWARE
LOG_CRIT

CLUSTER ERROR: DISK/SHELF COUNT MISMATCH LOG_EMERG

CLUSTER GIVEBACK COMPLETE
LOG_INFO

CLUSTER TAKEOVER COMPLETE AUTOMATIC
LOG_ALERT

CLUSTER TAKEOVER COMPLETE MANUAL
LOG_INFO

CLUSTER TAKEOVER FAILED
LOG_INFO

CONFIGURATION_ERROR!!!
LOG_ALERT

CPU FAN WARNING - [fan]
LOG_WARNING

DEVICE_QUALIFICATION_FAILED
LOG_CRIT

DISK CONFIGURATION ERROR
LOG_ALERT

DISK RECONSTRUCTION FAILED!!
LOG_ALERT

DISK_FAIL!!! - Bypassed by ESH
LOG_ALERT

DISK_FAIL!!!
LOG_ALERT

DISK_FAILURE_PREDICTED!!!
LOG_ALERT

DISK_FIRMWARE_NEEDED_UPDATE!!!
LOG_EMERG

DISK_IO_DEGRADED
LOG_WARNING

DISK_LOW_THRUPUT
LOG_NOTICE

DISK_RECOVERED_ERRORS
LOG_WARNING

DISK_SCRUB!!!
LOG_EMERG

FC-AL LINK_FAILURE!!!
LOG_ERR

FC-AL RECOVERABLE ERRORS
LOG_WARNING

OVER_TEMPERATURE_SHUTDOWN!!!
LOG_EMERG

OVER_TEMPERATURE_WARNING!!!
LOG_EMERG

PARTNER DOWN, TAKEOVER IMPOSSIBLE
LOG_ALERT

POSSIBLE BAD RAM
LOG_ERR

POSSIBLE UNLINKED INODE
LOG_ERR

REBOOT (CLUSTER TAKEOVER)
LOG_ALERT

REBOOT (after WAFL_check)
LOG_INFO

REBOOT (after entering firmware)
LOG_INFO

REBOOT (after giveback)
LOG_INFO

REBOOT (halt command)
LOG_INFO

REBOOT (internal halt)
LOG_INFO

REBOOT (internal reboot)
LOG_INFO

REBOOT (panic)
LOG_CRIT

REBOOT (power glitch)
LOG_INFO

REBOOT (power on)
LOG_INFO

REBOOT (reboot command)
LOG_INFO

REBOOT (watchdog reset)
LOG_CRIT

REBOOT
LOG_INFO

SHELF COOLING UNIT FAILED
LOG_EMERG

SHELF COOLING UNIT FAILED
LOG_WARNING

SHELF_FAULT!!!
LOG_ALERT

SNMP USER DEFINED TRAP
LOG_INFO

SPARE_FAIL!!!
LOG_ALERT

SYSTEM_CONFIGURATION_CRITICAL_ERROR
LOG_CRIT

SYSTEM_CONFIGURATION_ERROR
LOG_ERR

UNDER_TEMPERATURE_SHUTDOWN!!!
LOG_EMERG

UNDER_TEMPERATURE_WARNING!!!
LOG_EMERG

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

WAFL_check!!!
LOG_ALERT

WEEKLY_LOG
LOG_INFO

[EMS event]
LOG_INFO

[fan] FAN_FAIL!!!
LOG_ALERT

[mini core]
LOG_CRIT

[power supply failure]
LOG_ALERT

[power supply] POWER_SUPPLY_DEGRADED!!!
LOG_ALERT

[shelf over temperature critical]
LOG_EMERG

CLUSTER CONSIDERATIONS

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

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

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

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

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

SEE ALSO

options , partner , setup , hosts , RFC821


Table of Contents






























































Categories: Manual Pages Tags: , , , ,

auditlog

July 7th, 2009 Chris Kranz No comments

Sisukord

NAME

auditlog – contains an audit record of recent administrative activity

SYNOPSIS

<logdir>/auditlog

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

DESCRIPTION

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

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

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

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

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

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

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

ja

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

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

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

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

local7.*
@1.2.3.4

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

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

local7.*
/var/logs/filer_auditlogs

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

FILES

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

SEE ALSO

options , syslog.conf


Table of Contents

Categories: Manual Pages Tags: , , , ,

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

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