NetApp已請給我許可再版的手冊頁。 他們還需要一點點整理，但數量龐大，意味著它會帶我一段時間，以獲得他們的所有排序和交叉引用正確，請原諒任何視覺問題的時刻。 我寫了一個快速的分析工具，讓所有的信息在這裡，所以有可能會產生的一些問題仍然。
我一直喜歡的方式是PHP有其功能頁面使用戶能夠直接到他們的評論。 這使得人們離開反饋功能和工具，並遵循一些額外的用途或不一定明確公佈的命令語法。 希望這能養活到NetApp的，以提高他們的文檔。
我一定要鼓勵人們評論任何可能有用的手冊頁，並希望建設成為一個有用的參考部分。 許多感謝NetApp幫助我的民歌。
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總額組成的RAID-0（無校驗）RAID組（V系列的NetCache只）。
RAID4總額組成的RAID 4 RAID組。
raid_dp
總額組成的RAID-DP（雙奇偶校驗）RAID組。
重建
正在重建中至少有一個RAID組的總。
重定向
已經開始對總總結再分配或-p選項的文件再分配。 閱讀量在總體性能可能會降低。
重新同步
鏡像總額的plex正在重新同步。
snapmirrored
聚合是另一個聚合snapmirrored副本。 如果聚合是一個傳統卷的一部分，這種狀態只能出現。
繁體總額融合與一個單一的量。 這也被稱為作為一個傳統的體積是完全等價的Data ONTAP 7.0之前存在的卷。 靈活的卷內不能創建此聚合。
驗證
RAID鏡像核查行動，目前正在上運行的總和。
WAFL不一致
總已被標記為損壞。 如果你看到一個聚集在此狀態下，請聯繫客戶支持。
添加鏡子限制undestroy複製脫機擦洗驗證創建在線show_space破壞分裂media_scrub重命名狀態的選項 如果不使用-g選項，磁盤被添加到最近創建的RAID組中的util是充分，然後創建一個或多個新的RAID組和剩餘磁盤被添加到新組。 任何其他現有的RAID組是不完整的部分仍然充滿。
-g選項允許指定一個RAID組（例如，rg0）應該被添加到指定的磁盤或磁盤被添加到新的或現有的RAID組的方法。
如果-g選項用於指定一個RAID組中，RAID組必須已經存在。 添加到磁盤，RAID組UTIL是充分。 任何剩餘的磁盤將被忽略。
如果使用-g選項是由新的Data ONTAP創建一個或多個新的RAID組，並增加了對他們的磁盤，磁盤，即使將融入現有的RAID組。 任何現有的RAID組是不完整的部分仍然充滿。 自動選擇的新RAID組的名稱。 這是不可能指定為新的RAID組的名稱。
如果-g選項， 所有的Data ONTAP指定的磁盤添加到現有的RAID組第一。 畢竟現有的RAID組都滿了，它會創建一個或多個新的RAID組，並增加了新組指定的磁盤。
-n選項，可以用來顯示，該系統將執行的命令，實際上不進行任何更改。 顯示自動選擇的磁盤，例如，這是有用的。
默認情況下，文件管理器填補了與磁盤一個RAID組開始之前另一個RAID組。 假設總目前有12個磁盤的RAID組的RAID組大小為14。 如果添加5磁盤此聚合，它將有一個有14個磁盤的RAID組和另3個磁盤的RAID組。 文件管理器並不均勻地分佈在RAID組中的磁盤。
你可以不添加磁盤鏡像總的plex。
在一個複雜的磁盤不允許跨越磁盤池。 這種行為可以用-f標誌覆蓋，用-D參數一起使用時，列出要添加的磁盤。 組合與-d，-f標誌，也可以被用於強制加入具有轉速不匹配的磁盤，大多數現有的磁盤總。
AGGR副本中止[-H] operation_number | 所有
終止聚合的複製操作。 opera_ţion_number參數指定的操作終止。 如果指定了所有 ，所有總活躍的複製操作被終止。
AGGR副本啟動
[ - S-S 快照 ] []
源目標
複製包括快照和靈活的卷的所有數據，從一個聚合到另一個。 如果使用-S標誌，命令複製源總目標總的所有快照。 指定一個特定的快照，複製，使用-s標誌快照的名稱。 如果你既不用在命令中，小號和-s標誌，文件管理器創建一個快照時的AGGR副本啟動命令執行時，只複製到目的地總的快照。
-C標誌是必需的，如果源總有自由空間碎片上進行，或者如果目標總額將是自由空間碎片整理。 自由空間碎片可以使用再分配命令總額。
總結的副本只能承載靈活的卷之間的聚合。 嵌入在傳統卷的集合體不能參加。
源和目標聚集在同一個文件管理器或不同的文件管理器。 如果源或目的地聚集在其中輸入的AGGR副本啟動命令比一的其他文件管理器，指定總額在filer_name的名稱：aggre_的Ğate_name格式，。
在一個聚合的副本涉及的申報者必須符合為的AGGR副本啟動命令成功完成下列要求：
源聚合必須是聯機的，必須限制和目標聚集。
如果複製兩個文件管理器是必須定義為可信主機的其他文件管理器，每個文件管理器。 也就是說，文件管理器的名字必須是在/ etc / hosts.equiv中的其他文件管理器的文件。
如果複印件上是相同的文件管理器中，localhost必須包含在文件管理器的/ etc / hosts.equiv文件。 此外，環回地址必須是在文件管理器的/ etc / hosts文件。 否則，文件管理器無法通過回送地址發送數據包本身時，試圖複製數據。
目標總的可用磁盤空間必須大於或等於源聚合的可用磁盤空間。 使用DF-一個 路徑命令看到特定總量的可用磁盤空間量。
每個AGGR副本啟動命令生成兩個總的複製操作：一個從源頭上聚合讀取數據和寫數據到目的地總之一。 每個文件管理器支持最多四個同步的複製操作總額。
AGGR副本的狀態 [operation_number]
顯示一個或所有AGGR複製操作的進度。 編號從0到3的操作。
所有過戶文件，重新啟動檢查點的信息也顯示出來。
AGGR副本油門 [operation_number]值
控制的AGGR複製操作的性能。 值的範圍從10（全速）1（全速的十分之一）。 在文件管理器的aggr.copy.throttle選項保持默認值，並在出廠時設置為10（全速）。 你可以申請性能價值由operation_number參數中指定的操作。 如果你不指定操作數在AGGR副本油門命令，該命令適用於所有AGGR複製操作。
如果你懷疑的AGGR複製操作造成文件管理器的性能問題，使用此命令限制的AGGR複製操作的速度。 油門，特別是旨在幫助限制的AGGR複製操作的CPU使用率。 它不能被用來微調的網絡帶寬消費模式。
不但可以讓你的AGGR副本油門命令設置速度一個AGGR複製操作正在進行中。 為了設置默認AGGR的複印速度，可用於未來的複製操作，使用的選項命令設置的aggr.copy.throttle選項。
AGGR創建 aggrname
[-F]
[ 米 ]
[-N]
[-T raidtype]
-R raidsize的 ]
[-T的 磁盤類型 ]
[-R的 RPM]
[-L的合規 | 企業 ]
[-V]
[-L 語言代碼 ]
{ndisks [ 大小 ]
創建一個嵌入式的聚合都可以作為一個傳統的音量使用-v選項的一部分。 它不能包含任何靈活的卷。
定期匯總，創建沒有-v選項，可以只包含靈活的卷。 它不能被納入傳統的體積，它包含創建後沒有立即卷。 使用 vol create命令可以創建新的靈活卷。
-T raidtype參數指定類型的RAID組（S）被用來創建聚合。 可能的RAID組類型RAID4 raid_dp的RAID-DP（雙奇偶校驗），RAID-4，簡單的條紋無奇偶校驗保護RAID0。 總量和傳統報稅卷的默認raidtype是raid_dp。 不允許設置raidtype V系列系統; RAID0默認總是使用。
-R raidsize參數指定聚集在每個RAID組中的磁盤的最大數目。 raidsize的最大默認值是依賴於平台的，基於性能和可靠性方面的考慮。 見AGGR選項的更多細節raidsize。
盤型的-T參數指定的磁盤類型，使用時，創建一個新的聚合。 它是只需要連接到不同類型的磁盤系統。 可能的磁盤類型：ATA，FCAL以及LUN的的SAS和SATA和SCSI。 在一個聚合不同類型的混合磁盤上是不允許的。T不能與-d一起使用。
磁盤類型標識磁盤技術和連接類型。ATA識別IDE或串行ATA接口連接FCAL（光纖通道仲裁環路）。FCAL標識在貨架上的FC-AL連接FC磁盤的LUN。貨架ATA磁盤標識出口從虛擬磁盤外部存儲陣列。 底層的磁盤技術和RAID類型取決於實施等外部存儲陣列SAS標識匹配的貨架上串行連接的SCSI磁盤，SATA標識串行ATA磁盤在SAS貨架。SCSI代表小型計算機系統接口，它是為了向後兼容與早期的磁盤技術。
-R的 轉速參數指定類型的磁盤使用，其轉速在每分鐘轉速（RPM）的基礎上。 它是只需要對系統具有不同轉速的磁盤。 轉速的典型值是5400，7200，10000和15000。-R的不能與-d一起使用。
ndisks是磁盤的總人數，包括奇偶校驗磁盤。 來自聚集在這個新創建的磁盤備用磁盤池中。 在這個池中的最小的磁盤總參加第一，除非你指定了@的大小參數。 大小是GB的磁盤大小，磁盤內指定大小的10％將在總使用選擇。
可以使用-m選項指定新的聚合是在創建鏡像（有兩個plex）。 如果有給這個選項，然後將指定的磁盤分割成兩個plex。 默認情況下，新的聚合不會鏡像。
-n選項，可以用來顯示，該系統將執行的命令，實際上不進行任何更改。 顯示自動選擇的磁盤，例如，這是有用的。
如果你使用了-d DISK1 DISK2 ... 文件管理器]參數，創建指定的備用磁盤DISK1，DISK2總，等等。 你可以指定一個磁盤名稱空間分隔的列表。 必須指定兩個不同的列表，如果新的總鏡像。 在新的聚合是鏡像的情況下，指定的磁盤必須在磁盤上每一個新的plex的數目相等。
在一個複雜的磁盤不允許跨越備用池。 這種行為可以使用-f選項覆蓋。 相同的選項也可以被用於強制使用的磁盤，不具有匹配的轉速。 只有當使用-d選項指定的磁盤使用-f選項具有效力。
要創建的SnapLock總的AGGR創建命令，指定-L標誌。 如果其中的SnapLock履約或授權的SnapLock企業，該標誌只支持。 的SnapLock創建聚合的類型，要么遵守或企業，確定安裝的SnapLock許可證。 如果雙方的SnapLock遵守和 SnapLock 企業許可， 遵守使用-L或-l企業指定所需的聚合類型。
-L LANGUAGE_CODE參數可用於僅使用-v選項時，創建一個傳統卷。 文件管理器創建的語言代碼指定的語言，傳統卷。 默認的是文件管理器的根量所使用的語言。 見的 VOL 語言代碼清單的手冊頁。
AGGR摧毀{aggrname | plexname} [-F]
Destroys the aggregate named aggrname , or the plex named plexname . Note that if the specified aggregate is tied to a traditional volume, then the traditional volume itself is destroyed as well.
If an aggregate is specified, all plexes in the aggregate are destroyed. The named aggregate must also not contain any flexible volumes, regardless of their mount state (online, restricted, or offline). If a plex is specified, the plex is destroyed, leaving an unmirrored aggregate or traditional volume containing the remaining plex. Before destroying the aggregate, traditional volume or plex, the user is prompted to confirm the operation. The -f flag can be used to destroy an aggregate, traditional volume or plex without prompting the user.
The disks originally in the destroyed object become spare disks. Only offline aggregates, traditional volumes and plexes can be destroyed.
aggr media_scrub status [ aggrname | plexname | groupname ]
[ -v ]
Prints the media scrubbing status of the named aggregate, plex, or group. If no name is given, then status is printed for all RAID groups currently running a media scrub. The status includes a percent-complete and whether it is suspended.
The -v flag displays the date and time at which the last full media scrub completed, the date and time at which the current instance of media scrubbing started, and the current status of the named aggregate, plex, or group. If no name is given, this more verbose status is printed for all RAID groups with active media scrubs.
aggr mirror aggrname
[ -f ]
[ -n ]
[ -v victim_aggrname ]
[ -d disk1 [ disk2 ... ] ]
Turns an unmirrored aggregate into a mirrored aggregate by adding a plex to it. The plex is either newly-formed from disks chosen from a spare pool, or, if the -v option is specified, is taken from another existing unmirrored aggregate. Aggregate aggrname must currently be unmirrored. Use aggr create to make a new, mirrored aggregate from scratch.
Disks may be specified explicitly using -d in the same way as with the aggr create and aggr add commands. The number of disks indicated must match the number present on the existing aggregate. The disks specified are not permitted to span disk pools. This behavior can be overridden with the -f option. The -f option, in combination with -d , can also be used to force using disks that have a rotational speed that does not match that of the majority of existing disks in the aggregate.
If disks are not specified explicitly, then disks are automatically selected to match those in the aggregate's existing plex.
The -v option can be used to join victim_aggrname back into aggrname to form a mirrored aggregate. The result is a mirrored aggregate named aggrname which is otherwise identical to aggrname before the operation. Victim_aggrname is effectively destroyed. Victim_aggrname must have been previously mirrored with aggrname , then separated via the aggr split command. Victim_aggrname must be offline. Combined with the -v option, the -f option can be used to join aggrname and vic_ t im_aggrname without prompting the user.
The -n option can be used to display the command that the system will execute without actually making any changes. This is useful for displaying the automatically selected disks, for example.
aggr offline { aggrname | plexname }
[ -t cifsdelaytime ]
Takes the aggregate named aggrname (or the plex named plexname ) offline. The command takes effect before returning. If the aggregate is already in restricted state, then it is already unavailable for data access, and much of the following description does not apply.
If the aggregate contains any flexible volumes, then the operation is aborted unless the filer is in maintenance mode.
Except in maintenance mode, the aggregate containing the current root volume may not be taken offline. An aggregate containing a volume that has been marked to become root (using vol options vol_ n ame root ) also cannot be taken offline.
If the aggregate is embedded in a traditional volume that has CIFS shares, users should be warned before taking the aggregate (and hence the entire traditional volume) offline. Use the -t switch for this. The cifsdelaytime argument specifies the number of minutes to delay before taking the embedded aggregate offline, during which time CIFS users of the traditional volume are warned of the pending loss of service. A time of 0 means take the aggregate offline immediately with no warnings given. CIFS users can lose data if they are not given a chance to terminate applications gracefully.
If a plexname is specified, the plex must be part of a mirrored aggregate and both plexes must be online. Prior to offlining a plex, the system will flush all internally-buffered data associated with the plex and create a snapshot that is written out to both plexes. The snapshot allows for efficient resynchronization when the plex is subsequently brought back online.
A number of operations being performed on the aggregate's traditional volume can prevent aggr offline from succeeding, for various lengths of time. If such operations are found, there will be a one-second wait for such operations to finish. If they do not, the command is aborted.
A check is also made for files in the aggregate's associated traditional volume opened by internal ONTAP processes. The command is aborted if any are found.
aggr online { aggrname | plexname }
[ -f ]
Brings the aggregate named aggrname (or the plex named plexname ) online. This command takes effect immediately. If the specified aggregate is embedded in a traditional volume, the volume is also also brought online.
If an aggrname is specified, it must be currently offline, restricted, or foreign. If the aggregate is foreign, it will be made native before being brought online. A “foreign” aggregate is an aggregate that consists of disks moved from another filer and that has never been brought online on the current filer. Aggregates that are not foreign are considered “native.”
If the aggregate is inconsistent, but has not lost data, the user will be cautioned and prompted before bringing the aggregate online. The -f flag can be used to override this behavior. It is advisable to run WAFL_check (or do a snapmirror initialize in case of an aggregate embedded in a traditional volume) prior to bringing an inconsistent aggregate online. Bringing an inconsistent aggregate online increases the risk of further file system corruption. If the aggregate is inconsistent and has experienced possible loss of data, it cannot be brought online unless WAFL_check (or snapmirror initialize in the embedded case) has been run on the aggregate.
If a plexname is specified, the plex must be part of an online mirrored aggregate. The system will initiate resynchronization of the plex as part of online processing.
aggr options aggrname [ optname optval ]
Displays the options that have been set for aggregate aggrname , or sets the option named optname of the aggregate named aggrname to the value optval . The command remains effective after the filer is rebooted, so there is no need to add aggr options commands to the /etc/rc file. Some options have values that are numbers. Some options have values that may be on (which can also be expressed as yes , true , or 1 ) or off (which can also be expressed as no , false , or 0 ). A mixture of uppercase and lowercase characters can be used when typing the value of an option. The aggr status command displays the options that are set per aggregate.
以下描述的選項和其可能的值：
fs_size_fixed上 | 關閉
此選項僅適用於嵌入在傳統卷的聚集。 它會導致文件系統，以保持相同的大小，並沒有增長或收縮時，SnapMirrored體積的關係被打破，或AGGR附加其上執行。 自動設置這個選項是對傳統卷時成為SnapMirrored量。 它將保持對傳統的音量發出後，SnapMirror的break命令。 這使得傳統的體積要回來，而無需將磁盤添加到源傳統的音量SnapMirrored源。 如果傳統的音量大小是大於文件系統的大小，關閉此選項將迫使增長到傳統的體積的大小的文件系統。 默認設置是關閉的。
ignore_inconsistent上 | 關閉
此命令只能用在維護模式。 如果設置了此選項，它允許被帶到總根量開機在線，即使它是不一致的。 用戶請注意：上網前先運行WAFL_check或wafliron可能導致進一步的文件系統不一致。
nosnap上 | 關閉
如果此選項，總禁用自動快照。 默認設置是關閉的。
raidsize 數量
這個選項的值是總可以在創建一個RAID組的最大大小。 更改這個選項的值，不會導致現有的RAID組，以擴大或收縮;它只會影響更多的磁盤是否將被添加到最後一個現有RAID組，如何將新的大型RAID組。
此選項的合法值取決於raidtype。 例如，raid_dp比RAID4允許更大的RAID組。 限制和默認值也有不同的文件管理器用具的不同類型和不同類型的磁盤。 下表定義為raidsize限制和默認值。
—————————————— raid4 raidsize min default max —————————————— R100 2 8 8 R150 2 6 6 FAS250 2 7 14 other (FCAL disks) 2 8 14 other (ATA disks) 2 7 7 —————————————— —————————————— raid_dp raidsize min default max —————————————— R100 3 12 12 R150 3 12 16 other (FCAL disks) 3 16 28 other (ATA disks) 3 14 16 ——————————————
raidtype raid4 | raid_dp | raid0
Sets the type of RAID used to protect against disk failures. Use of raid4 provides one parity disk per RAID group, while raid_dp provides two. Changing this option immediately changes the RAID type of all RAID groups within the aggregate. When upgrading RAID groups from raid4 to raid_dp , each RAID group begins a reconstruction onto a spare disk allocated for the second `dparity' parity disk.
Changing this option also changes raidsize to a more suitable value for new raidtype . When upgrading from raid4 to raid_dp , raidsize will be increased to the default value for raid_dp . When downgrading from raid_dp to raid4 , raidsize will be decreased to the size of the largest existing RAID group if it is between the default value and the limit for raid4 . If the largest RAID group is above the limit for raid4 , the new raidsize will be that limit. If the largest RAID group is below the default value for raid4 , the new raidsize will be that default value. If raidsize is already below the default value for raid4 , it will be reduced by 1.
resyncsnaptime number
This option is used to set the mirror resynchronization snapshot frequency (in minutes). The default value is 60 minutes.
root
If this option is set on a traditional volume, then the effect is identical as that defined in vol man page. Otherwise, if this option is set on an aggregate capable of containing flexible volumes, then that aggregate is marked as being the one that will also contains the root flexible volume on the next reboot. This option can be used on only one aggregate or traditional volume at any given time. The existing root aggregate or traditional volume will become a non-root entity after the reboot.
Until the system is rebooted, the original aggregate and/or traditional volume will continue to show root as one of its options, and the new root aggregate or traditional volume will show diskroot as an option. In general, the aggregate that has the diskroot option is the one that will contain the root flexible volume following the next reboot.
The only way to remove the root status of an aggregate or traditional volume is to set the root option on another aggregate or traditional volume.
snaplock_compliance
This read only option indicates that the aggregate is a SnapLock Compliance aggregate. Aggregates can only be designated SnapLock Compliance aggregates at creation time.
snaplock_enterprise
This read only option indicates that the aggregate is a SnapLock Enterprise aggregate. Aggregates can only be designated SnapLock Enterprise aggregates at creation time.
snapmirrored off
If SnapMirror is enabled for a traditional volume (SnapMirror is not supported for aggregates that contain flexible volumes), the filer automatically sets this option to on . Set this option to off if SnapMirror is no longer to be used to update the traditional volume mirror. After setting this option to off , the mirror becomes a regular writable traditional volume. This option can only be set to off ; only the filer can change the value of this option from off to on .
snapshot_autodelete on | off
This option is used to set whether snapshot are automatically deleted in the aggr. If set to on then snapshots may be deleted in the aggr to recover storage as necessary. If set to off then snapshots in the aggr are not automatically deleted to recover storage. Note that snapshots may still be deleted for other reasons, such as maintaining the snapshot schedule for the aggr, or deleting snapshots that are associated with specific operations that no longer need the snapshot. To allow snapshots to be deleted in a timely manner the number of aggr snapshots is limited when snapshot_autodelete is enabled. Because of this, if there are too many snapshots in an aggr then some snapshots must be deleted before the snapshot_autodelete option can be enabled.
aggr rename aggrname newname
Renames the aggregate named aggrname to newname . If this aggregate is embedded in a traditional volume, then that volume's name is also changed.
aggr restrict aggrname
[ -t cifsdelaytime ]
Put the aggregate named aggrname in restricted state, starting from either online or offline state. The command takes effect before returning.
If the aggregate contains any flexible volumes, the operation is aborted unless the filer is in maintenance mode.
如果總被嵌入在傳統的體積，有CIFS共享，用戶應警告限制的總和（因而整個傳統卷）。 使用-t開關。 cifsdelaytime參數指定分鐘之前延遲採取嵌入式總額脫機，在這期間的時間CIFS傳統卷的用戶服務有待損失的警告數量。 0意味著立即採取總額脫機沒有發出警告。 CIFS的用戶可能會失去數據，如果他們沒有機會來終止應用程序正常。
[aggrname plexname | groupname的 AGGR擦洗簡歷 ]
恢復命名的總和，複雜，或組校驗擦洗。 如果沒有指定名稱，恢復已經暫停目前正在進行平價擦洗所有的RAID組。
[aggrname plexname | groupname的 AGGR擦洗啟動 ]
開始命名的在線總平價擦洗。 平價擦洗比較數據磁盤的奇偶校驗磁盤的RAID組（S），必要時糾正奇偶校驗磁盤的內容。 如果沒有指定名稱，平價擦洗開始對所有在線的總量。 如果給出一個總名稱，洗滌開始在總量中包含的所有RAID組。 如果給出一個plex名稱，擦洗開始的plex中所有RAID組。
AGGR的磨砂膏狀態 [aggrname | plexname | 組名 ] [-V]
打印平價擦洗命名的總和，複雜的，或組中的地位，目前所有的RAID組進行校驗擦洗，如果沒有給定名稱。 狀態包括％完整的，磨砂的懸浮狀態。
-v標誌顯示的日期和時間命名的總和，複雜的，或組的當前狀態完成最後的全磨砂;如果沒有名字，所有的RAID組。
[aggrname plexname | groupname的 AGGR擦洗站 ]
停止平價擦洗命名的總和，複雜的，或組，如果沒有給定的名稱，在所有的RAID組，目前正處於平價擦洗。
AGGR擦洗暫停 aggrname | plexname | 組名 ]
暫停平價擦洗命名的總和，複雜的，或組，如果沒有名字，在所有的RAID組，目前正處於平價洗滌。
AGGR show_space [-H |-K-M |-G-T |-B] <aggrname>
顯示在聚合空間使用。 不像DF，此命令顯示每個空間內聚集的靈活卷使用如果aggrname指定，AGGR show_space只有在相應的總運行，否則報告上所有的聚合空間使用情況。
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.
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.
-r標誌顯示，總的RAID信息的列表。 如果沒有指定aggrname，打印對所有的集合體，有關文件系統的磁盤的信息，備用磁盤，發生故障的磁盤的RAID信息。 欲了解更多有關故障的磁盤的信息，請參閱-f開關下面的說明。
-d標誌顯示在指定的總磁盤信息。 磁盤信息的類型是為那些從sysconfig中-d命令相同。
-c標誌顯示塊的校驗數據的完整性保護功能的升級狀態。
-b是用來獲得使用AGGR副本的源和目標聚集的大小。 輸出包含存儲在總量和規模較小的總額可能。 總的複製命令使用這些數字，以確定是否源和目的地的總大小是兼容的。 源總的大小必須等於或小於目標總的大小。
-s標誌顯示備用磁盤上的文件管理器的列表。
-f標誌顯示發生故障的磁盤上的文件管理器的列表。 該命令的輸出包括磁盤故障的原因，它可以是下列任何一項：
-i標誌顯示在聚合中的靈活卷的列表。
未知故障原因不明。 失敗的Data ONTAP出現故障的磁盤，由於一個致命的磁盤錯誤。 此磁盤管理失敗的用戶發出一個磁盤失敗'的命令。 沒有標記的破盤下的Data ONTAP 6.1.X或更早版本。 初始化失敗磁盤初始化序列失敗。 此磁盤管理刪除用戶發出“磁盤刪除”命令。 不響應不響應請求的磁盤。 拉磁盤身體拉，或沒有訪問磁盤上的數據路徑存在。 繞過磁盤的ESH繞過。
undestroy部分完整或以前銷毀的聚合或傳統卷。 該命令打印匹配給定的名稱，它可以潛在的未銷毀的候選人聚集和傳統卷的列表。
-n選項，打印清單由聚合或包含由傳統的體積，它可以潛在的未銷毀的磁盤。 這個選項可以用來顯示命令執行的結果，實際上不作任何修改。
AGGR驗證簡歷 [aggrname]
恢復RAID名為聚合鏡核查;如果沒有總的名稱，目前正在進行RAID鏡像核查，已暫停所有聚集。
AGGR驗證啟動 [aggrname] [-F plexnumber]
開始在網上鏡像總RAID鏡像核查。 如果沒有給定的名字，然後開始對所有在線的鏡像集合體RAID鏡像驗證。 驗證比較兩個plex的鏡像聚合數據。 在默認情況下，所有不同的塊記錄，但不進行任何更改。 如果給出了-f標誌，指定的plex是固定的，被發現不匹配時，以配合其他的plex。 -F plexnumber選項必須指定一個名稱。
AGGR驗證停止 [aggrname]
停止對命名的總RAID鏡像核查;如果沒有總的名稱，目前正在對所有總量RAID鏡像核查。
AGGR驗證地位 [aggrname]
打印命名總的鏡像的RAID核查的狀態;目前正在進行RAID鏡像驗證所有聚集，如果沒有總的名稱。 狀態包括％完成，核查暫停狀態。
AGGR驗證暫停 [aggrname]
暫停RAID名為聚合鏡核查;如果沒有總的名稱，目前正在進行RAID鏡像驗證所有聚集。
然而，在集群中具有獨特的總名稱，可以更容易地遷移集群中的文件管理器之間的聚合。
創建命名的20個磁盤aggr1的總和。 在這個總的RAID組中最多可包含10個磁盤，所以這個新的聚合有兩個RAID組。 文件管理器將當前的備用磁盤，以新的聚合，最小磁盤的開始。
AGGR創建aggr1的20 @ 9
創建名為20 9 GB的磁盤aggr1的總和。 RAID組的大小，因為沒有指定，默認大小（8個磁盤）。 新創建的聚合包含兩個8盤和第三組四個磁盤的RAID組。
AGGR創建aggr1的-D 8A.1 8A.2 8a.3
創建名為指定的三個磁盤aggr1的總和。
AGGR創建aggr1的10
AGGR選項aggr1的raidsize 5
第一個命令創建名為aggr1的 10個磁盤屬於一個RAID組的聚合。 第二個命令規定，如果任何磁盤添加到這個總隨後，他們將不會導致任何當前的RAID組，有五年以上的磁盤。 每個現有的RAID組將繼續有10個磁盤，並沒有更多的磁盤，RAID組將被添加到。 當創建新的RAID組，他們將有5個磁盤的最大尺寸。
AGGR show_spaceĤAG1
顯示總AG1和規模的大小的空間單位的空間使用率。
總結“AG1”總面積的WAFL儲備捕捉儲備可用空間的BSR NVLOG 66GB 6797MB 611MB 59GB 65KB的空間分配給總卷的卷分配用於保證VOL1 VOL2 8861MB 14GB 11GB體積8871MB文件VOL3 VOL4沒有26GB 25GB體積vol1_clone 1028MB 1028MB 6161MB 6169MB（脫機）總結分配用可用總空間55GB 51GB 3494MB捕捉儲備611MB 21MB 590MB的WAFL儲備6797MB 5480KB 6792MB AGGR狀態aggr1的-R
顯示關於總aggr1的 RAID信息。 在下面的例子中，我們看到aggr1的是一個RAID-DP粒料塊校驗保護。 它是在線的，所有的磁盤都正常運作。 總包含四個磁盤，兩個數據的磁盤，一個奇偶磁盤，磁盤和一個doubleparity。 0B適配器，適配器1B兩個位於兩個磁盤。 每個磁盤的磁盤架和托架編號表示。 所有四個磁盤是10，000 RPM光纖通道連接的磁盤通過磁盤通道A中的磁盤的“池”屬性顯示SyncMirror可只有被許可，這是不是這裡的情況（SyncMirror可如果被授權，游泳池將是0或1） 。 最右邊的列中顯示的磁盤空間的使用量的Data ONTAP（“二手”）和磁盤上的可用（“物理學報”）。
AGGR aggr1的（在線，raid_dp）（塊校驗）Plex的/ aggr1/plex0（在線，正常，活躍）RAID組/ aggr1/plex0/rg0（正常）RAID磁盤設備醫管局架灣陳池型轉用（MB /次蓋帽）物理學（MB /蓋帽）----------------------------一個 - FCAL dparity 0b.16 0B 1 0 FC：10000 136000 /二億七千八百五十二萬八千一十三萬七千一百○四/二億八千〇七十九萬〇一百八十四平價1b.96 1B 6 0 FC FCAL A - 10000 136000 /二億七千八百五十二萬八千一十三萬九千〇七十二/二億八千四百八十二萬零八百數據0b.17 0B 1 1的FC：一個 - FCAL 10000 136000 /二億七千八百五十二萬八千一三九零七二/二八四八二零八零零數據1b.97 1B 6 1 FC： - FCAL 10000 136000 / 27852.8萬一三九〇七二/ 28482.08萬 cf nfo [ enable | disable ] disk_shelf
cf nfo status
The cf command is available only if your filer has the cluster license.
partner giveback incomplete, some data may be lost
forcetakeover [-F] forcetakeover是危險，並可能導致數據損壞，在幾乎所有情況下， 比照收購，而不是使用。
強制一個文件管理器來接管其合作夥伴，即使在文件管理器檢測到一個錯誤，否則將阻止收購。 例如，通常，如果一個分離或出現故障的ServerNet的文件管理器之間的電纜，導致不同步的文件管理器的NVRAM的內容，接管被禁用。 不過，如果你輸入的CF forcetakeover命令，文件管理器需要在其合作夥伴，儘管不同步的NVRAM的內容。 該命令可能會導致文件管理器被接管失去客戶數據。 如果您使用-f選項， 比照命令允許這種forcetakeover的進行，而無需操作確認。
forcetakeover-D [F]強制文件管理器接管其合作夥伴在所有情況下，在forcetakeover會失敗。 此外，這將迫使收購一些合作夥伴的郵箱磁盤，即使是人跡罕至。 它只能用於授權cluster_remote時。
forcetakeover-D是非常危險的。 它不僅可以導致數據損壞，如果不小心使用，它也可以導致文件管理器和它的合作夥伴是業務（裂腦）的情況。 正因為如此，它應該只用於作為最後手段時收購和forcetakeover命令在成功實現收購。 操作人員必須確保合作夥伴的文件管理器，並不能成為隨時操作，而文件管理器，在使用此命令發起收購模式是。 在RAID鏡像的結合，它可以允許從災難中恢復過來時，集群中的兩個文件管理器，在兩個遙遠的地方位於。 使用-f選項允許這個命令來進行，而無需操作確認。
如果你使用-n選項， 比照命令允許進行收購，即使夥伴節點運行的Data ONTAP版本不兼容。 乾淨的合作夥伴節點必須停止在此選項成功。 這是用來作為一個不間斷的升級過程中的一部分。
NFO [啟用 | 禁用] disk_shelf
啟用或禁用磁盤架數不匹配的談判故障轉移。
此命令是過時的。 選項cf.takeover.on_disk_shelf_miscompare取代它。
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).
bootfs core [ -v ] disk
bootfs dir [ -r ] path
BOOTFS轉儲， 磁盤驅動器 } { 部門集群 }
BOOTFS FDISK 磁盤partition1sizeMB partition2sizeMB] [partition3sizeMB] [partition4sizeMB]
BOOTFS格式的 驅動器 [ 標籤 ]
BOOTFS信息 盤
BOOTFS同步 [-F] { 磁盤 | 驅動 }
BOOTFS測試 [-V] 磁盤
使用BOOTFS命令，可以執行四個重要的功能。 您可以通過CHKDSK命令檢查引導設備的完整性。 通過目錄 ， 轉儲 ， 信息子，你可以查看你的引導設備的內容。 你可能會改變通過FDISK命令的引導設備上的分區大小及格式類型。 您可以通過format命令的引導設備上格式化分區。 您可以同步所有內存中的內容，通過同步子物理介質。 最後，您可以通過測試命令的引導設備健康診斷。
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.] 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
bootfs test -v 0a.0
版權所有©1994-2008 NetApp的公司法律信息
bmc reboot
bmc setup
bmc status
bmc test autosupport
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
版權所有©1994-2008 NetApp的公司法律信息
The following are the events filer monitors:
Start_logging Logging begins.
TYPE TIME_STAMP IDENTIFIER EVENT (EVENT_INFO)
dmp Thu Apr 5 18:54:56 PDT 2001 /vol/vol0/ home(5) Start (level 0, NDMP)
In the particular example:
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.)
backup terminate <ID>
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:
ID State Type Device Start Date Level Path — ———– —- —— ———— —– ————— 0 ACTIVE NDMP urst0a Nov 28 00:22 0 /vol/vol0/ 1 RESTARTABLE dump Nov 29 00:22 1 /vol/vol1/
backup terminate <ID>
A RESTARTABLE dump, though not actively running, retains a snapshot and other file system resources. To release the resources, user can explicitly terminate a RESTARTABLE dump. Once terminated, it cannot be restarted again.
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.
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.
Generation date and timestamp
Software Version
System ID
Hostname
SNMP contact name (if specified)
SNMP location (if specified)
Partner System ID (if clustered)
Partner Hostname (if clustered)
Cluster Node Status (if clustered)
Console language type
sysconfig -a output
sysconfig -c output
sysconfig -d output
System Serial Number
Software Licenses (scrambled prior to transmission)
Option settings
availtime output
cf monitor all output (if clustered)
ic stats performance output (if clustered with VIA)
ic stats error -v output (if clustered with VIA)
snet stats -v output (if clustered with SNET)
ifconfig -a output
ifstat -a output
vlan stat output
vif status output
nis info output
nfsstat -c output (if licensed)
cifs stat output (if licensed)
cifs sessions summary (if licensed)
cifs sessions output (if licensed and enabled)
cifs shares summary (if licensed)
cifs shares output (if licensed and enabled)
vol status -l (if cifs is licensed)
httpstat output
vfiler status -a output (if licensed)
df output
df -i output
snap sched output
vol status -v output
vol status output
vol status -c output
vol scrub status -v output
sysconfig -r output
fcstat fcal_stats output
fcstat device_map output
fcstat link_stats output
ECC Memory Scrubber Statistics
ems event status output
ems log status output
registry values
perf report -t output
storage show adapter -a output
storage show hub -a output
storage show disk -a output
storage show fabric output
storage show switch output
storage show port output
EMS log file (if enabled)
/etc/messages content
Parity Inconsistancy information
WAFL_check logs
BATTERY_LOW!!!
LOG_ALERT
BMC_EVENT: BUS ERROR
LOG_ERR
BMC_EVENT: POST ERROR
LOG_ERR
CPU FAN WARNING - [fan]
LOG_WARNING
DISK_FAIL!!! - Bypassed by ESH
LOG_ALERT
DISK_FAIL!!!
LOG_ALERT
DISK_FAILURE_PREDICTED!!!
LOG_ALERT
DISK_FIRMWARE_NEEDED_UPDATE!!!
LOG_EMERG
FC-AL LINK_FAILURE!!!
LOG_ERR
OVER_TEMPERATURE_WARNING!!!
LOG_EMERG
PARTNER DOWN, TAKEOVER IMPOSSIBLE
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
UNDER_TEMPERATURE_WARNING!!!
LOG_EMERG
USER_TRIGGERED ([user input from autosupport.doit]) LOG_INFO
WAFL_check!!!
LOG_ALERT
[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
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.
<logdir> is /etc/log for filers and /logs for NetCache appliances.
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
和
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:
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:
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
Bad Behavior has blocked 1678 access attempts in the last 7 days.
©2009-2012 克里斯·克蘭茲保留所有權利
This site is not affiliated or sponsored in anyway by NetApp or any other company mentioned within.