Unsolved
4 Posts
0
1132
June 9th, 2020 16:00
MD3820i no IPV4 on 0 IN 0
I have a Dell MD3820i that I'm configuring and connecting two Hyper-V hosts to. For some reason, I can only connect to 0 IN 0 via IPV6. Static IPV4 addresses are set on the hosts and on the ports on the PowerVault and IPV4 is enabled.
When I try to create an ISCSI session via MDCU, it says not reachable for 0IN0. I can't ping that address either. I can, however, ping 1IN0 (same subnet). I also can connect to 0IN0 via IPv6.
The other host has no issues seeing 0IN1 or 1IN1 on IPv4. I changed the IP on that host to match the 0IN0 range and it too will not see it via IPV4, so it's got to be an issue with the PowerVault.
I'm just at a loss-the port obviously works since I can access it over IPv6, just not IPv4.
Any ideas? Thanks!
DiegoLopez
4 Operator
4 Operator
•
2.7K Posts
0
June 12th, 2020 08:00
Hello @js312,
I am wondering if you are experiencing this due to the default DHCP configuration of IPv4..
First, I would like you to check the Deployment Guide for the MD3820i series. On page 35 you have the guide about how to Set Up a Microsoft Host Network Using Static IP Addressing.
Also, in the very same document you can find the information regarding the Manual Configuration Of iSCSI (Page 39) and how to discover the Storage Array. Finally, make sure to read about how to perform the Target Discovery From the iSCSI Initiator Using Windows Server.
Please, check this documentation and let me know if you find it useful.
Regards
js312
4 Posts
0
June 12th, 2020 12:00
Hi @DiegoLopez
Thanks for the articles. The first definitely matches what I'm doing--the hosts have static IPs set for IPv4 on the interfaces I'm using for iSCSI. Those interfaces on the PowerVault are also set to static IPs and IPv4 in MDCU. As I mentioned, it's odd that three of the four interfaces work on IPv4 and one only works on IPv6.
Is there any harm in just using it with the unconfigured link-local IPv6 addresses on both ends? So far I haven't experienced any disconnects on restart or otherwise.
I'm also wondering if there's simply a factory reset that can be performed via console or MDSM. I haven't done much configuration on this, so it's easy to recreate the disk groups and set management IPs again. Maybe that would clear up the issue.
I attached a few screenshots to show what's going on. For testing purposes, this was done with a single cable from a NIC on the host to 0IN0 on the PowerVault.
IPV6 connection is reachable:
'IPV4 is not:
Showing the configuration on the PowerVault:
Showing the configuration on the interface on the Host:
DellEMCSupport
Moderator
Moderator
•
631 Posts
0
June 12th, 2020 13:00
Hello js312,
You need to uninstall MDCU and install MDSM. You use MDCU to Deploy a& install your MD3820i. You use MDSM to manage your MD3820i. MDSM is found on the resource dvd. Here is the link to the resource dvd. https://dell.to/2AmQZ0p
Please let us know if you have any other questions.
js312
4 Posts
0
June 12th, 2020 14:00
I already have MDSM installed. I uninstalled MDCU and tried to simply ping that interface, but it still cannot communicate via IPv4 on that interface, only IPv6. If I connect to 0IN1 or any other interface and set the IP on the host to match the subnet, it can ping via IPv4 just fine.
js312
4 Posts
0
June 12th, 2020 14:00
DellEMCSupport
Moderator
Moderator
•
631 Posts
0
June 12th, 2020 16:00
Hello js312,
If you disable IPv6 can you ping your IPv4 address?
Please let us know if you have any other questions.