Several sm_server options are common to all Managers that are installed as services (the IP Availability Manager, for example, and the Service Assurance Manager). Common sm_server options lists these sm_server options.

Exceptions to these parameters are noted and described with the default parameters for the individual SDK products.

Table 1. Common sm_server options




Specifies the name of the Manager (Manager or Global Manager).


Specifies the sm_server configuration file to use. Configuration files are loaded from the directories BASEDIR/smarts/local/conf/<cfg> and BASEDIR/smarts/conf/<cfg>.


Specifies the alternate Manager port.


Specifies the alternate bootstrap configuration file. The file name is relative to the configuration directory (as set by the --configoption). The default is bootstrap.conf.


Indicates ignore errors encountered while restoring the saved topology.


Indicates do not attempt to restore any saved objects.


Start a subscription adapter that automatically subscribes to the specified notifications.


Specifies the alternate Broker location as host:port. Also -b <location>.


Redirects the output (stdout and stderr). The file name is <file>, or the --logname value if <file> is omitted. Log files are always placed in BASEDIR/smarts/local/logs.


Run the SDK program as a daemon (UNIX only). Messages generated from internal logging calls are directed to the log file. Log files are written to the BASEDIR/smarts/logs directory.


Instructs the VMware program to log any syslog messages with the specified syslog facility (UNIX/Linux only). The default is Daemon.

The <facility> setting can be one of the following:

  • Kern

  • User

  • Mail

  • Daemon

  • Auth

  • Lpr

  • News

  • Uucp

  • Cron

  • Local0

  • Local1

  • Local2

  • Local3

  • Local4

  • Local5

  • Local6

  • Local7

To display a complete list of the sm_server options on your system, type the following command with administrative privileges:

         /bin/sm_server --help