1 / 81

CIS 185 CCNP ROUTE Ch. 8 Implementing IPv6 – Part 2

CIS 185 CCNP ROUTE Ch. 8 Implementing IPv6 – Part 2. Rick Graziani Cabrillo College graziani@cabrillo.edu Last Updated: Fall 2010. Materials. Book: Implementing Cisco IP Routing (ROUTE) Foundation Learning Guide: Foundation learning for the ROUTE 642-902 Exam By Diane Teare Book

dyre
Download Presentation

CIS 185 CCNP ROUTE Ch. 8 Implementing IPv6 – Part 2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CIS 185 CCNP ROUTECh. 8 Implementing IPv6 – Part 2 Rick Graziani Cabrillo College graziani@cabrillo.edu Last Updated: Fall 2010

  2. Materials • Book: • Implementing Cisco IP Routing (ROUTE) Foundation Learning Guide: Foundation learning for the ROUTE 642-902 Exam • By Diane Teare • Book • ISBN-10: 1-58705-882-0 • ISBN-13: 978-1-58705-882-0 • eBook • ISBN-10: 0-13-255033-4 • ISBN-13: 978-0-13-255033-8

  3. IPv6 Routing Protocols • Static routes • RIP new generation (RIPng) (defined in RFC 2080, RIPng for IPv6) • OSPFv3 (defined in RFC 5340, OSPF for IPv6) • EIGRP for IPv6 • Multiprotocol Border Gateway Protocol Version 4 (MP-BGP4 or MBGP) (defined in RFC 2545, Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing, and RFC 4760, Multiprotocol Extensions for BGP-4)

  4. Router(config)# ipv6 unicast-routing • Ipv6 unicast-routing global configuration command • enables IPv6 routing • Required before any ipv6 routing protocol can be configured

  5. IPv6 Static Routes Router(config)# ipv6 route ipv6-prefix/prefix-length {ipv6-address | interface-type interface-number [ipv6-address]} [administrative-distance] [administrative-multicast-distance | unicast| multicast] [next-hop-address] [tag tag] Types of static routes (same as IPv4) • A directly attached static route is created using only the interface-type and interface-number parameters. Router(config)# ipv6 route 2001:CC1E::/32 serial 0/0/0 • A recursive static route is created using only the next-hop address parameter. Router(config)# ipv6 route 2001:CC1E::/32 2001:12::1 • A fully specified static route includes both the outgoing interface and the next hop address. Router(config)# ipv6 route 2001:CC1E::/32 ser 0/0/0 2001:12::1 • A floating static route • Router(config)# ipv6 route 2001:CC1E::/32 ser 0/0/0 15

  6. Default :: R1(config)# ipv6 unicast-routing R1(config)# ipv6 route 13::/64 s0/1/0 R1# show ipv6 route static IPv6 Routing Table - 9 entries <output omitted> S 13::/64 [1/0] via ::, Serial0/1/0 R2(config)# ipv6 unicast-routing R2(config)# ipv6 route ::/64 s0/1/0 R2# show ipv6 route static IPv6 Routing Table - 7 entries <output omitted> S ::/64 [1/0] via ::, Serial0/1/0

  7. R1# ping 13::13:1 !!!!! R1# R2# ping 11::11:1 !!!!! R2# ping 10::10:1 !!!!! R2#

  8. RIPng (the Next Generation) For Enterprise Networks

  9. RIPv2 vs RIPng IPv4 IPv6 IPv4, UDP IPv6, UDP 520 521 IPv4 address IPv6 link-local address 224.0.0.9 FF02::9 RIP-specific uses IPv6 AH/ESP yes yes 120 120 yes yes yes N/A yes yes yes yes yes yes yes yes yes yes 16 16 yes yes Advertises routes for… Layer 3/4 protocols UDP Port Source IP address Multicast Update destination (All RIP routers) Authentication Use Distance Vector Default Administrative distance Supports VLSM Automatic summarization Uses Split Horizon Uses Poison Reverse 30 second periodic full updates Uses triggered updates Uses Hop Count metric Metric meaning infinity Supports route tags

  10. Enable IPv6 routing Configure an IPv6 addressing and enable RIPng, process “luigi" R1(config)# ipv6 unicast-routing R1(config)# interface FastEthernet0/0 R1(config-if)# ipv6 address 2012::1/64 R1(config-if)# ipv6 rip luigi enable R1(config)# interface FastEthernet0/1 R1(config-if)# ipv6 address 2013::1/64 R1(config-if)# ipv6 rip luigi enable R1(config)# interface Serial0/0/0 R1(config-if)# ipv6 address 2014::1/64 R1(config-if)# ipv6 rip luigi enable R1(config)# interface Serial0/0/1 R1(config-if)# ipv6 address 2015::1/64 R1(config-if)# ipv6 rip luigi enable R1(config)# ipv6 router luigi Create the RIPng process named “luigi“

  11. R3# show ipv6 route IPv6 Routing Table - Default - 19 entries Codes: C - Connected, L - Local, S - Static, U - Per-user Static route B - BGP, M - MIPv6, R - RIP, I1 - ISIS L1 <output omitted> R 2005::/64 [120/3] via FE80::11FF:FE11:1111, Serial0/0/0 via FE80::22FF:FE22:2222, Serial0/0/1 R 2012::/64 [120/2] via FE80::11FF:FE11:1111, Serial0/0/0 via FE80::22FF:FE22:2222, Serial0/0/1 All next-hop IP addresses that begin with FE80 – RIPng uses link local addresses as next-hop addresses.

  12. RIPng over Frame Relay • See our text book for an example of RIPng over Frame Relay.

  13. OSPFv3 OSPFv3

  14. OSPF vs OSPFv3 IPv4 IPv6 IPv4 IPv6 89 89 IPv4 address IPv6 link-local 224.0.0.5 FF02::5 224.0.0.6 FF02::6 yes yes yes yes same same same same same same same same same same yes yes yes yes yes yes yes yes yes yes 30 minutes 30 minutes OSPF-specific uses IPv6 AH/ESP same no "same subnet" check no yes Advertises routes for… Layer 3 protocol IP Protocol Type Source IP address Multicast – all SPF routers Multicast – All Designated routers Uses Link State logic Supports VLSM RID process, compared to OSPFv2 LSA flooding and aging compared to OSPFv2 Area structure compared to OSPFv2 Packet types LSA flooding and aging compared to OSPFv2 RID 32-bit LSID Cost metric, bandwidth Supports route tags DR/BDR election compared to OSPFv2 Periodic re-flooding every… Authentication Neighbor checks compared to OSPFv2 (table 5-5) multiple instances per interface

  15. OSPF Version 3 (OSPFv3) (RFC 2740) • Router ID: • OSPFv3 uses the same process as OSPFv2 including an IPv4 address. • If there are no IPv4 addresses configured, the router ID (IPv4 address) must be explicitly configured. • Similar to OSPF for IPv4: • Same mechanisms, but a major rewrite of the internals of the protocol • Updated features for IPv6: • Every IPv4-specific semantic is removed • Carry IPv6 addresses • Link-local addresses used as source

  16. Example of two instances of OSPFv3 running on the same physical network segment, using two different IPv6 prefixes. • OSPF interfaces connect to links instead of to IP subnets. • Multiple IPv6 subnets can be assigned to a single link, and two nodes can talk directly over a single link, even if they do not share a common IPv6 subnet (IPv6 prefix), because they use the link-local addresses, rather than the global unicast addresses, to communicate. • OSPF for IPv6 therefore runs per-link instead of the IPv4 behavior of per-IP-subnet • OSPFv3 has explicit support for multiple instances per link through the instance ID field in the packet header. • This feature allows separate routing domains, each running OSPF, to use a common link. • A single link could belong to multiple areas. • Instances need to have the same instance ID to communicate with each other. • By default, the instance ID is 0

  17. OSPFv3—Similarities with OSPFv2 • OSPFv3 is OSPF for IPv6 (RFC 2740): • Based on OSPFv2, with enhancements • Distributes IPv6 prefixes • Runs directly over IPv6 • OSPFv3 & v2 can be run concurrently, because each address family has a separate SPF (ships in the night). • OSPFv3 uses the same basic packet types as OSPFv2: • Hello • Database description blocks (DDB) • Link state request (LSR) • Link state update (LSU) • Link state acknowledgement (ACK) • Neighbor discovery and adjacency formation mechanism are identical. • LSA flooding and aging mechanisms are identical.

  18. The multicast addresses used by OSPFv3 are as follows: • FF02::5—This address represents all SPF routers on the link-local scope; it is equivalent to 224.0.0.5 in OSPFv2. • FF02::6—This address represents all designated routers (DRs) on the link-local scope; it is equivalent to 224.0.0.6 in OSPFv2.

  19. Enable the interface for OSPFv3 Creates the “ipv6 router ospf 100” process dynamically Enable the interface for OSPFv3 • Two routers and two areas • Area 1 • Area 0 Enable the interface for OSPFv3 Creates the “ipv6 router ospf 100” process dynamically Summarizes area 0’s routes to the 2001:410::/32 route

  20. This network has three areas.

  21. R1(config)# ipv6 unicast-routing R1(config)# interface Serial0/1/0 R1(config-if)# ipv6 address 12:12::1/64 R1(config-if)# ipv6 ospf 1 area 0 R1(config)# interface Fa0/0 R1(config-if)# ipv6 address 13:13::1/64 R1(config-if)# ipv6 ospf 1 area 13 R1(config)# ipv6 router ospf 1 R1(config-router)# router-id 0.0.0.1 R2(config)# ipv6 unicast-routing R2(config)# interface Serial0/1/0 R2(config-if)# ipv6 address 12:12::2/64 R2(config-if)# ipv6 ospf 1 area 0 R2(config)# interface Fa0/0 R2(config-if)# ipv6 address 24:24::1/64 R2(config-if)# ipv6 ospf 1 area 24 R2(config)# ipv6 router ospf 1 R2(config-router)# router-id 0.0.0.2 • These routers do not have any IPv4 addresses configured, so the 32-bit router ID must be configured with the router-id command

  22. R2# show ipv6 ospf neighbor Neighbor ID Pri State Dead Time Interface ID Interface 0.0.0.1 1 FULL/ - 00:00:39 6 Serial0/1/0 R2# show ipv6 ospf interface serial 0/1/0 Serial0/1/0 is up, line protocol is up Link Local Address FE80::219:55FF:FE92:B212, Interface ID 6 Area 0, Process ID 1, Instance ID 0, Router ID 0.0.0.2 Network Type POINT_TO_POINT, Cost: 64 Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40,Wait 40, Retransmit 5 Hello due in 00:00:06 Index 1/3/3, flood queue length 0 Next 0x0(0)/0x0(0)/0x0(0) <output omitted> • This output is from R2, and indicates that R2 has a FULL relationship with R1.

  23. R2(config)# ipv6 unicast-routing R2(config)# interface Serial0/1/0 R2(config-if)# ipv6 address 12:12::2/64 R2(config-if)# ipv6 ospf 1 area 0 R2(config)# interface Fa0/0 R2(config-if)# ipv6 address 24:24::1/64 R2(config-if)# ipv6 ospf 1 area 24 R2(config)# ipv6 router ospf 1 R2(config-router)# router-id 0.0.0.2 R4(config)# ipv6 unicast-routing R4(config)# interface Fa0/0 R4(config-if)# ipv6 address 24:24::4/64 R4(config-if)# ipv6 ospf 1 area 24 R4(config)# ipv6 router ospf 1 R4(config-router)# router-id 0.0.0.4 • R2 was configured earlier. • Here is the configuration for R4

  24. R4# show ipv6 route ospf OI 12:12::/64 [110/65] via FE80::219:55FF:FE92:B212, FastEthernet0/0 • OSPF portion of R4’s routing table • Includes the 12:12::/64 inter-area route; the link between R1 and R2.

  25. R1(config)# ipv6 unicast-routing R1(config)# interface Serial0/1/0 R1(config-if)# ipv6 address 12:12::1/64 R1(config-if)# ipv6 ospf 1 area 0 R1(config)# interface Fa0/0 R1(config-if)# ipv6 address 13:13::1/64 R1(config-if)# ipv6 ospf 1 area 13 R1(config)# ipv6 router ospf 1 R1(config-router)# router-id 0.0.0.1 R3(config)# ipv6 unicast-routing R3(config)# interface Fa0/0 R3(config-if)# ipv6 address 13:13::3/64 R3(config-if)# ipv6 ospf 1 area 13 R3(config)# ipv6 router ospf 1 R3(config-router)# router-id 0.0.0.3 • R1 was configured earlier. • Here is the configuration for R3

  26. R3# show ipv6 route ospf OI 12:12::/64 [110/65] via FE80::219:56FF:FE2C:9F60, FastEthernet0/0 OI 24:24::/64 [110/66] via FE80::219:56FF:FE2C:9F60, FastEthernet0/0 R3# ping 24:24::4 !!!!! R3# • OSPF portion of R3’s routing table

  27. R1(config)# ipv6 unicast-routing R1(config)# interface Serial0/1/0 R1(config-if)# ipv6 address 12:12::1/64 R1(config-if)# ipv6 ospf 1 area 0 R1(config)# interface Fa0/0 R1(config-if)# ipv6 address 13:13::1/64 R1(config-if)# ipv6 ospf 1 area 13 stub no summary R1(config)# ipv6 router ospf 1 R1(config-router)# router-id 0.0.0.1 Totally Stubby R3(config)# ipv6 unicast-routing R3(config)# interface Fa0/0 R3(config-if)# ipv6 address 13:13::3/64 R3(config-if)# ipv6 ospf 1 area 13 stub R3(config)# ipv6 router ospf 1 R3(config-router)# router-id 0.0.0.3 • Area 13 can be configured to be a totally stubby area since the area has only one ABR which it can use to get anywhere outside of the area. • R3 now only has a default route (::/0), but it can still ping R4 successfully

  28. Totally Stubby R3# show ipv6 route ospf OI ::/0 [110/2] via FE80::219:56FF:FE2C:9F60, FastEthernet0/0 R3# ping 24:24::4 !!!!! R3# • R3 now only has a default route (::/0), but it can still ping R4 successfully.

  29. EIGRP for IPv6 For Winnebago Networks

  30. EIGRP vs EIGRP for IPv6 IPv4 IPv6 IPv4 IPv6 88 88 N/A N/A yes yes yes yes yes yes yes N/A yes yes yes yes 224.0.0.10 FF02::10 EIGRP-specific IPv6 AH/ESP Advertises routes for… Layer 3 protocol for EIGRP messages Layer 3 header protocol type UDP Port Uses Successor, Feasible Successor Uses Dual Supports VLSM Can perform automatic summarization Uses triggered updates Default metric bandwidth and delay Multicast Update destination Authentication

  31. EIGRP for IPv6 • EIGRP RID decision steps based on IPv4 configuration: • Use the configured value (using the eigrp router-ida.b.c.d EIGRP subcommand under the ipv6 router eigrp command) • Use the highest IPv4 address on an up/up loopback interface • Use the highest IPv4 address on an up/up non-loopback interface • IOS lets you stop and start the EIGRP process with the shutdown and no shutdown router mode subcommands. • After initial configuration, the EIGRP for IPv6 process starts in shutdown mode, • To start the EIGRP process it is required to issue the no shutdown

  32. EIGRP for IPv6 configuration • All interfaces have IPv6 addresses, including the three loopback interfaces on R3.

  33. R1(config)# ipv6 unicast-routing R1(config)# interface Serial0/0/0.2 point-to-point R1(config-if)# ipv6 address 12::1/64 R1(config-if)# ipv6 eigrp 100 R1(config)# interface Serial0/0/0.3 point-to-point R1(config-if)# ipv6 address 13::1/64 R1(config-if)# ipv6 eigrp 100 R1(config)# ipv6 router eigrp 100 R1(config-router)# router-id 1.1.1.1 R1(config-router)# no shutdown R3(config)# ipv6 unicast-routing R3(config)# interface Serial0/0/0.1 point-to-point R3(config-if)# ipv6 address 13::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# interface loopback 301 R3(config-if)# ipv6 address 3:1::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# interface loopback 302 R3(config-if)# ipv6 address 3:2::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# interface loopback 303 R3(config-if)# ipv6 address 3:3::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# ipv6 router eigrp 100 R3(config-router)# router-id 3.3.3.3 R3(config-router)# no shutdown

  34. R1# show ipv6 route eigrp D 3:1::/64 [90/2297856] via FE80::3, Serial 0/0/0.3 D 3:2::/64 [90/2297856] via FE80::3, Serial 0/0/0.3 D 3:3::/64 [90/2297856] via FE80::3, Serial 0/0/0.3

  35. R2(config)# ipv6 unicast-routing R2(config)# interface Serial0/0/0.1 point-to-point R2(config-if)# ipv6 address 12::2/64 R2(config-if)# ipv6 eigrp 100 R2(config)# interface Serial0/0/0.4 point-to-point R2(config-if)# ipv6 address 24::2/64 R2(config-if)# ipv6 eigrp 100 R2(config)# ipv6 router eigrp 100 R2(config-router)# router-id 2.2.2.2 R2(config-router)# no shutdown R4(config)# ipv6 unicast-routing R4(config)# interface Serial0/0/0.2 point-to-point R4(config-if)# ipv6 address 24::4/64 R4(config-if)# ipv6 eigrp 100 R4(config)# ipv6 router eigrp 100 R4(config-router)# router-id 3.3.3.3 R4(config-router)# no shutdown

  36. R4# show ipv6 route eigrp D 3:1::/64 [90/3321856] via FE80::2, Serial 0/0/0.2 D 3:2::/64 [90/3321856] via FE80::2, Serial 0/0/0.2 D 3:3::/64 [90/3321856] via FE80::2, Serial 0/0/0.2 D 12::/64 [90/2681856] via FE80::2, Serial 0/0/0.2 D 13::/64 [90/2681856] via FE80::2, Serial 0/0/0.2 R4# ping 3:1::3 !!!!!

  37. R4# show ipv6 eigrp neighbors IPv6-EIGRP neighbors for process 1 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 0 Link-local address: Se0/0/0.2 14 01:50:51 3 200 0 82 FE80::2

  38. R4(config)# ipv6 unicast-routing R4(config)# interface Serial0/0/0.2 point-to-point R4(config-if)# ipv6 address 24::4/64 R4(config-if)# ipv6 eigrp 100 R4(config)# ipv6 router eigrp 100 R4(config-router)# router-id 3.3.3.3 R4(config-router)# eirgp stub R4(config-router)# no shutdown No EIGRP Queries sent to R4 EIGRP Update X EIGRP Reply Stub • Remember an EIGRP stub router indicates in its hello packet to all neighboring routers its status as a stub router. • The neighboring routers do not query the stub router for any routes. • Since R4 is a stub router, it should be configured as such, to stop unnecessary queries going to it. • If the link goes down between R3 and R1, there are no queries sent to R4 • Only an update and a reply message are received, telling R4 about the deleted route.

  39. R3(config)# ipv6 unicast-routing R3(config)# interface Serial0/0/0.1 point-to-point R3(config-if)# ipv6 address 13::3/64 R3(config-if)# ipv6 eigrp 100 R3(config-if)# ipv6 summary-address eigrp 100 3::/16 R3(config)# interface loopback 301 R3(config-if)# ipv6 address 3:1::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# interface loopback 302 R3(config-if)# ipv6 address 3:2::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# interface loopback 303 R3(config-if)# ipv6 address 3:3::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# ipv6 router eigrp 100 R3(config-router)# router-id 3.3.3.3 R3(config-router)# no shutdown EIGRP Summary • Another feature supported by EIGRP for IPv6 is route summarization. • Unlike EIGRP for IPv4, this protocol does not automatically summarize

  40. R3(config)# ipv6 unicast-routing R3(config)# interface Serial0/0/0.1 point-to-point R3(config-if)# ipv6 address 13::3/64 R3(config-if)# ipv6 eigrp 100 R3(config-if)# ipv6 summary-address eigrp 100 3::/16 R3(config)# interface loopback 301 R3(config-if)# ipv6 address 3:1::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# interface loopback 302 R3(config-if)# ipv6 address 3:2::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# interface loopback 303 R3(config-if)# ipv6 address 3:3::3/64 R3(config-if)# ipv6 eigrp 100 R3(config)# ipv6 router eigrp 100 R3(config-router)# router-id 3.3.3.3 R3(config-router)# no shutdown EIGRP Summary R4# show ipv6 route eigrp D 3::/16 [90/3321856] via FE80::2, Serial 0/0/0.2 D 12::/64 [90/2681856] via FE80::2, Serial 0/0/0.2 D 13::/64 [90/2681856] via FE80::2, Serial 0/0/0.2 R4# ping 3:1::3 !!!!!

  41. MBGP

  42. IPv4 Header TCP Header BGP: IPv4 Prefixes IPv4 Header TCP Header BGP: IPv6 Prefixes IPv6 Header TCP Header BGP: IPv6 Prefixes Multiprotocol BGP • IPv6-specific extensions incorporated into MBGP include the following: • The NEXT_HOP and Network Layer Reachability Information (NLRI) attributes are expressed as IPv6 addresses and prefixes. • Operates by identifying two separate protocols: • Carrier protocol • Passenger protocol

  43. IPv4 Header TCP Header BGP: IPv4 Prefixes • In an all-IPv4 environment, BGP establishes sessions using IPv4 • IPv4 is the carrier protocol • The routes that BGP advertises are also IPv4 • IPv4 is also the passenger protocol

  44. IPv4 Header TCP Header BGP: IPv6 Prefixes • Protocols other than IPv4 also need to advertise reachability information: • MPLS VPN • Multicast • IPv6 prefixes for BGP • MBGP extensions allow these and other protocols to be carried using BGP. • An analogy is that BGP is a truck that can transport multiple payloads. • BGP “truck” (IPv4) could be used to transport “payloads” (IPv6 prefixes) • The carrier protocol is IPv4 • The passenger protocol is IPv6 prefixes being advertised

  45. IPv6 Header TCP Header BGP: IPv6 Prefixes • In an all IPv6 environment, BGP can be used as both the: • Carrier protocol • Passenger protocol • Both the truck and the payload are IPv6 • In this case IPv6 is used to: • Establish BGP sessions • BGP advertises IPv6 prefixes

  46. IPv6 Header TCP Header BGP: IPv6 Prefixes • The first section: • router bgp configuration defines a 32-bit router ID (which must be configured in an IPv6-only network) • The peering session is established using IPv6, so IPv6 is the carrier protocol. • The second section: • address-family ipv6 command defines the passenger protocol, the protocol that is to be advertised using MBGP. • The passenger protocol is IPv6.

  47. IPv6 Policy Base Routing (PBR) • Policy-based routing (PBR) allows the network administrator to define a routing policy other than destination-based routing using the routing table. • Sometimes called traffic engineering • Provide a higher degree of control over routing • Available for both IPv4 and IPv6 • Like IPv4, IPv6 PBR is based on: • match commands for identifying the traffic to be policy-based routed • set commands for defining how that traffic will be routed

  48. R1(config)# interface fa 0/0 R1(config-if)# ipv6 policy route-map PBR_SOURCE_ADDRESS R1(config)# route-map PBR_SOURCE_ADDRESS permit 10 R1(config-route-map)# match ipv6 address SOURCE_104 R1(config-route-map)# set ipv6 next-hop 123::3 R1(config)# ipv6 access-list SOURCE_104 R1(config-ipv6-acl)# permit ipv6 104::/64 any • Recall that PBR is configured on the interface that receives the traffic that should be routed differently than the default path. • R1: The traffic is received on the FastEthernet 0/0 interface • If the packets are from R4’s loopback interface, they will be routed via R3 • Otherwise they will be routed normally, through R2. • Notice the ipv6 commands which are similar to ipv4: • match ipv6 address • ipv6 access-list • permit ipv6 • Can verify with ping and debug ipv6 policy commands

  49. IPv6 Redistribution

  50. IPv6 Redistribution • Similar to IPv4, IPv6 routing information can be redistributed between routing protocols, and between instances of routing protocols. • The examples used in this section are a bit complex, maybe more than they need to be, but… • This also is a good review of IPv4 redistribution. • It’s exactly the same only different.

More Related