|
|
Currently, we don't get an
accurate picture of how are used our networks, which computers are
consuming most of the bandwidth, in which proportion, at what period of
the day.
This deficiency could be
satisfied with the traceability of data exchanged between all computers
communicating over the networks.
From this knowledge, we could
focus our efforts on real causes of bandwidth soaring.
In the end, networks cost would be better controlled. NER(Network Exchanges Reporter) is an answer to our needs on network traceability. It holds the history of all network exchanges between computers for years. Its mains assets are:
|
 |
In
general, Network Exchanges Reporter is composed of several network
interfaces dedicated to capture network packets. Each network interface is connected to a communication node which is physically a port of a switch set as mirroring other ports. |
| High
visibility on network exchanges You'll know with a high
precision, which pairs of communicating computers are consuming most of
your bandwidth.
You'll know on any past period,
response time of all ports of communication of each network actor.
Relevant analysis tool when an incident occurs NER brings key elements on
network activity on the period of the incident.
It enables to better understand
causes and effects of the incident.
Detect abuses and anomalies Creation of monitoring tasks on
many criteria permits to trigger alerts when thresholds are reached.
Thus, we can easily detect bandwidth abuses, or being alerted in case response time of crucial servers is rising. Brings the proof in case of dispute NER logs all network exchanges
between computers, so it will tell who's doing what for the target time
frame.
|
Visibility
on the evolution of traffic and computers response time On any selected period, NER
shows you the evolution of the traffic and response time on any group
of computers and/or networks and/or protocols.
Curves of the evolution of the top 15 protocols are shown depending on the criteria you've selected. Data exportation NER contains a sophisticated
scheduler in order to export data regularly via FTP or mail.
Thus, you'll be able to use your favorite tool to create your own analysis reports. Also, as data exportation can be done via Email, then it will be possible, for example, to remotely follow the behavior of a new application. Helps in taking a decision With NER you'll know if an
application is well filling packets and so whether it is well adapted
to WAN.
You'll also see how a new application is consuming your WAN bandwidth with the traffic of all ports. Quantify how slow are key applications for remote users NER gives information on
response time of client computers, so it gives a good idea on how
remote users feel.
|
|
Select the
group of network actors on which you would to know the traffic volume
or the response time evolution on a period you select and you get 1
curve for all protocols involved and 3 curves highlighting Top 5, Top 5
to 10 and Top 10 to 15 protocols.
|
|
Global evolution
 |
Top 5 protocols
 |
Top 5 to 10 protocols  |
Top 10 to 15 protocols |
| Select the group of network actors and the period on which you would to get the details, and you get a report as below. |
| Another type of report, this time it's all network actors communicating with each network actor. |
|
Monitoring
tasks enable to be alerted by Email when a threshold is reached.
|
|
Data
exportation is done either by FTP or by Email with an attached gzip
file.
Export
attributes for FTP flat file are: ip_server,
server_DNS_name, server_volume_outbound_bytes,
server_nb_packets_outbound, server_response_time_ms, server_protocol,
server_protocol_name, server_port server_port_name,
server_port_volume_outbound_bytes, server_port_nb_packets_outbound,
server_port_response_time_ms, ip_client, client_DNS_name,
client_volume_outbound_bytes, client_nb_packets_outbound,
client_response_time_ms, client_protocol, client_protocol_name,
client_port, client_port_name, client_port_volume_outbound_bytes,
client_port_nb_packets_outbound, client_port_response_time_ms,
total_server_client_volume_bytes, total_server_client_nb_packets,
total_server_client_port_volume_bytes,
total_server_client_port_nb_packets
|
|
|