Arkiv

Indlæg tagget med 'mand'

NetApp Man Sider

NetApp har venligst givet mig lov til at genudgive deres mand sider her. De har stadig brug for lidt rydde op, men den store mængde betyder, at det vil tage mig et stykke tid at få dem alle sorteres og krydshenvises ordentligt, undskyld eventuelle visuelle problemer for øjeblikket. Jeg skrev en hurtig parsing værktøj til at få al den info om her, så der kan være et par problemer som følge af, at der stadig.

Jeg har altid godt kunne lide den måde, at PHP har deres funktion sider giver brugerne mulighed for at kommentere direkte på dem. Dette giver folk mulighed for at give feedback på funktioner og værktøjer, og også følge op med nogle ekstra anvendelser eller syntaks for kommandoer, der ikke nødvendigvis er klart offentliggjort. Forhåbentlig dette kan føres tilbage til NetApp til at forbedre deres dokumentation.

Jeg vil absolut gerne opfordre folk til at kommentere på de man-sider med noget som kan være nyttige, og forhåbentlig bygge det ind i en nyttig lille henvisning sektion. Mange tak igen for NetApp folk for at hjælpe mig med dette.

VN: F [1.9.11_1134]
Bedømmer dette indlæg:
Rating: 8.8 / 10 (19 stemmer)

Tags: , , , , Kategorier: Generelle og Manualsider Tags: og og , ,

aggr

Indholdsfortegnelse

NAVN

aggr - kommandoer til styring af aggregater, viser samlet status, og kopiering aggregater

SYNOPSIS

aggr kommando argument ...

BESKRIVELSE

Den aggr kommando familien styrer aggregater. De aggr kommandoer kan skabe nye aggregater, ødelægge eksisterende, undestroy tidligere ødelagt samlet, styre komplekser i en spejlet aggregat, ændre den samlede status, gælder muligheder for en samlet, kopi én samlet til en anden, og vise deres status. Samlede kommandoer ofte påvirke volumen (r) indeholdt i aggregater.

Den aggr Kommandoen familien er nyt i Data ONTAP 7,0. Den vol. kommando Familien forudsat kontrol over den traditionelle vol_ u MES at smeltet en enkelt bruger-synligt filsystem og en enkelt RAID-niveau opbevaringscontainer (samlet) i en uadskillelig enhed, og stadig gør. For at give mulighed for en mere fleksibel brug af lagerfaciliteter, aggregater nu også støtte evnen til at indeholde flere uafhængige bruger-niveau filsystemer navngivne fleksible mængder.

Dataene ONTAP 7,0 støtter fuldt ud både traditionelle og fleksible mængder. Den aggr Kommandoen Familien er den foretrukne metode til styring af en ansøger, har aggregater, herunder dem, der er indlejret i traditionelle mængder.

Bemærk, at de fleste af de aggr kommandoer gælde for både den type aggregat, der indeholder fleksible mængde og den type, der er tæt bundet til dannelse af en traditionel volumen. Således er udtrykket aggregatet anvendes her til at henvise til både opbevaring klasser. I disse tilfælde giver det en forkortelse for de længere og tungere udtrykket "tilslagsmaterialer og traditionelle mængder".

Aggregater kan enten være spejles eller unmirrored. En Plex er en fysisk kopi af WAFL opbevaring i aggregatet. En spejlet samlet består af to komplekser; unmirrored aggregater indeholde en enkelt Plex. For at skabe en spejlet samlet, skal du have en filer konfiguration, der understøtter RAID-niveau spejling. Når spejling er aktiveret på filer, bliver de ekstra diskene opdelt i to disk pools. Når en samlet er oprettet, skal alle diske i et enkelt kompleks kommer fra den samme disk pulje, og de to komplekser i en spejlet samlet skal bestå af diske fra forskellige puljer, da dette maksimerer fejl isolation. Denne politik kan tilsidesættes med-f mulighed for at aggr skaber, aggr add og aggr spejl, men det anbefales ikke.

Et aggregat navn kan indeholde bogstaver, tal og understregningstegn (_), men det første tegn skal være et bogstav eller et understregningstegn. En kombineret alt op til 200 tilslagsmaterialer (herunder indlejret i traditionelle mængder) kan oprettes på hver filer.

En kompleks kan være online eller offline. Hvis det er offline, er det ikke tilgængeligt for læse eller skrive adgang. Komplekser kan være i en kombination af følgende tilstande:

normale Alle RAID grupper i kompleks er funktionelle.

mislykkedes Mindst en af de RAID grupper i kompleks har svigtet.

tømme kompleks er en del af et aggregat, der bliver skabt, og én eller flere af skiverne målrettet til aggregatet skal nulstilles før tilsætning til den komplekse.

active kompleks er klar til brug.

inaktiv
Den Plex er ikke tilgængelig til brug.

resyncing
Den komplekse indhold er nu forældede og er i færd med at blive gensynkroniseret med indholdet af den anden kompleks af aggregatet (gælder spejlede aggregater).

tilføje diske
Diske bliver tilføjet til plex RAID gruppe (r).

out-of-dato
Denne tilstand kun forekommer i spejlede aggregater, hvor en af ​​de komplekser ikke har. Den ikke-mislykkede Plex vil være i denne tilstand, hvis det skulle synkronisering igen på det tidspunkt, den anden Plex mislykkedes.

En kompleks er opkaldt bruge navnet af den samlede, en skråstreg delimiter, og navnet på Plex. Systemet vælger automatisk komplekse navne på oprettelsestidspunktet. For eksempel vil den første plex skabt i samlet aggr0 være aggr0/plex0.

Et aggregat kan være online, begrænset eller offline. Når en samlet er offline, ikke læse eller skrive adgang er tilladt. Når en samlet, er begrænset, er visse operationer tilladt (som samlet kopi, paritet omregning eller RAID rekonstruktion), men adgang til data er ikke tilladt. Aggregater, som ikke er en del af en traditionel volumen kun begrænses eller offlined hvis de ikke indeholder fleksible mængder.

Aggregater kan være i en kombination af følgende tilstande:

aggr Den samlede er en moderne aggregat; det er i stand til at indeholde nul eller flere fleksible mængder.

kopiering
Den samlede er i øjeblikket målet summen af en aktiv aggr kopi drift.

nedbrudt
Den samlede indeholder mindst en forringet RAID gruppe, som ikke bliver rekonstrueret.

udenlandske
De diske, at den samlede indeholder blev flyttet til den nuværende filer fra en anden filer.

voksende
Diske er i færd med at blive tilsat til aggregatet.

initialisering
Aggregatet er i færd med at blive initialiseret.

ugyldig
Den samlede indeholder ingen volumener og ingen kan tilsættes. Typisk sker kun efter en afbrudt samlet kopi drift.

strygning
En WAFL konsistens kontrollen bliver udført på dette aggregat.

spejl nedbrudt
Aggregatet er en spejlvendt aggregat, og en af ​​dets komplekser er offline eller resyncing.

spejlet
Den samlede er modsat og alle dens RAID grupper er funktionelt.

behov for kontrol
En WAFL konsistenstjek skal udføres på aggregat.

delvis
Mindst én skive blev fundet for aggregatet, men to eller flere skiver mangler.

RAID0 Den samlede består af RAID-0 (ingen paritet) RAID-grupper (V-serien og NetCache kun).

raid4 Den samlede består af RAID-4 RAID-grupper.

raid_dp
Den samlede består af RAID-DP (Double Parity) RAID grupper.

rekonstruere
Mindst en RAID gruppe i den samlede bliver rekonstrueret.

omdirigering
Samlet omfordeling eller fil omfordeling med-p option er startet på den samlede. Læs ydeevne til volumener i den samlede kan blive forringet.

resyncing
En af komplekser af spejlet aggregat bliver gensynkroniseres.

snapmirrored
Aggregatet er en snapmirrored kopi af et andet aggregat. Denne tilstand kan kun opstå, hvis den samlede er en del af en traditionel volumen.

trad Den samlede er fusioneret med en enkelt enhed. Dette er også nævnt som en traditionel volumen og er netop svarer til de mængder, der eksisterede før data ONTAP 7,0. Fleksible mængder ikke kan skabes på indersiden af ​​dette aggregat.

verificere
En RAID spejl Kontrollen er i øjeblikket kører på den samlede.

WAFL inkonsekvent
Den samlede er markeret beskadiget. Kontakt Kundeservice, hvis du ser et aggregat i denne tilstand.

BRUG

Følgende kommandoer er tilgængelige i aggr suite:

  tilføje spejl begrænse undestroy kopiere offline krat kontrollere skabe online show_space ødelægge mulighederne opdelt media_scrub rename status 

aggr add aggrname
[-F]
[N]
[-G {raidgroup | ny | alle}]
{Ndisks [@ størrelse]
|
-D Disk1 [disk2 ... ] [-D diskn [diskn en ... ]]}

Tilføjer diske til det samlede navn aggrname. Angiv diske på samme måde som for aggr Opret kommandoen. Hvis den samlede er spejlvendt, så-d argumentet skal anvendes to gange (hvis overhovedet).

Hvis-g option ikke er brugt, er diske tilføjes til den nyligt oprettede RAID gruppe util den er fuld, og derefter en eller flere nye RAID-grupper er oprettet, og de ​​resterende diske føjes til nye grupper. Alle andre eksisterende RAID-grupper, der ikke er fuld forbliver delvist fyldt.

Den-g valgmulighed kan specifikation af en RAID gruppe (for eksempel rg0), som de angivne skiverne skal tilføjes, eller en fremgangsmåde, hvorved skiverne tilsættes til nye eller eksisterende RAID grupper.

Hvis-g option bruges til at angive en RAID-gruppe, skal denne RAID gruppe allerede eksisterer. Skiverne tilsættes til RAID gruppe util den er fuld. Eventuelle resterende skiver ignoreres.

Hvis-g option er efterfulgt af nye, Data ONTAP skaber en eller flere nye RAID-grupper og tilføjer diske til dem, selvom de diske ville passe ind i en eksisterende RAID-gruppe. Alle eksisterende RAID-grupper, der ikke er fuld forbliver delvist fyldt. Navnet på den nye RAID-grupperne er valgt automatisk. Det er ikke muligt at angive navne for de nye RAID-grupper.

Hvis-g option følges af alle, Data ONTAP tilføjer de angivne diske eksisterende RAID-grupper først. Efter at alle eksisterende RAID-grupper er fuld, det skaber en eller flere nye RAID-grupper og tilføjer de specificerede diske til de nye grupper.

The-n option kan bruges til at vise den kommando, at systemet vil udføre, uden faktisk at foretage nogen ændringer. Dette er nyttigt for at vise den automatisk valgte diske, f.eks.

Som standard, fylder filer op en RAID gruppe med diske, før du starter en anden RAID-gruppe. Antag et samlet har i øjeblikket en RAID gruppe på 12 diske og RAID gruppens størrelse er 14. Hvis du tilføjer 5 diske til dette samlet, vil det have en RAID-gruppe med 14 diske og en anden RAID gruppe med 3 diske. Den filer ikke fordeles jævnt skiverne mellem RAID grupper.

Du kan ikke tilføje diske til en spejlet samlet, hvis en af ​​de komplekser er offline.

De diske i en kompleks er ikke tilladt at spænde disk puljer. Denne adfærd kan tilsidesættes med-f flag, når de bruges sammen med-d argumentet til listen diske for at tilføje. -F flag, i kombination med-d, kan også anvendes til at tvinge tilsætning diske, der har en rotationshastighed, der ikke svarer, at de fleste af de eksisterende diske i aggregatet.

aggr kopi abortere [-h] operation_number | alle

Afslutter samlede kopifunktioner. Den opera_ t ion_number parameter angiver, hvilken operation for at afslutte. Hvis du angiver alle, alle samlede aktive kopifunktioner afsluttet.

aggr kopi starten
[-S |-s snapshot] [-C]
kilde destination

Kopierer alle data, herunder snapshots og fleksible mængder, fra en samlet til en anden. Hvis-S flaget anvendes, kommandoen kopieres alle snapshots i kilden aggregat til destinationen aggregatet. Hvis du vil angive en bestemt snapshot at kopiere, skal du bruge parameteren-s efterfulgt af navnet på snapshot. Hvis du bruger hverken-S eller-s flag i kommandoen, filer skaber et øjebliksbillede på det tidspunkt, hvor aggr kopi startkommando udføres, og kun kopier, der snapshot til destinationen samlet.

Den-C flaget er påkrævet, hvis kilden samlede har haft fri-plads defragmentering udført på den, eller hvis destinationen samlede vil være fri-rum defragmenteret. Free-plads defragmenteringen kan udføres på en samlet ved hjælp af realloker kommandoen.

Samlede kopier kan kun udføres mellem aggregater, der er vært fleksible mængder. Aggregater, der er indlejret i de traditionelle mængder, kan ikke deltage.

Kilde og destination aggregater kan være på samme filer eller forskellige filers. Hvis kilden eller destination samlet er på en filer anden end den, som du indtaster aggr kopi startkommando, skal du angive det samlede navn i filer_name: aggre_ g. ate_name format.

De menige er involveret i en samlet kopi, skal opfylde følgende krav til aggr kopi startkommando at blive afsluttet med succes:

Kilden samlede skal være online og destination samlede skal begrænses.

Hvis kopien er mellem to menige, skal hver filer defineres som en betroet vært for anden filer. Det er, må filer navn være i / etc / hosts.equiv fil på den anden filer.

Hvis kopien er den samme ansøger, skal localhost indgå i filer / etc / hosts.equiv fil. Desuden skal loopback adressen være i filer / etc / hosts. Ellers kan filer ikke sende pakker til sig selv gennem loopback adresse, når de forsøger at kopiere data.

Den anvendelige diskplads for destinationen aggregat skal være større end eller lig med den anvendelige diskplads af kilden aggregat. Brug df-A stinavn kommando for at se mængden af brugbar diskplads til en bestemt aggregat.

Hver aggr kopi startkommando genererer to samlede kopifunktioner: en til at læse data fra kilden samlet, og en til at skrive data til bestemmelsesstedet samlede. Hver filer understøtter op til fire samtidige samlede kopifunktioner.

aggr kopi status [operation_number]

Viser forløbet af en eller alle aggr kopifunktioner. De operationer er nummereret fra 0 til 3.

Genstart checkpoint information for alle overførsler, vises også.

aggr kopi gasspjæld [operation_number] værdi

Styrer ydeevne aggr kopieringen. Værdien varierer fra 10 (fuld hastighed) til 1 (en tiendedel af fuld hastighed). Standardværdien opretholdes i filer har aggr.copy.throttle indstilling og er sat 10 (fuld hastighed) på fabrikken. Du kan anvende resultaterne værdi til en operation, er angivet af operation_number parameter. Hvis du ikke angiver en operation nummer i aggr kopi gashåndtaget kommando, kommandoen gælder for alle aggr kopifunktioner.

Brug denne kommando til at begrænse hastigheden af aggr kopi operation, hvis du har mistanke om, at aggr kopieringen er årsag til problemer med ydeevnen på din filer. Især er gashåndtaget designet til at hjælpe begrænse CPU-forbruget af aggr kopieringen. Det kan ikke bruges til at finjustere netværk båndbredde forbrugsmønstre.

Den aggr kopi gashåndtaget kommandoen kun giver dig mulighed for at indstille hastigheden på en aggr kopi operation, der er i gang. For at opsætte standardsproget aggr kopihastighed at blive brugt af fremtidige kopifunktioner, skal du bruge kommandoen Indstillinger for at indstille aggr.copy.throttle mulighed.

aggr skaber aggrname
[-F]
[M]
[N]
[-T raidtype]
[-R raidsize]
[T skive-typen]
[-R rpm]
[-L [overholdelse | virksomhed]]
[-V]
[-L sprog-kode]
{Ndisks [@ størrelse]

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

Opretter en ny samlet navnet aggrname. Den samlede Navnet kan indeholde bogstaver, tal og understregningstegn (_), men det første tegn skal være et bogstav eller et understregningstegn. Op til 200 aggregater kan oprettes på hver filer. Dette tal omfatter de aggregater, der er indlejret i traditionelle mængder.

En integreret samlet kan oprettes som en del af en traditionel volumen ved hjælp af-v option. Det kan ikke indeholde fleksible mængder.

En regelmæssig samlet, skabt uden-v option, kan kun indeholde fleksible mængder. Det kan ikke inkorporeres i en traditionel volumen, og det indeholder ingen mængder umiddelbart efter skabelsen. Nye fleksible mængder kan oprettes ved hjælp af vol. Opret kommandoen.

The-t raidtype argument angiver, hvilken type RAID gruppe (r), der skal bruges til at skabe den samlede. De mulige raid gruppe typer er raid4 for RAID-4, raid_dp for RAID-DP (Double Paritet), og RAID0 for simple striber uden paritet beskyttelse. Standard raidtype for aggregater og traditionelle mængder på filers er raid_dp. Indstilling af raidtype er ikke tilladt på V-serien systemer misligholdelse af RAID0 altid bruges.

The-r raidsize argument angiver det maksimale antal diske i hvert RAID gruppe i den samlede. De maksimale værdier og standardværdier for raidsize er platform-afhængig, er baseret på ydeevne og pålidelighed overvejelser. Se aggr muligheder raidsize for flere detaljer.

The-T disk-type argument angiver den type diske at bruge, når du opretter en ny samlet. Det er kun nødvendigt på systemer forbundet med skiver af forskellige typer. Mulige disk typer er: ATA, FCAL, LUN, SAS, SATA og SCSI. Blanding skiver af forskellige typer i en samlet, ikke tilladt. T kan ikke anvendes sammen med-d.

Disk type identifies disk technology and connectivity type. ATA identifies ATA disks with either IDE or serial ATA interface in shelves connected in FCAL (Fibre Channel Arbitrated Loop). FCAL identifies FC disks in shelves connected in FC-AL. LUN identifies virtual disks exported from external storage arrays. The underlying disk technology and RAID type depends on implementation of such external storage arrays. SAS identifies Serial Attached SCSI disks in matching shelves. SATA identifies serial ATA disks in SAS shelves. SCSI stands for Small Computer System Interface, and it is included for backward compatibility with earlier disk technologies.

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

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

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

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

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

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

For at oprette en låseringfikseret aggregat, angive-L flag med aggr skabe kommandoen. Dette flag understøttes kun, hvis enten låseringfikseret overensstemmelsesdokument eller låseringfikseret Enterprise licens. Typen af ​​låseringfikseret skabte samlet, enten Compliance eller Enterprise, bestemmes af den installerede låseringfikseret licens. Hvis både låseringfikseret Compliance og låseringfikseret Enterprise er givet i licens, brug-L overholdelse eller-L virksomhed at angive den ønskede samlede type.

-L language_code argument kan kun bruges, når du opretter en traditionel volumen ved hjælp af option-v. Det filer skaber traditionelle volumen med sproget er specificeret af sprogkode. Som standard er det sprog, der bruges af filer rod volumen. Se vol man side for en liste over sprogkoder.

aggr ødelægge {aggrname | plexname} [-f]

Ødelægger den samlede navn aggrname eller komplekst navngivne plexname. Bemærk, at hvis den angivne aggregat er bundet til en traditionel volumen, derefter traditionelle volumen selv ødelagt.

Hvis en samlet er angivet, er alle komplekser i aggregatet ødelagt. Den navngivne samlede må heller ikke indeholde fleksible mængder, uanset deres mount tilstand (online, begrænset eller offline). Hvis en Plex er angivet, er Plex ødelagt, efterlader en unmirrored samlet eller traditionel volumen indeholdende resterende Plex. Før ødelægge den samlede, traditionelle volumen eller kompleks, bliver brugeren bedt om at bekræfte transaktionen. The-f flaget kan bruges til at ødelægge en samlet, traditionel volumen eller plex uden at spørge brugeren.

De diske oprindeligt i den ødelagte genstand bliver ekstra diske. Kun offline aggregater, kan traditionelle mængder og komplekser blive ødelagt.

aggr media_scrub status [aggrname | plexname | gruppenavn]
[-V]

Udskriver medierne skrubning status opkaldt samlede, Plex, eller gruppe. Hvis intet navn er givet, så status er trykt for alle RAID-grupper kører i øjeblikket et medie krat. Status indeholder en procent-komplet, og om det er suspenderet.

-V flaget viser dato og tidspunkt, hvor den sidste hele medierne scrub afsluttet, dato og tidspunkt, hvor den nuværende forekomst af medier skrubbe startede, og den aktuelle status for den navngivne samlede, Plex, eller gruppe. Hvis intet navn er givet, er dette mere detaljeret status udskrives for alle RAID-grupper med aktive medier krat.

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

Vender en unmirrored aggregere til en spejlet aggregat ved tilsætning af en kompleks til det. Den plex enten nydannede fra diske valgt fra en ekstra pool, eller, hvis V-løsning er angivet, er taget fra en anden eksisterende unmirrored aggregat. Samlet aggrname skal i øjeblikket være unmirrored. Brug aggr skaber til at lave en ny, spejles samlet fra bunden.

Diskene kan angives eksplicit med-d på samme måde som med aggr oprette og aggr tilføje kommandoer. Antallet af angivne skiver skal svare til antallet stede på eksisterende aggregat. De angivne diske er ikke tilladt at spænde disk puljer. Denne adfærd kan tilsidesættes med-f option. -F mulighed, i kombination med-d, kan også anvendes til at tvinge hjælp diske, der har en rotationshastighed, der ikke svarer, at de fleste af de eksisterende diske i aggregatet.

Hvis diske ikke er angivet eksplicit, og derefter diske er automatisk valgt til at matche dem i den samlede eksisterende Plex.

-V mulighed kan anvendes til at sammenføje victim_aggrname tilbage i aggrname til dannelse af en spejlet aggregat. Resultatet er en spejlvendt aggregat navngivet aggrname som ellers identisk aggrname før operationen. Victim_aggrname effektivt ødelægges. Victim_aggrname skal have været afspejlet med aggrname, adskilles derpå via aggr split-kommandoen. Victim_aggrname være offline. Kombineret med-v option, kan den-f option bruges til at slutte sig til aggrname og vic_ t im_aggrname uden at spørge brugeren.

The-n option kan bruges til at vise den kommando, at systemet vil udføre uden egentlig at foretage nogen ændringer. Dette er nyttigt for at vise den automatisk valgte diske, f.eks.

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

Tager den samlede navngivne aggrname (eller plex navngivne plexname) offline. Kommandoen træder i kraft før han vendte tilbage. Hvis den samlede allerede er i begrænset tilstand, så er det allerede tilgængelig for adgang til data, og meget af den følgende beskrivelse gælder ikke.

Hvis den samlede indeholder nogen fleksible mængder, så operationen er afbrudt, medmindre filer er i vedligeholdelsestilstand.

Undtagen i vedligeholdelse tilstand, kan den samlede indeholder den aktuelle rod volumen ikke tages offline. Et aggregat, der indeholder en mængde, der er markeret til at blive root (ved hjælp af vol muligheder vol_ N AVN root) kan heller ikke tages offline.

Hvis den samlede er indlejret i en traditionel volumen, der har CIFS aktier, bør brugerne advares, før du tager den samlede (og dermed hele traditionel volumen) offline. Anvende-t kontakten for denne. Den cifsdelaytime argument angiver det antal minutter til at forsinke, før du tager den integrerede samlede offline, i hvilket tidsrum CIFS brugere af traditionelle volumen er advaret om den forestående tab af service. En tid med 0 betyder, at den samlede offline umiddelbart uden givne advarsler. CIFS brugere kan miste data, hvis de ikke får en chance for at opsige applikationer elegant.

Hvis en plexname er angivet, skal kompleks være en del af en spejlende aggregat og begge komplekser skal være online. Forud for offlining en Plex, vil systemet skylle alle internt-bufferet data, der er forbundet med Plex og skabe et øjebliksbillede, som er skrevet ud til begge komplekser. Det øjebliksbillede giver mulighed for effektiv gensynkronisering, når Plex er efterfølgende bragt tilbage online.

En række af operationer bliver udført på den samlede traditionelle lydstyrke kan forhindre aggr offline fra at lykkes, for forskellige længder af tid. Hvis sådanne operationer er fundet, vil der være en et sekund vente for sådanne transaktioner til slut. Hvis de ikke gør, kommandoen er afbrudt.

En kontrol er også lavet til filer i den samlede s tilhørende traditionel mængde, der åbnedes af interne ONTAP processer. Kommandoen afbrydes hvis der findes.

aggr online {aggrname | plexname}
[-F]

Bringer den samlede navngivne aggrname (eller plex navngivne plexname) online. Denne kommando træder i kraft straks. Hvis den angivne samlede er indlejret i en traditionel volumen, er lydstyrken også også bragt online.

Hvis en aggrname er angivet, skal det være offline i øjeblikket, begrænset eller udenlandsk. Hvis den samlede er fremmed, vil det blive indfødte, inden den bringes online. En "fremmed" aggregat er et aggregat, der består af diske flyttet fra en anden ansøger, og som aldrig er blevet bragt online på den aktuelle filer. Aggregater, der ikke er fremmede betragtes som "native".

Hvis den samlede er inkonsekvent, men har ikke mistet data, vil brugeren blive advaret og bedt om, før at bringe den samlede online. The-f flaget kan bruges til at tilsidesætte denne opførsel. Det er tilrådeligt at køre WAFL_check (eller lave en snapmirror initialisere i tilfælde af en samlet integreret i en traditionel volumen) før at bringe en inkonsekvent samlet online. Bringe en inkonsekvent samlet online øger risikoen for yderligere filsystemet korruption. Hvis den samlede er inkonsekvent og har oplevet mulige tab af data, kan det ikke blive bragt online, medmindre WAFL_check (eller snapmirror initialisere i den indlejrede tilfælde) er blevet kørt på den samlede.

Hvis en plexname er angivet, skal kompleks være en del af en online spejlede samlet. Systemet vil indlede gensynkronisering af kompleks som en del af online-behandling.

aggr muligheder aggrname [optname optval]

Viser de muligheder, der er blevet sat til samlet aggrname, eller sætter muligheden opkaldt optname af den samlede navngivne aggrname til værdien optval. Kommandoen forbliver i kraft efter filer genstartes, så der er ingen grund til at tilføje aggr muligheder kommandoer til / etc / rc-fil. Nogle muligheder har værdier, der er tal. Nogle muligheder har værdier, der kan være (som også kan udtrykkes som ja, sandt eller 1) eller fra (som også kan udtrykkes som nej, falsk eller 0). En blanding af store og små bogstaver kan bruges, når du indtaster værdien af ​​en option. Den aggr status kommando viser de indstillinger, der er fastsat pr aggregat.

I det følgende beskrives de muligheder og deres mulige værdier:

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.

Juridiske værdier for denne indstilling afhænger raidtype. For eksempel tillader raid_dp større RAID grupper end raid4. Grænser og standardværdier er også forskellige for forskellige typer filer apparater og forskellige typer diske. Følgende tabeller sætter grænser og standardværdier for raidsize.

  -------------- Raid4 raidsize min standard max -------------- R100 2 8 8 R150 2 6 6 FAS250 2 7 14 andre (FCAL diske) 2 8 14 andre (ATA-diske), 2 7 7 ---------------------------- raid_dp raidsize min standard max ------ -------- R100 3 12 12 R150 3 12 16 andre (FCAL diske) 3 16 28 andre (ATA diske) 3 14 16 ---------- ---- 

Disse værdier kan ændres i fremtidige versioner af data ONTAP.

raidtype raid4 | raid_dp | RAID0

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

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

resyncsnaptime number

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

rod

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

Denne læse eneste mulighed indikerer, at den samlede er en låseringfikseret Enterprise aggregat. Aggregater kan kun betegnes låseringfikseret Enterprise aggregater på oprettelsestidspunkt.

snapmirrored off

Hvis SnapMirror er aktiveret for en traditionel volumen (SnapMirror understøttes ikke for aggregater, der indeholder fleksible mængder), at filer automatisk denne indstilling til. Sæt denne indstilling til Off, hvis SnapMirror er ikke længere skal anvendes til at opdatere den traditionelle volumen spejlet. Efter at sætte denne indstilling til Off, bliver spejlet en almindelig skrivbar traditionel volumen. Denne mulighed kan kun indstilles til at slukke, kun filer kan ændre værdien af denne mulighed fra OFF til ON.

snapshot_autodelete on | off

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

aggr rename aggrname newname

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

aggr restrict aggrname
[ -t cifsdelaytime ]

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

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

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

aggr scrub resume [ aggrname | plexname | groupname ]

Genoptager paritet skrubning på den navngivne samlede, Plex, eller gruppe. Hvis intet navn er givet, genoptager alle RAID-grupper i øjeblikket gennemgår en paritet skrubbe, der er blevet suspenderet.

aggr scrub start [aggrname | plexname | gruppenavn]

Begynder paritet skrubning af den nævnte online aggregat. Paritet skrubbe sammenligner data diske til paritet disk (s) i deres RAID-gruppen, korrigere paritet diskens indhold, som er nødvendigt. Hvis intet navn er givet, er paritet skrubbe startet på alle online-aggregater. Hvis en samlet navn er angivet, er skrubbe startet på alle RAID-grupper, der er indeholdt i den samlede. Hvis et komplekst navn er angivet, er skrubbe startet på alle RAID-grupper, der er indeholdt i Plex.

aggr scrub status [aggrname | plexname | gruppenavn] [-v]

Udskriver status for paritet skrubbe på den navngivne samlede, Plex, eller gruppe, og alle RAID-grupper øjeblikket paritet skrubbe, hvis intet navn er givet. Status indeholder en procent-komplet, og krat har suspenderet status.

-V flaget viser dato og tidspunkt, hvor den sidste fulde scrub udfyldt sammen med den aktuelle status på den navngivne samlede, Plex, eller gruppe, og alle RAID-grupper, hvis intet navn er givet.

aggr scrub stop [aggrname | plexname | gruppenavn]

Stopper paritet skrubning på den navngivne samlede, Plex, eller gruppe, hvis der intet navn er givet, på alle RAID grupper undergår i øjeblikket en paritet skrubbe.

aggr scrub suspendere [aggrname | plexname | gruppenavn]

Afbryder paritet skrubning på den navngivne samlede, Plex, eller gruppe, hvis der intet navn er givet, på alle RAID-grupper i øjeblikket gennemgår paritet skrubning.

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

Viser pladsudnyttelsen i et aggregat. I modsætning til df, viser denne kommando pladsudnyttelsen for hver fleksibel volumen inden for en samlet Hvis aggrname er angivet, aggr show_space kun kører på de tilsvarende aggregerede, ellers rapporterer pladsudnyttelsen på alle aggregater.

Alle størrelser er rapporteret i 1024-byte blokke, medmindre andet ved en af-H,-k, m,-g-eller-t muligheder. The-k,-m,-g, og-t flagene skala hver størrelse-relateret område af produktionen skal udtrykkes i kilobyte, megabyte, gigabyte, eller terabytes hhv.

Følgende terminologi anvendes af kommandoen i rapporteringen rummet.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

       ukendt Manglende grund ukendt. 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.

EKSEMPLER

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

Den første kommando opretter en samlet opkaldt aggr1 med 10 diske, der hører til en RAID-gruppe. Den anden kommando angiver, at hvis de diske efterfølgende føjes til dette samlet, vil de ikke medføre nogen aktuelle RAID gruppe at have mere end fem diske. Hver eksisterende RAID-gruppe vil fortsætte med at have 10 diske, og ikke flere diske vil blive føjet til, at RAID-gruppe. Når nye RAID-grupper er oprettet, vil de have en maksimal størrelse på fem diske.

aggr show_space-h AG1

Viser pladsforbrug af aggregatet `AG1 'og skalerer enhed af rum afhængigt.

  Samlet 'AG1 "Total plads WAFL reserve Snap reserve brugbar plads BSR NVLOG 66GB 6797MB 611MB 59GB 65KB afsat plads til mængder i den samlede mængde Tildelt garanterer, Vol1 14DK 11DK volumen vol2 8861MB 8871MB fil vol3 6161MB 6169MB ingen vol4 26GB 25GB volumen vol1_clone 1028MB 1028MB ( offline) Samlet Fordelt Bruges Lagerstatus Samlet areal 55GB 51GB 3494MB Snap reserve 611MB 21 MB 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 

SE OGSÅ

vol , partner , snapmirror , sysconfig .


Indholdsfortegnelse






















































Categories: Manual Pages Tags: , , , ,

jf.

July 7th, 2009 Chris Kranz No comments

Table of Contents

NAVN

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

BESKRIVELSE

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.

muliggøre
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.

Tvinger en filer til at overtage sin partner selvom filer opdager en fejl, som ellers ville forhindre en overtagelse. For eksempel normalt, hvis en aftagelig eller defekt ServerNet kablet mellem filers bevirker filers har NVRAM indholdet blive synkroniserede, er overtagelse deaktiveret. Men, hvis du indtaster jf. forcetakeover kommando, filer overtager sin partner på trods af de usynkroniserede NVRAM indholdet. Denne kommando kan medføre, at filer bliver overtaget at miste kundedata. Hvis du bruger-f option, jf. kommandoen tillader en sådan forcetakeover at fortsætte uden at kræve bekræftelse af operatøren.

forcetakeover-d [f] tvinger en filer til at overtage sin partner i alle tilfælde, hvor en forcetakeover ville mislykkes. Desuden vil det tvinge en overtagelse, selvom nogle partnerlande mailboks diske er utilgængelige. Det kan kun bruges, når cluster_remote er licenseret.

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.

Hvis du bruger-n mulighed, jf. kommandoen tillader en overtagelse for at fortsætte, selvom partneren node kørte en inkompatibel version af Data ONTAP. Partneren node skal omhyggelig standses for at denne mulighed for at lykkes. Dette bruges som en del af en nondisruptive opgradering proces.

NFO [Aktiver | deaktivere] disk_shelf
Aktiverer eller deaktiverer forhandlet failover på disken hylde tæller mismatch.

Denne kommando er forældet. Mulighed cf.takeover.on_disk_shelf_miscompare erstatter det.

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.

SE OGSÅ

partner


Indholdsfortegnelse



Categories: Manual Pages Tags: , , , ,

bootfs

July 7th, 2009 Chris Kranz No comments

Table of Contents

NAVN

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

BESKRIVELSE

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.

EKSEMPLER

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 

SE OGSÅ

Download


Indholdsfortegnelse

Categories: Manual Pages Tags: , , , ,

boot

July 7th, 2009 Chris Kranz No comments

Indholdsfortegnelse

NAVN

boot – directory of Data ONTAP executables

SYNOPSIS

/etc/boot

BESKRIVELSE

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.

SE OGSÅ

Download


Indholdsfortegnelse

Copyright © 1994-2008 NetApp, Inc. Juridisk information

VN: F [1.9.11_1134]
Bedømmer dette indlæg:
Karakter: 0.0 / 10 (0 stemmer)

Categories: Manual Pages Tags: , , , ,

bmc

July 7th, 2009 Chris Kranz No comments

Indholdsfortegnelse

NAVN

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

SYNOPSIS

bmc help

bmc reboot

bmc setup

bmc status

bmc test autosupport

BESKRIVELSE

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

OPTIONS

hjælpe
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.

EKSEMPLER

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 

SE OGSÅ

setup , options

NOTES

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


Indholdsfortegnelse

Copyright © 1994-2008 NetApp, Inc. Juridisk information

VN: F [1.9.11_1134]
Bedømmer dette indlæg:
Karakter: 0.0 / 10 (0 stemmer)

Categories: Manual Pages Tags: , , , ,

backuplog

July 7th, 2009 Chris Kranz No comments

Table of Contents

NAVN

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

SYNOPSIS

/etc/log/backup

BESKRIVELSE

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.

Indstillinger
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

SE OGSÅ

dump , restore , options


Indholdsfortegnelse

Categories: Manual Pages Tags: , , , ,

backup

July 7th, 2009 Chris Kranz No comments

Indholdsfortegnelse

NAVN

backup – manages backups

SYNOPSIS

backup status [ <ID> ]

backup terminate <ID>

BESKRIVELSE

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.

BRUG

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.

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

Type
Either dump or NDMP.

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

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

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

SE OGSÅ

dump


Indholdsfortegnelse



Categories: Manual Pages Tags: , , , ,

autosupport

July 7th, 2009 Chris Kranz 2 comments

Indholdsfortegnelse

NAVN

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.

BESKRIVELSE

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

Værtsnavn

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.

SE OGSÅ

options , partner , setup , hosts , RFC821


Indholdsfortegnelse






























































Categories: Manual Pages Tags: , , , ,

auditlog

July 7th, 2009 Chris Kranz No comments

Indholdsfortegnelse

NAVN

auditlog – contains an audit record of recent administrative activity

SYNOPSIS

<logdir>/auditlog

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

BESKRIVELSE

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. En typisk besked er:

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

og

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

SE OGSÅ

options , syslog.conf


Indholdsfortegnelse

Categories: Manual Pages Tags: , , , ,

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

© 2009-2012 Chris Kranz Alle rettigheder forbeholdes
This site is not affiliated or sponsored in anyway by NetApp or any other company mentioned within.