Transcript Type wlbs display at the command prompt and press ENTER

Module 10:
Network Load
Balancing Cluster
Administration
Overview

Command Line Administration

Programmatic Management Solutions

Microsoft® Application Center Server 2000

Administration of a Network Load Balancing cluster can require
managing many individual hosts in addition to the single logical
cluster. You can perform administrative tasks at each individual
host, but performing remote administration can allow you to use a
more centralized approach.

For example, a large n-tiered Web site with multiple Network Load
Balancing clusters that you configure by using round robin DNS
entries requires administration of a potentially large number of
hosts. To provide efficient administration from a central location
requires the use of remote host administration. A solution that
provides a centralized administrative capability can include the use
of Wlbs.exe or applications and tools that are developed
specifically for the task.

In this module you will learn how to administer a Network Load
Balancing cluster by using Wlbs.exe and other programmatic
solutions.
After completing this module, you will be able to:

Utilize the command line to administer the Network
Load Balancing cluster.

Manage the Network Load Balancing cluster with
scripting tools.

Describe the feature sets of Microsoft® Application
Center 2000.
 Command Line Administration

Wlbs.exe Commands

Cluster and Host Commands

Cluster Control Commands

Setting Cluster and Host Operations

Setting Rule-based Operations

Wlbs.exe provides direct interaction with the Network Load
Balancing cluster both as a whole or with the individual host
members. In addition to providing the capability of stopping and
starting a cluster, Wlbs.exe provides commands to examine cluster
status, control the cluster, and enable and disable port rules.

You can achieve automation of tasks involving the Network Load
Balancing cluster or the individual cluster members by using
Wlbs.exe in .bat or .cmd command files. The degree to which this
type of automation is successful will depend on the tasks requiring
execution; and because Wlbs.exe provides little feedback on
operation performance, which can require you to create scripted
solutions by using Microsoft Windows® Management
Instrumentation (WMI) to monitor performance.

For example, if a cluster is scheduled to stop at the same time each
Friday to perform a backup, you can automate the backup task with
a simple batch file. The automated batch file stops the cluster and
starts the backup, restarting the cluster on backup completion.
Wlbs.exe Commands

Wlbs.exe Command Line Syntax

Wlbs.exe Commands

Wlbs start

Wlbs stop

The Wlbs.exe program operates on Network Load
Balanced hosts or on any remote computer that is
running Microsoft Windows 2000 that accesses the
cluster over a local or wide area network. You can also
use Wlbs.exe to issue commands to a single host or an
entire cluster remotely; however, firewalls or
intermediate security devices may require configuration
to allow communication to the cluster.
Wlbs.exe Command Line Syntax

The command line for Wlbs.exe uses the syntax
wlbs command [cluster [:host] [remote options]]
and is installed in the %Systemroot%\System32 folder.

You can omit the cluster, host, and remote options when
running Wlbs.exe directly on a cluster host. In this
case, the command applies only to the local cluster
host. To address the cluster as a whole or a different
host within the cluster, you must also specify the target
cluster, or target cluster and specific host together.

The following table provides examples of how to
address the cluster.
Cluster and Host
Parameter
Example
Action
(omitted)
wlbs command
Invokes command on
current cluster host
Cluster
wlbs command
mycluster
Invokes command on
all cluster hosts
cluster:host
wlbs command
\mycluster:host1
Invokes command on
a specific cluster host
Wlbs.exe Commands

You can configure Network Load Balancing hosts to join
the cluster automatically upon startup or to wait for the
wlbs start command by enabling the initial state option
in the Network Load Balancing Properties dialog box.
You can use the wlbs start command with the wlbs stop
command to change cluster parameters for the local
host without taking the entire cluster offline.
Wlbs start

The wlbs start command will attempt to start the actions
of the Network Load Balancing driver on the local host.
When you start a host, there is communication between
the local host and current members of the cluster
(heartbeat communications). If you have properly
configured the local host, it will successfully join the
cluster.

Note: You can restart cluster operations on the local
cluster host by either restarting the computer or typing
wlbs start at the command prompt. You can restart
cluster operations on all of the cluster hosts by typing
wlbs start followed by the cluster Internet Protocol (IP)
address or cluster name.
Wlbs stop

The wlbs stop command will stop the actions of the
Network Load Balancing driver on the local host. When
you stop the local host, it no longer participates in the
cluster. The wlbs stop command can be described as a
command to a host to leave the cluster.

You can use the following procedure to stop operations
on a specific host or the entire cluster by adding the IP
address or the cluster name after the wlbs stop
command.
To stop Network Load Balancing
1.
Click Start, point to Programs, point to Accessories,
and then click Command Prompt.
2.
Type wlbs stop at the command prompt. Cluster
operations are immediately stopped on the local
cluster host.
3.
If you want to stop cluster operations on all cluster
hosts, type wlbs stop followed by the cluster IP
address or cluster name.

Note: When you use the wlbs stop command any client
connections already in progress are interrupted. To
avoid interrupting active connections, consider using
the drainstop cluster control command. Drainstop will
be explained in a later topic within this module.
Cluster and Host Commands

Specifying Cluster Parameters

Specifying Host Parameters

Configuring Remote Options

Remote Operations

You can use Wlbs.exe commands to administer a single
host or all of the hosts within the cluster by using the
appropriate cluster and host parameters as part of the
Wlbs.exe command line syntax.
Specifying Cluster Parameters

The cluster parameter can be either the cluster’s full
Internet name or the cluster’s primary IP address. If you
omit the host parameter, the command applies to all of
the hosts within the cluster and is multicast or
broadcast to the hosts; otherwise, the command applies
to the specified host within the cluster. You use the
following commands to specify the cluster parameters.
Wlbs stop webcluster

This command will stop the actions of the Network Load
Balancing driver on all of the member hosts in the
cluster called webcluster. When the hosts are stopped,
the cluster is stopped.
Wlbs stop webcluster:5

This command will stop the actions of the Network Load
Balancing driver on the member host with a unique
identifier of 5 in the cluster called webcluster. When the
host is stopped, it is no longer participating in the
cluster.
Specifying Host Parameters

You can specify host names by using their unique host
priorities that you have assigned in the Network Load
Balancing Properties dialog box or use the special host
priority value 0 (zero) to refer to the default host within a
cluster.

Syntax examples are shown in the following table.
Example
Description
mycluster:host1
Internet host names
w.x.y.z:w.x.y.z.
IP addresses
mycluster:w.x.y.z
Mix of name and IP address
mycluster:1
Host 1 in mycluster
mycluster:0
Default host in mycluster
Mycluster
All of the hosts in mycluster
Configuring Remote Options

You can configure the Network Load Balancing driver
with remote operations enabled or disabled. If you
enable remote operation, you can require a password to
permit acceptance of remote commands by the driver.
When using Wlbs.exe to execute commands on a
remote driver instance, you must specify the password
on the command line. You use the following commands
to configure remote options.

Wlbs stop webcluster /doitnow
This command will stop the actions of the Network Load
Balancing driver on all of the member hosts in the
cluster called webcluster, where the remote password is
doitnow.

Wlbs stop webcluster: 5 /doitnow
This command will stop the actions of the Network Load
Balancing driver on the cluster host with a unique
identifier of 5 in the cluster called webcluster, where the
remote password is doitnow.
Remote Operations

Wlbs.exe uses either or both of the User Datagram
Protocol (UDP) ports 1717 or 2504 on the cluster IP
address. By default, remote commands are not
accepted by the cluster; these must be explicitly
enabled on each cluster member. Remote operations
are secured by using a password stored locally in the
registry on each host participating in the cluster.

Important: It is not recommended that you allow remote
control of a cluster or cluster hosts from a public
network. When you must permit remote control
operations, isolation of a cluster by using a firewall is
recommended with UDP ports 1717 and 2504 blocked to
the public network to prevent unauthorized access.
Cluster Control Commands
Cluster Command Example
Description
wlbs help
Returns Help information
wlbs query mycluster
Queries the status of all hosts in
mycluster
wlbs ip2mac mycluster
Displays MAC addresses corresponding
to mycluster

You can use the following control commands for a
Wlbs.exe cluster to display the host priorities, access
the help files if they are installed on your computer, and
display the media access control (MAC) address or data
about the cluster status.

Display. The display command can be invoked on the
cluster host only and displays extensive information
about your current Network Load Balancing parameters,
cluster state, and past cluster activity.

Help. The help command displays Network Load
Balancing online Help information if available on the
local computer.

Note: The display command shows the last several
event log records that Network Load Balancing
produced, including the binary data attached to those
records. This command is designed to assist in
technical support and debugging.

Ip2mac. The ip2mac command displays the MAC
address corresponding to the specified multicast or
unicast cluster name or IP address.

Query. The query command displays the current cluster state and
the list of host priorities for the current members of the cluster. The
possible states are:



Converged. The cluster has converged, and the responding host is
not the default host.
Converged as default. The cluster has converged, and the
responding host is the current default (the highest priority host that is
not performing a drainstop). The default host handles network traffic
for all of the Transmission Control Protocol (TCP) / UDP ports that
are not covered by the port rules.
Converging. The cluster is currently attempting to converge to a
consistent state. Prolonged convergence usually indicates a
problem with cluster parameters.

Draining. The cluster has converged, and the responding host is
draining active connections prior to stopping cluster mode.

Unknown. The responding host has not started cluster operations
and cannot determine the cluster’s state.
Setting Cluster and Host Operations

Drainstop

Reload

Resume

Suspend

By using the following Wlbs.exe cluster control
commands, you can temporarily stop cluster operations
and then resume command without restarting the
cluster. During a draining operation you can stop all of
the IP traffic to a specified host or reload the current
parameters of the Network Load Balancing driver.

Drainstop. The drainstop command disables all new
traffic handling on the specified hosts that enter
draining mode to complete existing connections. While
draining, hosts remain in the cluster and stop their
cluster operations only when there are no more active
connections. You can terminate the draining mode by
stopping the cluster mode with the stop command or by
restarting new traffic handling with the start command.

Reload. You can invoke the reload command on the
cluster host only and reload the Network Load
Balancing driver’s current parameters. The cluster
operations on the local host are stopped or restarted if
necessary.

Resume. The resume command resumes cluster
operations after a previous suspend command. It does
not restart cluster operations, but enables handling of
cluster control commands, including remote control
commands.

Suspend. The suspend command suspends all of the
cluster operations until the resume command is issued
and temporarily stops cluster operations. It overrides
any remote control commands that the administrator
may issue. The cluster ignores all subsequent cluster
control commands except resume and query.
Setting Rule-based Operations

Disable

Drain

Enable

The Network Load Balancing cluster must have rules to
specify the response to TCP and UDP traffic for the
cluster IP address. The following command is an
example of how you can control the rules that are
associated with the specified ports by using Wlbs.exe.

wlbs disable 80. The wlbs disable 80 command
disables the local host’s handling of new network traffic
for the Web server port (port 80).

The following Wlbs.exe commands allow you to control
the port rules:

Disable. The disable command disables and
immediately blocks all traffic handling for the rule
whose port range contains the specified port. All ports
that the port rule specifies are affected. If all is specified
for the port, this command is applied to the ports that all
of the port rules cover. All active connections on the
specified hosts are blocked to IP traffic. To maintain
active connections, use the drain command instead.
The drain command has no effect on IP traffic if the
specified hosts have not started cluster operations.

Drain. The drain command disables new traffic handling
for the rule whose port range contains the specified
port. All ports that the port rule specifies are affected. If
all is specified for the port, this command is applied to
the ports that all of the port rules cover. The specified
host will not allow new connections and will maintain all
of the active connections. To disable active
connections, use the disable command instead. The
disable command has no effect on IP traffic if the
specified hosts have not started cluster operations.

Enable. The enable command enables traffic handling
for the rule whose port range contains the specified
port. All ports that the port rule specifies are affected. If
all is specified for the port, this command is applied to
the ports that the port rules cover. This command has
no effect on IP traffic if the specified hosts have not
started cluster operations.
Programmatic Management Solutions

Network Load Balancing WMI Provider

Using the WMI SDK Tools

Microsoft Windows Scripting Host

Web-based Enterprise Management (WBEM) provides
uniform access to management information. Such
management information includes data on the state of
system memory, inventories of currently installed
applications, and other information on service and
application status.

Management information can be sourced from the
computer registry or direct from a service by using a
WMI provider. For example, the WMI provider for
Network Load Balancing permits configuration of
cluster and host parameters and setting of port rules.

Implemented for Microsoft Windows platforms, WMI
technology enables systems; applications, networks,
and other managed components to be represented by
using the Common Information Model (CIM). This model,
which the Desktop Management Task Force (DMTF)
designed, can represent anything in a managed
Windows environment regardless of the data source
location.

CIM is a data model, a conceptual view of the
environment that unifies and extends existing
instrumentation and management standards by using
class-based, object-oriented, constructs and design.

WMI supports a powerful set of base services that
include query-based information retrieval systems and
event notification. Access to these services and to the
management data is made possible with a Component
Object Model (COM) based programming interface that
you can use with a range of scripting and programming
languages.
Network Load Balancing WMI Provider
Microsoft
Management
Console (MMC)
Management
Application
Snap-In
DCOM
Snap-In
DCOM
CIM Object
Repository
CIM Object Manager
Object Providers
WDM
WDM Kernel
Objects
RPC
DMI
Objects
WIN32
Win32®
Objects
MicrosoftNLB
Network
Load Balancing

A WMI provider is an architectural element of Windows
Management Instrumentation. WMI defines a unified
architecture or schema for describing, accessing, and
instrumenting objects. Part of this architecture is a large
database of WMI classes or schemas that are used to
carry out remote management tasks on specific objects.

You can use WMI provider to manage the Network Load Balancing driver.
The WMI provider exposes the configuration and status information as part
of the CIM database and provides:

An access mechanism to monitor, command, and control any entity through
a common, unifying set of interfaces, irrespective of the underlying
instrumentation mechanism.

A logically organized, consistent model of Windows 2000 operating system
operation, configuration, and status.

A COM application-programming interface (API) for providing and accessing
management information.



A powerful event mechanism that allows management events to be
asserted and associated with other management information. These
notifications can also be forwarded to local or remote management
applications.
An interactive query language that enables detailed queries of the
information model.
A scriptable API that supports several languages, including Microsoft Visual
Basic®; Visual Basic for Applications; Visual Basic Scripting Edition
(VBScript); Microsoft JScript®, and Perl.
Using the WMI SDK Tools
Hosted in Web Browser,
accessing WMI CIM data
Name
Disable
Drain
DrainStop
Enable
Resume
SetPowerState
Start
Stop
Suspend
Method Qualifiers…
Object Qualifiers…
Execute methods
to change state of
the cluster
Allows interactive configuration of
Network Load Balancing by writing
to CIM database

You can access management data in an enterprise
environment by using the WMI Common Information
Model object browser or the WMI Object Browser. These
tools are available in the WMI Software Development Kit
(SDK). The focus of this topic is on the WMI Object
Browser shown in the preceding graphic.
WMI Object Browser

The WMI Object Browser contains an Object Explorer
window that shows the hierarchy of instances that you
find in a defined namespace by following association
links. The hierarchy is shown as a graphical tree within
the Object Explorer window. The tree shows regular
objects and grouping nodes. Grouping nodes are not
objects themselves but are a way to organize objects.
The Object Explorer window uses the icons next to the
names to indicate the type of object or node (also
referred to as host) as shown in the graphic.
WMI Common Information Model Object Browser

WMI Common Information Model (CIM) object browser is an
application designed primarily for use by developers, but
administrator can use it to view CIM data. Using this application,
you can:

Display the object tree that is contained in a specified CIM
repository.

Display properties, methods, and associations for a selected object.

Display custom views of object data.

Display instances of grouped objects.

Display property and object qualifiers.

Execute methods on a selected object.

Edit property values and object and property qualifiers.
Demonstration: Using the WMI Object Browser
Microsoft Windows Script Host
C:\WINNT\System32\cmd.exe
C:\>test.vbs_
Registry – File
Associations
Windows Scripting Host
Cscript.exe
Wscript.exe
Scripting Engines
VBScript, JScript
COM Objects

By using Windows Script Host you can write noninteractive
scripts for logging on, administering, and automating the
Network Load Balancing cluster hosts. Scripts are
commonly written in Microsoft Visual Basic® Scripting
Edition (VBScript) or Microsoft Jscript®. Other languages,
such as Perl, are also supported.

You can run Windows Script Host from either the Windowsbased host (WSCRIPT.EXE), or the command shell-based
host (CSCRIPT.EXE). The scripts are typically automated
with Scheduled Tasks. The scripts can run without a user
logged on, and with no access to the visible desktop. You
can also use script code in Web browser-based applications
as client-side script or implemented as server-side Active
Server Pages (ASP) script code by using Internet
Information Services (IIS).

The scripting languages support Component Object Model
(COM) automation objects, which allow the script to create
instances of both product and operating system service
objects, and pass data between them. The Windows Script
Host Reference documents elements, methods, objects, and
properties with which you can accomplish tasks such as:

Instantiation of COM components.

Printing of messages to the screen.

Mapping network drives.

Connecting to and controlling printers.

Retrieving and modifying environment variables.

Reading and modifying registry keys.

The Scripting API for WMI is a set of objects consisting of properties,
methods, and events that you can use to develop script and Microsoft
Visual Basic applications that view information about or control managed
objects, such as Network Load Balancing. The following code segment
lists all processes running on the local system and illustrates:



the use of enumeration
direct access to a CIM property (in this case the Name property
of an instance of the CIM class Win32_Service) as if it were an
automation property
local access for each Process in
GetObject("winmgmts:{impersonationLevel=impersonate}")
.InstancesOf ("Win32_process")
WScript.Echo Process.Name
Next
Demonstration: Examining and Executing Scripts

Using scripts you can list all of the processes and
services running or view the Event Log for the Network
Load Balancing cluster.
List all Processes Running on the Local System

The following code segment illustrates the use of
enumeration, direct access to a CIM property (in this
case the Name property of an instance of the CIM class
Win32_Service) as if it were an automation property, and
local access.
for each Process in
GetObject("winmgmts:{impersonationLevel=impersonate}")
.InstancesOf ("Win32_process")
WScript.Echo Process.Name
Next
List all Services Running on the System on
HostProducts1

The following code segment illustrates the use of
enumeration, direct CIM property access, and remote
access to a Windows 2000 system.
for each Service in
GetObject("winmgmts:{impersonationLevel=impersonate}!
//ServerName").InstancesOf ("Win32_service")
WScript.Echo Service.DisplayName
Next
Listen for NT Event Log Events on the Local
System

The following code segment illustrates the use of
registration of a temporary event consumer on a
specified event filter, and direct CIM property access.
on error resume next
set locator = CreateObject("WbemScripting.SWbemLocator")
'Access to the NT event log requires the security privilege
locator. Security_.Privileges.AddAsString
"SeSecurityPrivilege“
set events = locator.ConnectServer().ExecNotificationQuery
_
("select * from __instancecreationevent where
targetinstance is a 'Win32_NTLogEvent'")
if err <> 0 then
WScript.Echo Err.Description, Err.Number, Err.Source
end if
' Note this next call will wait indefinitely - a timeout
can be specified
WScript.Echo "Waiting for NT Events..."
WScript.Echo ""
do
set NTEvent = events.nextevent
if err <> 0 then
WScript.Echo Err.Number, Err.Description, Err.Source
Exit Do
elseif NTEvent.TargetInstance.Message <> Empty then
WScript.Echo NTEvent.TargetInstance.Message
else
Wscript.Echo "Event received, but it did not contain
a message."
end if
loop
WScript.Echo "finished"
Microsoft Application Center 2000 Server
Web Cluster
COM+
Application Cluster
Server A
Server 1
Server B
Server 2
Internet
Router
Firewall
Database
Cluster
NLB
Clients
CLB
Server C
Server 3

Microsoft Application Center 2000 provides for scaling and
managing a broad range of Web-based business
applications. Its feature set includes Network Load
Balancing, Component Load Balancing and server
synchronization features. Application Center 2000 Server
Version 1 is integrated with core Windows 2000 Server
services and extends the core operating system services by
providing tools, such as application publishing.

Application Center 2000 provides the following features:





Addresses issues related to scaling out Web-based
applications across multiple servers.
Accommodates deployment of content and
applications across cluster members.
Load balances and distributes connections across a
cluster.
Proactively monitors health and performance
metrics for cluster members.
Provides performance testing to enable scaling for
next-generation applications that are based on the
Microsoft .NET strategy.
Lab A: Network Load Balancing Administration
Objectives

After completing this lab, you will be able to:

Collect information on cluster operations.

Enable remote operations on a cluster member.

Start, stop, and drainstop a cluster member.

Start and stop a cluster.

Suspend and resume a cluster host.

Drain, enable, and disable a cluster host.

Modify and use a script to control cluster operations.
Exercise 1: Examining Cluster Status and Controlling
Cluster Operations

All students will complete this procedure and will work
with a partner. You will collect information on Network
Load Balancing.
To examine and record information on the status of
the 2-host cluster

Click Start, click Run, type cmd in the Open dialog
box, an then click OK to open a command prompt
window.
1.
Type wlbs at the command prompt, and then press
ENTER to execute Wlbs.exe.
2.
Read the help screen and examine the syntax that is
required to use Wlbs.exe.
3.
Type wlbs query at the command prompt, and then
press ENTER.
4.
Record the current status for the cluster:
6.
Type wlbs display at the command prompt and press
ENTER.
7.
Record the last event message for the cluster, the Host
Priority and Dedicated IP address.

Does the information that you recorded apply to the
virtual cluster or to the individual cluster member on
which you ran Wlbs?
To enable remote operations on the cluster

Perform the following task on both student computers.
1.
Type wlbs stop yourclusterIP at the command prompt
and press ENTER.
2.
Record the information provided.

Did the cluster stop?
3.
On the lowest number student ID computer,
reconfigure the Network Load Balancing Cluster
Parameters to enable remote control, and close the
configuration dialog box. Remove any passwords from
the dialog boxes.
4.
Type wlbs stop yourclusterIP at the command prompt
and press ENTER.
5.
Record the information provided.

Did the cluster stop?
6.
On the highest number student ID computer, type wlbs
query at the command prompt and press ENTER.
7.
Record the information provided.

Is this cluster host stopped?
8.
On the highest number student ID computer,
reconfigure the Network Load Balancing Cluster
Parameters to enable remote control, and close the
configuration dialog box. Do not enter a password in
the dialog boxes.
9.
Type wlbs start yourclusterIP at the command prompt
and press ENTER.
10.
Record the information provided.

Did the cluster start?
11.
Were there differences in the responses from both
hosts?
12.
On both student computers, type wlbs drainstop at the
command prompt and press ENTER.
13.
Record the response from the command.
14.
On both student computers, type wlbs query at the
command prompt and press ENTER.
15.
Record the convergence state of the cluster.

What can you say about the status information that is
supplied when the host is stopped? Compare your
answer with your partner’s.
16.
On both student computers, type wlbs start at the
command prompt and press ENTER.
17.
On the lowest number student ID computer, type wlbs
suspend at the command prompt and press ENTER.
18.
Record the information provided.
19.
On the highest number student ID computer, type wlbs
stop yourclusterIP at the command prompt and press
ENTER.
20.
Record the information provided.

Did the cluster stop?
21.
On the lowest number student ID computer, type wlbs
start yourclusterIP at the command prompt and press
ENTER.
22.
Record the information provided.

Did the cluster start?
23.
On the lowest number student ID computer, type wlbs
resume at the command prompt and press ENTER.
24.
Record the information provided.
25.
On the lowest number student ID computer, type wlbs
start at the command prompt and press ENTER.
26.
Record the information provided.
To enter a new rule on a cluster host and view the
convergence state
1.
On the lowest number student ID computer, enter a
new rule in the Port Rules tab for this cluster member.
Use Port 8080, Both, with the affinity set to None.
2.
Click OK to close the entire configuration dialog box to
activate this rule.
3.
On the highest number student ID computer, type wlbs
query at the command prompt and press ENTER.
4.
Record the information provided.
5.
Explain why the cluster will no longer reach a
converged state.
6.
On the highest number student ID computer, enter a
new rule in the Port Rules tab for this cluster member.
Use the same setting that is used on your partner’s
computer.
7.
Close the entire configuration dialog box to activate
this rule.
8.
On the lowest number student ID computer, type wlbs
query at the command prompt and press ENTER.
9.
Record the information provided.

10.
Does the cluster now reach a converged state?
Close all of the windows.
Exercise 2 Using WMI Object Browser

All students will complete this procedure and will work
with a partner. You will collect information on Network
Load Balancing.
To install the WMI SDK and use the WMI Object Browser to
examine and update Network Load Balancing information on
a local host
1.
Insert your student CD and use Windows Explorer to open the
WMISDK folder on the CD.
2.
Double-click the Wmisdk.exe program and follow the instructions
to install the SDK. Accept all default settings during the install
process.
3.
Start the WMI Object Browser by clicking Start – Programs – WMI
SDK – WMI Object Browser. The Object Browser tool will start and
run in an instance of Internet Explorer.
4.
Enter the namespace name (by default this is root) to connect to
the local computer, or click on the Browse for Namespace icon to
enter a computer name and namespace to connect to. Click
Connect to continue.
5.
If you selected root, browse to the MicrosoftNLB namespace and
click OK in the Browse for Namespace dialog box.
6.
Examine the entries under MicrosoftNLB_Node.Name.
7.
Select MicrosoftNLB_Node.Name and examine the
Properties and Methods tabs in the right-hand frame.
8.
Select CIM_ElementSetting.Setting, right-click on a
data column in the right-hand frame and click Go To
Object.
9.
Modify the AliveMessageTolerance from the default
value of 5 to 6.
10.
Select MicrosoftNLB_Node.Name to refresh the window and click
yes to update the value in the registry. Return to
CIM_ElementSetting.Setting.
11.
Use Wlbs display to check the configuration of the cluster
member. Did the value get updated for the cluster member?
12.
Select CIM_ElementSetting.Setting, right-click a data column in
the right-hand frame and click Go To Object.
13.
Modify the AliveMessageTolerance from the value set to 5.
14.
Select the Methods tab and right-click LoadAllSettings, click
Execute Method. (Network Load Balancing will be stopped and
restarted with the values stored in the registry.)
15.
16.
Use Wlbs display to check the configuration of the
cluster member.

Was the value updated for the cluster member?

What do you surmise from the preceding answer?
Exit all of the windows.
Review

Command Line Administration

Programmatic Management Solutions

Microsoft Application Center Server