HP UX DCE Software manual 89

		Configuring HP DCE Cells
		Configuring Cells with DCM
	By using the List menu, you can switch to a template mode that allows
	you to create prototype DCE cell configurations that can (and must) be
	tested for validity before actually being created.
	Important Security Warning
	DCM uses standard UNIX remote login utilities to perform remote
CAUTION
	administration. This causes the cell administrator’s password to be sent
	over the network whenever you perform a task on a remote system. If
	someone is very closely monitoring the network traffic, they could obtain
	the password and the security of the cell’s DCE services will be
	compromised. Note, however, that using DCM is no more or less secure
	than using standard UNIX remote login utilities directly. (Secure
	Internet Services (SIS) do not provide better security for the purpose of
	remote DCE cell administration.)
	Requirements for Running DCM
	If you choose to configure your cell with DCM, you should verify that the
	systems in your cell meet the following requirements:
	•	All systems from which you want to perform cell configuration tasks
		must have SAM installed.
	•	All systems must have the host name of each node (the
		administrative node and cell members) in their .rhosts and
		/etc/hosts.equiv files. The .rhosts file must be located in the root
		user’s home directory, usually the / directory. For more information
		about .rhosts files, see Using ARPA Services (B1014-90006), and the
		remsh (1) and hosts.equiv (4) man pages.
	•	All systems that you want to administer via DCM must be running
		HP DCE/9000 Version 1.2 , 1.2.1, 1.3.1, 1.4, 1.4.1, 1.4.2, 1.5, 1.6, or
		1.7. DCM does not configure and may not “discover” all aspects of
		other vendors’ system configuration.
	Running DCM
	To run DCM:
	1.	Log in as root.
	2.	Execute sam from a shell prompt.

Planning and Configuring HP DCE 1.7 5-5