Managing Console Manager › Managing Console Manager from the C3 Interface › Starting the Console Manager Software

Starting the Console Manager Software

To start Console Manager on your host system from the C3 interface:

1. Make sure that your DECwindows Motif transport is set up (see Appendix B, “Setting Up the DECwindows Motif Transport for the DECwindows Motif Interface.”).
2. Ensure that the session manager security for the system you are setting the display from is enabled on your local workstation.
3. Pull down the Commands menu and choose the Startup item from the Console Manager submenu.

Note: When you start the Console Manager software, the startup procedure verifies the configuration database. If any verification errors are found, the Console Manager software will not start. You must fix these errors using the configuration editor.

If the Startup option is grayed out, then you can restart the Console Manager software as described in Restarting Console Manager at the C3 interface, later in this chapter.

The startup procedure also invokes one or more child console controllers (see Chapter 1, “Introduction”), depending on the number of serviced systems you have. A child console controller can handle up to 16 serviced systems. If you have more than 16 serviced systems, then multiple child console controllers are started. For example, if you have 20 serviced systems, the first child console controller started handles the first 16 systems you have defined in the configuration database; the second handles the remaining four systems.

Each child console controller writes to its own log file. The primary child console controller writes to:

CONSOLE$TMP:CONTROLLER_nn.LOG

where nn is a number that identifies the child console controller.

The failover child console controller writes to:

CONSOLE$TMP:FAIL_CONTROLLER_primary-host-name_nn.LOG

where primary-host-name is the name of the primary host for serviced systems.