Network Monitoring from the End-User Perspective

A webinar by

1. Evolution of network monitoring

2. Troubleshooting IP networks

3. Network monitoring from the end-user perspective

4. A real use case

What we’ll cover today:

What is Network Monitoring?A network monitoring tool verifies the correct functioning of networked

devices, such as routers, switches, and servers, and enables network and

systems administrators to be notified of failures and performance

issues.

Evolution of Network Monitoring

1981: RFC 792 defines the Internet Control Message Protocol (ICMP).

1988: The first RFC for SNMP was written.

1996: The NetFlow protocol was first implemented on Cisco IOS 11.x.

The Network Monitoring Stack

>_

SNMPCPU utilization,

interfaces stats, etc.

PassiveTraffic traversing the

interfaces, etc.

ActiveRound-trip-time, packet loss, etc.

Workstation

Server

ActiveProbe

Troubleshooting IP Networks

Top reasons for network problems:

● Hardware failures

● Software bugs and configuration errors

● Resources oversubscription

● Routing changes

What are the best tools to troubleshoot each class of problems?

Reducing Time to Detection and to Resolution

Have the right tool in place.

Problem Network monitoring protocol

Hardware failures SNMP

Software and configuration changes Active monitoring

Resources oversubscription Passive monitoring or SNMP

Routing changes Active monitoring

Network Monitoring from the End-User Perspective

● Performed from the access layer (Ethernet or Wi-Fi) at remote sites

● Runs active network & application tests:○ Packet loss

○ Network latency

○ Routing changes

○ DNS resolution time

○ HTTP response time

● Continuous tests, interval based on application

NetBeez Approach● Sensors: Hardware, software, virtual, or cloud

● Server: On-premise or cloud based

● Tests○ Network layer: PING, Traceroute, Iperf, Speedtest

○ Application layer: DNS, HTTP, VoIP, TCP Ping

● Problems detected○ Network connectivity

○ Internet slowness

○ Unstable wireless

○ Slow websites

Use Case: Dual-Connected Branch Office

User traffic

Branch Office Switch

Branch Office Router

50 Mbps

Secondary Host Router

Primary Host Router

5 Mbps

Failover

Branch Office Switch

Branch Office Router

50 Mbps

Secondary Host Router

Primary Host Router

User traffic

✖

5 Mbps

Active checks (PING)

PING test

Branch Office Switch

Branch Office Router

50 Mbps

Secondary Host Router

Primary Host Routerॱ

5 Mbps

Triggered Alert

Test traffic

Branch Office Switch

Branch Office Router

50 Mbps

Secondary Host Router

Primary Host Router✖

5 Mbps

PING test to 10.32.1.1 failed (TIME OUT)

Request a demo today!

https://netbeez.net/demo

Q&A