Cisco Systems 1 Typical workflow for deploying Cisco PVM, Configure the NAMs in Your Network

Page 8

Access Layer: Place Cisco NAMs at the access layer only if critical clients are required to be monitored. IP phones, for example, can be monitored for latency or for adequate response to and from Cisco CallManagers.

WAN Edge: Place Cisco NAMs at the WAN edge to gather WAN statistics from Optical Services Module (OSM) or FlexWAN interfaces, or to collect NetFlow statistics on remote NetFlow-enabled routers. This can provide usage statistics for links, applications (protocol distributions), hosts, and conversations, which can be useful for trending data and capacity planning.

Branch Office: Place Cisco NAMs in the branch office to troubleshoot remote sites, similar to being on the campus, but taking full advantage of the remote accessibility and local data collection of the Cisco NAMs.

Typical workflow for deploying Cisco PVM

A user can expect to perform the following steps in deploying PVM.

Figure 2. Typical workflow for Deploying Cisco PVM

Initial steps of work flow such as installation and walk through of general PVM functionality are detailed in a section after the usage scenarios.

Configure the NAMs in Your Network

Once the NAMs have been strategically deployed in the network, it is imperative that they be configured to collect the appropriate statistics that can aid you in answering the questions you have about the traffic on your network. Cisco NAMs collect some traffic statistics by default. However, it is always a good practice to verify and ensure that the core statistics that you are interested in are indeed configured to be collected by the NAM. For more details on configuring NAMs consult the NAM Deployment Guide.

Note: The configuration of the NAMs can also be done after importing them into PVM.

Deploy PVM and add the NAMs in Cisco PVM

Once the NAMs have been deployed and configured, you can deploy PVM on any machine that meets the system requirements for PVM. The requirements specification is listed in detail in the PVM Requirements and Sizing section. After Cisco PVM is successfully installed, you can create and manage users who have access to Cisco PVM. You can also configure PVM with information regarding the NAMs and their associated devices that it should collect traffic data from as described in the PVM Setup section.

Cisco Internal Use Only

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

Page 8 of 66

Image 8
Contents Corporate Headquarters USA Cisco Performance Visibility Manager Data Collection and Traffic Analysis Traffic Analysis including Top-N AnalysisART Monitoring Historical Information NAM GUI Drill down CiscoWorks and Ldap IntegrationSample Deployment Scenario PVM in LAN and WAN Basic questions about the Problems to be addressed Placing Cisco NAM in Your NetworkDeploy PVM and add the NAMs in Cisco PVM Configure the NAMs in Your NetworkTypical workflow for deploying Cisco PVM Start monitoring your network using Cisco PVM Create the Datasource Groups DSGs in Cisco PVMNAM Setup Usage ScenariosUser Management through the GUI Cisco PVM Initial SetupUser Setup User management through Ldap Mapping Ldap users to PVM roles Adding a NAM through the GUICisco Internal Use Only Importing Multiple Devices User created CSV file Import File FormatsDCR Export 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 Scenario 2 Proactive Monitoring Create an ART Group that carries traffic you are interestedContd 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 Verify the link utilization on the client Branch Router Click RefreshClick Connect Cisco Internal Use Only Monitoring Traffic Analysis using Cisco PVMOverview of PVM functionality Cisco Internal Use Only Aggregation Schemes Real-Time and Trend Charts Report ViewsDrill-downs Report Name Drill-Down Reports Available ReportingCisco Internal Use Only Art Setup Application Response Time Analysis in Cisco PVMArt 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 Cisco PVM Requirements and Sizing Minimum Server Requirements HardwareSoftware Minimum Client Requirements HardwareDisk Space Required Cisco PVM Installation and UninstallationMaximum NAMs CPUs Install Procedure Cd PVMINSTALLDIR/j2sdk142/binUninstall Procedure Start and Stop Procedure $su pvmadm $pvm stopTroubleshooting Tips Maintaining and Troubleshooting Cisco PVMDatabase Management Purging and retention periodArchiving $su pvmadmGunzip -c archivefilenamecpio -icvB *switch Importing the archived filesConclusion Appendix Deployment Q&ACisco Internal Use Only Cisco Internal Use Only Deployment Troubleshooting Cisco Internal Use Only For More Information USA