Re: Ospf adding new interface
So, with 6.4 recently released, I just installed it rather than using latest current - worked flawlessly - thank you. ospfctl reload now picks up new interfaces added. /S On Sat, 29 Sep 2018 at 13:40, Stuart Henderson wrote: > On 2018/09/29 13:36, Simen Stavdal wrote: > > Thanks Stuart, > > > > -vd just said the same, i.e interface unknown, will try -current and > report back :) > > If it doesn't help, it would also be worth capturing "route -n monitor" > output while adding. > > > > > Thanks, > > Simon > > > > On Sat, 29 Sep 2018 at 13:06, Stuart Henderson > wrote: > > > > I've had problems at times with ospfd not seeing interfaces properly > > after adding them, please try a -current snapshot and see if you can > > replicate it, it's possible that a change made in June might help. > > > > Also maybe try running with ospfd -vd and see if you get anything > unusual > > logged when the interface is added or when you issue 'reload'. > > > > > > >
Re: Ospf adding new interface
On 2018/09/29 13:36, Simen Stavdal wrote: > Thanks Stuart, > > -vd just said the same, i.e interface unknown, will try -current and report > back :) If it doesn't help, it would also be worth capturing "route -n monitor" output while adding. > Thanks, > Simon > > On Sat, 29 Sep 2018 at 13:06, Stuart Henderson wrote: > > I've had problems at times with ospfd not seeing interfaces properly > after adding them, please try a -current snapshot and see if you can > replicate it, it's possible that a change made in June might help. > > Also maybe try running with ospfd -vd and see if you get anything unusual > logged when the interface is added or when you issue 'reload'. > > >
Re: Ospf adding new interface
Thanks Stuart, -vd just said the same, i.e interface unknown, will try -current and report back :) Thanks, Simon On Sat, 29 Sep 2018 at 13:06, Stuart Henderson wrote: > I've had problems at times with ospfd not seeing interfaces properly > after adding them, please try a -current snapshot and see if you can > replicate it, it's possible that a change made in June might help. > > Also maybe try running with ospfd -vd and see if you get anything unusual > logged when the interface is added or when you issue 'reload'. > > >
Re: Ospf adding new interface
I've had problems at times with ospfd not seeing interfaces properly after adding them, please try a -current snapshot and see if you can replicate it, it's possible that a change made in June might help. Also maybe try running with ospfd -vd and see if you get anything unusual logged when the interface is added or when you issue 'reload'.
Re: Ospf adding new interface
Thanks Remi,
I am doing almost exactly that too
My setup:
mgmt--6.3amd64<-rdomain0->6.3octeon-mgmt
Ospf is running inside rdomain0.
Scenario:
On amd64 : I have a few loopback interfaces running, and routing works ok.
Example, lo17 is advertised as 192.168.17.144/32
On octeon : I can ping 192.168.17.144, and it is showing expected egress
interfaces etc
On amd : cp /etc/hostname.lo17 /etc/hostname.lo13
I give lo13 the address of 192.168.13.144/32
I bring it up with sh /etc/netstart lo13
I ping it locally ok
I add the interface as passive in ospfd.conf like you described above,
syntax is good.
I issue ospfctl reload
In /var/log/messages, it says lo13
Sep 29 12:20:18 4nic2 ospfd[33900]: /etc/ospfd.conf:32: unknown interface
lo13
Sep 29 12:20:18 4nic2 ospfd[33900]: configuration reload failed
On octeon : new interface is obviously not seen.
On amd64 : restart the entire ospfd daemon (as opposed to ospfctl reload),
config file now reads ok, no issue.
On octeon : I now can see the advertised lo13 address, and ping it. routing
table looks as expected.
So, I know my syntax is good, because it works when I restart the daemon,
it just happens when I try reloading it.
My setup may be a little different to yours though.
I have a mangement interface that I use to connect to my lab, running in
routing domain 1.
After logging in, I issue a "route -T0 exec ksh" to work inside routing
domain 0.
I have verified that all processes run in the expected routing domains.
Also, I have issued all daemons and reload processes to be executed in
rdomain 0.
i.e route -T0 exec ospfctl reload
I am wondering why ospfd can't see the new interface while running, but it
does after completely restarting the daemon.
I am starting ospfd from command line, not with rc flags, because I am
still testing.
Have tried daemonized and with "-d" flag - both demonstrate the same issue.
Btw, when I reverse it, i.e creating the lo interfaces on the octeon box, I
see the same problem.
Cheers,
Simon.
On Fri, 28 Sep 2018 at 23:41, Remi Locherer wrote:
> Hi Simon
>
> On Fri, Sep 28, 2018 at 10:22:42PM +0200, Simen Stavdal wrote:
> > Hi all,
> >
> > On 6.3, using both octeon and amd64.
> >
> > While ospfd is running, I would like to add another interface (let’s say
> a
> > loopback if). After adding the loopback if to ospf as passive I reload
> > with ospfctl, but it does not start advertising the new interface. Only
> > when I restart ospfd will it start doing so, but it seems a bit intrusive
> > as all neighbours will recalculate. I am sure that something basic had
> > slipped my mind. Any way to make it register the new if?
> >
> > The config is working since it does pick up the if on ospfd restart.
> >
>
> When I do what you describe the route is immediate seen by other ospf
> router. I quickly checked on amd64 -current VMs. I did this many times
> in the last few years and it always worked for me.
>
> I tested now with this config:
>
> r2# cat /etc/ospfd.conf
> router-id 192.168.250.102
>
> area 0.0.0.0 {
> interface vio0
> interface vlan1
> }
>
>
> Then I started ospfd and created lo33. After that I added this line to
> ospfd.conf:
>interface lo33 { passive }
>
> Then I did "ospfctl reload" and the expectd route appeared in neighbor's
> routing table.
>
> Regards,
> Remi
>
Re: Ospf adding new interface
Hi Simon
On Fri, Sep 28, 2018 at 10:22:42PM +0200, Simen Stavdal wrote:
> Hi all,
>
> On 6.3, using both octeon and amd64.
>
> While ospfd is running, I would like to add another interface (let’s say a
> loopback if). After adding the loopback if to ospf as passive I reload
> with ospfctl, but it does not start advertising the new interface. Only
> when I restart ospfd will it start doing so, but it seems a bit intrusive
> as all neighbours will recalculate. I am sure that something basic had
> slipped my mind. Any way to make it register the new if?
>
> The config is working since it does pick up the if on ospfd restart.
>
When I do what you describe the route is immediate seen by other ospf
router. I quickly checked on amd64 -current VMs. I did this many times
in the last few years and it always worked for me.
I tested now with this config:
r2# cat /etc/ospfd.conf
router-id 192.168.250.102
area 0.0.0.0 {
interface vio0
interface vlan1
}
Then I started ospfd and created lo33. After that I added this line to
ospfd.conf:
interface lo33 { passive }
Then I did "ospfctl reload" and the expectd route appeared in neighbor's
routing table.
Regards,
Remi
Ospf adding new interface
Hi all, On 6.3, using both octeon and amd64. While ospfd is running, I would like to add another interface (let’s say a loopback if). After adding the loopback if to ospf as passive I reload with ospfctl, but it does not start advertising the new interface. Only when I restart ospfd will it start doing so, but it seems a bit intrusive as all neighbours will recalculate. I am sure that something basic had slipped my mind. Any way to make it register the new if? The config is working since it does pick up the if on ospfd restart. Cheers, Simon
