Wednesday, February 25, 2015

Verify the output 2 of RIP v2


 


R2#debug ip rip ?
  database  RIP database events
  events    RIP protocol events
  trigger   RIP trigger extension
  <cr>

R2#debug ip rip
RIP protocol debugging is on

R2#
*Mar  1 00:13:10.147: RIP: received v2 update from 10.1.12.1 on FastEthernet0/0
*Mar  1 00:13:10.151:      1.1.1.0/24 via 0.0.0.0 in 1 hops

R2#
*Mar  1 00:13:13.891: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)
*Mar  1 00:13:13.891: RIP: build update entries
*Mar  1 00:13:13.891:   1.1.1.0/24 via 0.0.0.0, metric 2, tag 0
*Mar  1 00:13:13.891:   3.3.3.0/24 via 0.0.0.0, metric 2, tag 0
*Mar  1 00:13:13.891:   10.1.12.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:13:13.891:   10.1.13.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:13:13.899: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses)
R2#
*Mar  1 00:13:15.191: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.1.13.2)
*Mar  1 00:13:15.195: RIP: build update entries
*Mar  1 00:13:15.195:   1.1.1.0/24 via 0.0.0.0, metric 2, tag 0
*Mar  1 00:13:15.199:   2.2.2.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:13:15.199:   10.1.12.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:13:15.331: RIP: received v2 update from 10.1.13.3 on FastEthernet1/0
*Mar  1 00:13:15.331:      3.3.3.0/24 via 0.0.0.0 in 1 hops
R2#
*Mar  1 00:13:25.999: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.12.2)
*Mar  1 00:13:26.003: RIP: build update entries
*Mar  1 00:13:26.003:   2.2.2.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:13:26.007:   3.3.3.0/24 via 0.0.0.0, metric 2, tag 0
*Mar  1 00:13:26.007:   10.1.13.0/24 via 0.0.0.0, metric 1, tag 0


R2#debug ip rip database

RIP database events debugging is on
R2#
*Mar  1 00:19:09.203: RIP-DB: network_update with 1.1.1.0/24 succeeds
*Mar  1 00:19:09.207: RIP-DB: adding 1.1.1.0/24 (metric 1) via 10.1.12.1 on FastEthernet0/0 to RIP database
R2#
*Mar  1 00:19:19.207: RIP-DB: network_update with 3.3.3.0/24 succeeds
*Mar  1 00:19:19.211: RIP-DB: adding 3.3.3.0/24 (metric 1) via 10.1.13.3 on FastEthernet1/0 to RIP database

R2#debug ip rip events
RIP event debugging is on
R2#
*Mar  1 00:21:06.799: RIP: received v2 update from 10.1.13.3 on FastEthernet1/0
*Mar  1 00:21:06.799: RIP: Update contains 1 routes
R2#
*Mar  1 00:21:10.047: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)
*Mar  1 00:21:10.051: RIP: Update contains 4 routes
*Mar  1 00:21:10.051: RIP: Update queued
*Mar  1 00:21:10.055: RIP: Update sent via Loopback0
*Mar  1 00:21:10.063: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses)
R2#
*Mar  1 00:21:12.275: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.12.2)
*Mar  1 00:21:12.279: RIP: Update contains 3 routes
*Mar  1 00:21:12.279: RIP: Update queued
*Mar  1 00:21:12.283: RIP: Update sent via FastEthernet0/0
R2#
*Mar  1 00:21:16.343: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.1.13.2)
*Mar  1 00:21:16.343: RIP: Update contains 3 routes
*Mar  1 00:21:16.343: RIP: Update queued
*Mar  1 00:21:16.343: RIP: Update sent via FastEthernet1/0
R2#
*Mar  1 00:21:28.731: RIP: received v2 update from 10.1.12.1 on FastEthernet0/0
*Mar  1 00:21:28.735: RIP: Update contains 1 routes
R2#

*Mar  1 00:21:35.191: RIP: received v2 update from 10.1.13.3 on FastEthernet1/0

Verify the output 1 of RIP v2


R2#sh run | s rip
router rip
 version 2
 network 2.0.0.0
 network 10.0.0.0
 no auto-summary


R3#sh run |  s rip
router rip
 version 2
 network 3.0.0.0
 network 10.0.0.0
 no auto-summary


R3#sh ip route rip

     
1.0.0.0/24 is subnetted, 1 subnets
R       1.1.1.0 [120/2] via 10.1.13.2, 00:00:08, FastEthernet0/0
     
2.0.0.0/24 is subnetted, 1 subnets
R       2.2.2.0 [120/1] via 10.1.13.2, 00:00:08, FastEthernet0/0
     10.0.0.0/24 is subnetted, 2 subnets
R       10.1.12.0 [120/1] via 10.1.13.2, 00:00:08, FastEthernet0/0


R2#sh ip rip database
1.0.0.0/8    auto-summary
1.1.1.0/24
    [1] via 10.1.12.1, 00:00:15, FastEthernet0/0
2.0.0.0/8    auto-summary
2.2.2.0/24    directly connected, Loopback0
3.0.0.0/8    auto-summary
3.0.0.0/8
    [1] via 10.1.13.3, 00:01:12, FastEthernet1/0
3.3.3.0/24
    [1] via 10.1.13.3, 00:00:15, FastEthernet1/0
10.0.0.0/8    auto-summary
10.1.12.0/24    directly connected, FastEthernet0/0
10.1.13.0/24    directly connected, FastEthernet1/0

R2#sh ip protocols

Routing Protocol is "rip"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Sending updates every 30 seconds, next due in 7 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240
  Redistributing: rip
  Default version control: send version 2, receive version 2
    Interface             Send  Recv  Triggered RIP  Key-chain
    FastEthernet0/0       2     2
    FastEthernet1/0       2     2
    Loopback0               2     2
  Automatic network summarization is not in effect
  Maximum path: 4
  Routing for Networks:
    2.0.0.0
    10.0.0.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    10.1.13.3            120      00:00:22
    10.1.12.1            120      00:00:25   

Distance: (default is 120)

Tuesday, February 24, 2015

RIP v2 update

Updates every 30 seconds , offset of +/- 0 to 5 seconds , means trigger anywhere  between 25 and 35 seconds 





R2#debug ip rip events

RIP event debugging is on

R2#
*Mar  1 00:21:06.799: RIP: received v2 update from 10.1.13.3 on FastEthernet1/0
*Mar  1 00:21:06.799: RIP: Update contains 1 routes
R2#
*Mar  1 00:21:10.047: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)
*Mar  1 00:21:10.051: RIP: Update contains 4 routes
*Mar  1 00:21:10.051: RIP: Update queued
*Mar  1 00:21:10.055: RIP: Update sent via Loopback0
*Mar  1 00:21:10.063: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses)
R2#
*Mar  1 00:21:12.275: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.12.2)
*Mar  1 00:21:12.279: RIP: Update contains 3 routes
*Mar  1 00:21:12.279: RIP: Update queued
*Mar  1 00:21:12.283: RIP: Update sent via FastEthernet0/0
R2#
*Mar  1 00:21:16.343: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.1.13.2)
*Mar  1 00:21:16.343: RIP: Update contains 3 routes
*Mar  1 00:21:16.343: RIP: Update queued
*Mar  1 00:21:16.343: RIP: Update sent via FastEthernet1/0
R2#
*Mar  1 00:21:28.731: RIP: received v2 update from 10.1.12.1 on FastEthernet0/0
*Mar  1 00:21:28.735: RIP: Update contains 1 routes
R2#
*Mar  1 00:21:35.191: RIP: received v2 update from 10.1.13.3 on FastEthernet1/0
*Mar  1 00:21:35.195: RIP: Update contains 1 routes

*Mar  1 00:21:36.111: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)
*Mar  1 00:21:36.115: RIP: Update contains 4 routes
*Mar  1 00:21:36.115: RIP: Update queued
*Mar  1 00:21:36.119: RIP: Update sent via Loopback0
*Mar  1 00:21:36.127: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses)
R2#
*Mar  1 00:21:38.963: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.12.2)
*Mar  1 00:21:38.963: RIP: Update contains 3 routes
*Mar  1 00:21:38.963: RIP: Update queued
*Mar  1 00:21:38.967: RIP: Update sent via FastEthernet0/0
R2#
*Mar  1 00:21:43.411: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.1.13.2)
*Mar  1 00:21:43.411: RIP: Update contains 3 routes
*Mar  1 00:21:43.411: RIP: Update queued
*Mar  1 00:21:43.411: RIP: Update sent via FastEthernet1/0
R2#
*Mar  1 00:21:57.363: RIP: received v2 update from 10.1.12.1 on FastEthernet0/0
*Mar  1 00:21:57.367: RIP: Update contains 1 routes

Monday, February 23, 2015

RIP v2 question 5

Is auhentication support in RIP v1 ?

For RIP v2 authentication


Create 30 loopbacks on R1

R2(config)#key chain ?
WORD Key-chain name

R2(config)#key chain AUTH
R2(config-keychain)#key ?
<0-2147483647> Key identifier

R2(config-keychain)#key 123
R2(config-keychain-key)#key-string ?
0 Specifies an UNENCRYPTED password will follow
7 Specifies a HIDDEN password will follow
LINE The UNENCRYPTED (cleartext) user password

R2(config-keychain-key)#key-string 123
R2(config-keychain-key)#exi
R2(config-keychain)#exi

R2(config)#int f 1/0

R2(config-if)#ip rip authentication ?
  key-chain  Authentication key-chain
  mode       Authentication mode

R2(config-if)#ip rip authentication key-chain AUTH


R3(config)#key chain AUTH
R3(config-keychain)#key 123
R3(config-keychain-key)#key-string 123
R3(config-keychain-key)#end
R3(config)#int f 0/0
R3(config-if)#ip rip authentication key-chain AUTH

(Note: after running authentication, RIP  update only contains 24 routes per packet instead of               25)

R3#debug ip rip events
RIP event debugging is on
R3#
*Mar 1 00:30:05.975: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.13.3) - suppressing null update
R3#
*Mar 1 00:30:24.727: RIP: received v2 update from 10.1.13.2 on FastEthernet0/0
*Mar 1 00:30:24.739: RIP: Update contains 24 routes
*Mar 1 00:30:24.743: RIP: received v2 update from 10.1.13.2 on FastEthernet0/0
*Mar 1 00:30:24.747: RIP: Update contains 6 routes

R3#debug ip rip
RIP protocol debugging is on

R3#debug ip rip events
RIP event debugging is on


R3#
*Mar  1 00:19:15.555: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.13.3)
*Mar  1 00:19:15.559: RIP: build update entries - suppressing null update
*Mar  1 00:19:15.679: RIP: received packet with text authentication 123
*Mar  1 00:19:15.679: RIP: received v2 update from 10.1.13.2 on FastEthernet0/0
*Mar  1 00:19:15.683:      1.1.1.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.683:      2.2.2.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.687:      3.3.3.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.691:      4.4.4.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.691:      5.5.5.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.695:      6.6.6.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.699:      7.7.7.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.699:      8.8.8.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.703:      9.9.9.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.707:      10.1.12.0/24 via 0.0.0.0 in 1 hops
*Mar  1 00:19:15.707:      10.10.10.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.711:      11.11.11.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.711:      12.12.12.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.715:      14.14.14.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.719:      15.15.15.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.719:      16.16.16.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.723:      17.17.17.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.727:      18.18.18.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.727:      19.19.19.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.731:      20.20.20.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.735:      21.21.21.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.735:      22.22.22.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.739:      23.23.23.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.743:      24.24.24.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.743: RIP: Update contains 24 routes
*Mar  1 00:19:15.743: RIP: received packet with text authentication 123
*Mar  1 00:19:15.743: RIP: received v2 update from 10.1.13.2 on FastEthernet0/0
*Mar  1 00:19:15.743:      25.25.25.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.743:      26.26.26.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.743:      27.27.27.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.743:      28.28.28.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.743:      29.29.29.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.743:      30.30.30.0/24 via 0.0.0.0 in 2 hops
*Mar  1 00:19:15.743: RIP: Update contains 6 routes

For RIPv1 authentication


RIP v1 does not support authentication

R1(config)#key chain new
R1(config-keychain)#key 1
R1(config-keychain-key)#key-string 123
R1(config-keychain-key)#exi
R1(config-keychain)#exi
R1(config)#int f 0/0
R1(config-if)#ip rip auth key-chain new

R2(config)#key chain new
R2(config-keychain)#key 1
R2(config-keychain-key)#key-string 123
R2(config-keychain-key)#end
R2#conf t
R2(config)#int f 0/0
R2(config-if)#ip rip auth key-chain new

R2#debug ip rip
RIP protocol debugging is on
R2#
*Mar  1 00:04:13.811: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (10.1.12.2)
*Mar  1 00:04:13.815: RIP: build update entries
*Mar  1 00:04:13.815:   network 2.0.0.0 metric 1
*Mar  1 00:04:13.819:   network 3.0.0.0 metric 2
*Mar  1 00:04:13.819:   subnet 10.1.13.0 metric 1
*Mar  1 00:04:13.823: RIP: sending v1 update to 255.255.255.255 via Loopback0 (2.2.2.2)
*Mar  1 00:04:13.823: RIP: build update entries
*Mar  1 00:04:13.827:   network 1.0.0.0 metric 2
*Mar  1 00:04:13.827:   network 3.0.0.0 metric 2
*Mar  1 00:04:13.831:   network 10.0.0.0 metric 1
*Mar  1 00:04:13.855: RIP: sending v1 update to 255.255.255.255 via FastEthernet1/0 (10.1.13.2)
R2#
*Mar  1 00:04:13.859: RIP: build update entries
*Mar  1 00:04:13.859:   network 1.0.0.0 metric 2
*Mar  1 00:04:13.863:   network 2.0.0.0 metric 1
*Mar  1 00:04:13.863:   subnet 10.1.12.0 metric 1
R2#
*Mar  1 00:04:16.827: RIP: received v1 update from 10.1.13.3 on FastEthernet1/0
*Mar  1 00:04:16.831:      3.0.0.0 in 1 hops
R2#
*Mar  1 00:04:17.979: RIP: received v1 update from 10.1.12.1 on FastEthernet0/0
*Mar  1 00:04:17.983:      1.0.0.0 in 1 hops



RIP v2 question 4

 ip summary-address rip Vs no auto-summary in RIP ?



R1(config-if)#do sh ip int brief
Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0          172.16.0.1      YES NVRAM  up                    up
Loopback0                  10.1.17.1       YES NVRAM  up                    up
Loopback1                  10.1.18.1       YES NVRAM  up                    up
Loopback2                  10.1.19.1       YES NVRAM  up                    up
Loopback3                  10.1.20.1       YES NVRAM  up                    up
Loopback4                  10.1.21.1       YES NVRAM  up                    up
Loopback5                  10.1.22.1       YES NVRAM  up                    up
Loopback6                  10.1.23.1       YES NVRAM  up                    up
Loopback7                  10.1.24.1       YES NVRAM  up                    up
Loopback8                  10.1.25.1       YES NVRAM  up                    up

RIP auto-summary

R1(config-if)#do sh run | s rip
router rip
 version 2
 network 10.0.0.0
 network 172.16.0.0


R2#sh ip route | b Gate
Gateway of last resort is not set

C    172.16.0.0/16 is directly connected, FastEthernet0/0
R    10.0.0.0/8 [120/1] via 172.16.0.1, 00:00:24, FastEthernet0/0

After no auto-summary


R1#sh run | s rip
router rip
 version 2
 network 10.0.0.0
 network 172.16.0.0
 no auto-summary




R2#sh ip route | b Gate
Gateway of last resort is not set

C    172.16.0.0/16 is directly connected, FastEthernet0/0
     10.0.0.0/8 is variably subnetted, 10 subnets, 2 masks
R       10.0.0.0/8     [120/1] via 172.16.0.1, 00:01:14, FastEthernet0/0
R       10.1.25.0/24 [120/1] via 172.16.0.1, 00:00:21, FastEthernet0/0
R       10.1.24.0/24 [120/1] via 172.16.0.1, 00:00:21, FastEthernet0/0
R       10.1.19.0/24 [120/1] via 172.16.0.1, 00:00:21, FastEthernet0/0
R       10.1.18.0/24 [120/1] via 172.16.0.1, 00:00:21, FastEthernet0/0
R       10.1.17.0/24 [120/1] via 172.16.0.1, 00:00:21, FastEthernet0/0
R       10.1.23.0/24 [120/1] via 172.16.0.1, 00:00:21, FastEthernet0/0
R       10.1.22.0/24 [120/1] via 172.16.0.1, 00:00:21, FastEthernet0/0
R       10.1.21.0/24 [120/1] via 172.16.0.1, 00:00:21, FastEthernet0/0
R       10.1.20.0/24 [120/1] via 172.16.0.1, 00:00:21, FastEthernet0/0



After manual summary


R1(config-router)#interface FastEthernet0/0

R1(config-router)#ip address 172.16.0.1 255.255.0.0

R1(config-router)# ip summary-address rip 10.1.16.0 255.255.248.0


R2#sh ip route | b Gate
Gateway of last resort is not set

C 172.16.0.0/16 is directly connected, FastEthernet0/0
10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
R 10.1.25.0/24 [120/1] via 172.16.0.1, 00:00:13, FastEthernet0/0
R 10.1.24.0/24 [120/1] via 172.16.0.1, 00:00:13, FastEthernet0/0
R 10.1.16.0/21 [120/1] via 172.16.0.1, 00:00:13, FastEthernet0/0