Chapter 11, SCO Doctor for Networks
Central Management Station Topologies
The CMS can be configured in one of three topologies.
One CMS/One Management System
See the
SCO Doctor Release and Installation Notes
for details on installing SCO Doctor.
To configure SCO Doctor for Networks using a single CMS:
- Install SCO Doctor for Networks on the management system.
- Install SCO Doctor for Networks or SCO Agent on each remote system which is to be managed by the CMS.
One CMS/Multiple Management Systems
To support a single CMS with multiple systems on a LAN, SCO Doctor for Networks requires NFS to provide a single integrated CMS service for the remote systems. NFS is used to advertise the Historical Database and to share the incoming alert notice queue with each management system in the CMS. One system should be designated as the CMS server.
A reliable CMS server with adequate resources is required to store the Historical Database. Each remote system will require up to 5 MB to store 12 months of data including approximately 100K of management data per day. Each month, the previous month's data for each system is summarized into a single database of approximately 200K.
To configure SCO Doctor for Networks using one CMS and multiple systems:
- Install SCO Doctor for Networks on the CMS server.
- Advertise via NFS the /usr/spool/doctor and /usr/lib/doctor directories on the CMS server.
- On each additional management system to be used as part of the CMS:
- Install SCO Doctor for Networks or SCO Agent on each remote system.
Multiple CMS/One Management System
Dividing the set of remote systems into separate domains, each with a dedicated CMS, has several advantages. Each domain can more easily adopt and enforce different management policies. Furthermore, reliability is enhanced when the failure of one CMS does not impair the operation of the others.
To configure SCO Doctor for Networks using a multiple CMS:
- Determine which remote systems will be managed by each CMS.
- Install SCO Doctor on each CMS.
- Install SCO Doctor for Networks or SCO Agent on each remote system specifying the name of the CMS which will be its manager.
To create multiple CMSs with multiple management systems follow the procedure described in the section One CMS/Multiple Management Systems, for each CMS you wish to create.
Configuring the CMS and Agent Systems
-
How to select systems to be managed:
-
From the main menu, select Config, Systems. This displays a list of known systems.
-
To select a system to be managed, highlight the system by using the cursor.
-
Either press ENTER, or select the Edit, Modify menu option.
-
In the displayed dialog box, set the Under management to Yes and the system will become a managed system.
How to change the security password:
To access a remotely running SCO Agent system, you must specify the security password that is being used by that particular remote system. You enter this password in the Password field of the dialog box, accessed from the system list, as described in the above example.
How to enable the CMS to initiate management:
The CMS system will initiate daily management to a remote system if the system is a managed system and Central dial has been specified. Ensure that both these options are set.
How to enable an Agent system to initiate management:
Consider a CMS system called ``mercury''
(which has a security password of ``secret'')
and a remote SCO Agent system called ``earth''.
If the remote Agent system is to initiate management:
-
Ensure that Central dial has been set to Disable on system ``mercury''. This is so both the remote and local system will not initiate the management process.
-
Connect to the remote Agent system, ``earth'', using the File, Open menu option.
-
Select the Config, Agent Configuration, Management option. In the dialog box, enter the name of the CMS (``mercury'') and the CMS password (``secret''). This will change the configuration on the system ``earth''. This system will now, on a daily basis, connect to the CMS and download its alerts and databases.
How to enable alerts on demand:
When an alert has triggered on a remote system, an alert notice will be generated and placed in a queue. At management time the alerts will be sent to the CMS. It is possible, however, to have alert notices sent immediately, known as alerts on demand. Select the Config, Agent Configuration, Alerts option. In the dialog box, set Send immediately to Yes. Alert notices will be sent to the CMS as they happen.
How to daisy chain CMS systems:
Just as a remote SCO Agent system can be managed by a CMS, a CMS can be managed by another CMS, forming a chain of management. This chain can be arbitrarily long. All alerts and databases from managed systems will be propagated along the chain to the managing systems.
To configure a CMS to be managed by another system:
-
Connect to the local agent system using the File, Open menu option.
-
Select the Config, Agent Configuration, Management option. In the dialog box, enter the name of the CMS and the CMS password. This system can now be managed by another CMS system.