Unsolved
This post is more than 5 years old
79 Posts
0
1749
March 25th, 2011 00:00
Is this a problem? ERROR: ID00005282: IP bind failed with error 10049
There is one warning messages within Event Viewer:
ERROR: ID00005282: IP bind failed with error 10049
This problem is raised for dual server during assigning virtual IP.
Environment: Windows Server 2003/2008 + AutoStart 5.4 build 195
Can anyone explain this message?
Thanks in advance
No Events found!
yito1
262 Posts
0
March 25th, 2011 00:00
Hi,
I searched this information with the knowledgebase of PowerLink.
However, there is no information.
In what situation was this message displayed?
yito1
262 Posts
0
March 25th, 2011 01:00
Hi,
Please display the console of the Settings tab of the Virtual IP.
EnvisionPlus
79 Posts
0
March 25th, 2011 01:00
Create new IP --> Asign IP. This message will be reported.
Thanks
EnvisionPlus
79 Posts
0
March 25th, 2011 01:00
yito1
262 Posts
0
March 25th, 2011 03:00
Hi,
This is a result of the execution of FT_ASSIGN_IP_PING_TIMEOUT.
To examine the duplication IP address before assign is done, this executes Ping for virtual IP.
At this time, the following event is generated.
ERROR: IP:xxx.xxx.xxx.xxx: Ping return socket Timeout error:0 :No error
ERROR: IP :xxx.xxx.xxx.xxx: Ping returns GetEchoReplies Failure: Did not get reply or timeout
Ping doesn't respond because it doesn't exist.
Therefore, the error is correct.
At this time, virtual IP is input as a variable.
However, the event of WinSock error 10049 is generated because it doesn't exist.
The event is generated four times moreover because ping is executed four times.
The event is generated three times moreover because ping is executed three times.
Please ignore this event.
P.S.
These are all guesses.
If you want correct information, please contact EMC Support.
yito1
262 Posts
0
March 28th, 2011 00:00
I'm sorry.
My guess was wrong.
I investigated it more.
And, the following result was obtained.
This has been generated at the ARP.
Please look at the packet capture and Windows Event Log.
It is generated at the same time.
This packet seems to be sent by the specification of OS.
http://support.microsoft.com/kb/980424/
This warning is a peculiar phenomenon of Windows2008.
Therefore, this warning is not generated in Windows2003.
Please ignore it.
jschrade1
106 Posts
0
March 28th, 2011 05:00
Based on your latest update I suspect this is a problem with the GARP changes that were made by MS Windows 2008. AutoStart provides a process which is considered a workaround for this Gratuitous ARP broadcast issue. However, if you upgrade from n existing 5.3.5 version of AutoStart to version 5.4, there is a known issue with this process no longer working. If you install 5.4 without upgrading from 5.3.5 then it works fine. There is an engineering request for this know issue to be fixed and there should be a hot fix for it available in approximately one month.
If this does not sound like your issue please update the blog accordingly.
1 Attachment
image001.jpg