Download document 
1 / Engine

2 / Instrumentation : wide support of the Cisco NAM (*)
-
|
Alaloop measurement name
|
NAM measurement
|
|
Performance (ART)
NAM_ART_SUMMARY
NAM_ART
|
Response Time
Server Response Time
Server-Client Response Time
|
|
Workload and traffic indicators
NAM_APPS_INDIVIDUAL
NAM_APPS_GROUP
NAM_APPS_URLBASED NAM_APPS_TCP/UDP
NAM_HOSTS_NETWORK
NAM_CONV_HOSTS
|
pps
Individual Applications
Application Groups
URLs
TCP/UDP Port table
Hosts
Network Hosts
Conversations
Network Hosts
|
The support of Multi NAM and Multi Data_Sources allows a widespread usage.

Deploying WaaS devices target optimization & acceleration of traffics like Cifs, Notes, ...
It usually occurs after the implementation of a Cos Policy (Classes of Service) on the Wan, conveniently controlled by Alaloop portal.
The portal can also summarize the necessary information for managing a WaaS architecture :
1 / Mapping to optimize traffic (Data Source Netflow)
2 / Response time analysis (Data Source : WaE through NAM);
3/ Monitoring & alarms
4/ SLA reporting and planning
(*) Network Analysis Module
(**) Wide Area Application Services
3 / Monitoring


4 / Dashboards
Dashboards menu gives access to 4 types of dashboards accessible by tabs. It is dynamically generated over any period preset or personalized by interactive calendars.
-
Scoring : measurement score over the period based on thresholds (OK, Warning, Critical)
-
Values : Max/Min/Avg values over the period;
-
Graphs : measurement graph dashboards
-
Custom graphs : graphs with multi measures analysis and multi scales
Remind: information provided in dashboards may vary depending on selected display mode (Technical / Executive)

Scoring dashboard (Scoring or SLA)

Values dashboard

Graph dashboard
New options to sort graphs based on :
Custom graphs : check the improvements described page 3
- analysis graphs generally build through multiple measurements
(*) accessible only in "technical" display mode.


Advanced Search : custom dashboards generation by multi-criteria research
1 / Tool accessible in the navigation tree by simple click (expandable area)
2 / Multi-criteria selection based on :
- current view within the tree (AlaloopNet_Without_COS)
- key fields to identify a measurement
(Measurement / Target / Details / Agent)
- state scores of measurement over the period
(ex : measures in Warning state > 20%)
- values for the result types of a measurement (example: network response time higher than 1 second)




Important notices :
-
the search criteria may vary according to the active dashboard (scoring, values, graphs, custom graphs) and the dashboards display mode (Executive or Technical).
-
All text fields provide autocompletion.
5 / Investigation tools
Portals have 5 investigation tools (the references indicate the new features)
-
Measurement Graph : graph of the values (parameters) of a measurement (1)
-
State Graph : graph of the states of a measurement (2)
-
Values : values Min/Max/Avg of a measurement
-
Measurement details : dashboards of the measurement values (3)
-
State Logs : dashboards of the measurement states (3)
(1) Management of multiple scales in Y : allows to manage measurements with different units.
(2) Unknown state (measure not realized) in white in the legend.
(3) In the heading of the summaries, display of the maintenance periods if applicable.

6 / Custom Graph improvements
4 steps (the references indicate the new features)
-
selection of measurements/result types to be graphed ;
-
edition of the components of the graph (1) ;
-
-
generation of the graph (2).

(1) edition of the components of the graph
-
Curves association : normal / stacked
-
Selection of color : hexa code or colour chart
-
Style of curve : area or line
-
Y-Axis : automatic assignment of scales according to the measure units (% and time for example). Activation of several scales for a same unit in case of strong disparity of values (example: comparison of a network response time in milliseconds and an application response time in seconds)
(2) Graph : multi-measurements / multi-scales
7 / Maps : investigation tools access

-

Investigation tools available by click upon the measurement point : the tools inherit the 24 hours period defined in the title of the graph (see example below)
-
"Pop-up Graph" options
(overflight of the measurement point)
-
-
Selection of the result-type to graph.
-
Management of the maps

8 / Reporting
-
Taking into account in all computations
-
Optional appendix detailing the maintenance periods (SLA, States logs)
-
possible even if the data base is locked
-
correct management of the dates displayed in the run, and the dates taken into account for the generation
-
Empty dashboards : SLA or State empty logs are replaced by a message "no data to display"
-
homogeneous management of the dates with the execution
-
simplification of the report edition screen
-
simple reorganization of the edition screens of the SLA/State logs (options of sorting/ layout )
-
RTF export : cleaning of SLO appendices
9 / Netflow
Cross-analysis between aggregate data and raw data
-

Investigate button : "Drill down" feature for the analysis of the traffic peaks.
-
drilling area is grayed out (data available) ;
-
slider to select traffic peak (period limited to one hour) ;
-
View Flows : detailed flows dashboard over the selected period ;
-
View Tops : selection of the Top report over the selected period (example : Top pairs who generated the peak)







-
slider to select traffic peak
-
button TOP REPORTS : generation of reports on the results of a "Flow Search"
-
Top Pairs generation : the IP address (x.y.z.211) is mainly behind the pic.




Measurement details resulting from NAM
|
Performance
|
Result_Type
|
Display
|
|
NAM_ART_SUMMARY (Server)
|
|
|
|
Response Time is the amount of time it takes a server to send the initial response to a client request as seen by the NAM.
|
Response Time avg Response Time min Response Time max
|
NAM_ART_AVG_RT
NAM_ART_MIN_RT
NAM_ART_MAX_RT
|
|
Number of TCP bytes sent from a server
|
Server Bytes
|
NAM_ART_SERVER_BYTES
|
|
AD is the time it takes a server application (for example, a web server application) to respond to a request. AD is the time between the client request arriving at the server application and the first response being returned by the application.
|
Application Delay avg Application Delay min
Application Delay max
|
NAM_ART_AVG_AD
NAM_ART_MIN_AD
NAM_ART_MAX_AD
|
|
The network round trip (flight time) between a client and a server through the NAM switch or router. ND is equal to the sum of CND and SND. The network round trip (flight time) between a client and a server through the NAM switch or router. ND is equal to the sum of CND and SND. NAM measures the ND using TCP 3-way handshakes. If there are no new TCP connections made during the monitoring interval, this metric is not reported.
|
Network Delay avg Network Delay min Network Delay max
|
NAM_ART_AVG_ND
NAM_ART_MIN_ND
NAM_ART_MAX_ND
|
|
SND is the network round-trip time between a server and the NAM switch or router.
In WAAS monitoring, CND from a Server data source represents the network RTT between the server and its core WAE.
|
Server Network Delay avg Server Network Delay min
Server Network Delay max
|
NAM_ART_AVG_SND
NAM_ART_MIN_SND
NAM_ART_MAX_SND
|
|
TD is the total amount of time from the first packet of a client request until the client receives the first response packet from the application server. Total Delay (TD) is the sum of the Network Delay (ND) and the Application Delay (AD).
Use TD with care because it is not measured directly and mixes the response time metric (SRT) with the connection metric (CND).
|
Total Delay avg Total Delay min Total Delay max
|
NAM_ART_AVG_TD
NAM_ART_MIN_TD
NAM_ART_MAX_TD
|
|
Total amount of time from the first packet of a client request until the client receives the final response packet from the server. TTT is a key indicator for detecting application performance anomalies.
|
Total Transaction Time avg Total Transaction Time min Total Transaction Time max
|
NAM_ART_AVG_TTT
NAM_ART_MIN_TTT
NAM_ART_MAX_TTT
|
|
NAM_ART (Server - Client)
|
|
|
|
Number of TCP bytes sent from a client during the monitoring interval.
|
Client Bytes
|
NAM_ART_CLIENT_BYTES
|
|
CND is the network round trip time (or flight time) between a client and the NAM switch or router.
In WAAS monitoring, CND from a WAE client data source represents the network RTT between the client and its edge WAE, while CND from the WAE server data source represents the WAN RTT (between the edge and core WAEs).
|
Client Network Delay avg Client Network Delay min Client Network Delay max
|
NAM_ART_AVG_CND
NAM_ART_MIN_CND
NAM_ART_MAX_CND
|
|
Workload
|
Result_Type
|
Affichage
|
|
NAM_APPS_INDIVIDUAL
|
Packets / s
Bytes / s
|
NAM_PACKETS_RATE
NAM_BYTES_RATE,
|
|
NAM_APPS_GROUP
|
Packets / s
Bytes / s
|
NAM_PACKETS_RATE
NAM_BYTES_RATE,
|
|
NAM_APPS_URLBASED
|
Hits
|
NAM_HITS
|
|
NAM_APPS_TCP-UDP
|
in packets/s
out packets/s
in bytes/s
out bytes/s
|
NAM_PACKETS_IN_RATE
NAM_PACKETS_OUT_RATE
NAM_BYTES_IN_RATE
NAM_BYTES_OUT_RATE
|
|
NAM_HOSTS_NETWORK
|
in packets/s
out packets/s
in bytes/s
out bytes/s
non-unicast/s
|
NAM_PACKETS_IN_RATE
NAM_PACKETS_OUT_RATE
NAM_BYTES_IN_RATE
NAM_BYTES_OUT_RATE
NAM_NON_UNICAST_RATE
|
|
NAM_CONV_HOSTS
|
Packets / s
Bytes / s
|
NAM_PACKETS_RATE
NAM_BYTES_RATE
|
Page Up