Network Security Management On-Premises Administration Guide
- Network Security Manager (On-Premises) 2.5.0
- Network Security Manager Overview
- Home Dashboard
- Tenants
- Firewalls
- Templates
- Global Objects
- VPN Topology
- SD-WAN Topology
- Configuration Management
- User Management
- Reports
- Logs and Alerts
- System Dashboard
- Settings
- Licenses
- Administration
- Time
- Certificates
- Common Access Card (CAC) Authentication
- Diagnostics
- Firmware and Settings
- Backups/Restore Feature
- Configure Backup Settings
- Configure a Scheduled NSM File System Backup
- Configure a Scheduled NSM File System Backup via SCP
- View NSM File System Backups
- Create a NSM File System Backup
- Create SCP of a NSM File System Backup
- Import a NSM File System Backup
- Export a NSM File System Backup
- Delete a NSM File System Backup
- Restore NSM to a File System Backup
- Backup/Restore NSM using Safemode
- Shutdown/Reboot
- Closed Network
- Analytics Agent
- Network
- System Monitor
- High Availability
- NSM Management Console
- SonicWall Support
HA Modes and Terminologies
| Modes | Definitions |
| None | Selecting None activates a standard high availability configuration and NSM failover functionality, with the option of enabling stateful High Availability. |
| Active/Standby |
Active/Standby mode provides basic high availability with the configuration of two identical NSMs as a High Availability pair. The Active NSM handles all traffic, while the Standby NSM shares its configuration settings and can take over at any time to provide continuous network connectivity if the Active NSM stops working. By default, Active/Standby mode is stateless, meaning that network connections must be re-established after a failover. To avoid this, stateful synchronization can be licensed and enabled with Active/Standby mode. In this stateful High Availability mode, the dynamic state is continuously synchronized between the Active and Standby NSMs. When the Active NSM encounters a fault condition, stateful failover occurs as the Standby NSM takes over the Active role with no interruptions to the existing network connections. |
| Terms | Definitions |
| Active | The operative condition of an NSM. The Active identifier is a logical role that can be assumed by either a primary or secondary NSM. |
| Primary | The principal NSM. The primary identifier is a manual designation and is not subject to conditional changes. Under normal operating conditions, the primary NSM operates in an Active role. |
| Secondary | The subordinate NSM. The secondary identifier is a relational designation and is assumed by an NSM when paired with a primary NSM. Under normal operating conditions, the secondary NSM operates in a standby mode. Upon failure of the primary NSM, the secondary NSMassumes the Active role. |
| HA | High Availability: non-state, NSM failover capability. |
| Failover | The actual process in which the Standby NSM assumes the Active role following a qualified failure of the Active NSM. Qualification of failure is achieved by various configurable physical and logical monitoring facilities. |
| Preempt | Applies to a post-failover condition in which the primary NSM has failed, and the secondary NSM has assumed the Active role. Enabling Preempt causes the primary NSM to seize the Active role from the secondary after the primary NSM has been restored to a verified operational state. |
| Standby (Idle) | The passive condition of an NSM. The standby identifier is a logical role that can be assumed by either a primary or secondary NSM. The Standby NSM assumes the Active role upon a determinable failure of the Active NSM. |
Was This Article Helpful?
Help us to improve our support portal