Monitors the status of the iSCSI target service
This monitor checks the state of the Microsoft iSCSI Software Target service and generates an alert if the service is not running. If the iSCSI Target service is not running, no iSCSI initiators will be able to connect to the server and iSCSI disks will not be available for use.
If the health state is unknown, monitoring has either not begun or the monitor may have been disabled for this object.
The iSCSI Target service may not be in a Running state for the following reasons:
An administrator stopped the service.
The service cannot be started due to a system failure such as low memory.
You should review other alerts from this server to identify related problems such as low memory.
Restart the iSCSI Target service by using one of the following procedures:
Restart the service in the Operations console
In the Operations console, select the appropriate server and then click the Start iSCSI Target Service task.
Restart the service on the affected server
At an elevated command prompt on the affected server, type net start wintarget and then press ENTER.
Verification
To confirm that the Server service is running, in the Operations Console, use the following procedure:
Click the Query iSCSI Target Service Status task.
This monitor automatically resets to a Healthy state after the service starts although there may be a delay of up to 2 minutes.
Target | Microsoft.Windows.FileServices.Service.iSCSITarget.6.2 | ||
Parent Monitor | System.Health.AvailabilityState | ||
Category | AvailabilityHealth | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.Windows.CheckNTServiceStateMonitorType | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.Windows.FileServices.Service.iSCSITarget.6.2.Service" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.FileServices.Service.iSCSITarget.6.2" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" TypeID="Windows!Microsoft.Windows.CheckNTServiceStateMonitorType" ConfirmDelivery="false">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.FileServices.Service.iSCSITarget.6.2.Service.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Running" MonitorTypeStateID="Running" HealthState="Success"/>
<OperationalState ID="NotRunning" MonitorTypeStateID="NotRunning" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ServiceName>WinTarget</ServiceName>
<CheckStartupType>true</CheckStartupType>
</Configuration>
</UnitMonitor>