NetApp的技術日記

NetApp已請給我許可再版的手冊頁。 他們還需要一點點整理，但數量龐大，意味著它會帶我一段時間，以獲得他們的所​​有排序和交叉引用正確，請原諒任何視覺問題的時刻。 我寫了一個快速的分析工具，讓所有的信息在這裡，所以有可能會產生的一些問題仍然。

我一直喜歡的方式是PHP有其功能頁面使用戶能夠直接到他們的評論。 這使得人們離開反饋功能和工具，並遵循一些額外的用途或不一定明確公佈的命令語法。 希望這能養活到NetApp的，以提高他們的文檔。

我一定要鼓勵人們評論任何可能有用的手冊頁，並希望建設成為一個有用的參考部分。 許多感謝NetApp幫助我的民歌。

一般來說 ， 手冊頁 命令 ， 男子 ， 手冊中， NetApp ， ONTAP的

目錄

名稱

內容簡介

描述

AGGR命令家庭是在Data ONTAP 7.0中新的。 vol命令系列提供比傳統vol_üMES控制一個單一的用戶可見的文件系統和單個RAID級別存儲容器（總）融合成一個不可分割的單位，仍然如此。 為了讓更多的存儲空間的靈活運用，總量現在也支持能力包含多個獨立的用戶級別的文件系統，名為“ 靈活的卷 。

的Data ONTAP 7.0完全支持傳統的和靈活的卷。 AGGR命令家庭是1文件管理器的集合體，包括那些在傳統卷的嵌入式管理的首選方法。

請注意，大部分的AGGR命令同樣適用於骨料類型，它包含靈活的數量和類型緊密結合，形成一個傳統的體積。 因此，長期總往往是用在這裡是指兩個存儲類。 在這些情況下，它提供了一個更長，更笨重的那句“聚集和傳統卷”的簡寫。

聚合可以是鏡像或鏡像的。 一個plex是一個總的WAFL存儲在物理副本。 鏡像總額由兩個plex鏡像的集合體，包含一個單一的plex。 為了創建一個鏡像總，你必須有一個文件管理器配置，支持RAID級別鏡像。 當鏡像文件管理器上啟用備用磁盤分為兩個磁盤池。 創建一個聚合時，在一個複雜的磁盤都必須來，從同一個磁盤池和兩個plex鏡像總必須由獨立池的磁盤，最大限度地提高故障隔離。 此策略可與-f選項，AGGR附加和AGGR的鏡子AGGR創建覆蓋，但不建議。

一個總的名稱可以包含字母，數字和下劃線字符（_），但第一個字符必須是字母或下劃線。 每個文件管理器可以創建一個高達200總量（包括嵌入在傳統卷）的總和。

一個plex可能是聯機或脫機。 如果它處於脫機狀態，它不能用於讀或寫訪問。 叢可以在下列國家的組合：

正常的所有plex的RAID組的功能。

並沒有失敗 ，至少在複雜的RAID組。

空的plex是一個正在創建的總額的一部分，一個或多個有針對性地合計的磁盤需要被添加到該plex之前要歸零。

積極的plex使用。

無效
plex的是不能使用。

重新同步
過時的plex的內容目前正在與其他複雜的聚合的內容重新同步過程（適用於鏡像總量只）。

添加磁盤
磁盤被添加的plex的RAID組（S）。

陳舊
這種狀態只發生在已經失敗的plex的鏡像集合體。 非失敗的plex將在此狀態下，如果要在其他的plex失敗的時候需要重新同步。

總體來說，一個斜線字符分隔符，和複雜的名稱使用的名稱命名的plex。 該系統在創建時會自動選擇plex名。 舉例來說，將是第一個plex在總aggr0創建aggr0/plex0。

聚合可能會上網，限制或脫機。 當聚合處於脫機狀態，沒有讀或寫訪問是允許的。 當集合是有限制的，允許某些操作（如總拷貝，重新計算校驗或RAID重建），但數據訪問是不允許的。 團聚，是不是一個傳統卷的一部分，只能被限制或脫機，如果它們不包含任何靈活的卷。

聚合可以在下列國家的組合：

AGGR總額是一個現代的總和;它是能夠包含零個或多個靈活的卷。

複製
聚合是目前活躍AGGR複製操作的目標總和。

退化
總包含至少一個未被重建降級的RAID組。

國外
總所包含的磁盤被移動到另一個文件管理器從目前的文件管理器。

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

初始化
總的是在被初始化的過程。

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

熨燙
正在執行在此聚集一WAFL一致性檢查。

鏡子退化
總鏡像聚合，和它的plex離線或RESYNCING的。

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

需要檢查
一的WAFL一致性檢查，需要總執行。

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

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重命名狀態的選項 

|

-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組的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 [ 大小 ]

|

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

創建一個嵌入式的聚合都可以作為一個傳統的音量使用-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]

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

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

原本在銷毀對象的磁盤將成為備用磁盤。 只有脫機聚合，傳統卷和plex可以被摧毀。

[aggrname plexname | groupname的 AGGR media_scrub狀態 ]
[-V]

打印媒體命名的總和，複雜的，或組的洗滌狀態。 如果沒有給定的名字，然後打印狀態為所有的RAID組，目前運行媒體擦洗。 包括％完整，是否暫停狀態。

-v標誌顯示，去年全媒體擦洗完成的日期和時間，日期和時間當前實例的媒體洗刷開始，命名的總和，複雜的，或組的當前狀態。 如果沒有給定的名字，這更詳細的狀態印刷與活躍的媒體洗刷所有的RAID組。

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

變成鏡像總給它添加一個plex的鏡像的總和。 無論是從選擇一個備用池的磁盤的plex新成立的，或者，如果指定了-v選項，從另一個現有的鏡像的聚合。 目前總aggrname必須是鏡像的。 使用AGGR創建一個新的，反映從頭總。

磁盤可以使用-D在與AGGR創建和add命令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關聯的數據，並創建一個快照被寫入了雙方的plex。 快照允許的plex隨後被帶回線上的高效再同步。

聚集的傳統量正在執行的操作數可以防止成功，為不同的時間長度，AGGR離線 。 如果發現這樣的操作，會有一秒鐘的等待一個這樣的操作完成。 如果他們不這樣做，命令中止。

支票也聚集的相關傳統內部ONTAP的過程中打開的卷中的文件。 如有發現，該命令將被中止。

AGGR在線 {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選項 aggrname [optname optval]

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

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

fs_size_fixed上 | 關閉

This option only applies to aggregates that are embedded in traditional volumes. It causes the file system to remain the same size and not grow or shrink when a SnapMirrored volume relationship is broken, or an aggr add is performed on it. This option is automatically set to be on when a traditional volume becomes a SnapMirrored volume. It will remain on after the snapmirror break command is issued for the traditional volume. This allows a traditional volume to be SnapMirrored back to the source without needing to add disks to the source traditional volume. If the traditional volume size is larger than the file system size, turning off this option will force the file system to grow to the size of the traditional volume. The default setting is off .

ignore_inconsistent on | off

This command can only be used in maintenance mode. If this option is set, it allows the aggregate containing the root volume to be brought online on booting, even though it is inconsistent. The user is cautioned that bringing it online prior to running WAFL_check or wafliron may result in further file system inconsistency.

nosnap on | off

If this option is on , it disables automatic snapshots on the aggregate. The default setting is off .

raidsize number

The value of this option is the maximum size of a RAID group that can be created in the aggregate. Changing the value of this option will not cause existing RAID groups to grow or shrink; it will only affect whether more disks will be added to the last existing RAID group and how large new RAID groups will be.

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

  -------------- RAID4 raidsize分鐘的默認最大-------------- R100的2 8 R150 2 6 FAS250 2 7 14其他（FCAL磁盤） 2 8月14日（ATA磁盤）2 7 7 ---------------------------- raid_dp raidsize分鐘的默認最大------ -------- R100的3 12 12 3 12 16其他（FCAL磁盤R150）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將下降之間的默認值和RAID4限制，是現存最大的RAID組的大小。 如果上述限制RAID4是最大的RAID組，新raidsize將是該限制。 如果下面是的RAID4默認值最大的RAID組，新的raidsize將是默認值。 如果raidsize已經低於的RAID4默認值是，它會減少1。

resyncsnaptime 數量

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

根

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

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

刪除聚合或傳統卷的根狀態的唯一途徑是另一個聚合或傳統卷的根選項設置。

snaplock_compliance

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

snaplock_enterprise

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

snapmirrored off

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

snapshot_autodelete on | off

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

aggr rename aggrname newname

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

aggr restrict aggrname
[ -t cifsdelaytime ]

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

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

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

aggr scrub resume [ aggrname | plexname | groupname ]

恢復命名的總和，複雜，或組校驗擦洗。 如果沒有指定名稱，恢復已經暫停目前正在進行平價擦洗所有的RAID組。

[aggrname plexname | groupname的 AGGR擦洗啟動 ]

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

AGGR的磨砂膏狀態 [aggrname | plexname | 組名 ] [-V]

打印平價擦洗命名的總和，複雜的，或組中的地位，目前所有的RAID組進行校驗擦洗，如果沒有給定名稱。 狀態包括％完整的，磨砂的懸浮狀態。

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

[aggrname plexname | groupname的 AGGR擦洗站 ]

Stops parity scrubbing on the named aggregate, plex, or group; if no name is given, on all RAID groups currently undergoing a parity scrubbing.

aggr scrub suspend [ aggrname | plexname | groupname ]

Suspends parity scrubbing on the named aggregate, plex, or group; if no name is given, on all RAID groups currently undergoing parity scrubbing.

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

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

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

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

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

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.

-c標誌顯示塊的校驗數據的完整性保護功能的升級狀態。

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.

CLUSTER CONSIDERATIONS

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

另請參見

目錄

• 名稱
• 內容簡介
• 描述
• 用法
• 集群的注意事項
• 舉例
• 另請參見

手冊頁 AGGR ， 男子 ， 手冊中， NetApp ， ONTAP的

Table of Contents

NAME

SYNOPSIS

cf nfo [ enable | disable ] disk_shelf

cf nfo status

DESCRIPTION

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

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

Table of Contents

• NAME
• SYNOPSIS
• DESCRIPTION
• OPTIONS
• SEE ALSO

Manual Pages cf , man , manual , NetApp , ONTAP

Table of Contents

NAME

SYNOPSIS

bootfs core [ -v ] disk

bootfs dir [ -r ] path

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

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

bootfs format drive [ label ]

bootfs info disk

bootfs sync [ -f ] { disk | drive }

bootfs test [ -v ] disk

DESCRIPTION

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

OPTIONS

-v

Turns on verbose output.

-r

Recursively lists directories and files.

path

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

disk

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

drive

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

number]:,

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

sector

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

cluster

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

partitionNsizeMB

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

label

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

CLUSTER CONSIDERATIONS

EXAMPLES

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

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

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

bootfs dump 0a.0 110

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

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

bootfs fdisk 0a.0 30

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

bootfs format 0a.0:1: NETAPP

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

bootfs info 0a.0

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

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

bootfs test -v 0a.0

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

SEE ALSO

下載

---

Table of Contents

• NAME
• SYNOPSIS
• DESCRIPTION
• OPTIONS
• CLUSTER CONSIDERATIONS
• EXAMPLES
• SEE ALSO

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

Manual Pages bootfs , man , manual , NetApp , ONTAP

Table of Contents

NAME

SYNOPSIS

DESCRIPTION

FILES

/etc/boot

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

SEE ALSO

Table of Contents

• NAME
• SYNOPSIS
• DESCRIPTION
• FILES
• SEE ALSO

Copyright © 1994-2008 NetApp, Inc. Legal Information

Manual Pages boot , man , manual , NetApp , ONTAP

Table of Contents

NAME

SYNOPSIS

bmc reboot

bmc setup

bmc status

bmc test autosupport

DESCRIPTION

OPTIONS

help

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

reboot

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

setup

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

status

Display the current status of the BMC.

test autosupport

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

CLUSTER CONSIDERATIONS

EXAMPLES

might produce:

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

SEE ALSO

NOTES

Table of Contents

• NAME
• SYNOPSIS
• DESCRIPTION
• OPTIONS
• CLUSTER CONSIDERATIONS
• EXAMPLES
• SEE ALSO
• NOTES

Copyright © 1994-2008 NetApp, Inc. Legal Information

Manual Pages bmc , man , manual , NetApp , ONTAP

Table of Contents

NAME

SYNOPSIS

DESCRIPTION

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.

錯誤

Dump/restore hits an unexpected event.

選項

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

Table of Contents

• NAME
• SYNOPSIS
• DESCRIPTION
• FILES
• SEE ALSO

Manual Pages backuplog , man , manual , NetApp , ONTAP

Table of Contents

NAME

SYNOPSIS

backup terminate <ID>

DESCRIPTION

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.

State

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

類型

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

Table of Contents

• NAME
• SYNOPSIS
• DESCRIPTION
• USAGE
• SEE ALSO

Manual Pages backup , man , manual , NetApp , ONTAP

Table of Contents

NAME

SYNOPSIS

DESCRIPTION

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

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

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

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

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

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

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

The setup command tries to configure autosupport as follows:

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

Setup also queries for autosupport.from information.

OPTIONS

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

主機

SNMP contact name (if specified)

SNMP location (if specified)

Partner System ID (if clustered)

Partner Hostname (if clustered)

Cluster Node Status (if clustered)

Console language type

sysconfig -a output

sysconfig -c output

sysconfig -d output

System Serial Number

Software Licenses (scrambled prior to transmission)

Option settings

availtime output

cf monitor all output (if clustered)

ic stats performance output (if clustered with VIA)

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

snet stats -v output (if clustered with SNET)

ifconfig -a output

ifstat -a output

vlan stat output

vif status output

nis info output

nfsstat -c output (if licensed)

cifs stat output (if licensed)

cifs sessions summary (if licensed)

cifs sessions output (if licensed and enabled)

cifs shares summary (if licensed)

cifs shares output (if licensed and enabled)

vol status -l (if cifs is licensed)

httpstat output

vfiler status -a output (if licensed)

df output

df -i output

snap sched output

vol status -v output

vol status output

vol status -c output

vol scrub status -v output

sysconfig -r output

fcstat fcal_stats output

fcstat device_map output

fcstat link_stats output

ECC Memory Scrubber Statistics

ems event status output

ems log status output

registry values

perf report -t output

storage show adapter -a output

storage show hub -a output

storage show disk -a output

storage show fabric output

storage show switch output

storage show port output

EMS log file (if enabled)

/etc/messages content

Parity Inconsistancy information

WAFL_check logs

TYPES

BATTERY_LOW!!!
LOG_ALERT

BMC_EVENT: BUS ERROR
LOG_ERR

BMC_EVENT: POST ERROR
LOG_ERR

CLUSTER DOWNREV BOOT FIRMWARE

LOG_CRIT

CLUSTER GIVEBACK COMPLETE

LOG_INFO

CLUSTER TAKEOVER COMPLETE AUTOMATIC

LOG_ALERT

CLUSTER TAKEOVER COMPLETE MANUAL

LOG_INFO

CLUSTER TAKEOVER FAILED

LOG_INFO

CPU FAN WARNING - [fan]
LOG_WARNING

DEVICE_QUALIFICATION_FAILED

LOG_CRIT

DISK CONFIGURATION ERROR

LOG_ALERT

DISK_FAIL!!! - Bypassed by ESH
LOG_ALERT

DISK_FAIL!!!
LOG_ALERT

DISK_FAILURE_PREDICTED!!!
LOG_ALERT

DISK_FIRMWARE_NEEDED_UPDATE!!!
LOG_EMERG

DISK_IO_DEGRADED

LOG_WARNING

DISK_LOW_THRUPUT

LOG_NOTICE

DISK_RECOVERED_ERRORS

LOG_WARNING

FC-AL LINK_FAILURE!!!
LOG_ERR

FC-AL RECOVERABLE ERRORS

LOG_WARNING

OVER_TEMPERATURE_WARNING!!!
LOG_EMERG

PARTNER DOWN, TAKEOVER IMPOSSIBLE
LOG_ALERT

POSSIBLE BAD RAM

LOG_ERR

POSSIBLE UNLINKED INODE

LOG_ERR

REBOOT (after WAFL_check)
LOG_INFO

REBOOT (after entering firmware)
LOG_INFO

REBOOT (after giveback)
LOG_INFO

REBOOT (halt command)
LOG_INFO

REBOOT (internal halt)
LOG_INFO

REBOOT (internal reboot)
LOG_INFO

REBOOT (panic)
LOG_CRIT

REBOOT (power glitch)
LOG_INFO

REBOOT (power on)
LOG_INFO

REBOOT (reboot command)
LOG_INFO

REBOOT (watchdog reset)
LOG_CRIT

REBOOT

LOG_INFO

SHELF COOLING UNIT FAILED

LOG_EMERG

SHELF COOLING UNIT FAILED

LOG_WARNING

SNMP USER DEFINED TRAP

LOG_INFO

SYSTEM_CONFIGURATION_CRITICAL_ERROR

LOG_CRIT

SYSTEM_CONFIGURATION_ERROR

LOG_ERR

UNDER_TEMPERATURE_WARNING!!!
LOG_EMERG

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

WAFL_check!!!
LOG_ALERT

WEEKLY_LOG

LOG_INFO

[fan] FAN_FAIL!!!
LOG_ALERT

[mini core]
LOG_CRIT

[power supply failure]
LOG_ALERT

[power supply] POWER_SUPPLY_DEGRADED!!!
LOG_ALERT

[shelf over temperature critical]
LOG_EMERG

CLUSTER CONSIDERATIONS

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

Table of Contents

• NAME
• SYNOPSIS
• DESCRIPTION
• OPTIONS
• CONTENTS
• TYPES
• CLUSTER CONSIDERATIONS
• SEE ALSO

Manual Pages AutoSupport , man , manual , NetApp , ONTAP

Table of Contents

NAME

SYNOPSIS

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

DESCRIPTION

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

Table of Contents

• NAME
• SYNOPSIS
• DESCRIPTION
• FILES
• SEE ALSO

Manual Pages auditlog , man , manual , NetApp , ONTAP