NETAPP在域用户下HOMEDIR的配置方法
NetApp存储设备安装配置手册
NetApp存储设备配置说明修改记录目录1编写目的 (1)2专业名词和缩略语 (2)3组网方式和环境介绍 (3)4安装配置方法 (3)4.1N ET A PP硬件安装 (3)4.2设备初始化和系统设定 (4)4.2.1设备初始化 (4)4.2.2系统设定 (4)4.3操作系统安装 (6)4.3.1注册现有系统的cifs服务，将操作系统文件上传至FAS存储系统 (6)4.4应用配置 (8)4.4.1系统参数配置 (8)4.4.2注册需要使用的服务 (10)4.4.3创建一个卷并输出空间 (12)4.4.4创建一个Qtree并实施quota限制 (17)4.4.5配置autosupport (19)4.4.6配置snapshot策略及数据恢复方法 (19)4.4.7磁盘故障的数据恢复方法 (19)4.4.8配置Cluster (19)1 编写目的编写本文档的目的在于详细地说明NetApp FAS存储系统的安装、配置以及常用命令的介绍和可靠性维护、故障检查与恢复的方法，便于开发、测试、用服和工程维护人员安装、使用和维护NetApp FAS存储系统存储系统。
2 专业名词和缩略语3 组网方式和环境介绍NetAppFAS3240AESX ServerSWITCHESX Server图3.1 NetApp FAS存储系统组网结构NetApp FAS存储系统存储设备以NAS存储方式使用，通过万兆交换机与主机相连接。
4 安装配置方法4.1 NetApp硬件安装存储设备硬件的安装主要是各盘柜间线缆的连接、磁盘安装、盘柜上架、上电等，以上操作多由NetApp技术支持工程师完成。
使用存储设备随机携带的“DB－9 to RJ－45”转接线将FAS存储系统的CONSOLE端口和安装了WINDOWS操作系统的主机串口相连，在WINDOWS主机上安装SecureCRT软件，新建一个serial协议的连接，其中port参数根据所连接的是COM1还是COM2来进行选择，其余参数参考图4.1所示，通过串口连接登录到FAS存储系统。
nas配置向导
目录1 设备信息 (2)2 硬件实施…………………………………………………………………………………错误！未定义书签。
3 存储系统配置过程………………………………………………………………………错误！未定义书签。
4 IBM NAS的存储配置 (7)4.1 增加卷 (7)4.2 建立Qtree .................................. (10)4.3 建立Share并配置权限.................................. (112)4.4 使用IBM实现用户homedir的配置 (14)4.5 创建新用户目录，并更改NTFS权限设置 (16)4.6 配置HOME目录.................................. . (27)4.7 检查共享权限.................................. (301)5 挂接HOME DIRECTORY.................................. (332)5.1 永久挂接.................................. (332)5.2 临时挂接.................................. (334)6 授权目录给其他用户.................................. (345)6.1 其他用户如何使用授权目录 (385)7 授权文件给其他用户.................................. (41)7.1 其他用户如何使用授权文件 (41)8 snapvault实施步骤 (48)1设备信息两台IBM N系列网络存储：N3300和N3600。
2硬件实施(1)拆箱验货。
(2)主机上架。
(3)存储加电自检。
(4)存储系统配置。
3存储系统配置过程一、两台主机已经预装操作系统，加电自检完毕。
NETAPP存储防火墙端口-典型NAS环境下的网络需求
网络需求所有需要执行SnapMirror数据复制的存储之间，需打开以下端口：NetApp FAS存储支持通过网络同步时钟。
如果存储和NTP服务器之间有防火墙，则打开以下端口：所有被管理的存储，必须通过IP网络与DFM服务器连通。
如果存储和DFM服务器之间有防火墙，则打开以下端口：如果有Windows机器需要管理（例如，客户端安装了OSSV备份软件），则Windows机器需要通过IP网络与DFM服务器连通。
如果Windows机器和DFM服务器之间有防火墙，则打开以下端口：启用DFM的autosupport功能，需要DFM服务器和邮件服务器连通；并且服务器需要一个不需密码验证的发送邮件的账号。
如果邮件服务器和DFM服务器之间有防火墙，则打开以下端口：附录：DOT 7.2使用的IP端口IP port usage on a storage systemAbout this appendixThis appendix describes the Data ONTAP services file that is available in the /etc directory. The /etc/services file is in the same format as its corresponding UNIX systems /etc/services file. Although this file is it not used by Data ONTAP, it is provided in this appendix as information useful to system administrators. Host identificationAlthough some port scanners are able to identify storage systems as storage systems, others port scanners report storage systems as unknown types, UNIX systems because of their NFS support, or Windows systems because of their CIFS support. There are several services that are not currently listed in the /etc/services file.Below is an example of a complete list of the file contents./etc/services NNTP and TTCP portsThe nntp and ttcp ports are unused by your storage system and should never be detected by a port scanner.Ports found in a block starting around 600The following ports are found on the storage system with NFS enabled:On other systems, the ports appear as follows:Enter the following command on UNIX systems to obtain the correct information by querying the port mapper on port 111:toaster# rpcinfo -p .or.ip.address program vers proto port service100011 1 udp 608 rquotad100021 4 tcp 607 nlockmgr100021 3 tcp 607 nlockmgr100021 1 tcp 607 nlockmgr100021 4 udp 606 nlockmgr100021 3 udp 606 nlockmgr100021 1 udp 606 nlockmgr100024 1 tcp 605 status100024 1 udp 604 status100005 3 tcp 603 mountd100005 2 tcp 603 mountd100005 1 tcp 603 mountd100005 3 udp 602 mountd100005 2 udp 602 mountd100005 1 udp 602 mountd100003 3 udp 2049 nfs100003 2 udp 2049 nfs100000 2 tcp 111 rpcbind100000 2 udp 111 rpcbindNoteThe port numbers listed for mountd, statd, lockd, and quotad are not committed port numbers. Storage systems can have these services running on other port numbers. Because the system selects these port numbers at random when it boots, they are not listed in the /etc/services file.Other ports not listed in /etc/servicesThe following ports appear in a port scan but are not listed in /etc/services file.NoteDisable open ports that you do not need.FTP•ftp-data•ftpFile transfer protocol (FTP) uses TCP ports 20 and 21. For a detailed description of the FTP support for your storage system, see the Data ONTAP File Access and Protocols Management Guide. If you use FTP to transfer filesto and from your storage system, the FTP port is required; otherwise, use FilerView or the following CLI command to disable the FTP port:options ftpd.enable offFTP is not a secure protocol for two reasons:•When users log in to the system, user names and passwords are transmitted over the network in clear text format that can easily be read by a packet sniffer program.These user names and passwords can then be used to access data and other network resources. You should establish and enforce policies that prevent the use of the same passwords to access storage systems and other network resources.•FTP server software used on platforms other than storage systems contains serious security-related flaws that allow unauthorized users to gain administrative (root) access and control over the host.SSH•sshSecure Shell (SSH) protocol is a secure replacement for RSH and runs on TCP port 22. This only appears in a port scan if the SecureAdmin TM software is installed on your storage system.There are three commonly deployed versions of the SSH protocol:•SSH version 1--is much more secure than RSH or Telnet, but is vulnerable to TCP session attacks.This vulnerability to attack lies in the SSH protocol version 1 itself andnot in the associated storage system products.•SSH version 2--has a number of feature improvements over SSH version 1 and is less vulnerable to attacks.•SSH version 1.5--is used to identify clients or servers that support both SSH versions 1 and 2.To disable SSH support or to close TCP port 22, use the following CLI command:secureadmin disable sshTelnet•telnetTelnet is used for administrative control of your storage system and uses TCP connections on port 23. Telnet is more secure than RSH, as secure as FTP, and less secure than SSH or Secure Socket Layer (SSL).Telnet is not secure because:•When users log into a system, such as your storage system, user names and passwords are transmitted over the network in clear text format.Clear text format can be read by an attacker using a packet snifferprogram. The attacker can use these user names and passwords to log in to your storage system and execute unauthorized administrativefunctions, including destruction of data on the system. If theadministrators use the same passwords on your storage system as they do on other network devices, the attacker can use these passwords toaccess those resources as well.NoteTo reduce the potential for attack, establish and enforce policiespreventing administrators from using the same passwords on yourstorage system that they use for access to other network resources.•Telnet server software used on other platforms (typically in UNIX environments) have serious security-related flaws that allow unauthorized users to gain administrative (root) control over the host.Telnet is also vulnerable to the same type of TCP session attacks as SSH protocol version 1, but because a packet sniffing attack is easier, TCP session attacks are less common.To disable Telnet, set options telnet.enable to off.SMTP•smtpThe Simple Mail Transport Protocol (SMTP) uses TCP port 25. Your storage system does not listen on this port but makes outgoing connections to mail servers using this protocol when sending AutoSupport e-mail.Time service•time•ntpYour storage system supports two different time service protocols:•TIME protocol (also known as rdate) is specified in the RFC 868 standard. This standard allows for time services to be provided on TCP or UDP port 37. Your storage systemuses only UDP port 37.•Simple network time protocol (NTP) is specified in the RFC 2030 standard and is provided only on UDP port 123.When your storage system has option timed.enable set to On and a remote protocol (rdate or ntp) is specified, the storage system synchronizes to a network time server.If the timed.enable option is set to Off, your storage system is unable to synchronize with the network time server using NTP. The rdate time protocol can still be used by manually issuing the rdate command from your storage system console.You should set the timed.enable option to On in a cluster configuration. DNS•domainThe Domain Name Service (DNS) uses UDP port 53 and TCP port 53. Your storage system does not typically listen on these ports because it does not run a domain name server. However, if DNS is enabled on your storage system, it makes outgoing connections using UDP port 53 for host name and IP address lookups. Your storage system never uses TCP port 53 because this port is used explicitly for communication between DNS servers. Outgoing DNS queries by your storage system are disabled by turning off DNS support. Turning off DNS support protects against receiving bad information from another DNS server.Because your storage system does not run a domain name server, the name service must be provided by one of the following:•Network information service (NIS)•An/etc/hosts file•Replacement of host names in the configuration files (such as /etc/exports, /etc/usermap.cfg, and so on) with IP addressesDNS must be enabled for participation in an Active Directory domain. DHCP•dhcpsClients broadcast messages to the entire network on UDP port 67 and receive responses from the Dynamic Host Configuration Protocol (DHCP) server on UDP port 68. The same ports are used for the BOOTP protocol.DHCP is used only for the first-time setup of your storage system. Detection of DHCP activity on your storage system by a port scan other than the activity during the first-time setup indicates a serious configuration or software error. TFTP•tftpTrivial File Transfer Protocol (TFTP) uses TCP port 69. It is used mostly for booting UNIX or UNIX-like systems that do not have a local disk (this process is also known as netbooting) and for storing and retrieving configuration files for devices such as Cisco routers and switches.Transfers are not secure on TFTP because it does not require authentication for clients to connect and transfer files.Your storage system's TFTP server is not enabled by default. When TFTP is enabled, the administrator must specify a directory to be used by TFTP clients, and these clients cannot access other directories. Even within the TFTP directory, access is read-only. TFTP should be enabled only if necessary. Disable TFTP using the following option:options tftpd.enable offHTTP•httpHypertext Transport Protocol (HTTP) runs on TCP port 80 and is the protocol used by web browsers to access web pages. Your storage system uses HTTP to access•Files when the HTTP protocol is enabled•FilerView for Graphical User Interface (GUI) administration•Secure FilerView when SecureAdmin is installedThe SecureAdmin SSL interface accepts connections on TCP port 443. SecureAdmin manages the details of the SSL network protocol, encrypts the connection, and then passes this traffic through to the normal HTTP FilerView interface through a loopback connection. This loopback connection does not use a physical network interface. HTTP communication takes place inside your storage system, and no clear text packets are transmitted.The HTTP protocol is not vulnerable to security attacks because it provides read-only access to documents by unauthenticated clients. Although authentication is not typically used for file access, it is frequently used for access to restricted documents or for administration purposes, such as FilerView administration. The only authentication methods defined by the HTTP protocol send credentials, such as user names and passwords, over the network without encryption. The SecureAdmin product is provided with SSL support to overcome this shortcoming.NoteIn versions of Data ONTAP earlier than 7.0, your storage system listens for new connections (by default, set to TCP port 80) even when the HTTP protocol is not licensed and FilerView is disabled. However, starting with Data ONTAP 7.0, you can stop your storage system from listening for new connections by setting the options httpd.enable and httpd.admin.enable to Off. If either of the options is set to On, your storage system will continue to listen for new connections.Kerberos•kerberos•kerberos-secThere are four Kerberos ports in the /etc/services file: TCP port 88, UDP port 88, TCP port 750, and UDP port 750. These ports are used only for outbound connections from your storage system. Your storage system does not run Kerberos servers or services and does not listen on these ports.Kerberos is used by your storage system to communicate with the Microsoft Active Directory servers for both CIFS authentication and, if configured, NFS authentication.NFS•portmap•nfsdThe Network File System (NFS) is used by UNIX clients for file access. NFS uses port 2049.NFSv3 and NFSv2 use the portmapper service on TCP or UDP port 111. The portmapper service is consulted to get the port numbers for services used with NFSv3 or NFSv2 protocols such as mountd, statd, and nlm. NFSv4 does not require the portmapper service.NFSv4 provides the delegation feature that enables your storage system to grant local file access to clients. To delegate, your storage system sets up a separate connection to the client and sends callbacks on it. To communicate with the client, your storage system uses one of the reserved ports (port numbers less than 1024). To initiate the connection, the client registers the callback program on a random port and informs the server about it.With delegations enabled, NFSv4 is not firewall friendly because several other ports need to be opened up as well.You can disable the TCP and UDP ports by setting the nfs.tcp.enable and nfs.udp.enable options to Off.To disable NFS, use the nfs off command.CIFS•netbios-name•netbios-dg•netbios-ssn•cifs-tcpThe Common Internet File Service (CIFS) is the successor to the server message block (SMB) protocol. CIFS is the primary protocol used by Windows systems for file sharing.CIFS uses UDP ports 137 and 138, and TCP ports 139 and 445. Your storage system sends and receives data on these ports while providing CIFS service. If it is a member of an Active Directory domain, your storage system also must make outbound connections destined for DNS and Kerberos.CIFS is required for Windows file service. You can disable CIFS using FilerView or by issuing the cifs terminate command on your storage system console.NoteIf you disable CIFS, be aware that your storage system's /etc/rc file can be set up to automatically enable CIFS again after a reboot.SSL•sslThe Secure Sockets Layer (SSL) protocol provides encryption and authentication of TCP connections.When SecureAdmin is installed and configured on your storage system, it listens for SSL connections on TCP port 443. It receives secure web browser connections on this port and uses unencrypted HTTP through a loopback connection to pass the traffic to FilerView, running on TCP port 80. This loopback connection is contained within your storage system and no unencrypted data is transmitted over the network.TCP port 443 can be disabled using FilerView or with the following command: secureadmin disable sslSNMP•snmpSimple Network Management Protocol (SNMP) is an industry-standard protocol used for remote monitoring and management of network devices over UDP port 161.SNMP is not secure because•Instead of using encryption keys or a user name and password pair, SNMP uses a community string for authentication. The community string is transmitted in clear textformat over the network, making it easy to capture with a packet sniffer.Within the industry, devices are typically configured at the factory to use public as the default community string. The public password allowsusers to make queries and read values but does not allow users toinvoke commands or change values. Some devices are configured atthe factory to use private as the default community string, allowingusers full read-write access.•Even if you change the read and write community string on a device to something other than private, an attacker can easily learn the new string by using the read-only publiccommunity string and asking the router for the read-write string.There are three versions of SNMP:•SNMPv1 is the original protocol and is not commonly used.•SNMPv2 is identical to SNMPv1 from a network protocol standpoint and is vulnerable to the same security problems. The only differences between the twoversions are in the messages sent, messages received, and the type ofinformation that is available. These differences are not important from a securitypoint of view. This version of SNMP is currently used on your storage systems.•SNMPv3 is the latest protocol version and includes security improvements but is difficult to implement and many vendors do not yet support it. SNMPv3 supportsseveral different types of network encryption and authentication schemes. Itallows for multiple users, each with different permissions, and solves SNMPv1security problems while maintaining an important level of compatibility withSNMPv2.SNMP is required if you want to monitor a storage system through an SNMP monitoring tool, such as DataFabric® Manager. Your storage system's SNMP implementation allows read-only access. Regardless of the community string used, the user cannot issue commands or change variables using SNMP on your storage system.You should use the snmp.access option to restrict SNMP access to a named set of trusted hosts.Set the snmp.enable option to Off to disable SNMP entirely.The snmp community delete and snmp community add commands are used to change the community string to something other than the default value.RSH•shellRemote shell protocol (RSH) is used for remote command execution and is the only protocol supported on your storage system. It is even less secure than TFTP and uses TCP port 514.RSH is not secure because passwords are not required for login and commands are easy to misconfigure. If possible, RSH should be disabled by setting the rsh.enable option to off.You should use the SSH supplied with SecureAdmin for remote command execution and login. If this is not possible, Telnet is preferred to RSH.If RSH is the only alternative, follow these guidelines when using RSH:•Specify only secure, trusted hosts in the /etc/hosts.equiv file.•Always use IP addresses rather than host names in the /etc/hosts.equiv file.•Always specify a single IP address with a single user name on each line in /etc/hosts.equiv file.•Use the rsh.access option instead of the trusted.hosts option for access control.•Make sure the ip.match_any_ifaddr option is set to off.Syslog•syslogYour storage system sends messages to hosts specified by the user in the/etc/syslog.conf file using the syslog protocol on UDP port 514. It does not listen on this port, nor does it act as a syslog server.Routed•routedThe route daemon, routed, listens on UDP port 520. It receives broadcast messages from routers or other hosts using the Routing Information Protocol (RIP). These messages are used by your storage system to update its internal routing tables to determine which network interfaces are optimal for each destination.Your storage system never broadcasts RIP messages containing routes because Data ONTAP is not capable of acting as a router.RIP is not secure because an attacker can easily send artificial RIP messages and cause hosts running the routed daemon (such as your storage system) toredirect network traffic to the attacker. The attacker can then receive and sift this traffic for passwords and other information and send it on to the actual destination, where the intrusion is undetected. This method can also be used as a starting point for TCP session attacks.Because of these security issues, use static routes (those set up using the route command on your storage system) instead of using the routed daemon. NDMP•ndmp•ndmp-localNetwork Data Management Protocol (NDMP) runs on TCP port 10000 and is used primarily for backup of network-attached storage (NAS) devices, such as your storage systems.The protocol defines three authentication methods:•NONE--allows authentication without restriction•TEXT--sends a clear text password over the network, similar to Telnet or FTP•MD5--uses the MD5 message digest algorithm along with a challenge-response message exchange to implement a secure login mechanismYour storage systems support both the TEXT and MD5 authentication methods. Most NDMP-enabled backup software uses MD5 by default.To entirely disable the TEXT authentication method, set thendmpd.authtype option to challenge.To restrict NDMP commands to certain authorized backup hosts, use the ndmp.access option.Regardless of the authentication method used, NDMP sends backup data in unencrypted format over the network, as does most other backup software. A separate network optimized for backup is a common means to increase performance while retaining data security.To disable NDMP, set the ndmp.enable option to off.SnapMirror and SnapVault•snapmirrorSnapMirror and SnapVault use TCP port 10566 for data transfer. Network connections are always initiated by the destination system; that is, SnapMirror and SnapVault pull data rather than push data.Authentication is minimal with both SnapMirror and SnapVault. To restrict inbound TCP connections on port 10566 to a list of authorized hosts or IP addresses, configure the snapmirror.access or snapvault.access option. Once a connection is established, the destination storage system communicates its host name to the source storage system, which then uses this host name to determine if a transfer is allowed. You should confirm a match between the host name and its IP address. To confirm that the host name and the IP address match, set the snapmirror.checkip.enable option to On.To disable SnapMirror, set the snapmirror.enable option to Off. To disable SnapVault, set the snapvault.enable option to Off.。
NetApp配置及维护手册
N e t A p p存储系统配置手册2011NetAppAll rights reserved本文档包含NetApp公司的商业及技术机密。
未经NetApp公司许可，不得向第三方泄漏或使用。
目录1配置指南 (2)1.1NetApp Filer快速入门 (2)1.2开关机 (2)1.2.1开机顺序： (2)1.2.2关机顺序： (2)2NetApp FAS3050/F3050C 系列 (3)2.1机架指示灯 (4)3设备管理 (7)3.1FILERVIEW 图形管理接口 (7)3.2命令行管理接口(CLI) (10)3.3空间管理：Aggr, V olume和qtree的介绍 (10)3.3.1命令行 (11)3.3.2图形界面 (11)3.3.3Qtree security styles的意义 (13)3.4NFS exports (13)3.4.1命令行 (14)3.4.2图形界面 (14)3.5CIFS Shares (15)3.5.1命令行 (15)3.5.2图形界面 (16)3.5.3用windows 2003或windows 2008管理 (17)3.6Snapshot 管理 (17)3.7Lun create (18)3.7.1命令行 (18)3.7.2图形界面 (19)3.8NetApp Filer常用命令 (21)1 配置指南1.1 NetApp Filer快速入门本指南是为初次使用NetApp存储系统的人员编写的，详细的系统描述和管理命令参见随机手册,在线帮助及/. 特别请您访问NOW (NetApp On the Web) site (), 您可从上面获得几乎所有得产品支持信息，如：电子版手册，知识库，软件下载，等等。
1.2 开关机1.2.1 开机顺序：1、先按照磁盘架编号顺序加电磁盘架的双电源；2、10秒钟后加电控制器。
1.2.2 关机顺序：1、确认所有连接的应用程序已经关闭；2、通过串口或TELNET登陆到系统。
NetApp存储安装、配置和维护手册
NETAPP存储系统安装、配置和维护手册文档信息本安装和维护手册为 XXX 定制，为NetApp标准文档之补充。
目录1作业规划步骤 (1)2配置步骤 (3)2.1设置磁盘归属，创建ROOT卷 (3)2.2检查并更新各部件的firmware系统版本 (15)2.3检查并更新存储操作系统版本 (19)2.4输入软件许可 (23)2.5执行SETUP进行初始化设置 (23)2.6调整ROOT卷的大小 (29)2.7配置VLAN (29)2.8修改HOSTS文件 (31)2.9修改/etc/rc文件 (32)2.10配置AutoSupport服务 (33)2.11配置SSH (34)2.12配置SNMP (35)2.13配置NTP (36)2.14配置MTA (37)2.15配置IPspace (37)2.16配置MultiStore (37)2.17配置CIFS (41)2.18配置ISCSI (44)2.19配置FCP (45)2.20配置NFS (46)2.21配置重复数据删除 (47)2.22配置Snaprestore (48)2.23容灾实现Snapmirror (52)3日常维护 (55)3.1正常开关机 (55)3.2维护手段 (55)3.2.1Filerview 图形管理接口 (55)3.2.2命令行(CLI) (57)3.3空间管理：Aggr, Volume和lun的介绍 (57)3.4常用命令基本应用 (58)3.5日常系统检查 (58)3.5.1目测 (58)3.5.2例行系统检查 (58)3.6autosupport功能简介和配置 (59)4故障处理流程 (61)Page II4.1支持方式 (61)4.1.1NetApp on the web (NOW) site和服务 (61)4.1.2GSC( Global Support Center 全球支持中心) (61)4.2案例开立流程 (62)4.3损坏部件更换流程 (62)Page III1 作业规划步骤Page 22 配置步骤配置参数表2.1 设置磁盘归属，创建ROOT卷Page 3Page 4Page 5Page 6Page 7Page 8Page 9Page 10Page 11Page 12Page 13Page 142.2 检查并更新各部件的firmware系统版本Page 15Page 16Page 17Page 182.3 检查并更新存储操作系统版本Page 19Page 20Page 21Page 222.4 输入软件许可使用license add XXXXXXX命令添加许可，全部输入后，使用license命令进行检查。
NetApp操作手册
NetApp FAS系列存储器操作手册目录App存储系统 (3)2.系统基本维护指南 (5)2.1.进入管理界面 (5)2.2.系统基本信息 (6)2.3.系统LOG信息 (7)2.4.配置Autosupport (8)2.5.设置时区、时间和日期 (8)2.6.杂项设置 (9)2.7.停机及重新启动 (10)2.8.管理及创建卷 (11)2.9.管理及创建Qtree (12)2.10.磁盘配额 (13)2.11.SnapShot的配置和管理 (15)2.12.CIFS的相关信息 (17)2.13.CIFS共享 (19)2.14.启用home directory功能 (20)2.15.ISCSI连接Windows (21)2.16.网络端口的管理 (33)2.16.1.VIF Multiple方式绑定,对应Cisco 交换机端配置命令 (34)2.17.其他网络参数 (35)2.18.更改root用户密码 (36)2.19.系统实时状态监控 (37)附录一：磁盘更换步骤 (39)附录二：时间同步服务器的设置 (40)App存储系统NetApp 系统为各种不同平台上的用户提供了对全部企业数据的无缝访问。
NetApp全系列光纤网络存储系统在文件访问方面支持NFS 和CIFS，在块存储访问方面支持FCP 和iSCSI，确保您可以非常方便地将NetApp 存储系统集成到NAS 或SAN 环境中，并且保护原来的信息。
NetApp 的设计为专用访问环境中的应用程序服务器和服务器集群以及多用户环境中的用户提供了经过优化和整合的高性能数据访问方式。
NetApp 存储系统提供了经过实践考验的、超过99.998% 的数据可用性，减少了代价高昂的停机时间（无论是计划内的还是计划外的），最大限度地保障了对关键数据的访问。
它们在一个简单、易用的环境中实现了数据的可管理性、可扩展性、互操作性和可用性，从而降低了您的总拥有成本，加强了竞争优势。
Netapp磁盘阵列的安装与配置
1、安装SANtricity Storage Management软件1) 进入安装页面后，会出现安装目录选择页面，根据需要选择安装目录并点击“Next”，如图所示。
2) 根据用户的环境配置选择安装方式。
推荐使用“Typical”安装模式，单击“Next”进入下一步安装步骤，如图所示。
3)选择自动启动系统监控器，点击“Next”进入下一步安装，如图所示。
4)点击“Next”进入下一步安装，如图所示。
5)点击“Done”完成安装，如图所示。
2、添加磁盘阵列点击“开始”->“程序”->“SANtricity Storage Manager Clinet”,选择“Automatic”，如图所示。
存储阵列出厂默认的双控制器两个网口的IP设置为：192.168.128.101和 192.168.128.102，需要将主机服务器和控制器IP地址设置成同一个网段，通过Out-of-Band以太网带外管理方式，这样才能检测出磁盘阵列。
3、配置卷组和卷单击存储阵列进入Array Management界面，点击菜单项“Storage &Copy Services”，在Total Unconfigured Capacity上右键点击“Create Volume Group”，如图所示。
点击next，输入Volume Group name，如图所示点击next，选择RAID5，如图所示点击Finish，自动进入Create Volume界面，按如图所示进行设置初始化卷，大概需要16分钟左右，如图所示4、定义主机组和主机点击菜单项“Host Mappings”，在Default Group上右键点击Define->Host Group,如图所示输入host group name ，如图所示右键点击Host Group 1->Define->Host，如图所示输入主机名，如图所示点击next，添加wwn号，按如图所示进行设置点击next，选择操作系统，如图所示点击next，单击Finish,选择“No”，如图所示5、添加磁盘阵列映射右键点击Host test1->Add LUN Mapping，如图所示点击Add，按如图所示进行设置完成以上操作后，查看服务管理器中是否能看到新的磁盘，如图所示。
NetApp配置及维护手册
N e t A p p存储系统配置手册2011NetAppAll rights reserved本文档包含NetApp公司的商业及技术机密。
未经NetApp公司许可，不得向第三方泄漏或使用。
目录1配置指南 (2)1.1NetApp Filer快速入门 (2)1.2开关机 (2)1.2.1开机顺序： (2)1.2.2关机顺序： (2)2NetApp FAS3050/F3050C 系列 (3)2.1机架指示灯 (4)3设备管理 (7)3.1FILERVIEW 图形管理接口 (7)3.2命令行管理接口(CLI) (10)3.3空间管理：Aggr, V olume和qtree的介绍 (10)3.3.1命令行 (11)3.3.2图形界面 (11)3.3.3Qtree security styles的意义 (13)3.4NFS exports (13)3.4.1命令行 (14)3.4.2图形界面 (14)3.5CIFS Shares (15)3.5.1命令行 (15)3.5.2图形界面 (16)3.5.3用windows 2003或windows 2008管理 (17)3.6Snapshot 管理 (17)3.7Lun create (18)3.7.1命令行 (18)3.7.2图形界面 (19)3.8NetApp Filer常用命令 (21)1 配置指南1.1 NetApp Filer快速入门本指南是为初次使用NetApp存储系统的人员编写的，详细的系统描述和管理命令参见随机手册,在线帮助及/. 特别请您访问NOW (NetApp On the Web) site (), 您可从上面获得几乎所有得产品支持信息，如：电子版手册，知识库，软件下载，等等。
1.2 开关机1.2.1 开机顺序：1、先按照磁盘架编号顺序加电磁盘架的双电源；2、10秒钟后加电控制器。
1.2.2 关机顺序：1、确认所有连接的应用程序已经关闭；2、通过串口或TELNET登陆到系统。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
NETAPP在域用户下HOMEDIR的配置方法
1. 前期准备工作
2. 域服务器的安装
安装域控制器，设置好DNS等服务。
3. 存储空间的分配
建立HOMEDIR所需要空间的卷
见图中的vol_homedir，建议设置为NTFS的加密样式，
建立HOMEDIR所需要QTREE
见下图中的qtree_homedir
共享该QTREE
注意后面加$，隐藏共享。
4. 存储加入域
5. 时间校对
在加入域的时候要求域成员和域控的时间不能相差超过5分钟，请先加入时间服务器或者将时间调整到一致。
6. 存储上设置DNS
7. 存储加入域控
在配置软件中选择Protocols，再选择CIFS，点击Setup进行加入域，见下图：
完成后的状态：
此时在域控应该可以看到：
8. 存储设置HOME DIR路径点击右下角的EDIT，加入路径。
通过Browse选择路径：
最后Save and Close。
9. 域用户的建立
来到域用户和计算机
10. 在Users里面建立第一个用户pc001，
然后在PC001上点右键，选择属性，找到配置文件选项卡，并在主文件夹处选择
，选择盘符（随意，只要是没有占用的就行）。
在到后面输入\\存储系统名\共享的Qtree名\%username%
示例：\\fas814\qtree_homedir$\%username%
如下图：
路径的未显示部分为
最后点击应用完成。
11. 在Users里面建立第二个用户在用户右键，选择复制。
只需要根据向导输入用户名和密码，配置文件和主文件夹就不用设置了。
12. 共享权限的提高
前面我们对QTREE做的共享是默认共享，现需要把这个共享改成管理员完全控制权限，去掉EVERYONE的权限，保证安全性。
进入域用户和计算机，
找到计算机中的NETAPP存储FAS814，点右建选择管理。
点击左边的共享文件夹，进入共享页面。
在Qtree_homedir$上点击右键，选择属性，删除everyone权限，添加域控管理员权限。
13. 网络映射盘路径修正
修改权限后，原用户配置的网络路径因没有权限不能访问，需要到域用户和计算机中进行修正。
配置文件和主文件夹
一起选中需要修正的用户，点击右键，进入属性，选择配置文件进行修改：
显示如下提示直接关闭，然后取消。
回到客户端登录测试网盘能访问而且自己只能看到自己的网络盘就大功告成了。
14. 用户配置文件
配置文件也可以放到NAS中，看实际情况了，可以做另一个共享并配置如下：
15. 客户端的使用方法
1，直接点击网络驱动器使用；
2，或者直接在地址档输入\\存储名进行访问，用户只能看到自己的个人主目录。
pc001:
pc002:。