Lab Objective:
The focus of this lab is to understand tunneling implementation and configuration in Cisco IOS routers. Additional technologies include Multi Protocol Border Gateway Protocol (MP-BGP).
Lab Topology:
The lab network topology is illustrated below:
|
IMPORTANT NOTE If you are using the www.howtonetwork.net racks, please bring up the LAN interfaces connected to the routers by issuing the no shutdown command on the connected switches. If you are using a home lab with no interface fastethernet 0/0 Alternately, you can simply connect the interfaces to a hub or switch if you have one available in your own lab. |
Task 1
Configure hostnames, IP addressing on all routers as illustrated in the network topology.
Task 2
Enable EIGRP on all routers as illustrated in the topology. Verify your EIGRP configuration.
Task 3
Configure automatic IPv4-compatible tunnels on R1 and R4. The tunnel source interface should be configured as the WAN interface. Verify the configuration using the appropriate commands.
Task 4
Enable MP-BGP between R1 and R4 using AS 254 and advertise the LAN subnets connected to R1 and R4. Use the WAN interface addresses to complete the 128-bit IPv6 addresses that will be used for peering. Verify that you can ping LAN-to-LAN between R1 and R4.
Lab Validation
Task 1
Please refer to previous labs for basic IPv4, IPv6 addressing and hostname configuration. This will not be included in this section to avoid being redundant.
Task 2
| R1(config)#router eigrp 254 R1(config-router)#no auto-summary R1(config-router)#network 10.0.0.0 R1(config-router)#exit |
| R2(config)#router eigrp 254 R2(config-router)#no auto-summary R2(config-router)#network 10.0.0.0 R2(config-router)#exit |
| R3(config)#router eigrp 254 R3(config-router)#no auto-summary R3(config-router)#network 10.0.0.0 R3(config-router)#exit |
| R4(config)#router eigrp 254 R4(config-router)#no auto-summary R4(config-router)#network 10.0.0.0 R4(config-router)#exit |
Verify your EIGRP configuration using the show ip eigrp neighbors command:
| R1#show ip eigrp neighbors IP-EIGRP neighbors for process 254 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 0 10.0.0.2 Se0/0 12 00:01:31 5 200 0 8 |
| R2#show ip eigrp neighbors IP-EIGRP neighbors for process 254 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 1 10.0.0.10 Se0/1 10 00:01:28 9 300 0 3 0 10.0.0.1 Se0/0 12 00:01:34 2 200 0 3 |
| R3#show ip eigrp neighbors IP-EIGRP neighbors for process 254 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 1 10.0.0.14 Se1/2 13 00:01:26 12 1140 0 3 0 10.0.0.9 Se1/1 12 00:01:31 12 1140 0 7 |
| R4#show ip eigrp neighbors IP-EIGRP neighbors for process 254 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 0 10.0.0.13 Se0/0 14 00:01:29 14 200 0 7 |
Task 3
Automatic IPv4-compatible tunnels use a tunnel mode of ipv6ip auto-tunnel. The tunnels are configured using only a source interface. The destination is automatically determined based on configured static routes or received MP-BGP updates. This task is completed as follows:
| R1(config)#interface tunnel 0 R1(config-if)#tunnel source serial 0/0 R1(config-if)#tunnel mode ipv6ip auto-tunnel R1(config-if)#exit |
| R4(config)#interface tunnel 0 R4(config-if)#tunnel source serial 0/0 R4(config-if)#tunnel mode ipv6ip auto-tunnel R4(config-if)#exit |
Verify your Tunnel status using the show interfaces command:
| R1#show interfaces tunnel 0 Tunnel0 is up, line protocol is up Hardware is Tunnel MTU 1514 bytes, BW 9 Kbit/sec, DLY 500000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation TUNNEL, loopback not set Keepalive not set Tunnel source 10.0.0.1 (Serial0/0), destination UNKNOWN Tunnel protocol/transport IPv6 auto-tunnel Fast tunneling enabled |
Task 4
Automatic IPv4-compatible tunnels enable IPv6 hosts to automatically enable tunnels to other IPv6 hosts across an IPv4 network infrastructure. Unlike 6to4 tunneling, automatic IPv4-compatible tunneling does use the IPv4-compatible IPv6 addresses. Automatic IPv4-compatible tunnels use the IPv6 prefix ::/96. To complete the 128-bit IPv6 address, the low order 32-bits are derived from the IPv4 address. These low-order 32-bits of the source and destination IPv6 addresses represent the source and destination IPv4 addresses of the tunnel endpoints. This task is completed as follows:
| R1(config)#router bgp 254 R1(config-router)#bgp router-id 1.1.1.1 R1(config-router)#no bgp default ipv4-unicast R1(config-router)#neighbor ::10.0.0.14 remote-as 254 R1(config-router)#address-family ipv6 unicast R1(config-router-af)#neighbor ::10.0.0.14 activate R1(config-router-af)#neighbor ::10.0.0.14 next-hop-self R1(config-router-af)#network 3ffe:abcd:1111:1::/64 R1(config-router-af)#exit R1(config-router)#exit |
| R4(config)#router bgp 254 R4(config-router)#bgp router-id 4.4.4.4 R4(config-router)#no bgp default ipv4-unicast R4(config-router)#neighbor ::10.0.0.1 remote-as 254 R4(config-router)#address-family ipv6 unicast R4(config-router-af)#neighbor ::10.0.0.1 activate R4(config-router-af)#neighbor ::10.0.0.1 next-hop-self R4(config-router-af)#network 3ffe:abcd:1111:4::/64 R4(config-router-af)#exit R4(config-router)#exit |
Verify MP-BGP configuration using the show bgp ipv6 unicast summary command:
| R1#show bgp ipv6 unicast summary BGP router identifier 1.1.1.1, local AS number 254 BGP table version is 3, main routing table version 3 2 network entries using 298 bytes of memory 2 path entries using 152 bytes of memory 3/2 BGP path/bestpath attribute entries using 372 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 0 BGP filter-list cache entries using 0 bytes of memory BGP using 822 total bytes of memory BGP activity 3/1 prefixes, 3/1 paths, scan interval 60 secs Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd |
| R4#show bgp ipv6 unicast summary BGP router identifier 4.4.4.4, local AS number 254 BGP table version is 3, main routing table version 3 2 network entries using 298 bytes of memory 2 path entries using 152 bytes of memory 3/2 BGP path/bestpath attribute entries using 372 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 0 BGP filter-list cache entries using 0 bytes of memory BGP using 822 total bytes of memory BGP activity 3/1 prefixes, 3/1 paths, scan interval 60 secs Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd |
Next, verify the BGP RIB entries using the show bgp ipv6 unicast command:
| R1#show bgp ipv6 unicast BGP table version is 3, local router ID is 1.1.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i – internal, r RIB-failure, S Stale Origin codes: i – IGP, e – EGP, ? – incomplete Network Next Hop Metric LocPrf Weight Path |
| R4#show bgp ipv6 unicast BGP table version is 3, local router ID is 4.4.4.4 Status codes: s suppressed, d damped, h history, * valid, > best, i – internal, r RIB-failure, S Stale Origin codes: i – IGP, e – EGP, ? – incomplete Network Next Hop Metric LocPrf Weight Path |
Finally, complete the task by pinging LAN-to-LAN between R1 and R4:
| R1#ping 3FFE:ABCD:1111:4::4 source fastethernet 0/0 repeat 10 size 1500
Type escape sequence to abort. |
| R4#ping 3FFE:ABCD:1111:1::1 source fastethernet 0/0 repeat 10 size 1500
Type escape sequence to abort. |
Final Router Configurations
R1
|
R1#term len 0 Current configuration : 1298 bytes R1# |
R2
|
R2#term len 0 Current configuration : 847 bytes R2# |
R3
|
R3#term len 0 Current configuration : 1188 bytes R3# |
R4
|
R4#term len 0 Current configuration : 1276 bytes R4# |