Ok, this smells like a buggy implementation of OSPF on the dot-com
vendor-side.
Upgrade of firmware on the both Cisco Nexus 3000-series to
NXOS: version 7.0(3)I4(4) fixed my problem with
ospf stuck in EXCHG/EXSTA.
Setup involving Dell switch shows following then ospfd on the obsd side is run
with
> 14 feb. 2017 kl. 11:33 skrev Jeremie Courreges-Anglas :
>
> I have no idea why you're getting this kind of error, but maybe you
> can simplify your setup a bit more. Can you reproduce when using just
> em1 (out of the trunk) instead of trunk1? Just bnx1?
Iâll try to modd this setup.
Any how
Maxim Bourmistrov writes:
> Unfortunately, this diff alone does not solves this problem.
The patch won't change much if you don't also have the kernel-side
change:
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/if.c.diff?r1=1.467&r2=1.468
Anyway, I'm not sure this will help in your ca
Unfortunately, this diff alone does not solves this problem.
Again, only reboot solved it.
Before reboot, ospfd from 6.0-stable patched with this diff:
# ospfctl sh nei
ID Pri StateDeadTime Address Iface Uptime
10.4.255.26 1 FULL/BCKUP 00:00:38 10.4.255.26
OSPF is sensitive to MTU changes. You probably want the change in
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/ospfd/ospfe.c.diff?r1=1.96&r2=1.97
from -current. This will track interface MTU changes.
On 2017 Feb 09 (Thu) at 14:51:05 +0100 (+0100), Maxim Bourmistrov wrote:
:This actuall
Hm, seems that I mistyped MTU in my original mail.
lacp system-priority 1
rate-limit cpu direction input pps 1024
system jumbo mtu 1518
It is 1518 by default.
> 9 feb. 2017 kl. 14:51 skrev Maxim Bourmistrov :
>
>
> This actually a default setting for this switch, then you don’t configure
jumbo
This actually a default setting for this switch, then you don’t configure
jumbo at all.
'sh running-config all’ shows this.
I had ’ip ospf mtu-ignore’ in the config as well, but it didn’t help, so
it is gone now.
I’ll try with 1518.
As seen in tcpdump, both obsd and dell announcing them selves wi
Are you establishing an ospf session with the N3048? If you are, then
there is an MTU miss-match.
Either "system jumbo mtu" refers to the IP packet, which doesn't match
the 1500 set on trunk1, or it refers to the ethernet packet which should
be 1518 (16 bytes for the ethernet header).
Is it fixe
I see similar behavior with Cisco Nexus and 5.9-stable.
How ever not 100% sure if it is the same trigger.
> 9 feb. 2017 kl. 14:08 skrev Maxim Bourmistrov :
>
> Hey,
>
> ospfd on 6.0-stable stucks in EXCHG/EXSTA while neighboring with Dell N3048
switch.
> According to some documentation around, t
Hey,
ospfd on 6.0-stable stucks in EXCHG/EXSTA while neighboring with Dell N3048
switch.
According to some documentation around, this is due to MTU mismatch.
This is not in my case.
N3048:
system jumbo mtu 1512
obsd:
trunk1: flags=8943 mtu 1500
lladdr 00:25:90:78:62:b6
descripti
10 matches
Mail list logo
