IBM System Storage N series Data ONTAP 7 2 Commands Manual Page Reference, Volumes 2

IBM System Storage N seriesData ONTAP 7.2 Commands Manual Page

Reference, Volume 2

GC26-7972-04 NA 210-03868_A0Updated for Data ONTAP 7.2.4

Table of Contents ..... 7About the Data ONTAP Commands: Manual Page Reference, Volume 2... 9Manual Pages by Section in This Volume and Complete Index of Both Volumes..................... 18tape.................... 21auditlog................... 23backuplog..................... 26boot.................. 27cifs_homedir.cfg.................. 29cifs_nbalias.cfg................... 31cloned_tapes.................... 32crash................... 33dgateways................... 34dumpdates.................... 35exports.................... 45fsecurity.................... 47ftpusers.................... 48group..................... 49hosts................... 50hosts.equiv................... 51httpd.access................... 53httpd.group................. 54httpd.hostprefixes.................... 56httpd.log.................. 58httpd.mimetypes................... 59httpd.passwd................. 60httpd.translations.................... 62messages................... 63ndmpdlog.................... 66netgroup.................... 68networks................... 69nsswitch.conf.................. 70nvfail_rename.................... 71passwd.................... 73psk.txt................... 74qual_devices.................... 75quotas..................... 79rc.................... 80registry................... 82resolv.conf.................... 83rmtab................... 84serialnum.................... 85services.................... 86shadow..................... 87sis..................... 90sm

Data ONTAP 7.2 Commands: Manual Page Reference, Volume 2 i

.................... 91snapmirror

................... 99snapmirror.allow

................... 101snapmirror.conf

.................... 106stats_preset

.................. 110symlink.translations

..................... 112syslog.conf

.................... 115tape_config

.................... 116treecompare

.................... 120usermap.cfg

..................... 122zoneinfo

.................... 124autosupport

...................... 134cifs

....................... 135cli

...................... 137dns

...................... 139http

...................... 140nfs

...................... 141nis

...................... 142pcnfsd

.................... 143protocolaccess

...................... 146rmt

..................... 149rquotad

...................... 150rshd

...................... 151snmpd

..................... 153syslogd

ii Data ONTAP 7.2 Commands: Manual Page Reference, Volume 2

Copyright and trademark information

Copyright information

Copyright © 1994–2007 Network Appliance, Inc. All rights reserved. Printed in the U.S.A.

Portions copyright © 2006, 2007 IBM Corporation. All rights reserved.

Portions © 1998–2001 The OpenSSL Project. All rights reserved.

No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner.

Portions of this product are derived from the Berkeley Net2 release and the 4.4-Lite-2 release, which are copyrighted and publicly distributed by The Regents of the University of California.

Copyright © 1980–1995 The Regents of the University of California. All rights reserved.

Portions of this product are derived from NetBSD, copyright © Carnegie Mellon University.

Copyright © 1994, 1995 Carnegie Mellon University. All rights reserved. Author Chris G. Demetriou.

Permission to use, copy, modify, and distribute this software and its documentation is hereby granted, provided that both the copyright notice and its permission notice appear in all copies of the software, derivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation.

CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.

Software derived from copyrighted material of The Regents of the University of California and

Carnegie Mellon University is subject to the following license and disclaimer:

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notices, this list of conditions, and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notices, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

All advertising materials mentioning features or use of this software must display the following acknowledgment:

This product includes software developed by the University of California, Berkeley and its contributors.

Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FO RANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

Copyright and trademark information iii

SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Portions of the software were created by Netscape Communications Corp. The contents of those portions are subject to the Netscape Public License Version 1.0 (the "License"); you may not use those portions except in compliance with the License. You may obtain a copy of the License at http://www.mozilla.org/NPL/.

Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License.

The Original Code is Mozilla Communicator client code, released March 31, 1998.

The Initial Developer of the Original Code is Netscape Communications Corp. Portions created by Netscape are Copyright © 1998 Netscape Communications Corp. All rights reserved.

This software contains materials from third parties licensed to Network Appliance Inc. which is sublicensed, and not sold, and title to such material is not passed to the end user. All rights reserved by the licensors. You shall not sublicense or permit timesharing, rental, facility management or service bureau usage of the Software.

Portions developed by the Apache Software Foundation (http://www.apache.org/). Copyright © 1999 The Apache Software Foundation.

Portions Copyright © 1995–1998, Jean-loup Gailly and Mark AdlerPortions Copyright © 2001, Sitraka Inc.Portions Copyright © 2001, iAnywhere SolutionsPortions Copyright © 2001, i-net software GmbHPortions Copyright © 1995 University of Southern California. All rights reserved.Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of Southern California, Information Sciences Institute. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission.

Portions of this product are derived from version 2.4.11 of the libxml2 library, which is copyrighted by the World Wide Web Consortium.

Network Appliance modified the libxml2 software on December 6, 2001, to enable it to compile cleanly on Windows, Solaris, and Linux. The changes have been sent to the maintainers of libxml2. The unmodified libxml2 software can be downloaded from http://www.xmlsoft.org/.

Copyright © 1994–2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/.

Software derived from copyrighted material of the World Wide Web Consortium is subject to the following license and disclaimer:

Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make:

iv Copyright and trademark information

The full text of this NOTICE in a location viewable to users of the redistributed or derivative work

Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright © [$date-of-software] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"

Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URLs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.

Software derived from copyrighted material of Network Appliance, Inc. is subject to the following license and disclaimer:

Network Appliance reserves the right to change any products described herein at any time, and without notice. Network Appliance assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by Network Appliance. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of Network Appliance.

The product described in this manual may be protected by one or more U.S.A. patents, foreign patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM, the IBM logo, AIX, System Storage. NetApp, the Network Appliance logo, the bolt design, NetApp–the Network Appliance Company, DataFabric, Data ONTAP, FAServer, FilerView, FlexClone, FlexVol, Manage ONTAP, MultiStore, NearStore, NetCache, SecureShare, SnapDrive, SnapLock, SnapManager, SnapMirror, SnapMover, SnapRestore, SnapValidator, SnapVault, Spinnaker Networks, SpinCluster, SpinFS, SpinHA, SpinMove, SpinServer, SyncMirror, Topio, VFM, and WAFL are registered trademarks of Network Appliance, Inc. in the U.S.A. and/or other countries. Cryptainer, Cryptoshred, Datafort, and Decru are registered trademarks, and Lifetime Key Management and OpenKey are

Copyright and trademark information v

trademarks, of Decru, a Network Appliance, Inc. company, in the U.S.A. and/or other countries. gFiler, Network Appliance, SnapCopy, Snapshot, and The evolution of storage are trademarks of Network Appliance, Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries. ApplianceWatch, BareMetal, Camera-to-Viewer, ComplianceClock, ComplianceJournal, ContentDirector, ContentFabric, EdgeFiler, FlexShare, FPolicy, HyperSAN, InfoFabric, LockVault, NOW, NOW NetApp on the Web, ONTAPI, RAID-DP, RoboCache, RoboFiler, SecureAdmin, Serving Data by Design, SharedStorage, Simplicore, Simulate ONTAP, Smart SAN, SnapCache, SnapDirector, SnapFilter, SnapMigrator, SnapSuite, SohoFiler, SpinMirror, SpinRestore, SpinShot, SpinStor, StoreVault, vFiler, Virtual File Manager, VPolicy, and Web Filer are trademarks of Network Appliance, Inc. in the U.S.A. and other countries. NetApp Availability Assurance and NetApp ProTech Expert are service marks of Network Appliance, Inc. in the U.S.A.

Apple is a registered trademark and QuickTime is a trademark of Apple Computer, Inc. in the U.S.A. and/or other countries. Microsoft is a registered trademark and Windows Med ia is a trademark of Microsoft Corporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries.

All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.

Network Appliance is a licensee of the CompactFlash and CF Logo trademarks.

Network Appliance NetCache is certified RealSystem compatible.

vi Copyright and trademark information

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing to:

IBM Director of Licensing IBM Corporation North Castle Drive Armonk, N.Y. 10504-1785 U.S.A.

For additional information, visit the web at: http://www.ibm.com/ibm/licensing/contact/

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. The materials at those web sites are not part of the materials for this IBM product and use of those web sites is at your own risk.

Notices vii

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

If you are viewing this information in softcopy, the photographs and color illustrations may not appear.

viii Notices

About the Data ONTAP Commands: ManualPage Reference, Volume 2The Commands: Manual Page Reference document is a compilation of all the manual (man) pages forData ONTAP commands, special files, file formats and conventions, and system management andservices. It is provided in two volumes, each of which includes a complete index of all man pages inboth volumes.

Manual pages are grouped into sections according to standard UNIX naming conventions and are listedalphabetically within each section. The following tables list the types of information for which DataONTAP provides manual pages and the reference volume in which they can be found.

Contents of Volume 1

Manualpage

sectionSection titles Information related to

1 Commands Storage system administration

Contents of Volume 2

Manualpage

sectionSection titles Information related to

4 Special Files Formatting of media

5 File Formats and Conventions Configuration files and directories

8 System Management and Services

Protocols, service daemons, and systemmanagement tools

Manual pages can also be viewed from the FilerView main navigational page or displayed at the storagesystem command line.

Terminology

Storage systems that run Data ONTAP are sometimes also referred to as filers, appliances, storage appliances, or systems. The name of the graphical user interface for Data ONTAP (FilerView) reflectsone of these common usages.

Data ONTAP 7.2 Commands: Manual Page Reference, Volume 2 7

About the Data ONTAP Commands: Manual Page Reference, Volume 2

The na prefix for manual page names

All Data ONTAP manual pages are stored on the storage system in files whose names are prefixed withthe string "na_" to distinguish them from client manual pages. The prefixed names are used to refer tostorage system manual pages from other manual pages and sometimes appear in the NAME field of themanual page, but the prefixes do not need to be part of commands.

Viewing manual pages in FilerView

To view a manual page in FilerView, complete the following steps:

1. Go to the following URL:

http://filername/na_admin

filername is the name (fully qualified or short) of your storage system or the IP address of thestorage system.

2. Click the manual pages icon.

For more information about FilerView, see the System Administration Guide or FilerView Help.

Viewing manual pages at the command line

To view a manual page for a command at your storage system command line (console), enter the following:

man command

Note: Data ONTAP commands are case sensitive.

To see a list of all commands from the storage system command line, enter a question mark (?) after thehost prompt.

Manual pages about using manual pagesUseful manual pages about using manual pages are the help(1) and the man(1) manual pages. You canuse the man help command to view information about how to display the manual page for aparticular command. You can use the man man command to view information about how to use the man command.

8 Data ONTAP 7.2 Commands: Manual Page Reference, Volume 2

About the Data ONTAP Commands: Manual Page Reference, Volume 2

Manual Pages by Section in This Volume andComplete Index of Both VolumesManual Pages By Section

Section 4: Special Files

Using device files such as tape.

[ Section 1 | Section 4 | Section 5 | Section 8 | Complete Index ]

tape information on the tape interface

Section 5: File Formats and Conventions

Formats for human-readable configuration files, such as those found in /etc on the root volume.


auditlog contains an audit record of recent administrative activity backuplog captures significant events during file system backup/recovery activities. boot directory of Data ONTAP executables cifs_homedir.cfg configuration file for CIFS home directories cifs_nbalias.cfg configuration file for CIFS NetBIOS aliases cloned_tapes list of nonqualified tape drives attached to the filer crash directory of system core files dgateways default gateways list dumpdates data base of file system dump times

exports a list of export entries for all file system paths that Data ONTAP exportsautomatically when NFS starts up.

fsecurity Definition file for an fsecurity job ftpusers file listing users to be disallowed ftp login privileges group group file hosts host name data base hosts.equiv list of hosts and users with rsh permission httpd.access authentication controls for HTTP access httpd.group names of HTTP access groups and their members httpd.hostprefixes configuration of HTTP root directories for virtual hosts httpd.log Log of HTTP httpd.mimetypes map of file suffixes to MIME ContentType httpd.passwd file of passwords required for HTTP access httpd.translations URL translations to be applied to incoming HTTP requests


Manual Pages by Section in This Volume and Complete Index of Both Volumes

messages record of recent console messages

ndmpdlog The ndmpdlog provides a detailed description of the activities of allactive NDMP sessions.

netgroup network groups data base networks network name data base nsswitch.conf configuration file for name service switch nvfail_rename Internet services passwd password file psk.txt pre-shared authentication key file qual_devices table of qualified disk and tape devices quotas quota description file rc system initialization command script registry registry database resolv.conf configuration file for domain name system resolver rmtab remote mounted file system table serialnum system serial number file services Internet services shadow shadow password file sis Log of Advanced Single Instance Storage (SIS) activities sm network status monitor directory snapmirror Log of SnapMirror Activity snapmirror.allow list of allowed destination filers snapmirror.conf volume and qtree replication schedules and configurations stats_preset stats preset file format symlink.translations Symbolic link translations to be applied to CIFS path lookups syslog.conf syslogd configuration file tape_config directory of tape drive configuration files treecompare Log of treecompare activities usermap.cfg mappings between UNIX and Windows NT accounts and users zoneinfo time zone information files

Section 8: System Management and Services

Protocols and service daemons, such as rshd and snmpd, and system management tools, such as autosupport and syslogd.




autosupport notification daemon cifs Common Internet File System (CIFS) Protocol cli Data ONTAP command language interperter (CLI) dns Domain Name System http HyperText Transfer Protocol nfs Network File System (NFS) Protocol nis NIS client service pcnfsd (PC)NFS authentication request server protocolaccess Describes protocol access control rmt remote magtape protocol module rquotad remote quota server rshd remote shell daemon snmpd snmp agent daemon syslogd log system messages

Man Page Complete Index

adconfig (1) Configuration tool for ATM devices adinfo (1) show ATM device information adstat (1) show ATM device driver statistic

aggr (1) commands for managing aggregates, displaying aggregate status, andcopying aggregates

arp (1) address resolution display and control atm (1) summary of atm commands atm_adconfig (1) Configuration tool for ATM devices atm_adinfo (1) show ATM device information atm_adstat (1) show ATM device driver statistics atm_atmarp (1) manipulate FORE IP Internet-to-ATM address mappings atm_atmconfig (1) FORE IP configuration tool atm_elarp (1) display or manipulate MAC to ATM address mappings atm_elconfig (1) ATM Forum LAN Emulation configuration tool atm_uniconfig (1) UNI configuration tool for ATM devices atmarp (1) manipulate FORE IP Internet-to-ATM address mappings atmconfig (1) FORE IP configuration tool atmfmbstat (1) Display Fore/IP Memory Statistics auditlog (5) contains an audit record of recent administrative activity autosupport (8) notification daemon backup (1) manages backups backuplog (5) captures significant events during file system backup/recovery activities. bmc (1) commmands for use with a Baseboard Management Controller (BMC)



boot (5) directory of Data ONTAP executables bootfs (1) boot file system accessor command (ADVANCED) cf (1) controls the takeover and giveback operations of the filers in a cluster charmap (1) command for managing per-volume character maps cifs (1) summary of cifs commands cifs (8) Common Internet File System (CIFS) Protocol cifs_access (1) modify share-level access control or Windows machine account access cifs_adupdate (1) update the filer’s account information on the Active Directory server cifs_audit (1) Configure CIFS auditing. cifs_broadcast (1) display a message on user workstations cifs_changefilerpwd (1) schedules a domain password change for the filer cifs_comment (1) display or change CIFS server description cifs_domaininfo (1) display domain type information cifs_help (1) display help for CIFS-specific commands cifs_homedir (1) Manage CIFS home directory paths. cifs_homedir.cfg (5) configuration file for CIFS home directories cifs_lookup (1) translate name into SID or vice versa cifs_nbalias (1) Manage CIFS NetBIOS aliases. cifs_nbalias.cfg (5) configuration file for CIFS NetBIOS aliases cifs_prefdc (1) configure and display CIFS preferred Domain Controller information cifs_resetdc (1) reset CIFS connection to Domain Controller cifs_restart (1) restart CIFS service cifs_sessions (1) information on current CIFS activity cifs_setup (1) configure CIFS service cifs_shares (1) configure and display CIFS shares information cifs_sidcache (1) clears the CIFS SID-to-name map cache cifs_stat (1) print CIFS operating statistics cifs_terminate (1) terminate CIFS service cifs_testdc (1) test the Filer’s connection to Windows NT domain controllers cifs_top (1) display CIFS clients based on activity cli (8) Data ONTAP command language interperter (CLI) cloned_tapes (5) list of nonqualified tape drives attached to the filer config (1) command for configuration management crash (5) directory of system core files date (1) display or set date and time dd (1) copy blocks of data df (1) display free disk space dgateways (5) default gateways list disk (1) RAID disk configuration control commands disk_fw_update (1) update disk firmware



disktest (1) Disk Test Environment dlm (1) Administer Dynamically Loadable Modules dns (1) display DNS information and control DNS subsystem dns (8) Domain Name System download (1) install new version of Data ONTAP dump (1) file system backup dumpdates (5) data base of file system dump times echo (1) display command line arguments elarp (1) display or manipulate MAC to ATM address mappings elconfig (1) ATM Forum LAN Emulation configuration tool ems (1) Invoke commands to the ONTAP Event Management System enable (1) DEPRECATED, use na_license(1) instead environ (1) DEPRECATED, please use the na_environment(1) command instead. environment (1) display information about the filer’s physical environment

exportfs (1) exports or unexports a file system path, making it available orunavailable, respectively, for mounting by NFS clients.

exports (5) a list of export entries for all file system paths that Data ONTAP exportsautomatically when NFS starts up.

fcadmin (1) Commands for managing Fibre Channel adapters. fcdiag (1) Diagnostic to assist in determining source of loop instability

fcp (1) Commands for managing Fibre Channel target adapters and the FCPtarget protocol.

fcstat (1) Fibre Channel stats functions fctest (1) test Fibre Channel environment file (1) manage individual files filestats (1) collect file usage statistics flexcache (1) commands for administering FlexCache volumes floppyboot (1) describes the menu choices at the floppy boot prompt fpolicy (1) configure file policies fsecurity (1) Summary of fsecurity commands fsecurity (5) Definition file for an fsecurity job

fsecurity_apply (1) Creates a security job based on a definition file and applies it to the filesystem.

fsecurity_cancel (1) Cancels outstanding fsecurity jobs fsecurity_help (1) Displays a description and usage information for fsecurity commands fsecurity_remove-guard (1) Removes the Storage-Level Access Guard from a volume or qtree fsecurity_show (1) Displays the security settings on files and directories fsecurity_status (1) Displays the status of outstanding fsecurity jobs ftp (1) display ftp statistics ftpd (1) file transfer protocol daemon ftpusers (5) file listing users to be disallowed ftp login privileges



group (5) group file halt (1) stop the filer help (1) print summary of commands and help strings hostname (1) set or display filer name hosts (5) host name data base hosts.equiv (5) list of hosts and users with rsh permission http (8) HyperText Transfer Protocol httpd.access (5) authentication controls for HTTP access httpd.group (5) names of HTTP access groups and their members httpd.hostprefixes (5) configuration of HTTP root directories for virtual hosts httpd.log (5) Log of HTTP httpd.mimetypes (5) map of file suffixes to MIME ContentType httpd.passwd (5) file of passwords required for HTTP access httpd.translations (5) URL translations to be applied to incoming HTTP requests httpstat (1) display HTTP statistics ifconfig (1) configure network interface parameters ifinfo (1) display driver-level statistics for network interfaces ifstat (1) display device-level statistics for network interfaces igroup (1) Commands for managing initiator groups

ipsec (1) manipulates the ipsec SP/SA/certificate Databases and displays ipsecstatistics

ipspace (1) ipspace operations iscsi (1) manage iSCSI service iswt (1) manage the iSCSI software target (ISWT) driver keymgr (1) key and certificate management license (1) license Data ONTAP services lock (1) manage lock records logger (1) record message in system logs logout (1) allows a user to terminate a telnet session. lun (1) Commands for managing luns man (1) locate and display reference manual pages maxfiles (1) increase the number of files the volume can hold memerr (1) print memory errors messages (5) record of recent console messages mt (1) magnetic tape positioning and control nbtstat (1) displays information about the NetBIOS over TCP connection ndmpcopy (1) transfers directory trees between filers using NDMP ndmpd (1) manages NDMP service

ndmpdlog (5) The ndmpdlog provides a detailed description of the activities of allactive NDMP sessions.



ndp (1) control/diagnose IPv6 neighbor discovery protocol netdiag (1) perform network diagnostics netgroup (5) network groups data base netstat (1) show network status networks (5) network name data base nfs (1) turn NFS service off and on, or setup Kerberos V5 for NFS nfs (8) Network File System (NFS) Protocol nfsstat (1) display NFS statistics nis (1) display NIS information nis (8) NIS client service nsswitch.conf (5) configuration file for name service switch nvfail_rename (5) Internet services options (1) display or set filer options orouted (1) old network routing daemon partner (1) access the data on the partner in takeover mode passwd (1) modify the system administrative user’s password passwd (5) password file pcnfsd (8) (PC)NFS authentication request server ping (1) send ICMP ECHO_REQUEST packets to network hosts ping6 (1) send ICMPv6 ECHO_REQUEST packets to network hosts pktt (1) controls on-filer packet tracing portset (1) Commands for managing portsets priority (1) commands for managing priority scheduling. priv (1) control per-connection privilege settings protocolaccess (8) Describes protocol access control psk.txt (5) pre-shared authentication key file qtree (1) create and manage qtrees qual_devices (5) table of qualified disk and tape devices quota (1) control filer disk quotas quotas (5) quota description file rc (5) system initialization command script rdate (1) set system date from a remote host reallocate (1) command managing reallocation of files, LUNs, volumes and aggregates reboot (1) stop and then restart the filer registry (5) registry database resolv.conf (5) configuration file for domain name system resolver restore (1) file system restore rlm (1) commmands for use with a Remote LAN Module (RLM) rmc (1) commmands for use with a remote management controller rmt (8) remote magtape protocol module



rmtab (5) remote mounted file system table route (1) manually manipulate the routing table routed (1) network RIP and router discovery routing daemon rquotad (8) remote quota server rshd (8) remote shell daemon rtsold (1) router solicitation daemon san (1) Glossary for IBM specific SAN terms sasadmin (1) Commands for managing Serial Attached SCSI (SAS) adapters. sasstat (1) Commands for managing Serial Attached SCSI (SAS) adapters. savecore (1) save a core dump secureadmin (1) command for secure administration of the appliance. serialnum (5) system serial number file services (5) Internet services setup (1) update filer configuration shadow (5) shadow password file

shelfchk (1) verify the communication of environmental information between diskshelves and the filer

sis (1) Advanced Single Instance Storage (SIS) management. sis (5) Log of Advanced Single Instance Storage (SIS) activities sm (5) network status monitor directory snap (1) manage snapshots snapmirror (1) volume, and qtree mirroring snapmirror (5) Log of SnapMirror Activity snapmirror.allow (5) list of allowed destination filers snapmirror.conf (5) volume and qtree replication schedules and configurations snapvault (1) disk-based data protection snmp (1) set and query SNMP agent variables snmpd (8) snmp agent daemon software (1) Command for install/upgrade of Data ONTAP source (1) read and execute a file of filer commands stats (1) command for collecting and viewing statistical information stats_preset (5) stats preset file format

storage (1) Commands for managing the disks and SCSI and fibre channel adaptersin the storage subsystem.

symlink.translations (5) Symbolic link translations to be applied to CIFS path lookups sysconfig (1) display filer configuration information syslog.conf (5) syslogd configuration file syslogd (8) log system messages sysstat (1) report filer performance statistics tape (4) information on the tape interface



tape_config (5) directory of tape drive configuration files timezone (1) set and obtain the local timezone traceroute (1) print the route packets take to network host treecompare (5) Log of treecompare activities uniconfig (1) UNI configuration tool for ATM device ups (1) controls the monitoring of UPS’ (Uninterruptable Power Supply’(s)) uptime (1) show how long system has been up useradmin (1) Administer filer access controls usermap.cfg (5) mappings between UNIX and Windows NT accounts and users version (1) display Data ONTAP version vfiler (1) vfiler operations vif (1) manage virtual network interface configuration vlan (1) manage VLAN interface configuration

vol (1) commands for managing volumes, displaying volume status, andcopying volumes

vscan (1) control virus scanning for files on the filer wcc (1) manage WAFL credential cache ypcat (1) print values from a NIS database

ypgroup (1) display the group file entries cached locally from the NIS server if NISis enabled

ypmatch (1) print matching values from a NIS database ypwhich (1) display the NIS server if NIS is enabled zoneinfo (5) time zone information files



tapeNAMEna_tape - information on the tape interface

DESCRIPTIONThe Data ONTAP system supports up to 64 local tape drives (tape drives connected directly to thesystem). The tape drive interface follows a UNIX-like device name allowing use of a rewind, norewind or unload/reload device. The device name can be the classic cstnd format, or of the format c.name.d where:

c describes the rewind/unload characteristic of the device. Use r to specify the rewind device, use nrto specify the norewind device, or use ur to specify the unload/reload device. The norewinddevice will not rewind when the tape device is closed. The unload/reload device is used withsequential tape loaders and will unload the current tape volume and attempt to load the next tapevolume (note that the server will wait up to one minute for the next volume to become ready beforeaborting the reload of the next volume). The rewind device will rewind the tape volume tobeginning-of-tape on close.

st the st portion of the device name is always present in the classic format, and is one of the optionsin the name format. It specifies that you are requesting a SCSI tape device.

n the alias number (in decimal) of the tape drive to use. The st and n parameters together - stnconstitute a tape "alias". See the storage alias command for information about tape aliases anddevice addresses.

d the density (or format) to use for tape write operations. Consists of one of the four letters l (low), m(medium), h (high) or a (advanced).

name specifies a tape alias, an electrical name or an IEEE World-Wide Name (WWN) corresponding tothe device. The electrical-name and WWN formats only can contain an optional device LUN(SCSI Logical UNit) parameter expressed as Llun. See the storage alias command for furtherinformation about the format of the name parameter.

Each tape device is automatically associated with an alias. If an alias assignment does not already existat the first discovery of a tape device, the system will create an alias for it. FC devices receive WWNaliases, and SCSI devices receive electrical aliases by default. The alias will remain associated with theWWN or electrical name -- even through boot -- until the alias is changed.

The storage alias and storage unalias commands (q.v.) allow the user to preassign electrical or WWNaddresses to aliases (the devices do not have to exist yet), or to adjust the aliases after automaticassignment. A WWN alias allows an FC device that has been moved from one FC adapter or switchport to another to be located by the system without further intervention. An electrical-name alias allowsa particular address to be persistently allocated to the alias.


tape

EXAMPLESThe density specifications for an Exabyte 8505 8mm drive:

l Exabyte 8200 format, no compression m Exabyte 8200 format with compression h Exabyte 8500 format, no compression a Exabyte 8500 format with compression

Examples of tape drive names:

nrst0l nr.st0.l r.9a.1L1.a ur.switch1:5.h nr.WWN[1:23:456789:012345].m

The sysconfig -t command displays the tape drives on your system, the device alias associated witheach tape device, and the device’s available density settings. The following is an example of the outputfrom a sysconfig command on a system with one tape device attached:

toaster> sysconfig -t

Tape drive (0.6) Exabyte 8505 8mm rst0l - rewind device, format is: EXB-8200 2.5GB nrst0l - no rewind device, format is: EXB-8200 2.5GB urst0l - unload/reload device, format is: EXB-8200 2.5GB rst0m - rewind device, format is: EXB-8200C (w/compression) nrst0m - no rewind device, format is: EXB-8200C (w/compression) urst0m - unload/reload device, format is: EXB-8200C (w/compression) rst0h - rewind device, format is: EXB-8500 5.0GB nrst0h - no rewind device, format is: EXB-8500 5.0GB urst0h - unload/reload device, format is: EXB-8500 5.0GB rst0a - rewind device, format is: EXB-8500C (w/compression) nrst0a - no rewind device, format is: EXB-8500C (w/compression) urst0a - unload/reload device, format is: EXB-8500C (w/compression)

The storage show tape command shows the electrical or WWN name associated with the device andthe corresponding alias:

toaster> storage show tape

Tape Drive: 0.6 Description: Exabyte 8505 8mm Serial Number: IE71E024 World Wide Name: Alias Name(s): st0 Device State: available


tape

SEE ALSOna_sysconfig(1)


tape

auditlogNAMEna_auditlog - contains an audit record of recent administrative activity

SYNOPSIS<logdir>/auditlog

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

DESCRIPTIONIf the option auditlog.enable is on, the system logs all input to the system at the console/telnet shell andvia rsh to the auditlog file. The data output by commands executed in this fashion is also logged toauditlog. Administrative servlet invocations (via HTTP, typically from FilerView) and API calls madevia the ONTAPI interface are also logged to the auditlog. A typical message is:

Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:OUT:date: Wed Feb 9 17:34:09 GMT 2000

This indicates that there was an rsh session around Wed Feb 9 17:34:09 GMT which caused the datecommand to be executed. The user performing the command was root. The type of log is data output bythe system as indicated by the OUT keyword.

Commands typed at the filer’s console or executed by rsh are designated by the IN keyword as in:

Wed Feb 9 17:34:03 GMT [rshd_0:auditlog]: :IN:rsh shell: RSH INPUT COMMAND is date

The start and end of an rsh session are specially demarcated as in

Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:START:rsh shell:orbit.eng.mycompany.com

and

Wed Feb 9 17:34:09 GMT [rshd_0:auditlog]: root:END:rsh shell:

The maximum size of the auditlog file is controlled by the auditlog.max_file_size option. If the filegets to this size, it is rotated (see below).

Every Saturday at 24:00, <logdir>/auditlog is moved to <logdir>/auditlog.0, <logdir>/auditlog.0 ismoved to <logdir>/auditlog.1, and so on. This process is called rotation. Auditlog files are saved for atotal of six weeks, if they do not overflow.

If you want to forward audit log messages to a remote syslog log host (one that accepts syslog messagesvia the BSD Syslog protocol specified in RFC 3164), modify the filer’s /etc/syslog.conf file to forwardmessages from the filer’s "local7" facility to the remote host. Do this by adding a line like:

local7.* @1.2.3.4


auditlog

to /etc/syslog.conf. An IP address has been used here, but a valid DNS name could also be used. Notethat using a DNS name can fail if the filer is unable to resolve the name given in the file. If thathappens, your messages will not be forwarded.

On the log host, you’ll need to modify the syslog daemon’s configuration file to redirect syslog messagetraffic from the "local7" facility to the appropriate configuration file. That is typically done by adding aline similar to the one shown above for the filer:

local7.* /var/logs/filer_auditlogs

Then restart the daemon on the log host, or send an appropriate signal to it. See the documentation foryour log host’s syslog daemon for more information on how to make that configuration change.

FILES

<logdir>/auditlog auditlog file for current week. <logdir>/auditlog.[0-5] auditlog files for previous weeks

SEE ALSOna_syslog.conf(5)


auditlog

backuplogNAMEna_backuplog - captures significant events during file system backup/recovery activities.

SYNOPSIS/etc/log/backup

DESCRIPTIONFiler captures significant dump/restore-related events and the respective times at which they occur. Allevents are recorded in one-line messages in /etc/log/backup.

The following are the events filer monitors:

Start Dump/restore starts.

Restart Restart of a dump/restore.

End Dump/restore completes successfully.

Abort The operation aborts.

Error Dump/restore hits an unexpected event.

Options Logs the options as users specify.

Tape_open Output device is opened successfully.

Tape_close Output device is closed successfully.

Phase_change As dump/restore completes a stage.

Dump specific events:

Snapshot When the snapshot is created or located.


backuplog

Base_dump When a valid base dump entry is located.

Logging events:

Start_logging Logging begins.

Stop_logging Logging ends.

Each event record is in the following format:

TYPE TIME_STAMP IDENTIFIER EVENT (EVENT_INFO)

TYPE Either dmp(dump), rst(restore) or log events.

TIME_STAMP Shows date and time at which event occurs.

IDENTIFIER Unique ID for the dump/restore.

EVENT The event name.

EVENT_INFO Event specific information.

A typical event record message looks like:

dmp Thu Apr 5 18:54:56 PDT 2001 /vol/vol0/home(5) Start (level 0, NDMP)

In the particular example:

TYPE = dmp

TIME_STAMP = Thu Apr 5 18:54:56 PDT 2001

IDENTIFER = /vol/vol0/home(5)

EVENT = Start

EVENT_INFO = level 0, NDMP

All event messages go to /etc/log/backup. On every Sunday at 00:00, backup is roated to backup.0and backup.0 is moved to backup.1 and so on. Up to 6 log files(spanning up to 6 weeks) are kept.


backuplog

The registry option backup.log.enable controls the enabling and disabling of the logging with values on and off respectively. The functionality is enabled by default. (See na_options(1) for how to setoptions.)

FILES

/etc/log/backup backup log file for current week. /etc/log/backup.[0-5] backup log files for previous weeks

SEE ALSOna_options(1)


backuplog

bootNAMEna_boot - directory of Data ONTAP executables

SYNOPSIS/etc/boot

DESCRIPTIONThe boot directory contains copies of the executable files required to boot the filer. The downloadcommand (see na_download(1)) copies these files from /etc/boot into the filer’s boot block, from whichthe system boots.

FILES

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

SEE ALSOna_download(1)


boot

cifs_homedir.cfgNAMEna_cifs_homedir.cfg - configuration file for CIFS home directories

SYNOPSIS/etc/cifs_homedir.cfg

DESCRIPTIONThe configuration file /etc/cifs_homedir.cfg is used to configure home directory paths for users whichaccess the filer using the CIFS network protocol.

EXAMPLEThis is a sample /etc/cifs_homedir.cfg file with one CIFS home directory path. The filer will look for aCIFS home directory for user "Bill" by appending the user’s name to the path. From the example below,the filer will provide user "Bill" a CIFS home directory at /vol/userVol/users/Bill if that directory exists.

# # This file contains the path(s) used by the filer to determine if a # CIFS user has a home directory. See the System Administrator’s Guide # for a full description of this file and a full description of the # CIFS homedir feature. # # There is a limit to the number of paths that may be specified. # Currently that limit is 1000. # Paths must be entered one per line. # # After editing this file, use the console command "cifs homedir load" # to make the filer process the entries in this file. # # Note that the "#" character is valid in a CIFS directory name. # Therefore the "#" character is only treated as a comment in this # file if it is in the first column. # # Two example path entries are given below. # /vol/vol0/users1 # /vol/vol1/users2 # # Actual path entries follow this line. /vol/userVol/users

EFFECTIVEAny changes take effect after running the ‘cifs homedir load’ command.


cifs_homedir.cfg

PERSISTENCEChanges are persistent across system reboots.

FILES/etc/cifs_homedir.cfg

SEE ALSOna_cifs_homedir(1)


cifs_homedir.cfg

cifs_nbalias.cfgNAMEna_cifs_nbalias.cfg - configuration file for CIFS NetBIOS aliases

SYNOPSIS/etc/cifs_nbalias.cfg

DESCRIPTIONThe configuration file /etc/cifs_nbalias.cfg is used to configure NetBIOS aliases for the filer. ANetBIOS alias allows the filer to be accessed by a CIFS client using an alternate name for the filer.

EXAMPLEThis is a sample /etc/cifs_nbalias.cfg file with one NetBIOS alias.

# # This file contains NetBIOS aliases used by the filer. # See the System Administrator’s Guide for a full # description of this file. # # There is a limit to the number of aliases that may be specified. # Currently that limit is 200. # # Aliases must be entered one per line. # # After editing this file, use the console command "cifs nbalias load" # to make the filer process the entries in this file. # # Note that the "#" character is valid in a CIFS NetBIOS alias. # Therefore the "#" character is only treated as a comment in this # file if it is in the first column. # # Actual NetBIOS alias name(s) for the filer follow this line. FILERALIAS01

EFFECTIVEAny changes take effect once CIFS services are restarted



cifs_nbalias.cfg

FILES/etc/cifs_nbalias.cfg

SEE ALSOna_cifs_nbalias(1)


cifs_nbalias.cfg

cloned_tapesNAMEna_cloned_tapes - list of nonqualified tape drives attached to the filer

SYNOPSIS/etc/cloned_tapes

DESCRIPTIONIf you attach a tape drive that IBM has not tested with the filer, enter information about the tape drive inthe /etc/cloned_tapes file. This file enables the filer to register the drive as a clone of a qualifed drive.

If the filer boots with a nonqualified tape drive and the /etc/cloned_tapes file does not exist, the filercreates a sample file, when the first "mt" command for the tape is executed.

Each entry in the /etc/cloned_tapes file corresponds to one tape drive. Specify the entry in one of thefollowing formats:

clone_vendor_id clone_product_id EMULATES vendor_id product_id

clone_product_id EMULATES product_id

The "storage show tape supported" command provides a list the product_id and vendor_id values ofqualified drives.

EXAMPLEThe following entry in the /etc/cloned_tapes file enables the filer to register the Quantum DLT9000tape drive, which has not been tested with the filer, as a clone of the Quantum DLT7000 tape drive:

QUANTUM DLT9000 EMULATES QUANTUM DLT7000

SEE ALSOna_storage(1)


cloned_tapes

crashNAMEna_crash - directory of system core files

SYNOPSIS/etc/crash

DESCRIPTIONIf a filer crashes, it creates a core file in the crash directory. The core files are very useful for findingand fixing bugs in Data ONTAP, so please notify IBM Service and Support of any core files on yourfiler.

See na_savecore(1) for more details about how core files are saved.

FILES

/etc/crash/core.* saved core files /etc/crash/core.*-small compact core file.

/etc/crash/bounds suffix for next core file

/etc/crash/minfree free KB in FS to maintain after savecore

SEE ALSOna_savecore(1)


crash

dgatewaysNAMEna_dgateways - default gateways list

SYNOPSIS/etc/dgateways

DESCRIPTIONThe use of /etc/dgateways file has been deprecated. Either add a static default gateway in /etc/rc orenable router discovery in routed to discover multiple default gateways.

The /etc/dgateways file is used by the old routed command to construct a set of potential defaultgateways. The file comprises a series of lines, each in the following format:

gateway metric

gateway is the name or address of a gateway to be used as a potential default gateway.

metric is a metric indicating the preference weighting of the gateway. 1 is the value to use for highestpreference, 15 for the least. If no value is specified, metric will default to the value 1.

There can be a maximum of 128 valid entries in the /etc/dgateways file - additional ones will beignored, with an error message being displayed. Duplicate gateway names or addresses are not allowed- only the first one encountered in the file will be added by routed to the default gateway table, and theadditional ones will produce error messages.

EXAMPLEHere are typical lines from the /etc/dgateways file:

main_router 1 backup_router 2

SEE ALSOna_rc(5),

NOTESThe use of /etc/dgateways file has been deprecated.


dgateways

dumpdatesNAMEna_dumpdates - data base of file system dump times

SYNOPSIS/etc/dumpdates

DESCRIPTIONThe dump command (see na_dump(1)) uses /etc/dumpdates to keep track of which subtrees have beendumped and when. Each line in dumpdates contains the subtree dumped, the dump level, and thecreation date of the snapshot used by dump. There is only one entry per subtree at a given dump level. dumpdates may be edited to change any of the fields, if necessary.

EXAMPLEThis shows the dumpdate file for a system on which /home and /export are backed up using dump.

/home 0 Tue Nov 2 10:56:27 1993 /export 0 Tue Nov 2 13:51:17 1993 /export 1 Tue Nov 5 18:31:17 1993 /home 1 Tue Nov 5 18:45:27 1993

FILES/etc/dumpdates

SEE ALSOna_dump(1)


dumpdates

exportsNAMEna_exports - a list of export entries for all file system paths that Data ONTAP exports automaticallywhen NFS starts up.

SYNOPSIS/etc/exports

DESCRIPTIONThe /etc/exports file contains a list of export entries for all file system paths that Data ONTAP exportsautomatically when NFS starts up. The /etc/exports file can contain up to 10,240 export entries. Eachexport entry can contain up to 4,096 characters, including the end-of-line character. To specify that anexport entry continues onto the next line, you must use the line continuation character "\".

An export entry has the following syntax:

path -option[,option...]

where path is a file system path (for example, a path to a volume, directory, or file) and option is one ofthe following export options:

actual=pathSpecifies the actual file system path corresponding to the exported file system path. You can use thisoption to move files to new locations without requiring NFS clients to mount new file system paths. Theactual file system path you specify must exist. In addition, the exported file system path you specifymust start with /vol/ or /etc/. For example, you cannot specify an exported file system path that consistsof a single forward slash (/), which would mislead some automounters. Note: NFS v4 does not supportthe actual option.

anon=uid|nameSpecifies the effective user ID (or name) of all anonymous or root NFS client users that access the filesystem path. An anonymous NFS client user is an NFS client user that does not provide valid NFScredentials; a root NFS client user is an NFS client user with a user ID of 0. Data ONTAP determines auser’s file access permissions by checking the user’s effective user ID against the NFS server’s /etc/passwd file. By default, the effective user ID of all anonymous and root NFS client users is 65534.To disable root access by anonymous and root NFS client users, set the anon option to 65535. To grantroot user access to all anonymous and root NFS client users, set the anon option to 0.

nosuidDisables setuid and setgid executables and mknod commands on the file system path. Unless the filesystem is a root partition of a diskless NFS client, you should set the nosuid option to prevent NFSclient users from creating setuid executables and device nodes that careless or cooperating NFS serverusers could use to gain root access.


exports

ro | ro=clientid[:clientid...]Specifies which NFS clients have read-only access to the file system path. To give all NFS clientsread-only access, specify the ro option. Otherwise, specify the ro= option followed by acolon-delimited list of NFS client identifiers. To exclude NFS clients from the list, prepend the NFSclient identifiers with a minus sign (-). Unless you specify the ro, ro=, or rw= option, Data ONTAPuses the rw option, giving all NFS clients read-write access to the file system path.

rw | rw=clientid[:clientid...]Specifies which NFS clients have read-write access to the file system path. To give all NFS clientsread-write access, specify the rw option. Otherwise, specify the rw= option followed by acolon-delimited list of NFS client identifiers. To exclude NFS clients from the list, prepend the NFSclient identifiers with a minus sign (-). Unless you specify the ro, ro=, or rw= option, Data ONTAPuses the rw option, giving all NFS clients read-write access to the file system path. Note: Unlike in DataONTAP releases prior to 6.5, if you specify the rw= option, Data ONTAP does not use the ro option asthe default for all other NFS clients.

root=clientid[:clientid...]Specifies which NFS clients have root access to the file system path. If you specify the root= option,you must specify at least one NFS client identifier. To exclude NFS clients from the list, prepend theNFS client identifiers with a minus sign (-).

sec=sectype[:sectype...]Specifies the security types that an NFS client must support to access the file system path. To apply thesecurity types to all types of access, specify the sec= option once. To apply the security types to specifictypes of access (anonymous, non-super user, read-only, read-write, or root), specify the sec= option atleast twice, once before each access type to which it applies (anon, nosuid, ro, rw, or root,respectively). Note: You cannot apply the same security type to more than one access type. By default,an NFS client must support the sys security type to access a file system path.

Specify any combination of the following security types as a colon-delimited list:

none No security. Data ONTAP treats all of the NFS client’s users as anonymous users.

sys Standard UNIX (AUTH_SYS) authentication. Data ONTAP checks the NFS credentials of all ofthe NFS client’s users, applying the file access permissions specified for those users in the NFSserver’s /etc/passwd file. This is the default security type.

krb5 Kerberos(tm) Version 5 authentication. Data ONTAP uses data encryption standard (DES) keyencryption to authenticate the NFS client’s users.

krb5i Kerberos(tm) Version 5 integrity. In addition to authenticating the NFS client’s users, DataONTAP uses message authentication codes (MACs) to verify the integrity of the NFS client’sremote procedure requests and responses, thus preventing "man-in-the-middle" tampering.

krb5p Kerberos(tm) Version 5 privacy. In addition to authenticating the NFS client’s users and verifyingdata integrity, Data ONTAP encrypts NFS arguments and results to provide privacy.


exports

Note: Before specifying the krb5, krb5i, or krb5p option, you must enable Kerberos V5 security usingthe nfs setup command. For more information, see na_nfs(1).

Specifying an NFS client identifierTo specify which NFS clients have read-only, read-write, and root access to a file system path (usingthe ro=, rw=, and root= options, respectively), you must specify an NFS client identifier. An NFSclient identifier is a host name, netgroup name, IP address, subnet, or DNS domain.

A host name is an alphanumeric string associated with an IP address. Data ONTAP uses the firstdefinition that it finds in the /etc/hosts file, searching the NIS, LDAP, DNS, and local versions in theorder specified in the /etc/nsswitch.conf file.

A netgroup name is an alphanumeric string associated with a group of host names. Data ONTAP usesthe first definition that it finds in the /etc/netgroup file, searching the NIS, DNS, and local versions inthe order specified in the /etc/nsswitch.conf file. Note: DNS does not support netgroups.

To specify that a name is a netgroup name, not a host name, thus preventing Data ONTAP fromsearching the /etc/hosts file unnecessarily, prepend the name with an "at" (@) character.

To specify that all netgroup names begin with an "at" (@) character, thus preventing Data ONTAP fromsearching the /etc/hosts or /etc/netgroups file unnecessarily, set the nfs.netgroup.strict option to on.For more information, see na_options(1).

Note: If a name is defined as both a host name and a netgroup name, Data ONTAP assumes the name isa host name.

An IP address is a 32-bit dotted-decimal value that uniquely identifies a machine on an IP network. Forexample:

104.342.403.224

A subnet is a group of machines that share a common network. To specify a subnet, use the followingshort form:

subnetaddr/subnetbits

where subnetaddr is the subnet IP address and subnetbits is the number of bits in the subnet mask.

You can also use the following long form, but Data ONTAP automatically converts this long form tothe short form:

[networkaddr] subnetaddr [subnetmask] subnetmask

where networkaddr is the network IP address, subnetaddr is the subnet IP address, and subnetmask isthe subnet mask.

A DNS domain is an alphanumeric value starting with a period (.) that identifies a group of machines.For example:

.frogs.fauna.netapp.com


exports

EXTENDED DESCRIPTIONTo edit the /etc/exports file, you must either use a text editor on an NFS client that has root access tothe storage system or run the exportfs command with the -b, -p, or -z option on the storage systemcommand line.

Enabling automatic updatingIf the nfs.export.auto-update option is on, Data ONTAP updates the /etc/exports file automaticallywhen you create, rename, or destroy a volume. In this case, when you create a volume, if anadministration host is defined, Data ONTAP adds the following export entry to the /etc/exports file:

path -sec=sys,root=adminhostid,nosuid

If an administration host is not defined, Data ONTAP adds the following entry to the /etc/exports file:

path -sec=sys,rw,nosuid

When you rename a volume, Data ONTAP automatically replaces the old volume name, wherever itappears in /etc/exports file, with the new volume name. When you delete a volume, Data ONTAPremoves all corresponding entries from the /etc/exports file.

If the nfs.export.auto-update option is off, Data ONTAP does not update the /etc/exports fileautomatically when you create, rename, or destroy a volume; instead, it adds a message to the systemlog that notifies you to update the /etc/exports file manually.

Specifying ro, ro=, rw, and rw=The following sections describe how to specify the ro, ro=, rw, and rw= options given their defaults,invalid combinations, and order of precedence.

Defaults:

* If you do not specify the ro, ro=, or rw= option, Data ONTAP uses the rw option by default.

* Unlike in Data ONTAP releases prior to 6.5, if you specify a list of NFS clients with read-write accessusing the rw= option, Data ONTAP does not use the ro option as the default for all other NFS clients.

Invalid combinations:

* You cannot specify the ro option with the ro= option.

* You cannot specify the rw option with the rw= option.

* You cannot exclude an NFS client identifier from the ro= or rw= option and include the same NFSclient identifier in the other option.

Order of precedence:

* The ro option takes precedence over the rw option.

* The ro= option takes precedence over the rw option.


exports

* The rw= option takes precedence over the ro option.

* The ro= option takes precedence over the rw= option.

* A host name or IP address in the ro= or rw option takes precedence over a netgroup, subnet, ordomain in the other option.

* Host names and IP addresses take precedence from left to right within an option.

Upgrading the /etc/exports fileWhenever you invoke the exportfs command to export file systems specified in the /etc/exports file(for example, whenever you invoke exportfs -a or exportfs -r), Data ONTAP automatically upgradesthe /etc/exports file to a format compatible with the current Data ONTAP release.

Data ONTAP no longer supports the access option; therefore, Data ONTAP automatically converts allexport entries containing an access option to an equivalent export entry containing the ro= or rw=option.

For example, if an export entry uses the access option to specify that an NFS client has read-writeaccess:

/vol/vol0 -access=hostname

Data ONTAP upgrades the export entry to use the rw= option instead:

/vol/vol0 -rw=hostname

Note: Unlike in Data ONTAP releases prior to 6.5, if you specify the rw= option, Data ONTAP doesnot use the ro option as the default for all other NFS clients.

Similarly, if an export entry uses the access option to specify that an NFS client has read-only access:

/vol/vol0 -access=hostname,ro

Data ONTAP upgrades the export entry to use the ro= option instead:

/vol/vol0 -ro=hostname

In addition, if an export entry specifies subnets in long form:

/vol/vol0 -rw="network 10.45.67.0 netmask 255.255.255.0"

Data ONTAP upgrades them to short form:

/vol/vol0 -rw=10.45.67.0/24

Note: Data ONTAP always preserves the ordering of NFS client identifiers within an option. Also,upgrading has no effect on the root=, rw=, and ro= options because their formatting has not changed.

Upgrade examplesOld:


exports

/vol/vol0 -anon=0

New:

/vol/vol0 -rw,anon=0

Old:

/vol/volo -access=pets:workers:alligator:mule,rw=dog:cat:skunk:pig:horse:ox:mule

New:

/vol/volo -ro=pets:workers:alligator,rw=dog:cat:skunk:pig:horse:ox:mule

This can be rewritten as:

/vol/vol1 -ro=pets:workers:alligator,rw=pets:workers

And should be:

/vol/vol1 -ro=alligator,rw=@pets:@workers

Reverting the /etc/exports fileTo revert the /etc/exports file to a format compatible with the Data ONTAP 6.5 or 6.4 release, run the exportfs -d 6.5 command or exportfs -d 6.4 command, respectively.

When you run the exportfs -d 6.5 command, Data ONTAP:

* Removes all "at" (@) symbols, which denote netgroups.

* Consolidates multiple security contexts into one security context. If the ro and/or rw options exist inany security context, Data ONTAP removes the ro= and rw= options, respectively, from the othersecurity contexts. Data ONTAP merges security contexts from left to right.

When you run the exportfs -d 6.4 command, Data ONTAP:

* Reverts the /etc/exports file to a format compatible with the Data ONTAP 6.5 release (see above).

* Replaces anon=clientid with anon=uid.

* Removes nosuid.

* Removes all domain names, each of which starts with a period (.).

* Removes all excluded NFS client identifiers, each of which starts with a minus sign (-).

* Removes the rw option.

* Replaces rw=clientid,ro with rw=clientid.

* Replaces rw=clientidX,ro=clientidY


exports

with access=clientidX+clientidY,rw=clientidX.

* Removes ro=clientid,rw.

Note: This access restriction cannot be expressed in a format that is compatible with the Data ONTAP6.4 release.

* Replaces ro=clientid with access=clientid,ro.

* Replaces rw=clientid with access=clientid,rw=clientid.

Note: After running the exportfs -d 6.4 command, you must manually edit all rw= and root= options inthe /etc/exports file to:

* Replace netgroup names with the host names.

* Reduce the number of host names to less than 255.

* Reduce the number of characters to 4,096 or less.

When reverting the /etc/exports file, Data ONTAP displays messages on the console notifying you ofany export entries that require manual editing.

Managing duplicate entriesData ONTAP processes export entries in sequential order, using only the last export entry in the /etc/exports file for a specific file system path. Therefore, you should not add multiple export entriesfor the same file system path, whether exported or actual, to the /etc/exports file.

For example, if you add the following export entries to the /etc/exports file:

/vol/vol0/ -ro /vol/vol0/ -rw

Data ONTAP exports /vol/vol0 to all NFS clients for read-write access.

And, if you add the following export entries to the /etc/exports file:

/vol/vol1/ -actual=/vol/vol0,ro /vol/vol2/ -actual=/vol/vol0,rw

Data ONTAP exports /vol/vol2/ to all NFS clients for read-write access, mapping it internally to /vol/vol0. Data ONTAP does not export /vol/vol1/.

Debugging mount and access problemsFor information about debugging mount and access problems, see na_exportfs(1).

EXAMPLESFor the following examples, assume the /etc/netgroup file contains the following entries:

farm pets livestock workers pets (dog,,) (cat,,) (pig,,) (parrot,,) livestock (cow,,) (pig,,) (chicken,,) (ostrich,,) workers (dog,,) (horse,,) (ox,,) (mule,,) predators (coyote,,) (puma,,) (fox,,) (crow,,)


exports

Read and write access: netgroupsThe following example exports /vol/vol0 to horse for read-write access:

/vol/vol0 -anon=0,rw=horse

Note: Unlike in Data ONTAP releases prior to 6.5, all other NFS clients do not get read-only access.

The following example exports /vol/vol0 to horse for read-write access and all other NFS clients forread-only access:

/vol/vol0 -anon=0,ro,rw=horse

Each of the following examples exports /vol/vol0 to workers (dog, cat, pig, and parrot) for read-onlyaccess and all remaining farm animals for read-write access:

/vol/vol0 -ro=@workers,rw=@farm /vol/vol0 -rw=@farm,ro=@workers

The following example exports /vol/vol0 to all NFS clients except workers for read-write access:

/vol/vol0 -rw=@farm:-@workers

Note: The workers do not have any access at all.

The following example exports /vol/vol0 to pets for read-write access and livestock for read-onlyaccess, but denies access to workers:

/vol/vol0 -rw=@pets:-@workers,ro=@livestock

Read and write access: subnetsThe following example exports /vol/vol0 to all NFS clients in the 10.56/16 subnet for read-write accessand all NFS clients in the 10.56.17/24 subnet for read-only access:

/vol/vol0 -ro=10.56.17/24,rw=10.56/16

The following example exports /vol/vol0 to 10.56.17.5 and 10.56.17.6 for read-write access and to allremaining NFS clients in the 10.56.17/24 subnet for read-only access:

/vol/vol0 -ro=10.56.17/24,rw=10.56.17.5:10.56.17.6

Read and write access: domainsThe following example exports /vol/vol0 to all NFS clients in the .frogs.fauna.netapp.com domain forread-only access and to all remaining clients in the .fauna.netapp.com domain for read-write access:

/vol/vol0 -ro=.frogs.fauna.netapp.com, rw=.fauna.netapp.com

Excluding NFS client identifiersData ONTAP gives precedence to NFS client identifiers from left to right within an access control list;therefore, if you exclude an NFS client identifier from a list, the order in which you specify netgroups,subnets, and domains becomes important if the same NFS client appears in more than one netgroup,subnet, or domain.


exports

For example, suppose cat, which belongs to the farm and pets netgroups, requests read-write access to /vol/vol0.

Data ONTAP grants cat read-write access if you specify the following export entry:

/vol/vol0 -ro,rw=@farm:-@pets

But Data ONTAP denies cat read-write access if you specify the following export entry in which theorder of the netgroups in the rw= list is reversed:

/vol/vol0 -ro,rw=-@pets:@farm

In the first example, Data ONTAP gives precedence to the farm netgroup, which is included in theread-write access list. In the second example, Data ONTAP gives precedence to the pets netgroup,which is excluded from the read-write access list.

Specifying an actual pathThe following example exports /vol/vol0/home/user1 as /vol/vol/user1 to all NFS clients for read-writeaccess:

/vol/vol0/home/user1 -actual=/vol/vol/user1,sec=sys,rw

Note: NFSv4 does not support the actual option.

Controlling anonymous accessThe following example exports /vol/vol0 to all NFS clients for read-write access, but prevents access byanonymous and root NFS client users:

/vol/vol0 -sec=sys,rw,anon=65535

The following example exports /vol/vol0 to all NFS clients for read-write access, giving anonymousand root NFS client users an effective user ID of 100:


The following example exports /vol/vol0 to all NFS clients for read-write access, giving anonymousand root NFS client users an effective user ID of 0 (root):


Controlling root accessThe following example exports /vol/vol0 to adminhost for root access and all other NFS clients forread-write access:

/vol/vol0 -sec=sys,rw,root=adminhost

The following example exports /vol/vol0 to adminhost for root access and all other NFS clients forread-write access, but prevents adminhost from creating setuid executables and device nodes:

/vol/vol0 -sec=sys,rw,root=adminhost,nosuid

Controlling access by sectypeThe following example exports /vol/vol0 to all NFS clients supporting the krb5 security type forread-write access and all remaining NFS clients in the .farm.netapp.com domain for read-only access:


exports

/vol/vol0 -ro=.farm.netapp.com,sec=krb5,rw

The following example exports /vol/vol0 to all hosts supporting no security type for read-write accessand all hosts supporting the krb5, krb5i, or krb5p security type for read-write and root access:

/vol/vol0 -sec=sys:none,rw,sec=krb5:krb5i:k4b5p,rw,anon=0

FILES/etc/hosts Maps IP addresses to host names and aliases.

/etc/netgroup Maps group names to hosts.

/etc/nsswitch.conf Specifies the order in which Data ONTAP searches local, NIS, DNS, and LDAPfiles.

/etc/passwd Specifies user information.

SEE ALSOna_hosts(5), na_passwd(5)


exports

fsecurityNAMEna_fsecurity - Definition file for an fsecurity job

DESCRIPTIONThe fsecurity definition files describe an fsecurity job, which is used as input to thena_fsecurity_apply(1) command, and contains a list of tasks that will be run against the file system.This file can have any convenient name, and can be stored in any convenient location in the localvolumes. The name of the file is given as a parameter to the "fsecurity apply" command.

The definition file can be in ASCII or Unicode format. The first line is always the file’s signature, withtask definitions on each subsequent line.

The file signature is currently cb56f6f4, and it will be updated when new versions of the file aresupported. It is important that this is the only value on the line, including spaces.

Each task is a comma-separated list of values that are defined as follows:

type,subtype,"path",propagation mode,"security definition"

type 1 - Security Descriptor Definition Language (SDDL)

subtype 0 - Standard 1 - Storage-Level Access Guard (Guard)

path The path to the target file system object, in double-quotes.

propagation mode 0 - Propagate inheritable permissions to all subfolders and files 1 - Do not allow permissions on this file or folders to be replaced (Not implemented) 2 - Replace existing permissions on all subfolders and files with inheritable permissions

security definition The security definition that will be applied to the specified path. The format is described by the type field, and is always enclosed in double-quotes.

For more information about SDDL syntax and proper formatting of the security description value, see "Security Descriptor String Format" at the following URL: http://msdn2.microsoft.com/en-us/library/aa379567.aspx

NOTE This file can also be generated by the secedit utility, which is available via download.


fsecurity

EXAMPLE This is a sample fsecurity definition file which propa- gates a security descriptor down the /vol/vol0/qtree hier- archy. The definition allows Everyone full control, and the second line sets a Guard security descriptor which denies the ability to Write. _NF_NF_

cb56f6f4 1,0,"/vol/vol0/qtree",0,"D:(A;CIOI;0x1f01ff;;;Everyone)" 1,1,"/vol/vol0/qtree",0,"D:(D;CIOI;0x000002;;;Everyone)"

EFFECTIVEAny changes take effect after running the ‘fsecurity apply’ command.


SEE ALSOna_fsecurity(1)


fsecurity

ftpusersNAMEna_ftpusers - file listing users to be disallowed ftp login privileges

SYNOPSIS/etc/ftpusers

DESCRIPTIONThe /etc/ftpusers file is an ASCII file that lists users for whom ftp login privileges are disallowed. Eachftpuser entry is a single line of the form:

user_name

where user_name is the user’s login name.

By default there is no /etc/ftpusers file, and therefore ftp login privileges are allowed to all users.

EFFECTIVEAny changes take effect immediately



ftpusers

groupNAMEna_group - group file

SYNOPSIS/etc/group

DESCRIPTIONThe /etc/group database contains information for each group in the following form:

groupname:password:gid:user-list

The following list describes the required fields:

groupname The name of the group.

password The group’s password, in an encrypted form. This field may be empty.

gid An integer representing the group; each group is assigned a unique integer.

user-list The user list is a comma-separated list of users allowed in the group.

EXAMPLE

Here is a sample group file: project:asderghuIoiyw:12:dan,dave myproject::11:steve,jerry

SEE ALSOna_quota(1), na_cifs_setup(1)


group

hostsNAMEna_hosts - host name data base

SYNOPSIS/etc/hosts

DESCRIPTIONThe hosts file contains information regarding the known hosts on the network. For each host a singleline should be present with the following information:

Internet-address official-host-name aliases

Items are separated by any number of blanks and/or tab characters. A ‘‘#’’ indicates the beginning of acomment; characters up to the end of the line are not interpreted by routines which search the file. Themaximum line length is 1022 characters. There is no way to continue an entry past the end of the line.

This file may be created from the official host data base maintained at the Network Information ControlCenter (NIC), though local changes may be required to bring it up to date regarding unofficial aliasesand/or unknown hosts.

Network addresses are specified in the conventional ‘‘.’’ (dot) notation. Host names may contain anyalphanumeric character, but not field delimiters, newline, or comment characters.

FILES/etc/hosts

SEE ALSOna_nis(8)


hosts

hosts.equivNAMEna_hosts.equiv - list of hosts and users with rsh permission

SYNOPSIS/etc/hosts.equiv

DESCRIPTIONThe hosts.equiv file contains a list of hosts on which you can enter a filer command through the remoteshell protocol (rsh).

Hosts specified in this file are considered the trusted hosts of the filer.

It is also possible to use hosts.equiv for other protocols such as ssh (both interactive andnon-interactive) and telnet. Additionally, access to ONTAPI (ONTAP management APIs) over HTTPand HTTPS can use hosts.equiv authentication by setting the filer optionhttpd.admin.hostsequiv.enable.

Each line in hosts.equiv has the following format:

hostname [ username ]

If the host on which you enter the filer command is a UNIX host, the user name is optional. If the hoston which you enter the filer command is a PC, you must enter the user name for that PC in the /etc/hosts.equiv file.

If you do not specify a user name for a UNIX host, you must be root on that host to execute a filercommand through rsh.

If multiple users on the same host should have access to the filer through rsh, enter each user name on aseparate line.

EXAMPLEThe following hosts.equiv file allows both root and joe_smith to enter filer commands through rsh ona UNIX host named adminhost:

adminhostadminhost joe_smith



hosts.equiv

httpd.accessNAMEna_httpd.access - authentication controls for HTTP access

SYNOPSIS/etc/httpd.access

DESCRIPTIONThe HTTP daemon can apply authentication controls to individual users or groups on a per directorybasis. The file /etc/httpd.access specifies the following items for each access-controlled tree:

the path to the tree

the authority required to authenticate access to the tree

the lists of users or groups who are permitted access when authenticated

The syntax is the same as the access control syntax used by NCSA and Apache. However, the httpd.access file only supports a subset of directives supported by NCSA and Apache. You can copy anexisting NCSA or Apache access to the filer without editing or reformatting.

SYNTAXThe supported directives are:<Directory directory_name></Directory>AuthName Title phraserequire user user_id[, user_id,...] require group group_id[, group_id,...]

where Title phrase is a word or phrase that is passed to the authentication dialog as a title for the dialogthat prompts the user for a password.

EXAMPLESThe following example restricts access to the file /home/htdocs/private/bob so that only user dole canaccess it, after supplying the required password. The authentication dialog is titled ‘‘My private stuff.’’

<Directory /home/htdocs/private/bob> AuthName My private stuff<Limit GET>require user dole</Limit></Directory>

The <Limit GET> and </Limit> directives are not supported, but are retained for format consistencywith NCSA and Apache. The filer just ignores them.


httpd.access

The following example restricts access to the directory tree /home/htdocs/private/conspiracy to thegroup ‘‘guyinblack’’, which consists of the users whose IDs are cancer, deepthroat, mrx, and skinner.The authentication dialog is titled ‘‘Area 51.’’

<Directory /home/htdocs/private/conspiracy> AuthName Area 51<Limit GET>require group guyinblack</Limit GET></Directory>

In this example, ‘‘guyinblack’’ is defined by the following entry in /etc/httpd.group:

guyinblack: cancer deepthroat mrx skinner

The following example requires the client to provide a Windows Domain username and password toaccess the directory tree /home/htdocs/win. The authentication dialog is ‘‘Windows(tm)Authentication’’ This authentication dialog, typed exactly as presented here, is required to enforceNTLM authentication.

<Directory /home/htdocs/win>AuthName Windows(tm) Authentication </Directory>

If this authentication control is used the Filer must have CIFS running, and either be a member of aWindows Domain or be using Local User authentication.

EFFECTIVEAny changes take effect within 5 minutes


SEE ALSOna_httpd.group(5).

BUGSOnly the directives listed above are supported; other directives that may appear in NCSA or Apacheaccess files are ignored.


httpd.access

httpd.groupNAMEna_httpd.group - names of HTTP access groups and their members

SYNOPSIS/etc/httpd.group

DESCRIPTIONThe file declares the names of groups and the user IDs of the members of each group, for use by theHTTP daemon in executing the access controls declared in /etc/httpd.access.

SYNTAXgroup_id1:user_id1 [ user_id2 ... ]



SEE ALSOna_httpd.access(5).


httpd.group

httpd.hostprefixesNAMEna_httpd.hostprefixes - configuration of HTTP root directories for virtual hosts

SYNOPSIS/etc/httpd.hostprefixes

DESCRIPTIONThe httpd.hostprefixes file maps virtual hosts used in HTTP to corresponding root directories. Thesame configuration file is used for both IP virtual hosts (discriminated by the IP address used forconnecting to the server) and HTTP virtual hosts (discriminated by the Host: header used in HTTPrequests).

Each virtual host has a corresponding subdirectory within the directory specified by the option httpd.rootdir. This subdirectory is called the virtual host root directory. Clients connected to a virtualhost can only access files within the virtual host root directory.

In the httpd.hostprefixes file, each line consists of a virtual host root directory followed by the namesand IP addresses of a virtual host. If you specify an IP address, the virtual host root directory isassociated with the given virtual host for IP-level virtual hosting. If you specify a name, the virtual hostroot directory is associated with the virtual host with that name, using HTTP-level virtual hosting. If thefiler can resolve that name to an IP address, which is used for an IP-level host alias (see the alias optionin na_ifconfig(1)), the filer uses that IP address in the same way as it would if you specified the IPaddress in the httpd.hostprefixes file.

If the /etc/httpd.hostprefixes file is edited, it is read again by the HTTP server after the changes aresaved.

EXAMPLEThis example maps requests sent to www.customer1.com to the customer1 subdirectory of httpd.rootdir and requests directed at a host with IP address 207.68.156.58 to the subdirectory customer2.

/customer1 www.customer1.com /customer2 207.68.156.58

If the command

toaster> ifconfig vh alias www.customer1.com

had been issued before the configuration file was read, requests destined for the IP address of www.customer1.com would also be mapped to the /customer1 subdirectory, regardless any the Host:header they included.


httpd.hostprefixes





httpd.hostprefixes

httpd.logNAMEna_httpd.log - Log of HTTP

SYNOPSIS/etc/log/httpd.log

DESCRIPTIONThe HTTP server logs an entry for every file retrieved via HTTP. This log, written to /etc/log/httpd.log,is stored in the "Common Log Format," which is used by many WorldWide Web servers.

Each entry in /etc/log/httpd.log consists of one line with seven fields. The fields are, in order:

address The IP address of the HTTP client requesting the file.

rfc931 This field is always "-".

authuser This field is always "-".

date The time and date the request was is reported in the format "[Day/Mon/Year:HH:MM:SS]", whichis logged in universal time (GMT) rather than the local time zone.

request A quoted string is recorded for the method (request type) and file involved in the request.

result The status code for the request, as defined in RFC 1945, the HTTP protocol specification. (Seebelow.)

bytes The size of the file in bytes.

Possible values for result codes include:

200 Success: the requested file was transmitted.

302 Redirected (see /etc/httpd.translations).

304 Not modified (client cache used).


httpd.log

400 Bad request.

401 Unauthorized request.

403 Access to file prohibited.

404 File not found.

503 HTTP server disabled.

The size of the log file can be restricted by the option httpd.log.max_file_size.

SEE ALSOna_httpd.translations(5)RFC 1945, "Hypertext Transfer Protocol -- HTTP/1.0"

BUGSSome Web servers report size statistics differently for result codes other than 200. For example, a filesize of 0 is often reported for result code 304 (Not modified).

The log file grows automatically and is never reset. It is your responsibility to rotate files and empty thelog files regularly.


httpd.log

httpd.mimetypesNAMEna_httpd.mimetypes - map of file suffixes to MIME ContentType

SYNOPSIS/etc/httpd.mimetypes

DESCRIPTIONFor HTTP/1.0 and higher protocols, a MIME header is returned in the reply of every GET request. Thisheader includes a "Content-Type" field, whose contents is determined by examining the suffix of thefile being transmitted.

The /etc/httpd.mimetypes file contains the mapping of filename suffixes to MIME Content-Type. Theformat of each line is: suffix, Content-Type. Comments are introduced with a "#".

The filer is not shipped with the /etc/httpd.mimetypes file. Instead, the filer’s system files include asample file named /etc/httpd.mimetypes.sample. Before you start using HTTP, make a copy of /etc/httpd.mimetypes.sample and name the copy /etc/httpd.mimetypes.

If the file /etc/httpd.mimetypes is not installed, the HTTP server looks for the file /etc/httpd.mimetypes.sample as a fallback.

EXAMPLE# map .ps files to PostScript type:ps application/postscript




httpd.mimetypes

httpd.passwdNAMEna_httpd.passwd - file of passwords required for HTTP access

SYNOPSIS/etc/httpd.passwd

DESCRIPTIONThe password file containing the encrypted form of the password that an HTTP client must supply tohave access to a file in a controlled-access directory tree, as declared in /etc/httpd.access.

The password is encrypted in the regular UNIX style. User of NCSA or Apache can use their htpasswdprogram to generate the user_id:passwd pair.

The HTTP access control does not use the existing CIFS password database on the filer because in httpbasic authentication, in each request for protected pages, the value of passwd is sent over the network inclear text, and without encryption would compromise the user’s password.

SYNTAXuser_id1:encrypted_passwd1used_id2:encrypted_passwd2...



SEE ALSOna_httpd.access(5).


httpd.passwd

httpd.translationsNAMEna_httpd.translations - URL translations to be applied to incoming HTTP requests

SYNOPSIS/etc/httpd.translations

DESCRIPTIONThe HTTP daemon supports four URL translation rules to filter incoming HTTP requests. The HTTPdaemon applies each rule in succession, stopping at the first successful Redirect, Pass, or Fail rule:

Map template resultAny request which matches template is replaced with the result string given.

Redirect template resultAny request which matches template is redirected to the result URL. Note that this must be a full URL,e.g., beginning with "http:".

Pass template [ result ]Any request which matches template is granted access, and no further rule processing occurs. Anoptional result can be used in place of the matching URL.

Fail templateAny request which matches template is denied access. Rule processing stops after a matched Fail.

Both templates and results may contain wildcards (a star "*" character). The wildcard behaves like ashell wildcard in the template string, matching zero or more characters, including the slash ("/")character. In the result string, a wildcard causes text from the corresponding match in the templatestring to be inserted into the result.

EXAMPLEThis example redirects CGI queries to cgi-host, prevents accesses to /usr/forbidden, and maps requestsfor images to a local image directory:

## Example URL translations#Redirect /cgi-bin/* http://cgi-host/*Fail /usr/forbidden/*Map /image-bin/* /usr/local/http/images/*


httpd.translations




httpd.translations

messagesNAMEna_messages - record of recent console messages

SYNOPSIS/etc/messages

DESCRIPTIONThe default behavior of the filer syslogd daemon (see na_syslogd(8)) is to print all logging messages ofpriority info or higher to the console, and to the messages file. A typical message is:

Fri Jun 10 14:31:37 PDT 2005 [rc]: Data ONTAP Release 7.1 boot complete.

Every Saturday at 24:00, /etc/messages is moved to /etc/messages.0, /etc/messages.0 is moved to /etc/messages.1, and so on. Message files are saved for a total of six weeks.

FILES

/etc/messages messages file for current week /etc/messages.[0-5] messages file for previous weeks



messages

ndmpdlogNAMEna_ndmpdlog - The ndmpdlog provides a detailed description of the activities of all active NDMPsessions.

SYNOPSIS/etc/log/ndmpdlog.yyyymmdd

DESCRIPTIONThe NDMP debug log provides a detailed description of the activities of all active NDMP sessions. See na_ndmpd (1) for a detailed description of how NDMP logging is enabled and disabled and the variousoptions associated with the control of logging. All events are recorded in multi-line entries and are sentto the filer console and/or the /etc/log/ndmpdlog.yyyymmdd files depending on how logging has beenconfigured with the ndmpd debug command.

The information in the ndmpdlog is a trace of the NDMP protocol messages as defined in the variousversions of the NDMP Protocol Specification. Data ONTAP supports versions 2, 3 and 4 of theprotocol. At least a cursory knowledge of the NDMP Protocol is required to analyze the ndmpdlog.Describing the protocol is beyond the scope of this manpage. Descriptions of the three supportedversions of the protocol can be found at www.ndmp.org.

If logging to files is enabled, a new log file is created each day. The last part of the log file name is thedate for which the log file applies. If NDMP sessions are active at the time a new daily log file iscreated, information for the existing sessions will continue to be logged to the file which was active atthe time the sessions were created. Information for any new sessions will be logged in the new log file.Up to 9 daily log files are retained on the system. A log file for a particular day may not exist if noNDMP activity occurred on that day. Log files over 8 days old are automatically deleted by DataONTAP.

The log has a multi-column, multi-line format.

The three columns contain:

Date The time of the messages displayed in the timezone specified by the timezone command.

Session The NDMP session number for the messages in [ndmpd:<session>] format.

Message The contents of the messages.

The information for each message occupies multilple lines in the log. At a high level, there are twotypes of log entries: those representing request/reply pairs and those representing log/notify messages.Note that there is only one entry for a request/reply pair. Some of the information is placed in the log asthe message is received by the filer and other information is placed in the log as the reply is being sentto the NDMP client. Also note that the debug level must be set to the appropriate level with the ndmpd


ndmpdlog

debug command as described in na_ndmpd (1) for the following information to be displayed.

The log entry for each request/reply message begins with the following 2 lines:

NDMP message type:The high-level message type such as

NDMP_DATA_START_BACKUP or NDMP_TAPE_OPEN.

NDMP message replysequence:The replysequence is the sequence number from the request message with which the reply is associated.

The log entry for each log/notify message begins with the following line:

Message <message type> sentThe high-level message type such as

NDMP_NOTIFY_DATA_ABORT or NDMP_LOG_MESSAGE.

The above information is followed by the NDMP message header.

Message header:The message header contains information such as sequence numbers, a numerical representation of themessage type, and an error field representing the success or failure of receiving and decoding themessage. The fields correspond to the fields in the NDMP message header as defined in the NDMPProtocol Specifications.

The header information is followed by the request/reply information or the log/notify information.

Request/Reply information including the Error code: Contains the remainder of the informationabout the request and reply for the message and possibly some other state information associated withthe request/reply. An Error code: field is displayed for all reply message log entries. This is the overallstatus of the execution of the request and is a key piece of information when diagnosing problems. Thecontents of the rest of the log entry varies widely depending on the message being logged. It is beyondthe scope of this manpage to describe the details for the dozens of different messages which are part ofthe NDMP protocol. Refer to the NDMP Protocol Specifications as well as the NDMP ExtensionSpecifications available from IBM to decode these fields in the logs.

Log/Notify information:Contains the remainder of the information about the log/notify message. As for the request/replyinformation, see the NDMP Protocol Specifications as well as the NDMP Extension Specifications todecode these fields in the logs.

VFILER CONSIDERATIONSThe log files are stored in the /etc/log directory of the vfiler’s root volume.


ndmpdlog

FILES

/etc/log/ndmpdlog.yyyymmdd daily ndmpd log file

SEE ALSOna_ndmpd(1).


ndmpdlog

netgroupNAMEna_netgroup - network groups data base

SYNOPSIS/etc/netgroup

DESCRIPTIONnetgroup defines network wide groups used for access permission checking during remote mountrequest processing. Each line defines a group and has the format:

groupname member-list

Each element in member-list is either another group name or a triple of the form:

(hostname, username, domainname)

The hostname entry must be fully qualified if the specified host is not in the local domain.

The filer can also use the netgroup NIS map.

Since the filer uses netgroups only in /etc/exports (see na_exports(5)), the username entry is ignored.The domainname field refers to the domain in which the netgroup entry is valid. It must either be emptyor be the local domain; otherwise the netgroup entry is ignored. An empty entry allows a single /etc/netgroup file to be used for filers in multiple domains.

A group definition can be at most 4096 bytes even when ‘\’s are used to extend the definition overseveral lines. The maximum nesting level when group names are used in the member-lists of othergroups is 1000.

Modifications to the /etc/netgroup file may take upto 60 seconds to take effect.

EXAMPLEThis is a typical netgroup file:

trusted_hosts (adminhost,,) (zeus,,) (thor,,) (minerva,,)

untrusted_hosts (sleepy,,) (dopey,,) (grumpy,,) (sneezy,,)

all_hosts trusted_hosts untrusted_hosts

With this netgroup file it might make sense to modify /etc/exports to export / on the filer only to trusted_hosts, but to export /home to all_hosts.


netgroup

FILES/etc/netgroup

/etc/exports directories and files exported to NFS clients

/etc/hosts host name data base

SEE ALSOna_nis(8)

BUGSThe only place that netgroups can be used are in the options of the exportfs command (see exportfs(1))and /etc/exports.

The /etc/netgroup configuration does not failover. Thus, the /etc/netgroup files on the active andbackup filer must be kept consistent manually.


netgroup

networksNAMEna_networks - network name data base

SYNOPSIS/etc/networks

DESCRIPTIONThe networks file contains information regarding the known networks which comprise the Internet. Foreach network a single line should be present with the following information:

official-network-name network-number aliases

Items are separated by any number of blanks and/or tab characters. A ‘‘#’’ indicates the beginning of acomment; characters up to the end of the line are not interpreted by routines which search the file. Thisfile is normally created from the official network data base maintained at the Network InformationControl Center (NIC), though local changes may be required to bring it up to date regarding unofficialaliases and/or unknown networks.

Network number may be specified in the conventional ‘‘.’’ (dot) notation or as a 32 bit integer.Numbers may be specified in decimal (default), octal or hexadecimal. A number is interpreted as octalif it starts with the digit "0". A hexadecimal number must begin with "0x" or "0X." Network names maycontain any printable character other than a field delimiter, newline, or comment character.

FILES/etc/networks


networks

nsswitch.confNAMEna_nsswitch.conf - configuration file for name service switch

SYNOPSIS/etc/nsswitch.conf

DESCRIPTIONThe name service switch configuration file contains the preferred order in which name services will becontacted for name resolution by the filer. For each map, the name services to be used and the lookuporder is specified in this file. Currently four name services are supported. They are local files in the /etcdirectory, NIS, LDAP, and DNS. The maps or "databases" that are supported are hosts, passwd,shadows, group, and netgroups (LDAP is currently supported in the passwd, group, and netgroups map).Each line has the form:

map: order of name services

For example:

hosts: files nis dns ldappasswd: files nis ldap

When trying to resolve a name, the services are contacted one by one, as per the order specified, untilthe name is successfully resolved. A name resolution failure occurs when no service can successfullyresolve the name. When enumerating a map, enumeration happens over all the services specified for themap.

FILES/etc/nsswitch.conf

SEE ALSOna_setup(1)


nsswitch.conf

nvfail_renameNAMEna_nvfail_rename - Internet services

SYNOPSIS/etc/services

DESCRIPTIONThe services file contains information mapping between port numbers and service names. This fileexists purely for reference purposes and is not currently used by Data ONTAP. Modifying entries in thisfile will have no effect on the filer. Removing entries will not disable ports or services. For informationon how to change which port numbers a service uses (if possible), see the relevant manual page for thatservice. Such changes will not update the services file.

Each line contains a service name followed by a port number, a ‘‘/’’, and a protocol, for example 20/tcp.Legal protocol names are ‘‘tcp’’ and ‘‘udp’’. Port numbers are decimal numbers in the range of 0 to65535. A service name may contain any printable character other than the comment character (i.e. nospaces, tabs, newlines, or ‘‘#’’).

Items are separated by any number of blanks and/or tab characters. A ‘‘#’’ indicates the beginning of acomment; characters up to the end of the line are not interpreted by routines which search the file.

FILES/etc/nvfail_rename

SEE ALSOna_vol(1)


nvfail_rename

passwdNAMEna_passwd - password file

SYNOPSIS/etc/passwd

DESCRIPTIONThe passwd file contains basic information about each user’s account. It contains a one-line entry foreach authorized user, of the form:

username:password:uid:gid:gcos_field:home_directory:login_shell

Required Fields:

username The user’s login name, not more than eight characters.

password The user’s password, in an encrypted form that is generated by the UNIX passwd function.However, if the encypted password is stored in /etc/shadow, (see shadow(5)), the password fieldof /etc/passwd is empty.

uid A unique interger assigned by the UNIX administrator to represent the user’s account; its value isusually between 0 and 32767.

gid An interger representing the group to which the user has been assigned. Groups are created by theUNIX system administrator; each is assigned a unique integer whose value is generally between 0and 32767.

gcos-field The user’s real name. The name may be of any length; it may include capital letters as well aslower case, and may include blanks. The name may be empty.

home_directory The user’s home directory. The home directory field may be empty.

login-shell The default shell launched at login. This field may be empty.

EXAMPLE


passwd

Here is a sample passwd file when the /etc/shadow does not exist: root:bDPu/ys5PBoYU:0:1:Operator:/:/bin/csh dave:Qs5I6pBb2rJDA:1234:12:David:/u/dave:/bin/csh dan:MNRWDsW/srMfE:2345:23:Dan:: jim:HNRyuuiuMFerx:::::

If the system keeps the passwords in the /etc/shadow, the file/etc/passwd would be exactly the same but the password field would be empty.

root::0:1:Operator:/:/bin/csh dave::1234:12:David:/u/dave:/bin/csh dan::2345:23:Dan:: jim::::::

SEE ALSOna_pcnfsd(8), na_cifs_access(1), na_cifs_setup(1)


passwd

psk.txtNAMEna_psk.txt - pre-shared authentication key file

SYNOPSIS/etc/psk.txt

DESCRIPTIONThe psk.txt file contains an pre-shared key that authenticates the specified machine For each machine asingle line should be present with the following information:

Internet-address authentication-key

Items are separated by any number of blanks and/or tab characters. authenticaion-key is specified as anascii text. Network addresses are specified in the conventional ‘‘.’’ (dot) notation.

FILES/etc/hosts

SEE ALSOna_ipsec(1),


psk.txt

qual_devicesNAMEna_qual_devices - table of qualified disk and tape devices

SYNOPSIS/etc/qual_devices

DESCRIPTIONThe qual_devices file names storage devices qualified for use with Data ONTAP. This is a read-onlyfile and must not be modified.

Disk and tape drives listed in this file are qualified for use with a Data ONTAP system. This file is readby the dynamic qualification process which is invoked to authenticate devices not listed in the internaltables of a particular Data ONTAP release. The dynamic qualification process may be invoked atsystem startup, cluster takeover, or when a new device is detected.

WARNINGDo not modify or remove this file. However, it may be replaced with an updated version containingidentification data for additionally qualified devices supplied by IBM.

NOTESEach line in the file contains identification strings for a qualified device.

QUALIFICATION ERRORSA qualification error will occur when Data ONTAP is unable to locate identification information for oneor more storage devices detected by the system. To resolve qualification errors, verify the existence of/etc/qual_devices and ensure it represents the latest version available from IBM. Periodic consolemessages will be generated when a qualification error is present. All qualification errors MUST beresolved for continued system operation.


qual_devices

quotasNAMEna_quotas - quota description file

SYNOPSIS/etc/quotas

DESCRIPTIONThe /etc/quotas file describes disk quotas that go into effect when quotas are enabled. All quotas areestablished on a per-volume basis. If a volume name is not specified in an entry of the /etc/quotas file,the entry applies to the root volume.

The following sample /etc/quotas file describes different kinds of quotas:

# Quota Target type disk files thold sdisk sfile # ------------- ----- ---- ----- ----- ----- ----- mhoward user 500M 50K lfine user@/vol/home 500M tracker user - - stooges group@/vol/vol0 750M 75K /vol/vol0/export tree 750M 75K mhoward user@/vol/vol0/export 50M 5K stooges group@/vol/vol0/export 100M 10K * user@/vol/home 100M 10K 90M 90M 9K * group@/vol/vol0 500M 70K * tree 500M 50K * user@/vol/vol0/export 20M 2K * group@/vol/vol0/export 200M 20K 150M * tree@/vol/home 500M 50K corp\bill user - - 100M corp\joe, fin\joe user 200M 40K 160M corp\sue, sue user 100M 20K corp\ann user 100M - 90M QUOTA_TARGET_DOMAIN corp # The following entry will become corp\jim jim user 200M - - # The following entry will become corp\beth beth user 120M 50K - QUOTA_TARGET_DOMAIN QUOTA_PERFORM_USER_MAPPING ON # If corp\sam maps to usam, the following entry will become # corp\sam, usam user ..... corp\sam user 50M # If umary maps to corp\mary, the following entry will become # umary, corp\mary user .... umary user 300M QUOTA_PERFORM_USER_MAPPING OFF


quotas

The first non-comment line in the file restricts the user mhoward to 500 MB of disk space and 51,200files in the root volume. The second line restricts the user lfine to 500 MB of disk space in the homevolume, but places no restriction on the number of files he can have. You can leave the file limit blankto indicate that no limit is imposed but you cannot omit the value for disk space. The third line placesno restriction on either disk usage or file usage by using a limit field of "-". This may be useful fortracking usage on a per-user or per-group basis without imposing any usage limits.

The next two lines restrict the stooges group and the /vol/vol0/export qtree to 750 MB and 76,800 fileseach in the root volume.

The fifth column of the /etc/quotas file contains a value for the warning threshold. If an attempt toallocate space for the quota target causes the quota target’s disk space usage to exceed the warningthreshold value, a warning message is logged on the filer’s console. Additionally, an SNMP trap isemitted indicating the condition. The disk space allocation will succeed if no other quota limits areexceeded. The value is specified in bytes.

The sixth column specifies a soft disk limit, while the seventh column specifies a soft file limit. Theyare analogous to the (hard) limits specified in the third and fourth columns, but behave more similarly tothe threshold value: when a soft limit is exceeded, a warning message is logged to the filer’s console.Additionally, an SNMP trap is emitted indicating the condition. Lastly, when the quota target’s usagereturns below the soft limit, a warning message and SNMP trap is also generated.

An entry in the /etc/quotas file may extend over several lines, but the last five columns (hard limits,warning threshold, and soft limit values) must be on the same line of the quota file.

A user is specified by one of the following values:

a unix user name, which must appear in the password database (either in the /etc/passwd file on thefiler, or in the password NIS map if NIS is enabled on the filer and is being used for the passworddatabase);

a numerical unix user ID;

the pathname of a file owned by that user;

a Windows account name, which consists of the domain name and the account name separated by abackslash (if the domain name or the account name contain spaces or other special characters, then theentire name must be enclosed in quotes);

the text form of a Windows SID that represents a Windows account;

a comma separated list of any of the above items that are to be considered one user quota target (the listcan extend to multiple lines, but the last item must be on the same line as the quota type, disk limit, filelimit and warning threshold values).

A group is specified by one of the following values:

a unix group name, which must appear in the group database (either in the /etc/group file on the filer, orin the group NIS map if NIS is enabled on the filer and is being used for the group database);


quotas

a numerical group ID;

the pathname of a a file owned by that group.

The user or group identifier for a user or group quota can be followed by an @/vol/volume string,which specifies the volume to which the quota applies. If the string is omitted, the quota applies to theroot volume.

A quota of type tree can only be applied to a qtree, which is a directory in the root directory of aspecified volume. A qtree is created with the qtree create command.

User and group quotas can be created inside a qtree, so that the user’s or group’s use of space or fileswithin that qtree is restricted. This is done by specifying the type as user@tree or group@tree where tree is the name of the qtree. In the example above, we first limit overall usage in the qtree/vol/vol0/export and then we restrict the user mhoward to 50 MB and 5,120 files under the/vol/vol0/export tree. Similarly, the group stooges has been limited to 100 MB of disk space and 10,240files under the /vol/vol0/export tree.

In any operation that creates files or writes to them, all applicable quotas must be satisfied. Forexample, the user mhoward can write to a file in the /vol/vol0/export tree if all of these requirements aremet:

his total disk usage in the root volume does not exceed 500 MB

his total number of files in the root volume does not exceed 51,200

his usage within the /vol/vol0/export tree does not exceed 50 MB

his number of files within the /vol/vol0/export tree does not exceed 5,120

the space already in use in the /vol/vol0/export tree does not exceed 750 MB

the number of files in the /vol/vol0/export tree does not exceed 768,000

The asterisk (*) in the /etc/quotas file specifies a default user, group, or tree quota depending on thetype. Any user, group, or qtree that is not specifically mentioned in the /etc/quotas file is subject to thelimits of the default user, group, or tree. Default user or group quotas can be specified on either a perqtree basis or a per volume basis.

Default tree quotas can be specified on a per volume basis. The tree identifier for a qtree quota can befollowed by an @/vol/volume string, which specifies the volume to which the quota applies. If thestring is omitted, the quota applies to the root volume.

Hard disk limits, hard file limits, warning threshold, soft disk limits, and soft file limits in the last fivecolumns of the /etc/quotas file end in ‘‘K’’, ‘‘M’’, or ‘‘G’’. ‘‘K’’ indicates kilobytes (or kilofiles). Thatis, it multiplies the limit by 1,024. Similarly, ‘‘M’’ denotes megabytes (or megafiles) and ‘‘G’’ denotesgigabytes (or gigafiles). The unit specifiers are not case sensitive so lower-case letters may be used. Thedefault for the disk limits and warning threshold is kilobytes.

The QUOTA_TARGET_DOMAIN domain directive can be used to change a user quota target that isa unix name to a user quota target that is a Windows account. It will prepend the domain and abackslash to subsequent user quota targets that are unix user names. It will continue to prepend the unixuser name names with the domain name until either the end of the /etc/quotas file or another


quotas

QUOTA_TARGET_DOMAIN directive is encountered.

The QUOTA_PERFORM_USER_MAPPING [ ON | OFF ] directive, when ON, will use the filer’suser name mapping support to map user quota targets that are unix user names to their correspondingWindows account names and consider both as one user quota target. It will also map user quota targetsthat are Windows account names to their corresponding unix user names and consider both as one userquota target. The setting remains until either the end of the /etc/quotas file is reached or another QUOTA_PERFORM_USER_MAPPING directive is encountered. If the directive is omitted or if thedirective is OFF, no user name mapping is done.

SEE ALSOna_usermap.cfg(5)


quotas

rcNAMEna_rc - system initialization command script

SYNOPSIS/etc/rc

DESCRIPTIONThe command script /etc/rc is invoked automatically during system initialization. Since the filer has nolocal editor, /etc/rc must be edited from an NFS client with root access to /etc. Alternately, you can usethe setup command to generate a new /etc/rc file without using NFS.

EXAMPLEThis is a sample /etc/rc file as generated by setup:

#Auto-generated by setup Tue Jun 2 21:23:52 GMT 1994 hostname toaster.mycompany.com ifconfig e0 ‘hostname‘-0 ifconfig e1a ‘hostname‘-1 route add default MyRouterBox 1 routed on timezone Atlantic/Bermuda savecore

FILES/etc/rc

SEE ALSOna_nfs(1), na_setup(1), na_timezone(1)


rc

registryNAMEna_registry - registry database

SYNOPSIS/etc/registry

DESCRIPTIONThe file /etc/registry stores a variety of persistent information for ONTAP. For example, the optionscommand uses this file to save option values, eliminating the need to manually add lines to the /etc/rcfile.

Do not edit this file directly; if you do, some aspects of ONTAP will not operate correctly. Severalbackups of the registry database exist and are automatically used if the original registry becomesunusable. In particular, /etc/registry.lastgood is a copy of the registry as it existed after the lastsuccessful boot.

If you back up the configuration files in the /etc directory, the /etc/registry file should be included. Afterrestoring all the configuration files, a reboot will be required to complete the restore (for example, inorder to reload the registry, and to re-execute /etc/rc).

ERRORSIf the /etc/rc file contains an explicit "options" statement whose value conflicts with the value of theoption stored in the registry, you will see an error message at boot time like this:

** Option cifs.show_snapshot is being set to "true" in /etc/rc, and this ** conflicts with a value - "off" - loaded from the registry. ** Commands in /etc/rc always override the registry at boot time, ** so the value of cifs.show_snapshot is now "true".

Similarly, if you execute the "options" statement interactively, and the /etc/rc file contains an explicit"options" statement for the same option, you may see an error message such as this:

** Option autosupport.enable is being set to "off", but this conflicts ** with a line in /etc/rc that sets it to "on". ** Options are automatically persistent, but the line in /etc/rc ** will override this persistence, so if you want to make this change ** persistent, you will need to change (or remove) the line in /etc/rc.

By removing the explicit options statements from /etc/rc, you can eliminate these warnings aboutinconsistencies between /etc/rc and the registry.


registry

FILES/etc/registry (primary registry)/etc/registry.bck (first-level backup)/etc/registry.lastgood (second-level backup)


registry

resolv.confNAMEna_resolv.conf - configuration file for domain name system resolver

SYNOPSIS/etc/resolv.conf

DESCRIPTIONThe resolver configuration file contains information that is read by the resolver routines. The file isdesigned to be human readable and contains a list of keywords with values that provide various types ofresolver information. Semicolon (’;’) or pound (’#’) starts comment. So, any character after ‘;’ or ‘#’ isignored until the next line. Lines in bad formats are ignored entirely.

The different configuration options are:

nameserver addressThis specifies the Internet address (in dot notation) of a name server that the resolver should query. Upto 3 name servers may be listed, one per keyword. If there are multiple servers, the resolver queriesthem in the order listed. When a query to a name server on the list times out, the resolver will move tothe next one until it gets to the bottom of the list. It will then restart from the top retrying all the nameservers until a maximum number of retries are made.

search domain-listThis specifies the search list for host-name lookup. The search list is normally determined from thelocal domain name; by default, it begins with the local domain name, then successive parent domainsthat have at least two components in their names. This may be changed by listing the desired domainsearch path following the search keyword with spaces or tabs separating the names. Most resolverqueries will be attempted using each component of the search path in turn until a match is found. Notethat this process may be slow and will generate a lot of network traffic if the servers for the listeddomains are not local, and that queries will time out if no server is available for one of the domains.

The search list is currently limited to six domains with a total of 256 characters.

The keyword and value must appear on a single line, and the keyword (e.g. nameserver) must start theline. The value follows the keyword, separated by white space.

FILES/etc/resolv.conf

SEE ALSOna_rc(5), RFC 1034, RFC 1035


resolv.conf

rmtabNAMEna_rmtab - remote mounted file system table

SYNOPSIS/etc/rmtab

DESCRIPTION/etc/rmtab maintains the list of client mount points between server reboots. The list of client mountpoints can be obtained by using the MOUNTPROC_DUMP remote procedure call, or by using theUNIX showmount(1) command. When the server successfully executes a mount request from a client,the server appends a new entry to the file. When the client issues an unmount request, the correspondingentry is marked as unused. When the server reboots, unused entries are deleted from the file.

BUGSEntries may become stale if clients crash without sending an unmount request. The file may be removedbefore rebooting the server in which case the server will lose information about any active client mountentries on reboot.


rmtab

serialnumNAMEna_serialnum - system serial number file

SYNOPSIS/etc/serialnum

DESCRIPTIONThe file /etc/serialnum should contain the serial number of your machine.

If /etc/serialnum does not exist, it is an indication that your machine could not obtain the serial numberfrom the hardware. In this case you need to enter the serial number manually. The serial number isfound on the back of the machine in the lower right hand corner. You should see a tag that says:

NetworkAppliance SN: xxxx

Use a text editor to create /etc/serialnum and put the machine’s serial number in it. The file shouldcontain a single line that only has the serial number. The file is used to help IBM’s customer servicegroup process your autosupport email more efficiently.

FILES/etc/serialnum

WARNINGSA warning is issued to the console if /etc/serialnum contains a different value other than the hardwareserial number in which case it is automatically overwritten with the hardware serial number. Also if thehardware serial number and /etc/serialnum do not exist, then a warning is issued to the console.


serialnum

servicesNAMEna_services - Internet services

SYNOPSIS/etc/services

DESCRIPTIONThe services file contains information mapping between port numbers and service names. This fileexists purely for reference purposes and is not currently used by Data ONTAP. Modifying entries in thisfile will have no effect on the filer. Removing entries will not disable ports or services. For informationon how to change which port numbers a service uses (if possible), see the relevant manual page for thatservice. Such changes will not update the services file.

Each line contains a service name followed by a port number, a ‘‘/’’, and a protocol, for example 20/tcp.Legal protocol names are ‘‘tcp’’ and ‘‘udp’’. Port numbers are decimal numbers in the range of 0 to65535. A service name may contain any printable character other than the comment character (i.e. nospaces, tabs, newlines, or ‘‘#’’).

Items are separated by any number of blanks and/or tab characters. A ‘‘#’’ indicates the beginning of acomment; characters up to the end of the line are not interpreted by routines which search the file.

FILES/etc/services

SEE ALSOna_hosts(5)


services

shadowNAMEna_shadow - shadow password file

SYNOPSIS/etc/shadow

DESCRIPTIONThe shadow file provides more secure storage for the user’s password (which would otherwise be in /etc/passwd). When the password field of an entry in /etc/passwd is empty, /etc/shadow must contain acorresponding entry with the same user name but a non-empty encrypted password.

username:password:

The following list explains the required fields:

username The user’s login name, not more than eight characters.

password The user’s password, in an encrypted form that is generated by the UNIX passwd function.

There can be other fields in the /etc/shadow file following the ":" after the password.

EXAMPLE

Here is a sample shadow password file entry: dave:Qs5I6pBb2rJDA:

SEE ALSOna_pcnfsd(8), na_nsswitch.conf(5)


shadow

sisNAMEna_sis - Log of Advanced Single Instance Storage (SIS) activities

SYNOPSIS/etc/log/sis

DESCRIPTIONThe sis log file contains a log of SIS activities for this filer. The file lives in /etc/log on the root volume.

Every Sunday at midnight, /etc/log/sis is moved to /etc/log/sis.0; /etc/log/sis.0 is moved to /etc/log/sis.1; and so on. The suffix can go up to 5, so the old /etc/log/sis.5 will be deleted. SIS activitiesare saved for a total of seven weeks.

Each entry of the /etc/log/sis file is a single line containing the following space-separated fields.

timestamp path event_info

The following is a description of each field.

timestampDisplayed in ctime() format, e.g. Fri Jul 17 20:41:09 GMT. Indicates the time this event was recorded.

path The full path to a SIS volume as shown below:

/vol/volume_name

event_infoThe event which is being logged. Some events may have extra information in parentheses. The currentevent types are:

Begin [ ( scan | check | snapvault | user ) ] When a SIS operation is first kicked off. There are multiplecases for a SIS operation. If the operation is not started by scheduler, the event is augmented with thefollowing additional information in parenthesis.

scan Corresponds to "sis start -s", when we are instructed to scan the entire file system for duplicatedblocks.

check If we are specifically instructed to perform fingerprint database checking.

snapvaultIf the snapvault initiated the SIS operation.

user When the SIS operation is kicked off with CLI or ZAPI.


sis

Undo Corresponds to "sis undo" command.

End ( processed_size KB )When a long-running SIS operation (either Begin or Undo) completes successfully. We should includethe size of data processed in the event.

Error ( Error_message )If a SIS operation aborts or fails to start, we should indicate the cause of the error.

Config ( schedule_string )When a "sis config" command successfully set or modified the SIS schedule on a volume. The newschedule string is logged with the event.

Enable When the SIS is enabled on a volume.

DisableWhen the SIS is disabled on a volume.

EXAMPLEA SIS operation initiated by schedule and based on change log is the most common case and thusconsidered the default. On the successful completion of such an operation, the log file should have thefollowing entries:

Tue Jul 12 02:01:05 GMT /vol/dense_vol Begin Tue Jul 12 02:02:22 GMT /vol/dense_vol End (2356080 KB)

If the SIS operation falls into one of the four cases listed above, the Begin event entries would lookrather like:

Tue Jul 12 02:01:05 GMT /vol/dense_vol Begin (scan) Tue Jul 12 02:01:05 GMT /vol/dense_vol Begin (check) Tue Jul 12 02:01:05 GMT /vol/dense_vol Begin (snapvault) Tue Jul 12 02:01:05 GMT /vol/dense_vol Begin (user)

If a SIS operation aborts, the Error event will replace the End event.

Fri Jul 15 00:40:31 GMT /vol/dense_vol Begin Fri Jul 15 18:58:26 GMT /vol/dense_vol Error (Volume is full)

The Undo is the only other long-running event, similar to the Begin event, is terminated by either Endor Error.

Fri Jul 15 18:58:26 GMT /vol/dense_vol Undo

The Enable, Disable and Config events are only logged when they complete successfully.

Fri Jul 15 18:58:26 GMT /vol/dense_vol Enable Fri Jul 15 18:58:26 GMT /vol/dense_vol Disable Fri Jul 15 18:58:26 GMT /vol/dense_vol Config (sun-sat@0-23)


sis

FILES

/etc/log/sis SIS log file for current week.

/etc/log/sis.[0-5] SIS log files for previous weeks.

SEE ALSO na_sis(1)


sis

smNAMEna_sm - network status monitor directory

SYNOPSIS/etc/sm

DESCRIPTIONThe network status monitor provides information about the status of network hosts to clients such as thenetwork lock manager. The network status monitor keeps its information in the /etc/sm directory.

The /etc/sm/state file contains an integer that is incremented each time the filer is booted.

The /etc/sm/monitor file contains a list of network hosts the filer is monitoring.

The /etc/sm/notify file contains a list of network hosts that made an NLM lock request to the filer. Eachtime the filer reboots, it tries to notify the hosts of its new state information. You can remove this file ifyou want the filer to stop notifying the hosts in this file.

BUGSIf the filer cannot resolve a host name in the /etc/sm/notify file or if a host in the /etc/sm/notify filedoes not exist on the network any more, the filer logs an error message each time it tries to contact thehost. The error message is similar to the following:

[sm_recover]: get RPC port for failed

To stop the error messages, remove the /etc/sm/notify file.


sm

snapmirrorNAMEna_snapmirror - Log of SnapMirror Activity

SYNOPSIS/etc/log/snapmirror

DESCRIPTIONThe SnapMirror log file contains a log of SnapMirror activity for this filer. The file lives in /etc/log onthe root volume of both the source and destination filers. When the option snapmirror.log.enable is setto on, all the SnapMirror activities will be recorded in this log file. See na_options(1) for detailsregarding how to enable and disable this option. Every Sunday at 00:00, /etc/log/snapmirror is movedto /etc/log/snapmirror.0, /etc/log/snapmirror.0 is moved to /etc/log/snapmirror.1, and so on. Thesuffix can go up to 5. This process is called rotation. SnapMirror log entries are saved for a total of sixweeks.

Each entry of the /etc/log/snapmirror file is a single line consisting of space-separated fields. All logentries begin with a type field and a timestamp field. The final field may be enclosed by parentheses, inwhich case it may contain spaces. The timestamp field contains a fixed number of spaces, and as suchcan be parsed as five space-delimited fields. Which fields appear, and in what order they appear in, isdetermined by the type field of log entry (which is the first field).

Following is a description of each field.

type Indicate the type of the entry, which also determines the format of the rest of the entry. It can beone of the following values:

log log facility activity

Format: type timestamp event_info...

sys system-wide activity

Format: type timestamp event_info...

tgt snapvault target activity

Format: type timestamp volume target event_info...

src source activity


snapmirror

Format: type timestamp source destination event_info...

dst destination activity


cmd user command activity


scn replication check source activity


chk replication check destination activity.


vol volume-wide activity

Format: type timestamp volume event_info...

slk softlock addition-deletion activity

Format: type timestamp softlock event_info...

timestampDisplayed in ctime() format, e.g. Fri Jul 17 20:41:09 GMT. Indicates the time this event is recorded.

volume Specifies the name of the volume to which this entry applies.

target This is the name and type of the target for this entry. Targets are volume-wide actions, typicallysnapshot creations. It is displayed as two colonseparated fields, as follows:

target_type:target_name

The target name may be an empty string.

source This is the name of the source filer and the volume name or qtree path to be mirrored. The nameis specified as two colon-separated fields, as follows:

host:path

This field may be ‘-’ when not applicable for the event.


snapmirror

destinationThis is the name of the destination filer and the volume name or qtree path of the destination. The nameis specified as two colon-separated fields, same as in the source field.

This field may be ‘-’ when not applicable for the event.

event_infoThis field contains the event which is being logged. Some events may have extra information inparentheses.

Request (IP address | transfer type) A transfer request has been sent (destination) or received (source).On source side, the IP address of the destination filer that made the request is included in parentheses.On destination side, the transfer type is included in the parentheses.

Start The beginning of a transfer.

Start (Snapshots to check=#num, level={data|checksum}, {check|fix}, {quick|full} mode)The beginning of a replication check or fix session. The session options are included in the parentheses.All options appear on the destination side log but only the "snapshots to check" option appears in sourceside log.

Restart (@ num KB)The beginning of a restarted transfer.

End (num KB done)The completion of a transfer. The total size of the transfer in KB is included in the parentheses.

End (src_only=num_1, dst_only=num_2, mismatch=num_3) The completion of a replication check orfix session. The summary of the session is included in the parentheses. The summary is present only onthe destination side logs. Source side logs will not contain any summary information.

Abort (error msg)A transfer is aborted. The error message is included in the parentheses.

Defer (reason)Indicates a transfer is deferred because of a resource limitation. The reason for the deferment is includedin the parentheses.

Wait_tapeA SnapMirror tape operation is waiting for next tape.

New_tapeA SnapMirror tape operation continued the operation with the new tape.

Sync_startThe start of synchronous mirroring mode for the SnapMirror relationship specified by this log entry.

Sync_end (reason)The end of synchronous mirroring mode for the SnapMirror relationship specified by this log entry. Thereason for dropping out of synchronous mode is included in the parentheses.


snapmirror

Quiesce_startThe beginning of quiesce process.

Quiesce_endThe completion of quiesce process.

Quiesce_failed (reason)The failure of quiesce process. The reason for failure is included in the parentheses.

Rollback_startThe beginning of a rollback process for a qtree SnapMirror or SnapVault.

Rollback_endThe completion of a rollback process for a qtree SnapMirror or SnapVault.

Rollback_failed (reason)The failure of a rollback process for a qtree SnapMirror or SnapVault. The reason for failure is includedin the parentheses.

Coalesce_start (snapshot)The beginning of a coalesce process for a SnapVault qtree. The base snapshot for the coalesce operationis included in the parentheses.

Coalesce_endThe completion of a coalesce process for a SnapVault qtree.

Coalesce_failed (reason)The failure of a coalesce process for a SnapVault qtree. The reason for failure is included in theparentheses.

Target_startThe beginning of a SnapVault target.

Target_endThe completion of a SnapVault target.

Target_failed (reason)The failure of a SnapVault target. The reason for failure is included in the parentheses.

Start_loggingSnapMirror log was enabled.

End_loggingSnapMirror log was disabled.

SnapMirror_on (cause)SnapMirror was enabled on this host. The operation or process that caused SnapMirror to becomeenabled is specified in the parentheses.

SnapMirror_off (cause)SnapMirror was disabled on this host. The operation or process that caused SnapMirror to becomedisabled is specified in the parentheses.


snapmirror

SnapVault_on (cause)SnapVault was enabled on this host. The operation or process that caused SnapVault to become enabledis specified in the parentheses.

SnapVault_off (cause)SnapVault was disabled on this host. The operation or process that caused SnapVault to becomedisabled is specified in the parentheses.

Resume_commandUser issued snapmirror resume command.

Break_commandUser issued snapmirror break command.

Release_commandUser issued snapmirror release command.

Abort_command

Abort_command (type)User issued snapmirror abort command. The type will only be present if the abort was issued withadditional options which changed the type of the abort.

Resync_command (common snapshot)User issued snapmirror resync command. The common snapshot for the resync operation is includedin the parentheses.

Migrate_commandUser issued snapmirror migrate command.

Request_check (snapshot_name)A request for single snapshot during replication check session. This is source side log entry. Eachsnapshot being checked in a replication check session will have its entry. Name of snapshot is includedin the parentheses.

Checking_snapshot source snapshot_name (timestamp, cpcount=num_2, snapid=id) to dest_snapshot_name (timestamp, cpcount=count, snapid=id) The beginning of a single snapshotcomparison during replication check. It is logged on both source and destination.

Abort_checkreplication check session for SnapMirror or SnapVault aborted. Reason of abort is included in theparentheses.

Abort_check_commandUser issued replication check abort command. Corresponding log file entry appears with cmd type.

Data_differ ({block blk_num in file_path | VBN vbn})Replication check found a data block mismatch. Either the block number and the inode path or VolumeBlock Number (VBN) is included in the parentheses.


snapmirror

Unique_in_src (entry_type for entry_path) Replication check found an entry only present in the source.The entry type and entry path are included in the parentheses.

Unique_in_dst (entry_type for entry_path) Replication check found an entry only present in the destination. The entry type and entry path are included in the parentheses.

Size_differ (path)Replication check found a file size mismatch in specified inode. The inode path is included in theparentheses.

Type_differ (path)Replication check found a inode type mismatch. The inode path is included in the parentheses.

UID_differ (path)Replication check found a user ID mismatch for specified inode. The inode path is included in theparentheses.

GID_differ (path)Replication check found a group ID mismatch for specified inode. The inode path is included in theparentheses.

Perm_differ (path)Replication check found a permission or dosbit mismatch for specified inode. The inode path isincluded in the parentheses.

Atime_differ (path)Replication check found a mismatch in the last access time for specified inode. The inode path isincluded in the parentheses.

Mtime_differ (path)Replication check found a mismatch in the last modification time for specified inode. The inode path isincluded in the parentheses.

Ctime_differ (path)Replication check found a mismatch in the last size/status change time for specified inode. The inodepath is included in the parentheses.

Crtime_differ (path)Replication check found a mismatch in the creation time for specified inode. The inode path is includedin the parentheses.

Rdev_differ (path)Replication check found a device number mismatch for specified inode. The inode path is included inthe parentheses.

DOSbits_differ (path)Replication check found a DOS bits mismatch for specified inode. The inode path is included in theparentheses.

ACL_differ (path)Replication check found an NT or NFS V4 ACL mismatch for specified inode. The inode path isincluded in the parentheses.


snapmirror

Hardlink_differ (path)Replication check found a hardlink for specified inode, but the inode on destination doesn’t matchbetween the links. The inode path is included in the parentheses.

Qtree_oplock_differ (path)Replication check found oplock setting mismatch for a qtree. The qtree path is included in theparentheses.

Qtree_security_differ (path)Replication check found security setting mismatch for a qtree. The qtree path is included in theparentheses.

Hole_uses_disk_space (path)Replication check found unnecessary disk usage for specified inode, this however is not a mismatch.The inode path is included in the parentheses.

Convert_commandUser issued snapmirror convert command.

Older_snapshotUpdating from a snapshot which is older than the current base snapshot.

Snapshot_delete (snapshot name)A snapshot is deleted from this volume. The snapshot name is included in the parentheses.

FILER_REBOOTEDThe filer is rebooted.

WORM_LOG_FAIL (reason)Write to WORM log file failed. The reason for failure is included in the parentheses.

WORM_LOG_FAILURE_RECOVER_STARTThe beginning of the recovery of the failed WORM log entries.

WORM_LOG_FAILURE_RECOVER_ENDThe end of the recovery of the failed WORM log entries.

Softlock_add (operation)A softlock is added. The operation that added the softlock is included in the parentheses.

Softlock_add_pending (operation)A softlock is added as a pending softlock. The operation that added the softlock is included in theparentheses.

Softlock_delete (operation)A softlock is deleted. The operation that deleted the softlock is included in the parentheses.

Softlock_delete_pending (operation) A pending softlock is deleted. The operation that deleted it isincluded in the parentheses.


snapmirror

Softlock_mark_pending (operation)A softlock is marked as pending. The operation that marked it is included in the parentheses.

EXAMPLESA typical entry in /etc/log/snapmirror looks like:

dst Fri Jul 17 22:50:18 GMT filer1:srcvol filer2:dstvol Request (Update)

The above example shows an update request recorded by the destination side for a SnapMirrorrelationship from filer:srcvol to filer2:dstvol that happened at the recorded time.

A typical Replication check session in /etc/log/snapmirror on destination looks like: chk Wed Jan 19 01:07:39 GMT woolf:/vol/vol1 milton:/vol/vol1 Request (check) chk Wed Jan 19 01:07:39 GMT woolf:/vol/vol1 milton:/vol/vol1 Start (Snapshots to check = 2, level= data, check, full) chk Wed Jan 19 01:07:39 GMT woolf:/vol/vol1 milton:/vol/vol1 Checking_snapshot milton(0033587346)_vol1.5 (Jan 18... chk Wed Jan 19 01:07:48 GMT woolf:/vol/vol1 milton:/vol/vol1 Checking_snapshot nightly.0 (Jan 18 00:00, cpcount =... chk Wed Jan 19 01:07:57 GMT woolf:/vol/vol1 milton:/vol/vol1 End (src_only = 0, dst_only = 0, mismatch = 0)

A typical Replication check session in /etc/log/snapmirror on source looks like: scn Wed Jan 19 00:58:27 GMT woolf:/vol/vol1 milton:/vol/vol1 Request (172.29.19.15) scn Wed Jan 19 00:58:27 GMT woolf:/vol/vol1 milton:/vol/vol1 Start (Snapshots to check = 2) scn Wed Jan 19 00:58:27 GMT woolf:/vol/vol1 milton:/vol/vol1 Request_check (milton(0033587346)_vol1.5) scn Wed Jan 19 00:58:27 GMT woolf:/vol/vol1 milton:/vol/vol1 Checking_snapshot milton(0033587346)_vol1.5 (Jan 18... scn Wed Jan 19 00:58:36 GMT woolf:/vol/vol1 milton:/vol/vol1 Request_check (nightly.0) scn Wed Jan 19 00:58:36 GMT woolf:/vol/vol1 milton:/vol/vol1 Checking_snapshot nightly.1 (Jan 18 00:00, cpcount =... scn Wed Jan 19 00:58:45 GMT woolf:/vol/vol1 milton:/vol/vol1 End

A typical softlock logging in /etc/log/snapmirror looks like:

slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011e.054.filer1:vol3 Softlock_add (Transfer) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Transfer) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Revert) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Release) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Clean_softlocks) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_add (RSM_forward) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (RSM_forward) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Snapmirror_destinations) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete_pending (Transfer) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_add_pending (Transfer) slk Wed May 10 03:06:15 GMT state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_mark_pending (Transfer)

FILES/etc/log/snapmirrorSnapMirror log file for current week.

/etc/log/snapmirror.[0-5]SnapMirror log files for previous weeks.

SEE ALSOna_snapvault(1) na_snapvault(1d)


snapmirror

snapmirror.allowNAMEna_snapmirror.allow - list of allowed destination filers

SYNOPSIS/etc/snapmirror.allow

DESCRIPTIONThe /etc/snapmirror.allow file provides for one of two ways for controlling SnapMirror access to asource filer.

The snapmirror.access option is the preferred method for controlling snapmirror access on asnapmirror source filer. See na_options(1) and na_protocolaccess (8) for information on setting theoption. If the option snapmirror.access is set to "legacy", the snapmirror.allow file defines the accesspermissions.

The snapmirror.allow file exists on the source filer used for SnapMirror. It contains a list of alloweddestination filers to which you can replicate volumes or qtrees from that filer.

The file format is line-based. Each line consists of the hostname of the allowed destination filer.

The snapmirror.checkip.enable option controls how the allow check is performed. When the option is off, which is the default, the entries in the allow file must match the hostname of the destination filer asreported by the hostname command. When the option is on, the source filer resolves the names in the snapmirror.allow to IP addresses and then checks for a match with the IP address of the requestingdestination filer. In this mode, literal IP addresses (e.g. 123.45.67.89) and fully qualified names (e.g.toaster.acme.com) may be valid entries in the allow file.

Note that the allow file entry must map to the IP address of the originating network interface on thedestination filer. For example, if the request comes from the IP address of a Gbit Ethernet interface e10which is given the name "toaster-e10", then the allow file must contain "toaster-e10" or"toaster-e10.acme.com" so the name resolves to the correct IP address.

A local snapmirror, between two volumes or qtrees on the same filer, does not require an entry in theallow file.

EXAMPLEThe following snapmirror.allow file on a filer allows filers named toaster and fridge to replicatevolumes or qtrees from it:

toaster fridge


snapmirror.allow

SEE ALSOna_snapmirror.conf(5) na_protocolaccess(8)


snapmirror.allow

snapmirror.confNAMEna_snapmirror.conf - volume and qtree replication schedules and configurations

SYNOPSIS/etc/snapmirror.conf

DESCRIPTIONThe /etc/snapmirror.conf file exists on the filer containing the mirror used for SnapMirror.

There are two types of lines in the configuration file: lines that define mirror relationships and lines thatdefine connections to source filers to be used in the relationship definitions. Relationship definitionlines are used to define the mirror relationships for destination volumes on this filer. Connectiondefinition lines are optional and are used to specify specific network connections to the source volumeand allow the specification of dual paths to the source volume.

Each relationship line of the file specifies the volume or qtree to be replicated, arguments for thereplication, and the schedule for updating the mirror. You may only have one line for each destinationvolume or qtree.

Each relationship entry of the /etc/snapmirror.conf file is a single line containing space-separatedfields. The entry has this format:

source destination arguments schedule

The following list describes the fields in each entry:

source This is the name of the source host, and the volume name, or the path of the qtree to be mirrored.The name is specified as two colon-separated fields, as follows:

host:volname

host:/vol/volume/qtree

Note that the host field is not necessarily the hostname of the filer (unlike the first field of the destination entry). You can specify a network resolvable name, IP address or connection name. Thehost field can be considered a definition of how to reach the source over the network.

destinationThis is the hostname (must match the result of the hostname command) of the destination filer and thename of the destination volume or the path of the destination qtree. The name is specified as twocolon-separated fields, as follows:

name:volume


snapmirror.conf

name:/vol/volume/qtree

The name field must match the hostname of the destination filer (use the hostname(1) function to checkthis).

argumentsThese are a comma-separated list of arguments for the transfer. To specify no arguments, enter a dash(‘‘-’’) in this field. Each argument is specified as a key and a value pair, as follows:

key=value

Currently, there are the following argument keys:

cksum This controls which checksum algorithm is used to protect the data transmitted by SnapMirror.Currently supported values are "crc32c" and "none".

kbs The value for this argument specifies the maximum speed (in kilobytes per second) at whichSnapMirror data is transferred over the network. The kbs setting is used to throttle networkbandwidth consumed, disk I/O, and CPU usage. By default, the filer transfers the data as fast as itcan. The throttle value is not used while synchronously mirroring.

tries The value for this argument specifies the maximum number of attempts that the destination willmake to complete a scheduled snapmirror update. A retry will be attempted on the first minute after theprevious attempt was abandoned. Notice that retries are only attempted for retry-able errors, and thatsome errors do not count as a retry. The tries setting is used to limit the number of retries, for instanceto assure that backup transfers are started within a designated backup window, or else abandonedentirely until the next scheduled update. The syntax is "tries=N" or "tries=unlimited", where N is greateror equal to 0, and N is less or equal to 1000000000. If no try count is specified, the default is"unlimited".

restartThis controls the behavior of the SnapMirror scheduler with respect to restartability. If value is set to always, then an interrupted transfer will always restart, if it has a restart checkpoint and the conditionsare the same as before the transfer was interrupted. If value is set to never, then an interrupted transferwill never restart, even if it has a restart checkpoint. By default, SnapMirror behaves like the alwayscase, unless it has passed the next scheduled transfer time, in which case it will begin that scheduledtransfer instead of restarting.

outstandingThis argument controls the performance versus synchronicity trade-off for synchronous mirrors. The value for this argument is a number followed by the suffixes: ops (operations), ms (milliseconds) or s(seconds). This governs the number of outstanding operations a synchronous mirror can have beforeforcing the client to wait for acknowledgement. The ops suffix allows the specified number of writeoperations to be outstanding while the ms and s suffixes allow operations in the last period of time to beoutstanding before forcing client waits. If not specified, the default value is zero. This argument isignored for asynchronous mirrors.

wsize This sets the TCP window size to use for the connection. Due to how TCP negotiates windowsizes, the size of the receive window will initially be large and gradually work its way down to the sizespecified.


snapmirror.conf

visibility_intervalThe value for this argument is a number optionally followed by the suffixes: s (seconds), m (minutes) or h (hours). If a suffix is not specified, value is interpreted as seconds. This argument controls the amountof time before an automatic snapshot is created on the source volume that is synchronously mirrored.The value is the number of seconds between automatically created snapshots. The default value is 3minutes. A small number here can negatively affect the performance of the mirror. This argument isignored for asynchronous mirrors.

scheduleThis is the schedule used by the destination filer for updating the mirror. It informs the SnapMirrorscheduler when transfers will be initiated. The schedule field can either contain the word sync to specifysynchronous mirroring or a cron-style specification of when to update the mirror. The cronstyleschedule contains four space-separated fields:

minute hour day-of-month day-of-week

Each field consists of one or more numbers or ranges. If a field contains more than one value, the valuesare separated from each other by a comma. A field consisting solely of an asterisk (‘‘*’’) is the same asa field enumerating all possible legal values for that field. A field consisting solely of a dash (‘‘-’’)represents a null value; any schedule with a dash in one of its fields will never run any scheduledtransfers. Values in a field can take any of the following forms:

number

first-last

first-last/step

A value with a dash in it specifies a range; it is treated as containing all the values between first and last, inclusive. A range value with a slash specifies skips of step size in the range. For example, thevalue of the entry ‘‘0-23/4’’ would be the same as that of the entry ‘‘0,4,8,12,16,20’’.

minute Which minutes in each hour to update on. Values are from 0 to 59.

hour Which hours in the day to update on. Values are from 0 to 23.

day-of-monthWhich days in the month to update on. Values are from 1 to 31.

day-of-weekWhich days in the week to update on. Values are from 0 (Sunday) to 6 (Saturday).

Whenever the current time matches all the specified schedule fields, a transfer from the source to the destination will be invoked.

The other type of line allowed in this file is a connec_tion definition line. These lines define an alternatename for the source filer that can be used as the source host in the relationship lines. They are used todescribe more specifically the parameters for the connection(s) to the source filer. SnapMirror supportsthe multi path specification for both asynchronous and synchronous mirrors.


snapmirror.conf

Each connection definition is a single line giving a name to one or two pairs of IP addresses along witha mode of operation for the connection. The lines are specified in the following format:

name = mode( source_ip_addr1 , dest_ip_addr1 ) ( source_ip_addr2 , dest_ip_addr2 )

name This is the name of the connection you would like to define. This name is to be used as the sourcefiler in relationship definitions.

mode The mode is optional and specifies the mode in which two IP address pairs will be used. Twomodes are allowed multiplexing and failover mode and are specified by using the multi and failoverkeywords. If not specified, multiplexing mode is used.

The multiplexing mode causes snapmirror to use both paths at the same time. If one should fail, it willswitch to use the remaining path only and use both again should the failing path be repaired.

Failover mode causes snapmirror to use the first path as the desired path and only use the second pathshould problems arise with the first path.

source_ip_addr1 source_ip_addr2 dest_ip_addr1 dest_ip_addr2These are resolvable network names or IP addresses that define a path through the network between thesource and the destination. The source addresses are the IP addresses of interfaces to use on the sourceand respectively for the destination. The pairing denotes a path from source to destination.

EXAMPLESThe following snapmirror.conf entry indicates that filer fridge’s qtree home, in volume vol2 willmirror qtree home, in volume vol1 from the filer toaster. Transfer speed is set at a maximum rate of2,000 kilobytes per second. The four asterisks mean transfers to the mirror are initiated every minute, ifpossible. (If a previous transfer is in progress at the minute edge, it will continue; a new transfer will beinitiated at the first minute edge after the transfer has completed.)

toaster:/vol/vol1/home fridge:/vol/vol2/home kbs=2000 * * * *

The following snapmirror.conf entry indicates that filer myfiler1’s volume home_mirror will mirrorvolume home via the myfiler0-gig interface. (The myfiler0-gig interface is whatever IP addressmyfiler1 can resolve that name to. In this case, it might be a gigabit ethernet link on filer myfiler0.) Themirror is updated at 9:30 a.m., 1:30 p.m., and 7:30 p.m., Monday through Friday. The asterisk meansthat the data replication schedule is not affected by the day of month; it is the same as entering numbers1 through 31 (comma-separated) in that space. The dash in the argu_ments field indicates that both the kbs and restart arguments are set to default.

myfiler0-gig:home myfiler1:home_mirror - 30 9,13,19 * 1,2,3,4,5

The following snapmirror.conf entry makes transfers every half hour, with the first at 8:15 a.m., andthe last at 6:45 p.m. The asterisks mean that the data replication schedule is not affected by the day ofmonth or week; in other words, this series of transfers are initiated every day.

filer1:build filer2:backup - 15,45 8,9,10,11,12,13,14,15,16,17,18 * *

The following snapmirror.conf entry, between the docs qtree on dev and docs_bak on icebox, iskicked off on every Sunday, at 12:00 midnight.


snapmirror.conf

dev:/vol/dept/docs icebox:/vol/backup/docs_bak - 0 0 * 0

The following snapmirror.conf entry, between the home and backup volume on icebox, is kicked offonce every halfpast the hour between 7:30 a.m. and 9:30 p.m., and once at midnight.

icebox:home icebox:backup - 30 0,7-21 * *

The following snapmirror.conf entry, between the db volumes on fridge-gig dev and icebox, is kickedoff on every five minutes, starting at 0. (Note that fridge-gig is just a network interface name. In thiscase, it could be a gigabit ethernet link on fridge.)

fridge-gig:db icebox:db - 0-55/5 * * *

This can be extended to use the multiple path options and synchronous mirroring.

fridge-con = failover(fridge-gig,icebox-gig)(fridge-slow,icebox-slow) fridge-con:db icebox:db - sync

This changes the relationship into synchronous mode and the connection specifies that we should use agigabit ethernet path for the mirroring where only if that connection fails, use a slower networkconnection. Even if you would like to use one path from source to destination, it is a good idea tospecify a connection line in your configuration file. This can reduce problems seen with nameresolution affects on the relationship configuration line.

SEE ALSOna_snapmirror.allow(5)


snapmirror.conf

stats_presetNAMEna_stats_preset - stats preset file format

SYNOPSIS/etc/stats/preset

DESCRIPTIONThe stats utility supports preset queries, using the -p argument. A preset includes the statistics to begathered, and the format for display. Using presets not only saves typing when entering commands fromthe CLI, it also allows greater flexibility in formatting the data than is possible on the command line.Each preset is described in an XML file, stored in the applicance directory /etc/stats/preset. The name ofeach preset file is pre_setname.xml.

PRESET FILE FORMATPreset ElementThe main element of a preset file is a single preset. The preset consists of attributes, plus one or objectsthat should be included in the preset. A simple preset to display all information from the system objectusing the default formats might be:

<?xml VERSION = "1.0" ?><preset><object name="system"></object> </preset>

Preset AttributesThe following attributes are available for the preset element.

orientationOutput orientation, "row" or "column", see -r/-c command line options.

outfileOutput file. See -o command line option.

intervalInterval between output. See -i command line option.

icount Number of outputs when using interval output. See -n command line option.

print_headerWhether or not to print a output header. Default: true

print_object_namesIn row output, whether or not to include object names in the output. Default: true


stats_preset

print_instance_namesIn column output, whether or not to include instance names as a column in the output. Default: true

print_footerAfter printing a set of counters print a footer string. Default: false. In multiple-count outputs the footeris printed after each iteration.

print_zero_valuesDetermines whether counters with zero values should be displayed. The default setting displays allcounters, except for counters that are flagged as not-zero-printing by default. The allowed values are default, true and false. This option only affects row output.

column_delimeterIn column output, the text to print between each column, changing the default TAB spacing.

catenate_instancesIn column output, whether or not to catenate all instance counters into a long line, or to split the outputso that each instance goes on its own line. Default: false

The following example specifies a preset with column output, that displays values each second:

<?xml VERSION = "1.0" ?><preset orientation="column" interval="1" > ...</preset>

ObjectsThe object element specifies an object that is to be used in the preset. It has attributes, as listed below,and optional counters and instances.

The following example shows a preset using the system and volume objects:

<?xml VERSION = "1.0" ?><preset><object name="system">...</object><object name="volume">...</object></preset>

The following table lists object attributes.

name

Object name. If "*" is used, this means all objects. This attribute is mandatory

Object counters and instancesEach object may list which instances and/or which counters are to be used in the preset, using the instance and counter elements. If no instances or counters are listed then all instances, all counters areassumed.


stats_preset

Counters may be listed for an object, or for an instance. If a counter is listed for an object then it appliesto all instances of the object in the preset. If a counter is listed for an instance then it only applies to thatinstance.

The following example shows a case where counter "global_counter" is being used for all instances, but"counter_0" is only being used for a specific instance.

<?xml VERSION = "1.0" ?><preset><object name="OBJNAME"><instance name="instance0"> <counter name="counter_0"> </counter"></instance>

<counter name="global_counter"> </counter></object></preset>See below for more information on the syntax for counters and instances.

CountersObject counters are specified with the counter element. The required attribute "name" specifies thecounter name, or "*" may be used to indicate all counters for an object.

A counter also has the following elements:

title Title to be used in column headers.

width Column width in output, in characters.

The following example shows a column named "disk_io" formatted in a column 8 characters wide, witha column header of "Disk I/O":<counter name="disk_io"><title>Disk I/O</title><width>8</width></counter">

InstancesObject instance are specified with the instance element. The required attribute "name" attributespecifies the instance name.

An instance has the following optional elements:

counterAn instance-specific counter. The element may occur multiple times.

Note that if no counters are listed for an instance then the default set of counters for the preset will beused. This is either counters listed at the object level, or all counters for the object.

The following example shows an instance with two counters:

<instance name="instance0"><counter name="counter0"> <title">Cnt0</title></counter"><counter name="counter1"> <title">Cnt1</title>


stats_preset

</counter"></instance">

EXAMPLEThe following example shows a preset with output similar to the sysstat command. It might be invokedas:

stats show -p sysstat -i 1

<?xml VERSION = "1.0" ?><preset orientation="column"print_instance_names="false" catenate_instances="true" > <object name="system"><counter name="cpu_busy"> <width>4</width><title>CPU</title></counter><counter name="nfs_ops"> <width>6</width><title>NFS</title></counter><counter name="cifs_ops"> <width>6</width><title>CIFS</title></counter><counter name="http_ops"> <width>6</width><title>HTTP</title></counter><counter name="net_data_recv"> <width>8</width><title>Net in</title> </counter><counter name="net_data_sent"> <width>8</width><title>Net out</title> </counter><counter name="disk_data_read"> <width>8</width><title>Disk read</title> </counter><counter name="disk_data_written"> <width>8</width><title>Disk write</title> </counter></object></preset>

SEE ALSOna_stats.1


stats_preset

symlink.translationsNAMEna_symlink.translations - Symbolic link translations to be applied to CIFS path lookups

SYNOPSIS/etc/symlink.translations

DESCRIPTIONWhen the CIFS server encounters a symbolic link (also called a "symlink," or "soft link"), it attempts tofollow the link. If the symlink target is a path that starts with a "/", the filer must interpret the rest of thepath relative to the root of the file system. On the filer, there is no way to know how NFS clients (whichmust be used to create the symlinks) might have mounted filesystems, so there is no reliable way tofollow such absolute, or "rooted" symlinks. The symlink.translations file enables you to use absolutesymlinks by mapping them to CIFS-based paths.

The entries in this file are similar to the httpd.translations file. There are two formats for file entries, asfollows:

Map template result

Widelink template [@qtree] result

Any request that matches template is replaced with the result string given. Note that the result path for a"Map" entry must point to a destination within the share to which the client is connected. This isbecause the client has only been authenticated to that share; therefore access is limited to the same sharefor security reasons. A result path for a "Widelink" entry may point anywhere, thus the name "widesymlink" or widelink for short. Widelinks have these limitations-- the filer share on which the symlinkresides must be enabled for wide symlinks, the CIFS client must support Microsoft’s Dfs protocol, andthe destination must be able to function as a Dfs leaf node. By using Dfs requests, the filer causes theclient to authenticate with the destination and thus enforces security. To enable a filer share for "widesymlinks", use the "cifs shares -change" filer console command.

Both templates and results might (and usually do) contain wildcards (a star "*" character). The wildcardbehaves like a shell wildcard in the template string, matching zero or more characters, including theslash ("/") character. In the result string, a wildcard causes text from the corresponding match in the template string to be inserted into the result.

The entries are examined in the order they appear in the file until a match is found or the lookup fails.

EXAMPLESThis example maps absolute symlinks that start with "/u/home" to go to the filer path "/vol/vol2/home".Also, symlinks starting with "/u" go to "/vol/vol0". Note that you should put the more restrictive entriesfirst to avoid premature mapping since the matches are done in order.


symlink.translations

## Example Map symlink translations#Map /u/home/* /vol/vol2/home/*Map /u/* /vol/vol0/*

The next example maps absolute symlinks that start with "/u/docs/" to go to the filer path"\\filer\engr\tech pubs". Note that widelink result paths use CIFS pathname syntax (backslashes areseparators, spaces in path components are allowed, and so on).

## Example Widelink symlink translation#Widelink /u/docs/* \\filer\engr\tech pubs\*

The next example maps absolute symlinks that start with "/u/joe". Note that depending on how NFSmounts are set up, it is possible that there could be several absolute symlinks pointing to "/u/joe" whichneed to have differing destinations. The qtree in which a symlink resides can optionally be used todistinguish destinations. Thus, following an absolute symlink starting with "/u/joe" in qtree/vol/vol1/mixed takes the client to "\\filer\home\joe", while symlinks in other qtrees take the client to"\\filer\test tools\joe".

## Example Widelink symlink translations #Widelink /u/joe/* @/vol/vol1/mixed \\filer\home\joe\* Widelink /u/joe/* \\filer\test tools\joe\*

Note that there is no theoretical reason why a wide symlink can’t point to another filer or indeed any NTserver, though it may be difficult to imagine the translated link making sense to the Unix client whichcreated the original symlink.

## More Widelink examples#Widelink /u/joe/* @/vol/vol1/mixed \\myfiler2\users2\joe\*Widelink /u/joe/* \\joe-PC\Program Files\*

SEE ALSOna_cifs_shares(1)


symlink.translations

syslog.confNAMEna_syslog.conf - syslogd configuration file

DESCRIPTIONThe syslog.conf file is the configuration file for the syslogd daemon (see na_syslogd(8)). It consists oflines with two fields separated by tabs or spaces:

selector action

The selector field specifies the types of messages and priorities to which the line applies. The actionfield specifies the action to be taken if a message the syslogd daemon receives matches the selectioncriteria.

The selector field is encoded as a facility, a period (‘‘.’’), and a level , with no intervening white-space.Both the facility and the level are case insensitive.

The facility describes the part of the system generating the message, and is one of the followingkeywords: auth, cron, daemon, kern and local7. Here’s a short description of each facility keyword:

kern Messages generated by the filer kernel.

daemon System daemons, such as the rshd daemon (see na_rshd(8)), the routing daemon (seena_routed(1)), the SNMP daemon (see na_snmpd(8)), etc.

auth The authentication system, e.g. messages logged for Telnet sessions.

cron The system’s internal cron facility.

local7 The system’s audit logging facility. All messages coming from the audit logging facility are loggedat level debug.

The level describes the severity of the message, and is a keyword from the following ordered list (higherto lower): emerg, alert, crit, err, warning, notice, info, and debug.

Here is a short description of each level keyword:

emerg A panic condition that results in the disruption of normal service.


syslog.conf

alert A condition that should be corrected immediately, such as a failed disk.

crit Critical conditions, such as hard disk errors.

err Errors, such as those resulting from a bad configuration file.

warning Warning messages.

notice Conditions that are not error conditions, but that may require special handling.

info Informational messages, such as the hourly uptime message (see na_uptime(1)).

debug Debug messages used for diagnostic purposes. These messages are supressed by default.

If a received message matches the specified facility and is of the specified level (or a higher level ), theaction specified in the action field will be taken.

Multiple selectors may be specified for a single action by separating them with semicolon (‘‘;’’)characters. It is important to note, however, that each selector can modify the ones preceding it.

Multiple facilities may be specified for a single level by separating them with comma (‘‘,’’) characters.

An asterisk (‘‘*’’) can be used to specify all facilities (except local7) or all levels .

The special level none disables a particular facility .

The action field of each line specifies the action to be taken when the selector field selects a message.There are four forms:

A pathname (beginning with a leading slash).Selected messages are appended to the specified file.

A hostname (preceded by an at (‘‘@’’) sign).Selected messages are forwarded to the syslogd daemon on the named host.

/dev/console. Selected messages are written to theconsole.

An asterisk. Selected messages are written to theconsole.

Blank lines and lines whose first non-blank character is a pound (‘‘#’’) character are ignored.

It is recommended that all /etc/syslog.conf files include the line


syslog.conf

*.info /etc/messages

so that all messages are logged to the /etc/messages file.

EXAMPLESA configuration file might appear as follows:

# Log all kernel messages, and anything of level err or # higher to the console. *.err;kern.* /dev/console

# Log anything of level info or higher to /etc/messages. *.info /etc/messages

# Also log the messages that go to the console to a remote # loghost system called adminhost. *.err;kern.* @adminhost

# The /etc/secure.message file has restricted access. auth.notice /etc/secure.message

Also see the sample configuration file in /etc/syslog.conf.sample

FILES

/etc/syslog.conf The syslogd configuration file. /etc/syslog.conf.sample Sample syslogd configuration file.

BUGSThe effects of multiple selectors are sometimes not intuitive. For example ‘‘daemon.crit,*.err’’ willselect ‘‘daemon’’ facility messages at the level of ‘‘err’’ or higher, not at the level of ‘‘crit’’ or higher.

SEE ALSOna_messages(5)


syslog.conf

tape_configNAMEtape_config - directory of tape drive configuration files

SYNOPSIS/etc/tape_config

DESCRIPTIONThe tape_config directory contains IBM-approved tape configuration files. These files allow DataONTAP to recognize a tape drive and to properly set its various parameters without the tape driveparameters being built into Data ONTAP. Only IBM-approved tape configuration files should be placedinto the tape_config directory.

The tape_config directory of the latest release of Data ONTAP contains tape configuration files for tapedrives that are configured exclusively with tape configuration files. Other approved files may be addedto the directory by the user as tape qualifications are completed by IBM and configuration files becomeavailable.

To use configuration files shown in this page -- if your version of Data ONTAP does not alreadysupport the tape drive(s) -- first verify that the configuration file is approved for your version of DataONTAP. Then copy the desired file(s) to the /etc/tape_config directory. The file(s) may be renamed ifnecessary. When an attached tape drive is accessed, Data ONTAP detects the presence of files in thedirectory and install the parameters for the tape drive.

SEE ALSOna_cloned_tapes(5)

NOTESExternal tape configuration files do not override built-in tape drive parameters. If the tape drive isalready supported by Data ONTAP, remove the corresponding tape configuration file.

If a tape drive is represented in tape_config directory, remove any reference from the /etc/cloned_tapesfile that attempts to cause the drive to use the parameters of another drive.

The command storage show tape supported displays all tape drives that are currently supporteddirectly within Data ONTAP. If any tape drives are connected to the system, the command will also anyshow tape drives specified by tape configuration files.


tape_config

treecompareNAMEna_treecompare - Log of treecompare activities

SYNOPSIS/etc/log/treecompare

DESCRIPTIONThe treecompare log file contains a log of treecompare activities for this filer. The file lives in /etc/logon the root volume.

Every Sunday at midnight, /etc/log/treecompare is moved to /etc/log/treecompare.0; /etc/log/treecompare.0 is moved to /etc/log/treecompare.1; and so on. The suffix can go up to 5, sothe old /etc/log/treecompare.5 will be deleted. Treecompare activities are saved for a total of sevenweeks.

Each entry of the /etc/log/treecompare file is a single line containing the following space-separatedfields.

timestamp tree1 tree2 event_info

The following is a description of each field.

timestampDisplayed in ctime() format, e.g. Fri Jul 17 20:41:09 GMT. Indicates the time this event was recorded.

tree1 The name of the host1 and the full path for tree1 as shown below:

host1:tree1_path

tree2 The name of the host2 and the full path for tree2 as shown below:

host2:tree2_path

event_infoThe event which is being logged. Some events may have extra information in parentheses. The existingevent types are:

Start (cmp_level={data|checksum}, {compare|ignore} NT ACL)The beginning of a treecompare session. The command options are included in the parentheses.

End (tree1_only=num_1, tree2_only=num_2, mismatch=num_3) The completion of a treecomparesession. The summary of the session is included in the parentheses.

Abort (error_msg)A treecompare operation was aborted. The error message is included in the parentheses.


treecompare

Data_differ (block blk_num in file_name) Found a data block mismatch. The block number and the filename are included in the parentheses.

Unique_in_tree1 (entry_type for entry_path) Found an entry only present in the first tree. The entrytype and entry path are included in the parentheses.

Unique_in_tree2 (entry_type for entry_path) Found an entry only present in the second tree. The entrytype and entry path are included in the parentheses.

Size_differ (file_name)Found a file size mismatch. The file name is included in the parentheses.

Type_differ (entry_name)Found a directory entry type mismatch. The entry name is included in the parentheses.

UID_differ (entry_name)Found a user ID mismatch for a directory entry. The entry name is included in the parentheses.

GID_differ (entry_name)Found a group ID mismatch for a directory entry. The entry name is included in the parentheses.

Perm_differ (entry_name)Found a permission mismatch for a directory entry. The entry name is included in the parentheses.

Atime_differ (entry_name)Found a mismatch in the last access time for a directory entry. The entry name is included in theparentheses.

Mtime_differ (entry_name)Found a mismatch in the last modification time for a directory entry. The entry name is included in theparentheses.

Ctime_differ (entry_name)Found a mismatch in the last size/status change time for a directory entry. The entry name is included inthe parentheses.

Crtime_differ (entry_name)Found a mismatch in the creation time for a directory entry. The entry name is included in theparentheses.

Rdev_differ (entry_name)Found a device number mismatch for a directory entry. The entry name is included in the parentheses.

DOSbits_differ (entry_name)Found a DOS bits mismatch for a directory entry. The entry name is included in the parentheses.

ACL_differ (entry_name)Found an NT ACL mismatch for a directory entry. The entry name is included in the parentheses.

Hardlink_differ (entry_name)Found a hardlink for a directory entry, but the inode on tree2 doesn’t match between the links. Theentry name is included in the parentheses.


treecompare

Skip (attr_type for entry_name)Skipped the comparison of an unsupported attribute type for a directory entry. The attribute type and theentry name are included in the parentheses.

Inode_Num_differ (entry_name)Found an inode number mismatch for a directory entry. The entry name is included in the parentheses.

Inode_Gen_differ (entry_name)Found an inode generation number mismatch for a directory entry. The entry name is included in theparentheses.

Inode_Tid_differ (entry_name)Found an inode tree id mismatch for a directory entry. The entry name is included in the parentheses.

CIFS_reserve_differ (entry_name)Found a cifs space reservation mismatch for a directory entry. The entry name is included in theparentheses.

HOLES_reserve_differ (entry_name)Found a holes space reservation mismatch for a directory entry. The entry name is included in theparentheses.

BLOCK_reserve_differ (entry_name)Found a block space reservation mismatch for a directory entry. The entry name is included in theparentheses.

QT_oplock_differ (entry_name)Found oplock setting mismatch for a qtree. The entry name is included in the parentheses.

QT_security_differ (entry_name)Found security setting mismatch for a qtree. The entry name is included in the parentheses.

QT_reserve_differ (entry_name)Found space reservation setting mismatch for a qtree. The entry name is included in the parentheses.

EXAMPLEA typical treecompare session in /etc/log/treecompare looks like:

Tue Jun 24 00:05:20 GMT fridge:/vol/src1/.snapshot/snap1/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 Start (cmp_level = data, compare NT ACL) Tue Jun 24 00:05:44 GMT fridge:/vol/src1/.snapshot/snap1/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 End (tree1_only = 0, tree2_only = 0, mismatch = 0)

This example shows a treecompare session which used comparison level data and did compare NTACLs. At the end of the session, the summary shows no mismatches were found.

The next example shows a log with several mismatches.

Tue Jun 24 00:07:31 GMT fridge:/vol/src1/.snapshot/snap2/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 Start (cmp_level = checksum, ignore NT ACL) Tue Jun 24 00:07:32 GMT fridge:/vol/src1/.snapshot/snap2/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 Atime_differ (.) Tue Jun 24 00:07:32 GMT fridge:/vol/src1/.snapshot/snap2/qt1 toaster:/vol/


treecompare

dst4/.snapshot/snap1/qt1 Atime_differ (./subd1) Tue Jun 24 00:07:42 GMT fridge:/vol/src1/.snapshot/snap2/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 Atime_differ (./subd1/dfile2) Tue Jun 24 00:07:42 GMT fridge:/vol/src1/.snapshot/snap2/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 Mtime_differ (./subd1/dfile2) Tue Jun 24 00:07:42 GMT fridge:/vol/src1/.snapshot/snap2/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 Size_differ (./subd1/dfile2) Tue Jun 24 00:07:42 GMT fridge:/vol/src1/.snapshot/snap2/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 Data_differ (block 0 in ./subd1/dfile2) Tue Jun 24 00:07:51 GMT fridge:/vol/src1/.snapshot/snap2/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 Data_differ (block 1000 in ./subd1/dfile2) Tue Jun 24 00:07:52 GMT fridge:/vol/src1/.snapshot/snap2/qt1 toaster:/vol/ dst4/.snapshot/snap1/qt1 End (tree1_only = 0, tree2_only = 0, mismatch = 7)

FILES

/etc/log/treecompare Treecompare log file for current week.

/etc/log/treecompare.[0-5] Treecompare log files for previous weeks.

SEE ALSO na_treecompare(1d)


treecompare

usermap.cfgNAMEna_usermap.cfg - mappings between UNIX and Windows NT accounts and users

SYNOPSIS/etc/usermap.cfg

DESCRIPTIONThe usermap.cfg file explicitly maps Windows NT users to the correct UNIX account and UNIX usersto the correct Windows NT account. Each line in /etc/usermap.cfg has the format:

[ IP-qual: ] [ NT-domain \] NTUser [ direction ] [ IP_qual: ] UnixUser

Lines are processed sequentially.

The following table describes the variables in the usermap.cfg file description.

IP-qual An IP qualifier that the filer uses to match a user. You use an IP qualifier to narrow a match. IP-qual can be a regular IP address, a host name, a network name, or a network name with a subnetspecified in dot notation.

NT-domain Specifies the domain to match or the domain to use for a mapped UNIX account. The default is thedomain in which the filer is installed.

NTUser Any user-type account name. If the name contains a space, put the name in quotation marks.

direction Restricts the direction of the mapping. By default, mappings are bidirectional. The three validdirection symbols are as follows: "=>" means NT to UNIX mapping only; "<=" means UNIX toNT mapping only; "==" means bidirectional mapping (use this to explicitly indicate a bidirectionalmapping).

The usermap.cfg file format uses the following symbol conventions. An asterisk (*) matches any name.The null string ("") matches no name and rejects any user. You can use either spaces or tabs asseparators.

Windows NT names are case-insensitive and can contain nonASCII characters within the character setin the current code page. Windows NT user names can contain spaces, in which case you must enclosethe name in quotation marks. UNIX user names are case-sensitive and must be in ASCII.

This manpage is not encyclopedic. Please refer to online documentation and the System Administrator’sGuide for further information.


usermap.cfg

EXAMPLESThe following usermap.cfg file ...

"Bob Garg" == bobgmktg\Roy => nobodyengr\Tom => ""uguest <= **\root => ""

maps NT user Bob Garg to UNIX user bobg and vice versa,

allows mktg\Roy to login, but only with the privileges of UNIX user nobody,

disallows login by NT user engr\Tom,

maps all other UNIX names to NT user uguest,

and disallows NT logins using the name root from all domains.


usermap.cfg

zoneinfoNAMEna_zoneinfo - time zone information files

SYNOPSIS/etc/zoneinfo

DESCRIPTIONThe directory /etc/zoneinfo contains time zone information files used by the timezone command (seena_timezone(1)). They are in standard Unix time zone file format as described below.

The time zone information files begin with bytes reserved for future use, followed by six four-bytesigned values, written in a "standard" byte order (the high-order byte of the value is written first). Thesevalues are, in order:

tzh_ttisgmtcnt The number of GMT/local indicators stored in the file.

tzh_ttisstdcnt The number of standard/wall indicators stored in the file.

tzh_leapcnt The number of leap seconds for which data is stored in the file.

tzh_timecnt The number of "transition times" for which data is stored in the file.

tzh_typecnt The number of "local time types" for which data is stored in the file (must not be zero).

tzh_charcnt The number of characters of "time zone abbreviation strings" stored in the file.

The above header is followed by tzh_timecnt four-byte signed values, sorted in ascending order. Thesevalues are written in "standard" byte order. Each is used as a transition time at which the rules forcomputing local time change. Next come tzh_timecnt one-byte unsigned values; each one tells whichof the different types of "local time" types described in the file is associated with the same-indexedtransition time. These values serve as indices into an array of structures that appears next in the file;these structures are written as a four-byte signed tt_gmtoff member in a standard byte order, followedby a one-byte signed tt_isdst member and a one-byte unsigned tt_abbrind member. In each structure, tt_gmtoff gives the number of seconds to be added to GMT, tt_isdst tells whether this time is during aDaylight Savings Time period and tt_abbrind serves as an index into the array of time zoneabbreviation characters that follow the structure(s) in the file.

Then there are tzh_leapcnt pairs of four-byte values, written in standard byte order; the first value ofeach pair gives the time at which a leap second occurs; the second gives the total number of leapseconds to be applied after the given time. The pairs of values are sorted in ascending order by time.


zoneinfo

Then there are tzh_ttisstdcnt standard/wall indicators, each stored as a one-byte value; they tellwhether the transition times associated with local time types were specified as standard time or wallclock time. A local time transition specified in standard time ignores any offset due to Daylight SavingsTime. On the other hand, a time specified in wall clock time takes the prevailing value of DaylightSavings Time in to account.

Finally there are tzh_ttisgmtcnt GMT/local indicators, each stored as a one-byte value; they tellwhether the transition times associated with local time types were specified as GMT or local time.

SEE ALSOna_timezone(1)


zoneinfo

autosupportNAMEna_autosupport - notification daemon

SYNOPSISData ONTAP is capable of sending automated notification to Customer Support at IBM and/or to otherdesignated addressees in certain situations. The notification contains useful information to help themsolve or recognize problems quickly and proactively. The system can also be configured to send a shortalert notification containing only the reason for the alert to a separate list of recipients. This notificationis sent only for critical events that might require some corrective action and can be useful forAdministrators with alphanumeric pagers that can accept short email messages.

DESCRIPTIONThe autosupport mechanism will use SMTP if there are any (user configured) destination emailaddresses set in the autosupport.to option. If autosupport.support.enable is on then autosupports willalso be sent to IBM. Autosupports sent to IBM may be transmitted by SMTP or by HTTP as specifiedin the autosupport.support.transport option.

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

If autosupport.support.enable is on then a copy of the autosupport message is also sent to IBM asfollows:

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

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

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

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


autosupport

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

The setup command tries to configure autosupport as follows:

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

Setup also queries for autosupport.from information.

OPTIONSAutosupport features are manipulated through the options command (see na_options(1)). The availableoptions are as follows:

autosupport.cifs.verboseIf on, includes CIFS session and share information in autosupport messages. If off, those sections areomitted. The default is off.

autosupport.contentThe type of content that the autosupport notification should contain. Allowable values are complete and minimal. The default value is complete. The minimal option allows the delivery of a "sanitized" andsmaller version of the autosupport, at the cost of reduced support from IBM. Please contact IBM if youfeel you need to use the minimal option. The complete option is the traditional (and default) form ofautosupport. If this option is changed from complete to minimal then all previous and pendingautosupport messages will be deleted under the assumption that complete messages should not betransmitted.

autosupport.doitTriggers the autosupport daemon to send an autosupport notification immediately. A text word enteredas the option is sent in the notification subject line and should be used to explain the reason for thenotification.

autosupport.enableEnables/disables the autosupport notification features (see na_autosupport(8)). The default is on tocause autosupport notifications to be sent. This option will override the autosupport.support.enableoption.

autosupport.fromDefines the user to be designated as the sender of the notification. The default is [email protected]. Email replies from IBM will be sent to this address.

autosupport.local.nht_data.enableEnables/disables the NHT data autosupport to be sent to the recipients listed in the autosupport.tooption. NHT data is the binary, internal log data from each disk drive, and in general, is not parsable byother than IBM. There is no customer data in the NHT autosupport. The default for this option is off.

autosupport.local.performance_data.enableEnables/disables performance data autosupport to be sent to the recipients listed in autosupport.to. Theperformance autosupport contains hourly samples of system performance counters, and in general isonly useful to IBM. The default is off.


autosupport

autosupport.mailhostDefines the list of up to 5 mailhost names. Enter the host names as a comma-separated list with nospaces in between. The default is an empty list.

autosupport.minimal.subject.idDefines the type of string that is used in the identification portion of the subject line when autosupport.content is set to minimal. Allowable values are systemid and hostname. The default is systemid.

autosupport.notetoDefines the list of recipients for the autosupport short note email. Up to 5 mail addresses are allowed.Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list todisable short note emails.

autosupport.nht_data.enableEnables/disables the generation of the Health Trigger (NHT) data autosupport. Default is off

autosupport.performance_data.enableEnables/disables hourly sampling of system performance data, and weekly creation of a performancedata autosupport. The default is on.

autosupport.retry.countNumber of times to try resending the mail before giving up and dropping the mail. Minimum is 5;maximum is 4294967295 ; The default is 15 .

autosupport.retry.intervalTime in minutes to delay before trying to send the autosupport again. Minimum is 30 seconds,maximum is 1 day. Values may end with ‘s’, ‘m’ or ‘h’ to indicate seconds, minutes or hoursrespectively, if no units are specified than input isassumed to be in seconds. The default value is 4m.

autosupport.support.enableEnables/disables the autosupport notification to IBM The default is on to cause autosupportnotifications to be sent directly to IBM as described by the autosupport.support.transport option.This option issuperceded (overridden) by the value of autosupport.enable.

autosupport.support.proxyAllows the setting of an http based proxy if autosupport.support.transport is https or http. Thedefault for this option is the empty string, implying no proxy is necessary.

autosupport.support.toThis option is read only; it shows where autosupport notifications to IBM are sent if autosupport.support.transport is smtp.

autosupport.support.transportAllows setting the type of delivery desired for autosupport notifications that are destined for IBM.Allowed values are https, http (for direct web based posting) or smtp (for traditional email). Thedefault value is https. Note that http and https may (depending on local network configuration) requirethat the autosupport.support.proxy option be set correctly. Also smtp requires that autosupport.mailhosts be configured correctly before autosupport delivery can be successful.


autosupport

autosupport.support.urlThis option is read only; it shows where autosupport notifications to IBM are sent if autosupport.support.transport is https or http.

autosupport.throttleEnables autosupport throttling (see na_autosupport(8)). When too many autosupports are sent in tooshort a time, additional messages of the same type will be dropped. Valid values for this option are onor off. The default value for this option is on.

autosupport.toDefines the list of recipients for the autosupport email notification. Up to 5 mail addresses are allowed.Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list.Note that it is no longer necessary to use the standard IBM autosupport email address in this field todirect autosupport messages to IBM. Please use autosupport.support.enable instead.

CONTENTSA complete autosupport will contain the following information. Note that some sections areconfigurable, and/or available depending on what features are licensed. The order given is the generalorder of appearance in the autosupport message itself.

Generation date and timestamp

Software Version

System ID

Hostname

SNMP contact name (if specified)

SNMP location (if specified)

Partner System ID (if clustered)

Partner Hostname (if clustered)

Cluster Node Status (if clustered)

Console language type

sysconfig -a output

sysconfig -c output

sysconfig -d output

System Serial Number

Software Licenses (scrambled prior to transmission)


autosupport

Option settings

availtime output

cf monitor all output (if clustered)

ic stats performance output (if clustered with VIA)

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

snet stats -v output (if clustered with SNET)

ifconfig -a output

ifstat -a output

vlan stat output

vif status output

nis info output

nfsstat -c output (if licensed)

cifs stat output (if licensed)

cifs sessions summary (if licensed)

cifs sessions output (if licensed and enabled)

cifs shares summary (if licensed)

cifs shares output (if licensed and enabled)

vol status -l (if cifs is licensed)

httpstat output

vfiler status -a output (if licensed)

df output

df -i output

snap sched output

vol status -v output

vol status output

vol status -c output


autosupport

vol scrub status -v output

sysconfig -r output

fcstat fcal_stats output

fcstat device_map output

fcstat link_stats output

ECC Memory Scrubber Statistics

ems event status output

ems log status output

registry values

perf report -t output

storage show adapter -a output

storage show hub -a output

storage show disk -a output

storage show fabric output

storage show switch output

storage show port output

EMS log file (if enabled)

/etc/messages content

Parity Inconsistancy information

WAFL_check logs

TYPESThe following types of autosupport messages, with their associated severity, can be generatedautomatically. The autosupport message text is in bold, and the LOG_XXX value is the syslog severitylevel. Note that text inside of square brackets ([]) is descriptive and is not static for any givenautosupport message of that type.

BATTERY_LOW!!!LOG_ALERT

BMC_EVENT: BUS ERRORLOG_ERR


autosupport

BMC_EVENT: POST ERRORLOG_ERR

CLUSTER DOWNREV BOOT FIRMWARELOG_CRIT

CLUSTER ERROR: DISK/SHELF COUNT MISMATCH LOG_EMERG

CLUSTER GIVEBACK COMPLETELOG_INFO

CLUSTER TAKEOVER COMPLETE AUTOMATICLOG_ALERT

CLUSTER TAKEOVER COMPLETE MANUALLOG_INFO

CLUSTER TAKEOVER FAILEDLOG_INFO

CONFIGURATION_ERROR!!!LOG_ALERT

CPU FAN WARNING - [fan]LOG_WARNING

DEVICE_QUALIFICATION_FAILEDLOG_CRIT

DISK CONFIGURATION ERRORLOG_ALERT

DISK RECONSTRUCTION FAILED!!LOG_ALERT

DISK_FAIL!!! - Bypassed by ESHLOG_ALERT

DISK_FAIL!!!LOG_ALERT

DISK_FAILURE_PREDICTED!!!LOG_ALERT

DISK_FIRMWARE_NEEDED_UPDATE!!!LOG_EMERG

DISK_IO_DEGRADEDLOG_WARNING


autosupport

DISK_LOW_THRUPUTLOG_NOTICE

DISK_RECOVERED_ERRORSLOG_WARNING

DISK_SCRUB!!!LOG_EMERG

FC-AL LINK_FAILURE!!!LOG_ERR

FC-AL RECOVERABLE ERRORSLOG_WARNING

OVER_TEMPERATURE_SHUTDOWN!!!LOG_EMERG

OVER_TEMPERATURE_WARNING!!!LOG_EMERG

PARTNER DOWN, TAKEOVER IMPOSSIBLELOG_ALERT

POSSIBLE BAD RAMLOG_ERR

POSSIBLE UNLINKED INODELOG_ERR

REBOOT (CLUSTER TAKEOVER)LOG_ALERT

REBOOT (after WAFL_check)LOG_INFO

REBOOT (after entering firmware)LOG_INFO

REBOOT (after giveback)LOG_INFO

REBOOT (halt command)LOG_INFO

REBOOT (internal halt)LOG_INFO

REBOOT (internal reboot)LOG_INFO


autosupport

REBOOT (panic)LOG_CRIT

REBOOT (power glitch)LOG_INFO

REBOOT (power on)LOG_INFO

REBOOT (reboot command)LOG_INFO

REBOOT (watchdog reset)LOG_CRIT

REBOOTLOG_INFO

SHELF COOLING UNIT FAILEDLOG_EMERG

SHELF COOLING UNIT FAILEDLOG_WARNING

SHELF_FAULT!!!LOG_ALERT

SNMP USER DEFINED TRAPLOG_INFO

SPARE_FAIL!!!LOG_ALERT

SYSTEM_CONFIGURATION_CRITICAL_ERRORLOG_CRIT

SYSTEM_CONFIGURATION_ERRORLOG_ERR

UNDER_TEMPERATURE_SHUTDOWN!!!LOG_EMERG

UNDER_TEMPERATURE_WARNING!!!LOG_EMERG

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

WAFL_check!!!LOG_ALERT


autosupport

WEEKLY_LOGLOG_INFO

[EMS event]LOG_INFO

[fan] FAN_FAIL!!!LOG_ALERT

[mini core]LOG_CRIT

[power supply failure]LOG_ALERT

[power supply] POWER_SUPPLY_DEGRADED!!!LOG_ALERT

[shelf over temperature critical]LOG_EMERG

CLUSTER CONSIDERATIONSThe autosupport email messages from a filer in a cluster are different from the autosupport emailmessages from a standalone filer in the following ways:

The subject in the autosupport email messages from a filer in a cluster reads, ‘‘Cluster notification,’’instead of ‘‘System notification.’’

The autosupport email messages from a filer in a cluster contains information about its partner, such asthe partner system ID and the partner host name.

In takeover mode, if you reboot the live filer, two autosupport email messages notify the emailrecipients of the reboot: one is from the live filer and one is from the failed filer.

The live filer sends an autosupport email message after it finishes the takeover process.

SEE ALSOna_hosts(5), RFC821


autosupport

cifsNAMEna_cifs - Common Internet File System (CIFS) Protocol

DESCRIPTIONThe filer supports the CIFS protocol, which is documented in an Internet Engineering Task Force(IETF) InternetDraft specification titled "A Common Internet File System (CIFS/1.0) Protocol."

CIFS is a file sharing protocol intended to provide an open cross-platform mechanism for client systemsto request file services from server systems over a network. it is based on the standard Server MessageBlock (SMB) protocol widely in use by personal computers and workstations running a wide variety ofoperating systems.

SEE ALSOna_cifs_audit(1), na_cifs_help(1), na_cifs_sessions(1),

na_cifs_shares(1), na_cifs_testdc(1)

RFC 1001, RFC 1002


cifs

cliNAMEna_cli - Data ONTAP command language interperter (CLI)

DESCRIPTIONThe Data ONTAP CLI is a command language interpreter that executes commands from the DataONTAP console. You can access the console with a physical connection, through telnet, or through theRemote LAN Manager (RLM). The commands can also be executed using rsh and ssh protocols.

You can concatenate commands together on the same line by separating the commands withsemi-colons, (;).

QuotingThe quoting rules in the Data ONTAP CLI are unusual. There is no escape character like the backslash;however there are the following special characters:

& (ampersand) - unicode indicator # (pound sign) - comment indicator ; (semicolon) - command separator ’ (single quote) - parameter wrapper " (double quote) - parameter wrapper (space) - parameter separator (tab) - parameter separator

When special characters are part of a command argument, the argument needs to be surrounded byquotes or the character will be treated as a special character. A single quote character needs to besurrounded by double quote characters and a double quote character needs to be surrounded by singlequote characters. The other special characters can be surrounded by either single or double quotes.

EXAMPLESThe following examples show quote usage:

qtree create /vol/test_vol/’qtree 1’

The qtree qtree 1 is created.

qtree create /vol/test_vol/’qtree#1’

The qtree qtree#1 is created.

qtree create /vol/test_vol/"qtree’1"

The qtree qtree’1 is created.

qtree create /vol/test_vol/’hello"’"’"1


cli

The qtree hello"’1 is created.

cifs shares add jふxp /vol/test_vol/home

Creates a share with a Japanese character; whereas

cifs shares add "jふxp" /vol/test_vol/home

Creates the share jふxp.

sysconfig; version

Executes the sysconfig and version commands.

SEE ALSOna_rshd(8), na_source(1),


cli

dnsNAMEna_dns - Domain Name System

DESCRIPTIONDomain Name Service provides information about hosts on a network. This service has two parts: aresolver which requests information and a nameserver which provides it.

Data ONTAP supports only the resolver. When the filer needs to resolve a host address, it first looks atthe /etc/nsswitch.conf (see na_nsswitch.conf(5)) file to get the order in which various name services areto be consulted. If the name services before DNS fail in their lookup and DNS is enabled, then the DNSname server is contacted for address resolution.

DNS can be enabled on the filer by running the setup command (see na_setup(1)) or by manuallyediting the configuration files as described below. If DNS is enabled by running the setup command,then the DNS domain name needs to be entered.

Enabling DNS without the setup command:

1. Create the /etc/resolv.conf file (see na_resolv.conf(5)) with up to 3 nameservers. Each line containsthe keyword nameserver followed by the IP address of the server. For example:

nameserver 192.9.200.1 nameserver 192.9.201.1 nameserver 192.9.202.1

2. Edit the /etc/rc file (see na_rc(5)) to make sure that the option specifying the DNS domain name isset and the option to enable DNS is on. For example:

options dns.domainname mycompany.com options dns.enable on

3. Reboot the filer for these changes to take effect. If the above options commands are also entered fromthe console, the reboot can be avoided.

Enabling DNS with the setup command:

At setup time, one can choose to enable DNS when prompted to do so. setup then queries for theInternet addresses of up to three DNS nameservers.

VFILER CONSIDERATIONSWhen run from a vfiler context, (e.g. via the vfiler run command), dns displays DNS information aboutthe concerned vfiler.


dns

SEE ALSOna_resolv.conf(5), RFC1034, RFC1035


dns

httpNAMEna_http - HyperText Transfer Protocol

DESCRIPTIONThe filer supports the HTTP/1.0 protocol, which is documented in the Internet Engineering Task Force(IETF) RFC 1945 titled "HyperText Transfer Protocol --HTTP/1.0."

HTTP is the primary Internet protocol used for transferring documents on the World Wide Web. It is asimple ASCII text request/response protocol. An HTTP request consists of a method, a target Webaddress or URL (Uniform Resource Locator), a protocol version identifier, and a set of headers. Themethod specifies the type of operation. For example, the GET method is used to retrieve a document.The POST method is used to submit a form. Headers contain additional information to the request inthe form of simple name-value pairs. The HTTP header section is similar to Multipurpose Internet MailExtensions (MIME).

The GET method is the most commonly used HTTP method. GET is used to retrieve a single resource,for example, an HTML document, image file, or other type of object, or part of it. By appending an If-modified-since header to the GET request, the document is retrieved conditionally, based on whetherit has been modified since the date specified in the header.

An HTTP response consists of a protocol version identifier, a status code, a text response status line,response headers, and the contents of the requested document.

Access for http can be restricted by the options httpd.access command. Please seena_protocolaccess(8) for details.

EXAMPLESThe following is an example of use of the GET method:

GET http://www.somesite.com/ HTTP/1.0 If-modified-since: Fri, 31 Dec 1999 15:45:12 GMT

SEE ALSOna_httpd.hostprefixes(5),

na_httpd.mimetypes(5), na_httpstat(1), na_protocolaccess(8)


http

nfsNAMEna_nfs - Network File System (NFS) Protocol

DESCRIPTIONThe filer supports versions 2, 3, and 4 of the NFS protocol, which are documented in RFC’s 1094,1813, and 3530 respectively.

NFS is a widely used file sharing protocol supported on a broad range of platforms. The protocol isdesigned to be stateless, allowing easy recovery in the event of server failure. Associated with the NFSprotocol are two ancillary protocols, the MOUNT protocol and the NLM protocol. The MOUNTprotocol provides a means of translating an initial pathname on a server to an NFS filehandle whichprovides the initial reference for subsequent NFS protocol opertions. The NLM protocol provides filelocking services, which are stateful by nature, outside of the stateless NFS protocol.

NFS is supported on both TCP and UDP transports. Support for TCP and UDP is enabled by default.Either one can be disabled by setting the nfs.tcp.enable or nfs.udp.enable options using the optionscommand.

SEE ALSOna_nfsstat(1), na_exports(5),


nfs

nisNAMEna_nis - NIS client service

DESCRIPTIONThe NIS client service provides information about hosts, user passwords, user groups and netgroups ona network. In NIS terminology, each of the above is referred to as the map and the specific informationbeing looked up is called the key. For example, the hosts map is like the /etc/hosts file; it provides atranslation from host names to IP addresses. The NIS service typically has two parts: a client componentwhich requests information and a name server which provides it.

Data ONTAP supports only the NIS client. When the filer needs to resolve a key in a given map, itlooks at the /etc/nsswitch.conf (see na_nsswitch.conf(5)) file to figure out the order in which thevarious databases should be consulted. For example, in case of the hosts map the lookup order may be file, nis, dns. This means that the filer will first consult the /etc/hosts file. If the host name is not foundin the local file, it will then try the NIS service. If the host name is still not found, then it will attempt aDNS lookup.

The NIS client can be enabled on the filer by running the setup command (see na_setup(1)) or bymanually editing the configuration files as described below. If NIS is enabled by running the setupcommand, then the NIS domain name needs to be entered.

Enabling NIS without the setup command:

1. Edit the /etc/rc file (see na_rc(5)) to make sure that the option specifying the NIS domain name is setand the option to enable NIS is on. For example:

options nis.domainname mycompany.com options nis.enable on

2. Reboot the filer for these changes to take effect. If the above options commands are also entered fromthe console, the reboot can be avoided. If the options are entered via the console only, they are notsaved across a reboot.

Enabling NIS with the setup command:

At setup time, one can choose to enable NIS when prompted to do so. setup then queries for the NISdomain name.

SEE ALSOna_nsswitch.conf(5).


nis

pcnfsdNAMEna_pcnfsd - (PC)NFS authentication request server

DESCRIPTIONpcnfsd provides a personal computer NFS client with the authentication services. This release supportsversions 1 and 2 of the PCNFSD protocol.

When pcnfsd receives an authentication request, it will register the user by validating the user name andpassword and returning the corresponding UID and primary GID pair, and the secondary group set forPCNFSD version 2.

It will look up the user in the /etc/shadow file, or the passwd.adjunct NIS map, if present, to find theuser’s password. It will look up the user in the /etc/passwd file, or the passwd.byname NIS map, tofind the user’s UID and primary GID, and to find the user’s password if there is no /etc/shadow file or passwd.adjunct NIS map.

For a PCNFSD version 2 request, it will scan the /etc/group file, or the group.byname NIS map, tofind all the groups of which the user is a member. It will look up the user in the auto.home NIS map, ifNIS is enabled, to find the user’s home directory; if NIS is not enabled, no home directory will bereturned.

FILES

/etc/passwd This file should be in the format used on many flavors of UNIX (SunOS 4.x and later, 4.4BSD,System V Release 4 and later, and others).

/etc/group This file should be in the format used on many flavors of UNIX (SunOS 4.x and later, 4.4BSD,System V Release 4 and later, and others).

/etc/shadow This file should be in the format used on many flavors of UNIX (SunOS 5.x and later, System VRelease 4 and later, and others).

SEE ALSOna_nis(8)

BUGSWhen the call fails, pcnfsd doesn’t fake by setting the UID and the GID to acceptable values.Passwords that have been encrypted using Kerberos are not supported.


pcnfsd

protocolaccessNAMEna_protocolaccess - Describes protocol access control

DESCRIPTIONProtocol access control defines a method to restrict access to the filer on a protocol-by-protocol basis.For example, the command options rsh.access host=admin restricts access to rsh to a host namedadmin. Access can be restricted by host name, IP address, and/or network interface name.

USAGEThe syntax is as follows:

options protocol.access access_spec [ AND | OR [ ( ] access_spec [ ) ] ... ]

protocol is currently one of the following: rsh, telnet, ssh, httpd, httpd.admin, snmp, ndmpd, snapmirror,or snapvault.

access_spec is composed of keywords and their values. Currently the following keywords and valuesare defined:

host [=|!=] host specif [=|!=] network interface spec allnonelegacy*

host spec is a comma separated list consisting of either a host name, an IP address, or an IP address witha netmask. Valid host name is a string and cannot contain the following characters: "=", "(", ")", "!","*", and "," . An IP address is of the format aa.bb.cc.dd . If the IP address contains a netmask, then theformat is: aa.bb.cc.dd/mm where mm represents the number of bits from the left.

network interface spec is a comma separated list of one or more network interface names. Validnetwork interface names can be obtained from the ifconfig -a command.

The access specs may be and’ed and or’ed by the keywords AND and OR respectively. The keywords AND and OR are not case-sensitive.

Operational precedence is from left to right. Parentheses may be used to force operational order.

The keyword all is used to allow access to all. The keyword none is used to allow access to none. The legacy keyword is used to specify previous behavior. For example, the legacy behavior of telnet is touse trusted.hosts, while the legacy behavior of rsh is to allow all.

The access spec can be a "*" which matches all. This is the same as the all keyword. If the access specis a "-", then all access is denied. This is the same as the none keyword.


protocolaccess

The difference between setting the host value to an IP address or a host name becomes apparent whenthe matching occurs. IP addresses are matched before the connection is made. If access is denied, theconnection is not made and the client times out. Therefore, specifiyng the IP address lessens the impactof denial of service attacks. Host names are matched after the connection is made, and therefore theclient is informed that access is denied.

If httpd.admin.access is not set to legacy, then trusted.hosts is ignored for httpd.admin. If telnet.access is not set to legacy, then trusted.hosts is ignored for telnet. If snapmirror.access is notset to legacy, then the /etc/snapmirror.allow file is ignored for snapmirror destination checking.

EXAMPLESHere are some protocol access control examples:

Allow an NDMP server to accept control connection request from any client.

options ndmpd.access legacy

Allow remote shell access for only one host named gnesha.zo.

options rsh.access "host = gnesha.zo"

Allow access for Telnet subnet 10.42.69.

options telnet.access host=10.42.69.1/24

Allow ssh access for hosts abc and xyz when on network interface e0.

options ssh.access "host=abc,xyz AND if=e0"

Allow access to SNMP for network interfaces e0, e1, and e2.

options snmp.access if=e0,e1,e2

Do not allow access to HTTPD for network interface e3.

options httpd.access "if != e3"

Allow access to administrative HTTPD from for two hosts.

options httpd.admin.access host=champagne,tequilla

Disallow all access to Telnet.

options telnet.access "host=-"

Set httpd.admin to use previous trusted.hosts access

options httpd.admin.access legacy

Point SnapMirror to the (deprecated) /etc/snapmirror.allow file to check access to sources from otherfilers.


protocolaccess

options snapmirror.access legacy

Allow a SnapVault server to accept any client requests.

options snapvault.access all

Note: quotes are needed around access specifications that include blanks.

SEE ALSOna_snmpd(8)


protocolaccess

rmtNAMEna_rmt - remote magtape protocol module

SYNOPSIS/etc/rmt

DESCRIPTION/etc/rmt is a special command that can be used by remote computers to manipulate a magnetic tapedrive over a network connection; for example, the UNIX dump and restore commands often can eitheruse /etc/rmt to access a remote tape, or have rdump and rrestore variants that can do so. /etc/rmt isnormally run by the rshd daemon (see na_rshd(8)) as a result of a remote machine making a request to rshd to do so.

The /etc/rmt command accepts requests specific to the manipulation of magnetic tapes, performs thecommands, then responds with a status indication. This protocol is provided by rmt commands onmany UNIX systems, although UNIX systems may support more commands and may give moredifferent error codes.

All responses are in ASCII and in one of two forms. Successful commands have responses of:

Anumber\n

number is an ASCII representation of a decimal number. Unsuccessful commands are responded towith:

Eerror-number\nerror-message\n

error-number is one of:

2 (ENOENT)The tape device specified in an open request did not have a valid syntax.

6 (ENXIO)The tape device specified in an open request does not exist.

5 (EIO)An I/O error occurred when performing the request.

25 (ENOTTY)An invalid tape operation was specified in a ‘‘perform special tape operation’’ request.

error-message is a (UNIX-style) error string for the error specified by error-number.

The protocol is comprised of the following commands, which are sent as indicated - no spaces aresupplied between the command and its arguments, or between its arguments, and \n indicates that anewline should be supplied:


rmt

Odevice\nmode\nOpen the specified device using the indicated mode. device is a tape name of the form described inna_tape(4) and mode is an ASCII representation of a decimal number specifying how the tape is to beopened:

0 read-only

1 write-only

2 read-write

If a device had already been opened, it is closed before a new open is performed.

Cdevice\nClose the currently open device. The device specified is ignored.

Lwhence\noffset\nPerforms no operation, and returns the value of offset; UNIX-style lseek operations are ignored on IBMfiler tape devices, just as they are on tape devices on many UNIX systems.

Wcount\nWrite data onto the open device. If count exceeds the maximum data buffer size (64 kilobytes), it istruncated to that size. /etc/rmt then reads count bytes from the connection, aborting if a prematureend-offile is encountered. The response value is the number of bytes written if the write succeeds, or -1if the write fails.

Rcount\nRead count bytes of data from the open device. If count exceeds the maximum data buffer size (64kilobytes), it is truncated to that size. /etc/rmt then attempts to read count bytes from the tape andresponds with Acount-read\n if the read was successful; otherwise an error in the standard format isreturned. If the read was successful, the data read is then sent.

Ioperation\ncount\nPerform a special tape operation on the open device using the specified parameters. The parameters areinterpreted as ASCII representations of the decimal values. operation is one of:

0 write end-of-file marker

1 forward space count files

2 backward space count files

3 forward space count tape blocks


rmt

4 backward space count tape blocks

5 rewind the tape

6 rewind and unload the tape

The return value is the count parameter when the operation is successful.

Any other command causes /etc/rmt to close the connection.

DIAGNOSTICSAll responses are of the form described above.

SEE ALSOna_rshd(8)


rmt

rquotadNAMEna_rquotad - remote quota server

DESCRIPTIONThe filer supports the remote quota service that allows NFS clients to determine their quota allocationon the server.

SEE ALSOna_quota(1)

BUGSThe rquota protocol doesn’t support group or tree quotas.


rquotad

rshdNAMEna_rshd - remote shell daemon

DESCRIPTIONThe filer has UNIX-compatible remote shell capability that enables you to execute certain filercommands from a UNIX command line or shell script. It also enables you to use a remote shellapplication on a PC to run filer commands.

The value of rsh.access controls access to the filer, and is set by options rsh.access. Seena_protocolaccess(8) for more details. This value is checked prior to the authentication mechanismsdiscussed below.

The /etc/hosts.equiv file controls authentication to the filer remote shell. The hosts and users (on thosehosts) listed in the /etc/hosts.equiv file are automatically authenticated. This means that the fileraccepts remote shell commands via rsh from these hosts and users.

An alternative authentication mechanism for rshd is to have the client use rsh with a -l option thatspecifies the admin_name and password in the form of -l admin_name:password. Both the admin_nameand password are created with the filer’s useradmin command.

EXAMPLEThe following example shows how to run the version command from a trusted host named adminhostthrough a remote shell:

adminhost% rsh -l root toaster version

The following example shows how to run the sysconfig -r command with a password rpass42 from anuntrusted host named ahost through a remote shell:

ahost% rsh -l root:rpass42 toaster sysconfig -r

To see a list of filer commands that can be executed, enter:

adminhost% rsh -l root toaster "?"

SEE ALSOna_protocolaccess(8)


rshd

snmpdNAMEna_snmpd - snmp agent daemon

DESCRIPTIONThe filer supports an SNMP version 1 (RFC 1157) compatible agent that provides support for both theMIB-II (RFC 1213) management information base for TCP/IP based internets as well as a Data ONTAPCustom MIB.

A number of user configurable options for the SNMP agent can be set and queried from the consoleusing the snmp command (see na_snmp(1)).

Due to weak authentication in SNMP version 1, SetRequest commands that allow the remote setting ofconfiguration variables have been disabled.

Access for snmp can be restricted by the options snmp.access command. Please seena_protocolaccess(8) for details.

MIB-II

Under MIB-II, information is accessible for the system, interfaces, at, ip, icmp, tcp, udp and snmpMIBII groups. The transmission and egp groups are not supported.

The coldStart, linkDown, linkUp and authenticationFailure traps are implemented. Traps areconfigured using the snmp command.

DATA ONTAP CUSTOM MIB

The Data ONTAP Custom MIB provides a means to obtain detailed information about many aspects offiler operation via SNMP.

The following is a summary of the top-level groups in the Custom MIB and the information theycontain:

productProduct-level information such as the software version string and system ID.

sysStatSystem-level statistics such as CPU uptime, idle time and aggregate kilobytes received and transmittedon all network interfaces.

nfsStatistics like those displayed by the nfsstat command (see na_nfsstat(1)), including statistics for eachclient if per-client NFS statistics have been enabled using the nfs.per_client_stats.enable option (seena_options(1)). The per-client NFS statistics are indexed by client IP addresses.


snmpd

quotaInformation related to disk quotas, including the output of the quota report command (see na_quota(1)).To access quota information, quotas must be turned on.

filesysInformation related to the file system, including the equivalent of the maxfiles and df commands, andsome of the information from the snap list command (see na_maxfiles(1), na_snap(1)).

raidInformation on RAID equivalent to the output of the sysconfig -r command (see na_sysconfig(1)).

CLUSTER CONSIDERATIONSIn takeover mode, SNMP agents can continue to access the MIBs on both filers in a cluster. However,the counters reported by SNMP are combined counters from both filers. For example, in takeover mode,the SNMP agent can report the number of packets sent or received by both filers, but you cannotdetermine from the number how many packets are sent or received on each filer.

You can have an application on the network management station set an alarm when a filer has beentaken over. The SNMP variable to check is the netapp.netapp1.sysStat.cf.cfSettings variable. If thisvariable is set to thisNodeDead, the filer has been taken over.

SEE ALSOna_options(1), na_snmp(1), na_protocolaccess(8)


snmpd

syslogdNAMEna_syslogd - log system messages

DESCRIPTIONThe syslogd daemon logs system messages to the console, log files and other remote systems asspecified by its configuration file, /etc/syslog.conf. The syslogd daemon reads its configuration filewhen it starts up during the boot procedure, or within 30 seconds after the /etc/syslog.conf file ismodified. For information on the format of the configuration file, see na_syslog.conf(5).

If /etc/syslog.conf does not exist the syslogd daemon will output all log messages of priority info orhigher to the console and to the file /etc/messages. To prevent /etc/messages from getting too large, the syslogd daemon will rotate the contents of /etc/messages through the files /etc/messages.0 through /etc/messages.5. This rotation is done once a week. So the log messages of the current week will besaved in the file /etc/messages and the message logs of the six weeks prior to that are saved in the files /etc/messages.0 through /etc/messages.5.

To prevent large numbers of repeated messages being logged, the syslogd daemon will follow the firstinstance of a repeated message with the number of times the message was repeated. If a message isrepeated over a long time period, the syslogd daemon will wait for increasingly longer intervals beforelogging the number of repeats. The repeat notification interval starts at 30 seconds and moves quickly to20 minutes.

FILES

/etc/syslog.conf The configuration file. /etc/syslog.conf.sample A sample configuration file.

/etc/messages Message log file for current week.

/etc/messages.[0-5] Message log for prior weeks.

CLUSTER CONSIDERATIONSIn takeover mode, the failed filer logs syslog messages to its own /etc/messages file and to the /etc/messages file on the live filer. The live filer logs its syslog messages only to its own /etc/messagesfile.

Because the /etc/messages file on the live filer contains syslog messages from two filers, the filer usesfiler names in the syslog messages to indicate the filer from which the syslog message originated.

For example, if toaster1 takes over toaster2, a message from toaster2 is logged to the /etc/messagesfile on toaster1, and the message can be similar to the following:


syslogd

Wed May 6 18:57:52 GMT [toaster2/toaster1]: raid_disk_admin]: Volume vol7 has been added to the system.

If the name of the failed filer is unknown, the string ‘‘partner’’ is printed instead of a filer name.



syslogd

Readers’ Comments — We’d Like to Hear from You

IBM System Storage N series

Data ONTAP 7.2 Commands Manual Page Reference, Volume 2

Publication No. GC26-7972-04

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,

organization, subject matter, or completeness of this book. The comments you send should pertain to only the

information in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, your

IBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any

way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use

the personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Submit your comments using one of these channels:

v Send your comments to the address on the reverse side of this form.

If you would like a response from IBM, please fill in the following information:

Name

Address

Company or Organization

Phone No. E-mail address

Readers’ Comments — We’d Like to Hear from You GC26-7972-04

GC26-7972-04

��

Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

International Business Machines Corporation

Information Development

Dept. GZW

9000 South Rita Road

Tuscon, AZ

U.S.A. 85744-0001

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

��

NA 210-03868_A0, Printed in USA

GC26-7972-04

IBM System Storage N series Data ONTAP 7 2 Commands Manual Page Reference, Volumes 2

Documents

gigabit ethernet link

creating setuid executables

relevant manual page

manual page reference

ndmp extension specifications

windows nt accounts

netscape communications corp

ndmp protocol specifications