PARTE II: REQUERIMIENTOS EN PLANTA 1. INTRODUCCIÓN
10. CALCULO DE ESFUERZOS DE LA CORRIENTE
11.4. BUQUES DE 20m
2.1.1. NAVEGACIÓN EN TRAMOS RECTOS CON CONDICIONES CLIMÁTICAS CONSTANTES A LO LARGO DE LA TRAZA
AG: Application Group.
Aggregated flow: an aggregated flow groups together IP micro-flows sharing given common characteristics. It is specified by a source subnet, a destination subnet and, where appropriate, a protocol, an application and a client/server direction and a TOS.
ANS: Autonomic Networking System.
Applications Dictionary: the Applications Dictionary contains a list of the applications recognized by the system. The applications are identified by protocol, a TCP or UDP port number, a type of Codec, a URL for HTTP, a published application for Citrix...
Applications Group: Group of Applications with a certain Criticality level and a certain QoS Profile; contains key parameters for AQS measurement and Application Control.
Application Quality Score: Ipanema notation for the traffic Quality. From 0 (very bad) to 10 (very good). The notation is calculated according to the expected behavior.
AQS: Application Quality Score (see description above).
ASL: Application Service Level.
BDP: Bandwidth Delay Product.
Byte counting: the system indicates the number of bytes in the IP packet, including IP headers.
CIFS: Common Internet File System, aka SMB (Server Message
Block).
CLI: Command Line Interface.
Congestion: state of a network resource in which the traffic incident on the resource exceeds its output capacity over an interval of time.
CoS: Class of Service.
CPE: Customer’s Premises Equipment (network access equipment
located on the customer’s site. In the case of an IP network this is usually an access router).
Delay variation: Standard deviation of the delay on a given period.
DPI: Deep Packet Inspection, the application recognition mechanism used by Ipanema, based on the layer 7 syntax.
DSCP: DiffServ Code Point.
DstPort: Destination Port.
Datagram: block of data transmitted on the packet switched network.
D/J/L: Delay/Jitter/Loss.
Domain: a Domain is composed of a set of ip|engines making and exchanging observations and making measurements based on these. ip|engines are configured and operated via the ip|boss central software. All elements in a Domain must be connected in the IP sense (each element must have an IP address that can be routed on the network).
DWS: Dynamic WAN Selection (feature provided by the smart|path service).
Ipanema System
Elementary observation: measure of time, length, etc., performed by the ip|engine on each measured packet.
Equipped site: site with an ip|engine, a nano|engine or a virtual|engine.
Flow: in the Ipanema system, we call a flow all the sessions of a given application, from a given source to a given destination.
Fragmentation: the process of division of a datagram into several fragments (IP packets), to facilitate traffic flow on low-speed links for example.
GLASS: GlobaL Autonomic Support System: ip|engine metrics aimed at accelerating technical escalations.
GPS: Global Positioning System (a positioning and synchronization system based on a satellite constellation (~ 24) in medium altitude orbit, covering practically the entire surface of the earth and is highly accurate. It used to be used in early versions of the Ipanema system).
Goodput: Number of received bits per second above layer 4 (i.e., TCP or UDP payload).
GUI: Graphic User Interface.
HSRP: Hot Standby Router Protocol (Cisco).
ICMP: Internet Control Message Protocol.
IMA: Ipanema Mobile Agent.
IP: Internet Protocol.
IP micro-flow: an IP micro-flow is specified by all packets identified by the same IP source and destination address, the same protocol and, where appropriate, the same TCP/UDP ports.
ip|agent: Ipanema software running on Ipanema appliances (ip|engines and nano|engines) and virtual appliances (virtual|engines);
by extension, we call ip|agent the software running on Ipanema Mobile Agents (IMAs), although the latter do not run all ip|agent services.
ip|agent services are ip|true, ip|fast, ip|xcomp, ip|xtcp, ip|xapp, smart|path and smart|plan.
ip|boss: component of the SALSA suite used to configure the Domains.
ip|coop: tele|engines’ cooperative control (part of ip|fast).
ip|dashboard: component of the SALSA suite allowing to monitor the traffic (in reality the server is part of ip|boss server).
ip|engine: Ipanema appliance that performs measurement, control, compression, acceleration, etc., to provide Visibility, Application Control and WAN Optimization.
ip|fast: ip|agent providing Application Control.
ip|reporter: component of the SALSA suite that generates the reports; it is powered by InfoVista.
ip|true: ip|agent’s measurement service, behind the Application Visibility feature.
ip|uniboss: component of the SALSA suite used to manage the Domains, Users and Licenses.
ip|xapp: ip|agent providing CIFS acceleration (part of the WAN optimization feature).
ip|xcomp: ip|agent providing Compression (SRE and ZRE — part of the WAN optimization feature).
6 Ipanema Technologies
October 2014
ip|xtcp: ip|agent providing TCP acceleration (part of the WAN optimization feature).
IPDR: IP Data Records.
ISU: Ipanema Software Unit.
ITP: Ipanema Time Protocol.
Jitter: standard deviation of the delay on a given period.
JRE: Java Runtime Environment.
LAN: Local Area Network (the same geographical site may have several LANs interconnected by a router).
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;
applies to the throughput, Delay, Jitter and packet Loss. Also abbreviated “LAN” (e.g. LAN-to-LAN Delay = “LAN Delay”).
LDAP: Lightweight Directory Access Protocol, used for authentication and authorization in SALSA.
LTL: Local Traffic Limiting.
Measurement interface: interface on the ip|engine giving access to the point of measure.
Measurement ticket: the measurement ticket groups together the elementary observations made on an IP packet by an ip|engine.
MetaView: Object we report on (Domain, Site, group of Sites, Application Group, etc.), created in ip|boss. The reports aggregate data on MetaViews, in ip|reporter.
MOS: Mean Opinion Score (standard Measure of the Quality of a Voice Call (notation between 0 (very bad) to 5 (very good), normalized by the ITU-T (G.107)).
MRE: Multi Redundancy Elimination (= SRE + ZRE; synonymous
with Compression).
nano|engine: Ultra compact Ipanema appliance that performs measurement and control, to provide Visibility and Application Control in small Branch offices (no WAN Optimization, unlike ip|engines).
NAP: Network Access Point.
OWD: One Way Delay.
Packets: series of binary elements organized in a predefined format and transferred as a whole.
Packet counting: the system indicates the number of datagrams observed.
It is insensitive to fragmentation by routers, whether this fragmentation occurred in the Domain of Measure (between ip|engines) or outside the Domain (before the first ip|engine).
Packet loss: the system indicates the number of datagrams lost. It is therefore insensitive to fragmentation by routers, whether this fragmentation occurred in the Domain of Measure (between ip|engines) or outside the Domain (before the first ip|engine).
PBR: Policy Base Routing.
Physical site: (Obsolete) old name for an Equipped site.
Point of measure: place of traffic acquisition where measures are made.
QoE: Quality of Experience (measured by the AQS).
Ipanema System
QoS: Quality of Service.
QoS Profile: Set of parameters in ip|boss, which applies to an Application Group. The parameters are: the traffic type (real time, transactional or background), the bandwidth objective and the maximum bandwidth (per session), followed by 6 quality metrics (delay, jitter, loss, RTT, SRT and TCP retransmission) with two thresholds each (objective — maximum).
RADIUS: Remote Authentication Dial-In User Service.
Router: interconnection gateway between two IP networks.
Routing: operation of determining the route to be taken through a network by a data packet.
RTT: Round Trip Time.
SALSA: Scalable Application Level Service Architecture.
SAML: Security Assertion Markup Language.
Sensitivity: Application Group parameter, used for DWS.
SLA: Service Level Agreement.
smart|path ip|agent providing Dynamic WAN Selection.
smart|plan ip|agent’s Network Rightsizing service
SNMP: Simple Network Management Protocol.
SrcPort: Source port.
SRE: Standard Redundancy Elimination (AKA “Disk-based
compression”).
SRT: Server Response Time.
SSL: Secure Socket Layer.
TCP: Transmission Control Protocol.
tele|engine: Allows traffic on unequipped Sites to be measured and controlled by the ip|engines of the remote Sites, thus providing Application Visibility and Control without any appliance on the local Site (branch office). tele|engines are configured in ip|boss as ”physical”ip|engines, checking a specific box. A Site with a tele|engine is called a tele-managed Site.
Tele-managed Site: Site with a tele|engine.
Ticket Record: groups measurement tickets together for transmission between ip|engines.
TOS: Type Of Service.
TOS Dictionary: the TOS Dictionary contains a list of TOS recognized by the system. The TOS are identified by the field Type Of Service in IP packet.
Traffic profile: a description of the temporal properties of a traffic stream such as rate and burst size.
Transfer delay: the transfer delay of a packet between ip|engines is measured when the last bit of the packet passes the measure points.
In the event of fragmentation of the datagram into several IP packets, the measure is made when the last bit of the last fragment passes.
Throughput: Number of bits per second at the IP level.
8 Ipanema Technologies
October 2014
UC: Unified Communications.
UDP: User Data Protocol.
VF0 / VF4: Vista Foundation 0 / 4 (InfoVista platforms provided with ip|reporter).
Virtual ip|engine: (Obsolete) old name for a tele|engine (< SALSA v6).
Virtual site: (Obsolete) old name for a tele-managed Site.
virtual|engine: Software image of an ip|engine, to be deployed on VMware ESXi.
VoIP: Voice over IP.
VPN: Virtual Private Network.
VRF: Virtual Routing and Forwarding.
WAN: Wide Area Network (long distance network that allows data exchange between remote sites).
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.
Applies to the throughput, Delay, Jitter and packet Loss. Also abbreviated “WAN” (e.g. WAN-to-WAN Delay = “WAN Delay”).
LAN-to-LAN Delay = Delay generated by the source ip|engine, if any + WAN-to-WAN Delay + Delay generated by the destination ip|engine, so the LAN-to-LAN Delay includes (and is higher than or equal to) the WAN-to-WAN Delay.
WFQ: Weighted Fairness Queuing.
Wizard: Way to create combinations of MetaViews and reports in ip|boss’ Reports menu.
ZRE: Zero delay Redundancy Elimination (AKA “RAM-based
compression”).
CHAPTER 1. IPANEMA SYSTEM
Document organization
1. 1. OVERVIEW
1. 1. 1. Autonomic Networking System
Ipanema’s self-learning and self-optimizing Autonomic Networking System™ (ANS) tightly integrates all the features to guarantee the best application performance: Application Visibility, Application Control, WAN Optimization, Dynamic WAN Selection and Network Rightsizing.
Easy to use and highly scalable, ANS addresses mid-size and thousands-sites companies. It also addresses Service Providers with thousands of customers.
Based on the SALSA central management platform and on a family of appliances and software agents, ANS fits from the smallest Branch Office to the largest Datacenter.
SALSA’s centrally managed cooperative architecture
Ipanema System
Ipanema’s ANS is:
■ Autonomic:
– It guarantees applications performances through global and distributed coordination between Ipanema appliances and software agents,
– it dynamically adapts to traffic and network changes thanks to a “Sense and Respond"
mechanism (Sense: Real-time view of the network performances and users demand;
Respond: Dynamic and distributed computation with second-by-second optimal policies enforcement),
– full control is provided, in most cases (depending on the network architecture), with as few as 10-20% of the sites equipped with physical appliances.
■ All-in-one:
– All features are tightly coupled,
– it optimizes all application flows: data transfers (FTP, CIFS...), interactive flows (ERPs, Citrix...), real-time flows (VoIP, Videoconference...), etc.
■ Service Framework:
– A unified management GUI is provided for all features,
– the multi-tenant SALSA platform scales up to 10M’s users and 100K’s sites, – objective-based control enables Application SLAs and global WAN Governance.
1-2 Ipanema Technologies
October 2014
Ipanema System
1. 1. 2. Ipanema features
This section quickly describes Ipanema features (for more details see 1.3. Features description).
Application Visibility
■ Goal: understand application usage and performance over the entire network.
■ How: providing clear application performance KPIs (Application Quality Score — or AQS — and MOS), high level consolidated reports, and very detailed information at the flow level.
Application Visibility
Ipanema System
Application Control
■ Goal: guarantee users’ experience by controlling each application flow in real-time, depending on the network resources.
■ How: dynamically enforcing Application SLAs for each user thanks to a global and dynamic approach, where the whole traffic matrix is taken into account in real time. Application Control manages the application flows in the most efficient way, even in full-mesh and very large networks.
Application Control
1-4 Ipanema Technologies
October 2014
Ipanema System
WAN Optimization
■ Goal: accelerate delay sensitive applications and reduce bandwidth consumption.
■ How: eliminating redundancy in the application flows (both at the packet level and data stream level), and accelerating TCP segments, CIFS application, SSL flows, etc.
WAN Optimization
These features are tightly coupled to address all situations.
Tightly coupled features
Ipanema System
Network Rightsizing:
■ Goal: align network sizing to budget and business requirements.
■ How: combining Application Visibility and Application Control data to determine sizing options and their consequences; the results are displayed in easy-to-use reports.
Network Rightsizing
1-6 Ipanema Technologies
October 2014
Ipanema System
Dynamic WAN Selection:
■ Goal: guarantee application performance across hybrid [MPLS + Internet] networks, improve business communication continuity, exploit large network capacity at low cost, benefit from Internet immediacy and ubiquity, turn back-up lines into business lines, eliminate complex policy based routing and unify the management of hybrid networks.
■ How: automatically and dynamically selecting the best path for each application flow across the various networks.
DWS
Ipanema System
1. 1. 3. Ipanema appliances, VMs and software agents
Ipanema features are performed by Ipanema appliances, virtual machines and software agents, generally located at the interface between the enterprise network (LAN) and the access router to the operator network (WAN).
There are two families of appliances: ip|engines and nano|engines, and two families of software agents: virtual|engines and Ipanema Mobile Agents (IMAs).
Application Visibility and Application Control features are also available on sites that are not equipped (no ip|engine, no nano|engine and no virtual|engine on the site), declaring
“tele|engines” on these sites.
ip|engines: hardware devices; various models are available, with different capacities
nano|engines: hardware ultra compact devices, for small Branch Offices
tele|engines: logical service delivered through the remote collaborating ip|agents
virtual|engines: virtual machines in .vmdk format
IMAs: software agents for Windows desktops
ip|agent is the software running on ip|engines, nano|engines and virtual|engines. IMAs run some of ip|agent’s services (but we also call them ip|agents, by extension).
To provide the features described above, ip|agents run the following services:
■ for Application Visibility:
– ip|true: measurement,
– ip|sync: time synchronization,
■ for Application Control:
– ip|fast: the Application Control service, – ip|coop: tele|engines’ cooperative control,
■ for WAN Optimization:
– ip|xtcp: TCP acceleration,
– ip|xcomp: compression (SRE and ZRE) + TCP acceleration, – ip|xapp: CIFS acceleration,
■ for Network Rightsizing:
– smart|plan
■ for Dynamic WAN Selection:
– smart|path.
1-8 Ipanema Technologies
October 2014
Ipanema System
1. 1. 4. Features availability
The table below summarizes the features provided by the different Ipanema appliances and virtual machines, and on tele-managed sites:
ip|eax ip|e
non-ax nano|e virtual|e tele|e
ip|true yes yes yes yes, performed by
the remote ip|agents;
no D/J/L info
ip|fast yes yes yes yes, performed by the
remote ip|agents ip|xcomp
SRE yes no no, except on hosts
running IMAs yes no, except on hosts running IMAs ip|xcomp
ZRE yes** no yes no
ip|xtcp yes** no* no* no*
ip|xapp yes*** no, except on hosts
running IMAs yes*** no, except on hosts running IMAs
smart|path yes yes no no
smart|plan yes yes yes no
Features availability
* ip|xtcp is a single-box sender-side technology, so traffic to a site with a nano|engine, a virtual|engine or a tele|engine can be accelerated.
** except for ip|e 40so.
*** ip|xapp is a single-box client-side technology, so the ip|engine or virtual|engine must be installed in the Branch Office (where the clients are). If it is not (sites with a nano|engine or a tele|engine), the feature can still be delivered, thanks to IMA.
Ipanema System
1. 1. 5. Functional architecture
SALSA (Scalable Application Level Service Architecture) is the Central Management Software; it is composed of:
■ ip|uniboss software (one server): it ensures the creation and management of the Domains, Unified User Management and Licenses management.
■ ip|boss software (one or several servers, depending on the number of Domains and their sizes;
it can be installed on the same server as ip|uniboss): it ensures system administration, system configuration (system provisioning, application provisioning and reports provisioning), service activation, real time monitoring (ip|dashboard), supervision, collect of the Correlation Records generated by ip|agents every minute (according to the parameters), interface with ip|reporter to create or delete reports (the main reports are automatically created).
■ ip|reporter software (one or several servers, depending on the number of Domains, the volume of traffic and the number of reports; on very small networks — less than 10 sites — it can be installed on the same server as ip|boss/ip|uniboss): it ensures the reporting function, polling ip|boss to collect the raw data that it then consolidates it in many different dimensions, with about 40 pre-defined report templates.
ip|reporter is powered by InfoVista and embeds an InfoVista run time licence; this run time provides all user functions in local, remote or client/server mode or with an HTML interface with VistaPortalSE.
InfoVista can be provided with two different VistaFoundation platforms: VF0 (provided to most Ipanema customers) and VF4 (provided for MSPs/NSPs or customers with very large networks only). Only VF0 platform is described in this document. For VF4 information, please refer to the relevant Technical notes.
ip|export, an optional module of ip|reporter, allows automatic and dynamic export of any data from any reports in text, CSV or Excel formats. It is designed for seamless inter-operability between network measurement systems and Business Support Services.
SALSA architecture
1-10 Ipanema Technologies
October 2014
Ipanema System
A SALSA unified portal gives access to ip|uniboss, ip|boss, ip|dashboard and ip|reporter web.
A Domain selector (drop-down list) allows selecting the Domain to be configured (with ip|boss) or monitored (with ip|dashboard) prior to connecting.
SALSA unified portal
It can be accessed with a web browser athttps://<ip|uniboss IP address>/salsa/.
Ipanema System
1. 2. GENERAL PRINCIPLES
1. 2. 1. System deployment
A Domain is made up of a set of Ipanema appliances and virtual machines positioned at the measurement or control points of a network, in the same LANs as the CPE routers.
Their ip|agent software measure, control, compress and accelerate the network traffic on the entire network.
One Domain has to be created by logical entity, using ip|uniboss software. Once created, it is managed by a dedicated ip|boss instance.
System deployment
ip|agents belonging to the same Domain cooperate (distributed intelligence), but do not interact with other ip|agents belonging to other Domains.
To measure, control and accelerate flows on a site with no ip|agent (no appliance nor virtual machine), the user can declare a tele|engine on that site (in the same way as they would declare a real ip|engine, in ip|boss). To make this possible, ip|agents must be present at the other ends of the flows (measurement, control and acceleration will be performed by the remote ip|agents indeed — reason why such a site is also called a tele-managed site).
1-12 Ipanema Technologies
October 2014
Ipanema System
ip|agents cooperation in a Domain (with tele-managed sites)
The system performs measurement, control, redundancy elimination and acceleration on the basis of the observed traffic in the user’s private IP addressing plan.
Each ip|agent recognizes the local network (LAN) traffic transmitted to and received from the long-distance network (WAN).
LANs have an IP address range expressed in the form a.b.c.d and a prefix, the length of which is
LANs have an IP address range expressed in the form a.b.c.d and a prefix, the length of which is