Event management and best practices
This IBM Redbooks publication presents a deep and broad understanding about event management with a focus on best practices. It examines event filtering, duplicate detection, correlation, notification, escalation, and synchronization. Plus it discusses trouble-ticket integration, maintenance modes,...
Autor Corporativo: | |
---|---|
Otros Autores: | |
Formato: | Libro electrónico |
Idioma: | Inglés |
Publicado: |
Austin, TX :
IBM, International Technical Support Organization
c2004.
|
Edición: | 1st ed |
Colección: | IBM redbooks.
|
Materias: | |
Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627126106719 |
Tabla de Contenidos:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. Introduction to event management
- 1.1 Importance of event correlation and automation
- 1.2 Terminology
- 1.2.1 Event
- 1.2.2 Event management
- 1.2.3 Event processing
- 1.2.4 Automation and automated actions
- 1.3 Concepts and issues
- 1.3.1 Event flow
- 1.3.2 Filtering and forwarding
- 1.3.3 Duplicate detection and throttling
- 1.3.4 Correlation
- 1.3.5 Event synchronization
- 1.3.6 Notification
- 1.3.7 Trouble ticketing
- 1.3.8 Escalation
- 1.3.9 Maintenance mode
- 1.3.10 Automation
- 1.4 Planning considerations
- 1.4.1 IT environment assessment
- 1.4.2 Organizational considerations
- 1.4.3 Policies
- 1.4.4 Standards
- Chapter 2. Event management categories and best practices
- 2.1 Implementation approaches
- 2.1.1 Send all possible events
- 2.1.2 Start with out-of-the-box notifications and analyze reiteratively
- 2.1.3 Report only known problems and add them to the list as they are identified
- 2.1.4 Choose top X problems from each support area
- 2.1.5 Perform Event Management and Monitoring Design
- 2.2 Policies and standards
- 2.2.1 Reviewing the event management process
- 2.2.2 Defining severities
- 2.2.3 Implementing consistent standards
- 2.2.4 Assigning responsibilities
- 2.2.5 Enforcing policies
- 2.3 Filtering
- 2.3.1 Why filter
- 2.3.2 How to filter
- 2.3.3 Where to filter
- 2.3.4 What to filter
- 2.3.5 Filtering best practices
- 2.4 Duplicate detection and suppression
- 2.4.1 Suppressing duplicate events
- 2.4.2 Implications of duplicate detection and suppression
- 2.4.3 Duplicate detection and throttling best practices
- 2.5 Correlation
- 2.5.1 Correlation best practices
- 2.5.2 Implementation considerations
- 2.6 Notification.
- 2.6.1 How to notify
- 2.6.2 Notification best practices
- 2.7 Escalation
- 2.7.1 Escalation best practices
- 2.7.2 Implementation considerations
- 2.8 Event synchronization
- 2.8.1 Event synchronization best practices
- 2.9 Trouble ticketing
- 2.9.1 Trouble ticketing best practices
- 2.10 Maintenance mode
- 2.10.1 Maintenance status notification
- 2.10.2 Handling events from a system in maintenance mode
- 2.10.3 Prolonged maintenance mode
- 2.10.4 Network topology considerations
- 2.11 Automation
- 2.11.1 Automation best practices
- 2.11.2 Automation implementation considerations
- 2.12 Best practices flowchart
- Chapter 3. Overview of IBM Tivoli Enterprise Console
- 3.1 The highlights of IBM Tivoli Enterprise Console
- 3.2 Understanding the IBM Tivoli Enterprise Console data flow
- 3.2.1 IBM Tivoli Enterprise Console input
- 3.2.2 IBM Tivoli Enterprise Console processing
- 3.2.3 IBM Tivoli Enterprise Console output
- 3.3 IBM Tivoli Enterprise Console components
- 3.3.1 Adapter Configuration Facility
- 3.3.2 Event adapter
- 3.3.3 IBM Tivoli Enterprise Console gateway
- 3.3.4 IBM Tivoli NetView
- 3.3.5 Event server
- 3.3.6 Event database
- 3.3.7 User interface server
- 3.3.8 Event console
- 3.4 Terms and definitions
- 3.4.1 Event
- 3.4.2 Event classes
- 3.4.3 Rules
- 3.4.4 Rule bases
- 3.4.5 Rule sets and rule packs
- 3.4.6 State correlation
- Chapter 4. Overview of IBM Tivoli NetView
- 4.1 IBM Tivoli NetView (Integrated TCP/IP Services)
- 4.2 NetView visualization components
- 4.2.1 The NetView EUI
- 4.2.2 NetView maps and submaps
- 4.2.3 The NetView event console
- 4.2.4 The NetView Web console
- 4.2.5 Smartsets
- 4.2.6 How events are processed
- 4.3 Supported platforms and installation notes
- 4.3.1 Supported operating systems
- 4.3.2 Java Runtime Environments
- 4.3.3 AIX installation notes.
- 4.3.4 Linux installation notes
- 4.4 Changes in NetView 7.1.3 and 7.1.4
- 4.4.1 New features and enhancements for Version 7.1.3
- 4.4.2 New features and enhancements for Version 7.1.4
- 4.4.3 First failure data capture
- 4.5 A closer look at the new functions
- 4.5.1 servmon daemon
- 4.5.2 FFDC
- Chapter 5. Overview of IBM Tivoli Switch Analyzer
- 5.1 The need for layer 2 network management
- 5.1.1 Open Systems Interconnection model
- 5.1.2 Why layer 3 network management is not always sufficient
- 5.2 Features of IBM Tivoli Switch Analyzer V1.2.1
- 5.2.1 Daemons and processes
- 5.2.2 Discovery
- 5.2.3 Layer 2 status
- 5.2.4 Integration into NetView's topology map
- 5.2.5 Traps
- 5.2.6 Root cause analysis using IBM Tivoli Switch Analyzer and NetView
- 5.2.7 Real-life example
- Chapter 6. Event management products and best practices
- 6.1 Filtering and forwarding events
- 6.1.1 Filtering and forwarding with NetView
- 6.1.2 Filtering and forwarding using IBM Tivoli Enterprise Console
- 6.1.3 Filtering and forwarding using IBM Tivoli Monitoring
- 6.2 Duplicate detection and throttling
- 6.2.1 IBM Tivoli NetView and Switch Analyzer for duplicate detection and throttling
- 6.2.2 IBM Tivoli Enterprise Console duplicate detection and throttling
- 6.2.3 IBM Tivoli Monitoring for duplicate detection and throttling
- 6.3 Correlation
- 6.3.1 Correlation with NetView and IBM Tivoli Switch Analyzer
- 6.3.2 IBM Tivoli Enterprise Console correlation
- 6.3.3 IBM Tivoli Monitoring correlation
- 6.4 Notification
- 6.4.1 NetView
- 6.4.2 IBM Tivoli Enterprise Console
- 6.4.3 Rules
- 6.4.4 IBM Tivoli Monitoring
- 6.5 Escalation
- 6.5.1 Severities
- 6.5.2 Escalating events with NetView
- 6.6 Event synchronization
- 6.6.1 NetView and IBM Tivoli Enterprise Console.
- 6.6.2 IBM Tivoli Enterprise Console gateway and IBM Tivoli Enterprise Console
- 6.6.3 Multiple IBM Tivoli Enterprise Console servers
- 6.6.4 IBM Tivoli Enterprise Console and trouble ticketing
- 6.7 Trouble ticketing
- 6.7.1 NetView versus IBM Tivoli Enterprise Console
- 6.7.2 IBM Tivoli Enterprise Console
- 6.8 Maintenance mode
- 6.8.1 NetView
- 6.8.2 IBM Tivoli Enterprise Console
- 6.9 Automation
- 6.9.1 Using NetView for automation
- 6.9.2 IBM Tivoli Enterprise Console
- 6.9.3 IBM Tivoli Monitoring
- Chapter 7. A case study
- 7.1 Lab environment
- 7.1.1 Lab software and operating systems
- 7.1.2 Lab setup and diagram
- 7.1.3 Reasons for lab layout and best practices
- 7.2 Installation issues
- 7.2.1 IBM Tivoli Enterprise Console
- 7.2.2 NetView
- 7.2.3 IBM Tivoli Switch Analyzer
- 7.3 Examples and related diagnostics
- 7.3.1 Event flow
- 7.3.2 IBM Tivoli Enterprise Console troubleshooting
- 7.3.3 NetView
- 7.3.4 IBM Tivoli Switch Analyzer
- Appendix A. Suggested NetView configuration
- Suggested NetView EUI configuration
- Event console configuration
- Web console installation
- Web console stand-alone installation
- Web console applet
- Web console security
- Web console menu extension
- A smartset example
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.