| Connection | Description |
|---|---|
| Cache tier to data tier | The cache tier (NXT Engine) odes connect to the data tier (Cassandra) nodes through a proprietary Cassandra database connector/driver. Each cache tier node is required to have direct connectivity to every data tier node. Connectivity is round-robin and is controlled by the driver in use by the cache tier nodes. |
| Cache tier to search tier | The cache tier nodes connect to the search tier nodes through proprietary request handlers. The search request is generated by any of the cache tier nodes and directed to a server running HAProxy or, it can be directed to a configured hardware load balancer. This server then forwards the request to the search tier nodes, using a round-robin load balanced algorithm. NOTE: Connectivity
can occur through the HAProxy Server or through a suitable
hardware load balancer: When using a hardware load balancer for
your search tier nodes, this connection does NOT require session
persistence. |
| Cache tier to customer notification server | The cache tier nodes connect to and post data with an on-premises customer notification system whenever an alarm is raised within the ServAssure NXT system. |
| Cache tier to message bus | The cache tier nodes connect to and exchange messaging with the ServAssure NXT Message Bus services when integrated with the ServAssure Collection Platform. |
| Trap Receiver to cache tier | The ServAssure NXT Trap Receiver
node sends filtered trap messages received from remote devices to
the cache tier nodes through the server running HAProxy or a
configured hardware load balancer. The load balancer then forwards
the request to the cache tier nodes, using a round-robin,
load-balanced algorithm. NOTE: If you plan to
use HAProxy with the Trap Receiver, then you must open the
optional port 8183. Refer to Trap Receiver-specific variables. NOTE: When using a hardware load balancer for cache tier nodes, this
connection does NOT require session persistence. |
| Application/UI to cache tier | The Application/UI nodes connect to the cache tier nodes through
the server running HAProxy or a configured hardware load balancer.
The HAProxy server then forwards the request to the cache tier
nodes, using a round-robin load balanced algorithm. NOTE: This connection
DOES REQUIRE session persistence. Session persistence is also
referred to as Session Based, Session Affinity, or Sticky
Sessions, depending on the load balancing/proxy server in
use. |
| Application/UI to Insight Reporting | The Application/UI nodes connect to Insight Reporting (Tableau)
nodes through a configured hardware load balancer. The source IP
addresses of all of the Application/UI nodes must be added to the
“Trusted hosts”. NOTE: If the
Application/UI nodes have more than one interface, add the
interfaces that are used for external access. Refer to Integration with Insight Reporting for details on configuring trusted hosts, and configuring the mapping from ServAssure NXT users to Tableau users. The Insight Reporting nodes must be using a CA-signed SSL certificate, not a self-signed SSL certificate, to avoid integration issues when displaying Insight Reporting in the ServAssure NXT UI. |
| CMTS to Trap Receiver node | The CMTS (trap sender) must be able to send traps to the Trap Receiver node at the configured port to which the application is bound. |
| Trap Receiver to Metrics relay node | All ServAssure NXT nodes will send
metrics data directly to the ServAssure NXT ServAssure Metrics
Platform server node.
NOTE: In the
event that a metrics relay is being used as a proxy to relay
metrics data from an on-premises Trap Receiver server to a
cloud-based Metrics server, port 8090 must also be opened for
TCP traffic from Graphite Metrics to the local metrics relay. For additional details on metrics relay and how it can be used to proxy metrics data to a cloud-based ServAssure NXT Metrics system, refer to CommScope ServAssure® NXT Metrics Platform Installation Guide. |
| All nodes to metrics server node | All ServAssure NXT nodes send system and other application-based metrics and data to the Metrics server for monitoring and overall health statistics. |
| Desktop browsers to Application/UI nodes | All desktop/user web browser connections to the Application/UI Servers connect over standard HTTPS protocols. If more than one Application/UI Server is configured (this is the recommended configuration), then CommScope suggests the use of a load balancer that supports session persistence. Notes:
|
| Desktop browsers to cache tier | Administrator users require desktop web browser access to the cache tier nodes for user administration of ServAssure NXT. NXT Engine Administration UI can be optionally secured through HTTPS (SSL). |
| Desktop browsers to metrics server | Administrator users require desktop web browser access to the Metrics server for viewing system administration and application monitoring. |
