ldmd - Logical Domains Manager daemon
The ldmd daemon is referred to as the Logical Domains Manager. It is the daemon program for the ldm command, which is used to create and manage logical domains. The ldmd daemon runs on the control domain, which is the initial domain created by the service processor (SP). For those platforms that have physical domains, the Logical Domains Manager runs only in the control domain of each physical domain. The control domain is named primary.
A logical domain is a discrete logical grouping with its own operating system, resources, and identity within a single system. Each logical domain can be created, destroyed, reconfigured, and rebooted independently, without requiring a power cycle of the server. You can use logical domains to run a variety of applications in different domains and keep them independent for security purposes.
You can use the svccfg command to modify the following properties:
Specifies whether to generate Logical Domains Manager audit records. A value of true generates Logical Domains Manager audit records. By default, the value is false.
When inter-vnet-link=auto, this property is the maximum number of virtual networks that are permitted to enable inter-vnet links. When the number of virtual networks connected to the same virtual switch exceeds this limit, inter-vnet links are disabled automatically. The default value is 8.
Specifies the autorecovery policy. This property can have one of the following values:
autorecovery_policy=1 – Logs warning messages when an autosave configuration is newer than the corresponding running configuration. These messages are logged in the ldmd SMF log file. The user must manually perform any configuration recovery. This is the default policy.
autorecovery_policy=2 – Displays a notification message if an autosave configuration is newer than the corresponding running configuration. This notification message is printed in the output of any ldm command the first time an ldm command is issued after each restart of the Logical Domains Manager. The user must manually perform any configuration recovery.
autorecovery_policy=3 – Automatically updates the configuration if an autosave configuration is newer than the corresponding running configuration. This action overwrites the SP configuration that will be used during the next power cycle. This configuration is updated with the newer configuration that is saved on the control domain. This action does not impact the currently running configuration. It impacts only the configuration that will be used during the next power cycle. A message is also logged, which states that a newer configuration has been saved on the SP and that it will be booted the next time the system performs a power cycle. These messages are logged in the ldmd SMF log file.
Specifies the CPU autoreplacement policy for the Fujitsu M10 platform. This property can have one of the following values:
autoreplacement_policy_cpu=1 – Enables the CPU autoreplacement process, which attempts to automatically replace faulty CPU resources. This is the default policy.
autoreplacement_policy_cpu=0 – Disables CPU autoreplacement process.
Specifies the maximum number of retries for the CPU autoreplacement process on the Fujitsu M10 platform. A value of 0 specifies that the number of retries are unlimited. The default value is 5 retries.
Specifies the interval in seconds between retries for the CPU autoreplacement process on the Fujitsu M10 platform. The minimum interval is 1 second. The default value is 300 seconds.
Specifies which shutdown method to use. If default_quick_stop is set to true when the Logical Domains Manager is started, the next ldm stop-domain command uses the –q method unless overridden on the command line. If default_quick_stop is set to false, the ldm stop-domain command uses the shutdown command method, if available in the specified domain, or automatically falls back to the –q option. The default value is false.
Specifies the memory removal policy to use when the SP uses the deleteboard command to make a dynamic memory removal request. This property applies only to the Fujitsu M10 platform.
The following are valid policy values:
auto – Uses the most recently supported fj_ppar_dr_policy policy value, which is ratio. The default policy is auto.
ratio – Keeps the memory size for each domain in the same relative proportion until the specified amount of memory has been removed from the domains.
This policy requires that all the domains in the system are installed with at least the Oracle Solaris 11.3 OS. The targeted policy is used if any domain is installed with an older version of the Oracle Solaris OS.
targeted – Removes memory only from domains that are assigned memory on the board to be deleted.
Specifies the number of hops (or subnets) a MAC collision detection message is permitted to traverse before the message is dropped. Valid values are 0 (use default value), 1 (same subnet), 32 (same site), 64 (same region), 128 (same continent), and 255 (unrestricted). By default, hops is set to 1, which means that multicast messages are sent only to other managers on the same subnet. When hops is set to 0, ldmd uses the default value, which is 1.
Enables a guest domain migration from another system to this system if xmpp_enabled is also set to true. The default value is true.
Enforces the authentication of domain migrations to the system. The default behavior requires the user to be authenticated. This property does not affect migrations from the system. To permit a migration without specifying a password set migration_authn_required to false on the target machine.
This property is used only by the XML/XMPP interface and not by the ldm migrate-domain command, which always requires a password to be given for a migration.
Enables or disables the Power Management (PM) Observability Module at ldmd startup. When this module is enabled, you can run the ldmpower command to view power-consumption data. See the ldmpower(1M) man page. The default value is true.
Enables a guest domain migration from this system to another system if xmpp_enabled is also set to true. The default value is true.
Determines the action that is taken when recovery mode is requested by the SP. This property applies only to those systems that support recovery mode, such as SPARC T5, SPARC M5, SPARC M6, and Fujitsu M10 platform. The following are the valid values:
auto performs a recovery without intervention by the administrator. This is the default behavior.
never specifies that no recovery is to be performed and that the system remains in the factory-default configuration.
Specifies the root domain boot timeout during recovery in minutes. Valid values start at 5 minutes. The default value is 30 minutes.
Enables the ldmd XMPP server to listen for configuration requests from third-party management applications. Also, permits the ldmd daemon to communicate with the ldmd daemon on another system to coordinate a migration between the two systems. The default value is true.
See the attributes(5) man page for a description of the following attributes.
The ldmd service is managed by the Service Management Facility (SMF) and uses the svc:/ldoms/ldmd:default service identifier. See the smf(5) man page.
To have the changes made to these SMF properties take effect, you must refresh and restart the service.
Use the svcadm command to perform administrative actions on this service, such as enabling, disabling, refreshing, or requesting a restart. Use the svcs command to query the service's status.
For more information about the ldmd SMF properties, see the Oracle VM Server for SPARC 3.4 Administration Guide.