这个是我考CCIE r&s的时候的实验笔记,全部是基于卷一的。十分详细。喜欢可以学习一下。
CCIE r&s
基础实验一 对RIP的深入研究一
注 实验中Flody 启用了环回接口 2.2.2 .2 Opie用了3.3.3.3
一.实验目的
1.复习RIP的基本配置
2.对RIP的更新报文的研究
3.对RIP的passive interface特点的研究
二实验开始a
1.基本配置及.对RIP更新机制的研究
Andy
en
conf t
host Andy
int fa0/0
ip add 192.168.83.1 255.255.255.0
no shu
int s1/1
ip add 172.17.2.1 255.255.255.0
no shu
int s1/0
ip add 172.17.1.1 255.255.255.0
no shu
int fa0/1
ip add 192.168.12.65 255.255.255.224
no shu
int lo1
ip add 10.1.2 .1 255.255.255.0
no shu
Barney
en
conf t
host Barney
int fa0/0
ip add 192.168.83.244 255.255.255.0
no shu
int lo1
ip add 10.1.1 .1 255.255.255.0
no shu
OPie
en
conf t
host OPie
int s1/1
ip add 172.17.2.2 255.255.255.0
no shu
int lo1
ip add 10.1.3 .1 255.255.255.0
no shu
Goober
en
conf t
host Goober
int s1/0
ip add 172.17.1.2 255.255.255.0
no shu
int lo1
ip add 10.1.4 .1 255.255.255.0
no shu
Floyd
en
conf t
host Floyd
int fa0/0
ip add 192.168.12.66 255.255.255.224
no shu
int lo4
ip add 10.1.6 .1 255.255.255.0
no shu
Bea
en
conf t
host Bea
int fa0/0
ip add 192.168.12.67 255.255.255.224
no shu
int lo4
ip add 10.1.5 .1 255.255.255.0
no shu
l 在Bareny上激活RIP后 只生明环回接口时的debug ip rip event
Mar 1 00:13:33.555: RIP: add Loopback1 to RIP idb list 说明lo1 加入RIP
*Mar 1 00:13:33.559: RIP: sending request on Loopback1 to 255.255.255.255^Z向环回接口发送广播的请求报文
Barney#
*Mar 1 00:13:35.555: RIP: sending v1 flash update to 255.255.255.255 via Loopback1 ( 10.1.1 .1) - suppressing null update 向环回接口发广播更新 (这时更新为空)
l 在Bareny及其它所有路由器(除环回外)激活RIP后
Barney#
*Mar 1 00:09:47.711: RIP: add FastEthernet0/0 to RIP idb list这时fa0/0加入RIP
*Mar 1 00:09:47.715: RIP: sending request on FastEthernet0/0 to 255.255.255.255
*Mar 1 00:09:48.343: %SYS-5-CONFIG_I: Configured from console by console
*Mar 1 00:09:49.711: RIP: sending v1 flash update to 255.255.255.255 via Loopback1 ( 10.1.1 .1)
*Mar 1 00:09:49.715: RIP: Update contains 1 routes 这时发给LO1的更新变成1 包涵了fa0/0
*Mar 1 00:09:49.715: RIP: Update queued
*Mar 1 00:09:49.715: RIP: sending v1 flash update to 255.255.255.255 via FastEthernet0/0 (192.168.83.244) - suppressing null update 从fa0/0发的更新为空
*Mar 1 00:09:49.723: RIP: Update sent via Loopback1
*Mar 1 00:09:55.783: RIP: sending v1 update to 255.255.255.255 via Loopback1 ( 10.1.1 .1)
*Mar 1 00:09:55.787: RIP: Update contains 1 routes
*Mar 1 00:09:55.787: RIP: Update queued
*Mar 1 00:09:55.791: RIP: Update sent via Loopback1
*Mar 1 00:10:10.163: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.83.244)
*Mar 1 00:10:10.167: RIP: Update contains 1 routes 从fa0/0发的更新为1
*Mar 1 00:10:10.167: RIP: Update queued
*Mar 1 00:10:10.167: RIP: Update sent via FastEthernet0/0
*Mar 1 00:18:35.523: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.83.244)
*Mar 1 00:18:35.527: RIP: Update contains 1 routes
*Mar 1 00:18:35.527: RIP: Update queued
*Mar 1 00:18:35.531: RIP: Update sent via FastEthernet0/0
*Mar 1 00:18:39.911: RIP: received v1 update from 192.168.83.1 on FastEthernet0/0
*Mar 1 00:18:39.915: RIP: Update contains 2 routes
*Mar 1 00:18:41.511: RIP: sending v1 update to 255.255.255.255 via Loopback1 ( 10.1.1 .1)
*Mar 1 00:18:41.515: RIP: Update contains 3 routes
*Mar 1 00:18:41.515: RIP: Update queued
*Mar 1 00:18:41.515: RIP: Update sent via Loopback1
*Mar 1 00:32:44.523: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.83.244)
*Mar 1 00:32:44.527: RIP: Update contains 1 routes
*Mar 1 00:32:44.527: RIP: Update queued
*Mar 1 00:32:44.531: RIP: Update sent via FastEthernet0/0
*Mar 1 00:32:56.471: RIP: sending v1 update to 255.255.255.255 via Loopback1 ( 10.1.1 .1)
*Mar 1 00:32:56.475: RIP: Update contains 4 routes 这时从环回口发出的更新有4条 一条为fa0/0 的 192.168.12.0 172.17.0.0 2.0.0 .0(在flody 的环回接口 )
*Mar 1 00:32:56.475: RIP: Update queued
*Mar 1 00:32:56.475: RIP: Update sent via Loopback1
*Mar 1 00:33:05.527: RIP: received v1 update from 192.168.83.1 on FastEthernet0/0
*Mar 1 00:33:05.531: RIP: Update contains 3 routes 这时的更新有3条消息 没有fa0/0的详见包结构
*Mar 1 00:33:13.675: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.83.244)
*Mar 1 00:33:13.679: RIP: Update contains 1 routes
l Opie上的show ip rip 输出
*Mar 1 00:41:31.815: RIP: sending v1 update to 255.255.255.255 via Serial1/1 (172.17.2.2)
*Mar 1 00:41:31.815: RIP: build update entries - suppressing null update由于只有s1/1通告rip故该更新包为空
*Mar 1 00:41:42.807: RIP: received v1 update from 172.17.2.1 on Serial1/1
*Mar 1 00:41:42.811: 2.0.0 .0 in 2 hops
*Mar 1 00:41:42.811: 172.17. 1.0 in 1 hops
*Mar 1 00:41:42.815: 192.168. 12.0 in 1 hops
*Mar 1 00:41:42.815: 192.168. 83.0 in 1 hops
l Floyd上的 show ip rip 输出
*Mar 1 00:46:15.731: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.12.66)
*Mar 1 00:46:15.731: RIP: build update entries
*Mar 1 00:46:15.735: network 2.0.0 .0 metric 1
*Mar 1 00:46:20.555: RIP: sending v1 update to 255.255.255.255 via Loopback1 ( 2.2.2 .2)
*Mar 1 00:46:20.555: RIP: build update entries
*Mar 1 00:46:20.559: network 172.17.0.0 metric 1
*Mar 1 00:46:20.559: network 192.168.12.0 metric 1
*Mar 1 00:46:20.563: network 192.168.83.0 metric 1
*Mar 1 00:46:36.107: RIP: received v1 update from 192.168.12.65 on FastEthernet0/0
*Mar 1 00:46:36.111: 172.17. 0.0 in 1 hops
*Mar 1 00:46:36.111: 192.168. 83.0 in 1 hops
l Barney上的show ip rip 输出
*Mar 1 00:51:57.727: RIP: sending v1 update to 255.255.255.255 via Loopback1 ( 10.1.1 .1)
*Mar 1 00:51:57.727: RIP: build update entries 这时该更新发给lo1 所以这时
*Mar 1 00:51:57.731: network 2.0.0 .0 metric 3
*Mar 1 00:51:57.731: network 172.17.0.0 metric 1
*Mar 1 00:51:57.735: network 192.168.12.0 metric 1
*Mar 1 00:51:57.735: network 192.168.83.0 metric 1
*Mar 1 00:52:01.323: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.83.244)
*Mar 1 00:52:01.323: RIP: build update entries
*Mar 1 00:52:01.327: network 10.0.0 .0 metric 1
*Mar 1 00:52:04.791: RIP: received v1 update from 192.168.83.1 on FastEthernet0/0
*Mar 1 00:52:04.795: 2.0.0 .0 in 2 hops 这是andy发给我的更新包的内容
*Mar 1 00:52:04.795: 172.17. 0.0 in 1 hops
*Mar 1 00:52:04.799: 192.168. 12.0 in 1 hops
Barney#show ip route
R 192.168.12.0/24 [120/1] via 192.168.83.1, 00:00:07, FastEthernet0/0
R 2.0.0 .0/8 [120/2] via 192.168.83.1, 00:00:07, FastEthernet0/0
R 172.17.0.0/16 [120/1] via 192.168.83.1, 00:00:07, FastEthernet0/0
C 192.168.83.0/24 is directly connected, FastEthernet0/0
10.0.0 .0/24 is subnetted, 1 subnets
C 10.1.1 .0 is directly connected, Loopback1
l 在Opie上启用环回接口 3.3.3 .3后 debug ip rip 后
OPie#debug ip rip
RIP protocol debugging is on
OPie#
*Mar 1 01:07:07.815: RIP: sending v1 update to 255.255.255.255 via Serial1/1 (172.17.2.2)
*Mar 1 01:07:07.819: RIP: build update entries
*Mar 1 01:07:07.819: network 3.0.0 .0 metric 1 这是从s1/1发出去的更新包在本路由器上的构建
*Mar 1 01:07:14.311: RIP: sending v1 update to 255.255.255.255 via Loopback3 ( 3.3.3 .3)
*Mar 1 01:07:14.311: RIP: build update entries
*Mar 1 01:07:14.315: network 2.0.0 .0 metric 3
*Mar 1 01:07:14.315: network 172.17.0.0 metric 1
*Mar 1 01:07:14.319: network 192.168.12.0 metric 1
*Mar 1 01:07:14.319: network 192.168.83.0 metric 1
*Mar 1 01:07:20.647: RIP: received v1 update from 172.17.2.1 on Serial1/1
*Mar 1 01:07:20.651: 2.0.0 .0 in 2 hops
*Mar 1 01:07:20.651: 172.17. 1.0 in 1 hops
*Mar 1 01:07:20.655: 192.168. 12.0 in 1 hops
*Mar 1 01:07:20.655: 192.168. 83.0 in 1 hops
2.本实验中非连续子网的探讨
此时只有Barney的 10.1.1 .1通告rip
Andy#show ip route
192.168.12.0/27 is subnetted, 1 subnets
C 192.168.12.64 is directly connected, FastEthernet0/1
R 2.0.0 .0/8 [120/1] via 192.168.12.66, 00:00:14, FastEthernet0/1
R 3.0.0 .0/8 [120/1] via 172.17.2.2, 00:00:26, Serial1/1
172.17.0.0/24 is subnetted, 2 subnets
C 172.17.1.0 is directly connected, Serial1/0
C 172.17.2.0 is directly connected, Serial1/1
C 192.168.83.0/24 is directly connected, FastEthernet0/0
10.0.0 .0/24 is subnetted, 1 subnets
C 10.1.2 .0 is directly connected, Loopback1
Andy#show ip route 10.0.0 .0
Routing entry for 10.0.0 .0/24, 1 known subnets
Attached (1 connections)
C 10.1.2 .0 is directly connected, Loopback1
这时Andy是ping不通 10.1.1 .1的 因为Barney是10.1.1.1的主网络边界 这时Barneny发的更新是10.0.0.0所以Andy不会写入路由表
3.Andy上passive-interface 的研究
*Dec 11 08:05:26.183: RIP: received v1 update from 172.17.2.2 on Serial1/1
*Dec 11 08:05:26.187: 3.0.0 .0 in 1 hops
*Dec 11 08:05:27.495: RIP: sending v1 update to 255.255.255.255 via Serial1/1 (172.17.2.1)
*Dec 11 08:05:27.495: RIP: build update entries
*Dec 11 08:05:27.499: network 2.0.0 .0 metric 2
*Dec 11 08:05:27.499: subnet 172.17.1.0 metric 1
*Dec 11 08:05:27.503: network 192.168.12.0 metric 1
*Dec 11 08:05:27.503: network 192.168.83.0 metric 1
*Dec 11 08:05:29.507: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.83.1)向fa0/0发出了更新
*Dec 11 08:05:29.511: RIP: build update entries
*Dec 11 08:05:29.515: network 2.0.0 .0 metric 2
*Dec 11 08:05:29.515: network 3.0.0 .0 metric 2
*Dec 11 08:05:29.519: network 172.17.0.0 metric 1
*Dec 11 08:05:29.519: network 192.168.12.0 metric 1
*Dec 11 08:05:30.295: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/1 (192.168.12.65)
*Dec 11 08:05:30.295: RIP: build update entries
*Dec 11 08:05:30.295: network 3.0.0 .0 metric 2
*Dec 11 08:05:30.295: network 172.17.0.0 metric 1
*Dec 11 08:05:30.295: network 192.168.83.0 metric 1
在fa0/0上启用passive-interface 后
*Dec 11 08:05:55.035: RIP: sending v1 update to 255.255.255.255 via Serial1/1 (172.17.2.1)
*Dec 11 08:05:55.039: RIP: build update entries
*Dec 11 08:05:55.039: network 2.0.0 .0 metric 2
*Dec 11 08:05:55.043: subnet 172.17.1.0 metric 1
*Dec 11 08:05:55.043: network 192.168.12.0 metric 1
*Dec 11 08:05:55.043: network 192.168.83.0 metric 1
*Dec 11 08:05:55.719: RIP: received v1 update from 172.17.2.2 on Serial1/1
*Dec 11 08:05:55.723: 3.0.0 .0 in 1 hops
*Dec 11 08:05:56.947: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/1 (192.168.12.65)
*Dec 11 08:05:56.947: RIP: build update entries
*Dec 11 08:05:56.947: network 3.0.0 .0 metric 2
*Dec 11 08:05:56.947: network 172.17.0.0 metric 1
*Dec 11 08:05:56.951: network 192.168.83.0 metric 1
*Dec 11 08:06:03.079: RIP: sending v1 update to 255.255.255.255 via Serial1/0 (172.17.1.1)
*Dec 11 08:06:03.083: RIP: build update entries
*Dec 11 08:06:03.087: network 2.0.0 .0 metric 2
*Dec 11 08:06:03.087: network 3.0.0 .0 metric 2
*Dec 11 08:06:03.091: subnet 172.17.2.0 metric 1
*Dec 11 08:06:03.091: network 192.168.12.0 metric 1
*Dec 11 08:06:03.095: network 192.168.83.0 metric 1 不再向fa0/0发送更新
l 在Flody上启用 2.2.2 .2后
不难发现Andy负载均衡
Andy#traceroute 2.2.2 .2
Type escape sequence to abort.
Tracing the route to 2.2.2 .2
1 192.168.12.67 56 msec
192.168.12.66 28 msec
192.168.12.67 56 msec