Step 1 Create a perl file, for example, sample.pl and store it on your CiscoWorks Server.

Step 2 Update the perl file with the sample perl code given above to connect to the database.

Step 3 Save the changes to the perl file.

Step 4 Run the perl script using the following commands:

•NMSROOT/bin/perlPerl_file_name(on Solaris systems)

•NMSROOT\bin\perlPerl_file_name(on Windows systems)

where,

•NMSROOT — CiscoWorks Installation directory.

•Perl_file_name —Absolute file name of the perl script with the code to connect to the database.

For example, if you have stored the perl file sample.pl under C:\ in a Windows systems, and if the CiscoWorks installation directory is under D:\CSCOpx you must enter the following to run the perl script:

D:\CSCOpx\bin\perl C:\sample.pl

In the code snippet below, you must change the dsn names based on the application database that you want to connect:

Changing the Database Password

While installing CiscoWorks, the installer prompts you to enter the database password. If you do not enter the password, CiscoWorks generates the password at random.

However, we recommend that you change the password periodically to ensure system security.

You must use the dbpasswd.pl utility to change the database password.

See the following URL for detailed explanation on changing the database passwords on Windows Systems, changing the database passwords on Solaris systems, and the formats available for changing the database passwords:

Fault_Event_Details View Details

Event Details from DFM contains the properties and details of the event. Each event may have multiple property and the number of property is dependent on event type. So each property is represented as one row.

For example, if the event has five properties, there will be five rows for that event.

Table 17 Fault_Event_History Schema Details

Column Name

Column Type

Constraints

Column Description

Event_Id

bigint

Not null

Event identifier number

Event_Property_Name

varchar(32)

Null

Name of the property

Event_Property_Value

varchar(255)

Null

Property value

IPM Database Schema

The IPM database schema defines the tables, fields in each table and the relationships between fields and tables.

The IPM database schema details are updated after installing the application and launching the same. You do not need to run the dbaccess.pl utility to see the schema details.

Connecting to IPM Database

To connect to the IPM database, you may have to enter the following information:

•Username — DBA

•Database password — You must enter the database password that you have provided while installing CiscoWorks

The last time at which a set operation occurred on any of the objects in this MIB.

See MIB object:

rttMonApplTimeOfLastSet

DisplayName

Varchar(255)

Null

Display name of the device

IPSLAVersion

Varchar(16)

Null

See MIB object:

rttMonApplVersion

MIB type: DisplayString

Round Trip Time monitoring application version string

CollCount

Integer

Null

Estimated number of configurable operations in the router.

See MIB object:

rttMonApplProbeCapacity

LastRebootTime

timestamp

Not null

Last reboot time of the source device

Note Source Table (table name `Source') contains all necessary information about a source router. A unique device ID is assigned to each source router. This device ID acts as the Primary Key of the table.

Target Table (table name Target) contains all information about a target. This target could be an SAA router, IPSLA responder enabled device, or an adhoc device. A unique device ID is assigned to each target in the table. This device ID acts as the Primary Key of the table.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0903R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.