Make NPM with APE a Global Solution for a Centralised Topology

As it stands right now NPM/NAM & SAM/ACM with Additional Polling Engines (or Remote Office Pollers) have a 200ms limit between the APE and the DB. This means that global latency will rule out at least one region from having a local APE.

EMEA -> ASIA - approx 200ms

EMEA -> AUSTRALIA - approx 300ms+

EMEA -> US - approx 140ms

We would really love to have a centralised deployment with APEs in each site within each region, but currently it seems this is not supported. Yes I know EOC can sit across distributed installations, but the benefits of a central topology are lost (alerting, consistency, custom properties etc)

Please can the architecture be enhanced to find a way to support APE's more than 350ms from the DB - even if there are restrictions placed on polling limits.

Find more posts tagged with

global topology

rop

latency

npm

ape

nam

Status: None

Comments

Deltona

Hi there,

You can tweak SQL timeout settings on both application servers and SQL server.

You can also tweak TCP settings on both types of servers to improve TCP sessions.

APEs will then be able to keep connections open longer and close them again as soon as possible.

Ask support for guidelines on how to achieve this.

PeterLyttle

That's really helpful information thanks, though I've been through this with pre-sales and it'll be classed as an 'unsupported' configuration - hence the request here.

planglois

MSMQ used to be the solution for this but it was really buggy.