Download - HP StorageWorks Clustered File System 3.2.1 CIFS File Serving …h10032. · 3 2 Introduction The HP Clustered File System software provides scalability and high availability for the

*403104-002* *403104–002*

HP StorageWorksClustered File System 3.2.1Windows Storage Server Edition

CIFS File Serving administration guide

Part Number: 403104–002Second edition: February 2006

Legal and notice information© Copyright 1997-2006 Polyserve, Inc.© Portions copyright 2006 Hewlett-Packard Development Company, L.P.Neither PolyServe, Inc. nor Hewlett-Packard Company makes any warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Neither PolyServe nor Hewlett-Packard shall be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided “as is” without warranty of any kind and is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Neither PolyServe nor HP shall be liable for technical or editorial errors or omissions contained herein.PolyServe and the PolyServe logo are trademarks of PolyServe, Inc.PolyServe Matrix Server contains software covered by the following copyrights and subject to the licenses included in the file thirdpartylicense.pdf, which is included in the PolyServe Matrix Server distribution.Copyright © 2000-2003 Microsoft Corporation. All rights reserved.Copyright © 1992, 1993 Simmule Turner and Rich Salz. All rights reserved.Copyright © 1995-2000, GoAhead Software, Inc. All rights reserved.Copyright © 1994-2004, Sun Microsystems, Inc. All rights reserved.The Java 2 Runtime Environment includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/.Copyright © 1999, 2000, 2001 Lev Walkin <[email protected]>. All rights reserved.Copyright © 1996, 1997, 1998, 1999, 2000, 2001 Institut National de Recherche en Informatique et en Automatique (INRIA). All rights reservedCopyright © 1998-2002 The OpenSSL Project. All rights reserved.Copyright © 1995-1998 Eric Young. All rights reserved.Copyright © 1998 John E. Bossom. All rights reserved.Copyright © 1999,2002 Pthreads-win32 contributors. All rights reserved.Copyright © 2000, 2001, 2002 Thomas Heller.Copyright © 2001 Python Software Foundation; All Rights ReservedCopyright © 1993-2001 Spread Concepts LLC. All rights reserved.Copyright © 2001 Daniel Barbalace. All rights reserved.

Copyright © 1989, 1991, 1992 by Carnegie Mellon University. All rights reserved.Copyright © 1996, 1998-2000 The Regents of the University of California. All rights reserved.Copyright © 2001, Networks Associates Technology, Inc. All rights reserved.Copyright © 2001, Cambridge Broadband Ltd. All rights reserved.Copyright © 1996-2003 Printing Communications Assoc., Inc. (PCAUSA). All rights reserved.Copyright © 2003 Storage Networking Industry Association. All rights reserved.Copyright © 1995-2002 Jean-loup Gailly and Mark AdlerHP and the HP logo are trademarks of HP, Inc.Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other company, brand, and product names are trademarks or registered trademarks of their respective companies and are hereby recognized.Linux is a U.S. registered trademark of Linus TorvaldsMicrosoft, Windows, Windows NT, and Windows XP are U.S. registered trademarks of Microsoft Corporation.Oracle® is a registered U.S. trademark of Oracle Corporation, Redwood City, California.UNIX® is a registered trademark of The Open Group.

Clustered File System 3.2.1 Windows Storage Server EditionCIFS File Serving administration guide

iii

Contents

1 HP Technical SupportHP Storage Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1HP NAS Services Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 IntroductionCIFS Virtual Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Cluster File Shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4HP Clustered File System, CIFS File Serving, and Legacy Client

Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Windows Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Linux Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Mac SMB Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 SetupPrerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Configuring HP Clustered Gateway with Cluster File SharesConfiguration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Add a Cluster File Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Configure DFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Setup Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Considerations for Using DFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14DFS Setup on Windows Storage Server 2003 . . . . . . . . . . . . . . . . 15

Other Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Cluster File Shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Cluster File Share Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Contents iv

5 Configuring CIFS with CIFS Virtual ServersConfiguration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Create a CIFS Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Add a Virtual File Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Virtual File Share Advanced Configuration. . . . . . . . . . . . . . . . . . . . 28

Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Linux Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Other Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

CIFS Virtual Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Virtual File Shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Index

1

1

HP Technical Support

Telephone numbers for worldwide technical support are listed on the following HP web site: http://www.hp.com/support. From this web site, select the country of origin. For example, the North American technical support number is 800-633-3600.

NOTE: For continuous quality improvement, calls may be recorded or monitored.

Be sure to have the following information available before calling:

• Technical support registration number (if applicable)

• Product serial numbers

• Product model names and numbers

• Applicable error messages

• Operating system type and revision level

• Detailed, specific questions

HP Storage Web SiteThe HP web site has the latest information on this product, as well as the latest drivers. Access the storage site at: http://www.hp.com/country/us/eng/prodserv/storage.html. From this web site, select the appropriate product or solution.

http://www.hp.com/support

http://www.hp.com/country/us/eng/prodserv/storage.html

Chapter 1: HP Technical Support 2

HP NAS Services Web SiteThe HP NAS Services site allows you to choose from convenient HP Care Pack Services packages or implement a custom support solution delivered by HP ProLiant Storage Server specialists and/or our certified service partners. For more information see us at http://www.hp.com/hps/storage/ns_nas.html.

http://www.hp.com/hps/storage/ns_nas.html

3

2

Introduction

The HP Clustered File System software provides scalability and high availability for the Common Internet FileSystem (CIFS). CIFS is a variation of the Server Message Block (SMB) protocol. It runs over TCP/IP and is commonly used on Windows systems to share files remotely.

CIFS file shares can be deployed in two ways: with CIFS Virtual Servers that provide failover support, or with Cluster File Shares that enable connection load balancing. In both methods, the data to be shared is stored on a PSFS filesystem (not an NTFS filesystem). Note that the PSFS filesystem was built with the Microsoft IFS (installable file system) toolkit, so it appears to be an NTFS filesystem.

CIFS Virtual ServersA CIFS Virtual Server “virtualizes” the network name and IP address associated with a particular CIFS service/share. When a CIFS Virtual Server is created, it is assigned a unique name/IP-address pair. Clients then access the CIFS Virtual Server via this name/IP address pair instead of using the network name and IP address of an actual server.

A CIFS Virtual Server is assigned to a primary node and one or more backup nodes. One or more CIFS file shares are then associated with the CIFS Virtual Server.

HP Clustered File System software provides a monitor for each CIFS file share. This monitor periodically checks the ability of the primary and backup nodes to access the file share. If the primary node fails or loses its

Chapter 2: Introduction 4

connection to the PSFS filesystem, the ClusterPulse process (provided with HP Clustered File System) will fail over, or migrate, the CIFS Virtual Server to one of the backup servers, where it will continue to provide access to the same PSFS filesystem data under the same name/IP-address pair.

This deployment method works well with clients running modern Windows operating systems such as Windows XP and Windows 2000. To take advantage of the transparent failover feature, clients must connect to the CIFS Virtual Server using either the Fully Qualified Domain Name (FQDN) or the IP address. This helps avoid conflicts with legacy (NetBIOS) network-name resolution methods. If NetBIOS name resolution is a requirement, then the Cluster File Share deployment method should be used instead.

Cluster File SharesCluster File Shares are Windows CIFS shares associated with an HP Clustered File System health monitor. Clients connect to Cluster File Shares using the network name or IP address of any physical (rather than virtual) server in the cluster. Each node in the cluster provides access to the same PSFS filesystems through its Cluster File Shares.

For high availability, Cluster File Shares are designed to be deployed with a connection-oriented load balancer such as the Microsoft Distributed File System (DFS). When deployed with a DFS front end, client connection requests to a single network name (provided by DFS) will be evenly distributed among the nodes in the cluster. On failure of a node, DFS will detect the loss of network connectivity and route new connection and re-connection requests to the remaining nodes in the cluster.

If a node in the cluster loses access to the PSFS filesystem (for example, because of a SAN problem) but it is otherwise healthy, the Cluster File Share monitor will tear down the associated CIFS share to prevent future connection and re-connection requests from being directed to a node that has lost access to the underlying shared filesystem.

When the node regains access to the shared filesystem, the Cluster File Share monitor automatically recreates the CIFS share and the node then starts handling requests.


HP Clustered File System, CIFS File Serving, and Legacy Client Operating SystemsSeveral legacy client operating systems do not support the modern networking infrastructure required to connect to a virtualized network connection such as that provided by the HP Clustered File System CIFS Virtual Server. These operating systems include Windows NT4, Windows ME, Windows 98, Windows 95, Windows 3.1, DOS, MAC SMB client, and some Linux versions. To support connectivity with these legacy clients, HP Clustered File System should be deployed with Cluster File Shares, plus DFS for connection load balancing and failover.

Many of these clients support the DFS interface; however, some of the operating systems (namely Windows 95/98/ME/NT4, Mac SMB clients, and Linux) require a software update to interoperate with DFS.

Windows ClientsThe following Microsoft Knowledge Base articles contain information about the Windows clients.

Windows 95/NT. The Windows 2000 AD/DFS client is recommended. See Microsoft Knowledge Base article 288358 for more information.

Windows 98/ME. The DS2003 client is recommended. A hotfix for Windows 98 is also needed. http://support.microsoft.com/default.aspx?scid=kb;en-us;555038

The following article regarding Windows ME may also be of interest.

http://support.microsoft.com/default.aspx?scid=kb;en-us;276472

Note that DOS and Windows 3.1 do not support DFS. While these clients can connect directly to Cluster File Shares, they cannot take advantage of the high availability and load balancing features provided by the Cluster File Shares/DFS deployment model.




Linux ClientsA software update for Linux is available at the following location:

http://us1.samba.org/samba/Linux_CIFS_client.html

A Linux client implemented in Java is available at this location:

http://jcifs.samba.org/

In addition to interoperating with DFS, Linux clients can also connect directly to Virtual File Shares. (See “Linux Clients” on page 32 for more information.)

NOTE: The following tool can be helpful for Linux clients that need to handle Windows DACLs on PSFS filesystems:

http://www.samba.org/samba/docs/man/manpages-3/smbcacls.1.html

Mac SMB ClientsA software update for Mac SMB clients is available at the following location:

http://www.admitmac.com

Name ResolutionCIFS Virtual Server deployments work with FQDN (DNS resolution) or IP address, but do not work with NetBIOS name resolution of non-qualified NetBIOS names (including WINS and NetBT broadcasts).If clients will be using non-qualified NetBIOS names, you must use Cluster File Shares and DFS load balancing for high availability, instead of the CIFS Virtual Server deployment method.

NOTE: By default, NetBIOS name resolution order is used on clients if the name does not contain a dot. If the name does contain a dot, hostname resolution order is used. Also, if DNS resolution fails because of improper network or DNS setup, during host name resolution the client will resort to NetBIOS name resolution methods including WINS and NetBT broadcasts, which could result in incorrect name resolution for VFS names.

http://www.admitmac.com

http://us1.samba.org/samba/Linux_CIFS_client.html

http://jcifs.samba.org/

http://www.samba.org/samba/docs/man/manpages-3/smbcacls.1.html

Copyright © 1999-2005 PolyServe, Inc. All rights reserved. 7

3

Setup

Prerequisites Before creating CIFS files, create PSFS cluster filesystems to store the files that will be shared via CIFS. For each filesystem, assign a drive letter or path that will be used to access the filesystem. See the HP StorageWorks Clustered File System Administration Guide for details about creating and configuring filesystems.

SecurityTo provide security protection across the cluster, we recommend that all nodes in the cluster participate in the same domain.


4

Configuring HP ClusteredGateway with Cluster File Shares

Configuration OverviewCluster File Shares are Windows CIFS shares associated with an HP Clustered File System health monitor. Clients connect to Cluster File Shares using the network name or IP address of any physical server in the cluster. Each node in the cluster provides access to the same PSFS filesystems through its Cluster File Shares.

For high availability, Cluster File Shares can be deployed with a connection-oriented load balancer such as the Microsoft Distributed File System (DFS). Client connection requests to a single network name (provided by DFS) are evenly distributed among the nodes in the cluster. On failure of a node, DFS detects the loss of network connectivity and routes new connection and re-connection requests to the remaining nodes in the cluster.

The Cluster File Share monitor can detect a situation in which a node in the cluster loses access to the PSFS filesystem (for example, because of a SAN problem) but is otherwise healthy. The monitor then tears down the associated CIFS share to prevent future connection and re-connection requests from being directed to a node that has lost access to the underlying shared filesystem.

Chapter 4: Configuring HP Clustered Gateway with Cluster File Shares 9

When the node regains access to the shared filesystem, the Cluster File Share monitor automatically recreates the CIFS share and the node then starts handling requests.

There are two steps to the configuration process: first create Cluster File Shares and then configure DFS (or another load balancer).

Add a Cluster File ShareCluster File Shares should be added via the HP CFS Management Console instead of using a Windows application to create them. When you add a file share with the HP CFS Management Console, a monitor that periodically checks the health of the Cluster File Share is also created.

To add a Cluster File Share, select CIFS File Serving > Add Cluster File Share on the HP CFS Management Console.


Application: An “application” provides a tag to group Cluster File Shares and related resources on the Applications tab. All of the resources associated with the application can then be treated as a unit. You can specify a new application name, select an existing application name, or leave this field blank. However, if you do not assign a name, HP Clustered File System will use the name of the Virtual File Share as the application name.

Share Name: Type a name for the Cluster File Share.


Path: Type the location of the Cluster File Share (such as y:\). This is typically the drive letter or path assigned to the PSFS filesystem that will be accessed via this share.

Comment: If desired, enter a description of the Cluster File Share.

User Limit: This value specifies the number of users that will be allowed to access the Cluster File Share simultaneously. Maximum is the system maximum, which is limited by the available memory. To specify a different number of users, select Allow and then type the number of users to be given access.

Access: Check this box to enable the Access-based Enumeration feature provided with Windows 2003 Service Pack 1. This feature allows users to see only the files and folders to which they have access on a file share.

Probe Configuration: The Cluster File Share monitor periodically probes the health of the file share. The timeout is the maximum amount of time that will be waited for the probe to complete. The default timeout interval is five seconds.

The frequency is the interval of time, in seconds, at which the monitor probes the file share. The default setting is 10 seconds.

Servers: Select the servers on which the Cluster File Share should be configured. Using the arrows, move the appropriate servers from the Available Servers column to the Selected Servers column.

When you click OK, the Cluster File Share displays on the Servers and Applications tabs on the HP Management Console. In the following example of the Servers tab, three Cluster File Shares are configured on each server. On each server, the Cluster File Share monitor is probing the health of the file share. (In the example, all file shares are UP.)


The Applications tab lists the Cluster File Shares under their associated applications. Following is the Applications view of the configuration shown above.


To add a Cluster File Share from the command line, use this command:

mx mfs add [arguments] --path <path> --servers ALL_SERVERS| <server1>,<server2>,... <mfs_name>

See the HP Clustered File System Command Reference for more information about this command.


Configure DFS The Microsoft Distributed File System (DFS) can be used in conjunction with CIFS to provide high availability failover and load balancing across the nodes in the cluster.

NOTE: If you are using Windows 2003, the DFS namespace must be administered from with the Windows 2003 version of the administrative tools. Do not use the administrative tools provided with Windows 2000 to manage DFS.

Setup ScenarioThe DFS setup procedure uses this scenario:

• A three-node cluster clust[1-3] in the domain data. The two domain controllers are dc[1-2]. These domain controllers are running Windows 2000 (or higher) with Active Directory.

• HP Clustered File System is started on the cluster nodes.

• On Windows Storage Server 2003, a shared PSFS volume is used for root and another shared PSFS volume is used for the link.

• A shared PSFS volume is mounted as x: on nodes clust[1-3]. The directory x:\foo is shared through CIFS via HP Clustered File System.

• All clients needing to access the share foo are either in domain data or in another domain that has a trust relationship with data.

• Clients are either Windows 2000 and higher, Windows 9x with the DFS client installed, NT4 with the DFS client installed, or other clients as described in Chapter 1.

Considerations for Using DFSWhen using DFS with HP Clustered File System, you should be aware of the following:

• We strongly recommend that domain-based DFS be used. Stand-alone DFS does not provide fault tolerance on root.


• Shares deployed via DFS must be under the control of CIFS. Use only Cluster File Shares; they are designed to work properly with DFS and CIFS. The following should not be used:

– CIFS shares created with other Windows applications. These shares will not be under CIFS control.

– CIFS Virtual Servers. These virtual servers are not compatible with DFS.

• Cluster File Shares must be created before you set up DFS. (See “Add a Cluster File Share” on page 9.)

DFS Setup on Windows Storage Server 2003After you have created the appropriate Cluster File Shares, complete the following steps to set up DFS:

1. Open the DFS MMC snap-in under “Administrative Tools.” Create a “domain-based” DFS root, dfsroot, in Active Directory. A DFS root target can be on a PSFS filesystem; however, it must be a different path/share than the link. (When creating the root, you will need to use drive letters; attempts to use mount points will fail.) Then create “root targets” pointing to a CIFS share (for example, Y:\dfsroot shared as \\clust1-3\dsfroot). Each server should have a target pointing to the same location on the PSFS filesystem.

2. Add a “New Link” called foo. Then add \\clust1\foo1, \\clust2\foo1, and \\clust3\foo1 as link targets.

3. Configure all link targets with “manual replication” because you are using a shared filesystem. There is no need to replicate data between nodes in the same cluster sharing the same filesystem. However, some form of manual replication will be needed if you create link targets of this same DFS link on nodes outside of this cluster.

The client can now have highly available, scalable access to foo over CIFS by mapping foo with the following command:

net use * \\data\dfsroot\foo /user:data\<username>


Other ProceduresCluster File SharesModify the Configuration of a Cluster File ShareTo change the configuration of a Cluster File Share, select it on the Servers or Applications tab, right-click, and select Properties. You can then modify the configuration as necessary.

You can also enter the following at the Command Prompt:

mx mfs update [arguments] [--path <path>] [--servers ALL_SERVERS|<server1>,<server2>,...] <mfs_name>

Delete a Cluster File ShareTo remove a Cluster File Share, select it on the Servers or Applications tab, right-click, and select Delete.


mx mfs delete <mfs_name> ...

Display StatusThe following command displays the status of a Cluster File Share.

mx mfs status [arguments] <mfs_name> ...

The arguments are:

[--up|--down][--enabled|--disabled][--active|--inactive]

Remove a Cluster File Share from a ServerThis procedure removes the selected server from the configuration of the Cluster File Share. Select the Cluster File Share on the Servers tab, right-click, and select Remove From Server. (On the Applications tab, right-click in the cell for the server from which the Cluster File Share is to be deleted.)


Cluster File Share MonitorsDisable or Enable a Cluster File Share MonitorTo disable a Cluster File Share monitor on a particular node, select it on the Servers tab, right-click, and select Disable. (On the Applications tab, right-click in the server cell corresponding to the Cluster File Share.)

To reenable the monitor, select it on the HP Management Console, right-click, and select Enable.


mx mfs enable <mfs_name> [ALL_SERVERS|<server> ...]

mx mfs disable <mfs_name> [ALL_SERVERS|<server> ...]

View ErrorsTo view the last error for a Cluster File Share monitor, select the file share on the Servers tab, right-click, and select View Last Error. (On the Applications tab, right-click in the server cell corresponding to the Cluster File Share.)

Clear ErrorsTo clear an error, select the affect Cluster File Share on the Servers tab, right-click, and select Clear Last Error. (On the Applications tab, right-click in the server cell corresponding to the Cluster File Share.)


mx mfs clear <mfs_name> <server> ...


5

Configuring CIFS with CIFSVirtual Servers

Configuration OverviewWhen CIFS is configured with HP Clustered File System, the data to be shared is stored on PSFS clustered filesystems. A set of Virtual File Shares, one per node in the cluster, is typically created for each filesystem.

CIFS uses “CIFS Virtual Servers” to provide CIFS access to the Virtual File Shares. Clients access the Virtual File Shares via the CIFS interface to those CIFS Virtual Servers; they do not need to know which physical node is providing the service.

When you create a CIFS Virtual Server, you will need to assign it to a primary node and one or more backup nodes. You can then add one or more Virtual File Shares to the CIFS Virtual Server. The following example shows a CIFS Virtual Server providing the Virtual File Share data1.

Chapter 5: Configuring CIFS with CIFS Virtual Servers 19

In this example, the CIFS Virtual Server VFS1 is initially active on the primary node; client requests for its Virtual File Shares go to this node. CIFS periodically monitors the Virtual File Shares to determine whether they can be accessed externally.

If CIFS detects that a Virtual File Share can no longer be accessed on the primary node, by default the ClusterPulse process (provided with HP Clustered File System) will fail over the associated CIFS Virtual Server to one of the designated backup nodes. Clients then access the CIFS Virtual Server’s Virtual File Shares from that node. Because the files associated with the Virtual File Shares are located on a PSFS cluster filesystem, the backup node can immediately access the data.

By default, the CIFS Virtual Server will remain active on the backup node. However, you can customize the failover and failback behavior. For example, after access to the Virtual File Share is restored on the original node, you may want the CIFS Virtual Server to fail back to that node.


Multiple Virtual File Shares can be associated with a CIFS Virtual Server, and multiple CIFS Virtual Servers can be supported on a physical node. Also, a node can host multiple active CIFS Virtual Servers while simultaneously serving as a backup for CIFS Virtual Servers that are active on other nodes.

In the following example, the first node is primary for CIFS Virtual Server VFS1 and a backup node for CIFS Virtual Server VFS2. The second node is primary for CIFS Virtual Server VFS2 and is a backup for VFS1. Node three is a backup for both CIFS Virtual Servers.


Configuration StepsPerform the configuration in this order:

• Create a CIFS Virtual Server, specifying a primary node. Depending on your configuration, you may also want to specify one or more backup nodes for this CIFS Virtual Server.

• Add Virtual File Shares to the virtual server. Be sure to create the Virtual File Shares on the HP Management Console; you should not use Windows applications such as Explorer to do this.

When you plan your configuration, keep in mind that all Virtual File Shares added to a particular CIFS Virtual Server are active on the node where the CIFS Virtual Server is active. Similarly, when the CIFS Virtual Server fails over, those Virtual File Shares become active on the backup node and will be accessed from there.

You may want to create multiple CIFS Virtual Servers to spread the CIFS activity across the cluster, taking advantage of the scalability of the HP solution. Remember, a node can simultaneously be primary for some CIFS Virtual Servers and a backup for other CIFS Virtual Servers.


Create a CIFS Virtual ServerTo create a CIFS Virtual Server, from the HP CFS Management Console select CIFS File Serving > Add CIFS Virtual Server. The Add CIFS Virtual Server window then is displayed.

Address: Specify either the IP address or the DNS name that will be associated with this CIFS Virtual Server. The DNS name must already be configured in the DNS service.

DNS/NetBIOS name: Use this field to specify a DNS/NetBIOS name. The NetBios name is calculated from the DNS name that you enter here. If Dynamic DNS is enabled on the DNS server, CIFS will add the DNS name to the DNS service. If not, you will need to update the DNS server with the corresponding host record for the CIFS Virtual Server IP address.

Application: An “application” provides a tag to group CIFS Virtual Servers and Virtual File Shares on the Applications tab. All of the resources associated with the application can then be treated as a unit.


You can specify a new application name, select an existing application name, or leave this field blank. However, if you do not assign a name, HP Clustered File System will use the IP address of the CIFS Virtual Server as the application name.

Policy: The policy determines the failback action that the CIFS Virtual Server will take following a failover to a backup node.

• AUTOFAILBACK. This policy is intended to return the CIFS Virtual Server to its original configuration, or as close to it as possible. After the CIFS Virtual Server fails over to a backup node, the ClusterPulse process watches the health of the nodes that are higher in the list of servers configured for that CIFS Virtual Server. When the health of one of these nodes is equal to or greater than the backup node where the CIFS Virtual Server currently resides, the CIFS Virtual Server will automatically attempt to fail over to that node.

• NOFAILBACK. This policy is intended to minimize failovers and is the default. The CIFS Virtual Server remains active on the backup node until a “healthier” node becomes available, at which point the CIFS Virtual Server fails over to that node. (On a “healthier” node, more of the services associated with the CIFS Virtual Server will be up than on the node currently hosting the CIFS Virtual Server.)

Network Interfaces Available/Members: Move the interfaces on which the CIFS Virtual Server should be configured from the Network Interfaces Available column to the Members column. The first interface that you select is the primary interface. The other interfaces that you select are backups. You can use the up and down arrows to reorder the interfaces on the Members column.

When you click OK, the CIFS Virtual Server displays on the Servers, Virtual Hosts, and Applications tabs on the HP Management Console. The following example of the Servers view shows a CIFS Virtual Server configured on two nodes; one node is the primary and the other is a backup.


To add a CIFS Virtual Server from the command-line, use this command:

mx vfs add [--policy autofailback|nofailback] <ip> <name> [ALL_SERVERS <primary_IP>|[<node1_IP> <node2_IP> <nodeN_IP>]

See the HP StorageWorks Clustered File System Command Reference for more information about using this command.

Add a Virtual File ShareWhen you add a Virtual File Share to a CIFS Virtual Server, be sure to use the HP CFS Management Console instead of a Windows application. (If Windows utilities are used to create the Virtual File Shares, they will not fail over.)

CIFS also creates a service monitor that periodically checks whether the Virtual File Share can be accessed externally. A failure detected by the monitor’s probe operation can cause the ClusterPulse process to fail over the CIFS Virtual Server to a backup node. You can use the Advanced options on the Add Virtual File Share window to customize the behavior of the service monitor.

To add a Virtual File Share to a CIFS Virtual Server, first select the CIFS Virtual Server on the HP CFS Management Console. Then right-click and select Add Virtual File Share.


CIFS Virtual Server: This field contains the IP address of the CIFS Virtual Server that you selected.

Share Name: Type a name for the Virtual File Share. If the associated CIFS Virtual Server is configured to fail over to other nodes in the cluster, the share name you specify must be unique across all nodes in the cluster (or at least across all potential backup nodes). Using unique names avoids share-name conflicts if a CIFS Virtual Server fails over.

Path: Type the location of the Virtual File Share (such as y:\). This is typically the drive letter or path assigned to the PSFS filesystem that will be accessed via this share.

Comment: If desired, enter a description of the Virtual File Share.

User Limit: This value specifies the number of users that will be allowed to access the Virtual File Share simultaneously. Maximum is the system maximum, which is limited by the available memory. To specify a different number of users, select Allow and then type the number of users to be given access.


Access: Check this box to enable the Access-based Enumeration feature provided with Windows 2003 Service Pack 1. This feature allows users to see only the files and folders to which they have access on a file share.

Probe Configuration: The Virtual File Share monitor periodically probes the health of the Virtual File Share on the node where the CIFS Virtual Server is active. The timeout is the maximum amount of time that will be waited for the probe to complete. The default value is five seconds.

The frequency is the interval of time, in seconds, at which the monitor probes the Virtual File Share. The default setting is 10 seconds.

NOTE: The probe behavior of the Virtual File Share monitor differs from the behavior of the service monitors provided with HP Clustered File System. In HP Clustered File System, the monitor probes the associated service on all nodes on which it is configured. The Virtual File Share Monitor probes only on the node where the CIFS Virtual Server is active.

When you click OK, the Virtual File Share displays on the Servers, Virtual Hosts, and Applications tabs. The following example of the Servers view shows a Virtual File Share configured on the CIFS Virtual Server qar20vfstest.


The next example shows the Applications tab with two CIFS Virtual Servers and the associated Virtual Files Shares configured across the four servers in the cluster. The CIFS Virtual Servers are assigned to the application Vcifs.

To add a Virtual File Share from the command line, use this command:

mx vfs_share add [arguments] --path <path> \\<vfs>\<vfs_share>

See the HP StorageWorks Clustered File System Command Reference for more information about using this command.


Virtual File Share Advanced ConfigurationYou can customize the operation of the Virtual File Share monitor by using the Advanced options provided on the Add Virtual File Share window. When you click the Advanced button, you will see two tabs: Policy and Scripts.

PolicyThe Policy tab lets you specify the failover policy and service priority that will apply to the Virtual File Share monitor.

Timeout and Failure Severity: This setting works with the CIFS Virtual Server policy (either AUTOFAILBACK or NOFAILBACK) to determine what happens when the monitor’s probe fails.

The default policies (NOFAILBACK for the virtual host and AUTORECOVER for the monitor) cause the ClusterPulse process to fail over the CIFS Virtual Server to a backup node. The CIFS Virtual Server remains on the backup node until a “healthier” node becomes available, at which point the CIFS Virtual Server will fail over to that node.


You can use the Timeout and Failure Severity attribute to change the failover/failback behavior. There are three settings: NOFAILOVER, AUTORECOVER, and NOAUTORECOVER.

NOFAILOVER. When the monitor probe fails, the CIFS Virtual Server does not fail over to a backup node. This option is useful when the monitored resource is not critical, but is important enough that you want to keep a record of its health. To use this option, you must also specify IGNORE as the Event Severity on the Scripts tab.

AUTORECOVER. When the monitor probe fails, the ClusterPulse process automatically fails over the associated CIFS Virtual Server to a backup node. Failback occurs in accordance with the policy setting for the CIFS Virtual Server (either AUTOFAILBACK or NOFAILBACK). See“Create a CIFS Virtual Server” on page 22 for a description of these settings.

NOTE: If you choose to use AUTORECOVER, you should be aware that fail over or fail back disrupts connectivity. Reconnection should be automatic, but data from in-flight updates may be lost.

NOAUTORECOVER. When the monitor probe fails, the ClusterPulse process automatically fails over the associated CIFS Virtual Server to a backup node. The monitor is then disabled on the original node. You will need to manually reenable the monitor before failback can occur to the original node. This option is useful when integrating CIFS with a custom application, where certain application-specific actions must be taken before the failback can occur.

Service Priority: The service priority is used when ClusterPulse fails over CIFS Virtual Servers. Service priorities are natural numbers, with 0 (zero) representing the highest priority and higher numbers representing lower priorities. If multiple failures prevent ClusterPulse from placing a CIFS Virtual Server on a node where all of its associated services are available, ClusterPulse next looks for a node where the associated service with the highest priority is available. The default priority is 0.


ScriptsThe Scripts tab lets you customize a Virtual File Share monitor with Start, Stop, and Recovery scripts. You can also configure the event severity and script ordering for the monitor.

Script Pathnames: The Virtual File Share monitor can optionally be configured with the following types of scripts:

Recovery script. Runs after a monitor probe failure is detected, in an attempt to restore access to the Virtual File Share.

Start script. Runs as the Virtual File Share is becoming active on a server.

Stop script. Runs as the Virtual File Share is becoming inactive on a server.

When a monitor is instantiated, the ClusterPulse process chooses the best node to make the service active. The Start script is run on this node. On all other nodes configured for the monitor, the Stop script is run to ensure that the service is not active.


Start scripts must be robust enough to run when the service is already started, without considering this to be an error. Similarly, Stop scripts must be robust enough to run when the service is already stopped, without considering this to be an error. In both of these cases, the script should exit with a zero exit status.

This behavior is necessary because the Start and Stop scripts are run to establish the desired start/stop activity, even though the service may actually have been started by something other than CIFS. The Start and Stop scripts must also handle recovery from events that may cause them to run unsuccessfully.

For example, if the system encounters a problem, the script will fail and exit non-zero. The service could then become active on another node, causing the Stop script to run on the original node even though the Start script did not complete successfully.

Event SeverityIf a Start or Stop script fails or times out, a monitor event is created on the the node where the failure or timeout occurred. An event is also created when a Virtual File Share monitor probe reports a status of DOWN. Configuration errors can also cause this behavior. You can view these events on the HP Management Console and clear them from the Console after you have fixed the problems that caused them.

When an event is created, the ClusterPulse process may initiate failover of the associated CIFS Virtual Server. You can configure the failover behavior with the Event Severity attribute. There are two settings: CONSIDER and IGNORE.

CONSIDER. This is the default value. Events are considered when the ClusterPulse process makes failover decisions.

IGNORE. Events are ignored; script failures and DOWN status reports from the monitor will not cause failover. This is useful when the DOWN status or the action performed by the scripts is not critical, but is important enough that you want to keep a record of it.


Script OrderingScript ordering determines the order in which the Start and Stop scripts are run when a CIFS Virtual Server moves from one node to another. If you do not configure the Virtual File Share monitor with Start and Stop scripts, the script ordering configuration has no effect. There are two settings: SERIAL and PARALLEL.

SERIAL. This is the default setting. When a CIFS Virtual Server moves from one node to another, the following strict ordering sequence for running Start and Stop scripts is enforced:

1. The Stop script is run on all nodes where the virtual host should be inactive.

2. ClusterPulse waits for all Stop scripts to complete.

3. The Start script is run on the node where the virtual host is becoming active.

PARALLEL. The strict ordering sequence for Stop and Start scripts is not enforced. The scripts run in parallel across the cluster as a CIFS Virtual Server is in transition.

The PARALLEL configuration can speed up failover time for services that do not depend on strict ordering of Start and Stop scripts. Assuming that it is safe to run the scripts in parallel (which depends on your application), this setting can also increase the chances of a successful failover because ClusterPulse does not have to wait for the failing node to finish running its Stop script.

Linux ClientsLinux clients can mount Virtual File Shares using the CIFS Virtual Server address. If a mount command fails with the message “Connection Refused,” retry the command with the port=445 option. Following is an example:

# mount -t smbfs -o ‘username=Administrator,uid=Administrator,port=445’//10.11.200.200/temp /try1


Other ProceduresCIFS Virtual ServersThese procedures can be performed from the HP CFS Management Console or the command line. On the Management Console, select the CIFS Virtual Server on the Servers, Virtual Hosts, or Applications tab and then right-click to display a menu listing the available options.

Modify the ConfigurationTo modify the configuration of a CIFS Virtual Server, select that CIFS Virtual Server on the HP CFS Management Console, right-click, and select either Properties or Rehost. You can add or remove interfaces from the CIFS Virtual Server configuration and can reorder the interfaces. If you designate a new primary interface, the service will automatically be moved to that interface.

You can also change the configuration at the Command Prompt:

mx vfs update [--policy autofailback|nofailback] [<ip>|<name>] [ALL_SERVERS <primary_interface>|<node1_IP> <node2_IP> <nodeN_IP>]

This command allows you to add or remove interfaces from the CIFS Virtual Server configuration and to reorder the interfaces. If you specify a different primary interface and --policy is set to autofailback, the command will automatically move the service to the new primary.

If --policy is set to nofailback, the update command will not move the service to the new primary. You will then need to use the vfs move command shown below to move the service.

mx vfs move <ip>|<name> <target_networkinterface>

Delete a CIFS Virtual Server To remove a CIFS Virtual Server, select that CIFS Virtual Server on the HP CFS Management Console, right-click, and select Delete.


mx vfs delete <ip>|<name>


Disable or Enable a CIFS Virtual ServerBy default, CIFS Virtual Servers are enabled. If you disable a currently active CIFS Virtual Server, any associated Virtual File Share monitors on the node where the CIFS Virtual Server is active will go through their stopping activities and the CIFS Virtual Server will become inactive throughout the cluster.

To disable a CIFS Virtual Server, select the CIFS Virtual Server on the HP Management Console, right-click, and select Disable.

To enable a previously disabled CIFS Virtual Server, select the CIFS Virtual Server on the HP Management Console, right-click, and select Enable.


mx vfs enable <ip>|<name>mx vfs disable <ip>|<name>

Display Status for a CIFS Virtual ServerUse the following command to see the status for a CIFS Virtual Server:

mx vfs status [arguments] <ip>|<name>

The arguments are:

[--up|--down][--enabled|--disabled][--primary|--backup][--active|--inactive]

Virtual File SharesModify the ConfigurationTo change the configuration of a Virtual File Share, select that Virtual File Share on the Servers, Virtual Hosts, or Applications tab, right-click, and select Properties. You can then modify the configuration as necessary.


mx vfs_share update [arguments] [--path <path>] \\vfs>\<vshare>


See the HP StorageWorks Clustered File System Command Reference for more information.

Disable or Enable a Virtual File Share MonitorWhen a monitor is disabled, the health of the server is affected in the same manner as a failure of the monitor’s probe operation. If the Policy configuration of the monitor is either AUTORECOVER or NOAUTORECOVER, the ClusterPulse process will attempt to fail over the CIFS Virtual Server to a backup node. If a backup node is not available or if the Policy configuration of the monitor is NOFAILOVER, the service will remain up on the original node.

To disable a Virtual File Share monitor on a particular server, select it on the Servers tab, right-click, and select Disable. (On the Applications tab, right-click in the cell corresponding to the Virtual File Share and server.) To reenable the monitor, select it on the HP Management Console, right-click, and select Enable.


mx vfs_share enable \\vfs>\<vshare> <netif> ...mx vfs_share disable \\vfs>\<vshare> <netif> ..

View Monitor ErrorsTo view the last error for a Virtual File Share monitor, select the Virtual File Share monitor on the Servers tab, right-click, and select View Last Error. (On the Applications tab, right-click in the cell corresponding to the Virtual File Share and server.)

Clear Monitor ErrorsTo clear an error, select the Virtual File Share monitor on the Servers tab, right-click, and select Clear Last Error. (On the Applications tab, right-click in the cell corresponding to the Virtual File Share and server.)


mx vfs_share clear \\vfs>\<vshare> <netif> ...


Display Status for a Virtual File ShareEnter the following at the Command Prompt:

mx vfs_share status [arguments] \\vfs>\<vshare>

The arguments are:

[--up|--down][--primary|--backup][--enabled|--disabled][--active|--inactive]

Delete a Virtual File ShareTo remove a Virtual File Share, select that Virtual File Share on the Servers, Virtual Hosts, or Applications tab, right-click, and select Delete.


mx vfs_share delete \\vfs>\<vshare>

37

AApplications tab

CIFS Virtual Server 27Cluster File Share 12

CCIFS Virtual Server

client requirements 4configuration

create 22delete 33modify 33planning 21

DNS/NetBIOS name 22on Applications tab 27overview 18primary and backup interfaces 23

clientsDNS name resolution 6NetBIOS name resolution 6operating systems 5

Cluster File Shareadd 9configuration planning 8delete 16modify configuration 16monitor

disable 17enable 17errors, clear 17errors, view 17probe configuration 11

on Applications tab 12overview 4user limit 11

DDFS, configure 14

Ggetting help 1

HHP

storage web site 1technical support 1

HP Clustered File Systemsecurity 7

NNetBIOS name resolution 6

RRecovery script 30

Sscripts

event severity 31ordering 32

security 7Start script 30Stop script 30

Ttechnical support, HP 1

VVirtual File Server

overview 18Virtual File Share

Index

Index 38

add 24configuration

modify 34delete 36failover policy 28monitor

disable 35

enable 35errors, clear or view 35event severity 31scripts, configure 30

probe configuration 26service priority 29user limit 25

Download - HP StorageWorks Clustered File System 3.2.1 CIFS File Serving …h10032. · 3 2 Introduction The HP Clustered File System software provides scalability and high availability for the

Top Related