Monitors the Network Load Balancing Service on ISA Server 2006
Monitors the Network Load Balancing Service on ISA Server 2006.
When using Network Load Balancing Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority.
As a security best practice, consider using Run as to perform this procedure.
To perform these procedures, you must be a member of the Administrators group, or you must have been delegated the appropriate authority. If you are configuring a cluster or host by running Network Load Balancing Manager from a computer that is not part of the cluster, you do not need to be a member of the Administrators group on that computer.
To start Network Load Balancing Manager, open a Command Prompt. From the command window, type NLBMgr, and then press ENTER:
If Network Load Balancing Manager is not used to enable Network Load Balancing, you must manually add the cluster's IP address to the TCP/IP settings on each host. For more information, see "Set up TCP/IP for Network Load Balancing" in Related Topics below.
To install and configure Network Load Balancing, you must use an account that is in the Administrators group on each host. As you install and configure each host, if you are not using an account in the Administrators group, you will be prompted to provide the logon credentials for such an account. You can set up an account that Network Load Balancing Manager will use by default by clicking Credentials in the Network Load Balancing Manager Options menu. It is recommended that this account is an account not used for any other purpose. Be sure to keep the password from expiring on the account (follow your organization's policies for password renewal).
To use this monitor, you can override the following parameters:
Enabled - Turn on or off this monitor.
Generate Alerts - Set the Flag if alerts are generated for state change conditions.
Autoresolve Alerts - Set the Flag if alerts are auto resolved (reset) for success state change conditions.
Alert Priority - Set the priority of the alerts generated like : High, Medium, Low.
Alert On State - Set the state level to trigger the alert.
Alert Severity - Set the severity of the alerts generated like : Critical, Information, Warning or to Match The Health State.
Alert Only if Service Startup Type is Automatic - Set the flag True or False. If set to False, it will trigger alerts no matter the startup type is. Default is set to True.
| Target | Microsoft.ISAServer.2006.NLB.ServerRole | ||
| Parent Monitor | System.Health.AvailabilityState | ||
| Category | AvailabilityHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | High | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Microsoft.Windows.CheckNTServiceStateMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default |
Home<UnitMonitor ID="Microsoft.ISAServer.2006.NLB.ServerRole.NLBServiceMonitor" TypeID="Windows!Microsoft.Windows.CheckNTServiceStateMonitorType" Accessibility="Internal" Target="Microsoft.ISAServer.2006.NLB.ServerRole" Priority="Normal" Remotable="true" ConfirmDelivery="false" ParentMonitorID="Health!System.Health.AvailabilityState" Enabled="onEssentialMonitoring">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.ISAServer.2006.NLB.ServerRole.NLBServiceMonitor.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='State']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState MonitorTypeStateID="NotRunning" HealthState="Error" ID="NotRunning"/>
<OperationalState MonitorTypeStateID="Running" HealthState="Success" ID="Running"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ServiceName>wlbs</ServiceName>
<CheckStartupType>true</CheckStartupType>
</Configuration>
</UnitMonitor>