Using the HP DTC Manager/UX

DTC Manager/UX overview

Required daemons

The following daemons must be running on the HP 9000 host computer for the

conﬁguration information to be downloaded to the DTC.

Note These daemons must be run with superuser privileges.

• rbootd—remote boot server daemon

• dtcnmd—DTC network management daemon

• dtcnmp—DTC state machine daemon

The rbootd daemon waits for a boot request packet from the DTC. When it

receives the packet, it downloads the code and the conﬁguration information that

was generated using the dtcconﬁg command.

The dtcnmd daemon handles the transmission of network management data

between the DTC management platform and the DTC.

The dtcnmp daemon executes the network management protocol enabling DTC

requests to be sent and received between the DTC Manager/UX user interfaces

(dtcconﬁg, dtcdiag and dtcmodifyconfs) and the DTC. The dtcnmp daemon is

always started by dtcnmd.

If you need information on the dtcnmd, dtcnmp and rbootd daemons, refer to

your man pages.

DTCs that can be managed by DTC Manager/UX

Five types of DTCs can be managed by the DTC Manager/UX:

DTC 16TN and DTC 16MX

The DTC 16TN has 16 asynchronous ports (separated in two eight-port groups) and

does not support add-on boards. Each port group can be conﬁgured to be modem or

direct-connect.

Note The full functionality of the DTC 16MX is only available using HP OpenView DTC

Manager. When managed by the DTC Manager/UX, the DTC 16MX is configured

and functions exactly like a DTC 16TN. Therefore, only the DTC 16TN product is

referred to in this manual.