iSCSI errors continue after removing inaccessible target portal

Posted by Ansgar Wiechers on Server Fault See other posts from Server Fault or by Ansgar Wiechers
Published on 2012-10-10T14:11:06Z Indexed on 2012/10/22 23:04 UTC
Read the original article Hit count: 734

By mistake I entered an iSCSI target portal address in the iSCSI Initiator on one of our virtual servers that does not have an address in the network range used for iSCSI. This caused the following errors/warnings to appear in the eventlog:

Log Name:      System
Source:        MSiSCSI
Event ID:      113
Level:         Warning
Description:
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target
portal *192.168.23.42 0003260 Root\ISCSIPRT\0000_0 .

Log Name:      System
Source:        iScsiPrt
Event ID:      1
Level:         Error
Description:
Initiator failed to connect to the target. Target IP address and TCP Port
number are given in dump data.

Log Name:      System
Source:        iScsiPrt
Event ID:      70
Level:         Error
Description:
Error occurred when processing iSCSI logon request. The request was not
retried. Error status is given in the dump data.

So far that's expected beahvior, so I removed the portal from the iSCSI Initiator as described in MSKB 976072. However, the errors/warnings keep appearing every hour, even though neither iSCSI Initiator GUI nor iscscli show any portals:

C:\>iscsicli ListTargetPortals
Microsoft iSCSI Initiator Version 6.1 Build 7601

The operation completed successfully.

The problem persists after rebooting the server. Uninstalling the Microsoft iSCSI Initiator device via devmgmt.msc as well as changing the Initiator parameters like this:

[HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}]
"MaxPendingRequests"=dword:00000001
"MaxConnectionRetries"=dword:00000001
"MaxRequestHoldTime"=dword:00000005

didn't help either. Each change was followed by a reboot.

Disabling the device does prevent the errors/warnings from re-appearing, of course, but I'd rather not have to resort to this.

How can I prevent those errors and warnings from appearing (short of disabling the initiator device or re-installing the server)? What am I missing?

Environment: The virtual machine runs on a Hyper-V cluster managed by SCVMM 2012. Hosts and guests run Windows Server 2008 R2 SP1. The physical machines are Dell PowerEdge M710HD blades.

© Server Fault or respective owner

Related posts about windows-server-2008-r2

Related posts about iscsi