[AFMUG] flapping ethernet port ospf workaround
So ive been dealing with the SAFs and the mikrotiks being uppity with one another. SAF has a gigabit port, but it only offers the option to lock it to 100, not gigabit. so I have the mikrotiks set, just not the otherside, the port still flaps on both radios what was happening is everytime it flaps, the interface dropped in ospf and went neighbor down, rerouting traffic then coming back up what I did was made a bridge, added that port to it, and put the ospf ip on the bridge itself, this allows the port to flap without the ospf interface going down until we work throught the issue with SAF I'm wondering if this is causing some other harm having it on the bridge, rather than the physical port
Re: [AFMUG] flapping ethernet port ospf workaround
Might make sure spanning tree is disabled on the MT bridge so its BPDUs don't interact with any spanning tree that might be enabled on the SAF. Otherwise, shouldn't be a huge deal. Jesse DuPont Network Architect email: jesse.dup...@celeritycorp.net Celerity Networks LLC Celerity Broadband LLC Like us! facebook.com/celeritynetworksllc Like us! facebook.com/celeritybroadband On 7/19/17 10:20 AM, Steve Jones wrote: So ive been dealing with the SAFs and the mikrotiks being uppity with one another. SAF has a gigabit port, but it only offers the option to lock it to 100, not gigabit. so I have the mikrotiks set, just not the otherside, the port still flaps on both radios what was happening is everytime it flaps, the interface dropped in ospf and went neighbor down, rerouting traffic then coming back up what I did was made a bridge, added that port to it, and put the ospf ip on the bridge itself, this allows the port to flap without the ospf interface going down until we work throught the issue with SAF I'm wondering if this is causing some other harm having it on the bridge, rather than the physical port
Re: [AFMUG] flapping ethernet port ospf workaround
lol that's always step 1. I wish you could just do global stp off On Wed, Jul 19, 2017 at 12:31 PM, Jesse DuPont < jesse.dup...@celeritycorp.net> wrote: > Might make sure spanning tree is disabled on the MT bridge so its BPDUs > don't interact with any spanning tree that might be enabled on the SAF. > Otherwise, shouldn't be a huge deal. > > *Jesse DuPont* > > Network Architect > email: jesse.dup...@celeritycorp.net > Celerity Networks LLC > > Celerity Broadband LLC > Like us! facebook.com/celeritynetworksllc > > Like us! facebook.com/celeritybroadband > On 7/19/17 10:20 AM, Steve Jones wrote: > > So ive been dealing with the SAFs and the mikrotiks being uppity with one > another. > SAF has a gigabit port, but it only offers the option to lock it to 100, > not gigabit. > so I have the mikrotiks set, just not the otherside, the port still flaps > on both radios > > what was happening is everytime it flaps, the interface dropped in ospf > and went neighbor down, rerouting traffic then coming back up > > what I did was made a bridge, added that port to it, and put the ospf ip > on the bridge itself, this allows the port to flap without the ospf > interface going down until we work throught the issue with SAF > > I'm wondering if this is causing some other harm having it on the bridge, > rather than the physical port > > >
Re: [AFMUG] flapping ethernet port ospf workaround
I’ve had to run OSPF on a bridge in a pinch, and so long as you don’t make any live changes to the bridge (adding/removing interfaces), the Mikrotik won’t mind. Just remember to set your static OSPF interfaces (if you have any) accordingly. Same goes for MPLS – LDP Interfaces if you’re using it. If you’re thinking it’ll be like this for longer than a week, leave yourself plenty of documentation to backtrack properly. Nothing like coming back to it three months later and trying to remember what you did! Chris Wright Network Administrator From: Af [mailto:af-boun...@afmug.com] On Behalf Of Steve Jones Sent: Wednesday, July 19, 2017 9:21 AM To: af@afmug.com Subject: [AFMUG] flapping ethernet port ospf workaround So ive been dealing with the SAFs and the mikrotiks being uppity with one another. SAF has a gigabit port, but it only offers the option to lock it to 100, not gigabit. so I have the mikrotiks set, just not the otherside, the port still flaps on both radios what was happening is everytime it flaps, the interface dropped in ospf and went neighbor down, rerouting traffic then coming back up what I did was made a bridge, added that port to it, and put the ospf ip on the bridge itself, this allows the port to flap without the ospf interface going down until we work throught the issue with SAF I'm wondering if this is causing some other harm having it on the bridge, rather than the physical port
Re: [AFMUG] flapping ethernet port ospf workaround
if this doesn't harm anything, I'm thinking I may make this the standard, its flapped 24 times since I put it in, not a single ospf drop On Wed, Jul 19, 2017 at 1:54 PM, Chris Wright wrote: > I’ve had to run OSPF on a bridge in a pinch, and so long as you don’t make > any live changes to the bridge (adding/removing interfaces), the Mikrotik > won’t mind. Just remember to set your static OSPF interfaces (if you have > any) accordingly. Same goes for MPLS – LDP Interfaces if you’re using it. > If you’re thinking it’ll be like this for longer than a week, leave > yourself plenty of documentation to backtrack properly. Nothing like coming > back to it three months later and trying to remember what you did! > > > > Chris Wright > > Network Administrator > > > > *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Steve Jones > *Sent:* Wednesday, July 19, 2017 9:21 AM > *To:* af@afmug.com > *Subject:* [AFMUG] flapping ethernet port ospf workaround > > > > So ive been dealing with the SAFs and the mikrotiks being uppity with one > another. > > SAF has a gigabit port, but it only offers the option to lock it to 100, > not gigabit. > > so I have the mikrotiks set, just not the otherside, the port still flaps > on both radios > > > > what was happening is everytime it flaps, the interface dropped in ospf > and went neighbor down, rerouting traffic then coming back up > > > > what I did was made a bridge, added that port to it, and put the ospf ip > on the bridge itself, this allows the port to flap without the ospf > interface going down until we work throught the issue with SAF > > > > I'm wondering if this is causing some other harm having it on the bridge, > rather than the physical port >
Re: [AFMUG] flapping ethernet port ospf workaround
Do you have shielded cable the whole way end to end? SAFs seem to be quite sensitive to that. On Jul 19, 2017 11:20 AM, "Steve Jones" wrote: > So ive been dealing with the SAFs and the mikrotiks being uppity with one > another. > SAF has a gigabit port, but it only offers the option to lock it to 100, > not gigabit. > so I have the mikrotiks set, just not the otherside, the port still flaps > on both radios > > what was happening is everytime it flaps, the interface dropped in ospf > and went neighbor down, rerouting traffic then coming back up > > what I did was made a bridge, added that port to it, and put the ospf ip > on the bridge itself, this allows the port to flap without the ospf > interface going down until we work throught the issue with SAF > > I'm wondering if this is causing some other harm having it on the bridge, > rather than the physical port >
Re: [AFMUG] flapping ethernet port ospf workaround
BBDGE its got the transtector surge suppressor, I'm suspecting that, this is the only lik with it and both radios are doing it On Wed, Jul 19, 2017 at 2:44 PM, Colin Stanners wrote: > Do you have shielded cable the whole way end to end? SAFs seem to be quite > sensitive to that. > > On Jul 19, 2017 11:20 AM, "Steve Jones" wrote: > >> So ive been dealing with the SAFs and the mikrotiks being uppity with one >> another. >> SAF has a gigabit port, but it only offers the option to lock it to 100, >> not gigabit. >> so I have the mikrotiks set, just not the otherside, the port still flaps >> on both radios >> >> what was happening is everytime it flaps, the interface dropped in ospf >> and went neighbor down, rerouting traffic then coming back up >> >> what I did was made a bridge, added that port to it, and put the ospf ip >> on the bridge itself, this allows the port to flap without the ospf >> interface going down until we work throught the issue with SAF >> >> I'm wondering if this is causing some other harm having it on the bridge, >> rather than the physical port >> >
Re: [AFMUG] flapping ethernet port ospf workaround
All surge suppressors can and probably will cause this if there is a ground potential difference or an unusually high amount of electrical noise on the ground that the surge suppressor is connected to. Lift the ground off the surge suppressor to see if that helps. From: Steve Jones Sent: Wednesday, July 19, 2017 1:49 PM To: af@afmug.com Subject: Re: [AFMUG] flapping ethernet port ospf workaround BBDGE its got the transtector surge suppressor, I'm suspecting that, this is the only lik with it and both radios are doing it On Wed, Jul 19, 2017 at 2:44 PM, Colin Stanners wrote: Do you have shielded cable the whole way end to end? SAFs seem to be quite sensitive to that. On Jul 19, 2017 11:20 AM, "Steve Jones" wrote: So ive been dealing with the SAFs and the mikrotiks being uppity with one another. SAF has a gigabit port, but it only offers the option to lock it to 100, not gigabit. so I have the mikrotiks set, just not the otherside, the port still flaps on both radios what was happening is everytime it flaps, the interface dropped in ospf and went neighbor down, rerouting traffic then coming back up what I did was made a bridge, added that port to it, and put the ospf ip on the bridge itself, this allows the port to flap without the ospf interface going down until we work throught the issue with SAF I'm wondering if this is causing some other harm having it on the bridge, rather than the physical port
Re: [AFMUG] flapping ethernet port ospf workaround
Oh you have the fancy cable. And indoors there are shielded patch cables etc? I agree that the SSes would be suspected. Also note that if you are using DC over a dedicated non-ethernet line and are using the SAF DC surge protector it is possible to miswire it, I had seen someone do that. On Wed, Jul 19, 2017 at 2:49 PM, Steve Jones wrote: > BBDGE > its got the transtector surge suppressor, I'm suspecting that, this is the > only lik with it and both radios are doing it > > On Wed, Jul 19, 2017 at 2:44 PM, Colin Stanners > wrote: > >> Do you have shielded cable the whole way end to end? SAFs seem to be >> quite sensitive to that. >> >> On Jul 19, 2017 11:20 AM, "Steve Jones" >> wrote: >> >>> So ive been dealing with the SAFs and the mikrotiks being uppity with >>> one another. >>> SAF has a gigabit port, but it only offers the option to lock it to 100, >>> not gigabit. >>> so I have the mikrotiks set, just not the otherside, the port still >>> flaps on both radios >>> >>> what was happening is everytime it flaps, the interface dropped in ospf >>> and went neighbor down, rerouting traffic then coming back up >>> >>> what I did was made a bridge, added that port to it, and put the ospf ip >>> on the bridge itself, this allows the port to flap without the ospf >>> interface going down until we work throught the issue with SAF >>> >>> I'm wondering if this is causing some other harm having it on the >>> bridge, rather than the physical port >>> >> >
Re: [AFMUG] flapping ethernet port ospf workaround
hopefully the SAF guys will get me a CLI or something to just configure the port at 1000. Anybody know why this is, Its like this on powercode BMUs also, you can only select up to 100 on the gigabit ports. I seem to recall reading something sometime back about that being somewhat common On Wed, Jul 19, 2017 at 2:51 PM, Chuck McCown wrote: > All surge suppressors can and probably will cause this if there is a > ground potential difference or an unusually high amount of electrical noise > on the ground that the surge suppressor is connected to. > > Lift the ground off the surge suppressor to see if that helps. > > *From:* Steve Jones > *Sent:* Wednesday, July 19, 2017 1:49 PM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] flapping ethernet port ospf workaround > > BBDGE > its got the transtector surge suppressor, I'm suspecting that, this is the > only lik with it and both radios are doing it > > On Wed, Jul 19, 2017 at 2:44 PM, Colin Stanners > wrote: > >> Do you have shielded cable the whole way end to end? SAFs seem to be >> quite sensitive to that. >> >> On Jul 19, 2017 11:20 AM, "Steve Jones" >> wrote: >> >>> So ive been dealing with the SAFs and the mikrotiks being uppity with >>> one another. >>> SAF has a gigabit port, but it only offers the option to lock it to 100, >>> not gigabit. >>> so I have the mikrotiks set, just not the otherside, the port still >>> flaps on both radios >>> >>> what was happening is everytime it flaps, the interface dropped in ospf >>> and went neighbor down, rerouting traffic then coming back up >>> >>> what I did was made a bridge, added that port to it, and put the ospf ip >>> on the bridge itself, this allows the port to flap without the ospf >>> interface going down until we work throught the issue with SAF >>> >>> I'm wondering if this is causing some other harm having it on the >>> bridge, rather than the physical port >>> >> >
Re: [AFMUG] flapping ethernet port ospf workaround
this is that POE injector deal from SAF where you break the DC back out up top. When we do the next I think we will do independent DC and fiber, its probably less prone to issues On Wed, Jul 19, 2017 at 2:53 PM, Colin Stanners wrote: > Oh you have the fancy cable. And indoors there are shielded patch cables > etc? I agree that the SSes would be suspected. Also note that if you are > using DC over a dedicated non-ethernet line and are using the SAF DC surge > protector it is possible to miswire it, I had seen someone do that. > > On Wed, Jul 19, 2017 at 2:49 PM, Steve Jones > wrote: > >> BBDGE >> its got the transtector surge suppressor, I'm suspecting that, this is >> the only lik with it and both radios are doing it >> >> On Wed, Jul 19, 2017 at 2:44 PM, Colin Stanners >> wrote: >> >>> Do you have shielded cable the whole way end to end? SAFs seem to be >>> quite sensitive to that. >>> >>> On Jul 19, 2017 11:20 AM, "Steve Jones" >>> wrote: >>> So ive been dealing with the SAFs and the mikrotiks being uppity with one another. SAF has a gigabit port, but it only offers the option to lock it to 100, not gigabit. so I have the mikrotiks set, just not the otherside, the port still flaps on both radios what was happening is everytime it flaps, the interface dropped in ospf and went neighbor down, rerouting traffic then coming back up what I did was made a bridge, added that port to it, and put the ospf ip on the bridge itself, this allows the port to flap without the ospf interface going down until we work throught the issue with SAF I'm wondering if this is causing some other harm having it on the bridge, rather than the physical port >>> >> >
Re: [AFMUG] flapping ethernet port ospf workaround
OSPF didn't lose the neighbor, but you still want to fix the ethernet issue. One thing that could be an issue is if you want OSPF to fail over to a secondary path. If the interface goes down, then the router knows instantly that something is wrong and convergence can start right away. If the path is down while the interface stays up, then the router has to wait for hello packets to time out before it's aware of the issue. The default dead timer is 40 seconds, so the "it's down but I don't know yet" condition has to last at least that long before the router takes action. -- Original Message -- From: "Steve Jones" To: "af@afmug.com" Sent: 7/19/2017 3:03:11 PM Subject: Re: [AFMUG] flapping ethernet port ospf workaround if this doesn't harm anything, I'm thinking I may make this the standard, its flapped 24 times since I put it in, not a single ospf drop On Wed, Jul 19, 2017 at 1:54 PM, Chris Wright wrote: I’ve had to run OSPF on a bridge in a pinch, and so long as you don’t make any live changes to the bridge (adding/removing interfaces), the Mikrotik won’t mind. Just remember to set your static OSPF interfaces (if you have any) accordingly. Same goes for MPLS – LDP Interfaces if you’re using it. If you’re thinking it’ll be like this for longer than a week, leave yourself plenty of documentation to backtrack properly. Nothing like coming back to it three months later and trying to remember what you did! Chris Wright Network Administrator From: Af [mailto:af-boun...@afmug.com] On Behalf Of Steve Jones Sent: Wednesday, July 19, 2017 9:21 AM To:af@afmug.com Subject: [AFMUG] flapping ethernet port ospf workaround So ive been dealing with the SAFs and the mikrotiks being uppity with one another. SAF has a gigabit port, but it only offers the option to lock it to 100, not gigabit. so I have the mikrotiks set, just not the otherside, the port still flaps on both radios what was happening is everytime it flaps, the interface dropped in ospf and went neighbor down, rerouting traffic then coming back up what I did was made a bridge, added that port to it, and put the ospf ip on the bridge itself, this allows the port to flap without the ospf interface going down until we work throught the issue with SAF I'm wondering if this is causing some other harm having it on the bridge, rather than the physical port
Re: [AFMUG] flapping ethernet port ospf workaround
Yeah, because the Ethernet standard *requires* negotiation. Forcing it breaks spec. Companies that allow breaking spec on their gear at the Ethernet level do so to mask their own chip and driver problems (imo). On Jul 19, 2017 2:55 PM, "Steve Jones" wrote: hopefully the SAF guys will get me a CLI or something to just configure the port at 1000. Anybody know why this is, Its like this on powercode BMUs also, you can only select up to 100 on the gigabit ports. I seem to recall reading something sometime back about that being somewhat common On Wed, Jul 19, 2017 at 2:51 PM, Chuck McCown wrote: > All surge suppressors can and probably will cause this if there is a > ground potential difference or an unusually high amount of electrical noise > on the ground that the surge suppressor is connected to. > > Lift the ground off the surge suppressor to see if that helps. > > *From:* Steve Jones > *Sent:* Wednesday, July 19, 2017 1:49 PM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] flapping ethernet port ospf workaround > > BBDGE > its got the transtector surge suppressor, I'm suspecting that, this is the > only lik with it and both radios are doing it > > On Wed, Jul 19, 2017 at 2:44 PM, Colin Stanners > wrote: > >> Do you have shielded cable the whole way end to end? SAFs seem to be >> quite sensitive to that. >> >> On Jul 19, 2017 11:20 AM, "Steve Jones" >> wrote: >> >>> So ive been dealing with the SAFs and the mikrotiks being uppity with >>> one another. >>> SAF has a gigabit port, but it only offers the option to lock it to 100, >>> not gigabit. >>> so I have the mikrotiks set, just not the otherside, the port still >>> flaps on both radios >>> >>> what was happening is everytime it flaps, the interface dropped in ospf >>> and went neighbor down, rerouting traffic then coming back up >>> >>> what I did was made a bridge, added that port to it, and put the ospf ip >>> on the bridge itself, this allows the port to flap without the ospf >>> interface going down until we work throught the issue with SAF >>> >>> I'm wondering if this is causing some other harm having it on the >>> bridge, rather than the physical port >>> >> >
Re: [AFMUG] flapping ethernet port ospf workaround
This right here. There is still a much bigger underlying problem, and putting OSPF on the bridge is only a palliative fix. Chris Wright Network Administrator From: Af [mailto:af-boun...@afmug.com] On Behalf Of Adam Moffett Sent: Wednesday, July 19, 2017 3:57 PM To: af@afmug.com Subject: Re: [AFMUG] flapping ethernet port ospf workaround OSPF didn't lose the neighbor, but you still want to fix the ethernet issue. One thing that could be an issue is if you want OSPF to fail over to a secondary path. If the interface goes down, then the router knows instantly that something is wrong and convergence can start right away. If the path is down while the interface stays up, then the router has to wait for hello packets to time out before it's aware of the issue. The default dead timer is 40 seconds, so the "it's down but I don't know yet" condition has to last at least that long before the router takes action. -- Original Message -- From: "Steve Jones" To: "af@afmug.com" Sent: 7/19/2017 3:03:11 PM Subject: Re: [AFMUG] flapping ethernet port ospf workaround if this doesn't harm anything, I'm thinking I may make this the standard, its flapped 24 times since I put it in, not a single ospf drop On Wed, Jul 19, 2017 at 1:54 PM, Chris Wright wrote: I’ve had to run OSPF on a bridge in a pinch, and so long as you don’t make any live changes to the bridge (adding/removing interfaces), the Mikrotik won’t mind. Just remember to set your static OSPF interfaces (if you have any) accordingly. Same goes for MPLS – LDP Interfaces if you’re using it. If you’re thinking it’ll be like this for longer than a week, leave yourself plenty of documentation to backtrack properly. Nothing like coming back to it three months later and trying to remember what you did! Chris Wright Network Administrator From: Af [mailto:af-boun...@afmug.com] On Behalf Of Steve Jones Sent: Wednesday, July 19, 2017 9:21 AM To: af@afmug.com Subject: [AFMUG] flapping ethernet port ospf workaround So ive been dealing with the SAFs and the mikrotiks being uppity with one another. SAF has a gigabit port, but it only offers the option to lock it to 100, not gigabit. so I have the mikrotiks set, just not the otherside, the port still flaps on both radios what was happening is everytime it flaps, the interface dropped in ospf and went neighbor down, rerouting traffic then coming back up what I did was made a bridge, added that port to it, and put the ospf ip on the bridge itself, this allows the port to flap without the ospf interface going down until we work throught the issue with SAF I'm wondering if this is causing some other harm having it on the bridge, rather than the physical port
Re: [AFMUG] flapping ethernet port ospf workaround
Id rather wait a little for a hello than have reconvergence across the network any day. Granted that attitude comes from a long time ago on a tranzeo based layer 2 network where they implemented rstp but got greedy and adjusted timers, those were awful days, just awful. I have a support ticket with saf going, i chose mikrotik because of the features at the cost, i knew going into it mikrotik is a little bugomatic factory. This only becam an issue after pulling the hp switches between the radios and router when i took the layer 2 component off the distribution network. Lower cost routers come with an increased toolset of bandaids and fukitol On Jul 19, 2017 7:06 PM, "Chris Wright" wrote: > This right here. There is still a much bigger underlying problem, and > putting OSPF on the bridge is only a palliative fix. > > > > Chris Wright > > Network Administrator > > > > *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Adam Moffett > *Sent:* Wednesday, July 19, 2017 3:57 PM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] flapping ethernet port ospf workaround > > > > OSPF didn't lose the neighbor, but you still want to fix the ethernet > issue. > > > > One thing that could be an issue is if you want OSPF to fail over to a > secondary path. If the interface goes down, then the router knows > instantly that something is wrong and convergence can start right away. If > the path is down while the interface stays up, then the router has to wait > for hello packets to time out before it's aware of the issue. > > > > The default dead timer is 40 seconds, so the "it's down but I don't know > yet" condition has to last at least that long before the router takes > action. > > > > > > ------ Original Message -- > > From: "Steve Jones" > > To: "af@afmug.com" > > Sent: 7/19/2017 3:03:11 PM > > Subject: Re: [AFMUG] flapping ethernet port ospf workaround > > > > if this doesn't harm anything, I'm thinking I may make this the standard, > its flapped 24 times since I put it in, not a single ospf drop > > > > On Wed, Jul 19, 2017 at 1:54 PM, Chris Wright wrote: > > I’ve had to run OSPF on a bridge in a pinch, and so long as you don’t make > any live changes to the bridge (adding/removing interfaces), the Mikrotik > won’t mind. Just remember to set your static OSPF interfaces (if you have > any) accordingly. Same goes for MPLS – LDP Interfaces if you’re using it. > If you’re thinking it’ll be like this for longer than a week, leave > yourself plenty of documentation to backtrack properly. Nothing like coming > back to it three months later and trying to remember what you did! > > > > Chris Wright > > Network Administrator > > > > *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Steve Jones > *Sent:* Wednesday, July 19, 2017 9:21 AM > *To:* af@afmug.com > *Subject:* [AFMUG] flapping ethernet port ospf workaround > > > > So ive been dealing with the SAFs and the mikrotiks being uppity with one > another. > > SAF has a gigabit port, but it only offers the option to lock it to 100, > not gigabit. > > so I have the mikrotiks set, just not the otherside, the port still flaps > on both radios > > > > what was happening is everytime it flaps, the interface dropped in ospf > and went neighbor down, rerouting traffic then coming back up > > > > what I did was made a bridge, added that port to it, and put the ospf ip > on the bridge itself, this allows the port to flap without the ospf > interface going down until we work throught the issue with SAF > > > > I'm wondering if this is causing some other harm having it on the bridge, > rather than the physical port > > > >
Re: [AFMUG] flapping ethernet port ospf workaround
So I went an put Procurves in at both sites, its so far completely stable, no CRCs or FCS errors. Im attributing this to mikrotiks historic negotiation issues. I wish everybody would just use whatever it is HP uses, Ive had negotiation issues with various vendors and environments over the years with the exception of HP gear, it always seems to just work On Wed, Jul 19, 2017 at 8:31 PM, Steve Jones wrote: > Id rather wait a little for a hello than have reconvergence across the > network any day. Granted that attitude comes from a long time ago on a > tranzeo based layer 2 network where they implemented rstp but got greedy > and adjusted timers, those were awful days, just awful. > I have a support ticket with saf going, i chose mikrotik because of the > features at the cost, i knew going into it mikrotik is a little bugomatic > factory. This only becam an issue after pulling the hp switches between the > radios and router when i took the layer 2 component off the distribution > network. > Lower cost routers come with an increased toolset of bandaids and fukitol > > On Jul 19, 2017 7:06 PM, "Chris Wright" wrote: > >> This right here. There is still a much bigger underlying problem, and >> putting OSPF on the bridge is only a palliative fix. >> >> >> >> Chris Wright >> >> Network Administrator >> >> >> >> *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Adam Moffett >> *Sent:* Wednesday, July 19, 2017 3:57 PM >> *To:* af@afmug.com >> *Subject:* Re: [AFMUG] flapping ethernet port ospf workaround >> >> >> >> OSPF didn't lose the neighbor, but you still want to fix the ethernet >> issue. >> >> >> >> One thing that could be an issue is if you want OSPF to fail over to a >> secondary path. If the interface goes down, then the router knows >> instantly that something is wrong and convergence can start right away. If >> the path is down while the interface stays up, then the router has to wait >> for hello packets to time out before it's aware of the issue. >> >> >> >> The default dead timer is 40 seconds, so the "it's down but I don't know >> yet" condition has to last at least that long before the router takes >> action. >> >> >> >> >> >> -- Original Message -- >> >> From: "Steve Jones" >> >> To: "af@afmug.com" >> >> Sent: 7/19/2017 3:03:11 PM >> >> Subject: Re: [AFMUG] flapping ethernet port ospf workaround >> >> >> >> if this doesn't harm anything, I'm thinking I may make this the standard, >> its flapped 24 times since I put it in, not a single ospf drop >> >> >> >> On Wed, Jul 19, 2017 at 1:54 PM, Chris Wright >> wrote: >> >> I’ve had to run OSPF on a bridge in a pinch, and so long as you don’t >> make any live changes to the bridge (adding/removing interfaces), the >> Mikrotik won’t mind. Just remember to set your static OSPF interfaces (if >> you have any) accordingly. Same goes for MPLS – LDP Interfaces if you’re >> using it. If you’re thinking it’ll be like this for longer than a week, >> leave yourself plenty of documentation to backtrack properly. Nothing like >> coming back to it three months later and trying to remember what you did! >> >> >> >> Chris Wright >> >> Network Administrator >> >> >> >> *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Steve Jones >> *Sent:* Wednesday, July 19, 2017 9:21 AM >> *To:* af@afmug.com >> *Subject:* [AFMUG] flapping ethernet port ospf workaround >> >> >> >> So ive been dealing with the SAFs and the mikrotiks being uppity with one >> another. >> >> SAF has a gigabit port, but it only offers the option to lock it to 100, >> not gigabit. >> >> so I have the mikrotiks set, just not the otherside, the port still flaps >> on both radios >> >> >> >> what was happening is everytime it flaps, the interface dropped in ospf >> and went neighbor down, rerouting traffic then coming back up >> >> >> >> what I did was made a bridge, added that port to it, and put the ospf ip >> on the bridge itself, this allows the port to flap without the ospf >> interface going down until we work throught the issue with SAF >> >> >> >> I'm wondering if this is causing some other harm having it on the bridge, >> rather than the physical port >> >> >> >>