OSPFv2 and OSPFv3 verification of area 0.0.0.250.

This is a totally stubby area and R11 is injecting a default route into it.



scenario


Since hardly anything is happening here, all verification can be done with 1 command:

 
play@MX80:R8> show route protocol ospf

inet.0: 13 destinations, 14 routes (13 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0          *[OSPF/10] 1w1d 08:50:05, metric 21
                    > to 18.0.0.2 via xe-0/0/3.30
1.1.1.8/32          [OSPF/10] 1w1d 11:18:47, metric 0
                    > via lo0.8
224.0.0.5/32       *[OSPF/10] 1w1d 11:18:52, metric 1
                      MultiRecv

inet6.0: 12 destinations, 14 routes (12 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

::/0               *[OSPF3/10] 6d 05:10:22, metric 21
                    > to fe80::8ae0:f300:1e55:f8f7 via xe-0/0/3.30
2001::8/128         [OSPF3/10] 6d 05:08:32, metric 0
                    > via lo0.8
2001:18:1:0:8ae0:f300:1e55:f8f7/128
                   *[OSPF3/10] 6d 02:34:24, metric 1
                    > to fe80::8ae0:f300:1e55:f8f7 via xe-0/0/3.30
ff02::5/128        *[OSPF3/10] 6d 05:11:37, metric 1
                      MultiRecv
                

By issuing this one command, we can see that we are only receiving a default route via OSPFv2 and OSPFv3.

17-10-2014