|
|
The core of each CiscoWorks Blue Maps application is a set of database tables and daemons. For the RSRB Map application, this appendix describes the command line syntax for starting its daemons and relationship of its daemons to the database tables.
cwbmonitord [-s] [-f] [-h] [-d] [-v] [-c] UDPport
cwbrsrbpollerd [-s] [-f] [-h] [-d] [-v] PollingInterval
cwbdlswpollerd [-s] [-f] [-h] [-d] [-v] PollingInterval
cwbsyncd [-s] [-f] [-h] [-d] [-v] SyncInterval
cwbrsrbdiscoverd [-s] [-f] [-h] [-d] [-v] DiscoverInterval
cwbdlswdiscoverd [-s] [-f] [-h] [-d] [-v] DiscoverInterval
cwbrsrbtrapd [-s] [-f] [-h] [-d] [-v]
Where:
-s stops a running instance.
-f force-starts the daemon.
-h displays a help message.
-d enables debug mode.
-v displays the version number of this daemon.
-c starts with an empty client list. Without this option, the Monitor daemon reestablishes the list of GUI application clients that were registered when it was last run. See "Client List Table" in the appendix "CiscoWorks Blue Maps Database Tables".
UDPport is the User Datagram Protocol port to which a GUI application listens. The default is 6000. If a GUI application will be instructed to listen to a nondefault port number, enter that number here.
Intervals are in seconds.
This section introduces to the role of tables and daemons in the operation of RSRB Map and provider a detailed description of each daemon.
In the first phase of operation, a table of IP devices is populated by the Sync daemon from the network management system, or the user creates a seed file of IP devices and populates the table by using either of the following methods:
In the second phase of operation, the Discovery daemon collects the list of IP devices and communicates with each device to determine which ones are RSRB-enabled routers.
In the third phase of operation, the Poller daemon queries known RSRB routers, and the Trap daemon receives unsolicited messages from those routers (via the NMS), and management information is forwarded to tables in the RSRB Maps application. When the Monitor daemon detects a change in the tables, it updates the graphical map accordingly.
The following daemon descriptions contain references to the database tables in the appendix "CiscoWorks Blue Maps Database Tables". Daemons labeled CWB are used by more than one CiscoWorks Blue Map application. Daemons labeled RSRB, APPN, or DLSw are application-specific.
The status of every daemon is stored in the Process table (Table B-1).
| Daemon | Name |
|---|---|
cwbmonitord | Monitor daemon |
cwbrsrbpollerd | Poller daemon |
cwbsyncd | Sync daemon |
cwbrsrbdiscoverd | Discovery daemon |
cwbrsrbtrapd | Trap daemon |
The Poller daemon queries the following MIB variables in known RSRB-enabled devices (those in the Devices table flagged discovered):
If a known RSRB-enabled (discovered) device does not respond to the Poller's SNMP query, the Poller daemon sets that device to Inactive in the Devices table. If the device responds with its current peer table, the Peer table is updated in the database.
The Sync daemon is responsible for synchronizing the RSRB database with the network management system's database. The Sync daemon obtains a list of all IP routers in the network from the NMS and stores these in the RSRB database. The routers in this list will subsequently be queried by the Discovery daemon to discover which ones are RSRB-enabled. (If a list of IP routers is not available from the NMS, the list can be supplied directly to the Discovery daemon. This alternative to using the Sync daemon is explained in the section "RSRB Discover Daemon.")
Depending on how often you expect the NMS to have new routers in its own database, you can set the Sync daemon to run at various intervals or not at all.
Before you execute the Sync daemon, you should discover your network by using your network management's discovery feature or automanagement feature. In addition, the Sybase database must be configured.
If started, the Sync daemon continuously executes in the background and retrieves a complete list of IP devices or routers periodically. If a device already exists in RSRB's database when the Sync daemon operates, the Sync daemon does not alter information about that device. If information about an IP device is absent from the Sybase table, the Sync daemon lists that device in the Sybase table and flags the entry as not discovered.
You can control the frequency with which the Sync daemon performs synchronization, or whether it runs at all. For example, if you know that no new devices are being added to your network, you do not need to run the Sync daemon.
To ensure that the Sybase tables contain the most current information about the IP devices or routers in your network, run the automanagement feature of your network management system. Otherwise, your network management database will be static and the Sync daemon need not update RSRB's database.
The Sync daemon does not detect the removal of IP devices from the network. The RSRB database is not affected by device removal until the Discover daemon operates and marks nonexistent routers as inactive due to lack of response to SNMP. Inactive devices remain in the RSRB database until you remove them by using Edit> Delete Device in the GUI.
If you have a dynamic network and expect to configure new or existing routers with RSRB, run both the Sync daemon and the Discover daemon to ensure that the database used for RSRB Maps reflects your current RSRB network topology.
When executed, the Discover daemon queries all IP devices in the RSRB database that are flagged not discovered. A device is set to not discovered when the following occur:
If the device responds to the RSRB query, the Discover daemon updates the RSRB Devices table to indicate that the node is an RSRB node. If the device responds to an SNMP query, it is flagged as discovered in the devices table.
Here are the MIB variables used by the DLSw Poller daemon:
Here are the MIB variables used by the DLSw Discover daemon:
Posted: Thu Aug 19 11:41:30 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.