Cisco Systems 1 manual Database Management, Purging and retention period, Archiving, $su pvmadm

Page 57

Cisco PVM is a database intensive software application. Similar to any database-driven application, Cisco PVM has some maintenance activities that the user can perform to ensure good performance and trouble free use. The most important aspect of the maintenance activities is database management.

Database Management

Cisco PVM uses 2 database instances to store the data it collects. Raw traffic statistics that are collected by the system are stored in the OLTP database. This database is a relational database and also contains the configuration information like devices, DSGs and users for Cisco PVM. The other database instance is an OLAP database where Cisco PVM stores aggregated information. This database is non-relational and is optimized for data mining and retrieval. The instance ids and the default roles are as follows:

–OLTP:

SID: CNAM

User: cnam / manc1521 Role: USER

– OLAP:

SID: SPDW

User: tadw / tadw Role: USER

– OLTP & OLAP:

 

tadwop / tadwop

Role: Operator

dw/password

Role: DBA

Note:

 

1.It is recommended that the user change these database passwords after installation.

Purging and retention period

Raw traffic statistics are aggregated and converted into OLAP artifacts by Cisco PVM. Raw traffic statistics are retained in the OLTP datastore for 2 days after which they are purged from the database. The aggregated data in OLAP is retained based on retention policies defined in the database. These retention periods default to 3 months for hourly data, 1 year for daily data and 3 years for monthly data. You can change these retention periods by using standard SQL to modify the records in the database. To change the OLTP retention period, change the value of the RETENTION_PERIOD column in the TA_RETENTION table of the CNAM database. To change the OLAP retention period, change the values of the RETENTIONPERIOD column in the RETENTION table of the SPDW database. Login as dw to make the changes.

The purge process in Cisco PVM is enabled by default and cannot be disabled.

Archiving

Cisco PVM allows the user to archive, the data that has been collected and aggregated and the configuration information from Cisco PVM for storage. The archive process has many options that the user can specify to either schedule the archive or run immediately. Using the appropriate switches, the user can archive both raw traffic statistics, historical data, and backup configuration information for later use on another installation of Cisco PVM.

The archive process is disabled by default. When enabled, the archive process archives only that information not previously archived. Archives can be re-imported into Cisco PVM. This re-imported data is not archived again.

The archive process can be enabled or disabled by using the following command:

$su – pvmadm

Cisco Internal Use Only

Copyright © 2006 Cisco Systems, Inc. All rights reserved.

Page 57 of 66

Page 56 Page 58
Image 57
Page 56 Page 58
Contents Corporate Headquarters USA Cisco Performance Visibility Manager Traffic Analysis including Top-N Analysis Data Collection and Traffic AnalysisART Monitoring Historical InformationCiscoWorks and Ldap Integration NAM GUI Drill downSample Deployment Scenario PVM in LAN and WAN Placing Cisco NAM in Your Network Basic questions about the Problems to be addressedConfigure the NAMs in Your Network Typical workflow for deploying Cisco PVMDeploy PVM and add the NAMs in Cisco PVM Create the Datasource Groups DSGs in Cisco PVM Start monitoring your network using Cisco PVMUsage Scenarios NAM SetupCisco PVM Initial Setup User SetupUser Management through the GUI User management through Ldap Adding a NAM through the GUI Mapping Ldap users to PVM rolesCisco Internal Use Only Importing Multiple Devices Import File Formats DCR Export FileUser created CSV file Datasource Group DSG Creation Cisco Internal Use Only Scenario 1 Traffic Profiling Contd Cisco Internal Use Only Cisco Internal Use Only Cisco Internal Use Only Contd Create an ART Group that carries traffic you are interested Scenario 2 Proactive MonitoringContd Click the Setup tab Click the Thresholds menu item Click Add Contd Cisco Internal Use Only PVM displays the details of the threshold violation Scenario 3 Troubleshooting Click Refresh Verify the link utilization on the client Branch RouterClick Connect Cisco Internal Use Only Traffic Analysis using Cisco PVM Overview of PVM functionalityMonitoring Cisco Internal Use Only Aggregation Schemes Report Views Real-Time and Trend ChartsDrill-downs Reporting Report Name Drill-Down Reports AvailableCisco Internal Use Only Application Response Time Analysis in Cisco PVM Art SetupArt Reports Cisco Internal Use Only ART Report Archives Baselining and Alerts in Cisco PVM Cisco Internal Use Only Generating Snmp Traps Alerts in Cisco PVM Cisco Internal Use Only Minimum Server Requirements Hardware Cisco PVM Requirements and SizingSoftware Minimum Client Requirements HardwareCisco PVM Installation and Uninstallation Maximum NAMs CPUsDisk Space Required Cd PVMINSTALLDIR/j2sdk142/bin Install Procedure Uninstall Procedure $su pvmadm $pvm stop Start and Stop ProcedureMaintaining and Troubleshooting Cisco PVM Troubleshooting TipsPurging and retention period Database ManagementArchiving $su pvmadmImporting the archived files Gunzip -c archivefilenamecpio -icvB *switchConclusion Deployment Q&A AppendixCisco Internal Use Only Cisco Internal Use Only Deployment Troubleshooting Cisco Internal Use Only For More Information USA
Top Page Image Contents