Automated IT Service Fault Diagnosis Based on Event Correlation Techniques

Total Page:16

File Type:pdf, Size:1020Kb

Automated IT Service Fault Diagnosis Based on Event Correlation Techniques Automated IT Service Fault Diagnosis Based on Event Correlation Techniques Dissertation an der Fakultat¨ fur¨ Mathematik, Informatik und Statistik der Ludwig-Maximilians-Universitat¨ Munchen¨ vorgelegt von Andreas Hanemann Tag der Einreichung: 22. Mai 2007 1. Berichterstatter: Professor Dr. Heinz-Gerd Hegering, Ludwig-Maximilians-Universit¨at M¨unchen 2. Berichterstatterin: Professor Dr. Gabrijela Dreo Rodosek, Universit¨at der Bundeswehr M¨unchen Automated IT Service Fault Diagnosis Based on Event Correlation Techniques Dissertation an der Fakultat¨ fur¨ Mathematik, Informatik und Statistik der Ludwig-Maximilians-Universitat¨ Munchen¨ vorgelegt von Andreas Hanemann Tag der Einreichung: 22. Mai 2007 Tag der m¨undlichen Pr¨ufung: 19. Juli 2007 1. Berichterstatter: Professor Dr. Heinz-Gerd Hegering, Ludwig-Maximilians-Universit¨at M¨unchen 2. Berichterstatterin: Professor Dr. Gabrijela Dreo Rodosek, Universit¨at der Bundeswehr M¨unchen Acknowledgments This thesis has been written as part of my work as a researcher at the Leib- niz Supercomputing Center (Leibniz-Rechenzentrum, LRZ) of the Bavarian Academy of Sciences and Humanities which was funded by the German Re- search Network (DFN-Verein) as well as in cooperation with the research group of Prof. Dr. Heinz-Gerd Hegering. Apart from the LRZ, this research group called MNM-Team (Munich Network Management Team) is located at the University of Munich (LMU), the Munich University of Technology (TUM) and the University of Federal Armed Forces in Munich. At first, I would like to thank my doctoral advisor Prof. Dr. Heinz-Gerd Hegering for his constant support and helpful advice during the whole prepa- ration time of this thesis. I would also like to express my special gratefulness to my second advisor, Prof. Dr. Gabi Dreo Rodosek, for giving me advice on finding an appropriate research matter for the thesis and also for many discussions about the thesis structure and contents. At the LRZ I would like to thank my supervisors Dr. Victor Apostolescu and Dr. Helmut Reiser for giving me the opportunity to integrate the work on the PhD thesis into the work on our network monitoring project. The meetings of the MNM Team have been an important possibilityfor me to present and discuss the status of my thesis with other researchers. In this con- text, I would like to thank Timo Baur, Latifa Boursas, Michael Brenner, Dr. Thomas Buchholz, Vitalian Danciu, Nils Otto vor dem gentschen Felde, Dr. Markus Garschhammer, Matthias Hamm, Iris Hochstatter, Wolfgang Hom- mel, Dr. Bernhard Kempter, Ralf K¨onig, Silvia Knittl, Annette Kostelezky, Dr. Michael Krause, Feng Liu, Dr. Harald R¨olle, Thomas Schaaf, Michael Schiffers, Georg Treu, and Mark Yampolskiy. In particular, I would like to thank David Schmitz and Martin Sailer (both also being members of the MNM Team) who have pursued related research directions for many valuable discussions. The outcome of some student work which I have supervised also has been helpful for the thesis preparation. Therefore, I would like to thank Dirk Bern- sau, Hans Beyer, Marta Galochino, Patricia Marcu, and Martin Roll for their efforts. At the LRZ I would like to thank Dr. Eberhard Hahn, Dr. Ulrike Kirchgesser, Klaus Natterer, Gudrun Sch¨ofer, Werner Spirk, and Michael Storz for infor- mation about the example services. Last but not least, I would like to express my gratitude to Karl-Heinz Geisler for improving the language quality of the thesis and my parents for their sup- port prior and during the thesis preparation. Munich, May 2007 This work was supported in part by the EC IST-EMANICS Network of Excellence (#26854). Summary In the previous years a paradigm shift in the area of IT service management could be witnessed. IT management does not only deal with the network, end systems, or applications anymore, but is more and more concerned with IT services. This is caused by the need of organizations to monitor the efficiency of internal IT departments and to have the possibility to subscribe IT services from external providers. This trend has raised new challenges in the area of IT service management, especially with respect to service level agreements lay- ing down the quality of service to be guaranteed by a service provider. Fault management is also facing new challenges which are related to ensuring the compliance to these service level agreements. For example, a high utilization of network links in the infrastructure can imply a delay increase in the de- livery of services with respect to agreed time constraints. Such relationships have to be detected and treated in a service-oriented fault diagnosis which therefore does not deal with faults in a narrow sense, but with service quality degradations. This thesis aims at providing a concept for service fault diagnosis which is an important part of IT service fault management. At first, a motivation of the need of further examinations regarding this issue is given which is based on the analysis of services offered by a large IT service provider. A gener- alization of the scenario forms the basis for the specification of requirements which are used for a review of related research work and commercial prod- ucts. Even though some solutions for particular challenges have already been provided, a general approach for service fault diagnosis is still missing. For addressing this issue, a framework is presented in the main part of this thesis using an event correlation component as its central part. Event correlation techniques which have been successfully applied to fault management in the area of network and systems management are adapted and extended accord- ingly. Guidelines for the application of the framework to a given scenario are provided afterwards. For showing their feasibility in a real world scenario, they are used for both example services referenced earlier. Kurzfassung In den letzten Jahren war im Bereich des IT-Managements ein Paradigmen- wechsel zu beobachten. Hierbei geht es in zunehmendem Maße nicht mehr um das reine Management von Netzen, Endsystemen oder Applikationen, sondern um das Management von IT-Diensten. Dieses ist dadurch bedingt, dass Organisationen die Leistungen interner IT-Abteilungen ¨uberpr¨ufbarer machen sowie den Einkauf extern erbrachter IT-Dienste von Dienstanbietern erm¨oglichen m¨ochten. Hieraus ergeben sich neue Anforderungen an das IT- Management, insbesondere im Zusammenhang mit Dienstvereinbarungen, die die durch einen Dienstleister zu erbringende Dienstqualit¨at festlegen. Auch im Bereich des Fehlermanagements ergeben sich neue Fragestellungen im Zusammenhang mit diesen Dienstvereinbarungen. Beispielsweise kann eine hohe Auslastung von Verbindungen in der Netzinfrastruktur zu einem Anstieg der Verz¨ogerung bei der Erbringung von Diensten f¨uhren, was im Hinblick auf vereinbarte Zeitbedingungen betrachtet werden muss. Solche Zusammenh¨ange m¨ussen erkannt und in einer dienstorientierten Fehlerdiag- nose behandelt werden, die sich daher nicht mehr mit Fehlern im engeren Sinne, sondern mit Verminderungen der Dienstqualit¨at befasst. In dieser Arbeit geht es um ein Konzept zur Diagnose von Fehlern bei der Erbringung von IT-Diensten, was einen Teil des Fehlermanagements f¨ur IT- Dienste darstellt. Zun¨achst wird eine Motivation der Notwendigkeit von weiteren Untersuchungen in diesem Bereich gegeben, die auf der Analyse von IT-Diensten, die im Umfeld eines großen IT-Dienstleisters angeboten werden, beruht. Eine Verallgemeinerung des Szenarios dient als Grundlage f¨ur die Festlegung von Anforderungen, die im weiteren f¨ur die Bewertung von verwandten Forschungsarbeiten und kommerziellen Produkten verwen- det werden. Obwohl einige bisherige Arbeiten L¨osungen f¨ur Teilaspekte der Fragestellung bieten, wird deutlich, dass ein allgemeiner Ansatz zur Dienst- fehlerdiagnose bislang fehlt. Im Hauptteil der Arbeit wird hierzu ein Rah- menwerk vorgestellt, als dessen zentrale Komponente ein Ereigniskorrela- tor eingesetzt wird. Ereigniskorrelationstechniken, die bisher erfolgreich auf der Netz- und Systemmanagementebene eingesetzt wurden, werden hierf¨ur entsprechend angepasst und erweitert. Empfehlungen zur Anpassung des Rahmenwerks an ein gegebenes Dienstszenario werden im folgenden zur Verf¨ugung gestellt. Um deren Nutzen in einem realen Szenario deutlich zu machen, werden diese f¨ur die beiden vorher dargestellten Beispieldienste angewendet. CONTENTS 1 Introduction 1 1.1 ResearchIssue ......................... 3 1.2 Deficits of Today’s IT Service Fault Management . 5 1.3 ThesisOutline.......................... 6 2 Requirements 9 2.1 DefinitionofTerms . .. .. .. .. .. .. 10 2.2 Service Management Scenario at the Leibniz Supercomputing Center.............................. 15 2.3 GenericScenarioforServiceFaultDiagnosis . 24 2.4 RequirementsDerivation . 26 2.5 Summary ............................ 35 3 Related Work 37 3.1 ITProcessManagementFrameworks. 39 3.2 ServiceandResourceModeling . 55 3.3 FaultManagementInterfaces . 61 3.4 FaultManagementTechniques . 69 3.5 SLAManagement........................ 91 3.6 Summary ............................ 99 4 Framework for Service-Oriented Event Correlation 105 4.1 Motivation for Service-Oriented Event Correlation . .107 I Contents 4.2 RefinementoftheRequirements . .108 4.3 EventCorrelationWorkflow . .110 4.4 EventCorrelationFramework. .124 4.5 HybridEventCorrelationArchitecture . 129 4.6 InformationModelingandManagement . 155 4.7 AssessmentMetricsforaGivenScenario . 174 4.8 CollaborationwithImpactAnalysis . .175 4.9 Assessment ...........................176
Recommended publications
  • Linux Administrators Security Guide LASG - 0.1.1
    Linux Administrators Security Guide LASG - 0.1.1 By Kurt Seifried ([email protected]) copyright 1999, All rights reserved. Available at: https://www.seifried.org/lasg/. This document is free for most non commercial uses, the license follows the table of contents, please read it if you have any concerns. If you have any questions email [email protected]. A mailing list is available, send an email to [email protected], with "subscribe lasg-announce" in the body (no quotes) and you will be automatically added. 1 Table of contents License Preface Forward by the author Contributing What this guide is and isn't How to determine what to secure and how to secure it Safe installation of Linux Choosing your install media It ain't over 'til... General concepts, server verses workstations, etc Physical / Boot security Physical access The computer BIOS LILO The Linux kernel Upgrading and compiling the kernel Kernel versions Administrative tools Access Telnet SSH LSH REXEC NSH Slush SSL Telnet Fsh secsh Local YaST sudo Super Remote Webmin Linuxconf COAS 2 System Files /etc/passwd /etc/shadow /etc/groups /etc/gshadow /etc/login.defs /etc/shells /etc/securetty Log files and other forms of monitoring General log security sysklogd / klogd secure-syslog next generation syslog Log monitoring logcheck colorlogs WOTS swatch Kernel logging auditd Shell logging bash Shadow passwords Cracking passwords John the ripper Crack Saltine cracker VCU PAM Software Management RPM dpkg tarballs / tgz Checking file integrity RPM dpkg PGP MD5 Automatic
    [Show full text]
  • Ticketing Systems with RT
    Ticketing Systems with RT Network Startup Resource Center www.nsrc.org These materials are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license (http://creativecommons.org/licenses/by-nc/4.0/) Typical Support Scenario • Lots of email traffic requesting help, request for services, etc • Archived as text without classification • Very difficult to find current status or problem history • Sometimes problems were forgotten or never resolved • Difficult for another person to follow up on a problem that someone else started dealing with Why Ticketing Systems? Ticketing Systems Why are they important? • Track all events, failures and issues • Focal point for help desk communication Use it to track all communications • Both internal and external Events originating from the outside: • customer complaints Events originating from the inside: • System outages (direct or indirect) • Planned maintenance, upgrades, etc. Ticketing Systems (Contd.) • Use a ticket system to follow cases, including communication between the support staff • Each case is considered a ticket • Each ticket has a ticket number • Each ticket goes through a similar life cycle: • New – Open – … – Resolved Help Request with Tickets Request Tracker / Trac RT • Heavily used worldwide • Can be customized to your location • Somewhat difficult to install and configure • Handles large-scale operations • A hybrid including wiki & project management features • Web-only ticket system works well but not robust as RT • Often used for ”trac”king group projects.
    [Show full text]
  • OTRS Asterisk PBX Integration Module PIM V2.0.0B Administrator's
    OTRS Asterisk PBX Integration Module PIM v2.0.0b Administrator's Guide 2019 © IP-LAB.RU Contents Introduction .................................................................................................................................................. 3 Preparing Asterisk PBX for integration with OTRS ........................................................................................ 4 Install the PIM package on the OTRS server ................................................................................................. 5 Configuring the PIMv2.0.0b module ............................................................................................................. 6 Definition of "Tracking number" ................................................................................................................... 8 Setting agent extensions ............................................................................................................................... 9 Assign agent extensions to the "Tracking Number" ................................................................................... 10 Customer User identification ...................................................................................................................... 11 CallerID modification ................................................................................................................................... 11 Starting the service ....................................................................................................................................
    [Show full text]
  • Onapp Admin Guide
    2.0 Admin Guide 2.0 Admin Guide Contents 0. About This Guide ............................................................................................... 5 1. OnApp Overview ................................................................................................ 6 1.1 Servers ................................................................................................................... 6 1.2 Networks ................................................................................................................ 7 1.3 Templates .............................................................................................................. 8 1.4 Virtual Machines .................................................................................................... 8 1.5 Scalability .............................................................................................................. 8 1.6 Availability and Reliability .................................................................................... 8 1.7 Security .................................................................................................................. 9 1.8 API and Integration ............................................................................................... 9 2. OnApp Hardware & Software Requirements ................................................. 10 2.1 Hypervisor Servers ............................................................................................. 10 2.2 Control Panel Server ..........................................................................................
    [Show full text]
  • Ispmail Tutorial for Debian Lenny
    6.10.2015 ISPmail tutorial for Debian Lenny ISPmail tutorial for Debian Lenny Add new comment 223533 reads This tutorial is for the former stable version "Debian Lenny". If you are using "Debian Squeeze" then please follow the new tutorial. A spanish translation of this tutorial is also available ­ courtesy of José Ramón Magán Iglesias. What this tutorial is about You surely know the internet service providers that allow you to rent a domain and use it to receive emails. If you have a computer running Debian which is connected to the internet permanently you can do that yourself. You do not even need to have a fixed IP address thanks to dynamic DNS services like dyndns.org. All you need is this document, a cup of tea and a little time. When you are done your server will be able to... receive and store emails for your users from other mail servers let your users retrieve the email through IMAP and POP3 ­ even with SSL to encrypt to connection receive and forward ("relay") email for your users if they are authenticated offer a webmail interface to read emails in a web browser detect most spam emails and filter them out or tag them License/Copyright This tutorial book is copyrighted 2009 Christoph Haas (email@christoph­haas.de). It can be used freely under the terms of the GNU General Public License. Don't forget to refer to this URL when using it. Thank you. Changelog 17.6.09: Lenny tutorial gets published. 19.6.09: The page on SPF checks is temporarily offline.
    [Show full text]
  • Projeto Final
    UNIVERSIDADE CATÓLICA DE BRASÍLIA PRÓ-REITORIA DE GRADUAÇÃO TRABALHO DE CONCLUSÃO DE CURSO Bacharelado em Ciência da Computação e Sistemas de Informação CRIAÇÃO DE UM CORREIO ELETRÔNICO CORPORATIVO COM POSTFIX Autores: Davi Eduardo R. Domingues Luiz Carlos G. P. C. Branco Rafael Bispo Silva Orientador: MSc. Eduardo Lobo BRASÍLIA 2007 Criação de um Servidor de Correio Eletrônico Corporativo com Postfix 2 / 111 DAVI EDUARDO R. DOMINGUES LUIZ CARLOS G. P. C. BRANCO RAFAEL BISPO SILVA CRIAÇÃO DE UM SERVIDOR DE CORREIO ELETRÔNICO CORPORATIVO COM POSTFIX Monografia apresentada ao Programa de Graduação da Universidade Católica de Brasília, como requisito para obtenção do Título de Bacharelado em Ciência da Computação. Orientador: MSc. Eduardo Lobo Brasília 2007 Criação de um Servidor de Correio Eletrônico Corporativo com Postfix 3 / 111 TERMO DE APROVAÇÃO Dissertação defendida e aprovada como requisito parcial para obtenção do Título de Bacharel em Ciência da Computação, defendida e aprovada, em 05 de dezembro de 2007, pela banca examinadora constituída por: _______________________________________________________ Professor Eduardo Lobo – Orientador do Projeto _______________________________________________________ Professor Mário de Oliveira Braga Filho – Membro Interno _______________________________________________________ Professor Giovanni – Membro Interno Brasília UCB Criação de um Servidor de Correio Eletrônico Corporativo com Postfix 4 / 111 Dedico este trabalho primeiramente a Deus que me deu a vida e paciência para chegar a este nível de estudo que me encontro. Em especial a minha mãe que acreditou em mim, aos bons valores que me ensinou e pelo apoio a toda minha vida acadêmica e me compreendeu pelos momentos de ausência ao seu lado. Davi Eduardo R. Domingues Criação de um Servidor de Correio Eletrônico Corporativo com Postfix 5 / 111 Dedico a minha família que sempre acreditou em mim, também aos meus grandes amigos e aos grandes amigos que se foram, aqueles que nos deixam saudades e uma vontade de continuar seus trabalhos.
    [Show full text]
  • An E-Mail Quarantine with Open Source Software
    An e-mail quarantine with open source software Using amavis, qpsmtpd and MariaDB for e-mail filtering Daniel Knittel Dirk Jahnke-Zumbusch HEPiX fall 2016 NERSC, Lawrence Berkeley National Laboratory United States of America October 2016 e-mail services at DESY > DESY is hosting 70+ e-mail domains, most prominent: ▪ desy.de — of course :) ▪ xfel.eu — European XFEL ▪ belle2.org — since summer 2016 ▪ cfel.de — Center for Free-Electron Laser Science ▪ cssb-hamburg.de — Center for Structural Systems Biology > mixed environment of open source software and commercial products ▪ Zimbra network edition with web access and standard clients (Outlook, IMAP, SMTP) ▪ Postfix for MTAs ▪ SYMPA for mailing list services ▪ Sophos and Clearswift‘s MIMEsweeper for SMTP > currently ~6.500 fully-fledged mailboxes, some 1000s extra with reduced functionality (e.g. no Outlook/ActiveSync/EWS access) > daily ~300.000 delivered e-mails 2 DESY e-mail infrastructure 1b 3 4 1 2 5 > 1 DMZ filtering ▪ restrictive filtering, reject e-mails from very suspicious MTAs ▪ 1b soon: DESY’s NREN (DFN) will be integrated into e-mail flow with virus- and SPAM-scanning > 2 filter for bad content ➔ suspicious e-mails into quarantine > 3 2nd-level SPAM-scan based on mail text and own rules > 4 distribution of e-mails to mailbox servers, mailing list servers or DESY-external destinations > 5 throttling of e-mail flow to acceptable rates (individual vs. newsletter) ▪ think “phishing” ➔ high rates trigger an alarm > mixed HW/VM environment 3 e-mail at DESY – attachment filtering & quarantine > policy: e-mail traffic is filtered ▪ block “bad” e-mails in the first place ➔ viruses are blocked ➔ executable content is blocked ▪ also block e-mails originating from DESY if they contain malicious or suspicious content ▪ up to now: commercial solution > additional measures ▪ mark e-mails with a high SPAM-score (2nd-level SPAM-filtering) ▪ monitor outgoing e-mail-flow ▪ throttle if over a specific rate ➔ this is sender-specific and customizable (e.g.
    [Show full text]
  • Scott E. Harney
    Scott E. Harney 1425 Melpomene St., New Orleans, LA 70130 504-298-UNIX scotth@scottharney. com Summary Highly motivated systems engineer with a broad background building and managing 24/7/365 Enterprise and service provider environments with a focus on getting the job done for customers. I am a self starter with a broad and deep understanding of a variety of technologies and how they can best be assembled to support business needs. I can handle multiple simultaneous projects from design through implementation to operational phases. Technologies • Operating Systems: Linux (Debian/Ubuntu, RedHat, Slackware, SuSe, CoreOS), Solaris 2.51-10, Open Solaris, Cisco IOS & NX-OS, VMWare Server/ESX/ESXi/vSphere 3.x-6.x, Sun Xvm Virtualbox, Xen 3.x, Win- dows Server 2008-2012R2 • Server software: Apache, Tomcat, Qmail, Postfix, Sendmail, Exim, OpenLDAP, SunONE Directory, Lucent QIP, ISC dhcpd, Bind, MySQL, PostresSQL, OpenSSL, OpenSSH, djbdns, Samba, NFS, Snort, Cisco CNR3.5-5.0.11, Nagios, MS Clustering Services, Active Directory, IIS, MSSQL • Storage software: Commvault Simpana 9-11, Legato Networker 7.2.x-8.x, Avamar 3.x-5.x, Netapp OnCommand Suite, Netapp Data OnTap 7.2.x- 8.2.x EMC ControlCenter 5.x, EMC Solutions Enabler 6.x, Navisphere 6.24.x, Veritas Command Central 4.3.x, Symmetrix Management Console Hitachi Storage Navigator, HDS Device Manager, Celerra Manager 5.6„ Veritas VxVM 3.x-6 • Cloud Technologies: AWS, GCE, Docker, Kubernetes, Ansible • Network technolgies: ISDN, PPP, MLPPP, DSL, BGP, Frame Relay, VoIP, POP3, IMAP, SMTP, SNMP, DNS, FTP, DHCP, SONET, EIGRP, RIP, IS-IS, Pv6, IPSEC, RADIUS, DOCSIS • Programming/Scripting: Python, PowerShell, Perl, Bourne and C shell scripting, PHP, C, HTML, XML • Hardware: – Sun Servers and Workstations including large scale SunFire E20/E25K through all current hardware Sparc, Intel, and AMD.
    [Show full text]
  • Gary Briggs Personal Details
    Gary Briggs Personal Details Home Address: 2251 S Bentley Ave, Apt 202 Los Angeles CA 90064 E-mail: [email protected] Phone: +1 (310) 406 7955 Objective I am looking to obtain a position that utilizes my skills and background as an advanced software engineer Work Experience Summer 2002 - Codehost, Inc, General Engineer. Multiple positions: Spring 2009: Software Engineer [C and C++] for server, desktop and limited-hardware work Database and Server administration. Maintaining a variety of servers including SCM repositories, file and mail servers [Samba, NFS/NIS, Postfix, Amavis], MySQL and Apache Printer driver development [for mostly PostScript devices] and associated tool development Web development [PHP and Perl with MySQL, developing an entire licensing system] Project Management including specification writing and managing external teams Documentation authoring QA Spring 2007 - Chickenware, Senior Games Architect and Developer Present: [Part Time] Lead Programmer and designer on fully networked multiplayer game Use many libraries: Bullet [physics], Ogre3d [graphics], RakNet [networking], Lua [scripting], OpenAL [sound] Fully cross-platform, works on Linux, OSX, Windows Extensive documentation authoring, including complete Doxygen source comments and PDF guides Summer 2000 - Lehman Brothers bank, Web technology group. General Web engineer including Fall 2001: Testing and expanding open source search engine technologies Server administration [Solaris, Linux, Apache, Netscape web server] Initiating work on a test lab for checking the functionality
    [Show full text]
  • Biblioteca Antispam De Propósito Geral
    Universidade Federal do Rio de Janeiro Escola Politécnica Departamento de Eletrônica e de Computação LibAntispam – Biblioteca Antispam de Propósito Geral Autor: _________________________________________________ Rafael Jorge Csura Szendrodi Orientador: _________________________________________________ Prof. Jorge Lopes de Souza Leão, Dr. Ing. Examinador: _________________________________________________ Prof. Antônio Cláudio Gómez de Sousa, M. Sc. Examinador: _________________________________________________ Prof. Aloysio de Castro Pinto Pedroza, Dr. DEL Maio de 2009 DEDICATÓRIA Dedico este trabalho: À Zeus (Jupiter), deus do Céu e da Terra, pai e rei dos deuses e dos homens, senhor do Olímpio e deus supremo deste universo. À Hera (Juno), rainha dos deuses, protetora da vida, das mulheres, da fecundidade e do matrimônio. À Athena (Miverva), deusa da sabedoria, do oficio, da inteligência e da guerra justa. Protetora do povo de Atenas. À Ártemis (Diana), deusa da caça, da natureza, da colheita, da serena luz da lua, dos nascimentos e protetora das Amazonas. À Afrodite (Venus), deusa da beleza e do amor, mãe de Enéias, fundador da raça romana, e matriarca da dinastia Julia (a dinastia de Julio Cesar). À minha mãe, Ildi e ao meu pai Gyorgy, pelo meu nascimento e por, de certa forma, terem contribuído para que eu me moldasse no que sou hoje. ii AGRADECIMENTO Ao povo brasileiro que contribuiu de forma significativa à minha formação e estada nesta Universidade. Este projeto é uma pequena forma de retribuir o investimento e confiança em mim depositados. Ao professor Leão, meu orientador neste projeto, por ter aceitado me guiar nesta minha jornada final do meu curso. Aos professores Baruqui (meu orientador acadêmico), Joarez, Gabriel, Petraglia e Mariane, meus amigos há vários anos que sempre me incentivaram a não desistir do curso de eletrônica.
    [Show full text]
  • Zimbra Collaboration Server Administrator's Guide
    Zimbra Collaboration Server Administrator’s Guide ZCS 8.0 Open Source Edition August 2013 Legal Notices Copyright ©2005-2014 Telligent Systems, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. “Telligent” and “Zimbra” are registered trademarks or trademarks of Telligent Systems, Inc. in the United States and other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. Telligent Systems, Inc. d/b/a Zimbra Software, LLC www.zimbra.com ZCS 8.0 March 2014 Rev 6 for 8.0.7 Table of Contents 1 Introduction . 9 Audience . 9 Third-Party Components . 9 Support and Contact Information . 9 2 Product Overview . 11 Core Email, Calendar and Collaboration Functionality . 11 Zimbra Components . 12 System Architecture . 12 Zimbra Application Packages . 14 Example of a Typical Multiserver Configuration . 15 Zimbra System Directory Tree . 17 Web Client Versions . 18 3 Zimbra Mailbox Server . 21 Incoming Mail Routing . 21 Mailbox Server . 21 Message Store . 21 Data Store. 22 Index Store . 22 Mailbox Server Logs . 23 4 Zimbra LDAP Service . 25 LDAP Traffic Flow . 25 LDAP Directory Hierarchy . 26 ZCS LDAP Schema . 27 ZCS Objects . 28 Account Authentication . 30 Internal Authentication Mechanism. 30 External LDAP and External AD Authentication Mechanism . 30 Custom Authentication . 31 Kerberos5 Authentication Mechanism . 32 Global Address List . 33 Flushing LDAP Cache . 34 Flush the Cache for Themes and Locales . 35 Flush Accounts, Groups, COS, Domains, and Servers . 35 5 Zimbra Mail Transfer Agent. 37 Zimbra MTA Deployment . 37 Postfix Configuration Files . 38 SMTP Authentication . 38 SMTP Restrictions . 39 Sending Non Local Mail to a Different Server.
    [Show full text]
  • Debian Tips & Tricks
    Linux-Kurs Theme - Debian Tips & Tricks - 14. Feb. 2008 Michel Bisson Debian Linux Tips and Tricks Table of Contents Basic configuration program.................................................................................................. 4 Install package groups...........................................................................................................4 Install individual packages.....................................................................................................4 Configuration program for system......................................................................................... 4 To configure postscript fonts for a postscript printer.............................................................4 Configuration for kdm to manage remote X servers..............................................................4 Xserver DPI settings ca be changed..................................................................................... 4 Edit the following files to allow TrueType fonts..................................................................... 4 Configuration of X-Server access control..............................................................................4 X-Server keyboard symbols for keys layout meanings......................................................... 4 To get rid of all the unused libraries ..................................................................................... 4 To search for a package name in All available packages.....................................................4
    [Show full text]