2.08 iSCSI Initiator Source IP incorrect in Persistent Target Details
After a reboot of the server, the Persistent Target Details shows the incorrect Source IP.
Example:
I have three network cards (NICs) utilized in my server. The first one for LAN access and the other two for iSCSI traffic . I setup the connection such that the iSCSI connections are persistent. After a reboot of the server, all the sessions are successfully connected. However, when I click on the details of the Persistent Targets, The Source IP is showing the LAN IP. I have double-checked my configuration and even reproduced the issue on different hardware.
While this is strictly a cosmetic issue at this point. I wonder if it could possibly affect something in the background that has not presented itself yet.
Also, has anyone else seen this issue?
Config:
Windows 2003 Server SP2
2.08 Initiator
All Replies
Hi dswilder,
Do you have multiple network cards or multiple IP addresses on the iSCSI target that you connect?
Do the host of iSCSI initiator and iSCSI target have static IP address or they got IP addresses from a DHCP server?
Did you specify the static IP address of iSCSI inititator and iSCSI target in both sides of configuration?
I build a test environment locally with static IP address without the issue.
Can you please run "ipconfig /all" on both of the iSCSI inititator and iSCSC target to dump the result for our reference?
Meanwhile, please take a screenshot of the Persistent Target Details before and after you reboot the server so that we can analyze it.
Note: you may send the result to us via tfwst@microsoft.com
I appreciate your time and effort.
Best Regards,
David Shen
This posting is provided "AS IS" with no warranties, and confers no rights.- Unmarked As Answer bydswilder Thursday, November 12, 2009 3:10 PM
- Marked As Answer byDavid Shen - MSFTMSFT, ModeratorThursday, November 12, 2009 9:51 AM
The iSCSI target does have multiple ports to connect to. All of the IP addresses in this configuration are Static.
I mailed the screenshots to tfwst@microsoft.com.
It seems to be random in nature as sometimes it comes up okay. And other times it shows half of the tragest with the incorrect Source IP.
IP addresses of the Target (not MS-target)
192.168.0.123
192.168.1.124
192.168.1.224
192.168.0.223
From the Initiator
C:\>ipconfig /allWindows IP Configuration
Host Name . . . . . . . . . . . . : patrick
Primary Dns Suffix . . . . . . . : test.domain.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : test.domain.com
Ethernet adapter Heartbeat:Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
Physical Address. . . . . . . . . : 00-1E-C9-3C-BE-96Ethernet adapter 192.168.0.23 A:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #2
Physical Address. . . . . . . . . : 00-10-18-4F-71-3E
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :Ethernet adapter 192.168.1.23 B:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)
Physical Address. . . . . . . . . : 00-10-18-4F-71-3C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :Ethernet adapter LAN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) #2
Physical Address. . . . . . . . . : 00-1E-C9-3C-BE-98
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.22.219.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.22.219.1
DNS Servers . . . . . . . . . . . : 172.22.212.92
