Splitting off SAM to separate server

Question

We have a special need, majority of our servers are in the "cloud" while all our circuits are local, so we can either move the entire box to the "cloud" for better SAM efficiency, which will impact all our circuit latency readings, or move SAM to it's own server, which the latter is what we would like to do, but can we do it using the same DB as the NPN/NCM server?

The driving factor behind moving the SAM to where the servers are is that we encounter occasional instances when all cloud functions drop off when SAM cant reach it for some reason or the other, which then resets all the cloud servers, sends a ton of alerts, and then stabilizes.  This is an issue with the "cloud" and not the server, or the connectivity to the "cloud".

steffen.gutzeit · Answer

Hello.

SAM uses the same SQL database as NPM and NCM.

All 3 products/modules are installed on your 1 Orion Server.

What comes to mind is to contemplate deploying an additional polling engine to your cloud environment as David Smith suggested. The benefit is that this polling engine can buffer 1GB of data and it only needs a handful of ports to be open to your Orion Server.

Also you could try playing around with alerting thresholds, like setting the trigger condition to a few minutes to avoid short-term connectivity issues resulting in email alert flooding.

Best regards,

Steffen

dgsmith80 · Answer

No, if you spin a new instance of SAM it will be stand-alone so new Database and new IIS Site. The best you could do is add a Hyper link to the SAM system.

ACDII · Answer

Option B is most likely what we would go with.    If we do this, can SAM be accessed via the Orion Console with the rest of NPM/NCM like the DB monitoring is?