Windows .NET Server 2003 Clustering

[Paul_185]

Hello,

We are currently experiencing problems with our Windows .NET Server 2003 clustered servers.

Symptoms:
The servers slowing (over a few days) lose network connectivity... starts off by not being able to Terminal Service into the boxes, then shares become inaccessible, etc. When this happens, the cluster service does not fail-over resource groups to the other node automatically/successfully.

Hardware:
- Proliant ML370 Servers
- Emulex LightPulse (L8000) HBA cards
- HDS 9960 disk subsystem connected via an InRange FC/9000 fibre channel switch

We are using the full port (beta) drivers from Emulex (as the mini port drivers do not appear work).

Anyone seen/heard of similar issues with servers losing connectivity? All advice/feedback appreciated!

Regards,


Paul.

[Frank Blando]

Can you give us more information?
- What build of Windows?
- What are the clustered applications?
- How much memory does the system have
- How much memory is free after a reboot, and how much is free once the problem starts?
- How is the CPU utilization when you have a problem?
- Can you still ping when the problem occurs?
- Are there errors in the system event log?
- Are there arrors in the cluster log?

Frank

[Candido Caceres]

I suppose that the problem was with the network drivers (or teaming). I got the same problem and change the teaming to fault tolerant.