Link to home
Start Free TrialLog in
Avatar of Anestis Psomas
Anestis Psomas

asked on

Exchange 2010 SP2 Cluster Errors

Hello ,


I have setup a multirole enviroment with Exchange 2010 SP2 with DAG and i have some strange problems with ipconflict errors that SCOM gives me . My enviroment works just fine. I have test that DAG working correctly and mailflow is working .

Every 2-3 days i take errors from SCOM which i have for monitoring my environment. The first errors is about the file share witness resource that is not accessible by the cluster. Then that i have an IP address conflict for my DAG Virtual Address and that cluster ip address resource cannot be brought online because of duplicate IP address.

After 1 minute the whole thing works again flawlessly .

The thing is that im sure i dont have an IP address conflict.

Any ideas what to look for ?

Thanks
Avatar of Manpreet SIngh Khatra
Manpreet SIngh Khatra
Flag of India image

Is the DAG in the same site or span between sites ?
If you try to ping the concerned IP what information do you get from DNS ?

I would suggest you to run EXBPA and ensure all is good

- Rancy
Avatar of Anestis Psomas
Anestis Psomas

ASKER

Hello ,


DAG is in the same site . If i am try to ping the DAG Virtual IP i get the response times only . Is there something else for this ?

Thanks
There isnt but i would run EXBPA and check all is good and ensure that this IP isnt in DHCP if there is any ?

- Rancy
I dont have DHCP and the IP im sure is only used by the DAG ,

I also RUN EXBPA and the only problem i have is that the mailbox servers with the DAG are running over Hyper-V cluster and this is unsupported. I knew this thing from start but i dont know if this is the reason for the errors i take .
ASKER CERTIFIED SOLUTION
Avatar of Manpreet SIngh Khatra
Manpreet SIngh Khatra
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I've requested that this question be deleted for the following reason:

Problem Solved