High Latency on Domain Controllers

Are your domain controllers busy?  High cpu? 

What sort of info are you getting on the interfaces...overall volume, dropped packets, crc errors, etc?

The questions from Jfrazier are the best place to start. It's hard to think of any way that an Orion upgrade could have any impact on domain controller performance. How far back does the latency show in your history for those nodes?

You could also try installing the agent on those DCs and see if the reported information stays the same or changes. I have found that some servers in general have a harder time responding to remote polling when their own CPU is pegged, but a local agent can take that one factor out of the equation.

Hi Jfrazier,

Please check screenshot.

hi,

The DCs are polled by 2.4.1 agent version. This bulk alerts issue is surfaced just few days ago so it was just an assumption that it is related to upgrade.

Start with health of AD server and then verify interface configurations (speed, half-duplex vs. full duplex, and such). Work your way down the chain once you validate AD server health.  Is there a load balancer in the mix?

I would only pursue that assumption if the latency started immediately after the upgrade, although again--it's hard to conceive of how an Orion upgrade would cause latency on your domain controllers. 

What does your historical CPU, memory, and network interface utilization look like on your DCs? What else has changed in your environment over that time period? What are the hardware specs on your DCs compared to the size of your AD environment? How many DCs do you have?