DOCSLIB.ORG

Cisco Tidal Enterprise Scheduler 6.2.1 Command Line Program Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cisco Tidal Enterprise Scheduler 6.2.1 Command Line Program Guide Cisco Tidal Enterprise Scheduler 6.2.1 SP3 Command Line Program Guide February 5, 2016 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco Tidal Enterprise Scheduler 6.2.1 SP3 Command Line Program Guide © 2016 Cisco Systems, Inc. All rights reserved. CONTENTS Preface ix Audience ix Related Documentation ix Obtaining Documentation and Submitting a Service Request ix Document Change History x Introduction 1-11 Overview 1-11 Installing the Command Line Program 1-11 Windows 1-11 Linux/Unix 1-12 Activating the Command Line Program 1-12 Using Job Aliases 1-13 Scripts and Batch Files 1-13 Running the Command Line from TES 1-13 Command Modes 1-13 Single Command Mode 1-14 Multiple Command Mode 1-14 Command Line Interface 1-15 Command Line Syntax 1-15 Text Conventions 1-16 Job Status ID Cross Reference 1-16 Command Summary 1-17 Master Commands 1-18 Individual Job Occurrence Commands 1-18 Production Schedule Commands 1-19 Dependency Commands 1-19 Job and Job Group Definitions Commands 1-19 Batch Processing Command 1-20 Help Command 1-20 Command Descriptions 2-23 addrule 2-23 Cisco Tidal Enterprise Scheduler 6.2 Command Line Program Guide 6.2.1 iii Contents Syntax 2-24 addrule -options 2-24 Examples 2-25 agent 2-26 Syntax 2-26 agent -options 2-26 Examples 2-26 alerts 2-27 Syntax 2-27 alert[s] -options 2-27 Examples 2-27 alertset 2-28 Syntax 2-28 alertset -options 2-28 Operation 2-28 Examples 2-28 calendar 2-28 Syntax 2-29 calrecalc 2-29 Syntax 2-29 calrecalc -options 2-29 Operation 2-29 compile 2-29 Syntax 2-29 compile -options 2-30 Operation 2-30 Examples 2-30 delrule 2-30 Syntax 2-30 delrule -options 2-31 Operation 2-31 Examples 2-31 depadd 2-31 Syntax 2-31 depadd -options 2-32 Job Dependency Options 2-32 File Dependency Options 2-33 Variable Dependency Options 2-34 Examples 2-34 Cisco Tidal Enterprise Scheduler 6.2 Command Line Program Guide iv 6.2.1 Contents depdel 2-34 Syntax 2-34 depdel -options 2-35 Examples 2-36 file 2-37 Syntax 2-37 Operation 2-37 Example 2-37 grpupd 2-38 Syntax 2-38 grpupd -options 2-38 help 2-38 Syntax 2-38 help -options 2-38 Operation 2-38 Example 2-39 historyPurge 2-39 Syntax 2-39 historyPurge -options 2-39 Operation 2-40 Example 2-40 hosts 2-40 Syntax 2-40 hosts -options 2-40 inactrule 2-40 Syntax 2-40 inactrule -options 2-41 Examples 2-41 jobadd 2-41 Syntax 2-41 jobadd -options 2-42 Examples 2-42 jobcancel 2-42 Syntax 2-42 jobcancel -options 2-43 Operation 2-43 Examples 2-43 jobdep 2-43 Syntax 2-43 Cisco Tidal Enterprise Scheduler 6.2 Command Line Program Guide 6.2.1 v Contents jobdep -options 2-44 Examples 2-44 jobgo 2-44 Syntax 2-44 jobgo -options 2-44 Operation 2-44 jobhold 2-45 Syntax 2-45 jobhold -options 2-45 Operation 2-45 jobmod 2-45 Syntax 2-45 jobmod -options 2-45 jobmon 2-46 Syntax 2-47 jobmon -options 2-47 Examples 2-48 jobrelease 2-48 Syntax 2-48 jobrelease -options 2-49 Operation 2-49 Example 2-49 jobremove 2-49 Syntax 2-49 jobremove -options 2-49 Operation 2-50 Examples 2-50 jobrerun 2-50 Syntax 2-50 jobrerun -options 2-50 Operation 2-51 Example 2-51 jobset 2-51 Syntax 2-51 jobset -options 2-52 Operation 2-52 Examples 2-52 listrule 2-52 Syntax 2-52 Cisco Tidal Enterprise Scheduler 6.2 Command Line Program Guide vi 6.2.1 Contents listrule -options 2-53 Examples 2-54 liststat 2-54 Syntax 2-54 liststat -options 2-55 modrule 2-55 Syntax 2-55 modrule -options 2-55 Operation 2-61 Examples 2-61 output 2-62 Syntax 2-62 output -options 2-62 Operation 2-62 pause 2-62 Syntax 2-62 pause -options 2-62 qlimit 2-62 Syntax 2-62 qlimit -options 2-63 Operation 2-63 resume 2-63 Syntax 2-63 resume -options 2-63 status 2-63 Syntax 2-64 status -options 2-64 Examples 2-64 submit 2-65 Syntax 2-65 submit -options 2-65 Examples 2-65 useradd 2-65 Syntax 2-65 useradd -options 2-66 Operation 2-66 varset 2-66 Syntax 2-66 varset -options 2-66 Cisco Tidal Enterprise Scheduler 6.2 Command Line Program Guide 6.2.1 vii Contents Operation 2-67 Using the Master Command Line Utility 3-71 Overview 3-71 Options for the TESM Command 3-71 cm 3-72 FT 3-72 JMX 3-72 keystoremgr 3-73 loglevel 3-73 pause 3-73 resume 3-74 setpwd 3-74 superuseradd userid domainname 3-74 systemvalue 3-75 Customizing the Command Line Program 4-1 Overview 4-1 tescmd.props 4-2 table.props 4-3 Cisco Tidal Enterprise Scheduler 6.2 Command Line Program Guide viii 6.2.1 Preface This guide describes how to the Command Line Program for Cisco Tidal Enterprise Scheduler (TES) 6.2. Audience This guide is for administrators who want to use the Command Line program to automate TES job control functions. Related Documentation See the Cisco Tidal Enterprise Scheduler 6.2 Documentation Overview for a list of all TES guides. Note We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates. Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html. Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service. Cisco Tidal Enterprise Scheduler 6.2 Command Line Program Guide 6.2.1 ix Preface Preface Document Change History The table below provides the revision history for the Command Line Program Guide. Version Number Issue Date Reason for Change 6.2 May 2014 • Updates for 6.2 release. 6.2.1 (SP3) February 2016 • Added <‐r TES variable>, a new alternative option for the varset command. This option indicates that the value for the variable is contained in another TES variable which has to be resolved first. •Minor corrections and restructuring. Cisco Tidal Enterprise Scheduler 6.2 Command Line Program Guide x 6.2.1 CHAPTER 1 Introduction Overview A hidden aspect of TES is its command line program. The sacmd.cmd (Windows) or sacmd.sh (Unix/Linux) program provides access to TES through the MS-DOS command prompt. The Unix version of TES uses a similar program called tesmcmd. The command line program is generally done from the Tidal Web client but you can also use the sacmd.cmd (Windows) or sacmd.sh (Unix/Linux) program on a master machine.
Load more

Recommended publications
  • Shell Scripting with Bash
    Introduction to Shell Scripting with Bash Charles Jahnke Research Computing Services Information Services & Technology Topics for Today ● Introductions ● Basic Terminology ● How to get help ● Command-line vs. Scripting ● Variables ● Handling Arguments ● Standard I/O, Pipes, and Redirection ● Control Structures (loops and If statements) ● SCC Job Submission Example Research Computing Services Research Computing Services (RCS) A group within Information Services & Technology at Boston University provides computing, storage, and visualization resources and services to support research that has specialized or highly intensive computation, storage, bandwidth, or graphics requirements. Three Primary Services: ● Research Computation ● Research Visualization ● Research Consulting and Training Breadth of Research on the Shared Computing Cluster (SCC) Me ● Research Facilitator and Administrator ● Background in biomedical engineering, bioinformatics, and IT systems ● Offices on both CRC and BUMC ○ Most of our staff on the Charles River Campus, some dedicated to BUMC ● Contact: [email protected] You ● Who has experience programming? ● Using Linux? ● Using the Shared Computing Cluster (SCC)? Basic Terminology The Command-line The line on which commands are typed and passed to the shell. Username Hostname Current Directory [username@scc1 ~]$ Prompt Command Line (input) The Shell ● The interface between the user and the operating system ● Program that interprets and executes input ● Provides: ○ Built-in commands ○ Programming control structures ○ Environment
    [Show full text]
  • The Linux Command Line
    The Linux Command Line Fifth Internet Edition William Shotts A LinuxCommand.org Book Copyright ©2008-2019, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042. A version of this book is also available in printed form, published by No Starch Press. Copies may be purchased wherever fine books are sold. No Starch Press also offers elec- tronic formats for popular e-readers. They can be reached at: https://www.nostarch.com. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. Release History Version Date Description 19.01A January 28, 2019 Fifth Internet Edition (Corrected TOC) 19.01 January 17, 2019 Fifth Internet Edition. 17.10 October 19, 2017 Fourth Internet Edition. 16.07 July 28, 2016 Third Internet Edition. 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. Table of Contents Introduction....................................................................................................xvi Why Use the Command Line?......................................................................................xvi
    [Show full text]
  • Shell Variables
    Shell Using the command line Orna Agmon ladypine at vipe.technion.ac.il Haifux Shell – p. 1/55 TOC Various shells Customizing the shell getting help and information Combining simple and useful commands output redirection lists of commands job control environment variables Remote shell textual editors textual clients references Shell – p. 2/55 What is the shell? The shell is the wrapper around the system: a communication means between the user and the system The shell is the manner in which the user can interact with the system through the terminal. The shell is also a script interpreter. The simplest script is a bunch of shell commands. Shell scripts are used in order to boot the system. The user can also write and execute shell scripts. Shell – p. 3/55 Shell - which shell? There are several kinds of shells. For example, bash (Bourne Again Shell), csh, tcsh, zsh, ksh (Korn Shell). The most important shell is bash, since it is available on almost every free Unix system. The Linux system scripts use bash. The default shell for the user is set in the /etc/passwd file. Here is a line out of this file for example: dana:x:500:500:Dana,,,:/home/dana:/bin/bash This line means that user dana uses bash (located on the system at /bin/bash) as her default shell. Shell – p. 4/55 Starting to work in another shell If Dana wishes to temporarily use another shell, she can simply call this shell from the command line: [dana@granada ˜]$ bash dana@granada:˜$ #In bash now dana@granada:˜$ exit [dana@granada ˜]$ bash dana@granada:˜$ #In bash now, going to hit ctrl D dana@granada:˜$ exit [dana@granada ˜]$ #In original shell now Shell – p.
    [Show full text]
  • Sleep 2.1 Manual
    Sleep 2.1 Manual "If you put a million monkeys at a million keyboards, one of them will eventually write a Java program. The rest of them will write Perl programs." -- Anonymous Raphael Mudge Sleep 2.1 Manual Revision: 06.02.08 Released under a Creative Commons Attribution-ShareAlike 3.0 License (see http://creativecommons.org/licenses/by-sa/3.0/us/) You are free: • to Share -- to copy, distribute, display, and perform the work • to Remix -- to make derivative works Under the following conditions: Attribution. You must attribute this work to Raphael Mudge with a link to http://sleep.dashnine.org/ Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under the same, similar or a compatible license. • For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do this is with a link to the license. • Any of the above conditions can be waived if you get permission from the copyright holder. • Apart from the remix rights granted under this license, nothing in this license impairs or restricts the author's moral rights. Your fair use and other rights are in no way affected by the above. Table of Contents Introduction................................................................................................. 1 I. What is Sleep?...................................................................................................1 II. Manual Conventions......................................................................................2 III.
    [Show full text]
  • Netstat Statistics Comparison with Perl by Noah Davids
    Netstat Statistics Comparison with Perl By Noah Davids Comparing sets of numeric output can be tiresome. Using the output from the netstat command helps diagnose problems. Over time, the changes in the statistics reported can be very informative.This article explains how this network specialist and Perl novice decided to write a program to do the comparison for him. INTRODUCTION THE SCRIPT Comparing sets of numeric output can be tedious, especially when The script expects as input a file with the following format: the numbers are large and there are a lot of them. Unfortunately it is Some number of random lines something I have to do fairly often. As a network support specialist, I Line with unique string indicating start of data set 1 often use the output from the netstat command to help diagnose Some fixed number of lines with the format: problems. Changes in the statistics reported over time can be very enlightening. In addition, as part of the support process, I have to LABEL NUMBER LABEL NUMBER LABEL include those differences in my written analysis. Punching the long numbers into a calculator and copying the answer back out is a drag. Some number of random lines Using cut and paste helps only marginally. Line with the same unique string indicating start of data 2 To make my life simpler, I decided to write a program to do the Some fixed number of lines with the format: comparison for me. However, I support four different operating sys- tems, and while each has a netstat command, the format and content LABEL NUMBER LABEL NUMBER LABEL of the output varies with each OS.
    [Show full text]
  • ANSWERS ΤΟ EVEN-Numbered
    8 Answers to Even-numbered Exercises 2.1. WhatExplain the following unexpected are result: two ways you can execute a shell script when you do not have execute permission for the file containing the script? Can you execute a shell script if you do not have read permission for the file containing the script? You can give the name of the file containing the script as an argument to the shell (for example, bash scriptfile or tcsh scriptfile, where scriptfile is the name of the file containing the script). Under bash you can give the following command: $ . scriptfile Under both bash and tcsh you can use this command: $ source scriptfile Because the shell must read the commands from the file containing a shell script before it can execute the commands, you must have read permission for the file to execute a shell script. 4.3. AssumeWhat is the purpose ble? you have made the following assignment: $ person=zach Give the output of each of the following commands. a. echo $person zach b. echo '$person' $person c. echo "$person" zach 1 2 6.5. Assumengs. the /home/zach/grants/biblios and /home/zach/biblios directories exist. Specify Zach’s working directory after he executes each sequence of commands. Explain what happens in each case. a. $ pwd /home/zach/grants $ CDPATH=$(pwd) $ cd $ cd biblios After executing the preceding commands, Zach’s working directory is /home/zach/grants/biblios. When CDPATH is set and the working directory is not specified in CDPATH, cd searches the working directory only after it searches the directories specified by CDPATH.
    [Show full text]
  • System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1
    SUSE Linux Enterprise Server 15 SP1 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1 An administrator's guide for problem detection, resolution and optimization. Find how to inspect and optimize your system by means of monitoring tools and how to eciently manage resources. Also contains an overview of common problems and solutions and of additional help and documentation resources. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xiii
    [Show full text]
  • Scripting in Axis Network Cameras and Video Servers
    Scripting in Axis Network Cameras and Video Servers Table of Contents 1 INTRODUCTION .............................................................................................................5 2 EMBEDDED SCRIPTS ....................................................................................................6 2.1 PHP .....................................................................................................................................6 2.2 SHELL ..................................................................................................................................7 3 USING SCRIPTS IN AXIS CAMERA/VIDEO PRODUCTS ......................................8 3.1 UPLOADING SCRIPTS TO THE CAMERA/VIDEO SERVER:...................................................8 3.2 RUNNING SCRIPTS WITH THE TASK SCHEDULER...............................................................8 3.2.1 Syntax for /etc/task.list.....................................................................................................9 3.3 RUNNING SCRIPTS VIA A WEB SERVER..............................................................................11 3.3.1 To enable Telnet support ...............................................................................................12 3.4 INCLUDED HELPER APPLICATIONS ..................................................................................13 3.4.1 The image buffer - bufferd........................................................................................13 3.4.2 sftpclient.........................................................................................................................16
    [Show full text]
  • Sleepless in Seattle No Longer
    Sleepless in Seattle No Longer Joshua Reich†, Michel Goraczko, Aman Kansal, Jitendra Padhye †Columbia University, Microsoft Research Abstract: In enterprise networks, idle desktop ma- wise maintain machines. A number of solutions to this chines rarely sleep, because users (and IT departments) problem have been proposed [33, 3, 6, 30]. The core idea want them to be always accessible. While a number of behind these is to allow a machine to sleep, while a sleep solutions have been proposed, few have been evaluated proxy maintains that machine’s network presence, wak- via real deployments. We have built and deployed a light- ing the machine when necessary. Some of these proposals weight sleep proxy system at Microsoft Research. Our rely on specialized NIC hardware [33, 3]; others advocate system has been operational for six months, and has over use of network-based proxies [6, 30]. 50 active users. This paper focuses on providing a de- Unfortunately, most previous work has been evaluated tailed description of our implementation and test deploy- either using small testbeds [3, 30, 6] or trace-based simu- ment, the first we are aware of on an operational network. lations [30]. We are not aware of any paper detailing the Overall, we find that our lightweight approach effected deployment of any of these proxying solutions in an oper- significant energy savings by allowing user machines to ational enterprise network on actual user machines.1 This sleep (most sleeping over 50% of the time) while main- is disconcerting: systems that work well on testbeds often taining their network accessibility to user satisfaction.
    [Show full text]
  • Introduction to BASH: Part II
    Introduction to BASH: Part II By Michael Stobb University of California, Merced February 17th, 2017 Quick Review ● Linux is a very popular operating system for scientific computing ● The command line interface (CLI) is ubiquitous and efficient ● A “shell” is a program that interprets and executes a user's commands ○ BASH: Bourne Again SHell (by far the most popular) ○ CSH: C SHell ○ ZSH: Z SHell ● Does everyone have access to a shell? Quick Review: Basic Commands ● pwd ○ ‘print working directory’, or where are you currently ● cd ○ ‘change directory’ in the filesystem, or where you want to go ● ls ○ ‘list’ the contents of the directory, or look at what is inside ● mkdir ○ ‘make directory’, or make a new folder ● cp ○ ‘copy’ a file ● mv ○ ‘move’ a file ● rm ○ ‘remove’ a file (be careful, usually no undos!) ● echo ○ Return (like an echo) the input to the screen ● Autocomplete! Download Some Example Files 1) Make a new folder, perhaps ‘bash_examples’, then cd into it. Capital ‘o’ 2) Type the following command: wget "goo.gl/oBFKrL" -O tutorial.tar 3) Extract the tar file with: tar -xf tutorial.tar 4) Delete the old tar file with rm tutorial.tar 5) cd into the new director ‘tutorial’ Input/Output Redirection ● Typically we give input to a command as follows: ○ cat file.txt ● Make the input explicit by using “<” ○ cat < file.txt ● Change the output by using “>” ○ cat < file.txt > output.txt ● Use the output of one function as the input of another ○ cat < file.txt | less BASH Utilities ● BASH has some awesome utilities ○ External commands not
    [Show full text]
  • Troubleshooting Tools and Methodology
    Send documentation comments to [email protected] APPENDIX B Troubleshooting Tools and Methodology This appendix describes the troubleshooting tools and methodology available for the Cisco MDS 9000 Family multilayer directors and fabric switches. It includes the following sections: • Using Cisco MDS 9000 Family Tools, page B-1 • Using Cisco Network Management Products, page B-24 • Using Other Troubleshooting Products, page B-27 • Using Host Diagnostic Tools, page B-28 Using Cisco MDS 9000 Family Tools If the server does not see its storage and you cannot use the information available on the host side to determine the root cause of the problem, you can obtain additional information from a different viewpoint using the troubleshooting tools provided with the Cisco MDS 9000 Family switches. This section introduces these tools and describes the kinds of problems for which you can use each tool. It includes the following topics: • Command-Line Interface Troubleshooting Commands, page B-2 • CLI Debug, page B-2 • FC Ping and FC Traceroute, page B-4 • Monitoring Processes and CPUs, page B-7 • Using On-Board Failure Logging, page B-10 • Fabric Manager Tools, page B-13 • Fibre Channel Name Service, page B-18 • SNMP and RMON Support, page B-19 • Using RADIUS, page B-21 • Using Syslog, page B-21 • Using Fibre Channel SPAN, page B-23 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x OL-9285-05 B-1 Appendix B Troubleshooting Tools and Methodology Using Cisco MDS 9000 Family Tools Send documentation comments to [email protected] Command-Line Interface Troubleshooting Commands The command-line interface (CLI) lets you configure and monitor a Cisco MDS 9000 Family switch using a local console or remotely using a Telnet or SSH session.
    [Show full text]
  • The Linux Command Line
    The Linux Command Line Second Internet Edition William E. Shotts, Jr. A LinuxCommand.org Book Copyright ©2008-2013, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, 171 Second Street, Suite 300, San Fran- cisco, California, 94105, USA. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. This book is also available in printed form, published by No Starch Press and may be purchased wherever fine books are sold. No Starch Press also offers this book in elec- tronic formats for most popular e-readers: http://nostarch.com/tlcl.htm Release History Version Date Description 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. 09.11 November 19, 2009 Fourth draft with almost all reviewer feedback incorporated and edited through chapter 37. 09.10 October 3, 2009 Third draft with revised table formatting, partial application of reviewers feedback and edited through chapter 18. 09.08 August 12, 2009 Second draft incorporating the first editing pass. 09.07 July 18, 2009 Completed first draft. Table of Contents Introduction....................................................................................................xvi
    [Show full text]