科技行者

行者学院 转型私董会 科技行者专题报道 网红大战科技行者

知识库

知识库 安全导航

至顶网网络频道路由交换ipv6的rip路由配置

ipv6的rip路由配置

  • 扫一扫
    分享文章到微信

  • 扫一扫
    关注官方公众号
    至顶头条

ipv6的rip路由配置

来源:chinaitlab 2010年11月27日

关键字: IPv6 路由技术

  • 评论
  • 分享微博
  • 分享邮件

  Rack01R3#sh ru int lo10

  Building configuration...

  Current configuration : 104 bytes

  !

  interface Loopback10

  no ip address

  ipv6 address 2003::3/64

  ipv6 enable

  ipv6 rip Cisco enable

  end

  Rack01R3#sh ru int e0

  Building configuration...

  Current configuration : 103 bytes

  !

  interface Ethernet0

  no ip address

  ipv6 address 2001::3/64

  ipv6 enable

  ipv6 rip Cisco enable

  end

  (config)#

  !

  ipv6 unicast-routing

  !

  !

  ipv6 router rip Cisco

  !

  -------------------------------(debug info)-------------------------------------------

  *Mar 1 00:51:33.019: RIPng: Triggered update requested

  *Mar 1 00:51:33.775: %SYS-5-CONFIG_I: Configured from console by console

  Rack01R1#

  *Mar 1 00:51:34.019: RIPng: generating triggered update for Cisco

  *Mar 1 00:51:34.019: RIPng: Sending multicast update on Ethernet0 for Cisco

  *Mar 1 00:51:34.023: src=FE80::260:5CFF:FEF4:CD0A

  *Mar 1 00:51:34.027: dst=FF02::9 (Ethernet0)

  *Mar 1 00:51:34.027: sport=521, dport=521, length=32

  *Mar 1 00:51:34.031: command=2, version=1, mbz=0, #rte=1

  *Mar 1 00:51:34.031: tag=0, metric=1, prefix=2001::/64

  Rack01R1#

  *Mar 1 00:51:46.987: RIPng: response received from FE80::250:73FF:FE6C:6813 on Ethernet0 for Cisco

  *Mar 1 00:51:46.991: src=FE80::250:73FF:FE6C:6813 (Ethernet0)

  *Mar 1 00:51:46.995: dst=FF02::9

  *Mar 1 00:51:46.995: sport=521, dport=521, length=52

  *Mar 1 00:51:46.999: command=2, version=1, mbz=0, #rte=2

  *Mar 1 00:51:46.999: tag=0, metric=1, prefix=2001::/64

  *Mar 1 00:51:47.003: tag=0, metric=1, prefix=2003::/64

  *Mar 1 00:51:47.003: RIPng: Added neighbour FE80::250:73FF:FE6C:6813/Ethernet0

  *Mar 1 00:51:47.007: RIPng: Inserted 2001::/64, nexthop FE80::250:73FF:FE6C:6813, metric 2, tag 0

  Rack01R1#

  *Mar 1 00:51:47.015: RIPng: Inserted 2003::/64, nexthop FE80::250:73FF:FE6C:6813, metric 2, tag 0

  *Mar 1 00:51:47.019: RIPng: Triggered update requested

  *Mar 1 00:51:48.019: RIPng: generating triggered update for Cisco

  *Mar 1 00:51:48.023: RIPng: Suppressed null multicast update on Ethernet0 for Cisco

  Rack01R1#

  *Mar 1 00:51:53.027: RIPng: Sending multicast update on Ethernet0 for Cisco

  *Mar 1 00:51:53.031: src=FE80::260:5CFF:FEF4:CD0A

  *Mar 1 00:51:53.031: dst=FF02::9 (Ethernet0)

  *Mar 1 00:51:53.035: sport=521, dport=521, length=52

  *Mar 1 00:51:53.039: command=2, version=1, mbz=0, #rte=2

  *Mar 1 00:51:53.039: tag=0, metric=1, prefix=2001::/64

  *Mar 1 00:51:53.043: tag=0, metric=1, prefix=2010::/64

  ------------------------(ipv6 route table)--------------------------------------

  Rack01R1#sh ipv6 route ri

  IPv6 Routing Table - 6 entries

  Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP

  U - Per-user Static route

  I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea

  O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2

  R 2003::/64 [120/2]

  via FE80::250:73FF:FE6C:6813, Ethernet0

  解释:

  环境为R1-----R3的E0口连接,分别启用loopback10接口,在全局模式下启用ipv6 unicast-routing ,和ipv6 rip 路由进程;在接口启用ipv6 enable,并且在接口启用ipv6 rip的路由。需要注意的地方,ipv6 rip Cisco, Cisco是进程的表示。在接口下的rip路由要与进程中的表识相同,并且大小写敏感。

  ipv6 ICMP debug

  *Mar 1 01:10:02.651: IPv6: SAS picked source 2010::1 for 2003::3 (Loopback10)

  *Mar 1 01:10:02.655: ICMPv6: Sending echo request to 2003::3

  *Mar 1 01:10:02.659: IPv6: nexthop FE80::250:73FF:FE6C:6813,

  *Mar 1 01:10:02.663: IPV6: source 2010::1 (local)

  *Mar 1 01:10:02.667: dest 2003::3 (Ethernet0)

  *Mar 1 01:10:02.667: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating

  *Mar 1 01:10:02.671: IPv6: Sending on Ethernet0

  *Mar 1 01:10:02.679: IPV6: source 2003::3 (Ethernet0)

  *Mar 1 01:10:02.683: dest 2010::1

  *Mar 1 01:10:02.683: traffic class 0, flow 0x0, len 100+14, prot 58, hops 64, forward to ulp

  *Mar 1 01:10:02.687: ICMPv6: Received ICMPv6 packet from 2003::3, type 129

  *Mar 1 01:10:02.691: ICMPv6: Received echo reply from 2003::3

  *Mar 1 01:10:02.695: IPv6: SAS picked source 2010::1 for 2003::3 (Loopback10)

  *Mar 1 01:10:02.699: ICMPv6: Sending echo request to 2003::3

  *Mar 1 01:10:02.703: IPv6: nexthop FE80::250:73FF:FE6C

  Rack0:6813,

  *Mar 1 01:10:02.707: IPV6: source 2010::1 (local)

  *Mar 1 01:10:02.711: dest 2003::3 (Ethernet0)

  *Mar 1 01:10:02.711: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating

  *Mar 1 01:10:02.715: IPv6: Sending on Ethernet0

  *Mar 1 01:10:02.723: IPV6: source 2003::3 (Ethernet0)

  *Mar 1 01:10:02.723: dest 2010::1

  *Mar 1 01:10:02.727: traffic class 0, flow 0x0, len 100+14, prot 58, hops 64, forward to ulp

  *Mar 1 01:10:02.727: ICMPv6: Received ICMPv6 packet from 2003::3, type 129

  *Mar 1 01:10:02.731: ICMPv6: Received echo reply from 2003::3

  *Mar 1 01:10:02.739: IPv6: SAS picked source 2010::1 for 2003::3 (Loopback10)

  *Mar 1 01:10:02.743: ICMPv6: Sending echo request to 2003::3

  *Mar 1 01:10:02.747: IPv6: nexthop FE80::250:73FF:FE6C:6813,

  *Mar 1 01:10:02.747: IPV6: source 2010::1 (local)

  *Mar 1 01:10:02.751: dest 2003::3 (Ethernet0)

  *Mar 1 01:10:02.755: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating

  *Mar 1 01:10:02.755: IPv6: Sending on Ethernet0

  *Mar 1 01:10:02.763: IPV6: source 2003::3 (Ethernet0)

  *Mar 1 01:10:02.767: dest 2010::1

  *Mar 1 01:10:02.767: traffic class 0, flow 0x0, len 100+14, prot 58, hops 64, forward to ulp

  *Mar 1 01:10:02.771: ICMPv6: Received ICMPv6 packet from 2003::3, type 129

  *Mar 1 01:10:02.775: ICMPv6: Received echo reply from 2003::3

  *Mar 1 01:10:02.779: IPv6: SAS picked source 2010::1 for 2003::3 (Loopback10)

  *Mar 1 01:10:02.783: ICMPv6: Sending echo request to 2003::3

  *Mar 1 01:10:02.787: IPv6: nexthop FE80::250:73FF:FE6C:6813,

  *Mar 1 01:10:02.791: IPV6: source 2010::1 (local)

  *Mar 1 01:10:02.791: dest 2003::3 (Ethernet0)

  *Mar 1 01:10:02.795: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating

  *Mar 1 01:10:02.799: IPv6: Sending on Ethernet0

  *Mar 1 01:10:02.803: IPV6: source 2003::3 (Ethernet0)

  *Mar 1 01:10:02.807: dest 2010::1

  *Mar 1 01:10:02.807: traffic class 0, flow 0x0, len 100+14, prot 58, hops 64, forward to ulp

  *Mar 1 01:10:02.811: ICMPv6: Received ICMPv6 packet from 2003::3, type 129

  *Mar 1 01:10:02.815: ICMPv6: Received echo reply from 2003::3

  *Mar 1 01:10:02.819: IPv6: SAS picked source 2010::1 for 2003::3 (Loopback10)

  *Mar 1 01:10:02.823: ICMPv6: Sending echo request to 2003::3

  *Mar 1 01:10:02.827: IPv6: nexthop FE80::250:73FF:FE6C:6813,

  *Mar 1 01:10:02.831: IPV6: source 2010::1 (local)

  *Mar 1 01:10:02.831: dest 2003::3 (Ethernet0)

  *Mar 1 01:10:02.835: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating

  *Mar 1 01:10:02.839: IPv6: Sending on Ethernet0

  *Mar 1 01:10:02.843: IPV6: source 2003::3 (Ethernet0)

  *Mar 1 01:10:02.847: dest 2010::1

  *Mar 1 01:10:02.847: traffic class 0, flow 0x0, len 100+14, prot 58, hops 64, forward to ulp

  *Mar 1 01:10:02.851: ICMPv6: Received ICMPv6 packet from 2003::3, type 129

  *Mar 1 01:10:02.855: ICMPv6: Received echo reply from 2003::3

  *Mar 1 01:10:04.907: IPV6: source FE80::260:5CFF:FEF4:CD0A (local)

  *Mar 1 01:10:04.911: dest FF02::9 (Ethernet0)

  *Mar 1 01:10:04.915: traffic class 224, flow 0x0, len 92+1408, prot 17, hops 255, originating

  *Mar 1 01:10:04.915: IPv6: Sending on Ethernet0

  *Mar 1 01:10:04.919: IPV6: source FE80::260:5CFF:FEF4:CD0A (local)

  *Mar 1 01:10:04.923: dest FF02::9 (Loopback10)

  *Mar 1 01:10:04.927: traffic class 224, flow 0x0, len 112+1402, prot 17, hops 255, originating

  *Mar 1 01:10:04.931: IPv6: Sending on Loopback101R1#

  Rack01R1#

  *Mar 1 01:10:07.679: IPV6: source FE80::250:73FF:FE6C:6813 (Ethernet0)

  *Mar 1 01:10:07.683: dest FE80::260:5CFF:FEF4:CD0A

  *Mar 1 01:10:07.683: traffic class 224, flow 0x0, len 72+14, prot 58, hops 255, forward to ulp

  *Mar 1 01:10:07.687: ICMPv6: Received ICMPv6 packet from FE80::250:73FF:FE6C:6813, type 135

  *Mar 1 01:10:07.691: IPV6: source FE80::260:5CFF:FEF4:CD0A (local)

  *Mar 1 01:10:07.695: dest FE80::250:73FF:FE6C:6813 (Ethernet0)

  *Mar 1 01:10:07.699: traffic class 224, flow 0x0, len 64+16, prot 58, hops 255, originating

  *Mar 1 01:10:07.703: IPv6: Sending on Ethernet0

  Rack01R1#sh debugging

  Generic IPv6:

  ICMP packet debugging is on

  IPv6 unicast packet debugging is on

  发现在ping的时候发出的包是以环回地址为source,在ipv4中是以出站借口地址为source.这里有点不太理解。

  Rack01R3#deb ip icmp

  ICMP packet debugging is on

  Rack01R3#deb ip pa

  IP packet debugging is on

  Rack01R3#p 10.10.10.1

  Type escape sequence to abort.

  Sending 5, 100-byte ICMP Echos to 10.10.10.1, timeout is 2 seconds:

  *Mar 1 01:14:20.459: IP: tableid=0, s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), routed via RIB

  *Mar 1 01:14:20.463: IP: s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), len 100, sending

  *Mar 1 01:14:20.471: IP: s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), len 100, encapsulation failed.!!!!

  Success rate is 80 percent (4/5), round-trip min/avg/max = 24/27/28 ms

  Rack01R3#

  *Mar 1 01:14:22.459: IP: tableid=0, s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), routed via RIB

  *Mar 1 01:14:22.463: IP: s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), len 100, sending

  *Mar 1 01:14:22.475: IP: tableid=0, s=10.10.10.1 (Ethernet0), d=10.10.10.3 (Ethernet0), routed via RIB

  *Mar 1 01:14:22.479: IP: s=10.10.10.1 (Ethernet0), d=10.10.10.3 (Ethernet0), len 100, rcvd 3

  *Mar 1 01:14:22.483: ICMP: echo reply rcvd, src 10.10.10.1, dst 10.10.10.3

  *Mar 1 01:14:22.487: IP: tableid=0, s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), routed via RIB

  *Mar 1 01:14:22.491: IP: s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), len 100, sending

  *Mar 1 01:14:22.503: IP: tableid=0, s=10.10.10.1 (Ethernet0), d=10.10.10.3 (Ethernet0), routed via RIB

  *Mar 1 01:14:22.507: IP: s=10.10.10.1 (Ethernet0), d=10.10.10.3 (Ethernet0), len 100, rcvd 3

  *Mar 1 01:14:22.511: ICMP: echo reply rcvd, src 10.10.10.1, dst 10.10.10.3

  *Mar 1 01:14:22.519: IP: tableid=0, s=10.10.10.3 (local)

  Rack01R, d=10.10.10.1 (Ethernet0), routed via RIB

  *Mar 1 01:14:22.523: IP: s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), len 100, sending

  *Mar 1 01:14:22.531: IP: tableid=0, s=10.10.10.1 (Ethernet0), d=10.10.10.3 (Ethernet0), routed via RIB

  *Mar 1 01:14:22.535: IP: s=10.10.10.1 (Ethernet0), d=10.10.10.3 (Ethernet0), len 100, rcvd 3

  *Mar 1 01:14:22.539: ICMP: echo reply rcvd, src 10.10.10.1, dst 10.10.10.3

  *Mar 1 01:14:22.547: IP: tableid=0, s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), routed via RIB

  *Mar 1 01:14:22.551: IP: s=10.10.10.3 (local), d=10.10.10.1 (Ethernet0), len 100, sending

  *Mar 1 01:14:22.563: IP: tableid=0, s=10.10.10.1 (Ethernet0), d=10.10.10.3 (Ethernet0), routed via RIB

  *Mar 1 01:14:22.567: IP: s=10.10.10.1 (Ethernet0), d=10.10.10.3 (Ethernet0), len 100, rcvd 3

  *Mar 1 01:14:22.571: ICMP: echo reply rcvd, src 10.10.10.1, dst 10.10.10.33#

  ---------------------ipv4的ping--------------------------

  Gateway of last resort is not set

  R 20.0.0.0/8 [120/1] via 10.10.10.1, 00:00:05, Ethernet0

  10.0.0.0/24 is subnetted, 1 subnets

  C 10.10.10.0 is directly connected, Ethernet0

  Rack01R3#deb ip icm

  ICMP packet debugging is on

  Rack01R3#deb ip pa

  IP packet debugging is on

  Rack01R3#p 20.20.20.1

  Type escape sequence to abort.

  Sending 5, 100-byte ICMP Echos to 20.20.20.1, timeout is 2 seconds:

  !!!!!

  Success rate is 100 percent (5/5), round-trip min/avg/max = 24/26/28 ms

  Rack01R3#

  *Mar 1 01:16:53.891: IP: tableid=0, s=10.10.10.3 (local), d=20.20.20.1 (Ethernet0), routed via RIB

  *Mar 1 01:16:53.895: IP: s=10.10.10.3 (local), d=20.20.20.1 (Ethernet0), len 100, sending

  *Mar 1 01:16:53.907: IP: tableid=0, s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), routed via RIB

  *Mar 1 01:16:53.911: IP: s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), len 100, rcvd 3

  *Mar 1 01:16:53.915: ICMP: echo reply rcvd, src 20.20.20.1, dst 10.10.10.3

  *Mar 1 01:16:53.923: IP: tableid=0, s=10.10.10.3 (local), d=20.20.20.1 (Ethernet0), routed via RIB

  *Mar 1 01:16:53.927: IP: s=10.10.10.3 (local), d=20.20.20.1 (Ethernet0), len 100, sending

  *Mar 1 01:16:53.935: IP: tableid=0, s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), routed via RIB

  *Mar 1 01:16:53.939: IP: s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), len 100, rcvd 3

  *Mar 1 01:16:53.947: ICMP: echo reply rcvd, src 20.20.20.1, dst 10.10.10.3

  *Mar 1 01:16:53.951: IP: tableid=0, s=10.10.10.3 (local)

  Rack01, d=20.20.20.1 (Ethernet0), routed via RIB

  *Mar 1 01:16:53.955: IP: s=10.10.10.3 (local), d=20.20.20.1 (Ethernet0), len 100, sending

  *Mar 1 01:16:53.967: IP: tableid=0, s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), routed via RIB

  *Mar 1 01:16:53.971: IP: s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), len 100, rcvd 3

  *Mar 1 01:16:53.975: ICMP: echo reply rcvd, src 20.20.20.1, dst 10.10.10.3

  *Mar 1 01:16:53.983: IP: tableid=0, s=10.10.10.3 (local), d=20.20.20.1 (Ethernet0), routed via RIB

  *Mar 1 01:16:53.987: IP: s=10.10.10.3 (local), d=20.20.20.1 (Ethernet0), len 100, sending

  *Mar 1 01:16:53.995: IP: tableid=0, s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), routed via RIB

  *Mar 1 01:16:53.999: IP: s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), len 100, rcvd 3

  *Mar 1 01:16:54.007: ICMP: echo reply rcvd, src 20.20.20.1, dst 10.10.10.3

  *Mar 1 01:16:54.011: IP: tableid=0, s=10.10.10.3 (local), d=20.20.20.1 (Ethernet0), routed via RIB

  *Mar 1 01:16:54.015: IP: s=10.10.10.3 (local), d=20.20.20.1 (Ethernet0), len 100, sending

  *Mar 1 01:16:54.027: IP: tableid=0, s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), routed via RIB

  *Mar 1 01:16:54.031: IP: s=20.20.20.1 (Ethernet0), d=10.10.10.3 (Ethernet0), len 100, rcvd 3

  *Mar 1 01:16:54.035: ICMP: echo reply rcvd, src 20.20.20.1, dst 10.10.10.3R3#

  Rack01R3#

  *Mar 1 01:16:56.211: IP: s=10.10.10.1 (Ethernet0), d=224.0.0.9, len 52, rcvd 2

    • 评论
    • 分享微博
    • 分享邮件
    邮件订阅

    如果您非常迫切的想了解IT领域最新产品与技术信息,那么订阅至顶网技术邮件将是您的最佳途径之一。

    重磅专题
    往期文章
    最新文章