Professional Documents
Culture Documents
User Manual
5.2
Contents
CONTENTS
INTRODUCTION ......................................................................... ..........
1. REVISIONS ......................................................................... ..........
2. LIST OF ASSOCIATED DOCUMENTS ............................... ..........
3. DOCUMENT ORGANIZATION ........................................... ..........
4. TERMS USED ..................................................................... ..........
1
1
2
2
3
1-1
1-1
1-1
1-4
1-5
1-5
1-7
1-8
1-11
1-12
1-12
1-13
1-13
1-14
1-14
1-15
1-16
1-17
1-19
1-23
2-1
2-1
2-4
2-4
2-4
2-5
2-12
2-13
2-18
2-21
2-21
2-21
2-22
2-29
2-30
2-35
2-38
2-38
2-39
2-40
2-40
2-41
2-41
2-42
2-52
2-53
2-54
2-55
2-55
June 2009
Ipanema Technologies
Contents
2-66
2-68
2-68
2-68
2-68
2-72
2-72
2-72
3-1
3-1
3-2
3-2
3-3
3-6
3-6
3-7
3-8
3-10
3-11
3-11
3-17
3-18
3-20
3-20
3-21
3-22
3-23
3-24
4-1
4-1
4-2
4-2
4-3
4-4
4-8
4-9
4-9
4-10
4-10
4-11
4-12
4-12
4-12
4-13
4-14
4-15
4-19
4-24
4-25
4-35
4-36
4-36
4-36
4-36
4-37
4-38
4-38
4-42
4-46
4-54
June 2009
Ipanema Technologies
ii
Ipanema System
iii
4-56
4-58
4-60
4-61
4-63
4-63
4-64
4-65
4-76
4-78
4-85
4-87
4-89
4-89
4-98
4-99
4-105
4-105
4-110
4-110
4-112
4-113
5-1
5-1
5-1
5-2
5-3
5-3
5-8
5-9
5-14
5-16
5-17
5-17
5-18
5-20
6-1
6-1
6-1
6-2
6-3
6-4
6-6
6-6
6-7
6-7
6-9
6-11
6-13
6-15
6-17
6-18
6-19
6-19
6-22
6-28
6-33
6-36
Ipanema Technologies
June 2009
Contents
June 2009
Ipanema Technologies
7-1
7-1
7-1
7-1
7-2
7-2
7-4
7-5
7-7
7-16
7-25
7-25
7-26
7-28
7-29
7-31
7-37
7-37
7-39
7-41
7-43
7-45
7-49
7-52
7-52
7-54
7-56
7-58
7-60
7-60
7-62
7-64
7-66
7-68
7-68
7-70
7-72
7-74
7-76
7-78
7-83
7-86
7-88
7-88
7-90
7-94
7-97
7-97
7-99
7-100
7-102
7-104
7-104
7-106
7-108
7-108
7-110
7-112
7-114
7-114
7-117
iv
Ipanema System
7-119
7-119
7-121
7-123
7-123
8-1
8-1
8-1
8-1
8-2
8-2
8-2
8-3
9-1
9-1
Ipanema Technologies
June 2009
INTRODUCTION
1. REVISIONS
Date of issue
Index
Chapter/
section
concerned
Subject
January 2001
All
Original
April 2001
All
September 2001
All
January 2002
All
March 2002
All
August 2002
All
October 2002
All
January 2003
Chapters 2,
3, 4 and 8
February 2003
Chapter 2
ip|reporter settings
April 2003
Chapter 2
About window
October 2003
All
July 2004
All
April 2005
All
November 2005
All
November 2005
Chapter 2
April 2006
All
August 2006
All
October 2006
Chapter 2
November 2006
Chapter 3
Alarming function
February 2007
All
November 2007
All
January 2008
Chapters 2
and 7
April 2008
All
July 2008
Chapters 2
and 3
June 2009
Ipanema Technologies
Ipanema System
October 2008
All
December 2008
All
January 2009
AA
Chapter 2
March 2009
AB
All
May 2009
AC
All
June 2009
AD
Chapters 2, 9
3. DOCUMENT ORGANIZATION
This document contains nine chapters:
Ipanema Technologies
June 2009
4. TERMS USED
Aggregated flow:
Applications Dictionary:
AQS:
ASL:
BDP:
Byte counting:
Congestion:
CoS:
Class of Service.
CPE:
Delay variation:
DSCP:
DstPort:
Destination Port.
Datagram:
D/J/L:
Delay/Jitter/Loss.
Domain of Measure or
Optimization:
Elementary observation:
Fragmentation:
GPS:
Goodput:
GUI:
HSRP:
ICMP:
June 2009
Ipanema Technologies
Ipanema System
IP:
Internet Protocol.
IP micro-flow:
IPDR:
IP Data Records.
ITP:
Jitter:
LAN:
LAN to LAN:
used for the measurement from the LAN port of the source
ip|engine to the LAN port of the destination ip|engine.
LTL:
Measure interface:
Measure ticket:
MOS:
MRE:
NAP:
OWD:
Packets:
Packet counting:
Packet loss:
PBR:
Point of measure:
QoS:
Quality of Service.
Quality Index:
Router:
Routing:
RTT:
SALSA:
SLA:
SNMP:
SrcPort:
Source port.
Ipanema Technologies
June 2009
SRT:
TCP:
Ticket Record:
TOS:
Type Of Service.
TOS Dictionary:
Traffic profile:
Transfer delay:
Throughput:
UDP:
UC:
User Class.
Vip:
Virtual ip|engine.
VoIP:
VPN:
VRF:
WAN:
WAN to WAN:
used for the measurement from the WAN port of the source
ip|engine to the WAN port of the destination ip|engine.
WFQ:
June 2009
Ipanema Technologies
1. 1. OVERVIEW
1. 1. 1. General
The Ipanema System enables IP networks Quality of Service (QoS) to be measured, optimized and
compressed. It measures data transfer characteristics between access points and, in particular,
real-time performance (throughput, transfer delay, delay variation (jitter), loss rate, round trip time,
server response time and TCP retransmission ratio) of this transfer. Improving the QoS is a question
of finding the best match between user needs and network performance and optimizing allocation of
available bandwidth at network level. To be suitable for configuring and monitoring SLAs, measures
are made at IP level (level 3) allowing a clear breakdown between the network and the information
system. The compression allows to compress data in some cases.
QoS measure and optimization service features:
Users specify high-level business objectives through User Classes. Customer traffic is classified
using a mix of the users applications and organization data. User Classes attributes include:
business criticality,
QoS performance objectives (nominal bandwidth per application session, delay, jitter, packets
loss, RTT, SRT and TCP retransmission ratio),
compression capability,
The users objectives are the only input to the system. There is no need to set low-level, network
and device specific policy rules.
The individual measures are grouped and analyzed according to multiple criteria (IP address,
subnet address, application, User Class, etc.).
The results are presented in the form of real-time graphs and archived with periodic aggregation
(hourly, daily, weekly, monthly). They are made available for subsequent processing or reference.
Specific QoS measure service features (ip|true):
multiple QoS measures: measures include number of packets and bytes transmitted and
received, number of sessions, transfer delay, jitter, loss, RTT, SRT and TCP retransmission
ratio,
highly-accurate: from 100 s to 1 ms according to the type of ip|engine used. This relies on
synchronization from the network (NTP) or GPS system,
precise: measures are made on the actual data packets and not on test packets,
exhaustive: all packets are measured,
independent: measures are made at the IP level, independently of operator network access
and core technology,
confidential: the contents of user packets are not, at any time, stored, saved or even transmitted
between the different system components,
complete: packets are measured LAN to LAN and WAN to WAN.
dynamic optimization, based on real-time measure of application demand and network capacity,
global bandwidth optimization, based on real-time detection of WAN access and End to End
(ingress and egress) congestion,
June 2009
Ipanema Technologies
1-1
Ipanema System
adaptive Policies management according to the QoS objectives and criticality of each
application,
IP packet marking (coloring) according to operator CoS, taking into account the QoS and
criticality objective of each application.
the ip|engine also handles the dynamic traffic conditioning according to adaptive policies. The
CPE only performs IP routing functions for network access.
dynamic selection of traffic path, according to User Class and WAN access configuration,
the ip|engine handles the dynamic traffic conditioning according to the destination of the flows.
ip|reporter:
This service provided by an optional module of ip|boss produces full technical metric reports and
User Class high level reports.
An InfoVista run time licence is embedded in the ip|reporter module; this run time provides all user
functions in local, remote or client/server mode or with an HTML interface with VistaPortalSE.
All tasks about creation, deletion of reports are automatically made by ip|boss. The configuration
and use are very easy.
ip|export:
This service, provided by an optional module of ip|reporter, allows the user to generate data
records about IP network QoS, in text format or CSV format in order to integrate the data in Excel
for example.
ip|export is designed for seamless inter operability between network measurement systems and
Business Support Services systems (including Billing systems).
smart|plan:
This service, provided by an optional module of ip|reporter, provides easy-to-use data for Capacity
Planning optimization. Using information gathered from Ipanemas ip|engines performance
measurement and optimization functions, then aggregated by the ip|boss central management
software, smart|plan generates very high added value data enabling a complete analysis for
each network access of the relationship between bandwidth (resource) and delivered service
level (results). Using this automatically generated data, it is immediately possible to identify if
the access link is under-provisioned or over-provisioned in regard of the expected service level
per applications business criticality. The data generated by the smart|plan module are available
throughout all the Ipanema System components. ip|boss makes them available through the
SNMP interface, ip|reporter uses them to generate the appropriate easy to use reports and
ip|export aggregates and exports them in text format for post-processing.
1-2
Ipanema Technologies
June 2009
Ipanema System
Security:
Ipanema System provides robust security features to protect the system against break-in and
hostility threats. Authentication mechanisms to access to system elements and between system
elements are used to protect the system against unauthorized access. Communication encryption
between system elements protects the system against sniffing of configuration information or
measure results exchanged between system elements.
June 2009
Ipanema Technologies
1-3
Ipanema System
1. 1. 2. System description
The system consists of the following elements:
ip|engines: these units measure real-time traffic and dynamically adapt the QoS management
rules. ip|engines are non-intrusive and are generally located at the interface between the
enterprise network (LAN) and the access router to the operator network (WAN). They have
high-quality synchronization thanks to a time server (e.g. NTP) or thanks to an external GPS
receiver. The ip|engine runs the ip|agent, modules are:
System architecture
1-4
Ipanema Technologies
June 2009
Ipanema System
1. 2. GENERAL PRINCIPLES
1. 2. 1. System deployment
ip|engines are positioned at the measure or optimization points. They are connected to the same
LAN as the access CPE.
A Domain is made up of a set of ip|engines that measure (ip|true), optimize (ip|fast, plus possibly
ip|coop), compress (ip|xcomp) and accelerate (ip|xtcp and ip|xapp) the network traffic and the
ip|boss software (the central software program), for configuration and exploitation of the Ipanema
System.
One Domain will be created by logical entity, using ip|uniboss client. ip|engines belonging to
the same Domain work together (measure, optimization, compression and acceleration), without
interacting with other ip|engines belonging to other Domains. Each Domain is managed by a
dedicated ip|boss instance.
To measure, optimize or accelerate flows on a site with no ip|engine, the user can configure (IP
address and alias) a virtual ip|engine in the configuration file, in the same way as for a real one.
To make it possible, physically existing ip|engines must be installed at the other ends of all flows to
be measured, optimized and accelerated. Unlike a physically existing ip|engine, a virtual ip|engine
does not measure one-way-delays, jitter and loss rates, and does not compress or decompress.
June 2009
Ipanema Technologies
1-5
Ipanema System
The local networks have an IP address range expressed in the form a.b.c.d and a prefix, the length
of which is expressed by /p.
For correct system operation:
1-6
Ipanema Technologies
June 2009
Ipanema System
1. 2. 2. Time synchronization
ip|engines synchronization on the Domain is used for Delay/Jitter/Loss measurement (and
measurement only: optimization, compression, etc., do not require synchronization).
There are two synchronization levels:
Time servers
can be either ip|engines (with or without GPS), ip|boss or External NTP servers,
must be delivering a consistent time between each other,
if an ip|engine is a Time Server, it will use its local ITP configuration (GPS, local or an
external source).
Synchronization servers
must be Domain ip|engines,
will not use their local reference (even if a GPS receiver is connected),
share their clocks with their peers (all other synchronization servers).
This feature allows GPS-less Domains, out of Domain synchronization and short term no time
function (a Domain can be disconnected from its time servers, thus making higher resiliency).
June 2009
Ipanema Technologies
1-7
Ipanema System
1-8
Ipanema Technologies
June 2009
Ipanema System
June 2009
Ipanema Technologies
1-9
Ipanema System
1-10
Ipanema Technologies
June 2009
Ipanema System
June 2009
Ipanema Technologies
1-11
Ipanema System
As the period of stability is short, policy settings need to change dynamically according to network
performance and users traffic variations.
1-12
automatically creates tunnels from the compressing sites to the decompressing sites (described
in ip|boss),
compresses the packets according to the owning User Class (as defined in ip|boss),
the tunnels still depend on the optimization feature.
Ipanema Technologies
June 2009
Ipanema System
The key idea is, for each connection, to proactively enslave the TCP source rate to the ip|fast
computed rate for this connection.
After the TCP connection to the Server (ports 445 and 139 are used), the NetBIOS Session
service is established (negotiation of a CIFS dialect, Username/Password, connection to the
resource - shared directory for instance).
File accesses are done within this NetBIOS session (open, read, write...; only ONE connection
from a Client to a Server for ALL file accesses).
All of this is using SMB messages within NetBIOS datagrams.
There is one SMB Response for each SMB Request (the next request is sent when the previous
response is received).
Deployment cases
CIFS Acceleration is a Client-side technology. So the typical deployment case uses ip|engines
installed near the CIFS clients, therefore mainly in branch offices.
CIFS acceleration and Compression
ip|xapp and ip|xcomp are compatible. It is possible to compress accelerated CIFS traffic, both
with RAM-based and Disk-based compressions, in one, the other or both directions:
This depends on the User Class CIFS is matching, and on the local and remote ip|engine
compression/decompression capacities.
June 2009
Ipanema Technologies
1-13
Ipanema System
network capacity,
network availability,
network performance.
Thanks to the smart planning feature, the Ipanema system allows the best usage of the network
capacity according to the performance objectives, by enabling the user to select a cost /
performance compromise based on application service levels.
1-14
Ipanema Technologies
June 2009
Ipanema System
Functional architecture
June 2009
Ipanema Technologies
1-15
Ipanema System
1. 2. 12. Monitoring
For the monitoring, the operations are performed by the:
ip|engine:
elementary observations,
correlation,
flow management.
ip|boss:
ip|engines configuration,
ip|engines alarm management,
monitoring,
analysis,
SNMP MIB update.
ip|uniboss:
Domains creation.
ip|reporter:
collection of SNMP data from ip|boss,
reports database management,
reports publishing.
1-16
Ipanema Technologies
June 2009
Ipanema System
ip|engine:
elementary observations,
correlation,
classification.
ip|boss:
ip|engines configuration,
ip|engines alarm management,
monitoring,
SNMP traps.
Measurement
Each IP packet observed by the ip|engines on their measure interface undergoes a series of
processing operations:
filtering of IP v4 packets,
classification and filtering of packets according to their type:
identification of the ip|engine associated with each packet. This ip|engine will subsequently
be responsible for correlating the different observations made on this packet - in practice this is
the "upstream" ip|engine (upstream with reference to the observed flow),
output of a measure ticket.
Tickets are grouped according to the corresponding ip|engine in compact Ticket Records. These
records are periodically sent to the ip|engine or stored locally if the ip|engine is itself associated
with the flow.
June 2009
Ipanema Technologies
1-17
Ipanema System
Measure traffic
The ip|engines send measure tickets to the correlator via the network.
The measure load generated by each ip|engine is approximately 2% of measured traffic for
datagrams with an average length of 300 bytes.
Datagram fragmentation
Transmitting large packets on the network can degrade the quality of service for applications,
particularly if access speed is low. IP protocol allows datagrams to be fragmented into several
packets (fragments). Fragmentation can be performed at different points, but is generally
performed:
Fragments are not reassembled on the network or in the router, but by the end station.
To keep measures consistent without making assumptions on whether and where fragmentation
occurred (before or after the first ip|engine), the system performs measures on the datagrams.
This choice enables the classification mechanisms to operate correctly, even though port numbers
of the TCP/UDP protocol are present only in the first fragment of a datagram.
This choice is also consistent with applications behavior. In all cases, the datagram user application
must wait for the datagram to be reassembled before being able to use the data it contains. It is
therefore reception of the last fragment that is important.
A datagram is considered to be lost as soon as one or more of its fragments is lost. In this case,
the datagram is not delivered to the transport layer by the destination terminal.
1. 2. 13. 2. Correlation
The correlation function, shared by all ip|engines, produces Correlation Records that contain
measures grouped by aggregated flows (classification level is determined by configuration).
Correlation Records are generated at regular intervals and collected by ip|boss Collector.
1. 2. 13. 3. Classification
The software enables flow measures to be classified according to the following criteria:
address: subnet address ranges at flow source and destination according to the User subnets
directory,
application: according to the Level 7 Application dictionary, allowing in most cases the user
application to be identified,
TOS: the "TOS" field of the IP header identifying the Type of Service according to the TOS
dictionary.
1. 2. 13. 4. Monitoring
The monitoring function enables the operator to get a real-time view of the performance and activity
of the observed traffic in the form of graphs.
1. 2. 13. 6. Analysis
Measures can undergo deferred analysis. Measures can be viewed in graph form.
1-18
Ipanema Technologies
June 2009
Ipanema System
to manage offer: for a given current network performance, an ip|engine will adapt
characteristics to achieve the best trade-off between QoS and goodput,
to manage demand: for a given current LAN to WAN traffic, LAN-to-LAN QoS and bandwidth
availability, an ip|engine will adapt the user traffic policy to share network capabilities among
the flows.
each ingress ip|engine periodically advises each egress ip|engine of data it estimates it will
have to send them - quantity (min, max), time and loss constraints and criticality,
each egress ip|engine computes a fair-sharing scheme of its egress bandwidth, taking into
account the above parameters. It sends information to all active ingress ip|engines on the
amount of data they are allowed to send.
One can see that this mechanism is quite similar to a reservation scheme with the following main
differences:
bandwidth allocation is performed starting from a statistic view of the end-to-end traffic. This
facilitates statistic multiplexing among flows and limits the computing load (it is no longer related
to the number of flows),
network elements between ip|engines are not involved in the allocation mechanisms.
Bs egress capabilities,
A, C and Ds currently estimated traffic demand (quantity, time and loss sensitivity, criticality).
June 2009
Ipanema Technologies
1-19
Ipanema System
As ingress capabilities,
As traffic demand to destinations B, C and D (quantity, time and loss sensitivity, criticality),
B, C and Ds currently estimated egress traffic authorization (see N-to-one control).
1-20
Ipanema Technologies
June 2009
Ipanema System
The features enhance the relevance of the goodput through provisioning of arbitration rules. The
total amount of information effectively transferred is equivalent, but the relative amount per User
Class is managed.
criticality of applications,
instantaneous bandwidth requirements,
current end-to-end quality of service and traffic capabilities.
June 2009
Ipanema Technologies
1-21
Ipanema System
physical ip|engines for central site and sites with meshed traffic,
virtual ip|engines for small branch offices and simple traffic pattern.
With ip|coop option, for each virtual ip|engine, a group of remote physical ip|engines cooperate
(Remote Coordination Group) to do what a local physical ip|engine would have done, namely:
This Remote Coordination Group is made of up to 8 physical ip|engines (on the 8 most active sites
with this unequipped site) and is automatically and dynamically configured by ip|boss.
Thus, the contribution of each virtual ip|engine can be precisely estimated so that congestion to
and from the remote site can be managed (as through a proxy).
Limitation for use of virtual ip|engines:
no Delay/Jitter/Loss measurement,
neither measure nor optimization take shadow traffic (traffic between sites equipped with a
virtual ip|engine) into account,
End to End (E2E) bandwidth tracking is less efficient and reactive,
no limitation of egress UDP traffic.
When ip|coop option is enabled, the number of virtual ip|engines is controlled by ip|boss and
defined in the license file delivered to the customer. Without this option, the number is unlimited.
1-22
Ipanema Technologies
June 2009
Ipanema System
1. 2. 15. Security
Ipanema System security features are based on SSL and SSH protocol usage, plus tools for key
generation and distribution.
Second level
The customer defines his own certificate. This is done centrally from ip|boss or from a
customers certificate generator. Certificate installation on ip|engines is handled from ip|boss
and does not require local access to the ip|engines.
Communications are secured. Unauthorized people will not be able to enter the system nor to
read and interpret configuration or measurement data.
Third level
The customer defines his own certificate AND a passphrase. This requires not only an ip|boss
certificate installation, but also to have local access to all ip|engines in order to setup the
passphrase configuration.
Communications are secured. Combination of certificate and local passphrase provides the
highest level of security.
June 2009
Ipanema Technologies
1-23
To install the Java Runtime Environment 1.5.0 (if needed), in ip|uniboss/ip|boss CD-ROM go
to win32\java directory and launch jre-1_5_0_15-windows-i586-p.exe. Follow the onscreen
instructions.
June 2009
Ipanema Technologies
2-1
Ipanema System
2-2
Ipanema Technologies
June 2009
Check if the JAVA_HOME variable is correctly defined in the System variables. If not,
click New (if the variable was not set) or Modify (if it was incorrectly set) in the System
variables and configure the JAVA_HOME environment variable (by default JAVA is installed
in C:\Program Files\Java\jre1.5.0_15).
June 2009
Ipanema Technologies
2-3
Ipanema System
2. 2. IP|UNIBOSS SOFTWARE
2. 2. 1. Specifications for ip|uniboss server
The software application runs on a server (or a workstation with enough power):
Please refer to the relevant Release note to check the minimum characteristics required.
2. 2. 2. ip|uniboss architecture
ip|uniboss runs in client/server mode. The server processes supervise the system. The client is
the Graphical User Interface (GUI).
The User can access the GUI of ip|uniboss with the ip|uniboss Java Client, which needs an
installation on his or her station, or with the ip|uniboss web Client via a web browser (Internet
Explorer or Mozilla Firefox). A CLI client is also available.
2-4
Ipanema Technologies
June 2009
manual
If the JDK installed is not in the right version, the following error message is
displayed during ip|uniboss installation:
June 2009
Ipanema Technologies
2-5
Ipanema System
Click Next, then indicate the directory of installation (C:\Program Files\salsa by default):
If the directory already exists, you are warned that existing files may be overwritten:
2-6
Ipanema Technologies
June 2009
ip|boss server can be installed at the same time and on the same station as
ip|uniboss server. Click both clickboxes if this is what you want to do.
June 2009
Ipanema Technologies
2-7
Ipanema System
2-8
Ipanema Technologies
June 2009
The setup process of ip|uniboss server has created and started 2 new services (3 if ip|boss
was installed at the same time):
SALSA ipuniboss Server: manages the start of the different processes,
SALSA Web Server: used by the previous service,
(and SALSA ipboss Server if ip|boss was installed at the same time).
June 2009
Ipanema Technologies
2-9
Ipanema System
2-10
Configure the recovery mode (Restart the Service in the three fields) for each service (select
a service, menu Action / Properties, tab Recovery):
The setup process of ip|uniboss server has created the following directory tree:
Ipanema Technologies
June 2009
June 2009
Ipanema Technologies
2-11
Ipanema System
ip|uniboss Services
Click on:
2-12
Ipanema Technologies
June 2009
To connect to ip|uniboss server with a web client, enter the following URL:
https://x.x.x.x/ipuniboss_portal (where x.x.x.x is the IP address of ip|uniboss server). For security
reasons, the use of HTTPS is mandatory.
If a security warning window opens, click Yes.
Connection window
The connection window has two fields:
June 2009
Ipanema Technologies
2-13
Ipanema System
Windows,
Solaris,
Linux.
It requires Java JRE 1.5.0.11. Refer to the JAVA section to install JRE if needed.
There must be no proxy installed:
2-14
check your web browser parameters (Tools / Internet Options / Connections / LAN
settings: click boxes must be blank (Windows));
check Java web start preferences
(C:\Program Files\Java\jre1.5.0_11\javaws\javaws.exe then File / Preferences /
General / Proxies: none (Windows)).
Launch your web browser (Internet Explorer / Mozilla / Netscape), and select the following URL:
https://x.x.x.x/ipuniboss_manager (where x.x.x.x is the IP address of ip|uniboss server; the
use of HTTPS is mandatory). A warning may tell you that the publisher is unknown; click Yes
to continue:
Ipanema Technologies
June 2009
In order to launch the installation of ip|uniboss java client, click on Start ip|uniboss rich client.
Warning messages may appear. Click Yes and Run to continue:
June 2009
Ipanema Technologies
2-15
Ipanema System
A Java message may warn you that the digital signature has been verified. Click Run to run the
application:
You are asked if you want to create shortcuts for ip|uniboss. Click Yes if you want to accept:
To launch the client complete the following fields in the Login window:
Server: IP address of ip|uniboss server
User name: administrator by default
Password: with administrator account the default password is admin
2-16
Ipanema Technologies
June 2009
To create Domains, you need a running license. Refer to the Section ip|uniboss license
file.
if ip|uniboss server is upgraded, the software upgrade of ip|uniboss Java client is
automatically handled by the Java Web Start Software when launching ip|uniboss Java
client.
June 2009
Ipanema Technologies
2-17
Ipanema System
2. 2. 6. Uninstall ip|uniboss
The uninstallation of ip|uniboss consists in uninstalling the ip|uniboss server program on the
server, and if installed on the server the ip|uniboss Java Client.
If ip|boss server is also installed on the station, you must also stop ip|boss service
(SALSA ipboss Server).
2-18
Ipanema Technologies
June 2009
After these steps, in order to remove ip|uniboss services in Windows, you have to
reboot the Windows server.
June 2009
Ipanema Technologies
2-19
Ipanema System
Launch Java web start Application manager from the desktop, from the menu Start / Programs
/ Java Web Start or from the directory C:\Program Files\Java\jre1.5.0_11\bin\javaws.exe.
Click on ip|uniboss application and select the menu Application / Uninstall Shortcuts in order
to delete the shortcut on the desktop:
Select the menu Application / Remove Application in order to uninstall ip|uniboss Java client:
If you want to uninstall Java on the server, select the menu Settings / Control Panel,
select Add / Remove programs and choose Java in the program list.
2-20
Ipanema Technologies
June 2009
2. 3. IP|BOSS SOFTWARE
2. 3. 1. Specifications for ip|boss server
The software application runs on a server (or a workstation with enough power):
Please refer to the relevant Release note to check the minimum characteristics required.
2. 3. 2. ip|boss architecture
ip|boss runs in client/server mode. The server processes supervise the system. The client is the
Graphical User Interface (GUI).
The User can access the GUI of ip|boss with the ip|boss Java Client, which needs an installation
on his or her station, or ip|boss web Client via a web browser (Internet Explorer or Mozilla Firefox).
A CLI client is also available.
ip|boss server manages the communications with the ip|engines: supervision, start, stop,
collect, SNMP interface, management of users requests (update for instance).
ip|boss client should be on a different station (on the same or on a different LAN). It allows to
modify the configuration: adds, deletions in the different dictionaries, start or stop order, display
of measurements in real-time, creation of Metaviews and reports.
ip|boss server can run on the same machine as ip|uniboss server.
ip|boss server is multi-access (max. 10 users), multi-profile in order to give some different rights
for each user (system administration, service activation, supervision, helpdesk, ....).
ip|boss architecture
June 2009
Ipanema Technologies
2-21
Ipanema System
manual
To install ip|boss server using the Command Line Interface, refer to the relevant
Technical Note (only the standard procedure is described here).
To install ip|boss server, you must be connected as an administrator on the server
(installation of services).
If the JDK installed is not in the right version, the following error message is
displayed during ip|boss installation:
2-22
Ipanema Technologies
June 2009
Click Next, then indicate the directory of installation (C:\Program Files\salsa by default):
If the directory already exists, you are warned that existing files may be overwritten:
June 2009
Ipanema Technologies
2-23
Ipanema System
ip|uniboss server can be installed at the same time and on the same station as
ip|boss server. Click both clickboxes if this is what you want to do.
2-24
Ipanema Technologies
June 2009
This window does not appear if ip|uniboss was installed on the station before.
The Domains location path will then be the one selected on ip|uniboss installation
(C:\Program files\salsa\uniboss\server by default).
June 2009
Ipanema Technologies
2-25
Ipanema System
The setup process of ip|boss server has created and started 1 new service (3 if ip|uniboss
was installed at the same time):
SALSA ipboss Server: manages the start of the different processes,
(and SALSA ipuniboss Server and SALSA Web Server if ip|uniboss was installed at
the same time).
2-26
Configure the recovery mode (Restart the Service in the three fields) for ip|boss service (for
the 3 services if ip|uniboss was installed at the same time): select a service, menu Action /
Properties, tab Recovery:
Ipanema Technologies
June 2009
The setup process of ip|boss server has created the following directory tree:
If ip|uniboss server was installed at the same time, the default directory tree is the following:
June 2009
Ipanema Technologies
2-27
Ipanema System
Domains
will
be
installed
in
Program
2-28
Ipanema Technologies
June 2009
ip|boss Service
Click on:
June 2009
Ipanema Technologies
2-29
Ipanema System
Launch Internet Explorer, and select the following URL: https://x.x.x.x/ipboss_portal (where x.x.x.x
is the IP address of ip|uniboss server ip|uniboss is the web portal for ip|boss; note that the
use of HTTPS is mandatory).
If a security warning window opens, click Yes.
2-30
Ipanema Technologies
June 2009
June 2009
Ipanema Technologies
2-31
Ipanema System
Windows,
Solaris,
Linux.
JRE 1.5.0_11 is required. Refer to the JAVA section to install JRE if needed.
There must be no proxy installed:
check your web browser parameters (Tools / Internet Options / Connections / LAN
settings: click boxes must be blank (Windows));
check Java web start preferences
(C:\Program Files\Java\j2re1.4.2_10\javaws\javaws.exe then File / Preferences /
General / Proxies: none (Windows)).
Launch your web browser (Internet Explorer / Mozilla / Netscape), and select the following
URL https://x.x.x.x/ipboss_manager (where x.x.x.x is the IP address of ip|uniboss server
ip|uniboss is an authentication and redirection server for ip|boss; the use of HTTPS is
mandatory).
2-32
Ipanema Technologies
June 2009
Click Yes in the Create shortcuts window in order to create desktop and start menu shortcuts:
To launch the client complete the following fields in the Login window:
Server: IP address of ip|uniboss server (ip|uniboss is an authentication and redirection
server for ip|boss).
User name: administrator by default.
Password: with administrator account the default password is admin.
June 2009
Ipanema Technologies
2-33
Ipanema System
2-34
Ipanema Technologies
June 2009
2. 3. 6. Uninstall ip|boss
The uninstallation of ip|boss consists in uninstalling the ip|boss server program on the server, and
if installed on the server the ip|boss Java Client.
manual
If ip|uniboss and ip|boss servers are installed on the station, the installation procedure
will uninstall both.
If ip|uniboss server is also installed on the station, you must also stop the 2
ip|uniboss services (SALSA ipuniboss Server and SALSA Web Server).
June 2009
Ipanema Technologies
2-35
Ipanema System
After these steps, in order to remove ip|boss service in Windows, you have to reboot
the Windows server.
2-36
Ipanema Technologies
June 2009
Launch Java web start Application manager from the desktop, from the menu Start / Programs
/ Java Web Start or from the directory C:\Program Files\Java\jre1.5.0_11\bin\javaws.exe.
Click on ip|boss application and select the menu Application / Uninstall Shortcuts in order
to delete the shortcut on the desktop:
Select the menu Application / Remove Application in order to uninstall ip|boss Java client:
If you want to uninstall Java on the server, select the menu Settings / Control Panel,
select Add / Remove programs and choose Java in the program list.
June 2009
Ipanema Technologies
2-37
Ipanema System
By clicking on the link (depending on your system), you will be asked to open or save a zip archive
named:
These zip archives have some files in common. It is possible to unzip them in the same directory.
Unzip the archive you need, depending on your system, and launch the executable file it contains:
2-38
Ipanema Technologies
June 2009
A message tells you when you are logged in to ip|boss CLI client.
The prompt turns to ipmcli@<Domain_name> (ip|boss client) or ipmunicli@<Domain_name>
(ip|uniboss client).
The CLI clients currently use no external settings whatsoever, no startup file, no registry. Just
download the binaries to some directory, unzip the archive and make sure to have that directory in
your PATH.
For Solaris you will also need to add that directory to your LD_LIBRARY_PATH. As an
alternative, you can create a launcher script like:
#!/bin/sh
IPMCLI_DIR=<some directory>
# Use absolute path here
LD_LIBRARY_PATH=$IPMCLI_DIR:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
$IPMCLI_DIR/ipm[uni]cli $*
Call that script ipm[uni]cli and put it into any directory that is in your PATH (usually
/usr/local/bin). Make sure you add execute permissions to that script for anyone who is
to use it.
June 2009
Ipanema Technologies
2-39
Ipanema System
2. 5. IP|REPORTER SOFTWARE
ip|reporter processes numerous high added value reports which leverage fully all the power of the
Ipanema System.
ip|reporter is powered by InfoVista.
It includes an embedded InfoVista runtime license which carries out all the user interface functions
locally, remotely in client/server mode, or through an HTML interface using VistaPortalSE
ip|reporter Web.
All the configuration tasks are carried out automatically by the ip|reporter module. Therefore, the
installation of the product is straightforward and its usage very simple.
Memory, processor and disk requirements vary according to how you use InfoVista software,
notably in terms of database size. Please refer to the relevant Release note to check them.
Always install ip|reporter server on a dedicated machine (in case of a small
configuration ip|boss and ip|reporter can be on the same machine).
2-40
Ipanema Technologies
June 2009
2. 5. 2. ip|reporter architecture
ip|reporter runs in client/server mode. The server processes (InfoVista) collect data from ip|boss
SNMP agent. The client (IVreport) is the GUI (graphical user interface) that allows to show the
reports.
The reports can also be visualized through a web client, using VistaPortal SEs web server (refer
to section ip|reporter web edition).
ip|reporter architecture
June 2009
Ipanema Technologies
2-41
Ipanema System
1. install InfoVista; if InfoVista is already installed, it is not mandatory to reinstall it if the version
is identical (see the build number and the instructions of the release note):
For an evaluation or demonstration period, use the EVAL key. This allows you to access the
server for a period of 30 days starting from your first connection to the server,
For an extended evaluation or an unlimited period, you need a license key provided by Ipanema
Technologies. Refer to the Obtaining License key section below.
If you are using an evaluation key, you are unable to connect to the InfoVista server
and to access the reports in the VistaView after the evaluation period. However, the
collected data are not lost and new data continue to be collected. You are able to access
the reports again after entering a valid server and VistaView license key.
2-42
Ipanema Technologies
June 2009
2. 5. 4. 1. Installation procedure
2. 5. 4. 1. 1. Prerequisites
Please note that to install InfoVista, you must have Administrator privileges because the installation
program installs Windows services.
The InfoVista server and client can be installed on systems running under Windows 2000 SP4
or higher and Windows 2003 SP1 or higher; additionally, the client can be installed on systems
running under Windows XP SP1 or higher.
For more information on Operating System requirements, refer to the Readme file. To open this
file, select Start/Programs/InfoVista/Readme/ InfoVista Readme.
2. 5. 4. 1. 2. Before installing
Before installing, and for optimal performance of InfoVista on a Windows server, it is important to
optimize your computer for applications and not for file sharing.
To optimize a Windows 2000 server for network applications:
first-time installation,
upgrade.
2. 5. 4. 1. 3. First-time installation
A first-time installation does the following:
2. 5. 4. 1. 3. 1. Procedure
Company Name
License key
if you have a license key, enter it here. If not, leave the evaluation key
EVAL, which allows you to use the software for 30 days
June 2009
Ipanema Technologies
2-43
Ipanema System
the Server Components and Client Components software packages are both selected for
installation by default. To install only one or the other, uncheck the box to the left of the item
you do not wish to install,
the Online Documentation component copies to disk the InfoVista core documentation in
PDF format. These files can be opened (with Acrobat Reader software) in IVreport using the
Help/Contents option or alternatively Start/Programs/InfoVista/Documentation.
the Perl Integration Toolkit component installs a Perl scripting-language extension, which allows
you to include InfoVista commands in Perl scripts.
2-44
Installation:
<installdir>\
This is the main directory. You can change it by clicking on the
Browse button in the Select Components window.
<installdir>\data\
This directory contains the manager.db file, responsible for
updating the InfoVista Information System model and the
collector.db file, which stores polled data.
Note: Upgrades of existing 3.2 installations do not allow database
directory changes.
Ipanema Technologies
June 2009
<installdir>\log\
InfoVista log files are installed in this directory.
To change the location of the Manager/Collector database files
or the log directory, modify the paths displayed in the Server
directories window.
Note: Upgrades of 3.0 do not propose a change in the log
directory.
InfoVista Online
Documentation:
<installdir>\doc\
Acrobat PDF-format documentation files are copied here.
The installation of Acrobat Reader is not proposed
during the installation process, but the software
is provided on the CD-ROM. You must install this
software to be able to read PDF-format documentation
files provided with InfoVista. To install Acrobat
Reader (version 5), execute:win32acr-505.exe from
CD-R:\infovista\redist\acrobat\win32
Manager Endpoint (Port): the IP port number used to access the InfoVista Manager. By default,
this value is automatically generated by InfoVista.
Collector Endpoint (Port): the IP port number used to access the InfoVista Collector. By
default, this value is automatically generated by InfoVista.
Browser Endpoint (Port): the IP port number used to access the InfoVista Browser. By default,
this value is automatically generated by InfoVista.
If there is a firewall between the InfoVista client-server systems, it is necessary to use
a fixed port number. Consult your firewall administrator to determine an available port
number and enter it here.
With InfoVista Server 3.2 and 4.0, you can connect to a server with a connection string
using the instance name in the case of a multi-server installation. See the InfoVista
Server Users Guide, Communicating with the server for additional information.
2. 5. 4. 1. 3. 7. ObjectStore settings
June 2009
Ipanema Technologies
2-45
Ipanema System
Click Yes to modify the PATH variable and continue with installation.
2-46
bin:
data:
ObjectStore databases
doc:
etc:
lib:
log:
mibs:
MIB files
migration:
sdk:
vviews:
the two automatically installed VistaView XML files (Core and Tuning)
Ipanema Technologies
June 2009
When going from InfoVista Server 3.2 to 4.0, there is no need for a migration of data. This is
an automatic upgrade that modifies the database schema, attributes, and model. It does not
impact the data.
See the InfoVista Server Users Guide or Ipanema Technical note (TN-010007510 how to
migrate from 4.3 to 5.1 version.pdf) for information about database migration.
Important recommendations
It is strongly recommended to make a backup of your databases before starting the installation
procedure. Refer to the "ObjectStore Management Guide" for details.
As the trap format has changed and more precisely the information provided (manager and
browser endpoints), it is mandatory to upload the new InfoVista Trap MIB in your trap receiver.
Following the upgrade, MIB variables corresponding to the old version of the InfoVista-Statistics
MIB are set to deprecated. They will not return any values. The old version of InfoVista Tuning
VistaView is not migrated and will not be available in the new manager.
June 2009
Ipanema Technologies
2-47
Ipanema System
name of the system running the InfoVista server. If the server is the
local system (the same system as the client), leave this parameter blank
User name
administrator
Password
You can connect to a server with a connection string using the instance name. See
the InfoVista Server Users Guide, Communicating with the server for additional
information.
During a client connection attempt, the server license key is checked against the all
known MAC address on a NIC (Network Interface Card).
2-48
Ipanema Technologies
June 2009
2. 5. 4. 1. 6. Installing VistaViews
This is the second step in installing / upgrading ip|reporter.
To install the Ipanema Technologies Vistaviews, you must use the graphical client InfoVista
IVreport:
(To read more information on the short and long reporting periods, refer to 3.6.1 Create a
Domain.)
Click on Install button.
Close.
2. 5. 4. 1. 7. Uninstalling VistaViews
When VistaViews are installed, InfoVista creates a library with the same name. To uninstall the
VistaView, delete the associated library as follows.
2. 5. 4. 1. 8. Upgrading VistaViews
To upgrade the Ipanema Technologies Vistaview, you must load them with IVreport.
(To read more information on the short and long reporting periods, refer to 3.6.1 Create a
Domain.)
Click on the Install button.
Close.
The new versions of VistaViews are NOT automatically updated. To avoid holes in report graphs
at critical times, we recommended you perform the upgrade in off-peak hours.
June 2009
Ipanema Technologies
2-49
Ipanema System
2. 5. 4. 1. 9. Troubleshooting
2. 5. 4. 1. 9. 1. Windows services
The installation program sets the following Windows services to Automatic:
They are started automatically at system startup. After installation, if the services are not running,
start them manually.
After an upgrade, services are set to the status (stopped, started) and to the same startup type
(manual, automatic, disabled).
If you experience server problems, check the status of these services. If any of these them have
been stopped, you should restart it:
2-50
Ipanema Technologies
June 2009
2. 5. 4. 2. Uninstallation procedure
Before uninstalling InfoVista, close ivreport and ivstatus if they are running.
June 2009
Ipanema Technologies
2-51
Ipanema System
Regular backups of your database limits the quantity of data loss in the eventuality of hardware,
software, or human failures.
You can automate backups using the following tools:
InfoVista Server 4.0 provides backup tools to facilitate the backup of a database (however
voluminous) if that should become necessary or inevitable.
The backup tools work at the file system level. They use a point-in-time technology based on file
system technologies provided by Microsoft (Volume Shadow Copy), Sun (fssnap, delivered with
Solaris 9 and 10) and Veritas (fsckptadm, delivered with Veritas Storage Foundation Enterprise).
These technologies enable the performance of a point-in-time copy of data with minimal impact on
application. Basically it performs a snapshot of a partition in a few minutes. During that time, the
InfoVista server must maintain the databases consistent (i.e. no write operations performed).
The advantage of these backup tools are:
No report outages
Reports always available for viewing
To use the backup tools, it is mandatory that the manager and collector databases of an InfoVista
server instance are stored on the same partition.
Backup procedure overview
The following section gives a general guideline by which to proceed when performing a backup.
See the section addressing your specific platform for precise details.
Prerequisites
The new InfoVista backup tool uses the Volume Shadow Copy technology provided with Windows
2003. For older version of Windows, the only solution is to perform backup using osbackup.
Usage
When an InfoVista Server is started, it registers the manager and collector database as VSS aware
with the Volume Shadow Copy Service.
Following this startup, you can use NTBackup to perform the backup of InfoVista databases.
Simply create your NTBackup task and schedule it.
With InfoVista registered with the Volume Shadow Copy Service, when you start a backup,
InfoVista automatically performs a checkpoint of the corresponding server. It automatically
performs a checkpoint when the snapshot is complete, before it releases the server checkpoint.
In addition to NTBackup, you can also use any other backup tool that supports Volume Shadow
Copy technology to back up your InfoVista databases.
2-52
Ipanema Technologies
June 2009
Windows:
Solaris:
Step 2) Answer Ipanema Technologies Supports email containing your ip|boss license and
indicate the MAC address in your answer (support@ipanematech.com).
Step 3) Ipanema Technologies generates and sends you the license key(s)
If you are requesting an unlimited key or you are moving or upgrading an existing unlimited
license, Ipanema Technologies generates and sends you the permanent key(s), which you
must enter in the software as described below.
It is possible to install the InfoVista software prior to obtaining the definitive license
key, using the 30-day evaluation EVAL key.
Solaris:
June 2009
Ipanema Technologies
2-53
Ipanema System
2. 5. 7. Reports templates
To finish the installation of ip|reporter, it is necessary to copy the description file of reports
templates on ip|boss server.
2-54
Ipanema Technologies
June 2009
InfoVista VistaPortal Standard Edition is the web interface for viewing InfoVista reports.
The purpose of this chapter is to Install the VistaPortal SE version 4.0 SP1 on a Windows server
after uninstallation of the version 2.2, or just install the version 4.0.
To install VistaPortal SE server on Solaris, refer to the installation manual
IPANEMA-IRPWEB-INSTALL-V[x].PDF (IRPWEB stands for ip|reporter web).
Windows 2000 Advanced Server SP4 or higher or Windows 2003 server SP1 or higher.
Minimum Processor frequency: 900 MHz.
Minimum RAM: 512 MB (2 GB minimum in production).
Minimum disk storage space: 1 GB.
The following elements are required on Windows and must be installed separately:
InfoVista 3.1 SP1 (or up to InfoVista 4.0 SP1) software. The InfoVista server software can be
installed anywhere on your network. The InfoVista client software does not have to be installed
on the same machine as VistaPortal SE. To be fully functional InfoVista 4.0 is required.
DirectX 9.0c End-User Runtime
Microsoft GDI+ Detection Tool (KB873374)
These components can be downloaded directly from the Microsoft Website or via Windows Update.
Please consult http://search.microsoft.com/.
Optimize your computer for applications
For optimal performance of VistaPortal on Windows Server versions, you must ensure that your
computer is optimized for applications and not for file sharing (by default).
Use the dialog: Start/Settings/Control Panel/Network/Local Area Connection.
June 2009
Ipanema Technologies
2-55
Ipanema System
2. 6. 1. 2. Installation Procedure
Before Installing:
2. 6. 1. 3. Memory configuration
Recommended memory settings are proposed during the installation of the product. These
recommended settings depend on your servers memory.
You can however change values of Java server parameters after the installation in order to modify
the settings youve made at installation time.
This update shall also be made if youre adding memory to your VistaPortal SE Server. Note that
the maximum value supported by Java is 1024 MB on Windows server.
Offline Reporting
Change values of Java server parameters in the export script, as follows:
<NN>
512MB
256
1024MB
512
2048MB
1024
1. Open <installdir>/PortalSE/wrapper/wrapper.conf
2. Locate the lines
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=512
2-56
<NN>
512MB
256
1024MB
512
2048MB
1024
Ipanema Technologies
June 2009
Firefox 2.0
Sun Java Plug-in: version 1.5.0_11 or 1.6.0_01
VistaPortal SE will remain fully functional with more recent releases of these Web Browsers and
Java Plug-ins, as long as no regressions or important changes are introduced by such releases.
However, until intensive testing has been carried out on any new releases, they will remain
unsupported.
The Web Browser must be configured to:
Accept Cookies,
Enable Java and JavaScript,
Enable Popups from the VistaPortal SE website,
If you wish to view PDF-format reports, you must install the Adobe Acrobat Reader software
(Acrobat Reader version 6 or above), available in the /redist/adobe directory of the VistaPortal
CD-ROM. To display PDFs in the Browser, the "Display PDF in Browser" option in the PDF
preferences has to be checked. If not, the PDF files will be opened in a separate Acrobat Reader
window.
If you wish to view Excel exports, Excel 2003 or greater must be installed.
If VistaPortal Standard Edition is installed using HTTPS, the web browser must allow encrypted
pages to be saved on disk in order to be able to save Report Data Exports (PDF, Txt, ...):
Open the menu "Tools" / "Internet Options"
Open the the "Advanced" tab
In the section "Security", uncheck "Do not save encrypted pages to disk".
Under Windows 2003 server, the VistaPortal Standard Edition website needs to be added in
the "Trusted Sites" list:
June 2009
Ipanema Technologies
2-57
Ipanema System
On Windows 2003 Server, Internet Explorer is setup by default not to play animations. No
animated images in VistaPortal Standard Edition are displayed. In order to see animations,
Internet Explorer must be set up with the following option:
Open the menu "Tools" / "Internet Options"
In the Advanced tab, for the Multimedia section check the Play animations in web
pages option.
2. 6. 1. 5. VistaPortal SE URLs
Assuming you accepted the default site name PortalSE, the URL of VistaPortal SE is:
http://localhost/PortalSE.
In the rest of this document, the installation directory will be referred to as <installdir>.
If you choose another directory, replace <installdir> with the name of your installation directory in
the rest of this document.
application
in
2-58
Insert the CD-ROM ip|reporter Web v4.0 and run the setup.exe application in
InstData\windows\VM (normally auto-run launch it). The welcome screen appears.
Click Next. The License Agreement window appears. After you have read and agreed to the
license terms, Click I accept... and click Yes.
The Setup README FILE window appears. This file contains the latest release notes, which
we recommend that you read.
If needed, click the Open in Web browser button to direct the ReadMe to your favorite browser.
The information remains available in a separate window. Click Next.
The Select installation directory window appears to allow you to change the default installation
directory, if necessary. By default, VistaPortal is installed in C:\Program Files\InfoVista.
Click Next.
When the Install set window appears, check only Core components. Unclick the check box
Report samples. Click Next.
Ipanema Technologies
June 2009
The VistaPortal SE Site Name window appears. Enter the name of the portal that users will
access as a URL. Our example uses the default name <PortalSE>. Click Next.
The Memory settings window appears. Available memory is automatically detected and a value
is proposed for both the VistaPortal and VistaPortal SE servers (= half of the physical memory
of the VistaPortal server. Maximum is 1GB (on Solaris systems the maximum is 2 GB). The
memory proposed for VistaPortal SE is half of the memory defined for VistaPortal). Click Next.
If you are upgrading to newer version of VistaPortal SE you can keep the existing
memory settings, or set the maximum memory allocated to VistaPortal. We
recommend that you keep the existing memory settings.
June 2009
Ipanema Technologies
2-59
Ipanema System
Unclick the check box install InfoVista Cockpit Agent in the window that appears. Click Next.
The Pre-Installation Summary page appears with summarized information about the parameters
you have entered. Click Next.
The installation starts. A progress bar indicates the progress of the installation.
The installer completes the installation of VistaPortal and displays a summary and message
that you have successfully installed VistaPortal SE.
Click Done to exit the installation window.
2-60
Ipanema Technologies
June 2009
After this section, add the following line (note: in this example, VistaPortal was installed in
C:\Program Files\InfoVista\, which is noted ~):
--------------------------------------------------------------------------LoadModule jk_module "~/TomcatWebServerConnector/apache2.2/win32/mod_jk.so"
-------------------------------------------------------------------------- At the end of the configuration file, add the following lines (note: ~ stands for C:\Program
Files\InfoVista\):
--------------------------------------------------------------------------JkWorkersFile "~/TomcatWebServerConnector/conf/workers.properties"
JkMountFile
"~/TomcatWebServerConnector/conf/uriworkermap.properties"
JkLogFile
"~/TomcatWebServerConnector/logs/jk.log"
JkLogLevel emerg
JkShmFile
"~/TomcatWebServerConnector/logs/jk.shm"
-------------------------------------------------------------------------- Save the modifications.
Restart the Apache service.
June 2009
Ipanema Technologies
2-61
Ipanema System
Select your host name in the left-hand pane, then right-click and select All Tasks - > Restart IIS.
For more information on Tomcat connectors, please consult the documentation included in the
directory
/opt/InfoVista/TomcatWebServerConnector/doc
or
C:\Program Files\InfoVista\TomcatWebServerConnector\doc
2. 6. 1. 7. 5. Use of URLs
Assuming you accepted the default site name PortalSE, the URL of VistaPortal SE is:
http://localhost/PortalSE.
In the rest of this document, the installation directory will be referred to as <installdir>.
If you choose another directory, replace <installdir> with the name of your installation directory in
the rest of this document.
2. 6. 1. 8. Customizing
It is possible to set the Portal to ipanema colors, set the Online mode, add a help for the reports,
delete the unused buttons and modify some settings.
This customizing is done thanks to the ipreporterweb_setup.exe installer (provided on ip|reporter
web CD-ROM). Please refer to the Technical note How to Install VPSE for further details.
After this customizing has been set, open an Internet Explorer with the following URL to access
the Portal:
http://<@IPServerVPSE>/PortalSE
2-62
Ipanema Technologies
June 2009
June 2009
Ipanema Technologies
2-63
Ipanema System
The reports list is the same as in the Infovista client (IVreport). The report access can be defined
for each user with specific rules (see Infovista documentation.
A help can be accessed by clicking on the help button.
2-64
Ipanema Technologies
June 2009
Report example
June 2009
Ipanema Technologies
2-65
Ipanema System
2-66
Ipanema Technologies
June 2009
Contains the Java (JAR) files used to run the VistaPortal SE interface.
doc
images
pages
styles
Contains the CSS files used by the VistaPortal SE interface and sub
folder with the default and customizable pages (welcome.htm).
Web-inf
June 2009
Ipanema Technologies
2-67
Ipanema System
2. 7. IP|EXPORT SOFTWARE
ip|export is an optional module of the ip|boss software suite, the use of this module is enabled by
ip|boss license file and requires the ip|reporter module.
ip|export is delivered on a dedicated CD-ROM, which contains the different software components
(VistaViews Ipanema, Task scheduler, and program about reports models).
All the configuration tasks are carried out automatically by the ip|export module. Therefore, the
installation of the product is straightforward and its usage very simple.
2. 7. 2. ip|export architecture
ip|export adds a dedicated VistaViews in ip|reporter (InfoVista). This VistaView allows to create
some dashboard reports according to different filters. A task scheduler allows to export these
dashboard reports at a scheduled time (hour, day...) in Excel format.
2-68
Ipanema Technologies
June 2009
After the installation of ip|export task scheduler, a new Windows service is created:
Windows service
Execute the following command: ipm_cron /start in order to launch the task scheduler.
June 2009
Ipanema Technologies
2-69
Ipanema System
Windows service
2. 7. 3. 2. Uninstallation procedure
ip|export uninstallation consists in unloading the Vistaview from Infovista server, deleting the task
scheduler service and uninstalling ip|export program.
To uninstall ip|export, you must be connected as administrator on the server (removal
of windows service).Cron service must be stopped before uninstalling.
2-70
Launch Start/Program/ipexport/uninstall
Ipanema Technologies
June 2009
When done,
June 2009
Ipanema Technologies
2-71
Ipanema System
2. 8. IP|ENGINES
2. 8. 1. Installing ip|engines
For hardware installation, please refer to the ip|engines installation manuals
(Ipanema-ipeXXX_Directives_YY.pdf and Ipanema-ipeXXX_Configuration.pdf, where XXX
depends on the ip|engine model and YY depends on the language).
1. At opening, the list of physical ip|engines in the configuration is displayed in the left frame.
The Version column is not filled in. Select some ip|engines (or all with the Select all button
) and click on the Status button
the selected ip|engines.
2-72
Ipanema Technologies
June 2009
June 2009
Ipanema Technologies
2-73
Ipanema System
3. Select the ip|engines to be upgraded in the left frame and the ip|agent software version in
the right frame, and click on the Upgrade button
A message confirms that the selected ip|engines have received the upgrade order.
allows to cancel the upgrade request. Cancelling an upgrade is possible
A Cancel button
before or during the FTP download of the new version of ip|agent, but before the ip|engine
has started swapping.
4. A scheduling window opens, that allows to schedule the upgrade (during the night for
example), or launch it immediately by clicking on Ok without specifying any date or time:
5. Check that the upgrade has been completed correctly by selecting the concerned ip|engines
and by clicking on the Status button
2-74
Ipanema Technologies
June 2009
3. 1. DOMAINS OVERVIEW
After ip|uniboss and ip|boss servers installation, you have to create a Domain to use the system.
A Domain is a coherent set of elements:
ip|boss,
ip|engines.
The Domains are hermetic, an ip|engine of a Domain cannot dialog with an ip|engine
of another Domain. An ip|boss server can manage several Domains; one instance per
Domain should be created.
The creation of a Domain is done only on the server.
To create a Domain launch ip|uniboss web client or Java client (a CLI client is also available).
June 2009
Ipanema Technologies
3-1
Ipanema System
All configuration operations described in this section are performed from Mozilla Firefox 2.0 as
a web GUI on the workstation.
3-2
Ipanema Technologies
June 2009
Managing Domains
June 2009
Ipanema Technologies
3-3
Ipanema System
(About): shows information about ip|uniboss version and license information, and
allows to import a license.
3-4
Ipanema Technologies
June 2009
Managing Domains
Preferences:
Save: to save the active filter (and column display),
Delete: to delete a filter (and column display).
Actions: allows to make all the actions achieved through the corresponding buttons:
Consult,
Clone,
Modify,
Delete.
?
About: shows the software version and license information (the same as the
About button).
In the table, the LED on the left gives the objects operational states; for the Domains, it can be:
green (Started),
amber (Starting),
small and dark (when the Domain has just been created, before an Update has been
applied).
June 2009
Ipanema Technologies
3-5
Ipanema System
Connection window
3-6
Ipanema Technologies
June 2009
Managing Domains
If the server is setup with the default port number 9999, the port number is
not mandatory.
User name: name of the user (administrator by default),
Password: the password of the user (admin by default).
Click Validate. When done, you are logged in ip|uniboss.
The menu bar in the main window has the 6 menus File, "Windows, Edit, Display, Actions
and ?:
File, Edit, Display and ? are the same as described above (web client),
Windows allows to close all windows,
Action allows to make all the actions achieved through the corresponding buttons
(Consult, Clone, Modify, Delete), as in the web client, plus it gives an access to the tools
(Update, ip|boss servers, Password modification, Log, Issues, Inventory).
Toolbar and table view: refer to the description above (web client).
June 2009
Ipanema Technologies
3-7
Ipanema System
3-8
green (Compatible) if the server is reachable and compatible with ip|boss; ip|boss
version, OS version and JRE version are polled and displayed:
Ipanema Technologies
June 2009
Managing Domains
small and dark (when the server has just been created, before an Update has
been applied: an Update
into account).
June 2009
Ipanema Technologies
3-9
Ipanema System
3. 5. IMPORT A LICENSE
To create Domains, the license file license.ipmsys must be installed.
To get your license file, please contact the Ipanema Support service at the e-mail address
support@ipanematech.com or license@ipanematech.com.
In the Toolbar, select
About:
It shows the software version and license information (maximum number of Domains, total ISU
credits (Ipanema Software Units), maximum number of physical and virtual ip|engines, authorized
features, etc.):
About menu
The total number of ISUs (Ipanema Software Units) can be allocated in a flexible way accross
different Domains; refer to the Create a Domain section below.
To import a license, click on the Import button, browse your folders and select the proper license
file (license.ipmsys).
(The license file is copied:
3-10
In each Domains directory (if Domains were already existing, for example when upgrading
from a version to a new one): ~\salsa\ipboss\server\domains\<Domain>\conf (on
ip|boss server).)
Ipanema Technologies
June 2009
Managing Domains
If other windows have been opened and if the Domains window is not the active one, click on
the Domains tab.
Domains.
3. 6. 1. Create a Domain
Operating procedure table: service ip|reporter
June 2009
Ipanema Technologies
3-11
Ipanema System
A creation window opens where you can indicate your Domains characteristics:
The Domains parameters can be read in the Domains window and in the Inventory window.
3-12
Ipanema Technologies
June 2009
Managing Domains
Access port: port used by the client for that Domain (set 0 for a dynamic port).
ip|boss server
ip|boss server: to choose the server that will manage the Domain (from a drop-down list).
In display mode, ip|boss version, OS version, JRE version and the Compatibility
status are polled from the server and displayed:
Domain ISU
Allocated ISUs: to specify the number of Ipanema Software Units that are needed on that
Domain. Each function requires a certain number of ISUs, that can be purchased from Ipanema
(a new license file is then provided; refer to the Import a license section above). The number
of consumed ISUs and available ISUs for each Domain is displayed in the Domains windows.
June 2009
Ipanema Technologies
3-13
Ipanema System
In display mode, the Credit ISUs (as a percentage of the total number of ISUs
accross all Domains), the consumed ISUs (according to the activated services and
WAN accesses bandwidths) and the number of Available ISUs (= Allocated
Consumed) are computed and displayed:
The fourth frame, SNMP Parameters, allows to configure the SNMP agent of ip|boss:
SNMP Parameters
SNMP IP Address: to specify the SNMP agent (ip|boss) to be polled by the SNMP Manager
(ip|reporter) in case of a servers cluster only, so that the polling can continue after a switch,
Community name: to specify the community name (Public by default).
The fifth frame, ip|reporter parameters, allows to configure the ip|reporter parameters in order to
supervise and to create/delete reports in Infovista Server:
ip|reporter parameters
3-14
Ipanema Technologies
June 2009
Managing Domains
The sixth frame, Tuning, allows to configure the maximum number of User classes and USer
subnets, the HTTP timeout and the data collection periods between ip|boss and the ip|engines
and between ip|reporter and ip|boss, and used as the reporting polling period:
Tuning
Maximum number of User classes: the administrator can limit the number of User Classes;
-1 (default value) allows an infinite number,
Maximum number of User subnets: the administrator can limit the number of User subnets;
-1 (default value) allows an infinite number,
HTTP timeout: the timeout (in seconds) used on HTTP (or HTTPS) request; the time entered
must be consistent with the network (more than the max. RTT for the most distant ip|engine),
Supervision: the polling period of ip|engine updated status (default values should be used):
1 mn: every minute, ip|boss collects the supervision status (default value),
5 mn: every 5 minutes, ip|boss collects the supervision status,
15 mn: every quarter, ip|boss collects the supervision status.
Collect: the elementary period of the Correlation Records generation (packets collected during
the specified time) and collect period for ip|boss (default values should be used):
1 mn: a CR is made by the ip|engine every minute of traffic (default value),
5 mn: a CR is made by the ip|engine every 5 minutes of traffic,
15 mn: a CR is made by the ip|engine every quarter of traffic.
This parameter is used for the maps and real time flows window updates.
Short reporting: update period for clients of collector service (SNMP agent, ip|export) for short
period reports (default values should be used):
1 mn: the SNMP data are updated by ip|boss every minute (default value),
5 mn: the SNMP data are updated by ip|boss every 5 minutes,
15 mn: the SNMP data are updated by ip|boss every quarter .
This parameter is used for some reports in Ipanema Libraries like Time Evolution,
Detailed per Application, Detailed per User class, ....
June 2009
Ipanema Technologies
3-15
Ipanema System
Long reporting: update period for clients of collector service (SNMP agent, ip|export) for long
period reports (default values should be used):
1 mn: the SNMP data are updated by ip|boss every minute ,
5 mn: the SNMP data are updated by ip|boss every 5 minutes (default value),
15 mn: the SNMP data are updated by ip|boss every quarter .
This parameter is used for some reports in Ipanema Libraries like dashboard, Site
Talker/Listener, Subnet Talker/Listener....
The last frame, User management, allows to configure ip|boss in order to use centralized user
management:
User management
Radius: to enable or disable the RADIUS (Remote Authentication Dial-In User service) server(s)
refer to the Create Radius servers section below.
3-16
Ipanema Technologies
June 2009
Managing Domains
After a Domain creation (HMS in the example below) the following directory tree is created on
ip|boss server (by default in ~\salsa\ipboss\server\domains\):
3. 6. 2. Move a Domain
Refer to the document DomainMove.pdf provided on the CD-ROM, in the \doc directory.
June 2009
Ipanema Technologies
3-17
Ipanema System
The Radius configuration is common to all Domains. For each Domain, the Radius management
can be activated or not (refer to the Create a Domain section above).
If the Radius management is not activated, or if all declared Radius servers are unreachable, we
automatically fall back to the embedded ip|boss users management mode.
The Radius window can be displayed by clicking on
Radius window
This window contains three tabs: Configuration, Authentication servers and Accounting
servers.
Configuration
3-18
Ipanema Technologies
June 2009
Managing Domains
Accounting: allows to configure the accounting parameters, which are the same as in the
Authentication frame above.
Authentication servers
Priority: value between 0 and 32767 used to define different priority levels between the different
servers, when there are several ones; the higher the value, the lower the priority; default value
is 10,
Name: name you want to give to the server (50 characters max); names must be unique accross
the servers dictionnary,
Host name: IP address or host name of the server (50 characters max),
Port: port on which the server is listening to authentication requests (1645 by default),
Shared secret: shared secret for Radius authentication; it must consist of 15 or fewer printable,
non space, ASCII characters; it should have the same qualifications as a well-chosen password.
Accounting servers
The Accounting server creation window contains the same fields as the Authentication server
creation window (see above) (note: the Port on which the server is listening to accounting requests
is 1646 (UDP) by default).
June 2009
Ipanema Technologies
3-19
Ipanema System
Log:
3-20
the list of system events (on ip|uniboss server) with a time stamping,
the list of connections/disconnections to/from ip|uniboss with a time stamping.
Ipanema Technologies
June 2009
Managing Domains
3. 8. 2. Issues window
In the Toolbar, select
Issues window
This window contains a list of issues that may require a users action:
non
non
non
non
non
created Domains,
deleted Domains,
started Domains,
configured Domains,
reachable Domains.
June 2009
Ipanema Technologies
3-21
Ipanema System
3. 9. INVENTORY
In the Toolbar, select
Inventory:
Inventory window
This window is made of two frames:
Domain inventory,
Topology inventory. This frame is contextual: if no Domain is selected in the previous frame,
it displays all Domains topologies; if one (or several) Domain(s) is (are) selected, it displays its
(their) topology(ies) only.
The
Print button prints all the columns of the selected Domain(s),
whereas the Action / Print menu prints the selected columns of all the Domains.
3-22
Ipanema Technologies
June 2009
Managing Domains
3. 9. 1. Domain inventory
This frame contains the following information:
Server
Manager port
Collector port
Browser port
Portmapper port
Supervision
Collect
Reporting short
Reporting long
Domain services: shows if the following services are started (Yes) or not (No):
ip|true
ip|fast
ip|coop
ip|xcomp
ip|xtcp
ip|xapp
smart|plan
ip|reporter
ip|export
smart|path
Number of: shows the number of the following objects, with their totals on the last line:
June 2009
Physical ip|engines
Virtual ip|engines
Automatic metaview
On demand metaview
Automatic reports
On demand reports
User class
Topology subnet
User subnet
Applications
Ipanema Technologies
3-23
Ipanema System
3. 9. 2. Topology inventory
This frame contains:
Domain name
ip|boss server
ip|engine (software version, model and IP addresses are polled from the ip|engine; if it has
not been reachable, the field is blank):
WAN Access:
Server
Manager port
Collector port
Browser port
Portmapper port
Domain: shows if the following services are started (Yes) or not (No):
3-24
Total
Total
Total
Total
ip|reporter:
Name
Main public IP address
Main private IP address
Auxiliary public IP address
Auxiliary private IP address
LAN MAC address
Physical: Physical (Yes) or Virtual (No) ip|engine
Enabled: Enabled (Yes) or disabled (No)
Software version
Hardware
ip|true: Yes / No
ip|fast: Yes / No
ip|xcomp compress: Yes / No
ip|xcomp uncompress: Yes / No
ip|xtcp: Yes / No
ip|xapp: Yes / No
smart|plan: Yes / No
ip|true
ip|fast
ip|coop
ip|xcomp
ip|xtcp
ip|xapp
smart|plan
ip|reporter
ip|export
Ipanema Technologies
June 2009
4. 1. CONFIGURATION OVERVIEW
Once your Domain has been created (refer to the previous Chapter) and before starting a
measurement, optimization or compression session, you have to parameter your configuration
(one configuration per Domain).
This configuration uses:
general settings for all functions (measurement, optimization, compression, acceleration and
smart planning) ensuring:
configuration of the Domains ip|engines,
configuration of the topology subnets associated with the ip|engines,
selection of applications, TOS and User subnets assigned to the session, according to
the specific features of the traffic to be measured, optimized, compressed or accelerated,
June 2009
Ipanema Technologies
4-1
Ipanema System
All configuration operations described in this section are performed from Mozilla Firefox 3.0 as
a web GUI on the workstation.
Connection screen
4-2
Ipanema Technologies
June 2009
Configuring services
June 2009
Ipanema Technologies
4-3
Ipanema System
A table view shows a list of objects. All the table views give:
A menu bar,
A tool bar,
A list of objects.
Selection: you can select an object in the list by clicking on its line. To select other objects, you
have to click on their lines while pressing the Alt key. To select an interval of objects, you select
the first then the last by clicking while pressing the Shift key. The Edit menu (see below) allows to
select/unselect all the objects on the list. In the status bar, the number of selected objects and the
total number of objects is shown.
Sort: you can sort the list according to one column by clicking on this columns header (by clicking
on the header a second time, you change the order ascending-descending). By clicking on several
columns while pressing the Ctrl key, you make a sort on multi-columns. These functions are also
available through the Display/Sort menu (see below).
4-4
Ipanema Technologies
June 2009
Configuring services
June 2009
Ipanema Technologies
4-5
Ipanema System
Filter: create filters on the list which display only the filtered objects according
to the selected criteria.
There are two kinds of filters:
Simple filter
An extended filter (New Extended Filter) is a combination of simple filters
(using AND, OR, NOT logical operators). When a filter is active, the
number of displayed objects and the total number of objects is written
on the status bar. You can activate/deactivate a filter by double-clicking
on the icon of the status bar.
Extended filter
Choose columns: choose the columns to display.
Preferences: save or delete the display mode (filters and selected columns).
4-6
Ipanema Technologies
June 2009
Configuring services
The Actions menu, which allows to consult, clone, modify, delete and change the
administrative state of the objects. The list of actions is the same as you get through
the context menu of the list.
The ? menu, which gives an access to the About menu.
June 2009
Ipanema Technologies
4-7
Ipanema System
4-8
Ipanema Technologies
June 2009
Configuring services
Connection screen
June 2009
Ipanema Technologies
4-9
Ipanema System
If the server is setup with the default port number 9999, the port number is
not mandatory.
User name: name of the user (administrator by default),
Password: the password of the user (admin by default).
A table view shows a list of objects. All the table views give:
A menu bar,
A tool bar,
A list of objects.
4-10
Ipanema Technologies
June 2009
Configuring services
They are the same as in the web client. Refer to the web client description above for more
details.
The Display menu contains one additional function to the web client:
Fix columns: to fix the columns: this keeps the left columns unaffected by an horizontal
scrolling.
June 2009
Ipanema Technologies
4-11
Ipanema System
4. 4. 1. CLI architecture
ip|boss and ip|uniboss have a specific GUI client each, that uses CORBA over SSL to
communicate with a dedicated client request handler (called the Leonardi connector because
of the underlying technology).
Quite similarly, there is a CLI client for ip|boss and a CLI client for ip|uniboss. They communicate
exclusively with their respective CLI connector using CORBA over SSL. The best image to illustrate
what the CLI clients and CLI connectors are is to compare the CLI clients to Telnet clients and the
CLI connectors to remote shell services.
The CLI client/server protocol relies on three verbs:
Login
Logout
Execute
The client and the server exchange version information prior to the login request. This allows either
side to adapt to an older peer.
In its current version, the ip|boss CLI connector forwards login and logout requests to the targeted
Domains Leonardi connector, besides establishing its own session information and setting up
a session specific command parser that will process execute requests. If no specific Domain is
targeted, the ip|boss CLI connector will use the naming service to get a list of all running Domains
and will connect to the first available Domain (in alphabetical order) the provided credentials are
valid for.
The ip|uniboss CLI connector will forward the login and logout requests to the ip|uniboss Leonardi
connector.
Once the session is established, the CLI client acts a transparent upstream pipe between the client
systems keyboard or input file and the CLI connector and a transparent downstream pipe between
the CLI connector and the client systems display or output file.
4. 4. 2. CLI language
The ip|boss Leonardi connector essentially maps a Domains configuration to a set of object
classes and objects within each class. The ip|uniboss Leonardi connector does the same at a
higher level, where Domains are objects in a class. (This is very much akin to tables and rows we
are used to in DBMSes such as Oracle for example.)
The CLI language builds on this paradigm. The language basics are the same for ip|boss CLI and
ip|uniboss CLI. The difference currently only lies in the underlying schema - names of tables and
columns.
A CLI script is a (possibly empty) list of statements. A statement is always terminated by a ";"
(semicolon) character. The semicolon is not a statement separator but a statement terminator. The
difference is important, particularly for parser robustness sake. Having the semicolon act as a
statement terminator and not anything else makes error recovery much easier: eat and discard
input until you see the next semicolon and try to parse more statements from there.
CLI statements currently fall into 2 categories:
4-12
Ipanema Technologies
June 2009
Configuring services
Create ( or insert),
Modify ( or update),
Delete,
List ( or select).
But there are not only similarities, there are differences too. CLI DML statements act on one table
or object class at a time, there is no such thing as a join. Future releases of CLI will make it easy
to clone objects, just overriding a few columns with specific values. That is not easy in SQL.
CLI offers fine grained control over error handling and logging because it is mainly targeted at
procedure automation versus ad hoc queries.
For the same reason, CLI not only produces tabular output but can also use tabular input in
statements
June 2009
Ipanema Technologies
4-13
Ipanema System
Working space
The main window gives access to all features of the system.
4-14
Ipanema Technologies
June 2009
Configuring services
Toolbar
The buttons give a direct access to the functions. The tool bar is separated into 7 areas:
Global tools
: gives access to the user settings modification,
: gives access to another Domain and allows to check the status of all Domains at a glance
(this icon is only visible if you have an access to several Domains),
: refreshes the view (on the web client only; on the Java client, the view is automatically
refreshed every minute),
June 2009
Ipanema Technologies
4-15
Ipanema System
System administration
Click on System administration to access the System administration functions:
System provisioning
Click on System provisioning to access the System provisioning functions:
4-16
software upgrade
reboot
scripts
security status
advanced configuration
Ipanema Technologies
June 2009
Configuring services
Application provisioning
Click on Application provisioning to access the Application provisioning functions:
Supervision
Click on Supervision to access the Supervision functions:
: gives access to the different options (mail, SNMP trap) of the system,
June 2009
Ipanema Technologies
4-17
Ipanema System
Helpdesk
Click on Helpdesk to access the Helpdesk functions:
Reporting
Click on Reporting to access the Reporting functions:
4-18
Ipanema Technologies
June 2009
Configuring services
Status zone
The status zone is made of the Domain name, two bargraphs and four LEDs.
Bargraphs:
Active flows: gauge displaying the current active flows (max number for each collection)
measured by all enabled ip|true agents of the Domain (left figure) over the peak flows
measured since the session start-up (right figure),
Total throughput (Mbps): gauge displaying the current total throughput measured by
all enabled ip|true agents of the Domain (left figure) over peak throughput measured
since the session start-up (right figure).
LEDs:
Discovery: indicates when a Discovery agent is running on an ip|engine (amber color).
Limiting: indicates when a Local Traffic Limiting rule is active on an ip|engine (amber
color).
ip|boss: shows the overall status of ip|boss,
ip|engine: shows the overall status of the physical ip|engines,
The color of the indicator can be:
green: the services are started and the ip|engines are up,
yellow: one or more ip|engines are down,
red: all ip|engines are down,
grey: the services are stopped or no information,
June 2009
Ipanema Technologies
4-19
Ipanema System
ip|boss: shows the state of the system with two colored indicators:
Connection: shows the status of the connection between the client and the ip|boss
server:
Indicator color
Green
Red
Indicator color
Green
Red
the license is not respected (the number of ISUs exceeds the total
ISU credit)
With the Java client, two additional LEDs are available:
active and up
Red
Indicator color
4-20
Green
active and up
Red
Ipanema Technologies
June 2009
Configuring services
Reachable: displays the number of ip|engines currently reachable upon the total
number of ip|engines activated.
Indicator color
Green
Red
Indicator color
Green
no ip|engine is overloaded
Red
Indicator color
Green
Yellow
Red
Grey
June 2009
Ipanema Technologies
4-21
Ipanema System
Yellow
Grey
Red
Indicator color
Green
Yellow
Red
ip|true: displays the number of ip|engines currently measuring (ip|true agent running)
upon the total number of ip|engines activated.
Indicator color
Green
Yellow
Red
Grey
Indicator color
4-22
Green
Yellow
Ipanema Technologies
June 2009
Configuring services
Red
Grey
Indicator color
Green
Yellow
Red
Grey
Indicator color
Green
Yellow
Red
Grey
Indicator color
Green
Yellow
Red
Grey
Indicator color
Green
Yellow
Red
Grey
June 2009
Ipanema Technologies
4-23
Ipanema System
4-24
Ipanema Technologies
June 2009
Configuring services
4. 6. OPERATING PROCEDURE
The operating procedure consists of the following phases:
choosing a Domain,
creating a configuration or using an archived configuration, that is, specifying all ip|engines and
Domain settings (topology subnets, applications, User Classes, Qos Profiles, MetaViews....),
running a measure, optimization, compression or virtual cooperative session, applied to the
Domain,
analyzing the results in real-time,
reporting configuration of measures and optimization (optional).
June 2009
Domain).
Ipanema Technologies
4-25
Ipanema System
Operations to be
performed
Commands
ip|
true
ip|
fast
(1)
Manual procedure
Manual procedure
Coloring
WAN access
ip|engines
Topology Subnets
TOS
Applications
4-26
Ipanema Technologies
June 2009
Configuring services
Operations to be
performed
Commands
ip|
true
ip|
fast
(1)
Analyze links
X
Link supervision
X
X
Topology Subnets
X
X
QoS profiles
User Class
Modify reports
ip|reporter
Update
Stop a session
Service activation, ip|engines: off
June 2009
Ipanema Technologies
4-27
Ipanema System
Operations to be
performed
Commands
ip|
true
ip|
fast
(1)
X
X
Start a session
X
Link supervision
X
Real-time
Real-time Maps
X
ip|engines
X
QoS profiles
User Class
User Subnets
X
Coloring
WAN access
X
X
X
Update
X
4-28
Ipanema Technologies
June 2009
Configuring services
Operations to be
performed
Commands
ip|
true
ip|
fast
(1)
X
X
Start a session
Link supervision
Real-time
X
Real-time Maps
X
Update
X
Commands
ip|
true
ip|
fast
(1)
X
X
Start a session
X
Link supervision
Analyze real-time
compressed flows
X
Real-time
Real-time Maps
Management by adjusting
compression settings: User
Class
User Class
Management by adjusting
compression direction
settings: ip|engines
ip|engines
X
Update
X
June 2009
Ipanema Technologies
4-29
Ipanema System
Operations to be
performed
Commands
ip|
true
ip|
fast
(1)
X
X
Start a session
X
Link supervision
Analyze real-time
accelerated flows
X
Real-time
Real-time Maps
Management by adjusting
acceleration settings: User
Class
User Class
Management by adjusting
acceleration settings:
ip|engines
ip|engines
X
Update
X
4-30
Ipanema Technologies
June 2009
Configuring services
Operations to be
performed
Commands
ip|
true
ip|
fast
(1)
X
X
Start a session
X
Link supervision
Analyze real-time
accelerated flows
X
Real-time
Real-time Maps
Management by adjusting
acceleration settings:
ip|engines
Modify the session
dynamically
ip|engines
X
Update
X
June 2009
Ipanema Technologies
4-31
Ipanema System
Operations to be
performed
Commands
ip|
true
ip|
fast
(1)
smart|path service
Start a session
Service activation, ip|engines: on
Management by adjusting
smart path settings: User
Class
User Class
Management by adjusting
smart path settings: WAN
access
WAN access
Management by adjusting
smart path settings:
ip|engines
ip|engines
Management by adjusting
smart path advanced
parameters: Tools
Tools
X
Update
X
Operations to be
performed
Commands
ip|
true
ip|
fast
(1)
smart|plan service
Enable smart|plan for all
ip|engines
X
X
Start a session
X
Update
X
4-32
Ipanema Technologies
June 2009
Configuring services
Operations to be
performed
Commands
ip|
true
ip|
fast
(1)
Commands
ip|
true
ip| fast
(1)
Domain creation
Operations to be
performed
Update
ip|reporter: reporting
Define InfoVista server
settings
Define automatic reporting
Automatic reporting
Define Metaview settings
Metaview
Define reports
ip|reporter
June 2009
Ipanema Technologies
4-33
Ipanema System
Operations to be
performed
Commands
ip|
true
ip| fast
(1)
ip|boss: management
Supervision management
settings (mail, SNMP trap)
Options
Log window
Log
Create/Delete users
Users
User password modification
Login
Security configuration
Security
Certificate generation tab enerate the
keys and the certificates
Configuration tab hoose the encryption
algorithm
ip|engine status
ip|engine status
ip|engine status map
Security status
Tools, Status tab: displays the
security status of ip|engines
Discovering of applications,
subnets.....
Discovery
Upgrade ip|engines
software
Reboot ip|engines
Tools, Reboot tab
Quit the application
File/Exit
4-34
Ipanema Technologies
June 2009
Configuring services
Domain window
To change Domain, click on the corresponding Domains line and click on the Connect Domain
.
button
The name of the selected Domain appears in the status zone:
Status zone
The colors of the lines show the global status of the Domains:
A blank line is either a fully operational Domain (all activated functions run normally) or
a deactivated Domain (the ip|engines have not been enabled globally).
An orange line is a Domain with some down status (but not all).
A red line shows a Domain with all status down.
When selected, a line turns blue, whatever the Domains status (and the lines previous
color).
For each Domain, a synthesis of the status of the ip|engines, measurement (ip|true),
optimization (ip|fast), compression and decompression (ip|xcomp), TCP acceleration
(ip|xtcp), application acceleration (ip|xapp) and synchronization (ip|sync) is displayed, as
well as the total throughput on the Domain and the total number of active flows.
June 2009
Ipanema Technologies
4-35
Ipanema System
4. 8. 2. Open a configuration
Operating procedure table
The name of the configuration file is fixed. This file is in the directory
~\salsa\ipboss\server\domains\<Domain_name>\config
and
its
name
is
__active__.ipmconf. It contains all the configurations parameters of the Domain.
During the start and the update, this file is sent to the ip|engines.
To work with an existing configuration file, you must:
4. 8. 3. Save a configuration
Operating procedure table
The configuration file of the Domain __active__.ipmconf which is stored in the directory
~\salsa\ipboss\server\domains\<Domain_Name>\config is automatically applied and saved
on the following actions:
Update/Save
In case of necessity (for backup), you should make the backup of this file from your
server to the media of your choice (do not backup the file while an update is pending
on the ip|engines).
Important reminder it is advisable to backup your configuration file in a different directory than
that used for installation in order to avoid deleting files during subsequent install.
4-36
Ipanema Technologies
June 2009
Configuring services
Undo table
If a modification has been carried out by another user in the interval, undo will not
operate.
June 2009
Ipanema Technologies
4-37
Ipanema System
4. 9. SYSTEM PROVISIONING
4. 9. 1. Configuring Coloring
Operating procedure table: settings, ip|fast service
The Coloring Policy is used with optimization. It is the capability to modify the TOS or DiffServ field
in the IP header with a new value according to the type and criticality of the packet.
The mode used is Color-Blind (in this mode, all packets are treated as if they were uncolored:
they are marked according to the selected coloring rule, regardless of their initial color).
ip|fast must be enabled.
Coloring:
4-38
Ipanema Technologies
June 2009
Configuring services
June 2009
Ipanema Technologies
4-39
Ipanema System
This window defines the coloring policies to apply at the access to WAN (you can create as many
Colorings as you want). The coloring parameters specify the type of service, the TOS or DSCP
values function of the traffic type and criticality level. It comprises:
input fields:
Name: to identify the coloring policy (string of characters). By default , the name none is
defined associated with an unspecified service type. The name is used to identify the
Coloring policy,
Service type: to select the type of coloring policy to set-up. The service is selected from
a drop-down list. The values offered are:
TOS: the TOS field of the frame is set to the value specified by the Code point
setting. It then contains the value of the IP PRECEDENCE and the TOS specified
for the Class of Service,
DiffServ: "Differentiated Service" type service. The TOS field of the frame is
set at the value specified by the PHB Group (DSCP) setting, in accordance
with RFC 2474 (definition of the Differentiated Services Fields (DS Field) in the
IPv4 and IPv6 headers), RFC 2597 (Assured Forwarding PHB group), RFC 2598
(Express Forwarding PHB group)
unspecified: not specified,
a Coloring zone: to define or modify the coloring for type of Traffic and Criticality level:
PHB Group (DSCP): when DiffServ is the Service Type selected, the value for each
peer (type of Traffic and criticality level) is selected with drop-down list,
Precedence/TOS (b0b7): when ToS is the Service Type selected,
a display zone in the form of a table corresponding to the data previously entered.
Service type
PHB
group
DSCP
value
TOS value
Top
Express
Forwarding
EF
101110
EF
101110
Medium
EF
101110
Low
EF
101110
AF11
001010
AF12
001100
Medium
AF21
010010
Low
AF22
010100
BE
000000
High
BE
000000
Medium
BE
000000
Low
BE
000000
Top
High
Background
ToS default
setting
Criticality
level
High
Transactional
Top
Assured
Forwarding
Best Effort
4-40
Ipanema Technologies
June 2009
Configuring services
Coloring rules can also be created by importing them from a configuration file. Refer to
section Importing objects.
June 2009
Ipanema Technologies
4-41
Ipanema System
WAN access:
4-42
Ingress (LAN to WAN) max Bandwidth: maximum ingress throughput allocated at the WAN
interface of the CPE (in kbps),
Ingress (LAN to WAN) min Bandwidth: minimum ingress throughput that the tracking function
(see below) can track down (in kbps); if no value is entered, it will be set to 0,
Egress (WAN to LAN) max Bandwidth: maximum egress throughput allocated at the WAN
interface of the CPE (in kbps),
Egress (WAN to LAN) min Bandwidth: minimum egress throughput that the tracking function
(see below) can track down (in kbps); if no value is entered, it will be set to 0,
Coloring: selection, from a drop-down list, of the Coloring policy created in the Coloring
directory, to be applied. If there is no specific coloring (LS, Best effort), select "none". The
default display is none.
Ipanema Technologies
June 2009
Configuring services
Trust level: Routine or Business: in case of smart|path, defines which type of traffic is allowed
to go through the Network Access Point (Routine and Business sensitivity levels are also defined
for each User class, where they are used in the path decision to route traffic to a NAP with at
least the same Trust Level).
Report key: this field is optional. A report key field is used for ip|export, SNMP and
ip|reporter and allows to define regrouping of WAN accesses. A WAN access belongs to
only one regrouping.
For example, this field can be used to gather WAN accesses according to:
the type of network (all WAN accesses to an MPLS backbone, all WAN accesses to
the Internet, etc.)
the type of access line (all WAN accesses with an access line at 64 kbps, 128 kbps, ....)
June 2009
Ipanema Technologies
4-43
Ipanema System
Bandwidth tracking
Congestion detection is key to know when and where to manage flows. Network available capacity
may also vary in time. Bandwidth Tracking learns the available network capacity:
Bandwidth Tracking
Bandwidth tracking principles:
Output:
Available bandwidth for each potential congestion point.
4-44
Ipanema Technologies
June 2009
Configuring services
ip|engines manage three potential congestion points between any pair of sites:
By setting a minimum bandwidth lower than the maximum bandwidth, the tracking function will
detect the actual value of the bandwidth between those two values:
By setting a minimum bandwidth equal to the maximum bw, the tracking function will not trigger:
WAN accesses can also be created by importing them from a configuration file. Refer
to section Importing objects.
June 2009
Ipanema Technologies
4-45
Ipanema System
4. 9. 3. Configuring ip|engines
Operating procedure table, ip|fast service, ip|xcomp service, ip|xtcp service, ip|xapp service,
smart|path service.
In the System provisioning Toolbar, select
displayed:
The number of virtual and physical ip|engines which can be created are limited by the
license. This number is displayed in the About window.
ip|engines can also be created by importing them from a configuration file. Refer to
section Importing objects.
4-46
Ipanema Technologies
June 2009
Configuring services
the General tab is made of three frames: General, WAN Access and Services.
the Advanced tab is made of two frames: Compression type and Navigation.
General tab
1. The General frame contains the following input fields and click boxes:
General frame
Name: character string used to identify the ip|engine (50 alphanumeric characters max),
Main public IP address (mandatory): IP address of the ip|engine visible by ip|boss server for
management purposes (configuration, collection of the correlation records, supervision),
Main private IP address (option if only the Main public address is declared, then the Main
private address is automatically allocated the same value): IP address of the ip|engine as it
has been locally configured (with the ipconfig command).
- In most cases (VPN, flat addressing, ...) only the Main public address is needed.
- In case of NAT, the two addresses must be different.
According to the MGT port being used or not, the Main addresses can be allocated to either the
LAN-to-WAN bridge (if the MGT port is not used in band management), or to the MGT port, if
used (out of band management):
June 2009
Ipanema Technologies
4-47
Ipanema System
Auxiliary public IP address (mandatory when the MGT port is used; must not be declared
otherwise): IP address of the ip|engine visible by other ip|engines for measurement (ip|true),
optimization (ip|fast), compression (ip|xcomp, signalling + tunnel), TCP acceleration (ip|xtcp),
application acceleration (ip|xapp) and synchronization (ITP/NTP) purposes; it allows for out of
band management (using the Main address) but in band inter-ip|engines messages (using the
Auxiliary address),
Auxiliary private IP address (option if only the Aux. public address is declared, then the
Aux. private address is automatically allocated the same value): IP address of the ip|engine as
it has been locally configured (with the ipconfig command) for the LAN-to-WAN bridge.
The Auxiliary addresses are allocated to the LAN-to-WAN bridge, when the MGT port is used (in
this case, the Main addresses are allocated to the MGT port). Refer to the second diagram above.
If no Auxiliary address is declared, the inter-ip|engines messages use the Main
address.
- In most cases (VPN, flat addressing, ...) only the Auxiliary public address is needed.
- In case of NAT, the two addresses must be different.
Report key: this field is optional. A report key field is used for ip|export, SNMP and ip|reporter
and allows to define regrouping of ip|engines. An ip|engine belongs to only one regrouping.
For example, this field can be used to gather ip|engines according to:
a geographical criteria (all ip|engines in Europe, North America, Asia, Africa...).
the type of access line (all ip|engines with an access line at 64 kbps, 128 kbps, ....)
4-48
Auto-reporting: to allow (yes) or not (no) the reports created with the Automatic reporting
function to be added for this ip|engine. Refer to the Automatic reporting section.
Type: physical or virtual ip|engine. If the selected ip|engine is virtual, it is characterized by an
alias and an IP address; if no IP address is defined ip|boss randomizes a virtual IP address
with a 240.x.x.x prefix.
Ipanema Technologies
June 2009
Configuring services
2. The WAN Access frame allows to configure the WAN access(es) on the Network Access
Point(s); it contains the following input fields:
Path Selection: when enabled (TOS clicked), allows to configure up to three WAN accesses
(if there are several NAPs on the site and if the smart|path feature is allowed in the license). It
is Disabled by default (one WAN access on one NAP only); optimize must be checked in the
Services frame to enable it.
WAN access 1: name of the NAPs WAN access (mandatory)
When the TOS click box is checked (optimize must be clicked in the Services frame first), the
WAN Access frame contains the following input fields after Path Selection:
June 2009
Ipanema Technologies
4-49
Ipanema System
3. The Services frame allows to define the ip|engines capabilities. It contains the following click
boxes:
Services frame
4-50
Ipanema Technologies
June 2009
Configuring services
Advanced tab
By default, both types of compression are enabled (when compress is checked in the Services
frame in the General tab).
We do not recommand to change the default settings without advice from the Ipanema
Support.
June 2009
Ipanema Technologies
4-51
Ipanema System
Navigation frame
These two fields allow to navigate in the reports (in ip|reporter) in different ways:
The first browsing method does not use these two fields: by selecting Folders in the drop-down
list in ip|reporters main window, you can access the reports with the following file system tree
(4 hierarchical levels):
<Domain> / <type of MetaView> / <MetaView> / <time level, public/private>
The second browsing method allows to navigate in the sites reports with two additional
hierarchical levels, defined by these two fields: by selecting Navigation in the drop-down list
in ip|reporters main window, you can access the sites reports with the following file system
tree (6 hierarchical levels):
<Domain> / Navigation / <Folder name for level 1> / <Folder name for level 2> /
<MetaView> / <time level, public/private>
(the <type of MetaView> level disappears, as this method is valid to access the sites reports
only).
This method is very helpful on larges networks, with hundreds or thousands of sites.
In the example below, Folder name for level 1 was used to group sites per continents, and
Folder name for level 2 was used to group sites per countries. The ip|engines created without
filling those fields are grouped under the Unknown folder name:
4-52
Ipanema Technologies
June 2009
Configuring services
June 2009
Ipanema Technologies
4-53
Ipanema System
Topology Subnets:
The Topology subnets are used by the ip|engines to classify, measure and optimize
the traffic peer to peer. These subnets match the IP subnets of the sites where the
ip|engines are installed. All of them must be declared (in the example above, two
Topology subnets are declared on the Datacenter, 10.2.1.0/24 and 10.2.4.0/24). Use
the Discovery agent and the SA Site throughput report to check if no one is missing.
The traffic from/to a Topology subnet is described as coming from/to the User subnet
Other. To report it with a specific name, see the User subnet paragraph.
4-54
Ipanema Technologies
June 2009
Configuring services
) or remove (
removed with
and
buttons).
Several physical ip|engines can be associated to a same subnet in case of clustering. The
clustering function defines the subnet partition for several ip|engines (for example Central site
with backup routers). At a time, a session belongs to only one ip|engine of the cluster.
Cluster solution works with a Hot Standby Router, load sharing per session but not
load sharing per packet.
Clustering
Clustering configuration:
Subnets
Associated ip|engines
This diagram
ip|e A, ip|e B
LAN_HQ
HQ1, HQ2
Administrative state:
Enable: Topology subnet taken into account,
Disable: Topology subnet not taken into account.
The ip|engines associated with a Topology subnet must be upstream from the data
flows of this subnet.
Topology subnets can also be created by importing them from a configuration file. Refer
to section Importing objects.
June 2009
Ipanema Technologies
4-55
Ipanema System
A Time server, which can be an external clock reference (NTP) or an ip|engine of the Domain,
is used as the main synchronization source,
Synchronization servers, which are ip|engines of the Domain (use several for redundancy
reasons), get their synchronization from the Time server and propagate it to all the other
ip|engines of the Domain,
All other ip|engines of the Domain get their synchronization from the Synchronization servers
(without any out of Domain connection).
This architecture allows GPS-less Domains, out of Domain synchronization and short term no
time function (a Domain can be disconnected from its Time server, the Synchronization servers
will remain synchronized to each other, thus making higher resiliency).
Time servers
can be either ip|engines (with or without GPS), ip|boss or External NTP servers,
must be delivering a consistent time between each other,
if an ip|engine is a Time Server, it will use its local ITP configuration (GPS, local or an external
source).
if a Time server is an external NTP server, the ITP port must be tuned to 123 (Sentry
Tuning section in the __active__.ipmconf ip|boss configuration file).
Synchronization servers
4-56
Ipanema Technologies
June 2009
Configuring services
Configuration
In the System provisioning Toolbar, select
ip|sync:
The Time server directory gives the list of all ITP servers. It includes:
a Server field: allows to enter the IP address of a time server (several ones can be
declared).
an ip|engine field: allows to select an ip|engine as a time server (select only one).
Declare a Server or an ip|engine.
the zone on the right displays the selected time servers for the Domain.
The Synchronization server directory gives the list of all ip|engines that can be used as ITP
servers. It includes:
an ip|engine field: allows to select ip|engines as ITP servers (choose two or three, for
redundancy reasons). They do not need GPS antennas.
the zone on the right displays the selected ITP servers for the Domain.
June 2009
Ipanema Technologies
4-57
Ipanema System
4. 9. 6. Importing objects
The following objects can be created by importing them from a configuration file: Coloring rules,
WAN accesses, ip|engines and Topology subnets.
As the procedure is the same for all those objects, we will consider one case only.
An existing configuration file in raw format (.res) can be imported:
In the Coloring rules window, the WAN accesses window, the ip|engines window or the
Import window
To import a file, its first line must be the description of the fields. This line is present
if the file was made with an export:
Exported file (the first line wrapped in the example is the description of the fields)
In the Import window that opens, click on Import all, or select the objects to import then click
on Import selection.
Import window
4-58
Ipanema Technologies
June 2009
Configuring services
A message tells you how many objects could be successfully imported; click on Ok.
If the Import file contains an object that already exists (same name), it will update it; an
update icon warns you:
If objects could not be created (already existing IP address for an ip|engine, for
example), an error message warns you:
June 2009
Ipanema Technologies
4-59
Ipanema System
4. 9. 7. Tools
The System provisioning Toolbar provides a
Tools
They are described in the following sections:
4-60
Software upgrade:
2.8.2. (INSTALLATION / ip|engines / Upgrading ip|engines software).
Reboot:
5.3.1. (SUPERVISION / SYSTEM PROVISIONING: TOOLS / Rebooting).
Scripts:
5.3.2. (SUPERVISION / SYSTEM PROVISIONING: TOOLS / Scripts).
Security status:
5.2.5. (SUPERVISION / SUPERVISION / Security).
Advanced configuration:
4.9.8. (CONFIGURING SERVICES / SYSTEM PROVISIONING / Configuring smart|path).
Ipanema Technologies
June 2009
Configuring services
Sticky choice:
- per packet:
- per session
(default
value):
Slave return:
- no:
- yes
(default
value):
June 2009
Ipanema Technologies
4-61
Ipanema System
Sensitivity policiy: matching User classes sensitivities with WAN accesses Trust Levels
depends on a policy which can be changed here.
This parameter can be overwritten for each User class, thanks to the User class
configuration windows Advanced tab.
- Strict:
- Protected:
- Ordered:
4-62
Ipanema Technologies
June 2009
Configuring services
The User Subnets are used by the system for services configuration (ip|true, ip|fast and
ip|reporter). These user subnets identify hosts, servers or subnets on which measure,
optimization or reporting is requested by the system. These user subnets are used in the
application, User class and metaview definitions.
In the Application provisioning Toolbar, select
User subnets:
June 2009
Ipanema Technologies
4-63
Ipanema System
TOS:
Configuring TOS
TOS that are not explicitly named in the dictionary are implicitly grouped into the Other category.
The TOS window contains the following input fields and click boxes:
4-64
Ipanema Technologies
June 2009
Configuring services
Applications:
Applications window
This window is made of two frames:
June 2009
Ipanema Technologies
4-65
Ipanema System
1. declared port,
2. syntax engine,
3. well-known port (RFC 1700).
Applications that are not recognized or enabled in the dictionary are implicitly grouped on the lower
layer protocol (e.g. TCP or UDP).
B
C
F
G
4-66
AIM
Audiogalaxy
BGP
Bittorrent
Citrix
Corba
= GIOP
COTP
CUPS
DCERPC
DHCP
DICT
DirectConnect
DNS
Edonkey
EIGRP
Exchange
= MAPI
FTP
FTPS
Secure FTP
G711a
G711u
G723
G729
GIOP
Gnutella
GoBoogy
GRE
Ipanema Technologies
June 2009
Configuring services
J
K
L
GTP
H225
HSRP
HTTP
HTTPS
Secure HTTP
ICMP
ICQ
I seek you
Identification protocol
IGMP
IMAP
IMAPS
Secure IMAP
IPP
IPSec
IP Secure
IRC
IRCS
Secure IRC
ISAKMP
Jabber
JetDirect
Kazaa
Kerberos
L2TP
LDAP
LDAPS
Secure LDAP
LoadBalancing
Lotus Notes
LPR
MAPI
MCS
MGCP
MMS
Mount
MS_SQL
= TDS
MS Exchange
= MAPI
MSN
MSN Messenger
Mute
MySQL
Napster
NARP
June 2009
Ipanema Technologies
4-67
Ipanema System
Q
R
4-68
Netbios
NetFlow
NFS
NNTP
NNTPS
Secure NNTP
NSPI
NTP
Open FT
OSPF
PCAnywhere
PIM
POP3
POP3S
Secure POP3
PortMapper
Postgres
PPP
Point-to-Point Protocol
PPTP
Printer_ipp
= IPP
Q931
Quake
(game)
RADIUS
RDP
Remote Shell
RFB
RLogin
Remote Login
RLP
RPC
RQuota
RSH
= Remote Shell
RStat
RSVP
ReSerVation Protocol
RSync
RTP/RTCP
RTSP
RUsers
Ipanema Technologies
June 2009
Configuring services
SAP
SIP
Skype
SLP
SMB
SMTP
SMTPS
Secure SMTP
SNMP
SOAP
Socks
Sockets
Soulseek
SrvLoc
SSDP
SSH
Secure Shell
SSL
Sync
Syslog
TCP
TDS
Telnet
TelnetS
Secure Telnet
TFTP
TNVIP
UCP
UDP
URL
VMWare
VNC
= RFB
VRRP
WINMX
X11
XOT
Yahoo Messenger
YPPasswd
YPServ
June 2009
Ipanema Technologies
4-69
Ipanema System
YPUpdate
Client/Server
Internet
ActiveX, FTP, IP, TCP, UDP, IRC, NNTP, SSH, SSL, TFTP, HTTP,
HTTPS, URL, Remote Shell, Socks
Security
ERP
SAP, Oracle
Database
Directory Service
Messenger,
Groupware
Network Service
Chat
File server
Terminal
Time
NTP
Game
Quake
Remote Client
Peer to peer
Tunneling
Audio/Video, VoIP
Routing
RIP ng1, RIP v1, RIP v2, EIGRP, IGMP, PIM, OSPF, BGP, HSRP,
Load Balancing
Network Management
Printing
4-70
Ipanema Technologies
June 2009
Configuring services
The system recognizes about 180 protocols (HTTP, ICMP, FTP, RTP/RTCP, H.225, SAP, Citrix,
Skype, VMWare....; refer to the comprehensive list in the tables above).
Attributes depend on protocols:
for HTTP: it is possible to distinguish the URL name (www.ipanematech.com for
example)
Syntax:
?
a unique character
separator in a list
Examples:
www.google.fr
www.google.*
www.google.*/*.gif
*/*.gif
*/*
www.ipanematech.*/web_germany/*
Specific cases:
host/*
"any" URI
host/
empty URI
*/full/uri
"any" HOST
/full/uri
empty HOST
for Citrix: it is possible to distinguish published applications (Word, Excel for example)
when the applications are not multiplexed on the same TCP session,
for RTP/RTCP: Codec type (choose from a drop-down list),
for TCP/UDP: port number, list of ports or range of ports, subnet or list of subnets
for others: no information is necessary.
Applications that are not explicitly named and enabled in the dictionary are implicitly grouped on
the lower layer protocol (e.g. TCP or UDP).
June 2009
Ipanema Technologies
4-71
Ipanema System
4-72
Ipanema Technologies
June 2009
Configuring services
June 2009
Ipanema Technologies
4-73
Ipanema System
User Subnets filter: this optional parameter can be used to identify an application by the IP
address of a server or client, or list of servers or clients (ex: SAP). It is possible to choose the
server or client from a drop-down list of the User subnets, or directly:
User Subnets List: choose the user subnet or server in the drop-down list of user
subnets to be associated with the application,
Prefix/Length: set the subnet with the following notation X.X.X.X/Y where X.X.X.X is
the IP address and Y the length integer between 0 and 32; a list of IP addresses can be
configured (; separator).
C/S Side: specify if the application must be recognized on the server side or on the client
side.
4-74
Ipanema Technologies
June 2009
Configuring services
Intranet , Internet corporate and Internet must be ordered in the Protocols frame...
June 2009
Ipanema Technologies
4-75
Ipanema System
QoS profiles:
4-76
Ipanema Technologies
June 2009
Configuring services
Session B/W (kbps): to specify the bandwidth per session; the value is used by ip|fast,
Obj. (objective): nominal bandwidth per session.
The objective bandwidth per session is operational during the congestion
step.
Max. (maximum): maximum bandwidth allowed per session.
The maximum bandwidth per session is always operational (even without
congestion).
The maximum bandwidth per session cannot be more than 20 x session
B/W objective for any kind of traffic.
Delay (ms), Jitter (ms), Packet loss (%), SRT (server response time, ms), RTT (round trip
time, ms), TCP retrans. (%): to specify, for each flow, the Objective and Maximum values for
that QoS profile. These parameters are enabled or not by checking the click box or not,
These information can be used by the User Class reporting to control the QoS associated with
each User Class.
all values <
Obj.
Max.
acceptable
Correct
unacceptable
Interpretation of Obj. and Max. criteria for Delay, Jitter, Loss, SRT, RTT and TCP retrans.
Name
Type
Session
BW
(kbps)
Delay
(ms)
Default
Bg
30-600
File transfer
Bg
Business
Jitter
(ms)
Packet
Loss
(%)
SRT
(ms)
RTT (ms)
TCP
retrans.
(%)
200-1000
1-10
0-0
400-2000
1-10
50-1000
500-1000
1-10
0-0
1000-2000
1-10
Tr
50-500
200-500
1-5
0-0
400-1000
1-5
Thin client
Tr
40-400
100-500
1-5
0-0
200-1000
1-5
Bg
50-1000
500-2000
1-10
0-0
1000-4000
1-10
Net services
Bg
20-200
100-500
1-10
0-0
200-1000
1-10
Web
Tr
40-400
200-1000
1-10
0-0
400-2000
1-10
G711
RT
90-120
100-200
50-100
0-2
0-0
200-400
0-2
G723
RT
20-30
50-150
50-100
0-1
0-0
100-300
0-1
G729
RT
30-45
50-150
50-100
0-1
0-0
100-300
0-1
Video streaming
RT
150-200
200-1000
50-100
1-5
400-2000
1-5
Ex. of QoS Profiles (Bg: background, Tr: transactional, RT: real-time; in each column: obj.-max.)
June 2009
Ipanema Technologies
4-77
Ipanema System
business criticality,
QoS performance objectives (nominal bandwidth per application session, delay, jitter, packet
loss, SRT, RTT and TCP retransmission),
the enabling of compression.
The users objectives are the only input to the system. There is no need to set low-level, network
and device specific policy rules.
The Ipanema System performs:
User Classes are independent of ip|true, ip|fast, ip|xcomp, ip|xtcp, smart|path and smart|plan
services.
User Classes are given in a tree structure, each User Class is characterized by:
a name,
filters to define the rules of traffic classification corresponding to the User Class,
a criticality level to define the level of criticality associated to the application(s) in this User Class,
a QoS profile that enables QoS objectives for the application(s) in this User Class,
the capability to be compressed.
tjhe capability to be accelerated.
The position of the User Classes in the tree structure is important, it determines the
classification of the packets. The classification is performed by running the structure
tree downwards. The packet is classified with the first applicable classification met.
Other, included the whole classifications, is at the end of the tree.
The configuration of the User Classes is necessary for the good behavior of the optimization agent,
ip|fast.
4-78
Ipanema Technologies
June 2009
Configuring services
User classes:
June 2009
Ipanema Technologies
4-79
Ipanema System
Dictionary filters,
Subnet filters,
ip|engine filters,
Advanced
The selection areas at the bottom of the window depend on the selected tab (see below).
A zone displaying the characteristics of the selected User Class:
A zone with multiple selection areas, that depend on the selected tab at the top of the window:
the first area (on the left) shows a list of elements of the Dictionaries (Applications,
ToS values), Subnets (source and destination) or ip|engines (ingress and egress) as
described in the system and managed by ip|boss
the second area (on the right) shows the selected elements for the User Class.
- A logical Or is applied for the different elements inside a filter (for example filter
Applications: HTTP or HTTPS).
- A logical And is applied for the different types of filters (for example Applications:
HTTP or HTTPS and subnet-src=LAN-192).
4-80
Ipanema Technologies
June 2009
Configuring services
Arrows are used to move the selected data from one area to the other (one by one or all at a
time).
June 2009
Ipanema Technologies
4-81
Ipanema System
By selecting Subnets with this tab, you create local rules that will apply only to
those Subnets! Do this only if really needed. Otherwise, use global parameters only
(Dictionary filters).
4-82
Ipanema Technologies
June 2009
Configuring services
an Ingress zone: displays the ip|engines list as described in the directory (include the virtual
ip|engines),
an Egress zone: displays the ip|engines list as described in the directory (include the virtual
ip|engines),
Description of the two areas of the tab: see description above.
By selecting ip|engines with this tab, you create local rules that will apply only to
those ip|engines! Do this only if really needed. Otherwise, use global parameters only
(Dictionary filters).
June 2009
Ipanema Technologies
4-83
Ipanema System
Advanced tab
This tab contains two additional frames:
Smart|path: matching User classes sensitivities with WAN accesses Trust Levels depends on
a policy which can be changed for each User class thanks to this parameter:
Sensitivity policies allows to choose between different policies.
Refer to 4.9.7. System provisioning / Tools / Advanced configuration for a comprehensive
description of each one.
Default: the policy selected in System provisioning / Tools / Advanced
configuration will apply.
Preferred: the policy selected in System provisioning / Tools / Advanced
configuration will be overwritten by the Preferred policy for this User class.
Strict: the policy selected in System provisioning / Tools / Advanced configuration
will be overwritten by the Strict policy for this User class.
Protected: the policy selected in System provisioning / Tools / Advanced
configuration will be overwritten by the Protected policy for this User class.
Ordered: the policy selected in System provisioning / Tools / Advanced
configuration will be overwritten by the Ordered policy for this User class.
4-84
Ipanema Technologies
June 2009
Configuring services
Using the Dictionary filters tab when configuring User Classes, as described above.
Using the Application mapping functionality.
To access the Application mapping functionality, in the Application provisioning Toolbar, select
Application mapping.
The Mapping of applications within User classes window is displayed.
This window contains the map itself plus the following buttons:
: no access,
: to get the list of flows corresponding to the square area in the window (refer to the real
time flows list below),
June 2009
Ipanema Technologies
4-85
Ipanema System
At the first zoom level, the map displays the full traffic with a main square per User class and a
sub-square per application.
The zoom in, zoom out and reset zoom functions can be accessed using the right
button on the mouse on the ip|boss Java Client.
By moving the mouse on a square, a contextual text shows the description of the square:
Contextual text
4-86
Ipanema Technologies
June 2009
Configuring services
limit the bandwidth used by the different networks of the departments, services (user subnets)
or applications according to specific criteria taking the following constraints into account:
source subnet,
remote subnet,
applications,
TOS/CP values.
a name,
filters to define the rules to classify the traffic corresponding to the LTL,
a limit on the bandwidth that can be used by the class.
The LTL rules are enabled only if ip|fast is activated on the ip|engine.
LTL.
June 2009
Ipanema Technologies
4-87
Ipanema System
4-88
Ipanema Technologies
June 2009
Configuring services
4. 11. REPORTING
4. 11. 1. Configuring MetaViews
Operating procedure table: settings, service ip|true, service ip|reporter
The Metaviews are objects used to show the data according to your criteria (topology,
applications...) in order to be used by external reporting tools (including ip|reporter) and to
trigger logs, traps or e-mails when certain thresholds are surpassed (Alarming). The MIB will be
populated according the settings of the Metaviews.
Metaviews show information about the traffic or availability according to the following criteria:
and any complex definition with the previous parameters, using several fields and, possibly,
several tabs.
For example, a Metaview can aggregate the data on the Domain (no filter), but another metaview
could detail the behavior between 2 subnets and a particular application.
ip|reporter uses the Metaviews for the reports creation and data collection.
Two modes of Metaview creation are available:
unitary mode: allows to create Metaviews one by one with your own naming rules. This mode
can be used in order to create a troubleshooting Metaview with complex filters (for example a
destination site, a source site and a specific application),
wizard mode: allows to create a big number of Metaviews with automatic naming rules and
simple filter (for example: one Metaview for each user subnet of the Domain).
Metaviews for the Domain, the Physical sites, the Virtual sites and the User classes are
automatically created by the system (as soon a new Domain, a new Physical site, a
new Virtual site or a new User class is created, respectively).
As a consequence, only one Metaview needs to be created manually in the window
below (the one that will be used to troubleshoot Telnet between Factory and
Headquarters, on the sixth line).
The Metaview name is used by ip|reporter to name the instances of the reports.
June 2009
Ipanema Technologies
4-89
Ipanema System
Metaview.
4-90
Ipanema Technologies
June 2009
Configuring services
The Name of the Metaview, used by ip|reporter to name the instances of the reports,
The Type: as this function is used to create a Metaview on demand, the field always displays
on demand.
Used for ip|export: the data collected for this Metaview will be provided to ip|export, if clicked.
A zone with three tabs:
Configuration,
User Subnets,
Traffic classification.
the first area (on the left) shows a list of elements (ip|engines, Keys, User subnets, Applications,
User Classes, etc.), as described in the system and managed by ip|boss
the second area (on the right) shows the selected elements for the Metaview.
A logical Or is applied for the different elements inside a filter.
A logical And is applied for the different types of filters.
Some arrows are used to move the selected data from one area to the other, one by one (using
the single arrows) or all at a time (using the double arrows).
June 2009
Ipanema Technologies
4-91
Ipanema System
Configuration tab
This tab comprises the filters which define the rules of traffic topologies corresponding to the
Metaview (from Site A to Site B, etc.). It contains the following areas:
Site A: displays the ip|engines list as described in the configuration (includes the virtual ones),
Reminder: Metaviews for the Sites are automatically created by the system.
Site B: displays the ip|engines list as described in the directory (includes the virtual ones),
This list is available only if at least one site in Site A is selected.
4-92
Engine Report Key A: displays the ip|engine report key list as described in the configuration,
Ipanema Technologies
June 2009
Configuring services
Engine Report Key B: displays the ip|engine report key list as described in the configuration,
This list is available only if at least one ip|engine report key in Engine Report Key
A is selected.
NAPid A: displays the Network Access Points list as described in the configuration,
NAPid B: displays the Network Access Points list as described in the configuration,
This list is available only if at least one Network Access Point in NAPid A is selected.
WAN Access Report Key A: displays the WAN Access report key list as described in the
configuration,
WAN Access Report Key B: displays the WAN Access report key list as described in the
configuration,
This list is available only if at least one WAN Access report key in WAN Access
Report Key A is selected.
User Subnet A: displays the User subnets list as described in the configuration,
User Subnet B: displays the User subnets list as described in the configuration.
This list is available only if at least one subnet in User Subnet A is selected.
June 2009
Ipanema Technologies
4-93
Ipanema System
4-94
Criticality: displays the criticality list as described in the configuration (from Top to Low).
Ipanema Technologies
June 2009
Configuring services
the first area (on the left) shows a list of elements (ip|engines, Keys, User Subnets, User
Classes, etc.) as described in the system and managed by ip|boss,
the second area (on the right) shows the selected elements for the Metaviews.
Some arrows are used to move the selected data from one area to the other (one by one or all at
a time).
By selecting several elements in each list, the system will create the Metaviews
according to combinative selected criteria.
The wizard mode automatically manages the naming rules (the name varies according to the
selected elements).
June 2009
Ipanema Technologies
4-95
Ipanema System
Configuration Tab
Configuration Tab window: see above.
This tab comprises the filters which define the rules of traffic topologies corresponding to the
Metaviews (From/to Site A, from/to Key ). It contains the following areas:
4-96
Site: displays the ip|engines list as described in the configuration (includes the virtual ones),
Reminder: Metaviews for the Sites are automatically created by the system.
Key: displays the ip|engines report keys list as described in the configuration,
NAP id: displays the Network Access Points as described in the configuration,
Network report key: displays the WAN access report keys as described in the configuration.
Ipanema Technologies
June 2009
Configuring services
User Subnets: displays the User subnets list as described in the configuration.
Criticality: displays the criticality list as described in the configuration (from Top to Low).
June 2009
Ipanema Technologies
4-97
Ipanema System
4-98
Ipanema Technologies
June 2009
Configuring services
Alarming.
Alarming window
This window contains three frames:
An alarm is the instantiation of a rule (when does the alarm trigger/rearm?) on a Metaview (on what
objects - sites, User classes, etc. - does the rule apply?).
Creating an alarm is achieved in three steps:
creating a rule,
associating a rule to a Metaview,
activating logs and/or mails and/or traps on alarming events.
June 2009
Ipanema Technologies
4-99
Ipanema System
When a rule is created, an Identifier is automatically attributed to it by the system, that can be seen
in the Alarming window (Ident).
4-100
Ipanema Technologies
June 2009
Configuring services
Rules syntax
The description of a threshold must respect the following grammar:
exp ::= prefixexp
exp ::= number
exp ::= exp binop exp
exp ::= unop exp
prefixexp ::= var | ( exp )
Examples:
lan_ingress_packet_loss > 5
wan_egress_throughput > 1000
wan_ingress_throughput > 0.2 * ingress_wan_access_ingress
Name
Unit
Name
Unit
ingress_tcp_rtt_min
ms
lan_egress_min_delay
ms
ingress_tcp_rtt_avg
ms
lan_egress_avg_delay
ms
ingress_tcp_rtt_max
ms
lan_egress_max_delay
ms
egress_tcp_rtt_min
ms
lan_egress_jitter
ms
egress_tcp_rtt_avg
ms
lan_egress_sessions
number
egress_tcp_rtt_max
ms
wan_ingress_throughput
kbps
ingress_tcp_srt_min
ms
wan_ingress_packet_loss
ingress_tcp_srt_avg
ms
wan_ingress_min_delay
ms
ingress_tcp_srt_max
ms
wan_ingress_avg_delay
ms
egress_tcp_srt_min
ms
wan_ingress_max_delay
ms
egress_tcp_srt_avg
ms
wan_ingress_jitter
ms
egress_tcp_srt_max
ms
wan_egress_throughput
kbps
ingress_tcp_retransmit
wan_egress_packet_loss
egress_tcp_retransmit
wan_egress_min_delay
ms
lan_ingress_throughput
kbps
wan_egress_avg_delay
ms
lan_ingress_goodput
kbps
wan_egress_max_delay
ms
lan_ingress_packet_loss
wan_egress_jitter
ms
lan_ingress_min_delay
ms
quality_ingress
010
lan_ingress_avg_delay
ms
quality_egress
010
lan_ingress_max_delay
ms
mos_ingress
05
lan_ingress_jitter
ms
mos_egress
05
lan_ingress_sessions
number per s
ingress_wan_access_ingress
kbps
lan_egress_throughput
kbps
ingress_wan_access_egress
kbps
lan_egress_goodput
kbps
egress_wan_access_ingress
kbps
lan_egress_packet_loss
egress_wan_access_egress
kbps
Metrics used
June 2009
Ipanema Technologies
4-101
Ipanema System
Binary and unary operators (binop and unop) consist of arithmetical, relational and logical
operators.
arithmetical operators are:
addition
multiplication
modulo
subtraction
division
negation (unary)
equal to
<
less than
<=
~=
different from
>
greater than
>=
and
not (unary)
1.
2.
3.
4.
5.
6.
or
and
< > <= >= ~= ==
+*/%
not - (unary)
A rule is validated when committed; a mistake will trigger an Error message window.
4-102
Ipanema Technologies
June 2009
Configuring services
The first area (on the left) shows the list of elements (Alarm rules and Metaviews), the second
area (on the right) shows the selected elements.
Some arrows are used to move the selected data from one area to the other.
By selecting several elements in each list, the system will create the Alarms according to
combinative selected criteria.
June 2009
Ipanema Technologies
4-103
Ipanema System
4. 11. 3. 5. Operation
Using the alarms triggered by ip|boss is achieved with external tools, according to the selected
Actions:
When an alarm is triggered or rearmed, the following information is available (in a log, an e-mail or
a trap):
Alarms are sent by pair: trigger when the first threshold is reached, rearm when the second is.
4-104
Ipanema Technologies
June 2009
Configuring services
Options.
Activation: specify how to manage the Supervision events and the Traffic alarming events.
Mail (e-mail): Supervision and/or Traffic alarming events can be mailed to a list of recipients
configured in ip|boss; it uses its own mailing command.
Trap (SNMP Trap): Fault management traps generated by ip|boss on Supervision and/or Traffic
alarming events are sent to configured SNMP managers.
June 2009
Ipanema Technologies
4-105
Ipanema System
You can manage the Supervision events. They consist of an alarm (log, mail or trap) in case of
system events like:
LicenseExpiration
Start
Stop
Update
Upgrade
Reboot
BeginOfDownStatus
an ip|engine is down
EndOfDownStatus
BeginOfSynchronizationLoss
EndOfSynchronizationLoss
CertificateExpiration
RestartByRecover
IpReporterManagerIsDown
IpReporterCollectorIsDown
IpReporterBrowserIsDown
IpReporterManagerIsUp
IpReporterCollectorIsUp
IpReporterBrowserIsDown
IpReporterBrowserIsUp
BeginOfNotReachableStatus
EndOfNotReachableStatus
MetaViewColors
BeginOfCompressDownStatus
EndOfCompressDownStatus
BeginOfUncompressDownStatus
EndOfUncompressDownStatus
BeginOfLanLinkDownStatus
EndOfLanLinkDownStatus
BeginOfWanLinkDownStatus
EndOfWanLinkDownStatus
Events (ip|engines are identified with Alias, IP Address and Domain name)
You can manage the Traffic alarming events. They consist of an alarm (log, mail or trap) in case
of an alarm triggered or rearmed (see CONFIGURING ALARMING above).
4-106
Ipanema Technologies
June 2009
Configuring services
Mail:
Supervision events:
Enable: to send e-mails on Supervision events,
Disable: not to send e-mails on Supervision events.
Traffic alarming events:
Enable: to send e-mails on Alarming events,
Disable: not to send e-mails on Alarming events.
Trap:
Supervision events:
Enable: to trap the Supervision events,
Disable: not to trap the Supervision events.
Traffic alarming events:
Enable: to trap the Alarming events,
Disable: not to trap the Alarming events.
June 2009
Ipanema Technologies
4-107
Ipanema System
Subject: ip|boss, the Origin (see table above) and the alarm type,
Alarm timestamp (time when alarm was detected),
description: optional comments on the alarm.
The Origin and Type fields are included in the subject of the mail. The Description field is included
into the body of the mail. The Field format is <Domain><Type><Origin><Events>.
Mail examples:
Object : HMS : ip|boss - OSS - Cold Start
Date : 26/03/02 13:42:42 Paris, Madrid
From: ipboss@ipanematech.com
To: support@ipanematech.com
ip|boss System has been started by DOC on 26/03/2002 at 13:43:47.
Configuration file is: C:\program files\server\domains\HMS\config\__active__.ipmconf.
Object : HMS : ip|boss - OSS - Stop
Date : 26/03/02 13:43:52 Paris, Madrid
From: ipboss@ipanematech.com
To: support@ipanematech.com
ip|boss System and ip|engine have been stopped by DOC on 26/03/2002 at 13:45:11.
Object : HMS : ip|boss - ip|engine - End of ip|fast down status
Date : 26/03/02 14:06:25 Paris, Madrid
From: ipboss@ipanematech.com
To: support@Ipanematech.com
ip|fast is up on following ip|engine on 26/03/2002 at 14:07:43 : - HQ (192.169.0.100)
4-108
Ipanema Technologies
June 2009
Configuring services
June 2009
Ipanema Technologies
4-109
Ipanema System
User:
4-110
Ipanema Technologies
June 2009
Configuring services
User window
This window contains input fields:
Functions
Rights
System Administration
Users
Automatic reporting
Security
Service activation
Supervision
ip|engines status
Supervision map
Log file
Options (Mail, SNMP trap)
Helpdesk
Maps
Discovery
Real time flows
Reporting
Metaviews
ip|reporter (reports)
Alarming
June 2009
Ipanema Technologies
4-111
Ipanema System
Application provisioning
Users Subnets
Applications
ToS (type of service)
User Class
QoS profile
LTL (local traffic limiting)
System provisioning
ip|engines
Topology Subnets
WAN access
Coloring
ip|sync
Tools (upgrade, script, reboot, security status)
User Profile
4-112
Ipanema Technologies
June 2009
Configuring services
1. The procedure (steps 1 to 5) is similar to the procedure of the second level, except that the
customer selects and defines a passphrase in Security/Certificate Generation window.
June 2009
Ipanema Technologies
4-113
Ipanema System
2. Configure the associated ip|engines. THE SAME PASSPHRASE MUST BE USED for the
ip|boss and the ip|engine to allow the SSL connections between ip|boss and ip|engine. This
passphrase should be configured on all ip|engines of the Domain.
3. Before using this command, check the system Administrator to obtain the same
passphrase as ip|boss.
Command usage:
sslpassphrase
usage: sslpassphrase set
sslpassphrase reset
Copyright (c) Ipanema Technologies 2000-2005
Set the passphrase:
sslpassphrase set
Enter old SSL passphrase:
Enter new SSL passphrase: *******************
Confirm new SSL passphrase: ******************
Passphrase has been changed
Do you want to restart HTTP Server with new passphrase now [y/n]?
y
Security.
step 1) defines the certificate name. Under this name, 4 files are generated:
the private key: <alias>.isk (Ipanema Server Key) in the Security directory
(~/ipboss/server/domains/<Domain Name>/Security). If a passphrase was provided,
the key has been encoded with the passphrase in the file,
The same passphrase should be also entered on all ip|engines of the
Domain.
4-114
step 2) defines the algorithm (encoding mode or not) used for communication encryption
between ip|boss and ip|engines,
Ipanema Technologies
June 2009
Configuring services
Certificate group box with the Name: name (without extension) of the key/certificate,
Key group box with:
the field Size: choice of the key size: 512, 1024 (by default), 2048,
the field Passphrase: to enter the passphrase. The selection displays the Security
Generation dialog box.
If used, the same passphrase must be used for ip|boss and all the
ip|engines of the Domain.
June 2009
Ipanema Technologies
4-115
Ipanema System
Configuration window
The configuration specifies to ip|boss which certificate of the Security directory to use and which
algorithm to associate in SSLv3 with RSA authentication. This window defines the encryption
applied to the communications.
The window contains:
4-116
Certificate group box with the Name: name (without extension) of the key/certificate to choose
in the drop-down list. With this name, ip|boss finds the .isk, .isc, .isk and .icc files.
Algorithm group box: click in the corresponding case (Selection) to select the encryption
algorithms to be applied between ip|boss and the ip|engines.
The algorithms are listed in security level order, NULL SHA is selected by default.
Ipanema Technologies
June 2009
Connection screen
June 2009
Ipanema Technologies
5-1
Ipanema System
Create
Set
Delete
Then the resource is granted to the first user that attempts the operation and a message is sent to
the other users to inform them that the resource is busy.
Thus, the second or other user can:
Abort the operation and try later when the resource is available
OR
Preempt the resource.
When the resource is preempted by a user then the first used is automatically disconnected.
A resource is released when the update operation is made by the user.
On the Java client, select the File menu, then the Quit option.
A dialog box appears for confirmation. If changes were made without being saved, it tells you.
5-2
If you select Yes : you quit the client application but the ip|boss server is still processing.
However, modifications will be lost if you do not save or update the configuration.
If you select No : you stay in the client application.
Ipanema Technologies
June 2009
5. 2. SUPERVISION
5. 2. 1. ip|boss main window (web client)
June 2009
Ipanema Technologies
5-3
Ipanema System
Indicator
lights
Service
status
Agent status
Causes
Discovery
Connection
Grey
Yellow
off or status
not available
on
No Discovery in process or
status is not available
Discovery in process
Limiting
Connection
Grey
off or status
not available
Yellow
on
Green
on
Red
on
Green
on
Red
on
ip|boss
Connection
License
SNMP
agent
Green
on
Red
on
Green
on
Red
on
Green
on
Yellow
on
ip|engines
Reachable
5-4
Ipanema Technologies
June 2009
overload
Synchronized
Red
on
Grey
off
Grey
off
No ip|engine is overloaded
Red
on
Green
on
Yellow
on
Synchronization in progress,
temporary synchronization
loss
Red
on
Synchronization in progress,
temporary synchronization
loss or server not available
Grey
off or status
not available
Indeterminate
ip|reporter
Database
server
June 2009
Green
on
Yellow
on
Synchronization running
between ip|boss and
Infovista
Grey
off
Red
on
Green
on
Yellow
on
Ipanema Technologies
5-5
Ipanema System
Red
on
Grey
off
Green
on
Yellow
on
Red
on
Grey
off or status
not available
Services
ip|true
ip|fast
ip|xcomp
Compress
ip|xcomp
Decompress
5-6
Green
on
Yellow
on
Red
on
Grey
off or status
not available
Green
on
Yellow
on
Red
on
Grey
off or status
not available
Green
on
Yellow
on
Ipanema Technologies
June 2009
ip|xtcp
ip|xapp
Red
on
Grey
off or status
not available
Green
on
Yellow
on
Red
on
Grey
off or status
not available
Green
on
Yellow
on
Red
on
Grey
off or status
not available
Status information
June 2009
Ipanema Technologies
5-7
Ipanema System
Domain window
5-8
For each Domain, a synthesis of the status of the ip|engines, measurement (ip|true),
optimization (ip|fast), compression and decompression (ip|xcomp) and synchronization
(ip|sync) is displayed, as well as the total throughput on the Domain and the total number of
active flows.
Ipanema Technologies
June 2009
ip|engine Status.
June 2009
Ipanema Technologies
5-9
Ipanema System
CPU (%): ip|engine load average during the last collect period,
Satellites: number of satellites seen and used for synchronization,
Source: synchronization source (GPS or ITP (Ipanema Time Protocol)),
Server: name of the synchronization server or n/a (not available),
LAN status: LAN interface status of ip|engine:
up: Ethernet interface is link Up,
down: Ethernet interface is link Down.
5-10
Ipanema Technologies
June 2009
June 2009
Ipanema Technologies
5-11
Ipanema System
CPU (%): ip|engine load average during the last collect period,
Satellites: number of GPS satellites seen and used for the time synchronization,
Version : ip|agent software version and type release of the ip|engine,
Source: synchronization source (GPS or ITP (Ipanema Time Protocol)),
Server: name of the synchronization server on n/a (not available),
Offset (ms): estimated synchronization offset from GPS and ITP server (time difference
between synchronizing and synchronized units),
Delay (ms): average round trip delay between the ip|engine and ITP server,
Frequency (ppm): local oscillator free running frequency difference with the synchronization
source,
LAN status: LAN interface status of ip|engine:
up: Ethernet interface is link Up,
down: Ethernet interface is link Down,
LAN (detected type): Ethernet current state of the LAN interface of ip|engine (it should be
compatible with the previous field):
auto, 10HD, 10FD, 100HD, 100FD, 1000FD,
LAN (received bytes): number of bytes received on the LAN interface of the ip|engine,
LAN (sent bytes): number of bytes sent on the LAN interface of the ip|engine,
LAN (received packets): number of packets received on the LAN interface of the ip|engine,
LAN (sent packets): number of packets received on the LAN interface of the ip|engine,
LAN (collisions): number of collisions on the LAN interface of the ip|engine,
LAN (error frames) : number of frames error on the LAN interface of the ip|engine,
WAN status: WAN interface status of the ip|engine:
up: Ethernet interface is link Up,
down: Ethernet interface is link Down,
WAN (configured type): Ethernet configuration of the WAN interface of the ip|engine:
auto, 10HD, 10FD, 100HD, 100FD, 1000FD,
WAN (detected type): Ethernet current state of the WAN interface of the ip|engine (it should
be compatible with the previous field and with the LAN detected type):
auto, 10HD, 10FD, 100HD, 100FD, 1000FD,
5-12
Ipanema Technologies
June 2009
WAN (received bytes): number of bytes received on the WAN interface of the ip|engine,
WAN (sent bytes): number of bytes sent on the WAN interface of the ip|engine,
WAN (received packets): number of packets received on the WAN interface of the ip|engine,
WAN (sent packets): number of packets received on the WAN interface of the ip|engine,
WAN (collisions): number of collisions on the WAN interface of the ip|engine,
WAN (error frames): number of frame errors on the WAN interface of the ip|engine,
Measure (diagnostics): last diagnostic message of ip|true of the ip|engine (Alarm in the
real-time flows list is at yes):
OutOfTicket: there are no more up tickets,
OutOfBuffer: the driver is overloaded,
WanOverload: the packets received by the ip|engine on its WAN interface are more
than it is capable of handling,
TooManyFlow: the maximum number of sessions has been reached (depends on the
ip|engine range),
PktOverload: Ethernet RX overrun,
CPUOverload: CPU overrun,
LanIntfDown: the LAN interface of the ip|engine is down,
WanIntfDown: the WAN interface of the ip|engine is down
OutOfAppCnx: the maximum number of sessions of the application recognition syntax
engine has been reached.
Optimization (diagnostics) : last diagnostic message of ip|fast of the ip|engine (Alarm in the
real-time flows list is at yes):
ip|fast unreachable from ip|true: ip|fast is not working (transitory state),
ip|engine set in parallel mode: ip|fast was started on an ip|engine set in parallel mode,
current state is xxxx (where xxxx can be Initial, Configuring, Configured, Stopping,
Resetting or Unknown): ip|fast has not been started while it should have been; ip|true
tries to start it until it succeeds (transitory state).
June 2009
Ipanema Technologies
5-13
Ipanema System
Supervision maps.
the map itself, with a square for each ip|engine, the size depends on the ip|engine hardware
model, and a color in order to give a quick synthetic view of the supervision status:
Red: when Status is down (ip|engine not reachable), or when one of the following
functions: Measure, Optimization, Compression, Decompression is down, not
started, not configured or not updated (after three trials of update),
Yellow: when not Synchronized, and/or Overloaded and/or Updating (update of
configuration running),
Green: all status are OK (Status, Measure, Optimization if used, Compression if used,
Decompression if used and Synchronization).
5-14
: to consult the detailed supervision status (refer to the supervision details above),
Ipanema Technologies
June 2009
By moving the mouse on the square, a contextual text shows the supervision status:
June 2009
Ipanema Technologies
5-15
Ipanema System
5-16
Ipanema Technologies
June 2009
Reboot window
This window contains:
June 2009
Ipanema Technologies
5-17
Ipanema System
5. 3. 2. Scripts
Operating procedure table: Management
This tool is to be used with the Ipanema Technologies Support.
In the System provisioning Toolbar, select
Scripts window
The window comprises the input fields:
The result files are given in a tree structure where the root is
~/salsa/ipboss/server/domains/<domain_name>/temp/Ipanema-dump/<date-time>
format: yymmdd-hhmm).
Three sub-directories are created for each Launch:
5-18
(date-time
ipboss: contains the current configuration and the log file of ip|boss,
Ipanema Technologies
June 2009
ipengine: contains the result file (format: <alias or @ip address of the ipengine>.ipmres),
script: contains the used script file. This file is encoded (.ipmscp). An ipengine.txt is associated
to the script file and contains the list of dumped ip|engines (alias+@ip).
The user can send these directories in a zipped file (by E-mail or FTP to Ipanema Technologies
support (support@ipanematech.com)).
Different script files are available. The main ones are :
default.ipmscp: dumps all information in the ip|engine, reserved for the support,
flows.ipmscp: dumps all flows in the ip|engine,
gpsinfo.ipmscp: dumps the synchronization information about the GPS receiver,
ipconfig.ipmscp: dumps information about the IP and Ethernet settings of the ip|engine,
check iptrue.ipmscp: dumps information about ip|true, reserved for the support,
check ipfast.ipmscp: dumps information about ip|fast, reserved for the support,
check ipxcomp.ipmscp: dumps information about ip|xcomp, reserved for the support,
check itp.ipmscp: dumps information about ip|sync synchronization, reserved for the support,
restart iptrue.ipmscp: restarts ip|true agent, reserved for the support,
restart ipfast.ipmscp: restarts ip|fast agent, reserved for the support,
restart ipxcomp.ipmscp: restarts ip|xcomp agent, reserved for the support,
restart itp.ipmscp: restarts ip|sync agent, reserved for the support,
process.ipmscp: dumps information about the process running, reserved for the support.
June 2009
Ipanema Technologies
5-19
Ipanema System
5. 4. IP|BOSS LOGS
Operating procedure table: Management
In the Supervision Toolbar, select
Log.
Log window
This window contains:
5-20
the list of Supervision events (on ip|engines, ip|reporter server....) with a time stamping,
the list of Traffic alarming events (on Metaviews) with a time stamping (only if it has been
activated in Options / Activation).
Ipanema Technologies
June 2009
Service activation.
June 2009
Ipanema Technologies
6-1
Ipanema System
in case of failure of ip|boss or of the server, at the next start of ip|boss, the session
will be on the same state (automatic restart if it was started, or stop if it was stopped).
6. 1. 2. Stopping a session
Operating procedure table: ip|true service, ip|fast service, ip|coop service, ip|xcomp service,
ip|xtcp service, ip|xapp service, smart|path service, smart|plan service.
A session can be stopped on the ip|engines by the Toolbar,
Service activation.
Stopping a session will stop all functions of the system (ip|true (measurement), ip|fast,
ip|xcomp, ip|coop, ip|xtcp, ip|xapp, smart|path, smart|plan).
Check that the indicator lights on the status zone turn to black.
6-2
Ipanema Technologies
June 2009
Using services
User settings.
June 2009
Ipanema Technologies
6-3
Ipanema System
A: means that the modifications made by a user of the service are automatically applied,
U: means that the user has to use Update to apply the modifications made.
Table Dynamically modifying a session: ip|true service, ip|fast service, ip|xcomp service,
ip|coop service, ip|xtcp service, ip|xapp service.
Components
Services
Dynamic
Login
Login/User Settings
Update
Help
User
Automatic reporting
Security/Generation
Security/Configuration
ip|engines
Topology Subnets
WAN access
Coloring
ip|sync
Other
Manager
System
System
Administration
System
provisioning
Tools/Software
grade
6-4
up-
Tools/Reboot
Tools/Script
Tools/Security status
Ipanema Technologies
June 2009
Using services
Components
Services
Dynamic
Other
Service activation
Enable ip|engines
Disable ip|engines
Enable ip|fast
Disable ip|fast
Enable ip|xcomp
Disable ip|xcomp
Enable ip|coop
Disable ip|coop
Enable ip|xtcp
Disable ip|xtcp
Enable ip|xapp
Disable ip|xapp
ip|engines status
Supervision map
Log
Options/Activation
Options/Mail
Options/Trap
User subnets
Applications
TOS
User Class
QoS profile
Maps
Realtime
Discovery
Metaview
ip|reporter
Alarming
Supervision
Application
provisioning
Helpdesk
Reporting
Whether for a Start or an Update, the configuration is checked to inform the user that resources
(Domains and services) are referenced even though they are not configured in the directories or
dictionaries. As long as the check is not OK, no Start or Update operation can be performed on
ip|engines. The check operation accepts configurations with empty dictionaries or directories.
June 2009
Ipanema Technologies
6-5
Ipanema System
6. 3. 1. Update procedure
Operating procedure table: ip|true service, ip|fast service, ip|coop service, ip|xcomp service,
ip|xtcp service, ip|xapp service, smart|path service, smart|plan service, ip|sync service.
In the Toolbar, select
Update.
If some ip|engines do not apply the new configuration, ip|boss automatically reconfigures these
ip|engines. The status indicator is yellow and shows either:
ip|boss systematically sends a complete configuration file to the ip|engines of the Domain.
6. 3. 2. Transition
In the ip|engines reconfiguration phase, some ip|engines must measure, optimize and compress
on the basis of different configurations. In addition, as an SNMP agent must take the new
configuration into account (after Update), it may receive measurement results for the previous
configuration. Different problems can arise:
For suppressed dictionary entries, reports on the previous configuration (i.e. with old aggregate
application or TOS values) are automatically classified in other by ip|boss. There is no retroactive
effect on measurement data that may have been saved in ip|reporter.
For suppressed subnet directory entries, reports on the previous configuration (i.e. with old subnet
values) are automatically rejected by ip|boss.
For suppressed ip|engine directory entries, reports on the previous configuration (i.e. with old
ip|engine values) are automatically rejected by ip|boss.
For suppressed ip|engine directory entries, the ip|engines that have disappeared are stopped.
However, the stop signal may not reach the ip|engines concerned after 10 attempts spaced out
over the recovery interval configured in the system, the stop operation is abandoned by the
manager and the user is informed.
6-6
Ipanema Technologies
June 2009
Using services
6. 4. SERVICE ACTIVATION
6. 4. 1. ip|true (measurement)
Operating procedure table: ip|engines Enabled, ip|engines Disabled
Stopping ip|true will stop all other functions of the system (ip|fast, ip|xcomp, ip|coop,
ip|xtcp, ip|xapp, smart|path, smart|plan). Refer to the section Stopping a session.
The measurement mechanisms are designed to measure precisely all flows crossing the
ip|engines and to provide comprehensive metrics (volume and quality).
ip|true is enabled, if:
Administrative stare: enable is checked in the ip|engines creation window (Services frame):
June 2009
Ipanema Technologies
6-7
Ipanema System
Applications
User Subnets
QoS profiles
Metaviews
User Classes
Reports
TOS
6-8
Ipanema Technologies
June 2009
Using services
6. 4. 2. ip|fast (optimization)
Operating procedure table: optimization Enabled, optimization Disabled
The optimization mechanisms are designed to find the best compromises to reach QoS objectives
and take express customer requirements into account:
QoS objectives are expressed in terms of "physical" constraints (delay, jitter, loss rate, etc.),
customer policies are expressed in terms of classes, defining relative traffic criticality.
ip|fast: on:
June 2009
Ipanema Technologies
6-9
Ipanema System
6-10
Applications
User Subnets
QoS profiles
LTL
User Classes
Coloring
TOS
WAN access
Ipanema Technologies
June 2009
Using services
If ip|fast is not checked for a virtual ip|engine, the latter will be optimizing (as long as
ip|fast is enabled globally), as it is the remote physical ip|engines which actually do
it, but without ip|coop (that is, without the remote physical ip|engines cooperating
to optimize the site with the virtual one).
ip|coop: on.
June 2009
Ipanema Technologies
6-11
Ipanema System
If ip|coop is not enabled, virtual ip|engines will still measure and optimize the traffic,
with the following restriction:
measure: the traffic will be measured and reported exactly the same,
optimization: the traffic will be optimized with no Remote Coordination Group, each
physical ip|engine managing the flows to and from the unequipped sites on its own,
without coordination with the other physical ip|engines communicating with this site.
6-12
Ipanema Technologies
June 2009
Using services
6. 4. 4. ip|xcomp (compression)
Operating procedure table: compression Enabled, compression Disabled
The compression mechanisms are designed to use as much bandwidth as possible, but still taking
the optimization parameters into account.
ip|xcomp is enabled, if:
June 2009
Ipanema Technologies
6-13
Ipanema System
ip|engines
6-14
User Classes
Ipanema Technologies
June 2009
Using services
ip|xtcp: on:
June 2009
Ipanema Technologies
6-15
Ipanema System
ip|engines
6-16
User Classes
Ipanema Technologies
June 2009
Using services
ip|xapp: on:
ip|engines
June 2009
Ipanema Technologies
6-17
Ipanema System
6. 4. 7. smart|plan
Operating procedure table: Smart Planning Enabled, Smart Planning Disabled
Ipanema Technologies Smart planning reports provide easy-to-use data for Capacity Planning
optimization. Smartplanning generates very high added value data enabling a complete analysis
for each network access of the relationship between Traffic (resource) and delivered service
level (results). Using this automatically generated data, it is immediately possible to identify if the
access link is under-provisioned or over-provisioned in regard of the expected service level per
applications business criticality.
smart|plan is enabled, if:
smart|plan: on:
6-18
Ipanema Technologies
June 2009
Using services
6. 5. HELPDESK
6. 5. 1. Link supervision
Operating procedure table: ip|true service, ip|fast service, ip|xcomp service, ip|coop service,
ip|xtcp service, ip|xapp service.
In the Helpdesk Toolbar, select
Link supervision.
: to open the real time monitored flows list for the selected sites link (highlighted),
in both directions, in a new tab,
: to open the real time monitored flows list for the selected sites ingress link
(highlighted), in a new tab,
: to open the real time monitored flows list for the selected sites egress link
(highlighted), in a new tab,
: to switch between average and worst AQS (color) in the Usage bars,
June 2009
and
Ipanema Technologies
6-19
Ipanema System
Table columns description (the order is the default one; it can be changed using the Display menu):
Site
if only one WAN access is declared on the ip|engine monitoring the link,
the name of the Site is the name of the ip|engine
if several WAN accesses are declared, the name of the Site is the
association of the name of the ip|engine with the identifier of the link
(NAP Id)
Ingress Usage
percentage of used ingress bandwidth during the last minute; the color of
the bar indicates the quality (AQS, see below): green = good, yellow =
average, red = bad, grey = not computed
Ingress AQS
Green: 10 points
Yellow: 5 points
Red: 0 point
The AQS can take any value in between 0 and 10 (e.g. 9.87), and can be
interpreted like this:
6-20
Egress Usage
percentage of used egress bandwidth during the last minute; the color of
the bar indicates the quality (AQS, see below): green = good, yellow =
average, red = bad, grey = not computed
Egress AQS
Application Quality Score of the egress link (AQS definition: see Ingress
AQS above)
Ipanema Technologies
June 2009
Using services
Columns that can be added through the Display / Choose column menu:
ip|engine
napId
Network Access Point identifier: when only one WAN access is declared on
a Site, it will always be 1; when several WAN accesses are declared (up to
three), the napId identifies them (the value, 1, 2 or 3, corresponds to WAN
access 1, WAN access 2 and WAN access 3 respectively, as declared
in the ip|engine creation window)
June 2009
Ipanema Technologies
6-21
Ipanema System
6. 5. 2. Real-Time flows
During a session, the operator can analyze real-time flows (optimized or not), via the Helpdesk
Toolbar,
Real-time.
Real-time.
a table, with each active flow shown on a separate line. A flow becomes active and is shown in
the window as soon as a packet belonging to it is detected during the session,
the following buttons:
: to show all the flows (active and past) / the active flows only,
The color of the first column indicates the quality (AQS, see below): yellow = average, red = bad.
The parameter (delay, jitter, loss, etc.) that triggered an average or a bad quality is also highlighted
with the same color, so that one can easyly find which parameters objective was not met (yellow)
or which parameters maximum was exceeded (red).
Table columns description (the order is the default one; it can be changed using the Display menu):
6-22
Ipanema Technologies
June 2009
Using services
The same metrics are used in the reports, with the same definitions. Yet, in the
reports, other metrics and symbols are also used: you can find their definitions in 7.3.4.
Definitions.
Last updated
Ingress
Egress
Source
Destination
Application
application name
TOS/CP
TOS name
User class
Criticality
Compression
AQS
Green: 10 points
Yellow: 5 points
Red: 0 point
The AQS can take any value in between 0 and 10 (e.g. 9.87), and can be
interpreted like this:
LAN Throughput
June 2009
level 3 flow, all IP packets (in kbps) sent on upstream side (measured on
the LAN port of the source ip|engine)
Ipanema Technologies
6-23
Ipanema System
LAN Goodput
rate of instantaneous loss (in %) (measured between the LAN port of the
source ip|engine and the LAN port of the destination ip|engine)
LAN Jitter
delay variation (in ms) (measured between the LAN port of the source
ip|engine and the LAN port of the destination ip|engine)
LAN Sessions
WAN Throughput
level 3 flow, all IP packets (in kbps) sent on upstream side (measured on
the WAN port of the source ip|engine)
rate of instantaneous loss (in %) (measured between the WAN port of the
source ip|engine and the WAN port of the destination ip|engine)
WAN Jitter
delay variation (in ms) (measured between the WAN port of the source
ip|engine and the WAN port of the destination ip|engine)
Accuracy
Alarm
this field indicates, when at yes, the presence of an alarm on the upstream
ip|engine. Check its status for further information. In case of alarm, the
correlation records are ignored.
This table is refreshed about every minute (according to the
ip|engine collect period option) if it is not frozen.
SRT Min
6-24
Ipanema Technologies
June 2009
Using services
SRT Avg
SRT Max
RTT Min
RTT Avg
RTT Max
TCP Retransmission
June 2009
Ipanema Technologies
6-25
Ipanema System
The graph window contains four tabs, and each tab is made of 4 graphs, displayed simultaneously:
Tab
Graphs
Additional information
LAN
Delay (ms)
Jitter (ms)
Throughput (kbps)
Delay (ms)
Jitter (ms)
Throughput (kbps)
Avg. sessions
Throughput (kbps)
SRT (ms)
RTT (ms)
Retransmission
Throughput (kbps)
WAN
LAN/WAN
TCP
6-26
Ipanema Technologies
June 2009
Using services
Example of tab
In case of optimization and/or compression, the differences between LAN and WAN
values might be very different.
Not all graphs are displayed for a virtual ip|engine.
If the upstream or downstream ip|engine is not synchronized, the delay, jitter and packet
loss are not displayed.
June 2009
Ipanema Technologies
6-27
Ipanema System
6. 5. 3. Discovery
Operating procedure table
In the Helpdesk Toolbar, select
Discovery.
The indicator light Discovery becomes yellow in the Main window when the Discovery is started.
The discovery function consists in creating one discovery agent for one ip|engine (one agent
maximum per ip|engine). According to the configuration rules this discovery agent will send to
ip|boss:
detailed by:
Discovery window
In addition to the other windows, some extra buttons allow to:
: start the selected discovery agent on the ip|engine,
: stop the selected discovery agent on the ip|engine,
6-28
Ipanema Technologies
June 2009
Using services
ip|engine : selects the ip|engine (site) on which the Discovery agent will be running,
Name : name of the Discovery agent (not mandatory),
Network filter: a set of parameters in order to filter the information sent by the Discovery agent:
Local : radio button (according to the choice, the following fields will be enabled),
user subnet: to select a user subnet declared in the configuration,
prefix/length: to specify a subnet address not in the configuration file (for
example a host),
Name: selects in the drop-down list the user subnet in the configuration,
prefix: enter the subnet X.X.X.X,
length: subnet mask associated to the prefix (integer between 0 and 32),
out of local config.: check box; if checked, allows to display the traffic which does not
belong to the local configuration only (e.g. in transit, locally rerouted, etc.), that is, which
is not measured by the ip|engine (nor reported, except in volume in the report SA Site throughput); if the box is unchecked, all the traffic that crosses the ip|engine is
displayed,
Remote: radio button (according to the choice, the following field will be enabled),
ip|engine: to select a destination ip|engine,
user subnet: to select a destination user subnet declared in the configuration,
prefix/length: to specify a user subnet address not in the configuration file (for
example a host),
Name: selects in the drop-down list the ip|engine or user subnet in the configuration,
prefix: enter the subnet X.X.X.X,
length: subnet mask associated to the prefix (integer between 0 and 32),
June 2009
Ipanema Technologies
6-29
Ipanema System
Application filter: a set of parameters in order to filter the information sent by the Discovery
agent in terms of applications:
Type: radio button (function of the choice, the following field will be enable):
Name: to select an application declared in the configuration,
Protocol/ports: to specify a port number or a range over the protocol TCP or
UDP.
Name: selects in the drop-down list the application in the configuration,
Protocol/ports: enter the protocol and port number or range with the following format
UDP/456, UDP/456789, TCP/456 or TCP/456789 (the port can be Out of config),
Out of config: check box, allows to discover the port number classified in other for the
application.
6-30
Ipanema Technologies
June 2009
Using services
Discovery.
Discovery window
In the Discovery agents zone, to start an agent, select the line(s) in the list and click on the Start
button
. The status indicator (on the left of the selected line(s)) becomes green.
In the Results zone, the results of the selected and started agent(s) are displayed.
The following command buttons allow to:
: export the Results zone to a text file,
: freeze the Results zone (the new result coming from the ip|engine are not updated),
According to the display parameters selected in the bottom of the Results zone:
Application: applications
hide: the detailed applications are not displayed (all applications will be merged) ,
show: the detailed applications are displayed,
Direction: sort the traffic by direction (ingress or egress) on the ip|engine where the discovery
agent is running:
Ingress: ingress traffic (LAN -> WAN),
Egress: egress traffic (WAN -> LAN),
Sorted by: this parameter defines the sort criteria for the Top N results:
Throughput: Top N by maximum throughput usage,
June 2009
Ipanema Technologies
6-31
Ipanema System
Top : this parameter defines the maximum number of entries to display in the results zone:
20,
50,
100,
The Discovery function displays the following results (the counter are cleared at each start of the
agent):
Example
Meaning
Recognized by
When
HTTP (http)
syntax engine
on the
session start
(handshake)
HTTP (tcp)
declared or
well-known port
on the
session start
(handshake)
IMAP
(established)
declared or
well-known port
TCP/0-19999
TCP/19999-0
not recognized
6-32
Ipanema Technologies
June 2009
Using services
6. 5. 4. Helpdesk maps
Operating procedure table: ip|true service, ip|fast service, ip|coop service, ip|xcomp service,
ip|xtcp service, ip|xapp service.
In the Helpdesk Toolbar, select
Topology map,
Applicative map or
VoIP map.
Map example
The maps show in a glance the behavior of the whole network. These graphical views use squares
with:
They are divided in main blocks and sub-blocks inside. Those blocks depend on the type of map
(see below) and level of zoom.
By moving the mouse on the square, a contextual text shows the description of the blocks:
This window contains the map itself plus the following buttons:
: no access,
: to get the list of flows corresponding to the square area in the real time window,
June 2009
Ipanema Technologies
6-33
Ipanema System
Topology map: to show the behavior with a topology point of view (sites, sites to sites),
Applicative map: to show the behavior with a criticality, User class point of view,
6. 5. 4. 1. Topology Map
By clicking on
Zoom levels:
Top level: at the first level, the map displays the full traffic with a main block per source (ingress)
ip|engine and a sub-block per destination (egress) ip|engine.
Zoom in level 1: by zooming in a Site block, you can see a sub-block per User class from
site to site.
Zoom in level 2: by zooming in a User Class block, you can see a sub-block from site to site
by User Class.
6. 5. 4. 2. Applicative Map
By clicking on
Zoom levels:
6-34
Top level: at the first level, the map displays the full traffic with a main block per criticality and
a sub-block per User Class.
Zoom in level 1: by zooming in a criticality block, you can see a sub-block for all User Classes
in the selected criticality level and the ingress site for each User Class.
Zoom in level 2: by zooming in a User Class block, you can see a sub-block for all ingress
sites in the selected User Class, and the egress sites for each ingress site.
Zoom in level 3: by zooming in a Site block, you can see a sub-block for the selected User
Class between ingress site and egress site.
Ipanema Technologies
June 2009
Using services
6. 5. 4. 3. VoIP Map
By clicking on
Unlike the other maps, the VoIP map does not show the AQS, but the MOS (mean opinion score)
of the voice calls.
MOS Definition
Zoom levels:
Top level: at the first level, the map displays the full traffic with a main block per source (ingress)
ip|engine and a sub-block per destination (egress).
Zoom in level 1: by zooming in a Site block, you can see a sub-block from site to site, and
per Codec for each site.
Zoom in level 2: by zooming in a Codec block, you can see a sub-block from site to site by
Codec.
June 2009
Ipanema Technologies
6-35
Ipanema System
6. 6. HELP
In the Toolbar, select
Help:
Help window
This window contains the documentation of Ipanema System.
6-36
Ipanema Technologies
June 2009
7. 1. MIB ACCESS
7. 1. 1. MIB
The description file is available in the directory of ip|boss:
~/salsa/ipboss/server/interface/ipanema-technologies.mib
~/salsa/ipboss/server/interface/ipanema-technologies-notifications.mib
7. 1. 2. SNMP
Measures can be used via a MIB access thanks to an SNMP agent included in the ip|boss software.
The UDP port used by this agent must be configured, Domain per Domain (a different port must
be declared for each Domain), in ip|uniboss.
Access to the agent is read-only with SNMPv2c protocol. The Community name is public (default
value, can be configured by user).
The SNMP agent instantiates the system and SNMP groups as well as a private MIB.
The SNMP agent is updated every Short reporting period (as defined in the Domain configuration
see chapter 3).
June 2009
Ipanema Technologies
7-1
Ipanema System
7. 2. IP|REPORTER
This section describes the reporting system, ip|reporter, made by Ipanema Technologies.
7. 2. 1. Ipanema Architecture
The Ipanema solution architecture is composed of the following system elements:
ip|boss is the centralized management software for the Ipanema performance management
system which runs on a standard Solaris or Windows platform. Through the ip|boss, business
objectives are communicated to ip|engines and measurement data are collected.
ip|reporter is a full-service report generating utility. It provides a global view of service levels
for each application, as well as detailed, metrics based reports for problem diagnostics.
The ip|reporter is a reporting tool powered by InfoVista and based on OEM agreement.
InfoVista can operate with real-time data or deferred-time data. Real time, such as SNMP data,
is retrieved from the ip|boss at regular intervals by polling the resource and requesting it for
specific information about the behavior of the resource. These data give up to date information
about IS behavior.
Deferred-time data is external to the SNMP world. It has its source in existing log files (a web
site log file, for example) or databases. It is batch-loaded onto the InfoVista server as some time
after it was generated. InfoVista uses these data to calculate Indicators in the same way as it
handles real time data. And, in fact, when the data is displayed on a report, the origin of the
resource data is totally transparent to the user.
7-2
SNMP (System MIB) Collect of measurement. Interfaced with SNMP agent of ip|boss.
Ipanema Technologies
June 2009
Ipanema architecture
June 2009
Ipanema Technologies
7-3
Ipanema System
7-4
Ipanema Technologies
June 2009
7. 2. 3. Terms
7. 2. 3. 1. The Instance
Each monitored resource in the network is represented by an Instance object (equivalent to a
Metaview in ip|boss) . An Instance can represent any logical or physical element in the network
such as an ip|engine source, an ip|engine destination, a subnet source, a subnet destination, an
application, a Key A, a Key B, a User Class, a criticality.
The Instance consists of values and identify and characterize the resource (for example, the alias
for an application). These characteristics are called Property and the values assigned to them are
called Property Values.
The data is displayed on a Graph. The Instance is mapped to the Graph via a report.
7. 2. 3. 2. The Vista
You create each Instance object from a template object called the Vista. The Vista indicates which
Properties each Instance should have. You can create any number of Instances from the same
Vista. In this way, you define each type of equipment only once and when you create Instances of
this equipment, you simply supply the values of the Properties.
InfoVista is installed with a number of standard, pre-configured Vistas which allow you to get up
and running immediately.
For example:
the Vista SNMP node has the Properties snmprd (SNMP community read) and snmpwr (SNMP
community write).
Rules can be defined to create relationships between Vistas. They are not immediately
visible in the object model but they are exploited by several Vistas you use. For example,
one of the standard Rules states that All Routers are SNMP nodes. The result is that
the Vista Router automatically inherits all the Properties of the Vista SNMP node as
well as its own intrinsic Properties.
7. 2. 3. 3. The Indicator
An Indicator is a measurement. It tells us something about the operation of a resource. Examples
are data traffic or quality of service. InfoVista calculates the values of Indicators from the source
data, which it collects from the monitored resource.
Standard, pre-configured Indicators exist for the most common situations that you encounter (and
for some of the more difficult ones, too).
7. 2. 3. 4. The Report
An InfoVista report shows one or more Graphs and possibly some decorative text or bitmaps. Each
Graph shows the values of a set of Indicators for a set of Instances (the monitored resources).
June 2009
Ipanema Technologies
7-5
Ipanema System
You can also create sub-folders, if necessary, to organize your working environment.
7. 2. 3. 7. Libraries
A Library (supplied by InfoVista or third parties, or created by you) is used to group together objects
such as Vistas, Indicators, etc. in order to obtain logical units.
7-6
Ipanema Technologies
June 2009
Manager service
Collector service
or
Client-Server communication failure
Browser service
Which may be displayed after trying to connect to a server, means that the InfoVista
server has not started correctly. If you have a problem, refer to chapter 1 section
Troubleshooting.
June 2009
Ipanema Technologies
7-7
Ipanema System
Starting IVreport
UNIX SPECIFIC
The InfoVista software is installed in:
/opt/InfoVista/Essentials/bin (Solaris)
(The path should be included in the PATH variable)
To start the client, execute:
./ivreport &
7-8
Ipanema Technologies
June 2009
7. 2. 4. 3. Connecting to a server
After startup, the Connection dialog box is displayed. Enter the parameters requested and click on
OK.
Startup window
Server name: Name of the system running the InfoVista server or IP address. If the server is on
the same machine as the client application, leave this field blank or put the loop back address
(127.0.0.1).
Several instances of InfoVista can be installed on the same server. In this case the
syntax is the following: <instance_name>@x.x.x.x (where x.x.x.x is the IP address
of InfoVista server).
In a firewall environment, the endpoints for Manager, Collector and
Browser services can be fix. In this case the syntax is the following:
x.x.x.x:ManagerPort:CollectorPort:BrowserPort (where x.x.x.x is the IP address of
InfoVista server). The endpoints ports can be setup using ip|reporter rich client
(IVreport):
June 2009
Ipanema Technologies
7-9
Ipanema System
7-10
Ipanema Technologies
June 2009
.A
Click a
Click a
Double-click the name of an object to open the Property sheet or List view window of the object
(shortcut for Edit/Open).
June 2009
Ipanema Technologies
7-11
Ipanema System
The right-hand pane of the window displays the list of sub-objects of the object that is currently
selected in the object tree.
Double-click an object name to open the Property sheet of the object (shortcut for Edit/Open).
The tool bar contains buttons which provide shortcuts for the more frequently used menu
commands.
Open the Property sheet of the selected object (shortcut for Edit/Open).
Create a new report with the Instant Report wizard (shortcut for
Reports/Instant Report).
7-12
Ipanema Technologies
June 2009
Report viewer
Report/Periodical Refresh/Stop
Report/Periodical Refresh/Start
The report template is configured to update the data display in function of the display rate value.
File/Print While a Report is open, you can print it with this command. The report is printed
on your systems default printer.
Edit/Copy
Toggle Information Mode (not in a menu) When depressed, displays a tool tip over graphic
objects, indicating the Metric name, Vista name and acquisition rates, time span and the objects
Description attribute.
June 2009
Ipanema Technologies
7-13
Ipanema System
Use the reference Time slider to adjust the reference time of the report:
or click on the time or date, edit with the keyboard and press Enter to validate
7-14
Ipanema Technologies
June 2009
June 2009
Ipanema Technologies
7-15
Ipanema System
7. 2. 5. Reports Management
Operating procedure table: settings (automatic reporting), settings (define reports), service ip|true
(automatic reporting), service ip|true (modify reports), service ip|reporter (automatic reporting),
service ip|reporter (define reports)
The reports are managed in the ip|boss interface, thanks to ip|reporter or to the Automatic
reporting tool.
ip|boss manages the Instances creation and deletion in InfoVista according to the configuration
parameters.
ip|boss is the reference for the reports and Instances for infovista. If some reports described in
ip|boss configuration file are not present in Infovista database, then ip|boss takes in charge to
create the missing reports. At the opposite, if some reports exist (for the Domain) in Infovista
database and not in ip|boss configuration, then ip|boss takes in charge to delete these reports.
ip|reporter uses the Metaviews for the reports creation and filling.
Three kinds of reports creation are available:
7-16
ip|reporter, unitary mode: one report is created on one Metaview. This mode is to use to add a
specific report on a specific Metaview, or to create some reports that cannot be created in the
Wizard mode.
ip|reporter, automatic mode (Wizard): several reports can be created on several Metaviews in
one operation. For example: 8 given reports on all physical sites.
automatic reporting: reports are automatically created for the Domain, for all Physical sites, for
all Virtual sites or for all User classes, and will automatically be added when new Physical sites,
new Virtual sites or new User classes are created.
Ipanema Technologies
June 2009
7. 2. 5. 1. Automatic reporting
This tool allows to create reports for the Domain, for all Physical sites, for all Virtual sites or for all
User classes.
The selected reports are automatically added for existing Physical sites*, Virtual sites* and User
classes, and will be automatically added when new Physical sites*, new Virtual sites* or new User
classes are created.
* For the sites (physical or virtual), the selected reports are created only if
Auto-reporting is at yes in the ip|engine parameters.
Automatic reporting.
Domain,
Physical sites,
Virtual sites,
User classes.
Report template: drop-down list of available report templates, to choose the reports attached
to the selected tab.
June 2009
Ipanema Technologies
7-17
Ipanema System
four click boxes allow to define which time aggregation can be created for the report:
Hour,
Day,
Week,
Month.
a click box that allows to define the level of confidentiality for the report:
Public (unclicked by default):
when clicked, the reports are stored in the hour / day / week / month folders
in IVreport, and an access to the reports can be given to all users using the web
client;
otherwise, the reports are stored in the hour private / day private
/ week private / month private folders in IVreport, and the
access to the reports can be restricted, for the users using the
web client, to authorized users only (refer to the Technical note
TN-0200011-04__how_to_configure_report_access_with_VPSE2.pdf).
7-18
Ipanema Technologies
June 2009
ip|reporter.
ip|reporter window
This window contains the list of reports created on each instance with the specific parameters.
By clicking on the New button
Metaview: drop-down list of Metaviews, to choose the Metaview on which the reports will be
created.
Report template: drop-down list of available report templates, to choose the reports attached
to the selected Metaview.
4 click boxes allow to define which time aggregation can be created for the report:
Hour,
Day,
Week,
Month.
a click box that allows to define the level of confidentiality for the report:
Public (unclicked by default):
when clicked, the reports are stored in the hour / day / week / month folders
in IVreport, and an access to the reports can be given to all users using the web
client;
otherwise, the reports are stored in the hour private / day private
/ week private / month private folders in IVreport, and the
access to the reports can be restricted, for the users using the
web client, to authorized users only (refer to the Technical note
TN-0200011-04__how_to_configure_report_access_with_VPSE2.pdf).
June 2009
Ipanema Technologies
7-19
Ipanema System
ip|reporter.
ip|reporter window
7-20
Hour,
Day,
Week,
Month.
Ipanema Technologies
June 2009
a click box that allows to define the level of confidentiality for the report:
Public (unclicked by default):
when clicked, the reports are stored in the hour / day / week / month folders
in IVreport, and an access to the reports can be given to all users using the web
client;
otherwise, the reports are stored in the hour private / day private
/ week private / month private folders in IVreport, and the
access to the reports can be restricted, for the users using the
web client, to authorized users only (refer to the Technical note
TN-0200011-04__how_to_configure_report_access_with_VPSE2.pdf).
The first zone (on the left) shows the list of elements (Metaviews and Report templates) as
described in the system and managed by ip|boss, the second area (on the right) shows the
selected elements.
Some arrows are used to move the selected data from one area to another.
By selecting several elements in each list, the system will create the reports according to
combinative selected criteria.
7. 2. 5. 4. Reports Deletion
To delete some reports in the Infovista database, just suppress the reports in the list accessible by
ip|reporter. After the validation of the deletion and update of the configuration, the reports
are definitively deleted, the reports and their data cannot be accessed anymore.
It is possible to suppress several reports by selection with the keyboard.
June 2009
Ipanema Technologies
7-21
Ipanema System
7. 2. 5. 5. Update in InfoVista
After creation or deletion of reports, click on the flashing Update button
in order to update the
Infovista Database with ip|boss configuration. After you have confirmed you want to update the
configuration in ip|reporter, this step is identified by the Database LED (in the ip|reporter status
screen) in amber during the synchronization (this can last several minutes, or several hours if you
created a large number of reports at a time).
7. 2. 5. 6. Force synchronize
If InfoVista suffers a Database synchronization problem, it is possible to force the synchronization
using ip|reporters menu Actions / Force synchronize.
This function should not be used under normal circumstances. Use it only in case
of synchronization problem. A synchronization problem can be checked in the
logs, and thanks to the Database LED above (grey: an error happened during last
synchronization; red: error in the reports description; amber is a normal color during
synchronization, but it should be a temporary state: if the LED remains amber for an
abnormaly long time, this can also be due to a synchronization problem).
7-22
Ipanema Technologies
June 2009
Click OK to confirm you want to force synchronization, Cancel if you wan to abort.
June 2009
Ipanema Technologies
7-23
Ipanema System
7. 2. 5. 7. Recommended reports
Ipanema recommends that the following reports are created:
Report
Dom
Phy
Vir
UC
other
PM - Compression Evolution
PM - Compression Synthesis - UC
PM - Time Evolution
X
X
PM - Site Summary
PM - Appli. Summary (per dir.)
X
(x)
PM - Detailed per UC
(x)
SA - Site Throughput
SA - Site Summary (ingress/egress)
FI - Availability Overview
FI - Availability Evolution
where Dom stands for Domain, Phy for Physical sites, Vir for Virtual sites, UC for User classes,
and other should be created for a specific occasion only (troubleshooting...), then removed.
7-24
Ipanema Technologies
June 2009
7. 3. 1. IVreport
To open a report using IVreport, launch IVreport (default login / password are administrator /
(no password)), open the Reports tab, open the following folders: Report folders / <Domain>
/ <MetaView> / <Level of aggregation, level of confidentiality>, then double-click on the reports
name.
If the Public click box was clicked on the reports creation, it can be found in the hour / day
/ week / month folders;
otherwise, it can be found in the hour private / day private / week private / month private
folders.
June 2009
Ipanema Technologies
7-25
Ipanema System
7. 3. 2. Web client
Using the web client, the directory structure is similar, but users may not have an access to all
reports (for example, the access may be limited to the Public reports only), according to their rights
(refer to the Technical note TN-0200011-04__how_to_configure_report_access_with_VPSE2.pdf).
by selecting Folders in the drop-down list in ip|reporters main window, you can access the
reports with the following file system tree (4 hierarchical levels):
<Domain> / <type of MetaView> / <MetaView> / <time level, public/private>
7-26
Ipanema Technologies
June 2009
The second browsing method allows to navigate in the sites reports with two additional
hierarchical levels, defined by the ip|engines Navigation fields Folder name for level 1 and
Folder name for level 2: by selecting Navigation in the drop-down list in ip|reporters main
window, you can access the sites reports with the following file system tree (6 hierarchical
levels):
<Domain> / Navigation / <Folder name for level 1> / <Folder name for level 2> /
<MetaView> / <time level, public/private>
(the <type of MetaView> level disappears, as this method is valid to access the sites reports
only).
This method is very helpful on larges networks, with hundreds or thousands of sites.
In the example below, Folder name for level 1 was used to group sites per continents, and
Folder name for level 2 was used to group sites per countries. The ip|engines created without
filling those fields are grouped under the Unknown folder name:
June 2009
Ipanema Technologies
7-27
Ipanema System
Report example
On the client you can use the time slider (IVreport) or specify the date and time (both clients) to see
the previous values of each indicator. This presents you with a historical view of each resource
for any moment during the lifetime of the report.
7-28
Ipanema Technologies
June 2009
7. 3. 4. Definitions
Here is a definition of the symbols and specific metrics that are used in the reports (for the definition
of the standard metrics, such as AQS, Delay, Jitter, Loss rate, RTT, SRT, TCP retrans., etc.), please
refer to 6.5.1.1 Analyzing Real time monitored flows):
=>
<=
Session
A session is identified:
Qualified
(sessions,
throughput,
goodput)
Non qualified
or Unqualified
(throughput,
goodput, sessions)
MOS
(1 to 5)
Mean Opinion Score. The MOS is based on the ipanema metrics Losses,
Delay, Jitter and Codec in use, and calculated over a scale between 1 and
5, with the following signification:
Overactivity
(%)
Evolution
(Volume, Quality,
Activity)
(++/+/0/-/- -)
June 2009
++: the metric has increased a lot (by more than +20%),
+: the metric has slightly increased (between +5 and +20%),
o: the metric is stable (between 5% and +5%),
- : the metric has slightly decreased (between 5 and 20%),
- -: the metric has decreased a lot (by more than 20%).
Ipanema Technologies
7-29
Ipanema System
Color Management
7-30
Ipanema Technologies
June 2009
Ipanema VistaViews
Some of these VistaViews are available only if you have purchased the corresponding
options and if they are enabled in the license file.
June 2009
Ipanema Technologies
7-31
Ipanema System
core
Acceleration
Acceleration - en
Application Monitoring
Application Monitoring - en
CIFS
CIFS - en
Compression (option)
Compression - en
Fault Isolation
Fault Isolation - en
ip_export (option)
Performance Monitoring
Performance Monitoring - en
Site Analysis
Site Analysis-en
SLA
SLA - en
Smartplanning (option)
Smartplanning - en
VoIP
VoIP-en
7-32
Ipanema Technologies
June 2009
The statistics generated by the different functions are available throughout the whole Ipanema
System:
All reports can be created with ip|reporter using the single or the wizard mode (unless otherwise
specified).
The reports on the Domain, on Physical or Virtual sites, and on User classes can also be created
with the Automatic reporting tool.
The available periodicity levels for the reports are the following (unless otherwise specified):
Hourly,
Daily,
Weekly,
Monthly.
The Ipanema System library contains the following report templates, with the following
abbreviations being used:
in What is measured: App: Application; Crit: Criticality; D/J/L: Delay/Jitter/Loss; Ses: number
of sessions; Tput: Throughput; Gput: Goodput; (un)qual: (un)qualified; UC: User class; Vol:
volume; evol: evolution
Filters: D: Domain; P: Physical Sites; V: Virtual sites; K: Keys; S: User Subnets; U: User classes;
A: Applications; C: Criticality
Legend in the Filters:
X: the report is available for Metaviews that contain this object.
Example: is - slm - site summary is available on the Domain.
L: the report is available for Metaviews that contain a list of this object.
Ex.: is - slm - site synthesis is not available on a single Physical site, but it is if the
Metaview contains a list of Physical sites.
o: the report is available for Metaviews that contain this object, but only if the Metaview
also contains objects with an X.
Ex.: is - slm - user class summary per direction is not available on a User class, but it is
if the Metaview is a combination of a Physical Site AND a User class.
What is measured
service level
evolution
site summary
uc summary
uc summary per
direction
D P
app. synthesis
site synthesis
June 2009
Filters
Ipanema Technologies
7-33
Ipanema System
What is measured
Filters
domain
domain overview
site exploitation
site customer
D P
D P
AM (Application Monitoring)
Report template
(is - am -)
What is measured
Filters
user class
summary - tcp
application
summary - tcp
D P
PM (Performance Monitoring)
Report template
(is - pm -)
What is measured
Filters
site summary
uc summary
uc summary per
direction
app. summary
traffic topology
time evolution
detailed per uc
Throughput
7-34
Ipanema Technologies
June 2009
What is measured
compression
evolution
compression
synthesis - uc
compression
synthesis application
Filters
D P
ACC (Acceleration)
Report template
(is - acc -)
What is measured
acceleration
evolution
Filters
D P
acceleration - site
summary
acceleration - uc
summary - per
direction
acceleration
- application
summary - per
direction
VoIP
Report template
(is - VoIP -)
What is measured
Filters
synthesis
MOS distribution
time evolution
Report template
(is - sa -)
What is measured
Filters
K
site summary
ingress
D P
SA (Site Analysis)
June 2009
D P
Ipanema Technologies
7-35
Ipanema System
site summary
egress
site throughput
FI (Fault Isolation)
Report template
(is - fi -)
What is measured
availability evolution
Filters
D P
availability overview
With ip|reporter, FI reports can only be created using the unitary mode.
Smart planning
Report template
(smartplanning -)
What is measured
profile
synthesis
Filters
D P
X
X
ip|export
Report template
(is - ip export -)
What is measured
type 1
Filters
D P
7-36
Ipanema Technologies
June 2009
June 2009
Ipanema Technologies
7-37
Ipanema System
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
Throughput graph
This graph represents the evolution of the Throughput over the period of time:
7-38
Throughput: the surface indicates the non qualified throughput only, whereas the top of the curve
(that sits above the Qualified throughput) indicates the total throughput (qualified + unqualified)
Qualified throughput
Goodput: the surface indicates the non qualified goodput only, whereas the top of the curve
(that sits above the Qualified goodput) indicates the total goodput (qualified + unqualified)
Qualified goodput
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
June 2009
Executive officers
Ipanema Technologies
7-39
Ipanema System
The table
The table presents the following information (note: for color and symbol explanation see the Color
Management picture in Definitions):
Site
Average AQS
Weighted average of the ingress AQS and egress AQS of the site.
In the following columns,
7-40
AQS
D/J/L
Symbolic representation for Delay, Jitter and packet Loss to show the
metrics causing color during a display period of time.
RTT/SRT/Retrans
Symbolic representation for RTT, SRT and TCP Retrans. to show the
metrics causing color during a display period of time.
Average sessions
Average
throughput
(kbps)
Average number of kbits per second at IP level (on physical and/or virtual
ip|engines).
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The table
The table present the following information (note: for color and symbol explanation see the Color
Management picture in Definitions):
User class
Criticality
AQS
D/J/L
Symbolic representation for Delay, Jitter and packet Loss to show the
metrics causing color during a display period for ingress and egress
directions.
RTT/SRT/Retrans
Symbolic representation for RTT, SRT and TCP Retrans. to show the
metrics causing color during a display period for ingress and egress
directions.
June 2009
Ipanema Technologies
7-41
Ipanema System
7-42
Average sessions
Average number of sessions per second for ingress and egress directions.
Average
throughput
(kbps)
Average number of kbits per second at IP level for ingress and egress
directions.
Ipanema Technologies
June 2009
A Domain.
Per Application or a list of applications.
Per User Class or a list of User Classes.
Per Criticality or a list of criticality levels.
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
June 2009
Executive officers
Ipanema Technologies
7-43
Ipanema System
The table
The table presents the following information (note: for color and symbol explanation see the Color
Management picture in Definitions):
User class
Criticality
Average AQS
7-44
AQS
D/J/L
Symbolic representation for Delay, Jitter and packet Loss to show the
metrics causing color during a display period for ingress and egress
directions.
RTT/SRT/Retrans
Symbolic representation for RTT, SRT and TCP Retrans. to show the
metrics causing color during a display period for ingress and egress
directions.
Average sessions
Average number of sessions per second for ingress and egress directions.
Average
throughput
(kbps)
Average number of kbits per second at IP level for ingress and egress
directions.
Ipanema Technologies
June 2009
June 2009
Ipanema Technologies
7-45
Ipanema System
What is measured
How it is measured
Hourly
Daily
Weekly
Monthly
Display rate
1 hour
1 day
1 week
1 month
Time Span
24 hours
1 week
5 weeks
12 months
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
Hourly
Daily
Weekly
Monthly
Display rate
15 minutes
15 minutes
1 hour
4 hours
Time Span
2 hours
2 days
2 weeks
2 months
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
User Class Volume, application volume Top 10, site activity and global evolution Tables
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
1 hour
1 day
1 week
1 month
Time Span
1 hours
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following informations:
Volume Evolution (GB) graph
This graph shows the volume evolution on the last 24 hours, 7 days, 5 weeks or 12 months
according to the periodicity level by criticality.
7-46
Ipanema Technologies
June 2009
%
%
%
%
green volume
yellow volume
red volume
grey volume when quality cannot be computed
Average (Throughput)
Number of Kbits per second at layer 3 level during a display rate.
Max (Peak throughput)
The peak throughput curve displays the maximum encountered value during a display rate.
Average (Throughput)
Number of kbits per second at layer 3 level during a display rate.
Max (Peak throughput)
The peak throughput curve displays the maximum encountered value during a display rate.
For LAN => WAN throughput (kbps) and WAN => LAN throughput (kbps), the
average and maximum throughputs are calculated on the following periods:
Periodicity
Average (throughput)
Hour
15 minutes
15 minutes
Day
15 minutes
15 minutes
Week
1 hour
15 minutes
Month
4 hours
15 minutes
The tables
The tables present the following information:
User Class table
User Class
Criticality
Volume (%)
Volume (MB)
Volume Evolution
(++/+/0/-/- -)
AQS (0 to 10)
Quality Evolution
(++/+/0/-/- -)
June 2009
Ipanema Technologies
7-47
Ipanema System
User class
Volume (%)
7-48
Site activity
Evolution
(++/+/0/-/- -)
Ipanema Technologies
June 2009
What is measured
How it is measured
June 2009
Ipanema Technologies
7-49
Ipanema System
Hourly
Daily
Weekly
Monthly
Display rate
1 hour
1 day
1 week
1 month
Time Span
24 hours
1 week
5 weeks
12 months
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
Throughput graph
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
15 minutes
15 minutes
1 hour
4 hours
Time Span
2 hours
2 days
2 weeks
2 months
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
Site table
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
1 hour
1 day
1 week
1 month
Time Span
1 hours
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following informations:
Volume Evolution (GB) graph
This graph shows the volume evolution on the last 24 hours, 7 days, 5 weeks or 12 months
according to the periodicity level by criticality.
Quality Evolution (%) graph
This graph represents quality evolution on the last 24 hours, 7 days, 5 weeks or 12 months
according to the periodicity level in percentage of volume with different colors:
%
%
%
%
green volume
yellow volume
red volume
grey volume when quality cannot be computed
7-50
Average (Throughput)
Number of kbits per second at layer 3 level during a display period.
Max (Peak throughput)
The peak throughput curve displays the maximum encountered value during a display period.
Ipanema Technologies
June 2009
For the Throughput (kbps), average and maximum throughput are calculated on the
following periods:
Periodicity
Average (throughput)
Hour
15 minutes
15 minutes
Day
15 minutes
15 minutes
Week
1 hour
15 minutes
Month
4 hours
15 minutes
The table
The Site table presents the following information:
Site
Volume (%)
Volume (MB)
Volume Evolution
(++/+/0/-/- -)
AQS (0 to 10)
Quality Evolution
(++/+/0/-/- -)
June 2009
Ipanema Technologies
7-51
Ipanema System
7-52
Ipanema Technologies
June 2009
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
Used to display in a graph an overall view of the service level agreement supplied by the network.
Presents the following information:
User class graph
This graph represents the AQS during no over activity, per critical User Class (Top and High).
Site graph
This graph represents the AQS during no over activity of the 10 worst Sites, for the critical User
Classes (Top and High).
Over activity per site (%) graph
This graph represents the percentage of time when the Right Size (computed by Smart planning)
is higher than the WAN access for Top and High traffic.
June 2009
Ipanema Technologies
7-53
Ipanema System
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The tables
The tables present the following information:
7-54
User class
Criticality
Volume (%)
AQS
MOS
Overactivity (%)
Ipanema Technologies
June 2009
Site
Volume (%)
Percentage of volume represented by the Site for the critical User classes
(Top and High).
AQS
MOS
Overactivity (%)
June 2009
Ipanema Technologies
7-55
Ipanema System
7-56
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following information:
AQS graph
This graph represents the Application Quality Score during no over activity, per critical User Class
(Top and High).
MOS graph
This graph represents the Mean Opinion Score during no over-activity, per User Class.
Volume (MBytes) graph
This graph represents the volume of data (MBytes) exchanged by each critical User Class (Top
and High) and for all non critical ones (Medium and Low).
Session density graph
This graph represents the number of sessions for each critical User Class (Top and High) and for
all non critical ones (Medium and Low).
Overactivity (%) graph
This graph represents the percentage of time when the Right Size (computed by Smart planning)
is higher than the WAN access for Top and High traffic.
June 2009
Ipanema Technologies
7-57
Ipanema System
7-58
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following information:
AQS graph
This graph represents the Application Quality Score during no over activity, per critical User Class
(Top and High).
MOS graph
This graph represents the Mean Opinion Score during no over-activity, per User Class.
Volume (MBytes) graph
This graph represents the volume of data (MBytes) exchanged by each critical User Class (Top
and High) and for all non critical ones (Low and Medium).
Session density graph
This graph represents the number of sessions for each critical User Class (Top and High) and for
all non critical ones (Low and Medium).
Overactivity (%) graph
This graph represents the percentage of time when the Right Size (computed by Smart planning)
is higher than the WAN access for Top and High traffic.
The table
The table presents the following information:
User class
Criticality
AQS
MOS
Overactivity (%)
Volume (%)
June 2009
Ipanema Technologies
7-59
Ipanema System
What is measured
How it is measured
7-60
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Ipanema Technologies
Executive officers
June 2009
The table
The table is used to display the following indicators concerning the Site traffic:
Site
Packet
retransmission
SRT
RTT
Non TCP
sessions
TCP sessions
Goodput
Non TCP
Throughput
TCP Throughput
June 2009
Ipanema Technologies
7-61
Ipanema System
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
7-62
Packet
retransmission
SRT
RTT
Ipanema Technologies
June 2009
Non TCP
sessions
TCP sessions
Goodput
Non TCP
Throughput
TCP Throughput
June 2009
Ipanema Technologies
7-63
Ipanema System
What is measured
How it is measured
7-64
Ipanema Technologies
June 2009
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
Application table
Used to display in a table the following indicators concerning the Application traffic.
Application
Packet
retransmission
SRT
RTT
Non TCP
sessions
TCP sessions
Goodput
Non TCP
Throughput
TCP Throughput
June 2009
Ipanema Technologies
7-65
Ipanema System
7-66
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following information:
SRT (ms) graph
This graph represents:
TCP: the number of TCP segments per second (in kbps, measured at IP level), between
ip|engines (dark blue).
non TCP: the number of non TCP segments per second (in kbps) measured at IP level),
between ip|engines (light blue).
Goodput: the number of kbits per second at layer 4 level (Virtual ip|engines) (green).
Peak: the maximum encountered value during a display period (red).
Sessions graph
This graph represents:
June 2009
Ipanema Technologies
7-67
Ipanema System
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
Site table
Used to display in a table the following indicators concerning the Site traffic.
7-68
Ipanema Technologies
June 2009
Site
LAN average
delay (ms)
WAN average
delay (ms)
LAN total
throughput
(kbps)
Number of kbits per second at the IP level measured on the LAN interface
of the ip|engine.
WAN total
throughput
(kbps)
Total sessions
June 2009
Ipanema Technologies
7-69
Ipanema System
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
7-70
User Class
Qualified
sessions
Qualified
throughput
(kbps)
Total sessions
Total throughput
(kbps)
Total number of kbits per second at IP level (on physical and/or virtual
ip|engines) for ingress and egress directions.
Average delay
(ms)
Average delay of packets delay (in ms) for ingress and egress directions.
Jitter (ms)
Ipanema Technologies
June 2009
Packet size
(bytes)
Average packet size in bytes (on physical and/or virtual ip|engines) for
ingress and egress directions.
Packet size
qualified (bytes)
June 2009
Ipanema Technologies
7-71
Ipanema System
A Domain.
Per Application or a list of applications.
Per User Class or a list of User Classes.
Per Criticality or a list of criticality levels.
What is measured
How it is measured
7-72
Ipanema Technologies
June 2009
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
Criticality
Average delay
(ms)
Jitter (ms)
Qualified Packet
size (bytes)
Qualified
sessions
Total throughput
(kbps)
Total number of kbits per second at IP level (on physical and/or virtual
ip|engines).
Packet size
(bytes)
Total sessions
Qualified
throughput
(kbps)
June 2009
Ipanema Technologies
7-73
Ipanema System
7. 8. 4. is - pm - application summary
Performance Monitoring Table
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
7-74
Application
Qualified
sessions
Qualified
throughput
(kbps)
Total sessions
Ipanema Technologies
June 2009
Total throughput
(kbps)
Total number of kbits per second at IP level (on physical and/or virtual
ip|engines) for ingress and egress directions.
Average delay
(ms)
Average delay of packets (in ms) for ingress and egress directions.
Jitter (ms)
Packet size
(bytes)
Average packet size in bytes (on physical and/or virtual ip|engines) for
ingress and egress directions.
Packet size
qualified (bytes)
June 2009
Ipanema Technologies
7-75
Ipanema System
A Domain.
Per Application or a list of applications.
Per User Class or a list of User Classes.
Per Criticality or a list of criticality levels.
What is measured
How it is measured
7-76
Ipanema Technologies
June 2009
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
Criticality
Average delay
(ms)
Jitter (ms)
Qualified Packet
size (bytes)
Qualified
sessions
Qualified
throughput
(kbps)
Packet size
(bytes)
Total sessions
Total throughput
(kbps)
Total number of kbits per second at IP level (on physical and/or virtual
ip|engines).
June 2009
Ipanema Technologies
7-77
Ipanema System
7. 8. 6. is - pm - traffic topology
Performance Monitoring Table
7-78
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The Tables
The tables present the following information:
Total traffic table
Used to display in a table the following indicators concerning the ip|engine traffic or the Domain
traffic:
Packet size
Sessions
Throughput
Volume
Jitter
Packet loss
Packets size
Sessions
Throughput
Volume
The graphs
The graphs present the following information:
Traffic profile (kbps / % time) graph
June 2009
Ipanema Technologies
7-79
Ipanema System
30
50
67
80
90
95
98
99
100
7-80
Ipanema Technologies
June 2009
<20
<50
<100
Percentage of packets that had a latency (delay) between 50 and 100 ms.
<200
Percentage of packets that had a latency (delay) between 100 and 200 ms.
<500
Percentage of packets that had a latency (delay) between 200 and 500 ms.
<1000
Percentage of packets that had a latency (delay) between 500 and 1000 ms.
<2000
Percentage of packets that had a latency (delay) between 1000 and 2000 ms.
June 2009
Ipanema Technologies
7-81
Ipanema System
Sites table
7-82
Site
Ipanema Technologies
June 2009
7. 8. 7. is - pm - time evolution
Performance Monitoring Table
June 2009
Ipanema Technologies
7-83
Ipanema System
What is measured
A Domain.
A Site or a list of sites.
A Key or a list of keys.
A Subnet or a list of subnets.
An Application or a list of applications.
A User Class or a list of User Classes.
A Criticality or a list of criticality levels.
Delay, jitter, packet loss, throughput, number of sessions.
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following information:
Delay (ms), Jitter (ms) graph
This graph represents:
LAN average delay: the average LAN-to-LAN delay of total packets (in ms) (Blue).
WAN average delay: the average WAN-to-WAN delay of total packets (in ms) (Orange).
LAN jitter: the average LAN-to-LAN delay variation (in ms) (Light blue).
WAN Jitter: the average WAN-to-WAN delay variation (in ms) (Purple).
LAN packet loss : the percentage of lost IP packets between the LAN interfaces of the physical
ip|engines (Red).
WAN packet loss : the percentage of lost IP packets between the WAN interfaces of the
physical ip|engines (Pink).
LAN peak throughput: the maximum encountered LAN-to-LAN throughput during a display
period (Blue).
WAN peak throughput: the maximum encountered WAN-to-WAN throughput during a display
period (Orange).
Throughput: the number of kbits per second at layer 3 level (light blue).
Goodput: the number of kbits per second above layer 4 level (light green).
Qualified throughput: the number of qualified kbits per second at layer 3 level (dark Blue).
Qualified goodput: the number of qualified kbits per second above layer 4 level (dark green).
Sessions graph
7-84
Ipanema Technologies
June 2009
June 2009
Ipanema Technologies
7-85
Ipanema System
7-86
Ipanema Technologies
June 2009
What is measured
A Domain.
A Site or a list of sites.
A Key or a list of keys.
A Subnet or a list of subnets.
An Application or a list of applications.
A User Class or a list of User Classes.
A Criticality or a list of criticality levels.
Throughput.
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graph
The Throughput graph represents the layer 3 throughput distribution for the flows per application
or User class in kbps.
June 2009
Ipanema Technologies
7-87
Ipanema System
7. 9. PM COMPRESSION REPORTS
7. 9. 1. is - pm - compression evolution
Compression Table
Compression Evolution
What can it do?
Monitored resource
What is measured
How it is measured
7-88
Ipanema Technologies
June 2009
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following information:
Ingress Throughput (compress) graph:
LAN Throughput : the Total throughput (in kbps) before compression (Blue curve), on the LAN
interface of the ip|engine.
WAN Throughput: the Total throughput (in kbps) after compression (Orange curve), on the
WAN interface of the ip|engine for all flows (compressed and non-compressed flows).
Compressed: the Throughput of the compressed flows (flows classified in User Class enabled
for compression and going to a physical ip|engines) (Orange area).
Saved: the Throughput saved on the compressed flows (flows classified in User Class enabled
for compression and going to a physical ip|engines) (Blue area).
LAN Throughput : the Total throughput (in kbps) before compression (Blue curve), on the LAN
interface of theip|engine.
WAN Throughput: the Total throughput (in kbps) after compression (Orange curve), on the
WAN interface of the ip|engine for all flows (compressed and non-compressed flows).
Compressed: the Throughput of the compressed flows (flows classified in User Class enabled
for compression and going to a physical ip|engines) (Orange area).
Saved: the Throughput saved on the compressed flows (flows classified in User Class enabled
for compression and going to a physical ip|engines) (Blue area).
June 2009
Ipanema Technologies
7-89
Ipanema System
Compression Synthesis UC
7-90
Ipanema Technologies
June 2009
What is measured
How it is measured
A Domain.
A Site or a list of sites.
A Key or a list of keys.
A Subnet or a list of subnets.
An Application or a list of applications.
A User Class or a list of User Classes.
A Criticality or a list of criticality levels.
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
June 2009
Ipanema Technologies
7-91
Ipanema System
Life Time
24 hours
7 days
Audience
Network analysts
5 weeks
12 months
Executive officers
The graphs
The graphs present the following information:
Ingress Volume (compress) graph:
Compressed volume (MB): for each User Class, the total compressed volume (flows classified
in User Class enabled for compression and going to a physical ip|engines) in MB for the ingress
way (Orange area).
Saved Volume (MB): for each User class, the total saved volume (flows classified in User Class
enabled for compression and going to a physicalip|engines) in MB for ingress way (Blue area).
7-92
Compressed volume (MB): for each User Class, the total compressed volume (flows classified
in User Class enabled for compression and going to a physical ip|engines) in MB for the egress
way (Orange area).
Saved Volume (MB): for each User class, the total saved volume (flows classified in User Class
enabled for compression and going to a physicalip|engines) in MB for egress way (Blue area).
Ipanema Technologies
June 2009
The tables
The tables present the following information:
Ingress Volume (compress) and Egress Volume (decompress) by User Class table
Used to display for each User Class, for all traffic in ingress and egress directions, the volume (in
MB) before and after compression, and the compression ratio.
In each column of the table,
For each User Class, the total volume of flows classified in User Class in
MB (compressed and non-compressed flows); this volume is measured
on the LAN interface of the ip|engine.
For each User Class, the total compressible volume (flows classified in
User Class enabled for compression and going to a physical ip|engine) in
MB before compression; this volume is measured on the LAN interface
of the ip|engine.
Comp. output
(MB)
For each User Class, the total compressed volume (flows classified in
User Class enabled for compression and going to a physical ip|engines)
in MB after compression; this volume is measured on the WAN interface
of the ip|engine.
Comp. factor
For each User Class, the compression factor is calculated by the formula:
Comp. input/Comp. output).
For each User Class, the compression ratio represents the percentage
of compression.
June 2009
Ipanema Technologies
7-93
Ipanema System
7-94
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following information:
Ingress Volume (compress) graph:
Compressed volume (MB): for each Application, the total compressed volume (flows classified
in User Class enabled for compression and going to a physical ip|engine) in MB for the ingress
way (Orange area).
Saved Volume (MB): for each Application, the total saved volume (flows classified in User Class
enabled for compression and going to a physical ip|engine) in MB for ingress way (Blue area).
Compressed volume (MB): for each Application, the total compressed volume (flows classified
in User Class enabled for compression and going to a physical ip|engine) in MB for the egress
way (Orange area).
Saved Volume (MB): for each Application, the total saved volume (flows classified in User Class
enabled for compression and going to a physical ip|engine) in MB for egress way (Blue area).
June 2009
Ipanema Technologies
7-95
Ipanema System
The tables
The tables present the following information:
Ingress Volume (compress) and Egress Volume (decompress) by Application table
Used to display for each Application, for all traffic in ingress and egress directions, the volume (in
MB) before and after compression, and the compression ratio.
In each column of the table,
For each Application, the total volume of flows classified in User Class in
MB (compressed and non-compressed flows); this volume is measured
on the LAN interface of the ip|engine.
Comp. output
(MB)
Comp. factor
7-96
Ipanema Technologies
June 2009
Acceleration Evolution
What can it do?
Monitored resource
What is measured
How it is measured
June 2009
Ipanema Technologies
7-97
Ipanema System
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following information:
Acceleration factors graph:
Compression factor: the compressible volume (measured on the LAN interface of the
ip|engine, before compression) / compressed volume (measured on the WAN interface of the
ip|engine, after compression).
TCP factor: the response time that would have been measured without acceleration (computed
with the following hypotheses: TCP window size equal to 64 Kbytes and MSS equal to 1400
bytes) / Response time of the accelerated sessions.
Acceleration factor: the acceleration factor is calculated by the formula: Compression factor
x TCP factor.
Accelerated session:
7-98
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The table
Used to display for ip|engines (in the Domain, list of sites, list of keys) the information concerning
the following indicators:
Site
Current sessions
New sessions
Comp. factor
TCP factor
Acc. factor
June 2009
Ipanema Technologies
7-99
Ipanema System
What is measured
A Domain.
A Site or a list of sites.
A Key or a list of keys.
A Subnet or a list of subnets.
An Application or a list of applications.
A User Classor a list of User Classes.
A Criticality or a list of criticality levels.
New sessions, Cur. sessions, Comp. factor, TCP factor, Acc. factor
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The table
Used to display for User Classes (in the Domain, list of User Classes) the information concerning
the following indicators:
7-100
User class
New sessions
Cur. sessions
Comp. factor
Ipanema Technologies
June 2009
TCP factor
Acc. factor
June 2009
Ipanema Technologies
7-101
Ipanema System
What is measured
A Domain.
A Site or a list of sites.
A Key or a list of keys.
A Subnet or a list of subnets.
An Application or a list of applications.
A User Classor a list of User Classes.
A Criticality or a list of criticality levels.
New sessions, Cur. sessions, Comp. factor, TCP factor, Acc. factor
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The table
Used to display for Applications (in the Domain, list of User Classes, User Class) the information
concerning the following indicators:
7-102
Application
New sessions
Cur. sessions
Comp. factor
Ipanema Technologies
June 2009
TCP factor
Acc. factor
June 2009
Ipanema Technologies
7-103
Ipanema System
MOS Definition
The data generated by the VoIP module is available throughout the whole Ipanema System.
ip|boss makes them available through the SNMP interface, ip|reporter uses them to generate
the appropriate easy to use reports.
VoIP Synthesis
7-104
Ipanema Technologies
June 2009
What is measured
A Domain .
A Site or a list of sites.
A Key or a list of keys.
A Subnet or a list of subnets,
MOS distribution ingress and egress direction per Codec
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following information:
MOS distribution graph
MOS range reached in percentage of Time.
[1,3]
[3,3.5]
MOS between 3 and 3.5 in percentage of time during the display period.
[3.5,4]
MOS between 3.5 and 4 in percentage of time during the display period.
[4,4.5]
MOS between 4 and 4.5 in percentage of time during the display period.
[4.5,5]
MOS between 4.5 and 5 in percentage of time during the display period.
This representation is very useful to get a view of Voice over IP quality.
MOS example
June 2009
Ipanema Technologies
7-105
Ipanema System
7-106
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
The graphs present the following information:
MOS graph:
Delay (ms): the average delay (in ms) (Blue) per Codec.
Jitter: the average delay variation (in ms) (Yellow) per Codec.
Sessions: the number of sessions per second in direction of Virtual ip|engines (light blue).
Qualified sessions: the number of qualified sessions per second (between physical
ip|engines) (dark Blue).
Peak sessions: the peak sessions curve displays maximum encountered value during a display
rate.
June 2009
Ipanema Technologies
7-107
Ipanema System
What is measured
A Domain.
A list of Sites.
A Key or a list of Keys.
Throughput to physical ip|engine, no correlation, to virtual
ip|engine, to Out of Domain, transit, other, locally rerouted, Non
IPv4 WAN, ignored LAN
From data collected every Long reporting period.
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The table
Used to display for ip|engines (in the Domain, list of sites, list of keys) the information concerning
the following indicators:
7-108
Site
To physical ipe
(kbps)
No correlation
(kbps)
To Virtual ipe
(kbps)
To out of Domain
(kbps)
Ipanema Technologies
June 2009
Transit (kbps)
Other (kbps)
Ingress throughput in kbps for Other traffic; in fact Other traffic contains
Multicast traffic, Broadcast traffic, local traffic.
Locally rerouted
(kbps)
Ingress throughput in kbps for non IPv4 traffic (Apple Talk, IPX, SNA,
IPv6).
Ignored LAN
(kbps)
June 2009
Ipanema Technologies
7-109
Ipanema System
What is measured
A Domain.
A list of Sites.
A Key or a list of keys.
Throughput from physical ip|engine, no correlation, from virtual
ip|engine, from Out of Domain, transit, other, locally rerouted, Non
IPv4 WAN, ignored LAN
From data collected every Long reporting period.
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The table
Used to display for ip|engines (in the Domain, list of sites, list of keys) the information concerning
the following indicators:
7-110
Site
To physical ipe
(kbps)
No correlation
(kbps)
To Virtual ipe
(kbps)
To out of Domain
(kbps)
Transit (kbps)
Other (kbps)
Egress throughput in kbps for Other traffic; in fact Other traffic contains
Multicast traffic, Broadcast traffic, local traffic.
Locally rerouted
(kbps)
Ipanema Technologies
June 2009
Egress throughput in kbps for non IPv4 traffic (Apple Talk, IPX, SNA,
IPv6).
Ignored LAN
(kbps)
June 2009
Ipanema Technologies
7-111
Ipanema System
How it is measured
7-112
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Ipanema Technologies
Executive officers
June 2009
The graphs
Used to display for each ip|engine the information concerning the following indicators:
Ethernet-Throughput (kbps) graphs:
June 2009
Ipanema Technologies
7-113
Ipanema System
7-114
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
Short reporting
5 minutes
1 hour
4 hours
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The graphs
Used to display for ip|engines the information concerning the following indicators:
Status Down graph
This graph represents the Unavailability status of the ip|engine seen by the management system:
Status Up graph
This graph represents the Availability status of the ip|engine seen by the management system:
June 2009
Ipanema Technologies
7-115
Ipanema System
7-116
Ipanema Technologies
June 2009
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display Rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
The table
Used to display for each ip|engine the information concerning the following indicators:
Site
Up Status (%)
June 2009
Ipanema Technologies
7-117
Ipanema System
Synchronization
loss (%)
WAN Overload
(%)
7-118
Ipanema Technologies
June 2009
Smartplanning Profile
What can it do?
Monitored resource
What is measured
A Site,
Throughput (kbps), Right Size (kbps)
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
June 2009
Executive officers
Ipanema Technologies
7-119
Ipanema System
The graphs
Used to display, for each site (ip|engine) in the Domain, for all traffic in the ingress and egress
direction, the throughput (in kbps) and right size (in kbps), by criticality level (top, high, medium
and low) per percentage of time.
The bargraph top shows the bandwidth for top critical flows.
The bargraph high shows the bandwidth for top and high critical flows.
The bargraph medium shows the bandwidth for top, high and medium critical flows.
The bargraph low shows the bandwidth for top, high, medium and low critical flows.
On a flow per flow basis, smartplanning takes into account the traffic demand (the per-session
objective bandwidth, as set in corresponding User Class), the actual network usage (from
measurement function) and the existence, or not, of local or distant congestions (from the
optimization function). Flows elasticity is also estimated and taken into account.
Then smartplanning aggregates this data according to access and criticality, and produces the
following information:
the actual traffic usage (what has been exchanged on the network) per percentage of time;
the right size value (estimated access size to match objectives, including correction for
end-to-end congestions and flows elasticity) per percentage of time.
7-120
The actual usage Throughput (in kbps) is carried out by the measurement module of the
Ipanema System. The original data produced is processed to be aggregated by criticality level
and by access.
The access right size Right Size (in kbps) presents for the site per criticality refined estimate
of the necessary access bandwidth to match the service level according to the percentage of
time, taking into account the flow matrix, end-to-end congestions as well as characteristics of
the flows. Depending on actual traffic nature and congestion status, it can be equal to or smaller
than the traffic demand.
Ipanema Technologies
June 2009
7. 14. 2. is - sp - synthesis
Smartplanning Table
Smartplanning Synthesis
June 2009
Ipanema Technologies
7-121
Ipanema System
What is measured
How it is measured
Type of report
Daily
Display rate
1 day
Time Span
1 day
Life Time
1 day
Audience
Executive officers
The tables
A table is provided per each level of criticality you want to take into account (top top and high
top, high and medium top to low).
Used to display for each site (ip|engine) in the Domain, per selected level of criticality for all traffic
in the ingress and egress directions, the throughput (in kbps), and the trends for the next 3 months
and for the next year per percentile of time.
For each level of criticality, 2 tables are provided:
The bandwidth and its trends for the next 3 months and next year,
The right size and its trends for the next 3 months and next year,
On a flow per flow basis, smartplanning takes into account the traffic demand (the per-session
objective bandwidth, as set in corresponding User Class), the actual network usage (from
measurement function) and the existence, or not, of local or distant congestions (from the
optimization function). Flows elasticity is also estimated and taken into account.
Then smartplanning aggregates these data according to access and criticality, and produces the
following information:
the actual traffic usage (what has been exchanged on the network) per percentage of time;
the estimated traffic value (estimated access size to match objectives, including correction for
end-to-end congestions and flows elasticity) for the next 3 months and for the next year per
percentage of time.
7-122
The actual usage Throughput (in kbps) is carried out by the measurement module of the
Ipanema System. The original data produced is processed to be aggregated by criticality level
and by access.
The estimated Throughput (in kbps) for the next 3 months according to the network activity
of the past 3 months.
The estimated Throughput (in kbps) for the next year according to the network activity of the
past year.
Ipanema Technologies
June 2009
ip export Type 1
What can it do?
Monitored resource
What is measured
How it is measured
Type of report
Hourly
Daily
Weekly
Monthly
Display rate
1 hour
1 day
1 week
1 month
Time Span
1 hour
1 day
1 week
1 month
Life Time
24 hours
7 days
5 weeks
12 months
Audience
Network analysts
Executive officers
This table is not made to use in Infovista, BUT to generate Excel files with these
values in order to make some off line treatment like Billing system.
June 2009
Ipanema Technologies
7-123
Ipanema System
The table
Used to generate for each site (ip|engine), per subnet and User Class the information concerning
the following indicators:
ip|export table
Site
Subnet
User Class
Criticality
IUB
EUB
Egress Unqualified Bytes: number of bytes for egress direction from virtual
sites
IQB
EQB
Egress Qualified Bytes: number of bytes for egress direction from physical
sites
IRB
Ingress Red Bytes: number of bytes for ingress direction to physical sites,
when one or several metrics (average delay, jitter and/or packet loss)
exceed the maximum objectives:
ERB
Egress Red Bytes: number of bytes for egress direction from physical
sites, when one or several metrics (average delay, jitter and/or packet loss)
exceed the maximum objectives:
IYB
when the average delay is between the delay objective and the maximum
delay objective,
when the jitter is between the jitter objective and the maximum jitter
objective,
when the packet loss is between the packet loss objective and the
maximum packet loss objective.
Egress Yellow Bytes: number of bytes for egress direction from physical
sites, when one or several metrics (average delay, jitter and/or packet loss)
are between the nominal and the maximum objectives:
7-124
Ingress Yellow Bytes: number of bytes for ingress direction to physical sites,
when one or several metrics (average delay, jitter and/or packet loss) are
between the nominal and the maximum objectives:
EYB
when the average delay is between the delay objective and the maximum
delay objective,
when the jitter is between the jitter objective and the maximum jitter
objective,
when the packet loss is between the packet loss objective and the
maximum packet loss objective.
Ipanema Technologies
June 2009
IGB
EGB
Egress Green Bytes: number of bytes for egress direction from physical
sites, when all metrics (average delay, jitter and packet loss) are better
than the objectives:
IS
Ingress Sessions: total number of sessions (on physical and/or virtual sites)
for ingress direction.
ES
Egress Sessions: total number of sessions (on physical and/or virtual sites)
for egress direction.
ID
Ingress Delay: average delay for ingress direction for all packets to physical
sites.
ED
Egress Delay: average delay for egress direction for all packets from
physical sites.
IL
EL
Egress Losses: percentage of losses for egress direction from physical sites.
IJ
Ingress Jitter: average jitter for ingress direction for all packets to physical
sites.
EJ
Egress Jitter: average jitter for egress direction for all packets from physical
sites.
June 2009
Ipanema Technologies
7-125
Apache License The Apache Software Licence, Version 1.1 and 2.0 http://www.apache.org
BSD 1.0 License http://opensource.org
GNU General Public License (GPL) Version 2, June 1991 http://www.fsf.org
GNU Lesser General Public License (LGPL) Version 2.1, February 1999 http://www.fsf.org
June 2009
Ipanema Technologies
8-1
Ipanema System
(15) days after formal demand requiring correction of the breach shall have been sent by registered
post with return receipt requested without the breach having been so corrected.
In the event of termination of this license, the End User shall:
8. 5. SOFTWARE WARRANTY
Ipanema warrants that the software performs substantially according to its documentation for a
period of ninety (90) days from date of shipment of the software license key.
Ipanemas sole and exclusive liability and the End Users sole and exclusive remedy under this
limited warranty shall be, at Ipanemas election, to provide corrective maintenance services to
correct the Ipanema software if it doesnt perform as warranted within the warranty period or to
replace it free of charge with a corrected version.
The limited warranty set forth in this article shall not apply to any non conformity that is caused
by: (a) the End Users misuse or improper use of the software, including, without limitation, the
use or operation of the software with an application or in an environment other than that specified
by Ipanema, or introduction of data into any data structures or tables used by the software by any
means other than use of the software; (b) any third party software or hardware; (c) any modifications
or alterations of or additions to the software performed by parties other than Ipanema; or (d) the
End Users failure to implement all problem corrections and new releases.
8. 6. DISCLAIMER
THE EXPRESS REPRESENTATIONS, WARRANTIES AND CONDITIONS OF IPANEMA
SET FORTH IN THIS DOCUMENT ARE IN LIEU OF ALL OTHER REPRESENTATIONS,
WARRANTIES AND CONDITIONS, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED
TO, IMPLIED REPRESENTATIONS, WARRANTIES AND CONDITIONS OF MERCHANTABLE
QUALITY, MERCHANTABILITY, TITLE, DURABILITY OR FITNESS FOR A PARTICULAR
PURPOSE AND THOSE ARISING BY STATUTE OR OTHERWISE IN LAW OR FROM A COURSE
OF DEALING OR USAGE OF TRADE. IPANEMA DOES NOT REPRESENT OR WARRANT
THAT: (A) THE SOFTWARE WILL MEET END USERSS BUSINESS REQUIREMENTS; (B)
THE OPERATION OF THE SOFTWARE WILL BE ERROR-FREE OR UNINTERRUPTED; OR
(C) THAT ALL PROGRAMMING ERRORS CAN BE FOUND AND CORRECTED. THE END
USER IS RESPONSIBLE FOR TAKING PRECAUTIONARY MEASURES TO PREVENT THE
LOSS OR DESTRUCTION OF THE END USERS DATA, INCLUDING WITHOUT LIMITATION,
MAKING REGULAR BACKUPS AND VERIFYING THE RESULTS OBTAINED FROM USING THE
SOFTWARE, AND IPANEMA SHALL HAVE NO OBLIGATIONS OR LIABILITY WHATSOEVER
WITH RESPECT TO SUCH LOSS, DESTRUCTION OR USE UNLESS CAUSED BY THE
WILFUL MISCONDUCT OF IPANEMA.
WITHOUT LIMITING THE GENERALITY OF THE FOREGOING DISCLAIMERS, IPANEMA
EXPRESSLY DISCLAIMS ANY REPRESENTATIONS, WARRANTIES AND CONDITIONS
REGARDING THE PERFORMANCE CHARACTERISTICS OF THE SOFTWARE, INCLUDING
RESPONSE TIMES, MACHINE USAGE AND OTHER OPERATING CHARACTERISTICS, ON
ANY PARTICULAR COMPUTER EQUIPMENT. IPANEMA SHALL HAVE NO RESPONSIBILITY
FOR THE SELECTION, INSTALLATION AND MAINTENANCE OF THE COMPUTER
EQUIPMENT ON WHICH THE PROGRAMS AND THIRD PARTY SOFTWARE ARE TO
OPERATE.
8-2
Ipanema Technologies
June 2009
FOR ANY BREACH OF THIS AGREEMENT OR ANY OTHER CLAIM ARISING FROM OR
RELATED TO THIS AGREEMENT GIVING RISE TO LIABILITY, IPANEMAS ENTIRE LIABILITY
SHALL BE LIMITED TO THE END USERS ACTUAL DIRECT, PROVABLE DAMAGES IN AN
AMOUNT NOT TO EXCEED IN THE AGGREGATE, THE TOTAL LICENSE FEES PAID BY THE
END USER FOR THE SOFTWARE THAT IS THE SUBJECT MATTER OF THE CLAIM.
IN NO EVENT SHALL IPANEMA OR ITS RESELLER BE LIABLE FOR LOSS OF PROFITS, LOSS
OF BUSINESS REVENUE, LOSS OF DATA, FAILURE TO REALIZE EXPECTED PROFITS OR
SAVINGS OR ECONOMIC LOSS OF ANY KIND, OR FOR ANY INDIRECT, CONSEQUENTIAL,
SPECIAL, INCIDENTAL OR PUNITIVE LOSSES OR DAMAGES, OR FOR ANY CLAIM AGAINST
END USER BY ANY OTHER PERSON, EVEN IF IPANEMA OR ITS RESELLER HAS BEEN
ADVISED OF OR COULD REASONABLY FORESEE THE POSSIBILITY OF ANY SUCH
DAMAGE OCCURRING.
THE LIMITATIONS SHALL APPLY REGARDLESS OF THE FORM OF ACTION, WHETHER
BASED ON CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, OR
OTHER LEGAL OR EQUITABLE THEORY, INCLUDING A BREACH OF A CONDITION OR
FUNDAMENTAL TERM OR FUNDAMENTAL BREACH OR BREACHES. THE LIMITATIONS
SHALL NOT APPLY TO CLAIMS FOR PERSONAL INJURY OR BODILY HARM CAUSED BY
EITHER PARTY, OR PAYMENT OF AMOUNTS OWING BY THE END USER TO IPANEMA OR
ITS RESELLER.
8. 7. GOVERNING LAW
This License is governed by French law and any proceedings arising out of or in connection with
this License shall be submitted to the Commercial Court of Paris, France.
If any provision hereof is held invalid, the remainder shall continue in full force and effect.
June 2009
Ipanema Technologies
8-3
Please refer to the support and maintenance contract for specific information about these services.
Should you have any problem with your system, please contact your supplier for technical
assistance.
In any case, you can get support and information by logging on Ipanemas Support web site:
https://support.ipanematech.com,
where you can access the Public Knowledge Database, find Technical notes and FAQs, be informed
of the latest developments and updates, download all the Ipanema software, create and track
tickets, and find other relevant information relating to the Ipanema System.
An account will be created on demand.
Other contact information:
E-mail: support@ipanematech.com
Phone: +(33)1 55 52 15 22
Fax: +(33)1 55 52 15 01
In the event of a technical problem, please supply as much information as possible, in particular:
your name, address, telephone number and the name of your company,
your Ipanema Technologies license number, see window about in ip|boss field reference,
the names, versions and serial numbers of the products you are using,
the version: Windows (2000 / 2003) or Solaris of operating system for ip|boss,
a description of the installed configuration and the configuration files,
a detailed description of the problem you have encountered.
June 2009
Ipanema Technologies
9-1