您現(xiàn)在的位置: test4exam >> 計算機考試 >> CISCO認證 >> 正文
實驗配置:實驗1:被動接口(passive-interface)
RIP中是不發(fā)送更新的 但是接收更新 EIGRP 中消息不在發(fā)送到指定的接口這樣的話也就不在形成鄰接關(guān)系了,也就是在接口上啥都不發(fā)! ospf 在被動接口上發(fā)送hello DBD分組 但是不發(fā)送LSU!
采用R2 R3 R5 回環(huán)接口也使用了!
啟用RIP進程 所有接口都加入
R2的路由表
C 192.168.55.0/24 is directly connected, Loopback0
R 10.0.0.0/8 [120/2] via 192.168.1.3, 00:00:07, FastEthernet0/0
C 192.168.1.0/24 is directly connected, FastEthernet0/0
R 192.168.3.0/24 [120/1] via 192.168.1.3, 00:00:07, FastEthernet0/0
r2#
R3 debug ip rip
*Mar 1 00:15:55.559: RIP: sending v1 update to 255.255.255.255 via Ethernet0/0 (192.168.1.3)
*Mar 1 00:15:55.563: RIP: build update entries
*Mar 1 00:15:55.563: network 10.0.0.0 metric 2
*Mar 1 00:15:55.563: network 192.168.3.0 metric 1
在接口E0/0廣播
現(xiàn)在R3
r3(config)#router rip
r3(config-router)#passive-interface e0/0
debug
Mar 1 00:17:42.163: RIP: sending v1 update to 255.255.255.255 via Serial1/0 (192.168.3.1)
*Mar 1 00:17:42.167: RIP: build update entries
*Mar 1 00:17:42.167: network 192.168.1.0 metric 1
*Mar 1 00:17:42.171: network 192.168.55.0 metric 2
*Mar 1 00:17:47.411: RIP: received v1 update from 192.168.1.2 on Ethernet0/0
*Mar 1 00:17:47.415: 192.168.55.0 in 1 hops
不再e0/0上廣播了但是仍然接收到更新報文
TNND的等了三分鐘
C 192.168.55.0/24 is directly connected, Loopback0
R 10.0.0.0/8 is possibly down, routing via 192.168.1.3, FastEthernet0/0
C 192.168.1.0/24 is directly connected, FastEthernet0/0
R 192.168.3.0/24 is possibly down, routing via 192.168.1.3, FastEthernet0/0
路由條目過了抑制時間 然后再過60S的刷新時間就刪除掉了!
實驗2:單播更新(unicast update)
正好接著上面的 關(guān)閉R5 啟動R1 其他的不變!
雖然接口PASSIVE了 我們?nèi)匀豢捎弥付?/FONT>鄰居 進行單播的更新 節(jié)省帶寬!
實驗?zāi)康模篟2和R1 .R2和R3之間交換RIP通告信息 R1 R3間不交換RIP信息!
R1的配置: r1(config)#router rip
r1(config-router)#network 192.168.66.0
r1(config-router)#network 192.168.1.0
r1(config-router)#passive-interface e0/0
r1(config-router)#passive-interface fa0/0
r1(config-router)#neighbor 192.168.1.2 #指定鄰居 單獨更新
R3的配置
r3(config)#router rip
r3(config-router)#network 192.168.1.0
r3(config-router)#network 192.168.8.0 #又定義了一個回環(huán)接口
r3(config-router)#passive-interface e0/0
r3(config-router)#neighbor 192.168.1.2
再看 r3#debug ip rip events
*Mar 1 00:35:28.559: RIP: sending v1 update to 192.168.1.2 via Ethernet0/0 (192.168.1.3)
*Mar 1 00:35:28.563: RIP: Update contains 1 routes
*Mar 1 00:41:38.871: RIP: sending v1 update to 255.255.255.255 via Loopback0 (192.168.88.1)
*Mar 1 00:41:38.871: RIP: Update contains 2 rout
*Mar 1 00:41:33.467: RIP: received v1 update from 192.168.1.2 on Ethernet0/0
*Mar 1 00:41:33.471: RIP: Update contains 1 routes
接口E0/0上阻止了廣播 只是單播到192.168.1.2
那么R1 R3的路由表會咋樣呢!
r3#show ip route
C 192.168.88.0/24 is directly connected, Loopback0
R 192.168.55.0/24 [120/1] via 192.168.1.2, 00:00:19, Ethernet0/0
C 192.168.1.0/24 is directly connected, Ethernet0/0
r1#show ip route
R 192.168.55.0/24 [120/1] via 192.168.1.2, 00:00:14, FastEthernet0/0
C 192.168.66.0/24 is directly connected, Loopback0
C 192.168.1.0/24 is directly connected, FastEthernet0/0
在共享的以太網(wǎng)上 水平分割的原因 R2從R1 R3學(xué)到的路由不會在從E0/0口發(fā)送出去的!
實驗三:不連續(xù)的子網(wǎng)(discontinuity subnet)
關(guān)閉R1.R2.SW 啟動R4 R5 關(guān)閉R4 R5的s1/0口
現(xiàn)有 R3 R4 R5
啟動RIP進程 所有接口都加入
因為RIPV1是有類別路由選擇 不帶子網(wǎng)掩碼 默認在主網(wǎng)絡(luò)邊界匯總
R4 R5都通告給R3 那么R3就會自以為的到達10.0.0.0/8有2條路可走!進行均衡負載了!
很顯然這樣到達10.0.0.0只會有50%的機會到達正確的子網(wǎng)
解決方法
在R4 R3 and R3 R5之間配置輔助IP地址(secondary ip address).關(guān)于子網(wǎng)10.0.0.0
見rip基礎(chǔ)里的一句話:如果目的地址是一個和路由器直接相連的主網(wǎng)絡(luò)的成員 那么該網(wǎng)絡(luò)的路由器接口上配置的子網(wǎng)掩碼將被用來確定目的地址的子網(wǎng)因此在那個主網(wǎng)絡(luò)中必須自始至終的統(tǒng)一使用這個子網(wǎng)掩碼
R3:
C 192.168.88.0/24 is directly connected, Loopback0
R 10.0.0.0/8 [120/1] via 192.168.3.2, 00:00:13, Serial1/0
[120/1] via 192.168.2.2, 00:00:25, Serial1/1
C 192.168.1.0/24 is directly connected, Ethernet0/0
C 192.168.2.0/24 is directly connected, Serial1/1
C 192.168.3.0/24 is directly connected, Serial1/0
R4:
r4#show ip route
R 192.168.88.0/24 [120/1] via 192.168.2.1, 00:00:17, Serial1/1
10.0.0.0/24 is subnetted, 1 subnets
C 10.1.3.0 is directly connected, Loopback0
R 192.168.1.0/24 [120/1] via 192.168.2.1, 00:00:17, Serial1/1
C 192.168.2.0/24 is directly connected, Serial1/1
R 192.168.3.0/24 [120/1] via 192.168.2.1, 00:00:17, Serial1/1
r4#
解決辦法:
r3(config)#int s1/1
r3(config-if)#ip add 10.2.1.1 255.255.255.0 secondary
r3(config-if)#int s1/0
r3(config-if)#ip add 10.2.2.1 255.255.255.0 secondary
r4(config)#int s1/1
r4(config-if)#ip add 10.2.1.2 255.255.255.0 secondary
r5(config)#int s1/1
r5(config-if)#ip add 10.2.2.2 255.255.255.0 secondary
習(xí)慣性的總是忘記加secondary 導(dǎo)致IP地址被覆蓋了重復(fù)了N次
看看R3的路由表
r3# show ip route
C 192.168.88.0/24 is directly connected, Loopback0
10.0.0.0/24 is subnetted, 5 subnets
R 10.1.3.0 [120/1] via 10.2.1.2, 00:00:11, Serial1/1
C 10.2.1.0 is directly connected, Serial1/1
C 10.2.2.0 is directly connected, Serial1/0
R 10.0.0.0 [120/1] via 192.168.3.2, 00:00:02, Serial1/0
[120/1] via 192.168.2.2, 00:00:11, Serial1/1
R 10.1.4.0 [120/1] via 10.2.2.2, 00:00:02, Serial1/0
C 192.168.1.0/24 is directly connected, Ethernet0/0
C 192.168.2.0/24 is directly connected, Serial1/1
是不是有更詳細的子網(wǎng)了
匯總的依然存在 畢竟是匹配最精確的路由的 沒關(guān)系!
輔助IP有時候很有用 比如網(wǎng)絡(luò)要開始重新規(guī)劃調(diào)整了 網(wǎng)絡(luò)又不能中斷 這個時候用輔助IP地址進行路由的協(xié)議的匯聚牙等等 然后午夜子時 切換到新的!
實驗4:RIP的度量(RIP metric)
拓撲依然是上面那個 另外要啟動R4 R5的s1/0接口!關(guān)掉R4R5的Loopback接口
r5(config)#int loopback 0
r5(config-if)#ip add 10.1.44.4 255.255.255.0
上面的回環(huán)接口改一下 TNND和 R5的s1/0 接口沖突 沒在意 哈哈!
啟動所有接口的RIP進程
命令參考:offset-list {access-list-number|name}{in|out} offset {type number}
Offset偏移 tcp/ip網(wǎng)絡(luò)層也有個偏移量的東東!
R4的子網(wǎng)10.1.3.0到R5的子網(wǎng)10.1.2.0 這樣走的話是以跳 經(jīng)過R3是2跳 現(xiàn)在的情況是向讓R4 R5之間的串行線路作為備份!不向動態(tài)鏈路的協(xié)議還可以改變什么接口帶寬啊什么的 RIP可不認 管你鏈路質(zhì)量好壞 過一個ROUTE就是一跳跳的越少就是好的!很簡單的協(xié)議!
r5(config)#access-list 1 permit 10.1.0.0
r5(config)#router rip ^
r5(config-router)#offset-list 1 in 2 s1/1
先檢查從s1/1接口接收進來的RIP通告如果存在和訪問列表1指定的地址相匹配的路由條目,那么把改路由條目的度量加大2跳! ^
r4(config)#access-list 3 permit 10.1.44.0 0.0.0.0
r4(config)#router rip
看看R4的路由表
r4#show ip route
R 192.168.88.0/24 [120/1] via 192.168.2.1, 00:00:10, Serial1/1
10.0.0.0/24 is subnetted, 6 subnets
C 10.1.3.0 is directly connected, Loopback0
C 10.2.1.0 is directly connected, Serial1/1
R 10.2.2.0 [120/1] via 10.1.4.2, 00:00:04, Serial1/0
R 10.0.0.0 [120/2] via 192.168.2.1, 00:00:10, Serial1/1
C 10.1.4.0 is directly connected, Serial1/0
R 10.1.44.0 [120/3] via 10.1.4.2, 00:00:04, Serial1/0
R 192.168.1.0/24 [120/1] via 192.168.2.1, 00:00:10, Serial1/1
C 192.168.2.0/24 is directly connected, Serial1/1
R 192.168.3.0/24 [120/1] via 192.168.2.1, 00:00:10, Serial1/1
[120/1] via 10.1.4.2, 00:00:04, Serial1/0
偏移列表指定額外增加的跳數(shù) 變成三跳了!
注意事項 如果不指定偏移列表的接口,那么偏移列表將在所有于訪問列表匹配的接口上更改所有的入站更新或者是出站的更新 如果不調(diào)用訪問列表來做匹配那就更改所有的入站或者出站的更新啦!
在正在運行使用的路由上實施偏移列表時需要注意 因為當(dāng)一個偏移列表引起下一跳路由器通告的度量只比他正在通告的路由更新的度量值更搞時將直到抑制計時器超時這個路由條目標記成不可達! 呵呵當(dāng)然了 收到了一個 又收到一個 跳數(shù)大的 就懷疑出問題 把這個條目關(guān)緊閉180S 過后發(fā)現(xiàn)還通告就無奈的接收了!
實驗5:5:版本之間的兼容性(compatibility)
Ripv2默認的情況是接收V2 V1版本的更新 只發(fā)送V1版的更新通告
缺省的方式是只發(fā)送和接收版本2的更新。上面的不對的 雖然看到文檔有這么說 做了實驗就知道了
命令 ip rip send version
Ip rip reveive version
采用R1 R2 SW R3 R5 所有接口參與RIP
r1(config-router)#ver 2
r3(config-router)#ver 2
r2(config-router)#ver 1
r5(config-router)#ver 1
R3的route table
r3#show ip route
R 192.168.66.0/24 [120/1] via 192.168.1.1, 00:00:16, Ethernet0/0
C 192.168.1.0/24 is directly connected, Ethernet0/0
C 192.168.3.0/24 is directly connected, Serial1/0
R2 R5都是版本一的 接收不到!
r2#show ip pro
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 1 1
Loopback0 1 1
r2#show ip route
C 192.168.55.0/24 is directly connected, Loopback0
C 192.168.1.0/24 is directly connected, FastEthernet0/0
R2是版本一的默認是收發(fā)v1的通告! 沒有學(xué)到其他的非直連的子網(wǎng)!
進行R3的配置 解決兼容性的問題
r3(config)#int s1/0
r3(config-if)#ip rip send ver 1
r3(config-if)#ip rip receive ver 1
r3(config)#int e0/0
r3(config-if)#ip rip send ver 1 2
r3#Debug ip rip
*Mar 1 00:20:06.491: RIP: sending v1 update to 255.255.255.255 via Ethernet0/0 (192.168.1.3)
*Mar 1 00:20:06.491: RIP: build update entries
*Mar 1 00:20:06.491: network 10.0.0.0 metric 2
*Mar 1 00:20:06.491: network 192.168.3.0 metric 1
*Mar 1 00:20:06.495: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (192.168.1.3)
*Mar 1 00:20:06.499: RIP: build update entries
*Mar 1 00:20:06.499: 10.0.0.0/8 via 0.0.0.0, metric 2, tag 0
*Mar 1 00:20:06.503: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0
Mar 1 00:21:33.191: RIP: sending v1 update to 255.255.255.255 via Serial1/0 (192.168.3.1)
*Mar 1 00:21:33.191: RIP: build update entries
*Mar 1 00:21:33.195: network 192.168.1.0 metric 1
*Mar 1 00:21:33.195: network 192.168.66.0 metric 2
r2#show ip route
C 192.168.55.0/24 is directly connected, Loopback0
R 10.0.0.0/8 [120/2] via 192.168.1.3, 00:00:25, FastEthernet0/0
C 192.168.1.0/24 is directly connected, FastEthernet0/0
R 192.168.3.0/24 [120/1] via 192.168.1.3, 00:00:25, FastEthernet0/0
R3只是在e0/0上發(fā)送RIP版本1和2的更新 但是仍然接收不到從R2通告的更新版本不匹配
Mar 1 00:25:40.579: RIP: ignored v1 packet from 192.168.1.2 (illegal version)
R3因為水平分割的原因 不通告從R1學(xué)到的路由更新,所以R2就學(xué)不到R1的通告的路由了
關(guān)閉水平分割!
r3(config)#int e0/0
r3(config-if)#no ip split-horizon
r2# debug ip rip
Mar 1 00:28:59.127: RIP: ignored v2 packet from 192.168.1.1 (illegal version)
*Mar 1 00:29:14.035: RIP: received v1 update from 192.168.1.3 on FastEthernet0/0
*Mar 1 00:29:14.035: 10.0.0.0 in 2 hops
*Mar 1 00:29:14.035: 192.168.1.0 in 1 hops
*Mar 1 00:29:14.039: 192.168.3.0 in 1 hops
*Mar 1 00:29:14.039: 192.168.66.0 in 2 hops
*Mar 1 00:29:14.043: RIP: ignored v2 packet from 192.168.1.3 (illegal version)
接收了版本一的更新 忽略了版本2的!
r2#show ip route
C 192.168.55.0/24 is directly connected, Loopback0
R 192.168.66.0/24 [120/2] via 192.168.1.3, 00:00:24, FastEthernet0/0
R 10.0.0.0/8 [120/2] via 192.168.1.3, 00:00:24, FastEthernet0/0
C 192.168.1.0/24 is directly connected, FastEthernet0/0
R 192.168.3.0/24 [120/1] via 192.168.1.3, 00:00:24, FastEthernet0/0
下一篇:VPN的特點
Copyright ©2013-2015 江浙滬招生考試網(wǎng) All Rights Reserved.
地址: 蘇州市姑蘇區(qū)閶胥路483號(工投創(chuàng)業(yè)園) 電話:0512-85551931 郵編: 214000
郵箱: [email protected] 版權(quán)所有:蘇州邁峰教育科技有限公司 蘇ICP備15050684號-2