Principles of Computer Systems and Network Management

1. Auflage 2010
ISBN: 978-0-387-89009-8
Verlag: Springer-Verlag
Format: PDF
Kopierschutz: Adobe DRM (»Systemvoraussetzungen)

E-Book, Englisch, 260 Seiten

As computer systems and networks have evolved and grown more complex, the role of the IT department in most companies has transformed primarily to ensuring that they continue to operate without disruption. IT spending, as reported by a variety of studies, shows the trend that most of the expenses associated with IT are related to the task of operating and managing installed computer systems and applications. Furthermore, the growth in that expense category is outstripping the expense associated with developing new appli- tions. As a consequence, there is a pressing need in the companies and organi- tions to find qualified people who can manage the installed base of computer systems and networks. This marks a significant shift from the previous trend in companies where the bulk of the IT department expenses were targeted on development of new computer applications. The shift from developing new applications to managing existing systems is a natural consequence of the maturity of IT industry. Computers are now u- quitous in every walk of life, and the number of installed successful applications grows steadily over the time. Each installed successful application in a company lasts for a long duration. Consequently, the number of installed applications is much larger than the number of projects focused on developing new appli- tions. While there always will be new applications and systems being developed within companies, the predominance of managing and operating existing app- cations is likely to continue.

Autoren/Hrsg.

Inhaltsverzeichnis

1;Principles of Computer Systems and Network Management;2
1.1;Preface;6
1.2;Contents;9
1.3;Introduction;14
1.3.1;1.1 Introduction;14
1.3.2;1.2 Computer System Life Cycle;15
1.3.3;1.3 Shared Hosting Data Center (SHDC);18
1.3.4;1.4 Large Enterprise;20
1.3.5;1.5 Network Service Provider;22
1.3.6;1.6 History of Systems Management;25
1.3.7;1.7 Summary;27
1.3.8;1.8 Review Questions;27
1.3.9;References;28
1.4;Planning and Implementation;29
1.4.1;2.1 Requirements;30
1.4.1.1;2.1.1 Performance Requirements;30
1.4.1.2;2.1.2 Resiliency and Availability Requirements;31
1.4.1.3;2.1.3 Power and Thermal Requirements;32
1.4.1.4;2.1.4 Security Requirements;33
1.4.1.5;2.1.5 Manageability Requirements;34
1.4.1.6;2.1.6 Backward Compatibility;34
1.4.1.7;2.1.7 Other Requirements;35
1.4.2;2.2 Evaluating Computer Systems;36
1.4.2.1;2.2.1 Evaluating Computer Systems Performance;38
1.4.2.1.1;2.2.1.1 General Principles for Performance Evaluation;39
1.4.2.1.1.1;Utilization Law;39
1.4.2.1.1.2;Little’s Law;39
1.4.2.1.1.3;Forced Flow Law;40
1.4.2.1.1.4;Safety Margins;42
1.4.2.1.2;2.2.1.2 Queuing Theory;43
1.4.2.1.3;2.2.1.3 Queuing Networks;44
1.4.2.1.3.1;Canonical Delay and Throughput Curves;45
1.4.2.1.4;2.2.1.4 An Example;47
1.4.2.1.5;2.2.1.5 Simulations;48
1.4.2.2;2.2.2 Evaluating Resiliency and Availability;49
1.4.2.2.1;2.2.2.1 Reliability Analysis;50
1.4.2.2.2;2.2.2.2 Critical Component Identification;52
1.4.2.2.3;2.2.2.3 Failure Effects Modeling;54
1.4.2.3;2.2.3 Power and Thermal Analysis;55
1.4.2.4;2.2.4 Computer System Security Analysis;59
1.4.2.4.1;2.2.4.1 Comparison Against Checklists;60
1.4.2.4.2;2.2.4.2 Vulnerability Analysis;60
1.4.3;2.3 Planning to Satisfy Requirements;61
1.4.3.1;2.3.1 Systems Planning Process;62
1.4.3.1.1;2.3.1.1 Architecture Definition;63
1.4.3.1.1.1;Tiering;63
1.4.3.1.1.2;Perimeter Defense;65
1.4.3.1.1.3;Separation of Management and Operations;65
1.4.3.1.1.4;Hierarchical Architecture;66
1.4.3.1.1.5;Standardization of Components;67
1.4.3.1.2;2.3.1.2 Logical Plan Development;67
1.4.3.1.3;2.3.1.3 Approaches for Satisfying Requirements;69
1.4.3.1.3.1;Reuse from a Catalogue;69
1.4.3.1.3.2;Extrapolate from a Catalogue;70
1.4.3.1.4;2.3.1.4 Dynamic Composition of Configurations;70
1.4.4;2.4 Implementation;71
1.4.5;2.5 Summary;71
1.4.6;2.6 Review Questions;72
1.4.7;References;73
1.5;Operations Management;74
1.5.1;3.1 Operations Center;74
1.5.2;3.2 Management Data;77
1.5.3;3.3 Manager Agent Protocols;80
1.5.3.1;3.3.1 Remote Consoles;80
1.5.3.2;3.3.2 Simple Network Management Protocol (SNMP);81
1.5.3.3;3.3.3 Common Object Repository Broker Architecture (CORBA);82
1.5.3.4;3.3.4 Web-Based Enterprise Management (WBEM);83
1.5.3.5;3.3.5 Web Services;83
1.5.3.6;3.3.6 NetConf;84
1.5.3.7;3.3.7 Comparison of the Different Management Protocols;85
1.5.4;3.4 Management Information Structure;85
1.5.4.1;3.4.1 Management Information Base;86
1.5.4.2;3.4.2 Common Information Model;88
1.5.4.3;3.4.3 Issues with Standard Representation;89
1.5.5;3.5 Device Agent Structure;91
1.5.6;3.6 Management Application Structure;92
1.5.7;3.7 Operations Center Function;94
1.5.8;3.8 Summary;97
1.5.9;3.9 Review Questions;97
1.5.10;References;98
1.6;Discovery;99
1.6.1;4.1 Discovery Approaches;100
1.6.1.1;4.1.1 Manual Inventory;100
1.6.1.2;4.1.2 Dictionary/Directory Queries;101
1.6.1.3;4.1.3 Self-Advertisement;101
1.6.1.4;4.1.4 Passive Observation;102
1.6.1.5;4.1.5 Agent-Based Discovery;102
1.6.1.6;4.1.6 Active Probing;103
1.6.2;4.2 Discovery of Specific Types of IT Infrastructure;104
1.6.2.1;4.2.1 Discovering Servers;104
1.6.2.1.1;4.2.1.1 DNS Zone Transfer;104
1.6.2.1.2;4.2.1.2 Traffic Analysis;105
1.6.2.1.3;4.2.1.3 Agent-Based Discovery;106
1.6.2.1.4;4.2.1.4 Agent-Less Discovery;107
1.6.2.2;4.2.2 Discovering Client Machines;107
1.6.2.3;4.2.3 Discovering Applications on Servers and Clients;108
1.6.2.4;4.2.4 Discovering Layer-3 Network Devices;110
1.6.2.5;4.2.5 Discovering Layer-2 Network Devices;111
1.6.3;4.3 Storing Discovered Information;112
1.6.3.1;4.3.1 Representing Hierarchical Relationships;113
1.6.3.2;4.3.2 Representing General Graphs;116
1.6.3.3;4.3.3 Representing Generic Relationships;117
1.6.3.4;4.3.4 Other Types of Databases;118
1.6.4;4.4 Summary;119
1.6.5;4.5 Review Questions;119
1.6.6;References;120
1.7;Monitoring;121
1.7.1;5.1 Monitored Information;121
1.7.2;5.2 Generic Model for Monitoring;122
1.7.3;5.3 Data Collection;124
1.7.3.1;5.3.1 Passive Monitoring;124
1.7.3.1.1;5.3.1.1 Applications;125
1.7.3.1.2;5.3.1.2 Servers, Personal Computers, and Laptops;126
1.7.3.1.3;5.3.1.3 Networks;128
1.7.3.2;5.3.2 Active Monitoring;129
1.7.3.2.1;5.3.2.1 Applications;129
1.7.3.2.2;5.3.2.2 Servers, Personal Computers, and Laptops;131
1.7.3.2.3;5.3.2.3 Networks;132
1.7.4;5.4 Pre-DB Data Processing;133
1.7.4.1;5.4.1 Data Reduction;133
1.7.4.2;5.4.2 Data Cleansing;134
1.7.4.3;5.4.3 Data Format Conversion;137
1.7.5;5.5 Management Database;139
1.7.5.1;5.5.1 Partitioned Databases;140
1.7.5.2;5.5.2 Rolling Databases;141
1.7.5.3;5.5.3 Load-Balanced Databases;141
1.7.5.4;5.5.4 Hierarchical Database Federation;142
1.7.5.5;5.5.5 Round-Robin Databases;144
1.7.6;5.6 Summary;144
1.7.7;5.7 Review Questions;144
1.8;Fault Management;146
1.8.1;6.1 Fault Management Architecture;146
1.8.1.1;6.1.1 Common Types of Symptoms;148
1.8.1.2;6.1.2 Common Types of Root Causes;150
1.8.2;6.2 Fault Diagnosis Algorithms;152
1.8.2.1;6.2.1 Topology Analysis Methods;153
1.8.2.2;6.2.2 Rule-Based Methods;156
1.8.2.3;6.2.3 Decision Trees;157
1.8.2.4;6.2.4 Dependency Graphs;158
1.8.2.5;6.2.5 Code Book;160
1.8.2.6;6.2.6 Knowledge Bases;161
1.8.2.7;6.2.7 Case-Based Reasoning;162
1.8.2.8;6.2.8 Other Techniques;163
1.8.3;6.3 Self-Healing Systems;164
1.8.3.1;6.3.1 Autonomic Computing Architecture and Variations;164
1.8.3.2;6.3.2 An Example of a Self Healing System;166
1.8.4;6.4 Avoiding Failures;167
1.8.4.1;6.4.1 Redundancy;167
1.8.4.2;6.4.2 Independent Monitor;168
1.8.4.3;6.4.3 Collaborative Monitoring;169
1.8.4.4;6.4.4 Aged Restarts;169
1.8.5;6.5 Summary;170
1.8.6;6.6 Review Questions;170
1.8.7;References;171
1.9;Configuration Management;173
1.9.1;7.1 Configuration Management Overview;173
1.9.2;7.2 Configuration Setting;175
1.9.2.1;7.2.1 Reusing Configuration Settings;176
1.9.2.2;7.2.2 Script-Based Configuration Management;178
1.9.2.3;7.2.3 Model-Based Configuration Management;179
1.9.2.4;7.2.4 Configuration Workflows;181
1.9.2.5;7.2.5 Simplifying Configuration Through Higher Abstractions;182
1.9.2.6;7.2.6 Policy-Based Configuration Management;183
1.9.3;7.3 Configuration Discovery and Change Control;184
1.9.3.1;7.3.1 Structure of the CMDB;185
1.9.3.2;7.3.2 Federated CMDB;186
1.9.3.3;7.3.3 Dependency Discovery;186
1.9.3.3.1;7.3.3.1 Application Dependencies;187
1.9.3.3.2;7.3.3.2 Network Dependencies;188
1.9.3.3.3;7.3.3.3 Service Dependencies;189
1.9.4;7.4 Configuration Management Applications;189
1.9.4.1;7.4.1 Configuration Validation;189
1.9.4.2;7.4.2 What-If Analysis;190
1.9.4.3;7.4.3 Configuration Cloning;191
1.9.5;7.5 Patch Management;191
1.9.5.1;7.5.1 Patch Identification;191
1.9.5.2;7.5.2 Patch Assessment;192
1.9.5.3;7.5.3 Patch Testing;193
1.9.5.4;7.5.4 Patch Installation;194
1.9.6;7.6 Summary;195
1.9.7;7.7 Review Questions;196
1.9.8;References;196
1.10;Performance and Accounting Management;198
1.10.1;8.1 Need for Operation Time Performance Management;199
1.10.2;8.2 Approaches for Performance Management;199
1.10.3;8.3 Performance Monitoring and Reporting;201
1.10.3.1;8.3.1 Performance Metrics;202
1.10.3.2;8.3.2 Addressing Scalability Issues;203
1.10.3.3;8.3.3 Error Handling and Data Cleansing;205
1.10.3.4;8.3.4 Metric Composition;207
1.10.3.5;8.3.5 Performance Monitoring Approaches;209
1.10.3.5.1;8.3.5.1 Networks;209
1.10.3.5.2;8.3.5.2 Servers;210
1.10.3.5.3;8.3.5.3 Applications;210
1.10.3.6;8.3.6 Performance Reporting and Visualization;212
1.10.4;8.4 Performance TroubleShooting;216
1.10.4.1;8.4.1 Detecting Performance Problems;216
1.10.4.1.1;8.4.1.1 Thresholds;216
1.10.4.1.2;8.4.1.2 Statistical Abnormality;218
1.10.4.1.3;8.4.1.3 Help Desk Reports;218
1.10.4.2;8.4.2 Correcting Performance Problems;218
1.10.4.2.1;8.4.2.1 Misconfiguration;219
1.10.4.2.2;8.4.2.2 System Changes;219
1.10.4.2.3;8.4.2.3 Workload Growth;219
1.10.4.2.4;8.4.2.4 Workload Surge;220
1.10.5;8.5 Capacity Planning;220
1.10.5.1;8.5.1 Simple Estimation;221
1.10.5.2;8.5.2 ARIMA Models;222
1.10.5.3;8.5.3 Seasonal Decomposition;223
1.10.6;8.6 Accounting Management;224
1.10.7;8.7 Summary;226
1.10.8;8.8 Review Questions;226
1.10.9;References;227
1.11;Security Management;228
1.11.1;9.1 General Techniques;229
1.11.1.1;9.1.1 Cryptography and Key Management;229
1.11.1.2;9.1.2 Authentication;233
1.11.1.3;9.1.3 Confidentiality/Access Control;235
1.11.1.4;9.1.4 Integrity;236
1.11.1.5;9.1.5 Non-Repudiation;238
1.11.1.6;9.1.6 Availability;238
1.11.2;9.2 Security Management for Personal Computers;239
1.11.2.1;9.2.1 Data Protection;240
1.11.2.2;9.2.2 Malware Protection;241
1.11.2.3;9.2.3 Patch Management;242
1.11.2.4;9.2.4 Data Backup and Recovery;243
1.11.3;9.3 Security Management for Computer Servers;244
1.11.3.1;9.3.1 Password Management;245
1.11.3.2;9.3.2 Single Sign-On;246
1.11.3.3;9.3.3 Secure Access Protocols;247
1.11.4;9.4 Security Management for Computer Networks;248
1.11.4.1;9.4.1 Firewalls;249
1.11.4.2;9.4.2 Intrusion Detection/Prevention Systems;250
1.11.4.3;9.4.3 Honeypots;252
1.11.5;9.5 Operational Issues;252
1.11.5.1;9.5.1 Physical Security;253
1.11.5.2;9.5.2 Security Policies;253
1.11.5.3;9.5.3 Auditing;255
1.11.6;9.6 Summary;255
1.11.7;9.7 Review Questions;256
1.11.8;References;257
1.12;Advanced Topics;258
1.12.1;10.1 Process Management;258
1.12.2;10.2 Helpdesk Systems;259
1.12.3;10.3 Web, Web 2.0, and Management;261
1.12.4;10.4 Summary;262
1.12.5;10.5 Review Questions;262
1.12.6;References;262
1.13;Index;263