Deep Security Manager 10 has reached end of support. Use the version selector (above) to see more recent versions of the Help Center.
View active Deep Security Manager nodes
The Manager Nodes page displays a list of all active Manager nodes. Double-click on a Manager node in the list to display its Properties window:
- Hostname: The hostname of the Deep Security Manager host computer.
- Description: A description of the Manager node.
- Performance Profile: A 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.)
The "Simultaneous Endpoint Disk and Network Jobs" referred to in the tables below include 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 the
Deep Security Manager is installed on a dedicated server. The following table gives an indication of how some common concurrent operations are distributed per Manager node using the Aggressive Performance Profile:
Operation 2-core system 8-core system Activations 10 20 Updates 25 50 Recommendation Scans 5 12 Check Status 100 Same (100) Agent- or Appliance-Initiated Heartbeats 20 Active
40 Queued50 Active
40 QueuedSimultaneous 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 the
Deep Security Manager and the database share the same host. The following table gives an indication of how some common concurrent operations are 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 Queued50 Active
40 QueuedSimultaneous 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 25 Recommendation Scans 5 12 Check Status 100 Same (100) Agent- or Appliance-Initiated Heartbeats 20 Active
40 Queued50 Active
40 QueuedSimultaneous Endpoint Disk and Network Jobs Unlimited Unlimited Simultaneous Endpoint Disk and Network Jobs per ESXi Unlimited Unlimited
All performance profiles limit the number of concurrent component updates to 100 per Relay Group. - Aggressive: This Performance Profile is optimized for installations where the
Deep Security Manager is installed on a dedicated server. The following table gives an indication of how some common concurrent operations are distributed per Manager node using the Aggressive Performance Profile:
- Status: Indicates whether the Deep Security Manager node whose properties you are viewing is online and active from the perspective of the Deep Security Manager node you are logged into.
- Options: You can choose to decommission the Manager node. The node has to be offline (uninstalled or service halted) to be decommissioned.
For more information on multi-node Deep Security Manager installations, see Run Deep Security Manager as multiple nodes.
