Event 113, MSiSCSI - iSCSI discovery via SendTargets failed

on
If you have a Hyper-V environment and are running SCVMM 2012 or SCVMM 2008, you might notice the following Warning in the System log repeating at intervals of roughly 30 minutes:

Source: MSiSCSI
Event ID: 113
Level: Warning
Description: iSCSI discovery via SendTargets failed with error code … to target portal …

This can be caused by configuring the Microsoft iSCSI Initiator on the Hyper-V host with a Target portal as the Default Adapter, and not assigning the Microsoft iSCSI Initiator as the Adapter, in circumstances where the operating system recognises cards in the server as being Hardware iSCSI HBA’s.

An Example to Clarify the Situation

We have a HP Blade server with two HP NC553i Dual Port FlexFabric 10Gb Converged Network Adapters - these adapters are Hardware iSCSI HBA capable.
We are using the Microsoft Software iSCSI Initiator.
We configure the Discover Target Portal with the Adapter as Default.

Fig. 1: iSCSI Initiator Properties > Discovery > Target portals > showing Default Adapter being used
We get the Event ID 133 Warning every 30 minutes, which is when SCVMM’s System Center Virtual Machine Manager Agent sends a refresh to the host, which triggers the two Hardware iSCSI Adapters to try a discover via SendTargets and they fail.
What we should have done is configured the Discover Target Portal with the Local adapter as the Microsoft iSCSI Initiator.

Fig. 2: iSCSI Initator Properties > Discover Target Portal > Advanced Settings > Selecting Microsoft iSCSI Initiator as the Local adapter (notice the HP NC553i’s appear as adapters)
A Test

Test by doing a refresh of the host from SCVMM; does the Event ID 133 Warning occur?

Fig. 3: System Center 2012 Virtual Machine Manager Console > Refresh host
A Not Recommended Fix

Another way to stop the error repeating every 30 minutes would be to stop the System Center Virtual Machine Manager Agent Service on the Hyper-V host; this is not recommended as stopping the service renders SCVMM unable to manage the Hyper-V host!

Fig. 4: Services.msc > System Center Virtual Machine Manager Agent

Comments

Post a Comment