Wednesday 26 September 2012
Project Meeting
Had a project meeting to discuss the debug outcomes which seemed to be conflicting., but there's need to investigate why the outputs have come out that way. When an interface is shut from the analysis it was noticed that the furthest router was taking less time than its predecessor. From the discussion it maybe due to the number of networks connected to it. The directions were changed and R2 also was slower in converging. as was R4. Further investigations are to be carried out. NTP is the other suspect, we investigated its operation in terms of monitoring the instances and we could see the diversion. If that is the case why is it only affecting when a network is disabled and not when it's enabled. Investigations need to be done ie tracing signals in and out of routers the time delays on device interfaces etc, ascertain whether that is a factor. Further analysis of the debug output is needed.
Thursday 20 September 2012
Conflicting updating times for Debug outputs EIGRP IPv6
I am discovering some inconsistencies in the duration which the update is being propagated thru the network. I was expecting that the times will flow smoothly from R1 --> R2-->R3-->R4 to R5, the times should increase as it move to R5. What I am noticing is in some instances the time I am getting on R5 is smaller than the router before it (R4). How can this be possible when R4 is the one which is updating R5???.
I particularly getting this for EIGRP IPv6 debug outputs. Most of the outputs have the flow right except of a couple of outputs, What could be the reasons if any? Check your e-mails for the debug outputs and the network topology .
I particularly getting this for EIGRP IPv6 debug outputs. Most of the outputs have the flow right except of a couple of outputs, What could be the reasons if any? Check your e-mails for the debug outputs and the network topology .
Wednesday 19 September 2012
IPv6 EIGRP debug output
I have been analyzing the debug output of EIGRP IPv6 and am not sure which times to take. The time when the DLS1 interface was shut or enabled in written before the debug output. The first output was somehow simple because I have taken the time when the route has been added to the Routing Information base. On the 2nd output was the tricky one , what I have considered is when FEC0::6:0/112 has been deleted. The logic being that , this when this route is being removed from the table because it can not be accessed due to a shut down interface. I stand to be corrected. The duration taken for each route to be removed or added is just below each output.
Interface fa0/1 was enabled on DLS1 @ 11:59:55.422
Sep 19 11:59:57.738: IPv6-EIGRP(0:20): Processing incoming UPDATE packet
Sep 19 11:59:57.738: IPv6-EIGRP(0:20): Int FEC0::6:0/112 M 41666560 - 40000000 1666560 SM 41154560 - 40000000 1154560
Sep 19 11:59:57.738: IPv6-EIGRP(0:20): FEC0::6:0/112 (90/41666560) added to RIB
Sep 19 11:59:57.754: IPv6-EIGRP(0:20): FEC0::6:0/112 - do advertise out FastEthernet0/0
Sep 19 11:59:57.754: IPv6-EIGRP(0:20): Int FEC0::6:0/112 metric 41666560 - 40000000 1666560
Sep 19 11:59:57.758: IPv6-EIGRP(0:20): Int FEC0::6:0/112 metric 41666560 - 40000000 1666560
R5#
R5#
R5#
R5#11:59:57.738
R5#11:59:55.422
R5# 2.316 secs
R5#
Interface fa0/1 was shut down on DLS1 @ 12:00:38.304
Sep 19 12:00:39.422: IPv6-EIGRP(0:20): Processing incoming QUERY packet
Sep 19 12:00:39.422: IPv6-EIGRP(0:20): Int FEC0::6:0/112 M 4294967295 - 25600 4294967295 SM 4294967295 - 25600 4294967295
Sep 19 12:00:39.438: IPv6-EIGRP(0:20): FEC0::6:0/112 - do advertise out FastEthernet0/0
Sep 19 12:00:39.438: IPv6-EIGRP(0:20): Int FEC0::6:0/112 metric 4294967295 - 25600 4294967295
Sep 19 12:00:39.470: IPv6-EIGRP(0:20): Processing incoming REPLY packet
Sep 19 12:00:39.470: IPv6-EIGRP(0:20): Int FEC0::6:0/112 M 4294967295 - 25600 4294967295 SM 4294967295 - 25600 4294967295
Sep 19 12:00:39.470: IPv6-EIGRP(0:20): FEC0::6:0/112 deleted FE80::C0A8:1401(FE80::C0A8:1401)/Serial0/0/1
Sep 19 12:00:39.470: IPv6-EIGRP(0:20): FEC0::6:0/112 (90/-1) added to RIB
Sep 19 12:00:39.478: IPv6-EIGRP(0:20): Processing incoming UPDATE packet
Sep 19 12:00:39.478: IPv6-EIGRP(0:20): Int FEC0::6:0/112 M 4294967295 - 25600 4294967295 SM 4294967295 - 25600 4294967295
Sep 19 12:00:39.486: IPv6-EIGRP(0:20): FEC0::6:0/112 - do advertise out FastEthernet0/0
Sep 19 12:00:39.486: IPv6-EIGRP(0:20): Int FEC0::6:0/112 metric 4294967295 - 25600 4294967295
Sep 19 12:00:39.490: IPv6-EIGRP(0:20): FEC0::6:0/112 - do advertise out Serial0/0/1
Sep 19 12:00:39.490: IPv6-EIGRP(0:20): Int FEC0::6:0/112 metric 4294967295 - 25600 4294967295
Sep 19 12:00:39.518: IPv6-EIGRP(0:20): FEC0::6:0/112 deleted FE80::C0A8:1401(FE80::C0A8:1401)/Serial0/0/1
Sep 19 12:00:39.522: IPv6-EIGRP(0:20): FEC0::6:0/112 - not in IPv6 routing table
Sep 19 12:00:39.522: IPv6-EIGRP(0:20): Int FEC0::6:0/112 metric 4294967295 - 25600 4294967295
R5#
R5#
R5#12:00:39.470
R5#12:00:38.304
R5# 1.166 secs
R5#
Sunday 9 September 2012
Ipv6 Test with RIP
Have been working with the group yesterday, doing some test using Rip on IPV6.. We found some interesting result from the test that we have, we used couple of different debug command to capture the results, like debug ipv6 icmp, debug ipv6 rip etc.. We have collect all the output through txt file and now we try to analyze the output from all the test that we have done to get the average convergence time as our best result, we also play around with the bandwidth but it was no effect on rip.
TEVITA
TEVITA
Monday 27 August 2012
Test on MD5
The last two days I have been conducting tests on topology 1 on all three routing protocols (RIPv2, EIGRP and OSPF) Tests have been carried out on protocols without authentication and with authentication MD5. I am trying to to build up my test results which I have lost. . I have been running debug commands to see what the protocols would be doing during the recalculation of an alternate route.
I will also use GNS3 to try and compare the outputs and another issue is the ability to use wireshark on the serial interfaces which can help understand the debug outputs.
Currently I am doing the analysis on the debug outputs -its time consuming .
I will also use GNS3 to try and compare the outputs and another issue is the ability to use wireshark on the serial interfaces which can help understand the debug outputs.
Currently I am doing the analysis on the debug outputs -its time consuming .
Thursday 23 August 2012
Analysis of RIPv2 outputs Authentication vs Non-Authentication
Last Wednesday I carried out tests on Topology 1 to compare the convergence speed difference if any between a network with authentication and that without. I am doing an analysis of the results., my opinion before the test was that convergence speed for network with authentication would have slower convergence. But results should reveal the correct opinion.
Tuesday 14 August 2012
Bug
Disaster, 50% of my flash drive has been wiped of several folders in the lab, on computer on position 8. including my project folder. All my configurations and outputs I had from February 2012. I am now looking into my backup which may not be up to date but may give me some where to start from. What a dull day for me,....
That's a bad news, and good to know so that we don't have to use that PC and backup our data all the times.. We have to all bring up the files that we have to see which one that we don't have so we can work on it again and to catch up with the rest of the project too..
Tevita
That's a bad news, and good to know so that we don't have to use that PC and backup our data all the times.. We have to all bring up the files that we have to see which one that we don't have so we can work on it again and to catch up with the rest of the project too..
Tevita
Debug outputs
EIGRP IPv6 Debug on 3 routers
R2 serial int 1/1 shut down
09:30:59.997 time when shut
09:31:02.957 confirmed link
down on the router itself
R1receives query packet on int.
fec0::3:0/112 Link-coal address
fe80::172:16:4:2
09:31:26.633
09:31:41.181 second query
processing
09:31:41.277 confirmed down
removed from table
R3 receives holding time expiry
09:31:25.253
09:31:46.017 finally confirmed
down
To calculate the time taken to
process change= 09:31:46.017 minus 09:30:59.997secs
Which equals 46.026seconds.
This the time taken for the routers to have the same information –convergence
of the network.
Monday 13 August 2012
Syslog server
The version which we have or using is a free version hence has limited number of logs it can record. It records only 40 to 50 , which is not very useful when running debug commands on routers. The version of the Sylog server which is paid for has 1000 to 5000 logs. This makes it difficult to monitor the activities of routers during change in the network, need an alternative so that we can compare the speed. Currently I have been using capture text on each router running the debug command. Got a lot of outputs which I am analyzing.
On the other down side weekend access to the lab is limited upto 1830hrs Sunday and Saturday was ok , seems we have issues of closing times which are different from those scheduled for us. Disappointed last Sunday for my targeted aims were not achieved due to the early closure. Needs addressing.
On the other down side weekend access to the lab is limited upto 1830hrs Sunday and Saturday was ok , seems we have issues of closing times which are different from those scheduled for us. Disappointed last Sunday for my targeted aims were not achieved due to the early closure. Needs addressing.
Saturday 11 August 2012
Syslog
Thanks guys for today and see you guys tomorrow again..
Today NTP finally works on our second topology. We configured a syslog server but we encounter a problem while running debug command, look forward to see whats the problem tomorrow. See you guys
Tevita
Today NTP finally works on our second topology. We configured a syslog server but we encounter a problem while running debug command, look forward to see whats the problem tomorrow. See you guys
Tevita
Friday 10 August 2012
Project progress:File transfer TFTP server
A file of 2 MB (chap.ppt) has been copied from a TFTP server (PC connected to ALS2 with IP address 172.30.20.20) to the flash of switch DLS1 using RIPv2, EIGRP and OSPF.
The following topology has been used for this experimentation:
The results have been surprising as it will be explain case to case:
Scenario 1: Using default behaviour of topology
--------------------------------------------------
A shown in the above results, the packet has been transferred through the Etherchannel link which is the fastest and the shortest link compared to the link via routers.
The expectation was confirm that EIGRP has the highest rate compared to others topology, but surprisingly the rate was almost the same in all cases.
Scenario 2: Blocking Etherchannel (port-channel 2)
---------------------------------------------------------------
As shown in the above results, the transfer has take much longer than the one using the Etherchannel link.
But this didn't change that the transfer rate is almost the same for the 3 protocols.
The following shows the path taken by the packet in this case:
DLS1#traceroute 172.30.20.20 (Path takenby packet when port-channel 2 disabled)
Type escape sequence to abort.
Tracing the route to 172.30.20.20
1 192.168.1.1 0 msec 8 msec 0 msec
2 166.56.1.2 8 msec 16 msec 9 msec
3 160.45.34.2 33 msec 26 msec 33 msec
4 172.16.2.2 42 msec 42 msec 34 msec
5 164.24.5.2 58 msec 59 msec 50 msec
6 172.30.1.2 59 msec 59 msec 50 msec
7 172.30.20.20 59 msec 59 msec 50 msec
Scenario 3: Blocking Etherchannel during transfer
------------------------------------------------------------
From these outputs, we can notice that the packet has been dropped in all protocols.
The routers couldn't adapt to topology change, they couldn't relearn a new path
Scenario 4: Etherchannel reenabled during tranfer
---------------------------------------------------------
The following topology has been used for this experimentation:
The results have been surprising as it will be explain case to case:
Scenario 1: Using default behaviour of topology
--------------------------------------------------
|
|
Test 1: ----------------------------------------------- DLS1#copy tftp://172.30.20.20/chap.ppt flash: Destination filename [chap.ppt]? Accessing tftp://172.30.20.20/chap.ppt... Loading chap.ppt from 172.30.20.20 (via Port-channel2): !!!!!!!!! [OK - 2112000 bytes] |
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash:
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via Port-channel2): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 31.667 secs (66694 bytes/sec)
|
|
|
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash:
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via Port-channel2): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 30.980 secs (68173 bytes/sec)
|
|
----------------------------------------------------------
DLS1#copy tftp://172.30.20.20/chap.ppt flash:
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via Port-channel2): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 31.541 secs (66960 bytes/sec)
|
|
|
|
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via Port-channel2): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 31.575 secs (66888 bytes/sec)
|
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash: (Test 2)
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via Port-channel2): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 31.029 secs (68065 bytes/sec)
|
A shown in the above results, the packet has been transferred through the Etherchannel link which is the fastest and the shortest link compared to the link via routers.
The expectation was confirm that EIGRP has the highest rate compared to others topology, but surprisingly the rate was almost the same in all cases.
Scenario 2: Blocking Etherchannel (port-channel 2)
---------------------------------------------------------------
|
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash:
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via FastEthernet0/5): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 1279.682 secs (1650 bytes/sec)
|
|
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash:
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via FastEthernet0/5): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 1279.707 secs (1650 bytes/sec)
|
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash:
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via FastEthernet0/5): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 1279.775 secs (1650 bytes/sec)
|
|
|
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash: (Test 3)
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via FastEthernet0/5): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 1280.043 secs (1650 bytes/sec)
|
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash: (Test 4)
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via FastEthernet0/5): !!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 1279.724 secs (1650 bytes/sec)
|
As shown in the above results, the transfer has take much longer than the one using the Etherchannel link.
But this didn't change that the transfer rate is almost the same for the 3 protocols.
The following shows the path taken by the packet in this case:
DLS1#traceroute 172.30.20.20 (Path takenby packet when port-channel 2 disabled)
Type escape sequence to abort.
Tracing the route to 172.30.20.20
1 192.168.1.1 0 msec 8 msec 0 msec
2 166.56.1.2 8 msec 16 msec 9 msec
3 160.45.34.2 33 msec 26 msec 33 msec
4 172.16.2.2 42 msec 42 msec 34 msec
5 164.24.5.2 58 msec 59 msec 50 msec
6 172.30.1.2 59 msec 59 msec 50 msec
7 172.30.20.20 59 msec 59 msec 50 msec
Scenario 3: Blocking Etherchannel during transfer
------------------------------------------------------------
|
|
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via Port-channel2): !!
*Mar 1 05:59:42.822: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/4, changed state to down
<Output omitted>
*Mar 1 05:59:44.072: %LINK-3-UPDOWN: Interface Port-channel2, changed state to
down... [timed out]
|
|
|
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via Port-channel2): !!!
*Mar 1 01:37:50.230: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/3, changed state to down
<Output Omitted>
*Mar 1 01:37:51.488: %DUAL-5-NBRCHANGE: EIGRP-IPv4:(20) 20: Neighbor 10.0.0.2 (
Port-channel2) is down: interface down... [timed out]
|
|
OSPF
|
*Mar 1 03:12:29.225: %OSPF-5-ADJCHG: Process 1, Nbr 172.30.55.250 on Port-chann
el2 from LOADING to FULL, Loading Done
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via Port-channel2): !!
*Mar 1 03:12:46.086: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/3, changed state to down
<Output Omitted>
*Mar 1 03:12:47.135: %OSPF-5-ADJCHG: Process 1, Nbr 172.30.55.250 on Port-chann
el2 from FULL to DOWN, Neighbor Down: Interface down or detached... [timed out]
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash:
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via FastEthernet0/5): !
*Mar 1 06:15:15.711: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state t
o up
*Mar 1 06:15:15.836: %LINK-3-UPDOWN: Interface FastEthernet0/4, changed state t
o up
*Mar 1 06:15:16.717: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/3, changed state to up
*Mar 1 06:15:16.843: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/4, changed state to up
*Mar 1 06:15:17.640: %LINK-3-UPDOWN: Interface Port-channel2, changed state to
up
*Mar 1 06:15:18.647: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-chann
el2, changed state to up!!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 110.654 secs (19087 bytes/sec)
| |
DLS1#copy tftp://172.30.20.20/chap.ppt flash:
Destination filename [chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via FastEthernet0/5): !!
*Mar 1 01:43:59.857: %LINK-3-UPDOWN: Interface FastEthernet0/4, changed state t
o up
*Mar 1 01:43:59.941: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state t
o up
*Mar 1 01:44:00.721: %DUAL-5-NBRCHANGE: EIGRP-IPv4:(20) 20: Neighbor 10.0.0.2 (
Port-channel2) is up: new adjacency
*Mar 1 01:44:00.948: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/3, changed state to up
*Mar 1 01:44:01.694: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/4, changed state to up
*Mar 1 01:44:01.770: %LINK-3-UPDOWN: Interface Port-channel2, changed state to
up
*Mar 1 01:44:02.776: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-chann
el2, changed state to up!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 200.446 secs (10537 bytes/sec)
| |
OSPF
|
DLS1#copy tftp://172.30.20.20/chap.ppt flash:.
Destination filename [./chap.ppt]?
Accessing tftp://172.30.20.20/chap.ppt...
Loading chap.ppt from 172.30.20.20 (via FastEthernet0/5): !!
*Mar 1 03:18:40.337: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state t
o up
*Mar 1 03:18:40.547: %LINK-3-UPDOWN: Interface FastEthernet0/4, changed state t
o up
*Mar 1 03:18:41.344: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/3, changed state to up
*Mar 1 03:18:41.553: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/4, changed state to up
*Mar 1 03:18:42.250: %LINK-3-UPDOWN: Interface Port-channel2, changed state to
up
*Mar 1 03:18:43.256: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-chann
el2, changed state to up
*Mar 1 03:19:27.263: %OSPF-5-ADJCHG: Process 1, Nbr 172.30.55.250 on Port-chann
el2 from LOADING to FULL, Loading Done!!!!!!!
[OK - 2112000 bytes]
2112000 bytes copied in 245.963 secs (8587 bytes/sec)
|
Packet has been transferred with port-channel 2 disabled on DLS2. During transfer, port-channel 2
has been reenabled.
Packet changed the path and took the fastest path (Etherchannel)
Note that the difference on the transfer rate on the 3 routnng protocols is only due to the difference of haw fast the Etherchannel has been reenalbled, not to the fact that one routing could be faster the the others.
Note that OSPF with different area (area 100 and 200 has been also tested with the same result as the other protocols
Wednesday 8 August 2012
Next meeting
Hope to see you guys on Saturday to fix some problems that we have on our projects, like configure NTP on ipv6 as I haven't manage to make it work..
Tevita
Tevita
Ipv6 config
Started working on ipv6 on topology one, still have some issues on my configuration but have to finish if off today and what happened..
EIGRP on IPv6
Got IPv6 going on the 1st topology , global addresses are needed for the routers to exchange routes. No global addresses routers will only be aware of the directly connected networks. I still failing to get NTP working. Thinking of trying multicasting to the respective routers.....may be it will work.
Tuesday 31 July 2012
IPv6 EIGRP NTP
Well, the configuration did not go as smooth as I expected , encountered several issues , eg like some interfaces shutting down. The problem I have to research on is configuring NTP for IPv6 seems to be a little tricky requires ntp version. ????
Saturday 28 July 2012
IPv6 Bandwidth effects (EIGRP)
I have noted that different versions or setings of routers have a certain bandwidth level cut off where when reached routes will be changed.That's routes will be selected or changed when they drop below these levels. So far I have noted 3 different cutoff levels 64kbps available bandwidth of 37kbps ; 1180kbp available bandwidth of 885kbps and recently 125ks available bandwidth of 93kbps. This raises a question , is it because of the version of IOS or is it anything to do with router settings? This may need further investigations.
Friday 27 July 2012
Running IPv6 networks
Today I will be running tests on test scenarios -IPv6 network. I will test effects of load and bandwidth on convergence speed.
Thursday 19 July 2012
Does Md5 affect convergence?
The ping tests were done on the same topology used on (14/07/12) my last post.
Md5 Authentication
on Routers in same EIGRP AS seems not to change the speed of convergence. As revealed by the ping results
above and wireshark results. There’s need to check whether it does on the other
routing protocols. I think it does on RIP.
Can you guys run the tests on the topology attached previously.
Wireshark was enabled to capture results on R2 interface S1/1 and R4 int S1/0 .
200 Pings were being sent from R5 to Lo1 address 1.1.1.1 of R1
Interface S1/0 of R2 would be shut during the pings.
This should be repeated 10 times and all results captured.
I will wait to hear your findings as well.
Thanks
Saturday 14 July 2012
I have found
out that the convergence time of the routers in the above topology can be calculated from the number of
pings lost multiplied by 2 which is the specified timeout. In the first output we lost 8pings x
2 =16seconds. I verified this also from the wireshark output which gave me 15.8840seconds. It took about 16seconds after
shutting down R2’s serial interface S1/2 for the routers to notice that and
begin to use an alternate route to R1’s loopback network 1.1.1.1 via R3. (R5Ã R4Ã R3Ã R2Ã R1)
Bandwidth
I have noted
that bandwidth would not affect path selection until the available bandwidth on
the preferred route falls below 885kps. If it does not fall below that the
preferred route would remain in use regardless of the huge differences say
7500kbps vs 885kbps.
From the
above outputs does not show any significant differences on the speed of
convergence at the moment. It needs to be tested with traffic flowing in the
network to figure out if the results will be different.
Sorry I have had difficulties in posting all my test result I will put them on google docs.
Thursday 12 July 2012
Progress
Well, I have been doing tests on the first/initial topology for the last two days. I will be posting the results, am currently analyzing the results so that I can put the results together with brief observations. I have been trying to rectify our last shortfall on our last capture of results- I have greatly improved that. I will also run the other routing protocols to capture the results for analysis.
Another disappointing issue is access to the lab, losing a lot of time waiting for security to open up lab- cards no working. I have experienced that today and Anthony was letting me in during the day for last two days (mon and Tues)
Tuesday 10 July 2012
Yesterday work progress
Hi Egious we finally fixed and configured topology 3 right after you left but we didn't have enough time to do more testing as they lock down the whole 3rd floor last night.
Tevita
Tevita
Topology 3
Thanks guys for the time and effort that we have to meet up today and work on our project, still a bit of a problem to fix on our traffic gen but I hope we can make it work next time we meet, thank you
Tevita
Tevita
Monday 9 July 2012
Topology 3 IPv6 basic config
Hi guys
These basic configurations are going to help us continue our Topology 3 IPv6
The IPv4 to IPv6 conversion have been made using the following page:
http://www.subnetonline.com/pages/subnet-calculators/ipv4-to-ipv6-converter.php
hostname ALS1
no ipv6 domain-lookup
interface Port-channel1
switchport mode trunk
flowcontrol send off
no shut
interface FastEthernet0/1
switchport mode trunk
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport mode trunk
channel-group 1 mode desirable
no shut
interface FastEthernet0/3
switchport access vlan 10
switchport mode access
no shut
interface FastEthernet0/4
switchport access vlan 20
switchport mode access
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan55
ipv6 address fe80:0:0:0:0:0:c0a8:3701/120
no shut
-------------------------------------------------------------------------------
hostname ALS2
no ipv6 domain-lookup
interface Port-channel1
switchport mode trunk
flowcontrol send off
no shut
interface FastEthernet0/1
switchport mode trunk
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport mode trunk
channel-group 1 mode desirable
no shut
interface FastEthernet0/3
switchport access vlan 20
switchport mode access
no shut
interface FastEthernet0/4
switchport access vlan 25
switchport mode access
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan55
ipv6 address fe80:0:0:0:0:0:ac1e:3701/120
no shut
------------------------------------------------------------------------------------------------
hostname ALS3
no ipv6 domain-lookup
interface FastEthernet0/1
switchport mode trunk
no shut
interface FastEthernet0/2
switchport mode trunk
no shut
interface FastEthernet0/3
switchport access vlan 15
switchport mode access
no shut
interface FastEthernet0/4
switchport access vlan 10
switchport mode access
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan10
ipv6 address 2002:0:0:0:0:0:aa10:a01/120
no shutdown
interface Vlan15
ipv6 address 2002:0:0:0:0:0:aa10:f01/120
no shut
------------------------------------------------------------------------------------------------
hostname DLS1
ipv6 routing
no ipv6 domain-lookup
interface Port-channel1
switchport trunk encapsulation dot1q
no shut
interface Port-channel2
no switchport
ipv6 address fe80:0:0:0:0:0:a00:1/120
no shut
interface FastEthernet0/1
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/3
no switchport
channel-group 2 mode desirable
no shut
interface FastEthernet0/4
no switchport
channel-group 2 mode desirable
no shut
interface FastEthernet0/5
no switchport
ipv6 address fe80:0:0:0:0:0:c0a8:102/120
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan10
ipv6 address fe80:0:0:0:0:0:c0a8:afa/120
no shut
interface Vlan15
ipv6 address fe80:0:0:0:0:0:c0a8:ffa/120
no shut
interface Vlan20
ipv6 address fe80:0:0:0:0:0:c0a8:14fa/120
no shut
interface Vlan25
ipv6 address fe80:0:0:0:0:0:c0a8:19fa/120
no shut
interface Vlan55
ipv6 address fe80:0:0:0:0:0:c0a8:37fa/120
no shut
--------------------------------------------------------------------------------------
hostname DSL2
ipv6 routing
no ipv6 domain-lookup
interface Port-channel1
switchport trunk encapsulation dot1q
no shut
interface Port-channel2
no switchport
ipv6 address fe80:0:0:0:0:0:a00:2/120
no shut
interface FastEthernet0/1
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/3
no switchport
channel-group 2 mode desirable
no shut
interface FastEthernet0/4
no switchport
channel-group 2 mode desirable
no shut
interface FastEthernet0/5
no switchport
ipv6 address fe80:0:0:0:0:0:ac1e:102/120
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan10
ipv6 address fe80:0:0:0:0:0:ac1e:afa/120
no shut
interface Vlan15
ipv6 address fe80:0:0:0:0:0:ac1e:ffa/120
no shut
interface Vlan20
ipv6 address fe80:0:0:0:0:0:ac1e:14fa/120
no shut
interface Vlan25
ipv6 address fe80:0:0:0:0:0:ac1e:19fa/120
no shut
interface Vlan55
ip6 address fe80:0:0:0:0:0:ac1e:37fa/120
no shut
-----------------------------------------------------------------------------------
hostname DSL3
ipv6 routing
no ipv6 domain-lookup
interface Port-channel1
no shut
interface FastEthernet0/1
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/5
no switchport
ipv6 address 2002:0:0:0:0:0:aa10:1e02/120
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan10
ipv6 address 2002:0:0:0:0:0:aa10:afa/120
no shut
interface Vlan15
ipv6 address 2002:0:0:0:0:0:aa10:ffa/120
no shut
interface Vlan20
ipv6 address 2002:0:0:0:0:0:aa10:14fa/120
no shut
interface Vlan25
ipv6 address 2002:0:0:0:0:0:aa10:19fa/120
no shut
interface Vlan55
ipv6 address 2002:0:0:0:0:0:aa10:37fa/120
no shut
--------------------------------------------------------------------
hostname R1
no ipv6 domain lookup
interface FastEthernet0/0
ipv6 address fe80:0:0:0:0:0:c0a8:101/120
no shut
interface Serial0/0/0
ipv6 address 2002:0:0:0:0:0:a638:100/126
clock rate 64000
no shut
-------------------------------------------------------------------------
hostname R2
no ipv6 domain lookup
interface Serial0/0/0
ipv6 address 2002:0:0:0:0:0:a638:102/126
no shut
interface Serial0/2/0
ipv6 address fe80:0:0:0:0:0:ac10:301/126
clock rate 64000
no shut
interface Serial0/2/1
ipv6 address 2002:0:0:0:0:0:a02d:2201/126
no shut
-------------------------------------------------------------------------------
hostname R4
no ipv6 domain lookup
interface FastEthernet0/0
ipv6 address 2002:0:0:0:0:0:aa10:1e01/120
no shut
interface Serial0/0/0
ipv6 address 2002:0:0:0:0:0:a02d:2202/126
clock rate 64000
no shut
interface Serial0/0/1
ipv6 address fe80:0:0:0:0:0:ac10:201/126
clock rate 64000
no shut
interface Serial0/2/1
ipv6 address fe80:0:0:0:0:0:ac10:401/126
no shut
-------------------------------------------------------------
hostname R5
interface Serial0/0/1
ipv6 address fe80:0:0:0:0:0:ac10:402/126
clock rate 64000
no shut
interface Serial0/2/0
ipv6 address fe80:0:0:0:0:0:ac10:101/126
no shut
--------------------------------------------------------------------
hostname R6
interface Serial0/0/0
ipv6 address fe80:0:0:0:0:0:ac10:102/126
clock rate 64000
no shut
interface Serial0/0/1
ipv6 address 2002:0:0:0:0:0:a418:501/126
no shut
interface Serial0/2/1
ipv6 address fe80:0:0:0:0:0:ac10:202/126
no shut
-----------------------------------------------------------------------------
hostname R7
interface FastEthernet0/0
ipv6 address fe80:0:0:0:0:0:ac1e:101/120
no shut
interface Serial0/0/0
ipv6 address 2002:0:0:0:0:0:a418:502/126
clock rate 64000
no shut
These basic configurations are going to help us continue our Topology 3 IPv6
The IPv4 to IPv6 conversion have been made using the following page:
http://www.subnetonline.com/pages/subnet-calculators/ipv4-to-ipv6-converter.php
hostname ALS1
no ipv6 domain-lookup
interface Port-channel1
switchport mode trunk
flowcontrol send off
no shut
interface FastEthernet0/1
switchport mode trunk
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport mode trunk
channel-group 1 mode desirable
no shut
interface FastEthernet0/3
switchport access vlan 10
switchport mode access
no shut
interface FastEthernet0/4
switchport access vlan 20
switchport mode access
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan55
ipv6 address fe80:0:0:0:0:0:c0a8:3701/120
no shut
-------------------------------------------------------------------------------
hostname ALS2
no ipv6 domain-lookup
interface Port-channel1
switchport mode trunk
flowcontrol send off
no shut
interface FastEthernet0/1
switchport mode trunk
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport mode trunk
channel-group 1 mode desirable
no shut
interface FastEthernet0/3
switchport access vlan 20
switchport mode access
no shut
interface FastEthernet0/4
switchport access vlan 25
switchport mode access
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan55
ipv6 address fe80:0:0:0:0:0:ac1e:3701/120
no shut
------------------------------------------------------------------------------------------------
hostname ALS3
no ipv6 domain-lookup
interface FastEthernet0/1
switchport mode trunk
no shut
interface FastEthernet0/2
switchport mode trunk
no shut
interface FastEthernet0/3
switchport access vlan 15
switchport mode access
no shut
interface FastEthernet0/4
switchport access vlan 10
switchport mode access
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan10
ipv6 address 2002:0:0:0:0:0:aa10:a01/120
no shutdown
interface Vlan15
ipv6 address 2002:0:0:0:0:0:aa10:f01/120
no shut
------------------------------------------------------------------------------------------------
hostname DLS1
ipv6 routing
no ipv6 domain-lookup
interface Port-channel1
switchport trunk encapsulation dot1q
no shut
interface Port-channel2
no switchport
ipv6 address fe80:0:0:0:0:0:a00:1/120
no shut
interface FastEthernet0/1
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/3
no switchport
channel-group 2 mode desirable
no shut
interface FastEthernet0/4
no switchport
channel-group 2 mode desirable
no shut
interface FastEthernet0/5
no switchport
ipv6 address fe80:0:0:0:0:0:c0a8:102/120
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan10
ipv6 address fe80:0:0:0:0:0:c0a8:afa/120
no shut
interface Vlan15
ipv6 address fe80:0:0:0:0:0:c0a8:ffa/120
no shut
interface Vlan20
ipv6 address fe80:0:0:0:0:0:c0a8:14fa/120
no shut
interface Vlan25
ipv6 address fe80:0:0:0:0:0:c0a8:19fa/120
no shut
interface Vlan55
ipv6 address fe80:0:0:0:0:0:c0a8:37fa/120
no shut
--------------------------------------------------------------------------------------
hostname DSL2
ipv6 routing
no ipv6 domain-lookup
interface Port-channel1
switchport trunk encapsulation dot1q
no shut
interface Port-channel2
no switchport
ipv6 address fe80:0:0:0:0:0:a00:2/120
no shut
interface FastEthernet0/1
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/3
no switchport
channel-group 2 mode desirable
no shut
interface FastEthernet0/4
no switchport
channel-group 2 mode desirable
no shut
interface FastEthernet0/5
no switchport
ipv6 address fe80:0:0:0:0:0:ac1e:102/120
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan10
ipv6 address fe80:0:0:0:0:0:ac1e:afa/120
no shut
interface Vlan15
ipv6 address fe80:0:0:0:0:0:ac1e:ffa/120
no shut
interface Vlan20
ipv6 address fe80:0:0:0:0:0:ac1e:14fa/120
no shut
interface Vlan25
ipv6 address fe80:0:0:0:0:0:ac1e:19fa/120
no shut
interface Vlan55
ip6 address fe80:0:0:0:0:0:ac1e:37fa/120
no shut
-----------------------------------------------------------------------------------
hostname DSL3
ipv6 routing
no ipv6 domain-lookup
interface Port-channel1
no shut
interface FastEthernet0/1
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/2
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
no shut
interface FastEthernet0/5
no switchport
ipv6 address 2002:0:0:0:0:0:aa10:1e02/120
no shut
vlan 10
exit
vlan 15
exit
vlan 20
exit
vlan 25
exit
vlan 55
exit
interface Vlan10
ipv6 address 2002:0:0:0:0:0:aa10:afa/120
no shut
interface Vlan15
ipv6 address 2002:0:0:0:0:0:aa10:ffa/120
no shut
interface Vlan20
ipv6 address 2002:0:0:0:0:0:aa10:14fa/120
no shut
interface Vlan25
ipv6 address 2002:0:0:0:0:0:aa10:19fa/120
no shut
interface Vlan55
ipv6 address 2002:0:0:0:0:0:aa10:37fa/120
no shut
--------------------------------------------------------------------
hostname R1
no ipv6 domain lookup
interface FastEthernet0/0
ipv6 address fe80:0:0:0:0:0:c0a8:101/120
no shut
interface Serial0/0/0
ipv6 address 2002:0:0:0:0:0:a638:100/126
clock rate 64000
no shut
-------------------------------------------------------------------------
hostname R2
no ipv6 domain lookup
interface Serial0/0/0
ipv6 address 2002:0:0:0:0:0:a638:102/126
no shut
interface Serial0/2/0
ipv6 address fe80:0:0:0:0:0:ac10:301/126
clock rate 64000
no shut
interface Serial0/2/1
ipv6 address 2002:0:0:0:0:0:a02d:2201/126
no shut
-------------------------------------------------------------------------------
hostname R4
no ipv6 domain lookup
interface FastEthernet0/0
ipv6 address 2002:0:0:0:0:0:aa10:1e01/120
no shut
interface Serial0/0/0
ipv6 address 2002:0:0:0:0:0:a02d:2202/126
clock rate 64000
no shut
interface Serial0/0/1
ipv6 address fe80:0:0:0:0:0:ac10:201/126
clock rate 64000
no shut
interface Serial0/2/1
ipv6 address fe80:0:0:0:0:0:ac10:401/126
no shut
-------------------------------------------------------------
hostname R5
interface Serial0/0/1
ipv6 address fe80:0:0:0:0:0:ac10:402/126
clock rate 64000
no shut
interface Serial0/2/0
ipv6 address fe80:0:0:0:0:0:ac10:101/126
no shut
--------------------------------------------------------------------
hostname R6
interface Serial0/0/0
ipv6 address fe80:0:0:0:0:0:ac10:102/126
clock rate 64000
no shut
interface Serial0/0/1
ipv6 address 2002:0:0:0:0:0:a418:501/126
no shut
interface Serial0/2/1
ipv6 address fe80:0:0:0:0:0:ac10:202/126
no shut
-----------------------------------------------------------------------------
hostname R7
interface FastEthernet0/0
ipv6 address fe80:0:0:0:0:0:ac1e:101/120
no shut
interface Serial0/0/0
ipv6 address 2002:0:0:0:0:0:a418:502/126
clock rate 64000
no shut
Thursday 5 July 2012
Monday 2 July 2012
Hi guys, I think I have found an open source traffic generator which works with WireShark according to writeup. I will try to see if it can work on our topology. You can also try it.http://ostinato.org/ It might be what we need for now.
Sunday 1 July 2012
What next
My suggestion is to do same scenarios we did before with exactly the same tests, but this time using IPv6.
This is a web site we can use to convert easily our IPv4 address to IPv6:
http://www.subnetonline.com/pages/subnet-calculators/ipv4-to-ipv6-converter.php
This is a web site we can use to convert easily our IPv4 address to IPv6:
http://www.subnetonline.com/pages/subnet-calculators/ipv4-to-ipv6-converter.php
Progress report
This week has been used to work on our topology 3 that has been covered more than other topologies, but later on each of these topology will be sufficiently covered to get convenient testing results so that the default behaviour can be can be mastered, and modified to improve the performance of each routing protocol.
EIGRP, RIPv2 and OSPF with all devices
in area 0 and next, with all devices in different area.
I.
OSPF
|
Case 1: OSPF (with only Area 0)
|
|||
|
R1#show run
interface FastEthernet0/0
ip address 192.168.1.1 255.255.255.0
interface Serial0/0/0
ip address 166.56.1.1 255.255.255.252
clock rate 64000
interface Serial0/0/1
no ip address
no shutdown
clock rate 125000
router ospf 1
network 166.56.1.0 0.0.0.3 area 0
network 192.168.1.0 0.0.0.255 area 0
|
R2#show run
interface Serial0/0/0
ip address 166.56.1.2 255.255.255.252
interface Serial0/2/0
ip address 172.16.3.1 255.255.255.252
clock rate 64000
interface Serial0/2/1
ip address 160.45.34.1 255.255.255.252
router ospf 1
network 160.45.34.0 0.0.0.3 area 0
network 166.56.1.0 0.0.3 area 0
|
R4#sh run
interface FastEthernet0/0
ip address 170.16.30.1 255.255.255.0
duplex auto
speed auto
interface Serial0/0/0
ip address 160.45.34.2 255.255.255.252
no fair-queue
clock rate 64000
interface Serial0/0/1
ip address 172.16.2.1 255.255.255.252
clock rate 64000
interface Serial0/2/1
ip address 172.16.4.1 255.255.255.252
router ospf 1
network 160.45.34.0 0.0.0.3 area 0
network 172.16.2.0 0.0.0.3 area 0
network 172.16.4.0 0.0.0.3 area 0
network 170.16.30.0 0.0.0.255 area 0
|
R5#show run
interface Serial0/0/0
no ip address
shutdown
no fair-queue
clock rate 64000
interface Serial0/0/1
ip address 172.16.4.2 255.255.255.252
clock rate 64000
interface Serial0/2/0
ip address 172.16.1.1 255.255.255.252
router ospf 1
network 172.16.1.0 0.0.0.3 area 0
network 172.16.4.0 0.0.0.3 area 0
|
|
R6#sh run
interface FastEthernet0/0
no ip address
no shutdown
interface Serial0/0/0
ip address 172.16.1.2 255.255.255.252
clock rate 64000
interface Serial0/0/1
ip address 164.24.5.1 255.255.255.252
interface Serial0/2/1
ip address 172.16.2.2 255.255.255.252
router ospf 1
network 164.24.5.0 0.0.0.3 area 0
network 172.16.1.0 0.0.0.3 area 0
network 172.16.2.0 0.0.0.3 area 0
|
R7#sh run
interface FastEthernet0/0
ip address 172.30.1.1 255.255.255.0
interface Serial0/0/0
ip address 164.24.5.2 255.255.255.252
clock rate 64000
router ospf 1
network 164.24.5.0 0.0.0.3 area 0
network 172.30.1.0 0.0.0.255 area 0
|
ALS1#sh run
interface Port-channel1
switchport mode trunk
flowcontrol send off
interface FastEthernet0/1
switchport mode trunk
channel-group 1 mode desirable
interface FastEthernet0/2
switchport mode trunk
channel-group 1 mode desirable
interface FastEthernet0/3
switchport access vlan 10
switchport mode access
interface FastEthernet0/4
switchport access vlan 20
switchport mode access
interface Vlan55
ip address 192.168.55.1 255.255.255.0
|
ALS2#sh run
interface Port-channel1
switchport mode trunk
flowcontrol send off
interface FastEthernet0/1
switchport mode trunk
channel-group 1 mode desirable
interface FastEthernet0/2
switchport mode trunk
channel-group 1 mode desirable
interface FastEthernet0/3
switchport access vlan 20
switchport mode access
interface FastEthernet0/4
switchport access vlan 25
switchport mode access
interface Vlan55
ip address 172.30.55.1 255.255.255.0
|
|
ALS3#show run
Same as EIGRP
|
DLS2#show run
router ospf 1
network 10.0.0.0 0.0.0.255 area 0
network 172.30.1.0 0.0.0.255 area 0
network 172.30.10.0 0.0.0.255 area 0
network 172.30.15.0 0.0.0.255 area 0
network 172.30.20.0 0.0.0.255 area 0
network 172.30.25.0 0.0.0.255 area 0
network 172.30.55.0 0.0.0.255 area 0
|
DLS2#show run
router ospf 1
network 10.0.0.0 0.0.0.255 area 0
network 192.168.1.0 0.0.0.255 area 0
network 192.168.10.0 0.0.0.255 area 0
network 192.168.15.0 0.0.0.255 area 0
network 192.168.20.0 0.0.0.255 area 0
network 192.168.25.0 0.0.0.255 area 0
network 192.168.55.0 0.0.0.255 area 0
|
DLS3#show run
router ospf 1
network 170.16.30.0 0.0.0.255 area 0
network 170.16.20.0 0.0.0.255 area 0
network 170.16.10.0 0.0.0.255 area 0
network 170.16.15.0 0.0.0.255 area 0
network 170.16.25.0 0.0.0.255 area 0
network 170.16.55.0 0.0.0.255 area 0
|
Testing Scenarios:
In the following steps, simple testing
tools have been used to check the path taken by a packet and see which
manipulation is the most beneficial for the routing protocol:
* CLI with "traceroute "command and "ping .... repeat" command
* Wireshark
More advanced tools will be used later
to generate specific packets.
a. Using Default
behaviour
* DLS2#traceroute
192.168.10.10 (Host connected to ALS1)
Type escape sequence to abort.
Tracing the route to 192.168.10.10
1 10.0.0.1 0 msec 0 msec 8 msec
2 192.168.10.10 0 msec 0 msec 9
msec
* DLS2#traceroute
192.168.10.10
Type escape sequence to abort.
Tracing the route to 192.168.10.10
1 172.30.1.1 0 msec 0 msec 0
msec
2 164.24.5.1 17 msec 17 msec 16
msec
3 172.16.2.1 26 msec 33 msec 25
msec
4 160.45.34.1 42 msec 42 msec 42
msec
5 166.56.1.1 50 msec 59 msec 50
msec
6 192.168.1.2 59 msec 51 msec 58
msec
7 192.168.10.10 59 msec 50 msec
51 msec
DLS2#
From the above output, we notice that
the preferred path for a packet forwarded from Host connected to ALS2 to Host
connected to ALS1 is through ether channel link:
DLS2#ping 192.168.10.10 repeat 2000
Type escape sequence to abort.
Sending 2000, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<output ommited>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent
(2000/2000), round-trip min/avg/max = 1/2/9 ms
DLS2#ping 192.168.10.10 repeat 2000
(Port Channel disabled)
Type escape sequence to abort.
Sending 2000, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output Ommited>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.
*Mar 1 02:50:46.961:
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/4, changed state to down
*Mar 1 02:50:47.003:
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/3, changed state to down
*Mar 1 02:50:47.011:
%LINEPROTO-5-UPDOWN: Line protocol on Interface Port-chann
el2, changed state to down
*Mar 1 02:50:47.959:
%LINK-3-UPDOWN: Interface FastEthernet0/4, changed state t
o down
*Mar 1 02:50:48.009:
%LINK-3-UPDOWN: Interface FastEthernet0/3, changed state t
o down
*Mar 1 02:50:48.009:
%LINK-3-UPDOWN: Interface Port-channel2, changed state to
down
*Mar 1 02:50:48.009:
%OSPF-5-ADJCHG: Process 1, Nbr 192.168.55.250 on Port-chan
nel2 from FULL to DOWN, Neighbor Down:
Interface down or detached...!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output Ommited>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 99 percent (1996/2000),
round-trip min/avg/max = 1/44/143 ms
DLS2#
DLS2#ping 192.168.10.10 repeat 500
Type escape sequence to abort.
Sending 500, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
Success rate is 100 percent (500/500),
round-trip min/avg/max = 109/112/135 ms
DLS2#ping 192.168.10.10 repeat 500 (R6
S0/2/1 disabled)
Type escape sequence to abort.
Sending 500, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!..U.U.!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
Success rate is 98 percent (494/500),
round-trip min/avg/max = 109/133/160 ms
DLS2#
|
Case 2: OSPF (with only Area
100, 200 and 300)
Note: This table will show only
OSPF configuration, the rest of configurations are the same as Case 1
|
|||
|
R1#show run
router ospf 1
log-adjacency-changes
network 166.56.1.0 0.0.0.3 area 100
network 192.168.1.0 0.0.0.255 area 100
|
R2#show run
router ospf 1
log-adjacency-changes
network 160.45.34.0 0.0.0.3 area 0
network 166.56.1.0 0.0.0.3 area 100
|
R4#sh run
router ospf 1
log-adjacency-changes
network 160.45.34.0 0.0.0.3 area 0
network 170.16.30.0 0.0.0.255 area 200
network 172.16.2.0 0.0.0.3 area 0
network 172.16.4.0 0.0.0.3 area 0
|
R5#show run
No change (Area 0 only)
|
|
R6#sh run
No change (Area 0 only)
|
R7#sh run
router ospf 1
log-adjacency-changes
network 164.24.5.0 0.0.0.3 area 0
network 172.30.1.0 0.0.0.255 area 300
|
ALS1#sh run
No change
|
ALS2#sh run
No change
|
|
ALS3#show run
No change
|
DLS2 #show run
ip routing
interface Port-channel1
switchport trunk encapsulation dot1q
interface Port-channel2
no switchport
ip address 10.0.0.2 255.255.255.0
interface FastEthernet0/1
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
interface FastEthernet0/2
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
interface FastEthernet0/3
no switchport
no ip address
channel-group 2 mode desirable
interface FastEthernet0/4
no switchport
no ip address
channel-group 2 mode desirable
interface FastEthernet0/5
no switchport
ip address 172.30.1.2 255.255.255.0
interface Vlan10
ip address 172.30.10.250 255.255.255.0
interface Vlan15
ip address 172.30.15.250 255.255.255.0
interface Vlan20
ip address 172.30.20.250 255.255.255.0
interface Vlan25
ip address 172.30.25.250 255.255.255.0
interface Vlan55
ip address 172.30.55.250 255.255.255.0
router ospf 1
network 10.0.0.0 0.0.0.255 area 300
network 172.30.1.0 0.0.0.255 area 300
network 172.30.10.0 0.0.0.255 area 300
network 172.30.15.0 0.0.0.255 area 300
network 172.30.20.0 0.0.0.255 area 300
network 172.30.25.0 0.0.0.255 area 300
network 172.30.55.0 0.0.0.255 area 300
|
DLS1#show run
ip routing
interface Port-channel1
switchport trunk encapsulation dot1q
interface Port-channel2
no switchport
ip address 10.0.0.1 255.255.255.0
interface FastEthernet0/1
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
interface FastEthernet0/2
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
interface FastEthernet0/3
no switchport
no ip address
channel-group 2 mode desirable
interface FastEthernet0/4
no switchport
no ip address
channel-group 2 mode desirable
interface FastEthernet0/5
no switchport
ip address 192.168.1.2 255.255.255.0
interface Vlan10
ip address 192.168.10.250 255.255.255.0
interface Vlan15
ip address 192.168.15.250 255.255.255.0
interface Vlan20
ip address 192.168.20.250 255.255.255.0
interface Vlan25
ip address 192.168.25.250 255.255.255.0
interface Vlan55
ip address 192.168.55.250 255.255.255.0
router ospf 1
network 10.0.0.0 0.0.0.255 area 100
network 192.168.1.0 0.0.0.255 area 100
network 192.168.10.0 0.0.0.255 area 100
network 192.168.15.0 0.0.0.255 area 100
network 192.168.20.0 0.0.0.255 area 100
network 192.168.25.0 0.0.0.255 area 100
network 192.168.55.0 0.0.0.255 area 100
|
DLS3#show run
ip routing
interface Port-channel1
interface FastEthernet0/1
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
interface FastEthernet0/2
switchport trunk encapsulation dot1q
channel-group 1 mode desirable
interface FastEthernet0/3
interface FastEthernet0/4
interface FastEthernet0/5
no switchport
ip address 170.16.30.2 255.255.255.0
interface Vlan1
no ip address
shutdown
interface Vlan10
ip address 170.16.10.250 255.255.255.0
interface Vlan15
ip address 170.16.15.250 255.255.255.0
interface Vlan20
ip address 170.16.20.250 255.255.255.0
interface Vlan25
ip address 170.16.25.250 255.255.255.0
interface Vlan55
ip address 170.16.55.250 255.255.255.0
router ospf 1
network 170.16.30.0 0.0.0.255 area 200
network 170.16.20.0 0.0.0.255 area 200
network 170.16.10.0 0.0.0.255 area 200
network 170.16.15.0 0.0.0.255 area 200
network 170.16.25.0 0.0.0.255 area 200
network 170.16.55.0 0.0.0.255 area 200
|
Different test scenarios have been
made, using default behaviour of the routing protocol, or modifying some of the
characteristics (bandwidth, cost)
Most of the modification have been done
on R6, R5 and R4 so that packets could be brought to choose a defined path and
check which of the combination is the fastest.
But before applying any modification,
the default interfaces status have been verified:
|
R6#sh int s0/0/0
Serial0/0/0 is up, line protocol is up
Hardware is GT96K Serial
Internet address is 172.16.1.2/30
MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
reliability 255/255,
txload 1/255, rxload 1/255
<Output omitted>
|
R6#
R6#sh int s0/2/1
Serial0/2/1 is up, line protocol is up
Hardware is GT96K Serial
Internet address is 172.16.2.2/30
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255,
txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set
<output omitted>
Available Bandwidth 1158 kilobits/sec
|
Testing Scenarios:
In the following steps, simple testing
tools have been used to check the path taken by a packet and see which
manipulation is the most benefique for the routing protocol.
Examples of tools used: Wireshark. CLI
(ping ... repeat, traceroute, ip route)
More advanced tools will be used later
to generate specific packets.
a. Using Default
behaviour
* R6#sh ip route
<Output omitted>
O
160.45.34.0 [110/128] via 172.16.2.1, 00:00:36, Serial0/2/1
Note: Cost = 128 to reach network
160.45.34.0 via 172.16.2.1
* R6#show ip route
(R6 s0/2/1 shutdown)
<Output omitted>
O
160.45.34.0 [110/909] via 172.16.1.1, 00:00:15, Serial0/0/0
Note: Cost = 909 to reach network
160.45.34.0 via 172.16.1.1
The first output in the next page
(MSDOS) indicates that path taken by packet using default bandwidth link R4 -
R6 (1544 kbps) and R5 - R6 (128 kbps), and R5 - R4 (1544 kbps) from Host
192.168.10.10 to host 172.30.20.20 is DLS1 - R1 - R2 - R4 - R6 - R7 - DLS2
* DSL2#ping
192.168.10.10 repeat 2000 (Default band:R4-R6 1544kbps;
Type escape sequence to abort.
Sending 2000, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output omitted>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent
(2000/2000), round-trip min/avg/max = 109/112/143 ms
* DSL2#ping
192.168.10.10 repeat 2000 (R4-R6 band 64; R6 s0/0/0 shut)
Type escape sequence to abort.
Sending 2000, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.U.U.!!!!!!!!!!!!!!!!
<output omitted>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 99 percent (1995/2000),
round-trip min/avg/max = 109/116/167 ms
b. Link R4 - R6
changed to 64 kbps
The second output indicates that
packet has changed path using DLS1 - R1 - R2 - R4 - R5 - R6 - R7 -
DLS2, preferring a faster link.
DSL2#ping
192.168.10.10 repeat 2000 (link R4-R6 band changed to 64kbps)
Type escape sequence to abort.
Sending 2000, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output omitted>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent
(2000/2000), round-trip min/avg/max = 134/139/185 ms
c. Changing cost from
128 to 1000 for R6 S0/2/1
* R6#sh ip route
<Output omitted>
O
160.45.34.0 [110/909] via 172.16.1.1, 00:00:51, Serial0/0/0
Note: when cost change
from 128 to 1000 for R6 s0/2/1, new path is 172.16.1.1 with cost 909
Verification of configured cost
:
R6# sh ip ospf int s0/2/1
Process ID 1, Router ID 172.16.2.2,
Network Type POINT_TO_POINT, Cost: 1000
* R6#sh ip route
(R6 s0/2/1 cost set to 1000; R6 s0/0/0 to 500 and R5 s0/0/1 to 500)
O
160.45.34.0 [110/1064] via 172.16.2.1, 00:00:09, Serial0/2/1
[110/1064] via 172.16.1.1, 00:00:09, Serial0/0/0
* DSL2#ping
192.168.10.10 repeat 2000 (R6 s0/2/1 cost changed to 1000)
Type escape sequence to abort.
Sending 2000, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output ommited)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent
(2000/2000), round-trip min/avg/max = 134/139/185 ms
* DSL2#ping
192.168.10.10 repeat 2000 (Link R5 - R6 cost = 500; R4- R5 Cost = 500)
Type escape sequence to abort.
Sending 2000, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output omitted>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent
(2000/2000), round-trip min/avg/max = 117/125/160 ms
Note that with the case of different
area, the ether channel failed to forward packets. Is it the true behaviour or
is it a result of misconfiguration? The question will be minded later.
d. Wireshark
Statistics summary in brief
|
2000 pings with R6 - R5
shutdown; band = 64 kbps
|
2000 ping with R6 S0/2/1 Cost
set to 1000
|
2000 ping with R6 S0/2/1 Cost =
1000; R5-R6 Cost = 500; R4-R5 Cost = 500
|
|
Time:
* First Packet: 2012-06-18 20:14:21
*Last Packet: 2012-06-18 20:19:18
* Elapsed: 00:04:57
Traffic captured:
*
Packets:
3865
* Between first and last
packet:
297.022 sec
* Avg packets/sec: 13.013
|
Time:
* First Packet: 2012-06-18 21:26:50
*Last Packet: 2012-06-18 21:31:56
* Elapsed: 00:05:05
Traffic captured:
*
Packets:
4249
* Between first and last
packet:
305.468 sec
* Avg packets/sec: 13.910
|
Time:
* First Packet: 2012-06-18 21:53:19
*Last Packet: 2012-06-18 21:58:53
* Elapsed: 00:05:34
Traffic captured:
*
Packets:
4270
* Between first and last
packet:
334.080 sec
* Avg packets/sec: 12.781
|
II. EIGRP
|
EIGRP
Note: This table will show only
EIGRP configuration, the rest of configurations are the same as OSPF
|
|||
|
R1#show run
router eigrp 20
network 166.56.1.0 0.0.0.3
network 192.168.0.0
network 192.168.0.0 0.0.255.255
no auto-summary
|
R2#show run
router eigrp 20
network 160.45.34.0 0.0.0.3
network 166.56.1.0 0.0.0.3
network 172.16.3.0 0.0.0.3
no auto-summary
|
R4#sh run
router eigrp 20
network 160.45.34.0 0.0.0.3
network 170.16.30.0 0.0.0.255
network 172.16.2.0 0.0.0.3
network 172.16.4.0 0.0.0.3
no auto-summary
|
R5#show run
router eigrp 20
network 172.16.1.0 0.0.0.3
network 172.16.4.0 0.0.0.3
no auto-summary
|
|
R6#sh run
router eigrp 20
network 164.24.5.0 0.0.0.3
network 172.16.1.0 0.0.0.3
network 172.16.2.0 0.0.0.3
no auto-summary
|
R7#sh run
router eigrp 20
network 164.24.0.0
network 172.30.0.0
no auto-summary
|
ALS1#sh run
Same as OSPF
|
ALS2#sh run
Same as OSPF
|
|
ALS3#show run
Same as OSPF
|
DSL2#sh run
router eigrp 20
no auto-summary
network 10.0.0.0 0.0.0.255
network 172.30.0.0
|
DLS1#show run
router eigrp 20
no auto-summary
network 10.0.0.0 0.0.0.255
network 192.168.0.0 0.0.255.255
|
DSL3#show run
router eigrp 20
network 170.16.10.0 0.0.0.255
network 170.16.15.0 0.0.0.255
network 170.16.20.0 0.0.0.255
network 170.16.25.0 0.0.0.255
network 170.16.30.0 0.0.0.255
network 170.16.55.0 0.0.0.255
|
Testing Scenarios:
Two different testing tools have been
used to test network convergence:
* CLI with "traceroute "command and "ping .... repeat" command
* Wireshark
a.
A traceroute
command from DLS2 to host connected to ALS1 (192.168.10.10) has shown that the preferred
route for packets is through the ether channel media, the more faster link in
our network.
* DSL2#traceroute
192.168.10.10 (Host connected to ALS1)
Type escape sequence to abort.
Tracing the route to 192.168.10.10
1 10.0.0.1 0 msec 0 msec 9 msec
2 192.168.10.10 0 msec 9 msec 0
msec
Because our network is redundant, the
port channel disabled doesn't block our packet to get to destination. But which
path will be used depend on the metric on router R6. The smallest metric will
be preferred to a higher one as shown in the routing table on router R6.
* R6#sh ip route
<Output omitted>
160.45.0.0/16 is variably subnetted, 2
subnets, 2 masks
D
160.45.0.0/16 [90/2681856] via 172.16.2.1, 01:45:55, Serial0/2/1
The preferred path for the packet will
be then through R7 - R6 - R4 - R2 - R1 - DLS1.
The following command confirm this
preference
* DSL2#traceroute
192.168.10.10 (with port-channel disabled)
Type escape sequence to abort.
Tracing the route to 192.168.10.10
1 172.30.1.1 0 msec 0 msec 0
msec
2 164.24.5.1 17 msec 8 msec 8
msec
3 172.16.2.1 34 msec 25 msec 25
msec
4 160.45.34.1 42 msec 42 msec 42
msec
5 166.56.1.1 50 msec 50 msec 59
msec
6 192.168.1.2 50 msec 50 msec 59
msec
7 192.168.10.10 51 msec 67 msec
51 msec
* DSL2#ping
192.168.10.10 repeat 10000
Type escape sequence to abort.
Sending 10000, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output omitted>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent
(10000/10000), round-trip min/avg/max = 1/2/9 ms
DSL2#
DSL2#ping 192.168.10.10 repeat 10000
(with port channel on DLS1 shut)
Type escape sequence to abort.
Sending 10000, 100-byte ICMP Echos to
192.168.10.10, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output omitted>
!!!!!!!!!!!.
*Mar 1 08:50:39.740:
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/3, changed state to down
*Mar 1 08:50:39.782:
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/4, changed state to down
*Mar 1 08:50:39.791:
%LINEPROTO-5-UPDOWN: Line protocol on Interface Port-chann
el2, changed state to down
*Mar 1 08:50:40.747:
%LINK-3-UPDOWN: Interface FastEthernet0/3, changed state t
o down
*Mar 1 08:50:40.789:
%LINK-3-UPDOWN: Interface FastEthernet0/4, changed state t
o down
*Mar 1 08:50:40.789:
%LINK-3-UPDOWN: Interface Port-channel2, changed state to
down
*Mar 1 08:50:40.806:
%DUAL-5-NBRCHANGE: EIGRP-IPv4:(20) 20: Neighbor 10.0.0.1 (
Port-channel2) is down: interface
down.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!
<Output omitted>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 99 percent
(9998/10000), round-trip min/avg/max = 1/93/160 ms
Wireshark Statistics
Summary in brief
|
10000 pings DLS2 to Host
connected to ALS1
|
10000 pings DLS2 to Host
connected to ALS1 (port-channel disabled)
|
|
Time:
* First Packet: 2012-06-16 21:54:10
*Last Packet: 2012-06-16 21:54:48
* Elapsed: 00:00:38
Traffic captured:
* Packets: 20032
* Between first and last packet: 38.007 sec
* Avg packets/sec: 527.059
|
Time:
* First Packet: 2012-06-16 22:05:58
* Last Packet: 2012-06-16 22:22:29
* Elapsed: 00:16:30
Traffic captured:
* Packets: 20910
* Between first and last packet: 990.154
* Avg packets/sec: 21.118
|
From these statistics, we can notice
that the ether cannel link is much more faster than the redundant link.
It is able to process 527 packets per second when the redundant link need the
same time to process only 21 packets.
Note that the redundant link here is R7
- R6 - R4 - R2 - R1 - DLS1
Compared to OSPF with the
parameters parameters used (default or modified), from the Wireshark
statistics captured from these scenario, we can notice that EIGRP process in
average much more packets per second. But this result is not enough to build a
general conclusion.
More tests need to be done.