Solved :
It's really a bug in IOS XE 03.07.02.S.
Routers don't send hello OSPFv3 after a reboot. Confirmed by packet capture on C6509 catalyst !
The issue is not present in IOS XE 03.08.00.S
A TAC case is opened.
Hi,
I'm trying to install an OSPFv3 area between two ASR1001 gateways. Routers are running IOS XE Version: 03.07.02.S.
Each router is connected trough a Port-Channel (2*1G) on a C6509E chassis.
A single vlan is configured to create the interconnection for both IPv4 and IPv6 peering between routers.
Routers can ping each other on their IPv4 adress, global unicast IPv6 adress and link local IPv6 adress on this 801.Q interface.
The OSPFv3 process is configured as it (only greater metric are applied on defaut originate from second router):
router ospfv3 1
router-id x.x.x.x
area 1 authentication ipsec spi 256 md5 7 toto
!
address-family ipv4 unicast
redistribute connected
redistribute bgp 12345
passive-interface default
no passive-interface Port-channel1.11
default-information originate metric
distribute-list prefix ospf-filter-v4-out out
distribute-list prefix ospf-filter-v4-in in
exit-address-family
!
address-family ipv6 unicast
passive-interface default
no passive-interface Port-channel1.11
distribute-list prefix-list ospf-filter-v6-in in
distribute-list prefix-list ospf-filter-v6-out out connected
distribute-list prefix-list ospf-filter-v6-out out static
default-information originate metric
redistribute connected
redistribute bgp 12345
exit-address-family
Interconnection interface is configured as it (only specific ospf3 priority is applied on second router) :
interface Port-channel1.11
encapsulation dot1Q 11
ip address X.X.X.X 255.255.255.248
no ip redirects
no ip proxy-arp
ip flow ingress
ipv6 address X:X:X:X::X/64
ipv6 nd ra suppress
no ipv6 redirects
ospfv3 1 ipv4 area 1
ospfv3 1 ipv6 area 1
By this way, routers don't see each other on OSPFv3 (no neighbor).
If I suppress the IPv6 OSPFv3 part from the interface, the adjacence is immediatly running through IPv4.
In fact, multicast hello OPSFv3 are not propagated on other router :
1) Each router is permanently sending hello OSPFv3 (first trafic to establish OSPFv3 adj) :
rt-01#
000167: *Feb 8 20:06:10.656: OSPFv3-1-IPv4 HELLO Po1.11: Send hello to FF02::5 area 1 from FE80::C664:13FF:FE9F:54C0 interface ID 16
000168: *Feb 8 20:06:11.634: OSPFv3-1-IPv6 HELLO Po1.11: Send hello to FF02::5 area 1 from FE80::C664:13FF:FE9F:54C0 interface ID 16
rt-02#
000120: *Feb 8 20:06:10.205: OSPFv3-1-IPv4 HELLO Po1.11: Send hello to FF02::5 area 1 from FE80::C664:13FF:FE9F:71C0 interface ID 16
000121: *Feb 8 20:06:10.646: OSPFv3-1-IPv6 HELLO Po1.11: Send hello to FF02::5 area 1 from FE80::C664:13FF:FE9F:71C0 interface ID 16
2) No packet arrive to destination. We can only see egress packets.
rt-01#
000198: *Feb 8 20:08:35.108: IPV6: source FE80::C664:13FF:FE9F:54C0 (local)
000199: *Feb 8 20:08:35.108: dest FF02::5 (Port-channel1.11)
000200: *Feb 8 20:08:35.108: traffic class 192, flow 0x0, len 76+0, prot 89, hops 1, originating
000201: *Feb 8 20:08:35.108: IPv6-Fwd: L3 injection feature enabled: skipping output feature 'Virtual fragment reassembly in Egress'
000202: *Feb 8 20:08:35.108: IPv6-Fwd: L3 injection feature enabled: skipping pak_encap
rt-02#
000161: *Feb 8 20:08:32.365: IPV6: source FE80::C664:13FF:FE9F:71C0 (local)
000162: *Feb 8 20:08:32.366: dest FF02::5 (Port-channel1.802)
000163: *Feb 8 20:08:32.366: traffic class 192, flow 0x0, len 76+0, prot 89, hops 1, originating
000164: *Feb 8 20:08:32.366: IPv6-Fwd: L3 injection feature enabled: skipping output feature 'Virtual fragment reassembly in Egress'
000165: *Feb 8 20:08:32.366: IPv6-Fwd: L3 injection feature enabled: skipping pak_encap
3) If I try a ping IPv6 on the multicast IPv6 address, the router on the other side respond :
rt-02#ping FF02::5
Output Interface: Port-channel1.11
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FF02::5, timeout is 2 seconds:
Packet sent with a source address of FE80::C664:13FF:FE9F:71C0%Port-channel1.11
Reply to request 0 received from FE80::C664:13FF:FE9F:54C0, 1 ms
Reply to request 1 received from FE80::C664:13FF:FE9F:54C0, 1 ms
Reply to request 2 received from FE80::C664:13FF:FE9F:54C0, 1 ms
Reply to request 3 received from FE80::C664:13FF:FE9F:54C0, 1 ms
Reply to request 4 received from FE80::C664:13FF:FE9F:54C0, 1 ms
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
5 multicast replies and 0 errors.
and we can see both ingress and egress directed trafic on the other side :
rt-01#
000223: *Feb 8 20:09:42.176: IPV6: source FE80::C664:13FF:FE9F:71C0 (Port-channel1.11)
000224: *Feb 8 20:09:42.176: dest FF02::5
000225: *Feb 8 20:09:42.176: traffic class 0, flow 0x0, len 100+18, prot 58, hops 64, forward to ulp
000226: *Feb 8 20:09:42.176: IPv6-Sas: SAS picked source FE80::C664:13FF:FE9F:54C0 for FE80::C664:13FF:FE9F:71C0 (Port-channel1.11)
000227: *Feb 8 20:09:42.176: IPv6-Fwd: Destination lookup for FE80::C664:13FF:FE9F:71C0 : i/f=Port-channel1.11, nexthop=FE80::C664:13FF:FE9F:71C0
000228: *Feb 8 20:09:42.176: IPV6: source FE80::C664:13FF:FE9F:54C0 (local)
000229: *Feb 8 20:09:42.176: dest FE80::C664:13FF:FE9F:71C0 (Port-channel1.11)
000230: *Feb 8 20:09:42.176: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating
000231: *Feb 8 20:09:42.176: IPv6-Fwd: Created tmp mtu cache entry for FE80::C664:13FF:FE9F:54C0 FE80::C664:13FF:FE9F:71C0 12000010
000232: *Feb 8 20:09:42.176: IPv6-Fwd: L3 injection feature enabled: skipping output feature 'Virtual fragment reassembly in Egress'
000233: *Feb 8 20:09:42.176: IPv6-Fwd: L3 injection feature enabled: skipping pak_encap
Other information, I tried to configure two separate OSPFv3 process using two different area number :
- one process - one area for IPv4
- one process - one area for IPv6
=> problem was exactly the same. After reload, no OSPFv3 adjacence is set.
=> the only way to set up adjacence is to suppress and re-enter the command "ospfv3 1 ipv6 area 1" on the interface Po1.1. on each router.
Solved :
It's really a bug in IOS XE 03.07.02.S.
Routers don't send hello OSPFv3 after a reboot. Confirmed by packet capture on C6509 catalyst !
The issue is not present in IOS XE 03.08.00.S
A TAC case is opened.
Best regards
Jérôme
