7月7日
NetApp公司已请批准我在这里发布他们的手册页。 他们还需要一些整理，但绝对数量意味着它会带我一段时间，让他们全部整理和交叉引用不当，请原谅目前任何视觉问题。 我写了一个快速解析工具，在这里得到的所有信息，因此可以从仍然造成一些问题。
我一直喜欢的方式，PHP的网页，其功能使用户能够直接上发表评论。 这使人们离开反馈功能和工具，并遵循一些额外的用途或命令不一定清楚公布的语法了。 希望这回能反馈到NetApp的改善他们的文档。
我一定要鼓励市民发表意见的任何可能有用的人的网页，并希望这将建立一个有用的小参考部分。 非常感谢再次为帮助我处理这个NetApp的民俗。
7月7日
该aggr命令系列7.0新的Data ONTAP。 第一卷家庭提供的命令控制单元比传统vol_ ü 尼姆的融合单个用户可见的文件系统和单个RAID级别的存储容器（不可分割的整体）为一，至今没有。 为了让更多的灵活的存储利用，总量现在也支持包含多个的能力，独立的用户级别的文件系统命名为灵活的卷 。
的Data ONTAP 7.0完全支持传统的和灵活的卷。 该系列是aggr命令的总量为首选方法管理滤波器，包括那些在传统的嵌入式卷。
请注意，命令大部分aggr同样适用于总类型，它包含灵活的数量和类型，数量是紧紧结合，形成一个传统。 因此，这个词经常被用来总量这里指两个存储类。 在这种情况下，它提供了一种简便的更长，更笨重的短语“总量和传统的数量”。
骨料可被镜像或unmirrored。 阿丛是一个总的物理副本对WAFL存储内。 镜像总分为两丛; unmirrored总量包含一个复合体。 为了创建一个镜像的总和，你必须有一个菲勒配置，支持RAID级别镜像。 当镜像对备案人启用备用磁盘分为两个磁盘池。 当聚合创建，所有的磁盘在一个丛必须来自同一个磁盘池，以及一个镜像总量的2丛必须包括从独立的磁盘池，这最大限度地故障隔离。 这一政策可以重写与- f选项aggr创建，aggr添加和aggr镜 ，但不建议。
一个总的名称可以包含字母，数字和下划线字符（_），但第一个字符必须是字母或下划线。 阿总量高达200（包括传统的嵌入量的总和）可以创建每个菲勒。
阿丛，可在线或离线。 如果是脱机，它是不是可以读或写访问。 丛可以在以下状态的组合：
所有RAID丛正常群体在有功能。
失败至少丛一组在RAID的失败。
清空丛创建的一部分被认为是一个聚合，一个或需要更多的磁盘总针对被清零前被添加到丛。
活跃的丛可使用。
无效
该丛不适用于使用。
resyncing
该复合体的内容已过时，目前的过程中正在重新同步同其他丛的总的内容（仅适用于镜像总量）。
添加磁盘
磁盘被添加到丛的RAID组（S）。
陈旧
这种状态只发生在那里的镜像丛一失败聚合。 非失败丛将在此状态下，如果需要在其他时间重新同步丛失败。
阿丛名为利用总体来说，一个反斜杠字符分隔的名称，以及丛名称。 该系统会自动选择在创建时丛名字。 例如，第一个创建的丛总aggr0将aggr0/plex0。
聚合可以联机，限制，或脱机。 当总量离线，没有读或写访问是允许的。 当一个总量限制，允许某些操作（如总复制，重新计算校验或RAID重建），但数据访问是不允许的。 汇总是不是一个传统的量的一部分，只能限制或offlined如果它们不包含任何灵活的卷。
骨料，可在以下状态的组合：
aggr的总和，是很现代的总和，它是能够大量含有零个或更多的灵活性。
复制
目前的总目标总的复制操作的积极aggr。
退化
总包含至少一个退化的RAID组，不被重建。
国外
总的磁盘包含被转移到当前菲勒从另一个菲勒。
成长
磁盘的过程中被添加到的总和。
初始化
总的过程中被初始化。
无效
总册，没有包含任何可以加入。 通常发生这种情况后，才中止总复制操作。
熨烫
阿WAFL的一致性检查正在执行此聚合。
镜子退化
总合计是一个镜像，丛一和它脱机或resyncing。
镜像
总镜像和RAID组的所有功能。
需要检查
阿WAFL的一致性检查需要对总结进行。
局部的
至少有一个磁盘被发现的总和，而是两个或更多的磁盘丢失。
支持RAID0的总组成的RAID - 0（无奇偶校验）RAID组（V系列和NetCache的只）。
raid4的总组成的RAID - 4 RAID组。
raid_dp
总的RAID - DP的（双奇偶校验）由RAID组。
重建
至少有一个RAID组中的总正在重建。
重定向
总结重新分配或文件用- p选项重新配置已开始对总结。 在读取性能，以总销量可能会下降。
resyncing
对镜像的聚合丛之一是被重新同步。
snapmirrored
总量是另一个聚合snapmirrored副本。 这种状态只能出现如果总体积是一个传统的一部分。
文章的总量与单个熔量。 这也被称为是一个传统的数量和准确的数量相当于前的Data ONTAP 7.0存在。 灵活的卷内不能创建这个总和。
验证
一个RAID镜像验证操作，目前正在运行的总和。
WAFL的不一致
累计已明显损坏。 请联系客户支持如果你看到在这个国家的总和。
添加镜像复制限制undestroy离线擦洗验证创建在线show_space摧毁分裂media_scrub选择重命名状态 如果使用- g选项不使用，磁盘被添加到最近创建RAID组的util满座，然后一个或多个新的RAID组的创建和剩余的磁盘被添加到新组。 任何其他现有的RAID组仍然是不完整部分填补。
- g选项允许指定一个RAID组（例如为，rg0），在其中指定的磁盘应添加或群体的方法，其中磁盘被添加到新的或现有的RAID。
如果- g选项用于指定一个RAID组，即RAID组必须已经存在。 磁盘被添加到该RAID组的util它已满。 任何剩余的磁盘将被忽略。
如果- g选项是组其次是新的Data ONTAP创建一个或多个RAID组，并增加了新的磁盘到他们，即使磁盘将融入现有的RAID。 任何现有的RAID组仍然是不完整部分填补。 新的RAID组名称是自动选择。 它不是可以指定为新的RAID组的名称。
如果- g选项都是其次，在指定的Data ONTAP添加到现有的磁盘RAID组第一。 毕竟现有的RAID组都满了，它会创建一个或多个新的RAID组，并增加了指定的磁盘到新的群体。
- n选项可以用来显示系统的命令将执行，但实际上没有进行任何更改。 这是非常有用的自动显示选定的磁盘，例如。
默认情况下，菲勒填补了一个RAID组磁盘之前，开始另一个RAID组。 假设一个聚合目前一个RAID 12磁盘和RAID组大小划分为14。 如果你加5磁盘本的总和，这将有14个磁盘和另外3 RAID组磁盘一个RAID组。 备案人之间的不平均分配RAID组磁盘。
您不能添加磁盘镜像总如果丛之一是脱机。
在一丛的磁盘不得跨磁盘池。 这种行为可以被覆盖用- f标志一起使用时磁盘用- D参数列出补充。 - f标志，结合三维 ，也可用于强制加入磁盘具有转速不匹配的总大多数现有磁盘的。
aggr复制中止[- H]的 operation_number | 所有
终止聚合复制操作。 该opera_吨ion_number参数指定的操作将终止。 如果指定ALL，所有总活跃复制操作被终止。
aggr复制开始
[- S的 | - S的 快照 ] [- C的]
来源目的地
复制所有数据，包括快照和灵活的总销量从一个到另一个。 如果- S标志使用时，命令所有快照副本目的地总在源聚合到。 要指定一个特定的快照复制，使用- s标志其次是快照的名称。 如果您使用不使用- S或- s命令国旗的，备案人创建和执行一个快照是在复制的时候aggr启动命令只是快照复制到目标的总和。
- c标志，如果需要源总量有自由空间碎片上执行它，或者如果目标总量将自由空间碎片整理。 自由空间碎片整理可以执行的一个命令总使用重新分配 。
总结副本只能进行汇总主机之间灵活的卷。 这是在传统的嵌入式量不能参加团聚。
源和目标总量可在同一或不同的档案库的菲勒。 如果源或目标总量的filer_name：格式aggre_克ate_name上菲勒以外的一开始就其中输入命令，aggr复制指定的总名称研究。
总复制的档案库的参与，必须符合以下命令复制启动所需的aggr得以圆满完成：
消息来源合计必须联机和目标总量必须受到限制。
如果在两个文件服务器，每个菲勒必须定义为一个值得信赖的备案人的其他主机。 也就是说，菲勒的名称必须在/ etc / hosts.equiv文件其他菲勒的。
如果该副本备案人是相同的，必须包含在本地主机备案人的/ etc / hosts.equiv文件。 此外，环回地址必须在菲勒的/ etc / hosts文件。 否则，备案人不能给自己发送数据包通过环回地址时，尝试复制数据。
总的目标可用磁盘空间必须大于或等于源总可用磁盘空间。 使用的 DF -甲 路径命令来查看某个特定总额的可用磁盘空间。
每个aggr启动命令复制拷贝操作聚合生成两个：一个总目标，从源头读取数据汇总和一个数据写入到。 每个菲勒同时支持多达4个聚合复制操作。
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复制油门命令只允许你设置的进展速度在1 aggr复制操作是。 要设置默认aggr复印速度，用于将来的复制操作，使用选项命令来设置aggr.copy.throttle选项。
aggr创建 aggrname
[- f]的
[ 米 ]
[- ŋ]
[-吨 raidtype]
[- R的 raidsize]
[- T的 磁盘类型 ]
[- R的 转 ]
[- L的 [ 符合 | 企业 ]]
[- v]将
[-升 语言代码 ]
（ndisks [@ 大小 ]
一个嵌入式骨料可作为选项的一部分创建一个传统 V音量使用-。 它不能包含任何灵活的卷。
一个普通的总和，选项创建不使用- v时 ，只能包含灵活的卷。 它不能被纳入传统的体积，它包含创建后没有立即册。 新创建灵活的卷可以使用命令创建卷 。
了- t参数指定raidtype S型的RAID组（）被用来创建聚合。 可能的RAID组类型4 raid4为RAID -）raid_dp为RAID - DP的（双奇偶校验， 支持RAID0和条纹的简单，没有平等的保护。 对申报者的总量和传统量默认raidtype是raid_dp。 设置raidtype不允许在V系列系统;的支持RAID0默认总是使用。
加上- r参数指定raidsize总在每个磁盘的最大数目RAID组研究。 最高和可靠性的考虑默认值raidsize是平台依赖的基础上，性能和。 见aggr选项raidsize更多详情。
该- T的 磁盘类型参数指定的磁盘类型的使用时，创造一个新的总和。 它是只需要在连接到不同类型的磁盘系统。 可能的磁盘的类型有： 阿拉木图的FCAL，伦的SAS，SATA和 SCSI。 混合聚合在一个磁盘的类型不同的是不允许的。- T的不能一起使用三维 。
磁盘类型标识磁盘技术和连接类型。 阿拉木图标识回路）与ATA磁盘或IDE或连接的串行ATA接口在货架上的FCAL（光纤通道仲裁。标识的FCAL。伦铝财委会在磁盘连接在货架上的FC -标识出口的虚拟磁盘外部存储阵列。 其基本技术和RAID磁盘阵列类型取决于贮藏对执行这些外部。标识的SAS串行连接SCSI硬盘配套货架英寸的SATA标识的SAS货架串行ATA磁盘。SCSI接口代表了小型计算机系统，它是为了向后兼容与早期的磁盘技术。
加上- r参数指定的磁盘转速类型的基础上，以使用rpm的转速每分钟在转速（）。 这是只有在有需要与不同的旋转速度磁盘系统。 转速的典型值是5400，7200，10000和15000。- R可不能一起使用，用- d。
ndisks是总人数的磁盘，包括奇偶磁盘。 在这个新创建的总的磁盘来自备用磁盘池中。 在此池的最小磁盘参加总第一，除非你指定的大小参数@。 大小是GB的磁盘大小，总的磁盘是在规定的10％，这一规模将在选定的被使用。
- m选项可以用来指定新的聚合进行镜像（有两个丛）创建时。 如果这个选项给出，则表示整个磁盘将被分割的两个丛。 默认情况下，新的总不会镜像。
- n选项可以用来显示系统的命令将执行，但实际上没有进行任何更改。 这是非常有用的自动显示选定的磁盘，例如。
如果您使用- d 为disk1 [disk2 ... ]参数，菲勒创建具有指定的总备用磁盘为disk1，disk2，等等。 您可以指定的磁盘的名称空间分隔的列表。 两个单独列出，如果必须指定新的总量镜像。 在案件的总和，是反映新的，指定的磁盘必须导致对每一个新的磁盘丛人数相等。
在一丛的磁盘不得跨越备用池。 这种行为可以被覆盖的- f选项。 相同的选项也可以用来强制使用磁盘，没有匹配的转速。 使用- f选项，使用时只使用效果与- d选项来指定磁盘。
要创建的SnapLock的总和，指定的国旗与aggr - L的创建命令。 此标志仅支持如果任何的SnapLock法规或的SnapLock Enterprise是许可。 作者的SnapLock创建聚合类型，无论是履约或企业，是由安装的SnapLock许可决定。 如果双方的SnapLock法规和 SnapLock 企业被授权，使用- L的履约或- L的企业，指定所需的聚合类型。
的- l language_code参数仅可用于创建一个传统的音量时使用选项- V的 。 该菲勒创建与语言代码中指定的语言传统的音量。 默认是由菲勒的根量所使用的语言。 见第一卷 男子页的语言代码列表。
aggr摧毁（aggrname | plexname）[- f]的
销毁总命名aggrname，或命名plexname的丛。 请注意，如果指定的总量绑在传统的容量，然后传统的体积本身也被破坏。
如果总指定，在总体上所有丛被破坏。 命名总还必须不包含任何灵活的量，不论其安装状态（在线，限制，或脱机）。 如果一丛指定，丛被破坏，留下一unmirrored聚合或传统卷包含其余丛。 前破坏的总和，传统的体积或丛，提示用户确认操作。 - f标志可以用来摧毁一合计，传统的数量或不提示用户丛。
原本在被摧毁的对象成为备用磁盘的磁盘。 只有脱机总量，传统量和丛可以被摧毁。
aggr media_scrub地位 [aggrname | plexname | 群组名称 ]
[- v]将
擦洗打印媒体已命名的总和，丛，或团体的地位。 如果没有给出名字，然后印制的地位是所有RAID当前正在运行的一组媒体擦洗。 该状态包括一个完成百分比和是否暂停。
使用- v标志显示的日期和时间的过去媒体擦洗充分完成，日期和时间的媒体开始洗刷当前实例，以及目前的状况或组已命名的骨料，丛。 如果没有给出名字，这更详细的地位是印有磨砂活跃的媒体所有的RAID组。
aggr镜 aggrname
[- f]的
[- ŋ]
[- V的 victim_aggrname]
[ 三维 为disk1 [disk2 ... ]]
打开一unmirrored聚合成镜像，加入一丛给它的总和。 该丛要么是新成立的，从池中选择一个备用磁盘，或者，如果- v选项指定，采取的是从另一个现有总unmirrored。 目前总结aggrname必须是unmirrored。 使用aggr创建作出新的，从总体镜像从零开始。
磁盘可以明确指定使用创建d在aggr用同样的方式和aggr添加命令。 作者指出，必须符合现行的总数目前磁盘的数量。 磁盘指定不允许跨越磁盘池。 这种行为可以被覆盖的- f选项。 - f选项，结合三维 ，也可用于强制使用磁盘具有转速不匹配的总大多数现有磁盘的。
如果没有明确指定磁盘，则磁盘将被自动选择匹配的总的现有丛的。
- v选项可以用来参加victim_aggrname aggrname回，形成一个镜像的总和。 其结果是总名为aggrname镜像，否则是相同aggrname手术前。Victim_aggrname有效地摧毁。Victim_aggrname必须此前已与aggrname镜像，然后通过aggr Victim_aggrname分离分裂命令。必须脱机。 选项与- V时，- f选项可以用来加入im_aggrname不提示用户aggrname和vic_吨。
- n选项可以用来显示系统的命令将执行，实际上不进行任何更改。 这是非常有用的自动显示选定的磁盘，例如。
aggr离线 （aggrname | plexname）
[-吨 cifsdelaytime]
注意到总命名aggrname（或命名plexname的丛）脱机。 该命令，然后返回需要的效果。 如果总量已经在限制状态，则它已经为数据访问不可用，和下面的说明非常不适用。
如果包含任何灵活的总数量，则操作被中止，除非菲勒在维护模式。
除了在维护模式，包含当前的总根量不属于可脱机。 聚合含根量已明显成为root（ 姓名使用选项 vol_ 卷 ）也不能脱机。
如果是在传统的总数量已CIFS共享嵌入，用户应给予警告后才采取总额（因而整个传统的音量）脱机。 使用- t开关本。 该cifsdelaytime参数指定的分钟数，然后才采取拖延嵌入式总脱机，在此期间，用户数量的CIFS的传统是服务警告说，悬而未决的损失。 0表示没有时间立即采取给予警告的总体脱机。 CIFS的用户可能会失去，如果他们没有机会终止应用程序正常数据。
如果plexname指定，丛必须联机部分镜像丛总，都必须。 在此之前offlining一丛，系统会清空所有内部缓冲与丛相关的数据并创建一个写出既丛快照。 快照可以当丛随后带回在线效率同步。
一个操作数被上执行总体积的传统可以防止成功aggr脱机 ，不同长度的时间。 如果这些行动发现，有将是这种行动一秒等待完成。 如果他们不这样做，命令中止。
支票是还为在总的相关传统量由内部的OnTap进程打开的文件。 该命令将中止，如果发现有损坏。
aggr在线 （aggrname | plexname）
[- f]的
带来的总命名aggrname（或命名plexname的丛）在线。 此命令立即生效。 如果指定的总体积是一个传统的嵌入式，体积也带来了网上。
如果aggrname被指定，它必须是目前离线，限制，或外国。 如果总量外国的，它将于本机前被带到网上。 “外国”总量是由一个总的磁盘从另一个菲勒感动，说从来没有提出对当前菲勒线上。 汇总并非外国被认为是“本土”。
如果总不一致，但并没有丢失数据，用户将被警告后，引进总在线提示。 - f标志，可用于覆盖此行为。 这是明智的运行WAFL_check（或做SnapMirror快照镜像初始化案件数量在传统的聚合嵌入式）之前，将不一致的总在线。 总在线带来不一致的进一步增加了文件系统损坏的风险。 如果总不一致，并经历了数据可能丢失，不能联机，除非WAFL_check（或SnapMirror快照镜像初始化嵌入式案）已被总在。
如果plexname指定，丛必须联机部分的镜像的总和。 该系统将启动，作为在线处理的一部分，丛重新同步。
aggr选项 aggrname [optname optval]
显示optval选项已设置为总aggrname，或值设置的选项名为optname总命名aggrname到。 该命令仍然有效的备案后重新启动，所以没有需要添加aggr选项命令到/ etc / rc文件。 一些选项有值的数字。 一些选项有可能在值（它也可以表示为1的话 ， 真实的 ，或）或关闭 （这也可以为0表示没有 ， 虚假 ，或）。 一个大写和小写字符时可以使用键入一个选项的值的混合物。 该aggr状态命令显示的总选项，每设置。
下面描述的选项及其可能的值：
fs_size_fixed于 | 关闭
此选项只适用于那些在传统的嵌入式量总量。 这会导致文件系统保持相同的大小，而不是增长或收缩时SnapMirrored量关系被打破，或aggr补充的是它上执行。 此选项会自动设置为在一个传统的量时成为SnapMirrored量。 它将继续命令后，SnapMirror快照镜像发放额突破是为传统。 这使得传统的量是SnapMirrored无需添加磁盘到源传统的音量回源。 如果传统的音量大小大于文件系统大小，关闭此选项将强制文件系统增长到了传统体积的大小。 默认设置是关闭的。
ignore_inconsistent于 | 关闭
此命令只能用于维护模式。 如果这个选项被设置，它允许含有的总根量得以在线上启动，即使它是不一致的。 用户是把它提醒说，网上运行WAFL_check之前或wafliron可能会导致进一步的档案系统不一致的情况。
nosnap于 | 关闭
如果此选项时 ，它的总禁用自动快照。 默认设置是关闭的。
raidsize 号码
此选项的值是一个RAID组可以在创建的最大规模的总额。 改变这个选项的值将不会造成现有RAID组增长或收缩，它只会影响是否有更多的磁盘将被添加到最后一个现有的RAID组和多大的新RAID组将。
法律上raidtype值这个选项而定。 例如，允许更大的RAID raid_dp比团体raid4。 界限和默认值也为菲勒用具和不同类型的磁盘不同类型不同。 以下表定义的限制和raidsize默认值。
—————————————— raid4 raidsize min default max —————————————— R100 2 8 8 R150 2 6 6 FAS250 2 7 14 other (FCAL disks) 2 8 14 other (ATA disks) 2 7 7 —————————————— —————————————— raid_dp raidsize min default max —————————————— R100 3 12 12 R150 3 12 16 other (FCAL disks) 3 16 28 other (ATA disks) 3 14 16 ——————————————
raidtype raid4 | raid_dp | raid0
Sets the type of RAID used to protect against disk failures. Use of raid4 provides one parity disk per RAID group, while raid_dp provides two. Changing this option immediately changes the RAID type of all RAID groups within the aggregate. When upgrading RAID groups from raid4 to raid_dp , each RAID group begins a reconstruction onto a spare disk allocated for the second `dparity' parity disk.
Changing this option also changes raidsize to a more suitable value for new raidtype . When upgrading from raid4 to raid_dp , raidsize will be increased to the default value for raid_dp . When downgrading from raid_dp to raid4 , raidsize will be decreased to the size of the largest existing RAID group if it is between the default value and the limit for raid4 . If the largest RAID group is above the limit for raid4 , the new raidsize will be that limit. If the largest RAID group is below the default value for raid4 , the new raidsize will be that default value. If raidsize is already below the default value for raid4 , it will be reduced by 1.
resyncsnaptime number
This option is used to set the mirror resynchronization snapshot frequency (in minutes). The default value is 60 minutes.
root
If this option is set on a traditional volume, then the effect is identical as that defined in vol man page. Otherwise, if this option is set on an aggregate capable of containing flexible volumes, then that aggregate is marked as being the one that will also contains the root flexible volume on the next reboot. This option can be used on only one aggregate or traditional volume at any given time. The existing root aggregate or traditional volume will become a non-root entity after the reboot.
Until the system is rebooted, the original aggregate and/or traditional volume will continue to show root as one of its options, and the new root aggregate or traditional volume will show diskroot as an option. In general, the aggregate that has the diskroot option is the one that will contain the root flexible volume following the next reboot.
The only way to remove the root status of an aggregate or traditional volume is to set the root option on another aggregate or traditional volume.
snaplock_compliance
This read only option indicates that the aggregate is a SnapLock Compliance aggregate. Aggregates can only be designated SnapLock Compliance aggregates at creation time.
snaplock_enterprise
This read only option indicates that the aggregate is a SnapLock Enterprise aggregate. Aggregates can only be designated SnapLock Enterprise aggregates at creation time.
snapmirrored off
If SnapMirror is enabled for a traditional volume (SnapMirror is not supported for aggregates that contain flexible volumes), the filer automatically sets this option to on . Set this option to off if SnapMirror is no longer to be used to update the traditional volume mirror. After setting this option to off , the mirror becomes a regular writable traditional volume. This option can only be set to off ; only the filer can change the value of this option from off to on .
snapshot_autodelete on | off
This option is used to set whether snapshot are automatically deleted in the aggr. If set to on then snapshots may be deleted in the aggr to recover storage as necessary. If set to off then snapshots in the aggr are not automatically deleted to recover storage. Note that snapshots may still be deleted for other reasons, such as maintaining the snapshot schedule for the aggr, or deleting snapshots that are associated with specific operations that no longer need the snapshot. To allow snapshots to be deleted in a timely manner the number of aggr snapshots is limited when snapshot_autodelete is enabled. Because of this, if there are too many snapshots in an aggr then some snapshots must be deleted before the snapshot_autodelete option can be enabled.
aggr rename aggrname newname
Renames the aggregate named aggrname to newname . If this aggregate is embedded in a traditional volume, then that volume's name is also changed.
aggr restrict aggrname
[ -t cifsdelaytime ]
Put the aggregate named aggrname in restricted state, starting from either online or offline state. The command takes effect before returning.
If the aggregate contains any flexible volumes, the operation is aborted unless the filer is in maintenance mode.
If the aggregate is embedded in a traditional volume that has CIFS shares, users should be warned before restricting the aggregate (and hence the entire traditional volume). Use the -t switch for this. The cifsdelaytime argument specifies the number of minutes to delay before taking the embedded aggregate offline, during which time CIFS users of the traditional volume are warned of the pending loss of service. A time of 0 means take the aggregate offline immediately with no warnings given. CIFS users can lose data if they are not given a chance to terminate applications gracefully.
aggr scrub resume [ aggrname | plexname | groupname ]
Resumes parity scrubbing on the named aggregate, plex, or group. If no name is given, resume all RAID groups currently undergoing a parity scrubbing that has been suspended.
aggr scrub start [ aggrname | plexname | groupname ]
开始于名为在线总平价擦洗。 奇偶擦洗比较数据磁盘的奇偶校验磁盘（在他们的RAID组），在必要时纠正奇偶校验磁盘的内容。 如果没有名字，便开始平价洗涤是所有在线聚合。 如果给出一个总的名称，洗涤启动从总体上所载的所有RAID组。 如果一丛名字，便开始洗刷是在丛所载的所有RAID组。
aggr擦洗地位 [aggrname | plexname | 群组名称 ] [- v]将
打印上的平等洗涤命名的总和，丛，或团体的地位，所有RAID组目前正在平价擦洗如果没有名字给出。 该状态包括一个完成百分比和灌木丛的暂停状态。
使用- v标志显示的日期和时间的最后完成全部擦洗或团体一起现状等命名的总和，丛;所有RAID组的名称，如果没有给出。
aggr擦洗停止 [aggrname | plexname | 群组名称 ]
停止对已命名的总和，丛，或团体平价擦洗;若没有名字，便在所有的RAID目前正经历一个平价洗涤集团。
aggr擦洗暂停 [aggrname | plexname | 群组名称 ]
暂停对已命名的总和，丛，或团体平价擦洗;若没有名字，便在所有的RAID组目前正在平价擦洗。
aggr show_space [- H的|介电|米| -克| -吨| - b]并<aggrname>
显示在聚合空间使用情况。 不同自由度，此命令显示每个灵活的聚合空间使用量下，如果aggrname指定，aggr show_space只运行在相应的总和，否则空间使用情况报告的聚集所有。
据报道在所有大小1024字节的块，除非另有要求用 K之一- H和-，-米，- g或- t选项。 的- k，-米，- G和- t选项规模的每个输出的大小，将在相关领域表示千字节，兆字节，千兆字节或万亿字节分别。
下面的术语是使用在航天司令部汇报。
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 ]
显示一个或全部聚集在菲勒地位。 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
Jul 7
cf nfo [ enable | disable ] disk_shelf
cf nfo status
The cf command is available only if your filer has the cluster license.
partner giveback incomplete, some data may be lost
forcetakeover [-f] forcetakeover 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.
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).
Jul 7
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
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.
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 0×25a00 on drive 0a.0:1: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 0123456789abcdef —-++————————————————++—————- 0000 0a 19 12 00 19 0f 00 01 00 64 00 00 00 00 00 00 ………d…… 0010 a1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ……………. 0020 00 00 00 00 5a 44 5a 44 00 10 00 00 00 00 01 b0 ….ZDZD…….. 0030 20 04 00 10 20 05 00 01 20 06 00 02 20 07 00 13 … … … … 0040 fc ef 00 00 fc b1 20 80 fc d0 20 80 4a 63 c0 55 …… … .Jc.U [etc.] bootfs fdisk 0a.0 30
The format subcommand formats a drive to the FAT file system standard. A drive must be formatted before it can store files.
bootfs format 0a.0:1: NETAPP
The info subcommand prints information about a disk. The location of various elements and sizes of sections is displayed.
bootfs info 0a.0
——————————————————————– partition: 1 2 3 4 ——————————————————————– file system: 0×01 0×01 0×01 0×01 bytes per cluster: 4096 4096 4096 4096 number of clusters: 2809 2809 2042 251 total bytes: 11534336 11534336 8388608 1048576 usable bytes: 11501568 11501568 8359936 1024000 free bytes: 11505664 11505664 8364032 1028096 FAT location: 512 512 512 512 root location: 9728 9728 6656 1536 data location: 26112 26112 23040 17920
bootfs test -v 0a.0
Jul 7
Copyright © 1994-2008 NetApp, Inc. Legal Information
Jul 7
bmc reboot
bmc setup
bmc status
bmc test autosupport
might produce:
Baseboard Management Controller: Firmware Version: 1.0 IPMI version: 2.0 DHCP: on BMC MAC address: 00:a0:98:05:2b:4a IP address: 10.98.144.170 IP mask: 255.255.255.0 Gateway IP address: 10.98.144.1 BMC ARP interval: 10 seconds BMC has user: naroot ASUP enabled: on ASUP mailhost: mailhost@netapp.com ASUP from: postmaster@netapp.com ASUP recipients: dl-qa-autosupport@netapp.com
Copyright © 1994-2008 NetApp, Inc. Legal Information
Jul 7
The following are the events filer monitors:
Start_logging Logging begins.
TYPE TIME_STAMP IDENTIFIER EVENT (EVENT_INFO)
dmp Thu Apr 5 18:54:56 PDT 2001 /vol/vol0/ home(5) Start (level 0, NDMP)
In the particular example:
The registry option backup.log.enable controls the enabling and disabling of the logging with values on and off respectively. The functionality is enabled by default. (See options for how to set options.)
Jul 7
backup terminate <ID>
A backup job runs on a filer as a process that copies a file system or a subset of it to secondary media, usually tapes. Data can be restored from the secondary media in case the original copy is lost. There are several types of backup processes that run on the filers:
ID State Type Device Start Date Level Path — ———– —- —— ———— —– ————— 0 ACTIVE NDMP urst0a Nov 28 00:22 0 /vol/vol0/ 1 RESTARTABLE dump Nov 29 00:22 1 /vol/vol1/
backup terminate <ID>
A RESTARTABLE dump, though not actively running, retains a snapshot and other file system resources. To release the resources, user can explicitly terminate a RESTARTABLE dump. Once terminated, it cannot be restarted again.
Jul 7
If SMTP is used then the autosupport mechanism contacts a mail host that is listening on the SMTP port (25) to send email. A list of up to 5 mailhosts can be specified by using the autosupport.mailhosts option, and they will be accessed in the order specified until one of them answers as a mailhost. It will then send email through the successful mailhost connection to the destination email address specified in the autosupport.to option. Note that the autosupport.to option only allows 5 email address. To send to more than 5 recipients, create a local alias, or distribution list, and add that as the recipient.
If autosupport.support.enable is on then a copy of the autosupport message is also sent to Network Appliance as follows:
If autosupport.support.transport is smtp then the copy of the autosupport is emailed to the destination specified in autosupport.support.to and the same mailhost picking algorithm is used as above.
If autosupport.support.transport is http then a direct connection to the location specified in autosupport.support.url is made and the autosupport is transmitted to Network Appliance via HTTP POST.
The autosupport mechanism is triggered automatically once a week by the kernel to send information before backing up the messages file. It can also be invoked to send the information through the options command. Autosupport mail will also be sent on events that require corrective action from the System Administrator. And finally, the autosupport mechanism will send notification upon system reboot from disk.
To accommodate multiple delivery methods and destinations and to preserve time dependent values, the outgoing autosupport messages are now spooled in /etc/log/autosupport . Autosupport processing will attempt to deliver all (currently undelivered) messages until the autosupport.retry.count has been reached or until subsequent autosupport messages "fill the spool" such that the oldest (undelivered) messages are forced to be dropped. The spool size is currently 40 messages.
The subject line of the mail sent by the autosupport mechanism contains a text string to identify the reason for the notification. The subject also contains a relative prioritization of the message, using syslog severity levels from DEBUG to EMERGENCY (see syslog.conf ). The messages and other information in the notification should be used to check on the problem being reported.
The setup command tries to configure autosupport as follows:
If a mailhost is specified, it adds an entry for mailhost to the /etc/hosts file.
Setup also queries for autosupport.from information.
autosupport.cifs.verbose
If on , includes CIFS session and share information in autosupport messages. If off , those sections are omitted. The default is off .
autosupport.content
The type of content that the autosupport notification should contain. Allowable values are complete and minimal . The default value is complete . The minimal option allows the delivery of a "sanitized" and smaller version of the autosupport, at the cost of reduced support from Network Appliance. Please contact Network Appliance if you feel you need to use the minimal option. The complete option is the traditional (and default) form of autosupport. If this option is changed from complete to minimal then all previous and pending autosupport messages will be deleted under the assumption that complete messages should not be transmitted.
autosupport.doit
Triggers the autosupport daemon to send an autosupport notification immediately. A text word entered as the option is sent in the notification subject line and should be used to explain the reason for the notification.
autosupport.enable
Enables/disables the autosupport notification features (see autosupport ). The default is on to cause autosupport notifications to be sent. This option will override the autosupport.support.enable option.
autosupport.from
Defines the user to be designated as the sender of the notification. The default is postmaster@your.domain . Email replies from Network Appliance will be sent to this address.
autosupport.local.nht_data.enable
Enables/disables the NHT data autosupport to be sent to the recipients listed in the autosupport.to option. NHT data is the binary, internal log data from each disk drive, and in general, is not parsable by other than Network Appliance. There is no customer data in the NHT autosupport. The default for this option is off .
autosupport.local.performance_data.enable
Enables/disables performance data autosupport to be sent to the recipients listed in autosupport.to . The performance autosupport contains hourly samples of system performance counters, and in general is only useful to Network Appliance. The default is off .
autosupport.mailhost
Defines the list of up to 5 mailhost names. Enter the host names as a comma-separated list with no spaces in between. The default is an empty list.
autosupport.minimal.subject.id
Defines the type of string that is used in the identification portion of the subject line when autosupport.content is set to minimal . Allowable values are systemid and hostname . The default is systemid .
autosupport.noteto
Defines the list of recipients for the autosupport short note email. Up to 5 mail addresses are allowed. Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list to disable short note emails.
autosupport.nht_data.enable
Enables/disables the generation of the Health Trigger (NHT) data autosupport. Default is off
autosupport.performance_data.enable
Enables/disables hourly sampling of system performance data, and weekly creation of a performance data autosupport. The default is on .
autosupport.retry.count
Number of times to try resending the mail before giving up and dropping the mail. Minimum is 5; maximum is 4294967295 ; The default is 15 .
autosupport.retry.interval
Time in minutes to delay before trying to send the autosupport again. Minimum is 30 seconds, maximum is 1 day. Values may end with `s', `m' or `h' to indicate seconds, minutes or hours respectively, if no units are specified than input is
assumed to be in seconds. The default value is 4m .
autosupport.support.enable
Enables/disables the autosupport notification to Network Appliance The default is on to cause autosupport notifications to be sent directly to Network Appliance as described by the autosupport.support.transport option. This option is superceded (overridden) by the value of autosupport.enable .
autosupport.support.proxy
Allows the setting of an http based proxy if autosupport.support.transport is https or http . The default
for this option is the empty string, implying no proxy is necessary.
autosupport.support.to
This option is read only; it shows where autosupport notifications to Network Appliance are sent if autosupport.support.transport is smtp .
autosupport.support.transport
Allows setting the type of delivery desired for autosupport notifications that are destined for Network Appliance. Allowed values are https , http (for direct web based posting) or smtp (for traditional email). The default value is https . Note that http and https may (depending on local network configuration) require that the autosupport.support.proxy option be set correctly. Also smtp requires that autosupport.mailhosts be configured correctly before autosupport delivery can be successful.
autosupport.support.url
This option is read only; it shows where autosupport notifications to Network Appliance are sent if autosupport.support.transport is https or http .
autosupport.throttle
Enables autosupport throttling (see autosupport ). When too many autosupports are sent in too short a time, additional messages of the same type will be dropped. Valid values for this option are on or off . The default value for this option is on .
autosupport.to
Defines the list of recipients for the autosupport email notification. Up to 5 mail addresses are allowed. Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list. Note that it is no longer necessary to use the standard Network Appliance autosupport email address in this field to direct autosupport messages to Network Appliance. Please use autosupport.support.enable instead.
Generation date and timestamp
Software Version
System ID
主机名
SNMP contact name (if specified)
SNMP location (if specified)
Partner System ID (if clustered)
Partner Hostname (if clustered)
Cluster Node Status (if clustered)
Console language type
sysconfig -a output
sysconfig -c output
sysconfig -d output
System Serial Number
Software Licenses (scrambled prior to transmission)
Option settings
availtime output
cf monitor all output (if clustered)
ic stats performance output (if clustered with VIA)
ic stats error -v output (if clustered with VIA)
snet stats -v output (if clustered with SNET)
ifconfig -a output
ifstat -a output
vlan stat output
vif status output
nis info output
nfsstat -c output (if licensed)
cifs stat output (if licensed)
cifs sessions summary (if licensed)
cifs sessions output (if licensed and enabled)
cifs shares summary (if licensed)
cifs shares output (if licensed and enabled)
vol status -l (if cifs is licensed)
httpstat output
vfiler status -a output (if licensed)
df output
df -i output
snap sched output
vol status -v output
vol status output
vol status -c output
vol scrub status -v output
sysconfig -r output
fcstat fcal_stats output
fcstat device_map output
fcstat link_stats output
ECC Memory Scrubber Statistics
ems event status output
ems log status output
registry values
perf report -t output
storage show adapter -a output
storage show hub -a output
storage show disk -a output
storage show fabric output
storage show switch output
storage show port output
EMS log file (if enabled)
/etc/messages content
Parity Inconsistancy information
WAFL_check logs
BATTERY_LOW!!!
LOG_ALERT
BMC_EVENT: BUS ERROR
LOG_ERR
BMC_EVENT: POST ERROR
LOG_ERR
CPU FAN WARNING - [fan]
LOG_WARNING
DISK_FAIL!!! - Bypassed by ESH
LOG_ALERT
DISK_FAIL!!!
LOG_ALERT
DISK_FAILURE_PREDICTED!!!
LOG_ALERT
DISK_FIRMWARE_NEEDED_UPDATE!!!
LOG_EMERG
FC-AL LINK_FAILURE!!!
LOG_ERR
OVER_TEMPERATURE_WARNING!!!
LOG_EMERG
PARTNER DOWN, TAKEOVER IMPOSSIBLE
LOG_ALERT
REBOOT (after WAFL_check)
LOG_INFO
REBOOT (after entering firmware)
LOG_INFO
REBOOT (after giveback)
LOG_INFO
REBOOT (halt command)
LOG_INFO
REBOOT (internal halt)
LOG_INFO
REBOOT (internal reboot)
LOG_INFO
REBOOT (panic)
LOG_CRIT
REBOOT (power glitch)
LOG_INFO
REBOOT (power on)
LOG_INFO
REBOOT (reboot command)
LOG_INFO
REBOOT (watchdog reset)
LOG_CRIT
UNDER_TEMPERATURE_WARNING!!!
LOG_EMERG
USER_TRIGGERED ([user input from autosupport.doit]) LOG_INFO
WAFL_check!!!
LOG_ALERT
[fan] FAN_FAIL!!!
LOG_ALERT
[mini core]
LOG_CRIT
[power supply failure]
LOG_ALERT
[power supply] POWER_SUPPLY_DEGRADED!!!
LOG_ALERT
[shelf over temperature critical]
LOG_EMERG
The subject in the autosupport email messages from a filer in a cluster reads, “Cluster notification, ” instead of “System notification.”
The autosupport email messages from a filer in a cluster contains information about its partner, such as the partner system ID and the partner host name.
In takeover mode, if you reboot the live filer, two autosupport email messages notify the email recipients of the reboot: one is from the live filer and one is from the failed filer.
The live filer sends an autosupport email message after it finishes the takeover process.
Jul 7
<logdir> is /etc/log for filers and /logs for NetCache appliances.
Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:OUT:date: Wed Feb 9 17:34:09 GMT 2000
This indicates that there was an rsh session around Wed Feb 9 17:34:09 GMT which caused the date command to be executed. The user performing the command was root. The type of log is data output by the system as indicated by the OUT keyword.
Commands typed at the filer's console or executed by rsh are designated by the IN keyword as in:
Wed Feb 9 17:34:03 GMT [rshd_0:auditlog]: :IN:rsh shell: RSH INPUT COMMAND is date
The start and end of an rsh session are specially demarcated as in
Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:START:rsh shell:orbit.eng.mycompany.com
和
Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:END:rsh shell:
The maximum size of the auditlog file is controlled by the auditlog.max_file_size option. If the file gets to this size, it is rotated (see below).
Every Saturday at 24:00, <logdir>/auditlog is moved to <logdir>/auditlog.0, <logdir>/auditlog.0 is moved to <logdir>/auditlog.1 , and so on. This process is called rotation. Auditlog files are saved for a total of six weeks, if they do not overflow.
If you want to forward audit log messages to a remote syslog log host (one that accepts syslog messages via the BSD Syslog protocol specified in RFC 3164), modify the filer's /etc/syslog.conf file to forward messages from the filer's "local7" facility to the remote host. Do this by adding a line like:
On the log host, you'll need to modify the syslog daemon's configuration file to redirect syslog message traffic from the "local7" facility to the appropriate configuration file. That is typically done by adding a line similar to the one shown above for the filer:
You are currently browsing the archives for the Manual Pages category.
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
 |  |  |  |  |  |  |
Bad Behavior has blocked 584 access attempts in the last 7 days.
© 2009-2010 Chris Kranz All Rights Reserved
这个网站是不隶属于或赞助反正由NetApp或任何其他公司提到内英寸