DOCSLIB.ORG

IBM Tivoli Monitoring: Linux OS Agent User's Guide Problem Classification

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM Tivoli Monitoring: Linux OS Agent User's Guide Problem Classification IBM Tivoli Monitoring Version 6.3 Linux OS Agent User's Guide SC22-5453-00 IBM Tivoli Monitoring Version 6.3 Linux OS Agent User's Guide SC22-5453-00 Note Before using this information and the product it supports, read the information in “Notices” on page 315. 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 Virtual Memory Statistics workspace ......23 Virtual Memory Usage Trends workspace ....24 Chapter 1. Using the monitoring agent . 1 New in this release ............1 Chapter 4. Attributes .........25 Using IBM Tivoli Monitoring .........3 Agent Availability Management Status attributes . 27 Components of the monitoring agent ......3 Agent Active Runtime Status attributes .....28 User interface options ...........4 Alerts Table attributes ...........29 All Users attributes ............30 Chapter 2. Requirements for the Configuration Information attributes ......31 monitoring agent ...........5 CPU attributes .............32 CPU attributes (superseded) .........33 Naming instances.............7 CPU Averages attributes ..........34 Running as a non-Administrator user ......7 CPU Averages attributes (superseded) .....36 Using Agent Management Services .......9 CPU Configuration attributes ........37 Filtering capabilities on the names of processes . 10 Disk attributes .............38 Disk attributes (superseded) .........39 Chapter 3. Workspaces........11 Disk IO attributes ............41 Organization of the predefined workspaces ....11 Disk IO attributes (superseded)........42 Agent Management Services workspace .....12 Disk Usage Trends attributes ........43 Agents' Management Log workspace ......12 Disk Usage Trends attributes (superseded) ....44 All Files workspace............13 File Comparison Group attributes .......46 Capacity Usage Information workspace .....13 File Information attributes .........46 CPU Averages workspace..........14 File Pattern Group attributes ........48 Disk I/O Extended Rate workspace ......14 I/O Ext attributes ............48 Disk I/O Rate workspace..........14 I/O Ext attributes (superseded)........50 Disk Usage workspace...........15 IP Address attributes ...........51 File Information workspace .........15 Linux Group attributes ..........52 Historical Summarized Availability workspace. 15 Linux Host Availability attributes .......52 Historical Summarized Availability Daily workspace 15 Linux TCP Statistics attributes ........53 Historical Summarized Availability Hourly LPAR attributes .............54 workspace ...............16 Machine Information attributes ........55 Historical Summarized Availability Weekly Network attributes ............56 workspace ...............16 Network attributes (superseded) .......60 Historical Summarized Capacity workspace . 16 NFS Statistics attributes ..........63 Historical Summarized Capacity Daily workspace 17 NFS Statistics attributes (superseded) ......68 Historical Summarized Capacity Hourly workspace 17 OS Configuration attributes .........72 Historical Summarized Capacity Weekly workspace 17 Process attributes ............73 Historical Summarized Performance workspace . 18 Process attributes (superseded) ........78 Historical Summarized Performance Daily Process User Info attributes .........82 workspace ...............18 Process User Info attributes (superseded) ....84 Historical Summarized Performance Hourly RPC Statistics attributes ..........86 workspace ...............18 RPC Statistics attributes (superseded)......87 Historical Summarized Performance Weekly Sockets Detail attributes ..........88 workspace ...............19 Sockets Detail attributes (superseded) .....90 Linux workspace ............19 Sockets Status attributes ..........91 Network workspace ...........19 Sockets Status attributes (superseded) .....91 NFS Statistics workspace ..........20 Swap Rate attributes ...........92 Process workspace ............20 Swap Rate attributes (superseded) .......93 Process CPU Usage workspace ........20 System Statistics attributes .........94 Process User Information workspace ......21 System Statistics attributes (superseded) .....96 RPC Statistics workspace ..........21 User Login attributes ...........98 Sockets Information workspace ........21 User Login attributes (superseded) ......98 Specific File Information workspace ......22 VM Stats attributes ............99 System Configuration workspace .......22 VM Stats attributes (superseded) .......102 System Information workspace ........22 Disk capacity planning for historical data ....103 Users Workspace ............23 © Copyright IBM Corp. 1994, 2013 iii Chapter 5. Situations ........107 AMS Start Agent Instance action .......121 Predefined situations ...........107 AMS Stop Agent action ..........122 Linux_AMS_Alert_Critical situation ......109 AMS Start Management action .......122 Linux_BP_AvgCpuBusyPct1h_Critic situation. 109 AMS Stop Management action .......123 Linux_BP_CpuBusyPct_Critical situation ....109 Sample_kill_Process action .........123 Linux_BP_CpuWaitIOPct_Warning situation . 110 Linux_BP_LoadAvg5min_Critical situation....110 Chapter 7. Policies .........125 Linux_BP_NetTotalErrPct_Warning situation . 110 Predefined policies ...........125 Linux_BP_NumberZombies_Warning situation . 110 Linux_BP_ProcHighCpu_Critical situation ....110 Chapter 8. Server dashboards ....127 Linux_BP_ProcMissing_Critical situation ....111 Server dashboards background information . 127 Linux_BP_SpaceUsedPct_Critical situation ....111 Checking the health of your monitored Linux_BP_SpaceUsedPctCustom_Cri situation . 111 environment..............130 Linux_BP_SwapSpaceUsedPct_Criti situation . 111 Displaying situation event results ......131 Linux_Fragmented_File_System situation ....111 Managed System Groups Overview dashboard . 132 Linux_Fragmented_File_System_2 situation . 112 Managed system group dashboard ......133 Linux_High_CPU_Overload situation .....112 Situation Events dashboard.........135 Linux_High_CPU_Overload_2 situation ....112 Situation event results dashboard.......136 Linux_High_CPU_System situation ......112 Linux managed system dashboard ......138 Linux_High_CPU_System_2 situation .....112 Page layout and controls .........140 Linux_High_Packet_Collisions situation ....112 Table controls .............141 Linux_High_Packet_Collisions_2 situation ....113 Copying the URL ............142 Linux_High_RPC_Retransmit situation .....113 Launching to the Tivoli Enterprise Portal ....142 Linux_High_RPC_Retransmit_2 situation ....113 Setting a trace .............143 Linux_High_Zombies situation .......113 Linux_High_Zombies_2 situation .......113 Chapter 9. Tivoli Common Reporting Linux_Low_Pct_Inodes situation .......113 Linux_Low_Pct_Inodes_2 situation ......114 for the monitoring agent ......145 Linux_Low_percent_space situation ......114 Utilization Details for Single Resource report . 150 Linux_Low_percent_space_2 situation .....114 Utilization Details for Multiple Resources report 153 Linux_Low_Space_Available situation .....114 Utilization Comparison for Single Resource report 156 Linux_Low_Space_Available_2 situation ....114 Utilization Comparison for Multiple Resources Linux_Network_Status situation .......114 report ................158 Linux_Network_Status_2 situation ......115 Utilization Heat Chart for Single Resource report 162 Linux_NFS_Buffer_High situation ......115 Memory Utilization for Single Resource report . 165 Linux_NFS_Buffer_High_2 situation ......115 Memory Utilization for Multiple Resources Linux_NFS_Getattr_High situation ......115 Comparison report ...........167 Linux_NFS_Getattr_High_2 situation .....115 Top Resources Utilization report .......169 Linux_NFS_rdlink_high situation .......115 Top Situations by Status report .......173 Linux_NFS_rdlink_high_2 situation ......116 Enterprise Resources List report .......174 Linux_NFS_Read_High situation .......116 Enterprise Daily Utilization Heat Chart report . 174 Linux_NFS_Read_High_2 situation ......116 Enterprise Summary report.........176 Linux_NFS_Writes_High situation ......116 Top Resources by Availability ........178 Linux_NFS_Writes_High_2 situation ......116 Top Resources Utilization Summary Heat Chart Linux_Packets_Error situation ........116 report ................180 Linux_Packets_Error_2 situation .......117 Top Resources by Availability (MTTR/MTBSI) . 182 Linux_Process_High_Cpu situation ......117 Resource Availability Comparison ......184 Linux_Process_High_Cpu_2 situation .....117 Availability Heat Chart for Single Resource . 186 Linux_Process_High_Instant_CPU situation . 117 CPU Utilization Comparison for Multiple Linux_Process_stopped situation .......117 Resources ..............188 Linux_Process_stopped_2 situation ......117 CPU Utilization for Single Resource ......191 Linux_RPC_Bad_Calls situation .......118 Disk Utilization for Single Resource ......192 Linux_RPC_Bad_Calls_2 situation ......118 Disk Utilization Comparison for Multiple Linux_System_Thrashing situation ......118 Resources ..............195 Linux_System_Thrashing_2 situation .....118 Situations History report .........198 Creating custom queries and reports .....200 Chapter 6. Take Action commands 119 Predefined Take Action commands ......119 Chapter 10. Troubleshooting .....207 AMS Recycle
Load more

Recommended publications
  • Kernel Boot-Time Tracing
    Kernel Boot-time Tracing Linux Plumbers Conference 2019 - Tracing Track Masami Hiramatsu <[email protected]> Linaro, Ltd. Speaker Masami Hiramatsu - Working for Linaro and Linaro members - Tech Lead for a Landing team - Maintainer of Kprobes and related tracing features/tools Why Kernel Boot-time Tracing? Debug and analyze boot time errors and performance issues - Measure performance statistics of kernel boot - Analyze driver init failure - Debug boot up process - Continuously tracing from boot time etc. What We Have There are already many ftrace options on kernel command line ● Setup options (trace_options=) ● Output to printk (tp_printk) ● Enable events (trace_events=) ● Enable tracers (ftrace=) ● Filtering (ftrace_filter=,ftrace_notrace=,ftrace_graph_filter=,ftrace_graph_notrace=) ● Add kprobe events (kprobe_events=) ● And other options (alloc_snapshot, traceoff_on_warning, ...) See Documentation/admin-guide/kernel-parameters.txt Example of Kernel Cmdline Parameters In grub.conf linux /boot/vmlinuz-5.1 root=UUID=5a026bbb-6a58-4c23-9814-5b1c99b82338 ro quiet splash tp_printk trace_options=”sym-addr” trace_clock=global ftrace_dump_on_oops trace_buf_size=1M trace_event=”initcall:*,irq:*,exceptions:*” kprobe_event=”p:kprobes/myevent foofunction $arg1 $arg2;p:kprobes/myevent2 barfunction %ax” What Issues? Size limitation ● kernel cmdline size is small (< 256bytes) ● A half of the cmdline is used for normal boot Only partial features supported ● ftrace has too complex features for single command line ● per-event filters/actions, instances, histograms. Solutions? 1. Use initramfs - Too late for kernel boot time tracing 2. Expand kernel cmdline - It is not easy to write down complex tracing options on bootloader (Single line options is too simple) 3. Reuse structured boot time data (Devicetree) - Well documented, structured data -> V1 & V2 series based on this. Boot-time Trace: V1 and V2 series V1 and V2 series posted at June.
    [Show full text]
  • Linux Perf Event Features and Overhead
    Linux perf event Features and Overhead 2013 FastPath Workshop Vince Weaver http://www.eece.maine.edu/∼vweaver [email protected] 21 April 2013 Performance Counters and Workload Optimized Systems • With processor speeds constant, cannot depend on Moore's Law to deliver increased performance • Code analysis and optimization can provide speedups in existing code on existing hardware • Systems with a single workload are best target for cross- stack hardware/kernel/application optimization • Hardware performance counters are the perfect tool for this type of optimization 1 Some Uses of Performance Counters • Traditional analysis and optimization • Finding architectural reasons for slowdown • Validating Simulators • Auto-tuning • Operating System optimization • Estimating power/energy in software 2 Linux and Performance Counters • Linux has become the operating system of choice in many domains • Runs most of the Top500 list (over 90%) on down to embedded devices (Android Phones) • Until recently had no easy access to hardware performance counters, limiting code analysis and optimization. 3 Linux Performance Counter History • oprofile { system-wide sampling profiler since 2002 • perfctr { widely used general interface available since 1999, required patching kernel • perfmon2 { another general interface, included in kernel for itanium, made generic, big push for kernel inclusion 4 Linux perf event • Developed in response to perfmon2 by Molnar and Gleixner in 2009 • Merged in 2.6.31 as \PCL" • Unusual design pushes most functionality into kernel
    [Show full text]
  • 24 Bringing Order to Chaos: Barrier-Enabled I/O Stack for Flash Storage
    Bringing Order to Chaos: Barrier-Enabled I/O Stack for Flash Storage YOUJIP WON and JOONTAEK OH, Hanyang University, Korea JAEMIN JUNG, Texas A&M University, USA GYEONGYEOL CHOI and SEONGBAE SON, Hanyang University, Korea JOOYOUNG HWANG and SANGYEUN CHO, Samsung Electronics, Korea This work is dedicated to eliminating the overhead required for guaranteeing the storage order in the modern IO stack. The existing block device adopts a prohibitively expensive approach in ensuring the storage order among write requests: interleaving the write requests with Transfer-and-Flush. For exploiting the cache bar- rier command for flash storage, we overhaul the IO scheduler, the dispatch module, and the filesystem sothat these layers are orchestrated to preserve the ordering condition imposed by the application with which the associated data blocks are made durable. The key ingredients of Barrier-Enabled IO stack are Epoch-based IO scheduling, Order-Preserving Dispatch,andDual-Mode Journaling. Barrier-enabled IO stack can control the storage order without Transfer-and-Flush overhead. We implement the barrier-enabled IO stack in server as well as in mobile platforms. SQLite performance increases by 270% and 75%, in server and in smartphone, respectively. In a server storage, BarrierFS brings as much as by 43× andby73× performance gain in MySQL and SQLite, respectively, against EXT4 via relaxing the durability of a transaction. CCS Concepts: • Software and its engineering → File systems management; Additional Key Words and Phrases: Filesystem, storage, block device, linux ACM Reference format: Youjip Won, Joontaek Oh, Jaemin Jung, Gyeongyeol Choi, Seongbae Son, Jooyoung Hwang, and Sangyeun Cho. 2018. Bringing Order to Chaos: Barrier-Enabled I/O Stack for Flash Storage.
    [Show full text]
  • Ein Wilder Ritt Distributionen
    09/2016 Besichtigungstour zu den skurrilsten Linux-Distributionen Titelthema Ein wilder Ritt Distributionen 28 Seit den frühen 90ern schießen die Linux-Distributionen wie Pilze aus dem Boden. Das Linux-Magazin blickt zurück auf ein paar besonders erstaunliche oder schräge Exemplare. Kristian Kißling www.linux-magazin.de © Antonio Oquias, 123RF Oquias, © Antonio Auch wenn die Syntax anderes vermu- samer Linux-Distributionen aufzustellen, Basis für Evil Entity denkt (Grün!), liegt ten lässt, steht der Name des klassischen denn in den zweieinhalb Jahrzehnten falsch. Tatsächlich basierte Evil Entity auf Linux-Tools »awk« nicht für Awkward kreuzte eine Menge von ihnen unseren Slackware und setzte auf einen eher düs- (zu Deutsch etwa „tolpatschig“), sondern Weg. Während einige davon noch putz- ter anmutenden Enlightenment-Desktop für die Namen seiner Autoren, nämlich munter in die Zukunft blicken, ist bei an- (Abbildung 3). Alfred Aho, Peter Weinberger und Brian deren nicht recht klar, welche Zielgruppe Als näher am Leben erwies sich der Fo- Kernighan. Kryptische Namen zu geben sie anpeilen oder ob sie überhaupt noch kus der Distribution, der auf dem Ab- sei eine lange etablierte Unix-Tradition, am Leben sind. spielen von Multimedia-Dateien lag – sie heißt es auf einer Seite des Debian-Wiki wollten doch nur Filme schauen. [1], die sich mit den Namen traditioneller Linux für Zombies Linux-Tools beschäftigt. Je kaputter, desto besser Denn, steht dort weiter, häufig halten Apropos untot: Die passende Linux- Entwickler die Namen ihrer Tools für Distribution für Zombies ließ sich recht Auch Void Linux [4], der Name steht selbsterklärend oder sie glauben, dass einfach ermitteln. Sie heißt Undead Linux je nach Übersetzung für „gleichgültig“ sie die User ohnehin nicht interessieren.
    [Show full text]
  • Linux on IBM Z
    Linux on IBM Z Pervasive Encryption with Linux on IBM Z: from a performance perspective Danijel Soldo Software Performance Analyst Linux on IBM Z Performance Evaluation _ [email protected] IBM Z / Danijel Soldo – Pervasive Encryption with Linux on IBM Z: from a performance perspective / © 2018 IBM Corporation Notices and disclaimers • © 2018 International Business Machines Corporation. No part of • Performance data contained herein was generally obtained in a this document may be reproduced or transmitted in any form controlled, isolated environments. Customer examples are without written permission from IBM. presented as illustrations of how those • U.S. Government Users Restricted Rights — use, duplication • customers have used IBM products and the results they may have or disclosure restricted by GSA ADP Schedule Contract with achieved. Actual performance, cost, savings or other results in IBM. other operating environments may vary. • Information in these presentations (including information relating • References in this document to IBM products, programs, or to products that have not yet been announced by IBM) has been services does not imply that IBM intends to make such products, reviewed for accuracy as of the date of initial publication programs or services available in all countries in which and could include unintentional technical or typographical IBM operates or does business. errors. IBM shall have no responsibility to update this information. This document is distributed “as is” without any warranty, • Workshops, sessions and associated materials may have been either express or implied. In no event, shall IBM be liable for prepared by independent session speakers, and do not necessarily any damage arising from the use of this information, reflect the views of IBM.
    [Show full text]
  • 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.
    [Show full text]
  • On Access Control Model of Linux Native Performance Monitoring Motivation
    On access control model of Linux native performance monitoring Motivation • socialize Perf access control management to broader community • promote the management to security sensitive production environments • discover demand on extensions to the existing Perf access control model 2 Model overview • Subjects: processes • Access control: • superuser root • LSM hooks for MAC (e.g. SELinux) subjects • privileged user groups • Linux capabilities (DAC) • unprivileged users • perf_event_paranoid sysctl access and • Objects: telemetry data • Resource control: • tracepoints, OS events resource control • CPU time: sample rate & throttling • CPU • Memory: perf_events_mlock_kb sysctl • Uncore Objects • Other HW • File descriptors: ulimit -n (RLIMIT_NOFILE) system • Scope • Level user cgroups • process • user mode • cgroups • kernel kernel • system process • hypervisor hypervisor 3 Subjects Users • root, superuser: • euid = 0 and/or CAP_SYS_ADMIN • unprivileged users: • perf_event_paranoid sysctl • Perf privileged user group: -rwxr-x--- 2 root perf_users 11M Oct 19 15:12 perf # getcap perf perf = cap_perfmon,…=ep root unprivileged Perf users 4 Telemetry, scope, level Telemetr Objects: SW, HW telemetry data y Uncore • tracepoints, OS events, eBPF • CPUs events and related HW CPU • Uncore events (LLC, Interconnect, DRAM) SW events • Other (e.g. FPGA) process cgroup user Scope: Level: system kernel • process • user hypervisor • cgroups • kernel Scope Leve • system wide • hypervisor l 5 perf: interrupt took too long (3000 > 2000), lowering kernel.perf_event_max_sample_rate
    [Show full text]
  • Enabling Virtualization Technologies for Enhanced Cloud Computing
    New Jersey Institute of Technology Digital Commons @ NJIT Dissertations Electronic Theses and Dissertations Fall 1-31-2015 Enabling virtualization technologies for enhanced cloud computing Kashifuddin Qazi New Jersey Institute of Technology Follow this and additional works at: https://digitalcommons.njit.edu/dissertations Part of the Computer Sciences Commons Recommended Citation Qazi, Kashifuddin, "Enabling virtualization technologies for enhanced cloud computing" (2015). Dissertations. 106. https://digitalcommons.njit.edu/dissertations/106 This Dissertation is brought to you for free and open access by the Electronic Theses and Dissertations at Digital Commons @ NJIT. It has been accepted for inclusion in Dissertations by an authorized administrator of Digital Commons @ NJIT. For more information, please contact [email protected]. Copyright Warning & Restrictions The copyright law of the United States (Title 17, United States Code) governs the making of photocopies or other reproductions of copyrighted material. Under certain conditions specified in the law, libraries and archives are authorized to furnish a photocopy or other reproduction. One of these specified conditions is that the photocopy or reproduction is not to be “used for any purpose other than private study, scholarship, or research.” If a, user makes a request for, or later uses, a photocopy or reproduction for purposes in excess of “fair use” that user may be liable for copyright infringement, This institution reserves the right to refuse to accept a copying order
    [Show full text]
  • Kernel Runtime Security Instrumentation Process Is Executed
    Kernel Runtime Security Instrumentation KP Singh Linux Plumbers Conference Motivation Security Signals Mitigation Audit SELinux, Apparmor (LSMs) Perf seccomp Correlation with It's bad, stop it! maliciousness but do not imply it Adding a new Signal Signals Mitigation Update Audit Audit (user/kernel) SELinux, Apparmor (LSMs) to log environment Perf variables seccomp Security Signals Mitigation Audit SELinux, Apparmor (LSMs) Perf seccomp Update the mitigation logic for a malicious actor with a known LD_PRELOAD signature Signals ● A process that executes and deletes its own executable. ● A Kernel module that loads and "hides" itself ● "Suspicious" environment variables. Mitigations ● Prevent mounting of USB drives on servers. ● Dynamic whitelist of known Kernel modules. ● Prevent known vulnerable binaries from running. How does it work? Why LSM? ● Mapping to security behaviours rather than the API. ● Easy to miss if instrumenting using syscalls (eg. execve, execveat) ● Benefit the LSM ecosystem by incorporating feedback from the security community. Run my code when a Kernel Runtime Security Instrumentation process is executed /sys/kernel/security/krsi/process_execution my_bpf_prog.o (bprm_check_security) bpf [BPF_PROG_LOAD] open [O_RDWR] securityfs_fd prog_fd bpf [BPF_PROG_ATTACH] LSM:bprm_check_security (when a process is executed) KRSI's Hook Other LSM Hooks Tying it all Together Reads events from the buffer and processes them Userspace further Daemon/Agent User Space Buffer Kernel Space eBPF programs output to a buffer process_execution
    [Show full text]
  • Implementing SCADA Security Policies Via Security-Enhanced Linux
    Implementing SCADA Security Policies via Security-Enhanced Linux Ryan Bradetich Schweitzer Engineering Laboratories, Inc. Paul Oman University of Idaho, Department of Computer Science Presented at the 10th Annual Western Power Delivery Automation Conference Spokane, Washington April 8–10, 2008 1 Implementing SCADA Security Policies via Security-Enhanced Linux Ryan Bradetich, Schweitzer Engineering Laboratories, Inc. Paul Oman, University of Idaho, Department of Computer Science Abstract—Substation networks have traditionally been and corporate IT networks are also fundamentally different. isolated from corporate information technology (IT) networks. SCADA protocols provide efficient, deterministic communi- Hence, the security of substation networks has depended heavily cations between devices [3] [4]. Corporate IT protocols upon limited access points and the use of point-to-point supervisory control and data acquisition (SCADA)-specific generally provide reliable communications over a shared protocols. With the introduction of Ethernet into substations, communications channel. pressure to reduce expenses and provide Internet services to Security-Enhanced Linux was initially developed by the customers has many utilities connecting their substation National Security Agency to introduce a mandatory access networks and corporate IT networks, despite the additional control (MAC) solution into the Linux® kernel [5]. The security risks. The Security-Enhanced Linux SCADA proxy was original proof-of-concept Security-Enhanced Linux SCADA introduced
    [Show full text]
  • Heterogeneous Clusters.Pdf
    HowTo Heterogeneous Clusters Running ClusterKnoppix as a master node to a CHAOS drone army HowTo Heterogeneous Clusters Running ClusterKnoppix as a master node to a CHAOS drone army CONTROL PAGE Document Approvals Approved for Publication: Author Name: Ian Latter 12 December 2003 Document Control Document Name: Heterogeneous Clusters; Running ClusterKnoppix as a master node to a CHAOS drone army Document ID: howto - heterogenous clusters.doc-Release-1.1(467) Distribution: Unrestricted Distribution Status: Release Disk File: C:\Documents and Settings\_.NULL\Desktop\whitepaper\HowTo - Heterogenous Clusters.doc Copyright: Copyright 2003, Macquarie University Version Date Release Information Author/s 1.1 12-Dec-03 Release / Unrestricted Distribution Ian Latter 1.0 11-Dec-03 Draft / Uncontrolled Ian Latter Distribution Version Release to 1.1 Public Release 1.0 Macquarie University, Moshe Bar, Bruce Knox, Wim Vandersmissen Unrestricted Distribution Copyright 2003, Macquarie University Page 2 of 13 HowTo Heterogeneous Clusters Running ClusterKnoppix as a master node to a CHAOS drone army Table of Contents 1 OVERVIEW..................................................................................................................................4 2 WHY YOU WANT A HETEROGENEOUS CLUSTER ..........................................................5 2.1 WHERE APPLICATIONS LIVE ...................................................................................................5 2.2 OPTIMIZING CLUSTER ADMINISTRATION ................................................................................5
    [Show full text]
  • Embedded Linux Conference Europe 2019
    Embedded Linux Conference Europe 2019 Linux kernel debugging: going beyond printk messages Embedded Labworks By Sergio Prado. São Paulo, October 2019 ® Copyright Embedded Labworks 2004-2019. All rights reserved. Embedded Labworks ABOUT THIS DOCUMENT ✗ This document is available under Creative Commons BY- SA 4.0. https://creativecommons.org/licenses/by-sa/4.0/ ✗ The source code of this document is available at: https://e-labworks.com/talks/elce2019 Embedded Labworks $ WHOAMI ✗ Embedded software developer for more than 20 years. ✗ Principal Engineer of Embedded Labworks, a company specialized in the development of software projects and BSPs for embedded systems. https://e-labworks.com/en/ ✗ Active in the embedded systems community in Brazil, creator of the website Embarcados and blogger (Portuguese language). https://sergioprado.org ✗ Contributor of several open source projects, including Buildroot, Yocto Project and the Linux kernel. Embedded Labworks THIS TALK IS NOT ABOUT... ✗ printk and all related functions and features (pr_ and dev_ family of functions, dynamic debug, etc). ✗ Static analysis tools and fuzzing (sparse, smatch, coccinelle, coverity, trinity, syzkaller, syzbot, etc). ✗ User space debugging. ✗ This is also not a tutorial! We will talk about a lot of tools and techniches and have fun with some demos! Embedded Labworks DEBUGGING STEP-BY-STEP 1. Understand the problem. 2. Reproduce the problem. 3. Identify the source of the problem. 4. Fix the problem. 5. Fixed? If so, celebrate! If not, go back to step 1. Embedded Labworks TYPES OF PROBLEMS ✗ We can consider as the top 5 types of problems in software: ✗ Crash. ✗ Lockup. ✗ Logic/implementation error. ✗ Resource leak. ✗ Performance.
    [Show full text]