OPNsense Forum

Archive => 18.7 Legacy Series => Topic started by: alex_rhys-hurn on September 23, 2018, 11:30:42 am

Title: [SOLVED] Weird OSPF Behaviour FRR
Post by: alex_rhys-hurn on September 23, 2018, 11:30:42 am
Hi All,

Your help appreciated with my situation. In summary, FRR is showing an interface that is not configured....

I have OPNsense running as a VM on Vsphere with VMXNET NICs:
Code: [Select]
OPNsense 18.7.3-amd64
FreeBSD 11.1-RELEASE-p14
OpenSSL 1.0.2p 14 Aug 2018

I have installed FRR v. 3.0.3

The running config is:
Code: [Select]
frr version 3.0.3
frr defaults traditional
!
log file /var/log/frr.log
!
interface vmx0
 ip ospf authentication message-digest
 ip ospf cost 10
 ip ospf message-digest-key 1 md5 MASKED
!
interface vmx1
 ip ospf authentication message-digest
 ip ospf cost 10
 ip ospf message-digest-key 1 md5 MASKED
!
router ospf
 ospf router-id 160.119.216.38
 passive-interface vmx2_vlan103
 passive-interface vmx2_vlan115
 passive-interface vmx2_vlan301
 network 160.119.216.32/29 area 0.0.0.1
 network 160.119.216.240/28 area 0.0.0.1
!
line vty
!
end

When I look at show ip ospf interfaces, I get:
Code: [Select]
sh ip ospf interface
vmx0 is up
  ifindex 1, MTU 9000 bytes, BW 10000 Mbit <UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
  Internet Address 160.119.216.38/29, Broadcast 160.119.216.39, Area 0.0.0.1
  MTU mismatch detection:enabled
  Router ID 160.119.216.38, Network Type BROADCAST, Cost: 10
  Transmit Delay is 1 sec, State Backup, Priority 1
  Backup Designated Router (ID) 160.119.216.38, Interface Address 160.119.216.38
  Multicast group memberships: OSPFAllRouters OSPFDesignatedRouters
  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
    Hello due in 6.044s
  Neighbor Count is 1, Adjacent neighbor count is 1
vmx2_vlan115 is up
  ifindex 10, MTU 1500 bytes, BW 10000 Mbit <UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
  Internet Address 160.119.216.241/28, Broadcast 160.119.216.255, Area 0.0.0.1
  MTU mismatch detection:enabled
  Router ID 160.119.216.38, Network Type BROADCAST, Cost: 10
  Transmit Delay is 1 sec, State DR, Priority 1
  No backup designated router on this network
  Multicast group memberships: <None>
  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
    No Hellos (Passive interface)
  Neighbor Count is 0, Adjacent neighbor count is 0

Thats not right! interface vmx2_vlan115 should be passive!!! That should read vmx1 as the interface name.

The log below shows that it even starts trying a neighbour election on the incorrect interface!

Code: [Select]
2018/09/23 12:21:51 OSPF: ospfd 3.0.3 starting: vty@2604
2018/09/23 12:21:51 ZEBRA: client 17 says hello and bids fair to announce only ospf routes
2018/09/23 12:21:51 OSPF: MPLS-TE(initialize_linkparams) Could not find corresponding OSPF Interface for enc0
2018/09/23 12:21:51 OSPF: MPLS-TE(initialize_linkparams) Could not find corresponding OSPF Interface for lo0
2018/09/23 12:21:51 OSPF: MPLS-TE(initialize_linkparams) Could not find corresponding OSPF Interface for pflog0
2018/09/23 12:21:51 OSPF: MPLS-TE(initialize_linkparams) Could not find corresponding OSPF Interface for pfsync0
2018/09/23 12:21:51 OSPF: interface 160.119.216.38 [1] join AllSPFRouters Multicast group.
2018/09/23 12:21:51 OSPF: SPF: Scheduled in 0 msec
2018/09/23 12:21:51 OSPF: MPLS-TE(initialize_linkparams) Could not find corresponding OSPF Interface for vmx2
2018/09/23 12:21:51 OSPF: SPF: Scheduled in 50 msec
2018/09/23 12:21:52 OSPF: SPF Processing Time(usecs): External Routes: 8

2018/09/23 12:22:01 OSPF: DR-Election[1st]: Backup 160.119.216.38
2018/09/23 12:22:01 OSPF: DR-Election[1st]: DR     160.119.216.33
2018/09/23 12:22:01 OSPF: DR-Election[2nd]: Backup 160.119.216.38
2018/09/23 12:22:01 OSPF: DR-Election[2nd]: DR     160.119.216.33
2018/09/23 12:22:01 OSPF: interface 160.119.216.38 [1] join AllDRouters Multicast group.
2018/09/23 12:22:01 OSPF: DR-Election[1st]: Backup 160.119.216.38
2018/09/23 12:22:01 OSPF: DR-Election[1st]: DR     160.119.216.33
2018/09/23 12:22:01 OSPF: Packet[DD]: Neighbor 160.119.216.106 Negotiation done (Slave).
2018/09/23 12:22:01 OSPF: SPF: Scheduled in 0 msec
2018/09/23 12:22:01 OSPF: SPF: Scheduled in 0 msec
2018/09/23 12:22:02 OSPF: SPF Processing Time(usecs): External Routes: 12

2018/09/23 12:22:06 OSPF: SPF: Scheduled in 0 msec
2018/09/23 12:22:06 OSPF: nsm_change_state(160.119.216.106, Loading -> Full): scheduling new router-LSA origination
2018/09/23 12:22:07 OSPF: SPF Processing Time(usecs): External Routes: 94

2018/09/23 12:22:31 OSPF: DR-Election[1st]: Backup 160.119.216.241
2018/09/23 12:22:31 OSPF: DR-Election[1st]: DR     160.119.216.241
2018/09/23 12:22:31 OSPF: DR-Election[2nd]: Backup 0.0.0.0
2018/09/23 12:22:31 OSPF: DR-Election[2nd]: DR     160.119.216.241

Thanks in advance, and best regards to all.

Alex
Title: Re: Weird OSPF Behaviour FRR
Post by: mimugmail on September 23, 2018, 12:12:00 pm
Why so you set the network of a passive interface in OSPF config?
Title: Re: Weird OSPF Behaviour FRR
Post by: alex_rhys-hurn on September 23, 2018, 04:56:54 pm
I didnt.

If you read the running-config closely, it should have interfaces vmx0 and vmx1

But sh ip ospf int gives me vmx0 and vmx2_vlan115.....

THe running config shows that vmx2_vlan115 should be passive.

Then if you look closely in the sh ip ospf int it does state that no hellos on vlan115 as its passive....

WHole thing seems messed up (or its a misconfig by me - likely).

Your added ideas, much appreciated.

Alex

Title: Re: Weird OSPF Behaviour FRR
Post by: mimugmail on September 23, 2018, 06:30:23 pm
Sorry, only mobile today. But for me it's seems in OSPF config you use in network config the one configured as your passive vlan and this will activate the interface.
Title: Re: Weird OSPF Behaviour FRR
Post by: alex_rhys-hurn on September 23, 2018, 11:36:27 pm
Hi,

Even though you are using your mobile, you have sorted me out. Many thanks!

I had not understood that announcing a network in "Networks" would bring the interface "Up" thanks for clarifying that.

I also learned from your comment that its not enough to have an interface configured, but that it wont come up until you announce its own subnet. So I did that and all is well.

This is my first foray with FRR, as am familliar with other platforms that behave a little differently.

Thanks for all your time on a sunday.

Alex