Professional Documents
Culture Documents
Modul 11 Analisa QoS
Modul 11 Analisa QoS
Network
• Fault management
– Network
N t k state
t t monitoring
it i
– Failure logging, reporting and tracking etc.
• Configuration management
– device and software configuration
– version control (compare, apply and rollback, backup) etc.
• Accounting management
– billing and traffic measurement etc.
• Performance
f managementt
• Security Management
– Access control,
control worm/attack detection and alert etc
etc.
Performance Management-Why
• Why needed and important?
– Capacity planning
• when do we need to upgrade our link and device?
– Ensure network availability
– Verify network performance, verify QoS (we expected)
– Ensure SLA compliance (customer expected)
– Better understanding and control of network
– Optimization, make the network runs better!
• Proactive or reactive?
– Know problem before users and boss
– Solve the problem before their complain
Or
– Wait for problem to happen, and customers complain?
Business Technology
SLA QoS
SLA example: Level 3
Delay
Packet Loss
Availability
Jitter
Bandwidth
SLA example: Sprintlink
Packet
Delay Availability Jitter
loss
North America 55 ms 0.30% 99.90% 2 ms
Europe 44 ms 0 30%
0.30% 99 90%
99.90% 2 ms
Asia 105 ms 0.30% 99.90% 2 ms
South pacific 70 ms 0 30%
0.30% 99 90%
99.90% 2 ms
Continental US
55ms 0.1% n/a 2 ms
(Peerless IP)
Measurement Technology
• We’ve known what metrics used to describe
network
t k performance,
f b
butt h
how to
t measure them?
th ?
• Technologies and tools
– ping,
i traceroute,iperf,
t t i f jperf.
j f
– SNMP
– Netflow (Cisco),
(Cisco) Sflow (Juniper),
(Juniper) NetStream (Huawei)
– IP SLA (Cisco)
– Etc.
Active Measurement Tools
• Tools that inject packets into the network to
measure some value l
– Available Bandwidth
– Delay/Jitter
– Loss
• Requires bi-directional traffic or
synchronized hosts
Passive Measurement Tools
• Tools that monitor existing traffic on the
network
t k and
d extract
t t some iinformation
f ti
– Bandwidth used
– Jitter
– Loss rate
• May generate some privacy and/or security
concerns
ping
• Normally used as a troubleshooting tool
• Uses ICMP Echo messages to determine:
– Whether a remote device is active (for trouble shooting)
– round trip time delay (RTT), but not one-way delay
– Packet loss
• Sometime we need to specify the source and length
of packet using extended ping in router or host
– Why using large packet when ping?
(to test the link quality and throughput.)
– Large packet ping is prohibited in Windows
Windows, but Linux is ok
Sample Ping
Freebsd>% ping 202.112.60.31
PING 202.112.60.31 (202.112.60.31) 56(84) bytes of data.
64 bytes from 202
202.112.60.31:
112 60 31: icmp_seq=1
icmp seq=1 ttl=253 time=0
time=0.326
326 ms
……
64 bytes from 202.112.60.31: icmp_seq=6 ttl=253 time=0.288 ms
6 packets transmitted, 6 received, 0% packet loss, time 4996ms
rtt min/avg/max/mdev = 0.239/0.284/0.326/0.025
0 239/0 284/0 326/0 025 ms
router# ping
Protocol [ip]:
[ p]
Target IP address: 202.112.60.31
Repeat count [5]:
Datagram size [100]: 3000
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 3000-byte ICMP Echos to 202.112.60.31, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
traceroute
• Can be used to measure the RTT delay, and also the
delayy between the routers along g the path
p
• Unix/linux traceroute uses UDP datagram with
different TTL to discover the route a packet take to
the destination, Microsoft Windows tracert uses
ICMP protocol,
t l If Windows
Wi d tracert
t t appears to
t show
h
continuous timeouts, the router may be filtering
ICMP traffic – try a Unix/Linux traceroute
• After
Aft ththe N
Nachi
hi worm, many ISPs
ISP filt
filter ICMP ttraffic.
ffi
So ping can not work, but traceroute is ok
19ms
get-request
get-response
get response Port 161
SNMP manager
get-next-request
SNMP agent
get-response Port 161
set-request
get-response Port 161
Monitoring
Optimiization
Bas
Performance
seline
management
Detection