IP SLA - Revision history

Admin at 05:45, 18 April 2017

2017-04-18T05:45:26Z

← Older revision		Revision as of 05:45, 18 April 2017
Line 1:		Line 1:
			Note: to experiment with IP SLA, use the [[GNS3]] software-defined networking appliance.

	=internet protocol service level agreements=		=internet protocol service level agreements=

Admin: /* Monitoring the fake traffic */

2017-04-18T05:42:09Z

Monitoring the fake traffic

← Older revision		Revision as of 05:42, 18 April 2017
Line 82:		Line 82:
	FastEthernet0/0		FastEthernet0/0
	Input Output		Input Output
	----- ---------		----- ---------

	Protocol Packet Count Packet Count Byte Count Byte Count		Protocol Packet Count Packet Count Byte Count Byte Count
	---------------------------------------------------------------------------------		---------------------------------------------------------------------------------
	telnet 70 28 4200 1974 1000		telnet 70 28 4200 1974 1000

	ssh 64 24 3840 1440 1000		ssh 64 24 3840 1440 1000

	secure-http 40 15 2400 900 1000		secure-http 40 15 2400 900 1000

	icmp 14 18 1452 1716 0		icmp 14 18 1452 1716 0

	ftp 30 15 1800 900		ftp 30 15 1800 900
	</pre>		</pre>

Admin: /* Monitoring the fake traffic */

2017-04-18T05:41:49Z

Monitoring the fake traffic

← Older revision		Revision as of 05:41, 18 April 2017
Line 82:		Line 82:
	FastEthernet0/0		FastEthernet0/0
	Input Output		Input Output
	~~—– ——~~		----- ---------

	Protocol Packet Count Packet Count Byte Count Byte Count		Protocol Packet Count Packet Count Byte Count Byte Count
	~~———————— ———————— ————————~~		---------------------------------------------------------------------------------
	telnet 70 28 4200 1974 1000		telnet 70 28 4200 1974 1000

Admin: /* Monitoring the fake traffic */

2017-04-18T05:41:15Z

Monitoring the fake traffic

← Older revision		Revision as of 05:41, 18 April 2017
Line 95:		Line 95:
	ftp 30 15 1800 900		ftp 30 15 1800 900
	</pre>		</pre>


	=Flags=		=Flags=

Admin at 05:40, 18 April 2017

2017-04-18T05:40:55Z

@@ Line 1: / Line 1: @@
 IP SLA = internet protocol service level agreements; these are used by routers to keep WANs running smoothly.
 You can use IP SLA to generate traffic between routers and create bottlenecks. This can also be simulated using the [[GNS3]] virtual networking appliance. See https://gns3vault.com/blog/gns3-ip-sla-traffic-generator/
@@ Line 68: / Line 72: @@
 ip sla monitor schedule 9 life forever start-time now
 </pre>
 {{LinuxNetworkingFlag}}
 {{NetworkMonitoringFlag}}

Admin at 05:37, 18 April 2017

2017-04-18T05:37:23Z

← Older revision		Revision as of 05:37, 18 April 2017
Line 3:		Line 3:
	You can use IP SLA to generate traffic between routers and create bottlenecks. This can also be simulated using the [[GNS3]] virtual networking appliance. See https://gns3vault.com/blog/gns3-ip-sla-traffic-generator/		You can use IP SLA to generate traffic between routers and create bottlenecks. This can also be simulated using the [[GNS3]] virtual networking appliance. See https://gns3vault.com/blog/gns3-ip-sla-traffic-generator/

			The following configuration will generate ping (ICMP), DNS, HTTP, HTTPS, Telnet, SSH and RTP traffic on a router:

			<pre>
			! ICMP Echo
			ip sla monitor 1
			type echo protocol ipIcmpEcho 192.168.23.3
			timeout 0
			frequency 9
			ip sla monitor schedule 1 start-time now life forever

			! DNS Request
			ip sla monitor 2
			type dns target-addr www.gns3vault.com name-server 192.168.23.3
			timeout 0
			frequency 9
			ip sla monitor schedule 2 start-time now life forever

			! G711 conversation
			ip sla monitor 3
			type jitter dest-ipaddr 192.168.23.3 dest-port 16384 codec g711ulaw codec-numpackets 50 codec-size 160 codec-interval 20
			timeout 0
			frequency 1
			ip sla monitor schedule 3 start-time now life forever

			! G729 conversation
			ip sla monitor 4
			type jitter dest-ipaddr 192.168.23.2 dest-port 16385 codec g729a codec-numpackets 50 codec-size 20 codec-interval 20
			timeout 0
			frequency 1
			ip sla monitor schedule 4 start-time now life forever

			! HTTP GET Traffic
			ip sla monitor 5
			type http operation get url http://192.168.23.3
			frequency 60
			ip sla monitor schedule 5 start-time now life forever

			! TCPConnect to Telnet
			ip sla monitor 6
			type tcpConnect dest-ipaddr 192.168.23.3 dest-port 23 control disable
			timeout 1000
			frequency 2
			ip sla monitor schedule 6 life forever start-time now

			! TCPConnect to HTTPS
			ip sla monitor 7
			type tcpConnect dest-ipaddr 192.168.23.3 dest-port 443 control disable
			timeout 1000
			frequency 3
			ip sla monitor schedule 7 life forever start-time now

			! TCPConnect to FTP
			ip sla monitor 8
			type tcpConnect dest-ipaddr 192.168.23.3 dest-port 21 control disable
			timeout 1000
			frequency 1
			ip sla monitor schedule 8 life forever start-time now

			! TCPConnect to SSH
			ip sla monitor 9
			type tcpConnect dest-ipaddr 192.168.23.3 dest-port 22 control disable
			timeout 1000
			frequency 2
			ip sla monitor schedule 9 life forever start-time now
			</pre>

Admin: Created page with "IP SLA = internet protocol service level agreements; these are used by routers to keep WANs running smoothly. You can use IP SLA to generate traffic between routers and creat..."

2017-04-18T05:35:47Z

Created page with "IP SLA = internet protocol service level agreements; these are used by routers to keep WANs running smoothly. You can use IP SLA to generate traffic between routers and creat..."

New page

IP SLA = internet protocol service level agreements; these are used by routers to keep WANs running smoothly.

You can use IP SLA to generate traffic between routers and create bottlenecks. This can also be simulated using the [[GNS3]] virtual networking appliance. See https://gns3vault.com/blog/gns3-ip-sla-traffic-generator/

{{LinuxNetworkingFlag}}

{{NetworkMonitoringFlag}}