Setting Security Parameters
2.8 CiscoWorks2000 Device Fault Manager
Create an adapter for each instance of a CiscoWorks2000 DFM on the network (see Section 5.1,
“Creating an Adapter,” on page 193). See the integration information in the following sections and then modify the adapter properties (see Section A.9, “CiscoWorks2000 DFM,” on page 302).
Section 2.8.1, “Integrating CiscoWorks2000 DFM,” on page 43
Section 2.8.2, “Error Handling,” on page 44
Section 2.8.3, “Understanding the Discovery of CiscoWorks2000 DFM Elements,” on page 44
Section 2.8.4, “Understanding Element Conditions,” on page 46
Section 2.8.5, “Understanding Element Operations Permissions,” on page 46
Section 2.8.6, “Viewing Attributes, Details, Programs, and Libraries,” on page 46
Section 2.8.7, “Creating and Managing Instances,” on page 48
Section 2.8.8, “Running Instance Operations,” on page 50
Section 2.8.9, “Saving and Restoring the Element Repository,” on page 50
Section 2.8.10, “Understanding Event Notifications and Alarms Mappings,” on page 51
Section 2.8.11, “Alarm Properties,” on page 53
Section 2.8.12, “Subscribing to Events,” on page 54
Section 2.8.13, “Correlating Events,” on page 56
Section 2.8.14, “Recomputing the DFM Codebook,” on page 57
2.8.1 Integrating CiscoWorks2000 DFM
To integrate CiscoWorks2000 DFM:
1 Stop the Operations Center server.
For instructions, see “Stopping the Operations Center server in Windows” and “Stopping the Server and the mosdaemon manually in UNIX” in the Operations Center 5.0 Server Installation Guide.
2 Configure the Operations Center server to not restart automatically.
For more information, see the Operations Center 5.0 Server Configuration Guide.
4 Update or install the license file through the Operations Center Configuration Manager, if applicable.
The license file must contain one or more key entries for com.mosol.integration.smarts.DfmIntegration. 5 Restart the Operations Center server.
For instructions, see “Manually Starting the Operations Center Server” and “Starting the Operations Center Server in UNIX” in the Operations Center 5.0 Server Installation Guide.
6 Create an adapter for each instance of CiscoWorks2000 DFM on the network.
For instructions, see Section 5.1, “Creating an Adapter,” on page 193.
It is helpful to know the following information:
The hostname of the DFM Broker
The port that the DFM Broker listens on (default is 9002)
A valid user name and password, if DFM is running with authentication required
IMPORTANT: The Operations Center server and CiscoWorks2000 DFM both run processes that use port 9002. If installing the Operations Center server and CiscoWorks2000 DFM on the same machine, change the Operations Center database listener port from 9002 to another port. Use the Operations Center Configuration Manager to change the Listener Port value from 9002 to an unused port number for the General Datastore and BSA and Alarm History values.
2.8.2 Error Handling
The integration might throw exceptions in the case of errors or malfunctions. Operations Center logs all exceptions in a standard format. Each logging statement is associated with the following
categories: ERROR, INFO, WARN and DEBUG.
2.8.3 Understanding the Discovery of CiscoWorks2000 DFM Elements
The CiscoWorks2000 DFM adapter automatically performs element discovery and synchronization that include:
Discovery of all the technology elements from the DFM database and populating the Operations Center object model
Discovery of classes, instances, and relations between objects for use in the Service Views
Relationship mapping between object for n‐deep nested class/instance/relation sets
Subscriptions to event notifications
Management of instances (when available)
Element property mapping and property pages for elements
Automatic adapter updates for DFM instance create and delete notifications
Figure 2‐3 shows CiscoWorks2000 DFM elements displaying under the adapter:
Figure 2-3 Explorer Pane
The specific objects are implemented as proxy objects of the actual DFM objects. When Operations Center queries values (or other data), the adapter requests the data on‐demand from the DFM server.
The adapter caches some common data values for efficiency.
Operations Center aggregates all data from the various consoles into the element hierarchy. When comparing the Operations Center element hierarchy tree to the DFM console, typically more Relation instances display in Operations Center than in a single DFM console. This is because the DFM console only shows the relations applicable to that console.
In Operations Center, a unique key value identifies each element. The key value consists of a
concatenation of up to three string values delimited by a colon (:). This key value uniquely identifies the element instance in the Operations Center element repository.
A single element can have multiple parents in multiple locations in the element hierarchy. The element’s key value consists of the concatenation of the root hierarchy key plus all element keys for each of its parents.
Table 2‐4 describes DFM elements names.
Table 2-4 DFM Element Names
Element Type Name in Operations Center consists of…
Class The class name. For example:
Host
Instance The concatenation of the class with the instance name. For example:
Host:server.mosol.com
Relation The concatenation of the class, instance, and relation name. For example:
Host:server.mosol.com:ComposedOf
2.8.4 Understanding Element Conditions
Normally, the default condition algorithm determines the condition of a Operations Center element.
The default condition algorithm sets the element condition equal to the most critical severity of any alarm attached to the element or to its children. The exception is for relation elements, which do not propagate up their condition.
For information on changing the default algorithm, see Using Algorithms to Calculate Element State in the Operations Center 5.0 Server Configuration Guide.
2.8.5 Understanding Element Operations Permissions
The ability to perform operations on elements using the right‐click menu depends on the ACL permissions granted. Table 2‐5 outlines the ACL permission on various element menu operations.
Table 2-5 CiscoWorks2000 DFM—ACL Permissions on Element Operations
2.8.6 Viewing Attributes, Details, Programs, and Libraries
The CiscoWorks2000 DFM adapter property pages provide a way to review information regarding attributes, programs, libraries and other features.
To view the adapter property pages:
1 In the Explorer pane, expand Elements > Adapter:CiscoWorks2000.
2 Right‐click an element, then click Properties to open the Status property page.
3 Select different property pages to view specialized information about the Adapter, Instance, and Class elements.
Element Operation ACL Permission
Adapter (top-level) Add Subscription Define
Correlate Now Manage
Instance Create Define Instance Delete Define Recompute Codebook Manage Repository Save Define Repository Restore Define
Instance Manage Manage
Unmanage Manage
Delete Define
Table 2‐6 outlines the various information and features found in the property pages for the adapter root, class and instance elements.
Table 2-6 CiscoWorks2000 DFM Adapter and Element Property Pages
Element Type Property Page Description
Adapter Root Details Provides information about the adapter connection with the CiscoWorks Domain Manager, including status, socket port and timeout settings.
Correlation Provides information regarding the Correlation Codebook and its associated settings. For more information, see Section 2.8.13,
“Correlating Events,” on page 56.
Programs Displays the list of programs loaded in the server.
Libraries Displays the list of models loaded in the server.
Subscriptions Displays a list of event notification subscriptions (see Section 2.8.12,
“Subscribing to Events,” on page 54). Allows adding, changing, or deleting subscriptions.
Class Description Displays a textual description for the class element.
Attributes Provides the values of various attributes associated with the element.
Events Displays a list of simple events defined for this class. The simple event names display. Information on this page is read-only.
Operations Displays a list of all operations defined for this class.
2.8.7 Creating and Managing Instances
The DFM monitors managed instances. The DFM does not monitor unmanaged elements, but does probe them and stores element information in the DFM inventory.
When adding elements to or deleting elements from the Domain Manager from another client, the adapter receives notification about the event. The adapter automatically creates (or deletes) the appropriate class and instance elements, allowing for a lazy discovery of object relations.
“Creating an Instance” on page 49
“Deleting an Instance” on page 49
“Managing an Instance” on page 49
“Unmanaging an Instance” on page 49
Instance Attributes Provides the values of various attributes defined for the class. Refresh updates the attribute values in real time.
Attributes Access types:
MR_NO_ACCESS: Attribute value is unavailable.
MR_STORED: Sets the attribute value when the class is modeled or instantiated. If the attribute is not read-only, modify it at runtime (optional).
MR_COMPUTED: Computes the attribute value upon request.
Computed access types are always read-only.
MR_INSTRUMENTED: Retrieves attribute value from an external source through a protocol.
MR_PROPAGATED: Derives attribute’s value from the values of other class instances in which this class is involved in a relationship or relationship set.
MR_UNCOMPUTABLE: Cannot compute attribute value.
MR_COMPUTED_WITH_EXPRESSION: Computes attribute value upon request, using an expression. Computed access types are always read-only.
Events Displays a list of simple events defined for this class. Allows subscribing and unsubscribing to event notifications for the instance element (see Section 2.8.10, “Understanding Event Notifications and Alarms Mappings,” on page 51).
Operations Displays a list of all available operations for this element. Allows running a selected operation (see Section 2.8.8, “Running Instance Operations,”
on page 50).
Element Type Property Page Description