Guys how are your skills preparations? I wish you the best in your exams. God bless.

I am discovering that RIPv2 does load balancing/sharing without specifying it in the configuration, by default provided the number of hops are equal. If the alternate fails it will keep trying it until convergence has re-occurs. It also seems convergence  time seems to be better that if the failure is after the alternate route. I have been doing these tests on a network with more than 6 hops and am now looking at the behaviour of the other protocols on this same network.

DLS0#ping
Protocol [ip]:
Target IP address:  172.30.6.2
Repeat count [5]: 200
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.101.2
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 200, 100-byte ICMP Echos to 172.30.6.2, timeout is 2 seconds:
Packet sent with a source address of 192.168.101.2
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!U!.!U!.!U!.!U!.!U!.!U!.!U!.!U!.!U!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 91 percent (182/200), round-trip min/avg/max = 17/166/219 ms
NB***
On this scenario the dls0 has analternative route and is load balancing/sharing even though nothing in

regards to that has been cofigured. Hence !U!, it woul be trying the failed route then the

alternative until it recognises that it has failed

Worked on 2nd topology last night using packet tracer. Just experimenting with eigrp.

Hi
Well, it's good, then we can use this forum for the discussions.
Thanks
Egious