Arxiu

Entrades etiquetades 'home'

NetApp Pàgines home

7 juliol 2009

NetApp han tingut l'amabilitat m'ha donat permís per publicar les seves pàgines del manual aquí. Ells encara necessiten una mica de neteja, però la gran quantitat vol dir que em portarà un temps per arribar a tots ells classificats i amb referències creuades correctament, demano disculpes per qualsevol problema visual, de moment. Vaig escriure una eina d'anàlisi ràpid per obtenir tota la informació aquí, el que pot haver-hi algunes qüestions que resulten d'aquesta encara.

Sempre m'ha agradat la forma en què les seves pàgines PHP tenen la funció donant als usuaris la possibilitat de comentar directament sobre ells. Això permet a la gent a deixar comentaris sobre les funcions i eines, i també un seguiment amb alguns usos addicionals o sintaxi de comandes que no necessàriament són clarament publicades. Esperem que això es pot alimentar de nou en NetApp per millorar la seva documentació.

Definitivament m'agradaria animar la gent a comentar a les pàgines del manual amb tot el que pot ser útil, i esperem que això en una secció de referència poc útil. Moltes gràcies de nou per la gent de NetApp per ajudar amb això.

VN: F [1.9.3_1094]
Qualificar aquesta entrada:
Qualificació: 9,0 / 10 (9 vots)

General , Pàgines de manual , , , ,

Aggr

7 juliol 2009

Taula de continguts

NAME

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

SYNOPSIS

aggr command argument …

DESCRIPTION

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

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's contents are currently out of date and are in the process of being resynchronized with the contents of the other plex of the aggregate (applies to mirrored aggregates only).

adding disks
Disks are being added to the plex's RAID group(s).

out-of-date
This state only occurs in mirrored aggregates where one of the plexes has failed. The non-failed plex will be in this state if it needed to be resynchronized at the time the other plex failed.

A plex is named using the name of the aggregate, a slash character delimiter, and the name of the plex. The system automatically selects plex names at creation time. For example, the first plex created in aggregate aggr0 would be aggr0/plex0 .

An aggregate may be online, restricted, or offline. When an aggregate is offline, no read or write access is allowed. When an aggregate is restricted, certain operations are allowed (such as aggregate copy, parity recomputation or RAID reconstruction) but data access is not allowed. Aggregates that are not a part of a traditional volume can only be restricted or offlined if they do not contain any flexible volumes.

Aggregates can be in combinations of the following states:

aggr The aggregate is a modern-day aggregate; it is capable of containing zero or more flexible volumes.

copying
The aggregate is currently the target aggregate of an active aggr copy operation.

degraded
The aggregate contains at least one degraded RAID group that is not being reconstructed.

foreign
The disks that the aggregate contains were moved to the current filer from another filer.

growing
Disks are in the process of being added to the aggregate.

initializing
The aggregate is in the process of being initialized.

invalid
The aggregate contains no volumes and none can be added. Typically this happens only after an aborted aggregate copy operation.

ironing
A WAFL consistency check is being performed on this aggregate.

mirror degraded
The aggregate is a mirrored aggregate, and one of its plexes is offline or resyncing.

mirrored
The aggregate is mirrored and all of its RAID groups are functional.

needs check
A WAFL consistency check needs to be performed on the aggregate.

partial
At least one disk was found for the aggregate, but two or more disks are missing.

raid0 The aggregate consists of RAID-0 (no parity) RAID groups (V-Series and NetCache only).

raid4 The aggregate consists of RAID-4 RAID groups.

raid_dp
The aggregate consists of RAID-DP (Double Parity) RAID groups.

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

USAGE

The following commands are available in the aggr suite:

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

aggr add aggrname
[ -f ]
[ -n ]
[ -g { raidgroup | new | all } ]
{ ndisks [@ size ]
|
-d disk1 [ disk2 ... ] [ -d diskn [ diskn+1 ... ] ] }

Afegeix discs a l'anomenat aggrname agregat. Especificar els discos de la mateixa manera que per al Aggr crear comandes. Si el conjunt es reflecteix, llavors l'argument-d ha de ser utilitzat dues vegades (si escau).

Si l'opció-g no s'utilitza, els discos es sumen al grup creat RAID útils, més recentment, està ple i, a continuació un o més nous es creen grups RAID i els discs restants s'afegeixen als nous grups. Qualsevol altres grups RAID existent que no estiguin plens romanen parcialment plens.

g permet l'opció-L'especificació d'un grup RAID (per exemple, rg0) a la qual els discs indicats cal afegir, o un mètode pel qual els discs s'afegeixen als ja existents o nous grups RAID.

Si l'opció-g s'utilitza per especificar un grup RAID, RAID que el grup ha d'existir. Els discs es sumen a aquest grup RAID útil que està ple. Tots els discs restants s'ignoren.

Si l'opció-g és seguit de nou, Data ONTAP crea un o més grups RAID i afegeix els discs d'ells, fins i tot si els discs es podria en un grup RAID existents. Cap grup RAID existents que no estiguin plens romanen parcialment plens. El nom dels nous grups RAID es seleccionen automàticament. No és possible especificar els noms dels grups RAID.

Si l'opció-g és seguit per tots, Data ONTAP afegeix els discs especificats als actuals grups de la primera incursió. Després de tots els grups existents RAID estan plens, es crea un o més grups RAID i afegeix els discs especificats als nous grups.

L'opció-n es pot utilitzar per mostrar la comanda que el sistema s'executarà, sense realitzar cap canvi. Això és útil per a la visualització dels discos seleccionats automàticament, per exemple.

Per defecte, el contribuent s'omple d'un grup RAID amb discs abans d'iniciar un altre grup RAID. Suposem que un agregat en l'actualitat té un grup RAID de 12 discos i la seva mida és de 14 grup RAID. Si afegeix 5 discs d'aquest conjunt, que tindrà un grup RAID amb discs de 14 i un altre grup RAID amb 3 discs. L'arxivador no distribuir equitativament entre els grups de discos RAID.

No es pot afegir discs en un mirall global si un dels plexes està en línia.

Els discs en un complex no es permet a les piscines disc clar. Aquest comportament pot ser anul.lat amb la bandera-f quan s'utilitza juntament amb l'argument-d de la llista de discs per afegir. El flag-f, en combinació amb-d, també pot ser usat per forçar l'addició de discos que tenen una velocitat de rotació que no coincideix amb la de la majoria dels discos existents en l'agregat.

Aggr [avortar h] en paper operation_number | tots

Acaba operacions de còpia total. El paràmetre t ion_number opera_ s'especifica que l'operació acabi. Si s'especifica tot, tots els actius operacions de còpia agregada s'acaben.

Aggr iniciar la còpia
[S |-s instantània] [-C]
origen destinació

Còpia totes les dades, incloses les instantànies i els volums flexibles, d'un conjunt a un altre. Si l'opció-S s'utilitza la comanda de les còpies en totes les instantànies de la font global per al conjunt de destinació. Per especificar una imatge particular per copiar, l'opció-s seguit per l'ús del nom de la instantània. Si no utilitza cap dels S-ni-s en la comanda, el contribuent crea una instantània en el moment de la còpia Aggr comanda d'inici s'executa i que només còpies d'instantànies per al conjunt de destinació.

El flag-C és necessari si l'agregat d'origen ha tingut l'espai lliure de desfragmentació a terme en ella, o si el conjunt de destinació serà l'espai lliure desfragmentar. L'espai lliure de desfragmentació es pot realitzar en un agregat mitjançant la reassignació de comandes.

còpies agregades només es pot realitzar entre els agregats que allotgen flexibles volums. Agregats que s'incrusten en els volums tradicionals no poden participar.

L'origen i destí poden ser agregats en l'arxivador mateix o per parella diferent. Si l'origen o destinació global està en un arxivador diferent d'aquell en què s'introdueix la còpia Aggr comanda d'inici, especifiqui el nom agregat a la filer_name: g format ate_name aggre_.

Els contribuents que participen en una còpia global ha de complir els requisits per a la còpia Aggr comanda d'inici que s'ha completat correctament:

L'agregat d'origen ha d'estar en línia i el conjunt de destinació ha de ser restringit.

Si la còpia és entre dos contribuents, cada arxivador ha de ser definit com un host de confiança del arxivador altres. És a dir, és el nom del arxiu ha d'estar en el / / hosts.equiv etc l'arxivador d'altres.

Si la còpia es troba en l'arxivador mateix, localhost ha de ser inclòs en arxivador / arxiu / hosts.equiv etc. A més, la direcció de bucle invertit ha d'estar en etc / hosts l'arxivador / arxiu. En cas contrari, el contribuent no pot enviar paquets a si mateix a través de l'adreça de bucle invertit quan es tracta de copiar les dades.

L'espai en disc utilitzable del conjunt de destinació ha de ser major o igual que l'espai en disc utilitzable del total de la font. Utilitzeu el DF-Un comandament de ruta per veure la quantitat d'espai utilitzable d'un agregat particular.

Cada còpia Aggr comanda d'inici de les operacions de còpia genera dos agregats: un per a lectura de dades des de la font d'agregat i una per a escriure dades en el conjunt de destinació. Cada arxivador suporta fins a quatre operacions simultànies còpia agregada.

Aggr [Estat de la còpia operation_number]

Mostra el progrés d'una o totes les operacions de còpia Aggr. Les operacions estan numerats del 0 al 3.

Informació de reinici de punt de comprovació per a totes les transferències també es mostra.

Aggr [accelerador còpia operation_number valor]

Controla el rendiment de l'operació de còpia Aggr. El valor oscil entre 10 (màxima velocitat) a 1 (una desena part de velocitat màxima). El valor per defecte es manté en els aggr.copy.throttle opció arxivador i s'estableix en 10 (velocitat màxima) a la fàbrica. Pot aplicar el valor de rendiment per a una operació especificada pel paràmetre operation_number. Si no s'especifica un nombre d'operació en la còpia Aggr comandament de l'accelerador, la comanda s'aplica a totes les operacions de còpia Aggr.

Utilitzeu aquesta comanda per a limitar la velocitat de l'operació de còpia Aggr si sospita que l'operació de còpia Aggr està causant problemes de rendiment en el seu arxiu. En particular, l'accelerador està dissenyat per ajudar a limitar l'ús de la CPU de l'operació de còpia Aggr. No es pot utilitzar per ajustar els patrons de consum d'ample de banda de xarxa.

The aggr copy throttle command only enables you to set the speed of an aggr copy operation that is in progress. To set the default aggr copy speed to be used by future copy operations, use the options command to set the aggr.copy.throttle option.

aggr create aggrname
[ -f ]
[ -m ]
[ -n ]
[ -t raidtype ]
[ -r raidsize ]
[ -T disk-type ]
[ -R rpm ]
[ -L [ compliance | enterprise ] ]
[ -v ]
[ -l language-code ]
{ ndisks [@ size ]

|
-d disk1 [ disk2 ... ] [ -d diskn [ diskn+1 ... ] ] }

Creates a new aggregate named aggrname . The aggregate name can contain letters, numbers, and the underscore character(_), but the first character must be a letter or underscore. Up to 200 aggregates can be created on each filer. This number includes those aggregates that are embedded within traditional volumes.

An embedded aggregate can be created as part of a traditional volume using the -v option. It cannot contain any flexible volumes.

A regular aggregate, created without the -v option, can contain only flexible volumes. It cannot be incorporated into a traditional volume, and it contains no volumes immediately after creation. New flexible volumes can be created using the vol create command.

The -t raidtype argument specifies the type of RAID group(s) to be used to create the aggregate. The possible RAID group types are raid4 for RAID-4, raid_dp for RAID-DP (Double Parity), and raid0 for simple striping without parity protection. The default raidtype for aggregates and traditional volumes on filers is raid_dp . Setting the raidtype is not permitted on V-Series systems; the default of raid0 is always used.

The -r raidsize argument specifies the maximum number of disks in each RAID group in the aggregate. The maximum and default values of raidsize are platform-dependent, based on performance and reliability considerations. See aggr options raidsize for more details.

The -T disk-type argument specifies the type of disks to use when creating a new aggregate. It is needed only on systems connected to disks of different types. Possible disk types are: ATA , FCAL , LUN , SAS , SATA , and SCSI . Mixing disks of different types in one aggregate is not allowed. -T cannot be used together with -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.

L'opció-n es pot utilitzar per mostrar la comanda que el sistema s'executarà, sense realitzar cap canvi. Això és útil per a la visualització dels discos seleccionats automàticament, per exemple.

Si utilitzeu l'opció-d disk1 [disk2 ... argument], el contribuent crea el conjunt amb la llanta de recanvi discs especificats disk1, disk2, etc. Podeu especificar una llista separada per espais de noms de disc. Dues llistes separades s'ha d'especificar si l'agregat de nou es reflecteix. En el cas que l'agregat de nou es repeteix, si els discs s'indica ha de resultar en un nombre igual de discs en cada complex nou.

Els discs en un complex no es permet que abasten grups de reposicions. Aquest comportament pot ser anul.lat amb l'opció f-. La mateixa opció també es pot utilitzar per obligar a utilitzar discs que no tenen concordança velocitat de rotació. L'opció f-es farà efectiu només quan s'utilitza amb l'opció-d especifica discs a utilitzar.

Per crear un agregat SnapLock, especifiqueu l'opció-L amb el Aggr crear comandes. Aquesta bandera només s'admet si bé el compliment de SnapLock o SnapLock Enterprise amb llicència. El tipus d'agregat SnapLock creat, ja sigui de compliment o empresa, està determinada per la llicència d'SnapLock instal lat. Si tant el compliment de SnapLock i Empresa SnapLock tenen llicència, el compliment o la L - L de l'empresa utilitza per especificar el tipus desitjat d'agregat.

-L'argument de la language_code l pot ser utilitzat només quan es crea un volum tradicional usant l'opció-v. L'arxivador crea el volum tradicional amb l'idioma especificat pel codi de la llengua. El valor per defecte és l'idioma utilitzat pel volum d'arrel l'arxivador. Veure la vol pàgina del manual per a una llista de codis d'idioma.

(Destruir Aggr aggrname | plexname) [-f]

Destrueix el nom aggrname agregada, o el complex anomenat plexname. Tingueu en compte que si l'agregat especificat està vinculat a un volum tradicional, llavors el volum tradicional mateixa es destrueix també.

Si s'especifica un agregat, tots els plexes en conjunt, són destruïts. El nomenat agregat no ha de contenir també els volums flexibles, independentment del seu estat de muntatge (en línia, restringit, o sense connexió). Si s'especifica un complex, el complex es destrueix, deixant un volum total sense reflex o tradicionals que contenen el complex restants. Abans de destruir l'agregat, el volum tradicional o complex, es demana a l'usuari que confirmi l'operació. La bandera-f es pot utilitzar per destruir un agregat, el volum tradicional o complexes sense preguntar a l'usuari.

Els discs originalment en l'objecte es van destruir els discos de recanvi. Només els agregats en línia, els volums tradicionals i plexes poden ser destruïts.

Aggr media_scrub estat [aggrname | plexname | groupname]
[V]

Imprimeix els mitjans de comunicació de l'estat de rentat nomenat agregat, complex, o grup. Si no es dóna el nom, la seva situació s'ha imprès en tots els grups RAID està executant una neteja mitjans de comunicació. L'estatut inclou una completa cent-i si se suspèn.

-V mostra la bandera de la data i l'hora en les quals els matolls mitjans complert en darrer lloc, la data i hora en què la instància actual dels mitjans de comunicació va començar a fregar, i l'estat actual del nomenat agregat, complex, o grup. Si no es dóna el nom, l'estat més detallat s'imprimeix en tots els grups RAID amb matolls mitjans actius.

Aggr aggrname mirall
[-F]
[-N]
[V] victim_aggrname
[-D disk1 [disk2 ... ]]

Resulta un conjunt sense reflex en un mirall global mitjançant l'addició d'un complex a la mateixa. El complex és de recent creació ja sigui de discos seleccionats d'un grup de recanvi, o bé, si l'opció-v l's'especifica, es pren d'una altra existent sense reflex agregat. aggrname agregat ha d'estar actualment sense reflex. Aggr ús per crear un nou mirall agregat a partir de zero.

Els discs es poden especificar explícitament usant-d de la mateixa manera com amb el Aggr Aggr crear i afegir comandes. El nombre de discos indicat ha de coincidir amb el número present en el total existent. Els discs s'especifica no se'ls permet a les piscines disc clar. Aquest comportament pot ser anul.lat amb l'opció f-. L'opció f, en combinació amb-d, també es pot utilitzar per obligar a utilitzar discos que tenen una velocitat de rotació que no coincideix amb la de la majoria dels discos existents en l'agregat.

Si els discs no s'especifiquen de forma explícita, a continuació, els discos es seleccionen automàticament per adaptar-se als complexos existents en el conjunt de.

V L'opció-pot servir per unir victim_aggrname de nou en aggrname per formar un mirall global. El resultat és un reflex anomenat aggrname granulat, que és idèntica a aggrname abans de l'operació. Victim_aggrname és realment destruït. Victim_aggrname ha d'haver estat prèviament reflectit amb aggrname, a continuació, separats per la comanda Dividir Aggr. Victim_aggrname ha d'estar fora de línia. Combinada amb l'opció-v, l'opció-f pot servir per unir i aggrname im_aggrname t vic_ sense preguntar a l'usuari.

L'opció-n es pot utilitzar per mostrar la comanda que el sistema s'executarà sense haver de realitzar cap canvi. Això és útil per a la visualització dels discos seleccionats automàticament, per exemple.

Aggr línia (aggrname | plexname)
t cifsdelaytime] [

Pren el nom aggrname agregada (o el complex anomenat plexname) en línia. L'ordre entrarà en vigor abans de tornar. Si el conjunt es troba ja en estat restringit, llavors ja està disponible per a accés de dades, i gran part de la descripció següent no s'aplica.

Si el conjunt conté els volums flexibles, l'operació es avorta si l'arxiu està en mode de manteniment.

Excepte en el mode de manteniment, l'agregat que conté el volum arrel actual no pot ser pres fora de línia. Un agregat que contingui un volum que s'ha marcat per convertir-se en root (utilitzant les opcions de vol n arrel estimi vol_) tampoc pot ser pres fora de línia.

Si el conjunt està integrat en un volum tradicional que té quotes de CIFS, els usuaris han de ser advertits abans de prendre l'agregat (i per tant el volum tradicional sencer) en línia. Utilitza el-t per a això. L'argument cifsdelaytime especifica el nombre de minuts a esperar abans de prendre l'agregat incorporat en línia, durant el qual CIFS vegada que els usuaris del volum tradicional se'ls adverteix de la pèrdua a l'espera del servei. Un temps de 0 significa prendre la línia agregada immediatament sense advertències. CIFS usuaris poden perdre dades si no se'ls dóna l'oportunitat de posar fi a les sol licituds de gràcia.

Si s'especifica un plexname, el complex ha de ser part d'un mirall global i ambdós plexes ha d'estar en línia. Abans de offlining un complex, el sistema eliminarà totes les dades interns de memòria intermèdia associat amb el complex i crear una instantània del que està escrit a dos plexes. La instantània permet resincronització eficient quan el complex és posteriorment tornat en línia.

Una sèrie d'operacions que s'efectuen en els tradicionals al volum total de la línia pot prevenir Aggr de tenir èxit, durant diferents períodes de temps. Si aquestes operacions es troben, caldrà esperar un segon per a aquestes operacions a fi. Si no ho fa, la comanda es avorta.

Un xec és també per als arxius en el conjunt d'associats volum tradicional oberta pels processos interns de ONTAP. La comanda es avorta si es troba.

Aggr línia (aggrname | plexname)
[-F]

Porta el nom aggrname agregada (o el complex anomenat plexname) en línia. Aquesta ordre entrarà en vigor immediatament. Si l'agregat especificat està incrustat en un volum tradicional, el volum també és també lloc en línia.

Si un aggrname s'especifica, ha d'estar actualment en línia, restringit, o estrangers. Si el conjunt és estranger, es farà nadius abans de comparèixer en línia. Un "estranger" global és un afegit que es compon de discos ha mudat d'un altre contribuent, i que mai ha estat posat en línia en l'arxivador actual. Els agregats que no són estrangers són considerats com a "nadius".

Si el conjunt és incoherent, però no ha perdut les dades, l'usuari serà advertit i avisat abans del que el total de línia. La bandera-f es pot utilitzar per canviar aquest comportament. És aconsellable executar WAFL_check (o fer un SnapMirror inicialitzar en el cas d'un conjunt integrat en un volum tradicional) amb anterioritat a la interposició d'un total de línia incoherent. Portar un augment global en línia incompatible el risc de corrupció més sistema d'arxius. Si el conjunt és inconsistent i ha experimentat una possible pèrdua de dades, no pot posar en connexió a menys WAFL_check (o SnapMirror inicialitzar en el cas integrat) s'ha executat en l'agregat.

Si s'especifica un plexname, el complex ha de ser part d'una línia mirall global. El sistema iniciarà la resincronització de les complexes com a part del processament en línia.

opcions Aggr aggrname [nom_opció] optval

Mostra les opcions que s'han fixat per aggrname agregat, o estableix l'opció de trucada de l'anomenada nom_opció aggrname agregada als optval valor. La comanda segueix sent eficaç després que el contribuent es reinicia, el que no hi ha necessitat d'afegir opcions Aggr comandaments al / etc / rc. Algunes opcions tenen valors que són números. Algunes opcions tenen valors reflectides a (que també es pot expressar com sí, és cert, o 1) o apagar (que també pot expressar com no, falsa, o 0). Una barreja de majúscules i minúscules es poden utilitzar en escriure el valor d'una opció. La comanda d'estat Aggr mostra les opcions que s'estableixen per cada agregat.

A continuació es descriuen les opcions i els seus valors possibles:

fs_size_fixed on | off

Aquesta opció només s'aplica als agregats que s'incrusten en els volums tradicionals. Fa que el sistema d'arxius que romanen de la mateixa mida i no creixen o es encongeixen quan una relació volum SnapMirror es trenca, o un complement Aggr es realitza en ell. Aquesta opció s'ajusta automàticament a estar en un volum tradicional quan es converteix en un volum SnapMirror. Romandrà en la comanda després de trencar SnapMirror que s'expedeixi per volum tradicional. Això permet un volum tradicional que es SnapMirror nou a la font sense necessitat d'afegir discs a la font de volum tradicional. Si la mida dels volums tradicionals és més gran que la mida del sistema de fitxers, desactivar aquesta opció forçarà que el sistema de fitxers a créixer fins a la mida del volum tradicional. La configuració per defecte està desactivada.

ignore_inconsistent on | off

Aquesta comanda només es pot utilitzar en mode de manteniment. Si s'estableix aquesta opció, permet l'afegit que conté el volum arrel perquè sigui posat en línia durant l'arrencada, tot i que no és coherent. S'adverteix a l'usuari que posar-la en línia abans de córrer o WAFL_check wafliron pot donar lloc a la inconsistència del sistema de fitxers més.

nosnap on | off

Si aquesta opció està activada, deshabilita les instantànies automàtiques en l'agregat. La configuració per defecte està desactivada.

nombre raidsize

El valor d'aquesta opció és la mida màxima d'un grup RAID que es poden crear en l'agregat. Canviar el valor d'aquesta opció no farà que els grups existents de RAID per augmentar o disminuir, sinó que només afectarà més discos si s'afegeix a l'última existent RAID grup i el gran que nous grups RAID serà.

Els valors permesos per a aquesta opció dependrà de RaidType. Per exemple, permet a les grans raid_dp grups RAID de raid4. Límits i valors per defecte són també diferents per a diferents tipus d'aparells arxivador i diferents tipus de discs. Després de definir els límits de les taules i els valors per defecte per raidsize.

  -------------- Raid4 màxim predeterminat raidsize mín -------------- R100 R150 2 8 8 2 6 6 2 7 14 FAS250 altres (discs FCAL) 8 febrer 1914 altres (ATA discs) 2 7 juliol -------------- -------------- raid_dp predeterminat raidsize ------ mín màx -------- R100 R150 3 12 12 3 12 16 altres (discs FCAL) 16 març 1928 altres (discs ATA) 14 març 1916 ---------- ---- 

Els valors poden canviar en futures versions de Data ONTAP.

RaidType raid4 | raid_dp | RAID 0

Estableix el tipus de RAID utilitza per protegir contra errors de disc. L'ús d'raid4 proporciona un disc de paritat RAID per grup, mentre que raid_dp proporciona dos. Canviar aquesta opció canvia immediatament el tipus de RAID de tots els grups RAID dins de l'agregat. En actualitzar els grups RAID de raid4 a raid_dp, cada grup comença una reconstrucció RAID i en un disc extra per `dparity" paritat del segon disc.

Canviar aquesta opció també canvia amb les condicions necessàries raidsize més valor pel RaidType nou. Quan s'actualitza de raid4 a raid_dp, raidsize s'incrementarà en el valor predeterminat per raid_dp. Quan desqualificació de raid_dp a raid4, raidsize es reduirà a la mida dels més grans existents RAID grup si està entre el valor per defecte i el límit de raid4. Si el RAID major grup està per sobre del límit de raid4, el nou raidsize serà el límit. Si el RAID major grup és inferior al valor per defecte per raid4, el nou raidsize serà el valor per defecte. Si raidsize és ja inferior al valor per defecte per raid4, es redueix en 1.

nombre resyncsnaptime

Aquesta opció s'utilitza per establir la freqüència de resincronització de duplicacions d'instantànies (en minuts). El valor per defecte és de 60 minuts.

arrel

Si aquesta opció es troba en un volum tradicional, llavors l'efecte és idèntic com es defineix en el vol pàgina del manual. En cas contrari, si aquesta opció està establerta en un agregat capaços de contenir volums flexibles, que s'agreguen es marca com la que conté també l'origen de volum flexible al reiniciar. Aquesta opció es pot utilitzar en un sol volum global o tradicionals en un moment donat. L'agregat arrel existent o el volum tradicional es convertirà en una entitat sense ànim d'arrel després del reinici.

Fins que el sistema és reiniciat, el conjunt original i / o volum tradicional seguirà mostrant l'arrel com una de les seves opcions, i l'agregat de noves arrels tradicionals o volum mostrarà diskroot com una opció. En general, l'agregat que té l'opció diskroot és la que contindrà l'origen de volum flexible que recorri el reiniciar.

L'única manera d'eliminar l'estat de l'arrel d'un volum total o tradicional és establir l'opció d'arrel en un altre o tradicionals volum total.

snaplock_compliance

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

snaplock_enterprise

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

snapmirrored off

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

snapshot_autodelete on | off

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

aggr rename aggrname newname

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

aggr restrict aggrname
[ -t cifsdelaytime ]

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

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

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

aggr scrub resume [ aggrname | plexname | groupname ]

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

aggr scrub start [ aggrname | plexname | groupname ]

Inicia la depuració de paritat en l'agregat en línia amb nom. rentat de paritat es comparen els discos de dades en el disc de paritat (s) en el seu grup RAID, la correcció dels continguts del disc de paritat, segons sigui necessari. Si no es dóna el nom, netejar la paritat s'ha iniciat en tots els agregats en línia. Si un nom global s'indica, la neteja es troba iniciat en tots els grups RAID contingudes en l'agregat. Si un nom complex es dóna, la neteja s'ha iniciat en tots els grups RAID que figuren en el complex.

matolls Aggr estat [aggrname | plexname | nom de grup] [-v]

Imprimeix l'estat de rentat de la paritat en el conjunt amb nom, complex, o grup, tots els grups de RAID i en procés de rentat de paritat si no té un nom determinat. L'estatut inclou una completa cent-, i l'estat de suspensió de la mala herba.

-V mostra la bandera del dia i l'hora en què el matoll complet complert en últim lloc juntament amb l'estat actual al nomenat agregat, complex, o grup, tots els grups RAID, si no es dóna el nom.

matolls Aggr atur [aggrname | plexname | groupname]

Deixa de fregar la paritat en el conjunt amb nom, complex, o grup, i si no té un nom donat, en tots els grups RAID actualment objecte d'una depuració de paritat.

matolls Aggr suspendre [aggrname | plexname | groupname]

Suspèn rentat de la paritat en el conjunt amb nom, complex, o grup, i si no té un nom donat, en tots els grups de RAID i en procés de rentat de paritat.

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

Displays the space usage in an aggregate. Unlike df, this command shows the space usage for each flexible volume within an aggregate If aggrname is specified, aggr show_space only runs on the corresponding aggregate, otherwise it reports space usage on all the aggregates.

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

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

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

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

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

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

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

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

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

Si el complex d'un conjunt integrat dins d'un volum tradicional no està en línia en el moment de la divisió, la suma resultant serà en línia. En dividir un complex d'un total de volums que hi ha flexible, si aquest complex no està en línia, però el conjunt no està en línia, el total resultant es posarà en connexió, i el seu volum flexible canviar el nom. No es permet dividir un complex d'un total de connexió.

Un mirall poden ser posades de nou junts es van unir a través de l'opció-v per a la Aggr mirall.

Aggr estat [aggrname]
[-R |-v | d-|-c |-b |-s |-f |-i]

Mostra l'estat dels agregats d'un o tots en l'arxivador. Si aggrname s'utilitza, l'estat de la suma especificada s'imprimeix, en cas contrari la situació de tots els agregats en l'arxivador s'imprimeixen. Per defecte, s'imprimeix una línia d'una sinopsi de la suma que inclou el nom d'agregat, ja sigui que contingui un sol volum tradicional o algun nombre de volums flexibles, si és en línia o sense connexió, altres estats (per exemple, parcial, degradats, inconsistents, i així successivament) i peraggregate WAFL opcions. -Agregat opcions per només apareixen si les opcions s'han canviat dels valors per defecte del sistema utilitzant les opcions de comandes Aggr, o per la comanda opcions vol si l'agregat està incrustat en un volum tradicional. Si l'estat incoherent WAFL es mostra, si us plau poseu-vos en contacte amb Atenció al client.

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

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

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

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

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

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

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

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

      unknown           Failure reason unknown. failed            Data ONTAP failed disk due to a                         fatal disk error. admin failed      User issued a 'disk fail' command                         for this disk. labeled broken    Disk was failed under Data ONTAP                         6.1.X or an earlier version. init failed       Disk initialization sequence failed. admin removed     User issued a 'disk remove' command                         for this disk. not responding    Disk not responding to requests. pulled            Disk was physically pulled,  or no                         data path exists on which to access                         the disk. bypassed          Disk was bypassed by ESH. 

aggr undestroy [ -n ] < aggrname >

Undestroy a partially intact or previously destroyed aggregate or traditional volume. The command prints a list of candidate aggregates and traditional volumes matching the given name, which can be potentially undestroyed.

The -n option prints the list of disks contained by the aggregate or by the traditional volume, which can be potentially undestroyed. This option can be used to display the result of command execution, without actually making any changes.

aggr verify resume [ aggrname ]

Resumes RAID mirror verification on the named aggregate; if no aggregate name is given, on all aggregates currently undergoing a RAID mirror verification that has been suspended.

aggr verify start [ aggrname ] [ -f plexnumber ]

Starts RAID mirror verification on the named online mirrored aggregate. If no name is given, then RAID mirror verification is started on all online mirrored aggregates. Verification compares the data in both plexes of a mirrored aggregate. In the default case, all blocks that differ are logged, but no changes are made. If the -f flag is given, the plex specified is fixed to match the other plex when mismatches are found. A name must be specified with the -f plexnumber option.

aggr verify stop [ aggrname ]

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

aggr verify status [ aggrname ]

Prints the status of RAID mirror verification on the named aggregate; on all aggregates currently undergoing RAID mirror verification if no aggregate name is given. The status includes a percent-complete, and the verification's suspended status.

aggr verify suspend [ aggrname ]

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

CLUSTER CONSIDERATIONS

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

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

EXAMPLES

aggr create aggr1 -r 10 20

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

aggr create aggr1 20@9

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

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

Creates an aggregate named aggr1 with the specified three disks.

aggr create aggr1 10
aggr options aggr1 raidsize 5

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

aggr show_space -h ag1

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

   AG1 'Espai total agregat de reserva WAFL complement reserva d'espai utilitzable BSR NVLOG 66GB 6797MB 611MB 59GB 65KB espai assignat als volums en el volum total assignat ª mà Garantia vol1 11ES 14GB 8861MB 8871MB volum vol2 arxiu VOL3 6161MB 6169MB cap VOL4 26GB 25 GB 1028MB 1028MB vol1_clone volum ( en línia) total assignat d'Espai utilitzat Disponibilitat Total 55GB 51 GB 3494MB reserva complement 21MB 611MB 590MB reserva WAFL 6797MB 6792MB 5480KB 

Aggr estat aggr1-r

Mostra la informació sobre RAID aggr1 agregada. En el següent exemple, veiem que és un agregat aggr1 RAID-DP protegits per les sumes de comprovació de bloc. És en línia, i tots els discs estan funcionant normalment. El conjunt consta de quatre discos i dos discs de dades, un disc de paritat, i un disc doubleparity. Dos discos es troben en 0B adaptador, i dos en 1b adaptador. La plataforma i els números de la badia de disc per a cada disc s'indiquen. Els quatre discos són de 10, 000 RPM discos Fibre Channel connectat a través del canal de disc A. El disc "Pool" atribut només es mostra si SyncMirror té llicència, que no és el cas aquí (si és SyncMirror tenien llicència, Piscina seria 0 o 1) . La quantitat d'espai en disc que s'utilitza per Data ONTAP ("Used") i està disponible al disc ("Phys") es mostra en les columnes més a la dreta.

  Aggr aggr1 (en línia, raid_dp) (sumes de comprovació de bloc) plexe / aggr1/plex0 (en línia, normal i activa) RAID grup / aggr1/plex0/rg0 (normal) de dispositius RAID de discs HA Prestatge BAY CHAN Pool Tipus ª mà RPM (MB / BLKS) Phys (MB / BLKS) --- - ----- - - - - ----- ----- dparity 0b.16 0B 1 0 FC: A - 10000 136000/278528000 FCAL 137104/280790184 paritat 1b.96 1b 6 0 FC: A - 10000 136000/278528000 FCAL 139072/284820800 dades 0b.17 0B gener 1 FC: A - 10000 136000/278528000 FCAL 139072/284820800 dades 1b.97 1b 1 juny FC: A - 10000 136000 / 278528000 FCAL 139072 / 284820800 

VEURE TAMBÉ

vol , El soci , SnapMirror , Sysconfig .


Taula de continguts






















































Pàgines de Manual , , , ,

cf

7 juliol 2009

Taula de continguts

NOM

cf - controla l'adquisició i les operacions giveback dels principals usuaris d'un clúster

SINOPSI

[Cf | impossibilitar permeten forcegiveback | | forcetakeover [gl] giveback | [-f] | hw_assist [estat de la prova | Estadístiques [clara]] | Monitor | parella | L'estat [-t adquisició] [-f] | [-n] ]

cf NFO [permeten desactivar disk_shelf] |

cf NFO estat

DESCRIPCIÓ

La comanda cf els controls del monitor de commutació per error del clúster, que determinen quan les operacions d'adquisició i giveback tenir lloc en un clúster.

La comanda cf està disponible si el contribuent té la llicència de dispersió.

OPCIONS

desactivar
Desactiva la capacitat d'absorció d'ambdós arxius del clúster.

permetre
Permet la capacitat d'absorció d'ambdós arxius del clúster.

forcegiveback
forcegiveback és perillosa i pot conduir a la corrupció de dades, en gairebé tots els casos, l'ús giveback cf-f al seu lloc.

Forces de viure l'arxivador de retornar els recursos del contribuent, encara que no l'arxivador viu determina que el fer-ho podria danyar les dades o causar altres problemes greus. Giveback es pot negar a giveback en aquestes condicions. Ús de les forces opció forcegiveback 01:00 giveback. Quan es reinicia el contribuent no com a resultat d'una giveback forçats, mostra el següent missatge:

soci giveback incompleta, algunes dades es poden perdre

forcetakeover [-f] forcetakeover és perillosa i pot conduir a la corrupció de dades, en gairebé tots els casos, cf adquisició utilitzar al seu lloc.

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

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

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

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

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

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

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

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

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

Si utilitzeu l'opció-n, la comanda cf permet una presa de possessió de procedir si el node parella estava executant una versió incompatible de Data ONTAP. El node de parella ha de ser netament va aturar perquè aquesta opció per tenir èxit. Això s'utilitza com a part d'un procés d'actualització sense interrupcions.

[NFO enable | disk_shelf disable]
Activa o desactiva la commutació per error negociat en compte desajust disc estant.

Aquesta comanda és obsolet. cf.takeover.on_disk_shelf_miscompare opció que substitueix.

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

nfo status
Displays the current negotiated failover status.

This command is obsolete. Use cf status instead.

SEE ALSO

partner


Table of Contents



Manual Pages , , , ,

bootfs

July 7th, 2009

Taula de continguts

NAME

bootfs – boot file system accessor command (ADVANCED)

SYNOPSIS

bootfs chkdsk disk

bootfs core [ -v ] disk

bootfs dir [ -r ] path

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

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

bootfs format drive [ label ]

bootfs info disk

bootfs sync [ -f ] { disk | drive }

bootfs test [ -v ] disk

DESCRIPTION

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

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

OPTIONS

-v
Turns on verbose output.

-R
Recursively lists directories and files.

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

disk
Un disc és un objecte físic, probablement un compact flash en aquest cas. A nom del disc és en general de la forma [nombre de ranura PCI] A.0, per exemple, 0a.0. Per descobrir d'arrencada del disc el nom del seu, utilitzeu "bootfs ajudar subcomarca".

conduir
Una unitat és una partició amb format al disc. Un disc pot contenir fins a quatre discos. A nom de la unitat és generalment de la forma [nombre de ranura PCI] A.0: partició [
Número]:,
0a.0 per exemple: 1:. Per descobrir el disc d'arrencada el nom del seu, utilitzeu "bootfs ajudar ommand c sub_".

sector
Els discs es divideixen en sectors. Sectors es basen en 0.

raïm
Les unitats es divideixen en grups. Les agrupacions es basen en 2, encara que el directori arrel pot ser pensat residir a cluster 0.

partitionNsizeMB
La mida de la partició de N en megabytes. No hi pot haver un màxim de quatre particions per disc.

etiqueta
Un nen de 11 caràcters o menys corda que els noms de la unitat.

CONSIDERACIONS de dispersió

La comanda bootfs no es pot utilitzar en el sistema en clúster d'un soci.

EXEMPLES

El subcomarca dir mostra tots els fitxers i subdirectoris continguts en la ruta proporcionada. La informació presentada per cada arxiu i subdirectori és (en aquest ordre de les columnes) nom, mida, data, hora, i per conglomerats.

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

  Etiqueta de volum en la unitat 0a.0: 1: és el volum KERNEL número de sèrie és 716C-E9F8 Directori de 0a.0: 1: / x86/kernel /.  2003.02.07 02:37 DIR febrer 1 ..  2003.02.07 02:37 DIR 1:00 PRIMARY.KRN 3 9.318.400 2003.07.04 06:53 p 4 2187264 bytes lliures 

Les llistes subcomarca bolcat d'un o altre sector una en un disc o un grup en una unitat, depenent de la línia d'ordres arguments proporcionats. El sector o grup s'inclou tant en forma hexadecimal i ASCII.

bootfs bolcat 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 0×25a00 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.

0a.0 bootfs format: 1: NetApp

El subcomarca info mostra informació sobre un disc. La ubicació dels elements de diferent tipus i mida de les seccions es mostra.

bootfs informació 0a.0

  ----------------------- Partició: 1 2 3 4 --------------------- - sistema de fitxers: 0 × 01 0 01 0 × × × 01 0 01 bytes per clúster: 4096 4096 4096 4096 nombre de clústers: 2809 2809 2042 251 bytes en total: 11.534.336 11.534.336 8.388.608 1.048.576 bytes utilitzables: 11.501.568 11.501.568 8.359.936 1.024.000 bytes lliures: 11505664 11505664 8364032 1028096 ubicació FAT: 512.512.512.512 ubicació arrel: 9728 9728 6656 1536 les dades de localització: 26.112 26.112 23.040 17.920 

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

bootfs test -v 0a.0

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

SEE ALSO

descarregar


Table of Contents

Manual Pages , , , ,

boot

July 7th, 2009

Taula de continguts

NAME

boot – directory of Data ONTAP executables

SYNOPSIS

/etc/boot

DESCRIPTION

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

FILES

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

SEE ALSO

descarregar


Table of Contents

Copyright © 1994-2008 NetApp, Inc. Legal Information

VN: F [1.9.3_1094]
Qualificar aquesta entrada:
Qualificació: 0.0 / 10 (0 vots)

Manual Pages , , , ,

bmc

July 7th, 2009

Taula de continguts

NAME

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

SYNOPSIS

bmc help

bmc reboot

bmc setup

bmc status

bmc test autosupport

DESCRIPTION

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

OPTIONS

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

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

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

status
Display the current status of the BMC.

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

CLUSTER CONSIDERATIONS

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

EXAMPLES

bmc status

might produce:

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

SEE ALSO

setup , options

NOTES

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


Table of Contents

Copyright © 1994-2008 NetApp, Inc. Legal Information

VN: F [1.9.3_1094]
Qualificar aquesta entrada:
Qualificació: 0.0 / 10 (0 vots)

Manual Pages , , , ,

backuplog

July 7th, 2009

Taula de continguts

NAME

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

SYNOPSIS

/etc/log/backup

DESCRIPTION

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

The following are the events filer monitors:

Començar
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.

Opcions
Logs the options as users specify.

Tape_open
Output device is opened successfully.

Tape_close
Output device is closed successfully.

Phase_change
As dump/restore completes a stage.

Dump specific events:

Snapshot
When the snapshot is created or located.

Base_dump
When a valid base dump entry is located.

Logging events:

Start_logging Logging begins.

Stop_logging
Logging ends.

Each event record is in the following format:

TYPE TIME_STAMP IDENTIFIER EVENT (EVENT_INFO)

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

TIME_STAMP
Shows date and time at which event occurs.

IDENTIFIER
Unique ID for the dump/restore.

EVENT
The event name.

EVENT_INFO
Event specific information.

A typical event record message looks like:

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

In the particular example:

TYPE
= dmp

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

IDENTIFER
= /vol/vol0/ home(5)

EVENT
= Start

EVENT_INFO
= level 0, NDMP

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

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

FILES

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

SEE ALSO

dump , restore , options


Table of Contents

Manual Pages , , , ,

de reserva

July 7th, 2009

Taula de continguts

NAME

backup – manages backups

SYNOPSIS

backup status [ <ID> ]

backup terminate <ID>

DESCRIPTION

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

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

dump
runs natively on the filer.

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

RESTARTABLE A failed dump that can be restarted.

USAGE

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

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

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

Tipus
Either dump or NDMP.

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

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

Level
The level of the backup.

Path
Points to the tree that is being backed up.

An example of the backup status command output:

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

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

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

SEE ALSO

dump


Table of Contents



Manual Pages , , , ,

autosupport

July 7th, 2009

Taula de continguts

NAME

autosupport – notification daemon

SYNOPSIS

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

DESCRIPTION

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

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

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

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

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

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

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

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

The setup command tries to configure autosupport as follows:

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

Setup also queries for autosupport.from information.

OPTIONS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

CONTENTS

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

Generation date and timestamp

Versió del programari

System ID

Hostname

SNMP contact name (if specified)

SNMP location (if specified)

Partner System ID (if clustered)

Partner Hostname (if clustered)

Cluster Node Status (if clustered)

Console language type

sysconfig -a output

sysconfig -c output

sysconfig -d output

System Serial Number

Software Licenses (scrambled prior to transmission)

Option settings

availtime output

cf monitor all output (if clustered)

ic stats performance output (if clustered with VIA)

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

snet stats -v output (if clustered with SNET)

ifconfig -a output

ifstat -a output

vlan stat output

vif status output

nis info output

nfsstat -c output (if licensed)

cifs stat output (if licensed)

cifs sessions summary (if licensed)

cifs sessions output (if licensed and enabled)

cifs shares summary (if licensed)

cifs shares output (if licensed and enabled)

vol status -l (if cifs is licensed)

httpstat output

vfiler status -a output (if licensed)

df output

df -i output

snap sched output

vol status -v output

vol status output

vol status -c output

vol scrub status -v output

sysconfig -r output

fcstat fcal_stats output

fcstat device_map output

fcstat link_stats output

ECC Memory Scrubber Statistics

ems event status output

ems log status output

registry values

perf report -t output

storage show adapter -a output

storage show hub -a output

storage show disk -a output

storage show fabric output

storage show switch output

storage show port output

EMS log file (if enabled)

/etc/messages content

Parity Inconsistancy information

WAFL_check logs

TYPES

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

BATTERY_LOW!!!
LOG_ALERT

BMC_EVENT: BUS ERROR
LOG_ERR

BMC_EVENT: POST ERROR
LOG_ERR

CLUSTER DOWNREV BOOT FIRMWARE
LOG_CRIT

CLUSTER ERROR: DISK/SHELF COUNT MISMATCH LOG_EMERG

CLUSTER GIVEBACK COMPLETE
LOG_INFO

CLUSTER TAKEOVER COMPLETE AUTOMATIC
LOG_ALERT

CLUSTER TAKEOVER COMPLETE MANUAL
LOG_INFO

CLUSTER TAKEOVER FAILED
LOG_INFO

CONFIGURATION_ERROR!!!
LOG_ALERT

CPU FAN WARNING - [fan]
LOG_WARNING

DEVICE_QUALIFICATION_FAILED
LOG_CRIT

DISK CONFIGURATION ERROR
LOG_ALERT

DISK RECONSTRUCTION FAILED!!
LOG_ALERT

DISK_FAIL!!! - Bypassed by ESH
LOG_ALERT

DISK_FAIL!!!
LOG_ALERT

DISK_FAILURE_PREDICTED!!!
LOG_ALERT

DISK_FIRMWARE_NEEDED_UPDATE!!!
LOG_EMERG

DISK_IO_DEGRADED
LOG_WARNING

DISK_LOW_THRUPUT
LOG_NOTICE

DISK_RECOVERED_ERRORS
LOG_WARNING

DISK_SCRUB!!!
LOG_EMERG

FC-AL LINK_FAILURE!!!
LOG_ERR

FC-AL RECOVERABLE ERRORS
LOG_WARNING

OVER_TEMPERATURE_SHUTDOWN!!!
LOG_EMERG

OVER_TEMPERATURE_WARNING!!!
LOG_EMERG

PARTNER DOWN, TAKEOVER IMPOSSIBLE
LOG_ALERT

POSSIBLE BAD RAM
LOG_ERR

POSSIBLE UNLINKED INODE
LOG_ERR

REBOOT (CLUSTER TAKEOVER)
LOG_ALERT

REBOOT (after WAFL_check)
LOG_INFO

REBOOT (after entering firmware)
LOG_INFO

REBOOT (after giveback)
LOG_INFO

REBOOT (halt command)
LOG_INFO

REBOOT (internal halt)
LOG_INFO

REBOOT (internal reboot)
LOG_INFO

REBOOT (panic)
LOG_CRIT

REBOOT (power glitch)
LOG_INFO

REBOOT (power on)
LOG_INFO

REBOOT (reboot command)
LOG_INFO

REBOOT (watchdog reset)
LOG_CRIT

REBOOT
LOG_INFO

SHELF COOLING UNIT FAILED
LOG_EMERG

SHELF COOLING UNIT FAILED
LOG_WARNING

SHELF_FAULT!!!
LOG_ALERT

SNMP USER DEFINED TRAP
LOG_INFO

SPARE_FAIL!!!
LOG_ALERT

SYSTEM_CONFIGURATION_CRITICAL_ERROR
LOG_CRIT

SYSTEM_CONFIGURATION_ERROR
LOG_ERR

UNDER_TEMPERATURE_SHUTDOWN!!!
LOG_EMERG

UNDER_TEMPERATURE_WARNING!!!
LOG_EMERG

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

WAFL_check!!!
LOG_ALERT

WEEKLY_LOG
LOG_INFO

[EMS event]
LOG_INFO

[fan] FAN_FAIL!!!
LOG_ALERT

[mini core]
LOG_CRIT

[power supply failure]
LOG_ALERT

[power supply] POWER_SUPPLY_DEGRADED!!!
LOG_ALERT

[shelf over temperature critical]
LOG_EMERG

CLUSTER CONSIDERATIONS

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

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

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

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

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

SEE ALSO

options , partner , setup , hosts , RFC821


Table of Contents






























































Manual Pages , , , ,

auditlog

July 7th, 2009

Taula de continguts

NAME

auditlog – contains an audit record of recent administrative activity

SYNOPSIS

<logdir>/auditlog

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

DESCRIPTION

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

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

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

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

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

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

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

i

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

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

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

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

local7.*
@1.2.3.4

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

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

local7.*
/var/logs/filer_auditlogs

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

FILES

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

SEE ALSO

options , syslog.conf


Table of Contents

Manual Pages , , , ,



Aquest lloc no és afiliat o patrocinat en cap cas per NetApp o qualsevol altra empresa esmentada dins.

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

© 2009-2010 Chris Kranz Tots els drets reservats
Aquest lloc no és afiliat o patrocinat en cap cas per NetApp o qualsevol altra empresa esmentada dins.