IP Conflict issue in two node cluster Windows 2008 failover cluster.

Cluster server is getting Ip conflict often with the primary cluster ip .

Solution : -

Solution: - change the binding order so that the first adapter will be listed as production LAN hence when it tries to do failover it will do it on Production Lan rather doing it on Local Area Connection 9 (Virtual Cluster Adapter). Tools to change the bind order are nvspbind.exe link to download is mentioned below.  

http://archive.msdn.microsoft.com/nvspbind/Release/ProjectReleases.aspx?ReleaseId=3837

BugCheck 7F:The bug check is : 0x0000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000) Windows 2003 Server

Nature of the problem , Server will reboot frequently with the BugCheck 7F:The bug check is : 0x0000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000)

While analyzing the issue , we found that it has cause due to symentec Antivirus, Recomended to analyze dump for correctly identifing the problem.

In my environment i found that the issue cause due to symentec antivirus since i have the dump trace which indicates , that the issue is related to savart.sys  This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault), Dont disable since if you disable also symentec will interact with kernel Instead uninstall symentec  and found server is stable then applied below fix to resolve the issue.

Event log

1005  auto protect couldnot scan the file <location>  for virus due to low kernal stack.

Solution : -

Upgrade the symentec antivirus to latest version which will correct the  issue.