OSPFv2 and OSPFv3 verification of area 0.0.0.50.

There are two things happening in this area, a static route is being redistributed and a virtual-link between R4 and R11 is configured. The verification of redistributing static routes into OSPFv2 and OSPFv3 is something that I went through before for the other areas. There, in this case, the focus will be on the virtual link.



scenario


The virtual link is configured to transit area 0.0.0.50 to connect the area behind R4, area 0.0.0.150, to the backbone. To accomplish this, the virtual link must be configured between R11, the router connecting to the backbone area and R4, the router connecting to area 0.0.0.150.

The following command shows that the OSPFv2 virtual link is configured correctly:

 
play@MX80:R4> show ospf neighbor area 0.0.0.0 extensive
Address          Interface              State     ID               Pri  Dead
16.0.0.22        vl-1.1.1.11            Full      1.1.1.11           0     2
  Area 0.0.0.0, opt 0x42, DR 0.0.0.0, BDR 0.0.0.0
  Up 10:29:36, adjacent 10:29:36
   Topology default (ID 0) -> Bidirectional

play@MX80:R4> show ospf interface extensive vl-1.1.1.11
Interface           State   Area            DR ID           BDR ID          Nbrs
vl-1.1.1.11         PtToPt  0.0.0.0         0.0.0.0         0.0.0.0            1
  Type: Virtual, Address: 16.0.0.25, Mask: 0.0.0.0, MTU: 0, Cost: 11
  Transit Area: 0.0.0.50, Destination: 16.0.0.22
  Adj count: 1
  Hello: 1, Dead: 3, ReXmit: 5, Not Stub
  Auth type: MD5, Active key ID: 14, Start time: 1970 Jan  1 00:00:00 UTC
  Protection type: None, No eligible backup
  Topology default (ID 0) -> Cost: 11
                

As a consequence, all R4 is now also maintaining an LSDB for area 0.0.0.0:

                 
play@MX80:R4> show ospf database area 0.0.0.0

    OSPF database, Area 0.0.0.0
 Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
Router  *1.1.1.4          1.1.1.4          0x800002f3  2108  0x22 0xf5f3  36
Router   1.1.1.11         1.1.1.11         0x800003fe  2440  0x22 0xd583  96
Router   1.1.1.12         1.1.1.12         0x800003c1  2557  0x22 0xb53b  60
Router   1.1.1.13         1.1.1.13         0x800003e3  2346  0x22 0x6910  84
Summary *1.1.1.3          1.1.1.4          0x800002a0   970  0x22 0x364e  28
Summary *1.1.1.4          1.1.1.4          0x8000029f  1384  0x22 0xc9c4  28
Summary  1.1.1.4          1.1.1.11         0x8000029e  1477  0x22 0xb5d0  28
Summary  1.1.1.6          1.1.1.12         0x800001a4  1210  0x22 0x9ce0  28
Summary  1.1.1.8          1.1.1.11         0x800000f8    10  0x22 0xd456  28
Summary  1.1.1.9          1.1.1.12         0x800000f4  1823  0x22 0xcc60  28
Summary  1.1.1.14         1.1.1.12         0x800002de  1272  0x22 0xc07b  28
Summary  1.1.1.15         1.1.1.12         0x800002df  1149  0x22 0xbe7a  28
Summary *1.1.1.16         1.1.1.4          0x800002a1   918  0x22 0xb1c4  28
Summary  1.1.1.16         1.1.1.11         0x8000029e  1732  0x22 0x3348  28
Summary *2.0.0.36         1.1.1.4          0x800002a1  1125  0x22 0xe085  28
Summary  2.0.0.120        1.1.1.12         0x8000023c  1088  0x22 0xd1a8  28
Summary  16.0.0.12        1.1.1.12         0x800002f9  1578  0x22 0xdf39  28
etc.
etc.
                

Checking the OSPFv3 part of the configuration is very similar. I did run into some issues with the OSPFv3 virtual-link though. The neighbor state across the virtual-link was in Init:

   
play@MX80:R4> show ospf3 neighbor 1.1.1.11
ID               Interface              State     Pri   Dead
1.1.1.11         vl-1.1.1.11            Init        0      2
  Neighbor-address 2001:16:21:0:8ae0:f30b:d955:f852              
                

First I did was checking the configuration again:

R4:
    
set protocols ospf3 area 0.0.0.0 virtual-link neighbor-id 1.1.1.11 transit-area 0.0.0.50 hello-interval 1
set protocols ospf3 area 0.0.0.0 virtual-link neighbor-id 1.1.1.11 transit-area 0.0.0.50 dead-interval 3
set protocols ospf3 area 0.0.0.0 virtual-link neighbor-id 1.1.1.11 transit-area 0.0.0.50 ipsec-sa ospfv3             
                
R11:
    
set protocols ospf3 area 0.0.0.0 virtual-link neighbor-id 1.1.1.4 transit-area 0.0.0.50 hello-interval 1
set protocols ospf3 area 0.0.0.0 virtual-link neighbor-id 1.1.1.4 transit-area 0.0.0.50 dead-interval 3
set protocols ospf3 area 0.0.0.0 virtual-link neighbor-id 1.1.1.4 transit-area 0.0.0.50 ipsec-sa ospfv3             
                

I did not see anything wrong with that. I then looked at the 'show ospf3 interface' command;

    
play@MX480-TEST:R11> show ospf3 interface vl-1.1.1.4 extensive
Interface           State   Area            DR ID           BDR ID          Nbrs
vl-1.1.1.4          PtToPt  0.0.0.0         0.0.0.0         0.0.0.0            0
  Address 2001:16:21:0:8ae0:f30b:d955:f852, Prefix-length 0
  Transit Area: 0.0.0.50, Destination: 2001::4
  OSPF3-Intf-index 5, Type Virtual, MTU 0, Cost 2
  Adj count: 0, Router LSA ID: -
  Hello 1, Dead 3, ReXmit 5, Not Stub
  IPSec SA name: ospfv3
  Protection type: None, No eligible backup
  
play@MX80:R4> show ospf3 interface vl-1.1.1.11 extensive
Interface           State   Area            DR ID           BDR ID          Nbrs
vl-1.1.1.11         PtToPt  0.0.0.0         0.0.0.0         0.0.0.0            1
  Address 2001:16:25:0:5e5e:ab00:10d:ed72, Prefix-length 0
  Transit Area: 0.0.0.50, Destination: 2001:16:21:0:8ae0:f30b:d955:f852
  OSPF3-Intf-index 3, Type Virtual, MTU 0, Cost 11
  Adj count: 0, Router LSA ID: -
  Hello 1, Dead 3, ReXmit 5, Not Stub
  IPSec SA name: ospfv3
  Protection type: None, No eligible backup             
                

The thing I noticed was that R11's destination differs from R4's source, or was it the other way around?! The interfaces that R4 was using correspond to the IPv6 address on both of the routers:

    
play@MX480-TEST:R11> show interfaces ge-0/1/0.3033 terse
Interface               Admin Link Proto    Local                 Remote
ge-0/1/0.3033           up    up   inet     16.0.0.22/30
                                   inet6    2001:16:21:0:8ae0:f30b:d955:f852/64
                                            fe80::8ae0:f30b:d955:f852/64
                                   multiservice


play@MX80:R4> show interfaces xe-0/0/2.1 terse
Interface               Admin Link Proto    Local                 Remote
xe-0/0/2.1              up    up   inet     16.0.0.25/30
                                   inet6    2001:16:25:0:5e5e:ab00:10d:ed72/64
                                            fe80::5e5e:ab00:10d:ed72/64
                                   multiservice             
                

Out of curiosity, I wanted to see if this would have been the case without the authentication on the link so I removed that:

R4:
    
delete protocols ospf3 area 0.0.0.0 virtual-link neighbor-id 1.1.1.11 transit-area 0.0.0.50 ipsec-sa             
                
R11:
    
delete protocols ospf3 area 0.0.0.0 virtual-link neighbor-id 1.1.1.4 transit-area 0.0.0.50 ipsec-sa            
                

To my surprise, the virtual-link came up and started working:

    
play@MX480-TEST:R11> show ospf3 interface vl-1.1.1.4 extensive
Interface           State   Area            DR ID           BDR ID          Nbrs
vl-1.1.1.4          PtToPt  0.0.0.0         0.0.0.0         0.0.0.0            1
  Address 2001:16:21:0:8ae0:f30b:d955:f852, Prefix-length 0
  Transit Area: 0.0.0.50, Destination: 2001::4
  OSPF3-Intf-index 5, Type Virtual, MTU 0, Cost 2
  Adj count: 1, Router LSA ID: 0
  Hello 1, Dead 3, ReXmit 5, Not Stub
  Protection type: None, No eligible backup

play@MX480-TEST:R11> show ospf3 neighbor extensive 1.1.1.4
ID               Interface              State     Pri   Dead
1.1.1.4          vl-1.1.1.4             Full        0      2
  Neighbor-address 2001:16:25:0:5e5e:ab00:10d:ed72
  Area 0.0.0.0, opt 0x13, OSPF3-Intf-Index 3
  DR-ID 0.0.0.0, BDR-ID 0.0.0.0
  Up 00:03:50, adjacent 00:03:45
  
play@MX80:R4> show ospf3 neighbor 1.1.1.11 extensive
ID               Interface              State     Pri   Dead
1.1.1.11         vl-1.1.1.11            Full        0      2
  Neighbor-address 2001:16:21:0:8ae0:f30b:d955:f852
  Area 0.0.0.0, opt 0x13, OSPF3-Intf-Index 5
  DR-ID 0.0.0.0, BDR-ID 0.0.0.0
  Up 00:04:06, adjacent 00:04:04

play@MX80:R4> show ospf3 interface vl-1.1.1.11 extensive
Interface           State   Area            DR ID           BDR ID          Nbrs
vl-1.1.1.11         PtToPt  0.0.0.0         0.0.0.0         0.0.0.0            1
  Address 2001:16:25:0:5e5e:ab00:10d:ed72, Prefix-length 0
  Transit Area: 0.0.0.50, Destination: 2001:16:21:0:8ae0:f30b:d955:f852
  OSPF3-Intf-index 3, Type Virtual, MTU 0, Cost 11
  Adj count: 1, Router LSA ID: 0
  Hello 1, Dead 3, ReXmit 5, Not Stub
  Protection type: None, No eligible backup             
                

As can be seen in the following output, R4 is now connected to area 0.0.0.0:

    
play@MX80:R4> show ospf3 database summary area 0.0.0.0
Area 0.0.0.0:
   4 Router LSAs
   27 InterArPfx LSAs
   4 InterArRtr LSAs
   3 IntraArPfx LSAs             
                

Possibly there is something I am doing wrong or there is something I seem to be missing out on.

18-10-2014