1. Manuals
  2. Brands
  3. Acopia Manuals
  4. Switch
  5. Adaptive Resource Switch
  6. Cli maintenance manual

Acopia Adaptive Resource Switch Cli Maintenance Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
CLI Maintenance Guide
Part Number: 810-0045-00, Revision F
Acopia Networks®, Inc.
41 Wellman Street
Lowell, MA 01851
(978) 513-2900 tel
(978) 513-2990 fax

Advertisement

Table of Contents
loading

Related Manuals for Acopia Adaptive Resource Switch

Summary of Contents for Acopia Adaptive Resource Switch

  • Page 1 CLI Maintenance Guide Part Number: 810-0045-00, Revision F Acopia Networks®, Inc. 41 Wellman Street Lowell, MA 01851 (978) 513-2900 tel (978) 513-2990 fax...

  • Page 2: Revision History

    In no event will Acopia Networks be liable for direct, indirect, special, exemplary, incidental, or consequential damages resulting from any defect or omission within this document. Acopia Networks®, Inc. reserves the right to alter the contents of this document at any time, and without any notice.

  • Page 3: Table Of Contents

    Contents Chapter 1 Introduction The ARX ........................1-1 Back-end Storage and Servers ................1-2 Front-end Services .....................1-2 Policy .........................1-2 Resilient Overlay Network (RON) ..............1-3 Audience for this Manual..................1-3 Using this Manual .....................1-3 Document Conventions .....................1-4 CLI Overview......................1-5 Exec Mode ......................1-5 Global Commands ..................1-5 Priv-exec Mode ....................1-5 Cfg Mode ....................1-5 Gbl Mode ....................1-6...
  • Page 4 Running the Restore from a Remote Host............2-8 Showing all Restore Operations ................2-10 Focusing on a Single Namespace, Volume, or Path ........2-12 Clearing Restore Operations from the Output..........2-13 Canceling a Restore Operation ................2-14 Chapter 3 Backing Up the Running Configuration Setting a Default FTP User..................
  • Page 5 Chapter 4 Upgrading Software Before You Begin ......................4-1 Clearing Space for a New Release File..............4-2 Showing the Software Versions .................4-3 Deleting a Release File ..................4-4 Copying a Release File to the Switch................4-5 Downloading from an SCP Server..............4-6 Showing the Version of a Release File...............4-7 Validating the Release File .................4-7 Arming the Switch with the Release File..............4-8 Rebooting the Switch ....................4-8...
  • Page 6 Focusing on One Share..................5-10 Sending the Output to a Different File ............5-11 Warning Signs for Metadata Inconsistencies............5-11 Finding Metadata Inconsistencies................5-12 Focusing on Multi-Protocol Issues..............5-16 Synchronizing Metadata with Actual Files............. 5-19 Synchronizing with Actual Directories ............5-22 Synchronizing Metadata in a Single Share............
  • Page 7 Reading IDs for Namespaces, Volumes, and Shares........6-17 Paging Through the Syslog (show logs) ............6-18 Searching Through the Syslog .................6-20 Filtering Messages Out ................6-21 Searching the End of the Syslog ...............6-22 Showing the Documentation for a Syslog Message.........6-24 Copying the Syslog File to an FTP Server............6-25 Copying the Syslog File through SCP ............6-26 Sending the Syslog File to an E-Mail Recipient........6-26 Adjusting Logging Levels................6-27...
  • Page 8 Pinging from a Particular Processor ..............7-3 Sending an Alternate Source IP................. 7-5 Pinging the OOB Management Network ........... 7-6 Using Traceroute....................... 7-8 Testing Throughput with TTCP................7-8 Cancelling a TTCP Transmission..............7-9 Testing a RON Tunnel ..................7-9 Tracing NSM Processes in the “fastpath” Log ............7-11 NSM-Log Components ...................
  • Page 9 Focusing on One Share ................8-11 Showing Share Statistics from One Filer ............8-12 Showing Statistics from One Filer Share..........8-13 Removing an Imported Share..................8-14 Removing the Empty Directory Tree ...............8-15 Extra Processing in a Multi-Protocol Volume..........8-15 Migrating NFS-Only Directories ..............8-16 Forcing Strict-Attribute Consistency..........8-16 Finding Reports About the Share Removal .............8-17 Showing the Drain-Share Report ..............8-19 Showing the Remove Report ..............8-20...
  • Page 10 Client View: Acopia-Generated Names..........8-66 Names That Resemble FGNs (FN) ............8-66 Unicode Characters in CIFS Names: Non-Mappable in NFS (NM)..8-67 Non-Mappable File Names ............... 8-68 Non-Mappable Directory Names ............8-68 Split Directories (SP) ................8-69 “Marked” Directories ................8-69 Preventative Striping.................
  • Page 11 Chapter 10 GUI Maintenance Removing the SSL Key...................10-1 Restarting the GUI ....................10-2 Chapter 11 Powering Down the ARX Saving Configuration Parameters................11-1 Checking the NVRAM Battery ................11-2 Turning Off the Power.....................11-3 Limited Down Time ....................11-3 Restoring Power ......................11-4 Verifying Successful Power-Up ...............11-4 Showing Overall Health................11-4 Showing Namespace Status ..............11-5 Showing Front-End Service Health ............11-8...
  • Page 12 2-xii CLI Maintenance Guide...

  • Page 13: Introduction

    Chapter 1 Introduction This manual contains instructions and best practices for troubleshooting and maintaining the Adaptive Resource Switch (ARX®) after it is fully connected to the network and running storage services. These instructions focus on the Command-Line Interface (CLI). Use this book after the ARX is installed, connected to the IP network, and serving clients.

  • Page 14: Back-End Storage And Servers

    Front-end Services The Adaptive Resource Switch acts as an in-band file proxy for the Network File System (NFS) and Microsoft's Common Internet File System (CIFS) protocols. Front-end services provide the file virtualization layer that masks the physical file storage from the user and application.

  • Page 15: Resilient Overlay Network (Ron)

    Introduction Audience for this Manual Resilient Overlay Network (RON) You can connect multiple ARXes with a Resilient Overlay Network (RON), which can reside on top of any IP network. This provides a network for distributing and accessing file storage. ARXes can replicate storage to other switches in the same RON, updating the replicas periodically as the writable master files change.

  • Page 16: Document Conventions

    Introduction Document Conventions The chapters in this manual contain maintenance instructions, such as backing up and restoring client files through the ARX, backing up configuration data with and similar commands, show running-config performing software upgrades, maintaining the metadata used by managed volumes, reading the syslog and working with other basic-maintenance facilities, using some network-troubleshooting tools (such as ping), taking down and repairing managed volumes, and...

  • Page 17: Cli Overview

    Introduction CLI Overview CLI Overview The Command-Line Interface (CLI) has its commands grouped into modes. Modes are structured as a tree with a single root, exec mode. This section summarizes the mode structure and explains some CLI conventions. Exec Mode When you log into the CLI, you begin in exec mode.

  • Page 18: Gbl Mode

    Introduction CLI Overview bstnA6k(cfg)# Config mode contains all modes and commands for changing the configuration of the local switch, such as network configuration. Gbl Mode To enter gbl mode, use the command: global bstnA6k# global bstnA6k(gbl)# Gbl mode controls all parameters that are shared in an HA pair, such as namespaces and global servers.

  • Page 19: The No Convention

    Introduction CLI Overview bstnA6k(gbl-ns[wwmed])# volume /local bstnA6k(gbl-ns-vol[wwmed~/local])# The tilde character (~) separates a parent object from its child: “wwmed~/local” shows that you are in the “/local” volume under the “wwmed” namespace. The no Convention Most config commands have the option to use the “no” keyword to negate the command.

  • Page 20: Getting Started

    For the initial login, refer to the instructions for booting and configuring the switch in the appropriate Hardware Installation Guide. For subsequent logins, use the following steps to log into the Acopia CLI: If you are on-site, you can connect a serial line to the serial console port. This port is labeled ‘Console;’...

  • Page 21: Sample Network

    Introduction Sample Network To enter gbl mode, use the command instead: global SWITCH> enable SWITCH# global SWITCH(gbl)# The command sequences in this manual all begin either in cfg mode or gbl mode. Sample Network The examples in this manual draw from a single, fictitious network. This section shows the topology of the network and the placement of the ARX.
  • Page 22 Introduction Sample Network The environment is assumed to be a three-tiered network in a large data center. The first tier is core routers that provide connectivity to a campus or WAN. The second tier has redundant distribution switches that distribute all data-center traffic between the access switches;...
  • Page 23 Introduction Sample Network the examples, the access switches are removed from the remaining illustrations in the book. The network filers all live on a class-C subnet at 192.168.25.x. These filers are called back-end filers, since they are the storage behind the front-end services of the ARX. The filers can be heterogeneous: NAS devices and file servers (possibly with additional DAS) need only support CIFS or NFS to be on the back end of the ARX.

  • Page 24: Contacting Customer Service

    Introduction Contacting Customer Service Contacting Customer Service You can use the following methods to contact Acopia Customer Service: support@acopia.com E-mail 1-866-4Acopia (1-866-422-6742) Telephone http://www.acopia.com/support/ Acopia TAC Online Acopia’s online customer knowledge base and support request system 1-12 CLI Maintenance Guide...

  • Page 25: Backing Up A Volume's Files

    Chapter 2 Backing Up a Volume’s Files You can back up volume files by working around the namespace and connecting directly to its back-end filers. Backups are read operations, so they cannot corrupt namespace metadata. This can follow the same workflow that was used before the introduction of the ARX.

  • Page 26: Mapping Client Requests To Back-End Paths

    Backing Up a Volume’s Files Mapping Client Requests to Back-End Paths Mapping Client Requests to Back-End Paths Many restore operations are invoked by client requests. The client requests a file or directory to be restored and the point-in-time for the desired file or directory. The client expresses the file share and path from the perspective of the front-end service that he or she uses.
  • Page 27 Backing Up a Volume’s Files Mapping Client Requests to Back-End Paths CIFS insur.medarch.org 192.168.25.14 insur.medarch.org 192.168.25.14 External Filer IP Address --------------------------------------------------------- --------------- das1 192.168.25.19 192.168.25.20 192.168.25.27 192.168.25.28 das2 192.168.25.22 das3 192.168.25.23 nas1 192.168.25.21 das7 192.168.25.24 das8 192.168.25.25 nas2 192.168.25.44 nas3 192.168.25.47 nasE1 192.168.25.51...

  • Page 28: Configuring A Source Server For The Restore

    Backing Up a Volume’s Files Configuring a Source Server for the Restore Configuring a Source Server for the Restore Once the back-end file or directory is identified, you need to identify a file server with its backed-up file(s). This is the source for the restore operation. In some installations, this may be a staging area for files recovered from archival media, such as backup tapes.

  • Page 29: Restoring Files

    Backing Up a Volume’s Files Restoring Files Restoring Files A restore operation copies the file(s) from the external filer to the managed volume, through a front-end service on the ARX. backup server servers restore clients command invokes the restore operation: restore data restore data namespace volume vol path dest-path filer src-filer {nfs export | cifs share}+ source-path src-path...
  • Page 30 Backing Up a Volume’s Files Restoring Files filer src-filer {nfs export | cifs share}+ source-path src-path points to the backup server and file(s): • src-filer (1-64 characters) is the external-filer name for the backup server, • nfs export (1-1024 characters) identifies the NFS export, and •...
  • Page 31 Backing Up a Volume’s Files Restoring Files **** Legend: **** OK = Object transferred without error. **** SK = Skipped object due to naming problems. **** FL = Encountered error during object transfer. **** SY = Error re-syncing directory attributes after data restore. **** DS = Error deleting source file or directory.

  • Page 32: Running The Restore From A Remote Host

    Backing Up a Volume’s Files Restoring Files DE NC] /stats/in_home:2005 FE NC] 249,856] /stats/in_home:2005/age:11-21yrs.csv FE NC] 162,816] /stats/in_home:2005/age:<10yrs.csv FE NC] 216,064] /stats/in_home:2005/age:>21yrs.csv 6,365] /stats/carrierCrossCheck.html FE NC] 305,152] /stats/PieChart.ppt **** Total Found Items: **** Total Transferred Items: **** Total Failures: **** Total Bytes Restored: 1,694,056 **** Total processed: **** Elapsed time:...
  • Page 33 Backing Up a Volume’s Files Restoring Files juser@mgmt17:~$ ssh admin@10.1.1.7 “restore data insur volume /claims path stats filer nasE1 nfs /root_vdm_4/backups cifs BACKUPS source-path /stats recurse” Command>restore data insur volume /claims path stats filer nasE1 nfs /root_vdm_4/backups cifs BACKUPS source-path /stats recurse Scheduling restore operation on switch bstnA6k, report name: restore.7._claims.rpt juser@mgmt17:~$ ssh admin@10.1.1.7 “show reports restore.7._claims.rpt”...

  • Page 34: Showing All Restore Operations

    Backing Up a Volume’s Files Showing all Restore Operations Entry Type Size Object ------------- ------------- ------------------------------------------------- /stats/PieChart.ppt /stats/piechart.ppt /stats/on_the_job:2003.cnv /stats/in_home:2005 /stats/on_the_job:2004.cnv FE NC] 313,344] /stats/piechart.ppt 2,202] /stats/cleanBU.csh 2,806] /stats/update.csh 4,790] /stats/index.html 1,694] /stats/makeCd.pl 714] /stats/acmeIns.txt FE NC] 6,365] /stats/on_the_job:2003.cnv FE NC] 421,888] /stats/on_the_job:2004.cnv DE NC]...
  • Page 35 Backing Up a Volume’s Files Showing all Restore Operations bstnA6k(gbl)# show restore data Namespace: wwmed Volume: /acct Path: / Options: recurse Source Filer: das1 [192.168.25.19] NFS Source: /exports/backups/acct Status: Success Report Name: restore.6._acct.rpt (bstnA6k) Items Found: Items Transferred: Failures: Total Bytes Restored: 11,163,668 Completed at: Thu Feb 1 13:03:59 2007...

  • Page 36: Focusing On A Single Namespace, Volume, Or Path

    Backing Up a Volume’s Files Showing all Restore Operations Focusing on a Single Namespace, Volume, or Path You can add some options to show a smaller set of restore operations: show restore data [namespace [volume vol-path [path path]]] where namespace (1-30 characters) selects a namespace, vol-path (1-1024 characters) narrows the scope to a specific volume, and.

  • Page 37: Clearing Restore Operations From The Output

    Backing Up a Volume’s Files Showing all Restore Operations Clearing Restore Operations from the Output command displays a running history of all restore operations. show restore data The history goes back indefinitely, so the command can display a very large number of records over time.

  • Page 38: Canceling A Restore Operation

    Backing Up a Volume’s Files Canceling a Restore Operation Canceling a Restore Operation To cancel an in-progress restore operation, go to priv-exec mode and use the cancel command: restore data cancel restore data namespace volume vol-path path path where namespace (1-30 characters) identifies the namespace, vol-path (1-1024 characters) is the volume, and path (1-1024 characters) is the specific virtual path that is being restored.

  • Page 39: Backing Up The Running Configuration

    Chapter 3 Backing Up the Running Configuration The switch configuration that you edit with the CLI is called the running configuration, or running config. You can save the running config for the next reboot, disaster recovery, or for exporting the configuration from one switch to another.The running config is divided into two major components: the local-running config for the current switch, and global config for parameters that are shared by both switches in a redundant pair.

  • Page 40: Saving The Local Running Config

    Backing Up the Running Configuration Saving the Local Running Config From cfg mode, use to set the FTP username: ip ftp-user ip ftp-user username where username is 1-32 characters. The CLI then prompts twice for the password. For example, the following command sequence sets up a default FTP user named “juser:”...

  • Page 41: Saving The Config Off To An Ftp Server

    Backing Up the Running Configuration Saving the Local Running Config scripts running Sep 19 05:03 5.7k Saving the Config Off to an FTP Server To save the running config off to a remote FTP server, use a URL in place of the destination filename.

  • Page 42: Saving The Config Off To An Scp Server

    Backing Up the Running Configuration Saving the Local Running Config Saving the Config Off to an SCP Server For secure sites, you can upload with the Secure Copy (SCP) protocol. The URL has a different syntax for SCP transfers: copy running-config scp://username@server:file [accept-host-key] where username@ is a valid username at the remote host, server identifies the SCP server with an IP address or FQDN (for example,...

  • Page 43: Showing The Local Config

    For example, the following command sequence sets up SMTP, exits from cfg mode to priv-exec mode, then mails the running-config file to “juser@wwmed.com:” bstnA6k(cfg)# smtp bstnA6k(cfg-smtp)# mail-server email1.wwmed.com bstnA6k(cfg-smtp)# from admin@acopia.wwmed.com bstnA6k(cfg-smtp)# exit bstnA6k(cfg)# exit bstnA6k# copy running-config smtp://juser@wwmed.com/oct24running bstnA6k# ...

  • Page 44: Saving The Global Config

    Backing Up the Running Configuration Saving the Global Config config logging level all info exit ;================================= vlan ================================== config vlan 25 members 3/1 to 3/1 members 3/2 to 3/2 exit exit ;============================ config-if-vlan ============================= config interface vlan 25 ip address 192.168.25.5 255.255.255.0 Saving the Global Config The next step in saving the running configuration is to save the global-config parameters.

  • Page 45: Saving The Config Off To An Ftp Server

    Backing Up the Running Configuration Saving the Global Config For example, the following command sequence exits to priv-exec mode, copies the global running configuration, then shows the new script file: bstnA6k(cfg)# exit bstnA6k# copy global-config scripts global bstnA6k# show scripts scripts global Sep 19 05:03...

  • Page 46: Saving The Config Off To An Scp Server

    Backing Up the Running Configuration Saving the Global Config Saving the Config Off to an SCP Server As with the running-config, you can also use the Secure Copy (SCP) protocol to upload the global config: copy global-config scp://username@server:file [accept-host-key] where username@ is a valid username at the remote host, server identifies the SCP server with an IP address or FQDN (for example, “172.16.100.12”...

  • Page 47: Showing The Global Config

    For example, the following command sequence sets up SMTP (including a destination E-mail address, “juser@wwmed.com”), exits from cfg mode to priv-exec mode, then mails the global-config file: bstnA6k(cfg)# smtp bstnA6k(cfg-smtp)# mail-server email1.wwmed.com bstnA6k(cfg-smtp)# from admin@acopia.wwmed.com bstnA6k(cfg-smtp)# to juser@wwmed.com bstnA6k(cfg-smtp)# exit bstnA6k(cfg)# exit bstnA6k# copy global-config smtp://oct24gbl bstnA6k# ...
  • Page 48 Backing Up the Running Configuration Saving the Global Config For example: bstnA6k> show global-config ; ARX-6000 ; Version 2.05.001.10121 (Apr 3 2007 17:40:25) [nbuilds] ; Database version: 205001.1 ; Generated global-config Wed Apr 4 04:19:41 2007 ;================================ global ================================= global nfs tcp timeout 30 ;================================= user ================================== user adm1 encrypted-password lH3VdGIIdBrlTvofTsMNqU3T7wIXEP5rE+BwY5G7a5Y=...

  • Page 49: Focusing On Specific Configuration Sections

    Backing Up the Running Configuration Saving the Global Config Focusing On Specific Configuration Sections You can show an individual group of commands from the output: show global-config show global-config {filer | namespace | schedule | security | global-server | nfs | cifs} where •...
  • Page 50 Backing Up the Running Configuration Saving the Global Config exit ;============================= radius-server ============================= radius-server 192.168.25.201 exit radius-server 192.168.25.207 auth-port 5555 retries 4 timeout 10 exit ;============================ nfs-access-list ============================ nfs-access-list eastcoast anonymous-gid 100 anonymous-uid 100 description “allowable subnets in MA, NY, & DC” nis domain wwmed.com permit 172.16.100.0 255.255.255.0 read-write root squash permit 172.16.204.0 255.255.255.0 read-only root allow...
  • Page 51 Backing Up the Running Configuration Saving the Global Config user lab encrypted-password Ygh0GuVO+h9Oww2pTdPvAhcQ/mububYQbAMwPEAdszBxYE8o exit ;=========================== ntlm-auth-server ============================ ntlm-auth-server dc1 encrypted-password Ygh0GuVO+h9Oww2pTdPvAhcQ/mtEaV7x5oWzzw== ip address 192.168.25.102 windows-domain MEDARCH.ORG exit ntlm-auth-server dc1-oldStyle encrypted-password Ygh0GuVO+h9Oww2pTdPvAhcQ/mtEaV7x5oWzzw== ip address 192.168.25.102 windows-domain NTNET exit ;============================== proxy-user =============================== proxy-user acoProxy1 user jqprivate encrypted-password qJQi/mIIdBrlTvofTsMNqU3T7wIXEP5riJiSbwjFd+1eLSf+Y39YtQ==...

  • Page 52: Focusing On Named Configurations

    Backing Up the Running Configuration Saving the Global Config Focusing On Named Configurations You can show an individual namespace, volume, or front-end service by specifying the name at the end of the command: show global-config namespace name [volume] where name (1-30 characters) identifies the namespace, show global-config {nfs | cifs} name where name (1-255 characters) is the fully-qualified domain name (FQDN) for the front-end service.
  • Page 53 Backing Up the Running Configuration Saving the Global Config no compressed-files named-streams persistent-acls no sparse-files unicode-on-disk share equip import skip-managed-check filer fs2 cifs lab_equipment enable exit share leased filer nas2 cifs for_lease enable exit vpu 2 domain 1 enable exit volume /rcrds filer-subshares replicate modify...

  • Page 54: Saving Both Configs

    Backing Up the Running Configuration Saving Both Configs Saving Both Configs The startup config is a combination of the running config and the global config. You can save the startup config as a single file. From priv-exec mode, use the copy command to save the startup config to an executable script file.

  • Page 55: Saving The Config Off To An Ftp Server

    Backing Up the Running Configuration Saving Both Configs Saving the Config Off to an FTP Server Use a URL in the command to save the startup config to an FTP copy startup-config site: copy startup-config ftp://[username:password@]ftp-site/file where username:password@ (optional) is an FTP username and password (the default is the username/password set by the command), ip ftp-user...

  • Page 56: Sending The Config To An E-Mail Recipient

    For example, the following command sequence sets up SMTP (including a destination E-mail address, “juser@wwmed.com”), exits from cfg mode to priv-exec mode, then mails the startup-config file: bstnA6k(cfg)# smtp bstnA6k(cfg-smtp)# mail-server email1.wwmed.com bstnA6k(cfg-smtp)# from admin@acopia.wwmed.com bstnA6k(cfg-smtp)# to juser@wwmed.com bstnA6k(cfg-smtp)# exit bstnA6k(cfg)# exit bstnA6k# copy startup-config smtp://feb6startup bstnA6k# ...

  • Page 57: Restoring The Configuration

    Backing Up the Running Configuration Restoring the Configuration Restoring the Configuration The first step to restoring the running config is to place the running-config script(s) onto the chassis. If the scripts are already on the switch (for example, if you saved the config(s) to the current chassis), you can skip this section.

  • Page 58: Restoring The Local And Global Configs

    Backing Up the Running Configuration Restoring the Configuration bstnA6k# delete startup-config Delete file 'startup-config' in directory 'configs'? [yes/no] bstnA6k# reload Reload the entire chassis? [yes/no] yes Broadcast message (Fri Feb 6 15:06:47 2004): The system is going down for reboot NOW! Wait for the machine to reboot, then log back in through the serial CONSOLE port.

  • Page 59: Restoring Configs To A Redundant Pair

    Backing Up the Running Configuration Restoring the Configuration The CLI commands run on the command line until the configuration is finished. For example, the following command sequence enters priv-exec mode, shows the saved scripts, and runs the “start_conf” script (which contains both the running and global configs): SWITCH>...
  • Page 60 Backing Up the Running Configuration Restoring the Configuration For instructions on joining a redundant pair, refer to “Enabling Redundancy” on page 6-16 of the CLI Network-Management Guide. For example, the following command sequence updates the running-config on both switches, then updates one switch with the global-config: Peer A SWITCH# run scripts running SWITCH# config...

  • Page 61: Restoring To One Peer

    Backing Up the Running Configuration Restoring the Configuration prtlndA1k# run scripts global prtlndA1k# global prtlndA1k(gbl)# exit prtlndA1k# ... Restoring to One Peer If you are only restoring the config on one switch, run its running-config script to set up networking and rejoin the switch with its waiting peer. The switch downloads the global config when it joins the redundant pair.
  • Page 62 Backing Up the Running Configuration Restoring the Configuration 3-24 CLI Maintenance Guide...

  • Page 63: Upgrading Software

    Chapter 4 Upgrading Software Acopia software is distributed in release files, typically named with a .rel extension (for example, “initial.rel” or “acopia-0.5.0_dev.rel”). To upgrade software on the ARX, you must clear space for a new release file (if necessary), copy a new release file to the switch, arm the switch with the release file, and reboot all modules in the switch.

  • Page 64: Clearing Space For A New Release File

    A is the armed release, the one that will run on the next reboot. By default, this is the same release as the running (R) release. • B is the backup release. Acopia personnel can revert the switch back to this release if necessary. For example, the command below shows three releases on the current switch. The test3.rel file is currently running, and armed to run again on the next reboot.

  • Page 65: Showing The Software Versions

    This shows the specific versions of each release and the module configuration for the chassis. For example: bstnA6k(gbl-ns[wwmed])# show version Copyright (c) 2002-2006 by Acopia Networks Inc. All rights reserved. Running Release test3.rel : Version 2.01.004.08731 (Mar 10 2006 18:33:05) [nbuilds] Armed Release test3.rel :...

  • Page 66: Deleting A Release File

    Upgrading Software Clearing Space for a New Release File Deleting a Release File You cannot delete the running, armed, or backup release. To delete any other release file, go to priv-exec mode and use the command: delete releases delete releases file where file (1-255 characters) identifies the release file.

  • Page 67: Copying A Release File To The Switch

    % INFO: Copying 328 megabytes from the specified source . . . % INFO: Transferred 190886 of 335963 kbytes; still copying . . .

  • Page 68: Downloading From An Scp Server

    For example, the following command exits from gbl mode to priv-exec mode, then downloads a release file through SCP: bstnA6k(gbl)# exit bstnA6k# copy scp://juser@rh1.wwmed.com:/var/rels/acopia-ac1-dev.rel releases test.rel Password: jpasswd % INFO: Copying 328 megabytes from the specified source . . .

  • Page 69: Showing The Version Of A Release File

    Upgrading Software Copying a Release File to the Switch bstnA6k# ... Showing the Version of a Release File Use the command on a release file to view the release version and show releases build date for the file: show releases file where file (1-255 characters) is the release-file name.

  • Page 70: Arming The Switch With The Release File

    Upgrading Software Arming the Switch with the Release File Arming the Switch with the Release File The next step in upgrading software is to arm the switch with the new release file. From priv-exec mode, use the command to arm the ARX: boot system boot system release-file where release-file (1-255 characters) identifies the desired release file.

  • Page 71: Verifying The Installation

    For example: version User Access Authentication Username: admin Password: acopia bstnA6k> show version Copyright (c) 2002-2006 by Acopia Networks Inc. All rights reserved. Running Release test3.rel : Version 2.04.000.09308 (Jun 15 2006 18:09:59) [nbuilds] Armed Release test3.rel : Version 2.04.000.09308 (Jun 15 2006 18:09:59) [nbuilds]...

  • Page 72: Upgrading A Redundant Pair

    Upgrading Software Upgrading a Redundant Pair Slot Admin ModuleType ModuleState FW Upgrade ---- ------- ------------ ---------------- ---------- Enabled Online Disabled Enabled Empty Disabled Enabled Online Disabled Enabled Empty Disabled Enabled Online Disabled Enabled Empty Disabled Resource State Forwarding -------- ------------------------------- ---------- Switch Disabled...
  • Page 73 Upgrading Software Upgrading a Redundant Pair verify the connection to the quorum disk (see “Showing the Quorum Disk” on page 6-19 of the CLI Network-Management Guide). Run this command at the Active switch, not the switch where you will do the upgrade first. Any “Up” status, even if the switch is not receiving heartbeats, is acceptable.

  • Page 74: Checking The Health Of The Backup Switch

    Upgrading Software Upgrading a Redundant Pair 01:00 - 02:00 00:00 - 01:00 23:00 - 24:00 22:00 - 23:00 21:00 - 22:00 20:00 - 21:00 19:00 - 20:00 18:00 - 19:00 17:00 - 18:00 16:00 - 17:00 15:00 - 16:00 14:00 - 15:00 13:00 - 14:00 12:00 - 13:00 11:00 - 12:00...

  • Page 75: Backing Up The Running-Config (Backup Switch Only)

    Upgrading Software Upgrading a Redundant Pair If the status is not “Up” for any of the nodes, contact Acopia Support before proceeding. Otherwise, use the command to check for any alarm conditions: show health prtlndA1kB# show health System Health Information...

  • Page 76: Sanity Check

    • to verify there are no active alarms, and show health • to ensure that redundancy is up and running. show redundancy If any issues appear, contact Acopia Support before proceeding. 4-14 CLI Maintenance Guide...

  • Page 77: Checking The Health Of The Active Switch

    If the status is not “Up” for any of the nodes, or if any active alarms appear, contact Acopia Support before proceeding. Failing Over to the Upgraded Switch The next step is to fail over and put the new software into active service. Reload the other switch, the switch currently running services on the old software.
  • Page 78 Upgrading Software Upgrading a Redundant Pair WARNING: Arming this release will cause your configuration to be reset to factory default because it is a lower version than the running release. Proceed? [yes/no] yes % INFO: The boot system command may take up to 5 minutes to complete. prtlndA1kB# reload Reload the entire chassis? [yes/no] yes Broadcast message (Fri Jun 3 13:31:35 2006):...

  • Page 79: Restoring The Old Configuration

    Upgrading Software Upgrading a Redundant Pair system initialization. If the software on this system has NOT recently been upgraded or downgraded, we advise you to restore the running-config and/or global-config from a recent backup. Otherwise, please use individual CLI commands to upgrade or downgrade in smaller steps.
  • Page 80 Upgrading Software Upgrading a Redundant Pair prtlndA1kB(cfg)# ... prtlndA1kB(cfg)# exit prtlndA1kB# ... 4-18 CLI Maintenance Guide...

  • Page 81: Metadata Utilities: Nsck And Sync

    Chapter 5 Metadata Utilities: nsck and sync The Namespace-Check (nsck) and synchronization (sync) utilities manipulate the metadata in managed volumes. Metadata is high-level information such as physical-file locations on back-end filers, modification-time stamps, and file sizes. The nsck utility can show a volume’s metadata to reveal which back-end shares hold its files and directories.

  • Page 82: Showing The Progress Of Nsck And Sync Jobs

    Metadata Utilities: nsck and sync Showing the Progress of nsck and sync Jobs Showing the Progress of nsck and sync Jobs Before you begin running nsck and sync jobs, it is helpful to know how to monitor their progress. You can monitor the progress of any nsck or sync job with the show command: nsck...

  • Page 83: Showing The Nsck/Sync Jobs For One Namespace

    Metadata Utilities: nsck and sync Showing the Progress of nsck and sync Jobs Showing the nsck/sync Jobs for One Namespace To view only the nsck and/or sync jobs for one namespace, add the clause namespace to the end of the command: show nsck show nsck namespace namespace...

  • Page 84: Showing All Nsck/Sync Jobs

    Metadata Utilities: nsck and sync Showing the Progress of nsck and sync Jobs For example, the following command shows the nsck job 1: bstnA6k(gbl)# show nsck 1 Op Type: report Op Id: Report Name: inconsistencies.1.rpt Switch: bstnA6k Namespace: wwmed Path: /acct Status: Complete...

  • Page 85: Showing All Nsck/Sync Reports

    Metadata Utilities: nsck and sync Showing the Progress of nsck and sync Jobs Showing all nsck/sync Reports command is focused on job status; if all nsck and sync jobs are cleared show nsck from the database (as described below), no jobs appear in .

  • Page 86: Showing The Status Of One Report

    Metadata Utilities: nsck and sync Showing the Progress of nsck and sync Jobs inconsistencies.3.rpt 8 14:26 1.2k DONE: 10 in 00:00:00 insur_meta.rpt 8 14:30 240k DONE: 1621 in 00:00:00 metadata_only.12.rpt 8 14:28 4.8k DONE: 30 in 00:00:00 metadata_only.13.rpt 8 14:28 3.4k DONE: 19 in 00:00:00 metadata_only.17.rpt...

  • Page 87: Showing Metadata

    Metadata Utilities: nsck and sync Showing Metadata Showing Metadata You can use the command to show the physical locations of nsck report metadata-only all files and directories in a namespace’s managed volumes. A file’s physical location is its directory path including the IP address of the filer where it resides; for example, 192.168.25.21:/usr/local/bin.
  • Page 88 Metadata Utilities: nsck and sync Showing Metadata The start time, namespace, volume, and path for the report. A table of namespace shares that were examined, along with the IP of the back-end filer and the share name at the filer. A legend of keys for the next table.
  • Page 89 Metadata Utilities: nsck and sync Showing Metadata **** SP = A persistent case collision split is registered in the metadata. **** SN = A persistent split restricts CIFS access, but no collision exists. Type Share Path ------------------- -------------------- ------------------------------------- [bills2 /planner [budget /.lost+found-1...

  • Page 90: Focusing On One Share

    Metadata Utilities: nsck and sync Showing Metadata Focusing on One Share You can generate a report that focuses on one managed-volume share. Use the optional clause to report the metadata for a single share: share nsck namespace report metadata-only [path] share share-name [norecurse] where namespace, report metadata-only, path, and norecurse are all explained...

  • Page 91: Sending The Output To A Different File

    Metadata Utilities: nsck and sync Warning Signs for Metadata Inconsistencies Sending the Output to a Different File Use the optional clause to send the nsck results to a file other than the outputfile default, “metadata_only.n.rpt:” nsck namespace report metadata-only [path] [share share-name] [norecurse] outputfile file-name where name, report metadata-only, path, share share-name, and norecurse are...

  • Page 92: Finding Metadata Inconsistencies

    Without the ARX in the data path, the switch has no knowledge of the changes and cannot update its metadata. servers invalid client Acopia valid clients 5-12 CLI Maintenance Guide...
  • Page 93 Metadata Utilities: nsck and sync Finding Metadata Inconsistencies A local process on the filer, such as anti-virus software, can cause an inconsistency by removing or renaming a file. You can use the to determine whether to run or a nsck report inconsistencies sync files full on a namespace, or to confirm that there are no inconsistencies at all.
  • Page 94 Metadata Utilities: nsck and sync Finding Metadata Inconsistencies The start time, namespace, volume, and path for the report. A table of shares that were examined, along with the IP of the back-end filer and the share name at the filer. A legend of keys for various types of metadata inconsistency.
  • Page 95 Metadata Utilities: nsck and sync Finding Metadata Inconsistencies **** MF = The file is currently being migrated. **** NL = Unable to lock parent directory during report. **** FE = Error contacting filer during report. **** FO = Filer Offline: The filer is offline or disabled. **** F8 = A file name matches a CIFS alternate “8.3”...

  • Page 96: Focusing On Multi-Protocol Issues

    Metadata Utilities: nsck and sync Finding Metadata Inconsistencies Focusing on Multi-Protocol Issues A volume in a multi-protocol (CIFS and NFS) namespace may have files whose names are inconsistent between CIFS and NFS. Some characters are legal in NFS filenames but unsupported in CIFS names, just as CIFS has some naming conventions that NFS cannot always follow.
  • Page 97 Metadata Utilities: nsck and sync Finding Metadata Inconsistencies **** LD = Directory exists in the metadata, but is missing from the physical filer. **** FF = File exists on the physical filer, but is missing from the metadata. **** FD = Directory exists on the physical filer, but is missing from the metadata. **** IF = Filehandles in the metadata do not match the filehandles on the physical filer.
  • Page 98 Metadata Utilities: nsck and sync Finding Metadata Inconsistencies NF IC [shr1-old /images/:PFCD700 NI NM [shr1-old /images/file012b/ (Characters: U+012b) NF CC [shr1-old /stats/piechart.ppt NF CC [shr1-old /stats/PieChart.ppt [shr1-next /Y2KCLA~1/C Angelis 1-12-00.doc [shr1-next /Y2KCLA~1/M soprano 9-30-00.doc [shr1-next /Y2KCLA~1/r aprile II 6-5-00.doc [shr1-next /Y2KCLA~1/r aprile I 9-4-00.doc [shr1-next /Y2KCLA~1/a soprano rec.doc...

  • Page 99: Synchronizing Metadata With Actual Files

    Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files Synchronizing Metadata with Actual Files The above example shows a file that was recorded in volume metadata but is missing from its back-end filer. You can use the sync utility to re-synchronize the metadata with the actual contents of the filers.
  • Page 100 Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files As with nsck jobs, every sync operation produces a report as it runs. The CLI shows the report name after you invoke the command. Use for a full list of sync show reports reports, and use , or...
  • Page 101 Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files **** CN = CIFS case blind name collision, file renamed. **** CZ = CIFS case blind name collision, no rename, use rename-files. **** RV = Reserved name encountered on filer, not imported. **** FD = Found Directory, Directory exists on filer, but not in the metadata.

  • Page 102: Synchronizing With Actual Directories

    Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files Synchronizing with Actual Directories Some installations require new directories that cannot be configured through the client interfaces. These directories have features that can only be added through an administrative interface on the back-end filer itself, such as disk quotas. If such a directory is created behind a managed volume, you can use the sync utility to add it to the metadata.
  • Page 103 Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files bstnA6k# show reports sync.5._lab_equipment.rpt **** Sync Report: Started at Thu Sep 14 03:19:42 2006 **** **** Namespace: medarcv **** Volume: /lab_equipment **** Path: Share Physical Filer -------------------- ------------------------------------------------- [equip 192.168.25.27:lab_equipment [leased 192.168.25.44:for_lease **** Legend:...

  • Page 104: Synchronizing Metadata In A Single Share

    Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files =============================================================================== Total Found Items: Total Lost Items: Total Invalid Filehandles: File Name Collisions: File Collision Renames: Total Migrations Aborted: Total Items Synchronized: Directories completely processed: Total Directories: CIFS Case Blind Collisions: Non-Empty Directories: **** Total processed: **** Elapsed time:...

  • Page 105: Showing The Progress Of All Sync Operations

    Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files For example, this command sequence syncs files in a single share, “wwmed~/acct~bills.” It calls for a recursive sync, and it allows renaming of newly-discovered files that introduce collisions: bstnA6k(gbl)# end bstnA6k# sync files wwmed volume /acct path /payable share bills recurse rename-files Scheduling sync files operation on switch bstnA6k, report name: sync.1._acct.rpt bstnA6k# ...

  • Page 106: Focusing On A Single Namespace, Volume, Or Path

    Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files Options: recurse rename-files Status: Success Report Name: sync.2._rcrds.rpt (bstnA6k) Lost Items: Found Items: Synchronized Items: 0 Processed Items: Path: / Options: recurse rename-files Status: Success Report Name: sync.3._rcrds.rpt (bstnA6k) Lost Items: Found Items: Synchronized Items: 1 Processed Items:...
  • Page 107 Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files For example, this command shows all the sync-file operations performed on the medarcv~/rcrds volume: bstnA6k(gbl)# show sync files medarcv volume /rcrds Namespace: medarcv Volume: /rcrds Path: /sprains Options: recurse rename-files Status: Success Report Name:...

  • Page 108: Clearing Sync Operations From The Output

    Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files Clearing Sync Operations from the Output command displays a running history of all sync operations. The show sync history goes back indefinitely, so the command can display a very large number of records over time.

  • Page 109: Canceling A Sync Operation

    Metadata Utilities: nsck and sync Synchronizing Metadata with Actual Files Processed Items: bstnA6k(gbl)# end bstnA6k# clear sync files Clear sync records? [yes/no] yes bstnA6k# show sync files bstnA6k# ... Canceling a Sync Operation To cancel an in-progress sync operation, go to priv-exec mode and use the cancel command: sync...

  • Page 110: Adding And Synchronizing Filer Subshares (Cifs)

    Metadata Utilities: nsck and sync Adding and Synchronizing Filer Subshares (CIFS) Adding and Synchronizing Filer Subshares (CIFS) This section only pertains to volumes that support CIFS. Skip to the next section for NFS-only volumes. A filer subshare is a shared directory that is under another shared directory. A CIFS service and its managed volume can pass clients from a front-end subshare through to the corresponding subshare on a back-end filer.
  • Page 111 Metadata Utilities: nsck and sync Adding and Synchronizing Filer Subshares (CIFS) After you add new subshare (and ACL) at a filer, use the command to sync shares find them and copy them to all other filers behind the volume. This copies the share definition, ACL, and any underlying subdirectories: sync shares namespace volume vol-path share share-name where:...
  • Page 112 Metadata Utilities: nsck and sync Adding and Synchronizing Filer Subshares (CIFS) bstnA6k(gbl)# end bstnA6k# sync shares medarcv volume /rcrds share rx % INFO: Sync operation completed; see report 'syncShares_200612140356.rpt'. bstnA6k# show reports syncShares_200612140356.rpt **** Sync Filer Subshares Report: Started at Thu Dec 14 03:56:51 2006 **** **** Software Version: 2.05.000.09890 (Dec 11 2006 17:41:02) [nbuilds] **** Hardware Platform: ARX-6000 Source...
  • Page 113 Metadata Utilities: nsck and sync Adding and Synchronizing Filer Subshares (CIFS) % WARNING: Not all nested back-end shares were successfully exported due to collisions with existing exports. See report 'cifsExportSubshares_200612140400.rpt' for details. bstnA6k# ... The report shows that the warning is not serious. It indicates that the operation found three subshares on the filer, and two of them were already exported: bstnA6k# show reports cifsExportSubshares_200612140400.rpt **** Cifs Export Subshares Report: Started at Thu Dec 14 04:00:32 2006 ****...

  • Page 114: Rebuilding A Namespace

    Metadata Utilities: nsck and sync Rebuilding a Namespace Rebuilding a Namespace The nsck rebuild utility completely rebuilds all managed volumes in a namespace: it re-imports the back-end shares and rebuilds its metadata databases. This command disables the namespace during the rebuild process, and it forces all NFS clients to unmount and then re-mount their managed volumes;...

  • Page 115: Rebuilding A Volume

    Metadata Utilities: nsck and sync Rebuilding a Namespace bstnA6k# ... Rebuilding a Volume You can narrow the focus of an to a single volume: nsck rebuild nsck namespace rebuild volume volname where: name (1-30 characters) is the name of the namespace to rebuild. Use the command to see a list of configured namespaces.

  • Page 116: Forcing The Rebuild

    Metadata Utilities: nsck and sync Rebuilding a Namespace Forcing the Rebuild It is possible for an nsck-rebuild job to freeze in an unfinished state: for example, the job freezes if one of the back-end filers goes down during the re-import. In this situation, you should resolve the problem and then restart the rebuild.
  • Page 117 Metadata Utilities: nsck and sync Rebuilding a Namespace For example, this command sequence moves all masters in “archives~/etc” to a share named “nas8.” It deletes the file-placement rule and the fileset once the initial migration is complete: bstnA6k(gbl)# policy-filename-fileset fulltree bstnA6k(gbl-ns-vol-fs-name[fulltree])# path match / bstnA6k(gbl-ns-vol-fs-name[fulltree])# recurse bstnA6k(gbl-ns-vol-fs-name[fulltree])# exit...
  • Page 118 Metadata Utilities: nsck and sync Rebuilding a Namespace Total Directories Promoted: Total Failed Migrations: Total Failed Directory Promotes: Total Retried Migrations: Total Canceled Migrations: Total Hard Links Skipped: Total Files Placed Inline: Total File Renames Processed Inline: Total Directories Placed Inline: Total Directory Renames Processed Inline: Number of Inline Overflow Errors: Number of Scans Performed:...

  • Page 119: De-Staging A Namespace's Managed Volumes

    Metadata Utilities: nsck and sync De-Staging a Namespace’s Managed Volumes De-Staging a Namespace’s Managed Volumes You may want to perform filer recoveries directly on the filer. To directly access the shares behind a namespace’s managed volumes, you first release (or de-stage) the shares from the volumes.

  • Page 120: De-Staging A Volume

    Metadata Utilities: nsck and sync De-Staging a Namespace’s Managed Volumes You can run one nsck job at a time on a given namespace. Use to monitor show nsck the progress of nsck jobs; see “Showing the Progress of nsck and sync Jobs” on page 5-2.

  • Page 121: Forcing The De-Stage

    Metadata Utilities: nsck and sync De-Staging a Namespace’s Managed Volumes The CLI prompts for confirmation before releasing the volume: enter yes to continue. Enter no to cancel the destage operation. For a short interval (roughly 10 seconds) all front-end NFS or CIFS services that host the volume are inaccessible.

  • Page 122: Re-Enabling The Shares

    Metadata Utilities: nsck and sync De-Staging a Namespace’s Managed Volumes bstnA6k(gbl)# end bstnA6k# nsck wwmed destage volume /it force This operation will remove entries for all shares in the volume from the namespace metadata. To reimport a destaged share, enable the share in namespace-volume-share mode. Destage all shares from volume /it in namespace wwmed? [yes/no] yes bstnA6k# ...

  • Page 123: Migrating Metadata To A New Back-End Share

    Metadata Utilities: nsck and sync Migrating Metadata to a New Back-End Share Migrating Metadata to a New Back-End Share Managed volumes require fast and extremely-reliable back-end shares to store their metadata. A slow metadata share can affect client service as well as import speed. To migrate a volume’s metadata from a slow back-end share to one on a faster filer, use command: nsck migrate-metadata...
  • Page 124 Metadata Utilities: nsck and sync Migrating Metadata to a New Back-End Share The CLI prompts for confirmation before it starts the migration; enter yes to proceed. The nsck utility copies all of the metadata to the target share, verifies its integrity at the target share, then switches the managed volume over to the new metadata share.

  • Page 125: Canceling A Metadata Migration

    Metadata Utilities: nsck and sync Clearing All nsck Jobs bstnA6k# ... Canceling a Metadata Migration You cannot cancel a migration after it has restarted the volume. The restart occurs after the metadata is successfully copied to the new share. To cancel a metadata migration in an earlier phase, go to priv-exec mode and use the cancel command:...

  • Page 126: Clearing One Nsck Job

    Metadata Utilities: nsck and sync Clearing All nsck Jobs For example: bstnA6k(gbl)# end bstnA6k# clear nsck Clear all nsck records? [yes/no] yes bstnA6k# show nsck Op Id Op Type Namespace:Path Status ------ ------------ ---------------------------------------- ------------------ bstnA6k# ... Clearing One nsck Job Use the nsck-job ID with the command to clear one nsck job: clear nsck...

  • Page 127: Truncating A Report

    Metadata Utilities: nsck and sync Clearing All nsck Jobs Truncating a Report To conserve CPU cycles and/or internal-disk space, you may want to stop a report before it is finished. A oversized, CPU-intensive report could possibly have an effect on namespace performance. You can stop the report without stopping the nsck job. From priv-exec mode, use the command to stop all report processing truncate-report...
  • Page 128 Metadata Utilities: nsck and sync Clearing All nsck Jobs 5-48 CLI Maintenance Guide...

  • Page 129: Troubleshooting Tools

    You can show the current tasks running on the system. • You can collect all diagnostic information from a troubled switch and send it to a remote site. This is for sending information to Acopia for thorough diagnosis. • Using SSH, you can run commands from a remote host.

  • Page 130: Accessing The Syslog

    Troubleshooting Tools Accessing the Syslog Refer to the SNMP Reference for detailed information about any trap, including correction procedures. For example, this shows two alarm conditions on the ARX named “bstnA6k:” bstnA6k(cfg)# show health System Health Information Date Event Description --------------------------------------------------------------------------------------- Thu Jan 25 03:11:30 2007 (131) - diskFail Disk in bay 2 failed...
  • Page 131 Troubleshooting Tools Accessing the Syslog logs catalina.out Nov 21 03:27 dfpd.dump.0 Nov 20 14:31 dmesg Nov 21 03:23 error.log Nov 21 03:59 897k fastpath Nov 21 03:51 firebird.log Nov 21 03:23 gziplog Nov 20 14:32 kernel.log Nov 21 03:51 583k megaserv.log Nov 21 03:54 9.5k...

  • Page 132: Tailing The Syslog

    Troubleshooting Tools Accessing the Syslog traplog.5 Nov 20 15:30 traplog.6 Nov 20 15:01 traplog.7 Nov 20 14:32 traplog.8 Nov 20 14:12 traplog.9 Nov 20 13:57 txnmond.dump.0 Nov 20 14:28 Tailing the Syslog You can use the command from any mode to view syslog messages as they are tail added to the log: tail logs filename follow...

  • Page 133: Showing The End Of The Syslog

    Troubleshooting Tools Accessing the Syslog 2004-06-18T18:37:13.257-0400:bstnA6k:1-1-SCM-0:LOG-0-6-FILTER:: sshd[9204]: WARNING: /usr/local/etc/moduli does not exist, using old modulus 2004-06-18T18:37:13.371-0400:bstnA6k:1-1-SCM-0:LOG-0-6-FILTER:: sshd[9204]: Could not reverse map address 172.16.22.183. 2004-06-18T18:37:14.028-0400:bstnA6k:1-1-SCM-0:LOG-0-6-FILTER:: sshd[9204]: Accepted keyboard-interactive for admin from 172.16.22.183 port 60054 ssh2 2004-06-18T18:37:14.032-0400:bstnA6k:1-1-SCM-0:LOG-0-6-FILTER:: sshd[9204]: lastlog_get_entry: Error reading from /var/log/lastlog: Bad file descriptor Showing the End of the Syslog You can show the last few lines in the syslog file, without following any new syslog entries, by omitting the...

  • Page 134: Log Components

    Troubleshooting Tools Accessing the Syslog Log Components Every log message originates from a log component (such as SCM_CLI in the sample above). A log component is a source of syslog messages, typically an internal process or group of processes. The table below is an alphabetical list of all log components, with a brief description and an indication of the board(s) where the software runs.
  • Page 135 Troubleshooting Tools Accessing the Syslog Log Component Description CIFS_SHIM_LIB Interface to metadata storage on CIFS filers Command Line Interface CLI_WIZARD Startup Interview CLUSTER SCM Utilities COMMONLIB Common Messages COMMON_DNAS Common DNAS Messages COMMON_NIS Common NIS messages CORE Core collector messages CRMD Critical Resource Monitor Daemon DDBD...
  • Page 136 Troubleshooting Tools Accessing the Syslog Log Component Description DNAS_PGRP DNAS Process Group and NFS DNAS_POLICY DNAS Policy DNAS_SINIT DNAS Storage Initialization DNAS_SREMOVE DNAS Storage Removal DNC_LIB DNAS Configuration Library - NFS DOMAIN_JOIN Messages from the Active Directory domain joining components EMAILHOME Email home daemon and cli commands...
  • Page 137 Troubleshooting Tools Accessing the Syslog Log Component Description FTP Front End Service GBLSVC_CLI Global Service CLI Messages GBL_LIB Global Services Library GBL_SVCMGR Global Server Graphical user interface operation messages HA_CLI High Availability CLI messages HWAGENT Hardware Agent IFILER_CLI Internal Filer CLI Messages IPC_EVENT_LIB IPC Event Library IPC_EVENT_MGR...
  • Page 138 Troubleshooting Tools Accessing the Syslog Log Component Description LIBEXIM Exim Utilities messages LIBSDDL CIFS security-descriptor sddl translation library LIBXSD CIFS security-descriptor translation library LIP_LIB Logical IP Address Library LOGMGRD Logging Manager Daemon LVMD Logical Volume Manager Daemon MANUF Manufacturing Purposes only - Internal Switch Software Max enum for message categories, put new categories before this entry.
  • Page 139 Troubleshooting Tools Accessing the Syslog Log Component Description MGT_SVCMGR Service Manager MGT_SVC_AGENT Service Agent MS_CLIENT Microsoft RPC Services Client Library MS_RPC Microsoft RPC Library MTLDAEMON Metalog Daemon NDMP Network DataMover Protocol NDMPAUTH_CLI NDMP Authentication CLI Messages NSM Messages NETBIOS NetBios Configuration Daemon NET_APP Miscellaneous Application Events NET_CIFS...
  • Page 140 Troubleshooting Tools Accessing the Syslog Log Component Description NET_SLB Server Load Balancing NET_STATS NSM Statistics Collection NET_TCPSP TCP Splicing NFSCONFD NFS Configuration Daemon NISD NIS daemon messages Network Lock Manager Daemon messages NMPIPE Named Pipe log messages NSCK DNAS Namespace Check NSCKRPT NSCK Report Messages NSM_RON...
  • Page 141 Troubleshooting Tools Accessing the Syslog Log Component Description PERSONALITY OEM Personality POLICY Policy Engine POLICY_ACTION Replication and Migration POLICY_CLI Policy CLI Messages POLICY_PDP Policy Decision Point POLICY_PEP Policy Enforcement Point POLICY_SHADOW Policy Shadow Volume PROBE Probes for Monitoring and Controlling Subsystems Parallel Treewalk Library RELMGR Release Manager...
  • Page 142 Troubleshooting Tools Accessing the Syslog Log Component Description RON_SPFD RON Routing Daemon RON_VPND RON VPN Daemon ROOTD Root Daemon SCM_DSMD DNAS Switch Monitor SECURITYD Security Daemon SECURITY_CLI Security CLI Messages SEC_CONFIG Security COnfiguration SEC_LOCAL Security Local Enforcement SHMEM Shared Memory SHRTOP Share topology library SLB_CLI...
  • Page 143 Troubleshooting Tools Accessing the Syslog Log Component Description SSB_LIB SSB Library Messages SSB_SIM SSB Simulator SSH configuration SSRM Simple Share Resource Monitor STATSD Statistics Daemon SVCMGR_LIB SvcMgr Client Library SYNC_LIB Shadow Synchronization Library TASK_LIB Task Dispatcher Library TCMD NSM Configuration Manager TIME Time related log messages TRANFS...

  • Page 144: Syslog Syntax

    Troubleshooting Tools Accessing the Syslog Log Component Description Windows Management Authorization CLI Commands and Library XSDD Security descriptor translation daemon Syslog Syntax Each line in the syslog uses the following syntax: utc.uuu-tz:switch:slot-proc-board-pid:cmp-ins-sev-id:: msg For example, 2004-05-06T18:16:54.888-0400:bstnA6k:1-1-SCM-7341:SCM_CLI-0-6-CLI_COMMAND:: User admin: Command: bstnA6k# show nsck Where •...

  • Page 145: Reading Ids For Namespaces, Volumes, And Shares

    Troubleshooting Tools Accessing the Syslog • sev ( ) is the message severity, from 7 (debug) to 2 (critical). • id ( ) is the message-catalog ID, a unique ID for each log message. CLI_COMMAND MSGn is an ID for an uncatologued message. The n is the severity of the message, from 7 (debug) down to 2 (critical).

  • Page 146: Paging Through The Syslog (Show Logs)

    Troubleshooting Tools Accessing the Syslog Share Volume Namespace -------------------- --------------------- --------------------- ----- corporate /vol medco sales /vol medco generic /vol medco budget /acct wwmed bills /acct wwmed bills2 /acct wwmed /acct wwmed metadata-share /acct wwmed /rcrds medarcv charts /rcrds medarcv bulk /rcrds medarcv...
  • Page 147 Troubleshooting Tools Accessing the Syslog For example, this command shows the contents of the active syslog: bstnA6k(cfg)# show logs syslog SWITCH:2004-05-06T06:24:52.386-0400:1-scm-905:SCM_CLI-0-6(I)-CLI_COMMAND:User admin: Command: SWITCH# del report SWITCH:2004-05-06T06:24:53.136-0400:1-scm-905:SCM_CLI-0-6(I)-CLI_COMMAND:User admin: Command: SWITCH# slot reload SWITCH:2004-05-06T06:24:53.161-0400:1-scm-643:CHASS_NEW-0-7(D)-MSG7:slot_cmd_1_s vc SLOT_CMD_RELOAD: begin SWITCH:2004-05-06T06:24:53.206-0400:1-scm-643:CHASS_NEW-0-7(D)-MSG7:Post Event type=CHASSIS, state=DOWN-REQ, shelf=0x1800, slot=0, mod=0x0, proc=0. sm-3-2:init: Switching to runlevel: 6 sm-3-1:init: Switching to runlevel: 6 sm-3-2:2004-05-06T06:24:53.362-0400:3-apm-277:LOGMGRD-0-6(I)-MSG6:Version...

  • Page 148: Searching Through The Syslog

    Troubleshooting Tools Accessing the Syslog Searching Through the Syslog Use the command to apply a regular expression to the syslog as you page grep through it, viewing only the lines that contain a desired string: grep pattern logs [filename] where pattern (1-255 characters) is the regular-expression pattern to search for in the syslog.

  • Page 149: Filtering Messages Out

    Troubleshooting Tools Accessing the Syslog 2004-05-06T06:28:57.198-0400:SWITCH:1-1-SCM-437:LOGMGRD-0-6-MSG6:: Copyright (c) 2002-2004 by bstnA6k Networks Inc. All rights reserved. 2004-05-06T06:31:06.193-0400:SWITCH:3-1-ASM-280:LOGMGRD-0-6-MSG6:: Version 0.12.0.4650 (May 05 2004 18:04:50) [lwisniewski] (build 4650) starting up 2004-05-06T06:31:06.194-0400:SWITCH:3-1-ASM-280:LOGMGRD-0-6-MSG6:: Copyright (c) 2002-2004 by bstnA6k Networks Inc. All rights reserved. 2004-05-06T06:27:49.223-0400:SWITCH:3-2-ASM-280:LOGMGRD-0-6-MSG6:: Version 0.12.0.4650 (May 05 2004 18:04:50) [lwisniewski] (build 4650) starting up 2004-05-06T06:27:49.223-0400:SWITCH:3-2-ASM-280:LOGMGRD-0-6-MSG6:: Copyright (c) 2002-2004 by bstnA6k Networks Inc.

  • Page 150: Searching The End Of The Syslog

    LOGMGRD logs syslog tail 10 sm-3-2:2004-05-06T16:04:58.607-0400:3-apm-280:LOGMGRD-0-6(I)-MSG6:Version 0.12.0.4642 (May 05 2004 06:32:09) [eallen] (build 4642) starting up sm-3-2:2004-05-06T16:04:58.608-0400:3-apm-280:LOGMGRD-0-6(I)-MSG6:Copyright (c) 2002-2004 by Acopia Networks Inc. All rights reserved. 2004-05-06T17:43:58.919-0400:SWITCH:1-1-SCM-425:LOGMGRD-0-6-MSG6:: Version 0.12.0.4652 (May 06 2004 02:29:35) [nbuilds] (build 4652) starting up 2004-05-06T17:43:58.919-0400:SWITCH:1-1-SCM-425:LOGMGRD-0-6-MSG6:: Copyright (c)
  • Page 151 Troubleshooting Tools Accessing the Syslog 2004-05-06T17:46:07.777-0400:SWITCH:3-1-ASM-279:LOGMGRD-0-6-MSG6:: Version 0.12.0.4652 (May 06 2004 02:19:13) [nbuilds] (build 4652) starting up 2004-05-06T17:46:07.777-0400:SWITCH:3-1-ASM-279:LOGMGRD-0-6-MSG6:: Copyright (c) 2002-2004 by Acopia Networks Inc. All rights reserved. 2004-05-06T19:06:53.248-0400:bstnA6k:1-1-SCM-14453:SCM_CLI-0-6-CLI_COMMAND:: User admin: Command: bstnA6k> grep LOGMGRD logs syslog 2004-05-06T19:28:10.958-0400:bstnA6k:1-1-SCM-23511:SCM_CLI-0-6-CLI_COMMAND:: User admin: Command: bstnA6k> grep LOGMGRD logs syslog tail 10...

  • Page 152: Showing The Documentation For A Syslog Message

    Troubleshooting Tools Accessing the Syslog Showing the Documentation for a Syslog Message Many syslog messages (as well as messages from the CLI) have more-verbose documentation associated with them; you can access this additional documentation from the CLI. From any mode, use the command to view the show documentation documentation for a given message:...

  • Page 153: Copying The Syslog File To An Ftp Server

    Lead with an extra “/” if the path starts at the root of the server machine; for example, “porthos//var/log/acopia/syslog” specifies “/var/log/acopia/syslog” on server porthos. Omit the leading slash if the file is going to the home directory for username.

  • Page 154: Copying The Syslog File Through Scp

    Troubleshooting Tools Accessing the Syslog Copying the Syslog File through SCP For secure sites, you can upload with the Secure Copy (SCP) protocol. The URL has a different syntax for SCP transfers: copy logs syslog-file scp://username@server:file [accept-host-key] where syslog-file identifies the syslog file to copy, username@ is a valid username at the remote host, server identifies the SCP server with an IP address or FQDN (for example, “172.16.100.18”...

  • Page 155: Adjusting Logging Levels

    For example, the following command sequence sets up SMTP, exits from cfg mode to priv-exec mode, then mails the “syslog” file to “juser@wwmed.com:” bstnA6k(cfg)# smtp bstnA6k(cfg-smtp)# mail-server email1.wwmed.com bstnA6k(cfg-smtp)# from admin@acopia.wwmed.com bstnA6k(cfg-smtp)# exit bstnA6k(cfg)# exit bstnA6k# copy logs syslog smtp://juser@wwmed.com/arx_syslog bstnA6k# ...

  • Page 156: Disabling Log Messages

    Troubleshooting Tools Accessing the Syslog From cfg mode, use the command to change the logging level for one (or logging level all) log components: logging level component {critical | error | warning | notice | info | debug} where component can be all or any log component (see “Log Components”...

  • Page 157: Showing All Log Components And Levels

    Troubleshooting Tools Accessing the Syslog Showing All Log Components and Levels Use the command to see the logging levels for all log show logging levels components: show logging levels The output is a table where the X next to each log component marks its logging level. If the APP_RON_RTMD component has an X in the “warning”...

  • Page 158: Focusing On One Logging Level

    Troubleshooting Tools Accessing the Syslog Focusing on One Logging Level You can specify a particular log component to show its current logging level: show logging levels component where component can be all or any log component (see “Log Components” on page 6-6).

  • Page 159: Sending Logs To An External Server

    Troubleshooting Tools Sending Logs to an External Server Sending Logs to an External Server You can configure the ARX to send its syslog messages to one or more external servers. The external server receives log messages as they are generated and appends them to its local syslog file.

  • Page 160: Sending Log Messages From A Vlan Interface (Optional)

    Troubleshooting Tools Sending Logs to an External Server For example: bstnA6k(cfg)# no logging destination 10.1.1.90 bstnA6k(cfg)# ... Sending Log Messages from a VLAN Interface (optional) By default, the log messages come from the out-of-band management interface (labeled MGMT on the switch’s front panel). You have the option to change the source address to an in-band (VLAN) management interface, instead: this uses the client/server ports.

  • Page 161: Showing All Logging Destinations

    Troubleshooting Tools Listing Current System Tasks command has the same effect: management source mgmt management source mgmt For example: bstnA6k(cfg)# management source mgmt bstnA6k(cfg)# ... Showing all Logging Destinations To show all configured logging destinations, use from any show logging destination mode: show logging destination For example:...
  • Page 162 Troubleshooting Tools Listing Current System Tasks The processes are listed in the “Subsystem” column. For example: bstnA6k(cfg)# show system tasks Proc Subsystem Instance Memory (Kb) CPU% ---- ---------------------------- -------- ------------ ---- afnEmailHomed 13788 afnEximMgrd 11308 afnFfpMgrd 10372 afnSlmConfd 17652 afncrmd 11784 afnipceventmgrd 9552...
  • Page 163 Troubleshooting Tools Listing Current System Tasks coreCollector (script) 1600 coreTimer (script) 1560 dme_main 14860 dme_main 14228 dmountd 10344 dnas 85844 dnas 104680 dnaspepd 40336 svc_agent 11232 syslog-ng txnmond 11452 Other Tasks 11344 afnloggermgrd 9868 afnnetd 10152 afnssbdevd 5576 coreCollector (script) 1600 coreTimer (script) 1560...

  • Page 164: Showing Tasks From One Processor

    Troubleshooting Tools Listing Current System Tasks Showing Tasks from One Processor You can show the tasks running on a single processor by adding the clause: from show system tasks from slot.processor where slot (1-6 on an ARX®6000) is the slot number of the desired module, and processor (1-6) is the processor number.

  • Page 165: Collecting Diagnostic Information

    Troubleshooting Tools Collecting Diagnostic Information afnnetd 9896 afnpdpd 9884 afnrootd 12236 afnssbdevd 5628 bstnA6k> ... Collecting Diagnostic Information Some problems require thorough examination and diagnosis. To facilitate this, the CLI has a command for collecting all interesting diagnostic information on the ARX and sending it to a remote site.

  • Page 166: Sending The Information Securely, Through Scp

    Troubleshooting Tools Collecting Diagnostic Information For example, the following command exits from cfg mode to priv-exec mode, then sends diagnostic data to ftp.acopia.com: bstnA6k(cfg)# exit bstnA6k# collect diag-info ftp://juser@ftp.acopia.com/acopia-diags.tgz Password: jpasswd Collect diagnostic information? [yes/no] yes % INFO: Transferred 0 megabytes; still copying . . .

  • Page 167: Sending The Information In An E-Mail Message

    Collecting Diagnostic Information For example, the following command exits from gbl mode to priv-exec mode, then uploads diagnostic data through SCP: bstnA6k(cfg)# exit bstnA6k# collect diag-info scp://juser@rh1.wwmed.com:acopia-diags.tgz accept-host-key Password: jpasswd Collect diagnostic information? [yes/no] yes % INFO: The copy command completed successfully.

  • Page 168: Collecting The Information Locally

    Troubleshooting Tools Collecting Diagnostic Information bstnA6k# collect diag-info smtp://juser@wwmed.com/acopia-diags.tgz Collect diagnostic information? [yes/no] yes % INFO: The copy command completed successfully. bstnA6k# ... Collecting the Information Locally You have the option to store the diagnostic-information file on the switch’s internal disks.

  • Page 169: Running The Collection Asynchronously

    For example, the following command exits from cfg mode to priv-exec mode, then asynchronously collects and uploads diagnostic data: bstnA6k(cfg)# exit bstnA6k# collect diag-info async ftp://juser:jpasswd@ftp.acopia.com/acopia-diags.tgz Collect diagnostic information? [yes/no] yes Scheduling report: collect_diag_200711292228.rpt bstnA6k# ... CLI Maintenance Guide...

  • Page 170: Collecting Partial Information

    Troubleshooting Tools Collecting Diagnostic Information Collecting Partial Information You can choose from several optional keywords to expand or narrow the focus of the command: collect collect {diag-info | config | cores | logs | reports | state | all} destination [async] where: diag-info collects everything except reports, as described above.

  • Page 171: Collecting Logs Within A Time Frame

    Troubleshooting Tools Collecting Diagnostic Information For example, the following command exits from gbl mode to priv-exec mode, then sends state information to ftp.acopia.com: bstnA6k(cfg)# exit bstnA6k# collect state ftp://ftp.acopia.com/sys-state.tgz Collect diagnostic information? [yes/no] yes % INFO: The copy command completed successfully.

  • Page 172: Running Show Commands From A Remote Host

    Troubleshooting Tools Running Show Commands from a Remote Host As with a full collection, the CLI prompts for confirmation before collecting the logs. Answer yes to continue. The collection process can be time-consuming, depending on system state and the options that you have chosen; allow at least one minute for the CLI prompt to return.
  • Page 173 Troubleshooting Tools Running Show Commands from a Remote Host juser@mgmt17:~$ ssh admin@10.1.1.7 “show processors” Command>show processors Proc Module State Up Time Total Kb Free Kb CPU1M CPU5M ---- ------ ---------- ------------------ -------- ------- ------ ----- 0 days, 00:27:21 4138072 3774532 3.1* 0 days, 00:28:56 509672...

  • Page 174: Using Quotes Within The Show Command

    Troubleshooting Tools Running Show Commands from a Remote Host portmap rtmd 5544 sntpc 1908 syslog-ng svc_agent 5300 juser@mgmt17:~$ Using Quotes within the Show Command Some show commands require quotes within the command itself. This confuses the CLI parser, and single quotes (‘) are also problematic. To work around this issue, use the URL encoding for the double quote, %22, for the inner quotes.

  • Page 175: Troubleshooting Network Connections

    Chapter 7 Troubleshooting Network Connections This chapter describes the following tools and procedures for troubleshooting the ARX’s network connections: • Ping, • Traceroute, • TTCP, • tracing NSM processes, • packet capture, and • Port mirroring The next chapter discusses tools for troubleshooting managed volumes. Pinging an IP Address From any mode, use the command to send an ICMP ECHO request to another...

  • Page 176: Limiting The Ping Count

    Troubleshooting Network Connections Pinging an IP Address bstnA6k# ping 172.16.22.183 PING 172.16.22.183 (172.16.22.183) 0 data bytes 8 bytes from 172.16.22.183: icmp_seq=1 ttl=60 time=1 ms. from 3.5 8 bytes from 172.16.22.183: icmp_seq=2 ttl=60 time=1 ms. from 3.5 8 bytes from 172.16.22.183: icmp_seq=3 ttl=60 time=1 ms. from 3.5 8 bytes from 172.16.22.183: icmp_seq=4 ttl=60 time=1 ms.

  • Page 177: Pinging From A Particular Processor

    Troubleshooting Network Connections Pinging an IP Address -------172.16.22.183 ping statistics 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max 2/2/2 ms bstnA6k# ... Pinging from a Particular Processor The SCM processor and all the network processors in the ARX can communicate independently through one or more internal addresses.
  • Page 178 Troubleshooting Network Connections Pinging an IP Address To send a ping from a specific processor, use the clause in the command: from ping ping ip-address from slot.processor [count number] where ip-address is the destination for the ping, from is a required keyword, slot (1-6;...

  • Page 179: Sending An Alternate Source Ip

    Troubleshooting Network Connections Pinging an IP Address 8 bytes from 10.53.2.10: icmp_seq=4 ttl=0 time=100 ms from 3.3 8 bytes from 10.53.2.10: icmp_seq=5 ttl=0 time=100 ms from 3.3 8 bytes from 10.53.2.10: icmp_seq=5 ttl=0 time=100 ms from 3.3 -------10.53.2.10 ping statistics 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max 1/1/3 ms bstnA6k>...

  • Page 180: Pinging The Oob Management Network

    Troubleshooting Network Connections Pinging an IP Address Use the clause with the command to send an alternate source IP in the source ping ICMP ECHO request: ping ip-address [from slot.processor] source source-address [count number] where ip-address is the destination for the ping, from slot.processor (optional, 1-6.1-6) chooses a source processor.
  • Page 181 Troubleshooting Network Connections Pinging an IP Address IP Address Subnet Mask Admin Description --------------- --------------- -------- ------------------- 10.1.23.11 255.255.255.0 Enabled prtlndA1k> show ip route Destination/Mask Gateway Cost Interface --------------------------------------------------------------------- 0.0.0.0/0 192.168.74.1 VLAN74 0.0.0.0/0 10.1.23.1 Mgmt 2070 192.168.74.0/24 0.0.0.0 VLAN74 Direct 192.168.78.0/24 192.168.74.2 VLAN74...

  • Page 182: Using Traceroute

    Troubleshooting Network Connections Using Traceroute Using Traceroute You can use the command to show each IP-router hop between the expect traceroute NSM and a given IP address. Like , the command is accessible ping expect traceroute from any mode: expect traceroute destination-address where destination-address is the IP-address for the traceroute.

  • Page 183: Cancelling A Ttcp Transmission

    Troubleshooting Network Connections Testing Throughput with TTCP When the test ends, the CLI shows the results in a one-line report. For example, the following command runs a test to the station at 192.168.98.55: bstnA6k# expect ttcp transmit 192.168.98.55 Starting 10 second TCP transmit test. Hit ^C to abort... 1003.0552 MB / 10.00 sec = 841.3741 Mbps 9 %TX...
  • Page 184 Troubleshooting Network Connections Testing Throughput with TTCP Go to the sending switch to run the test. The IP address to use for the server switch is the .1 address on the server’s private subnet. Use the command (see show ron route “Showing the RON Routes”...

  • Page 185: Tracing Nsm Processes In The "Fastpath" Log

    (and their modules and slots) on the ARX. NSM processes can be very verbose on a busy ARX. This slows client/server traffic at the chosen processor. Use this option only under the guidance of Acopia personnel. The first time you issue any...

  • Page 186: Nsm-Log Components

    Troubleshooting Network Connections Tracing NSM Processes in the “fastpath” Log NSM-Log Components Every NSM-log message originates from a log component on the NSM. A log component is a source of fastpath-log messages, typically an internal NSM process or group of processes. They are similar to the log components that write to the syslog, described in “Log Components”...
  • Page 187 Troubleshooting Network Connections Tracing NSM Processes in the “fastpath” Log Log Component Description TEM_NAT The Start of tem message categories TEM_NAT The Nat subsystem TEM_NFS The NFS proxy TEM_NFS_CLIENT NSM NFS client TEM_NFS_DNAS The NFS proxy interactions with DNAS (becoming obsolete) TEM_NFS_FC NFS file cache management proxy TEM_NFS_IPC...

  • Page 188: Adjusting Nsm Logging Levels

    Troubleshooting Network Connections Tracing NSM Processes in the “fastpath” Log Log Component Description TEM_STATS Statistics TEM_TEME Fastpath environement-kernel TEM_TFTP TFTP client TEM_TTCP The TTCP service TEM_VIP VIP Processing TEM_VIP_FENCE VIP Fencing. Adjusting NSM Logging Levels Each NSM-log component has a logging level that determines the volume of logs that it generates.
  • Page 189 The log output can get very verbose. A busy NSM processor may fail if this level is set too high for too long. You should only use this feature under the strict guidance of Acopia personnel. The first time you enter any...

  • Page 190: Filtering The Log Messages

    Troubleshooting Network Connections Tracing NSM Processes in the “fastpath” Log Filtering the Log Messages You can focus the log output by filtering for a particular subnet, IP address, or other search string. Add a clause to the end of the filter logging fastpath component command:...

  • Page 191: Disabling Log Messages For An Nsm Component

    Troubleshooting Network Connections Tracing NSM Processes in the “fastpath” Log Disabling Log Messages for an NSM Component You can stop all log messages from a given NSM component; this applies to every instance of the component, on every NSM processor that is enabled for logging. Use form of the command: logging fastpath component...

  • Page 192: Disabling Logs From An Nsm Processor

    Troubleshooting Network Connections Tracing NSM Processes in the “fastpath” Log Component Trace Level Filter Type Filter String ------------------------------------------------------------------- TEM_CIFS TEM_CIFS inclusive 192.168.25.15 TEM_CIFS inclusive 172.16.100.183 Disabling Logs from an NSM Processor Remember to stop all NSM processors from logging as soon as you finish your tracing session;...

  • Page 193: Accessing The Fastpath Log

    Troubleshooting Network Connections Tracing NSM Processes in the “fastpath” Log Accessing the fastpath Log You can use to view the fastpath file and show logs fastpath tail logs fastpath follow follow it as it grows. To search through the fastpath file for a pattern, use grep pattern .

  • Page 194: Nsm-Log-Message Syntax

    Troubleshooting Network Connections Tracing NSM Processes in the “fastpath” Log NSM-Log-Message Syntax Each line in the fastpath log file uses the following syntax: utc.uuu+tz:switch:slot-proc-board-pid:cmp-ins-sev-id:: msg This is the same format as is used in the syslog file (recall “Syslog Syntax” on page 6-16).

  • Page 195: Capturing Ip Traffic In A File

    Troubleshooting Network Connections Capturing IP Traffic in a File Capturing IP Traffic in a File This feature is not supported on the ARX®500. From priv-exec mode, you can use the command to start capturing IP capture session traffic and streaming it into a file: capture session session-id ip ip-address [vlan vlan-id] file prefix where session-id (1-4) identifies this capture session, so that you can close it later.

  • Page 196: Changing The Size And Number Of Capture Files

    Troubleshooting Network Connections Capturing IP Traffic in a File Changing the Size and Number of Capture Files By default, the capture session stops when it fills a single file with 16,000 kilobytes of data. You can use the and/or options to change the size and number of filesize filecount capture files:...

  • Page 197: Capturing All Proxy-Ip Traffic

    Troubleshooting Network Connections Capturing IP Traffic in a File bstnA6k# no capture session 1 bstnA6k# ... Capturing all Proxy-IP Traffic You can monitor all traffic to and from the back-end filers with the option. proxy-all This captures any packet whose source or destination IP address is any of the proxy-IP addresses on the ARX (recall “Adding a Range of Proxy-IP Addresses”...

  • Page 198: Showing The Capture

    Troubleshooting Network Connections Capturing IP Traffic in a File proxyTraffic_00002_20060329081643.cap Mar 29 03:17 shadow_usage.cap Mar 29 04:14 268k bstnA6k# ... Showing the Capture The capture-file contents are the same as the output from Tethereal, a commonly-used Network Analyzer. Tethereal is the command-line version of Wireshark (formerly Ethereal), a graphical interface to the same Network-Analyzer functions.

  • Page 199: Showing All Capture Sessions

    Troubleshooting Network Connections Capturing IP Traffic in a File 1.130093 192.168.25.19 -> 192.168.25.10 MOUNT V3 MNT Call 1.130225 192.168.25.19 -> 192.168.25.10 TCP 872 > sunrpc [ACK] Seq=46 Ack=293 Win=6432 Len=0 TSV=1212228831 TSER=144989 1.133642 192.168.25.19 -> 192.168.25.10 Portmap V2 GETPORT Call 1.134426 192.168.25.19 ->...

  • Page 200: Copying The Capture File To An Ftp Server

    Troubleshooting Network Connections Capturing IP Traffic in a File Copying the Capture File to an FTP Server Like the syslog file, you can save the capture file off to a remote FTP server for further analysis. On the remote machine, you can use the graphical Wireshark/Ethereal program or the CLI-based Tethereal program to view the capture file.

  • Page 201: Copying The Capture File To An Scp Server

    Troubleshooting Network Connections Capturing IP Traffic in a File Copying the Capture File to an SCP Server For secure sites, you can upload with the Secure Copy (SCP) protocol. The URL has a different syntax for SCP transfers: copy capture capture-file scp://username@server:file [accept-host-key] where capture-file identifies the capture file to copy,...

  • Page 202: Configuring Port Mirroring

    Oversubscription of the destination monitor port during port mirroring can result in a service interruption. Proceed only upon the advice from Acopia Technical Support. Port mirroring is not supported on the ARX®500. From cfg mode, use the...
  • Page 203 Troubleshooting Network Connections Configuring Port Mirroring Type Slot/ Admin Link Speed Duplex Description Port State Status ----- ---- ------- ------ ------- ------- ----------------------------------- Enabled 100Mb/s Full Enabled Gb/s Full Default Enabled Down Gb/s Unknown Default Enabled Down Gb/s Unknown Default Enabled Down Gb/s Unknown Default...

  • Page 204: Using An Alternative Destination Interface

    Troubleshooting Network Connections Configuring Port Mirroring Using an Alternative Destination Interface You can optionally use another external interface as the destination instead of the “MIRROR” interface. For an ARX®6000 with multiple NSM’s, you must choose a destination on the same NSM as the source interface. From cfg mode, use the monitor command: module...

  • Page 205: Shutting Down Port Mirroring

    Troubleshooting Network Connections Configuring Port Mirroring For example, the following command sequence shows one active monitor session: bstnA6k(cfg)# show monitor Monitor Session: System Source : Slot 3 Port 1 Destination :Mirror-Port Mode: Rx bstnA6k(cfg)# ... Shutting Down Port Mirroring Remember to shut off port-mirroring sessions when you are not actively monitoring them.
  • Page 206 Troubleshooting Network Connections Configuring Port Mirroring 7-32 CLI Maintenance Guide...
  • Page 207 Chapter 8 Troubleshooting Managed Volumes This chapter describes how to • show usage statistics for managed volumes, • remove shares from them, • correct share-import errors, • cleanly remove a namespace and all of its associated configuration objects, • manage file collisions after an import, •...

  • Page 208: Troubleshooting Managed Volumes

    Troubleshooting Managed Volumes Showing Share Statistics Showing Share Statistics The ARX records read/write statistics, including latency measures, for each of its filer shares. It keeps these statistics from the moment each share is “enabled” as part of a namespace share. (For instructions on configuring and enabling a namespace share, refer to the CLI Storage-Management Guide:...
  • Page 209 Troubleshooting Managed Volumes Showing Share Statistics Read: 38,526,836 Bytes Read Calls: 4,866 Total Write: 52,513,213 Bytes Write Calls: 6,543 Total Average Latency: 3.06 MilliSeconds Other Calls: 2,601 Total All Calls: 14,010 Total Namespace : “wwmed”, Share Name: “bills2” Volume : “/acct” Filer: “das3”...
  • Page 210 Troubleshooting Managed Volumes Showing Share Statistics Average Latency: 0.28 MilliSeconds Other Calls: 412 Total All Calls: 517 Total Namespace : “medco”, Share Name: “corporate” Volume : “/vol” Filer: “nas1” NFS Export: “/vol/vol0/direct” Read: 0 Bytes Read Calls: 0 Total Write: 0 Bytes Write Calls: 0 Total...
  • Page 211 Troubleshooting Managed Volumes Showing Share Statistics Volume : “/vol” Filer: “nas3” NFS Export: “/vol/vol2/direct” Read: 41,058,845 Bytes Read Calls: 6,197 Total Write: 55,049,541 Bytes Write Calls: 7,521 Total Average Latency: 0.72 MilliSeconds Other Calls: 19,075 Total All Calls: 32,793 Total Namespace : “medarcv”, Share Name: “rx”...
  • Page 212 Troubleshooting Managed Volumes Showing Share Statistics Read Calls: 12 Total Write: 1,174,640 Bytes Write Calls: 74 Total Average Latency: 0.45 MilliSeconds Other Calls: 26 Total All Calls: 112 Total Namespace : “medarcv”, Share Name: “bulk” Volume : “/rcrds” Filer: “fs2” CIFS Share: “bulkstorage”...

  • Page 213: Showing Share Statistics From One Namespace

    Troubleshooting Managed Volumes Showing Share Statistics Other Calls: 76 Total All Calls: 76 Total Namespace : “insur”, Share Name: “shr1-next” Volume : “/claims” Filer: “nasE1” NFS Export: “/root_vdm_4/patient_records” CIFS Share: “patient_records” Read: 0 Bytes Read Calls: 0 Total Write: 0 Bytes Write Calls: 0 Total Average Latency:...
  • Page 214 Troubleshooting Managed Volumes Showing Share Statistics Volume : “/acct” Filer: “das1” NFS Export: “/lhome/budget” Read: 26,797,768 Bytes Read Calls: 3,868 Total Write: 23,764,102 Bytes Write Calls: 3,342 Total Average Latency: 2.44 MilliSeconds Other Calls: 12,133 Total All Calls: 19,343 Total Namespace : “wwmed”, Share Name: “bills”...

  • Page 215: Showing Statistics From One Volume

    Troubleshooting Managed Volumes Showing Share Statistics Read Calls: 115 Total Write: 822,433 Bytes Write Calls: 115 Total Average Latency: 2.72 MilliSeconds Other Calls: 275 Total All Calls: 505 Total Namespace : “wwmed”, Share Name: “it5” Volume : “/acct” Filer: “das7” NFS Export: “/lhome/it5”...
  • Page 216 Troubleshooting Managed Volumes Showing Share Statistics bstnA6k> show statistics filer dataplane namespace wwmed /acct Share Statistics Summary: ------------------------- Namespace : “wwmed”, Share Name: “budget” Volume : “/acct” Filer: “das1” NFS Export: “/lhome/budget” Read: 26,797,768 Bytes Read Calls: 3,868 Total Write: 23,764,102 Bytes Write Calls: 3,342 Total...

  • Page 217: Focusing On One Share

    Troubleshooting Managed Volumes Showing Share Statistics Focusing on One Share You can narrow the focus down to a single share in the volume. After the volume path, add the share name to the command: show statistics filer dataplane show statistics filer dataplane namespace name volume share-name where name (1-30 characters) identifies the desired namespace, volume (1-1024 characters) identifies the volume, and...

  • Page 218: Showing Share Statistics From One Filer

    Troubleshooting Managed Volumes Showing Share Statistics Showing Share Statistics from One Filer To focus on the share statistics from one back-end filer, use the clause in the filer show command: statistics filer dataplane show statistics filer dataplane filer filer-name where filer-name (1-64 characters) identifies the desired filer. For example, the following command shows share statistics from the “das1”...

  • Page 219: Showing Statistics From One Filer Share

    Troubleshooting Managed Volumes Showing Share Statistics Showing Statistics from One Filer Share To focus on the statistics from one share, use the clause in the filer ... share show command: statistics filer dataplane show statistics filer dataplane filer filer-name share share-name where filer-name (1-64 characters) identifies the desired filer and share-name (1-1024 characters) identifies the filer-share.

  • Page 220: Removing An Imported Share

    Troubleshooting Managed Volumes Removing an Imported Share Removing an Imported Share You can remove a share from its managed volume without affecting service to the volume’s clients. The command migrates all of the share’s files remove-share migrate and master directories to another share or share farm in the same volume. (A master directory is the first-imported (or only) instance of a directory in the managed volume.) Before you remove the share, you must first verify that it is not referenced by any...

  • Page 221: Removing The Empty Directory Tree

    Troubleshooting Managed Volumes Removing an Imported Share The CLI prompts you with a warning before removing the share; enter yes to proceed. The CLI blocks as the volume migrates the files and directories off of the share, then prints a message indicating the success of the share removal. If the removal is interrupted by a reboot and/or failover, it may be incomplete after the switch(es) finish booting.

  • Page 222: Migrating Nfs-Only Directories

    This removes the CIFS attributes from NFS-only directories that migrate to the share. We recommend that you use this feature only under the guidance of Acopia personnel. For example, the following command sequence turns off strict-attribute consistency in the ‘shr1-next’...

  • Page 223: Finding Reports About The Share Removal

    Troubleshooting Managed Volumes Removing an Imported Share bstnA6k(gbl)# namespace insur bstnA6k(gbl-ns[insur])# volume /claims bstnA6k(gbl-ns-vol[insur~/claims])# share shr1-next bstnA6k(gbl-ns-vol-shr[insur~/claims~shr1-next])# strict-attribute-consistency bstnA6k(gbl-ns-vol-shr[insur~/claims~shr1-next])# ... Finding Reports About the Share Removal Each remove-share operation creates two reports as it runs: • drain_share_rule_for_share_share-name_time.rpt, and • remove.job-id.share-name.share-id.rpt These describe two of the phases in removing a share.
  • Page 224 Troubleshooting Managed Volumes Removing an Imported Share import.3.bills2.4.rpt 1 15:19 1.6k DONE: 138 in 00:00:01 import.4.it5.5.rpt 1 15:19 1.6k DONE: 15 in 00:00:01 import.5.rx.10.rpt 1 15:21 1.4k DONE: 20 in 00:00:04 import.6.charts.11.rpt 1 15:21 1.4k DONE: 11 in 00:00:01 import.7.bulk.12.rpt 1 15:21 1.4k DONE: 1 in 00:00:02...

  • Page 225: Showing The Drain-Share Report

    Troubleshooting Managed Volumes Removing an Imported Share Showing the Drain-Share Report The drain-share report shows the number of files migrated off of the share. Use the command to show it. For example, this shows the numbers of files show reports migrated from the it5 share: bstnA6k# show reports drain_share_rule_for_share_it5_200603011538.rpt **** File Placement Report: Started at Wed Mar...

  • Page 226: Showing The Remove Report

    Troubleshooting Managed Volumes Removing an Imported Share Showing the Remove Report The remove report shows the details of the share removal from the volume. For example, this shows the removal of the it5 share: bstnA6k# show reports remove.13.it5.5.rpt **** Storage Remove Report: Started at Wed Mar 1 15:38:47 2006 **** **** Namespace: wwmed...

  • Page 227: Removing The Share Asynchronously

    Troubleshooting Managed Volumes Removing an Imported Share Prepare Stop Time: Wed Mar 1 15:38:47 2006 Prepare Elapsed Time: 00:00:00 ---------------------------------------------------------- Commit Phase: ============================================================ ---------------------------------------------------------- Commit Start Time: Wed Mar 1 15:38:47 2006 ---------------------------------------------------------- Number of Directories Evaluated: Number of Files Removed: ---------------------------------------------------------- Commit Stop Time: Wed Mar...

  • Page 228: Removing Shares Without File Migration

    Troubleshooting Managed Volumes Removing an Imported Share bstnA6k# remove-share migrate wwmed /acct it5 fm1 async WARNING !! Share 'it5' will be removed from volume '/acct' in namespace 'wwmed' after migrating files to 'fm1' Proceed? [yes/no] yes Scheduling report: removeShare.it5.rpt bstnA6k# ... Removing Shares Without File Migration You can also remove a share without migrating its files.

  • Page 229: Forcing The Share Removal For Offline Filers

    Troubleshooting Managed Volumes Removing an Imported Share WARNING !! Share 'oldrx' will be removed from volume '/rcrds' in namespace 'medarcv' WITHOUT migrating files. Proceed? [yes/no] yes Scheduling report: removeShare.oldrx.rpt bstnA6k# ... Forcing the Share Removal for Offline Filers A online-share removal requires a scan of the filer. The scan finds the file attributes (such as ownership and access permissions) for all master directories.

  • Page 230: Canceling A Share Removal

    Troubleshooting Managed Volumes Removing an Imported Share WARNING !! Share 'defunctShr' will be removed from volume '/' in namespace 'ns' WITHOUT migrating files. Proceed? [yes/no] yes Scheduling report: removeShare.defunctShr.rpt bstnA6k# ... Canceling a Share Removal Before the share removal begins, the volume scans the back-end filer. This scan collects all attributes for all of the share’s master directories, to be duplicated at the destination share.

  • Page 231: Correcting Share-Import Errors

    Troubleshooting Managed Volumes Correcting Share-Import Errors Correcting Share-Import Errors After you enable a namespace volume, the volume reads all of its back-end shares and imports all of their files and directories. If anything goes wrong in any share, the failed share shows a Status of “ ”...
  • Page 232 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Access denied by filer. This indicates that the ARX does not have proper permissions to connect to the back-end filer. For NFS exports, check your back-end filer configuration: the back-end share should allow root access to all of the ARX’s proxy IP addresses.
  • Page 233 You may need to escalate to Acopia Support. After you correct the error, retry the import. CLI Maintenance Guide 8-27...
  • Page 234 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: CIFS operation failed with an (CIFS) The filer returned an unexpected error during the import, error indicating a filer fault. and the error indicates a problem at the filer itself. The syslog shows the specific error.
  • Page 235 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Could not update attributes on Failure to update file attributes can be caused by loss of a file/directory during import. connectivity during the import. Use the command show exports and/or...
  • Page 236 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Detected Two or more of the volume’s shares had common filenames that collisions/inconsistencies during no either collided or had NFS/CIFS naming inconsistencies, and modify import. this volume disallows import if it encounters either of these problems.
  • Page 237 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Directory attribute collision A directory on this share has the same name and path as a detected during import. directory on another share, but the attributes are different. (Directory attributes are permission settings for various users and groups, along with various other flags.) For example, suppose share A had a \docs\img directory and share B had a...
  • Page 238 Status Condition Description/Action Error: Export In Use By Another The filer share contains a hidden directory, .acopia, written by a Switch different ARX. Two ARXes cannot import the same share. If the share is not imported by another switch anymore, remove the directory manually and re-import.
  • Page 239 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Failed to create a file/directory This may indicate a full disk on the back-end filer or permissions on filer. problems. Use the command examine all show exports permission settings at the filer.
  • Page 240 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Failed to rename a file/directory The ARX may not have adequate permissions for renaming on filer. files. (The volume is permitted to rename files by the modify command.) Use the command examine all...
  • Page 241 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: File exists in CIFS, but not in (multi-protocol) The share is configured for both NFS and CIFS, NFS. but a directory that is visible in the back-end-CIFS share is not found in the NFS export.
  • Page 242 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Filer does not support specified The protocol(s) configured for the back-end share are not protocols. actually supported at the filer. Use the command to show exports check the protocols supported by the filer.
  • Page 243 Error: Internal IPC communications Internal problems; contact Acopia personnel. failure during import. Error: Invalid sub path specified. CLI Maintenance Guide 8-37...
  • Page 244 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Maximum number of A directory in this share has too many entries (files and/or namehash collisions for a filename subdirectories) whose names differ only in case (for example, reached in a directory.
  • Page 245 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Metadata filer configuration is This is not an import error: it typically occurs while the volume invalid. Data written has been lost, is providing service. This condition disables the volume. corrupting the database.
  • Page 246 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Multi-protocol share is split. (multi-protocol) The command specified an NFS export and filer a CIFS share over two different directory trees. This is unsupported. Retry the command with the correct share and export names, then retry the import.
  • Page 247 You may need to escalate to Acopia Support. After you correct the error, retry the import. CLI Maintenance Guide 8-41...
  • Page 248 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Proxy User does not map to (multi-protocol) The proxy user is a Windows username and root user via NFS. password that the volume can use as its identity for share import and for policy operations.
  • Page 249 Someone attempted to remove a share (with filer share pending directory operations could , or remove-share migrate remove-share nomigrate remove not be flushed. ), and an internal error caused the removal to fail. Contact service Acopia Support if you see this message. CLI Maintenance Guide 8-43...
  • Page 250 Troubleshooting Managed Volumes Correcting Share-Import Errors Table 8-1. Share Status Conditions (Continued) Status Condition Description/Action Error: Storage-scan database is (NFS) The ARX creates a temporary database during the import corrupt or inaccessible. process. The database was deleted while the import was underway.

  • Page 251: Restarting The Import

    Internal Error (number) nternal problem; contact Acopia personnel. Metadata Only The share is designated to store namespace metadata only, so there are no client-accessible files to import. This serves as an explanation;...

  • Page 252: Removing The Share From The Volume

    Troubleshooting Managed Volumes Correcting Share-Import Errors If the import failed during the scan of the back-end filer, the managed volume did not change any of its metadata for the share. In this case, it should be enough to disable the share (with in gbl-ns-vol-shr mode) and then re-enable it.
  • Page 253 Troubleshooting Managed Volumes Correcting Share-Import Errors Use the command to migrate all files and directories to another remove-files migrate share before removing it from the volume. This command was described above; see “Removing an Imported Share” on page 8-14. The share with the master instance of a directory (or master directory) is considered the “home”...

  • Page 254: Retaining Imported Directories (Not Files) In The Volume

    Troubleshooting Managed Volumes Correcting Share-Import Errors Retaining Imported Directories (Not Files) in the Volume To keep imported directories in the volume but remove any of the share’s imported files, use the command. This was described in “Removing remove-files nomigrate Shares Without File Migration” on page 8-22.

  • Page 255: Retaining Nothing From The Share

    Troubleshooting Managed Volumes Correcting Share-Import Errors Retaining Nothing from the Share To remove all traces of the share, you must remove all of the share’s directories from the volume’s directory tree. This is a serious change in the volume’s metadata, and it requires that you take the volume offline.

  • Page 256: Reimporting The Entire Volume

    Troubleshooting Managed Volumes Correcting Share-Import Errors For example, the following command sequence returns the “budget” share to the “/acct” volume: bstnA6k(gbl)# namespace wwmed bstnA6k(gbl-ns[wwmed])# volume /acct bstnA6k(gbl-ns-vol[wwmed~/acct])# share budget This will create a new share. Create share 'budget'? [yes/no] yes bstnA6k(gbl-ns-vol-shr[wwmed~/acct~budget])# filer das1 nfs3 /exports/budget bstnA6k(gbl-ns-vol-shr[wwmed~/acct~budget])# enable bstnA6k(gbl-ns-vol-shr[wwmed~/acct~budget])# exit...

  • Page 257: Removing A Full Namespace Service

    Troubleshooting Managed Volumes Removing a Full Namespace Service Removing a Full Namespace Service You can use a single command to remove a namespace, all of its volumes, all the global servers and services that export its volumes, and any other configuration objects that are used only by this namespace.
  • Page 258 Troubleshooting Managed Volumes Removing a Full Namespace Service bstnA6k# ... bstnA6k# show reports removeNs_medco_200605260811.rpt **** Remove Namespace Report: Started at Fri May 26 04:11:23 2006 **** % INFO: nsck medco destage force % INFO: wait-for nsck medco 300 % INFO: no enable; namespace medco % INFO: wait-for volume-disable medco 300 % INFO: Removing service configuration for namespace medco % INFO: Removing CIFS browsing for namespace medco...

  • Page 259: Managing Namespace Collisions

    Troubleshooting Managed Volumes Managing Namespace Collisions Managing Namespace Collisions When a managed volume is enabled, the ARX takes inventory from all of the volume’s back-end shares and includes their files into the volume. An important part of this process is to ensure that there is only a single instance of any given path/filename.

  • Page 260: Finding The Renamed Files

    Troubleshooting Managed Volumes Managing Namespace Collisions Finding the Renamed Files To find any files that have collided and been renamed, you can view the report that was generated during import. Each share generates one import report each time it imports (import occurs when the share and volume are first enabled, or if you use to rebuild the volume).
  • Page 261 Troubleshooting Managed Volumes Managing Namespace Collisions bstnA6k(cfg)# show reports import.2.bills.6.rpt **** Share Import Report: Started at Thu Apr 26 03:26:07 2007 **** **** Software Version: 2.05.001.10142 (Apr 25 2007 17:40:50) [nbuilds] **** Hardware Platform: ARX-6000 **** Namespace: wwmed **** Volume: /acct **** Share: bills...
  • Page 262 Troubleshooting Managed Volumes Managing Namespace Collisions ---------------------------------------------------------- Directory Scan Start Time: Thu Apr 26 03:26:07 2007 ---------------------------------------------------------- Type Path -------- ---------------------------------------------------------------------- [R F NC] /index.html -> index_bills-2.html Directories found: Files found: Directories Scanned/Second: Files Scanned/Second: Total Entries Scanned/Second: Leaf Directories Not Scanned: ---------------------------------------------------------- Directory Scan Stop Time: Thu Apr 26 03:26:08 2007...

  • Page 263: Finding Collisions With Cifs '8.3' Names

    Troubleshooting Managed Volumes Finding Collisions with CIFS ‘8.3’ Names Finding Collisions with CIFS ‘8.3’ Names Volumes that support CIFS have an additional naming-collision obstacle, caused by back-end servers keeping an extra name for some files and directories. Windows once ran on file systems (such as FAT12 and FAT16) that supported only short filenames, sometimes called 8.3 names.

  • Page 264: The '8.3'-Fgn Pattern

    Troubleshooting Managed Volumes Finding Collisions with CIFS ‘8.3’ Names The ‘8.3’-FGN Pattern Filers generate alternate 8.3 names with specific patterns, usually including a tilde (~) character to indicate that the name is filer-generated. Any 8.3 FGN falls into one of two patterns: name-with-tilde[.ext] is the most-common pattern, where...

  • Page 265: Identifying All '8.3' Collisions

    Troubleshooting Managed Volumes Finding Collisions with CIFS ‘8.3’ Names Identifying All ‘8.3’ Collisions If CIFS clients complain about access issues or slow performance, you should identify the 8.3 collisions in the volume and work toward changing their names. This is especially true for directory names, which may affect performance for files and directories under them.

  • Page 266: Correcting The Collisions

    Troubleshooting Managed Volumes Finding Collisions with CIFS ‘8.3’ Names Type Share Path ------------------------- -------------------- ------------------------------- [charts /copyRandomx.exe [charts /KMO_ME~1.DAT -> kmo_medical_record.dat [charts /RECORD~1/ -> records_predating_y2k **** Total Found Items: **** Total Lost Items: **** Total Invalid Filehandles: **** Total Migrating Files: **** Total Locking Errors: **** Total Filer Errors: **** Total processed:...

  • Page 267: Finding Nfs-Only Entries In A Multi-Protocol Volume

    Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume Finding NFS-Only Entries in a Multi-Protocol Volume This section applies to volumes in a multi-protocol (CIFS and NFS) namespace only, where the CIFS name and the NFS name for a file may differ. Some file/directory names are legal in NFS but illegal in CIFS, or are legal in CIFS but illegal in NFS.

  • Page 268: Identifying All Nfs-Only Entries

    Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume A directory with any FGN-patterned names introduces the opposite problem: a new NFS-only entry can create a back-end FGN that collides with an existing entry. In this case, the pre-existing entry with the FGN-patterned name becomes “NFS-only.” For example, if “MYFILE~1”...
  • Page 269 Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume **** LF = File exists in the metadata, but is missing from the physical filer. **** LD = Directory exists in the metadata, but is missing from the physical filer. **** FF = File exists on the physical filer, but is missing from the metadata.
  • Page 270 Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume [shr1-old /OVERDU~1.DOC -> overdueclaimsmemo.doc NF IC [shr1-old /images/:PFCD700 NI NM [shr1-old /images/file012b/ (Characters: U+012b) NF CC [shr1-old /stats/piechart.ppt NF CC [shr1-old /stats/PieChart.ppt NF IC [shr1-old /stats/on_the_job:2004.cnv NF IC [shr1-old /stats/on_the_job:2003.cnv NF IC [shr1-old /stats/in_home:2005...

  • Page 271: Case-Blind Collisions (Cc)

    Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume Case-Blind Collisions (CC) A case-blind collision occurs when two or more entries in the same parent directory have names that differ only in case (for example, “index.html” and “INDEX.html”). CIFS does not support case collisions, but NFS does. These are created by NFS clients, either before import or while the volume is in service.

  • Page 272: Client View: Acopia-Generated Names

    Finding NFS-Only Entries in a Multi-Protocol Volume Client View: Acopia-Generated Names A managed volume creates its own Acopia-generated names (AGNs) for files or directories with illegal CIFS characters. The volume presents the AGN to its CIFS clients. The AGN has a unique format, easily distinguishable from the formats of any...

  • Page 273: Unicode Characters In Cifs Names: Non-Mappable In Nfs (Nm)

    Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume An FGN pattern typically follows the “8.3” model; recall “The ‘8.3’-FGN Pattern” on page 8-58. The exception is on EMC file servers, where the base name may exceed 8 characters. Whenever an EMC file server generates a long FGN, the base name ends with a tilde (~) followed by a number: long-base-name~n[.[ext]] An entry is NFS-only if it matches the FGN pattern and collides with an actual FGN.

  • Page 274: Non-Mappable File Names

    Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume Non-Mappable File Names For files, the volume uses the NFS-side FGN for the filename. If the FGN contains any illegal CIFS characters (as they often do), the volume also creates a CIFS-side AGN from that FGN.

  • Page 275: Split Directories (Sp)

    Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume The directory renames follow the pattern below. The volume replaces each unmappable CIFS character with its numeric equivalent: new-dirname_share-jobid[-index][.ext] where new-dirname is the original CIFS-side name, but with “(U+nnnn)” in place of each unmappable character.

  • Page 276: Preventative Striping

    Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume If the directory contains either of these name types, the volume must check for FGN collisions every time a client creates a name of the other type. The FGN-collision check was described earlier, in “Performance Issues”...

  • Page 277: Recursively Correcting Split Directories

    Troubleshooting Managed Volumes Finding NFS-Only Entries in a Multi-Protocol Volume You can correct a marked directory by correcting all of the NFS-only entries within it. After the rename(s), you must run the command to remove the sync files ... recurse NFS-only flags from the volume’s renamed files and directories.

  • Page 278: Finding A File's Physical Location

    Troubleshooting Managed Volumes Finding a File’s Physical Location Finding a File’s Physical Location Using a virtual-file path, visible through a VIP, you can find a file’s location on its actual back-end filer. From any mode, use the command: find find host hostname-or-vip {cifs | nfs} share-name path path where hostname-or-vip (1-255 characters) is the DNS hostname or VIP that clients use to access the file (syntax for a WINS name appears later),...

  • Page 279: Showing The Nfs Filehandles

    Troubleshooting Managed Volumes Finding a File’s Physical Location Showing the NFS Filehandles You can also show the NFS filehandles, both from the client perspective and the server perspective. Use the optional keyword at the end of the command to verbose add the filehandles to the output: find host hostname-or-vip {cifs | nfs} share-name path path verbose where verbose (optional) adds the NFS filehandles to the output.

  • Page 280: Finding The File With A Global-Server Name

    Troubleshooting Managed Volumes Finding a File’s Physical Location Finding the File with a Global-Server Name You can also use the global-server name and path to find a file: find global-server fqdn {cifs | nfs} share-name path path [verbose] where fqdn (1-255 characters) identifies the global server that clients use to access the file (for example, “myServer.com”), {cifs | nfs} share-name (1-4096 characters) is the share that clients use, and path (1-4096 characters) specifies the client-visible path to the file.

  • Page 281: Finding The File With A Wins Name

    Troubleshooting Managed Volumes Finding a File’s Physical Location Finding the File with a WINS Name A CIFS/NTLM front-end service can advertise its shares using a NetBIOS name registered with a WINS server (see “Setting the NetBIOS Name (optional, CIFS)” on page 10-7 of the CLI Storage-Management...

  • Page 282: Finding The File From A Namespace Perspective

    Troubleshooting Managed Volumes Finding a File’s Physical Location Finding the File from a Namespace Perspective You can also use the namespace name and path to find a file: find namespace namespace path path [verbose] where namespace (1-30 characters) identifies the namespace of the file, path (1-4096 characters) specifies the client-visible path to the file, and verbose (optional) adds the file’s NFS filehandles to the output.

  • Page 283: Showing Policy History For A Volume

    Troubleshooting Managed Volumes Showing Policy History for a Volume 0x000040006e00000001000000000001000000000000000000--------00000000 Physical File Handle (20 bytes): 0x0100000100030002020000000f831b00c862ec6d bstnA6k(gbl)# ... Showing Policy History for a Volume From any mode, you can use the command to show all of the show policy history policy transactions for a given managed volume: show policy history namespace vol-path where...

  • Page 284: Showing Detailed Status For A Particular Rule

    Troubleshooting Managed Volumes Showing Policy History for a Volume 2008-01-29T05:54:57 Rule [wwmed:/acct:docs2das8]: Starting scan. 2008-01-29T05:55:01 Rule [wwmed:/acct:docs2das8]: Scan complete. 2008-01-29T06:33:25 Rule [wwmed:/acct:wwmed:/acct:drain_share_rule_for_share_it5]: Created. 2008-01-29T06:33:25 Rule [wwmed:/acct:drain_share_rule_for_share_it5]: Enabled. 2008-01-29T06:33:36 Rule [wwmed:/acct:drain_share_rule_for_share_it5]: Starting scan. 2008-01-29T06:33:36 Rule [wwmed:/acct:drain_share_rule_for_share_it5]: Scan complete. 2008-01-29T06:33:40 Rule [wwmed:/acct:drain_share_rule_for_share_it5]: Disabled. 2008-01-29T06:36:57 Rule [wwmed:/acct:fm1]: Reset.

  • Page 285: Showing Any Or All Pending Migrations

    Troubleshooting Managed Volumes Showing Policy History for a Volume This example shows the history for the “fm1” share farm in the same volume: bstnA6k(gbl)# show policy history wwmed /acct fm1 Namespace: wwmed Volume: /acct Rule ---------------------------------------- Time Message -------------------- ------------------------------------------------------------ 2008-01-29T05:54:47 Enabled.
  • Page 286 Troubleshooting Managed Volumes Showing Policy History for a Volume The output shows a table with one row per file. The file path, rule name, and storage target are identified in each line. If files appear in the queue, the files may be very large, or there may be a problem with the policy engine or filers.

  • Page 287: Troubleshooting Cifs Services

    Chapter 9 Troubleshooting CIFS Services This chapter describes how to run various show commands that monitor client traffic to a front-end CIFS service. It also contains commands to break a CIFS-client connection or close an open file. This extends the previous chapters, which described tools for collecting diagnostic information and troubleshooting network connections.
  • Page 288 Global Server: ac1.medarch.org [192.168.25.15] Tree Connects Proc Export Virtual Path Curr Peak Total ---- ---------------- ---------------- ---- ---- ----- ARCHIVES /rcrds Y2005 /rcrds/2005 acopia#rcrds$ /rcrds acopia#lab_equipment$ /lab_equipment /test_results /acopia# CELEBS /rcrds/VIP_wing Y2004 /rcrds/2004 ARCHIVES /rcrds acopia#rcrds$ /rcrds acopia#lab_equipment$ /lab_equipment /test_results /acopia# CELEBS...

  • Page 289: Showing Statistics From One Nsm Processor

    Global Server: ac1.medarch.org [192.168.25.15] Tree Connects Proc Export Virtual Path Curr Peak Total ---- ---------------- ---------------- ---- ---- ----- ARCHIVES /rcrds Y2005 /rcrds/2005 acopia#rcrds$ /rcrds acopia#lab_equipment$ /lab_equipment /test_results /acopia# CELEBS /rcrds/VIP_wing Y2004 /rcrds/2004 ---- ---- ----- Totals: CLI Maintenance Guide...

  • Page 290: Showing Client Sessions

    Troubleshooting CIFS Services Showing Client Sessions Showing Client Sessions If MMC is allowed for this CIFS service (see “Allowing Clients to Use Windows Management (MMC)” on page 11-22 of the CLI Storage-Management Guide), authorized clients can use MMC to list all client connections to the CIFS service. You can perform the same operation from the CLI.

  • Page 291: Showing Client Sessions At One Nsm Processor

    Troubleshooting CIFS Services Showing Client Sessions Showing Client Sessions at One NSM Processor Each CIFS-client session is managed by one NSM processor. If you show the connections to a single CIFS service (as shown above), you can narrow the focus further to a single NSM processor.

  • Page 292: Getting Details On A Single Client

    Troubleshooting CIFS Services Showing Client Sessions Getting Details on a Single Client For a more-detailed view of a client session, use the show cifs-service client-activity command: show cifs-service client-activity fqdn ip where fqdn (1-128 characters) identifies a single CIFS service, and ip identifies the client session by its source-IP address.
  • Page 293 Troubleshooting CIFS Services Showing Client Sessions Open Files: 5 FE Client ID FE UID FE TID FE FID BE Client ID BE UID BE TID BE FID Path ------------ ------ ------ ------ 4096 2052 16395 \rcrds\2004\infarction_stats.xsl 4096 2052 49158 \rcrds\2004\planB\jmilton_rcrd.dat \rcrds 4096 2053...

  • Page 294: Dropping A Cifs Client

    Troubleshooting CIFS Services Dropping a CIFS Client Dropping a CIFS Client From priv-exec mode, you can use to close a session drop cifs-service user-session with a CIFS client: drop cifs-service user-session fqdn slot.processor ipaddress client where fqdn (1-128 characters) identifies a single CIFS service, slot.processor identifies an NSM processor, and client identifies the client session by its source-IP address.

  • Page 295: Listing Open Files In A Cifs Service

    Troubleshooting CIFS Services Listing Open Files in a CIFS Service Listing Open Files in a CIFS Service To prevent locking contention with CIFS clients, the policy engine does not migrate or replicate (shadow-copy) any files that are already opened by CIFS clients for writes.

  • Page 296: Focusing On One Nsm Processor

    Troubleshooting CIFS Services Listing Open Files in a CIFS Service 172.16.100.68 Read 192.168.25.15 Y2004 medarch\mhoward_md 0.0.0.0 File:\rcrds\2004 172.16.100.6 Read+Write 192.168.25.15 Y2004 medarch\juser 16395 192.168.25.20 Y2004 File:\rcrds\2004\infarction_stats.xsl 172.16.100.6 Read+Write 192.168.25.15 Y2004 medarch\juser 49158 192.168.25.20 Y2004 File:\rcrds\2004\planB\jmilton_rcrd.dat 172.16.100.6 Read 192.168.25.15 ARCHIVES medarch\juser 0.0.0.0 File:\rcrds 172.16.100.6...
  • Page 297 Troubleshooting CIFS Services Listing Open Files in a CIFS Service For example, this shows all open files hosted by the “ac1.medarch.org” service at NSM processor 3.6: bstnA6k> show cifs-service open-files ac1.medarch.org 3.6 Proc User IP F/E FID Mode Virtual IP F/E Share Name User Name B/E FID...

  • Page 298: Closing An Open File

    Troubleshooting CIFS Services Closing an Open File Closing an Open File The policy engine does not migrate or replicate (shadow-copy) any file that is opened for writes by a CIFS client. For situations where migration is required for a long-opened file, you can use the command to close the file.
  • Page 299 Troubleshooting CIFS Services Closing an Open File 172.16.100.6 1046 Read+Write 192.168.25.15 ARCHIVES medarch\juser 32781 192.168.25.29 prescriptions File:\rcrds\flu_vaccine.list Total number of files displayed is 5. bstnA6k> enable bstnA6k# close cifs file ac1.medarch.org 3.6 fid 1046 slot:3.6 CIFS open file with FID:1046 closed.

  • Page 300: Listing Kerberos Tickets Granted To Clients

    Troubleshooting CIFS Services Listing Kerberos Tickets Granted to Clients Listing Kerberos Tickets Granted to Clients If Kerberos is active for this CIFS service, the service passes Kerberos tickets to clients who successfully authenticate. The CIFS service caches the Kerberos tickets on behalf of its clients.

  • Page 301: Listing Tickets Granted To A Particular Principal

    Troubleshooting CIFS Services Listing Kerberos Tickets Granted to Clients 06/07/06 21:06:37 06/08/06 07:06:10 pv770n$@MEDARCH.ORG Total number of principals displayed is 1 Total number of ticket-granting-tickets cached for this selection is 1 Total number of service tickets cached for this selection is 2 bstnA6k>...
  • Page 302 Troubleshooting CIFS Services Listing Kerberos Tickets Granted to Clients Total number of principals displayed is 1 Total number of ticket-granting-tickets cached for this selection is 1 Total number of service tickets cached for this selection is 2 bstnA6k> ... 9-16 CLI Maintenance Guide...

  • Page 303: Gui Maintenance

    Use the instructions in this chapter to regenerate the SSL key. Removing the SSL Key The SSL key in stored in the “acopia.keystore” file in the configs directory. You can use the command to view the contents of the configs directory, and you...

  • Page 304: Restarting The Gui

    Access” on page 8-2 of the CLI Network-Management Guide. For example, the following command sequence stops and restarts the GUI, then shows that the GUI recreated the “acopia.keystore” file: bstnA6k# config bstnA6k(cfg)# management access https bstnA6k(cfg-mgmt-access[HTTPS])# no permit all 10-2...
  • Page 305 GUI Maintenance Restarting the GUI bstnA6k(cfg-mgmt-access[HTTPS])# permit all bstnA6k(cfg-mgmt-access[HTTPS])# show configs configs acopia.keystore May 18 11:42 1.2k boot-config May 18 11:42 1.3k omDbVersion.info May 18 03:00 running May 17 10:25 7.5k startup-config May 18 11:43 6.2M bstnA6k(cfg-mgmt-access[HTTPS])# ... CLI Maintenance Guide...
  • Page 306 GUI Maintenance Restarting the GUI 10-4 CLI Maintenance Guide...

  • Page 307: Powering Down The Arx

    You can power down the ARX for up to 72 hours without incurring significant down time on power-up. This chapter describes how to power down a single ARX and a redundant pair of them. For down times of greater than 72 hours, contact Acopia support.

  • Page 308: Checking The Nvram Battery

    Powering Down the ARX Checking the NVRAM Battery If the ARX has a redundant peer, copy the running-config off of the peer, too. You do not need to copy the global-config, which is shared between the peers. For example, bstnA6kB# copy running-config ftp://juser:jpasswd@172.16.100.183//var/a6kB-running.cfg % INFO: The copy command completed successfully.

  • Page 309: Turning Off The Power

    Turning Off the Power Good No Error bstnA6kB# Contact Acopia support if your output does not match the above NVR Battery and ECC State. Turning Off the Power By this time, all ARX clients should be aware of the impending service outage.

  • Page 310: Restoring Power

    Powering Down the ARX Restoring Power Restoring Power To watch the boot-up messages as the system powers up, you can connect a serial line to the ARX’s Console port. Each Hardware Installation guide shows the location of this port, a 9600-baud, 8-N-1 terminal. Turn the power back on with the power button or switch(es).

  • Page 311: Showing Namespace Status

    Powering Down the ARX Restoring Power --------------------------------------------------------------------------------------- Fri Jul 21 03:55:08 - No active alarms. bstnA6kB(cfg)# ... Showing Namespace Status command shows the state of all namespaces, show namespace status all volumes, and shares. This is described in the CLI Storage-Management Guide;...
  • Page 312 Powering Down the ARX Restoring Power das7 Online NFS: /lhome/it5 Namespace: medco Description: Share Filer Status NFS Export ------------------------- ------------------------------------- ----------- Volume: /vol Enabled corporate nas1 Online NFS: /vol/vol0/direct sales nas2 Online NFS: /vol/vol1/direct generic nas3 Online NFS: /vol/vol2/direct Namespace: medarcv Description: Share Filer...
  • Page 313 Powering Down the ARX Restoring Power Online CIFS: prescriptions bulk Online CIFS: bulkstorage charts Online CIFS: histories metadata-share nas1 Online NFS: /vol/vol1/meta3 Volume: /test_results Enabled chemistry Online CIFS: chem_results hematology Online CIFS: hematology_results Namespace: insur Description: Share Filer Status CIFS Share NFS Export ------------------------- ------------------------------------- ----------- Volume: /claims...

  • Page 314: Showing Front-End Service Health

    Powering Down the ARX Restoring Power shr1-next nasE1 Online CIFS: patient_records NFS: /root_vdm_4/patient_records bstnA6k(cfg)# ... Showing Front-End Service Health to verify that all NFS and/or CIFS services are running show virtual service properly. In a redundant pair, these services only run on the active peer. All services should have a state of “Ready.”...
  • Page 315 Powering Down the ARX Restoring Power 192.168.25.234 Quorum 07:36:57 07/21/2006 Date/Time(UTC) Recent History --------------------------------------------------------------------------- 07-21 07:37:13 Quorum disk is online, system is ready for failover 07-21 07:37:08 Pair status changed from JoinWait to Formed 07-21 07:37:08 Peer switch 'bstnA6kB' is now online CLI Maintenance Guide 11-9...
  • Page 316 Powering Down the ARX Restoring Power 11-10 CLI Maintenance Guide...
  • Page 317 Copyrights Copyright (c) 1990, 1993, 1994, 1995 The Regents of the University of California. All rights reserved. Copyright 2000 by the Massachusetts Institute of Technology. All Rights Reserved. Export of this software from the United States of America may require a specific license from the United States Government.
  • Page 318 Copyright-2 CLI Maintenance Guide...
  • Page 319 CIFS 5-30 support for CIFS share-level ACLs services 8-53 Acopia-generated names listing open files in front-end CIFS services Adaptive Resource Switch (ARX) Alarms showing client-activity details for CIFS shares showing active alarms showing client-connection stats for CIFS shares 9-14...
  • Page 320 show global-config show running-config 8-72 find delete releases Front-end services Disaster recovery troubleshooting CIFS 3-19 restoring the switch configuration drop cifs-service user-session copying a software release from an FTP server restoring running-config from an FTP server 3-19 7-26 saving a capture file to an FTP server 6-25 saving a syslog file to an FTP server , use...
  • Page 321 8-45 import collisions nsck utility 8-14 removing an imported share 5-19 sync utility Nested shares in a CIFS volume Reboot 5-30 adding after import Release files Network upgrading Acopia switch’s place reload CLI Maintenance Guide Index-3...
  • Page 322 8-25 Reports Share import error conditions 8-19 drain-share-rule Shares 8-54 5-30 import adding CIFS subshares after import 8-54 listing all nsck and sync reports import report 5-12 metadata inconsistencies showing read/write stats 5-43 7-23 metadata migration show capture 7-25 metadata-only show capture sessions showing status show cifs-service client-activity...
  • Page 323 running CLI commands on a remote ARX 6-44 using to run a from a remote host restore data Volume backing up and restoring 8-16 strict-attribute-consistency 5-39 de staging (for recovery) Subshares troubleshooting managed volumes 5-30 adding after volume import 5-22 sync directories 5-19 sync files...
  • Page 324 Index-6 CLI Maintenance Guide...

Table of Contents