Cisco Systems OL-11390-01 manual 11-14, Name, Description, Dependency

Chapter 11 Administering DFM (Advanced)

System Administration

Table 11-3	DFM-Related CiscoWorks Processes (continued)
Name		Description	Dependency
DfmBroker		DFM Broker maintains a registry about DFM	None
		domain managers, which register the following
		information with the broker when its
		initialization is complete:
		• Application name of the domain manager
		• Hostname where the domain manager is
		running
		• TCP port at which the HTTP server is
		listening
		When a client needs to connect to the domain
		manager, it first connects to the broker to
		determine the hostname and TCP port where that
		server’s HTTP service is listening. It then
		disconnects from the broker and establishes a
		connection to the domain manager.
		The DfmBroker log file is located at
		NMSROOT/objects/smarts/local/logs/brstart.log
		.
DFMLogServer		Controls DFM logs.	None
DFMMultiProcLogger		Handles processes with multiple threads.	None
DFMOGSServer		DFM Object Grouping Service Server evaluates	CmfDbEngine, ESS
		group membership.
DfmServer		Infrastructure device domain manager, a	DfmBroker
		program that provides backend services for
		DFM. Services include SNMP data retrieval and
		event analysis. The DfmServer log is
		NMSROOT/objects/smarts/logs/DFM.log.
		Note If there are two instances of the
		DfmServer running, each will have a log
		file, DFM.log and DFM1.log.
DFMCTMStartup		Handles interprocess communication.	None
EPMDbEngine		Event Promulgation Module (EPM) database	None
		engine—Repository for the EPM module.
EPMDbMonitor		EPM database monitor.	EPMDbEngine
EPMServer		Sends events to notification services.	EPMDbEngine
FHDbEngine		Fault History database engine—Repository for	None
		alerts and events.
FHDbMonitor		Fault History database monitor.	FHDbEngine
FHPurgeTask		Fault History purge task.	None

	User Guide for Device Fault Manager
11-14	OL-11390-01