We have R1, R2 and R3 as routers within an autonomous system, R4 a random (IPv4-only) Internet router and R5 as another (IPv6-only, this time) random Internet router. My intent was to set up BGP peering between R1, R4 and R5, and to have R1, R2 and R3 share routes via OSPF. Sounds easy enough, right?
Hahaha...no.
In a previous lab, we set up OSPFv3 (OSPF for IPv6) on Cisco 3640 routers, so I used those instruction to (try to) set up OSPFv3 on the 7200 routers:
R1(config)#int gig0/0
R1(config-if)#ipv6 ospf 42 area 0.0.0.0
^
% Invalid input detected at '^' marker.
R1(config-if)#ipv6 o?
% Unrecognized command
R1(config-if)#ipv6 ?
IPv6 interface subcommands:
address Configure IPv6 address on interface
authentication authentication subcommands
...
multicast multicast
nat Enable IPv6 NAT on interface
nd IPv6 interface Neighbor Discovery subcommands
next-hop-self Configures IP-EIGRP next-hop-self
policy Enable IPv6 policy routing
redirects Enable sending of ICMP Redirect messages
rip Configure RIP routing protocol
...
Okay...is OSPFv3 not supported on this router? As it turns out, I think it actually is, but I'll save that for another lab.
Edit: no, it's not. I mean, it is, but it isn't. The "hooks" are there to configure OSPFv3 using "ipv6 ospf <process ID>" in global configuration, but you have to have an Advanced IP Services image to run it. The SP Services image I am running isn't licensed for it, because after all, what service provider would run OSPF on their network (answer: every one I've ever worked at), grrr...
For now, I decided to try to set up EIGRP for IPv6 since, 1) it *is* supported on the 7200, and 2) it did not seem to be supported on the 3640's:
R1(config)#int gig0/0
R1(config-if)#ipv6 router eigrp 10
R1(config-rtr)#int gig1/0
R1(config-if)#ipv6 router eigrp 10
R1(config-rtr)#exit
R1(config)#exit
R1#sho run int gig0/0
Building configuration...
Current configuration : 201 bytes
!
interface GigabitEthernet0/0
ip address 66.223.227.5 255.255.255.252
duplex full
speed 1000
media-type gbic
negotiation auto
ipv6 address 2001:C0:FFEE:2::1/126
ipv6 enable
ipv6 eigrp 10
end
R1#sho ipv6 route
IPv6 Routing Table - Default - 8 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
M - MIPv6, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
C 2001:C0:FFEE::/126 [0/0]
via GigabitEthernet1/0, directly connected
L 2001:C0:FFEE::1/128 [0/0]
via GigabitEthernet1/0, receive
C 2001:C0:FFEE:2::/126 [0/0]
via GigabitEthernet0/0, directly connected
L 2001:C0:FFEE:2::1/128 [0/0]
via GigabitEthernet0/0, receive
LC 2001:C0:FFEE:254::1/128 [0/0]
via Loopback0, receive
C 2016:FA:1::/64 [0/0]
via FastEthernet6/0.20, directly connected
L 2016:FA:1::1/128 [0/0]
via FastEthernet6/0.20, receive
L FF00::/8 [0/0]
via Null0, receive
R1#
Weird...why are none of my EIGRP routes showing up? I could ping across the interfaces and my IPv4 routing protocols were working as expected, but I could not get EIGRP in IPv6 to form neighbor adjacencies. What gives?
I started troubleshooting EIGRP using essentially the same toolkit I would use for IPv4...:
R1#sho ipv6 eigrp 10 neigh
IPv6-EIGRP neighbors for process 10
% EIGRP 10 is in SHUTDOWN
R1#sho ipv6 eigrp 10 int
IPv6-EIGRP interfaces for process 10
% EIGRP 10 is in SHUTDOWN
R1#
"EIGRP...is in SHUTDOWN?" I'm not familiar with that error message. WWGS ("What Would Google Say")? I quickly found a couple of tutorials on-line which showed that setting up EIGRP in IPv6 on a 7200 is a little different than setting OSPFv3 on a 3640 (go figure). Whereas OSPFv3 on a 3640 is entirely configured on the interface, EIGRP for IPv6 is a mix of interface-level commands and global config commands:
R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#ipv6 router eigrp 10
R1(config-rtr)#router-id 10.254.254.1
R1(config-rtr)#redistribute connected
R1(config-rtr)#passive-int default
R1(config-rtr)#no passive-int gig0/0
R1(config-rtr)#no passive-int gig1/0
R1(config-rtr)#no shut
02:35:27: %DUAL-5-NBRCHANGE: IPv6-EIGRP(0) 10: Neighbor FE80::C802:7FF:FE00:70 (GigabitEthernet1/0) is up: new adjacency
R1(config-rtr)#
02:35:38: %DUAL-5-NBRCHANGE: IPv6-EIGRP(0) 10: Neighbor FE80::C801:6FF:FEF0:70 (GigabitEthernet0/0) is up: new adjacency
R1(config-rtr)#exit
R1(config)#exit
After making eseentially the same changes on R2 and R3 (the interface names were different, but...), I saw my routes as expected:
R1#sho ipv6 route
IPv6 Routing Table - Default - 12 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
M - MIPv6, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
C 2001:C0:FFEE::/126 [0/0]
via GigabitEthernet1/0, directly connected
L 2001:C0:FFEE::1/128 [0/0]
via GigabitEthernet1/0, receive
C 2001:C0:FFEE:2::/126 [0/0]
via GigabitEthernet0/0, directly connected
L 2001:C0:FFEE:2::1/128 [0/0]
via GigabitEthernet0/0, receive
D 2001:C0:FFEE:3::/64 [90/28416]
via FE80::C802:7FF:FE00:70, GigabitEthernet1/0
LC 2001:C0:FFEE:254::1/128 [0/0]
via Loopback0, receive
D 2001:C0:FFEE:254::2/128 [90/130816]
via FE80::C801:6FF:FEF0:70, GigabitEthernet0/0
D 2001:C0:FFEE:254::3/128 [90/130816]
via FE80::C802:7FF:FE00:70, GigabitEthernet1/0
D 2001:C0:FFEE:2222::/64 [90/28416]
via FE80::C801:6FF:FEF0:70, GigabitEthernet0/0
C 2016:FA:1::/64 [0/0]
via FastEthernet6/0.20, directly connected
L 2016:FA:1::1/128 [0/0]
via FastEthernet6/0.20, receive
L FF00::/8 [0/0]
via Null0, receive
R1#
Well that was more cumbersome than it should have been, but <shrug>. At least we've got EIGRP working now. BGP via IPv4 is nothing new, so I won't waste a lot of time discussing the BGP configuration for R1-R4. However, the IPv6 configuration between R1 and R5 had me swearing at Cisco:
R1(config)#router bgp 65511
R1(config-router)# neighbor 2016:FA:1::5 remote-as 65515
R1(config-router)# address-family ipv6
R1(config-router-af)# network 2001:C0:FFEE:254:0:0:0:1/128
R1(config-router-af)# network 2001:C0:FFEE:254:0:0:0:2/128
R1(config-router-af)# network 2001:C0:FFEE:254:0:0:0:3/128
R1(config-router-af)# network 2001:C0:FFEE:2:0:0:0:0/126
R1(config-router-af)# network 2001:C0:FFEE:0:0:0:0:0/126
R1(config-router-af)# network 2001:C0:FFEE:2222:0:0:0:0/64
R1(config-router-af)# network 2001:C0:FFEE:3:0:0:0:0/64
R1(config-router-af)# neighbor 2016:FA:1::5 activate
% BGP context not been initialized properly.
R1(config-router-af)# exit
R1(config-router)#exit
R1(config)#exit
R1#sho bgp ipv6 unicast neighbors
R1#sho run | begin router bgp
router bgp 65511
bgp router-id 10.254.254.1
bgp log-neighbor-changes
neighbor 2016:FA:1::5 remote-as 65515
neighbor 209.193.4.4 remote-as 65514
!
address-family ipv4
neighbor 209.193.4.4 activate
no auto-summary
no synchronization
network 10.254.254.1 mask 255.255.255.255
network 10.254.254.2 mask 255.255.255.255
network 10.254.254.3 mask 255.255.255.255
network 66.223.224.0 mask 255.255.255.224
network 66.223.224.32 mask 255.255.255.224
network 66.223.227.0 mask 255.255.255.252
network 66.223.227.4 mask 255.255.255.252
network 209.193.4.0
exit-address-family
!
ip forward-protocol nd
...
Wait, where's my "address-family ipv6" entries, and what's with that "BGP context has not been initialized properly" error message? I went back to the Great Oracle of Google, where I found this little tidbit of information:
Q. Error message: "% BGP context not been initialized properly." when Configuring neighbor under address-family IPv6
A. The issue is with the feature set. If the feature set is SP services, the following services are not supported.
- IPv6 Routing: Multiprotocol BGP Extensions for IPv6
- IPv6 Routing: Multiprotocol BGP Link-local Address Peering
To use these features,change the feature set to Advanced Enterprise Services.
Okay, let's check the code version on my routers:
R1#sho ver
Cisco IOS Software, 7200 Software (C7200-SPSERVICESK9-M), Version 12.4(24)T4, RELEASE SOFTWARE (fc2)
Well, <expletive deleted>! Since I don't have an Advanced IP Services image laying around, that pretty much kills the BGP portion of this lab for now.
I went ahead and removed the BGP portion and played with EIGRP across the network, but I'm slightly miffed by the fact that I couldn't do any testing with BGP or OSPF under IPv6, since IPv6 is now a part of certification testing. With adoption of IPv6 "in the wild" still lagging, it would be nice to be able to mock such networks up in a lab without spending a fortune in hardware and software licensing.
No comments:
Post a Comment