Network Security Manager On-Prem Getting Started Guide
Table of Contents
Deployment Modes
Standalone deployment: Controller can be configured to perform firewall management, processing and storing reporting and analytics data. NSM provide flexibility to extend standalone deployment to multi-node deployment.
Multi-node deployment: NSM On-Premises provide flexibility to deploy it in multi-node setup. In this deployment, controller node is associated with one or more reporting agents.
Controller and Reporting Agents can be added as deployment nodes.
- Controller can be used as an independent or distributed setup. In single setup, the controller will be used for management, processing firewall log data for reporting and analytics and storing reporting and analytics data. In distributed setup, controller can be associated with multiple reporting agent and controller can be configured to perform firewall management only or management, reporting and analytics. NSM controller user interface is the primary user interface for accessing all NSM functionality.
- Reporting Agent is used for processing and storing reporting data, the reporting agent must be associated with the controller. Reporting agent user interface provides functions like setting up reporting agent, resource monitoring and troubleshooting.
The distributed setup is needed when you have multiple firewalls. In this case, Controller is used to manage all the firewalls but the reporting agent will be assigned to each firewall to store the reporting data.
- If you wish to configure NSM in (Undefined variable: Book_Variables.HA) (HA) mode, the reporting and analytics cannot be enabled on controller and you will need reporting agents.
- If you want to move from standalone deployment with reporting and analytics to NSM HA, reporting data stored in controller needs to be deleted.