To display a list of all active Deep Security Manager nodes, go to Administration > Manager Nodes . See also Run Deep Security Manager as multiple nodes.
To display details about one of the manager nodes, double-click its row in the list. The Properties window displays the following:
  • Hostname: The hostname of the computer on which Deep Security Manager is installed.
  • Description: A description of the manager node.
  • Performance Profile: Deep Security Manager's performance can be affected by several factors including number of CPUs, available bandwidth, and database responsiveness. The manager's default performance settings are designed to be suited for most installation environments. However, if you experience performance issues, your support provider may suggest that you change the performance profile assigned to one or more of your Deep Security Manager nodes; you should not change these settings without first consulting your support provider.
    Note
    Note
    The Simultaneous Endpoint Disk and Network Jobs operation listed in the following tables includes anti-malware scans, integrity monitoring scans, reconnaissance scans, sending policy updates to computers, and distributing security updates.
    • Aggressive: This performance profile is optimized for installations where Deep Security Manager is on a dedicated server. For example, this is how some common concurrent operations could be distributed per manager node using the Aggressive performance profile:
      Operation
      2-core system
      8-core system
      Activations
      10
      20
      Updates
      25
      50
      Recommendation Scans
      10
      20
      Check Status
      100
      Same (100)
      Agent- or Appliance-Initiated Heartbeats
      20 Active 40 Queued
      50 Active 40 Queued
      Simultaneous Endpoint Disk and Network Jobs
      50
      50
      Simultaneous Endpoint Disk and Network Jobs per ESXi
      3
      3
    • Standard: This Performance Profile is optimized for installations where Deep Security Manager and the database are on the same computer. For example, this is how some common concurrent operations could be distributed per manager node using the Standard performance profile:
      Operation
      2-core system
      8-core system
      Activations
      5
      10
      Updates
      16
      46
      Recommendation Scans
      3
      9
      Check Status
      65
      100
      Agent- or Appliance-Initiated Heartbeats
      20 Active 40 Queued
      50 Active 40 Queued
      Simultaneous Endpoint Disk and Network Jobs
      50
      50
      Simultaneous Endpoint Disk and Network Jobs per ESXi
      3
      3
    • Unlimited Agent Disk and Network Usage: This setting is identical to Aggressive, but has no limit on computer disk and network usage operations.
      Operation
      2-core system
      8-core system
      Activations
      10
      20
      Updates
      25
      50
      Recommendation Scans
      10
      20
      Check Status
      100
      Same (100)
      Agent- or Appliance-Initiated Heartbeats
      20 Active 40 Queued
      50 Active 40 Queued
      Simultaneous Endpoint Disk and Network Jobs
      Unlimited
      Unlimited
      Simultaneous Endpoint Disk and Network Jobs per ESXi
      Unlimited
      Unlimited
    • Higher Capacity: This setting has higher capacity than Aggressive or Unlimited Agent Disk and Network Usage, as it can consume more jobs simultaneously. With this performance profile, larger memory usage is predictable. If necessary, you can increase memory or JVM size.
      Operation
      2-core system
      8-core system
      Activations
      15
      45
      Updates
      39
      114
      Recommendation Scans
      15
      45
      Check Status
      259
      Same (259)
      Agent- or Appliance-Initiated Heartbeats
      20 Active 40 Queued
      50 Active 40 Queued
      Simultaneous Endpoint Disk and Network Jobs
      100
      100
      Simultaneous Endpoint Disk and Network Jobs per ESXi
      3
      3
    All performance profiles limit the number of concurrent component updates to 100 per relay group.
  • Status: Indicates the node's online and active status from the perspective of the Deep Security Manager node in which you are currently logged in.
  • Options: You may decommission a manager node. The node must be offline (uninstalled or service halted) to be decommissioned.