NetApp Technical Dnevnik

NetApp so sami dati dovoljenje, da me znova njihov človek straneh tukaj. Še vedno potrebujejo malo urejanje gor, ampak že zaradi same količine pomeni, da bomo mi, da nekaj časa, da se jih vse sortirati in navzkrižno sklicuje pravilno, prosim oprostite vse vizualne vprašanja za trenutek. Napisal sem hitro razčlenjevanju orodje, da bi dobili vse informacije o tem, tako da je lahko nekaj vprašanj, ki izhajajo iz tega še vedno.

Vedno sem si všeč način, da so njihove funkcije PHP strani, ki daje uporabnikom možnost, da dajo svoje pripombe neposredno na njih. To omogoča ljudem, da zapusti povratne informacije o funkcijah in orodja, pa tudi spremljanje z nekaj dodatnimi uporabe ali sintakso za ukaze, ki niso nujno jasno objavljena. Upajmo, da se lahko ta vir nazaj v NetApp, da izboljšajo svoje dokumentacije.

Jaz bi vsekakor želel spodbuditi ljudi, da dajo pripombe na moški strani s čimerkoli, ki so lahko koristni, in upajmo, da gradijo v tem koristno malo oddelek reference. Hvala lepa še enkrat za NetApp folk mi pomagali s tem.

General , Manual Pages commands , man , manual , NetApp , ONTAP

Kazalo

NAME

SYNOPSIS

OPIS

The aggr command family is new in Data ONTAP 7.0. The vol command family provided control over the traditional vol_ u mes that fused a single user-visible file system and a single RAID-level storage container (aggregate) into an indivisible unit, and still does. To allow for more flexible use of storage, aggregates now also support the ability to contain multiple, independent user-level file systems named flexible volumes .

Data ONTAP 7.0 fully supports both traditional and flexible volumes. The aggr command family is the preferred method for managing a filer's aggregates, including those that are embedded in traditional volumes.

Note that most of the aggr commands apply equally to both the type of aggregate that contains flexible volumes and the type that is tightly bound to form a traditional volume. Thus, the term aggregate is often used here to refer to both storage classes. In those cases, it provides a shorthand for the longer and more unwieldy phrase "aggregates and traditional volumes”.

Aggregates may either be mirrored or unmirrored. A plex is a physical copy of the WAFL storage within the aggregate. A mirrored aggregate consists of two plexes; unmirrored aggregates contain a single plex. In order to create a mirrored aggregate, you must have a filer configuration that supports RAID-level mirroring. When mirroring is enabled on the filer, the spare disks are divided into two disk pools. When an aggregate is created, all of the disks in a single plex must come from the same disk pool, and the two plexes of a mirrored aggregate must consist of disks from separate pools, as this maximizes fault isolation. This policy can be overridden with the -f option to aggr create , aggr add and aggr mirror , but it is not recommended.

An aggregate name can contain letters, numbers, and the underscore character(_), but the first character must be a letter or underscore. A combined total of up to 200 aggregates (including those embedded in traditional volumes) can be created on each filer.

A plex may be online or offline. If it is offline, it is not available for read or write access. Plexes can be in combinations of the following states:

normal All RAID groups in the plex are functional.

failed At least one of the RAID groups in the plex has failed.

empty The plex is part of an aggregate that is being created, and one or more of the disks targeted to the aggregate need to be zeroed before being added to the plex.

active The plex is available for use.

inactive
The plex is not available for use.

resyncing
The Plex je vsebina trenutno zastarela in so v postopku resynchronized z vsebino drugih plex agregata (velja za agregate samo zrcalno).

dodajanje diskov
Diski se dodajajo RAID plex je skupina (-e).

out-of-datum
To stanje se pojavi samo v agregate zrcalno kadar je eden od plexes ni uspelo. Ne-ne plex bo v tem stanju, če je bilo treba resynchronized v času po drugi Plex ni uspelo.

Plex je poimenovana z imenom agregata, znak za ločevanje poševnica in ime Plex. Sistem samodejno izbere plex imena v času nastanka. Na primer, prvi plex ustvarjena v skupni aggr0 se aggr0/plex0.

Agregat se lahko na spletu, omejiti ali brez povezave. Ko je offline agregat, ne brati ali pisati, je dostop dovoljen. Ko je agregat omejena, so nekateri ukrepov, ki so (kot je agregat kopija, pariteta recomputation ali RAID obnovo), vendar dostop do podatkov ni dovoljeno. Agregati, ki niso del tradicionalne prostornine je mogoče samo omejiti ali offlined, če ne vsebujejo prilagodljiv obseg.

Agregati so lahko v kombinacije naslednjih držav:

aggr agregat je sodobna agregata, ampak je lahko vsebuje nič ali bolj prilagodljiv obseg.

kopiranje
Agregat je trenutno cilj seštevek aktivnega delovanja aggr kopijo.

degradiranih
Skupni vsebuje vsaj eno degradiranih RAID skupino, ki ga ne rekonstruirali.

tuji
Lističi, da so skupni vsebuje so preselili v trenutno filer iz drugega filer.

narašča
Diski so v postopku doda agregat.

inicializacija
Agregat je v postopku initialized.

neveljaven
Agregat ne vsebuje obseg in nihče se lahko doda. Običajno se to zgodi šele potem, ko je prekinjena skupno operacijo kopirati.

likanje
WAFL preverjanje skladnosti, ki se izvaja na ta agregat.

ogledalo degradiranih
Agregat je agregat zrcalno, in eden od njenih plexes je offline ali resyncing.

zrcali
Agregat je izpričano in vse svoje RAID skupine so funkcionalni.

potrebe preverjanja
WAFL preverjanje skladnosti, je treba opraviti na agregat.

delna
Vsaj en disk je bilo ugotovljeno za agregat, vendar pa dve ali več diskov manjka.

RAID0 agregat je sestavljen iz RAID-0 (brez pariteta) RAID skupine (V-Series in NetCache samo).

raid4 agregat je sestavljen iz RAID-4 RAID skupine.

raid_dp
Agregat je sestavljen iz RAID-DP (Double Parity) RAID skupin.

rekonstruirati
At least one RAID group in the aggregate is being reconstructed.

redirect
Aggregate reallocation or file reallocation with the -p option has been started on the aggregate. Read performance to volumes in the aggregate may be degraded.

resyncing
One of the plexes of a mirrored aggregate is being resynchronized.

snapmirrored
The aggregate is a snapmirrored replica of another aggregate. This state can only arise if the aggregate is part of a traditional volume.

trad The aggregate is fused with a single volume. This is also referred to as a traditional volume and is exactly equivalent to the volumes that existed before Data OnTAP 7.0. Flexible volumes can not be created inside of this aggregate.

verifying
A RAID mirror verification operation is currently being run on the aggregate.

wafl inconsistent
The aggregate has been marked corrupted. Please contact Customer Support if you see an aggregate in this state.

UPORABA

 add mirror restrict undestroy copy offline scrub verify create online show_space destroy options split media_scrub rename status 

|

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

Če je-g možnost ne uporablja, so diski doda nazadnje ustvaril RAID skupina util, da je poln, nato pa sta eno ali več novih RAID skupine se ustanovijo in ostalih diskov se dodajo nove skupine. Vsak drug obstoječi RAID skupine, ki niso v celoti ostane delno napolnjena.

-G možnost omogoča specifikacijo skupine RAID (na primer, rg0), na katero se navedeno diske je treba dodati, ali metodo, s katero so diski dodajo nove ali obstoječe skupine RAID.

Če je-g možnost uporabljena za določitev RAID skupine, mora ta skupina RAID že obstajajo. Diski se dodajo, da je util skupini RAID je poln. Vse ostale diski so prezrti.

Če je-g možnost, sledijo novi, Data ONTAP ustvari eno ali več novih RAID skupine in dodaja diskov, da jih, tudi če bi diske uvrstiti v obstoječo skupino RAID. Vsi obstoječi RAID skupine, ki niso v celoti še vedno delno napolnjena. Ime nove RAID skupine so samodejno izbrani. Ni mogoče določiti imena za novo RAID skupine.

Če je-g možnost, sledijo vse, Data ONTAP dodaja določene diskov z obstoječimi skupinami RAID prvi. Po vseh obstoječih RAID skupine so polne, ustvarja eno ali več novih RAID skupine in dodaja določene diskov na nove skupine.

-N možnost se lahko uporablja za prikaz ukaz, da bo sistem izvede, ne da bi dejansko pripravi kakršne koli spremembe. To je uporabno za prikazovanje samodejno izbrana diskov, na primer.

Privzeto filer napolni eno skupino z RAID diski Pred začetkom drugega RAID skupine. Recimo, da skupni trenutno ima eno RAID skupino 12 diskov in RAID njeno skupino znaša 14. Če dodamo 5 diskov do tega agregata, bo to eno RAID skupino s 14 diskov in RAID drugo skupino, s 3 diski. Filer ne enakomerno razdeli med diskov RAID skupinami.

Ne morete dodati diskov v skupni zrcalno če je eden od plexes ni dosegljiv.

Diskov v plex ni dovoljeno span disk bazenih. To vedenje morejo nadomestiti z-f zastave, kadar se uporablja skupaj z-d argument v seznam diskov dodati. The-f zastave, v kombinaciji s-d, se lahko uporablja tudi za silo dodajanje diskov, ki imajo hitrost vrtenja, ki se ne ujema, da je za večino obstoječih diskov v agregat.

aggr kopiranje prekiniti [-h] operation_number | vse

Odpove agregat operacije kopijo. Opera_ t ion_number parameter, ki določa, da prekine operacijo. Če določite vse, prenehajo veljati vsi skupni aktivni kopiranje.

aggr kopiranje začetek
[-S |-ov posnetek] [-C]
vir cilj

Kopije vseh podatkov, vključno s posnetki in prilagodljiv obseg, iz enega agregata v drugo. Če se uporabi-S zastavo, ukaz kopira vse posnetke v viru agregat do cilja agregat. Če želite določiti posebno posnetek za kopiranje, uporabite-s zastave, ki mu sledi ime posnetka. Če uporabljate niti-niti-S s zastave na ukaz, filer ustvari posnetek v trenutku, ko se izvrši kopija aggr začetek ukaz in kopije le, da je posnetek do cilja agregat.

-C zastave se zahteva, če je vir agregat imel free-prostor defragmentation izvajajo na to, ali bo cilj skupne prosto-prostor defragmented. Free-prostor defragmentation se lahko izvede na agregat z ukazom prerazporedi.

Agregat kopij se lahko izvede samo med agregati, ki gostijo prilagodljive količine. Agregati, ki so vgrajeni v tradicionalne količine ne morejo sodelovati.

Agregati vira in cilja je mogoče na istem filer ali drugačen filers. Če je vir ali cilj agregat je na filer, ki ni tista, na kateri vnesete začetni kopija aggr ukaz, navedite skupno ime v filer_name: aggre_ g ate_name format.

The filers so vključeni v skupni kopija mora izpolnjevati naslednje pogoje za kopijo aggr ukaz začetek je lahko uspešno zaključil:

Vir agregat mora biti na spletu in skupni cilj mora biti omejen.

Če je kopija je med dvema filers treba vsako filer opredeli kot zaupanja vredno vrsto drugih filer. To pomeni, da mora biti filer ime se v / etc / hosts.equiv datoteke druge filer.

Če je kopija je na isti filer mora, je treba vključiti v localhost / The filer je etc / hosts.equiv datoteke. Prav tako mora biti loopback naslov v / filer je etc / hosts. V nasprotnem primeru filer ne more poslati pakete, da se prek loopback naslov, ko poskušajo kopiranje podatkov.

Uporabna prostora na disku v skupni cilj mora biti večje ali enako uporabne prostora na disku vira agregata. Uporabite df-pathname ukaz videti količino uporabnega prostora na disku posameznega agregata.

Vsak izvod aggr začetek ukaz ustvarja dve skupni kopiranje: enega za branje podatkov iz vira agregat in eno za zapisovanje podatkov na destinacijo agregat. Vsak filer podpira do štiri simultano agregat kopiranje.

aggr kopija statusa [operation_number]

Prikaže napredka enega ali vseh aggr kopiranje. Operacije so oštevilčene od 0 do 3.

Restart checkpoint informacije za vse prenose, je prav tako prikazana.

aggr kopirati plin [operation_number] vrednost

Nadzira izvajanje operacije kopije aggr. Vrednost se giblje od 10 (polni hitrosti) do 1 (ene desetine polno hitrostjo). Privzeta vrednost je ohranila v aggr.copy.throttle filer je možnost in je nastavljena 10 (polno hitrostjo), v tovarni. Prijavite se lahko opravljanje vrednost za operacijo, ki jo določi operation_number parameter. Če ne določite delovanje številke v izvodu aggr ukaz plin, ukaz velja za vse kopiranje aggr.

Uporabite ta ukaz za omejitev hitrosti delovanja kopije aggr, če sumite, da je kopija aggr delovanje povzroča težav z delovanjem na vašem filer. Zlasti je plin, namenjene za pomoč omejiti CPU uporaba delovanja kopije aggr. Ni ga mogoče uporabiti za omrežja uskladili vzorcev porabe pasovne širine.

Kopija aggr plin ukaz samo vam omogoča, da nastavite hitrost delovanja kopija aggr ki je v teku. Če želite nastaviti privzete kopije aggr hitrost, ki se uporabljajo za prihodnje operacije kopijo, uporabite možnosti ukaz za nastavitev aggr.copy.throttle možnost.

aggr ustvariti aggrname
[-F]
[-M]
[-N]
[-T raidtype]
[-R raidsize]
[T-disk tipa]
[-R rpm]
[-L [skladnost | podjetja]]
[-V]
[-L jezikovno-code]
{Ndisks [@ velikost]

|

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

Vgrajen agregat je mogoče ustvariti v okviru tradicionalnega obsega uporabo-v možnost. Ne sme vsebovati prilagodljivo količine.

Redna agregat, ne da bi ustvaril-v možnost, lahko vsebuje le fleksibilno količine. To se ne more vključiti v tradicionalni obsega, in ne vsebuje količino takoj po nastanku. Nova prilagodljiva količine lahko ustvarite s vol ustvarjajo ukaz.

-T raidtype argument določa vrsto RAID skupina (-e), ki se uporablja za ustvarjanje agregat. Možni tipi so raid4 skupina RAID za RAID-4, raid_dp za RAID-DP (Double Parity), in RAID0 za enostavne črtaste podobe brez zaščite paritete. Privzeto raidtype za agregate in tradicionalne količine na filers je raid_dp. Nastavitev raidtype ni dovoljeno na V-Series sistemov; neplačila RAID0 se vedno uporablja.

-R raidsize argument določa največje število diskov RAID v vsaki skupini, v agregat. Vrednosti največ in neplačila raidsize so odvisne od platforme, ki temelji na zmogljivost in zanesljivost vidikov. Glej aggr možnosti raidsize za več podrobnosti.

The-T disk tipa argument določa vrsto diskov za uporabo pri ustvarjanju novega agregata. To je potrebno samo za sisteme, priključene na diske različnih vrst. Možni tipi so disk: ATA, FCAL, LUN, SAS, SATA in SCSI. Mešanje različnih vrst diskov v enem agregat ni dovoljeno.-T se ne morejo uporabljati skupaj s-d.

Disk tip opredeljuje disk tehnologijo in povezljivost tipa. ATA identificira ATA diske bodisi z IDE ali serijski ATA vmesnika v policah povezani v FCAL (Fibre Channel razsojalo Loop). FCAL opredeljuje FC diskov na policah povezani v FC-AL. LUN opredeljuje virtualne diske izvozi iz zunanja polja za shranjevanje. Osnovni disk in tehnologijo RAID tip je odvisen od izvajanja takšnih zunanjih shranjevanje nizi. SAS opredeljuje Serial Attached SCSI diskov v ujemanje police. SATA identificira serijsko diskov ATA v policah SAS SCSI je kratica za Small Computer System Interface, in je vključen za združljivost. s starejšimi tehnologijami disk.

The-R rpm argument določa vrsto diskov za uporabo, ki temelji na njihovi vrtljajev v vrtljajih na minuto (rpm). To je potrebno le na sistemih, ki imajo diske z različnimi hitrostmi vrtenja. Tipične vrednosti za hitrost vrtenja so 5400, 7200, 10000 in 15000.-R, ni mogoče uporabljati skupaj z-d.

ndisks je število diskov v agregat, vključno s pariteto diskov. Lističi, v tem novoustanovljenim agregat prihaja iz bazena rezervnih diskov. Najmanjši diskov v tem bazenu se pridružijo skupni prvi, razen če določite argument @ velikosti. Velikosti je disk velikosti v GB, in diski, ki so v 10% od določene velikosti, bodo izbrani za uporabo v agregat.

The-m opcija se lahko uporabi za navedeno, da je novi agregat se zrcali (imajo dve plexes) po ustvarjanju. Če je podana ta možnost, se bo nato navedeno diske razdeli med oba plexes. Privzeto je, da novi agregat ne bo zrcalno.

The-n možnost se lahko uporablja za prikaz ukaz, da se bo sistem izvede, ne da bi dejansko pripravi kakršne koli spremembe. To je uporabno za prikazovanje samodejno izbrana diskov, na primer.

Če uporabljate-d disk1 [disk2 ... ] Argument je filer ustvarja agregat s predpisanim nadomestnih diskov disk1, disk2, in tako naprej. Določite lahko prostorsko ločen seznam imen disk. Dve ločeni seznami, je treba opredeliti, če novi agregat je bilo razvidno. V primeru, da je novi agregat je bilo razvidno, mora biti naveden diskov za posledico enako število diskov na vsaki novi Plex.

Diskov v plex ni dovoljeno span rezervnih bazenov. To vedenje morejo nadomestiti z-f opcijo. Enako možnost se lahko uporablja tudi za silo z uporabo diskov, ki nimajo ujemanje hitrost vrtenja. The-f opcijo ima učinek le, če se uporablja s-d možnost, ki določa diskov za uporabo.

Če želite ustvariti SnapLock agregat, določite-L zastava z aggr ustvarjajo ukaz. Ta zastava je podprta samo, če je bilo izdano dovoljenje bodisi SnapLock skladnosti ali SnapLock Enterprise. Vrsto SnapLock ustvarili skupni, bodisi skladnosti ali Enterprise, se določi z nameščeno licenco SnapLock. Če so licenco tako Skladnost SnapLock in SnapLock Enterprise, uporabite-L skladnost ali-L podjetja, da določite želeno vrsto agregata.

-L language_code argument se lahko uporabi samo pri ustvarjanju tradicionalnega obsega z izbiro-v. The filer ustvarja tradicionalne prostornine z jezikom, ki ga določi jezikovno kodo. Privzeto je jezik, ki ga root filer obsega. Oglejte si vol človek stran za seznam jezikovnih kod.

aggr uničiti {aggrname | plexname} [-f]

Uniči agregat imenovan aggrname, ali Plex imenom plexname. Upoštevajte, da če je določen skupni vezana na tradicionalno obsega, potem je tradicionalna prostornina sam uničeno, kot dobro.

Če je določena agregat, so uničeni vsi plexes v agregat. Imenovanega tudi agregat ne sme vsebovati prilagodljivo količine, ne glede na njihovo stanje mount (online, omejena ali brez povezave). Če je določeno plex, je plex uničena, tako da unmirrored agregat ali tradicionalnih prostornine, ki vsebuje preostalih Plex. Pred uničuje agregat, tradicionalne prostornine ali plex, je uporabnik pozove k potrditvi operacije. -F zastave se lahko uporabljajo za uničevanje agregat, tradicionalni volumen ali plex ne da bi od uporabnika.

Diskov v prvotno uničil objekt postane rezervne diske. Samo offline agregatov, tradicionalne količine in plexes je mogoče uničiti.

aggr media_scrub statusa [aggrname | plexname | GROUPNAME]
[-V]

Natisne mediji ščetkanje status imenom agregata, plex, ali skupino. Če je podana brez imena, potem je stanje natisne za vse RAID skupine trenutno izvaja medijski čiščenje. Status vključuje odstotkov, popolna in ali je začasno razveljavljen.

The-v zastavo prikaže datum in čas, ko čiščenje končano zadnje polno medijev, datum in čas, ko ščetkanje začetka tega primerek medijev, in trenutno stanje poimenovali agregata, plex, ali skupino. Če je podana brez imena, je to bolj verbose statusa tiskani RAID za vse skupine z aktivnimi grmičevja mediji.

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

Ta možnost velja samo za agregate, ki so vgrajeni v tradicionalne količine. To povzroči, da datotečni sistem, da ostanejo enake velikosti in ne raste ali skrči, če je pretrgana volumen SnapMirrored odnos, ali dodate aggr se izvaja na njem. Ta možnost se samodejno nastavi, da se o tem, kdaj tradicionalni volumen postane volumen SnapMirrored. Še naprej bo na po tem, ko je izdal ukaz snapmirror odmor za tradicionalne volumen. To omogoča tradicionalni volumen, ki ga SnapMirrored nazaj vir ne da bi morali dodati diskov na vir tradicionalne prostornine. Če tradicionalni obseg velikost je večja od velikosti datotečnega sistema, bo izklopite to možnost silo datotečni sistem, da raste z velikostjo tradicionalnega obsega. Privzeta nastavitev je off.

ignore_inconsistent na | off

Ta ukaz se lahko uporablja samo v načinu za vzdrževanje. Če nastavite to možnost, saj omogoča agregat, ki vsebuje koren volumen, ki ga na spletu, vložena škorenj, čeprav je to v neskladju. Uporabnik je opozoril, da lahko postavitve na spletu pred teče WAFL_check ali wafliron povzroči nadaljnje nedoslednosti datotečnem sistemu.

nosnap na | off

Če je ta možnost vključena, jo onemogoči samodejni posnetke na agregat. Privzeta nastavitev je off.

raidsize številka

Vrednost te možnosti je največja velikost RAID skupine, ki se lahko ustvari v agregat. Spreminjanje vrednosti te možnosti ne bo povzročila obstoječe skupine RAID, da raste ali skrči, ampak bodo vplivale samo na to, ali bo bolj diskov dodati zadnjo obstoječo skupino RAID in kako velik bo novih skupin RAID biti.

Pravna vrednosti za to možnost, odvisno od raidtype. Na primer, raid_dp omogoča večje skupine RAID kot raid4. Mejne vrednosti in privzete vrednosti so tudi različne za različne vrste filer aparatov in različne vrste diskov. Po tabelah opredelijo omejitve in privzete vrednosti za raidsize.

   -------------- Raid4 raidsize min privzeta max -------------- R100 R150 8 2 8 2 6 6 FAS250 2 7 14 drugih (FCAL diskov) 2 8 14 drugih (ATA diski) 2 7 7 -------------- -------------- raid_dp raidsize min privzeta max ------ -------- R100 R150 3 12 12 3 12 16 drugo (FCAL diskov) 3 16 28 drugo (ATA diskov) 3 14 16 ---------- ---- 

raidtype raid4 | raid_dp | RAID0

Nastavi tip RAID se uporablja za zaščito pred disk napak. Uporaba raid4 da en paritetni disk na skupino RAID, medtem ko raid_dp ponuja dve. Spreminjanje to možnost takoj spremeni RAID tip RAID vseh skupin v skupnem. Pri nadgradnji RAID skupin iz raid4 do raid_dp, vsaki skupini RAID začne obnovo na rezervni disk, dodeljenih za drugi `dparity" disk paritete.

Spreminjanje te možnosti tudi spremembe raidsize na primernejše vrednosti za nove raidtype. Pri nadgradnji raid4 do raid_dp bo, raidsize poveča na privzeto vrednost za raid_dp. Ko deklasiranje od raid_dp do raid4 bo, raidsize se je zmanjšala na velikost največje obstoječe skupine RAID, če je med privzete vrednosti in omejitev za raid4. Če je največja RAID skupina je nad mejo za raid4, bo novi raidsize se ta mejna. Če je največja RAID skupina je pod privzeto vrednost za raid4, bo novi raidsize se te privzete vrednosti. Če raidsize že pod privzeto vrednost za raid4 bo, se zmanjša za 1.

resyncsnaptime številka

Ta možnost se uporablja za določitev posnetek ogledalo ponovno sinhronizacijo frekvence (v minutah). Privzeta vrednost je 60 minut.

koren

Če je ta možnost nastavljena na tradicionalno obsega, potem je učinek enak, kot je opredeljena v vol moški strani. V nasprotnem primeru, če je ta možnost nastavljena na agregat, ki lahko vsebuje prilagodljive količine, je potem, da je agregat označena kot tista, ki bo prav tako vsebuje koren prilagodljivo prostornino ob ponovnem zagonu. Ta možnost se lahko uporablja samo eno skupno ali tradicionalne prostornine v določenem trenutku. Obstoječi skupni koren ali tradicionalne prostornine bo postala nekorenski podjetja po reboot.

Dokler se sistem ponovno zagnan, bo prvotna skupna in / ali tradicionalne obseg še naprej kažejo koren kot eno od možnosti, in novi skupni koren ali tradicionalnih prostornine bo pokazal diskroot kot možnost. Na splošno velja, da je skupna možnost diskroot je tista, ki bo vsebovala koren prilagodljiv volumen po naslednji reboot.

Edini način, da odstranite koren status agregata ali tradicionalna prostornina je določiti koren možnost na drugem agregat ali tradicionalnih prostornine.

snaplock_compliance

To branje edina možnost, nakazuje, da je agregat Skladnost SnapLock agregat. Agregati so lahko le določene SnapLock skladnosti agregatov v času nastanka.

snaplock_enterprise

To branje edina možnost, nakazuje, da je agregat Enterprise SnapLock agregat. Agregati so lahko le določene SnapLock Enterprise agregatov v času nastanka.

snapmirrored off

Če je SnapMirror omogočena za tradicionalne volumen (SnapMirror ni podprta za agregate, ki vsebujejo prilagodljive količine), filer samodejno nastavi ta možnost, da na. Nastavite to možnost na off, če SnapMirror ni več treba uporabiti za posodobitev tradicionalne ogledalo prostornine. Po nastavitev te možnosti na off, ogledalo postane redno pisati tradicionalni volumen. Ta možnost je mogoče nastaviti le na off, samo filer lahko spremenite vrednost te možnosti iz off na on.

snapshot_autodelete na | off

Ta možnost se uporablja za določitev, ali so posnetek samodejno izbriše v aggr. Če naj bi na lahko nato posnetke črta v aggr, da si opomore skladiščenja, kot je potrebno. Če je nastavljen na off nato pa so posnetki v aggr ni samodejno izbriše, da si opomore shranjevanje. Upoštevajte, da lahko posnetke še vedno treba črtati iz drugih razlogov, kot je ohranjanje posnetek razpored aggr, brisanje posnetkov, ki so povezane z določenimi postopki, da se nič več ne potrebujejo posnetek. Da bi posnetke, ki se črtajo pravočasno število posnetkov aggr je omejen, kadar je omogočeno snapshot_autodelete. Zaradi tega, če je preveč posnetke v aggr mora nato nekaj posnetkov se črta, preden se lahko omogočite snapshot_autodelete možnost.

aggr preimenovanje aggrname newname

Preimenuje agregat imenovan aggrname na newname. Če je ta agregat vgrajen v tradicionalni volumen, nato pa je, da je količina ime spremenili tudi.

aggr omejujejo aggrname
[-T cifsdelaytime]

Postavite agregat poimenovali aggrname v omejenem stanju, od bodisi online ali offline stanju. Ukaz stopi v veljavo, preden se vrne.

Če skupni vsebuje vse prilagodljiva obsegu, je operacija prekinjena, razen če filer je v načinu za vzdrževanje.

Če se skupni vgrajeni v tradicionalni obsega, ki je CIFS delnic, je treba opozoriti uporabnike pred omejujejo agregat (in s tem celoten obseg traditional). Uporabite-t stikalom za to. Cifsdelaytime argument določa število minut do zamude preden vgrajeni agregat offline, v tem času CIFS uporabniki tradicionalnega obsega, so opozorili, dokler izguba službe. Čas od 0 pomeni, da je skupni offline takoj dati brez opozorila. CIFS uporabniki lahko izgubi podatkov, če niso dana priložnost, da prekine aplikacij elegantno.

aggr čiščenje nadaljevati [aggrname | plexname | GROUPNAME]

Resumes pariteta ščetkanje na imenom agregat, plex, ali skupino. Če je izbira brez imena, spet vse RAID skupine trenutno v postopku paritete ribanje ki je bil prekinjen.

aggr čiščenje začetek [aggrname | plexname | GROUPNAME]

Začne pariteta ščetkanje na spletu imenovan agregat. Pariteta ščetkanje primerja podatke diskov na pariteto disk (s) v svoji skupini RAID, popravljanje pariteta disk z vsebino, kot je potrebno. Če je podana brez imena, je pariteta ščetkanje je začel na vseh spletnih agregate. Če je podana skupna imena, je ščetkanje je začel na vseh RAID skupine, ki jih vsebuje agregat. Če je podana plex ime, je ščetkanje je začel na vseh RAID skupine, ki jih vsebuje Plex.

aggr čiščenje statusa [aggrname | plexname | GROUPNAME] [-v]

Natisne status ribanje paritete na imenom agregat, plex, ali skupine, vse skupine, RAID trenutno dogajajo paritetni ribanje, če je podana nobena imena. Status vključuje popolno-odstotno, in drgnjenje je začasno stanje.

The-v zastavo prikaže datum in čas, ko je bilo zadnje celo drgnjenje zaključili skupaj s trenutnim statusom na imenom agregat, plex, ali skupine, vse skupine, RAID, če je podana nobena imena.

aggr čiščenje stop [aggrname | plexname | GROUPNAME]

Ustavi pariteta ščetkanje na imenom agregat, plex, ali skupine, če je dana brez imena, na vseh RAID skupine trenutno v postopku paritete ribanje.

aggr čiščenje odloži [aggrname | plexname | GROUPNAME]

Prekine pariteta ščetkanje na imenom agregat, plex, ali skupine, če je dana brez imena, na vseh RAID skupine trenutno dogajajo paritete ribanje.

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

Prikaže uporabo prostora v agregat. Za razliko od df, ta ukaz kaže prostor uporabi za vsako prilagodljivo prostornino v skupni Če je določeno aggrname, aggr show_space deluje le na ustreznih zbirnih, sicer poroča prostora pojavlja na vseh agregatov.

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.

       Skupni prostor To je znesek vseh prostora na disku, ki je skupna.  WAFL rezerve WAFL rezerv odstotek skupnih celotnega prostora na disku za agregatni ravni metapodatkov.  Prostor, ki se uporablja za ohranjanje količine v skupnem prihaja iz rezerve WAFL. 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. 

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.

Če je agregat, v katerem prebiva plexname vsebuje več kot eno prilagodljivo prostornino, je treba določiti, kako poimenovati količine v novi agregat, ki izhaja iz Splita. Izbira-r je mogoče večkrat uporabiti, da bi vsaki prilagodljiv volumen v dobljeni sestavljeni novo ime. Poleg tega je mogoče uporabiti izbiro-s se uporablja za določitev pripona, ki se doda na konec vseh prilagodljive obsega imena, ki niso zajeti v a-r.

Če je prvotna skupna omejeni v času po delih, se bo, ko dobljeni sestavljeni tudi omejiti. Če je omejena agregat gosti prilagodljiv obseg, niso preimenovali v času po delih. Prilagodljiva obseg se bo kasneje preimenovalo, ko je ime konflikt odkriti, obenem pa prinaša agregat online. Prilagodljiv obseg v agregat, ki je vložena na spletu first da njihova imena. To agregat je lahko prvotna skupna, ali skupni, ki izhaja iz Splita. Ko je drugi agregat bo prinesel na spletu kasneje, prilagodljiv obseg v tem agregat se preimenovali.

Če je plex od agregata vključena v tradicionalno obsega offline v času po delih, se bo, ko dobljeni sestavljeni nedosegljivi. Pri delitvi plex iz agregata, ki gosti prilagodljive količine, če je plex ni dosegljiv, vendar mora sestavljeni je na spletu, bo dobljeni sestavljeni prihajajo na spletu, in njegovih prilagodljivih obseg se bo preimenovalo. To ni dovoljeno razdeliti plex od offline agregat.

Split ogledalo se lahko spet združili preko-v možnost, da ogledalo aggr.

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.

       Neznana napaka vzrok neznan.  ni podatkov ONTAP ni disk zaradi usodne napake disk.  admin ni izdal uporabnika "disk ne" ukaz za ta disk.  označeni zdrobljen Disk ni bil pod Data ONTAP 6.1.X ali starejšo različico.  init ni Disk initialization zaporedje ni uspelo.  admin odstraniti uporabnika izdal ukaz "disk odstranite" za ta disk.  ne odziva Disk ne odziva na zahteve.  potegnil Disk je bil fizično potegnil, ali ne obstajajo podatki o poti, na katerih za dostop do diska.  obšli Disk je obiti z ESH. 

Undestroy delno nedotaknjena ali prej uničil agregat ali tradicionalnih prostornine. Ukaz izpiše seznam kandidata agregatov in tradicionalnih količin, ki ustrezajo ime, ki se lahko potencialno undestroyed.

The-n Možnost natisne seznam diskov, ki jih vsebuje v skupno ali s tradicionalnim prostornino, ki se lahko potencialno undestroyed. Ta možnost se lahko uporablja za prikaz rezultata izvedbe ukaza, ne da bi dejansko pripravi kakršne koli spremembe.

aggr preverjanje nadaljevati [aggrname]

Resumes RAID ogledalo preverjanja na imenom agregat, če je podana nobena skupna imena, za vse agregate trenutno v postopku preverjanja, RAID ogledalo, ki je bil prekinjen.

aggr preveri začetek [aggrname] [-f plexnumber]

Začne preverjanje RAID ogledalo na poimenovali skupni spletni zrcalno. Če je podana nobena ime, nato pa je RAID ogledalo preverjanja začelo na vse spletne agregate zrcalno. Preverjanje primerja podatke v obeh plexes od agregata zrcalno. V primeru neplačila, so vse bloke, ki se razlikujejo prijavljeni, vendar nobene spremembe so narejene. Če je podana-f zastavo, je določena plex pritrjen na tekmo drugi plex, ko so našli neusklajenosti. Ime mora biti določena z-f opcijo plexnumber.

aggr preveri stop [aggrname]

Zaustavi preverjanje RAID ogledalo na imenom agregat, če je podana nobena skupna imena, za vse agregate trenutno v postopku preverjanja RAID ogledalo.

aggr preverijo stanje [aggrname]

Natisne status ogledalo preverjanja RAID na imenom agregat, za vse agregate trenutno v postopku preverjanja RAID ogledalo, če je podana nobena skupna imena. Status vključuje popolno-odstotno, in preverjanje je začasno stanje.

aggr preverjanje prekine [aggrname]

Prekine RAID ogledalo preverjanja na imenom agregat, če je podana nobena skupna imena, za vse agregate trenutno v postopku preverjanja RAID ogledalo.

CLUSTER PREUDARKI

Vendar pa imajo edinstveno agregat imen v skupini olajša prehod agregatov med filers v skupini.

PRIMERI

Ustvari agregat imenovan aggr1 z 20 diskov. RAID skupine v tem agregat lahko vsebuje do 10 diskov, tako da je ta nova agregata ima dve skupini RAID. The filer dodaja sedanje proste diskov na nov agregat, začenši z najmanjšimi disk.

aggr ustvariti aggr1 20 @ 9

Ustvari agregat imenovan aggr1 z 20 9-GB diske. Ker ni določena RAID velikost skupine, se uporabi privzeta velikost (8 diskov). Novo ustvarjene agregat vsebuje dve skupini RAID z 8 diski in tretja skupina s štirimi diski.

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

Ustvari agregat imenovan aggr1 s določitev treh diskov.

aggr ustvariti aggr1 10
aggr možnosti 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

Kazalo

• NAME
• POVZETEK
• OPIS
• UPORABA
• CLUSTER CONSIDERATIONS
• EXAMPLES
• GLEJ TUDI

Manual Pages aggr , man , manual , NetApp , ONTAP

Kazalo

NAME

SYNOPSIS

cf nfo [ enable | disable ] disk_shelf

cf nfo status

DESCRIPTION

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

MOŽNOSTI

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.

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.

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.

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.

GLEJ TUDI

Kazalo

• NAME
• POVZETEK
• OPIS
• MOŽNOSTI
• GLEJ TUDI

Manual Pages cf , man , manual , NetApp , ONTAP

Kazalo

NAME

SYNOPSIS

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

OPIS

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.

MOŽNOSTI

-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

EXAMPLES

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 

GLEJ TUDI

Prenesi

---

Kazalo

• NAME
• POVZETEK
• OPIS
• MOŽNOSTI
• CLUSTER CONSIDERATIONS
• EXAMPLES
• GLEJ TUDI

Read more... (1013 words, estimated 4:03 mins reading time)

Manual Pages bootfs , man , manual , NetApp , ONTAP

Kazalo

NAME

SYNOPSIS

DESCRIPTION

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.

GLEJ TUDI

Kazalo

• NAME
• POVZETEK
• OPIS
• FILES
• GLEJ TUDI

Copyright © 1994-2008 NetApp, Inc Pravno-informacijski

Manual Pages boot , man , manual , NetApp , ONTAP

Kazalo

NAME

SYNOPSIS

bmc reboot

bmc setup

bmc status

bmc test autosupport

OPIS

MOŽNOSTI

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

EXAMPLES

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 

GLEJ TUDI

NOTES

Kazalo

• NAME
• POVZETEK
• OPIS
• MOŽNOSTI
• CLUSTER CONSIDERATIONS
• EXAMPLES
• GLEJ TUDI
• NOTES

Copyright © 1994-2008 NetApp, Inc Pravno-informacijski

Manual Pages bmc , man , manual , NetApp , ONTAP

Kazalo

NAME

SYNOPSIS

OPIS

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.

Možnosti

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.

Snapshot

When the snapshot is created or located.

Base_dump

When a valid base dump entry is located.

Start_logging Logging begins.

Stop_logging

Logging ends.

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.

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

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

GLEJ TUDI

Kazalo

• NAME
• POVZETEK
• OPIS
• FILES
• GLEJ TUDI

Manual Pages backuplog , man , manual , NetApp , ONTAP

Kazalo

NAME

SYNOPSIS

backup terminate <ID>

OPIS

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.

UPORABA

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.

Level

The level of the backup.

Path

Points to the tree that is being backed up.

 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/ 

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.

GLEJ TUDI

Kazalo

• NAME
• POVZETEK
• OPIS
• UPORABA
• GLEJ TUDI

Manual Pages backup , man , manual , NetApp , ONTAP

Kazalo

NAME

SYNOPSIS

OPIS

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.

MOŽNOSTI

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

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

BATTERY_LOW!!!
LOG_ALERT

BMC_EVENT: BUS ERROR
LOG_ERR

BMC_EVENT: POST ERROR
LOG_ERR

CLUSTER DOWNREV BOOT FIRMWARE

LOG_CRIT

CLUSTER GIVEBACK COMPLETE

LOG_INFO

CLUSTER TAKEOVER COMPLETE AUTOMATIC

LOG_ALERT

CLUSTER TAKEOVER COMPLETE MANUAL

LOG_INFO

CLUSTER TAKEOVER FAILED

LOG_INFO

CPU FAN WARNING - [fan]
LOG_WARNING

DEVICE_QUALIFICATION_FAILED

LOG_CRIT

DISK CONFIGURATION ERROR

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

FC-AL LINK_FAILURE!!!
LOG_ERR

FC-AL RECOVERABLE ERRORS

LOG_WARNING

OVER_TEMPERATURE_WARNING!!!
LOG_EMERG

PARTNER DOWN, TAKEOVER IMPOSSIBLE
LOG_ALERT

POSSIBLE BAD RAM

LOG_ERR

POSSIBLE UNLINKED INODE

LOG_ERR

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

SNMP USER DEFINED TRAP

LOG_INFO

SYSTEM_CONFIGURATION_CRITICAL_ERROR

LOG_CRIT

SYSTEM_CONFIGURATION_ERROR

LOG_ERR

UNDER_TEMPERATURE_WARNING!!!
LOG_EMERG

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

WAFL_check!!!
LOG_ALERT

WEEKLY_LOG

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 PREUDARKI

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.

GLEJ TUDI

Kazalo

• NAME
• POVZETEK
• OPIS
• MOŽNOSTI
• CONTENTS
• TYPES
• CLUSTER CONSIDERATIONS
• GLEJ TUDI

Manual Pages AutoSupport , man , manual , NetApp , ONTAP

Kazalo

NAME

SYNOPSIS

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

OPIS

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

in

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

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

FILES

<logdir>/auditlog

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

GLEJ TUDI

Kazalo

• NAME
• POVZETEK
• OPIS
• FILES
• GLEJ TUDI

Manual Pages auditlog , man , manual , NetApp , ONTAP