vnes lab manual 8.0

of 35

Training

CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.

Table of Contents TROUBLESHOOTING INCORRECT LOGIN CREDENTIALS ............................. 2

RUNNING AN ADAPTER CHAIN ................................................................................ 8

DEVICE MIB CONFIGURATION IMPORT ............................................................. 13

LINK INFERENCE AND CONNECTION INFERENCE ......................................... 18

LINK INFERENCE AND CONNECTION INFERENCE ......................................... 18

IMPORTING TRAFFIC DATA ................................................................................... 24

CREATING GROUPS ................................................................................................... 28

USING OPNET ANALYSIS SOFTWARE .................................................................. 32

of 35

Training


Troubleshooting Incorrect Login Credentials Overview In this lab, you manually edit the Device and Platform Info File to correct password and login script errors. Objectives

• Edit a list of devices and the associated authentication information (Device and Platform Info) for use with VNES

• Let VNES try to connect to these devices and run “show” commands • Investigate any access problems and make the necessary corrections

Instructions

1. Open the VNES Web Interface a. Login Credentials: admin/opnet

2. Navigate to the Device Management tab 3. Click the import button and choose File Based Import Advanced

of 35

Training


This will prompt you for the location of the file 4. Select Import Local File 5. Browse to the location where your device info file is stored 6. Click Next 7. Leave the default import options and Click Finish 8. Click OK to confirm the import of your device entries.

Note the following:

How many devices are in the list? How many devices have a checkbox set in the Active column? What is the Latest CLI and SNMP status? What is the significance of this status? Are any columns that are blank?

of 35

Training


9. Click on the Save button before leaving the Devices tab. a. You will receive confirmation to save, click OK

10. Create a new adapter chain with Device Data Collection adapter only

of 35

Training


11. Ensure that only the Device Configuration File Import is Active

12. Run the newly created chain

of 35

Training


13. There may be a few devices that are reporting errors. Some of these errors are the

result of incorrect passwords or login scripts in your Device and Platform Info file

14. Correct any Password and Login Script Errors a. Ping the devices to ensure that there is IP connectivity b. If the device does not respond to ICMP requests, ignore that device for the

duration of class c. Use your Access List info to change the usernames, passwords and login scripts

where necessary d. Navigate to the Devices Tab and look at the ‘Active’ devices, select a device

that could not be reached by the adapter. Notice, these devices have a Red ‘X’ or a “?” in the Latest CLI Status column.

e. Right Click on one of these devices and choose Edit Selected

15. Edit the Login Info for these devices

of 35

Training


16. Troubleshooting Procedure: i. Telnet to the device of interest

ii. Using the information on your Access List, log in iii. Attempt to run a “show” command to ensure your login has

permission to do so iv. Set the username, password, and privileged password in the

Device and Platform Info to match the information you entered when you logged in

v. Ensure that the Vendor Type column in Device and Platform Info is correct. (Hint: In your telnet window, try a show version or read the text that appears when you first log in to verify that the vendor and OS are what you expect.)

vi. Ensure that steps you used to login are reflected in the Login Script for the device

vii. Example: If you entered a username, password, “en” to get to privileged mode and a privilege password you Login Script would be: User Pwd Priv Priv_Pwd

viii. Ask instructor for help if you get stuck

15. Once all errors have been fixed save your changes and run the Device Config File Collection adapter once more and verify that no errors appear

16. Return to the Device Management tab and ensure that there are green checks in the Latest CLI columns for all your active devices

17. Save your changes to the Devices Tab and Re-run the Device Data Collection Adapter and look for errors. You should have resolved the issues associated with the devices.

of 35

Training


Running an Adapter Chain Overview In this lab, you will setup a series of collection and import adapters that represent the most commonly used VNE configuration for a Sentinel implementation. Objectives

• Create a new default adapter chain consisting of the CLI collection and import adapters

• Run the adapter chain to populate the VNES database • Import most recent VNES topology in to SP Guru Network

Instructions

1. Go to the VNES Management Tab and Select Schedule Chains 2. Select “ My Chain” in the left pane 3. Add Network Data Import to your chain

of 35

Training


4. Investigate the properties of the Network Data Import Adapter

5. Please ensure that your adapter chain is configured correctly and Click OK to save it. You will receive confirmation to Save changes, click OK.

This configuration will daisy-chain the adapters together, so that when one adapter completes, the next one will begin a few seconds later. The Network Import Adapter should always run right after the Device Config File Collection adapter ran, so that the latest configs are imported into the database.

of 35

Training


6. Return to the Schedule Chains tab and highlight My Chain 7. Scroll to the bottom of the left pane and click on Run to start the adapter chain

now. Click OK to proceed.

8. Check for warnings when your adapter chain is complete. Choose one and

investigate the problem. These errors may indicate that one of the import adapters can not parse a file. Navigate to this file in Windows to see what it contains. The file will be in: <VNES temp directory>\ Collect\<command>\Archived

a. Example: c:\op_admin\tmp\vne\Collect\CDP\Archived 9. If you don’t know what some of these import properties do, do one or all of the

following: a. Read the collected output files. b. Search the VNES documentation for information about the adapters. c. Google the show command it parses.

of 35

Training


You can view the run count of each adapter under the Adapters tab.

10. Final STEP: Import the model so far into SP Guru a. Open SP Guru (Start Programs) (If you are prompted to confirm product

modules, Click OK. b. File / New / Project c. Name the project first_import and the scenario no_links d. Import from VNE Server e. Choose the localhost VNE Server or enter the IP address of the system where

your VNE server is running f. Check the box to Generate Import Log g. Click Import

of 35

Training


11. Try to answer the following questions: a. How many devices were imported? b. How many were skipped (not created)? c. Why are there no links?

of 35

Training


Device MIB Configuration Import Overview This lab uses SNMP credentials and the MIB Configuration Import adapter to augment the CLI collected data in the VNES database with MIB values. Objectives

• Run the Device Data Collection adapter with the Device MIB Configuration Import adapter set to active

• Explore the VNES database using the Network Browser • Use the Network Browser to visualize attribute values that have been populated

my multiple sources. Instructions

1. Go to your chain and change the Device MIB configuration Import property to true and save your changes. You will receive a confirmation warning, click OK to proceed.

of 35

Training


2. Run your adapter chain

3. We will now disable SNMP collection for the devices that were not successfully

collected with the Device MIB Collection Adapter.

a. Return to the Devices tab and look at the column called Latest SNMP status. b. Right Click on a device that has red ‘X’ in this column c. Choose Edit Selected and go to the General tab and uncheck MIB collection d. Repeat these steps for all that were unsuccessful

of 35

Training


4. Go to the Network Browser and see what information was brought in.

a. Click the toolbar button for Show Historical Data, Current Data Source, and Observed Values

of 35

Training


5. Expand the tree on the left and choose a device 6. Explore the attributes and values for that device. Drill into an interface and look at

those attributes.

of 35

Training


7. Generate an Interface Summary Report and a Software Version Summary Report a. Navigate to the Reports Tab in the VNES Web Interface b. Select Inventory from the Report Categiories drop-down c. Double-click on the relevant report name to generate the report d. Click on an export option after the report is generated

of 35

Training


Link Inference and Connection Inference Overview This lab uses the Link and Connection Inference adapter to establish connectivity between the devices we have already imported into VNES database. This is the final step in building out the fully connected topology. Objectives

• Import a new topology into SP Guru Network Planner • Run the Link and Connection Inference Adapter • Import a new topology and compare it to the previous scenario

Instructions

1. Import current topology to SP Guru Network Planner a. Open your project in SP Guru b. Navigate to Scenarios New Scenario c. Name your scenario After_MIB Import d. Choose to Import from VNE Server e. Accept the defaults and click Import

There are no links because we have not yet run the Link Inference Adapter! 2. Add the Link and Connection Inference adapter to your adapter chain

of 35

Training


3. Investigate the properties of the adapter but do not make any changes

a. Keep all the defaults. These work well in the “best-case” scenario. b. Run your new chain

4. Import new topology to SP Guru Network Planner

a. Open your project in SP Guru b. Navigate to Scenarios New Scenario c. Name your scenario After_Link_Inference d. Choose to Import from VNE Server e. Accept the defaults and click Import

of 35

Training


5. Explore your newly created network and compare the links created to the interface information collected in the database.

of 35

Training


6. Use the Connection Analyzer to investigate which engines were used to create a specific link.

a. In SP Guru Network Planner i. Select any link of interest and mouse over it to see the attached

devices and interfaces ii. Record the Device and Interface Names

of 35

Training


b. Return to the PC where VNES is running i. Open a command prompt

ii. Navigate to VNES Installation Directory 1. Example: cd C:\OPNET\VNE\8*

iii. Run the command vnes.bat ca

of 35

Training


c. In the resulting Connection Analyzer dialog box i. Select your devices and interfaces from the drop down selectors

ii. Click Analyze iii. Record the results

of 35

Training


Importing Traffic Data Overview This lab highlights the use VNES to import performance metrics from 3rd party data sources. Secondly, we use SP Guru Network Planner to visualize the traffic data imported by VNES. Objectives

• Create a new (secondary) adapter chain of two performance metric adapters • Import a new topology with traffic and visualize link loads

Instructions

1. Create a new adapter chain to collect performance metrics. a. Using the procedure outlined in the “Running an Adapter Chain” lab configure

a new adapter chain consisting of: i. Metrics Collection

ii. Network Data Import iii. Metric Maintenance Service Adapter

of 35

Training


b. Explore the Metric Collection adapter properties.

c. Run your new adapter chain

of 35

Training


2. Import new model into SP Guru a. Create a new scenario called with_traffic b. Import from VNES, but choose to Yes import Link Loads under the Traffic tab

of 35

Training


3. Visualize link loads a. From the View menu, choose to Visualize Link Usage Color by Link

Usage b. Click on the pull-down menu at the top-left. Choose to view Baseline Link

Loads rather than loads that come from Flow Analysis or DES. c. Click on the pull-down menu on the right. Choose to view peak utilization. d. Click OK e. Note that most links are now colored based on utilization values

of 35

Training


Creating Groups Overview This lab uses the Auto Group Adapter to separate devices in your VNE Server Database into logical groupings. Objectives

• Create at least one group using the auto group adapter • Import a single group into SP Guru Network Planner

Instructions

1. Examine the topologies created in previous labs a. Decide how you would partition this network into groups b. Determine whether you could use string matching or regular expressions to

define each group 2. Using the Auto Group Adapter, attempt to create one or two groups

of 35

Training


3. Save your new group

4. Preview the changes

5. If you are satisfied with the results, run the grouping adapter

of 35

Training


6. Import just one group into SP Guru a. Create a new scenario b. In the Import from VNE Server dialog box, change Nodes from All to Filter c. Click Edit... on the right and choose your group

d. Verify that just that group was imported

of 35

Training


7. If you named everything “project1” and “scenario2”, go back and give your project and scenarios more interesting names at this time, using the Scenarios / Manage Scenarios dialog box.

8. Save this project

Using OPNET Analysis Software Overview This lab uses the network model that we have created in the previous labs to generate analysis reports. You will first create a Model Completeness Report (MCR) during the import process. Secondly, you will run the Common Enterprise Rules NetDoctor report on your model Objectives

• Generate the MCR during import • Run NetDoctor using the Common Enterprise Rules template

Instructions

1. Return to the PC running SP Guru Network Planner a. Open your existing project if it is not already open b. Navigate to Scenarios New Scenario c. Name the scenario “Analysis Reports” d. Import from VNES as usual but be sure to check the box to generate the MCR

e. Browse the Network Model Summary of the report

2. Run NetDoctor using the default report template

a. Select the toolbar shortcut to Configure/Run NetDoctor

b. Select the Common Enterprise Rules template and click Run.

c. Explore the report

vnes lab manual 8.0

Documents