Changes between Version 3 and Version 4 of GENIExperimenter/Tutorials/SystematicExprCaseStudy/SmallTopoQuagga/Execute

Timestamp:

06/27/16 18:39:26 (8 years ago)

Author:

pjayanth@bbn.com

Comment:

--

GENIExperimenter/Tutorials/SystematicExprCaseStudy/SmallTopoQuagga/Execute

@@ -178 +178 @@
 From the `traceroute` result above, we know that from `client` to `server`, the path is `client` --> `router-1` --> `router-2` --> `router-3` --> `server`
 
-Now let's try some failure events and see how many updates occurs at a particular router, and we select `router-1` to view the updates, and trigger the failures at `router-2`.
-
- * Login to `router-1` and start the script (i.e., `xorp_log.sh`) that periodically tracking the routing table updates. If there is no change, you will see ''No Change'' from the terminal. Here we run the script for 60 seconds. The script captures the routing table every 1 second. 
- 
-{{{
-xuanliu@router-1:~$ cd /local/xorp_run
-xuanliu@router-1:/local/xorp_run$ /bin/bash xorp_log.sh 60 1
-/local/xorp_run/logs/rt-change.csv
-07-01-2014-18-28-28
-Create the folder for routing table logs
-/local/xorp_run/logs/xorp-rtable_07-01-2014-18-28-28.txt
-07-01-2014-18-28-28 1404239308
-
-No Change
-
-No Change
-
-No Change
-
-......
-}}}
+Now let's try some failure events and see how many updates occurs at a particular router, and we select `Client` to view the updates, and trigger the failures at `router-2`.
+
 
  * Bring down the interface at router-2
 
- We can make the link between `router-1` and `router-2` fail by bringing down the corresponding interface on `router-2`. While running `xorp_log.sh` at `router-1`, we disable the virtual interface at `router-2`, which is associated with the virtual link (`192.168.1.0/24`) to `router-1`.  
- Use `/sbin/ifconfig` to find the name of that interface.
-
-{{{
-xuanliu@router-2:~$ /sbin/ifconfig
-eth0      Link encap:Ethernet  HWaddr 02:6c:4e:0a:be:dc  
-          inet addr:172.17.1.19  Bcast:172.31.255.255  Mask:255.240.0.0
-          inet6 addr: fe80::6c:4eff:fe0a:bedc/64 Scope:Link
-          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
-          RX packets:1298 errors:0 dropped:0 overruns:0 frame:0
-          TX packets:1309 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1000 
-          RX bytes:153645 (153.6 KB)  TX bytes:116549 (116.5 KB)
-          Interrupt:25 
-
-<snip>
-
-eth2      Link encap:Ethernet  HWaddr 02:4a:cc:17:60:44  
-          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
-          inet6 addr: fe80::4a:ccff:fe17:6044/64 Scope:Link
-          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
-          RX packets:3401 errors:0 dropped:0 overruns:0 frame:0
-          TX packets:2551 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1000 
-          RX bytes:127175180 (127.1 MB)  TX bytes:177712 (177.7 KB)
-          Interrupt:26 
-
-<snip>
-
-lo        Link encap:Local Loopback  
-          inet addr:127.0.0.1  Mask:255.0.0.0
-          inet6 addr: ::1/128 Scope:Host
-          UP LOOPBACK RUNNING  MTU:16436  Metric:1
-          RX packets:8368 errors:0 dropped:0 overruns:0 frame:0
-          TX packets:8368 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:0 
-          RX bytes:895016 (895.0 KB)  TX bytes:895016 (895.0 KB)
-}}}
-
- For example, in the above the appropriate interface is `eth2`.  So the command to bring down the interface to `router-1` is:
-{{{
-xuanliu@router-2:$ sudo ifconfig eth2 down
-}}}
-
- We can see one routing table update occurred at `router-1`:
-
-{{{
-......
-
-No Change
-
-No Change
-Files /local/xorp_run/logs/tmp.txt and /local/xorp_run/logs/last_table.txt differ
-routing table changed!
-
-No Change
-
-....
-}}}
-   
+ We can make the link between `router-1` and `router-2` fail by bringing down the corresponding interface on `router-2`. We disable the virtual interface at `router-2`, which is associated with the virtual link (`192.168.1.0/24`) to `router-1`.  
+ Use `show ip ospf interface` to find the name of that interface.
+
+{{{
+router-2.quagga.ch-geni-net.instageni.rnoc.gatech.edu(config-router)# do show ip ospf  interface  
+eth0 is up
+  ifindex 2, MTU 1500 bytes, BW 0 Kbit <UP,BROADCAST,RUNNING,MULTICAST>
+  OSPF not enabled on this interface
+eth1 is up
+  ifindex 3, MTU 1500 bytes, BW 0 Kbit <UP,BROADCAST,RUNNING,MULTICAST>
+  Internet Address 192.168.1.2/24, Broadcast 192.168.1.255, Area 0.0.0.0
+  MTU mismatch detection:enabled
+  Router ID 192.168.5.1, Network Type BROADCAST, Cost: 10
+  Transmit Delay is 1 sec, State Backup, Priority 1
+  Designated Router (ID) 192.168.10.10, Interface Address 192.168.1.1
+  Backup Designated Router (ID) 192.168.5.1, Interface Address 192.168.1.2
+  Multicast group memberships: OSPFAllRouters OSPFDesignatedRouters
+  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
+    Hello due in 5.658s
+  Neighbor Count is 1, Adjacent neighbor count is 1
+eth2 is up
+  ifindex 4, MTU 1500 bytes, BW 0 Kbit <UP,BROADCAST,RUNNING,MULTICAST>
+  Internet Address 192.168.2.1/24, Broadcast 192.168.2.255, Area 0.0.0.0
+  MTU mismatch detection:enabled
+  Router ID 192.168.5.1, Network Type BROADCAST, Cost: 10
+  Transmit Delay is 1 sec, State DR, Priority 1
+  Designated Router (ID) 192.168.5.1, Interface Address 192.168.2.1
+  Backup Designated Router (ID) 192.168.20.11, Interface Address 192.168.2.2
+  Multicast group memberships: OSPFAllRouters OSPFDesignatedRouters
+  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
+    Hello due in 0.410s
+  Neighbor Count is 1, Adjacent neighbor count is 1
+eth3 is up
+  ifindex 5, MTU 1500 bytes, BW 0 Kbit <UP,BROADCAST,RUNNING,MULTICAST>
+  Internet Address 192.168.5.1/24, Broadcast 192.168.5.255, Area 0.0.0.0
+  MTU mismatch detection:enabled
+  Router ID 192.168.5.1, Network Type BROADCAST, Cost: 10
+  Transmit Delay is 1 sec, State DR, Priority 1
+  Designated Router (ID) 192.168.5.1, Interface Address 192.168.5.1
+  Backup Designated Router (ID) 192.168.5.2, Interface Address 192.168.5.2
+  Multicast group memberships: OSPFAllRouters OSPFDesignatedRouters
+  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
+    Hello due in 4.842s
+  Neighbor Count is 1, Adjacent neighbor count is 1
+lo is up
+  ifindex 1, MTU 65536 bytes, BW 0 Kbit <UP,LOOPBACK,RUNNING>
+  OSPF not enabled on this interface
+router-2.quagga.ch-geni-net.instageni.rnoc.gatech.edu(config-router)# 
+
+}}}
+
+ For example, in the above the appropriate interface is `eth1`.  So the command to bring down the interface to `router-1` is:
+{{{
+router-2.quagga.ch-geni-net.instageni.rnoc.gatech.edu(config-router)# int eth1
+router-2.quagga.ch-geni-net.instageni.rnoc.gatech.edu(config-if)# shutdown
+
+}}}
+    
+ At this time, we can run `traceroute` from `client` to `server` again, and we see that the path is changed: `client` --> router-1 --> router-4 --> router-3 --> `server`.
+
+{{{
+root@client:~# traceroute 192.168.20.10
+traceroute to 192.168.20.10 (192.168.20.10), 30 hops max, 60 byte packets
+ 1  router-1-link-5 (192.168.10.10)  0.525 ms  0.492 ms  0.511 ms
+ 2  router-4-link-3 (192.168.4.1)  0.679 ms  0.669 ms  0.719 ms
+ 3  router-3-link-2 (192.168.3.1)  1.123 ms  1.124 ms  1.034 ms
+ 4  Server-link-6 (192.168.20.10)  1.298 ms  1.346 ms  1.380 ms
+
+}}}
+
+  
  When we bring up `eth2` at `router-2` again, we notice another routing table update at `router-1` immediately.  The command to bring the interface back up is:
 {{{
-xuanliu@router-2:$ sudo ifconfig eth2 up
-}}} 
-
-  * Make `router-2` fail. 
-   
- As we mentioned before, to emulate a node failure, we can kill the `XORP` processes to disable the routing functionality at a router.  We can use the command
-
-{{{
-ps -ef | grep xorp_ | /usr/bin/awk '{ if ( $1 == "root" ) {print "sudo kill -9 " $2}}' | sh
-}}}
-
- Now start `xorp_log.sh` again at `router-1`, and kill the `XORP` processes at `router-2`, the output from `router-1` is
-
-{{{
-......
-
-No Change
-Files /local/xorp_run/logs/tmp.txt and /local/xorp_run/logs/last_table.txt differ
-routing table changed!
-
-No Change
-
-No Change
-......
-
-}}}
-
- At this time, we can run `traceroute` from `client` to `server` again, and we see that the path is changed: `client` --> router-1 --> router-4 --> router-3 --> `server`.
-
-{{{
-xuanliu@client:~$ traceroute 192.168.20.10
-traceroute to 192.168.20.10 (192.168.20.10), 30 hops max, 60 byte packets
- 1  router-1-lan4 (192.168.10.10)  0.668 ms  0.617 ms  0.584 ms
- 2  router-4-lan3 (192.168.4.1)  1.279 ms  1.252 ms  1.220 ms
- 3  router-3-lan2 (192.168.3.2)  1.753 ms  1.733 ms  1.700 ms
- 4  server-lan5 (192.168.20.10)  2.680 ms  2.656 ms  2.624 ms
-}}}
-
- Rerun `xorp_log.sh` again at `router-1`, and restart `XORP` on `router-2`  to enable `OSPF` routing at `router-2`. 
-
-
- Start `XORP` by specifying the routing protocol configuration file. 
-{{{
-xuanliu@router-2:~$ cd /usr/local/xorp/sbin/
-xuanliu@router-2:/usr/local/xorp/sbin$ sudo ./xorp_rtrmgr -b /etc/xorp/ospfd.conf -l /tmp/xorp_rtrmgr_log -d
-}}}
-
- Verify the `XORP` process is running
-{{{
-xuanliu@router-2:/usr/local/xorp/sbin$ ps -ef | grep xorp
-root      1972     1  0 13:30 ?        00:00:02 xorp_fea
-root      1973     1  0 13:30 ?        00:00:00 xorp_rib
-root      1974     1  0 13:30 ?        00:00:00 xorp_policy
-root      1975     1  0 13:30 ?        00:00:01 xorp_ospfv2
-root      1976     1  0 13:30 ?        00:00:00 ./xorp_rtrmgr -b /etc/xorp/ospfd.conf -l /tmp/xorp_rtrmgr_log -d
-}}}
-
- We see the `OSPF` routing table updates at `router-1` this time! This is because when the `XORP` processes were started again, it sent `OSPF` `hello` messages to other routers to notify that `router-2` was up, and the `OSPF` routing table was updated at each router afterwards. 
-
-{{{
-......
-No Change
-
-No Change
-Files /local/xorp_run/logs/tmp.txt and /local/xorp_run/logs/last_table.txt differ
-routing table changed!
-
-No Change
-Files /local/xorp_run/logs/tmp.txt and /local/xorp_run/logs/last_table.txt differ
-routing table changed!
-Files /local/xorp_run/logs/tmp.txt and /local/xorp_run/logs/last_table.txt differ
-routing table changed!
-
-No Change
-Files /local/xorp_run/logs/tmp.txt and /local/xorp_run/logs/last_table.txt differ
-routing table changed!
-
-No Change
-
-No Change
-......
-
-}}}
-
-  * CSV File at router-1
-
-  For research purposes, we would like to mark down the timestamp for every second when we capture the routing table. `xorp_log.sh` actually generates a `csv` log file that stores the timestamp (in UTC) and routing table update information. To simplify the log format, we use '''1''' to represent '''There is an Update!  ''', and '''0''' for '''No Update! '''.  These `csv` files live in `/local/xorp_run/logs/rt-change_*.csv`.  A sample `csv` file can be like:
-
-{{{
-router-1,1404240360,0
-router-1,1404240362,1
-router-1,1404240363,0
-router-1,1404240365,1
-router-1,1404240366,1
-router-1,1404240368,0
-router-1,1404240369,1
-router-1,1404240371,0
-}}}
-
- In this way, we can plot figures for routing table updates over time. 
+router-2.quagga.ch-geni-net.instageni.rnoc.gatech.edu(config)# int eth1
+router-2.quagga.ch-geni-net.instageni.rnoc.gatech.edu(config-if)# no shutdown
+
+
+
+
+
+ In this way, we can see routing table updates over time.