ospfv3_multiarea_topology

So through begging all over on Cisco support community and other tech forums, someone had pointed out that my running config appears to be missing the frame map statements, and I just facepalmed so hard I might have just smacked myself.

Once more, if you use templates that setup “base configs” like ip addressing and no shutting interfaces to get you started, remember when not using that template you must configure the whole ball of wax.

So I am not really sure what Frame Map statements look like in IPv6, lets take a look:

R1(config-if)#frame map ipv6 ?
  X:X:X:X::X  Protocol specific address

R1(config-if)#frame map ipv6 2001::2 ?
  <16-1007>  DLCI
  vc-bundle  vc-bundle

R1(config-if)#frame map ipv6 2001::2 122 ?
  broadcast            Broadcasts should be forwarded to this address
  cisco                Use CISCO Encapsulation
  ietf                 Use RFC1490/RFC2427 Encapsulation
  payload-compression  Use payload compression
  <cr>

R1(config-if)#frame map ipv6 2001::2 122
R1(config-if)#frame map ipv6 2001::3 123
R1(config-if)#
ASR>2
[Resuming connection 2 to r2 … ]

R2(config)#int s0/0
R2(config-if)#frame map ipv6 2001::1 221
R2(config-if)#frame map ipv6 2001::3 221
R2(config-if)#
ASR>3
[Resuming connection 3 to r3 … ]

R3(config)#
R3(config)#int s0/2
R3(config-if)#frame map ipv6 2001::1 321
R3(config-if)#frame map ipv6 2001::3 321
R3(config-if)#
ASR>1
[Resuming connection 1 to r1 … ]

R1(config-if)#do sh ip ospf nei

R1(config-if)#

I was taught that IPv6 does not use broadcasts, but I am wondering if in this case it needs the same configuration as regular old frame-relay. So after half my cinammon coffee cake and double shot mocha from Caribou (the best study tool ever), my adjacencies on R1 aren’t even trying to form.

So, I am going to remove the old statements, and throw broadcast on there like an IPv4 deployment to see what happens. It’s not like we can break it anymore, unless I throw these damn routers out the second story window, and do a jumping double fist slam down onto the Hub for being a stubborn pile 🙂

Anyways, lets put on some broadcast statements with frame relay to see what happens:

R1(config)#do clear ipv6 ospf proc
Reset ALL OSPF processes? [no]: yes
R1(config)#
*Mar  1 21:51:23.101: %OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.0 on Serial0/0 from ATTEMPT to DOWN, Neighbor Down: Interface down or detached
*Mar  1 21:51:23.101: %OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.0 on Serial0/0 from ATTEMPT to DOWN, Neighbor Down: Interface down or detached
R1(config)#do sh frame pvc

PVC Statistics for interface Serial0/0 (Frame Relay DTE)

              Active     Inactive      Deleted       Static
  Local          2            0            0            0
  Switched       0            0            0            0
  Unused         0            0            0            0

DLCI = 122, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0

  input pkts 0             output pkts 2            in bytes 0
  out bytes 160            dropped pkts 0           in pkts dropped 0
  out pkts dropped 0                out bytes dropped 0
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0
  out BECN pkts 0          in DE pkts 0             out DE pkts 0
  out bcast pkts 2         out bcast bytes 160
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 00:04:13, last time pvc status changed 00:04:13
 –More–
*Mar  1 21:53:23.102: %OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.0 on Serial0/0 from ATTEMPT to DOWN, Neighbor Down: Dead timer expired
*Mar  1 21:53:23.102: %OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.0 on Serial0/0 from ATTEMPT to DOWN, Neighbor Down: Dead timer expired

R1(config)#do show frame map
Serial0/0 (up): ipv6 2001::2 dlci 122(0x7A,0x1CA0), static,
              broadcast,
              CISCO, status defined, active
Serial0/0 (up): ipv6 2001::3 dlci 123(0x7B,0x1CB0), static,
              broadcast,
              CISCO, status defined, active
R1(config)#
R1(config)#do sh ipv6 ospf nei

Neighbor ID     Pri   State           Dead Time   Interface ID    Interface
N/A               0   ATTEMPT/DROTHER    –        0               Serial0/0
N/A               0   ATTEMPT/DROTHER    –        0               Serial0/0
R1(config)#

Ok, pardon my language, but this is really starting to piss me off why on Earth this not working. I did not trying clearing the OSPF proc before adding the broadcast statements, and IPv6 is supposed to be no broadcasts aloud club, so I’ll remove and replace once more as I originally did and clear all ospf proc on hub and spokes.

If this does not work, I am going to copy my running configs on all other routers, and R1 / R2 / R3 are getting bare bones configs with an IPv6 setup once more to see what the fudge is going on. This is actually starting to be more of a pain in the ass than a fun challenge to overcome, because I have barely learned IPv6, so I have no idea if the interfaces in my training vids are pre-configured in some special way. Though the fact that those PVC’s show broadcast, and that isn’t supposed to be how IPv6 gets down, I am really hoping this fixes the issue.

So here goes my last attempt before I call it a night, I was really hoping that would work, the fact it hasn’t yet is getting me quite irritated with the lack of knowledge in this particular area around the internet in general:

R1#clear ipv6 ospf proc
Reset ALL OSPF processes? [no]:
*Mar  1 22:10:25.542: %SYS-5-CONFIG_I: Configured from console by console
yes
R1#
*Mar  1 22:10:28.335: %OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.0 on Serial0/0 from ATTEMPT to DOWN, Neighbor Down: Interface down or detached
*Mar  1 22:10:28.335: %OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.0 on Serial0/0 from ATTEMPT to DOWN, Neighbor Down: Interface down or detached
R1#wr
Building configuration…
[OK]
R1#
*Mar  1 22:12:28.335: %OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.0 on Serial0/0 from ATTEMPT to DOWN, Neighbor Down: Dead timer expired
*Mar  1 22:12:28.335: %OSPFv3-5-ADJCHG: Process 1, Nbr 0.0.0.0 on Serial0/0 from ATTEMPT to DOWN, Neighbor Down: Dead timer expired
R1#

No, no, no no no no NO NO NO!!! WTF???

Ok, I am going to “wr er” R1 / R2 / R3, and on the next lab I will only be configuring their serial interfaces as Area 0 in an OSPFv3 domain.

I feel smitten, but I just do not have the brain power to dig through forums and documentation, cause there is not a whole lot out there regarding ospfv3 and nbmas.