Cisco Systems OL-11390-01 manual Example 1 Specifying Clients that Can Connect to DFM, 11-18

Page 18

Chapter 11 Administering DFM (Advanced)

System Administration

Example 1: Specifying Clients that Can Connect to DFM

This example shows how to configure DFM to only accept client connections from the hostnames lucy and ethel. In this case you must unregister and reregister the DFM broker, server, and notification adapter processes.

Note To allow connections from processes running on the same host, specify the host's name—do not use “localhost.” This is because connections made using the DFM Broker will appear to come from the DFM Broker’s host. Only connections that explicitly specify “localhost” as the target address will appear to come from localhost. Such target addresses may result in configurations that forward incoming connections (such as through software that provides an encrypted tunnel).

Step 1 Unregister the processes.

a.Unregister the DFM notification adapters:

#NMSROOT/bin/pdcmd -u DfmFileNotifier

#NMSROOT/bin/pdcmd -u DfmMailNotifier

#NMSROOT/bin/pdcmd -u DfmTrapNotifier

b.Unregister the DFM server process:

#NMSROOT/bin/pdcmd -u DfmServer

c.Unregister the DFM broker process:

#NMSROOT/bin/pdcmd -u DfmBroker

Step 2 Reregister the processes, specifying the clients that can connect to the broker and server:

a.For the DFM broker (the following command is one line):

#NMSROOT/bin/pdcmd -r DfmBroker -e NMSROOT/objects/smarts/bin/brstart -f "--output --port=9002 --accept=lucy,ethel --restore=NMSROOT/objects/smarts/conf/broker.rps"

b.For the DFM server (the following command is one line):

#NMSROOT/bin/pdcmd -r DfmServer -e NMSROOT/objects/smarts/bin/sm_server -d DfmBroker -f

"--bootstrap=DFM_bootstrap.conf --accept=lucy,ethel --output --name=DFM"

When specifying other options (such as --privopen) for DfmServer, use one pdcmd instance. See Example 2: Configuring the DFM Server to Use a Privileged Port, page 11-19.

c.For DFM notification adapters (the following commands are each one line):

#NMSROOT/bin/pdcmd -r DfmFileNotifier -d DfmServer -e NMSROOT/objects/smarts/bin/sm_notify -f "--adapter=filelog --output=sm_file_notifier"

#NMSROOT/bin/pdcmd -r DfmMailNotifier -d DfmServer -e NMSROOT/objects/smarts/bin/sm_notify -f "--adapter=mail --output=sm_mail_notifier"

#NMSROOT/bin/pdcmd -r DfmTrapNotifier -d DfmServer -e NMSROOT/objects/smarts/bin/sm_notify -f "--adapter=trap --output=sm_trap_notifier"

 

User Guide for Device Fault Manager

11-18

OL-11390-01

Image 18
Contents File Ownership and Protection 11-1Working with Firewalls Secure Socket Layer SSLSNMPv3 11-2NMSROOT/objects/smarts/bin/smserver --help 11-3Configuring Users ACS and Non-ACS Registering Additional DFM Servers with the LMS Portal11-4 Configuring Users Using CiscoWorks Local Mode 11-5Using DFM in ACS Mode 11-6Creating Self-Signed Security Certificates Yearly Field Description Usage Notes11-7 Backing Up and Restoring DFM Data 11-8Before You Begin Changing the Password for DFM DatabasesOption Description Usage Notes 11-9Configuring Logging 11-10No. Folder Maximum Backup Function/ModuleViewing and Maintaining Log Files Log Files Size KBDPS 11-12Starting and Stopping DFM Processes Name Description Dependency11-13 11-14 Registering and Unregistering DFM Processes 11-15Option Description and Arguments 11-16Arguments 11-17Example 1 Specifying Clients that Can Connect to DFM 11-18Reregister any processes that depend on DfmServer 11-1911-20