DOCSLIB.ORG

UNIX OS Agent User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

IBM Tivoli Monitoring Version 6.3.0 UNIX OS Agent User's Guide SC22-5452-00 IBM Tivoli Monitoring Version 6.3.0 UNIX OS Agent User's Guide SC22-5452-00 Note Before using this information and the product it supports, read the information in “Notices” on page 399. This edition applies to version 6, release 3 of IBM Tivoli Monitoring (product number 5724-C04) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1994, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Tables ...............vii Solaris System CPU Workload workspace ....28 Solaris Zone Processes workspace .......28 Chapter 1. Using the monitoring agent . 1 Solaris Zones workspace ..........28 System Details workspace .........28 New in this release ............2 System Information workspace ........29 Components of the monitoring agent ......3 Top CPU-Memory %-VSize Details workspace . 30 User interface options ...........4 UNIX OS workspace ...........30 UNIX Detail workspace ..........31 Chapter 2. Requirements for the Users workspace ............31 monitoring agent ...........5 Enabling the Monitoring Agent for UNIX OS to run Chapter 4. Attributes .........33 as a nonroot user .............7 Agent Availability Management Status attributes . 36 Securing your IBM Tivoli Monitoring installation 7 Agent Active Runtime Status attributes .....37 Setting overall file ownership and permissions for AIX AMS attributes............38 nonroot users .............7 AIX Defined Users attributes ........39 Setting kuxagent binary permissions .....7 AIX Devices attributes...........39 Limitations of starting the agent as a nonroot user 8 AIX Logical Volumes attributes ........39 Setting up the Monitoring Agent for UNIX OS in a AIX LPAR attributes ...........40 cluster environment ............9 AIX Physical Volumes attributes .......43 Using Agent Management Services .......9 AIX Volume Groups attributes ........44 Filtering capabilities on the names of processes . 10 AIX WPAR CPU attributes .........45 AIX WPAR File System attributes .......45 Chapter 3. Workspaces........11 AIX WPAR Information attributes .......46 Predefined workspaces ..........11 AIX WPAR Network attributes ........47 Agent Management Services workspace .....13 AIX WPAR Physical Memory attributes .....47 Agents' Management Log workspace ......13 Alerts Table attributes ...........48 AIX LPAR Information workspace .......14 All Users attributes ............49 AIX Storage workspace ..........14 Configuration Information attributes ......49 AIX WPAR workspaces ..........14 Data Collection Status attributes .......51 All Files workspace............16 Disk attributes .............51 All Processes workspace ..........16 Disk Performance attributes .........55 Devices Status workspace .........16 File Comparison Group attributes .......57 Disk Usage workspaces ..........16 File Information attributes .........58 Enterprise UNIX System Summary workspace. 18 File Pattern attributes ...........61 File Information workspace .........18 Group attributes .............61 Historical Summarized Availability workspace. 19 IP Address attributes ...........61 Historical Summarized Availability Daily workspace 19 Machine Information attributes ........62 Historical Summarized Availability Hourly Network attributes ............62 workspace ...............19 NFS / RPC Statistics attributes ........68 Historical Summarized Availability Weekly Ping attributes .............77 workspace ...............20 Print Queue attributes ...........78 Historical Summarized Capacity workspace . 20 Process attributes ............78 Historical Summarized Capacity Daily workspace 20 SMP CPU attributes ...........87 Historical Summarized Capacity Hourly workspace 21 Solaris Zones attributes ..........92 Historical Summarized Capacity Weekly workspace 22 SP2 System attributes ...........93 Historical Summarized Performance workspace . 23 System attributes ............101 Historical Summarized Performance Daily TCP Statistics Attributes ..........108 workspace ...............23 Top CPU Processes attributes ........109 Historical Summarized Performance Hourly Top Memory Processes attributes .......110 workspace ...............24 UNIX Devices attributes ..........111 Historical Summarized Performance Weekly UNIX Memory attributes .........112 workspace ...............25 User attributes .............118 Network workspace ...........25 Disk capacity planning for historical data ....119 NFS Activity workspace ..........26 Process workspace ............27 RPC Performance workspace ........28 © Copyright IBM Corp. 1994, 2013 iii Chapter 5. Situations ........123 UNIX_CPU_Busy_Warning situation ....134 Predefined situations ...........124 UNIX_Device_Stopped_Warning situation . 134 Agent Management Services node ......126 UNIX_HD_Excessive_IO_Wait situation . 134 UNIX_AMS_Alert_Critical situation .....126 UNIX_LPARBusy_pct_Warning situation . 134 Disk Usage node ............126 UNIX_LPARPhyBusy_pct_Warning situation 134 UNIX_AIX_Avg_ReqInWaitQ_MS_Info situation 126 UNIX_LPARvcs_Info situation.......135 UNIX_AIX_Avg_Transfer_MS_Info situation . 126 UNIX_LPARfreepool_Warning situation . 135 UNIX_AIX_ServQ_Full_PerSec_Info situation 126 UNIX_LPARPhanIntrs_Info situation ....135 UNIX_BP_SpaceUsedPct_Critical situation. 127 UNIX_LPARentused_Info situation .....135 UNIX_BP_SpaceUsedPctCustom_Crit situation 127 UNIX_LPAR_MaxCPUCapUsed_Info situation 135 UNIX_CMD_Disk_Inodes_Critical situation . 127 UNIX_LPAR_Moved_Info situation .....135 UNIX_CMD_Disk_Inodes_Critical_2 situation 127 UNIX_LPAR_Phyp_Used_High_Info situation 135 UNIX_CMD_Disk_Space_Warning situation . 127 UNIX_Memory_PgFault_Hi_Info situation. 135 UNIX_Disk_Availability situation......127 UNIX_System_Busy_Critical situation ....136 UNIX_Filemount_Critical situation .....128 UNIX_System_Busy_Warning situation ....136 UNIX_HD_Config_Critical situation .....128 UNIX_System_Capacity_Critical situation . 136 UNIX_HD_Config_Critical_2 situation ....128 UNIX_System_Paging_Critical situation . 136 UNIX_scratch_tmp_Disk_Full situation ....128 UNIX_System_RunqAvg_Hi_Info situation . 136 File Information node ..........128 UNIX_User_CPU_Critical situation .....136 UNIX_User_File_Exists situation ......128 UNIX_System_Virtual_Memory_Warning Network node .............128 situation ..............136 UNIX_AIX_NetBandwidth_High_Info situation 128 UNIX_WPAR_Admin_Op_Info situation . 136 UNIX_AIX_TCP_ConnEst_High_Info situation 128 UNIX_WPAR_Broken_Warning situation . 137 UNIX_BP_NetInOutErrPct_Critical situation . 129 UNIX_WPAR_CPU_Usage_Warning situation 137 UNIX_Network_Collsns_Critical situation . 129 UNIX_WPAR_Mem_Usage_Warning situation 137 UNIX_Network_Collsns_Warning situation . 129 UNIX_WPAR_Min_CPU_Limit_Info situation 137 UNIX_Network_Errors situation ......129 UNIX_WPAR_Min_Mem_Limit_Info situation 137 UNIX_Network_Interface_Busy situation . 129 UNIX_WPAR_RC_Inactive_Info situation . 137 UNIX_Network_Interface_Idle situation . 129 UNIX_WPAR_Unlim_CPU_Shares_Info situation 137 NFS Activity workspace ..........129 UNIX_WPAR_Unlim_Mem_Shares_Info UNIX_NFS_RPC_Rejects situation .....129 situation ..............137 Process node .............130 UNIX_AIX_Process_ResDat_Hi_Info situation 130 Chapter 6. Take Action commands 139 UNIX_AIX_Process_ResTxt_Hi_Info situation 130 Predefined Take Action commands ......139 UNIX_BP_ProcHighCpu_Critical situation . 130 AMS Recycle Agent Instance ........140 UNIX_BP_ProcMissing_Critical situation . 130 AMS Reset Agent Daily Restart Count .....140 UNIX_CMD_Process_Critical situation ....130 AMS Start Agent action ..........141 UNIX_CMD_Runaway_Process situation . 130 AMS Start Agent Instance action .......141 UNIX_CPU_Critical situation .......131 AMS Stop Agent action ..........142 UNIX_CPU_Warning situation.......131 AMS Start Management action .......142 UNIX_Process_Memory_Critical situation . 131 AMS Stop Management action .......143 UNIX_Process_Memory_Leak situation ....131 Sample_kill_Process action .........143 UNIX_Process_Memory_Warning situation . 131 UNIX_Process_MISSING_inetd situation . 131 Chapter 7. Policies reference.....145 System Information node .........131 Predefined policies ...........145 UNIX_Active_Virtual_Memory situation . 131 UNIX_CPU_Busy policy..........145 UNIX_AIX_CPU_CtxSwitch_Hi_Info situation 132 UNIX_Disk_Space_Full policy ........145 UNIX_AIX_Device_Stopped_Warning situation 132 UNIX_Virtual_Memory_High policy......146 UNIX_AIX_Memory_RePg_Hi_Info situation 132 UNIX_AIX_System_HypPct_Hi_Info situation 132 Chapter 8. Server dashboards ....147 UNIX_AIX_System_NProcs_Hi_Info situation 132 UNIX_AIX_User_Acct_Locked_Info situation 132 Server dashboards background information . 147 UNIX_AIX_User_Login_Retry_Info situation . 132 Checking the health of your monitored UNIX_BP_AvgCpuBusyPct5min_Criti situation 132 environment..............150 UNIX_BP_CpuBusyPct_Critical situation . 133 Displaying situation event results ......151 UNIX_BP_LoadAvg5min_Critical situation . 133 Managed System Groups Overview dashboard . 152 UNIX_BP_NumberZombies_Warning situation 133 Managed system group dashboard ......152 UNIX_BP_PagingRate_Critical situation . 133 Situation Events dashboard.........154 UNIX_BP_SwapSpaceUsedPct_Critic situation 133 Situation event results dashboard.......155 UNIX_BP_SysWaitIOPct_Warning situation . 134 UNIX managed system dashboard ......157 UNIX_CPU_Busy_Critical situation
Recommended publications
  • Web Vmstat Any Distros, Especially Here’S Where Web Vmstat Comes Those Targeted at In

    Web Vmstat Any Distros, Especially Here’S Where Web Vmstat Comes Those Targeted at In

    FOSSPICKS Sparkling gems and new releases from the world of FOSSpicks Free and Open Source Software Mike Saunders has spent a decade mining the internet for free software treasures. Here’s the result of his latest haul… Shiny statistics in a browser Web VMStat any distros, especially Here’s where Web VMStat comes those targeted at in. It’s a system monitor that runs Madvanced users, ship an HTTP server, so you can connect with shiny system monitoring tools to it via a web browser and see on the desktop. Conky is one such fancy CSS-driven charts. Before you tool, while GKrellM was all the rage install it, you’ll need to get the in the last decade, and they are websocketd utility, which you can genuinely useful for keeping tabs find at https://github.com/ on your boxes, especially when joewalnes/websocketd. Helpfully, you’re an admin in charge of the developer has made pre- various servers. compiled executables available, so Now, pretty much all major you can just grab the 32-bit or distros include a useful command 64-bit tarball, extract it and there line tool for monitoring system you have it: websocketd. (Of course, Here’s the standard output for vmstat – not very interesting, right? resource usage: vmstat. Enter if you’re especially security vmstat 1 in a terminal window and conscious, you can compile it from copy the aforementioned you’ll see a regularly updating (once its source code.) websocketd into the same place. per second) bunch of statistics, Next, clone the Web VMStat Git Then just enter: showing CPU usage, free RAM, repository (or grab the Zip file and ./run swap usage and so forth.
  • 20 Linux System Monitoring Tools Every Sysadmin Should Know by Nixcraft on June 27, 2009 · 315 Comments · Last Updated November 6, 2012

    20 Linux System Monitoring Tools Every Sysadmin Should Know by Nixcraft on June 27, 2009 · 315 Comments · Last Updated November 6, 2012

    About Forum Howtos & FAQs Low graphics Shell Scripts RSS/Feed nixcraft - insight into linux admin work 20 Linux System Monitoring Tools Every SysAdmin Should Know by nixCraft on June 27, 2009 · 315 comments · Last updated November 6, 2012 Need to monitor Linux server performance? Try these built-in commands and a few add-on tools. Most Linux distributions are equipped with tons of monitoring. These tools provide metrics which can be used to get information about system activities. You can use these tools to find the possible causes of a performance problem. The commands discussed below are some of the most basic commands when it comes to system analysis and debugging server issues such as: 1. Finding out bottlenecks. 2. Disk (storage) bottlenecks. 3. CPU and memory bottlenecks. 4. Network bottlenecks. #1: top - Process Activity Command The top program provides a dynamic real-time view of a running system i.e. actual process activity. By default, it displays the most CPU-intensive tasks running on the server and updates the list every five seconds. Fig.01: Linux top command Commonly Used Hot Keys The top command provides several useful hot keys: Hot Usage Key t Displays summary information off and on. m Displays memory information off and on. Sorts the display by top consumers of various system resources. Useful for quick identification of performance- A hungry tasks on a system. f Enters an interactive configuration screen for top. Helpful for setting up top for a specific task. o Enables you to interactively select the ordering within top. r Issues renice command.
  • Oracle® Linux 7 Monitoring and Tuning the System

    Oracle® Linux 7 Monitoring and Tuning the System

    Oracle® Linux 7 Monitoring and Tuning the System F32306-03 October 2020 Oracle Legal Notices Copyright © 2020, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
  • Chapter 3. Booting Operating Systems

    Chapter 3. Booting Operating Systems

    Chapter 3. Booting Operating Systems Abstract: Chapter 3 provides a complete coverage on operating systems booting. It explains the booting principle and the booting sequence of various kinds of bootable devices. These include booting from floppy disk, hard disk, CDROM and USB drives. Instead of writing a customized booter to boot up only MTX, it shows how to develop booter programs to boot up real operating systems, such as Linux, from a variety of bootable devices. In particular, it shows how to boot up generic Linux bzImage kernels with initial ramdisk support. It is shown that the hard disk and CDROM booters developed in this book are comparable to GRUB and isolinux in performance. In addition, it demonstrates the booter programs by sample systems. 3.1. Booting Booting, which is short for bootstrap, refers to the process of loading an operating system image into computer memory and starting up the operating system. As such, it is the first step to run an operating system. Despite its importance and widespread interests among computer users, the subject of booting is rarely discussed in operating system books. Information on booting are usually scattered and, in most cases, incomplete. A systematic treatment of the booting process has been lacking. The purpose of this chapter is to try to fill this void. In this chapter, we shall discuss the booting principle and show how to write booter programs to boot up real operating systems. As one might expect, the booting process is highly machine dependent. To be more specific, we shall only consider the booting process of Intel x86 based PCs.
  • Performance, Scalability on the Server Side

    Performance, Scalability on the Server Side

    Performance, Scalability on the Server Side John VanDyk Presented at Des Moines Web Geeks 9/21/2009 Who is this guy? History • Apple // • Macintosh • Windows 3.1- Server 2008R2 • Digital Unix (Tru64) • Linux (primarily RHEL) • FreeBSD Systems Iʼve worked with over the years. Languages • Perl • Userland Frontier™ • Python • Java • Ruby • PHP Languages Iʼve worked with over the years (Userland Frontier™ʼs integrated language is UserTalk™) Open source developer since 2000 Perl/Python/PHP MySQL Apache Linux The LAMP stack. Time to Serve Request Number of Clients Performance vs. scalability. network in network out RAM CPU Storage These are the basic laws of physics. All bottlenecks are caused by one of these four resources. Disk-bound •To o l s •iostat •vmstat Determine if you are disk-bound by measuring throughput. vmstat (BSD) procs memory page disk faults cpu r b w avm fre flt re pi po fr sr tw0 in sy cs us sy id 0 2 0 799M 842M 27 0 0 0 12 0 23 344 2906 1549 1 1 98 3 3 0 869M 789M 5045 0 0 0 406 0 10 1311 17200 5301 12 4 84 3 5 0 923M 794M 5219 0 0 0 5178 0 27 1825 21496 6903 35 8 57 1 2 0 931M 784M 909 0 0 0 146 0 12 955 9157 3570 8 4 88 blocked plenty of RAM, idle processes no swapping CPUs A disk-bound FreeBSD machine. b = blocked for resources fr = pages freed/sec cs = context switches avm = active virtual pages in = interrupts flt = memory page faults sy = system calls per interval vmstat (RHEL5) # vmstat -S M 5 25 procs ---------memory-------- --swap- ---io--- --system- -----cpu------ r b swpd free buff cache si so bi bo in cs us sy id wa st 1 0 0 1301 194 5531 0 0 0 29 1454 2256 24 20 56 0 0 3 0 0 1257 194 5531 0 0 0 40 2087 2336 34 27 39 0 0 2 0 0 1183 194 5531 0 0 0 53 1658 2763 33 28 39 0 0 0 0 0 1344 194 5531 0 0 0 34 1807 2125 29 19 52 0 0 no blocked busy but not processes overloaded CPU in = interrupts/sec cs = context switches/sec wa = time waiting for I/O Solving disk bottlenecks • Separate spindles (logs and databases) • Get rid of atime updates! • Minimize writes • Move temp writes to /dev/shm Overview of what weʼre about to dive into.
  • Pingdirectory Administration Guide Version

    Pingdirectory Administration Guide Version

    Release 7.3.0.3 Server Administration Guide PingDirectory | Contents | ii Contents PingDirectory™ Product Documentation................................................ 20 Overview of the Server............................................................................. 20 Server Features.................................................................................................................................20 Administration Framework.................................................................................................................21 Server Tools Location....................................................................................................................... 22 Preparing Your Environment....................................................................22 Before You Begin.............................................................................................................................. 22 System requirements..............................................................................................................22 Installing Java......................................................................................................................... 23 Preparing the Operating System (Linux).......................................................................................... 24 Configuring the File Descriptor Limits.................................................................................... 24 File System Tuning.................................................................................................................25
  • Linux Performance Tools

    Linux Performance Tools

    Linux Performance Tools Brendan Gregg Senior Performance Architect Performance Engineering Team [email protected] @brendangregg This Tutorial • A tour of many Linux performance tools – To show you what can be done – With guidance for how to do it • This includes objectives, discussion, live demos – See the video of this tutorial Observability Benchmarking Tuning Stac Tuning • Massive AWS EC2 Linux cloud – 10s of thousands of cloud instances • FreeBSD for content delivery – ~33% of US Internet traffic at night • Over 50M subscribers – Recently launched in ANZ • Use Linux server tools as needed – After cloud monitoring (Atlas, etc.) and instance monitoring (Vector) tools Agenda • Methodologies • Tools • Tool Types: – Observability – Benchmarking – Tuning – Static • Profiling • Tracing Methodologies Methodologies • Objectives: – Recognize the Streetlight Anti-Method – Perform the Workload Characterization Method – Perform the USE Method – Learn how to start with the questions, before using tools – Be aware of other methodologies My system is slow… DEMO & DISCUSSION Methodologies • There are dozens of performance tools for Linux – Packages: sysstat, procps, coreutils, … – Commercial products • Methodologies can provide guidance for choosing and using tools effectively • A starting point, a process, and an ending point An#-Methodologies • The lack of a deliberate methodology… Street Light An<-Method 1. Pick observability tools that are: – Familiar – Found on the Internet – Found at random 2. Run tools 3. Look for obvious issues Drunk Man An<-Method • Tune things at random until the problem goes away Blame Someone Else An<-Method 1. Find a system or environment component you are not responsible for 2. Hypothesize that the issue is with that component 3. Redirect the issue to the responsible team 4.
  • Java Bytecode Manipulation Framework

    Java Bytecode Manipulation Framework

    Notice About this document The following copyright statements and licenses apply to software components that are distributed with various versions of the OnCommand Performance Manager products. Your product does not necessarily use all the software components referred to below. Where required, source code is published at the following location: ftp://ftp.netapp.com/frm-ntap/opensource/ 215-09632 _A0_ur001 -Copyright 2014 NetApp, Inc. All rights reserved. 1 Notice Copyrights and licenses The following component is subject to the ANTLR License • ANTLR, ANother Tool for Language Recognition - 2.7.6 © Copyright ANTLR / Terence Parr 2009 ANTLR License SOFTWARE RIGHTS ANTLR 1989-2004 Developed by Terence Parr Partially supported by University of San Francisco & jGuru.com We reserve no legal rights to the ANTLR--it is fully in the public domain. An individual or company may do whatever they wish with source code distributed with ANTLR or the code generated by ANTLR, including the incorporation of ANTLR, or its output, into commerical software. We encourage users to develop software with ANTLR. However, we do ask that credit is given to us for developing ANTLR. By "credit", we mean that if you use ANTLR or incorporate any source code into one of your programs (commercial product, research project, or otherwise) that you acknowledge this fact somewhere in the documentation, research report, etc... If you like ANTLR and have developed a nice tool with the output, please mention that you developed it using ANTLR. In addition, we ask that the headers remain intact in our source code. As long as these guidelines are kept, we expect to continue enhancing this system and expect to make other tools available as they are completed.
  • AIX Version 7.2: Performance Tools Guide and Reference About This Document

    AIX Version 7.2: Performance Tools Guide and Reference About This Document

    AIX Version 7.2 Performance Tools Guide and Reference IBM AIX Version 7.2 Performance Tools Guide and Reference IBM Note Before using this information and the product it supports, read the information in “Notices” on page 315. This edition applies to AIX Version 7.2 and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 2015, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document ......... v The procmon tool ............ 212 Highlighting .............. v Overview of the procmon tool....... 212 Case-sensitivity in AIX ........... v Components of the procmon tool...... 212 ISO 9000................ v Filtering processes........... 215 Performing AIX commands on processes ... 215 Performance Tools Guide and Reference 1 Profiling tools ............. 215 The timing commands ......... 215 What's new in Performance Tools Guide and The prof command .......... 216 Reference ............... 2 The gprof command .......... 217 CPU Utilization Reporting Tool (curt) ...... 2 The tprof command .......... 219 Syntax for the curt Command ....... 2 The svmon command .......... 226 Measurement and Sampling ........ 3 Security .............. 227 Examples of the curt command ....... 4 The svmon configuration file ....... 227 Simple performance lock analysis tool (splat) ... 32 Summary report metrics......... 227 splat command syntax.......... 32 Report formatting options ........ 228 Measurement and sampling ........ 33 Segment details and -O options ...... 230 Examples of generated reports ....... 35 Additional -O options ......... 234 Hardware performance monitor APIs and tools .. 50 Reports details ............ 238 Performance monitor accuracy ....... 51 Remote Statistics Interface API Overview .... 259 Performance monitor context and state .... 51 Remote Statistics Interface list of subroutines 260 Performance monitoring agent ......
  • How to Maintain Happy SAS® Users

    How to Maintain Happy SAS® Users

    NESUG 2007 Administration & Support How to Maintain Happy SAS ® Users Margaret Crevar, SAS Institute Inc., Cary, NC ABSTRACT Today’s SAS ® environment has high numbers of concurrent SAS processes and ever-growing data volumes. It is imperative to proactively manage system resources and performance to keep your SAS community productive and happy. We have found that ensuring your SAS applications have the proper computer resources is the best way to make sure your SAS users remain happy. INTRODUCTION There is one common thread when working with the IT administration staff at a SAS customer’s location with regard to what they can do to maintain happy SAS users, and that is to ensure that underlying hardware is properly configured to support the SAS applications. This is not a trivial task since different SAS applications need to have the hardware configured differently and depending on where you are with your understanding of how SAS will be used will help you evaluate options for the hardware, operating, and infrastructure (mid-tier) configuration. This is easier for existing SAS customers and more difficult with new SAS customers or new SAS applications at an existing SAS customer site. In this paper we will: • discuss briefly how SAS works, especially from an IO perspective • give some guidance on how to initially configure hardware for SAS usage • give some guidance on how to monitor the hardware to avoid running out of a computer resource • discuss if you should run all your SAS components under a single operating system or split them across multiple operating system This paper pulls together information that has been presented in recent SAS Global Forum and SUGI papers.
  • Nxadmin CLI Reference Guide Unity Iv Contents

    Nxadmin CLI Reference Guide Unity Iv Contents

    HYPER-UNIFIED STORAGE nxadmin Command Line Interface Reference Guide NEXSAN | 325 E. Hillcrest Drive, Suite #150 | Thousand Oaks, CA 91360 USA Printed Thursday, July 26, 2018 | www.nexsan.com Copyright © 2010—2018 Nexsan Technologies, Inc. All rights reserved. Trademarks Nexsan® is a trademark or registered trademark of Nexsan Technologies, Inc. The Nexsan logo is a registered trademark of Nexsan Technologies, Inc. All other trademarks and registered trademarks are the property of their respective owners. Patents This product is protected by one or more of the following patents, and other pending patent applications worldwide: United States patents US8,191,841, US8,120,922; United Kingdom patents GB2466535B, GB2467622B, GB2467404B, GB2296798B, GB2297636B About this document Unauthorized use, duplication, or modification of this document in whole or in part without the written consent of Nexsan Corporation is strictly prohibited. Nexsan Technologies, Inc. reserves the right to make changes to this manual, as well as the equipment and software described in this manual, at any time without notice. This manual may contain links to web sites that were current at the time of publication, but have since been moved or become inactive. It may also contain links to sites owned and operated by third parties. Nexsan is not responsible for the content of any such third-party site. Contents Contents Contents iii Chapter 1: Accessing the nxadmin and nxcmd CLIs 15 Connecting to the Unity Storage System using SSH 15 Prerequisite 15 Connecting to the Unity
  • SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4

    SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4

    SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4 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 http://www.suse.com/company/legal/ . All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a SUSE or Novell trademark; an asterisk (*) denotes a third party trademark. 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 xi 1 Available Documentation xii 2 Feedback xiv 3 Documentation Conventions xv I BASICS 1 1 General Notes on System Tuning 2 1.1 Be Sure What Problem to Solve 2 1.2 Rule Out Common Problems 3 1.3 Finding the Bottleneck 3 1.4 Step-by-step Tuning 4 II SYSTEM MONITORING 5 2 System Monitoring Utilities 6 2.1 Multi-Purpose Tools 6 vmstat 7