Revision: B5
Document Number: 96-00320-001 October 2014Version 1.4.0
Admin Guide
Important Information
Information in this document is subject to change without notice and does not represent a commitment on the part of DataDirect Networks, Inc. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose other than the purchaser’s personal use without the written permission of DataDirect Networks, Inc.
© 2014 DataDirect Networks, Inc. All rights reserved.
DataDirect Networks, the DataDirect Networks logo, DirectOS, DirectProtect, DirectMon, EXAScaler, GRIDScaler, Information in Motion, NAS Scaler, NoFS, ObjectAssure, SATAssure, Silicon Storage Appliance, S2A, Storage Fusion Architecture, SFA, Storage Fusion Fabric, Storage Fusion Xcelerator, SFX, xSTREAMScaler, Web Object Scaler, WOS are registered trademarks or trademarks of DataDirect Networks, Inc. All other brand and product names are trademarks of their respective holders.
DataDirect Networks makes no warranties, express or implied, including without limitation the implied warranties of merchantability and fitness for a particular purpose of any products or software. DataDirect Networks does not warrant, guarantee or make any representations regarding the use or the results of the use of any products or software in terms of correctness, accuracy, reliability, or otherwise. The entire risk as to the results and performance of the product and software are assumed by you. The exclusion of implied warranties is not permitted by some jurisdictions; this exclusion may not apply to you.
In no event will DataDirect Networks, their directors, officers, employees, or agents (collectively DataDirect Networks) be liable to you for any consequential, incidental, or indirect damages, including damages for loss of business profits, business interruption, loss of business information, and the like, arising out of the use or inability to use any DataDirect product or software even if DataDirect Networks has been advised of the possibility of such damages by you. Because some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, these limitations may not apply to you. DataDirect Networks liability to you for actual damages from any cause whatsoever, and regardless of the form of the action (whether in contract, tort including negligence, product liability or otherwise), is limited to the sum you paid for the DataDirect product or software.
T
ABLE OF
C
ONTENTS
1.0 WOS ACCESS OVERVIEW ... 12
1.1 Product Description ... 12 1.2 NFS Service ... 12 1.2.1 NFSv4 ID Mapping ... 13 1.3 CIFS Service ... 13 1.4 Namespace Synchronization ... 13 1.5 Disaster Recovery ... 14 1.6 Services Relocation ... 14
1.7 Web Administration User Interface Overview ... 16
1.8 Network Configuration ... 16
1.9 Sharing Files Between NFS and CIFS ... 17
2.0 SOFTWARE INSTALLATION ... 17
2.1 Operating System Installation ... 17
2.2 Web Object Storage Prerequisites ... 17
2.3 WOS-Access Appliances ... 18
2.4 Default passwords ... 18
2.5 Configuring WOS client I/O filters ... 19
2.6 Verify WOS Access network connections between WOS Access Nodes and WOS Core ... 19
2.7 Adding a Mellanox ConnectX-3 Networking Card ... 19
3.0 WEB CONFIGURATION PROCEDURE ... 19
3.1 WEB Configuration Steps ... 19
3.1.1 Single WOS Access Server ... 19
3.1.2 Multiple WOS Access Servers ... 20
3.2 WOS Access Login Page... 20
3.3 WOS Storage Policy Configuration ... 21
3.4 WOS Access Namespace Synchronization Configuration for Two Or More Servers Sharing the Same Namespace or for Service Relocation ... 24
3.4.1 Configuring Namespace Synchronization ... 24
3.4.2 Creating New Replication Group ... 26
3.4.3 Join Existing Replication Group ... 27
3.5 WOS Access NFS Configuration ... 28
3.5.1 Creating NFS Export Points ... 29
3.5.2 NFS Protocol Configuration ... 30
3.5.3 NFS Security Configuration... 30
3.5.4 Delete NFS Export Point ... 32
3.5.5 Start NFS Service ... 33
3.6 WOS Access CIFS Configuration ... 33
3.6.1 Changing CIFS Service Status ... 34
3.6.2 Changing CIFS Service Configuration ... 35
3.6.3 Creating, Modifying, and Deleting CIFS Export Points... 36
3.7 WOS Access Disaster Recovery Configuration ... 40
3.7.1 Enable Disaster Recovery Service ... 40
3.7.2 Scheduling a Full Backup ... 41
3.8 WOS Access Services Relocation Service Configuration ... 41
3.9 WOS Access Preferences ... 44
3.9.1 Changing Email Alerts Preferences... 45
3.9.2 Changing Credentials ... 47
3.9.3 Changing User Interface Preferences ... 47
3.9.4 Changing Exporting syslog ... 48
4.0 WEB ADMINISTRATION REFERENCE ... 50
4.1 General Navigation ... 50 4.2 Status Icons ... 51 4.3 User Interface ... 52 4.3.1 Summary Screen ... 52 4.3.1.1 Service Status ... 52 4.3.1.2 Storage Statistics ... 53
4.3.1.3 System Charts: Protocols ... 54
4.3.1.4 System Charts: WOS Storage ... 54
4.3.1.5 System Charts: Synchronization ... 55
4.3.1.6 System Charts: System ... 55
4.3.1.7 System Charts: Controls ... 56
4.3.1.8 Installed Packages Chart ... 56
4.3.2 Synchronization Screen ... 56
4.3.2.1 Nodes Section of Synchronization ... 57
4.3.2.2 Total Section of Synchronization ... 57
4.3.3 Services Screen ... 57 4.3.3.1 WOS Access ... 58 4.3.3.2 Synchronization ... 58 4.3.3.3 Services-Relocation... 59 4.3.3.4 Backup ... 59 4.3.4 Configuration Screen ... 60 4.3.4.1 Export List ... 60 4.3.4.2 NFS ... 63 4.3.4.3 CIFS ... 63
4.3.4.4 Active Directory Configuration ... 63
4.3.4.5 WOS ... 65
4.3.4.6 Services-Relocation... 65
4.3.4.7 Synchronization ... 66
4.3.4.8 Adding A New Node to a Cluster Synchronization Group ... 67
4.3.4.9 Backup ... 68
4.3.5 Preferences Screen ... 68
4.3.5.1 E-mail notifications ... 68
4.3.5.2 Credentials ... 69
4.3.5.3 User Interface preferences ... 69
4.3.5.4 Export syslog ... 69
5.3 CIFS Users and Groups Management ... 72
5.3.1 Add a new user ... 72
5.3.2 Delete an existing user ... 73
5.3.3 Modify user account attributes ... 73
5.3.4 Add a new group ... 74
5.3.5 Delete an existing group ... 75
5.3.6 Modify a group membership ... 75
5.3.7 List users and groups ... 76
5.3.8 Check group membership ... 76
5.3.9 CIFS Service Access Management ... 77
5.3.10CIFS Share Access Mode ... 77
5.3.11CIFS Service Current Usage Metrics ... 77
5.3.12Setup a Local CIFS User to Access CIFS Share ... 78
5.3.13Configuring CIFS UID/GID Values ... 78
5.4 CIFS Service configuration in Active Directory (optional) ... 79
5.4.1 Accessibility of Active Directory Domain Controller ... 80
5.4.2 Join AD Domain... 80
5.4.3 Check AD Domain accounts ... 81
5.4.4 Access to CIFS shares... 81
5.4.5 Leave AD Domain ... 81
5.5 Namespace Synchronization Service ... 81
5.5.1 Network requirements ... 82
5.5.2 Join Synchronization Group ... 82
5.5.3 View Synchronization Cluster Status ... 85
5.5.4 Leave Synchronization Cluster ... 85
5.6 WOS Access Services Relocation Service Configuration ... 86
5.6.1 Network requirements ... 87
5.6.2 Configure Cluster ... 89
5.6.3 Cluster Installation ... 92
5.6.4 Update Cluster Configuration... 94
5.6.5 Remove Cluster ... 94
5.6.6 Failover Policy Details ... 95
5.7 WOS Access Disaster Recovery Configuration ... 98
5.7.1 Configuration steps ... 98
5.7.2 Overview of backup process ... 99
5.7.3 Scheduling backup ... 100
5.7.4 Manual backups ... 100
5.7.5 Restoring from backup ... 100
5.7.6 References ... 102
5.8 Mellanox ConnectX-3 configuration ... 103
5.9 Enabling wos-fst logging dynamically ... 103
5.10 Disk Space Monitoring ... 103
5.11 Orderly Shut Down of the WOS Access Node ... 103
5.11.1WOS Access Shut Down Script ... 104
5.12 Renaming Host Names ... 105
6.0 QUOTAS ... 106
6.1 Planning ... 106
6.2 Setting Quotas ... 106
6.4 Enabling Quotas ... 108
6.5 Quota Reporting ... 108
6.5.1 Quota Reports using quotactl... 109
6.5.2 Quota Reports from NFS clients ... 109
6.5.3 Quota Reports via Email ... 110
6.6 Functional Limitations ... 110
6.6.1 Using quotas in a mixed CIFS/NFS environment ... 111
6.7 Troubleshooting ... 111
7.0 TRASHCAN FEATURE ... 112
7.1 Overview ... 112
7.2 TrashCan Utility tool (trashCanUtil) ... 112
7.2.1 TrashCan: A Simple Example ... 113
7.2.2 Handling conflicts on recovery ... 113
7.3 Background Delete ... 114
8.0 WOS ACCESS UPGRADE PROCEDURE ... 114
8.1 Preparing for Upgrade ... 114
8.2 Upgrade ... 115 8.3 Post-Upgrade ... 115 9.0 REFERENCES ... 116 9.1 NFS Configuration ... 116 9.1.1 Overview ... 116 9.1.2 Export ... 116 9.1.3 OVFS_WOS ... 117 9.1.4 OVFS_BACKUP ... 119 9.1.5 CacheInode_Client ... 119 9.1.6 NFS CORE Parameters ... 120 9.1.7 Deprecated NFS Parameters ... 120 9.2 Sync Configuration ... 122 9.3 SR Configuration ... 123 9.4 CIFS Configuration ... 123 9.5 quotactl command ... 125 9.5.1 quotactl on/off ... 125 9.5.2 quotactl status ... 125 9.5.3 quotactl cfg ... 126 9.5.4 quotactl set ... 126 9.5.5 quotactl get... 126 9.5.6 quotactl clear ... 127 9.5.7 quotactl check... 127 10.0TROUBLESHOOTING ... 127 10.1 Troubleshooting Installation ... 127 10.2 Troubleshooting NFS Service ... 128
10.4 Troubleshooting RabbitMQ ... 132
10.5 Troubleshooting Administration Web UI ... 134
10.6 Troubleshooting Disaster Recovery ... 135
10.6.1Backup failure ... 135
10.6.2Backup uses up all the available disk space ... 136
10.6.3No backup mail notification ... 136
10.7 Troubleshooting SR Cluster... 137
10.8 Troubleshooting CIFS Service ... 138
11.0SUPPORT ... 142
11.1 Available Online Documentation ... 142
12.0APPENDIX ... 142
12.1 List of Product Files ... 142
L
IST OF
F
IGURES
Figure 1 WOS Access Network Configuration Example ... 16
Figure 2 WOS Access Login Screen ... 21
Figure 3 WOS Access Initial Configuration Screen ... 21
Figure 4 WOS Configuration Section... 22
Figure 5 Password Prompt Box... 22
Figure 6 WOS IP Address Configuration ... 23
Figure 7 WOS Policy Configuration ... 23
Figure 8 Restart NFS/CIFS Services to apply WOS Parameters Message ... 23
Figure 9 Synchronization option ... 25
Figure 10 WOS Synchronization option ... 26
Figure 11 Restart Notification Message... 26
Figure 12 Join Replication Group Window: Create New Replication Group... 27
Figure 13 Namespace Synchronization Started ... 27
Figure 14 Join Existing Replication Group ... 28
Figure 15 Synchronization Tab ... 28
Figure 16 WOS NFS Configuration Section ... 29
Figure 17 Restart Service Confirmation Screen ... 29
Figure 18 NFS Export Point Sample Screen ... 30
Figure 19 Creating NFS Export Point for All ... 31
Figure 20 Granting Client and Root Access to those specified ... 32
Figure 21 Edit/Delete NFS Export Points ... 33
Figure 22 Start NFS Service ... 33
Figure 23 NFS Service Status ... 33
Figure 24 Export List section of the Configuration tab ... 34
Figure 25 CIFS section of Configuration tab ... 34
Figure 26 CIFS Service Running Status ... 34
Figure 27 CIFS Service Configuration Screen ... 35
Figure 28 Confirmation Message to confirm changes to CIFS Service Configuration ... 36
Figure 29 Create New Export Point via CIFS ... 37
Figure 30 Success Message ... 38
Figure 35 JoinActive Domain Result Message ... 40
Figure 36 DC name ... 40
Figure 37 Confirm Action to Leave Domain ... 40
Figure 38 Enable Disaster Recovery Backup options Screen ... 41
Figure 39 Disaster Recovery enabled ... 41
Figure 40 Services Relocation Section ... 43
Figure 41 Services Relocation Restart Notification Message ... 44
Figure 42 Services Relocation Group Created ... 44
Figure 43 WOS Access Preferences Tab Screen ... 45
Figure 44 Email Alerts section on Preferences screen ... 45
Figure 45 Email test status message ... 46
Figure 46 Change Status Message ... 46
Figure 47 Credentials section of Preferences screen ... 47
Figure 48 Notification of Changes Message ... 47
Figure 49 User Interface Preferences... 48
Figure 50 Notification of Changes Message ... 48
Figure 51 Exporting syslog section of Preferences screen ... 49
Figure 52 Notification of Changes Message ... 49
Figure 53 WOS Access UI Screen ... 50
Figure 54 Status Icons ... 51
Figure 55 User Interface (UI) sample screen ... 52
Figure 56 WOS Storage Protocols... 54
Figure 57 WOS Storage Chart ... 55
Figure 58 System Synchronization Chart ... 55
Figure 59 System Chart ... 56
Figure 60 Synchronization Screen ... 56
Figure 61 WOS Access Service tab screen ... 58
Figure 62 Configuration tab screen ... 60
Figure 63 Join AD Step 1 ... 64
Figure 64 Join AD Step 2 ... 64
Figure 65 Confirmation message... 65
Figure 66 Join Synchronization Group ... 68
Figure 67 Preferences tab screen... 70
Figure 68 Sample Logs Screen ... 71
List of Tables
Table 1 WOS Access Credentials ... 18
Table 2 Administrative User Interface Tabs ... 50
Table 3 Service Status Icons ... 51
Table 4 Node Section Parameters ... 57
Table 5 Total Section Parameters ... 57
Table 6 WOS Access Status Parameters ... 58
Table 7 Synchronization Parameters ... 59
Table 8 Services-Relocation Parameters ... 59
Table 9 Backup Parameters ... 59
Table 10 Export List Parameters ... 61
Table 11 CIFS Export List Parameters ... 62
Table 12 NFS Parameters ... 63
Table 13 CIFS Parameters... 63
Table 14 Join Active Directory Wizard ... 64
Table 15 WOS Parameters ... 65
Table 16 SR Service Parameters ... 65
Table 17 Synchronization Service Parameters... 66
Table 18 Join To Synchronization Group Wizard. ... 68
Table 19 Backup User Interface Options ... 68
Table 20 Email Notifications Parameters (NFS/CIFS) ... 68
Table 21 User Attribute Options ... 72
Table 22 Modification Options of User Accounts ... 73
Table 23 Group Attribute Options ... 75
Table 24 Modifications Options for Group Membership ... 75
Table 25 Users and Group Options ... 76
Table 26 Group Membership Filters ... 77
Table 27 Node management command-line tool ... 83
Table 28 Nodectl Commands with optional parameters ... 84
Table 29 SR Service Configuration Parameters ... 87
Table 30 System Parameters... 91
Table 31 Policy description for tracked services ... 96
Table 35 Backup Command Line Options ... 102
Table 36 Restore Command Line Options... 102
Table 37 Block Name Usage Descriptions ... 116
Table 38 Export ... 117
Table 39 OVFS_WOS Block ... 117
Table 40 OVFS_BACKUP ... 119
Table 41 Cachelnode_Client Parameters ... 119
Table 42 NFS Core Parameters ... 120
Table 43 WOSAccess Sync Configuration Parameters... 122
Table 44 SR Configuration Parameters ... 123
Table 45 WOSACCESS_CIFS Configuration ... 123
Table 46 ClientProtocols key default values ... 139
Table 47 Notable product directories and files ... 142
Table 48 WOS Access TCP/UDP ... 142
1.0
WOS Access Overview
1.1
Product Description
DataDirect Networks’ WOS™ Access is a bundled server and software solution designed specifically to front the DDN Web Object Scaler (WOS) cluster with NFS and CIFS interfaces that provide a common, globally distributed namespace. With multiple WOS Access gateway nodes, distributed users can collaborate across geographic locations using NAS protocols.
WOS Access supports two gateways to be configured for services relocation in an
active/passive configuration. Up to eight gateway nodes (or four active/passive pairs) can be linked together to form a namespace synchronization group.
Key features of WOS Access include: • NFSv3 compatibility
• Basic NFSv4 compatibility (see the NFS Service section below for current NFSv4 limitations)
• CIFS (SMB 1.0, 2.0, and 2.1) compatibility • Active Directory authentication support
• Support for local users and groups where Active Directory authentication is not available or desirable
• Synchronized namespace across remote sites (maximum of eight (8) gateway nodes)
• Multiple export points per gateway • Local read and write cache
• Disaster Recovery (DR) protection • Services Relocation
WOS Access consists of the following key modules: • NFS Service
• CIFS Service
• Namespace Synchronization • Disaster Recovery (DR) • Services Relocation (SR) • Web User Interface (UI)
1.2
NFS Service
• Authentication mechanisms other than SYS_AUTH (i.e., AUTH_DH, Kerberos, LIPKEY, etc.)
• ID mapping (see below) • Volatile file handles
• Access Control Lists (ACLs)
o Permissions are stored only using NFS mode bits • File Locking
• Delegations (Client-side caching)
1.2.1
NFSv4 ID Mapping
A key part of any secure protocol is properly establishing identity of the users or groups that are attempting to use the protocol. In NFSv3, a common way of doing this is by using numeric identity values (i.e. UID/GID). However, this means that in order to share data between different NFS clients, all clients have to use the same UID/GID values. In some cases, this adds significant management overhead for system administrators.
For this reason, and others, the NFSv4 protocol provides the ability to identify users and groups by name, rather than numeric ID. However, most UNIX-based systems require numeric IDs for file system attributes. This means that there must be a way to map NFSv4 user/group names to UID/GID values, consistently, on both the client and the NFS server. Currently, WOS Access does not support NFSv4 identity mapping and requires that NFS clients identify users and groups using UIDs and GIDs, respectively. Linux clients based on RHEL can be configured to do this by running the following command and rebooting the client:
echo "options nfs nfs4_disable_idmapping=1" > /etc/modprobe.d/nfs.conf
1.3
CIFS Service
The Common Internet File System (CIFS) Service is a network-based service allowing a user on a client computer to access files over a network in a manner similar to how a local Microsoft Windows® shared folder is accessed. WOS Access CIFS fully supports Windows® authentication via Active Directory or a local user/group database. Windows ACLs are fully supported. WOS Access CIFS supports SMB versions 1.0, 2.0, and 2.1.
1.4
Namespace Synchronization
The Namespace Synchronization feature provides synchronization of the namespace metadata between multiple WOS Access gateways. This multi-master synchronization system is responsible for propagating the data modifications made by each node to the rest of the nodes in the same synchronization group or cluster.
Namespace synchronization does not propagate the Active Directory (AD) state and changes across an existing cluster. This propagation can only be done when adding a new node to an existing synchronization group.
1.5
Disaster Recovery
WOS Access Disaster Recovery (DR) provides the ability to backup namespace metadata and the gateway configuration to WOS and to restore in the event of catastrophic failure. Backup can be executed manually or run according to a configurable schedule.
1.6
Services Relocation
The Services Relocation (SR) feature provides an active-passive solution to relocate a Virtual IP address in the event of certain failures. When the IP address is relocated, applications that were performing I/O will need to restart their sessions, and CIFS clients may need to remap the export points.
The following is a summary of the operations and support provided by Services Relocation and the Unified Namespace:
• NFS file data written to WOS Access is cached and flushed to WOS Core after 30 seconds (OVFS_WOS_CACHE_EXP_TIME) of file inactivity in order to optimize handling and converting NFS files into WOS Objects. This caching is performed on a file-per-file basis (I.e., any files inactive for 30 seconds will be flushed while any actives files will continue to be cached).
• WOS Access synchronizes its namespace database with other WOS Access and Service Relocation nodes every 10 seconds (SYNC_BATCH_INTERVAL) or 1000 name space changes (SYNC_BATCH_SIZE).
• Therefore, WOS Access effectively performs a checkpoint with other WOS Access nodes and WOS Core every 10 seconds for CIFS files and 30 seconds of inactivity for an NFS file.
• Upon failure of a WOS Access node, the state of files written to that node since the last successful checkpoint is undefined.
• When Services Relocation is configured, NAS Services will be relocated to a secondary node upon failure of the primary node, and any file data written to that failed node since the last checkpoint will need to be rewritten to the secondary node once the NAS Services have been relocated. Note that the ‘Stale file handle’ error can occur on a client after fail-over of the NFS service, even if the file exists. The error will disappear when the NFS service is ready to work (relocation of NFS takes ~60 seconds). [DE13093]
Services relocation does not guarantee high availability. While the active instance is being shut down and the passive instance being brought up, a brief interruption will be
experienced. Once services relocation starts the services on the passive node, the NFS and CIFS shares, become available again but the data may not be fully available as the metadata synchronization from the Active node to the Passive node may not have taken place. Furthermore, NFS and CIFS clients would need to resubmit the write requests that were in flight at the time of services relocation. Any new NFS or CIFS requests will be satisfied by the node that has taken over the services.
Any services may die unexpectedly due to configuration or software problems. Services-Relocation cluster monitoring and restart services are available if a failure occurs.
• Clustering and Failover
Clustering allows the components to be viewed functionally as a single entity from client-side for runtime processing and manageability.
• Server Migration
Virtual IP (VIP) service can only have one instance running. If the active instance becomes unavailable, the service is automatically started on a different cluster member.
NOTE: SR does not currently relocate the VIP to a secondary SR node in the event of a
network connection failure between the WOS Access primary SR node and WOS Core.
SR provides support for services relocation nodes pairing and four services tracking, so these tracked services can be reliably utilized with a minimum of downtime. The package remedies the situation, when system services fail, by detecting software faults, and
immediately restarting the set of services on another node without requiring administrative intervention.
Services Relocation (SR) does not support automatic procedure for the planned downtime. The planned downtime is a manual procedure in order to ensure that there is no data-loss. The procedure essentially comprises of manually stopping NFS/CIFS traffic going to the WOS Access active node; then allowing WOS Access NFS and CIFS on the active node to run for some time to allow the files on staging area to be pushed to WOS Core and the WOS Access namespace synchronization to synchronize the metadata to the Passive instance; and finally trigger an event on active node like shutting down the machine, network or services to let these services be relocated to the passive node.
1.7
Web Administration User Interface Overview
The WOS Access Administration User Interface (UI) provides simplified way to monitor and manage:
• Services Status, Storage Statistics, Installed Packages • Synchronization • Services • Configuration • Preferences • Logs
1.8
Network Configuration
Figure 1 below shows a possible network configuration for a multi-site WOS Access setup. In this example, there are three network connections specified:
• Protocol/external network – used for connecting NFS and CIFS clients to the WOS Access gateway nodes. If the nodes are part of a Services Relocation pair then the connection should utilize the Virtual IP Address.
• Private network for storage – provides the network connection to the WOS cluster. • Heartbeat network – If the nodes are part of a Services Relocation pair then the two
nodes should be connected directly to each other on one or two dedicated interfaces.
1.9
Sharing Files Between NFS and CIFS
The following points should be considered when sharing files between NFS and CIFS protocols:
• On a Unix-based system, the filenames “file” and “FILE” are considered to be two different files. On Windows, the two file names are seen as the same file. So, if files with those names were created on NFS and then listed on Windows, you see both names but the content of only one of them.
• Windows doesn’t support symlinks, so all files of that type are displayed as regular files (for example, a symbolic link to a directory created on the NFS mount using a Linux client).
• Due to incompatibility between NFS and CIFS protocols, not all file permissions created on an NFS mount will be available on the CIFS Share, and vice-versa. • When using one export point for both NFS and CIFS, the NFS client will see an
additional file within the directory as an artifact from CIFS. For example: drwx--- 3 root root 4096 Apr 26 13:02 :STREAM
This extra file can by ignored by NFS users.
• In WOS Access, the Access time file attribute (i.e. ‘atime’) is not supported on either NFS or CIFS. When reporting file or folder atime to NFS or CIFS clients, the mtime will be used instead.
• By default, WOS Access will auto-generate unique UID and GID values for CIFS users and groups. In an environment where WOS Access is being used for both CIFS and NFS access, these auto-generated ID values may conflict with NFS ID values, leading to unexpected permission issues and problems with using quotas. For a full explanation of the issue and potential workarounds, see Section 5.3.13.
2.0
Software Installation
2.1
Operating System Installation
The WOS Access appliance ships with the operating system and product already installed.
2.2
Web Object Storage Prerequisites
These WOS prerequisites are required by WOS Access:
• All nodes in the WOS cluster must be installed and configured. Please refer to the latest WOS Access Release Notes for WOS version requirements.
• At least one policy should be created. This policy will be used by WOS Access for storing data to the WOS cluster. If namespace synchronization will be used then a second, separate policy is required.
• The WOS Access gateway must be able to communicate through the network to at least one node in the WOS cluster.
• TCP ports 80, 8085, 8088, and 8090 are used by WOS Access to communicate with the WOS cluster. These ports must be accessible from all WOS Access nodes.
NOTE: Contact DDN support for help in any of the above procedures.
2.3
WOS-Access Appliances
If you purchased a WOS Access gateway appliance from DDN, please note:
• The default root password is “DDNWOSaccess1". Please change this password immediately.
• Product installation logs may be found in /opt/ddn/nas/log. If the factory installation was successful, you should see a file in the log named wosaccess-install-successful. A detailed installation log is named wosaccess-install-<timestamp>.log.
• You must assign a hostname to your system and add it to/etc/hosts and /etc/sysconfig/network.
o Ensure the hostname is not on the same line as localhost in /etc/hosts. o Ensure that the IP address is not localhost (127.0.0.1) and that you see 0%
packet loss.
o Try both ping commands to ensure correct hostname configuration. The ip addresses returned by both commands should match each other.
For example, these commands produce the correct ping responses:
[root@dell26 log]# ping -c 1 $(hostname ) PING dell26 (10.40.30.26) 56(84) bytes of data.
64 bytes from dell26 (10.40.30.26): icmp_seq=1 ttl=64 time=0.013 ms
--- dell26 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.013/0.013/0.013/0.000 ms
[root@dell26 log]# ping -c 1 $(hostname -i)
PING 10.40.30.26 (10.40.30.26) 56(84) bytes of data. 64 bytes from 10.40.30.26: icmp_seq=1 ttl=64 time=0.008 ms
--- 10.40.30.26 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.008/0.008/0.008/0.000 ms
2.4
Default passwords
To ensure the security of your system, you should change the following default passwords immediately (Table 1).
Table 1 WOS Access Credentials
Feature User Password Notes
Factory OS root DDNWOSaccess1 This is the default OS root password for the WOS Access gateway appliance. Use the passwd command to change it.
CIFS
Feature User Password Notes
WebUI admin DDNWOSaccess1 Web interface access. To change this password, refer to please see section 3.6 for instructions.
2.5
Configuring WOS client I/O filters
WOS Access is a NAS gateway to WOS storage. By default, WOS storage does not have any client I/O filters which means it allows any node to access the data given the Object identifier (OID). However to secure data access, WOS storage provides Administrator the ability to specify IP filters (IP address (or ranges) in CIDR format) in its management GUI to restrict hosts that can do I/O. As a security best practice you could set the I/O filters in the WOS to restrict the data access from the specific WOS Access nodes.
2.6
Verify WOS Access network connections between WOS Access Nodes and
WOS Core
A misconfigured network or networking issues between WOS Access server and WOS Core may lead to an overflow of staging area on NFS Server. Check and ensure networking settings on all servers and switches are properly configured and acceptable network connectivity and performance.
2.7
Adding a Mellanox ConnectX-3 Networking Card
If the WOS Access Server does not have a Mellanox ConnectX 3 card installed during the WOS Access ISO install and it is added to the system, the Mellanox card will not be recognized as an Ethernet adapter. The fix is to execute the
/sbin/connectx_port_config script from the shell prompt and select the Ethernet
option. This configures the Mellanox card to be the Ethernet adaptor. Next, restart the Mellanox driver by executing /etc/init.d/openibd restart from the shell prompt.
3.0
WEB Configuration Procedure
3.1
WEB Configuration Steps
The WOS Access configuration procedure has two variants: • Single WOS Access server
• Multiple WOS Access servers. This includes Services Relocation. The multiple WOS sites have a synchronized name space
3.1.1
Single WOS Access Server
If you have a single WOS Access server, perform: 1. WOS Storage Policy Configuration (Section 3.3) 2. WOS Access NFS Configuration (Section 3.4) 3. WOS Access CIFS Configuration (Section 3.6)
4. WOS Access Disaster Recovery Configuration (Section 3.7)
3.1.2
Multiple WOS Access Servers
If you have multiple WOS Access servers (two or more), perform either step 1 or 2 and then step 3:
1. Create a new replication group (Namespace Synchronization) on first (head) server: a. WOS Access Configuration (Section 3.3)
b. WOS Access NFS Configuration (Section 3.4) c. WOS Access CIFS Configuration (Section 3.6 )
d. WOS Access Namespace Synchronization Configuration (Section 3.4 ) 2. Join existing replication group (Namespace Synchronization):
a. WOS Access Configuration (Section 3.3 )
b. WOS Access Namespace Synchronization Configuration (Section 3.4 ) c. Join Existing Replication Group (Section 3.4.3 )
d. WOS Access NFS Configuration (Section 3.4 ) e. WOS Access CIFS Configuration (Section 3.6 )
3. After creating or joining existing replication group configure DR and SR: a. WOS Access Disaster Recovery Configuration (Section 3.7)
b. WOS Access Services Relocation Service Configuration (Section 3.8)
3.2
WOS Access Login Page
Access the administration user interface (Figure 2) with one of the recommended browsers by the web address http://<server_address>/.
Default Web Administration credentials: • user name - admin
• password - DDNWOSaccess1
NOTE: Although the default WEB UI account, “admin”, is PAM managed; you cannot use it to log in via SSH or TTY.
Figure 2 WOS Access Login Screen
Once you have logged in, you will need to configure WOS Access. Select the Configuration tab to access the configuration options (Figure 3).
Figure 3 WOS Access Initial Configuration Screen
3.3
WOS Storage Policy Configuration
To configure access to WOS,
1. Select the Configurebutton (can be grayed out) next to the WOS label on the
Configuration screen (Figure 3). WOS configuration options are now available (Figure 4).
NOTE: The user interface updates both NFS and CIFS configuration files with WOS
parameters at the same time. However, if NFS and CIFS configuration files have different values set, NFS parameters are shown. (If the NFS and CIFS config files are different, you will see an error notification in the Web UI, and this needs to corrected—please contact DDN support.)
Figure 4 WOS Configuration Section
2. On the WOS Configuration section of the screen, select the edit link next to the WOS IP label (Figure 4). You are prompted for an administration password (Figure 5).
Figure 5 Password Prompt Box
3. Enter the password for the WOS Access Administrator and select the Edit button. 4. On the WOS Configuration section of the screen (Figure 4), enter the WOS IP address. 5. Click on the Refresh button (Figure 6) to update the list of available WOS policies.
From the drop-down list, select the WOS policy (Figure 7)that will used to store file data in WOS.
Figure 6 WOS IP Address Configuration
Figure 7 WOS Policy Configuration
Figure 8 Restart NFS/CIFS Services to apply WOS Parameters Message
NOTE: If the list of WOS Policies does not appear, you should set WOS User and WOS Password using the same way described above for WOS IP field.
7. If the WOS Policy in the CIFS and NFS configuration files are different, a warning symbol will appear next to the WOS Policy label. This suggests that one of the configuration files may have been edited manually. In this case, check each
configuration file to ensure that the same WOS IP address and policy is being used in both files.
3.4
WOS Access Namespace Synchronization Configuration for Two Or More
Servers Sharing the Same Namespace or for Service Relocation
If you are deploying a single WOS Access server attached to a single WOS Cluster, this section is optional.
If you are deploying WOS Access with Services Relocation (SR) or with a remote synchronized site, this section is mandatory. The steps needed to set up namespace synchronization are:
1. Configure namespace synchronization
2. Create or join a sync cluster. If creating a new namespace synchronization group, go to Section 3.4.2. To join an existing group, go to Section 3.4.3.
The following requirements must be met before configuring namespace synchronization: • All network interfaces that are used in the cluster configuration must be configured
for IPv4.
• Each WOS Access server hostname must be resolvable by all other WOS Access servers in the replication group. This can be achieved in one of two ways:
1. Register the primary IP address of each WOS Access server with a centralized DNS server. This is the recommended method.
2. Create an entry for each WOS Access server in the /etc/host file on all servers in the replication group.
• All WOS Access servers must use NTP for time synchronization.
• The namespace synchronization scripts use SSH to get the replication states on remote servers. Each WOS Access server must be configured to allow root-level password-less SSH access from all other WOS Access servers. Please refer to your operating system documentation for information on how to configure password-less SSH access to a node. [DE12753]
3.4.1
Configuring Namespace Synchronization
Before running the Namespace Synchronization (NS) service, which performs metadata replication, configure the NS service on each node using Synchronization option (Figure 9). For NS, you can specify these parameters:
• Batch Size • Batch TTL (Days) • Batch Interval
To change the WOS Policy:
1. See Section 3.3 for WOS Policy configuration.
NOTE: You will use the same WOS Policy with CIFS and NFS services. You have to have a separate WOS Policy for Namespace Synchronization Service in order to keep the data related to the namespace synchronization separate from the file system data from CIFS and NFS.
2. Select edit from Synchronization pane (Figure 9), and enter in the WOS Access Administrator password (Figure 5), and press the Edit button.
Figure 9 Synchronization option
3. Select your WOS Sycnronization Policy, which is different from the WOS Config Policy (Figure 10), and press the Apply button
Figure 10 WOS Synchronization option
4. On the Restart Notification Message (Figure 11), select the OK button to continue.
Figure 11 Restart Notification Message
5. On the Synchronization screen (Figure 9), you can configure these parameters by selecting the edit link next to the parameter:
• Batch Size • Batch TTL (Days) • Batch Interval.
3.4.2
Creating New Replication Group
Before a new replication group can be created, the following precondition must be met: • The node cannot already be joined to a replication group.
2. On the Join Replication Group window, select the Create new Replication
Group radio button.
3. Select the OK button (Figure 12).
Figure 12 Join Replication Group Window: Create New Replication Group
After creating a new group, The Stop button replaces the Start button in the New Replication Group Synchronization section (Figure 13).
Figure 13 Namespace Synchronization Started
3.4.3
Join Existing Replication Group
Before a WOS Access node can join an existing replication group, the following preconditions must be met:
• The NFS, CIFS and Synchronization services must be stopped on the local node. • The database on the local node must be empty. This can be verified by running the
following command and checking that the output matches:
# psql -Uovfs -c "select count(*) from handle" count
0 (1 row)
If the command output does not match the above, then the database must be reinitialized before proceeding, using the following commands:
# psql -U postgres –c “DROP DATABASE ovfs” # /opt/ddn/nas/etc/ovfsdb_install_nfs.sh
• The CIFS, NFS, and Synchronization services must be running on the primary node in the existing replication group. The primary node is the node on which the replication group was created.
To join an existing replication group:
2. In the Join Replication Group window, select Join existing Replication
Group radio-button (Figure 14).
3. In the text input box, enter the hostname of the primary node in the replication group. Only a hostname may be entered—do not use an IP address.
4. Select the OK button.
Figure 14 Join Existing Replication Group
If the attempt to join the replication group fails, please refer to the Troubleshooting section of this guide for help in diagnosing the issue.
After creating a new group, The Stop button replaces the Start button in the New
Replication Group Synchronization section (Figure 12).
To check the status of the replication group, select the Synchronization tab (Figure 15). Figure 15 Synchronization Tab
NFS and CIFS services will need to be started. NFS mounts will not appear on the secondary nodes, you will need to either add those mounts on the secondary nodes, or configure an SR pair.
3.5
WOS Access NFS Configuration
If your node needs to join an existing replication group, you must perform Namespace Synchronization Configuration before you configure NFS and CIFS service.
Figure 16 WOS NFS Configuration Section
To configure NFS:
1. Enter the required number of workers.
2. Select the Apply button and click on Ok when the restart message appears (Figure
17).
Figure 17 Restart Service Confirmation Screen
3.5.1
Creating NFS Export Points
This section will review the steps necessary to manage NFS export points.
NOTE: Unlike CIFS export points, NFS export points will not be synchronized across all members of a namespace synchronization group. NFS exported mounts are only synchronized between members of a Service Relocation pair. If the gateway node belongs to a synchronization group, then the export will need to be configured on the other nodes in the group as well, after time has been allowed for database synchronization to occur.
You must specify these parameters to create the NFS export point:
• Export Name—this is the name to be used when mounting the export from the NFS client
• File System Path—this is the WOS Access namespace path associated with the export point, relative to /mnt
To create the NFS export point:
1. On the Export List section under the Configuration tab (Figure 18), select the
Add new button.
3. Enter the File System Path, for example, sharedfolder. 4. Select the Enable Export via NFS checkbox. Figure 18 NFS Export Point Sample Screen
3.5.2
NFS Protocol Configuration
WOS Access allows administrators to specify NFS protocol version access on a per-export basis. The following protocols are currently supported:
• NFSv3 • NFSv4
By default, NFS exports are configured for both NFSv3 and NFSv4. Use the checkboxes to add or remove protocol support.
3.5.3
NFS Security Configuration
WOS Access NFS provides the following security capabilities: • Namespace access at the export level
• Access authorization at the host/client level • Root access at the host/client level
• Unix system authentication and authorization at the file level
WOS Access provides the following options for securing access at the export level. These options apply to all users, groups and host systems.
• Read-Only – File data and metadata is read-only, regardless of permissions.
• Read/Write (default) – File data and metadata accessibility is dictated by file/folder permissions.
• Metadata Only – Read-Only – File data cannot be accessed in any way. File/folder attributes can only be read.
• Metadata Only - Read/Write – File data cannot be accessed in any way. File/folder metadata accessibility is dictated by file/folder permissions.
WOS Access also provides the ability to control export access at the host or client level. The default configuration allows any client to access the export but users attempting to access the export as root will have read-only access.
Figure 20 Granting Client and Root Access to those specified
Host entries can be specified as IP addresses or hostnames, using the ‘*’ or ‘?’ wildcards. Ranges can be specified using brackets (such as ‘[3-9]’).
Once all host entries have been added, click on the Apply button to create the export point. Click on the OK button in the dialog box to confirm creation and then restart the NFS service to make the export available to NFS clients.
3.5.4
Delete NFS Export Point
To delete an NFS export, select the bold red next to the edit link (Figure 21) in the Export List. Confirm the deletion by selecting OK at the Delete Confirmation prompt.
Figure 21 Edit/Delete NFS Export Points
3.5.5
Start NFS Service
To start the NFS service, select the Start button on NFS section (Figure 22). Figure 22 Start NFS Service
If there are no errors, the NFS section will indicate that NFS has started (Figure 23) by showing the option to stop the service.
Figure 23 NFS Service Status
3.6
WOS Access CIFS Configuration
If your node needs to join an existing replication group, you must perform Namespace Synchronization Configuration before you configure the NFS and CIFS services.
The Configuration screen presents two sections:
• Export List section to create, modify, and delete CIFS export points (Figure 24) • CIFS section to modify CIFS service status and configuration (Figure 25) Use the CIFS and Export List sections to:
• Check status of CIFS service • Start, stop, or restart CIFS service • Modify CIFS service configuration • Join or leave Active Directory Domain
• Add, modify, or delete CIFS export points
Figure 24 Export List section of the Configuration tab
Figure 25 CIFS section of Configuration tab
3.6.1
Changing CIFS Service Status
NOTE: You must properly configure the WOS IP and the WOS policy before starting the CIFS service.
On the CIFS service section (Figure 25):
• Select the Start button to start the CIFS service. • Select the Restart button to restart the CIFS service.
• Select the Stop button to stop the CIFS service if it is running (Figure 26).
Figure 26 CIFS Service Running Status
As the CIFS service changes its status, the CIFS status icon automatically changes and presents the new status and valid buttons. For example, if the CIFS service is not running,
3.6.2
Changing CIFS Service Configuration
NOTE: CIFS service must be restarted to apply changes
To change the default CIFS user password for Administrator (Figure 27): 1. Select the edit link next to the Administrator Password label.
2. Enter the new password (case-sensitive) in the revealed edit box. 3. Select the Apply button.
Figure 27 CIFS Service Configuration Screen
To change space for CIFS cache (Figure 27): 1. Either:
a. Enter the new limit in the edit box next to the Staging Limit (MB) label.
b. Or select the checkbox Unlimited.
2. Select the Apply button.
3. On the Confirmation Message popup window (Figure 28), select the OK button.
To enable Data Integrity Check (Figure 27): 1. Select the appropriate checkbox. 2. Select the Apply button.
3. On the Confirmation Message popup window (Figure 28), select the OK button.
To disable Data Integrity Check (Figure 27):
1. Select the checked Data Integrity Check checkbox to remove the check. 2. Select the Apply button.
To cancel changes, select the Cancel button instead of the Apply button on the CIFS Service Configuration Screen.
Figure 28 Confirmation Message to confirm changes to CIFS Service Configuration
3.6.3
Creating, Modifying, and Deleting CIFS Export Points
This section will review the steps necessary to manage CIFS export points.
NOTE: CIFS export points will automatically be synchronized across all members of a namespace synchronization group. Export points should only be created on one node of a synchronization group.
To create a new export point via CIFS:
1. Select the Add new button on the Export List section of the Configuration tab screen
(Figure 25).
2. Once this section expands, select the Enable Export via CIFS checkbox.
3. On the expanded CIFS configuration section (Figure 29), enter a CIFS export point name (case-insensitive) in the edit box under the Export Name label.
Figure 29 Create New Export Point via CIFS
4. Enter new or existing relative path (case-insensitive) in the edit box under File System Path.
5. Choose the Access Type, select either Read/Write or Read Only radio button.
6. Check Enable Access Based Enumeration to enable access-based enumeration
support.
NOTE: Access Based Enumeration is set on a per-share basis and when enabled,
displays only those files and folders to which a user has at least read-level permissions. This feature is disabled by default. To enable Access Based Enumeration, use the CIFS configuration section of the WOS Access Web GUI. The actual permissions setting on the files and folder is performed from Windows Client mounting the WOS Access CIFS share.
7. To add users to Allow Access to or Deny Access to the list of CIFS export points:
a. Choose the appropriate new permissions radio button in the Access Permissions section.
b. Enter a username (case-insensitive) in the text field under the Username label.
8. To add more than one user to the list:
a. Select the bold green cross under the appropriate list. b. Enter additional usernames.
9. To remove a user from an access list, press the bold red cross next to the text field with username.
NOTE: You may enter a domain username in the domainusername@FQDN
10. To clear appropriate Permissions List, select the Remove access list radio button.
11. After entering all data and selecting required options, select the Apply button to
create the share.
12. On the Confirmation Message popup window (Figure 30), select the OK button. Figure 30 Success Message
NOTE: Select the Cancel button to prevent the creation of CIFS export point.
To modify a CIFS export point, click the edit link on the line of the CIFS export point you want to modify (Figure 31). The configuration of existing share is same as configuration of new share.
Figure 31 Export list with created CIFS export point
To delete a CIFS share, select the bold red next to the edit link (Figure 31). Confirm the deletion by selecting OK to the Delete Confirmation prompt (Figure 32).
Figure 32 Delete CIFS share point confirmation window
3.6.4
Join Active Directory Domain
Since AD configuration is not propagated automatically to all nodes in an existing cluster, DDN recommends to setup AD configuration on primary synchronization group node before joining other nodes.
When adding a new node to an existing synchronization group where all nodes already joined AD, the AD configuration will be propagated to new node automatically.
In an existing synchronization group, an AD join operation should be performed on each node separately.
To join Active Directory domain:
1. Select the Join button next to the Active Directory label at CIFS section of Configuration screen.
2. At the prompt, enter the Domain FQDN (case-insensitive) and IP address of Domain Controller (Figure 33).
3. Select the Next button.
Figure 33 Join Active Directory – Step 1
4. At the prompt, enter the Domain Administrator’s username and its password. 5. Optionally, select the Synchronize Time checkbox to synchronize time with Domain
Controller (Figure 34).
6. Select the Next button to join the Domain. Figure 34 Join Active Directory – Step 2
Figure 35 JoinActive Domain Result Message
After the host is joined to the Domain, the DC name appears next to the Active Directory label and the Join button has changed to Leave button (Figure 36).
Figure 36 DC name
To leave the active directory domain, select the Leave button. At the prompt (Figure 37),
select the Yes button to leave or Cancel button to stay. Figure 37 Confirm Action to Leave Domain
3.7
WOS Access Disaster Recovery Configuration
The backup service by itself is quite I/O intensive. Therefore, if you run WOS Access SR setup with data replication between nodes, run the Backup service only on the passive node. Leave the Active SR node with backup running.
DDN Recommendation:
Only one active backup service per site
To enable Disaster Recovery, select the Start button on the Backup option line (Figure 38)
on the Configuration tab screen (Figure 3).
Figure 38 Enable Disaster Recovery Backup options Screen
If there are no errors, the Stop button replaces the Start button (Figure 39). Figure 39 Disaster Recovery enabled
3.7.2
Scheduling a Full Backup
To schedule a full backup, from the drop-down menu on the Full Backup Schedule option line, select the number of days and then click the Apply button.
3.8
WOS Access Services Relocation Service Configuration
Configure the Namespace Synchronization Service before configuring Services Relocation.
The Services Relocation (SR) module configuration is only required if you need an active redundancy service. The SR module provides features to monitor and manage these services:
• Heartbeat network – virtual IP of services relocation pair • Database – namespace database
• NFS service – WOS Access service • CIFS service – WOS Access CIFS service
• NFS disk space – service to monitor free space on a specific disk device, which used for NFS cache
• CIFS disk space – service to monitor free space on a specific disk device, which used for CIFS cache
• WOS – service to monitor connection to WOS Storage nodes Before configuring SR, please ensure that these requirements are met:
• The two WOS Access gateway nodesthat will be paired together can be located in different subnets. However, they should still be visible to each other over the network.
• All network interfaces that will be used in an SR configuration should be configured for IPv4.
• Two UDP ports to be used for the Corosync service must be opened over the network. (Refer to AIS_UCASTPORT description in Table 27.)
• Hosts should be visible to each other over the network by hostnames. To achieve this requirement, the hostnames should either be configured by using the corporate DNS server, or be specified in /etc/hosts.
• Hosts should be accessible via SSH without password requirements. • Primary Host has virtual network interface.
Before configuring Services Relocation, first configure the nodes individually per the requirements above. All requirements stated above must be met prior to configuration. Configuration of Services Relocation is only required on one of the two nodes that will be paired together. The other node will be automatically configured.
To configure Services Relocation:
1. Expand the Services Relocation section on the Configuration page of the Web UI (Figure 41).
Figure 40 Services Relocation Section
a. Supported Services - select the NAS services that should be monitored – NFS, CIFS, or both.
b. Local Heartbeat Interface #1 – select the network interface on the local node that will be used as the primary heartbeat link between the two nodes. c. Local Heartbeat Interface #2 – select the network interface on the local node
that will be used as the backup heartbeat link between the two nodes (this setting is optional).
d. Remote Node – specify the hostname of the other node in the SR pair. This must be the real hostname of the other node (as reported from the ‘hostname’
command) not an IP address. After specifying the hostname, click on the “Reload Interfaces” button to load the remote network interfaces.
e. Remote Heartbeat Interface #1 – select the network interface on the remote node that will be used as the primary heartbeat link between the two nodes. f. Remote Heartbeat Interface #2 – select the network interface on the remote
node that will be used as the backup heartbeat link between the two nodes (this setting is optional).
g. Virtual IP Address - enter the IP address that will be used for providing NAS services. If services fail on the primary node, this IP address will be migrated to the secondary node.
h. Virtual IP Mask- enter the network mask to be used by the Virtual IP address, either as a number in the range [1..31] or in IP format (i.e. 255.255.255.0). i. Virtual IP Interface – select the network interface that will be used to host the
Virtual IP Address. The interface must be present on both the local node and the remote node.
j. Primary Node – select the node that will host the Virtual IP Address when the SR service is started.
k. Select the Apply button to save the configuration changes to both the local
node and the remote node.
2. On the Services Relocation Restart Notification window (Figure 41), select the OK
button to confirm and continue.
Figure 41 Services Relocation Restart Notification Message
To create the Services Relocation pair and start the service: 1. On the Services Relocation section, select the Start button.
2. After creating an SR pair, the Stop button replaces the Start button in the Services
Relocation section on the Primary and Secondary hosts (Figure 42).
Figure 42 Services Relocation Group Created
3.9
WOS Access Preferences
Use the WOS Access Preferences screen (Figure 43) to configure the settings for: • email alerts,
• credentials (login password), • exporting syslog
Figure 43 WOS Access Preferences Tab Screen
3.9.1
Changing Email Alerts Preferences
To configure email notifications, access the Email Alerts section on the Preferences tab screen (Figure 44).
To configure email notifications about backup events, select the Backup Notifications
checkbox.
To configure email notifications about CIFS service events, select the CIFS Notifications
checkbox.
To receive email notifications:
1. In the Mail Server box, enter hostname (case-insensitive) or IPv4 address of mail
server which accepts SMTP requests. Required.
NOTE: You may use the hostname, “localhost” here if the Mail Server allows for unauthenticated message delivery and the MX DNS record points to an address that can be reached from the WOS Access node.
2. Optionally, to set the subject of email notifications, enter text in the Subject box.
3. In the From user box, enter the username (case-insensitive) to be used to send email
notifications via mail server. Required.
4. In the Notification E-mail, enter the email address which will receive notifications.
Required.
5. To add some additional addresses, select the Add new button in Email Alerts section
and enter email address in the box which appears.
6. To remove email address from notification list, select the bold red x next to appropriate editbox.
7. To validate your email preferences settings, select the Send Test Email button. This
generates a test email message using the values you have entered. A message window with the results of the test email sending operation is displayed (Figure 45).
Figure 45 Email test status message
To refuse to change email preferences, select the Cancel button on Email Alerts section.
To save email preferences, select the Apply button. Message with results of changing email
preferences appears (Figure 46). Select the OK button to continue. Figure 46 Change Status Message
3.9.2
Changing Credentials
Note: The default password of WOS Access Web UI admin is DDNWOSaccess1. To change the password of WOS Access Web UI administrator:
1. On the Credentials section of the Preferences screen (Figure 47), enter the current password (case-sensitive) in the Current Password box.
2. Enter the new password (case-sensitive) in the New Password box. 3. Enter the new password (case-sensitive) in the Retype Password box.
Figure 47 Credentials section of Preferences screen
To keep the current password, select the Cancel button.
To save the new admin password, select the Apply button. Notification of changes message
appears(Figure 48); select the OK button to confirm and continue. Figure 48 Notification of Changes Message
3.9.3
Changing User Interface Preferences
To change the Auto-Refresh Data interval, select the appropriate interval from the dropdown menu on the User Interface Preferences section on the Preferences screen (Figure 49).
Figure 49 User Interface Preferences
To keep the current auto-refresh data interval, select the Cancel button.
To save the new auto-refresh data interval, select the Apply button. Notification of changes
message appears (Figure 50); select the OK button to confirm and continue. Figure 50 Notification of Changes Message
3.9.4
Changing Exporting syslog
To push syslog messages to a remote server using the syslog daemon, at the Exporting syslog section of the Preferences page (Figure 51), select the Add new button.
In the revealed Facility and Severity drop-boxes, select the appropriate values.
In the Export Address box, enter the IPv4 address of the remote machine that is running rsyslog.
Figure 51 Exporting syslog section of Preferences screen
To refuse to push syslog messages to export address, click the bold red cross next to appropriate edit box.
To refuse to change exporting syslog preferences, click the Cancel button.
To save exporting syslog preferences, select the Apply button. Notification of changes
message appears (Figure 52); select the OK button to confirm and continue. Figure 52 Notification of Changes Message
4.0
Web Administration Reference
You can access the administration user interface using any web browser client http://<server_address>/.
Default Web Administration credentials: • user name ‘admin’
• password ‘DDNWOSaccess1’. Recommended versions of browsers:
• Internet Explorer l0 • Firefox 27
• Chrome 33
These sections provide basic information regarding features exposed via the User Interface. refer to the administrative guides of respective services for the most detailed and up-to-date configuration and usage information.
4.1
General Navigation
There are six areas in Administrative UI (represented on the tabs in Figure 53 and explained in Table 2): • Summary • Synchronization • Services • Configuration • Preferences • Logs
Figure 53 WOS Access UI Screen
Table 2 Administrative User Interface Tabs Service Document
Summary Provides summary view of the cluster statistics and node system information.
Synchronization Provides real-time view of synchronization process. Services Summary for all WOS Access services.
Service Document
Logs Provides access to service logs.
4.2
Status Icons
Administrative User Interface uses unified icons to display service statuses across different pages (Table 3). Administrator may see such icons as part of other icons (Figure 54), but they will still mean exactly the same status everywhere.
Figure 54 Status Icons
Table 3 Service Status Icons
Service Icon Description
Service is not installed.
Service is started active.
Service is stopped / inactive.
Service is in idle state (only applies to Services-Relocation Service).
Service state is unknown.
4.3
User Interface
This section discusses the User Interface (UI).
4.3.1
Summary Screen
A sample Summary tab screen is shown in Figure 55.
Figure 55 User Interface (UI) sample screen
4.3.1.1 Service Status
Service Status displays information about: • Uptime and status of these services
o NFS Server o CIFS Server
o Services-Relocation o Synchronization o Backup
outgoing queue holds file system changes sent to all other nodes in the WOS Access cluster and they will be kept in the outgoing queue until target servers confirm that they processed those changes:
o Low and steady numbers during operations with file systems indicate that file systems on different nodes are kept in sync with minimal timeout.
o A high number in incoming queue indicates that current WOS Access node is behind the file system changes done on remote nodes. And it may take some time for it to get synchronized
o A high number in outgoing queue indicates that some or all remote nodes have large numbers of changes, which they have not applied to their file systems yet. o A growing number in the incoming queue means that the local WOS Access
node is lagging behind since it cannot process all changes from other nodes at the same rate that they arrive.
o A growing number in outgoing queue means that remote nodes do not send confirmations for processed changes and that they are lagging behind. o Zeros in the queues indicate that there is no activity which changes a file
system. It does not mean there is no activity at all. For example, reading a file does not change a file system.
4.3.1.2 Storage Statistics
The Storage Statistics are represented with a pie chart. The legend at the left of the pie chart gives the colors’ meanings, and shows relative values for used and free space:
• Total/Active Nodes. The number of Total and Active Nodes • Object Count. Displays number of objects stored
• Capacity / Used Capacity / Free Capacity. Displays storage usage information • Cluster Data represents space used by file objects stored by WOS Access cluster • Synchronization displays space used by Synchronization service to transmit file
system changes between nodes in WOS Access cluster
• Other WOS Consumers shows space used by any other client applications, which may also use the same WOS Cluster.
NOTE: The system distinguishes the objects stored by the different clients based on the WOS policy used. If all clients use the same policy Cluster Data,
4.3.1.3 System Charts: Protocols
The Protocols chart (Figure 56) displays CPU usage by WOS Access protocols (NFS and CIFS) and staging storage usage.
Figure 56 WOS Storage Protocols
4.3.1.4 System Charts: WOS Storage
The WOS Storage chart (Figure 57) displays performance characteristics for WOS Cluster: • Rate
Displays number of Read, Write and Delete operations per second going through WOS Cluster
• Throughput
• Displays Read, Write and Delete operations going through WOS Cluster • Latency in milliseconds
Figure 57 WOS Storage Chart
4.3.1.5 System Charts: Synchronization
The System Synchronization chart displays number of messages in incoming and outgoing queues. Refer to page 52 in section 4.3.1.1 for queue details).
Figure 58 System Synchronization Chart
4.3.1.6 System Charts: System
The System chart displays the system characteristics: • Memory usage
• CPU usage
