• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 670
  • Last Modified:

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
0
Anestis Psomas
Asked:
Anestis Psomas
  • 3
  • 3
1 Solution
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
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
0
 
Anestis PsomasSystem and Network AdministratorAuthor Commented:
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
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
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
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Anestis PsomasSystem and Network AdministratorAuthor Commented:
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 .
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
I dont think so it can be a reason and if this IP isnt anywhere you should have this issue as well ... when you have try to do a ping, nslookup and Tracert

- Rancy
0
 
Anestis PsomasSystem and Network AdministratorAuthor Commented:
I've requested that this question be deleted for the following reason:

Problem Solved
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now