Visual Select Webinar TrainingSession 6: Network Configuration

Kirk O’Connortraining@visualnetworks.com

301 296 2300

2

Introduction

Welcome!

Kirk O’Connor301 296 2744training@visualnetworks.com

Office Headquarters:Visual Networks, Inc.2092 Gaither RoadRockville, MD 20901www.visualnetworks.com

For troubleshooting or questions related to this training, please contact: training@visualnetworks.com.

For troubleshooting or questions related to your Visual Select system, contact your Service Provider or Sales Representative.

3

Agenda

Housekeeping

System Overview

Network Configuration

System Demonstration

4

Housekeeping

Training webinars are one hour or less.

1. System Overview2. Getting Started3. Application Troubleshooting4. Network Troubleshooting5. Traffic Capture6. Network Configuration7. Planning and Reporting8. ASE Installation9. Network Configuration10. Managing the ASEs

Total Time: 10 hours

For troubleshooting or questions related to this training, please contact: training@visualnetworks.com.

For troubleshooting or questions related to your Visual Select system, contact your Service Provider or Sales Representative.

5

Training Webinar Courses

1. System Overview: A demonstration of all the Tools.

2. Getting Started: Logging in, Service Summary, Events, Performance Monitoring. (1 hour)

3. Application Troubleshooting: Using the Application Integrity toolset including Application Summary and Application Flows. (1 hour)

4. Network Troubleshooting: Using the Troubleshooting Toolset on the Physical and Port views of the Local Loop and end-to-end SLAs on the Circuit. (1 hour)

5. Traffic Capture: Using the Traffic Capture Toolset for advanced level troubleshooting. (1 hour)

6

Training Webinar Courses

6. Network Configuration: Adding Networks, Sites, ASEs and Circuits to be monitored by the Server. (1 hour)

7. Planning and Reporting: Creating and analyzing Executive Reports and Site-Specific Reports for trending and problem analysis. (1 hour)

8. ASE Installation: Installing the ASE and commands. (1 hour)

9. Network Configuration: Adding, Networks, Sites, ASEs and Circuits to be monitored by the Server. (1 hour)

10. Managing the ASEs: Getting the data home. (1 hour)

7

Course Objectives

Network Configuration: Logging in, Service Summary, Events, Performance Monitoring.

By the end of the session, participants will be able to:

Log into the Platform Applicable Client.Navigate to a Customer.Use Network Configuration to Move, Add, Change, Delete a Network, Site, Access Line, and/or Circuit.Add Applications to be monitored.Add the Committed Access Rate (CAR) value.Add a Local Subnet for mapping to a Remote Subnet to create an IP Circuit.

Total Time: 1 hour

8

Visual UpTime Select – 2005 - 2006

Instrumentation SELECTSELECT

Visual UpTimeSelect Server

Third-Party Integration Interfaces

Software Modules

Service SummaryCore System Software

SelectAppSummary

SelectAppFlows

SelectTraffic Capture

SelectClass-of-Service

SelectNetwork Troubleshooting

SelectBack-in-Time

SELECTSELECT

Probe

SelectVoIP MRI

SELECTSELECT

ASE/DSU

SelectCitrix Intelligence

SelectEnhanced VoIP

SelectLAN/WLAN

Ethernet

SELECTSELECT

SelectRemote Control

SelectRouter Polling

9

The Visual System

Data Collection:Analysis Service Element

Data Collection:Analysis Service Element

“ASE”“ASE”

Data Interpretation:Performance Archive Manager

Data Interpretation:Performance Archive Manager

Select ServerSelect Server

Data Presentation:Platform Applicable ClientsData Presentation:

Platform Applicable Clients

“PAC” or Web Client“PAC” or Web Client

SQL

SQL

SQL

SNMP/TFTP

Servers come in two sizesSingle Processor: 1,000 ASEs or 1-15 Domains or 5,000 objects*Dual Processor: 8,000 ASEs or 1-250 Domains or 28,000 objects*Objects are the total number of ASEs, partner devices, and defined VPI/VCI’s or IP circuits supported on the server.

Events, Real Time and 48 hours worth of data in 1 second granularity

1 years’ worth of data via Planning and Reporting Toolset

Traps, Real Time View, 2 weeks “back in time” data plus 1 year

of Reports

10SELECTSELECT

T1

T1 WIC

56k

T1

DS3

Remote Locations Headquarters

Data Center

Management Data

Customer Web-Based GUI

Deployment Model

SELECTSELECT

SELECTSELECT

Operations Center

SELECTSELECT

SELECTSELECT

SELECTSELECT

SELECTSELECT

WAN

PAC Tool for NOC

SELECTSELECT

Mgmt PVC for Nightly Data Collection

SELECTSELECT Ethernet LAN based ASE

*Images

Best Practice: Probe at every location.

11

System Communication

Service Providers use multiple servers that point to a single Web server.A back up server can be deployed as well.

12

SelectServer

RPCPAC initiated transfer of

database information

UDPUnacknowledged

status notifications: new events, data

collection progress

NOTE: Arrows indicate direction of information transfer.

SNMP SETModify ASE configuration

VIA the Select Server

SNMP GET/GETNEXTPAC initiated retrieval of real-time

stats and configurationVIA the Select Server

TFTP PUTPAC initiated transfer

of a new software image to the ASE

VIA the Select Server

SNMP TRAPSUnacknowledged

exception reports. The only ASE initiated communications.

TFTP GETPAM initiated bulk

transfer of historical statistics

SNMP GET/GETNEXTPAM initiated transfer of

lost traps (events)

Visual APITCP/IP based access to configuration, historical statistics, and events

ASEPAC

P&R APIPAC initiated Report

generation control and data

Visual Communication

Firewall ports will need to be

configured correctly.

13

ASE memory(2 days of data)

long-term database(n weeks of data)

short-term database(14 days of data)

PAMnetwork performance

database

daily ASE data collection

daily databasemaintenance default:

daily at 2 a.m.

default:daily at 1 a.m.

Data Movement

One Second Granularity in 15 minutes buckets, or 900 seconds for a total of 192 buckets.

Data really collected nightly (1x) each night because of the nightly

collection.Removes unnecessary polling.

1 years’ worth of data

Data is organized as follows: Domain = Customer Network Network Site Access Line = Port = ASE Circuits

PVC IP HDLC ATM

Application Summary Data (4 weeks of AppFlows)**

**Application Alarms are generated nightly during the Daily Database Maintenance.

SNMP Traps in Real Time

or by hourly or On-Demand

Or On-Demand

Select Server

14

Service Summary Polling

PAMWebClient

NetworkPerformance

Database

ServiceSummary

poller ASE

ServiceSummary

middleware

Pollsevery #minutes

ASE

events

WebServer

15 min.

Refreshesevery #minutes

Service Summary data includes:•Updates of layer 2 up/down status on ASE-monitored ports polled from ASEs every 15 minutes and circuit up/down status polled every hour.•Port history (link up/down status) stored in 1-hour intervals for the most recent three days.•The five most recent port and circuit events uploaded by ASEs, updated every 15 minutes or when you refresh the Port and Circuit Details page in Service Summary. An ASE uploads recorded events as they occur to the Service Summary process in the Visual UpTime Select server and to the network performance database. To view all events for the previous two weeks, use the PAC Event Processor.

On the Visual UpTime Select server, the Service Summary process polls ASEs for status data every 15 minutes (this setting can be changed in Server Administration on the server). A Service Summary middleware component in the server requests updates from the poller every 15 minutes and interfaces with the Web Server to make detected ASE status changes available to Web Clients.

Server polls ASE every 15 minutes (default) for up/down status. Useful for HARD OUTAGES or cuts on the circuit.Web Client automatically refreshes, globally, every 300 seconds (default), or a manually with the REFRESH button.

Select Server

15

Network Configuration Requirements

User must have the Platform Applicable Client (PAC) loaded on their PC or access via Remote Terminal Services.

User must have connectivity from the PAC to the Select Server. Note: Firewall configuration for PAC <-> Server communication necessary.

User must have Network Configuration user access on the Domain, i.e. Customer.

The ASE probe must be installed at the customer’s premise.

The Select Server must have connectivity to the ASE probe.Note: Firewall configuration for ASE <-> Server communication necessary.

Proper licensing must be deployed on the Server (or the Domain) in order for the ASE probe to be added for monitoring.

DOMAIN: A logical partitioning of all networks configured on a Visual UpTime Select server. A user can have access to more than one domain, and a domain can be accessed by multiple users. The Visual UpTime Select administrator configures which toolsets and functions a given user can access by domain.

16

Decisions to be made: *The only fun part

The Customer Data is segmented by the following:SERVER: (the highest level, encompasses the server and all the Domains/Customers within the Server)DOMAIN: This is typically the Customers’ Name.

example: GlobalFinacials

NETWORK: This can be a single Network or multiple Networksexample: GlobalFinacials

Or

example: Asia Network, US Network, South America Network, Europe Network

SITES: This can be the Physical Location of the ASE, or LEC Circuit ID.

example: Rockville MD

ACCESS LINES: This is also equal to PORT. The actual IP Address of the ASE is provisioned here.CIRCUITS: Mapping of two ASEs to each other to create an IP Circuit, PVC, HDLC, or ATM circuit.

17

Example and Notes

Server: 192.168.236.46

Domain:

GlobalFinancials

Network:

Global Financials

Site:

Rockville MD

Access Line:

RTR123CKTid

Circuit:

RockvilleMD<->EverettWA

NOTES:•User Access is controlled at the Domain Level, not the Network.•WAN Planning and Reporting has the option to generate Reports on ‘All Networks’, or specific Networks like ‘ASIA Network’ or ‘US Network’.•Sites can have more than one ASE, in the case of multiple Access Lines.•Access Lines is where the ASE IP address lives. •Circuits must be mapped correctly and MACD’ed if changed in reality on the network.

18

PAC: Log in

1. Navigate to: START Program Visual Networks Visual UpTime Select Client PAC

3. Name* Server and input IP address:

4. Highlight Server and click CLOSE:

5. Login with provided User name and Password:

2. Click ADD

Successful PAC attempts to contact server.

*Any name will work. It is local to the Client.

*Steps 1-4 will be skipped next time you log in.

19

To switch customers: 4 clicks

*Once log in’ed it is very easy to change customers for a MACD within the Network Configuration toolset.

A. Login Setup Domain Selection

B. All Servers and Domains that the USER has access to is populated in the Domain Selection screen.

12

3.

4.

20

Network Configuration

1. Click Network Configuration

2. Click Add Networks

3. Click Add Sites4. Click Access

Lines = Port = ASE: more work needed

5. Click Auto Add must be correct

6. Click Close

1.

2.

3. 4. See next screen

5. See Creating IP Circuits

6.

Best Practice: Print...to file and save the Domain Configuration for backup.

21

Add Access Line = Port = ASE

1. Add the Access Line Name2. Decide on Data Collection3. Add the LAN IP or INBAND IP

address of the ASE.4. Click ASE Setup*

*This will cause the Select Server to contact the ASE to confirm communication and license for monitoring.

*Best Practice: Fat fingering the IP address of the ASE will cause failure, as will, no IP route between ASE and Select Server, as will, the wrong SNMP Community string in the CLI of the ASE.

*Best Practice: Collect Data more often than once a day for locations with known power outages or generators.

1.

3.

2. 4.

Best Practice#1: Set the Data Collection to the ASE Local Time based upon the Server Time.Best Practice#2: If ASE is not installed or down, make the ASE Active checkbox inactive (grey).

*Always, Always do a Data Collection prior to rebooting or updating an ASE.

22

ASE Configuration

IP...: Lots’ of Action Here

Frame Relay...: hmm, interestingT1 Interface...: DO NOT MESS

WITH. *This is the T1 command on the ASE. Not applicable on probes.

________________________________________________

Software Version:

IP Transport ASE = MPLS IP VPN Networks

Multi-Protocol ASE = Traditional Frame, ATM, HDLC Networks

Same Hardware, different Firmware

Buttons depends on the type of ASE

T1 Interface The most dangerous button

The ID command on the ASE

* Do Data Collection first, requires a reboot.

= Same as Serial #= Good info

or Multi-Protocol

Best Practice: Always confirm the latest Software Version during installation by checking Visual Customer Care (VTAC).

or Multi-Protocol

23

T1 Interface

The PAC ASE Setup T1 button allows for editing the CSU/DSU configurations.

Best Practice: On circuit upgrades, change the CSU/DSU via command or PAC prior to upgrading the circuit. Communication will be lost with the ASE until the circuit is upgraded and the CSU/DSU becomes synchronized.

The T1 Command on the ASE is used to configure the CSU/DSU.

This information is provided by the local Telco and must match in order to work, otherwise truck roll.

NOTE: Any T1 Command Line or PAC changes are instantaneous. Double check.

=

24

Frame Relay

Frame length > than 4096 can be viewed under PORT STATISTICS

Enscapulation Protocols are for those tricky moments

Link Management is standard LMI between the CER and the PER.

25

IP...Applications

Top 10 Applications will be rotated every 7 days unless LOCKED.

Use LOCK for your favorite protocols.

Auto Select should be used initially for every install.

Very cool feature: Auto discovery and monitoring of the top 10 Protocols for the week.

26

IP...Subnets

Subnet Guidance List is a “suggested discovered subnets” that the ASE automatically discovers.

If BGP is being used, the Local Subnet List will be automatically populated.

The subnets related to the Customers Routers Serial interface should be used.

Customize your local subnets

THE LOCAL SUBNET LIST MUST BE CORRECT IN ORDER TO MAP AN IP CIRCUIT AND GAIN PROPER COS SLA METRICS.

These Local Subnets will be mapped to another Remote Local Subnet to create an IP CIRCUIT.

27

IP...Class of Service

The CoS Configurations default configuration is set on the Select Server for each Domain.Getting it right in the Select Server will get it right on every ASE.Each field is configurable on the server.Only Policing Threshold settings for each CoS is configurable here.

Reminder: All traffic is “tagged” in the ToS on the Customer Edge Router, the ASE is only “monitoring” the ToS field.

If the Web Client shows “Unknown” then the CER is typically mis-configured because all traffic is tagged as “best effort.” Up to 8 CoS settings can be configured.

Jitter on CoS only available once.

28

IP...Committed Access Rate (CAR)

CAR values are represented at the PORT BURST tab.

In some ASEs, like the Ethernet ASE, the CAR value is also used in the PORT Summary tab for PORT Utilization graphing and reporting.

This value is only used for calculations and reporting.

This values does NOT affect traffic.

Setting to ‘zero’ will default to ASE Port Speed.

The GREAT DEBATE: In some cases, CAR = PORT speed, in other cases CAR = the value “guaranteed” by the Service Provider on the Local Loop. Also known as the “policed value” as related to the Port NOT CoS.

29

IP...IP Circuit Clean Up

IP Circuit Clean Up: an easy way to delete non-functional, or mis-configured IP Subnet to IP Subnet mapping.

30

Creating IP Circuits

AUTO ADD SHOULD NOT BE USED ON REMOTE SITES and only on LIMITED HUB SITESThis creates a fully meshed environment that may not be accurate with the routing statements.BE VERY CAUTIOUS HERE.

31

IP Circuit Properties

This screen is useful when BGP is running on the network. If you see red, check the square and close. Click “OK”, close, and re-open.

IF BGP is not running, much more consideration needs to takes place in creating an IP Circuit.

Best Practice: Use the ADD button in the Circuit Network Configuration to make an educated IP Circuit; mapping proper subnet to subnets

32

PAC: Identify ASE

IP Class of Service settings are configured on the Customer Domain by the Server Administrator.

Identify ASE only available

on the PAC.

1. Log into PAC and go to: File > Identify ASE

2.

3.

4.

**By getting it right in one place, the ASE’s will track COS and thresholds for all Sites.**

33

PAC: System Management

1. Run Identify ASE… often, especially after upgrading an ASE, or the Select Server.

2. Run ASE Inventory… to better understand your connection status.

3. Run Collect Data Now…on individual sites, especially if Data Collection Poll Failure Event.

4. Search for DATA COLLECTION POLL FAILURES: Partial Data Collection in the Event Processor means mis-mapped circuits and are not good. Fix these ASAP in Network Configuration, or open a ticket. This effects SLA metrics.

Log into PAC and go to File…

*Best Practice:

34

Review:

Use the PAC to run Identify ASE and Data Collection to quickly assess the monitoring of your Visual Select system.

Search for Data Collection Poll Failures and fix these immediately on the Circuit in Network Configuration or by opening a ticket.

Sort the Events by Site or Priority for quick site analysis.

Use the Acknowledge Displayed to remove Events from the Event Processor and keep the Events manageable.

Use the context sensitive HELP system.

35

Introduction

Thank you! Any questions?

Kirk O’Connor301 296 2744training@visualnetworks.com

Office Headquarters:Visual Networks, Inc.2092 Gaither RoadRockville, MD 20901www.visualnetworks.com

For troubleshooting or questions related to this training, please contact: training@visualnetworks.com.

For troubleshooting or questions related to your Visual Select system, contact your Service Provider or Sales Representative.