OSPFv2 and OSPFv3 verification of area 0.0.200.1.

This is an NSSA area. R9 is redistributing several static routes into the area and R12 is summarizing these routes into area 0.0.0.0. R12 is also configured to inject a default route into the area and to withhold summary routes.

First, we'll check the redistribution of the static routes and the summarization of these routes into area 0.0.0.0.

After that, we'll look at the default route generated by R12 and we'll see how many LSA's there are in the area's LSDB.



scenario


The following command will verify the area type, the router type and whether or not the router has any neighbors in the area:

 
play@MX80:R9> show ospf overview
Instance: master
  Router ID: 1.1.1.9
  Route table index: 21
  AS boundary router, NSSA router
  LSA refresh time: 50 minutes
  Area: 0.0.200.1
    Stub type: Stub NSSA
    Authentication Type: None
    Area border routers: 1, AS boundary routers: 1
    Neighbors
      Up (in full state): 1
  Topology: default (ID 0)
    Prefix export count: 4
    Full SPF runs: 58
    SPF delay: 0.200000 sec, SPF holddown: 5 sec, SPF rapid runs: 3
    Backup SPF: Not Needed

play@MX80:R9> show ospf3 overview
Instance: master
  Router ID: 1.1.1.9
  Route table index: 21
  AS boundary router, NSSA router
  LSA refresh time: 50 minutes
  Area: 0.0.200.1
    Stub type: Stub NSSA
    Area border routers: 1, AS boundary routers: 1
    Neighbors
      Up (in full state): 1
  Topology: default (ID 0)
    Prefix export count: 4
    Full SPF runs: 41
    SPF delay: 0.200000 sec, SPF holddown: 5 sec, SPF rapid runs: 3
    Backup SPF: Not Needed
                

This output tells us R9 is functioning as an ASBR in an NSSA area 0.0.200.1 for both OSPFv2 and OSPFv3. It also tells us that R9 has 1 neighbor in this area.

To see if this 1 neighbor is in fact R12, we can issue the following command;

 
play@MX80:R9> show ospf neighbor
Address          Interface              State     ID               Pri  Dead
18.0.0.6         xe-0/0/3.31            Full      1.1.1.12         128    39

play@MX80:R9> show ospf3 neighbor
ID               Interface              State     Pri   Dead
1.1.1.12         xe-0/0/3.31            Full      128     39
  Neighbor-address fe80::8ae0:f300:1f55:f8f7
                

Let's if R9 is adding NSSA LSAs to the LSDB in both OSPFv2 and OSPFv3;

 
play@MX80:R9> show ospf database advertising-router self nssa detail

    OSPF database, Area 0.0.200.1
 Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
NSSA    *55.0.0.0         1.1.1.9          0x800000ef  1459  0x28 0x3339  36
  mask 255.255.255.0
  Topology default (ID 0)
    Type: 2, Metric: 0, Fwd addr: 1.1.1.9, Tag: 0.0.0.0
NSSA    *55.0.1.0         1.1.1.9          0x800000ef   259  0x28 0x2843  36
  mask 255.255.255.0
  Topology default (ID 0)
    Type: 2, Metric: 0, Fwd addr: 1.1.1.9, Tag: 0.0.0.0
NSSA    *55.0.2.0         1.1.1.9          0x800000ee  2659  0x28 0x1f4c  36
  mask 255.255.255.0
  Topology default (ID 0)
    Type: 2, Metric: 0, Fwd addr: 1.1.1.9, Tag: 0.0.0.0
NSSA    *55.0.3.0         1.1.1.9          0x80000001    95  0x28 0xef68  36
  mask 255.255.255.0
  Topology default (ID 0)
    Type: 2, Metric: 0, Fwd addr: 1.1.1.9, Tag: 0.0.0.0
NSSA    *56.0.0.0         1.1.1.9          0x800000ef  2059  0x28 0x2645  36
  mask 255.0.0.0
  Topology default (ID 0)
    Type: 2, Metric: 0, Fwd addr: 1.1.1.9, Tag: 0.0.0.0

play@MX80:R9> show ospf3 database advertising-router self nssa detail

    OSPF3 database, Area 0.0.200.1
 Type       ID               Adv Rtr           Seq         Age  Cksum  Len
NSSA       *0.0.0.1          1.1.1.9          0x800000b5   318  0xf3b9  36
  Prefix 2001:55:1::/64
  Prefix-options 0x8, Metric 0, Type 2,
NSSA       *0.0.0.2          1.1.1.9          0x800000b4  2943  0xfbb0  36
  Prefix 2001:55:2::/64
  Prefix-options 0x8, Metric 0, Type 2,
NSSA       *0.0.0.3          1.1.1.9          0x800000b4  2568  0x2a8   36
  Prefix 2001:55:3::/64
  Prefix-options 0x8, Metric 0, Type 2,
NSSA       *0.0.0.4          1.1.1.9          0x800000b4  1818  0xc7e4  36
  Prefix 2001:55::/64
  Prefix-options 0x8, Metric 0, Type 2,
NSSA       *0.0.0.5          1.1.1.9          0x80000001   218  0xb4bb  36
  Prefix 2001:56::/46
  Prefix-options 0x8, Metric 0, Type 2,
                

That, quite lengthy, output shows the additions to the LSDB in both OSPFv2 and OSPFv3. All the static routes were converted into an NSSA-LSAs.

To see if the summarization is working, we have to move over to R12. On this ABR, the NSSA-LSAs will be turned into External-LSAs.

 
play@MX480-TEST:R12> show ospf database advertising-router self external extensive
    OSPF AS SCOPE link state database
 Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
Extern  *55.0.0.0         1.1.1.12         0x800000ef  1034  0x22 0xfe7d  36
  mask 255.255.0.0
  Topology default (ID 0)
    Type: 2, Metric: 1, Fwd addr: 0.0.0.0, Tag: 0.0.0.0
  Gen timer 00:32:19
  Aging timer 00:42:46
  Installed 00:17:14 ago, expires in 00:42:46, sent 00:17:14 ago
  Last changed 00:17:14 ago, Change count: 3, Ours
Extern  *56.0.0.0         1.1.1.12         0x800000ef   203  0x22 0x8ae5  36
  mask 255.0.0.0
  Topology default (ID 0)
    Type: 2, Metric: 0, Fwd addr: 1.1.1.9, Tag: 0.0.0.0
  Gen timer 00:46:36
  Aging timer 00:56:36
  Installed 00:03:23 ago, expires in 00:56:37, sent 00:03:21 ago
  Last changed 1w1d 05:32:33 ago, Change count: 1, Ours

play@MX480-TEST:R12> show ospf3 database advertising-router self external extensive
    OSPF3 AS SCOPE link state database
 Type       ID               Adv Rtr           Seq         Age  Cksum  Len
Extern     *0.0.0.1          1.1.1.12         0x80000021   421  0x7cbe  36
  Prefix 2001:55::/46
  Prefix-options 0x0, Metric 1, Type 2,
  Gen timer 00:42:58
  Aging timer 00:52:58
  Installed 00:07:01 ago, expires in 00:52:59, sent 00:06:59 ago
  Last changed 1d 02:38:03 ago, Change count: 1, Ours
Extern     *0.0.0.2          1.1.1.12         0x80000001   778  0xba9f  36
  Prefix 2001:56::/46
  Prefix-options 0x0, Metric 0, Type 2,
  Gen timer 00:37:01
  Aging timer 00:47:01
  Installed 00:12:58 ago, expires in 00:47:02, sent 00:12:58 ago
  Last changed 00:12:58 ago, Change count: 1, Ours
                

Here we can see that for both OSPFv2 and OSPFv3, only two prefixes are announced as External-LSAs. 1 NSSA-LSAs prefix is unaltered, and four other prefixes were summarized into 1 prefix.

The other things that needed verification were the amount of LSAs send into the NSSA area by R12 and whether or not a default route was being generated.

 
play@MX480-TEST:R12> show ospf database advertising-router self area 0.0.200.1 detail netsummary

    OSPF database, Area 0.0.200.1
 Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
Summary *0.0.0.0          1.1.1.12         0x800000ef  2470  0x20 0x32fa  28
  mask 0.0.0.0
  Topology default (ID 0) -> Metric: 20

play@MX480-TEST:R12> show ospf3 database advertising-router self area 0.0.200.1 detail inter-area-prefix

    OSPF3 database, Area 0.0.200.1
 Type       ID               Adv Rtr           Seq         Age  Cksum  Len
InterArPfx *0.0.0.1          1.1.1.12         0x800000b7  2087  0x481c  28
  Prefix ::/0
  Prefix-options 0x0, Metric 20
                

Here, we can see that only one Summary-LSA is advertised in OSPFv2 and only 1 Inter-Area-Prefix-LSA is advertised in OSPFv3. Just for reference, let's compare that to the number of LSAs advertised into another area;

 
play@MX480-TEST:R12> show ospf database advertising-router self area 0.0.0.1 summary
Area 0.0.0.1:
   1 Router LSAs
   22 Summary LSAs
   5 ASBRSum LSAs
Externals:
   2 Extern LSAs
Interface ge-0/0/0.3028:
Area 0.0.0.0:
Interface ge-0/0/0.3031:
Area 0.0.0.1:
Interface lo0.12:
Area 0.0.0.0:
Interface xe-0/3/1.31:
Area 0.0.200.1:

play@MX480-TEST:R12> show ospf3 database advertising-router self area 0.0.0.1 summary
Area 0.0.0.1:
   1 Router LSAs
   15 InterArPfx LSAs
   3 InterArRtr LSAs
   1 IntraArPfx LSAs
Externals:
   2 Extern LSAs
Interface ge-0/0/0.3028:
Area 0.0.0.0:
   1 Link LSAs
Interface ge-0/0/0.3031:
Area 0.0.0.1:
   1 Link LSAs
Interface lo0.12:
Area 0.0.0.0:
Interface xe-0/3/1.31:
Area 0.0.200.1:
   1 Link LSAs
                

Let's have one last look at the default route on R9 and verify if there is connectivity between R9's loopback IP address and the IP address of R15, a router located in another area:

 
play@MX80:R9> show route 0.0.0.0

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

0.0.0.0/0          *[OSPF/10] 1w1d 05:49:40, metric 21
                    > to 18.0.0.6 via xe-0/0/3.31

play@MX80:R9> show route ::/0 exact

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

::/0               *[OSPF3/10] 09:32:52, metric 21
                    > to fe80::8ae0:f300:1f55:f8f7 via xe-0/0/3.31

play@MX80:R9> ping 1.1.1.15 source 1.1.1.9
PING 1.1.1.15 (1.1.1.15): 56 data bytes
64 bytes from 1.1.1.15: icmp_seq=0 ttl=62 time=0.765 ms
^C
--- 1.1.1.15 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.765/0.765/0.765/0.000 ms

play@MX80:R9> ping 2001::15 source 2001::9
PING6(56=40+8+8 bytes) 2001::9 --> 2001::15
16 bytes from 2001::15, icmp_seq=0 hlim=62 time=17.103 ms
16 bytes from 2001::15, icmp_seq=1 hlim=62 time=16.443 ms
^C
--- 2001::15 ping6 statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 16.443/16.773/17.103/0.330 ms
                

17-10-2014