您的位置:首页 > 其它

RIP实验学习(一)

2009-03-22 17:22 323 查看
RIP实验学习(一)实验目标:理解RIP协议的版本,汇总,验证实验环境:DynamipsGUI 2.8 + SecureCRT5.2物理拓扑:Router1 S1/0 <----> Router5 S1/0
Router1 S1/1 <----> Router5 S1/1
Router2 S1/0 <----> Router5 S1/2
Router2 S1/1 <----> Router5 S1/3
Router3 S1/0 <----> Router5 S1/4
Router3 S1/1 <----> Router5 S1/5
Router4 S1/0 <----> Router5 S1/6
Router4 S1/1 <----> Router5 S1/7Router5在本实验中扮演 Frame-relay Switch角色 ,这样连接的最终目的是使R1 s1/0---R4 s1/1; R1 s1/1---R2 s1/0 ;R2 s1/1----R3 s1/0 ;R3 s1/1---R4 s1/0 之间实现FR口相连。实验步骤:首先搭建frame-relay环境1.验证物理连通性FR#sh cdp nei
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - RepeaterDevice ID Local Intrfce Holdtme Capability Platform Port ID
R2 Ser 1/3 171 R 7206VXR Ser 1/1
R2 Ser 1/2 171 R 7206VXR Ser 1/0
R3 Ser 1/5 176 R 7206VXR Ser 1/1
R3 Ser 1/4 172 R 7206VXR Ser 1/0
R1 Ser 1/1 169 R 7206VXR Ser 1/1
R1 Ser 1/0 169 R 7206VXR Ser 1/0
R4 Ser 1/7 176 R 7206VXR Ser 1/1
R4 Ser 1/6 173 R 7206VXR Ser 1/0
FR#2. 在R5上实现FR功能,并给DTE(本实验中DTE端为R1,R2,R3,R4)端指定DLCI值;FR(config)#frame-relay switching
FR(config)#int s1/0
FR(config-if)#encapsulation frame-relay
FR(config-if)#frame-relay intf-type dce
FR(config-if)#clock rate 9600
FR(config-if)#frame-relay lmi-type ansi
FR(config-if)#frame-relay route 104 interface serial 1/7 401
FR(config-if)#exitFR(config)#int s1/7
FR(config-if)#encapsulation frame-relay
FR(config-if)#frame-relay lmi-type ansi
FR(config-if)#frame-relay intf-type dce
FR(config-if)#clock rate 9600
FR(config-if)#frame-relay route 401 interface serial 1/0 104
FR(config-if)#exitFR(config)#int s1/1
FR(config-if)#encapsulation frame-relay
FR(config-if)#frame-relay lmi-type ansi
FR(config-if)#frame-relay intf-type dce
FR(config-if)#clock rate 9600
FR(config-if)#frame-relay route 102 interface s1/2 201
FR(config-if)#exitFR(config)#int s1/2
FR(config-if)#encapsulation frame-relay
FR(config-if)#frame-relay lmi-type ansi
FR(config-if)#frame-relay intf-type dce
FR(config-if)#clock rate 9600
FR(config-if)#frame-relay route 201 interface s1/2 102
FR(config-if)#exitFR(config)#int s1/3
FR(config-if)#encapsulation frame-relay
FR(config-if)#frame-relay lmi-type ansi
FR(config-if)#frame-relay intf-type dce
FR(config-if)#clock rate 9600
FR(config-if)#frame-relay route 203 interface serial 1/4 302
FR(config-if)#exitFR(config)#int s1/4
FR(config-if)#encapsulation frame-relay
FR(config-if)#frame-relay lmi-type ansi
FR(config-if)#frame-relay intf-type dce
FR(config-if)#clock rate 9600
FR(config-if)#frame-relay route 302 interface serial 1/3 203
FR(config-if)#exitFR(config)#int s1/5
FR(config-if)#encapsulation frame-relay
FR(config-if)#frame-relay lmi-type ansi
FR(config-if)#frame-relay intf-type dce
FR(config-if)#clock rate 9600
FR(config-if)#frame-relay route 304 interface serial 1/6 403
FR(config-if)#exitFR(config)#int s1/6
FR(config-if)#encapsulation frame-relay
FR(config-if)#frame-relay lmi-type ansi
FR(config-if)#frame-relay intf-type dce
FR(config-if)#clock rate 9600
FR(config-if)#frame-relay route 403 interface serial 1/5 304
FR(config-if)#exit//显示PVC,因为DTE端还没有封装FR,所以Status是inactive状态FR#sh frame-relay route
Input Intf Input Dlci Output Intf Output Dlci Status
Serial1/0 104 Serial1/7 401 inactive
Serial1/1 102 Serial1/2 201 inactive
Serial1/2 201 Serial1/1 102 inactive
Serial1/3 203 Serial1/4 302 inactive
Serial1/4 302 Serial1/3 203 inactive
Serial1/5 304 Serial1/6 403 inactive
Serial1/6 403 Serial1/5 304 inactive
Serial1/7 401 Serial1/0 104 inactive
3. 分别在R1,R2,R3,R4对应接口上自定义IP地址,并封装FR,测试。R1(config)#int s1/0
R1(config-if)#ip add 1.1.1.1 255.255.255.0
R1(config-if)#encapsulation frame-relay
R1(config-if)#exit
R1(config)#int s1/1
R1(config-if)#encapsulation frame-relay
R1(config-if)#ip add 2.2.2.1 255.255.255.0
R1(config-if)#exitR2(config)#int s1/0
R2(config-if)#ip add 2.2.2.2 255.255.255.0
R2(config-if)#encapsulation frame-relay
R2(config-if)#exit
R2(config)#int s1/1
R2(config-if)#encapsulation frame-relay
R2(config-if)#ip add 3.3.3.1 255.255.255.0
R2(config-if)#exitR3(config)#int s1/0
R3(config-if)#ip add 3.3.3.2 255.255.255.0
R3(config-if)#encapsulation frame-relay
R3(config-if)#exit
R3(config)#int s1/1
R3(config-if)#ip add 4.4.4.1 255.255.255.0
R3(config-if)#encapsulation frame-relay
R3(config-if)#exitR4(config)#int s1/0
R4(config-if)#ip add 4.4.4.2 255.255.255.0
R4(config-if)#encapsulation frame-relay
R4(config-if)#exit
R4(config)#int s1/1
R4(config-if)#ip add 1.1.1.2 255.255.255.0
R4(config-if)#encapsulation frame-relay
R4(config-if)#exit//测试连通性,查看pvc
//由于frame-relay inverse-arp默认启用,所以我这里先用的动态映射R1#sh frame-relay map
Serial1/0 (up): ip 1.1.1.2 dlci 104(0x68,0x1880), dynamic,
broadcast,, status defined, active
Serial1/1 (up): ip 2.2.2.2 dlci 102(0x66,0x1860), dynamic,
broadcast,, status defined, activeR2#sh frame-relay map
Serial1/0 (up): ip 2.2.2.1 dlci 201(0xC9,0x3090), dynamic,
broadcast,, status defined, active
Serial1/1 (up): ip 3.3.3.2 dlci 203(0xCB,0x30B0), dynamic,
broadcast,, status defined, activeR3#sh frame-relay map
Serial1/0 (up): ip 3.3.3.1 dlci 302(0x12E,0x48E0), dynamic,
broadcast,, status defined, active
Serial1/1 (up): ip 4.4.4.2 dlci 304(0x130,0x4C00), dynamic,
broadcast,, status defined, activeR4#sh frame-relay map
Serial1/0 (up): ip 4.4.4.1 dlci 403(0x193,0x6430), dynamic,
broadcast,, status defined, active
Serial1/1 (up): ip 1.1.1.1 dlci 401(0x191,0x6410), dynamic,
broadcast,, status defined, active//以上动态映射结果,只是我想证明frame-relay DTE端,最小配置就是只要在DTE端的接口下配置IP然后封装Frame-relay就可以了
//为了RIP实验要求,我下面将将改frame-relay map方式为 staticR1(config)#int s1/0
R1(config-if)#frame-relay map ip 1.1.1.2 104 broadcast
R1(config)#int s1/1
R1(config-if)#frame-relay map ip 2.2.2.2 102 broadcastR1#sh frame-relay map
Serial1/0 (up): ip 1.1.1.2 dlci 104(0x68,0x1880), static,
broadcast,
CISCO, status defined, active
Serial1/1 (up): ip 2.2.2.2 dlci 102(0x66,0x1860), static,
broadcast,
CISCO, status defined, activeR2(config)#int s1/0
R2(config-if)#frame-relay map ip 2.2.2.1 201 broadcast
R2(config)#int s1/1
R2(config-if)#frame-relay map ip 3.3.3.2 203 broadcastR2#sh frame-relay map
Serial1/0 (up): ip 2.2.2.1 dlci 201(0xC9,0x3090), static,
broadcast,
CISCO, status defined, active
Serial1/1 (up): ip 3.3.3.2 dlci 203(0xCB,0x30B0), static,
broadcast,
CISCO, status defined, activeR3(config)#int s1/0
R3(config-if)#frame-relay map ip 3.3.3.1 302 broadcast
R3(config-if)#exit
R3(config)#int s1/1
R3(config-if)#frame-relay map ip 4.4.4.2 304 broadcast
R3(config-if)#end
R3#sh frame-relay map
Serial1/0 (up): ip 3.3.3.1 dlci 302(0x12E,0x48E0), static,
broadcast,
CISCO, status defined, active
Serial1/1 (up): ip 4.4.4.2 dlci 304(0x130,0x4C00), static,
broadcast,
CISCO, status defined, active
R4(config)#int s1/0
R4(config-if)#frame-relay map ip 4.4.4.1 403 broadcast
R4(config-if)#exit
R4(config)#int s1/1
R4(config-if)#frame-relay map ip 1.1.1.1 401 broadcast
R4(config-if)#end
R4#sh frame-relay map
Serial1/0 (up): ip 4.4.4.1 dlci 403(0x193,0x6430), static,
broadcast,
CISCO, status defined, active
Serial1/1 (up): ip 1.1.1.1 dlci 401(0x191,0x6410), static,
broadcast,
CISCO, status defined, active//至此frame-relay 环境以搭好,可能前面讲frame-relay太啰嗦,会的朋友可掠过不看,实验谨供参考实验目标一: 所有路由器以最小资源运行RIP 2,全网通告本地路由器的loopback0.在R1,R2,R3,R4上分别起loopback0接口,并分配ip //这步我暂省略,相信大家都会
试验中loopback0地址的设定按此规则,128.1.*.* 例如 R1 128.1.1.1 R2 128.1.2.2R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#network 2.2.2.0
R1(config-router)#network 1.1.1.0
R1(config-router)#network 128.1.1.0
R1(config-router)#passive-interface serial 1/0
R1(config-router)#passive-interface serial 1/1
R1(config-router)#neighbor 2.2.2.2
R1(config-router)#neighbor 1.1.1.2
R1(config-router)#no auto-summary R1#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static routeGateway of last resort is not set 1.0.0.0/24 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Serial1/0
2.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 2.2.2.0/24 is directly connected, Serial1/1
R 2.0.0.0/8 [120/2] via 1.1.1.2, 00:00:48, Serial1/0
3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
R 3.3.3.0/24 [120/1] via 2.2.2.2, 00:00:10, Serial1/1
R 3.0.0.0/8 is possibly down,
routing via 2.2.2.2, Serial1/1
4.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
R 4.4.4.0/24 [120/1] via 1.1.1.2, 00:00:20, Serial1/0
R 4.0.0.0/8 [120/1] via 1.1.1.2, 00:00:48, Serial1/0
128.1.0.0/16 is variably subnetted, 5 subnets, 2 masks
C 128.1.1.0/24 is directly connected, Loopback0
R 128.1.0.0/16 [120/1] via 1.1.1.2, 00:00:49, Serial1/0
R 128.1.3.0/24 [120/2] via 2.2.2.2, 00:00:11, Serial1/1
[120/2] via 1.1.1.2, 00:00:21, Serial1/0
R 128.1.2.0/24 [120/1] via 2.2.2.2, 00:00:11, Serial1/1
R 128.1.4.0/24 [120/1] via 1.1.1.2, 00:00:23, Serial1/0R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#network 2.2.2.0
R2(config-router)#network 3.3.3.0
R2(config-router)#network 128.1.2.0
R2(config-router)#passive-interface serial 1/0
R2(config-router)#passive-interface serial 1/1
R2(config-router)#neighbor 2.2.2.1
R2(config-router)#neighbor 3.3.3.2
R2(config-router)#no auto-summary R2#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static routeGateway of last resort is not set 1.0.0.0/24 is subnetted, 1 subnets
R 1.1.1.0 [120/1] via 2.2.2.1, 00:00:06, Serial1/0
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Serial1/0
3.0.0.0/24 is subnetted, 1 subnets
C 3.3.3.0 is directly connected, Serial1/1
4.0.0.0/24 is subnetted, 1 subnets
R 4.4.4.0 [120/1] via 3.3.3.2, 00:00:09, Serial1/1
128.1.0.0/24 is subnetted, 4 subnets
R 128.1.1.0 [120/1] via 2.2.2.1, 00:00:06, Serial1/0
R 128.1.3.0 [120/1] via 3.3.3.2, 00:00:09, Serial1/1
C 128.1.2.0 is directly connected, Loopback0
R 128.1.4.0 [120/2] via 2.2.2.1, 00:00:06, Serial1/0
[120/2] via 3.3.3.2, 00:00:09, Serial1/1R3(config)#router ri
R3(config-router)#version 2
R3(config-router)#network 3.3.3.0
R3(config-router)#network 4.4.4.0
R3(config-router)#network 128.1.3.0
R3(config-router)#passive-interface serial 1/0
R3(config-router)#passive-interface serial 1/1
R3(config-router)#neighbor 3.3.3.1
R3(config-router)#neighbor 4.4.4.2
R3(config-router)#no auto-summary R3#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static routeGateway of last resort is not set 1.0.0.0/24 is subnetted, 1 subnets
R 1.1.1.0 [120/1] via 4.4.4.2, 00:00:05, Serial1/1
2.0.0.0/24 is subnetted, 1 subnets
R 2.2.2.0 [120/1] via 3.3.3.1, 00:00:25, Serial1/0
3.0.0.0/24 is subnetted, 1 subnets
C 3.3.3.0 is directly connected, Serial1/0
4.0.0.0/24 is subnetted, 1 subnets
C 4.4.4.0 is directly connected, Serial1/1
128.1.0.0/24 is subnetted, 4 subnets
R 128.1.1.0 [120/2] via 3.3.3.1, 00:00:25, Serial1/0
[120/2] via 4.4.4.2, 00:00:05, Serial1/1
C 128.1.3.0 is directly connected, Loopback0
R 128.1.2.0 [120/1] via 3.3.3.1, 00:00:25, Serial1/0
R 128.1.4.0 [120/1] via 4.4.4.2, 00:00:07, Serial1/1
R4(config)#router rip
R4(config-router)#version 2
R4(config-router)#network 1.1.1.0
R4(config-router)#network 4.4.4.0
R4(config-router)#network 128.1.4.0
R4(config-router)#passive-interface serial 1/0
R4(config-router)#passive-interface serial 1/1
R4(config-router)#neighbor 1.1.1.1
R4(config-router)#neighbor 4.4.4.1
R4(config-router)#no auto-summary R4#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static routeGateway of last resort is not set 1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 1.1.1.0/24 is directly connected, Serial1/1
R 1.0.0.0/8 [120/5] via 1.1.1.1, 00:00:17, Serial1/1
2.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
R 2.2.2.0/24 [120/1] via 1.1.1.1, 00:00:17, Serial1/1
R 2.0.0.0/8 [120/4] via 1.1.1.1, 00:00:17, Serial1/1
3.0.0.0/24 is subnetted, 1 subnets
R 3.3.3.0 [120/1] via 4.4.4.1, 00:00:15, Serial1/0
4.0.0.0/24 is subnetted, 1 subnets
C 4.4.4.0 is directly connected, Serial1/0
128.1.0.0/24 is subnetted, 4 subnets
R 128.1.1.0 [120/1] via 1.1.1.1, 00:00:17, Serial1/1
R 128.1.3.0 [120/1] via 4.4.4.1, 00:00:15, Serial1/0
R 128.1.2.0 [120/2] via 1.1.1.1, 00:00:19, Serial1/1
[120/2] via 4.4.4.1, 00:00:17, Serial1/0
C 128.1.4.0 is directly connected, Loopback0
实验目标二:R1和R2之间触发更新 触发更新需在接口模式下启用,且需点到点链路,所以先将R1 s1/1接口的ip 和R2 s1/0上的ip去掉,然后起分别起子接口,并设置point to point 类型,具体如下:R1(config)#int s1/1
R1(config-if)#no ip add
R1(config)#int s1/1.1 point-to-point
R1(config-subif)#ip address 2.2.2.2 255.255.255.0
R1(config-subif)#frame-relay interface-dlci 102
R1(config-fr-dlci)#exit
R1(config-subif)#ip rip triggered
R1(config-subif)#endR2(config)#int s1/0
R2(config-if)#no ip add
R2(config)#int s1/0.1 point-to-point
R2(config-subif)#ip add 2.2.2.2 255.255.255.0
R2(config-subif)#ip rip triggered
R2(config-subif)#frame-relay interface-dlci 201
R2(config-fr-dlci)#end开debug ip rip 看下效果R1#debug ip rip events
RIP event debugging is on
R1#debug ip rip
RIP protocol debugging is on
R1#
*Mar 22 17:08:10.351: RIP: sending triggered request on Serial1/1.1 to 224.0.0.9
R1#
*Mar 22 17:08:15.351: RIP: sending triggered request on Serial1/1.1 to 224.0.0.9
R1#
*Mar 22 17:08:20.351: RIP: sending triggered request on Serial1/1.1 to 224.0.0.9
R1#*Mar 22 17:08:25.399: RIP: received v2 update from 1.1.1.2 on Serial1/0
*Mar 22 17:08:25.399: 1.1.1.0/24 via 0.0.0.0 in 1 hops
*Mar 22 17:08:25.399: 3.3.3.0/24 via 0.0.0.0 in 2 hops
*Mar 22 17:08:25.403: 4.4.4.0/24 via 0.0.0.0 in 1 hops
*Mar 22 17:08:25.403: 128.1.2.0/24 via 0.0.0.0 in 3 hops
*Mar 22 17:08:25.403: 128.1.3.0/24 via 0.0.0.0 in 2 hops
*Mar 22 17:08:25.403: 128.1.4.0/24 via 0.0.0.0 in 1 hops
*Mar 22 17:08:25.407: RIP: Update contains 6 routes
R1#
*Mar 22 17:08:27.155: RIP: sending v2 update to 1.1.1.2 via Serial1/0 (1.1.1.1)
*Mar 22 17:08:27.155: RIP: build update entries
*Mar 22 17:08:27.155: 1.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 22 17:08:27.155: 2.2.2.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 22 17:08:27.159: 3.3.3.0/24 via 1.1.1.2, metric 3, tag 0
*Mar 22 17:08:27.159: 4.4.4.0/24 via 1.1.1.2, metric 2, tag 0
*Mar 22 17:08:27.159: 128.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 22 17:08:27.159: 128.1.2.0/24 via 1.1.1.2, metric 4, tag 0
*Mar 22 17:08:27.159: 128.1.3.0/24 via 1.1.1.2, metric 3, tag 0
*Mar 22 17:08:27.163: 128.1.4.0/24 via 1.1.1.2, metric 2, tag 0
R1#
*Mar 22 17:08:27.163: RIP: Update contains 8 routes
*Mar 22 17:08:27.163: RIP: Update queued
*Mar 22 17:08:27.163: RIP: Update sent via Serial1/0
R1#
*Mar 22 17:08:34.991: RIP: sending v2 update to 224.0.0.9 via Serial1/1.1 (2.2.2.2)
*Mar 22 17:08:34.991: RIP: build update entries
*Mar 22 17:08:34.991: 1.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 22 17:08:34.991: 3.3.3.0/24 via 0.0.0.0, metric 3, tag 0
*Mar 22 17:08:34.995: 4.4.4.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 22 17:08:34.995: 128.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 22 17:08:34.995: 128.1.2.0/24 via 0.0.0.0, metric 4, tag 0
*Mar 22 17:08:34.995: 128.1.3.0/24 via 0.0.0.0, metric 3, tag 0
*Mar 22 17:08:34.995: 128.1.4.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 22 17:08:34.999: RIP: Update contains 7 routes
*Mar 22 17:08:34.999: RIP: Update queued
*Mar 22 17:08:34.999: RIP: sending v2 update to 2.2.2.2 via Serial1/1.1 (2.2.2.2)
*Mar 22 17:08:34.999: RIP: build update entries
*Mar 22 17:08:34.999: 1.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 22 17:08:35.003: 3.3.3.0/24 via 0.0.0.0, metric 3, tag 0
*Mar 22 17:08:35.003: 4.4.4.0/24 via 0.0.0.0, metri
R1#c 2, tag 0
*Mar 22 17:08:35.003: 128.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 22 17:08:35.003: 128.1.2.0/24 via 0.0.0.0, metric 4, tag 0
*Mar 22 17:08:35.003: 128.1.3.0/24 via 0.0.0.0, metric 3, tag 0
*Mar 22 17:08:35.007: 128.1.4.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 22 17:08:35.007: RIP: Update contains 7 routes
*Mar 22 17:08:35.007: RIP: Update queued
*Mar 22 17:08:35.007: RIP: Update sent via Serial1/1.1
*Mar 22 17:08:35.007: RIP: Update sent via Serial1/1.1
R2#debug ip rip eve
R2#debug ip rip events
RIP event debugging is on
R2#debug ip rip
RIP protocol debugging is on
R2#
*Mar 22 17:09:03.579: RIP: sending triggered request on Serial1/0.1 to 224.0.0.9
*Mar 22 17:09:03.931: RIP: sending v2 update to 3.3.3.2 via Serial1/1 (3.3.3.1)
*Mar 22 17:09:03.931: RIP: Update contains 8 routes
*Mar 22 17:09:03.931: RIP: Update queued
*Mar 22 17:09:03.935: RIP: Update sent via Serial1/1
R2#
*Mar 22 17:09:08.579: RIP: sending triggered request on Serial1/0.1 to 224.0.0.9
总结,rip 的验证及其他特性,将在rip(二)里继续学习,今天搞得实在有些长了,第一次发这么专业的贴子(呵呵,脸红),做了一下午的实验,累,刚开始调试frame-relay就花了一个多小时,菜啊,由于用模拟器,难免会有一些问题,所以只能慢慢调试咯。来51CTO不久,看上面很多兄弟们都乐于奉献,实在太感动,想想自己没什么东西可拿得出手的,所以只能把自己平时的一些实验拿出来供大家参考,不足之处,敬请斧正,虚心接受,再次感谢。
本文出自 “飞翔的蜘蛛” 博客,请务必保留此出处http://zhengjinjia.blog.51cto.com/406017/141332
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: