Upload
networksguy
View
427
Download
1
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
2
Introduction
Welcome!
Kirk O’Connor301 296 [email protected]
Office Headquarters:Visual Networks, Inc.2092 Gaither RoadRockville, MD 20901www.visualnetworks.com
For troubleshooting or questions related to this training, please contact: [email protected].
For troubleshooting or questions related to your Visual Select system, contact your Service Provider or Sales Representative.
3
Agenda
Housekeeping
System Overview
Getting Started
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: [email protected].
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
Getting Started: Logging in, Service Summary, Events, Performance Monitoring.
By the end of the session, participants will be able to:
Log into the Web Client.Log into the Platform Applicable Client.Navigate to the selected Domain, Network, Site, Port, Circuit.View Administrative Events and Performance Threshold Events.Navigate the Event Processor.Create Statistical Threshold Events.Use Identify ASE, Data Collection, ASE Inventory, and Update ASE Software.
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
Web: Log InThe Web Client and PAC are supported on Windows Server 2003 (Service Pack 1), Windows XP Professional (Service Packs 2 and 1), and Windows 2000 Server and Professional (Service Pack 4).
1. Type the Server IP address in a supported Web browsers on Windows like Microsoft Internet Explorer 6.0 (Service Pack 1 with critical updates) and Netscape 7.2.
2. Install Sun Java Plug-in 1.5.0 (for Select 1.2) or 1.4.2_02 (from Select 1.1). Both are supported in Select 1.2.
3. Install Web Planning and Reporting Software for access to the Long Term Planning and Reporting Toolset via the Web Client.
4. Create a New Folder on your PC called Visual Networks/Select12/Manuals and Download Documentation. Be sure to download all the PDFs.
5. If you have Select Server <-> PAC communication with properly configured firewall ports, download and install the Platform Applicable Client (for Network Configuration, Traffic Capture, and creating custom performance threshold events).
6. Start Visual UpTime Select.
2
345
6
1 Type the Server IP Address in the web browser
16
Web: Log In
1. Sever IP address in browser.
2. Log in with the provided Username and Password.
17
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.
18
Web: Service Summary
Review: ASE devices collect data on 1 second granularity in 15 minute buckets for 48 hours. Each night the data is collected by the Select Server where it is stored for up to one year.Download the appropriate Java and P&R applet for the Web Client.For PAC access, make sure the appropriate firewalls are open in order for the PAC and Server to communicate.
Service Summary Details:All Hardware comes with the Service Summary view, if managed by a Select Server.Service Summary provides a Domain wide view of the HEALTH of your network.Service Summary provide a Site HEALTH analysis for every site.Events/Traps are a powerful way to pro-actively manage and tweak your network for maximum performance management.
19
Web: Service Summary
To Navigate:
1. Select a Domain, ex. Acme
2. Select a Network ex. Class of Service
3. Select a Site ex. Site 59 Austin
4. Select a Port ex. M49 T1 208.58
Status Legend: Explains the Health Indicators
Company URL: Optional Link to another website, like Intranet.
Service Summary: Access to Health of Network
Health leads to Events Red is bad. Green is Good. Orange are Performance Issues based on Priority.
Password Reset
Help: Context sensitive
Access to 1 years worth of Network data
Access to 4 weeks of comprehensive Application data
Access to 2 weeks worth of Network Troubleshooting
ASE Inventory
20
Web: Site Performance
Site Performance with three day view.
Traps sent in Real Time.
Service Summary polls ASE every 15 minutes (default) for Port Up Status.
Web Client refreshed every 300 seconds (default)
Domain > Network > Site > Port = ASE = Access Line
Circuits: 108 is mis-configured
Launches Troubleshooting at the Time and OSI Layer.
PORT & CIRCUIT Events:•UP/DOWN (last 5)•Custom % Thresholds (last 5)
21
Event Trap Details
Events come directly from the ASE in SNMP format to the Select Server in Real Time.
Events can be forwarded in “Plain English” to a 3rd Party Reporting tool, like HP OpenView, or What’s Up Gold from the Server in Real Time.
Events can be forwarded in SNMP OID format to a 3rd Party Reporting tool, like HP OpenView, or What’s Up Gold from the ASE directly.
Each Domain can support 11,000 Events.
The Platform Applicable Client can display 5,000 Events.
The Web displays the last 5 Port and the last 5 Circuit Events.
The number of Events supported are dependent on the ASE type.
1500 events for Visual v6.0 Multi-Protocol ATM ASE models
1000 events for Visual v1.1 and later ATM-based ASE models
512 events for Visual HSSI ASEs
64 events for other Visual frame relay-based ASEs
*Note: Pre-v1.1 IP Transport ASEs do not support statistical threshold events.
22
Available EventsAdministrative Events (4), incl. Power Outage Notification
Priority is set individually.
Physical Events (34 Total)
Up/Down (21): Priority is set at 255, the highest level, Red
% Thresholds (13): Priority should be individualized between 1-255.
Link (Port) Layer Events (17 Total)
Up/Down (10): Priority is set at 200, or, Maroon
% Thresholds (7): Priority should be individualized between 1-255
Circuit Layer Events (17 Total)
Up/Down (8): Priority is set at 175, or, Orange
% Thresholds (9): Priority should be individualized between 1-255
43 Up/Down Automatic Traps +29 Performance Thresholds Traps (customized) 72 Total Traps Available: L1-L7
Priorities are set on a DOMAIN Level by the Server Administrator. This effects the color on the Web Service Summary View.
Best Practice: Make sure Global Event Priorities are all different values, in order to easily sort on within the PAC.
23
Configuration of Custom Events
Steps to Configure Performance Thresholds1. Event Processor2. Select a Site3. Click Performance Monitoring4. Click Add an Event5. Select Layer Type of Event: Physical, Port,
or Circuit6. Select Line Side: To Network, From
Network7. Set Parameters Threshold8. Set Measurement Threshold9. !Change Priority!10. Click OK11. Repeat for different Events12. Repeat for different Sites
Best Practice: • Set Low Level Priority Events (0-50/Yellow)• Set Events during Installation (adds 30
seconds to install, but huge benefits)• Set Low Thresholds to generate Events,
then tweak to a better value
1 3
4 5
2
*Always change the priority
Select a site
6
7 9
8
10
24
Administrative Events(Recommended)
Priority
150
75
50
150
For System Maintenance, check for this Event Daily
Log into the ASE, type EVENT or LOG to see the IP Address attempting to contact with wrong SNMP.
25
Physical Layer Events= Priority 255
26
Physical Layer Events= Priority 255
Physical Layer Issues are typically Copper Related, Layer 1, configuration, or bad connections. To better monitor, Layer 1 use the Custom Performance Threshold Events.
27
Physical Layer: Custom Events
*Good Threshold Events for monitoring Physical Layer Local Loop Issues.
*
28
Physical: Performance Thresholds
Best Practice:Use the Planning and Reporting toolset to narrow down sites requiring Physical Layer Events.
New Executive Reports->Services Level Verification>Top Problem Physical Lines->Tabular (daily or monthly)
New Standard Reports->Access Line Performance (Network T1) or T1 Access Line Performance->Tabular (daily or monthly)
Note: Probes that sit behind the CPE Router or behind an NTU have limited Physical Layer Events.
*Always change the priority
29
Link (Port) Events: Priority 200
*
*Seen when LMIsolate is enabled: An ASE feature that provides emulation of link management messages in the absence of a router or when the end-user router is down. Provides 100% local loop Availability (not including hard cuts) and better MTTR metrics due to not having to do a Local Loop Test by the Telco. Faster time to resolution by identifying the CPE Router is the problem.
30
Link (Port) Layer Events: Priority 200
Link Layer Events
Link Layer Issues are typically Local Loop issues. To better monitor, Layer 2 use the Custom Performance Threshold Events.
31
Link (Port) Layer: Custom Events
Application Utilization and IP COS Utilization are very powerful traps.
32
Port: Performance Thresholds
Best Practice:Use the Planning and Reporting
toolset to narrow down sites requiring Port Layer Events.
New Executive Reports->Services Level Verification->Top Problem Access Channels->Tabular (daily or monthly)
and the
New Executive Reports->Capacity Planning-Most Active Channels and Most Over-utilized Access Channels (Tx or Rx)
Application Monitoring Events can be set here as well to generate an event such as:
Port Utilization by HTTP (or COS VOIP) to the network is xx.xx%, equal to or exceeding xx%.
*Always change the priority
33
Circuit Status Events: Priority 175
34
Circuit Status Events: Custom Events
*
* Round Trip Delay packet generated within every 15 minutes. Very powerful when combined with VOIP Class of Service. Set two thresholds, one at 100 ms with a priority of 199 and one at 120 ms with a priority of 201.
35
CKT: Performance Monitoring
Best Practice:
Use the New Executive Report-> Service Level Verification-> Service Level Report (monthly) to identify circuits requiring Events.
For IPT Circuits, use the New Standard Reports->End-to-End IP Circuit Round Trip Delay for each COS.
Or use Troubleshooting -> Circuit-> Service Advisor
*Always change the priority
RTD is very important for VOIP
36
Web: Service Summary
Review:All Hardware comes with the Service Summary view, if managed by a Select Server.
Service Summary provides a Domain wide view of the HEALTH of your network.
Events/Traps are a powerful way to pro-actively manage and tweak your network for maximum performance management.
Ask your System Administrator about creating custom performance thresholds Events.
Use the context sensitive HELP system.
37
PAC: Event Processor
#1 Question: I have no tools/buttons available. What’s up? Answer: 1*Click an Event or 2*Click the Cloud and select an Access Line.
CLICK an Event1*PAC and Web Client data is organized and navigated as follows:
Domain = Customer Network
Network
Site
Access Line = Port = ASE
Circuits
PVC, IP, HDLC, ATM
ACK: Acknowledges an Event and removes it from the Event Processor window display
**Click the Blinking color to make it stop. Indicates a new Event has arrived.**
2*
Used to Filter the Events by Network Elements and Priority Range
Server Name/Domain/Login 1* 2*
38
PAC: Event Processor NavigationThe PAC allows access to:
A: Network Configuration: Used to configure the Network, Site, Access Line, and Circuits, ASE Firmware Upgrades, Application choices.
B: Traffic Capture: Used for advanced troubleshooting, a full protocol analyzer on every site.
C: Performance Monitoring: Used to set Performance Thresholds on individual ASE’s.
**These toolsets are for NOC Operators and typically not provided to the End User of a Service Provider Managed Solution. They have not been webifi’ed yet.
*
These tools are not available on the web, yet…
AC
B
39
PAC: Event Processor Navigation
To configure performance threshold events at each site.
To clean out all Events.
*Best Practice: ACK ALL on Friday’s at 5 PM in order to see the latest events on Monday morning.
To Acknowledge ONLY the Events Displayed that are filtered
**Acknowledging Events effect all PAC users, but does not affect the Events within the Web browser.
Displayed Events: Shows the total number of Events for the whole Domain.
If over 5000, an (*) is Displayed. Use the Restrict Displayed Events…tool.
*Best Practice: 1. Customer calls with a problem at a SITE: Use the SELECT button to navigate to that individual SITE or SITES and note the latest EVENTS that have occurred.2. System Management: Use the Priority Range EDIT button and view the latest Daily Data Collection Poll Failure Events. (50 to 50)
Use this box to filter the Events quickly in order to View specific Events by Network, Site (s), and/or Priority Range.
40
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. Run Update ASE Software… individually or for the whole network (useful after a Server upgrade).*only with customer approval.
Log into PAC and go to File…
*Best Practice:
41
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.**
42
Web/PAC: ASE Inventory
IP Address > License class1. Log into Web2. Click Tools3. Click ASE Inventory4. Click Start5. Click Export6. Save to Desktop
1. Log into PAC2. File > ASE
Inventory3. Select Network4. Click Begin5. Click Save As6. Save to Desktop
**Web ASE Inventory can go across multiple Networks.**
ASE Up Since: Good to see which ASE has been up the longest…
Product ID = Serial Number: Good to see which ASEs will require a Hardware or Software upgrade. Right Click and immediately upgrade!
ASE Inventory available on the PAC & the Web.
43
PAC: Data Collection
Best Practice: Run Data Collection on sites that exhibit Data Collection Poll Failure Events in the Event Processor window. Event #50.
Best Practice: Prior to Troubleshooting a Site, do a Data Collection on the individual Site for faster screen response.
Best Practice: For Partially Succeeded Data Collection status, use the Network Configuration toolset (PAC) to confirm PVC and IP circuits are properly mapped between DLCI’s or IP Subnets.
1. Log into PAC and go to: File >Collect Data Now
4.
2.
3. Click a SITE or SELECT ALL
4.
Data Collection only available on the
PAC.
44
PAC: Update ASE Software
Best Practice:
Always do a DATA Collection FIRST before upgrading or rebooting an ASE.(The Select Server will transfer the Image to the ASE and the ASE will reboot.)
Best Practice:
Use the Identify ASE tool next and do a Data Collection after upgrading or rebooting an ASE.
1. Log into PAC and go to: File > Update ASE Software…
**It is not possible to schedule an upgrade.**
Update ASE Software only
available on the PAC.
45
Review:
Use the PAC to run Identify ASE and Data Collection to quickly assess the monitoring of your Visual Select system.Use the PAC to see all the Events for a Domain in one place.Sort the Events by Site or Priority for quick analysis.Use the Cloud as a button within the Event Processor.Use the Acknowledge Displayed to remove Events from the Event Processor and keep the Events manageable.Use the Web to navigate to a site for quick analysis.Review the Best Practices.Use the context sensitive HELP system.
46
Introduction
Thank you! Any questions?
Kirk O’Connor301 296 [email protected]
Office Headquarters:Visual Networks, Inc.2092 Gaither RoadRockville, MD 20901www.visualnetworks.com
For troubleshooting or questions related to this training, please contact: [email protected].
For troubleshooting or questions related to your Visual Select system, contact your Service Provider or Sales Representative.