Cisco Network Collector Quick Start Guide For As Transactional Customers

Cisco Network Collector
Quick Start Guide for AS Transactional

Customers
For Windows 2000/XP/2003 and Solaris SunOS 5.8

CNC Version 5.x
February 19, 2007
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
EDCS-359623
CNC Quick Start Guide
TABLE OF CONTENTS
Introduction ............................................................................................................................................... 1
Purpose .................................................................................................................................................... 1
Scope and Program Limitations .............................................................................................................. 1
Audience.................................................................................................................................................. 1
CNC v5.x Overview .................................................................................................................................. 1
Usage Restrictions................................................................................................................................... 2
Download and Install the CNC Software .................................................................................................. 2
Read the Release Notes ............................................................................................................................. 2
Access CNC............................................................................................................................................... 3
Add Devices............................................................................................................................................... 5
View Inventory Status and Inventory Details............................................................................................ 8
Modify Device Access............................................................................................................................. 10
Access Verification ............................................................................................................................... 12
Retrieve and Verify Configuration........................................................................................................ 14
Net Audit ................................................................................................................................................. 16
Transfer Inventory and Reports Data to Cisco ........................................................................................ 20
Network Profile Backend page................................................................................................................ 21
Troubleshooting....................................................................................................................................... 22
Discovery Hangs ................................................................................................................................... 22
Import the Seed File............................................................................................................................ 22
View the Inventory ............................................................................................................................. 23
Run Device Inventory Again .............................................................................................................. 24
Appendix A—CNC FAQs ....................................................................................................................... 26
Appendix B—CNC Commands............................................................................................................... 28
Terminating CNC Processes to Restore System Resources.................................................................. 28
© 2007 Cisco Systems, Inc. All rights reserved.

Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page i
Introduction
Purpose
The Cisco Network Collector (CNC) Quick Start Guide is a simple step-by-step guide to quickly start using the CNC Version
5.x GUI to perform customer network hardware and software discoveries and inventories and Net Audits, and transfer that
data back to Cisco.
Scope and Program Limitations

This quick start guide is a summarized tutorial on using the installed CNC tools on your server, enabling you to compile a
software and hardware inventory from a customer network, and securely transfer the data back to Cisco. This guide assumes
that all procedures in the companion Cisco Network Collector (CNC) Installation Guide have been completed before using
this quick start guide.
CNC also has the capability to conduct network audits, network profile data collections, and generate reports. For auditing
customer networks, Cisco’s Advanced Services should be engaged. If your customer is interested in a network audits, please
contact the Advanced Services Manager within the customer’s region.
Note: Discovery is currently limited to a maximum of 5000 devices. For a list of supported devices, click:
http://commanche/NP/rbml/LWCDEVICE.html.
Audience
The CNC tool is intended for use by Cisco Systems Advanced Services (AS). Installation and deployment of CNC on a
customer network and subsequent analyses of the inventory data should be performed by Network Consulting Engineers and
the customer’s STS Support engineer.
CNC v5.x Overview

Cisco Network Collector (CNC) is an automated network discovery and inventory tool. CNC tracks all network elements
discovered or added from a seed file, providing timely delivery of network information to Advanced Services (AS)
engineers. Data collected by CNC is used to generate Network Profile Reports and Net Audits that detail the network
inventory and present Cisco hardware and software analyses. Collected and/or inventoried data from a customer network is
securely transported back to Cisco by HTTPS, using the Advanced Encryption Standard (AES)-128 which incorporates 128
bit encryption.
Version 5.x of the CNC tool is a Java-based tool. It is supported on Windows 2000 Pro, Windows XP, Windows 2003 and
Solaris platforms, with the Java Runtime Engine, and Microsoft Internet Explorer web browser.

Page 1
Usage Restrictions
CNC is used by various programs within Cisco. However, AS subscription customers are entitled to the full functionality of
the tool.
Download and Install the CNC Software

Follow the instructions in the CNC Installation Guide and ensure your server is prepared and meets the minimum software
requirements for installation. Download and install the CNC software following the instructions.
Read the Release Notes

After installing the CNC software, download the Release Notes from the same location. Check the Release Notes for important
information, known issues, and patch availability before using CNC.

Page 2
Access CNC
Follow the steps in the table below to get started using CNC.
Procedure Access CNC

Step 1. Start CNC by double-clicking the icon
on your desktop.
Step 2. Use the following default login

name and password for this initial
login session:
• User Name: natkadmin
• Password: natkadmin
A successful login will take you to
the CNC Reports page. For
security reasons, you should next
change your login password.

Page 3
Procedure Access CNC
Step 3. Go to the System Setup tab, and click

Security.
Step 4. Enter your old password, your new

password, retype your new password,
and click Modify User Details.

Page 4
Add Devices
Next you will need to add your devices to CNC. There are three ways to do this:
• Device Discovery
• NMS Integration
• Importing a Seed File
Device Discovery can be performed by clicking Device Discovery Administration from the Discovery option of the Device
Manager tab, and following the steps provided by the Wizard. Explanation of the options provided by the Wizard is given in the
CNC User Guide. For all other details and aspects of discovery configuration, such as additional options, filters, scheduling,
etc., please also consult the CNC User Guide.
NMS Integration is supported with CiscoWorks RME versions 3.3, 3.4 and 3.5 on the Solaris platform. A small package must be
installed on the customer’s CW box to enable the NMS integration functionality. This package can be obtained by contacting
your Cisco network consulting engineer.
Importing a Seed File is the easiest and most common way of adding devices, and is the method described below. You can use
the import seed file method if the customer’s network is running CiscoWorks 2000/Resource Manager Essentials to manage all
devices. First, you will need to export a Seed File from their RME server as follows:
Step 1. Select Resource Manager Essentials > Admin > Inventory and choose Export to File
Step 2. Save file as 1.0 CSV format. This will give you a Seed File like the following example:
Sample Seed file
//
snmp ro
snmp rw
serial number
user field 1
user field 2
user field3
user field 4
telnet password
enable
enable secret
tacacs username
tacacs password
tacacs enable username
tacacs enable password
local user
local password
rcp user
rcp password
//
Step 3. Next, follow the steps in the table below to import the Seed File.

Page 5
Procedure Add Devices

Step 1. From the Device Manager tab, click
Device List.
Step 2. From the TOC on the left, click Add

Devices.
Step 3. In the Add Methodology section, select

the Import from Seed File option.

Page 6
Procedure Add Devices
Step 4. Browse to find your file.
Step 5. Make sure Perform Full Inventory Now is

selected, and click Import.

Page 7
View Inventory Status and Inventory Details

After device discovery is completed, all the discovered managed devices should show up in inventory. This section describes
how to view inventory progress on devices, and view inventory details.
To view the current inventory status of discovered devices, use the following procedure:
Procedure View Inventory Status and Inventory Details

Step 1. If you are not already viewing the Device
Manager tab, click that to view that
screen. Then click Inventory and then
click View Device Inventory Status from
the TOC menu.
Step 2. The status bar now displays completed

progress percentage in green and
unfinished discovery percentage in red.
When the entire bar is green, the
inventory is complete for all network
devices.
Step 3. When the discovery is complete, select

View Device Inventory Details from the
TOC menu. You should now see an
inventory status of all devices, Review
the status screen to confirm that all the
devices inventoried are listed in “Active
Device” state. (Configurations are not
necessary for IOS/CatOS profile
generation). See the explanation of
device states reported below.

Page 8
The IP address of each device is listed in the Available Devices column of the Device Inventory Viewer screen.
The Inventory Summary screen lists a summary of devices, giving the following information:
• TOTAL DEVICES. Total number of devices added into CNC.

• ACTIVE DEVICES. All devices which are currently in active status. All devices which are currently accessible via the
given SNMP RO string.
• CONFIG COLLECTED: All devices for which config is collected, that is, either running or startup config.
• MANAGED DEVICES: All devices which are either currently active or was active earlier.
• NON-CISCO DEVICES: All devices which are neither Cisco device nor parent company is Cisco.
• DEVICE ADDED: All devices which are added into CNC but inventory collection is not started.
• DEVICE UNREACHABLE: All devices which are currently not accessible via the given SNMP RO string.
• CONFIG FAILED: All devices for which config collection is tried but config collection failed.
• UNMANAGED DEVICES: Devices for which inventory is not collected at all or devices which are always in “not
reachable” state or devices which are always in “device added” state, that is, all devices which are not listed in managed
devices are unmanaged.
Note on Device Installed Memory: To capture devices’ installed memory, you must have telnet user level access to the device,
provided by the customer. For more information on telnet access and getting installed memory data, see “Modify Device” in the
following section.

Page 9
Modify Device Access

For Telnet Users Only: Use the following procedure only if you have a customer-provided Telnet username and password to the
devices on the customer’s network.
For modifying the access information (telnet username/password, SNMP, enable password or enable secret), follow the
instructions in the table below. You can modify all the devices in one attempt (if same username password applies to all of them)
or modify the devices one by one.
• To obtain the installed memory of all devices, CNC must run the show version command.
• If you do not require the device memory or device config information, skip this procedure and proceed to the “Net
Audit” or “Transfer Data to Cisco” section. The Net Audit or CNC report can be processed properly without these
procedures.
Procedure Modify Device

Inventory.
Step 2. In the Device Inventory-Details screen,

click the checkbox next to the Device
Name of the device you want to modify.

Page 10
Procedure Modify Device

Step 3. Click Modify Access Method.
Step 4. In the Modify Access Method screen,
click the checkbox next to the access
methods you want to enable, and click
Apply.
Step 5. Continue with the Access Verification
section below.

Page 11
Access Verification
After modifying device access information, perform access verification by following the steps in the table below:
Procedure Access Verification

Access Verification.
Step 2. Scroll to the bottom of the screen and

click Verify Failed Devices.

Page 12
Procedure Access Verification
Step 3. Access Verification is scheduled. To

verify if devices can be reached with
telnet/ping/SNMP, click Access Verification
Report from the TOC on the left.
Step 4. Enter the necessary parameters in the

Access Verification Report screen, and click Run.
Step 4. Check to verify if devices can be reached

with telnet/ping/SNMP or not. Don't worry about
SSH if SSH is not enabled. If access verification
fails for any device then make sure that correct
credentials are provided for that device.
Continue with the Retrieve Configuration section

below.

Page 13
Retrieve and Verify Configuration
After you have verified access to the modified devices, you will need to schedule a full inventory to retrieve and verify
configuration information. To retrieve and verify configuration information, follow the steps in the table below:
Procedure Retrieve and Verify Configuration
Inventory.
Step 2. From the TOC on the left, click View

Device Inventory Details.
Step 3. In the Group Name box, select All, click

the Select All checkbox, and click Add to
Selected Devices.
Step 4. In the Selected Devices box, click the
Select All checkbox, in the View
Selected Information box click Device
Configuration, and click View.

Page 14
Procedure Retrieve and Verify Configuration

Step 5. The Inventory Detail screen appears,
allowing you to verify configuration
details.
Step 6. Scroll to the left and click a Device

Running Configuration link.

Page 15
Net Audit
Important Notes:
• In Step 2 below, never click the Submit button more than once. If you do, all net audit data will be lost and not
recoverable.
• Some7 day audits may take longer than 7 days, sometimes as many as 10 or 11, so don’t return the laptop until it is
finished.
o Since the last telnet iteration starts at the end of the 7 days, if you have a 300 device switch v4 audit, the telnet
alone will take about one to two days to finish at the end, so you have a 9 day audit.
o If download task and preparser for telnet comes in, then it will be an additional one or two days, so you will
have a 10 day audit. It is suggested not to power off the laptop at all until you get confirmation from your CNC
support engineer.
To perform a net audit, follow the steps in the table below:

Procedure Net Audit
Step 1. From the Audit tab, click Register Audit.
Step 2. Enter your Authentication Key and any

other optional information, and click
Submit.

Page 16
Procedure Net Audit

Step 3. From the Audit tab, click Audit Settings.
Make sure the information is correct.
Step 4. From the Audit tab, click Device

Selection. Select all the devices you
want to run audit for. Click Next. The
Start/Stop Data Collection page appears.

Page 17
Step 5. Click Start Data Collection Now. The

Data Collection Status page appears.
Step 5. On the Data Collection Status page you

can monitor the audit progress. The
audit will finish running and transfer the
data back to Cisco by itself.
Step 7. This next step is to be performed when

you are in the Cisco network. Go to
Download->Schedule Download and
schedule the transfer of data to the
backend. From here on, the Tools group
will process the data and post the data on
the Network Profile page. Now whatever
you are transferring is not the audit data
itself.

Page 18
Step 8. Confirm the audit data was successfully

transferred to Cisco. The audit data
transfer is an automated process, and it
starts one hour after the audit finishes.
After you arrive at Cisco, to run it
manually, go to
../CSCONsap/bin/supportutilits/
Type run start_download, and make sure

you call your CNC support engineer to
make sure they receive the audit data
before you schedule a new audit.
You will receive an email stating the

audit is ready for review; the SLA is 7
days after data download.
If you want to schedule a new audit, you

need to get a new authentication key
from the dashboard and register the
audit.

Page 19
Transfer Inventory and Reports Data to Cisco

Use the Correct Data Transfer Certificate to Ensure Data Transfer: The correct Data Transfer Certificate must be
provided to Cisco before the inventory file is transferred. Otherwise, the collected data will not be accepted at the CCO
backend. Normally, the certificate is located at ../CSCONsap/lib/classpath/xxxxxxx.cer
The Data Transfer certificate is completely different from the Entitlement certificate you entered when installing CNC. For
more information, see Appendix A: FAQs.
Procedure Transfer Data to Cisco
Step 1. From the Data Transfer tab,
choose the Set Parameters option from the
menu. Then check the Enable Data
Transfer check box and click Save
Configuration.

Page 20
Procedure Transfer Data to Cisco
Step 2. From the Data Transfer tab

select the Select Modules option.
Uncheck any modules you do not
want to transfer and click Submit.
This will transfer the selected
data to Cisco immediately.
Step 3. Click on Inventory Data Transfer

Status from the TOC menu to see
the transfer status.
Network Profile Backend page
Currently, after data download and audit download if you want a report right away, you need to call the support engineer to have
the NP run manually for the ID, and tell them the ID. Or you can wait, but since the backend is profiled once every 24 hours
hence may have to wait another day before scheduling the report. The CNC support engineer will call an infrastructure engineer
to have the process done if needed immediately.
You may then to review the web page at: http://commanche/cgi-bin/netw/np/np_viewer.pl?p_cust_id=&cust.id=xxxx
Replace the above xxxx with your ID number. You may then select the REP tab and schedule IOS profile report, SSR report and
Cat OS report. To get a BP report, select the Other links under the home page, select Extract Device Configurations, and select
all devices and get the zip and tar file.
After you get the file, select the BP tab, from a regular CNC page, eg:
http://commanche/cgi-bin/netw/bp/main.pl?p_cust_id=&cust.id=care and select On demand and then On demand batch. Upload the file
and then you will receive a BP report.

Page 21
Troubleshooting
The topics in this section give general guidelines to resolving common issues.
Discovery Hangs
Use the procedures in this section if the discovery process either dies or hangs, or if you need to manually stop discovery to
import the device data for inventory collection. This section includes the following procedures:
• Import the Seed File

• View the Inventory
• Run Device Inventory Again
Import the Seed File

After discovery is finished, a list of devices is displayed. Use notepad to open the file that lists the discovered devices from
the following path:
c:\progra~1\CSCONsap\objects\CSCOad\nsa\natkit\data\crmexport.txt
Import the Seed File using the procedures outlined in the section above titled “Add Devices”.

Page 22
View the Inventory

Use the procedure in this section to start the inventory process for devices and to collect inventory via SNMP:
Procedure View the Inventory
Step 1. To view the inventory process, select
Inventory from the Device Manager
tab.
Step 2. Click View Device Inventory Status.
Devices will be listed in one of the following states:
• TOTAL DEVICES. Total number of devices added into CNC.

• ACTIVE DEVICES. All devices which are currently in active status. All devices which are currently accessible via the
given SNMP RO string.
• CONFIG COLLECTED: All devices for which config is collected, that is, either running or startup config.
• MANAGED DEVICES: All devices which are either currently active or was active earlier.
• NON-CISCO DEVICES: All devices which are neither Cisco device nor parent company is Cisco.
• DEVICE ADDED: All devices which are added into CNC but inventory collection is not started.
• DEVICE UNREACHABLE: All devices which are currently not accessible via the given SNMP RO string.
• CONFIG FAILED: All devices for which config collection is tried but config collection failed.
• UNMANAGED DEVICES: Devices for which inventory is not collected at all or devices which are always in “not
reachable” state or devices which are always in “device added” state, that is, all devices which are not listed in managed
devices are unmanaged.

Page 23
Run Device Inventory Again

Run the inventory process again so that the device lists include the additional inventory received via telnet, or if you forgot to
check the Start Inventory check box earlier. To run the device inventory again, select Inventory from the Device Manager tab
and use the following procedure:
Procedure Run Device Inventory
Step 1. Select Device Inventory Collection
from the TOC menu.
Step 2. In the Group Name box, select All.
Step 3. In the Available Devices list, click the
Select All checkbox, and click Add to
Selected Devices.
Step 4. In the Selected Devices list, click the
Select All checkbox.
Step 5. In the View Selected Information list,
click the Select All checkbox, then
click Submit to start the inventory.
Step 6. To see the status of your inventory

collection, select View Device
Inventory Status from the TOC menu
on the left to display the View
Inventory Status screen. Click Refresh
to update the screen with the latest
status.

Page 24
Procedure Discovery Dashboard: Inventory

Step 7. After inventory is completed, select the
Reports tab and then Network Profile
from the menu to view the complete
status of the inventory. Click Refresh to
display the latest network profile
information.

Page 25
Appendix A—CNC FAQs

Q. The CNC discovery process does not find anything in the inventory; what are the possible causes?
A. Most likely, this is the result of an invalid SNMP read only access. Try the following procedure to check whether your computer has
SNMP access:
Download the snmputil.exe utility from the CNC website at http://astg.cisco.com/products/CNC%203.0/software.html.
Use this utility to access the first router in your seed IP address configuration. Check if the SNMP read only string is correct.
If the string is correct, then check the SNMP access list configured on the first router. Your computer IP address may not have access privileges
for SNMP queries if it is not on the router’s SNMP access list.
For CDP and IP Route Table based discovery, the first router must be accessible by SNMP. If the first router is not accessible by SNMP, then
no devices will be discovered.
Q. Which logs should I read to investigate problems?

A. From CNC, select the Reports tab option Logs and Errors to view various types of logs and error messages.
Q. Why do devices become unmanaged (active)? And, how can I troubleshoot this state?
A. Devices become unmanaged for the following reasons:
• A hostname problem due to an invalid DNS server or DNS server entry. To remedy, try issuing a PING to the hostname,
and check your PC DNS settings.
• An IP address problem may be due to an n invalid gateway setting. Check your TCP/IP settings in your PC network
control panel.
• If devices are still unmanageable, use snmputil.exe to attempt a MIB walk (e.g. snmputil.exe walk devicename snmpro
.1.3.6 to see if you can get a response. If you still get no response, then verify your SNMP read only strings, and check
SNMP access list settings on device).

Page 26
Q. Why do devices remain pending in the Inventory collection?

A. Where a large number of interfaces are associated with certain devices, more time is required to complete the inventory. However, if you
see large number of devices pending, this may indicate a software problem. In cases where devices are already discovered, you can rule out
SNMP or DNS problems. From command line, type the following command strings to reactivate devices:
net stop InventoryServer
Wait one minute, and then type the following command string:
Net start InventoryServer
Wait one minute, and then type the following command string:
Net stop CollectionServer
Wait one more minute, and then type the following command string:
Net start CollectionServer
Q. What is the difference between entitlement certificate and data transfer certificate?
A. During the install of the CNC software, it will ask you for the path to a file before you can continue. This file is called the Entitlement
certificate Obtaining the Entitlement certificate is part of the process you do at CCO for getting the transaction ID. The Entitlement certificate
is necessary to verify you are allowed to use CNC, and what features are enabled for you depend on your program. Each certificate represents a
different customer and can not be used for anything else.
The Data Transfer certificate is the encryption key used by the software to handshake with the Cisco backend. This certificate is located at
../CSCONsap/lib/classpath/xxxxxxx.cer, not the outback.cer and you need to upload the certificate into the CCO for the backend to be able to
handshake.
Q. What will happen if the Data Transfer certificate did not get imported?
A. If the Data Transfer certificate is not imported, then the transferred data file will be disregarded by Cisco and you will not get a report.
Please be sure to import the certificate.

Page 27
Appendix B—CNC Commands

Task Command
Check status of CNC processes run psshow
Terminate all, or selected, CNC processes run psterm [serverName/All]
Start all, or selected, CNC processes run psexec [serverName/All]
Re-initialize CNC database to use CNC package for run reconfigureCNC.pl [customer ID]
different CNC ID
Download CNC run java
com.cisco.nettools.downloader.sa.DownloadD
ataCollector
Create CNC database run create.db –n CNC –f
Start CNC database run start.db –n CNC –f
Stop CNC database run stop.db –n CNC -f
Note: Wait two minutes for processes to terminate before restarting. Then, wait another two minutes for processes to start
up again
Terminating CNC Processes to Restore System Resources

CNC requires a large amount of processing resources on the server. We recommend that the CNC server be a standalone
server set aside purely for the CNC application. All other applications and/or processes running on the server should be
disabled.
• To terminate CNC processes, go to the PC command line interface (Choose Run from Windows’ Start menu to access),
type run psterm all, and press Enter.
• To restore CNC processes to use the tool later, go back to the command line, type run psterm all and press Enter.

Page 28

Cisco Network Collector Quick Start Guide For As Transactional Customers

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Cisco Network Collector Quick Start Guide For As Transactional Customers

Încărcat de

Drepturi de autor:

Formate disponibile

Cisco Network Collector

Quick Start Guide for AS Transactional

For Windows 2000/XP/2003 and Solaris SunOS 5.8

© 2007 Cisco Systems, Inc. All rights reserved.

Scope and Program Limitations

CNC v5.x Overview

© 2007 Cisco Systems, Inc. All rights reserved.

Download and Install the CNC Software

Read the Release Notes

© 2007 Cisco Systems, Inc. All rights reserved.

Procedure Access CNC

Step 2. Use the following default login

© 2007 Cisco Systems, Inc. All rights reserved.

Procedure Access CNC

Step 3. Go to the System Setup tab, and click

Step 4. Enter your old password, your new

© 2007 Cisco Systems, Inc. All rights reserved.

© 2007 Cisco Systems, Inc. All rights reserved.

Procedure Add Devices

Step 2. From the TOC on the left, click Add

Step 3. In the Add Methodology section, select

© 2007 Cisco Systems, Inc. All rights reserved.

Procedure Add Devices

Step 4. Browse to find your file.

Step 5. Make sure Perform Full Inventory Now is

© 2007 Cisco Systems, Inc. All rights reserved.

View Inventory Status and Inventory Details

Procedure View Inventory Status and Inventory Details

Step 2. The status bar now displays completed

Step 3. When the discovery is complete, select

© 2007 Cisco Systems, Inc. All rights reserved.

• TOTAL DEVICES. Total number of devices added into CNC.

© 2007 Cisco Systems, Inc. All rights reserved.

Modify Device Access

Procedure Modify Device

Step 2. In the Device Inventory-Details screen,

© 2007 Cisco Systems, Inc. All rights reserved.

Procedure Modify Device

© 2007 Cisco Systems, Inc. All rights reserved.

Procedure Access Verification

Step 2. Scroll to the bottom of the screen and

© 2007 Cisco Systems, Inc. All rights reserved.

Procedure Access Verification

Step 3. Access Verification is scheduled. To

Step 4. Enter the necessary parameters in the

Step 4. Check to verify if devices can be reached

Continue with the Retrieve Configuration section

© 2007 Cisco Systems, Inc. All rights reserved.

Retrieve and Verify Configuration

Step 2. From the TOC on the left, click View

Step 3. In the Group Name box, select All, click

© 2007 Cisco Systems, Inc. All rights reserved.

Procedure Retrieve and Verify Configuration

Step 6. Scroll to the left and click a Device

© 2007 Cisco Systems, Inc. All rights reserved.

To perform a net audit, follow the steps in the table below:

Step 2. Enter your Authentication Key and any

© 2007 Cisco Systems, Inc. All rights reserved.

Procedure Net Audit

Step 4. From the Audit tab, click Device

© 2007 Cisco Systems, Inc. All rights reserved.

Step 5. Click Start Data Collection Now. The

Step 5. On the Data Collection Status page you