Tài liệu Module 11: Windows 2000 Network Services Management pptx

Contents Overview 1 Defining Management Strategies 2 Identifying Management Processes 7 Generating Information on the Status Analyzing the Collected Data 26 Selecting Response Strategie

Contents

Overview 1

Defining Management Strategies 2

Identifying Management Processes 7

Generating Information on the Status

Analyzing the Collected Data 26

Selecting Response Strategies 28

Review 30

Module 11:

Windows 2000 Network Services Management

to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may

be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property

 2000 Microsoft Corporation All rights reserved

Microsoft, Active Directory, ActiveX, BackOffice, FrontPage, JScript, MS-DOS, NetMeeting, PowerPoint, Visual Basic, Visual C++, Visual Studio, Win32, Windows, Windows Media, Windows NT, are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries/regions

Project Lead: Don Thompson (Volt Technical)

Instructional Designers: Patrice Lewis (S&T OnSite), Renu Bhatt NIIT (USA) Inc

Instructional Design Consultants: Paul Howard, Susan Greenberg

Program Managers: Jack Creasey, Doug Steen (Independent Contractor)

Technical Contributors: Thomas Lee, Bernie Kilshaw, Joe Davies

Graphic Artist: Kirsten Larson (S&T OnSite)

Editing Manager: Lynette Skinner

Editor: Kristen Heller (Wasser)

Copy Editor: Kaarin Dolliver (S&T Consulting)

Online Program Manager: Debbi Conger

Online Publications Manager: Arlo Emerson (Aditi)

Online Support: Eric Brandt (S&T Consulting)

Multimedia Development: Kelly Renner (Entex)

Test Leads: Sid Benevente, Keith Cotton

Test Developer: Greg Stemp (S&T OnSite)

Production Support: Lori Walker (S&T Consulting)

Manufacturing Manager: Rick Terek (S&T OnSite)

Manufacturing Support: Laura King (S&T OnSite)

Lead Product Manager, Development Services: Bo Galford

Lead Product Manager: Ken Rosen

Group Product Manager: Robert Stewart

Other product and company names mentioned herein may be the trademarks of their respective owners

Instructor Notes

This module provides students with the information and decision-making processes needed to design a plan for managing network services

At the end of this module, students will be able to:

Define the strategies for managing the network services

Identify the processes used to execute the management plan

Select the appropriate methods to generate information on the status of the services

Select the appropriate methods to analyze collected data

Select appropriate response strategies

There is no lab in this module

Course Materials and Preparation

This section provides you with the materials and preparation needed to teach this module

Required Materials

To teach this module, you need the following materials:

Microsoft® PowerPoint® file 1562B_11.ppt

Preparation Tasks

To prepare for this module, you should:

Review the contents of this module

Read any relevant information provided in the Windows 2000 Help files, the Windows 2000 Resource Kit, or materials on the Instructor CD

Be familiar with processes and procedures for detection, notification, and response to both critical and noncritical variations in network services

Be familiar with strategies for generating information about the status of the network services

Understand methods for analyzing the collected data

Be familiar with reactive and proactive responses to status information

Review discussion and demonstration material and be prepared to lead class discussions on the topics

Read the review questions and be prepared to elaborate beyond the answers provided in the text

Presentation:

75 Minutes

Lab:

00 Minutes

Module Strategy

Use the following strategy to present this module

Defining Management Strategies

A successful management plan for network services includes strategies that permit detection of, and response to, changes in the network services The management strategies define policies, procedures, and processes that permit the network administrator to respond to, verify, and anticipate variations in the service

In this section:

• Explain that the highest priority in a management plan must be to detect and respond to critical events such as service or network failures The need to monitor design compliance and anticipate the need for design changes is a lower priority Point out that strategies for responses to service variations can be reactive, proactive, manual, or automatic

• Emphasize that management strategies must define processes to respond

to the service variations automatically, or provide notification to operations staff for manual responses

• Point out that verifying compliance with the design specifications requires both the monitoring and testing of the services

• Emphasize that requirements for the services infrastructure will change over time as needs for resources change Operations staff can use collected information about the consumption of resources to anticipate the need for changes to the network design

• Point out that the management plan must include processes to provide feedback and control of the network services infrastructure The processes must be designed to obtain the current status of the services, verify service compliance, and predict trends

Identifying Management Processes The management plan must include processes to provide feedback and control of the network services infrastructure The processes must be designed to obtain the current status of the services, verify compliance of the service operation, and respond to service variations Emphasize that any plan to monitor and respond to service variations is often part of a larger management system, such as Microsoft Systems Management Server, or third-party management solutions

Generating Information on the Status of the Services Emphasize that obtaining the operational status of a service requires information about individual service providers and network conditions, and verification that client requests receive appropriate responses

In this section:

• Emphasize that the collection of status information for analysis is critical

to the process of monitoring the individual services and the overall network

• Point out that command-line network tools and utilities can be used to test and analyze service and network operation and variation Explain that these tools and utilities can be used interactively, or their output stored in files for later analysis

• Explain that System Monitor, which is found within the Performance console allows you to obtain real-time data and collect logs

• Make sure students understand the illustration, scenario description, and directions for the Discussion Direct them to read through the scenario and answer the questions Be prepared to clarify if necessary Lead a class discussion on the students’ responses

• Emphasize that Simple Network Management Protocol (SNMP) can be used to both derive the status of hosts and control hosts in a

Transmission Control Protocol/Internet Protocol (TCP/IP) network Point out that in a Windows 2000 network, SNMP is an optional component Emphasize that SNMP may be required to support services

if the infrastructure has devices that are already managed and configured

by using SNMP

• Emphasize that Event logs are useful to calculate uptime based on service stop/starts, and to analyze errors and status changes Point out that the Event Log service starts automatically when you start

Windows 2000

• Emphasize that acquiring the necessary status information requires the automated accumulation of logs, or the running of command-line utilities and programs Discuss the use of scripts and programs to provide scheduled automation

• Emphasize that Windows Management Instrumentation (WMI) provides

a single point of integration through which status information from many sources within a computer can be accessed Mention the sample scripts on the Student CD

Analyzing the Collected Data The status of the network services can be generated from real-time data, accumulated logs, and calculated result sets The analysis processes, either manual or automatic, draw on the collected status information to create a final result set This result set can then be used to respond to service variations

Selecting Response Strategies Emphasize that the time taken to return a service to full operation is a function of the time taken to detect and respond to the failure, and the time

to repair Point out that minimizing the time taken to detect and respond to service variations, or to provide automated responses to service variations, can reduce the impact of failures and variations

Overview

Defining Management Strategies

Identifying Management Processes

Generating Information on the Status of the Services

Analyzing the Collected Data

Selecting Response Strategies

An essential component of a Microsoft® Windows® 2000 networking services infrastructure design is the management of the network services An effective management plan for network services can ensure that the functionality, security, availability, and performance of the network services, and the network, continue to meet the specifications of your infrastructure design

At the end of this module, you will be able to:

Define strategies for managing the network services

Identify the processes used to execute a management plan

Select the appropriate methods to generate information about the status of the services

Select the appropriate methods to analyze collected data

Select appropriate response strategies

In this module, you will

evaluate and develop the

management strategies

required to manage a

Windows 2000 networking

services infrastructure

Defining Management Strategies

Management StrategiesMonitor All DNS Activity

Responding to Service Variations

Verifying Compliance with Design

Anticipating Changes to a Design

Management Plan for DNS

Policies, Procedures, Processes

Policies, Procedures, Processes

Policies, Procedures, Processes

A management plan for network services is generated from strategies and permits detection of, and response to, changes in the network services Your management plan defines policies, procedures, and processes that permit you to respond to, verify, and anticipate variations in the service

The highest priority in your management plan must be to detect and respond to critical events such as service or network failures At a lower priority, you must monitor design compliance and anticipate the need for design changes The strategies defining your management plan can specify reactive, proactive, manual, or automatic responses to service variations

The management plan for network services is only one component of a larger network management plan The larger plan manages the network and

applications that are supported in the organization You must give consideration

to how the services management plan integrates with any larger network management plan

A services management plan includes strategies for:

Responding to service variations as they occur

Verifying that current operations are compliant with the design specifications

Anticipating the need for changes to the network services design

Management strategies must include processes and procedures used to continuously acquire the current status, analyze the collected data, and specify appropriate responses

strategies must define

processes and procedures

for detection, notification,

and response to both critical

and noncritical variations in

network services

Responding to Service Variations

Services and Servers Unavailable

Client Requests Not Resolved

Threshold Values Exceeded

Calculated Values Outside Specification

You must detect network service variations, such as the failure of a service, and respond appropriately to restore operation Your strategies must define

processes to respond to the service variations automatically, or provide notification to operations staff for manual responses

Typically, immediate detection, notification, and responses are required when:

Services or servers are unavailable

Client requests for services fail

Threshold values are exceeded

Calculated values are outside the specifications

Wherever possible, an effective management plan defines processes to detect

and respond to service variations before failure occurs

Immediate notifications of service variations are required when operations staff must make the response If your strategies include processes to automate responses to service variations, these processes must also include notifications

to operations staff of automated system responses that have occurred

Slide Objective

To describe typical service

variations that require

immediate detection and

response strategies

Lead-in

Your management plan

must determine which

service variations require

immediate detection, along

with the required responses

to these variations

Ask students to give

examples of services and

threshold values that are

critical in their organizations

Verifying Compliance with the Design

You can design your management plan to verify compliance with the design specifications either manually or automatically To verify that services are operating within the required specifications, it may be necessary to analyze both threshold values and accumulated data

Manual Testing

You cannot verify some aspects of a design, such as the testing of server redundancy, by using automatically collected data These design aspects require the definition of the appropriate manual processes and procedures to ensure that the services are compliant

Scheduled Audits, Availability, and Redundancy Tests

The security and access permissions for a service are often modified over time You can conduct regular audits to ascertain compliance with security, and access design specifications

If the service infrastructure consists of multiple servers providing redundancy and load balancing, tests will confirm compliance with the design

specifications Your compliance testing procedures can specify that servers or services be stopped to test the response of either automated or manual reconfiguration procedures

Slide Objective

To describe how to ensure

that functionality, security,

availability, and

performance are within the

design specifications

Lead-in

To verify compliance with

the design specifications,

you must include both the

monitoring and testing of the

services

Monitoring

Include monitoring processes in your management plan to measure service uptime, service performance, and service-to-service interaction The operations staff can use these measurements to verify compliance with the design

Service-to-service interaction

You must monitor interaction between services, such as replication between multiple WINS servers, or DNS to WINS query traffic, to ensure compliance with the specifications Your management plan must include analysis of replication schedules, replication traffic, and service interaction traffic

Anticipating Service Infrastructure Design Changes

Change Design?

Change Design?

Collected Data

Collected Data

Analysis

Router

The resources required to support the services infrastructure, and the requirements of the infrastructure, can change over time For example, a WINS database requires more disk resources as the database grows In addition, day-to-day operations management, and automatic changes, can alter the services infrastructure enough to require design changes Although most of these changes are minor, over time, the cumulative effect can be significant

Include in your management strategies processes to measure the change in resource needs for your services The measurement processes require the accumulation of information about the consumption of resources over time Operations staff uses this information to anticipate the need for changes to the network design

For example, when you release a new application to users, it might increase the load on the DNS service Monitoring the response of the DNS service will show

a decrease in performance as the client load increases Although the DNS service might currently comply with the design specifications, monitored data shows a trend indicating that redesign is necessary to support this new application

If you must design your management plan to predict the need for future changes to the design specifications, you must include processes for trend analysis by using the monitored data

Slide Objective

To describe the possible

methods of anticipating the

need for changes to the

services network design

Lead-in

In your strategy, you must

include the processes

necessary to anticipate

when design changes will

be required

Note

Identifying Management Processes

Status of the Services

Analysis of Relevant Data

Response to Service Variations

Status

Analysis Response

You must design processes in your management plan to provide feedback and control of the network services infrastructure For example, you need

immediate warning when a required service stops so that the appropriate action can be taken to restore operation

Design the processes for your management plan to:

Obtain the current status of the services or the services infrastructure

Analyze collected data to verify service operation and compliance with the design, and use trend analysis to predict when compliance will be

compromised

Respond to service variations to bring services back into compliance

Any plan to monitor and respond to service variations is often part of a larger management system, such as Microsoft Systems Management Server, or third-party management solutions

The acquisition of status information, along with the analysis of data, can be automated or manual

You must design processes

in your management plan to

monitor the status of the

services, analyze collected

data, and respond to service

variations

Note

Generating Information on the Status of the Services

Data Collection Strategies

Tools and Utilities

Performance Logs and Alerts

Discussion: Acquiring Data with Logs and Alerts

SNMP

Event Logs

Scripting and Programming Solutions

Windows Management Instrumentation

To obtain the operational status of a service requires information about individual service providers and network conditions, and verification that client requests receive appropriate responses When the data available from a single source is not extensive enough to give a complete picture of service operation, you can use a combination of several tools and sources to derive the status

To obtain the necessary information for assessing a service, you can use the following sources:

Data collection strategies

Tools and utilities

Performance Logs and Alerts

Simple Network Management Protocol (SNMP)

Event logs

Scripting and programming solutions

Windows Management Instrumentation (WMI)

Slide Objective

To describe how to establish

the status of the services

Lead-in

You can use a combination

of tools and sources to

obtain status information

about the individual service

providers and the overall

network

Data Collection Strategies

In-band data collection The status data flows across the same network that

is used for services and user data This data flow will impact the network if large amounts of data are collected, or network failures occur

Out-of-band data collection The status data flows through separate logical

or physical network connections The data collection network is not affected

by failures in the network being used for services and user data

Select in-band data collection when the network infrastructure is tolerant, or has redundant paths Use an out-of-band strategy when the network

failure-infrastructure is not fault tolerant, and the network failures would prevent data collection

Slide Objective

To describe the strategies

available for the collection of

status information about

services

Lead-in

You need to design

strategies to accumulate

status information about

services and the overall

network

Centralized Data Collection

In a centralized monitoring strategy, the status data is accumulated and analyzed at a central location This central location can be a management station or a central node within a larger management system; it is typically a host running a set of management tools and programs Centralized data collection increases network usage, which can degrade network performance In the case of a network failure, no status data will be available

If the centralized data collection strategy is designed to operate even when

network and node failures exist, then you must plan to use out-of-band data

collection This means providing different paths for data collection For example, you can use a series of dial-up modems, or Integrated Services Digital Network (ISDN) connections, that are not part of the normal data network for data collection

Distributed Data Collection

A distributed monitoring strategy accumulates the data on many nodes within the services infrastructure This accumulation allows the data to be processed before being sent to a management node, thereby significantly reducing the amount of data that is processed at the management node Collecting the status

at distributed locations allows localized responses to failures This can be important when the strategy must allow for the independent operation of locations when network failures occur

Generated Events

Event notification requires that the monitored service provide information about its current status, or that some external software is used to monitor the service for status changes Active service monitoring can generate events, send event notification, and in some cases, automatically restart a service

Performance Logs and Alerts events

System Monitor allows events to be generated by running an application when set thresholds are exceeded This allows status information to be written to a log file, thereby providing an event that is sent directly to the operations staff or to

an intermediary monitoring application

Service monitor events

The service monitors available for use depend on which products are installed Service recovery and monitoring is built into the Windows 2000 operating system and is provided in products such as Microsoft Exchange Server On detecting a failure, service monitors restart the failed services, restart the server,

or run a program to send notification of failure events

SNMP events

Adding SNMP to Transmission Control Protocol/Internet Protocol (TCP/IP) allows use of SNMP Management Information Base (MIB) definitions to assess the current service operation When SNMP is installed on a Windows 2000–based computer, SNMP traps may be generated based on the events written to the Event logs and defined in the MIB for that particular service

Tools and Utilities

Status Information

Tools and Utilities

WAN Link

Router

You can use command-line network tools and utilities to test the status of both the services and the network infrastructure You can use the information collected by these tools and utilities to analyze service and network operation and variation You can use the tools and utilities interactively or store their output in files for later analysis

You can use the following tools interactively to provide status information:

Network Monitor A tool used to monitor the network data stream for all of

the information (called frames or packets) that is transferred over a network

The Network Monitor supplied with Windows 2000 captures data sent to and from the computer on which it is running The version of Network Monitor available with Microsoft Systems Management Server can capture all network data

Netdiag A utility that performs a series of tests to isolate networking and

connectivity problems; it is also used to determine the functional state of your network client Netdiag does extensive testing of the computer on which it is run, including checking the availability of WINS and DNS Netdiag is installed with the support tools, which are available in the

\Support\Tools directory of your Windows 2000 CD

Ping A utility used to troubleshoot IP-level connectivity Ping allows you to

specify the size of packets to use (the default is 32 bytes), how many to send, whether to record the route used, what Time to Live (TTL) value to use, and whether to set the "don't fragment" flag Ping provides a minimum average and maximum roundtrip time (RTT), which is useful to analyze where routing delays occur

Tracert A route-tracing utility that displays a list of nearside router

interfaces from the routers along the path between a source host and a destination Tracert uses the IP TTL field in Internet Control Message Protocol (ICMP) Echo Requests and ICMP Time Exceeded messages to determine the path from a source to a destination through an IP

internetwork

Slide Objective

To describe the tools and

utilities that can be used to

generate network and

service status information

Lead-in

You can use a variety of

network tools and utilities to

analyze the operational

status of the network

services

Pathping A route-tracing tool that combines the features of Ping and

Tracert with additional unique information Over a period of time, Pathping sends packets to each router on the path to a final destination, and then computes results based on the packets returned from each hop Pathping shows the degree of packet loss at any given router or link, so you can pinpoint which routers or links might be causing network problems

Nslookup A utility used for troubleshooting DNS problems, such as host

name resolution failure Nslookup displays a command prompt and shows the host name and IP address of the local DNS server You can then perform interactive queries to test DNS name resolution

Netstat A utility used to display protocol statistics and current TCP/IP

connections You can display the connection status and throughput statistics for TCP/IP interfaces in the computer

Nbtstat A utility that displays protocol statistics and current TCP/IP

connections that use NetBIOS over TCP/IP (NetBT) When a network is functioning normally, NetBT resolves NetBIOS names to IP addresses

Performance Logs and Alerts

Server Performance

Network Performance

Infrastructure Performance

Centralized Collection

Distributed Collection

System Monitor, which is found within the Performance Console, allows you to obtain real-time data and collect logs The Performance Console also includes Performance Logs and Alerts to provide logging and notification of changes in

a service It does this by setting triggers on appropriate counters You can automate the collection process by specifying a schedule

System Monitor and Performance Logs and Alerts support a large number of objects, and can access counters covering many aspects of an object’s operation You can select the objects and counters to suit your particular infrastructure DHCP, WINS, DNS, and RAS Objects exist to supply the status

on these services

System Monitor log files can be generated on individual servers, or the data can

be obtained from multiple servers by a single instance of System Monitor, and written to a centralized log To ensure the smallest file sizes, always log data by using the binary format

You can select a strategy for data collection:

Centralized, if the number of counters is low, the collection interval is long,

Slide Objective

To describe how

Performance Logs and

Alerts can be used to obtain

data and trigger alerts

Lead-in

You can use Performance

Logs and Alerts to obtain

real-time data, and to collect

data logs

Note