• SonicOSX 7
• Product Overview
  • Enterprise Class High-performance Firewall
  • Feature Summary
    • Simplified Management and Reporting
    • Advanced Threat Protection
    • Capture Cloud Platform
    • Deep Packet Inspection of SSL/TLS (DPI-SSL)
    • Content Filtering Service
    • Intrusion Prevention Service
    • Application Control
    • Unified Policy Configuration and Management
    • Multiple Instances / High Availability
  • System Architecture
  • Hardware Overview
    • Front Panel
    • Rear Panel
    • LEDs
    • Specifications
• System Setup
  • Default Settings
  • System Startup
    • HTTPS Management via X0
    • HTTPS Management via MGMT Port
      • Using SafeMode
      • Using CLI
  • SonicOSXBasic Configuration
  • Connecting LAN and WAN Interfaces
  • Network Configuration
  • Registration and Licensing
• Configuring Multiple Instances
  • Enabling Multi-Instances
  • Configuring Multi-Instances
• Licenses for Multiple Instances
  • Surveying Multiple Instances
  • Instance Registration
  • Instance License Update
  • Deactivating an Instance
  • Instance HA Pair on a Standalone NSsp Node
• Configuring High Availability
  • High Availability Overview
  • Setting Up Unit-to-Unit HA
  • Configuring Advanced Settings
  • Checking High Availability Status
  • Monitoring High Availability
  • Configuring Multi-Appliance Instance-Level HA
• CLI Bring-up
  • Access the Console Port
  • At the ChassisOS Prompt
  • To Change to the Console Port of Another Physical Blade
  • Check Network Address Settings
  • Commands at ChassisOS Prompt
  • Show Commands at ChassisOS Prompt
  • Configure IP Addresses from the CLI
  • Restart SonicOSX from the CLI
  • To Access SonicOSX Console
• Using the SafeMode GUI
  • Accessing SafeMode
  • Rebooting the System
  • Upgrading Firmware
  • Diagnostics
• SonicWall Support
  • About This Document

Surveying Multiple Instances

Instance licenses are required for spawning instances. The Multi-Instance licenses are fetched onto the system after the device is registered with the license manager. The licenses are then managed by the Root Instance for spawning instances. The root instance takes care of assigning an available instance license to an instance after it has started.

The licenses are assigned to an instance and marked as in use only when the instance is started. The license assigned to an instance remains in use until an instance is deleted. Stopping an instance does not release its license.

After all instances are consumed, a request to start a new instance would fail owing to insufficient licenses.

The Instances page displays the list of instance licenses and their status (used/available) and also the name of the instance (for licenses in use).

Instance Listing