VSAN 8.0 and not showing all interface IPs on Networking

ekhouser · Thu Jul 10, 2014 8:29 pm

So after installing VSAN version 8 on two boxes with multiple NICs and following the instructions, I noticed while creating a "replication partner" and selecting sync and heartbeat IPs, not all of them are showing. So, on one node, I look at the configuration>Networking portion and the only IP showing up is 127.0.0.1?? I turned on the debug log, look at at it it states the following

7/10 16:15:46.287 dd0 Srv: bind() to 10.10.20.3:3260 failed: Only one usage of each socket address (protocol/network address/port) is normally permitted. (code: 10048)

What is this error?? Also, while creating the replica and selecting network settings, what should be shown are the IPs for each box, but it only shows IPs for the other box, not the local and they are all greyed out?

Thu Jul 10, 2014 8:54 pm

StarWind logs are for StarWind support staff. Don't try to analyze and troubleshoot using them as a source.

Q: Do you have missing interfaces accessible from both hosts?

ekhouser · Thu Jul 10, 2014 11:47 pm

I have tried three different boxes and only one will show the IPs, the other two do not show anything. I was able to get one box to show an IP other than 127.0.0.1 but for testing, I attached a Hyper-V virtual switch and used that port, the IP in VSAN went away. BUT, the server that has no problems showing ALL interface IPs uses numerous virtual switches and even though none are connected to the interface being used for sync, the other ones which are a part of Vswitches DO show on this server.

As far as the logs go, I was not trying to "analyze" the log--only attaching it for reference purposes.

Fri Jul 11, 2014 12:01 am

Please either attach full log or send it zipped to support@starwindsoftware.com with a reference (link) to this thread. Thanks!

ekhouser wrote:I have tried three different boxes and only one will show the IPs, the other two do not show anything. I was able to get one box to show an IP other than 127.0.0.1 but for testing, I attached a Hyper-V virtual switch and used that port, the IP in VSAN went away. BUT, the server that has no problems showing ALL interface IPs uses numerous virtual switches and even though none are connected to the interface being used for sync, the other ones which are a part of Vswitches DO show on this server.

As far as the logs go, I was not trying to "analyze" the log--only attaching it for reference purposes.

ekhouser · Fri Jul 11, 2014 12:11 am

Log attached...thank you! It would not allow attaching .txt or .log files

[ ... ]

Fri Jul 11, 2014 12:20 am

It's not attached it's "copy pasta" into message and is truncated by phpBB. Please either attach zip or send to e-mail I gave above.

ekhouser · Fri Jul 11, 2014 12:53 am

Sent the zip file, funny because the copy paste looked fine when I pasted it? I attached it as well. Thank you!

Fri Jul 11, 2014 12:25 pm

Just want to let you know that we received the logs. Once we will have any investigation results we `ll get back to you.

Fri Jul 11, 2014 2:59 pm

It looks like the issue is caused by the fact that some application uses and reserved the port 3260 that is required for StarWind functioning. On my experience that is MS target. Can I ask you to doublecheck if that is so?
You can check what app is using the port using

Code: Select all

netstat –abn

ekhouser · Fri Jul 11, 2014 3:23 pm

AHHH!!! THANK YOU!! That was it. Odd thing though is, that must be a default service maybe? I do not remember ever starting or configuring that service and this is a fresh install of 2012 R2. Nonetheless, they all show now! Thank you again!

Fri Jul 11, 2014 11:55 pm

You enable (or disable?) iSCSI target role on your Windows host and that's it. It's possible to change default ports for both StarWind and MSFT iSCSI engines.

ekhouser wrote:AHHH!!! THANK YOU!! That was it. Odd thing though is, that must be a default service maybe? I do not remember ever starting or configuring that service and this is a fresh install of 2012 R2. Nonetheless, they all show now! Thank you again!