NetApp have kindly given me permission to republish their man pages here. They still need a little tidying up, but the sheer quantity means it'll take me awhile to get them all sorted and cross-referenced properly, please excuse any visual issues for the moment. I wrote a quick parsing tool to get all the info on here, so there may be a few issues resulting from that still.

I've always liked the way that PHP have their function pages giving users the ability to comment directly onto them. This allows people to leave feedback on functions and tools, and also follow up with some extra uses or syntax for commands that aren't necessarily clearly published. Hopefully this can feed back into NetApp to improve their documentation.

I'd definitely like to encourage people to comment on the man pages with anything that may be useful, and hopefully build this into a useful little reference section. Many thanks again for the NetApp folk for helping me with this.

目錄表

名稱

內容簡介

說明

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.

增長
磁盤被添加到聚合的過程中。

初始化
聚合是在被初始化的過程中。

無效的
總額不包含卷，並沒有可以加入。 通常情況下，發生這種情況後，才中止的總複製操作。

熨衣服
一個正在執行此聚合WAFL一致性檢查。

鏡退化
骨料是一個鏡像的總和，其叢之一是脫機或RESYNCING。

鏡像
總額鏡像卷和RAID組所有的功能。

需要檢查
一個 WAFL一致性檢查需要對總執行。

部分
總額至少一個磁盤被發現，但兩個或更多磁盤丟失。

RAID0總額組成的RAID - 0（無校驗）RAID組（V系列的NetCache只）。

RAID4的總和，包括RAID 4 RAID組。

raid_dp
總額組成的RAID - DP（雙奇偶校驗）RAID組。

重建
至少有一個 RAID組，在總量上正在重建。

重定向
已經開始對總總結的重新分配或- p選項的文件重新分配。 讀取性能，從而在總量上卷可能會降低。

RESYNCING
鏡像總的plex正在重新同步。

snapmirrored
總額的另一個總 snapmirrored副本。 如果聚合是傳統卷的一部分，這種狀態只能出現。

TRAD聚集融合與單個卷。 這也被稱為作為一個傳統的量是完全等同於之前的Data ONTAP 7.0中存在的卷。 靈活的卷不能創建在此聚集。

驗證
RAID鏡像的核查行動，目前正在對總運行。

WAFL不一致
總量已被標記為已損壞。 如果你看到一個總在這種狀態下，請聯繫客戶支持。

用法

 加鏡面限制undestroy複製脫機擦洗驗證創建在線 show_space摧毀分裂media_scrub重命名狀態的選項 

|

- D DISK1 [DISK2 ... ] [- D diskn [diskn 1 ... ]]}

如果不使用- 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組的大小是14的RAID組。 如果添加5磁盤此聚合，將有14個磁盤的RAID組和另3個磁盤的RAID組。 文件管理器沒有均勻地分佈在RAID組中的磁盤。

你可以不添加磁盤鏡像總的plex之一是離線的。

在複雜的磁盤不允許跨越磁盤池。 這種行為可以與- f標誌覆蓋- D參數一起使用時，列出要添加的磁盤。 的結合- D - F標誌，也可以用來強制添加磁盤，具有轉速不匹配，大多數現有磁盤總。

[- H] operation_number | 所有AGGR複製中止

終止聚合的複製操作。 該opera_噸ion_number參數指定的操作終止。 如果你指定所有 ，所有總活躍的複製操作被終止。

AGGR複製啟動
[ - S | - S 快照 ] [- C]
源目標

複製的所有數據，包括快照和靈活卷，從一個聚合到另一個。 如果使用了- 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]
[- M]
[- N]
[- T raidtype]
[ř raidsize]
[- T的 磁盤類型 ]
[- R的 RPM]
[ - L [ 合規 | 企業 ]
[- V]
[- L 語言代碼 ]
{ndisks [ 大小 ]

|

- D DISK1 [DISK2 ... ] [- D diskn [diskn 1 ... ]]}

創建一個嵌入式的骨料可作為傳統使用- v選項的音量的一部分。 它不能包含任何靈活的卷。

一個定期匯總，創建沒有- v選項，只能包含靈活的卷。 它不能被納入傳統卷，它包含創建後沒有立即卷。 使用卷創建命令可以創建新的靈活卷。

- T raidtype參數指定類型的RAID組中（S）被用來創建聚合。 可能的RAID組類型RAID4 raid_dp的RAID - DP（雙奇偶校驗），RAID - 4，和RAID0簡單的條帶無奇偶校驗保護。 總量和傳統卷上的文件管理器的默認 raidtype raid_dp 。 V系列系統上不允許設置raidtype;總是使用默認的RAID0。

- R raidsize參數指定總在每個RAID組磁盤的最大數目。 raidsize的最大值和默認值依賴於平台的，基於性能和可靠性方面的考慮。 有關詳細信息，請參閱AGGR選項 raidsize 。

- T的 磁盤類型參數指定創建一個新的聚合時使用的磁盤類型。 它是只需要連接到不同類型的磁盤系統。 可能的磁盤類型：ATA，FCAL以及LUN的SAS，SATA和SCSI。 在一個聚合的不同類型的混合磁盤是不允許的。- T不能與 - d一起使用。

磁盤類型標識磁盤技術和連接類型。ATA識別IDE或串行ATA接口在FCAL（光纖通道仲裁環路）。FCAL連接貨架，ATA磁盤標識在貨架中的FC - AL連接FC 磁盤LUN的標識出口從虛擬磁盤外部存儲陣列。 底層的磁盤技術和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的數目相等。

一個 plex的磁盤不允許跨越備用池。 這種行為可以使用- f選項覆蓋。 同樣的選擇，也可以用來強制使用的磁盤，沒有匹配的轉速。 - f選項只有當使用- ð指定的磁盤使用“選項的效果。

要創建的SnapLock總AGGR創建命令，指定- L標誌。 這個標誌只支持如果任的SnapLock遵守或企業的SnapLock的許可。 類型的SnapLock創建的總和，無論是遵守或企業，是由安裝的SnapLock許可證。 如果雙方的SnapLock遵守和 SnapLock 企業的許可， 符合使用- L或- l企業 ，指定所需的總類型。

- L LANGUAGE_CODE論點可用於只有當創建一個傳統的卷使用- v選項。 文件管理器創建的傳統語言代碼所指定的語言量。 默認情況下是由文件管理器的根卷使用的語言。 見的 VOL 手冊頁的語言代碼清單。

AGGR破壞 aggrname | plexname} [- F]

銷毀總名為aggrname，或複雜的命名 plexname的。 請注意，如果指定的聚合與傳統卷，那麼傳統的體積本身以及銷毀。

如果一個總的規定，在總所有plex被銷毀。 命名總還必須不包含任何靈活的卷，不論其mount狀態（在線，限制，或離線）。 如果指定了一個 plex plex的破壞，留下一個未鏡像包含其餘複雜的聚合或傳統卷。 在銷毀總體來說，傳統卷或plex之前，將提示用戶確認操作。 可以使用- f標誌，不提示用戶的情況下聚合，傳統卷或plex的破壞。

最初的磁盤成為備用磁盤在被摧毀的對象。 離線聚集，傳統卷和plex可以被摧毀。

AGGR media_scrub狀態 aggrname | plexname | 組名 ]
[- V]

打印命名的總和，複雜，或組的媒體洗刷狀態。 如果沒有名字，然後狀態是所有RAID組當前正在運行的媒體擦洗打印。 狀態包括一個完成百分比和是否暫停。

- v標誌顯示在去年的全媒體擦洗完成的日期和時間，當前實例的媒體洗刷開始的日期和時間，並命名的聚合，複雜的，或組的當前狀態。 如果沒有名字，這更詳細的狀態印刷與磨砂積極媒體 RAID組。

AGGR鏡 aggrname
[- F]
[- N]
[- V victim_aggrname]
[- D DISK1 [DISK2 ... ]]

加入一個 plex變成鏡像總未鏡像的聚合。 該plex是新成立的，從選擇一個備用池，或者，如果指定了- v選項，是從另一個現有的未鏡像總的磁盤。 總結aggrname目前必須鏡像。 使用AGGR創建從頭開始一個新的，鏡像總。

磁盤可以明確指定使用- D AGGR創建和AGGR添加命令相同的方式。 表示磁盤的數目必須與現有的總量上存在的數量。 指定的磁盤不允許跨越磁盤池。 可以使用- f選項覆蓋此行為。 - f選項結合- D，也可以用來強制使用有轉速不匹配大多數現有磁盤總的磁盤。

如果沒有明確指定磁盤，然後磁盤自動選擇匹配聚集的現有的plex。

可以使用- v選項加入到aggrname victim_aggrname形成一個鏡像聚合。 其結果是鏡像總名為aggrname否則相同aggrname之前的操作。Victim_aggrname有效地摧毀。Victim_aggrname以前必須有被鏡像aggrname，然後通過AGGR split命令分開。Victim_aggrname必須離線。 - V選項，可以使用- f選項不提示用戶的情況下加入 aggrname 和 vic_噸im_aggrname。

可以使用- n選項，以顯示該系統將實際作出任何改變的情況下執行的命令。 顯示自動選擇的磁盤，例如，這是有用的。

AGGR離線 {aggrname | plexname}
[- T cifsdelaytime]

時間總命名aggrname（或名為plexname的plex）脫機。 該命令返回之前的效果。 如果總已經在限制狀態，那麼它已經是不可用於數據訪問，下面的說明不適用。

如果聚合包含任何靈活的卷，然後將中止操作，除非文件管理器處於維護模式。

除了在維護模式下，總包含當前的根卷可能不會採取脫機。 包含已標記成為root（使用卷選項 vol_ ñ AME 根 ）的卷的總也不能脫機。

如果總是嵌入在傳統卷，CIFS共享，用戶應警告的總和（因而整個傳統卷）脫機之前。 使用了- t此開關。 cifsdelaytime參數指定的分鐘數，延遲到嵌入式總脫機之前，在此期間，CIFS的傳統卷的用戶服務有待損失的警告。 0意味著時間立即採取總脫機沒有給予警告。 CIFS用戶可以失去的，如果他們沒有機會來終止應用擺好的數據。

如果plexname指定的plex必須鏡像聚合的一部分，叢都必須在線。 一個 plex脫機之前，系統將刷新所有內部緩衝的plex關聯的數據，並創建一個快照被寫入到兩個叢。 快照允許高效的plex再同步時，隨後被帶回在線。

一些聚集的傳統卷上執行的操作，可以防止AGGR脫機成功，不同的時間長度，。 如果發現這樣的操作，將會有一個這樣的操作一秒鐘的等待完成。 如果他們不這樣做，命令中止。

也聚集的相關傳統內部 ONTAP的進程打開的卷中的文件進行檢查。 如果發現任何命令中止。

AGGR在線 {aggrname | plexname}
[- F]

帶總命名aggrname（或名為plexname的plex）在線。 此命令立即生效。 如果指定的總嵌入在傳統卷，體積也還帶來了網上。

如果指定的aggrname是，它必須是目前處於離線狀態，限制或外國。 如果聚合是外國的，它將會原生之前聯機。 “洋”總是從另一個文件管理器和移動從未有過帶來了對當前文件管理器的在線的磁盤組成的聚合。 是不是外國的聚集被認為是“本土”。

如果聚合是不一致的，但沒有數據丟失，用戶將被警告，才使總在線提示。 可以使用- f標誌來覆蓋此行為。 這是可取運行WAFL_check（或嵌入在傳統卷的總的情況下做一個SnapMirror的初始化）之前將不一致的總在線。 帶來的總在線不一致，增加了進一步的文件系統損壞的風險。 如果聚合是不一致的，經歷了可能的數據丟失，無法聯機，除非WAFL_check（或在嵌入式案件的SnapMirror初始化 ）總運行。

如果指定了一個 plexname，plex必須是一個網上的鏡像聚合的一部分。 該系統將啟動在線處理的一部分的plex重新同步。

AGGR選項 aggrname [optname optval]

顯示總aggrname已設置的選項，或者設置選項命名的總命名aggrname optname 價值 optval 。 該命令仍然有效的文件管理器重新啟動後，所以沒有必要添加AGGR選項命令在/ etc / rc文件。 有些選項是數字的值。 有些選項的值可能（也可表達為是 ， 真實 ，或1）或關閉 （也可以沒有 ， 虛假 ，或0表示）。 鍵入一個選項的值時，可以使用大寫和小寫字符的混合。 AGGR status命令顯示每總設置的選項。

以下描述的選項和它們的可能值：

fs_size_fixed上 | 關閉

此選項僅適用於嵌入在傳統卷的聚合。 它會導致文件系統，以保持相同的大小，而不是增長或收縮時SnapMirrored體積的關係被打破，或 AGGR添加就可以執行。 此選項會自動設置為在傳統卷時成為SnapMirrored量。 它的SnapMirror打破傳統的卷發出命令後仍將。 這使得傳統卷SnapMirrored回源，而無需將磁盤添加到源傳統卷。 如果傳統的音量大小是大於文件系統的大小，關閉此選項將迫使增長到傳統的體積的大小的文件系統。 默認設置是關閉的。

ignore_inconsistent上 | 關閉

此命令只能用在維護模式。 如果設置了這個選項，它允許總根量將提請啟動網上，即使它是不一致的。 提醒用戶的是，把它上網前先運行 WAFL_check或wafliron可能導致進一步的文件系統不一致。

nosnap上 | 關閉

如果此選項，禁用對總的自動快照。 默認設置是關閉的。

raidsize 數量

此選項的值是在總量上可以創建一個 RAID組的最大大小。 更改這個選項的值不會造成現有的RAID群體增長或收縮;它只會影響，是否有更多的磁盤將被添加到最後一個現有 RAID組和新的大型RAID組將。

此選項的法律價值取決於 raidtype 。 例如，raid_dp比RAID4允許更大的RAID組。 限制和默認值也有不同的文件管理器設備的不同類型和不同類型的磁盤。 下表定義為raidsize限制和默認值。

  -------------- RAID4 raidsize分鐘默認的最大-------------- R100 2 8 8 R150 2 6 6 FAS250 2 7 14其他（FCAL磁盤） 2 8月14日其他（ATA磁盤）2 7 7 -------------- -------------- raid_dp raidsize分鐘默認最大------ -------- R100 3 12 12 R150 3 12 16其他（FCAL磁盤）3 16 28其他（ATA磁盤）3 13 14 15 16 ---------- ---- 

raidtype RAID4 | raid_dp | RAID0

設置用來防止磁盤故障的RAID類型。 使用RAID4提供每一個RAID組的奇偶校驗磁盤， 而 raid_dp提供了兩個。 更改此選項，立即改變了所有RAID組內總的RAID類型。 當升級RAID組從RAID4 raid_dp，每個RAID組開始到第二個`dparity“奇偶校驗磁盤分配一個備用磁盤重建。

更改此選項，也改變 raidsize到一個新 raidtype的更合適的值。 當升級從RAID4 raid_dp，raidsize raid_dp默認值將增加。 降級從raid_dp RAID4，raidsize將減少到現有的RAID組中的最大的大小，如果它之間的默認值和RAID4的限制。 如果以上RAID4的限制是最大的RAID組，新raidsize將這一限額。 如果低於RAID4的默認值是最大的RAID組，新raidsize將默認值。 如果raidsize已經低於RAID4的默認值，它會減少1 。

resyncsnaptime 數量

此選項用於設置鏡像重新同步快照的頻率（以分鐘為單位）。 默認值是60分鐘。

根

如果是傳統卷上設置此選項，那麼效果是相同的定義，在第 手冊頁。 否則，如果這個選項是能夠包含靈活的卷聚合的聚合，然後被標記為一個，也將包含根在下次重新啟動的靈活卷。 此選項可用於只有一個聚合或傳統的體積在任何給定的的時間。 現有根的總量或傳統卷將成為一個非根實體，在重新啟動後。

直到系統重新啟動後，原來的聚合和/或傳統卷將繼續顯示其選項之一根，新的根聚合或傳統卷將顯示為一個選項diskroot。 在一般情況下，總有diskroot選項是一個將包含在下次重新啟動後的根靈活的批量。

只有這樣，才能去除聚合或傳統卷的根狀態是另一個聚合或傳統卷的根選項設置。

snaplock_compliance

這閱讀的唯一選擇表明，聚合是的SnapLock遵守聚合。 聚合只能在創建時指定的SnapLock遵守聚合。

snaplock_enterprise

這閱讀的唯一選擇，總是的SnapLock企業總。 聚合只能在創建時指定的SnapLock企業聚合。

snapmirrored關閉

如果啟用的SnapMirror是傳統卷（SnapMirror的是不支持聚合包含靈活的卷），文件管理器會自動設置這個選項上。 將此選項設置為關閉 ，如果SnapMirror的不再是被用來更新傳統的卷鏡像。 設置此選項關閉後，鏡子成為一個常規的可寫的傳統卷。 這個選項只能被設置為關閉 ，只有文件管理器可以從這個選項的值就 。

snapshot_autodelete上 | 關閉

此選項用於設置是否快照在AGGR自動刪除。 如果設置為 on，則快照可能會被刪除，在AGGR必要的恢復存儲。 如果設置為 off，然後AGGR的快照不會自動刪除，以恢復存儲。 請注意，仍可能為其他原因，如維持 AGGR快照排程，或刪除相關的具體操作，不再需要快照的快照，刪除快照。 為了讓 AGGR快照的數量是有限的啟用 snapshot_autodelete時及時刪除快照。 正因為如此，如果有一個 AGGR太多的快照，然後一些快照，必須刪除之前snapshot_autodelete選項可啟用。

AGGR命名 aggrname NEWNAME

重命名的總命名aggrname NEWNAME。 如果此聚合是在傳統卷中，則該卷的名稱也發生了變化。

AGGR限制 aggrname
[- T cifsdelaytime]

限制狀態的總命名aggrname，從聯機或脫機狀態開始。 該命令返回之前的效果。

如果總包含任何靈活的卷，操作將被中止，除非文件管理器處於維護模式。

如果聚合是嵌入在傳統卷，CIFS共享，用戶應當予以警告，然後限制的總和（因而整個傳統卷）。 使用此開關- T。 cifsdelaytime參數指定的分鐘數，延遲到嵌入式總脫機之前，在此期間，CIFS的傳統卷的用戶服務有待損失的警告。 0意味著時間立即採取總脫機沒有給予警告。 CIFS用戶可以失去的，如果他們沒有機會來終止應用擺好的數據。

AGGR擦洗恢復 aggrname | plexname | 組名 ]

恢復命名的總和，複雜，或組平價擦洗。 如果沒有名字，恢復所有的RAID組，目前正處於平價擦洗已經暫停。

AGGR擦洗啟動 [aggrname | plexname | 組名 ]

啟動命名的在線總校驗擦洗。 奇偶擦洗比較數據磁盤奇偶校驗磁盤的RAID組（S），糾正必要的奇偶校驗磁盤的內容。 如果沒有名字，平價擦洗啟動所有在線的集合體。 如果給出一個總的名稱，擦洗開始在總量中包含的所有RAID組。 如果一個 plex名稱，擦洗開始的plex中所有RAID組。

AGGR擦洗狀態 [aggrname | plexname | 組名 ] [- V]

打印平價擦洗命名的聚合，複雜的，或組中的地位;所有的RAID組，目前正處於平價擦洗，如果沒有名字。 狀態包括一個完成百分比，擦洗暫停狀態。

- v標誌顯示的日期和時間命名的總和，複雜，或組的當前狀態完成最後的全面擦洗;如果沒有名字，所有的RAID組。

AGGR擦洗停止 aggrname | plexname | 組名 ]

停止平價命名的聚合，複雜的，或組擦洗，如果沒有給定的名稱是，在所有的RAID組，目前正處於平價擦洗。

AGGR擦洗暫停 aggrname | plexname | 組名 ]

暫停平價命名的聚合，複雜的，或組擦洗，如果沒有給定的名稱是，在所有的RAID組，目前正處於平價擦洗。

AGGR show_space [- H | - K |米| - G | - T | - B] <aggrname>

顯示在聚合空間使用。 DF不同，此命令顯示的空間內的每個總AGGR show_space如果aggrname指定，只有在相應的總運行靈活體積使用情況，否則報告的聚集空間的使用率。

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.

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. 

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.

簇的注意事項

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

舉例

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

aggr create aggr1 20@9

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

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

Creates an aggregate named aggr1 with the specified three disks.

aggr create aggr1 10
aggr options aggr1 raidsize 5

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

aggr show_space -h ag1

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

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

aggr status aggr1 -r

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

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

SEE ALSO

目錄表

• 名稱
• 內容簡介
• 說明
• USAGE
• 簇的注意事項
• 舉例
• SEE ALSO

目錄表

名稱

SYNOPSIS

cf nfo [ enable | disable ] disk_shelf

cf nfo status

說明

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

OPTIONS

disable

Disables the takeover capability of both filers in the cluster.

enable

Enables the takeover capability of both filers in the cluster.

forcegiveback

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

partner giveback incomplete, some data may be lost

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

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

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

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

giveback [ -f ]

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

monitor

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

partner

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

status

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

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

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

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

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

nfo status

Displays the current negotiated failover status.

SEE ALSO

目錄表

• 名稱
• 內容簡介
• 說明
• 選項
• SEE ALSO

目錄表

名稱

內容簡介

BOOTFS核心 [- V] 磁盤

BOOTFS DIR - R] 路徑

BOOTFS轉儲 { 磁盤 | 群集 | 驅動器 } { 部門 }

BOOTFS FDISK 磁盤partition1sizeMB partition2sizeMB] [partition3sizeMB] [partition4sizeMB]

BOOTFS格式 驅動器 [ 標籤 ]

BOOTFS信息 磁盤

BOOTFS同步 [- F] { 磁盤 | 驅動器 }

BOOTFS測試 [- V] 磁盤

說明

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

磁盤

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

drive

A drive is a formatted partition on the disk. A disk may contain up to four drives. A drive name is generally of the form [PCI slot number]a.0:[partition

number]:,

eg 0a.0:1:. To discover your boot drive's name, use " bootfs help sub_ c ommand ".

sector

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

cluster

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

partitionNsizeMB

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

label

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

簇的注意事項

舉例

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

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

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

bootfs dump 0a.0 110

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

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

bootfs fdisk 0a.0 30

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

bootfs format 0a.0:1: NETAPP

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

bootfs info 0a.0

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

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

bootfs test -v 0a.0

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

SEE ALSO

下載

---

目錄表

• 名稱
• 內容簡介
• 說明
• 選項
• 簇的注意事項
• 舉例
• SEE ALSO

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

目錄表

名稱

內容簡介

說明

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

目錄表

• 名稱
• 內容簡介
• 說明
• FILES
• SEE ALSO

版權所有© 1994-2008公司NetApp的法律信息

目錄表

名稱

內容簡介

bmc reboot

bmc setup

bmc status

bmc test autosupport

說明

選項

幫助

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 .

簇的注意事項

舉例

可能會產生：

 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

附註

目錄表

• 名稱
• 內容簡介
• 說明
• 選項
• 簇的注意事項
• 舉例
• SEE ALSO
• 附註

版權所有© 1994-2008公司NetApp的法律信息

目錄表

名稱

內容簡介

說明

The following are the events filer monitors:

Start

Dump/restore starts.

Restart

Restart of a dump/restore.

End

Dump/restore completes successfully.

Abort

The operation aborts.

Error

Dump/restore hits an unexpected event.

Options

Logs the options as users specify.

Tape_open

Output device is opened successfully.

Tape_close

Output device is closed successfully.

Phase_change

As dump/restore completes a stage.

Snapshot

When the snapshot is created or located.

Base_dump

When a valid base dump entry is located.

Start_logging Logging begins.

Stop_logging

Logging ends.

TYPE TIME_STAMP IDENTIFIER EVENT (EVENT_INFO)

TYPE

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

TIME_STAMP

Shows date and time at which event occurs.

IDENTIFIER

Unique ID for the dump/restore.

EVENT

The event name.

EVENT_INFO

Event specific information.

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

In the particular example:

TYPE

= dmp

TIME_STAMP

= Thu Apr 5 18:54:56 PDT 2001

IDENTIFER

= /vol/vol0/ home(5)

EVENT

= Start

EVENT_INFO

= level 0, NDMP

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

FILES

/etc/log/backup

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

SEE ALSO

目錄表

• 名稱
• 內容簡介
• 說明
• FILES
• SEE ALSO

目錄表

名稱

內容簡介

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:

dump

runs natively on the filer.

NDMP

driven by a 3rd party client through NDMP protocol.

USAGE

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.

國家

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.

類型

Either dump or NDMP.

Device

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

Level

The level of the backup.

Path

Points to the tree that is being backed up.

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

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

SEE ALSO

目錄表

• 名稱
• 內容簡介
• 說明
• USAGE
• SEE ALSO

目錄表

名稱

SYNOPSIS

說明

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.

CONTENTS

Generation date and timestamp

Software Version

System ID

Hostname

SNMP contact name (if specified)

SNMP location (if specified)

Partner System ID (if clustered)

Partner Hostname (if clustered)

Cluster Node Status (if clustered)

Console language type

sysconfig -a output

sysconfig -c output

sysconfig -d output

System Serial Number

Software Licenses (scrambled prior to transmission)

Option settings

availtime output

cf monitor all output (if clustered)

ic stats performance output (if clustered with VIA)

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

snet stats -v output (if clustered with SNET)

ifconfig -a output

ifstat -a output

vlan stat output

vif status output

nis info output

nfsstat -c output (if licensed)

cifs stat output (if licensed)

cifs sessions summary (if licensed)

cifs sessions output (if licensed and enabled)

cifs shares summary (if licensed)

cifs shares output (if licensed and enabled)

vol status -l (if cifs is licensed)

httpstat output

vfiler status -a output (if licensed)

df output

df -i output

snap sched output

vol status -v output

vol status output

vol status -c output

vol scrub status -v output

sysconfig -r output

fcstat fcal_stats output

fcstat device_map output

fcstat link_stats output

ECC Memory Scrubber Statistics

ems event status output

ems log status output

registry values

perf report -t output

storage show adapter -a output

storage show hub -a output

storage show disk -a output

storage show fabric output

storage show switch output

storage show port output

EMS log file (if enabled)

/etc/messages content

Parity Inconsistancy information

WAFL_check logs

TYPES

BATTERY_LOW!!!
LOG_ALERT

BMC_EVENT: BUS ERROR
LOG_ERR

BMC_EVENT: POST ERROR
LOG_ERR

CLUSTER DOWNREV BOOT FIRMWARE

LOG_CRIT

CLUSTER GIVEBACK COMPLETE

LOG_INFO

CLUSTER TAKEOVER COMPLETE AUTOMATIC

LOG_ALERT

CLUSTER TAKEOVER COMPLETE MANUAL

LOG_INFO

CLUSTER TAKEOVER FAILED

LOG_INFO

CPU FAN WARNING - [fan]
LOG_WARNING

DEVICE_QUALIFICATION_FAILED

LOG_CRIT

DISK CONFIGURATION ERROR

LOG_ALERT

DISK_FAIL!!! - Bypassed by ESH
LOG_ALERT

DISK_FAIL!!!
LOG_ALERT

DISK_FAILURE_PREDICTED!!!
LOG_ALERT

DISK_FIRMWARE_NEEDED_UPDATE!!!
LOG_EMERG

DISK_IO_DEGRADED

LOG_WARNING

DISK_LOW_THRUPUT

LOG_NOTICE

DISK_RECOVERED_ERRORS

LOG_WARNING

FC-AL LINK_FAILURE!!!
LOG_ERR

FC-AL RECOVERABLE ERRORS

LOG_WARNING

OVER_TEMPERATURE_WARNING!!!
LOG_EMERG

PARTNER DOWN, TAKEOVER IMPOSSIBLE
LOG_ALERT

POSSIBLE BAD RAM

LOG_ERR

POSSIBLE UNLINKED INODE

LOG_ERR

REBOOT (after WAFL_check)
LOG_INFO

REBOOT (after entering firmware)
LOG_INFO

REBOOT (after giveback)
LOG_INFO

REBOOT (halt command)
LOG_INFO

REBOOT (internal halt)
LOG_INFO

REBOOT (internal reboot)
LOG_INFO

REBOOT (panic)
LOG_CRIT

REBOOT (power glitch)
LOG_INFO

REBOOT (power on)
LOG_INFO

REBOOT (reboot command)
LOG_INFO

REBOOT (watchdog reset)
LOG_CRIT

REBOOT

LOG_INFO

SHELF COOLING UNIT FAILED

LOG_EMERG

SHELF COOLING UNIT FAILED

LOG_WARNING

SNMP USER DEFINED TRAP

LOG_INFO

SYSTEM_CONFIGURATION_CRITICAL_ERROR

LOG_CRIT

SYSTEM_CONFIGURATION_ERROR

LOG_ERR

UNDER_TEMPERATURE_WARNING!!!
LOG_EMERG

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

WAFL_check!!!
LOG_ALERT

WEEKLY_LOG

LOG_INFO

[fan] FAN_FAIL!!!
LOG_ALERT

[mini core]
LOG_CRIT

[power supply failure]
LOG_ALERT

[power supply] POWER_SUPPLY_DEGRADED!!!
LOG_ALERT

[shelf over temperature critical]
LOG_EMERG

簇的注意事項

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

目錄表

• 名稱
• 內容簡介
• 說明
• 選項
• CONTENTS
• TYPES
• 簇的注意事項
• SEE ALSO

目錄表

名稱

SYNOPSIS

<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:

local7.*

@1.2.3.4

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

local7.*

/var/logs/filer_auditlogs

FILES

<logdir>/auditlog

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

SEE ALSO

目錄表

• 名稱
• 內容簡介
• 說明
• FILES
• SEE ALSO