| |
| |
| Introduction | |
| |
| |
| Acknowledgments | |
| |
| |
| |
| Today's Computing Environment | |
| |
| |
| Complexity, Complexity, Complexity | |
| |
| |
| Multiple Technologies and Protocols | |
| |
| |
| Multiple Vendors | |
| |
| |
| Varied Users | |
| |
| |
| Multiple Locations | |
| |
| |
| Rapid Change | |
| |
| |
| Greater Business Demands | |
| |
| |
| A Daunting Environment To Work In | |
| |
| |
| The Total Cost of Ownership Issue | |
| |
| |
| Total Cost of Ownership Defined | |
| |
| |
| Industry TCO Estimates | |
| |
| |
| What TCO Studies Reveal | |
| |
| |
| The Underlying Reason for High TCO | |
| |
| |
| A Typical Scenario: Choosing Office Systems | |
| |
| |
| Availability as the Most Significant Contributor to TCO | |
| |
| |
| Summary | |
| |
| |
| |
| Achieving Higher Availability | |
| |
| |
| Determining User Availability Requirements | |
| |
| |
| The Service Level Agreement | |
| |
| |
| Helping Users Identify Their Availability Requirements | |
| |
| |
| Availability Levels and Measurements | |
| |
| |
| High Availability Level | |
| |
| |
| Continuous Operations Level | |
| |
| |
| Continuous Availability | |
| |
| |
| Quantifying Availability Targets | |
| |
| |
| Availability: A User Metric | |
| |
| |
| Measuring End-To-End Availability | |
| |
| |
| Summary | |
| |
| |
| |
| Planning for System Availability | |
| |
| |
| Identifying System Components | |
| |
| |
| Addressing Critical Components | |
| |
| |
| The Four Elements of Availability | |
| |
| |
| Summary | |
| |
| |
| |
| Preparing for Systems Management | |
| |
| |
| Processes, Data, Tools, and Organization | |
| |
| |
| Systems Management in the PC World (or the Lack of It) | |
| |
| |
| IT Organizations: Away from Centralization, Then Back Again | |
| |
| |
| Understanding the Systems To Manage | |
| |
| |
| The Basics of Management: Five Phases | |
| |
| |
| |
| Setting Objectives | |
| |
| |
| |
| Planning | |
| |
| |
| |
| Execution | |
| |
| |
| |
| Measurement | |
| |
| |
| |
| Control | |
| |
| |
| Identifying the Systems Management Disciplines | |
| |
| |
| |
| Implementing Service-Level Management | |
| |
| |
| Service-Level Management | |
| |
| |
| Process Requirements | |
| |
| |
| Data and Measurement Requirements | |
| |
| |
| Organization Requirements | |
| |
| |
| Tools Requirements | |
| |
| |
| Benefits of Service-Level Management | |
| |
| |
| Problem Management | |
| |
| |
| Process Requirements | |
| |
| |
| Data Requirements | |
| |
| |
| Organization Requirements | |
| |
| |
| Tools Requirements | |
| |
| |
| Benefits of Problem Management | |
| |
| |
| Change Management | |
| |
| |
| Process Requirements | |
| |
| |
| Data Requirements | |
| |
| |
| Organization Requirements | |
| |
| |
| Tools Requirements | |
| |
| |
| Benefits | |
| |
| |
| Security Management | |
| |
| |
| Process Requirements | |
| |
| |
| Data Requirements | |
| |
| |
| Organization Requirements | |
| |
| |
| Tools Requirements | |
| |
| |
| Benefits | |
| |
| |
| Asset and Configuration Management | |
| |
| |
| Process Requirements | |
| |
| |
| Data Requirements | |
| |
| |
| Organization Requirements | |
| |
| |
| Tools Requirements | |
| |
| |
| Availability Management | |
| |
| |
| Process Requirements | |
| |
| |
| Data Requirements | |
| |
| |
| Organization Requirements | |
| |
| |
| Tools Requirements | |
| |
| |
| Benefits | |
| |
| |
| |
| From Centralized to Distributed Computing Environments | |
| |
| |
| Systems Management Disciplines | |
| |
| |
| The Centralized Computing Environment | |
| |
| |
| The Distributed Computing Environment | |
| |
| |
| Systems Management in Today's Computing Environment | |
| |
| |
| Defining Appropriate Functions and Control | |
| |
| |
| Choosing a Deployment Strategy | |
| |
| |
| Developing a Deployment Strategy | |
| |
| |
| Management by Exception | |
| |
| |
| Policy-Based Management | |
| |
| |
| Standardization of Performance Data | |
| |
| |
| Accountability of the Distributed Systems Manager | |
| |
| |
| Central Definition of Systems Management Architectures | |
| |
| |
| Process Ownership | |
| |
| |
| Summary | |
| |
| |
| |
| Techniques That Address Multiple Availability Requirements | |
| |
| |
| Redundancy | |
| |
| |
| Hardware Redundancy Examples | |
| |
| |
| Software Redundancy Examples | |
| |
| |
| Environmental Redundancy Example | |
| |
| |
| Critical Success Factors | |
| |
| |
| Backup of Critical Resources | |
| |
| |
| Methods of Backup | |
| |
| |
| Hardware Backup Examples | |
| |
| |
| Software Backup Examples | |
| |
| |
| IT Operations Backup Examples | |
| |
| |
| Critical Success Factors | |
| |
| |
| Clustering | |
| |
| |
| Comparing Clustering and Redundancy | |
| |
| |
| Hardware and Software Clustering Examples | |
| |
| |
| IT Operations Clustering Examples | |
| |
| |
| Environmental Clustering Examples | |
| |
| |
| Critical Success Factors | |
| |
| |
| Fault Tolerance | |
| |
| |
| Hardware Fault Tolerance Examples | |
| |
| |
| Software Fault Tolerance Examples | |
| |
| |
| Environmental Fault Tolerance Examples | |
| |
| |
| Critical Success Factors | |
| |
| |
| Isolation or Partitioning | |
| |
| |
| Hardware Isolation Examples | |
| |
| |
| Software Isolation Examples | |
| |
| |
| Other Benefits of Isolation | |
| |
| |
| Critical Success Factors | |
| |
| |
| Automated Operations | |
| |
| |
| Console and Network Operations Examples | |
| |
| |
| Workload Management Examples | |
| |
| |
| System Resource Monitoring Examples | |
| |
| |
| Problem Management Applications | |
| |
| |
| Distribution of Resources Example | |
| |
| |
| Backup and Restore Examples | |
| |
| |
| Critical Success Factors | |
| |
| |
| Access Security Mechanisms | |
| |
| |
| Steps to Secure Access | |
| |
| |
| Types of Security | |
| |
| |
| Password Management | |
| |
| |
| Critical Success Factors | |
| |
| |
| Standardization | |
| |
| |
| Hardware Standardization Examples | |
| |
| |
| Software Standardization Examples | |
| |
| |
| Network Standardization Examples | |
| |
| |
| Processes and Procedures Standardization Examples | |
| |
| |
| Naming Standardization Examples | |
| |
| |
| Critical Success Factors | |
| |
| |
| Transitioning to Standardization | |
| |
| |
| Summary | |
| |
| |
| |
| Special Techniques for System Reliability | |
| |
| |
| The Use of Reliable Components | |
| |
| |
| Techniques for Maximizing Hardware Component Reliability | |
| |
| |
| Techniques for Maximizing Software Component Reliability | |
| |
| |
| Personnel-Related Techniques for Maximizing Reliability | |
| |
| |
| Environment-Related Techniques for Maximizing Reliability | |
| |
| |
| Some Reliability Indicators for Suppliers | |
| |
| |
| Programming to Minimize Failures | |
| |
| |
| Correctness | |
| |
| |
| Robustness | |
| |
| |
| Extensibility | |
| |
| |
| Reusability | |
| |
| |
| Implement Environmental Independence Measures | |
| |
| |
| Use Power Generators | |
| |
| |
| Use Independent Air-Conditioning Units | |
| |
| |
| Use Fire Protection Systems | |
| |
| |
| Use Raised Flooring | |
| |
| |
| Install Equipment Wheel Locks | |
| |
| |
| Locate Computer Room on the Second Floor | |
| |
| |
| Utilize Fault Avoidance Measures | |
| |
| |
| Analyzing Problem Trends and Statistics | |
| |
| |
| Use of Advanced Hardware Technologies | |
| |
| |
| Use of Software Maintenance Tools | |
| |
| |
| Summary | |
| |
| |
| |
| Special Techniques for System Recoverability | |
| |
| |
| Automatic Fault Recognition | |
| |
| |
| Parity Checking Memory | |
| |
| |
| ECC Memory | |
| |
| |
| Data Validation Routines | |
| |
| |
| Fast Recovery Techniques | |
| |
| |
| Minimizing Use of Volatile Storage Media | |
| |
| |
| Regular Database Updates to Central Storage | |
| |
| |
| Automatic File-Save Features | |
| |
| |
| Summary | |
| |
| |
| |
| Special Techniques for System Serviceability | |
| |
| |
| Online System Redefinition | |
| |
| |
| Add or Remove I/O Devices | |
| |
| |
| Selectively Power Down Subsystems | |
| |
| |
| Commit or Reject Changes | |
| |
| |
| Informative Error Messages | |
| |
| |
| Use Standard Corporate Terminology | |
| |
| |
| Adopt Terms Already Used by Common Applications | |
| |
| |
| Tell What, Why, Impact, and How | |
| |
| |
| Implement Context-Sensitive Help | |
| |
| |
| Give Options for Viewing More Detailed Error Information | |
| |
| |
| Make Error Information Available After the Error Has Been Cleared | |
| |
| |
| Complete Documentation | |
| |
| |
| Have a Manual of Operations on Hand | |
| |
| |
| Write Basic Problem Isolation and Recovery Guides | |
| |
| |
| Provide System Configuration Diagrams | |
| |
| |
| Label Resources | |
| |
| |
| Provide a Complete Technical Library | |
| |
| |
| Installation of Latest Fixes and Patches | |
| |
| |
| Summary | |
| |
| |
| |
| Special Techniques for System Manageability | |
| |
| |
| Use Manageable Components | |
| |
| |
| Simple Network Management Protocol (SNMP) | |
| |
| |
| Common Management Information Protocol (CMIP) | |
| |
| |
| Desktop Management Interface (DMI) | |
| |
| |
| Common Information Management Format (CIM) | |
| |
| |
| Wired for Management (WfM) | |
| |
| |
| Management Applications | |
| |
| |
| Systems Management Issues | |
| |
| |
| Automated Systems Management Capabilities | |
| |
| |
| System Management Applications and Frameworks | |
| |
| |
| Educate IS Personnel on Systems Management Disciplines | |
| |
| |
| Business Value of the Information System | |
| |
| |
| Value of Systems Management Disciplines | |
| |
| |
| Principles of Management | |
| |
| |
| Basic Numerical Analysis Skills | |
| |
| |
| Summary | |
| |
| |
| |
| All Together Now | |
| |
| |
| The Value of Systems Management Disciplines | |
| |
| |
| Which One First? | |
| |
| |
| Analyze Outages | |
| |
| |
| Identify Single Points of Failure | |
| |
| |
| Exploit What You Have | |
| |
| |
| An Implementation Strategy | |
| |
| |
| Summary | |
| |
| |
| |
| Availability Features of Selected Products | |
| |
| |
| Availability Features of Selected Operating Systems | |
| |
| |
| Availability Features of Novell NetWare | |
| |
| |
| Availability Features of Sun Solaris 8 | |
| |
| |
| Availability Features of AIX | |
| |
| |
| Availability Features of Microsoft Windows 2000 Server and Professional | |
| |
| |
| Availability Features of IBM OS/400 | |
| |
| |
| Availability Features of Selected Hardware Components | |
| |
| |
| Availability Features of IBM S/390 Integrated Server | |
| |
| |
| Availability Features of the IBM AS/400 Midrange System | |
| |
| |
| Availability Features of the IBM RS/6000 | |
| |
| |
| Availability Features of Compaq Proliant Servers | |
| |
| |
| Availability Features of Selected Software Components | |
| |
| |
| Availability Features of the Oracle 8i Database | |
| |
| |
| Index | |